fix(5363): fix memory leaks during unmount

fix #5363
We created invoker at here and reference component instance.
https://github.com/vuejs/core/blob/c35ec47d73212b1b1fb1abca9004f992c45aa942/packages/runtime-dom/src/modules/events.ts#L107-L132
These elements reference invoker's closure
https://github.com/vuejs/core/blob/c35ec47d73212b1b1fb1abca9004f992c45aa942/packages/runtime-dom/src/modules/events.ts#L81-L82
So after removeChild, these elements become detached, even can't remove component instance.
https://github.com/vuejs/core/blob/9aa5dfd4bb8efac0041e33ef5fdbebab59cc6516/packages/runtime-dom/src/nodeOps.ts#L17
Because we should remove these references before removeChild:

As long as a reference is kept on the removed child, it still exists in memory, but is no longer part of the DOM. It can still be reused later in the code.  mdn

No idea how to test, but I prepared a repo, you can test on it, just do like #5363
https://github.com/caozhong1996/v3-memory-leaks/tree/main/abnormal

https://github.com/caozhong1996/v3-memory-leaks/tree/main/normal

Not only removed elements, but also removed component instance.
BTW, in the development environment, these code will cause the same problem, but I don't know how to avoid.
https://github.com/vuejs/core/blob/15adf251ab69459fc5713f66921781931f3a517f/packages/runtime-core/src/renderer.ts#L697-L706
asides
尤大新年好，以下纯属“迷弟”行为：
你一直是我前进路上的榜样，所以我想加上你的微信（单纯加微信，不尬聊，也是我一个新年小愿望）。
这个pr也花了两个晚上追踪（不一定完全正确，但是大体思路是这样的），element-plus也有这个issue 4434，vue一直很重视性能，我想这应该算不小的提升，所以趁此机会提一下。
除此之外，我也有10个pr被merge，应该可以筛选出我不是低素质的人，保证不打扰，信息也绝不外泄（我也不太社交）。
虽然这样确实不适合，但是也找不到别的方法。另外这真不是道德绑架，可以直接拒绝的。如有冒犯，希望不要介意，下次不会了。
我的微信: justmilkplease

Hi buddy, I need to confirm whether #5363 #5400 already been fixed and already been merged to main branch, because I could not find it been mentioned in changelog. Very much appreciated if you can reply me ASAP, thanks.

Hi buddy, I need to confirm whether #5363 #5400 already been fixed and already been merged to main branch, because I could not find it been mentioned in changelog. Very much appreciated if you can reply me ASAP, thanks.
Nope, it's related to the weird behavior of chrome🙈


remove desword from nukie uplink

the nightmares wont stop
🆑

remove: Removed desword from nukie uplink.

Considering from what I've seen I agree with the removal.
A team of nukies with deswords sounds insane considering the reflection and pseudo-resistances.

glowing approval no objections send it


API V2

Type of change

[ ] Refactor
[x] New feature
[ ] Bug fix
[ ] Optimization
[ ] Documentation Update

Description
Adds new API version
Adds new endpoint for Homepage in the dashboard
Takes dates to filter results returned
Related Tickets & Documents

Related Issue #
Closes #

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please describe the System Under Test.
Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

/lgtm


jsdoc: type expressions containing new lines aren't parsed

TypeScript Version:  master
Code (JavaScript)
/**
 * @typedef {(
 *     string | number)}
 */
var NumberLike;

/**@type {NumberLike}*/
var x;

Expected behavior: the type of x should be string | number.
Actual behavior: x is any.
Works if rewritten like this:
/**
 * @typedef {(string | number)}
 */
var NumberLike;

/**@type {NumberLike}*/
var x;

They are parsed, as long as you don't put the * inside the {} block.
This causes odd-looking comment blocks, but at least it's not completely unsupported.

@sandersn @RyanCavanaugh this has been fixed for a while.

Yes, it works now (TS 3.1.3),


Accessibility: Mark document-like outputs with role="document" for easier screen reader navigation.

While it is appropriate to treat large parts of VS Code as an application for screen readers, there are areas where it makes sense to suggest to screen readers to use their browse mode (AKA virtual cursor) mode navigation paradigm instead. Places I've found this to be the case are, among possibly more:

The Welcome page.
Details for an extension.
After an extension has been installed, the ReadMe HTML output.

All of these are places where structured HTML output is generated for pure consumption and possibly following links or initiating things like installing or uninstalling an extension, etc., but not more complex interactions.
I found this while trying out Code for the first time for real, using current 1.44 Insider builds.

Additional info:

NVDA is using an appModule to disable browse mode by default in VS Code. If we don't do this, browse mode is enabled automatically in many parts of the application where it shouldn't be active.

I would say that an application role on the body element can help a lot, as long as all documents such as extension information, welcome page and other document like content have the document role.

Thanks for filling this. Agree with your feedback. We already set the role=application on the top level element.
I wll look into setting role=document on our readonly content. Like the welcome page, extension details and other read only content we might have.
fyi @chrmarti @sandy081

According to the NVDA developer info, the application role is set on the div with class="monaco-workbench". However, the status bar and the monaco-alert are outside that application div.
Having said that, the document role is set on an element that is the parent of the body element, so may be this is an electron thing.

@leonardder I do see that monaco-alert is outside the application div. @bpasero why did we put it out of the workbench, does it make sense to move it inside the workbench div? We create it [here] (https://github.com/microsoft/vscode/blob/0687d65b30a752cef32490bca7ca85f4b41015b2/src/vs/base/browser/ui/aria/aria.ts#L19)
However for the status bar I see it is inside the monaco-workbench div. @leonardder are you sure for you it does not belong to the monaco-workbench div?

according to NVDA, there is a monaco-status in the monaco-aria-container, sibling of the alert container. This is based on what NVDA gets from IA2, though.

I do see that monaco-alert is outside the application div.

No specific reason as far as I can remember.

I have pushed two changes:

monaco-alert is now inside the role=application div
I have changed the welcome page and the extension details page to use role=document

@MarcoZehe @jvesouza @ajborka please let me know if there are other places in VS Code where the role=document would be more fitting?

How about for editors which are read only? Is the current role textbox fitting?
How about for Outputs? For example F1 > Show Git Output
How about for Terminal which uses the rool toolbar, should we use a more correct role there? F1 > toggle integrated termianl to get it.

@isidorn What about the display of Readme files from installed extensions? These are HTML-ified .md files AFAIK, and the role =„document“ would be appropriate there, too.
As for the terminal, the input is a textbox, the output is definitely not a toolbar. A toolbar is a container for buttons. The output is either a read-only textbox or, if links are provided etc., a document role would also be appropriate here, as this would then kind of act like an HTML document.

@MarcoZehe from installed extensions are markdown preview editors. For those I am in discussion with @mattbierner so we change the role of markdown preview to document.
As for the terminal it is not a toolbar I misread the html element. It currently does not have a role.
Though I see that the each element in the terminal has a listitem  role. @Tyriar should we then assign a role of list to the terminal container element?
Output is currently textbox, is there an aria way to mark a textbox readonly? @MarcoZehe

@leonardder  your concept of turning off browse mode on the entire vscode application might have a flaw in it. When I start NVDA, then start vscode insiders 1.44, the explorer window now automatically turns off browse mode. I would like it to remain in browse mode because navigation is easier. I shouldn't be required to turn forms mode on whenever vscode starts. All you need to do as a user is create a custom profile for vscode, then in browse mode under settings, tell browse mode to remain turned off. @isidorn  it might be difficult navigating readonly text boxes with Orca. Right now, an Orca user has to press F7 in order to read readonly edit fields. I think document role would work in Windows, but not sure how it will work in Linux. Also, the markdown previews should have the document role.

@ajborka the vs code app module will be considered if we have a viable solution. I will test Insiders tomorrow to see how it behaves and will give appropriate feedback.

@MarcoZehe from installed extensions are markdown preview editors. For those I am in discussion with @mattbierner so we change the role of markdown preview to document.

That sounds right, since the preview is always going to show the result in HTML, and that is always easier if the screen reader applies the web reading techniques rather than the application interaction model.

As for the terminal it is not a toolbar I misread the html element. It currently does not have a role.

Yes, I tested that briefly and found that only the buttons are in a tool bar, which is fine.

Though I see that the each element in the terminal has a listitem role. @Tyriar should we then assign a role of list to the terminal container element?

The direct container of all these list items should be a list. There is another div that gets focus when you shift-tab twice from the input textbox. The first tabstop is a div with class focus-trap or so directly preceding the input. The second shift-tab, a div container to all the output items, is what I would consider the candidate for role="document".

Output is currently textbox, is there an aria way to mark a textbox readonly? @MarcoZehe

Yeah, but that's probably not what we want, not if we also linkify stuff in there. And it would mean we'd still need arrow/caret navigation, which a read-only div doesn't give us. So instead of a textbox for the output, as stated above, document is more appropriate.

@leonardder your concept of turning off browse mode on the entire vscode application might have a flaw in it. When I start NVDA, then start vscode insiders 1.44, the explorer window now automatically turns off browse mode. I would like it to remain in browse mode because navigation is easier.

Question, how is file explorer easier in browse mode, AKA with the virtual cursor? It is a tree view, and a set of buttons related to the selected file or folder, and a tree view would require focus/forms mode anyway. I'd say the global role="application" as is already the case is exactly what we want, with some selected bits getting the document role as this issue originally discussed. Tomorrow's insider build will have @isidorn's changes, so we can see how they affect things. I'm almost certain this will be positive.

Question, how is file explorer easier in browse mode, AKA with the virtual cursor? It is a tree view, and a set of buttons related to the selected file or folder, and a tree view would require focus/forms mode anyway. I'd say the global role="application" as is already the case is exactly what we want, with some selected bits getting the document role as this issue originally discussed. Tomorrow's insider build will have @isidorn https://github.com/isidorn 's changes, so we can see how they affect things. I'm almost certain this will be positive.
As long as the explorer gets the document role(I would hate to lose the ability to browse it like a website), or each element of the explorer view had a keyboard shortcut that is easy to use and remember. I come from the age of traditional/conservative software design. For example, instead of having a chorded shortcut for each button/element/component in the explorer view, F6 traditionally cycled through components on the screen. The Microsoft Office apps are a good example of using F6 to cycle between the panes/panels in a window. Maybe this requires a different discussion, so I will stop. However, @@joanmarie https://github.com/joanmarie  Might be able to provide insight since she worked with the Gmail web interface which has similar issues.

Not sure how it will impact Orca though. If NVDA made it possible to change settings in reference to your new app module, then it might work. Either way, we will check it out and give feedback tomorrow.

I can confirm the document role being present on the welcome page and extension details outputs in the latest insider build. This issue can be marked as verified. We should maybe file separate issues for more items that benefit from role "document" when we come across them. Now we can go and fix the VS Code app modules in NVDA, @leonardder .

@marcozehe Sounds good, thanks for letting us know. Adding verified label here.
Matt already opened a PR for adding document label for markdown preview docuemnts https://github.com/microsoft/vscode/pull/93435
For using the list role in the terminal I have opened this issue https://github.com/microsoft/vscode/issues/93480
For using the document role in the output I have created this issue https://github.com/microsoft/vscode/issues/93481
For all othere element please create separate issues.
Thank you very much


New converter trustMarkdown check is inverted

The new trustMarkdown boolean for #503 is inverted:
https://github.com/microsoft/vscode-languageserver-node/blob/ccb894231aae0942d2cc29fd2381ccf51ac4f823/client/src/common/protocolConverter.ts#L249
I think this is a typo and should have been !!trustMarkdown to convert to a default value of false. Maybe the more readable trustMarkdown ?? false... :)

