Custom loggers

Is it possible to collect logs from customer ILogger<T> instances?
How can we configure the level for each category? Is it possible to use a wildcard like MyNamespace.* to log everything under MyNamespace?

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

ID: 86aff194-f810-3c21-e322-cdda05dfc734
Version Independent ID: 0864707c-97a7-1166-1bd4-ef9ea212c64e
Content: Configure monitoring for Azure Functions
Content Source: articles/azure-functions/configure-monitoring.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

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

@fleed Thanks for reaching out.
Is it possible to collect logs from customer ILogger instances
Do you mean you want to get the logs in your azure function? If this is the case then it is not possible to access all logs using the ILogger in azure function.
How can we configure the level for each category
To configure the logging level for a specific category, you can use the categoryLevels property in the logger section of the host.json file as mentioned here
"logging": {
        "logLevel": {
            "default": "Information",
            "Function.HttpTrigger1": "Information",
            "Function.HttpTrigger2": "None",
            "System.Net.Http.HttpClient.default.ClientHandler" : "None",
            "Function.AccessTokenTimer" : "None"
        }
    }

Is it possible to use a wildcard like MyNamespace.* to log everything under MyNamespace
No you cannot use the wildcare or namespace. You can only define the category as documented here
Let me know if you have any further queries or concerns.

Thank you for clarification, @MayankBargali-MSFT
I think that this issue will extend the logging capabilities.


dapr should fail when operator connection fails | istio compatibility

In what area(s)?
/area runtime
/area operator

/area placement

/area docs

/area test-and-release

What version of Dapr?
1.6.0
Expected Behavior

The sidecar should fail when operator connections are not possible.
Actual Behavior
If the operator is not reachable during dapr startup, dapr retries 4 times, a warning is issued that components could not be loaded and thus nothing will happen afterwards. Even though the deployment is broken, all probes indicate otherwise. Instead the pod should fail directly after the connection fails.
In the logs we see:
time="2022-03-14T19:39:17.430742891Z" level=info msg="starting Dapr Runtime -- version 1.6.0 -- commit 4bb25fab444c4f1a1bf0ffd74293dbd4fdcea580" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:17.430776527Z" level=info msg="log level set to: debug" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:17.43090313Z" level=info msg="metrics server started on :9090/" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.metrics type=log ver=1.6.0
time="2022-03-14T19:39:17.431519074Z" level=info msg="loading default configuration" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:17.431552739Z" level=info msg="kubernetes mode configured" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:17.431559492Z" level=info msg="app id: api-saga" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:17.431711243Z" level=info msg="mTLS is disabled. Skipping certificate request and tls validation" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:17.43201628Z" level=info msg="Initialized name resolution to kubernetes" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:17.432616624Z" level=debug msg="loading component. name: kubernetes, type: secretstores.kubernetes/v1" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:17.433388308Z" level=info msg="loading components" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:17.433401222Z" level=info msg="component loaded. name: kubernetes, type: secretstores.kubernetes/v1" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:17.435713377Z" level=error msg="error from operator stream: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp <IP_ADDRESS>:80: connect: connection refused\"" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:18.128005545Z" level=error msg="error from operator stream: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp <IP_ADDRESS>:80: connect: connection refused\"" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:19.115913969Z" level=error msg="error from operator stream: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp <IP_ADDRESS>:80: connect: connection refused\"" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:19.840914126Z" level=error msg="error from operator stream: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp <IP_ADDRESS>:80: connect: connection refused\"" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:21.266058888Z" level=error msg="error from operator stream: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp <IP_ADDRESS>:80: connect: connection refused\"" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:22.467246592Z" level=warning msg="failed to load components: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp <IP_ADDRESS>:80: connect: connection refused\"" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:22.467320485Z" level=info msg="waiting for all outstanding components to be processed" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
time="2022-03-14T19:39:22.467335734Z" level=info msg="all outstanding components processed" app_id=api-saga instance=my-app-api-saga-v1-79f796db94-h597k scope=dapr.runtime type=log ver=1.6.0
...

The reason why the pod should fail is simply because a network connection is not possible to the operator to load the components -> The deployment cannot work.
Background
We run dapr with istio. The problem now occurs if dapr is started extremly fast and istio is taking a few more seconds. In this case dapr cannot connect to the operator as it started up quicker than istio and istio is blocking connections.
Typically what should happen in these cases is that the application requiring the connection, in this case dapr, fails, and is then restarted by kubernetes automatically with the other pods still running.

We could mitigate this issue with https://github.com/dapr/dapr/issues/2984 but I still think it is a valid point that dapr should not successfully start if the operator is not reachable.

At present, in some cases, the communication failure between daprd and operator also leads to many unknown problems. The communication failure between daprd and operator should  @yaron2
time="2022-03-23T03:37:55.800807544Z" level=error msg="error from operator stream: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp <IP_ADDRESS>:80: connect: connection refused\""
//After 6 retries, daprd starts and no components are loaded at this time
time="2022-03-23T03:38:03.385290191Z" level=info msg="dapr initialized. Status: Running. Init Elapsed 7616.786076ms" app_id=  instance= -7bc895bfdc-tx5sf scope=dapr.runtime type=log ver=1.6.0

/active

@yaron2 Is there a plan to deal with this problem?


"Access Denied" when trying to update to newest build.

Brief description of your issue
Trying to update SI to the latest build and as soon as i hit "install", it shows this:

... and then it just force-closes itself. This is even with admin permission enabled.
Steps to reproduce (optional)
No response
Expected behavior (optional)
No response
Actual behavior (optional)
No response
Environment (optional)
Build 3.0.6550, commit cd8e90b (current)
Build 3.0.6772, commit a7cce79 (new)
Windows 11 Pro, 22H2

Can you check Process Monitor and find the last file/folder returning access denied?
https://learn.microsoft.com/en-us/sysinternals/downloads/procmon

Alright, took me some time to understand how to filter out the events, but here's what i got:

Date:	12/06/2023 18:26:06.5879151
Thread:	5448
Class:	File System
Operation:	CreateFile
Result:	ACCESS DENIED
Path:	D:\Program\System Informer\systeminformer-setup.exe
Duration:	0.0000241
Desired Access:	Generic Write
Disposition:	OverwriteIf
Options:	Sequential Access, Synchronous IO Non-Alert, Non-Directory File
Attributes:	N
ShareMode:	Read
AllocationSize:	13,955,072


Document list of forecast products

Describe the Task
Need to identify a list of products that will be available for display for each of the forecasts. First work offline with team to collect all potential products and necessary data information. Then finalize the list and include in the documentation.
Time Estimate
1 day
Sub-Issues
Consider breaking the task down into sub-issues.

[x] Work offline on doc to identify all potential products and information
[x] Finalize the list for beta version
[x] Include list in the documentation

Relevant Deadlines
Sep 30, 2022
Define the Metadata
Assignee

[ ] Select engineer(s) or no engineer required
[ ] Select scientist(s) or no scientist required

Labels

[ ] Select component(s)
[ ] Select priority

Projects and Milestone

[ ] Select Project
[ ] Select Milestone as the next official version or Backlog of Development Ideas

Task Checklist

[ ] Complete the issue definition above, including the Time Estimate.
[ ] Fork this repository or create a branch of develop.
Branch name: feature_<Issue Number>/<Description>
[ ] Complete the development and test your changes.
[ ] Add/update log messages for easier debugging.
[ ] Add/update tests.
[ ] Add/update documentation.
[ ] Push local changes to GitHub.
[ ] Submit a pull request to merge into develop.
Pull request: feature <Issue Number> <Description>
[ ] Define the pull request metadata, as permissions allow.
Select: Reviewer(s), Project, and Development issue
Select: Milestone as the next official version
[ ] Iterate until the reviewer(s) accept and merge your changes.
[ ] Delete your fork or branch.
[ ] Close this issue.

Initial set of products has been implemented and documented in the users guide.


Regarding CSV file based datasets for 11_yolov_train for text detection

here is the dataset link: https://www.kaggle.com/datasets/robikscube/textocr-text-extraction-from-images-dataset
I was struggling trying to adapt the code for the dataset above, the model would freeze after 1 full epoch

I almost integrated feature for TextOCR dataset, I'll reopen this and close after I merge these changes

Thank you! I attached my attempts on #56


Scale type support

Any plans for implementing scaling support?

You mean like in Android-ScalableVideoView
? It's not planned as TextureVideoView tries to be a as-pure-as-possible drop-in replacement of Android's VideoView based on the original sources. Of course, you are free to call TextureVideoView#setTransform(Matrix) from outside to apply any transformation matrix you like. But in general it's very unlikely that we add features that are not included in the original (besides additions from TextureView, obviously).

OK, thanks for clarifying that.
I managed to implement scaling by taking some logic from Android-ScalableVideoView and integrating it with TextureVideoView.
You can check it out here.

Great example, good to know that it's works for you! Thanks for sharing and using TextureVideoView :smile:


conversion not working in windows 10

xls2xlsx version:
Python version: 3.8.2
Operating System: Windows 10

Description
i created a simple xls file and tried to use the utility from command line it is give the below error

![image](https://user-images.githubusercontent.com/68939440/96094846-7cde9f00-0eeb-11eb-8c93-9a86784d8527.png)

Sorry about that - looks like I have no tests for the cli (command line interface).  Anyhow I know what the problem is and will push a fix tonight.

Fixed in v0.1.3


typo

A disabled dimension will now (should be not?) show up in any lists of dimensions for a plan seen by customers.

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

ID: 3a4a35b2-e653-3199-1b07-f3e466ac1cb1
Version Independent ID: 07da492b-dc77-1dbf-4712-922cb069c0ab
Content: Metered billing using the marketplace metering service
Content Source: articles/marketplace/partner-center-portal/saas-metered-billing.md
Service: marketplace
GitHub Login: @qianw211
Microsoft Alias: v-qiwe

@allenwux fixed :)
Once the PR merges the changes will go live after a few hours.


Github action for running tests

This should set up Github actions for running all Go tests recursively on all pull requests and pushes.
The configured Go version is Go 1.13.

The checks are currently failing as expected.

We may also want to configure golangci-lint.

Yeah, there's an action for that -- https://github.com/actions-contrib/golangci-lint

looks good, thanks!

CC @jcharum


Fix failing variable explorer nightly tests

These may have regressed again so can't tell if your fixed worked or not.

The new failures are only from this Wednesday and this was fixed early August. I'm resolving as these were passing just as of last week.
https://dev.azure.com/ms/vscode-python/_build/results?buildId=110412&view=ms.vss-test-web.build-test-results-tab
No need to keep the old issue around.


removing hiring banner

If it's not a huge hassle before we switch sites, it would be best to remove the hiring banner as the jobs page has already been updated to reflect that H. has no open positions.

+1

Since this code no longer powers the Hypothesis site, I’m closing this issue.


Don't stop the query when stopping polling.

You may still want to receive updates to the query from other (non-polling) sources.
@helfer does it make sense to add a test for this?

@tmeasday yeah, let's also add a test for this so we don't screw it up again.

Ping: can we add a test here?

Done

Thanks!

Actually hold on, my test is bogus.

Ok, I fixed it.


Updated content and screenshots

We have modified the content, updated branding from VSTS to Azure DevOps wherever necessary and updated the screenshots.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: CanarysAutomations sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

The content has been updated for "CI and CD with Azure DevOps - Quickstart" lab to match the new terminologies.


npm test from clean project yields eslint error

did yo babel-boilerplate, answered questions, then did npm test. That, and all other npm run commands result in an error about eslint not knowing where to look for .globals.json:
Error: Cannot read config file: /Users/ixtli/Downloads/foo/node_modules/setup/.globals.json
Error: ENOENT: no such file or directory, open '/Users/ixtli/Downloads/foo/node_modules/setup/.globals.json'
Referenced from: /Users/ixtli/Downloads/foo/test/.eslintrc
    at Error (native)
    at Object.fs.openSync (fs.js:634:18)
    at Object.fs.readFileSync (fs.js:502:33)
    at readFile (/Users/ixtli/Downloads/foo/node_modules/eslint/lib/config/config-file.js:71:15)
    at loadJSONConfigFile (/Users/ixtli/Downloads/foo/node_modules/eslint/lib/config/config-file.js:121:41)
    at loadConfigFile (/Users/ixtli/Downloads/foo/node_modules/eslint/lib/config/config-file.js:213:26)
    at load (/Users/ixtli/Downloads/foo/node_modules/eslint/lib/config/config-file.js:500:18)
    at /Users/ixtli/Downloads/foo/node_modules/eslint/lib/config/config-file.js:392:36
    at Array.reduceRight (native)
    at applyExtends (/Users/ixtli/Downloads/foo/node_modules/eslint/lib/config/config-file.js:363:28)

That file exists where it should (./test/setup/) but it seems like .eslintrc is using a relative path which is being resolved to node_modules for some reason.
Tried on both node 6.2.2 and 4.2.2.

oh also, i did not have eslint installed globally when i ran these commands. i installed it globally, reinstalled node modules, and retried the commands and i get the same error.

Thanks! I'll take a look today.

This is the oddest thing – I can't reproduce it. @paulfalgout / @megawac would either of you have a sec to try this?

:( For what it's worth I was able to make this happen on a separate machine
which had 4.2.2 installed.
On Tue, Jun 21, 2016 at 01:15 James, please<EMAIL_ADDRESS>wrote:

This is the oddest thing – I can't reproduce it. @paulfalgout
https://github.com/paulfalgout / @megawac https://github.com/megawac
would either of you have a sec to try this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/babel/generator-babel-boilerplate/issues/363#issuecomment-227342612,
or mute the thread
https://github.com/notifications/unsubscribe/AAM5AIVRVVtpAXpiwrYg7n42AlS7VLU_ks5qN3N-gaJpZM4I55hq
.

Ah, look at that. It must be an upstream bug: https://github.com/eslint/eslint/issues/6489

oh well done. thanks for doing the googlin' :)

oh well done. thanks for doing the googlin' :)

No problem! If you restrict your version of ESLint, you should be able to avoid it. Have you been able to get past the problem?

@ixtli does the latest eslint cause an error for you?

After some more investigating, I don't think that the above issue is the problem.
I've tried on two different macs and can't reproduce this, so I'm going to close for now. @ixtli if you want to pair or spend more time trying to figure this out, then let me know.
If anyone else runs into this issue, please comment here and we can keep the discussion going!

Oh I'm sorry I missed the Jul 15th message :( If I have reason to come back to this I will reopen. Thanks for your help :D

Oh I'm sorry I missed the Jul 15th message :(

No problem!

If I have reason to come back to this I will reopen. Thanks for your help :D

Sounds good :)


Add flag for a short branch name

Hitting an issue where the branch names are too big for certain tests we are doing with AWS. This adds in a flag to use a shorter branch name.

This may not be needed, as we are looking into other solutions.

Nevermind, we found a different solution. Unless anyone else needs this I am going to close it.

Nevermind, we found a different solution. Unless anyone else needs this I am going to close it.

SGTM.
Just out of curiosity, what was your solution?

The issue was with role names, they must be 64 chars or smaller. We just opted to truncate them as that should be fine for our purposes


typescript-resolver adds an extra property for my custom scalars

Which packages are impacted by your issue?
"@graphql-codegen/typescript-resolvers"
Describe the bug
I just recently added the typescript-resolvers plugin to my codegen config, and while it does what I need, it seems to also add my custom scalars to the ResolversTypes.
The issue is that it seems to add an extra ['output'] property to these scalars. For example; I end up getting an error:
Property 'output' does not exist on type 'X'

Example:
// generated.ts
/** All built-in and custom scalars, mapped to their actual values */
export type Scalars = {
  ID: string;
  String: string;
  Boolean: boolean;
  Int: number;
  Float: number;
  DataURL: any;
  Date: any;
  DateTime: any;
  Email: any;
  JSON: any;
  PhoneNumber: any;
};

// ....

