Update cluster selection and reconcile logic

Description:

update cluster selection to only include in the remediationPlan those clusters that are present in the CR and NonCompliant in the at least one of the specified managed policies
have just one copy of each managed policy to use for the upgrade; for each of those copied policies, have one placement rule and one placement binding. Before the upgrade starts, each placement rule matches 0 clusters and the copied inform policies are set to enforce.
in the main reconcile loop, once the upgrade starts, for each cluster in a batch, start applying one policy at a time (starting with the first policy) by adding the cluster to the corresponding placement rule.
add new member to UpgradeStatus: RemediationPlanForBatch that holds the policy index for each cluster in the batch
once a batch is done, the placement rules are cleared (go back to matching no cluster)
TODOs have been added to places that need either cleanup or further restructuring

/lgtm


displayValue does not match value for File Sizes

Description
This problem mainly stems from a dependent package^1 that converts the file sizes in https://github.com/relative-ci/bundle-stats/blob/afe79a3f89f8110c2e6957ed565a5aa4bb3e9824/packages/utils/src/utils/format.js#L9-L17
As a result the displayValue does not match the value.
"name": "save-topic.js.231018ed472196b528b5.js",
"value": 3530,
"isEntry": true,
"isInitial": true,
"isChunk": true,
"chunkId": "3825",
"displayValue": "3.45KB"

There is already an issue on the dependent package^2, but it has been more than 3 years and the issue has not been fixed. I am wondering if the formatFileSize function should be changed to not depend on convert-units for formatting the file sizes?

Thank you for opening the issue @ardelato, i was not aware about the upstream bug.
Let's see if covert-units is planning to fix it soon.

Hey! I've release a new version 3.0.0-beta.5 which includes a fix for this issue. The release does not contain any breaking changes from version 3.0.0-beta.4 therefore it should be safe to bump the dependency version. Let me know if you have any questions or concerns. @ardelato Did confirm that the fix solves the problem. See this issue for more details. Thanks!

@Taar Thank you for the fix! 🙇  I updated the dependency and released a new version: v4.0.7.
@ardelato, thanks for confirming the upstream fix!


Fix: errors while pressing c-j

<C-j> works in the buffer of the bookmark window. Otherwise, the error appears while pressing <c-j>.
partially address https://github.com/crusj/bookmarks.nvim/issues/27

You're right. It's merged. Thanks for the pr.


thirdparty/mbedtls/library/ssl_tls.c:7413:5: runtime error: null pointer passed as argument 1, which is declared to never be null

When running studio, following error happens during opening of Asset library:
godot.x11.tools.64s
OpenGL ES 3.0 Renderer: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2)
thirdparty/mbedtls/library/ssl_tls.c:7413:5: runtime error: null pointer passed as argument 1, which is declared to never be null
    #0 0x4f2bda in mbedtls_ssl_read thirdparty/mbedtls/library/ssl_tls.c:7413
    #1 0x13dc9f3 in StreamPeerMbedTLS::poll() modules/mbedtls/stream_peer_mbed_tls.cpp:273
    #2 0xe9f698f in HTTPClient::poll() core/io/http_client.cpp:382
    #3 0x7c3b1eb in HTTPRequest::_update_connection() scene/main/http_request.cpp:351
    #4 0x7c40e81 in HTTPRequest::_thread_func(void*) scene/main/http_request.cpp:144
    #5 0x46c1bc8 in ThreadPosix::thread_callback(void*) drivers/unix/thread_posix.cpp:74
    #6 0x7f197c68d553 in start_thread (/lib64/libpthread.so.0+0x7553)
    #7 0x7f197b17bcce in __GI___clone (/lib64/libc.so.6+0xfacce)

One needs to build godot with use_ubsan=1.

Confirmed, this is caused by using mbedtls_ssl_read with a NULL buffer to force the library to process the following frames without copying them. Then, the library calls memcpy, with null as dest and 0 size, which is undefined behaviour. I didn't realize that at the time.
Thanks for reporting.


Fusis - Kernel statistics and logging

This pull request has the following contributions:

Added LogInterval command line argument
At Fusis load a Go routine is executed and uses the LogInterval to collect statistics from Kernel
Updated documentation inserting LogInterval usage
Created ServiceStats and DestinationStats structs
Functions GetServiceStats and GetDestinationsStats
Sync Fusis services struct with kernel
Created Log struct to be used in fusis.json
logging.go file should contain all logging implementation from different providers
Created default log implementation RouterStats that logs Router statistics to stdout.

PS:

Take a look at editors configurations that I think is breaking identation
New contributions will come. This one was becoming to big for a single Pull Request.
We need to plan a test bed for writing tests for statistics collection. Maybe using Docker compose.

If you have any question, please let me know.
Regards,

[Current coverage][cc-pull] is 72.92%