Good catch. I don't even know why that was in there since the line is totally unnecessary since the test is if (trustMarkdown === true)
Removed the line.


Memory efficient undoredo support

Alternatively, instead off keeping a copy of the root_tag (TagSVG) , signal up from Attributes new_value and old_value then from tagB then add child_tag , attribute_name

Working well


Left label identification by class or id

It'd be nice to have way to hook anything to line-labels. Like tooltips when mouse over. atm only way to find it, is a txt that and it changes when user scroll it.
maybe even integrated tooltip mechanism for that :)

I actually have that functionality implemented somewhere.
You could make the chart add a div and then position the tooltip, however as the chart is not returning a div to wrap it in, I don't think that would be a nice solution.
The demo example shows how one can add it to the drops. Currently, I have something similar, where I attach a callback on mouseover on the text labels. In D3 it's easy to get the value and it works quite well. Maybe also add ellipisis to the text (the name) and not the numbers, so in case the text get's quite big it can overflow? Or maybe allow setting a different font-size.
Personally, I use popper.js to position the tooltip as some of mine are quite big.

@Sarseth
Here is an example of what I have done in the past:
I use a function to get the text length (as font's differ) then if the length is more, I shorten it until it will fit the screen, as well as ...;
Too long desc ... (120)
Then when I do
.text(function(d) {
 // Add the text and any logic you need
// If the length is too long, add a shortName to the data element
}).on('mouseover', function(d) {
 if (d.shortName !== undefined) {
    onMouseOver(d);
 }
})

Example:

Awesome, thanks, will tinker with what you provide here tomorrow :)

So I made a PR to expose the onMouseOver and onMouseOut here: #273
If you download the files and then run the make command you can include the files into your project and take it from there.
Here is an example, where index.js is the EventDrop with the tooltip added (Couldn't paste it on JsBin as too large).
Github gist


Request for Enlight cgm support

Would like to test on 723 v2.4a with enlight and connect and enlight/RileyLink pairs

Bill, do you have a RileyLink so you can test this feature?

On Jun 22, 2016, at 7:10 PM, Bill Stackpole<EMAIL_ADDRESS>wrote:
Would like to test on 723 v2.4a with enlight and connect and enlight/RileyLink pairs
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Let me know if you have issues with this.  The NS uploader does attempt to take BG data from mysentry packets and upload them to NS entries.  It used to work back when we were using it, but a lot of code has changed, and I haven't tested it recently.

Yes - more than one in case one fails.


Corrected 6x8 font

Apologies for pushing the wrong dev version of the 6x8 font previously!

Relevant commit has been cherry-picked into #70


Support for lost signal and new client

Use Case
We are creating a canary environment and we needed to set signal and expiration configs
Decisions
I did not leveraged alerts.AlertsNrqlConditionSignal and alerts.AlertsNrqlConditionExpiration since the json annotation were not adding omit_empty possibly causing a breaking change.
Moreover one of the field was float64 that is not supported and discuraged by the generator
Fix https://github.com/newrelic/newrelic-kubernetes-operator/issues/135

@thande pinging you after slack conversation :)
Let me know if the approach is correct, I tried to follow the same structure you had already in place

@thande any news on this?


Release/7.1.0

Other Changes

Fix missing gitignore causing release process errors via Toni Rico (@tonidero)

Dependency Updates

[AUTOMATIC BUMP] Updates purchases-hybrid-common to 7.3.0 (#142) via RevenueCat Git Bot (@RCGitBot)

Android 7.2.0
iOS 4.30.2

Did this manually, and should be ready now.

Yay awesome!

Good to deploy?

Yup! Started deploy

Awesome! Capacitor was a bit behind, so glad we're all up to date now 🙏🏻


Excuse me, I would like to ask how to perform semantic segmentation tasks, such as training your own data set

Hi, we use mmseg library to perform semantic segmentation. Full readme would be released here.

Hi, we have released the segmentation checkpoint and scripts here.
If you want to fine-tune your own dataset, please refer link to prepare your own dataset.

can you help me how to modify your code to infer on single image? I tried to set ADE20K data following your guide but the official ADE20K data structure is different from your guide.


Wrong assumption for sharding_index name

vshard configuration has an option to specify a name or id of sharding index, by default it values is 'bucket_id'. It's up to the user to change it or keep the default value [1].
Source code of ddl/check.lua has a wrong assumption for sharding index name:

https://github.com/tarantool/ddl/blob/master/ddl/check.lua#L641
https://github.com/tarantool/ddl/blob/master/ddl/check.lua#L669
https://github.com/tarantool/ddl/blob/master/ddl/check.lua#L677-L698

https://www.tarantool.io/en/doc/latest/reference/reference_rock/vshard/vshard_ref/#confval-shard_index

The decision to make it so strict was conscious. We've interviewed many vshard users, and they all agreed that the custom sharding index is confusing.

Well, let's wait until someone will ask for that.

More on the topic:
https://github.com/tarantool/ddl/blob/master/ddl/check.lua#L641

index of %s type can't be composite

This is not a correct statement.
We always use a composite index for sharding. The tail of such an index is the primary key.


中文显示bug

最新稳定版本Harbor 1.2.2

请提供截图？

@ninjadq
Please take a look! Thanks!

@robinwangrubin
Are you install v1.2.2 from scratch or upgraded from other earlier version?

@ninjadq  Yes i am, I update v1.2.2 From v 1.1.1

@ninjadq  Do you have any update solutions to solve this problem?

This issue seems like i18n file not upgrade properly. You should clear cache first if it still exist you can try to restore and upgrade again.


add LICENSE

Hello, could you please add the LICENSE file to the project?

Done. Thanks!

Arigato)


Bring back the setting to automatically redirect to the EH site

需求 / Requirement
Please, bring back the setting to automatically redirect to the EH site
原因 / Reason
I live in Russia and for a long time eh has been blocking russian ips from entering, but the ex version allows entering it from a russian ip.
建议实现 / Suggested implemention
Reintroduce the aforementioned setting
备注 / Addition details
No response
自查步骤 / Verify steps

[X] 您已仔细查看并知情 常见问题 中的内容 / You have checked Q&A carefully
[X] 您已搜索过 Issue Tracker，没有找到类似内容 / I have searched on Issue Tracker, No duplicate or related open issue has been found
[X] 您确保这个 Issue 只提及一个问题。如果您有多个功能请求，烦请发起多个 Issue / Ensure there is only one feature request in this issue. Please make mutiply issue for mutiply bugs
[X] 您确保已使用最新版本测试，并且该问题在最新版本中仍未实现 / This feature have not supported in latest version

Oh i didn't realise it, i will add it back later.

Added it back in latest CI version, you can experient it now or wait for next release version.


Including tasks from another file does not work with the poetry plugin when the poetry command is ""