/** Mapping between all available schema types and the resolvers types */
export type ResolversTypes = {
  Boolean: ResolverTypeWrapper<Scalars['Boolean']['output']>;
  ID: ResolverTypeWrapper<Scalars['ID']['output']>;
  Float: ResolverTypeWrapper<Scalars['Float']['output']>;
  Int: ResolverTypeWrapper<Scalars['Int']['output']>;
  PhoneNumber: ResolverTypeWrapper<Scalars['PhoneNumber']['output']>; // <-- this one weirdly doesn't throw an error?
  String: ResolverTypeWrapper<Scalars['String']['output']>;

/** Mapping between all available schema types and the resolvers parents */
export type ResolversParentTypes = {
  Boolean: Scalars['Boolean']['output'];
  DataURL: Scalars['DataURL']['output']; // <-- this one also doesn't throw an error
  Date: Scalars['Date']['output']; // <-- this one also doesn't throw an error
  DateTime: Scalars['DateTime']['output']; // <-- this one also doesn't throw an error
  Float: Scalars['Float']['output'];
  ID: Scalars['ID']['output'];
  Int: Scalars['Int']['output'];
  String: Scalars['String']['output'];

Am I missing something from my config? Ideally I want to remove this weird ['output'] property
Your Example Website or App
N/A
Steps to Reproduce the Bug or Issue
N/A
Expected behavior
Ideally, I want to not have this ['output'] generated
Screenshots or Videos
No response
Platform

OS: OSX 13.2
NodeJS: v18.16.1
graphql version: "^16.7.1"
"@graphql-codegen/cli": "^3.3.1",
"@graphql-codegen/typescript": "^3.0.4",
"@graphql-codegen/typescript-graphql-request": "^5.0.0",
"@graphql-codegen/typescript-operations": "^3.0.4",
"@graphql-codegen/typescript-react-apollo": "^3.3.7",
"@graphql-codegen/typescript-resolvers": "^4.0.1",

Codegen Config File
generates:
  ./src/generated/generated-mock.ts:
    plugins:
      - typescript-mock-data:
          typesFile: ./graphql.ts
          typeNames: pascal-case#pascalCase
  ./src/generated/graphql.ts:
    plugins:
      - typescript
      - typescript-operations
      - typescript-react-apollo
      - typescript-resolvers

Additional context
No response

You'll need to downgrade your typescript-resolvers dependency to 3.x (in fact, align all of them to 3.x if possible) as in 4.0 Scalars are defined as
export type Scalars = {
  ID: { input: string; output: string; }
  String: { input: string; output: string; }
  Boolean: { input: boolean; output: boolean; }
  Int: { input: number; output: number; }
  ...

If I want to use the 4.x version then what changes I have to do ?

Hi @davidgtu,
Your Scalars type should also have input/output. For example:
export type Scalars = {
  ID: { input: string, output: string };
  String: { input: string, output: string };
  Boolean: { input: boolean, output: boolean };
  Int: { input: number, output: number };
  Float: { input: number, output: number };
  DataURL: { input: any, output: any };
  Date: { input: any, output: any };
  DateTime: { input: any, output: any };
  Email: { input: any, output: any };
  JSON: { input: any, output: any };
  PhoneNumber: { input: any, output: any };
};

I think in your case, one of the other packages will need to be bumped to the latest versions as well. I think it's either @graphql-codegen/typescript or @graphql-codegen/visitor-plugin-common

Here's an example repo with codegen setup which doesn't have this issue: https://github.com/eddeee888/graphql-server-template.
Please bump your package versions. I'm more than happy to re-open this issue if it's still a problem.


chore: document Xcode >= 11.6 is required

Summary
document Xcode >= 11.6 is required

:tada: This PR is included in version 3.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


IndexArray question

Some noticement about new IndexArray:
Why 'at' function is template?

If you know _stride, you know size of keeping elements.
As it is now, I need to instantiate template function explicitly, otherwise error:

Returned type could be IndexFormat::U_INT as maximum size index format
Besides, is it possible to implement the following api for IndexArray ?
IndexArray::operator[]
IndexArray::begin()
IndexArray::end()
IndexArray::erase(iterator_from, iterator_to) - (There is no erase function for underlying type yasio::byte_buffer at all)

If it is not simple to implement the function as non template, then the solution could be to define default template parameter, like this:

If it is not simple to implement the function as non template, then the solution could be to define default template parameter, like this:

looks good.

Implement at as template is for readwrite operation, certainly, we can add two fuction like:
void seti(size_t idx, uint32_t val);
uint32_t geti(size_t idx);

Hide begin, end stubs, because we don't want user use for loop external, just use IndexArray::for_each instead.

Hide begin, end stubs, because we don't want user use for loop external, just use IndexArray::for_each instead.

Certainly, we can make the begin, end stubs return void* to for the same purpose.

Certainly, we can make the begin, end stubs return void* to for the same purpose.

It is a normal practice to provide begin/end api since there is opportunity to random access with at according to stl.
But, you could implement it like at template and return pointer to _Ty rather then void* to keep opportunity for +/- operations, since, as I properly understand, iterator in terms of yasio::byte_buffer is pointer to keeping element and default_allocator allocates linear array

ok, will do


[fix] Fixed too short wait in ResourceGroupRateLimiterTest

Fixes #20385
Motivation
The test wait time is too short.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[X] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

Codecov Report

Merging #21509 (01919db) into master (78fc853) will increase coverage by 39.87%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master   #21509       +/-   ##
=============================================
+ Coverage     33.39%   73.27%   +39.87%
- Complexity    12194    32612    +20418
=============================================
  Files          1638     1890      +252
  Lines        127949   140440    +12491
  Branches      13952    15436     +1484
=============================================
+ Hits          42733   102901    +60168
+ Misses        79564    29454    -50110
- Partials       5652     8085     +2433

Flag
Coverage Δ

inttests
24.19% <ø> (+0.04%)
:arrow_up:

systests
24.78% <ø> (?)

unittests
72.54% <ø> (+40.72%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1538 files with indirect coverage changes


Added waitResponse utility method

I believe this method will be very appreciated as it greatly simplifies user interaction into bots!

Really interesting I like it too much!. I was working with another solution which don't uses promises (but a callback that can be executed many times).

Closed by 17cb062c9642313f17c3c5e070de2032031857d3

I see your implementation is quite different.... I personally prefer promises over callbacks... Do you mind if I publish an alternative npm module?

I prefer promises over callbacks too but a Promise can't be called (resolved) more than once. There can be multiple replies to the same message.

Of course, you can alternative npm module, this is OpenSource :blue_heart:

There can be multiple replies to the same message.
I believe we are taking two different approaches, but I understand your point.

I've just added another feature, an onCommand function which splits arguments by commas: a little less flexible than onText but simpler for the end user in the most common cases, I believe.
Have a look at my fork if you wish, I will not submit a pull request
:+1:


Run merf from recipe

Fixes #152

`springtime src/springtime/recipes/model_comparison_usecase.yaml` fails

Downloading dataset:  npn_obs
/tmp/data/rnpn/rnpn_npn_data_y_2015_Deciduous broadleaf_breaking leaf buds_Washington.csv already exists, skipping
/tmp/data/rnpn/rnpn_npn_data_y_2016_Deciduous broadleaf_breaking leaf buds_Washington.csv already exists, skipping
/tmp/data/rnpn/rnpn_npn_data_y_2017_Deciduous broadleaf_breaking leaf buds_Washington.csv already exists, skipping
/tmp/data/rnpn/rnpn_npn_data_y_2018_Deciduous broadleaf_breaking leaf buds_Washington.csv already exists, skipping
/tmp/data/rnpn/rnpn_npn_data_y_2019_Deciduous broadleaf_breaking leaf buds_Washington.csv already exists, skipping
/tmp/data/rnpn/rnpn_npn_data_y_2020_Deciduous broadleaf_breaking leaf buds_Washington.csv already exists, skipping
Dataset npn_obs loaded with 241 rows
Dataset npn_obs resampled to 241 rows
Downloading dataset:  daymet
Dataset daymet loaded with 326310 rows
Dataset daymet resampled to 894 rows
Downloading dataset:  modis
Dataset modis loaded with 40975 rows
Dataset modis resampled to 894 rows
Datesets joined to shape: (241, 49)
Data saved to: /tmp/output/data.csv
                   Description                   Value
0                   Session id                     123
1                       Target  breaking leaf buds_doy
2                  Target type              Regression
3          Original data shape               (241, 49)
4       Transformed data shape               (241, 49)
5  Transformed train set shape               (180, 49)
6   Transformed test set shape                (61, 49)
7             Numeric features                      48
Processing:   0%|                                                                                | 0/1 [00:00<?, ?it/s]Traceback (most recent call last):
  File "/home/stefanv/mambaforge/envs/springtime/bin/springtime", line 8, in <module>
    sys.exit(cli())
  File "/home/stefanv/mambaforge/envs/springtime/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/home/stefanv/mambaforge/envs/springtime/lib/python3.10/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/home/stefanv/mambaforge/envs/springtime/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/stefanv/mambaforge/envs/springtime/lib/python3.10/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/home/stefanv/git/springtime/springtime/src/springtime/main.py", line 161, in cli
    main(recipe)
  File "/home/stefanv/git/springtime/springtime/src/springtime/main.py", line 155, in main
    Workflow.from_recipe(recipe).execute()
  File "/home/stefanv/git/springtime/springtime/src/springtime/main.py", line 115, in execute
    self.run_experiments(df)
  File "/home/stefanv/git/springtime/springtime/src/springtime/main.py", line 145, in run_experiments
    compare_models(
  File "/home/stefanv/git/springtime/springtime/src/springtime/experiment.py", line 166, in compare_models
    save_leaderboard(s, output_dir)
  File "/home/stefanv/git/springtime/springtime/src/springtime/experiment.py", line 185, in save_leaderboard
    df = s.get_leaderboard()
  File "/home/stefanv/mambaforge/envs/springtime/lib/python3.10/site-packages/pycaret/internal/pycaret_experiment/supervised_experiment.py", line 5130, in get_leaderboard
    results = pd.concat(result_container_mean)
  File "/home/stefanv/mambaforge/envs/springtime/lib/python3.10/site-packages/pandas/util/_decorators.py", line 331, in wrapper
    return func(*args, **kwargs)
  File "/home/stefanv/mambaforge/envs/springtime/lib/python3.10/site-packages/pandas/core/reshape/concat.py", line 368, in concat
    op = _Concatenator(
  File "/home/stefanv/mambaforge/envs/springtime/lib/python3.10/site-packages/pandas/core/reshape/concat.py", line 425, in __init__
    raise ValueError("No objects to concatenate")
ValueError: No objects to concatenate
INFO     [embedded.py:352] Embedded R ended.
INFO     [embedded.py:337] Embedded R already ended.


fix(rbac): Add kafkachannels to default Knative Sinks RBAC

This PR fixes #2950.
It adds kafkachannels resources to default Knative Sinks RBAC and documents RBAC requirements for Knative Sinks.
Release Note
fix(rbac): Add kafkachannels to default Knative Sinks RBAC

@maschmid let us know any feedback you have on this.


Inference Endpoint and Deployment resources

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

Contribution checklist:

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

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

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

Adding new API(s)
Adding a new API version
Adding a new service

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

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

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

While adding new version the recommendation is to copy the existing version into new directory structure for first commit and then push new changes for easy review. Please create new branch with this recommendation for faster review.
Also please resolve the errors in the automated tests.

/azp run automation - sdk

While adding new version the recommendation is to copy the existing version into new directory structure for first commit and then push new changes for easy review. Please create new branch with this recommendation for faster review.
Also please resolve the errors in the automated tests.

Thanks for the recommendation. Which existing version should I copy? Latest stable or latest preview?

While adding new version the recommendation is to copy the existing version into new directory structure for first commit and then push new changes for easy review. Please create new branch with this recommendation for faster review.
Also please resolve the errors in the automated tests.

Thanks for the recommendation. Which existing version should I copy? Latest stable or latest preview?

Also it seems that the errors in the automated tests are not changes I made, but in machineLearningServices.json that was already checked in.

moved changes to new PR as instructed. https://github.com/Azure/azure-rest-api-specs/pull/10420


Add support for NHK for School

Checklist

[x] I'm reporting a new site support request
[x] I've verified that I'm running youtube-dl version 2021.05.16
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that none of provided URLs violate any copyrights
[x] I've searched the bugtracker for similar site support requests including closed ones

Example URLs

Single video: https://www2.nhk.or.jp/school/movie/bangumi.cgi?das_id=D0005150191_00000
Playlist: https://www.nhk.or.jp/school/kokugo/drill/
Playlist: https://www.nhk.or.jp/school/ouchi/playlist_g1_march.html

Description

@devesh Doing some starting research at the moment:

This site has a search function we should support:

https://www.nhk.or.jp/school/keyword/?kw=メダカ&cat=all&from=1&sort=ranking
https://www.nhk.or.jp/school/keyword/?kw=<query>&cat=<category>&from=<page>&sort=<sorting>

Supported values for category:

all
b (program)
c (clip)

Supported values for sort

ranking (most popular)
update (most recent)

Alongside bangumi, we also have clip:

https://www2.nhk.or.jp/school/movie/bangumi.cgi?das_id=D0005150191_00000 (program)
https://www2.nhk.or.jp/school/movie/clip.cgi?das_id=D0005311329_00000&p=box (clip)
https://www2.nhk.or.jp/school/movie/<type>.cgi?das_id=<id>

The site has its own playlist feature, separate from the concept of playlists in youtube-dl, that allows you to create and share custom playlists. Should we support this, and if so, do you have any playlist IDs?
kokugo pages have a JSON version of the page (https://www.nhk.or.jp/school/kokugo/drill/meta/program.json), which will make them super easy to scrape.
ouchi pages, unlike kokugo pages, aren't very standardized on the frontend and backend, so I'm probably going to have to skip parsing them; sorry.

I created playlist ID 9178 if you want to try to implement support for it. I do not plan to use it myself, but somebody else might.
Similarly, I do not plan to download from ouchi pages and instead plan to use only the kokugo pages, so what you're proposing to implement support for is fantastic.

Apart from the issue, they do use Akamai!? so rich they are!
I wonder why they don't geo-restrict the website for overseas, since NHK is funded by Japanese government.
I'll try to write extractor for that later.


NPI-3072 additional comments explaining why we read Sinex with read_fwf() and that field names do not map

@treefern @ronaldmaj  I love it! We might dump the slow read_fwf in the future for a faster parsing method but that method is to be discovered

I assume read_fwf would be a bit faster (and more reliable) if we explicitly set column boundaries, but I haven't tested this.
I think we could also improve robustness and maybe speed, by adding logic to first trim to the data structure needed. Eg +SOLUTION/APRIORI through -SOLUTION/APRIORI

@treefern you could definitely measure this but from experience it won't help. One could make it marginally faster by not asking for STD column if it's not present but there is no way of telling from a header of the file or the block if STD is present or not... SINEX is a pain to read efficiently in python


Redirect to english version for non-french browsers

Should require storing the local in session.

Shouldn't this be in the 1.0 version?
Without this, what's the default behaviour for a non-French user? He'll see the French version?

Replace /en/ path prefix by Content-Language detection + optional lang query param de request switching the locale, that will fix #29 as well.

It seems we follow Google guideline with the current behavior so I plan to keep it as it is.


[New Port Request] SingleApplication

Library name: SingleApplication
Library description: This is a replacement of the QtSingleApplication for Qt5 and Qt6.
Source repository URL: https://github.com/itay-grudev/SingleApplication
Project homepage (if different from the source repository):
Anything else that is useful to know when adding (such as optional features the library may have that should be included):

I have created a vcpkg port for this - can we reopen this issue? Also, would qt-single-application be a more appropriate name for the port?

@nickdademo As long as the name is brief and clear, we can completely accept qt-single-application. :)

@nickdademo As long as the name is brief and clear, we can completely accept qt-single-application. :)

<GH-orga>-<GH-repo>: itay-grudev-singleapplication
Avoids confusion about its origin.

So since PR was merged this issue could be closed now?

So since PR was merged this issue could be closed now?

Yes, thanks.


Fix is_ds_attached

Closing because the travis-ci config is too old at the time of this PR. Re-open to re-trigger the build.


Cosmetics

For CS linter. Trailing colons, whitespaces, indent issues, ++.

Thanks! Merged ;) Now I know there is such thing as CSLint ;) This is actually my very first project in coffescript and I'm not sure I like it. But, it's a good fun

Yeah even non-verbose CS needs a linter :)


[Dice] PingA for dice adventure (pasring and executing errors)

Teaching: Go up and Ping A, VAL gets stuck

Index Error when pinga at the beginning of the game
still problems of coding and natural language
Coding      Natural Language
Pinga <---> Ping A
move_to <---> move to

VAL still shows in coding language for move_to and pingA
current prompts

displayed in Dice

json file for Dice actions:


Dependency flutter_mailer throws error

Since the catcher_2 ^1.0.0 depends on this package I'm getting the following error running my Flutter op on Android:
/Users/koenvestjens/.pub-cache/hosted/pub.dev/flutter_mailer-2.1.1/android/src/main/java/com/dataxad/flutter_mailer/FlutterMailerPlugin.java uses or overrides a deprecated API.
--
Flutter 3.13.7 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 2f708eb839 (4 days ago) • 2023-10-09 09:58:08 -0500
Engine • revision a794cf2681
Tools • Dart 3.1.3 • DevTools 2.25.0

It's not an error, but a warning which I have already reported to the corresponding package quite some time ago: https://github.com/taljacobson/flutter_mailer/issues/51

I see thanks. But Google is rejecting my app because of this warning. The app crashes on startup.

Then, that seems to be some error that has nothing to do with the warning you mentioned above. Try to find that and report back if it has something to do with catcher_2 itself.


Environment variable SHELL set to pw->pw_dir.

In lines 164 and 169 of file asroot.c, pw_dir should probably be changed to pw_shell.
https://github.com/maandree/asroot/blob/e3784823610347e5908e119189c9a51e22c609b2/asroot.c#L164
https://github.com/maandree/asroot/blob/e3784823610347e5908e119189c9a51e22c609b2/asroot.c#L169

Thank you, this has been is correct now.


Flaken Tyre Sports Car Challenge

@bfiete : Add new Road serie for 2023 Season 3

Add #481 and #485 for new tracks for Season 3


Release date for sentinel and streams support

Hi guys,
could you please tell me the release date for the aioredis version with support for sentinel and streams ?
Thanks

https://github.com/aio-libs/aioredis/issues/438

v1.2.0 with streams support has been just released.


Handle abrupt player disconnection

Explicit disconnects are handled properly but if a connection times out or ambient is simply killed then the player is still seen as connected.
Add an explicit player disconnected callback
OR
Add handling inside proxied connection and report an error there to let Ambient handle disconnection

You could have the proxy send a Disconnect frame on behalf of the timed out user
See: https://github.com/AmbientRun/Ambient/blob/f4e68976e77dac06268883acad0bcd82aaf7f493/crates/network/src/proto/mod.rs#L10

Feel free to add more variants to that enum if you need, it will be backwards compatible anyway as long as they are added after the existing variants

I'd prefer proxy to be more transparent and not to rely too much on Ambient protocol.


fix:Veracode CVEs fix

Description
Veracode CVEs fix in jetty-http jar.

CVE-2023-36478 | CWE-190
Denial Of Service (DoS): org.eclipse.jetty is vulnerable to Denial Of Service (DoS). The vulnerability arises from the library's failure to appropriately limit the size in HPACK header values. This allows an attacker to repeatedly send maliciously crafted HTTP messages, leading to an integer overflow and ultimately causing an application crash through the checkSize function in MetaDataBuilder.java.

CVE-2023-40167| CWE-130
HTTP Request Smuggling: Jetty is vulnerable to HTTP Request Smuggling. The vulnerability is due to accepting + character proceeding the content-length in the request. This vulnerability can be exploited by the attacker to possibly conduct request smuggling attacks.

@shijinrajbosch  Update changelog with new version please.

@shijinrajbosch Update changelog with new version please.

Hi @tunacicek ,
Please note that the change log was updated with the CVEs fix already (with the previous PR - https://github.com/eclipse-tractusx/sldt-semantic-hub/pull/179/files ) . This PR to address the problem with previous PR.

@shijinrajbosch Update changelog with new version please.

Hi @tunacicek ,
Please note that the change log was updated with the CVEs fix already (with the previous PR - https://github.com/eclipse-tractusx/sldt-semantic-hub/pull/179/files ) . This PR to address the problem with previous PR.

since we created the image yesterday for the previous PR and now since we have new changes we will need to create new image and hence need to update the version again in Changelog and create new version.

@shijinrajbosch Update changelog with new version please.

Hi @tunacicek ,
Please note that the change log was updated with the CVEs fix already (with the previous PR - https://github.com/eclipse-tractusx/sldt-semantic-hub/pull/179/files ) . This PR to address the problem with previous PR.

since we created the image yesterday for the previous PR and now since we have new changes we will need to create new image and hence need to update the version again in Changelog and create new version.

Thanks @tunacicek  for the clarification. I have updated the changelog accordingly.


Add Binary Parsing Support & Refactor TryGetNumberValue & ScanNumberHelper

PR Summary
Fixes #7557

Adds support for binary parsing in format echoing hex: 0b11010110

Works with all existing type suffixes and multipliers.
Supports arbitrary length parsing with n suffix using BigInteger; details below.

Adds NumberFormat enum to specify hex/binary/base 10 for the tokenizer, replacing old bool hex.
Adds n suffix for all numeric literals to support returning value as a BigInteger if requested. This bypasses the issue of large literals losing accuracy when they cast through double.
Adds tests for all new behaviours.

Binary / Hex Parsing Implementation

Mimics old sign bit behaviour for int and long types. Sign bits accepted for 8 or 16-bit Hex parsing, and 8, 16, 32, 64 for binary.

i.e., 0xFFFFFFFF -eq ([int]-1) and 0xFFFFFFFFFFFFFFFF -eq ([long]-1), but suffixing u creates int.MaxValue and long.MaxValue, respectively, instead.

Sign bits higher than this are accepted for bigint-suffixed numerals:

Hex: Bigint-suffixed hex treats the high bit of any literal with a length multiple of 8 as the sign bit
Binary: Bigint-suffixed binary accepts sign bits at 96 and 128 chars, and from there on every 8 characters.
Prefixing the literal with a 0 will bypass this and be treated as unsigned, e.g. 0b011111111

Specifying an unsigned suffix (or combination suffix that includes u) ignores sign bits, similar to how parsing a hex string using [Convert]::ToUint32() would do so.
Supports negating literals using - prefix. This can result in positive numbers due to sign bits being permitted, just like hex literals.

Refactored numeric tokenizer parsing
New flow:

Check for real (.01, 0.0, or 0e0 syntaxes)

If the decimal suffix is present, TryParse directly into decimal. If the TryParse fails, TryGetNumberValue returns false.
TryParse as Double, and apply multiplier to value. If the TryParse fails, TryGetNumberValue returns false.

Check type suffixes and attempt to cast into appropriate type. This will return false if the value exceeds the specified type's bounds.
Default to parsing as double where no suffix has been applied.

Check number format.

If binary, manually parse into BigInteger using optimized helper function to directly construct the BigInteger bytes from the string.
If hex, TryParse into BigInteger using some special casing to retain original behaviours in int/long ranges.
If neither binary nor hex, TryParse normally as a BigInteger.

Apply multiplier value before attempting any casts to ensure type bounds can be appropriately checked without overflows.
Check type suffixes.

If a specific type suffix is used, check type bounds and attempt to parse into that type.

If the value exceeds the type's available values, the parse fails. Otherwise, a straight cast is performed.

If no suffix is used, the following types are bounds-checked, in order, resulting in the first successful test determining the type of the number.

int
long
decimal (base-10 literals only)
double (base-10 literals only)
BigInteger for binary or hex literals. If the value is outside long range (for hex and binary) or double range (for base 10), the parse will fail; higher values must be explicitly requested using the n/N BigInteger suffix.

This is a breaking change as binary literals are now read as numbers instead of generic tokens which could potentially have been used as function / cmdlet names or file names.
Notes:

Binary literal support was approved by the committee in #7557
The same issue is still under further discussion for underscore support in numeric literals and whether BigInteger parsing ought to be exposed to the user at all.

Supporting underscore literals is a further breaking change causing some generic tokens like 1_000_000 to be read as numerals instead. Per @SteveL-MSFT's comment this proposal was rejected.
Removing underscore support or preventing standard parsing from accepting BigInteger ranges is a relatively trivial matter. It is my personal opinion that there is no particular reason not to hand the user a BigInteger when they enter a sufficiently large literal, but I will defer to the PowerShell Committee's judgement on this.

PR Checklist

[X] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[X] Summarized changes
[ ] ~[Change is not breaking]~(https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#making-breaking-changes)
[X] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[X] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[ ] Not Applicable
OR
[X] User-facing Documentation needed

[X] Issue filed - Issue link: https://github.com/PowerShell/PowerShell-Docs/issues/2965

Testing - New and feature

[ ] Not Applicable or can only be tested interactively
OR
[X] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

/cc @iSazonov , @SteveL-MSFT as it pertains to the tagged-for-further-discussion #7557

These are the benchmarks @HumanEquivalentUnit and I performed whilst working on this binary parser. Top notch work from him, frankly astonishing.
Note that all cases were tested within ranges that Convert.ToIntX() methods are available, but the current method (labelled BigEndianBinaryOr in this table) generalises seamlessly to arbitrary-length binary strings.
https://gist.github.com/vexx32/852cd1d0ddc3e1a93f77b90ab23cfe3d

@vexx32 I'd prefer to see small PR - with 0b only. We could more fast review.

I understand your viewpoint, but in order to permit 0b parsing a majority of these changes are required -- or a significant amount of redundant code would need to be in place, because TryParse() methods are not capable of parsing binary.
I think the alternative would leave you guys with a lot more to review, only to possibly pull it out later. Also, it would make any further PRs significantly more complex. I felt it best to simplify the code paths as much as possible, in order to prevent the tokenizer becoming a complex morass of unmaintainable code.

Underscore and I suffix is not approved in related issue. So we have to wait.

@vexx32 I have no more ideas than to occupy your time :-) - thanks for great work! We are waiting PowerShell Committee.

Appreciate you taking the time to help us make it better, Ilya! 😄
I might rebase once more to tidy the commit history a little if I get a moment, but otherwise I don't mind waiting till the Committee makes a decision here.

Please don't rebase until maintainers ask you.

🤔 might be an idea to have stalebot exempt things tagged with Review - Committee perhaps... anyway. Let me know when you guys have a decision and I'll get it all sorted out. 😄

@PowerShell/powershell-committee reviewed this with the associated issue, we do not accept the underscore delimiter syntax nor rolling over into BigInt.

Thank you @SteveL-MSFT & committee! I'll make sure the code reflects that decision.
Just need one more decision from you fellows, then, which is:

How do we want to handle binary and/or hex parsing in general? Whether it is to respect sign bits or not, and if so which bits are acceptable to be used as sign for both binary and hexadecimal literals. 😄

@vexx32 Please update the PR description (only don't remove expired text - cross out it)

@iSazonov Updated description!

@vexx32 my recommendation is to split off the signing as a separate item as not block this PR on committee review since we're a bit backlogged on the number of issues/PRs that are waiting to be reviewed

@SteveL-MSFT Roger that, sounds like a good plan!
Then I'll make a final pass on the logic and make sure the PR description reflects any quirks in the implementation at higher ranges.

Rebased to fix merge conflict. Should be ready to go. 😄

O-kay... that was unexpected. That's definitely beyond my changes, as far as I can tell. What's going on there?

@SteveL-MSFT @daxian-dbw @TravisEz13 Please review the PR. I do not see what can be done better.

Did a final pass to make sure I'm happy with the code style everywhere I've touched, I think this is about as good as it'll get. 😄
I've also revised the PR description because I found it messy and confusing to read. Hopefully this is much better. 😉

Give me a holler if you'd like me to rebase and handle the merge conflict, otherwise I'll wait till we get this thoroughly reviewed and rebase at the end. 😄

You could resolve the merge conflict without rebase.

@iSazonov with a straightforward merge commit? 🤔

@daxian-dbw If you have a time please review the PR.

@SteveL-MSFT @TravisEz13 @daxian-dbw Please review the PR.

@TravisEz13 I assume we're just pending Dongbo to get back form his well-deserved vacation and review?
Any chance this will make it for 6.2, or should I expect it to wait till after that is released? :slight_smile:

@vexx32 	I'd like to get someone to review this that has some experience in the area. Or at least one more person from the PowerShell team.

@TravisEz13 Seems like CI got stuck here, sorry; could you kick it for me when you get some time? Cheers! 😊

@vexx32 The jobs never started.  I cannot restart them without closing the PR and re-opening it.  I've seen in a few cases where you have force-pushed that the PR cannot be reopened.  The easiest way is to force push again.  For example, make a whitespace change to one of your commit messages and push.

Because this is a breaking change, I'm scheduling it to be merged first thing during 6.3.

@TravisEz13 Do you guys need anything more from me before you merge? 🙂

Perhaps @daxian-dbw could find something :-)

@vexx32 Thanks for the great improvement!


Signrawtransaction is not working on v<IP_ADDRESS>-rc3

Describe the issue
If you try to use deprecated signrawtransaction it won't work on new version v<IP_ADDRESS>-rc3, but signrawtransactionwithwallet works.
Can you reliably reproduce the issue?
If so, please list the steps to reproduce below:

Add another wallet to your dash instance with ./dash-cli createwallet test
Add deprecatedrpc=signrawtransaction into your dash.conf
Try to sign transaction with default wallet:
Dash returns error:
Wallet file not specified (must request wallet RPC through /wallet/<filename> uri-path).

If you try to use new method signrawtransactionwithwallet it works just fine.
Expected behaviour
signrawtransaction should work if there are multiple wallets and it's enabled via deprecated flag
Actual behaviour
signrawtransaction fails
What version of Dash Core are you using?
v<IP_ADDRESS>-rc3
Machine specs:

OS: Linux

Ping @PastaPastaPasta @UdjinM6

Thank you for reporting this. The issue is now fixed in develop, and will likely be released in a new minor release


Patch __awaiter to use bluebird

Keep in mind that even with this patch, the return type of an async function will still be the ES6 Promise, even though the runtime value will be a bluebird Promise.

Why?  It would be nicer to get rid of Bluebird and just use native promises?

@bterlson requested it. I'd prefer to use native promises as well.

I guess it would be good to at least add a comment linking to the docs on __awaiter.

@domenic Added in de98f8c

@domenic the key reason is perf - using bluebird and the __awaiter override shaves ~3s off the ECMA262 build process. Will document it better.

Committed some extra rationale in 33da4fb. Closing this as I've incorporated all the changes here as part of my previous commits.

Make that 662f3a2.


Remove first class pooling support from KestrelOptions

Remove first class support for pooling parameters in KestrelOptions
Expose IHttpComponentFactory as something that can be configured from the outside
Remove IHttpComponentFactory from server features

We should decide if we want to add IHttpComponentFactory as part of KestrelOptions or have it be a service in the DI container.

With the new Options is it possible to add extension methods that add to the config options?

Go generic?
interface IComponentFactory<T>
{
   T CreateComponent();
   void DisposeComponent(T component);
}

Not sure how the init params would work; maybe
interface IComponentFactory<T, TInit>
{
   T CreateComponent(TInit init);
   void DisposeComponent(T component);
}

Nope, too generic is always bad. That looks like a generic IFactory<T> thats trying to replace new()

@DamianEdwards @Eilon
If we decide to do this, we'll need to do design and make the changes in RC2. Thoughts?

@davidfowl can you provide some more detail here? As it stands, this doesn't seem like a an area that will be exposed enough to warrant making this change now, i.e. if we change it RTM we're going to break hardly anybody as almost nobody will set this option on KestrelOptions.

Hardly anybody... :stuck_out_tongue_winking_eye:

Related: #780

Resolved by  #815 ?

@benaadams Did you reference the right PR?

@cesarbs lol no, should be https://github.com/aspnet/KestrelHttpServer/pull/791


stdThreadLocalLog does not print log and trace logs

ttanjo (@tom-tan) reported this on 2024-03-29T18:56:10Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=24468
CC List

forestix
kinke

Description
I reproduce this issue with dmd 2.107.1 on Ubuntu 22.04 and run.dlang.io.
I cannot reproduce this issue with `shaledLog`.

# PoC code
```dlang
import std.logger, std.stdio;

void main()
{
    writeln("==== stdThreadLocalLog ====");
    stdThreadLocalLog.logLevel = LogLevel.all;
    stdThreadLocalLog.log("log");
    stdThreadLocalLog.trace("trace");
    stdThreadLocalLog.info("info");
    stdThreadLocalLog.warning("warning");
    stdThreadLocalLog.error("error");
    stdThreadLocalLog.critical("critical");

    writeln("==== sharedLog ====");
    (cast()sharedLog).logLevel = LogLevel.all;
    (cast()sharedLog).log("log");
    (cast()sharedLog).trace("trace");
    (cast()sharedLog).info("info");
    (cast()sharedLog).warning("warning");
    (cast()sharedLog).error("error");
    (cast()sharedLog).critical("critical");
}

```

# Expected output
Both loggers print `all`, `trace`, `info`, `warning`, `error` and `critical` logs.
```
==== stdThreadLocalLog ====
2024-03-29T18:38:03.881 [all] onlineapp.d:16:main log
2024-03-29T18:38:03.881 [trace] onlineapp.d:17:main trace
2024-03-29T18:38:03.881 [info] onlineapp.d:9:main info
2024-03-29T18:38:03.881 [warning] onlineapp.d:10:main warning
2024-03-29T18:38:03.881 [error] onlineapp.d:11:main error
2024-03-29T18:38:03.881 [critical] onlineapp.d:12:main critical
==== sharedLog ====
2024-03-29T18:38:03.881 [all] onlineapp.d:16:main log
2024-03-29T18:38:03.881 [trace] onlineapp.d:17:main trace
2024-03-29T18:38:03.881 [info] onlineapp.d:18:main info
2024-03-29T18:38:03.881 [warning] onlineapp.d:19:main warning
2024-03-29T18:38:03.882 [error] onlineapp.d:20:main error
2024-03-29T18:38:03.882 [critical] onlineapp.d:21:main critical
```

# Actual behavior
`sharedLog` prints all the logs but `stdThreadLocalLog` lacks `all` and `trace` logs.

```
==== stdThreadLocalLog ====
2024-03-29T18:38:03.881 [info] onlineapp.d:9:main info
2024-03-29T18:38:03.881 [warning] onlineapp.d:10:main warning
2024-03-29T18:38:03.881 [error] onlineapp.d:11:main error
2024-03-29T18:38:03.881 [critical] onlineapp.d:12:main critical
==== sharedLog ====
2024-03-29T18:38:03.881 [all] onlineapp.d:16:main log
2024-03-29T18:38:03.881 [trace] onlineapp.d:17:main trace
2024-03-29T18:38:03.881 [info] onlineapp.d:18:main info
2024-03-29T18:38:03.881 [warning] onlineapp.d:19:main warning
2024-03-29T18:38:03.882 [error] onlineapp.d:20:main error
2024-03-29T18:38:03.882 [critical] onlineapp.d:21:main critical
```

forestix commented on 2024-05-28T23:13:54Z
The experience I had today as a newcomer to Phobos logging:

- Read the std.logger docs.
- Create a StdForwardLogger for each of my modules.
  (I want to control each module's log level separately.)
- Discover that trace log messages are silently discarded.
- Set my logger's log level.
- Discover that trace log messages are still silently discarded.
- Read the std.logger docs again.
- Set globalLogLevel.
- Discover that trace log messages are still silently discarded.
- Read the std.logger docs again.
- Set sharedLog.logLevel.
- Discover that the compiler won't let me
  (none of the overloads of `logLevel` are callable using a `shared` mutable object)
- Read the std.logger docs again.
- Notice how much time this basic task is taking, and swear in exasperation.
- Grovel through the dlang forum archive in search of help.
- Find the magic incantation here:
<EMAIL_ADDRESS>  (cast()sharedLog).logLevel = LogLevel.all;
- Try the magic incantation.
- Discover that the compiler won't let me use it in @safe code.

A default log level higher than `trace` is no surprise; that's reasonably common in logging libraries. However, dealing with it in Phobos is surprisingly painful.

In particular, the solution has at least these problems:

- It's nonintuitive.
- It's not clearly documented.
- It's unreasonably awkward for something as common as logging.
- It doesn't work at all in @safe code.

After finally getting to the bottom of it (and nearly giving up on D because this is far from the first Phobos usability problem to bite me) I see that I could work around it in my own programs by using @trusted code. However, I'm writing a library, and I really don't want to require that its users resort to library-specific functions or @trusted shenanigans to control such basic functionality as logging.

It would be nice if this was either fixed by a revised std.logger design, or at least hidden behind a clearly documented standard interface.

forestix commented on 2024-05-29T01:36:00Z
Also, is `(cast()sharedLog).logLevel = LogLevel.all` thread-safe?

If so, how is the user supposed to know that?

If not, where is the thread-safe equivalent?

ttanjo (@tom-tan) commented on 2024-03-30T03:37:33Z
Thank you for the information.
It works when I set `Loglevel.all` to both logger before calling logging methods  as follows.

```dlang
    ...
    (cast()sharedLog).logLevel = LogLevel.all;
    stdThreadLocalLog.logLevel = LogLevel.all;

    writeln("==== stdThreadLocalLog ====");
    stdThreadLocalLog.log("log");
    ...
```

> Perhaps this should be duplicated in the documentation for the `stdThreadLocalLog` property.

I guess the information of default logLevel in each logger should be in the `Thread Local Redirection` section in std.logger because most users read the documents in std.logger first.

Can I close this issue or leave it opened until the document is improved?
If the case of latter, I will send a pull request for it.

kinke commented on 2024-03-29T22:25:48Z
According to the docs (https://dlang.org/phobos/std_logger_core.html#.stdThreadLocalLog), `stdThreadLocalLog` just forwards to `sharedLog`. The latter has a default LogLevel of info. So in your example, you'd need to set the `sharedLog.logLevel` *before* logging to `stdThreadLocalLog` (which defaults to `LogLevel.all`, forwarding everything to the shared logger).

The key info is in the std.logger package docs (https://dlang.org/phobos/std_logger.html):
> The LogLevel of the stdThreadLocalLog can be used to filter log calls before they reach the sharedLog Logger.

Perhaps this should be duplicated in the documentation for the `stdThreadLocalLog` property.


[SPARK-48959][SQL] Make NoSuchNamespaceException extend NoSuchDatabaseException to restore the exception handling

What changes were proposed in this pull request?
Make NoSuchNamespaceException extend NoSuchNamespaceException
Why are the changes needed?
1, https://github.com/apache/spark/pull/47276 made many SQL commands throw NoSuchNamespaceException instead of NoSuchDatabaseException, it is more then an end-user facing change, it is a breaking change which break the exception handling in 3-rd libraries in the eco-system.
2, NoSuchNamespaceException and NoSuchDatabaseException actually share the same error class SCHEMA_NOT_FOUND
Does this PR introduce any user-facing change?
No
How was this patch tested?
CI
Was this patch authored or co-authored using generative AI tooling?
No

thanks, merging to master!

late LGTM.


need to support pynq-z2 board

currently only z1, ultra96, and zcu104 are supported.

I have fixed this on pull request #7


How can I get a kompilable kast for a program?

The following was sent on k-list. Since I didn't receive an answer yet, I include it here for recording.
I would like to write a rule of the form
rule funs =>
I used the "kast" program to get the kast of a particular program:
$ ~/k-3.6/bin/kast -e "two() { return 2; }" --parser "program"
'_(_){_}(#token("two", "Id"),'.List{"'_,_"}(.::KList),'return_;(#token("2", "#Int")))
Then I included in my definition the following rule:
rule funs
   =>

   `'_(_){_}`(#token("two", "Id"),`'.List{"'_,_"}`(.::KList),`'return_;`(#token("2", "#Int")))

and I got the following kompilation error:
$ ~/k-3.6/bin/kompile alk.k
[Error] Critical: Parse error: Syntax error near unexpected character '`'
Source(./../packages/compgeom.k)
Location(9,8,9,8)
The line 9 is the line including the rhs of the above rule.
So, the question is: "Having a definition in K, how can I obtain the kast of a given program s.t. I can copy-paste it in another K definition?"
This is useful, e.g., for loading libraries of programs.
For teaching purposes I still using K 3.6.

The KAST seems to be using the backtick syntax. That was introduced in K 3.6 but we decided against it in K 4.0. As far as I know, we never got to a point where we had a working roundtrip, printing a definition and being able to parse it back in K 3.6. This would likely work better in K 4.0, as we highly encourage you to use it if at all possible -- Elsa Gunter is also using it for teaching the Programming Language Design course at UIUC this semester.
My best advice right now would be to try to fix each case manually. @radumereuta, do you have any idea why the above doesn't work?

I expected that the kast generated with 3.6 can be compiled with K 3.6, but it seems that it doesn't.
When I started the teaching, K 4.0 was not released and therefore I preferred the last stable released version. The definition I use for teaching is quite complex and needs a significant effort to switch to K 4.0 and I have no time now. I will do it for the next year. Now I need a simple and stable solution that can be used by several hundreds of bachelor students in the first year.


does mkldnn support depthwise convolution?

does it support depthwise convolution?
If it supports, there is any  example?

Hi @kriszhangyf,
Formally speaking MKL-DNN supports groups, which covers the functionality of depthwise convolution:
dst[n][c][oh][ow] <-- src[n, c, ih, iw] (*) wei[c][1][1][kh][kw]

Here wei is 5D tensor of weights with number of groups = c, oc = 1, ic = 1, and kh x kw spatial.

Does it means that the out channel is still c?
can it supports the depthwide conv as
src[n, c, ih, iw] * wei[oc, 1, kh, hw] -> dst[n, oc, oh, ow]?
which oc = g*c

Convolution has strict definition, so
src[n, ic, ih, iw] (*) wei[oc, 1, kh, hw]

is illegal, since ic in source doesn't match ic in weights.

Hi @emfomenk,
Are there any updates on the optimized depthwise convolution?
Thanks

Hi,
we recently tuned gemm-based implementation for depwise convolution (see 967d7bf). Also we will promote avx2 specialized version for forward pass (maybe in few days).
If you want to check performance for mobile convolutions, you may use benchdnn with mobile-net input file: 3768fb22.

Just a quick update: optimized avx2 version is here 3edac962.

That's awesome! Thanks! I'm still struggling with compiling intel-caffe on macOS. Hope I can test it soon.

Hi @fei1107,
Depthwise convolution uses regular grouped API (basically ic = oc = g, so I think IntelCaffe already supports it (since IntelCaffe supports grouped convolutions).

Thanks! Do you mean that when ic = oc = g, Intel caffe will automatically run on the optimized depthwise convolution code rather than general convolution?

Many thanks! Does the depthwise conv support quantization for int8 on avx512 right now? And one last question, how can I fuse the convolution and relu layer in intel caffe, do I have to set some flag, or it can fuse automatically?Really appreciate for your answer!

Does the depthwise conv support quantization for int8 on avx512 right now?

Not sure I understand the question.

If you are asking whether MKL-DNN supports int8 depthwise convolution then the answer is yes, thought we don't have a kernel with direct implementation (so int8-gemm-based fallback will be used).

If you are asking whether you can quantize the input/weights (f32 -> int8) or dequantize output (int8 -> f32) then the answer is also yes. You can do that via reorders.

Also you can apply output_scaling factor for int8 depthwise convolution output.

Long story short, everything applicable for regular convolution is applicable for depthwise convolution as well (since in MKL-DNN depthwise convolution is treated as the regular one).

how can I fuse the convolution and relu layer in intel caffe, do I have to set some flag, or it can fuse automatically?

AFAIK, IntelCaffe will do some fusion on the fly. In particular it can merge convlutions followed by relu. It also can fuse convolutions followed by batch-normalization (on inference), and residual blocks (conv + relu + sum). For more details see: compile rules in net.cpp. You can also try running your topology and look at the output of IntelCaffe. If you run ResNet-50 you most likely will see something like:
...
I0305 23:44:59.466156  3880 remove_batch_norm.cpp:276] Dropped Layer: bn_conv1 # <-- batch normalization is fused
...
I0305 23:44:59.466895  3880 net.cpp:739] Dropped layer: res2a_branch2a_relu # <-- relu is fused
...

@emfomenk That's so great! I will try that after my network's training is done. Once again , thanks for your reply!

Hi @sfraczek, oc a multiple of ic = g is a valid convolution. In this case, within each group there are two output filters for each input filter. But note that unlike the case of depthwise convolutions (g = ic = oc), there is currently no jitted implementation, so convolutions such as mb1_g32ic32oc64_ih10oh10kh3ph1 will dispatch to gemm-based implementation.


[ 4p ] Login with validation

[x] Send Json request
[x] React Json request
[x] React to json request failure
[x] Save User to localstore if 201 with username and userid
[x] Redirect to HomePage

https://github.com/AdedayoOpeyemi/hotel_services_frontend/pull/9
Pull request link


Use all compatible versions when calculating tags.

Previously, we'd pass a single version to get_supported when we knew
one which would lead to a single tag being generated for the abi3 case
instead of one per previous minor version.
Fixes #539

NB: Not for review - getting a full CI burn before adding tests and possibly streamlining pex/platforms.py modifications a bit.

This is now ready for review.

Starting review now.
If you're able to, it would be helpful to break out a pre-cursor PR for the tweaks you make to the copied code, i.e. the indentation and the NB comments about what you changed from the copied code. Don't include the ABI3 changes. That way, this diff can be smaller and only include the changes you needed to make for ABI3 to work. Won't block on this though.

I filed #696 to track getting rid of these very confusing copies of doubly indirect and double modified copies of pip's glibc.py and pep425tags.py files.

Thanks for the reviews and please accept my apolgies for lack of reviewer notes. I'm adding them below for posterity.
1st, the actual changes to the pep425tags.py  and glibc.py files copied from out vendored setuptools:
$ diff pex/vendor/_vendored/setuptools/setuptools/pep425tags.py pex/pep425tags.py
0a1,6
> # NB: Copied from our vendored setuptools' version at:
> #   pex/vendor/_vendored/setuptools/setuptools/pep425tags.py
> # Modifications are marked with `# NB: Modified from ...`
> # TODO(John Sirois): Remove this file as part of https://github.com/pantsbuild/pex/issues/696
> # -------------------------------------------------------------------------------------------
>
3c9,16
< """Generate and work with PEP 425 Compatibility Tags."""
---
> """Generate and work with PEP 425 Compatibility Tags.
>
> NB: Several functions here have their code grabbed by `pex.interpreter._generate_identity_source`
> to use in runtime identification of python interpreter platform details. These functions are marked
> here and should maintain reliance on only stdlib support. Even then, any new imports added should
> be checked against those setup in `pex.interpreter.ID_PY_TMPL`.
> """
>
12d24
< import warnings
15,17c27
< from .extern import six
<
< from . import glibc
---
> from pex import glibc  # NB: Modified from `from . import glibc`
21a32,33
> # NB: Used in `pex.interpreter.ID_PY_TMPL` and should only rely on stdlib. If imports change,
> # please consult `pex.interpreter.ID_PY_TMPL` and adjust stdlib imports there as needed.
26c38
<         warnings.warn("{}".format(e), RuntimeWarning)
---
>         log.warn(str(e))  # NB: Modified from `warnings.warn("{}".format(e), RuntimeWarning)`
29a42,43
> # NB: Used in `pex.interpreter.ID_PY_TMPL` and should only rely on stdlib. If imports change,
> # please consult `pex.interpreter.ID_PY_TMPL` and adjust stdlib imports there as needed.
42a57,58
> # NB: Used in `pex.interpreter.ID_PY_TMPL` and should only rely on stdlib. If imports change,
> # please consult `pex.interpreter.ID_PY_TMPL` and adjust stdlib imports there as needed.
50a67,68
> # NB: Used in `pex.interpreter.ID_PY_TMPL` and should only rely on stdlib. If imports change,
> # please consult `pex.interpreter.ID_PY_TMPL` and adjust stdlib imports there as needed.
62,68c80,81
< def get_impl_tag():
<     """
<     Returns the Tag for this specific implementation.
<     """
<     return "{}{}".format(get_abbr_impl(), get_impl_ver())
<
<
---
> # NB: Used in `pex.interpreter.ID_PY_TMPL` and should only rely on stdlib. If imports change,
> # please consult `pex.interpreter.ID_PY_TMPL` and adjust stdlib imports there as needed.
80a94,95
> # NB: Used in `pex.interpreter.ID_PY_TMPL` and should only rely on stdlib. If imports change,
> # please consult `pex.interpreter.ID_PY_TMPL` and adjust stdlib imports there as needed.
98,103c113,119
<         if get_flag('Py_UNICODE_SIZE',
<                     lambda: sys.maxunicode == 0x10ffff,
<                     expected=4,
<                     warn=(impl == 'cp' and
<                           six.PY2)) \
<                 and six.PY2:
---
>
>         # NB: Modified from ~ `from .extern import six; six.PY2`
>         PY2 = sys.version_info[0] == 2
>         if (get_flag('Py_UNICODE_SIZE',
>                      lambda: sys.maxunicode == 0x10ffff,
>                      expected=4,
>                      warn=(impl == 'cp' and PY2)) and PY2):
104a121
>
317,319d333
<
<
< implementation_tag = get_impl_tag()

$ diff pex/vendor/_vendored/setuptools/setuptools/glibc.py pex/glibc.py
0a1,6
> # NB: Copied from our vendored setuptools' version at:
> #   pex/vendor/_vendored/setuptools/setuptools/glibc.py
> # Modifications are marked with `# NB: Modified from ...`
> # TODO(John Sirois): Remove this file as part of https://github.com/pantsbuild/pex/issues/696
> # -------------------------------------------------------------------------------------------
>
7c13
< import warnings
---
> from pex import pex_warnings  # NB: Modified from `import warnings`
45,46c51,53
<         warnings.warn("Expected glibc version with 2 components major.minor,"
<                       " got: %s" % version_str, RuntimeWarning)
---
>         # NB: Modified from `warnings.warn(..., RuntimeError)`
>         pex_warnings.warn("Expected glibc version with 2 components major.minor,"
>                           " got: %s" % version_str)

2nd, note that the code added to the top of platforms.py:

Moves the get_supported_for_any_abi from pep425tags.py to _get_supported_for_any_abi unaltered.
Moves the manylinux code previously embedded in the pep425tags.py get_supported code into _get_supported - changing to a post-filter technique for 0 disruption to the original pep425tags.py code.


Lockdown firewall rules for example network architecture for out/in perimeter routing

Depending on the vpc context (perimeter facing for example) - we just DENY everyone <IP_ADDRESS>/0 - another option
In the case of an internal VPC - those behind the perimeter - peer routing takes care of the public internet and we can allow <IP_ADDRESS>/0 for - however to be safe we should limit to the CIDRs of the peered VPCs
https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/blob/main/environments/common/prod-private-perimeter-firewall.auto.tfvars#L49
allow-ssh-ingress = {
  description          = "Allow SSH Connections from the internet"
  direction            = "INGRESS"
  action               = "deny"
  ranges               = ["<IP_ADDRESS>/0"]

20240406: Closing issue during retrofit/rebase of this TEF V1 based/modified repo to TEF V4 standards
This issue may participate in the LZ refactor after rebase
Query on all issues related to the older V1 version via the tag
https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/labels/2024-pre-tef-v4


Add instant reminder for P6S Transmission

In some "full uptime strats" like https://youtu.be/03kPYiaWBV8?t=109, players are required to do pre-position according to the buff they gain. It would be useful if cactbot can remind player instantly whether their buff is forwardCleave or backwardCleave.

This is great, but can you merge this into the main branch and not into the triggers branch? The triggers branch is just a "read only" javascript version for people to reference but the main branch in typescript is the real one.


wallet: Always skip conflicting txes in SelectCoinsGroupedByAddresses

How would you feel about a regression test? My understanding is this is a bug, no?


Open explorer

Little add-on which opens an explorer in the selected directory via File.Start E&xplorer menu or CTRL+E.
Is useful if your task can only be completed by e.g. Shell Extensions like archivers, renamers, ... from Explorer.exe
Has been discussed in #373

rebased onto master


Update host version to 2.0.14048 3.0.14063

conflicts?

Hmm, this is interesting since the master branch is already updated. Maybe I accidentally created 2 PRs doing the same thing. Closing now.


Rename master branch to main?

Is it a good timing to rename master branch to main?
I would like to hear member's (or other's) opinions on this issue.

If there's no technical reason to change, I'd leave it as-is


Consider browser overrides for module existence

Here's one conceivable fix for #177. It covers our use-case, and hopefully won't be unexpected behavior. Thoughts?
Happy to write tests for this - just want to know whether y'all think this is an appropriate solution.

Thanks for your work on this PR. We're getting ready to move this plugin to https://github.com/rollup/plugins and are tying up loose ends. Your Issue and PR raises good questions and we'll definitely make an effort to get it address.  We're definitely going to keep it around for reference, and will be transferring the issue to the new home when the move happens.


Fixing Filter + Filter Tests

The main issues with filtering are due to (1) inconsistent/confusing behavior for totally missing series (all NaN) and (2) the aggregating functions failed whenever a single entry in their argument arrays was NaN.
This PR moves the not-NaN filter from the applyAggregate function into each one of the aggregators, so that they can be used as useful summarizes for FilterBy.
The tests don't cover expression evaluation directly but do cover the functionality of FilterBy() which is used by expressions registered as filters.
FilterBy's argument "ascending" has been renamed to the more-clear "lowest" meaning that when true, it will return the N lowest results (if false, it returns the N highest). [This change doesn't effect behavior in calling the function].

LGTM


Certain custom formatting from spdlog doesn't work

Hi all, I'm currently evaluating spdlog-python as a replacement for logging in the python standard library.
Looking at the documentation from spdlog for custom formatting, it seems like there are some patterns that are not working/ supported.
These are:

%@ (Source file and line)
%s (Basename of the source file)
$g (Full or relative path of the source file)
%# (Source line)
$! (Source function)

I would presume some of it wouldn't work since it's a pybind11 wrapper of the cpp code. I wonder if there are other alternative to getting some of these working, especially the source function pattern?

@nicholas-presien did you find a way to make this work for you? I have the same issue. The solution mentioned here https://github.com/gabime/spdlog/wiki/3.-Custom-formatting#source-location-flags does not work for me.

Hey @justagist, I wasn't able to get it working, I think the information or context is lost when wrap in a python wrapper.
What I did was forcing the same logging format between spdlog and python logging for the entire application.


Requesting rewrite of first sentence in step 32 of the new JS course build an rpg

Describe the Issue
The first sentence of step32 of the new JS course learn-basic-javascript-by-building-a-role-playing-game states the following:
Use querySelector() to get the other two button elements, using their #button2 and #button3 ids.
Attempting to translate the last half of this sentence in Arabic is a challenge because the order of the code elements cannot be changed and in Arabic the phrasing as-is would be nonsensical.
The closest I could get in my attempt would have to be something like "...using #button2 and #button3 which are the values of their id attributes."
I can do this, but the overall effect is almost to obfuscate what it is we are actually trying to say because of the extreme wordiness that I would resort to.
I, therefore, propose a slight rewording and re-organization for this sentence which is to use :
Use querySelector() to get the other two button elements using their ids: button2 and button3.
Affected Page
https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/challenges/english/15-javascript-algorithms-and-data-structures-22/learn-basic-javascript-by-building-a-role-playing-game/62fc20387ef88d1d1998aac5.md
Your code

Expected behavior
My suggestion is to rewrite to this:
Use querySelector() to get the other two button elements using their ids: button2 and button3.
This separates the attribute name 'id' from the values to follow and allows for easier translation.
Screenshots
No response
System
N/A
Additional context
No response

I asked Dario and he said the suggestion is valid, so I am opening this for contribution.
If you would like to fix this issue, please make sure you read our guidelines for contributing, we prioritize contributors following the instructions in our guides. Join us in our chat room or the forum if you need help contributing, our moderators will guide you through this.

Sorry @Sboonny I think there is an additional issue with this sentence. The ids should be indicated without # before the id name. button1 is the id; #button1 is the id selector

We have a few places where that's unclean in our course content - I agree with dropping that #

I have removed the hashtags from the expected string.


Fail to test/sslapitest.c when use option DOPENSSL_TLS_SECURITY_LEVEL=0 in OpenSSL 3.4.0

When build OpenSSL 3.4.0 with option DOPENSSL_TLS_SECURITY_LEVEL=0. In step make test, an error occurred with test/sslapitest.c
# INFO:  @ test/helpers/ssltestlib.c:1289
# SSL_accept() failed -1, 11
# ERROR: (memory) 'p == expected_ciphers' failed @ test/sslapitest.c:735
# --- p
# +++ expected_ciphers
# 0000:-009dc02c00ff
# 0000:+009dc02c
#
# INFO:  @ test/helpers/ssltestlib.c:1289
# SSL_accept() failed -1, 1
# 40A71ED6677F0000:error:0A0000EA:SSL routines:tls_early_post_process_client_hello:callback failed:ssl/statem/statem_srvr.c:1710:
# INFO:  @ test/helpers/ssltestlib.c:1255
# SSL_connect() failed -1, 1
# 40A71ED6677F0000:error:0A000438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:ssl/record/rec_layer_s3.c:908:SSL alert number 80
# ERROR: (bool) 'create_ssl_connection(serverssl, clientssl, SSL_ERROR_NONE) == true' failed @ test/sslapitest.c:779
# false
# OPENSSL_TEST_RAND_SEED=1734598103
not ok 26 - test_client_hello_cb

I don't know what this error means, please help me claim it and how to fix.
I noticed there is a difference with the old OpenSSL version in
https://github.com/openssl/openssl/commit/972ee925b16fc3bc7ec71080c439e669754235ab#diff-ac041dcce48346a57d70403803133a58fb4ac5764e173d7cbfd6db2c2df5afdc

This is a bug in our tests. Fix in #26256.

I tested it, and the bug is fixed.


Hex.pm and Waffle pointing to old GitHub repository

👋🏽 Hi, I don't know if you're aware. But the Hex.PM and the Waffle GitHub is pointing to https://github.com/tyler-eon/waffle_gcs

Hi @ulissesalmeida.
Thanks for pointing it out and for the other comments/PRs you've made.
I haven't used waffle_gcs or Google Cloud Storage for a long time, so I've lost the incentive to maintain this project.
I see you're involved deeply with the waffle_gcs package, so if you're interested, I can transfer you its ownership on Hex.pm.

Thank you for the invite. The company I'm working at the moment uses GCS for minor things, so it's not a huge interest for me to maintain it. However, at the same time the library seems to be pretty stable.
@petermueller did review my goth PR, and seems to be an active participant before me. If @petermueller is interested I think Peter would a better candidate. If not, I would be happy to absorb the responsibility to apply the fixes and the goth upgrade, review and patch minor fixes.

I'd be happy to maintain or co-maintain w/ @ulissesalmeida.
I've a couple young kids, so I'm not sure me being the sole-maintainer would be advisable.
Would you be interested in something like that, @ulissesalmeida?

Yes! Much better!

@almirsarajcic, let me know if that's cool with you, and how you'd like us to handle where the repo lives :)

My hex.pm user is: https://hex.pm/users/ulissesalmeida
In case you want to share the management roles


Compile output files

Fixes #16.
TODO: find some way to test the custom imports.

Running this already reveals some issues with the current output:

Colors (rawValue): there's a value that appears twice (0xff66ccff)
Strings (structured/dot): there's a duplicate definition of Deeper (the case, and the sub-enum)
Images (dot-syntax): the struct init methods don't need to be public


Build Support API: Ticket Comments

Need to build, validate input, and test all the following endpoints for "Ticket Comments":

[x] List Comments
[x] List Email CCs for a Comment
[x] Redact String in Comment
[x] Make Comment Private

closed by #69


java.lang.UnsatisfiedLinkError: No implementation found for int com.github.mjdev.libaums.a.c()

'java.lang.UnsatisfiedLinkError: No implementation found for int com.github.mjdev.libaums.a.c() (tried Java_com_github_mjdev_libaums_a_c and Java_com_github_mjdev_libaums_a_c__) at com.github.mjdev.libaums.a.c(Native Method) at com.github.mjdev.libaums.a.a(Unknown Source) at com.github.mjdev.libaums.d.b.a(Unknown Source) at com.github.mjdev.libaums.a.a.a.a(Unknown Source) at com.github.mjdev.libaums.a.a.a.a(Unknown Source) at com.github.mjdev.libaums.c.a.a(Unknown Source) at com.github.mjdev.libaums.b.a.a.a(Unknown Source) at com.github.mjdev.libaums.b.a.g.a(Unknown Source) at com.github.mjdev.libaums.b.h.read(Unknown Source) at a.a.a.o.b(Unknown Source) at a.a.a.o.a(Unknown Source) at a.a.a.o.a(Unknown Source) at a.a.a.l.a(Unknown Source) at a.a.a.d.run(Unknown Source) at java.lang.Thread.run(Thread.java:818) '

This should not happen. If the c lib fails to load I am not using it: https://github.com/magnusja/libaums/blob/develop/libaums/src/main/java/com/github/mjdev/libaums/ErrNo.java#L16
Can you maybe give me an unobfuscated stack trace?


fix and add monitor and txwatcher tests

Scope
Testing Monitor and TxWatcher, adding some documentation for them
Why?
Increase code robustness
Todos
N/A

Codecov Report

Merging #87 (d7df7be) into main (bb2e65f) will increase coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #87      +/-   ##
==========================================
+ Coverage   45.61%   45.62%   +0.01%
==========================================
  Files         214      214
  Lines       38504    38504
==========================================
+ Hits        17563    17568       +5
+ Misses      19007    19006       -1
+ Partials     1934     1930       -4

Impacted Files
Coverage Δ

layer1/transaction/backend.go
0.86% <0.00%> (ø)

layer1/transaction/transaction.go
0.00% <ø> (ø)

layer1/transaction/worker_pool.go
0.00% <0.00%> (ø)

badgerTrie/smt_merkle_proof.go
64.84% <0.00%> (+3.90%)
:arrow_up:

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 bb2e65f...d7df7be. Read the comment docs.

LGTM, just waiting CI to pass


helix idealstate zk node size limitation with large pinot table

Hi, is there any suggested solution for pinot table with a large number of segments? We are currently trying a few tricks to alleviate this issue (enalbing zk compression, increase realtime.segment.flush.threshold.size config). However, it seems that pinot is still going to hit the idealstate zknode size limit if the table got large enough (around 5-10TB range)
also see the previous issue: https://github.com/linkedin/pinot/issues/2088 about too many segments causing ingestion issue.
Thanks
James

Can be solved by adjusting the ZK setting (documented here)


toolbar in clock activity not responsive

Whatever could be the screen size the Stop button should always visible to be sure the user will be able to quit the activity.
but here it is not in the case of clock activity.

The window size you're suggest doesn't match any real device and is not in landscape mode.
As mentioned here, activities are not suppose to be responsive in any condition.


Output each actor's soc time series in csv

The SOC is implicit to the load, production and price time series + battery + Strategy. What is however missing is the output of Actor.socs List into a result file.
Currently, the simulation has to be started to get the SOC values. Without simulation it is only possible to look into the orders.csv that is outputted during simulation and compare it with the load and production time series.

already merged in dev


Jetbrain's IDE's Connector

DataGrip provides a summary which information is needed to come up with a dedicated connector: https://www.jetbrains.com/datagrip/new_dbms/
Originally posted by @ckurze in https://github.com/crate/crate-clients-tools/issues/35#issuecomment-1941228270

It looks like JetBrains may have depublished their page? Here is an archived variant, but maybe you can find back a native source again?
https://web.archive.org/web/20240129181954/https://www.jetbrains.com/datagrip/new_dbms/
/cc @surister, @ckurze

I'm joining https://plugins.jetbrains.com/slack/ I will ask there :), I'd love to get CrateDB support for jetbrains, such a must for developer experience IMHO.

Asked again in their slack https://jetbrains-platform.slack.com/archives/C5P9YB0LT/p1733319820077659

Hi. We've refreshed the documentation about how to connect to CrateDB using DataGrip and the CrateDB JDBC Driver.
https://cratedb.com/docs/guide/integrate/datagrip/
Currently, the driver needs to be supplied manually by downloading and providing a JAR file.

Over here, we have a bug that needs to be addressed, most probably by adding a corresponding behavioral/dialect adjustment to the CrateDB JDBC Driver.

https://github.com/crate/crate-jdbc/issues/441

/cc @kneth

Jetbrain's devrel told me to follow up on https://youtrack.jetbrains.com/issue/DBE-12075/CrateDB-Full-Dialect-Support, left a comment there but it seems that it's up to them. I'll try to be active and follow up swiftly with them.

Thank you very much, @surister. So, the gist is:

The better your jdbc driver is implemented, the better is our basic support.

Indeed, CrateDB JDBC Internals outlines quite a bunch of things that can be done on the driver level already, essentially all the ingredients of that delta, plus something in the io.crate.client.jdbc wrapper. This is where @kneth is currently looking into.
What I almost certainly know is the detail that this gap of CrateDB, for example, seems to be masked, or otherwise not be an issue with the CrateDB JDBC driver, while it is an issue with current vanilla pgJDBC.

https://github.com/crate/crate/issues/12086

So, effectively, the CrateDB JDBC Driver should aim to compensate for all possible details like outlined per https://github.com/crate/crate/labels/tool%3A DataGrip, or otherwise CrateDB may improve on some of them? [^1]
[^1]: However, on a few significant on them, that might not be easy, and will take time.

NB
Within SQLAlchemy Core, we are doing many such compensations and masking in the act of re-using as many details from the PostgreSQL dialect adapter as possible, and adjusting them properly for the SQLAlchemy CrateDB Dialect. From our experiences there, we think it is business as usual, and should likewise be applied to Java/JDBC and downstream frameworks. It's too sad that DataGrip is closed source.


Take down nixos.wiki or set up URL redirect

I think that it is known at this point that NixOS now has an official wiki. But the old wiki (https://nixos.wiki) should be removed or have  the domain redirect to https://wiki.nixos.org.

This is not possible, since the admin of the old wiki doesn't want to do that.

Yeah. We tried everything https://github.com/NixOS/foundation/issues/113

:(