broken images showing after migrating django site to localhost.

on production server images was working fine but when i migrated it to localhost it is displaying broken images and image path is showing like this.
src="/media/cache/da/d5/dad54510386c9cb699f5fff4a772e240.png"
and this file is not present in the cache directory.

+1
I have the same problem with a fresh install of dajngo 1.9

It's realated with https://github.com/mariocesar/sorl-thumbnail/issues/448, it's my problem too in Django 1.9.3.

@sandeepwisecells @pablovg2 are both using the latest dev version?  pip install --pre sorl-thumbnail

Now, i'm using the current pip version, but, i'll twy to test with the dev version.


Release the new version (Qulice updated)

Subj.

@rultor release, tag is 1.0.2

@rultor release, tag is 1.0.2

@kniazkov OK, I will release it now. Please check the progress here

@rultor release, tag is 1.0.2

@kniazkov Done! FYI, the full log is here (took me 13min)

@rultor release, tag is 1.0.3

@rultor release, tag is 1.0.3

@kniazkov Done! FYI, the full log is here (took me 8min)


I have been looking for this kind of responsitory for 10 years

Thank you man

🙌🏻🙌🏻🙌🏻 let me know if you find something interesting using ManuFuzzer. Will add it to trophies :)


fix: set passive to true for scroll event listener in ProgressiveLoadingContainer [DHIS2-9508]

A minor optimization that probably won't have much impact on the performance, but nevertheless doesn't have a negative impact.
Changes include:

do not add eventListener on the window
set passive: true on the event listener (see explanation here: https://web.dev/uses-passive-event-listeners/?utm_source=lighthouse&utm_medium=devtools)

Code looks good to me - we're sure the window handler is unnecessary? Probably is...

I tested the dashboard scroll in Chrome, FF, and Safari. When I get access, will also test with Edge. So far the scrolling works.
Can you think of a reason why we would need the event listener on window?

No, I think I just added it as a fallback - in full-screen layouts we shouldn't have any window scroll events


feat: add section component

with this feature, authors can create components to get feedback from readers or share their posts easily

Please add a test to blog_test.tsx for this change

done


Update ns-winuser-rawmouse.md

Add more info on ulRawButtons from https://docs.microsoft.com/en-us/windows/win32/api/ntddmou/ns-ntddmou-mouse_input_data
Also add more related reference links.

@DJm00n : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@jwmsft any updates on this?

@DJm00n, there's a merge conflict that I haven't had a chance to sort through yet. If you'd like to take a look at resolving the conflict, please feel free. Otherwise, I'll try to get to it soon. Thanks.

@DJm00n : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@DJm00n : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Rebased with -Xignore-all-space option.

Thanks!


boolean type

Is your feature request related to a problem? Please describe.
I was trying to create a schema but the boolean type was missing
Describe the solution you'd like
Adding the boolean type
Describe alternatives you've considered
Using ints
Additional context
I could make a pull request to add this if you want me to.

SQLite does not have a native boolean type, it instead casts it to an int. It's difficult to provide type safety for this, though I'm open to suggestions

If you come up with something, please let me know 🙂
Will close as not planned for now

This is in fact being worked on in #43, will reopen


What movement mods can be disabled?

Hey folks, not sure if its my pc or the settings but I find the movement is very strange. When I tap W its super responsive, the camera and charachter overly lurge forward. Its the camera moving with it, its very strange. I downloaded this pack because it said it was mainly graphical updates, dont want anything but graphics so wondering if I can disable the movement mod?

You can't disable the behavior movement mod without having to rerun Nemesis. So I do not recommend it unless you know what you are doing.


Move the qr code generated from the sdk at https://dhrishi.github.io/connectedhomeip/ to a more formal location :)

Problem
The current qr code url points to  https://dhrishi.github.io. I had a discussion a while back with Woody to request this change. :)
It would be good to move it to a more formal (for lack of a better term) location
Proposed Solution
<suggested fix, suggested enhancement>

#3266

@nivi-apple This is done now!


Adding the update from the April 21st session

Not yet finished work, so it might be better to wait till we figure things out. However, I leave the updated notebook here in case someone else is sharing the notebook and wants to reuse it.


Ask for help converting Clue Data

Hello, I have finally received my data export from Clue. Unfortunately, the conversation with my data did not work, or the converted file could not be read by Drip. As the data is too private for me to post it here publicly, perhaps I can send you my data and you can take a closer look at it?
E-mail<EMAIL_ADDRESS>

Absolutely! I'm sending you an email immediately. Thank you for telling me about the bug, I should be able to investigate during the weekend :)

It just works. Thank you so much!


[5.6] Initial Requirement 7 Lofi-Prototyping

Description: Prototyping based on Initial Requirement 7.
Goals: Create a Prototype based on the Requirement.
Success or Completion Criteria: Prototype Figma.
Allocated Time: 2 days
Start Date: 31/08/23
End Date: 01/09/23
Main Task :  Create lo-fi prototypes/wireframes based for the initial requirements

Completed.

Issue Comments
Description
Completed prototype for initial requirement 7
Changes to success or completion criteria? y/n (if y, describe)
n
Start Date: 31/08/23, 0000
End Date: 01/09/23, 2359


Better syn highlight

Optimized _base.less Closes #5 #3

@KomodoKode I want to discuss about the red
useful links:
https://coolors.co/fa7b7b-fa7687-f97092
https://coolors.co/fa7d7d-f9798a-f87593 (lightened and desaturated)

@KomodoKode I want to discuss about the red
useful links:
https://coolors.co/fa7b7b-fa7687-f97092
https://coolors.co/fa7d7d-f9798a-f87593 (lightened and desaturated)

I feel like its too pink-ish. What about #F63C55 or #F75066?

I feel like its too pink-ish. What about #F63C55 or #F75066?

#F75066 Looks OK but the colors aren't harmonized

#F75066 Looks OK but the colors aren't harmonized

Actually, what do you think?

Actually, what do you think?

Your new red gives off a different vibe

Your new red gives off a different vibe

You have a point...
The red should probably be darker. Thinking of C7283D.

You have a point...
The red should probably be darker. Thinking of C7283D.

Actually, what do you think?

This looks ok though many of the colors look very similar.

Actually, what do you think?

This looks ok though many of the colors look very similar.

Maybe too pink? I mean its fall syntax after all. Try #d6294b

or a darker #c21f3f.

Maybe too pink? I mean its fall syntax after all. Try #d6294b

or a darker #c21f3f.

Those colors does horribly on coolor's contrast checker
The pink ones, on the other hand does decently well

Those colors does horribly on coolor's contrast checker
The pink ones, on the other hand does decently well

I see. If "very good" is ok with you, then I think #FF8787 might be the best color for this theme.

I see. If "very good" is ok with you, then I think #FF8787 might be the best color for this theme.


Add  automated tests to catch regressions

SDKs/Packages need to set higher bar wrt to quality and tests. How will one catch regressions before releasing a new version? Test can be as simple as taking Screenshot of render of examples included and performing image diff against a refrence image.
Joss Review

Added in a regression test as outlined in the JOSS review


ENYO-5603: Clean up spotlight container disabled prop propagation

Checklist

[x] I have read and understand the contribution guide

[ ] A CHANGELOG entry is included

[ ] At least one test case is included for this feature or bug fix

[ ] Documentation was added or is not needed

[ ] This is an API breaking change

Issue Resolved / Feature Added
SpotlightContainer is declared in Scrollables and yet it's propagating data-spotlight-disabled property down to its children. I believe this is a cruft left over from #1553
Resolution
Removed all setContainerDisabled from moonstone/Scrollable, moonstone/Scroller and moonstone/ScrollableNative
Enact-DCO-1.0-Signed-off-by: Stephen Choi<EMAIL_ADDRESS>

I'm going to look into this more. I think there are some parts of this change that we should take but I'm concerned about the removal of the code that sets data-spotlight-container-disabled. That change allows the pointer to focus contents while scrolling which should be prevented (if I recall the requirements correctly).

I don't think we can safely remove spotlightId from Scrollable either. VirtualList relies on it to configure the spotlight container.
It does seem like we have some confused responsibilities from the refactoring. moonstone/Scrollable "owns" the spotlight container but calls into its child for setContainerDisabled which then finds the parent node to set data-spotlight-container-disabled. Seems like there would be an opportunity to optimize this interaction and reduce the coupling.
What do you think, @viodragon2?

The more I look into this, the more complicated it becomes to untangle spotlight from Scrollable. I don't think there's a clean or an easy way to address this issue, but the benefits of cleaning this up at this point seem tiny. I'll close this issue for now and reconsider this later as a bigger part of Scroller, VirtualList, and Scrollable refactor work.


How can I use Vulkan extensions / or is it not a problem with extensions?

I tried using
#extension GL_KHR_cooperative_matrix : enable #extension GL_KHR_memory_scope_semantics : enable
in the GLSL shader codes, but it gives:
[Jul 15 2024 14:51:38] [debug] [D:\kompute\src\Manager.cpp:30] [VALIDATION]: Validation - Validation Error: [ VUID-VkShaderModuleCreateInfo-pCode-08740 ] | MessageID = 0x6e224e9 | vkCreateShaderModule():  SPIR-V Capability VulkanMemoryModel was declared, but one of the following requirements is required (VkPhysicalDeviceVulkan12Features::vulkanMemoryModel). The Vulkan spec states: If pCode is a pointer to SPIR-V code, and pCode declares any of the capabilities listed in the SPIR-V Environment appendix, one of the corresponding requirements must be satisfied (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkShaderModuleCreateInfo-pCode-08740)

[Jul 15 2024 14:51:38] [debug] [D:\kompute\src\Manager.cpp:30] [VALIDATION]: Validation - Validation Error: [ VUID-VkShaderModuleCreateInfo-pCode-08740 ] | MessageID = 0x6e224e9 | vkCreateShaderModule():  SPIR-V Capability CooperativeMatrixKHR was declared, but one of the following requirements is required (VkPhysicalDeviceCooperativeMatrixFeaturesKHR::cooperativeMatrix). The Vulkan spec states: If pCode is a pointer to SPIR-V code, and pCode declares any of the capabilities listed in the SPIR-V Environment appendix, one of the corresponding requirements must be satisfied (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkShaderModuleCreateInfo-pCode-08740)

It gives the same results when I tried to initialize the manager with the extensions given.
  uint32_t physicalDeviceIndex = 0;
  std::vector<uint32_t> familyQueueIndices = {}; // Initialize this with the necessary queue family indices if needed.
  std::vector<std::string> desiredExtensions = {"VK_KHR_get_physical_device_properties2", "VkPhysicalDeviceVulkan12Features", "VK_KHR_vulkan_memory_model", "VK_KHR_cooperative_matrix"};

  kp::Manager mgr(physicalDeviceIndex, familyQueueIndices, desiredExtensions);

And those are listed in the available extensions, but not added to the manager.

[Jul 16 2024 15:19:31] [debug] [D:\GitHub\kompute\src\Manager.cpp:414] Kompute Manager desired extension layers VK_KHR_get_physical_device_properties2, VkPhysicalDeviceVulkan12Features, VK_KHR_vulkan_memory_model, VK_KHR_cooperative_matrix
[Jul 16 2024 15:19:31] [debug] [D:\GitHub\kompute\src\Manager.cpp:424] Kompute Manager available extensions VK_AMD_buffer_marker, VK_AMD_calibrated_timestamps, VK_AMD_device_coherent_memory, VK_AMD_display_native_hdr, VK_AMD_draw_indirect_count, VK_AMD_gcn_shader, VK_AMD_gpa_interface, VK_AMD_gpu_shader_half_float, VK_AMD_gpu_shader_int16, VK_AMD_memory_overallocation_behavior, VK_AMD_mixed_attachment_samples, VK_AMD_shader_ballot, VK_AMD_shader_core_properties, VK_AMD_shader_core_properties2, VK_AMD_shader_early_and_late_fragment_tests, VK_AMD_shader_explicit_vertex_parameter, VK_AMD_shader_image_load_store_lod, VK_AMD_shader_info, VK_AMD_shader_trinary_minmax, VK_EXT_4444_formats, VK_EXT_attachment_feedback_loop_layout, VK_EXT_border_color_swizzle, VK_EXT_calibrated_timestamps, VK_EXT_color_write_enable, VK_EXT_conditional_rendering, VK_EXT_conservative_rasterization, VK_EXT_custom_border_color, VK_EXT_depth_clamp_zero_one, VK_EXT_depth_clip_control, VK_EXT_depth_clip_enable, VK_EXT_depth_range_unrestricted, VK_EXT_descriptor_buffer, VK_EXT_descriptor_indexing, VK_EXT_device_address_binding_report, VK_EXT_device_fault, VK_EXT_dynamic_rendering_unused_attachments, VK_EXT_extended_dynamic_state, VK_EXT_extended_dynamic_state2, VK_EXT_extended_dynamic_state3, VK_EXT_external_memory_host, VK_EXT_frame_boundary, VK_EXT_full_screen_exclusive, VK_EXT_global_priority, VK_EXT_global_priority_query, VK_EXT_graphics_pipeline_library, VK_EXT_hdr_metadata, VK_EXT_host_query_reset, VK_EXT_image_robustness, VK_EXT_image_sliced_view_of_3d, VK_EXT_image_view_min_lod, VK_EXT_index_type_uint8, VK_EXT_inline_uniform_block, VK_EXT_line_rasterization, VK_EXT_load_store_op_none, VK_EXT_memory_budget, VK_EXT_memory_priority, VK_EXT_mesh_shader, VK_EXT_mutable_descriptor_type, VK_EXT_nested_command_buffer, VK_EXT_non_seamless_cube_map, VK_EXT_pageable_device_local_memory, VK_EXT_pipeline_creation_cache_control, VK_EXT_pipeline_creation_feedback, VK_EXT_pipeline_library_group_handles, VK_EXT_post_depth_coverage, VK_EXT_primitive_topology_list_restart, VK_EXT_primitives_generated_query, VK_EXT_private_data, VK_EXT_provoking_vertex, VK_EXT_queue_family_foreign, VK_EXT_robustness2, VK_EXT_sample_locations, VK_EXT_sampler_filter_minmax, VK_EXT_scalar_block_layout, VK_EXT_separate_stencil_usage, VK_EXT_shader_atomic_float, VK_EXT_shader_atomic_float2, VK_EXT_shader_demote_to_helper_invocation, VK_EXT_shader_image_atomic_int64, VK_EXT_shader_module_identifier, VK_EXT_shader_stencil_export, VK_EXT_shader_subgroup_ballot, VK_EXT_shader_subgroup_vote, VK_EXT_shader_viewport_index_layer, VK_EXT_subgroup_size_control, VK_EXT_texel_buffer_alignment, VK_EXT_tooling_info, VK_EXT_transform_feedback, VK_EXT_vertex_attribute_divisor, VK_EXT_vertex_input_dynamic_state, VK_EXT_ycbcr_image_arrays, VK_GOOGLE_decorate_string, VK_GOOGLE_hlsl_functionality1, VK_GOOGLE_user_type, VK_KHR_16bit_storage, VK_KHR_8bit_storage, VK_KHR_acceleration_structure, VK_KHR_bind_memory2, VK_KHR_buffer_device_address, VK_KHR_calibrated_timestamps, VK_KHR_cooperative_matrix, VK_KHR_copy_commands2, VK_KHR_create_renderpass2, VK_KHR_dedicated_allocation, VK_KHR_deferred_host_operations, VK_KHR_depth_stencil_resolve, VK_KHR_descriptor_update_template, VK_KHR_device_group, VK_KHR_draw_indirect_count, VK_KHR_driver_properties, VK_KHR_dynamic_rendering, VK_KHR_dynamic_rendering_local_read, VK_KHR_external_fence, VK_KHR_external_fence_win32, VK_KHR_external_memory, VK_KHR_external_memory_win32, VK_KHR_external_semaphore, VK_KHR_external_semaphore_win32, VK_KHR_format_feature_flags2, VK_KHR_fragment_shader_barycentric, VK_KHR_fragment_shading_rate, VK_KHR_get_memory_requirements2, VK_KHR_global_priority, VK_KHR_image_format_list, VK_KHR_imageless_framebuffer, VK_KHR_index_type_uint8, VK_KHR_line_rasterization, VK_KHR_load_store_op_none, VK_KHR_maintenance1, VK_KHR_maintenance2, VK_KHR_maintenance3, VK_KHR_maintenance4, VK_KHR_maintenance5, VK_KHR_maintenance6, VK_KHR_map_memory2, VK_KHR_multiview, VK_KHR_pipeline_executable_properties, VK_KHR_pipeline_library, VK_KHR_push_descriptor, VK_KHR_ray_query, VK_KHR_ray_tracing_maintenance1, VK_KHR_ray_tracing_pipeline, VK_KHR_ray_tracing_position_fetch, VK_KHR_relaxed_block_layout, VK_KHR_sampler_mirror_clamp_to_edge, VK_KHR_sampler_ycbcr_conversion, VK_KHR_separate_depth_stencil_layouts, VK_KHR_shader_atomic_int64, VK_KHR_shader_clock, VK_KHR_shader_draw_parameters, VK_KHR_shader_expect_assume, VK_KHR_shader_float16_int8, VK_KHR_shader_float_controls, VK_KHR_shader_float_controls2, VK_KHR_shader_integer_dot_product, VK_KHR_shader_maximal_reconvergence, VK_KHR_shader_non_semantic_info, VK_KHR_shader_quad_control, VK_KHR_shader_subgroup_extended_types, VK_KHR_shader_subgroup_rotate, VK_KHR_shader_subgroup_uniform_control_flow, VK_KHR_shader_terminate_invocation, VK_KHR_spirv_1_4, VK_KHR_storage_buffer_storage_class, VK_KHR_swapchain, VK_KHR_swapchain_mutable_format, VK_KHR_synchronization2, VK_KHR_timeline_semaphore, VK_KHR_uniform_buffer_standard_layout, VK_KHR_variable_pointers, VK_KHR_vertex_attribute_divisor, VK_KHR_video_decode_h264, VK_KHR_video_decode_h265, VK_KHR_video_decode_queue, VK_KHR_video_queue, VK_KHR_vulkan_memory_model, VK_KHR_win32_keyed_mutex, VK_KHR_workgroup_memory_explicit_layout, VK_KHR_zero_initialize_workgroup_memory, VK_VALVE_mutable_descriptor_type
[Jul 16 2024 15:19:31] [error] [D:\GitHub\kompute\src\Manager.cpp:433] Kompute Manager not all extensions were added: VK_KHR_vulkan_memory_model, VK_KHR_cooperative_matrix

@han-minhee you can add extensions by following this example: https://kompute.cc/overview/advanced-examples.html?highlight=extension#add-extensions

Thank you for the answer, and I've added extensions like above, but the problem was that it failed to add VK_KHR_vulkan_memory_model, VK_KHR_cooperative_matrix even when they are in the supported lits.


Work on deployment of Phoenix Website

Title: Phoenix
About:  Work on deployment of Phoenix Website
Name: adithya-s-k
Label: Feature Request

Is your feature request related to a problem? Please describe.
Work on deployment of Phoenix Website. Go Ahead with GH Pages. Deploy in the upstream repository

Additional notes

N/A

I will work on this issue


When i run this file,i had a error in dataReader.py:TypeError: expected str, bytes or os.PathLike object, not _io.TextIOWrapper,how to fix it

File "/mnt/DATA1/jsl/MARL/MARLsourcefile/dataReader.py", line 170, in init
self.image_files = [line.split('\n')[0] for line in open(files_list[0])]
TypeError: expected str, bytes or os.PathLike object, not _io.TextIOWrapper

check that you are passing a list strings


Value can not be shown.

Yes, I'm encountering the same issue.

Solved it by adding:
gaugeView.showScale = YES;

Thanks for your comment.


Error page component

Supporting change for https://github.com/aptible/dashboard.aptible.com/pull/646 — also fixes a broken href

cc @sandersonet @gib

👍


use systemd-boot everywhere

Moving us closer to trusted boot

I would suggest to make a systemd-boot profile for now and make it optional this way. There also other targets that need uboot or even EFI platforms that do not work with systemd-boot (We have one expensive arm server that does not boot with systemd-boot)


compose: When editing the selected message, quote into the edit box.

Until now, when a user quoted and replied to a message, even while editing another, the quote would be inserted into the compose box. There was no way to quote into the edit box.
Detecting the edit box to add content too was tricky, since on opening the message actions popover, that message would be selected, while the edit box would lose focus.
Now we don't shift focus on opening the message actions popover, and add the quote content to the edit box when its message is selected.
Fixes: #20380.
compose: Do not select message row on opening message actions popover.
Now since all actions available in the message actions popover operate
on that message itself, we don't need to select the message row when
opening the popover.
compose: Pass in the message_id when quoting from the message's popover.
compose: Allow message_id to be passed into quote_and_reply.
compose: Allow message_id to be passed to respond_to_message.

Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@alya This is ready for you to test

Works great in my manual testing!
I tried having multiple messages open for editing, as well as selecting yet another message (so the quote-and-reply text correctly went into the compose box).

@timabbott tagging for your review.

After chatting with @timabbott , I started https://chat.zulip.org/#narrow/stream/101-design/topic/shifting.20blue.20box.20on.20clicks/near/1661454.

Would we like more opinions on the CZO thread or should we stick to the current strategy of not shifting the blue box on clicking the message menu button, and quoting into the currently selected (one with the blue box) message being edited?

I think we can go with the proposal on CZO not to shift the blue box.

@timabbott Now that we have decided to not shift the blue box on clicking the message menu button, what do you suggest is the next step for this PR?

As noted in https://github.com/zulip/zulip/pull/27075#discussion_r1357336572, I think we need to add a preparatory commit to keep track of the last compose-type text input that was focused.

Merged, thanks @N-Shar-ma! But please consider https://github.com/zulip/zulip/pull/27075#discussion_r1401054409 and potentially open a PR or start conversation in #frontend about changing that convention for the | false elements in compose_state.ts.

The refactor is ready for review: #28480


Add default service config file to the list of config files

A small fix to support https://github.com/valory-xyz/open-autonomy/pull/978

Codecov Report

Merging #192 (4468fd0) into main (1987eaa) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #192      +/-   ##
==========================================
- Coverage   94.60%   94.60%   -0.01%
==========================================
  Files         311      311
  Lines       24969    24971       +2
==========================================
  Hits        23623    23623
- Misses       1346     1348       +2

Flag
Coverage Δ

unittests
94.60% <0.00%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

aea/configurations/base.py
99.69% <0.00%> (-0.31%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1987eaa...4468fd0. Read the comment docs.


test: update add_vagrant_box.sh

This commit fixes a few portability issues and minor bugs, mainly caught
by ShellCheck.

test-me-please

This script is not used in CI tests.

Ah, thanks. I saw references to it in several Jenkinsfiles:
jenkinsfiles/ginkgo-kernel.Jenkinsfile:102:                sh '/usr/local/bin/add_vagrant_box ${WORKSPACE}/${PROJ_PATH}/vagrant_box_defaults.rb'
jenkinsfiles/ginkgo-runtime-kernel.Jenkinsfile:73:                sh '/usr/local/bin/add_vagrant_box ${WORKSPACE}/${PROJ_PATH}/vagrant_box_defaults.rb'
jenkinsfiles/kubernetes-upstream.Jenkinsfile:65:                sh '/usr/local/bin/add_vagrant_box ${WORKSPACE}/${PROJ_PATH}/vagrant_box_defaults.rb'

but see now that these are in fact provisioned as part of the Packet Terraform scripts.

We should really move this script to contrib/ to clarify that and fix the codeowners in one go. I've stopped the Jenkins builds.

We should really move this script to contrib/ to clarify that and fix the codeowners in one go.

-> https://github.com/cilium/cilium/pull/15859


[prometheus] Don't log high cardinality labels

Motivation
From the documentation (https://prometheus.io/docs/practices/naming/#labels):

Do not use labels to store dimensions with high cardinality (many different label values), such as user IDs, email addresses, or other unbounded sets of values.

Proposal
Oversight on my part, this can cause a huge amount of data to Prometheus, so let's remove it for now. We can figure out another solution if we ever need this level of cardinality. Thanks @ma2bd for pointing out
Test Plan
Kubernetes CI should fail if these metrics are failing to be logged

Current dependencies on/for this PR:

main

PR #1262   👈

This stack of pull requests is managed by Graphite.


build perl 5.16.x

build fails from v5.17.3 https://github.com/shogo82148/actions-setup-perl/pull/56/checks?check_run_id=334249822 to v5.17.11 https://github.com/shogo82148/actions-setup-perl/runs/334249753
they are develop version. I'll fix it later...


Remove unnecessary pyobjc dependencies

Currently this project pulls in the full set of pyobjc dependencies. However it only seems to use pyobjc-framework-quartz.
Removing the unneeded dependencies speeds up installation, dependency management and reduces install size.

See also asweigart/mouseinfo#1.

This removes 110 unnecessary dependencies.

Thanks! This is a big help!


#228 Overwrite happens - fix extension of filename

Description (required)
Fixes #228
What changes did you make and why?
Use extension fixing code on structured data branch
Tests performed (required)
Tested betaDebug on Nexus5X with API level 27

Codecov Report

Merging #3689 into structured-data will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@                Coverage Diff                @@
##             structured-data   #3689   +/-   ##
=================================================
  Coverage               7.34%   7.34%
  Complexity               335     335
=================================================
  Files                    293     293
  Lines                  12914   12912    -2
  Branches                1022    1022
=================================================
  Hits                     948     948
+ Misses                 11889   11887    -2
  Partials                  77      77

Impacted Files
Coverage Δ
Complexity Δ

...n/java/fr/free/nrw/commons/upload/UploadModel.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f7b1b14...913ee93. Read the comment docs.

Merged, could you update master with this please?


Debugger API - threadsRequest method is fired even after TerminatedEvent is sent

In the Python extension we're seeing the threadsRequest method is being invoked even after the TerminatedEvent is sent by the Debug Apdater.
The flow is as follows:

Debug a python program
The python program ends, and this is detected by the debug adapter
The debug adapter then sends a TerminatedEvent,
Next the disconnectRequest gets invoked and a response is sent to this
Immediately after the above, the threadsRequest method is invoked

This causes the code to fall over, as the process no longer exists.
I've checked out the sample debugger code and can see we have a check to see whether the process exists.
Shouldn't VS Code, stop sending these requests to the debug adapter.
Or is it merely a timing issue (i.e. the threadsRequest had already been dispatched by vscode before it received the TerminatedEvent?
If it's the latter, then please feel free to close this issue.

Yes, VS Code should not send any  threadsRequest after it has received a TerminatedEvent.
@isidorn please verify this and then close this issue.
However, it is always possible that a threadsRequest had already been dispatched by VS Code before the TerminatedEvent has been received. So DAs should protect themselves against that.

@weinand thanks. In that case, please feel free to close this issue, I'm being more defensive in the code as a solution.
I'm choosing not to close the issue myself, due to some followup work for @isidorn.

VSCode should not send an threadsRequest after a terminatedEvent, it might be a timing issue.
@DonJayamanne Since you have a reproducable on your machine feel free to place a breakpoint here and check the callstack
Though looking at all the possible callers it can only be a timing issue. Thus closing until proven otherwise.


I've just completed a simplified version of AnimateAnyone and invite everyone to give it a try! Currently, the training code has been made available, and soon we'll be releasing our pre-trained models as well. You can access the project via this link: https://github.com/guoqincode/AnimateAnyone-unofficial. Looking forward to your feedback and support!

I've just completed a simplified version of AnimateAnyone and invite everyone to give it a try! Currently, the training code has been made available, and soon we'll be releasing our pre-trained models as well. You can access the project via this link: https://github.com/guoqincode/AnimateAnyone-unofficial. Looking forward to your feedback and support!

Cool！

Could you provide some examples of animation results you've accomplished with this ? Preferrably not cherrypicked

Good~!

You can always bet on the community

AnimateAnyone-unofficial -> DWPose
MagicAnimate -> Densepose
AnimateAyone -> Openpose

wonderful!


Run the code on data closer to the Academy Award Ceremony

Data on twitter and letterboxd will be more accurate closer to the event, re-collect data then to build the models.

This was completed on March 10th, 2023. Closing now as this issue is stale.


Replace Module Info Dummies with Real Data

@majordwarf Can you please add some information here on the original approach to gather module info?
Potentially relevant for future work on this: https://github.com/MovingBlocks/Terasology/pull/3966

@majordwarf can you please explain about Modules and how we are going to implement that

Well, the data present in the repository aside from the modules/ directory will be changed/modified manually. To gather the modules' info, I have had two approaches. One would be a single-time pipeline to scrape data of all of the modules together and one to be a part of the module build pipeline to update the earlier gathered data on every push event or module build trigger.
We'd typically look for data in module.txt, README.md, module logo, and cover image. If the logo or cover images are not found we revert back to a boilerplate.
The single-time pipeline I wrote in 2019 resides here: https://github.com/dwarf-test/master-scrape
The scraped data is stored in a separate repo, during the module site deployment, the data is fetched from this repo and formatted as per the need of the Module site. The temporary data in modules/ would be purged first before we start to generate actual module data.

done


chore: update to latest vc-go.

Codecov Report
Attention: 28 lines in your changes are missing coverage. Please review.

Comparison is base (b77aa73) 89.23% compared to head (d403e5e) 88.63%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #646      +/-   ##
==========================================
- Coverage   89.23%   88.63%   -0.61%
==========================================
  Files         102      102
  Lines        4060     4090      +30
==========================================
+ Hits         3623     3625       +2
- Misses        298      323      +25
- Partials      139      142       +3

Files
Coverage Δ

cmd/wallet-sdk-gomobile/display/resolve.go
85.36% <100.00%> (ø)

cmd/wallet-sdk-gomobile/openid4vp/interaction.go
81.63% <100.00%> (ø)

pkg/common/keyresolver.go
100.00% <100.00%> (ø)

pkg/credentialquery/credentialquery.go
100.00% <100.00%> (ø)

pkg/credentialschema/opts.go
94.56% <100.00%> (ø)

pkg/internal/issuermetadata/issuermetadata.go
75.00% <100.00%> (ø)

pkg/openid4ci/interaction.go
88.16% <100.00%> (-0.17%)
:arrow_down:

pkg/openid4ci/issuerinitiatedinteraction.go
91.85% <100.00%> (ø)

pkg/openid4ci/walletinitiatedinteraction.go
78.18% <100.00%> (ø)

pkg/openid4vp/openid4vp.go
91.36% <100.00%> (+0.08%)
:arrow_up:

... and 3 more

... and 1 file with indirect coverage changes

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


Signals like post_delete don't get called for related models

If I have a child model, such as Book (child of Author), and I configure the ForeignKey with ondelete="CASCADE", the post_delete signal of the child model does not get called when the parent is deleted. Is this expected behavior? If yes, are there better workarounds than to shift all of the child signal code to the parent signal function?
To reproduce:
from typing import Optional
import databases
from ormar import Model, ModelMeta, post_delete, Integer, ForeignKey
import sqlalchemy

DATABASE_URL = f"sqlite:///db.sqlite"
database = databases.Database(DATABASE_URL)
metadata = sqlalchemy.MetaData()
engine = sqlalchemy.create_engine(DATABASE_URL)

class BaseMeta(ModelMeta):
    metadata = metadata
    database = database

class Author(Model):
    class Meta(BaseMeta):
        tablename = "authors"
        post_delete_was_called = False
    id: int = Integer(primary_key=True)

@post_delete(Author)
async def post_delete_author(sender, instance, **kwargs):
    Author.Meta.post_delete_was_called = True

class Book(Model):
    class Meta(BaseMeta):
        tablename = "books"
        post_delete_was_called = False
    id: int = Integer(primary_key=True)
    author: Optional[Author] = ForeignKey(Author, ondelete="CASCADE", skip_reverse=True)

@post_delete(Book)
async def post_delete_book(sender, instance, **kwargs):
    Book.Meta.post_delete_was_called = True

metadata.create_all(engine)

async def test_case():
    async with database:
        author = await Author.objects.create()
        await Book.objects.create(author=author)

        await author.delete()

        assert Author.Meta.post_delete_was_called
        assert Book.Meta.post_delete_was_called

import asyncio
asyncio.run(test_case())
metadata.drop_all(engine)

Yes, the signals was effect on current model.
For example:
If the book has 1000 authors,  we must get all `authors`, and send 1000 signals, it's not good.

Yes, that is expected as when you set the CASCADE option it is performed by the database alone. That means that it never reaches the python code, which is not aware that something was deleted. You can create database triggers to fire something on deletion in this case or roll back to manual/ signal deletion from python (although that is for sure slower).


Feature additions, updates & refactoring

Spam/Unspam email message/messages based on query search.
ReportSpamMessage()
ReportSpamMessages()
UnspamMessage()
UnspamMessages()
Mark email message/messages read/unread based on query search.
MarkMessageAsRead()
MarkMessagesAsRead()
MarkMessageAsUnread()
MarkMessagesAsUnread()
Gmail Helper documentation updates.
Tests addition, updates, refactoring.
Readme updates.
Nuget package creation - v1.4.0.

Codecov Report

Merging #18 (248aae7) into main (570fcc9) will increase coverage by 0.45%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #18      +/-   ##
==========================================
+ Coverage   98.76%   99.22%   +0.45%
==========================================
  Files           1        1
  Lines         324      516     +192
  Branches       65       93      +28
==========================================
+ Hits          320      512     +192
  Misses          2        2
  Partials        2        2

Impacted Files
Coverage Δ

GmailAPIHelper/GmailHelper.cs
99.22% <100.00%> (+0.45%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 570fcc9...248aae7. Read the comment docs.


Clarification on definition of gene

Currently the definition of gene http://purl.obolibrary.org/obo/SO_0000704 is A region (or regions) that includes all of the sequence elements necessary to encode a functional transcript. A gene may include regulatory regions, transcribed regions and/or other functional sequence regions. http://www.sequenceontology.org/browser/current_svn/term/SO:immuno_workshop
The URL doesn't resolve.
I realize this is a whole can of worms, finding the perfect definition is hard, but it may be useful to provide additional examples of what is meant and not meant.
I seem to recall SO previously having a definition that was more precise operational, and specifically mentioned that in the case of coding genes there would be no in-frame overlaps. Did I hallucinate this?

the gene now includes (as parts?) regulatory regions etc, this seems in contradiction to how the gene feature is used in GFF3 typically? I seem to recall that previously the gene didn't include these as parts (i.e. determining start/end/extent) - this of course does not rule out their functional role
' all of the sequence elements necessary' - I think the intent here is to be inclusive of all regulatory regions, exons, introns, what else? 'all elements necessary' to me includes all the transcription factor proteins... where does it end?
the definition refers to 'functional transcript', I see the intent but it's an odd term as mRNA isn't functional the same way an ncRNA is
there isn't really anything that says how we count distinct genes. If we were to ask SO how many genes are in the human genome, by the def the answer may be one per transcript...

I don't want to re-tread old ground if the definition was agreed upon by a wide variety of people, but it would be useful to have links out to other documentation (e.g. how gene is applied in GFF3, how start/end is determined, how uniqueness is determined)
E.g.
https://github.com/The-Sequence-Ontology/Specifications/blob/master/gff3.md#the-canonical-gene
(which specifically excludes TFBSs)
I'm particularly interested in how to apply SO's definition for gene in the case of RNA viruses such as SARS-CoV-2. Do nsp1, nsp2, etc come from distinct genes? Are pps 1a and 1ab distinct genes? Or is there a single gene that encompasses 1a and 1ab? More on how this genome is treated by gene/protein databases here: https://douroucouli.wordpress.com/2020/08/05/what-is-the-sars-cov-2-molecular-parts-list/

Hi @cmungall,
I can understand wanting to update the definition of gene. As discussed with Colin Logie for the BBA paper, the SO gene includes the regulatory regions that are inherited as well. The phrase ' all of the sequence elements necessary'  does sound ambiguous as it might include proteins (transcription factors). Is there a specific wording that you would like to use in place of this?
Of note, I am not familiar enough with the GFF3 format to change this. However, the definition in SO has included regulatory regions of a gene for several years and this was covered in the BBA manuscript, so I believe the definition should continue to include regulatory regions. We will have to have another discussion to determine if GFF3 needs updates. I will bring it up to the group, but if changes are needed they are likely to go in to the GFF3 GitHub Page and will be addressed by someone more familiar with updating the GFF3 format.
Thanks,
Dave

I wouldn't say that usage in GFF3 precludes inclusion of regulatory sequences. While common usage is to define the gene range based on the maximal transcript range, that's partially a matter of convenience and lack of information about promoter elements. promoter (SO:0000167) and regulatory_region (SO:0005836) are children of gene, so it's currently valid to include them. And fun tidbit: there's nothing in the GFF3 spec that says a parent feature location needs to encompass the location(s) of its children.

(which specifically excludes TFBSs)

The canonical gene example includes a TF_binding_site feature (line 3).
I don't have any suggestions on how to improve the definition, other than to say it's a thorny subject and gene has such varied use that any changes to make it more restrictive or specific are likely to be incompatible with current usage.


chore: Add an instancetype controller to encapsulate caching logic

Fixes #N/A
Description
This is a first step in a multi-PR change that causes the Karpenter codebase to get instance types from an abstraction layer. In the future, we will hang Ice caching and #1305 on top of this provider.
How was this change tested?

make presubmit
Manually

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

79 of 102 (77.45%)  changed or added relevant lines in 13 files are covered.
6 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.1%) to 78.684%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/controllers/instancetype/provider.go
34
36
94.44%

pkg/controllers/controllers.go
0
4
0.0%

pkg/controllers/instancetype/controller.go
0
17
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/utils/atomic/lazy.go
2
87.88%

pkg/test/expectations/expectations.go
4
93.29%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
8623

Relevant Lines:
10959

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

79 of 102 (77.45%)  changed or added relevant lines in 13 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.1%) to 78.702%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/controllers/instancetype/provider.go
34
36
94.44%

pkg/controllers/controllers.go
0
4
0.0%

pkg/controllers/instancetype/controller.go
0
17
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/utils/atomic/lazy.go
2
87.88%

pkg/controllers/provisioning/scheduling/nodeclaim.go
2
89.13%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
8625

Relevant Lines:
10959

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

79 of 106 (74.53%)  changed or added relevant lines in 13 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 78.603%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/controllers/instancetype/provider.go
34
36
94.44%

pkg/controllers/controllers.go
0
8
0.0%

pkg/controllers/instancetype/controller.go
0
17
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/node/termination/terminator/eviction.go
2
89.09%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
8622

Relevant Lines:
10969

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

79 of 106 (74.53%)  changed or added relevant lines in 13 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 78.603%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/controllers/instancetype/provider.go
34
36
94.44%

pkg/controllers/controllers.go
0
8
0.0%

pkg/controllers/instancetype/controller.go
0
17
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/test/expectations/expectations.go
2
93.69%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
8622

Relevant Lines:
10969

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

74 of 99 (74.75%)  changed or added relevant lines in 12 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.08%) to 78.173%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/controllers/controllers.go
0
8
0.0%

pkg/controllers/instancetype/controller.go
0
17
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/test/expectations/expectations.go
2
93.71%

pkg/controllers/node/termination/terminator/eviction.go
2
89.09%

Totals

Change from base Build<PHONE_NUMBER>:
-0.08%

Covered Lines:
9000

Relevant Lines:
11513

💛  - Coveralls

/reopen

/remove-lifecycle stale


feature: reconnect when disconnected from rosbridge

Fixes https://github.com/siemens/ros-sharp/issues/186

Delete unecessary Thread : remove spawn overhead, the thread was waiting most of its time, a coroutine (via async/await api) is more suited to this
Lower Timeout default value from 10 to 3 seconds
Each OnClosed Event, the RosConnector wait Timeout before attempting to connect again

Thank you for this pull request @PymZoR !
Please give us some time to test and revise it throughly.

Dear @PymZoR , we reviewed your pull request in detail and feel it does not fit into the master due to the following reasons:

Generally it is not a good idea to always reconnect OnClose().
Unity does not stop trying to reconnect, even after stopping PlayMode in this implementation.
Please feel free to continue working with this implementation in your fork/ROS# applications!


Implement a better "schema" for easily mapping logical columns to CF columns (blob1, blob2, etc.)

There's a basic mapping here, but if you look around the code you'll see there's hardcoded columns being used.
There should be a consistent, safe way of mapping columns to CF Analytics Engine columns and the other way around.

At some point schema.ts got introduced and I'd say that's good enough for now.


ROS implementation

How can the different policies be implemented in ROS and take sensor input (camera)?

Hi this repo only contains codes for training and tesing policies with 2D coordinates as input. For deployment, you need to process the sensory data into 2D coordinates and then give it to the policy as input. This detection & tracking part is not included in this repo.


feat(healthcheck): Add support for healthcheck per proctype

Current coverage is 5.01% (diff: 0.00%)

Merging #160 into master will decrease coverage by 0.04%

@@            master      #160   diff @@
========================================
  Files           46        46
  Lines         3256      3287    +31
  Methods          0         0
  Messages         0         0
  Branches         0         0
========================================
  Hits           165       165
- Misses        3069      3100    +31
  Partials        22        22

Powered by Codecov. Last update 51a2103...b8cbd1f

Another thought that I can't put into comments: we should be able to set the same healthcheck for multiple processes in one command (is this what the web/cmd syntax accomplishes?)


QA: proofread SDK wiki

Read everything
Look for typos
Look for errors
Consider yourself a complete novice and see if everything is well explained and makes sense

I collect my notes here (ongoing!):
https://hackmd.io/U4pXAsuGS4Gd0-gLVPYS6A

From Antonio https://hackmd.io/@IOTA-X-TEAM/Sk7QxtKun


Camera cannot survive after screen off/on❓

Question
Camera cannot survive, From a react native Android app.
What I tried
Hi, I am not a developer. I am using a React Native Android app created by some dev., some time ago. Vision camera is used in the app, to capture qr code.
A problem suddenly developed and I am trying to figure out if it's my phone, or something wrong with code.
When I open qr code scanner and start live qr code scanning, it's all fine.
After a scan, I am turning off phone screen using physical button, to preserve battery. If I turn it on under a minute, in most cases, no problems.
If I keep it off a minute or longer, when I open phone screen, the camera is black, like it did not come up from sleep or whatever mode. Sometimes this happens immediately after closing phone screen and open, sometimes, after a couple mins later.
Do anyone of you experienced such an issue?
Thank you for any guidance.
VisionCamera Version
V2
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

Hey - thanks for reporting this, but two things:

This is a question, not a bug report. I am missing all kinds of relevant information for this like logs or traces.
I will not work on any bug fixes or improvements for VisionCamera V2 anymore, this has likely been fixed in V3 (full rewrite)


Update PullStrategy.java

pick top value from query and as mentioned in the documentation, choose  minimum between "User entered" and "Max Allowed(100)"
We have been struggling with this, and i verified by changing top to 25 and it works but above can never work with existing source.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

i think this will need bit more work.so closing it


Clean up async code

Asynchronous code in _api needed to know too much about the internal workings of the AwaitHandler.  Changed it so that there's a little bit more separation.
Also made some asynchronous functions really be asynchronous.
Added on_submitted_word_done.
Commenting out implementation of create_xxx_pipeline_async because these are unimplemented in wgpu-native.  The code is still there, but a constant forces the synchronous implementation.
Added tests.  Added dependency on pytest-asyncio to run those tests.

Very nice improvements!

While I'm cleaning up.  Why do both enumerate_adapters_sync and enumerate_adapters_async exist?   There seems to be no value added by the async version.  Can these just be merged into `enumerate_adapters"?
When I look at the Rust documentation, there seems to be only a single synchronous operation.

Why do both enumerate_adapters_sync and enumerate_adapters_async exist?

Good question. The reason is that in order to implement this method in JS, we must probably just call request_adapter with different power settings, and request_adapter is async.

Just an open suggestion: maybe it would be helpful to leverage anyio if our goal is to support both trio and asyncio? It has a pytest plugin too. It might make our lives simpler.

Applications and libraries written against AnyIO’s API will run unmodified on either asyncio or trio

This quote from their docs seems very promising.

I was going to ask about anyio.  It seems like a reasonable solution, but I
didn’t want to bring in a third-party library without prior approval.
And pytest-anyio conveniently runs both asyncio and trio.
Ignore the push I just did. I’ll rewrite to use anyio.
On Mon, Nov 4, 2024 at 13:11 Korijn van Golen @.***>
wrote:

Just an open suggestion: maybe it would be helpful to leverage anyio
https://anyio.readthedocs.io/en/stable/index.html if our goal is to
support both trio and asyncio? It has a pytest plugin too. It might make
our lives simpler.
Applications and libraries written against AnyIO’s API will run unmodified
on either asyncio or trio
This quote from their docs seems very promising.
—
Reply to this email directly, view it on GitHub
https://github.com/pygfx/wgpu-py/pull/631#issuecomment-2455709387, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABC2LIM2VQLLEMRXSGLMFZLZ67PHRAVCNFSM6AAAAABRBBMQXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJVG4YDSMZYG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

I was going to ask about anyio.

For testing It definitely makes sense. For implementation, only if it remains somewhat contained and an implementation detail.
There's a lot of changes coming in how wgpu-native implements futures, and I'm also not sure what we'd need to do to support this running in JS. My point is that this will code will evolve quite a bit in the coming months, and I don't want to lock into a dependency.

The Python documentation on writing implementation-agnostic asynchronous
code is very thin. I'm still investigating if there is an easy way of
saying in an async function "Let other coroutines run and then come back to
me" that doesn't tie the code down into a specific implementation.
This is one of the more painful areas of Python development.  It's a lot
easier if you know which async library you're going to use.
On Tue, Nov 5, 2024 at 12:13 AM Almar Klein @.***>
wrote:

I was going to ask about anyio.
For testing It definitely makes sense. For implementation, only if it
remains somewhat contained and an implementation detail.
There's a lot of changes coming in how wgpu-native implements futures, and
I'm also not sure what we'd need to do to support this running in JS. My
point is that this will code will evolve quite a bit in the coming months,
and I don't want to lock into a dependency.
—
Reply to this email directly, view it on GitHub
https://github.com/pygfx/wgpu-py/pull/631#issuecomment-2456502137, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABC2LIOTFDYMYH6VAXRKED3Z7B42JAVCNFSM6AAAAABRBBMQXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJWGUYDEMJTG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

I need some advice on how to finish this.  I'm temporarily using anyio, which can deal with both trio and asyncio and it's mostly working.
The problem I'm running into is on the build.  I've included "anyio" in pyproject.toml , and the build and tests run fine.  But when the wheel is being built, it doesn't include anyio.  How do I tell the wheel-builder to include this?
Just as an aside, I went to a clean environment and did "pip install wgpu".  I was surprised to see pycparser included.  I can't find where that dependency is coming from.

The problem I'm running into is on the build. I've included "anyio" in pyproject.toml , and the build and tests run fine. But when the wheel is being built, it doesn't include anyio. How do I tell the wheel-builder to include this?

Wheels don't ship their dependencies, they're only listed in their metadata files.

Just as an aside, I went to a clean environment and did "pip install wgpu". I was surprised to see pycparser included. I can't find where that dependency is coming from.

I'm guessing it's a transient dependency of cffi.

I'm guessing it's a transient dependency of cffi.

It is: https://github.com/python-cffi/cffi/blob/88f48d22484586d48079fc8780241dfdfa3379c8/pyproject.toml#L12-L14

It looks like yield None works for Trio too. The below runs two tasks simultaneously. One uses the awaitable that constantly switches back to the event-loop using yield None, the other prints the time on an interval.
import time
import trio

class Awaitable:
    def __await__(self):
        while True:
            yield None

async def main():
    async with trio.open_nursery() as nursery:
        nursery.start_soon(child1)
        nursery.start_soon(child2)

async def child1():
    await Awaitable()

async def child2():
    while True:
        print(time.time())
        trio.sleep(0.01)

trio.run(main)

To be honest I'm reluctant for using anyio because it brings in 4 extra dependencies.
If we really do want to sleep, we can maybe use sniffio (which anyio also uses), which is a tiny self-contained library, and use that to detect asyncio vs trio and then use either trio.sleep or asyncio.sleep.
But my preference would be to use the yield None trick if that's possible, because its simple and because the code will have to change anyway when the new future-implementation in wgpu-native arrives. From what I can see yield None works on Trio too, but maybe I'm missing something.

Okay.  I'm now happy with this.
I verified that when wgpu is install normally (pip install /tmp/builder/wgpu-py/dist/wgpu-0.19.0-py3-none-manylinux_2_28_aarch64.whl) that anyio is installed.  It is only the special pip instructions used in cd.yml that were causing problems.
For now, this works with asyncio and trio.  I'm still looking for a way to say "I don't care which async package I'm using, let someone else run for X seconds."  Such a think doesn't seem to exist.  There really doesn't even seem to be a way of finding out which asynchronous package you're using.
Note that test-async uses pytest.anyio which causes it to test the code using both asyncio and trio.

There really doesn't even seem to be a way of finding out which asynchronous package you're using.

That's what sniffio tries to do.

Everything resolved.

I will agree with Almar on the dependency management topic here.
If you switch from anyio to sniffio, you can write something like the following:
def get_async_backend():
    lib = sniffio.current_async_library()
    if lib == "asyncio":
        import asyncio
        return asyncio
    # and so on

That would reduce our dependency footprint quite a lot.

Interesting that CI is green; if I checkout this branch and run an example, it panics in _wgpuDeviceCreateRenderPipeline. Note the invalid vertex format for vertex attribute: 0:
thread '<unnamed>' panicked at src/lib.rs:2169:42:
invalid vertex format for vertex attribute: 0
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread '<unnamed>' panicked at library/core/src/panicking.rs:221:5:
panic in a function that cannot unwind
stack backtrace:
   0:        0x1034a14e8 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h243268f17d714c7f
   1:        0x1034ba19c - core::fmt::write::hb3cfb8a30e72d7ff
   2:        0x10349fb84 - std::io::Write::write_fmt::hfb2314975de9ecf1
   3:        0x1034a2504 - std::panicking::default_hook::{{closure}}::h14c7718ccf39d316
   4:        0x1034a2128 - std::panicking::default_hook::hc62e60da3be2f352
   5:        0x1034a2fc8 - std::panicking::rust_panic_with_hook::h09e8a656f11e82b2
   6:        0x1034a28f0 - std::panicking::begin_panic_handler::{{closure}}::h1230eb3cc91b241c
   7:        0x1034a1974 - std::sys::backtrace::__rust_end_short_backtrace::hc3491307aceda2c2
   8:        0x1034a25e0 - _rust_begin_unwind
   9:        0x1034df108 - core::panicking::panic_nounwind_fmt::h91ee161184879b56
  10:        0x1034df180 - core::panicking::panic_nounwind::heab7ebe7a6cd845c
  11:        0x1034df224 - core::panicking::panic_cannot_unwind::hedc43d82620205bf
  12:        0x1031ec070 - _wgpuDeviceCreateRenderPipeline
  13:        0x1a5051050 - <unknown>
  14:        0x1a5059b04 - <unknown>
  15:        0x101c51188 - _cdata_call
  16:        0x100ed20d0 - __PyObject_Call
  17:        0x100fc4358 - __PyEval_EvalFrameDefault
  18:        0x100eeb4b0 - _gen_send_ex2
  19:        0x100eeb114 - _gen_send_ex
  20:        0x100f20524 - _cfunction_vectorcall_O
  21:        0x100fe3124 - _context_run
  22:        0x100fc3e30 - __PyEval_EvalFrameDefault
  23:        0x100eeb4b0 - _gen_send_ex2
  24:        0x100eeb114 - _gen_send_ex
  25:        0x100fc3cbc - __PyEval_EvalFrameDefault
  26:        0x100fb942c - _PyEval_EvalCode
  27:        0x100fb6d44 - _builtin_exec
  28:        0x100f2024c - _cfunction_vectorcall_FASTCALL_KEYWORDS
  29:        0x100ed1e60 - _PyObject_Vectorcall
  30:        0x100fc2968 - __PyEval_EvalFrameDefault
  31:        0x100fb942c - _PyEval_EvalCode
  32:        0x101019e20 - _run_mod
  33:        0x1010183ec - __PyRun_SimpleFileObject
  34:        0x101017e20 - __PyRun_AnyFileObject
  35:        0x10103bb50 - _Py_RunMain
  36:        0x10103bf10 - _pymain_main
  37:        0x10103bfb0 - _Py_BytesMain
thread caused non-unwinding panic. aborting.

I was wondering how our trio example was able to run, while your new test indicated that trio does not handle the yield None. Turns out that in main, the Awaitable.is_done() calls the poll function, and it seems to always resolve on the first try, so the None is never yielded. Conclusion: the yield None is a asyncio-specific trick.

Is there something holding this up?

Is there something holding this up?

Yes, these two comments:

https://github.com/pygfx/wgpu-py/pull/631#discussion_r1833891369
https://github.com/pygfx/wgpu-py/pull/631#issuecomment-2464021896

I double checked "yield None" with the simplest possible code:
>>> class Foo:
...     def __await__(self):  yield None; return 10
...
>>> async def foo():
...     await Foo()
...
>>> import trio
>>> trio.run(foo)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/fy/Pycharm/wgpu-py/.venv/lib/python3.12/site-packages/trio/_core/_run.py", line 2407, in run
    raise runner.main_task_outcome.error
  File "<stdin>", line 2, in foo
  File "<stdin>", line 2, in __await__
TypeError: trio.run received unrecognized yield message None. Are you trying to use a library written for some other framework like asyncio? That won't work without some kind of compatibility shim.
>

Meanwhile asyncio.run(foo()) worked just fine.  So the yield None is definitely asyncio specific.

@almarklein .  What are you doing to see your crash?   I haven't seen that on either my Mac or on the headless Linux machines I occasionally test on.

What are you doing to see your crash?

python examples/triangle.py shows a black window. python examples/cube.py crashes.

@almarklein.  Hmm.  It works just fine on my Mac. . . .  Let me see if I can re-create this on a headless Linux device.  If not, I'll just close this PR.  Not worth the hassle it's causing.

@almarklein.  Can you give me details on OS, Python version, and GPU?  I rewrote cube.py to be windowless, ran it on a Linux machine, and it just worked.  The bug you've found sounds serious, but I just can't reproduce it. . .

I'm on MacOS (M1), python 3.12.4. This is very strange indeed. I'm having a quick look. (will update this comment)

I found and fixed the problem by adding a new_array() function. It makes sure that the substructs are associated with the array so they are not gc'd prematurely. It also returns null when the list of substructs is empty, which simplifies the code in a few other places (and produces a cleaner struct where we did not consider the case of the empty array). This change should also make further refactoring easier.

The last remaining issue is to replace anyio with sniffio.

For the record, I'll try to explain what was happening a bit better. When you create an ffi struct, it does not hold a reference to its fields when these fields are pointers. So if you do:
sub_struct = ffi.new("CSubType")
struct = ffi.new("CType")
struct.aField = sub_struct

then struct does not hold a reference to sub_struct. If sub_struct goes out of scope, its memory is removed, and struct is now pointing to unclaimed memory; using it can result into garbage or a segfault.
We solved this problem long ago using the new_struct() and new_struct_p() functions in _api.py. One of the things these functions do is associated the fields with the struct, using a WeakKeyDictionary.
However, for arrays we had code like this in many places:
list_of_sub_structs = [new_struct("CSubType", ...) for ... in ...]
array_of_sub_structs = ffi.new("CSubType[]", list_of_sub_structs)
struct.a_field = array_of_sub_structs

These arrays are contiguous copies of the list of structs. The problem is not that the sub-structs in the list get cleared by the gc (as I thought earlier), but that any sub-sub-structs and/or sub-sub-arrays of these sub-structs get cleared when the sub-struct gets cleared.

Wow, this PR is interesting, in being quite technical/deep on two very different topics 😅

I replaced anyio with sniffio and made sure it worked with with the changed in https://github.com/pygfx/rendercanvas/pull/41. This is ready from my end.


[IOTDB-1117][Distributed]Batched creation and fetch of RemoteSeriesRe…

Deliver readers of the same partition in batches to form a RemoteMultSeriesReader.
A MultiSeriesRawDataPointReader is created for readers of the same local partition in batches.
Construct an AssignPathManagedMergeReader for multiple partitions of the same sequence and implement it by using the MultPriorityMergeReader class.

Good job, but there are still some small issues. I think the definition and usage of IMultReader are confusing, especially that some classes are defined as Mult but only have Single behavior.

I refactor code， please review again.

@mychaow @neuyilan @LebronAl  hi, could you please review?
Thanks


feat(EMS-2474): No PDF - Your buyer - Buyer financial information page setup

Introduction :pencil2:
This PR sets up the buyer information page
Resolution :heavy_check_mark:

Added buyer information page controllers and routes and content strings
Added unit tests
Added e2e test

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main-application-no-pdf@87b2f92). Click here to learn what that means.

:exclamation: Current head 3fbdb9b differs from pull request most recent head 64872b7. Consider uploading reports for the commit 64872b7 to get more accurate results

Additional details and impacted files
@@                    Coverage Diff                     @@
##             main-application-no-pdf    #1848   +/-   ##
==========================================================
  Coverage                           ?   98.41%
==========================================================
  Files                              ?      508
  Lines                              ?     8476
  Branches                           ?      896
==========================================================
  Hits                               ?     8342
  Misses                             ?      134
  Partials                           ?        0

Flag
Coverage Δ

unit-test
98.41% <0.00%> (?)

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

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


Update config to point to main branch

the current edit button points to master branch, not main branch
example:
https://docs.microsoft.com/en-us/java/api/overview/azure/resourcemanager-appservice-readme?view=azure-java-stable
this causes problems when we are trying edit the docs, so creating this PR to make this change


No config chosen

I created an android application with map activity and I did all configurations.
map used to work but now it doesn't. I get this error
java.lang.IllegalArgumentException: No config chosen at com.google.maps.api.android.lib6.gmm6.vector.ak.a(:com.google.android.gms.DynamiteModulesB:25) at com.google.maps.api.android.lib6.gmm6.vector.ba.f(:com.google.android.gms.DynamiteModulesB:147) at com.google.maps.api.android.lib6.gmm6.vector.ba.run(:com.google.android.gms.DynamiteModulesB:11)

Hi, this seems to be an issue with the Google Maps Android API. Could you file it on the official issue tracker for that API, as documented here.


Stale osr-rover-code submodule reference

A newly built rover using information as of mid-August, pulling down everything via git clone --recurse-submodules, was unable to run the rover software due to two issues:

To drive LED matrix, ros.launch kicks off screen.py when it should be arduino_comm.py. Looks like this has been resolved in the osr-rover-code repo but open-source-rover repo still points to now-stale rover-code @5858da7 without the fix.

To talk to motor controllers, roboclaw_wrapper.py uses hard coded device path /dev/ttyAMA0 instead of pulling from ROS parameter which specified /dev/serial0. This is already tracked in issue 34 of the osr-rover-code repo and, once addressed, will need another update of submodule reference in open-source-rover repo.

Workarounds

Edit ROS/osr_bringup/launch/ros.launch line 20 from
<node name="led_screen" pkg="led_screen" type="screen.py" respawn="true" />
To
<node name="led_screen" pkg="led_screen" type="arduino_comm.py" respawn="true" />

Edit ROS/osr/scripts/roboclaw_wrapper.py line 28 from
self.rc = Roboclaw("/dev/ttyAMA0",115200)
To
self.rc = Roboclaw("/dev/serial0",115200)

Symptoms

Because ROS/led_screen/scripts/screen.py initializes out_msg[] with invalid negative values, and never had a chance to update it with valid data before calling send_msg(), it will fail with the following error at first:

  File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 222, in <module>
    main()
  File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 216, in main
    led.send_msg()
  File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 163, in send_msg
    message.append(val)
ValueError: byte must be in range(0, 256)

Once that failure occurs, serial communication between Pi and Arduino is stuck in a bad state and any further attempts will continue to fail repeatedly with this error:
Traceback (most recent call last):
  File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 222, in <module>
    main()
  File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 212, in main
    led = LedScreen()
  File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 49, in __init__
    self.send_init()
  File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 206, in send_init
    if (ord(response[0]) == 67 and ord(response[1]) == 68):
IndexError: string index out of range

Once stuck, we'll have to power cycle the Arduino to reset it.

Because ROS/osr/scripts/roboclaw_wrapper.py is talking to the wrong port, when it attempts to communicate:

Attempting to talk to motor controller128
It will never receive a response and wait at this point forever.

Following issue @RogerRandom:
https://github.com/nasa-jpl/open-source-rover/issues/173
the osr.launch file edited as advised (in all locations):
To drive LED matrix, ros.launch kicks off screen.py when it should be arduino_comm.py. Looks like this has been resolved in the osr-rover-code repo but open-source-rover repo still points to now-stale rover-code @5858da7 without the fix.
Workaround:
Edit ROS/osr_bringup/launch/ros.launch line 20 from

To

Symptoms
Because ROS/led_screen/scripts/screen.py initializes out_msg[] with invalid negative values, and never had a chance to update it with valid data before calling send_msg(), it will fail with the following error at first:
File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 222, in
main()
File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 216, in main
led.send_msg()
File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 163, in send_msg
message.append(val)
ValueError: byte must be in range(0, 256)
Once that failure occurs, serial communication between Pi and Arduino is stuck in a bad state and any further attempts will continue to fail repeatedly with this error:
Traceback (most recent call last):
File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 222, in
main()
File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 212, in main
led = LedScreen()
File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 49, in init
self.send_init()
File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 206, in send_init
if (ord(response[0]) == 67 and ord(response[1]) == 68):
IndexError: string index out of range
Once stuck, we'll have to power cycle the Arduino to reset it.
When I run:
pi@Fidelity:~ $ roslaunch osr_bringup osr.launch
I get...
... logging to /home/pi/.ros/log/266bdef0-e799-11e9-bbfd-b827eb7e3218/roslaunch-Fidelity-1713.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://Fidelity:39217/
SUMMARY
PARAMETERS

/accel: 0,0,0,0
/battery_high: 18
/battery_low: 11
/baud_rate: 115200
/enc_max: 1380,1480,1200,1230
/enc_min: 310,345,75,425
/joy_node/autorepeat_rate: 1.0
/joy_node/coalesce_interval: 0.05
/mech_dist: 7.254,10.5,10.5,1...
/motor_controller_addresses: 128,129,130,131,132
/motor_controller_device: /dev/serial0
/qpps: 0,0,0,0
/rosdistro: kinetic
/rosversion: 1.12.14

NODES
/
joy_node (joy/joy_node)
joystick (osr/joystick.py)
led_screen (led_screen/screen.py)
motor_controller (osr/motor_controller.py)
rover (osr/rover.py)
auto-starting new master
process[master]: started with pid [1723]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to 266bdef0-e799-11e9-bbfd-b827eb7e3218
process[rosout-1]: started with pid [1736]
started core service [/rosout]
process[motor_controller-2]: started with pid [1742]
process[joystick-3]: started with pid [1749]
process[rover-4]: started with pid [1754]
process[led_screen-5]: started with pid [1756]
process[joy_node-6]: started with pid [1757]
Attempting to connect to Arduino...
10
[ERROR] [1570298065.444768066]: Couldn't open joystick force feedback!
Traceback (most recent call last):
File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 230, in
main()
File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 220, in main
led = LedScreen()
File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 49, in init
self.send_init()
File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 212, in send_init
print str(response[0])          #DEBUG
IndexError: string index out of range
[led_screen-5] process has died [pid 1756, exit code 1, cmd /home/pi/osr_ws/src/led_screen/scripts/screen.py __name:=led_screen __log:=/home/pi/.ros/log/266bdef0-e799-11e9-bbfd-b827eb7e3218/led_screen-5.log].
log file: /home/pi/.ros/log/266bdef0-e799-11e9-bbfd-b827eb7e3218/led_screen-5*.log
[led_screen-5] restarting process
process[led_screen-5]: started with pid [1788]
Attempting to connect to Arduino...
10
repeat...
Power cycling the Arduino fails to resolve the problem.
JHP
USAi Labs (formerly Houston Robotics)

To JHP:
Your error trace
File "/home/pi/osr_ws/src/led_screen/scripts/screen.py", line 230, in
main()
Indicates ROS is still launching main() of screen.py and not the correct main() in arduino_comm.py
Please double check osr.launch points to arduino_comm.py and not screen.py.

@Roger-random
What is the full path to the correct osr.launch?  (there are at least 2 and I thought I changed both)
JHP

The correct path will be dependent on your system configuration, fortunately ROS includes an utility to help us find the exact file it would use.
First, make sure you have an editor specified. I personally use nano on my Raspberry Pi so
export EDITOR=nano
Then, in the exact same environment as you would use to launch OSR code (where you would run roslaunch osr_bringup osr.launch) type rosed osr_bringup osr.launch. "ROS Edit" will bring up your $EDITOR with the exact same file in package that "ROS Launch" would use.

@Roger-random
Above when you said:
"Workarounds
Edit ROS/osr_bringup/launch/ros.launch line 20 from..."
Did you mean osr.launch instead of ros.launch as osr.launch is what I have.
In EITHER case:
pi@Fidelity:~ $ export EDITOR=nano
pi@Fidelity:~ $ rosed osr_bringup osr.launch
That file does not exist in that package.
pi@Fidelity:~ $ rosed osr_bringup ros.launch
That file does not exist in that package.
When I look for osr.launch:
pi@Fidelity:~ $ find ~/ -name osr.launch
/home/pi/osr/ROS/osr_bringup/launch/osr.launch
/home/pi/osr_ws/src/osr_bringup/launch/osr.launch
pi@Fidelity:~ $ cat /home/pi/osr/ROS/osr_bringup/launch/osr.launch
...

pi@Fidelity:~ $ cat /home/pi/osr_ws/src/osr_bringup/launch/osr.launch
...

...even though I KNOW I changed both osr.launch files!
So I changed them AGAIN.
This time roslaunch stops at the usual joystick warning and DOESN'T give me repeat errors on "index out of range".  The LED display has changed from a series of WHITE lines at the top,
to a series of GREEN lines, except the first which goes red through yellow to green.
The display doesn't tell me much, but I'm sure the detailed explanation elsewhere will translate it.]
Any idea why I get the "That file does not exist in that package" error when the files clearly exist and work?
Thanks!
JHP
USAi Labs