Merging [#14][cc-pull] into [master][cc-base-branch] will increase coverage by 18.42%

@@             master        #14   diff @@
==========================================
  Files            16          6    -10
  Lines          1022        373   -649
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits            557        272   -285
+ Misses          380         71   -309
+ Partials         85         30    -55

Powered by Codecov. Last updated by [9664dac...a2b91a4][cc-compare]
[cc-base-branch]: https://codecov.io/gh/luizbafilho/fusis/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/luizbafilho/fusis/compare/9664dac35c22a27faeff2c870ab5036f79200936...a2b91a4c46a50787f5ef42e3830f38fb79af7912
[cc-pull]: https://codecov.io/gh/luizbafilho/fusis/pull/14?src=pr


Add support for Desktop platform.

It would be great to support desktop platform.

Error on Windows:
../../sdks/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_quill-1.0.4/lib/widgets/raw_editor.dart(112,7): error G21C97077: The non-abstract class 'RawEditorState' is missing implementations for these members: [C:\_dev\\generate_router\build\windows\flutter\flutter_assemble.vcxproj]
../../sdks/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_quill-1.0.4/lib/widgets/raw_editor.dart(1025,8): error G76A9B1F6: The method 'RawEditorState.hideToolbar' has fewer positional arguments than those of overridden method 'TextSelectionDelegate.hideToolbar'. [C:\_dev\\generate_router\build\windows\flutter\flutter_assemble.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(238,5): error MSB8066: Custom build for 'C:\_dev\\generate_router\build\windows\CMakeFiles\8ee630b34045194ed45c9c7d3dcc6b33\flutter_windows.dll.rule;C:\_dev\\generate_router\build\windows\CMakeFiles\5ba78232244fa789eedb41a8845b05ed\flutter_assemble.rule' exited with code 1. [C:\_dev\\generate_router\build\windows\flutter\flutter_assemble.vcxproj]
Exception: Build process failed.

We don't have plan for that. But pull requests are welcome

I'm not sure it's possible until desktop platforms get web-view support.
Your pub.dev page currently indicates you do support desktop fwiw.

No idea why it is like that

@esDotDev @GreenLim see https://github.com/singerdmx/flutter-quill/pull/79


Unlisted addons appear in the devhub activity feed (bug 1144685)

Fixes bug 1144685
This PR is based on PR #484, which is based on #479, only the last commit is relevant to this bug

r+wc


Update app-insights-release-notes-java.md

Version 1.0.2

Hi @harelbr, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

Hi @alancameronwills, can you review this PR?
Thanks,
Dave

#sign-off


USER abc should be USER $DEFAULT_USER

See https://github.com/DigitalTransformation/vs-code-container-with-ssl/blob/85793d29d2e3be038fe40c23461fce8f71883625/dockerfile#L71
Also, (untested) not to sure about the /home/linuxbrew lines, I would expect $Default_user there as well.

Hey,
Just pushed commit 215a095e51d3cfd17d45d223d1d4084f24a7cbf2 to update the reference with the arg $DEFAULT_USER.
https://github.com/DigitalTransformation/vs-code-container-with-ssl/blob/215a095e51d3cfd17d45d223d1d4084f24a7cbf2/dockerfile#L71
Here's some clarification on linuxbrew...
https://github.com/DigitalTransformation/vs-code-container-with-ssl/blob/85793d29d2e3be038fe40c23461fce8f71883625/dockerfile#L73
Docs mention that linuxbrew inflates binaries in the path /home/linuxbrew/.linuxbrew/bin/ by default. This behavior can be customized to ~/ but presumably it's done for sandboxing roles.
Thanks for posting this and hope that helps! Feel free to fork & customize the layers with the devtools you need.

Hey,
Just pushed commit 215a095e51d3cfd17d45d223d1d4084f24a7cbf2 to update the reference with the arg $DEFAULT_USER.
https://github.com/DigitalTransformation/vs-code-container-with-ssl/blob/215a095e51d3cfd17d45d223d1d4084f24a7cbf2/dockerfile#L71
Here's some clarification on linuxbrew...
https://github.com/DigitalTransformation/vs-code-container-with-ssl/blob/85793d29d2e3be038fe40c23461fce8f71883625/dockerfile#L73
Docs mention that linuxbrew inflates binaries in the path /home/linuxbrew/.linuxbrew/bin/ by default. This behavior can be customized to ~/ but presumably it's done for sandboxing roles.
Thanks for posting this and hope that helps! Feel free to fork & customize the layers with the devtools you need.


Support AWS Secrets Manager as remote component

PR Description
Which issue(s) this PR fixes

Closes #689
Notes to the Reviewer

Should I poll the Secrets Manager API continuously to fetch latest secret. Pricing per API calls for Secrets Manager is much expensive compared to AWS SSM Parameter Store and AWS S3 API calls so I'm hesitant to implement poller. Would like to hear everyone thoughts about it.
I expose the inner component.Component in componenttest in order to verify the component's health status. Is this A-OK?

PR Checklist

[x] CHANGELOG.md updated
[x] Documentation added
[x] Tests added

Thanks Matt! I'll implement the poller and fix whatever makes the tests failed.
Maybe in the long run,  we can have a reusable implementation. But that's for another day, I suppose :D

Docs look ok.

I think it would be nice if it could poll but set the default to not poll. Most of our pulling mechanisms support it so it would be odd if this one did not have that capability.

@mattdurham Can you help me understand setting the default to not poll for updates? Don't all of our components default to polling in the background?

My thought on the default to not polling is related to this comment Pricing per API calls for Secrets Manager is much expensive compared to AWS SSM Parameter Store and AWS S3 API. if it is expensive default to no but allow it to be poll. Also fine with the other direction, default to a low poll rate.

Comparing the pricing of AWS Secrets Manager to S3 does show that secrets manager is more expensive, but perhaps not significantly:

AWS Secrets manager: $0.05 per 10,000 API calls
S3: $0.004 per 10,000 GET calls

It will take 200,000 polls of secrets for it to cost $1 USD. If we set the polling interval to hourly, and you had 100 Alloy instances all running the same component, that would still only be 73,000 polls per month ($0.36).
It seems like the cost is reasonable enough if we used a 1h polling interval by default. If you're running Alloy in an environment where you need AWS secrets manager (likely Enterprise-like), running Alloy itself probably costs orders of magnitude more money than the secrets manager bill would be.
WDYT @mattdurham?


Adapting the Shard::close example to ShardEventStream

A lot of users have expressed interest in processing already received events when shutting down shards, as documented in the Shard::close example, but as most of our users (want to) run multiple shards they want to adapt it to ShardEventStream, which they've found difficult. We should therefore include a second example on Shard::close for ShardMessageStream where MessageSender and mem::forget is used to remove shutdown shards from the stream. However, there's a risk of missing events when transitioning from the two event loops as dropping the stream cancels any in progess future. To mitigate this would require merging the two event loops' match statements, and use e.g. an atomic bool to guard shutting down shards.
The required changes almost mirror the gateway-parallel example, but instead of spawning each shard on a separate task and awaiting close on the main task, it spawns a task that awaits the close and processes shards as normal. This raises the question, as ShardEventStream is meant only as a simple convenience type (one that is sadly slower than spawning shards in their own task) should this setup even be recommended over one based upon gateway-parallel? The complexity is almost the same, but ShardEventStream gives strictly less control to the user.
Sparked from the following support post: https://discord.com/channels/745809834183753828/1075600478899032104

ShardEventStream is removed in 0.16 and with poll_next being cancel safe (#2309), there's no risk in missing events when naively using tokio::select! in a loop. Furthermore, tokio_util::task::TaskTracker automates task shutdown. Closing shards should thus be quite easy.


Web client

Two pages, using materialize.css and angular2, with mock data, haven't tested build parts of the script.

Sorry it didn't occur to me that your PR was sitting here. Merging now.


WARNING:root:Page 1: Different page-vs-block token counts

Hi,
I'm getting this warning.
WARNING:root:Page 1: Different page-vs-block token counts: 787 vs 465
WARNING:root:Page 2: Different page-vs-block token counts: 123 vs 70

Anyway, running in the debug mode, the resulting pictures look fine overall.

Actually I think I found why it's saying that, and it is a problem:
line=14 fonts=Arial Unicode MS-13.2,Times New Roman-10.4,Times New Roman-12.2,Times New Roman-12.7,Times New Roman-13.0,Times New Roman-13.3,Times New Roman-13.5 bbox=47.157,414.694,503.248,492.399 iscore=0.00
:considerando(relativosettoreultimoaiutobrioCEEtra)perndalldel.allil1308il''volumeorganizzazionelinoattolino/70chetessilediedeldellaadesionedilConsiglio',articoloproduzionealcanapafinecomunedel4di, del(assicurare19793del),necessario29deimodificato, giugnoregolamentoistituiscemercatil'equili1970nellanelunda, (dipromuovereesse11982CEE. cuiPer/ottenuti)1983nallpromuovere. '1308articolo—.l'uso/198670delle, /1sono,1987loparagrafofibresmercio, istituitemisuredi linodei1,,comunitarieperdeleprodottideileregolamentoprodotticampagnediattelinodaa

it reads the lines without white spaces

Those warnings occur after grouping tokens into blocks. The first count is how many tokens are in the page and the second is the sum of all tokens in the detected groups. Sometimes you'd need to tweak some heuristics in your PDF-to-XML step (if you're using TET or PDFMiner), especially on pages that have very little space between words.
Sorry but I'm not sure I can help much further, as I'm not actively working on this project anymore.

Thank you very much for your help anyway.


Modify content extraction

Coverage increased (+0.28%) to 36.8% when pulling b4aed1a9c34b954bb8149b54b8ed184677d93d15 on AlexMathew:scrapple into 3a2f3978c99fb44b187041d59b4f3fc37096e2d2 on scrappleapp:master.


How to check if the value is a decimal

Can you please help me to know if it is possible to check if the value is a decimal or float.
Also does the validation check accepts regex?

This middleware uses node-validator, so you should check there first for existing methods. Looks like there is an isDecimal() and isFloat() that you could use. Let me know if this helps.

@rakesh1988 as @rustybailey suggested, please check https://github.com/chriso/validator.js
if you can't find what are you looking for there you can always create your custom validator
i will close an issue, please comment if you need any further help with this


[REQ] Source type "context" is confusing to explain and understand

What kind of request is this?
Improvement of existing experience
What is your request or suggestion?
We have a source type: "context".
This has very little meaning to users, and is even more confusing because the default context name from docker is called "context".
So to use that we have a source that looks like this:
sources:
  foo:
    context:
      name: context

I think we should rename this source type.
The only suggestion that comes to mind right now is client since that is where the content comes from.
Are you willing to submit PRs to contribute to this feature request?

[ ] Yes, I am willing to implement it.

cc @adamperlin @pmengelbert @DannyBrito


Fix for typo in Failure

https://gitter.im/finagle/finch?at=564301ec94df6212290da0db
in other case it makes no sense?

Current coverage is 93.36%

Merging #435 into master will decrease coverage by -0.70% as of 98c559f

Powered by Codecov. Updated on successful CI builds.

My bad. I'm probably going to release 0.9.1 with this fix. Thanks @ImLiar!


Change to use image from gcr

What this PR does / why we need it:
Change to use image from gcr
Fix the hostname to predict
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

This change is

/lgtm

Nice! Will let yuzi approve /lgtm

/lgtm

/retest


[iOS] Adaptive cards not rendering in Teams iOS app but show up on the desktop client.

Target Platform
Please list the platform(s) that your application is targeting and remove platforms you are not targeting:

iOS

Target Application
Microsoft Teams for iOS
Problem Description
Microsoft Teams app on iOS is not rendering adaptive cards when sent via an inbound webhook.
Screenshot
Desktop:

Phone:

Card JSON
Tried it with some of the templates as well available online and none of them rendered at all.
Sample Code
N/A
Version of SDK
N/A

This issue has been copied over to Microsoft Teams repo here: https://github.com/MicrosoftDocs/msteams-docs/issues/3672


fix(build): README.md

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


Emit ktlint failure detail to console log

Seems to be going to a plain text file which then has to be separately opened. Whereas the Android lint is emitting to console so it's more accessible, especially in CI.
e.g.:
ably-asset-tracking-android % ./gradlew clean check

> Task :publishing-sdk:ktlintMainSourceSetCheck FAILED
/Users/quintinwillison/code/ably/ably-asset-tracking-android/publishing-sdk/src/main/java/com/ably/tracking/publisher/DefaultAssetPublisher.kt:5:1: Unused import (no-unused-imports)
"plain" report written to /Users/quintinwillison/code/ably/ably-asset-tracking-android/publishing-sdk/build/reports/ktlint/ktlintMainSourceSetCheck/ktlintMainSourceSetCheck.txt

> Task :publishing-sdk:lint
Ran lint on variant debug: 2 issues found
Ran lint on variant release: 2 issues found
/Users/quintinwillison/code/ably/ably-asset-tracking-android/publishing-sdk/src/main/java/com/ably/tracking/publisher/DefaultAssetPublisher.kt:73: Information: TODO call found; points to code which must be fixed prior to release [StopShip]
        TODO()
        ~~~~~~
/Users/quintinwillison/code/ably/ably-asset-tracking-android/publishing-sdk/build.gradle:10: Information: A newer version of com.mapbox.mapboxsdk:mapbox-android-sdk than 9.5.0 is available: 9.6.0 [GradleDependency]
    implementation 'com.mapbox.mapboxsdk:mapbox-android-sdk:9.5.0'
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
0 errors, 0 warnings

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':publishing-sdk:ktlintMainSourceSetCheck'.
> A failure occurred while executing org.jlleitschuh.gradle.ktlint.KtLintWorkAction
   > Process 'command '/Users/quintinwillison/.asdf/installs/java/adoptopenjdk-8.0.272+10/bin/java'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.7.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 9s
92 actionable tasks: 91 executed, 1 up-to-date

┆Issue is synchronized with this Jira Task by Unito

It turns out that now the ktlint behaves as expected (prints errors to the console), an example is provided below. Due to that, I'm closing this issue.
> Task :publishing-sdk:ktlintMainSourceSetCheck FAILED
/home/kacper/Projects/AndroidProjects/ably-asset-tracking-android/publishing-sdk/src/main/java/com/ably/tracking/publisher/Publisher.kt:83:27 Unnecessary semicolon (no-semi)

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':publishing-sdk:ktlintMainSourceSetCheck'.
> A failure occurred while executing org.jlleitschuh.gradle.ktlint.worker.ConsoleReportWorkAction
   > KtLint found code style violations. Please see the following reports:
     - /home/kacper/Projects/AndroidProjects/ably-asset-tracking-android/publishing-sdk/build/reports/ktlint/ktlintMainSourceSetCheck/ktlintMainSourceSetCheck.txt


How should I upload video？

Everything works fine when i upload the picture, it's broke while uploading the video.Where am I doing wrong?
# url example
# http://abc.com/1.mp4
# http://abc.com/2.png
# http://abc.com/3.jpg
if (os.path.splitext(url)[-1][1:]).lower() not in ["jpg", "jpeg", "gif", "png", "webp", "mp4", "mov"]:
    return
response = requests.get(url)
old_domain = twitter.domain
twitter.domain = 'upload.twitter.com'
id_img1 = twitter.media.upload(media=response.content)["media_id_string"]
twitter.domain = old_domain
twitter.statuses.update(status=text, media_ids=",".join([id_img1]))

details: {'request': '/1.1/media/upload.json', 'error': 'media type unrecognized.'}

I'm not sure videos upload is supported in this library yet: as it says on Twitter's official API documentation https://developer.twitter.com/en/docs/twitter-api/v1/media/upload-media/api-reference/post-media-upload the regular media.upload route only supports images, and it should be called differently to post videos or big images, through multiple different calls using the same route but with different arguments:

first an INIT call https://developer.twitter.com/en/docs/twitter-api/v1/media/upload-media/api-reference/post-media-upload-init
then multiple APPEND calls containing chunks of the video https://developer.twitter.com/en/docs/twitter-api/v1/media/upload-media/api-reference/post-media-upload-append
finally a FINALIZE call to get the media id before using it in a tweet https://developer.twitter.com/en/docs/twitter-api/v1/media/upload-media/api-reference/post-media-upload-finalize

I've never tried it before and will be curious of your feedback!


reorder the admin panel sidebar

logical ordering
e.g
logs, alerts -> pushed to the back
actionable items e.g wallet -> go higher
watcher @rkhamis

Commit_ID 1ef7edd7ea95962389d3a071c094fc50cbb0eafb , Branch development


Can I load TWO contracts in the ONE UnitTest by using DebugManager.LoadContract?

I want to do UnitTest loading the two contracts in the same class.
Can I do this?

Hello Keisuke, you can work with two smart contracts, however, I'm almost sure that you can't invoke other smart contracts.
How are you doing your tests? We use a virtual blockchain, so it may not be possible at this moment but could be implemented in the future.
What exactly do you want to achieve using 2 contracts?

Thank you for answering ,lock9.
I want to do dynamic invoke one smart contract through the other smart contracts.
One smart contract give storage context to the other smart contract and manipulate it.

Sorry, I don't really know the answer. I need a few more days to investigate.
I suppose you are using the master branch, right?


update the device for is_valid_x

This PR should address issues in the tests mentioned in #788. The is_valid_x index will be (maybe) copied to the correct device for x and theta before indexing. Thereby a runtime error is avoided.

Codecov Report

Merging #789 (5c0bf36) into main (8fe45c9) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #789   +/-   ##
=======================================
  Coverage   74.52%   74.52%
=======================================
  Files          77       77
  Lines        6120     6120
=======================================
  Hits         4561     4561
  Misses       1559     1559

Flag
Coverage Δ

unittests
74.52% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

sbi/inference/snle/snle_base.py
91.58% <100.00%> (ø)

sbi/inference/snpe/snpe_base.py
89.17% <100.00%> (ø)

sbi/inference/snre/snre_base.py
94.87% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

this commit fixes the tests that were failing but makes pyright fail


Tier 1 Features

includes tests and implementation

https://github.com/idcrook/BiftVector/wiki/Tier_1_Features

Comparisons are implemented in #4

Casting functions for Array and Array are added in #7
Tier 1 are now done


Render dist options

Picking up on yet another abandoned PR. Made all changes suggested by @clarkdo and wrote a test.

Codecov Report

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

@@           Coverage Diff           @@
##              dev    #3671   +/-   ##
=======================================
  Coverage   98.94%   98.94%
=======================================
  Files          18       18
  Lines        1139     1139
  Branches      306      306
=======================================
  Hits         1127     1127
  Misses         12       12

Impacted Files
Coverage Δ

lib/common/nuxt.config.js
100% <ø> (ø)
:arrow_up:

lib/core/renderer.js
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Release Google.Cloud.ContactCenterInsights.V1 version 2.15.0

Changes in this release:
New features

Add IServiceCollection extension methods for client registration where an IServiceProvider is required. (commit 022fab2)

Created release for Google.Cloud.ContactCenterInsights.V1-2.15.0


fix(host): hide kvm only gpu guests

What this PR does / why we need it:

Does this PR need to be backport to the previous release branch?:
release/3.10

/hold


Dropping builder as dependency ?

builder is only used for generating xml. Should we keep it as a dependency ? We're using to_xml and active_support takes care to require builder when needed and will tell users if its not found.
For those who doesn't format :xml, builder is just an overhead.

I don't see why not.


Fix and optimize algorithms

Fixed DE implementation, which was inconsistent with the pseudocode.
Added inbounds macros to speed up array access
Updated tests to cover these changes.

Codecov Report
Base: 94.79% // Head: 99.00% // Increases project coverage by +4.21% :tada:

Coverage data is based on head (073bea9) compared to base (5a5e17f).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #14      +/-   ##
==========================================
+ Coverage   94.79%   99.00%   +4.21%
==========================================
  Files          14       14
  Lines         288      301      +13
==========================================
+ Hits          273      298      +25
+ Misses         15        3      -12

Impacted Files
Coverage Δ

src/optimization/de.jl
100.00% <100.00%> (+4.65%)
:arrow_up:

src/optimization/pso.jl
100.00% <100.00%> (+2.27%)
:arrow_up:

src/rule.jl
100.00% <0.00%> (+12.82%)
:arrow_up:

src/feature.jl
90.90% <0.00%> (+18.18%)
:arrow_up:

src/attribute.jl
90.90% <0.00%> (+18.18%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


the installed extensions seems not work, i build code-server project by myself

Web Browser:Chrome 83.0.4103.116 x64
Local OS:macOS Catalina 10.15.5
Remote OS:macOS Catalina 10.15.5
Remote Architecture:
code-server --version:3.4.1

i contribute the code-server project use these steps:
1.yarn
2.yarn vscoe
3.yarn watch
i visit http://localhost:8080, it works normally. then i installed extensions: cpptools and Chinese Language Pack, but the extensions seems not work. it still use English Language, and the vscode-web will pop a warning dialog at bottom-right corner when i first visit. When running the debugger for an active C++ file, the debugger throws an error saying that it cannot find the build task associated with the debug configuration.
but when i develop the code-server use the Standalone Releases 3.4.1, all of these problems disappeared, the extensions work normally.

The language packs don't work in development mode; you have to do a full build. It's because the necessary language data is only generated during the full build process (I'm not sure why it's orchestrated it this way though).
I actually can't get tasks to run at all even in 1.4.1 so this might be a bug.

The tasks seem to be working again after I updated the version of VS Code that ships with code-server. Let me know if it still doesn't work for you and we can re-open the issue!

The tasks seem to be working again after I updated the version of VS Code that ships with code-server. Let me know if it still doesn't work for you and we can re-open the issue!

I updated the latest code. It works correctly. Thanks a lot.
But the pop-up in my first picture still exists, unless I copy the extracted plugin "references-view" to the "lib/vscode/extensions" folder.
If I change "bind-addr" to a special ip in config.yaml, it will pop a message 'code-server is being accessed over an insecure domain. Web views, the clipboard, and other functionality will not work as expected.' and can't find the task again.
So do I have to publish using domain and https for other developers to use? Is there a way for others to use it in a development environment?

Yeah, unfortunately a bunch of functionality depends on service workers and other features (like the clipboard API) which browsers simply won't enable over insecure domains, so https is a requirement for everything to work properly.
About the popup, some plugins aren't generated until the full build process. The references plugin seems to be one, the Node debug plugins are another (so Node debugging won't work in development mode) and there might be others I'm not aware of as well.

Yeah, unfortunately a bunch of functionality depends on service workers and other features (like the clipboard API) which browsers simply won't enable over insecure domains, so https is a requirement for everything to work properly.
About the popup, some plugins aren't generated until the full build process. The references plugin seems to be one, the Node debug plugins are another (so Node debugging won't work in development mode) and there might be others I'm not aware of as well.

I use nginx and mkcert to solve this problem.
I want to modify some logics of login, but I run it by using yarn watch. How can I debug the ".ts" files under the "src" folder?
These files are not available in chrome.

Oh, it looks like our source maps for VS Code are broken. If we fix those the .ts files will show up in Chrome.

Oh but the login source files should show up fine. But there isn't any JavaScript logic on the login page. It's only on the Node end. The Node files won't show up in Chrome unfortunately, but it should be possible to connect a debugger to the Node process.

You can connect the Chrome debugger to the Node process by starting code-server like this:
NODE_OPTIONS=--inspect yarn watch

Then in Chrome go to chrome://inspect.
But, there don't seem to be any files in the developer console so I'm not sure how to use it.

 It works! But we spawn a child process and that's the process that actually needs to be debugged and using NODE_OPTIONS doesn't seem to work because the parent process has already taken the port.
I think we'll need to add a command-line flag for passing Node options to the child process.
One manual workaround is to edit this line: https://github.com/cdr/code-server/blob/e858a4f4c7f30898d0a884015f34353b354a04ad/src/node/wrapper.ts#L229
And add the inspect option:
const wrapper = new WrapperProcess(require("../../package.json").version, { nodeOptions: "--inspect=9999" })

Oh you can just use ctrl+p to search files. It works! But we spawn a child process and that's the process that actually needs to be debugged and using NODE_OPTIONS doesn't seem to work ~because the parent process has already taken the port~ nope it's because we override NODE_OPTIONS in the yarn watch invocation.
I think we'll need to add a command-line flag for passing Node options to the child process.
One manual workaround is to edit this line:
https://github.com/cdr/code-server/blob/e858a4f4c7f30898d0a884015f34353b354a04ad/src/node/wrapper.ts#L229
And add the inspect option:
const wrapper = new WrapperProcess(require("../../package.json").version, { nodeOptions: "--inspect" })

Then run code-server normally (without NODE_OPTIONS).

It works good. Thanks.
I know that there isn't any logic code on the login page. I debug it to know the process before entering vscode, because I want to change it to different users who login with their own username and password, and can only view their own workspace. ^^

Makes sense!


Added Android Build Support for newer React Native Versions

Added Android Build Support for newer React Native Versions which uses a new SDK and Build Tool version.

Closing in favor of #27 which was here before and deals with same issue.
Sorry I didn't see it.


Adding Unfried JSM 2022

👷 Deploy Preview for douglaswhitaker processing.

Name
Link

🔨 Latest commit
02d12e3579cdfe7dc8b6ef94997b57a8617aa846

🔍 Latest deploy log
https://app.netlify.com/sites/douglaswhitaker/deploys/631672ef7f702b0009a06587


V1.3 user guide

Codecov Report
Base: 52.62% // Head: 52.62% // No change to project coverage :thumbsup:

Coverage data is based on head (571d12d) compared to base (caae225).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #136   +/-   ##
=========================================
  Coverage     52.62%   52.62%
  Complexity      708      708
=========================================
  Files           159      159
  Lines          3202     3202
  Branches        394      394
=========================================
  Hits           1685     1685
  Misses         1370     1370
  Partials        147      147

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Maximized window is too large

Issue Type: Bug
When VS Code window is on secondary monitor, it is bigger than it should be.
This is a screenshot from the corner of the window:

other three corners look similar.

VS Code version: Code 1.41.0 (9579eda04fdb3a9bba2750f15193e5fafe16b959, 2019-12-11T18:37:42.077Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 x 1498)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.75GB (5.66GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (5)

Extension
Author (truncated)
Version

gitlens
eam
10.2.0

csharp
ms-
1.21.9

powershell
ms-
2019.12.0

team
ms-
1.161.0

LiveServer
rit
5.6.1

I've also experienced this issue, window content extends beyond its actual bounds. Issue also occurs when windowed (can tell as dragging to resize in the bottom right has the drag point too far in).
This is on a Surface Book 2 (high DPI screen) paired with 2 23" full HD screens (comparably lower pixel density).
This hasn't been an issue in the past, I first noticed the issue a few weeks ago, but hadn't the chance to report.

/duplicate of #85592


Adjust date & time column width to fit all dates @ 1280px wide screen

3dotting should never happen for dates & times in the event listing page, at 1280px wide screens.
We should adjust the width of the date column (at the expense of the event title column) to make sure that it can take long date formats like W10 Wed 11am - 12pm without 3dotting them.

Assigning to @bp323 for review

Coverage remained the same at 100.0% when pulling 74fcd6646629e302293508ad3849c15d9d77ad58 on Coenego:issue-325-column-width into f8ec4fd01e463bd816e04456d4ba7ae58151022c on CUL-DigitalServices:master.

Verified and merged.


Could not copy the file "\packages\FaceRecognitionDotNet.<IP_ADDRESS>\runtimes\win-AnyCPU\native\DlibDotNetNativeDnnAgeClassification.dll" because it was not found.

Hi,
I'm trying to use this library in my application and i'm getting this build error. I would really appreciate if someone Please help me fix this problem. I have attached a screenshot for your reference.
cc: @takuya-takeuchi
Thank you

@salmana66
It is not bug.
https://github.com/takuya-takeuchi/FaceRecognitionDotNet/wiki/Quickstart#warning-warning-for-visual-studio-users
I'm not planning to support any-cpu because nuget package should be more larger.

Okay i got it @takuya-takeuchi , can you please suggest to which platform should we target our project? i mean which one is better and works better with this library, x86 or x64?

You should choise x64.
I'm not sure x64 cpu is better than x86 in the point of view pf architecture.
But x64 program can allocate huge memory.
It should make stable program.
Espeicailly, model file take large memory. We would avoid out of memory by choise x64.

Sure thing @takuya-takeuchi , Thank you very much!


Add protocol spec/description

There is a protocol description for the old Lumberjack protocol at https://github.com/logstash-plugins/logstash-input-beats/blob/v2.0.0/PROTOCOL.md but I'm missing like this for the Beats protocol.
While having a working library for the Lumberjack/Beats protocol is nice and a specification could be "reverse engineered" by looking at the Go code, it would be great if a textual protocol spec of the Lumberjack (v1) and Beats (v2) protocols existed.

Project moved to elastic/go-lumber. New issue created in new repo.


WslRegisterDistribution failed with error: 0x80070003

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070003
Error: 0x80070003 ???????????
Press any key to continue...

Please collect WSL logs and provide a link the feedback hub item.

https://github.com/microsoft/WSL/issues/6512#issuecomment-773173169
Please do https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html and try to enable wsl again, it should work correctly. It mean there're some file missing. I seen this in many windows installation (clean windows), and the only way to fix it is either reset the windows or in-place upgrade. I choose In-place upgrade.

Saying "there's some file missing" isn't helpful. Not everyone in corporate settings can do an in-place upgrade.

Instead of relying on Microsoft's Windows Store, try to manually install a distribution with wsl.exe --import command.

Saying "there's some file missing" isn't helpful. Not everyone in corporate settings can do an in-place upgrade.

I agree with that, but til about 6 month looking into log, there're nothing that help, and my lab need to go on, so I just in-place upgrade each computer on my lab. It's troublesome. The mod on reddit also doesn't help at all and state there won't be any 0x80070003 if we put the wsl on C: drive. In-place ugrade is my last resort, at least it's working now, but https://github.com/microsoft/WSL/issues/5718 hasn't fixed yet till now.

Logs from #6512 here.

Saying "there's some file missing" isn't helpful. Not everyone in corporate settings can do an in-place upgrade.

Hi !
I have the same problem, when I try to install a Linux distribution on my Windows (because it is a WSL2 requirement, in order to run Docker Desktop on my local Windows10 laptop), I get this message:

Have you found a solution other than the one proposed by @benyaminl  ?
It happens to me like @pdebuitlear , I have a corporative settings and I can't do an in-place upgrade.
Thankyou!

Saying "there's some file missing" isn't helpful. Not everyone in corporate settings can do an in-place upgrade.

Hi !
I have the same problem, when I try to install a Linux distribution on my Windows (because it is a WSL2 requirement, in order to run Docker Desktop on my local Windows10 laptop), I get this message:

Have you found a solution other than the one proposed by @benyaminl ?
It happens to me like @pdebuitlear , I have a corporative settings and I can't do an in-place upgrade.
Thankyou!

The fix for me was to set the following registry key value to 1:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\kernel\obcaseinsensitive

My system:
Edition	Windows 10 Pro
Version	Dev
Installed on	5/21/2021
OS build	21382.1
Experience	Windows 10 Feature Experience Pack 321.12100.0.3

Fresh installed system and it produced the op error. Did the inplace upgrade by iso and no success. Even docker is giving me errors:
System.InvalidOperationException:
Failed to deploy distro docker-desktop to %LOCALAPPDATA%\Docker\wsl\distro: exit code: -1
 stdout: The system cannot find the path specified.

Funny thing is: before I format the PC due to another issue everything was working flawlessly (I was already using this Dev Channel Build)

Does the folder exist? Because if that folder doesn't exist than it will
raise such error.
Regards,
Benyamin Limanto
sent from my Sony XPERIA XZ Premium
On Fri, 21 May 2021, 21:46 Dante Souza e Souza, @.***>
wrote:

My system:
Edition	Windows 10 Pro
Version	Dev
Installed on	5/21/2021
OS build	21382.1
Experience	Windows 10 Feature Experience Pack 321.12100.0.3
Fresh installed system and it produced the op error. Did the inplace
upgrade by iso and no success. Even docker is giving me errors:
System.InvalidOperationException:
Failed to deploy distro docker-desktop to %LOCALAPPDATA%\Docker\wsl\distro: exit code: -1
stdout: The system cannot find the path specified.
Funny thing is: before I format the PC due to another issue everything was
working flawlessly (I was already using this Dev Channel Build)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/WSL/issues/6363#issuecomment-846003605, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVP2NEBD2S6K5LIEM7KULDTOZW4TANCNFSM4VD3JWJA
.

Does the folder exist? Because if that folder doesn't exist than it will raise such error.

Yes it does but i managed to finally solve the issue by deleting the file %USERPROFILE%\.wslconfig, restarting wsl and retrying the distro install. It is worth to check for this before doing any in-place upgrade...

Does the folder exist? Because if that folder doesn't exist than it will raise such error.

Yes it does but i managed to finally solve the issue by deleting the file %USERPROFILE%\.wslconfig, restarting wsl and retrying the distro install. It is worth to check for this before doing any in-place upgrade...

Thanks a lot, this is finally the one that able to solve mine as well.
I tried to do the upgrade-reset windows as well as I forgot someone said it is working on him but I cannot find his post again now. Didn't work though.

I was having issues reinstalling, just deleted the wslconfig file as suggested by @lokinmodar and it resolved my issue as well. Thanks for sharing.

Does the folder exist? Because if that folder doesn't exist than it will raise such error.

Yes it does but i managed to finally solve the issue by deleting the file %USERPROFILE%\.wslconfig, restarting wsl and retrying the distro install. It is worth to check for this before doing any in-place upgrade...

Thanks a lot, this is finally the one that able to solve mine as well.
I tried to do this repair-install

#6512 (comment)
Please do https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html and try to enable wsl again, it should work correctly. It mean there're some file missing. I seen this in many windows installation (clean windows), and the only way to fix it is either reset the windows or in-place upgrade. I choose In-place upgrade.

Didn't work for me.

====> This work for me.

For my case there's no .wslconfig file. The error persists on fresh install of windows 11.

For my case there's no .wslconfig file. The error persists on fresh install of windows 11.

any luck in fixing this?
I regretted so much to upgrade my windows..

None of the provided workarounds helped me.
I also don't have a .wslconfig. I still get the following error:
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070003
Error: 0x80070003 Das System kann den angegebenen Pfad nicht finden.

Press any key to continue...

Really enjoyed working with WSL so i hope this can get fixed 😞.

None of the provided workarounds helped me. I also don't have a .wslconfig. I still get the following error:
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070003
Error: 0x80070003 Das System kann den angegebenen Pfad nicht finden.

Press any key to continue...

Really enjoyed working with WSL so i hope this can get fixed 😞.

Back up data and reinstall win 11, I also reset it and it works.
But all applications need to re-install.

None of the provided workarounds helped me. I also don't have a .wslconfig. I still get the following error:
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070003
Error: 0x80070003 Das System kann den angegebenen Pfad nicht finden.

Press any key to continue...

Really enjoyed working with WSL so i hope this can get fixed 😞.

Back up data and reinstall win 11, I also reset it and it works. But all applications need to re-install.

I'm on Windows 10. Idk why, but WSL just suddenly stopped working.
I really don't want to reinstall windows all over again... I'd rather use a Linux Machine on Hyper-V, haha.
I feel like there must be another wokraround or fix.

Any progress?
I am using windows 11

Does the folder exist? Because if that folder doesn't exist than it will raise such error.

Yes it does but i managed to finally solve the issue by deleting the file %USERPROFILE%\.wslconfig, restarting wsl and retrying the distro install. It is worth to check for this before doing any in-place upgrade...

Forgot about this lurking around when I compiled a custom kernel :)

I came across this same issue on Windows 10 Home.
I have enabled virtualization on my BIOS and enabled both Virtual Machine Platform and Windows Hypervisor Platform Windows Features. I have tried re-installing these features multiple times but I couldn't make it work.
I was finally able to fix the issue by doing a a Windows In-Place Upgrade. More specifically I followed the direction in this tutorial: repair-install-windows-10-place-upgrade to do the upgrade with the ISO file.
Hope this can help someone :)

