Refactoring

init function now works properly with default params
Make load configuration non-recursive. In the future maybe I can check for recursive references in the config file
Add tests to autoConfig

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Kube driver: pod restart does not bring back compose app

Compose app is deployed on ephemeral storage, so when the pod restarts docker starts with no containers.

fixed in #396


Query Docs

Query docs revisited.

New structure
Brought back remote queries doc from hiding
Brain dump
Marked missing sections as TODO

@Sanne thanks! +1 to push and iterate it afterwards: let me just fix the typos and remove some ancient references

That's fair. We provide a safe default which should perform fine in an
"average environment" bit in reality some tuning will always be needed.. As
no one runs on the average ;)
On Tue, 7 Mar 2017, 08:11 Yoann Rodière<EMAIL_ADDRESS>wrote:

@yrodiere commented on this pull request.
In documentation/src/main/asciidoc/user_guide/query.adoc
https://github.com/infinispan/infinispan/pull/4931#discussion_r104607975
:

+

+----
+
+Indexes are stored in a set of clustered caches, called by default LuceneIndexesData, LuceneIndexesMetadata and LuceneIndexesLocking.
+
+The LuceneIndexesLocking cache is used to store Lucene locks, and it is a very small cache: it will contains one entry per entity (index).
+
+The LuceneIndexesMetadata cache is used to store info about the logical files that are part of the index, such as names, chunks and sizes and it is also
+small in size.
+
+The LuceneIndexesData cache is the where most of the index is located: it is much bigger then the other two but should be smaller than the data in the cache itself, thanks to Lucene
+efficient storing techniques.
+
+The configuration above is changing the name of those 3 caches and redefining their configuration. Reasons to do so is performance tuning: since two of the 3 caches are small
+and heavily accessed, it makes sense to make them replicated, while the largest cache is configured as distributed. Manually redefining the index caches also
@Sanne https://github.com/Sanne I guess, but when reading this I had
the impression that the default was less optimal than this example, and
that may lead some users to needlessly redefine the configuration.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/infinispan/infinispan/pull/4931#discussion_r104607975,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACmTd2FPdHkVWKlNEqLJzzcPZvvSig3ks5rjREagaJpZM4MRQ-D
.

Addressed all reviews and added JIRAs for those not addressed, let's integrated this and continue the work on master?

@gustavonalle agreed! Feel free to push..


docs: Update manifest-releaser.md

I use release-please in one of my projects and was at first not able to use the automatic bootstrap functionality. I had to enable the "Allow GitHub Actions to create and approve pull requests" to make it work. I thought it may be a good idea to add this hint to the docs :)
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Appropriate docs were updated (if necessary)

→ closing, not needed. Different reason behind the initial failure on my side :)


Udeler_Setup-v1.12.9_mac-arm64.dmg not working on MacOS Sonoma (Apple Silicon)

Udeler | Udemy Course Downloader
1.12.9
Account Type?
Personal
Steps to reproduce
Steps to reproduce:

Download Udeler_Setup-v1.12.9_mac-arm64.dmg
Attempt to open the file
MacOS indicates the file is damaged and moves it to the Trash

✔ Expected Behavior
The application should open and function correctly without indicating that the file is damaged.
🔍 Additional context
OS: MacOS Sonoma
Processor: Apple Silicon
Note: I had to install a previous version (Udeler_Setup-v1.12.7_mac-x64.dmg) which worked fine.

Hello, the installation works fine and the application does not open? Or installation didn't work?

Hello,
The installation process itself works fine: I can open the DMG file, drag the app to the Applications folder, and that completes without any issues. However, when I try to open the application, I receive an error indicating that the file is damaged and it is moved to the Trash.
t seems likely that there is a problem with the new "Universal" version compiled for the first time. The Udeler_Setup-v1.12.7_mac-x64.dmg version for Intel processors works, but the new version Udeler_Setup-v1.12.9_mac-arm64.dmg for Apple Silicon does not.

same issue in both .zip and dmg, using Mackbook M3

Solução alternativa (no meu M1 Sonoma 14.5):
xattr -c /Applications/Udeler.app

Então eu posso executar o aplicativo Udeler sem personalizar "Segurança do sistema / privacidade".
Btw, em outra máquina (Mac Intel), eu só posso executar 1.12.7 porque há apenas a versão 1.12.9 para "arm64". Gostaria de saber por que não há lançamento "Mac_x64" para 1.12.9?

There was a failure in publishing this, a new one will be released in a few days

New version available, check.


VPP001: Error: tool.ruff.lint cannot be validated by any definition

See:
https://learn.scientific-python.org/development/guides/repo-review/?repo=pypa%2Fsetuptools_scm&branch=main
The error message is unclear, I think the failure originates here:
[tool.ruff.lint.isort]
force-single-line = true
from-first = false
lines-between-types = 1
order-by-type = true

Are one of those fairly new? We probably need to bump

None of these settings is very recent, the most recent is from-first from 2023 (https://github.com/astral-sh/ruff/pull/8663).
In the error message, the isort key is almost empty:
    'isort':
      at least one of the following:
        - {}
        - {type: null}

Is that expected?

Hard to check on my phone, is it in here: https://json.schemastore.org/ruff.json

It points to the IsortOptions definitions:

It's mad about
lint.select = ["E", "F", "B", "U", "YTT", "C", "DTZ", "PYI", "PT", "I", "FURB", "RUF"]

I think because it has preview only selections in it.

The issue is "U" is not a valid code. "UP" is the correct code. See https://github.com/pypa/setuptools_scm/pull/1064.

What got me confused is that there were 2 error messages for the same issue;

RF103: pyupgrade must be selected. Must select the pyupgrade UP checks.
VPP001: Error: tool.ruff.lint cannot be validated by any definition

The error message could be more helpful (perhaps show the actual invalid code).

For validation, that's handled by validate-pyproject, maybe the error message can be improved there (it's from fastjsonshema). For our end (sp-repo-review, that is), RF103: pyupgrade must be selected.

Because RF103 had already been raised about the UP typo, I was misled into looking elsewhere for the VPP001 cause.
The same root cause should not result into different error messages, especially without enough details to clearly identify the root cause (at least a line number).


How to right clean input?

vue-autosuggest 2.0.4:
node 12.13.0:
npm (or yarn) 6.13.0:

What you did:
I want to create a method by which cleaning input (v-model)
selectSection(data) {       if (data) {         this.currentSuggestValue = '  ';       }     }
What happened:
This code cleared input, but not rendering placeholder (empty).
Problem description:
How to right clean input?

@Sendoo assuming you have v-model="currentSuggestionValue' then any reason you are not simply clearing it all the way? e.g.
- this.currentSuggestValue = ' '
+ this.currentSuggestValue = null

@Sendoo assuming you have v-model="currentSuggestionValue' then any reason you are not simply clearing it all the way? e.g.
- this.currentSuggestValue = ' '
+ this.currentSuggestValue = null

Since this is a text field, an error will be shown with null.

I deleted props get-suggestion-value and the previous cleaning worked as it should!

I deleted props get-suggestion-value and the previous cleaning worked as it should!


Website: editing an existing obs and mentioning a user doesn't generate a notification

https://forum.inaturalist.org/t/tagged-users-in-notes-arent-notified/30236

On the website, edit an exsiting observation.
In the Notes section, mention another user, eg @tiwane
Save observation
No notification is generated

Doing this on both iOS and Android apps generates a notification

Working now, not sure why it wasn't earlier.

OK, here's set of steps I could replicate the bug with.

Add a photo in web uploader. Make observation obscured and captive/cultivated and include test in the Notes section. ID as Canis familiaris.
Submit observation.
Right after it's uploaded, Edit it in the website. In the notes section, hit return twice and mention another user
Save changes
No notification is generated for the user who's mentioned


Add rootdisk size on compute offering

Description
This PR allows configuring a Service Offering with root disk size.
PR Allow to configure root disk size via Service Offering (disk offering of type Service). #4341 allows enforcing VM Root disk size accordingly to its Service Offering.
NOTE: Once PR https://github.com/apache/cloudstack/pull/4341 gets merged, the code of this PR will "work" with the new parameter at the API
How Has This Been Tested?

