pass upgrade_configs parameters to envoy

The following is a config file works for envoy. The key part is the "upgrade_configs" param after route item. Can I set the "upgrade_configs" param to VirtualService as a item of route?
This configuration terminates a POST request and sends the POST payload upstream.
It can be used to test TCP tunneling as described in docs/root/intro/arch_overview/http/upgrades.rst
admin:
  address:
    socket_address:
      protocol: TCP
      address: <IP_ADDRESS>
      port_value: 9902
static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address:
        protocol: TCP
        address: <IP_ADDRESS>
        port_value: 10001
    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
          route_config:
            name: local_route
            virtual_hosts:
            - name: local_service
              domains:
                - "*"
              routes:
                - match:
                    prefix: "/"
                    headers:
                      - name: ":method"
                        exact_match: "POST"
                  route:
                    cluster: test_service
                    upgrade_configs:
                      - upgrade_type: CONNECT
                        connect_config:
                          allow_post: true
          http_filters:
          - name: envoy.filters.http.router
  clusters:
  - name: test_service
    connect_timeout: 0.25s
    type: LOGICAL_DNS
    dns_lookup_family: V4_ONLY
    lb_policy: ROUND_ROBIN
    load_assignment:
      cluster_name: test_service
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: <IP_ADDRESS>
                port_value: 8888

You could do it with an https://istio.io/docs/reference/config/networking/envoy-filter/


Ollama models not loading

i am going to use ollama with this, as i dont own openai key or anthropic key, i still added them to the env var in docker compose, but still asking for login via github, and even if i do try to login, it wont allow me to, the github page gives 404
i have it running in production mode, and i also have a domain attached to it, its also behind a basic auth

Update, after looking thru some issues, i removed OPENUI_ENVIRONMENT=production, and it worked, while i cannot access the ui locally thru the ip ( as its running in a remote machine ), i am able to access it with the domain as nginx and openui are running in same machine maybe, but issue is that there are no models being loaded
ollama is running in a remote machine and its accessible because my other apps that uses ollama are working. the env variable i am using in docker for ollama is
OLLAMA_HOST=http://<IP_ADDRESS>:11434

Hi @ZeyoYT,
It seems the issue arises from the OLLAMA_HOST environment variable. Ensure that the IP address that you are using, is accessible from your Docker container.
If the container is on the same host as Ollama,
set OLLAMA_HOST to http://host.docker.internal:11434.
If on a different host, verify network connectivity between the container and the Ollama server.
confirm that the Ollama server is running and listening on port 11434.


PIP-121: Pulsar cluster level auto failover

Motivation
We have geo-replication to support Pulsar cluster level failover. We can setup Pulsar cluster A as a primary cluster in data center A, and setup Pulsar cluster B as backup cluster in data center B. Then we configure geo-replication between cluster A and cluster B. All the clients are connected to the Pulsar cluster by DNS. If cluster A is down, we should switch the DNS to point the target Pulsar cluster from cluster A to cluster B. After the clients are resolved to cluster B, they can produce and consume messages normally. After cluster A recovers, the administrator should switch the DNS back to cluster A.
However, the current method has two shortcomings.

The administrator should monitor the status of all Pulsar clusters, and switch the DNS as soon as possible when cluster A is down. The switch and recovery is not automatic and recovery time is controlled by the administrator, which will put the administrator under heavy load.
The Pulsar client and DNS system have a cache. When the administrator switches the DNS from cluster A to Cluster B, it will take some time for cache trigger timeout, which will delay client recovery time and lead to the product/consumer message failing.

Goal
It's better to provide an automatic cluster level failure recovery mechanism to make pulsar cluster failover more effective. We should support pulsar clients auto switching from cluster A to cluster B when it detects cluster A has been down according to the configured detecting policy and switch back to cluster A when it has recovered. The reason why we should switch back to cluster A is that most applications may be deployed in data center A and they have low network cost for communicating with pulsar cluster A. If they keep visiting pulsar cluster B, they have high network cost, and cause high produce/consume latency.
In order to improve the DNS cache problem, we should provide an administrator controlled switch provider for administrators to update service URLs.
In the end, we should provide an auto service URL switch provider and administrator controlled switch provider.
Design
We have already provided the ServiceUrlProvider interface to support different service URLs. In order to support automatic cluster level failure auto recovery, we can provide different ServiceUrlProvider implementations. For current requirements, we can provide AutoClusterFailover and ControlledClusterFailover.
AutoClusterFailover
In order to support auto switching from the primary cluster to the secondary, we can provide a probe task, which will probe the activity of the primary cluster and the secondary one. When it finds the primary cluster failed more than failoverDelayMs, it will switch to the secondary cluster by calling updateServiceUrl. After switching to the secondary cluster, the AutoClusterFailover will continue to probe the primary cluster. If the primary cluster comes back and remains active for switchBackDelayMs, it will switch back to the primary cluster.
The APIs are listed as follows.
In order to support multiple secondary clusters, use List to store secondary cluster urls. When the primary cluster probe fails for failoverDelayMs, it will start to probe the secondary cluster list one by one, once it finds the active cluster, it will switch to the target cluster. Notice: If you configured multiple clusters, you should turn on cluster level geo-replication to ensure the topic data sync between all primary and secondary clusters. Otherwise, it may distribute the topic data into different clusters. And the consumers won’t get the whole data of the topic.
In order to support different authentication configurations between clusters, we provide the authentication relation configurations updated with the target cluster.
public class AutoClusterFailover implements ServiceUrlProvider {

   private AutoClusterFailover(AutoClusterFailoverBuilderImpl builder) {
//
}

    @Override
    public void initialize(PulsarClient client) {
        this.pulsarClient = client;

        // start to probe primary cluster active or not
        executor.scheduleAtFixedRate(catchingAndLoggingThrowables(() -> {
            // probe and switch
        }), intervalMs, intervalMs, TimeUnit.MILLISECONDS);

    }

    @Override
    public String getServiceUrl() {
        return this.currentPulsarServiceUrl;
    }

    @Override
    public void close() {
        this.executor.shutdown();
    }

    // probe pulsar cluster available
    private boolean probeAvailable(String url, int timeout) {

    }

In order to create an AutoClusterFailover instance, we use AutoClusterFailoverBuilder interface to build the target instance. The AutoClusterFailoverBuilder interface is located in the pulsar-client-api package.
In the probeAvailable method, we will probe the Pulsar service port, and check whether the port is open. This probe method has many disadvantages, such as
We're connecting to a Pulsar proxy, but there are no available brokers
Using Istio on server side, which always accepts the connection even if the broker is in a bad state
We might have deadlocks in (all) brokers and while the connections get accepted, the brokers are not able to serve them.
In order to solve this problem, we’d better provide a health check command on the broker side, just like Zookeeper’s ruok command.
We can use the probe port method first, and in the next step, we will provide the health check command on the broker side.
ControlledClusterFailover
If the users want to control the cluster switch operation, they can provide the current service URL by a http service. The ControlledClusterFailover will get the newest service url from the provided http service periodically.
The APIs are listed as follows.
public class ControlledClusterFailover implements ServiceUrlProvider {

    private ControlledClusterFailover(String defaultServiceUrl, String urlProvider) throws IOException {
    }

    @Override
    public void initialize(PulsarClient client) {
        this.pulsarClient = client;

        // start to check service url every 30 seconds
        executor.scheduleAtFixedRate(catchingAndLoggingThrowables(() -> {
            // probe and switch
        }), interval, interval, TimeUnit.MILLISECONDS);

    }

    protected ControlledConfiguration fetchControlledConfiguration() throws IOException {
        // call the service to get controlled configuration
    }

    @Override
    public String getServiceUrl() {
        return this.currentPulsarServiceUrl;
    }

    @Override
    public void close() {
        this.executor.shutdown();
    }

protected static class ControlledConfiguration {
        private String serviceUrl;
        private String tlsTrustCertsFilePath;

        private String authPluginClassName;
        private String authParamsString;

}

The configuration we get from the third url provider, we define it as java Bean by json format. In the configuration, we provide authentication-related parameters to support different clusters that have different authentication configurations. These authentication-related parameters can support all current authentication plugin types.
In order to create an ControlledClusterFailover instance, we use ControlledClusterFailoverBuilder interface to build the target instance. The ControlledClusterFailoverBuilder interface is located in the pulsar-client-api package.
API Changes
For the current ServiceUrlProvider interface, we should add a close method to close an allocated resource, such as a timer thread.
public interface ServiceUrlProvider {
    /**
     * Close the resource that the provider allocated.
     *
     */
    default void close() {
        // do nothing
    }

    /**
     * Update the authentication this client is using.
     *
     * @param authentication
     *
     * @throws IOException
     */
    void updateAuthentication(Authentication authentication)
            throws IOException;

    /**
     * Update the tlsTrustCertsFilePath this client is using.
     *
     * @param tlsTrustCertsFilePath
     */
    void updateTlsTrustCertsFilePath(String tlsTrustCertsFilePath);

