Move operator infrastructure from circleci to prow

(This is used to request new product features, please visit https://discuss.istio.io for questions on using Istio)
Describe the feature request
We are moving entirely to prow for all CI.
Describe alternatives you've considered
TOC has made a determination that going forward, all repos should use prow and only one CI system should be voting (that being prow rather than circleci).
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[X] Developer Infrastructure
Additional context

circleci lint -> prow - operator repo: https://github.com/istio/operator/pull/50

circleci lint -> prow - test-infra repo: https://github.com/istio/test-infra/pull/1380

test of mergify  and cleanup of prow lib: https://github.com/istio/operator/pull/82

make prow jobs non-optional now that manual branch protection settings are not in place: https://github.com/sdake/test-infra/pull/new/issue/15156-6

remove redundant circcleci jobs: https://github.com/istio/operator/pull/83

all wrapped up.  closing.


Added cors middleware to the api

Closes #83

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 91.575%

Totals

Change from base Build<PHONE_NUMBER>:
0.06%

Covered Lines:
250

Relevant Lines:
273

💛  - Coveralls


[Missing] Contacts filter from group/channel member list

Categorize group Members as Contacts/Bots/Administrators/Other Members

This is an interface feature. All needed chat members search filters (except contacts filter) are available for a very long time.

The filters supergroupMembersFilterContacts and chatMembersFilterContacts was added in TDLib 1.5.0. See Change Log for the full list of changes.


[keymgr] questions about LC disable

@tjaychen
I have a few questions about LC disabling keymgr

If the key manager has not been initialized, it cannot be initialized until life cycle enables key manager.

For this statement in the spec, keymgr can't be initialized is due to cfgen=0 if keymgr_en isn't On, right?

Once the system settles to Disabled state, the behavior is consistent with normal behavior.

This statement seems not precise. Since cfgen is 0 when keymgr_en isn't On, all operations will be ignored after the system settles to Disabled state. Is it worth adding the cfgen is set to 0 in the spec?
From below codes, if state is in Disabled and keymgr_en is set to off, we don't enter StCtrlWipe to wipe secret. In this case, sideload key will be valid unless SW generates another one to override it. SW_SHARE will be still available if SW doesn't read it to clear. Will it be a risk?
       StCtrlWipe: begin
        stage_sel_o = Disable;
        op_done_o = op_start_i & kmac_done_i;
        op_accepted = op_start_i;
        wipe_key_o = 1'b1;

        for (int i = 0; i < Shares; i++) begin
          key_state_d[i] = {EntropyRounds{entropy_i}};
        end

        if (!op_start_i) begin
          state_d = StCtrlDisabled;
        end
      end

      // Terminal state (StDisabled is included)
      // However, it will continue to kick off dummy transactions
      default: begin
        op_done_o = op_start_i & kmac_done_i;

        // accept any command, but always select fake data
        op_accepted = op_start_i;
        stage_sel_o = Disable;

        // During disabled state, continue to update state
        key_state_d = (op_done_o && advance_sel) ? kmac_data_i : key_state_q;

        invalid_op = op_start_i;
      end

@tjaychen
I have a few questions about LC disabling keymgr

If the key manager has not been initialized, it cannot be initialized until life cycle enables key manager.

For this statement in the spec, keymgr can't be initialized is due to cfgen=0 if keymgr_en isn't On, right?

yes that and the keymgr_ctrl fsm itself. If the enable is low, it also will not allow us to transition out of reset state.
So hopefully the protection is two-fold.

Once the system settles to Disabled state, the behavior is consistent with normal behavior.

This statement seems not precise. Since cfgen is 0 when keymgr_en isn't On, all operations will be ignored after the system settles to Disabled state. Is it worth adding the cfgen is set to 0 in the spec?

so to clarify, Disabled state and keymgr_en are kind of orthogonal.
Because it is possible for software to issue a transition into disable state also with keymgr_en high the entire time.
Does that make sense?

From below codes, if state is in Disabled and keymgr_en is set to off, we don't enter StCtrlWipe to wipe secret. In this case, sideload key will be valid unless SW generates another one to override it. SW_SHARE will be still available if SW doesn't read it to clear. Will it be a risk?

if we are already in Disabled, we are okay. There are 2 ways to transition to diasabled.

software directly issues a command -> in this case, it is up to software whether it wants to wipe the sideload keys
keymgr_en went low after being high.  In this case, we go through and wipe, and everything is gone.

Does this help? Maybe I can make this clearer in the spec.

       StCtrlWipe: begin
        stage_sel_o = Disable;
        op_done_o = op_start_i & kmac_done_i;
        op_accepted = op_start_i;
        wipe_key_o = 1'b1;

        for (int i = 0; i < Shares; i++) begin
          key_state_d[i] = {EntropyRounds{entropy_i}};
        end

        if (!op_start_i) begin
          state_d = StCtrlDisabled;
        end
      end

      // Terminal state (StDisabled is included)
      // However, it will continue to kick off dummy transactions
      default: begin
        op_done_o = op_start_i & kmac_done_i;

        // accept any command, but always select fake data
        op_accepted = op_start_i;
        stage_sel_o = Disable;

        // During disabled state, continue to update state
        key_state_d = (op_done_o && advance_sel) ? kmac_data_i : key_state_q;

        invalid_op = op_start_i;
      end

so to clarify, Disabled state and keymgr_en are kind of orthogonal.
Because it is possible for software to issue a transition into disable state also with keymgr_en high the entire time.
Does that make sense?

After enter disabled state, I will also test some operations.
However, if disabled state is entered by keymgr_en=Off, the behavior is not really consistent with being entered by SW. I feel the statement "Once the system settles to Disabled state, the behavior is consistent with normal behavior" may be a bit inaccurate. Perhaps we can mention keymgr_en=Off will set cfgen=0 in spec, so that we know any operation will be ignored.

if we are already in Disabled, we are okay. There are 2 ways to transition to diasabled.
software directly issues a command -> in this case, it is up to software whether it wants to wipe the sideload keys
keymgr_en went low after being high. In this case, we go through and wipe, and everything is gone.
Does this help? Maybe I can make this clearer in the spec.

I tried to test all secrets (hw key, sw_share_output) will be wiped if keymgr_en turns 0. Then I found this case:
SW enters disabled without clearing sideload key and sw_share_output, then keymgr_en turns low, sideload key and sw_share_output won't be wiped. In this case, we need SW manually wipe the secrets.
I'm also thinking a case. hackers may make SW enter Disabled state to bypass HW wipe secret logic, then try to steal HW sideload key.

so to clarify, Disabled state and keymgr_en are kind of orthogonal.
Because it is possible for software to issue a transition into disable state also with keymgr_en high the entire time.
Does that make sense?

After enter disabled state, I will also test some operations.
However, if disabled state is entered by keymgr_en=Off, the behavior is not really consistent with being entered by SW. I feel the statement "Once the system settles to Disabled state, the behavior is consistent with normal behavior" may be a bit inaccurate. Perhaps we can mention keymgr_en=Off will set cfgen=0 in spec, so that we know any operation will be ignored.

o i see what you're saying. Yes i can do that.  Let me explain that.

if we are already in Disabled, we are okay. There are 2 ways to transition to diasabled.
software directly issues a command -> in this case, it is up to software whether it wants to wipe the sideload keys
keymgr_en went low after being high. In this case, we go through and wipe, and everything is gone.
Does this help? Maybe I can make this clearer in the spec.

I tried to test all secrets (hw key, sw_share_output) will be wiped if keymgr_en turns 0. Then I found this case:
SW enters disabled without clearing sideload key and sw_share_output, then keymgr_en turns low, sideload key and sw_share_output won't be wiped. In this case, we need SW manually wipe the secrets.
I'm also thinking a case. hackers may make SW enter Disabled state to bypass HW wipe secret logic, then try to steal HW sideload key.

hmmmm... then if that's the concern we could separate Disabled from an actual invalid state.

thinking about this more, even if i'm not concerned about it, making the behavior more consistent will probably be easier for DV and future use.
So let's do this.. i'll create another state called StCtrlInvalid.  This will be the state we go to whenever keymgr_en goes low, even if we were in StCtrlDisabled.  To get to this new state, we must always go through a control wipe, but otherwise, its behavior will be identical to disabled.  How does that sound?
This should then make all the behavior consistent.

thinking about this more, even if i'm not concerned about it, making the behavior more consistent will probably be easier for DV and future use.
So let's do this.. i'll create another state called StCtrlInvalid. This will be the state we go to whenever keymgr_en goes low, even if we were in StCtrlDisabled. To get to this new state, we must always go through a control wipe, but otherwise, its behavior will be identical to disabled. How does that sound?
This should then make all the behavior consistent.

sounds good to me. It's certainly more consistent for DV. But do we need to change the operation Disable to Invalid too?

no, because i think it's worth having a state where we can't do anything
"new", but it preserves the last snapshot..until it's overridden.
It's not super usable IMO, but you never know.
On Mon, Dec 28, 2020 at 2:45 PM weicaiyang<EMAIL_ADDRESS>wrote:

thinking about this more, even if i'm not concerned about it, making the
behavior more consistent will probably be easier for DV and future use.
So let's do this.. i'll create another state called StCtrlInvalid. This
will be the state we go to whenever keymgr_en goes low, even if we were
in StCtrlDisabled. To get to this new state, we must always go through a
control wipe, but otherwise, its behavior will be identical to disabled.
How does that sound?
This should then make all the behavior consistent.
sounds good to me. It's certainly more consistent for DV. But do we need
to change the operation Disable to Invalid too?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/issues/4680#issuecomment-751886915,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSQFDKLOCMZF42ILTV3SXEDB3ANCNFSM4VMOBVPA
.

no, because i think it's worth having a state where we can't do anything "new", but it preserves the last snapshot..until it's overridden. It's not super usable IMO, but you never know.

I see. Sounds good.

addressed via #4755

addressed via #4755


fix: Root is not necessary to execute the bootstrap script, removing

Removing the need of impersonation on root to execute the bootstrap.sh script
Signed-off-by: Juan Manuel Parrilla Madrid<EMAIL_ADDRESS>Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please select the appropriate options:

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

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


Fix docs scripts to work with latest node.js

New version of Node (v0.5.x) does not support require.paths.push().

closing


Adding sortable class to sortable headers

If a header is sortable this will add a class "ag-header-cell-sortable" to it, and then in the styles I added cursor: pointer.

thanks. will take a look when i get a chance.

i have added the class, but i have not taken the suggestion of changing the mouse to pointer. this is easy to add yourself if you want. reason is that no other parts of the header (eg menu) change when mouse hovers over them.


chore: build docs in debug mode

Description
Don't merge. Just need diagnostic data to fix a hydration mismatch on https://vitejs.dev/plugins/ . It's not happening locally but only on deployed versions.

Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following

[ ] Read the Contributing Guidelines.
[ ] Read the Pull Request Guidelines and follow the PR Title Convention.
[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Huh, not happening with debug mode either.


Taxi dataset

Hi,
Thank you for developing this package. I was trying to get started and was wondering where to get the taxi dataset. It does not seem to be on google drive:

Also, could you point me to how to select datasets from the default config (if you do not have all of the datasets in the right directory)? Thank you!

Apparently the right link is in the paper: https://drive.google.com/drive/u/0/folders/1f8k82-NL6KFKuNMsUwozmbzDSFycYvz7.

Hi, in ReadME file,  i indeed put this link. https://drive.google.com/drive/u/0/folders/1f8k82-NL6KFKuNMsUwozmbzDSFycYvz7.
In short future, we will put the processed data in huggingface instead of Google drive so it will be easy to find and use them.


⚠ Processors has degraded performance

In 5a88289, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 222 ms

Resolved: Processors performance has improved in 8093685.


Remove x-ms-flatten setting for resource properties

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@msyyc could you check the failure of generating python sdk?

/azp run

Why is this not considered a breaking change? It does break any client that respects the annotation...

hey i removed the breaking change and will create separate PR for that

This is a massive breaking change!

@tamilmani1989
Why this change?

i removed the breaking change and will create separate PR for that

@tamilmani1989 any hints on when this will ship? this is blocking our integration right now.


Remove unused monadic for plugin

This plugin is awesome, but there are no fancy fors in this project

Blocks #207

Yeah I think not merging this is fine now, but I was looking for any examples of this plugin's usage and didn't find any in this project, plus it compiles without so I don't think it's used anywhere?


noisetorch: Add noisetorch to systemPackages with programs.noisetorch enable

Description of changes

When a  user uses programs.noisetorch.enable = true; it does currently just set the security wrapper, but does not add it to the environment.systemPackages. Compared with other programs.*.enable thats somehow a bit unexpected for the user.
fixes #183069
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Changes LGTM. Thank you!

Oh sorry I'm curious if this is right. The usage of security.wrappers.noisetorch adds the wrapper noisetorch to the environment and this one should be launched. Adding it also to systemPackages adds an other conflicting noisetorch binary to the path.
Wouldn't it be better to avoid this duplicate entry and maybe add the .desktop file entry differently?

Havent thought about it yet, and as i neither had issues with it on my own system and as other modules also do this. i hadnt thought that it could result in a problem (hadnt thought about).
One example which does exactly the same is the iftop package.
How would be the right approach here? As the desktop item is from the package (currently still missing, there is another pr open to fix that), and i dont see any option to properly override that, so that the wrapper gets picked up.
Do you have an example where its done the right way?
the wrapper does not have any output which can be linked sadly.
nix-repl> nixosConfigurations.pointalpha.config.security.wrappers.noisetorch
{ capabilities = "cap_sys_resource=+ep"; group = "root"; owner = "root"; permissions = "u+rx,g+x,o+x"; program = "noisetorch"; setgid = false; setuid = false; source = "/nix/store/am70cik576cvxx04fa3zggy14pzns0gk-NoiseTorch-0.12.2/bin/noisetorch"; }


Make ComponentValidator internal

...as its no longer used outside of the ResourceInitializer.
Reviewer checklist

[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage remained the same at 97.674% when pulling f5a4a28d9fa41b0b69050fd71c4a425873d26863 on private_component_validator into bf13e3487af64ddf29e9bbd33c5db9017ad20e4e on main.


Update README.md

What it does
Adds some suggested additions to the readme.
Notes
Please let me know if you have any suggestions!

@slammer8 What did you add exactly? I'm having trouble trying to do the diff between commits.


HTML on one line renders incorrectly

If you have HTML on a single line, only the first will render.
See this screenshot of the behavior from the demo.

Only happens in Parsedown Extra. Regular Parsedown is fine.

Also occurs when there is nbsp (u+a0) at the end of the line.

Google is eaten

It seems only block elements do this. Inline elems are unaffected. Only Parsedown Extra is affected.

I can confirm that this is a serious issue.

1

2

The p tag (and contents), along with this line are eaten.

I left a small donation hoping that it helps others resolve this.

I'll see what I can do. It might take some time, though. I'll be quite busy over the next couple of weeks..

It might take some time, though.

Copy that :-) I'm a veteran with PHP, but new to Parsedown. Any ideas where I might start debugging this? If so I might be able to submit a PR for this.

Sure,
It's in the blockMarkup methods in Parsedown.php.
Parsedown does supports one line block-level elements, but it looks for a closing tag at the end of the line. It doesn't consider the element closed when it doesn't find a closing tag at the end of the line.
You could give it a shot, but it might take me much less time to fix, so unless it's urgent it might make more sense to wait.

@erusev writes...

blockMarkup methods in Parsedown.php

Thank you :-) I'll take a look at this in the next day or so and see what I can make of it. Otherwise, I'll wait patiently as suggested.

I noticed an issue with a self closing element which ended in an endless loop. If an element doesn't have any children, the html should be appended directly and not through processText().
I've fixed this in:
https://github.com/storeman/parsedown-extra/commit/ddd0d0bad88429fa8d3e372615b239d78bfd3f42

@storeman Can you provide an example that I can use to reproduce the issue?

First,I have to say it only occurs in the fix from @acmitch. The block element problem seems to be resolved.
Just process '' gave me this issue.
I wanted to notify you about this, in case you wanted to merge the fix from @acmitch.

@storeman Ah, I see, thanks, I appreciate it.

Had more issues today with the solution from @acmitch. I deleted my fork because i could not find the clear edge case where his solution was breaking my html. One of the issues was, textareas were replicated and the dom-structure was altered. For example:
<textarea></textarea>
<input type="checkbox"> Some test

Became
<textarea><textarea></textarea></textarea>
<input type="checkbox"> Some test

It was caused by the surrounding html, but those 13000 lines were to hard to walk through.

@storeman thanks for the feedback! Found a few issues related to the code block you provided.
<textarea></textarea>
<input type="checkbox"> Some test

This first issue, as you mentioned above, was that specific elements were causing endless loops. This has been fixed in my latest commit acmitch@468ecc6
It is important to note that all inline or voided HTML elements must be within the $this->textLevelElements  and $this->voidElements arrays located within the parsedown library for my fix to work properly.
Therefore, to fix the textarea issue you must add the textarea value to the $this->voidElements array, like such:
 protected $voidElements = array(
    'area', 'base', 'br', 'col', 'command', 'embed', 'hr', 'img', 'input', 'link', 'meta', 'param', 'source', 'textarea'
 );

Once, that has been added you should be good to go (I've already tested and works like a charm)! Maybe @erusev can add the textarea permanently if he gets a chance. FYI: I plan to do a little more work to this library over the next few months. I can't seem to get the script tags working as well as a few small things. I will likely have to change the saveXML back to saveHTML once my PHP is updated to a newer version. You might even want to make that change if your PHP version is 5.3.6 or greater.

Here is a failing testcase if it would be off help:
public function testStripping()
{
    $expectedMarkup = '
Contact Method: email

Test

Some italic text.
';
    $actualMarkup = (new ParsedownExtra())->text($expectedMarkup);

    $this->assertEquals($expectedMarkup, $actualMarkup);
}

Results:
1) ParsedownExtraTest::testStripping
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'
Contact Method: email

Test

Some italic text.
'
+'
Contact Method: email
'

@ericbarnes Thanks, Eric, I appreciate it, hopefully, I'll have some time later this month to address the issue.


Update asset admin toolbar

To be merged with - https://github.com/silverstripe/silverstripe-cms/pull/1304
This is the first part of implementation of https://groups.google.com/forum/#!topic/silverstripe-dev/9sfkXXgJS8c
Before:

After:

Just updated with sending the user to a new screen as per wire-frames over at https://groups.google.com/forum/#!topic/silverstripe-dev/9sfkXXgJS8c

The back navigation in the popup title bar disappears in some cases:

Open "Insert Media" and switch to "Insert URL" view
Add a URL, click "Insert"
Select item, open "Insert Media" again (showing edit view)
Close view, unselect item
Open "Insert Media" again -> back navigation is gone


Custom environment

The tutorial for creating a custom environment describes how to add the environment. However, It doesn't mention how to start the RL algorithms on it. Is there some guideline I can follow to test my environment on various algorithms? Also, how can I use AlphaZero, since it assumes a perfect simulator inside its mcts ?

Hello, thank you for your patience. Regarding how to test one environment on various algorithms, we have provided a brief instruction on setting up the config file here, hoping to be helpful to you.
Regarding the use of AlphaZero, indeed as you mentioned, it requires the environment to have a perfect simulator. Specifically, like the board game environment, it needs to have the capability to reset(state), you can refer to the implementation of the Gomoku environment. Therefore, if you want to apply AlphaZero to a custom environment, you need to ensure that your environment can implement this function. If the environment does not meet these conditions, you might not be able to use AlphaZero. As an alternative, you could consider using the MuZero algorithm, which conducts MCTS within the learned model. You can refer to the specific details in the MuZero research paper.
We hope this information is helpful to you! If you have other questions or need further guidance, please feel free to contact us. Thank you again for your attention and support!


eventf not named properly

the source member name is missing from the downloaded eventf
leaving only file names like
.PGM.RPGLE.evfevent
.PGM.SQLRPGLE.evfevent
.PGM.evfevent
.evfevent
This breaks diagnostic viewing for Merlin and Code for i

fixed by pull 147


Handle export JSON from AppMap webview

Integrate the "Export JSON" option from the AppMap. The data is saved to a temp file and opened in the system File Explorer / Finder. The data can then be drag-and-dropped over into Confluence, or any other system that accepts AppMaps / JSON files. The view filter and prune settings are embedded in the exported file, so they will be restored by the AppMap diagram when the file is opened.
https://www.loom.com/share/64b87bad09004ca0978a5f4cee8e070a
Related (pre-requiste): https://github.com/getappmap/appmap-js/pull/1532

@ahtrotta to include some technical details

@jansorg here is some more information:
Here is the relevant PR in VS Code: https://github.com/getappmap/vscode-appland/commit/ba10c685cb678d4efacf7fb02b149cbbecc16f4b
The IDE needs to handle the exportJSON message from the frontend by saving the data to a temp file in the system's temp directory (e.g. tmp on linux) and then opening that temp file using the system's file explorer. The message from the frontend will contain the data that needs to be written in the appmapData field.
Here is the function that needs to be implemented: https://github.com/getappmap/vscode-appland/commit/ba10c685cb678d4efacf7fb02b149cbbecc16f4b#diff-43e9f4ad853fb48d2437ccd2b43a5bc11772c92de1d2193541f6933cf55569d7R35-R50
The temp file should be have the name appmapData.metadata.name if it is present, otherwise it should be a random hex string consisting only of letters, numbers, -, and/or _ (see above implementation in VS Code). Note that the metadata field may not be present on appmapData. The file should have the .appmap.json file extension.
Let me know if you have any questions! Thanks!

:tada: This issue has been resolved in version 0.58.0 :tada:
The release is available on:

v0.58.0
GitHub release

Your semantic-release bot :package::rocket:


This is just a minor fix for issue #204, a typo made it .j" instead o…

…f .js."

Most welcome!! Thank you for pulling :)
On 11/10/21 04:21, Peter Farkas wrote:

