NMS.GEN.MCTS.004 - MCTS Beneficiary (Kilkari subscriber) identification

A Kilkari Beneficiary shall be identified by a unique identifier that comprises of state specific MCTS Id along with State identifier. However, if the Kilkari subscriber activates their subscription by calling the IVR long codes (one for each pack) then they will remain anonymous unless and until MCTS data is uploaded where a pregnancy or birth record matches with the MSISDN number of the anonymous subscriber. For anonymous subscribers, they are only identified by their MSISDN + pack info.
It’s possible that a child MCTS record and pregnancy MCTS record could exist at the same time for the same woman. If the pregnancy record is present, then this record will be UPDATED if a new MCTS record is uploaded  that contains both a child MCTS ID and a pregnancy MCTS ID, where the pregnancy MCTS ID already exists in NMS. In other words, only one subscription will be maintained for the same woman, the pregnancy pack shall be de-activated (if activated) and child-pack shall be activated based on DOB of the child. If, when a MCTS child record is being uploaded, no pregnancy record is found then only the child-pack shall be activated based on DOB of the child.
For details see Appendix A

From Appendix A:

During every pregnancy, a mother is assigned a mother ID which is
generated by MCTS application (MCTS ID for mother) and this ID remains the
same, even after Child Birth. This MCTS ID is a unique 18 digit ID (see format
below)
After the birth of the child, the child is registered with a new MCTS ID, which
is the child ID (child registration is mapped to the mother MCTS ID)
There are records in MCTS for the babies who have a child MCTS ID but no
mother MCTS ID as their mothers were not registered during their pregnancy.
MoHFW is in the process of transitioning MCTS to RCH (however, the MCTS
can be used for current purpose). RCH application shall also have a unique
ID for mothers but it will be a 12 digit ID; furthermore post the transition to
RCH, there shall be mapping between RCH IDs and MCTS IDs
MCTS Team confirmed that Tamil Nadu, Rajasthan, Gujrat, Tripura,
Chhattisgarh and Karnataka have their own formats for IDs in the MCTS,
which is not 18 digit and varies from state to state. So a strict format for
MCTS may not be assume as of now.
There shall be a web-service to fetch all new or newly updated records since
last fetch from MCTS. However, this interface is outside the scope of this
document.
MCTS team confirmed that the application does not have a unique MSISDN
mapping i.e. same MSISDN can be linked with multiple mother records. For
the NMS, one MSISDN can map to two records
Any field update in records shall come as update in entire record

The second part of this (automatic deactivation of mother pack when child is imported) still needs to be implemented.


Add use_element_bounding

See https://solidjs-use.github.io/solidjs-use/core/useElementBounding
Branch: use_element_bounding

Implemented in commit 34c913c


Add pip install support

Move svelte files from src/ to pysvelte/svelte/src so that they can be packaged up within the module
Set the setup.py file to use scm & package data (so that it includes these non-python files)
Fix .gitignore to allow for moved files (and put in categories)
Minor bug fix on setup version to make pip happy

Can confirm it works with Colab and Jupyter Lab. Colab test at https://colab.research.google.com/drive/1o7jMEQ81UP1lzKejVFos99ss21FwuLZS?usp=sharing

Thanks Alan! I've just added a small addition to the instructions, and once I've merged it I'll update my Colab notebook (linked in the instructions) to use the new install process


add e2e test for slr

[x] Make sure you have followed Kube-OVN Code Style.

What type of this PR
Examples of user facing changes:

Tests

add e2e test for slr
Which issue(s) this PR fixes:
Fixes #(issue-number)
WHAT

🤖 Generated by Copilot at 8598127
This pull request adds e2e tests for the vpc-internal-lb feature, which enables internal load balancers for services in a VPC network. It also adds helper files and methods in the test/e2e/framework package to interact with endpoints and switch-lb-rule resources, which are used by the vpc-internal-lb feature. The main test file is test/e2e/vpc-internal-lb/e2e_test.go, and the test cases are run by the Makefile.e2e file.

🤖 Generated by Copilot at 8598127

To test the vpc-internal-lb feature
We need some wrappers and clients to measure
The endpoints and rules
That create the switch pools
And the e2e tests to check the behavior

HOW

🤖 Generated by Copilot at 8598127

Add a new feature to enable internal load balancing for services in a VPC network
Define a new resource type switch-lb-rule to create and manage internal load balancers (link)
Add a new file test/e2e/framework/switch-lb-rule.go to provide a wrapper for the switch-lb-rule client (link)
Add a new e2e test suite test/e2e/vpc-internal-lb/e2e_test.go to verify the functionality and conformance of the switch-lb-rule resource (link)
Add a new line to build the test binary for the vpc-internal-lb e2e test suite (link)
Add a new target to run the vpc-internal-lb e2e test suite as a separate command or as part of the conformance-e2e target (link)
This file is used to interact with endpoints resources in the e2e tests, which are used to verify the functionality of the switch-lb-rule resources (link)

Move this test case into kube-ovn-conformance-e2e.

Move this test case into kube-ovn-conformance-e2e.

done

There are some changes in the e2e framework, please rebase the master branch.


Cannot use web proxy to access Artifactory

Hey,
I am using artifactory client services 2.6.0 in my project in order to fetch data from Artifactory. My desktop is behind a corporate web proxy. I get a timeout every time I tried to fetch data. Looking for a solution I found in this repository the class ProxyClient.
But a get the following error while building :
ProxyConfig(java.lang.String,int,java.lang.String,java.lang.String,java.lang.String) has protected access in org.jfrog.artifactory.client.ProxyConfig

It seems that ProxyConfig contrustor is protected in 2.6.0 and public in 2.6.1.
When will you push version 2.6.1 on bintray ?
My code is :
        ArtifactoryClientBuilder builder = ArtifactoryClientBuilder.create();
        builder.setUrl(url)
                .setUsername(login)
                .setPassword(api_key);

        // Set proxy if needed
        List<Proxy> hostProxies =  ProxySelector.getDefault().select(new URI(url));
        Proxy hostProxy = hostProxies.get(0);
        if ( hostProxy.type() == Proxy.Type.HTTP ) {
            InetSocketAddress hostProxyAddr = (InetSocketAddress) hostProxy.address();
            String proxy_host = hostProxyAddr.getHostString();
            int proxy_port = hostProxyAddr.getPort();
            log.debug("Configuration du proxy web " + proxy_host + ":" + proxy_port);
            ProxyConfig proxy = new ProxyConfig(proxy_host, proxy_port, null, null, null);
            builder.setProxy(proxy);
        }

@zeenlym,
Thanks for reporting.
2.6.1 published today on Bintray: https://bintray.com/jfrog/artifactory-tools/artifactory-client-java/2.6.1


Service Offering Sorting is broken in UI

ISSUE TYPE
Bug Report
COMPONENT NAME
UI
CLOUDSTACK VERSION
4.11.1
CONFIGURATION
N/A
OS / ENVIRONMENT
Ubuntu 16.04
SUMMARY
Trying to order Compute service offerings in UI, but the result is the same as before sorting. UI controls allow moving offerings against each other, including drag and drop way, but after page reload they are still in the same order as before.
STEPS TO REPRODUCE
Create several service offerings, try to reorder them in UI.
EXPECTED RESULTS
Items reordered
ACTUAL RESULTS
Items in the same order

Later investigation has shown that it also broke in Templates/ISO sorting order.

@anuragaw can you verify fix this, since I think you've fixed sorting for couple of resources in the UI.

Copy @rhtyd

DB support for service offerings was existing but I discovered another bug while testing and fixed it in the above PR.

As per remarks on https://github.com/apache/cloudstack/pull/3445, this is fixed. Closing.


Add an Option to Register a Global Hotkey for Toggling the Main Window

Description of the feature, modification, idea or suggestion
Currently, toggling the display of the main window requires moving the cursor to the tray menu to show it and then navigating to the top-right corner to hide it. This process can be inconvenient and interrupts workflow.
Adding support for a customizable global hotkey to toggle the main window would greatly enhance usability and improve efficiency.
Proposed implementation details (optional)
No response

This is a feature already included with Windows by default.

You can make System Informer the default Task Manager and Ctrl+Shift+Esc, Ctrl+Alkt+Del and a bunch of other Windows keys will toggle the main window.

or

Right-click the application icon from the start-menu or the desktop shortcut and open the file properties.
Configure the "Shortcut Key" which is a global hotkey.

Windows will launch the application when using the "Shortcut Key" so it doesn't need to remain running. If you've enabled the "Allow only one instance", "Hide when closed" and "Hide when minimized" options then the shortcut key will toggle the main window.

Hi @dmex ! Thank you for your quick response and the detailed guidance!
My Experience and Observations

Default Task Manager Settings
I once tried setting System Informer as the default task manager. However, I found myself struggling to adapt to it. Some features, like CPU virtualization, memory frequency, and the speed of individual disks or network adapters, are occasionally useful, and I missed having direct access to these details. Finally I decided to use both.

Shortcut Key Behavior
I tried setting up a shortcut key just now, but it didn’t work as expected. This might be because I placed the shortcut in a custom directory, such as Startup or the Desktop.

Why not put it in the Startup folder?
Files in the Startup folder execute synchronously, which significantly slows down the boot process. To address this, I use a .bat script to launch applications asynchronously.

My Suggestion
Given these limitations, I believe a built-in global hotkey registration feature would be a much better solution—similar to how Everything implements it.

By including such functionality, System Informer would offer a smoother and more integrated user experience. Let me know if there are any additional details you'd like me to provide!


Pass functions to ConfigureOptions to print version, help, tls help

This will allow NATS Streaming to provide its own version of what
should be printed when various flags are set.
Related to #578

Coverage increased (+0.07%) to 92.018% when pulling 8b4a02dd9a4918b7603d264419d514ad3ef6d325 on update_configure_options into b58178d74342ec20474ce2ff6451a84f8efafd12 on master.


Shorter than seq_len sequences, padding from left?

Sorry, silly question..
Let's say my seq_len is 100 and these are time-ordered, so t0 < t1 < ... < t100 and I have a few instances in my batch which are shorter. So I'll pad them with zeros naturally from the left, i.e:
batch_size=2

0, 0, 0, t1 < t2 < ... < t97
0, 0, 0, 0, t1 < t2 < ... < t96

Am I right in assuming that TCN will read (enforce causality) from left to right, i.e. the future time points have to be always to the right of the older ones?
Thanks in advance..

Yep, that's the right way to do it.


[New Feature] Add support for accelerated Networking and Hibernation (image def only)

Added support for Accelerated Networking during session host deployment and adding the feature to the image definition during custom image creation. This feature flag is required in order to deploy session hosts from the custom image with accelerated networking configured. Additionally added the capability to select an additional image definition feature - Hibernation.
Required update to the Microsoft.Compute\galleries\images CARML module (matches recent merged PR to CARML).

@shawntmeyer thanks for your contribution.
cc: @swathibhat1 adding accelerated networking and hibernation features.


Remove or migrate Type/snapper

https://docs.perl6.org/type/snapper
This is not a Type.
@lizmat @zoffixznet

I agree.  Do you have a suggestion where to put this then?

On 24 Nov 2017, at 06:55, Alex Chen<EMAIL_ADDRESS>wrote:
https://docs.perl6.org/type/snapper
This is not a Type.
@lizmat @zoffixznet
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Language/Telemetry is an option.

0a93d3f fixes this issue, isn't it?


Add permissible value to Bulk RNA-seq Level 3 'File Format' data element

Information
Proposed change:
Add the permissible value 'rds' to File Format data element for use in Bulk RNA-seq Level 3 data submission

How important is this feature?
Will allow Lung Precancer Atlas (BU) to submit file format accurately

🌗 Medium - can do work without it; but it's important (e.g. to save time or for convenience)

When will use cases depending on this become relevant?

Short-term - 2-4 weeks (required for accurate metadata submission)

Discussed with Clarisse who suggests the site can use RData indicating rds format.  Closing issue.


Wrong description on "Feature Contributions" tab

Brief Issue Summary
Incorrect descriptions of settings on "Feature Contributions" tab. See screenshot

Expected:
Correct descriptions
Platform and Versions

Operating System: macOs 10.14.5
CMake Version: 3.14.5
VSCode Version: 1.45.1
CMake Tools Extension Version: 1.4.0

This started to happen with 1.3.1.

This is a VS Code bug: https://github.com/microsoft/vscode/issues/54111


Incorrect use of exported function in module's other functions

Describe the bug
Modules other functions should use live binding instead of local function directly
Input code
export const thing = () => {
    console.log("hello")
}

export const other = () => {
    thing()
}

Config
{
    "jsc": {
      "parser": {
        "syntax": "typescript",
        "tsx": false
      },
      "target": "es5",
      "loose": false,
      "minify": {
        "compress": false,
        "mangle": false
      }
    },
    "module": {
      "type": "commonjs"
    },
    "minify": false
  }

Playground link
https://swc-play.vercel.app/?version=1.2.165&code=H4sIAAAAAAAAA0utKMgvKlFIzs8rLlEoycjMS1ewVdDQVLC1U6jmUgACkEx%2BTqpeTn66hlJGak5OvpImVy0XVyqyxvySjNQiNI1gwzRAagFUTES3ZAAAAA%3D%3D&config=H4sIAAAAAAAAA0WNSwrDMAxE76J1tt3kDj2ESZXg4B8aBWqM7165OGQnzedNoxMbrY2KE7CMCzWp%2B9JKWgtjE1%2BUFlKYtLsA7vY4OVgtwniZF3IGT3eh6JPf6yBtORZh4LFcOsKd7AaK%2BXMNof3HDGiVmNMJ6g9olj3eM61ycf8BnwbyVboAAAA%3D
Expected behavior
other uses exports.thing
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
exports.other = exports.thing = void 0;
exports.thing = function () {
    console.log("hello");
};
exports.other = function () {
    exports.thing();
};

Actual behavior
thing is used directly in other's body
"use strict";
Object.defineProperty(exports, "__esModule", {
    value: true
});
exports.other = exports.thing = void 0;
var thing = function() {
    console.log("hello");
};
exports.thing = thing;
var other = function() {
    thing();
};
exports.other = other;

Version
1.2.194
Additional context
This is issue when patching exported function from external module in unit tests.
PS. SWC playground seems broken. wasm.js was renamed to wasm-web.js in swc 1.2.171 in jsdeliver.

No swc is correct.
Please search for issues before creating one

I couldn't find reference to the bug neither in swc or typescript repos before opening this issue. Maybe i'm just missing related search tems.
But after checking how rollup, swc and babel transpiles that same code I can see that swc is consistent with others. Could you point me to related issue?


Can not run the project

Hello,
I can not execute ng serve, I have this error
ERROR in Error: Metadata version mismatch for module D:/sts-workspace/project/node_modules/ng2-tree/index.d.ts, found version 4, expected 3, resolving symbol ComponentsModule in D:/sts-workspace/project/src/app/pages/components/components.module.ts, resolving symbol ComponentsModule in D:/sts-workspace/project/src/app/pages/components/components.module.ts

+1

+1

I also have the same problem

+1

+1

version 2.0.0 works

2.0.0-rc.1 doesn't works for me. my angular/cli is 1.2.7

I delete ng2-tree and delete the folder "tree" from pages, and I delete treemodule call in page module.
npm uninstall ng2-tree
and it's work I don't need this component but it will be cool if we cans fixe it for next versions.

Hey Guys, could you let me know your npm version? As it looks like your npm avoided package-lock.json and installed the latest angular 5 version of ng2-tree. Please, conder using the correct npm version (5+).

Ok :
works with
"ng2-tree": "2.0.0-alpha.10"
Don't work with the caret (^)
"ng2-tree": "**^**2.0.0-alpha.10"
With the caret npm take the "2.0.0-rc.1" and this release need Angular 5.

I am also facing the same issue with npm start command:
ERROR in Error: Metadata version mismatch for module D:/workspace/akeveo/ngx-admin/node_modules/ng2-tree/index.d.ts, found version 4, expected 3, resolving symbol ComponentsModule in D:/workspace/akeveo/ngx-admin/src/app/pages/components/components.module.ts, resolving symbol ComponentsModule in D:/workspace/akeveo/ngx-admin/src/app/pages/components/components.module.ts
at Error (native)
at syntaxError (D:\workspace\akeveo\ngx-admin\node_modules@angular\compiler\bundles\compiler.umd.js:1729:34)
at simplifyInContext (D:\workspace\akeveo\ngx-admin\node_modules@angular\compiler\bundles\compiler.umd.js:24979:23)
at StaticReflector.simplify (D:\workspace\akeveo\ngx-admin\node_modules@angular\compiler\bundles\compiler.umd.js:24991:13)
I am using the following node version:
node --version : v6.11.4
npm -v : 3.10.10

node V7
npm 3.10.8
node degrade to last version a.k.a  2.0 it work only this version got the error

Don't you just love when your release doesn't happen due to a plugin!

Guys, please make sure you npm version is 5+ or update it to a newer with:
 npm i npm -g
Then remove the node_modules and install from scratch.
This is a requirement for the project.

What do you mean by "remove the node_modules"?  Thanks

@anishThomas4419 Did you find a solution?

@vishaldhiman I've uninstalled ng2-tree and reinstalled with 2.0.0-alpha.10 version. It helped me to run non start. followed the comments from  @FARHANE. Thanks all.

@Yolepo Thanks, "ng2-tree": "2.0.0-alpha.10"  it works for me

