feature: support for proxy caching plugin based on disk.

Summary
This is a prototype implementation and there is a lot of work to be done.
Hopefully it does not affect the review. Thanks.
The admin api looks like the following:
{
    "plugins": {
        "proxy-cache": {
           "cache_zone": "disk_cache_one",
           "cache_key": "${uri}-cache-key",
           "cache_bypass": "${arg_bypass}",
           "cache_method": ["GET"],
           "cache_http_status": [200],
           "hide_cache_headers": true,
           "no_cache": "$arg_no_cache"
        }
    },
    "upstream": {
        "nodes": {
            "<IP_ADDRESS>:1999": 1
        },
        "type": "roundrobin"
    },
    "uri": "/hello"
}

Fix #1127

Currently only supports the upstream dynamically specify the cache time. If the upstream does not specify it such as the header Expires or Cache-Control, the cache_ttl in the config.yaml will be used.  And the option hide_cache_headers  will be decide whether the upstream header Expires and Cache-Control is sent to the client.
It's just a trick. Hopefully you can understand it.
Thanks.

how to add test cases for this plugin?

Hi
Tests cases I think the t/servroot/conf/nginx.conf file should be modified.
In recent days, i have been preparing to make a presentation. So I'm gonna add tests in this weekend.
And are there any other problems with code implementation?

How about the new style? I think the new style is simpler.
# current style
"proxy-cache": {
    "cache_key": ["$uri"]
    "cache_bypass": ["$arg_bypass"],
    ... ...
}

# new style
"proxy-cache": {
    "cache_key": ["uri"]
    "cache_bypass": ["arg_bypass"],
    ... ...
}

And I have other new questions:

need some e2e test case
need a way to purge the old cache

How about the new style? I think the new style is simpler.
# current style
"proxy-cache": {
    "cache_key": ["$uri"]
    "cache_bypass": ["$arg_bypass"],
    ... ...
}

# new style
"proxy-cache": {
    "cache_key": ["uri"]
    "cache_bypass": ["arg_bypass"],
    ... ...
}

Here can use variables or strings, so need an identifier to distinguish it.

And I have other new questions:

need some e2e test case
need a way to purge the old cache

I'm also considering these things. For 2 if there is no better solution, cache purge script will be the final choice.

And I have other new questions:

need some e2e test case
need a way to purge the old cache

e2e test cases I haven't figured it out yet. Do you have any suggestions?
Added.  Users only need to specify the method=PURGE to delete cache file. Please review it.

Thanks.

https://github.com/apache/incubator-apisix/pull/1153/files/56a1f42fd1e8bd30575856758a51e8a21acf2e4c..b3ccdb372520e2849871afe017591a148be4664c#diff-df639fd03e25e10ae720a3ccd80a9430R187
that is cool.

And I have other new questions:

need some e2e test case
need a way to purge the old cache

e2e test cases I haven't figured it out yet. Do you have any suggestions?
Added.  Users only need to specify the method=PURGE to delete cache file. Please review it.

Thanks.

@moonming @membphis

Do you have any suggestions for the test cases?
Moreover, I think I should figure out the logic of the APISIX test cases.
Thanks.

Please review @moonming @membphis

LGTM. Need add this plugin to README.md.
@membphis please take a look about how to add test cases.

OK. I'll add it to README. Basically test cases are covered.

@membphis  ping

@agile6v It seems that you have to rebase your branch, this branch has conflicted with master branch.

@agile6v It seems that you have to rebase your branch, this branch has conflicted with master branch.

Resolved.

LGTM, we can merge it after run the test cases.

merged, many thx @agile6v


Extra progress bars in the heatmap module

Using get heatmap, extra progress bars can be seen both in the optimization case and no optimization case.

@ShreyPandit Can you have a look at it?

Sent a PR request


I can't delete elements that contain an expression (but nothing else)

STR

New project, new component with prop username, return {props.username} or <span style={{ backgroundColor: props.username === 'malte' ? 'grue' : 'mauve' }}
Render component onto new scene
Select the span containing username
Delete it

Result: cannot
Expected: can, info toast telling you "The element you deleted contained an expression".

Reading this issue, it sounds like you're trying to delete the root element of the component? Is that right? If so, that's something we don't support yet, because we haven't come to a conclusion of what deleting the root element should actually do to the component.

Sorry, the STR missed an outer div - i.e. this ticket is for anything but root elements.

I've just tried with the following
import * as React from 'react'
export var App = (props) => {
  const b = 'light-blue'
  return (

      Some text

  )
}

I'm able to select and delete the span from the canvas (with the editor in "edit" mode), which makes me think this is the same issue as #1558, i.e. that the deletion did nothing because it's blocked in "select" mode, so maybe we shouldn't block it.

@Rheeseyb OMG I think that's it. Yes, I think we can allow this in select mode np


uart: Returns actual baudrate in uart_get_baudrate

The UART module cannot always be set to any specific baudrate which
means that the uart_get_baudrate was returning the desired baudrate
instead of the actual baudrate.
This commit computes the baudrate from UART3 registers in
uart_get_baudrate and removes the current_baud_rate variable.
Signed-off-by: Francois Berder<EMAIL_ADDRESS>

Closing this pr because this code breaks compatibility with LetMeCreate.


Updated ItemsRepeater Page

Description
Added two new samples: one sample that shows an ItemsRepeater with mixed-type items, and another that shows how to use nested ItemsRepeaters.
I also updated the sample code for all examples making them more detailed, and adding C# code-behind samples when relevant.
Motivation and Context

This is a part of my ongoing changes to the collections/layout pages of the Controls Gallery to make the samples easier to use for new developers, yet still helpful and interesting to experienced developers. For ItemsRepeater specifically, I wanted to keep the samples centered around interesting layout situations while showing off the flexibility of the control.
How Has This Been Tested?

Manually tested by me in dark mode and light mode, tried all possible combinations/options, etc.
Screenshots (if appropriate):

Types of changes

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

We also briefly chatted about moving this page to the Collections section of the Gallery. It looks like it is still under Layout. Double checking if you decided one way or the other.

We also briefly chatted about moving this page to the Collections section of the Gallery. It looks like it is still under Layout. Double checking if you decided one way or the other.

After discussing the samples with @pag3, we decided that keeping the ItemsRepeater page in the Layout section would be best as its more of a building block then a standalone collection control.

Additionally: I really like the look of the new samples. You could consider moving them to the top of the page.
He also suggested this specific ordering because it told the best story, in terms of how the features tie into one another/the ascending complexity of each sample.


Run all supported pytorch versions in CI

Currently, it seems that we only do conda install pytorch in CI, which will test (at the time of this writing) 2.2. If we want to claim we support other pytorch versions, let's add these to CI.

@ebsmothers do we still need this?


perf: globally cache intermediate type class results

See Zulip discussion here
This is a PR to determine whether this idea indeed results in faster type class search.

If this PR is created just to get the CI test, but you don't want people to look at and comment on the idea and implementation yet, using a “draft PR” makes it even more clear.


date-picker does not have a tabindex to make it focusable

Main issue is that tabindex does not work correctly, and you cannot focus a vaadin-date-picker in a vaadin-dialog
Solution might be extend vaadin-control-state so as it's aligned with other vaadin form elements

This is fixed right? @manolo

Fixed by #478
note: it seems that in order to target several issues by PR, each of them needs "fixes" or "closes" keyword, otherwise only the first one gets closed after merge (this is what happened here).


use packaging.version parse rather than raw string compare

as a string '0.0.9' is greater than '0.0.10' which is bad.
instead do
from packaging import version
version.parse('0.0.9') < version.parse('0.0.10')

"Creating a LegacyVersion has been deprecated"

... we may need to find a replacement version parser and/or write something custom to support x.y.z
May tie into #3 when we support more robust & configurable version strings

we should use the semver package
specifically 2.x.x as 3.x.x is still in development


[Bulk] Validation: validation fixes JM 6/8c

This PR fixes 29 issues.
-missing descriptions
-duplicate descriptions
-column headers

Global effort to fix build validation errors
@VesaJuvonen
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you'd like to see. Thank you!

Docs Build status updates of commit 1590717:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/schema/manifestfiles-element-deploymentsystemdata.md
:warning:Warning
View
Details

docs/schema/manifesturi-simpletype-sharepoint-add-in-manifest.md
:warning:Warning
View
Details

docs/schema/mapfile-element-feature.md
:warning:Warning
View
Details

docs/schema/mappedcrawledproperties-element-managedpropertyinfo-complextypesps15xsdsearchset.md
:warning:Warning
View
Details

docs/schema/mappedmanagedproperties-element-crawledpropertyinfo-complextypesps15xsdsearchset.md
:warning:Warning
View
Details

docs/schema/mappingdisallowed-element-managedpropertyinfo-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/mappinginfo-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/mappinginfo-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/mappinginfocollection-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/mappinginfocollection-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/mappingorder-element-mappinginfo-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/mappings-element-searchschemaconfigurationsettings-complextypesps15xsdsearchset3.md
:warning:Warning
View
Details

docs/schema/mappingsoverridden-element-overrideinfo-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/maptocontenttype-element-view.md
:warning:Warning
View
Details

docs/schema/matchingoptions-element-sps15xsdsearchset4.md
:warning:Warning
View
Details

docs/schema/matchingoptions-simpletype-sps15xsdsearchset4.md
:warning:Warning
View
Details