You shouldn't have multiple launch files, only one is necessary, and it should be in whatever workspace is set as your source destination, which you set by editing the ~/.bashrc file

my .bashrc reads as per Software Steps:
source /opt/ros/kinetic/setup.bash
source /home/pi/osr_ws/devel/setup.bash
source /home/pi/osr_ws/devel/setup.sh
so the
/home/pi/osr/ROS/osr_bringup/launch/osr.launch
version shouldn't be necessary (rename & test - correct!)
Just from playing I see the
4th set of 6 LEDs indicate red when a drive motor stalls
5th set of 4 LEDs indicate red when a corner motor moves
will have to explore the code to see what the rest do.
Some brief explanation of the display should be made part of the build instructions.
I'm thinking of finding a way to display simultaneously or alternately a banner advertising our group.
JHP


[Documentation] Apple Silicon Users

Installation Notes for Passerby Apple Silicon Users
You may have noticed that the build breaks at lithops runtime build sc-runtime -f Dockerfile. Documenting this information here so that others can get it installed properly.
brew install<EMAIL_ADDRESS>
Modify Dockerfile references:
FROM

to

FROM --platform=linux/amd64

Run the build:
lithops runtime build sc-runtime -f Dockerfile

I got this error after running the build : lithops runtime build sc-runtime -f Dockerfile

