Typescript

2 'bugs' might have been fixed btw
Platforms affected
What does this PR do?
What testing has been done on this change?
Tested features checklist

[ ] Default setup (example)
[ ] Carousels with and without momentum enabled (prop enableMomentum)
[ ] Vertical carousels (prop vertical)
[ ] Slide alignment (prop activeSlideAlignment)
[ ] Autoplay (prop autoplay)
[ ] Loop mode (prop loop)
[ ] ScrollView/FlatList carousels (prop useScrollView)
[ ] Callback methods
[ ] ParallaxImage component
[ ] Pagination component
[ ] Layouts and custom interpolations

@Titozzz This is looking great, kudos to you 👍
The only issue is that some of the code styling rules you've used are absolute no-go's for us — the rules we use are opinionated and enforced company-wide.
Particularly:

4 spaces for indentation.
Space required before methods' parenthesis.
Ternaries are written this way:

let nextActiveItem =
    typeof this._activeItem !== 'undefined' ?
        this._activeItem :
        nextFirstItem;

Apart from that, excellent job so far!
Can you tell me why you've removed the eslint file?

I just aligned the repo to the default config from eslint community. No problem, I'll update it back

I tried reverting to your config + adding some typescript defaults. Lemme know if that need any more changes

I've made sure the example works, let me know if I need to test more

@Titozzz Amazing work, thank you so much 🙏
I'll set aside some time this weekend to review it in length. Anything particular I should know about using https://github.com/react-native-community/bob?

Nope it's just used in the prépare phase to build the code

@Titozzz @bd-arc TypeScript looks fine to me. add a few suggestions. Please take look and share your thoughts.

@Titozzz Just went over the whole PR and, as far as I can tell, you've done an astounding job! Thank you so much 🙏
Let me know once you're done with the really minor corrections and then... Let's get this merged!
PS — Thanks a lot @narender2031 for your thorough review 🙂

Hey guys,
I would like to test this. Currently I have "react-native-snap-carousel": "4.0.0-beta.5" on my package.json. What should I do to test this PR?
Thank you

@nelsonprsousa You can target any commit of the repo with its SHA.
Here's an example with this PR's current latest commit:
"react-native-snap-carousel": "https://github.com/archriss/react-native-snap-carousel#e719467"

I tried it, but got this error:

I am sure I am missing something here 🤔

I tried it, but got this error:

I am sure I am missing something here 🤔

Please try cloning it from my fork

Please try cloning it from my fork

Seems to work with your fork. However, once I yarn I get this error:

Here's my package.json: https://gist.github.com/nelsonprsousa/61ef81bdddc0823bb9ec793924d4c22b
Do you know if this is a local related problem?

@nelsonprsousa Fixed it, thanks :)
I uploaded a packed version if you want to try it out just download and you can add it with yarn add "path"
https://github.com/Titozzz/files/blob/master/react-native-snap-carousel-v4.0.0-beta.5.tgz
@bd-arc @narender2031 fixes are done, can't do many tests as I don't have a good connection here, but should be just fine.
Please test 🚀

@nelsonprsousa Fixed it, thanks :)
I uploaded a packed version if you want to try it out just download and you can add it with yarn add "path"
https://github.com/Titozzz/files/blob/master/react-native-snap-carousel-v4.0.0-beta.5.tgz
@bd-arc @narender2031 fixes are done, can't do many tests as I don't have a good connection here, but should be just fine.
Please test 🚀

Now I could add it 👍
Already tested our application with this version and it is working as expected. 🚀  We are using the Carousel and Pagination, too.
I was also expecting to have types with the migration to TypeScript. Am I missing something here? Maybe we need to do something else?

Nevertheless the runtime app looks 👌

Thanks for testing, I fcked up the path to the d.ts file 🙄 , now it is fixed @nelsonprsousa

Thanks for testing, I fcked up the path to the d.ts file 🙄 , now it is fixed @nelsonprsousa
Feel free to edit the package.json if you don't wanna reinstall 😛

Types are now working 👌
Just find it hard to compile it without any error 😅
This is my code:
const renderItem = (baseData: {
    index: number;
    dataIndex: number;
    item: IPointOfSale;
}): ReactNode => (
    <Card
        title={baseData.item.title}
        subtitle={baseData.item.subtitle}
        imagePath={baseData.item.imagePath}
        width={96}
        height={25}
        onPress={navigate(navigation, baseData.item.navigation)}
    />
);

<Carousel
    ref={carouselRef}
    data={pointsOfSale}
    renderItem={renderItem}
    onScrollIndexChanged={setActiveSlide}
    sliderWidth={theme.mixins.width}
    itemWidth={theme.mixins.width}
    hasParallaxImages
    containerCustomStyle={{
        overflow: 'visible',
        marginLeft: theme.mixins.widthPercentageToDP(2),
    }}
    inactiveSlideScale={0.65}
    inactiveSlideOpacity={0.35}
/>

But I am getting this:
Type '{ ref: MutableRefObject<null>; data: IPointOfSale[]; renderItem: (baseData: { index: number; dataIndex: number; item: any; }) => ReactNode; onScrollIndexChanged: Dispatch<...>; ... 5 more ...; inactiveSlideOpacity: number; }' is not assignable to type '(IntrinsicAttributes & IntrinsicClassAttributes<Carousel<unknown>> & Pick<Readonly<CarouselBaseProps<unknown> & VerticalCarouselProps & Pick<...>> & Readonly<...>, "onTouchStart" | ... 19 more ... | "children"> & Partial<...> & Partial<...>) | (IntrinsicAttributes & ... 3 more ... & Partial<...>)'. Type '{ ref: MutableRefObject<null>; data: IPointOfSale[]; renderItem: (baseData: { index: number; dataIndex: number; item: any; }) => ReactNode; onScrollIndexChanged: Dispatch<...>; ... 5 more ...; inactiveSlideOpacity: number; }' is not assignable to type '(IntrinsicAttributes & IntrinsicClassAttributes<Carousel<unknown>> & Pick<Readonly<CarouselBaseProps<unknown> & VerticalCarouselProps & Pick<...>> & Readonly<...>, "onTouchStart" | ... 19 more ... | "children"> & Partial<...> & Partial<...>) | (IntrinsicAttributes & ... 3 more ... & Partial<...>)'.
Maybe the problem is the item's type? 🤔

I'll do some tests and come back at you

I've had to make a few key changes to make sure types would be as close to reality as they needed to be.
Most library don't bother doing this but it will make the user experience better.
We could have typed the carousel like that:
{
  vertical?: boolean,
  height?: number,
  width?: number,
}

That's the easy way.
Instead I've gone
{
  vertical: false,
  width: number
} | {
  vertical: true,
  height: number,
}

Which is more accurate, and doesn't allow for user error.
The drawback is now that when using TypeScript you need to specify vertical={false} (or true) explicitly.
I've tried for a long time to make it default to horizontal so that user would have the horizontal types when not specifying but that is just not possible with the current TS version.
Note that this doesn't impact the JS users, and is not a breaking change for them. Only TS users will see a difference.
I've also removed the hasParallaxImages prop, and I'm now always passing a second argument, this has no perf impact, and vastly simplified the types. Now the function renderItem is properly typed depending on vertical.
There are plenty of things I'd like to go over but this PR has waited enough and code is working fine as is.
Unless anyone comments otherwise, has bugs, this is READY TO MERGE @bd-arc

