Updated accessors.py

Just did some small assignment task to remove this small error of walrus operator(:=) which will make the module xwrf run even in unupdated versions of python solving the import error

Change Summary

Related issue number

Checklist

[ ] Unit tests for the changes exist
[ ] Tests pass on CI
[ ] Documentation reflects the changes where applicable

Thank you for offering this contribution! However, Python versions older than 3.8 are not being supported by most of the community (see NEP 29 already at 3.8 minimum and conda-forge dropping 3.7 in the coming days), which means that xwrf trying to support such outdated Python versions would be an undue maintenance burden (e.g., custom CI builds, increased complexity in dependency management). So, with xwrf only supporting Python >= 3.8, this PR's change is unfortunately not worthwhile. If you are currently using Python <= 3.7, I highly encourage you to focus your efforts on modernizing your environment (be it yourself or working with a sysadmin) to regularly update and keep pace with the present Scientific Python community (for example, in about 6 months, many packages will have Python 3.9 as their minimum version).

Understood!
so it is plausible to close the issue : SyntaxError encountered upon import #114
as in newer versions walrus operator is supported so no error while importing xwrf.

Understood! so it is plausible to close the issue : SyntaxError encountered upon import #114 as in newer versions walrus operator is supported so no error while importing xwrf.

Correct, we are just waiting for a response from the issue's author to verify that was indeed their issue prior to closing.


Adding translation of README file for PT-br

Thanks for the effort, @franklindias. I highly appreciate it!
As of now, we don’t have the infrastructure to support multiple languages. If we start with one, we’d have to accept all translations and that would become impractical as we don’t have the resources to keep them all up2date.
I’m going to close this (aside from the fact that the CLA hasn’t been signed and we legally can’t accept the PR anyways).


Huge delay when hover a emoji in Picker

Hello, recently I started to use your library, but recently I have encountered a huge delay in the hover function of each emoji onEmojiEnter(), here is a video that shows this delay:
https://user-images.githubusercontent.com/113697875/190650506-9ece797c-2c01-48d0-af5f-532510db87a4.mp4
As you can see in the video, the hover function takes a long time to load, in my case I had cases where the delay was up to 100ms, when I had the mouse hovering over several emojis the preview didn't even change.

Does it work like this if you close the Vue inspector? Or maybe some browser extension affects the speed?
I just tried and it works good for me:
https://user-images.githubusercontent.com/597640/196013930-0f874778-652e-4e08-bc21-a4fa1751653f.mov

Closing, not enough details to reproduce of fix this issue.
If you have more information about it, please feel free to provide it and reopen the issue.


Sticker not properly set on face as per position of eye or face.

I have used this demo to implement live stickers on the face. But there is an issue that sticker does not set on the face properly. For example, glasses do not set on the eye position of the face.  The similarly same thing happens for the other stickers.
Can you help I resolved this issue?
Please reply soon.............................

i got same problem

 Face face = mFace;
        if (face == null) return;
        // Draws a circle at the position of the detected face, with the face's track id below.
        float x = translateX(face.getPosition().x + face.getWidth() / 2);
        float y = translateY(face.getPosition().y + face.getHeight() / 2);
        /*
        canvas.drawCircle(x, y, FACE_POSITION_RADIUS, mFacePositionPaint);
        canvas.drawText("id: " + mFaceId, x + ID_X_OFFSET, y + ID_Y_OFFSET, mIdPaint);
        canvas.drawText("happiness: " + String.format("%.2f", face.getIsSmilingProbability()), x - ID_X_OFFSET, y - ID_Y_OFFSET, mIdPaint);
        canvas.drawText("right eye: " + String.format("%.2f", face.getIsRightEyeOpenProbability()), x + ID_X_OFFSET * 2, y + ID_Y_OFFSET * 2, mIdPaint);
        canvas.drawText("left eye: " + String.format("%.2f", face.getIsLeftEyeOpenProbability()), x - ID_X_OFFSET*2, y - ID_Y_OFFSET*2, mIdPaint);
        */
        float xOffset = scaleX(face.getWidth()/2.00f);
        float yOffset = scaleY(face.getHeight()/1.20f);

        float left = x - xOffset;
        float top = y - yOffset;
        //float right = x + xOffset;
        //float bottom = y + yOffset;
        //canvas.drawRect(left, top, right, bottom, mBoxPaint);
        canvas.drawBitmap(op, left, top, new Paint());

after changing draw method like this, it is solved!

Hi @HEMAL-PATEL , @poojan28 , @JDevelopes : I can close the issue?

It is not clear Solution  as on first line
Face face = mFace;
and
canvas.drawBitmap(op, left, top, new Paint());
what is op ??

anyone solve accurate face sticker problem?


Hi, I'm doing research about Kinect V2.
I get some problem with that when I try to run the example from KinectPV2 on Processing.
After I click "run" botton , All I get is:
console output :
64 windows 10
Loading KinectV2
Creating Kinect object ...
Setting Color Frame
Done Loading Kinect V2
Version: 0.7.8
output:

Both are from different example, All I get is a black screen (second one has frame data).
And my KinectV2 device has no light (I think the problem is because of it).
Please help me for solving this issue.
My environment are as follow:
Window 10 64bit
Kinect V2
Processing 3.4
KinectPV2 version : 0.7.8
SDK Browser v2.0 (Kinect for Windows)
USB 3.0

I resolved this problem already, thanks.

Hi, I'm having this same problem.
Could you let me know how you resolved it?
Thanks!

How did you resolve it?

I am a little bit late, but i solved it.
I deleted the LibusbK driver i needed for openkinect for processing lib and switched back to the standard driver.
This one works with the official Kinect SDK and the KinectV2 library.


Travis: Stop node testing on 6 (EOL); start on 12

Thanks. Will land in 1.4.0. But releasing 1.3.2 quickly first before that.

Yeah, that makes sense.


feat(api): implement branch/commit comparison API