Create Service offering via UI with rootdisk (CloudStack from commit https://github.com/apache/cloudstack/pull/4341/commits/4f501f0624a44fe2414835f17f210bf977f08846)
Assert that the offering has indeed the root disk size configured (same test as in https://github.com/apache/cloudstack/pull/4341)

Screenshots:

Empty:

Value not supported:

Value for Root disk size supported:

@blueorangutan package

@GabrielBrascher a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/770 (JID-3542)

@blueorangutan package

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/770 (JID-3547)


Send network disconnect requests directly to worker engines

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "network_disconnecting" git@github.com:wsong/swarm.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

There are two parts to this change:

Always send network disconnect requests to their associated container's
engine, rather than a random engine. This is necessary in Swarm mode because
only the engine with the associated container knows about the container-network
connection, rather than pre-Swarm mode where all engines shared cluster state.
Don't translate network names to network IDs before forwarding network
disconnect requests. This is necessary because containers created with network
names in their configs don't map these names to network IDs until they get
started for the first time; thus, network disconnect requests will fail for
these containers if you try to specify a network by ID since the container's
engine won't know about the network ID.

These changes are necessary for Swarm to work when Swarm mode is enabled.

Always send network disconnect requests to their associated container's
engine, rather than a random engine.

This was done on purpose to allow disconnect from a live node so a dead engine will not block disconnect.
https://github.com/docker/swarm/commit/5347098defaf4671205c1f2317d83b0f18b39a59

Updated the PR to try a random engine if we can't reach the network's associated engine.

Refactored a bit to use the Docker engine API instead of just proxying HTTP requests.

Addressed comments.

LGTM


AWS Lambda authorization header isn't generating properly.

Title: AWS Lambda authorization header isn't generating properly
Description:
I tried to invoke a AWS Lambda function  with envoy AWS lambda filter and AWS Request Signing filter. I passed the Access token and Secret key in docker environment. But when I try to send request to the aws lambda it shows following error;

"message":"'AWS4-HMAC-SHA256' not a valid key=value pair (missing equal-sign) in Authorization header:

and I noticed that the authorization header was generated twice in the request like this.

AWS4-HMAC-SHA256 Credential=AK**************/20221026/us-east-1/lambda/aws4_request, SignedHeaders=accept;accept-encoding;accept-language;host;sec-fetch-dest;sec-fetch-mode;sec-fetch-site;sec-fetch-user;upgrade-insecure-requests;user-agent;x-amz-content-sha256;x-amz-date;x-request-id, Signature=0fb5eb87fb7e9***********************,AWS4-HMAC-SHA256 Credential=AK******************/20221026/us-east-1/lambda/aws4_request, SignedHeaders=accept;accept-encoding;accept-language;authorization;content-length;content-type;host;sec-fetch-dest;sec-fetch-mode;sec-fetch-site;sec-fetch-user;upgrade-insecure-requests;user-agent;x-amz-content-sha256;x-amz-date;x-amz-invocation-type;x-request-id, Signature=4666a70c***************************************

Config:
admin:
  access_log_path: /tmp/admin_access.log
  address:
    socket_address: { address: <IP_ADDRESS>, port_value: 9902 }

static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address: { address: <IP_ADDRESS>, port_value: 10000 }
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_http
          access_log:
          - name: router_access_log
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.access_loggers.file.v3.FileAccessLog
              path: /tmp/access.log
              format: '"%REQ(:METHOD)% %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% %PROTOCOL%" %RESPONSE_CODE% %RESPONSE_FLAGS% %REQUEST_HEADERS_BYTES% %BYTES_RECEIVED% %BYTES_SENT% %UPSTREAM_HEADER_BYTES_SENT% %DURATION%%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)% ""%REQ(X-FORWARDED-FOR)%" "%REQ(USER-AGENT)%""%REQ(X-REQUEST-ID)%" "%REQ(:AUTHORITY)%" "%UPSTREAM_HOST%"\n'
          codec_type: AUTO
          route_config:
            name: local_route
            virtual_hosts:
            - name: local_service
              domains: ["*"]
              routes:
              - match: { prefix: "/" }
                route: { cluster: lambda_egress_gateway }
          http_filters:
          - name: envoy.filters.http.aws_request_signing
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning
              service_name: lambda
              region: us-east-1
              host_rewrite: lambda.us-east-1.amazonaws.com
              use_unsigned_payload: false
              match_excluded_headers:
              - prefix: x-envoy
              - prefix: x-forwarded
              - exact: x-amzn-trace-id
          - name: envoy.filters.http.aws_lambda
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.aws_lambda.v3.Config
              arn: "arn:aws:lambda:us-east-1:*****************:function:************"
              payload_passthrough: false
          - name: envoy.filters.http.router
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
  clusters:
  - name: lambda_egress_gateway
    connect_timeout: 10s
    type: LOGICAL_DNS
    dns_lookup_family: V4_ONLY
    lb_policy: ROUND_ROBIN
    metadata:
      filter_metadata:
        com.amazonaws.lambda:
          egress_gateway: true
    load_assignment:
      cluster_name: lambda_egress_gateway
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: lambda.us-east-1.amazonaws.com
                port_value: 443
    transport_socket:
      name: envoy.transport_sockets.tls
      typed_config:
        "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
        sni: "*.amazonaws.com"

Logs:
envoytest-envoy-1  | [2022-10-27 06:53:10.519][16][debug][conn_handler] [source/server/active_tcp_listener.cc:147] [C5] new connection from <IP_ADDRESS>:46378
envoytest-envoy-1  | [2022-10-27 06:53:10.519][16][trace][connection] [source/common/network/connection_impl.cc:563] [C5] socket event: 2
envoytest-envoy-1  | [2022-10-27 06:53:10.519][16][trace][connection] [source/common/network/connection_impl.cc:674] [C5] write ready
envoytest-envoy-1  | [2022-10-27 06:53:10.519][16][trace][connection] [source/common/network/connection_impl.cc:563] [C5] socket event: 3
envoytest-envoy-1  | [2022-10-27 06:53:10.519][16][trace][connection] [source/common/network/connection_impl.cc:674] [C5] write ready
envoytest-envoy-1  | [2022-10-27 06:53:10.519][16][trace][connection] [source/common/network/connection_impl.cc:603] [C5] read ready. dispatch_buffered_data=0
envoytest-envoy-1  | [2022-10-27 06:53:10.519][16][trace][connection] [source/common/network/raw_buffer_socket.cc:24] [C5] read returns: 123
envoytest-envoy-1  | [2022-10-27 06:53:10.519][16][trace][connection] [source/common/network/raw_buffer_socket.cc:38] [C5] read error: Resource temporarily unavailable
envoytest-envoy-1  | [2022-10-27 06:53:10.519][16][debug][connection] [./source/common/network/connection_impl.h:92] [C5] current connecting state: false
envoytest-envoy-1  | [2022-10-27 06:53:10.520][16][debug][aws] [source/extensions/common/aws/credentials_provider_impl.cc:43] Getting AWS credentials from the environment
envoytest-envoy-1  | [2022-10-27 06:53:10.520][16][debug][aws] [source/extensions/common/aws/credentials_provider_impl.cc:56] Found following AWS credentials in the environment: AWS_ACCESS_KEY_ID=AKI********************************** AWS_SECRET_ACCESS_KEY=*****, AWS_SESSION_TOKEN=
envoytest-envoy-1  | [2022-10-27 06:53:10.520][16][debug][aws] [source/extensions/common/aws/signer_impl.cc:64] Canonical request:
envoytest-envoy-1  | POST
envoytest-envoy-1  | /addressCheck
envoytest-envoy-1  |
envoytest-envoy-1  | accept:*/*
envoytest-envoy-1  | content-type:application/json
envoytest-envoy-1  | host:lambda.us-east-1.amazonaws.com
envoytest-envoy-1  | user-agent:curl/7.68.0
envoytest-envoy-1  | x-amz-content-sha256:e3b0c44298fc1c149afbf4c*********************************************
envoytest-envoy-1  | x-amz-date:20221027T065300Z
envoytest-envoy-1  | x-request-id:7d25e420-3475-4cd5-8363-064642ad2c20
envoytest-envoy-1  |
envoytest-envoy-1  | accept;content-type;host;user-agent;x-amz-content-sha256;x-amz-date;x-request-id
envoytest-envoy-1  | e3b0c4429**********************************************************
envoytest-envoy-1  | [2022-10-27 06:53:10.520][16][debug][aws] [source/extensions/common/aws/signer_impl.cc:68] String to sign:
envoytest-envoy-1  | AWS4-HMAC-SHA256
envoytest-envoy-1  | 20221027T065300Z
envoytest-envoy-1  | 20221027/us-east-1/lambda/aws4_request
envoytest-envoy-1  | 6da0feaf89be7b2ba9**********************************************
envoytest-envoy-1  | [2022-10-27 06:53:10.520][16][debug][aws] [source/extensions/common/aws/signer_impl.cc:75] Signing request with: AWS4-HMAC-SHA256 Credential=AKI*************************/20221027/us-east-1/lambda/aws4_request, SignedHeaders=accept;content-type;host;user-agent;x-amz-content-sha256;x-amz-date;x-request-id, Signature=de7c3a**************************************************
envoytest-envoy-1  | [2022-10-27 06:53:10.520][16][debug][aws] [source/extensions/common/aws/credentials_provider_impl.cc:43] Getting AWS credentials from the environment
envoytest-envoy-1  | [2022-10-27 06:53:10.520][16][debug][aws] [source/extensions/common/aws/credentials_provider_impl.cc:56] Found following AWS credentials in the environment: AWS_ACCESS_KEY_ID=AKI****************************, AWS_SECRET_ACCESS_KEY=*****, AWS_SESSION_TOKEN=
envoytest-envoy-1  | [2022-10-27 06:53:10.520][16][debug][aws] [source/extensions/common/aws/signer_impl.cc:64] Canonical request:
envoytest-envoy-1  | POST
envoytest-envoy-1  | /2015-03-31/functions/arn%3Aaws%3Alambda%3Aus-east-1%3A825678434177%3Afunction%3AaddressCheck/invocations
envoytest-envoy-1  |
envoytest-envoy-1  | accept:*/*
envoytest-envoy-1  | authorization:AWS4-HMAC-SHA256 Credential=AKI*********************************20221027/us-east-1/lambda/aws4_request, SignedHeaders=accept;content-type;host;user-agent;x-amz-content-sha256;x-amz-date;x-request-id, Signature=de7c3a3b*******************************************************
envoytest-envoy-1  | content-length:678
envoytest-envoy-1  | content-type:application/json
envoytest-envoy-1  | host:lambda.us-east-1.amazonaws.com
envoytest-envoy-1  | user-agent:curl/7.68.0
envoytest-envoy-1  | x-amz-content-sha256:e7e783***************************************************
envoytest-envoy-1  | x-amz-date:20221027T065300Z,20221027T065300Z
envoytest-envoy-1  | x-amz-invocation-type:RequestResponse
envoytest-envoy-1  | x-request-id:7d25e42***********************************
envoytest-envoy-1  |
envoytest-envoy-1  | accept;authorization;content-length;content-type;host;user-agent;x-amz-content-sha256;x-amz-date;x-amz-invocation-type;x-request-id
envoytest-envoy-1  | e7e78*****************************************************
envoytest-envoy-1  | [2022-10-27 06:53:10.520][16][debug][aws] [source/extensions/common/aws/signer_impl.cc:68] String to sign:
envoytest-envoy-1  | AWS4-HMAC-SHA256
envoytest-envoy-1  | 20221027T065300Z
envoytest-envoy-1  | 20221027/us-east-1/lambda/aws4_request
envoytest-envoy-1  | 0676f34e4c22f947e****************************
envoytest-envoy-1  | [2022-10-27 06:53:10.520][16][debug][aws] [source/extensions/common/aws/signer_impl.cc:75] Signing request with: AWS4-HMAC-SHA256 Credential=AKI*******************/20221027/us-east-1/lambda/aws4_request, SignedHeaders=accept;authorization;content-length;content-type;host;user-agent;x-amz-content-sha256;x-amz-date;x-amz-invocation-type;x-request-id, Signature=7b81***********************************************************
envoytest-envoy-1  | [2022-10-27 06:53:10.520][16][debug][connection] [./source/common/network/connection_impl.h:92] [C7] current connecting state: true
envoytest-envoy-1  | [2022-10-27 06:53:10.520][16][debug][client] [source/common/http/codec_client.cc:57] [C6] connecting
envoytest-envoy-1  | [2022-10-27 06:53:10.520][16][debug][connection] [source/common/network/connection_impl.cc:924] [C7] connecting to <IP_ADDRESS>:443
envoytest-envoy-1  | [2022-10-27 06:53:10.520][16][debug][connection] [source/common/network/connection_impl.cc:943] [C7] connection in progress
envoytest-envoy-1  | [2022-10-27 06:53:10.764][16][trace][connection] [source/common/network/connection_impl.cc:563] [C7] socket event: 2
envoytest-envoy-1  | [2022-10-27 06:53:10.764][16][trace][connection] [source/common/network/connection_impl.cc:674] [C7] write ready
envoytest-envoy-1  | [2022-10-27 06:53:10.764][16][debug][connection] [source/common/network/connection_impl.cc:683] [C7] connected
envoytest-envoy-1  | [2022-10-27 06:53:10.764][16][trace][connection] [source/extensions/transport_sockets/tls/ssl_handshaker.cc:93] [C7] ssl error occurred while read: WANT_READ
envoytest-envoy-1  | [2022-10-27 06:53:10.814][16][debug][connection] [source/common/network/connection_impl.cc:924] [C8] connecting to <IP_ADDRESS>:443
envoytest-envoy-1  | [2022-10-27 06:53:10.814][16][debug][connection] [source/common/network/connection_impl.cc:943] [C8] connection in progress
envoytest-envoy-1  | [2022-10-27 06:53:11.012][16][trace][connection] [source/common/network/connection_impl.cc:563] [C7] socket event: 3
envoytest-envoy-1  | [2022-10-27 06:53:11.012][16][trace][connection] [source/common/network/connection_impl.cc:674] [C7] write ready
envoytest-envoy-1  | [2022-10-27 06:53:11.012][16][trace][connection] [source/extensions/transport_sockets/tls/ssl_handshaker.cc:93] [C7] ssl error occurred while read: WANT_READ
envoytest-envoy-1  | [2022-10-27 06:53:11.012][16][trace][connection] [source/common/network/connection_impl.cc:603] [C7] read ready. dispatch_buffered_data=0
envoytest-envoy-1  | [2022-10-27 06:53:11.012][16][trace][connection] [source/extensions/transport_sockets/tls/ssl_handshaker.cc:93] [C7] ssl error occurred while read: WANT_READ
envoytest-envoy-1  | [2022-10-27 06:53:11.013][16][trace][connection] [source/common/network/connection_impl.cc:563] [C7] socket event: 2
envoytest-envoy-1  | [2022-10-27 06:53:11.013][16][trace][connection] [source/common/network/connection_impl.cc:674] [C7] write ready
envoytest-envoy-1  | [2022-10-27 06:53:11.013][16][trace][connection] [source/extensions/transport_sockets/tls/ssl_handshaker.cc:93] [C7] ssl error occurred while read: WANT_READ
envoytest-envoy-1  | [2022-10-27 06:53:11.050][16][trace][connection] [source/common/network/connection_impl.cc:563] [C8] socket event: 2
envoytest-envoy-1  | [2022-10-27 06:53:11.050][16][trace][connection] [source/common/network/connection_impl.cc:674] [C8] write ready
envoytest-envoy-1  | [2022-10-27 06:53:11.050][16][debug][connection] [source/common/network/connection_impl.cc:683] [C8] connected
envoytest-envoy-1  | [2022-10-27 06:53:11.050][16][trace][connection] [source/extensions/transport_sockets/tls/ssl_handshaker.cc:93] [C8] ssl error occurred while read: WANT_READ
envoytest-envoy-1  | [2022-10-27 06:53:11.120][16][debug][connection] [source/common/network/connection_impl.cc:924] [C9] connecting to <IP_ADDRESS>:443
envoytest-envoy-1  | [2022-10-27 06:53:11.120][16][debug][connection] [source/common/network/connection_impl.cc:943] [C9] connection in progress
envoytest-envoy-1  | [2022-10-27 06:53:11.258][16][trace][connection] [source/common/network/connection_impl.cc:563] [C7] socket event: 3
envoytest-envoy-1  | [2022-10-27 06:53:11.258][16][trace][connection] [source/common/network/connection_impl.cc:674] [C7] write ready
envoytest-envoy-1  | [2022-10-27 06:53:11.258][16][trace][connection] [source/common/network/connection_impl.cc:418] [C7] raising connection event 2
envoytest-envoy-1  | [2022-10-27 06:53:11.258][16][debug][connection] [source/common/network/connection_impl.cc:139] [C8] closing data_to_write=0 type=1
envoytest-envoy-1  | [2022-10-27 06:53:11.258][16][debug][connection] [source/common/network/connection_impl.cc:250] [C8] closing socket: 1
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][trace][connection] [source/common/network/connection_impl.cc:418] [C8] raising connection event 1
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][debug][connection] [source/common/network/connection_impl.cc:139] [C9] closing data_to_write=0 type=1
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][debug][connection] [source/common/network/connection_impl.cc:250] [C9] closing socket: 1
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][trace][connection] [source/common/network/connection_impl.cc:418] [C9] raising connection event 1
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][debug][client] [source/common/http/codec_client.cc:88] [C6] connected
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][trace][connection] [source/common/network/connection_impl.cc:478] [C7] writing 1131 bytes, end_stream false
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][trace][connection] [source/common/network/connection_impl.cc:478] [C7] writing 678 bytes, end_stream false
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][debug][client] [source/common/http/codec_client.cc:139] [C6] encode complete
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][trace][connection] [source/common/network/connection_impl.cc:674] [C7] write ready
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][trace][connection] [source/extensions/transport_sockets/tls/ssl_socket.cc:268] [C7] ssl write returns: 1809
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][trace][connection] [source/common/network/connection_impl.cc:603] [C7] read ready. dispatch_buffered_data=0
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][trace][connection] [source/extensions/transport_sockets/tls/ssl_socket.cc:87] [C7] ssl read returns: -1
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][trace][connection] [source/extensions/transport_sockets/tls/ssl_socket.cc:127] [C7] ssl error occurred while read: WANT_READ
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][trace][connection] [source/extensions/transport_sockets/tls/ssl_socket.cc:163] [C7] ssl read 0 bytes
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][trace][connection] [source/common/network/connection_impl.cc:563] [C7] socket event: 2
envoytest-envoy-1  | [2022-10-27 06:53:11.259][16][trace][connection] [source/common/network/connection_impl.cc:674] [C7] write ready
envoytest-envoy-1  | [2022-10-27 06:53:11.510][16][trace][connection] [source/common/network/connection_impl.cc:563] [C7] socket event: 3
envoytest-envoy-1  | [2022-10-27 06:53:11.510][16][trace][connection] [source/common/network/connection_impl.cc:674] [C7] write ready
envoytest-envoy-1  | [2022-10-27 06:53:11.510][16][trace][connection] [source/common/network/connection_impl.cc:603] [C7] read ready. dispatch_buffered_data=0
envoytest-envoy-1  | [2022-10-27 06:53:11.510][16][trace][connection] [source/extensions/transport_sockets/tls/ssl_socket.cc:87] [C7] ssl read returns: 923
envoytest-envoy-1  | [2022-10-27 06:53:11.510][16][trace][connection] [source/extensions/transport_sockets/tls/ssl_socket.cc:87] [C7] ssl read returns: -1
envoytest-envoy-1  | [2022-10-27 06:53:11.510][16][trace][connection] [source/extensions/transport_sockets/tls/ssl_socket.cc:127] [C7] ssl error occurred while read: WANT_READ
envoytest-envoy-1  | [2022-10-27 06:53:11.510][16][trace][connection] [source/extensions/transport_sockets/tls/ssl_socket.cc:163] [C7] ssl read 923 bytes
envoytest-envoy-1  | [2022-10-27 06:53:11.510][16][trace][connection] [source/common/network/connection_impl.cc:478] [C5] writing 271 bytes, end_stream false
envoytest-envoy-1  | [2022-10-27 06:53:11.510][16][trace][connection] [source/common/network/connection_impl.cc:478] [C5] writing 679 bytes, end_stream false
envoytest-envoy-1  | [2022-10-27 06:53:11.510][16][debug][client] [source/common/http/codec_client.cc:126] [C6] response complete
envoytest-envoy-1  | [2022-10-27 06:53:11.510][16][trace][connection] [source/common/network/connection_impl.cc:563] [C5] socket event: 2
envoytest-envoy-1  | [2022-10-27 06:53:11.510][16][trace][connection] [source/common/network/connection_impl.cc:674] [C5] write ready
envoytest-envoy-1  | [2022-10-27 06:53:11.510][16][trace][connection] [source/common/network/raw_buffer_socket.cc:67] [C5] write returns: 950
envoytest-envoy-1  | [2022-10-27 06:53:11.511][16][trace][connection] [source/common/network/connection_impl.cc:563] [C5] socket event: 3
envoytest-envoy-1  | [2022-10-27 06:53:11.511][16][trace][connection] [source/common/network/connection_impl.cc:674] [C5] write ready
envoytest-envoy-1  | [2022-10-27 06:53:11.511][16][trace][connection] [source/common/network/connection_impl.cc:603] [C5] read ready. dispatch_buffered_data=0
envoytest-envoy-1  | [2022-10-27 06:53:11.511][16][trace][connection] [source/common/network/raw_buffer_socket.cc:24] [C5] read returns: 0
envoytest-envoy-1  | [2022-10-27 06:53:11.511][16][debug][connection] [source/common/network/connection_impl.cc:651] [C5] remote close
envoytest-envoy-1  | [2022-10-27 06:53:11.511][16][debug][connection] [source/common/network/connection_impl.cc:250] [C5] closing socket: 0
envoytest-envoy-1  | [2022-10-27 06:53:11.511][16][trace][connection] [source/common/network/connection_impl.cc:418] [C5] raising connection event 0
envoytest-envoy-1  | [2022-10-27 06:53:11.511][16][trace][conn_handler] [source/server/active_stream_listener_base.cc:111] [C5] connection on event 0
envoytest-envoy-1  | [2022-10-27 06:53:11.511][16][debug][conn_handler] [source/server/active_stream_listener_base.cc:120] [C5] adding to cleanup list
envoytest-envoy-1  | [2022-10-27 06:53:13.921][1][debug][upstream] [source/common/upstream/logical_dns_cluster.cc:108] starting async DNS resolution for lambda.us-east-1.amazonaws.com
envoytest-envoy-1  | [2022-10-27 06:53:13.934][1][debug][upstream] [source/common/upstream/logical_dns_cluster.cc:116] async DNS resolution complete for lambda.us-east-1.amazonaws.com
envoytest-envoy-1  | [2022-10-27 06:53:13.934][1][debug][upstream] [source/common/upstream/logical_dns_cluster.cc:167] DNS refresh rate reset for lambda.us-east-1.amazonaws.com, refresh rate 5000 ms