This is superb! I'll do a few more tests and will most certainly merge and publish your PR tomorrow.
Thank you for your awesome job on this one @Titozzz 👍

Can't wait to get some feedbacks on this. I'm playing with reanimated 2 right now

Can't wait to get some feedbacks on this. I'm playing with reanimated 2 right now

@Titozzz Merged and published!
Two observations:

The code styling you've used is pretty far from what we enforce in the company and what is defined in the .eslintrc file (I've just updated it by the way). For some reason, I can no longer get ESLint to work and autofix as much of it as possible. Better luck on your end?
Nice to hear about Reanimated 2. The plugin could really use an addition like this one further down the road ;-)

@bd-arc Any way we can chat, other that using github issues ? :)

https://github.com/archriss/react-native-snap-carousel/pull/750 for 1)

I noticed that the Carousel component is missing some props from "InheritedPropsFromFlatlist", namely extraData which I required on my component when the size changes (lets say a photo finishes uploading).
Should I make a separate ticket for that?

@Titozzz
I was looking at this again. Few things:

Why are we using a "type" for CarouselProps instead of "interface"? I can't extend from CarouselProps to create other interfaces because it is not a static type. I believe in the @types version it was an interface.
Why are optional props listed as "required". My guess is that that type is used internally in the library but most of those values are defaulted by the library. To the user, they should all be optional.
renderItem requires "parallaxData" as the second argument but I don't believe it's required by the library to work.

Is there another way I should be looking at getting typescript support for 4.0.0-beta?

@Aryk Thanks for the feedback! @Titozzz did an amazing job migrating everything to TypeScript, but we know that a few things probably need some fine-tuning.
You're more than welcome to update the Typescript definition and submit a PR if you feel like it. Just make sure to ping me when you do so or I'm probably going to miss it.

There is definitely a big need for polishing. I'll try fixing this in the next weeks


Revert to direct to Helium miner for now.

Issue

Link:
Summary:

How

Screenshots

References

Checklist

[ ] Tests added
[ ] Cleaned up commit history (rebase!)
[ ] Documentation added
[ ] Thought about variable and method names

@robputt what's the purpose of this? Something not working?

Apparently after some time hotspots stop forwarding packets from the multiplexer to the helium miner and they just blat out UDP error to the log. I am investigating but for now reverting. I think it hasn't been seen on my dev device because it doesn't stay online long enough without code pushes to see these affects. I'll try and get a fix in and deployed to the dev device before the weekend as I am away and then see if it's in this state when I get back :-).

Oh ok, interesting. I did notice something similar but didn't realise it was all packets falling.
By the way, does the port need to change to something different?

1680 isn't it @robputt ?

Oh ok, interesting. I did notice something similar but didn't realise it was all packets falling.
By the way, does the port need to change to something different?

Nah port is unrelated.


Fixup for latest rosbridge, add Log

Hi there,
I'm an engineer at Microsoft leading the effort to enable ROS1 on Windows. For a demo, we're using the UWP ROS Bridge, and made some updates. This change enables fixes up some things and adds logging

Looks great, thanks!


AAR for MediaPipe Face Detection failed.

Hello, I was trying to build AAR file for learning/my project so I followed this link and it failed and has error
https://google.github.io/mediapipe/getting_started/android_archive_library.html
I checked other issues saw protobuf patches but already in there (0.8.3-2) then I looked for that other issues but didn't see something similar.
bazelisk build -c opt --host_crosstool_top=@bazel_tools//tools/cpp:toolchain --fat_apk_cpu=arm64-v8a,armeabi-v7a --strip=ALWAYS mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar

DEBUG: Rule 'rules_foreign_cc' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "c2cdcf55ffaf49366725639e45dedd449b8c3fe22b54e31625eb80ce3a240f1e"
DEBUG: Repository rules_foreign_cc instantiated at:
  /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/WORKSPACE:42:13: in <toplevel>
Repository rule http_archive defined at:
  /home/thunderbirdtr/.cache/bazel/_bazel_thunderbirdtr/47aecfbb39c3d4019351abcfc511078c/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in <toplevel>
DEBUG: /home/thunderbirdtr/.cache/bazel/_bazel_thunderbirdtr/47aecfbb39c3d4019351abcfc511078c/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /home/thunderbirdtr/.cache/bazel/_bazel_thunderbirdtr/47aecfbb39c3d4019351abcfc511078c/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /home/thunderbirdtr/.cache/bazel/_bazel_thunderbirdtr/47aecfbb39c3d4019351abcfc511078c/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /home/thunderbirdtr/.cache/bazel/_bazel_thunderbirdtr/47aecfbb39c3d4019351abcfc511078c/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /home/thunderbirdtr/.cache/bazel/_bazel_thunderbirdtr/47aecfbb39c3d4019351abcfc511078c/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'rules_cc' because it already exists.
DEBUG: /home/thunderbirdtr/.cache/bazel/_bazel_thunderbirdtr/47aecfbb39c3d4019351abcfc511078c/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /home/thunderbirdtr/.cache/bazel/_bazel_thunderbirdtr/47aecfbb39c3d4019351abcfc511078c/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /home/thunderbirdtr/.cache/bazel/_bazel_thunderbirdtr/47aecfbb39c3d4019351abcfc511078c/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /home/thunderbirdtr/.cache/bazel/_bazel_thunderbirdtr/47aecfbb39c3d4019351abcfc511078c/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'bazel_skylib' because it already exists.
DEBUG: /home/thunderbirdtr/.cache/bazel/_bazel_thunderbirdtr/47aecfbb39c3d4019351abcfc511078c/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'pybind11' because it already exists.
INFO: Build options --cpu, --crosstool_top, --fat_apk_cpu, and 2 more have changed, discarding analysis cache.
DEBUG: Rule 'rules_cc' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "66af5b045d30b49a61faaf063ba5da7e47b9b393e3d64b40035f66ec1ade8f34"
DEBUG: Repository rules_cc instantiated at:
  /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/WORKSPACE:36:13: in <toplevel>
Repository rule http_archive defined at:
  /home/thunderbirdtr/.cache/bazel/_bazel_thunderbirdtr/47aecfbb39c3d4019351abcfc511078c/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in <toplevel>
WARNING: API level 30 specified by android_ndk_repository 'androidndk' is not available. Using latest known API level 29
DEBUG: Rule 'android_opencv' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "cdb0e190c3734edd4052a3535d9e4310af912a9f70a421b1621711942a1028d5"
DEBUG: Repository android_opencv instantiated at:
  /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/WORKSPACE:224:13: in <toplevel>
