Weighting Strategy

Hey! Thanks for making the code public, the results are great! I'm wondering if you could share some light on the weightings strategy used. Specifically, how did you arrive at $$w(t) = \sigma^2 \sqrt{1-\sigma^2}$$
I'm working on SDS in a different scenario and considering borrowing some ideas from Fantasia3D so would appreciate any insights! I noticed that in the README you provide some tips on the weighting strategy implemented in the code, but any explanation/guess on the behaviour would be useful. Thanks!
https://github.com/Gorilla-Lab-SCUT/Fantasia3D/blob/a9d0ac1076dcc85a797bbbbb200bd5ef56aa117b/geometry/dlmesh.py#L120-L130

The strategy weight is a hyperparameter. The parameter, i.g. $\omega(t) =\sigma ^{2}$, used in DreamFusion is an equation that increases as the time step t increases. This may apply to volume rendering, but it is not as suitable for surface rendering. In practice, I found that using the weight of the original version will make the rendered image over-saturated and lack detail and realism. This may be caused by the excessive weight of large t. Therefore, I want to use the weight that gradually decreases with the increase of t, so I get the strategy 0.
As for the proposal of strategy 1, I have observed that in some cases, using strategy 0 can produce a more realistic appearance, but often strange colors appear. Therefore, I would like to switch to a more suitable weight. I realized that the score function is essentially a directional gradient pointing towards the target distribution, and it can transform with the estimated noise, so I came up with Strategy 1, i.g.
 s(z_{t};t) =-\frac{1}{\sigma _{t}}\varepsilon(z_{t};t),

where $s$ is the score function. In practice, I found that it can effectively alleviate the problem of strange colors when used in conjunctions with the time step range of [0.02, 0.98].

Thanks for the detailed response! Those are some interesting observations - I'll try them out. I'm wondering if you also tried out the gradient from score jacobian chaining instead - I think the expression for that will resemble strategy 1 slightly.


chore: Add support for Scala 2.13.12

Closes https://github.com/scalameta/scalameta/issues/3329

@tgodzik do you need to add resolvers, like https://github.com/scalameta/scalameta/pull/3318/files#diff-8fd74420ca55aa91d4c53775d2a55a999c405b5a4fafeaf73b7f0ef83e1f3b0c

@tgodzik do you need to add resolvers, like https://github.com/scalameta/scalameta/pull/3318/files#diff-8fd74420ca55aa91d4c53775d2a55a999c405b5a4fafeaf73b7f0ef83e1f3b0c

They are already added, we are just missing releases for native and js, which will need to come first. This is basically ready and when Scala is released we should be good to update the version to 2.13.12

@tgodzik @bjaglin does this change (the fact that some older scala versions are now excluded) mean the next scalameta version is 4.8.11 or 4.9.0?

Hmm... I don't think this fits into semantic versioning at all so either way is fine.


Clarify Getting Started section instructions of the README

The instructions on how to enable SolutionColors are not clear for a new first-time user.
It was confusing for me, and it seems to have also confused several other users in the Q&A section for this extension in the Visual Studio Marketplace.
Reference: https://marketplace.visualstudio.com/items?itemName=MadsKristensen.SolutionColors&ssr=false#qna
From the instructions it was not very clear What or Where I had to right click to get the context menu shown in the screenshot.
I think it might be helpful to clarify the instructions and to maybe provide a screenshot that provides more context.
Personally, it wasn't clear what the "it" in "... right-click it to select the Set Solution Color submenu..." was referring to exactly so I wasn't sure what I should be right clicking on.
I was trying to right click the Solution name that is in the middle and at the top of the Visual Studio window since that is one of the main things that stands out in all the other screenshots. It's the solution name and it colorized so I thought that was what I should to be right clicking on.
I'll submit a pull request with a suggestion, but any clarification here would be helpful.

Suggested changes in pull request #36

@jp41011 I think you can close this issue, since your PR was merged.


Questions about old vs new amplify approach

Hello,
After reading this I have some questions:
https://aws.amazon.com/about-aws/whats-new/2020/05/announcing-general-availability-amplify-ios-android-authentication-data-ai-ml-support/
Should I use the new Amplify version if I think it is not necessary in my case? My iOS app works perfectly and I don't feel anything from the new approach.
Are you going to deprecate "AWS Mobile SDKs for iOS" or maintain both approaches?
My app uses Cognito (passwordless login, that is, I modified the cloud formation template to add 4 lambda functions and specific configuration), AppSync (without offline support or caching and custom cloud formation templates to support pipelines), S3, Aurora Serverless (no predicates using eq, ne, le, equals...). I don't see any advantage using the new Amplify libraries for iOS in my case.
What is your opinion about this? Should I use the newest approach sooner or later.
Thanks a lot for suggestions.
BTW, here:
https://github.com/aws-amplify/amplify-ios
I see:
"All services and features not listed above are supported via the iOS SDK or if supported by a category can be accessed via the Escape Hatch like below"
That link opens the new version of the documentation, so I guess it is wrong. It should open the old one.

Hi @Ricardo1980,

Should I use the new Amplify version if I think it is not necessary in my case?

It is really up to you. If you have an app in production and feel like Amplify won't help you, then you don't need to feel the urge nor obligated to migrate.

Are you going to deprecate "AWS Mobile SDKs for iOS" or maintain both approaches?

Eventually we will, but we will announce it in advance and provide a migration plan. Right now both will be maintained. However, new features will only be added to Amplify.

What is your opinion about this? Should I use the newest approach sooner or later.

It's hard to tell without knowing more details about your use case and the reality of your app in terms of stability, number of users, etc. But from what you have seen so far, if you believe Amplify won't help your existing app then trust your knowledge about your app to define the best strategy.
If I may recommend something, I would say you could try Amplify in a new app, for testing purposes if you're curious about the differences between the new approach and the existing SDK. That could give you a better idea for future endeavors.
Let me know if my answers helped you.

That link opens the new version of the documentation, so I guess it is wrong. It should open the old one.

You're right, that link is broken. Thanks for reporting!

That link opens the new version of the documentation, so I guess it is wrong. It should open the old one.

You're right, that link is broken. Thanks for reporting!

Thanks a lot!


Can you combine multiple modifiers?

my view has a need for a minimum width of 37, but always multiplied by 1.5
countLabel <- [
    Width(>=37),
    Width(*1.5)
]

it does not generate an error, but it doesn't work either..

Hi @avalanched 👋
I'm afraid you are not allowed to do that for now. In that piece of code Width(*1.5) will override Width(>=37). Instead you can set different priorities for those Attributes (if that's the intended implementation).
Thanks for the issue 👍

that also means you cannot constraint the following:

view should have a width of equal or greater then 200 but no greater then 400

You can constrain it like this:
view <- [
    Width(<=400),
    Width(>=200).with(.MediumPriority)
]

👍  thanks


1509 dont close history browsing on remove

Thank you for your contribution to the KodaDot NFT gallery.
👇  _ Do a quick check before the merge.
PR type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted screenshot of demonstrated change in this PR

https://user-images.githubusercontent.com/17953978/146058883-0077e920-99b5-4938-97e6-f762ae948680.mov
Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything works
[ ] I found edge cases

What's new?

[x] PR closes #1509
[x] don't close history on removeItem; remove bottom padding; dont show history icon at all if no items in history

Had issue bounty label ?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[ ] My fix has changed something on UI, a screenshot for others, is best to understand changes.

Perfect, I’ve sent the payout https://kusama.subscan.io/extrinsic/0x41692201e37ac0c28e67da6e02de6f0c370fff79b572f82ccc9d854bd5ee4a7c
Let’s grab another issue and get rewarded!
https://github.com/kodadot/nft-gallery/issues/
It's lovely now! :)


Fix generation of content types

Currently static content is being assigned a Content-Type header of an empty string.
The index works out of the box correctly, but will misbehave if other middleware is added to the request handler.

:+1: awesome, thanks @danielwhite


Advanced Weather Viewer Branch layer sync issue when closing and reopening the AWV.

In this screenshot, I was displaying the 8-day, all years median on the map, then I closed the AWV. Now that I've reopened the AWV, the cloud layer is not displaying, but "show on map" is no longer active. I have to click any other choice (say, 1-day), then go back to 8-day to redisplay the 8-day data.

Possible solutions - make the "show on map" button active when we reopen, or keep the cloud layer displayed when we reopen.

If we use v-show (which hides component) instead of v-if (which rebuilds component) that would keep the AWV state consistent, but that might degrade performance for main app. So probably want to pass props to component.

so this is in a dialog. turns out the issue was just that I was turning displayData variable, so the component appeared to reset. the state is preserved as a dialog.

Reopening this issue - So the AWV preserves it's state, but what is going wrong is that the LocationSelector does not. Vue saves the AWV state (it is in a dialog) but the LocationSelector (and any other child components) are removed. What happens is that it seems like this.map is null when it gets to the parseResult function. setup is getting run, but seems like this.map is not getting set soon enough. This seems to be because updateCloudCover uses this.map but is called in the setup function before this.map is set. #93 resolves this by moving updateCloudCover to the end of setup


Clean elses

I've removed the elses when we have already returned something :put_litter_in_its_place:
We can also enable no_useless_else in StyleCI. Should we?

@carusogabriel this looks good. Not familiar with no_useless_else settings of StlyeCI but if it does automate this step, then I'm in favor of it.


Envoy memory usage rises indefinitely when failing to fetch configuration via the xDS protocol

Description:
We use the Basic xDS protocol to deliver dynamic configuration to Envoy from a management server.
In addition, we have a static configuration with one listener and one cluster.
It seems that if Envoy fails to fetch the configuration from the management server, for example, when the management server is down, Envoy's memory usage rises indefinitely (approximately ~1Mb per minute). It only stops when Envoy is able to fetch the configuration.
Some observations we were able to make:

