🐛 frame-processor/unavailable: Frame Processors are not enabled

What were you trying to do?
Using this + the QR scanner library for QR detection.
Reproduceable Code
import { observer } from 'mobx-react-lite'

import * as React from 'react'
import 'react-native-reanimated'
import { StyleSheet, View } from 'react-native'
import { useCameraDevices, Camera } from 'react-native-vision-camera'
import { useScanBarcodes, BarcodeFormat } from 'vision-camera-qrcode-scanner'
import { Center, Flex, Heading, Text } from 'native-base'
import { useIsFocused } from '@react-navigation/core'
import Layout from '../../components/layouts/Layout'

export const ScanScreen: React.FC = observer(({ navigation }) => {
  const [hasPermission, setHasPermission] = React.useState(false)
  const devices = useCameraDevices()
  const device = devices.back
  const isFocused = useIsFocused()
  const [frameProcessor, qrCodes] = useScanBarcodes([BarcodeFormat.ALL_FORMATS])
  const [isActive, setIsActive] = React.useState(isFocused)

  React.useEffect(() => {
    ; (async () => {
      const status = await Camera.requestCameraPermission()
      setHasPermission(status === 'authorized')
    })()
  }, [])

  React.useEffect(() => {
    if (qrCodes.length) {
      console.log(qrCodes[0])
      navigation.navigate('details', { id: qrCodes[0].displayValue })
    }
  }, [qrCodes.length])

  return (
    <Layout noScroll noPadding>
      <View style={styles.overlayContent}>
        <Center pb={16}>
          {qrCodes.map((qrCode, idx) => (
            <Text key={idx} style={styles.qrCodeTextURL}>
              {qrCode.displayValue}
            </Text>
          ))}
        </Center>
      </View>
      {device != null && hasPermission && (
        <Camera
          style={StyleSheet.absoluteFill}
          device={device}
          isActive={isFocused}
          frameProcessor={isFocused ? frameProcessor : undefined}
          frameProcessorFps={1}
        />
      )}
    </Layout>
  )
})

What happened instead?
frame-processor/unavailable: Frame Processors are not enabled.
The app works perfectly after a completely clean start - and after code changes (or bundle refresh) I can't use the frameProcessors function at all.
I'm just guessing here - I disabled the assertFrameProcessorsEnabled call in node_modules/react-native-vision-camera/src/Camera.tsx and I get the error:
Invariant Violation: Tried to register two views with the same name CameraView, js engine: hermes

So, I can only guess (a proper guess) that this library perhaps is not tearing down views correctly, so next run they are not initialised correctly?
I've managed to find a temporary fix (it stopped working after a while) by making the following change:
-     {device != null && hasPermission && (
+     {device != null && hasPermission && isFocused && (

Relevant log output
No response
Device
OnePlus 7 Pro (Android 12)
VisionCamera Version
2.9.4
Additional information

[ ] I am using Expo
[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.

Interesting, does this work on iOS?

My colleagues on iOS tell me they haven't experienced the issue, but ill update this thread if they do today.

@mrousavy this also happens with me
after navigating to screen app crashes with this error, after restarting the app it works fine

Are you sure that you're not using some remote debugger such as Chrome? It makes me wonder that the JSI functions are missing. Or maybe you are using fast-refresh and that breaks?
Can you reproduce the error if you simply open the app on your phone, without any debugger attached, and navigate through screens without fast-refresh or hot-reload?

Not using Chrome debugger - doesn't work with  so I've been using flipper when required, but this occurs if flipper is disconnected or not.
Disabling fast refresh did not fix the issue if it already occurs.
Tried this too:

From a fresh app (react-native run-android) on device
Disabling fast refresh (no option for hot-reload)
Clean bundle yarn install && yarn start --reset-cache
Navigate to page with camera, allow permission
Works fine
Navigate away from page
Error Exception in HostFunction: com.mrousavy.camera.ViewNotFoundError: [system/view-not-found] The given view (ID 2559) was not found in the view manager.
Reload app via metro bundler
Navigate back to camera screen -> frame processors are not enabled

Hope this helps somewhat!

Ah, this is a race condition in the C++ view finder part. (findViewById, called on JS Thread through JNI, so C++ -> JS -> C++)
I have tried several times to fix this issue, but all of those times turned into long nights of debugging and after the morning light started to shine through my window I didn't want to spend more time on it. If you are interested in posting a bug bounty on the issue, let me know and me and my guys in my agency can look at this issue in greater detail to fix it once and for all.

No worries. If you don't mind linking any relevant code, I will see if I can't obtain time myself to see what I can do.
Appreciate it all the same!

by when this PR will be merged?

Please see if #691 fixes the issue for you guys 🙏

@mrousavy almost!
I no longer experience the original issue on reload, however navigating away from the screen that uses frame processors gives me
com.mrousavy.camera.ViewNotfoundError: [system/view-not-found] The given view (ID 12429) was not found in the view manager
I tried nuking node_modules & gradlew clean and no change.

Hm, okay that's a separate concurrency issue. will take a look soon

+1

I'm getting this error as well

in my system node version is 12.  just installing the package and did changes in android manifest and other files given in docs.
VisionCamera: Frame Processors are disabled because REA v2 does not exist. C++ part will not be built.

> Task :app:checkDebugAarMetadata FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.9/userguide/command_line_interface.html#sec:command_line_warnings
9 actionable tasks: 2 executed, 7 up-to-date

FAILURE: Build failed with an exception.

that's all, one will get this error.

@vikasacharya16 the output you shared is not an error.
Please read up on what errors are and how to identify them, this is a simple log output. The actual error is further up.

@jack828 Hey! Does v2.13.1 fix the issue for you?

I re-built and re-ran the app while also restarting metro with --reset-cache and that seemed to fix my issue. I also ran npm update but it didn't appear to update much in package.json, just some deps of deps.

I'm getting this same error running in debub on Android emulator...

"react-native-vision-camera": "2.15.2",
"react-native-reanimated": "2.13.0",
"vision-camera-code-scanner": "0.2.0",
"react-native": "0.68.2",
"react": "17.0.2",

`import React, { useEffect, useState } from 'react'
import { View, Alert, StyleSheet } from 'react-native'
import styles from './styles'
import { Camera, useCameraDevices, useFrameProcessor } from 'react-native-vision-camera'
import { BarcodeFormat, scanBarcodes, Barcode } from 'vision-camera-code-scanner'
import { runOnJS } from 'react-native-reanimated'
const QRReader: React.FC = () => {
const [loading, setLoading] = useState(false)
const devices = useCameraDevices()
const device = devices.back
const [hasPermission, setHasPermission] = useState(false)
const [barcodes, setBarcodes] = useState<Barcode[]>()
const frameProcessor = useFrameProcessor((frame) => {
'worklet'
const detectedBarcodes = scanBarcodes(frame, [BarcodeFormat.QR_CODE], { checkInverted: true })
runOnJS(setBarcodes)(detectedBarcodes)

}, [])
useEffect(() => {
;(async () => {
const status = await Camera.requestCameraPermission()
setHasPermission(status === 'authorized')
})()
}, [])
useEffect(() => {
if (barcodes && barcodes.length) {
console.log('barcodes', barcodes);
}
}, [barcodes])
return (

{device != null && hasPermission && (
<>

</>
)}

)
}
export default QRReader
`

I'm getting this same error running in debug on Android emulator...

"react-native-vision-camera": "2.15.2",
"react-native-reanimated": "2.13.0",
"vision-camera-code-scanner": "0.2.0",
"react-native": "0.68.2",
"react": "17.0.2",

import 'react-native-reanimated'
import React, { useEffect, useState } from 'react'
import { View, Alert, StyleSheet } from 'react-native'

import styles from './styles'

import { Camera, useCameraDevices, useFrameProcessor } from 'react-native-vision-camera'
import { BarcodeFormat, scanBarcodes, Barcode } from 'vision-camera-code-scanner'
import { runOnJS } from 'react-native-reanimated'

const QRReader: React.FC = () => {
  const [loading, setLoading] = useState<boolean>(false)
  const devices = useCameraDevices()
  const device = devices.back
  const [hasPermission, setHasPermission] = useState<boolean>(false)
  const [barcodes, setBarcodes] = useState<Barcode[]>()

  const frameProcessor = useFrameProcessor((frame) => {
    'worklet'

    const detectedBarcodes = scanBarcodes(frame, [BarcodeFormat.QR_CODE], { checkInverted: true })
    runOnJS(setBarcodes)(detectedBarcodes)
  }, [])

  useEffect(() => {
    ;(async () => {
      const status = await Camera.requestCameraPermission()
      setHasPermission(status === 'authorized')
    })()
  }, [])

  useEffect(() => {
    if (barcodes && barcodes.length) {
      console.log('barcodes', barcodes);
    }
  }, [barcodes])

  return (
    <View style={styles.container}>
      {device != null && hasPermission && (
        <>
          <Camera
            style={StyleSheet.absoluteFill}
            isActive={true}
            device={device}
            frameProcessor={frameProcessor}
            frameProcessorFps={1}
          />
        </>
      )}
    </View>
  )
}

export default QRReader

After upgrade to "react-native": "0.70.6", the problem is still happening...
I can't get away from this "frame-processor/unavailable: Frame Processors are not enabled" error.
While building, it seems to log that "frame processors are enabled!"

So I'm not sure why it is throwing this error. I cannot use the "frameProcessor" prop on Camera.

Finally I was able to resolve this by upgrading my emulator SDK version to 31.

Hey @emaxedon  I am facing same issue on the development build on my device (One Plus 9r).
Surprisingly its working on my emulator .
How do i solve this problem?
PS - I am relatively new to react-native

Hey @emaxedon I am facing same issue on the development build on my device (One Plus 9r). Surprisingly its working on my emulator . How do i solve this problem? PS - I am relatively new to react-native
My camerascreen code - `import { Button, StyleSheet, Text, View ,TouchableOpacity} from "react-native"; import { StatusBar } from "expo-status-bar"; import * as MediaLibrary from "expo-media-library"; import * as Permissions from "expo-permissions"; import { useRef, useState, useEffect } from "react"; import styles from "../styles"; import { Ionicons } from "@expo/vector-icons"; import { useIsFocused } from "@react-navigation/native"; import {useCameraDevices,Camera,CameraPermissionStatus,frameRateIncluded,useFrameProcessor} from 'react-native-vision-camera'; import { examplePlugin } from './frame-Processors/ExamplePlugin'; import {useFrameCallback} from 'react-native-reanimated';
export default function CameraScreen({ navigation }) { const [cameraDevice, setCameraDevice] = useState('back'); const [recording, setRecording] = useState(false); const [flash, setFlash] = useState('off'); const [cameraPermission, setCameraPermission] = useState(); const [microphonePermission, setMicrophonePermission] = useState()
const cameraRef = useRef(Camera) const isFocused = useIsFocused(); const devices = useCameraDevices();
var device = devices[cameraDevice];
const frameProcessor = useFrameProcessor((frame) => { 'worklet'; const values = examplePlugin(frame); console.log(Return Values: ${JSON.stringify(values)}); }, []);
useEffect(() => { Camera.getCameraPermissionStatus().then(setCameraPermission); Camera.getMicrophonePermissionStatus().then(setMicrophonePermission); if (cameraPermission!='authorized'){ Camera.requestCameraPermission().then(setCameraPermission); } if (microphonePermission!='authorized'){ Camera.requestMicrophonePermission().then(setMicrophonePermission); } }, [setCameraPermission,setMicrophonePermission]);
console.log(Re-rendering Navigator. Camera: ${cameraPermission} | Microphone: ${microphonePermission});
if (!device) { return null; }
async function toggleCameraType(){ await setCameraDevice(cameraDevice => (cameraDevice=='back'?'front':'back')) device = devices[cameraDevice]; }
function startRecording(){ try { if (cameraRef.current == null) throw new Error('Camera ref is null!');
  console.log('calling startRecording()...');
  cameraRef.current.startRecording({
    flash: flash,
    onRecordingError: (error) => {
      console.error('Recording failed!', error);
      stopRecording();
    },
    onRecordingFinished: (video) => {
      console.log(`Recording successfully finished! ${video.path}`);
      navigation.navigate('ReelPreview',{videoURI:video.path});
      stopRecording();
    },
  });
  // TODO: wait until startRecording returns to actually find out if the recording has successfully started
  console.log('called startRecording()!');
  setRecording(true);
} catch (e) {
  console.error('failed to start recording!', e);
}
// alert('Starting Recording')
// console.log("Lets Record")
// cameraRef.current?.startRecording({
//   flash: 'on',
//   onRecoringFinished: (video) => {alert(video);console.log(video)},
//   onRecordingError: (error) => {alert(error);console.log(error)}
// })

} async function stopRecording (){ console.log('Recording Stopped!') await cameraRef.current?.stopRecording() } function manageFlash(){ if(!device.hasFlash){ alert('Camera does not has flash'); } console.log(flash) setFlash(flash => (flash==='on'?flash='off':flash='on')) }
return ( {/* {isFocused && hasPermission && ( */} <Camera ref = {cameraRef} photo={true} isActive={isFocused} device={device} whiteBalance="auto" type="back" style={StyleSheet.absoluteFill} video ={true} audio ={true} enableZoomGesture={true} frameProcessor={device.supportsParallelVideoProcessing ? frameProcessor : undefined} frameProcessorFps={60}
    />
    <View style={{ flex: 9 }} />
      <View
        style={{
          flex: 1,
          justifyContent: "space-around",
          alignItems: "center",
          backgroundColor: "#1c1c1c",
          flexDirection: 'row'
        }}
        >
        <Ionicons
          name={recording ? "stop-circle" : "play-circle"}
          size={60}
          color={recording ? "red" : "white"}
          onPress={async () => {
            console.log("btn clicked");
            if (!recording) {
              startRecording();
              setRecording(true);
            } else {
              setRecording(false);
              stopRecording();
            }
          }}
        />
        <Ionicons
          name={"camera-reverse"}
          size={60}
          color ={"white"}
          onPress={toggleCameraType}
        />
        <Ionicons
          name={"flash"}
          size={50}
          color ={(device.hasFlash && flash == 'on')?"yellow":"white"}
          onPress={manageFlash}
        />
      </View>

  {/* )} */}
</View>

); } `
Example plugin -
`/* global __example_plugin __example_plugin_swift */ import type { Frame } from 'react-native-vision-camera';
declare let _WORKLET: true | undefined;
export function examplePluginSwift(frame: Frame): string[] { 'worklet'; if (!_WORKLET) throw new Error('examplePluginSwift must be called from a frame processor!');
// @ts-expect-error because this function is dynamically injected by VisionCamera return __example_plugin_swift(frame, 'hello!', 'parameter2', true, 42, { test: 0, second: 'test' }, ['another test', 5]); }
export function examplePlugin(frame: Frame): string[] { 'worklet'; if (!_WORKLET) throw new Error('examplePlugin must be called from a frame processor!');
// @ts-expect-error because this function is dynamically injected by VisionCamera return __example_plugin(frame, 'hello!', 'parameter2', true, 42, { test: 0, second: 'test' }, ['another test', 5]); }`
Bable.config.json -
module.exports = function(api) { api.cache(true); return { presets: ['babel-preset-expo'], plugins: [ [ 'react-native-reanimated/plugin', { globals: ['__example_plugin', '__example_plugin_swift'], }, ] ] }; };
Error that i get on console is
ERROR frame-processor/unavailable: Frame Processors are not enabled. See https://mrousavy.github.io/react-native-vision-camera/docs/guides/troubleshooting ERROR Your app just crashed. See the error below. java.lang.UnsatisfiedLinkError: No implementation found for void com.mrousavy.camera.CameraView.frameProcessorCallback(androidx.camera.core.ImageProxy) (tried Java_com_mrousavy_camera_CameraView_frameProcessorCallback and Java_com_mrousavy_camera_CameraView_frameProcessorCallback__Landroidx_camera_core_ImageProxy_2) com.mrousavy.camera.CameraView.frameProcessorCallback(Native Method) com.mrousavy.camera.CameraView.configureSession$lambda-7$lambda-6(CameraView.kt:491) com.mrousavy.camera.CameraView.$r8$lambda$cqtIchEZdTZaV3R0UUrDpVbB1Es(Unknown Source:0) com.mrousavy.camera.CameraView$$ExternalSyntheticLambda1.analyze(Unknown Source:2) androidx.camera.core.ImageAnalysis.lambda$setAnalyzer$2(ImageAnalysis.java:463) androidx.camera.core.ImageAnalysis$$ExternalSyntheticLambda0.analyze(Unknown Source:2) androidx.camera.core.ImageAnalysisAbstractAnalyzer.lambda$analyzeImage$0$androidx-camera-core-ImageAnalysisAbstractAnalyzer(ImageAnalysisAbstractAnalyzer.java:283) androidx.camera.core.ImageAnalysisAbstractAnalyzer$$ExternalSyntheticLambda1.run(Unknown Source:14) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) java.lang.Thread.run(Thread.java:923)

Hey, @Ankushpandey-ti - you need to ensure that your device is running Google Android API 31 or greater (Android 12 or greater).

Hey ,
@emaxedon  , i tried the development build of my app on android 13, still getting same error.
Anyidea why is it so?

@Ankushpandey-ti In this case, it is unlikely that it is tied to the android SDK version. I see in your error logs that "Frame processors are not enabled". This will definitely cause issues.
I also notice you are not directly importing the entire "react-native-reanimated" module...
import {useFrameCallback} from 'react-native-reanimated';

should be
import 'react-native-reanimated';
import {useFrameCallback} from 'react-native-reanimated';

Hey ,@emaxedon
I did a rebuild for android with no changes now the error is gone but the development app keeps crashing on starting the camera without any log or error.
It some times gives a pop up the APP keeps stopping.
One more thing that i noticed is if i keep the isActive = {false} , then the app doesn't closes.
It closes after  i turn the isActive ={true}
Also its working fine on emulator as it was earlier.

Any solution for this? @mrousavy

Any solution for this? @mrousavy

@DeepikaSharma5  The solution that worked for me was.

I updated my android device to Andorid 13 as suggested by @emaxedon  in above comments.
Insted of directly using true false for the isActive tag is used isFocuses.

Here is the sample code for better understanding
Not working code :-
<Container>         {isFocused && <Camera           ref={cameraRef}           photo={true}           isActive={true}           device={device}           style={StyleSheet.absoluteFill}           video={true}           audio={true}           enableZoomGesture={true}         />}       </Container>
Working Code part :-
const isFocused = useIsFocused();      <Container>         {isFocused && <Camera           ref={cameraRef}           photo={true}           isActive={isFocused}           device={device}           style={StyleSheet.absoluteFill}           video={true}           audio={true}           enableZoomGesture={true}         />}       </Container>

In my case what solved this was add the Processor plugin class package to the MainApplication.java file in getPackages method.
Like:
@Override
    protected List<ReactPackage> getPackages() {
      return Arrays.<ReactPackage>asList(
         ...
         new VisionCameraFaceDetectorPluginPackage() // -> Frame processor
      );
    }

I got the same issue but on IOS. And i follow all the steps on https://mrousavy.com/react-native-vision-camera/docs/guides/troubleshooting/
do someone has some some idea ?
in my Podfile i have
platform :ios, '13'
and ...
if pod.name.eql?('vision-camera-code-scanner') || pod.name.eql?('VisionCamera')
def pod.build_type;
Pod::BuildType.static_library
end
end

Just close debugger mode on android

¿Estás seguro de que no estás usando algún depurador remoto como Chrome? Me pregunto si faltan las funciones JSI. ¿O tal vez estás usando una actualización rápida y eso se rompe?
¿Puede reproducir el error si simplemente abre la aplicación en su teléfono, sin ningún depurador adjunto, y navega por las pantallas sin una actualización rápida o una recarga en caliente?

I stopped debugging by chrome and instantly the error went away so it worked for me

I have finally solve this issue.
For today the latest version of  react-native-reanimated is "3.0.2", this is not compatible with latest version of react-native-camera.
Using version "react-native-reanimated": "^2.10.0" solved the issue for me after deleting yarn.lock file and then yarn install again.

I have finally solve this issue. For today the latest version of react-native-reanimated is "3.0.2", this is not compatible with latest version of react-native-camera. Using version "react-native-reanimated": "^2.10.0" solved the issue for me after deleting yarn.lock file and then yarn install again.

Solved the issue for me too!
I installed the 2.14.4 version.
The site says: "If you want to use Frame Processors, you need to install react-native-reanimated 2.2.0 or higher."
3.0.2 is higher than 2.2.0 but not works, maybe you can fix this info on the site?

Tôi cuối cùng đã giải quyết vấn đề này. Hiện tại, phiên bản mới nhất của react-native-reanimated là "3.0.2", phiên bản này không tương thích với phiên bản mới nhất của react-native-camera. Việc sử dụng phiên bản "react-native-reanimated": "^2.10.0"đã giải quyết vấn đề cho tôi sau khi xóa tệp yarn.lock rồi yarn installxóa lại.

my version is ^2.9.0. when update to 2.10.0 it work fine

I have finally solve this issue. For today the latest version of react-native-reanimated is "3.0.2", this is not compatible with latest version of react-native-camera. Using version "react-native-reanimated": "^2.10.0" solved the issue for me after deleting yarn.lock file and then yarn install again.

thank you, its work for me

If anyone is facing this issue, it is most likely because you are using a package like Firebase that requires   use_frameworks! :linkage => :static. You need specify the build types for RNReanimated and Vision camera. Add the block below to your pod file and it should work.
pre_install do |installer|
installer.pod_targets.each do |pod|
if pod.name.eql?('RNReanimated') || pod.name.eql?('VisionCamera')
def pod.build_type
Pod::BuildType.static_library
end
end
end
end

If anyone is facing this issue, it is most likely because you are using a package like Firebase that requires use_frameworks! :linkage => :static. You need specify the build types for RNReanimated and Vision camera. Add the block below to your pod file and it should work.
pre_install do |installer|
installer.pod_targets.each do |pod|
if pod.name.eql?('RNReanimated') || pod.name.eql?('VisionCamera')
def pod.build_type
Pod::BuildType.static_library
end
end
end
end

It worked for me, and I didn't need to update reanimated, just add this line in the Podfile

Hi. I had this issue when running my app on Android device:
 LOG  Running "viewfinder" with {"rootTag":11}
 ERROR  system/frame-processors-unavailable: Frame Processors are not enabled!, js engine: hermes

I've installed react-native-worklets-core as it is suggested in the docs (https://www.react-native-vision-camera.com/docs/guides/frame-processors), and I was no longer getting the error mentioned above.
However, my app started to crash / close when launching the camera.
There was no error output, just this:
 LOG  Running "viewfinder" with {"rootTag":11}
 LOG  Loading react-native-worklets-core...
 LOG  Worklets loaded successfully

Module versions:
    "react-native": "0.72.4",
    "react-native-vision-camera": "^3.0.0",
    "react-native-worklets-core": "^0.2.0"

I've deleted node_modules and package-lock.json and did a clean re-install of the modules.
After that the app could no longer be launched or built, I was getting the following output:
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-vision-camera:buildCMakeDebug[arm64-v8a]'.
> com.android.ide.common.process.ProcessException: ninja: Entering directory `/Users/peter/Projects/viewfinder/node_modules/react-native-vision-camera/android/.cxx/Debug/4a1m2e2g/arm64-v8a'
  [1/1] Linking CXX shared library ../../../../build/intermediates/cxx/Debug/4a1m2e2g/obj/arm64-v8a/libVisionCamera.so
  FAILED: ../../../../build/intermediates/cxx/Debug/4a1m2e2g/obj/arm64-v8a/libVisionCamera.so
  : && /Users/peter/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ --target=aarch64-none-linux-android21 --sysroot=/Users/peter/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/sysroot -fPIC -O2 -frtti -fexceptions -Wall -Wno-unused-variable -fstack-protector-all -g  -fno-limit-debug-info  -Wl,--build-id=sha1 -Wl,--no-rosegment -Wl,--fatal-warnings -Qunused-arguments -Wl,--no-undefined -shared -Wl,-soname,libVisionCamera.so -o ../../../../build/intermediates/cxx/Debug/4a1m2e2g/obj/arm64-v8a/libVisionCamera.so CMakeFiles/VisionCamera.dir/Users/peter/Projects/viewfinder/node_modules/react-native-vision-camera/cpp/JSITypedArray.cpp.o CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCamera.cpp.o CMakeFiles/VisionCamera.dir/src/main/cpp/VideoPipeline.cpp.o CMakeFiles/VisionCamera.dir/src/main/cpp/PassThroughShader.cpp.o CMakeFiles/VisionCamera.dir/src/main/cpp/OpenGLContext.cpp.o CMakeFiles/VisionCamera.dir/src/main/cpp/OpenGLRenderer.cpp.o CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/FrameHostObject.cpp.o CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/FrameProcessorPluginHostObject.cpp.o CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/JSIJNIConversion.cpp.o CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/VisionCameraProxy.cpp.o CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrame.cpp.o CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp.o CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrameProcessorPlugin.cpp.o CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraScheduler.cpp.o  /Users/peter/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/lib/aarch64-linux-android/21/liblog.so  -landroid  /Users/peter/.gradle/caches/transforms-3/6fe00d6361b0f0c55549aec89a7f6742/transformed/jetified-react-android-0.72.4-debug/prefab/modules/jsi/libs/android.arm64-v8a/libjsi.so  /Users/peter/.gradle/caches/transforms-3/6fe00d6361b0f0c55549aec89a7f6742/transformed/jetified-react-android-0.72.4-debug/prefab/modules/reactnativejni/libs/android.arm64-v8a/libreactnativejni.so  /Users/peter/.gradle/caches/transforms-3/34c2120d0d3cd8dc97826fc02c9e8fc4/transformed/jetified-fbjni-0.3.0/prefab/modules/fbjni/libs/android.arm64-v8a/libfbjni.so  -lGLESv2  -lEGL   -latomic -lm && :
  ld: error: undefined symbol: RNWorklet::JsiWorkletContext::getWorkletRuntime()
  >>> referenced by JFrameProcessor.cpp:37 (/Users/peter/Projects/viewfinder/node_modules/react-native-vision-camera/android/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp:37)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp.o:(vision::JFrameProcessor::callWithFrameHostObject(std::__ndk1::shared_ptr<vision::FrameHostObject> const&) const)
  >>> referenced by JVisionCameraProxy.cpp:57 (/Users/peter/Projects/viewfinder/node_modules/react-native-vision-camera/android/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp:57)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o:(vision::JVisionCameraProxy::~JVisionCameraProxy())

  ld: error: undefined symbol: RNWorklet::JsiWorkletContext::invokeOnJsThread(std::__ndk1::function<void (facebook::jsi::Runtime&)>&&)
  >>> referenced by JFrameProcessor.cpp:50 (/Users/peter/Projects/viewfinder/node_modules/react-native-vision-camera/android/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp:50)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp.o:(vision::JFrameProcessor::callWithFrameHostObject(std::__ndk1::shared_ptr<vision::FrameHostObject> const&) const)
  >>> referenced by WKTJsiWorklet.h:358 (/Users/peter/Projects/viewfinder/node_modules/react-native-worklets-core/android/build/headers/rnworklets/react-native-worklets-core/WKTJsiWorklet.h:358)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp.o:(RNWorklet::WorkletInvoker::~WorkletInvoker())

  ld: error: undefined symbol: RNWorklet::JsiWorkletContext::runtimeMappings
  >>> referenced by __tree:0 (/Users/peter/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/__tree:0)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp.o:(RNWorklet::WorkletInvoker::call(facebook::jsi::Runtime&, facebook::jsi::Value const&, facebook::jsi::Value const*, unsigned long))
  >>> referenced by __tree:0 (/Users/peter/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/__tree:0)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp.o:(RNWorklet::WorkletInvoker::call(facebook::jsi::Runtime&, facebook::jsi::Value const&, facebook::jsi::Value const*, unsigned long))

  ld: error: undefined symbol: RNWorklet::JsiWorkletContext::invokeOnWorkletThread(std::__ndk1::function<void (RNWorklet::JsiWorkletContext*, facebook::jsi::Runtime&)>&&)
  >>> referenced by WKTJsiWorklet.h:361 (/Users/peter/Projects/viewfinder/node_modules/react-native-worklets-core/android/build/headers/rnworklets/react-native-worklets-core/WKTJsiWorklet.h:361)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp.o:(RNWorklet::WorkletInvoker::~WorkletInvoker())

  ld: error: undefined symbol: RNWorklet::JsiWorkletContext::defaultInstance
  >>> referenced by memory:3887 (/Users/peter/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/memory:3887)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp.o:(RNWorklet::JsiWorkletContext::getDefaultInstance())
  >>> referenced by memory:3887 (/Users/peter/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/memory:3887)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp.o:(RNWorklet::JsiWorkletContext::getDefaultInstance())

  ld: error: undefined symbol: RNWorklet::JsiHostObject::JsiHostObject()
  >>> referenced by WKTJsiWorkletContext.h:31 (/Users/peter/Projects/viewfinder/node_modules/react-native-worklets-core/android/build/headers/rnworklets/react-native-worklets-core/WKTJsiWorkletContext.h:31)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp.o:(RNWorklet::JsiWorkletContext::getDefaultInstance())
  >>> referenced by WKTJsiWorklet.h:77 (/Users/peter/Projects/viewfinder/node_modules/react-native-worklets-core/android/build/headers/rnworklets/react-native-worklets-core/WKTJsiWorklet.h:77)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o:(RNWorklet::JsiWorklet::JsiWorklet(facebook::jsi::Runtime&, facebook::jsi::Value const&))

  ld: error: undefined symbol: vtable for RNWorklet::JsiWorkletContext
  >>> referenced by WKTJsiWorkletContext.h:31 (/Users/peter/Projects/viewfinder/node_modules/react-native-worklets-core/android/build/headers/rnworklets/react-native-worklets-core/WKTJsiWorkletContext.h:31)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp.o:(RNWorklet::JsiWorkletContext::getDefaultInstance())
  >>> referenced by WKTJsiWorkletContext.h:31 (/Users/peter/Projects/viewfinder/node_modules/react-native-worklets-core/android/build/headers/rnworklets/react-native-worklets-core/WKTJsiWorkletContext.h:31)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp.o:(RNWorklet::JsiWorkletContext::getDefaultInstance())
  >>> the vtable symbol may be undefined because the class is missing its key function (see https://lld.llvm.org/missingkeyfunction)

  ld: error: undefined symbol: RNWorklet::JsiWorkletContext::~JsiWorkletContext()
  >>> referenced by memory:2252 (/Users/peter/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/memory:2252)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp.o:(std::__ndk1::__shared_ptr_emplace<RNWorklet::JsiWorkletContext, std::__ndk1::allocator<RNWorklet::JsiWorkletContext> >::~__shared_ptr_emplace())
  >>> referenced by memory:2252 (/Users/peter/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/memory:2252)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp.o:(std::__ndk1::__shared_ptr_emplace<RNWorklet::JsiWorkletContext, std::__ndk1::allocator<RNWorklet::JsiWorkletContext> >::~__shared_ptr_emplace())

  ld: error: undefined symbol: RNWorklet::JsiWorkletContext::JsiWorkletContext(std::__ndk1::basic_string<char, std::__ndk1::char_traits<char>, std::__ndk1::allocator<char> > const&, facebook::jsi::Runtime*, std::__ndk1::function<void (std::__ndk1::function<void ()>&&)>, std::__ndk1::function<void (std::__ndk1::function<void ()>&&)>)
  >>> referenced by memory:2278 (/Users/peter/Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/memory:2278)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o:(vision::JVisionCameraProxy::JVisionCameraProxy(facebook::jni::alias_ref<facebook::jni::detail::JTypeFor<facebook::jni::HybridClass<vision::JVisionCameraProxy, facebook::jni::detail::BaseHybridClass>::JavaPart, facebook::jni::JObject, void>::_javaobject*> const&, facebook::jsi::Runtime*, std::__ndk1::shared_ptr<facebook::react::CallInvoker> const&, facebook::jni::basic_strong_ref<facebook::jni::detail::JTypeFor<facebook::jni::HybridClass<vision::JVisionCameraScheduler, facebook::jni::detail::BaseHybridClass>::JavaPart, facebook::jni::JObject, void>::_javaobject*, facebook::jni::GlobalReferenceAllocator> const&))

  ld: error: undefined symbol: RNWorklet::JsiHostObject::~JsiHostObject()
  >>> referenced by WKTJsiWorklet.h:79 (/Users/peter/Projects/viewfinder/node_modules/react-native-worklets-core/android/build/headers/rnworklets/react-native-worklets-core/WKTJsiWorklet.h:79)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o:(RNWorklet::JsiWorklet::JsiWorklet(facebook::jsi::Runtime&, facebook::jsi::Value const&))
  >>> referenced by WKTJsiWorklet.h:74 (/Users/peter/Projects/viewfinder/node_modules/react-native-worklets-core/android/build/headers/rnworklets/react-native-worklets-core/WKTJsiWorklet.h:74)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o:(RNWorklet::JsiWorklet::~JsiWorklet())

  ld: error: undefined symbol: RNWorklet::JsiWrapper::wrap(facebook::jsi::Runtime&, facebook::jsi::Value const&, RNWorklet::JsiWrapper*)
  >>> referenced by WKTJsiWrapper.h:62 (/Users/peter/Projects/viewfinder/node_modules/react-native-worklets-core/android/build/headers/rnworklets/react-native-worklets-core/WKTJsiWrapper.h:62)
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o:(RNWorklet::JsiWorklet::createWorklet(facebook::jsi::Runtime&, std::__ndk1::shared_ptr<facebook::jsi::Function>))

  ld: error: undefined symbol: RNWorklet::JsiHostObject::get(facebook::jsi::Runtime&, facebook::jsi::PropNameID const&)
  >>> referenced by JVisionCameraProxy.cpp
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o:(vtable for RNWorklet::JsiWorklet)

  ld: error: undefined symbol: RNWorklet::JsiHostObject::set(facebook::jsi::Runtime&, facebook::jsi::PropNameID const&, facebook::jsi::Value const&)
  >>> referenced by JVisionCameraProxy.cpp
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o:(vtable for RNWorklet::JsiWorklet)

  ld: error: undefined symbol: RNWorklet::JsiHostObject::getPropertyNames(facebook::jsi::Runtime&)
  >>> referenced by JVisionCameraProxy.cpp
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o:(vtable for RNWorklet::JsiWorklet)

  ld: error: undefined symbol: typeinfo for RNWorklet::JsiHostObject
  >>> referenced by JVisionCameraProxy.cpp
  >>>               CMakeFiles/VisionCamera.dir/src/main/cpp/frameprocessor/java-bindings/JVisionCameraProxy.cpp.o:(typeinfo for RNWorklet::JsiWorklet)
  clang-12: error: linker command failed with exit code 1 (use -v to see invocation)
  ninja: build stopped: subcommand failed.

  C++ build system [build] failed while executing:
      /Users/peter/Library/Android/sdk/cmake/3.22.1/bin/ninja \
        -C \
        /Users/peter/Projects/viewfinder/node_modules/react-native-vision-camera/android/.cxx/Debug/4a1m2e2g/arm64-v8a \
        VisionCamera
    from /Users/peter/Projects/viewfinder/node_modules/react-native-vision-camera/android

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 14s
error Failed to install the app.
info Run CLI with --verbose flag for more details.

I uninstalled react-native-worklets-core, removed react-native-worklets-core from babel.config.js, removed worklet notation from useFrameProcessor() handler and tried to launch the app, but I am back from where I started -
I get system/frame-processors-unavailable: Frame Processors are not enabled!, js engine: hermes error.
I am not using Reanimated.
App and camera works fine if I am not using frameProcessor property on <Camera />.
I am testing this on a device with Android 10, I'll try to test on other Android versions.

any solutions so far , am still facing this issue in both IOS and Android

The same with w4t3r-45
"react-native": "0.72.5", "react-native-vision-camera": "3.0.0", "react-native-reanimated": "3.0.0",

@w4t3r-45 Hi. Could you please provide your package.json file and Android version that you use for testing?

@w4t3r-45 Hi. Could you please provide your package.json file and Android version that you use for testing?
this are the versions of packages am using , besides that i tested on Android 10 physical device and on IOS 16.6 also physical device.

"react-native": "0.71.13",
"react-native-reanimated": "^3.5.4",
"react-native-vision-camera": "^2.16.1",

@w4t3r-45 Thank you, I will try your solution.

@peterdee just let me know if you have any issues.

@w4t3r-45 , I have tried your solution but I am still getting the same issue.
ReanimatedError: Property '__scanCodes' doesn't exist, js engine: reanimated
"react-native": "0.71.4",
"react-native-reanimated": "^3.5.4",
"react-native-vision-camera": "^2.16.1",

still breaking in IOS 17
The Camera is not ready yet! Wait for the onInitialized() callback!

Still breaking on iOS 17. Please help!

The same issue after updating to iOS 17.
"react-native-vision-camera": "^2.15.2",
"react-native": "0.70.6",
"react-native-reanimated": "2.14.4"

Hi!
I've spent several hours working to resolve this issue with the react-native-vision-camera package 📷. I'd like to share the potential solution I've found. Here's a step-by-step guide:

Ensure Package Versions: First and foremost, please ensure these versions are specified in your package.json:

react-native-vision-camera: 2.15.2
react-native-reanimated: 2.17.0
vision-camera-code-scanner: 0.2.0
react-dom: ^18.2.0
react-native: 0.70.6

Android Cleanup: Navigate to the Android directory and execute the cleaning command:

cd android && ./gradlew clean

Yarn Cache and Android Start: Clear the yarn cache and initiate the Android application with:

yarn cache clean && yarn run android

iOS Build Cleanup: For iOS concerns, please delete the build folder:

rm -rf ios/build

CocoaPods Cleanup: Refresh your CocoaPods configurations in the iOS directory:

cd ios/
pod cache clean --all
pod deintegrate
pod install

Additional Cleanup: For a thorough cleanup, consider these steps:
watchman watch-del-all
rm -rf node_modules/ && npm install
rm -rf /tmp/metro-*.lock

🧩 Frame Processors are now enabled with these changes!
As a guiding note for future endeavors, for those starting new projects, I highly recommend using react-native-vision-camera version 3. This updated version offers enhanced features, better stability, and consistent support.
Furthermore, a special shoutout to mrousavy is essential. The development and enhancement of react-native-vision-camera have been monumental for the React Native community. Thank you, mrousavy, for your dedication and for arming developers with such invaluable tools.
Greetings!

`/* eslint-disable eol-last /
/ eslint-disable react-hooks/exhaustive-deps */
import * as React from 'react';
import {
Alert,
BackHandler,
Platform,
StatusBar,
StyleSheet,
Text,
View,
} from 'react-native';
import {useCameraDevices} from 'react-native-vision-camera';
import {Camera} from 'react-native-vision-camera';
import {useScanBarcodes, BarcodeFormat} from 'vision-camera-code-scanner';
import {useIsFocused} from '@react-navigation/native';
import CustomAppStatusBar from '../../Helpers/AppBar';
import BackNavigation from '../../Components/BackNavigation/BackNavigation';
import {
widthPercentageToDP as wp,
heightPercentageToDP as hp,
} from 'react-native-responsive-screen';
const styles = StyleSheet.create({
barcodeTextURL: {
fontSize: 20,
color: 'white',
fontWeight: 'bold',
},
parentCam: {
flex: 1,
backgroundColor: '#0D6E72',
},
camOne: {
height: hp('7%'),
width: wp('100%'),
},
camTwo: {
marginTop: 0,
paddingTop: 0,
height: hp('93%'),
width: wp('100%'),
},
});
export default function Scanner({navigation}) {
const [hasPermission, setHasPermission] = React.useState(false);
const devices = useCameraDevices();
const device = devices.back;
const isFocused = useIsFocused();
const [frameProcessor, barcodes] = useScanBarcodes([BarcodeFormat.QR_CODE], {
checkInverted: true,
});
const filteredBarcodesRef = React.useRef([]);
React.useEffect(() => {
const backAction = () => {
navigation.navigate('Dashboard');
return true;
};
const backHandler = BackHandler.addEventListener(
  'hardwareBackPress',
  backAction,
);

return () => backHandler.remove();

}, []);
React.useEffect(() => {
(async () => {
const status = await Camera.requestCameraPermission();
setHasPermission(status === 'authorized');
})();
}, []);
React.useEffect(() => {
// Update the filteredBarcodesRef with the detected barcodes
filteredBarcodesRef.current = barcodes.filter(
barcode => barcode.format === BarcodeFormat.QR_CODE,
);
// Check if the filteredBarcodes array has any barcodes
if (filteredBarcodesRef.current.length > 0) {
  navigation.navigate('TransactionWithCamera', {
    filteredBarcodes: filteredBarcodesRef.current,
  });

  // Reset filteredBarcodesRef after navigation
  filteredBarcodesRef.current = [];
}

}, [barcodes, navigation]);
return (
device != null &&
hasPermission &&
isFocused && (

<CustomAppStatusBar
backgroundColor={${Platform.OS === 'ios' ? '#fff' : '#0D6E72'}}
barStyle="dark-content"
/>

<BackNavigation name={'Qr Code'} route={'Dashboard'} />

    <View style={styles.camTwo}>
      <StatusBar animated={true} backgroundColor="#0D6E72" />
      <CustomAppStatusBar
        backgroundColor={`${Platform.OS === 'ios' ? '#fff' : '#0D6E72'}`}
        barStyle="dark-content"
      />

      <Camera
        style={StyleSheet.absoluteFill}
        device={device}
        isActive={true}
        frameProcessor={frameProcessor}
        frameProcessorFps={5}
      />
      {/* {filteredBarcodes.map((barcode, idx) => (
        <Text key={idx} style={styles.barcodeTextURL}>
          {barcode.displayValue}
        </Text>
      ))} */}
    </View>
  </View>
)

);
}
`
still shows me an error frameprocessor is not defined


feat: Support multiple services for ui5 yaml files and manifest.json

Allows to add multiple services in YAML file configurations and Manifest (and multiple annotations per service).
Previous logic only rewrote whole mockserver config. This is still possible, but through an optional parameter.
During mockserver config generation localService/data folder (mockdataPath) is also generated if it does not exist in project.

Hi @broksy,
I've tested adding a mockserver and found following issues:
In interactive mode there is no text for overwrite, it just gives the technical information questions.overwrite › (y/N):
✔ questions.pathToMock › mainService: /sap/opu/odata4/dmo/sb_travel_mdsk_o4/srvd/dmo/sd_travel_mdsk/0001/
? questions.overwrite › (y/N)

I can see a maintained text "Overwrite existing services", but can't see it in the question when running on command line.

I found the issue with i18n, there was a conflict due to global initialization of i18n in @sap-ux/cap-config-writer and @sap-ux/mockserver-config-writer. I switched now to an own instance of i18n for @sap-ux/mockserver-config-writer, see commit https://github.com/SAP/open-ux-tools/pull/2455/commits/5162ea34229ba8e6fc86b8fb1a4ea812a7f8ee7b.


Add isRequired() and isNotRequired() assertions

This assertion should check if the required property of e.g. an <input> element is true or not.
Example:
assert.dom('.username-field').isRequired();
assert.dom('.coupon-code').isNotRequired();

Also, the attribute being present also represents true, so the assertion should take that into consideration too.

@Turbo87 guess you can mark this as complete


Fixed issue with on set systems for pair types

Addressed issue with on set systems with pairs when matching multiple columns on a single table only triggering for the last column.

Needs a target branch that isn't master


Is the FP and FBP part of the algorithm in LEAP based on ray-driven, pixel-driven, or distance-driven?

I assume you meant "BP" instead of "FP" in your post, right?
The backprojection step of the FBP algorithms in LEAP uses a slight variation to the Separable Footprint (SF-RR) method.  All projectors in LEAP (expect non-axially aligned modular-beam data) use this method as well.


Run pytest using worksteal

This safes nearly 50% of runtime when running the tests locally for me on a 6 core machine.
This is possible now since most(all?) leaking state between the tests has been fixed.
https://pytest-xdist.readthedocs.io/en/stable/distribution.html#running-tests-across-multiple-cpus
Also set the deadline higher on a test that often fail for me locally

Unfortunatly this seems to be significantly slower on windows


Codegen add serde derives to enums, if specified

Related Issues
closes #461
Changes

Added support for serde derives for enums (following the same method as write_entities()

Hey @BenJeau, thank you so much for the quick fix!

No problem! The source code is clean and I was easily able to write up a fix - my first PR in a Rust related repo :)

Welcome to the Rust party! :P
Thanks for the support and we love to hear from the community


installation fails with "Skipping 1 packages not available: bamUtils"

Probably just missing bamUtils in your remotes

Hi, is there any update on this?
I couldn't install the package with same issues.

** byte-compile and prepare package for lazy loading
Error: package or namespace load failed for ‘bamUtils’:
(converted from warning) replacing previous import ‘GenomicRanges::shift’ by ‘data.table::shift’ when loading ‘bamUtils’
Error: package ‘bamUtils’ could not be loaded
Execution halted
ERROR: lazy loading failed for package ‘Ppurple’.`

Sorry for the late reply – we should update the install instructions.
You have to set this environment variable otherwise install_github errors out on any warning during package install (also for dependencies).
allows dependencies that throw warnings to install
Sys.setenv(R_REMOTES_NO_ERRORS_FROM_WARNINGS = TRUE)
May be good to put this in your .Rprofile or set the env variable in your .bash_profile
Marcin
From: mjko1210<EMAIL_ADDRESS>Reply-To: mskilab/JaBbA<EMAIL_ADDRESS>Date: Tuesday, June 23, 2020 at 2:28 PM
To: mskilab/JaBbA<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [mskilab/JaBbA] installation fails with "Skipping 1 packages not available: bamUtils" (#24)
Hi, is there any update on this?
I couldn't install the package with same issues.
** byte-compile and prepare package for lazy loading
Error: package or namespace load failed for ‘bamUtils’:
(converted from warning) replacing previous import ‘GenomicRanges::shift’ by ‘data.table::shift’ when loading ‘bamUtils’
Error: package ‘bamUtils’ could not be loaded
Execution halted
ERROR: lazy loading failed for package ‘Ppurple’.`
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/mskilab/JaBbA/issues/24*issuecomment-648338146__;Iw!!C6sPl7C9qQ!Ec5uknEfNxIxyuNHD9oYJoqTMayt0BQP7umA_bThTzYmotMimD4qPzlSQ8FSKLUcBzM$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ABFUFY44LRGMMXS2KBFSW5TRYDX3PANCNFSM4J6CWKLQ__;!!C6sPl7C9qQ!Ec5uknEfNxIxyuNHD9oYJoqTMayt0BQP7umA_bThTzYmotMimD4qPzlSQ8FS_yomDVo$.

This message is for the recipient’s use only, and may contain confidential, privileged or protected information. Any unauthorized use or dissemination of this communication is prohibited. If you received this message in error, please immediately notify the sender and destroy all copies of this message. The recipient should check this email and any attachments for the presence of viruses, as we accept no liability for any damage caused by any virus transmitted by this email.

We removed bamUtils from the dependency chain. This is related to the Ppurple package which we also suspended in JaBbA until we reduce its dependency lists.


Address CG issue in Ubuntu 16.04 image

Ubuntu 16.04 got left behind when we fixed dotnet/arcade#13186 in !32218. We need to continue work to

Find a way to bump the offending package version on the legacy machine
Remove this platform from our queues if we're unable to complete (1)
Get an exception for the CG issue — after we've exhausted other options

Release Note Category

[x] Feature changes/additions
[ ] Bug fixes
[ ] Internal Infrastructure Improvements

Release Note Description
We removed the hard-to-support ubuntu.1604.amd64* queues after working w/ the runtime team to ensure nothing was still using them.

waiting for a clean week w/o use of these queues

PR merged. change rolled out 8 November 2023


Travis: PHP 7.4 isn't allowed to fail anymore

Following https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/4340, stated that currently 7.4snapshot isn't failing and that the community seems to already trust the state of art of the PHP 7.4 branch (see e.g. Ocramius/ProxyManager), I suggest to start right now to require PHP 7.4 green builds

https://github.com/travis-ci/php-src-builder/pull/36 has been merged and in production, builds now already show errors that will need a fix for 7.4, like:
Failed asserting that 'PHP Parse error: syntax error, unexpected 'fn' (T_FN), expecting identifier (T_STRING) or '{' on line 3.\n
\n
Source:\n
<?php\n
use const A\ConstA;\n
use function B\fn;\n
use C\B;\n
                ' is null.

:tada:

ref https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/4427

after #4427 got merged, i let myself restart the build here - now all is green
let's be brave and merge this

Thank you @Slamdunk.


Abstracting the propagator method

Although this seems like a great way to generalize the propagators and make the code less repetitive, unfortunately we can't follow this approach because of limitations in numba :sweat:
In particular:

*args and **kwargs are not fully supported for functions as arguments https://github.com/numba/numba/issues/2916
passing functions as arguments has a noticeable overhead https://github.com/numba/numba/issues/2952 (I'm the author of this one)

In fact, I conducted some benchmarks with a modified version of your code, and the generic propagator function is about 3x slower:
In [30]: @jit
    ...: def propagator(k, r0, v0, tof, propagator_name_coe):
    ...:     p, ecc, inc, raan, argp, nu0 = rv2coe(k, r0, v0)
    ...:     nu = propagator_name_coe(k, p, ecc, inc, raan, argp, nu0, tof)
    ...:     return coe2rv(k, p, ecc, inc, raan, argp, nu)
    ...:

In [31]: propagator(k, r, v, tof, farnocchia_coe)
Out[31]:
array([[-3.59793410e+03, -4.33451819e+03,  3.75865837e+03],
       [ 6.22049734e+00, -1.48115243e+00,  4.24825467e+00]])

In [32]: farnocchia(k, r, v, tof)
Out[32]:
array([[-3.59793410e+03, -4.33451819e+03,  3.75865837e+03],
       [ 6.22049734e+00, -1.48115243e+00,  4.24825467e+00]])

In [33]: %timeit farnocchia(k, r, v, tof)
7.18 µs ± 61.5 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

In [34]: %timeit propagator(k, r, v, tof, farnocchia_coe)
21.4 µs ± 275 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)

Therefore, we have no other option than to create specific *_coe functions for every propagation algorithm.


How can i read data

How can i read data ?
How to connect to existing database in Android & IOS ?
Is there any documentation available ?
anything would be helpful.
Why there is not official nuget package from Micorsoft/Xamarin/SQLite ?

I no longer work on Xamarin, so closing this issue.
Will try it when get some free time.


Mysterious bug causes incorrect scrolling to bottom of page (and messes unread counts)

When I logged onto Zulip this morning via my Desktop, I had 96 unread messages but I did not read any of them.
I decided to look at my messages through my mobile which immediately marked all my unread messages as read and moved the pointer all the way to the bottom.
I then checked back on my Desktop and saw that all 96 unread messages were marked as read on Desktop as well.
Before on desktop:

Mobile view immediately after accessing on Desktop

Hrm, that definitely should happen.  I've also never had something of this form reported before, which makes me think that this is probably a regression new to chat.zulip.org.  I wish I had an idea for what could have caused it.

@showell @brockwhittaker do either of you have ideas of things we merged recently that could everything to be marked as read unexpectedly?  I've verified it isn't bankruptcy-related (from server logs).

https://github.com/zulip/zulip/blob/ba7b7a9a360249c47fc8b34ba7a648dcd714b405/static/js/resize.js
could this file have anything to do with it? the last two commits seem to be refactoring some resizing functionality which might be related because this bug only happens when there is some resizing going on, but i don't have enough experience with this css stuff to know if its relevant or not.
also, i noticed this problem happening about a week or so ago so the recent commits dated 10-16 days ago seem to fit the timeline. i figured maybe i was just seeing things then, but today it was definitely noticeable.

I haven't observed this happening again, so I now wonder whether it was the side of effect of some bug in chat.zulip.org.
Removing the priority label, since this may have some sort of strong 1-time thing where several people experienced this on the same day, and none of them again (could reasonably have to do with changes we made to how reloading worked).

Closing this as non-actionable.  We'll be making lots of changes to the unread-counts system in the next couple weeks, so if this quirk still exists, we'll be more likely to see it in testing.

I actually have seen this a couple times recently, and I think it's actually unrelated to the unread counts system -- the symptom is that you come back to your computer, and:
(1) The visual scroll position is at the bottom of the feed
(2) The cursor is actually still in the right place, as demonstrated by hitting up-arrow
(3) Everything has been marked as read, presumably through being scrolled down
So the bug here is definitely some piece of code that is incorrectly scrolling us to the bottom.  I will probably try to debug this by adding a log of console.log statements on chat.zulip.org for all of our scroll entries, and see which one is the culprit.

Can we rename the title to something like "Mysterious bug causes incorrect scrolling to bottom of page (and messes unread counts)"?

Yep, done.

I have a suspicion that what's going on is this:
https://blog.chromium.org/2017/03/reducing-power-consumption-for.html
Possibly what's happening is that Chrome's throttling means that sometimes the scroll events don't get throttled, but the "move the pointer" events that would normally prevent scroll events from proceeding too far are being throttled, resulting in the pointer walking below the screen.  I'll see if I can verify this by reading code.
If this is true, this would only affect Chrome (and maybe Edge if they're doing the same thing).  @wangjames what browser do you use?

This actually only ever happened to me on iOS Safari. I've never had this problem on desktop.

Just tested it again using the mobile web app with iOS safari and it automatically scrolled all the way to the bottom marking everything as read.

@wangjames interesting; did this happen the moment you loaded the app, or did you do something?

Moment I loaded the app

I have the same issue on iOS Safari, hence why I've never bothered to use Zulip on mobile.

OK.  It sounds like we actually have 2 bugs here; the thing I've been investigating is something in Chrome on web that happens when you leave a browser window overnight.
@brockwhittaker can you investigate the mobile Safari issue?

@synicalsyntax @wangjames what version of iOS are you on?  We can't reproduce with @brockwhittaker's phone.

10.3.3 (thanks for the reminder to update lol)
I have a iPhone 6 - what is brock using?

one thing I've kind of wondered is how does zulip handle the viewport resizing from desktop to mobile? i just went to the developer tools on chrome and changed the viewport and that marked my messages as read. I'll retry again later to see if that happens again

static/js/resize.js does it.  That's a great reproducer concept, though; it could explain some other things we've been seeing.  Let me investigate.

@wangjames I actually can't reproduce changing the viewport in chrome marking anything as read.  You can try doing this in a development environment, using manage.py mark_all_messages_unread  to set up the situation.

Also, what exact browser platform and version are you using?

oh wow
so i was unable to reproduce the issue on my desktop and my laptop so I must have just been seeing things with regards to the viewport
i just updated my iphone to 11.0.2 from 10.3.3 and now when i go to zulip it doesn't mark everything as read - so maybe this issue was just specific to a version of iOS safari?

OK.  I guess we should get someone who still has 10.3.3 to reproduce this in development and figure out what code is causing the scrolling.  It sounds like a Safari in iOS 10.3.3 bug, but we'll want to work around it somehow to minimize user pain.

I'm on 10.3.2 on a iPhone 5, but I'd need instructions on how to properly debug.

We haven't seen reports of this since the thing I thought might fix this 6 months ago, so I'm closing this as likely fixed.


[READY] Testing out actions and doc updates

Description

Testing out the github actions from #8
Updates to the publishing docs to account for new comment functionality in GHA

publish

The following docker images:
awsutils, helmsman-aws
have been published on Docker Hub.

@Nebulaworks/approvers this is ready to go

@sarcasticadmin Looks good on my end! Thanks for writing up the process on how to publish these docker images using the new process!


KerasClassifier model weights does not look properly reset before being fit

Hello,
I still has some bug/incomprehension with the Scikeras and Sklearn fit function interaction. Last issue was done in a hurry and did not highlight the bug so here I am again.
So I have the impression that fitting a model wrapped in KerasClassifier in a loop will not reset its weights before fitting it to the data in the same manner as If the Keras model alone is instantiated in the loop before being fit.
In summary, It seems that the model is not correctly reset so fitting it in a loop (a KFold cross-validation loop).
I encountered this issue using Scikeras professionally (there, I had clearly models that gave me an accuracy of 0.6 in the first loop turn before skyrocketing to something close to 1. I tried to reproduce the behavior with standard dummy data but performances depends too much on the data quality so I wanted to highlight the issue by looking directly at the weight of biases (even if it less intuitive to me than sudden performance increase).
Here the 2 piece of codes using a dummy dataset and printing the weight of the model's bias:
Reinstantiate the model directly in the loop:
from numpy import loadtxt
import numpy as np
from scikeras.wrappers import KerasClassifier
from keras.models import Sequential
from keras.layers import Dense
from sklearn.metrics import accuracy_score
from sklearn.utils import shuffle
from sklearn.pipeline import make_pipeline

def model_nn():

    model = Sequential()
    model.add(Dense(12, input_shape=(8,), activation='relu'))
    model.add(Dense(8, activation='relu'))
    model.add(Dense(1, activation='sigmoid'))
    model.compile(loss='binary_crossentropy', optimizer='adam', metrics=['binary_crossentropy'])
    return model

# load the dataset
dataset = loadtxt('pima-indians-diabetes.csv', delimiter=',')
model_nn = model_nn()

n_split = 10
X, y = dataset[:, 0:8],  dataset[:, 8].astype(int)
num_runs = 30
all_scores = []
kf = KFold(n_splits=n_split, shuffle=True)
for train_index, eval_index in kf.split(X, y):
    x_test, x_train = X[eval_index, :], X[train_index, :]
    y_test, y_train = y[eval_index], y[train_index]
    scores = []
    score = 0
    for nrun in range(num_runs):
        x_, y_ = shuffle(x_train, y_train)
        biais = model.layers[1].get_weights()[1]
        print(f"Before: {biais}")
        model_nn.fit(x_, y_, epochs=30, batch_size=16, verbose=False)
        biais = model.layers[1].get_weights()[1]
        print(f"After: {biais}")
        y_pred = (model_nn.predict(x_test) > 0.5).astype(int)
        score += np.mean(accuracy_score(y_test, y_pred))
    score /= num_runs
    all_scores.append(score)
print(f"{Mean accuracy: np.mean(all_scores)}")

Some of the logs showing the weights:

Console:

Before: [0. 0. 0. 0. 0. 0. 0. 0.]
After: [-0.07789122  0.44471914  0.17739178  0.18815784 -0.06638421 -0.134316
 -0.19207452  0.        ]
Before: [0. 0. 0. 0. 0. 0. 0. 0.]
After: [-0.19981909 -0.11162576  0.27216756 -0.26187867  0.2923611  -0.22338101
  0.31982166 -0.12609349]
Before: [0. 0. 0. 0. 0. 0. 0. 0.]
After: [ 0.         -0.17140345 -0.12318961  0.28291494  0.26646045 -0.15588419
 -0.01235106 -0.12218504]
Before: [0. 0. 0. 0. 0. 0. 0. 0.]
After: [-0.05344929 -0.05919147 -0.2310531   0.04890905  0.42504674 -0.04857899
 -0.11618819  0.04065897]
Before: [0. 0. 0. 0. 0. 0. 0. 0.]
After: [ 0.1234226  -0.15809119  0.17418759  0.          0.         -0.01723221
 -0.02341213 -0.2070783 ]
Mean accuracy: 0.6363636363636364
Before: [0. 0. 0. 0. 0. 0. 0. 0.]
After: [ 0.          0.09611724  0.36199677 -0.03512564 -0.2497901  -0.14980865
 -0.2800358  -0.20440115]
Before: [0. 0. 0. 0. 0. 0. 0. 0.]
After: [ 0.          0.          0.          0.1239132  -0.08133116 -0.0666899
 -0.12992416  0.        ]
Before: [0. 0. 0. 0. 0. 0. 0. 0.]
After: [-0.05295666 -0.13505259  0.05375762  0.1768484  -0.07555941 -0.00511672
 -0.09020937  0.00096915]
Before: [0. 0. 0. 0. 0. 0. 0. 0.]
After: [ 0.19113357 -0.25497457 -0.17226881  0.04259212 -0.27500728  0.
 -0.08212745  0.26095137]
Before: [0. 0. 0. 0. 0. 0. 0. 0.]
After: [-0.02211879 -0.2620719  -0.27976933  0.3668856   0.3155859  -0.25485513
  0.05424322 -0.27320358]
Mean accuracy: 0.6753246753246753

Using KerasClassifier :
from numpy import loadtxt
import numpy as np
from scikeras.wrappers import KerasClassifier
from keras.models import Sequential
from keras.layers import Dense
from sklearn.metrics import accuracy_score
from sklearn.utils import shuffle
from sklearn.pipeline import make_pipeline

def model_nn(num_sample=8, num_hidden=12):

    model = Sequential()
    model.add(Dense(num_hidden, input_shape=(num_sample,), activation='relu'))
    model.add(Dense(8, activation='relu'))
    model.add(Dense(1, activation='sigmoid'))
    model.compile(loss='binary_crossentropy', optimizer='adam', metrics=['binary_crossentropy'])
    return model

# load the dataset
dataset = loadtxt('pima-indians-diabetes.csv', delimiter=',')
modelscikeras = KerasClassifier(model_nn(8, 12), epochs=30, batch_size=16, verbose=False)

n_split = 10
X, y = dataset[:, 0:8],  dataset[:, 8].astype(int)
num_runs = 5
all_scores = []
kf = KFold(n_splits=n_split, shuffle=True)
for train_index, eval_index in kf.split(X, y):
    x_test, x_train = X[eval_index, :], X[train_index, :]
    y_test, y_train = y[eval_index], y[train_index]
    scores = []
    score = 0
    for nrun in range(num_runs):
        biais = modelscikeras.model.layers[1].get_weights()[1]
        print(f"Before: {biais}")
        modelscikeras.fit(x_, y_)
        biais = modelscikeras.model.layers[1].get_weights()[1]
        print(f"After: {biais}")
        y_pred = modelscikeras.predict(x_test)
        score += np.mean(accuracy_score(y_test, y_pred))
    score /= num_runs
    all_scores.append(score)
print(f"{Mean accuracy: np.mean(all_scores)}")

Console:

Before: [0. 0. 0. 0. 0. 0. 0. 0.]

Do you know a way to see if the model is properly reset when fitting with KerasClassifier ?
Thank you in advance for your time

You're using a pre-trained model:
KerasClassifier(model_nn(8, 12))

I think what you want is:
KerasClassifier(model_nn, num_sample=8, num_hidden=12)

So it was this all along, thank you very much


Mark functionPerRoute as deprecated

Description (required)
Marks the functionPerRoute option as deprecated in the Vercel page.
Related issues & labels (optional)

https://github.com/withastro/astro/pull/11728

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
guides/integrations-guide/vercel.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Filters/Charts Problems

[x] editing of filters not possible (@DmitryAstafyev)

[x]  long filters hide checkmark and color (@DmitryAstafyev)

[x] vertical scale needed, chart values seem to go missing...but we just adapt the scale (@fur-gan)

[x] after resizing we lost some space to the right (@fur-gan)

[x] dashed white line needs to show up in main chart view (@fur-gan)

[ ] selection needs to be possible with mouse drag (@fur-gan)

[x] yellow legend is only shown to the side and always with pink legend (@fur-gan)

[ ] missing focus in search field when hitting the / shortcut (works only on 2nd / (@DmitryAstafyev)

[x] sometimes the content in main view is missing (@fur-gan)

missing focus in search field when hitting the / shortcut
Duplicate of #1779

selection needs to be possible with mouse drag
Duplicate of #1600


Documentation: Update in Write your first program

TableauAuth Class requires a third parameter site_id as specified in the API reference. But the Getting started sample code passes only username and password. This leads to an authentication  error.

Updates should be made directly on the page:
https://tableau.github.io/server-client-python/docs/
Click "edit" at the top of the page to edit the correct spot.  This will get the changes into the correct branch.
Closing this merge request as the doc branch here is old.


[BUG] docs website is not pulling from docs/website/config/README.md

Describe the bug
https://docs.cocogitto.io/config/  is not pulling from docs/website/config/README.md. It looks like it is still referring to https://github.com/cocogitto/website even though a note says that was deprecated 8 months ago.
To Reproduce
Go to https://docs.cocogitto.io/config/ and see that bump_patch does not appear here but it does appear in docs/website/config/README.md
Expected behavior
https://docs.cocogitto.io/config/ matches docs/website/config/README.md
Additional context
Once this is resolved, also update reference to the old website repo here: https://github.com/cocogitto/cocogitto/blob/main/CONTRIBUTING.md#writing-documentation

Duplicate of #400


Bucket mixin callback functions should have a retry

What happened?
When a mixin to create a callback function that listens on a bucket is created, there may be times where the Cloud Function fails to deploy as it seems like Cloud Storage buckets are eventually consistent. Thus, creating a Cloud Function with the bucket as an event trigger immediately after creating the bucket could result in a failed function deployment. Re-running pulumi up on the Pulumi program will succeed in configuring these functions.
Since the mixin is a high-level bstraction over the raw CloudFunction resource, https://github.com/pulumi/pulumi-gcp/blob/885cf4a114fb22c0520c1945b2293472ca183073/sdk/nodejs/cloudfunctions/zMixins.ts#L170C42-L176, there doesn't appear to be an easy way to retry recreating this resource.
https://github.com/pulumi/pulumi/issues/7932 would be helpful for this.
Example
Run the examples/bucket Pulumi program a few times and observe that it usually fails with one or more of the Cloud Functions failing to deploy.
Output of pulumi about
NA
Additional context
Related: #1267
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Is that a bug in Cloud Storage Bucket resource? I think TF resources are supposed to be fully initialized by the time they are reported as created. Is there a similar issue upstream?


Improve configuration role section in release notes

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.


Updated README.md

Hey @T-u-s-h-a-r,
this is a duplicate URL

no, it should work
On Thu, 1 Oct 2020, 2:34 am Sonkeng Maldini<EMAIL_ADDRESS>wrote:

Hey @T-u-s-h-a-r https://github.com/T-u-s-h-a-r,
this is a duplicate URL
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sdmg15/Best-websites-a-programmer-should-visit/pull/423#issuecomment-701644936,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQI4HG6NPCWIK2PRMNA3EL3SIOMOVANCNFSM4R7PG6VQ
.

it is working fine ,i have checked
On Thu, 1 Oct 2020, 2:43 am Tushar Agrawal<EMAIL_ADDRESS>wrote:

no, it should work
On Thu, 1 Oct 2020, 2:34 am Sonkeng Maldini<EMAIL_ADDRESS>wrote:

Hey @T-u-s-h-a-r https://github.com/T-u-s-h-a-r,
this is a duplicate URL
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sdmg15/Best-websites-a-programmer-should-visit/pull/423#issuecomment-701644936,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQI4HG6NPCWIK2PRMNA3EL3SIOMOVANCNFSM4R7PG6VQ
.


Why alert Cannot read property 'on' of undefined when react-native start

Alert Cannot read property 'on' of undefined when run react-native start
slindeiMac:ReactNativeSampleApp slin$ react-native start
//...
/Users/slin/Desktop/ReactNativeSampleApp/node_modules/_yiewd@0.6.0@yiewd
/Users/slin/Desktop/ReactNativeSampleApp/node_modules/_zip-stream@1.1.1@zip-stream
Cannot read property 'on' of undefined
slindeiMac:ReactNativeSampleApp slin$ pwd
/Users/slin/Desktop/ReactNativeSampleApp

It work when i use ‘npm install ’ instead of 'cnpm install'


[Apple Reminders] composed time recognition no working anymore

Extension
https://www.raycast.com/raycast/apple-reminders
Description
With the latest updates of the Apple Reminders some “composed time” strings (like 1 hour and 10 mins) are not recognized as it used to be.
There are some weird strings that are recognized as in the screenshots below.

Steps To Reproduce

Open Raycast and an action from Apple Reminders extension (like My Reminders)
On a reminder item, change Due Date or press cmd+d
Enter one of the strings above and check the behaviour

Current Behaviour
No response
Expected Behaviour
It works as before

Thanks for reporting this issue. It seems it's related to our native date picker. I'll check with the team what's up.

This will be fixed in the next release.

I'm closing the issue since it appears to be fixed with latest update.
Thanks for the support and looking into this


fix - adding /ping for eik-client ping command

Adds a /ping route to be used by the cli ping command, which currently fails by default when running:
eik ping http://localhost:4100

the PR will enable changing this to eik ping http://localhost:4100/ping

The ping command works as expected for me with npx @eik/cli ping https://your.eik.server. I think perhaps we can close this.


[BUG] OpenID Connect redirects to "/" even if server.basePath is set

What is the bug?
Since i upgraded from 1.3.0 to 2.3.0 Opensearch-Dashboards configured with OICD always redirects to "/" not to the value defined in server.basePath.
What is the expected behavior?
After a successful login it should redirect to the value defined in server.basePath
What is your host/environment?

OS: docker on ubuntu 22.04
Version 2.3.0
Plugins: security

Do you have any screenshots?

Here in this screenshot you can see the redirect from oicd host back to the opensearch-dashboards auth works, but after that it redirects always to "/", expected value here should be "/dynrep"
Do you have any additional context?
opensearch-dashboards.yml
server.name: kibana
server.host: <IP_ADDRESS>
server.basePath: /dynrep
opensearch.hosts: https://localhost:9200
opensearch.ssl.verificationMode: none
opensearch.username: kibanaserver
opensearch.password: kibanaserver
opensearch.requestHeadersWhitelist: ["Authorization", "securitytenant"]

opensearch_security.multitenancy.enabled: true
opensearch_security.multitenancy.tenants.preferred: ["Global", "Private"]
opensearch_security.readonly_mode.roles: ["kibana_read_only"]

opensearch_security.auth.type: "openid"
opensearch_security.openid.connect_url: "https://myoicdhost/.well-known/openid-configuration"
opensearch_security.openid.client_id: "foo"
opensearch_security.openid.client_secret: "bar"
opensearch_security.openid.logout_url: "https://myoicdhost/logout"
opensearch_security.openid.scope: "email"
opensearch_security.openid.base_redirect_url: "https://myhostname/dynrep"

# Use this setting if you are running kibana without https
#opensearch_security.cookie.secure: false

opensearch-security/config.yml
---

_meta:
  type: "config"
  config_version: 2

config:
  dynamic:
    http:
      anonymous_auth_enabled: false
    authc:
      basic_internal_auth_domain:
        description: "Authenticate via HTTP Basic against internal users database"
        http_enabled: true
        transport_enabled: true
        order: 0
        http_authenticator:
          type: basic
          challenge: false
        authentication_backend:
          type: internal
      openid_auth_domain:
        description: "Authenticate via MSI IDP OIDC"
        http_enabled: true
        transport_enabled: true
        order: 1
        http_authenticator:
          type: openid
          challenge: false
          config:
            subject_key: "email"
            roles_key: "https://myoicdhost/groups"
            openid_connect_url: "https://myoicdhost/.well-known/openid-configuration"
        authentication_backend:
          type: noop
    authz:

Tracking related issue: https://github.com/opensearch-project/security-dashboards-plugin/issues/1098 and closing this.


⚠ Cioos National CKAN has degraded performance

In 986c27f, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 6549 ms

Resolved: Cioos National CKAN performance has improved in 484f700 after 5 minutes.


links around cmsplugins are removed upon save

When I create a cmsplugin instance in the text editor (for example a bootstrap3 image) and then click on the cursor icon that appears on hover, and then create a normal link (not a cmsplugin link), the link gets correctly created around the image cmsplugin. But upon saving it is stripped away.
I am currently searching for ways to prevent that.

@macolo any updates here? Could you please share more details about versions?


[DUOS-2905] Supports external & open access property in the data library table

Addresses
https://broadworkbench.atlassian.net/jira/software/c/projects/DUOS/boards/123?selectedIssue=DUOS-2905
Summary
Supports external & open access property in the data library table

Have you read Terra's Contributing Guide lately? If not, do that first.

Label PR with a Jira ticket number and include a link to the ticket
Label PR with a security risk modifier [no, low, medium, high]
PR describes scope of changes
Get a minimum of one thumbs worth of review, preferably two if enough team members are available
Get PO sign-off for all non-trivial UI or workflow changes
Verify all tests go green
Test this change deployed correctly and works on dev environment after deployment

I'll send out a cleaner PR.


Zipkin Example

I see @paolochiodi (and @rjrodger) implemented zipkin support and have since updated  the ramanujan project.
My question is how would you implement this as part of nodezoo? I'm assuming you add zipkin tracing to each individual micro-service?
Github as an example:
Would this be as simple as including seneca-zipkin-tracer and then adding this around line 46?
Service.use('zipkin-tracer', { sampling: 1 });

Obviously this is a change from your Iteration 3: Measurement where you use influxdb, grafana, etc.

Hi Shaun.
I didn't touch nodezoo in a long time and I'm not entirely familiar with it but from what I see those steps unfortunately aren't enough.
seneca-zipkin-tracer require a recent seneca version, but from what I see nodezoo services are stuck with seneca 2.0.0.
Once they are up to date then yes, the steps you described should work


Update 04-Integers.md

Typo error at 8th line
Thank you for your contribution to the IC Developer Portal.
Before submitting your Pull Request, please make sure that:

[x] You have updated the .github/CODEOWNERS file according to your changes.
[x] You have registered new documents to /sidebars.js if any.

Hi @saikumarb12345  , please review and agree to the DFINITY CLA to have this PR merged. Thank you!


OpenShiftCreator assumes /oapi/v1 endpoints

OpenShiftCreator.java sets up the target URL endpoint using a /oapi/vi/ path string:
url = new URL(apiURL + "/oapi/v1/namespaces/" + namespace + "/" + path + "s");
However, when parsing a JSON List that contains a "Service" item, this undefined endpoint cannot be resolved (404) using /oapi/v1/namespaces/[namespace]/services (OpenShift).
The endpoint can be resolved using the Kubernetes (/api/v1) API endpoint: /api/v1/namespaces/[namespace]/services
Question..
Should there be a 'services' endpoint exposed in oapi/v1 or should this code use the api/v1 endpoint for "Service" requests?

fixed via https://github.com/openshift/jenkins-plugin/commit/e720e3b6022bff59740dc51d7acdf91c53f8dd9d


Ruff and reviewdog question

Guys, I'd appreciate a little help here, has anybody integrated reviewdog with ruff yet?
Which --output-format value did you use?

@VianneyMI I saw you mentioned it here: https://github.com/astral-sh/ruff/discussions/4982#discussioncomment-6140413 could you please share your config?

I'm gonna merge this into #8655 which is an explicit request to support the reviewdog format as a first-class --output-format.

Just so I understand, this was marked closed "not planned" because it's been merged with #8655 , not because we aren't going to have ruff + reviewdog support, right?

Ah, it does say "duplicate" but i totally missed that. doh.
Thanks for the response.


Menu popover doesn't disappear after you click away from it

Description
On each of the status grid items there is a menu button in the top right of the page. When you click that menu item, the menu popover that appears only ever disappears when you click the button again. If you click away, it doesn't disappear.
Steps to Reproduce

Click on the menu button of any of the status grid items on the page (it looks like a small grey button with 3 dots inside).
Click outside of the menu anywhere on the page.
Notice how the menu does not disappear.

Expected Behaviour
I expect that when I click outside of from the menu (or after a short delay after a mouseOut event) that the menu would disappear.
Your Environment

NR1 CLI version used: @datanerd/nr1/1.19.5 darwin-x64 node-v10.16.3
Browser name and version: Versión 80.0.3987.122 (Build oficial) (64 bits)
Operating System and version: MacOS Catalina 10.15.3 (19D76)

:tada: This issue has been resolved in version 0.12.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

Note to self: Apply this same fix to the newrelic/workloads-geo-ops popovers on the menu button in the "all maps" screen.


RTL is not supported ( Arabic )

When adding ar local and adding the language json file it fall down to default local

var delegate = await LocalizationDelegate.create(
fallbackLocale: 'en_US',
supportedLocales: ['en_US', 'es', 'ar']);

Sorry , it's my bad . My implementation was wrong
It works perfect


Mass serialization ($all->to_json())

I hope we can convert a list of objects to json format or an array. Example:
$all = Person::all();
$json = $all->to_json();

or
$array = $all->to_array();

I speak English not well, so sorry for that.

I understand the performance implications that involve to make this a PHPActiveRecord core feature. I just want to share the workaround that I have applied on my PHPActiveRecord projects.
First of all, my models extends my "own" model abstract, which also extends the original PHPActiveRecord Model. Then, there I have a "helper" function:
<?php
abstract class DanielArandaModelAbstract extends ActiveRecord\Model{

    public function collection_to_array(){
        $results = call_user_func_array([get_class($this), 'all'], func_get_args());

        if( is_array($results) ){

            $results = array_map(function($item){
                return $item->to_array();
            }, $results);

            return $results;

        }else{
            return [$results->to_array()];
        }

    }

}

Then, in your project you only need this:
var_dump(YourModel::collection_to_array());

You will get the result of "all" converted into raw array.
It also forward the arguments for all, so you use it like all with the plus that it returns raw array instead of objects. And you are not doing foreach or maps around your project.
Bests,

You'd probably want to define your function as static.
And instead of using get_class($this) you're better of using "late static bindings"' get_called_class():
$results = call_user_func_array([get_called_class(), 'all'], func_get_args());

And it's better to not pass them by reference:
$called_class = get_called_class();
$args = func_get_args();
$results = call_user_func_array([$called_class, 'all'], $args);

I already refactor it a bit also:
<?php

namespace App\Models;

abstract class ModelAbstract extends \ActiveRecord\Model{

    public static function collection_to_array(){
        $results = call_user_func_array('static::all', func_get_args());

        if( is_array($results) ){

            $results = array_map(function($item){
                return $item->to_array();
            }, $results);

            return $results;

        }else{
            return [$results->to_array()];
        }

    }

}

BTW get_called_class is not needed as static refer to current class, and is how source code of PHPActiveRecord also does with all as wrapper to find.

Is there a case that Model::all doesn't return an array ?

Fair point, in theory not, but if you remember "all" is a proxy to find, thought that someone could call all with one argument, which will be ending using find_by_pk.
I have seen people doing:
Model::all(1);

It is a programmer "issue" as it is wrong implementation of all; we want our workaround code to be homogeneous with the native behavior. In strict mode, I would say that in my own project I would throw an Exception if programmer attempts to use "all" as finder by pk.

Model::all(1) will never return as single object.
https://github.com/jpfuentes2/php-activerecord/blob/master/lib/Model.php#L1579

@koenpunt  $single is not used, please double check the line, it proxy to find_by_pk and ignore the var $single:
https://github.com/jpfuentes2/php-activerecord/blob/master/lib/Model.php#L1606
I also confirmed the behavior with Unit Test:
public function testIsArray(){
    $this->assertFalse( is_array(SomeModel::all(1)) );
    $this->assertTrue( is_array(SomeModel::all()) );
}

;)

Oh well, that's pretty ugly. An obvious bug if you ask me.

Right! Thank You for create the issue. Please mention me when the PR is ready and I would love to collaborate in the code review.


Should not init axis if provided to controller

Currently even if axisLeft, axisRight is provided to controller, it gets overridden in the doneBeforePainterInit function.
I have created #56 to fix this issue.

merged