cc @marcomagdy @tonya11en

I guess if we are making call only to AWS Lambda then no need to include the aws_request_signing configuration?

You don't need the aws_request_signing filter.
The Lambda filter signs the request independently.
https://github.com/envoyproxy/envoy/blob/362e415045e1c8b7391fcb1a21f8c6003de3e8e0/source/extensions/filters/http/aws_lambda/aws_lambda_filter.cc#L174


Might be UI issue

I changed the concurrency value to be picked up from env. So the picked up value for the env is correct.
But  In the UI under concurrency, it still shows 10 instead of the provided value.

I'm missing context. Can you provide a minimal set of steps (with code snippets) to reproduce that? Did you restart the app that serves UI?


Add assertion for missing fixed source

As in #1467 I also tough here it would start to make sense to test the applied the fix its as it will ensure the quality in many different cases and scenarios.
So when there is 1 or more fix its we expect a fixed source.
What do you think. Is it worth it?
Just before I continue with the rest of the 195 failing test cases 🫣

As with my comment on the other PR, I think that it’s a great change and allows everybody to explicitly write down their expectation. I certainly remember a bug or two that would have been caught if we had written down the fixed source straight away.

@swift-ci please test

Wow, that’s a big PR. And thanks for catching all those incorrect formattings. I think most of the space-related issues should be fixed in the next couple of days by my changes to BasicFormat. All the other ones look like real problems to me. Shows that requiring you to specify fixedSource does provide value 🤩 .