@.**** approved this pull request.
I had the same conclusion. Nice job, thanks! :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zostera/django-bootstrap5/pull/209#pullrequestreview-802327148,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWEB3YBAQXPZBVHBK5EMNOLULI2RZANCNFSM5HTECNQA.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Can this be merged urgently, or the pypi release with the broken reference pulled?

I thought it already had been?
Pull from my repo if you require it right now:
https://github.com/di-delta9/django-bootstrap5
On 28/11/2021 18:56, James Hodgkinson wrote:

Can this be merged urgently, or the pypi release with the broken
reference pulled?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zostera/django-bootstrap5/pull/209#issuecomment-981177984,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWEB3YEUO5KPUEMIL7WXWMDUOK6SLANCNFSM5HTECNQA.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

It only got reviewed, not merged or released...

It only got reviewed, not merged or released...

Yes I see this.
If you need a quick and dirty fix like I did first,
Go to your pip library path and fix the file itself, I suppose while we get a permanent merge:
You probably already know but the fix is is easy: you can modify the string in /lib/python3.9/site-packages/django_bootstrap5/core.py. the mistake is right there.

I've already rolled back to an older version rather than making fun patches the norm in prod :)

Fixing in #224, thanks.


always export the requests duration as histogram

handle the case where the user has set a custom prefix.
Fixes https://github.com/Ptrskay3/axum-prometheus/issues/24
This fix is not ideal.
The user has to call with_prefix before calling with_default_metrics.

