Update documentation

Update documentation to include BFS use of this library

@flybrianfly Can you please make me understand the issue a bit better? That would really help me

Hi @AlkaDas991, thanks for your interest in this issue. SdFat supports many Arduino devices and has documentation in HTML format in the docs folder. I think it would be beneficial to pull out the relevant objects and methods for Teensy 3.x and 4.x processors and move them into the README in Markdown format, especially focused on how to use the builtin SD card on Teensy 3.5, 3.6, and 4.1.
I think our MPU-9250 library is an example of one that is well documented.
As you may be aware on the Teensy Forum, there are many questions related to how to use the SD card, which I think points to a need to have some more clear documentation on the subject. We have been using the SD card in our projects (i.e. the logger library), but I think having better documentation and some clear examples would really help.
We have similar requests for our core library and navigation library.


Recording - Open Channel/ iOS - Delete message

DeleteMessageOpenChannel
Click ‘Create’ to create new open channel
Name channel ‘Foodies’
Click ‘Create’
Enter ‘Foodies’ channel

Omar sends: I completely forgot about our dinner plans tonight, was the reservation for 5:00pm?
Daniel sends: No, it’s at 6:00 pm now. Joyce changed it last night
Joyce sends at the same time as Daniel: I changed it to 6:00 instead!

As user ‘Joyce’, hold down message sent above
Click ‘Delete’

Ready

@justinbaldwin
https://drive.google.com/file/d/1iOI2CD7zeqP6zm9sR_ihSMgW0oHEuJGa/view?usp=sharing

@justinbaldwin - Light
https://drive.google.com/file/d/1cIjhaQx83JqsArqar_FshedJ6nvFeYJi/view?usp=sharing

@chrischabot ready for review
https://drive.google.com/file/d/1cIjhaQx83JqsArqar_FshedJ6nvFeYJi/view?usp=sharing


Refactor cookbook to use files, instead of 'content' blocks for semodule building

@BackSlasher this one is going to be a more significant change to how the module provider works. Right now it can only handle a single .te file, which is not enough in the case where you need to build a fully fledged semodule, including interfaces and file types.
For this I propose to re-factor the provider to support the usage of cookbook files that contain the actual .te/.fc/.if content, furthermore I will also move the actual compilation into it's own folder within the Chef.temp folder such as to exclude any accidents if anyone needs to create more than one module.