This is exaxctly what I am coming accross.

I don't have a Apple M1 machine so no idea really. @vysecurity any idea what these errors could be?

Is your Docker set up correctly on M1? There's an experimental feature to use the faster version of x64 if I recall. Maybe it's that?

I got this error after running the build : lithops runtime build sc-runtime -f Dockerfile

Install and run the docker in your machine ;)

@gustavorobertux I solve that by using linux machine, Apple Mac M1 Silicone docker is not working well this the docker build architecture.


Support for [new] .. string concatenation operator introduced in vim 8.1.1114

patch 8.1.1114: confusing overloaded operator "." for string concatenation
Problem:    Confusing overloaded operator "." for string concatenation.
Solution:   Add ".." for string concatenation.  Also "let a ..= b".
Vint currently doesnt understand '..' as a string concatenation operator.

Thanks for the report.
Needs to go into vimlparser first I guess: https://github.com/vim-jp/vim-vimlparser/issues/95


CSO events for gui user password expiry are not periodic

Describe the bug
CSO event when GUI User expired of remote cluster is coming before 24 Hours , where it should be after completion of 24 Hours.
How to Reproduce?

Install CSI 2.10 (PR1002 Image)

[root@saurabh6-master ~]# oc get pods
NAME                                                  READY   STATUS    RESTARTS        AGE
ibm-spectrum-scale-csi-attacher-b6b6d4948-5kfcn       1/1     Running   0               6h56m
ibm-spectrum-scale-csi-attacher-b6b6d4948-pz77p       1/1     Running   0               6h56m
ibm-spectrum-scale-csi-operator-567f8455f5-l7ntt      1/1     Running   1 (6h57m ago)   2d1h
ibm-spectrum-scale-csi-provisioner-b456fbb49-tzlsx    1/1     Running   0               6h56m
ibm-spectrum-scale-csi-resizer-84d84bfdf6-x798x       1/1     Running   0               6h56m
ibm-spectrum-scale-csi-sj7wj                          3/3     Running   0               6h56m
ibm-spectrum-scale-csi-snapshotter-656d4bd64f-s8fv9   1/1     Running   0               6h56m
ibm-spectrum-scale-csi-vbkvw                          3/3     Running   0               6h56m
[root@saurabh6-master ~]# oc get cso
NAME                     VERSION   SUCCESS
ibm-spectrum-scale-csi   2.10.0    True
[root@saurabh6-master ~]# oc describe pod | grep quay
    Image:         quay.io/badri_pathak/ibm-spectrum-scale-csi-operator:events_gui_pass_v9
    Image ID:      quay.io/badri_pathak/ibm-spectrum-scale-csi-operator@sha256:a31ef1636903b3f3f75406cc463d0045a5064c7db12d59b07a322e89259e2065
      CSI_DRIVER_IMAGE:      quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:ee9bd3e431cf0d3fb1e407a6e2ed51d6be957dd1445c2cd88f329cbb5b1ea494
    Image:         quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:ee9bd3e431cf0d3fb1e407a6e2ed51d6be957dd1445c2cd88f329cbb5b1ea494
    Image ID:      quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:31172dc13f5cc514cf2474cb440697c1da20d035f3fd12ec761f12b06cc2e0a7
    Image:         quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:ee9bd3e431cf0d3fb1e407a6e2ed51d6be957dd1445c2cd88f329cbb5b1ea494
    Image ID:      quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:31172dc13f5cc514cf2474cb440697c1da20d035f3fd12ec761f12b06cc2e0a7

Expire the password of storage cluster which is being used by CSI
[root@csi-86-scalegui ~]# /usr/lpp/mmfs/gui/cli/chuser remoteadmin --expirePassword
Check CSO event after 24 Hours

Events:
  Type     Reason         Age                  From              Message
  ----     ------         ----                 ----              -------
  Normal   CSIConfigured  17m (x9 over 24h)    CSIScaleOperator  The CSI driver resources have been created/updated successfully
  Warning  AuthError      17m (x3 over 3h48m)  CSIScaleOperator  Either the username/password is incorrect or the password has been expired for the Scale GUI clusterIds: [227604367530725699]

Expected behavior
CSO events should come after 24 hours only , as per above cso event is coming before 3h48m , Also this event is coming 3 times which is also not expected
Data Collection and Debugging
/scale-csi/D.1005

The current manager uses default period which is 10hrs to execute Reconcile loop of the controller everytime.
The gui-password expiry check is being called on the every reconcile irrespect of the setting any RequeueAfter of 24 hours i.e. reconcile after every 24hrs because by deafult reconcile happens in 10hrs.
If needed to perform manual reconcile before auto reconcile loop we need to set SyncPeriod while manager creation of each controller and accordance to RequeueAfter in the Reconcile function.
e.g.
mgr, err := ctrl.NewManager(ctrl.GetConfigOrDie(), ctrl.Options{
		Scheme:             scheme,
		MetricsBindAddress: metricsAddr,
		...
		NewCache:                cache.MultiNamespacedCacheBuilder(namespaces),
		SyncPeriod:              &syncPeriod,
	})