Oh, I see the problem now, it slipped through previous code reviews. I agree this fix is not ideal as-is: we should deny calling with_prefix after with_default_metrics or with_metrics_from_fn has been called.
We're already using the typestate pattern for our builder, that means it's possible to encode this constraint in the type system.
https://github.com/Ptrskay3/axum-prometheus/blob/da7630a48107996cd0b6f01a757256957cb91b55/src/builder.rs#L15-L20
It's far from a trivial change, but it should be possible with some modifications in builder.rs. If you're not comfortable with the typestate pattern, just tell me, I'll probably be able to look into fixing it this weekend.

I had a quick look.
If we could use negative bounds, I guess it would have been pretty easy:
impl<'a, S> PrometheusMetricLayerBuilder<'a, S>
where
    S: !Paired
{
    /// Use a prefix for the metrics instead of `axum`. This will use the following
    /// metric names:
    ///  - `{prefix}_http_requests_total`
    ///  - `{prefix}_http_requests_pending`
    ///  - `{prefix}_http_requests_duration_seconds`
    ///
    /// Note that this will take precedence over environment variables.
    pub fn with_prefix(mut self, prefix: impl Into<Cow<'a, str>>) -> Self {
        self.metric_prefix = Some(prefix.into().into_owned());
        self
    }
}

But expressing the same without negative bounds is a bit complex for me.
You can take over.

I had some time to take a look, and it's not that complicated as I initially thought.
There're two valid builder states: Paired and LayerOnly, which means !Paired  must be LayerOnly, and we don't need the negative bound. I guess then we can just move the with_prefix method to the appropriate impl block:
impl<'a> PrometheusMetricLayerBuilder<'a, LayerOnly>
How does this sound?

You're right, it's looking good: https://github.com/Ptrskay3/axum-prometheus/pull/26/commits/346e04e05e4830db282fa40ad0825242e0027989

Do we have infrastructure to test that some code does not compile?
If yes, I could add a test for this.

We don't have compile-fail tests, but I'm planning to create some basic test suite, and I might include that as well.
Anyways, the changes look good to me.
Not related to your changes, but one thing I also noticed:
https://github.com/Ptrskay3/axum-prometheus/blob/da7630a48107996cd0b6f01a757256957cb91b55/src/builder.rs#L224-L230
The metric_prefix is not passed through there. This should be
        metric_prefix: layer_only.metric_prefix,

Could you add this to the PR? I don't have the access to push to your branch.

good catch, done in https://github.com/Ptrskay3/axum-prometheus/pull/26/commits/7daedfcff6d26e1f0151e5c551d4156964324ca9

Thanks, overall it looks good to me. I'll go ahead and merge this. I'm planning to release the next version of this crate this weekend.


PropertyAssignmentStructure name property does not allow for quoted strings