Sounds legit. I only used the module resource to support my own modules, which were ridiculously simple. I have no issue with you extending the resource to support more use-cases. Could you describe the way the resource should look (A snippet describing how you'd use it)?
This will be a challenge. I still want to support very simple modules, contained entirely in the recipe (maybe keep a simple_module or make this a complex_module). I guess some people will also want to use templates as file sources, but if that can't be accommodated it's OK.
Capital idea.

It seems like it would be less intrusive to add a "file" attribute, in addition to the content/name/force attributes that the module resource already exposes.

I think so too (that's how they do it in puppet btw, I prefer that), but I wonder if it's un-Chef-like

My gut instinct is that separate providers would more closely match the stuff from Opscode, with cookbook_file vs. file being the closest example. I hacked a helper to do what I needed right this second, but am looking forward to seeing the proposed changes :)

Just writing in case it wasn't clear - I'm waiting to see some code - either the resource definition or a usage example

Sorry for the delay, here is the pull request: https://github.com/BackSlasher/chef-selinuxpolicy/pull/26

Should be solved in 0.9.0


TypeError: _stack_dispatcher() got an unexpected keyword argument 'dtype'

got prompt
Loading model from /home/sam/ComfyUI/models/Molmo/molmo-7B-D-bnb-4bit
Unused kwargs: ['_load_in_4bit', '_load_in_8bit', 'quant_method']. These kwargs are not used in <class 'transformers.utils.quantization_config.BitsAndBytesConfig'>.
We will use 90% of the memory on device 0 for storing the model, and 10% for the buffer to avoid OOM. You can set max_memory in to a higher value to use more memory (at your own risk).
Loading checkpoint shards: 100%|██████████████████████████████████████████████████████████| 2/2 [00:02<00:00,  1.39s/it]
Model and processor have been unloaded, and CUDA cache has been cleared.
!!! Exception during processing !!! _stack_dispatcher() got an unexpected keyword argument 'dtype'
Traceback (most recent call last):
File "/home/sam/ComfyUI/execution.py", line 323, in execute
output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
File "/home/sam/ComfyUI/execution.py", line 198, in get_output_data
return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
File "/home/sam/ComfyUI/execution.py", line 169, in _map_node_over_list
process_inputs(input_dict, i)
File "/home/sam/ComfyUI/execution.py", line 158, in process_inputs
results.append(getattr(obj, func)(**inputs))
File "/home/sam/ComfyUI/custom_nodes/ComfyUI-Molmo/Molmo7BDbnb.py", line 170, in generate_caption
inputs = self.processor.process(
File "/home/sam/.cache/huggingface/modules/transformers_modules/molmo-7B-D-bnb-4bit/preprocessing_molmo.py", line 145, in process
out = self.image_processor.multimodal_preprocess(
File "/home/sam/.cache/huggingface/modules/transformers_modules/molmo-7B-D-bnb-4bit/image_preprocessing_molmo.py", line 525, in multimodal_preprocess
crops, image_tokens, patch_idx, img_mask = self.preprocess(
File "/home/sam/.cache/huggingface/modules/transformers_modules/molmo-7B-D-bnb-4bit/image_preprocessing_molmo.py", line 450, in preprocess
crops, image_tokens, patch_ordering, img_mask = self.image_to_patches_and_tokens(
File "/home/sam/.cache/huggingface/modules/transformers_modules/molmo-7B-D-bnb-4bit/image_preprocessing_molmo.py", line 235, in image_to_patches_and_tokens
tiling = select_tiling(
File "/home/sam/.cache/huggingface/modules/transformers_modules/molmo-7B-D-bnb-4bit/image_preprocessing_molmo.py", line 138, in select_tiling
original_size = np.stack([h, w], dtype=np.float32)  # [1, 2]
File "<array_function internals>", line 179, in stack
TypeError: _stack_dispatcher() got an unexpected keyword argument 'dtype'

My ComfyUI :
** Platform: Linux
** Python version: 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0]
** Python executable: /home/sam/ComfyUI/venv/bin/python
** ComfyUI Path: /home/sam/ComfyUI
** Log path: /home/sam/ComfyUI/comfyui.log
Total VRAM 24576 MB, total RAM 31689 MB
pytorch version: 2.4.1+cu121
xformers version: 0.0.28.post1
Set vram state to: NORMAL_VRAM
Device: cuda:0 NVIDIA GeForce RTX 3090 : cudaMallocAsync
Using xformers cross attention

Find a solution 👍
pip install numpy==1.24.4


Eternal "Enabling cmake-server support requires that VSCode be restarted"

Hi,
Thank you for this fantastic extension!
After updating from VSCode 1.13 to 1.13.1 I get an info box saying "Enabling cmake-server support requires that VSCode be restarted". Restarting VSCode doesn't help - it will just show up again. Likely side-effect: I can configure my project using the "CMake: " button, but I never get a build "button" next to it.
That's on Linux with VSCode
Version 1.13.1
Commit 379d2efb5539b09112c793d3d9a413017d736f89
Date 2017-06-14T18:18:03.540Z
Shell 1.6.6
Renderer 56.0.2924.87
Node 7.4.0

What can I provide to help debug this?
Axel.

@Axel-Naumann It is likely dup of #173 if your CMake version is < 3.7.2
Either update CMake version (to have nice Server Mode support) or temporary set cmake.useCMakeServer to false to get rid of the message.

Darn, I should have found that one (but expected an open issue)! You're right, it's 3.7.1! It would've been nice to be told differently than "pleas restart" :-) but that's still an error on my side; your doc clearly states the limitation. Thanks & apologies for the bogus ticket!


Add schedules to the labels of map nodes

Without this, SDFV needs to re-calculate the node label on each draw call

Closed as discussed, not necessary


MIDI Machine sequencing on port2 via MDSeqTrack, preliminary

Compiles, completely untested.
Not sure if note length is correct.
Arpeggiator code needs to be looked at as well for the MIDI Machine type.

So this is partly working. It'll trigger notes, chords and velocity is working including parameter locks.
However, note length is not doing anything. and not sure if the CCs are working.


TNT-43012 Return default content items

Note: DO NOT MERGE until target-upstream v0.0.56 with support for characteristics -> scopeType is released to production.
Description

Support default content proposition items delivered for control experiences with no offer content.
Related Issue

https://jira.corp.adobe.com/browse/TNT-43012
Motivation and Context

Support default content propositions in the response, so that customers know when a control experience is selected.
Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (non-breaking change which does not add functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA or I'm an Adobe employee.
[x] I have made any necessary test changes and all tests pass.
[x] I have run the Sandbox successfully.

@XDex Your PR title is referring to the wrong TNT number.

@ninaceban As we discussed today, I'll wait for your A4T PR to get merged before adding the mods to mark default content items as renderable actions

@ninaceban @jonsnyder I've implemented support for default-content items when renderDecisions=true, with proper grouping  to view/mbox scopes, please take another look when you get a chance.
Note - This PR requires the support of characteristics -> scopeType to be released in Target upstream before being merged, see https://jira.corp.adobe.com/browse/TNT-43696
Thank you!


Register OpenGL buffer for interoperability?

How can I register an OpenGL buffer for use in my CUDA/HIP kernel?
oroGraphicsMapResources(int count, oroGraphicsResource_t * resources, oroStream_t stream) expects a registered resource as its second parameter but there is no oroGraphicsRegisterX functions (although oroGraphicsUnregisterResource exists). I would expect the oroGraphicsGLRegisterBuffer and oroGraphicsGLRegisterImage functions to be present in Orochi API but there are no such functions.
The DX12 example of this repo doesn't really help as it uses a sharedHandle created specifically with the DX12 API:
oroExternalMemoryHandleDesc externalMemoryHandleDesc;
externalMemoryHandleDesc.type = oroExternalMemoryHandleTypeD3D12Resource;
externalMemoryHandleDesc.handle.win32.handle = sharedHandle;
externalMemoryHandleDesc.size = actualSize;
externalMemoryHandleDesc.flags = ORO_EXTERNAL_MEMORY_DEDICATED;

oroImportExternalMemory(&gOroExtMem, &externalMemoryHandleDesc);

Is it somehow possible to adapt this example for OpenGL buffers or is there something simpler I missed in Orochi's API?

I tried doing it with HIP (not Orochi), but I still cannot get past hipGraphicsGLRegisterBuffer:
#include "GL/glew.h"
#include "GLFW/glfw3.h"
#include "Orochi/Orochi.h"

#include <iostream>

int main()
{
	glfwInit();
	glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 4);
	glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3);
	GLFWwindow* window = glfwCreateWindow(1280, 720, "Test OpenGL Interop", NULL, NULL);
	glfwMakeContextCurrent(window);

	glewInit();

	oroInitialize(oroApi::ORO_API_HIP, 0);
	oroInit(0);

	GLuint buffer;
	glGenBuffers(1, &buffer);
	glBindBuffer(GL_ARRAY_BUFFER, buffer);
	glBufferData(GL_ARRAY_BUFFER, 1024, nullptr, GL_DYNAMIC_DRAW);

	hipGraphicsResource* buffer_resource;
	if (hipGraphicsGLRegisterBuffer(&buffer_resource, buffer, hipGraphicsRegisterFlagsNone) != hipSuccess)
	{
		std::cerr << hipGetErrorString(hipGetLastError()) << std::endl;
		return 3;
	}

	return 0;
}

The above piece of code prints "invalid argument" as hipGraphicsGLRegisterBuffer returns an hipErrorInvalidValue error.
I also tried textures with hipGraphicsGLRegisterImage but I got the exact same issue.

It's not merged yet but you can get the functionality in a branch we'll merge. https://github.com/GPUOpen-LibrariesAndSDKs/Orochi/blob/feature/ORO-0-ogl/Test/OpenGL/main.cpp


Add Bean Validation support to belgif-rest-problem-spring

At CBSS, we don't (currently) use Spring Boot for implementing REST APIs. So the belgif-rest-problem-spring library is not completely on par with the belgif-rest-problem-java-ee library.
One of the lacking features is Bean Validation support.
More specifically, an ExceptionMapper for converting whatever exception the Spring Framework throws in case of a Bean Validation constraint violation, to a BadRequestProblem, similar to what is done in belgif-rest-problem-java-ee with
ConstraintViolationExceptionMapper and ConstraintViolationUtil.

Created pull request, ready for review


Add support for cohorts in create_test_subset script

Closes https://github.com/populationgenomics/metamist/issues/770

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

Project coverage is 77.30%. Comparing base (b8121aa) to head (daca8cc).

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #813   +/-   ##
=======================================
  Coverage   77.30%   77.30%
=======================================
  Files         157      157
  Lines       13010    13010
=======================================
  Hits        10057    10057
  Misses       2953     2953

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


Protect from arrays with ElementType.ElementSize >= 64k

This can't be encoded in the EEType (and in the array GCDescs, for that
matter).
I'm removing checked arithmetic from the GCDesc encoder because that
code runs before ComponentSize emission, but it's not the right place to
check for this, because this also applies to value types with no GC
pointers.

LGTM


Update some dependencies

Update all backend dependencies and only Sentry frontend dependency

Hey!
Looks great, thanks for your contribution!


Add a 'useStaticContext' hook

This PR adds a useStaticContext hook, to get a hold of the staticContext without needing to instantiate a Route wrapper.
This just mirrors the work already done to achieve e.g. useLocation.

I'm also open to alternative suggestions or code-changes here 🙂


Update SAML2 auth sessionkey cookie path

Description
This change will set the sessionkey under the /client/api path. This commit should prevent duplicate sessionkey cookies from being set on both /client (incorrect) and /client/api (correct). Prior to this commit, the /client version was being set while the /client/api version remained unchanged with an invalid sessionkey. As a result, subsequent requests after the SAML2 authentication would immediately fail with an invalid session and results in the user being logged out.
The sessionkey is now set explicitly for the /client/api path which should fix this issue, regardless of the SSO URL and path that's being used.

Fixes: #6127

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

I've built <IP_ADDRESS> with this change and SAML2 auth is now working as expected again.

Hi @kohrar is this PR still valid after the UI fixes?

I would think so. The UI issue is a separate issue. The original issue was that the session key cookie was set with a different path by the browser, resulting in the valid session key being ignored by the invalid key set previously.
The UI issue is merely an interface issue with the login page which can be worked around by refreshing the login page. The cookie issue here can't be worked around unless cookies are cleared completely.

@nvazquez a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_multiplication_x: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 3124

@blueorangutan package

@nvazquez a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 3131

@blueorangutan test

@nvazquez a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-3868)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 35798 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr6149-t3868-kvm-centos7.zip
Smoke tests completed. 88 look OK, 5 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_01_add_primary_storage_disabled_host
Error
0.57
test_primary_storage.py

test_01_primary_storage_nfs
Error
0.11
test_primary_storage.py

ContextSuite context=TestStorageTags>:setup
Error
0.19
test_primary_storage.py

test_03_deploy_and_scale_kubernetes_cluster
Failure
34.14
test_kubernetes_clusters.py

test_04_autoscale_kubernetes_cluster
Failure
685.81
test_kubernetes_clusters.py

test_07_deploy_kubernetes_ha_cluster
Failure
62.51
test_kubernetes_clusters.py

test_08_upgrade_kubernetes_ha_cluster
Failure
36.05
test_kubernetes_clusters.py

test_09_delete_kubernetes_ha_cluster
Failure
33.86
test_kubernetes_clusters.py

ContextSuite context=TestKubernetesCluster>:teardown
Error
130.03
test_kubernetes_clusters.py

test_01_secure_vm_migration
Error
155.55
test_vm_life_cycle.py

test_02_unsecure_vm_migration
Error
270.22
test_vm_life_cycle.py

test_03_secured_to_nonsecured_vm_migration
Error
144.95
test_vm_life_cycle.py

test_08_migrate_vm
Error
43.71
test_vm_life_cycle.py

test_02_list_snapshots_with_removed_data_store
Error
8.45
test_snapshots.py

test_02_list_snapshots_with_removed_data_store
Error
8.45
test_snapshots.py

test_hostha_enable_ha_when_host_in_maintenance
Error
307.04
test_hostha_kvm.py

@blueorangutan package

@rohityadavcloud a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 3158

@blueorangutan test

@rohityadavcloud a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-3920)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 31620 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr6149-t3920-kvm-centos7.zip
Smoke tests completed. 93 look OK, 0 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File


Support SET command

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
(This section helps Arrow developers understand the context and why for this feature, in addition to  the what)
a SET command to change the value in config_options
Describe the solution you'd like
A clear and concise description of what you want to happen.
following what postgresql has except [LOCAL]
https://www.postgresql.org/docs/current/sql-set.html
assignment operator should support both TO and =
value should support single quoted string / number / bool / non space separate string
SET [VARIABLE] [TO | =] [VALUE | 'VALUE']

e.g.
❯ set datafusion.execution.batch_size = 1;

❯ set datafusion.execution.coalesce_batches to 'false';

support alias TIME ZONE and TIMEZONE (same as postgrseql https://www.postgresql.org/docs/current/sql-set.html)
❯ set time zone = 1;

note that this should return error for now as discussed in https://github.com/apache/arrow-datafusion/issues/3148#issuecomment-1226105182
cc @avantgardnerio @alamb
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

YES!  This will be awesome
Note there is still some nonsense related to Config settings (e.g. see https://github.com/apache/arrow-datafusion/pull/3885#pullrequestreview-1152448744) but I think supporting the SET command will provide us that much more reason to unify the configuration story


Simulator covered by shadows in Python/JS tutorial

Describe the bug
Simulator covered by shadows in Python/JS tutorial
Steps to reproduce the behavior

Navigate to https://arcade.makecode.com/beta#
Tutorials---->Chase the Pizza---->JavaScript Start Tutorial

Actual behavior
Simulator covered by shadows in Python/JS tutorial. And you need to click Play button at the beginning.
Expect behavior
Simulator shows normally. And you don't need to click Play button at the beginning.
Actual Recording

Expect Recording

Additional context
1.OS: Windows10
2.arcade version: 1.10.19
6.Microsoft MakeCode version: 8.2.14

This is a regression

Bug is about double layout of simulator. It is expected that in manaco the simulator is stopped by default.


Allow lists in secrets.yaml

Use case discussed here: https://github.com/danielwelch/hassio-zigbee2mqtt/issues/259

You need also to address the CI issues. As next, the current implementation on addon/validate.py does support only single types. If you want list support, you need to extend the validator to work correctly with this.

I guess my proposal would be to move this: https://github.com/home-assistant/hassio/blob/f5c171e44fd8dd4333b7a94b9b846a707401eb90/hassio/addons/validate.py#L359-L364
out of _single_validate, and instead do something like this
def validate(struct):
        """Create schema validator for add-ons options."""
        options = {}

        # read options
        for key, value in struct.items():
            # Ignore unknown options / remove from list
            if key not in raw_schema:
                _LOGGER.warning("Unknown options %s", key)
                continue

           # Lookup secret
           if str(value).startswith("!secret "):
               secret: str = value.partition(" ")[2]
               value = coresys.secrets.get(secret)
           if value is None:
               raise vol.Invalid(f"Unknown secret {secret}")

            typ = raw_schema[key]
            try:
                if isinstance(typ, list):
                    # nested value list
                    options[key] = _nested_validate_list(coresys, typ[0], value, key)
                elif isinstance(typ, dict):
                    # nested value dict
                    options[key] = _nested_validate_dict(coresys, typ, value, key)
                else:
                    # normal value
                    options[key] = _single_validate(coresys, typ, value, key)
            except (IndexError, KeyError):
                raise vol.Invalid(f"Type error for {key}") from None

        _check_missing_options(raw_schema, options, "root")
        return options

    return validate

Could work, please add some tests to verify that it works. Thanks

Any future plan on this?


This seems dead, no action in 4 months...that's years in internet age.

If anybody is offering commercialized support, please leave a pointer.   Currently, we are forced to do design workarounds to avoid existing bugs, affecting user experience.

i have not seen any contributions from anyone myself on this. I really love this semantic ui implementation so I hope it stays alive and progresses!!

fully agree, great implementation... no jQuery!...  we're basing a commercial product on this, which maybe is a mistake, because the bugs we find are in some basic components (e.g. drop-down listbox, tooltip).  So, if the authors have given up on that, then you can use this for prototyping and mini-apps only.

might be worth you checking out Clarity Design System.. its a nice alternative .

According to some earlier PRs raised. @edcarroll is travelling around the world at the moment and the project is on hold until he's back.

Thanks for that pointer, @scblur869 . It does look nice. I'm building a large commercial application and the bugs on this build are a huge blocker.

@stephenasamoah what specific bugs that are blockers for your application? We are researching using it ourselves and we are trying to get some insight. Thanks!

I'm sorry for the lack of communication about the project. Things have been extremely busy over the last 6 months, and although things will remain busy I'm hoping to be able to start working through the backlog in the coming weeks.


Keyboard cannot be hidden when TextField action item show

Keyboard cannot be hidden when long press TextField show paste\copyaction  item , accurate， Keyboard will be reopen when I click hide button .
In addition, the number of pop-up paste\copyaction  item also seems to affect the keyboard（Using a third party keyboard） .
https://user-images.githubusercontent.com/10770362/109121565-60e4e700-7782-11eb-87a3-be45ee2c89fe.mp4

——
Test device： Mi 11（Android 11） 、HuaWei VOG-AL10（P30pro Androd10）、 Vivo S7（Android 10）、 Virtual Device （Android 11 x86_64 Using a third party keyboard ）
——

Steps to Reproduce
As shown in the video before ：

1、Enter some numbers in the TextField
2、long press or double press TextField and show paste\copy item
3、click hide keyboard button
4、keyboard will be reopen

Expected results:  keyboard hidden when I click hide button
Actual results:  keyboard will be reopen when I click hide button

ps : This problem can be avoided set enableInteractiveSelection: false  , but I don't think it's a good way .

update:
It looks like when you click the  TextField  to  keyboard, The requestkeyboard  would be multiple  called in editable_text .
In the process:

1、the first requestKeyboard is due to onSingleTapUp

2、When there is some content in the TextField  , sometimes two onSingleTapUp will cause the requestkeyboard  would be multiple  called in editable_text .I not  sure  if this will affect this issue.

3、When I click to hide the keyboard, there will be a TextInputClient.updateEditingState  Event  call  requestKeyboard to pop up the keyboard again.

Logs

no error log

no analysis log

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel unknown, 1.22.5, on macOS 11.2.1 20D74 darwin-x64, locale
    zh-Hans-CN)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 12.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.1)
[!] IntelliJ IDEA Ultimate Edition (version 2018.3.5)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] Connected device (5 available)