@nnixaa Hello nnixaa, I try your method and it OK ,now the npm is 5.6.0 and the node.js is 6.12.0.But a new issue is occurs after I update the npm(this issue doesn't occur before update) is as fellows:
kris-allen@krisallen:~/ngx-admin$ npm install
npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EINTEGRITY: sha512-WIr7iDkdmdbxu/Gh6eKEZJL6KPE74/5MEsf2whTOFNxbIoIixogroLdKYqB6FDav4Wavh/lZdzzd3b2KxIXC5Q== integrity checksum failed when using sha512: wanted sha512-WIr7iDkdmdbxu/Gh6eKEZJL6KPE74/5MEsf2whTOFNxbIoIixogroLdKYqB6FDav4Wavh/lZdzzd3b2KxIXC5Q== but got sha1-EfgjGPX+e7LNIpZaEI6TBiCCFtg=. (1837200 bytes)
npm WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.
npm WARN tar zlib error: unexpected end of file
npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/kris-allen/.npm/_logs/2017-11-29T19_48_56_963Z-debug.lo

### Why the issue is ? How should I do for it ?


White list does not work

I have just set variable intero-whitelist via M-x customize-variable to list of my projects (one directory) and set
(add-hook
 'haskell-mode-hook 'intero-mode-whitelist)

as documentation says. Intero still loads on every project it can touch and eats all my memory for nothing.

Try M-x describe-variable haskell-mode-hook. Make sure that you no longer have intero-mode in that list. You can do this by running (remove-hook 'haskell-mode-hook 'intero-mode).


Freeing Pirates on Kaltherz is not Roster bound

But instead you can do it on every character, together with the unas task.
Gr8 work m8!!

Fixed


Wrong test count in slack when using playwright-slack-reporter from Bitbucket pipeline

I do use standard setup for playwright-slack-reporter in my config

For some reason when i run tests from Bitbucket - i do have wrong test pass/fail/skip count in case i do have retries set
retries: process.env.CI ? 2 : 0,

If i do it from local - there are no issues
Is there a way to fix it when run on Bitbucket?

hey @Alona-T ,
I would recommend having 2 playwright config files: 1 for your local and the other for Bitbucket, that way you wouldn't need to do any ternary logic in your config.
Can you try running the Playwright reporter by itself on Bitbucket and see what results you get?
And then try re-running it using just the normal html reporter and then see what results you get?

@ryanrosello-og
I tried to divide configs and added one for CI specifically using:
retries: 2,
workers: 1,
Also tried to run on CI same config with html report only - same wrong result
What i do find weird is - it does retry on passed tests as well (and i suspect it calculates these retries for some reason and sending that count to slack

So as far as i see failed test cases count is shown correctly in slack however passed and skipped - they are not. So maybe you guys can support it in your code where retries for same test case will be counted as 1 for all type of results?

@ryanrosello-og i actually tried to run plain playwright-slack-report without any custom reports locally with 2 retries and it gave me wrong calculation for skipped and passed when there is a failure present (check point 2)
If there are no failures - it did give correct count (check point 1)

In terms of tests - i do have describe/test structure, nothing super complicated being honest

Thanks for reporting @Alona-T ! I am experiencing the same @ryanrosello-og . The retries are messing up the counting for skipped.

@Alona-T , struggling to reproduce this.

This is my playwright config:
import type { PlaywrightTestConfig } from "@playwright/test";
import { devices } from "@playwright/test";

const config: PlaywrightTestConfig = {
  testDir: "./tests",
  timeout: 30 * 1000,
  expect: {
    timeout: 5000,
  },
  fullyParallel: true,
  forbidOnly: !!process.env.CI,
  retries: 2,
  workers: 1,
  reporter: [
    ["dot"],
    [
      "./node_modules/playwright-slack-report/dist/src/SlackReporter.js",
      {
        channels: ["chan-chan"],
        sendResults: "always", // "always" , "on-failure", "off",
        meta: [
          {
            key: "Branch",
            value: "feature/test-slack-report",
          },
          {
            key: "Build",
            value: "v1.08-RC_2331150.033",
          },
        ],
      },
    ],
    ["html"],
  ],
  use: {
    actionTimeout: 0,
    trace: "on-first-retry",
    screenshot: "only-on-failure",
    video: "retain-on-failure",
  },
  projects: [
    {
      name: "chromium",
      use: {
        ...devices["Desktop Chrome"],
      },
    },
  ],
};

export default config;

Can you tell me a little bit more about your project?

Are you using projects in the playwright config?
Are you using the page supplied by playwright or are you handling the creation of browsers yourself?
Are you using serial mode within your tests?
How many workers are you using?

@ryanrosello-og
Are you using projects in the playwright config?

i am not sure i have any as i do use similar config structure as you shared

Are you using the page supplied by playwright or are you handling the creation of browsers yourself?

this particular error was in API project (no browsers involved)

Are you using serial mode within your tests?

Yes we do use it
Example:
test.describe.serial('Test name', () => {} or

test.describe.configure({ mode: "serial" }); test.describe.serial(POST /execute for unauthed user @coins, () => {}
How many workers are you using?

1 worker

I believe this will be fixed by https://github.com/ryanrosello-og/playwright-slack-report/pull/54
Please try v1.1.24 Release @miguelofbc, @Alona-T


Fixed issues with shebang

Please answer these questions before submitting a pull request

Why submit this pull request?

[+ ] Bug fix

[ ] New feature provided

[ ] Improve performance

Related issues

Bug fix

Bug description.
Fixed issues with the placement/missing shebang
How to fix?
Add the shebang to the respective files

New feature or improvement

Describe the details and related test reports.

This is blocked as same as #5592. You need to resolve the code style check mechanism to make CI passed.


restric SciMLBase version

<EMAIL_ADDRESS>removes the odefunction.syms which we use quite heavily. Therefore I suggest to restrict SciMLBase to lower versions in a patch release until we can resolve this.

ci fail unrelated, probably because of changes in the random seeds.


Update guest-experience.md

https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/3060
Added capability

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@LanaChin PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


How do i unban my 7 year old?

My 7 year old has got himself banned from oblique server for what he thought was just a battle.
How can I get him unbanned as he had no idea he was in the wrong as he can't read or write obviously after explaining to him why he was banned he now understand he can't "battle".

Almost had me fooled with the act here, but I do thorough checks on all banned personnel and look what we have here:

Your 7 year old seems to have exceptional english skills. Even if this did happen to be a 7 year old, and someone else had taken over when they wrote that sentence, doesn't hide the fact they knew full well what they were doing, since literally this LSFH11 player had joined the server, all they did was PVP people at spawn. Appeal has been declined. Hopefully you can explain that to the 7 year old.


fix: update redux saga guide article

Write introductory information about Redux saga

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.


Radiogroup for subgroups

Hi, firts of all thank you very much for this excelent work, my proposal is, if possible, create mutually exclusive subgroups of layers, that is, subgroups with radiogroups
Example:
var overlayLayers = {
label: 'Group 1',
children: [
  {  label: 'SubGroup 1',
      radioGroup: 'bc',
      children: [
         {  label: 'Layer 101',
            layer: lay101-example
         },
         ...
   },
  {  label: 'SubGroup 2',
      radioGroup: 'bc',
      children: [
         {  label: 'Layer 201',
            layer: lay202-example
         },
         ...
   }
 ]
};

I hope i have explained myself, i know my english is not good but im working on it

That would be very nice, and very useful !


Include filename in mardown-it objects

I'd like to add a custom rule to check for broken links and orphaned pages in my Markdown documents. I've been using Markdown in a personal knowledgebase, and have a lot of relative paths I want to maintain.
This would be simple with the customRules API, but it doesn't provide the filename in the line-annotated markdown-it objects. I believe this could be added by modifying this call in lintFile() and the called function, lintContent() to accept the filename as an argument. I can submit a PR if this makes sense.

Sure! If you want to start with a sketch, I’d be happy to review that to be sure we are on the same page.

Thinking about this, I propose:

Add it to params
Call it file
Pass it exactly as provided to options.files
Use null when not available (strings)
Update the README and CustomRules docs
Update the tests

Update: The value of file should be the same path already used to open it successfully. I don’t think we should commit to normalizing it.

(Don't worry about a PR - I did this just now and will push it tomorrow after reviewing the changes.)


[LG] Multi Language supports loading lg file dynamically

Is your feature request related to a problem? Please describe.
I split logic and text in two lg files like this:
Activity.lg

# Test
[Activity
    Text = {Test.Text()}
    InputHint = expectingInput
]

Text.lg

# Test.Text
- balabala

And a top-level file import all the lg files:
All.lg

[import](Activity.lg)
[import](Text.lg)

I use this top-level file as an 'entry':
this.UseResourceExplorer(resourceExplorer);
this.UseLanguageGeneration(resourceExplorer, "All.lg");

Now I hope Text.lg can support multi language, for example Text.zh-cn.lg. So that when I talk to my bot in Chinese, the bot will reply to me in Chinese. It can also save the time needed to translate lg files into different language(We only need to translate Text lg file).
Text.zh-cn.lg

# Test.Text
- 你好

But this doesn't work.
Describe alternatives you've considered
This will work but not very convenient: Add multi-lang All.lg file
All.zh-cn.lg

[import](Activity.lg)
[import](Text.zh-cn.lg)

This just like assembling a project. I should write this 'config file' to tell LG what files I used,  for all languages I support.
It seems that multi-lang in LG can load 'top-level' file dynamically(In this example it's All.lg). But I hope that I don't need to do this. And I hope that when I talk in Chinese, it can find Text.lg file in Chinese dynamically.

We need to clean up and document multi-lingual support outside of declarative.
@boydc2014  - let's discuss this in our next sync.

We need to clean up and document multi-lingual support outside of declarative.
@boydc2014 - let's discuss this in our next sync.

Yes, definitely doc and samples should be updated. But this user is actually reporting one issue, that our "Multi-languageGenerator" only support dynamically choose lg file at top level. Which mean it can choose from "all.en_us.lg" and "all.zh_cn.lg", but if "all.en_us.lg" import "text.lg", it will not resolve to "text.en_us.lg".

Presumed fixed via #2800


[ADD ME TO THE ORGANIZATION]

Abhishek Shukla:
India:
Ai,Ml Devops,web3:
Discord username(optional):-
Why do you want to join?

I want to join because learn and contribute to opensource and give back to community.

You can also join our Discord community here
Feel free to check out other cool repositories of the DevsInTech Community here.

@Shukla007 Thanks for your interest. Invitations have been sent to you. Kindly accept it and make your membership public.


fix(deps): update default logs agent to 1.3.1

Description
Update default logs agent to 1.3.1. Renovate should be doing this, but it did not (I may need to add a special renovate rule / config since the helm repo is authenticated)
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

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


Create missing_ranges.py

Hii,Sir,i enjoyed your repo a lot,it was a gr8  experience learning new stuffs ,I have added a new problem plz see to it, and plz accept my pull request,it will help a lot for hacktoberfest,happy coding sir,,,

Hii sir ,added a double dimension array famous problem to your repo.Hope you like it,plz accept my pull request if so.


PDPDEVTOOL-4548: Change SDF project to SuiteCloud project

Only for NSN now. NSX will be updated in a later date.


Rename VersionInfo to Version

So there are my two suggestions for this issue:

Overload the constructor with __init__(self, version: str)
Rename VersionInfo to Version

Originally posted by @tlaferriere in https://github.com/python-semver/python-semver/issues/258#issuecomment-648810597
Just addressing this explicitly

Thanks for opening this. :+1:
I think, this issue is closely related to #303. In this issue, I present the idea of an (overloaded) semver.version function which acts as a wrapper for all different types. So I guess, we have a third option here which we should discuss. :wink:
Regardless of the constructor/initializer or the semver.version function, renaming VersionInfo to Version is okay to me as long as we have an alias (something like VersionInfo = Version which also outputs a deprecation warning when used).


Getting null Webhook Payload for Unsubscribe Action

Describe the bug
After activating a subscription, when I cancel the subscription from the portal, the webhook is getting called, but the payload is empty. The application log
To Reproduce
Steps to reproduce the behavior:

Subscribe to SaaS product
Click on link to Configure Account Now
Activate subscription from accelerator portal
Activate subscription via admin portal
Cancel subscription from Azure portal as customer

Expected behavior
The Application log should have a record of the Unsubscribe Webhook action, and the subscription should show as Unsubscribed in the admin portal. The only entries I see in the Application Log are: "The Azure Webhook Triggered." These entries should be followed by the webhook payload JSON.
Screenshots

Desktop (please complete the following information):

OS: Mac OS
Browser Chrome

This appears to be related to PR #160 - converting Application Log requests to async. It causes the portal app to crash whenever a webhook call is received, with this stack trace.
Microsoft.EntityFrameworkCore.DbContext.CheckDisposed
Microsoft.EntityFrameworkCore.DbContext.get_DbContextDependencies
Microsoft.EntityFrameworkCore.DbContext+d__54.MoveNext
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification
System.Runtime.CompilerServices.TaskAwaiter`1[[System.Int32 System.Private.CoreLib]].GetResult
Microsoft.Marketplace.SaaS.SDK.Services.Services.ApplicationLogService+d__2.MoveNext
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification
System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult
Microsoft.Marketplace.SaasKit.Client.Controllers.WebHook.AzureWebhookController+d__8.MoveNext
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw
System.Threading.Tasks.Task+<>c.b__139_1
System.Threading.QueueUserWorkItemCallback+<>c.<.cctor>b__6_0
System.Threading.ExecutionContext.RunForThreadPoolUnsafe[[System.__Canon System.Private.CoreLib]]
System.Threading.QueueUserWorkItemCallback.Execute
System.Threading.ThreadPoolWorkQueue.Dispatch
System.Threading._ThreadPoolWaitCallback.PerformWaitCallback


[WIP] [SPARK-38060] [SQL] Respect allowNonNumericNumbers when parsing quoted NaN and Infinity values in JSON reader

Signed-off-by: Andy Grove<EMAIL_ADDRESS>
What changes were proposed in this pull request?
When parsing JSON unquoted NaN and Infinityvalues for floating-point columns we get the expected behavior as shown below where valid values are returned when the parsing option allowNonNumericNumbers is enabled and null otherwise.

Value
allowNonNumericNumbers=true
allowNonNumericNumbers=false

NaN
Double.NaN
null

+INF
Double.PositiveInfinity
null

+Infinity
Double.PositiveInfinity
null

Infinity
Double.PositiveInfinity
null

-INF
Double.NegativeInfinity
null

-Infinity
Double.NegativeInfinity
null

However, when these values are quoted we get the following unexpected behavior due to a different code path being used that is inconsistent with Jackson's parsing and that ignores the allowNonNumericNumbers parser option.

Value
allowNonNumericNumbers=true
allowNonNumericNumbers=false

"NaN"
Double.NaN
Double.NaN

"+INF"
null
null

"+Infinity"
null
null

"Infinity"
Double.PositiveInfinity
Double.PositiveInfinity

"-INF"
null
null

"-Infinity"
Double.NegativeInfinity
Double.NegativeInfinity

This PR updates the code path that handles quoted non-numeric numbers to make it consistent with the path that handles the unquoted values.
Why are the changes needed?

The current behavior does not match the documented behavior in https://spark.apache.org/docs/latest/sql-data-sources-json.html
Does this PR introduce any user-facing change?

Yes, parsing of quoted NaN and Infinity values will now be consistent with the unquoted versions.
How was this patch tested?

Unit tests are updated.

Can one of the admins verify this patch?

Dumb questions as I just don't know this code path -- would we parse "1.0" as a number or reject it for being a string? and you're saying that Jackson would parse "NaN" as NaN and not a string? It feels weird to parse strings that aren't even numbers as numbers, even when the option to do so is set, but if that is consistent with other behavior I could see it.

Dumb questions as I just don't know this code path -- would we parse "1.0" as a number or reject it for being a string? and you're saying that Jackson would parse "NaN" as NaN and not a string? It feels weird to parse strings that aren't even numbers as numbers, even when the option to do so is set, but if that is consistent with other behavior I could see it.

Jackson will parse valid JSON numbers as either integers or floats. It will parse strings as strings and does not try to interpret them. Jackson has special behavior for tokens such as NaN and Infinity which are not valid JSON values (JSON does not support non-numeric numbers at all). Jackson will not attempt to interpret "NaN" and would just return a string.
For some reason, the code we have today in Spark's JacksonParser will look at any returned strings and will parse them if they are NaN, Infinity or -Infinity (but not the other special values that Jackson supports, such as +INF). It will not attempt to parse strings that contain actual numeric values like "1.0". This secondary parsing seems like a bad idea overall IMO. Users could get similar behavior by specifying that the column is StringType when reading and then performing an explicit CAST to a floating-point type and it would support reading numbers and not-numbers regardless of whether they are JSON strings or JSON numbers.
If we have the option of removing this code (or putting it behind a configuration option) then I would be in favor of that. If not, then I would like it to support the same set of not-a-number strings as Jackson and I would like it to respect the allowNonNumericNumbers option.

I see, so the most consistent behavior would be to not allow "NaN", whether allowing non-numeric inputs to be parsed as numbers or not?
So a raw literal like NaN is not handled by this section of code in Spark, but by Jackson?
Well in any event, I suppose it's a little better to be permissive in this narrow case, to achieve a little more consistency, rather than 'break' existing functionality.
allowNonNumericNumbers is on by default, so adding the additional constraint here wouldn't affect most paths. If someone had explicitly disallowed it, now Spark would parse things like "NaN" as NaN. It could be worth a note in core-migration-guide.md for good measure.

I see, so the most consistent behavior would be to not allow "NaN", whether allowing non-numeric inputs to be parsed as numbers or not?

Yes.

So a raw literal like NaN is not handled by this section of code in Spark, but by Jackson?

That is correct.

Well in any event, I suppose it's a little better to be permissive in this narrow case, to achieve a little more consistency, rather than 'break' existing functionality.

Yes, I agree.

allowNonNumericNumbers is on by default, so adding the additional constraint here wouldn't affect most paths. If someone had explicitly disallowed it, now Spark would parse things like "NaN" as NaN. It could be worth a note in core-migration-guide.md for good measure.

Ok, I will add a note to the migration guide in this PR later today.
Thanks for the review so far.

i'm fine with this change.

Merged to master


Body can't be used as scroll-container

Hi,
what is the reason for the following if-else-block?
// define scroll context
if (el === d.body) {
  scrollable = w;
  startX = w.scrollX || w.pageXOffset;
  startY = w.scrollY || w.pageYOffset;
  method = original.scroll;
} else {
  scrollable = el;
  startX = el.scrollLeft;
  startY = el.scrollTop;
  method = scrollElement;
}

If i'm not totally wrong it prevents us from using the body as scroll container. But i need the body to be the scroll-container because i dynamically remove some DOM elements while runtime what leads to a flickering behaviour in safari / edge when document is the outer scrolling container. Using an inner div as scroll-container doesn't work either because this breaks the mobile browsers feature of hiding the url-bar on scroll... using the body is the only possibility :)
So... is there a good reason for always using the window as scroll container instead of the body (like the code above does) or is it save to remove this if-block?

I guess we crawl up the DOM tree to find the closest scrollable parent and we imperatively sotp at body, so we use this element as signal to whether we need to rely on scrollX and scrollY or scrollLeft and scrollTop as initial starting points. So, no it is not safe, you need to be aware whether you are scrolling the window or an element that is scrollable.
We could stop at documentElement but it doesn't change much, at the end we need to use the window's default scroll method. The animation mechanism needs the right starting point as it ignores whether you are scrolling in a container or the window, it just tweens values using requestAnimationFrame.
If you have a case where body is scrollable, but fixated in viewport metrics, I would like to see an example and how it behaves on browsers that already implemented the spec, but it could be an edge case for sure.

Here is an example https://jsfiddle.net/wpjz7afu/
Using the polyfill would lead to the button doing nothing because "body" would replaced by "window" and on that level there is nothing to scroll.

Oh ok, now I see it here I'm forcing the polyfill for comparison: https://jsfiddle.net/cqfgvn4b/2/
The error though is not on that condition, but on the fact that we stop at body on the scrollable parent instead of using documentElement, that condition needs to stay there but point to documentElement too.
I'll try to wrap a fix this week 🙏 should be easy.

Wouldn't be everything that has to be changed to replace the three occurrences of e.body with e.documentElement?

Sorry... Closed by accident.


chore(deps): update dependency org.springframework:spring-orm to 5.1.4.release

This PR contains the following updates:

Package
Change

org.springframework:spring-orm
4.3.21.RELEASE -> 5.1.4.RELEASE

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR is stale, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will now ignore this update (5.1.4.RELEASE). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


Help me with the real-time graph

Please, a simple example with updating the signal chart

https://scottplot.net/faq/live-data/


Better behavior with Cluster Autoscaler

Is your feature request related to a problem? Please describe.
I'm testing ARC with cluster autoscaler (on GKE).  I add the annotation safe-to-evict:true for the runners.
Occasionally cluster autoscaler reschedules the pod that is running a workflow so the workflow remains in limbo til it fails.
This happens very rarely but enough to warrant not using it.
Describe the solution you'd like
I wonder if we can toggle the safe-to-evict:true annotation when the runner is processing a job. Set it to false when it's busy, and true when it's not.
Describe alternatives you've considered
I consider not setting safe-to-evict:true annotation at all. This will not reschedule the pods but it's less than accurate node autoscaling.

@GoldenMouse Thanks for raising this up!

Occasionally cluster autoscaler reschedules the pod that is running a workflow

This is the most interesting part to me. With today's ARC, a runner pod and its runner container should terminate gracefully as long as there's enough time to do so.
How long was your GitHub Actions workflow job got stuck due to this issue running? 1min, 20min, or hours?

It waited for 15m and times out (jobs usualy takes 2mins).

apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
  name: sweetspot-runner
spec:
  template:
    metadata:
      annotations:
        "cluster-autoscaler.kubernetes.io/safe-to-evict": "true"
    spec:
      organization: sweetspot
      # repository: sweetspot/helm-harness-poc
      #dockerdWithinRunnerContainer: true
      #dockerEnabled: false
      group: Default
      labels:
        - arc
        - sweetspot
      resources:
        requests:
          cpu: 1
          memory: "4Gi"
          # ephemeral-storage: 10Gi
---

---
apiVersion: actions.summerwind.dev/v1alpha1
kind: HorizontalRunnerAutoscaler
metadata:
  name: sweetspot-runner-autoscaler
spec:
  scaleDownDelaySecondsAfterScaleOut: 300
  minReplicas: 1
  maxReplicas: 100
  scaleTargetRef:
    name: sweetspot-runner
    # Uncomment the below in case the target is not RunnerDeployment but RunnerSet
    #kind: RunnerSet
  scaleUpTriggers:
    - githubEvent:
        workflowJob: {}
      duration: "5m"
      amount: 2

I'm running with a 0 pdb to avoid unnecessary evitcs.
i.e.:
apiVersion: policy/v1
kind: PodDisruptionBudget
metadata:
  name: runner-16-ramdisk
spec:
  maxUnavailable: 0
  selector:
    matchLabels:
      runner-deployment-name: runner-16-ramdisk

The runners surely wait to finish handling the job, but they will be given only so much time.
That however is configurable in kubernetes (terminationGracePeriodSeconds), one can configure how much time the pod gets to terminate by itself before kubernetes will force kill it.
I've ran workloads with terminationGracePeriodSeconds up to half an hour, with no issues.
So if that was configurable (maybe it already is?) it would be a good extension to help OPs issue.
Only concern I'd have is if moving pods around doesn't introduce possible new race condition (scenarios). That would be the risk :)

it looks like terminationGracePeriodSeconds can already be configured.
@GoldenMouse can you try setting this to about the longest running job that you have?
then the pod should get the chance to finish the job and terminate gracefully

Possibly related: https://github.com/actions-runner-controller/actions-runner-controller/issues/1535

So the possible cause of this might be that our runner pod finalizer doesn't prevent SIGTERM on actions/runner and dind running within respective containers of a runner pod.
If CA or any other operator tried to terminated the pod before the node shutdown/cluster scale-in, it will terminate the important processes anyway before the runner finishes it's job.
To address it, we might need another entrypoint that handles SIGTERM gracefully.

@mumoshu That's awesome. Sorry for the late response. I've handed our Runners project off to another team. I'll relay it to them so they can try it out.

We're still working on https://github.com/actions-runner-controller/actions-runner-controller/pull/1759. It would be great if you could give it a try by building your own ARC runner image from the branch, and leave any feedback!

we currently have the reverse problem. We don't have safe to evict set and node won't scale down because it claims pods aren't owned by a controller.
Is there a way to "certify" the controller or is there a reason a RunnerDeployment doesn't create a Deployment as it's resulting object?
if this is too off topic should I create an issue for this or is it just a known problem and safe-to-evict is the way to go?

is there a reason a RunnerDeployment doesn't create a Deployment as it's resulting object?

That's because we wanted full control over when to create/delete the pod, which is only possible via validatingwebhook or very complex via validatingwebhook when we controlled runner pods "indirectly" via deployments.

We don't have safe to evict set and node won't scale down because it claims pods aren't owned by a controller.

@snuggie12 I thought we already set an owner reference on every runner pod.. didn't we? If that's not about owner referencing, could you clarify what's needed to mark it as owned by a controller?

We don't have safe to evict set and node won't scale down because it claims pods aren't owned by a controller.

@snuggie12 I thought we already set an owner reference on every runner pod.. didn't we? If that's not about owner referencing, could you clarify what's needed to mark it as owned by a controller?

@mumoshu I presume the message either means there is something that needs done for your controller to be considered a controller (some form of registration or some piece of metadata which makes it more "official",) or when the log says "controller" it only means core kubernetes ones like a replica set controller and no custom controllers count.

@snuggie12 I've read CA code for you. Apparently you only need to add the safe-to-evict annotation on the pod to evictable according to https://github.com/kubernetes/autoscaler/blob/b5e2dcade06bcbf01f2b2b11c79deb0ab81bd1fa/cluster-autoscaler/utils/drain/drain.go#L209

Ah, we've already documented it
https://github.com/actions-runner-controller/actions-runner-controller/blob/40eec3c7834d17fa7a76c66d82453941d577dca3/docs/detailed-docs.md?plain=1#L1079

@mumoshu Yeah, I know we can add that but then you're back to the problem of this ticket where things are turning off mid run.
BTW, I also read drain.go and I feel like it's confirmed that when they say "controller" they mean it has to be a core controller like a replicaset controller. I don't think there's a way to say your controller is a "known good" controller.

you're back to the problem of this ticket where things are turning off mid run

Why? It looks like any pod with the safe-to-evcit annotation can be terminated by CA like other pods that are managed by a controller that is known to CA.

I don't think there's a way to say your controller is a "known good" controller.

Yeah, sounds true!


Long paths cause TransferUtility.Upload to throw ArgumentException

The exception message is The file indicated by the FilePath property does not exist!.
A quick inspection revealed it's caused by a validation in TransferUtility.cs#L372  that fails because it uses FileInfo, which expressly does not support long paths (those longer than MAX_PATH).
I'm not sure whether this is a regression or if it was never supported - didn't go thru all the history to check.

It appears that long paths were never supported. This is an issue with FileInfo, so I'm not sure if/when there would be a fix or a workaround available.

Hmm, I suspected that. I'd suggest a fix using native APIs like CreateFile (and unicode counterparts), which support long paths (disregarding portability for the sake of argument). Fixing this way may require an extensive effort, but someone already worked our all (or most) details in the past - see ZetaLongPaths - it has almost drop-in replacements for FileInfo and DirectoryInfo without such restriction.

If it's worth anything, leaving PCL out, a (very) quick impact check on the S3/Custom/ code reveals the following:

Model/_bcl/PutObjectRequest.bcl.cs: Uses System.IO.FileStream and System.IO.Path;
Model/_bcl/UploadPartRequest.bcl.cs: Uses System.IO.FileStream and System.IO.Path;
Model/_bcl45/GetObjectResponse.cs: Uses System.IO.FileStream, System.IO.FileInfo and System.IO.File (for Exists);
Model/GetObjectResponse.cs: Uses System.IO.FileStream, System.IO.File (for Exists) and System.IO.FileInfo;
Transfer/_bcl35/TransferUtility.bcl35.cs: Uses System.IO.File (for Exists);
Transfer/Internal/_async/DownloadCommand.async.cs: Uses System.IO.FileStream and System.IO.File (for Exists);
Transfer/Internal/_bcl/DownloadDirectoryCommand.bcl.cs: Uses System.IO.File (for Exists);
Transfer/Internal/_bcl35/DownloadCommand.bcl35.cs: Uses System.IO.FileStream and System.IO.File (for Exists);
Transfer/Internal/_bcl35/UploadDirectoryCommand.bcl35.cs: Uses System.IO.Directory (for GetFiles) and System.IO.FileInfo;
Transfer/Internal/_bcl45/UploadDirectoryCommand.async.bcl45.cs: : Uses System.IO.Directory (for GetFiles) and System.IO.FileInfo (to retrieve the file length);
Transfer/Internal/DownloadCommand.cs: Uses System.IO.File (for Exists) and System.IO.FileInfo;
Transfer/TransferUtility.cs: Uses System.IO.File (for Exists);
Transfer/TransferUtilityUploadRequest.cs: Uses System.IO.FileInfo (haven't checked but seems to use only the file length);
Util/_bcl/AmazonS3Util.Operations.cs: Uses System.IO.File (for OpenRead);

I believe the only thing ZetaLongPaths doesn't cover is the FileStream.

I agree that the path limit is frustrating. Given the complexity of all the platforms the .NET SDK is supported on and the amount of effort it would take to implement this change, it is not high on our priority list. If other developers disagree and feel this is higher priority than other feature work for the SDK, then please +1 this issue.

Looks like .NET >= 4.6.2 on Windows 10 supports long paths natively, but it is not enabled by default. You need to change a local group policy - https://blogs.msdn.microsoft.com/jeremykuhne/2016/07/30/net-4-6-2-and-long-paths-on-windows-10/ - Anyway, it's good to see the direction .NET is taking.


Additional help access

A user recommended a help button per area where there is specific help.  For instance, there is a page or section of help relevant to each panel.  If the info icon was a ?, clicking it would go to the relevant help.

Good idea. My users always missed that there was help.


Show latest updates across all collectives

It would be good to have a page to list all the latest updates across the platform but also within a host / collection of collectives (e.g. https://opencollective.com/opensource, https://opencollective.com/brusselstogether)
This will also incentivize people to post updates has it will give their collective more visibility.
This could be a section like "Next events" that we have today on the page of a collective.

I agree, this is kind of missing. As a logged-in user you click on the OC logo, go to home and then you're asked to join the movement - just like any other anonymous, first time visitor.

a simple activity-stream that only displays latest updates from the collectives you're backing, maybe with filters for transactions, updates, events in a second step
the same activity-stream on every collective page, but with updates from this collective only, obviously


fix(dashboard): allow resetting custom domains

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (a291da6) 86.84% compared to head (f0deffa) 86.84%.

:exclamation: Current head f0deffa differs from pull request most recent head 8df84d7. Consider uploading reports for the commit 8df84d7 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2331   +/-   ##
=======================================
  Coverage   86.84%   86.84%
=======================================
  Files          85       85
  Lines        9352     9352
  Branches      495      495
=======================================
  Hits         8122     8122
  Misses       1230     1230

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


machine attribute in both machine_execute and machine_file resources should be required.

I declared a machine_execute block accidentally without specifying machine attribute. I made a bad assumption that the attribute was :name_attribute.
Anyway it failed when trying to connect to the machine but exception thrown was not in spot I expected.
NoMethodError
-------------
undefined method `split' for nil:NilClass
https://github.com/chef/chef-provisioning/blob/63e88632122375476eb40a8a7a2db1e8b6d6b876/lib/chef/provisioning.rb#L46
Since my resources name attribute for resource is nil this call ended up setting machine_spec to object containing list of all machine managed entries. Since machine_spec in this case did not contain driver_url you hit the exception.
Suffice to say this confused me enough to have to walk-through the code. With the current implementation of machine_execute and machine_file resources I don't see how they can work without machine attribute declared. If we made the attribute required I believe it would result in error message which shows root cause of problem.

Closed by merging https://github.com/chef/chef-provisioning/pull/542


Split SA1600, SA1601 and SA1602 into three rules each

For public, internal and private members. Added code to resolve visibility correctly in scope of parent type.
Updated tests.

This is a first pass at trying to resolve #829 and #789. I'm sure this will generate some discussion, but hopefully it's a step in the right direction.
SA1600 has a completely new set of tests, and uses a crazy-new-test-code-generator.
There are, of necessity, new diagnostic IDs. These have the suffices "In" and "Pr".

I'd be interested to get some feedback on this. I know the test code is a bit weird and wonderful (OK: maybe just weird), but I think the logic changes to the rules themselves make the doc rules more useful—especially the changes to take into account the effective visibility of elements based on the visibility of their parent types.

I just did a quick review of the code and most of it looks good.
I do have an issue with the the way the tests are set up.
In my opinion the new setup has a serious issue with readability. I find it quite frustrating that I have to analyze each test case in detail to see what the intended test case is.
The new test cases will probably take slightly less time to code, but reviewing them and determining if they are correct has become a much more difficult job.

Besides that I also think that having a StyleCop (like) config file would be a much better option than having separate rules for public / internal / private.
I appreciate the effort to get things working right now, but I think in the long run the project would be better off with a config file mechanism.

@vweijsters - Thanks for taking a look. I'm happy to try to re-work the tests.
The comment about the settings file makes sense. I went this way after reading comments by @sharwell on #422. However, I can keep this in a private build for my own use (since the current versions of these rules throw up a lot of false positives for us) up until settings files have been implemented. Then it should be fairly easy to integrate those changes into this branch.

@oatkins I ran into a similar problem with SA1503 - I wanted some but not all of its behavior. We resolved this without configuration by proposing (#716, #717) and finally implementing (#861) two brand new StyleCop rules.
Suppose now that you want to split rule SA1600 into two categories (for simplifying the example): publicly-accessible members, and non-publicly-accessible ("internal") members. In this case you could propose a rule for either of these two. Ideally you would propose a rule for publicly accessible members, which means two things:

The new rule would be enabled by default. Users who suppressed SA1600 due to its scope would see new warnings, but only on publicly-accessible members. They would then have the option of disabling the new rule as well.
If the new rule is disabled, but SA1600 is enabled, the behavior of SA1600 wouldn't change at all.

If you break SA1600 into more than two categories, you will need to be very specific in your descriptions with respect to nested types and members.

@sharwell Thanks for the tips. I'm still not 100% clear on where to go with this, so I hope you'll excuse a couple more questions.
The StyleCop behaviour for SA160x is, by default (i.e. no settings file, no suppressions), to require comments on all elements, whether public, internal or private. This can be modified (relaxed) by two properties in the settings file: one to disable the requirement for documentation on private elements, and the other for internal elements.
Here are two alternatives that come to mind for how this could be handled with new rules (taking SA1600 as the example case):
Option 1

SA1600 functions as per the SC defaults, requiring documentation on all elements.
Three new rules, disabled by default, break out the results at the three accessibility levels.
It would never make sense to enable SA1600 and one or more of the new rules.
When configuration is supported later, the legacy SC configuration properties could be supported on SA1600 but ignored by the new rules.

Option 2

SA1600 functions as if a settings file had enabled it for public members only.
Two new rules add support for requiring comments on internal and private members.
The legacy SC behaviour would be obtained by enabling all the rules.
When configuration is supported later, the two new rules could respect the configuration properties too.

To my mind the second option is more straightforward because enabling all the rules wouldn't give duplicate diagnostic messages. However, the first option mirrors the legacy SC behaviour more precisely.
What do you think?

How about option 3: Give me a couple of days to get the configuration stuff working and go from there?

I would pick option 4:

SA1600 reports anything not reported by another rule. Similar to how SA1503 behaves today with respect to SA1519 and SA1520.
Two new rules, one for publicly-accessible signatures, and one for non-private but also non-public signatures.
All rules can be enabled by default without conflicts.

I'm not so sure about option 4 yet. There will be a large number of additional rules needed to support all scenarios, especially if we also want take into account the 'ignore for fields' setting.
The list below would be all rules that are needed:
SA1600, SA1600 public only, SA1600 internal only, SA1600 no fields, SA1600 public only - no fields, SA1600 internal only - no fields
SA1601, SA1601 public only, SA1601 internal only, SA1601 no fields, SA1601 public only - no fields, SA1601 internal only - no fields
SA1602, SA1602 public only, SA1602 internal only, SA1602 no fields, SA1602 public only - no fields, SA1602 internal only - no fields
(protected would be considered the same as public, as would public internal)
I would very much prefer to handle that with a settings file, instead of having to fill-in the correct puzzle in the rule set file.
The use case here is having settings that are the same for a number of different analyzers. We could solve that by creating individual analyzers to cover each setting, but I think we should not. I like the pattern that was implemented for SA1503, but this is a different case and therefore it warrants a different solution.

@sharwell I agree that there are definite benefits to avoiding reliance on config files where possible—though this probably won't be possible for, say, SA1636.
@vweijsters I completely agree with the comment,

protected would be considered the same as public, as would public internal.

though I suspect you intended to write protected internal in that last clause. This makes perfect sense from a documentation perspective, and makes it much easier to reason on the rules.
I don't see why fields should be excluded. Some APIs make extensive use of fields, e.g. WPF. StyleCop doesn't make such an exclusion.
@sharwell  I can't quite figure out the rationale behind "option 4." It seems to be the same as 2, but with SA1600 and one of the new rule proposals transposed.
It'll certainly be helpful for the rules to be mutually exclusive, but by the logic that, "SA1600 reports anything not reported by another rule" (which is logical) it seems as though SA1600 would end up being for private elements only. Since this is perhaps the least useful case (and least frequently enabled in legacy SC) it seems rather counter-intuitive.
Here is my (over-)simplified understanding of your two proposed new rules (again, treating protected and protected internal as public):

publicly-accessible elements, and
internal elements (i.e. non-public, non-private).

That leaves only "private" for the existing rule.
What am I missing? btw Sorry to be a pain with this. Just want to make sure I fully understand before making the changes.

@oatkins The option to exclude fields is present in StyleCop and definitely handy if you want private / internal stuff documented, except for the fields.

@oatkins Option 4 is about SA1600 reporting everything, unless the two new rules are enabled. In that case SA1600 will only report for the private stuff. It is a mechanism that we introduced recently to suppress duplicate messages. Have a look at the implementation of SA1503, SA1519 and SA1520 for details.

@vweijsters I disagree with your breakdown. In particular, we could get away with only the following additional rules:

Publicly-visible elements must be documented. This single rule covers the relevant subset of SA1600, SA1601, and SA1602. For discussion below, call this SA16X1.
Non-private elements must be documented. This single rule covers the relevant subset of SA1600, SA1601, and SA1602. For discussion below, call this SA16X2.

I do not believe fields need to receive special consideration outside of the above rules. If you don't want to document fields, enable SA16X1, SA16X2, and SA1401 (FieldsMustBePrivate). If you want to document public members only, enable SA16X1 and disable SA1600, SA1601, SA1602, and SA16X2.
As it turns out, SA16X1 as described above already exists - it's CS1591. This means only one additional rule is needed to enable all scenarios.

@sharwell Good analysis :smile:
The only minor case that is missing is when private fields should not be documented, but private methods / properties should be.
Another minor issue might be that CS1591 will only be enabled when the /doc compiler option is specified. It might be handy to still implement SA16X1 to work around that.

Great. The bit I hadn't grasped is the way SA160x changes its behaviour depending on whether the other rules are enabled. Ingenious. I will take a look at SA1503 before coding anything.

@vweijsters It's important to always enable the documentation compiler, otherwise all semantic information in documentation comments is ignored and refactoring operations in the IDE will do the wrong thing. This Best Practice is outside the scope of StyleCopAnalyzers. See dotnet/roslyn#2773 for more information.

The only minor case that is missing is when private fields should not be documented, but private methods / properties should be.

The reason I think we can ignore that now is this generally applies to cases where a private field simply backs a property. With auto-properties, and now read-only auto-properties, I think the demand for such a configuration option is rapidly dropping.

Hopefully this represents the latest suggestions on how these rules should function.
I've not done the work to change the tests so they don't depend on my little test code factory class yet. Also, the rules now change their behaviour depending on whether other rules are enabled. I can't see how to write tests that take that into account, so for now the tests only exercise the behaviour of the analyzers when all rules are enabled.

If we rely on CS1591, does this mean that we might end up with a code fix (#764) that works for private elements but not public ones? That would be a bit weird.

Code fixes can be applied to any warning identifier, including ones provided by the compiler. :smile:
Doesn't mean we won't provide our own ID for it. It's just one option.

Superseded by #1278.


Drop cap isn't dropping

I'm pretty sure the drop cap  is not as it should be. See below, I believe the second image is how it should be.

+1   @camelburrito , is it possible to get this working in the classic dropcap sense?
/cc @spacedino

@ericlindley-g - very easy to make the change (one of the opinionated templates already has this.)
What exists is per design - the question should be if we need to change the design

Thanks! Passing to @spacedino then for thoughts

so yea technically what we have is called an "Initial Cap" . We could rename it and then make another component "Drop Cap" that has the suggested behavior. @ericlindley-g @camelburrito what do you think?
thanks @derekcecillewis !

some articles for reference:
http://theworldsgreatestbook.com/book-design-part-6/
http://www.magazinedesigning.com/drop-caps-and-initial-letters/

Thanks @spacedino!  Clarifying the language here in the way you describe would be nice. If it's quick to just re-name this feature for now to "initial cap", that seems worth doing, so we don't get in a backward-compatibility bind later if we want to introduce a true drop cap.  Is the re-name from "drop cap" to "initial cap" low effort to do, @camelburrito ?


DSA <IP_ADDRESS> Introduction to Stacks-video

Description
Give an introduction and explain the working of stacks
Task

[ ] Documentation
[ ] Audio
[ ] Video

Note

While requesting the issue to be assigned, please mention your NAME & BATCH NUMBER.
Kindly refer to Issue Guidelines.
In case you see that the issue has already been assigned, try to request for a different task within the same issue.
Changes should be made inside the DSA/directory & DSA branch.
Name of the file should be same as the issue.
This issue is only for 'GWOC' contributors of 'DSA' Domain.

Domain
DSA
Type of Contribution
Video
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

I would like to work on this issue.
Uzma Firoz Khan
DSA
Batch 10
video.

@uzma024 sure


Change Redis cluster discovery to use CLUSTER_SHARDS API

Title: Change Redis cluster discovery to use CLUSTER_SHARDS API
Description:
Currently Envoy uses CLUSTER_SLOTS to fetch cluster topology from Redis. CLUSTER_SLOTS is deprecated in Redis 7.0. It is slower and less efficient than the new API, CLUSTER_SHARDS. We observed CLUSTER_SHARDS payload size to be 10x smaller than the CLUSTER_SLOTS payload for big redis cluster with 12k shards.
Redis doc also recommends using CLUSTER_SHARDS over CLUSTER_SLOTS
[optional Relevant Links:]

Any extra documentation required to understand the issue.

cc @mattklein123 @weisisea @msukalski

12k shards seems to be a very rare case scenario. Do you happen to know the size difference let say for a 10 shards cache?


NextJS app router support

Any plans to support the NextJS app router or an example of how to do so? I think the NextResponse and NextRequest objects are slightly different than the NextAPiResponse/NextAPIRequest objects, so the current iteration doesn't work without some messing around of the objects.

This should be fairly easy to set up once a fetch adapter is implemented #188

Forked and support added here:
https://github.com/Vercjames/package-trpc-swagger

I made https://www.npmjs.com/package/next-trpc-openapi

.npmjs.com/package/next-trpc-openapi

I tried using ur framework I am getting errors like
for each HTTP method instead.
⨯ No HTTP methods exported in 'C:\Users\Mehul\Desktop\testT3\demo4\src\app\api[...trpc]\route.ts'. Export a named export for each HTTP method.
GET /api/say-hello 405 in 40ms
⨯ Detected default export in 'C:\Users\Mehul\Desktop\testT3\demo4\src\app\api[...trpc]\route.ts'. Export a named export for each HTTP method instead.
⨯ No HTTP methods exported in 'C:\Users\Mehul\Desktop\testT3\demo4\src\app\api[...trpc]\route.ts'. Export a named export for each HTTP method.
`
[trpc]/route.ts
import { inferRouterContext } from "@trpc/server";
import { FetchCreateContextFn, FetchCreateContextFnOptions, fetchRequestHandler } from "@trpc/server/adapters/fetch";
import { type NextRequest } from "next/server";
import { env } from "~/env";
import { appRouter } from "~/server/api/root";
import { createTRPCContext } from "~/server/api/trpc";
import { db } from "~/server/db";
/**

This wraps the createTRPCContext helper and provides the required context for the tRPC API when
handling a HTTP request (e.g. when you make requests from Client Components).
*/
// export const createContext = async (req: NextRequest) => {
//   return createTRPCContext({
//     headers: req.headers,
//   });
// };
export const createContext: FetchCreateContextFn = async (opts: FetchCreateContextFnOptions) => {
const req = opts.req; // Access request object from options
// Your logic to create context
const headers = req.headers;

return { headers, db } as inferRouterContext; // Return the context object
};
const trpcApiRouteHandler = (req: Request) =>
fetchRequestHandler({
endpoint: "/api",
req,
// Your trpc router
router: appRouter,
// Your trpc createContext
createContext,
});
export {
trpcApiRouteHandler as DELETE,
trpcApiRouteHandler as GET,
trpcApiRouteHandler as HEAD,
trpcApiRouteHandler as PATCH,
trpcApiRouteHandler as POST,
trpcApiRouteHandler as PUT,
};
`
`
[...trpc]\route.ts
import { createOpenApiNextAppHandler } from "next-trpc-openapi";
import { appRouter } from "~/server/api/root";
import { createContext } from "../trpc/[trpc]/route";
const handler = createOpenApiNextAppHandler({
// Your trpc router
router: appRouter,
// Your trpc createContext
createContext : createContext,
responseMeta: undefined,
onError: undefined,
});
export default handler;
`
Can you help with this. Appreciate it. Thanks

Forked and support added here: https://github.com/Vercjames/package-trpc-swagger

Thanks!


IMPRO-436: Changes to CLIs for use in importing ancillaries

Adds ignore failure option to cube extract to return input if constraints are not matched; useful for e.g. applying realization extraction to a cube of unknown origin which could be determinitistc. Also modified topographic band generation CLIs to work on an x-y slice in case there are leading dimensions of time/realization etc.
Added bats tests to relevant CLIs.
Reference issue if exists
IMPRO-436
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

I've ran this code with the corresponding suite change and it works. I have not looked at the code or run the tests.


Enforce dtype = str for certain columns

Is your feature request related to a problem? Please describe.
https://gin.g-node.org/EL1000/lucid/issues/4#issuecomment-1908
Describe the solution you'd like
ChildProject should probably enforced dtype = str for certain columns.
Maybe dtype should be a new property of IndexColumn. This is already what has been done in the experimental #260 branch.

Actually, I think this move may have undesired side-effects. So, instead, I think we should use double quotes around IDs that we want to enforce as strings; This way, reading the metadata with pandas or through the package would yield identical results...


Fix crash when CurrentUICulture is Invariant

Fix issue: https://github.com/microsoft/Power-Fx/issues/1553
CultureInfo.CurrentUICulture.Name is empty (make locale empty) when CurrentUICulture is set to invariant. This makes TryGetErrorResource throw exception for empty locale.
This PR fix to set "en-US" default when CultureInfo.CurrentUICulture.Name is empty (invariant case).

✅ No public API change.


urlparse is not available in Python 3

I get the same error! For your information:

The urlparse module is renamed to urllib.parse in Python 3.


[ISSUE#4824] Support consumequeue, indexfile multiple directories storage  mode

ISSUE#4824
In RIP-7 https://github.com/apache/rocketmq/wiki/RIP-7-Multiple-Directories-Storage-Support, CommitLog File has supported multi-directories storage mode.
In this case, the commitlog can be stored on multiple disks, but consumequeue/index is still stored on one disk. However, the size of consumequeue/index can reach tens of Gbs, or even 100 Gbs, and the space used can't be easily ignored.
The current commitLog multipath needs to be configured independently, as follows:
storePathRootDir=/rmqstore1
storePathCommitLog=/rmqstore1/commitlog:/rmqstore2/commitlog

Therefore, I optimized the multi-path mode, and the improvements are as follows:
● Add multi-path mode for consumequeue.
● Add multi-path mode for indexfile.
● Optimize the method to get the commitlog path. It is not necessary to specify storePathCommitLog separately, and generate the storePathCommitLog from storePathRootDir.
● Add a Timed thread to check path capacity. When select store path, it will  try to avoid writing to a nearly full disk.
● Loading  metadata in multi-path. By default, the config file is stored in the first path, and the config bak file is stored in the second path. For example: storePathRootDir = /rmqstore0:/rmqstore1:/rmqstore2, config dir = /rmqstore0/config, config bak dir = /rmqstore1/config. At startup, scan all paths and load the config file from the latest path of dataversion.（This ensures that when the path is changed, the latest version can be loaded）
● Loading checkpoint file and abort file in multi-path. The loading path of the checkpoint file and the abort file is the same as that of the config file.
Chinese Version / 中文版本
在RIP-7 https://github.com/apache/rocketmq/wiki/RIP-7-Multiple-Directories-Storage-Support 当中，CommitLog文件已经支持了多文件路径的存储模式。
在这个情况下，commitLog可以被存储至多块磁盘当中，但是consumequeue和index依然存储于单盘上。然而consumequeue 和 index的文件大小也可能达到数十G或者上百G的大小。这样的存储空间并不能被忽略。
当前的commitLog的多路径需要被额外配置，如下所示：
storePathRootDir=/rmqstore1
storePathCommitLog=/rmqstore1/commitlog:/rmqstore2/commitlog

因此，我对多路径模式做了一定的优化，改进主要如下：
● consumequeue的存储增加多路径模式。
● indexfile的存储增加多路径模式。
● 优化commitlog获取文件路径的方式。不必要单独设置storePathCommitLog，storePathCommitLog可以从storePathRootDir根目录下直接生成。
● 增加一个定时线程检查路径的容量。当选择写入路径的时候，尽量避免写入至快满的磁盘中。
● 多路径下的元数据加载。默认将config文件夹写入至第1个路径中，config文件夹的bak文件写入至第2个路径。例如：storePathRootDir = /rmqstore0:/rmqstore1:/rmqstore2, config dir = /rmqstore0/config, config bak dir = /rmqstore1/config。在启动的时候，扫描所有路径，选择dataversion最新的所在路径作为初始加载路径。（这样能确保路径被更改时，能够从最新的路径下加载）
● 加载checkpoint文件和abort文件。checkpoint文件和abort文件的加载路径与config路径保持一致。

Codecov Report

Merging #4825 (f52caee) into develop (8dd07c8) will decrease coverage by 0.14%.
The diff coverage is 47.89%.

@@              Coverage Diff              @@
##             develop    #4825      +/-   ##
=============================================
- Coverage      44.94%   44.80%   -0.15%
- Complexity      7640     7687      +47
=============================================
  Files            980      982       +2
  Lines          68135    68563     +428
  Branches        9014     9075      +61
=============================================
+ Hits           30622    30717      +95
- Misses         33729    34006     +277
- Partials        3784     3840      +56

Impacted Files
Coverage Δ

...cketmq/broker/offset/LmqConsumerOffsetManager.java
74.35% <0.00%> (-1.96%)
:arrow_down:

...apache/rocketmq/store/timer/TimerMessageStore.java
53.96% <0.00%> (-0.22%)
:arrow_down:

...a/org/apache/rocketmq/broker/BrokerController.java
42.74% <8.10%> (-1.15%)
:arrow_down:

...apache/rocketmq/store/queue/BatchConsumeQueue.java
66.73% <9.09%> (-2.77%)
:arrow_down:

...apache/rocketmq/broker/BrokerPathConfigHelper.java
32.20% <18.18%> (-47.80%)
:arrow_down:

...cketmq/broker/offset/ConsumerOrderInfoManager.java
8.49% <33.33%> (+0.35%)
:arrow_up:

...c/main/java/org/apache/rocketmq/common/MixAll.java
43.90% <37.50%> (-0.70%)
:arrow_down:

...java/org/apache/rocketmq/common/ConfigManager.java
40.35% <40.90%> (-19.11%)
:arrow_down:

...e/rocketmq/store/config/StorePathConfigHelper.java
55.88% <52.17%> (-7.76%)
:arrow_down:

...org/apache/rocketmq/store/DefaultMessageStore.java
55.23% <54.43%> (-0.30%)
:arrow_down:

... and 62 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Coverage decreased (-0.09%) to 49.139% when pulling f52caeee88b8644cc3eba9f2062e210c5980fd7c on shengminw:multi-route into 8dd07c84697d3709f1f4bef5d78089b7d171b6cd on apache:develop.

Coverage decreased (-0.09%) to 49.139% when pulling f52caeee88b8644cc3eba9f2062e210c5980fd7c on shengminw:multi-route into 8dd07c84697d3709f1f4bef5d78089b7d171b6cd on apache:develop.

Can you fix the codes' conflicts firstly! @shengminw

Can you fix the codes' conflicts firstly! @shengminw

Sorry, this conflict was newly created when the develop branch was merged yesterday. I have fixed this conflict.

We intend to add CI pipelines for more platforms recently besides Linux, there are too many unit test could not pass in other platforms especially Windows.
It would be awesome if you could concern more about cross-platform issues.
By the way, if you don't have windows device for testing now, Github Action is a good choice. You can refer to https://github.com/aaron-ai/rocketmq/pull/1. I am pleased to provide support.

@aaron-ai thanks for your suggestion, I will check the compatible with windows platform.


Support for read-only attributes from *.edmx

I am attempting to create a poco from Microsoft Business Central, which is admittedly ODataV4 .  I am getting desperately close, except that some properties of entities in the Metadata is marked as read-only, but it comes into the generated poco with {get; set;} modifiers.  Is there a switch I am missing, or is this currently not supported?

Welcome @dawiehyman to Odata2Poco project
Can you show me sample of the xml schema of Odata v4 service that support readonly properties?
You mean the generated property could be:
         public string  Name {get;}   //rather than {get;set;}

A new package v3.3.0 is released that fix your issue.
The new features:
You can download:

Commandline console: o2pgen
Dotnet core tool
class library:

Try the commandline
o2pgen -r http://services.odata.org/V4/TripPinServiceRW -v

You find the class with ReadOnly properties has get only.
public partial class Airline
	{
	    public string AirlineCode {get;} //PrimaryKey not null ReadOnly
	    public string Name {get;set;} // not null
	}

Let me know if that version fixes your issue.


Removed obsolete columns from WNAI codes.csv

closes #175

@SimonGreenhill for this time of somewhat heavy restructuring of the repos, I turned off the branch protection. Will turn it on again for changes of content rather than data structure.


A question about Uint8Array operation

Version
Version: 3.0.0 (fea10bb7)
Test case
var foo = function () {
    let view = new Uint8Array([1,2,3]);
    view[''] = 0;
    print(view);
}
foo();

Execution steps
/.jsvu/jerry Testcase.js

Output
0,2,3

Expected behavior
1,2,3

Description
The correct output of the test case should be 1,2,3 while jerryscript yields 0,2,3 . we simply change the Uint8Array  view by view[''] = 0 ,which shouldn't have any impact on view, but jerryscript abnormally replace the first element of view with 0 ,I think it might be an issue of jerryscript.

This bug has been silently fixed in the latest version of JerrySctript.


Match doesn't allow bot to be addressed by name

match should still allow a bot to be addressed by name in a channel or by private message:

@bot ping should be possible, however even updating the regex does not fix, i.e.
match(/^@botname ping$/)

Example Code:
class PongBot < SlackRubyBot::Bot
  match('/ping$/') do |client, data, match|
    client.say(text: 'pong', channel: data.channel)
  end
end

PongBot.run

Have you tried something like match(/^(?<bot>\S*)[\s]*(?<expression>.*)$/)?

@dblock Thanks for the suggestion! That indeed worked.
I also noticed that using match do not populate the bot's help command. If using match and I want to provide syntax / all the commands for a bot -- will I need to manually do that?

I think so and we should document how to do that. Maybe take a look at how that's implemented and we can move the code from command to match so that it can document all commands?

@dblock I see. I have a long weekend coming up, so I'll give this a look and see if I can open an PR.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/815 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target.git

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

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-05-14-07-16-59 has been deleted or has been force pushed

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


Required file typo

Hello,
I was trying out the library, and noticed that there is a typo in index.js. Here it requires:
var SuffixTrie= require('./lib/CommonSubstrings.min');
But the file is named commonSubstrings.min (no capital C). You can also see it failing in the runkit link provided in the npm page.
Bye, Aldo.

Hi, Aldo,
Thanks a lot, I just fixed it.
Best, Hanwen


adds test for esri token generation from client credentials

This stubs the generate_token method only within this test. This brings the test coverage of Geocoder::Lookup::Esri closer to 100%.

...stubbing the create_token method on the ESRI lookup instance in the test (using instance_eval or something similar). This way we can avoid stubbing (and then not unstubbing) important methods in the code.

What I mean is something like this:
lookup.instance_eval do
  # redefine `create_token` to return a manually-created token
end

We don't want to touch any classes, only the particular instance we're testing.

Got it, fixed.

Looks good! Just two things and this is ready to merge:

Please rename the test to explain more precisely what is being tested (eg: test_token_generation_doesnt_overwrite_existing_config).
Squash into a single commit.

Thanks for your patience!

Thanks! It looks like you can squash the commits when you merge the PR. https://help.github.com/articles/about-pull-request-merge-squashing/


Support Ledger Hardaware

Support Ledger for Polkadot network on web3-onboard

[x] Connect with Ledger
[x] Sign transaction
[x] Add ledger for more network

[x] Kusama
[x] Polkadot Asset Hub
[x] Kusama Asset Hub

[ ] Connect Warning

Bug related to this feature in issue #2639


dependency updates

Codecov Report

Merging #208 (330043f) into main (bf1c5df) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #208   +/-   ##
=======================================
  Coverage   73.37%   73.37%
=======================================
  Files          30       30
  Lines        5040     5040
=======================================
  Hits         3698     3698
  Misses       1342     1342

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

I'll rebase this on main as soon as #207 is merged (when it's finished its test runs)
If this then passes the checks (up to 5 hours later now 🤦 ), could you then please merge this in your morning, @didierofrivia ?
We can then work on releasing… As this takes forever with since aarch


Does it support JavaFX?

Hello , first of all congratulations for your attempt , secondly very happy that found this repository today.
Is it supporting JavaFX or only Swing ?
I will be very glad to contribute on the Windows Development side . I have solid experience with JxBrowser and Java generally.

Journey is essentially a JCEF wrapper. If JCEF can't do it then Journey currently won't be able to. As far as I can tell it doesn't seem to be possible to use JavaFX with JCEF (see here).
If you're able to get JavaFX working with JCEF (but with changes), I would gladly help in getting those integrated with Journey. I don't use JavaFX so I don't currently know what issues exist with it.

Ah , JavaFX is Swing replacement.

JCEF has an open issue to provide JavaFX support, but there is a rather bad workaround that only works for offscreen rendering. By changing the GLCanvas in CefBrowserOsr to a GLJPanel, you can embed JCEF in JavaFX, with some keymapping issues.


Adding about version numbers not being mentioned in the enrichment recipe manuscript?

Can we add something about version numbers not being mentioned in the enrichment recipe manuscript?
I have checked and found that only 5/20 papers have mentioned version numbers of DAVID. 4 of them have used v6.8, 1 has used v6.7.
15 articles didn't mention anything...
In this line: "The reproducibility analysis was performed using the respective methodologies stated in the methods sections of the 20 articles using the DAVID version specified in the articles (March-May 2022) [23]."
I can add some more lines saying most of the articles did not state the version numbers but with article publishing timeline, there are chances of analysis being done using v6.7 or v6.8?

Yes I have added the relevant details to the methods and results thanks!

We attempted reproduction according to the methods described in the respective articles, with the limitation that we had to use DAVID v6.8 as v6.7 was no longer available.


Allow file downloads

Should be able to drag-and-drop from the file browser to my local machine.

Having an option to disable this downloading feature would be nice as well when it is added - I know for example the industry I'm in (financial data) wouldn't want this allowed.

@rubysown couldn't someone just copy and paste the file?

@nhooyr Yes. That might be easy for small files but not large ones. It's just a suggestion from a real-world scenario I've had to deal with, that's all.

need this function

https://github.com/microsoft/vscode/issues/93599 is tackling this.

Also somewhat related is #1292

In another similar server app, JupyterLab (https://jupyter.org/), you can drag and drop a file from local to the remote directory, but you can't drag a file from the remote to local (just like in code-server). However, JupyterLab does have an option to download a file from the right-click context menu. Not sure how they do that, but it would be nice if this was in vscode.

This seems to be in the works for the upstream side IIRC, might be worth a look.

@nhooyr It seems the VSCode 1.51 version has added the function:
https://code.visualstudio.com/updates/v1_51#_download-folders-edge-chrome

1.51.1 has been merged and this'll be released with 3.7.2.

Having an option to disable this downloading feature would be nice as well when it is added - I know for example the industry I'm in (financial data) wouldn't want this allowed.

i think need this feature

Having an option to disable this downloading feature would be nice as well when it is added . I know for example the industry I'm in (IT) wouldn't want this allowed. Improve code security

@lsc196 I opened https://github.com/cdr/code-server/issues/2426 to address this.


Patch golang related module in moby-buildx  for CVE-2021-44716

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[X] The toolchain has been rebuilt successfully (or no changes were made to it)
[X] The toolchain/worker package manifests are up-to-date
[X] Any updated packages successfully build (or no packages were changed)
[X] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[X] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[X] All package sources are available
[X] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[X] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[X] All source files have up-to-date hashes in the *.signatures.json files
[X] sudo make go-tidy-all and sudo make go-test-coverage pass
[X] Documentation has been updated to match any changes to the build system
[ ] Ready to merge

Summary

What does the PR accomplish, why was it needed?
Added a patch to the vendored module of moby-buildx to address CVE-2021-44716
Change Log

Address CVE-2021-44716 by patching vendored golang.org/x/net

Does this affect the toolchain?

NO
Associated issues

#xxxx

Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-2021-44716

Test Methodology

Pipeline build id: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=504394&view=results

Auto cherry-pick results:

main :white_check_mark: -> https://github.com/microsoft/CBL-Mariner/pull/7855

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=504553&view=results


refactor(blockifier): remove versioned runnable contract class

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2811  👈 (View in Graphite)
#2809
#2752
#2680 : 1 other dependent PR (#2681 )
#2679
#2678
#2668 : 1 other dependent PR (#2641 )
#2614
#2493
#2438
#2420 : 1 other dependent PR (#2421 )
#2467
#2466
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 22, 4:32 AM EST: A user merged this pull request with Graphite.


fix(types): router types fix for vue-router 3.3.3

Types of changes

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

Description
See :
https://github.com/nuxt/typescript/issues/374
https://github.com/nuxt/typescript/commit/b181e7aa49080e10a8bbea3d0818258f5ecf1e8e
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Codecov Report

Merging #7503 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #7503   +/-   ##
=======================================
  Coverage   70.18%   70.18%
=======================================
  Files          88       88
  Lines        3733     3733
  Branches     1015     1015
=======================================
  Hits         2620     2620
  Misses        905      905
  Partials      208      208

Flag
Coverage Δ

#unittests
70.18% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 245d32d...0be2d18. Read the comment docs.


Creating a discussion not working after RPC breaking change

Describe the bug
Creating a discussion involves looking up a transaction by its hash. Because of a breaking change in the RPC API this does not work anymore.
To Reproduce
Steps to reproduce the behavior:
This is reproduced by the discussions test case "should create a discussion when content matches"
Expected behavior
It should be able to find the transaction in the transaction hash.

The breaking change seem to have been introduced here
https://github.com/near/nearcore/pull/9648

There was a bug in read-rpc that did not implement the backwards compatibility for the tx API change. It was fixed yesterday: https://github.com/near/read-rpc/issues/212
If this issue still persists, let's re-open this ticket.