Hey,
First of all thank you for this wonderful library. I find it very useful.
I was using ObjectLiteralExpression.addPropertyAssignment and tried to use a name wrapped in double quotes eg '"options"' (which is legal in JavaScript and allows for things such as reserved name properties such as '"class"' and dash joint words such as  '"some-others"', as well as necessary point to make an object valid JSON)
this error is thrown :
Error: Cannot read property 'kind' of undefined
-- Details --
Path: E:/Data/showWS/ribbon.initialstate.ph_modfiled.ts
Text: "...\t\t\t\"tooltip\": \"Lesions\",\n\t\t\t\t\t\t\"text\": \"Lesions\",\n\t\t\t\t\t\t\"clientActionOnly\": true\n\t\t\t\t\t},\n\t\t\t\t\t\n\t\t\
t\t\t\n\t\t\t\t\t\"children\": [],\n                    \"options\": {\n                        {\n                                                \"s
howIcon\": true,\n                                                \"showText\": false\n                                            }\n
    }\n                },\n\n\t\t\t]\n\t\t},\n\t\t{\n\t\t\t\"type\": \"TabsContainerModel\",\n\t\t\t\"toolID\": \"ribbon.control\",\n\t\t\t\"elementMo
del\": {..."
    at InvalidOperationError.BaseError [as constructor] (E:\Data\showWS\node_modules\ts-simple-ast\dist\errors\BaseError.js:7:28)
    at new InvalidOperationError (E:\Data\showWS\node_modules\ts-simple-ast\dist\errors\InvalidOperationError.js:8:28)
    at Object.doManipulation (E:\Data\showWS\node_modules\ts-simple-ast\dist\manipulation\manipulations\doManipulation.js:12:15)
    at insertIntoParentTextRange (E:\Data\showWS\node_modules\ts-simple-ast\dist\manipulation\manipulations\insertion.js:16:22)
    at Object.insertIntoCommaSeparatedNodes (E:\Data\showWS\node_modules\ts-simple-ast\dist\manipulation\manipulations\insertion.js:53:9)
    at ObjectLiteralExpression._insertProperty (E:\Data\showWS\node_modules\ts-simple-ast\dist\compiler\expression\object\ObjectLiteralExpression.js:2
39:24)
    at ObjectLiteralExpression.insertPropertyAssignments (E:\Data\showWS\node_modules\ts-simple-ast\dist\compiler\expression\object\ObjectLiteralExpre
ssion.js:69:21)
    at ObjectLiteralExpression.addPropertyAssignments (E:\Data\showWS\node_modules\ts-simple-ast\dist\compiler\expression\object\ObjectLiteralExpressi
on.js:52:21)
    at ObjectLiteralExpression.addPropertyAssignment (E:\Data\showWS\node_modules\ts-simple-ast\dist\compiler\expression\object\ObjectLiteralExpressio
n.js:45:21)
    at visitTSNode (E:\Data\showWS\fix-external-options.js:78:17)

if I remove the quotes (this time it was only for consistency with other properties on that object, which is really a JSON)
it runs OK

Hey @nadavsinai, there must be some kind of bug here, but I think it's probably the same as #334. I just committed some tests that pass when using single and double quotes for the name.
I never received word back in #334 about how to reproduce. Would you be able to provide a simple example that reproduces the bug? Thanks!

I'm closing this as a duplicate of #334. I still don't know what causes this issue because I'm awaiting feedback on that issue.


[KYUUBI #2066] fix spelling mistake and appropriate naming

Why are the changes needed?

fix #2066
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

thanks, merged to master


Add support for a cookstyle config file

Really enjoy the extension - thank you!
It would be nice to be able to configure a per workspace configuration file.  For example, we regularly set the Style/EndofLine cop to  enabled: false via a configuration file.  Not sure how difficult that would be to implement, but it would keep the user experience consistent how we manage the behaviors of various cops in our projects.
Thanks for considering this.

This sounds like a reasonable request!  If we exposed a workspace setting like rubocop.configfile to enable this and you were able to set the value to either a relative path within the workspace or an explicit path that could be outside the workspace, would that work for you?  This would be the equivalent of calling cookstyle --config #{rubocop.configfile} from your command line.

I think that would work well for the scenario I described.
I looked at the code earlier today and I'm not sure I understand it completely, but I may attempt to address this myself in the next few days.

I had a look tonight and as I haven't touched the code for a while had to upgrade a lot of the underlying framework (latest Typescript, linting tools, typings etc...) - anyway this is now fixed as of extension 0.6.3 - please give it a go and report back!

This appears to not work as expected - with version 0.6.3 i've defined my config file as follows:
"rubocop.configFile": ".rubocop_todo.yml"
It contains:
Style/EndOfLine:   Enabled: false
Code is still alerting me to this issue.  But, if I run cookstyle manually it runs without flagging this issue in my file:
` cookstyle --config ..rubocop_todo.yml .
Inspecting 8 files
........
8 files inspected, no offenses detected`
Thoughts?

ahh... need to reload code after making my workspace settings... thanks so much!

Great.  A reload is required for this config change if the project has already been loaded (as the extension only loads this config at load time).  Closing this one now.


Unable to write to stream: fwrite(): send of 8192 bytes failed with errno=32 Broken pipe

11:19:34 ERROR     [websocket] Connection error occurred Unable to write to stream: fwrite(): send of 8192 bytes failed with errno=32 Broken pipe in /var/www/awex.com.ua/vendor/react/stream/src/Buffer.php line 121 ["connection_id" => 10862,"session_id" => "456846955a323dee318b1236559306","client" => "anon-456846955a323dee318b1236559306"] []
"require": {
        "php": ">=7.1",
        "ext-intl" : "*",
        "doctrine/doctrine-bundle": "^1.6",
        "doctrine/doctrine-fixtures-bundle": "^2.3",
        "doctrine/doctrine-migrations-bundle": "^1.2",
        "doctrine/orm": "^2.5",
        "gos/web-socket-bundle": "^1.8",
        "gregwar/captcha-bundle": "^2.0",
        "h4cc/wkhtmltopdf-amd64": "^0.12.3",
        "h4cc/wkhtmltopdf-i386": "^0.12.3",
        "incenteev/composer-parameter-handler": "^2.0",
        "knplabs/knp-paginator-bundle": "^2.6",
        "knplabs/knp-snappy-bundle": "^1.5",
        "kwn/number-to-words": "^1.3",
        "misd/phone-number-bundle": "^1.2",
        "phpoffice/phpexcel": "^1.8",
        "sensio/distribution-bundle": "^5.0.19",
        "sensio/framework-extra-bundle": "^4.0",
        "sonata-project/admin-bundle": "^3.23",
        "sonata-project/doctrine-orm-admin-bundle": "^3.1",
        "stof/doctrine-extensions-bundle": "^1.2",
        "symfony/monolog-bundle": "^3.1.0",
        "symfony/polyfill-apcu": "^1.0",
        "symfony/swiftmailer-bundle": "^2.3.10",
        "symfony/symfony": "^3.4",
        "twig/extensions": "^1.5",
        "twig/twig": "^1.0||^2.0",
        "yadelivery/name-case-lib": "^1.1"
    },

PHP 7.1.12-1 (cli) (built: Nov 29 2017 10:01:08) ( NTS ) Copyright (c) 1997-2017 The PHP Group Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies     with Zend OPcache v7.1.12-1, Copyright (c) 1999-2017, by Zend Technologies
"name": "react/stream",
"version": "v0.4.6",

"name": "react/socket",
"version": "v0.4.6",

It looks like you're using an outdated version of this component, can you try updating to the latest version?
Without further details, it's a bit hard to diagnose this. It looks like your server is trying to write to a connection that has been closed on the client side. This it not a fatal issue and after emitting an error event, the server should automatically close() the connection.
I hope this helps :+1:

I have problem:
Unable to write to stream: fwrite(): Send of 205 bytes failed with errno=32 Broken pipe
File: ../vendor/react/stream/src/WritableResourceStream.php
Line: 140


“PimpMyStremio” is damaged and can’t be opened. You should move it to the Trash.

Hi,
I was having an issue with one of the addons for pms. I tried deleting pms and reinstalling it but receive this error when opening it again. "“PimpMyStremio” is damaged and can’t be opened. You should move it to the Trash."
on MacOS Catalina

It's possible that the update failed for some reason and the engine is now a corrupted.
When downloading PimpMyStremio, you are actually downloading an updater, which checks for a new version, downloads it and installs it if needed, then runs PimpMyStremio.
The actual installed version is at ~/Library/Preferences/PimpMyStremio, deleting this folder deletes the entirety of all PimpMyStremio data from your Desktop.
You should try deleting that folder and re-downloading PimpMyStremio.

Actually, no.. i don't think an update caused this, any chance you can tell me what add-on you were you having issues with? I should debug it to make sure it isn't causing any issues for the PimpMyStremio environment.

I tried deleting that folder but am still receiving the same error. I was having issues with the Jackett addon. I was never able to load it onto Stremio.

Do you think it could be an issue with terminal using zsh on CatalinaOS instead of bash?

I was also able to install the 123TV add-on to stremio but it didn't work.

Uhm, I haven't personally tested it on Catalina.. You should try running PimpMyStremio with --verbose from the terminal to see if there's anything helpful in the logs. (they will be printed in the terminal)
A different user recently mentioned he managed to get Jackett working well with that add-on by using the mono version of Jackett:
https://github.com/sungshon/PimpMyStremio/issues/45

Nov  7 19:10:09 Mac-mini com.apple.xpc.launchd[1] (com.apple.xpc.launchd.oneshot.0x10000004.PimpMyStremio[1466]): Service exited due to SIGKILL | sent by CoreServicesUIAgent[1462]
I could not get it to run in terminal. I see this error in the console.app. Do you know what it means?

This does not tell us much...
You can also try running it from the terminal with the --no-children flag, to see if that helps, but I somehow doubt it.
I've checked around to see if there were any major changes in Catalina, but the only one I can find is that it now only supports 64bit apps, but PimpMyStremio was always 64bit on OSX, so that can't be the problem.

Oh, ok, I think I see the problem now, check this StackExchange answer:
https://apple.stackexchange.com/questions/372084/macos-catalina-app-is-damaged-and-cant-be-opened-you-should-move-it-to-the-t
Please try the solution mentioned there. As much as I can gather from it, some OSX security thing is much more rigorous in Catalina, and PimpMyStremio was quarantined without asking you, OSX is now actively blocking it from starting.
This is probably due to the fact that I'm not paying for a very expensive code signing certificate to sign the app, which would make OSX / Win trust it in general.

Yup, this is an OSX Gatekeeper issue, there are more solutions on this page too:
https://apple.stackexchange.com/questions/262355/xxx-cant-be-opened-you-should-move-it-to-trash-for-flash-projector-applicat
This is more of an OSX issue in general it seems, not a PimpMyStremio issue.

That was the issue. I tried the first solution and it worked.
Thank you so much for your help on this issue and thank you for all your great work on PimpMyStremio.

Glad to hear it! For add-ons that don't currently work, they could be automatically fixed in time as their developers fix them. All installed add-ons are automatically updated when you start PimpMyStremio.


Create C++ library for doing polynomial factorization

Since there isn't any great or useful libraries for doing polynomial factorization, create a library that can be used in C++ programs, etc. for doing them

Done https://github.com/gbowne1/polyfact


Request: expose ASIN

Currently {{url}} is available in the plugin. The last part of the URL is the Amazon ASIN, which is useful for a couple reasons - I can use it to call up a cover image for the book, for example. (In sample link https://www.amazon.com/dp/B08S35PYWM the ASIN is B08S35PYWM.) Could you expose this as {{asin}} perhaps?
This would also make possible a link to jump to the highlight in a kindle app, like this: [link](kindle://book?action=open&asin={{asin}}&location={{highlight.location}}) - or the kindle://book?action=open&asin={{asin}}&location={{highlight.location}} could be {{applink}} or something? (I'm happy to put that string in my template though, everything but the {{asin}} part works as expected. ^_^
If there's an easy way to do this in the nunjucks template and I just haven't figured it out, I'd welcome the knowledge. Super, super great plugin, already a vast improvement over my previous workflow.

This enhancement has been bundled as part of release 0.0.7.
If you go to the plugin settings tab, you should see many new variables that I've added including your suggestions - asin, and appLink. If you change your template, you will need to reset and re-sync your highlights to use the latest templates again.


setup.py needs to be updated (2)

Hi there. First of all, thanks for this awesome project, simplifies a lot of work!
I'm creating this issue with the same name as https://github.com/kubeflow-kale/kale/issues/196 because when I install kubeflow-kale via pip3 I'm getting:
ERROR: Could not find a version that satisfies the requirement ml-metadata==0.23.0 (from kubeflow-kale==0.5.1) (from versions: 0.12.0.dev0, 0.13.0.dev0, 0.13.1.dev0, 0.24.0)
ERROR: No matching distribution found for ml-metadata==0.23.0 (from kubeflow-kale==0.5.1)

I was thinking that this was related to announcement-pip-20-2-release/4863 or use-feature-2020-resolver
But when I downloaded kubeflow-kale: kubeflow-kale-0.5.1.tar.gz from: pypi.org/project/kubeflow-kale/0.5.1 and uncompress tar.gz in setup.py there's  ml_metadata == 0.23.0:
  install_requires=[
        'kfp',
        'autopep8 >=1.4, <1.5',
        'astor >= 0.8.1',
        'nbformat >=4.4, <5.0',
        'networkx >=2.3, <3.0',
        'jinja2 >=2.10, <3.0',
        'graphviz >=0.13, <1.0',
        'pyflakes >=2.1.1',
        'dill >=0.3, <0.4',
        'IPython >= 7.6.0',
        'jupyter-client >= 5.3.4',
        'jupyter-core >= 4.6.0',
        'nbconvert >= 5.6.1, < 6.0.0',
        'ipykernel >= 5.1.4',
        'packaging > 20',
        # XXX: remove this once https://github.com/google/ml-metadata/pull/60
        # is merged.
        'grpcio >= 1.8.6',
        'ml_metadata == 0.23.0',
    ],
    extras_require={
....

Cheers

p.d. to reproduce this you can use this Dockerfile It stops with error in line 28

ml_metadata has already been updated in the master branch. Please try installing from there as it should solve your issue.

Ok, thanks. I'm closing this.


bug: react-native package '@react-native-clipboard/clipboard' is missing.

Describe the bug
A clear and concise description of what the bug is.
Install React-Native package @react-native-clipboard/clipboard. Package is missing from package.json file of ( .wrappid\runtime\mobile).
Vesrion should be<EMAIL_ADDRESS>To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Stack Trace
The stack trace of the bug if any.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

This issue has become invalid and does not require testing.


[P000606] Rep. Robert Pittenger

Rep. Robert Pittenger:
http://pittenger.house.gov
Likely contact form URL to start with:
http://pittenger.house.gov/contact/email-me

YMAL file not found. I am working on it.


Now working on fallback devices

it is working fine in all high end ios and all android but not working on low end ios,
i am using this code
ReactNativeHapticFeedback.trigger('notificationWarning', true);
please suggest

Are you using the latest version, 1.1.6?

Hey,
thanks for getting back.
The Fallback applies to Devices not capable of the haptic engine (iPhone 6 and lower) and should return a heavy vibrate.
Can you specify the devices that are not working?
According to the iOS Docs:
"On some iOS devices, you can pass the kSystemSoundID_Vibrate constant to invoke vibration. On other iOS devices, calling this function with that constant does nothing."
Greetings
PS: Please use 1.1.5 for the latest working solution. Will provide an update to the 1.1.6 that is currently available

Currently, I am using version 1.1.6, getting a build error related to peer dependency, I have resolved it by modifying, in package.json
  "peerDependencies": {
    "react-native": "^0.41.2"
  },

Alright, I'll wait for 1.1.7 then.

@wouterds version 1.1.7 is released now and working ;)
@ranvir-gorai for iOS it´s not possible to make a fake vibration pattern like i implemented for android. Actually the fallback is also just a workaround. There is no other way that i could find to trigger really small vibrate (50ms) callback if haptic is not available.
The only thing i can do is make the supportsHaptic Callback public available through the library to properly find an other way to give feedback to the user from UI perspective.

I'm a bit confused, is there a fallback implemented now for older devices like iPhone 6 or not? I just tried it with 1.1.7 but it's indeed not doing anything on iPhone 6.

Hi,
sorry for the late response. I had a pod and npm package mismatch. Can you check if it´s occuring with the 1.2.0 Version?

Tested on iPhone 6, iOS 10.2, doesn't work.

@mkuczera is there any way to make it work on iPhone 6?

Hi @Kamill90 ,
i implemented a small vibrate for older iPhone Devices. But i´m struggling because i got no iPhone older than 7 for testing. In fact, i would appreciate it if someone could have a look on it and open a PR due to the fact that this library is only testable through real devices.
Greetings


Volume keys (.volumeUp and .volumeDown) do not work

When listening for a volume keypress (.volumeUp or .volumeDown) using
let hotKey = HotKey(key: .volumeUp, modifiers: [])
hotKey.keyDownHandler = {
 print("Volume up pressed")
}

the keyDownHandler is not called. In this example, it should print "Volume up pressed" when you press the volume up key.

I'm seeing the same thing, and this was reported earlier as well (https://github.com/soffes/HotKey/issues/11). I take it no one is looking at this? The earlier thread had a suggested fix. Although I have no idea if that would actually work.
In my case I'm adding modifiers, the idea is to use the volume keys to control the volume on something besides my Mac, but no matter what I try the built in functions take over. Does anyone know if it's possible to make this work?
Thanks!


add partial callback

With this change the user can decide to provide a callback for partials.
This callback will be queried when a partial is needed. Partials can thererfore be provided lazy.

The ci seems to be broken. It fails to install the base system rather than a real compiler error

I was thinking of implementing exactly this, too.
My one suggestion would be to cache partials obtained via the callback. That way they don't need to be refetched every time (e.g., if used in a list).


Typescript compatibility

Is it type-safe? Because i dont see @types/ultimate-express in npm site

If you'll make a PR with .d.ts file I'll happily merge it. I don't have experience with TS stuff.

Though your workaround probably wouldn't work since we don't include Express as module

I haven't seen a way of publishing package to @types. Looks like its managed automatically from .d.ts in npm modules so that would including express as dependency, which I really wouldn't want to do. Looks like we have to make our own d.ts file afterall

@dimdenGD What if install @types/express as dependency, then use that as typings ?

declare module 'ultimate-express' {
  import express from 'express';
  export = express;
}

declare module 'ultimate-express' {
-  import express from 'express';
+  import express from '@types/express';
  export = express;
}

Like @hillac solution but alternative way

declare module 'ultimate-express' {
  import express from 'express';
  export = express;
}

declare module 'ultimate-express' {
-  import express from 'express';
+  import express from '@types/express';
  export = express;
}

Like @hillac solution but alternative way

Wow, is this possible? Feels like a simple solution

I dont know how TS works, but wouldn't it notice that instances of objects are different from original ones?

Since this project its API is compatible with express I override express with ultimate-express in the package.json
{
  "dependencies": {
    "express": "npm:ultimate-express@latest"
  },
  "devDependencies": {
    "@types/express": "latest",
    "typescript": "latest"
  }
}

Change latest with the version of your choice

Simple solution
src/typings/ultimate-express.d.ts
declare module 'ultimate-express' {
    import express from '@types/express';
    export = express;
}

tsconfig.json
{
    ...
    "typeRoots": [
        "src/typings",
    ],
    ...
}

It works!
Just a problem. Default export of express ia a function with no arguments:
express(): Express;

But ultimate-express accept an settings parameter (https://github.com/dimdenGD/ultimate-express/blob/main/src/application.js#L50C17-L50C26)
On typescript if try to add settings I show this error:

the workaround is mutate typescript error

If you know how TS declaration file works, you can make PR to fix this: https://github.com/dimdenGD/ultimate-express/blob/main/src/types.d.ts
Unfortunately I don't have knowledge in it

Should be all working in 1.3.1!

Should be all working in 1.3.1!

Nice one!! So.. what is the solution? We can just use npm i uiltimate-express?? Does it already come with type safety feature?

Yes

This happen because "cookie-parser" get a different version of "express" types. Try to override express
{
    "name": "test",
    "version": "1.0.0",
    "devDependencies": {
        "@types/cookie-parser": "^1.4.8",
        "typescript": "^5.6.3"
    },
    "scripts": {
        "build": "tsc"
    },
    "dependencies": {
        "cookie-parser": "^1.4.7",
        "ultimate-express": "^1.3.16",
        "express": "npm:ultimate-express" // <--------- override express with ultimate-express
    },
    "false": {}
}


Fix hover when it should separate multiple summaries

Fixes #6998
Summary of the changes
The actual behavior:

The expected behavior:

The fix:
The changes in this PR helps to add a line of padding in between summaries.

It somehow seems like it is adding two new lines. So I need to figure our why this is happening.
Fixes: #6998

I expected the proper fix to be the thing, that was done in the legacy editor with the separation line, but this implementation is ok as a tactical fix. I believe, this separation line is just not available in the current state of LSP-based hovers, right?

@DoctorKrolic where can I find the source code for legacy editor?

Would be good to compare with the source code for the legacy editor

I believe, the legacy editor is not open source. Since your are a Member and can push to this repo directly, you might probably have access to the internal VS repository as well, where the sources for the legacy editor are most likely to be. I don't think comparing source code is a valid thing to do here since these two editors are based on completely different approaches of making IDE tooling though

Fixed the two failing tests in DefaultVSLSPTagHelperTooltipFactoryTest.cs due to the fix in this PR.
Remaining test failures that might show up in CI would be flaky integration tests and unrelated to the change here.


Feature request: allow language services to validate breakpoint locations

Note
I am opening this feature request based on https://github.com/OmniSharp/omnisharp-vscode/issues/5267
Original opener: @cateyes99
Overview
In full Visual Studio, when the user tries to set a breakpoint, the UI will ask the language service to validate the breakpoint request. This allows the language service to decide if a given location is a valid location for a breakpoint. For example, a comment isn't a valid location.
Visual Studio has an LSP extension for this -- textDocument/validateBreakableRange.

Neither VS Code nor DAP knows anything about LSP. So this feature request sounds like a private communication between a specific DAP and LSP.

VS handles breakpoint placement different than VS Code does. @weinand correct me if I am wrong:  in VS Code breakpoints are placed and only validated when a debugger runs. In VS a language server can validate a breakpoint. This makes sense where a language server knows enough about the generated code (which is the case in C#). To support that VS as an LSP extension that send a request to a language server to validate such a breakpoint.
I guess @gregg-miskelly is asking to support such a validation model in VS Code as well.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

@gregg-miskelly @dbaeumer thanks for clarifying.
This feature request is similar to the "inline value" and "debug hover" support because the feature is debug-related but the "data provider" lives on the language extension side.
Similar to the corresponding InlineValuesProvider and EvaluatableExpressionProvider extension APIs we would need something like a BreakpointLocationValidator extension API that the C# extension could implement for C# via the LSP extension textDocument/validateBreakableRange.
VS Code's generic debugger UI would use the BreakpointValidator to validate breakpoint creation. One problem in VS Code is that breakpoints are not typed (or bound to a specific source language). Users can set them at any time in any file and any debugger can make use of them. So if a C# breakpoint validator thinks that a breakpoint in a C# comment isn't valid, there might be another debugger that sees this differently. I don't really know how the UI for breakpoint validations would look like.
Since I don't think that invalid breakpoint locations are a big pain point in VS Code, I don't see that this feature request gets high priority on our backlog...

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Game crashes immediately without error message

Godot version
4.0.1.stable.official [cacf49999]
System information
Windows 10
Issue description
When I attach a PackedScene to my script, the game crashes immediately upon opening with no messages. Without the scene attached, it works as normal.

Steps to reproduce
Play Game1 scene with Linked Scene attached
Minimal reproduction project
Project.zip

There are error, but they don't appear in the editor for some reason (only the external console):
ERROR: res://scenes/player_living_room.tscn:13 - Parse Error: [ext_resource] referenced nonexistent resource at: res://scenes/player_bedroom.tscn
   at: ResourceLoaderText::load (scene\resources\resource_format_text.cpp:490)
ERROR: Failed loading resource: res://scenes/player_living_room.tscn. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core\io\resource_loader.cpp:223)
ERROR: res://scenes/player_bedroom.tscn:6 - Parse Error: [ext_resource] referenced nonexistent resource at: res://scenes/player_living_room.tscn
   at: ResourceLoaderText::load (scene\resources\resource_format_text.cpp:490)
ERROR: Failed loading resource: res://scenes/player_bedroom.tscn. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core\io\resource_loader.cpp:223)
ERROR: res://scenes/Game1.tscn:4 - Parse Error: [ext_resource] referenced nonexistent resource at: res://scenes/player_bedroom.tscn
   at: ResourceLoaderText::load (scene\resources\resource_format_text.cpp:490)
ERROR: Failed loading resource: res://scenes/Game1.tscn. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core\io\resource_loader.cpp:223)
ERROR: Failed loading scene: res://scenes/Game1.tscn
   at: (main\main.cpp:2965)

You can't have a cyclic scene reference. You can use @export_file and load() as a workaround.
While cyclic scene references are not supported, this shouldn't be crashing silently.


ConfigureFunctionsWebApplication method no longer exists

Firstly, thanks for the great write-up, I'm most of they way through migrating a fairly complex set of function apps from in-proc to isolated mode thanks to this document.
One thing I noticed is that the Program.cs code:
var host = new HostBuilder()
    .ConfigureFunctionsWebApplication()

doesn't work any more - I think this should now be:
var host = new HostBuilder()
    .ConfigureFunctionsWorkerDefaults()

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

ID: ebb94eda-541d-913f-0668-64690a8320a7
Version Independent ID: 4fe76422-6653-a93f-d6c4-3bc510da6cf0
Content: Migrate .NET function apps from the in-process model to the isolated worker model
Content Source: articles/azure-functions/migrate-dotnet-to-isolated-model.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

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


Integrate Eye Tracking Insights into Usability Reports

Design templates and formats for incorporating eye tracking insights into usability testing reports.

Develop scripts or plugins to automate the generation of visualizations and summaries from eye tracking data.

Define key metrics and performance indicators derived from eye tracking analysis to assess usability and user experience.

Ensure that eye tracking insights are presented in a clear and actionable manner for stakeholders and design teams.

Hey, I can take this up. Can you tell me the approach of how can I start this?


Cant Paper Trade With Model File

2017-09-02 18:25:52  0.00004954 XRP-BTC   +0.0%     3182   53 +       buying  0.2017-09-02 18:25:52  0.00004954 XRP-BTC   +0.0%     3182   53 +       buying  0.2017-09-02 18:25:52  0.00004954 XRP-BTC   +0.0%     3182   53 +       buying  0.00 XRP  1000.00000 BTC    +0.0%   -0.9%
{ Error: connect ETIMEDOUT <IP_ADDRESS>:443
at Object._errnoException (util.js:1041:11)
at _exceptionWithHostPort (util.js:1064:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1153:14)
code: 'ETIMEDOUT',
errno: 'ETIMEDOUT',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 443,
desc: 'could not execute buy: error fetching quote' }
2017-09-02 18:26:00  0.00004962 XRP-BTC   +0.2%     3210   56 ++              0.00 XRP  1000.00000 BTC    +0.0%   -1.0%
how do I fix this?

This has nothing to do with the model file, zenbot has problems connecting to the exchange API. Just try again, check you exchange's status page and check your internet connection.

ok yea ur right it works now.


EventLogTamper.ps1 Error Catch

Code seems to finish and run on local system, due to no logs being found, but no logs being found also breaks the recursive nature after checks for multiple events. This makes sense to me, but makes for bad code. Review and fix.

Get-WinEvent : The specified query is invalid
At line:5 char:20

... ingEvents = Get-WinEvent -LogName Security -FilterXPath "*[System[(Ev ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Get-WinEvent], EventLogException
FullyQualifiedErrorId : System.Diagnostics.Eventing.Reader.EventLogException,Microsoft.PowerShel
l.Commands.GetWinEventCommand

The error "The specified query is invalid" was caused by the FilterXPath parameter in the Get-WinEvent cmdlet. The FilterXPath parameter expected a valid XPath expression, mine was not valid. Built an actual XPath array line, and code works as expected.


llvmlite: init at 0.6.0 - work in progress

I'm trying to make a package of llvmlite, which seems to be a bit more challenging than the average Python package. llvmlite is an important prerequisite for the numba JIT.
The environmental variable LLVM_CONFIG needs to be set to the path that llvm_config resides in. Aside from this, the docs don't mention any further configuration.
Unfortunately, when building, the headers cannot be found:
fatal error: llvm/Config/config.h: No such file or directory
I've tried setting C_INCLUDE_PATH to the directory with the headers by appending this value to makeFlags without success.
Any suggestions?
[ci skip]

Using now
  llvmlite = buildPythonPackage rec {
    name = "llvmlite-${version}";
    version = "0.6.0";

    src = pkgs.fetchurl {
      url = "https://github.com/numba/llvmlite/archive/v${version}.tar.gz";
      md5 = "b3a6b60d600f18e9f5948af5fb4a354b";
    };

    propagatedBuildInputs = with self; [ pkgs.llvm ];

    # set directory containing llvm-config binary
    buildPhase= ''
      export LLVM_CONFIG=${pkgs.llvm}/bin/llvm-config
      ${self.python.executable} setup.py build
    '';

    meta = {
      description = "A lightweight LLVM python binding for writing JIT compilers";
      homepage = "http://llvmlite.pydata.org/";
      license = licenses.bsd2;
    };
  };

and unfortunately still unable to find the headers. LLVM_CONFIG is set correctly.


crate jdbc driver question - SchemaUnknownException: Schema 'doc' unknown

My question is that crate jdbc driver can not fetch the data of the doc schema.
CrateDB version is 3.0.6， crate jdbc version is 2.3.0
Error: ERROR: SchemaUnknownException: Schema 'doc' unknown
SQLState:  XX000
ErrorCode: 0
please help me, thanks!

This issue is resolved, because of user privilege。


[#3910][DotNet] Add Bot Authentication SNI sample bot

#minor
#addresses #3910
Description
This PR adds a new sample for csharp_dotnetcore that shows how to authenticate the Azure bot using the Subject Name/Issuer from MSAL.
Proposed Changes

Added the new sample bot-authentication-sni.
Added a simple bot conversation to validate the authentication.
Added README file with the instructions and information about the sample and how to create a SSL/TSL certificate.

Testing
This image shows the new bot-authentication-sni sample working.

@JhontSouth Can you update this to use SDK version 4.21.1


Add ' description: "" ' to output from generate_source to match generate_model_yaml

Describe the feature
generate_model_yaml is great!   I like that it adds the description line even though it is blank.
I would love that same feature for generate_source.
Describe alternatives you've considered
I could probably cobble something together with a script.
Additional context
This would be especially powerful when combined with a script and yq to merge the yml files like I currently do.
Who will this benefit?
Anyone who wants to document their data with as few a keystrokes as possible.
Are you interested in contributing this feature?
At this time that isn't an option due to legal reasons.
Thanks!

I think this exists now, see this file: macros/generate_source.sql
here's an example usage of the args that generate placeholder descriptions: dbt run-operation generate_source --args '{"generate_columns": "True", "include_descriptions": "True", "schema_name": "some_schema", "database_name": "some_db"}'


local variable use lower case to avoid clashing with the main script

CLOUD variable is set up in the post-startup script as readonly

In this context, you are defining this as a script-local variable (as opposed to a function-local variable)?
Since the script is sourced, then "cloud" becomes available to the parent (the post-startup script) as a side-effect. I think that we should establish some patterns to avoid that.
As this script is always sourced, why pass the parameter instead of just picking up the variable from the environment. Otherwise, we can do things like:
declare FOO=...

unset FOO

to avoid side effects.

i renamed user to USER_NAME in the first PR and i forgot to rename user in a subscript and break the script.  so it feels unreliable to depends on the master script to set certain variable.. but i guess i should just add a test to run the script in a github action to catch this.

A few additional patterns to consider:
1- The sub-script header contains a comment indicating the expected variables and functions, this would be one of them
2- We can add a section at the start of the script that will validate that all expected variables are set
# Fail fast and consistently if required variables are not set
declare -F emit > /dev/null || (echo "Function emit does not exist" && exit 1)
declare -F get_metadata_value > /dev/null || (echo "Function get_metadata_value does not exist" && exit 1)

echo "${RUN_AS_LOGIN_USER}" >/dev/null
echo "${WORKBENCH_INSTALL_PATH}" >/dev/null
echo "${WORKBENCH_LEGACY_PATH}" >/dev/null
echo "${USER_BASH_COMPLETION_DIR}" >/dev/null

i will apply the fail-fast suggesiton in a follow-up


Implement cats-effect ConcurrentEffect instance for IO

I think this depends on #81

Nope, it is already in 0.10.1

I have it mid implemented already but I have to fix a bug in runAsync first

I mean the laws were improved and ZIO has no chance to pass the old ones

Dunno, we're passing the old laws for Effect. You saying for Concurrent it's somehow different? We've got other finalization and cancellation semantics. Haven't we?

Yes. We didn't pass concurrent laws which prompted a super long discussion.


Getting started

To get started with OpenFOAM,

have a look at the files contained in test_cases/cylinder2D_base
determine how drag coefficient and Reynolds number are computed
run the test case according to the instructions in README.md
create two refined versions of the base case by adjusting the refinementSurfaces and refinementRegions sections in the snappyHexMeshDict
compare drag and lift

time signals
statistics (mean, variance, min/max)

` $PV_PLUGIN_PATH and -plugin-path= not defined
No supplementary ParaView/OpenFOAM reader modules
Using builtin reader: paraFoam -vtk
/usr/lib/openfoam/openfoam2006/bin/paraFoam: 420: paraview: not found
I am getting this Error after exicutingparaFoam` command.
I have run the test run and it runs fine just can not visualize in paraFoam.

$PV_PLUGIN_PATH and -plugin-path= not defined
No supplementary ParaView/OpenFOAM reader modules
Using builtin reader: paraFoam -vtk

/usr/lib/openfoam/openfoam2006/bin/paraFoam: 420: paraview: not found

I am getting this Error after exicuting paraFoam command.
I have run the test run and it runs fine just can not visualize in paraFoam.

There is no ParaView inside the Docker container, but you can do visual post-processing outside the container using a standard ParaView installation. You can install it, e.g., using one of the following commands:
# debian-like
sudo apt-get install paraview
# archlinux and similar
sudo pacman -S paraview
# centOS and similar
sudo yum install paraview

Then you can open an OpenFOAM case by running (not in the container):
paraview post.foam

post.foam is just an empty dummy file. If there is no such file, you can create one in the case folder using touch:
touch post.foam

Best, Andre

Thank you very much Andre.
For the OpenFoam issue.
solution 1)
As you mentioned i have created post.foam(in case you are running Allrun.sh then it will generate by shell scrip.) and then i have opened with paraview. And while opening one has to select : Case Type to Decomposed Case (as the decomposition is occurred due to parallelization).
(If one is running container(docker) that the paraview command should executed from another terminal window as container does not have paraview)
solution 2)
Generating the VTK file to each folder of processor_0 and processor_1 by following command:
foamToVTK

This command will generate VTK directory in both processor_0 and processor_1, which will be imported consequently in paraview. (because of decomposition).

Hello Andre,
I have tried to fine the mesh but i am not able to do it. I can maximum refine it till blockX=275.

Create mesh for time = 0

Selecting extrudeModel linearDirection
Selected extrudeModel for linearDirection using coeffs
{
    constructFrom   patch;
    sourceCase      "$FOAM_CASE";
    sourcePatches   ( front );
    exposedPatchName back;
    extrudeModel    linearDirection;
    direction       ( 0 0 1 );
    thickness       0.01;
    flipNormals     false;
    mergeFaces      false;
}

Extruding from patch using model linearDirection
Collapsing edges < 0.0001 of bounding box

Extruding patches 1(front) on mesh "/home/darshan/test_cases/cylinder2D_base"

Create mesh for time = 0

Adding overall 0 processor patches.
Mesh bounding box : (0 0 0.0073333333) (2.2 0.41 0.017333333)
        with span : (2.2 0.41 0.01)
Merge distance    : 1e-06

Collapsing edges < 1e-06 ...

            Uncollapsed edges = 0 / 83566
    Number of points : 33712
    Not visited      : 0
    Not collapsed    : 33712
    Collapsed        : 0

Collapsing 0 cells

Hi Darshan,
the attached log file was created by the utility extrudeMesh (executed after snappyHexMesh). Are you sure that snappyHexMesh fails? If so, could you push the current state to the repository such that I can have a look?
Best, Andre

Hi Andre,
I am not sure weather snappyHexMesh fails. But i can see no error on log of blockMesh and the following fatal error message from snappyHexMesh. Moreover i push the current status and that contains terminal_log.txt file where you can see the terminal messages.
Best Andre,
Darshan
--> FOAM FATAL ERROR:
Point (1.02 0.15 0.008) is not inside the mesh or on a face or edge.
Bounding box of the mesh:(0 0 0) (2.2 0.41 0.0073333333)

    From static Foam::labelList Foam::refinementParameters::findCells(bool, const Foam::polyMesh&, const pointField&)
    in file snappyHexMeshDriver/refinementParameters/refinementParameters.C at line 241.

FOAM exiting

Hi Darshan,
this issue is easy to fix. snappyHexMesh needs a reference point to identify cells that are inside the domain and cells that can be deleted. As you refine the background mesh, the thickness in z-direction becomes smaller and smaller. At some point, the locationInMesh parameter in the snappyHexMeshDict will be located outside the background mesh generated by blockMesh. The solution is to reduce the z-coordinate of the reference point to a very small value, e.g., 1e-8.
Best, Andre

Hi Andre,
Thank you for the reply. :)
i should change thickness = some small value. Right ?
Best Regards,
Darshan

Yes, but in the snappyHexMeshDict and not in the blockMeshDict

Thank you. I understood. :)

Respected Sir,
Hi Andre, I hope you had nice weekend. i have created new commit containing graphs of mesh study. From the graphs it is clear that after 500 blocks in X-axis the value will not fluctuate more. Moreover 500 blocks seems computationally expensive as it took nearly 3hr to finish, so my question is weather 500 is the most appropriate mesh size or we can go for 250 or 300.
Thank you :)
mesh_study.csv format : | no. | mesh_size | μ_Cd | std_Cd | mean_Cl | std_Cl |
Best Regards,
Darshan


Can't align qrcode in center of paper

Hey, Marcus !
I'm using your package and you've doing a great job!
But , when I try print a QR-Code in center of paper, in a Sunmi TS2, the QR-CODE are printed in the left of paper...
I tried:
await SunmiPrinter.setAlignment(SunmiPrintAlign.CENTER);
await SunmiPrinter.printQRCode('myqrcodestring', size:3, errorLevel: SunmiQrcodeLevel.LEVEL_M);

But don't worked.
Best Regards!

So I find the best way to work with T2s.
Before print QrCode or BarCode , close transaction(submit and exit), init transaction again and print.
After print, again, close transaction and init transaction.
In this way the setAlignment work's fine.

So I find the best way to work with T2s.
Before print QrCode or BarCode , close transaction(submit and exit), init transaction again and print. After print, again, close transaction and init transaction.
In this way the setAlignment work's fine.

That´s a good approach!
I think the qrcode just print in some align  and to do that i think will work.
Thanks for your reply!


Polishing README.md (and possibly other docs)

I've edited the first part of the documentation here to improve clarity and readability, including making it easier to understand for less technically-inclined users who wish to test the new Corescripts via the release builds (I'd like to go further with a more in-depth step by step in order to get 1.1x into the hands of more testers).
Please understand that I don't mean to insult you with these changes. This is very well written for someone with English as a second language, and I would like to offer my assistance in helping to polish this and future documentation as well. :)
If you like the idea, I will return to finish refining the remainder of the document at a later time. I love RPG Maker MV and I've written several software manuals in the past as I do this professionally, so this is the best way I can contribute.

Hmm, I should look further into things like that before trying to do any editing then.

@JALowther it seems ok otherwise, it was just a minor nitpick. Please don't shy away from polishing the text because of that minor issue!!

Oh, it's not just that (please don't feel bad).
After I did these edits, it occurred to me that there were a few things I'd need to ask for clarification on from the developers...and then it occurred to me that this would be counter productive as I'd be taking up more of their already valuable time. :\
The docs will be okay as they are. It would take someone with a better technical grasp than I have in order to touch these up without having to pester the devs about clarifying things so I had best leave it to someone else.

