[scripts-audit] Rollup PR 2021-02-26 - cmake scripts not found #16440

Describe the bug

See PR #16440 vcpkg helper cmake port scripts not found
Vcpkg appears to not know how to find the new portfile functions vcpkg_cmake_build vcpkg_cmake_configure vcpkg_cmake_install and vcpkg_cmake_config_fixup

Environment

OS: [Microsoft Windows [Version 10.0.19042.844]]
(I have not tested this on my Linux OpenSUSE 15.2 on WSL2 and Hyper-V)
Compiler:

Visual Studio 2017 Edition [Version 15.9.33]

Visual Studio Toolset [Version 14.16.27023]
Microsoft (R) C/C++ Optimizing Compiler [Version 19.16.27045 for x64]

Visual Studio 2019 Edition [Version 16.8.6]

Visual Studio Toolset [Version 14.28.29333]
Microsoft (R) C/C++ Optimizing Compiler [Version 19.28.29337 for x64]

To Reproduce
Steps to reproduce the behavior:

System default triplet is x64-windows
From Powershell Core 7.2 prompt with VS variables set
git pull  updates vcpkg instance with PR #16640
Update local port(s) portfile.cmake to use new vcpkg CMake port helper functions from #16440 as the following messages are now present:

See attached: New vcpkg CMake Deprecation Warnings.txt

./vcpkg install vcpkg-cmake vcpkg-cmake-config --recurse --keep-going installed successfully for x64-windows
./vcpkg install [port] - in this case a local copy of rapidstring as vcpkg no longer maintains the port
See error - console log only:

PS D:\vcpkgMgr\2019\test> vcpkg install rapidstring
Computing installation plan...
The following packages will be built and installed:
rapidstring[core]:x64-windows -> 2018-08-03#1002
Starting package 1/1: rapidstring:x64-windows
Building package rapidstring[core]:x64-windows...
-- Using cached D:/vcpkgMgr/2019/test/downloads/cenit-rapidstring-2a5fa4a42b37b00e1388f4161b1a96876e25b555.tar.gz
-- Cleaning sources at D:/vcpkgMgr/2019/test/buildtrees/rapidstring/src/876e25b555-4a0d79fa33.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source D:/vcpkgMgr/2019/test/downloads/cenit-rapidstring-2a5fa4a42b37b00e1388f4161b1a96876e25b555.tar.gz
-- Using source at D:/vcpkgMgr/2019/test/buildtrees/rapidstring/src/876e25b555-4a0d79fa33.clean
CMake Error at ports/rapidstring/portfile.cmake:11 (vcpkg_cmake_configure):
Unknown CMake command "vcpkg_cmake_configure".
Call Stack (most recent call first):
scripts/ports.cmake:139 (include)
Error: Building package rapidstring:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: rapidstring:x64-windows
Vcpkg version: 2021-01-13-8027bea90b47d50fd6090bbf5ded330f00f87570

Expected behavior
vcpkg should install port using new helper cmake port scripts
Failure logs
-None - only console log shown above
Additional context
After install the ports vcpkg

The new scripts are located  at these locations after install:

Port vcpkg-cmake-config

[vcpkg-root]\installed\x64-windows\share\vcpkg-cmake-config
[vcpkg-root]\packages\vcpkg-cmake-config_x64-windows\share\vcpkg-cmake-config
[vcpkg-root]\ports\vcpkg-cmake-config

Port vcpkg-cmake

[vcpkg-root]\installed\x64-windows\share\vcpkg-cmake
[vcpkg-root]\packages\vcpkg-cmake-config_x64-windows\share\vcpkg-cmake
[vcpkg-root]\ports\vcpkg-cmake

Vcpkg List showing x64-windows version of ports installed:

PS D:\vcpkgMgr\2019\test> vcpkg list
vcpkg-cmake-config:x64-windows                     2021-02-26
vcpkg-cmake:x64-windows                            2021-02-26
vcpkg-gfortran:x64-windows                         3                Metaport to install gfortran dependencies from m...
vcpkg-gfortran:x86-windows                         3                Metaport to install gfortran dependencies from m...
yasm-tool-helper:x64-windows                       2020-10-12       This port provides helper functions for ports ne...
yasm-tool-helper:x86-windows                       2020-10-12       This port provides helper functions for ports ne...
yasm-tool:x86-windows                              2020-10-12       A modular assembler. This port is intended to bu...

Note 1: Vcpkg.exe was built from the latest clone of microsoft/vcpkg-tool with CMake as of ~ 03/01/2021 01:45 UTC
Note 2: Downloaded vcpkg.exe with same results only difference is the sha commit string version Vcpkg version: 2021-01-13-d67989bce1043b98092ac45996a8230a059a2d7e
Note 3: Tried to install ports vcpkg-cmake:x86-windows and vcpkg-cmake-config:x86-windows in case it is like port yasm-tool which is only installed as x86-windows, but was not allowed to install x86-windows triplet with message:

PS D:\vcpkgMgr\2019\test> vcpkg install vcpkg-cmake vcpkg-cmake-config --triplet=x86-windows --recurse --keep-going
Computing installation plan...
warning: vcpkg appears to be in a Visual Studio prompt targeting x64 but is installing packages for x86-windows. Consider using --triplet x64-windows or --triplet x64-uwp.
The following packages will be built and installed:
vcpkg-cmake[core]:x86-windows -> 2021-02-26
vcpkg-cmake-config[core]:x86-windows -> 2021-02-26
Starting package 1/2: vcpkg-cmake:x86-windows
Building package vcpkg-cmake[core]:x86-windows...
CMake Error at ports/vcpkg-cmake/portfile.cmake:2 (message):
vcpkg-cmake is a host-only port; please mark it as a host port in your
dependencies.
Call Stack (most recent call first):
scripts/ports.cmake:139 (include)
Error: Building package vcpkg-cmake:x86-windows failed with: BUILD_FAILED
Elapsed time for package vcpkg-cmake:x86-windows: 712.7 ms
Starting package 2/2: vcpkg-cmake-config:x86-windows
Building package vcpkg-cmake-config[core]:x86-windows...
CMake Error at ports/vcpkg-cmake-config/portfile.cmake:2 (message):
vcpkg-cmake-config is a host-only port; please mark it as a host port in
your dependencies.
Call Stack (most recent call first):
scripts/ports.cmake:139 (include)
Error: Building package vcpkg-cmake-config:x86-windows failed with: BUILD_FAILED
Elapsed time for package vcpkg-cmake-config:x86-windows: 32.85 ms

Attached

Portfiles for local copy of rapidstring:

CMakeLists.txt: CMakeLists.txt
portfile.cmake: portfile.cmake.txt with updates as follows:

vcpkg_install_cmake has been deprecated in favor of vcpkg_cmake_install
vcpkg_build_cmake has been deprecated in favor of vcpkg_cmake_build
vcpkg_fixup_cmake_targets has been deprecated in favor of  vcpkg_cmake_config_fixup

vcpkg.json: vcpkg.json.txt

/cc: @strega-nil
I forgot to cc you on this.
Thank you for all the hard work! 👍✨

@strega-nil Seems you forgot to revert some files.

Hmm, right; the issue is that these deprecation warnings are only meant to be followed for people who are writing ports, not for people who are installing ports... @ras0219, any ideas?

@StarGate-One the point of these ports is that the user should never be installing these on their own; they are only used as helpers. The whole point of them is that ports like this are supposed to replace the scripts tree for certain scripts. Therefore, the only "useful" way to use them is as a host port, since it's a tool.

@strega-nil

We did not install them, vcpkg did on both Windows and then both Linux installs on WSL2 and Hyper-V... A total of 8 vcpkg instances.
We did try to install the x86-windows which failed, when vcpkg could not find the x64-windows it did install.
Since we have local ports, which are not in the ports provided on the vcpkg repo (and never will since they are proprietary), we should not use the new scripts and stay with the old ones until they are deleted or should we convert our proprietary ports when vcpkg can see these scripts?
Thank you and have a wonderful evening, sorry if we have caused problems.

Additional Information, it appears there are 3 ports already using the new cmake scripts:

PS D:\vcpkgMgr\2017\prod> vcpkg remove vcpkg-cmake-config vcpkg-cmake
The following packages will be removed:

fmt:x64-windows
shiva:x64-windows
spdlog:x64-windows
vcpkg-cmake:x64-windows
vcpkg-cmake-config:x64-windows
Additional packages (*) need to be removed to complete this operation.
If you are sure you want to remove them, run the command with the --recurse option
PS D:\vcpkgMgr\2017\prod>

There is an additional deprecation about FEATURES keyword now:

Starting package 8/9: spdlog:x64-windows
Building package spdlog[benchmark,core]:x64-windows...
-- Using cached D:/vcpkgMgr/2017/prod/downloads/gabime-spdlog-4a9ccf7e38e257feecce0c579a782741254eaeef.tar.gz
-- Cleaning sources at D:/vcpkgMgr/2017/prod/buildtrees/spdlog/src/41254eaeef-61b213204a.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source D:/vcpkgMgr/2017/prod/downloads/gabime-spdlog-4a9ccf7e38e257feecce0c579a782741254eaeef.tar.gz
-- Applying patch fix-featurebuild.patch
-- Using source at D:/vcpkgMgr/2017/prod/buildtrees/spdlog/src/41254eaeef-61b213204a.clean
CMake Deprecation Warning at scripts/cmake/vcpkg_check_features.cmake:182 (message):
calling vcpkg_check_features without the FEATURES keyword has been
deprecated.
Please add the `FEATURES` keyword to the call.

Call Stack (most recent call first):
ports/spdlog/portfile.cmake:10 (vcpkg_check_features)
scripts/ports.cmake:139 (include)

We do set the environment variable VCPKG_FEATURE_FLAGS to turn off all the features we are not using:
VCPKG_FEATURE_FLAGS=-binarycaching,-compilertracking,-manifests,-registries,-versions
Does this mean to change our scripts to somehow other disable these features we do not want to use?

@StarGate-One alright, I'll answer your questions one at a time:

Yeah, correct
Don't try to install these yourself, they're just helper ports to be depended upon by other ports
Yes, you should switch to the new scripts if you have the time; you should depend on the vcpkg-cmake port as a host dependency (i.e., in "dependencies" of your vcpkg.json, you'd put { "name": "vcpkg-cmake", "host": true }
yep, correct (technically, only fmt uses it, the other two depend on fmt)
these are for port features, not vcpkg's feature flags; spdlog uses the vcpkg_check_features function without the FEATURES keyword, which is now deprecated (but still works fine).


RTL Languages direction is LTR

There are many Right-To-Left (RTL) languages in the translation but they lack RTL styles, at least the html tag for RTL languages should declared as defined in W3 Internationalization Docs like following

However further CSS fixes is required to improve the interface to fully support RTL languages.

Do you mean the notification bar or the website? Or both?
In the bar i already incorporated some stuff.
<style>.buorg {direction:RTL; unicode-bidi:embed;}</style>
Do I need HTML there as well?
What do I need to do for the website?

@farshad-sadri
Can you help me a little bit with this?

Hey @josselex
Sorry I totally missed your messages!
Sure, I can do some CSS and UI.
And I was talking both about your main website browser-update.org supporting RTL languages and also the update bar people use on their website.


Attaching a touch event handler on ScrollView breaks the scrolling

Attaching a touch event handler like touchstart or touchend to a ScrollView makes the scroll view not scrollable.
var page = tabris.create("Page", {
  title: "Scroll Composite - Horizontal",
  topLevel: true
});

var scrollView = tabris.create("ScrollView", {
  direction: "horizontal",
  layoutData: {left: 0, top: [40, 0], right: 0, bottom: [40, 0]},
  background: "#234"
}).on("touchstart", function(event) {
  console.log("touchstart triggered: " + JSON.stringify(event));
}).appendTo(page);

for (var i = 0; i < 50; i++) {
  tabris.create("TextView", {
    layoutData: {left: i * 30 + 20, centerY: 0, width: 30},
    text: i + "°",
    foreground: "white"
  }).appendTo(scrollView);
}

page.open();

Is this still valid? Could you try a "tap" gesture listener instead?

Listening for tap on a ScrollView generates the following error on the Android client:
Could not create object "tabris.GestureRecognizer" (reason:
Attempt to invoke interface method 'void com.eclipsesource.tabris.
client.core.IOperator.create(com.eclipsesource.tabris.client.core.
operation.CreateOperation)' on a null object reference)

Could not listen to event "gesture" (reason: The parameter 'type'
in call ParamCheck.notNull() must not be null)

The iOS client doesn't generate an error, but tap never gets triggered.

tap gesture works fine.
Currently touchstart blocks scrolling on Android, but works on iOS.
Possible use case would be implementing focus out for custom widgets in a scroll view.

Similarly, listening for touchend on a ScrollView prevents scrolling on Android but works fine on iOS.  A scrollend event is what I was looking for.
var page = new tabris.Page({
  title: '#191',
  topLevel: true
});

var scrollView = new tabris.ScrollView({
  layoutData: {left: 0, top: 0, right: 0, bottom: 0}
}).appendTo(page);

scrollView.on('touchend', function() {});

for(var i = 0; i < 20; i++) {
  new tabris.Composite({
    top: i * 100,
    left: 0, right: 0,
    height: 100,
    background: i % 2 ? 'black' : 'white'
  }).appendTo(scrollView);
}
page.open();

Neither platform fires the event.
The following is a valid workaround on Android, but does not work on iOS (no event is fired and no widgets are visible):
var page = new tabris.Page({
  title: '#191 Workaround',
  topLevel: true
});

var scrollView = new tabris.ScrollView({
  layoutData: {left: 0, top: 0, right: 0, bottom: 0}
}).appendTo(page);

var composite = new tabris.Composite().appendTo(scrollView);

composite.on('touchend', console.log);

for(var i = 0; i < 20; i++) {
  new tabris.Composite({
    top: i * 100,
    left: 0, right: 0,
    height: 100,
    background: i % 2 ? 'black' : 'white'
  }).appendTo(composite);
}
page.open();

The use case for listening for touchend was getting the ScrollView to "snap" to certain positions when the user finished scrolling.  It's not a very high priority for me at this time.

Thanks for the heads up. I can confirm the issue and we will have a look at it.

Original snippet seems to have been written for 1.x; rewrote for 3.x and tested this on 3.0.0-beta2 and can confirm scrolling works well on both Android and iOS
import {ScrollView, TextView, contentView, WidgetTouchEvent, Composite} from 'tabris';

const scrollView = new ScrollView({
	left: 0, top: '40%', right: 0, bottom: '40%',
	direction: 'horizontal',
	background: '#234',
}).onTouchStart(({type}: WidgetTouchEvent) => {
	console.log(`${type} triggered`);
}).appendTo(contentView);

for (let i = 0; i < 50; i++) {
	new TextView({
		left: i * 30 + 20, centerY: 0, width: 30,
		text: i + '°',
		textColor: '#FFF',
	}).appendTo(scrollView as Composite);
}

Thanks for the update on the original issue snippet. The attached snippet of code seams to be based on the previous scrollview.js snippet which has just been replaced with a more streamlined scrollview.jsx version.

@cookieguru @cpetrov I actully tested your snippet above and found that scrolling and the touch start event worked as expected on 3.x nightly. Can you still reproduce the issue?

I just retested the snippet above and found that the Android client does fire the touch start event, while ios does not.


Problem, help. I've refresh the wrong version of PKG

I've flashed the wrong version of PKG (cp1 1.4ver), actually my  device is Rp1(1.4ver) , Now its Stuck on welcome screen...how should i do

i can still use adb shell. but wifi cannot connected ,so i cannot use fw to refresh the correct PKG(RP1)

go to black block state and connect the usb cable.
python dpt-tools.py --diagnosis
install-pkg

go to black block state and connect the usb cable.
python dpt-tools.py --diagnosis
install-pkg

Thanks a lot !
should i unpack the correct PKG, and run apk which is included in ?

No, just flash the right system pkg. Don't unpack anything.
On Thu, Jun 6, 2019, 06:16 devilzwy<EMAIL_ADDRESS>wrote:

go to black block state and connect the usb cable.
python dpt-tools.py --diagnosis
install-pkg
Thanks a lot !
should i unpack the correct PKG, and run apk which is included in ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/HappyZ/dpt-tools/issues/102?email_source=notifications&email_token=ABDVEKTA7NUSW4ETATE2CSDPZDWXTA5CNFSM4HU2XNHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXCQZWY#issuecomment-499453147,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDVEKUI5IUTP6S6XJFSPW3PZDWXTANCNFSM4HU2XNHA
.

Sorry, but how to "install-PKG" in diagnosis mode?
could you show me the shell ?

download the latest dpt-tool:
>> python dpt-tools.py --diagnosis
...
>> help
...
>> install-pkg
<follow instructions>

i tried "python dpt-tools.py --diagnosis "

i tried "python dpt-tools.py --diagnosis ", but  the shell show “Cannot open serial port /dev/tty.usbmodem01 due to could not open port '/dev/usbmodem01”

If you are using a Windows system, when the USB cable is connected, check which COM port is added in the serial port of the system device list. If it is COM8, enter the command line when you ask for your communication port: com8
获取 Outlook for iOShttps://aka.ms/o0ukef

发件人: devilzwy<EMAIL_ADDRESS>发送时间: Friday, June 7, 2019 10:43:16 PM
收件人: HappyZ/dpt-tools
抄送: H; Comment
主题: Re: [HappyZ/dpt-tools] Problem, help. I've refresh the wrong version of PKG (#102)
i tried "python dpt-tools.py --diagnosis ", but the shell show “Cannot open serial port /dev/tty.usbmodem01 due to could not open port '/dev/usbmodem01”
―
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/HappyZ/dpt-tools/issues/102?email_source=notifications&email_token=AFAUYMOGY6GRV6KWA75YIHTPZJXYJA5CNFSM4HU2XNHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXGA54A#issuecomment-499912432, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFAUYMNJHN5YJD7P7QPF6W3PZJXYJANCNFSM4HU2XNHA.

If you are using a Windows system, when the USB cable is connected, check which COM port is added in the serial port of the system device list. If it is COM8, enter the command line when you ask for your communication port: com8

Thanks 6bigfire ,
Done this bebfore, and now i've flashed the correct PKG ( 0x3 FwUpdater.pkg ) by install-pkg. ( following instructions ) .  But its still Stuck on welcome screen for a long time ( over 10min...) , should i flash 0x4 FwUpdater.pkg now?

to confirm, you see welcome but it stucks? are you still able to use adb? If so, you got stuff wrong in system partition.
Which pkg were you downloaded?
I kinda suggest you to upgrade to 1.6 directly based on the upgrade guide. If adb works, then using cables you should still be able to use fw in that welcome screen. Otherwise, use the same install-pkg method in diagnosis mode.

to confirm, you see welcome but it stucks? are you still able to use adb? If so, you got stuff wrong in system partition.

yes, I can use 'adb shell'  when welcome.

To HappyZ：
I think i got wrong stuff wrong in system partition when 0x3 (The modification will change your Android boot partition.) ,  could you tel me how to fix it

i suggest you to flash the official pkg and update to 1.6 first

Thanks,
i do so ~

I factory reset my device and now it cannot be connected with WiFi. I can connect it with command:
dpt-tools --diagnosis
But I have no idea what to do next to connect the device to WiFi. I tried to flash v1.6 with install-pkg, but it seems failed.
I checked this thread, @HappyZ suggests to flash the official pkg first. I would like to know where to find the official pkg? Thanks a lot!


No apps connected. Sending "reload" to all React Native apps failed. Make sure your app is running in the simulator or on a phone connected via USB.

On my Iphone, React Native Debugger does not work.
With emulator there is no problem. But when I use my Iphone, If I click reload button in Chrome React Native Debugger it is not working and it throws below error.
I can see logs on my Chrome React native debugger but it is not stable.
Warn in Metro bundler console:
No apps connected. Sending "reload" to all React Native apps failed. Make sure your app is running in the simulator or on a phone connected via USB.
Real device is connected. My all devices use same Wireless network.
React Native version:
System:
OS: macOS 10.15.5
CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
Memory: 110.77 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.13.1 - /usr/local/bin/node
Yarn: Not Found
npm: 6.14.6 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.0 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 13.6, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
Android SDK:
API Levels: 23, 28, 29
Build Tools: 28.0.3, 29.0.2, 29.0.3
System Images: android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 3.5 AI-191.8<IP_ADDRESS>10548
Xcode: 11.6/11E708 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_232 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.11.0 => 16.11.0
react-native: 0.62.2 => 0.62.2
Steps To Reproduce

Connect IOS device (IOS 13.6) to device.
Validate real device connection on XCode
Start app on real device
Debugger and metro bundler starts
Press reload button in debugger and get above error in metro bundler console

Same issue for me

Same issue for me too after migrate to RN 0.62 (from 0.59)
Using Windows and tested on Android

So can you provide your full solution step by step please?

I don't have any solution about "No apps connected" problem, because I still have the same ...
I have just a solution about bundling (ci below), but I don't know if it is linked. Do you have the same problem ?
https://github.com/facebook/react-native/issues/18692

After 24 hours I solved this issue. Problem is somehow related to rn0.62 or its dependencies. I upgrade my project to 0.63.1 and it solved. 0.62 is really buggy version. I recommend 0.63.x

Okay, I will try this, thanks !

@hakkikonu Not working to me in Android. With command: react-native run-android, it is not attaching with npm. Please suggest any way out.

use 0.63.1

use 0.63.1

I am using 0.63.1 as you recommended but still it's not working. Any another way out?

I'm having a similar issue and i think it is related to the Metro Bundler. Out of nowhere my React Native project stopped working.  When I create a new project with react-native init, after installing dependencies and pods, i cannot get the example app to run with react-native run-ios.

use 0.63.1

I am already using as you recommended. After too many deeps I found the problem which is My project got corrupted after package name changes.

Did you upgrade xcode recently? I started experiencing this problem since the day I installed Xcode 11.6. Downgrading to 11.5 and reported if it solved my issue.

I also only have problems while deploying on actual devices. You can try to run the metro bundler from console while specifying a port
react-native start --port 8085 --reset-cache
Then try to see if you can access metro bundler from the browser: localhost:8085. Here you should see metro bundler info. In theory I guess, you should also be able to access this address from your phone or tablet. (Sometimes replacing "localhost" with your actual ip address helps). Here is also my problem, that this address isnt accessible through my devices, even while being on the same network.

Downgrading to 11.5 wont change a thing for me.
To anyone who also experinces this error: do you have also problems with freshly created projects using react-native init???

Yes, in my case I migrated an app from 0.48 to 0.52. So, I created a new project, and copy/paste codebase.
And yes, I have this problem since this new project.
I upgrade to 0.63 but still the same problem

I m using RN version 0.63.1, but still getting the same error.

For me I realized the issue was because my phone and laptop were not on the same network (one was on wifi one was on cellular). After putting phone on wifi it worked.

React Native is a real piece of work.

I have the same problem.
And also, another:
I've created a react application with the command npx react-native init. it worked well. I can deploy this app on an Android Emulator, but cannot do it on my device. The device is in developer mode and when I run the command adb devices it returns the device connected.
But, when I try to run the npx react-native run-android command, it responds that  No Android device or emulator connected.

Ok I solved this issue (on Android Emulator). Please follow this steps (only for Android) :

Open MainApplication.java and remove import com.facebook.react.BuildConfig;

Reset metro bundler cache : npx react-native start --reset-cache

Remove Android assets cache : cd android && ./gradlew clean

Relaunch metro server : npx react-native run-android

And see the magic 🎉
If you have a error like Invariant Violation: Module AppRegistry is not a registered callabel module, scroll on your terminal to see root cause.

I was able to resolve this on iOS when running on a real device. After bundle finishes, press the stop button in Xcode then open and close the app and it works fine.

If the app build mode is a Release, it will not be connected.
To switch build you should go to the Product > Scheme > Edit Scheme and select Debug for Build Configuration.

The phone and the computer have to be on the same WiFi connection.

Sometimes connect pc and phone on the same network is not enough :/

i painstakingly updated from RN 0.59 to 0.62 and now i have this issue on iOS device. no shake, no metro-triggered dev menu or reload works.
i would try upgrading to 0.63 but react-native-webview doesn't fully support it.

I am having this issue with iOS. Using RN v0.63.2 and code v12.0 beta 5 with ios 14 beta on my device. I am unable to connect to the metro bundler and the app can only run on my device while it is running inside of xcode.

Windows 10.
With me the problem was solved as follows.
I was using PowerShell before and the error started to appear out of nowhere.
Then I opened the Command Prompt (CMD) in administrator mode. I ran the npx react-native run-android and then opened the normal emulator and stopped giving this error.

https://docs.microsoft.com/fr-fr/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7
if u r in windows change this setup works for me

Sounds like some people were able to fix this by upgrading 0.63.x, others are reporting that didn't work, there's some workarounds suggested... but overall lots of people are hitting this and there's some confusion for sure. As people are able to unblock themselves definitely share so that others can benefit.

I also had the same problem in Android only - the development build didn't have Developer Menu or connection to the Metro Bundler.
The answer from @Johbrun helped me resolve it - just remove import com.facebook.react.BuildConfig;. I have added that line because I thought the BuildConfig class wasn't imported. However, that's not the case and importing it from the com.facebook.react namespace actually caused harm:
// com.facebook.react.BuildConfig;
public final class BuildConfig {
    public static final boolean DEBUG = false;
    public static final String LIBRARY_PACKAGE_NAME = "com.facebook.react";
    /** @deprecated */
    @Deprecated
    public static final String APPLICATION_ID = "com.facebook.react";
    public static final String BUILD_TYPE = "release";
    public static final String FLAVOR = "";
    public static final int VERSION_CODE = 1;
    public static final String VERSION_NAME = "1.0";
    public static final int EXOPACKAGE_FLAGS = 0;
    public static final boolean IS_INTERNAL_BUILD = false;

    public BuildConfig() {
    }
}

The global BuildConfig which is the correct one:
public final class BuildConfig {
  public static final boolean DEBUG = Boolean.parseBoolean("true");
  public static final String APPLICATION_ID = "my_app_id";
  public static final String BUILD_TYPE = "debug";
  public static final String FLAVOR = "";
  public static final int VERSION_CODE = 22;
  public static final String VERSION_NAME = "2.2";
}

@tsvetan-ganev that seems like it should be included. Could you send a PR for that for someone to check out?

I had the same problem so I put the app in debug mode and saw this error
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libreactnativejni.so
This answer helped https://stackoverflow.com/questions/54888255/react-native-app-crashes-on-real-android-device/54889555#54889555

I had this error when developing using react-native-macos. When I did npm run start:macos I got the error. Running npx react-native run-macos made it work again.

shaking device (or CMD + D ...) -> Configure Bundler -> metro bundler machine IP Address on Local Network
and also check this
iOS 14 > Settings > Privacy > Local Network
It works fine.

I had to run yarn web instead of yarn start

For me it was happening when using android emulator. Adding this to the android manifest did the trick:
android:usesCleartextTraffic="true"
reference: https://stackoverflow.com/questions/45940861/android-8-cleartext-http-traffic-not-permitted

For us, the issue was using a different configuration on ios. We created a Local configuration to connect to an emulated backend, this caused the live reload to stop working. It seems like it only works on Debug configuration.

Try this hakkı kardeş put your terminal command at below.
adb reverse tcp:8081 tcp:8081
Then just start server
npx react-native start --reset-cache
It worked for me

Ok I solved this issue "No apps connected. " (on Android Emulator). Please follow this steps (only for Android) :

Open MainApplication.java and remove import com.facebook.react.BuildConfig;
Reset metro bundler cache : npx react-native start --reset-cache
Remove Android assets cache : cd android && ./gradlew clean
Relaunch metro server : npx react-native run-android

And see the magic 🎉
If you have an error like Invariant Violation: Module AppRegistry is not a registered callabel module, scroll on your terminal to see the root cause.

I tried everything... I almost wanted to remove my code bit by bit to see which one is causing the issue. Luckily I didn't, it would've been a waste of time. Thank you so much!!!!!

In my case, it works well on ios simulator and android but not on real ios devices. What worked for me in ios was.

npx react-native start --reset-cache --port 8081 in terminal
Shake your ios device
Configure Bundler
Enter IP address from system preferences like the picture below
Add 8081 on the next field and empty on last

Ok I solved this issue "No apps connected. " (on Android Emulator). Please follow this steps (only for Android) :

Open MainApplication.java and remove import com.facebook.react.BuildConfig;
Reset metro bundler cache : npx react-native start --reset-cache
Remove Android assets cache : cd android && ./gradlew clean
Relaunch metro server : npx react-native run-android

And see the magic 🎉
If you have an error like Invariant Violation: Module AppRegistry is not a registered callabel module, scroll on your terminal to see the root cause.

It Works for me

I think that metro shoul be smart enough to open the port redirection through adb as the default connection depends on that

Ok I solved this issue "No apps connected. " (on Android Emulator). Please follow this steps (only for Android) :

Open MainApplication.java and remove import com.facebook.react.BuildConfig;
Reset metro bundler cache : npx react-native start --reset-cache
Remove Android assets cache : cd android && ./gradlew clean
Relaunch metro server : npx react-native run-android

And see the magic 🎉
If you have an error like Invariant Violation: Module AppRegistry is not a registered callabel module, scroll on your terminal to see the root cause.

Thanks you, i search Google in 3 days and you help me. Thanks you so much

El teléfono y la computadora deben estar en la misma conexión WiFi.

I have had the same problem in iOS with React native 0.62 and the solution was it

Experienced this. My device was on a different network than machine running metro.  Don't be me! Run on the same network!

Ok I solved this issue "No apps connected. " (on Android Emulator). Please follow this steps (only for Android) :

Open MainApplication.java and remove import com.facebook.react.BuildConfig;
Reset metro bundler cache : npx react-native start --reset-cache
Remove Android assets cache : cd android && ./gradlew clean
Relaunch metro server : npx react-native run-android

And see the magic 🎉
If you have an error like Invariant Violation: Module AppRegistry is not a registered callabel module, scroll on your terminal to see the root cause.

It's worked!

In my case, it works well on ios simulator and android but not on real ios devices. What worked for me in ios was.

npx react-native start --reset-cache --port 8081 in terminal
Shake your ios device
Configure Bundler
Enter IP address from system preferences like the picture below
Add 8081 on the next field and empty on last

This one worked for me!

Ok, resolvi esse problema "Nenhum aplicativo conectado." (No Android Emulator). Siga estas etapas (apenas para Android) :

Abra MainApplication.java e removaimport com.facebook.react.BuildConfig;
Redefinir o cache do bundler metro: npx react-native start --reset-cache
Remova o cache de ativos do Android: cd android && ./gradlew clean
Reiniciar servidor metro: npx react-native run-android

E veja a magia 🎉
Se você tiver um erro como Invariant Violation: Module AppRegistry is not a registered callabel module, role em seu terminal para ver a causa raiz.

Uoouu ... it worked for me.

Ok I solved this issue "No apps connected. " (on Android Emulator). Please follow this steps (only for Android) :

Open MainApplication.java and remove import com.facebook.react.BuildConfig;
Reset metro bundler cache : npx react-native start --reset-cache
Remove Android assets cache : cd android && ./gradlew clean
Relaunch metro server : npx react-native run-android

And see the magic 🎉
If you have an error like Invariant Violation: Module AppRegistry is not a registered callabel module, scroll on your terminal to see the root cause.

My MainApplication.java file does not have - "import com.facebook.react.BuildConfig;", what to do?? :(

Ok I solved this issue "No apps connected. " (on Android Emulator). Please follow this steps (only for Android) :

Open MainApplication.java and remove import com.facebook.react.BuildConfig;
Reset metro bundler cache : npx react-native start --reset-cache
Remove Android assets cache : cd android && ./gradlew clean
Relaunch metro server : npx react-native run-android

And see the magic 🎉
If you have an error like Invariant Violation: Module AppRegistry is not a registered callabel module, scroll on your terminal to see the root cause.

My MainApplication.java file does not have - "import com.facebook.react.BuildConfig;", what to do?? :(

Ok I solved this issue "No apps connected. " (on Android Emulator). Please follow this steps (only for Android) :

Open MainApplication.java and remove import com.facebook.react.BuildConfig;
Reset metro bundler cache : npx react-native start --reset-cache
Remove Android assets cache : cd android && ./gradlew clean
Relaunch metro server : npx react-native run-android

And see the magic 🎉
If you have an error like Invariant Violation: Module AppRegistry is not a registered callabel module, scroll on your terminal to see the root cause.

My MainApplication.java file does not have - "import com.facebook.react.BuildConfig;", what to do?? :(

Same :(

If you're using USB connection, the most common case is that you don't have the port redirection running. So run:
adb reverse tcp:8081 tcp:8081
adb reverse tcp:8097 tcp:8097 # for flipper

Happens to me too. Worked fine on 0.62.2 and then when I upgraded to 0.63.4 I could not longer get it to work for iPhone. Works fine on android phone and iOS simulator, but not on the iPhone.
I've checked:

The phone and computer are on the same network
The scheme is on the Debug build configuration

While viewing the logs I noticed that the connection from the phone to the laptop was attempted but the connection was refused.
2021-02-09 19:44:18.804771-0500 unit[1076:1041269] Task <5666-0E66-446F-A3F3-1404C54B5955>.<1> finished with error [-1001] Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={_kCFStreamErrorCodeKey=-2102, NSUnderlyingError=0x2817d4300 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <5666-0E66-446F-A3F3-1404C54B5955>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=(     "LocalDataTask <5666-0E66-446F-A3F3-1404C54B5955>.<1>" ), NSLocalizedDescription=The request timed out., NSErrorFailingURLStringKey=http://<IP_ADDRESS>:8081/status, NSErrorFailingURLKey=http://<IP_ADDRESS>:8081/status, _kCFStreamErrorDomainKey=4} 2021-02-09 19:44:18.834182-0500 unit[1076:1041011] [native] Running application main ({     initialProps =     {     };     rootTag = 1; }) 2021-02-09 19:45:19.248767-0500 unit[1076:1041269] Task <48D57837-F00E-47EA-B4CF-6A28376E727>.<2> finished with error [-1001] Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={_kCFStreamErrorCodeKey=-2102, NSUnderlyingError=0x2817ed020 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <48D57837-F00E-47EA-B4CF-6A28376E727>.<2>, _NSURLErrorRelatedURLSessionTaskErrorKey=(     "LocalDataTask <48D57837-F00E-47EA-B4CF-6A28376E727>.<2>" ), NSLocalizedDescription=The request timed out., NSErrorFailingURLStringKey=http://<IP_ADDRESS>:8081/status, NSErrorFailingURLKey=http://<IP_ADDRESS>:8081/status, _kCFStreamErrorDomainKey=4} 2021-02-09 19:45:19.334461-0500 unit[1076:1041270] [connection] nw_socket_handle_socket_event [C3.1:1] Socket SO_ERROR [61: Connection refused] 2021-02-09 19:45:19.335218-0500 unit[1076:1041270] [connection] nw_socket_handle_socket_event [C4.1:1] Socket SO_ERROR [61: Connection refused] 2021-02-09 19:45:19.337833-0500 unit[1076:1041270] [connection] nw_socket_handle_socket_event [C3.2:1] Socket SO_ERROR [61: Connection refused]

Here's my steps to reproduce in a clean project, with a clean install of react-native-cli and react-native. I also cleared my Metro cache.

Run npx react-native init pleasework --version 0.63.4
Open the .xcworkspace
Select your real device
Hit run

Surprisingly, the first build seemed to initially working. After doing a clean build it stopped working. This is of course with the Debug build config and I've even tried some other results from 2018 like disabling the Xcode debugger but that hasn't helped.

Ok, resolvi esse problema "Nenhum aplicativo conectado." (No Android Emulator). Siga estas etapas (apenas para Android) :

Abra MainApplication.java e removaimport com.facebook.react.BuildConfig;
Redefinir o cache do bundler metro: npx react-native start --reset-cache
Remova o cache de ativos do Android: cd android && ./gradlew clean
Reiniciar servidor metro: npx react-native run-android

E veja a magia
Se você tiver um erro como Invariant Violation: Module AppRegistry is not a registered callabel module, role em seu terminal para ver a causa raiz.

This worked for me! Thank you

Ok I solved this issue "No apps connected. " (on Android Emulator). Please follow this steps (only for Android) :

Open MainApplication.java and remove import com.facebook.react.BuildConfig;
Reset metro bundler cache : npx react-native start --reset-cache
Remove Android assets cache : cd android && ./gradlew clean
Relaunch metro server : npx react-native run-android

And see the magic 🎉
If you have an error like Invariant Violation: Module AppRegistry is not a registered callabel module, scroll on your terminal to see the root cause.

My MainApplication.java file does not have - "import com.facebook.react.BuildConfig;", what to do?? :(

Same for me...

Ok I solved this issue "No apps connected. " (on Android Emulator). Please follow this steps (only for Android) :

Open MainApplication.java and remove import com.facebook.react.BuildConfig;
Reset metro bundler cache : npx react-native start --reset-cache
Remove Android assets cache : cd android && ./gradlew clean
Relaunch metro server : npx react-native run-android

And see the magic tada
If you have an error like Invariant Violation: Module AppRegistry is not a registered callabel module, scroll on your terminal to see the root cause.

My MainApplication.java file does not have - "import com.facebook.react.BuildConfig;", what to do?? :(

Same for me...

same...

Hi,
Same issue here.
Both mac and iPhone connected to same network but on reloading metro blunder a warning is show no connected apps.
Xcode 12.4
Mac OS : 10.15.7
iPhone: 14.4.1
Any solution?

Hi, I got the same issue, but the situation is a little different.
I have schemes Debug (default scheme) and copy-of-Debug.
Debug scheme works, but the copy-of-Debug has the error message.
It seems the configuration file is the same as Debug.

hello everyone .... I had the same problem
When i removed  import com.facebook.react.BuildConfig from MainApplication.java and delete cache
Everything was fine

Ok I solved this issue "No apps connected. " (on Android Emulator). Please follow this steps (only for Android) :

Open MainApplication.java and remove import com.facebook.react.BuildConfig;
Reset metro bundler cache : npx react-native start --reset-cache
Remove Android assets cache : cd android && ./gradlew clean
Relaunch metro server : npx react-native run-android

And see the magic tada
If you have an error like Invariant Violation: Module AppRegistry is not a registered callabel module, scroll on your terminal to see the root cause.

My MainApplication.java file does not have - "import com.facebook.react.BuildConfig;", what to do?? :(

Same for me...

same...

same..

Ok I solved this issue "No apps connected. " (on Android Emulator). Please follow this steps (only for Android) :

Open MainApplication.java and remove import com.facebook.react.BuildConfig;
Reset metro bundler cache : npx react-native start --reset-cache
Remove Android assets cache : cd android && ./gradlew clean
Relaunch metro server : npx react-native run-android

And see the magic tada
If you have an error like Invariant Violation: Module AppRegistry is not a registered callabel module, scroll on your terminal to see the root cause.

My MainApplication.java file does not have - "import com.facebook.react.BuildConfig;", what to do?? :(

Same for me...

same...

same..

same... has anyone found a solution for this? (also using an android emulator)

Adding android:usesCleartextTraffic="true" in the Android Manifest File solves it for me. Seems in newer versions of RN or some of its packages this is disabled.
<application       android:name=".MainApplication"       android:label="@string/app_name"       android:icon="@mipmap/ic_launcher"       android:usesCleartextTraffic="true"       ... />

Hi, I got the same issue, but the situation is a little different.
I have configurations Debug (default scheme) and copy-of-Debug.
Debug configuration works, but the copy-of-Debug has the error message.
It seems the configuration file causes it, but I don't find the difference.

In my case I created new targets for our app's different environments and renamed Debug to SIT.
I tried duplicating SIT and renaming it to Debug. App runs both on simulator and Xcode but bundler can't detect the device and thus auto-reload is not working.

I was able to resolve this on iOS when running on a real device. After bundle finishes, press the stop button in Xcode then open and close the app and it works fine.

It worked for me. Thanks al lot !! But its so weird :d

Here is what worked for me:

http://hiddenlinux.blogspot.com/2016/01/how-to-fix-adb-device-offline.html

hello everyone .... I had the same problem in app react-native version 62.0
When i removed import com.facebook.react.BuildConfig from MainApplication.java and delete cache
Everything became normal

How do you fix this? Or have any solution to create multiple environment?

Ok I solved this issue "No apps connected. " (on Android Emulator). Please follow this steps (only for Android) :

Open MainApplication.java and remove import com.facebook.react.BuildConfig;
Reset metro bundler cache : npx react-native start --reset-cache
Remove Android assets cache : cd android && ./gradlew clean
Relaunch metro server : npx react-native run-android

And see the magic tada
If you have an error like Invariant Violation: Module AppRegistry is not a registered callabel module, scroll on your terminal to see the root cause.

My MainApplication.java file does not have - "import com.facebook.react.BuildConfig;", what to do?? :(

Same for me...

same...

same..

same... has anyone found a solution for this? (also using an android emulator)

same for me :<

Adding android:usesCleartextTraffic="true" in the Android Manifest File solves it for me. Seems in newer versions of RN or some of its packages this is disabled.
<application android:name=".MainApplication" android:label="@string/app_name" android:icon="@mipmap/ic_launcher" android:usesCleartextTraffic="true" ... />

This worked for me

Ok I solved this issue "No apps connected. " (on Android Emulator). Please follow this steps (only for Android) :

Open MainApplication.java and remove import com.facebook.react.BuildConfig;
Reset metro bundler cache : npx react-native start --reset-cache
Remove Android assets cache : cd android && ./gradlew clean
Relaunch metro server : npx react-native run-android

And see the magic tada
If you have an error like Invariant Violation: Module AppRegistry is not a registered callabel module, scroll on your terminal to see the root cause.

My MainApplication.java file does not have - "import com.facebook.react.BuildConfig;", what to do?? :(

Same for me...

same...

same..

same... has anyone found a solution for this? (also using an android emulator)

same for me :<

Same !

What did the trick for me was the following:
In Xcode go to Debug/Detach from YourAppName
Then reattach it by going to Debug/Attach to Process, select your app from the list (usually the first entry at the top).

in gradle-wrapper.properties change to distributionUrl=https://services.gradle.org/distributions/gradle-6.3-all.zip
from 5.x

Make sure you're not on a vpn 😅

Ok I solved this issue "No apps connected. " (on Android Emulator). Please follow this steps (only for Android) :

Open MainApplication.java and remove import com.facebook.react.BuildConfig;
Reset metro bundler cache : npx react-native start --reset-cache
Remove Android assets cache : cd android && ./gradlew clean
Relaunch metro server : npx react-native run-android

And see the magic 🎉
If you have an error like Invariant Violation: Module AppRegistry is not a registered callabel module, scroll on your terminal to see the root cause.

This save my job...thankyou very much

Thanks everyone for providing suggestions & work arounds. Closing as there isn't an actionable pull request for this.

I was able to resolve this on iOS when running on a real device. After bundle finishes, press the stop button in Xcode then open and close the app and it works fine.

This solution worked for me

building through xcode, started metro, but will not cannot to metro.

device and laptop are connected to the same wifi
Tried the option of stopping as the soon as the bundle finished but never connected.
Made sure the build configuration was set to "DEBUG" instead of RELEASE.
clear cache, reinstalled pods, watchman watch-del-all, rm -rf /temp/metro-*
cannot believe this is still an issue. Is there a proper fix for this?

Try this:

Open the terminal.
cd into the root directory of your app.
run npm start -- --reset-cache

i solved this issue too
my issue is network problem
and I'm reset the network profile

If you have this code in androidmanifest.xml then remove
android:dataExtractionRules="@xml/data_extraction_rules"
This was auto-gen by the android studio while you clicked ALT+ENTER on the warning (<application.....)

The phone and the computer have to be on the same WiFi connection.

You will not believe... I spent 2 days and could not understand why iPhone didn't want to connect to JS bundler (Android worked).

Try to remove any network_config.xml in debug mode
Android

Had a similar issue but React Native: Emulator stuck on "loading from localhost:8081.."
solution is here https://stackoverflow.com/a/72322750/574475
fixed this by uninstalling watchman. Could be an issue with installing it on M1 or something but it worked immediately after.
brew uninstall watchman


Update data-privacy.md

Added this retention note

🚀 Deployed on https://65831a35b8d6353600d2031f--cozy-fox-0defec.netlify.app


(URGENT) Remove "viewed: xxx" from all normative references

We should remove "viewed: xxx" from all normative references.
This is inappropriate as all normative references are meant to be uniquely identifiable and accessible content. This is different from citing a website where it will change the next day.

CC is inheriting its template from the relaton-render default.
The rule you are proposing of normative references not having viewed dates for URIs is NOT practice in the major style guides, which put viewed dates on every single URI nominated for a resource, as a blanket rule. The "trust me bro, standards bodies will keep their URIs stable" sentiment is not one I am comfortable implementing as default behaviour for relaton-render.
OTOH, Chicago makes an exception for "citations of formally published electronic sources", such as academic articles (which have the same rationale as standards that you give): https://camosun.libguides.com/Chicago-17thEd/onlineArticles . MLA does not make that distinction: https://owl.purdue.edu/owl/research_and_citation/mla_style/mla_formatting_and_style_guide/mla_works_cited_electronic_sources.html and neither does Mouton/De Guyter, who I proofread for.
There is clearly variable practice out there, as Chicago acknowledges, but it is also more common to insert the date accessed universally than not. Rather than get bogged down in yet another argument, I will take the dates accessed out of the default template for articles, monographs, and standards, and I will document in the readme that these may need to be put back in for specific flavours.


[FEATURE REQUEST] find a package's install location

Please confirm these before moving forward

[X] I have searched for my feature proposal and not found a work-in-progress/duplicate/resolved/discarded issue.
[X] This proposal is a completely new feature. If you want to suggest an improvement or an enhancement, please use this template

Describe the new feature
adding this will allow people to be able to open a package's install location without having to search manually.
Describe how this new feature could help users.
sometimes apps do not have a desktop shortcuts and are not in the search menu so they are hard to find and open and you can't change the install location and this would fix this issue.

Duplicate of #1386


Why are all Firebird type constants in Rust SqlType + 1?

I've only been looking at Rust for two days, but I've been dealing with Firebird/Interbase for 20 years.
When trying with the sample sources, I wanted to test the SQLType of the field:
let abd: (u32, u32) = row.cols[0].value.sql_type_and_subtype();
if abd.0 == SQL_INT64
{
println!("Int64 " );
}
This did not work because " abd.0 == SQL_INT64 + 1 " is
Extract from params.rs
impl SqlType {
/// Convert the sql value to interbase format
pub fn sql_type_and_subtype(&self) -> (u32, u32) {
match self {
Text(s) => {
if s.len() > MAX_TEXT_LENGTH {
(ibase::SQL_BLOB + 1, 1)
} else {
(ibase::SQL_TEXT + 1, 0)
}
}
Integer() => (ibase::SQL_INT64 + 1, 0),
Floating() => (ibase::SQL_DOUBLE + 1, 0),
Timestamp() => (ibase::SQL_TIMESTAMP + 1, 0),
Null => (ibase::SQL_TEXT + 1, 0),
Binary() => (ibase::SQL_BLOB + 1, 0),
Boolean(_) => (ibase::SQL_BOOLEAN + 1, 0),
}
}
}
What reason is there to take any original type of Firebird +1 ?
I think the blob subtypes are also swapped.
Excerpt from : https://firebirdsql.org/file/documentation/chunk/en/refdocs/fblangref30/fblangref30-datatypes-bnrytypes.html
3.7.1 BLOB subtypes
The optional SUB_TYPE parameter specifies the nature of data written to the column. Firebird provides two pre-defined subtypes for storing user data:
Subtype 0: BINARY (ibase::SQL_BLOB + 1, ->1<-)
If a subtype is not specified, the specification is assumed to be for untyped data and the default SUB_TYPE 0 is applied. The alias for subtype zero is BINARY. This is the subtype to specify when the data are any form of binary file or stream: images, audio, word-processor files, PDFs and so on.
Subtype 1: TEXT (ibase::SQL_TEXT + 1, ->0<- )
Subtype 1 has an alias, TEXT, which can be used in declarations and definitions. For instance, BLOB SUB_TYPE TEXT. It is a specialised subtype used to store plain text data that is too large to fit into a string type.

What reason is there to take any original type of Firebird +1 ?

Because we perform some "Bitwise AND" operations with the sqltyle. So this sql_type_and_subtype doesn't reflects the exactly firebird type.

I think the blob subtypes are also swapped.

Not exactly. We use the sub_type 0 for raw binary here.
But when we have a text until 32.769 chars, we can send it as a normal varchar(ibase::SQL_TEXT + 1), after that size we send it as a blob sub_type 0(ibase::SQL_BLOB + 1).

For matching the Firebird types, you can use the SqlType enum values:
let abd = row.cols[0];
if abd == SqlType::Integer {
     println!("Int64 " );
}

For matching the Firebird types, you can use the SqlType enum values:
let abd = row.cols[0];
if abd == SqlType::Integer {
     println!("Int64 " );
}

Unfortunately, it doesn't work like that and my attempts to change it myself haven't worked yet either.
But when I am a bit more familiar with RUST, it should be feasible.
That was the reason why I came up with the idea of "if abd.0 == SQL_INT64" in the first place.
Thank you

Didn't work either!
I have tested this and other variants, but only got from one error to the next.

The last bit of the sqltype number is 0 if the column is not nullable, and 1 if the column is nullable.
If you just want to compare with the type, you can use sqltype & (!1) == ibase::SQL_TEXT to set the last bit to 0.


PMID:9303310 missed from

decreased  protein degradation in G1 during vegetative growth

decreased protein degradation during mitotic G1 phase FYPO:0006519
edit file: 624241bb5ea36d807028f32008966c4537678811
release: 0a472de1ef2061633019526ba2aab2df216964fb


How to hide "Cancel" button?

If this method is called:
public void selectProfilePic(){
        Intent pickProfPicIntent = new Intent(this, ImageSelectActivity.class);
        pickProfPicIntent.putExtra(ImageSelectActivity.FLAG_COMPRESS, true);
        pickProfPicIntent.putExtra(ImageSelectActivity.FLAG_CAMERA, true);
        pickProfPicIntent.putExtra(ImageSelectActivity.FLAG_GALLERY, true);
        pickProfPicIntent.putExtra(ImageSelectActivity.FLAG_CROP, true);
        startActivityForResult(pickProfPicIntent, 1213);
    }

A dialog showing "Camera", "Gallery", and "Cancel" appears. Is there a way to hide the "Cancel" button"? I don't need that. Back press is enough.

currently its not possible to hide the cancel button

OK got it.


Can't bind ion-option checked/selected to dynamic property

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/driftyco/ionic-v1)
[ ] 2.x
[x] 3.x
I'm submitting a ...  (check one with "x")
[ ] bug report
[x] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
When I bind the selected ion-option property to a model property, inside a multiple ion-select, and then change it dynamically (like with an exclusive option in a checkbox list) it won't change.
Expected behavior:
Ideally the checked input property would be bind to the model selected property

Hello, thanks for opening an issue with us! Would you be able to provide a plunker that demonstrates this issue? Thanks for using Ionic!

Hello! As it seems it has been a while since there was any activity on this issue i will be closing it for now. Feel free to comment if you are still running into this issue. Thanks for using Ionic!


⚠ SOAP Platform has degraded performance

In 58a55e9, SOAP Platform (https://soap.six-group.com/healthcheck) experienced degraded performance:

HTTP code: 503
Response time: 20460 ms

Resolved: SOAP Platform performance has improved in 6af947a.


Community Fork?

I see a lot of people have currently forked this repository working independently on new feature and keeping it maintained.  What do you guy think of joining forces together and drive this as a community effort?
Tagging everyone how contributed on a fork within the last year:
@cbw @mhollstein @srkaviani @longpaul @n27051538 @baonq-me @root-ali  @wardellc
Please let me know what you think and/or willing to do this as a community.

Very good.
I agree to join this community.

What do you suggest?

I have created the hpilo-exporter github organization and sent you invites. I would suggest that we continue the discussion there.

I'm open to participating. Thanks @roock for driving this!

I have created the hpilo-exporter github organization and sent you invites. I would suggest that we continue the development of this project there and start further discussions there.

Can you be more specific, like which feature or problem should be addressed?

Sadly the exporter is not actively maintained. That's why I'm also willing to help

Can you be more specific, like which feature or problem should be addressed?

The problem I would like to solve is that currently there are 10+ forks of the original repository, all with different features and/or features which have been implemented multiple times independently. I think everyone would benefit if we have one repository which contains all features and is kept uptodate.
I can understand that you have already spend a lot of time to merge some of the changes together, but your repository is lacking some important things like python3 support or automated building of docker image.

Hello, dears!
I have added this to exporter a few years ago:

support for Python 3.6.
ilo_user, ilo_password, ilo_port may be preset via environment.
storage health information from iLO (cache, controller, logical drives, physical drives).
temperature values information from iLO.
per-fan and per-power-supply statuses.
OA info for Blade servers
Server ON status.
Alert rules for Prom
Also I have Grafana Dashboard about, but it is not published to github.

Since this modification it works well on all HPE servers that I have to monitor.
I am not using docker still, so DockerFile is without any mod and not tested.

Here is my dashboard (of course it works with my fork https://github.com/baonq-me/hpilo-exporter)
https://gist.github.com/baonq-me/75f3041fea0e01f74d6a170c53c95a5e

Here is my dashboard (of course, it works with my fork https://github.com/baonq-me/hpilo-exporter) https://gist.github.com/baonq-me/75f3041fea0e01f74d6a170c53c95a5e

Yeah, your Grafana Dashboard looks great, I'm already using it 😄  As you just stated, it works with YOUR fork, I think everyone would benefit from one shared repository where all the improvements are collected and kept uptodate. And which is easy to find and you don't have to look in 5 different forks to get all the features.
Also your Grafana Dashboard contains some hardcoded references (e.g. to datasources and hostnames).

Hello, dears!
I have added this to exporter a few years ago:

support for Python 3.6.
ilo_user, ilo_password, ilo_port may be preset via environment.
storage health information from iLO (cache, controller, logical drives, physical drives).
temperature values information from iLO.
per-fan and per-power-supply statuses.
OA info for Blade servers
Server ON status.
Alert rules for Prom
Also I have Grafana Dashboard about, but it is not published to github.

Since this modification it works well on all HPE servers that I have to monitor. I am not using docker still, so DockerFile is without any mod and not tested.

Yeah, you did a great job with the improvements, I would really like to see them in a shared repository. (Unfortunately it's a bit hard to cherry-pick your changes, since you make more or less complete rewrite 😄

Here is my dashboard (of course, it works with my fork https://github.com/baonq-me/hpilo-exporter) https://gist.github.com/baonq-me/75f3041fea0e01f74d6a170c53c95a5e

Your Grafana Dashboard is very good. but it contains some hardcoded references. for fix this issue please export dashboard with option "Export for sharing externally".
and I suggest to share this dashboard and other future dashboard of this exporter to grafana.com (same as : https://grafana.com/orgs/soroush7339)

Here is my dashboard (of course, it works with my fork https://github.com/baonq-me/hpilo-exporter) https://gist.github.com/baonq-me/75f3041fea0e01f74d6a170c53c95a5e

Your Grafana Dashboard is very good. but it contains some hardcoded references. for fix this issue please export dashboard with option "Export for sharing externally". and I suggest to share this dashboard and other future dashboard of this exporter to grafana.com (same as : https://grafana.com/orgs/soroush7339)

Thanks for your idea. I'll bring the dashboard to grafana.com.

I've started creating a repository with all the combined changes of the different forks including a matching Grafana Dashboard and a working Dockerfile with Python3.
https://github.com/hpilo-exporter/hpilo-exporter

            Hello Roman,You can use everything from my forkand put it into your project if you want. Best Regards,MichaelGesendet mit der mobilen Mail AppAm 06.04.23 um 17:00 schrieb Roman Pertl

                Von: "Roman Pertl"<EMAIL_ADDRESS>6. April 2023An: "infinityworks/hpilo-exporter"<EMAIL_ADDRESS>"mhollstein" ***@***.***>,"Mention"<EMAIL_ADDRESS>[infinityworks/hpilo-exporter] Community Fork? (Issue #21)

I see a lot of people have currently forked this repository working independently on new feature and keeping it maintained.  What do you guy think of joining forces together and drive this as a community effort?
Tagging everyone how contributed on a fork within the last year:
@cbw @mhollstein @srkaviani @longpaul @n27051538 @baonq-me @root-ali  @wardellc
Please let me know what you think and/or willing to do this as a community.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Hi guys,
I am interested to have this exporter, but please help me how to install and make it work properly.
I had installed and run the dcoker as follows:
docker run -p 9416:9416 hpilo-exporter:latest
with result:
CONTAINER ID   IMAGE                     COMMAND                  CREATED        STATUS        PORTS                                       NAMES
8e2472b7bc2d   hpilo-exporter:latest     "hpilo-exporter"         14 hours ago   Up 14 hours   <IP_ADDRESS>:9416->9416/tcp, :::9416->9416/tcp   jovial_archimedes
Starting exporter on: http://<IP_ADDRESS>:9416/metrics
Press Ctrl+C to quit
but when I tried to curl it:
[root@grafaprome ~]# curl -v 'http://<IP_ADDRESS>:9416/metrics?ilo_host=<IP_ADDRESS>&ilo_port=443&ilo_user=administrator&ilo_password=P@ssw0rd!'

About to connect() to <IP_ADDRESS> port 9416 (#0)
Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 9416 (#0)

GET /metrics?ilo_host=<IP_ADDRESS>&ilo_port=443&ilo_user=administrator&ilo_password=P@ssw0rd! HTTP/1.1
User-Agent: curl/7.29.0
Host: <IP_ADDRESS>:9416
Accept: /

Empty reply from server
Connection #0 to host <IP_ADDRESS> left intact
curl: (52) Empty reply from server
[root@grafaprome ~]#

the prometheus yml is as follows:

job_name: 'hpilo-agent'
scrape_interval: 1m
params:
ilo_port: ['443']
ilo_user: ['administrator']
ilo_password: ['P@ssw0rd!']
static_configs:

targets:

'<IP_ADDRESS>

- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
relabel_configs:
- source_labels: [__address__]
  target_label: __param_ilo_host
- source_labels: [__param_ilo_host]
  target_label: ilo_host
- target_label: __address__
  #replacement: <IP_ADDRESS>:8082  # hpilo exporter
  replacement: <IP_ADDRESS>:9416  # hpilo exporter

Did I any missed in configuration?
Please help to make it done well to show it on the dashboard.
Thanks in advance

Hi

Hi guys,
I am interested to have this exporter, but please help me how to install and make it work properly.
I had installed and run the dcoker as follows: docker run -p 9416:9416 hpilo-exporter:latest with result: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 8e2472b7bc2d hpilo-exporter:latest "hpilo-exporter" 14 hours ago Up 14 hours <IP_ADDRESS>:9416->9416/tcp, :::9416->9416/tcp jovial_archimedes
Starting exporter on: http://<IP_ADDRESS>:9416/metrics Press Ctrl+C to quit
but when I tried to curl it: [root@grafaprome ~]# curl -v 'http://<IP_ADDRESS>:9416/metrics?ilo_host=<IP_ADDRESS>&ilo_port=443&ilo_user=administrator&ilo_password=P@ssw0rd!'

About to connect() to <IP_ADDRESS> port 9416 (#0)
Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 9416 (#0)

GET /metrics?ilo_host=<IP_ADDRESS>&ilo_port=443&ilo_user=administrator&ilo_password=P@ssw0rd! HTTP/1.1
User-Agent: curl/7.29.0
Host: <IP_ADDRESS>:9416
Accept: /

Empty reply from server
Connection #0 to host <IP_ADDRESS> left intact
curl: (52) Empty reply from server
[root@grafaprome ~]#

the prometheus yml is as follows:

job_name: 'hpilo-agent'
scrape_interval: 1m
params:
ilo_port: ['443']
ilo_user: ['administrator']
ilo_password: ['P@ssw0rd!']
static_configs:

targets:

'<IP_ADDRESS>

- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
relabel_configs:
- source_labels: [__address__]
  target_label: __param_ilo_host
- source_labels: [__param_ilo_host]
  target_label: ilo_host
- target_label: __address__
  #replacement: <IP_ADDRESS>:8082  # hpilo exporter
  replacement: <IP_ADDRESS>:9416  # hpilo exporter

Did I any missed in configuration? Please help to make it done well to show it on the dashboard.
Thanks in advance

Hi,
this repository is not maintained .
Please use this and if you have any issues you can create issue there:
https://github.com/hpilo-exporter/hpilo-exporter

the dashboard is now does not show the metric, why? how long it will scrap back?


Script supports only one type of plymouth theme

s

Hello, I saw your email, but couldn't really understand the issue. Could you please clarify your problem?

Hello, I saw your email, but couldn't really understand the issue. Could you please clarify your problem?

I'm really sorry for posting this here. I made a mistake and I realized that I don't really know how to delete an issue on github, bacause in years I never done this.
My issue is kinda about your theme. I'm looking for a way to package it to rpm. I'm using Fedora Silverblue based oci and I don't have the access to /usr directory. I can only layer packages via rpm-ostree. I've never packaged an rpm so I don't really know how to do this properly. I meant to post it on a script specifically made for this but it has completely diffrent file structure for plymouth theme and doesn't support a script themes.
tl;dr
I'm really dumb and I tried to make your theme into an rpm, because only that way I can install it

Relax, you are doing fine;)
Unfortunately, Plymouth for now allow only themes located in /lib/plymouth/themes (didn't check that, but community says that it's possible) or /usr/share/plymouth/themes
You could create an issue on gitlab https://gitlab.freedesktop.org/plymouth/plymouth and ask for help. Repo is pretty alive, so there is a solid chance to be answered.


[Feature Request] Improve support for package version

Hi @pattobrien, first excellent job in the package; this looks good!
I might be adding some issues or requests here based on common CLI problems that might fall under the scope of this package.
Problem
Make the auto generation of the CLI version and command more effortless and seamless.
Description
CLIs need to easily check the version. This is used for update checking, compatibility, user support, and so on. Right now, most have to use build_version or a custom script (my case) in order to write the version value from pubspec.
Request

cli_gen should automatically generate a version.g.dart  file based on the pubspec.
@cliRunner should allow for top level options similar to the @cliCommand, so we can have $ cmd --version which is "somewhat" the standard.

The top level arguments its important on the runner as that is the way also we can configfure global arguments for all commands, or log levels like --verbose and so on.

Hey @leoafarias !
I'm excited that you were able to give the package a try, and really appreciate the well thought out feedback! Please keep the issues / feature requests coming, and I'll do my best to get those out the door as quickly as possible! :)
I'll break this issue down into two main features: Built-in support for common args, and handling globally-scoped args.
Built-in Support for Versions
I think it absolutely makes sense to build this functionality directly into cli_gen. I'm wondering if there's any reason you rolled your own tool - just in case there's some use case build_version is missing that I'm not seeing.
Otherwise, to make the UX a little better, it may make the most sense for cli_gen to generate a public version constant in the same (part) file as the Runner so that we don't need to generate an extra version.g.dart file - what do you think?
Top Level Options
I'm breaking this one down in 2 parts: a) option declarations and b) argument handling.
From my look over the fvm repo, from what I can tell, global args are only consumed by the Runner, would you say that's more or less correct?
Proposed Solution(s)
There are a couple good ways we could have users declare and consume global args:

1: create a Runner method for handling globals, via a dedicated annotation (e.g. @cliRun(), @cliEntrypoint, etc)
2: create a Runner method for handling globals, reserving a namespace like runApp() without an annotation
3: allow any Runner, Subcommand or Command class/method to be wrapped by a middleware that handles arg parsing before methods are called (more on this below)

In options 1 & 2, parameter declaring would be done just like how cli_gen currently handles all other parameters, and would generate --verbose and --version flags for the below code:
@cliRunner
class Runner {
  @override
  void runApp({
    bool isVerbose = false,
    bool version = false,
  }) {
   /* ... */
  }
}

Option 3 is far from being shippable, but I've been experimenting with such a DI system on another backend-related project I'm working on in parallel to cli_gen. Essentially it would look something like the following:
@use({
  loggerMiddleware,
  versionMiddleware,
})
@cliRunner
class Runner {
  ...
}

In short, any middleware on a cli_gen annotated class will run before any of the methods on the class can be called. In the examples you gave, this obviously seems like overkill, but on features like authentication or general configuration setup, you can see how integration with a middleware + DI system could be a really nice quality of life improvement!
Suggestion
I think we should move forward with option 2, which would be easiest to implement in the near term and would handle the two use cases you mentioned.
In the future, if/when a DI / middleware system is possible, then I think that would be the most reasonable way to go long-term, as it allows for unlocking more use cases that Option 2 can on its own.

For the version generation, I didn't create a "tool." I have grinder scripts to do specific tasks, so it didn't make sense to have build_runner just for the version generation.
Option 2 makes sense. FYI, this is not a blocker; I got the version by overriding the runCommand and adding the "version" through the argParser like this.
@CliRunner(
  name: packageName,
  description: description,
)
class SuperDeckRunner extends _$SuperDeckRunner<int> {
  SuperDeckRunner() {
    argParser.addFlag('version', abbr: 'v', help: 'Print the version');
  }

  /// Builds the slides configured within the project
  @cliCommand
  Future<int> build({
    @Flag(
      abbr: 'w',
      help: 'Watch for changes to the slides.md file',
      negatable: false,
    )
    bool watch = false,
  }) {
    return buildCommandRunner(watch: watch);
  }

  @override
  Future<int?> runCommand(ArgResults topLevelResults) async {
    if (topLevelResults['version'] == true) {
      logger.info(packageVersion);
      return ExitCode.success.code;
    }
    try {
      return await super.runCommand(topLevelResults);
    } on UsageException catch (e) {
      stdout.writeln('${e.message}\n');
      stdout.writeln(e.usage);
    }
    return null;
  }
}

Also, a CLI tool like FVM might require more work than its worth to fit within the cli_gen. The global variable problem is done through dependency injection of a scope context to make it easier for testing and so on. I think cli_gen can focus on the DX of a CLI but only add a little magic to a lot that is going on.
Middleware might make sense in certain use cases but will probably not resolve the more advanced use cases, and probably it shouldn't.
One last thing: If you are following the macros feature for Dart, it is still being prepared, but it seems it's progressing well. It might be worth following it closely as it might help many of the things you are currently working on.

I got the version by overriding the runCommand and adding the "version" through the argParser like this.

I spent a lot of time designing cli_gen to allow access to the underlying APIs, so that's really assuring to hear!

will probably not resolve the more advanced use cases, and probably it shouldn't.

That's a good point, I hadn't thought of it that way. There's still a good amount of experimentation that I planned to see if such a system would work or not, but your experience holds more weight tbh.

If you are following the macros feature for Dart...

I absolutely have been! The first iteration of this package was actually made with macros a couple weeks ago (as much as could be done at the time). Unless things really change, there should be almost no differences between the current implementation of cli_gen vs. with macros; and this is the reason why Parameter doc comments currently don't work (because its unclear if the same workaround will be doable using macros).

@leoafarias hey Leo! Just to let you know, I just published v0.1.0-dev.6 that includes automatically inferring version values from pubspec.yaml, and automatic generation of a --version command.
I'll close this issue as done! Thanks for filing :)


my.discord.data_export: support ZipPath + some code deduplication

Wanted to benefit from ZipPath instead of unpacking in tmp dir.. hopefully this isn't too hacky!
Checked that this works both ways via hpi query -s my.discord.data_export... (with cache disabled) -- both outputs match :)

Ah sure, could you just add a link to ZipPath in your repo as a comment


Regression in Linux_android_complex_layout_android__compile/debug_full_compile_millis

There appears to be a regression in compile time starting with https://github.com/flutter/flutter/commit/daa051c354d20301b0cc0d5a1ae376c017e77398
Skia perf dashboard:
https://flutter-flutter-perf.skia.org/e/?begin=1631661125&end=1631756523&keys=X97c80be5e525f7cb3d98a33837f14294&num_commits=50&request_type=1&xbaroffset=25834

Tried reproducing this locally but did not notice any change in compilation time during this interval.
The metric on the Skia perf dashboard has been fluctuating between ~40000 and ~50000 for a while.  The current value is back to ~50000, so I don't think this outside the acceptable range.


delete the posts with ipad not possible

From @pixelroot on March 2, 2014 9:43
the symbol for delete is on iPad not visible.
perhaps too far right.
Copied from original issue: friendica/red#349

From @git-marijus on March 3, 2014 10:12
if you mean the symbol to delete items on the wall they are only visible on hover... not sure how this behaves on ipad... on my phone the icon becomes visible if i touch the item once...

From @pixelroot on March 3, 2014 12:0
ah, ok > i test it.

From @pixelroot on March 3, 2014 19:51
no, not visible, impossible.
touch the item once: does not work.
hover is very bad idea for tablets.
:-(

From @pixelroot on March 17, 2014 7:18
I have found that out by accident:
one click on a profile photo in a post aktivate "X" (delete Item).
yes!


Added ExpandIcon widget.

Added a widget that automaitcally rotates the expansion icon and
offers a callback interface that captures presses.

LGTM, but in the future please focus on fixing existing PRs before adding more. You should ideally only be adding more PRs to the queue if your PRs already in the queue are awaiting review.

Can TwoLevelList incorporate this? That would prove its mettle :-)


Conservation of Energy

Dears,
the Parseval's Theorem show that the energy it's conserved in time and frequency domain, right?
I'm using the continuous wavelet transform in a data set but the energy not conserved!
This's a fragment of my code:

escalas = np.linspace(1, 1500, num=3000)
coefs, freq = pywt.cwt(xfast, escalas, 'mexh')
power = (abs(coefs)**2)
sum1 = np.sum(np.sum(xfast**2))
sum2 = np.sum(np.sum(power)

The output  show that sum1 is different sum2! (Incorrecty because the Parserval's Theorem show that sum1 = sum2).
There is a constant normalization of coefficients wavelet array non-explicited?
Thansks for help,
Luciano
PS: Sorry for my english. It isn't very good.
Clique aqui para Responder

The discrete wavelet transforms in PyWavelets are energy preserving, but the continuous wavelet transform is not normalized as you are expecting.  The scaling is the same as in Matlab's cwt (there are unit tests that validate the output of these routines vs. pre-stored output from Matlab).  I think the discussion on scaling in Matlab's documentation near the bottom of the following page should apply:
https://www.mathworks.com/help/wavelet/ref/cwt.html

Hi! Thank's for your answer.
I read in the shared link with the scaling "s" is normalized for the factor "1/sqrt(s)" (L2 norm).
I will introduce this fact em my code.
If energy conservation happens, I'll post it here for other users!

@lucianomagrini
Were you able to get the normalization to work as you expected?  I am going to close this for now as the implementation here seems consistent with the Matlab routine we are testing against.


fix broken image link

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

Could you also fix image link in mdtest.md?


Option to reduce the snap speed

Feature request is related to

[ ] The Vanilla JavaScript version
[ ] The React version
[x] The Embla Carousel core (all versions)
[ ] Documentation website
[ ] Other

Is your feature request related to an issue?
I was formerly on v4.3.0 and jumped up to v4.5.0 to start using the skipSnaps option, but noticed that the carousel snaps to the slide quicker than it did in v4.3.0. It snaps a little too quick for my app.
You can flip between v4.5 and v4.3 and notice the difference
CodeSandbox
Describe the solution you'd like
A way to modify the drag force to feel more like v4.3
Describe alternatives you've considered
Is there a value I could modify from the dangerouslyGetEngine() function?

Hi Sam (@akardet),
Did you try the latest version on a desktop?
Best,
David

Feels different for both desktop and on a touch device.

I think the change in speed for touch devices turned out to be better. But I think we could lower the speed when dragging with a mouse. What’s your thoughts about this suggestion?

I won't make too much of a fuss about it if no one else has any strong opinions about it. It still functions great. Thanks for the reply.

@akardet maybe some users prefer the previous speed (4.3.x and down). Let's see if this gets any traction. I'll take a look at this next week and maybe I'll lower the speed.

Hi Sam (@akardet),
I've decided to slightly reduce the snap speed (not as much as it was before the v4.5.0 release though). I can't tell when but I'll let you know when I've had time to release it.
Best,
David

Hello Sam (@akardet),
I've just released v4.5.1 with a reduction of snap speed when dragging. Enjoy!
Best,
David

Hey David,
Finally got around to upgrading and testing out 4.5.1 and it's feeling great. Thank you for all your hard work!

Is it possible to have this be customizable? That would be a great feature add!

Hi Paul (@pm0u),
Thank you for your question. Have you read the announcement?
Cheers,
David

Is it possible to have this be customizable? That would be a great feature add!

I second this :)


Fix incorrect KMap injections, received from the LLVM library

This is a temporary fix for #321 until properly addressed upstream by https://github.com/runtimeverification/llvm-backend/issues/886 . The fix involves manually adjusting an injection to the correct sort, since we know the sort of the argument for a given symbol from the KoreDefintion, passed to the decoder.

I've confirmed that with the latest k version, removing our injection fix works for the unit test we originally added to test this behaviour. Do we want to revert the injection fix or leave it in case someone still uses an old version of the llvm-backend?


My plugin is not compatible with luckperms??

My users can do /godmode which is part of my plugin and I can not disable it with luckperms. Please help and thank you.

https://luckperms.net/wiki/Verbose

https://luckperms.net/wiki/Verbose


Support for update collections

Fixes #69
You can run it with:
go run ./cli collection update a79983a1-edf5-4a37-affb-2254aecba1a8 --name "Test Outline API Backup Update" --key [KEY] --server [SERVER]

[!NOTE]
It seems you can only update collections where you have the permission to update.
So we can't update our existing "test cli" collections.
To test it, better first create your own collection and update it afterwards ❗
In case you update an collection where you don't have permission to update, you get the following error message:

{clientErr:{"ok":false,"error":"authentication_required","status":401,"message":"Invalid API key"} serverErr: status:401

To test:

Create a new collection:

go run ./cli collection create "New Collection" --key [KEY] --server [SERVER]

The response contains the collection id:
{
  "id": "[ID_HERE]",
  "name": "New Collection",
  "description": "",
  "sort": {
    "direction": "asc",
    "field": "index"
  },
  "index": "    P",
  "color": "#42DED1",
  "icon": "",
  "permission": "",
  "createdAt": "2024-02-06T07:17:24.658Z",
  "updatedAt": "2024-02-06T07:17:24.658Z",
  "deletedAt": "0001-01-01T00:00:00Z"
}

Use the id from the newly created collection to update it

go run ./cli collection update [ID_HERE] --permission-read-write --name "Test Outline API Backup Update" --key [KEY] --server [SERVER]

Response should be something like this:
{
  "id": "[ID_HERE]",
  "name": "Test Outline API Backup Update", // Notice the new name!
  "description": "",
  "sort": {
    "direction": "asc",
    "field": "index"
  },
  "index": "    P",
  "color": "#42DED1",
  "icon": "",
  "permission": "read_write", // Notice the new permission
  "createdAt": "2024-02-06T07:17:24.658Z",
  "updatedAt": "2024-02-06T07:17:42.914Z",
  "deletedAt": "0001-01-01T00:00:00Z"
}

@rsjethani could you please have a look on this 🙃

@rsjethani can you also check if the cli works for you? As mentioned in the description 🙏

@rsjethani I tested it again by creating a new collection first. This time it worked as expected 🎉
Checkout the updated PR description 🚀


Running blonide multiple times results in filename collision

Minimal example:
use std::process::Command;

fn main() {
    let handle = std::thread::spawn(|| {
        let mut cmd = Command::new("ping");
        cmd.arg("localhost");
        let _ctx = blondie::trace_command(cmd, false).unwrap();
    });

    let mut cmd = Command::new("ping");
    cmd.arg("localhost");
    let _ctx = blondie::trace_command(cmd, false).unwrap();

    handle.join().unwrap();
}

Output
$ cargo run
    Blocking waiting for file lock on build directory
   Compiling ring v0.17.8
   Compiling rustls v0.21.12
   Compiling sct v0.7.1
   Compiling rustls-webpki v0.101.7
   Compiling tokio-rustls v0.24.1
   Compiling hyper-rustls v0.24.2
   Compiling reqwest v0.11.27
   Compiling symsrv v0.2.0
   Compiling blondie v0.5.2
   Compiling blondie-test v0.1.0 (D:\Projects\blondie-test)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 9.69s
     Running `target\debug\blondie-test.exe`
thread 'main' panicked at src/main.rs:12:51:
called `Result::unwrap()` on an `Err` value: Other(WIN32_ERROR(183), "Cannot create a file when that file already exists.\r\n", "StartTraceA")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: process didn't exit successfully: `target\debug\blondie-test.exe` (exit code: 101)

StartTraceA is what's returning error code 183 (File already exists). From the docs, this means:
ERROR_ALREADY_EXISTS

A session with the same name or GUID is already running.

We are using a session name, specifically KERNEL_LOGGER_NAME  There's a comment that explains why we use it:

    // Build the trace properties, we want EVENT_TRACE_FLAG_PROFILE for the "SampledProfile" event
    // https://docs.microsoft.com/en-us/windows/win32/etw/sampledprofile
    // In https://docs.microsoft.com/en-us/windows/win32/etw/event-tracing-mof-classes that event is listed as a "kernel event"
    // And https://docs.microsoft.com/en-us/windows/win32/etw/nt-kernel-logger-constants says
    // "The NT Kernel Logger session is the only session that can accept events from kernel event providers."
    // Therefore we must use GUID SystemTraceControlGuid/KERNEL_LOGGER_NAME as the session

Brieefly thinking about it, maybe we could store the session globally somewhere with refcounting to know when to close it. And then we'd need to modify the event_record_callback since it currently ignores all events except the ones for the target process, probably with some global array of process ids to filter. And then somehow correectly route the results to each trace.
The global session check would be around here and the event filtering here

Seems like Block until processing thread is done for a specific process would have to be different if the session continues

Where does the const EVENT_TRACE_TYPE_LOAD: u8 = 10; magic opcode number come from?


2.0-wip: FEATURE REQUEST: Replace raster Glyphicons with vector Iconic icons

I think, vector Iconic icons packed into a font would be more useful than raster Glyphicons in single black color.
This is how it looks like:
http://habrastorage.org/storage2/fb6/957/f0e/fb6957f0ee02753c0276e44db980ab7c.png
These icons also look nice in headers, like h2:
http://habrastorage.org/storage2/d10/8bf/2cc/d108bf2cca9a06b0444c48401d357101.png
If you are going to implement this thing in Bootstrap, some conflicts need to be resolved this way:

.info:before {
    content: '';
}
.iconic .info:before {
    content: '\2139';
}

Iconic icon set:
http://somerandomdude.com/work/iconic/

We won't be using Iconic. It's a fine set of icons, but not in the style I want to use with Bootstrap. Feel free to use it yourself though.


Aqua integration

This PR includes all the changes required to integrate aqua with paladin ( focused only on image vulnerability scan data)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Chore (no code changes)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] This change requires a documentation update

How Has This Been Tested?

[X] Installer changes tested by running the installer and verified the new resources needs to be created
[X] Code changes are tested by running the Data collector jobs and policies

Checklist:

[X] My code follows the style guidelines of this project
[X] My commit message/PR follows the contribution guidelines of this project
[X] I have performed a self-review of my code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes

Other information:
In progress will update soon

lets clean the smells next time.


Smart selectors - ability to pin selected elements

Specifically, found repositories but also about every other search autocomplete,

Steps to replicate please.

This is really a comment on the inability to pin something just searched for on various autocompletes.  I was just looking for a pin icon.  The lock icon seems to allow a short term carry over of the selected items, but it would maybe be nice to be able to pin more than one thing.

@jrflood I understand now.  This is a good idea.

recent tab keep track of last uses of the search. Do we still need this functionality?

I think we can close for specific suggestsions of places to add the Pin icon.


Adding interpolation choice for line charts

@akuhn , it's so easy to add a chart option now! I like how form_data is just available in the js


最新版 0.14.1编译没问题，但是当我运行时报错，win11

error[E0587]: type has conflicting packed and align representation hints
--> D:\workbench\rust\ffmpeg-test\target\debug\build\rusty_ffmpeg-74b7e75f9a2f9582\out/binding.rs:2013:1
|
2013 | pub union __mingw_ldbl_type_t {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Related issue: https://github.com/pgcentralfoundation/pgrx/issues/1132
It seems that bindgen doesn't generate bindings for MinGW types correctly. Are you using mingw toolchain? Please link some environment information in issue description(build args etc). It would be helpful if I can reproduce it on my own machine.

ok,It is indeed a MinGW problem,so i remove it


CRDs in Helm Chart Contain Status

What happened?
We use a GitOps approach to deploy Crossplane: We render the Helm chart and commit the rendered manifests to git. From there it will be applied by ArgoCD on the cluster.
Since the CRDs in the chart contain the status field, ArgoCD always sees changes from the version currently applied in the cluster and the version the GitOps repo (rendered Helm chart).
How can we reproduce it?
The rendered Helm chart includes the CRDs with the status filed set.
What environment did it happen in?
Crossplane version: v0.6.0

Suggested Solution
Remove the status field from all CRDs in the Helm chart. I tried to come up with a PR myself, but I'm not sure if the CRDs in the Helm chart are somehow copied there or if I can just modify them?

@srueg thanks for opening this! This the empty status fields are actually a product of the generation from controller-tools. I noticed a comment regarding this situation here indicating that these fields must be explicitly be set to their zero-values due to missing omitempty tags, but I am not sure it is still accurate. I will investigate and see if I can drive a fix upstream.

Thanks for looking into it :+1:
In the meantime I found a workaround by ignoring the status field of CRDs in ArgoCD.

I also observed a similar issue with the .spec.scope field of the CRDs: The manifests in the Helm chart specify scope: '' (empty string) while once applied to the cluster it gets defaulted to scope: Namespaced.

For anyone coming across this. The workaround looks like this (in the argo-cm ConfigMap):
data:
  resource.customizations: |
    apiextensions.k8s.io/CustomResourceDefinition:
      ignoreDifferences: |
        jsonPointers:
          - /status
          - /spec/scope

The manifests in the Helm chart specify scope: '' (empty string) while once applied to the cluster it gets defaulted to scope: Namespaced.

This appears to be corrected in 6e0954d992492dd2836d06e3b2d0395b60071567 which should be included in the next (0.7.0) release.


improve tunnel availability

What type of PR is this?
/kind bug
What this PR does / why we need it:

before this pr, all csr(pending/approved/other status) will try enqueue every 10 seconds, but the default queue is only 10qps, 100 bucket. tunnel-server is not able to approve csr when large number of csr comes.
the connection is not available before certificate signed, so tunnel-agent must wait for the certificate signed

Which issue(s) this PR fixes:

None
Special notes for your reviewer:

/assign @rambohe-ch
Does this PR introduce a user-facing change?

None

other Note

/assign @fei-guo

/lgtm

/lgtm

@Fei-Guo If you have not any other comments, i'd like to approve this pr.

/approve
/lgtm


Error on operator with explicit type argument

An infix operator with an explicit type argument causes the following error:
[error] .../GenericOperator.scala: Expected token SEMI but got Token(LBRACKET,[,83,[)

The code is this (the problem is at the C() ?[Int] 7 expression):
object GenericOperator {

  case class C() {
    def ?[A](a: A): A = a
  }

  C() ?[Int] 7
}

This is possibly caused by  daniel-trinh/scalariform/issues/111.

Which version of scalastyle are you using? And which version of scala?

scalastyle-sbt-plugin 0.7.0
Scalastyle 0.7.0
Scala 2.11.7

Update: I tried with Scalastyle 0.8.0, and I got the same error.

This is due to a bug in the scalariform parser that we use. For now, you can use the workaround, but I agree that it isn't nice. https://github.com/scala-ide/scalariform/issues/217
Also linked to #195, #191.


[Bug]: Render when slides are wider than view size

Hi David,
Thanks for a great library. You efforts are much appreciated.
This PR addresses an issue I ran into - when the first slide is wider than the view size, an exception is thrown. This happens because of an underlying assumption when creating scroll groups by size (see test case).
Happy to make additional changes if any suggestions.

@tolu-fuelled thanks a lot for your contribution ✨! I will check this out as soon as possible.
One thing I noticed (that isn’t easy to know): We can get rid of the last commit with the patch version bumps on this bug fix branch, because this will be done automatically on the main branch by running yarn version:patch - which automatically creates a release and pushes it to the remote. The next patch version 8.0.1 will include several bug fixes.
Thanks a lot and I’ll let you know when I’ve reviewed this.
Best,
David

This is awesome, thanks for the fix @tolu-fuelled I have been waiting for this for long time. @davidjerleke When can we expect this to be officially released?

@suriyaprakash-s I can never give time estimates because I work on this library on my unpaid spare time.
However, reviewing this PR is next up after a minor release with some other bug fixes that has higher priority.

@davidjerleke made the requested changes and added a few more tests.
The RTL snaps don't add up to me if you don't mind giving it a second look. I ran the react playground - the slides render left to right but they move right to left. So slides render [1, 2, 3, 4, 5] but move [1, empty, empty, empty, empty]. I'm probably missing something.

@davidjerleke made the requested changes and added a few more tests.

Thanks! It looks great 👍.

The RTL snaps don't add up to me if you don't mind giving it a second look. I ran the react playground - the slides render left to right but they move right to left. So slides render [1, 2, 3, 4, 5] but move [1, empty, empty, empty, empty]. I'm probably missing something.

@tolu-fuelled you've set the direction option to 'rtl' but my guess would be that you've forgot to set the content direction to RTL too, because Embla respects the native browser direction and doesn't shift around your slides to achieve a RTL carousel. From the docs:

[!NOTE]
Note: When using rtl, the content direction also has to be set to RTL, either by using the HTML dir attribute or the CSS direction property.

Could that be the case?
Best,
David

@davidjerleke that’s exactly it.
El 9 abr 2024, a la(s) 00:57, David Jerleke @.***> escribió:

@davidjerlekehttps://github.com/davidjerleke made the requested changes and added a few more tests.
Thanks! It looks great 👍.
The RTL snaps don't add up to me if you don't mind giving it a second look. I ran the react playground - the slides render left to right but they move right to left. So slides render [1, 2, 3, 4, 5] but move [1, empty, empty, empty, empty]. I'm probably missing something.
@tolu-fuelledhttps://github.com/tolu-fuelled you've set the direction optionhttps://www.embla-carousel.com/api/options/#direction to 'rtl' but my guess would be that you've forgot to set the content direction to RTL too, because Embla respects the native browser direction and doesn't shift around your slides to achieve a RTL carousel. From the docshttps://www.embla-carousel.com/api/options/#direction:
Note
Note: When using rtl, the content direction also has to be set to RTL, either by using the HTML dir attributehttps://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/dir or the CSS directionhttps://developer.mozilla.org/en-US/docs/Web/CSS/direction property.
Could that be the case?
Best,
David
—
Reply to this email directly, view it on GitHubhttps://github.com/davidjerleke/embla-carousel/pull/805#issuecomment-2044273234, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A54BW2VDYTMGCB554A73JLLY4OGLZAVCNFSM6AAAAABFIEKMHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBUGI3TGMRTGQ.
You are receiving this because you were mentioned.Message ID: @.***>

@tolu-fuelled great work! Thanks for solving this problem and stabilizing Embla with relevant tests. It will prevent the bug from reoccuring in the future 👍.

@tolu-fuelled this has been released in v8.0.2.


tests plugin

Tasks

[x] pinned main
[x] tests
[x] release
[x] readme documentation
[x] dev documentation

Required for

[x] NR
[x] MOSBRI

@mesemus @SilvyPuzzlewell can we close this issue?