This only happens when Envoy is unable to fetch the configuration since startup.
Removing the static listener and cluster from the config seems to fix the issue (memory doesn't rise indefinitely).

Repro steps:

Deploy envoy with the static configuration specified in the configuration section. There is no need to setup an actual management server.
Monitor the memory usage, for example, via the /memory endpoint in the admin interface.

Config
admin:
  access_log:
  - typed_config:
      "@type": type.googleapis.com/envoy.extensions.access_loggers.file.v3.FileAccessLog
      path: /dev/null
  address:
    socket_address:
      address: <IP_ADDRESS>
      port_value: 19000

node:
  cluster: protected_app
  id: aaa

dynamic_resources:
  ads_config:
    api_type: GRPC
    transport_api_version: V3
    grpc_services:
      envoy_grpc:
        cluster_name: cluster1
        authority: "auth"
  cds_config:
    ads: {}
    resource_api_version: V3
    initial_fetch_timeout: 0s
  lds_config:
    ads: {}
    resource_api_version: V3
    initial_fetch_timeout: 0s

static_resources:
  clusters:
  - name: cluster1
    connect_timeout: 10s
    type: "STRICT_DNS"
    dns_refresh_rate: 180s
    lb_policy: ROUND_ROBIN
    load_assignment:
      cluster_name: cluster1
      endpoints:
      - lb_endpoints:
          endpoint:
            address:
              socket_address:
                address: "control-plane"
                port_value: 8080
    typed_extension_protocol_options:
      envoy.extensions.upstreams.http.v3.HttpProtocolOptions:
        "@type": type.googleapis.com/envoy.extensions.upstreams.http.v3.HttpProtocolOptions
        explicit_http_config:
          http2_protocol_options:
            connection_keepalive:
              interval: 30s
              timeout: 5s
    upstream_connection_options:
      tcp_keepalive:
        keepalive_time: 300

  - name: a_metrics
    connect_timeout: 1s
    type: "static"
    lb_policy: ROUND_ROBIN
    load_assignment:
      cluster_name: a_metrics
      endpoints:
      - lb_endpoints:
          endpoint:
            address:
              socket_address:
                address: <IP_ADDRESS>
                port_value: 19000
  listeners:
    - name: lst-metrics
      address:
        socket_address:
          address: "<IP_ADDRESS>"
          port_value: 19010
      filter_chains:
        - filters:
            - name: envoy.http_connection_manager
              typedConfig:
                "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
                codec_type: auto
                stat_prefix: a_metrics
                route_config:
                  name: local_route
                  virtual_hosts:
                    - name: backend
                      domains:
                        - "*"
                      routes:
                        - match:
                            prefix: "/stats/prometheus"
                          route:
                            cluster: a_metrics
                        - match:
                            prefix: "/metrics"
                          route:
                            regex_rewrite:
                              pattern:
                                regex: "metrics"
                              substitution: "stats/prometheus?text_readouts"
                            cluster: a_metrics
                      response_headers_to_remove: ["Server"]
                http_filters:
                  - name: envoy.filters.http.router
                    typed_config:
                      "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
                server_header_transformation: PASS_THROUGH

Logs
':status', '200'
'content-type', 'application/grpc'
'grpc-status', '14'
'grpc-message', 'no healthy upstream'

[2023-12-31 15:54:26.116][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:190] StreamAggregatedResources gRPC config stream to cluster1 closed since 6654s ago: 14, no healthy upstream
[2023-12-31 15:54:26.116][1][debug][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:125] gRPC update for type.googleapis.com/envoy.config.cluster.v3.Cluster failed
[2023-12-31 15:54:26.116][1][debug][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:60] Unable to establish new stream to configuration server cluster1
[2023-12-31 15:54:26.116][1][debug][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:125] gRPC update for type.googleapis.com/envoy.config.cluster.v3.Cluster failed
[2023-12-31 15:54:26.573][1][debug][main] [source/server/server.cc:263] flushing stats
[2023-12-31 15:54:26.573][1][debug][main] [source/server/server.cc:273] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2023-12-31 15:54:31.573][1][debug][main] [source/server/server.cc:263] flushing stats
[2023-12-31 15:54:31.573][1][debug][main] [source/server/server.cc:273] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2023-12-31 15:54:31.786][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:365] dns resolution for control-plane started
[2023-12-31 15:54:31.794][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:152] dns resolution for control-plane failed with c-ares status 11
[2023-12-31 15:54:31.799][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:152] dns resolution for control-plane failed with c-ares status 11
[2023-12-31 15:54:31.799][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:285] dns resolution for control-plane completed with status 1
[2023-12-31 15:54:31.799][1][debug][upstream] [source/extensions/clusters/strict_dns/strict_dns_cluster.cc:184] DNS refresh rate reset for control-plane, (failure) refresh rate 180000 ms
[2023-12-31 15:54:33.622][1][debug][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:51] Establishing new gRPC bidi stream to cluster1 for rpc StreamAggregatedResources(stream .envoy.service.discovery.v3.DiscoveryRequest) returns (stream .envoy.service.discovery.v3.DiscoveryResponse);

[2023-12-31 15:54:33.623][1][debug][router] [source/common/router/router.cc:520] [Tags: "ConnectionId":"0","StreamId":"16089286589495779457"] cluster 'cluster1' match for URL '/envoy.service.discovery.v3.AggregatedDiscoveryService/StreamAggregatedResources'
[2023-12-31 15:54:33.623][1][debug][upstream] [source/common/upstream/cluster_manager_impl.cc:1942] no healthy host for HTTP connection pool
[2023-12-31 15:54:33.623][1][debug][http] [source/common/http/async_client_impl.cc:106] async http request response headers (end_stream=true):
':status', '200'
'content-type', 'application/grpc'
'grpc-status', '14'
'grpc-message', 'no healthy upstream'

[2023-12-31 15:54:33.623][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:190] StreamAggregatedResources gRPC config stream to cluster1 closed since 6662s ago: 14, no healthy upstream
[2023-12-31 15:54:33.623][1][debug][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:125] gRPC update for type.googleapis.com/envoy.config.cluster.v3.Cluster failed
[2023-12-31 15:54:33.623][1][debug][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:60] Unable to establish new stream to configuration server cluster1
[2023-12-31 15:54:33.623][1][debug][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:125] gRPC update for type.googleapis.com/envoy.config.cluster.v3.Cluster failed
[2023-12-31 15:54:36.573][1][debug][main] [source/server/server.cc:263] flushing stats
[2023-12-31 15:54:36.573][1][debug][main] [source/server/server.cc:273] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2023-12-31 15:54:41.576][1][debug][main] [source/server/server.cc:263] flushing stats
[2023-12-31 15:54:41.576][1][debug][main] [source/server/server.cc:273] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2023-12-31 15:54:44.949][1][debug][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:51] Establishing new gRPC bidi stream to cluster1 for rpc StreamAggregatedResources(stream .envoy.service.discovery.v3.DiscoveryRequest) returns (stream .envoy.service.discovery.v3.DiscoveryResponse);

[2023-12-31 15:54:44.950][1][debug][router] [source/common/router/router.cc:520] [Tags: "ConnectionId":"0","StreamId":"2604332730402544397"] cluster 'cluster1' match for URL '/envoy.service.discovery.v3.AggregatedDiscoveryService/StreamAggregatedResources'
[2023-12-31 15:54:44.950][1][debug][upstream] [source/common/upstream/cluster_manager_impl.cc:1942] no healthy host for HTTP connection pool
[2023-12-31 15:54:44.950][1][debug][http] [source/common/http/async_client_impl.cc:106] async http request response headers (end_stream=true):
':status', '200'
'content-type', 'application/grpc'
'grpc-status', '14'
'grpc-message', 'no healthy upstream'

[2023-12-31 15:54:44.950][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:190] StreamAggregatedResources gRPC config stream to cluster1 closed since 6673s ago: 14, no healthy upstream
[2023-12-31 15:54:44.950][1][debug][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:125] gRPC update for type.googleapis.com/envoy.config.cluster.v3.Cluster failed
[2023-12-31 15:54:44.950][1][debug][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:60] Unable to establish new stream to configuration server cluster1
[2023-12-31 15:54:44.950][1][debug][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:125] gRPC update for type.googleapis.com/envoy.config.cluster.v3.Cluster failed
[2023-12-31 15:54:46.577][1][debug][main] [source/server/server.cc:263] flushing stats
[2023-12-31 15:54:46.577][1][debug][main] [source/server/server.cc:273] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2023-12-31 15:54:51.574][1][debug][main] [source/server/server.cc:263] flushing stats
[2023-12-31 15:54:51.575][1][debug][main] [source/server/server.cc:273] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2023-12-31 15:54:56.575][1][debug][main] [source/server/server.cc:263] flushing stats
[2023-12-31 15:54:56.575][1][debug][main] [source/server/server.cc:273] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2023-12-31 15:55:01.574][1][debug][main] [source/server/server.cc:263] flushing stats
[2023-12-31 15:55:01.574][1][debug][main] [source/server/server.cc:273] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2023-12-31 15:55:06.577][1][debug][main] [source/server/server.cc:263] flushing stats
[2023-12-31 15:55:06.577][1][debug][main] [source/server/server.cc:273] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2023-12-31 15:55:09.067][1][debug][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:51] Establishing new gRPC bidi stream to cluster1 for rpc StreamAggregatedResources(stream .envoy.service.discovery.v3.DiscoveryRequest) returns (stream .envoy.service.discovery.v3.DiscoveryResponse);

[2023-12-31 15:55:09.067][1][debug][router] [source/common/router/router.cc:520] [Tags: "ConnectionId":"0","StreamId":"15864330249036367919"] cluster 'cluster1' match for URL '/envoy.service.discovery.v3.AggregatedDiscoveryService/StreamAggregatedResources'
[2023-12-31 15:55:09.067][1][debug][upstream] [source/common/upstream/cluster_manager_impl.cc:1942] no healthy host for HTTP connection pool
[2023-12-31 15:55:09.067][1][debug][http] [source/common/http/async_client_impl.cc:106] async http request response headers (end_stream=true):
':status', '200'
'content-type', 'application/grpc'
'grpc-status', '14'
'grpc-message', 'no healthy upstream'

[2023-12-31 15:55:09.067][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:190] StreamAggregatedResources gRPC config stream to cluster1 closed since 6697s ago: 14, no healthy upstream
[2023-12-31 15:55:09.067][1][debug][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:125] gRPC update for type.googleapis.com/envoy.config.cluster.v3.Cluster failed
[2023-12-31 15:55:09.067][1][debug][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:60] Unable to establish new stream to configuration server cluster1
[2023-12-31 15:55:09.067][1][debug][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:125] gRPC update for type.googleapis.com/envoy.config.cluster.v3.Cluster failed
[2023-12-31 15:55:11.574][1][debug][main] [source/server/server.cc:263] flushing stats
[2023-12-31 15:55:11.574][1][debug][main] [source/server/server.cc:273] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2023-12-31 15:55:16.575][1][debug][main] [source/server/server.cc:263] flushing stats
[2023-12-31 15:55:16.575][1][debug][main] [source/server/server.cc:273] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2023-12-31 15:55:21.577][1][debug][main] [source/server/server.cc:263] flushing stats
[2023-12-31 15:55:21.577][1][debug][main] [source/server/server.cc:273] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2023-12-31 15:55:23.860][1][debug][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:51] Establishing new gRPC bidi stream to cluster1 for rpc StreamAggregatedResources(stream .envoy.service.discovery.v3.DiscoveryRequest) returns (stream .envoy.service.discovery.v3.DiscoveryResponse);

[2023-12-31 15:55:23.860][1][debug][router] [source/common/router/router.cc:520] [Tags: "ConnectionId":"0","StreamId":"11845650912692327212"] cluster 'cluster1' match for URL '/envoy.service.discovery.v3.AggregatedDiscoveryService/StreamAggregatedResources'
[2023-12-31 15:55:23.860][1][debug][upstream] [source/common/upstream/cluster_manager_impl.cc:1942] no healthy host for HTTP connection pool
[2023-12-31 15:55:23.860][1][debug][http] [source/common/http/async_client_impl.cc:106] async http request response headers (end_stream=true):
':status', '200'
'content-type', 'application/grpc'
'grpc-status', '14'
'grpc-message', 'no healthy upstream'

[2023-12-31 15:55:23.860][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:190] StreamAggregatedResources gRPC config stream to cluster1 closed since 6712s ago: 14, no healthy upstream
[2023-12-31 15:55:23.860][1][debug][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:125] gRPC update for type.googleapis.com/envoy.config.cluster.v3.Cluster failed
[2023-12-31 15:55:23.860][1][debug][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:60] Unable to establish new stream to configuration server cluster1
[2023-12-31 15:55:23.860][1][debug][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:125] gRPC update for type.googleapis.com/envoy.config.cluster.v3.Cluster failed
[2023-12-31 15:55:26.574][1][debug][main] [source/server/server.cc:263] flushing stats
[2023-12-31 15:55:26.574][1][debug][main] [source/server/server.cc:273] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2023-12-31 15:55:31.574][1][debug][main] [source/server/server.cc:263] flushing stats
[2023-12-31 15:55:31.574][1][debug][main] [source/server/server.cc:273] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2023-12-31 15:55:36.576][1][debug][main] [source/server/server.cc:263] flushing stats
[2023-12-31 15:55:36.576][1][debug][main] [source/server/server.cc:273] Envoy is not fully initialized, skipping histogram merge and flushing stats

Thanks for reporting this!
Do you happen to have flame graph showing memory usage after it is run for some time while failing to fetch a configuration?

Thanks for reporting this! Do you happen to have flame graph showing memory usage after it is run for some time while failing to fetch a configuration?

Hi, thanks for responding.
No, we don't have one.

I let this run overnight and got this profile. I don't have experience reading these yet, but I've attached the overall shape and a zoom on the red parts. The last call leading into the red part is TimerImpl, so I wonder if some timers are created but never closed for each attempt to fetch the config --I'm not familiar with the code yet.
fwiw, I do something like this. You'll need to run pprof to have a good look at the data.
curl <IP_ADDRESS>:19000/heap_dump -o memory-bug.heap
pprof -http localhost:9999 memory-bug.heap

mem-leak-profile.pb.gz

memory-bug.heap.gz
memory-leak-test.yaml.txt --remove the .txt that's a github weirdness

Seems that The TlsCachingDateProviderImpl creates objects in the thread local storage (https://github.com/envoyproxy/envoy/blob/4265b99cfb42516296d95c63da9b7e02990264af/source/common/http/date_provider_impl.cc#L27) that are never deallocated when the xDS server is unavailable.
I'm not sure why the objects are not freed, and further investigation is required.

Thanks! I haven't seen one of these with the dotted arrow going up, but if the TimerImpl is properly cleaned up (on xDS fail) that should clean up the TlsCachingDateProviderImpl too, correct?

@cgthayer  & @adisuissa - Thanks for investigating this.
Are you aware of any plans for fixing this?

Hi, thanks.
Any plans on fixing this?

At the moment my bandwidth is limited. Setting it as no-stale.


[FLINK-28911] Ensure the SerializationSchema has been opened.

Proposed fix for https://issues.apache.org/jira/browse/FLINK-28911
I'm a bit in doubt if it is good enough to simply pass a null value to the open method.
It works in this case; but are there cases where a reaal value is needed?

Have a look at https://github.com/apache/flink/commit/fb95798b1c301152b912c4b8ec4a737ea16d8641 how I solved it for the version in Flink.

@zentol Thanks !
Yet now I'm confused (sorry for not reading the mailing lists properly): What is the source repo of these connectors? Which version do we maintain?

Yet now I'm confused (sorry for not reading the mailing lists properly): What is the source repo of these connectors? Which version do we maintain?

In 1.17 the ES connector will only exist in this repository. Until then they exist in both, to provide a better migration path.

Then I'm going to copy your solution into here (it is much better).

@nielsbasjes Will you update the PR? I'll have a look then

@MartijnVisser I'm in doudbt.
Either

We close this ticket/pullrequest and simply copy the entire connector the moment we move from within flink to this project.
I'm going to copy the entire connector for this pull request and we repeat this when we do the move.

Personally I'm inclined to wait until the 1.16.0 feature branch was cut, and then do the sync. Maybe even until 1.16.0 is released.

Yes I agree. Let's just close this. And after 1.16.0 has been release do a "great migration".
@zentl If you guys also agree then please close this one.


Add Sketchbook Earth

Insert URLs to the project here:
https://github.com/ECMWFCode4Earth/sketchbook-earth

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as 'Good First Issue' of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.
I had to use google to find the deployed website:
https://ecmwfcode4earth.github.io/sketchbook-earth/intro.html

@nicrie @NikosMastrantonas


[Change Request] - Remove multiple sign in with provider when migration is required

Is your feature request related to a problem? Please describe.
When using Sign in with Apple and allowMigration set to nil, if the Apple ID is a registered user, we get the usual migrationRequired error. That is fine to handle this case, but there's no way to continue the authentication without restarting the procedure from scratch; this result in the Sign in with Apple dialog appearing twice.
Describe the solution you'd like
We should be able to continue the authentication procedure after having asked the user what they'd like to do with their existing data. I'm seeing something like:
func signIn(with credentials: <someCredentialHolder>, updateUserDisplayName: Bool, allowMigration: Bool) -> Single<LoginDescriptor>

When the migrationRequired error is thrown, the caller receives an instance of someCredentialHolder and it is responsible of passing it back to the UserManager in order to proceed with the authentication.
Additional context
This, in addition to solving this issue, would allow us to support more providers without actually implementing them into the library, but that would mean exposing a generic structure to store credentials (something that Firebase already does).

This has been solved in version 1.3.0.


Question about map

Hello, I tried to use PASCAL VOC2007 trainval to train this orignal FPN_resnet_101 without any changes, and test on VOC2007 test, I found the test map is 78.57%. So I wonder if you did some improvement on FPN recently, cause the test result on VOC2007 in your cfgs.py is 76.14%.

I set the parameter "USE_07_METRIC=True" in the cfgs.py, which means using 11 point method to calculate ap, and the test map is 76.003%, I think this might be the reason of higher map I got before, emmm, which one is the correct map, I am confused.

So, is the VOC2007 and VOC2012 map given by cfgs.py calculated by setting parameter "USE_07_METRIC=True"?

In general, if you use the voc2007 dataset, set USE_07_METRIC to True, and if you use the voc2012 dataset, set it to False. The former is generally lower than the latter, and the latter is more accurate. In addition, the COCO data evaluation script should be consistent with voc2012.
@TianhangTang

Thank you very much. Emmm, so the voc2012_test2007 map(78.57%) in cfgs.py is calculated by setting "USE_07_METRIC=False"?Because I made a little change based on FPN, and the voc2012 test on voc2007 map is 81.79%("USE_07_METRIC=False"), I want to see whether I made any improvement or not. If the voc2012 map(78.57%) is calculate by "USE_07_METRIC=True", then the real value should be larger, and I have to retrain the original FPN and do the comparative experiment, it is really time consuming.

I wrote in cfgs.py whether to use USE_12_METRIC （line46） or USE_07_METRIC (line88)
@TianhangTang

USE_07_METRIC = False in the default cfgs.py, that is, the evaluation method of voc2012 is used @TianhangTang

@yangxue0827 I got it, both map results are trained and evaluated on VOC2007, I mistook the former one as trained on VOC2012. Thanks again.


ruby_library not using specified SDK version

We are testing out the flow where the desired version of ruby is not installed on the host.
I expect for rules_ruby to be able to install and use v2.7.6. (Note this first requires bumping the ruby-build version, which I created a PR here).
With the version specified in WORKSPACE:
load("@bazelruby_rules_ruby//ruby:deps.bzl", "rules_ruby_select_sdk")
rules_ruby_select_sdk(version = "2.7.6")

I can confirm that ruby interpreter that's installed to the @org_ruby_lang_ruby_toolchain external repository is the right version:
➜  org_ruby_lang_ruby_toolchain build/bin/ruby -v
ruby 2.7.6p219 (2022-04-12 revision c9c2245c0a) [arm64-darwin21]

However, running any ruby_library target i get this error on my macos:
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in 'require': incompatible library version...
I think this requires updating the way the binary wrapper is implemented, which defaults to the first ruby found in PATH today rather than the version that's specified in the SDK:
#!/usr/bin/env ruby

...

def find_ruby_binary
  File.join(
    RbConfig::CONFIG['bindir'],
    RbConfig::CONFIG['ruby_install_name'],
  )
end

In fact, it looks like there was an intention to substitute {interpreter} here but the wrapper script template itself does not have a {interpreter} placeholder anywhere, which looks like a bug.

I missed this issue, which points to the same bug.

That's not the issue afaik.
Thank you for including your error:
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in 'require': incompatible library version...

What this error tells you is that the Ruby being used here is the system Ruby that comes with Os-X. It's a Ruby 2.6, and it's installed into a read only file system. So naturally you can't install any gems there.
The rules expect your ruby to be installed by rbenv.
In order for rbenv to work, you must add the following to your shell initialization file:
eval "$(rbenv init -)"


File Upload Issue

I use concrete5 8.4.2. The video link shows below the actual steps taken. I try and upload a video directly from the File Manager that is 42MB, it will not upload. However, if I upload a video smaller than 25MB, it will upload. Then I can REPLACE it in the File Manager and the replacement of 42MB uploads just fine. I have my PHP settings on the server at 500MB. I've tested this on older versions and it functions properly.
http://www.screencast.com/t/vvo6x0zVyh
Thanks,
Ed.

@edsaxmoore - Not trying to push your issue aside, but github is meant to be issues that are found on the latest development branch, not a stable release. This is because there's a chance that the bug or issue has already been corrected and will be released with a future version of concrete5
When you create the issue it describes that:

[ ] this is an issue that I tested with the development version of GitHub
Bugs of stable releases should be submitted to https://www.concrete5.org/developers/bugs/

I'd encourage you to post your bug report to the appropriate channel (the url above) or check if there are other bug reports similar to yours and I'd encourage you to also log any relevant PHP errors that show up in the log or web server errors that might be occurring.
I'd also like to say that if no issues crop up, we are implementing file upload chunking (via pull request #7118) in a future release which should eliminate any upload size issues, most likely in 8.4.4 or 8.5.0 I would guess. So keep patching your concrete5 version as new releases come out and hopefully all will be solved!

@joe-meyer - You're right about everything you're saying and in a perfect world the bug tracker would be the tool of choice, but experience shows that there is no noticeable response to bug reports posted there, at least from the user's point of view. Maybe the development team still reads every report carefully in the background, but if this is not visible to the user in any way, this channel will not be used in the way it certainly should.

@joe-meyer that's not entirely correct, there are plenty of times where user environments are not updated to the latest version, and the bug is present in even the latest version. Reporting a bug does not quire to be on the development branch, that's just an unrealistic expectation for production environments.
As someone who has for quite a while reported many bugs and such, I have yet to see use of the dev branch be an actual requirement for such here. So yeah, keep that in mind.

@BloodyIron
@joe-meyer is correct, GitHub bug report issues need to be tested against the develop branch. This is a requirement listed in the issue template. The issue template was created on Feb 18, 2016, but was a requirement before that date.
https://github.com/mlocati/concrete5/blob/46546a8450e434dceaa9cf2d62ae4ce536639b45/.github/ISSUE_TEMPLATE.md
This policy helps prevent issue creation for issues that have already been resolved in the develop branch or are for older versions of concrete5. Testing and validating bug report issues is often time consuming and is made more so if you need to test against multiple versions.

I understand the importance of the conversation going on here, but... what about the REAL issue of the uploading of files of a particular size? Please, let's not lose site of that as it still is not working. Whether it is on github or concrete5 site... the upload is not working correctly. So far, I haven't heard anyone trying to address the REAL problem, only trying to decide if it was posted in the correct place. I posted in BOTH places. I appreciate all that you do and LOVE concrete5, purchase add-ons and hire developers to customize things for me. I know this issue can be solved, I just don't have the knowledge to do it and am relying on all of you for help. Thank you.

@edsaxmoore do you have any javascript error in your browser developer console? Did you try to wait a few minutes before closing the "Add Files" dialog?

@edsaxmoore did you test it with the development branch or just with 8.4.2? As I said in my original post, I think this issue should be solved already in the next release assuming it was a file size uploading issue, which is the only reason I brought up the guidelines to begin with.

We routinely upload files 100MB and more @edsaxmoore – this sounds like an environment issue.

I realize I haven’t responded to this in quite some time. We stopped uploading large videos for a while. However, I have upgraded to 8.4.5 and am still having the same issue. I can upload a video of 24MB, but anything over that just stalls from the File Manager. What I do to get it to work is to upload a small video of the same name, then go to properties and REPLACE that video with a 50MB+- video and it will upload just fine.
I have checked all the settings on the server, we allow up to 500MB to upload at a time. I am using Cloudways/Digital Ocean servers.  I really need to get this resolved.  Any help is appreciated.
Ed Moore
Red Sneakers Mobile Marketing
direct<PHONE_NUMBER>tel:239-284-1878
From: Joe Meyer<EMAIL_ADDRESS>Sent: Friday, October 19, 2018 7:20 AM
To: concrete5/concrete5<EMAIL_ADDRESS>Cc: Ed Moore<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [concrete5/concrete5] File Upload Issue (#7175)
@edsaxmoorehttps://github.com/edsaxmoore did you test it with the development branch or just with 8.4.2? As I said in my original post, I think this issue should be solved already in the next release assuming it was a file size uploading issue, which is the only reason I brought up the guidelines to begin with.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/concrete5/concrete5/issues/7175#issuecomment-431330607, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Agygna_79V2CQV1zttpsPeJ6KP16IqELks5umbVWgaJpZM4XMDmD.


Get List of Available IP for Subnet

Azure CLI recently added this command:
az network vnet list-available-ips -g [resource group] -n [vnet name]

This works great but only seems to return some ip addresses in the VNet.
Can we leverage the jmeshquery --query to specify some ip range or a subnet to narrow this down?
Is your feature request related to a problem? Please describe.
Yes, the list-available-ips command doesnt return all available ip's
For example you may have <IP_ADDRESS>/16 and you may have a bunch of subnets, can we filter to a given subnet, or get all available ip's from the vnet.
Describe the solution you'd like
Option 1 - Possibly use --query to specify the ip range of the subnet or subnet name
Option 2 - Add the same list-available-ips command for az network vnet subnet
If there is a way to do this, maybe we can document it and update the CLI Docs with an example.
Describe alternatives you've considered
Manually typing random ip's in a range to see if they are consumed.
Additional context
We did this for VNet level but that only returns some of the available ip's.

@geoarchitect Thanks for your suggestions. I would invite service team to take a look. When I worked for this command, I didn't find a way to list some ips within a subnet. We might need service team's help.

We are looking into this. Thanks for the feedback, @geoarchitect .

Hi @jl-ms , we have a use-case where in our create/upgrade aks cluster playbooks..we need to know the number of available IPs within a given subnet before performing creation or upgrading.

We have the same need using python SDK where we need to query number of available ( Free ) IPs in a subnet before we allow VM provisioning to continue. I will be watching this post closely to see if anyone comes up with solution or workaround using NetworkManagementClient.   Thanks, OO

#!/usr/bin/bash

vnet_rg="rg-th01-sea-n-nonprodsrv01-network01"
vnet_name="vnet-th01-sea-n-nonprodsrv01"
subnet_name="subnet-u-nonprod-aks01-<IP_ADDRESS>-24"

network_prefix=`az network vnet subnet show -g $vnet_rg -n $subnet_name --vnet-name $vnet_name -o json | jq -r .addressPrefix`

regex="\/(.*)"

[[ $network_prefix =~ $regex ]]

subnet_mask=${BASH_REMATCH[1]}

max_ip=$((2 ** (32-$subnet_mask)-5))

used_ip=`az network vnet subnet show -g $vnet_rg -n $subnet_name --vnet-name $vnet_name -o json -o json | jq  ".ipConfigurations[].id" | wc -l`

available_ip=$(($max_ip - $used_ip))

echo "There are $available_ip IPs available for subnet $subnet_name"

we are using this as a workaround
#!/usr/bin/bash

vnet_rg=""
vnet_name=""
netmask="24"

max_ip=$((2 ** (32-$netmask)-5))

used_ip=`az network vnet subnet show -g $vnet_rg -n $subnet_name --vnet-name $vnet_name -o json -o json | jq  ".ipConfigurations[].id" | wc -l`

available_ip=$(($max_ip - $used_ip))

echo "There are $available_ip IPs available for subnet $subnet_name"

Testing blocked by feature Microsoft.Network/AllowMultipleAddressPrefixesOnSubnet registration.


[Feature Request]: Adding Translation Tool

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Feature Description
websites are increasingly becoming a primary means of communication and interaction. To ensure that these digital platforms reach the widest possible audience, it's imperative that they are accessible to people from diverse linguistic backgrounds. A translation tool can play a pivotal role in achieving this goal.
Use Case
Global Reach: By providing content in multiple languages, a website can attract visitors from around the world, expanding its potential customer base.
Enhanced User Experience: Users who can access content in their native language are more likely to engage with the website, leading to increased satisfaction and loyalty.
Benefits
Adding a translation tool to your website can offer numerous benefits, from expanding your global reach to improving user experience and boosting SEO.
MockUp
https://github.com/user-attachments/assets/c1c359de-c2a6-4936-924a-b582e63c871f
@JayShukla8    can you assign this issue to me with labels "gssoc-ext" with levels 3  and "hacktoberfest-accepted";
Record

[X] I agree to follow this project's Code of Conduct
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

Hii, @VidhanThakur09 thanks but this feature is not required as of now.


Parsing compiler name & version from Spack environment to include in the performance log file

Attempt for issue https://github.com/ukri-excalibur/excalibur-tests/issues/251
Thanks: @giordano

Besides compilers, another specific bit of information that users may be interested in is the MPI implementation used, which can be fished out with spec["mpi"], with the caveat that not all packages depend on MPI, so this would need to check whether "mpi" in spec, so not to error out (e.g. spec["mpi"] if "mpi" in spec else "").

for  spack install<EMAIL_ADDRESS>+std build_system=cmake std_submodel=data :
$ spack -e /lustre/home/br-kolgu/excalibur-tests-upstream/stage/isambard-macs/cascadelake/default/STDDATABenchmark/spack_env/cascadelake python -c 'from spack import environment; d = environment.active_environment().spec_lists["specs"].specs[0].variants;print(d)'
+std build_system=cmake std_submodel=data

According to the manual dict should do the job:
$ spack -e /lustre/home/br-kolgu/excalibur-tests-upstream/stage/isambard-macs/cascadelake/default/STDDATABenchmark/spack_env/cascadelake python -c 'from spack import environment; d = environment.active_environment().spec_lists["specs"].specs[0].variants;print(d.dict)'
{'std': BoolValuedVariant('std', True), 'build_system': AbstractVariant('build_system', 'cmake'), 'std_submodel': AbstractVariant('std_submodel', 'data')}

Keys :
$ spack -e /lustre/home/br-kolgu/excalibur-tests-upstream/stage/isambard-macs/cascadelake/default/STDDATABenchmark/spack_env/cascadelake python -c 'from spack import environment; d = environment.active_environment().spec_lists["specs"].specs[0].variants;print(d.dict.keys())'
dict_keys(['std', 'build_system', 'std_submodel'])

From here we try :
$ spack -e /lustre/home/br-kolgu/excalibur-tests-upstream/stage/isambard-macs/cascadelake/default/STDDATABenchmark/spack_env/cascadelake python -c 'from spack import environment; d = environment.active_environment().spec_lists["specs"].specs[0].variants;print(d.dict["std_submodel"])'
std_submodel=data

$ spack -e /lustre/home/br-kolgu/excalibur-tests-upstream/stage/isambard-macs/cascadelake/default/STDDATABenchmark/spack_env/cascadelake python -c 'from spack import environment; d = environment.active_environment().spec_lists["specs"].specs[0].variants;print(d.dict["std_submodel"].value)'
('data',)

$ spack -e /lustre/home/br-kolgu/excalibur-tests-upstream/stage/isambard-macs/cascadelake/default/STDDATABenchmark/spack_env/cascadelake python -c 'from spack import environment; d = environment.active_environment().spec_lists["specs"].specs[0].variants;print(d.dict["std_submodel"].value[0])'
data

So we could form a loop to run through all the keys and export them as different columns for the perflog. But my question was during the meeting for the reframe_config.py file :
https://github.com/ukri-excalibur/excalibur-tests/blob/323ae1142337563783d5de5ca04ac5ae2ad9d883/benchmarks/reframe_config.py#L733-L758
how do we know the names ? I have an idea to export all the spack_spec variants into a list and run through that list in the reframe_config.py file to print each column is it valid approach ?

This modified code for the utils.py :
        spack_spec_keys = 'from spack import environment; list(environment.active_environment().spec_lists["specs"].specs[0].variants.dict.keys())'
        spack_spec_vals = 'from spack import environment; d = environment.active_environment().spec_lists["specs"].specs[0].variants.dict; l = list(d.keys()); values=[d[key].value[0] if isinstance(d[key].value,tuple) else d[key].value for key in l];print(values) '
        cmd_compiler_name = 'from spack import environment; print(environment.active_environment().spec_lists["specs"].specs[0].compiler.name)'
        cmd_compiler_version = 'from spack import environment; environment.active_environment().spec_lists["specs"].specs[0].compiler.versions[0]'
        self.postrun_cmds.append(f'echo "compiler_name: $(spack -e {self.build_system.environment} python -c \'{cmd_compiler_name}\')"')
        self.postrun_cmds.append(f'echo "compiler_version: $(spack -e {self.build_system.environment} python -c \'{cmd_compiler_version}\')"')
        self.postrun_cmds.append(f'echo "Spack_Spec keys : $(spack -e {self.build_system.environment} python -c \'{spack_spec_keys}\')"')
        self.postrun_cmds.append(f'echo "Spack_Spec vals : $(spack -e {self.build_system.environment} python -c \'{spack_spec_vals}\')"')

Prints out :
compiler_name: gcc
compiler_version: 13.1.0
Spack_Spec keys : ['std', 'build_system', 'std_submodel']
Spack_Spec vals : [True, 'cmake', 'ranges']

For  : spack install<EMAIL_ADDRESS>+std build_system=cmake std_submodel=data
I will check if sanity library function extractall is what we need for reading all the values from keys to pass to the reframe_config.py and values to be assigned for each.
I am open for any other suggestions if there is anything more direct approach than this

I think you're almost there, @kaanolgu . The output I was thinking (for one package in the spec, see my comment above about many packages) is something like:
Spack_Spec : {'std':True, 'build_system':'cmake', 'std_submodel':'ranges'}

instead of the two separate lists spack_spec-keys and spack_spec-vals. I think a dict(zip(spack_spec-keys,spack_spec-vals)) should do it.

@giordano @ilectra
https://github.com/ukri-excalibur/excalibur-tests/pull/262/commits/8ba75611d79834c3a0d4d6083cce21c90e9345dc Tested with following :
Input:
reframe -c benchmarks/apps/babelstream -r --tag cuda --system=isambard-macs:volta --setvar=num_cpus_per_task=40 -S build_locally=false -Sspack_spec='babelstream%gcc@9.2.0,12.1.0 +cuda cuda_arch=70,72'

Output :
spack_spec: {'cuda': True, 'cuda_arch': {'70', '72'}, 'compiler_name': 'gcc', 'compiler_version': {'12.1.0', '9.2.0'}}

Output (perflog) :
...|spack_spec|...
...|{'cuda': True, 'cuda_arch': {'70', '72'}, 'compiler_name': 'gcc', 'compiler_version': {'9.2.0', '12.1.0'}}|...

Besides compilers, another specific bit of information that users may be interested in is the MPI implementation used, which can be fished out with spec["mpi"], with the caveat that not all packages depend on MPI, so this would need to check whether "mpi" in spec, so not to error out (e.g. spec["mpi"] if "mpi" in spec else "").

Just saw this, will add it in a new commit

The added columns don't seem to require any additional changes for post-processing to function normally, so this looks good to me on that front.
Edit: Do note, however, that if you'd like to unpack any of your dict fields, please see how extra_resources and env_vars are handled in lines 119-125 of the read_perflog function in perflog_handler.py.

Yes, you have to unpack those the way Emily says. And once you add all the packages in the spec, it will be a bit more complicated than extra_resources and env_vars, as your values will not be just a dict anymore, but a nested dict of dicts (see my review comments and other comments above).
Also, in order to make the postprocessing not dependent on perflog version, there should be a check if those columns exists, before it's attempted to unpack them.

@giordano @ilectra
https://github.com/ukri-excalibur/excalibur-tests/pull/262/commits/49f22867d29feafd1886ac7dea08bf3e9e79244b
Fixes the issues we discussed and also includes the post-processing too

The pytests pass on my local machine, but for some reason the GHA ci workflow still fails. We are wondering if it's using a cached version of utils.py that is not writing the spec into the output.


selinux: consume deployer selinux policy updates

We need different selinux policies based on the platform version.
Starting with v0.7.0, changes were implemented in the deployer which can be vendored in here.
Redo of #337 to test CI issues

/cherry-pick release-4.11


Actually terminate zip on clicking the X button

Fixes the issue #959. Uploading zip files were not getting canceled on clicking the X button. The progress bar was retracting but the actual uploading of the zips continued in the background. So if the user tried to upload another zip, then it won't get uploaded until the first one has finished.
I have made two videos to demonstrate this issue

Before the changes
https://www.opentest.co/share/c6365830d5c611e6a7cb6f2926412bab
After the changes
https://www.opentest.co/share/a49ba540d5cb11e68531cf81a6426bba
@mariobehling @aayusharora Please review.

Current coverage is 33.77% (diff: 0.00%)

Merging #963 into development will decrease coverage by 0.16%

@@           development       #963   diff @@
=============================================
  Files                7          7
  Lines             1043       1048     +5
  Methods            130        131     +1
  Messages             0          0
  Branches           162        163     +1
=============================================
  Hits               354        354
- Misses             689        694     +5
  Partials             0          0

Powered by Codecov. Last update 121227e...0c4fd66

@Princu7 LGTM !! Please squash the commits.

@Princu7 Please squash commits in future. I am merging now to keep the development flow. Cheers.


Merge master into horizon v0.24.1 release branch

In particular, I'd like to make sure https://github.com/stellar/go/pull/2047 is included in the horizon v0.24.1 release so we can test out the publish docker circleci job

@tamirms can you cherry-pick this specific PR commit: https://github.com/stellar/go/pull/2047 and create a new PR? We're going to release 0.24.1 early next week so I'd like to make a set of changes minimal (and there are a lot of files included in Horizon that has changed recently in master).

closing this PR in favor of https://github.com/stellar/go/pull/2049


docker:dind not working in 1.11.1 qemu-virtiofs

Description of problem
We use a kata-deploy style install for using Kata with Kubernetes (containerd 1.3.4 -- overlaysfs snapshotter) and just tried updating from 1.11.0 to 1.11.1. When using the qemu-virtiofs runtime we now cannot run docker commands and get operation not permitted errors. The errors below are using the unmodified 1.11.1 release.
Expected result
(When running inside a K8 pod using kata)
docker run hello-world -- works just like it did in 1.11.0

Actual result
/ # docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
0e03bdcc26d7: Pull complete
Digest: sha256:d58e752213a51785838f9eed2b7a498ffa1cb3aa7f946dda11af39286c3db9a9
Status: Downloaded newer image for hello-world:latest
docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"process_linux.go:415: setting cgroup config for procHooks process caused \\\"failed to write \\\\\\\"b *:* m\\\\\\\" to \\\\\\\"/sys/fs/cgroup/devices/docker/81a3c5750ffe91ea0c5992f5b532589c8aa2a64cd1cb22c6a49036bf356b32e2/devices.allow\\\\\\\": write /sys/fs/cgroup/devices/docker/81a3c5750ffe91ea0c5992f5b532589c8aa2a64cd1cb22c6a49036bf356b32e2/devices.allow: operation not permitted\\\"\"": unknown.

Just the error message:

Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused "process_linux.go:415: setting cgroup config for procHooks process caused \"failed to write \\\"b : m\\\" to \\\"/sys/fs/cgroup/devices/docker/81a3c5750ffe91ea0c5992f5b532589c8aa2a64cd1cb22c6a49036bf356b32e2/devices.allow\\\": write /sys/fs/cgroup/devices/docker/81a3c5750ffe91ea0c5992f5b532589c8aa2a64cd1cb22c6a49036bf356b32e2/devices.allow: operation not permitted\""": unknown.

Here is a simples pod spec to help illustrate...
apiVersion: v1
kind: Pod
metadata:
  name: untrusted-dind
  annotations:
    io.kubernetes.cri.untrusted-workload: "true"
spec:
  containers:
    - name: docker
      image: docker:dind
      imagePullPolicy: IfNotPresent
      command:
      - dockerd-entrypoint.sh
      - dockerd
      - --host=unix:///var/run/docker.sock
      - --host=tcp://localhost:2375
      - --mtu=1400
      securityContext:
        privileged: true
      ports:
        - containerPort: 2375

(using untrusted annotation because runtimeClass feature gate is off in my environment)

It seems pretty likely that the fix for CVE-2020-2023 and CVE-2020-2026 here are causing this problem. Does something special need to be done to accommodate because this is a privileged container?

To be clear, this is a "regression" between Kata 1.11.0 and 1.11.1.  I do not believe this is a problem with virtio-fs.

@skaegi I have the same problem.
kata-runtime  : 1.10.4
   commit   : dc550720a31582ced60d26cd7c64d746b1449864
   OCI specs: 1.0.1-dev

createPodSandbox for pod "metrics-server-7566d596c8-j8qvr_kube-system(78d9aeb0-ec60-4f47-84a9-1d50062d0442)" failed: rpc error: code = Unknown desc = failed to create containerd task: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"process_linux.go:415: setting cgroup config for procHooks process caused \\\"failed to write \\\\\\\"b *:* m\\\\\\\" to \\\\\\\"/sys/fs/cgroup/devices/kubepods/besteffort/pod78d9aeb0-ec60-4f47-84a9-1d50062d0442/4f8df6b8d065fd9e355e87f8fbcf20fa4a9a8b19dbb7caabb5eba4bf37b1da04/devices.allow\\\\\\\": write /sys/fs/cgroup/devices/kubepods/besteffort/pod78d9aeb0-ec60-4f47-84a9-1d50062d0442/4f8df6b8d065fd9e355e87f8fbcf20fa4a9a8b19dbb7caabb5eba4bf37b1da04/devices.allow: operation not permitted\\\"\"": unknown

I found the problem. I built the image with the wrong AGENT_VERSION

@skaegi I have been able to reproduce your issue. I did a git bisect accross repos and saw that this commit is causing the issue:
https://github.com/kata-containers/agent/commit/a88af321f7c591404b0316320c46591fa8250992
Let me see how we can fix this.

The commit https://github.com/kata-containers/agent/commit/a88af321f7c591404b0316320c46591fa8250992 restricts access of the container to the VM rootfs devices, whereas docker running in the container should write to the container's /sys/fs/cgroup.
I am not sure why the container would need access to the VM rootfs device.
@devimc @bergwolf Any idea?

Awesome thanks @amshinde that makes sense. FWIW I tried 1.11.2 and have the same problem.

@skaegi Changing that patch to below fixes the issue:
diff --git a/device.go b/device.go
index ae95572..01ee559 100644
--- a/device.go
+++ b/device.go
@@ -496,7 +496,7 @@ func updateDeviceCgroupForGuestRootfs(spec *pb.Spec) {
                Major:  devMajor,
                Minor:  devMinor,
                Type:   "b",
-               Access: "rwm",
+               Access: "rw",
        }

        spec.Linux.Resources.Devices = append(spec.Linux.Resources.Devices, nvdimmCg)

From the error it looks like docker needs "m" access for block devices ie ability to create device nodes for block devices.
I am not entirely sure why the nested docker container needs this, the config.json does not contain any such device cgroup entry, so not entirely sure why libcontainer tried to add the devices.allow entry for block devices.
@bergwolf @devimc Let me know if have knowledge about it.
@bergwolf By the way, the above patch does not allow read/write access for the rootfs, which means it still addresses the CVEs we had fixed previously. Let me know if the patch is good, I'll raise a PR for it in the agent repo.

@amshinde I'm using the latest version of kata-agent, I started a debug console to check the device cgroup of a container, the problem is that I don't see any device constraint, could you check that?
bash-4.2# ls /dev/pmem0*
/dev/pmem0  /dev/pmem0p1
bash-4.2# mount | grep pmem
/dev/pmem0p1 on / type ext4 (ro,relatime,dax,errors=remount-ro,data=ordered)
bash-4.2# pwd
/sys/fs/cgroup/devices/docker/9e3e1dc87b80daf70d573774257de495a9e6bb6a364d847c1dcb446118426ece
bash-4.2# cat devices.list
a *:* rwm
bash-4.2# kata-agent --version
kata-agent version 1.12.0-alpha0-e01f28988780f43b1d023dd46272f334d5ec8230

Thanks @amshinde I'll rebuild and try that patch.

@devimc Thats strange, I do have a test that checks whether you can read/write/mknod to the rootfs and I do see the desired behaviour when I toggle the device cgroup. Let me create a debug image and check.
I am not sure about the devices.list, but I think you atleast should see entry under devices.allow.

@amshinde
bash-4.2# cat devices.allow
cat: devices.allow: Invalid argument

fwiw I fail the same way with 1.12.0-alpha0

yes, 1.12.0-alpha0 would fail as well.
Let me know if that patch works for you. I tried it at my end and don't see the error any more.
For some reason, docker adds permissions to create device nodes for all block devices which conflicts with the approach taken by us to restrict all permission to the rootfs block device.
Will be adding an integration test for this to make sure we dont break in the future.
cc @GabyCT

Thanks @amshinde -- I can confirm your patch works.
I created my own build for our environment with and without your patch on top of 1.12.0-alpha0 and it worked with your patch and failed as above without it.

@amshinde this all works well for me now. I have the luxury of my own build environment so can do the patching myself but it might be a good idea to check a fix in for 1.12/master and probably for stable-1.11 too as anyone else trying this out for the first-time will fail.

@skaegi Was away for a few days. I have now raised a PR to address this. Will backbort to stable as well.
https://github.com/kata-containers/agent/pull/807

We run into the same issue, about to see if the agent patch provided by @amshinde will work for us.

@amshinde  so is this  not a virtiofs issue, correct ?
Can we close this issue now?

@jcvenegas Yes, not related to virtiofs. Fix has been merged in master and stable branches. Closing this.

@amshinde do you know if the merge of commit to https://github.com/kata-containers/agent stable-1.11 branch would also refresh packages on http://download.opensuse.org/repositories/home:/katacontainers:/releases:/x86_64:/stable-1.11/xUbuntu_18.04/ ?


[Bug]: Page ordering is incorrect on forking an app

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Page ordering is incorrect on forking an app
Steps To Reproduce

Create an app with multiple pages
Fork the app onto the same/different workspace
Notice that the page ordering of the forked app is different from the original app

Public Sample App
No response
Environment
Production
Severity
Medium (Frustrating UX)
Issue video log
https://www.loom.com/share/924d992ebde9411b855c786acd6f695e?sid=84294046-2306-4cba-8bd4-812de8115cff
Version
Production v1.16.0

@rohan-arthur I'm assuming this regressed due to IDE changes. Please reassign if it doesn’t come under the purview of the IDE pod

@laveena-en please add the correct product tags when creating an issue

Also looks like a duplicate of #9016


Add command to set security group of instance during create or reset of instance

We have a need where we need to reset the instance and install the master solution every once in a while. With current pac command, most of the stuff can be automated except for setting security group of the instance. Since the security group cannot be set while running reset command, the service account that is being used to automate the process loses access after the reset is complete because of missing security group. It would be nice to set the security group during the process of reset of instance so that when the instance comes back after reset, the service account won't lose access and can perform other tasks against the environment. Same request during the creation of the new instance.
example:
`
pac  admin reset -env [URL or ID] -security-group-id [AD-Group-Guid-ID]

Noticed in pac 1.17.4 there's now a --team-id option in pac admin create.  Might this help?

@filcole
don't think it adds the security group, atleast it didn't for mine.

@filcole  i believe you might be right.


Update Readme.md

Why exactly did you open this?

Chinese documents have no

This can probably be closed.


Text Disappears After Page Reroute

I am resolving gatsby-plugin-scroll-reveal in my gatsby-config.js file, I have it installed in my node_modules, and it is working initially. The issue I'm encountering is that when I go to an interior page, then back to the home page, where I have text animating up using the plugin, the text is gone and I can't find anything in the source that would be causing it to do that.
Here is my hero.js component:
import React from "react"

const IndexHero = () => (

Hi, my name is

Elijah Kleinsmith

                {/*
 */}

                Some text...

                <a<EMAIL_ADDRESS>

                    <button
                        className="special"
                        style={{
                            padding: '12px 30px',
                            fontSize: 14,
                            backgroundColor: 'transparent',
                            color: '#EE4E31',
                            borderColor: '#EE4E31',
                            textTransform: 'uppercase',
                            border: '1px solid',
                            transition: 'all 400ms'
                        }}
                    >
                        Get In Touch
                    </button>

)

export default IndexHero

One other strange thing: any time I set data-sal-delay value to above 1000, it runs at the default delay instead of the set delay time.
Any help is very much appreciated.
Thank you for building this!

Encountered the similar issue as well.
When the same page is re-rendered or re-routed with gatsby <Link>, all the element wrapped by the

    ...

will disappear and does not reveal upon scroll.
That is, those elements seems either not initialized or were initialized in the bad state.
Any guidance on how to resolve this would be much appreciated!

I had the same problem and I just added the dependency "sal.js" to my page and started the initialization with a useEffect.
import sal from 'sal.js';

const IndexPage = () => {
  useEffect(() => {
      sal();
    }, []);

  return (

Hello

  )
}

I had the same problem and I just added the dependency "sal.js" to my page and started the initialization with a useEffect.
import sal from 'sal.js';

const IndexPage = () => {
  useEffect(() => {
      sal();
    }, []);

  return (

Hello

  )
}

Hi @nlenaerts could you help elaborate how import sal from 'sal.js' work in the context of using gatsby-plugin-scroll-reveal? My impression is gatsby-plugin-scroll-reveal does not explicitly made sal.js available to JSX in gataby. Thanks

I had the same problem and I just added the dependency "sal.js" to my page and started the initialization with a useEffect.
import sal from 'sal.js';

const IndexPage = () => {
  useEffect(() => {
      sal();
    }, []);

  return (

Hello

  )
}

This solution worked for me! Thanks!


Set putRequiresUpdate and putStreamRequiresUpdate to false

Please see https://github.com/thephpleague/flysystem/pull/709 as that issue contains the rationale and code to support these changes.

Fixed by https://github.com/thephpleague/flysystem-aws-s3-v3/commit/05b2bdcdef2d45210ba6c066576bb061e30eb289


[Document Intelligence] Generate 1.0.0-beta.3 version

Regeneration done
Tests in sync with latest src
Live tests ✅
Migrated to ESM and vitest
Added new tests for the new features
Added custom code to support

the "completed" poller status for batch analysis /documentModels/{modelId}:analyzeBatch
getting operation id from the poller
and the new /documentModels/{modelId}/analyzeResults/{resultId}/pdf and /documentModels/{modelId}/analyzeResults/{resultId}/figures/{figureId} methods

/azp js - documentintelligence - ci

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure-rest/ai-document-intelligence


Improvement: Save default values as null when resetting to default

If I change a value in a non-default locale and save a Page, for example the Title and save it, Things are saved as expected:
mysql> SELECT Title, Title_en_NZ, Title_en_US FROM SiteTree WHERE ID = 1;
+----------+-------------+-------------------+
| Title    | Title_en_NZ | Title_en_US       |
+----------+-------------+-------------------+
| Homepage | NULL        | My American Title |
+----------+-------------+-------------------+
1 row in set (0.00 sec)

If I then click on the locale indicator to reset it to its default value and save it again, the value is saved as the default value but as the string literal rather than acting as a transparent fallback as it would if null:
mysql> SELECT Title, Title_en_NZ, Title_en_US FROM SiteTree WHERE ID = 1;
+----------+-------------+-------------+
| Title    | Title_en_NZ | Title_en_US |
+----------+-------------+-------------+
| Homepage | Homepage    | Homepage    |
+----------+-------------+-------------+

This means if I go through and change the default locale's value it doesn't reflect to the non-default locale:
mysql> SELECT Title, Title_en_NZ, Title_en_US FROM SiteTree WHERE ID = 1;
+------------------+------------------+-------------+
| Title            | Title_en_NZ      | Title_en_US |
+------------------+------------------+-------------+
| Homepage changed | Homepage changed | Homepage    |
+------------------+------------------+-------------+

Improvement request
When resetting to a default value we should set the localised field to null to allow it to be transparent. This would match the expectation for when you first created the page and default changes would be reflected everywhere.

I'm thinking something like this - not sure of any flow on effect yet:
diff --git a/code/extensions/FluentExtension.php b/code/extensions/FluentExtension.php
index d26d78d..078c68a 100644
--- a/code/extensions/FluentExtension.php
+++ b/code/extensions/FluentExtension.php
@@ -740,6 +740,15 @@ class FluentExtension extends DataExtension
                     if (!empty($updates['fields'][$defaultField]) || $this->isFieldNullable($field)) {
                         $updates['fields'][$field] = $updates['fields'][$defaultField];
                     }
+
+
+                    // If the localised field has been reset to the default value (i.e. they're the same value)
+                    // we should store it as null to allow change transparency from the default locale in future.
+                    if ((!empty($updates['fields'][$defaultField]))
+                        && ($updates['fields'][$updateField] === $updates['fields'][$defaultField])
+                    ) {
+                        $updates['fields'][$updateField] = null;
+                    }
                 }
             }

Now that I can triage my own issue I'm going to close it =) It's still an issue, but due to the way that Fluent works, it's not going to be setting the values back to null again
If anyone else experiences this then we can reopen it as an enhancement for future


Tls

Kyle added functionality to allow support for using TLS connections and a flag to allow self-signed certificates when connecting with gears-cli.
Default behavior when using tls connections is to require valid certs.  the self-signed flag must be explicitly passed to turn off cert validation.

Is it possible to get this merged as I need the functionality?

@deji-alaran I still think we should allow providing a certificate file to make the feature complete.

Handled here: https://github.com/RedisGears/gears-cli/pull/32


Removed extra UI from inventory and orders pages(#251xtg2)

Related Issues

Closes #
Short Description and Why It's Useful

Screenshots of Visual Changes before/after (If There Are Any)

IMPORTANT NOTICE - Remember to add changelog entry
Contribution and Currently Important Rules Acceptance

[ ] I read and followed contribution rules


Metron-302 Build Common Deployment RPM

Create base spec for metron rpm's
https://issues.apache.org/jira/browse/METRON-302

Closing this PR - this will instead be included as part of another merged PR


Retrieve the total hits value that is locked during the PIT creation

In point in time pagination technique, it is considered that OpenSearch locks a set of segments for those indexes, freezing them in time. So when we create a pit id using the query POST /_search/point_in_time?keep_alive=1d .
We need to get the total hits for the particular PIT created.
Like the below query:
POST //_search?track_total_hits=true&size=0
{
pit:{id:"xxxxxxxx"}
}

Cc: @bharath-techie

@Raja18lakshmi -- can you please add some more details?
Would a match-all-docs query with size:0 executed against the PIT provide the total hit count you're looking for?
Can you please clarify what you're trying to do with the total hit count? Thanks

Based on @msfroh 's comment :
Here's an example to get total hits with a sample request:
{
    "pit": {
	"id":  "<pit id>
    },
    "size": "0",
    "query": {
        "match_all": {}
    }
}

Sample response :
hits.total.value gives the total hits
{
    "pit_id": "<pit_id>",
    "took": 3,
    "timed_out": false,
    "_shards": {
        "total": 2,
        "successful": 2,
        "skipped": 0,
        "failed": 0
    },
    "hits": {
        "total": {
            "value": 5,
            "relation": "eq"
        },
        "max_score": null,
        "hits": []
    }
}


[SPARK-7515] [DOC] Update documentation for PySpark on YARN with cluster mode

Now PySpark on YARN with cluster mode is supported so let's update doc.
Author: Kousuke Saruta<EMAIL_ADDRESS>Closes #6040 from sarutak/update-doc-for-pyspark-on-yarn and squashes the following commits:
ad9f88c [Kousuke Saruta] Brushed up sentences
469fd2e [Kousuke Saruta] Merge branch 'master' of https://github.com/apache/spark into update-doc-for-pyspark-on-yarn
fcfdb92 [Kousuke Saruta] Updated doc for PySpark on YARN with cluster mode

Merged build triggered.

Merged build started.

Test build #34985 has started for   PR 6842 at commit de025cd.

Test build #34985 has finished for   PR 6842 at commit de025cd.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

This looks like a break introduced in a different commit, fff8d7ee6c. Not sure why that wasn't caught by the automated tests.

Merged build triggered.

Merged build started.

Test build #35042 has started for   PR 6842 at commit 0b83648.

Test build #35042 has finished for   PR 6842 at commit 0b83648.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

LGTM merging into master 1.4

I just merged this. Could you close this PR?


How can i

Accidentally clicked enter sorry,
Well i was gonna ask how can i use the email account verification?

No worries, could you provide more details on what sort of workflow you're hoping to use with email account verification? Are you perhaps looking to implement magic link sign in or similar?
One way to enforce email verification would be t call supabase.auth.signup() and then ensure you have correctly configured the settings under Authentication > Settings > Email  and click Enable Email confirmation to ensure that users are only verified after they confirm/verify their emails

Sorry for not being clear. I wanted to ask, how can I confirm email addresses? When i do supabase.auth.signup() the email sent has a localhost link and a key. Do i have to handle that in my server? If so, how can i do that?

Also how can i use the hcaptcha protection?

When you click on the link sent to your email a request is sent to Supabase Auth to verify the token in the link. The user is then marked as confirmed and redirected to your site .
For HCaptcha, you can take a look at this guide and we will also have video tutorials coming soon.
Hope this helps and let us know if you have further questions

Thanks a lot!


"CUSPARSE_SPMV_CSR_ALG1" is undefined

Compiling mfem with cuda support on ORNL Summit using the cuda 11.2.0 module.
Full error mssage
$ nvcc -Xcompiler=-fPIC  -g -Xcompiler=-Wall -std=c++14 -x=cu --expt-extended-lambda -arch=sm_70 -ccbin mpicxx \
-I/ccs/home/jfaibussow/petsc/arch-olcf-summit-streams-debug/include \
-I/ccs/home/jfaibussow/petsc/arch-olcf-summit-streams-debug/include  -I/ccs/home/jfaibussow/petsc/include \
-I/ccs/home/jfaibussow/petsc/arch-olcf-summit-streams-debug/include -I/sw/summit/cuda/11.2.0/include  \
-c linalg/complex_operator.cpp -o linalg/complex_operator.o

linalg/sparsemat.cpp(694): error: identifier "CUSPARSE_SPMV_CSR_ALG1" is undefined

Version info
Output of make info:  mfemInfo.txt
$ nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2020 NVIDIA Corporation
Built on Mon_Nov_30_19:09:01_PST_2020
Cuda compilation tools, release 11.2, V11.2.67
Build cuda_11.2.r11.2/compiler.29373293_0

$ echo $CUDA_DIR
/sw/summit/cuda/11.2.0

As a workaround I plopped
#define CUSPARSE_SPMV_CSR_ALG1 CUSPARSE_CSRMV_ALG1

at the top of linalg/sparsemat.cpp and everything compiled cleanly.

I'm confused we're supposed to have addressed this in: https://github.com/mfem/mfem/pull/2200

Could you check if replacing #if CUDA_VERSION >= 11020 with #if CUDA_VERSION >= 11021 in linalg/sparsemat.cpp solves this issue?

Could you check if replacing #if CUDA_VERSION >= 11020 with #if CUDA_VERSION >= 11021 in linalg/sparsemat.cpp solves this issue?

This works.

I just tried on Lassen, the problem is that if I change for #if CUDA_VERSION >= 11021, and use cuda-11.2.0, then I get the following warning:
linalg/sparsemat.cpp:724:119: warning: 'CUSPARSE_CSRMV_ALG1' is deprecated: please use CUSPARSE_SPMV_CSR_ALG1 instead [-Wdeprecated-declarations]
cusparseSpMV(handle, CUSPARSE_OPERATION_NON_TRANSPOSE, &alpha, matA_descr, vecX_descr, &beta, vecY_descr, CUDA_R_64F, CUSPARSE_CSRMV_ALG1, dBuffer);
                                                                                ^
/usr/tce/packages/cuda/cuda-11.2.0/nvidia/bin/../targets/ppc64le-linux/include/cusparse.h:6314:1: note: 'CUSPARSE_CSRMV_ALG1' has been explicitly marked deprecated here
CUSPARSE_CSRMV_ALG1 __attribute((deprecated("please use CUSPARSE_SPMV_CSR_ALG1 instead"))),

That confuses me about what version of cuda Summit is actually using, it doesn't seem to behave the same...

Yeah it does seem like summits version is a bit wonky. When loading the cuda module on summit one is met with:
---------------------------------------------------------------------------------------------------
There are messages associated with the following module(s):
---------------------------------------------------------------------------------------------------

cuda/11.2.0:
  This modulefile is provided for testing purposes only. If you encounter
  issues, please report them to<EMAIL_ADDRESS>
---------------------------------------------------------------------------------------------------

I figured this might refer to some experimental backend implementations not missing features... I will send mail to the ornl help desk about this. Maybe they have more insight.

Alrighty so after getting in touch with the ORNL folks they mentioned that:

Cuda 11.3.0 documentation, where CUSPARSE_CSRMV_ALG1 was deprecated. In the 11.2.0 documentation (https://docs.nvidia.com/cuda/archive/11.2.0/cusparse/index.html#cusparse-generic-function-spmv) you can see that CUSPARSE_CSRMV_ALG1 is the only one present and CUSPARSE_SPMV_CSR_ALG1 is not defined at all. That missing definition is probably what you are running into in this case.

With that I inspected the respective $CUDA_[HOME|DIR]/include/cusparse.h for both Lassen and Summit and lo and behold
Lassen:
#define CUSPARSE_VER_MAJOR 11
#define CUSPARSE_VER_MINOR 4
#define CUSPARSE_VER_PATCH 1
#define CUSPARSE_VER_BUILD 1152

Summit:
#define CUSPARSE_VER_MAJOR 11
#define CUSPARSE_VER_MINOR 3
#define CUSPARSE_VER_PATCH 1
#define CUSPARSE_VER_BUILD 68

So maybe its not the cuda version that needs checking but the cusparse version.

@Jacobfaib Would you have an idea of what would be the correct value to check for CuSparse?
Also did you see that comment by @adam-sim-dev

@Jacobfaib Would you have an idea of what would be the correct value to check for CuSparse?
Also did you see that comment by @adam-sim-dev

Yeah which is why I am doubly confused as to why summits cusparse doesn't have this value defined. In fact, it does not even throw a deprecation warning for CUSPARSE_CSRMV_ALG1! I'm starting to think that maybe the summit cusparse build is defective. I grepped the whole of the cuda directory for CUSPARSE_SPMV_CSR_ALG1 and it came up completely empty.

I was thinking that replacing #if CUDA_VERSION >= 11020 with something like #if CUSPARSE_VER_MAJOR >= 11 && CUSPARSE_VER_MINOR >= 4 could be the answer, but I'm not sure...

Hey guys, do we have a clear resolution for this? Is it something that should be in mfem-4.3?

Not completely, the cusparse documentation suggests that 11.2.1 (see https://github.com/mfem/mfem/issues/2164#issuecomment-826440946) should be the right cusparse version, but https://github.com/mfem/mfem/issues/2336#issuecomment-863297380 suggests that 11.4 is the right version in the case of Summit...

I might be confusing the cuda version and the cusparse version though.
I think we could try replacing #if CUDA_VERSION >= 11020 with #if CUSPARSE_VER_MAJOR >= 11 && CUSPARSE_VER_MINOR >= 4, this will work for Lassen and Summit, but I don't find any documentation on the cusparse versions to be sure it's the right condition.

I'd say use the condition CUSPARSE_VERSION >= 11400 where CUSPARSE_VERSION is defined in cusparse.h as
#define CUSPARSE_VERSION (CUSPARSE_VER_MAJOR * 1000 + \
                          CUSPARSE_VER_MINOR *  100 + \
                          CUSPARSE_VER_PATCH)

Judging by the posts above, this should work on both Lassen and Summit with their respective installs of CUDA 11.2.0.
If this is not the exact cutoff version, we can adjust again later, if this comes up again.

@Jacobfaib do you want to propose a PR with the above suggested change?

@Jacobfaib do you want to propose a PR with the above suggested change?

Yeah sure, I'll check that the cusparse version check works on the machines I've got access to.

What is the status of this issue? Just met the same error on a local machine, with cuda11.2 and this configuration for cusparse
#define CUSPARSE_VER_MAJOR 11
#define CUSPARSE_VER_MINOR 3
#define CUSPARSE_VER_PATCH 1
#define CUSPARSE_VER_BUILD 68
#define CUSPARSE_VERSION (CUSPARSE_VER_MAJOR * 1000 + \
                          CUSPARSE_VER_MINOR *  100 + \
                          CUSPARSE_VER_PATCH)

ping: @Jacobfaib, @YohannDudouit

I'll open a PR tomorrow morning (for real this time!).

Discussion continued in #2445.


Enhanced Ui of Component Card

Description
Enhance UI of Component Cards and Add Animations for Better User Experience
Description:
Enhancing the UI of component cards and integrating animations can significantly improve the user experience. This issue outlines the proposed enhancements and their expected benefits.
Enhancements:
Visual Hierarchy: Use different font sizes and weights to distinguish titles, subtitles, and body text.
Highlight important information with color, bold text, or icons.
Color Scheme: Choose a color palette that aligns with our brand.
Use contrasting colors for text and background to improve readability.
Interactive Elements: Incorporate buttons and links with clear call-to-actions (CTAs).
Ensure buttons are easy to identify and click.
Animations:
Smooth Transitions: Implement animations for transitions between different states (e.g., hover effects, page changes).
Aim for smooth and natural transitions to reduce cognitive load.
Guided Interactions:
Use animations to guide users' attention to important elements or actions.
For example, subtle animations on CTA buttons can draw attention without being intrusive.
Feedback and Affordance:
Provide visual feedback for user interactions, indicating actions have been recognized (e.g., button presses, form submissions).
Enhance the sense of control and satisfaction for users.
Attachments/References:
https://github.com/Rakesh9100/Beautiify/assets/128406559/56acd49e-6175-4989-8639-94730f9e0275
Screenshots

Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Please @Rakesh9100 assign this issue to me!

Please @Rakesh9100  assign this issue to me, i can add some more UI in this

Pls review this @saurabhsingh720

@Rakesh9100
It makes the website looks better.
We can assign her

@mahak0711
You have to add icons as well that are used in the recent components

@saurabhsingh720 okay,i'll add it.

@saurabhsingh720 Please review it.I added the new components

@mahak0711
Add icons make it look good.
Currently it is looking very empty

@mahak0711 your img is not opening

@saurabhsingh720

@mahak0711
It is not looking good
Make the icon centre

@saurabhsingh720 made the changes

@mahak0711 looks cool.
Make the proper alignment of all the components


Custom number of weeks for chart

You define the getCommitData() function's input here:
https://github.com/HCLonely/hexo-calendar/blob/7122b0f42708e19af42108052ad07abc12d79fc7/index.js#L22
However, there doesn't appear a way to change the default 40 weeks to a different value. Can you update this?

You can use the hexo gc -w=10 command to change the number of weeks to 10.

Thanks, can you add that detail to the readme file?


Did this fix a security vulnerability?

https://github.com/srikanth-lingala/zip4j/issues/400
Reaching out to ask if this fixed a security vulnerability, or was it just a bug? If it was a bug, do you need assistance with vulnerability disclosure and getting a CVE number assigned?

If I understand it correctly, that was only a bug without any security impact.
Zip4j treats an entry with the name / as being the directory to which the files are extracted (so this normally has no effect because that directory already exists). However, the issue was that for the Zip Slip check after resolving the / name the results were:

outputCanonicalPath: extract-dir/
outputFile.getCanonicalPath(): extract-dir

So the Zip Slip check performing startsWith was erroneously detecting this as Zip Slip attack.
After the fix it is now extract-dir/ in both cases, so startsWith passes.


Pod creation fails with "unable to allocate IP via local cilium agent: [POST /ipam][502] postIpAMFailure  range is full"

Summary
Pods fail to deploy with errors like this:
Warning  FailedCreatePodSandBox  20m (x2412 over 65m)  kubelet, minikube  (combined from similar events): Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "49a1e22aa6f14f5da53b6ab0fe253a20303246c3e31299bbd489b09a814cab12" network for pod "coredns-5c98db65d4-h5vwr": NetworkPlugin cni failed to set up pod "coredns-5c98db65d4-h5vwr_kube-system" network: unable to allocate IP via local cilium agent: [POST /ipam][502] postIpamFailure  range is full

Description
By default, when Cilium starts up it detects all routes configured on the node and blacklists those ranges from its IP Allocation Management (IPAM) module. This is to prevent accidental allocation of the same IP in multiple locations in the cluster.
Depending on other components that are configured in the node (eg docker networking), they may choose an IP range to allocate IPs from and/or configure routes in the routing stack to determine how to forward traffic to those IPs to their destinations. If this range
Symptoms
When deploying containers, this message is seen (eg in kubectl logs):
... unable to allocate IP via local cilium agent: [POST /ipam][502] postIpamFailure  range is full

Cilium status describes that the IP range is full or almost full:
$ cilium status | grep IPAM
IPAM:                   IPv4: 65534/65535 allocated from <IP_ADDRESS>/16,

Cilium logs have lines like this, and the range is the same or a superset of the range in the cilium status output above:
2019-10-08T12:20:24.210886728Z level=info msg="Blacklisting local route as no-alloc" route=<IP_ADDRESS>/8 subsys=ipam

The route table shows a route for the range which does not point towards the cilium_host device:
# ip r s
default via <IP_ADDRESS> dev ens10
<IP_ADDRESS>/8 via <IP_ADDRESS> dev ens10

Resolution

Kubernetes: Reconfigure --cluster-cidr in controller-manager and kube-proxy (if applicable) so that the pod IP allocation range does not conflict with existing routes on cluster nodes.

Note that kubernetes may not modify the podCIDR for existing nodes, you may need to redeploy the nodes.

Generic: Remove the routes that overlap with the podCIDR from individual nodes
Workaround: Configure Cilium --blacklist-conflicting-routes=false. Note however if there is another component allocating IPs from this range then this may lead to conflicts between IP addresses allocated by Cilium vs. IPs allocated by other components on your nodes which manage conflicting routes which could lead to connectivity issues for network endpoints with the same IP.

A user on slack also observed this when running minikube with --enable-default-cni, as it will automatically configure a bridge with a conflicting route via its default CNI. If this option is not passed, then no CNI will be established at first and you should be able to install cilium either via YAMLs directly or through helm v2 (templating only) or helm v3 (install or via templating).

Cilium will no longer trigger this error in Cilium 1.9 or later.


Android: 'notification' event is never called when the app is in the background

Hi There,
I am having an issue with your plugin: I am unable to receive the notification event in the app when it is in the background.
When in the foreground the event works fine.
I am using android 4.4.2
I have tried various versions of the plugin with the same result across the board, 1.3.0, 1.5.1, 1.5.2
I am using the ionic framework:
ionic cli version: 1.7.12
cordova version: 5.4.1
The JSON that is sent to GCM is as follows:
{
  "registration_ids": [
    "xyz"
  ],
  "content_available": true,
  "data": {
    "silent": "message here"
  }
}

With the above, the notification event is never fired regardless of further actions
If I use something like:
{
  "registration_ids": [
    "xyz"
  ],
  "content_available": true,
  "notification": {
    "title": "title here",
    "message": "message here"
  }
}

Then the notification is displayed to the user, however there is still no event.
If I reopen the app by selecting the icon, no event.
If I reopen the app by selecting the notification shown, then I get an event.
As far as I understand things this is not the intended functionality for the plugin and the app should receive the event while it is in the background. This is how things work when I tested on iOS.
Any help / suggestions would be greatly appreciated :)
Thanks,
Jon

so do I

@jwbeech the value to tell Android to raise an event when the app is in the background is
{
  "registration_ids": [
    "xyz"
  ],
  "data": {
    "silent": "message here",
    "content-available": "1"
  }
}

https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/PAYLOAD.md#background-notifications

@ikromy No error events received with my implementation, you must have an error with your registration or GCM communication setup.
The communication and parameters don't change between foreground notifications (which work fine) and background ones.
For background notifications I get no activity in the app at all, no errors, no notifications.
Response from GCM also reports no errors:
{"multicast_id":7157479278139605882,"success":1,"failure":0,"canonical_ids":0,"results":[{"message_id":"0:1452779796161447%4f1c2b144f1c2b14"}]}

@macdonst you beauty! Working, thanks muchly!!

Hi.
I am sending this with GCM server:
{
"to": " XXXXXXX",
"data": {
"Nick": "Mario",
"Room": "PortugalVSDenmark",
"content-available": "1"
}
}
in your link descibing the background notification it's not very clear where should the "content-available" property be... inside the data payload!
now how about IOS, I have been trying to send the same message but no... the callback does not seem to be triggered in backgournd when this message is send...

GCM uses slightly different syntax.  Make it  "content_available":"true".
Also see https://developers.google.com/cloud-messaging/http-server-ref
On Fri, Jan 29, 2016 at 4:47 PM, clembo590<EMAIL_ADDRESS>wrote:

Hi.
I am sending this with GCM server:
{
"to": " XXXXXXX",
"data": {
"Nick": "Mario",
"Room": "PortugalVSDenmark",
"content-available": "1"
}
}
in your link descibing the background notification it's not very clear
where should the "content-available" property be... inside the data payload!
now how about IOS, I have been trying to send the same message but no...
the callback does not seem to be triggered in backgournd when this message
is send...
—
Reply to this email directly or view it on GitHub
https://github.com/phonegap/phonegap-plugin-push/issues/503#issuecomment-177033724
.

Thanks for your quick answer.
What I just posted works on GCM on android in background.
For ios,
I just tried to switch "data" to "aps" as you wrote in the doc... and also content available to true
-->
{
"to": "nYYYYY",
"aps": {
"Nick": "Mario",
"Room": "PortugalVSDenmark",
"content-available": "true"
}
}
until now no success...
one stupid question:
on android, in the notificationCallback, I send an http request to my server, on which there is a trace, that is how I that my notificationCallback has been called (even in background).
Can this work on ios? I think yes... if no why it does not? (ios prevent me from making http request in background? PS: I have enabled the fetch background functionnality...)

Two things:
First, you have a "-", and not an underscore "_".
Second, in reading the docs, I think Android does this automatically, so
not sure why it would be needed in that case.  I haven't been able to get
background notifications to execute in Android though.
On Fri, Jan 29, 2016 at 5:02 PM, clembo590<EMAIL_ADDRESS>wrote:

Thanks for your quick answer.
What I just posted works on GCM on android in background.
For ios,
I just tried to switch "data" to "aps" as you wrote in the doc... and also
content available to true
-->
{
"to": "nYYYYY",
"aps": {
"Nick": "Mario",
"Room": "PortugalVSDenmark",
"content-available": "true"
}
}
until now no success...
one stupid question:
on android, in the notificationCallback, I send an http request to my
server, on which there is a trace, that is how I that my
notificationCallback has been called (even in background).
Can this work on ios? I think yes... if no why it does not? (ios prevent
me from making http request in background? PS: I have enabled the fetch
background functionnality...)
—
Reply to this email directly or view it on GitHub
https://github.com/phonegap/phonegap-plugin-push/issues/503#issuecomment-177035908
.

thank you very much.
at last I managed to get it in the bakcground for ios:
{
"to": "YYYYYYYY",
"notification": {
"content_available": "true",
"body": "great match!",
"title": "Portugal vs. Denmark",
"icon": "myicon"
}
}
I guess it would be nice to put this in the doc....
(the ios exemple is not silent...)
thanks again!

(on IOS you will notice that we have to use "notification" on not "data"....)