@JALowther sure, but you should at least go ahead and keep this README.md pull request. You're not really touching any technical topics (apart from the place I mentioned, where I already suggested you a correction) and it seems like a worthy improvement.
As for the docs, I can't comment for the developers but there are people around like me who still have a good grasp on the core script source code (I'm a plugin developer mainly, so I have dug through a lot of it in my freetime) and who can help you with this as well. While I guess if you really have no idea of any technical details that might be a problem, if you just have some occasional gap you can't decipher from the code then it's probably not much of an issue either.

@JALowther Hi, we are not good at English, so your contribution is very appreciated! 😇
Would you please reopen this pull request?
If you have any questions on revision, please ask me :-)


Suggestion: increase non-blocking writing syntactic sugar

idea
There are too many codes in golang for Chan to write without blocking. Often write this code, the mood will be depressed
current writing
select {
    case m.err <- err:
    default:
}

hope, possible writing
m.err <<- err

m.err <<- err

To make the Chan of go non blocking, you usually need to write the following code.
package main

import (
        "errors"
        "fmt"
)

type message struct {
        err chan error //In concurrency, only the first error is saved
}

func newMessage() *message {
        return &message{err: make(chan error, 1)}
}

func (m *message) writeNoblockingError(err error) {
        select {
        case m.err <- err:
        default:
        }
}

func (m *message) readNoblockingError() error {
        select {
        case err := <-m.err:
                return err
        default:
        }
        return nil
}

func main() {
        m := newMessage()
        m.writeNoblockingError(errors.New("1. error"))
        fmt.Println(m.readNoblockingError())
        fmt.Println(m.readNoblockingError())
}

If you have a short code, it can make things simple and interesting
package main

import (
        "errors"
        "fmt"
)

type message struct {
        err chan error //In concurrency, only the first error is saved
}

func newMessage() *message {
        return &message{err: make(chan error, 1)}
}

func main() {
        m := newMessage()
        m.err <<-errors.New("1. error"))
        fmt.Println(<<-m.err)
        fmt.Println(<<-m.err)
}

Thank you for your sample code. I see that in this example this would reduce the need for a helper method to turn the receive into a non blocking receive. My next question will be -- does this help in real code? What is the value of doing a non blocking read? Yes it does not block the caller, but what does that permit the caller to do in a real program?
If you could explain how your proposal would affect programs that use methods like readNoblockingError() that would be useful for me.
Thank you.

@guonaihong I wouldn't invest time on this; the language avoids multiple ways to write things. See #33892.
The best you can do is write it on one line: select { case c <- v: default: }

I don't understand how it is possible to use a statement like m.err <<-errors.New("1. error")).  In order to use a channel correctly you have to know whether the value is sent or not.
Similarly, for <<-m.err, you have to know whether a value was received.
As a historical note, before Go 1 you could write
    if c <- v {
        fmt.Println("sent value on channel")
    } else {
        fmt.Println("failed to send value on channel")
    }