    /**
     * Update the tlsTrustStorePath and tlsTrustStorePassword this client is using.
     *
     * @param tlsTrustStorePath
     * @param tlsTrustStorePassword
     */
    void updateTlsTrustStorePathAndPassword(String tlsTrustStorePath, String tlsTrustStorePassword);

}

Tests
Add tests for the two service provider implementations.
For AutoClusterFailover, when the primary cluster shuts down, it should switch to the secondary cluster. And then the primary cluster came back, we should switch back.
For ControlledClusterFailover, when switching the service url on the http service side, it should switch to the newest service url.

If  cluster B has a different authentication data with cluster A, such as another token string, how to change the authentication setting in client when auto failover happen?

If cluster B has a different authentication data with cluster A, such as another token string, how to change the authentication setting in client when auto failover happen?

Cluster A and Cluster B should be configured with the same authentication, otherwise the client should update authentication settings when switch cluster.

Is it possible to auto update authentication settings when switch cluster by implements AuthenticationDataProvider for AutoClusterFailover? We already support config geo-replicator cluster with different authentication in #10242.

Is it possible to auto update authentication settings when switch cluster by implements AuthenticationDataProvider for AutoClusterFailover? We already support config geo-replicator cluster with different authentication in #10242.

@wangjialing218 Thanks for your suggestion, i have updated the design to support different authentication configuration for different clusters.

The proposal makes sense to me.
This is only a client side feature and only for the Java client (initially)
So I would like to see it stated in the title of the PIP

The PIP mentions primary and secondary.
Can we make it more general for an arbitrary number of clusters?

The PIP mentions primary and secondary.
Can we make it more general for an arbitrary number of clusters?

@eolivelli +1 for this, was thinking in the same direction:
https://github.com/apache/pulsar/pull/13316#issuecomment-995509184

In order to support multiple secondary clusters, use List to store secondary cluster urls. When the primary cluster probe fails for failoverDelayMs, it will start to probe the secondary cluster list one by one, once it finds the active cluster, it will switch to the target cluster. Notice: If you configured multiple clusters, you should turn on cluster level geo-replication to ensure the topic data sync between all primary and secondary clusters. Otherwise, it may distribute the topic data into different clusters. And the consumers won’t get the whole data of the topic.

@eolivelli The secondary just represent the backup clusters, and I use a List to store secondary clusters to support arbitrary number of clusters.

@eolivelli +1 for this, was thinking in the same direction:

@hpvd Thanks for your suggestion. Choose cluster from secondary cluster list according to probe latency is a good idea, I will add a parameter to configure choose policy to support it.

The proposal makes sense to me. This is only a client side feature and only for the Java client (initially)
So I would like to see it stated in the title of the PIP

@eolivelli  I updated the PIP title.

@eolivelli +1 for this, was thinking in the same direction:

@hpvd Thanks for your suggestion. Choose cluster from secondary cluster list according to probe latency is a good idea, I will add a parameter to configure choose policy to support it.

@hangc0276 awesome! many thanks!

The implementation is https://github.com/apache/pulsar/pull/13316 , close this issue.

@hangc0276  你好, 看文档介绍, 受控的 failover 需要一个 service provider 管理元数据, 请问这个 provider 服务 Pulsar 会提供吗, 还是需要使用者自己写这个服务, 感谢!


:bug: Fix agent node affinity settings to always prefer control plane nodes

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Checklist:

[x] squashed commits into logical changes
[ ] includes documentation
[x] adds unit tests
[x] adds or updates e2e tests

I think we need to hold off on this change for the following reasons:

We've not seen any issues in our testing specifically related to the scheduling/placement of the agent pod(s).
We don't have time to thoroughly test the impact of this before the release
We should consider fixing this upstream instead

Lets split out the helm addon and changing the tests to use calico instead of kindnet.

@Danil-Grigorev let's break this PR into two, the one with the changes @richardcase suggested and the latter we can go through in more detail.

I’ll close this PR and open a separate one with calico changes only later.


Logfile flooding with warnings: "Could not find hp2 of hp.temperatureWaterOut"

System Health details

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
The Home Assistant log is flooded with the following warning: WARNING (MainThread) [custom_components.quatt] Could not find hp2 of hp2.temperatureWaterOut.
I have a single Quatt installation so the JSON file does not contain any hp2 information therefore it is correct that the JSON field cannot be found.
2024-02-28 11:17:48.808 DEBUG (MainThread) [custom_components.quatt.api] Fetching data from url: http://quatt.home.local:8080/beta/feed/data.json
2024-02-28 11:17:48.845 DEBUG (MainThread) [custom_components.quatt] Finished fetching quatt data in 0.037 seconds (success: True)
2024-02-28 11:17:48.846 DEBUG (MainThread) [custom_components.quatt] hp1.computedWaterDelta.temperatureWaterOut 28.33
2024-02-28 11:17:48.847 DEBUG (MainThread) [custom_components.quatt] hp1.computedWaterDelta.temperatureWaterIn 23.91
2024-02-28 11:17:48.847 WARNING (MainThread) [custom_components.quatt] Could not find hp2 of hp2.temperatureWaterOut
2024-02-28 11:17:48.847 DEBUG (MainThread) [custom_components.quatt] in {'boiler': {'oTtbTurnOnOffBoilerOn': False, 'otFbChModeActive': False, 'otFbDhwActive': False, 'otFbFlameOn': False, 'otFbSupplyInletTemperature': 67.0, 'otFbSupplyOutletTemperature': 47.0, 'otTbCH': False}, 'flowMeter': {'waterSupplyTemperature': 28.469662}, 'hp1': {'getMainWorkingMode': 2, 'limitedByCop': False, 'modbusSlaveId': 1, 'power': 4188.177787, 'powerInput': 1089.794454, 'silentModeStatus': False, 'temperatureOutside': 4.13, 'temperatureWaterIn': 23.91, 'temperatureWaterOut': 28.33}, 'qc': {'flowRateFiltered': 804.0, 'stickyPumpProtectionEnabled': False, 'supervisoryControlMode': 2}, 'system': {'hostName': 'CIC-xxx'}, 'thermostat': {'otFtChEnabled': True, 'otFtControlSetpoint': 33.0, 'otFtCoolingEnabled': False, 'otFtDhwEnabled': True, 'otFtRoomSetpoint': 19.0, 'otFtRoomTemperature': 18.75}, 'time': {'ts':<PHONE_NUMBER>662, 'tsHuman': '2024-02-28T10:17:34Z'}}
2024-02-28 11:17:48.848 DEBUG (MainThread) [custom_components.quatt] .computedWaterDelta.temperatureWaterOut None
2024-02-28 11:17:48.848 DEBUG (MainThread) [custom_components.quatt] .computedWaterDelta.temperatureWaterIn 23.91
2024-02-28 11:17:48.848 DEBUG (MainThread) [custom_components.quatt] computedHeatPower.computedWaterDelta None
2024-02-28 11:17:48.848 DEBUG (MainThread) [custom_components.quatt] computedHeatPower.flowRate 804.0
2024-02-28 11:17:48.850 DEBUG (MainThread) [custom_components.quatt] hp1.computedQuattCop.powerInput 1089.794454
2024-02-28 11:17:48.850 DEBUG (MainThread) [custom_components.quatt] hp1.computedQuattCop.powerOutput 4188.177787
2024-02-28 11:17:48.851 DEBUG (MainThread) [custom_components.quatt] electicalPower <state sensor.quatt_warmtepomp_meter_electric_consumption_w=1023.6; state_class=measurement, meter_type=1, meter_type_name=ELECTRIC, unit_of_measurement=W, device_class=power, friendly_name=Quatt warmtepomp meter Electric Consumption [W] @ 2024-02-28T11:16:29.577946+01:00>
2024-02-28 11:17:48.851 WARNING (MainThread) [custom_components.quatt] Could not find hp2 of hp2.temperatureWaterOut
2024-02-28 11:17:48.851 DEBUG (MainThread) [custom_components.quatt] in {'boiler': {'oTtbTurnOnOffBoilerOn': False, 'otFbChModeActive': False, 'otFbDhwActive': False, 'otFbFlameOn': False, 'otFbSupplyInletTemperature': 67.0, 'otFbSupplyOutletTemperature': 47.0, 'otTbCH': False}, 'flowMeter': {'waterSupplyTemperature': 28.469662}, 'hp1': {'getMainWorkingMode': 2, 'limitedByCop': False, 'modbusSlaveId': 1, 'power': 4188.177787, 'powerInput': 1089.794454, 'silentModeStatus': False, 'temperatureOutside': 4.13, 'temperatureWaterIn': 23.91, 'temperatureWaterOut': 28.33}, 'qc': {'flowRateFiltered': 804.0, 'stickyPumpProtectionEnabled': False, 'supervisoryControlMode': 2}, 'system': {'hostName': 'CIC-xxx'}, 'thermostat': {'otFtChEnabled': True, 'otFtControlSetpoint': 33.0, 'otFtCoolingEnabled': False, 'otFtDhwEnabled': True, 'otFtRoomSetpoint': 19.0, 'otFtRoomTemperature': 18.75}, 'time': {'ts':<PHONE_NUMBER>662, 'tsHuman': '2024-02-28T10:17:34Z'}}
2024-02-28 11:17:48.852 DEBUG (MainThread) [custom_components.quatt] .computedWaterDelta.temperatureWaterOut None
2024-02-28 11:17:48.852 DEBUG (MainThread) [custom_components.quatt] .computedWaterDelta.temperatureWaterIn 23.91
2024-02-28 11:17:48.852 DEBUG (MainThread) [custom_components.quatt] computedHeatPower.computedWaterDelta None
2024-02-28 11:17:48.852 DEBUG (MainThread) [custom_components.quatt] computedHeatPower.flowRate 804.0
2024-02-28 11:17:48.852 DEBUG (MainThread) [custom_components.quatt] computedCop.electicalPower 1023.6
2024-02-28 11:17:48.852 DEBUG (MainThread) [custom_components.quatt] computedCop.computedHeatPower None
2024-02-28 11:17:48.854 DEBUG (MainThread) [custom_components.quatt] hp1.computedDefrost.powerInput 1089.794454
2024-02-28 11:17:48.854 DEBUG (MainThread) [custom_components.quatt] hp1.computedDefrost.powerOutput 4188.177787

Reproduction steps

Quatt installation with one heatpump
Check Home Assistant logfile

Debug logs
-

Diagnostics dump
No response

I’ve got the same issue.

This error message is really annoying. It did not have a hp2. Are we the only ones who have these errors?
Any hints to solve it?

I also have this error message, I have single Quatt. I haven't found a solution yet

@marceldejongnl, @bertdeelman
I fixed the issue and created a pull-request for the maintainer to merge.
@marcoboers, could you have a look at the pull-request?


vCenter Server version 7 is missing in requirements

Hi,
Under Prerequisites and Requirement, vCenter Server version 7 is missing
Regards
L-E

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

ID: 2dc0f9e8-9503-5d8c-e597-66c629e23357
Version Independent ID: 2f6e08f6-8e07-f283-9254-c2152774dd4b
Content: Discover servers running in a VMware environment with Azure Migrate Discovery and assessment - Azure Migrate
Content Source: articles/migrate/tutorial-discover-vmware.md
Service: azure-migrate
GitHub Login: @Vikram1988
Microsoft Alias: vibansa

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

@LarsErikPalm - Thanks again for bringing this to our attention. We have updated the Doc and it will be live once its merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Add vote.ledgity.com custom domain

Hi! What is your PR about?

[ ] Add or edit a skin
[x] Add custom domain for your space
[ ] Add alias for migrate your space
~Add images for your space~ (deprecated) Add the image URL on the space settings directly
~Edit your space with GitHub?~ (deprecated) Please migrate your space to ENS https://docs.snapshot.page/spaces/migrate
~Create your space with GitHub~ (deprecated) Create your space with ENS instead https://docs.snapshot.page/spaces/create

Hi @gokaiorg, thanks for the review.
I’ve fixed the conflict and added domain between two existing.
Thanks by advance


Query Android 13 onBackgroundEvent vs getInitialNotification

I have an android 10 device and an android 13 device.
When the app is exited on the android 10 device and a notification is pressed, onBackgroundEvent handles the notification correctly.
However, on the android 13 device, onBackgroundEvent doesn't pick up the notification. Only getInitialNotification works.
If I implement both there are issues on android 10 as the notification is being handled twice.
Is this how notifee is supposed to be working? The documentation makes it appear that getInitialNotification should not be required in my case.

If I implement both there are issues on android 10 as the notification is being handled twice.
Hi! You can use Platform.Version to avoid double handling
https://reactnative.dev/docs/platform

We noticed some android 12 or 13 devices can trigger onBackgroundEvent when launching the app from a notification, but some cannot.  It's unclear what the difference between them yet.

Same situation, any ideas? I saw for sure it is not working for me on android 13 Samsung's devices ie Galaxy S23

Not stale

Indeed - hopefully I'm able to reward your faith in this repo with some solid maintenance, it's a struggle but I am here and watching

Not stale

Not stale

Not stale

Not stale

Not stale

Not stale

Not stale

Not stale

check https://github.com/invertase/notifee/issues/616#issuecomment-1380261291. looks like onBackgroundEvent is not like what we think about. use onForegroundEvent.

We noticed some android 12 or 13 devices can trigger onBackgroundEvent when launching the app from a notification, but some cannot. It's unclear what the difference between them yet.

check https://github.com/invertase/notifee/issues/621#issuecomment-2342711032. It's mostly like reactContext is null.

Hi @Eclipses-Saros, thanks for the heads up.  The first comment you shared is about iOS. On android, when you launch the app (app was closed), the onForegroundEvent will not fire.
We run the same app on different devices, but they have different behaviours. Is it possible that reactContext is null on some devices but not on others?

The first comment you shared is about iOS.

yes I know. but seems like Android also following same behavior as iOS after update. (I can remember onBackgroundEvent was works well before) now I can see only onForegroundEvent event when you press notification at background. (I'm guessing onBackgroundEvent is now only working as receive events) you should check it again.

On android, when you launch the app (app was closed), the onForegroundEvent will not fire.

this is normal behavior as far as I know. try using notifee.getInitialNotification(). it will be there. if there's not exist, something went wrong. need to debug.

We run the same app on different devices, but they have different behaviors. Is it possible that reactContext is null on some devices but not on others?

returning reactContext null is one of the problem onForegroundEvent or onBackgroundEvent cannot do the job. I have two Android devices, which versions are 12 and 14, have same problem. but since you're saying "different behaviors", I cannot tell exactly what's wrong. first you need to check device permission and battery save policy again.

This may be fixed in v9.1.2 here - there was definitely a problem with new architecture if it was in use, and it would not work until v9.1.2 just now

We (Doris, Yupeng and I) are on old architecture still but we'll give it a retest on 9.1.2 when we're able to do the upgrade.

What I expect is notifee.onBackgroundEvent to fire when I receive a notification. I have rnfb already integrated and notification comes wonderfully when in background, but the event is just not firing. I'm on the latest version 9.1.2. Firebase one works beautifully.
messaging().setBackgroundMessageHandler(async (remoteMessage) => {
  console.log('setBackgroundMessageHandler', remoteMessage);
});

notifee.onBackgroundEvent(async ({ type, detail }) => {
  const { notification, pressAction } = detail;
  console.log('notifee on background event', { type, detail });
});


Empty array elements and trailing comma in array literals

At some point, php parser started to parse [1, 2,] as array of 3 elements where the last array element consisting of key=nil and val=nil.
If we dig further, it also parses something like [,,,] as an array of 4 (empty) elements.
Is it intended behavior?

Relevant comment: https://github.com/VKCOM/noverify/pull/108#issuecomment-497758847
Seems like it's not an issue.

As @YuriyNasretdinov mentioned, it is a way to represent skipped elements in a list.
Unfortunately array and list use the same syntax rules to parse their items, so PHP engine checks empty elements at the compile phase https://github.com/php/php-src/blob/775e86344f05f3332463003230ef93df8167ab6c/Zend/zend_compile.c#L7666

Thanks. That resolves my question.


[a11y]: Export Modal, Dialog heading is provided in h3 instead of h2

Package
@carbon/ibm-products
Browser
Firefox
Operating System
Windows
Package version
v2.49.0-rc.0
React version
No response
Automated testing tool and ruleset
manual
Assistive technology
JAWS
Description
Reported by Raghu during screen reader testing.
Maintain hierarchical order for the Heading levels :
Recommended to present the Modal Main heading in H2.
If page headings are not in the right sequence, screen reader users find it difficult to comprehend the hierarchical structure of the page content.
WCAG 2.1 Violation
1.3.1 Info & Relationships
Reproduction/example
https://ibm-products.carbondesignsystem.com/?path=/story/ibm-products-components-export-exportmodal--standard&globals=viewport:basic
Steps to reproduce
noticeable in storybook
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems

In export modal, we are using composed modal from carbon. This heading h3 is coming from there, I have raised the issue in carbon.


sending hex str in device chirpstack

Hi
I tried sending "51282412059f23190000000000000000000000000000000000000000000000000000000000000000" in device payload and i am getting base64 encoded data on chirpstack as
NTEyODI0MTIwNTlmMjMxOTAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDA=
whereas expected encoded data is
USgkEgWfIxkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
i tried finding the issue and in order to get this data correctly i need to do a hex decode , but i am not sure where to do it
i am addding the sample sudo code here
package main
import (
"encoding/base64"
"encoding/hex"
"fmt"
)
func main() {
fmt.Printf("expected: \n USgkEgWfIxkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==")
payload := "51282412059f23190000000000000000000000000000000000000000000000000000000000000000"
current_output := base64.StdEncoding.EncodeToString([]byte(payload))
db := decodeHex([]byte(payload))
expected_output := base64.StdEncoding.EncodeToString(db)

fmt.Printf("\noriginal encoding \n %s\n", current_output)
fmt.Printf("new encoding \n %s\n", expected_output)

}
func decodeHex(input []byte) []byte {
db := make([]byte, hex.DecodedLen(len(input)))
hex.Decode(db, input)
return db
}
kindly suggest where this decodeHex needs to be put

We are working on improving this feature! Then the normal send does not work?

Closing the issue because is considered solved


ST-2560: Adding support for building debian and rhel images

Since this image is built from artifacts and not packages we don't need to create separate docker files for each os type we want to build, which is the pattern we use with the other images that are built from packages. This change will build the same docker file twice but each time using a different docker upstream tag so that it uses a different base image each time.
I have tested the debian images locally and it worked with cp-demo. Testing of the rhel images with cp-demo is still on going.

@confluentinc It looks like @elismaga just signed our Contributor License Agreement. :+1:
Always at your service,
clabot

now that we have rhel, do we need to update anything on readme?

now that we have rhel, do we need to update instructions on readme as well?

yes, there is a task on the one pager / plan to update the readme and the wiki docs. that will happen today or tomorrow


[3.5.0] Regression: Ability to add game objects to a scene before launching

It looks like 3.5.0 removed a feature I was using quite a lot in a few of my projects.
Before, it was possible to add game objects to the display list of a scene before it was displayed. That may sound like an unusual use case but that allowed me, for example:

to show a proper progress bar graphic over a splash screen (combined with a camera viewport for the bar stretching effect) (example);
get references to game objects on scenes launched in parallel.

The sample code provided below demonstrates a reduced example of that feature. It works well with 3.4.0, but fails in 3.5.0, because neither displayList or updateList exist in the scene object.
Those features may be lost due changes made for the addition of transition effects in the scene manager.

Code sample (live)
class SceneA extends Phaser.Scene {
    constructor() {
        super({
            key: 'SceneA',
            files: [{
                key: 'atari1200xl',
                type: 'image'
            }]
        });
    }
    create() {
        const sceneB = this.scene.get('SceneB');
        sceneB.getLogo();

        this.scene.launch(sceneB);
    }
}

class SceneB extends Phaser.Scene {
    constructor() {
        super({
            key: 'SceneB'
        });
    }
    getLogo() {
        return this.add.image(320, 180, 'atari1200xl');
    }
}

const game = new Phaser.Game({
    type: Phaser.AUTO,
    width: 640,
    height: 360,
    backgroundColor: '#2d2d2d',
    loader: {
        baseURL: 'https://labs.phaser.io/',
        path: 'assets/sprites/',
        crossOrigin: true
    },
    scene: [SceneA, SceneB]
});

This is nothing to do with transitions I'm afraid, it's because we fixed how scene systems start up and shut down, allowing you to close a scene down properly, re-run it later, etc without the internal systems crashing or getting confused about what state they were in, re: all the issues about re-running Matter worlds, etc. It's a lot cleaner and more robust now. However, while the above code feels like an anti-pattern I can see why it would be useful in some cases, so I'll see if I can reenable it without losing what was achieved in the restructure.

Thank you for submitting this feature request. We have implemented this and the feature has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.

The comment in the code is true though. If you already have a reference to the Scene it’s pointless getting it from the Scene Manager again!

But that method is used by several others (eg: start, pause, remove etc) internally. Enabling that branch, it is possible to pass an scene object and operate on scenes the same way as using string keys. What that branch did was (as I understand) check if that given object is a scene registered in the manager ─ if that's efficient is another matter.
Ok. If that is how things are supposed to work from the start then I'll revert to using string keys instead. :/

If you have the Scene you don’t need to go via the Scene Manager for any of those, can just do ‘menuRef.scene.start’ etc. I guess I could re-enable it, it’s a bit wasteful but happens so rarely under normal use it likely makes no difference.


server: reduce build times by ~50%

reduce build times with this one weird trick! https://fasterthanli.me/articles/why-is-my-rust-build-so-slow

| Platform        | Task                                      | Before | After |
|-----------------|-------------------------------------------|--------|-------|
| Macbook Pro x64 | `cargo check`                             | 11s    | 11s   |
| Macbook Pro x64 | `cargo build` (one line change)           | 52s    | 31s   |
| Macbook Pro x64 | `cargo build --release` (one line change) | 1m22s  | 1m3s  |


[MWPW-140706] Quiz options should use Adobe Clean and [MWPW-140499] fix multiple merch card width issue on result page

Quiz options should use Adobe Clean
fix multiple merch card width issue on result page

Resolves: MWPW-140706
MWPW-140499
Test URLs:

Before: https://main--milo--adobecom.hlx.live/drafts/quiz/quiz-2/?martech=off
After: https://uar-integration--milo--adobecom.hlx.live/drafts/quiz/quiz-2/?martech=off

There's a gnav unit test failure, but I can't see that it has anything to do with these changes in this PR.
❌ Gnav > doesn't have the toggle menu and sign-in dropdown open at the same time
Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
at createTimeoutError (node_modules/@web/test-runner-mocha/dist/autorun.js:1:243195)
at Gg._timeoutError (node_modules/@web/test-runner-mocha/dist/autorun.js:1:259145)
at node_modules/@web/test-runner-mocha/dist/autorun.js:1:257217
CC: @skumar09


Add support to scan for npm package-lock.json when scanning a NuGet solution/project

It should only look for alternative package types when the --type parameter is not specified, which triggers the auto type.


iStore not raspberry pi 5

详细叙述
Raspberry PI 5 does not have istore
重复 issue

[X] 没有类似的 issue

具体型号
Raspberry PI 5
详细日志
Raspberry PI 5 does not have istore

Currently only x86Lite comes with iStore.


[azure-identity-cpp] publish version 1.9.0

Update vcpkg ports for Azure SDK release. This release may contain multiple ports.

Adding azure-identity to release
cc: @ahsonkhan


termshow(::DataType) fails

I suppose it is a rather niche bug but I sometimes want to display DataTypes in the REPL, and I can't when install_term_repr() has been run.

Hi, https://github.com/FedeClaudi/Term.jl/pull/128 should've fixed this. If you update Term to v1.0.2 it should work.

Yes it works, thanks!


docs(ui/loadingBar): add loadingBar progress value

Checklist

[ ] Fix linting errors
[ ] Tests have been added / updated (or snapshots)

Change information

@haoziqaq Please approve PR

@BeADre

value is a internal prop and not exposed


Initial content rewrite

Initial content rewrite for docs

Rewrote a significant portion of the docs to add information and make things more clear
Added multiple sections like Stacks Academy, Tutorials, and Cookbook

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

I would also like to see a dedicated section/page with more prominence given to the whitepapers

https://stacks-docs-lcj697nen-stacks-team.vercel.app/docs/nodes-and-miners/miner-costs-and-fees
I think we should add a link to friedgers cost tool here - https://friedger.id/mining-calculator/

Not a huge fan of how cluttered this top bar looks. do we need all of these at the top, or could they be given higher prominence on the landing page perhaps?

Will we be adding this section back?
https://docs.stacks.co/docs/services-using-stacks/nft

I can't find the content under "files changed" tab for this page: https://stacks-docs-lcj697nen-stacks-team.vercel.app/docs/stacks-academy/sips
Error on this page is on line SIP 004, the word "Committment" is spelled wrong,
should be "Commitment"

again, can't find the text from this page https://stacks-docs-lcj697nen-stacks-team.vercel.app/docs/stacks-academy/microblocks  under the Files Changed tab.
under Enabling microblocks
Miners can choose to enable or disable microblocks in their mining configuration. As a best practice, miners should enable microblock mining.
that last microblock word should be plural I think, therefore should say microblocks
whole paragraph should say:
Enabling microblocks
Miners can choose to enable or disable microblocks in their mining configuration. As a best practice, miners should enable microblocks mining.

https://stacks-docs-lcj697nen-stacks-team.vercel.app/docs/nodes-and-miners/run-a-node
Under the sub-page: run-a-node with DOCKER
Incorrect: prefered
Correct: preferred
Possible incorrect: Vcpu
Possible correct: cpu
Incorrect: perfomance
Correct: performance
Incorrect: perfomance
Correct: performance
Incorrect: optionaly
Correct: optionally

https://stacks-docs-lcj697nen-stacks-team.vercel.app/docs/nodes-and-miners/digitalocean
Incorrect: prefered
Correct: preferred

https://stacks-docs-lcj697nen-stacks-team.vercel.app/docs/nodes-and-miners/miner-mainnet
Incorrect: crytpocurrency
Correct: cryptocurrency
There are 6 same error / occurrences on this page.

ping @kenrogers if you need help, maybe add myself and a few others here as collaborators on your branch so we can get these corrections resolved?

Going through and addressing all these today. I also added a spell check extension in VS Code and will be running that through all files to hopefully eliminate that issue. Will add you and Hero as collaborators after my initial sweep today so we don't end up with conflicts on this initial batch of fixes.

Will we be adding this section back?
https://docs.stacks.co/docs/services-using-stacks/nft

Yep, added this back in most recent push.

Everything in this PR has been addressed except for the Gaia/miner content, which will be addressed with future changes in the develop branch.

https://stacks-docs-lcj697nen-stacks-team.vercel.app/docs/gaia/
Incorrect: immutabile
Correct: immutable

https://stacks-docs-lcj697nen-stacks-team.vercel.app/docs/contribute/#articles
More of a visual/functional comment: The links that only appears when you hover cursor over felt little strange and pointless? I'm not sure the purpose of it without further context, just flagging.

https://stacks-docs-lcj697nen-stacks-team.vercel.app/docs/contribute/docs
(Some of which below may already been commented already, some may not have)
Incorrect:docs reposiroty
Correct: docs repository
Incorrect: so you can see a preview of yourhanges in real time.
Correct: so you can see a preview of your changes in real time.
Incorrect: Aditional information
Correct: Additional information
Incorrect: alterative
Correct: alternative

@kenrogers once you resolve the conflicts, let's merge this.
@Hero-Gamer please hold off on any new comments until we can get the changes into this repo where we can all make changes as needed vs putting it all on Ken

merge into https://github.com/stacks-network/docs/tree/develop.
I'll open a PR for develop-> master so we can continue the updates there

I finished commenting all good! I checked all pages I think :P
Good luck let me know if you need a second run through or other help.


put the FSA version back for now to fix the python build.

rename/removing fsa_predictive_compression broke pykeyvi
we need to change the python wrapper to take the reimplementation, instead of this one. For now, just quick-fixing it.
@david-cliqz

@hendrik-cliqz OK, sorry about this; will change it in my upcoming PR.


Error creating shared library on Windows 11

I attempted to create a shared library, but encountered an error when running zig build. I’m currently using Windows 11 and zig version 0.12.0-dev.3212+40e64245f.
zig build
install
└─ install zlo
   └─ zig build-lib zlo Debug native 1 errors
error: lld-link: ___chkstk_ms was replaced
error: the following command failed with 1 compilation errors:

//build.zig
pub fn build(b: *std.Build) void {
    const target = b.standardTargetOptions(.{});
    const optimize = b.standardOptimizeOption(.{});
    const lib = b.addSharedLibrary(.{
        .name = "zlo",
        .root_source_file = .{ .path = "src/root.zig" },
        .target = target,
        .optimize = optimize,
    });
    const ziglua = b.dependency("ziglua", .{
        .target = target,
        .optimize = optimize,
        .lang = .lua53,
        .shared = true,
    });
    lib.root_module.addImport("ziglua", ziglua.module("ziglua"));
    b.installArtifact(lib);
}

//src/root.zig
const ziglua = @import("ziglua");
fn zlo(lua: *ziglua.Lua) i32 {
    lua.newLib(&.{
        .{ .name = "add", .func = ziglua.wrap(add) },
    });
    return 1;
}
fn add(lua: *ziglua.Lua) i32 {
    const a = lua.toInteger(1) catch 0;
    const b = lua.toInteger(2) catch 0;
    lua.pushInteger(a + b);
    return 1;
}
comptime {
    _ = ziglua.exportFn("zlo", zlo);
}

Hmmm. I don't get a compile error on macOS, and I don't have a windows zig dev environment set up.
From some initial digging it seems that ___chkstk_ms is a libgcc function for windows. I wonder if you need to do lib.linkLibC(); in your build.zig file, but that is just a wild guess.
I can take a closer look soonish, but it may take me some days to get things setup on my windows pc.

This was merged last week https://github.com/ziglang/zig/pull/20138
I just setup a dev environment on Windows and was able to compile your example code! So it looks like you need to either wait for Zig 0.14.0 or use a dev build.
Feel free to comment if you are still having issues


Remove cfg-if

Related discussion #32

I'll just add to the discussion that right now my project depends indirectly on cfg-if and trying to update dirs to 3.0.0 causes cfg-if to be downgraded from 0.1.10 to to 0.1.9. I would be interested in dirs-rs either unpinning the exact patch dependency or removing it.

Fixed in v3.0.1.


Format change for windows in json files

PR description:
This PR enables having different values for hit selection windows in the backward and forward propagation.
The PR should be tested with using the new jsons (https://github.com/leonardogiannini/RecoTracker-MkFit/tree/newWindows, need to open PR to cms-data).
At this stage this is a purely technical PR, but new windows will be derived separately for layers where hits can be picked up both in the backward and forward propagation.
PR validation:
no differences are found in the MTV validation, as expected
http://uaf-10.t2.ucsd.edu/~legianni/TechnicalPRNewWindows/plots-new-windows/

I think that this can be submitted to cms-sw already.


Gauge chart going out of alignment when content editor is expanded

Description
The value in gauge chart went out of alignment when the content editor is expanded.

Atoti version: <IP_ADDRESS>00403103345
Browser: Chrome
Operating System: Windows 10 Pro

Thanks for reporting!
@tibdex  this looks like a core ActiveUI issue. What do you think?

Hi Hui Fang, I can reproduce this but I can always manage to get it aligned again by resizing some more:

It doesn't happen in ActiveUI. Maybe it's because the codebases of JupyterLab and ActiveUI combined register too many resize event listeners for the browser to keep being responsive.
There isn't much we can do on our side to fix this.


Suggest the best matching target for cargo run

Gets a Package from the root file path in order to look up the targets
in the project. If the specified example is not found, cargo will bail
out. Otherwise, it's added to the list of targets.
The test cases create a project with an empty lib.rs and a bin or
example source file. It then attempts to run them with target names that
are way off (bin.rs/example.rs) and names that are just a bit off (a.rs)
and analyses the result for the correct return codes and output.

Travis build failed in the style check. I didn't run make test.

Perhaps this logic could be centralized? I believe that other commands like cargo build --bin foo may also benefit from this

And of course, thanks for the PR!

Would making this a function on the Package struct make sense? You need the Package to call it as it, and that would make it available to anyone that uses that struct.

The new diff moves the new function to be a member of Package.
Closes #2266

Ah I was thinking more along the lines of moving this logic to cargo_compile.rs where the error message about "this isn't a valid target name" is generated as well.

Oh, I assumed you meant moving the function to make it available for other uses. I can add the suggestion logic to cargo_compile.rs. Would that be in addition to or instead of the use I've already added?

You'll probably want to shuffle some logic around to avoid duplication, but yeah what's here is basically what we want, just applied to more places!

Screwed up my repo, so closing and posting a new PR.


Filestackclient upload - option 'path' does not set the s3 directory correctly

Hi,
In the upload function (FilestackClient->upload($filepath, $options )) we can pass option array as the second parameter with many options. As I understand 'path' is one of the available options according to docs which set the path inside the s3 bucket.
Issue :
But no matter what you set with the option['path'] the uploads always end up in the root of the s3 bucket.
"version": "1.1.12"

The docblock don't indicate that the option is available. But it is for  uploadUrl()... It need to be implemented... thanks.

+1 thanks. this is a bit annoying as our web picker allows it, but our sdk scripts don't, which means we have some files in one folder, and other files in another folder...

Hi was this ever resolved?  I can't figure out as well how to set my specific AWS folder.  Also, I am finding the final uploaded filename is the KEY rather than the filename I have set.


Replace sles:15-sp2 test case with sles:15

Description

Replaces sles:15-sp2 test case with sles:15. Image used for sles:15-sp2 test case is no longer available. See https://github.com/gravitational/gravity/issues/2703.
Type of change

Bug fix (non-breaking change which fixes an issue)

Linked tickets and other PRs

Refs https://github.com/gravitational/gravity/issues/2703

TODOs

[x] Self-review the change
[ ] Address review feedback

Assuming robotest passes -- go for it.  I'll take a deeper look next week.


Editing Morgan tutorial - in progress

Adding edits as I go to this tutorial

Ace work, I'm done here!


Update query-json-files.md

Fixed grammar issue on line 59. Changed "Previous example uses full..." to "The previous example uses full..."

@kevinjpereira : Thanks for your contribution! The author(s) have been notified to review your proposed change.


TUS to handle lo upload

Added TUS functionality to handle LO files upload.

Looks good, just add a context object that will manage the strategy types. Tus service will call context.setStrategy(FileType) and then context.transferFile etc,

Added a context class to set the strategy and moved the other functions to it. Only cannot move the function to transfer the file because that is being used in the controller as well so it is better to keep it as part of the Tus service class.


feat: ListItem component

Description
ListItem component for Solid

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Josh Howenstine seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

I'm seeing a lot of linting errors, can you run it before we merge?


Local epub files aren't opening on older android versions

Steps to reproduce

put epub, cover, and detail files into \TachiyomiSY\local on sd card
clear database
open manga entry
open epub chapter

Expected behavior

should open the epub file as normal
should show the book title of the epub when set to source title

Actual behavior

app claims epub file is missing
book title doesn't show when set to source title

Crash logs
No response
Tachiyomi version
1.9.4
Android version
11
Device
Onyx Boox Nova5
Other details
Was testing this out on my phone because I'm planning to move from j2k over to sy and other than not being able to use both sy and normal tachiyomi's folders for local source like in j2k (i saw that this would be a thing in the next update so I'm setting everything up for that) everything worked fine. I have a set up on my ereader where I'd like to keep the 1st chapter as an epub file and when I tried it on  my samsung s22 ultra it displayed fine and it open perfectly. I test it out on my ereader and it's saying the chapter is not found.
It will show the chapter number correctly but not the source title. I don't know if this is an old os problem since my ereader is running android 11 while my phone is running 13 and not having this problem. This also seems to be an sy problem as the epub file in both j2k and normal tachiyomi opens fine.
Acknowledgements

[X] This is a TachiyomiSY specific issue that does not happen in Tachiyomi Preview.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 1.9.4.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Kinda fixed it months ago by reconverting the epubs to epubs with calibre. But also I've moved away from SY since theen.


How to understand the FGC in Heap Usage chart

How to understand the FGC in Heap Usage chart or PermGen Usage chart？
Is this FGC the same with the JVM‘s  FGC？And how to caculate  the FGC count and time n Heap Usage chart ？

I don't understand the mean about the image's FGC tip.

Hi @chuanyi-fang
The FGC is the same as JVM's FGC.
The Heap Usage chart will show them as orange bars like below:

I found the FGC（shown in the heap usage chart）is sampling from the gcOldCount or gcOldTime (in the class JvmGcBo) by the method under .So i  think the FGC isn't the same as JVM's FGC.

/**

@author HyunGil Jeong
*/
@Component
public class JvmGcSampler implements AgentStatSampler<JvmGcBo, SampledJvmGc> {
private static final DownSampler LONG_DOWN_SAMPLER = DownSamplers.getLongDownSampler(SampledJvmGc.UNCOLLECTED_VALUE);
@Override
public SampledJvmGc sampleDataPoints(int timeWindowIndex, long timestamp, List dataPoints, JvmGcBo previousDataPoint) {
JvmGcType jvmGcType = JvmGcType.UNKNOWN;
List heapUseds = new ArrayList<>(dataPoints.size());
List heapMaxes = new ArrayList<>(dataPoints.size());
List nonHeapUseds = new ArrayList<>(dataPoints.size());
List nonHeapMaxes = new ArrayList<>(dataPoints.size());
List gcOldCounts = new ArrayList<>(dataPoints.size());
List gcOldTimes = new ArrayList<>(dataPoints.size());
// dataPoints are in descending order
JvmGcBo previousBo = previousDataPoint;
for (int i = dataPoints.size() - 1; i >= 0; --i) {
JvmGcBo jvmGcBo = dataPoints.get(i);
jvmGcType = jvmGcBo.getGcType();
if (jvmGcBo.getHeapUsed() != JvmGcBo.UNCOLLECTED_VALUE) {
heapUseds.add(jvmGcBo.getHeapUsed());
}
if (jvmGcBo.getHeapMax() != JvmGcBo.UNCOLLECTED_VALUE) {
heapMaxes.add(jvmGcBo.getHeapMax());
}
if (jvmGcBo.getNonHeapUsed() != JvmGcBo.UNCOLLECTED_VALUE) {
nonHeapUseds.add(jvmGcBo.getNonHeapUsed());
}
if (jvmGcBo.getNonHeapMax() != JvmGcBo.UNCOLLECTED_VALUE) {
nonHeapMaxes.add(jvmGcBo.getNonHeapMax());
}
     if (previousBo != null) {
         // Technically, this should not be needed as data should already be partitioned by their agent start
         // timestamp and should only contain data from a single jvm life cycle.
         // Added to maintain backwards compatibility for data that do not have agent start timestamp.
         if (checkJvmRestart(previousBo, jvmGcBo)) {
             if (isGcCollected(jvmGcBo)) {
                 gcOldCounts.add(jvmGcBo.getGcOldCount());
                 gcOldTimes.add(jvmGcBo.getGcOldTime());
             } else {
                 jvmGcBo.setGcOldCount(0L);
                 jvmGcBo.setGcOldTime(0L);
             }
         } else {
             if (isGcCollected(jvmGcBo) && isGcCollected(previousBo)) {
                 gcOldCounts.add(jvmGcBo.getGcOldCount() - previousBo.getGcOldCount());
                 gcOldTimes.add(jvmGcBo.getGcOldTime() - previousBo.getGcOldTime());
             } else {
                 if (!isGcCollected(jvmGcBo)) {
                     jvmGcBo.setGcOldCount(previousBo.getGcOldCount());
                     jvmGcBo.setGcOldTime(previousBo.getGcOldTime());
                 }
             }
         }
     } else {
         if (isGcCollected(jvmGcBo)) {
             if (timeWindowIndex > 0) {
                 gcOldCounts.add(jvmGcBo.getGcOldCount());
                 gcOldTimes.add(jvmGcBo.getGcOldTime());
             } else {
                 gcOldCounts.add(0L);
                 gcOldTimes.add(0L);
             }
         }
     }
     previousBo = jvmGcBo;
 }
 SampledJvmGc sampledJvmGc = new SampledJvmGc();
 sampledJvmGc.setJvmGcType(jvmGcType);
 sampledJvmGc.setHeapUsed(createSampledPoint(timestamp, heapUseds));
 sampledJvmGc.setHeapMax(createSampledPoint(timestamp, heapMaxes));
 sampledJvmGc.setNonHeapUsed(createSampledPoint(timestamp, nonHeapUseds));
 sampledJvmGc.setNonHeapMax(createSampledPoint(timestamp, nonHeapMaxes));
 sampledJvmGc.setGcOldCount(createSampledPoint(timestamp, gcOldCounts));
 sampledJvmGc.setGcOldTime(createSampledPoint(timestamp, gcOldTimes));
 return sampledJvmGc;

}
......

JvmGcBo's gcOldCount and gcOldTime hold the gc count and time that happened in the agent's JVM.
So the chart does show the agent JVM's gc count and time. Is this not what you were asking?

Yes,
And i think JvmGcBo's gcOldCount and gcOldTime are Minor GC or Major GC,not the JVM's FULL GC.
Is it right about what i think?

Yeh, that is actually a very good point.
They're gc counts from old so Major GC would technically be correct. I can definitely see how labeling them as Full GC would be confusing.
I think we should change the label to Major GC.
Thanks for reporting!

Above the code I pasted,I can't understand the class JvmGcSampler' method "sampleDataPoints" is why to sample the gcOldCount and gcOldTime like this.

It was done this way to cover cases where 1) the agent has been restarted (even multiple times) within the time period, and 2) multiple agents with the same agent id are running.
Add all this to the fact that older pinpoint agents did not send agent startTimestamp and we had to maintain backwards compatibility.

Is pinpoint-agent to get gcOldCount and gcOldTime by "jstat"?
so gcOldCount and gcOldTime are  Cumulative,Is it right?

No, the agent queries GarbageCollectorMXBean for gcOldCount and gcOldTime.
And yup, gcOldCount and gcOldTime are cumulative.


langgraph.pregel.GraphRecursionError: Recursion limit of 25 reachedwithout hitting a stop condition. You can increase the limitby setting the recursion_limit config key.

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.

Example Code
do you know typically what is the root cause of this error and how to resolve it? Thanks.
langgraph.pregel.GraphRecursionError: Recursion limit of 25 reachedwithout hitting a stop condition. You can increase the limitby setting the recursion_limit config key.
Error Message and Stack Trace (if applicable)
do you know typically what is the root cause of this error and how to resolve it? Thanks.
langgraph.pregel.GraphRecursionError: Recursion limit of 25 reachedwithout hitting a stop condition. You can increase the limitby setting the recursion_limit config key.
Description
do you know typically what is the root cause of this error and how to resolve it? Thanks.
langgraph.pregel.GraphRecursionError: Recursion limit of 25 reachedwithout hitting a stop condition. You can increase the limitby setting the recursion_limit config key.
System Info
python 311

Same Question on running the cookbook "langgraph_self_rag.ipynb"

Same Question on Running cookbook LangGraph-Self-RAG
add config in app works for me
for output in app.stream(inputs,config={"recursion_limit":100}):

Yes you can set a higher recursion limit if you wish to loop for longer

If I type a question which is not related to the documents, then the graph keeps looping between:
'retrieve' -> grade_documents->transform_query``
As it isn't finding any relevant documents even after query transformation, it will end up looping and hitting the recursion limit of 25 or whatever is set.
I would like to raise a PR to handle this issue, would that be a useful addition?


Android APP Crashes

Hi,
when the data is loading from API in one tab which is in progress mean while the user trying swiping on to the next tab crashes the app..when the data is not completely loaded from the API.
How to enable the swipe only when the data is completely loaded in one tab and make the user to swipe to the consecutive tabs.please help us

Do you have a stack trace for the crash report? I can't think of a reason this will happen.
You can do swipeEnabled={false} when you don't want to enable swipe. Check the README.

Closed #133.


richtext-lexical: Custom components calling external API in blocks causes page to hang

Link to reproduction
No response
Describe the Bug
I'm trying to write my own blocks to be used in the Lexical editor. In particular, my blocks need to call an external API to get custom options for my editors. To try and incorporate this, I followed the example in the published YouTube video by the Payload team here:
https://www.youtube.com/watch?v=Efn9OxSjA6Y
(code here: https://github.com/JessChowdhury/custom-select/)
I then built a simple custom block that used the CustomSelectField code provided and added it to a custom block and then made the Lexical rich-text field aware of the block. When trying to add this block to a test page, my browser (Firefox) sits and hangs and the page cannot be interacted with.
After letting Firefox run for a while, it eventually tells me the page is slowing down my browser and lets me step through the code. When I do so I see the following message in the terminal:
Uncaught Error: Should not already be working.
After pressing Play again, it finishes rendering after a minute with the custom select options. I'm certainly not proficient enough with React or Lexical to really understand what's going on, but my cursory look tells me it is some sort of circular dependency when it tries to render the block UI and the CustomSelect together. The block works fine outside the Lexical editor.
I appreciate any advice on getting this to work, or if this is truly a bug that my report helps to make the editor even better. Thanks for this excellent plugin, loving using Lexical otherwise!
To Reproduce
Use the code provided by the Payload team in my description, and add a Lexical rich-text field that adds in a custom block that includes the custom select. Then, with the app running, try to add one of those blocks while in the editor (via slash command) in the admin panel.
Payload Version
2.2.1
Adapters and Plugins
db-mongodb, bundler-webpack, richtext-lexical

Hey @denvoros
can you check if this bug only happens in Firefox, or if it happens in Chrome as well?

Just tried it in Chrome, and the same thing is happening. Eventually Chrome says that the page is taking too long and gives me the option to wait or to exit.

https://github.com/payloadcms/payload/assets/70709113/4c2bf63b-8d84-46b7-b1d5-e92c8a01b696
Sadly I'm not able to reproduce this - it works for me. Could you attach a reproduction to your issue? You can find a reproduction guide here :)

Closing this for now due to missing reproduction, feel free to re-open this issue if you have one, though!


[github-actions] cli-commissioner.exp fails intermittently

logs_91907.zip

logs_95457.zip

logs_102281.zip
syslog-expect-linux.zip

Should assign to @wgtdkp ?

@wgtdkp , can you help take a look?

logs_110576.zip
syslog-expect-linux.zip

The log shows that the commissioner mgmtget sessionid steeringdata joinerudpport locator binary 0b081209 command fails with Invalid Args which is expected because the CLI format is changed to use -x for binary arguments in #5549:
2022-01-15T00:38:35.7052385Z expect: set expect_out(buffer) "\r\r\n> Donecommissioner mgmtget sessionid steeringdata joinerudpport locator binary 0b081209\r\n\r\r\n> Error 7: InvalidArgs\r\r\n> "
2022-01-15T00:38:35.7052766Z Timed out
2022-01-15T00:38:35.7052953Z     while executing
2022-01-15T00:38:35.7053133Z "error $message"
2022-01-15T00:38:35.7053339Z     (procedure "fail" line 3)
2022-01-15T00:38:35.7053537Z     invoked from within
2022-01-15T00:38:35.7053738Z "fail "Timed out" "
2022-01-15T00:38:35.7053941Z     invoked from within
2022-01-15T00:38:35.7054230Z "expect -re "\[\r\n \]($line)(?=\[\r\n>\])""
2022-01-15T00:38:35.7054477Z     (procedure "expect_line" line 3)
2022-01-15T00:38:35.7054689Z     invoked from within
2022-01-15T00:38:35.7054894Z "expect_line "Done""
2022-01-15T00:38:35.7055231Z     (file "tests/scripts/expect/cli-commissioner.exp" line 69)
2022-01-15T00:38:35.7068282Z ##[error]Process completed with exit code 1.

https://github.com/openthread/openthread/pull/7325 is opened to fix the cli command.

It's unexpected this test case doesn't fail consistently. A success test result shows that the Done output of the previous command is captured by expect_line below the commissioner mgmtget command:
> commissioner mgmtset sessionid 14283 locator 0x0100
commissioner mgmtget sessionid steeringdata joinerudpport locator binary 0b081209
Done

> Error 7: InvalidArgs

And so the InvalidArgs error is ignored.
I think there is something wrong with either the CLI output driver or the expect driver. @bukepo thoughts?

https://github.com/openthread/openthread/runs/5544984585?check_suite_focus=true


Uncaught Error: Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs.

I'm running into this issue when trying to use react-css-transition-replace:
Uncaught Error: Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside a component's `render` method, or you have multiple copies of React loaded (details: https://fb.me/react-refs-must-have-owner).

I thought it is because the npm version uses 0.14.0-rc1 but even when using the master version that uses 0.14.0, I get this...
Any idea what I'm doing wrong ?

I've come across this error when I have a local npm dependency which depends on React linked into my project with npm link. When running npm link in the dependency folder all its dependencies, including react, gets installed. When you import this dependency in your project, it references its own locally installed react, while the project uses its own instance.
The result is that, as the error message you posted states, you have multiple copies of React loaded which breaks.
I don't know if there is a solution for this problem. I have resolved to accept the rule that dependencies that depend on React themselves can't be linked with npm link.
If you're not doing something like this we can investigate further.
I just released v0.2.1 which uses<EMAIL_ADDRESS>and not the release candidate.

Actually, I do not npm link at all. But I do use React without the npm package. I mean, I explicitely import React in my HTML page header withing scripts tags:
    <script src="https://cdnjs.cloudflare.com/ajax/libs/react/0.14.0/react.js"></script>
    <script src="https://cdnjs.cloudflare.com/ajax/libs/react/0.14.0/react-dom.js"></script>

Is there a way to use your component without using npm packages ?

No, unfortunately not at the moment. I've seen other repos that support both CommonJS and script tags (and RequireJS). It should boil down to checking if you're in a CommonJS environment or not and acting accordingly, although I can't recall the specifics right now.
If you'd be willing to create a PR I will merge it. I can also take a look when I have some time, but I can't make promises on that right now.

 Darwin 14.0.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "react-css-transition-replace"
npm ERR! node v0.12.2
npm ERR! npm  v2.7.4
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package react-css-transition-replace does not satisfy its siblings' peerDependencies requirements!

And I've just material-ui installed too...

I did an npm update on one of my own projects earlier this evening and everything installed fine. But tomorrow I'll create a new project and include react 0.14, material-ui 0.13 and this latest release just to make sure it works.
What I find strange though is that those packages your install complained about aren't used by this lib at all...

sorry @marnusw it was an issue at my side... For me you can close this ticket or let it open until I or someone else package this component to work without require() calls...


feat: landing page for relay server

Just a fun landing page to show something when one hits the / path on the relay server with a browser. Probably something most people that start up a relay do the first time!
Currently shows the Portal logo, the relay's version, and a (pretty cool) animated "star travel" screensaver type of background.
Clicking the logo brings you to the Portal GitHub page. Clicking the version brings you to the releases page.
Hovering over the logo/version puts the animation into hyperdrive, taking off into hyperspace. It's a lot of fun!
Changes:

Template file for landing page: https://github.com/SpatiumPortae/portal/blob/f/server-landing/templates/relay/info.html
Added handler for /, intialized templates in server.go

Demo
https://user-images.githubusercontent.com/6842167/223131145-6ec08c8b-ff28-473a-81bc-9624ffb3f6b6.mp4

Looking into embedding the templates into the binary.


fixed undefined articleBySlug error and header validation

Updates in the states of the children of ArticlePage and the external redux state were triggering a loss of articleBySlug in the data prop of Apollo(ArticlePage). This was causing several Cannot get X from Y issues. An ArticlePage.shouldComponentUpdate checking for this would unnecessarily silence updates to all of its children, destroying commenting, sign-in, and subscription functionality in the subscription form and comment thread underneath the article's body.
The solution I've proposed is to use a setState within Article.componentWillReceiveProps to let ArticlePage keep an intact data.articleBySlug.

Feels like you're not solving the problem, but implementing a hack to patch it. Don't like it


Is there a way to use SOAP Basic Auth while making a SOAP call?

Hello, I need to make a SOAP requestw with Basic Authentication. Following the Auth documentation, I'm calling the request method in this way:
<?php
//...
$client = new GuzzleHttp\Client();
$response = $client->request('POST', $soapUri, [
    'body'    => $xmlRequest, // <x:Envelope ... ><x:Header/>...
    'headers' => [
         'Content-Type' => 'text/xml',
         'accept' => '*/*',
         'accept-encoding' => 'gzip, deflate'
    ],
    'auth' => [
        $username // basic auth username,
        $password // basic auth password,
    ]
]);
$responseBody = $response->getBody();

But apparently this is not the correct way, as the response I get is "MISSING AUTHENTICATION", despite the Header Authentication in the XML being correct, so those parameters appear not to be passed to the SOAP perver.
Is there a correct way to use the Soap Basic Auth with Guzzle?
Thanks in advance.

Could it be because you are putting your commas at the end of a comment? You should have your commas after the $username variable. Notice where I put the comma
'auth' => [
        $username, // basic auth username
        $password // basic auth password
 ]

Otherwise that should be the correct way to setup basic auth according to the docs. :)

Well spotted @Martyr2


escape regex in shellIntegration-bash.sh file

Place regular expressions in variables before use, fixes #212139 and allow the script run in older shells.

should be working now, tested on:
GNU bash, version 3.1.23(1)-release (i686-pc-msys) [MINGW32_??-10.0] oldest
and
GNU bash, version 5.2.26(1)-release (x86_64-pc-msys) [MINGW64_NT-10.0-19045] lastest

Seems to be failing the tests which likely mean there's a regression on Linux ☹


windows compatibility for postinstall setup

closes #763

merging because it’s currently breaking install of Hoodie on Windows. I test it with npm@5 and npm i hoodiehq/hoodie#763/windows-postinstall-setup-fix and it worked

retroactive +1, thanks for moving so quickly with this!


Repull image on target host

How can you repull an image on your target host, assuming you don't know what the target host will be?

@vbichov I don't understand what you mean by you don't know what the target host will be

you may use swarm to issue a "docker pull" command on some host.
you presumably also use some strategy and a filter to guide the selection of the target host.
ultimately, the target host is selected by swarm - you don't know ahead of time which it will be.
if you wish to pull (specifically, repull) an image before running it, you will run "swarm pull" and then "swarm run".
but these two commands may run on two different hosts.

@vbichov not sure it's what you want, but currently swarm pull will pull on all hosts, so the next run will have the last version of the image.

@vieux Thank you.

Is there a plan to change this behavior?
(So that Swarm will not pull on all hosts?)

I'd like to rephrase what @vbichov asked to this one.
@vieux can we do docker pull -e constraint:node==node1 image to let it pulls to a specific node.
If not, may be it's a possible one to be a PR.

I see what you mean - basically how to update an image on a particular host?

@aluzzardi Yes, but not just a particular host! the host that is going to run your container.
You do no possess this information, even if you could pull on a specific host, (which you must be able to do, or Swarm is not scalable and therefore cannot be used) if you use "docker pull" and "docker run" separately, it is conceivable that the host where the image was pulled on, and the host where it will run will not be the same host.
The only solution I can think of - and I know you won't like this - is to break the Swarm abstraction over Docker API and add a "-swarm" flag(s) to the run command.
you will need one to pull before running.
(and very possibly one to "rerun" - kill the running container by name and run - but that's a separate discussion)

Got it.
The workaround for now would be to run docker pull against Swarm - it will pull on every host (therefore including the host that is going to run your container).
But I agree that we need to find a real solution. Perhaps having a swarm specific flag (-e repull) or maybe a Docker flags (docker run --pull)

I don't know if this is the right place to pile on, but a option for the engine (which would get exposed via swarm) to force a pull before running would be very helpful in some situations. +1

Actually, there is a better workaround.

If possible, rely on tags rather than latest when scheduling a container (as in, instead of running redis, run redis:3.0.3). That way you will be sure that the underlying host will pull the right tag before creating the container
Docker supports addressing the content with a digest. You can schedule a container with the exact image you want and swarm will pull it.

@aluzzardi either one of the flags you've suggested would be awesome!
(the workaround would work - of course , but may be tricky to pull off under certain circumstances... )

@aluzzardi "You can schedule a container with the exact image you want and swarm will pull it."
How can you do that?
I have runned into the same problem, it is not really a solution to pull the same images on all hosts, and that I am trying to pull a private registry image.

Maybe in that case docker pull should be called on the node implicitly during container creation step?
See https://github.com/docker/swarm/pull/1350#issuecomment-152112163

Old issue... closing.

Why is it closed? Is possible to do it now ?

Also interested in having a solution for this. Thanks.

I think that this improvement suggested by @aluzzardi can help. Actually I need it too. But looks like it was never implemented.


Specific mp4a codec panics rodio

Audio streams downloaded from YouTube fail to play in rodio, likely as a result of the codec, although it plays fine in VLC.
Here's the panic:
thread 'main' panicked at src/main.rs:31:59:
called `Result::unwrap()` on an `Err` value: IoError("end of stream")
stack backtrace:
   0: rust_begin_unwind
             at /rustc/7cf61ebde7b22796c69757901dd346d0fe70bd97/library/std/src/panicking.rs:647:5
   1: core::panicking::panic_fmt
             at /rustc/7cf61ebde7b22796c69757901dd346d0fe70bd97/library/core/src/panicking.rs:72:14
   2: core::result::unwrap_failed
             at /rustc/7cf61ebde7b22796c69757901dd346d0fe70bd97/library/core/src/result.rs:1649:5
   3: core::result::Result<T,E>::unwrap
             at /rustc/7cf61ebde7b22796c69757901dd346d0fe70bd97/library/core/src/result.rs:1073:23
   4: rustube_demo::main::{{closure}}
             at ./src/main.rs:31:17
   5: tokio::runtime::park::CachedParkThread::block_on::{{closure}}
             at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.38.0/src/runtime/park.rs:281:63
   6: tokio::runtime::coop::with_budget
             at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.38.0/src/runtime/coop.rs:107:5
   7: tokio::runtime::coop::budget
             at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.38.0/src/runtime/coop.rs:73:5
   8: tokio::runtime::park::CachedParkThread::block_on
             at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.38.0/src/runtime/park.rs:281:31
   9: tokio::runtime::context::blocking::BlockingRegionGuard::block_on
             at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.38.0/src/runtime/context/blocking.rs:66:9
  10: tokio::runtime::scheduler::multi_thread::MultiThread::block_on::{{closure}}
             at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.38.0/src/runtime/scheduler/multi_thread/mod.rs:87:13
  11: tokio::runtime::context::runtime::enter_runtime
             at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.38.0/src/runtime/context/runtime.rs:65:16
  12: tokio::runtime::scheduler::multi_thread::MultiThread::block_on
             at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.38.0/src/runtime/scheduler/multi_thread/mod.rs:86:9
  13: tokio::runtime::runtime::Runtime::block_on
             at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.38.0/src/runtime/runtime.rs:349:45
  14: rustube_demo::main
             at ./src/main.rs:33:5
  15: core::ops::function::FnOnce::call_once
             at /rustc/7cf61ebde7b22796c69757901dd346d0fe70bd97/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

This is the result of ffprobe:
libavutil      56. 70.100 / 56. 70.100
  libavcodec     58.134.100 / 58.134.100
  libavformat    58. 76.100 / 58. 76.100
  libavdevice    58. 13.100 / 58. 13.100
  libavfilter     7.110.100 /  7.110.100
  libswscale      5.  9.100 /  5.  9.100
  libswresample   3.  9.100 /  3.  9.100
  libpostproc    55.  9.100 / 55.  9.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'eLhSxOAaWmg.mp3':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    encoder         : Google
  Duration: 00:03:00.35, start: 0.000000, bitrate: 130 kb/s
  Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 360x360 [SAR 1:1 DAR 1:1], 31 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
    Metadata:
      handler_name    : ISO Media file produced by Google Inc.
      vendor_id       : [0][0][0][0]
  Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 95 kb/s (default)
    Metadata:
      handler_name    : ISO Media file produced by Google Inc.
      vendor_id       : [0][0][0][0]

The main.rs contains the "play audio" example.

What's even stranger is that Symphonia plays it without issue. Looking into this atm.

Seems like a duplicate of #577 I now realize, however, I'll continue to add updates here as upstream seems to be working? Unsure if the referenced codec is the same, as I'm not very familiar with audio codecs.
My panic seems to be a result of this line:
let mut probed = get_probe().format(&hint, mss, &format_opts, &metadata_opts)?;
I've done the "scientific" process of adding breakpoints on the surrounding lines and it always panics on that line. Currently working on a fix for this.

Currently working on a fix for this.

Thank you very very much :+1:
What I remember from #577 the issue there was seek being very inaccurate, not the decoder crashing. The seek was off for a few seconds.

Unsure if the referenced codec is the same, as I'm not very familiar with audio codecs.

I investigated the difference as part of #577, eliminating any difference didnt fix the seek inaccuracy. Did you try updating the rodio symphonia dependency to the latest version? Maybe that fixes it?

 Well, in addition to selecting a track Symphonia can actually decode!
If I had to do this again in the future, I would start by adding the debug statements in the working example and non-working example to find the difference (though I'm not sure that would've made it any faster), but this was a helpful experience as I don't have much experience in rust or audio codecs :+1:
I've created a pull request #582 where we can continue looking into this. This is my first(!) contribution to open source, so any guidance is much appreciated!

closed by #582


Run multiple report.print or report.run doesn't work

If you try to run two reports in a row in the same code even with standard code like codeunit 242 "Item Jnl.-Post+Print".
        if ItemReg.Get(ItemJnlPostBatch.GetItemRegNo) then
            PrintItemRegister();

        if WhseReg.Get(ItemJnlPostBatch.GetWhseRegNo) then
            PrintWhseRegister();

local procedure PrintItemRegister()
var
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforePrintItemRegister(ItemReg, ItemJnlTemplate, IsHandled);
    if IsHandled then
        exit;

    ItemReg.SetRecFilter();
    Report.Run(ItemJnlTemplate."Posting Report ID", false, false, ItemReg);
end;

local procedure PrintWhseRegister()
var
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforePrintWhseRegister(WhseReg, ItemJnlTemplate, IsHandled);
    if IsHandled then
        exit;

    WhseReg.SetRecFilter();
    Report.Run(ItemJnlTemplate."Whse.Register Report ID", false, false, WhseReg);
end;

Just print the last one.

As is documented:
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/report/reportinstance-run-method

Internet browsers can only handle one file per request. Therefore, with the Web client, if this method is called in a repetitive statement (or loop) that generates multiple files, only the last file will be sent to the browser. Alternatively, when designing for the Web client, bundle the files in an archive file (.zip), for example, by using the methods found in codeunit 419 File Management. For more details about this design pattern, see Multi-File Download. The methods in codeunit 419 are not external, therefore cannot be used in extensions. Instead, when developing extensions in AL, use the external methods of codeunit 425 Data Compression. The approach is similar.

dnpb is correct. Closing as that is the right answer.


Docker swarm container cannot connect service port in other container

Description

I'm running 3 service in 2 nodes in a docker swarm using docker stack deploy a yaml file. Here' my docker version:
docker version
Client:
 Version:      1.13.1
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 06:38:28 2017
 OS/Arch:      linux/amd64

Server:
 Version:      1.13.1
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 06:38:28 2017
 OS/Arch:      linux/amd64
 Experimental: false

I'm using the default overlay network for swarm.
docker network inspect vikro_keke_default
[
    {
        "Name": "vikro_keke_default",
        "Id": "i5dub8ikcz750trpce0wdbu9g",
        "Created": "2017-03-06T16:28:53.258523288+08:00",
        "Scope": "swarm",
        "Driver": "overlay",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "<IP_ADDRESS>/24",
                    "Gateway": "<IP_ADDRESS>"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Containers": {
            "51f9bebad132592a83d52490ab41fb7f7c51e560aaea35470bdba4077e884f54": {
                "Name": "vikro_keke_rabbitmq_keke.1.tnvgpz75mmkrzzc6zv2kzj4l0",
                "EndpointID": "147e8682aae09df2a250afb988bffa2b42dc1293fd5c879eeae1e32dbc89e7fc",
                "MacAddress": "02:42:0a:00:00:03",
                "IPv4Address": "<IP_ADDRESS>/24",
                "IPv6Address": ""
            },
            "bc880c77a8e5586b2a5fdffb4d76ee47aa57e226b854961e96014cf386f1431d": {
                "Name": "vikro_keke_math.1.a26tv4f60e2v6vbn5l58tqms9",
                "EndpointID": "fd8dfb96314eb58205a68918e5473a86aa13939c3664bae79db5539689996cd8",
                "MacAddress": "02:42:0a:00:00:07",
                "IPv4Address": "<IP_ADDRESS>/24",
                "IPv6Address": ""
            }
        },
        "Options": {
            "com.docker.network.driver.overlay.vxlanid_list": "4097"
        },
        "Labels": {
            "com.docker.stack.namespace": "vikro_keke"
        },
        "Peers": [
            {
                "Name": "LocalVM-b21c412a5aef",
                "IP": "<IP_ADDRESS>"
            },
            {
                "Name": "Keke-Ubuntu-0d7dc23057aa",
                "IP": "<IP_ADDRESS>"
            }
        ]
    }
]

I can ping services using name but I failed to connect to the service port inside container.
For example:
When I ping rabbitmq_keke, I got <IP_ADDRESS> while in inspect it says <IP_ADDRESS>, but I cannot telnet the 5672 and 15672 port from other container, while these ports can be accessed outside container.
Here's the yaml file I use to start stack:
version: "3"

services:

  rabbitmq_keke:
    image: <IP_ADDRESS>:5000/rabbitmq_keke:0.2
    ports:
      - 5672:5672
      - 15672:15672
    deploy:
      placement:
        constraints: [node.role == manager]

  hello:
    image: <IP_ADDRESS>:5000/vikro:0.2
    links:
      - rabbitmq_keke
    ports:
      - 8088:8088
    command: hello.HelloService
    deploy:
      replicas: 1

Steps to reproduce the issue:

Start swarm service using yaml file
Attach to container and telnet the service port
Failed to access the port

Describe the results you received:
I can ping the name but cannot telnet the service port
Describe the results you expected:
Container can access service port
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Client:
 Version:      1.13.1
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 06:38:28 2017
 OS/Arch:      linux/amd64

Server:
 Version:      1.13.1
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 06:38:28 2017
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:
Containers: 48
 Running: 2
 Paused: 0
 Stopped: 46
Images: 29
Server Version: 1.13.1
Storage Driver: devicemapper
 Pool Name: docker-253:0-1154740-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 2.354 GB
 Data Space Total: 107.4 GB
 Data Space Available: 46.01 GB
 Metadata Space Used: 6.459 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.141 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.135-RHEL7 (2016-11-16)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: active
 NodeID: 5qfgo2rcl5grn4xi5uj9c0vew
 Is Manager: true
 ClusterID: xrxeojzf5xb6a6mm3u9nyz4zo
 Managers: 1
 Nodes: 2
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
 Node Address: <IP_ADDRESS>
 Manager Addresses:
  <IP_ADDRESS>:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1
runc version: 9df8b306d01f59d3a8029be411de015b7304dd8f
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 3.10.0-514.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.797 GiB
Name: LocalVM
ID: APMI:MS2X:MYGR:WZX2:MXHW:X2NR:IYDD:X4GE:6F57:LW64:RSS6:JSFX
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-ip6tables is disabled
Labels:
 provider=generic
Experimental: false
Insecure Registries:
 <IP_ADDRESS>:5000
 <IP_ADDRESS>/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):
One of the swarm node (Ubuntu) was running in a VirtualBox while the other (Centos) is running in a physical machine.

It turns out I can use nc to check if the port is open and it is. Close this issue.
Sorry for inconvenience.


"null://undefined" added to esriConfig.defaults.io.corsEnabledServers after sign in

This causes issues with layer-selector.
Need to look at a way to prevent or just manually remove it after successfully signing in via something like this:
esriConfig.defaults.io.corsEnabledServers.splice(
    esriConfig.defaults.io.coresEnabledServers.indexOf('null://undefined'), 1);

I don't think this belongs here because corsEnabledServers is not modified in this project. The problem stems from somewhere else. I'm still looking for where that is.


Update compare-groups.md

Added DDL to the list.

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/7258


Error when running a uv backend session with active conda environment

Current Behavior
If you have a conda environment active and try to run a session with using uv as a backend and session.install, uv throws an error because it detects both an active conda environment and an active virtual environment:
nox > Command uv pip install ruff failed with exit code 2:
error: Both VIRTUAL_ENV and CONDA_PREFIX are set. Please unset one of them.

Expected Behavior
nox should clear both VIRTUAL_ENV and CONDA_PREFIX environment variables before trying to run a session.
(I am mixing conda environments and virtual environments for a project because my project needs graphviz, which is nice to install with conda. My dev environment is using conda. However, I don't need it for all environments like linting, so it would be nice to be able to use uv for fast sessions.)
Steps To Reproduce
# noxfile.py
import nox

@nox.session(venv_backend="uv")
def lint(session):
    session.install("ruff")

# No conda environment active, no problem
❯ nox -s lint
nox > Running session lint
nox > Creating virtual environment (uv) using python in .nox/lint
nox > uv pip install ruff
nox > Session lint was successful.

# Activate a conda environment, try to run
❯ mamba create -n my-conda-env -y
...redacted for brevity...
❯ mamba activate my-conda-env
❯ nox -s lint
nox > Running session lint
nox > Creating virtual environment (uv) using python in .nox/lint
nox > uv pip install ruff
nox > Command uv pip install ruff failed with exit code 2:
error: Both VIRTUAL_ENV and CONDA_PREFIX are set. Please unset one of them.
nox > Session lint failed.

Environment
- OS: macOS
- Python: 3.12.1
- Nox: 2024.3.2

Anything else?
No response

It looks like manually unsetting the CONDA_PREFIX environment variable is a workaround, e.g.,
@nox.session(venv_backend="uv")
def lint(session):
    session.env.pop("CONDA_PREFIX")
    session.install("ruff")

I just saw https://github.com/astral-sh/uv/pull/2574 was released with uv v0.1.23.
This fixes the specific problem I was having. However, I think the opposite case would still be an issue (active venv, nox session uses conda env and user tries to use uv) and would install things into the wrong environment.


feat: set generateParameterizedFieldsResolvers to false to have parameterized queries be generated

The current graphql code gen does not generate as properties in the generated classes in mainGeneratedGprahQL for parameterized fields defined in graphql schema. As a result, fields like schemaMetadata is missing in generated Dataset, or IngestionSourceExecutionRequests is missing in IngestionSource.
According to the author of graphql-java-codegen, setting the optiongenerateParameterizedFieldsResolvers to false in build.gradle will generate the parameterized queries as properties in the generated classes and he also suggested this flag should be set to false by default in 6.0.0 release in one of the issue raised here
This PR sets the option generateParameterizedFieldsResolvers to false to have the parameterized queries generated as properties in the class. Since datahub doesn't use the generated resolver interfaces that come from when setting this to true. There's only one place to change in  CreateViewResolver.java because the constructor of DatahubView takes one more parameter with this change.
Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Thanks Tony! Changes look good :)


Update wikipedia example dialog

The output of the example is incompatible with current tantivy.

closing due to lack of activity.


problem in rails console

when I run lp [] in irb everything is fine, but when running the same command in rails console I get something like this:
ESC[1;37mArrayESC[0m
ESC[1;32m&ESC[0m         ESC[1;32mcompact!ESC[0m    ESC[1;32minclude?ESC[0m
ESC[1;32mrassocESC[0m        ESC[1;32mto_aESC[0m
the ansi colors are working fine in irb but in rails console they just make a mess in way that makes it unusable!

Thanks!


Movie Search App

Description
It a js webapp that searches movie and give brief intro about the movie and rating
Screenshots

Additional information
No response

I am assigning you this issue @Atif0604


how to apply pytorch's WeightedRandomSampler

@GuillaumeLeclerc

+1

https://github.com/libffcv/ffcv/issues/301#issuecomment-1521627945
Heres my workaround to use WeightedRandomSampler in an ffcv Loader


[Documentation] Update Ignite XML Configuration

Update Ignite XML Configuration

Codecov Report

Merging #528 (8959c07) into master (c7b0bae) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #528      +/-   ##
============================================
- Coverage     35.10%   35.06%   -0.05%
+ Complexity     1154     1148       -6
============================================
  Files           471      471
  Lines         11442    11442
  Branches       1465     1465
============================================
- Hits           4017     4012       -5
- Misses         6883     6886       +3
- Partials        542      544       +2

Impacted Files
Coverage Δ
Complexity Δ

...i/alcor/portmanager/processor/RouterProcessor.java
79.41% <0.00%> (-5.89%)
9.00% <0.00%> (-1.00%)

...rewei/alcor/portmanager/processor/PortContext.java
64.70% <0.00%> (-2.95%)
26.00% <0.00%> (-2.00%)

...alcor/elasticipmanager/dao/ElasticIpAllocator.java
63.53% <0.00%> (-0.28%)
48.00% <0.00%> (-1.00%)

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 c7b0bae...8959c07. Read the comment docs.


[Storage] Fix the self vs window rule in storage packages

This PR fixes up the latest linter rule we added to our linter.
Found this when running the lint:fix script on the storage packages
More details are in #13873
Related to #10782

cc @maorleger

@EmmaZhu @ljian3377 please take a look.


[all hosts] Publish

Docs Build status updates of commit 5e4f81d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/performance.md
:white_check_mark:Succeeded
View

docs/overview/office-add-ins-community-call.md
:white_check_mark:Succeeded
View

docs/reference/objectmodel/requirement-set-1.10/outlook-requirement-set-1.10.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel