Is there a method to resolve partially defined items with GetItemCommand?

Hi all,
Currently working on the migration from v0 to v1, and one issue that I'm coming up against is an inability to retrieve partial items stored inside Dynamo via the GetItemCommand. I.E:
const testSchema = schema({
  first: string().key(),
  second string().key().default('blah'),
  third: string({
    required: 'atLeastOnce',
 status: string(),
  }),

export const testEntity = new Entity({
  name: 'test',
  table: testTable,
  schema: testSchema,
});

// Does an upsert, but does not define the third attribute
 await testEntity.build(UpdateItemCommand).item({
    first: 'test',
    status: 'testStatus',
  }).send();

 const getItem = await testEntity.build(GetItemCommand).key({
        first: 'test',
 }).send();

will then throw the below error
Error: Missing required attribute for formatting: 'third'. Partition key: test / Sort Key: Data
This is due to the attrFormatter being unable to format the returned item via the EntityFormatter. We have a decent chunk of integration tests where partial items are generated and then removed from DynamoDB so that we can verify that our use cases perform the expected actions against DynamoDB, so we were wondering if there was a way to specifically define an option inside the GetItemCommand to allow the retrieval of partial items.
I can see inside that there is an options.partial checked, but there doesn't seem to be a way to define that option specifically from building a GetItemCommand.

Hello @nicholas-yong !
No there's no way to do it atm, although a partial option wouldn't be too hard to implement. Would the attributes option work for you?
const { Item } = await PokemonEntity.build(GetItemCommand)
  .key({ pokemonId: 'pikachu1' })
  .options({
    attributes: ['type', 'level'] // <= Creates a projection expression
  })
  .send()

Hello @nicholas-yong !
No there's no way to do it atm, although a partial option wouldn't be too hard to implement. Would the attributes option work for you?
const { Item } = await PokemonEntity.build(GetItemCommand)
  .key({ pokemonId: 'pikachu1' })
  .options({
    attributes: ['type', 'level'] // <= Creates a projection expression
  })
  .send()

Hey @ThomasAribart thanks for getting back so quickly. Yup a partial option would be the best way forward I think.
I did try with the attributes option as you mentioned but got the same issue. It seems the error has to do with the retrieval of the item iself.


[Story] Update the home page with number of challenges, organization, etc. from the backend

What projects is this story for?
OpenChallenges
As a user, I want
TBD
Description
No response
Acceptance criteria
No response
Tasks
No response
Anything else?
No response
Have you linked this story to a GitHub Project?

[X] I have linked this story to a GitHub Project and set its metadata.

@vpchung I will try to do that before the release of the PP, otherwise we will continue to hardcode the number on the home page a little longer.


Pull request for issue #156

The full description of the issue:
https://github.com/mojombo/jekyll/issues#issue/156
The patch is an option to do:
URL: /2010/02/27/first-post
File: /2010/02/27/first-post.html
Instead of:
URL: /2010/02/27/first-post
File: /2010/02/27/first-post/index.html
The branch should hopefully merge cleanly.
Cheers,
Pedro

This accomplishes the same thing as the :title.html permalink specification. The added test here still passes with the following change:
--- a/test/test_post.rb
+++ b/test/test_post.rb
@@ -352,9 +352,9 @@ class TestPost < Test::Unit::TestCase
         end

         should "write properly without creating folder" do
-          @site.no_post_dirs = true
+          @site.no_post_dirs = false
           post = setup_post("2008-10-18-foo-bar.textile")
-          post.site.permalink_style = ":title"
+          post.site.permalink_style = ":title.html"
           do_render(post)
           post.write(dest_dir)

I'm trying to achieve two things:

Have the file hierarchy with "post-name.html" instead of "post-name/index.html"
Have the permalinks be to "post-name" instead of "post-name/" or "post-name.html"

Setting permalink_style to ":title.html" achieves 1 but not 2 (it adds the .html to the links). The test was checking for 1 and not 2 and that's why setting permalink_style to ":title.html" was making the test pass. I'll review the test code, rebase it against the latest version and resubmit the pull request.


TypeScript typing support

Hi, the module looks great! I'm trying to draw dynamic 2d textures using this.
Are there any typescript types available for the module?
Thanks!

For potentially upgrade easily from https://github.com/alibaba/GCanvas , there is no plan to change js to ts.

For potentially upgrade easily from https://github.com/alibaba/GCanvas , there is no plan to change js to ts.


host/gap: fix doxygen for ble_gap_ext_disc()

Documentation for the parameters filter_duplicates and filter_policy for ble_gap_ext_disc() was missing. This made me mix up parameters a couple of times now, so I decided to fix this :-)
Not 100% sure if I understood the usage of those parameters correctly and got the parameter description just right - so any enhancements are welcome!

and go.


Add a script to query pilot for proxy configurations

What this PR does / why we need it:
This script issues curl requests to pilot for LDS/RDS/CDS/SDS configurations. It makes it easier for the user to examine the current proxy configurations in the system for debugging and learning purposes.
Which issue this PR fixes
fixes 1641
Special notes for your reviewer:
Release note:

@baodongli: Adding do-not-merge/release-note-label-needed because the release note process has not been followed.

One of the following labels is required "release-note", "release-note-action-required", or "release-note-none".
Please see: https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md#write-release-notes-if-needed.
Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Hi @baodongli. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/ok-to-test

@baodongli: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-e2e-smoketest.sh
eb06e658928e00c226198b3c9f5b1ff9a323d8c8
link
/test pilot-e2e-smoketest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Can't see what caused the failure. Looks like it timed out on getting k9s nodes. Can it be retested?

Sorry we are moving repos. Can you resubmit this script to istio/istio?

PR Submitted to istio/isto


The special test case for explicit cerficate passing

Has been included and hardly reworked in the #348 so I am closing it to avoid unnecessary clashes


feature(provisioner) Add a default mssql provisioner

Adding a new default provider for a mssql database.
Description
Created a new default provider template for a mssql db based on already existing mysql and postgres ones. Updated zz-default.provisioners.yaml and README.md.
What does this PR do?
Adding a new default provider for a mssql database per feature request https://github.com/score-spec/score-k8s/issues/66
Was tested with the following score.yaml file:
apiVersion: score.dev/v1b1
metadata:
    name: test-container
containers:
    main:
        image: mcr.microsoft.com/mssql-tools
        variables:
            SERVER_NAME: ${resources.db.host}
            MSSQL_SA_USER: ${resources.db.username}
            MSSQL_SA_PASSWORD: ${resources.db.password}
        command:
            - /bin/sh
            - -c
            - /opt/mssql-tools/bin/sqlcmd -S $SERVER_NAME -U $MSSQL_SA_USER -P $MSSQL_SA_PASSWORD -Q "select @@version"
resources:
    db:
        type: mssql

Once deployed in a k3s cluster, the following was succesfully logged by the test-container:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Microsoft SQL Server 2022 (RTM-CU15-GDR) (KB5046059) - 16.0.4150.1 (X64)
     Sep 25 2024 17:34:41
     Copyright (C) 2022 Microsoft Corporation
     Developer Edition (64-bit) on Linux (Ubuntu 22.04.5 LTS) <X64>

  (1 rows affected)

Types of changes

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

Checklist:

[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] I've signed off with an email address that matches the commit author.

Commits were signed-off and changes were applied. Leaving one conversation open as to confirm reviewer's approval.

Thanks, @Hentouane!
LGTM
@astromechza, another pair of eyes for this review please? Thanks1


Propagate trace context from SQS events

What does this PR do?

When this lambda function is a consumer for a SQS queue, collect the trace context passed back from the extension and apply it.
Motivation

Traces with a go SQS consumer were broken.
Testing Guidelines

Sample trace using these updates

Note that any child span created inside the lambda function currently will not appear in the trace. This is because the extension isn't reading sampling priority and therefore the tracer defaults to priority 0 (throw it away). See https://datadoghq.atlassian.net/browse/SVLS-3537.
Additional Notes

For some reason I am not seeing the aws.lambda span created for my sqs consumer. This should be created in the extension when universal instrumentation is turned on. I haven't been able to get to the bottom of this. However, I have been able to show that any child spans created in the SQS comsumer lambda will have the proper trace ID and show up properly in the trace.
Types of changes

[ ] Bug fix
[ ] New feature
[ ] Breaking change
[ ] Misc (docs, refactoring, dependency upgrade, etc.)

Checklist

[ ] This PR's description is comprehensive
[ ] This PR contains breaking changes that are documented in the description
[ ] This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
[ ] This PR impacts documentation, and it has been updated (or a ticket has been logged)
[ ] This PR's changes are covered by the automated tests
[ ] This PR collects user input/sensitive content into Datadog

Codecov Report

Merging #142 (3436460) into main (ba44882) will decrease coverage by 0.58%.
The diff coverage is 57.69%.

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

@@            Coverage Diff             @@
##             main     #142      +/-   ##
==========================================
- Coverage   83.13%   82.55%   -0.58%
==========================================
  Files          13       13
  Lines         848      860      +12
==========================================
+ Hits          705      710       +5
- Misses        114      118       +4
- Partials       29       32       +3

Files Changed
Coverage Δ

internal/trace/listener.go
54.79% <50.00%> (+0.62%)
:arrow_up:

internal/trace/context.go
73.57% <52.94%> (-3.53%)
:arrow_down:

internal/extension/extension.go
80.76% <100.00%> (+0.50%)
:arrow_up:

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

It seems your description sc shows the aws.lambda consumer span. Assuming the description is just out of date? if so np, just want to make sure I understand

For some reason I am not seeing the aws.lambda span created for my sqs consumer.

It seems your description sc shows the aws.lambda consumer span. Assuming the description is just out of date? if so np, just want to make sure I understand

For some reason I am not seeing the aws.lambda span created for my sqs consumer.

Yes, great catch! I did get to the bottom of why I wasn't seeing the aws.lambda consumer span. It's due to sampling priority getting set to 0. I took that screenshot after putting in a hardcoded hacky fix.

np doing a full review now :)


[REQ] Quick toggle using R2 for joypad to mouse?

Is this possible?

Are you not enough, using Keyboard's arrow keys and Joypad's mouse?

For game Alaskan Malamute it is necessary to swap between mouse and keyboard quite often.
Also in T&E New 3D Golf Simulation series.

On Retroarch, operation with Joypad must controll guest Keyboard/Mouse/Joypad.
I think toggling 3 mode with R2 button press.
How about you?

My idea was to work as opposite (mouse/keyboard) whilst R2 is held down.
But, toggle is fine also!

And I think "now mode" indicate on screen necessary.
Then, it is difficult. And it'll affects other games.

OK, I will leave it up to you.

Sorry, now I don't have good idea.
If I find good method, report to you.
Thanks.

Yes, please.
I'll keep thinking too


lrz-fix_addcdiv and addcmul again

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation and Context
fix addcmul
fix addcmulInp
fix addcdiv
fix addcdicInp
Description
2 file change
fix addcmul
fix addcmulInp
fix addcdiv
fix addcdicInp
fix again
Use cases (Optional)

BC-breaking (Optional)

Checklist
Before PR:

[ ] I have read and followed the workflow indicated in the Contributors.md to create this PR.
[ ] Pre-commit or linting tools indicated in Contributors.md are used to fix the potential lint issues.
[ ] Bug fixes are covered by unit tests, the case that causes the bug should be added in the unit tests.
[ ] New functionalities are covered by complete unit tests. If not, please add more unit test to ensure the correctness.
[ ] The documentation has been modified accordingly, including docstring or example tutorials.

After PR:

[ ] CLA has been signed and all committers have signed the CLA in this PR.

already fix addcdiv and addcmul


NoTransparency should ignore invisible objects

I'll try and find a sample PDF for this. I don't have one to hand.

Cheers, I'll leave this ticket open so I don't forget about it


Added an apply_table function and test

This is in response to this gitter message. It's a pretty simple implementation of an Apply method. It basically converts to a df, applies the function, and then converts back.

yay! thanks.


Update concept-cloud-security-posture-management.md

#sign-off

@tarosler this was opened on the public repo i will close this here and make the change myself.

#please-close


Instance::ensure() doesn't check type if 'class' field is presented in $reference param

What steps will reproduce the problem?
Make the code like that:
$instance = \yii\di\Instance::ensure(
    [
        'class' => \foo\Bar::className(),
        'param1' => 'value 1',
    ],
    \yii\db\Connection::className(),
);

var_dump($instance instanceof \yii\db\Connection);

What is the expected result?
Thrown InvalidConfigException
What do you get instead?
The "false" string
Additional info

Q
A

Yii version
2.0.11

PHP version
7.1

Operating system
Fedora release 25 (Twenty Five)

Here's a test:
public function testExceptionInvalidDataTypeInArray()
    {
        $this->setExpectedException('yii\base\InvalidConfigException', 'Invalid data type: yii\db\Connection. yii\base\Widget is expected.');
        Instance::ensure([
            'class' => Connection::className(),
        ], 'yii\base\Widget');
    }


VSCode abnormal while saving

Version: 1.43.0
Commit: 78a4c91400152c0f27ba4d363eb56d2835f9903a
Date: 2020-03-09T19:34:44.548Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 18.7.0
Steps to Reproduce:

After do update, 5 min vscode close unexpected
Then i running again (look like normal)
Then open existing file (in my case golang file)
Saving with CTRL+S or via menu

here video https://youtu.be/Z3e6PWXLS_c

I have a similar issue saving java files. Where the interface hangs trying to get Code Actions. I had to revert to 1.42.1.

I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line (NOT the integrated terminal in Code), execute: code --disable-extensions and try your steps again to see if it reproduces. If you see it is an issue with the extension, please file it against the extension repository itself.

@bpasero i've been check it, and saving going well

@luthfikw can you pin point which extension is causing this?

@luthfikw Can you try to disable code actions running during save via editor.codeActionsOnSave. The go-extension is know for being super slow when it participates in saves and that likely causes this.

@luthfikw Can you try to disable code actions running during save via editor.codeActionsOnSave. The go-extension is know for being super slow when it participates in saves and that likely causes this.

still happening, this my setting:
    "[go]": {
        "editor.snippetSuggestions": "none",
        "editor.formatOnSave": true,
        "editor.codeActionsOnSave": {
            "source.organizeImports": false
        }
    },

@luthfikw can you pin point which extension is causing this?

i can't identify that, but i can lists my enable extensions
this the list:

alefragnani.bookmarks
coenraads.bracket-pair-colorizer
mihelcic.colored-regions
mikestead.dotenv
editorconfig.editorconfig
ms-vscode.go
aleksandra.go-group-imports
pkief.material-icon-theme
arcticicestudio.nord-visual-studio-code
zhuangtongfa.material-theme
fabiospampinato.vscode-projects-plus
foxundermoon.shell-format
gearintellix.vscode-sqml
gruntfuggly.todo-tree
shardulm94.trailing-spaces
zxh404.vscode-proto3
redhat.vscode-yaml

Than also disable format on save. And read the progress message that will appear on the lower right of your screen. It names the operation (formatting, code actions) and the extension that's performing it

Than also disable format on save. And read the progress message that will appear on the lower right of your screen. It names the operation (formatting, code actions) and the extension that's performing it

on old version, it appear
not to latest version

i've been found extension that trouble maker, that aleksandra.go-group-imports
but on vscode self, i think having bug too
see this: https://youtu.be/RFsqW0aZ2lk


Basic benchmark suite

We need basic benchmark suite for Splash, something that renders a few typical web pages, hosted locally (to avoid network latencies affecting the results). Just a few (5-10) diverse enough websites should be enough to get started.
The main goal for this benchmark suite is to compare Splash performance reliable on different server configurations/deployments, but we could also use it for comparing performance with other tools (see #99).

@immerrr could you work on this soon?

FTR, this is the benchmark script I used when hacking on splash: https://gist.github.com/immerrr/a1419c4175d9c59d1cb6

yup, will do

Could you try the code from #185 and see if it is usable?


Host is not ejected due to race condition in the outlier detection

Title: Host is not ejected due to race condition in the outlier detection
Description:
We use outlier detection with consecutive_local_origin_failure to eject hosts.
When a host is down for a longer period of time(>10 minutes), we occasionally see that envoy stops ejecting the troubled host after the host has been ejected and unejected several times, and, keeps sending requests to the host afterwards.
I instrumented envoy with addtional debug logging, and below is what I found is causing the issue.
When envoy sees a connection timeout to an upstream host, envoy checks the consecutive_local_origin_failure_ counter and ejects the host as below.

[worker thread] DetectorHostMonitorImpl::localOriginFailure: The function is called when envoy detects a local origin error, it increments consecutive_local_origin_failure_ counter , and calls onConsecutiveLocalOriginFailure method on detector which notifies the main thread to eject the host.

void DetectorHostMonitorImpl::localOriginFailure() {
 std::shared_ptr<DetectorImpl> detector = detector_.lock();
 if (!detector) {
   // It's possible for the cluster/detector to go away while we still have a host in use.
   return;
 }
 local_origin_sr_monitor_.incTotalReqCounter();
 if (++consecutive_local_origin_failure_ ==
     detector->runtime().snapshot().getInteger(
         ConsecutiveLocalOriginFailureRuntime,
         detector->config().consecutiveLocalOriginFailure())) {
   detector->onConsecutiveLocalOriginFailure(host_.lock());
 }
}

[main thread] DetectorImpl::onConsecutiveErrorWorker: checks healthFlag to see if the host is already flagged as FAILED_OUTLIER_CHECK. If not, proceed to the next steps
[main thread] DetectorImpl::onConsecutiveErrorWorker: ejectHost method is called in to eject host. the method will set the healthFlag of the host to be FAILED_OUTLIER_CHECK
[main thread] DetectorImpl::onConsecutiveErrorWorker: resetConsecutiveLocalOriginFailure is called to reset consecutive_local_origin_failure_ counter

void DetectorImpl::onConsecutiveErrorWorker(HostSharedPtr host,
                                           envoy::data::cluster::v3::OutlierEjectionType type) {
 // Ejections come in cross thread. There is a chance that the host has already been removed from
 // the set. If so, just ignore it.
 if (host_monitors_.count(host) == 0) {
   return;
 }
 if (host->healthFlagGet(Host::HealthFlag::FAILED_OUTLIER_CHECK)) {
   return;
 }

 // We also reset the appropriate counter here to allow the monitor to detect a bout of consecutive
 // error responses even if the monitor is not charged with an interleaved non-error code.
 updateDetectedEjectionStats(type);
 ejectHost(host, type);

 // reset counters
 switch (type) {
 case envoy::data::cluster::v3::CONSECUTIVE_5XX:
   stats_.ejections_consecutive_5xx_.inc(); // Deprecated
   host_monitors_[host]->resetConsecutive5xx();
   break;
 case envoy::data::cluster::v3::CONSECUTIVE_GATEWAY_FAILURE:
   host_monitors_[host]->resetConsecutiveGatewayFailure();
   break;
 case envoy::data::cluster::v3::CONSECUTIVE_LOCAL_ORIGIN_FAILURE:
   host_monitors_[host]->resetConsecutiveLocalOriginFailure();
   break;
 default:
   // Checked by schema.
   NOT_REACHED_GCOVR_EXCL_LINE;
 }
}

If there is another pending request to upstream that times out, it follows step 1. and 2. but does not proceed to step 3 and 4 since the host has been flagged as FAILED_OUTLIER_CHECK.
Since step 4 is skipped. consecutive_local_origin_failure_ counter is not reset to 0, and thus, it never becomes lower than the threshold value.
Repro steps:
Run the envoy with the configuration below, and have a http server that listens to the one of the endpoints addresses, and run multiple clients that send requests simultaneously.
Here's python code I used to reproduce the issue
import requests
import time
from concurrent.futures import ThreadPoolExecutor

session = requests.Session()
def send_queries(url):
    fast_count = 0
    consecutive_slow_response = 0

    for idx in range(10000):
        start_time = time.time()
        r = session.get(url)
        r.raise_for_status()
        duration = time.time() - start_time

        if duration > 0.5:
            print("[{}] Duration {:.2f} ms, Downstream: {}, Client Addr: {}, Instance: {}. After {} fast responses".format(
                idx,
                duration * 1000,
                r.headers['x-downstream'],
                r.headers['X-remote'],
                r.headers['X-instance'],
                fast_count
            ))
            if fast_count == 0:
                consecutive_slow_response += 1
                if consecutive_slow_response > 2:
                    print("consecutive slow responses, stopping")
                    break
            else:
                consecutive_slow_response = 0
            fast_count = 0
        else:
            fast_count += 1
        time.sleep(0.1)

NUM_THREADS=2
with ThreadPoolExecutor(max_workers=NUM_THREADS) as executor:
    works = []
    for _ in range(NUM_THREADS):
        works.append(executor.submit(send_queries, 'http://<IP_ADDRESS>:8080'))

    for w in works:
        w.result()

I was able to reproduce the issue with envoy version 1.19.1 and 1.20.0
Config:
node:
  cluster: test-cluster
  id: test-id

admin:
  address:
    socket_address: { address: <IP_ADDRESS>, port_value: 9901 }

cluster_manager:
  outlier_detection:
    event_log_path: "./eject-event.log"

dynamic_resources:
  lds_config:
    path: "./envoy-lds.yaml"
  cds_config:
    path: "./envoy-cds.yaml"

resources:
- "@type": type.googleapis.com/envoy.config.cluster.v3.Cluster
  name: dynamic_service
  connect_timeout: 1.0s
  type: STRICT_DNS
  lb_policy: ROUND_ROBIN
  outlier_detection:
    # consecutive_5xx: 1
    consecutive_local_origin_failure: 1
    interval: 1s
    base_ejection_time: 2s
    max_ejection_time: 3s
    split_external_local_origin_errors: true

  load_assignment:
    cluster_name: dynamic_service
    endpoints:
    - lb_endpoints:
      - endpoint:
          address:
            socket_address:
              address: <IP_ADDRESS>
              port_value: 8081
      - endpoint:
          address:
            socket_address:
              address: <IP_ADDRESS>
              port_value: 8082

resources:
- "@type": type.googleapis.com/envoy.config.listener.v3.Listener
  name: listener_0
  address:
    socket_address:
      address: <IP_ADDRESS>
      port_value: 8080
  filter_chains:
  - filters:
    - name: envoy.http_connection_manager
      typed_config:
        "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
        stat_prefix: ingress_http_3
        http_filters:
        - name: envoy.router
        route_config:
          name: local_route
          virtual_hosts:
          - name: local_service
            domains: ["*"]
            routes:
            - match: { prefix: "/" }
              route: { cluster: dynamic_service }
            # https://www.envoyproxy.io/docs/envoy/latest/api-v3/config \
            # /route/v3/route_components.proto#config-route-v3-retrypolicy
            retry_policy:
              retry_on: "connect-failure,refused-stream,gateway-error"
              num_retries: 1
        http_filters:
        - name: envoy.filters.http.router

This can be fixed by resetting the counter inside  DetectorImpl::checkHostForUneject. I can make a PR for the fix, but would like to hear if that is the right way to fix this issue.

@cpakulski would you mind looking at it?

@rojkov. Sure - I will take care of this.

@jparklab I am trying to repro this, but since Envoy and backend webservers are running on the same host in my setup I never experience any timeout. I have a full control of webservers, so I can easily add a timeout before replying. If I add a random delay to a webserver, say between 0-2 seconds, do you think that the described scenario should occur?

You can simply have a cluster with two endpoints where one of the endpoints point to an invalid ip address/port, and the other points to your webserver.

@jparklab Yes, you are right. Your proposed fix is fine. consecutive5xx and gateway counters are already reset in https://github.com/envoyproxy/envoy/blob/release/v1.20/source/common/upstream/outlier_detection_impl.cc#L358-L359, so you can also call resetConsecutiveLocalOriginFailure().

@cpakulski Thanks for checking. I created a PR with the fix: #19205

I will try to construct a unit test to simulate timeouts and see if it triggers the bug (as suggested in #19205 comment).

ping.


Reversing Json Object

Hi guys,
lhs object returned below is always reversed(upside down). Is there a simple way to reverse it?
observableDiff(lhs, rhs, function (d) {
applyChange(lhs, rhs, d);
});
return lhs

Please provide an illustration in code that I can use in an example/issue-xxx.js... see other examples here.


Typescript reference is formatted to comment

When I do this
/// <reference path="circleMath.ts"/>
/// <reference path="RectangleMath.ts" />

It is automatically formatted to
/// <reference path="circleMath.ts"/> / <reference path="RectangleMath.ts" />

and in general every comment. I am using TSLint with Prettier. Any idea?
Thanks!

Does this reproduce with all extensions disabled?

All linters at least, yes.

Yes, try disabling Prettier and tslint too to see which one causes this

I'm happy to say I am a true idiot, I didn't disable "taichi.react-beautify" which I totally forgot I had installed.
However, I had to find an error in the console to be able to point to that. Is there a way to track what extensions are doing what? That would be handy!

Ok, closing as caused by extension. Please try filing this issue against that extension
I think helping users debug what extension contributes what falls under #53146


[release-1.11] Fix 1p jwt on k8s 1.21+ (again)

This is an automated cherry-pick of #34294

@howardjohn cla

@howardjohn ping

@googlebot I consent.


Migrate Thirdweb to V5

closes #773
What changed? Why?
This PR migrates the codebase to work with thirdweb on V5.
How has it been tested?

[ ] Locally
[ ] Vercel Preview Branch
[ ] Unit test
[ ] Functional test

TODOs:
[ ] Change E2E tests to work with the new auth

nice work, man


Spike and Segments datashader operation not renaming dimensions correctly

The following example attempts to datashade Spikes elements, showing one way that works as expected and two that don't:
# In[1]
import holoviews as hv
import numpy as np
import pandas as pd
from holoviews.operation.datashader import rasterize
hv.extension('bokeh')

# In[2]
arr = np.random.rand(10) * 10
df = pd.DataFrame({'xpos':arr})
rasterize(hv.Spikes(arr), aggregator='count')  # Works

# In[3]
rasterize(hv.Spikes(df.xpos), aggregator='count') # Doesn't work

# In[4]
rasterize(hv.Spikes(df, ['xpos']), aggregator='count') # Also doesn't work

The error message in both cases:

```
WARNING:param.dynamic_operation: Callable raised "DataError("xarray Dataset must define coordinates for all defined kdims, [Dimension('xpos')] coordinates not found.\n\nXArrayInterface expects gridded data, for more information on supported datatypes see http://holoviews.org/user_guide/Gridded_Datasets.html")". Invoked as dynamic_operation(height=400, scale=1.0, width=400, x_range=None, y_range=None)
```

This is somewhat surprising as a numpy array works, but a Series (which is array-like) does not.

Nothing to do with Spikes or rasterization, it's just that none of the data interfaces accept a Series.

This also causes issues when converting datetimes.

This has been fixed.


Update gtfs-realtime-bindings

Fixes #2546

To be honest, I just updated the dependency and checked if the unit tests are passing. The phasing out of the old protobuf dependency is the main reason for this PR.

@michaz

Unless there's a clear and present danger, I think I'd prefer to change this only as needed.
But if someone else really really wants to merge, I don't mind.


Fix for issue #771: Fixed incorrect call to VersionControlServer.QueryMerges().

Fix for #771. I added an extra variable (searchTo) because it makes intent much clearer.
Fixed incorrect call to VersionControlServer.QueryMerges(). Now searches for merges from the beginning of time instead of from the current version. See MSDN API documents for more details: https://msdn.microsoft.com/en-us/library/bb138969.aspx

@ryanbnl - thanks for the fix. There are some CI test failures. They look unrelated to me. :/

It looks like an intermittent fault, is there any way to force a new CI build?

I think I kicked off a new build yesterday, and it failed too. (build 1, build 2) I see that it's green now.
¯\_(ツ)_/¯


[Microservice] Network ACL Manager

This PR contains the following features:

Network ACL create/update/delete/query interfaces
Network ACL rule create/delete/query interfaces
Network ACL batch interfaces
Network ACL rule batch interfaces
Interact with vpc manager to verify that if vpc id is validate
Interact with subnet manager to verify that if subnet id is validate

Codecov Report

Merging #251 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #251   +/-   ##
=========================================
  Coverage     37.55%   37.55%
  Complexity      550      550
=========================================
  Files           241      241
  Lines          5680     5680
  Branches        575      575
=========================================
  Hits           2133     2133
  Misses         3292     3292
  Partials        255      255

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 80110a7...d1be9b8. Read the comment docs.

@chenpiaoping Let me start getting back this PR. Do you expect that other services have dependency on this payload? Likely not, just want to confirm.

@chenpiaoping Let me start getting back this PR. Do you expect that other services have dependency on this payload? Likely not, just want to confirm.

Ping.. Let us get some traction on this PR @chenpiaoping

@chenpiaoping I will merge this PR as we will need some time to stabilize the codes. Could you look into those pending comments, mostly minor? Thanks.


Retaining source addresses after forwarding SMTP connections to mox running behind NAT

Hey, first of all thank you for this project.
I have a use case where

I'd like to run an email server behind NAT (the reasons for that aren't interesting, let's call the machine it'd run on Machine A). It's all IPv4.
I'd like the server to be publicly accessible via forwarding connections from a machine with a public IP address (Machine B).
The email server running on Machine A needs to use Machine B to send email to the outside world (the public IP address of Machine A's connection wouldn't be accepted by third-party email servers).
I'd like Machine B to forward the source address and port information to the email server running on Machine A so that my logs are useful, I can make anti-spam decisions based on that etc.

IPv6 isn't the answer in my case, sadly.
Points 1 and 2 are easy, just set up a reverse TCP proxy.
Point 3 is achievable since the SOCKS proxy support has been added to mox[1].
What's left is point 4. I've been wondering – would something like the PROXY protocol[2] support be considered a fitting addition to mox? It's lightweight, protocol-independent and has a reasonably broad support (nginx, which I use, speaks it).
As a bonus, if this actually happened, when running in Docker mox wouldn't require the host-mode networking[3] to see the IP addresses anymore.
[1] https://github.com/mjl-/mox/issues/36
[2] https://github.com/haproxy/haproxy/blob/3a0b44b122067676ad13d8348a17e6c5bd279901/doc/proxy-protocol.txt
[3] https://github.com/mjl-/mox/issues/24

Hi @jstasiak, this seems like a reasonable approach indeed.
We could implement a ProxyListener that implements the net.Listener interface. It would wrap a another listener (created with net.Listen, for tcp connections). Its Accept() method would return a type that implements net.Conn that returns the original client address for RemoteAddr(). That would make it transparent to most of the mox code. I see there is one occurrence that looks for a connection being a net.TCPConn for setting keepalives. That could need a small change.
We could add a field TrustedProxyIPs to a config.Listener, with a list of subnets (<IP_ADDRESS>/0 or <IP_ADDRESS>/32, etc). Any connection coming in from a TrustedProxyIP will get the PROXY protocol treatment, others wouldn't. All code in mox where a new listener is created would have to check if TrustedProxyIPs is set and wrap the listener in a ProxyListener.
The PROXY protocol seems simple enough to implement in mox (not adding a new dependency). Probably best to implement both v1 and v2. Must be careful not to Read() data beyond the proxy header. For v2 that's easy, for v1 it's probably best to inefficiently do a bunch of small reads until end of line (the spec has example code that peeks at available data without consuming, but let's not go there with Go).
Would this really help not needing host-mode networking with docker? Does docker implement the PROXY protocol? I think I've looked at support for a PROXY-like protocol in the past, but couldn't find docker implementing it.
Are you interested in working on this? If so I can give hints for development.

This is almost exactly how I'd envision the implementation and the behavior so that's good to hear. My only concern is that maybe the protocol is not so simple to implement to warrant skipping a dependency here – judging by https://github.com/pires/go-proxyproto code – but that's just my intuition so far.
What I forgot to mention in my Docker remark is that in that non-host-mode scenario where proxy protocol was used there would have to be a proxy-protocol-speaking reverse proxy in front of it – I don't imagine Docker itself could handle it. So not quite out of the box solution there.
Yes, I'm not sure how soon exactly but I'd like to take a stab at it – any and all tips are appreciated.

Yes, I'm not sure how soon exactly but I'd like to take a stab at it – any and all tips are appreciated.

Great!
I looked at the listening code again just now. I think it's mostly the code that calls mox.Listen() needs changes. That's the smtp, imap and http servers. See https://github.com/search?q=repo%3Amjl-%2Fmox mox.Listen&type=code. mox.Listen abstracts away getting a listener file descriptor either by calling net.Listen or taking a listener fd that was passed by its parent privileged process.
Another relevant topic is the TLS listeners. They are created by tls.NewListener(plainListener, ...). They occur at the same call sites as the mox.Listen() calls from above that need changing.
So far, initializing a listener works like this: mox.Listen() to get a plain listener. Then wrap the listener in tls.NewListener() if TLS should be enabled.
I expect the new order to be: mox.Listen() for plain listener, optionally wrap that in a PROXY listener, then optionally wrap that listener in the TLS listener.
Perhaps it makes sense to either modify mox.Listen or to make a new listen-helper function that handles the wrapping into a PROXY listener.
mox.Listen is at https://github.com/mjl-/mox/blob/aead73883601ecb259e7a27d834bcbaf8e4af07a/mox-/lifecycle.go#L80.
There are a few direct calls to net.Listen() in mox, but those are for unix domain sockets or tests, so I don't expect they need to be changed.
This check for *net.TCPConn may need changing: https://github.com/mjl-/mox/blob/aead73883601ecb259e7a27d834bcbaf8e4af07a/imapserver/server.go#L675
And the few places in smtpserver that expect *net.TCPAddr may need attention:  https://github.com/search?q=repo%3Amjl-%2Fmox+net.TCP&type=code
As for using a library: If it really fits it's fine to use it, but often there is some issue (e.g. go-proxyproto seems to inject a bufio.Reader in every connection, not great). Keep in mind we also need testing code that dials, so we need a PROXY "client" as well.
We can also discuss by email/irc/matrix/slack.


Is it possible to train MANGO without using character-level annotation?

Is it possible to train MANGO without using character-level annotation? Just use the word-level annotation.

You can finetune the model (using the pretrained model) on any dataset without using character-level annotation.
If the dataset is relatively simple, the model can also be trained from scratch only using word-level annoation.

Thank you for your reply!
Can you provide the annotations files of SynthText and SynthCurve:
'/path/to/datalist/synthtext_80w.json',
'/path/to/datalist/train_syntext_word_eng.json',
'/path/to/datalist/train_emcs_imgs.json',

@qiaoliang6

Thank you for your reply!
Can you provide the annotations files of SynthText and SynthCurve: '/path/to/datalist/synthtext_80w.json', '/path/to/datalist/train_syntext_word_eng.json', '/path/to/datalist/train_emcs_imgs.json',

We have just uploaded all these formated datalist in HikOne. See demo/text_spotting/datalist/readme.md

Thank you!


gigasecond:  use full time test cases

cases_test.go regenerated with new cases from x-common.
flexibility added in gigasecond_test.go to parse full times.
testVersion bumped to 2 to reflect new test cases.

This was a small change to the test program just to handle the new data.  The example needed no changes other than bumping testVersion.  Existing solutions should similarly continue to work.

Excellent, thank you!


hygieia/api dockerfile outdated

the document site instruction seems like doesn't match the most recent code in master, application.properties file is src/main/resources/ but dockerfile seems like is completely outdated, can someone update the dockerfile or give guide to update the dockerfile ?

Hi @YeWang555, I see you closed this issue as completed, was the Dockerfile updated or did your company decide to go in another direction?


DES support?

I just needed it myself, and did it in:
https://github.com/indutny/des.js
Perhaps it could be used in crypto-browserify too?
Currently supported ciphers:

des-ecb
des-cbc
des-ede3-ecb
des-ede3-cbc

@indutny,  is it available in node?

Mmm.. of course, all of them are available via crypto.createCipher/crypto.createCipheriv (and deciphers too)

no reason not to include it, though looking at the library we'd need to make them sub classes of streams.  You probably don't want that in your library because it will slow things down, but we could create a wrapper library to pull in DES.

Cool, thank you!

ok step 1 i've extracted the cipher-base out into it's own module, I think next I need:

to extract EVP_BytesToKey into it's own module
make a des-browserify package that provides createCipherIV stuff
make a cipher package that consumes both des and aes and move the stuff for createCipher there

That sounds like a good roadmap @calvinmetcalf :+1:

Hooray!

#137

Added


History summary can grow longer than it should

The new historySummary field in FFTM 1.2.1 can grow longer than it should when subStatus changes regularly.

I think this can be closed as history is stored differently now


Feat: Analytics and Snapshota

Use Firestore to store game snapshots
Requirements

[ ] Create a Firestore collection for game logs
[ ] Store snapshots of a Room at each turn, countdown, and room join
[ ] On room termination, upload the snapshot array to Firestore

POG AWS


TF Lite in Google Play services has stable ABI version 1.11.0 which is less than the required version 1.13.0

We are using   mobile_scanner: ^3.5.1 version in our flutter project, on android device when ever camera opens below warning keeps on coming repeatedly
W/native  (30072): W0000 00:00:1698456375.622782   32103 abi_method_util.h:33] not supported: TfLiteInterpreterGetTensor: TF Lite in Google Play services has stable ABI version 1.11.0 which is less than the required version 1.13.0.
environment:
sdk: '>=2.12.0 <3.0.0'
Where do we need to make changes to upgrade to required version 1.13.0

As far as I know, Tensor Flow Lite is a dependency of MLKit. I think we have to bump the version of MLKit that is used to get rid of this warning. I'll look into this.

Thanks for update, we will be waiting for this change to be done in new version.

the issue is still pending!

@dhirajmishra98 As I mentioned in https://github.com/juliansteenbakker/mobile_scanner/issues/836#issuecomment-1787248290 the MLKit version has been updated to the latest available version in mobile_scanner 3.5.2.
If this issue is still occurring, we cannot do anything at the moment since version 18.3.0 is the latest version.
See https://developers.google.com/ml-kit/release-notes#latest_versions

Could @rachitjoshi9 or @dhirajmishra98 reply to https://github.com/tensorflow/tensorflow/issues/62331 with the following information:

Device info of the Android device (adb shell getprop ro.build.fingerprint)
Google Play Services version (Settings > Apps > Google Play Services > App details)

Apparently support for version 1.13.0 is still in preview. Is anyone using preview/beta versions here?

This issue still happen. I used mobile_scanner: ^3.5.2. After that first time opening the camera still get
TF Lite in Google Play services has stable ABI version 1.11.0 which is less than the required version 1.13.0

and can't use. Only work in second time after enter again to this screen.

I use simple_barcode_scanner and got a lot of outputs in console

TF Lite in Google Play services has stable ABI version 1.11.0 which is less than the required version 1.13.0.

TF Lite on Google Play services has a stable ABI version of 1.13.0, which is less than the required version 1.11.0. Does the problem still persist

yes problem still persists...

is there a work around it?

For beginners, I have used the bundled version,
there is no exception about the TF Lite in Google Play services has stable ABI version 1.11.0 which is less than the required version 1.13.0
just remove "dev.steenbakker.mobile_scanner.useUnbundled=true"

Is there any way to solve it?

I'm on the "TF Lite in Play services" team at Google, and I just came across this issue.
(For faster support on similar issues in future, file an issue in the tensorflow github issues list, and tag it with the appropriate tags to indicate that it is related to TF Lite in Play services.)
I believe this issue should be fixed already, by an updated version of TF Lite in Play services, with no need for code changes or even recompilation for apps that were previously affected. If the issue is still occuring, please let us know.

Thanks for the update

I'm on the "TF Lite in Play services" team at Google, and I just came across this issue. (For faster support on similar issues in future, file an issue in the tensorflow github issues list, and tag it with the appropriate tags to indicate that it is related to TF Lite in Play services.)
I believe this issue should be fixed already, by an updated version of TF Lite in Play services, with no need for code changes or even recompilation for apps that were previously affected. If the issue is still occuring, please let us know.

Thanks for the update. I'll keep that in mind for future similar reports here.


v-bind on "component" component not passing "is" prop correctly

Vue version
3.2.37
Link to minimal reproduction
https://sfc.vuejs.org/#eNqVkt1ugzAMhV/Fyy62SQ1o6x2ilfoekSZ+QklXnCgJrBXi3edAR7t1QtodNj6ffez0bGdM1LWSJSx1hVXGg5O+NVuBqjHaeujBygoGqKxu4IlKnwQKLDQ6D9p4B5tQ8NwrlwhWvwo2vAhM4wlGGAq8bMwx85IigLTQBEaJHjqeKyw3ggWOYFvBpoxgaTxX/S1KlLvoIkXSBRRkWMJ3SLL/w7eHlrwuIx44h1FVv1FLV+v2WEIuQXfSWlVKhPx8oQPnV82uKLQtFe7Ba6i9Ny6J427NG7W3mVcaw3EOLtJ2H+dWZh9Uyos6w7108cSLat8cH9/X/MTdGX12mhtcfV1Hu1/UuD86epigVFUlbVDM2tWym5+bSOP51mzFphfEm8xEB6eR3lgf5qKW4w/qm8CYCTnyGWIa87IFVxU35ukrsi161chIuobnVn86aQks2OqGEVOSpuRkoiQndon5q/SOG7CDwIENX+icF7I=
Steps to reproduce

Create an object containing the key "is" with the value of the name of another component (ex. {is:"h1"})
In the template, add a component tag with v-bind set to the previously created object (ex. <component v-bind="opts">this should render as an "h1"</component>)

What is expected?
The component tag should render as the tag defined in the object passed through v-bind
What is actually happening?
The component tag still renders as a component tag, though other properties passed through v-bind are applied correctly
System Info
npx: installed 1 in 1.386s

  System:
    OS: Linux 5.10 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
    Memory: 170.50 MB / 5.79 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 14.19.3 - ~/.nvm/versions/node/v14.19.3/bin/node
    Yarn: 1.22.18 - ~/.nvm/versions/node/v14.19.3/bin/yarn
    npm: 6.14.17 - ~/.nvm/versions/node/v14.19.3/bin/npm
  npmPackages:
    vue: ^3.0.0 => 3.2.37

Any additional comments?
As seen in the minimal reproduction link, if the "is" property is applied using :is or v-bind:is, the tag is replaced correctly. Also notably, if both a v-bind:is and v-bind object with the "is" key is provided, the v-bind:is property is always used, rather than being overwritten if provided first (according to https://v3-migration.vuejs.org/breaking-changes/v-bind.html#_3-x-syntax)

  <component v-bind:is="opts.is">just "v-bind:is"</component>
  <component is="h2" v-bind="opts">"is" set to different component, should be overriden by v-bind</component>

The first component tag is parsed as _createBlock(_resolveDynamicComponent($setup.opts.is).
The second component tag is parsed as _createBlock(_resolveDynamicComponent("h2").
When opts.is changed, the second component tag is still _createBlock(_resolveDynamicComponent("h2"). So that's why 'opts.is' doesn't work.

is is a special attribute that must be explicitly declared to work because it is specially handled during the compilation phase.


private link scope default resource type -JEDI

We expose a new default resource type for Azure Monitor to solve the case for private link on global endpoints. This resource will store reference to Azure Monitor resource required for private link access.
This is an urgent JEDI ask.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

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


Problem

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Additional context

Please fill the issue template and describe your problem and then re-open the issue.


style issue: operators list vs type operator lists

I find while implementing the compiler having to switch between the operators on int and bit and arbitrary-precision integers sections to see which type is valid for each operator. I also noticed there are many of the same verbage for each type.
A big example is the slicing operator which only differs by the last setence which says the type of the operator is always unsigned.
The C language is the opposite of what the P4 specifications is. That has sections for similar expressions and then list constraints and semantics of each operator. Obvious this is easier for compiler development. You still can help the current sections but much shorter and provide links to the new sections which then have only one copy of almost the same thing.
The reason why I filed this is to record this style issue I found. Plus someone might also run into this issue.
Also Concatenation and shifts seems to be handled this way but then still duplicate verbage in both signed and unsigned type sections.

In the interest of tidying up the set of active issues on the P4 specification repository, I'm marking this as "stalled" and closing it. Of course, we can always re-open it in the future if there is interest in resurrecting it.


Rijksmuseum

Provider API Endpoint / Documentation
https://data.rijksmuseum.nl/object-metadata/api/
Provider description
The Rijksmuseum is the national museum of the Netherlands. It tells the story of 800 years of Dutch history, from 1200 to now.
Licenses Provided
CC0 and others
Provider API Technical info
Openverse has the Rijksmuseum media that was collected through CommonCrawl. We need to create a provider api script.
Checklist to complete before beginning development

[X] Verify there is a way to retrieve the entire relevant portion of the provider's collection in a systematic way via their API.
[X] Verify the API provides license info (license type and version; license URL provides both, and is preferred)
[X] Verify the API provides stable direct links to individual works.
[X] Verify the API provides a stable landing page URL to individual works.
[X] Note other info the API provides, such as thumbnails, dimensions, attribution info (required if non-CC0 licenses will be kept), title, description, other meta data, tags, etc.
[X] Attach example responses to API queries that have the relevant info.

Implementation

[ ] 🙋 I would be interested in implementing this feature.

Duplicate of #1296.


add zstd to self-hosted runner cloud-init

We need zstd in our self-hosted runners for GitHub actions/cache to work correctly across runners. Thanks to @giggsoff for pointing out the right location for this.

I have no idea why this CI failed. The change doesn't even touch anything triggered by CI 🤷♂

I have no idea why this CI failed. The change doesn't even touch anything triggered by CI 🤷♂

I can see connection reset to docker hub: https://github.com/lf-edge/eve/actions/runs/3121824941/jobs/5063382682#step:7:131


[BLOCKER] [UICollectionBundle] .deleteOne doesn't work after a specific fetch

Describe the bug
When opening my app, I can delete items without a problem.
There's one action though, that, when performed, prevents any further collection.deleteOne to work, and throws the following exception :
apollo client Payload is not serializable: cyclic object value

In my case, the action that get things messy is to simply open a open that fetches a document to display it (actually that document was already in the apollo-cache, I just fetch some additional fields). here's the only query/Action performed between a working working deletion and a bugged one, that starts the problem  :
Query :

Result :

After that, no more .deleteOne can be performed on any collection without throwing this :
Error: Network request failed. Payload is not serializable: cyclic object value
    ApolloError index.js:29
    error QueryManager.js:137
    notifySubscription module.js:137
    onNotify module.js:176
    error module.js:229
    makeCallback asyncMap.js:32
    notifySubscription module.js:137
    onNotify module.js:176
    error module.js:229
    iterateObserversSafely iteration.js:4
    iterateObserversSafely iteration.js:4
    error Concast.js:36
    notifySubscription Observable.js:140
    onNotify Observable.js:179
    error Observable.js:240
    promise callback*setContext/</< bundle.esm.js:19
    Subscription Observable.js:197
    subscribe Observable.js:279
    complete Concast.js:57
    node_modules main.6c1597cc4e45fba49a4f.js:352551
    Concast Concast.js:75
    node_modules main.6c1597cc4e45fba49a4f.js:348647
    node_modules main.6c1597cc4e45fba49a4f.js:348174
    node_modules main.6c1597cc4e45fba49a4f.js:348173
    step tslib.es6.js:102
    verb tslib.es6.js:83
    __awaiter tslib.es6.js:76
    __awaiter tslib.es6.js:72
    node_modules main.6c1597cc4e45fba49a4f.js:348133
    node_modules main.6c1597cc4e45fba49a4f.js:346891
    deleteOne Collection.js:229
    onOk ContactCard.index.tsx:36
    onClick ActionButton.js:97
    handleClick button.js:209
    React 14
    unstable_runWithPriority scheduler.development.js:468
    React 22
    render confirm.js:89
    setTimeout handler*render confirm.js:78
    confirm confirm.js:129
    confirmFn index.js:29
    onDeleteContact ContactCard.index.tsx:18
    handleClick button.js:209
    React 5

I still can delete via a direct apolloClient.mutate though. So the bug is clearly inside the .deleteOne itself.
The code that works before I fetch the document, and throws after I did :
relatedContactsCollection
    .deleteOne(relatedContact._id)
    .catch(console.log);

apollo client Payload is not serializable: cyclic object value
What is the object? Do you have certain serialisation options ?

@theodorDiaconu I do not have the information about the exact object, the error is not really transparent. I'll try adding a error link on the apollo client

@Fen747 do you happen to have documents that reference themselves directly or indirectly? Those cannot be JSON serialised? Looking at the code really, it's just a mutation.

@Fen747 can you help me reproduce this?

ping @Fen747


Still request failed with status code 429 and connections reset

Describe The Bug:
Versions 16 and 17 beta, still with bug 449. Status requests seem to overlap with timeouted reconnections, resulting in tcp L510 flooding and connection dropping. Several hours after restarting HB, four L510s are plagued by several dozen connections per second, which generates error 449 (checked in router logs). Please do something about it, as plugins from version 16 on are useless as they are.
To Reproduce:
Just start/reboot HB service, wait a few minutes and watch the rapidly increasing HB tcp port 80 connections to L510.
Expected behavior:
Elimination of overlapping connections (summing reconnections, and the set frequency of device state requests).
Logs:
Logs, as in my previous post.

[05/04/2022, 07:59:38] [Tapo Smart Platform] 371 Error: read ECONNRESET
[05/04/2022, 07:59:38] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:38] [Tapo Smart Platform] 371 Error: read ECONNRESET
[05/04/2022, 07:59:38] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:38] [Tapo Smart Platform] 371 Error: read ECONNRESET
[05/04/2022, 07:59:38] [Tapo Smart Platform] 371 Error: read ECONNRESET
[05/04/2022, 07:59:38] [Tapo Smart Platform] 371 Error: read ECONNRESET
[05/04/2022, 07:59:38] [Tapo Smart Platform] 371 Error: read ECONNRESET
[05/04/2022, 07:59:38] [Tapo Smart Platform] 371 Error: read ECONNRESET
[05/04/2022, 07:59:38] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:38] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:38] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:38] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:39] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:39] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:39] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:40] [Tapo Smart Platform] 371 Error: read ECONNRESET
[05/04/2022, 07:59:40] [Tapo Smart Platform] 371 Error: read ECONNRESET
[05/04/2022, 07:59:40] [Tapo Smart Platform] 371 Error: read ECONNRESET
[05/04/2022, 07:59:40] [Tapo Smart Platform] 371 Error: read ECONNRESET
[05/04/2022, 07:59:40] [Tapo Smart Platform] 371 Error: read ECONNRESET
[05/04/2022, 07:59:40] [Tapo Smart Platform] 371 Error: read ECONNRESET
[05/04/2022, 07:59:40] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:40] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:42] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:42] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:42] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:42] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:42] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/04/2022, 07:59:42] [Tapo Smart Platform] 371 Error: Request failed with status code 429

Brand new 1.4.17! :)

Same Log-Message on my HB.
What I have done so far:

Created Sub-Bridge for the PlugIn
Uninstalled the PlugIn, cleared all Files from the HB-Users directory, Reinstalled it and added device per device to the PlugIn again

Still showing the Error message:
[05/11/2022, 10:42:16] [Tapo Smart Platform] Restarting child bridge...
[05/11/2022, 10:42:16] Got SIGTERM, shutting down child bridge process...
[05/11/2022, 10:42:21] [Tapo Smart Platform] Child bridge process ended
[05/11/2022, 10:42:21] [Tapo Smart Platform] Process Ended. Code: 143, Signal: null
[05/11/2022, 10:42:28] [Tapo Smart Platform] Restarting Process...
[05/11/2022, 10:42:29] [Tapo Smart Platform] Launched child bridge with PID 18651
[05/11/2022, 10:42:31] Registering platform 'homebridge-tapo.TapoP100'
[05/11/2022, 10:42:31] [Tapo Smart Platform] Loaded homebridge-tapo v1.4.17 child bridge successfully
[05/11/2022, 10:42:31] Loaded 4 cached accessories from cachedAccessories.0E82BD9C222F.
[05/11/2022, 10:42:31] [Tapo Smart Platform] Loading accessory from cache: Licht in Dianas Büro
[05/11/2022, 10:42:31] [Tapo Smart Platform] Loading accessory from cache: Licht in Michas Büro
[05/11/2022, 10:42:31] [Tapo Smart Platform] Loading accessory from cache: Licht im Schlafzimmer
[05/11/2022, 10:42:31] [Tapo Smart Platform] Loading accessory from cache: Ampel
[05/11/2022, 10:42:31] [Tapo Smart Platform] Restoring existing accessory from cache: Licht in Dianas Büro
[05/11/2022, 10:42:32] [Tapo Smart Platform] Restoring existing accessory from cache: Licht in Michas Büro
[05/11/2022, 10:42:32] [Tapo Smart Platform] Restoring existing accessory from cache: Licht im Schlafzimmer
[05/11/2022, 10:42:32] [Tapo Smart Platform] Restoring existing accessory from cache: Ampel
[05/11/2022, 10:42:33] [Tapo Smart Platform] Adding new accessory: 192.x.x.111
[05/11/2022, 10:42:33] Homebridge v1.5.1 (HAP v0.10.4) (Tapo Smart Platform) is running on port 39654.
[05/11/2022, 10:42:56] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/11/2022, 10:43:04] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/11/2022, 10:43:04] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/11/2022, 10:43:04] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/11/2022, 10:43:08] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[05/11/2022, 10:43:08] [Tapo Smart Platform] 371 Error: Request failed with status code 429
(x-ed out one IP Address)
Don't know, how to fix this.

Have you played around with these settings?

Of course. I've set interval to 300 secs (5 minutes) and increased timeout value to 180 secs without effects. Unfortunately after couple of minutes flood has begun again.


[ShaderC] Fix leak in Metal/SPIRV - using no fancy smanshy new age voodoo

Issue https://github.com/bkaradzic/bgfx/issues/2387
Raw: https://github.com/phniix/bgfx/commits/shaderc_option_3


drivers: rcar_mmc: add request retry mechanism

Add request retry mechanism to Renesas SD/MMC driver.

Thanks!

However, can be some types of errors after which it isn't necessary to retry

Word missing? Did you wanted to say "However, there can be some types..."?
With that fixed:
Acked-by: Volodymyr Babchuk<EMAIL_ADDRESS>


Governance. Retract votes. Unavailable for multishard wallet

Description
When user try to retract votes with multishard wallet it opens empty window:

Test accounts:
accounts.json
wallets.json
Steps to Reproduce

Open Governance
Go to Add delegations as a multishard wallet
Try to remove vote via message about unavailable tracks

Expected Behavior
Success remove with multishard wallet
Actual Behavior
Empty window
Environment
https://github.com/novasamatech/nova-spektr/commit/7a92b170ac2e88d1778ed74839a9d723707d762b

will be implemented in:
https://github.com/novasamatech/nova-spektr/issues/2364


Revisit option to single-click list items

Options:
1, Convert one of the rows field to a link
2. Add a new column - "Open" or some derivation of this
I like #1

Agreed. #2 was the first idea I had, but #1 makes more sense.

Okay, this turns out to be an easy fix. I'll have a PR up for it shortly.

Could we get this added to some board or other so we can mark it in-review/closed as appropriate?

done!


Shutting down an Alpine instance takes a long time

Shutting down the default Ubuntu client takes 2 seconds, whereas shutting down an alpine client takes about 80 seconds.
Ubuntu

ha.stderr.log
{"level":"info","msg":"Received SIGINT, shutting down the host agent","time":"2021-08-06T15:34:33-07:00"}
{"level":"info","msg":"Shutting down the host agent","time":"2021-08-06T15:34:33-07:00"}
{"level":"info","msg":"Unmounting \"/Users/jan\"","time":"2021-08-06T15:34:33-07:00"}
{"level":"info","msg":"Unmounting \"/tmp/lima\"","time":"2021-08-06T15:34:33-07:00"}
{"level":"debug","msg":"shutting down the SSH master","time":"2021-08-06T15:34:33-07:00"}
{"error":"unexpected EOF","level":"warning","msg":"connection to the guest agent was closed unexpectedly","time":"2021-08-06T15:34:33-07:00"}
{"level":"info","msg":"Shutting down QEMU with ACPI","time":"2021-08-06T15:34:33-07:00"}
{"level":"info","msg":"Sending QMP system_powerdown command","time":"2021-08-06T15:34:33-07:00"}
{"error":null,"level":"info","msg":"QEMU has exited","time":"2021-08-06T15:34:35-07:00"}

serial.log (no useful information)
[  OK  ] Removed slice system-modprobe.slice.
[  OK  ] Stopped target Cloud-init target.
[  OK  ] Stopped target Graphical Interface.
[  OK  ] Stopped target Host and Network Name Lookups.
[  OK  ] Stopped target Timers.
[  OK  ] Stopped Daily apt upgrade and clean activities.
[  OK  ] Stopped Daily apt download activities.
[  OK  ] Stopped Periodic ext4 Onli…ata Check for All Filesystems.
[  OK  ] Stopped Discard unused blocks once a week.
[  OK  ] Stopped Refresh fwupd metadata regularly.
[  OK  ] Stopped Daily rotation of log files.
[  OK  ] Stopped Daily man-db regeneration.
[  OK  ] Stopped Message of the Day.
[  OK  ] Stopped Daily Cleanup of Temporary Directories.
[  OK  ] Stopped Ubuntu Advantage update messaging.
[  OK  ] Stopped Download data for …ailed at package install time.
[  OK  ] Stopped Check to see wheth…w version of Ubuntu available.
[  OK  ] Stopped target System Time Synchronized.
[  OK  ] Stopped target System Time Set.
[  OK  ] Closed LVM2 poll daemon socket.
[  OK  ] Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
         Stopping Accounts Service...
         Stopping Availability of block devices...
[  OK  ] Stopped Execute cloud user/final scripts.
[  OK  ] Stopped target Multi-User System.
[  OK  ] Stopped target Login Prompts.
         Stopping LSB: automatic crash report generation...
[  OK  ] Stopped Apply the settings specified in cloud-config.
[  OK  ] Stopped target Cloud-config availability.
[  OK  ] Stopped target Network is Online.
         Stopping Regular background program processing daemon...
         Stopping Create final runt…dir for shutdown pivot root...
         Stopping Getty on tty1...
[  OK  ] Stopped Record successful boot for GRUB.
         Stopping irqbalance daemon...
         Stopping Dispatcher daemon for systemd-networkd...
         Stopping PackageKit Daemon...
[  OK  ] Stopped Terminate Plymouth Boot Screen.
         Stopping Authorization Manager...
         Stopping System Logging Service...
         Stopping Serial Getty on ttyS0...
[  OK  ] Stopped Wait until snapd is fully seeded.
         Stopping Snap Daemon...
         Stopping OpenBSD Secure Shell server...
         Stopping User Login Management...
[  OK  ] Stopped Commit a transient machine-id on disk.
         Stopping Load/Save Random Seed...
         Stopping Disk Manager...
         Stopping User Manager for UID 501...
[  OK  ] Stopped Accounts Service.
[  OK  ] Stopped Regular background program processing daemon.
[  OK  ] Stopped irqbalance daemon.
[  OK  ] Stopped Dispatcher daemon for systemd-networkd.
[  OK  ] Stopped System Logging Service.
[  OK  ] Stopped Snap Daemon.
[  OK  ] Stopped Serial Getty on ttyS0.
[  OK  ] Stopped Getty on tty1.
[  OK  ] Stopped Disk Manager.
[  OK  ] Stopped Authorization Manager.
[  OK  ] Stopped OpenBSD Secure Shell server.
[  OK  ] Stopped User Manager for UID 501.
[  OK  ] Stopped PackageKit Daemon.
[  OK  ] Stopped Availability of block devices.
[  OK  ] Stopped Load/Save Random Seed.
[  OK  ] Removed slice system-getty.slice.
[  OK  ] Removed slice system-serial\x2dgetty.slice.
[  OK  ] Stopped Hold until boot process finishes up.
         Stopping User Runtime Directory /run/user/501...
[  OK  ] Stopped User Login Management.
[  OK  ] Unmounted /run/user/501.
[  OK  ] Stopped LSB: automatic crash report generation.
[  OK  ] Stopped User Runtime Directory /run/user/501.
[  OK  ] Removed slice User Slice of UID 501.
         Stopping Permit User Sessions...
[  OK  ] Stopped Permit User Sessions.
[  OK  ] Stopped target Basic System.
[  OK  ] Stopped target Network.
[  OK  ] Stopped target User and Group Name Lookups.
[  OK  ] Stopped target Paths.
[  OK  ] Stopped target Remote File Systems.
[  OK  ] Stopped target Remote File Systems (Pre).
[  OK  ] Stopped target Slices.
[  OK  ] Removed slice User and Session Slice.
[  OK  ] Stopped target Sockets.
[  OK  ] Closed Open-iSCSI iscsid Socket.
[  OK  ] Closed Socket unix for snap application lxd.daemon.
[  OK  ] Closed Socket activation for snappy daemon.
[  OK  ] Closed Syslog Socket.
[  OK  ] Closed UUID daemon activation socket.
[  OK  ] Stopped target System Initialization.
[  OK  ] Stopped target Local Encrypted Volumes.
[  OK  ] Stopped Dispatch Password …ts to Console Directory Watch.
[  OK  ] Stopped Forward Password R…uests to Wall Directory Watch.
[  OK  ] Stopped Initial cloud-init…ob (metadata service crawler).
[  OK  ] Stopped Wait for Network to be Configured.
         Stopping Network Name Resolution...
         Stopping Network Time Synchronization...
         Stopping Update UTMP about System Boot/Shutdown...
[  OK  ] Stopped Network Name Resolution.
         Stopping Network Service...
[  OK  ] Stopped Update UTMP about System Boot/Shutdown.
[  OK  ] Stopped Network Time Synchronization.
[  OK  ] Stopped Create Volatile Files and Directories.
[  OK  ] Stopped Network Service.
[  OK  ] Stopped target Network (Pre).
[  OK  ] Stopped Initial cloud-init job (pre-networking).
[  OK  ] Stopped Apply Kernel Variables.
[  OK  ] Stopped Load Kernel Modules.
[  OK  ] Stopped Create final runtime dir for shutdown pivot root.
[  OK  ] Stopped target Local File Systems.
         Unmounting /boot/efi...
         Unmounting /mnt/lima-cidata...
         Unmounting /run/snapd/ns/lxd.mnt...
         Unmounting Mount unit for core18, revision 2066...
         Unmounting Mount unit for lxd, revision 20684...
         Unmounting Mount unit for snapd, revision 12159...
[  OK  ] Unmounted /boot/efi.
[  OK  ] Unmounted /run/snapd/ns/lxd.mnt.
[  OK  ] Unmounted /mnt/lima-cidata.
         Unmounting /run/snapd/ns...