@AlexV525 Hey, how did you repro this, i can not repro this. 😭

Me and @xu-baolin tested on the latest master and beta (1.26.0-17.7.pre) branch, and it's no reproducible on these branches. But it did repro on stable. So I assume it's been fixed by recent commits. Can you verify that? @CarGuo

It fixed in master


Modify scalar's url in overview.md

fixed the scalars's url

Thanks @lonyehan for the fix. Just to note fixing the docs in docs/ folder will apply to the next version of the docs if you wanted to fix the latest as well can you make the same cahnge in packages/website/versioned_docs/latest

Thanks @timotheeguerin for remind me that.
I will modify the document in packages/website/versioned_docs/latest  too.

@microsoft-github-policy-service agree


Fix parsing metadata key-value pairs

Fixes how metadata key-value pairs are split so that values can contain color characters.
Addresses #511

I'm only on my first cup of coffee... so apologies for my braindumb, but this is still not working for me. I see the updated regex in your file changes but when I build (npx grunt build), the dist/showdown.js gets updated with the old, broken code, and thus, my app still fails with colons in the metadata 🤔 Same if I try my app with package.json dependancies of "showdown": "https://github.com/zzzzBov/showdown/tree/fix-metadata-colons",.
Is dist not getting created properly? I mean, dist is checked in (which is odd)... so maybe it's getting overwritten?


fix: list only assigned drivers for unassign

updated to use listAssignedDrivers function
use drivers get function to get name
also catch 404 from driver get to but instead of weeding out drivers, here we just give the driver the name <deleted driver> so the user can still clean it up and remove it

Types of Changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] I have read the CONTRIBUTING document
[x] My code follows the code style of this project (npm run lint produces no warnings/errors)
[ ] Any required documentation has been added
[ ] I have added tests to cover my changes

:tada: This PR is included in version 1.0.5 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


hax takes more than 1 minute to stop

Single-node cluster:
$ hctl shutdown
Stopping m0d@0x7200000000000001:0xc (ios) at centos79...
Stopped m0d@0x7200000000000001:0xc (ios) at centos79
Stopping m0d@0x7200000000000001:0x9 (confd) at centos79...
Stopped m0d@0x7200000000000001:0x9 (confd) at centos79
Stopping hare-hax at centos79...
 !!!!!!!!!!!   STUCK FOR MORE THAN 1 MINUTE HERE  !!!!!!!!
Stopped hare-hax at centos79
Stopping hare-consul-agent at centos79...
Stopped hare-consul-agent at centos79
Shutting down RC Leader at centos79...

Log:
$ sudo systemctl status hare-hax -l
● hare-hax.service - HAX daemon for Hare
   Loaded: loaded (/usr/lib/systemd/system/hare-hax.service; static; vendor preset: disabled)
   Active: failed (Result: signal) since Mon 2021-05-17 18:23:10 BST; 1min 24s ago
  Process: 10699 ExecStart=/bin/sh -c cd /var/motr/hax && exec /opt/seagate/cortx/hare/bin/hax (code=killed, signal=KILL)
 Main PID: 10699 (code=killed, signal=KILL)

May 17 18:21:53 centos79 hare-hax[10699]: motr[10699]:  d720   WARN  [ha/halon/interface.c:537:halon_interface_link_disconnected_cb]  hl=0x7f06f8043ca0 ep=<IP_ADDRESS>@tcp:12345:2:2
May 17 18:21:55 centos79 hare-hax[10699]: motr[10699]:  d960   WARN  [ha/link.c:1513:ha_link_outgoing_fom_tick]  rlk_rc=-110 endpoint=<IP_ADDRESS>@tcp:12345:2:1
May 17 18:21:55 centos79 hare-hax[10699]: motr[10699]:  d680   WARN  [ha/halon/interface.c:451:halon_interface_msg_is_not_delivered_cb]  hl=0x7f06f8020da0 ep=<IP_ADDRESS>@tcp:12345:2:1 tag=101
May 17 18:21:55 centos79 hare-hax[10699]: 2021-05-17 18:21:55,555 [INFO] {Dummy-1} Message delivery failed, endpoint'<IP_ADDRESS>@tcp:12345:2:1', process fid = 0x0:0x0tag= 101
May 17 18:21:55 centos79 hare-hax[10699]: motr[10699]:  d720   WARN  [ha/halon/interface.c:537:halon_interface_link_disconnected_cb]  hl=0x7f06f8020da0 ep=<IP_ADDRESS>@tcp:12345:2:1
May 17 18:23:10 centos79 systemd[1]: hare-hax.service stop-sigterm timed out. Killing.
May 17 18:23:10 centos79 systemd[1]: hare-hax.service: main process exited, code=killed, status=9/KILL
May 17 18:23:10 centos79 systemd[1]: Stopped HAX daemon for Hare.
May 17 18:23:10 centos79 systemd[1]: Unit hare-hax.service entered failed state.
May 17 18:23:10 centos79 systemd[1]: hare-hax.service failed.

Vaibhav Prakash Paratwar commented in Jira Server:

[~520414] are we still seeing this? cc [~520513] [~520478]


[Enhancement] Request that these binaries should be uploaded to maven central to enable simple integration with build scripts.

This has been requested to be submitted by me on behalf of a user:
fod-uploader-java:
https://github.com/fod-dev/fod-uploader-java
binaries currently here:
https://github.com/fod-dev/fod-uploader-java/releases
these binaries should be uploaded to maven central to enable simple integration with build scripts.
currently the jar file has to be downloaded manually and stored in source control which is a primitive way of working.

I would be more inclined to do that if it weren't a "deployable" and acted more as a library.  Also, Maven Central has a pretty long verification process if I remember correctly.  I'll look into possibly pushing this to our Fortify JCenter Org.

Thank you so much sir.


Feature Request Load All Thumbnails by default

Please correct me if i am wrong but not all thumbnails are generated unless the user scrolls downward to the last of the page.
I do not see any option that will generate all thumbnails on load so this is a feature request.

Please see https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#allthepages, hence no such option will be added (since a thumbnail is essentially just a page at a smaller size).


Remove dll's from extensions

To clean up de repository we should remove the Local packages folder and dll's that are on the extensions.

These have been removed from git with a filter repo.


OIDC service scopes applied to all token requests

I noticed that the application and OIDC service scope limits were not applied to OIDC client credentials grants, ie client credentials grant requests could get assign any scope to the access tokens.  I've attempted to fix it in the DefaultTokenGenerator classes by removing scopes from the requested scopes that aren't allowed by the application / service.  Subsequent testing showed that the OIDC service scope limits could be avoided by using the /oauth2.0/ token endpoints instead, so I've pushed scopes down into the OAuth services.
I'm not sure if there's anywhere I've missed where a similar scope calculation needs to occur or whether this could be solved in a better way, happy to take suggestions.

Thanks for the patch.