Saying "there's some file missing" isn't helpful. Not everyone in corporate settings can do an in-place upgrade.

Hi !
I have the same problem, when I try to install a Linux distribution on my Windows (because it is a WSL2 requirement, in order to run Docker Desktop on my local Windows10 laptop), I get this message:

Have you found a solution other than the one proposed by @benyaminl ?
It happens to me like @pdebuitlear , I have a corporative settings and I can't do an in-place upgrade.
Thankyou!

The fix for me was to set the following registry key value to 1: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\kernel\obcaseinsensitive

THANK YOU!!!!  This fixed my WSL issue, awesome!

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\kernel\obcaseinsensitive

Didn't work:

Windows 10, 19045.2364; Windows Feature Experience Pack 120.2212.4190.0

Open regedit
Find 计算机\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Lxss
删除Lxss下空的注册表项，例如：{24022fa9-20a9-4e2a-9cde-9c1bfe4e67f3}

Try this simple solution, it works with me
https://stackoverflow.com/a/67639264/1849480

I have not coded  for like a month because of this issue, any progress?

Disabling core isolation (VBS) and then reenabling and reinstalling WSL fixed the problem for me.

I managed to fix the problem by going to "Turn Windows featuers on or off" in Settings, unchecking "Virtual Machine Platform" and "Windows Subsystem for Linux", rebooting, and then reinstalling WSL.