[  OK  ] Stopped File System Check on /dev/disk/by-label/UEFI.
[  OK  ] Removed slice system-systemd\x2dfsck.slice.
[  OK  ] Unmounted /run/snapd/ns.
[  OK  ] Unmounted Mount unit for core18, revision 2066.
[  OK  ] Stopped target Swap.
[  OK  ] Unmounted Mount unit for lxd, revision 20684.
[  OK  ] Unmounted Mount unit for snapd, revision 12159.
[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Reached target Unmount All Filesystems.
         Stopping Monitoring of LVM…meventd or progress polling...
         Stopping Device-Mapper Multipath Device Controller...
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Stopped Create System Users.
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Stopped File System Check on Root Device.
[  OK  ] Stopped Device-Mapper Multipath Device Controller.
[  OK  ] Stopped Monitoring of LVM2… dmeventd or progress polling.
[  OK  ] Reached target Shutdown.
[  OK  ] Reached target Final Step.
[  OK  ] Finished Power-Off.
[  OK  ] Reached target Power-Off.

Alpine

ha.stderr.log
{"level":"info","msg":"Received SIGINT, shutting down the host agent","time":"2021-08-06T15:29:05-07:00"}
{"level":"info","msg":"Shutting down the host agent","time":"2021-08-06T15:29:05-07:00"}
{"level":"info","msg":"Unmounting \"/Users/jan\"","time":"2021-08-06T15:29:05-07:00"}
{"level":"info","msg":"Unmounting \"/tmp/lima\"","time":"2021-08-06T15:29:05-07:00"}
{"level":"debug","msg":"shutting down the SSH master","time":"2021-08-06T15:29:05-07:00"}
{"error":"unexpected EOF","level":"warning","msg":"connection to the guest agent was closed unexpectedly","time":"2021-08-06T15:29:05-07:00"}
{"level":"info","msg":"Shutting down QEMU with ACPI","time":"2021-08-06T15:29:05-07:00"}
{"level":"info","msg":"Sending QMP system_powerdown command","time":"2021-08-06T15:29:05-07:00"}
{"level":"info","msg":"Forwarding \"/run/user/501/lima-guestagent.sock\" (guest) to \"/Users/jan/.lima/std/ga.sock\" (host)","time":"2021-08-06T15:29:15-07:00"}
{"error":"failed to run [ssh -i /Users/jan/.lima/_config/user -i<EMAIL_ADDRESS>-i<EMAIL_ADDRESS>-o StrictHostKeyChecking=no -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -F /dev/null -l jan -o ControlMaster=auto -o ControlPath=/Users/jan/.lima/std/ssh.sock -o ControlPersist=5m -T -O forward -L /Users/jan/.lima/std/ga.sock:/run/user/501/lima-guestagent.sock -N -f -p 40022 <IP_ADDRESS> --]: \"\": exit status 255","level":"warning","msg":"failed to setting up forward from \"/run/user/501/lima-guestagent.sock\" (guest) to \"/Users/jan/.lima/std/ga.sock\" (host)","time":"2021-08-06T15:29:15-07:00"}
{"error":"stat /Users/jan/.lima/std/ga.sock: no such file or directory","level":"warning","msg":"connection to the guest agent was closed unexpectedly","time":"2021-08-06T15:29:16-07:00"}
{"level":"info","msg":"Forwarding \"/run/user/501/lima-guestagent.sock\" (guest) to \"/Users/jan/.lima/std/ga.sock\" (host)","time":"2021-08-06T15:29:26-07:00"}
{"error":"failed to run [ssh -i /Users/jan/.lima/_config/user -i<EMAIL_ADDRESS>-i<EMAIL_ADDRESS>-o StrictHostKeyChecking=no -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -F /dev/null -l jan -o ControlMaster=auto -o ControlPath=/Users/jan/.lima/std/ssh.sock -o ControlPersist=5m -T -O forward -L /Users/jan/.lima/std/ga.sock:/run/user/501/lima-guestagent.sock -N -f -p 40022 <IP_ADDRESS> --]: \"\": exit status 255","level":"warning","msg":"failed to setting up forward from \"/run/user/501/lima-guestagent.sock\" (guest) to \"/Users/jan/.lima/std/ga.sock\" (host)","time":"2021-08-06T15:29:26-07:00"}
{"error":"stat /Users/jan/.lima/std/ga.sock: no such file or directory","level":"warning","msg":"connection to the guest agent was closed unexpectedly","time":"2021-08-06T15:29:26-07:00"}
{"level":"info","msg":"Forwarding \"/run/user/501/lima-guestagent.sock\" (guest) to \"/Users/jan/.lima/std/ga.sock\" (host)","time":"2021-08-06T15:29:36-07:00"}
{"error":"failed to run [ssh -i /Users/jan/.lima/_config/user -i<EMAIL_ADDRESS>-i<EMAIL_ADDRESS>-o StrictHostKeyChecking=no -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -F /dev/null -l jan -o ControlMaster=auto -o ControlPath=/Users/jan/.lima/std/ssh.sock -o ControlPersist=5m -T -O forward -L /Users/jan/.lima/std/ga.sock:/run/user/501/lima-guestagent.sock -N -f -p 40022 <IP_ADDRESS> --]: \"\": exit status 255","level":"warning","msg":"failed to setting up forward from \"/run/user/501/lima-guestagent.sock\" (guest) to \"/Users/jan/.lima/std/ga.sock\" (host)","time":"2021-08-06T15:29:36-07:00"}
{"error":"stat /Users/jan/.lima/std/ga.sock: no such file or directory","level":"warning","msg":"connection to the guest agent was closed unexpectedly","time":"2021-08-06T15:29:36-07:00"}
{"level":"info","msg":"Forwarding \"/run/user/501/lima-guestagent.sock\" (guest) to \"/Users/jan/.lima/std/ga.sock\" (host)","time":"2021-08-06T15:29:46-07:00"}
{"error":"failed to run [ssh -i /Users/jan/.lima/_config/user -i<EMAIL_ADDRESS>-i<EMAIL_ADDRESS>-o StrictHostKeyChecking=no -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -F /dev/null -l jan -o ControlMaster=auto -o ControlPath=/Users/jan/.lima/std/ssh.sock -o ControlPersist=5m -T -O forward -L /Users/jan/.lima/std/ga.sock:/run/user/501/lima-guestagent.sock -N -f -p 40022 <IP_ADDRESS> --]: \"\": exit status 255","level":"warning","msg":"failed to setting up forward from \"/run/user/501/lima-guestagent.sock\" (guest) to \"/Users/jan/.lima/std/ga.sock\" (host)","time":"2021-08-06T15:29:46-07:00"}
{"error":"stat /Users/jan/.lima/std/ga.sock: no such file or directory","level":"warning","msg":"connection to the guest agent was closed unexpectedly","time":"2021-08-06T15:29:46-07:00"}
{"level":"info","msg":"Forwarding \"/run/user/501/lima-guestagent.sock\" (guest) to \"/Users/jan/.lima/std/ga.sock\" (host)","time":"2021-08-06T15:29:56-07:00"}
{"error":"failed to run [ssh -i /Users/jan/.lima/_config/user -i<EMAIL_ADDRESS>-i<EMAIL_ADDRESS>-o StrictHostKeyChecking=no -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -F /dev/null -l jan -o ControlMaster=auto -o ControlPath=/Users/jan/.lima/std/ssh.sock -o ControlPersist=5m -T -O forward -L /Users/jan/.lima/std/ga.sock:/run/user/501/lima-guestagent.sock -N -f -p 40022 <IP_ADDRESS> --]: \"\": exit status 255","level":"warning","msg":"failed to setting up forward from \"/run/user/501/lima-guestagent.sock\" (guest) to \"/Users/jan/.lima/std/ga.sock\" (host)","time":"2021-08-06T15:29:56-07:00"}
{"error":"stat /Users/jan/.lima/std/ga.sock: no such file or directory","level":"warning","msg":"connection to the guest agent was closed unexpectedly","time":"2021-08-06T15:29:56-07:00"}
{"level":"info","msg":"Forwarding \"/run/user/501/lima-guestagent.sock\" (guest) to \"/Users/jan/.lima/std/ga.sock\" (host)","time":"2021-08-06T15:30:06-07:00"}
{"error":"failed to run [ssh -i /Users/jan/.lima/_config/user -i<EMAIL_ADDRESS>-i<EMAIL_ADDRESS>-o StrictHostKeyChecking=no -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -F /dev/null -l jan -o ControlMaster=auto -o ControlPath=/Users/jan/.lima/std/ssh.sock -o ControlPersist=5m -T -O forward -L /Users/jan/.lima/std/ga.sock:/run/user/501/lima-guestagent.sock -N -f -p 40022 <IP_ADDRESS> --]: \"\": exit status 255","level":"warning","msg":"failed to setting up forward from \"/run/user/501/lima-guestagent.sock\" (guest) to \"/Users/jan/.lima/std/ga.sock\" (host)","time":"2021-08-06T15:30:06-07:00"}
{"error":"stat /Users/jan/.lima/std/ga.sock: no such file or directory","level":"warning","msg":"connection to the guest agent was closed unexpectedly","time":"2021-08-06T15:30:06-07:00"}
{"level":"info","msg":"Forwarding \"/run/user/501/lima-guestagent.sock\" (guest) to \"/Users/jan/.lima/std/ga.sock\" (host)","time":"2021-08-06T15:30:16-07:00"}
{"error":"failed to run [ssh -i /Users/jan/.lima/_config/user -i<EMAIL_ADDRESS>-i<EMAIL_ADDRESS>-o StrictHostKeyChecking=no -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -F /dev/null -l jan -o ControlMaster=auto -o ControlPath=/Users/jan/.lima/std/ssh.sock -o ControlPersist=5m -T -O forward -L /Users/jan/.lima/std/ga.sock:/run/user/501/lima-guestagent.sock -N -f -p 40022 <IP_ADDRESS> --]: \"\": exit status 255","level":"warning","msg":"failed to setting up forward from \"/run/user/501/lima-guestagent.sock\" (guest) to \"/Users/jan/.lima/std/ga.sock\" (host)","time":"2021-08-06T15:30:16-07:00"}
{"error":"stat /Users/jan/.lima/std/ga.sock: no such file or directory","level":"warning","msg":"connection to the guest agent was closed unexpectedly","time":"2021-08-06T15:30:16-07:00"}
{"error":null,"level":"info","msg":"QEMU has exited","time":"2021-08-06T15:30:23-07:00"}

serial.log
Welcome to Alpine Linux 3.13
^MKernel 5.10.38-0-virt on an x86_64 (/dev/ttyS0)

^Mlima-std login:  * Stopping sshd ... [ ok ]
 * Shutting down ssh connections ... * sshd: caught SIGTERM, aborting
 [ ok ]
 * Stopping busybox syslog ... [ ok ]
 * Unregistering QEMU binaries in binfmt misc ... [ ok ]
 * Stopping busybox acpid ... [ ok ]
 * Unmounting loop devices
 *   Remounting /.modloop read only ... *   in use but fuser finds nothing
 [ !! ]
 * Unmounting filesystems
 *   Unmounting /var/lib ... [ ok ]
 *   Unmounting /usr/local ... *   Unmounting /tmp ... [ ok ]
 *   Unmounting /home ... [ ok ]
 *   Unmounting /etc ... [ ok ]
 *   Unmounting /mnt/data ... [ ok ]
 *   Unmounting /mnt/lima-cidata ... [ ok ]
 *   Unmounting /.modloop ... *   in use but fuser finds nothing
 [ !! ]
 *   Unmounting /media/cdrom ... *   in use but fuser finds nothing
 [ !! ]
 * Setting hardware clock using the system clock [UTC] ... [ ok ]
 * Stopping udev ... [ ok ]
 * Unmounting /.modloop ... [ ok ]
 * Terminating remaining processes ... [ ok ]
 * Killing remaining processes ... [ ok ]
 * Saving dependency cache ... [ ok ]
 [ ok ]
 * Remounting remaining filesystems read-only ... *   Remounting /usr/local read only ... [ ok ]
 *   Remounting / read only ... [ ok ]
 *   Remounting /media/cdrom read only ... [ ok ]
 [ ok ]
^MThe system is going down NOW!
^MSent SIGTERM to all processes
^MSent SIGKILL to all processes
^MRequesting system poweroff

The shutdown is not always this slow, here are logs when it took 8 seconds:

ha.stderr.log
{"level":"info","msg":"Received SIGINT, shutting down the host agent","time":"2021-08-06T16:20:44-07:00"}
{"level":"info","msg":"Shutting down the host agent","time":"2021-08-06T16:20:44-07:00"}
{"level":"info","msg":"Unmounting \"/Users/jan\"","time":"2021-08-06T16:20:44-07:00"}
{"level":"info","msg":"Unmounting \"/tmp/lima\"","time":"2021-08-06T16:20:44-07:00"}
{"level":"debug","msg":"shutting down the SSH master","time":"2021-08-06T16:20:44-07:00"}
{"error":"unexpected EOF","level":"warning","msg":"connection to the guest agent was closed unexpectedly","time":"2021-08-06T16:20:44-07:00"}
{"level":"info","msg":"Shutting down QEMU with ACPI","time":"2021-08-06T16:20:44-07:00"}
{"level":"info","msg":"Sending QMP system_powerdown command","time":"2021-08-06T16:20:44-07:00"}
{"error":null,"level":"info","msg":"QEMU has exited","time":"2021-08-06T16:20:52-07:00"}

serial.log (seems same as above)
Welcome to Alpine Linux 3.13
^MKernel 5.10.38-0-virt on an x86_64 (/dev/ttyS0)

^Mlima-std login:  * Stopping sshd ... [ ok ]
 * Shutting down ssh connections ... * sshd: caught SIGTERM, aborting
 [ ok ]
 * Stopping busybox syslog ... [ ok ]
 * Unregistering QEMU binaries in binfmt misc ... [ ok ]
 * Stopping busybox acpid ... [ ok ]
 * Unmounting loop devices
 *   Remounting /.modloop read only ... *   in use but fuser finds nothing
 [ !! ]
 * Unmounting filesystems
 *   Unmounting /var/lib ... [ ok ]
 *   Unmounting /usr/local ... *   Unmounting /tmp ... [ ok ]
 *   Unmounting /home ... [ ok ]
 *   Unmounting /etc ... [ ok ]
 *   Unmounting /mnt/data ... [ ok ]
 *   Unmounting /mnt/lima-cidata ... [ ok ]
 *   Unmounting /.modloop ... *   in use but fuser finds nothing
 [ !! ]
 *   Unmounting /media/cdrom ... *   in use but fuser finds nothing
 [ !! ]
 * Setting hardware clock using the system clock [UTC] ... [ ok ]
 * Stopping udev ... [ ok ]
 * Unmounting /.modloop ... [ ok ]
 * Terminating remaining processes ... [ ok ]
 * Killing remaining processes ... [ ok ]
 * Saving dependency cache ... [ ok ]
 [ ok ]
 * Remounting remaining filesystems read-only ... *   Remounting /usr/local read only ... [ ok ]
 *   Remounting / read only ... [ ok ]
 *   Remounting /media/cdrom read only ... [ ok ]
 [ ok ]
^MThe system is going down NOW!
^MSent SIGTERM to all processes
^MSent SIGKILL to all processes
^MRequesting system poweroff

I believe this has been fixed by https://github.com/lima-vm/lima/commit/dae7e65, in particular:

cancel HA context to stop reconnecting to the guestagent


Unused on_cancel Attribute in Dialog Component

In the Dialog component, the on_cancel attribute is declared but not used.
Is this intentional, or should it work similarly to the Modal component in the core_component?
Let me know if I can help!
Thanks!

Closed as merged #101

Release 0.14.4 for this fix


Using fastlane PEM getting error

After creating my pem file with fastlane I try to send a testing notification to my test device. But I keep getting "Error: certificate does not support configured environment, production: false", same for production: true.
Fastlane generates a .p12, .pem and a .pkey file for APNS certification. I can't get this to work.

Could you please email me a copy of your certificate PEM without the public key so I can see what might be going wrong.
Thanks
―A

On 2 Sep 2015, at 23:17, Lee Jacobs<EMAIL_ADDRESS>wrote:
After creating my pem file with fastlane I try to send a testing notification to my test device. But I keep getting "Error: certificate does not support configured environment, production: false", same for production: true.
Fastlane generates a .p12, .pem and a .pkey file for APNS certification. I can't get this to work.
―
Reply to this email directly or view it on GitHub.

Things have actually been fixed, changed my env variable to production, removed production val from options and this issue has vanished. Thanks for the fast response though.


Multiple GPUs causing delays in job start

Speaking with Irek, we should probably remove the ability to request nodes and just request the number of GPUs we need and let SLURM determine which GPUs to give us.
However there may be times we want to specify the 4x32GB GPUs for large datasets, including when we need Peer-to-Peer to share VRAM for very large datasets.

Irek believe we may be requesting GPUs incorrectly at present and only requesting the 4x32GB GPUs which is why, when we request more than one GPU, we see significant delays between job submission and job start

We need to identify if this is a coding issue, or simply under resourced hardware, is there a way to display in the IPP what's being used in a simple graphic to let users decide how to shape their job

Indication on resources page what GPUs are available now?

Scheduling time from walltime on bunya expected to improve prediction
Average runtimes for similar size jobs based on slurm vs IPP metrics
Heuristics on resources becoming available
View work queue on monitoring page
IPP stats over time
minimal effort to provide some improvement compared to other priorities


Standardized Contract Deployment/Call Process

Context
A long time ago, when we were able to deploy hello world for the first time, due to some too-old-unreproducable-but-not-important-anymore issue, we had this workaround that waits until the tx is mined to return tx receipt, for at most 20s.
#126
However, this is not a very standard workflow, the standard flow for pending tx should be:

eth_getTxByHash should return partial tx data, and some fields being null
eth_getTxReceipt should return null

Breaking Changes
Changed eth_getTxByHash and eth_getTxReceipt's behavior to the standard way.
Now both of the RPCs should return immediately without waiting for tx to be mined, and client itself should handle when tx is mined. For examples:

Metamask will keep asking eth_getTxReceipt until it's not null after sending token
hardhat will keep asking eth_getTxReceipt until it's not null after deploying a contract. However, hardhat doesn't wait automatically for contract calls, so if we want hardhat to work with normal-sealing, we need to manually add tx.wait().

As a result, we will need a couple polish for hardhat tutorials (partial PR):

we don't need to loop helper anymore!
in order for contract call to work with normal-sealing node, we need to add tx.wait() for all state changing calls.

This PR also polished getTransactionCount to be able to get more accurate nonce by adding the pending nonce.
Test
normal-sealing
manually tested:

truffle tutorials all passed
hardhat Token tutorials passed after adding tx.wait()
metamask token sending still works

instant-sealing
after removing loop helper, all previous CI tests still passed with instant sealing
Reference
RPC behavior

https://eth.wiki/json-rpc/API
https://stackoverflow.com/a/67263711/5770676

Hardhat behavior

https://discord.com/channels/750408878008827925/750408878008827928/954325283597582356

Thanks @zjb0807 , I will merge it and if it's incompatible with latest mandala I will upload fix in another PR


Print a backtrace on error or test failure

Related to issue #12

Thanks. Committed with some changes.


bug：hub cannot startup

What is the bug?
hub cannot startup
Additional context (optional)
{"level":30,"time":1696922814632,"pid":1,"hostname":"e7752c3619fd","component":"L2EventsProvider","blockNumber":110662018,"msg":"new block: 110662018"}
{"level":40,"time":1696922816197,"pid":1,"hostname":"e7752c3619fd","component":"SyncEngine","error":{"presentable":false,"name":"HubError"},"errMsg":"Deadline exceeded","peerId":"12D3KooWQSyPDa14MJUhwU9UcvCkipMVsPYCGoNpyRNS55y5gZ9W","peerContact":{"gossipAddress":{"address":"<IP_ADDRESS>","family":4,"port":2282,"dnsName":""},"rpcAddress":{"address":"<IP_ADDRESS>","family":4,"port":2283,"dnsName":""},"excludedHashes":["af1349b9f5f9a1a6a0404dea36dcc9499bcb25c9","af1349b9f5f9a1a6a0404dea36dcc9499bcb25c9","9de2e2088f1be3950fe971b0526cade9302dc067","fd7174ce5e6c3a7bbe809b4a9255b03a8d4d3b68","554470f60d432b183e0009569913f61b49e80e90","697a4fb8fb3c8e18da8c524329e2152b216ba808","3f426974b5408f0fffc4502bd4183eaa0ba73189"],"count":4558598,"hubVersion":"2023.10.4","network":1,"appVersion":"1.6.0"},"msg":"Diffsync: Failed to get peer state, skipping sync"}
{"level":30,"time":1696922818898,"pid":1,"hostname":"e7752c3619fd","component":"L2EventsProvider","blockNumber":110662020,"msg":"new block: 110662020"}
{"level":30,"time":1696922823190,"pid":1,"hostname":"e7752c3619fd","component":"L2EventsProvider","blockNumber":110662022,"msg":"new block: 110662022"}
{"level":30,"time":1696922825261,"pid":1,"hostname":"e7752c3619fd","component":"FNameRegistryEventsProvider","msg":"Fetched 0 fname events upto 20737"}
{"level":30,"time":1696922827450,"pid":1,"hostname":"e7752c3619fd","component":"L2EventsProvider","blockNumber":110662024,"msg":"new block: 110662024"}
{"level":30,"time":1696922831732,"pid":1,"hostname":"e7752c3619fd","component":"L2EventsProvider","blockNumber":110662027,"msg":"new block: 110662027"}
{"level":60,"time":1696922835209,"pid":1,"hostname":"e7752c3619fd","msg":"Forcing exit after grace period"}

I have the same problem
hubble-hubble-1  | {"level":40,"time":1696939530351,"pid":1,"hostname":"4ccf7866adb6","component":"Hub","event":{"blockNumber":108877896,"blockHash":"0xeafe5cb9d7544d0eb7104aeb475d0b2a46c5c6510bb041bbe94b1b9590a37c37","fid":16889,"type":"EVENT_TYPE_SIGNER"},"source":"l2-provider","errCode":"bad_request.duplicate","msg":"submitOnChainEvent error: onChainEvent already exists"} hubble-hubble-1  | {"level":40,"time":1696939530351,"pid":1,"hostname":"4ccf7866adb6","component":"Hub","event":{"blockNumber":108877896,"blockHash":"0xeafe5cb9d7544d0eb7104aeb475d0b2a46c5c6510bb041bbe94b1b9590a37c37","fid":16892,"type":"EVENT_TYPE_SIGNER"},"source":"l2-provider","errCode":"bad_request.duplicate","msg":"submitOnChainEvent error: onChainEvent already exists"} hubble-hubble-1  | {"level":40,"time":1696939530352,"pid":1,"hostname":"4ccf7866adb6","component":"Hub","event":{"blockNumber":108877896,"blockHash":"0xeafe5cb9d7544d0eb7104aeb475d0b2a46c5c6510bb041bbe94b1b9590a37c37","fid":16956,"type":"EVENT_TYPE_SIGNER"},"source":"l2-provider","errCode":"bad_request.duplicate","msg":"submitOnChainEvent error: onChainEvent already exists"} hubble-hubble-1  | {"level":40,"time":1696939530352,"pid":1,"hostname":"4ccf7866adb6","component":"Hub","event":{"blockNumber":108877896,"blockHash":"0xeafe5cb9d7544d0eb7104aeb475d0b2a46c5c6510bb041bbe94b1b9590a37c37","fid":16956,"type":"EVENT_TYPE_SIGNER"},"source":"l2-provider","errCode":"bad_request.duplicate","msg":"submitOnChainEvent error: onChainEvent already exists"} hubble-hubble-1  | {"level":40,"time":1696939530353,"pid":1,"hostname":"4ccf7866adb6","component":"Hub","event":{"blockNumber":108877896,"blockHash":"0xeafe5cb9d7544d0eb7104aeb475d0b2a46c5c6510bb041bbe94b1b9590a37c37","fid":16958,"type":"EVENT_TYPE_SIGNER"},"source":"l2-provider","errCode":"bad_request.duplicate","msg":"submitOnChainEvent error: onChainEvent already exists"} hubble-hubble-1  | {"level":30,"time":1696939530384,"pid":1,"hostname":"4ccf7866adb6","component":"GossipNode","identity":"12D3KooWSakyQismXysr1HKfqjPKeWmMp6hkjEw38wbDKpF6EWiV","msg":"Stopped libp2p..."} hubble-hubble-1  | {"level":30,"time":1696939534275,"pid":1,"hostname":"4ccf7866adb6","component":"L2EventsProvider","blockNumber":110670378,"msg":"new block: 110670378"} hubble-hubble-1  | {"level":30,"time":1696939538297,"pid":1,"hostname":"4ccf7866adb6","component":"L2EventsProvider","blockNumber":110670380,"msg":"new block: 110670380"} hubble-hubble-1  | {"level":30,"time":1696939542325,"pid":1,"hostname":"4ccf7866adb6","component":"L2EventsProvider","blockNumber":110670382,"msg":"new block: 110670382"} hubble-hubble-1  | {"level":30,"time":1696939546392,"pid":1,"hostname":"4ccf7866adb6","component":"L2EventsProvider","blockNumber":110670384,"msg":"new block: 110670384"} hubble-hubble-1  | {"level":30,"time":1696939550414,"pid":1,"hostname":"4ccf7866adb6","component":"L2EventsProvider","blockNumber":110670386,"msg":"new block: 110670386"} hubble-hubble-1  | {"level":30,"time":1696939553935,"pid":1,"hostname":"4ccf7866adb6","component":"FNameRegistryEventsProvider","msg":"Fetched 0 fname events upto 20740"} hubble-hubble-1  | {"level":30,"time":1696939554438,"pid":1,"hostname":"4ccf7866adb6","component":"L2EventsProvider","blockNumber":110670388,"msg":"new block: 110670388"} hubble-hubble-1  | {"level":30,"time":1696939558467,"pid":1,"hostname":"4ccf7866adb6","component":"L2EventsProvider","blockNumber":110670390,"msg":"new block: 110670390"} hubble-hubble-1  | {"level":60,"time":1696939560280,"pid":1,"hostname":"4ccf7866adb6","msg":"Forcing exit after grace period"} hubble-hubble-1 exit

I think this is a duplicate of https://github.com/farcasterxyz/hub-monorepo/issues/1481. Please follow along on that bug


A getElements method has been added to DateSelect and MonthSelect which ...

...returns an array of the Select elements created.
Unit tests have been added to cover the new method.

Merged, thanks @MajorCaiger!
develop: zendframework/zf2@d2d7146bc7d9246ea73118144157c8857d4a5ce8


Fix for notification lights getting stuck

I sometimes have an issue where many notifications in quick succession will cause the extension to "forget" to unset the notification color on the light.  I was reviewing the Hue API and I believe adding "alert": "select" to the parameters you pass to setLights will let you skip the entire "restore lights to previous state" event.  You may need to play with transitiontime instead of using the current value of 0 to make it look good though.

Hi @RedKrieg, "alert": "select" is supposed to run notification, but it doesn't work well along with setting a specific color. Not changing the color, It works as expected - it uses the last know color. Changing the color has an unexpected and inconsistent behavior:-(
I am thinking to add a timestamp to the restore state and in case the timestamp is fresh, the restore state would not be overwritten because many notifications are in progress...

That's funny to see this issue right now, I,  yesterday, exprienced this.

I opened thunderbird (or telegram, maybe both)
I had some notifications
light starter to play the notification color
I didn't focus on it a lot because it was at that moment I left the room, when I came back later (20min?) the light was still running the notification light instead of the scene it was displaying before.

Issue fixed. Notifications have been redesigned to use queues. The problem shouldn't be possible to happen again.


marathon app update documentation misleading (requires file)

The cli documentation states:
dcos marathon app update [--force]  [...]
However, the update command cannot simply accept a json string as indicated but rather requires piping to it.
For example,
dcos marathon app update basic-0 '{"instances":100}' will fail.
These will succeed:
echo '{"instances" : 100}' | dcos marathon app update basic-0
dcos marathon app update basic-0 < config.json

Hi @SL4YT1M3 !
This seems to be related to the dcos-cli and not to Marathon itself.
Could you post your issue in this repository again?
Thank you very much.

@SL4YT1M3
This syntax works without piping:
dcos marathon app update --force basic-0 instances=5
See https://docs.mesosphere.com/using/cli/marathonsyntax/ for more examples.