Add new Compare struct to represent comparison between two commits
Introduce new API endpoint /compare/* to get commit comparison information
Create new file repo_compare.go with the Compare struct definition
Add new file compare.go in routers/api/v1/repo to handle comparison logic
Add new file compare.go in routers/common to define CompareInfo struct
Refactor ParseCompareInfo function to use common.CompareInfo struct
Update Swagger documentation to include the new API endpoint for commit comparison
Remove duplicate CompareInfo struct from routers/web/repo/compare.go
Adjust base path in Swagger template to be relative (/api/v1)

GitHub API https://docs.github.com/en/rest/commits/commits?apiVersion=2022-11-28#compare-two-commits

Sorry, the code looks like duplicated to previous blocks.

@lunny Yes, so I remove some unused logic for API

It's better to have an integration test for the API.

@lunny See the testing https://github.com/go-gitea/gitea/pull/30349/files#diff-41e2d9c42fe9e4bf3e8eb44f89eef65b5bc77dfb19c4692092686b4bcf5f5151

Added permission check 6ce81db (#30349)

Sorry, I cannot give my approval since the ParseCompareInfo function is almost copied from https://github.com/go-gitea/gitea/blob/708e87e17df2b6a03eca3cac026a51beed296b5b/routers/web/repo/compare.go#L200-L574
It contains many logics and detailed comments which make me believe it contains complex logic and shouldn't be maintained in two places.

@wolfogre Yes, in the next phase I will refactor the ParseCompareInfo from route/web and route/api.

@wolfogre  @lunny  See the latest commit. https://github.com/go-gitea/gitea/pull/30349/commits/94746ecc56147f2265960d0c140cc314137f74df


allow the use of query variables

@jesucarr thanks for investing the time back then 🙌 I'm closing this PR because it's out of date and cleaning up this repo now. Happy to accept new PR though.


Various De-Bloating Optimisations

Objective
Reduce the binary size of Bevy applications with negligible negative impact on runtime performance.
Solution
Using cargo bloat I identified methods with disproportionately increased the final binary size of Bevy applications, using the 3d_scene as my reference for binary sizes. I then refactored these high-value functions to reduce the amount of code present in generic functions, opting to instead move that code into concrete functions. The exact change varies case by case, but the general transformation involves isolating operations requiring the generic parameter and either evaluating them early or providing them as opaque fn pointers.
In all cases, public APIs are unaffected.
Currently, this has reduced the final size of the 3d_scene example by 2.45MiB, 7.3%. I've kept each refactor in its own commit to allow reviewers to see the specific impact each refactor has on the final binary size (please see the commit descriptions). I will also note that some of these may be more controversial than others, and I am open to removing them if an SME has reasonable objections.
On WASM using the wasm-release profile, the gains are less extreme, 475KiB or 2.0% saved. However, a size reduction of even that magnitude is still sizable considering the wasm-release profile is already optimising for size.
I'm leaving this in a draft state for now while I continue experimenting with refactors. Since these are long-established APIs I don't expect to have much difficulty in keeping this branch updated against main.
Testing

For each function, cargo bloat and my customised analyzer were run to assess the before and after size of the 3d_scene example to ensure changes positively impacted binary size.
CI run locally to ensure tests pass.

Showcase

Bloat Analysis Before: 34142KiB
Total Size: 34142KiB
3.26% 1111KiB: core::ops::function::FnOnce::call_once
2.70% 920KiB: hashbrown::raw::inner::RawTable<T,A>::reserve_rehash
1.70% 578KiB: std::sync::once::Once::call_once_force::{{closure}}
1.17% 398KiB: core::ops::function::impls::<impl core::ops::function::FnMut<A> for &mut F>::call_mut
1.04% 355KiB: bevy_ecs::query::state::QueryState<D,F>::new_with_access
0.95% 324KiB: bevy_reflect::utility::GenericTypeCell<T>::get_or_insert_by_type_id
0.92% 313KiB: <dyn bevy_reflect::reflect::Reflect>::take
0.89% 303KiB: <bevy_ecs::change_detection::ResMut<T> as bevy_ecs::system::system_param::SystemParam>::init_state
0.88% 299KiB: bevy_ecs::system::system::System::run
0.80% 273KiB: <&mut serde_json::de::Deserializer<R> as serde::de::Deserializer>::deserialize_struct
0.75% 255KiB: <bevy_ecs::change_detection::Res<T> as bevy_ecs::system::system_param::SystemParam>::init_state
0.74% 251KiB: bevy_reflect::struct_trait::StructInfo::new
0.72% 245KiB: bevy_ecs::reflect::from_reflect_with_fallback
0.71% 243KiB: bevy_asset::server::impl$0::load_internal::async_fn$0
0.69% 235KiB: bevy_reflect::type_registry::TypeRegistry::register
0.68% 232KiB: <bevy_ecs::system::function_system::FunctionSystem<Marker,F> as bevy_ecs::system::system::System>::run_unsafe
0.64% 218KiB: <bevy_ecs::system::query::Query<D,F> as bevy_ecs::system::system_param::SystemParam>::init_state
0.60% 203KiB: bevy_reflect::enums::enum_trait::EnumInfo::new
0.56% 190KiB: <bevy_ecs::system::function_system::FunctionSystem<Marker,F> as bevy_ecs::system::system::System>::initialize
0.56% 189KiB: <&T as core::fmt::Debug>::fmt
0.54% 183KiB: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter
0.50% 171KiB: bevy_reflect::reflect::PartialReflect::apply
0.49% 167KiB: alloc::sync::Arc<T,A>::drop_slow
0.46% 156KiB: futures_lite::future::block_on
0.46% 156KiB: bevy_ecs::bundle::Bundles::init_info

Bloat Analysis After: 31638KiB
Total Size: 31638KiB
2.75% 870KiB: hashbrown::raw::inner::RawTable<T,A>::reserve_rehash
1.86% 588KiB: std::sync::once::Once::call_once_force::{{closure}}
1.74% 549KiB: core::ops::function::FnOnce::call_once
1.28% 403KiB: core::ops::function::impls::<impl core::ops::function::FnMut<A> for &mut F>::call_mut
1.19% 376KiB: bevy_ecs::query::state::QueryState<D,F>::new_with_access
1.06% 336KiB: bevy_reflect::utility::GenericTypeCell<T>::get_or_insert_by_type_id
0.96% 304KiB: bevy_ecs::system::system::System::run
0.86% 273KiB: <&mut serde_json::de::Deserializer<R> as serde::de::Deserializer>::deserialize_struct
0.76% 239KiB: <bevy_ecs::system::query::Query<D,F> as bevy_ecs::system::system_param::SystemParam>::init_state
0.72% 226KiB: <bevy_ecs::system::function_system::FunctionSystem<Marker,F> as bevy_ecs::system::system::System>::run_unsafe
0.67% 212KiB: <dyn bevy_reflect::reflect::Reflect>::take
0.60% 188KiB: <&T as core::fmt::Debug>::fmt
0.58% 184KiB: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter
0.58% 182KiB: <bevy_ecs::system::function_system::FunctionSystem<Marker,F> as bevy_ecs::system::system::System>::initialize
0.53% 167KiB: alloc::sync::Arc<T,A>::drop_slow
0.49% 156KiB: <&mut ron::de::Deserializer as serde::de::Deserializer>::deserialize_struct
0.44% 137KiB: bevy_reflect::enums::dynamic_enum::DynamicEnum::from_ref
0.43% 136KiB: bevy_reflect::enums::dynamic_enum::impl$6::try_apply
0.43% 136KiB: alloc::collections::btree::node::Handle<alloc::collections::btree::node::NodeRef<alloc::collections::btree::node::marker::Mut,K,V,alloc::collections::btree::node::marker::Leaf>,alloc::collections::btree::node::marker::Edge>::insert_recursing
0.43% 136KiB: bevy_asset::server::impl$0::load_internal_owned::async_fn$0
0.42% 133KiB: hashbrown::raw::RawTable<T,A>::reserve_rehash
0.42% 133KiB: bevy_reflect::reflect::PartialReflect::apply
0.40% 125KiB: futures_lite::future::block_on
0.40% 125KiB: bevy_input::keyboard::_::impl$5::try_apply
0.39% 122KiB: async_task::raw::RawTask<F,T,S,M>::run

After merging in the latest main, fixing documentation, and a few other low-hanging fruit, the current bloat analysis is sitting at 31,898KiB, which is higher than a previous commit by just under 200KiB. From experimentation that appears to be the amount of variance observable from a typical set of changes made to Bevy.
Looking at an expanded bloat summary (below), I think we're at a point now where the "easy" wins are already included in this PR. Anything from an external dependency (std, hashbrown, core, etc.) can't really be directly debloated since we'd need to find all the uses of those types, which becomes additionally challenging since they could be indirectly used by Bevy (e.g., hashbrown::raw::inner::RawTable<T,A>::reserve_rehash is a private function called as an implementation detail in the hashbrown crate). Out of the Bevy controlled functions, the vast majority of the bloat comes from:

PartialReflect and its derived implementation, especially the try_apply method.
FunctionSystem
Query and QueryState

These items aren't trivial to refactor in a way which removes type parameters, since they're deeply intertwined with their types. I do believe it is possible, especially with the PartialReflect trait, but I think it is out of the scope of a general "debloating" PR and should be handled by a more targeted venture.

Current Bloat Analysis: 31898KiB
Total Size: 31898KiB
2.74%    874KiB:         hashbrown::raw::inner::RawTable<T,A>::reserve_rehash
1.85%    591KiB:         std::sync::once::Once::call_once_force::{{closure}}
1.69%    540KiB:         core::ops::function::FnOnce::call_once
1.45%    463KiB:         core::ops::function::impls::<impl core::ops::function::FnMut<A> for &mut F>::call_mut
1.43%    456KiB:         bevy_ecs::query::state::QueryState<D,F>::new_with_access
1.04%    331KiB:         bevy_reflect::utility::GenericTypeCell<T>::get_or_insert_by_type_id
0.94%    300KiB:         bevy_ecs::system::system::System::run
0.86%    273KiB:         <&mut serde_json::de::Deserializer<R> as serde::de::Deserializer>::deserialize_struct
0.67%    212KiB:         <dyn bevy_reflect::reflect::Reflect>::take
0.66%    211KiB:         <bevy_ecs::system::function_system::FunctionSystem<Marker,F> as bevy_ecs::system::system::System>::run_unsafe
0.61%    195KiB:         <bevy_ecs::system::function_system::FunctionSystem<Marker,F> as bevy_ecs::system::system::System>::initialize
0.58%    185KiB:         <&T as core::fmt::Debug>::fmt
0.58%    183KiB:         <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter
0.54%    171KiB:         alloc::sync::Arc<T,A>::drop_slow
0.54%    171KiB:         futures_lite::future::block_on
0.51%    163KiB:         <bevy_ecs::system::query::Query<D,F> as bevy_ecs::system::system_param::SystemParam>::init_state
0.44%    138KiB:         bevy_asset::server::impl$0::load_internal_owned::async_fn$0
0.43%    138KiB:         bevy_reflect::enums::dynamic_enum::impl$6::try_apply
0.43%    136KiB:         alloc::collections::btree::node::Handle<alloc::collections::btree::node::NodeRef<alloc::collections::btree::node::marker::Mut,K,V,alloc::collections::btree::node::marker::Leaf>,alloc::collections::btree::node::marker::Edge>::insert_recursing
0.42%    133KiB:         hashbrown::raw::RawTable<T,A>::reserve_rehash
0.40%    127KiB:         bevy_ecs::query::state::QueryState<D,F>::new_archetype_internal
0.39%    123KiB:         <&mut ron::de::Deserializer as serde::de::Deserializer>::deserialize_struct
0.37%    119KiB:         async_task::raw::RawTask<F,T,S,M>::run
0.37%    117KiB:         bevy_input::keyboard::_::impl$1::type_info::closure$0
0.36%    116KiB:         bevy_color::color::_::impl$5::try_apply
0.36%    113KiB:         bevy_reflect::reflect::PartialReflect::apply
0.35%    112KiB:         core::slice::sort::merge_sort
0.33%    106KiB:         bevy_ecs::schedule::schedule::ScheduleGraph::process_configs
0.33%    106KiB:         bevy_ecs::intern::Interner<T>::intern
0.31%    99KiB:  hashbrown::raw::inner::RawTableInner::drop_inner_table
0.29%    93KiB:  bevy_reflect::reflect::impl$16::fmt
0.27%    87KiB:  bevy_asset::handle::_::<impl bevy_reflect::reflect::PartialReflect for bevy_asset::handle::Handle<A>>::try_apply
0.27%    85KiB:  core::slice::sort::recurse
0.24%    77KiB:  bevy_asset::id::_::<impl bevy_reflect::reflect::PartialReflect for bevy_asset::id::AssetId<A>>::try_apply
0.24%    77KiB:  <core::panic::unwind_safe::AssertUnwindSafe<F> as core::future::future::Future>::poll
0.24%    76KiB:  wgpu_core::command::bundle::RenderBundleEncoder::finish
0.23%    73KiB:  <bevy_ecs::system::function_system::FunctionSystem<Marker,F> as bevy_ecs::system::system::System>::default_system_sets
0.23%    71KiB:  bevy_ecs::system::function_system::SystemState<Param>::new
0.22%    71KiB:  bevy_gltf::loader::load_gltf::async_fn$0
0.22%    70KiB:  <arrayvec::arrayvec::ArrayVec<T,_> as core::iter::traits::collect::FromIterator<T>>::from_iter
0.21%    68KiB:  <bevy_ecs::system::function_system::FunctionSystem<Marker,F> as bevy_ecs::system::system::System>::update_archetype_component_access
0.21%    66KiB:  hashbrown::map::HashMap<K,V,S,A>::insert
0.21%    65KiB:  taffy::compute::grid::track_sizing::resolve_intrinsic_track_sizes<taffy::tree::taffy_tree::TaffyView<enum2$<bevy_ui::measurement::NodeMeasure>,bevy_ui::layout::ui_surface::impl$2::compute_camera_layout::closure_env$0> >
0.21%    65KiB:  bevy_ecs::world::World::resource_scope
0.20%    65KiB:  bevy_ecs::schedule::config::IntoSystemConfigs::in_set
0.20%    64KiB:  wgpu_core::device::queue::<impl wgpu_core::global::Global>::queue_submit
0.20%    62KiB:  bevy_input::keyboard::_::impl$5::try_apply
0.20%    62KiB:  <&mut ron::de::Deserializer as serde::de::Deserializer>::deserialize_tuple
0.19%    62KiB:  bevy_ecs::schedule::schedule::Schedules::add_systems
0.19%    61KiB:  <&mut serde_json::de::Deserializer<R> as serde::de::Deserializer>::deserialize_map

Great effort!  On my laptop it took about 10 minutes per cargo bloat invocation so I hadn't considered a wider investigation as feasible. I was personally hoping to get a larger improvement, but even an (up to) 5% binary reduction seems worth this one-time effort.

Closing this as having missed the train. Not a particularly high priority change, but the techniques are documented here if anyone wishes to try again!


Make container-interop a forwards-compatible polyfill for PSR-11

Per discussion on php-fig/container#38, this patch updates the three shipped interfaces to instead become class aliases for the official PSR-11 interfaces.  This allows implementing libraries to immediately switch to PSR-11 typehints/implementations while retaining backwards compatibility with container-interop.
The patch also includes documentation of workflows for moving from container-interop to PSR-11 for both package and application authors.

Ping @mnapoli and/or @moufmouf

I wonder if abandoned packages can publish new releases to packagist.

I wonder if abandoned packages can publish new releases to packagist.

If they cannot, the maintainers can "un-abandon" it, sync, and then re-abandon.

Looks good, thank you!
Would there be any conflict caused by implementing the same interface twice? (now that these classes are aliases)

@mnapoli Good point. For implementing libraries/projects, this will lead to a fatal error:
PHP Fatal error:  Class Laminas\ServiceManager\ServiceLocatorInterface cannot implement previously implemented interface Psr\Container\ContainerInterface in /laminas/laminas-servicemanager/src/ServiceLocatorInterface.php on line 14

maybe releasing v2.0 of this component would be a good idea rather than having a new minor version. This would provide proper migration path for implementing libraries/components.

Has anyone tried if this trips psalm or phpstan in any way, before we move on with this approach?

@Ocramius there were issues with the laminas-zendframework-bridge but that was due to the fact that the bridge does its magic during request. When used via autoloader, psalm is able to realize that its the exact same interface.
Thus said, when using composer autoloader to provide the alias, we should be good to go. But I can check that tomorrow in a large application using tons of these interfaces.

I've executed this in our project and I receive exactly 1 static-analysis error for this case:
https://psalm.dev/r/d0893a607e
I am actually unsure if thats a bug in psalm as the container mentioned does definitely implement that interface.
When switching the class_alias back to its original, psalm has no issue:
https://psalm.dev/r/5e5acaed94

I think that really needs to be tried out on a playground with an
autoloader, not on psalm.dev
Marco Pivetta
http://twitter.com/Ocramius
http://ocramius.github.com/
On Tue, Aug 17, 2021 at 11:50 AM Maximilian Bösing @.***>
wrote:

I've executed this in our project and I receive exactly 1 static-analysis
error for this case:
https://psalm.dev/r/d0893a607e
I am actually unsure if thats a bug in psalm as the container mentioned
does definitely implement that interface.
When switching the class_alias back to its original, psalm has no issue:
https://psalm.dev/r/5e5acaed94
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/container-interop/container-interop/pull/97#issuecomment-900154468,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABFVEFL34NF6YBD33IEQBLT5IWFZANCNFSM5B4RERSQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

This error is reproduced from the project I have scanned. I just added it to psalm.dev for better understanding on whats going on.
I did added this branch to our composer dependencies, updated, removed the interop Interface from the laminas servicemanager servicelocator and ran psalm.
Do you have something specific in mind when you say that this needs to be tried out on a playground with autoloader?
I can create a dedicated github project 🤷🏼♂

It is indeed an error within psalm which is issued by https://github.com/vimeo/psalm/pull/6325 and will be fixed with https://github.com/vimeo/psalm/pull/6327.

So, @boesing , that sounds like an endorsement of this approach? If so, can you comment, and then @mnapoli can tag and release v2.0.0. :smile:
Thanks, everyone, for working on this - it's nice to finally find a potential way forward that won't cause huge issues for existing users!

@weierophinney Yes, I think from all informations we got, having a new major in here would be the best option for now.
I have a project where another 3rd-party library is using container-interop with the  ^1.1 constraint (which is closed source) and thus, we may have issues in our company to migrate BUT I already reached out to the company which does provide that library. Hopefully they either migrate to 2.0 of container-interop as well (or better, getting rid of container-interop as they only provide the container for their own library).
So I am 100% on-board here, if no one has other feedback or doubts, I think we are good to go.

@mnapoli We have a green light!  Thanks in advance!

I just pinged @moufmouf to get a review from him. This is a v2 so I prefer to find a bit of time to review it, will try to do asap 😓

@moufmouf when tagging 1.3, upstream projects implementing both PSR-11 and interop Interfaces will immediately break.
I wont assume that there are too many projects out there still depending on interop and if so, a smooth transition to PSR can be made when requiring 2.0 of interop.

@moufmouf here are code examples in why it should be a major release
before: https://3v4l.org/B5KL1
after: https://3v4l.org/iPLfM


Camera dosent work

"White noise" on both cameras on Lumia 640DS (build .107)

App doesnt work

Alright, thanks for the issue, both of these are known in other issues, please check before you open a new issue.
Thanks
-Alex


clrDisabled on clrDropdownItem still emits click events

Describe the bug
We have a directive that sets the disabled attribute on controls based on metadata on the object we're displaying.
First of all, this didn't work on clrDropdownItem which is really inconvenient and we needed to hack around that with the clrDisabled property.
Second, after having implemented that, it appeared that users were still able to click the button since it's not actually disabled. This, in my opinion, is a bug since a disabled control should be just disabled and not emitting events.
Our clrDropdownItem look like this
<button
    clrDropdownItem
    [clrDisabled]="getActionMetaData(truckDossier.actionMetaData, 'CanCloseOrderItem')"
    [agidensActionMetadata]="truckDossier.actionMetaData"
    [actionName]="'CanCloseOrderItem'"
    [translationKeyPrefix]="'handling.truckDossier.actionMetaData.messageCodes'"
    (click)="openConfirmCloseDialog(truckDossier)">
    {{ 'handling.truckDossier.menu.close' | translate }}
</button>

while they should look like this, ideally
<button
    clrDropdownItem
    [agidensActionMetadata]="truckDossier.actionMetaData"
    [actionName]="'CanCloseOrderItem'"
    [translationKeyPrefix]="'handling.truckDossier.actionMetaData.messageCodes'"
    (click)="openConfirmCloseDialog(truckDossier)">
    {{ 'handling.truckDossier.menu.close' | translate }}
</button>

How to reproduce
https://stackblitz.com/edit/clarity-v4-dark-theme-eughli
Expected behavior
Not emit click when disabled and it would be nice to just respect a disabled attribute instead of that hideous clrDisabled.
Versions
Clarity project:

[x] Clarity Core
[x] Clarity Angular/UI

Clarity version:

[x] v3.x
[x] v4.x
[x] v5.x

Framework:

[x] Angular

Framework version:
Angular 9 & 11

Hi @sylvaingirardbe,
The disabled attribute seems to work as expected.
https://stackblitz.com/edit/clarity-v4-dark-theme-yver8f?file=src%2Fapp%2Fapp.component.html
Line 20
I'm going to close it cause it is not a bug from our side.


chore(master): release 0.6.0

:robot: I have created a release beep boop
0.6.0 (2024-05-03)
Features

cucumber gradle plugin (#18) (beda224)

Bug Fixes

dir config for GroovyCompiler spock test to avoid storing generated Hello class in the working copy (fc424dc)
RegexParser lazy matcher to handle multiple tags on single line (2d17147)
target-branch, release-please v4.1.0 (fb0cfbe)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/boolivar/jdoc-test/releases/tag/0.6.0 :sunflower:


Add Argilla notebooks using Setfit and HF Inference Endpoints

What does this PR do?

We would like to add two new tutorials:

Add zero-shot text classification suggestions using SetFit: how to implement a zero-shot approach using SetFit to get some initial suggestions for dataset that combines two text classification tasks that include a LabelQuestion and a MultiLabelQuestion.
Create a legal preference dataset: to learn how to use the Notus model on Inference Endpoints to create a legal preference dataset based on RAG instructions from the European AI Act

Issue #55
Image PR here.
Thanks in advance! @MKhalusova

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@davanstrien please take a look.

@davanstrien Thanks for your feedback! I'll check and let you know :)

@davanstrien I made some changes based on your feedback. Let me know what you think! :)

@sdiazlor  Look great! Thanks for making those changes :) @MKhalusova I think this is good to merge, but I'm not familiar with the build system for this, so maybe you want to check toc and index look correct still.

@MKhalusova Thank you for your feedback! I have applied your comments. Let me know if they look good for you!


swamp/tests: node continues sync at latest synced height after stop/start

Store should not be reinitialised after being already initialised
Ref: #457

I made this test on the unit test level btw, not sure if Swamp test will add more value here.


Document all wonka operators.

WiP – just putting this here to let you know I'm nearly done w/ the operators docs @kitten. Hopefully there by end of this week 🎉 A bit too tired to get it all done now 😴

I'll merge this for now, since this has been unmerged for a while, so I can pick up more docs on master :)


Sample Blog Title - CYC Blog

https://yechengchu.github.io/2022/09/07/Sample-Article/
Welcome to my blog!

hhh


Make the date returned by snapshot script friendly

Fixes #3568
Not sure if the right approach. @fabxc @brian-brazil

This change is

@SuperQ @robfig

I'd use hyphens to avoid having both hyphens and underscores.

@brian-brazil Yes, but if you want to convert it back to RFC3339 in some python-script, I think its easier to just replace the _ with :.

ISO 8601 supports a format with no special characters, and is also script friendly. ie.20171210T201116Z

Done


Feature: statements to be run as scheduled

A new field in the config file (modeled on initStatements) could be added, with statements/queries to be run in a scheduled fashion, with the same syntax as the maintenance. Good to do cleanups.

Merged into #20


[Refactor] remove duplicated input object types

Previously, every arithmetic input (with {LT, GT, ...}) has its own input object type, but they are almost the same -- there are only 2 types of such input throughout rumors-api, one is for integers, another for date strings.
This PR replaces these getArithmeticExpressionType calls with 2 input object type instance to simplify the schema. Behavior of rumors-api should not be affected at all.

Unit test on travis is totally broken......


problem releated to the code

In the middle of this picture, the code has a function named "get_files" highlighted in purple clour, Are you use this function to import the background audio files to the jupyter notebook ??

but in jupyter notebook does not highlight the get_files function

You need to run all the cells in the notebook. You can't simply copy a section of code out of the notebook and expect it to work.
What are you trying to do?

What are you trying to do?

Why, Don't want to do that??

 There is a readme file in the model folder where the notebooks are.
You can't just copy bits out of the notebook.

But, as I've said in your other issues, you don't need to run the notebooks if you just want to use the firmware with the current wake word. So I'm not sure what you are trying to do.

But, as I've said in your other issues, you don't need to run the notebooks if you just want to use the firmware with the current wake word. So I'm not sure what you are trying to do.

Ahh ok ok i use the current Wake word for my project, I asked to know that

When I want to make a new wake word am I need to import the background audio files to the jupyter notebook??

You need to look at the notebooks in the GitHub repository and read the code that generates the training dataset. I'm afraid your questions aren't really making any sense to me.

You need to look at the notebooks in the GitHub repository and read the code that generates the training dataset.

ok ok I already looked the code in GitHub but my issue is are you import background audio files to the jupyter notebook, I want a "yes" or "no" answer

Are we need some background audio files for made training data??

Ok, I think I understand what you are asking. There are samples of background noise included in the dataset that you download from here: https://storage.cloud.google.com/download.tensorflow.org/data/speech_commands_v0.02.tar.gz
Follow the instructions in the notebook and extract the file to the speech_data folder.

If you don't want to use background noise then you can comment out that part of the code.

Ok, I think I understand what you are asking. There are samples of background noise included in the dataset that you download from here: https://storage.cloud.google.com/download.tensorflow.org/data/speech_commands_v0.02.tar.gz
Follow the instructions in the notebook and extract the file to the speech_data folder.

Ok tell me why are you use this background audio files??  For code or for training data ??


Update Composer dependencies (2021-12-17-21-11)

Visual regression test passed!
View the visual regression test report


Cloudwatch dimension general token

Literally was cutting a release when this came in.  :)  Cancelled it to look at this one.  Got any others incoming in I should wait for?


support Taproot

The BitBoxApp supports Taproot receive addresses since the last release. BitBoxApp users who use EPS now get warnings like  Address not known to server.
It would be great if they could configure EPS to track Taproot addresses from an xpub/descriptor.

Thanks for the issue.
Good idea. I wasn't aware of BitBox.
Do you know if they have any documentation for their taproot? For example what does the master public key format look like

Currently it's just a plain xpub... string, but we could easily turn it into a descriptor if it helps, e.g. as proposed in https://github.com/spesmilo/electrum/issues/7544#issuecomment-971816165. I don't think anyone plans on continuing with the ypub... and zpub... versioning scheme.

@chris-belcher Let me know as soon as you have a patch. I have exactly this problem and can test it.

It seems internally, descriptors are used already:
https://github.com/chris-belcher/electrum-personal-server/blob/cc3085caf227fc8678e79f24a956fe44e8e6dbfd/electrumpersonalserver/server/deterministicwallet.py#L73
It looks like extending this to accept descriptors directly from the config is the way to go, and would make EPS more flexible and forwards-compatible. @chris-belcher do you plan to work on it?

I don't plan to work on it for at least several months.
I'd prefer not to have the config file use descriptors instead of xpub ypub zpub, because Electrum's GUI doesn't use them. Right now the instructions to Electrum users are simple as they have to click Wallet -> Information and then copypaste the master public key into the config file.

There is no need to remove support for xpub ypub zpub, but it would help to also parse descriptors additionally. Electrum will likely use descriptors as well, at least for their Taproot wallets.
Fyi, Electrum is not the only wallet using Electrum backends, many wallets do.

@chris-belcher I use both wallets (electrum and BitBoxApp). If EPS is not patched, sooner or later I will be forced to use another implementation.
I do not use taproot addresses at the moment. But I can't work with the latest version of BitBoxApp because EPS brings this error and disconnects.

Ah I see, yes adding additional ways to tell EPS about addresses to watch is fine. As long as it continues to work for Electrum users.


[sailfish-secrets] Don't fetch cache passphrase on retry.

Passphrases can be cached as Secrets, so they are not asked everytime. Before asking to enter a passphrase to unlock a GnuPG key, the pinentry is requesting access to a Secret collection to retrieve the passhrase if stored.
This commit disables this cache retrieval if the provided passphrase was erroneous (having an error generates a prompt instruction explaining about the error).
@chriadam may you review ?

It seems somehow suboptimal to use the "prompt is empty" to ascertain that no error occurred during the passphrase step (as that seems like a "side effect").  Could the error value itself be passed somehow to that function?
If not, I am not against merging this as-is, but thought I'd raise the point above for discussion.

GnuPG is passing information to the pinentry as strings, one by one. The C++ object QAssuanServer we have defined is storing these strings internally and when the ask_password command is received, it is creating the appropriated dialog with the stored strings.
Since the prompt object is itself storing strings, I decided to use it instead of a bunch of QStrings as private members to directly store the strings sent by GnuPG. There is (currently) no error related string in prompt, so I used instruction instead to store the error string (GnuPG is not using any instruction semantic as far as I know). I can document this better if you want.
Besides, if you look how Gnome or KDE are handling the GnuPG dialogs (type gpg -s foo to sign a file 'foo' to have a password dialog and enter a wrong passphrase), having actually an error in red colour or something could be quite nice to have: some possible later evolution in lipstick-security-ui ?

Ok.  Yes, there are a few improvements we could do for lipstick-security-ui, certainly.


No matching function

Hi,
I have already install liquid with successes. Examples work properly.
But if I create new cpp script with liquid function I am not able to compile it with cmake and even gcc.
I have errors like:
root@beaglebone:/home/debian/workarea/uhd-<IP_ADDRESS>/host/examples/init_usrp/build# make
[ 50%] Building CXX object CMakeFiles/init_usrp.dir/init_usrp.cpp.o
/home/debian/workarea/uhd-<IP_ADDRESS>/host/examples/init_usrp/init_usrp.cpp:42:16: error: no matching function for call to 'modem_create'
        modem mod   = modem_create(ms);
                      ^~~~~~~~~~~~
/usr/local/include/liquid/liquid.h:2492:7: note: candidate function not viable: requires 2 arguments, but 1 was provided
modem modem_create(modulation_scheme, unsigned int _bits_per_symbol);
      ^
/home/debian/workarea/uhd-<IP_ADDRESS>/host/examples/init_usrp/init_usrp.cpp:43:19: error: no matching function for call to 'modem_create'
    modem demod = modem_create(ms);
                  ^~~~~~~~~~~~
/usr/local/include/liquid/liquid.h:2492:7: note: candidate function not viable: requires 2 arguments, but 1 was provided
modem modem_create(modulation_scheme, unsigned int _bits_per_symbol);
      ^
2 errors generated.
make[2]: *** [CMakeFiles/init_usrp.dir/build.make:63: CMakeFiles/init_usrp.dir/init_usrp.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:73: CMakeFiles/init_usrp.dir/all] Error 2
make: *** [Makefile:84: all] Error 2

I am not able also to compile simple code with gcc or clang. Even if I try to compile the example I have errors.
I use cmake because I will create script with liquid and UHD fof my usrp.
Should I link library? What can I do? May you help me?
lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster
cat /proc/cpuinfo
processor       : 0
model name      : ARMv7 Processor rev 2 (v7l)
BogoMIPS        : 995.32
Features        : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x3
CPU part        : 0xc08
CPU revision    : 2
Hardware        : Generic AM33XX (Flattened Device Tree)
Revision        : 0000
Serial          : 4219BBBK05E9

My CMakeLists.txt
`

Copyright 2014-2015 Ettus Research LLC
Copyright 2018 Ettus Research, a National Instruments Company

SPDX-License-Identifier: GPL-3.0

cmake_minimum_required(VERSION 2.8)
include_directories(include /usr/local/include/liquid/)
Set up build environment
Choose a static or shared-library build (shared is default, and static will
probably need some special care!)
Set this to ON in order to link a static build of UHD:
option(UHD_USE_STATIC_LIBS OFF)
This example also requires Boost:
set(BOOST_REQUIRED_COMPONENTS
program_options
system
thread
)
if(MSVC)
set(BOOST_ALL_DYN_LINK "${BOOST_ALL_DYN_LINK}" CACHE BOOL "boost enable dynamic linking")
if(BOOST_ALL_DYN_LINK)
add_definitions(-DBOOST_ALL_DYN_LINK) #setup boost auto-linking in msvc
else(BOOST_ALL_DYN_LINK)
set(BOOST_REQUIRED_COMPONENTS) #empty components list for static link
endif(BOOST_ALL_DYN_LINK)
endif(MSVC)
find_package(Boost "1.46" REQUIRED ${BOOST_REQUIRED_COMPONENTS})
To add UHD as a dependency to this project, add a line such as this:
find_package(UHD "3.8.0" REQUIRED)
The version in  ^^^^^  here is a minimum version.
To specify an exact version:
#find_package(UHD 3.8.1 EXACT REQUIRED)
Configure Compiler
if(CMAKE_VERSION VERSION_LESS "3.1")
if(${CMAKE_CXX_COMPILER_ID} STREQUAL "GNU")
set(CMAKE_CXX_FLAGS "--std=gnu++11 ${CMAKE_CXX_FLAGS}")
elseif(${CMAKE_CXX_COMPILER_ID} STREQUAL "Clang")
if("${IS_APPLE}" STREQUAL "")
set(CMAKE_CXX_FLAGS "-std=c++11 ${CMAKE_CXX_FLAGS}")
else()
set(CMAKE_CXX_FLAGS "-std=c++11 -stdlib=libc++ ${CMAKE_CXX_FLAGS}")
endif()
endif()
else()
set(CMAKE_CXX_STANDARD 11)
endif()
if(CMAKE_SYSTEM_NAME STREQUAL "FreeBSD" AND ${CMAKE_CXX_COMPILER_ID} STREQUAL "Clang")
set(CMAKE_EXE_LINKER_FLAGS "-lthr ${CMAKE_EXE_LINKER_FLAGS}")
set(CMAKE_CXX_FLAGS "-stdlib=libc++ ${CMAKE_CXX_FLAGS}")
endif()
include_directories(
${Boost_INCLUDE_DIRS}
${UHD_INCLUDE_DIRS}
)
link_directories(${Boost_LIBRARY_DIRS})
Make the executable
add_executable(init_usrp init_usrp.cpp)
set(CMAKE_BUILD_TYPE "Release")
message(STATUS "")
message(STATUS " NOTE: When building your own app, you probably need all kinds of different  ")
message(STATUS " compiler flags. This is just an example, so it's unlikely these settings    ")
message(STATUS " exactly match what you require. Make sure to double-check compiler and     ")
message(STATUS " linker flags to make sure your specific requirements are included.          ")
message(STATUS "****")
Shared library case: All we need to do is link against the library, and
anything else we need (in this case, some Boost libraries):
if(NOT UHD_USE_STATIC_LIBS)
message(STATUS "Linking against shared UHD library.")
target_link_libraries(init_usrp ${UHD_LIBRARIES} ${Boost_LIBRARIES})
Shared library case: All we need to do is link against the library, and
anything else we need (in this case, some Boost libraries):
else(NOT UHD_USE_STATIC_LIBS)
message(STATUS "Linking against static UHD library.")
target_link_libraries(init_usrp
# We could use ${UHD_LIBRARIES}, but linking requires some extra flags,
# so we use this convenience variable provided to us
${UHD_STATIC_LIB_LINK_FLAG}
# Also, when linking statically, we need to pull in all the deps for
# UHD as well, because the dependencies don't get resolved automatically
${UHD_STATIC_LIB_DEPS}
)
endif(NOT UHD_USE_STATIC_LIBS)
Once it's built...
Here, you would have commands to install your program.
We will skip these in this example.
`

My CMakeLists.txt
`

Copyright 2014-2015 Ettus Research LLC
Copyright 2018 Ettus Research, a National Instruments Company

SPDX-License-Identifier: GPL-3.0

cmake_minimum_required(VERSION 2.8)
include_directories(include /usr/local/include/liquid/)
Set up build environment
Choose a static or shared-library build (shared is default, and static will
probably need some special care!)
Set this to ON in order to link a static build of UHD:
option(UHD_USE_STATIC_LIBS OFF)
This example also requires Boost:
set(BOOST_REQUIRED_COMPONENTS
program_options
system
thread
)
if(MSVC)
set(BOOST_ALL_DYN_LINK "${BOOST_ALL_DYN_LINK}" CACHE BOOL "boost enable dynamic linking")
if(BOOST_ALL_DYN_LINK)
add_definitions(-DBOOST_ALL_DYN_LINK) #setup boost auto-linking in msvc
else(BOOST_ALL_DYN_LINK)
set(BOOST_REQUIRED_COMPONENTS) #empty components list for static link
endif(BOOST_ALL_DYN_LINK)
endif(MSVC)
find_package(Boost "1.46" REQUIRED ${BOOST_REQUIRED_COMPONENTS})
To add UHD as a dependency to this project, add a line such as this:
find_package(UHD "3.8.0" REQUIRED)
The version in  ^^^^^  here is a minimum version.
To specify an exact version:
#find_package(UHD 3.8.1 EXACT REQUIRED)
Configure Compiler
if(CMAKE_VERSION VERSION_LESS "3.1")
if(${CMAKE_CXX_COMPILER_ID} STREQUAL "GNU")
set(CMAKE_CXX_FLAGS "--std=gnu++11 ${CMAKE_CXX_FLAGS}")
elseif(${CMAKE_CXX_COMPILER_ID} STREQUAL "Clang")
if("${IS_APPLE}" STREQUAL "")
set(CMAKE_CXX_FLAGS "-std=c++11 ${CMAKE_CXX_FLAGS}")
else()
set(CMAKE_CXX_FLAGS "-std=c++11 -stdlib=libc++ ${CMAKE_CXX_FLAGS}")
endif()
endif()
else()
set(CMAKE_CXX_STANDARD 11)
endif()
if(CMAKE_SYSTEM_NAME STREQUAL "FreeBSD" AND ${CMAKE_CXX_COMPILER_ID} STREQUAL "Clang")
set(CMAKE_EXE_LINKER_FLAGS "-lthr ${CMAKE_EXE_LINKER_FLAGS}")
set(CMAKE_CXX_FLAGS "-stdlib=libc++ ${CMAKE_CXX_FLAGS}")
endif()
include_directories(
${Boost_INCLUDE_DIRS}
${UHD_INCLUDE_DIRS}
)
link_directories(${Boost_LIBRARY_DIRS})
Make the executable
add_executable(init_usrp init_usrp.cpp)
set(CMAKE_BUILD_TYPE "Release")
message(STATUS "")
message(STATUS " NOTE: When building your own app, you probably need all kinds of different  ")
message(STATUS " compiler flags. This is just an example, so it's unlikely these settings    ")
message(STATUS " exactly match what you require. Make sure to double-check compiler and     ")
message(STATUS " linker flags to make sure your specific requirements are included.          ")
message(STATUS "****")
Shared library case: All we need to do is link against the library, and
anything else we need (in this case, some Boost libraries):
if(NOT UHD_USE_STATIC_LIBS)
message(STATUS "Linking against shared UHD library.")
target_link_libraries(init_usrp ${UHD_LIBRARIES} ${Boost_LIBRARIES})
Shared library case: All we need to do is link against the library, and
anything else we need (in this case, some Boost libraries):
else(NOT UHD_USE_STATIC_LIBS)
message(STATUS "Linking against static UHD library.")
target_link_libraries(init_usrp
# We could use ${UHD_LIBRARIES}, but linking requires some extra flags,
# so we use this convenience variable provided to us
${UHD_STATIC_LIB_LINK_FLAG}
# Also, when linking statically, we need to pull in all the deps for
# UHD as well, because the dependencies don't get resolved automatically
${UHD_STATIC_LIB_DEPS}
)
endif(NOT UHD_USE_STATIC_LIBS)
Once it's built...
Here, you would have commands to install your program.
We will skip these in this example.
`

The error says everything you need to know. You are calling modem_create like
modem mod   = modem_create(ms);

but it requires two parameters, modulation scheme (which I assume is what your ms argument), and bits/symbol which you are not providing:
modem mod  modem_create(ms, /* add an argument for bits per symbol here */ );

The error says everything you need to know. You are calling modem_create like
modem mod   = modem_create(ms);

but it requires two parameters, modulation scheme (which I assume is what your ms argument), and bits/symbol which you are not providing:
modem mod  modem_create(ms, /* add an argument for bits per symbol here */ );

@JayKickliter  thank you. It helped me. But I still have problem with compiling.
root@beaglebone:/home/debian/workarea/uhd-<IP_ADDRESS>/host/examples/init_usrp/build# make Scanning dependencies of target init_usrp [ 50%] Building CXX object CMakeFiles/init_usrp.dir/init_usrp.cpp.o [100%] Linking CXX executable init_usrp /usr/bin/ld: CMakeFiles/init_usrp.dir/init_usrp.cpp.o: in functionmain':
init_usrp.cpp:(.text+0x90): undefined reference to windowf_create' /usr/bin/ld: init_usrp.cpp:(.text+0xa0): undefined reference to modem_create'
/usr/bin/ld: init_usrp.cpp:(.text+0xb0): undefined reference to modem_create' /usr/bin/ld: init_usrp.cpp:(.text+0xf0): undefined reference to windowf_push'
/usr/bin/ld: init_usrp.cpp:(.text+0x124): undefined reference to windowf_push' /usr/bin/ld: init_usrp.cpp:(.text+0x158): undefined reference to windowf_push'
/usr/bin/ld: init_usrp.cpp:(.text+0x18c): undefined reference to windowf_push' /usr/bin/ld: init_usrp.cpp:(.text+0x1c0): undefined reference to windowf_push'
/usr/bin/ld: CMakeFiles/init_usrp.dir/init_usrp.cpp.o:init_usrp.cpp:(.text+0x1f4): more undefined references to windowf_push' follow /usr/bin/ld: CMakeFiles/init_usrp.dir/init_usrp.cpp.o: in function main':
init_usrp.cpp:(.text+0x2d0): undefined reference to windowf_read' /usr/bin/ld: init_usrp.cpp:(.text+0x4f8): undefined reference to windowf_destroy'
/usr/bin/ld: init_usrp.cpp:(.text+0x500): undefined reference to modem_destroy' /usr/bin/ld: init_usrp.cpp:(.text+0x508): undefined reference to modem_destroy'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [CMakeFiles/init_usrp.dir/build.make:91: init_usrp] Error 1
make[1]: *** [CMakeFiles/Makefile2:73: CMakeFiles/init_usrp.dir/all] Error 2
make: *** [Makefile:84: all] Error 2
`
My library: #include <uhd/utils/thread.hpp> #include <uhd/utils/safe_main.hpp> #include <uhd/utils/static.hpp> #include <uhd/usrp/multi_usrp.hpp> #include <uhd/exception.hpp> #include <boost/program_options.hpp> #include <boost/math/special_functions/round.hpp> #include <boost/format.hpp> #include <boost/algorithm/string.hpp> #include <stdint.h> #include <iostream> #include <csignal> #include <string> #include <chrono> #include <thread> #include <stdlib.h> #include <stdio.h> #include <getopt.h> #include <liquid/liquid.h> #include <complex>
What about reference problem?

@JayKickliter  thank you. It helped me. But I still have problem with compiling.
root@beaglebone:/home/debian/workarea/uhd-<IP_ADDRESS>/host/examples/init_usrp/build# make Scanning dependencies of target init_usrp [ 50%] Building CXX object CMakeFiles/init_usrp.dir/init_usrp.cpp.o [100%] Linking CXX executable init_usrp /usr/bin/ld: CMakeFiles/init_usrp.dir/init_usrp.cpp.o: in functionmain':
init_usrp.cpp:(.text+0x90): undefined reference to windowf_create' /usr/bin/ld: init_usrp.cpp:(.text+0xa0): undefined reference to modem_create'
/usr/bin/ld: init_usrp.cpp:(.text+0xb0): undefined reference to modem_create' /usr/bin/ld: init_usrp.cpp:(.text+0xf0): undefined reference to windowf_push'
/usr/bin/ld: init_usrp.cpp:(.text+0x124): undefined reference to windowf_push' /usr/bin/ld: init_usrp.cpp:(.text+0x158): undefined reference to windowf_push'
/usr/bin/ld: init_usrp.cpp:(.text+0x18c): undefined reference to windowf_push' /usr/bin/ld: init_usrp.cpp:(.text+0x1c0): undefined reference to windowf_push'
/usr/bin/ld: CMakeFiles/init_usrp.dir/init_usrp.cpp.o:init_usrp.cpp:(.text+0x1f4): more undefined references to windowf_push' follow /usr/bin/ld: CMakeFiles/init_usrp.dir/init_usrp.cpp.o: in function main':
init_usrp.cpp:(.text+0x2d0): undefined reference to windowf_read' /usr/bin/ld: init_usrp.cpp:(.text+0x4f8): undefined reference to windowf_destroy'
/usr/bin/ld: init_usrp.cpp:(.text+0x500): undefined reference to modem_destroy' /usr/bin/ld: init_usrp.cpp:(.text+0x508): undefined reference to modem_destroy'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [CMakeFiles/init_usrp.dir/build.make:91: init_usrp] Error 1
make[1]: *** [CMakeFiles/Makefile2:73: CMakeFiles/init_usrp.dir/all] Error 2
make: *** [Makefile:84: all] Error 2
`
My library: #include <uhd/utils/thread.hpp> #include <uhd/utils/safe_main.hpp> #include <uhd/utils/static.hpp> #include <uhd/usrp/multi_usrp.hpp> #include <uhd/exception.hpp> #include <boost/program_options.hpp> #include <boost/math/special_functions/round.hpp> #include <boost/format.hpp> #include <boost/algorithm/string.hpp> #include <stdint.h> #include <iostream> #include <csignal> #include <string> #include <chrono> #include <thread> #include <stdlib.h> #include <stdio.h> #include <getopt.h> #include <liquid/liquid.h> #include <complex>
What about reference problem?

