Current Operations (MultiDisplay) (Operations View) item has issues

Current Operations (MutliDisplay) (Operations View) owned by Demonstration: 59ec3b3e65f344f2922c6f68eaf0c142

[ ] No description
[ ] No credits
[ ] No summary
Opening item downloads Operations Dashboard, Sign in to TEM2016, message pops up in Ops Dashboard "Warning. The following data sources are not accessible ".
Operations Dashboard is open and can interact with some of the stuff on the map. Not sure what to expect here.

@mfunk For items owned by Demonstration, we really aren't worried about the description, credits and summary. As far as the error "The following data sources are not accessible", this ops view references the service Military/AirC2_MilitaryAirTracks/MapServer which has to be published manually by users. Instructions for publishing this service are being written and will be provided in the Ops Server release, therefore this service will exist at some point on a deployed Ops Server, so I will close this issue. Thanks.


Some improvements for the procedure

We discussed in #36 what needed to be done. So after this is merged it will close #36
To get this updated, all that you should need to do would be to run the management command insert_procedures again

To be clear, once this style issue is addressed, and you have confirmed the other behaviour, please merge in and deploy.

I've confirmed that I'm seeing entries in green_presenting during the execution of backfill.


Add first draft of "Proof Guide" document for review.

This PR adds a "Cookbook" for how to develop and run CBMC proofs for the C code in this repo.
The guide uses the proof of poly_tobytes() as an example, so PR #235 should be reviewed and merged first.

I think this should also be reviewed by someone who does not know CBMC. @mkannwischer What about you? I imagine you don't have time until November?

High-level comment: should there be any links towards more-general CBMC training (like https://model-checking.github.io/cbmc-training/)?

Most of that existing training material talks about using CBMC in "bounded model checking" mode, rather than "deductive sound contract-based proof" mode. I think pushing readers towards the former will cause confusion...

Rebased and squashed. Ready to approve and merge.


Add some details about cross-domain AJAX requests to the documentation.

Not sure if the style is correct, if I've added the right amount of detail, or if it's even in the right place. And I've only eyeballed the HTML so hopefully it's formatted correctly.

Hmm, I just noticed that the contributing docs say that pull requests should be submitted against the development branch instead of master. Let me know if want me to resubmit this against development.

Nah, for docs fixes master is fine.  :)
I will merge it this friday, thank you!
Cheers,
Carson
On November 13, 2016 at 11:05:38 PM, torohill<EMAIL_ADDRESS>wrote:
Hmm, I just noticed that the contributing docs say that pull requests should be submitted against the development branch instead of master. Let me know if want me to resubmit this against development.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Merged into dev, will be going out soon.  Thank you!


Messages at import time should go to the Python logger rather than stderr

Issue type
Feature Request
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
v2.15.0-rc1-8-g6887368d6d4 2.15.0
Custom code
No
OS platform and distribution
Mac Intel 14.1.1
Mobile device
No response
Python version
3.10.12
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
When I import tensorflow, it prints the following to stderr:
[Jan-09 17:37]$ poetry run python -c "import tensorflow as tf; print('stdout here')" > stdout.txt
2024-01-09 17:38:41.470429: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.

[Jan-09 17:38]$ cat stdout.txt
stdout here

Even if I configure my Python logger before importing tensorflow the results still go to stderr.
This is a problem for me because these messages show up in my logging system as errors.  When I query my logs, it looks like the app is unhealthy.
I know that I could silence messages using:
import os
os.environ['TF_CPP_MIN_LOG_LEVEL'] = '1'

import tensorflow as tf

Source
But I would prefer to keep these messages.
Possible solutions:
Ideal solution: Use the python logger.
Less ideal solution: Allow me to redirect these logs to stdout so they do not show up as errors.
Standalone code to reproduce the issue
Import tensorflow :)

Relevant log output
No response
Related issues and threads

Similar discussion for Keras: https://github.com/keras-team/keras/issues/1406#issuecomment-410437449
Similar feature request: https://github.com/tensorflow/tensorflow/issues/57553#issuecomment-1247641242
https://stackoverflow.com/questions/35911252/disable-tensorflow-debugging-information

Hi @JakeSummers ,
This might be intentional as it will give the users required info/warnings during import which may be useful for some users.As you know already this may be silenced by setting the environment variable TF_CPP_MIN_LOG_LEVEL. Also there are some logs generating from C++ backend passed to stderr directly.

@SuryanarayanaY

This might be intentional as it will give the users required info/warnings during import which may be useful for some users

This is totally useful and I do not want to silence these messages.
That being said, sending them directly to stderr is not best practice for Python packages.  Sending things through the logger is the standard behaviour.
This allows them messages to get redirected to the right place.  Two examples of when this doesn't work well:

Because these logs are getting send to stderr, they are raising alerts in our monitoring system.  I probably need to redirect them to stdout to prevent this from happening but would prefer to not need to do this for all stderr messages.
In some of my projects, we explicitly forward logs to to gcp-logging .  Since theses logs do not flow through the logger, these logs are lost.

I thought as a workaround, I would be able to do something like this:
def redirect_tensorflow_logs():
    with redirect_stderr(sys.stdout):
        import tensorflow as tf

But it appears that doesn't work.  See stackoverflow question: https://stackoverflow.com/questions/77796003/how-to-redirect-tensorflow-import-errors-from-stderr-to-stdout

This is the best workaround that I have found so far:
# NOTE this must be run prior to any other import tensorflow

from contextlib import redirect_stderr
from wurlitzer import sys_pipes
with redirect_stderr(sys.stdout):
    with sys_pipes():
        import tensorflow


Disable/remove Tabs swipe transition for low-end devices?

Apologies if this has been asked before (we are very new to Material UI but we are incredibly impressed with it) but is it possible to disable the swipe transition (I know it's a Material convention) when switching between tabs? We see a slight latency on low-end devices and would like to mitigate this as much as possible by removing the transition at devices <= sm breakpoint
E.g., something like the following would be superb...
<Tabs TabIndicatorProps={{disableTransition: true}} >
    <Tab disableRipple={this.props.width =< 992 ? true : false} label="Tab 1" className="text-capitalize"...
</Tabs>

Thank you all. Keep up the great work :)

@JavaJamie Great concern, please follow #10560.

 Thank you! :D


feature!: add windows support to worker fixture

What was the problem/requirement? (What/Why)
What was the solution? (How)
What is the impact of this change?
How was this change tested?
Was this change documented?
Is this a breaking change?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

🤯 I've been waiting for this

Wow! I've been waiting for this!

Wow, this is awesome! 🤯

Woah cool!


problem in application launch in chrome v 63 and 64

Hello
The polymer-skeleton app is working fine for me in firefox quantum.
But always get an error when I run the script "yarn dev:module" and try to open it in chrome v 63 or 64.
the error message is:
Uncaught TypeError: Cannot read property 'webpackHotUpdate' of undefined
at window.JSCompiler_renameProperty (bootstrap eeee88485f55dfc4e65b:4)
at module.bundle.js:728
window.JSCompiler_renameProperty @ bootstrap eeee88485f55dfc4e65b:4
(anonymous) @ module.bundle.js:728

Hi @mib-kamel, thanks for using the Skeleton :D
This is actually a known problem of Webpack, you can check out the related issue to solve partially this problem right now: https://github.com/PolymerX/polymer-skeleton/issues/71.
Let me know if you have other problems.

Yes, it worked thank you
Now how can I make a build which works in both firefox and chrome?

The build command will create two bundles both for Firefox alike browsers and Chrome alike browsers. The splitted build is only for the dev command. I planned to add both builds also for the dev command asap.

Worked.
Thank you :)


GPDR Delete User functionality

This PR

[x] Adds functionality to allow a user to delete all their information from OpenCFP

@chartjes
Quick note, as suggested by someone earlier, I have created a GDPR milestone, maybe we can remove the GDPR label, then?

@localheinz Implemented most of what you commented on, please take a look


ability to test not only packages & cleanup

Max, thanks for your contribution!
Questions:

It seems better to have "Test Commands" on Codeship be node start_test.js rather than have them as part of configure.sh. Do you agree?
Why cleanup start_test.js and phantom_runner.js?

Hi Mark,

Yes, I agree. It's more flexible
Testing on codeship be performed in the same directory as our source code., In my case, if I don't delete the files, the demeteorizer command tries to process the files and is running into an error.

Sorry - forgot about this. I merged it but commented out both node start_test.js and rm start_test.js phantom_runner.js. As discussed it's more flexible to explicitly call node start_test.js in your test settings... and you cannot rm start_test.js if you're going to be manually calling it.
I'll (finally) fill out the readme and suggest the rm statement.
Thanks again!

readme updated


Using ModuleAndWorkerAwareSpringBootApplication for workflow properties does not work properly

Using
vanillabp:
   workflow-modules:
        xxxx:
            resources-location: classpath:xxxxx/bpmn

brings an error since this property-file is not loaded before the adapters initialize.

The given error only appears, if the workflow-module's properties yaml is not in classpath:config/xxxxx.yaml.
To avoid name-clashes in classpath on running multiple workflow-module is own Spring Boot container, a path-prefix (the workflow-module-id) should be enabled:
classpath:xxxxx/config/xxxxx.yaml
As one can see as the name of the file is already the workflow-module-id there can't occur any name-clashes. However, typically there are also other configuration files used by the workflow-module which should be located in one directory: the path-prefix suggest:
xxxxx/
    config/xxxxx.yaml
    bpmn/camunda7/my-workflow.bpmn
    liquibase/master.yaml