Yes it gives a lot 🙌

What do you think about the following? We wait for my BasicFormat changes to get in and see which tests are still odd after that. For all of those, you file issues on GitHub (and feel free to mark them as “good first issue” if you think they’ll be easy to fix) and reference those issues as TODOs in the test cases.

Let's wait yes, there will 100% be cases that are fixed now.
I will go trough the other files and open issues 😁

@ahoppen it's not rebased on latest main and all swift parser tests passes locally.

@swift-ci please test

@swift-ci please test windows


add AutoCompleteTextField

Added AutoCompleteTextField.
Use Tab key to input the first suggestion
Please comment if you think the functionality is unnecessary/simple tab without popup is enough/design of key (tab pageup pagedown) is not user-friendly.....

I think we need to implement autocomplete feature from scratch because using personal library (AutoCompleteTextField) with no explicit license is not allowed according to Prof. I have finished one and I will pr it tonight.

Okay sure, thank you. Btw just a suggestion, would really appreciate it if you could say in advance about what group feature you are implementing to prevent unnecessary workload.

Sorry for the miscommunication. I agree that the workflow can be improved if we submit issues before taking on a task. Thank you :-)


Makefile: add a distclean target

This patch prevents the clean target from removing node_modules and
adds a distclean target instead.
Fixes #162.

Thanks @stephenmathieson!

np


Update all the dependencies

Best to review this commit-by-commit in Reviewable.

Dependency on Etcd server was becoming pretty gross. Rip it out, in favor of spawning off an etcd subprocess instead that uses the new testing.Main API. Gazette depends only on the Etcd client now.
Update RocksDB to 6.7.3 (and fix a bug in ArenaIterator).

This change is

Thanks, updated changelog with this as well as some other notable updates not already covered.


Bootable container ISO installer fails to initialize dbus.socket

Hello, trying the build the following bootc:
FROM quay.io/centos-bootc/centos-bootc-dev:stream9

RUN dnf -y install httpd && \
    systemctl enable httpd && \
    mv /var/www /usr/share/www && \
    sed -ie 's,/var/www,/usr/share/www,' /etc/httpd/conf/httpd.conf && \
    touch /HTTPD_DEMO

RUN rm /usr/share/httpd/noindex -rf
COPY index.html /usr/share/www/html
EXPOSE 80

The resulting ISO can be installed locally via removable media, however, it fails to initialize dbus, thus network manager and the network is offline. That is not a problem for removable media installation, it is for PXE installation.

Fwiw, I tried to debug this with uay.io/centos-bootc/centos-bootc:stream9 and AFAICT dbus.socket is not failing there, trying -dev now.

Sorry, I cannot reproduce this, here is what I did:
$ $ cat Containerfile
FROM quay.io/centos-bootc/centos-bootc-dev:stream9

RUN dnf -y install httpd && \
    systemctl enable httpd && \
    mv /var/www /usr/share/www && \
    sed -ie 's,/var/www,/usr/share/www,' /etc/httpd/conf/httpd.conf && \
    touch /HTTPD_DEMO

RUN rm /usr/share/httpd/noindex -rf
COPY index.html /usr/share/www/html
EXPOSE 80
$ touch index.html
$ sudo podman build -f Containerfile  -t image-issue391
$ mkdir output
$ sudo podman run --rm -it --privileged --pull=newer  --security-opt label=type:unconfined_t -v $(pwd)/output:/output  quay.io/centos-bootc/bootc-image-builder:latest --type iso --local localhost/image-issue391
...
$ cd output/bootiso
$ sudo truncate -s 10G test-disk.img
$ kvm -cpu host -m 1500 -snapshot -cdrom install.iso  -boot d test-disk.img
...

in the booted image I did "sendkey ctrl-alt-f2" and ran "systemctl --failed" and "systemctl status dbus.socket" and got no errors. When running "nmcli" in the booted iso (while it was installing) I saw that it was connected on the ethernet port.
What am I missing :) ?

, however, it fails to initialize dbus

Do you have /var/run as a physical directory?  https://github.com/CentOS/centos-bootc/issues/140#issuecomment-1946996913

@cgwalters is a symlink to ../run

Correction, dbus.socket is not failing, it does not appear to be enabled.

I just noticed I was using -dev trying again with quay.io/centos-bootc/centos-bootc:stream9 instead but getting.
xorriso : FAILURE : Image size 1095584s exceeds free space on media 785896s

So tried to build a clean (base) Fedora ELN, the same result when I PXE boot it.

So uay.io/centos-bootc/centos-bootc:stream9 does boot up correctly, however hitting something different. Need to figure that one out:

Ok increased VM size to 10GB RAM and it installed, after boot it fails with:

But I am getting there. Now I will try to build my own container of top of the correct base image.

Looks like I was missing this in my KS:
%post
bootc switch --mutate-in-place --transport registry quay.io/lzapletal/fedora-eln-bootc-httpd-test
%end

And it works now. So the root cause was I was using -dev version. I am closing, if you run into this just reopen. Thanks for help.

Looks like I was missing this in my KS:
%post
bootc switch --mutate-in-place --transport registry quay.io/lzapletal/fedora-eln-bootc-httpd-test
%end

This should be added automatically by bootc-image-builder when building an ISO.  How was it missing?  Were you replacing the ks with your own?

Yeah I am doing PXE installation. Still I am running into an issue when booting the system - bootc is unable to find a commit or something. Not sure why it does not work with my KS: https://gist.github.com/lzap/3ade88a6f8d63ff98af4d0e7cd670059


Andrew Team Info

Please add your name and github username to the "Meet the team" section in the readme.md.
Follow the same format of the first name.

Working on it.


Support for new HTTP/2 provider API

Apple announced a new provider API for APNs based on HTTP/2 at WWDC 2015. Currently, there is no written documentation, but it should be available in the coming weeks.
See this video starting at 20:50 for an introduction to the new API: https://developer.apple.com/videos/wwdc/2015/?id=720
With the new APIs there is no need for a separate feedback service. There will be no need to keep the existing APNS provider API as the new API applies to older devices. The video mentions some other changes, such as 4K payloads and ~100-character device tokens.
Also see the slides starting at page 98: http://devstreaming.apple.com/videos/wwdc/2015/720xwbi9nl/720/720_whats_new_in_notifications.pdf?dl=1
Do you plan to integrate the new provider API in ApnsPHP?

Just to know: this project is still active?

@delitestudio It depends by you and by other developers that want to contribute... is an open-source project! ;-)

Fair enough :) It was just to ask if there are official development plans or if future developments are left to the community :)

@aDev123 I was joking, yes, we will implement the new provider HTTP/2 APIs as soon as Apple will release the official documentation. We participated at WWDC 2015 in SF and we are very excited to have the new APIs! ;-) Thanks!

That's great, thank you guys for your work!


[Gally]: master <- dev

Automatically created by Git-Ally

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


LinkedIn Post: Improving Developer Productivity with Unikube

https://docs.google.com/document/d/1GiFp9S_l7aXQCXr2Ztmd69VE35-ux0zRaAVv2yq-uIM/edit#
Turning this blogpost into a LinkedIn-Posting for Unikube.
Working title: Improving Developer Productivity with Unikube

@Schille @Truthans let's talk about this in our meeting tomorrow!

Changes are done, please review @Truthans


Max 10 Minimaps appear when collapsed:true

Hi,
When collapsed:false, all of Minimaps appear.
But if collapsed is set to true, then max 10 Minimaps appear, others not.

var layersControl = L.control.layers.minimap(baseLayers, overlays, {
collapsed: true
}).addTo(map);

Thanks.

Minimale are lazy loaded when they appear into view; we need to check why this does not happen with collapsed: true


chore: remove auth variables and react default files

Further cleanup to removes things we don't use. Don't want to confuse people thinking they are still needed.

Removes the old authentication variables we used when we had AAD authentication. I forgot to remove them when we switched to LUIS key auth.  We can always look at older commit to reference how it was done if needed.
Removes the default files that come with new react app.  We don't use the service worker or the logo file.
Moves shared NODE_OPTIONS variable to the shared .env file.