That's definitely a linker error. It seems as though it isn't finding libliquid.so

That's definitely a linker error. It seems as though it isn't finding libliquid.so

Try adding target_link_libraries(<YOUR_TARGET_NAME>, liquid)

Try adding target_link_libraries(<YOUR_TARGET_NAME>, liquid)

I added this line to CMakeLists.txt:
target_link_libraries(init_usrp liquid)
Where init_usrp is the name of my targed.
It helped, Now I am able to compile scripts.
Thank you for your help.

I added this line to CMakeLists.txt:
target_link_libraries(init_usrp liquid)
Where init_usrp is the name of my targed.
It helped, Now I am able to compile scripts.
Thank you for your help.

This can be closed.


Remove some unsafe in the wgctrl-sys kernel backend

After reading the code a bit, I saw a bit of unsafe that caught my eye.
The previous device name parsing could potentially lead to UB since it doesn't look like Wireguard nor Netlink care about if the interface name is valid ASCII or UTF-8 and str::from_utf8_unchecked was being used. I made an InterfaceName wrapper struct to help validate interface names better and to ensure nothing weird happens passing the interface name around.
It also made converting the interface names cheaper since its just copies some bytes now. I also added some basic validation for interface name creation to prevent data that's going to be rejected anyway from making it across the FFI. As part of the newtype I moved the magic 16 constant to use the same libc constant that the Wireguard headers do for interfaces max length.
Also thanks for open sourcing this, its a very cool project and I look forward to using it in one of my setups :D