The implementation will be adopted to support these locations (based on the default behavior Spring Boot https://docs.spring.io/spring-boot/reference/features/external-config.html#features.external-config.files):

classpath:xxxxx.yaml
classpath:config/xxxxx.yaml
classpath:xxxxx/xxxxx.yaml
classpath:xxxxx/config/xxxxx.yaml


vArmour Application Controller TemplateSpec Solution

Change(s):
See guidance below
Reason for Change(s):
This PR is part of template spec solution migration for solution vArmour Application Controller.
See guidance below
Version Updated:
2.0.0
Required only for Detections/Analytic Rule templates
See guidance below
Testing Completed:
The link for test results is - https://microsoftapc.sharepoint.com/:w:/r/teams/SentinelCATTeam/_layouts/15/Doc.aspx?sourcedoc={4D870C0C-3D27-49F9-84B8-9AD5C3468790}&file=Sentinel Solution Migration -TemplateSpec - vArmour Application Controller.docx&action=default&mobileredirect=true&share=IQEMDIdNJz35SYS4mtXDRoeQAfTNw3b-CZS2bLxPlEIRyzQ
See guidance below
This is an ISV solution.

Please check if we need to remove en-us from url shown in screenshot below


Replace SingleNodeLauncher with SimpleLauncher for MPI Mode

Description
Corrects a problem in the MPI mode implementation of HTEx. SingleNodeLauncher creates too many workers when running in MPI mode because it launches multiple copies of the executor onto the head node.
We want SimpleLauncher, which (instead) launches a single copy of the executor.
Changed Behaviour
Anything that uses the MPI mode will now create the desired number of workers.
Fixes
No issue, but see discussion in Slack.
Type of change
Choose which options apply, and delete the ones which do not apply.

Bug fix
Update to human readable text: Documentation/error messages/comments

i changed "executor" to "worker pool" in the merge message - another note for #3426


Maple crashes when I connect from Maple GUI

When I use the top bar toggle switch to connect maple disappears instantly, is this normal?
I also can't connect to my V2ray server using Maple and was wondering this crash on connect could be a hint.
here is my v2ray json config:
{
  "log": {
    "level": "warning"
  },
  "dns": {
    "servers": [
      "<IP_ADDRESS>",
      "<IP_ADDRESS>"
    ],
    "hosts": {
      "example.com": [
        "<IP_ADDRESS>",
        "<IP_ADDRESS>"
      ],
      "server.com": [
        "<IP_ADDRESS>"
      ]
    }
  },
  "inbounds": [
    {
      "address": "<IP_ADDRESS>",
      "port": 1087,
      "protocol": "http"
    },
    {
      "address": "<IP_ADDRESS>",
      "port": 1086,
      "protocol": "socks"
    },
    {
      "protocol": "tun",
      "settings": {
        "name": "utun8",
        "address": "<IP_ADDRESS>",
        "netmask": "<IP_ADDRESS>",
        "gateway": "<IP_ADDRESS>",
        "mtu": 1500,
        "fakeDnsInclude": [
          "google"
        ]
      },
      "tag": "tun_in"
    }
  ],
  "outbounds": [
    {
      "protocol": "failover",
      "settings": {
        "actors": [
          "vmess_out",
          "trojan_out"
        ]
      },
      "tag": "failover_out"
    },
    {
      "protocol": "chain",
      "settings": {
        "actors": [
          "vmess_tls",
          "vmess_ws",
          "vmess"
        ]
      },
      "tag": "vmess_out"
    },
    {
      "protocol": "tls",
      "tag": "vmess_tls"
    },
    {
      "protocol": "ws",
      "settings": {
        "path": "/websocket/"
      },
      "tag": "vmess_ws"
    },
    {
      "protocol": "vmess",
      "settings": {
        "address": "myserver",
        "port": 8080,
        "uuid": "myuuid"
      },
      "tag": "vmess"
    },
    {
      "protocol": "chain",
      "settings": {
        "actors": [
          "trojan_tls",
          "trojan"
        ]
      },
      "tag": "trojan_out"
    },
    {
      "protocol": "tls",
      "tag": "trojan_tls"
    },
    {
      "protocol": "direct",
      "tag": "direct_out"
    },
    {
      "protocol": "drop",
      "tag": "drop_out"
    }
  ],
  "rules": [
    {
      "ip": [
        "<IP_ADDRESS>",
        "<IP_ADDRESS>"
      ],
      "target": "failover_out"
    },
    {
      "domain": [
        "www.google.com"
      ],
      "target": "failover_out"
    },
    {
      "domainSuffix": [
        "google.com"
      ],
      "target": "failover_out"
    },
    {
      "domainKeyword": [
        "google"
      ],
      "target": "failover_out"
    },
    {
      "external": [
        "site:cn"
      ],
      "target": "direct_out"
    },
    {
      "external": [
        "mmdb:cn"
      ],
      "target": "direct_out"
    }
  ]
}

Hi @Ali-Flt , you can try connecting VPN from System Settings if the in-app toggle does not work.
You are recommended to use the conf format configuration as it is more human-readable, plus the renovated editor in Maple v0.7.0 is able to detect more errors in your conf files.

I also tried the windows VPN settings multiple times but no luck

I assume the configuration is used in #35. As there is no error when connecting the VPN itself, I am going to close this issue and continue tracking VMess AEAD matters in #35.


Support P-256 (secp256r1)

I started working on it and hit a little bit of a blocker. I'm not a cryptography pro. Open questions I have:

The p256 crate doesn't seem to provide a way to recover a public key like the k256 one does. I assume we're not providing that functionality?
(This is the blocker.) It doesn't look like it's possible to normalize a p256 signature like it is for k256. This should be possible, right? Is this something to raise with p256 authors? Edit: https://github.com/RustCrypto/signatures/issues/341
Are p256 signatures also going to be 64 bytes? I get 71 or 72 using online tools or openssl, but I'm assuming this is before they're normalized?

I started working on it and hit a little bit of a blocker. I'm not a cryptography pro. Open questions I have:

The p256 crate doesn't seem to provide a way to recover a public key like the k256 one does. I assume we're not providing that functionality?

I assume so. Good to raise an issue / ask the crate maintainers about it.

(This is the blocker.) It doesn't look like it's possible to normalize a p256 signature like it is for k256. ~This should be possible, right? Is this something to raise with p256 authors?~ Edit: Normalize NistP256 signature RustCrypto/signatures#341

Good find. This is pretty recent, and for the comments it seems they are going to add this normalization soon. I would just put a TODO here s a reminder, instead of implementing this normalization.

Are p256 signatures also going to be 64 bytes? I get 71 or 72 using online tools or openssl, but I'm assuming this is before they're normalized?

AFAIK, normalizing wouldn't change the signature length. I have no idea about the signature lengths for secp256r1. This depends a lot on the formats we're using for the input data, and the specific scheme / impl we want to support / be compatible with. @webmaster128 (or @plusCubed perhaps; issue #1058 creator) might be able to help you better here.

Are p256 signatures also going to be 64 bytes? I get 71 or 72 using online tools or openssl, but I'm assuming this is before they're normalized?

70/71/72 bytes indicate a DER encoding of variable length integers (r, s) instead of fixed length encoding 32 bytes r and 32 bytes s. See https://github.com/cosmos/cosmjs/blob/v0.26.0/packages/crypto/src/secp256k1signature.spec.ts#L102-L133

70/71/72 bytes indicate a DER encoding of variable length integers (r, s) instead of fixed length encoding 32 bytes r and 32 bytes s. See https://github.com/cosmos/cosmjs/blob/v0.26.0/packages/crypto/src/secp256k1signature.spec.ts#L102-L133

Oh, good! That's a clue. Thanks.

In the Cosmos ecosystem 2x32 bytes fixed length encoding is predominant. And if I recall correctly Bitcoin regrets to have picked DER for historic reasons.

The p256 crate doesn't seem to provide a way to recover a public key like the k256 one does. I assume we're not providing that functionality?

Recovering the public key from signature + message seems to be an algorithm that works for ECDSA over all curves. At least this is stated here: https://bitcointalk.org/index.php?topic=5183471.msg52417717#msg52417717. The algorithm described here also makes no restrictions on the curve: https://crypto.stackexchange.com/a/18106. So it should be possible to implement and is worth a feature request.
If we need it is a different story. In Cosmos, the public key is always stored on chain. For Ethereum this is not the case. There only 20 byte addresses are stored instead of 33 byte pubkeys. In order to verify a transaction signature you need to recover the pubkey from signature+message first before the actual verification can be done. But Ethereum does not have secp256r1.

(This is the blocker.) It doesn't look like it's possible to normalize a p256 signature like it is for k256. This should be possible, right? Is this something to raise with p256 authors? Edit: Normalize NistP256 signature RustCrypto/signatures#341

Great insight, thanks. I consider this feature blocked because of that.

Note, I saw the linked issue "Normalize NistP256 signature". Tony, who answered the questions, is relatively well known in Cosmos, and works with Zaki. I hit him up with crypto questions from time to time on discord. If you want an intro, I can make one.

Also, Regen is adding secp256r1 support to the Cosmos SDK (maybe they already did in 0.44?). I would focus on compatibility with their design unless there is another strong driving force behind this.

Currently not planned. Maybe we can re-use this work later. Cosing for now. Thanks!


Fix for order by bug with ArrayBindingSet

GitHub issue resolved: #4020
GitHub issue resolved: #4041
Briefly describe the changes proposed in this PR:

use try-catch to handle exception thrown by missing binding

PR Author Checklist (see the contributor guidelines for more details):

[x] my pull request is self-contained
[x] I've added tests for the changes I made
[x] I've applied code formatting (you can use mvn process-resources to format from the command line)
[x] I've squashed my commits where necessary
[ ] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

@kenwenzel This should fix the bug you reported.

@hmottestad thanks for taking this over. Code change looks good to me

@hmottestad Thank you :-)


disallow ill-typed if and get

I have been aware of this for a while, so I finally fixed it with a small patch to prevent someone from running into it before the new type system is implemented.

You can add tests if you want, but I think with the changes coming up it would be okay to wait and see what the new system looks like first.


Invalid max value after peak

Example: https://turnipprophet.io/?prices=97.87.81..149.490.144......&pattern=3
The max should be 490, not 136

The last two columns only reflect future states, not current/past. This could be made clearer in the UI though..

Rewriting this in #307


NoSuchMethodException: org.springframework.context.annotation.ConfigurationClassPostProcessor.()

I am trying to build a native image for CAS, and it is probably a long way from happening because CAS is a large project, but trying to make some progress. I am currently building and trying to run without any generated json b/c the generated json was an unmaintainable 40K+ lines and I was hitting this NPE issue during build so I couldn't make much progress finding issues in CAS that would prevent native builds. I have a public project building a native image with a github workflow and it builds the binary and then errors out when it runs due to:
2021-12-30 03:30:40.833  WARN 2236 --- [           main] o.a.cas.web.CasWebApplicationContext     : Exception encountered during context initialization -
cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name
 'org.springframework.context.annotation.internalConfigurationAnnotationProcessor': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException:
Failed to instantiate [org.springframework.context.annotation.ConfigurationClassPostProcessor]:
No default constructor found; nested exception is java.lang.NoSuchMethodException: org.springframework.context.annotation.ConfigurationClassPostProcessor.<init>()

That seems like an internal spring class so it doesn't seem like something I should be putting in reflect-config.json, but maybe it is a class whose work is supposed to be handled by AOT processing? Could the fact that CAS has custom app context that extends AnnotationConfigServletWebServerApplicationContext be a problem? The custom application context is just overriding the onRefresh() method. Work has been done in CAS to not use cglib proxies for any configuration classes.
Here is the project: graal-starter branch
https://github.com/hdeadman/cas-overlay-template.git (Not much code b/c it pulls in code from https://github.com/apereo/cas)
Here are the logs from build and the error when running native image. It uses mac-os b/c mac github runners have 14GB memory and ubuntu runners with 8GB weren't enough to build (gc overhead exceeded). This is building with the latest snapshot of spring-native and using the Liberica Native Image Kit.
https://github.com/hdeadman/cas-overlay-template/runs/4663765980?check_suite_focus=true#step:6:132

Could the fact that CAS has custom app context that extends AnnotationConfigServletWebServerApplicationContext be a problem?

Yes. An AOT-runtime context is not annotation-based at all. By forcing this at runtime (not sure how), you're bringing configuration class parsing in the native image again. I got a bit lost by the overlay and how things are wrapped up together. Can you share how the override of the context takes place at runtime?

I backed out the custom context override (in a fork of CAS) in order to see if that made the problem go away. You can see the change here:
https://github.com/hdeadman/cas/commit/d7daf5a36fe33ba775d8e2443cc7a8c33d6eced8
I think the custom context that I removed uses this class to validate that there aren't properties that are invalid for the configuration beans. I suppose that would qualify as runtime configuration processing and that won't be doable at runtime?
With the custom app context removed, I updated the github action workflow to build that custom of CAS in the workflow and tried to build the native image with it. I got past the error above and it's getting a different error related to refresh scope, possibly on the messageSource bean?.
2022-01-04 05:43:34.653 ERROR 51295 --- [           main] o.s.boot.SpringApplication               : Application run failed

java.lang.IllegalStateException: No Scope registered for scope name 'refresh'
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:368) ~[na:na]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:213) ~[na:na]
	at org.springframework.context.support.AbstractApplicationContext.initMessageSource(AbstractApplicationContext.java:772) ~[na:na]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:571) ~[na:na]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145) ~[na:na]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:730) ~[cas:2.6.2]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:412) ~[cas:2.6.2]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:302) ~[cas:2.6.2]
	at org.springframework.boot.builder.SpringApplicationBuilder.run(SpringApplicationBuilder.java:164) ~[na:na]
	at org.apereo.cas.web.CasWebApplication.main(CasWebApplication.java:64) ~[cas:6.5.0-HD-SNAPSHOT]