But we removed that capability because it was unnecessary given the existence of the select statement.  https://go.googlesource.com/go/+/19d9a408451662d09b49fe3b0f1971728e28213f^!/#F0

I echo @ianlancetaylor point. On paper it is possible to create a new syntax that makes a One line blocking receive into a non blocking one but this introduces another problem. Channel receive is an expression, it must return a value. In both the original example and your <<- syntax this “nothing was available” value was the zero value for the type. It seems to me that the caller would have to inspect this value to know “was a value received or not” and then you’re back to the same level of verbosity as previous, just one level of abstraction removed.

If the type of m.err is a comparable type, the m.err <<- err is a comparison expression.

Duplicate of #34203


al-input/al-model

Alight has al-value, al-checked, al-radio, al-select, al-focused for two-way.

one directive for two-way?
angular 1<input ng-model="todo.text" />
angular 2<input [(ngModel)]="todo.text" />
vuejs <input v-model="message" />
aurelia.io <input type="number" value.bind="model" />

yes, please. :-)
But i also would it implement only as alias directive (al-bind or al-model), so it automatically chooses the correct directive (al-radio or al-value etc.).

but al-value and al-focus is two different directives, if merge it to one, why it wouldn't cause collision?

al-focus is an event handler, this will be al-on.focus or @focus.
al-value is accessing an attribute AND watching for a change / keydown event, so this the typical way how you can interact with an input element. So it is useful to move the default usage pattern into a model abstraction, e.g. using al-model or al-bind.
Some examples:
When changing