Does the folder exist? Because if that folder doesn't exist than it will raise such error.

Yes it does but i managed to finally solve the issue by deleting the file %USERPROFILE%\.wslconfig, restarting wsl and retrying the distro install. It is worth to check for this before doing any in-place upgrade...

works for me!!

I just tried this solution but with Ubuntu-18.04.6 and Ubuntu-22.04.6 and it finally worked for me :)
https://github.com/microsoft/WSL/issues/3054#issuecomment-1783150815

Resolved WslRegisterDistribution failed with error: 0x80070003

Open regedit
Find 计算机\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Lxss
删除Lxss下空的注册表项，例如：{24022fa9-20a9-4e2a-9cde-9c1bfe4e6700}

This works for situations like you mishandle the regits qaq

Resolved WslRegisterDistribution failed with error: 0x80070003

Open regedit
Find 计算机\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Lxss
删除Lxss下空的注册表项，例如：{24022fa9-20a9-4e2a-9cde-9c1bfe4e6700}

it works for me after delete items under Lxss, thanks.

Hello, I'm having the same error since installing Atlas OS on my computer. I have enabled the optional features, virtualization is enabled in BIOS, there is no .wslconfig file, there is no Lxss entry in my registry. I cannot do an in-place system upgrade. Any other solutions?

This issue has been open for a long time, and so we're going to close it out for bookkeeping purposes.
If you're still seeing this issue please check out this workaround: https://github.com/microsoft/WSL/issues/6363#issuecomment-1789786151 and if that doesn't fix you please file a new issue on our GitHub so we can actively triage you! Thanks!


Add Comelit 6741W

Hi, is it possible to add wifi video intercom 6741W support?
Even just the ability to open the gate and door.
Thank you
https://pro.comelitgroup.com/en-gb/product/6741w

Hi, unfortunately, I'm not in touch with this device.
Could you look into it?
Thank you

Hi, unfortunately, I'm not in touch with this device.
Could you look into it?
Thank you

Sure, if I can help in any way.  I use it with google assistant at the moment

I'm interested too. I have the device and I can do any test you like. I'm using it with the alexa skill and it works but I look forward to use it in HA. I have downloaded the settings backup from the device and I can attach it if you think it useful.
It has an http.cfg
httpListenPort.0 = 0:2:8080
httpListenSSLPort.0 = 0:2:8443
httpPageCompression.0 = 0:2:1
httpWebLanguage.0 = 0:2:-1
httpAdminPassword.0 = 0:4:"comelit"
httpAptManagerPassword.0 = 0:4:"admin"
httpAdminEnabled.0 = 0:2:1
and some configurations related to mqtt in mqttslk.cfg and comelit cloud services on registerd.cfg
the device is reachable at
PORT      STATE SERVICE
53/tcp    open  domain
8080/tcp  open  http-proxy
8443/tcp  open  https-alt
64100/tcp open  unknown

Unfortunately, it's not just a matter of configuration. The intercom has a life of its own away from the Comelit hub, so I cannot work on the development side without it. I can help with the process, but it is really hard to add support without the device.
You need to start sniffing for the HTTP traffic. I really don't know which protocol it uses.

Can you do things from the web panel? Or is it just something you use to configure/manage the system?

The web seems for configuring / managing the device but I don't know if there is an exposed API or something like that.

mmm, so you need to sniff the app's traffic

ok, the app talks to the device on the 64100 port, on that port a web server is listening so probably this is one way. I'll sniff around and I'll get back to you.

Thanks all for try to add!!

Hi all,
here is a recap of what I learned so far.
The device listens on:
TCP

53/tcp    open  domain
8080/tcp  open  http-proxy ---/USED By modern by web control panel
8443/tcp  open  https-alt ---/USED By modern by web control panel
64100/tcp open  unknown ---/USED By modern by legacy app

UDP

53/udp   open|filtered domain
123/udp  open          ntp
161/udp  open          snmp ---/USED By SNMP, accessible by public
5353/udp open|filtered zeroconf

The device has two operating modes a modern one using comelit cloud services and a legacy local one using a dismissed app.
The Cloud mode
-The hosts involved  are:
-  	developer.cloud.comelitgroup.com:443 --/USED by the swagger documentation https://developer.cloud.comelitgroup.com/mugconf/index.html
-  eps.cloud.comelitgroup.com	--/USED by the device to share info with the cloud about endpoints
- 	moduleapp.cloud.comelitgroup.com:443 --/USED by the modern app to talk with the cloud API
- 	checkweb.cloud.comelitgroup.com:80 --/ USED by the device for a connection checker keep-alive that calls home every while
-Rely on a PJSIP-based infrastructure for the audio/video transmission
-The audio/video is transmitted in UDP
I was able to sniff and decode a couple of interactions:
________DEVICE talks to cloud
POST /servicerest/p2p/start HTTP/1.1
Host: eps.cloud.comelitgroup.com
User-Agent: libnebula-agent/1.0
Accept: /
authorization: ccstoken DbKEsR6AiuEM11vR39pQMrREDACTED
content-type: application/json
Content-Length: 1007
{"deviceUuid":"be4bdc9e-a822-47a0-8d1d-REDACTED-00001","data":{"authMode":"user_viper_token","secret":"REDACTED","timeout":10,"sdp":"BASE64 payload"},"protocol":{"name":"viper_p2p_v2","version":1}}HTTP/1.1 200 OK
--Decoded sdp=base64 payload
v=0
o=- 993454509 993454509 IN IP4 <IP_ADDRESS>
s=ice
t=0 0
a=nego-wait:0
a=comelit-legacy-session:TCP
a=comelit-session-id:MUX
a=comelit-nego-aggressive:true
c=IN IP4 <IP_ADDRESS>
m=audio 15001 RTP/SAVPF 0 8
b=RS:0
b=RR:0
c=IN IP4 <IP_ADDRESS>
a=sendrecv
a=candidate:Sc0a80132 1 UDP<PHONE_NUMBER> <IP_ADDRESS> 15001 typ srflx raddr <IP_ADDRESS> rport 56373
a=candidate:Sc0a80132 1 UDP<PHONE_NUMBER> <IP_ADDRESS> 15002 typ srflx raddr <IP_ADDRESS> rport 56373
a=candidate:Hc0a80132 1 UDP<PHONE_NUMBER> <IP_ADDRESS> 56373 typ host
a=ice-role:a
a=ice-ufrag:5ab08d4b
a=ice-pwd:20334ed64ed9fREDACTED
Server: nginx/1.23.3
Date: Thu, 23 May 2024 14:49:00 GMT
Content-Type: application/json
Content-Length: 942
Access-Control-Allow-Origin: https://developer.cloud.comelitgroup.com
Access-Control-Allow-Methods: *
Access-Control-Allow-Headers: *
Via: 1.1 google
Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
{"result":"SUCCESS","data":{"sdp":"BASE64payload"}}
--Decoded sdp base 64 payload
v=0
o=-<PHONE_NUMBER><PHONE_NUMBER> IN IP4 <IP_ADDRESS>
s=ice
t=0 0
a=nego-wait:0
a=comelit-legacy-session:TCP
a=comelit-session-id:MUX
m=audio 63603 RTP/SAVPF 8
c=IN IP4 <IP_ADDRESS>
a=sendrecv
a=candidate:Sc0a8019c 1 UDP<PHONE_NUMBER> <IP_ADDRESS> 44914 typ srflx raddr <IP_ADDRESS> rport 54063
a=candidate:Sc0a8019c 1 UDP<PHONE_NUMBER> <IP_ADDRESS> 44915 typ srflx raddr <IP_ADDRESS> rport 54063
a=candidate:Hc0a8019c 1 UDP<PHONE_NUMBER> <IP_ADDRESS> 54063 typ host
a=candidate:R2d4d341e 1 UDP 16777215 <IP_ADDRESS> 63603 typ relay raddr <IP_ADDRESS> rport 20820
a=ice-role:o
a=ice-ufrag:59b3353f
a=ice-pwd:7c4f38cb1971c0REDACTED
a=ssrc:0 cname:user60696REDACTED@host-15709REDACTED
________Modern app talks to cloud
POST /servicerest/appbundlecheck/verify HTTP/1.1
Host: moduleapp.cloud.comelitgroup.com
Accept: application/json
Content-Type: application/json
Content-Length: 214
{"ccapi":{"version":"1.1.0","endpoint":{"requuid":"1469265513","service":"appbundlecheck/verify","version":"1.1.0"},"login":{},"body":{"bundle":"com.comelit.bigapp","appId":"058dbeff-d5ee-4f26-a0a7-22e18e09fcc6"}}}HTTP/1.1 200
Server: nginx/1.23.3
Date: Thu, 23 May 2024 14:48:58 GMT
Content-Type: application/json
Content-Length: 196
Access-Control-Allow-Origin: https://developer.cloud.comelitgroup.com
Access-Control-Allow-Methods: *
Access-Control-Allow-Headers: *
Via: 1.1 google
Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
{"ccapi":{"version":"1.1.0","endpoint":{"service":"appbundlecheck/verify","version":"1.1.0","requuid":"1469265513"},"login":{},"body":{"allowed":true},"error":{"code":0,"action":0,"message":""}}}
**The legacy mode **
-It requires a dismissed APP "ComelitViP Remote” or older "App Intercall Remote ViP". I was able to download the first one from a legacy store and looking at.
-It uses the 64100 port that has an active server listening, not identified at the moment
-Not cloud-based, you can reach it locally or remotely via port forwarding

Hi, any news about gate open integration?

Nothing new, I think no one is working on this feature.

Hi all, my building just decided to replace the broken interphone system with this one. Something I applauded because I hoped the Comelit Integration would allow me to add the video camera to my dashboard. But now I see things are not so simple. I really hope someone can continue this work and am most willing to test whatever is developed...


Folder names are not shown

I would like to point out to a minor issue happening on Manjaro Linux KDE (latest):

In order to show the names of folders, it is necessary to click over them instead of the name appearing automatically.
Thank you very much for your hard work ! I hope the suggestion would be useful...

Build failed.. will look at that when I have the time

After updating Manjaro today, the issue has been solved !
Might have been an OS specific issue or KDE related.
Thanks for your kind help! Your GUI has been a life saver !

Glad your enjoying it and that the issue is resolved.
I actually did not expect anybody else to use the GUI and packaged it as a
snap just to see if I could get it to work.
Feel free to open an issue on GitHub if you find something new or have a
suggestion for an enhancement.
On Tue, Sep 14, 2021, 19:20 marreromarco @.***> wrote:

After updating Manjaro today, the issue has been solved !
Might have been an OS specific issue or KDE related.
Thanks for your kind help! Your GUI has been a life saver !
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/alexanderlanganke/ocrmypdfgui/issues/22#issuecomment-919356373,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKF5ELXJGZLPJWDHT475KNTUB575NANCNFSM5C36PO6A
.


Remove dependency on Permit.SDK to support HttpClientFactory