Minimal Example:
pyproject.toml:
[tool.poetry]
name = "poe-test"
version = "0.1.0"
description = ""
authors = ["Nick Valin<EMAIL_ADDRESS>
[tool.poetry.dependencies]
python = "^3.12"

[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"

[tool.poe]
poetry_command = ""
include = "tasks.toml"

tasks.toml
[tool.poe.tasks]
test = "python --version"

Run commands
poetry self add 'poethepoet[poetry_plugin]'
poetry install
poetry test

Expected result:
Poe => python --version
Python 3.12.1

Actual result:
The command "test" does not exist.
I've been looking into the code, and I believe the root cause is that the tasks from an "include" statement are not registered until after cleo is monkey patched, meaning cleo cannot find the task. The reason it works if the poetry command is not an empty string is because the poetry command is registered as a task before cleo is monkey patched. Cleo can then find the poetry command, and the plugin takes back over and finds the task from the included file.
I see two ways this can be fixed, and I'm happy to create a PR for either, though I'd like some guidance from the maintainers on the favored solution:

The easier solution is to register a dummy command (like "poe") when the poetry command is an empty string.

if command_prefix == "":
    self._register_command(
        application,
        "",
        {"help": "Run poe tasks defined for this project"},
        "poe",
    )
    for task_name, task in poe_tasks.items():
        if task_name in COMMANDS:
            raise PoePluginException(
                f"Poe task {task_name!r} conflicts with a poetry command. "
                "Please rename the task or the configure a command prefix."
            )
        self._register_command(application, task_name, task)

Then, when monkey patching cleo, add that dummy command to the token list:
if prefix == "":
    tokens.insert(0, "poe")

This allows cleo to do its thing, and the plugin can take back over and load the tasks from the included file.

The (probably) harder solution is to refactor the plugin activation to load tasks from an included file before monkey patching cleo. I haven't tested this solution yet, so I'm not totally sure about the LOE.

Would love for some feedback from the maintainers about their preferred solution.

Hi @nickvalin1, thanks for reporting this issue and working on a solution.
I checked out your branch locally to see how it runs and I've encountered a curious issue. It seems to direct all of poetry's own tasks to poe when used inside the empty_prefix test project!
I can't say I understand what's happening (or exactly how your fix it meant to work for that matter).
I'm currently in the process of refactoring how config is loaded (particularly includes), so I'll definitely return to this issue as part of that if it still isn't fixed.

@nat-n any update on the config refactor? If not, can you share a test case that would fail so I can fix my PR?

Hi @nickvalin1, Yes! the refactor is merged on the development branch. Investigating this issue is on my TODO list before the next release.

Hi @nickvalin1,
I finally came back to look at your PR. I think approach 2 is cleaner, so I added that onto your PR. Apparently I accidentally closed your PR, so I created a new one here. The fix will be in the next release soon.
Thanks again for spending time on this and sorry for the slow turn around.

This bug is now fixes with 0.26.0 🚀


Sidekiq::PeriodicJob sync_schedule enhancements

Overview
I have made a few fixes and enhancements to the Sidekiq::PeriodicJob extension, and have bundled them into a single PR. Happy to test other parts of the integration with Sidekiq Enterprise if needed 🙂
Constantize loopset class
I found when using the Sidekiq Periodic Jobs feature, the sync_schedule! feature does not seem to work. The job class on Sidekiq::Periodic::LoopSet is a string rather than a constant, therefore I have constantized it before calling the sidekiq_options method and this seems to have fixed the integration.
Add cronitor_key, cronior_grace_seconds, cronitor_group options
This allows passing in cronitor_key, cronitor_grace_seconds, and cronitor_group in the Sidekiq periodic jobs list:
mgr.register('* * * * *', 'MyPeriodicJob', cronitor_key: 'My Periodic Job', cronitor_grace_seconds: 120, cronitor_group: 'periodic')

Include timezone
Sidekiq::PeriodicJob has an option for passing in a different timezone for a job. This supports it, and will fall back on the server timezone if not present.

@dwtong thanks a lot for these updates/fixes!


Hover Menu elevation not working

Hi
I have built this library from the source from here, without any modifications, and the Hover Menu elevation seems not to work.
I found a line in the code that, if I'm not wrong, is supposed to set the elevation to the menu, but it doesn't seem to work.
This is how the Hover Menu looks like:

I'm using a device with Android 7.1.1 so the elevation should be properly set/viewed.
I hope you can fix it. Thanks in advance.

Hi Jahir, did you launch the menu in the window, or within an Activity? (there are 2 launch buttons in the demo app).

@matthew-carroll
Thanks for the reply. I launched it in the window. With the first button (from top to bottom) in the app.

Ok.  Perhaps some aspect of the elevation API changes with Android 7.  My devices on 6 are still showing the elevation shadow as far as I can tell.  I'll take a look when I get a minute.  In the meantime if you stumble upon a solution, please feel free to post it here and I'll integrate it (I haven't formalized the contribution process yet).

@matthew-carroll
Thanks. I will try to investigate a bit more. From what I have found (in the last couple days of me trying to find an answer to not bother you with this issue), all solutions were either hard for me to understand, or made with XML files. Will keep trying. Thanks.

found a solution yet? having the same problem here on android lollipop


Fix a security bug of logging bearer tokens

Please provide a description for what this PR is for: fix a security bug of logging bearer token (a bearer token is a secret and should NOT be logged).

In response to a cherrypick label: new pull request created: #19641


Feedback for “Local Setup Guide”

Step 3 is out of date, .env.example is not used anymore according to this https://github.com/cookiecutter/cookiecutter-django/issues/1773

It's not relevant to the LibreChat repo as we do make use of an example file with bare-minimum configuration for fast setup.


Update monitor-resource-reference.md

changed Cluster Name description to 'compute cluster resource' instead of 'compute instance' to avoid confusion with compute instance feature.

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

#sign-off

@PeterCLu: I'm sorry - only the author of this article, @aashishb, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@PeterCLu: I'm sorry - only the author of this article, @aashishb, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


[BUG] SEEN Configuration "Mail from", "Test Email" and others not configurable.

Describe the bug
After successfully deploying the solution via the ARM template it is not possible to set certain configuration options such as "Mail from, "Test Email", "Support Email", Support Phone" and "Admin Email".  The fields are greyed out / inactive / not editable.

Hello @MatthiasScharl , was the setup script ran successfully after the ARM template deployment?

Hello @piaudonn, I ran the deployment including the setup script again and it is working as expected. Very nice work !


check-ttf.py: "Font contains magic code in PREP table?"

Hello,
We have magiccode = "\xb8\x01\xff\x85\xb0\x04\x8d", I'm assuming this is something ttfautohint inserts or why is this needed?
My fonts which have been run through ttfautohint all fail this test.
Cheers,
Marc

This magiccode check was added to fontbakery prior to my involvement in the development. As it lacks inline documentation in the source, I have just put the effort to manually disassemble this tiny snippet of TrueType instructions bytecode in order to figure out what does it do. Here's what I figured out, based on the instruction set documentation available at https://www.microsoft.com/typography/otspec/ttinst.htm:
    magiccode = "\xb8\x01\xff" + \ # PUSHW 0x01FF
                "\x85" + \         # SCANCTRL (unconditinally turn on
                                   #           dropout control mode)
                "\xb0\x04" + \     # PUSHB 0x04
                "\x8d"             # SCANTYPE (enable smart dropout control)

    # Smart dropout control means activating rules 1, 2 and 5:
    # Rule 1: If a pixel’s center falls within the glyph outline,
    #         that pixel is turned on.
    # Rule 2: If a contour falls exactly on a pixel’s center,
    #         that pixel is turned on.
    # Rule 5: If a scan line between two adjacent pixel centers
    #         (either vertical or horizontal) is intersected
    #         by both an on-Transition contour and an off-Transition
    #         contour and neither of the pixels was already turned on
    #         by rules 1 and 2, turn on the pixel which is closer to
    #         the midpoint between the on-Transition contour and
    #         off-Transition contour. This is “Smart” dropout control.

I used ttx to inspect the prep table of Merriweather-Black.ttf and the block of truetype instructions is a bit larger than this check expects to see. But I could find this in the middle of the Merriweather-Black routines:
      PUSHW[ ]  /* 1 value pushed */
      511
      SCANCTRL[ ]       /* ScanConversionControl */
      PUSHB[ ]  /* 1 value pushed */
      4
      SCANTYPE[ ]       /* ScanType */

which is effectively what the check is expecting to find (please not that 511 is the decimal representation of 0x1FF).
So instead of expecting it to be exactly equal, maybe we should check if this tiny snippet of code is at least present in the middle of the tested font prep table bytecode.

Regarding "why this is needed?" maybe @davelab6 could clarify that to us here. I can trace it back to commit c30b7981 by @vitalyvolkov on January 2015, but it could be a bit older.

@m4rc1e I have just fixed the check to detect the presence of the expected snippet inside a larger chunk of bytecode,

Ah cool.
But still, what exactly is the purpose of this test. To check whether there is a prep table?

it's a minimal PREP table for enabling dropout control, useful to improving rendering for unhinted TTFs:
See @davelab6 comment at: https://github.com/googlefonts/fontbakery/issues/890#issuecomment-236450011
and my comment here:
https://github.com/googlefonts/fontbakery/issues/890#issuecomment-236457209

From the O'Reilly book "Fonts and Encodings" by Yannis Haralambous:
The tables fpgm and prep contain global TrueType instructions (which, therefore, are not
attached to any specific glyph). These instructions are executed when the first glyph in the
active font is typeset (for fpgm) and every time the type size or the current transformation
matrix is changed (for prep).

@m4rc1e I've just merged it into master now. Let me know if the check still fails for your font projects

Thanks folks, that's much clearer.
The comment is great.
surely dropout_control is a much more suitable variable name than magiccode

well... it was a kind of magic when it was undocumented :-P

Fabulous.
INFO     OK: Font contains magic code in 'prep' table
Thanks for this,
I've done some more fixes throughout today. I will send you a pr with those in a few hours.
Cheers,
Marc

cool, thanks.


[Docs] improve NAT and manual peering documentation

Description
This PR improves documentation about manual peering and the way to configure the network when there is a NAT in the topology

Two comments on the picture.

Typo: "gatway" instead of "gateway" :-)
To me, one of the biggest advantage of the manual Liqo peering is that for the network setup we don't care who is the provider, and who is the consumer. I think this should be stated clearly in the documentation, ans possibly reflected in the picture, where clusters could be named "cluster1" and "cluster2" instead of "consumer/provider".

/test

/merge


90th_percentile_vsync_transitions_missed99th_percentile_frame_rasterizer_time_millisaverage_vsync_transitions_missedworst_frame_rasterizer_time_millis flutter_gallery_sksl_warmup__transition_perfflutter_gallery_sksl_warmup__transition_perf_e2e regressions

https://flutter-flutter-perf.skia.org/e/?begin=1603669622&end=1603752548&keys=Xd5f06ed0bf6f897c371d6f777fb1dccc&num_commits=50&request_type=1&xbaroffset=22190
Started around https://github.com/flutter/flutter/pull/68887. If that really is the commit, I think these are related to the tests themselves, and not true regressions.

These benchmarks were affected the first time the noted change was landed and reverted, so it is probably related, but I agree that the tool's drive command refactoring probably shouldn't have been able to have such a big effect on these numbers. @jonahwilliams @liyuqian

/cc @jonahwilliams and @liyuqian to determine if there's anything actionable here.

The tools could have a big impact on performance and "[flutter_tools] fix --use-existing-app for flutter drive #69237" does seem to be a promising fix. Specifically, flutter_gallery_sksl_warmup__transition_perfflutter_gallery_sksl_warmup__transition_perf_e2e verifies that the existing app built SkSL cache is fast. If the tool doesn't properly run the existing app built with SkSL cache, then there will be regressions.

It looks like this one recovered on https://github.com/flutter/flutter/commit/735f6eec2caf0c123d6328cf2a9e6f1be21ee274


Unable to determine docker version error

~> docker-credential-gcr configure-docker
ERROR: Unable to determine Docker version: strconv.ParseInt: parsing "3'\n": invalid syntax
~> docker version
Client:
Version:      1.12.3
API version:  1.24
Go version:   go1.6.3
Git commit:   6b644ec
Built:        Wed Oct 26 21:39:14 2016
OS/Arch:      linux/amd64
Server:
Version:      1.12.3
API version:  1.24
Go version:   go1.6.3
Git commit:   6b644ec
Built:        Wed Oct 26 21:39:14 2016
OS/Arch:      linux/amd64

~> docker-credential-gcr version
Google Container Registry Docker credential helper 1.3.1

Thanks for reporting! There was an issue with the version parsing code which resulted in that error for some users, and has been fixed in 1.3.2, which will be included in the next gcloud release.

Your attempt to create an issue via email has failed.
Reason:
User did not have permission to make an update in component '166824'
For information on how to use Buganizer's email interface please visit
http://wiki.corp.google.com/twiki/bin/view/Main/BuganizerHelpEmailAccessToBuganizer.
Thanks!
Buganizer
Original body:
@KingEmet is there a way to use the 1.3.2 version now? I am getting the
same error
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/docker-credential-gcr/issues/6#issuecomment-273403631
--
You received this message because you are subscribed to the Google
Groups "container registry contact" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit
https://groups.google.com/a/google.com/d/msgid/gcr-contact/GoogleCloudPlatform/docker-credential-gcr/issues/6/273403631%40github.com.

@dantei Yup, you can download a compiled binary for your appropriate platform here: https://github.com/GoogleCloudPlatform/docker-credential-gcr/releases/tag/v1.3.2

Your attempt to create an issue via email has failed.
Reason:
User did not have permission to make an update in component '166824'
For information on how to use Buganizer's email interface please visit
http://wiki.corp.google.com/twiki/bin/view/Main/BuganizerHelpEmailAccessToBuganizer.
Thanks!
Buganizer
Original body:
@dantei Yup, you can download a compiled binary for your appropriate
platform here:
https://github.com/GoogleCloudPlatform/docker-credential-gcr/releases/tag/v1.3.2
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/docker-credential-gcr/issues/6#issuecomment-273536147
--
You received this message because you are subscribed to the Google
Groups "container registry contact" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit
https://groups.google.com/a/google.com/d/msgid/gcr-contact/GoogleCloudPlatform/docker-credential-gcr/issues/6/273536147%40github.com.

@dantei gcloud sdk v140 is out as of now

Your attempt to create an issue via email has failed.
Reason:
User did not have permission to make an update in component '166824'
For information on how to use Buganizer's email interface please visit
http://wiki.corp.google.com/twiki/bin/view/Main/BuganizerHelpEmailAccessToBuganizer.
Thanks!
Buganizer
Original body:
@dantei gcloud sdk v140 is out as of now
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/docker-credential-gcr/issues/6#issuecomment-273541721
--
You received this message because you are subscribed to the Google
Groups "container registry contact" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit
https://groups.google.com/a/google.com/d/msgid/gcr-contact/GoogleCloudPlatform/docker-credential-gcr/issues/6/273541721%40github.com.


Revert "Second attempt: grpclb stabilization"

Reverts grpc/grpc#22481
After this PR the client_channel_stress_test started timing out again.  Btw, setting test size to large is not helping because the variance of the duration of the test has went through the roof, so we're still seeing cases where even 1800s is not enough
See b/153136407
Btw, anytime we want to use size=large  we should pay attention to what the avg runtime is and what the variance is and deciding if increasing the test size makes sense at all. I've noticed that people generally like to resort to increasing the timeout as quick-and-easy solution whenever they see a timed out test, rather than investigating why the test is slow (and trying to fix that) and checking that increasing the timeout actually helps. Experience shows that this only leads to increased test latency (with increased timeout it takes long time before a stuck test is stopped) and not necessarily to decreased flakiness.

@markdroth we've held the revert PR for over two working days, but we don't have a fix and based on what I can tell based on the internal discussion, we're not any closer to a fix forward than we were. At the same time this is now our top flake and it's not practical to mark it as Flaky = true because the timeout is 1800s so retrying would become the bottleneck in the entire test suite. I don't think it's fair to let this test harm our test health for any longer. (and TBH, I do think that the overhead of everyone else on the team running into the flake on PRs, seeing it constantly in the dashboards and the costs of tracking it is much worse than the cost to revert and roll forward)
Please approve so we can merge the revert (and sorry for needing to do extra work, but I do think strict enforcement of the revert policy is important for our long term test health).

Closing this in favor of #22602.


MANIFEST.in is required to have the resources installed correctly

cf http://python-packaging.readthedocs.io/en/latest/non-code-files.html

I'm no longer interested in maintaining this. Would you like to become the maintainer?

@agronholm "this" being js.jqgrid, js.jqueryui_selectmenu, js.jqueryui_syronex_colorpicker and js.jquery_markitup ?

Only js.jqgrid.

@ochriste This repo is not being maintained any longer. The last change was from 4 years ago and the js library is probably terribly out of date.
I see that you forked it and I see that this package does not get pulled a lot from anybody.

If you are interested in maintaining this package, feel free to tell me your pypi username and I add you.


Static extensions

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

/retest

/retest


Add Python binding support

I've started work on enabling Python binding support in our cerbero build here: https://github.com/superdump/cerbero/tree/pygi
It currently has this issue on OS X: https://gist.github.com/superdump/358454535dcae162ee05

https://github.com/EricssonResearch/cerbero/pull/30

I've made some progress on this and have pushed those changes to cerbero. I'll keep going a bit more and hopefully stabilise this and make it more reliable.

Is there any documentation on how to connect openwebrtc in to the python environment and run the python tests? Installing with the posted binary packages doesn't seem to be enough:
ImportError: cannot import name Owr, introspection typelib not found

@andrewpew Did you get this working with the binary or did you build it?

@bitdivision I built it myself. I have never tried it with the pre-built binary.


How to stub out Count?

We have a func that uses sth like  db.DbClient.Model(&Countable{}).Where("filter = ?", filter).Count(&count), any way to set query that could help to test with testdb?

Solved.
testdb.SetQueryFunc(func(query string) (driver.Rows, error) {
	columns := []string{"count"}
	result := `
	1`
	return testdb.RowsFromCSVString(columns, result), nil
})


Feature Request: Add support for "delete" to NuSpec Alias

What You Are Seeing?
There are times when something goes wrong and there is a need to "delete" one or more nuget packages from a server.  It would be nice if this was possible via cake
What is Expected?
Add NuGetDelete Alias to NuSpec namespace

@ravensorb just to confirm... This would be a standalone task within the build.cake file right?  This isn't something that you would want to do as part of the automated build process.  It seems like quite a dangerous operation.

Correct, this would be just an alais that someone creating a build.cake file could use if they wanted to.  For me, I have an Task called "UnPublish" that allows me to unpublish the last build or override with a specific build I use this if a regression error was accidentally introduced in nuget packages that is not discovered until after they are published to nuget.org -- considering how amazingly difficult it is to automate testing packages (installations, upgrades, etc) sometimes the only option is to pull down a package if it is not working.

@cake-build/team what are your thoughts on this one?

@ravensorb are you in a position to submit a PR for this?

Closing as #2784
The NuGetDelete alias is available since Cake v0.38.0
We also have a DotNetNuGetDelete alias since Cake v2.0.0 that runs dotnet nuget delete


dumps claim file as CSV with telco/non-telco

New TNF command t dump claim results as CSV with classification information.
Required inputs:

a list of "telco" CNF names to identify which CNF names are "telco"
a claim file
the name of the CNF to which the claim file belongs to

The test case catalog, classification table and telco CNF list are used to do the following:

the catalog is used to add a remediation column to each test case in the generated CSV
the classification is used to determine whether a test case is mandatory or optional (and add a column). The determination is based on the test name and CNF type (telco/non-telco)
add a telco/non-telco column based on the telco CNF list

I'm ok if you want to add this new command, but I must say that it sounds too specific to me. The subcommand name itself "csv-telco" restricts it to just a csv output for either telco or non-telco workloads. But what about the other workload types?

using JSON file to import the CNF name to type mapping (in latest commit) makes this command more generic -- to support all types. It is renamed "show csv". In the future, we can update the "show failures" command to support an even more generic export to CSV and various modifiers beyond the simple merge and dump of this command or include the classification/catalog to the claim file directly.


blur_xray does not xray with windows on special workspaces

Please consult the issue guidelines at
https://github.com/vaxerski/Hyprland/blob/main/docs/ISSUE_GUIDELINES.md
BEFORE submitting.
Steps to reproduce:

Turn on blur_xray in hyprland config (with prereqs)
Open terminal with transparency (in my case foot)
Float terminal, and see blurred background as expected
Unfloat terminal, and open terminal on special workspace (scratchpad)
See blurred everything open, and not background

Expected outcome:
I expected that blur_xray would work the same for floating windows on special workspaces the same as on the same workspace
Noted outcome:
Rather, floating transparent windows on special workspaces will blur all of the opened apps (as pictured) and not the background.
Noticed on Arch 0.24.1-1 package, but I also tested on the latest Hyprland commit, as requested in the above guidelines, and got the same result.
Here is when floating a window of the same workspace

Here is when floating a window on a special workspace

fixed in 28dfe215844fe33d425bda33c677a0fae835082b

whoopsie daisy 72b118cd8f8fc56e611a6b357c844637b85ccc54


Fix WNS layout and other CSS bits.

@richburdon I can now see the logs in a separate div, but nothing on the top. This is on my Mac. I will give it a shot in the Docker on the NUC as well.


Support mobile authentication via OAuth2

The OAuth stuff that is about to land will work just fine on mobile if you are inside a browser. However, if you are talking to feathers from a native app or from React Native you won't be able to follow the redirects that are required for the OAuth flow. Therefore, we need to optionally support token based social auth like passport-facebook-token where you would already have the access token from authenticating with the OAuth provider on the mobile device.
My thought is that a developer can include the this strategy and pass it as a tokenStrategy option. If that option is passed we set up that token strategy (potentially along side the regular strategy) and then map that to the create service method (ie. POST /auth/facebook).

There may be some backend work to do still to support redirect's for deep linking back to an app on mobile devices. Will reopen or create a new issue if needed.


:package: Chore: Extract cache into it's own package

Description
Extract cache into it's own package so it's easily sharable across all bundler and builds as it's own build target that is unlikely to need to change
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 #776   👈

This stack of pull requests is managed by Graphite.


Additional logging of account change operations

We have a case where someone demoted the role of an administrator to a manager without approval. It would be useful to have information about which admin performed the operation.
Also, I have concerns about usage<EMAIL_ADDRESS>user on production (cloud) IPTs. I think we should use our dedicated accounts instead, otherwise it's unclear who is behind<EMAIL_ADDRESS>Any thoughts @gbif/dataproducts @MattBlissett

Yes, I agree that if we want to track changes, we should using individual admin accounts


Config Profile for HoloLens 1

Overview
By default the MRTK config profile assumes articulated hand input using HoloLens 2 style hand rays + direct interaction, however many people using MRTK are still deploying to HoloLens 1. People often ask how they can simulate HoloLens 1 style interactions in the Unity Editor.
People building and deploying HoloLens 1 apps can use this configuration in their MRTK.
This change adds an MRTK profile that people can use to simulate HoloLens 1 style GGV interactions.
Fixes: #5046
Changes

New profile to simulate HoloLens 1 interations.
Profile uses "gesture hand" for input simulation, not the articulated hand
Set Camera Clipping plane for HoloLens 1 to 0.3 per comfort guidelines at https://docs.microsoft.com/en-us/windows/mixed-reality/comfort

Profile lgtm.
Consider adding notes to this doc as well to explain the differences to consumers:
https://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/Profiles/Profiles.html#hololens-2-profile
i.e. add a "hololens 1 profile" section
I don't believe that people will all find it, but when people ask, it is important for us to be able to point to an answer and help build up a culture of doing a search on the docs.

/azp run

/azp run mrtk_pr

/azp run mrtk_pr

/azp run mrtk_pr

/azp run

So, I have no idea why this is failing the build on mrtk_pr, and why it seems to only be this particular change.
I tried pulling this locally as well and running this in batch mode and it works just fine - I'm trying to retarget to the stabillization branch and trying again.
The worst part is that the tests named "sanity tests" are failing


Use docker mirror with container.d

Hello,
I'm trying to use docker registry mirror with :
Containerd v1.16.1-k3s.1
K3S v1.16.3-k3s.2
I've modified file /var/lib/rancher/k3s/agent/etc/containerd/config.toml.tmpl on each node :
[plugins.opt]

  path = "/var/lib/rancher/k3s/agent/containerd"

[plugins.cri]
  stream_server_address = "<IP_ADDRESS>"
  stream_server_port = "10010"
[plugins.cri.cni]
  bin_dir = "/var/lib/rancher/k3s/data/2492a28b74abfbdbd3f943c8109a93e979669647bbbe95eadae43b60c667df69/bin"
  conf_dir = "/var/lib/rancher/k3s/agent/etc/cni/net.d"
[plugins.cri.containerd.runtimes.runc]
  runtime_type = "io.containerd.runc.v2"
[plugins.cri.registry]
  [plugins.cri.registry.mirrors]
    [plugins.cri.registry.mirrors."docker.io"]
      endpoint = ["https://mirror.gcr.io"]

After reboot, I check with crictl info all is good :
...
"cni": {
      "binDir": "/var/lib/rancher/k3s/data/2492a28b74abfbdbd3f943c8109a93e979669647bbbe95eadae43b60c667df69/bin",
      "confDir": "/var/lib/rancher/k3s/agent/etc/cni/net.d",
      "maxConfNum": 1,
      "confTemplate": ""
    },
    "registry": {
      "mirrors": {
        "docker.io": {
          "endpoint": [
            "https://mirror.gcr.io",
            "https://registry-1.docker.io"
          ]
        }
      },
      "configs": null,
      "auths": null
    },
    "disableTCPService": true,
    "streamServerAddress": "<IP_ADDRESS>",
    "streamServerPort": "10010",
...

But when I try to pull image it seems container.d always use registry-1.docker.io because when I shut down network I can see :
pulling image failed: rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/rancher/local-path-provisioner:v0.0.11": failed to resolve reference "docker.io/rancher/local-path-provisioner:v0.0.11": failed to do request: Head https://registry-1.docker.io/v2/rancher/local-path-provisioner/manifests/v0.0.11: dial tcp <IP_ADDRESS>:443: i/o timeout
Does anyone know why I'm having this error ?

I am too trying to set up a mirror with k3s and containerd but running into simulair issues, it doesn't appear to be taking my values.
https://rancher.com/docs/k3s/latest/en/installation/private-registry/#mirrors
/etc/rancher/k3s/registries.yaml
mirrors:
  docker.io:
    endpoint:
      - "http://<IP_ADDRESS>:5000"

However whenever I pull a new image, there's no logs in my registry. When I try it locally with Docker I see the image pulling pulled in the registry logs.

Did you put that file on all of your nodes? What message did you get when pulling the image that indicates that it's not using the mirror?

I only put it on the one node and tried pulling on that node specifically, which should yield the results I am looking for... I didn't see any errors in the /var/lib/rancher/k3s/agent/containerd/containerd.log logs, or anything relating.

For the next person that comes to the thread looking for HTTP image mirroring, looks like it is an issue upstream and will be fixed in containerd 1.4.0
https://github.com/containerd/cri/issues/1433

Common mistake. You have specified an endpoint for docker.io but are trying to explicitly pull from <IP_ADDRESS>:5000. If you want to be able to pull from it explicitly, you need to configure another mirror entry for that registry.

@brandond I am trying to set up a pull-through cache for my cluster using docker registry. I've spent a couple hours with different configurations, restarting agents, redeploying docker registry and nothing seems to be working. I cannot get k3s to use my cache even though it works perfectly on my macbook using docker.

If you want to pull through for docker.io then don't put your local registry URI in the name. Leave the registry unspecified or specify docker.io.

I've tried that already as I mentioned in my comment https://github.com/rancher/k3s/issues/1210#issuecomment-656347828
If I pull from docker.io using that config, the cache doesn't get populated, no errors, no logs as to why...

The OP was on a much older release of k3s. Since you jumped on an existing issue I don't have any info on which specific version you're using, or how your environment is configured - but this has worked for me and many other people, so if you're on a recent version of k3s I suspect the issue is either your configuration, or how you're testing it.

You could try the following, which should let you both pull directly from your registry, and have that same registry used in place of docker.io:
mirrors:
  docker.io:
    endpoint:
      - "http://<IP_ADDRESS>:5000"
  <IP_ADDRESS>:5000:
    endpoint:
      - "http://<IP_ADDRESS>:5000"

@bradtopol I finally got back to this. I tried what you mentioned above and I still cannot get containerd to use my docker registry as a pull thru cache.


FRI+ECFFT

FRI is an interactive oracle proof of proximity for polynomials to assess probabilistically (in a logarithmic-in-the-degree number of rounds) if a function, provided as an oracle, is a low degree polynomial. It leverages the same structure than the FFT, that is it works on a sequence of finite algebraic groups, with associated rational maps (which can be the identity, as in the multiplicative FFT), linked together by surjective maps with given kernel. As the ECFFT is used to mimic the FFT in an arbitrary finite field, the ECFFT technique can be used to implement FRI on an arbitrary finite field. The ECFFT allows to do fast polynomials operations (like division) on an arbitrary finite field. However, when working on arbitrary finite fields, one lacks an efficient polynomial commitment scheme. With FRI+ECFFT, this gap is filled because FRI can be transposed on arbitrary finite fields. It would allow PLONK to work on an arbitrary finite field.

https://eccc.weizmann.ac.il/report/2022/110/


Question: What is the reason for building the an S3 bucket for each region

Dear Folks,
I have a question regarding the following Terraform resources:
resource "aws_s3_bucket" "AHA-S3Bucket-PrimaryRegion" {
    count      = "${var.ExcludeAccountIDs != "" ? 1 : 0}"
    bucket     = "aha-bucket-${var.aha_primary_region}-${random_string.resource_code.result}"
    tags = {
      Name        = "aha-bucket"
    }
}

resource "aws_s3_bucket" "AHA-S3Bucket-SecondaryRegion" {
    count      = "${var.aha_secondary_region != "" && var.ExcludeAccountIDs != "" ? 1 : 0}"
    provider   = aws.secondary_region
    bucket     = "aha-bucket-${var.aha_secondary_region}-${random_string.resource_code.result}"
    tags = {
      Name        = "aha-bucket"
    }
}

I was not able to figure out what they are used for.
I think they are used for a CSV file holding data about excluded accounts if so I do not see a reason to create these buckets if I were just to pass the excluded accounts as a list in Terraform that is interpreted in python as a string and parsed.
If someone could tell me what these buckets are used for that would be great.
Many thanks.

For the Terraform deployment, yes those buckets hold the object/file for ExcludeAccountIDs.
https://github.com/aws-samples/aws-health-aware/blob/cfb786368b6dd7b8b1a9c03fb03ba1dff9ba811a/terraform/Terraform_DEPLOY_AHA/Terraform_DEPLOY_AHA.tf#L231


.net 6 polymorphic json converter article mentions stack overflow and links to something unrelated

https://learn.microsoft.com/en-us/dotnet/standard/serialization/system-text-json/converters-how-to?pivots=dotnet-6-0#an-alternative-way-to-do-polymorphic-deserialization states:

A disadvantage of this method is you can't pass in the original options instance that registers the converter to Deserialize.  The following example shows a Read method that uses this alternative:

yet the linked article does not explain this.

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

ID: 5de37d79-751f-e372-e866-efde28f4908c
Version Independent ID: 678c4f23-764a-7ccd-0d6d-159a30957477
Content: How to write custom converters for JSON serialization - .NET
Content Source: docs/standard/serialization/system-text-json/converters-how-to.md
Product: dotnet-fundamentals
GitHub Login: @gewarren
Microsoft Alias: gewarren

Thanks @bbarry, this is due to some versioned content, so I've fixed the link.


React Parity: Components & Context

For me this is the last question that is hanging on me so I'm looking for feedback suggestions. I've implemented JSX Fragments, control flow with fallbacks, Portals, and Suspense. I've had a lot of fun solving similar problems to React but in completely different ways that are Web Component friendly and work with Fine Grained performance considerations. I feel now, most typical cases are covered and you can do some pretty amazing things.
But ultimately, a library like Solid does not need Components to work, and in so upper case Function Components are essentially just Function templates. There are no context boundaries, no internalized state etc. This is definitely the biggest departure for those familiar with React.
Components vs Templates
If you want to pass state variables to these templates you need to essentially pass the whole state object or wrap in function accessors to get fine grained resolution.
const Child = ({ getName }) => (

{( getName() )}

);

const App = () => {
  const [state, setState] = createState({ name: 'John' });
  return <Child getName={() => state.name} />
}

With WebComponents this isn't a problem since children will be bound as DOM elements:
const App = () => {
  const [state, setState] = createState({ name: 'John' });
  return <child-elem name={( state.name )} />
}

Where does that leave us? I can simplify binding syntax to use the similar approach to auto wrap but the child template still is dealing with a function. I can always wrap all props in a state variable and create computations based on the binding to update that state behind the scenes. But the overhead of doing the same on simple Function components seems awkward. I'm not sure I like creating these arbitrary Component boundaries as it sidesteps the power of a library like Solid. That the UI or Code modularity considerations are independent of your ability to optimally manage data flow.
Dependency Injection
Solid Components has a Context API but Solid does not. The context in Solid is the computation or Root context which is not tied to a specific DOM node necessarily. While this can work like a typical framework like React it wouldn't play nice with Web Components. So it makes sense to tie context to elements but Solid Template Functions are independent of those boundaries.
It goes further than this as I can use control flow to inject context providers fairly easily but the reading(consumer) gets much more complicated as the current executing code, which is independent of it's place in the hierarchy, needs to know it's got the right context. The only constant is its owning context or the Elements being rendered at that scope of templating. What ultimately comes down to is that Fine Grained regardless of how nested the tree, flattens the problem. This is something I used to my advantage in Sierpinski Triangle Demo to show really controlled finite Asynchronous rendering to provide ultimate control and performance, but it bites us here pretty hard.
There are other ways to solve DI like import global registries as a variation on the Singleton where Dependencies are constructed and registered.  This method is just as controllable for testing and is in the majority effectively the same as using hierarchical look up but it is definitely not as nice. I can fake it behind a lovely API that makes it looks just like React and no one would be the wiser, well until they tried to nest contexts of the same type in multi levels of the tree.
I think I'm just not as familiar with what Angular or other non-React libraries do here so I'm hoping investigation lends to a good option.
Debugging
I'm fairly happy with Debugging since the compiled code hides the complications of triggers but exposes the direct imperative DOM operations and node creation, so by dropping breakpoints right in your implementation code you can very transparently see what is going on. Much more so than with a Virtual DOM or earlier non-compiled Fine Grained libraries. However, working around those restrictions I feel VDOM libraries have come up with really clever ways to improve the debugging experience. Even through browser tooling. I'd love to know what sort of debugging experience elements you really like from your experience or anything you would like to see with Solid. I played with the idea of Chrome Extension but mapping mapping the Real Dom back to Components or Context didn't feel very useful. It's possible visualization like Cycle.js/RxJS is the better option here. This is an area that earlier Fine Grained predecessors have been pretty poor in tooling.

In any case any thoughts on these topics would be much appreciated. I feel these are the final pieces to really solidify (excuse the pun) what the 1.0.0 release would look like.

A solution like this could work for components and context. It would be easy for the compiler to split {( )} dynamic expressions off and wrap them in a function, and change from calling Function components directly to creating them with createComponent. Skipping the the extra proxy wrap when there aren't any dynamic properties would be trivial. But it wouldn't cleanly support spread operators for dynamic data.
In one sense this might all be unnecessary. In another case maybe this is the missing piece.
let currentContext = {};
export function createContext(initFn) {
  return { id: Symbol('context'), initFn };
}

export function createProvider(context, value) {
  return currentContext[context.id] = context.initFn ? context.initFn(value) : value;
}

function lookupContext(current, key) {
  return current[key] || (current.parent && lookupContext(current.parent, key));
}
export function useContext (context) { return lookupContext(currentContext, context.id); }

function wrapContext(fn) {
  currentContext = {parent: currentContext};
  const ret = fn();
  currentContext = currentContext.parent;
  return ret;
}

function wrapProps(props, dynamicProps) {
  return new Proxy(props, {
    get(target, property) {
      let value;
      if (value = dynamicProps[property]) return value();
      return target[property];
    }
  });
}

function createComponent(fn, props, dynamicProps) {
  dynamicProps && (props = wrapProps(props, dynamicProps))
  return wrapContext(() => fn(props));
}

I suppose I could wrap every prop in a function. It would still require consideration for HyperScript but it would be consistent and I could have the compiler handle the spread operator better. Although I question the value of the spread operator in this scenario since it isn't really dynamic on Components (only the keys present on original run will be dynamic).
function wrapProps(props) {
  return new Proxy(props, {
    get(target, property) {
      let value;
      if (value = target[property]) return value();
    }
  });
}

function createComponent(fn, props) {
  return wrapContext(() => fn(wrapProps(props)));
}

So,
const view = <Comp name={ state.name } handleClick={ clickHandler } />

// compiles to
const view = createComponent(Comp, { name: () => state.name, handleClick: () => clickHandler, children: [] })

//used like
const Comp = props =>
{( props.name )}

I guess the caveat in both of these approaches is destructuring props would be a no go for anything dynamic since the getter triggers on property access. So again questioning if the Proxy magic is truly transparent in this scenario. I think in many ways this approach is more inline of what my thinking would be first seeing the library, but I'd also immediately fall into trying to destructure and having it not dynamically update (event handlers etc, would work fine).

What about React Native?

What about React Native?

That's a fair question. The state part of the library is React compatible(react-solid-state) to potentially work with React Native (I'm currently investigating). The renderer as presented here is not.
While the state management solution benchmarks favourable against something like MobX, the majority of Solid's performance comes from a completely different approach to rendering (that can also benefit MobX too). While I've tentatively looked at things like Native Script and see some potential there, I think it is going to be a much bigger undertaking since the approach to rendering is significantly different than most other solutions that have JS/native bridge API's. On the plus the way I've approached this stuff, if I find a solution it would benefit more than this library but take these techniques to potentially allow libraries like MobX to work without React or any sort of fine grained library (like Knockout) have a mobile solution.
For now I think PWA's and Web Components is probably the tact this library will take for mobile in the near term given my limited resources as largely a single contributor. While the Web rendering has really good performance, I feel I still am going to focus on improving it over the next several months. And investigating how I can continue to improve web component development experience.

Back on task, the more I think about it the more I like the idea I posted above in https://github.com/ryansolid/solid/issues/18#issuecomment-478050373. Basically at any point you can always just call a function so I think people coming from a React perspective will expect JSX tag Components to be contextual (have context).
What I mean the overhead is completely opt in. If you didn't want to create these components could always still just use a Function call:
const Child = ({ getName }) => (

{( getName() )}

);

const App = () => {
  const [state, setState] = createState({ name: 'John' });
  return Child({getName: () => state.name});
}

I think the fact that functions are just Templates can still be powerful without using JSX Component syntax. You can wrap these calls in expressions in other Elements or Fragments so it's just as flexible just not as clean. But this allows for having Components as well which lets you:
const Child = props => (

{( props.name )}

);

const App = () => {
  const [state, setState] = createState({ name: 'John' });
  return <Child name={state.name} />
}

As well as support a React like Context API. I think this is what I'd expect as a new Developer.
This is a potential breaking change for all the libraries that depend on the Babel Plugin so I need to spend some time with it. Other consideration is the role of HOCs. It's pretty trivial to compose plain functions. While the same is true for these Components there is a real overhead (multi depth Proxies). I might need to expose access into setters in the Proxy so that except for the outer call we can use simple function composition and only take the Component overhead once for all layers of Mixin. Sure with Hook like interface less of a concern but I need to spend some time working through these patterns as well before I can settle on this decision.

So I started implementing solutions and I noticed a couple things. I wanted to update this thread. Where I'm sitting right now this likely what I'm implementing at this time.
Components
I looked where I was using spreads mostly were to pass down handler functions. The thing is spreading over state is anti-pattern. Observable objects trigger based on property access so it is always a ton of work to wrap and unwrap. It makes more sense to pass the whole state object. Similarly as soon as you to pick out certain properties you aren't spreading. So largely I'm leaving spreads out of consideration. At that point it's easy to indicate which properties need to be wrapped. We can follow the same convention as native elements {( )}. It's consistent and it is completely opt in. By setting wrapped keys explicitly I can use getter instead of proxy which keeps backward compatibility for non es6 platforms. There is no weirdness around wrapping unnecessary fields. Largely these Components just remain a function call. There is no overhead or performance hit if you don't use the feature. Basically this becomes non-breaking change.
const Child = props => (

{( props.name )}

);

const App = () => {
  const [state, setState] = createState({ name: 'John' }),
    clickHandler=() => console.log('Clicked');
  return <Child name={( state.name )} handleClick={ clickHandler } />
}

Mostly I think extends the mentality of Solid and how it differs from Surplus. In Surplus everything is generally live and each new context creates a layer in reactive tree. Every piece automatically updates and fallsback to higher context. Even if you make a mistake things will update. This is the common mentality in fine grained libraries. If you wire it will update.
Solid on the otherhand is mostly inert. Changes are whitelisted. You need to indicate if you want things to update. This means things may not update when mistakes are made but it is less likely things will update unexpectedly. Admittedly there are still contexts that can cause unexpected updates, but wherever there are library means Solid will attempt to keep updates contained.
Dependency Injection
I finally figured out exactly why this is so hard to do. By that I mean Hierarchical Container DI as found in React and Angular. It is easy to use other patterns. Single global DI, or Service Locator pattern is fairly straightforward. But not worth making part of this library.
There are 2 solutions to Hierarchical DI in Solid as far as I can tell. Approach 1 is using the reactive graph. With a simple modification to S.js I can backtrace up Owner contexts. This is probably on the surface the most reasonable approach if it weren't for asynchronous side effects. And maybe I'm worrying about stuff too much but I hit this issue immediately trying this approach. Appending a Web Component to the page on a polyfilled environment is scheduled on microtask instead of synchronously. I also hit this with a router doing async imports. I like how easy it is to do async rendering in Solid. Having a solution not work nicely with it is too restrictive. There may be library supported features to manage these tasks in the future but it seems like I'd have trouble accounting for every scenario.
Approach 2 is building up a node tree. Components do this as they construct the Virtual DOM and in a sense we do the same with the real DOM. However the lack of lifecycles bite us here. See React always re-renders the tree so it knows it's parents as it goes even on updates. Web Components do most of their work in the ConnectedCallback meaning the root is already connected to the DOM. A Solid Template fragment has no idea what it is going to be inserted to, so it basically goes down the tree building and only attaches it as it goes back up. Meaning on initial construction I can't easily pull the data from DOM nodes going up the tree (fragment support doesn't make this any easier). Without messing up with timing of the templates or inserting more unnecessary elements I don't see this working.
For now I think I need to leave this in the domain of 3rd party libraries or the Solid Components solution.

Spreads
While I didn't have many use cases since I've been building for performance spreads, transparent prop passing for HOCs is a thing. For that reason I need to support dynamic (wrapped) spreads. I realized that I can use the same wrapping Parenthesis trick to inform the compiler. For example:
const MyHOC = Child => props => {
    // Do some logic .....
    return <Child {...(props)} addedProp={(state.data)} />
}

To be consistent I think all Spreads should be static first render only unless they are wrapped in parens for both Components and native elements. Essentially:
const view =

forwardRef
This one is a little tricky since all Components return is their rendered DOM elements. I'm thinking of piggybacking an element reference on the returned element under a special key. The only downside of this approach besides some complication in compilation is it would be only applicable on first render and not under dynamic updates since the parent context would only be reading off the reference once. So if the ref inside the Component was in a node in a conditional causing that node to not render on initial render it would never forward the ref properly.
The solution could be to change how Refs work.  If refs were identity functions or specialized objects like React we could dynamically update them. The thing is outside of the forward ref scenario there is no reason to do anything so fancy with refs. At that point you are just passing props in essentially that keep their reference. Using either a function or an object to have a key set on is the same deal. The only benefit of making this a thing, is for consistencies sake.
I mean I could hide these details with the compiler by

Always compiling refs on Components to functions with assignment
Reserving a forwardRef prop to call said function with reference

const Child = props =>

const Parent = () => {
  let ref;
  return <Child ref={ref} />
}

// Becomes
const Child = props => {
  const $el = $tmpl.content.firstChild.cloneNode(true);
  props.ref($el);
  return $el;
}

const Parent = () => {
  let ref;
  return Child({ ref: r$ => ref = r$ })
}

The benefit is the end user never thinks of this more than a simple assignment and there is no specialized object you have to worry about. The HyperScript version already handles all refs with functions anyway so this would keep consistent-ish for those solutions (they wouldn't need forwardRef).

I think this thread has served it's purpose or as much as it can given my long monologue. In the future I will move ideas and discussions like this mostly in the community chat under https://spectrum.chat/solid-js/features


ErrorException (E_NOTICE) Undefined variable: content

ErrorException (E_NOTICE)
Undefined variable: content
\vendor\tcg\voyager\src\Controllers\VoyagerBreadController.php
Line 323
I'm use image field and file field, Please help me.

File field isn't implemented yet for now

.

I'm add this functional, but it's not safe.
Please, developers this package, fix it's in next version
https://www.snip2code.com/Snippet/1525077/add-functional-to-file-types

and if add new table through admin panel, column ID need add auto_increment functionality

Haven't this already been fixed?


Quaternions are used incorrectly

Is your design request related to a problem? Please describe.
The current implementation of parenting only uses euler angles that get converted to quaternions and then to matrices. This is correct, but doesn't make any sense. It would be better to convert "all" matrices to quaternions; reducing the memory/bandwidth cost and increasing performance.
Describe the solution you'd like
Only use matrices when needed (like clip space conversions) and use quaternions otherwise.
Describe alternatives you've considered
Matrices can still be used, but will result into rotations being less accurate and potential rendering issues.
Additional context
N.A.

Currently we also have a used_quaternion boolean. This is quite a bad way to handle quaternions. Requires a better version in the future.


Problem with shortcut remapper

Hello.
Since the new 0.19 update I started having problems with shortcuts - at least with alt+t and alt+w. I have them remapped to ctrl+t and ctrl+w respectively and:

shortcuts would sometimes work after clicking them two times
they would trigger default (alt+t, alt+w) effect instead of remapped one (ctrl+t, ctrl+w).

Environment:
Windows build number: Microsoft Windows [Version 10.0.18363.900]
PowerToys version: 0.19.0
PowerToy module: Keyboard manager
Steps to reproduce:

remap shortcut alt+t to ctrl+t and alt+w to ctrl+w
open any web browser with ctrl+t/ctrl+w shortcuts to open/close tab
install LastPass extension (not sure if needed but alt+w shortcut is used by it)
try clicking alt+t, alt+t, alt+w fast

Expected behavior:
Opening new tab, opening new tab, closing a tab...
Actual behavior:
Sometimes opening a tab, sometimes not, sometimes closing a tab, sometimes triggering default alt+w shortcut, general bugginess.
After downgrading to 0.18.2 everything works as expected.

@istir I think this is the same issue reported at #4647. Can you confirm that you're facing the issue only when it's two shortcuts that are remapped and both have the same modifier (like Alt+t and Alt+w, or Win+t and Win+w)? If so this will be fixed in 0.19.1.

Sorry for not reaching out earlier, seems to be fixed now as of 0.19.1.


Max File size too small

Need an environment variable to set max file size.
What is the current limit?
It's currently too small to support 24 minutes of audio, even with flac level 8 compression.

I've added two variables UPLOAD_FILE_SIZE_LIMIT (size in MB) and YOUTUBE_LENGTH_LIMIT (length in minutes) to be able to configure upload limits in https://github.com/JeffreyCA/spleeter-web/commit/00993e9556dac8b2198a40d7d0812b75d71a8bcf.


XFCE4 Lock screen

Please describe the issue in as much detail as possible, including any errors and traces
I'm running XFCE4 on Arch using GDM as the display manger, it works perfectly there, and when I sign into gnome it works flawlessly.  However in an XFCE session the lock screen doesn't respect the pam settings.  Every other kind of authentication does (ex: sudo, gsudo, ect ect..) does just not the lock screen.  I've added the line for howdey in all the lightdm pam files as well as the xfce4 screensaver pam file, and I'm not sure where else I can look for settings.
Thank you
I've searched for similar issues already, and my issue has not been reported yet.
Linux distribution (if applicable): Arch Linux
Howdy version: Unsure, might be a version or two behind.

I have the same issue in xfce4 over xubuntu 20.04.
The /var/log/auth.log show that:
Jun 20 18:03:30 phoenix /lib/security/howdy/pam.py[5576]: Traceback (most recent call last):
Jun 20 18:03:30 phoenix /lib/security/howdy/pam.py[5576]:   File "/lib/security/howdy/pam.py", line 68, in pam_sm_authenticate
Jun 20 18:03:30 phoenix /lib/security/howdy/pam.py[5576]:     return doAuth(pamh)
Jun 20 18:03:30 phoenix /lib/security/howdy/pam.py[5576]:   File "/lib/security/howdy/pam.py", line 62, in doAuth
Jun 20 18:03:30 phoenix /lib/security/howdy/pam.py[5576]:     pamh.conversation(pamh.Message(pamh.PAM_ERROR_MSG, "Unknown error: " + str(status)))
Jun 20 18:03:30 phoenix /lib/security/howdy/pam.py[5576]: PamException: Error de conversación
Jun 20 18:03:30 phoenix xfce4-screensaver-dialog[5576]: pam_unix(xfce4-screensaver:auth): Couldn't open /etc/securetty: No existe el archivo o el directorio
Jun 20 18:03:30 phoenix xfce4-screensaver-dialog[5619]: pam_unix(xfce4-screensaver:auth): Couldn't open /etc/securetty: No existe el archivo o el directorio
Jun 20 18:03:34 phoenix xfce4-screensaver-dialog[5652]: pam_unix(xfce4-screensaver:auth): Couldn't open /etc/securetty: No existe el archivo o el directorio

Seeing the same on Ubuntu Budgie 20.04
Aug 30 08:30:14 amdi-bud /lib/security/howdy/pam.py[15473]: Traceback (most recent call last):
Aug 30 08:30:14 amdi-bud /lib/security/howdy/pam.py[15473]:   File "/lib/security/howdy/pam.py", line 84, in pam_sm_authenticate
Aug 30 08:30:14 amdi-bud /lib/security/howdy/pam.py[15473]:     return doAuth(pamh)
Aug 30 08:30:14 amdi-bud /lib/security/howdy/pam.py[15473]:   File "/lib/security/howdy/pam.py", line 77, in doAuth
Aug 30 08:30:14 amdi-bud /lib/security/howdy/pam.py[15473]:     pamh.conversation(pamh.Message(pamh.PAM_ERROR_MSG, "Unknown error: " + str(status)))
Aug 30 08:30:14 amdi-bud /lib/security/howdy/pam.py[15473]: PamException: Konversationsfejl
Aug 30 08:30:14 amdi-bud gnome-screensaver-dialog[15473]: pam_unix(gnome-screensaver:auth): Couldn't open /etc/securetty: Ingen sådan fil eller filkatalog
Aug 30 08:30:14 amdi-bud gnome-screensaver-dialog[15485]: pam_unix(gnome-screensaver:auth): Couldn't open /etc/securetty: Ingen sådan fil eller filkatalog
Aug 30 08:30:18 amdi-bud gnome-screensaver-dialog[15488]: pam_unix(gnome-screensaver:auth): Couldn't open /etc/securetty: Ingen sådan fil eller filkatalog
A

Same on cinnamon-screensaver. Commenting out all "pamh.conversation" lines fixes this.

Same on arch+lightdm+xfce4. Howdy works on lightdm, but not on xflock.


Build partest coverage check into partest runner

Hum, IIUC, we are losing one functionality here: the fact that check-partest-coverage.sh was not only testing that every actual test is known, but also that we don't "know" a test that does not, in fact, exist.

Also: what's the motivation for this change?

Hum, IIUC, we are losing one functionality here: the fact that check-partest-coverage.sh was not only testing that every actual test is known, but also that we don't "know" a test that does not, in fact, exist.

Ah, indeed.

Also: what's the motivation for this change?

Less code, less logic duplication (where is what).
But fair enough, maybe its not worth it.


DSA solver webpages(solve issue #922)

🛠 Issue (#922 )

Closes #922
Description
I Had Made a DSA Solver WEBpages using html , css , js.
Type of change

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

Checklist:

[x] I have made this from my own
[x] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] The title of my pull request is a short description of the requested changes.

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

Please Check The updated Branch is correct or Not.i had Solve The issue(#922)

update the branch

@zugzwang03 what would be the branch name

@zugzwang03 what types of Changes i have to made.

you have to make your branch up to date, that is in sync with the present repo version.

Okk

@zugzwang03 I had Make Every-thing update but still.showing behind

it Still doesn't show uptodate

@zugzwang03 Please merge this issue.i had updated my branch

there is some issue with the deployment

did you add your project to the cards?

I don't know about any project card please help me.


Add devcontainer

Add a devcontainer that spins up a local MQTT server for testing purposes. I got this mostly working but F5 doesn't launch for some reason.

Closing old issues.


[FLINK-5669] Change DataStreamUtils to use the loopback address (<IP_ADDRESS>)

For local environments, using loopback rather than the "local address" allows tests to run in
situations where the local machine's hostname may not be resolvable in DNS
(because DNS is unreachable or the hostname is not found) or the hostname does
resolve, but not to an IP address that is reachable.
Thanks for contributing to Apache Flink. Before you open your pull request, please take the following check list into consideration.
If your changes take all of the items into account, feel free to open your pull request. For more information and/or questions please refer to the How To Contribute guide.
In addition to going through the list, please provide a meaningful description of your changes.

[x] General

The pull request references the related JIRA issue ("[FLINK-XXX] Jira title text")
The pull request addresses only one issue
Each commit in the PR has a meaningful commit message (including the JIRA id)

[x] Documentation

Documentation has been added for new functionality
Old documentation affected by the pull request has been updated
JavaDoc for public methods has been added

[x] Tests & Build

Functionality added by the pull request is covered by tests
mvn clean verify has been executed successfully locally or a Travis build has passed

The change basically renders the utility unusable, other than for local execution...

Thanks for taking a look. Could you explain more? The modified code is in the else branch of if (env instanceof RemoteStreamEnvironment), so my assumption was that it only needed to work for local execution. (And that it wouldn't have worked if used with remote execution before, because it just selects the IP returned by DNS, which is often not the IP that a remote taskmanager would need to use to reach the client --- hence the use of ConnectionUtils.findConnectingAddress in the remote case.)

Sorry for answering so brief before.
The branch you changed is executed for all non-remote environments. Those are the local environments, but also the "context environments", which are used when you submit a job via the command line to a standalone/yarn/mesos cluster.
You can probably make a change to check explicitly whether the environment is a local environment, and use the loopback address only then, and keep the local host in the other cases.

Thanks for the detailed explanation. I confirmed that using the previous patch with a standalone cluster failed, then applied the suggested alternative approach and tested that works with both standalone and local (online and offline). (I don't have ready access to Yarn or Mesos clusters, but believe they should be fine since this version only affects LocalStreamEnvironments).

This change looks good, thank you!
Merging this...


libmariadb:x64-windows failed with: BUILD_FAILED

I got this problem when I install libmariadb;
already download the last version of vcpkg;
I also readed the closed issues,and try them;
the problem still happened,the 10043.patch ,fix branch(not exist anymore);
I also regit all vcpkg;but it does not work on my computer
thoes were the procedure：
The following packages will be built and installed:
    libmariadb[core,openssl,zlib]:x64-windows -> 3.1.10#5
Detecting compiler hash for triplet x64-windows...
Could not locate cached archive: C:\Users\Administrator\AppData\Local\vcpkg\archives\c5\c55f538c5644330238ea71dc567194bb567a6c4b.zip
Starting package 1/1: libmariadb:x64-windows
Building package libmariadb[core,openssl,zlib]:x64-windows...
-- Using cached E:/vcpkg/vcpkg/downloads/MariaDB-mariadb-connector-c-159540fe8c8f30b281748fe8a1b79e8b17993a67.tar.gz
-- Cleaning sources at E:/vcpkg/vcpkg/buildtrees/libmariadb/src/8b17993a67-4af4dbafde.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source E:/vcpkg/vcpkg/downloads/MariaDB-mariadb-connector-c-159540fe8c8f30b281748fe8a1b79e8b17993a67.tar.gz
-- Applying patch arm64.patch
-- Applying patch md.patch
-- Applying patch disable-test-build.patch
-- Applying patch fix-InstallPath.patch
-- Applying patch fix-iconv.patch
-- Applying patch export-cmake-targets.patch
-- Using source at E:/vcpkg/vcpkg/buildtrees/libmariadb/src/8b17993a67-4af4dbafde.clean
CMake Deprecation Warning at scripts/cmake/vcpkg_check_features.cmake:182 (message):
  calling `vcpkg_check_features` without the `FEATURES` keyword has been
  deprecated.

      Please add the `FEATURES` keyword to the call.
Call Stack (most recent call first):
  ports/libmariadb/portfile.cmake:20 (vcpkg_check_features)
  scripts/ports.cmake:142 (include)

-- Configuring x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:105 (message):
    Command failed: ninja -v
    Working Directory: E:/vcpkg/vcpkg/buildtrees/libmariadb/x64-windows-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
      E:\vcpkg\vcpkg\buildtrees\libmariadb\config-x64-windows-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_cmake.cmake:324 (vcpkg_execute_required_process)
  ports/libmariadb/portfile.cmake:31 (vcpkg_configure_cmake)
  scripts/ports.cmake:142 (include)

Error: Building package libmariadb:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: libmariadb:x64-windows
  Vcpkg version: 2021-01-13-d67989bce1043b98092ac45996a8230a059a2d7e

I found some error in libmariadb v3.1.10 in cmake/ConnectorName.cmake at line 25;
IF(CMAKE_SYSTEM_NAME MATCHES "Windows")
SET(PLATFORM_NAME "win")
SET(CONCAT_SIGN "")
IF(IS64)
SET(MACHINE_NAME "x64")
ELSE()
SET(MACHINE_NAME "32")
END()
ENDIF()
please update to v3.1.12 to fix this
the new url is
https://github.com/mariadb-corporation/mariadb-connector-c

@SGD9919 ,Thanks for posting this issue,
I can successfully install libmariadb:x64 triplet locally, I will upgrade the libmariadb version to 3.1.12, you can wait for the merge and reinstall

thankful

@SGD9919 ,Sounds great, I will update libmariadb to the latest version and link to this issue


correct the command to start the repl

The read says the REPL can be started with bin massive. But in linux (ubuntu 14.4) this doesn't work (I get a No command 'bin' found, did you mean: ...). Am I missing something?
However I successfully started the REPL in the normal way.

Meanwhile I found the bin entry in package.json. But as I wrote in the pr, the given instruction (bin massive) are not working in linux.
Shouldn't the bin entry be in the scripts property, along with test?


dose the leshan client support to connect with multiple server  concurrently？

hi，i want to know if the leshan client support to connect with multiple server concurrently?
thank you!

Currently it does not.
See :

https://github.com/eclipse/leshan/wiki/LWM2M-Supported-features#client-registration)
https://github.com/eclipse/leshan/issues/600

(can we close this issue ?)

yes, thanks a lot!


Integrate with nycma

Been chatting with Saje, and she can send us requests that they get for neighborhoods of our choosing.

#56 fixes this


build: don't include scope in dependabot commits

Description
I made an error when writing the config, the scope should not be included in the commit messages

no clue about dependabot -- was so far only annoying. good catch


Extension issue

Issue Type: Bug
Extension Name: html-css-class-completion
Extension Version: 1.20.0
OS Version: Windows_NT x64 10.0.19042
VSCode version: 1.54.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Seems to be already reported at #155


Move defaultSHMSize in daemon pkg

it shouldn't break anything and basically just moves DefaultSHMSize to daemon because it isn't used anywhere in runconfig but it's something the daemon applies if shmsize is nil (let's see if tests agree with me)
/cc @estesp @cpuguy83
Followup of: https://github.com/docker/docker/pull/18261#issuecomment-161027959
Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

Make sense to me.. LGTM

@cpuguy83 updated

LGTM pending janky.

Failings in userns/windows seem totally unrelated

Today is the day of mass rebases.

rebased

@estesp You still good with these changes?

yup, still LGTM


[Vue 2.7][vite] Can't use special characters in translation message

Reporting a bug?
I have a custom block with translations:
<i18n>
{
  "en": {
    "hello": "Use varible like this: {{UTC}}"
  }
}
</i18n>

I want it to be displayed as is. But I had an error from unplugin-vue-i18n: Not allowed nest placeholder. To display curly braces I tried using literal interpolation as suggested in the docs. And so I changed the translation  to:  "Use varible like this: {'{{'}UTC{'}}'}". But in the interface I see this message with symbols that are used to escape special characters (like curly braces in my case):

Expected behavior
I want the possibility to escape special characters
Reproduction
https://stackblitz.com/edit/vitejs-vite-masrj4?file=package.json,vite.config.ts,src%2Fmain.ts,src%2FApp.vue,src%2Fi18n.ts&terminal=dev
Issue Package
unplugin-vue-i18n
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
  npmPackages:
    vite: ^3.1.0 => 3.1.0
    vue: ^2.7.10 => 2.7.10
    vue-i18n: ^8.27.2 => 8.27.2

Screenshot
No response
Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the README
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.

Thank you for your reporting!
This is bug of vue-i18n message compiler.
so, We will move this issue to vue-i18n-next.


Introduce additional fold environment variables

We have received feedback from @darktears who created multiple demos as well as a cool library for dual-screens devices and well as @Crissov via this GitHub issue https://github.com/w3c/csswg-drafts/issues/4736 to add env(fold-right) and env(fold-bottom)
I am in favor of adding env(fold-right) and env(fold-bottom), this example illustrates the benefit:

before
[dir="ltr"] .col {
   flex: 0 0 env(fold-left);
}

[dir="rtl"] .col {
   flex: 0 0 calc( 100vw - ( env(fold-left) + env(fold-width) ) );
}

after
[dir="ltr"] .col {
   flex: 0 0 env(fold-left);
}

[dir="rtl"] .col {
   flex: 0 0 env(fold-right);
}

the latter is provides better ergonomics.

This looks much better :)

credits to @chris480 for originally sparking the conversation on RTL vs LTR here: https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/138

+1
fold-right is much better than having to calc it yourself

Not being too familiar with the full goals, considering this takes text direction into account, would something like the new margin logical properties make more sense? https://drafts.csswg.org/css-logical/#margin-properties

@RichiCoder1 great suggestion, there's an on-going discussion in this issue about that topic: https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/138