textarea the property "value" is changed
text-input the property "value" is changed
checkbox the checked-state is changed
select the selectedIndex is changed

This is the default change, when a user interacts with a element which he can modify.
The default attribute are the attributes i just noticed, so it is useful to map them against a simple API.
E.g.:
<input type="text" al-model="user.name" />
<textarea al-model="user.description"></textarea>
<input type="checkbox" al-model="user.gender" value="Male" />
<input type="checkbox" al-model="user.gender" value="Female" />

This would simplify the API for developers, because they can alwayse use al-model to bind a model to a user input element.

al-focus is an event handler, this will be al-on.focus or @focus.

al-on:focus.twoway="model"
@focus.twoway="model"

?

@focus="fn()"  // element --> scope
@focus.twoway="model"  // element <--> scope
@focus.oneway="model"  // element <-- scope

@focus="fn()"  // element --> scope
al-model="model"  // element <--> scope
:focus="model"  // element <-- scope - your case would be an attribute "focus" and does not make sense in my opinion

ok, looks well

@focus and :focus are ready  http://jsfiddle.net/lega911/o24sn60h/

al-model

done: http://jsfiddle.net/lega911/2rzLrxgr/
it proxies to other directives: https://github.com/lega911/angular-light/blob/master/src/directive/model.coffee

al-model="model"  // element <--> scope

we can't do this for focus, because it's used for element.value

al-model="model" // element <--> scope
we can't do this for focus, because it's used for element.value

now it is al-focused="model", propose if you have an idea about it

al-model

done: http://jsfiddle.net/lega911/2rzLrxgr/
it proxies to other directives: https://github.com/lega911/angular-light/blob/master/src/directive/model.coffee

This is great!

now it is al-focused="model", propose if you have an idea about it

This is ok for now.
I think about using user experience states, e.g.

focus
hover
active
disabled
But i think it does not make sense to build additional directives for the others.

hover

it's interesting, al-hovered="model" ?

active

what is it about?

active

maybe click-time?

it's interesting, al-hovered="model" ?

Maybe, the idea is to change a scope when the mouse is over an element.

what is it about?

http://www.w3schools.com/cssref/sel_active.asp
E.g. when you click on an element. When you click on another element, the click state gets disabled (see example on w3schools).

hover and active are both one-way bindings - they are events, so probably we can itegrate them to @events, we can add modifier "model" to declare that we use model instead of js expression.
@mousehover.model="model"
@mouseactive.model="model"

for "hover" we can use "mouseenter + mouseleave"
@mousehover.model="model"
==
@mouseenter="model=true" @mouseleave="model=false"

for "active": mousedown + mouseup + mouseleave
https://jsfiddle.net/lega911/x4ggb2ct/

You asked if al-focus should be a standalone directive.
I recomended to take a look to typical CSS pseudo classes, because :focus is a pseudo class in CSS.
We do not need to implement these pseudo classes, it is just a recommendation, that al-focus does not need to be integrated in the al-model concept.
The only additional case i see would be the hover-state, but there should be no problem to apply events for this case. So it is ok to let al-focus stay standalone.


Add additional dependency

Noticed when building on Ubuntu now fails without libunwind.
On Ubuntu: sudo apt install libunwind-dev

It should only be with Musl: https://github.com/bpfkorea/agora/blob/1a76952d3102c45b6894b54d9a00f32f9f26e896/source/agora/utils/libunwind.d#L21-L23

It should only be with Musl: https://github.com/bpfkorea/agora/blob/1a76952d3102c45b6894b54d9a00f32f9f26e896/source/agora/utils/libunwind.d#L21-L23

Also the submodules downgrade are accidental I suppose ?

Also the submodules downgrade are accidental I suppose ?

It should only be with Musl:
https://github.com/bpfkorea/agora/blob/1a76952d3102c45b6894b54d9a00f32f9f26e896/source/agora/utils/libunwind.d#L21-L23
But it is linked here

It should only be with Musl:
https://github.com/bpfkorea/agora/blob/1a76952d3102c45b6894b54d9a00f32f9f26e896/source/agora/utils/libunwind.d#L21-L23
But it is linked here

Yeah it's because we don't have the ability to specify that we only want this linking to happen in Musl (https://github.com/dlang/dub/issues/2080).
Let's merge for now and I'll revert once we upgrade LDC.

Yeah it's because we don't have the ability to specify that we only want this linking to happen in Musl (https://github.com/dlang/dub/issues/2080).
Let's merge for now and I'll revert once we upgrade LDC.


Detailed explanation of level

As the user suggested, I have applied detailed descriptions of levels.
Problem: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/4577

Thanks @illfated. @joinimran, please review the suggested changes so that @nenonix or @JohanFreelancer9 can do the final copy review.

Done, thanks @illfated for all your contribution.

Done.

Hello @Dansimp, this pull request has been copy edited and is ready for your final review and approval. The descriptions are now in sync with the information the user sees on the actual screens (Intune & Group Policy Management Editor). Please let us know if there are outstanding issues to be resolved prior to merge. Thank you.

Rich Text Diff view, for easier overview of the changes:
https://github.com/MicrosoftDocs/windows-itpro-docs/pull/5068/files?short_path=c20f56c#diff-c20f56c413c3550eccd8b260606a30dc

Hi @Dansimp, just a follow-up on the status of this PR. Kindly review when you have time. Thank you.

As always, thank you @Dansimp for merging this PR. Much appreciated!


Desync - Synchronization Problems

A list of all reported synchronization problems to help route users to the appropriate issue.
Text out of sync:

Briefly out of sync, but then caught back up
Lines were duplicated and/or deleted
Browser
"The current document is out of sync with the host" dialog
Browsing source control changes
File operations
git operations
Save/Discard changes
New tab with same name
Can't see cursors or any edits
External application modifying files
Simultaneous editing
Another extension causing issues
Issues with Dart

Other components out of sync:

Diagnostics aren't in sync
Save not working

Closing this tracking issue as stale.


Migrate FieldValue to Protobuf

This PR removes the FieldValue classes and updates the client to directly use Protobuf messages internally. It aligns the iOS client with the Web and Android client.
CPU time benchmark On iPhone 8:

Benchmark Name
Branch (us)
Master (us)
Speedup (x)

BM_QueryIndexFree/0/1
7.68
18.6
2.42

BM_QueryIndexFree/1/1
12.3
27.7
2.25

BM_QueryIndexFree/1/10
13
28.7
2.21

BM_QueryIndexFree/10/10
22.4
25.9
1.16

BM_QueryIndexFree/1/100
11.9
29.2
2.45

BM_QueryIndexFree/100/100
8.87
24.3
2.74

BM_QueryIndexFree/1/1000
18.7
29
1.55

BM_QueryIndexFree/10/1000
17.8
28.9
1.62

BM_QueryIndexFree/100/1000
9.89
36.9
3.73

BM_QueryIndexFree/1000/1000
21.1
46.4
2.20

BM_QueryMatching/0/1
12.8
40.5
3.16

BM_QueryMatching/1/1
18.7
41.2
2.20

BM_QueryMatching/1/10
35.3
45.9
1.30

BM_QueryMatching/10/10
53.4
59.4
1.11

BM_QueryMatching/1/100
63.4
108
1.70

BM_QueryMatching/100/100
44.5
127
2.85

BM_QueryMatching/1/1000
60.3
251
4.16

BM_QueryMatching/10/1000
73.3
181
2.47

BM_QueryMatching/100/1000
24.7
149
6.03

BM_QueryMatching/1000/1000
27.8
150
5.40

BM_QueryAll/1
21
32.2
1.53

BM_QueryAll/10
24.5
34.5
1.41

BM_QueryAll/100
9.41
37.9
4.03

BM_QueryAll/1000
17.3
Out of memory
Inf

Full results (internal): go/fieldvalue-benchmark
XCode's Leak Detector does not detect any leaks with this PR when used in FriendlyEats.

I shared a trace with the remaining leaks (excluding spec tests). I don't think there are any more relevant leaks from this PR.

@var-const Verified that ASAN tests still pass and added more performance numbers to go/fieldvalue-benchmark


Revert stake and mint integration tests

Fixes #609
This PR adds revert stake and mint integration tests.

Reviewing 🦑


added bze external gauges in web feature-flag

Sorry for writing here but I wonder if this can be merged ? I half of hour are incentives start. We didn't know that a PR is required to show the incentives in FE, otherwise we would've submit this PR a lot earlier.

@faneaatiku  These gauges were set to run over only 2 and 4 epochs, so they are nearly done already. Will longer gauges be created (ideally at least 30 days)?

@faneaatiku These gauges were set to run over only 2 and 4 epochs, so they are nearly done already. Will longer gauges be created (ideally at least 30 days)?

Seems that I didn't understood the documentation. I started a new gauge. and modified the PR


[region-isolation] Some initial NFCI refactoring commits before adding experimental support for inheriting isolation to nonisolated functions

I am preparing a larger patch that actually implements the experimental feature that allows for nonisolated functions to inherit isolation from their caller.
To make the larger patch easier to review, I am peeling the onion by slicing off some refactoring commits that it depends on for early testing/landing.

@swift-ci smoke test

@swift-ci smoke test

@swift-ci smoke test

@swift-ci smoke test

@swift-ci smoke test

Had to restart testing due to a sourcekit-lsp issue that is unrelated to this PR.