I've pushed scopes down into the OAuth services.

I don't think this is something we can reasonably take in via a pull request. The work to handle this is quite large, and I do see this PR is missing quite a few more places to run the same check, plus real integration tests, (unit tests alone are not enough here), plus documentation, etc. To accommodate all of this, (and I am not sure you have the bandwidth to handle this all), it will take quite some time, and the reviews would be very difficult since the number of modified files would continue to grow.
Is there a smaller variant where you could just handle a fix for OIDC, and leave OAuth alone for the time being?

@mmoayyed thanks for the feedback and review.  I'm afraid I wouldn't have the bandwidth to handle fully adding scopes to the oauth support (as much as I'd like to).
I've reworked this patch to remove the oauth scopes field and created a(n almost) functional type that can evaluate the allowed scopes for a token request context.
You also mentioned it missing places to run the same check, did they pertain to OIDC and are they still missing in this patch?  If so, any hints where they might be?

@mmoayyed any thoughts on this?

Haven't had time to give this a proper review. Please merge with master once and I'll see if I can offer suggestions later this week or the next.

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

This appears to have been taken care of now, and should be more or less correct with 6.6 or the current master. Please follow up if you see otherwise. Thank you!


Color#fromHex need polish

Related to #32235
static fromHex(hex: string): Color | null;

The API doesn't use null but undefined
The jsdoc-comment used html, we use markdown, the return type isn't documeted

No longer valid any more.


ParseError when using openstreetmap(nominatim) reverse geocoder

When parsing a response from openstreetmap geocoder nominatim in a function
private func parseResultPlace(_ json: JSON) -> Place
the library is trying to access a fields "address" -> "city",  "address" -> "city_district" that do not exist.
Example request URL:
https://nominatim.openstreetmap.org/reverse?format=json&lat=55.766403&lon=37.584307&addressdetails=1&limit=1
Example response JSON:
{
    "place_id": 198709562,
    "licence": "Data © OpenStreetMap contributors, ODbL 1.0. https://osm.org/copyright",
    "osm_type": "relation",
    "osm_id": 3834185,
    "lat": "55.76649205",
    "lon": "37.5847426655174",
    "display_name": "Школа №1950, 28 с1, Зоологическая улица, Кудрино, Presnensky District, Central Administrative Okrug, Moscow, Central Federal District, 123056, Russia",
    "address": {
        "school": "Школа №1950",
        "house_number": "28 с1",
        "road": "Зоологическая улица",
        "suburb": "Presnensky District",
        "state_district": "Central Administrative Okrug",
        "state": "Moscow",
        "postcode": "123056",
        "country": "Russia",
        "country_code": "ru"
    },
    "boundingbox": [
        "55.7661513",
        "55.7668406",
        "37.5841336",
        "37.585355"
    ]
}

It seems we need to send an additional request with osm_id to get the city
Address lookup section in a link below:
https://wiki.openstreetmap.org/wiki/Nominatim

I've tried to get lookup data from osm_id:
https://nominatim.openstreetmap.org/reverse?format=json&osm_type=R&osm_id=3834185&addressdetails=1&extratags=1
but I didn't get any extra data, in fact it's the same place in address:
{
    "place_id": 198709562,
    "licence": "Data © OpenStreetMap contributors, ODbL 1.0. https://osm.org/copyright",
    "osm_type": "relation",
    "osm_id": 3834185,
    "lat": "55.76649205",
    "lon": "37.5847426655174",
    "display_name": "Школа №1950, 28 с1, Зоологическая улица, Кудрино, Presnensky District, Central Administrative Okrug, Moscow, Central Federal District, 123056, Russia",
    "address": {
        "school": "Школа №1950",
        "house_number": "28 с1",
        "road": "Зоологическая улица",
        "suburb": "Presnensky District",
        "state_district": "Central Administrative Okrug",
        "state": "Moscow",
        "postcode": "123056",
        "country": "Russia",
        "country_code": "ru"
    },
    "extratags": {},
    "boundingbox": [
        "55.7661513",
        "55.7668406",
        "37.5841336",
        "37.585355"
    ]
}

I've also tried with Rome:
https://nominatim.openstreetmap.org/reverse?format=json&lat=41.931725&lon=12.517384&addressdetails=1&limit=1
And the result contains the city data:
{
    "place_id": 198986782,
    "licence": "Data © OpenStreetMap contributors, ODbL 1.0. https://osm.org/copyright",
    "osm_type": "relation",
    "osm_id": 5473366,
    "lat": "41.9279026",
    "lon": "12.5157982106648",
    "display_name": "Quartiere XVII Trieste, Via Acherusio, Municipio Roma II, Rome, RM, Lazio, 00199, Italy",
    "address": {
        "address29": "Quartiere XVII Trieste",
        "road": "Via Acherusio",
        "suburb": "Municipio Roma II",
        "city": "Rome",
        "county": "RM",
        "state": "Lazio",
        "postcode": "00199",
        "country": "Italy",
        "country_code": "it"
    },
    "boundingbox": [
        "41.9129308",
        "41.9428268",
        "12.4984614",
        "12.5266728"
    ]
}

I think it maybe a point with missing data.


python311Packages.google-cloud-pubsub: 2.21.4 -> 2.21.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.google-cloud-pubsub is: Google Cloud Pub/Sub API client library
meta.homepage for python311Packages.google-cloud-pubsub is: https://github.com/googleapis/python-pubsub
meta.changelog for python311Packages.google-cloud-pubsub is: https://github.com/googleapis/python-pubsub/blob/v2.21.3/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.21.3 with grep in /nix/store/ikik18srh7zzl5wfkwykl9cb57l1xj84-python3.11-google-cloud-pubsub-2.21.3
found 2.21.3 in filename of file in /nix/store/ikik18srh7zzl5wfkwykl9cb57l1xj84-python3.11-google-cloud-pubsub-2.21.3

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath

home-assistant-component-tests.google_pubsub
home-assistant-component-tests.nest
python311Packages.google-cloud-pubsub
python311Packages.google-nest-sdm
python312Packages.google-cloud-pubsub
python312Packages.google-nest-sdm

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ikik18srh7zzl5wfkwykl9cb57l1xj84-python3.11-google-cloud-pubsub-2.21.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.google-cloud-pubsub https://github.com/r-ryantm/nixpkgs/archive/d52626e65bd02fe5708c71fb5124ca3df2650bbb.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/d52626e65bd02fe5708c71fb5124ca3df2650bbb#python311Packages.google-cloud-pubsub

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ikik18srh7zzl5wfkwykl9cb57l1xj84-python3.11-google-cloud-pubsub-2.21.3
ls -la /nix/store/ikik18srh7zzl5wfkwykl9cb57l1xj84-python3.11-google-cloud-pubsub-2.21.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

10 packages built:

home-assistant-component-tests.google_pubsub
home-assistant-component-tests.nest
python311Packages.google-cloud-pubsub
python311Packages.google-cloud-pubsub.dist
python311Packages.google-nest-sdm
python311Packages.google-nest-sdm.dist
python312Packages.google-cloud-pubsub
python312Packages.google-cloud-pubsub.dist
python312Packages.google-nest-sdm
python312Packages.google-nest-sdm.dist

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.google-cloud-pubsub is: Google Cloud Pub/Sub API client library
meta.homepage for python311Packages.google-cloud-pubsub is: https://github.com/googleapis/python-pubsub
meta.changelog for python311Packages.google-cloud-pubsub is: https://github.com/googleapis/python-pubsub/blob/v2.21.5/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.21.5 with grep in /nix/store/0vbvpc9zd2nk7d9hn8lqspf5zaadawvr-python3.11-google-cloud-pubsub-2.21.5
found 2.21.5 in filename of file in /nix/store/0vbvpc9zd2nk7d9hn8lqspf5zaadawvr-python3.11-google-cloud-pubsub-2.21.5

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath

home-assistant-component-tests.google_pubsub
home-assistant-component-tests.nest
python311Packages.google-cloud-pubsub
python311Packages.google-nest-sdm
python312Packages.google-cloud-pubsub
python312Packages.google-nest-sdm

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0vbvpc9zd2nk7d9hn8lqspf5zaadawvr-python3.11-google-cloud-pubsub-2.21.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.google-cloud-pubsub https://github.com/r-ryantm/nixpkgs/archive/5e2f3b11252c494aa4041fc7fe5b39ff3b9d2b33.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5e2f3b11252c494aa4041fc7fe5b39ff3b9d2b33#python311Packages.google-cloud-pubsub

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0vbvpc9zd2nk7d9hn8lqspf5zaadawvr-python3.11-google-cloud-pubsub-2.21.5
ls -la /nix/store/0vbvpc9zd2nk7d9hn8lqspf5zaadawvr-python3.11-google-cloud-pubsub-2.21.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

10 packages built:

home-assistant-component-tests.google_pubsub
home-assistant-component-tests.nest
python311Packages.google-cloud-pubsub
python311Packages.google-cloud-pubsub.dist
python311Packages.google-nest-sdm
python311Packages.google-nest-sdm.dist
python312Packages.google-cloud-pubsub
python312Packages.google-cloud-pubsub.dist
python312Packages.google-nest-sdm
python312Packages.google-nest-sdm.dist

Maintainer pings


Microservices, Docker, and Kubernetes

Project Tye should be introduced as well

Looking forward for Tye, will you also cover Microsoft Orleans and Dapr?

Looking forward for Tye, will you also cover Microsoft Orleans and Dapr?


Fix compiling on Windows, and fix tests against ExactPredicates by refining float range

Fixes #4. Since the algorithms are said to be guaranteed correct only for exponents in $[-142, 201]$, the tests against ExactPredicates now only test in this range.
I accidentally included my Windows fixes in this branch so I closed #3 and am using this for both. Hopefully that's fine.

Was using 141 when it should be 142, should be good now


Support new fields

Plugin name and version
Server port

Added via 01439e4a07d842fdc0dbb41e9a15de29f794ae16

published with v0.6.1


carousel don't work

http://plnkr.co/edit/WXGMkC5mUvC03NrQSk06?p=preview
angular 1.4.7

This version is right
https://github.com/angular-ui/bootstrap/blob/8899fc8e850d227a8dd384d61f7a092bf7471ef6/src/carousel/carousel.js

Dude, do you even open source?

@allendongyx, I'm not really sure what you're attempting to accomplish.  Our demo is working fine.
Perhaps if you gave us more information we can point you in the right direction.  Until then, I'm closing this issue.  Thanks.


auth: Save ext_auth_id for LDAP

https://chat.zulip.org/#narrow/stream/31-production-help/topic/EMail.20changes.20in.20LDAP/near/998915
Testing Plan:
I started writing tests. But I really do not know how to finish it.
I wrote a test that tests that.
Needing help
I would like to have some help with the TODO in backends.py Line 840 and the tests.

rebased of master. changed dict to be non-nullable

@strifel do you have time to update this effort?
Adding a note that it should close #24104 when completed.

I do want to finish this PR finally and I will try to finish this in the coming weeks.

Awesome! I'll be on vacation next week but @mateuszmandera should be around to help push this forward in the meantime.

I merged https://github.com/zulip/zulip/pull/24285 with a reference to this PR. I think even once we finish this, we'll largely want the text that's there to explain the default state when this feature isn't configured, so I expect we can just do the docs for this feature as an edit on that section.

@strifel Do you perhaps have some kind of note on what remains to be done in this PR?

@mateuszmandera sadly not really.
I need to

fix the failing tests (again)
work through your change requests
check that the code does actually make sense


Documentation

Add documentation

Quick question: can we support Google pydoc format? It looks better.

Changed to Google pydoc format.


Some fixes to new-version

I’m currently not using symfony standards. But I’m willing to use them.
The added PHPDocs are something that I find obsolete (they add no value to the code, since php 7.1 already adds everything). Can you remove that from your PR?

Hi, I've decided that I don't want "symfony standards" in a PHP library that has nothing to do with symfony...
Hmm can you tell why my travis keeps on failing?
https://travis-ci.org/jeroendesloovere/vcard/jobs/315791035

Never mind. I fixed it.


Added test case for calculate outcomes

A set_seed at the start of calculate_outcomes should be sufficient, and we don't need to set the seed for every function, but in case there's a lot going on right now, we can open up an issue on this and tackle this later.


Add Sentry.withScope

Currently there's no way to modify a scope for a single event without global side effect.
The Unified API includes a couple of ways to do that: pushScope/popPop and withScope.
Works like:
Sentry.withScope(scope => {
    scope.setTag(..);
    Sentry.captureException(..)

Turns out this isn't on develop.sentry.dev so we need to add there, or figure out why it's not there anymore

it was a conscious decision not to do it, what's the use case? it was not done because it'd require push scope and pop scope and it's not really useful for global scope mode.
ideally, we'd likely do as iOS which is an optional withScope block -> https://github.com/getsentry/sentry-cocoa/blob/master/Sources/Sentry/SentrySDK.m#L176-L187
but we wanted this feature to get mature.

a workaround could be Sentry.captureEvent(SentryEvent(exception, tags)), and this event has your tags or whatever you like.

it was a conscious decision not to do it, what's the use case?

The use case is adding a tag to an event I'm capturing without having that tag show up in any other event that comes after that.

it was not done because it'd require push scope and pop scope and it's not really useful for global scope mode.

Agree push and pop doesn't make sense with global scopes, bu we can have single scope and still allow a scope to be mutated through a clone. On withScope, the method will take a clone of the current (global) scope and pass that as an argument to the callback. That would then be isolated from the global scope as it's a clone.

ideally, we'd likely do as iOS which is an optional withScope block -> https://github.com/getsentry/sentry-cocoa/blob/master/Sources/Sentry/SentrySDK.m#L176-L187
but we wanted this feature to get mature.

Yeah I agree that's a better approach than withScope. It came after the original API design was just passing a callback as a second argument, such as:
Sentry.captureException(e, s => { s.setTag("my-tag","on a cloned, isolated scope" });

this arguably reads best because the withScope thing, since the scope object in the callback isn't explicitly passed to capture, looks like magic.
I'll update the issue title

Is this method supposed to be only available on the static Sentry class?

iOS already does it, https://docs.sentry.io/platforms/apple/enriching-events/scopes/#scope-callback
it'd be an optional param to the capture methods.
Hub would take an optional Scopeand use it if passed, otherwise use the scope from the _peek


vLLM 0.5.4 failure to start the TP+ PP mode on 8 ARC

The vllm docker image is
intelanalytics/ipex-llm-serving-xpu-vllm-0.5.4-experimental:2.2.0b1
vLLM start command is
'model="/llm/models/Qwen2-72B-Instruct/"
served_model_name="Qwen2-72B-Instruct"
source /opt/intel/1ccl-wks/setvars.sh
export SYCL_PI_LEVEL_ZERO_USE_IMMEDIATE_COMMANDLISTS=2
python -m ipex_llm.vllm.xpu.entrypoints.openai.api_server
--served-model-name $served_model_name
--port 8000
--model $model
--trust-remote-code
--gpu-memory-utilization 0.85
--device xpu
--dtype float16
--enforce-eager
--load-in-low-bit fp8
--max-model-len 2048
--max-num-batched-tokens 2048
--max-num-seqs 24
-tp 4 -pp 2 --disable-log-requests'
The error information is
(WrapperWithLoadBit pid=35347) 2024:09:13-11:21:50:(35347) |CCL_ERROR| exchange_utils.cpp:202 sendmsg_fd: condition !check_msg_retval("sendmsg", send_bytes, iov, msg, sizeof(u.cntr_buf), sock, fd) failed
(WrapperWithLoadBit pid=35347)  errno: Broken pipe
2024:09:13-11:21:50:(31157) |CCL_ERROR| exchange_utils.cpp:202 sendmsg_fd: condition !check_msg_retval("sendmsg", send_bytes, iov, msg, sizeof(u.cntr_buf), sock, fd) failed
errno: Broken pipe
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386] Error executing method init_device. This might cause deadlock in distributed execution.
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386] Traceback (most recent call last):
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386]   File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/worker_base.py", line 378, in execute_method
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386]     return executor(*args, **kwargs)
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386]            ^^^^^^^^^^^^^^^^^^^^^^^^^
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386]   File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/xpu_worker.py", line 105, in init_device
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386]     self.init_worker_distributed_environment()
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386]   File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/xpu_worker.py", line 205, in init_worker_distributed_environment
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386]     get_pp_group().all_reduce(torch.zeros(1).xpu())
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386]   File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/distributed/parallel_state.py", line 293, in all_reduce
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386]     torch.distributed.all_reduce(input_, group=self.device_group)
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386]   File "/usr/local/lib/python3.11/dist-packages/torch/distributed/c10d_logger.py", line 47, in wrapper
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386]     return func(*args, **kwargs)
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386]            ^^^^^^^^^^^^^^^^^^^^^
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386]   File "/usr/local/lib/python3.11/dist-packages/torch/distributed/distributed_c10d.py", line 2055, in all_reduce
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386]     work.wait()
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386] RuntimeError: oneCCL: exchange_utils.cpp:202 sendmsg_fd: EXCEPTION:  errno: Broken pipe
ERROR 09-13 11:21:51 worker_base.py:386] Error executing method init_device. This might cause deadlock in distributed execution.
ERROR 09-13 11:21:51 worker_base.py:386] Traceback (most recent call last):
ERROR 09-13 11:21:51 worker_base.py:386]   File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/worker_base.py", line 378, in execute_method
ERROR 09-13 11:21:51 worker_base.py:386]     return executor(*args, **kwargs)
ERROR 09-13 11:21:51 worker_base.py:386]            ^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR 09-13 11:21:51 worker_base.py:386]   File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/xpu_worker.py", line 105, in init_device
ERROR 09-13 11:21:51 worker_base.py:386]     self.init_worker_distributed_environment()
ERROR 09-13 11:21:51 worker_base.py:386]   File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/xpu_worker.py", line 205, in init_worker_distributed_environment
ERROR 09-13 11:21:51 worker_base.py:386]     get_pp_group().all_reduce(torch.zeros(1).xpu())
ERROR 09-13 11:21:51 worker_base.py:386]   File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/distributed/parallel_state.py", line 293, in all_reduce
ERROR 09-13 11:21:51 worker_base.py:386]     torch.distributed.all_reduce(input_, group=self.device_group)
ERROR 09-13 11:21:51 worker_base.py:386]   File "/usr/local/lib/python3.11/dist-packages/torch/distributed/c10d_logger.py", line 47, in wrapper
ERROR 09-13 11:21:51 worker_base.py:386]     return func(*args, **kwargs)
ERROR 09-13 11:21:51 worker_base.py:386]            ^^^^^^^^^^^^^^^^^^^^^
ERROR 09-13 11:21:51 worker_base.py:386]   File "/usr/local/lib/python3.11/dist-packages/torch/distributed/distributed_c10d.py", line 2055, in all_reduce
ERROR 09-13 11:21:51 worker_base.py:386]     work.wait()
ERROR 09-13 11:21:51 worker_base.py:386] RuntimeError: oneCCL: exchange_utils.cpp:202 sendmsg_fd: EXCEPTION:  errno: Broken pipe
Process Process-65:
Traceback (most recent call last):
File "/usr/lib/python3.11/multiprocessing/process.py", line 314, in _bootstrap
self.run()
File "/usr/lib/python3.11/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/usr/local/lib/python3.11/dist-packages/ipex_llm/vllm/xpu/entrypoints/openai/rpc/server.py", line 220, in run_rpc_server
server = AsyncEngineRPCServer(async_engine_args, usage_context, port, load_in_low_bit)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/ipex_llm/vllm/xpu/entrypoints/openai/rpc/server.py", line 27, in init
self.engine = AsyncLLMEngine.from_engine_args(async_engine_args,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/ipex_llm/vllm/xpu/engine/engine.py", line 43, in from_engine_args
return super().from_engine_args(engine_args, start_engine_loop, usage_context, stat_loggers)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/engine/async_llm_engine.py", line 476, in from_engine_args
engine = cls(
^^^^
File "/usr/local/lib/python3.11/dist-packages/ipex_llm/vllm/xpu/engine/engine.py", line 29, in init
super().init(*args, **kwargs)
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/engine/async_llm_engine.py", line 381, in init
self.engine = self._init_engine(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/engine/async_llm_engine.py", line 557, in _init_engine
return engine_class(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/engine/llm_engine.py", line 255, in init
self.model_executor = executor_class(
^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/executor/ray_xpu_executor.py", line 35, in init
super().init(*args, **kwargs)
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/executor/ray_gpu_executor.py", line 555, in init
super().init(*args, **kwargs)
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/executor/distributed_gpu_executor.py", line 25, in init
super().init(*args, **kwargs)
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/executor/xpu_executor.py", line 53, in init
self._init_executor()
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/executor/ray_gpu_executor.py", line 61, in _init_executor
self._init_workers_ray(placement_group)
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/executor/ray_gpu_executor.py", line 230, in _init_workers_ray
self._run_workers("init_device")
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/executor/ray_gpu_executor.py", line 468, in run_workers
self.driver_worker.execute_method(method, *driver_args,
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/worker_base.py", line 387, in execute_method
raise e
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/worker_base.py", line 378, in execute_method
return executor(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/xpu_worker.py", line 105, in init_device
self.init_worker_distributed_environment()
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/xpu_worker.py", line 205, in init_worker_distributed_environment
get_pp_group().all_reduce(torch.zeros(1).xpu())
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/distributed/parallel_state.py", line 293, in all_reduce
torch.distributed.all_reduce(input, group=self.device_group)
File "/usr/local/lib/python3.11/dist-packages/torch/distributed/c10d_logger.py", line 47, in wrapper
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/torch/distributed/distributed_c10d.py", line 2055, in all_reduce
work.wait()
The workaround is
vi /usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/xpu_worker.py
            get_pp_group().all_gather(torch.zeros(1).xpu())
            #get_pp_group().all_reduce(torch.zeros(1).xpu())

After use modify the /usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/xpu_worker.py with the
get_pp_group().all_gather(torch.zeros(1).xpu())
vLLM start with the following error
2024:09:14-11:02:35:(  241) |CCL_WARN| topology recognition shows PCIe connection between devices. If this is not correct, you can disable topology recognition, with CCL_TOPO_FABRIC_VERTEX_CONNECTION_CHECK=0. This will assume XeLinks across devices
2024:09:14-11:02:35:(  241) |CCL_WARN| topology recognition shows PCIe connection between devices. If this is not correct, you can disable topology recognition, with CCL_TOPO_FABRIC_VERTEX_CONNECTION_CHECK=0. This will assume XeLinks across devices
-----> current rank: 0, world size: 4, byte_count: 33554432
(WrapperWithLoadBit pid=3548) -----> current rank: 1, world size: 4, byte_count: 33554432
(WrapperWithLoadBit pid=4874) INFO 09-14 11:01:33 selector.py:127] Cannot use _Backend.FLASH_ATTN backend on XPU. [repeated 13x across cluster] (Ray deduplicates logs by default. Set RAY_DEDUP_LOGS=0 to disable log deduplication, or see https://docs.ray.io/en/master/ray-observability/user-guides/configure-logging.html#log-deduplication for more options.)
(WrapperWithLoadBit pid=4874) INFO 09-14 11:01:33 selector.py:76] Using IPEX attention backend. [repeated 13x across cluster]
(WrapperWithLoadBit pid=4874) 2024:09:14-11:01:32:( 4874) |CCL_WARN| did not find MPI-launcher specific variables, switch to ATL/OFI, to force enable ATL/MPI set CCL_ATL_TRANSPORT=mpi [repeated 6x across cluster]
(WrapperWithLoadBit pid=4874) 2024:09:14-11:01:33:( 5291) |CCL_WARN| no membind support for NUMA node 1, skip thread membind [repeated 6x across cluster]
(WrapperWithLoadBit pid=3548) 2024:09:14-11:02:35:( 3548) |CCL_WARN| topology recognition shows PCIe connection between devices. If this is not correct, you can disable topology recognition, with CCL_TOPO_FABRIC_VERTEX_CONNECTION_CHECK=0. This will assume XeLinks across devices [repeated 392x across cluster]
(WrapperWithLoadBit pid=4211) -----> current rank: 0, world size: 4, byte_count: 33554432 [repeated 3x across cluster]
(WrapperWithLoadBit pid=4211) 2024:09:14-11:02:42:( 4211) |CCL_WARN| topology recognition shows PCIe connection between devices. If this is not correct, you can disable topology recognition, with CCL_TOPO_FABRIC_VERTEX_CONNECTION_CHECK=0. This will assume XeLinks across devices [repeated 168x across cluster]
(WrapperWithLoadBit pid=4211) GPU-Xeon4410Y-ARC770:rank4: Assertion failure at psm3/ptl_am/ptl.c:196: nbytes == req->req_data.recv_msglen
(WrapperWithLoadBit pid=4211) 2024-09-14 11:02:34,843 - INFO - Loading model weights took 9.7260 GB [repeated 6x across cluster]
(WrapperWithLoadBit pid=4211) [1726282973.117141429] GPU-Xeon4410Y-ARC770:rank4.perWithLoadBit.execute_method: Reading from remote process' memory failed. Disabling CMA support
(WrapperWithLoadBit pid=4874) -----> current rank: 3, world size: 4, byte_count: 33554432 [repeated 3x across cluster]
(WrapperWithLoadBit pid=4874) 2024:09:14-11:02:42:( 4874) |CCL_WARN| topology recognition shows PCIe connection between devices. If this is not correct, you can disable topology recognition, with CCL_TOPO_FABRIC_VERTEX_CONNECTION_CHECK=0. This will assume XeLinks across devices [repeated 168x across cluster]
(WrapperWithLoadBit pid=4211) /usr/lib/python3.11/multiprocessing/resource_tracker.py:254: UserWarning: resource_tracker: There appear to be 1 leaked shared_memory objects to clean up at shutdown
(WrapperWithLoadBit pid=4211)   warnings.warn('resource_tracker: There appear to be %d '
(raylet) A worker died or was killed while executing a task by an unexpected system error. To troubleshoot the problem, check the logs for the dead worker. RayTask ID: ffffffffffffffffb4b97d156cb581f7dbb82f2701000000 Worker ID: 3604d35e3933d71bde300919a86052b60242e5e8b0941e93374b84dc Node ID: 5c6f23e2660bea6d8af3fd5fd8ab94aa9233ae8d1bbfa29dfe86f788 Worker IP address: <IP_ADDRESS> Worker port: 38205 Worker PID: 4211 Worker exit type: SYSTEM_ERROR Worker exit detail: Worker unexpectedly exits with a connection error code 2. End of file. There are some potential root causes. (1) The process is killed by SIGKILL by OOM killer due to high memory usage. (2) ray stop --force is called. (3) The worker is crashed unexpectedly due to SIGSEGV or other unexpected errors.
Process Process-65:
Traceback (most recent call last):
File "/usr/lib/python3.11/multiprocessing/process.py", line 314, in _bootstrap
self.run()
File "/usr/lib/python3.11/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/usr/local/lib/python3.11/dist-packages/ipex_llm/vllm/xpu/entrypoints/openai/rpc/server.py", line 220, in run_rpc_server
server = AsyncEngineRPCServer(async_engine_args, usage_context, port, load_in_low_bit)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/ipex_llm/vllm/xpu/entrypoints/openai/rpc/server.py", line 27, in init
self.engine = AsyncLLMEngine.from_engine_args(async_engine_args,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/ipex_llm/vllm/xpu/engine/engine.py", line 43, in from_engine_args
return super().from_engine_args(engine_args, start_engine_loop, usage_context, stat_loggers)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/engine/async_llm_engine.py", line 476, in from_engine_args
engine = cls(
^^^^
File "/usr/local/lib/python3.11/dist-packages/ipex_llm/vllm/xpu/engine/engine.py", line 29, in init
super().init(*args, **kwargs)
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/engine/async_llm_engine.py", line 381, in init
self.engine = self._init_engine(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/engine/async_llm_engine.py", line 557, in _init_engine
return engine_class(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/engine/llm_engine.py", line 270, in init
self._initialize_kv_caches()
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/engine/llm_engine.py", line 369, in _initialize_kv_caches
self.model_executor.determine_num_available_blocks())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/executor/distributed_gpu_executor.py", line 38, in determine_num_available_blocks
num_blocks = self._run_workers("determine_num_available_blocks", )
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/executor/ray_gpu_executor.py", line 481, in _run_workers
ray_worker_outputs = ray.get(ray_worker_outputs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/ray/_private/auto_init_hook.py", line 21, in auto_init_wrapper
return fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/ray/_private/client_mode_hook.py", line 103, in wrapper
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/ray/_private/worker.py", line 2661, in get
values, debugger_breakpoint = worker.get_objects(object_refs, timeout=timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/ray/_private/worker.py", line 873, in get_objects
raise value
ray.exceptions.ActorDiedError: The actor died unexpectedly before finishing this task.
class_name: get_ipex_llm_wrapper..WrapperWithLoadBit
actor_id: b4b97d156cb581f7dbb82f2701000000
pid: 4211
namespace: ac18545b-bc5c-4a95-a517-cfa1e1af06de
ip: <IP_ADDRESS>
The actor is dead because its worker process has died. Worker exit type: SYSTEM_ERROR Worker exit detail: Worker unexpectedly exits with a connection error code 2. End of file. There are some potential root causes. (1) The process is killed by SIGKILL by OOM killer due to high memory usage. (2) ray stop --force is called. (3) The worker is crashed unexpectedly due to SIGSEGV or other unexpected errors.
/usr/lib/python3.11/multiprocessing/resource_tracker.py:254: UserWarning: resource_tracker: There appear to be 1 leaked shared_memory objects to clean up at shutdown
warnings.warn('resource_tracker: There appear to be %d '

2024:09:13-11:21:50:(31157) |CCL_ERROR| exchange_utils.cpp:202 sendmsg_fd: condition !check_msg_retval("sendmsg", send_bytes, iov, msg, sizeof(u.cntr_buf), sock, fd) failed
errno: Broken pipe
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386] Error executing method init_device. This might cause deadlock in distributed execution.
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386] Traceback (most recent call last):
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386] File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/worker_base.py", line 378, in execute_method
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386] return executor(*args, **kwargs)
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386] ^^^^^^^^^^^^^^^^^^^^^^^^^
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386] File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/xpu_worker.py", line 105, in init_device
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386] self.init_worker_distributed_environment()
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386] File "/usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/xpu_worker.py", line 205, in init_worker_distributed_environment
(WrapperWithLoadBit pid=35347) ERROR 09-13 11:21:50 worker_base.py:386] get_pp_group().all_reduce(torch.zeros(1).xpu())

The first issue could be solved by this modification:
vi /usr/local/lib/python3.11/dist-packages/vllm-0.5.4+xpu-py3.11-linux-x86_64.egg/vllm/worker/xpu_worker.py
            get_pp_group().all_gather(torch.zeros(1).xpu())
            #get_pp_group().all_reduce(torch.zeros(1).xpu())

(WrapperWithLoadBit pid=4874) 2024:09:14-11:01:33:( 5291) |CCL_WARN| no membind support for NUMA node 1, skip thread membind [repeated 6x across cluster]
(WrapperWithLoadBit pid=3548) 2024:09:14-11:02:35:( 3548) |CCL_WARN| topology recognition shows PCIe connection between devices. If this is not correct, you can disable topology recognition, with CCL_TOPO_FABRIC_VERTEX_CONNECTION_CHECK=0. This will assume XeLinks across devices [repeated 392x across cluster]
(WrapperWithLoadBit pid=4211) -----> current rank: 0, world size: 4, byte_count: 33554432 [repeated 3x across cluster]
(WrapperWithLoadBit pid=4211) 2024:09:14-11:02:42:( 4211) |CCL_WARN| topology recognition shows PCIe connection between devices. If this is not correct, you can disable topology recognition, with CCL_TOPO_FABRIC_VERTEX_CONNECTION_CHECK=0. This will assume XeLinks across devices [repeated 168x across cluster]
(WrapperWithLoadBit pid=4211) GPU-Xeon4410Y-ARC770:rank4: Assertion failure at psm3/ptl_am/ptl.c:196: nbytes == req->req_data.recv_msglen

We were unable to reproduce the second issue in our environment. It may be related to settings in the startup container script.

fixed


fix(DevGenerator): The variable 'changesVar' is assigned but its value is never used

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

Closes #8940

You can test this PR using the following package version. 11.0.999-cibuild0023780-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0023785-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]


Add support for Pico4Button2Group

Tested working on my homebridge instance.

🥰😍🤩👏🏼👍🤘🏼🤌🤙🏼
I won’t be able to merge this until Tuesday but thank you!


Backport of 2765 in stable-3.0

Backport of #2765 in stable-3.0

jenkins test pipeline

jenkins test pipeline


Revert "python3: resolve ncursesw host contamination"

This reverts commit ce8c3dc8f5a0675a7e881c920e2e66d9a57a9cd1.
Because same patch has been included in meta-debian.

Thanks!


Finer control over dependencies

As long as I use composer, I have to include ALL services if I only want to access a single service.
This is a MASSIVE overkill.
Why don't you create composer deps/packages for each service and maybe a target to include all services for backward compat?
It really sucks to add thousands (5097 !!) of files for a super simple API query.

This is seriously an embarrassing reality of this repository. Google libraries are usually pretty terrible, tho, so it's not super surprising.

Thank you for voicing your opinions here. I fully agree.
Because Composer requires a repository per package, we'd have to maintain 140+ repositories to allow for each service to be used individually. This is actually not a big deal IMHO, it could be automated and would be well worth the investment ford what we'd gain in usability. But the extra overhead and is why this hasn't been done yet.

@bshaffer you could also look into subtree splits. Considering the number of repositories, it may prove unwieldy, but that way you get a repository per package, but you only have to maintain the main monolithic repo. Laravel does this where the main package is laravel/framework but they have a bunch of subsplits for the various Illuminate subdirectories (https://github.com/illuminate/http for example).
You can see how they used to do this here:
https://github.com/laravel/framework/blob/5.1/build/illuminate-split.sh
And a post about how it is done here:
https://www.tomasvotruba.cz/blog/2017/01/31/how-monolithic-repository-in-open-source-saved-my-laziness/
Sorry for the snarky comment above, but in my experience complaining about things to Google is about as effective as shouting at a hurricane. If you guys don't mind simply having an extra 150 repositories, the extra build legwork by you guys could save everyone who uses this repository roughly ~15-30 seconds per composer update (depending on machine specs).

More information here about subsplit: https://github.com/dflydev/git-subsplit

Would really like to see an update on this.
My composer has to download 7000+ files just for this code here:
// verify validity of token
$client = new Google_Client(array_merge(['jwt' => $jwt], $config));
$payload = $client->verifyIdToken($request->getData('id_token'));
if(!$payload)
    return false;

This is quite silly and a MASSIVE overkill just like OP wrote.

Full agree with janhartigan

the google api lib is too large , about 16.8M but i just wanna use the simple function
the composer update waste much of my time.  Here is China, it`s not ~15-30 seconds per composer update, It waste too many minutes per composer update

Thanks everybody for your input. We are moving newer libraries in this direction as seen in the GCP libraries
Since it is not a change we are going to make to this repo, I am closing this issue.


iOS. Implement ExpireAfterAccessCache

ExpireAfterAccessCache.native.kt:

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


[editor] A couple of small FreeText-related fixes (PR 14976 follow-up)

Ensure that the modified-warning won't be displayed, when navigating away from the viewer, if the user has added custom Annotations and then removed all of them.
Ensure that the initial editor-buttons state, i.e. the toggled-class, is correctly displayed in the toolbar when then viewer loads.
Tweak the CSS-classes for the editor-buttons, such that they use the correct focus/hover-rules (similar to the sidebar-buttons).
Remove a no longer accurate comment from the BaseViewer.annotationEditorMode-setter.
Address a couple of smaller outstanding review comments, including some re-formatting changes, from PR #14976.

/botio integrationtest


Takon changes

Currently rare (1/4500 from COX) to get and gives smithing boost to make items into bars, but has no effect on smelting bars.
It can be said that Dwarven gauntlets are an option for smelting, but like cooking, where you can have Remy or gauntlets for cooking, you don't have that choice for smelting between gauntlets and takon.
Smelting is the common way people get smithing xp and should be added to takon, considering the rarity.
Just seems weird for a pet so rare to get half a skill it's intended for - smithing items but not smelting ores.

Bump

if this is still something you want to suggest a run a poll here https://discord.com/channels/342983479501389826/1032668754561224734


issue #87: supporting ptr type for structs

Added support for reflect.Ptr in Send Method.
See issue #87

LGTM thank you


Add data folder based on cookiecutter-data-science

Hi,
I added a data folder and sub-folders based on http://drivendata.github.io/cookiecutter-data-science/#directory-structure.
I have a split opinion on this one. I think most of the time the data should stay on the cloud infrastructure. However, there are projects where this is not possible ... .
I thought about making it an option but I think it is easier to just delete the folder if it is not needed.

I like having a data folder and at the same time having it excluded in .gitignore, so folks don't accidentally push files from there (unless they use git lfs, but whoever knows about git lfs probably knows their way around gitignore anyways ^^). I'm not sure about the subfolders, personally I never used a structure like this. Maybe just have the data folder and .gitkeep inside?

@klamann I have similar feelings because I've mostly used Cloud Storage for all my projects. I like the compromise of only having a data folder without sub-folders and updated accordingly

Hey @SimonCW, I‘m on board with adding a data folder to the template. Two questions though:

Do we want to add some context on the purpose of the folder to the readme (of this repo, not the one we create via the template)? I.e. a pointer to Cookiecutter DS and a hint that we suggest using cloud storage accessible to the whole team if possible?
Will the .gitkeep file remain in the folder that is created by Cookiecutter? I feel that this might be confusing for users not familiar with the concept or how this template works, especially since the data folder is in .gitignore (rightfully so).

@sbunzel,

I would say no, the folder name should be self-explanatory
Yep, will remain. There is no way around that and I think everyone should be able to understand it from the file name or google in 30 seconds ;)

I think this is fine to merge, what are you waiting for?

@sbunzel,

I would say no, the folder name should be self-explanatory
Yep, will remain. There is no way around that and I think anyone should be able to understand it from the file name or google in 30 seconds ;)

@SimonCW, sorry for the late reply :-)

Okay
I find it confusing that the template creates a data folder which is listed in .gitignore (rightfully so), but contains a .gitkeep file. That doesn't make sense to me. I get why we need it to create the data folder in the first place, but I think we should clean it up in our post_gen_project hooks.

I agree, the method right now doesn't work as intended, because all contents under data are ignored, even the .gitkeep file. So when you apply the template, you will have the data folder, but everyone else who clones the git repo won't.
Here's what we should do: ignore the contents of data and add an exception to .gitignore for data/.gitkeep, as explained in this article.


TypeScript diagnostics error with jest builder v7.4.1

Describe the bug
After upgrade to v7.4.1 of the jest builder and using<EMAIL_ADDRESS>I get this error from jest:
TypeScript diagnostics (customize using [jest-config].globals.ts-jest.diagnostics option):     error TS6053: File 'src/test.ts' not found.
Also the jest typing were gone but I've fixed that by manually installing @types/jest
To Reproduce
Steps to reproduce the behavior:

npm i @angular-builders/jest on an existing project

Expected behavior
no configuration or typescript related errors
Builder:

jest
7.4.1

Thanks for the report. Would you mind providing a repo with a minimal reproduction?

yes, I will try

I'm not able to reproduce this with a new repo but found that the problem is having:
  "files": [     "test.ts",     "polyfills.ts"   ],
in tsconfig.spec.json where test.ts is removed. but with the new repo - same tsconfig.spec.json with the missing file the error is not shown. I also need to add @types/jest in the existing project but it works without it in the new repo.
so I guess I've misconfigured something or am in a dependency hell

So it's not a bug, it is an expected error. You're getting this error because you have test.ts in files (which tells TS compile to compile this file) but this file doesn't exist.
The real problem here is that it's mentioned in docs that you should remove the file but it's not mentioned that you have to remove it from files array.
Ideally all these steps should be done with schematics (automatically when you install @angular-builders/jest) but unfortunately I'm just not getting to it.
But yes, it should at least appear in the README. Want to create a PR for this?

yes, I'd like to. but I still don't understand why it is working for a new project and the test.ts is still in the files array

Did you remove the actual file in the new project?

yes

That's interesting. Unfortunately without the reproduction I can't figure out the problem. Any chance you can start with your repo and make a reproduction from it? Just leave the necessary pieces and remove the rest so I could take a look?

I think I found the cause for this. I didn't notice this before:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
after manually installing the dependency it works as expected

If you had to manually install the dependency it probably means that you're on outdated version of Angular, I'd check it.
The issue can be closed?

I'm on 6.1.10. yes, I think it can be closed


METRON-896: Document Having Kerberos Issue Renewable Tickets

Contributor Comments
Added a couple lines to the doc about setting up tickets as renewable, if they aren't already.
See: https://web.mit.edu/kerberos/krb5-1.12/doc/admin/conf_files/kdc_conf.html, specifically max_renewable_life may have to be set to a nonzero value.  Interestingly, full dev doesn't care, but an actual (non-AWS) cluster did care.  I'm guessing this is related to some version or OS differences or something, but I'm not entirely sure.
Also added a couple lines to both manual and full dev docs about how to verify a ticket is renewable, and how to modify the principals to add the appropriate flags if needed.
Given that it's potentially a versioning type thing, and the solutions are Kerberos specific issues, I don't know how much of a test plan we need/want to repeat it. We're giving KDC instructions as a convenience, not supporting the KDC itself.  To me, this feels like a best-effort type attempt to address issues.  If we feel that way as a group, I'd be interested in if anyone wants to modify or update the READMEs to reflect that a bit better.  Otherwise, coming up with a test plan may be a pain, because we'd have to track down the actual root versioning cause.
I've also included a formatting fix to the docs from while I was in the area.  The newline didn't show up properly in triple backticks in the maven site output.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[ ] Have you included steps to reproduce the behavior or problem that is being changed or addressed?
See comments above.  I'm personally inclined to consider this a best effort attempt to provide a solution to a KDC configuration issue.
[ ] Have you included steps or a guide to how the change may be verified and tested manually?
See comments above.  I'm personally inclined to consider this a best effort attempt to provide a solution to a KDC configuration issue.
[x] Have you ensured that the full suite of tests and checks have been executed in the root incubating-metron folder via:mvn -q clean integration-test install && build_utils/verify_licenses.sh

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
bin/generate-md.sh
mvn site:site

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

Oops.  I thought you had wanted me to take this.  I already created METRON-895.  Please at least grab the diagnostic log information that I have added to METRON-895 and add to your METRON-896 so that users can identify when this is an issue for them.

@nickwallen My bad, apparently I didn't refresh Jira and didn't see the ticket.  I'll migrate the info over, and add the relevant snippet to the docs.

Do you have a preference which ticket we close as a dupe?  I can pretty easily rename my PR if we want to use yours.

No preference as long as it has the log output.  Please close whatever one is the dup.  Thanks for doc'ing this.  Nice job figuring this one out too!

Why do we have 2 separate kerberos docs at this point?  Can we get rid of the vagrant one or is there a difference there?

Imo, the vagrant one should be moved up to the level of the manual one, and just made to be the Ambari Kerberos doc with any notes for full dev.
Combining them is kind of a pain in the butt, since there's the whole giant set of manual steps that aren't relevant to anything Ambari.  It's just annoying to deal with because a couple of steps are similar but not quite the same, etc.
If we want to go ahead and roll that change into this, I can go ahead and do that.

@cestella As a note, it looks like there's a regression in the docs (the vagrant install should be much, much shorter and limited to Ambari), so that needs to be cleaned up.

To elaborate on the regression comment:
The vagrant Kerberos steps have all the manual steps added back in.  They should largely be removed, barring any profiler ACL setup.
The manual Kerberos setup is fine (or should be), and can pretty much be left as-is.
Like I said above, IMO we move the Ambari Kerberos to the same level and just make any notes regarding the dev environments specifically.

Looks like https://github.com/apache/incubator-metron/pull/554 cleans up a lot of things. I'll wait for that to go in, then I'll adjust this PR and we'll revisit it.

Updated after merging in master, which included the README fixes as well as moving the Ambari instructions alongside the Manual instructions.

+1 Looks good.  Thanks!


Add jyotiman

Adding two more Open Source Project names

@Zyo86  contribute here https://github.com/Ishaan28malik/Get-Dev-Resources


Problem with building URLs with Areas in .NET Core 2.1

From @piecho1991 on July 17, 2018 13:48
I have problem with URL-s in ASP.NET Core 2.1 Web Application.
I have used code like below:
nasihdfgasih

and Razor is generating wrong URL not like http://example.com/Area/Controller/List but http://example.com/Controller/List?area=Area.
My routes configuration:
app.UseMvc(routes =>
{
	routes.MapRoute(
		name: "default",
		template: "{controller=Home}/{action=Index}/{id?}"
	);

	routes.MapRoute(
		name: "areas",
		template: "{area:exists}/{controller=Home}/{action=Index}/{id?}"
	);
});

Copied from original issue: dotnet/core#1796

@piecho1991 You need to reorder the routes in your configuration. In general, routes with more number of segments (in your case 4 vs. 3) should be before the one with less number of segments

Thanks for contacting us. We believe that the question you've raised have been answered. If you still feel a need to continue the discussion, feel free to reopen it and add your comments.

Hi, I believe I am experiencing the same issue.
My routes:
app.UseMvc(routes =>
{
	routes.MapRoute(
	name: "areaRoute",
	template: "{area:exists}/{controller=Home}/{action=Index}/{id?}");

	routes.MapRoute(
	name: "default",
	template: "{controller=Home}/{action=Index}/{id?}");
});

From what I can tell this issue is related to having Identity being implemented within the project. To test this I created a new application with no authentication and areas/routes work great no problems.
Creating a new project with individual user accounts being added as the authentication results in the routes no longer operating correctly. The result being a URL that looks like this - https://localhost:44396/Admin?area=Admin

Even i am f

Hi, I believe I am experiencing the same issue.
My routes:
app.UseMvc(routes =>
{
	routes.MapRoute(
	name: "areaRoute",
	template: "{area:exists}/{controller=Home}/{action=Index}/{id?}");

	routes.MapRoute(
	name: "default",
	template: "{controller=Home}/{action=Index}/{id?}");
});

From what I can tell this issue is related to having Identity being implemented within the project. To test this I created a new application with no authentication and areas/routes work great no problems.
Creating a new project with individual user accounts being added as the authentication results in the routes no longer operating correctly. The result being a URL that looks like this - https://localhost:44396/Admin?area=Admin

Even i am facing exactly same issue, on a sample application url works fine, but as son as I add authentication its breaking, unable to figure out whats going wrong. Just stuck up in our migration to .net core process.

Cshtml code

html rendered code

Routes:
app.UseMvc(routes =>
{
routes.MapRoute(
"Bio_default",
"Bio/{controller}/{action}/{id?}",
new { controller = "Story", action = "Index" }
);
routes.MapRoute(
"default_route",
"{controller}/{action}/{id?}",
new { controller = "Home", action = "Index" }
);
});
Even changing the area route to
routes.MapRoute(
"Bio_default",
"{area:exists}/{controller}/{action}/{id?}",
new { controller = "Story", action = "Index" }
);
isn't changing the behavior. Can someone suggest what could be wrong here. I am banging my head right now. :(

Hi @neesinch,
I had given up on looking for a fix for this. I had a quick look there there this morning and found some documention for core 2.1 - https://docs.microsoft.com/en-us/aspnet/core/mvc/controllers/areas?view=aspnetcore-2.1
It looks like you're meant to mark the areas controllers with an area attribte and provide the area name. See my example below. "Admin" is the name of my area. So I have;

Areas

Admin

Controllers
Views

    [Area("Admin")]
    public class AdminPanelController : Controller
    {
        public IActionResult Index()
        {
            return View();
        }
    }

I then setup my routes  like so;
            app.UseMvc(routes => {
                routes.MapRoute(
                    name: "areaRoute",
                    template: "{area:exists}/{controller=Home}/{action=Index}/{id?}");

                routes.MapRoute(
                    name: "default",
                    template: "{controller=Home}/{action=Index}/{id?}");
            });

Keep in mind that the area route defination has to come first. Then is is what my link off the area looks like

Admin Panel

I would suspect that your  would also work.

Did you add the Area attribute to HomeController
namespace CarDealerNG.Areas.Admin.Controllers {     [Area("Admin")]     public class HomeController : Controller     {         public IActionResult Index()         {             return View();         }     } }
Startup.cs file
` app.UseMvc(routes =>
{
routes.MapRoute(
name: "default",
template: "{controller}/{action=Index}/{id?}");
            routes.MapRoute(
                name: "areaRoute",
                template: "{area:exists}/{controller=Home}/{action=Index}/{id?}");
        });`

Hi, it looks like you are posting on a closed issue/PR/commit!
We're very likely to lose track of your bug/feedback/question unless you:

Open a new issue
Explain very clearly what you need help with
If you think you have found a bug, include detailed repro steps so that we can investigate the problem

Thanks!