Full logs here:
https://github.com/hdeadman/cas-overlay-template/runs/4698338180?check_suite_focus=true#step:8:129
CAS has configuration classes that are annotated with @RefreshScope(proxyMode = ScopedProxyMode.DEFAULT). Is that causing a problem? Or is it a problem specific to the messageSource bean that CAS overrides with this bean that has the RefreshScope annotation?

Thanks for the follow-up.

I think the custom context that I removed uses this class to validate that there aren't properties that are invalid for the configuration beans

If that is the case, there isn't really any reason I can think of that requires a custom context for this. A library such as CAS requiring a custom context is highly unusual so stopping that irrespective of Spring Native is an improvement.
That call in onRefresh can be called in plenty of other locations. For instance, you could write an ApplicationContextInitializer  that  gives you back the context prior of it being refreshed.

I got past the error above and it's getting a different error related to refresh scope

Unfortunately, refresh scope isn't supported, see the reference documentation.

We don't really need refreshscope for a native build (it would just be a feature that wouldn't be available natively), but the documentation wording implies to me that spring native is disabling refreshscope automatically. I am going to try setting that property to false when I do nativeCompile, or can the code not use the refreshscope annotations at all?

Yes, this is a good point. We do disable the feature but AOT doesn't take that into account, detect the scope and generate some code for it to be created at runtime. This is new in 0.11 as 0.10 was doing all that work at runtime (and the feature was disabled with the property we've discussed).
To fix this properly we might need a contributor that knows refresh scope is disabled and prevents the scope proxy to be created.

I have created a reproducer, just build it with mvn -Pnative -DskipTests clean package, run target/demo-refresh-scope, you should get the java.lang.IllegalStateException: No Scope registered for scope name 'refresh' error.
demo-refresh-scope.zip

@snicoll Thanks for the fix. I tried it out and its using the new code but it got a ConcurrentModificationException.
https://github.com/hdeadman/cas-overlay-template/runs/4729204318?check_suite_focus=true#step:8:134
java.util.ConcurrentModificationException: null
	at java.util.HashMap.computeIfAbsent(HashMap.java:1135) ~[cas:na]
	at org.springframework.aot.beans.factory.config.NoOpScope.get(NoOpScope.java:41) ~[na:na]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:371) ~[na:na]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:213) ~[na:na]
	at org.springframework.context.support.AbstractApplicationContext.initMessageSource(AbstractApplicationContext.java:772) ~[na:na]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:571) ~[na:na]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145) ~[na:na]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:730) ~[cas:2.6.2]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:412) ~[cas:2.6.2]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:302) ~[cas:2.6.2]
	at org.springframework.boot.builder.SpringApplicationBuilder.run(SpringApplicationBuilder.java:164) ~[na:na]
	at org.apereo.cas.web.CasWebApplication.main(CasWebApplication.java:63) ~[cas:6.5.0-HD-SNAPSHOT]

Thanks for testing! I think that might be the lambda callback. I'll have another look.

Thanks, the latest fix gets me past that RefreshScope issue. Now I am running into Caffeine library needing reflect-config.json but according to this issue https://github.com/spring-projects-experimental/spring-native/issues/465, not sure anyone has gotten that working. Looks like Caffeine 3.x might be blocked from working by an open Graal issue but CAS is using Caffeine 2.x so maybe there is some hope it can be made to work, I will try adding reflect-config.json for caffeine 2.x.

When try to build the app in NATIVE_AGENT mode and then run the app with java and the native-image-agent, to trace and generate metadata files, java -DspringAot=true -agentlib:native-image-agent=access-filter-file=access-filter.json,config-merge-dir=./src/main/resources/META-INF/native-image/org/apereo/cas/overlay,config-write-period-secs=300,config-write-initial-delay-secs=15 -jar build/libs/cas.jar
I am getting this error like it isn't using the new NoOpScope.
2022-01-08 00:52:15.666 ERROR 43787 --- [           main] o.s.boot.SpringApplication               : Application run failed

java.lang.IllegalStateException: No Scope registered for scope name 'refresh'
	at

https://github.com/hdeadman/cas-overlay-template/runs/4745129666?check_suite_focus=true#step:8:165
I don't understand everything that is going on with but when I looked at the BOOT-INF/lib/spring-native-0.11.2-SNAPSHOT.jar jar inside cas.jar, it contains the new NoOpScope.class but it doesn't appear to be using it in when running with java vs. running inside the native image.
Am I doing something wrong?


New filters?

Is it possible to read the new filters being uploaded to snapchat? Or anyway to allow new filters being used in the patched Snapcamera?

https://github.com/jaku/SnapCameraPreservation#notice


How can I download articles from a given url?

Is it possible to extract article urls from a certain page? build() method go lower level. I checked Source class. It seems that I can only extract articles by using category urls via categories_to_articles() method. My solution is
paper.categories = [Category(url = 'url_I_want')]   paper.download_categories()  paper.parse_categories()  paper.generate_articles()
But it seems too unprofessional. Is there official way to do this? Thank you in advance.

Hello there,
Did you try using Source() instead of Article() ?

Can I use Source() to find all articles for a category (for example : http://test.com/categoryExample) ?


provide option to set default year

for some projects the first year of the dates visualized by the calendar might be considered as boring or not representative enough (i look at you @martinantonmueller ;) ; see e.g. https://schnitzler-tagebuch.acdh.oeaw.ac.at/calendar.html or https://schnitzler-briefe.acdh.oeaw.ac.at/calendar.html)
therefore it would be nice if the calendar could be configured via an optional attribute e.g.
<acdh-ch-calendar-year data-variant="sparse" default-year="1995">
if this attribute is set, the given year is displayed on initial load

i'd prefer a method on the class to programmatically set the current year, would that be ok?
e.g. calendar.setData({ events, currentYear: 2024 });

you can now do https://github.com/acdh-oeaw/calendar-component/blob/main/example/index.html#L121
if that's all you need, please close this issue - thanks!

works like a charme, thanks!

Thanks from my part as well! – I like it when my needs are in consideration without me having to do anything!


change the tasks.loop seconds

change the tasks.loop seconds to something above 60, lower can cause ratelimiting so it isnt a good idea

change the tasks.loop seconds to something above 60, lower can cause ratelimiting so it isnt a good idea

will fix when i have time, or you can contribute and add it 🙂


chore: storybook migration

Hey @jguddas , could you please fix the conflicts? 🙏🏻

Resolved by #1301


slice_mode option does not exist; blurry content

I am trying get live streaming using libopenh264 near the quality of libx264, but I am running into the quality issues. Here is a live stream standing still:

And here is image when there is fast movement:

The only documentation I've been able to find on options for libopenh264 is here: https://support.medialooks.com/hc/en-us/articles/360000210192-H-264-encoding-options
Which give these values:

Name
Default value
Description

slices
0
Set the number of slices, used in the parallelized encoding. This is only used when slice_mode is set to ‘fixed’

slice_mode
auto
Set slice mode.Possible values:fixedrowmbautodyn

loopfilter
1
Enable loop filter, if set to 1. To disable set a value of 0.

max_nal_size
0
Set maximum NAL size in bytes.

allow_skip_frames
0
Allow skipping frames to hit the target bitrate if set to 1.

But it seems options like slice_mode is incorrect, and playing around with options like slices and max_nal_size don't do anything. Here is my ffmpeg command:
ffmpeg -y  -i pipe:0 -vf "scale=1920:1080:out_color_matrix=bt709" -color_primaries bt709 -color_trc bt709 -colorspace bt709 -c:v libopenh264 -b:v 9000k  -profile:v high -slices 10 -allow_skip_frames 1 -b_strategy 0 -maxrate 12000k -bufsize 9000k -pix_fmt yuv420p -r 60 -g 120 -c:a aac -b:a 256k -ac 2 -ar 44100  -af afftdn -f tee -map 0 "[f=flv]${data.stream.invirtu_rtmp_broadcast_endpoint}?sign=${data.stream.invirtu_rtmp_broadcast_key}|[f=mp4]${escapedTempFilePath}"`;

Are there any other options I can be testing for  libopenh264 to improve the quality?

Maybe related to https://github.com/cisco/openh264/pull/3638 ?
Try git version if so


Do not fail on 'Invalid comparator' error

Trying to install definitions with flow-typed install I faced an Invalid comparator error due to GitHub repo dependency in my package.json file.
This solution just avoids Invalid comparator errors by omitting them (and installing stubs therefore).
Another solution would be to check package version against RegExp like following (but it may be not complete/error prone):
const pkgVersionRegExp = /^http|^ssh|^git[\:\+]|^[^\/]+\/[^\/]+$/;

Possible fixes #399 and #367

Maybe it is reasonable to move try {} catch {} into libdefMatchesPackageVersion ?

Moved to #619


Selected border color change

I'm using the following config for the example on the right:
 cssOptions : {
			"vertical": true,
			"quadratic": true,
			"element": {
				"width": "100%",
				"color": "#000"
			},
	        "selected": {
	            "background": "#C1F5B0",
	            "border-color": "2px solid green"
	        }
		}

I was expecting the border to behave like the left example.

Any chance to fix it?

Hi @Blakko
You can add plain css which will fix your issue :
	<style type="text/css">
		.center-side {
			border-top: 0 !important;
			border-bottom: 0 !important;
		}
		.right-side {
			border-top: 0 !important;
		}
		.left-side {
			border-bottom:0  !important;
		}
	</style>

Also if you notice picker's height blinking issue,  then you can fix it by changing padding-top and padding-bottom of .center-side / left-side / right-side classes, their values depend on border size you would like to specify.
Let me know if there is anything else.
Thanks!

Worked, thx :+1:


compilation error snackbar and closable notistack

clicking on snackbar with close that notification
Error message if code was not sucessfully compiled by jdoodle

#171
#132


Consider options for applying different configuration options to different chaincode

It may be desirable to deploy different chaincode in different namespaces and, with #102, with different resource requests and limits.
Currently the chaincode packages only contain information about what is being deployed, not how to deploy it, and I am keen to keep this distinction. For example, requiring a new package to go through the chaincode lifecycle to change resource limits is not ideal. It would also reduce the likelihood of different organisations being able to share the same chaincode package.

Having a way for deploying each chaincode in a specifc namespace will be good and is a solution for the weird chaincode hash names. :)

Having a way for deploying each chaincode in a specifc namespace will be good and is a solution for the weird chaincode hash names. :)

@davidfdr I've also opened #105 to improve the pod names :)

consider also the pod availability if the pod is deleted / stopped, what are the other options other than restarting the peer to create the pod

@labibfarag The peer should already restart the chaincode if the pod is deleted/stopped as part of the Fabric builder and launcher implementation, so definitely open an issue if that isn't happening


Clan wars

Hello Dear Developers
What do you think about introduce in the future "clan wars"?
Each clan could have a skin or unique group for character, at this moment like you saw on the youtube, some youtubers have own group and the members just add some sign #BH [$] etc on the end to be friendly to the other if someone is in the same group.
From the client side in home page every one should be able choose from the selector his group to mark him self where he/she belongs, after join to the server, see the skin of the group, we could have create popular default skins like on agar.io are like earth etc...
Example Menu:
nickname: [     ] [ a-z A-Z 0-9 ]
group / clan: [     ] - if choose the group of clan/group, someone can't select the skin due of unique skin signed for the clan/group.
skins: [     ] - only available for neutral players.
server: [     ] sub-servers instances.
Best Regards
Mateusz

Thanks for the suggestion, but someone already created an issue for Team Mode: #66 :)
In order to keep the discussion in a single issue, I'm going to close this one so we can focus on the older issue :)


Fix package location url

The tng-sdk-package return a location such as http://tng-cat:4011/catalogues/api/v2/packages/cd891051-7d15-416b-b758-2ec9ef63dcb2, which is internal. Need to map that to http://pre-int-sp-ath.5gtango.eu:32002/api/v3/packages/cd891051-7d15-416b-b758-2ec9ef63dcb2

We're not going to implement this


Error installing on Raspberry Pi (256mb)

Hey, I just tried to install the update for use with node-opus, but I'm having an issue:
pi@raspberrypi ~/nodeplayer $ node -v
v0.12.2
pi@raspberrypi ~/nodeplayer $ npm -v
2.7.4
pi@raspberrypi ~/nodeplayer $ npm install<EMAIL_ADDRESS>|
><EMAIL_ADDRESS>install /home/pi/nodeplayer/node_modules/ogg
> node-gyp rebuild

make: Entering directory '/home/pi/nodeplayer/node_modules/ogg/build'
  CC(target) Release/obj.target/libogg/deps/libogg/src/framing.o
In file included from ../deps/libogg/include/ogg/ogg.h:25:0,
                 from ../deps/libogg/src/framing.c:25:
../deps/libogg/include/ogg/os_types.h:143:32: fatal error: ogg/config_types.h: No such file or directory
compilation terminated.
deps/libogg/libogg.target.mk:89: recipe for target 'Release/obj.target/libogg/deps/libogg/src/framing.o' failed
make: *** [Release/obj.target/libogg/deps/libogg/src/framing.o] Error 1
make: Leaving directory '/home/pi/nodeplayer/node_modules/ogg/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Linux 3.18.12+
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/pi/nodeplayer/node_modules/ogg
gyp ERR! node -v v0.12.2
gyp ERR! node-gyp -v v1.0.3
gyp ERR! not ok
npm ERR! Linux 3.18.12+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"<EMAIL_ADDRESS>npm ERR! node v0.12.2
npm ERR! npm  v2.7.4
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
...

Any ideas?

Oh, actually, I think I know what it is - there's no arm config - https://github.com/TooTallNate/node-ogg/tree/master/deps/libogg/config/linux
I'm about out of time for tonight, but I'll see if I can figure one out tomorrow.

Ya, PR welcome. See https://github.com/TooTallNate/node-ogg/blob/master/deps/libogg/config/README

Hey, I found a few minutes, and that was pretty easy. It now installs.. although I still can't get it to play audio (but I'm not sure this one is node-ogg's fault):
ALSA lib pcm_hw.c:1401:(_snd_pcm_hw_open) Invalid value for card
[../deps/mpg123/src/output/alsa.c:165] error: cannot open device default
node: pcm_params.c:2286: snd_pcm_hw_refine: Assertion `pcm && params' failed.
Aborted

Any ideas what to look at there?


Fix issue when streaming LLM response

Problem
Currently, if stream flag is set to True in the LLM params, there will be an exception raised fromllm.py. The reason is that litellm will return an instance of litellm's CustomStreamWrapper which cannot be accessed in the current way. This is a real issue for our use case where we stream LLM response for special handling of lengthy content as well as optimizing application performance.
Proposed Change
To solve this, we can check the stream flag when calling litellm.completion and have a separated handling for streaming mode.
Test Case
The following sample code fails due to TypeError: 'CustomStreamWrapper' object is not subscriptable and succeeds after the PR.
from crewai import Agent, Task, LLM
from crewai import Crew, Process

api_key = "my_key"
my_llm = LLM(model="gpt-4o-mini", api_key=api_key, stream=True)

# Create a researcher agent
researcher = Agent(
    role='Senior Researcher',
    goal='Discover groundbreaking technologies',
    verbose=True,
    llm=my_llm,
    backstory='A curious mind fascinated by cutting-edge innovation and the potential to change the world, you know everything about tech.'
)

# Task for the researcher
research_task = Task(
    description='Identify the next big trend in AI',
    expected_output="A single short sentence.",
    async_execution=False,
    agent=researcher  # Assigning the task to the researcher
)

# Instantiate your crew
crew = Crew(
    agents=[researcher],
    tasks=[research_task],
    process=Process.sequential  # Tasks will be executed one after the other
)

# Begin the task execution
crew.kickoff()

Hey @MottoX!
Thank you for submitting this PR! Could you please elaborate more on this use case?
It looks like you are trying to create an LLM that is going to stream a response. However, within crewAI, we don't really support streaming results.
Are you trying to add support for streaming because you're going to use the same LLM with streaming elsewhere?

Hello @bhancockio
Our team is developing applications using crewAI and in-house LLMs to process extensive data and generate or proofread articles. In some tasks, particularly those with lengthy request messages, non-streaming requests can lead to server timeouts.  Invoking LLM in streaming fashion can address the issue and ensure that sufficient content is generated in the response. We have implemented engineering optimizations for LLM streaming, enhancing its efficiency, stability, and fault tolerance.
However, after upgrading to the latest crewAI version, we found that crewAI, now using litellm for LLM invocation, only supports non-streaming requests.
This PR aims to enhance crewAI by enabling users to interact with their LLMs in streaming mode via passing stream=True in crewai.LLM. This feature will benefit users like us and make crewAI more flexible and adaptable.


Unable to concatenate cubes when the units of the time coordinate differ

Hello,
I've just discovered that Iris raises:
ConcatenateError: failed to concatenate into a single cube.
  Dimension coordinates metadata differ: time != time

when attempting to concatenate cubes that differ only by the units of the time coordinate, e.g. days since 1850-01-01 00:00:00.
Would you consider this to be a bug? When the points of the time coordinate are determined by applying the units, it's clear that they are contiguous, so shouldn't the cube concatenate in this case?
(We are dealing with this issue within our code, so there's no rush for a response, I just thought I'd start the conversation) :)

Hi @ehogan, thanks for raising this. This is deliberate, reasoned behaviour (I should know; I implemented it!), which is done because the coordinate metadata is not identical. It would be much harder to get Iris to work out that the two coordinates are actually contiguous once the units have been taken into account, and would actually require converting the units of the time coordinate to ensure the concatenation could go ahead (to make sure that the underlying values really are contiguous, rather than being implicitly contiguous once the unit is accounted for).
That said, the solution for this is just to unify the cubes' time units, and there's a suchly-named function provided in Iris for precisely this situation, which will fix this situation for you.

That said, the solution for this is just to unify the cubes' time units, and there's a suchly-named function provided in Iris for precisely this situation, which will fix this situation for you.

That's better than my solution; thanks! :D


go/cli: mcap info show channels count

Public-Facing Changes

show channels count like channels(45): in mcap info print.
Description

The channels list printed by mcap info might have discontinuous sequence numbers due to certain reasons (for example, if one of the topics in the original recorded data has zero messages, then the mcap generated after using mcap filter will exhibit this). Therefore, it's important to visually see the number of channels.

this seems nice to me but the count formatting is inconsistent with the way other counts are displayed. Here is the existing info:
library:   mcap go v0.4.0
profile:   ros1
messages:  1606
duration:  7.780758504s
start:     2017-03-21T19:26:20.103843113-07:00<PHONE_NUMBER>.103843113)
end:       2017-03-21T19:26:27.884601617-07:00<PHONE_NUMBER>.884601617)
compression:
        zstd: [314/314 chunks] [119.10 MiB/58.57 MiB (50.82%)] [7.53 MiB/sec]
channels:
        (0) /diagnostics              52 msgs (6.68 Hz)    : diagnostic_msgs/DiagnosticArray [ros1msg]
        (1) /image_color/compressed  234 msgs (30.07 Hz)   : sensor_msgs/CompressedImage [ros1msg]
        (2) /tf                      774 msgs (99.48 Hz)   : tf2_msgs/TFMessage [ros1msg]
        (3) /radar/points            156 msgs (20.05 Hz)   : sensor_msgs/PointCloud2 [ros1msg]
        (4) /radar/range             156 msgs (20.05 Hz)   : sensor_msgs/Range [ros1msg]
        (5) /radar/tracks            156 msgs (20.05 Hz)   : radar_driver/RadarTracks [ros1msg]
        (6) /velodyne_points          78 msgs (10.02 Hz)   : sensor_msgs/PointCloud2 [ros1msg]
attachments: 0
metadata: 0

what about instead adding a "channels: 7" above where "attachments: 0" is printed?

@james-rms please take a look

Closing in favor of https://github.com/foxglove/mcap/pull/1243


 I am using above package.json for my project.
I have made one changes that related to rarible sdk version earlier I was using rarible sdk version  "^0.13.7" so it was working for my project only issue was coming on accept auction and NFT listing for sell and buy was working.
But since 27Oct my all functionality not working when I checked in console then I saw rarible order API is getting failed with 400 status.
And when I checked the payload then I saw like this
"status": 400,
"url": "https://testnet-ethereum-api.rarible.org/v0.1/order/orders",
"data": {
"code": "INCORRECT_SIGNATURE",
"message": "Maker's signature is not valid for V2 order",
"status": 400
},
"code": "ETHEREUM_NETWORK_ERR"
}
payload:  {
"code": "INCORRECT_SIGNATURE",
"message": "Maker's signature is not valid for V2 order",
"status": 400
}
After that I shared my problem on discord they suggest to me upgrade sdk version  ^0.13.7" to ^0.13.56"
After updating the rarible sdk version ^0.13.56" and while I am running the project then I am getting first warning that are as follows:
One of your dependencies, babel-preset-react-app, is importing the
"@babel/plugin-proposal-private-property-in-object" package without
declaring it in its dependencies. This is currently working because
"@babel/plugin-proposal-private-property-in-object" is already in your
node_modules folder for unrelated reasons, but it may break at any time.
babel-preset-react-app is part of the create-react-app project, which
is not maintianed anymore. It is thus unlikely that this bug will
ever be fixed. Add "@babel/plugin-proposal-private-property-in-object" to
your devDependencies to work around this error. This will make this message
go away.
After some getting error msg in terminal like this:

Closing this as duplicate
https://github.com/rarible/sdk/issues/556


preventScroll set to false but unable to scroll the main body.

Describe the bug
Even after passing the prop of preventScroll = false,
<Sheet.Root
	preventScroll={false}
	closeOnOutsideClick={true}
>
<slot/>
<Sheet.Root/>

The content that is wrapped by the Sheet.Root is not scrollable. (When attempting to scroll on the outside, it gives the behaviour that the scroll bar has reached the end of the page, i.e. the elastic band effect).
Here's a video:
https://github.com/huntabyte/bits-ui/assets/48677212/59b8b87e-a47e-4c0d-9528-25ac594e8552
Reproduction
https://bits-ui.com/repro
Logs
No response
System Info
System:
    OS: macOS 14.2.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 73.64 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm
    pnpm: 8.7.5 - ~/Library/pnpm/pnpm
    bun: 1.0.14 - ~/.bun/bin/bun
  Browsers:
    Chrome: 122.0.6261.94
    Safari: 17.2.1
  npmPackages:
    @sveltejs/kit: ^2.5.0 => 2.5.0
    bits-ui: ^0.14.0 => 0.14.0
    svelte: ^4.2.11 => 4.2.11

Severity
blocking an upgrade

Dialog has this problem as well if you use bind:open to open the dialog.
But if you do like
<Dialog.Trigger class={buttonVariants({ variant: "outline" })}
>Edit Profile</Dialog.Trigger

it's will be fine.

if you are using bind:open. just try below code. it works for me.
  let editing = false;

  function updateBodyOverflow() {
    if (typeof window !== 'undefined') {
      document.documentElement.style.overflow = editing ? 'hidden' : '';
    }
  }

  onMount(updateBodyOverflow);

  $: editing, updateBodyOverflow();```


@Serenity.Decorators.filterable() issue

I have defined some fields available only with a certain PermissionKey in xyzRow.cs / xyzColumns.cs / xyzForm.cs (ReadPermission as attribute).
When i log with a user not having this permission, these columns are CORRECTLY :

NOT available in the Grid
NOT available in the Column Picker

but they are ALL AVAILABLE to filter when the grid is defined using the @Serenity.Decorators.filterable() decorator (columns are proposed while they should NOT - to be consistent with others).
Looks like the filterable does not take into account permissionkey setting.

you can see from the source below that there's no client side permission checks when creating the filterbar, so you'll need to add the [NotFilterable] attribute to the fields you want to hide in xyzColumns.cs class, OR override the createFilterBar method on the xyzGrid.ts and add your own permission checks to filter out.
https://github.com/volkanceylan/Serenity/blob/ea41e1f28fc0aa0bae911738f76487acb0de92af/Serenity.TypeScript.CoreLib/UI/DataGrid/DataGrid.ts#L651-L669

Thanks.
Fixed - maybe i am gonna push a pull request for this modification in Serenity.
protected createFilterBar(): void {
      var filterBarDiv = $('<div/>').appendTo(this.element);
      var self = this;
      this.filterBar = new Serenity.FilterDisplayBar(filterBarDiv);
      if (!this.isAsyncWidget()) {
        this.filterBar.set_store(new Serenity.FilterStore(this.allColumns.filter(function (x) {
          return (x.sourceItem != null) && (x.sourceItem.notFilterable !== true) && (Authorization.hasPermission(x.sourceItem.readPermission) || x.sourceItem.readPermission == null);
        }).map(function (x1) {
          return x1.sourceItem;
        })));
        this.filterBar.get_store().add_changed((s: JQueryEventObject, e: any) => {
          if (this.restoringSettings <= 0) {
            self.persistSettings(null);
            self.view && (self.view.seekToPage = 1);
            self.refresh();
          }
        });
      }
    }

great idea, you might even find you can reuse the method canShowColumn to perform the permission check.
https://github.com/volkanceylan/Serenity/blob/ea41e1f28fc0aa0bae911738f76487acb0de92af/Serenity.TypeScript.CoreLib/UI/DataGrid/DataGrid.ts#L1308-L1327


Initial work

This job is designed to examine your ACM Cloud Provider Connection objects and generate events if the quota's are within 15% of their capacity total.
The job will also generate an event on failure.  The Kubernetes cronjob runs once every 60min.

[ ] Initial support for Azure

Initial Commit: https://github.com/open-cluster-management/cloud-provider-quota-check/commit/993055ce7088f7a17eae2311fb1e8df56ca9588f


Run google drive folder creator in another thread

This way we decreased create_project_with_tasks' execution time from 9.6 seconds to 2.2 seconds (in dev environment).

Coverage increased (+0.03%) to 94.453% when pulling b70852bdd0fc3525755ca737b11bb34ed0d086e2 on run-google-folder-creator-in-other-thread into 552d6029d20c50d6f410383de86809903576e2e0 on main.


Update fromsflow.ai to version 5.0.0

The Digital Journeys project is currently running on formsflow.ai v4.0.6. A need for features in the latest formsflow version has been identified, so a version upgrade is needed

Note: Major version update this time may be trickier than the last version update

Link to all the new features in v5:
https://github.com/AOT-Technologies/forms-flow-ai/releases/tag/v5.0.0

Deployed to DEV and ready for testing

Stella and I tested the telework agreement for: 2 days, 3+ days, and occasional agreements. Everything looks good; no issues were generated.

That's great news, thank you for testing it and the update!
@iman-jamali-fw and @simensma-fresh, what comes next, push to Prod? Timing?

Regarding the next steps, one question would be if the team wants the new draft feature enabled in PROD.

@iman-jamali-fw if pushed to Prod, draft would automatically be applied to TW? If so, not yet I'd say.

@Abuchana  We can disable it on PROD if you want everything in v5 except the draft (which would require some prep work).

UPDATE: I tested this in the test environment and realize this should have been tested in DEV. Doing that now.

I'm not seeing the Draft test page

Testing is complete  - please let me know when this can be closed.

@Stella-Archer To have draft, you first need to start a new form (Telework), wait for a few seconds, and then a draft version of that form is saved and will be accessible under /draft page.

@MeghanStothers @Stella-Archer
To move v5 to Prod, you need make a decision whether to have draft feature for Telework enabled or not. To help you decide, here are some steps we can take:

We can globally disable draft feature with no effort involved.
We can toggle draft per form, other words, only disable it for the Telework form. This will require some effort, I estimate it to be 3.
If you decide to enable draft for Telework, we need to make sure drafts are removed completely after being submitted. Currently drafts are soft deleted, which means user data will persist in database AND delete submissions functionality for incomplete and completed submissions will partially fail. Efforts involved to add hard-delete for drafts is 2.

We have ticket 601 to address 3.2 of the above comment. 3.1 needs to be addressed after 3.1/601 has been solved. The decision from the program team is to enable the draft feature globally and make sure it's working accurately

Tested in DEV. Ready to be transferred to TEST and PROD


STT0078: update missing rows of inference transcript due to transfered text to database.

Description
Currently when using transfered text function in stt training data creation we are losing some initial transcript of the full audio when matching transcript od the split audio is not found in full audio text. therefore we need to upload the missing audio splits back to database and update the transfered text function to append missing data back to transcript csv file.
Completion Criteria
uploaded the missing data in database and update transfered text function
Implementation

filter the missing audio splits from man inf transcript csv with transfered text csv file.
upload the filtered data to database
update the transfered text function
do testing on a sample data.

Subtask

[ ] write a script to filter the missing audio splits
[ ] get the missing audio splits and assign group id then upload to database
[ ] update transfered text function to append missing rows after tranfering text
[ ] write a test case

first will run inf transcript on missing audio splits row 1 to 4

add @jim-gyas as reviewer

Calculating Cer between Inference Transcript and Transfer Text


Consider storing a pointer to the value of a coefficient in the final R1CS object

Loopring put out a blog post earlier today discussing optimizations they used (https://medium.com/loopring-protocol/zksnark-prover-optimizations-3e9a3e5578c0)
One interesting memory reduction optimization is noting that for ~all circuits of interest, there are not that many distinct values of coefficients. So instead of storing one field element for each coefficient, you can instead make a list of unique coefficients used in you're circuit, and then make the coefficients in the end R1CS constraints be an index into this list. This drops the memory to store the coefficient from 32 bytes to 8 bytes. (A 1 word index)
8 bytes is enough to store an index for 2^24 unique coefficients, if for some reason the library had to be able to support R1CS constraints with more unique coefficients, then 16 bytes would be more than enough.
This optimization could be taken when producing the final R1CS object after optimizations, that gets passed into the prover.
This should be a notable reduction in the memory size of Groth16, less so for Fractal/Marlin due to them requiring degree K polynomials. This may increase proving times though, as you have to read the value of the coefficient from the pointer, though this is hopefully in L1 cache.
Similarly, I believe that this observation also suggests a better Fractal/Marlin arithmetization for circuits of interest. (Eliminating the preprocessed val oracles in exchange for more (relatively cheap) verifier work)

This is essentially a string interning optimization, right?

Yes! (Didnt know there was a term for this)

(I only know of this because I spend too much time on the rust-lang issue tracker 😅)


Experiencing issues with register_font_directory and semibold font files

I'm on Python 3.11.8 and Version: 1.4.0 of vl-convert-python.
I'm using vl-convert-python to create png files of Altair charts that use a specific theme file
alt.themes.register('jil_theme', jil_theme) alt.themes.enable('jil_theme')
My theme file has the following fonts:
font_regular = "Matter"
font_semibold = "Matter SemiBold"
But the png outputs do not recognize Matter SemiBold despite having the font file on my computer. They do recognize Matter so if I change font_semibold to Matter, it will output correctly. Also, if I specify the font weight to 600 where I want the charts to use a semibold, I can get the right output if the font_semibold is set to "Matter". If I specify font weight to 670, it does not work.
Let me know if you need more details about this, thanks!

Thanks for the report @jcweaver, I was able to reproduce what you're seeing.
This may be related to https://github.com/RazrFalcon/resvg/issues/702, which was fixed in version 0.39 of resvg. We're currently on 0.36.0, so this is a good reason to look into updating.

@jonmmease I was wondering if you had a projected date for this fix?

Hi @jcweaver, I did take a look at this and forgot to update the issue. We'll need to wait for a release of the svg2pdf crate before we can update resvg.

Hi @LaurenzV, do you have any plans for when you might publish the next version of svg2pdf to crates.io? Thanks!

You'd have to ask @laurmaedje. But I think a new version will be published as soon as we've managed to update Typst to the newest resvg, which unfortunately proved to be a bit complicated...

New version is out.

Thanks for the ping @LaurenzV!

@jonmmease any update on when you might be able to update this now that a new version of resvg is out? Thanks!

Hey @jcweaver, it's on my list and definitely something I'm planning to get to. But I don't have an ETA to share.  There are a bunch of breaking changes in resvg/usvg to work through, so it's not just a matter of bumping the version unfortunately.


🔥Can't compile after upgrading to 5.0

Bug
After having updated to 5.0 to migrate to AndroidX I am getting the following error:
> Task :react-native-video:compileReleaseJavaWithJavac FAILED
/Users/waltermonecke/Documents/Code/React-Native2/moodPixel/node_modules/react-native-video/android-exoplayer/src/main/java/com/brentvatne/
exoplayer/VideoEventEmitter.java:3: error: package android.support.annotation does not exist
import android.support.annotation.StringDef;
                                 ^
/Users/waltermonecke/Documents/Code/React-Native2/moodPixel/node_modules/react-native-video/android-exoplayer/src/main/java/com/brentvatne/
exoplayer/ExoPlayerView.java:5: error: package android.support.v4.content does not exist
import android.support.v4.content.ContextCompat;
                                 ^
/Users/waltermonecke/Documents/Code/React-Native2/moodPixel/node_modules/react-native-video/android-exoplayer/src/main/java/com/brentvatne/exoplayer/ResizeMode.java:3: error: package android.support.annotation does not exist
import android.support.annotation.IntDef;
                                 ^
/Users/waltermonecke/Documents/Code/React-Native2/moodPixel/node_modules/react-native-video/android-exoplayer/src/main/java/com/brentvatne/exoplayer/ResizeMode.java:33: error: cannot find symbol
    @IntDef({
     ^
  symbol:   class IntDef
  location: class ResizeMode
/Users/waltermonecke/Documents/Code/React-Native2/moodPixel/node_modules/react-native-video/android-exoplayer/src/main/java/com/brentvatne/exoplayer/VideoEventEmitter.java:74: error: cannot find symbol
    @StringDef({
     ^
  symbol:   class StringDef
  location: class VideoEventEmitter
/Users/waltermonecke/Documents/Code/React-Native2/moodPixel/node_modules/react-native-video/android-exoplayer/src/main/java/com/brentvatne/exoplayer/ExoPlayerView.java:72: error: cannot find symbol
        shutterView.setBackgroundColor(ContextCompat.getColor(context, android.R.color.black));
                                       ^
  symbol:   variable ContextCompat
  location: class ExoPlayerView
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
6 errors

React native info output:
 System:
    OS: macOS 10.14.5
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    Memory: 4.45 GB / 16.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 8.9.4 - /usr/local/bin/node
    npm: 6.9.0 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
    Android SDK:
      API Levels: 23, 25, 26, 27, 28
      Build Tools: 26.0.2, 26.0.3, 27.0.2, 27.0.3, 28.0.2, 28.0.3
      System Images: android-28 | Google Play Intel x86 Atom, android-P | Google APIs Intel x86 Atom
  IDEs:
    Android Studio: 3.4 AI-183.6<IP_ADDRESS>92245
    Xcode: 10.1/10B61 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.8.6 => 16.8.6
    react-native: 0.60.4 => 0.60.4
  npmGlobalPackages:
    create-react-native-app: 1.0.0
    react-native-cli: 2.0.1
    react-native-git-upgrade: 0.2.7

MainApplication.java
package com.moodpixel;

import android.app.Application;
import android.util.Log;
import android.support.multidex.MultiDexApplication;

import com.facebook.react.PackageList;
import com.facebook.hermes.reactexecutor.HermesExecutorFactory;
import com.facebook.react.bridge.JavaScriptExecutorFactory;

import com.horcrux.svg.SvgPackage;
import com.facebook.soloader.SoLoader;
import com.facebook.react.ReactPackage;
import com.facebook.react.ReactNativeHost;
import com.facebook.react.ReactApplication;
import com.brentvatne.react.ReactVideoPackage;
import com.reactnative.ivpusic.imagepicker.PickerPackage;
import com.github.reactnativecommunity.location.RNLocationPackage;
import com.arttitude360.reactnative.rngoogleplaces.RNGooglePlacesPackage;

// react-native-firebase
import io.invertase.firebase.RNFirebasePackage;
import io.invertase.firebase.auth.RNFirebaseAuthPackage;
import io.invertase.firebase.admob.RNFirebaseAdMobPackage;
import io.invertase.firebase.firestore.RNFirebaseFirestorePackage;
import io.invertase.firebase.messaging.RNFirebaseMessagingPackage;
import io.invertase.firebase.notifications.RNFirebaseNotificationsPackage;

import com.rnfs.RNFSPackage;
import com.RNFetchBlob.RNFetchBlobPackage;
import com.learnium.RNDeviceInfo.RNDeviceInfo;
import com.oblador.vectoricons.VectorIconsPackage;
import com.BV.LinearGradient.LinearGradientPackage;
import co.apptailor.googlesignin.RNGoogleSigninPackage;
import org.devio.rn.splashscreen.SplashScreenReactPackage;
import com.babisoft.ReactNativeLocalization.ReactNativeLocalizationPackage;

import java.util.List;

public class MainApplication extends MultiDexApplication implements ReactApplication {

  private final ReactNativeHost mReactNativeHost = new ReactNativeHost(this) {
    @Override
    public boolean getUseDeveloperSupport() {
      return BuildConfig.DEBUG;
    }

    @Override
    protected List<ReactPackage> getPackages() {
      @SuppressWarnings("UnnecessaryLocalVariable")
      List<ReactPackage> packages = new PackageList(this).getPackages();
      // Packages that cannot be autolinked yet can be added manually here, for example:
      packages.add(
        new SvgPackage(),
        new RNFSPackage(),
        new RNDeviceInfo(),
        new PickerPackage(),
        new RNLocationPackage(),
        new ReactVideoPackage(),
        new RNFirebasePackage(),
        new RNFetchBlobPackage(),
        new VectorIconsPackage(),
        new RNGooglePlacesPackage(),
        new RNFirebaseAuthPackage(),
        new LinearGradientPackage(),
        new RNGoogleSigninPackage(),
        new RNFirebaseAdMobPackage(),
        new SplashScreenReactPackage(),
        new RNFirebaseFirestorePackage(),
        new RNFirebaseMessagingPackage(),
        new RNFirebaseNotificationsPackage(),
        new ReactNativeLocalizationPackage()
      );
      return packages;
    }

    @Override
    protected String getJSMainModuleName() {
      return "index";
    }
  };

  @Override
  public ReactNativeHost getReactNativeHost() {
    return mReactNativeHost;
  }

  @Override
  public void onCreate() {
    super.onCreate();
    AppEventsLogger.activateApp(this);
    SoLoader.init(this, /* native exopackage */ false);
  }
}

Library version: 5.0

which react native version are you using ?
please check readme again to migrate to AndroidX

android/app/build.gradle
From version >= 5.0.0, you have to apply this changes:
dependencies {
   ...
    compile project(':react-native-video')
+   implementation "androidx.appcompat:appcompat:1.0.0"
-   implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"

}

mmm I think it can be my fault, seems a bad merge from my part, let me check.
As I also merged https://github.com/react-native-community/react-native-video/pull/1629 seems changes for AndroidX have been overriden, I will check

@wmonecke @vokhuyetOz Can you check this PR?
https://github.com/react-native-community/react-native-video/pull/1690
Sorry for the inconveniences (bad idea to make a release from mobile)
I will reopen this if error persists

@CHaNGeTe Great! When will it be merged?

As soon as I can, as 5.0.0 is totally broken.
Did you have the chance to test it?

Any news? For me it is working, but I want to be double sure

@CHaNGeTe , it is also working for me

I tried each and every solutions from all community but still same error with version 5.0.0 and 4.4.4 and 4.0.0 .
Please suggestions...?

Following steps helped to recover from above issue:

Install npm react-native-video package
Link package using react-native link react-native-video
Go to YourReactNativeProject/ios folder in terminal then run 'pod install' command, followed by 'pod update'  command (This will link libreact-native-youtube.a (library) to Pods/Products folder. You can check in Xcode)
Re-run your project with react-native run-ios

@ShivangiModi6220 It's worked...!!!!!
Thanks a lot ...!

Following steps helped to recover from above issue:

Install npm react-native-video package
Link package using react-native link react-native-video
Go to YourReactNativeProject/ios folder in terminal then run 'pod install' command, followed by 'pod update'  command (This will link libreact-native-youtube.a (library) to Pods/Products folder. You can check in Xcode)
Re-run your project with react-native run-ios

@ShivangiModi6220
It's worked...!!!!!
Thanks a lot ...!

As soon as I can, as 5.0.0 is totally broken.
Did you have the chance to test it?

@CHaNGeTe  I tested and is working perfectly fine.

react-native do jetify for you (convert old android modules to new format) when building directly you need to add $> npx jetify to solve the problem with module migration

One of those two (or both) worked for me
react-native link react-native-video
and
npx jetify
Just a reminder to people, use the --scan flag when building your project, it helped me to get more insights into what was the problem and find this issue to help me fix my problem

On one of the projects, I fixed it like this, and added to the readme, hope helped
Build failed
Task :react-native-video:compileReleaseJavaWithJavac FAILED
.../node_modules/react-native-video/android-exoplayer/src/main/java/com/brentvatne/exoplayer/VideoEventEmitter.java:3: error: package android.support.annotation does not exist
import android.support.annotation.StringDef;
^
.../node_modules/react-native-video/android-exoplayer/src/main/java/com/brentvatne/exoplayer/ExoPlayerView.java:5: error: package android.support.v4.content does not exist
import android.support.v4.content.ContextCompat;
^
.../node_modules/react-native-video/android-exoplayer/src/main/java/com/brentvatne/exoplayer/ResizeMode.java:3: error: package android.support.annotation does not exist
import android.support.annotation.IntDef;
^

### Fix problem
.../node_modules/react-native-video/android-exoplayer/src/main/java/com/brentvatne/exoplayer/VideoEventEmitter.java:3: error: package android.support.annotation does not exist
import android.support.annotation.StringDef;

.../node_modules/react-native-video/android-exoplayer/src/main/java/com/brentvatne/exoplayer/ResizeMode.java:3: error: package android.support.annotation does not exist
import android.support.annotation.IntDef;

replace `android.support` with `androidx`

.../node_modules/react-native-video/android-exoplayer/src/main/java/com/brentvatne/exoplayer/ExoPlayerView.java:5: error: package android.support.v4.content does not exist
import android.support.v4.content.ContextCompat;

replace `android.support.v4` with `androidx.core`


Feature Request: Implement clipboard plugin

It would be nice to exchange at least text between a SqueakJS image and the host system. ATM, this appears not to be supported.

It works fine on Chrome. Other browsers don’t work quite as well, that’s bug #74. It would be great if someone could look into that :)

If you are on Chrome and Cmd-C/V (Mac) or Ctrl-C/V (Win/Linux) are not working, please re-open, and give it a better title :)

I'm quite sure it did not work earlier, but at the moment, it is fine. Will reopen if I succeed to reproduce the issue. :-)


[BUG] Performance Regression in 2.14 and 3.0 hourly_aggs in http_logs workload

Describe the bug
https://opensearch.org/benchmarks

The P90 latency observed for hourly_aggs query has regressed over the last weekk
Related component
Search:Aggregations
Expected behavior
Latency should not increase
Additional Details
No response

Tagging @getsaurabh02 @msfroh @bbarani to see if they may be aware of any changes. In parallel, looking through the commit history to see if I can find some commit which could've cause this.

One of the commits (on the same day when regression started) which touch aggregation path slightly: https://github.com/opensearch-project/OpenSearch/commit/8332859ff28c9cd03e468cbd0e7b97092fd795ee [Can be evaluated if this could have had some impact]

@mgodwan This looks related to the https://github.com/opensearch-project/OpenSearch/pull/13179 where @bowenlan-amzn has added cluster setting to dynamically disable filter rewrite optimization.
Based on the description it reduces the deciding threshold for rewrite filters from 1024 to 24. Meaning if the date histogram aggregation include more than 24 buckets (e.g. hourly aggregation of 1 day), we won't use the optimization After this change, we will probably see regression for date_histogram_hourly_agg of big5 workload. That will be handled after the long term solution merged in next.

The change causing this is adding a dynamic cluster setting to decrease the threshold of apply our optimization on date histogram. The threshold is the number of filters rewritten from date histogram. Previous 1024 is reported to causing regression on pmc workload.
Since it's a dynamic setting, it won't actually cause regression for users and instead giving them ability to tune for their workload.

Thanks @bowenlan-amzn

Since it's a dynamic setting, it won't actually cause regression for users and instead giving them ability to tune for their workload.

Is this setting enabled for the benchmark setup where we are seeing regression?

The setting is a threshold. This operation of http workload currently exceed the threshold so our previous optimization is disabled, hence the regression.

[Triage - attendees 1 2 3 4 5 6]
@mgodwan Thanks for creating this issue.  This looks like a potential release blocking for v2.14.  Please let me know if you need any help getting eyes on this issue.

The setting is a threshold. This operation of http workload currently exceed the threshold so our previous optimization is disabled, hence the regression.

@bowenlan-amzn Do we need to revisit the threshold defaults in that case as the current ones have shown to cause regression?

Fix/Improvements merged in


Use LB server if API URL is empty

This changes the API URL preference to use the ListenBrainz server if it is empty. This simplifies the configuration a bit as it is easier to go back to default config. If the text edit field is empty it shows the default URL as a cue.
Also extends the README a bit, explicitly describing setup with Maloja (as it might be a common use case).

@subjut What do you think?

I can't test it right now, but the code looks good. I like the preference pane cue. And the clarifications in the README are good. I hope people actually read it. The /submit-listens URL ending tripped me up good for a couple of hours when I tried to connect to my server.

The /submit-listens URL ending tripped me up good for a couple of hours when I tried to connect to my server.

Yes. I also had to spend a few minutes looking up the proper URL, even though I knew what I was looking for. That's why I made it so explicit in the README


Support optional "inputId" prop to set ID of input

The text input should have an ID for accessibility reasons. This PR adds a inputId prop.
I had to update some of the dependencies to get the project building on my machine

Closing PR since this repository does not seem to be maintained anymore


Log request when Flask throws error

Fix some import issues along the way.

nice! we shoudl be able to test this on staging too


Can't communicate with Solis

Getting the following error:
_This error originated from a custom integration.
Logger: custom_components.pyscript.file.solis_control.solis_control
Source: custom_components/pyscript/eval.py:1982
integration: Pyscript Python scripting (documentation, issues)
First occurred: 16:30:02 (2 occurrences)
Last logged: 17:11:36
solis response:{"code":"0","data":[{"msg":"Send failed !","code":1}],"time":"1729006201907"}
I've checked API details and they are correct. Using latest script.
Any suggestions?

Hi I  have got the same error.  Did you manage to resolve this?

I'm still getting a success on my inverter. I wonder if it's that cahnge in send code sneaking back in on some inverters?


Seed packet enhancement

Add generation and end date to seed packets, also ability to create observations.

Completed.


Remove all the incomplete model loaders from core

I think we should remove all the incomplete/broken model loaders from the core.
I would keep only gltf and obj.
Having so many choices confuses the newcomers, increases the code we need to maintain... and they don't fully work anyway.

Agreed. In the best case every loader would be it's own module and especially push those formats towards tools to generate j3os. That doesn't mean you can't load .blend if it drives your gears, but it doesn't have to be included everywhere and advertised as such.


[terra-disclosure-manager] afterDismiss promise is resolved prior to dismissing

Bug Report
Description

The afterDismiss promise is being resolved prior to dismissing [1] the component. If disclosureManager.closeDisclosure() is then called in afterDismiss to close the rest of the disclosure stack, an exception is thrown and the disclosure is not properly closed.
[1] https://github.com/cerner/terra-framework/blob/master/packages/terra-disclosure-manager/src/DisclosureManager.jsx#L430
Example project: https://github.com/mschile/terra-framework/tree/afterDismiss
Steps to Reproduce

After starting the example project, navigate to http://localhost:8080/#/tests/terra-modal-manager/modal-manager/modal-manager-after-dismiss
Click 'Disclose B' button
Click 'Disclose C' button
Click 'Dismiss C' button and observe the disclosure is not properly closed.

Additional Context / Screenshots

Expected Behavior

The disclosure is properly closed.
Possible Solution

Resolve the afterDismiss promise after the component has been dismissed.
https://github.com/cerner/terra-framework/blob/master/packages/terra-disclosure-manager/src/DisclosureManager.jsx#L430
Environment

Component Name and Version: terra-disclosure-manager 4.9.0
Browser Name and Version: Chrome
Node/npm Version: [e.g. Node 8/npm 5] Node 8.16.0 / npm 6.4.1
Webpack Version: 4.30.0
Operating System and version (desktop or mobile): macOS 10.14.4

@ Mentions

@tbiethman

@tbiethman Should the deferred afterDismiss promise be resolved after Line 440 to ensure that the disclosure was closed / a disclosure was popped out before resolving it?
https://github.com/cerner/terra-framework/blob/ab093a9a2203d5f4a90fe3aaa66e18c719328e02/packages/terra-disclosure-manager/src/DisclosureManager.jsx#L427-L441

Correct, I think it would make the most sense to add callback function arguments to closeDisclosure/popDisclosure and execute them as setState callbacks:
popDisclosure(callback) {
  this.setState({
    ...
  }, callback);
}

// When executed
this.popDisclosure(() => {
  this.dismissChecks[key] = undefined;
  this.resolveDismissPromise(key);
});

It might also make sense for popDisclosure to internally call closeDisclosure if there's only one item in the stack. That would simplify the existing handler logic.


deployment problem

Hi， i followed your instrucion  step by step, while come to this  issue above.
I change the version to  '2.0/2.1/3.0'  all  print error. did you see this before.
I try different version docker-compose  inlude yours but in vain.

Hi, you're seeing this error because your docker doesn't support  version: '2.3' I specified in docker-compose.yml. I used this exact version, because only 2.3 supports healthcheck and condition: service_healthy. Which operation system are you using and how did you install docker?

latest docker-compose(1.21) solved this probelms. thanks！
keeping eyes on this nice project.

next problem
"bash download_content.sh  all"
is there any way more easier to deploy  OR  develop this proj? T T

Are you using docker?

Using docker shouldn't cause this issue, and you do NOT need execute bash download_content.sh all.
If you're not using docker you should export PYCHAT_CONFIG variable as specified in  https://github.com/Deathangel908/djangochat/#archlinux . Execute export PYCHAT_CONFIG=local

django expects this variable to be present in global variables while executing scripts.

I would like to  follow your video guide .. Expolring by my self may cause more problems.  Hope you can make a more cleare development-evn deployment video on youtube  . An auto deployment shell script  will be more helpful.  Thanks for your answear and help

I also added single Dockerfile image build. You can pull it with docker run -p 443:443 -p 8888:8888 deathangel908/pychat or build one using docker build -t pychat . -f docker-all/Dockerfile following build-docker


Update _index.md #41674 updated

links were broken have been updates issue  #41674

/retitle Update outdated links in Japanese localization
We avoid referencing PRs and issues in commit messages (including PR merge commits)


Feature request: using abduco in a DUMB terminal

I was looking for something like TMUX that will work in a DUMB terminal (ie, Emacs shell buffer).  This might be due to our use of the alternate screen buffer. That is something like tput smcup (enter) and tput rmcup (leave) won't work either. It is not clear whether using the alternate screen buffer is a good idea, see #35 for further discussion.


[Gally]: master <- dev

Automatically created by Git-Ally

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove the version number from the kernel extension id

I have a hard conflict between MATLAB HID support and Karabiner, so I have to unload/reload the deamons and kernel extension (https://github.com/tekezo/Karabiner-Elements/issues/1501).
One small annoyance it the bundle name of the kext including the version number: org.pqrs.driver.Karabiner.VirtualHIDDevice.v061000 — it means my commands break every time the version number changes and no other kext include version numbers in the bundle id, e.g.  at.obdev.nke.LittleSnitch — if you need to know the version, kextstat returns that info.

This is still an issue…

Sorry for inconvenience.
There is a reason that I append the version number to the kext.
macOS often fails to unload the kext which related keyboard driver once it used.
When the issue happened, we cannot reload the same kext until the system is rebooted.
So, I append the version number to recognized as another kext to avoid the issue.
I believe the latest Karabiner-Elements does not affect other apps while the device is unselected.
https://pqrs.org/osx/karabiner/document.html#configuration-devices
Do you still need to unload the kext with the latest Karabiner-Elements?

Hi, I've just tested, and you are correct, deselecting my keyboard now allows MATLAB HID code to work as expected, that is brilliant thank you!!!
I'll close this, and thank you for such wonderful software!!!!!!

I also closed linked issue #1501


Run JSHint on tests

JSHint was not run on the tests.
The failure is the same as in #1034, too long lines. Fix it, or ignore it in tests?

:+1:

:+1:


Set up logging

Before we move to full production mode, i.e. before NewCantus replaces OldCantus, we should really have some kind of logging set up.

I know technically how to set this up, and have a sense of what we'd want to have logs on in case something goes wrong, but I've never set up logging for an actual project before, so I'd be happy to hear suggestions/pointers/etc. about how best to approach this.

I didn't foresee the specifics of #1098, but this is exactly the kind of situation I was worried might occur where good logs could have been useful. And they would have been!
upgrading this to high priority. While it's not urgent, it really warrants some attention. After we finish cleaning up #1098 and a handful of other in-process tasks, I hope to properly attend to this.

As discussed earlier today, to begin work on this issue, we must:

set up the infrastructure for handling logging and making sure it persists
write documentation explaining how to include logging
as work on CantusDB proceeds into the future, we add logging statements to the code, but only to places we touch (i.e., not trying to do a full pass through the codebase all at once)

@lucasmarchd01 will bring up at next lab meeting!


What is the process for using the code to implement Nerf Slam technology images I take in real time?

What is the process for using the code to implement Nerf Slam technology images I take in real time?

Same question....

Same question....
I didn't do Nerf-Slam in real-time.

Did you do Nerf-slam in real-time?

ok.thank you.

@Frankz78 something like orbslam3 is your best bet


Fix duplicate nicks (maybe)

Due to the rarity of this bug, I suspect there is some kind of race condition going on where we send a NAMES request, and in the meantime users have joined on the server so we get them back as a result. But then we also receive their respective JOINs after the names list, so we add them to our existing list.
Well even if it's not it, it should fix the problem anyway so whatever.

To anyone who experience the issue (I never saw it ever), it would be great if you could merge this branch in your instance and paste us the log when you notice duplicate nicks in the list.  (I am not using ZNC though)
Do we want to commit to this PR? I am not too convinced by it, and it seems like you feel it might not even fix the issue...
Is there an associated issue? I couldn't find it in the issue list.
My opinion is to close this PR for now to clean up the PR list since we won't merge, and wait to see if someone reports this issue again. If they do, let's open an issue, you point them to your branch, and we take it from here. Sounds good?

Yeah, I have no idea how people manage to get that bug. Might as well be a node issue on their end as well, seems like these people also tend to be using quite massively outdated node versions.


Cannot remove from favorites

I've just installed hoobs on raspberry pi 4 (4GB RAM) and running 5 hikvision cameras in 360p of sub stream with vcodec: copy. Video is a bit laggy. Unable to remove from favourites. plz help!!!

flip the favorite flag, then flip it on then off again. It’s a HomeKit bug.


Update index.js

⛔ Snyk has found 2 issues.

Icon
Severity
Issues

Critical
0

High
0

Medium
2

Low
0

✅ security/snyk check is completed. No issues were found. (View Details)
✅ license/snyk check is completed. No issues were found. (View Details)
⛔ code/snyk check is completed. Snyk found 2 issues. (View Details)


Roll engine 0e2c8feeeb47..0d114c0c2fed (6 commits)

https://github.com/flutter/engine/compare/0e2c8feeeb47...0d114c0c2fed
git log 0e2c8feeeb47..0d114c0c2fed --first-parent --oneline
2020-03-09<EMAIL_ADDRESS>Add libfreetype6-dev to desktop Linux dependencies (flutter/engine#17020)
2020-03-09<EMAIL_ADDRESS>Disable shell benchmarks (flutter/engine#17038)
2020-03-09<EMAIL_ADDRESS>Fix bounds of image_filter_layer (flutter/engine#16960)
2020-03-09<EMAIL_ADDRESS>Record fml and shell benchmarks (flutter/engine#16991)
2020-03-09<EMAIL_ADDRESS>Roll src/third_party/skia c56950442dd1..23899c64e3db (11 commits) (flutter/engine#17033)
2020-03-09<EMAIL_ADDRESS>use commit date instead of author date (flutter/engine#17032)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Gold has detected one or more untriaged digests on patchset 6.
Please triage them at https://flutter-gold.skia.org/search?issue=52287.

Commit queue failed; closing this roll.


Update README.md to include Hugging Face Spaces'links

Reference: https://github.com/google-research/maxim/issues/30#issuecomment-1291613089

@vztu FYI.

Thanks @sayakpaul!


Add release notes for 4.1.1

Realized that the previous release notes have been mistakenly omitted.


cowboy:start_http does not work and gives a run-time error.

When I made the following change code runs without any problem.

Yes that example has not been converted yet.

The example has been converted and a test has been added. Thanks!


Migrate from Travis to GitHub Actions

Travis is no longer free for open source, and we've exceeded our allotment. https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing

Resolved by e521d4d


bool expression || and &&

Current behavior (how does the issue manifest):
Here are 2 examples regarding && and ||

$activity[GetByCompositeKey].code == 200 && $activity[GetByCompositeKey].result[0].key != $flow.agreement.AgreementID
$activity[GetByCompositeKey].code == 400 || $activity[GetByCompositeKey].code == 400

Today we are going to evaluate both the right and left sides. but we don't need to

If left expression is false and we don't need to evaluate the right expression for &&
We don't need evaluate the right expression if the left expression is true for ||

Expected behavior:

If left expression is false and we don't need to evaluate the right expression for &&
We don't need evaluate the right expression if the left expression is true for ||

Minimal steps to reproduce the problem (not required if feature enhancement):
Please tell us about your environment (Operating system, docker version, browser & web ui version, etc):
Flogo version (CLI & contrib/lib. If unknown, leave empty or state unknown): 0.X.X
Additional information you deem important (e.g. issue happens only occasionally):

Fixed at PR https://github.com/project-flogo/core/pull/195


vue build err (Dom7)

when i user vue-awesome-swiper in vue , build err ;
ERROR in static/js/vendor.....Unexpected token:name [static/js/vende.....]

same question here

version:
"vue": "^2.5.2",
"vue-awesome-swiper": "^3.0.4",

sorry,I check out  my webpack file and add this code solved my problem
alias: {
'swiper$': 'swiper/dist/js/swiper.js'
}

Webpack - webpack.config.js:
alias: {
  'swiper$': 'swiper/dist/js/swiper.js'
}

Nuxt.js - nuxt.config.js
build: {
  extend(webpackConfig) {
     webpackConfig.resolve.alias['swiper$'] = 'swiper/dist/js/swiper.js'
     webpackConfig.resolve.alias['dom7$'] = 'dom7/dist/dom7.js'
  }
}

If you are encountering errors while packing with webpack, please refer to the solution here #206 #204. Add the corresponding alias code in your webpack config.
alias: {
  'swiper$': 'swiper/dist/js/swiper.js'
}

v3.0.6 fix it.

For anyone coming from google in 2020:
The solution above has moved to "'swiper/js", you can use
alias: {
  'swiper$': 'swiper/js/swiper.min.js'
}

Im using
"swiper": "^5.4.0",
"vue-awesome-swiper": "^4.1.1"


gRPC Proxying on Kubernetes is not working

Note: If you have a general support question and are looking for a quicker response, please checkout our discord channel for answers from the community:
https://aka.ms/dapr-discord
In what area(s)?

/area runtime

/area operator

/area placement

/area docs

/area test-and-release

Ask your question here
I'm trying to follow the Kubernetes example for gRPC Proxying and I have no luck. It works fine with dapr run locally but when I try to do the same thing on Kubernetes I get the following error:
  File "/project/helloworld/client.py", line 14, in run
    response = await stub.SayHello(request=HelloRequest(name='you'), metadata=metadata)
  File "/usr/local/lib/python3.8/site-packages/grpc/aio/_call.py", line 290, in __await__
    raise _create_rpc_error(self._cython_call._initial_metadata,
grpc.aio._call.AioRpcError: <AioRpcError of RPC that terminated with:
	status = StatusCode.UNAVAILABLE
	details = "failed to connect to all addresses"
	debug_error_string = "{"created":"@1636338980.842821977","description":"Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":3158,"referenced_errors":[{"created":"@1636338980.842735374","description":"failed to connect to all addresses","file":"src/core/lib/transport/error_utils.cc","file_line":147,"grpc_status":14}]}"

Steps I take:

dapr init -k
Applying the config mentioned here: https://docs.dapr.io/developing-applications/building-blocks/service-invocation/howto-invoke-services-grpc/
Here is the config:

apiVersion: dapr.io/v1alpha1
kind: Configuration
metadata:
  name: serverconfig
spec:
  tracing:
    samplingRate: "1"
    zipkin:
      endpointAddress: http://localhost:9411/api/v2/spans
  features:
    - name: proxy.grpc
      enabled: true

Deploy my Server app using the config mentioned in the tutorial:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: grpc-app
  namespace: default
  labels:
    app: grpc-app
spec:
  replicas: 1
  selector:
    matchLabels:
      app: grpc-app
  template:
    metadata:
      labels:
        app: grpc-app
      annotations:
        dapr.io/enabled: "true"
        dapr.io/app-id: "server"
        dapr.io/app-protocol: "grpc"
        dapr.io/app-port: "50051"
        dapr.io/config: "serverconfig"
spec:
      containers:
      - name: helloworld
        image: myrepo/helloworld:v1
        imagePullPolicy: Never #it's local
        ports:
        - containerPort: 50051

Applying the config for the test client:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: testapp
  labels:
    app: foo
spec:
  replicas: 1
  selector:
    matchLabels:
      app: foo
  template:
    metadata:
      labels:
        app: foo
      annotations:
        dapr.io/enabled: "true"
        dapr.io/app-id: "testapp"
        dapr.io/app-protocol: "grpc"
        dapr.io/app-port: "50007"
        dapr.io/config: "serverconfig"
    spec:
      containers:
      - name: foo
        image: myrepo/testapp:v1
        imagePullPolicy: Never
        ports:
          - containerPort: 50007

Any idea why this is not working? I check the logs on the server and it's listening on the port but the client apparently cannot find it. Again, as I mentioned, the app works locally using dapr run. I also checked the dapr app name and they are consistent.

Update: sending on port 50001 on Kubernetes works and it doesn't get configured to send on port 50007

Update: sending on port 50001 on Kubernetes works and it doesn't get configured to send on port 50007

The Dapr gRPC port is 50001, that's what you should be using.

@yaron2 Is there a way to set this up in Kubernetes config?