Access to additional NHM BA variables

Hi there,
I'm back again with other variable questions. The datasets in the 'nhm-v1.1-c404-bc-catalog', available currently on hovenweep, provide the variable 'hru_actet', but do not provide any of the component / secondary variables composing this bulk variable. Those secondary variables are:

intcp_evap | Evapotranspiration from canopy surfaces for each HRU, inches
hru_impervevap | Evapotranspiration from impervious surfaces for each HRU, inches
dprst_evap_hru | Evapotranspiration from surface-depression strorage for each HRU, inches
perv_actet | Actual ET from the capillary reservoir of each HRU, inches
snow_evap | Evaporation and Sublimation from snowpack on each HRU, inches

Is there any way to get ahold of these secondary variables? Or is it similar to the other datasets, where an archive lives on Black Pearl but can't be readily accessed?
This is for a project where we want to assess the partitioning of evaporation and transpiration in models using water isotope approaches. The 'perv_acetet' variable is effectively the transpiration component, so would be necessary for this goal.
Thank you!
Annie

@pnorton-usgs do you have any insights here? I'm not familiar with the NHM outputs.

@putmanannie - While these variables are not part of the current NHM release runs I can re-run the model and include additional variables. It could take a few weeks for me to do this. Are you needing these variables for a particular calibration level (e.g. byHRU, byHW, byHWobs for the CONUS404-bc forced model?

@pnorton-usgs That would be awesome. To double check, the byHWObs calibration is the result of the full calibration, right (per fig below)? If so, we would like that one. Another question: would it be easier to run a subset of years?

@aputman-usgs - I have re-run the NHM CONUS production runs and added the variables you requested (hru_impervevap, hru_intcpevap, dprst_evap_hru, hru_perv_actet, snow_evap). Let me know if you run into any problems.

Thank you, Parker!


Create Cucumber MANY framework to allow easy writing of BDD tests

There should be a way to write tests with a minimum of Rust code or knowledge. This is to help specification writers write tests about their specification while writing the specification (in the same PR).
Cucumber seems to be the ideal framework for this. Tests are written in pre-conditions, actions and assertions, using a language that resembles plain english. This would allow us to write a test for example (not final):
# Requires ledger and ledger_command attributes.
@attribute-2 @attribute-6
Scenario: Ledger can send tokens
    Given an identity id1
    And an identity id2
    And a symbol MFX
    Given id1 has 100 MFX
    When id1 send 50 MFX to id2
    then the balance of id1 should be 50 MFX
    then the balance of id2 should be 50 MFX

This tracking issue should track the work of writing the framework and the feature files for the current test suite (all the integration tests in https://github.com/liftedinit/many-framework).

There should be some Given that describes messages, like:
Given a send message "ledger.send" with "{ 0: <from>, 1: <to>, 2: <amount>, 3: <symbol> }".

This would allow features to describe messages. Just an idea for milestone 2. For the first round, let's just pretend actions are already defined in the code itself.

Since all the id requirements are needed before starting a many-ledger server, I've took the liberty of adding one more step in the example feature, Given the server is started, where the configuration files are generated from the previous steps and the server is actually started.

PR is done, will be reviewed and merged this week. After which we will add more and more tests (including the implementations of the sentences).


[Get Familiar][Core] Improve output image labels

Steps

Follow Readme to setup and run OMRChecker
Set show_image_level = 4 or 5
Run OMRChecker on sample images
For each image that you see, try to add appropriate labels to each output image using cv2.putText, etc so that they are more understandable. For any queries discuss in discord.
You can create them in separate PRs if needed.

Note: this issue is marked with the hacktoberfest label. Follow #hacktoberfest-discussions on Discord for further details .

Hey, can I try to solve this?

sure @05Alston, you can discuss your approach or ask for any help in the discord channel. Link in description.

Merged

Creating a clone of this issue for further enhancements! Please feel free to pick this up again


Publish context as npm package

We should publish a DCC contexts as an npm package, so it can be consumed as described here: https://github.com/digitalcredentials/sign-and-verify-core/issues/3
See an example of how Digital Bazaar does this in did-context

Implemented in PR #4, closing.


Revert "[fix] (scan) push down expr in agg and mor"

Reverts apache/doris#38379

run buildall

run buildall


[zh] sync self-subject-review-v1beta1.md

Sync with en text:
content/zh-cn/docs/reference/kubernetes-api/authentication-resources/self-subject-review-v1beta1.md

See preview please.

/lgtm
/approve


Tom's Simple storage mod Incompatibility

For some reasson, any books of lore put into a storage network from Tom's simple Storage mod https://www.curseforge.com/minecraft/mc-mods/toms-storage-fabric cannot be taken out once they are put in

Thanks for the report. Ill try to look into it, but seems maybe like an issue on their end

Cannot replicate in 1.19.2.


[FEATURE] Save checkpoint interval

How can I edit the save-checkpoint inverval for my model?
While training with high epochs, old checkpoints are often overwitten by new checkpoints.
In my case, the last 10 checkpoints are usually over-fit so I want to avoid that by adding saving interval, keeping my old checkpoints without taking up too much spaces for checkpointing.
How can I do this?
Thank you!

@ngfuong there's no interval to skip some subset of epochs for eval & save ... but you can use --checkpoint-history 20 to say keep the last 20 epochs of eval checkpoints.

@ngfuong there's no interval to skip some subset of epochs for eval & save ... but you can use --checkpoint-history 20 to say keep the last 20 epochs of eval checkpoints.

Thank you for replying!
Since I intend to implement this feature, which files should I modify to add this?


How to increase build with distcc pump?

It looks distcc's pump is able to override environment variables to use it's own compiler binary wrapper. But I see no way how to increase number of parallel make jobs via MAKEOPTS. Please help me.

Please note we may immediately close your issue without comment if you do not fill out the issue template and provide the requested information.


fix unit tests

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 63.26%. Comparing base (c878f2c) to head (f290325).
Report is 10 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #217      +/-   ##
==========================================
- Coverage   64.27%   63.26%   -1.02%
==========================================
  Files          91       91
  Lines        2819     2937     +118
  Branches      461      512      +51
==========================================
+ Hits         1812     1858      +46
- Misses       1005     1077      +72
  Partials        2        2

Flag
Coverage Δ

63.26% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


preset-ant-design does't work with TypeScript

What happens?
Ant Design components in Storybook does not have any styling applied to them.
It does however work if I change both the MyComponent.tsx and MyComponent.stories.tsx to MyComponent.js and MyComponent.stories.js.
I also tried adding the preset-typescript package which did not change anything.
.storybook/config.js
import { configure } from '@storybook/react'

const componentsReq = require.context('../src/components', true, /\.stories.tsx$/)

function loadStories() {
  componentsReq.keys().forEach(componentsReq)
}

configure(loadStories, module)

.storybook/presets.js
module.exports = [
  {
    name: '@storybook/preset-ant-design',
    options: {
      lessOptions: {
        modifyVars: {
          'layout-body-background': '#ffffff',
          'layout-header-background': '#ffffff',
        },
      },
    },
  },
]

I just discovered that it is only the source component (MyComponent.tsx) that needs to be either .js or .jsx for the preset to apply the styling. Hence it is no problem that the storybook file of MyComponent uses .stories.tsx

Still a problem with the preset though, right?

Still a problem with the preset though, right?

Either that or it has something to do with how Storybook consumes .tsx imports when using presets (this is pure speculation though).

Is there any update on how to resolve this? @antonbramsen

Is there any update on how to resolve this? @antonbramsen

@SuspensionPoint to my knowledge this has not been resolved, it has however been a long time since I looked at it and the project I worked on has since then been archived, but according to a referenced commit I have to this issue, we just ended up importing the antd/dist/antd.css in the storybook config.
And then for overriding ant design styling we used a config-overrides.js file:
const { override, fixBabelImports, addLessLoader } = require('customize-cra')
module.exports = override(
  fixBabelImports('import', {
    libraryName: 'antd',
    libraryDirectory: 'es',
    style: true,
  }),
  addLessLoader({
    javascriptEnabled: true,
    modifyVars: {
      '@white': '#ffffff',
      '@primary-color': '#03273B',
      '@primary-color-bright': '#FFB904',
      '@secondary-color-light': '#CCDDE3',
      '@secondary-color-medium': '#1C7690',
      '@alert': '#FF7537',
      '@text-color': '@primary-color',
      '@text-color-light': '@white',
      '@size-base': '10px',
      '@border-color-base': '@primary-color',
      '@body-background': '@secondary-color-light',
      '@layout-header-background': '@white',
      '@layout-body-background': '@white',
      '@layout-header-padding': '0',
      '@item-active-bg': '@primary-color',
      '@item-hover-bg': '@primary-color',
    },
  })
)


Missing Microsoft.DBforPostgreSQL/servers/configurations

https://www.pulumi.com/docs/reference/pkg/azure-nextgen/dbforpostgresql/
it's presented in non-nextGen Azure provider: https://www.pulumi.com/docs/reference/pkg/azure/postgresql/configuration/

@XBeg9 This is because currently we are modeling resources which have create and delete endpoints. Configurations has a create/update endpoint but no delete. We are currently evaluating options to cover such resources. FWIW you can use the azure provider along side the azure-nextgen provider. Would creating configuration through the azure provider be an option in the meantime?

@viveklak thanks for the reply! Using azure and azure-nextgen side-by-side is what I am doing right now and it works without any issues!


Configurable 403 rbac response body

Describe the feature request
Firstly, sorry for the issue repetition, this is very similar to the last one. Just wanted to separate concerns.
We are looking to invest eng time in the upstream codebase to move some of our long standing EnvoyFilters back into the codebase, as first class features - if the use cases are considered acceptable.
--
We would like to be able to configure the body returned in Gateway rbac 403 responses. We are mandated to use a more "anonymous" header value by security org.
Describe alternatives you've considered
Today we use an EnvoyFilter;
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: rbac-message-override
  namespace: istio-system
spec:
  workloadSelector:
    labels:
      istio: ingressgateway
  configPatches:
    - applyTo: NETWORK_FILTER
      match:
        context: GATEWAY
        listener:
          portNumber: 443
          filterChain:
            filter:
              name: envoy.filters.network.http_connection_manager
      patch:
        operation: MERGE
        value:
          name: "envoy.filters.network.http_connection_manager"
          typed_config:
            "@type": "type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager"
            local_reply_config:
              mappers:
                - filter:
                    status_code_filter:
                      comparison:
                        op: EQ
                        value:
                          default_value: 403
                          runtime_key: local-reply-runtime-key # This key is REQUIRED for filter compilation. See https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/accesslog/v3/accesslog.proto#envoy-v3-api-msg-config-accesslog-v3-comparisonfilter
                  body:
                    inline_string: "Forbidden"

This works well, but we always want to eliminate EnvoyFilters in place of first class APIs where possible.
I would be willing to invest resources in this myself, if the Istio developers consider this is reasonable and feasible. I don't consider it important enough at all to waste your time. Having said that, I am not as familiar with the Istio codebase as I'd like to be, so I can't estimate the difficulty of supporting this.
We have a somewhat similar API available for the server response header (thanks John!), so something similar could be considered here?
Greatly appreciate any feedback! Thanks.
Affected product area (please put an X in all that apply)
[ ] Ambient
[ ] Docs
[ ] Dual Stack
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context

cc @kyessenov I think you had some designs around merging something like this?

Yeah, the above seems like a reasonable feature request. There's basically two ways to do this: either a local template or a remote service via redirect. Most (regulatory) use cases can be solved with the local template. My proposal was something like this add to ProxyConfig:
message CustomErrorHeader {
  string key = 1;
  string value = 2; // Template for the header value with %MACRO%s
}
message CustomErrorResponse {
  string status_code = 1; // Status code filter, e.g. "403", "503", "4xx",
                          // "5xx", but should extend to gRPC
  string body = 2; // Template for the default body with %MACRO% expansion.
  repeated CustomErrorHeader headers = 3; // Optional error headers.
  int64_t override_status_code = 4; // Optional change to the status code.
}
message CustomErrorResponses {
  string default_body = 1; // Template for the default body, e.g.
                           // %RESPONSE_CODE%: %RESPONSE_CODE_DETAILS%
  repeated CustomErrorResponse mappers = 2; // Distinct errors for the
                                            // specific status codes.
}
CustomErrorResponses custom_error_responses = ...


Add support for com.github.ben-manes.caffeine:caffeine:3.1.2

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

No.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Add support for com.github.ben-manes.caffeine:caffeine:3.1.2.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Null.

Additional context
Add any other context or screenshots about the feature request here.

Metadata generated at https://github.com/linghengqian/graalvm-trace-metadata-smoketest/issues/1 .

Linkes to https://github.com/apache/shardingsphere/issues/21347 .

I'm working on this issue.

To be honest, caffeine's unit tests use more dependencies than I imagined. I'm in the process of refactoring most of my unit tests to the standard Junit Jupiter + AssertJ combo.

dependencies {
    testImplementation 'org.junit.jupiter:junit-jupiter-api:5.9.2'
    testRuntimeOnly 'org.junit.jupiter:junit-jupiter-engine:5.9.2'
    testImplementation 'com.github.ben-manes.caffeine:caffeine:3.1.2'
    testImplementation 'org.mockito:mockito-core:5.0.0'
    testImplementation 'org.mockito:mockito-junit-jupiter:5.0.0'
    testImplementation 'org.hamcrest:hamcrest:2.2'
    testImplementation 'org.testng:testng:7.7.1'
    testImplementation 'com.google.truth:truth:1.1.3'
    testImplementation 'org.awaitility:awaitility:4.2.0'
    testImplementation 'uk.org.lidalia:lidalia-slf4j-ext:1.0.0'
    testImplementation 'com.google.truth.extensions:truth-java8-extension:1.1.3'
    testImplementation 'it.unimi.dsi:fastutil-core:8.5.11'
    testImplementation 'com.google.guava:guava:31.1-jre'
    testImplementation 'com.google.guava:guava-testlib:31.1-jre'
    testImplementation 'org.jctools:jctools-core:4.0.1'
    testImplementation 'site.ycsb:core:0.17.0'
    testImplementation 'com.github.valfirst:slf4j-test:2.8.1'
    testImplementation 'org.apache.commons:commons-lang3:3.12.0'
    testImplementation 'org.jooq:joor-java-8:0.9.14'
    testImplementation 'org.eclipse.collections:eclipse-collections:11.1.0'
    testImplementation 'org.jetbrains.kotlinx:lincheck:2.16'
    testImplementation 'info.picocli:picocli:4.7.0'
}


can Metro support notify icon/ bubble notification?

Notify Icon

bubble notification

it can be shown at  right top position of screen

these feature is already supported in HandyControl , Since I am currently using metro, the styles of the two are not the same, can these functions be supported in future?

@li-zheng-hao You can also use one of these libraries which are theme aware of MahApps, so you can style it to your needs:

https://github.com/hardcodet/wpf-notifyicon
https://github.com/Federerer/Notifications.Wpf


redisson plugin support high version

Please answer these questions before submitting pull request

Why submit this pull request?

[ ] Bug fix

[x] New feature provided

[ ] Improve performance

Related issues
resolve https://github.com/apache/skywalking/issues/3762

Low version（3.6.0）

High version（3.11.5）

New feature or improvement

Use reflection to avoid no such method, because they are all modified in the construction method, so the performance will not be much lower

resolve https://github.com/apache/skywalking/issues/3762

This interceptor is for client management, right? So, even using reflect should not cause a performance concern. Am I right?

This interceptor is for client management, right? So, even using reflect should not cause a performance concern. Am I right?

Yes.

Workload 2 has over 200 cases, and group1 is full I think. Later, group2 should have available slots, and workload 1.

Workload 2 has over 200 cases, and group1 is full I think. Later, group2 should have available slots, and workload 1.

OK


Last input character is still visible even when deleted when using a custom font

I'm a beginner with pixijs and pixijs ui, sorry if I made a beginner mistake and thanks for your work.
Expected Behavior
When deleting the last character of an input field that use a custom font, the character is erased from the input so no character is visible.
Current Behavior
When deleting the last character of an input field that use a custom font, the character is not erased from the input and is still visible even if it has been deleted (if you move out of the input field, the last character is replaced by the placeholder).
Steps to Reproduce

Input content in the input
Delete all the characters

When not using a custom font the behavior is the expected one.
Environment

version: 2.0.0 for ui, 8.1.0 for pixi.js
Browser & Version: Firefox 124.0.2, Chrome 123.0.6312.123, Safari 17.3.1
OS & Version:  Mac OS 13.6.4
Code example: https://github.com/archiloque/tactical-fulcrum , the input code is at https://github.com/archiloque/tactical-fulcrum/blob/main/src/editor/enemies_tab.ts#L90 , the code can be run locally with npm run dev

You should retry using latest pixi.js version. v8.5.x had a few improvements on measureText that helped solve similar problems.


youtube-dl seems to ignore port in m3u8 url

Checklist

[ x] I'm reporting a broken site support
[ x] I've verified that I'm running youtube-dl version 2019.08.13
[ x] I've checked that all provided URLs are alive and playable in a browser
[ x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[ x] I've searched the bugtracker for similar issues including closed ones

Verbose log

youtube-dl --verbose "http://driveproxy.net/drive/MlA3M2xCUmNSU3RlQWoyYW1HMllYQT09.html?hls=1"
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'http://driveproxy.net/drive/MlA3M2xCUm
NSU3RlQWoyYW1HMllYQT09.html?hls=1']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2019.08.13
[debug] Python version 3.4.4 (CPython) - Windows-7-6.1.7601-SP1
[debug] exe versions: ffmpeg 3.2.1
[debug] Proxy map: {}
[generic] MlA3M2xCUmNSU3RlQWoyYW1HMllYQT09: Requesting header
WARNING: Falling back on generic information extractor.
[generic] MlA3M2xCUmNSU3RlQWoyYW1HMllYQT09: Downloading webpage
[generic] MlA3M2xCUmNSU3RlQWoyYW1HMllYQT09: Extracting information
[generic] hdplay: Downloading m3u8 information
ERROR: Failed to download m3u8 information: HTTP Error 404: Not Found (caused by
 HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you
 are using the latest version; type  youtube-dl -U  to update. Be sure to call y
outube-dl with the --verbose flag and include its complete output.
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp5b8vs7
2_\build\youtube_dl\extractor\common.py", line 627, in _request_webpage
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp5b8vs7
2_\build\youtube_dl\YoutubeDL.py", line 2229, in urlopen
  File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
  File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
  File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
  File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
  File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_defau
lt

Description

Downloading gives a 404 error in yt-dl but not in browser.
From another tool I know that this link refers to an m3u8 file on an url similar to this one:
http://<IP_ADDRESS>:8080/hdplay-cache/eygdlhm7z2rmda63yoljex3wbqjds5dxbzezx2eqm3b2rrhg7bdqrk4a5jux6jc4sdgyaltbd7mayyasp77rt45zjvaroti6ombp2e7m2l3v5jodgkfntvqlckin3iicrzu5pm2g6n5wcds7jrve5mzzaic3ctuifzdfmghit747iu7st66lo3sdjzb7avhj3ymyqg5foa/hdplay.m3u8?SD
Beware however that the actual IP address changes all the time. With a browser I can download the m3u8 with no problems, but yt-dl cannot find it. It seems to ignore the fact that the URL needs to be found at port 8080 and not the default http-port. Seems like a pretty basic thing...

I suspect that the problem isn't with the m3u3 port but that the browser is sending a referer header whereas youtube-dl isn't. Try running youtube-dl with
--referer "http://driveproxy.net/drive/MlA3M2xCUmNSU3RlQWoyYW1HMllYQT09.html"


Please remove r34.app

Hey, Rule 34 App author here
I take it as a compliment that you have added support for my project, but I have not given you permission to use it, nor I allow anyone to use it for their own projects
Please remove it

Okey, thank you, im already work on it. 🥭


x509: certificate signed by unknown authority

Hello,
I have followed the steps in the article to set up a fleet-server, but for some reason the fleet-server does not like the self signed certificate. I double checked all the environment variable flags and they appear correct. Or at least identical to the gitlab repo.
Any suggestions would be greatly appreaciated.
Cheers,
Erwin
FLEET env vars:
# env | grep ^FLEET_
FLEET_SERVER_POLICY_ID=fleet-server-policy
FLEET_INSECURE=true
FLEET_SERVER_ELASTICSEARCH_HOST=https://es01:9200
FLEET_SERVER_CERT_KEY=/certs/fleet-server/fleet-server.key
FLEET_SERVER_INSECURE_HTTP=true
FLEET_ENROLL=1
FLEET_SERVER_ELASTICSEARCH_CA=/certs/ca/ca.crt
FLEET_SERVER_ELASTICSEARCH_INSECURE=true
FLEET_URL=https://fleet-server:8220
FLEET_SERVER_CERT=/certs/fleet-server/fleet-server.crt
FLEET_SERVER_ENABLE=1
FLEET_CA=/certs/ca/ca.crt

fleet-server log
{"log.level":"info","@timestamp":"2023-12-04T00:11:11.363Z","message":"request accepted","component":{"binary":"apm-server","dataset":"elastic_agent.apm_server","id":"apm-default","type":"apm"},"log":{"source":"apm-default"},"log.origin":{"file.line":61,"file.name":"middleware/log_middleware.go"},"service.name":"apm-server","user_agent.original":"apm-agent-python/6.17.0 (my_python_service)","http.request.id":"ebe88572-690c-4c26-ae07-8b9e938434d6","log.logger":"request","http.request.method":"POST","url.original":"/intake/v2/events","event.duration":711917,"http.response.status_code":202,"ecs.version":"1.6.0","source.address":"<IP_ADDRESS>","ecs.version":"1.6.0"}

{"log.level":"error","@timestamp":"2023-12-04T00:11:12.683Z","message":"precondition failed: x509: certificate signed by unknown authority","component":{"binary":"apm-server","dataset":"elastic_agent.apm_server","id":"apm-default","type":"apm"},"log":{"source":"apm-default"},"log.logger":"beater","log.origin":{"file.line":64,"file.name":"beater/waitready.go"},"service.name":"apm-server","ecs.version":"1.6.0","ecs.version":"1.6.0"}

{"log.level":"error","@timestamp":"2023-12-04T00:11:14.449Z","message":"Failed to connect to backoff(elasticsearch(https://es01:9200)): Get \"https://es01:9200\": x509: certificate signed by unknown authority","component":{"binary":"metricbeat","dataset":"elastic_agent.metricbeat","id":"beat/metrics-monitoring","type":"beat/metrics"},"log":{"source":"beat/metrics-monitoring"},"ecs.version":"1.6.0","log.logger":"publisher_pipeline_output","log.origin":{"file.line":150,"file.name":"pipeline/client_worker.go"},"service.name":"metricbeat","ecs.version":"1.6.0"}

{"log.level":"info","@timestamp":"2023-12-04T00:11:14.449Z","message":"Attempting to reconnect to backoff(elasticsearch(https://es01:9200)) with 4 reconnect attempt(s)","component":{"binary":"metricbeat","dataset":"elastic_agent.metricbeat","id":"beat/metrics-monitoring","type":"beat/metrics"},"log":{"source":"beat/metrics-monitoring"},"log.logger":"publisher_pipeline_output","log.origin":{"file.line":141,"file.name":"pipeline/client_worker.go"},"service.name":"metricbeat","ecs.version":"1.6.0","ecs.version":"1.6.0"}

{"log.level":"error","@timestamp":"2023-12-04T00:11:14.456Z","message":"Error dialing x509: certificate signed by unknown authority","component":{"binary":"metricbeat","dataset":"elastic_agent.metricbeat","id":"beat/metrics-monitoring","type":"beat/metrics"},"log":{"source":"beat/metrics-monitoring"},"network":"tcp","address":"es01:9200","ecs.version":"1.6.0","log.logger":"esclientleg","log.origin":{"file.line":38,"file.name":"transport/logging.go"},"service.name":"metricbeat","ecs.version":"1.6.0"}

Upgraded to 8.9.0 and this issue went away.

Yeah i was fooled by the indentation in the yaml example for Advanced YAML configuration from Getting started with the Elastic Stack and Docker Compose: Part 2.
ssl:
certificate_authorities:
- |

Should be:
ssl:
  certificate_authorities:
     - |

thanks @olitooni and @ehogeweg!
For any future people following the guide:
Another error source for me were old certs. So, I also removed all es-cluster prefixed docker volumes like es-cluster_certs.

Yeah I was fooled by the indentation in the yaml example for Advanced YAML configuration from Getting started with the Elastic Stack and Docker Compose: Part 2.
ssl:
certificate_authorities:
- |

Should be:
ssl:
  certificate_authorities:
     - |

Hi Are you sure there must be 5 spaces for the "- |" ?

Ah sorry. Corrected with another error. Fixed it now.

thanks @olitooni and @ehogeweg!
For any future people following the guide: Another error source for me were old certs. So, I also removed all es-cluster prefixed docker volumes like es-cluster_certs.

Sorry, is that what it makes that the docker names have the "es-" thing before their real names? like they are shown in the following "sudo docker ps" output?
sudo docker ps --format 'table {{.ID}}\t{{.Names}}\t{{.Status}}\t{{.RunningFor}}'
CONTAINER ID   NAMES               STATUS                    CREATED
7f1ed5cdc635   es-fleet-server-1   Up 30 minutes             32 minutes ago
30975ea6ecee   es-kibana-1         Up 31 minutes (healthy)   32 minutes ago
8958cf6a57ed   es-es01-1           Up 32 minutes (healthy)   32 minutes ago
8affb78cca39   es-webapp-1         Up 32 minutes             32 minutes ago
oellc@RT620:~/elk/elk-docker$

then, if so, how can I remove that? i.e., how can I do what you are quoting?

When settings things up, docker creates volumes for the certs. However, when you mess up and have to create new certificates you first have to remove the old certs volumes otherwise you keep using the old ones and no new ones are generated.

just my two cents, if you start the docker-compose project, and you've made an error in your cert config:

without having to completely remove all your containers,
you can prune the affected volumes,
edit your cert related actions in the docker-compose yml
restart the cluster

When settings things up, docker creates volumes for the certs. However, when you mess up and have to create new certificates you first have to remove the old certs volumes otherwise you keep using the old ones and no new ones are generated.

Oh I see. That's why the Fleet Server never "integrates" into Kibana because the ca.crt is not "updated". Thanks!

Thank you for this great tutorial!
I did not get this working using the suggested method.
I did get it working by directly pointing to the certificate in the YAML config:
ssl.certificate_authorities: ["/certs/ca/ca.crt"]

Thank you for this great tutorial! I did not get this working using the suggested method.
I did get it working by directly pointing to the certificate in the YAML config: ssl.certificate_authorities: ["/certs/ca/ca.crt"]

Struggling with the same issue here... In which yaml config did you put this?

Since this was asked directly to me: I did this in the user interface.

ssl.certificate_authorities: ["/certs/ca/ca.crt"]

Very nice!!!

I am using this setup with STACK_VERSION=8.15.0 and I was getting this error in the logs of the fleet-server:
"message":"no CA certificate matching the fingerprint","component":
To fix this I followed what was discussed here: https://discuss.elastic.co/t/elastic-agent-ca-trusted-fingerprint-does-not-working-but-the-certificate-works/362239/3
The output edit fields that worked to resolve that error:

The automation way would be to add the following to the kibana.yml:
xpack.fleet.outputs:
  - id: elasticsearch
    name: Elasticsearch
    type:  elasticsearch
    hosts: ["https://es01:9200"]
    is_default: true
    config:
      ssl:
        certificate_authorities: ["/certs/ca/ca.crt"]

I also added a pull request:
https://github.com/elkninja/elastic-stack-docker-part-two/pull/7


Renesas: Smartbond: Add MIPI DBI Driver Support

@ioannis-karachalios can you take a look at the CI/compliance failures?

@ioannis-karachalios can you take a look at the CI/compliance failures?

Sure. I was just waiting for your complete feedback.

Sure. I was just waiting for your complete feedback.

Understood. I'll continue giving feedback, but I would start addressing the failures. It is difficult to give a final review when CI is failing, since the contents of the PR will necessarily have to change in order for it to merge.

@danieldegrasse I am done with all the changes requested. Let me know if more updates are required.

#69410 is also required so the LCD controller can handle partial updates appropriately.

@danieldegrasse many thanks for reviewing this PR.


tokenize problem

Hello, your project is really helpful for me, but I am confused about how this model embeds words like "lemongrass" which will be tokenized as [lemon. ##grass] in Bert. Could you please illustrate it :)

Hi,
This model learns static word embeddings in the end and if lemongrass is in the vocab(which it should for the trained models) it'll return the static emedding for it. The BERT tokenization is only used for training these static embeddings.


Oauth autentication example not working

Hi, i have two problems, the first is that when i execute the authentication request it doesn't prompt any link.
The second is that i don't know what kind of link i should put in the url variable.
if someone have any idea of what i'm missing i'll be very grateful

So, adding a print url after "print('Go to this url in your browser, and paste the code below')" got the job done.


ML 1.9 : Hypothesis Testing (D) #1258

Description 📜
Made documentation on the topic of Hypothesis Testing and the ways we can perform the testing along with suitable examples.
Fixes #1258

Type of change 📝

[x] Doc#umentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Machine #Learning

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@Isha307, I will add the bullet points and make it attractive and get back soon Mam.

@Isha307, I have added the bullet points, where ever necessary, can you please look into that and merge the PR if everything is fine.


Incompatibility with Rom 3.2.0

Having upgraded Rom to 3.2.0, we get this error now when initialising rom-yesql
Other than dropping back to Rom 3.1.0; is there a workaround?
ArgumentError: wrong number of arguments (0 for 1)
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-yesql-0.4.0/lib/rom/yesql/gateway.rb:29:in `block in <class:Gateway>'
  (eval):6:in `instance_exec'
  (eval):6:in `block in __initialize__'
  (eval):6:in `fetch'
  (eval):6:in `__initialize__'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/dry-initializer-1.3.0/lib/dry/initializer.rb:36:in `initialize'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-yesql-0.4.0/lib/rom/yesql/gateway.rb:71:in `initialize'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-3.2.0/lib/rom/gateway.rb:78:in `new'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-3.2.0/lib/rom/gateway.rb:78:in `setup'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-3.2.0/lib/rom/environment.rb:51:in `block in normalize_gateways'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-3.2.0/lib/rom/environment.rb:45:in `each'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-3.2.0/lib/rom/environment.rb:45:in `each_with_object'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-3.2.0/lib/rom/environment.rb:45:in `normalize_gateways'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-3.2.0/lib/rom/environment.rb:25:in `configure_gateways'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-3.2.0/lib/rom/environment.rb:18:in `initialize'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-3.2.0/lib/rom/configuration.rb:24:in `new'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-3.2.0/lib/rom/configuration.rb:24:in `initialize'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-3.2.0/lib/rom/create_container.rb:48:in `new'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-3.2.0/lib/rom/create_container.rb:48:in `initialize'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-3.2.0/lib/rom/create_container.rb:58:in `new'
  /Users/shipmana/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rom-3.2.0/lib/rom/create_container.rb:58:in `container'```

I'll update it to work with 3.2 today, thank for reporting

@mrship 0.5.0 is on rubygems 🎉

Much obliged. This (obviously) doesn't work with 3.1.0 though so it might be worthwhile adding a fixed dependency on rom > 3.2 for the next version, as we had some issues when upgrading getting the dependencies right.
Thanks for the quick response.

Ugh, right, thank for spotting this, I'll release 3.2.1 with a bumped dep


question

How do i make my ip forword to a domain name. Like https://hrng.io/
My local IP is http://<IP_ADDRESS>:3010/ and i wil like to forword it to my domain www.p2k.nl
How to do that.
Please help me

That's way out of scope to help you out with but take a look at some basic tutorials on nginx reverse proxying, DNS, etc. I run my install on an AWS EC2 instance with proxying taking place on the same server, but you could also run an rproxy from somewhere else to your local IP if preferred.


feat: Add service_version setter to configurator

PR #417 added a setter to the configurator for service.name - this follows suite by adding the same for service.version to simplify the setting of the other attribute requested by many tracing backends.
Prior to this change, setting the pair of these would have looked like this:
c.service_name = 'Otel Demo App'
c.resource = OpenTelemetry::SDK::Resources::Resource.create(
  OpenTelemetry::SDK::Resources::Constants::SERVICE_RESOURCE[:version] => '0.6.0'
)

After this change, the same is accomplished with this:
c.service_name = 'Otel Demo App'
c.service_version = '0.6.0'

I'm late to the party and ultimately fine with this change. I wanted to get folks pulse on a possible alternative. Rather than add one off configuration for various resource attributes, would it make sense to make setting them a little easier? Just so we don't end up with n-different ways to set resources, I was thinking we could repurpose the c.resource method to accept either a Resource, or a Hash of resrouce attributes. This way you could do something like:
sdk= OpenTelemetry::SDK.configure do |c|
  c.resource = { 'service.name' => 'my service', 'service.version' => '0.0.1', 'some.attr` => 'some value' }
 ...
end

I'm not sure if this a better solution, but I just wanted to throw it out there.

I'm not sure if this a better solution, but I just wanted to throw it out there.

I agree with your sentiment. But if it ends up just being these two, then I think it is fine to leave this the way it is.  If we go for a third we should rework it to be a bit more flexible for adding resources.

The current solution helps with maintaining semantic conventions without excessive verbosity. Repurposing the c.resource= method is nice, but doesn't help with either semantic conventions or verbosity.

WFM. I think service name and service version are important enough to have as first class configure options. I suppose we can always consider repurposing c.resource =  as an additional niceity  in the future.

It already does accept a hash. Note the custom attribute in this block:
  c.resource = OpenTelemetry::Resource::Detectors::AutoDetector.detect
  c.resource = OpenTelemetry::SDK::Resources::Resource.create({
    OpenTelemetry::SDK::Resources::Constants::SERVICE_RESOURCE[:name] => service_name,
    OpenTelemetry::SDK::Resources::Constants::SERVICE_RESOURCE[:version] => version,
    'abs_component' => ENV['ABS_COMPONENT'],
  })

I was recommending making the OpenTelemetry::SDK::Resources::Resource.create part optional, so that a hash could be passed in alone. It seems that looking up the attribute key constants is also a bit cumbersome. It was just an idea I wanted to float, but am happy with the first class config for service name and service version as-is.

I was recommending making the OpenTelemetry::SDK::Resources::Resource.create part optional

Ahh, didn't quite catch that that was the intent. I would be very much in favor of that.


Update README.md with Authentication and Authorization details

Added additional details in pre-reqs document for Terraform templates

Luis...looks good.  Reviewed @4:57 PM EST 10/27/23.


Adds partner logos for activity footers

Adds project/theme specific text for footers
Changed theme names in the sample docs to show a variety of themes

Some notes on footer:
When no project or footer text is specified, default text will be shown.
Because of the logo transparencies, I made the logo section have a white background, but this should probably be fixed when themes are introduced.
Most footer logos are stored as a an array in ProjectTypes, except for NGSS Assessments. The logos for that project were embedded in many different parts of the footer.


timeouted payment can never be completed

When calling up a payment like
sumupmerchant://pay/1.0?affiliate-key=XXXXX&app-id=XXXXX&amount=1.00&currency=EUR&title=ICard-Payment&receipt-mobilephone=+491720000&receipt-email=xxx@xxx.de&foreign-tx-id=2-1001-54-20160415-7&callback=mycallbackscheme://result
then letting the "insert card" time out, any further attempt to start payment for the same foreign-tx-id will just fail "Die Zahlung konnte aufgrund von Netzwerkproblemen nicht durchgeführt werden. Die Karte wurde nicht belastet. Sie können die Durchführung der Zahlung noch einmal versuchen."
Contrary to what is written, it probably not a network issue, and no retry will ever succeed.
E/SumUp   ( 4282): (SourceFile:31)@main | Event rpcEventCheckout - Reason:
E/SumUp   ( 4282): (SourceFile:31)@main | Error for in emv response:
...
java.io.FileNotFoundException: https://static.sumup.com/images/checkout/result/connection_error@1.5x.png?v=5

It works well again for any other foreign-tx-id

We are aware of this issue, it will be fixed in a future version of the app

Thank you for reporting anyway!

Does this effect only special cases or all usages of foreign-tx-id?
Are there any known workarounds ? (This renders all safeguards discussed in issue 1 unusable... )
Any timeline for the fix? (days, months, far future)
(We are currently unsure whether we should continue with sumup integration at all at this point...)

Not sure how this relates to issue 1, can you elaborate? As documented, foreign-tx-id` has to be unique in the scope of the merchant account, so the behaviour of the app is as expected - Just the error you get back is wrong.
If your issue is with the misleading error message, we can put the fix for this into the development pipeline. We are currently in release preparation for the next app release, so the fix for this bug will not make it into the next version. The one after that should be feasible though. If this is too long for you, we can supply you a test version for development.

No, I do not care for a wrong error message.
My problem is:

payment is attempted for foreign-tx-id 123
and fails for whatever reason
now 123 is still unpaid in pos
thus another payment is attempted foreign-tx-id 123
but will never succeed.
To successfully pay the bill with sumup, we must total-void in the pos, and reenter all positions so it will become new tx 124 ...

This behaviour is as expected. We have to keep a record for each transaction attempt, it it is successful or not. If you start a transaction with foreign-tx-id 123, you need to use a different one for the second attempt. Otherwise foreign-tx-id could not uniquely identify a transaction.

Okay, so foreign-tx-id is not meant to be the POS-side's own transaction id, but just a POS-generated unique-id-per-payment-attempt.
So this must be remembered (persistently) on the POS side for each POS transaction if we want to be able to use https://api.sumup.com/v0.1/me/transactions?foreign_transaction_id=XXX in order to query if a broken/crashed/timeouted (on POS side) payment attempt was successful in SumUp app anyway...
Okay, this is doable, albeit with unexpected additional work on POS side...

Yes, exactly. We will discuss if we can make the documentation more clear at this point.


iPad keyboard "next" doesn't close select2 dropdown

If the dropdown is open and someone clicks the iPad keyboard shortcut for "next" or "previous" the dropdown stays open often covering the next input box.  It also doesn't open the dropdown then those buttons are used to focus to a select2 box.

This is a duplicate of https://github.com/select2/select2/issues/4013.


feat!: upgrade minimum node version to v20

As taken from the GitHub Blog:

Node 16 has reached its end of life, prompting us to initiate
its deprecation process for GitHub Actions. Our plan is to
transition all actions to run on Node 20 by Spring 2024.

This Pull Request:

updates the minimum supported version of commisery-action to Node20.
updates the used GitHub Actions to the latest version (supporting Node20)

see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/
thanks-to: @brunorosa-tomtom

Thanks a lot @brunorosa-tomtom :100:

@KevinDeJong-TomTom just so I learn a few more things: what was needed to finalize the changes? I think I missed some npm magic, but couldn't find a straightforward doc to guide me...

BTW, another (?) npm magic seems to have failed :(((
https://github.com/tomtom-international/commisery-action/actions/runs/7708784324/job/21008603828


Improve code readability & Merge stylesheets

Merged stylesheets into a singular file

Create .github directory

Remove code whitespace

Add meta tags

Fix indentation on some elements

Rename ThankYou.html to thankyou.html

@Zyphaex thank you for your contribution could you add any few medicinal plants you know into this project and if you like this repo give it a star


Create E2E Aquilon broker install scripts for RHEL7

Test out end-to-end install of Aquilon broker for RHEL7/Fedora and/or CentOS. Create either detail step guide or automated script to deploy Aquilon broker.

@urbonegi we should create pan templates and bootstrap it with quattor. we can use the same tempaltes to actually manage the aquilon broker after installation too

Sure - but before starting to create a template we need a set of steps that would make Aquilon broker deploy and run. I still fail to successfully deploy it E2E on RHEL7.4. Was trying yesterday reading the Installation guide in Quattor website - will continue further. If you have working more up to date guide for RHEL7?

no i don't. if you need help with the debugging, i can free up some time this afternoon to help out.
i think @jrha and @samary were also going to try today

Updated installation documentation should provide the basis requested by @urbonegi. Based on my experience, I am not convinced at all that providing an Aquilon package would make the life easier. The current installation process, based on using the Git repo, is very flexible, in particular when it comes to upgrades (easy to revert using branches) or to test/install modifications until they are merged upstream.
As for providing a template for bootstrapping the broker from Quattor, it may be useful mainly for sites currently running SCDB (but that means almost all current Quattor sites!). I did the effort at LAL. This is currently a site-specific template (in fact several!) but I could easily share them. I think that making them generic should not be a huge work and we could then add them to the template library, as we have done for the AII server.


Task 1

Message box displaying Welcome message

@muthyasravani
please provide PR number in respective task on tracker.
Task – 1
Code verified. Change Default activity names and provide annotations

Task – 2
Code verified.


Versioning Issues.

Please change the way the mod requires create mod. Create mod had a bug in which you couldn't put "unbreakable" on the back tank, place it in a contraption to refill it, then pick it back up, it would clear the "unbreakable" tag making it start taking damage again.  When I mentioned this to the create developers, they either fixed it or had previously fixed it in an upcoming version, but your mod makes it impossible to use the updated version. Your mod uses exact versioning on its requirement of create mod, and should be using a minimum requirement instead. As in, it should be set up "requires 0.5.1-f or later" not "requires 0.5.1-f".

It uses exact versioning because things might break. Will try to port soon.

it uses create 0.5.1-f now


fabric 1.19.2 fabricproxy-lite 2.3.0 connect nullpointerexception

Using a clean server folder with fabric-server-mc.1.19.2-loader.0.14.10-launcher.0.11.1.jar, FabricProxy-Lite-2.3.0.jar and
hackOnlineMode = true
hackEarlySend = true
hackMessageChain = true
secret = "asecret"

(I've tried variations on the above as well)
velocity-3.1.1-98.jar set to player-info-forwarding-mode = modern and the same secret from above. I also have ping-passthrough = description so I can see the minecraft servers MOTD in the velocity MOTD to tell me the connection is working ("Hi Velocity").
I get the following when trying to connect with a plain 1.19.2 fabric client:
Failed to connect to the server

Internal Exception: io.netty.handler.codec.DecoderException:
java.lang.NullPointerException: Cannot invoke "net.minecraft.class_2539$class_4532.method_22310(int, net.minecraft.class_2540)" because the return value of "java.util.Map.get(Object)" is null.

Both Velocity (<IP_ADDRESS>:25577) and Minecraft server (server-ip=<IP_ADDRESS>, server-port=30066) and client all on same host (Velocity using home = "<IP_ADDRESS>:30066")
Hopefully I've not done a stupid, but I just can't get it to connect. Nothing in Velocity or Minecraft server logs.
If I try to directly connect, I get the "This server requires you to connect with velocity" warning as expected, and a server log message to that effect.

I suspect a subtle issue with velocity configuration. I will update this when I figure it out in case someone else gets stuck on this in future.

The stable version of Velocity does not support Minecraft 1.19... sigh.


[Fix #15991] Pseudo-class :hover styles should allow class .hover

[Fix #15991] Pseudo-class :hover styles should also be enabled with the class selector .hover

Wanted to follow up on this and check if it was missing anything.

Wanted to follow up on this and check if it was missing anything.

Eh, I'm not so sure we need to address this one. The .focus is there for our JS components—we make no use of .hover on our end.

Punting on adding this to v3.


Can't save the cropped image

Hi
After cutting the image, how can I save this image?
Thanks,
Hadas

Even I am getting this problem...

@faizsameerahmed96 @hgelb paste your code

@altaf2892 it's according to your code (Android-Image-Cropper)

@hgelb i m able to save so it will be more specific if u show your implementation.

@altaf2892 I downloaded your code, but I didn't see how can I save the cropped image. can you please share me an example code for this issue please? or to direct me to the relevant class?

@altaf2892 please see in CropImage.startPickImageActivity method. how can I get the cropped image and save it to gallery layout (in this activity, like in the camera)?

I don't know what do you mean by "save" so..

Picking image from camera/gallery doesn't "save" it anywhere, it makes it available for the code to do whatever you want.
Saving an image "Gallery" is not related to the functionality of this library, never had to do it so you will have to google it as I would have to.

thx @altaf2892 for trying to help.

@hgelb as @ArthurHub said not functionality ..but to get cropped image u can use getCroppedImage() method and can save it wherever u want(google how to create folder ans save image to it)

@hgelb as @ArthurHub said not functionality ..but to get cropped image u can use getCroppedImage() method and can save it wherever u want(google how to create folder and save image to it)


IfStatementAssignment False Positives on Function Signature

PHPMD version: 2.7.0
PHP Version: PHP 7.2.19
Installation type: composer
Operating System / Distribution & Version: (Windows 10 / CentOS 7.6 / ...): Ubuntu

Current Behavior
Rule ifstatementassignment is thrown on a function signature that does not contain any if-statement assignments.
Full Function where Rule is Thrown:
public function setOrganizations() : AssociateRecords
    {
        if ($this->request->has('organizations')) {
            // get the user's current organizations so we can properly set updated user / date
            $currentOrganizations = $this->user->organizations->keyBy('id');
            $organizationIDs      = Organization::findMany($this->request->get('organizations'))
                                    ->pluck('id');
            $toSync               = collect();

            // loop over each ID and update or modify the record
            $organizationIDs->each(function ($id) use ($currentOrganizations, $toSync) {
                $createdAt = new \DateTime;
                $createdBy = auth()->id();

                if ($currentOrganizations->has($id)) {
                    /** @var Organization $org */
                    $org       = $currentOrganizations->get($id);
                    $createdAt = $org->pivot->created_at;
                    $createdBy = $org->pivot->created_by;
                }

                $toSync->put($id, [
                    'created_at'  => $createdAt,
                    'created_by'  => $createdBy,
                    'updated_at'  => new \DateTime(),
                    'modified_by' => auth()->id(),
                ]);
            });

            // sync
            $this->user->organizations()->sync($toSync->toArray());
        }

        return $this;
    }

Expected Behavior
The rule should not be thrown in the example code above. I'm not sure exactly what is causing it to trigger. I thought it was the type hinted return type but removing that didn't resolve it.
Steps To Reproduce:
Explain all the steps you did to create this bug so we can reproduce it.

I have been using phpmd on my code base for quite a while and not encountered this violation before
my code base has not changed significantly and these lines are not newly created. I'm not sure why this just started happening, it popped up in a CI / CD build recently.
I updated to the latest version of phpmd 2.7 in hopes that it would be resolved, but that did not help.

Checks before submitting

[x] Be sure that there isn't already an issue about this. See: Issues list
[x] Be sure that there isn't already a pull request about this. See: Pull requests
[x] I have added every step to reproduce the bug.
[x] If possible I added relevant code examples.
[x] This issue is about 1 bug and nothing more.
[x] The issue has a descriptive title. For example:  "JSON rendering failed on Windows for filenames with space".

Hi, this is fixed and will be released in 2.7.1. See #661
Thanks.

Thanks! Sorry for the duplicate. I saw those but thought they were fixed in 2.7.0.

Try to require "phpmd/phpmd": "dev-master", if you have your bug with it, I would re-open the issue.


Add Download Links To README

We kinda need download links for ruby, gem and bundler. So people can find the programs a lot easier. Without spending time searching for the programs.

Bump

why would a normal user need to install this?

A user who does not have the knowledge to download these dependancies does not have the proper knowledge to run and contribute to this repository.
Also, bumping issues/pull requests is highly discouraged.

Oh okay :P


ARROW-1331: [JAVA] Refactor unit tests

[cc @jacques-n , @StevenMPhillips ]
Refactored the java-vector unit tests in TestValueVector.java
(1) Moved all the BitVector related tests to TestBitVector.java
(2) Enhanced and added the tests for different vector types and grouped them into different categories in TestValueVector.java
(3) Moved https://github.com/dremio/dremio-oss/blob/master/sabot/kernel/src/test/java/com/dremio/exec/vector/TestSplitAndTransfer.java to arrow. This currently has splitAndTransfer() test for NullableVarCharVector.
(4) No tests have been removed -- they have either been enhanced or moved around for grouping.
Recently we added splitAndTransfer tests for BitVector, UnionVector and ListVector in their respective test files.  We should ideally move all the splitAndTransfer() related tests to TestSplitAndTransfer.java and should try to cover other vector types as well. A follow-up will address this (I want to keep the patch size small for easy review).

Unit tests should not check for 0 values in fixed width vectors at positions where no data has been set. No assumption can be made about the value -- it is garbage.

Does this look good?

Can this be merged?

@icexelloss @jacques-n @StevenMPhillips can you take a look?
I would probably wait until after the 0.6.0 release vote is completed to merge more patches

I scan through the changes the it looks good. But this is particular hard to review line by line.
@siddharthteotia, is there anything in particular you want to be reviewed?

LGTM +1


'Style Settings' Plugin warning is shown even when Style Settings is installed and enabled

I am creating a minimal repro for a different issue, and so have a vault with:

Only community plugin is Style Settings
Only core plugin is File Explorer
No snippets

When I go to the Appearance pane, I see this:

Yet community plugins settings shows this:

I installed Style Settings after Prism, having seen this warning.
I have reopened this vault, and yet the Style Settings warning still shows.

I tried going to the Style Settings plugin's Settings pane, and selecting "Reset all settings to default" - which created the settings file for the plugin, with this content:
{}

The warning did not go away.

I then increased the Scrollbar Width a bit, which changed the Style Settings's settings to:
{
  "obsidian-prism-theme@@scroll-bar-size": 12
}

And still I see:

Maybe it's intended that this red warning always be shown?

Hi @claremacrae,
I recently added the warning instead of the screenshot as that felt like the most unobtrusive and immediate way to make sure new users of the theme will know that Style Settings is a requirement. I didn't think of having it disable after Style Settings gets enabled, however it was actually quite trivial.
Style Settings adds this class .css-settings-manager to the Body. So I used this  body:not(.css-settings-manager) prefix for the selectors used to replace the screenshot with the warning and it now it will returns to normal when Style Settings is enabled and show when it's disabled.
Thank you for reporting this and taking the time to do your own testing. Will add this fix in the coming update.

Hi @damiankorcz
Many thanks for the swift and helpful reply.
I do think the message is a good thing. From my notes, I ran Prism previously and gave up on it, and I do now wonder whether that was because I didn't have Style Settings installed...

What is the nature of the problem if Style Settings is not installed, may I ask?

@claremacrae, It's mostly due to how I've setup the theme to work with Style Settings. The default options for customisable settings are using custom classes that are added by Style Settings to the HTML Body; hence why when it's enabled they all trigger and make the theme look as it should. If Style Settings isn't enabled they don't get picked up at all making things look unfinished/broken. Can see how that would scare away new users.
Style Settings is where the customisability, additional features and most of this theme's efforts were placed. Since a lot of popular themes also make use of it I just hopped most users would have it installed and enabled anyway making it a non issue.
Now that It has been brought up a few times by users, it's definitely on the list to fix. Just need to get around to address it 😅

@claremacrae, Yeah it's a brilliant addition for theme makers for sure. @mgmeyers did a brilliant job with it.
For example when using custom colours I can create an option for the user to select a colour from a colour picker in Style Settings which will create a variable I specify in the id field; in this case h1-border-color-custom-lt.

Then I can use that variable to change the border colour like so (there are multiple formats in which the colour can be exported from the setting):

You can also triggered any CSS you want by using a custom class and prefixing it onto your selectors. The value fields are what will be added as custom classes to the HTML Body depending on what the user selects; in this case from a dropdown.
In this case pt-status-bar-position-top will trigger all the selectors I added it to and move the Status Bar to the top of the window overlapping the Titlebar.

Here for example I'm using that class stacked with another custom class to have the Titlebar Text hide when the Status Bar is set to display at the top and is aligned horizontally to the centre. Just to clarify, there are other things that these custom classes are added to make this work this is just one of them I'm using as an example.

I hope that somewhat clarifies how, at least I, use Style Settings in Prism.

This should now be addressed in Version 1.3.0.


Support for Kiwi Browser

Can you add support for Kiwi Browser? It's an Android browser supports chromium extensions. I installed it in the browser but it's act and looks weird, so for now I'm using just one square.

Btw, how do we change the square to rectangle? I'm trying to put all of them in one square. I did this and the greeting message went up under toolbar and can't scroll it back to visibility.

How do I add two squares side by side and fit it in the browser?

The thing is UI is not responsive for mobile devices. It's not a browser specific issue, instead the page is not responding to the smaller screen size.
I will try to fix this as much as possible but there might be issues supporting multiple squares and might break the overall design language of startpage in which case I cannot guarantee that you would love using it 😅 .

The thing is UI is not responsive for mobile devices. It's not a browser specific issue, instead the page is not responding to the smaller screen size.
I will try to fix this as much as possible but there might be issues supporting multiple squares and might break the overall design language of startpage in which case I cannot guarantee that you would love using it 😅 .

How about another repo just for Mobile Devices? I understand if you don't agree, it's time consuming and waste of time to develop just for one user 😅.
If it might break something, you should ignore this issue then.


highlight group style

Good day to you!
is it possible to set style (bold, underscore, etc.) to highlight groups in setup function?

e.g. `... colors.InactiveStyle = "bold: ..."
Thank you!

you need to  set it when you create a highlight group { fgcolor,bgcolor, style}
colors.color_name is only a hex rgb string
you can see a sample here
https://github.com/windwp/windline.nvim/blob/36bdcd225c893f3fa507bfc3b9e68fe139c25312/lua/wlsample/bubble.lua#L29

Thank you!


🐛 "no non-static method" error only on release mode

What's happening?
I'm using expo SDK 50 managed workflow and while on dev mode (npx expo run:android -d --variant debug) everything works really fine but running a release build (npx expo run:android -d --variant release) my app crash when trying to open the camera view.
I'm using my own face detector plugin and it's working really fine on debug mode.
I think this is something related to #2168
Full crashlytics error:
Error: Exception in HostFunction: java.lang.NoSuchMethodError: no non-static method "Lcom/mrousavy/camera/frameprocessor/FrameProcessor;.<init>(Lcom/facebook/jni/HybridData;)V", js engine: hermes, stack:
setFrameProcessor@1:1674615
onViewReady@1:1674705
invokeGuardedCallbackImpl@1:371841
invokeGuardedCallback@1:371898
invokeGuardedCallbackAndCatchFirstError@1:371930
executeDispatch@1:372059
executeDispatchesAndReleaseTopLevel@1:376253
forEachAccumulated@1:373535
anonymous@1:376616
batchedUpdatesImpl@1:434780
batchedUpdates@1:376169
_receiveRootNodeIDEvent@1:376454
receiveEvent@1:429381
__callFunction@1:133914
anonymous@1:132354
__guard@1:133295
callFunctionReturnFlushedQueue@1:132312
       at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:75)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:142)
       at com.facebook.react.bridge.JavaModuleWrapper.invoke(:21)
       at com.facebook.jni.NativeRunnable.run(SourceFile)
       at android.os.Handler.handleCallback(Handler.java:789)
       at android.os.Handler.dispatchMessage(Handler.java:98)
       at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage()
       at android.os.Looper.loop(Looper.java:164)
       at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(:37)
       at java.lang.Thread.run(Thread.java:764)

Reproduceable Code
import {
  StyleSheet,
  Text,
  View
} from 'react-native'
import {
  useEffect,
  useState
} from 'react'
import {
  Camera,
  useCameraDevice,
  useFrameProcessor
} from 'react-native-vision-camera'
import {
  detectFaces,
  DetectionResult
} from 'react-native-vision-camera-face-detector'
import { Worklets } from 'react-native-worklets-core'

export default function App() {
  const device = useCameraDevice('front')

  useEffect(() => {
    (async () => {
      const status = await Camera.requestCameraPermission()
      console.log({ status })
    })()
  }, [device])

  const handleDetectionWorklet = Worklets.createRunInJsFn( (
    result: DetectionResult
  ) => {
    console.log( 'detection result', result )
  })
  const frameProcessor = useFrameProcessor((frame) => {
    'worklet'
    runAsync(frame, () => {
      'worklet'
      detectFaces(
        frame,
        handleDetectionWorklet, {
          // detection settings
        }
      )
    })
  }, [handleDetectionWorklet])

  return (
    <View style={{ flex: 1 }}>
      {!!device? <Camera
        style={StyleSheet.absoluteFill}
        device={device}
        frameProcessor={frameProcessor}
        pixelFormat="yuv"
      /> : <Text>
        No Device
      </Text>}
    </View>
  )
}

Relevant log output
adb logcat "*:S" ReactNative:V ReactNativeJS:V 'FaceDetector':

02-13 08:20:07.566 18791 18856 I ReactNativeJS: Loading react-native-worklets-core...
02-13 08:20:07.570 18791 18856 I ReactNativeJS: Worklets loaded successfully
02-13 08:20:07.883 18791 18856 W ReactNativeJS: `new NativeEventEmitter()` was called with a non-null argument without the required `addListener` method.
02-13 08:20:07.884 18791 18856 W ReactNativeJS: `new NativeEventEmitter()` was called with a non-null argument without the required `removeListeners` method.
02-13 08:20:07.908 18791 18856 I ReactNativeJS: Running "main
02-13 08:20:18.462 18791 18856 E ReactNativeJS: Error: Exception in HostFunction: java.lang.NoSuchMethodError: no non-static method "Lcom/mrousavy/camera/frameprocessor/FrameProcessor;.<init>(Lcom/facebook/jni/HybridData;)V", js engine: hermes
02-13 08:20:19.344 18791 18856 E ReactNativeJS: Error: Exception in HostFunction: java.lang.NoSuchMethodError: no non-static method "Lcom/mrousavy/camera/frameprocessor/FrameProcessor;.<init>(Lcom/facebook/jni/HybridData;)V"
02-13 08:20:19.344 18791 18856 E ReactNativeJS:
02-13 08:20:19.344 18791 18856 E ReactNativeJS: This error is located at:
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Camera
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in RCTView
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Unknown
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in RCTView
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Unknown
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Index
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Index
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in RCTView
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Unknown
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Index
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in StaticContainer
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in EnsureSingleNavigator
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in SceneView
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in RCTView
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Unknown
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in DebugContainer
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in MaybeNestedStack
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in RCTView
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Unknown
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in RNSScreen
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Unknown
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Suspender
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Suspense
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Freeze
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in DelayedFreeze
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in InnerScreen
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Screen
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in SceneView
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Suspender
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Suspense
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Freeze
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in DelayedFreeze
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in RNSScreenStack
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in ScreenStack
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in NativeStackViewInner
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in RCTView
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Unknown
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in SafeAreaProviderCompat
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in NativeStackView
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in PreventRemoveProvider
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in NavigationContent
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Unknown
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in NativeStackNavigator
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in AuthPages
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Index
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Index
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in AuthProvider
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in NotificationProvider
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in EnsureSingleNavigator
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in BaseNavigationContainer
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in ThemeProvider
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in NavigationContainerInner
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in RNCSafeAreaProvider
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in SafeAreaProvider
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in ThemeProvider
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in RCTView
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Unknown
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Portal.Host
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in RNCSafeAreaProvider
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in SafeAreaProvider
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in SafeAreaProviderCompat
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in PaperProvider
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in RCTView
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Unknown
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in KeyboardAvoidingView
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in ThemeProvider
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Index
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in RCTView
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Unknown
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in RCTView
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in Unknown
02-13 08:20:19.344 18791 18856 E ReactNativeJS:     in AppContainer, js engine: hermes

adb logcat | grep com.mrousavy.camera :

02-13 08:34:01.324 20702 20772 W unknown:ViewManagerPropertyUpdater: Could not find generated setter for class com.mrousavy.camera.CameraViewManager
02-13 08:34:26.377 20702 20770 E ReactNativeJS: Error: Exception in HostFunction: java.lang.NoSuchMethodError: no non-static method "Lcom/mrousavy/camera/frameprocessor/FrameProcessor;.<init>(Lcom/facebook/jni/HybridData;)V", js engine: hermes
02-13 08:34:26.403 20702 20772 E AndroidRuntime: com.facebook.react.common.JavascriptException: Error: Exception in HostFunction: java.lang.NoSuchMethodError: no non-static method "Lcom/mrousavy/camera/frameprocessor/FrameProcessor;.<init>(Lcom/facebook/jni/HybridData;)V", js engine: hermes, stack:
02-13 08:34:27.530 20702 20770 E ReactNativeJS: Error: Exception in HostFunction: java.lang.NoSuchMethodError: no non-static method "Lcom/mrousavy/camera/frameprocessor/FrameProcessor;.<init>(Lcom/facebook/jni/HybridData;)V"
02-13 08:34:33.580 20702 20702 E CameraSession:         at com.mrousavy.camera.core.e.n0(Unknown Source:107)
02-13 08:34:33.580 20702 20702 E CameraSession:         at com.mrousavy.camera.core.e.S(Unknown Source:240)
02-13 08:34:33.580 20702 20702 E CameraSession:         at com.mrousavy.camera.core.e.x0(Unknown Source:136)
02-13 08:34:33.580 20702 20702 E CameraSession:         at com.mrousavy.camera.core.c.O(Unknown Source:199)
02-13 08:34:33.580 20702 20702 E CameraSession:         at com.mrousavy.camera.core.c$j.invokeSuspend(Unknown Source:32)
02-13 08:34:33.580 20702 20702 E CameraSession:         at com.mrousavy.camera.core.c.r0(Unknown Source:14)
02-13 08:34:33.580 20702 20702 E CameraSession:         at com.mrousavy.camera.core.c.G(Unknown Source:0)
02-13 08:34:33.580 20702 20702 E CameraSession:         at com.mrousavy.camera.core.c$i.surfaceDestroyed(Unknown Source:33)
02-13 08:34:33.581 20702 20702 W System.err:    at com.mrousavy.camera.core.e.n0(Unknown Source:107)
02-13 08:34:33.581 20702 20702 W System.err:    at com.mrousavy.camera.core.e.S(Unknown Source:240)
02-13 08:34:33.581 20702 20702 W System.err:    at com.mrousavy.camera.core.e.x0(Unknown Source:136)
02-13 08:34:33.581 20702 20702 W System.err:    at com.mrousavy.camera.core.c.O(Unknown Source:199)
02-13 08:34:33.581 20702 20702 W System.err:    at com.mrousavy.camera.core.c$j.invokeSuspend(Unknown Source:32)
02-13 08:34:33.581 20702 20702 W System.err:    at com.mrousavy.camera.core.c.r0(Unknown Source:14)
02-13 08:34:33.581 20702 20702 W System.err:    at com.mrousavy.camera.core.c.G(Unknown Source:0)
02-13 08:34:33.581 20702 20702 W System.err:    at com.mrousavy.camera.core.c$i.surfaceDestroyed(Unknown Source:33)

Camera Device
{
  "hardwareLevel": "limited",
  "minExposure": -20,
  "neutralZoom": 1,
  "minZoom": 1,
  "supportsFocus": false,
  "formats": [],
  "supportsLowLightBoost": false,
  "hasTorch": false,
  "supportsRawCapture": false,
  "minFocusDistance": 0,
  "sensorOrientation": "landscape-right",
  "maxZoom": 4,
  "physicalDevices": [
    "wide-angle-camera"
  ],
  "isMultiCam": false,
  "position": "front",
  "id": "1",
  "hasFlash": false,
  "maxExposure": 20,
  "name": "FRONT (1)"
}

Device
Galaxy J5 with android 8
VisionCamera Version
both 3.8.2 and 3.9.0-beta.3
Can you reproduce this issue in the VisionCamera Example app?
I didn't try (⚠ your issue might get ignored & closed if you don't try this)
Additional information

[X] I am using Expo
[X] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Are you using ProGuard?

Thanks for the issue report, I found a fix: https://github.com/mrousavy/react-native-vision-camera/pull/2546 :) 💪

This is not true. Please only post correct information

@mrousavy Thanks for quick response, I was writing a reply about ProGuard and you already found the fix XD.

This is not true. Please only post correct information

Sorry, my bad.

I also noticed that this error happens only when opening app at first time, if I reopen it there's no crash but frame processors doesn't work.

Unfortunately there's nothing I can do without logs and potentially a symbolicated stack trace. Please try to get those from the crash, then I can help you

First, I'm using proguard on my expo app (enabled it on BuildProperties)
I got some runtime logs, here they are:
31876-31951 unknown:ViewManagerPropertyUpdater  Could not find generated setter for class com.mrousavy.camera.CameraViewManager
31876-31951 CameraDevices                       Camera #0 is now available.
31876-31951 CameraDevices                       Camera #1 is now available.
31876-31948 ReactNativeJS                       Loading react-native-worklets-core...
31876-31948 ReactNativeJS                       Worklets loaded successfully
31876-31948 VisionCameraProxy                   Initializing VisionCameraProxy...
31876-31948 VisionCameraProxy                   Creating Worklet Context...
31876-31948 VisionCameraProxy                   Worklet Context created!
31876-31948 CameraManager                       getCameraCharacteristics : cameraId = 0
31876-31948 CameraManager                       getCameraCharacteristics : cameraId = 0
31876-31948 CameraManager                       getCameraCharacteristics : cameraId = 1
31876-31948 CameraManager                       getCameraCharacteristics : cameraId = 1
31876-31948 FrameProcessorPluginRegistry        Looking up Frame Processor Plugin "detectFaces"...
31876-31948 FrameProcessorPluginRegistry        Frame Processor Plugin "detectFaces" found! Initializing...
31876-31876 PreviewView                         Creating PreviewView...
31876-31876 PreviewView                         PreviewView is 0x0, rendering 720x1280 content. Resizing to: 0x0 (COVER)
31876-31876 CameraView                          Updating CameraSession...
31876-31940 CameraSession                       configure { ... }: Waiting for lock...
31876-31940 CameraSession                       configure { ... }: Updating CameraSession Configuration... Difference(deviceChanged=true, outputsChanged=true, sidePropsChanged=true, isActiveChanged=true)
31876-31940 CameraSession                       Configuring inputs for CameraSession...
31876-31940 PersistentCameraCaptureSession      --> setInput(1)
31876-31951 zygote                              Deoptimizing void com.facebook.react.uimanager.n0.<init>() due to JIT inline cache
31876-31940 CameraSession                       Destroying previous outputs...
31876-31940 CameraManager                       getCameraCharacteristics : cameraId = 1
31876-31951 zygote                              Deoptimizing void com.facebook.react.uimanager.d1.t(com.facebook.react.uimanager.m0, int, com.facebook.react.uimanager.o0) due to JIT inline cache
31876-31940 CameraSession                       Creating outputs for Camera #1...
31876-31940 CameraSession                       Adding 2560x1440 Photo Output in JPEG...
31876-31940 Surface                             sf_framedrop debug : 0x4f4c, game : false, logging : 0
31876-31940 CameraSession                       Adding 1920x1080 Video Output in YUV_420_888...
31876-31940 VideoPipeline                       Initializing 1920 x 1080 Video Pipeline (format: YUV)
31876-31940 Surface                             sf_framedrop debug : 0x4f4c, game : false, logging : 0
31876-31940 VideoPipeline                       Using ImageReader round-trip (format: #35)
31876-31940 VideoPipeline                       Using legacy API for CPU ImageReader...
31876-31940 Surface                             sf_framedrop debug : 0x4f4c, game : false, logging : 0
31876-31951 zygote                              Deoptimizing void com.facebook.react.uimanager.d1.V(int, com.facebook.react.bridge.ReadableArray) due to JIT inline cache
31876-31951 zygote                              Deoptimizing void com.facebook.react.uimanager.n0.d(com.facebook.react.uimanager.n0, int) due to JIT inline cache
31876-31940 Surface                             sf_framedrop debug : 0x4f4c, game : false, logging : 0
31876-31940 PersistentCameraCaptureSession      --> setOutputs([PHOTO (2560x1440 in JPEG), VIDEO (1920x1080 in YUV)])
31876-31940 CameraSession                       Successfully configured Session with 2 outputs for Camera #1!
31876-31940 CameraSession                       Updating Video Outputs...
31876-31940 VideoPipeline                       Removing RecordingSession Output...
31876-31940 PersistentCameraCaptureSession      --> setRepeatingRequest(...)
31876-31940 PersistentCameraCaptureSession      --> setIsActive(false)
31876-31940 PersistentCameraCaptureSession      Configure() with isActive: false, ID: 1, device: null, session: null
31876-31940 PersistentCameraCaptureSession      Creating new device...
31876-31940 CameraManager                       Camera #1: Opening...
31876-31940 CameraManager                       getCameraCharacteristics : cameraId = 1
31876-31876 zygote                              Deoptimizing android.view.View com.facebook.react.uimanager.ViewManager.createViewInstance(int, com.facebook.react.uimanager.y0, com.facebook.react.uimanager.o0, com.facebook.react.uimanager.x0) due to JIT same target
31876-31951 CameraDevices                       Camera #1 is now unavailable.
31876-31951 CameraManager                       getCameraCharacteristics : cameraId = 1
31876-31945 CameraManager                       Camera #1: Opened!
31876-31940 PersistentCameraCaptureSession      Creating new session...
31876-31940 CameraManager                       getCameraCharacteristics : cameraId = 1
31876-31940 CreateCaptureSession                Camera #1: Creating Capture Session #1... (Hardware Level: 0 | Outputs: [PHOTO (2560x1440 in JPEG), VIDEO (1920x1080 in YUV)])
31876-31940 CreateCaptureSession                Using legacy API (<28)
31876-31945 CreateCaptureSession                Camera #1: Successfully created CameraCaptureSession #1!
31876-31940 PersistentCameraCaptureSession      Stopping repeating request...
31876-31940 PersistentCameraCaptureSession      Configure() done! isActive: false, ID: 1, device: android.hardware.camera2.impl.CameraDeviceImpl@7fea12, session: android.hardware.camera2.impl.CameraCaptureSessionImpl@bb455e3
31876-31940 CameraSession                       configure { ... }: Completed CameraSession Configuration! (isActive: false, isRunning: false)
31876-31940 CameraView                          invokeOnInitialized()
31876-31886 zygote                              NativeAllocBackground concurrent copying GC freed 80868(3MB) AllocSpace objects, 1(20KB) LOS objects, 50% free, 8MB/16MB, paused 495us total 250.012ms
31876-31876 zygote                              Deoptimizing void com.facebook.react.uimanager.u.updateProperties(int, com.facebook.react.uimanager.o0) due to JIT same target
31876-31876 zygote                              Deoptimizing void com.facebook.react.uimanager.b1.d(com.facebook.react.bridge.ReadableArray, double[], float, float, com.facebook.react.bridge.ReadableArray) due to JIT inline cache
31876-31876 CameraView                          Updating CameraSession...
31876-31940 CameraSession                       configure { ... }: Waiting for lock...
31876-31940 CameraSession                       configure { ... }: Updating CameraSession Configuration... Difference(deviceChanged=false, outputsChanged=false, sidePropsChanged=false, isActiveChanged=true)
31876-31940 PersistentCameraCaptureSession      --> setIsActive(false)
31876-31940 PersistentCameraCaptureSession      Configure() with isActive: false, ID: 1, device: android.hardware.camera2.impl.CameraDeviceImpl@7fea12, session: android.hardware.camera2.impl.CameraCaptureSessionImpl@bb455e3
31876-31940 PersistentCameraCaptureSession      Stopping repeating request...
31876-31940 PersistentCameraCaptureSession      Configure() done! isActive: false, ID: 1, device: android.hardware.camera2.impl.CameraDeviceImpl@7fea12, session: android.hardware.camera2.impl.CameraCaptureSessionImpl@bb455e3
31876-31940 CameraSession                       configure { ... }: Completed CameraSession Configuration! (isActive: true, isRunning: false)
31876-31876 PreviewView                         PreviewView is 720x1280, rendering 720x1280 content. Resizing to: 720x1280 (COVER)
31876-31876 ViewRootImpl@1854c61[MainActivity]  Relayout returned: old=[0,0][720,1280] new=[0,0][720,1280] result=0x1 surface={valid=true<PHONE_NUMBER>} changed=false
31876-31876 SurfaceView                         BG show() Surface(name=Background for - SurfaceView - dev.rheconhece/dev.rheconhece.MainActivity@a665515@0) ib.p0{a665515 V.E...... ......ID 0,0-720,1280}
31876-31876 Surface                             sf_framedrop debug : 0x4f4c, game : false, logging : 0
31876-31876 SurfaceView                         surfaceCreated 1 #8 ib.p0{a665515 V.E...... ......ID 0,0-720,1280}
31876-31876 CameraSession                       PreviewView Surface created! Surface(name=null)/@0xebcd02a
31876-31876 CameraSession                       Setting Preview Output...
31876-31876 SurfaceView                         surfaceChanged (720,1280) 1 #8 ib.p0{a665515 V.E...... ......ID 0,0-720,1280}
31876-31876 CameraSession                       PreviewView Surface updated! Surface(name=null)/@0xebcd02a 720 x 1280
31876-31940 CameraSession                       configure { ... }: Waiting for lock...
31876-31940 CameraSession                       configure { ... }: Updating CameraSession Configuration... Difference(deviceChanged=false, outputsChanged=true, sidePropsChanged=true, isActiveChanged=true)
31876-31940 CameraSession                       Destroying previous outputs...
31876-31940 SurfaceOutput                       Closing 2560x1440 PHOTO ImageReader..
31876-31940 SurfaceOutput                       Closing 1920x1080 Video Pipeline..
31876-31940 CameraManager                       getCameraCharacteristics : cameraId = 1
31876-31940 CameraSession                       Creating outputs for Camera #1...
31876-31940 CameraSession                       Adding 2560x1440 Photo Output in JPEG...
31876-31940 Surface                             sf_framedrop debug : 0x4f4c, game : false, logging : 0
31876-31940 CameraSession                       Adding 1920x1080 Video Output in YUV_420_888...
31876-31940 VideoPipeline                       Initializing 1920 x 1080 Video Pipeline (format: YUV)
31876-31940 Surface                             sf_framedrop debug : 0x4f4c, game : false, logging : 0
31876-31940 VideoPipeline                       Using ImageReader round-trip (format: #35)
31876-31940 VideoPipeline                       Using legacy API for CPU ImageReader...
31876-31940 Surface                             sf_framedrop debug : 0x4f4c, game : false, logging : 0
31876-31940 Surface                             sf_framedrop debug : 0x4f4c, game : false, logging : 0
31876-31940 CameraSession                       Adding 1280x720 Preview Output...
31876-31876 zygote                              Deoptimizing int com.facebook.react.bridge.JavaOnlyArray.size() due to JIT inline cache
31876-31876 VisionCameraProxy                   Finding view 1329...
31876-31876 VisionCameraProxy                   Found view 1329!
31876-31876 ViewRootImpl@1854c61[MainActivity]  Relayout returned: old=[0,0][720,1280] new=[0,0][720,1280] result=0x1 surface={valid=true<PHONE_NUMBER>} changed=false
31876-31876 PreviewView                         Setting PreviewView Surface Size to 720x1280...
31876-31876 SurfaceHolder                       Resizing SurfaceHolder to 1280 x 720...
31876-31876 SurfaceView                         setPackageUsesOwnResolution() (Java SurfaceView) for dev.rheconhece: 1280x720 (true)
31876-31876 SurfaceView                         BG show() Surface(name=Background for - SurfaceView - dev.rheconhece/dev.rheconhece.MainActivity@a665515@0) ib.p0{a665515 V.E...... ......ID 0,0-720,1280}
31876-31876 SurfaceView                         surfaceChanged (1280,720) 2 #8 ib.p0{a665515 V.E...... ......ID 0,0-720,1280}
31876-31876 CameraSession                       PreviewView Surface updated! Surface(name=null)/@0xebcd02a 1280 x 720
31876-31876 SurfaceHolder                       Resized SurfaceHolder to 1280 x 720!
31876-31876 ViewRootImpl@1854c61[MainActivity]  Relayout returned: old=[0,0][720,1280] new=[0,0][720,1280] result=0x1 surface={valid=true<PHONE_NUMBER>} changed=false
31876-31940 PersistentCameraCaptureSession      --> setOutputs([PHOTO (2560x1440 in JPEG), VIDEO (1920x1080 in YUV), PREVIEW (1280 x 720)])
31876-31940 CameraSession                       Successfully configured Session with 3 outputs for Camera #1!
31876-31940 CameraSession                       Updating Video Outputs...
31876-31940 VideoPipeline                       Removing RecordingSession Output...
31876-31940 PersistentCameraCaptureSession      --> setRepeatingRequest(...)
31876-31940 PersistentCameraCaptureSession      --> setIsActive(true)
31876-31940 PersistentCameraCaptureSession      Configure() with isActive: true, ID: 1, device: android.hardware.camera2.impl.CameraDeviceImpl@7fea12, session: null
31876-31940 PersistentCameraCaptureSession      Creating new session...
31876-31940 CameraManager                       getCameraCharacteristics : cameraId = 1
31876-31940 CreateCaptureSession                Camera #1: Creating Capture Session #2... (Hardware Level: 0 | Outputs: [PHOTO (2560x1440 in JPEG), VIDEO (1920x1080 in YUV), PREVIEW (1280 x 720)])
31876-31940 CreateCaptureSession                Using legacy API (<28)
31876-31945 CreateCaptureSession                Camera #1: CameraCaptureSession #1 has been closed.
31876-31945 PersistentCameraCaptureSession      Session android.hardware.camera2.impl.CameraCaptureSessionImpl@bb455e3 closed!
31876-31945 CreateCaptureSession                Camera #1: Successfully created CameraCaptureSession #2!
31876-31940 PersistentCameraCaptureSession      Updating repeating request...
31876-31940 CameraManager                       getCameraCharacteristics : cameraId = 1
31876-31876 ViewRootImpl@1854c61[MainActivity]  Relayout returned: old=[0,0][720,1280] new=[0,0][720,1280] result=0x1 surface={valid=true<PHONE_NUMBER>} changed=false
31876-31940 PersistentCameraCaptureSession      Configure() done! isActive: true, ID: 1, device: android.hardware.camera2.impl.CameraDeviceImpl@7fea12, session: android.hardware.camera2.impl.CameraCaptureSessionImpl@39e00f7
31876-31940 CameraSession                       configure { ... }: Completed CameraSession Configuration! (isActive: true, isRunning: true)
31876-31940 CameraView                          invokeOnStarted()
31876-31886 zygote                              NativeAllocBackground concurrent copying GC freed 33532(1373KB) AllocSpace objects, 0(0B) LOS objects, 49% free, 7MB/14MB, paused 4.779ms total 255.337ms
31876-31945 VideoPipeline                       ImageReader::onImageAvailable!
31876-31886 zygote                              NativeAllocBackground concurrent copying GC freed 15236(603KB) AllocSpace objects, 0(0B) LOS objects, 49% free, 7MB/14MB, paused 7.749ms total 351.642ms
31876-31945 libc                                Fatal signal 11 (SIGSEGV), code 2, fault addr 0x74656d14 in tid 31945 (ionCamera.video)

On first app load (or if you clean app data and reopen it) there's a crash when trying to open camera view but after the crash if I reopen the app there's no crash but frame processors are not beeing called because none of my logs are printed, only 32675-32737 VideoPipeline                       ImageReader::onImageAvailable!.
Can you say something with these logs? Is there something I can try to fix this?

@mrousavy I did a lot of testing in my app and I discovered that if I replace runAsync with runAtTargetFps in my frame processor the app doesn't crash but there's a side effect that camera preview freezes when my face detector plugin is processing.
I also tryed increasing and decreasing target fps value but when frame is beeing processed camera preview freezes.

What does your Frame Processor look like?

Here is my plugin repo.
Crashing:
const handleDetectionWorklet = Worklets.createRunInJsFn( (
    result: DetectionResult
  ) => {
    console.log( 'detection result', result )
  })
  const frameProcessor = useFrameProcessor((frame) => {
    'worklet'
    runAsync(frame, () => {
      'worklet'
      detectFaces(
        frame,
        handleDetectionWorklet, {
          // detection settings
        }
      )
    })
  }, [handleDetectionWorklet])

Not crashing but freezing:
const handleDetectionWorklet = Worklets.createRunInJsFn( (
    result: DetectionResult
  ) => {
    console.log( 'detection result', result )
  })
  const frameProcessor = useFrameProcessor((frame) => {
    'worklet'
    runAtTargetFps(2, () => {
      'worklet'
      detectFaces(
        frame,
        handleDetectionWorklet, {
          // detection settings
        }
      )
    })
  }, [handleDetectionWorklet])

Does it work if you use an empty Frame Processor? Or none at all?

If you mean this code, yes it works:
const frameProcessor = useFrameProcessor((frame) => {
    'worklet'
    console.log('I'm running')
  }, [])

But if I add a runAsync (with processNestedWorklets in babel config) the app crash.
Without processNestedWorklets I got Regular javascript function cannot be shared. Try decorating the function with the 'worklet' keyword to allow the javascript function to be used as a worklet. error related here.
If I use runAtTargetFps it works doesn't matter if processNestedWorklets is present or not on babel config but with preview frozing issue.
Any suggestion?

runAsync and runAtTargetFps are two completely different things - runAsync schedules the function to run on a background Thread, with a maximum of one function at a time being able to run. runAtTargetFps runs on the same thread as the Frame Processor, but skips all Frames that come in more often than the target FPS rate.
So by design, runAtTargetFps still freezes the Camera if your code is slow. This is how it works, by design.
Can you use runAsync in the Example app here? For me that works.

@mrousavy sorry for the delay in reply, I've been running some tests and I think I found the problem in my app, I suppose it's something related to react-native-reanimated and/or react-native-svg...
I'm not sure yet what is really making it crash as I'm still doing some tests. I'll give you a feedback asap.

Ok, after a lot of tests I got a conclusion:
I have coppied whole example CameraPage.tsx code and remove everything I don't need, I left only most basic things. Here is my current code.
The problem is: If I try to use react-native-reanimated there's no crash but runAsync method is NOT called. Also here's my whole package.json
{
  "name": "myApp",
  "version": "1",
  "private": true,
  "scripts": {
    "lint": "yarn test && eslint --quiet --fix --ext .js,.ts,.tsx,.jsx .",
    "test": "tsc",
    "prebuild": "npx expo prebuild",
    "prebuild:clean": "npx expo prebuild --clean",
    "android": "yarn prebuild && npx expo run:android -d",
    "android:prod": "yarn prebuild &&  npx expo run:android -d --variant release",
    "ios": "yarn prebuild && npx expo run:ios -d",
    "ios:prod": "yarn prebuild && npx expo run:ios -d --configuration Release",
    "android:clean": "yarn prebuild:clean && npx expo run:android -d --no-build-cache",
    "ios:clean": "yarn prebuild:clean && npx expo run:ios -d --no-build-cache",
    "start": "expo start --dev-client"
  },
  "main": "index.js",
  "dependencies": {
    "@react-native-community/hooks": "^3.0.0",
    "@react-navigation/native": "^6.1.9",
    "expo": "~50.0.6",
    "expo-application": "~5.8.3",
    "expo-build-properties": "~0.11.1",
    "expo-constants": "~15.4.5",
    "expo-dev-client": "~3.3.8",
    "react": "18.2.0",
    "react-native": "0.73.4",
    "react-native-gesture-handler": "~2.14.1",
    "react-native-hole-view": "^3.0.0-alpha4",
    "react-native-reanimated": "~3.7.0",
    "react-native-safe-area-context": "4.8.2",
    "react-native-svg": "^14.1.0",
    "react-native-vector-icons": "^10.0.3",
    "react-native-vision-camera": "3.9.0-beta.5",
    "react-native-vision-camera-face-detector": "^1.2.2",
    "react-native-worklets-core": "^0.3.0"
  },
  "devDependencies": {
    "@babel/core": "^7.23.9",
    "@types/react": "~18.2.48",
    "@typescript-eslint/eslint-plugin": "^6.19.1",
    "@typescript-eslint/parser": "^6.19.1",
    "babel-plugin-module-resolver": "^5.0.0",
    "eslint": "^8.56.0",
    "eslint-config-google": "^0.14.0",
    "eslint-config-next": "^14.1.0",
    "eslint-plugin-import": "^2.29.1",
    "eslint-plugin-react": "^7.33.2",
    "typescript": "^5.3.3"
  },
  "resolutions": {
    "@expo/config-plugins": "^7.8.0"
  }
}

No matter what I do in the code, If I run my app using yarn android:prod the app don't crash but frame processor is not called.
About the crashes.... the problem is react-native-svg. If I try to use any Svg with vision-camera the app crash. I tryed:

create a aniamted svg:

import Svg from 'react-native-svg'
const AnimatedSvg = Animated.createAnimatedComponent( Svg )

returning only a normal svg:

return (
  <Camera
    ....
  />
  <Svg>
    ...
  </Svg>
)

My SVG is rendered in front of camera preview because I'm creating a hole view (indication where user face must be).
@mrousavy do you have any thoughts on this?


scatter, but at the same time, tooltip.

I need to view the actual point value when i click on the label.
please is there any solution.

@bilal9876 Do you still need help? If yes, could you explain a bit more what you mean? Do you mean that you want a tooltip to open when clicking on the label of an axis?

@bilal9876 Do you still need help? If yes, could you explain a bit more what you mean? Do you mean that you want a tooltip to open when clicking on the label of an axis?

Hi. '
Yes, I Solved the previous issue.
But Unfortunately, a new problem arises. How can I use a logarithmic chart in react native. Moreover, the variation should be in X and Y. So, I have a multi dimensional array.


Prevent browsers autocomplete suggestions.

Using react-datepicker i noticed that the browser still show autocomplete suggestions based on previous values used on the field. This suggestion is a dropdown and overlaps the calendar.

autoComplete="off"