That was a suggestion for the Appveyor customer support folks when our builds were hanging.
From: Matt Mazzola<EMAIL_ADDRESS>Sent: Thursday, January 31, 2019 2:03 PM
To: Microsoft/ConversationLearner-UI<EMAIL_ADDRESS>Cc: Lars Liden<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Microsoft/ConversationLearner-UI] chore: remove auth variables and react default files (#980)
From what I understand the the NODE_OPTIONS only affects the currently running node process.
Developers using our UI aren't running node. They are viewing the website in a browser.
Maybe @LarsLidenhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FLarsLiden&data=02|01|Lars.Liden%40microsoft.com|d3fb75a54137444df4f208d687c7d18b|72f988bf86f141af91ab2d7cd011db47|1|0|636845689620838214&sdata=IbyaCVkUHsSZDuNDP7yTxdzgp28hzAEeJGyW%2BR%2FLg9A%3D&reserved=0 can clarify why this what added, but I'm guess it could only be an issue because of reacts's hot reloading build system. I thought we only saw problems with the SDK running out of memory I can't remember what the issue was with this one.
Sometimes the process would fail with FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory and I think this option prevents that by allowing node to use more memory.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FConversationLearner-UI%2Fpull%2F980%23issuecomment-459523384&data=02|01|Lars.Liden%40microsoft.com|d3fb75a54137444df4f208d687c7d18b|72f988bf86f141af91ab2d7cd011db47|1|0|636845689620848209&sdata=n7IPqvJbaiODBsNBn5R2Ta8FH1SoP%2FMxf08ngxAZ3B4%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGOd5sdTEyLt8Dm6ktuVZEFL05hZgjwJks5vI2f8gaJpZM4ac2I8&data=02|01|Lars.Liden%40microsoft.com|d3fb75a54137444df4f208d687c7d18b|72f988bf86f141af91ab2d7cd011db47|1|0|636845689620848209&sdata=53EEwsHQgoP12pffX0fkNCAvlOhif43f5wmgN%2BeXBFg%3D&reserved=0.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Dynamically created donation location number on website

It would be awesome to have the number of locations in this paragraph (1700) on the website be dynamically created so that it keeps better aligned with the actual number. Some thoughts...

should it be per country total or total number of all donation sites across the globe?
should it be rounded to the nearest hundred or exact number?

=======
How To Donate PPE
Our network of volunteers has created a global map of over 1700+ locations, like hospitals and clinics, where you can donate your masks, gowns, and other PPE.

This will be closed with: https://github.com/findthemasks/findthemasks/pull/607


House cleaning: Move grpc, http, and universal under pkg/api. Make Universal immutable.

General house cleaning PR to move the grpc, http and universal packages under pkg/api.
Makes the shared universal object immutable by callers.
Based on https://github.com/ItalyPaleAle/dapr/pull/97

/ok-to-test

@JoshVanL please fix conflicts and make CI happy, then we can merge it.

@daixiang0 done! Please take  look

I think the file structure is more explicit and helpful now. Thanks for moving it all around 👍🏻

@JoshVanL please resolve the conflicts

@yaron Done.

Note this PR broke the builds with the subtlecrypto tag:
pkg/api/universal/subtlecrypto_subtlecrypto.go:50:5: a.Logger undefined (type *Universal has no field or method Logger, but does have logger)
pkg/api/universal/subtlecrypto_subtlecrypto.go:56:16: a.Resiliency.ComponentOutboundPolicy undefined (type func() "github.com/dapr/dapr/pkg/resiliency".Provider has no field or method ComponentOutboundPolicy)
pkg/api/universal/subtlecrypto_subtlecrypto.go:68:5: a.Logger undefined (type *Universal has no field or method Logger, but does have logger)
pkg/api/universal/subtlecrypto_subtlecrypto.go:94:6: a.Logger undefined (type *Universal has no field or method Logger, but does have logger)
pkg/api/universal/subtlecrypto_subtlecrypto.go:101:6: a.Logger undefined (type *Universal has no field or method Logger, but does have logger)
pkg/api/universal/subtlecrypto_subtlecrypto.go:114:6: a.Logger undefined (type *Universal has no field or method Logger, but does have logger)
pkg/api/universal/subtlecrypto_subtlecrypto.go:138:16: a.Resiliency.ComponentOutboundPolicy undefined (type func() "github.com/dapr/dapr/pkg/resiliency".Provider has no field or method ComponentOutboundPolicy)
pkg/api/universal/subtlecrypto_subtlecrypto.go:152:5: a.Logger undefined (type *Universal has no field or method Logger, but does have logger)
pkg/api/universal/subtlecrypto_subtlecrypto.go:171:16: a.Resiliency.ComponentOutboundPolicy undefined (type func() "github.com/dapr/dapr/pkg/resiliency".Provider has no field or method ComponentOutboundPolicy)
pkg/api/universal/subtlecrypto_subtlecrypto.go:184:5: a.Logger undefined (type *Universal has no field or method Logger, but does have logger)
pkg/api/universal/subtlecrypto_subtlecrypto.go:184:5: too many errors


Added additional needles to the cpu_temp attribute

Description:
Added additional keys in the section that checks for the "cpu_temp" attribute from the Glances API with a fallback to "Core 0" to at least provide some temperature information.
Checklist:

[ Y] The code change is tested and works locally.
[ Y] Local tests pass with tox. Your PR cannot be merged unless tests pass
[ Y] There is no commented out code in this PR.

Hello @shutupflanders,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

302a5152dd6a818190f36acb79d998c31dd6e53a - This commit has something that looks like an email address (martin@flamedevelopment.co.uk). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

On which hardware/architecture does this occur? I though that by now we have covered all available CPU architectures...

I have a gigabyte brix and a Lenovo q180, couldn't tell you the architecture off the top of my head, but in testing it pulled through both, whereas I was getting a blank value on the main release

This should be ordinary hardware (x86_64). Both should expose the temperature through Package id 0.
What do you get if you run?
$ curl http://IP_ADDRESS:61208/api/3/sensors

I get Core 0, Core 1, and one of the other strings depending on which box I run it against, I only get Package 0 on my NUC

I'll drop the full responses in later when I'm at my desk

Here's the response from the sensors endpoint on 3 of my machines that were reporting nothing prior to my changes:
Q180
[
  {
    "key": "label",
    "type": "temperature_core",
    "unit": "C",
    "value": 74,
    "label": "Core 0"
  },
  {
    "key": "label",
    "type": "temperature_core",
    "unit": "C",
    "value": 73,
    "label": "Core 1"
  },
  {
    "key": "label",
    "type": "temperature_core",
    "unit": "C",
    "value": 68,
    "label": "radeon 1"
  }
]

Proxmox server (Ryzen 7)
[
  {
    "key": "label",
    "type": "temperature_core",
    "unit": "C",
    "value": 23,
    "label": "amdgpu 1"
  }
]

Brix (Core 0 fallback needed for this)
[
  {
    "key": "label",
    "type": "temperature_core",
    "unit": "C",
    "value": 26,
    "label": "acpitz 1"
  },
  {
    "key": "label",
    "type": "temperature_core",
    "unit": "C",
    "value": 39,
    "label": "Core 0"
  },
  {
    "key": "label",
    "type": "temperature_core",
    "unit": "C",
    "value": 39,
    "label": "Core 1"
  },
  {
    "key": "label",
    "type": "temperature_core",
    "unit": "C",
    "value": 41,
    "label": "Core 2"
  },
  {
    "key": "label",
    "type": "temperature_core",
    "unit": "C",
    "value": 41,
    "label": "Core 3"
  }
]

If you need any more info, please let me know.

Also, I added both my email accounts to my github, but the cla error hasn't gone away, not sure if that's set to check again or if it's a manual thing I'm supposed to trigger?

Hi @shutupflanders,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

@fabaff can you make a decision what to do with this PR, can we merge, do we require changes or do we not want this change?

@fabaff ?

What should we do here? This is six months old.

I pinged @fabaff on Discord


Revert "chore(i18n): updating translations"

Reverts openedx/tutor-contrib-aspects#829

Thanks for the pull request, @Ian2012! Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.


Problem with  cachedEventIds in the fetchEvents function

I am getting events disappearing when I use the fetchEvents() method to load calendar events.
If I comment out the line the caches the event ids in the fullcalendar.blade.php file, it works as expected.
const fetchEvents = function ({ start, end }, successCallback, failureCallback) {
    @if( $this::canFetchEvents() )
        return $wire.fetchEvents({ start, end }, cachedEventIds)
            .then(events => {
                // Cache fetched events
                //cachedEventIds.push(...events.map(event => event.id)); <--- comment out this line fixes the issue

                return successCallback(events);
            })
            .catch( failureCallback );
    @else
        return successCallback([]);
    @endif
}

I think this is due to the way Fullcalendar calls Event Sources that are a function.
From the Fullcalendar docs:

events (as a function)
...
FullCalendar will call this function whenever it needs new event data. This is triggered when the user clicks prev/next or switches views.

Is this line needed? I am not getting any duplication of events if it is commented out.

hmm, can i see your implementation, please? We need to cache event ids that are returned from the fetchEvents to ignore them in the next fetchEvents call.

Here is my implementation:
public static function getAppointments(Carbon $start, Carbon $end, array $ignorableIds = []): array
{
    $appointments = Appointment::query()
        ->where([
            ['start_at', '>=', $start],
            ['end_at', '<=', $end],
        ])
        ->whereNotIn('id', $ignorableIds)
        ->get();

    return $appointments->map(function ($appointment) {
            return [
                'id' => $appointment->id,
                'title' => $appointment->title,
                'start' => $appointment->start_at,
                'end' => $appointment->end_at,
                'user_id' => $appointment->user_id,
                'client_id' => $appointment->client_id,
                'parent_id' => $appointment->parent_id,
                'location' => $appointment->location,
                'follow_up' => $appointment->follow_up,
                'type' => $appointment->type,
                'status' => $appointment->status,
            ];
        })
        ->toArray();
}

public function getViewData(): array
{
    return static::getAppointments(now()->subMonths(1), now()->addMonths(1));
}

public function fetchEvents(array $fetchInfo, array $ignorableIds): array
{
    $timezone = $this->config('timeZone', config('app.timezone'));

    $start = Carbon::parse($fetchInfo['start'], $timezone);
    $end = Carbon::parse($fetchInfo['end'], $timezone);

    return static::getAppointments($start, $end, $ignorableIds);
}

When I have the ids cached (cachedEventIds.push(...events.map(event => event.id))) and click the next month chevron and go 2 months forward and then back 1 month and then forward again (i.e. July->August->September->August->September), it won't show that months (i.e. September) events anymore.

this is confirmed.
the reason is how FullCalendar handles previously loaded data when using function as eventSources
the issue is whenever FC trigger retrieves, it clears the old data, and when combine with the $ignorableIds in fetch, we lose the current events won't be able to fetch/display the events again.
there are 2 approaches to solve this:

not using $ignorableIds
this is the easiest. just remove the cachedEventIds from blade and $ignorableIds from method param

cache the events data fix in #24
previously I included events data caching but removed by @saade . i forgot to raise this as i forgot about the reasoning behind it. So the purpose of caching the events data is to avoid the short blink of empty calendar when changing to month that is previously loaded (as FC clears all events, including days that span across month view). this cache provides better UX

I further tested and figured that ignorableIds won't bring much benefits and it causes updated event info (if the info can change rather frequent)
so i combine the 2 approaches I mentioned in #25 by removing ignorableIds and implemented event data cache. caching on client side shouldn't be a big concern, or perhaps can have a config to turn it off.
@ashleyhood can you try if it solve your issue


Font size not working?

fontSize doesn't seem to be working?
...

    const PDFhtml = ReactDOMServer.renderToStaticMarkup(

15855

    );

    const PDFDocument = () => (
        <Document title="Title">
            <Page
                size="A4"
            >

                    {PDFhtml.toString()}

            </Page>
        </Document>
    )

...

Renders to:

15855

Now, as far as I can tell from the docs px is not supported unit for react-pdf, so this is possibly the cause? Although I have tried passing a string through the html style, '36pt', which should be supported and rendering the following:

15855

But this doesn't work either. The font size in the document stays base.

Font family are not working according to https://github.com/danomatic/react-pdf-html/issues/27
On the other hand I think these libraries only support pixels as unit. Change 36pt to 36px.

@sanchitos font-family works for me, but there seems to be confusion or a problem with font-family not working if combining italic, bold etc.


Please update to 1.18

Hi there
Love this mod, use it on my family server. Please will you recompile it for 1.18?
Thanks!

I see there is a 1.18 branch, and it compiles fine, but in game it just does nothing :(

Yeah, seems like the latest commit on the 1.18 branch does nothing for me on a 1.18.1 server.
There's nothing logged from commandaliases at all, other than it being in the list of active mods.
Commands that come with the mod, as well as commands configured, don't exist. The config file was also not automatically generated.

Sorry, the 1.18.x/dev branch is has a lot of changes that didn't make it into the 1.17 release. It's still a work in progress. I currently don't have time to work on it at the moment. It will be released when it's ready.

OK, thanks for that info! I went back to the 1.17 branch and made the minimal changes needed to upgrade it to 1.18.1 - here is an experimental build for those that are willing to trust an internet stranger! :)
I've tested that it works fine in my worlds.
https://random.wolfen.za.net/commandaliases-1.18.1-9.0.0.jar

I've added a PR #23 to this repo - so others can review the code changes I made. @FlashyReese perhaps you could release the 1.18.1 version with the old stuff, until the new stuff is ready?

thanks for building and uploading!
COMMAND_REDIRECT is working fine, however COMMAND_REASSIGN is not
when trying to reassign, all it does is break the tab autocomplete. the "reassignTo" does nothing, just gives an error when trying to execute it in game. The original command still works, just with no autocomplete.
removing the reassign from the config and reloading doesn't revert things to normal either. the whole server needs to be stopped and started again. I also notice an error in the console:
[Server thread/ERROR]: Skipping "help", couldn't modify command literal
This is the error when using the example to reassign help to minecraft:help. It only appears on server start, it does not appear when running /commandalias reload.
Also I get errors like [17:49:24] [Server thread/ERROR]: Could not find existing command "home set" because /home was supposed to be reassigned. Despite getting these errors, the aliases still work.
I was trying to get it to work for /home for Essential-Commands, it uses the syntax /home tp (homename) to teleport to homes and I want to make it so you don't have to type tp. redirects for /home set -> /sethome and /home delete -> /delhome work fine, but I obviously can't redirect /home tp -> /home. For now I'm just going to redirect /home tp -> /go, but it would be nice to get COMMAND_REASSIGN to work.
Running 1.18.1
fabric loader 0.12.12
fabric api 0.45.0+1.18

I wish I knew how to fix that, but its beyond my mod skills! I see what you are saying, disconnect the existing command and then you can hook up a new one in that space. I use vanillatweaks.net datapack on my worlds, with their commands like /trigger home set 1 mapped with commandaliases to /home 1 - perhaps a similar approach might work for you?

I wish I knew how to fix that, but its beyond my mod skills! I see what you are saying, disconnect the existing command and then you can hook up a new one in that space. I use vanillatweaks.net datapack on my worlds, with their commands like /trigger home set 1 mapped with commandaliases to /home 1 - perhaps a similar approach might work for you?

You can see https://github.com/FlashyReese/CommandAliases/commit/4ba851620187b9896cf957941810a1ad16d82924 for reference, code is pretty similar.
Sorry, I haven't found the time and motivation for publishing the new changes and updating the wiki.


Error with sample code for custom tooltips

Expected Behavior
Sample code using custom tooltips should not report an error, this tooltips should display normally
Current Behavior
Sample code using custom tooltips gives an error. Error message: Uncaught TypeError: Cannot read property 'opacity' of undefined.
Possible Solution
// plugin.tooltip.js
if (changed && options.custom) {
    options.custom.call(me, me);
}

Steps to Reproduce (for bugs)
https://www.chartjs.org/docs/3.0.0-alpha/configuration/tooltip.html#external-custom-tooltips
Environment

Chart.js version: master branch
Browser name and version: Chrome v80.0
Link to your project: https://www.chartjs.org/docs/3.0.0-alpha/configuration/tooltip.html#external-custom-tooltips

Fixed by https://github.com/chartjs/Chart.js/pull/7240


attach .key to .data, so errors have err.data.key

this helps dealing with dat instance of Error archives

blocks https://github.com/datproject/dat-desktop/issues/400

Codecov Report

Merging #13 into master will increase coverage by 0.08%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #13      +/-   ##
==========================================
+ Coverage    97.1%   97.18%   +0.08%
==========================================
  Files           1        1
  Lines          69       71       +2
==========================================
+ Hits           67       69       +2
  Misses          2        2

Impacted Files
Coverage Δ

index.js
97.18% <100%> (+0.08%)
:arrow_up:

Continue to review full report at Codecov.

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

5.1.0


Fix typo in thrift comment

🤦
Also slightly tweak the wording as we could use either string or int
values in the http health checks.

👓 @spladug


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 871 ms

Resolved: Bofrost.de performance has improved in c4dc89d after 8 minutes.


special 6.3

include autoprovisioning variables only if used
remove resharing option
follow web depreciations, remove unclear configuration examples and outdated default documentation
add activitylog
add activitylog stream to nats deployment example
remove uneeded ocis-config-tmp volume
add option to not use wopi proof keys
generate docs

Description

Related Issue

Fixes <issue_link>

Motivation and Context

How Has This Been Tested?

test environment:
test case 1:
test case 2:
...

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

Checklist:

<!-- or create documentation PR in https://github.com/owncloud/docs-ocis/tree/master/modules/ROOT/pages/deployment/container>
- [ ] Code changes
- [ ] Unit tests added
- [ ] Acceptance tests added
- [ ] Documentation generated (`make docs`) and committed
- [ ] Documentation ticket raised:
- [ ] Documentation PR created:

meanwhile the PRs have been merged so I can get rid to this intermediate state branch


Pop-Up has a wrong z-index on smaller screens

Prerequisites
Please answer the following questions for yourself before submitting an issue.

[x] This is bug in the application 🐛
[x] I am running the latest version
[x] I checked the documentation and found no answer
[x] I checked to make sure that this issue has not already been filed
[x] I'm reporting the issue to the correct repository

Describe the bug
Pop-Up is showing up behind the add task and select buttons
To Reproduce
Steps to reproduce the behavior:

Visit the web-app on a mobile phone
View the version of web on smaller devices through inspect

Expected behavior
Pop-Up should come in front of all components
Current behaviour
Pop-Up is showing up behind the add task and select buttons
Screenshots

Smartphone (please complete the following information):

Device: Techno Pop 2F
OS: Android
Browser: Chrome
Version [e.g. 22]

Hey I can work on this. Please assign it to me

@SauveJeanLuc Kindly assign this to me please


[rust_analyzer] initalizationOptions causing ra_lsp_server an error

Because of how vim json_encode transform vim data into JSON data, the lua value {} which is the default value for init_options is being encoded into an empty JSON array.
But ra_lsp_server expect to receive a JSON map for decoding the init options and emit an error: failed to deserialize config: invalid length 0, expected struct ServerConfig with 12 elements when receiving an empty initializationOptions by vim.lsp.
Hopefully rust-analyzer handle this error by just logging it and sticking with default values, but still the error message appears, which can be actually confusing.

@justinmk you are correct.

Can someone please double check? I still have this issue.

@tuxsoy always need to know exact version of Nvim and this plugin.

@justinmk I'm using the appimage release of neovim (NVIM v0.5.0-363-g31614d3eb) with nvim-lsp commit 42385db. The error message is:
LSP[rust_analyzer] failed to deserialize config: invalid length 0, expected struct ServerConfig with 12 elements

Reverting to commit b4f4b72 does not solve the issue either.
Commenting the following lines fixes the issue for me, so the problem is probably on these lines:
https://github.com/neovim/nvim-lsp/blob/42385dbf6a5eac40da213322fdd3037588eede56/lua/nvim_lsp/configs.lua#L102-L103

OK, I'll check it later.

@KokaKiwi @matu3ba  @tuxsoy
Would you try this branch?

@KokaKiwi @matu3ba @tuxsoy
Would you try this branch?

This removes the error message and shows "LSP[rust_analyzer][Info] workspace loaded, 12 rust packages".
Did try on the old and current nightly neovim appimage.

I think neovim/neovim#11864 will solve this.

I manually patched the last nightly (v0.5.0-372-g68de6b17b) with the 5 lines (here) and it didn't fix the error. Also tried it in combination with pull 121 with no success.

@halzy
It works fine in my environment.
Would you show me this command result?
:lua print(vim.inspect(vim.deepcopy(vim.empty_dict())))

This is the result:
E5105: Error while calling lua chunk: [string "<VimL compiled string>"]:1: attempt to call field 'empty_dict' (a nil value)
I had modified the file that were unzip'd with neovim's nightly (osx) and had used Plug to install (git fetch) the nvim-lsp directory, to which I added the other repo as a remote and checked the branch out that the pull request was for.

Ah, shoot. I was in the wrong neovim for that command you mentioned.
The actual result: {}

@halzy

Ah, shoot. I was in the wrong neovim for that command you mentioned.

The actual result: {}

That result is not expected.
Expected behavior is vim.empty_dict().
You may have something wrong build.

Versions:
NeoVIM: NVIM v0.5.0-374-gd9657b3ae
nvim-lsp: :Plug 'h-michael/nvim-lsp', { 'branch': 'ra-server' }
With the nvim-osx files expanded in my home dir patched with:
https://github.com/neovim/neovim/pull/11864/files#diff-7f472431a1463bbeec031cd66114173e
All other NeoVim install have been removed from my system.
:lua print(vim.inspect(vim.deepcopy(vim.empty_dict())))
still reports: {}
@h-michael Am I missing a step? is there a cache of the original ~/nvim-osx64/share/nvim/runtime/lua/vim/shared.lua file somewhere?

I just ran a git bisect on the issue. 3062676b5c846174996bfd7ee746b3e5b7176d5b is the commit that introduced the error.

This got closed by automatic github action. If issues persist we can reopen it.

@halzy Try nightly Neovim. My fixes are included.

Issue has been resolved. Thank you!


Removing pre filter on drag and applying it while points traversal

Fix for the issue #2793
Because of the pre filter the index for the point was coming incorrect in mouse drag handler. Removed the filter and applied the check for isselectable inside the each loop.

Also realised that the points selected using drag were not getting unselected with chart.unselect API if the series has a combination of selectable and non selectable points. That problem also will get fixed with this change.


list customer feature

list customer feature

Codecov Report

Merging #92 (07a1def) into main (891b2a2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #92   +/-   ##
=======================================
  Coverage   96.21%   96.21%
=======================================
  Files           5        5
  Lines         396      396
=======================================
  Hits          381      381
  Misses         15       15

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 891b2a2...07a1def. Read the comment docs.


Singleton and config cleanup, also some minor fixes

Not yet tested on all platforms. Keep in mind that Window is no longer a singleton. This was done to remove all the circular includes. Window can still be reached, look at dialogs.cc for an example.
Compilation time also greatly improved.

@zalox: There are some issues with the dialogs_win.cc that I am currently fixing. Should be done Tomorrow morning if not before. I know you are working on the same, but the reason behind it was segmentation faults. Hopefully the work is not overlapping too much.

I'll make an merge request now. I changed a lot.

Splendid, I'll continue on it Tomorrow after applying your changes.

I went maybe abit crazy on dialogs_win.cc, but there were some issues. Mainly:

Exceptions are not handled correctly always on MSYS2 it seems, may lead to segmentation faults
Save file as extensions were set only to cpp-files, now it detects the extension used on the file that is going to be saved.
No need for 3 classes when one can do with 1
Opened folder is now the same as the gtk version
Memory was not always freed

I must say, I feel sorry for the people working on the Windows API every day... Hopefully, I will never see that awful thing again!;)