Finally got the tests passing too /o/


docs for APIs updated to resonate with fusionauth docs

Summary by CodeRabbit

Documentation

Enhanced OTP Service documentation with detailed request parameters and response codes.
Updated terminology in Application Service documentation from "FusionAuth" to "Auth Service."
Reorganized Key Management API documentation for better readability.
Refined Refresh Tokens documentation with expanded endpoint details and examples.
Improved Group Management documentation by refactoring endpoint structure and adding detailed request/response information.
Reorganized Tenant Management documentation with clear endpoint groupings.
Refined User Service documentation for better clarity and comprehensive endpoint details.

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
:information_source: You can also turn on project coverage checks and project coverage reporting on Pull Request comment
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Rename px to proxmox

Is your feature request related to a problem? Please describe.
px is not a very descriptive name.
Describe the solution you'd like
I would recommend to rename the role to ansible-role-proxmox-lxc
Additional context
Thank you for this ansible role. This is the only role I found online which supports multiple containers at once and is not bloated with other stuff like downloading templates etc etc. I hope you keep it like that.

I suggest some additional renaming to support other roles like some ansible-role-proxmox-kvm without the requirement to duplicate variables
px_lxc_api_user -> proxmox_api_user
px_lxc_api_password -> proxmox_api_password
px_lxc_proxmox_host -> proxmox_api_host