To improve performance, we need to use HttpClientFactory which the Permit.SDK is not used.
For this reason only the Allowed endpoint is implemented and it also used the System.Json library to even better performance.

I still need to run integration tests.
After those it would be nice to have the package release on NuGet

Awesome stuff @matteobortolazzo - much appreciated.
Let us know once you're ready for review
CC: @obsd

Hi, you can review and merge, I realized I need a few more PRs to have a complete package. After those it can be released

Added support for the new Minimal APIs and fixed the call to the PDP

@obsd is it ok to merge? And should the library cover all PDP endpoints? In that case there can be a another PR, I can consider  a code generator based on the openai file

@matteobortolazzo congrats on this!
Did we send you some swag yet? If not @danielbass37 please make sure we do ;-)

No swag yet :)

Hey @matteobortolazzo! The package is already on its way :)

Hey @matteobortolazzo! The package is already on its way :)

Nice 😁 but I moved last week 😂 but no worries thanks 😁

Hi Matteo can you still get mail delivered to that address? If not let us
know the new address and we'll ship you a new one.
On Fri, Feb 9, 2024, 22:42 Matteo Bortolazzo @.***>
wrote:

Hey @matteobortolazzo https://github.com/matteobortolazzo! The package
is already on its way :)
Nice 😁 but I moved last week 😂 but no worries thanks 😁
—
Reply to this email directly, view it on GitHub
https://github.com/permitio/permit-aspnet/pull/1#issuecomment-1936575650,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAP3ULOO4TEEO35KKAK2HLTYS2CZRAVCNFSM6AAAAABCJEYR2CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWGU3TKNRVGA
.
You are receiving this because you commented.Message ID:
@.***>

Hi Matteo can you still get mail delivered to that address? If not let us
know the new address and we'll ship you a new one.
On Fri, Feb 9, 2024, 22:42 Matteo Bortolazzo @.***>
wrote:

Hey @matteobortolazzo https://github.com/matteobortolazzo! The package
is already on its way :)
Nice 😁 but I moved last week 😂 but no worries thanks 😁
—
Reply to this email directly, view it on GitHub
https://github.com/permitio/permit-aspnet/pull/1#issuecomment-1936575650,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAP3ULOO4TEEO35KKAK2HLTYS2CZRAVCNFSM6AAAAABCJEYR2CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWGU3TKNRVGA
.
You are receiving this because you commented.Message ID:
@.***>

No worries, there should be no problem :)


chore: Delete outdated files & merge configs into pyproject.toml

Closes #6262
I've gone ahead and deleted .gitlab-ci.yml with this. Do we still depend on the GitLab pipelines for anything important? If so, are there issues open to track the migrate of these CI elements over to GitHub workflows/actions?

Coverage is handled separately in https://github.com/meltano/meltano/pull/6304

@WillDaSilva This removes the lint checks that were running on gitlab ci, but I'm not sure if we want to simply adapt the old implementation (which had some drawbacks) or pursue a different approach.

This removes the lint checks that were running on gitlab ci, but I'm not sure if we want to simply adapt the old implementation (which had some drawbacks) or pursue a different approach.

@edgarrmondragon I'll open an issue to address that, and switch this PR to a draft.

Superseded by:

https://github.com/meltano/meltano/pull/6837
https://github.com/meltano/meltano/pull/6838
https://github.com/meltano/meltano/pull/6839
https://github.com/meltano/meltano/pull/6842
https://github.com/meltano/meltano/pull/6843
https://github.com/meltano/meltano/pull/6847


Add support for request-received middleware

The request-received middleware at https://github.com/cabinjs/request-received exposes a Symbol.for property, which this package could conditionally consume if interested (as opposed to just generating a new Date().
e.g. https://github.com/pinojs/pino-http/blob/master/logger.js#L63 would change as follows:
-    res[startTime] = res[startTime] || Date.now()
+    res[startTime] = res[startTime] || req[Symbol.for('request-received.startTime')] ? req[Symbol.for('request-received.startTime')].getTime() : Date.now()

Ref: #65

PR #67 opened


Document Eddystone example code

@pan-

This PR addresses https://github.com/ARMmbed/ble-examples/issues/49


Trouble with timing

C:\Users\vinicius.maureira\Documents\Testing\Pipeline Cybertrust>pbixrefresher Cybertrust-Pipeline.pbix
Starting Power BI
Identifying Power BI window
Refreshing
Saving
Publish
Traceback (most recent call last):
File "C:\Program Files\Python36\lib\site-packages\pywinauto\application.py", line 245, in __resolve_control
criteria)
File "C:\Program Files\Python36\lib\site-packages\pywinauto\timings.py", line 447, in wait_until_passes
raise err
pywinauto.timings.TimeoutError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "pbixrefresher.py", line 72, in
publish_dialog.child_window(title = WORKSPACE).click_input()
File "C:\Program Files\Python36\lib\site-packages\pywinauto\application.py", line 351, in getattribute
ctrls = self.__resolve_control(self.criteria)
File "C:\Program Files\Python36\lib\site-packages\pywinauto\application.py", line 248, in __resolve_control
raise e.original_exception
File "C:\Program Files\Python36\lib\site-packages\pywinauto\timings.py", line 425, in wait_until_passes
func_val = func(*args)
File "C:\Program Files\Python36\lib\site-packages\pywinauto\application.py", line 209, in __get_ctrl
ctrl = self.backend.generic_wrapper_class(findwindows.find_element(**ctrl_criteria))
File "C:\Program Files\Python36\lib\site-packages\pywinauto\findwindows.py", line 87, in find_element
raise ElementNotFoundError(kwargs)
pywinauto.findwindows.ElementNotFoundError: {'auto_id': 'KoPublishToGroupDialog', 'top_level_only': False, 'parent': <uia_element_info.UIAElementInfo - 'Cybertrust-Pipeline - Power BI Desktop', WindowsForms10.Window.8.app.0.17ad52b_r8_ad1, 722594>, 'backend': 'uia'}
don´t refresh and don't save

Hello @viniciusmauser & @dubravcik
What did you guys do for timeout Error? I also get the same. Any idea how to get rid of this will highly appreciate.  Thank you so much
C:\#AutoRefresh\Top100>python top100pbixrefresher.py Starting Power BI Identifying Power BI window Refreshing Traceback (most recent call last):   File "top100pbixrefresher.py", line 95, in <module>     main()   File "top100pbixrefresher.py", line 59, in main     win.wait("enabled", timeout = 300)   File "C:\Users\dbulugahamulle\AppData\Local\Programs\Python\Python36\lib\site-packages\pywinauto\application.py", line 501, in wait     lambda: self.__check_all_conditions(check_method_names, retry_interval))   File "C:\Users\dbulugahamulle\AppData\Local\Programs\Python\Python36\lib\site-packages\pywinauto\timings.py", line 367, in wait_until     raise err pywinauto.timings.TimeoutError: timed out

Its working perfectly fine. I have put refresh iteration every 2 mins and it worked perfect. :)

I am facing exactly the same issue. The code breaks and ask "Do you want to save your changes" and throws an error.


Session expired error every 5 min in saleor admin after set JWT_EXPIRE='True'

What I'm trying to achieve
I set JWT_EXPIRE='True' in my server, so that the access token will expire every 5 min, but I'm having a problem in the admin panel, every 5 min it closes my session, this is normal?
Steps to reproduce the problem

Setup Saleor 2.11.0 in Ubuntu 20.04 server
Set environment variable JWT_EXPIRE='True'
Hosting as static website the Dashboard on amazon bucket
Try to stay login after 5 min

What I expected to happen
Shouldn't the user stay logged in with a silent authentication after 5 minutes?
Screenshots
Current problem

Configured environment variables

Http request and response from inspector
In the screenshot I put the response of the last graphql request.

Console output
This happens after trying to enter one of the administrator tabs, in this case the product tab, after 5 minutes.

System information
Saleor version:

[ ] dev (current master)
[ ] 3.0
[x] 2.11
[ ] 2.10

Operating system:

[ ] Windows
[x] Linux
[ ] MacOS
[ ] Other

Browser:

[ ] Safari
[x] Chrome
[ ] Edge
[ ] Other

I've managed to hack it and get it work in version saleor 3.0 maybe 2.11.x, using apollo-link onError
Having below two files modified, auto refresh token will work like a charm.
Inspired by https://able.bio/AnasT/apollo-graphql-async-access-token-refresh--470t1c8
This feature is so in need, and hope Saleor team could implement it in the near future, thx.
// src/auth/link.ts
import { fromPromise } from "apollo-link";
import { setContext } from "apollo-link-context";
import { ErrorResponse, onError } from "apollo-link-error";

import { getTokens, removeTokens } from "./";
import { isJwtError, isTokenExpired, JWTError } from "./errors";

interface ResponseError extends ErrorResponse {
  networkError?: Error & {
    statusCode?: number;
    bodyText?: string;
  };
}

export const invalidateTokenLink = onError((error: ResponseError) => {
  if (
    (error.networkError && error.networkError.statusCode === 401) ||
    error.graphQLErrors?.some(isJwtError)
  ) {
    if (error.graphQLErrors[0].extensions.code !== JWTError.expired) {
      removeTokens();
    }
  }
});

export const tokenLink = setContext((_, context) => {
  const authToken = getTokens().auth;

  return {
    ...context,
    headers: {
      ...context.headers,
      Authorization: authToken ? `JWT ${authToken}` : null
    }
  };
});

const link = invalidateTokenLink.concat(tokenLink);

export default link;

// ======hacking starts ======
let isRefreshing = false;
let pendingRequests = [];

const resolvePendingRequests = () => {
  pendingRequests.map(callback => callback());
  pendingRequests = [];
};

export function prepareErrorLink(tokenRefresh: ()=> Promise<boolean>) {
  const errorLink = onError(
    ({ graphQLErrors, response, operation, forward }) => {
      if (graphQLErrors.some(isJwtError) && graphQLErrors.every(isTokenExpired)) {
        // no error in the operation
        response.errors = null;
        let forward$;
        if (!isRefreshing) {
          isRefreshing = true;
          forward$ = fromPromise(
            tokenRefresh()
              .then((success) => {
                // Store the new tokens for your auth link
                // The token storing logic has been already handled in src/auth/hooks/use(Saleor|Exxternal)AuthProvider.ts
                resolvePendingRequests();
                return success;
              })
              .catch(error => {
                pendingRequests = [];
                // Handle token refresh errors e.g clear stored tokens, redirect to login, ...
                console.error(error);
                console.error('should show a msg and then redirect to login');
                return;
              })
              .finally(() => {
                isRefreshing = false;
              })
          ).filter(value => Boolean(value));
        } else {
          // Will only emit once the Promise is resolved
          forward$ = fromPromise(
            new Promise(resolve => {
              pendingRequests.push(() => resolve(undefined));
            })
          );
        }

        return forward$.flatMap(() => forward(operation));
      }
    }
  );
  return errorLink;
}
// ======hacking ends ======