Please notify when ready for merge, I've looked over the changes.

Tested on most platforms. Ready for merge I think.


[meta] User Interface refactoring/enhancements

This is a meta issue to discuss/record tasks for UI refactoring and enhancements on the back of #744 and the discussion in the associated PR #761

[ ] 10.8 Fixes for autolayout #771
[ ] Replace PSMTabBar with MMTabBarView #762
[ ] Change ActivityViewer to use more of Interface Builder for setup & configuration #767
[ ] Make FoldersTree use the ‘Source List’ NSOutlineView
[ ] Move most of the NSToolbar stuff out of code and into Interface Builder
[ ] Use template images on the toolbar (and maybe NSSegmentedControl)
[ ] Enable layer-backed views (some discussion in #724)
[ ] Option to hide "filter folder" #582

FYI @Eitot @barijaona

How do you want to approach the refactoring of the toolbar? Keep the toolbar-related code in AppController or refactor into a subclass (e.g. NSToolbar or NSWindowController)?

Ok my preferred approach for all enhancements is to move as much as possible out of AppController.
I was thinking of creating an VNAToolbarController, maybe subclass from NSObject and implement NSToolbarDelegate.
Configure as much as possible using interface builder and then let the VNAToolbarController do the rest.
What do you think?

That would be my preferred approach. We could put the delegate methods and IB actions into it.
One problem is that the AppController keeps access to some resources to itself. For instance, PluginManager only lives as an instance variable in AppController, but access to it is needed by some toolbar actions as well (the style menu). Not sure how this can be done elegantly.

OK I hate singletons but I think we could move PluginManager to a singleton which should make things easier.

Which design pattern do you prefer?

I prefer as close to functional programming as possible but I know it isn't always possible and Vienna is basically the opposite to functional programming 😅
I am happy to have a simple and modular design that would be simple for unit and UI testing.
What do you prefer?

I am not an experienced programmer. I only got into programming through Swift. I have yet to learn how to program coherently and work with larger code bases. I do like modularity and the MVC pattern, but then I start refactoring things every so often, defeating the purpose of modularity. 😀
Objective-C is a different beast to me and I have no idea how to approach it yet.

Well you seem experienced!
Once we drop 10.8 we can start using Swift more which will be good :)