Hi @tabic, thanks for the feedback!
I agree that renaming the role would make sense. On my local machine, px became an equivalent for Proxmox in many places, but it's really not very descriptive.
About renaming some variables: As there is currently no KVM role planned, I wouldn't like to change them. The way they are, the name reflects clearly to what role a variable belongs and ensures that no namespace issues occur with some other third party role. Also, I'm not sure whether there are cases in which you have dedicated credentials for either managing LXCs or KVMs. In this case, you wouldn't want this namespace collision.
You can still do something like this:
proxmox_api_user: foo
proxmox_lxc_api_user: "{{ proxmox_api_user }}"
proxmox_kvm_api_user: "{{ proxmox_api_user }}"

Good point, makes sense!

This was resolved in #2. I have released a new version 2.0.0 which can be downloaded here: https://galaxy.ansible.com/bellackn/proxmox_lxc


Notifications don't always come through (actually they mostly don't). I'm on macOS High Sierra 10.13.3. We've now resorted to sending each other messages through Slack to say there's a new message on KeyBase ...

Keybase GUI Version: 1.0.44-20180223192708+9a9ccec79

Same in windows; If you click the task bar icon you can see the red dot when the agent window pops up; otherwise its eerie silence. I have to rely on my phone buzzing.


Indicate when it is too early to click after crossing an Agility Course Obstacle

Wasted clicks are extremely frustrating and when added up can really demoralize the grind; I think something as simple as changing the cursor from red (indicating that it is too early for a click to be registered successfully) to green (when you're all clear for the next click) would help to remedy this in most cases.
This could also help in many other scenarios besides the Agility Courses example, as it the same logic could apply anywhere multiple sequential clicks are required, but may not register if you do it at the wrong times such as with Performing High Alchemy and not being able to casts it again until the xp drop is finished or using the Humidify spell followed by trying to bank too soon into the animation.
I apologize if this has been requested before under a different name or with different wording, and I hope this will be of some interest to anyone else =).

I feel we should not add such a feature. Generally speaking, agility courses (and most other activities) will have XP drops when an action is completed which can signal to players when they can interact with something afterward.

I feel we should not add such a feature. Generally speaking, agility courses (and most other activities) will have XP drops when an action is completed which can signal to players when they can interact with something afterward.

That is a valid point, however, it is important to note that the xp drop cannot always be used reliably (especially late at night or after longer sessions), and unless I am mistaken, with different methods having different tick speeds that will also influence how far the xp drop has to travel before you can click again, making it even more difficult to keep track of across skills/activities.
What I liked about my suggestion was that unlike the former, this visual indicator is absolute, it can only be red or green, nothing in between; Ultimately, timing clicks properly will still be up to the player to perform correctly, this just helps to remove the guesswork in between clicks, which would be excellent for longer sessions when you can't quite keep up so well as that first hour.
Obviously, this is not a priority to implement in the grand scheme of things, and as you mentioned, the xp drop method more or less provides the same utility, but I stand by my point of this being a potentially nice QOL improvement over using XP drops as a visual aid to skilling.

with different methods having different tick speeds that will also influence how far the xp drop has to travel before you can click again