// src/index.tsx
import useAppState from "@saleor/hooks/useAppState";
import { defaultDataIdFromObject, InMemoryCache } from "apollo-cache-inmemory";
import { ApolloClient } from "apollo-client";
import { ApolloLink } from "apollo-link";
import { BatchHttpLink } from "apollo-link-batch-http";
import { createUploadLink } from "apollo-upload-client";
import React, { useContext, useEffect } from "react";
import { ApolloProvider } from "react-apollo";
import { render } from "react-dom";
import ErrorBoundary from "react-error-boundary";
import TagManager from "react-gtm-module";
import { useIntl } from "react-intl";
import { BrowserRouter, Route, Switch } from "react-router-dom";

import AppsSection from "./apps";
import { appsSection } from "./apps/urls";
import AttributeSection from "./attributes";
import { attributeSection } from "./attributes/urls";
import Auth, { UserContext } from "./auth";
import AuthProvider, { useAuth } from "./auth/AuthProvider";
import LoginLoading from "./auth/components/LoginLoading/LoginLoading";
import SectionRoute from "./auth/components/SectionRoute";
import authLink, { prepareErrorLink } from "./auth/link";
import { hasPermission } from "./auth/misc";
import CategorySection from "./categories";
import ChannelsSection from "./channels";
import { channelsSection } from "./channels/urls";
import CollectionSection from "./collections";
import AppLayout from "./components/AppLayout";
import useAppChannel, {
  AppChannelProvider
} from "./components/AppLayout/AppChannelContext";
import { DateProvider } from "./components/Date";
import { LocaleProvider } from "./components/Locale";
import MessageManagerProvider from "./components/messages";
import { ShopProvider } from "./components/Shop";
import ThemeProvider from "./components/Theme";
import { WindowTitle } from "./components/WindowTitle";
import { API_URI, APP_MOUNT_URI, GTM_ID } from "./config";
import ConfigurationSection, { createConfigurationMenu } from "./configuration";
import AppStateProvider from "./containers/AppState";
import BackgroundTasksProvider from "./containers/BackgroundTasks";
import ServiceWorker from "./containers/ServiceWorker/ServiceWorker";
import { CustomerSection } from "./customers";
import DiscountSection from "./discounts";
import HomePage from "./home";
import { commonMessages } from "./intl";
import NavigationSection from "./navigation";
import { navigationSection } from "./navigation/urls";
import { NotFound } from "./NotFound";
import OrdersSection from "./orders";
import PageSection from "./pages";
import PageTypesSection from "./pageTypes";
import PermissionGroupSection from "./permissionGroups";
import PluginsSection from "./plugins";
import ProductSection from "./products";
import ProductTypesSection from "./productTypes";
import errorTracker from "./services/errorTracking";
import ShippingSection from "./shipping";
import SiteSettingsSection from "./siteSettings";
import StaffSection from "./staff";
import TaxesSection from "./taxes";
import TranslationsSection from "./translations";
import { PermissionEnum } from "./types/globalTypes";
import WarehouseSection from "./warehouses";
import { warehouseSection } from "./warehouses/urls";

if (process.env.GTM_ID) {
  TagManager.initialize({ gtmId: GTM_ID });
}

errorTracker.init();

// DON'T TOUCH THIS
// These are separate clients and do not share configs between themselves
// so we need to explicitly set them
const linkOptions = {
  credentials: "include",
  uri: API_URI
};
const uploadLink = createUploadLink(linkOptions);
const batchLink = new BatchHttpLink({
  batchInterval: 100,
  ...linkOptions
});

const link = ApolloLink.split(
  operation => operation.getContext().useBatching,
  batchLink,
  uploadLink
);

const apolloClient = new ApolloClient({
  cache: new InMemoryCache({
    dataIdFromObject: (obj: any) => {
      // We need to set manually shop's ID, since it is singleton and
      // API does not return its ID
      if (obj.__typename === "Shop") {
        return "shop";
      }
      return defaultDataIdFromObject(obj);
    }
  }),
  link: authLink.concat(link)
});

const App: React.FC = () => {
  const isDark = localStorage.getItem("theme") === "true";

  return (
    <ApolloProvider client={apolloClient}>
      <BrowserRouter basename={APP_MOUNT_URI}>
        <ThemeProvider isDefaultDark={isDark}>
          <DateProvider>
            <LocaleProvider>
              <MessageManagerProvider>
                <ServiceWorker />
                <BackgroundTasksProvider>
                  <AppStateProvider>
                    <ShopProvider>
                      <AuthProvider>
                        <AppChannelProvider>
                          <Routes />
                        </AppChannelProvider>
                      </AuthProvider>
                    </ShopProvider>
                  </AppStateProvider>
                </BackgroundTasksProvider>
              </MessageManagerProvider>
            </LocaleProvider>
          </DateProvider>
        </ThemeProvider>
      </BrowserRouter>
    </ApolloProvider>
  );
};

const Routes: React.FC = () => {
  const intl = useIntl();
  const [, dispatchAppState] = useAppState();

  const {
    hasToken,
    isAuthenticated,
    tokenAuthLoading,
    tokenVerifyLoading,
    user
  } = useAuth();
  const { channel } = useAppChannel(false);

  const channelLoaded = typeof channel !== "undefined";

  const homePageLoaded =
    channelLoaded &&
    isAuthenticated &&
    !tokenAuthLoading &&
    !tokenVerifyLoading;

  const homePageLoading =
    (isAuthenticated && !channelLoaded) || (hasToken && tokenVerifyLoading);
  // ======hacking starts ======

  // set a new link after apollo client installation
  const userContext = useContext(UserContext);
  useEffect(() => {
    const errorLink = prepareErrorLink(userContext.tokenRefresh);
    // apolloClient.setLink() in version 3.0
    // copy from https://github.com/apollographql/apollo-client/blob/efa593dada250f5e60a747e01d4a4737f222dbd5/src/ApolloClient.ts
    apolloClient.link = apolloClient.queryManager.link = errorLink.concat(apolloClient.link);
  }, []); // empty dependent array so that execute this logic only once

  // ======hacking ends ======
  return (
    <>
      <WindowTitle title={intl.formatMessage(commonMessages.dashboard)} />
      {homePageLoaded ? (
        <AppLayout>
          <ErrorBoundary
            onError={e => {
              const errorId = errorTracker.captureException(e);

              dispatchAppState({
                payload: {
                  error: "unhandled",
                  errorId
                },
                type: "displayError"
              });
            }}
          >
            <Switch>
              <SectionRoute exact path="/" component={HomePage} />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_PRODUCTS]}
                path="/categories"
                component={CategorySection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_PRODUCTS]}
                path="/collections"
                component={CollectionSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_USERS]}
                path="/customers"
                component={CustomerSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_DISCOUNTS]}
                path="/discounts"
                component={DiscountSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_PAGES]}
                path="/pages"
                component={PageSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_PAGES]}
                path="/page-types"
                component={PageTypesSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_PLUGINS]}
                path="/plugins"
                component={PluginsSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_ORDERS]}
                path="/orders"
                component={OrdersSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_PRODUCTS]}
                path="/products"
                component={ProductSection}
              />
              <SectionRoute
                permissions={[
                  PermissionEnum.MANAGE_PRODUCT_TYPES_AND_ATTRIBUTES
                ]}
                path="/product-types"
                component={ProductTypesSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_STAFF]}
                path="/staff"
                component={StaffSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_STAFF]}
                path="/permission-groups"
                component={PermissionGroupSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_SETTINGS]}
                path="/site-settings"
                component={SiteSettingsSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_SETTINGS]}
                path="/taxes"
                component={TaxesSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_SHIPPING]}
                path="/shipping"
                component={ShippingSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_TRANSLATIONS]}
                path="/translations"
                component={TranslationsSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_MENUS]}
                path={navigationSection}
                component={NavigationSection}
              />
              <SectionRoute
                permissions={[
                  PermissionEnum.MANAGE_PRODUCT_TYPES_AND_ATTRIBUTES
                ]}
                path={attributeSection}
                component={AttributeSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_APPS]}
                path={appsSection}
                component={AppsSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_PRODUCTS]}
                path={warehouseSection}
                component={WarehouseSection}
              />
              <SectionRoute
                permissions={[PermissionEnum.MANAGE_CHANNELS]}
                path={channelsSection}
                component={ChannelsSection}
              />
              {createConfigurationMenu(intl).filter(menu =>
                menu.menuItems.map(item => hasPermission(item.permission, user))
              ).length > 0 && (
                <SectionRoute
                  exact
                  path="/configuration"
                  component={ConfigurationSection}
                />
              )}
              <Route component={NotFound} />
            </Switch>
          </ErrorBoundary>
        </AppLayout>
      ) : homePageLoading ? (
        <LoginLoading />
      ) : (
        <Auth />
      )}
    </>
  );
};

render(<App />, document.querySelector("#dashboard-app"));

I'm still very interested in seeing this fixed Mr. Stale Bot.


Standalone : Mix not found

Laravel Mix Version: 5.0.9
Node Version (node -v): 12.5.0
NPM Version (npm -v): 6.9.0
OS: Windows 10

Description:
After add laravel mix in standalone mode, i run "npx mix" like the documentation said, but i received only this :
λ npx mix
npx: installed 1 in 1.226s
command not found: mix
Steps To Reproduce:
Install laravel mix in a vue cli app, in standalone mode, that's it.
Regards,
Christophe

The mix CLI is only available in Mix v6 which is not yet out of beta. You can grab the scripts to use for Mix 5.x from here: https://github.com/laravel/laravel/blob/d9e85605cbc491e710d9a2df1939ba2db773b404/package.json

Oh, good to know, but i've don't talk about my "Vue Version", i'm using vue-cli, so i don't have this :
    "scripts": {         "dev": "npm run development",         "development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --config=node_modules/laravel-mix/setup/webpack.config.js",         "watch": "npm run development -- --watch",         "watch-poll": "npm run watch -- --watch-poll",         "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --disable-host-check --config=node_modules/laravel-mix/setup/webpack.config.js",         "prod": "npm run production",         "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --config=node_modules/laravel-mix/setup/webpack.config.js"     },
i've this :
  "scripts": {     "serve": "vue-cli-service serve",     "build": "vue-cli-service build"   },
How can i use Laravel-mix with this configuration ? I think i'm missing something.

Mix cannot be used in conjunction with Vue CLI. If you are using Vue CLI you should use it's built in scripts via yarn or npm.
npm run serve
npm run build


Qutebrowser updated to v1.1.2!