Reference manager options<EMAIL_ADDRESS>

Normal   CSIConfigured  17m (x9 over 24h)    CSIScaleOperator  The CSI driver resources have been created/updated successfully
Warning  AuthError      17m (x3 over 3h48m)  CSIScaleOperator  Either the username/password is incorrect or the password has been expired for the Scale GUI clusterIds: [227604367530725699]

The password expiry is being checked on every reconcile. Here the last event of password expiry has happened 17m ago, this could be because the reconcile has happened because of other reasons. The password expiry checks is not the reason for this non-periodic time. There are various reasons for reconciles.


Does this crate support any USB function?

I can see the USB support exists in esp-hal, but I failed to find anything about USB in this crate.
Is it possible to use USB with this crate, such as ESP-IDF builtin TinyUSB components, or something equivalent to Peripherals::USB0?

I think there is currently no wrapper written for TinyUSB in this crate. This is only effecting esp32s2/s3 and because other's don't have USB CDC-ACM support correct? Currently one would have to use esp-idf-sys and interact with it directly, though i am not sure if all the headers are exposed. When using esp-idf v4.4 it should be included, but with v5 it is now an external component.
So to answer your question -> I am not sure what it is in no_std about Peripherals::USB0, but you can use the normal USB functionality to use it as an virtual serial connection, or use it for jtag debugging and programming. For further TinyUSB support - PR's are always welcome. But thanks for bringing it up on the radar.