docs/schema/manifestfiles-element-deploymentsystemdata.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/manifesturi-simpletype-sharepoint-add-in-manifest.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mapfile-element-feature.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappedcrawledproperties-element-managedpropertyinfo-complextypesps15xsdsearchset.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappedmanagedproperties-element-crawledpropertyinfo-complextypesps15xsdsearchset.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappingdisallowed-element-managedpropertyinfo-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappinginfo-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappinginfo-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappinginfocollection-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappinginfocollection-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappingorder-element-mappinginfo-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappings-element-searchschemaconfigurationsettings-complextypesps15xsdsearchset3.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappingsoverridden-element-overrideinfo-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/maptocontenttype-element-view.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/matchingoptions-element-sps15xsdsearchset4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/matchingoptions-simpletype-sps15xsdsearchset4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

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

Docs Build status updates of commit eb5c718:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/schema/manifestfiles-element-deploymentsystemdata.md
:warning:Warning
View
Details

docs/schema/manifesturi-simpletype-sharepoint-add-in-manifest.md
:warning:Warning
View
Details

docs/schema/mapfile-element-feature.md
:warning:Warning
View
Details

docs/schema/mappedcrawledproperties-element-managedpropertyinfo-complextypesps15xsdsearchset.md
:warning:Warning
View
Details

docs/schema/mappedmanagedproperties-element-crawledpropertyinfo-complextypesps15xsdsearchset.md
:warning:Warning
View
Details

docs/schema/mappingdisallowed-element-managedpropertyinfo-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/mappinginfo-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/mappinginfo-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/mappinginfocollection-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/mappinginfocollection-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/mappingorder-element-mappinginfo-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/mappings-element-searchschemaconfigurationsettings-complextypesps15xsdsearchset3.md
:warning:Warning
View
Details

docs/schema/mappingsoverridden-element-overrideinfo-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/maptocontenttype-element-view.md
:warning:Warning
View
Details

docs/schema/matchingoptions-element-sps15xsdsearchset4.md
:warning:Warning
View
Details

docs/schema/matchingoptions-simpletype-sps15xsdsearchset4.md
:warning:Warning
View
Details

docs/schema/manifestfiles-element-deploymentsystemdata.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/manifesturi-simpletype-sharepoint-add-in-manifest.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mapfile-element-feature.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappedcrawledproperties-element-managedpropertyinfo-complextypesps15xsdsearchset.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappedmanagedproperties-element-crawledpropertyinfo-complextypesps15xsdsearchset.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappingdisallowed-element-managedpropertyinfo-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappinginfo-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappinginfo-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappinginfocollection-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappinginfocollection-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappingorder-element-mappinginfo-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappings-element-searchschemaconfigurationsettings-complextypesps15xsdsearchset3.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/mappingsoverridden-element-overrideinfo-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/maptocontenttype-element-view.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/matchingoptions-element-sps15xsdsearchset4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/matchingoptions-simpletype-sps15xsdsearchset4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

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

Global effort to fix build validation errors
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you'd like to see. Thank you!


multiple featurizations can create bugs in building regression models

If there is an error in featurizing, it will break the regression script in the model.py script - need to add error handling to all featurizers (zero arrays) in the event there is a bug. This can be a larger feature in a release.

Fixed with https://github.com/jim-schwoebel/allie/commit/fa69b40ea018b2459f4765ad38216b23ce28e732


Added a troubleshoot section to the english build guide.

Part of a series of PRs to improve the english build guide by adding some info that I would have wished was there when building the crkbd myself. Split into parts to make it easier to choose which part you want to accept and which to leave our or rewrite if necessary.
This is an attempt to add a troubleshooting section to the build guide, with the goal of addressing some of the issues I had during my build and what I think are measure you can take to remedy them. Would be great with some feedback on this, as this is my first keyboard build. See this a starting point to which info, tips and tricks from real build pros could be added. :)

Please resolve conflicts.


mvn 3.0 vs . mvn 3.3 // resolve dependency problems

Currently only maven  3.0.x creates a full functional running shaded jar. Building a shaded jar with mvn 3.3.x leads to a nonfunctional jar. Maven reports during packaging a lot of overlapping classes, which all comes from a com.spotify#docker-client dependency (depends on an outdated jackson.core#databind and maybe other libs). A fast solution is to remove any dependency to the JobProxyJavaDocker module. However we have to find a good solution to resolve such dependency problems ...

With PR #68 this might be fixes. We have to test it first with both maven versions.

Good work! Try both versions (3.0.4 from NB and 3.3.9), works!

Thanks! I'm happy to hear that! :-)


enhancement: implementation of caching for the user profile (aka resume)

The current system fetches data from GitHub API on every call request and is not backed by any caching services. This makes every API call costly (in sense of server costs and load).
To resolve all these issues we need a caching system.
Why implement caching?

Avoids rate limit for repeated requests
Faster response time
Less load on the server

Please assign this issue to me under GSSoC.

After implementing the caching, there are no API calls made to the GitHub servers to fetch the resume.

Should we start using upstash with redis?

Should we start using upstash with redis?

Yes

Before caching implementation: loading time 11.56 sec

After caching implementation: loading time 3.42 sec

Seems good go ahead. We will shift to graphql next


doesn't work when updated to slate 0.34.0

An update would be great, this plugin is what I'm looking for actually...
Or any will to release the current Gitbook Editor in open source guys?
Thanks!