Repository rule http_archive defined at:
  /home/thunderbirdtr/.cache/bazel/_bazel_thunderbirdtr/47aecfbb39c3d4019351abcfc511078c/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in <toplevel>
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/components:AudioDataConsumer.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/components:AudioDataProcessor.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/components:AudioDataProducer.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/components:CameraHelper.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/components:CameraXPreviewHelper.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/components:ExternalTextureConverter.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/components:FrameProcessor.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/components:MicrophoneHelper.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/components:PermissionHelper.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/components:TextureFrameConsumer.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/components:TextureFrameProcessor.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/components:TextureFrameProducer.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:AndroidAssetUtil.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:AndroidPacketCreator.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:AndroidPacketGetter.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:AppTextureFrame.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:AssetCache.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:AssetCacheDbHelper.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:Compat.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:GlSyncToken.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:Graph.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:GraphGlSyncToken.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:GraphProfiler.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:GraphService.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:GraphTextureFrame.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:MediaPipeException.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:MediaPipeRunner.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:Packet.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:PacketCallback.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:PacketCreator.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:PacketGetter.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:PacketListCallback.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:PacketWithHeaderCallback.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:ProtoUtil.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:SurfaceOutput.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:TextureFrame.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:TextureReleaseCallback.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:TypeNameRegistry.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/framework:TypeNameRegistryLite.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/glutil:CommonShaders.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/glutil:EglManager.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/glutil:ExternalTextureRenderer.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/glutil:GlThread.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/glutil:ShaderUtil.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/thunderbirdtr/Projects/MpProjects/mediapipe-<IP_ADDRESS>/mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar/BUILD:3:14: in srcs attribute of android_library rule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_android_lib: please do not import '//mediapipe/java/com/google/mediapipe/glutil:TextureRenderer.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
INFO: Analyzed target //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar (0 packages loaded, 17819 targets configured).
INFO: Found 1 target...
INFO: From Executing genrule //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar_aar_manifest_generator:
/bin/bash: line 10: warning: here-document at line 2 delimited by end-of-file (wanted `EOF')
INFO: From Compiling com_google_protobuf/src/google/protobuf/message_lite.cc [for host]:
In file included from /usr/include/string.h:519,
                 from external/com_google_protobuf/src/google/protobuf/stubs/port.h:39,
                 from external/com_google_protobuf/src/google/protobuf/stubs/common.h:46,
                 from external/com_google_protobuf/src/google/protobuf/message_lite.h:45,
                 from external/com_google_protobuf/src/google/protobuf/message_lite.cc:36:
In function 'void* memcpy(void*, const void*, size_t)',
    inlined from 'google::protobuf::uint8* google::protobuf::io::EpsCopyOutputStream::WriteRaw(const void*, int, google::protobuf::uint8*)' at external/com_google_protobuf/src/google/protobuf/io/coded_stream.h:699:16,
    inlined from 'virtual google::protobuf::uint8* google::protobuf::internal::ImplicitWeakMessage::_InternalSerialize(google::protobuf::uint8*, google::protobuf::io::EpsCopyOutputStream*) const' at external/com_google_protobuf/src/google/protobuf/implicit_weak_message.h:87:28,
    inlined from 'bool google::protobuf::MessageLite::SerializePartialToZeroCopyStream(google::protobuf::io::ZeroCopyOutputStream*) const' at external/com_google_protobuf/src/google/protobuf/message_lite.cc:388:30:
/usr/include/bits/string_fortified.h:29:33: warning: 'void* __builtin___memcpy_chk(void*, const void*, long unsigned int, long unsigned int)' specified size between<PHONE_NUMBER>1562067968 and<PHONE_NUMBER>3709551615 exceeds maximum object size<PHONE_NUMBER>854775807 [-Wstringop-overflow=]
   29 |   return __builtin___memcpy_chk (__dest, __src, __len,
      |          ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
   30 |                                  __glibc_objsize0 (__dest));
      |                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~
INFO: From ProtoCompile mediapipe/calculators/internal/callback_packet_calculator.pb.h:
bazel-out/android-armeabi-v7a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/gpu/gl_surface_sink_calculator.pb.h:
bazel-out/android-armeabi-v7a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/framework/tool/calculator_graph_template.pb.h:
bazel-out/android-armeabi-v7a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/gpu/gl_context_options.pb.h:
bazel-out/android-armeabi-v7a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/framework/calculator_profile.pb.h:
bazel-out/android-armeabi-v7a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From Generating JavaLite proto_library //mediapipe/framework:mediapipe_options_proto:
[libprotobuf WARNING external/com_google_protobuf/src/google/protobuf/compiler/java/java_file.cc:230] mediapipe/framework/mediapipe_options.proto: The file's outer class name, "MediapipeOptions", matches the name of one of the types declared inside it when case is ignored. This can cause compilation issues on Windows / MacOS. Please either rename the type or use the java_outer_classname option to specify a different outer class name for the .proto file to be safe.
INFO: From ProtoCompile mediapipe/framework/calculator.pb.h:
bazel-out/android-armeabi-v7a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From Generating JavaLite proto_library //mediapipe/framework:mediapipe_options_proto:
[libprotobuf WARNING external/com_google_protobuf/src/google/protobuf/compiler/java/java_file.cc:230] mediapipe/framework/mediapipe_options.proto: The file's outer class name, "MediapipeOptions", matches the name of one of the types declared inside it when case is ignored. This can cause compilation issues on Windows / MacOS. Please either rename the type or use the java_outer_classname option to specify a different outer class name for the .proto file to be safe.
INFO: From ProtoCompile mediapipe/framework/calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/tensor/inference_calculator.pb.h:
bazel-out/android-armeabi-v7a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/gpu/gl_context_options.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/internal/callback_packet_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/framework/calculator_profile.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/framework/tool/calculator_graph_template.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/gpu/gl_surface_sink_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/util/detections_to_render_data_calculator.pb.h:
bazel-out/android-armeabi-v7a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/tflite/ssd_anchors_calculator.pb.h:
bazel-out/android-armeabi-v7a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/tensor/tensors_to_detections_calculator.pb.h:
bazel-out/android-armeabi-v7a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/util/non_max_suppression_calculator.pb.h:
bazel-out/android-armeabi-v7a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/framework/calculator.pb.h [for host]:
bazel-out/host/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/gpu/gl_context_options.pb.h [for host]:
bazel-out/host/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/tensor/tensors_to_detections_calculator.pb.h [for host]:
bazel-out/host/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/framework/calculator_profile.pb.h [for host]:
bazel-out/host/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/tflite/ssd_anchors_calculator.pb.h [for host]:
bazel-out/host/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/internal/callback_packet_calculator.pb.h [for host]:
bazel-out/host/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/util/non_max_suppression_calculator.pb.h [for host]:
bazel-out/host/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/framework/tool/calculator_graph_template.pb.h [for host]:
bazel-out/host/bin/external/com_google_protobuf/src: warning: directory does not exist.
ERROR: /home/thunderbirdtr/.cache/bazel/_bazel_thunderbirdtr/47aecfbb39c3d4019351abcfc511078c/external/com_google_absl/absl/synchronization/BUILD.bazel:30:11: C++ compilation of rule '@com_google_absl//absl/synchronization:graphcycles_internal' failed (Exit 1): gcc failed: error executing command /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 38 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox gcc failed: error executing command /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 38 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox
external/com_google_absl/absl/synchronization/internal/graphcycles.cc: In member function 'void absl::lts_2020_09_23::synchronization_internal::GraphCycles::RemoveNode(void*)':
external/com_google_absl/absl/synchronization/internal/graphcycles.cc:451:26: error: 'numeric_limits' is not a member of 'std'
  451 |   if (x->version == std::numeric_limits<uint32_t>::max()) {
      |                          ^~~~~~~~~~~~~~
external/com_google_absl/absl/synchronization/internal/graphcycles.cc:451:49: error: expected primary-expression before '>' token
  451 |   if (x->version == std::numeric_limits<uint32_t>::max()) {
      |                                                 ^
external/com_google_absl/absl/synchronization/internal/graphcycles.cc:451:52: error: '::max' has not been declared; did you mean 'std::max'?
  451 |   if (x->version == std::numeric_limits<uint32_t>::max()) {
      |                                                    ^~~
      |                                                    std::max
In file included from /usr/lib/gcc/x86_64-redhat-linux/11/../../../../include/c++/11/algorithm:62,
                 from external/com_google_absl/absl/synchronization/internal/graphcycles.cc:38:
/usr/lib/gcc/x86_64-redhat-linux/11/../../../../include/c++/11/bits/stl_algo.h:3467:5: note: 'std::max' declared here
 3467 |     max(initializer_list<_Tp> __l, _Compare __comp)
      |     ^~~
Target //mediapipe/examples/android/src/java/com/google/mediapipe/apps/facedetectioncpu_aar:mp_face_detectioncpu_aar failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 105.919s, Critical Path: 95.53s
INFO: 839 processes: 187 internal, 652 linux-sandbox.
FAILED: Build did NOT complete successfully

gcc --version
gcc (GCC) 11.0.1 20210405 (Red Hat 11.0.1-0)

python --version
Python 3.9.4

pip list | grep -E "six|numpy"
numpy             1.20.1
six                  1.15.0

bazelisk --version
bazel 3.7.2

That looks like related with this issue : https://github.com/bazelbuild/bazel/issues/12702

I managed to compile with this change in WORKSPACE
http_archive(
    name = "com_google_absl",
    urls = [
        "https://github.com/abseil/abseil-cpp/archive/20210324.0.tar.gz",
    ],
    # Remove after https://github.com/abseil/abseil-cpp/issues/326 is solved.
    patches = [
        "@//third_party:com_google_absl_f863b622fe13612433fdf43f76547d5edda0c93001.diff"
    ],
    patch_args = [
        "-p1",
    ],
    strip_prefix = "abseil-cpp-20210324.0",
    sha256 = "dd7db6815204c2a62a2160e32c55e97113b0a0178b2f090d6bab5ce36111db4b"
)

But didn't tested yet. (I'll update the comment when I tested)

I was able to use Kotlin with basic face detection :+1:  the only issue I had "camera" didn't start normal but start with "black screen" until rotate landmark then portrait mode.

import android.graphics.SurfaceTexture
import android.os.Bundle
import android.util.Log
import android.util.Size
import android.view.SurfaceHolder
import android.view.SurfaceView
import android.view.View
import android.view.ViewGroup
import androidx.appcompat.app.AppCompatActivity
import com.google.mediapipe.components.CameraHelper.CameraFacing
import com.google.mediapipe.components.CameraXPreviewHelper
import com.google.mediapipe.components.ExternalTextureConverter
import com.google.mediapipe.components.FrameProcessor
import com.google.mediapipe.components.PermissionHelper
import com.google.mediapipe.formats.proto.LandmarkProto.NormalizedLandmarkList
import com.google.mediapipe.framework.AndroidAssetUtil
import com.google.mediapipe.framework.Packet
import com.google.mediapipe.framework.PacketGetter
import com.google.mediapipe.glutil.EglManager
import com.google.mediapipe.framework.AndroidPacketCreator

class MainActivity : AppCompatActivity() {

    private val BINARY_GRAPH_NAME = "face_detection_mobile_gpu.binarypb"
    private val INPUT_VIDEO_STREAM_NAME = "input_video"
    private val OUTPUT_VIDEO_STREAM_NAME = "output_video"
    private val CAMERA_FACING = CameraFacing.FRONT

    // Flips the camera-preview frames vertically before sending them into FrameProcessor to be
    // processed in a MediaPipe graph, and flips the processed frames back when they are displayed.
    // This is needed because OpenGL represents images assuming the image origin is at the
    // bottom-left corner, whereas MediaPipe in general assumes the image origin is at top-left.
    private val FLIP_FRAMES_VERTICALLY = true

    companion object {
        // Used to load the 'native-lib' library on application startup.
        init {

            System.loadLibrary("mediapipe_jni")
            System.loadLibrary("opencv_java3")
        }
    }

    // {@link SurfaceTexture} where the camera-preview frames can be accessed.
    private var previewFrameTexture: SurfaceTexture? = null

    // {@link SurfaceView} that displays the camera-preview frames processed by a MediaPipe graph.
    private var previewDisplayView: SurfaceView? = null

    // Creates and manages an {@link EGLContext}.
    private var eglManager: EglManager? = null

    // Sends camera-preview frames into a MediaPipe graph for processing, and displays the processed
    // frames onto a {@link Surface}.
    private var processor: FrameProcessor? = null

    // Converts the GL_TEXTURE_EXTERNAL_OES texture from Android camera into a regular texture to be
    // consumed by {@link FrameProcessor} and the underlying MediaPipe graph.
    private var converter: ExternalTextureConverter? = null

    // Handles camera access via the {@link CameraX} Jetpack support library.
    private var cameraHelper: CameraXPreviewHelper? = null

    // Face mesh
    private val INPUT_NUM_FACES_SIDE_PACKET_NAME = "num_faces"
    private val OUTPUT_LANDMARKS_STREAM_NAME = "multi_face_landmarks"

    // Max number of faces to detect/process.
    private val NUM_FACES = 1

    private val TAG = "LLOG"

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.activity_main)
        //findViewById<TextView>(R.id.sample_text).text = stringFromJNI()

        previewDisplayView = SurfaceView(this)
        setupPreviewDisplayView()
        // Initialize asset manager so that MediaPipe native libraries can access the app assets, e.g.,
        // binary graphs.

        // Initialize asset manager so that MediaPipe native libraries can access the app assets, e.g.,
        // binary graphs.
        AndroidAssetUtil.initializeNativeAssetManager(this)
        eglManager = EglManager(null)
        processor = FrameProcessor(
            this,
            eglManager!!.nativeContext,
            BINARY_GRAPH_NAME,
            INPUT_VIDEO_STREAM_NAME,
            OUTPUT_VIDEO_STREAM_NAME
        )
        processor!!.videoSurfaceOutput.setFlipY(FLIP_FRAMES_VERTICALLY)
        PermissionHelper.checkAndRequestCameraPermissions(this)

        val packetCreator:AndroidPacketCreator = processor!!.packetCreator
        val inputSidePackets: MutableMap<String, Packet> = HashMap()
        inputSidePackets[INPUT_NUM_FACES_SIDE_PACKET_NAME] = packetCreator.createInt32(NUM_FACES)
        processor!!.setInputSidePackets(inputSidePackets)
        //logFaceLandmark()
    }

    override fun onResume() {
        super.onResume()
        converter = ExternalTextureConverter(eglManager!!.context)
        converter?.setFlipY(FLIP_FRAMES_VERTICALLY)
        converter?.setConsumer(processor)
        if (PermissionHelper.cameraPermissionsGranted(this)) {
            startCamera()
        }
    }

    override fun onPause() {
        super.onPause()
        converter!!.close()
    }

    private fun startCamera() {
        cameraHelper = CameraXPreviewHelper()
        cameraHelper!!.setOnCameraStartedListener { surfaceTexture: SurfaceTexture? ->
            previewFrameTexture = surfaceTexture
            // Make the display view visible to start showing the preview. This triggers the
            // SurfaceHolder.Callback added to (the holder of) previewDisplayView.
            previewDisplayView!!.visibility = View.VISIBLE
        }
        cameraHelper!!.startCamera(this, CAMERA_FACING,  /*surfaceTexture=*/null)
    }

    private fun setupPreviewDisplayView() {
        previewDisplayView!!.visibility = View.GONE
        val viewGroup = findViewById<ViewGroup>(R.id.preview_display_layout)
        viewGroup.addView(previewDisplayView)

        previewDisplayView!!
            .holder
            .addCallback(
                object : SurfaceHolder.Callback {
                    override fun surfaceCreated(holder: SurfaceHolder) {
                        processor!!.videoSurfaceOutput.setSurface(holder.surface)
                    }

                    override fun surfaceChanged(
                        holder: SurfaceHolder,
                        format: Int,
                        width: Int,
                        height: Int
                    ) {
                        // (Re-)Compute the ideal size of the camera-preview display (the area that the
                        // camera-preview frames get rendered onto, potentially with scaling and rotation)
                        // based on the size of the SurfaceView that contains the display.
                        val viewSize = Size(width, height)
                        val displaySize: Size =
                            cameraHelper!!.computeDisplaySizeFromViewSize(viewSize)

                        // Connect the converter to the camera-preview frames as its input (via
                        // previewFrameTexture), and configure the output width and height as the computed
                        // display size.
                        converter?.setSurfaceTextureAndAttachToGLContext(
                            previewFrameTexture, displaySize.height, displaySize.width
                        )
                    }

                    override fun surfaceDestroyed(holder: SurfaceHolder) {
                        processor!!.videoSurfaceOutput.setSurface(null)
                    }
                })
    }
    override fun onRequestPermissionsResult(
        requestCode: Int,
        permissions: Array<out String>,
        grantResults: IntArray
    ) {
        super.onRequestPermissionsResult(requestCode, permissions, grantResults)
    }
}

I had to also change setSurfaceTextureAndAttachToGLContext
width = displaySize.height
height = displaySize.width
Because there was a "stretched in width" I don't know because of layout but It was ugly.

                        converter?.setSurfaceTextureAndAttachToGLContext(
                            previewFrameTexture, displaySize.height, displaySize.width
                        )

Hello, is there any updates about this ?
Thank you :)


External DNS fails to process DNS names if wildcards present

Kubernetes version: any version
DNS provider: AWS Route53
How to reproduce:
Create an ingress with the following manifest:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: test-hack
spec:
  rules:
  - host: "*.hack-test.mycompany.com"
    http:
      paths:
      - backend:
          serviceName: nginx-hack-service
          servicePort: 80

Description:
Once the record is created on the next iteration the following error occurs:
Tried to create resource record set [name='\052.hack-test.mycompany.com.', type='A'] but it already exists

Investigation shows the following:
aws route53 list-resource-record-sets --hosted-zone-id=Z29O22JY2BY7OV | jq '.ResourceRecordSets|map(select(.Name=="\\052.hack-test.mycompany.com."))'
# outputs:
[
  {
    "Type": "CNAME",
    "ResourceRecords": [
      {
        "Value": "test-this.mycompany.com."
      }
    ],
    "Name": "\\052.test-this.mycompany.com.",
    "TTL": 300
  }
]

* is getting converted to its octal ASCII representation.
Suggested course of action:

Do the right string comparison for DNSNames and extracted value from the TXT record

More to follow

@ideahitme I think this can be closed now with the merge of #302

IMHO wildcard domains should be supported on every cloud provider.
There is a discussion issue opened related to this subject: #255


Favicon added

I have added relevant favicon icon and made it visible over the tab
Fixes #19

@nagamukesh Resolve Conflict & add screenshot


[Feature Request] Data extraction & interaction DSL

Hey Puppeteer guys,
I really think you've made a great job so far and I'm imprerssed by all the posibillities you gave us developers now. Of course I know there are tools like selenium but puppeteer made this browser interaction accessible and accepted for me. While using pupeteer I've figured out that from my pov I'm using it mostly as a tool to extract data from one or a series of urls and connect these to user individual input or analytic purposes. After a while I've written a lib to "datafy" websites using a DSL that gets translated into pupeteer method calls. Since one week it's getting more and more stable and after integrating it in other puppeteer projects of colleagues I see endless possibilities having a DSL to do such things on websites like  a human could do in the same way.
So from an open source perspective I think the best place to have something realized like that is on the puppeteer level rather than having a separate lib to reduce the barriers using such a DSL.
So I wanted to ask is if this is something you could imagine to have in puppeteer or if this is not alignable / too different with your scope.
I think to really close the gap in terms of "make websites analyzable/programmatically usable for the main internet user" would be, to have an understandable chrome extension that make DOM selectors accessible and build the DSL in background...
Anyway...
I'd like to ask you if you could imagine to do something like this together.
Build an additional DSL in puppeteer to grab data declarative from a website and navigate to others as well
As mentioned above I've build a basic lib to do things explained above but I would also like to help getting something like this work in puppeteer directly.
You'll find the draft here and here
Thanks so far for reading and of course for your great work.
Bernhard

This is certainly interesting, but I think it’s outside the scope of Puppeteer. You can and should use external libraries in tandem with puppeteer, but in the core project we want to stick as close as possible to the web platform.


Feat landing page redesign

Description
Landing Page Redesign
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Type of change
Redesigned whole landing page and updated Tailwind styling and adding components
Needed to be able to have full responsive design from mobile to desktop
Components added:
BottomCard, HamburgerNav, LogoContainer, NavButtons, NavContainer
Component removed:
NavBtn no longer needed
Please select everything applicable. Please, do not delete any lines.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
This will break navigation buttons.
[ ] This change requires a documentation update

Issue

[ ] Is this related to a specific issue? Is so please specify: #178

Checklist:

[x] I have executed npm run lint and resolved any outstanding errors. Most issues can be solved by executing npm run format
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings

Looking good! Great work on the styling! Since we have a bit more work to do, like adding the buttons and adding text content to the boxes below, I switched the branch from development to feature/LandingPageRedesign.
I'll go ahead and approve the merge now.
Some things to be worked on:

Media queries still exist for the background color
Nav buttons do not work
Content must be added to the bottom half of the landing page

Accepting Merge into landingPageRedesign
Opening issues to resolve:

Fixing the nav buttons
Adding content to the content boxes


CosmosDB Emulator support for devcontainer

Type of PR

[x] Documentation changes
[x] Code changes
[ ] Test changes
[ ] CI-CD changes
[ ] GitHub Template changes

PR Checklist

[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] My code follows the code style of this project.
[x] I ran lint checks locally prior to submission.
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Purpose of PR

Run cosmos db emulator as part of codespaces dev container to support self contained dev env.
Updated emulator url using nginx to pass the standard cosmos url validations
Updated docs to provide guidance on running with lodeRunner applications.

Steps To Test:

Create new codespaces from this branch
Once done executing postCreate and postStart scripts, navigate to port tab and locate Cosmos DB Emulator port
Copy local adress for port 9090 and open in a browser with _explorer/index.html endpoint.
Validate LodeRunner databse in data explorer.
execute ./scripts/cosmos-emulator-mode.sh from root directory to update loderunner applications secrets
Validate LodeRunner.API and LodeRunner application

Does this introduce a breaking change

[ ] YES
[x] NO

Validation

[x] Unit tests updated and ran successfully
[x] Update documentation or issue referenced above

Issues Closed or Referenced

Closes https://github.com/retaildevcrews/wcnp/issues/595

doesn't need to be part of your PR but would be interesting to consider moving integration testing to point against emulator vs test database

doesn't need to be part of your PR but would be interesting to consider moving integration testing to point against emulator vs test database

@alfredoihernandez, that is the plan.  Probably won't be until after M4 though.


[Enhancement] (nereids)implement syncCommand in nereids

What problem does this PR solve?
Issue Number: close #42814
Related PR: #xxx
Problem Summary:
implement syncCommand in nereids
Release note
None
Check List (For Author)

Test

[X] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[ ] No.
[ ] Yes.

Does this need documentation?

[ ] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall

run buildall

run buildall

run buildall

run buildall


use requests library for raw_iter, to support custom http_session

This fixes a problem with loading data from urls which require a custom http session (e.g. for http auth)
While tabulator accepts http_session option to support this, the raw_iter method which is used to infer encoding doesn't
To fix it - changed the raw_iter to use requests library and optionally use the http_session option from table options
I think that in the long term we should have the encoding detection done in tabulator - to keep a consistent loading method

lgtm

@OriHoch
Thanks!
There is one thing I'm concerned about. You use requests.raw (http://docs.python-requests.org/en/master/user/quickstart/#raw-response-content). But as far as I can remember I failed to use it with tabulator because it doesn't decompress the stream. Not sure it has been changed for requests@3. I think we at least need to add a few tests to figure it out.


React native navigation issue on android with react-native 0.60.0

Hi Everyone,
I have an application with react native version 0.60.0 and i am using react-native-navigation .
"react": "16.8.6",
"react-native": "0.60.0",
"react-native-navigation": "^2.26.2",

I got issues when i build for android like below (also screenshot added)
error: cannot find symbol class MeasureSpecProvider
error: cannot find symbol class SizeMonitoringFrameLayout
My environment details
defaultConfig {
    applicationId "com.clubz"
    minSdkVersion rootProject.ext.minSdkVersion
    targetSdkVersion rootProject.ext.targetSdkVersion
    versionCode 1
    versionName "1.0"
    missingDimensionStrategy "RNN.reactNativeVersion", "reactNative57_5" // See note below!

}

subprojects { subproject ->
    afterEvaluate {
        if ((subproject.plugins.hasPlugin('android') || subproject.plugins.hasPlugin('android-library'))) {
            android {
                variantFilter { variant ->
                    def names = variant.flavors*.name
                    // To check for a certain build type, use variant.buildType.name == "<buildType>"
                    if (names.contains("reactNative51") || names.contains("reactNative55")) {
                        // Gradle ignores any variants that satisfy the conditions above.
                        setIgnore(true)
                    }
                }
            }
        }
    }
}

Thanks in advance

wrong community


Password Reset (routeNotificationForMail)

If using auht:make scaffolding, for password reset is necessary add function ruouteNotificationForMail in User model
public function ruouteNotificationForMail()
{
    return $this->getEmailForPasswordReset();
}

This is correct?

The email property will be used by default, so no, you don't have to add the function to the model if you don't want to.

if i have custom email property ?

In that case yes.

ok ty!


sea-orm-cli generate entity PoolTimedOut error with large schema

First off, thanks for all the hard work!
Description
When trying to use sea-orm-cli generate entity on a large Postgres 9.6.22 database (>400 tables of varying shapes, sizes, constraints, etc.), I encounter the following error:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: PoolTimedOut', /Users/will.wang/dev-projects/sea-schema/src/postgres/discovery/executor/real.rs:30:55

Similar to: https://github.com/SeaQL/sea-orm/issues/555
Steps to Reproduce
Unfortunately, I can't provide exact details around the schema. I think any sufficiently large database should work. I believe this occurs because the connection times out in between executing the many introspection queries.
Expected Behavior
Entities are automatically generated
Actual Behavior
Connection fails, panic occurs
Reproduces How Often
Always
Versions
sea-orm-cli: 0.8.1 (built locally on master at https://github.com/SeaQL/sea-schema/commit/00429f3bdbfe56af1afcee94b069a9619cea4263)
postgres: 9.6.22
os: MacOS Monterey 12.3.1
Additional Information
I think the default connect_timeout of 30 seconds for the underlying sqlx::PoolOptions is too short. When I changed this locally to 120 seconds, I was able to avoid this issue. It would be great if we could configure a connect_timeout as an argument in sea-orm-cli generate entity similar to max_connections.

Hey @001wwang, thanks for the investigations! Increasing the connect_timeout seems like a good temporary fix. However, I want to know why it takes so long to fetch the info of all db tables? Does anyone have a large sample schema for testing?

No problem, thanks for the prompt reply! I'll see if I can produce a large sample schema for recreating this issue later.

I think the default connect_timeout of 30 seconds for the underlying sqlx::PoolOptions is too short. When I changed this locally to 120 seconds, I was able to avoid this issue. It would be great if we could configure a connect_timeout as an argument in sea-orm-cli generate entity similar to max_connections.

How did you solve it? I also have this problem now

How did you solve it? I also have this problem now

Sorry, this issue slipped my mind. Perhaps you could provide more details about your schema to help @billy1624 reproduce this locally.
For my fix, I modified the sea-orm-cli codebase locally to use a timeout of 120 seconds (then, built and run locally). Disclaimer: it's been a few months since then, so this may not be guaranteed to work nor may be the problem you're facing.

I encountered this error for tables with partitions (postgres). If a table has a lot of partitions, the generator will see those as separate tables and try to generate for all of them. Deleting those partitions solved this problem for me.
This is actually expected and JOOQ also has the same behavior. You can solve this in JOOQ by providing an exclude regex like
<excludes>.*_p[0-9_]+</excludes> so that it skips those.
In an ideal scenario you should not have partitions in your target schema but regex option can be added in cli as well to help these kind of situations in general.

Hey everyone, I created 3,000 tables on my local Postgres but still not able to reproduce the error.
CREATE TABLE IF NOT EXISTS t_793593555976192 (col1 integer, col2 integer, col3 integer);
... 3,000 create table statements

I'll go ahead and close this issue given the above comments. I haven't looked into this any time recently, and it seems like it might be working at this point. Thanks all!

Just for anyone else facing the issue: This seem to happen intermittently on slow/weak/high packet loss networks. Ensure your network is low latency to make it work.

I am having the same issue with partitioned tables as well. +1 for regex exclusion.

Ah, I think I tracked it down.
In sea-schema, we are doing future::join_all() on potentially a very large list. They all end up rushing to the executor to get a connection to execute their query. The default cli configis to only have a single connection so they're all just waiting for that one connection to be available. So the pool times out for some of the later ones. The fix was to set --max-connections 50 to allow a higher throughput and avoid the timeout. A lower number probably would've worked too but that's what did it for me.

@jared-mackey thank you for pointing it out. It seems like we should not join_all more than the pool size in SeaSchema.

@tyt2y3 Seems like a good approach.
A couple of thoughts on the issue after looking into it a bit.
There is the join all problem that should be solved. However, that seems to be exacerbated by these

It seems that tables set to ignore via the CLI argument are still pulled via the discovery process, they're just not generated in the output. There is probably a good reason for this, but thought I'd mention it.
And to tie it back to #1582 a bit, in my case all the partitions were the same schema and I don't care about anything other than the super table. But I do believe there are cases where partitions can be different than the super schema so maybe we cannot optimize those out. Would need to do some research to see if they have a flag or something where we can tell if the partitions are the same as the super or not. If they are, we shouldn't pull them at all I don't believe.


'cosmosSearch' is not supported

I've read about the recent vector search feature added to Azure Cosmos DB for MongoDB vCore:
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cosmos-db/mongodb/vcore/vector-search.md?plain=1
however, when I try to create the index I get this error:
'cosmosSearch' is not supported
I'm guessing this feature is not publicly supported yet? If so, are there any instructions on how to enable it for my instance?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 5e53e4aa-c504-448b-9598-419eda127192
Version Independent ID: 79fdea2a-5317-4996-a2b1-57662c2b9aa0
Content: Vector search on embeddings - Azure Cosmos DB for MongoDB vCore
Content Source: articles/cosmos-db/mongodb/vcore/vector-search.md
Service: cosmos-db
Sub-service: mongodb-vcore
GitHub Login: @gahl-levy
Microsoft Alias: gahllevy

@frouhi
Thanks for your feedback! We will investigate and update as appropriate.

Hello, I'm getting the same when trying to create a vector index using pymongo:
pymongo.errors.OperationFailure: cosmosSearchOptions, full error: {'ok': 0.0, 'errmsg': 'cosmosSearchOptions', 'code': 197, 'codeName': 'InvalidIndexSpecificationOption'}

I noticed this is because the RU version of Azure Cosmos does not have the vector search feature available. Only the vCore does at the moment. Will the RU version have it in the near term?

@seesharprun the docs for deciding whether to use RU or vcore do not mention this, could we please update them? #114834


Move up the "cvss" field when creating/editing finding

Is your feature request related to a problem? Please describe
The cvss3 field is way at the bottom. Too bad, it's got a nice JS to actually fill out the cvss right within dojo!
Describe the solution you'd like
Put it right under "severity" maybe?

I noticed it also lower on the page on the view finding page using a whole panel for itself. Might be more logical to put it at the top, maybe in the same row as location / component name+version?

It's a good idea


bug: Oil does not remember the initial buffer if you open a file with preview window active

Did you check the docs and existing issues?

[X] I have read the docs
[X] I have searched the existing issues

Neovim version (nvim -v)
0.9.4
Operating system/version
MacOS 13.6
Describe the bug
Sometimes, closing Oil does not return you to the buffer you opened it from. Simple steps to reproduce below.
What is the severity of this bug?
tolerable (can work around it)
Steps To Reproduce

nvim -u repro.lua a.txt
:Oil
open preview using ^P
navigagte to and open b.txt (i.e. via <CR>)
:Oil
^C
You will be returned to a.txt

Expected Behavior
You return to the b.txt buffer (since that was the buffer you were in when you last opened Oil)
Directory structure
a.txt
b.txt
repro.lua
Repro
-- save as repro.lua
-- run with nvim -u repro.lua
-- DO NOT change the paths
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "runtime", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "--single-branch",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  {
        "stevearc/oil.nvim",
        config = function()
            require("oil").setup({
              -- add any needed settings here
            })
        end,
  },
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Did you check the bug with a clean config?

[X] I have confirmed that the bug reproduces with nvim -u repro.lua using the repro.lua file above.

Should be fixed now. Thanks for the report!


Input.Date's first day of the week at Teams doesn't change

Platform
What platform is your issue or question related to? (Delete other platforms).

.Net Core
Adaptive cards in MS Teams inside Chat bot

Details
I use an Input.Date in adaptive card. In Teams a week in the calendar starts on Sunday:

I need it to be displayed from Monday, so I tried to change app's language to English (United Kingdom), but it didn't help.

@siduppal feature request for Teams to change calendar start day based on the card's localization

Could you please Raise a user voice?

I created an idea on the user voice - link

Hello! Maybe do you have some additional opportunity to find out the predictions on this problem?

Currently we don't have any other way. Thanks for Raising a user voice.

User voice would be right place to track this. Closing this from issues page.


Search results should include warnings for ignored parameters

User story
As a client, I want to clearly see which search parameters were ignored in my request.
For example, when searching using an invalid search parameter in Vonk, cush as https://vonk.fire.ly/Observation?foo=bar, you get a helpful OperationOutcome in the search results
        {
            "fullUrl": "https://vonk.fire.ly/OperationOutcome/d5c6d473-b1ef-4692-8b19-709c8bdc3b83",
            "search": {
                "mode": "outcome"
            },
            "resource": {
                "resourceType": "OperationOutcome",
                "id": "d5c6d473-b1ef-4692-8b19-709c8bdc3b83",
                "meta": {
                    "versionId": "4d208d26-49cc-453d-bf07-94e38c817ee1",
                    "lastUpdated": "2019-08-13T19:55:21.916+00:00"
                },
                "issue": [
                    {
                        "severity": "warning",
                        "code": "not-supported",
                        "details": {
                            "coding": [
                                {
                                    "system": "http://hl7.org/fhir/dotnet-api-operation-outcome",
                                    "code": "5003"
                                }
                            ],
                            "text": "Parameter foo is not implemented"
                        }
                    }
                ]
            }
        }

This is in addition to the self and next links omitting the invalid parameter (as we do as well).

AB#73598
@CaitlinV39 update description in DevOps


Let :Other accept file path as an argument

Sometimes you do not want to map a pattern for maybe a single file, and you just want to teach :Other that the following file is the 'other' file that I always want you to open.
At the moment passing anything other than the context to :Other returns No 'other' file found
Would be nice to be able to do the following :Other my/new/file/path.rb and the plugin will store that as the 'other' file for this current file. Now the next time I will just need to type :Other and it'll open my/new/file/path.rb

Hey @kaka-ruto!
I really like your idea and I'm totally onboard with integrating it. The only thing I'm not quite sure about is the syntax ':Other ' you mentioned. But don't worry, I'll figure out a way to make it work.
And you're absolutely right about #27. I totally need to write up the requirements to help the devs get started. I'm actually in the middle of updating and streamlining the readme, so I'll add a section specifically addressing this. I'll be sure to keep you in the loop with any updates.
Thanks for sharing your ideas, much appreciated!


gpu out of memory

HI bro ,my gpu is RTX2080 with sm75 architecture .I can not train the data,the problem is gpu out of memory. please help me ,thanks!

reduce batch size.


npm error

root~# git clone https://github.com/hihumanzone/Gemini-Discord-Bot.git
Cloning into 'Gemini-Discord-Bot'...
remote: Enumerating objects: 713, done.
remote: Counting objects: 100% (346/346), done.
remote: Compressing objects: 100% (165/165), done.
remote: Total 713 (delta 219), reused 280 (delta 181), pack-reused 367
Receiving objects: 100% (713/713), 2.95 MiB | 9.88 MiB/s, done.
Resolving deltas: 100% (403/403), done.
root:~# cd Gemini-Discord-Bot/
root:~/Gemini-Discord-Bot# npm install dotenv<EMAIL_ADDRESS>discord.js @google/generative-ai fs sharp pdf-parse cheerio youtube-transcript axios eventsource node-os-utils @google/generative-ai/files
npm error code ENOENT
npm error syscall open
npm error path<EMAIL_ADDRESS>npm error errno -2
npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open<EMAIL_ADDRESS>npm error enoent This is related to npm not being able to find a file.
npm error enoent
npm error A complete log of this run can be found in: /root/.npm/_logs/2024-06-28T08_54_06_758Z-debug-0.log
Here's the log
2024-06-28T08_54_06_758Z-debug-0.log

I think I fixed it, could you please try again now and confirm if it's fixed?

yes the problem has been fixed, thank you and have a nice day.


Whatsapp media uploads stopped working on Android in 25 Feb.

Since early in the morning 25 Feb 2023, Whatsapp for Android has been unable to show media attachments sent by Matterbridge. On Whatsapp Web, the attachments work fine. Has been confirmed with multiple users.
I did not do anything to my setup at that time, so I guess that something on WA for Android has changed.

According to whatsmeow author, "the android app stopped reading the url field in media messages and only supports directPath now".

Hey not so sure if recent PR actually resolved the issue
When using latest master I am running into this problem:

Is this the original bug behavior?

Yes on web I do see the image
(and I am on android)

Actually I think its working now.
Idk what was the issue before.
Thanks!


Allow installing a package from outside a manifest

Consider https://github.com/cmr/hgl-rs/blob/master/.travis.yml. It installs glfw-rs manually just so it can be available when building the examples, but otherwise nothing depends on them.

That'd be https://github.com/rust-lang/cargo/pull/1318

Hey guys, I was pointed in this direction by Alex.
It seems [RFC]/PR (#1318) has been closed by the guy who proposed it due to lack of time.
There are a bunch of good ideas scattered around:

cargo package (#557 and later on #1318): package already exists but not as described in those threads.
cargo install foobar (#1318, #1593)

Needed for a comprehensive feature set (#1593):

cargo uninstall foobar # or remove...
cargo view foobar
cargo list
cargo upgrade foobar

Here is my attempt to an RFC.

Btw, @alexcrichton can we use rust-lang/rfcs for Cargo related rfcs (add a cargo/ folder)? if not, can we have an rfcs/ folder on cargo itself where we can place the .md of ongoing RFCs and collaborate?

[RFC] - Extended package management

version: 0.0.1

[back-end] local repository
To make this possible we need some sort of local repository running on the machine.
System wide and local to the user need to be considered.
[command] cargo package
Scope: This command only works from inside a cargo project.
Possible packaging outputs include but are not limited to: deb, rpm, tar, zip, or installer (Windows).

This feature does not interact with the local repository.

Other considerations
We need to consider architectures.

cargo package [github-url] might be a possibility too, but not clear on the use cases of creating a new package without needing to have the code.

[command] cargo install [crate.io[version] | github-url]
Scope: Works inside or outside a cargo project.
When run from outside a cargo project the crate name or github-url is required. It will download the package or source, compile and install on the machine.
When run inside a cargo project (and no crate arguments), it will compile and install that project in the machine.
Other considerations
Do we want the outputs of  cargo package to interact with the repository when unpackaged on the target machines?
Examples
> cargo install foobar
foobar 0.1.2 installed (crates.io)
> foobar
Hello foobarians!
> cargo install https://github.com/example/repo-rs.git
repo 0.0.1 installed (https://github.com/example/repo-rs)

[command] cargo view crate.io
Scope: This command only works from inside a cargo project.
Displays information on a package (installed or not).
Possible information displayed would be:

installed version is available,
the latest version on crates.io.
dependencies (are they installed? which version is on the system, whats available on crates.io)

Examples
> cargo view foobar
foobar 0.1.2 (0.3.7 is available)
    | foo 0.0.3 (0.2.0 is available)
    | bar 0.1.2 (0.1.8 is available)
> cargo view oops
oops not installed (0.1.0 is available)
> cargo view qwerty
qwerty crate does not exist

[command] cargo list
Scope: This command is valid anywhere.
The purpose is to know what packages are available on the computer.
Other considerations
We need to consider system wide + user local.
Can the repository know what source code only projects are available but not installed? (might be overcomplicating things)
Examples
> cargo list
foobar 0.1.2 installed (0.3.7 is available)
repo 0.0.1 installed (https://github.com/example/repo-rs.git [behind 9 commits])
> cargo list --dependencies
foobar 0.1.2 installed (0.3.7 is available)
repo 0.0.1 installed (https://github.com/example/repo-rs.git [behind 9 commits])
The following crates are available as dependencies
foo 0.0.3 (0.2.0 is available)
bar 0.1.2 (0.1.8 is available)

[command] cargo upgrade crate
Scope: This command is valid anywhere.
The purpose is to upgrade a package to a newer version.
Other considerations
If the current version is a hard dependency for some other crate then we need to keep that copy around too.
We also need to figure out how to swap between different versions of the same crate if we allow to have multiple versions installed (or just 1 installed + n versions as dependencies).

It is possible to use cargo update and have it be context dependent instead of adding a new command name. In this case, running it inside a cargo project or outside behave differently.

Examples
> cargo upgrade foobar
foobar 0.3.7 upgraded

[command] cargo remove crate
Scope: This command is valid anywhere.
The purpose is to remove an installed package.
Other considerations
Similar to upgrade, we need to be careful when this crate is a dependency to another crate. We also need to consider removing all the dependencies that are not primary installs unless they happen to be dependencies to some other installed crate.

@icorderi wow, thanks for writing this up! For now major changes/additions to Cargo are going through the normal Rust RFC process, so I would recommend drafting up an RFC for that repo to gain comments on this.
This is looking pretty good! Some hesitations that I've had in the past are:

What's the scope of cargo install? Is it intended to install libraries? Only binaries? In terms of package management, isn't the "correct way" to install software through the distro's package manager, and is cargo install an antipattern as a result?
How will cargo generate all these various kinds of packages? What kinds of native tools will Cargo depend on to build an RPM or a Windows installer? Are these sorts of tasks better suited to Cargo subcommands instead of Cargo itself?
With cargo install, where are all the artifacts stored? Do we just have ~/.cargo/bin and such?
How does cargo install interact with native dependencies? If a native dependency is a dylib, then it'll need to be installed on the local system as well. Some packages may also need things like native assets. This kind of configuration typically necessitates an "install script" in addition to a build script.

Some of these questions I don't have great answers to, but they may want to be at least considered before pushing too hard on this.

Implemented as cargo install!


Added newsletter

Description
Added a component for newsletter with link in products part of footer
Fixed #263
Type of change
Please check options that are relevant to your PR.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:

[x] I have pulled the latest changes in the repository
[x] I have squashed my commits
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

@sandra9711 Apologies for the delay.
We don't want a separate page for subscribing to our newsletter, instead you can just add an input field with a button to Subscribe, like here.
Also, Newsletter is not a Product, so remove it from there and simply add this input field above "Get in Touch" section.

@vaishali614
Made all changes mentioned

@vaishali614
Made all changes mentioned

It's not in center, please keep it aligned with other components. Other than that, it looks good to go.

@vaishali614
I corrected the alignment as in this picture

But it looks like this in the deploy preview