Mavericks solves everything 😜; Swift, stack views, NSURLSession, full base localisation, improvements to asset catalogs and a bunch of other useful Cocoa APIs.

OK I'll try to fix some of the remaining 10.8 bugs in the autolayout branch, and after we release it we can drop 10.8 support unless it is for bug fixes which I can back port.
If we are spending too much time fixing autolayout bugs for 10.8 then I suggest we end 10.8 support early.

The DisclosureView still has some bugs. It still happens that a constraint is added twice. I have made small changes to it to alleviate it somewhat, but I don’t know how I can prevent it effectively. There is no way to disable a constraint directly <10.11. It may also be possible to just set the constraint in IB and don’t remove it, but that means that the height cannot change dynamically.
I think I also spotted a concurrency bug that can happen when the filter bar should collapse. I think the direct cause is this line here in -setFilterBarState:withAnimation: in AppController.m:
[self searchUsingFilterField:self];

Eventually, this line will result in -getArticlesWithCompletionBlock in ArticleController.m being called, which executes -filterString in AppController.m on a different thread.
I am not sure if this has something to do with the implicit animation in DisclosureView, because I have been seeing these messages in the debugger which are similarly pointing to these last two methods:

CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

Here an image of the stack trace:

Interesting discovery @Eitot ! I'll see what I can do about it.

The smart-folder panel also needs some work. It is probably better to put it into a table view. Stack view would also do.

Stack view isn't available on 10.8 is it? Or is this something that would require more work and should be  >= 10.9-only ?

Yep, 10.9 only. It currently just adds the subviews to the hierarchy, but I reckon that this is not compatible with Auto Layout, hence why it doesn’t work correctly yet.

I have made a start on the toolbar in IB. Unfortunately, I have been running into lots of wee problems.
The toolbar depends on the plugin manager (for the custom toolbar items), but the plugin manager itself is only instantiated in -awakeFromNib:, so after the toolbar is loaded. This means that the toolbar calls its delegate before the plugins are initialised. I thought about just instantiating the plugin manager in AppController’s -init:, but it turns out that the plugin manager cross-references the main menu again for the menu items and accordingly fails, because the menu isn’t there yet.
Am I overlooking something? 😔

It is recommended practice to keep the MainMenu.xib separate from the NSWindow xibs of your app. If we do that, MainMenu can load with PluginManager and then we can instantiate our main window + NSWindowController.
Would this approach work? It is something we need to do sooner or later so I could break out NSWindow +  NSWindowController.
I really want to try and get the autolayout working in 10.8 first though.

No worries, this is just something I work on. What needs to be done before you can merge your branch into autolayout?
I actually think that Plugin Manager should not have any code that directly relies upon the UI. That’s a violation of the MVC pattern. It should do its tasks and then have a controller request the necessary information to build the UI.

I need remove the auto resizing masks and use constraints for the splitview i think. I was hoping to do it tonight but unfortunately something else came up.
I agree with you about Plugin Manager. I guess the other thing to consider is it worth making these changes now or should it wait for Swift?

That depends on how strongly we are committed to Mountain Lion.
Ideally, I would like to rewrite parts of the plugin manager and take advantage of Apple’s NSSharingService class for native sharing support and the extensions in Yosemite. Technically, this can be supported just fine in Mountain Lion, but I am not experienced with Objective-C. I’d prefer Swift, but I am not unwilling to learn more about Objective-C. I’m a bit worried that I have been spoilt by Swift and will try to make Swift concepts work in Objective-C. 😂

Well, so far your Objective-C code looks great! And if you send me an email to my gmail account (josh64@) I can send you some Objective-C resources that might help.
I do feel bad dropping 10.8 support, but now that is 4 versions behind, and any system that can run 10.8 can also run 10.9 - 10.11 I think we should drop it as soon as I can fix autolayout.
I will create a new branch after that for mountain-lion which is where the last version that supported mountain lion can live. We can back-port any bug fixes that are easy enough or a new volunteer that needs 10.8 support can take over maintenance of that branch.
I know some people have a good reason for staying on 10.9 in the poll I ran a couple of months ago on the forums so I wouldn't mind supporting 10.9 for a bit longer, and then maybe move to 10.11 as the minimum after the new version of macOS is announced at WWDC.

Sounds reasonable. At the end of the day, it doesn’t really help us if we constrain ourselves when there is still so much that can be done. Apple seems to be ramping up the development of Cocoa with lots of convenience classes and UIKit transplants, which would be unfortunate to miss.

Well I've tried a lot of things to fix it - you think it would be simple to add some constraints to pin the top/bottom/left/right to the superview, but it's not because Interface Builder doesn't recognise that the superview is the "Partner View".
I'm thinking NSViewController and add the constraints in code using the visual format language.

Are we ready to update the project config for 10.9?

How are we tracking on these tasks? :P


Dns file - add entry into a csv file for easy multiple server update to DNS

Pull Request Template
By contributing, you agree that your contributions will be licensed under the projects original open source license.
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change

[ ] 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 not work as expected)
[x] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce, or provide screenshots. Please also list any relevant details for your test configuration.
Sucessful execution will need to be demostrated to the repository admins if you are a Veeam Employee.
Checklist (check all applicable):

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard to understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Added entry to the end to add Server name and IP from AWS into a CSV file that can be used to mass update DNS.


Pretrained models

Hi! Thanks for sharing the codes, could you also provide a pretrained models with the best result?
Thanks

I've added links to pertained models. Please find the links in readme.


Pages without section displays incorrect navigation link

Hi, I found that when you are in a page that doesn't belong to any section (about page, 404 page for example) the navigation links are displayed incorrectly.
The template: nav-single.html has the following code:

Back to {{ .Section }}

When .Section is empty this generates the following link Back to
The fix I think is obvious... If you don't have a section, then don't display a link since you have no section to go back to.

Merged #39


Purchased and sent Cat to stake and its not showing.

Hi I sent  2- Cat/avax over last night to the nursery to stake and i can not find them anywhere??  Can someone please check and see and make sure they are in my wallet on kitty?
Thank you
I can be reached here or email<EMAIL_ADDRESS>Korey

Is there anyone that can help please?


help with PR 50

Creating an "issue" feels a bit "heavy handed", but I am not sure what else to try.
I create a PR to add scrape interval to the service monitor:
https://github.com/coredns/helm/pull/50
But, I can't "signoff" and it doesn't look like I can add reviewers/assignees/...
I don't see any kind of "contributing.md" doc for guidance. So, I am a little stuck...

Asking in the PR like you have already done works.  No need for a separate issue.


chore: Add missing parenthesis in support workflow

I thought that expr1 || expr2 && expr3 would implicitly be expr1 || (expr2 && expr3) as && typically binds "harder" than ||. That's apparently not the case in bash :D

I'm just going to merge this right away


add docker support for xs-gem5

ref issue: #207
It works fine on my server.
@shinezyy @jensen-yan

Not tested, because we don't have docker permission on our servers.
But Code look good to me


⚠ SolarOscp has degraded performance

In c240df1, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 398 ms

Resolved: SolarOscp performance has improved in fe4ee88 after 10 minutes.


Reference to Rotoselect/-solve optimizers

Added a reference to the Rotoselect and Rotosolve optimizers in PennyLane.

Website build
Commit: ce390d9d41a23796d2f09bc1e373f52740f886f7
Circle build number: 607
Website zip: https://607-214003948-gh.circle-artifacts.com/0/tmp/qml_html.zip
Website url: https://607-214003948-gh.circle-artifacts.com/0/_build/html/index.html
Please double check the rendered website build to make sure everything is correct.


Hive: Transition to a Chain with Invalid Terminal Block, Higher Configured Total Difficulty (Transition Payload)

Description
Test is failing with:
FAIL (Transition to a Chain with Invalid Terminal Block, Higher Configured Total Difficulty (Transition Payload)): Timeout while waiting for sync on the alternative PoW chain
Versions (Add all that apply)

Software version: 22.4.3-SNAPSHOT

Client 1 starts with chain G <- A, Client 2 starts with chain G <- A <- B.
Client 1's configured TTD is reached by A.
Client 2's configured TTD is reached by B.
ForkchoiceUpdated is sent to both clients with B as Head.
P1 is prepared by Client 2 on top of G <- A <- B.
newPayload(P1) is sent to Client 1 and verification is made that {status: INVALID, latestValidHash: 0x00..00}
on the #3808 branch
2022-06-07 17:28:19.590+00:00 | vert.x-worker-thread-18 | DEBUG | JsonRpcExecutor | JSON-RPC request -> engine_forkchoiceUpdatedV1 [{headBlockHash=0x2d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4, safeBlockHash=0x0000000000000000000000000000000000000000000000000000000000000000, finalizedBlockHash=0x0000000000000000000000000000000000000000000000000000000000000000}, null]
2022-06-07 17:28:19.591+00:00 | vert.x-worker-thread-0 | DEBUG | ExecutionEngineJsonRpcMethod | execution engine JSON-RPC request engine_forkchoiceUpdatedV1 [{headBlockHash=0x2d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4, safeBlockHash=0x0000000000000000000000000000000000000000000000000000000000000000, finalizedBlockHash=0x0000000000000000000000000000000000000000000000000000000000000000}, null]
2022-06-07 17:28:19.591+00:00 | vert.x-worker-thread-0 | DEBUG | FinalizedBlockHashSupplier | New finalized block hash announced Optional.empty
2022-06-07 17:28:19.592+00:00 | vert.x-worker-thread-0 | DEBUG | FinalizedBlockHashSupplier | New finalized block hash announced Optional.empty
2022-06-07 17:28:19.593+00:00 | vert.x-worker-thread-0 | DEBUG | MergeCoordinator | appending block hash 0x2d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4 to backward sync
2022-06-07 17:28:19.594+00:00 | vert.x-worker-thread-0 | INFO  | BackwardSyncContext | Starting new backward sync towards a pivot 0x2d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4
2022-06-07 17:28:19.608+00:00 | EthScheduler-Workers-0 | DEBUG | RetryingGetBlockFromPeersTask | Getting block -1 (Optional[0x2d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4]) from peer Optional[Peer 0x2e178b6db499439305... PeerReputation 100, validated? true, disconnected? false], attempt 1
2022-06-07 17:28:19.609+00:00 | EthScheduler-Workers-0 | DEBUG | GetBlockFromPeerTask | Downloading block -1 (Optional[0x2d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4]) from peer Peer 0x2e178b6db499439305... PeerReputation 100, validated? true, disconnected? false.
2022-06-07 17:28:19.610+00:00 | EthScheduler-Workers-0 | DEBUG | GetHeadersFromPeerByHashTask | Requesting 1 headers from peer Peer 0x2e178b6db499439305... PeerReputation 100, validated? true, disconnected? false.
2022-06-07 17:28:19.611+00:00 | EthScheduler-Workers-0 | TRACE | AbstractPeerConnection | Writing RawMessage{code=3, data=0xe601e4a02d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4018080} to PeerInfo{version=5, clientId='besu/v22.4.3-dev/linux-x86_64/openjdk-java-11', capabilities=[eth/62, eth/63, eth/64, eth/65, eth/66, snap/1], port=30303, nodeId=0x2e178b6db499439305a11c95966f5ce31ba4ddd8e6f0d14c8dd618b929f583fb36830669e8c894ec084f726f7f4faff6d0a05875a9e42570a7261859c44c6fda} via protocol eth/66
2022-06-07 17:28:19.630+00:00 | nioEventLoopGroup-3-2 | TRACE | EthProtocolManager | Process message eth/66, 4
2022-06-07 17:28:19.636+00:00 | nioEventLoopGroup-3-2 | TRACE | AbstractGetHeadersFromPeerTask | Peer chain state ChainState{estimatedHeight=2, bestBlock=BestBlock{totalDifficulty=0x000000000000000000000000000000000000000000000000000000000008ffa0, blockHash=0x2d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4, number=2}}
2022-06-07 17:28:19.636+00:00 | nioEventLoopGroup-3-2 | DEBUG | AbstractGetHeadersFromPeerTask | Received 1 of 1 headers requested from peer Peer 0x2e178b6db499439305... PeerReputation 100, validated? true, disconnected? false
2022-06-07 17:28:19.639+00:00 | nioEventLoopGroup-3-2 | DEBUG | GetBodiesFromPeerTask | Requesting 1 bodies from peer Peer 0x2e178b6db499439305... PeerReputation 100, validated? true, disconnected? false.
2022-06-07 17:28:19.640+00:00 | nioEventLoopGroup-3-2 | TRACE | AbstractPeerConnection | Writing RawMessage{code=5, data=0xe380e1a02d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4} to PeerInfo{version=5, clientId='besu/v22.4.3-dev/linux-x86_64/openjdk-java-11', capabilities=[eth/62, eth/63, eth/64, eth/65, eth/66, snap/1], port=30303, nodeId=0x2e178b6db499439305a11c95966f5ce31ba4ddd8e6f0d14c8dd618b929f583fb36830669e8c894ec084f726f7f4faff6d0a05875a9e42570a7261859c44c6fda} via protocol eth/66
2022-06-07 17:28:19.660+00:00 | nioEventLoopGroup-3-2 | TRACE | EthProtocolManager | Process message eth/66, 6
2022-06-07 17:28:19.663+00:00 | nioEventLoopGroup-3-2 | DEBUG | GetBlockFromPeerTask | Successfully downloaded block -1 (Optional[0x2d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4]) from peer Peer 0x2e178b6db499439305... PeerReputation 100, validated? true, disconnected? false.
2022-06-07 17:28:19.664+00:00 | nioEventLoopGroup-3-2 | DEBUG | SyncStepStep | Appending block 2(0x2d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4)
2022-06-07 17:28:19.667+00:00 | nioEventLoopGroup-3-2 | DEBUG | BackwardsSyncAlgorithm | Nothing to validate yet, consensus layer did not provide a new finalized block
2022-06-07 17:28:19.670+00:00 | nioEventLoopGroup-3-2 | INFO  | BackwardsSyncAlgorithm | Backward sync reached final header, starting Forward sync
2022-06-07 17:28:19.679+00:00 | ForkJoinPool.commonPool-worker-3 | DEBUG | ForwardSyncStep | Requesting 1 blocks 2->2 (0x2d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4)
2022-06-07 17:28:19.680+00:00 | ForkJoinPool.commonPool-worker-3 | DEBUG | GetBodiesFromPeerTask | Requesting 1 bodies from peer Peer 0x2e178b6db499439305... PeerReputation 100, validated? true, disconnected? false.
2022-06-07 17:28:19.682+00:00 | ForkJoinPool.commonPool-worker-3 | TRACE | AbstractPeerConnection | Writing RawMessage{code=5, data=0xe301e1a02d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4} to PeerInfo{version=5, clientId='besu/v22.4.3-dev/linux-x86_64/openjdk-java-11', capabilities=[eth/62, eth/63, eth/64, eth/65, eth/66, snap/1], port=30303, nodeId=0x2e178b6db499439305a11c95966f5ce31ba4ddd8e6f0d14c8dd618b929f583fb36830669e8c894ec084f726f7f4faff6d0a05875a9e42570a7261859c44c6fda} via protocol eth/66
2022-06-07 17:28:19.689+00:00 | nioEventLoopGroup-3-2 | TRACE | EthProtocolManager | Process message eth/66, 6
2022-06-07 17:28:19.691+00:00 | nioEventLoopGroup-3-2 | TRACE | BackwardSyncContext | Going to validate block 2 (0x2d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4)
2022-06-07 17:28:19.691+00:00 | nioEventLoopGroup-3-2 | DEBUG | BackwardSyncContext | Finalized block not known yet...
2022-06-07 17:28:19.692+00:00 | nioEventLoopGroup-3-2 | TRACE | LondonFeeMarket | block #2 parentBaseFee: 0x00000000000000000000000000000000000000000000000000000000342770c0 parentGasUsed: 43104 parentGasTarget: 1570796 baseFee: 0x000000000000000000000000000000000000000000000000000000002dd04ea9
2022-06-07 17:28:19.692+00:00 | nioEventLoopGroup-3-2 | DEBUG | BlockHeaderValidator | org.hyperledger.besu.consensus.merge.headervalidationrules.NoNonceRule rule failed
2022-06-07 17:28:19.692+00:00 | nioEventLoopGroup-3-2 | ERROR | MainnetBlockValidator | Invalid block header. Block 2 (0x2d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4)
2022-06-07 17:28:19.694+00:00 | nioEventLoopGroup-3-2 | INFO  | ForwardSyncStep | Saved blocks 2 -> 2 (target: 2)
2022-06-07 17:28:19.695+00:00 | nioEventLoopGroup-3-2 | DEBUG | BackwardsSyncAlgorithm | Nothing to validate yet, consensus layer did not provide a new finalized block
2022-06-07 17:28:19.695+00:00 | nioEventLoopGroup-3-2 | INFO  | BackwardsSyncAlgorithm | Backward sync reached final header, starting Forward sync
2022-06-07 17:28:19.695+00:00 | ForkJoinPool.commonPool-worker-3 | DEBUG | ForwardSyncStep | Requesting 1 blocks 2->2 (0x2d4f65a26a8d5ca4f8000010b4741652decb89c8ccf19119b5d9f58846efbbd4)
2022-06-07 17:28:19.696+00:00 | ForkJoinPool.commonPool-worker-3 | DEBUG | GetBodiesFromPeerTask | Requesting 1 bodies from peer Peer 0x2e178b6db499439305... PeerReputation 100, validated? true, disconnected? false.


Children manipulation after block's creation

How can I manipulate block children after creation?
Currently, I assign a new child in the render function, but it feels smelly:
export const myBlock = createCustomBlock({
  name: 'My block',
  type: CustomBlocksType.MY_BLOCK,
  validParentType: [AdvancedType.WRAPPER],
  create: payload => {
    const type = payload?.data?.value.type
    const defaultData = {
      type: CustomBlocksType.MY_BLOCK,
      data: {
        value: {
          type: 'text',
        },
      },
      attributes: {},
      children: [
        advanced_column.create({
          children: [advanced_text.create()],
        }),
      ],
    };
    return merge(defaultData, payload);
  },
  render: (params) => {
    const { data, idx, mode, context, dataSource } = params

    if (data.data.value.type === 'image') {
       data.children[1].children[0] = advanced_image.create()
    }

    return (
      <Section
        padding='16px 0 0 0'
        css-class={mode === 'testing' ? getPreviewClassName(idx, data.type) : ''}
      >
        {data.children.map((child, index) => {
          const childIdx = idx ? getChildIdx(idx, index) : null
          return (
            <BlockRenderer
              key={index}
              {...params}
              data={child}
              idx={childIdx}
            />
          );
        })}
      </Section>
    );
  },
});

What do you mean by different "states"?
In my example the "state" changes by data.data.value.type, it can be image, column, etc..

 In my opinion, such a complicated block should not be done.
 if (data.data.value.type === 'image') {
       data.children[1].children[0] = advanced_image.create()
    }

You can also manipulate children in configPanel.

I have four (custom) blocks:

List
List Row
Text
Status

List contains List Rows which may contain both Text and Status.
In List Row panel, I have a type attribute which may contain text or status
I want to replace List Row children the the appropriate block according to its type attribute

In this case, I suggest doing it in configPanel.
The selectedType is inferred from the children's type.
Update children when selecting other select value.

  const { input: { value } } = useField(name);

  useEffect(()=> {
     const selectedType = get(value, "children.0.type");
     if (selectedType === 'xxx') {
      // change
     }

  },[value])


Security & Rate Limiting

Task

[x] Enable Rate Limiting
[ ] Enforce Authentication on Mongo Instances
[ ] Stretch Goal: Enforce Auth Headers on API calls; whitelist only

Rate limiting can be defined in your appSettings.json