Qutebrowser updated to v1.1.2!

It is already updated by @r15ch13

My update cronjob runs every full hour, so just be patient 😁

And I wonder that how can be so fast! 😄 I hope that one day WSL can run Arch. 🙏


Allow empty vectors

The design decision for the mandatory L > 0 constraint is unclear, since the user is free to specify it themselves anyway, but in its current form it forbids a very useful idiom of "possibly empty vector containing not more than N elements". Also, with it in place, NonEmptyVec seems somewhat redundant.

Ah, nevermind, I see this idiom is represented by OptBoundedVecToVec already.


Cloud Error Reporting Trace for ASP.NET Core

Allows for automated tracing of incoming requests to ASP.NET Core applications.  Trace data is sent to the Stackdriver Trace API.
This PR includes:

Middleware for Tracing
Unit tests
Documentation
Snippets and examples

Coming soon:

Integration Tests
Delegate Handler for Tracing outgoing requests.

As Mike seems to be on the case here, I'll wait until he's done - I wouldn't be reviewing it today anyway, as I'm off soon and this is a big thing to start last minute on Friday :)

Thanks! PTAL


System is frozen? No confirm_vote for delegator

Wise doesn't work? Votes are not coming out from delegator but there are send_voteorder from voters. Examples:
https://steemd.com/tx/3e584c2006bf2b5d832fea06afd99b20f6042f2a
https://steemd.com/tx/e2f05b26ca3f57bed3e6e0079e4e083c22ad1196
https://steemd.com/tx/d372da983a1a3afad6ebaec1162091067a8f03be

Thank you for reporting this.
It looks like, lack of response from @noisy account was caused by https://github.com/noisy-witness/steem-wise-cli/issues/8.
if voteorder was written into a blockchain, with a message like this:
[
    "v2:send_voteorder",
    {
        "delegator":"noisy",
        "ruleset":"Na wsparcie tagu #tematygodnia",
        "author":"steemit-polska",
        "permlink":"tematy-tygodnia-tematygodnia-33-wyniki",
        "weight":4955
    }
]

then that means that probably this is not a problem with Voter Page, and therefore I will close this issue in this repository. More info will be posted in https://github.com/noisy-witness/steem-wise-cli/issues/8


[BUG]

Before you begin

This is NOT Forlax's mod or any other mod. If you have issues related to those versions DO NOT post them here as they will be closed and disregarded immediately.
Do NOT post any form of illegal content (e.g. screenshots of you cracking a website with stolen credentials) and do NOT ask for Configs for websites. Doing that will result in a report to the GitHub security team and a permanent ban from posting to this repository.

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Version

Version [e.g. 1.0.1]

Additional context
Add any other context about the problem here.


Square Logos

Is your feature request related to a problem?
I want to use an Xarray logo on a Coiled docs page.  I'd really like to have a square logo, like this one:

But when I look at  https://github.com/pydata/xarray/tree/026aa7c073d03fb6d749c216be1d829816583fac/doc/_static/logos I only see logos like these:

Any tips?
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

@mrocklin, I'm not sure if this meets your needs 💯, but we have a couple of square logos in this folder: Xarray-assets/Icon

Yeah, I saw that, but I wanted an image with "Xarray" in the name, so the icon files don't quite do what I need.

(thanks for the response though)

Yeah, I saw that, but I wanted an image with "Xarray" in the name, so the icon files don't quite do what I need.

we missed this detail when we were redesigning the logo. we've got all the original designs/assets, so I thought putting together a new square logo would be pretty simple. I went ahead and tried it out :)

does this work for you?

and here's same logo for light background:

Those look cool.  I'd happily use them in our assets.
I'll say some generic things that would make these better (but I think you probably know all of this anyway).  These might be better if ...

They live in the repo or on a webpage somewhere where we can link to them with more confidence (although I guess this github comment will likely live forever)
They're well cropped (especially the dark background one)
They have transparent backgrounds
They have SVG and PNG outputs

Also, at first I thought it was weird to left-justify the text (putting the x on the same line as the boxes) but now I see how it creates a nice stairstep pattern on the right.  👍

@mrocklin, i was able to tweak the settings, such as cropping and background, and i have added four new logos to this pull request in xarray-contrib/xarray.dev repo. when you get a chance i could use your feedback in case i missed something.
thank you again for opening this issue. it gave me the motivation to finally work on this :)

Thanks @andersy005 !
also cc @scharlottej13 and @jrbourbeau who sometimes use xarray logos

Thanks as always @andersy005 : )


Implement asset cache busting for production builds

I've noticed that when building for production the CSS and JS files aren't cache busted. It would be nice if they were, do you know of an approach of how this would be possible?

Yeah, sounds like a good idea. Gotta investigate it.
This looks like a good starting point
tl;dr

Use [chunkhash] to add a content-dependent cache-buster to each file.

Use compiler stats to get the file names when requiring resources in HTML.

Generate the chunk-manifest JSON and inline it into the HTML page before loading resources.

Ensure that the entry point chunk containing the bootstrapping code doesn’t change its hash over time for the same set of dependencies.

also opened for further discussion :information_desk_person:


Fix a bug where fetching resource returns success even though fetching nested relationship fails.

Description
This PR fixes an issue where fetching resource would produce success value even though fetching one or more nested relationships has failed.
This is now fixed in a way that:

success is returned when all responses return success value.
failure is returned when we encounter first response that produced a failure value.

This solution is aligned with other places where we have similar logic.
I have also added a test that covers this scenario.

Great fix @Anteo95! Talked with @z-turk3 and @hhrvoic and they proposed putting this behaviour in options struct so the client can opt in based on their preferences. For example, one can fetch Optional model and don't care if backend returns 404 for it (in our case favourite logic could be the one, but we are fetching it via separate API call, outside of Halley)

@fgulan @z-turk3
I have added an option to configure the expected behaviour.
please check when you have time whether this makes sense to you.

(in our case favourite logic could be the one, but we are fetching it via separate API call, outside of Halley)

This is tricky one. To support this properly, we would need to be able to ignore based on response code. E.g. 404 can be transformed to favourite=false, but 401 can't.
I think it would be better to think about ways to transform response instead of ignoring failure in this broad sense. My feeling is that this would be too easy to misuse and hide actual failures accidentally.

In my opinion this favouriting example is not even related that much to Halley since you would have a similar problem without it where you would need some place to validate the response and then map the error to success because it's not actually an error. (I would say that this is not how backend should design that API in the first place and we should not receive an error here but that's another story...)
In fact we can already do that within Halley as far as I understand since Halley does not have it's own logic whether some response is  success or a failure that is entirely provided by the user of the library through implementation of RequesterInterface.
However I agree with @jcavar that ignoring of failures can be potentially misused and you can hide actual failures by accident (current implementation is also not good since it always hides nested failures).
I am not however sure whether we need to add explicit support for transforming responses into Halley as it would add additional complexity for the library and at the call site.
How I see it is that all nested requests including initial request should be seen as a "single" request in a sense that it either errors or succeeds. What I think can be improved is the way we handle errors when they happen. Instead of returning the first error that we encounter we could return a structure that contains all errors that occurred (since we are already waiting for all requests to finish by using zip). This way user of the library would receive "complete response" in both cases (success or failure) and can decide how to interpret the result.
It might be that I am missing something here since I have been only digging deeper into library since yesterday so please correct me if I misunderstood the problem.

In my opinion this favouriting example is not even related that much to Halley since you would have a similar problem without it where you would need some place to validate the response and then map the error to success because it's not actually an error. (I would say that this is not how backend should design that API in the first place and we should not receive an error here but that's another story...)

My understanding is that failure is implicitly mapped to optional which is then considered favorite=false?

In fact we can already do that within Halley as far as I understand since Halley does not have it's own logic whether some response is  success or a failure that is entirely provided by the user of the library through implementation of RequesterInterface.

I think the problem (and the reason for this suggested change) is Nested request whose failure needs to be transformed. I think we don't have context required to transform the response of Nested request at RequesterInterface level, but I am not sure about this either. If it can be done, then we don't need this new flag?

How I see it is that all nested requests including initial request should be seen as a "single" request in a sense that it either errors or succeeds.

I agree with this with caveat that failures can be transformed to successes. Otherwise, we have no way of dealing with API design that returns e.g. 404 as part of regular flow.

What I think can be improved is the way we handle errors when they happen. Instead of returning the first error that we encounter we could return a structure that contains all errors that occurred (since we are already waiting for all requests to finish by using zip). This way user of the library would receive "complete response" in both cases (success or failure) and can decide how to interpret the result.

Hmm, not sure how would this look from API side? What would be return type - (Response?, ErrorStruct?)?
If it is e.g. Result<Response, ErrorStruct> then we lose Response in error case (which in my option is ok).

Agree with both of you guys - it should be handled per single request. RequesterInterface is just too cumbersome since in most cases it is a singleton and we have to relay on URL comparing which is not the best solution.
For now I would keep the flag as you've added it. And if it is okay for all of our projects we can opt in by default to treating the 4xx/5xx response as failed.
As an improvement we could add a strategy provider on a call site (probably closure) which would give us a "window" where we can preprocess request or post process the response - there we could provide a key to the relationship rather than the URL which can be used as a comparison value wether the mapping should happen or not. That could solve the favourite example.
The whole failure chain of errors as a return parameter seems as an okay approach as well, then client can handle it however it likes

I am ok with merging this PR.
It's only improved the library by providing clients a way to opt in to nested failures.

I agree that the default flag value should be true as it looks like it fixes more issue then it causes
I think this is worth extra discussion though. In my opinion, the default value should be false as that seems like commonly needed behaviour. However, from backwards compatibility perspective, it should be true.

What are others thoughts about it?

First, thanks everyone for responding and for concrete discussion :)
I agree that relying on transforming specific URL requests in RequesterInterface implementation is cumbersome but I guess it's doable if we really need that currently. It probably makes more sense then to implement it per "relationship key" instead as you said but I would leave it for a separate PR then.

Hmm, not sure how would this look from API side? What would be return type - (Response?, ErrorStruct?)?
If it is e.g. Result<Response, ErrorStruct> then we lose Response in error case (which in my option is ok).

Good point, my idea was to just improve current implementation to not return first error (since that does not make much sense anyway because it's very unpredictable what first encountered error actually is) but rather something like a ErrorStruct as you specified. That would of course lose Response as it loses it now but would allow better error handling on the call site.
However that does not help you with this favouriting example as you want both the response and error at the same time I suppose?  I suppose because of examples like this I agree that it's useful to have ability to transform errors into successes per request.

@jcavar I think you misinterpreted it because as far as I can see
from backwards compatibility perspective the default value should be false but I have set it to true because it makes more sense to me.

Yes, sorry, you are right!