Thanks for the reply.
I tried several approaches to include TinyUSB into the project which uses esp-idf-hal but didn't work.
I don't have too much experience with ESP-IDF, could you please show me some clues or hints about the task?

If you don't have a lot of experience with ESP-IDF itself than this is a hard problem. Because you need to directly interact with the provided c functions from ESP-IDF to get it started. If you want to give it a shot here are some rough pointers.
Assuming you are building ontop of esp-idf v4.4.4.

read the TinyUSB esp-idf docs extensively and understand what the complete API can do DOCS
make sure you can interact with the API through esp-idf-sys -> Some simple way to checkout if the headers are exposed to rust is to have a look inside the bindings.rs generated on build. Build a hello world program with esp-idf-sys and find it somewhere in target/xtensa.../debug/build/esp-idf-sys.../out/bindgen.rs
Interact with the esp-idf API through it.
Profit

Depending on your knowledge this is a fun project, but you should have a good grasp of thinks first. If you want to learn more best is to try to understand the wrapper code we already written and how are things can be done. Have fun with this info.

Thanks for the guidance.
Finally, I managed to make every piece work together, an demo project is at https://github.com/windoze/esparrier-idf, which is an ESP32-based USB HID device with a Barrier/Synergy client to allow the user to use remote keyboard and mouse on the local computer without needs to install any driver or app.
Despite a lot of hacks, the program works and the only existing problem is that ESP32S3 seems to have huge lags (sometimes 100+ms) over WIFI, but I think it's totally off-topic here.
Thanks again for the information and your kind help.

One more question, does this crate support ESP-IDF 5? I can only find settings for 4.4 and master.

some guys are using it with esp-idf 5. Though we not made it official a switch but it will probably happen not in the far future. The settings you are talking about are about cargo generate template ? You can edit it manually to set it for example to the taged version v5.0.1 and try it out.

I tried to create a brand new project from esp-idf-template and change the ESP-IDF version to release/v5.0 in .cargo/config.toml, also I changed rustflags to ["--cfg", "espidf_time64"] as comments instructed.
But cargo build reported an error:
   --> /Users/windoze/.cargo/registry/src/github.com-1ecc6299db9ec823/esp-idf-svc-0.45.0/src/espnow.rs:126:53
    |
126 |         esp!(unsafe { esp_now_register_recv_cb(Some(Self::recv_callback)) })?;
    |                                                ---- ^^^^^^^^^^^^^^^^^^^ expected struct `esp_now_recv_info`, found `u8`
    |                                                |
    |                                                arguments to this enum variant are incorrect

Do I need to use git head of esp-idf-svc and/or esp-idf-hal to make it work?

First we deviate quite a bit from the original issue -> For quick questions the matrix chat is always a good place, alternative create new issues for new topics.
That said when using first its always best to not use release/5.0 or release/v4.4 as they are moving git targets. better use the fixed release tags -> v5.0.1 or v4.4.4. Yes it is better to use git master of esp-idf-hal/svc for using esp-idf 5 currently

Sorry for being off-topic, I'll close this one and submit new issues when I've further questions.
Thanks again for your help.


Disable swipe to close

Hi guys, there are any ways that I can disable Draggable or Swipe to close ?

Hey @hoanghai9650, do you mean this feature?
val sheetState = rememberFlexibleBottomSheetState(
    skipHiddenState = true,
    ..
)


Added new matched User-Agent's, Highlighted Stories and some UserResponse properties

New User-Agent's fixed Google Play header and LoginWebView related issues like  #173
Added some missing properties to UserResponse like follow counts, profile context vs..
Added Highlighted Stories request

Added Friendship response for follow, unfollow requests instead of Status response.

Counters on Useris part of handler.users.user request; If send request with primaryKey counter values returns. I'm using it in my app.
I tested new User-Agents in different devices, networks and I've also tested with your repo Swiftagram it works for any request with LoginWebView.
I didn't tested without LoginWebView.

Replying here so it's easier to follow.
I'm perfectly aware User-like instances when called directly return counters (for instance in /users/:id/info), but they don't in most other cases when User like structures are returned: followers, media users, tags, etc. I was just stating that and that's reason why they were never included, cause they are optional fields, definitely not required in the endpoint response schema.
But I finally agree with adding them, definitely not a problem 💪
About the user agent, there's no point in even storing it then since you write it in Device but never read it, as requests fallback to the default one.
So I suggest removing it entirely then.

Just the better understand; should I remove the parts related to device or User-Agent?

Just the definition of userAgent from Device: it's never read so it serves no purpose.

Just the definition of userAgent from Device: it's never read now, so it serves no purpose. 😊

😊 Its removed.

Great 💪
I'll deal with linting (there are some trailing whitespaces, so it might fail in Travis, but no worries), merging this and bumping the pod version, np.
Do you know why the CI report is not showing up here? 😢  @TheM4hd1

@sbertix no idea what happened, it shows on travis panel, but not sure why it disabled here.


Create CONTRIBUTING.md  - InfluxDB v2

creating a new CONTRIBUTING for InfluxDB v2.
We need to revise the Test Cases section for sure and review the remaining content to ensure it's consistent with the current build, test, pprof, etc.

re-opening. This still needs some help.

Bad stale bot!
I will take care of making sure this gets done.

@8none1 could you please make sure this is good to go and get all the changes merged next week?

i think every section that refers to GOPATH needs to be re-written to exclude it.  that includes many of the examples.


Error while connecting to Helvar router 910

Hi, thank you for putting this together. I was trying out your code with my Helvar 910 router. Im getting this error below.
Any ideas?
Connecting to router at address: <IP_ADDRESS>...
Connected to router on workgroup: x.
Initializing router...
Request command<EMAIL_ADDRESS>triggered an error back from the router<EMAIL_ADDRESS>Request command<EMAIL_ADDRESS>triggered an error back from the router<EMAIL_ADDRESS>Traceback (most recent call last):
File<EMAIL_ADDRESS>line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File<EMAIL_ADDRESS>line 87, in _run_code
exec(code, run_globals)
File "/Users/x/.vscode/extensions/ms-python.python-2023.8.0/pythonFiles/lib/python/debugpy/adapter/../../debugpy/launcher/../../debugpy/main.py", line 39, in
cli.main()
File "/Users/x/.vscode/extensions/ms-python.python-2023.8.0/pythonFiles/lib/python/debugpy/adapter/../../debugpy/launcher/../../debugpy/../debugpy/server/cli.py", line 430, in main
run()
File "/Users/x/.vscode/extensions/ms-python.python-2023.8.0/pythonFiles/lib/python/debugpy/adapter/../../debugpy/launcher/../../debugpy/../debugpy/server/cli.py", line 284, in run_file
runpy.run_path(target, run_name="main")
File "/Users/x/.vscode/extensions/ms-python.python-2023.8.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_runpy.py", line 321, in run_path
return _run_module_code(code, init_globals, run_name,
File "/Users/x/.vscode/extensions/ms-python.python-2023.8.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_runpy.py", line 135, in _run_module_code
_run_code(code, mod_globals, init_globals,
File "/Users/x/.vscode/extensions/ms-python.python-2023.8.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_runpy.py", line 124, in _run_code
exec(code, run_globals)
File "/Users/x/code/helvar-prufa/test.py", line 44, in
asyncio.run(main())
File<EMAIL_ADDRESS>line 44, in run
return loop.run_until_complete(main)
File<EMAIL_ADDRESS>line 616, in run_until_complete
return future.result()
File "/Users/x/code/helvar-prufa/test.py", line 30, in main
await router.initialize()
File "/Users/x/.local/share/virtualenvs/helvar-prufa-qfz8EuSG/lib/python3.8/site-packages/aiohelvar/router.py", line 207, in initialize
await self.get_scenes()
File "/Users/x/.local/share/virtualenvs/helvar-prufa-qfz8EuSG/lib/python3.8/site-packages/aiohelvar/router.py", line 222, in get_scenes
await get_scenes(self, self.groups)
File "/Users/x/.local/share/virtualenvs/helvar-prufa-qfz8EuSG/lib/python3.8/site-packages/aiohelvar/scenes.py", line 74, in get_scenes
parts = response.result.strip("@").split("@")
AttributeError: 'NoneType' object has no attribute 'strip'

Hi Gardart, not sure if you managed to solve this.
Looking at the HelvarNET documentation, it seems that the reply 11 is on the address which indicates that the device at that IP address does not exist.


fixed autocapitalize cursor issue

fixed the cursor issue http://g.recordit.co/I5kZVj8LQK.gif
fixed when you type select * from foo then move the cursor back to * and add date_trunc it will capitalize DATE but not lowercase it again when typing further. http://g.recordit.co/hTB7BCuB0C.gif

Coverage remained the same at 81.226% when pulling 543cd94038b14f0d6e700fdb2e85f01c0d641323 on meri/fix-cursor into 3d94765d493764441b7b103dea42743df2a34908 on master.

Coverage remained the same at 81.226% when pulling 543cd94038b14f0d6e700fdb2e85f01c0d641323 on meri/fix-cursor into 3d94765d493764441b7b103dea42743df2a34908 on master.

Coverage remained the same at 81.226% when pulling 543cd94038b14f0d6e700fdb2e85f01c0d641323 on meri/fix-cursor into 3d94765d493764441b7b103dea42743df2a34908 on master.

Coverage remained the same at 81.226% when pulling 543cd94038b14f0d6e700fdb2e85f01c0d641323 on meri/fix-cursor into 3d94765d493764441b7b103dea42743df2a34908 on master.

Coverage remained the same at 81.226% when pulling 543cd94038b14f0d6e700fdb2e85f01c0d641323 on meri/fix-cursor into 3d94765d493764441b7b103dea42743df2a34908 on master.

Coverage remained the same at 81.226% when pulling 543cd94038b14f0d6e700fdb2e85f01c0d641323 on meri/fix-cursor into 3d94765d493764441b7b103dea42743df2a34908 on master.

Coverage remained the same at 81.226% when pulling 7b3e2f605ec4990494e3ef898a6c48ff10e36cf5 on meri/fix-cursor into 3d94765d493764441b7b103dea42743df2a34908 on master.

Coverage remained the same at 81.226% when pulling 7b3e2f605ec4990494e3ef898a6c48ff10e36cf5 on meri/fix-cursor into 3d94765d493764441b7b103dea42743df2a34908 on master.

Coverage remained the same at 81.226% when pulling 7b3e2f605ec4990494e3ef898a6c48ff10e36cf5 on meri/fix-cursor into 3d94765d493764441b7b103dea42743df2a34908 on master.

Coverage remained the same at 81.226% when pulling 7b3e2f605ec4990494e3ef898a6c48ff10e36cf5 on meri/fix-cursor into 3d94765d493764441b7b103dea42743df2a34908 on master.

Coverage remained the same at 81.226% when pulling 7b3e2f605ec4990494e3ef898a6c48ff10e36cf5 on meri/fix-cursor into 3d94765d493764441b7b103dea42743df2a34908 on master.

Coverage remained the same at 81.226% when pulling 7b3e2f605ec4990494e3ef898a6c48ff10e36cf5 on meri/fix-cursor into 3d94765d493764441b7b103dea42743df2a34908 on master.

Codecov Report

Merging #174 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #174   +/-   ##
=======================================
  Coverage   81.11%   81.11%
=======================================
  Files          16       16
  Lines        1859     1859
=======================================
  Hits         1508     1508
  Misses        351      351

Impacted Files
Coverage Δ

src/crate/crash/repl.py
51.56% <100%> (ø)
:white_check_mark:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3d94765...7b3e2f6. Read the comment docs.

Coverage remained the same at 81.226% when pulling 451b1fd7b65716ce849b3c3730968a2c1b5f91fb on meri/fix-cursor into 3d94765d493764441b7b103dea42743df2a34908 on master.

@m-kharbat please wait for green CI

Coverage remained the same at 81.226% when pulling f14c266f45bb2a0e48bc5bd1b463829af48cb156 on meri/fix-cursor into 3d94765d493764441b7b103dea42743df2a34908 on master.

Coverage remained the same at 81.226% when pulling f14c266f45bb2a0e48bc5bd1b463829af48cb156 on meri/fix-cursor into 3d94765d493764441b7b103dea42743df2a34908 on master.


Add license files

Add license files so they'll be included in packages crates (this is a requirement for the MIT license in particular).

Approved, will be part of 1.2.0 release.


Support maximum micro batch size

The connector will aggressively empty the queue for every micro batch. Meaning RabbitMQ is no longer doing any work as a queue and instead Spark has to handle peaks by queuing batches. This is fine if Spark is running stable, but throughput peaks can mean for us a very long queue in Spark. Unfortunately this exposes us to more risk of data loss:

Data is safer sitting on the Rabbit queue than having to rely on checkpointing for a restart.
The system is far more likely to crash when the queue is large i.e. you are setting yourself up for data loss on every crash.
If the system crashes, it can become impossible to restart it as the first batch will completely empty the queue, causing another high throughput crash.

A solution would be to provide an option of limiting the maximum micro batch size that RabbitMQ connector is allowed to ack from RabbitMQ.

It looks like it's not as simple as limiting by count - once you've called store, it's handled by the executor. kafta-spark-consumer supports limiting throughput with "back pressure" https://github.com/dibbhatt/kafka-spark-consumer/blob/master/src/main/java/consumer/kafka/ReceiverLauncher.java. They attach a streaming listener to update a streaming rate that's managed by zookeeper meta data. I don't know if there'a a way to do this without using zookeeper.

Never mind. I found spark.streaming.receiver.maxRate. Also looks like back pressure is supported in later versions of Spark.