Can you elaborate on that? I can't speak for everyone, but I'd prefer to see more specific examples fitting this criteria to justify a feature which implements this. (which aren't covered by using the "Fake XP Drop" feature of the XP Drop plugin)

Duplicate of https://github.com/runelite/runelite/issues/4717


Fix string/boolean parsing regression with null

Related issue
Fixes https://github.com/microsoft/AdaptiveCards/issues/3436
Please refer to the issue for a full description of the problem.
How verified
Verified manually (test card can be found here: https://github.com/microsoft/AdaptiveCards/blob/master/samples/v1.0/Tests/NullValuesAreAccepted.json)
Microsoft Reviewers: Open in CodeFlow

Hey David, do we know when this was regressed? 1.2 or prior?

Can you also include this payload as a test card in our samples folder - @rebeccaanne, can you help guide where such a card would exist? Thanks

In reply to: 530586405 [](ancestors = 530586405)

I suppose since this applies to all versions, the https://github.com/microsoft/AdaptiveCards/tree/master/samples/v1.0/Tests folder would be a good place to add this card.

In reply to: 530586712 [](ancestors = 530586712,530586405)

I unfortunately don't know when the regression was introduced. I have added the card to the samples folder.

Thanks ; @dclaux, once you are able to do that please go ahead update the ##how verified section to include the reference to the new sample card created as well. (Also minor nit can you include the headings when you use the PR template for descriptions? ) THanks

In reply to: 530588425 [](ancestors = 530588425,530586712,530586405)

Thanks - @RebeccaAnne, anything else that's needed here as part of adding hte new sample card?

In reply to: 530590567 [](ancestors = 530590567)

Done

@paulcam206 what's up with hte failed .NET PR build ? Could you help? Tx

Also @dclaux, you call it a "hotfix" where is this going to be patched to?

I call it hotfix because it's a quick fix that is time sensitive given Teams needs it... it will be applied to master like any other fix.

Ideally the new card would be run against the UWP test app to set baseline results. David, let me know if you'd like pointers on how to do that. Alternatively, we can log a bug to do that in a separate change.

In reply to: 530590809 [](ancestors = 530590809,530590567)

I call it hotfix because it's a quick fix that is time sensitive given Teams needs it... it will be applied to master like any other fix.

Hmm I see ; So for these issues, remember to use the Msft-TeamsIntegration label for now to the issue please (I added it right now); Does Teams Web/Desktop pick up the latest greatest off of master or do they pull the released packages (my understanding was the latter); For patching we'd need to ensure we backport the changes but since npm is lagging way behind the other platforms anyways we'll be able to push this through as part of the Sept patch we are working towards end of this month. (So it would likely be version 1.2.3)

test failure due to new test card being added:
Starting test execution, please wait...
Failed   TestAllTestCards
Error Message:
 Test method AdaptiveCards.Test.AllPayloadTests.TestAllTestCards threw exception:
System.AggregateException: One or more errors occurred. (Payload file failed: NullValuesAreAccepted.json) ---> System.Exception: Payload file failed: NullValuesAreAccepted.json ---> System.NullReferenceException: Object reference not set to an instance of an object.
Stack Trace:
    at AdaptiveCards.IgnoreDefaultStringEnumConverter`1.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer) in C:\BA\795\s\source\dotnet\Library\AdaptiveCards\IgnoreDefaultStringEnumConverter.cs:line 40
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter converter, JsonReader reader, Type objectType, Object existingValue)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.SetPropertyValue(JsonProperty property, JsonConverter propertyConverter, JsonContainerContract containerContract, JsonProperty containerProperty, JsonReader reader, Object target)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Populate(JsonReader reader, Object target)
   at AdaptiveCards.AdaptiveTypedElementConverter.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer) in C:\BA\795\s\source\dotnet\Library\AdaptiveCards\AdaptiveTypedElementConverter.cs:line 100
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter converter, JsonReader reader, Type objectType, Object existingValue)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
   at AdaptiveCards.IgnoreEmptyItemsConverter`1.<>c__DisplayClass1_0.<ReadJson>b__1(JObject obj) in C:\BA\795\s\source\dotnet\Library\AdaptiveCards\IgnoreEmptyItemsConverter.cs:line 27
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.ToList()
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at AdaptiveCards.IgnoreEmptyItemsConverter`1.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer) in C:\BA\795\s\source\dotnet\Library\AdaptiveCards\IgnoreEmptyItemsConverter.cs:line 25
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter converter, JsonReader reader, Type objectType, Object existingValue)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.SetPropertyValue(JsonProperty property, JsonConverter propertyConverter, JsonContainerContract containerContract, JsonProperty containerProperty, JsonReader reader, Object target)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Populate(JsonReader reader, Object target)
   at AdaptiveCards.AdaptiveTypedElementConverter.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer) in C:\BA\795\s\source\dotnet\Library\AdaptiveCards\AdaptiveTypedElementConverter.cs:line 100
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter converter, JsonReader reader, Type objectType, Object existingValue)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
   at AdaptiveCards.IgnoreEmptyItemsConverter`1.<>c__DisplayClass1_0.<ReadJson>b__1(JObject obj) in C:\BA\795\s\source\dotnet\Library\AdaptiveCards\IgnoreEmptyItemsConverter.cs:line 27
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.ToList()
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at AdaptiveCards.IgnoreEmptyItemsConverter`1.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer) in C:\BA\795\s\source\dotnet\Library\AdaptiveCards\IgnoreEmptyItemsConverter.cs:line 25
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter converter, JsonReader reader, Type objectType, Object existingValue)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.SetPropertyValue(JsonProperty property, JsonConverter propertyConverter, JsonContainerContract containerContract, JsonProperty containerProperty, JsonReader reader, Object target)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Populate(JsonReader reader, Object target)
   at AdaptiveCards.AdaptiveTypedElementConverter.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer) in C:\BA\795\s\source\dotnet\Library\AdaptiveCards\AdaptiveTypedElementConverter.cs:line 100
   at AdaptiveCards.AdaptiveCardConverter.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer) in C:\BA\795\s\source\dotnet\Library\AdaptiveCards\AdaptiveCardConverter.cs:line 54
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter converter, JsonReader reader, Type objectType, Object existingValue)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
   at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
   at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
   at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
   at AdaptiveCards.AdaptiveCard.FromJson(String json) in C:\BA\795\s\source\dotnet\Library\AdaptiveCards\AdaptiveCard.cs:line 247
   at AdaptiveCards.Test.AllPayloadTests.TestPayloadsInDirectory(String path, String[] excludedCards) in C:\BA\795\s\source\dotnet\test\AdaptiveCards.Test\AllPayloadTests.cs:line 55
--- End of inner exception stack trace ---
    at AdaptiveCards.Test.AllPayloadTests.TestPayloadsInDirectory(String path, String[] excludedCards) in C:\BA\795\s\source\dotnet\test\AdaptiveCards.Test\AllPayloadTests.cs:line 90
   at AdaptiveCards.Test.AllPayloadTests.TestAllTestCards() in C:\BA\795\s\source\dotnet\test\AdaptiveCards.Test\AllPayloadTests.cs:line 111

In reply to: 530592123 [](ancestors = 530592123)

How can I easily and quickly test in the UWP test app?

Teams pulls the nightly builds right now because they can't wait until we're ready to publish new packages.

@RebeccaAnne / @paulcam can you work with David today to get him unblocked and as part of this let's document what it takes to add a new sample card and CI implications/troubleshooting.

In reply to: 530594077 [](ancestors = 530594077)

If you don't mind I don't think there is a good reason to hold this PR. We can run the UWP test app separately. If it's OK with everyone, I will merge (and ignore the .NET error)

We can't have a new card that breaks CI checked in to the repo.

If you don't mind I don't think there is a good reason to hold this PR. We can run the UWP test app separately. If it's OK with everyone, I will merge (and ignore the .NET error)

Hey can you give folks some time to help figure this out? This will result in a build break as-is without addressing the CI break.

I think the right thing to do for now is to remove the new test card to avoid the build break. We can add it back, along with whatever else needs to be done, as a separate issue/PR. How does that sound?

How can I easily and quickly test in the UWP test app?

[These instructions are for UWP, and will help us keep our UWP test app clean. This will not address the .NET CI issue (I can look into that in a minute)]

Open https://github.com/microsoft/AdaptiveCards/blob/master/source/uwp/AdaptiveCards.sln in Visual Studio.
Choose AdaptiveCardTestApp from the pulldown and run it (F5)

Click the "Cards" header to deselect all cards:

Scroll down and select your new card:

Click Start Test on the bottom of the test app.
The test app should show the rendered card as follows for each host config:

If the card shows an error, please log an issue against UWP to follow up (you can assign it to me).
Whether or not the card renders, select "Accept all changes" at the top of the app:

Commit the generated files to github

For the .NET break:

Open https://github.com/microsoft/AdaptiveCards/blob/master/source/dotnet/Test/AdaptiveCards.Test/AllPayloadTests.cs
In TestAllTestCards(), update the array of cards that is expected to fail to include your new card:

            TestPayloadsInDirectory(Path.Combine(SamplesPath, "v1.0", "tests"),
                new string[]
                {
                    // These cards are expected to fail
                    "TypeIsRequired",
                    "AdaptiveCard.MissingVersion",
                    "NullValuesAreAccepted.json"
                });

Log an issue against .NET for this card

I'll let Shalini speak to whether she has a strong preference that the sample be part of this change or a separate one (although please log an issue if it doesn't go in with this). My only request would be that whenever it does go in, this .NET issue (and one against UWP if it also fails) are logged before the sample goes in so we don't lose track of it.

Log an issue against .NET for this card
I logged #3439


Children Resize

I'm using this React-mansory-component library and it's very useful except one thing.
The height of my elements in the layout can be increased or decreased (It has edit button and if it is clicked, the edit form appears at the bottom of element)
In this case, Mansory changes the position of elements. I want to stop this.
Please let me know the solution for this.

Have you tried the stamp method from Masonry?

I'm using this React-mansory-component library and it's very useful except one thing.
The height of my elements in the layout can be increased or decreased (It has edit button and if it is clicked, the edit form appears at the bottom of element)
In this case, Mansory changes the position of elements. I want to stop this.
Please let me know the solution for this.

Add the prop enableResizableChildren={true}.


Support Dataset labels and Project#datasets filter param

Add CRUD methods for Dataset labels. Also add a filter param for labels filtering to Project#datasets.
See Labels overview and Labeling datasets.

Closed by #1681.


A problem about multi-GPU training

When I use multi-GPU training, the result is lower than that of single one. What is the reason for this? does it have anything to do with accelerate?

Apologies for the delayed response. Have you been able to solve the problem?
If not, could you provide the command you used so I can take a closer look?
Thank you for your interest in our work!