Sorry for the lack of update. Since we have forked Slate (https://github.com/GitbookIO/slate), we are no longer maintaining this plugin for the upstream version.
I invite you to look for forks or ask for alternatives in Slate's Slack community


[SPARK-48866][SQL] Fix hints of valid charset in the error message of INVALID_PARAMETER_VALUE.CHARSET

What changes were proposed in this pull request?
This PR fixes hints at the error message of INVALID_PARAMETER_VALUE.CHARSET. The current error message does not enumerate all valid charsets, e.g. UTF-32.
This PR parameterizes it to fix this issue.
Why are the changes needed?
Bugfix, the hint w/ charsets missing is not helpful
Does this PR introduce any user-facing change?
Yes, error message changing
How was this patch tested?
modified tests
Was this patch authored or co-authored using generative AI tooling?
no

cc @LuciferYang @dongjoon-hyun @cloud-fan thanks

Merged into master. Thanks @yaooqinn


Rustup

@bors r+

:pushpin: Commit 9ff2debceb3fd288e1568f677c8f62f5e1c12aa2 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 9ff2debceb3fd288e1568f677c8f62f5e1c12aa2 with merge a98e55e9d73523fddfbfc7d841a7135932c78955...


Merge branch 'release/2.1' into release/2.2

#2709

Merged here: https://github.com/aspnet/KestrelHttpServer/commit/864cfeb2aa1921188fd66eccbeaddf4155f47ad6


inline namespaces to move namespaces up top

is there a fixer that moves all inline long namespaces on a codebase to the top and shortens the names automatically?

You mean something like;
expected;
    use Symfony\CS\Tokenizer\Tokens;

    public function a()
    {
        $a = new Tokens();
    }

input:
    public function a()
    {
        $a = new \Symfony\CS\Tokenizer\Tokens();
    }

No, there isn't one here.

will there be ever one?

You are welcome to contribute @cordoval !

would be terrific, i have no time now but will certainly look if you help me

This could be nice for a start:
https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/1.12/COOKBOOK-FIXERS.md

+1

:-1: We have no way to do this without potentially breaking the code due to collisions with existing class names in the same namespace.

it should be a controlled run rather than a totally automated thing, i can go and fix some left overs for sure, it is just so tedious sometimes

@GrahamCampbell usually the use scenario is that the people choose really separate class names so even if i try to create collisions there is none. So this fear should be remedied with a stern warning about this or just have the fixer not do the changes when in doubt, for everything else it should tackle the refactor. Does this option sound better?

i went and solved it by hand since phpstorm had the feature so closing.

@cordoval where is the feature in phpstorm? I didn't find it. :-/


fix broken item linkages in prior PR

hopefully this one does the trick!

I force merged this (hopefully correctly) using the command line


Make it more obvious when things are filtered

Hi,
I am trying to place trees in a farmland paddock however they are not displaying in ID 2.8.2 on Google Chrome 66. This appears to have been occurring during May 2018
** Validation Process **
Check changeset 59271085 https://www.openstreetmap.org/changeset/59271085#map=16/-34.2854/141.8505 and you should see four nodes created, all around the two areas of scrub.
Edit the area and you should see two trees to the east and one tree to the north west plus one to the south. All four should show nodes with natural=tree hover no nodes are located at any zoom level. This is the failure

Go to JOSM or Overpass to the area around -34.28331,141.85103 and you will be able to locate the multiple tree nodes (one tree from each past changeset) that exist proving that ID  is not rendering.

Hmm weird.. I see the trees.. Do you have points filtered?

@bhousel , Thank you! I must have selected it accidentally when swapping the fill area style. Many thanks
I did notice the "19 hidden feature"s pop up in blue on the status bar but didn't put 2 and 2 together. Now to get rid of the duplicated trees.

Thanks @EwenH - glad there was no loss of data 👍
I do want to improve iD's filtering behavior to make it more obvious.  This is something that @geohacker and I were chatting about this week.

This was done in #5876.


Error when build game

You Did Not Rebuild It
Please Think Before Making Issues Like This
lime rebuild extension-webm windows


Add a toggle for DHCP default route advertisement

This PR is part of a workaround for https://github.com/PlanktoScope/PlanktoScope/issues/201. Specifically, it moves the PlanktoScope's advertisement of itself as a default route to the internet from default behavior into a new planktoscope-dhcp-default-route feature flag provided by the core/host/networking/interface-forwarding package. Regardless of whether that feature flag is enabled, the PlanktoScope can still resolve IP addresses such as <IP_ADDRESS> and <IP_ADDRESS> from any connected interface.

I tested this on a PlanktoScope's local pallet, and it worked! So I will merge this PR now.


Update bootstrap version to V4.0.0 alpha.2

Initial work for using Bootstrap 4, would wish for an official version

The official version of the Bootstrap 4 Ruby gem is at https://github.com/twbs/bootstrap-rubygem.


[Bug] tpu-info can not access metrics

Minimal working code is Here. Code follows GoogleCloudPlatform example
Code run completed successfully on TPU VM v3-8, but while call !tpu-info at the end, it shows:
TPU Chips
┏━━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━┓
┃ Chip        ┃ Type        ┃ Devices ┃ PID ┃
┡━━━━━━━━━━━━━╇━━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━┩
│ /dev/accel0 │ TPU v3 chip │ 2       │ 13  │
│ /dev/accel1 │ TPU v3 chip │ 2       │ 13  │
│ /dev/accel2 │ TPU v3 chip │ 2       │ 13  │
│ /dev/accel3 │ TPU v3 chip │ 2       │ 13  │
└─────────────┴─────────────┴─────────┴─────┘
Libtpu metrics unavailable. Is there a framework using the TPU? See https://github.com/google/cloud-accelerator-diagnostics/tree/main/tpu_info for more information

Minimal working code is Here. Code follows GoogleCloudPlatform example
Code run completed successfully on TPU VM v3-8, but while call !tpu-info at the end, it shows:
TPU Chips
┏━━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━┓
┃ Chip        ┃ Type        ┃ Devices ┃ PID ┃
┡━━━━━━━━━━━━━╇━━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━┩
│ /dev/accel0 │ TPU v3 chip │ 2       │ 13  │
│ /dev/accel1 │ TPU v3 chip │ 2       │ 13  │
│ /dev/accel2 │ TPU v3 chip │ 2       │ 13  │
│ /dev/accel3 │ TPU v3 chip │ 2       │ 13  │
└─────────────┴─────────────┴─────────┴─────┘
Libtpu metrics unavailable. Is there a framework using the TPU? See https://github.com/google/cloud-accelerator-diagnostics/tree/main/tpu_info for more information

Same issue for me on different TPUs (v3 or v4)

@will-cromar @SurbhiJainUSC @bvandermoon Please take a look, Thanks

I am seeing the same issue. Using jax, and creating a v4-8 from --runtime-version tpu-ubuntu2204-base.
I see the comment about "Releases from before 2024 may not be compatible.". However, it is not clear to me what that refers to, and what needs to be updated.


Errno::E086: Bad CPU type in executable

Summary
I've recently started seeing this error when I run my feature tests in rails using capybara and the geckodriver webdriver
Errno::E086:
       Bad CPU type in executable - /Users/rreynolds/.webdrivers/geckodriver

Debug Info

Webdrivers version: 4.6.0 and 4.6.1
Ruby version: 2.4
Operating system / CI Environment: Big Sur 11.4
Browser and version: Chrome Version 94.0.4606.54 (Official Build) (x86_64)

Expected Behavior
Capybara feature tests should open up a firefox browser window and run. It has done this until very recently.
Actual Behavior
 Errno::E086:
       Bad CPU type in executable - /Users/rreynolds/.webdrivers/geckodriver
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/webdrivers-4.6.1/lib/webdrivers/system.rb:187:in `popen'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/webdrivers-4.6.1/lib/webdrivers/system.rb:187:in `call'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/webdrivers-4.6.1/lib/webdrivers/common.rb:152:in `binary_version'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/webdrivers-4.6.1/lib/webdrivers/geckodriver.rb:17:in `current_version'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/webdrivers-4.6.1/lib/webdrivers/common.rb:134:in `correct_binary?'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/webdrivers-4.6.1/lib/webdrivers/common.rb:91:in `update'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/webdrivers-4.6.1/lib/webdrivers/geckodriver.rb:72:in `block in <top (required)>'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/selenium-webdriver-3.142.7/lib/selenium/webdriver/common/service.rb:133:in `binary_path'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/selenium-webdriver-3.142.7/lib/selenium/webdriver/common/service.rb:94:in `initialize'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/selenium-webdriver-3.142.7/lib/selenium/webdriver/common/service.rb:58:in `new'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/selenium-webdriver-3.142.7/lib/selenium/webdriver/common/service.rb:58:in `firefox'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/selenium-webdriver-3.142.7/lib/selenium/webdriver/common/driver.rb:299:in `service_url'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/selenium-webdriver-3.142.7/lib/selenium/webdriver/firefox/marionette/driver.rb:38:in `initialize'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/selenium-webdriver-3.142.7/lib/selenium/webdriver/firefox/driver.rb:33:in `new'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/selenium-webdriver-3.142.7/lib/selenium/webdriver/firefox/driver.rb:33:in `new'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/selenium-webdriver-3.142.7/lib/selenium/webdriver/common/driver.rb:54:in `for'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/selenium-webdriver-3.142.7/lib/selenium/webdriver.rb:88:in `for'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/capybara-3.32.0/lib/capybara/selenium/driver.rb:52:in `browser'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/capybara-3.32.0/lib/capybara/selenium/driver.rb:71:in `visit'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/capybara-3.32.0/lib/capybara/session.rb:278:in `visit'
     # /Users/rreynolds/.rvm/gems/ruby-2.4.1/gems/capybara-3.32.0/lib/capybara/dsl.rb:58:in `block (2 levels) in <module:DSL>'
     # ./spec/support/feature_spec_helpers/sessions.rb:3:in `sign_in'
     # ./spec/features/client/choosing_session_loanset_spec.rb:8:in `block (2 levels) in <top (required)>'

Hmmm, I think I fixed it. I just deleted everything in ~/.webdrivers and then ran my specs again. The webdrivers gem seems to have redownloaded the geckodriver. Perhaps my binary got corrupted...


Break out XLSX Support or release an alasql core

Thank you for your awesome work. This is an excellent library.
A huge portion of the code weight is devoted to supporting xlsx. While that may be a big portion of your users, it's not all of them. It would be great if there was a way to do a build without this code. I'm not sure where this stands in your priorities, but it seems like it might be a relatively easy task so I'd like to really advocate for this.
Thanks again and keep up the great work.

This is one of the most important elements: to build the library so you can select what parts you need.
There is work in progress in the feature/plugin_structure branch primary driven by @nickdeis
If you would like to help out that would be really awesome.

I'm interested in helping out, but to be honest your code structure is very very confusing.

It really is :)
That is why nickdeis is working on restructuring it to be small individual modules requiring each other (all his work is placed in https://github.com/agershun/alasql/tree/feature/plugin_structure/ecma6 )
Ill ask him if he can write a short description on how to start contributing

That's awesome, thanks!

Completely agree.  I was going to write a ticket about how we should do plugins. XLSX and XLS were my first target. The vast majority of the alasql codebase works by attaching itself to the global alasql object, so I was trying to organize the codebase to reflect that.
While certainly not elegant, I was thinking a plugin would simply be a function passed through some function (alasql.plugin?) and just do what it needs to do.
Let me see if I can write up an example this week.
I'll try to add README to each directory. Alasql is full of hidden secrets, which is probably a bad thing, but once you get the idea things kind of make sense.
Nice to be working with a fellow DC programmer btw.

Alasql is full of hidden secrets, which is probably a bad thing, but once you get the idea things kind of make sense

:+1:

@nickdeis :wave:
Here's an example of how I handle plugins in my project: https://github.com/koopjs/koop/blob/3.0/src/index.js#L155-L166
Perhaps not elegant but it works well in practice.

@mathiasrw
Do we plan on updating the typescript definition files?
If so, the AlaSQLCallback is a little out of date.
For the sake of documentation and the plugins, I've added typescript definition files for things other the from, into, and engine namespaces (eg: alasql.from).
I think the best way to approach the XLSX plugin is to have it implement a AlaSQLFrom functional interface, and likewise a ALASQLInto functional interface.

Do we plan on updating the typescript definition files?

Good you point it out.
I have never worked with typescript definition files. I will look into how to get them updated.

I have pushed a new version of the typescript definition: https://github.com/agershun/alasql/blob/develop/dist/alasql.d.ts
@nickdeis would you be so kind to check if its working?

It is sort of working: AlasqlCallbacks (cb) typically take three arguments. However, that's enough for me to work with.
Should these plugins be build time or run time? I'm leaning toward build time.

Im in strong favour of build time...
If it will help you if I get the typescript more correct please let me know.

Let me see if I can write up an example this week.

@nickdeis did you ever get to describe with a few lines how to compile / run the new plugin structure ?

@mathiasrw  Sorry about the delay. This a lot more architectural astronautics than I'm use to.
Example: (I don't really care if we keep plugins in separate repos or not).
alasql-plugin-xlsx.
I tried to design them to the best of my knowledge on how to write a good plugin, and what other plugin heavy libraries do. All of them have a well defined inversion of control where the plugins are not aware of the parent library.
I will write the core attachment code next.
Tell me what you think

@nickdeis Quick question: How do I testrun the ecma6 structure? Is it just to (forexample) browserify ecma6/global/start.js and then go play?

[Go to a flavor folder|https://github.com/agershun/alasql/tree/feature/plugin_structure/ecma6/flavors/slim]
gulp
Should produce the slim build

@dmfenton + @mathiasrw
This plugin might have to get ugly because of some interesting features in the XSLX library.
Good thing we are breaking it out as a plugin!
I just have to use webpack instead of rollup

@nickdeis nice - thanks...
@dmfenton is this enough to get you started?

Go to a flavor folder
gulp


Only build pushes to master

Coverage remained the same at 60.0% when pulling 0e548d3ac61f761de4d88cb0a590f1cb3e1e3199 on feature/travis-fix into 7c5438e6b5c21860ef65d7210a34f462e7b9d0fa on master.

Coverage remained the same at 60.0% when pulling 8ba37da0631bd45a65f6a056be3766e0b85dfb60 on feature/travis-fix into 7c5438e6b5c21860ef65d7210a34f462e7b9d0fa on master.

Coverage remained the same at 60.0% when pulling 637265877d781d37160cde7b6bda336ed346e4a3 on feature/travis-fix into 7c5438e6b5c21860ef65d7210a34f462e7b9d0fa on master.

Coverage remained the same at 60.0% when pulling c10f2aaae9ed85ca425ad3683823807a19278501 on feature/travis-fix into 7c5438e6b5c21860ef65d7210a34f462e7b9d0fa on master.

Coverage remained the same at 60.0% when pulling 348e5593928a0ed0f164191b4f6499a0a6908a63 on feature/travis-fix into 7c5438e6b5c21860ef65d7210a34f462e7b9d0fa on master.

Coverage remained the same at 60.0% when pulling<PHONE_NUMBER>7acf839df00d0cba24178711f72ba0 on feature/travis-fix into 7c5438e6b5c21860ef65d7210a34f462e7b9d0fa on master.


Refactor: QuizQuestion model

Part of an ongoing code refactoring to move all models to a common models package.
Fixes #4782
Moved QuizQuestion to data.models package.
Tested debug on Pixel 4 (Emulator) with API level 30.

Hi, is this PR sleeping @ben-mathu ?:)

Closing: 2 years old and looks abandoned.


flaky smoke tests

happened again

TBH I do not know what went wrong here and there are other smoke test failures which I do not own. I see all of them are running fine locally.
Since there is no action can be taken, closing this.


Added USE_CONFIDENTIAL_COMPUTING check

Problem: A node operator cannot check or add support for confidential computing.
Solution: Implemented a setting to allow node operator to enable confidential computing. A check ensure that the system is well configured, and it shows that configuration on the /public/config endpoint.
Implementations:

Added USE_CONFIDENTIAL_COMPUTING setting with a False default value. If the user enables it, it checks the module availability on the system.
Added a new computing section on /public/config endpoint with relevant information about computing.
Added PAYMENT_MONITOR_INTERVAL field on payment section on /public/config endpoint to show the payment interval check.

I suggest we change the name to ENABLE_CONFIDENTIAL_COMPUTING or ENABLE_CONFIDENTIAL_SUPPORT, because "use" for me imply that it will be used by default, while  "enable" tell to make it available.
For example USE_JAILER : mean jailer is used for all program, the user launching a program cannot choose when it's used or not.
But ENABLE_QEMU_SUPPORT make the backend available for users


Polyculture progress report for meeting 2023-03-21

As requested by @markus2330 .

Basics

[x] Details of what you changed are in commit messages
(first line should have module: short statement syntax)
[ ] References to issues, e.g. close #X, are in the commit messages.
[ ] The buildserver is happy.
[x] The PR is rebased with current master.

Checklist

[ ] I added unit tests for my code
[ ] I fully described what my PR does in the documentation
(not in the PR description)
[ ] I fixed all affected documentation
[ ] I fixed all affected decisions
[ ] I added code comments, logging, and assertions as appropriate
[ ] I mentioned every code not directly written by me in reuse syntax

Review

[x] Documentation is conforming to our Documentation Guidelines
[ ] Examples are well chosen and understandable
[ ] Code is conforming to our Coding Guidelines
[ ] Code is consistent to our Design Decisions

Thank you! Please also a longer report to  #116.


Fix compile errors, render items in hand, and reenable all catwalks

The first two commits get this project to build again. The next two are fluff. The fifth one successfully renders Catwalk items both in hand and in inventories by equipping CatwalkBakedModel to be rendered as an item, adding a default CatwalkRenderData and applying the forge-default item camera transforms via changes to BaseBakedModel and callers. The sixth commit repairs the model and texture paths for all of the catwalks I could find. The seventh commit is probably wrong, but it causes the material IDs passed to the item registry to line up with the ones in EnumCatwalkMaterial. The eighth commit is the continuation of the fifth, allowing Scaffolds to render in hand and in inventories.
By the way, I love the new models!

thecodewarriors!

Thanks!


Make paragraph longer to fix content width

This page is formatted really narrowly because the paragraphs were so short. Until we have more info to add here, combining separate sentences into a single paragraph fixes the formatting.
Before:

After:

I don't think this will be a good fix because it happens on other pages
https://docs.etherlink.com/building-on-etherlink/token-addresses
Could we include a global style for page width? https://docusaurus.io/docs/styling-layout#global-styles

I don't think this will be a good fix because it happens on other pages https://docs.etherlink.com/building-on-etherlink/token-addresses
Could we include a global style for page width? https://docusaurus.io/docs/styling-layout#global-styles

This appears to be caused by a custom style we added to keep the sidebar wide enough. I'll see if there's a way to fix this while keeping the sidebar wide enough:
https://github.com/etherlinkcom/docs/commit/7b46288c16dfec1821ecf25609abfde45c0ef3df

@devon-n How does  this look? I removed a style that was causing the problem: https://docs-etherlink-git-fix-page-width-trili-tech.vercel.app/tools/price-feeds


Not able to use angular-json-editor and ng-jsoneditor together

Hey,
I'm stuck into a problem,
angular-json-editor and ng-json-editor both are using a json-editor.js file, so i'm facing some conflict problem and not able to solve issue by my self.
<json-editor schema="deviceSh" startval="deviceValSh" buttons-controller="addDeviceED1Ctrl" id='editor_holder'>
        </json-editor>

The directive above is loading ng-json-editor not angular-json-editor.

Hey,
I am not familiar with ng-json-editor, so I am not sure as to what is it's purpose.
Other than that, I don't see any reason for a conflict, as angular-json-editor uses the Element restriction for the directive, and ng-json-editor (as far as I can see) uses the Attribute restriction.
This means that <json-editor> which calls my directive, is different from <div json-editor> which calls ng-json-editor's directive.

Hey,
Can you explain more about your use case?
What is ng-json-editor, and what is it's use?
I am not sure how Angular handles multiple directives with the same name, so it might be overwriting my directive with ng-json-editor's definition.

had the same problem. the problem is that both json editors use window.JSONEditor. i ended up renaming one.
        <!-- this is https://github.com/josdejong/jsoneditor, and will be exposed as window.JSONTreeEditor -->
        <script src="bower_components/jsoneditor/dist/jsoneditor.min.js"></script>
        <script type="text/javascript">
            window.JSONTreeEditor = window.JSONEditor
            delete window.JSONEditor
        </script>
        <!-- this is a wrapper around the above, directive called <ng-json-tree-editor> -->
        <script src="/ng-json-tree-editor.js"></script>
        <!--this is https://github.com/jdorn/json-editor, and will be exposed as window.JSONEditor-->
        <script src="bower_components/json-editor/dist/jsoneditor.js"></script>
        <!--wrapper around the above (https://github.com/rodikh/angular-json-editor), directive called <json-editor> -->
        <script src="bower_components/angular-json-editor/dist/angular-json-editor.js"></script>


Feature/variable suffix

Adds support var using variables in Suffix() expressions as requested in #998
e.g:
var prop = "propXY12";
P(p => p.Name.Suffix(prop)).Should().Be("name.propXY12");

This PR also fixes a bug where IDictionary<TKey, TValue> expressions would fail unexpectedly where `Dictionary<Tkey, TValue> worked fine.

Nice!  LGTM :+1:


Need to add timestamp in logs

There are currently no timestamp in the log, which makes analysis difficult

Done with commit c105e08


Handle RemoveFlightFromTrip

HTD: RemoveFlightFromTrip should give the user a list of the flights in their trip and allow them to choose one to remove from the trip. The flight should then be deleted from the trip's list and the UIState should be set back to updateTrip

Worked on for 1.5 hours

Worked on for additional 1.5 hours, ready for testing


Fix Xvnc backend disconnects when some data copied to clipboard

Should fix #755.

I tested these 4 scenario works fine (no disconnection, copy & paste works).
Now clipboard is working fine with Windows 7 mstsc, MS Remote Desktop for Mac 8.0.40 (Build 27310) however not working with FreeRDP due to FreeRDP/FreeRDP#3309.

Xvnc backend + clipboard sharing enabled client side
Xvnc backend + clipboard sharing disabled client side
vnc-proxy + clipboard sharing enabled client side
vnc-proxy + clipboard sharing disabled client side

Let's merge and observe.


Sync Settings and extensions on user login

WE Need Supprate Sync Settings and extensions on user login, Just like Chrome, So we can Sync All data After login in New PC
irrespective to the GitHub in the project

This feature is available already - https://code.visualstudio.com/docs/editor/settings-sync


obsolete

app.UseOpenIdConnectAuthentication(...) is obsolete. http://go.microsoft.com/fwlink/?linkid=845470

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

ID: 41684cfd-250e-251f-b059-1ca2ea2464bf
Version Independent ID: d3b0a0ea-5d1f-0408-61bf-1fd95bacf00c
Content: Call a secured web api ASP.NET Azure Active Directory B2C
Content Source: articles/active-directory-b2c/active-directory-b2c-devquickstarts-web-api-dotnet.md
Service: active-directory-b2c
Product: unspecified
GitHub Login: @davidmu1
Microsoft Alias: davidmu

@jaider Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@jaider Thanks for the feedback. The article needs to be updated in conjunction with an update to the sample that it points to. I have opened a workitem to track this work and will report back to the issue when complete.

Is there any update on this. This is still one of the highest ranking pieces on getting B2C authentication to work between Apps and Api, and it would be good if was maintained.

As the author of the article I'm responsible for the content of the article itself. The engineering team owns the sample. The sample needs to be changed and the engineering team is working on new samples. Because there isn't actually a change to this article, I think the issue should be closed.
#please-close


Update community_connectors.json

Coverage remained the same at 98.913% when pulling 794a527d5294d4b26c029f27548c189b43c824c7 on NeelShah00:patch-1 into 247887b8ae2409238f71d5e2e37f6d260dbe54e6 on tableau:master.

What should I do to resolve this?

Hi @NeelShah00
Thank you for submitting your WDC.
Your WDC is working but the interface is confusing. Did you try to host it on a different platform? We listed some options here: https://tableau.github.io/webdataconnector/docs/wdc_hosting_and_submissions.html
Can you also update the description to give your details on the data, please?

Absolutely, I had prepared my WDC with the help of Javascript and html. It is divided into two parts:

I had made html website on the Blogger
I had hosted Javascript file on google Drive

Working: when the user clicks on the get data button it executes the file uploaded on google drive
Data: I had acquired precise data from the official government website of india for coronavirus
Website: https://www.covid19india.org

Hi - Do you think you can edit the HTML. The Blogger interface might be confusing for users.

Yes, lately I had made changes to the HTML and removed ambiguous components from them. Kindly, check the update and let me know if any changes are necessary.


[SR-4195] non throwing whitelist

Changes the whitelist method to filter out non whitelisted flags instead of throwing when a non-whitelisted flag is found.
Background
Currently Vapor is using a custom pkgconfig-like system to gather and apply build flags. This works through a vapor.json file at the root of the repository (e.g, mysql) that the Vapor toolbox can then parse and use to apply flags.
Obviously this solution only works if the end user is using the Vapor toolbox, and has made it difficult for Vapor developers to use native SPM (swift build, swift test, etc) commands.
In Vapor 2, we were hoping to move to the pkg-config system to remove the need for build flags in native SPM and the custom Toolbox build flag system.
This has worked so far really well except for one blocking issue [SR-4195].
Issue
Build flags not whitelisted by SPM are failing the builds. So common .pc files like MySQL's which has some additional build flags prevent SPM from compiling.
Solutions
Discard
Discarding any non-whitelisted build flags and warning that they've been discarded would allow many more .pc files to be compatible with the SPM build system.
This is the approach taken in this PR.
Add Specific Flags
The flags causing MySQL's .pc file to fail could be added to a "discardable" list of flags.

-fabi-version=2
-fno-omit-frame-pointer

This solution still has the potential issue of breaking builds for some .pc files we may not yet know about.
Manually Modify .pc files
We could distribute commands to remove these non-whitelisted flags from the .pc  files themselves such as:
# linux
sudo sed -i 's/-fabi-version=2 -fno-omit-frame-pointer/ /g' /usr/lib/x86_64-linux-gnu/pkgconfig/mysqlclient.pc
# macos
sudo sed -i '.bak' 's/-fno-omit-frame-pointer/ /g' /usr/local/opt/mysql/lib/pkgconfig/mysqlclient.pc

This solution is not ideal since it creates extra steps for the end user and could create issues elsewhere.
Swift 3.1
This issue will make or break Vapor's ability to use the pkgConfig system in Swift 3.1 (which Vapor 2 will be relying on). As such, we would greatly appreciate this issue being viewed as a bug and to help patch it in time for Swift 3.1.

Thanks for the clear and detailed explanation, Tanner. Unfortunately I think it's too late to get further fixes into Swift 3.1. I'll double-check with Ted before closing this PR, however. In the meantime, you should definitely get this into master. I'm not sure if we're going to do a 3.1.1, but if we did this would also be a good candidate fix to pull in at that time.

As @rballard says this is very late for 3.1.  Let's take for the 3.1 branch as there is always the possibility of minor updates to 3.1 (which will be assessed based on the changes driving an update).

This should go into master first, however.   All changes should be staged that way.   We should never propose a change for the release branch until it is already on master.

@tkremenek @rballard that's understandable. I've re-opened this PR against the master branch. https://github.com/apple/swift-package-manager/pull/1010


bug: select and with_columns don't always preserve column index name for pandas-like

import pandas as pd
# import narwhals.stable.v1 as nw
import narwhals as nw

df = pd.DataFrame({'a': [1,2,3], 'b': [4,5,6]})
df.columns.name = 'foo'

print(nw.from_native(df).select(c=nw.col('a')+1).to_native())
print(nw.from_native(df).with_columns(c=nw.col('a')+1).to_native())
print(nw.from_native(df).to_native())
print(nw.from_native(df).to_native().assign(c=lambda df: df['a']+1))

outputs
   c
0  2
1  3
2  4
   a  b  c
0  1  4  2
1  2  5  3
2  3  6  4
foo  a  b
0    1  4
1    2  5
2    3  6
foo  a  b  c
0    1  4  2
1    2  5  3
2    3  6  4

expected:
foo  c
0    2
1    3
2    4
foo  a  b  c
0    1  4  2
1    2  5  3
2    3  6  4
foo  a  b
0    1  4
1    2  5
2    3  6
foo  a  b  c
0    1  4  2
1    2  5  3
2    3  6  4

having said that...should we really care? is this in-scope for Narwhals? not totally sure I want to deal with multi-index columns' names weirdness

should we really care?

I feel slightly uncomfortable not caring about it. Some "meta" information might be easy(er) than expected to preserve. Except at the same time I totally share this take:

not totally sure I want to deal with multi-index columns' names weirdness

and also:

is this in-scope for Narwhals?

Probably not 😂


Naming of repository

Hi I am developing using this library, so thanks for that, its working really well.
I am using using your repository as a submodule using the syntax:
from py-pushover-open-client.pushover_open_client import Client
However python complains at it has the - symbol in, so I am having to rename the folder locally to
from py_pushover_open_client.pushover_open_client import Client
My repository is here if you wanted to take a look to see what I mean.
IFTTTtoDomoticzUsingPushover
I know there are other ways around this such as taking the python file (with copyright/license/credit, etc) and putting it in my own repository, however I prefer to link to your repository, so it gives you the credit and also if you make updates (such as the empty title issue, which, I also hit).
Any other suggestions welcome.
Thanks Joe

Hi @aeirsoul
That's a great solution and I will update my repository to reflect this.
Joe


how can you make bert (encoder-only )model into item-llm (decoder-only)

In your paper HLLM: Enhancing Sequential Recommendations via Hierarchical Large Language Models for Item and User Modeling,I found you test bert-base,bert-large as item-llm in Table 5,but previous description reveal  item-llm is a decoder-only model,how can you make bert an encoder-only model into decoder-only, and test it's performance?

Hi~ We use traditional bert (uses bi-direction attention not casual attention) to extract item feature in our experiments.


⚠ Bofrost.de has degraded performance

In a41e9c0, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 760 ms

Resolved: Bofrost.de performance has improved in e47fb18.


Feature/docker

Interesting approach. Unconventional, but I guess it works. A few pointers: Espresso (ess-PRESS-oh) is a full-flavored, concentrated form of coffee that is served in “shots.” It is made by forcing pressurized, hot water through very finely ground coffee beans. This process is called “pulling a shot.” Tip: Espresso is commonly misspelled and mispronounced as 'expresso.' There is no 'x' in the word and you'll sound like a true coffeehouse newbie if you include it


Update dark mode

Updated dark mode detection

Watches for browser mode change
Watches for toggle change

Either change sets the scheme variable in localStorage

Added a couple of changes to the CSS as well to clean up & separate the dark mode classes for the toggle element

Enable dark mode checks, which coincidentally fixes broken HTML ( end tag but no  start tag)
With this, my set of changes are done for this PR.

Applied changes as requested. Looks alright on my website so far. Also updated main screenshot.png file.

lgtm - Thank you!


Calculating tokens prior to prompt

hey all,
I'm often making few-shot classification models using completions and I need to be able to check how many tokens exactly are inside my prompt prior to sending it off. Right now I do something like:
# sudo code
def send_request(prompt)
    try:
        ret = make_request(prompt)
    except:
        prompt = reduce_tokens(prompt)
        ret = send_request(prompt)
    return ret

but I'd rather just have the right number of tokens calculated in my preprocessing stage. Is there a way to use OpenAI's tokenizing tool to calculate this ahead of time?

from Openai's interactive tokenizer page:

If you need a programmatic interface for tokenizing text, check out the transformers package for python or the gpt-3-encoder package for node.js.


Creating chart arrays

Hi,
Thank you for the excellent plotting module. While I’ve successfully used it to plot technical indicators for individual stocks, I’m struggling to figure out how to create multiple stock charts in a single plot. Currently, my workaround involves saving individual charts as images and then stitching them together into a single image. Is there a more efficient solution you could recommend?
Thanks,
Ajith

Hi,
Thank you for the update.

Hi Ajith,
I looked into this a little further. The latest release adds a way to plot multiple assets in the same chart. This is a tentative solution.
chart = Chart(title="Versus", max_bars=max_bars, style=style)
chart.plot(data1, [ Candlesticks(), Volume(), RSI(), MACD() ] )
chart.plot(data2, [ Price() ] , target='main')

You can add replace=True in the second plot to have the prices rebased to the first series.
Example in examples/multiple-plots.ipynb

Hi,
Thank you very much. I really appreciate your help.

Glad it was helpful.


Vue3 support

Describe the problem
I found out that Eel is very much usable with vue. JS can call python and get a return value without a problem. My problem is that i cant figure out a way how to expose vue methods that can be called by python.
Code snippet(s)
Here is some code that can be easily used to reproduce the problem or understand what I need help with.
const { createApp } = Vue
        createApp({
            data() {
                return {
                    message: "",
                    inputValue: "",
                    response: ""
                }
            },
            mounted: function () {
                eel.hello_world()((val) => { // this works js -> py -> js (callback)
                    this.message = val
                })
            },
            methods: {
                onClick() { // this works js -> py -> js (callback)
                    eel.print_string(this.inputValue)((val) => {
                        this.response = val
                    })
                },

                // it needs to be exposed? eel.expose(this.calledFromPython) does not work
                calledFromPython() { // how can this be called from python? py -> js
                    alert("pythonCalledThis");
                }
            }
        }).mount('#app')

Desktop (please complete the following information):

OS: Win
Browser: Chrome
Version: latest?

I figured it out
    const { createApp } = Vue

    const app = createApp({
        mounted: function () {
        },
        methods: {
            toPy_print() {
                eel.print_string(inVal)((retVal) => {
                    // Return response from Python.
                    // this.response = retVal
                })
            },
            alert(text) {
                alert(text)
            }
        },
        data() {
            return {
            }
        },
    }).mount('#app');

    eel.expose(fromPy_alert);
    function fromPy_alert(text) {
        app.alert(text);
    }

import eel
eel.init('web')

@eel.expose
def print_string(text):
    print(text)
    return True

eel.fromPy_alert("Eel started")
eel.start('index.html', size=(640, 320))

calling vue methods from outside is not good though. its called anti-pattern and should be avoided. there seems to be no other way and for things like chat apps, where the incoming message to python should update js - instead of js requesting updates from python, it has to be this way.


Add support for broadcasting cache update messages

To allow other parts of related applications (e.g. the web dashboard) to be aware of the cache_loader events without having to create their own jetstream ephemeral consumers, we should allow code to declare interest in these events, probably through a Registry.

Related to #166


[YUNIKORN-849] The web can't get correct partition name from "/ws/v1/…

…queues" since the key was changed from "partitionname" to "partitionName"
What is this PR for?
the key was changed by https://github.com/apache/incubator-yunikorn-core/commit/160343fa2caacc9c825a3a92e717376a3f1c1f22.
Noted that this issue does not make web repo use new API. It just fix web to show the correct partition name.
What type of PR is it?

[x] - Bug Fix
[ ] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-849
How should this be tested?
Screenshots (if appropriate)
config
 partitions:
  - name: notdefault
    nodesortpolicy:
        type: binpacking
    placementrules:
      - name: provided
        create: true
    queues:
      - name: root
        properties:
          application.sort.policy: stateaware

Before

After

Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

Seems to be straight forward fix, but still good to ask @yangwwei to take a look.

This has been lingering for a long time. @manirajv06: go ahead and commit this.

@wilfred-s Could I merge it myself after I rebase code to trigger QA?

yes sure, squash and merge from the Github web UI should handle it all for you.


gpu_data_manager_impl_private.cc(445)] GPU process isn't usable.

Issue description
Hello,
on fedora 35 with native NVidia driver 470.94 i get this error when i start firefly app image.
On my laptop, which has the same fedora version, but no NVidia or AMD card, firefly works.
Discord has the same error.
workaround: start firefly with --nosandbox or better --disable-gpu-sandbox
Firefly version
1.3.0
OS details
Fedora 35 64bit Nvidia 470.97
Can the issue be reliably reproduced?
Yes
Steps to reproduce the issue

...
start simply the app
Expected behaviour
app starts
Actual behaviour
app stops to start with:
3:46:31.674 › Checking for update
13:46:31.807 › Update for version 1.3.0 is not available (latest version: 1.3.0, downgrade is disallowed).
(node:13054) Electron: Loading non-context-aware native module in renderer: '/tmp/.org.chromium.Chromium.Pj7JhX'. This is deprecated, see https://github.com/electron/electron/issues/18397.
[12985:1222/134631.990818:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye.
Trace/Breakpoint ausgelöst (Speicherabzug geschrieben)
Errors
3:46:31.674 › Checking for update
13:46:31.807 › Update for version 1.3.0 is not available (latest version: 1.3.0, downgrade is disallowed).
(node:13054) Electron: Loading non-context-aware native module in renderer: '/tmp/.org.chromium.Chromium.Pj7JhX'. This is deprecated, see https://github.com/electron/electron/issues/18397.
[12985:1222/134631.990818:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye.
Trace/Breakpoint ausgelöst (Speicherabzug geschrieben)

Duplicate of #1628


Exception when enqueuing many jobs in different queues while polling

Exception
The following exception has been reported to occurr while enquing new jobs:
ActiveRecord::Deadlocked: Mysql2::Error: Deadlock found when trying to get lock; try restarting transaction: INSERT INTO `jobs` (`queue`, `handler`, `priority`, `perform_at`, `created_at`, `updated_at`) VALUES ('queue_198', o:FailingTestJob\0', 0, '2019-08-12 16:17:10', '2019-08-12 16:17:10', '2019-08-12 16:17:10')

Surrounding conditions
This only happens under the following conditions:

Many (~23) jobs are enqueued in quick succession
Every enqueuing is done in a separate transaction (or without any transaction altogether)
Multiple workers (~6) run in the background while enqueueing the jobs
The workers are run with an aggressive polling interval (<= 1s)

Reproducibility
The exception has not always been reproducible but happened often. By tweaking the numbers (10 workers, 200 jobs, polling interval 0.1s), the exception seems to be reproducible virtually everytime.
Similar issues
While debugging this issue, other exceptions that happen when running many workers / pollers simultaneously have occurred. As the primary issue, these all seem to be fixed by applying the fix described under "Possible fix".
Possible fix
The problem seems to be solved when passing
isolation: :read_committed

to the transaction opened in Poller#poll. It is left to determine why this is needed and if this is the correct solution.
Test
The unit test test/workhorse/concurrent_poller_test.rb in branch issue_21 reproduces all the issues mentioned here.

This exception has been fixed in later versions.


Fix mice steering

Thinks there's obstacles when there isn't. Blending exposed it but it was an issue before.
Requires https://github.com/space-wizards/RobustToolbox/pull/4946
:cl:

fix: Fix NPC mouse movement.

Is this why the Dev mouse loves to run in circles under the tables?

Is this why the Dev mouse loves to run in circles under the tables?

Yeah, it's just before it didn't make a difference to steering.
I'm going to rework it slightly at some point but requires a pathfinder refactor.


Documents opened using window.showTextDocument send a delayed didClose event to LSP

Version/OS information:
Version: 1.85.1 (system setup)
Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2
Date: 2023-12-13T09:49:37.021Z
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621

Steps to Reproduce:

Setup an LSP for some language
Create a file of said language
Open the file using the window.showTextDocument -> This will (correctly) send a didOpen request
Close the file -> Does not didClose for a while

Using the commands API (commands.executeCommand("vscode.open", resourceUri, options)) seems to work as expected (more interactive)
Related but the documentation for "vscode.open" seems to have been deleted: https://code.visualstudio.com/api/references/commands
Reopening the file does not resend a didOpen request and closing the tab does not send a didClose - so it must be that (for some reason) closing the file is delayed significantly. After waiting for 5 minutes, a didClose is actually emitted but it is very strange that using the commands API it is more predictable and interactive than the window API

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!

The editor decides when to close a document by its own rules.

I understand that but it seems there is inconsistency between using window.showTextDocument and commands.executeCommand("vscode.open"). For example, if you open a file from the explorer and close it, an event is emitted immediately which is the desired behavior and matches the documents opened using the commands API but not the window API. The docs do not cover such cases (https://code.visualstudio.com/api/references/commands)

Let me describe the user case:
A language server performs more thorough validation for open documents vs files that are in the project. When using the command API, an editor is opened, the server reports a number of diagnostics and the user can perceive this as related to their own interaction with VS code. If they close the document, the regular validations are restored and the additional feedback diagnostics disappear - also perceived as a reaction to the user input.
With the window API, it's not possible anymore for the user, to understand the changed number of diagnostics "a while after the user interaction" based on the editors "own rules". This is not related to tab handling or anything.
@jrieken Do you understand the use case and if so, can you confirm that the UX is inferior with the window.showTextDocument behavior compared to exectureCommand?

@EhabY @szarnekow Why are you not using the tabs API (vscode.window.tabGroups) which was built specifically with diagnostics in mind

The language server is implemented for different front ends. I don't feel like replicating everything that's already handled by didOpen and didClose. What is the advantage of doing a client-specific implementation?


pydart dict fixes

Relates to https://github.com/adsharma/py2many/issues/293

I'll merge everything till  acac608. Need more time for:

understanding dart null safety. a[key]! seems more succinct and null safety is more in line with static compilation mindset of py2many.
mutable state in the transpiler (_in_assign_node). For complex ASTs it could make it harder to reason about.

Ya, I was going to suggest that.  Two notes:

I got a[key]! working, except that dart format wouldnt accept it.
_in_assign_node is horrid, but I couldnt think of a less complicated mechanism.  I am all ears if you have another pattern.  We should probably look at whether other languages also need similar decoration except when the expression is part of the LHS.  Very likely this occurs in other languages for a[x], but there might be others also.

Ya, I was going to suggest that. Two notes:
* I got `a[key]!` working, except that `dart format` wouldnt accept it.

Is it because dart hasn't been migrated to handle null safety? Docs seem to suggest that this requires 2.12.

* `_in_assign_node` is horrid, but I couldnt think of a less complicated mechanism.  I am all ears if you have another pattern.  We should probably look at whether other languages also need similar decoration except when the expression is part of the LHS.  Very likely this occurs in other languages for `a[x]`, but there might be others also.

The other pattern is the one in py2many/mutability_transformer.py, where the mutable state is isolated to a small piece of code (the transformer itself). So any bugs are easier to triage since it's isolated to that piece of code.
It's also possible to save the lvalue/rvalue info on the ast.Subscript node itself from a transformer, so the transpiler code is simplified.

Would it have the same behavior as python for cases such as:
#!/usr/bin/env python3

def main():
    a = [1, 2, 3, None, 5]
    for i in range(len(a)):
        print(a[i])

That is - can it distinguish between cases where the key was not found vs the key was found, but the value was null?
Also doesn't look like there was much progress on https://github.com/AmirKamali/Flutter_Vnum/issues/10

Also, I was able to do:
  dart pub upgrade --nullsafety collection lints sprintf tuple

and change dart version to 2.12 and use a[i]!. Seems to work. Let me ping that issue one more time to see if we can get a new release.

The approach you are taking this would enforce that end-user projects must have null-safety enabled.
That isnt feasible for many projects, due to dependencies like our own problem with vnum.
See https://github.com/search?q="null-safety"+language%3ADart+state%3Aopen&type=Issues for examples of the problem.  Including very important packages like https://github.com/dart-lang/intl_translation/issues/134 .
On the plus side, the issue mentioned above suggests a workaround which it might make it possible to override the dependency.
Unless you can see a better solution for v0.3.0, I think it is would best that we get this in, as it is good-enough to make Dart support more typical dicts.  And we can create an issue to improve it for the next release.

https://github.com/adsharma/py2many/pull/423 has a transformer to help with this, essentially move the in_assign_node logic out of line.
After that the commit will be small and easy to maintain.
I suspect there may be more languages which might want this behavior. Ok to keep it to dart for now.
If you choose to go the generic route, we'd rewrite the AST with if a[i] is None: throw Exception(...) and then transpile this using dart's ?? operator.

The bug in #423 has been fixed. Please try rebasing on top of it.
Also, having the stack ordered by pull request number makes it easier to review. That order would make this the lowest diff in the stack.
I have some concerns about the human readability impact of this on generated code. But on balance I think the impact is small (at least for the cases we have) and think that this diff should go in for greater python compatibility till dart ecosystem adopts null_safety more fully.

Closing this.  I dont have the capacity to work on multiple PRs interleaved with yours atm.
Feel free to take over this PR in https://github.com/adsharma/py2many/pull/423, i.e. do the complete solution.  That will be more efficient.


wrong with  shell AI website

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
If applicable, provide steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.

I have integrated a shell AI website, and the basic address has been filled in. However, I've noticed that it is unstable, sometimes accessible but mostly not. Could you please tell me the reason and how to resolve this issue? Your prompt response is greatly appreciated

Closing due to lack of information and no PR description


The documentation for Japan contains an error in the note about the fastest frequency of issuing Metric Alerts.

The note on the fastest frequency of metric alert rules is now 10 minutes for the ja-jp language, and 5 minutes for the en-us language. In fact, 5 minutes is more correct, and en-us seems to be the most up-to-date information.

1 For stateless metric alert rules, an alert will trigger once every 5 minutes at a minimum, even if the frequency of evaluation is equal or less than 5 minutes and the condition is still being met.

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

ID: 73e74d3e-7e13-646e-d07c-9409a2e38cc4
Version Independent ID: 33c32e9c-046d-4160-9c8b-c2f9623da674
Content: Troubleshooting Azure metric alerts - Azure Monitor
Content Source: articles/azure-monitor/alerts/alerts-troubleshoot-metric.md
Service: azure-monitor
Sub-service: alerts
GitHub Login: @harelbr
Microsoft Alias: harelbr

Thanks for bringing this to our attention. We will investigate it further and update you shortly.

@sakkuntyo - Thanks again for bringing this to our attention. We have updated the Doc last week and there is nothing in document that should cause difference in languages. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


[cache] receive crude Cache objects

This draft PR adds, likely broken, support for receiving CacheItem objects.

I've merged a slightly modified version of this deep into a refactor. Gonna close this since it's in the codebase now.


added onStart hook

ref: #232
This probably isn't ready to merge yet, because:

There is no test (I couldn't figure out how to add them).
It doesn't work as expected. It's called before the app is added to the DOM and has no access to the state.

The thing of having it before the DOM is updated is not that important, but it definitely should have access to the state. Any help or opinion is appreciated.

Hey @YerkoPalma, I think I recall this being mentioned in IRC. Remind me / those not there of the use case?

The use case is basically initialization of librarys or APIs, like service workers, indexedDB or something other. Now, the onload event of bel is definitely a good choice too, but the thing is those events are not set on the choo.use function, so they can't be wrapped in a plugin.
If those events could be wrapped in the use function to be used as a plugin it would be awesome, and this PR would have no sense :smile:

Wouldn't it make sense to do this sort of initialization in your own function around choo.start?
function startMyApp () {
  myService.init()
  return app.start()
}

@ajoslin But that wraping function has the same problems described above, besides can't be used in a plugin. The main intention of this PR is to be able to do this
const startPlugin = require('start-plugin')
const choo = require('choo')

choo.use(startPlugin())

choo.start()
// ...

closes in favor of #249


Fixed file-descriptor leak by waiting for child processes to terminate.

fixes #392
:tada: Hi and welcome! Please read the text below and remove it - Thank you! :tada:
No worries if anything in these lists is unclear. Just submit the PR and ask away! :+1:

Things to check before submitting a PR

[x] the tests are passing locally with cargo test
[x] cookbook renders correctly in mdbook serve -o
[x] commits are squashed into one and rebased to latest master
[x] PR contains correct "fixes #ISSUE_ID" clause to autoclose the issue on PR merge

if issue does not exist consider creating it or remove the clause

[x] non rendered items are in sorted order (links, reference, identifiers, Cargo.toml)
[x] links to docs.rs have wildcard version https://docs.rs/tar/*/tar/struct.Entry.html
[x] example has standard error handling
[x] code identifiers in description are in hyperlinked backticks

[`Entry::unpack`]: https://docs.rs/tar/*/tar/struct.Entry.html#method.unpack

Things to do after submitting PR

[x] check if CI is happy with your PR
[ ] drop a comment on https://github.com/rust-lang-nursery/rust-cookbook/issues/209 if you consent to repository being relicensed with CC0 license :+1:

Thank you for reading, you may now delete this text! Thank you! :smile:

Done.

Looks like expect() was throwing a panic when a None value is unwrapped.  We can't just directly replace them with ?
I replaced them with if let with this sample:
#[macro_use]
 extern crate error_chain;

use std::process::{Command, Stdio};

 error_chain! {
     foreign_links {
         Io(std::io::Error);
         Utf8(std::string::FromUtf8Error);
     }
 }

fn run() -> Result<()> {
	let directory = std::env::current_dir()?;
	let mut du_output_child = Command::new("du")
		.arg("-ah")
		.arg(&directory)
		.stdout(Stdio::piped())
		.spawn()?;

	if let Some(du_stdout) = du_output_child.stdout.take() {

        let mut sort_output_child = Command::new("sort")
    		.arg("-hr")
    		.stdin(Stdio::from(du_stdout))
    		.stdout(Stdio::piped())
    		.spawn()?;

    	du_output_child.wait()?;

        if let Some(mut sort_stdout) = sort_output_child.stdout.take() {
            let head_output_child = Command::new("head")
                .args(&["-n", "10"])
                .stdin(Stdio::from(sort_stdout))
                .stdout(Stdio::piped())
                .spawn()?;

            sort_output_child.wait()?;

            let head_stdout = head_output_child.wait_with_output()?;

            println!(
        		"Top 10 biggest files and directories in '{}':\n{}",
        		directory.display(),
        		String::from_utf8(head_stdout.stdout)?
        	);
        }
    }
    Ok(())
}

 quick_main!(run);

Hi @nimtiazm would you be able to look into Andy's comments?

Hi Michal,
Sure. I'll take a look over the weekend.
Nabeel
On Tue, Jul 10, 2018 at 4:47 PM, Michał Budzyński<EMAIL_ADDRESS>wrote:

Hi @nimtiazm https://github.com/nimtiazm would you be able to look into
Andy's comments?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang-nursery/rust-cookbook/pull/393#issuecomment-403809539,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM4CT1se0Hn465qPU0WUfjly3Bsos1Pgks5uFKJygaJpZM4TGz_c
.

To keep the PR/merge commit clean, i'm pulling off this one and creating a new one addressing the same issue.
https://github.com/rust-lang-nursery/rust-cookbook/pull/435


Make the magic bool more clear in the README

So that the reader can more easily figure out what the 4th argument to dumps is for.

Thank you @slafs :heart_eyes:


Updated details around Server Pending Reboot

Now are able to determine what type of action is causing the reboot. Just need to include some more information of where this is coming from.

#375

#375


Add compatiblewith and modelversion label to domain specific specs

Relates #222
Unfortunately, I did not find out how I could add a well-defined model into the model.json files. Is this possible? A problem could be that it's just an extension bag of properties and now we want to define at least one label inside of it.
Btw. I have troubles running the makefile locally on a Windows machine. Would need to install Linux Subsystem to make it work, I guess. But I've added an https://editorconfig.org/ file that tells editors / IDEs how to handle spacing etc. by default.

Unfortunately, I did not find out how I could add a well-defined model into the model.json files. Is this possible? A problem could be that it's just an extension bag of properties and now we want to define at least one label inside of it.

I'm not following. What do you mean by "add a well-defined model into model.json" ? Do you mean "how to include a list of possible values w/o actually adding them as labels?"

Btw. I have troubles running the makefile locally on a Windows machine. Would need to install Linux Subsystem to make it work, I guess. But I've added an https://editorconfig.org/ file that tells editors / IDEs how to handle spacing etc. by default.

Is it because of the linux shell commands that are run?


Reply on user's messages which triggered command execution

It's impossible to do it in a common way, but I've added a reply in most of them


CI: code analysis

resolves #2454

This PR is done, and it just does basic line counting. See https://swharden.com/blog/2023-03-05-dotnet-code-analysis/ for more information about code complexity analysis. Future PRs may extend this work by adding tables and charting.


ci: 'fix' libbpf build

The LLVM 12 + libbpf build breaks in the ci, pinning to a version that
should work.
Bit hacky but proper fix can come later, this unblocks the CI for other
PRs
fixes #2068

blocking some other useful PRs so merging this


StandardLockService: Ensure waitForLock() invokes acquireLock() at least once

Unless this is considered a feature, when changeLogLockWaitTimeInMinutes=0, acquireLock() doesn't get invoked.

Having a way to timeout locks is useful, but since execution of a changelog can take an arbitrarily long time, I worry about hard-coding a time.
We are looking at ways to improve the lock system in general to make it clean up locks better when possible, so that may go a long way to reducing the need for something like this.
But, something like this may still be needed as long as it has configurable timeouts.

My use case is a micro-service environment where the application lifecycle is controlled by a cluster manager.  If a node fails to start the manager will retry depending on its setup.
And generally, I think it makes the behavior more predictable.  In the current implementation, it exhibits one more quirk in my opinion – it always performs one extra wait cycle after aquireLock : false even if the timeout has been reached while trying the aquireLock already.


Example for remoteStopTransaction / remoteStartTransaction

Hello, could you explain to me which function I must use to carry out the remoteStopTransaction / remoteStartTransaction  commands via the central server?
I can't figure out how it works...
Thanks

Hi,
It sounds like you're talking specifically about OCPP version 1.6 ?
RemoteStartTransaction and RemoteStopTransaction are calls sent from the server to the client.
Here's an example of how to set up an OCPP1.6 server which sends a RemoteStartTransaction request whenever a client connects:
const {RPCServer} = require('ocpp-rpc');

const server = new RPCServer({
    protocols: ['ocpp1.6'], // server accepts ocpp1.6 subprotocol
});

server.on('client', async (client) => {

    try {
        const response = await client.call('RemoteStartTransaction', {
            connectorId: 1, // start on connector 1
            idTag: 'XXXXXXXX', // using an idTag with identity 'XXXXXXXX'
        });

        if (response.status === 'Accepted') {
            console.log('Remote start worked!');
        } else {
            console.log('Remote start rejected.');
        }

    } catch (err) {
        console.log('Remote start errored:', err.message);
    }

});

server.listen(80); // listen on port 80

Thank you for this quick response.
Indeed I am on ocpp 1.6.
I will try with your code thank you very much

It's good, thank you 👍


Bug: eqMac asking for drivers to be installed again often

[x] I have checked for a similar issue and sure it hasn't been reported before.

Describe the bug
I'm being asked to install the drivers again at least once a day.
Steps to Reproduce

Use Macbook M2 fully updated as normal
Wait for eqMac to ask me to install drivers again

Expected behaviour
Installing drivers once per update should settle the matter.
Setup information:

Audio setup: Macbook speakers, occasional BenQ monitor speakers
Audio transmission interface: USB-C power/data cable
macOS Version: very latest at all times
eqMac Version [e.g. 0.0.1] 1.7.10
eqMac UI Version [e.g. 0.0.4] 4.7.3 (Remote)

Some more info, after just experiencing this again:
The app itself seems to be unaware that it is no longer effective, and I need to go into system settings and EqMac settings to change the output device to get it to realise that it needs to reinstall the system audio driver.

➡ there might need to be other verification than internal state that something is wrong

My current main usage of this is to scale system audio for external speakers connected through an external device, so it's fairly obvious when the problem occurs.

I'm having this issue A LOT. Almost everyday.
App: v.1.8.0
Driver: v2.5.0
UI: v5.0.2

Same issue here on M1 Pro MacBook Pro 2021.

Can anyone confirm if this is still an issue with latest version 1.8.7? It should have been fixed, if not you can try manually reinstalling the driver https://help.eqmac.app/en/article/how-to-install-eqmac-driver-automatically-or-manually-1r2dnlk/

Yes still an issue for me

On 1 Jun 2024, at 16:41, Lina Ra @.***> wrote:
Can anyone confirm if this is still an issue with latest version 1.8.7? It should have been fixed, if not you can try manually reinstalling the driver https://help.eqmac.app/en/article/how-to-install-eqmac-driver-automatically-or-manually-1r2dnlk/
—
Reply to this email directly, view it on GitHub https://github.com/bitgapp/eqMac/issues/865#issuecomment-2143491595, or unsubscribe https://github.com/notifications/unsubscribe-auth/APIMKTGIYGRZ2BF2SSCTI4LZFHTTBAVCNFSM6AAAAAA5F4NVYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTGQ4TCNJZGU.
You are receiving this because you commented.

Have you tried to manually reinstall the driver? Also/Alternatively if issue is occurring after wake/on start please check if eqMac is enabled in system Settings > General > Login Items, if it's not enabled - enable it and see if that helps

I have tried this twice so far on 1.8.7 and it is enabled in Login Items

I see, I've talked to dev and he will continue looking into it but it may take a long time as on neither of our devices this issue occurs and it's reported by very few people, he previously asked for certain logs but those proved to be useless in resolving this specific issue.  It's also not something that can be debugged over screen share with device that has the issue happening, making debugging/solving even more tricky

I'm no longer getting the prompt to reinstall the drivers, but I am getting
a new problem: it often shudders, just tiny bursts of sound, then no sound
at all, and stopping and starting the app doesn't help, nor does killing
it. For some reason that's completely unclear so far, the sounds comes back
at some point later, though I can't tell if it's something I've done by
fiddling with re-starting it or turning it off and on repeatedly. Nor do I
have time to investigate it.
On Sat, 1 Jun 2024 at 18:57, Lina Ra @.***> wrote:

I see, I've talked to dev and he will continue looking into it but it may
take a long time as on neither of our devices this issue occurs and it's
reported by very few people, he previously asked for certain logs but those
proved to be useless in resolving this specific issue. It's also not
something that can be debugged over screen share with device that has the
issue happening, making debugging/solving even more tricky
—
Reply to this email directly, view it on GitHub
https://github.com/bitgapp/eqMac/issues/865#issuecomment-2143531648, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AZPMHVGI4GQYNMV5XQMAV7DZFIDPLAVCNFSM6AAAAAA5F4NVYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTGUZTCNRUHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I understand regarding the time. Currently there are similar reports of audio appearing and disappearing but there's lack of information on this issue at the moment and unfortunately we can't replicate it making it more difficult to resolve. If/when we'll have an update for this I'll provide an update here.


_Math_bitLogicalShift gives wrong output

assertSame(4294967294, _Math_bitLogicalShift(-2, 0))
assertSame(1, _Math_bitLogicalShift(-2, -1))

output:
Failed asserting that -2 is identical to<PHONE_NUMBER>.
Failed asserting that -4 is identical to 1.

I seem unable to come up with a fix.
This blocks the implementation of Math_clz32.
Solution will be to delete bitLogicalShift.au3 and WIP clz32.au3


fix: handle get varbinds

:tada: This PR is included in version 0.11.0-next.47 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Patch for v1.1.0

v1.1.0 has the same bandpass file for WFC3_IR.G141 and WFC3_IR.G102 grisms. This patch bumps the dependency svo_filters to v0.3.1, which has the correct WFC3_IR.G102 grism file.

@bourque @nespinoza Is this the correct workflow? I branched from v1.1.0, made the changes and issued the PR to be merged into the v1.1.0 branch? I'm not sure what to merge this into in order to make the v1.1.1 release.

@bourque @nespinoza Ok, I think this is ready. As soon as it's merged, we can deploy it to tlexo.

This diagram shows the proper workflow we should take here, I think:

Note that the release branch should be merged into both master and develop.  So I think we are fine to merge in this PR as it is, and we will have to open another PR that merges v1.1.1 into develop.
Once this PR is merged into master, we can create a GitHub release/tag off of master, which will officially mark the release of the new version.

I created the PR to merge into develop here: #482

@bourque Can you also review it so I can merge? It's just some dependency changes. I was able to make the fix with a new release of svo_filters.

@hover2pi Ah yes, sorry about that.  I forgot to hit the approval buttons yesterday.  The changes look good to me, but I would suggest we test on the test server before we merge.

@hover2pi This is now redundant with #484 and can be closed, correct?

@hover2pi This is now redundant with #484 and can be closed, correct?


Voice kit v1 with Pi Zero

With the new kit being released with a Pi0, is this change in compatibility due to a hardware change in the HAT?
Does the current code/API support using the original HAT with a Pi Zero W?

Yes, original (v1) Voice Hat  should work on Pi Zero as well, just use our SD card image.

Does this mean that the limitation of hotword support was resolved?  Are there no functional limitations that result from using a Pi0?

@dmitriykovalev I have installed the official image.  Only the button trigger works. No sign of hotword trigger working.  Is there any special step required to get it working?

That's correct. Unfortunately, Pi Zero is not powerful enough for real time hotword detection. We rely on assistant library which is optimized only for armv7l, i.e. for Pi 3, more info can found here: https://developers.google.com/assistant/sdk/overview

@dmitriykovalev
Does this mean that v2 of the kit is less functional than v1?  Does the v2 image use a different API/SDK?

No, that doesn't mean that. V2 board is more advanced than V1. The question is about Raspberry Pi board (Pi Zero vs Pi 3). We use the same software and the same Assistant library for both.

So, anyone who owns a v2 voicekit would need to replace the Pi0 (and the case) to get hotword functionality?  Am I wrong to consider the loss of hotword functionality a step backwards?

@mpember
Not exactly.
Voice Hat v2 and Voice Hat v1 both work on either version of the raspberry pi. So users feel free to use either of the Hats with the raspberry pi of their choosing.
Raspberry pi 0 is not powerful enough to support hotwording. This is due to the fact that their CPU is only single core arm v6. AIY team cannot really do anything about it, therefore, if you want to use the hotwording feature you have to use raspberry pi 3 with your builds.
Hope this helps.


README update

Added more notes
Updated explanation for Installation
Change in-app payments to in-app purchases (Not sure if this is appropriate, do you play to support Apple Pay?)
Cleaned up styling a bit

Thanks :+1: