[Cosmos] Adds full text policy and full text indexes

This PR adds the functionality, samples and tests for creating and replacing containers with full text policies and full text indexes for the SDK.
Currently missing:
[ ] - updating samples once we have way to test
[ ] - updating tests once we have way to test

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-cosmos


boards: st: introduce new stm32f413 disco kit

Add the stm32f413h_disco target to the boards/st
Add the PLL I2S if the clock 48MHz is required as a source clock by the SDMMC or USB or RNG
this PLLI2S is of compatible = "st,stm32f412-plli2s-clock";  introduced by the #82259
/* Enable PLL I2S to Deliver 48MHz clock from HS Clock */
&plli2s {
	div-m = <4>;
	mul-n = <96>;
	div-q = <4>;
	div-r = <2>;
	clocks = <&clk_hse>;
	status = "okay";
};

https://www.st.com/en/evaluation-tools/32f413hdiscovery.html

@FRASTM please check the CI failures

rebase on 7c4abb1eb9fddadc469318f7bf4f0d4d573d3726 (CI error fixed)

with new image and new 1 commit

with new image and new 1 commit

I'm not sure what's going on but can't you just use: https://www.mouser.fr/images/marketingid/2017/img/128173244_STMicroelectronics_32F413HDISCOVERYDiscoveryKit.png?v=070223.0256 ? The image you have in your latest commit appears to be webp, sure, but without a transparent background as if you had converted your jpg image or something?

that's the case : the webp image I put, was processed by https://tinypng.com/    but  it does not makes the background transparent. Does it really make a difference ?
I'd really prefer to have the webp format of this one :

with new image and new 1 commit

I'm not sure what's going on but can't you just use: mouser.fr/images/marketingid/2017/img/128173244_STMicroelectronics_32F413HDISCOVERYDiscoveryKit.png?v=070223.0256 ? The image you have in your latest commit appears to be webp, sure, but without a transparent background as if you had converted your jpg image or something?

that's the case : the webp image I put, was processed by tinypng.com but it seems it does not have the transparent background (I do not know exactly the command to obtain that effect) . Does it really make a difference ? I'd really prefer to have the webp format of this one :

but why don't you want to use the one I linked to? It falls under fair-use, if that's your concern.
The image with the mbed logo is really not an option IMO, for just so many reasons, including the fact that we're Zephyr and that Mbed is EOL :)

taking the recommended image

taking the recommended image

Thanks! https://builds.zephyrproject.io/zephyr/pr/82275/docs/boards/st/stm32f413h_disco/doc/index.html :)

@FRASTM sample.bluetooth.peripheral_hr.frdm_kw41z_shield build failure in CI
west build -p -b stm32f413h_disco/stm32f413xx samples/bluetooth/peripheral_hr -T sample.bluetooth.peripheral_hr.frdm_kw41z_shield

rebase on main will fix the issue


Ground truth binvox

Hi,
Thank you for sharing codes.
I wonder how you generate ground truth voxels.
I would like to run this code in another class of the ShapeNet dataset.
I have used binvox to generate a 64^3 voxel model from ShapeNet v2, but it does not match the model you are providing.
Specifically, the following commands were executed.
binvox model_normalized.obj -d 64 -cb
If there is no problem with the command, it is because of the version of binvox or my environment. So I won't worry about this anymore.
If you know of a better way, please let me know.

Hi, I think your command looks good. I remember we used a similar way to generate the voxelized shapes. What do you mean by "does not match"? Maybe some of our categories are not centralized, whereas I think these differences in scale or alignment do not affect the results too much because the primitives are distributed evenly in the voxel space.
Note in this implementation you also need a low-resolution voxel in 16^3 for Prim-Agent for better efficiency and abstraction.

Hi,

What do you mean by "does not match"?
It means that the voxel data of the model you provide is different from the model obtained by the above command. The models look similar, so if scale and alignment don't affect the results, it doesn't matter.

Thank you.


After module flash, does not boot

Hi!
I am using the OnePlus 7T with latest Oxygen OS 11 available for my device.
Bootloader of course unlocked, Magisk 24.3 w/Zygisk, flashing Pixelify 2.01 makes the phone frozen at the boot animation when eventually it goes into TWRP, saying "Android Rescue Party" or something.
When I remove it from /data/adb/modules, phone boots.
Thanks for your help,
Oskar.
(its @onn_net on telegram)

+1
I'm facing the same issue on Oneplus 7T

I'm on OnePlus 7 Pro... flashed this yesterday.  Similar thing as above 2 ppl, except the phone will boot to the unlock screen, and then immediately go into a continuous bootloop.  I saw a super brief message popup saying "Google Play Services has stopped", but the phone bootloops before I can go into Settings and clear the Storage and Data for Google Play Services (I am not sure if this was required for me to do before initial reboot after Pixelify install or not).  I was trying to follow this Guide/FAQs:
https://telegra.ph/Pixelify-Troubleshooting-and-FAQ-05-08
I had to use Magisk Manager for Recovery (in TWRP) and uninstall the Pixelify module for the phone to boot normally.
Oxygen OS 11
Magisk 24.3 with Zygisk enabled
Flashed Pixelify v2.02

Hi guys, I ran into the same problem and reverted back to pixelify 2.0

Can anyone send me Bootlogs? So that i can check whats wrong.

Does it works on v2.1?

Can confirm same issue on OnePlus 7 Pro OxygenOS <IP_ADDRESS> with latest Magisk and v2.1 version.

Can anyone send me Bootlogs? So that i can check whats wrong.

Could you tell me how to do that? I could give it a try.

I have the same issue with v2.1 on my OnePlus 7T Pro OxygenOS 11 with Magisk/Zygisk and after the second reboot (because the first one was aborted by the bootloop saver and restarted my phone without Pixelify) I can't find the bootlogs under /sdcard/Pixelify/. With version 2.02, my phone boots into fastbootd after the failed restart


[BUG] Unwanted uppercase conversion in staging macro

Describe the bug
When columns from the source model and/or derived columns have mixed casing the hashed_columns and columns_to_select CTEs are incorrect as they update all column names to uppercase.
Versions
dbt: 1.1.0
dbtvault: 0.8.3
To Reproduce
Steps to reproduce the behavior:

Have a source model with pascal/camel case column names,
Add a derived column with  pascal/camel case for example '"CreatedOnDateGMT"'
have a Hash Diff column where is_hashdiff: true
When the model builds the source_data and derived_columns CTEs are using the correct casing.  The CONCAT_WS for the Hash is using the correct Casing.  Only the column names being selected in the hashed_columns and columns_to_select are incorrect.

Expected behavior
The column names should not be changed
Screenshots

Thanks for your report. What database platform are you on please?

Snowflake.

Thanks, will add this to the backlog for the next update!

Fix released in v0.9.0. Let us know if you continue to have issues. Thanks!

We're still seeing an error when implementing the staging macro with lowercase letters in the source columns.  The column lists being generated for the CTEs and final selects are all mapped to upper case in the stage macro and the process_columns_to_select is also  casting all the columns to upper case.
stage macro:
...
{%- set derived_column_names = derived_column_names | map('upper')   | list -%}
{%- set null_column_names = null_column_names | map('upper') | list -%}
{%- set hashed_column_names = hashed_column_names | map('upper') | list -%}
{%- set ranked_column_names = ranked_column_names | map('upper') | list -%}
{%- set exclude_column_names = exclude_column_names | map('upper') | list -%}
{%- set source_and_derived_column_names = source_and_derived_column_names | map('upper') | unique | list -%}

process_columns_to_select:
{%- macro process_columns_to_select(columns_list=none, exclude_columns_list=none) -%}

    {% set columns_list = columns_list | **map('upper')** | list %}
    {% set exclude_columns_list = exclude_columns_list | map('upper') | list %}

    {% set columns_to_select = [] %}

    {% if not dbtvault.is_list(columns_list) or not dbtvault.is_list(exclude_columns_list)  %}

        {{- exceptions.raise_compiler_error("One or both arguments are not of list type.") -}}

    {%- endif -%}

    {%- if dbtvault.is_something(columns_list) and dbtvault.is_something(exclude_columns_list) -%}

        {%- for col in columns_list -%}

            {%- if col not in exclude_columns_list -%}
                {%- do columns_to_select.append(col) -%}
            {%- endif -%}

        {%- endfor -%}

    {%- endif -%}

    {%- do return(columns_to_select) -%}

{%- endmacro -%}


(PDB-2407) PQL- Allow inequalities on date fields

This patch allows inequality operators (>,>=,<,<=) to be used on date
fields similar to how they are allowed in the AST language. There is
currently no validation to ensure correct format of the date
strings (similar to AST).

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/550/
Test PASSed.


Some samples aren't found in API docs

I wrote a horribly inefficient script to find all samples that aren't mentioned in /packages.
font_feature.font_feature_lining_figures.0.dart
font_feature.font_feature_historical_forms.0.dart
font_feature.font_feature_contextual_alternates.0.dart
font_feature.font_feature_fractions.0.dart
font_feature.font_feature_oldstyle_figures.0.dart
font_feature.font_feature_alternative.0.dart
font_feature.font_feature_proportional_figures.0.dart
font_feature.font_feature_locale_aware.0.dart
font_feature.font_feature_subscripts.0.dart
font_feature.font_feature_notational_forms.0.dart
font_feature.font_feature_slashed_zero.0.dart
font_feature.font_feature_stylistic_alternates.0.dart
font_feature.font_feature_swash.0.dart
font_feature.font_feature_scientific_inferiors.0.dart
font_feature.0.dart
font_feature.font_feature_superscripts.0.dart
font_feature.font_feature_denominator.0.dart
font_feature.font_feature_case_sensitive_forms.0.dart
font_feature.font_feature_alternative_fractions.0.dart
font_feature.font_feature_stylistic_set.0.dart
font_feature.font_feature_ordinal_forms.0.dart
font_feature.font_feature_historical_ligatures.0.dart
font_feature.font_feature_tabular_figures.0.dart
font_feature.font_feature_character_variant.0.dart
font_feature.font_feature_numerators.0.dart
font_feature.font_feature_stylistic_set.1.dart
linear_border.0.dart
action_icon_theme.0.dart
text_field.2.dart
search_anchor.4.dart
search_anchor.3.dart
switch.3.dart
snack_bar.2.dart
scaffold_state.show_snack_bar.0.dart
overflowbox.0.dart

These should be added to relevant API docs, e.g.
/// {@tool dartpad}
/// This example shows how to detect if the user has selected the logical "Q"
/// key and handle the key if they have.
///
/// ** See code in examples/api/lib/services/keyboard_key/logical_keyboard_key.0.dart **
/// {@end-tool}

Can we use the script as a presubmit check to make sure that we don't have unreferenced samples?

I deleted it but I used an AI query like "given a file containing a list of strings and a directory to search recursively, give me the subset of strings that were not found in the contents of that directory" to get a bash script
and the following to get the list of examples:
find /Users/plg/Developer/flutter-dev/examples/api/lib -name "*.dart" -type f -exec basename {} \; > examples.txt

Some of these actually seem to be referenced from the engine repo, example https://github.com/flutter/engine/blob/16e2ab7e986c8c7ad2a704245df48ca96ea90948/lib/ui/text.dart#L454
But nevertheless some kind of check to ensure that all files from examples/api are used somewhere would be great to have...
/cc @gspencergoog

If we do a check, we could add a search in bin/cache/pkg/sky_engine/lib as well as in the framework, which should find any of the engine references.


VMR test failure in RC2 branch: VerifyVersionFile

The test is failing with unexpected content in the generated .version file for the source-built artifacts:
Expected: 8.0.100
Actual:   8.0.100-rtm.23470.1

The expected value comes from the MicrosoftSourceBuildIntermediateInstallerVersion property from the generated PackageVersions.package-source-build.Current.props file. But I don't know where it gets this value from when generating that props file.

The branch that this failure was occurring on was suspect and not up-to-date. After updating the branch to latest, things are passing now.


Add dedicated with* options methods in favour over withOptions

Implements / Closes #154

@clue updated it to the latest comments.


Template preprocessor missing after recent refactoring

A function regression occurred when the recent YAML processing was refactored.
Specifically, the template processor was left out of certain call paths for yaml loading.
This would have allowed TEMPLATE(...) and <<...>> forms to remain unprocessed.

fixed in latest release


Didn't work in Google Colab.

I tried lootdl in Google colab and it didn't work.  It appears to not be configured as a proper python3 package.
Here's a fully functional link to the colab notebook attempting to load a file from a google drive.
https://colab.research.google.com/drive/1xWX4L_lw-YAIBLfV29vmvL5bFXzWhkf3?usp=sharing

I'm not fully sure of the issue since I use it with Python running locally on my PC and have never used Google Colab. Make sure to import it and install all requirements. I'll investigate the issue.

In colab import like this:
`%cd /content
!git clone https://github.com/jesusyanez/cdl.git
%cd cdl
!pip install patool
sys.path.insert(0,'/content/cdl')`
and example usage:
`import cdl
import string
url = ""  # @param {type:"string"}
Out = "Downloads" #@param {type:"string"}
%cd /content/
%mkdir "$Out"
if url != "":
%cd "$Out"
cdl.grab(url, './')
else:
print("Empty url")`


plume: Use the public bucket proxy for anonymous access

The image download from the bucket is not possible anymore directly but
needs to be done through the HTTP proxy.
Create a limited bucket object for anonymous access, which can only
download particular files and has no listing or	upload ability.
Calling code needs to make sure it only tries uploads or directory
listings when the bucket object is using a proper gs:// URL and that
it configured credentials before trying to upload.
How to use
Testing done
bin/plume pre-release --gce-json-key none --aws-credentials /dev/null --platform aws -d --version 2983.2.0 --channel stable -P china

Thanks, done


How to run a command from reconcile inside of a pod/container?

Type of question
Usage
Question
What did you do?
Getting a pod and trying to kubectl exec by using the client libs available.
What did you expect to see?
Do something as :
	cmd := []string{
		"/bin/sh",
		"-c",
		"pg_dump mobile_security_service | gzip > mobile_security_service.gz",
	}

       command(cmd).Run()

API example:
/api/v1/namespaces/project-1/pods/pod-1-lmlzj/exec?command=/bin/bash&command=-c&command=/bin/bash&stdin=true&stderr=true&stdout=true&tty=true

@camilamacedo86 Can you explain a bit more, not sure I understand the reconcile part.

Why don't you use the k8s client to execute this command - see https://github.com/snowdrop/kreate/blob/78f0b5ee8e27117b78fe9d6d5192bc5b04c0e5db/pkg/k8s/client.go#L243 ? @camilamacedo86

hi @LiliC I want in the reconcile execute a command inside of the container like kubectl exec

I tried the following impl and it did not work as well. The restClient is nil.
// Get the config
	cfg, err := config.GetConfig()
	if err != nil {
		return reconcile.Result{}, err
	}

	// Get The Rest client for this config
	restClient, _ := rest.RESTClientFor(cfg);

	// Do the request
	req := restClient.Post().
		Namespace(pod.Namespace).
		Resource("pods").
		Name(pod.Name).
		SubResource("exec").
		VersionedParams(&corev1.PodExecOptions{
			Command: cmd,
		}, scheme.ParameterCodec)

	// Connect to url (constructed from req) using SPDY (HTTP/2) protocol which allows bidirectional streams.
	exec, err := remotecommand.NewSPDYExecutor(cfg, "POST", req.URL())
	if err != nil {
		reqLogger.Error(err, "cmd", cmd, "pod", pod.Name)
		return reconcile.Result{}, err
	}

	// initialize the transport of the standard shell streams
	err = exec.Stream(remotecommand.StreamOptions{})
	if err != nil {
		reqLogger.Error(err, "cmd", cmd, "pod", pod.Name)
		return reconcile.Result{}, err

	}

Could you help me here? How can I execute a command inside of the containers of the pods managed by the operator? PS.: I cannot add the command via args when the deployment is made for example. In my case, I would like to do a bkp of the database and move the file for another place.

@shawn-hurley @LiliC @cmoulliard any ideas?

I think you need to change some of the options of your impl to get it to work.
https://github.com/snowdrop/kreate/blob/78f0b5ee8e27117b78fe9d6d5192bc5b04c0e5db/pkg/k8s/client.go#L251
https://github.com/snowdrop/kreate/blob/78f0b5ee8e27117b78fe9d6d5192bc5b04c0e5db/pkg/k8s/client.go#L270

Hi @shawn-hurley,
Really tks. However, I am still with an issue before that. The following code will return null.
	// Get The Rest client for this config
	restClient, _ := rest.RESTClientFor(cfg);

PS.: The cfg is that one injects in the manager. Have you any idea to solve it?

some of the options of your impl to get it to work.

Such examples will work as the restclient is created outside of the k8s cluster, We need for the Camila use case, something like this but able to working within the cluster
https://gist.github.com/cmoulliard/ec4dac1275042643bab7f4ba2867604f#file-gistfile1-txt-L279

@camilamacedo86 if you want to do the request directly we do it like this:
https://github.com/operator-framework/operator-sdk/blob/c8ead552930d086056f779e8fdefa7f681c1e432/test/e2e/memcached_test.go#L792-L801
and to get the client we do:
https://github.com/operator-framework/operator-sdk/blob/c8ead552930d086056f779e8fdefa7f681c1e432/pkg/test/framework.go#L72-L79
You should be able to do direct requests then, haven't tried it myself.

Hi @LiliC I am not sure if it will attend the need as well.
Note that is required the kubeconfigPath. From inside of the cluster it is one path (when the operator been executed) and from outside of the cluster (when we run operator-sdk up local) is another path

@Marco shared: https://github.com/zalando/postgres-operator/blob/master/pkg/cluster/exec.go#L44

Guys, any ideas here ? Or we should just use kubeClient ?


[client] Include lucene.codecs services files in shadowJar

If the client is used with assertions enabled it will try to load the
PostingFormats. That failed because it couldn't locate them as the
META-INF/services files were missing.

ack


query plot suggests influence where there is none

q1 = Query(dag).do(a=0, c=1).given(d=1)
q1.plot()

maybe there should no longer be an arc between a and d.

New Chart looks like this.


Handle generic supertypes

This PR resolves #2382.
supertype_field and interfaces_field are empty if the parent uses generics. The method types.directSupertypes returns the parent and sets the generic type information properly.

Thanks

Including tests!


What type of update are you requesting?
Something else not listed
Current Package Identifier
Arm.GnuArmEmbeddedToolchain
Package Version
12.2.Rel1
Please describe the changes you would like to see
It looks like ARM has changed the way they package their toolchains and it is now called "Arm GNU Toolchain". This seems to replace the "GNU Arm Embedded Toolchain" which has not been updated since 2021.
Download page URL: https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads

Gday, just noting, the version currently on winget is officially deprecated.

Is the new software "Arm Gnu Toolchain" a direct replacement for "Arm Gnu Embedded Toolchain" or can they exist side by side on the same machine?


[DPO] Refactor eval logging of dpo trainer

Address part 1 of #952 by removing store_metrics and switching to more standard compute_metrics letting Trainer handle logging

Thanks for working on this! Just ping me whenever you would like to run the CI.

@lvwerra, I completed this part of the refactor, can you run the CI?
@kashif as part of this, I removed logging all the logits since it seemed a bit excessive to pass around the batch x seq_len x vocab size array and taking the mean didn't feel like a meaningful thing to log since we already have logps. Let me know if you'd like this reversed

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

@mnoukhov are you also logging sample outputs as well here?

@kashif I didn't change sample output logging in this PR, so it's still there. I was going to address the sample logging issue (2 in #952) in a second PR to keep things managable

so this PR LGTM! feed free to merge

@mnoukhov so folks really want the additional metrics to be logged during training which isn't possible at the moment, so lets revert this for now and continue this refactoring to figure that out.

I don't think this change prevents additional metrics from being logged. It feels like it actually makes it easier to log

Ok so let's try to add the previous behavior if possible... I couldn't figure it out at first glance... I think the trainer's training loop doesn't seem to have a way to do it... can you kindly confirm?

Basically what #1046 wants is to log metrics during training, which is not how Trainer usually works but it is a common ask e.g. https://discuss.huggingface.co/t/logging-training-accuracy-using-trainer-class/5524/3. The reverted code does not do this correctly.
AFAIK the problem with trying to put self.log into compute_loss is it doesn't really make sense whenever you use multi-gpu or gradient accumulation. In both cases you're calling compute_loss more than once per step and the previous code just logged the metrics for one subset of that batch (e.g. the last minibatch in gradient accumulation or one gpu's batch). @lewtun, is this right?
If you want metrics for the training set, I would recommend doing evaluate on the training set any time it is also done on the test set, using a callback.


Refine headless mode more

New enhancements:

[x] Don't print the prompt when in headless mode
[x] #26
[x] When in headless mode, send output to stderr by default
[x] #27
[x] When in headless mode, serialize output and errors to JSON

Done.


[fix] Threshold Rules search i18n error (#2692)

What's changed?
1、translate search content to stored content in web front end
2、back end parse search list，and build search condition
Checklist

[√]  I have read the Contributing Guide
[√ ]  I have written the necessary doc or comment.
[ ]  I have added the necessary unit tests and all cases have passed.

Add or update API

[ ] I have added the necessary e2e tests and all cases have passed.

this api  will be called every input, but the response will be same.  could we adjust this. load i18n content when the page init


The CommandAPI should use MinecraftServer#getCommands instead of MinecraftServer.vanillaCommandDispatcher

Description
As per this comment:

People using nms
Please move away from MinecraftServer.vanillaCommandDispatcher, instead, use MinecraftServer#getCommands().
This change supports the internal dispatcher being reloaded. We will need to figure out some api in order to properly support re-registering commands under some kind of lifecycle api.

Expected code
Replace the use of MINECRAFT_SERVER.vanillaCommandDispatcher in NMS implementations of NMS#getBrigadierDispatcher
https://github.com/JorelAli/CommandAPI/blob/2efd3a3ffdee797ab8b2a4b12784c9e5741d197a/commandapi-nms/commandapi-1.19.3/src/main/java/dev/jorel/commandapi/nms/NMS_1_19_3_R2.java#L395-L398
with MINECRAFT_SERVER.getCommands():
@Override
public final com.mojang.brigadier.CommandDispatcher<CommandSourceStack> getBrigadierDispatcher() {
    return MINECRAFT_SERVER.getCommands().getDispatcher();
}

Extra details
No response

I notice that comment is from a Paper PR. If this change was applied, would the CommandAPI still work on Spigot? If not, I suppose we would just need to migrate calls to getBrigadierDispatcher over to PaperImplementations.
Also, does this change apply to Paper right now, or only after that PR is merged?

I notice that comment is from a Paper PR. If this change was applied, would the CommandAPI still work on Spigot? If not, I suppose we would just need to migrate calls to getBrigadierDispatcher over to PaperImplementations.
Also, does this change apply to Paper right now, or only after that PR is merged?

Yes, this will still work on Spigot. The MinecraftServer#getCommands method exists in Spigot and has always existed since 1.13. There isn't any particular reason why the CommandAPI should not be using this method, other than the fact it hasn't been tested and testing will be required to ensure it's a viable solution (i.e. make sure everything works as it should!)


Port to Xcode 9.3

Fixes #1695

Moves the dataSource to be public, if people care about it's access control - you're welcome to merge and make your changes ;)
Hits the "Update to Latest Build Settings" button
Kills all warnings (flatMap ->  compactMap, and warning about compilation timing for the time ago (250ms on one function, in danger-js with wallaby, my tests can run in that time ) - fixed by making types explicit

Manually verified that tests pass BTW, only ones that don't are
        XCTAssertNotEqual(Secrets.GitHub.clientId, "{GITHUBID}")
        XCTAssertNotEqual(Secrets.GitHub.clientSecret, "{GITHUBSECRET}")
        XCTAssertNotEqual(Secrets.Imgur.clientId, "{IMGURID}")

Apparently compactMap is part of Swift 4.1. 🤔 Never seen it before.
I am just placing this link in case someone has trouble understanding the difference between flatMap and compactMap
https://useyourloaf.com/blog/replacing-flatmap-with-compactmap/

@orta hero 🙌

Thanks @orta! 😀
Sent with GitHawk

Test
Sent with GitHawk


Chore : make readme more welcoming

as a follow-up to PR #19,

added a build step to build the examples
revised the readme to contain some info on library integration, running tests and building examples
everything tested on Linux and Windows, can't test on Mac since I don't have such a thing around ;-)

Thank you very much!

I'm happy somebody already did the work and wrote such a library, so, happy to make it a bit more shiny ;-)


Explicit position_maker field in NewOrder and when initializing Order

Makes it clearer what the position represents throughout creating an Order.
This is a tiny cleanup.

bors r+


Fix crash on empty tables

fix for empty oath scopes
fix for empty definition properties

See also https://github.com/Swagger2Markup/swagger2markup-cli/issues/17

Coverage decreased (-0.03%) to 88.403% when pulling 16211b284a4dd8ab6322794b8032b4b16a9ef512 on ctytgat:master into aad387802ec5eae7954840564028dfa71913d057 on Swagger2Markup:master.

Coverage increased (+0.01%) to 88.445% when pulling e934b5fb9f85ba6983d827b3a2a5256d16a54924 on ctytgat:master into aad387802ec5eae7954840564028dfa71913d057 on Swagger2Markup:master.

@RobWin Hi I see you started preparing the 3.2.0 release, any idea when it'll be available?

Done.
1.3.2 has been released.


Prevent Android App Manager taking screenshots

Most security related apps implement a method to prevent Android from making screenshots of apps thst display sensetive data like private email or contacts

Dear customer,
Screenshots cannot be taken if the app preview is disabled. Thus, they will not work if the appropriate setting is enabled (github.com/CTemplar/android/issues/336) or a pin lock is set.
Please let us know if the option is not clear or you have further suggestions.

Please explain where is the 'disable app preview' setting.

@raven9nine I've just confirmed this feature has been developed recently and it will not be public until the next app version is released within the next coming days (probably next week as it will include other improvements).


redesign the about page

Describe the feature
to make attractive
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

assign to me for this work

What changes can you make ??
The about us page has alredy been changed by some other contributer , please do check the updated one and then if you feel like changing something raise the issue !!

okay ,thanks for your information


chore:  bump to latest version

Original changes https://github.com/jquense/react-big-calendar/compare/master...noloco-io:react-big-calendar:master

The library no longer bundles it's own versions of luxon, date-fns etc (the breaking change from 0.x => 1.x). We already have our own installed so this is ok.
The DnD fixes we'd applied seem to also have been made upstream
We still want support for our custom current time component

We could probably make a commit for the current time component & stop having to maintain this at all

We could probably make a commit for the current time component & stop having to maintain this at all


Add ab testing document

What does this change?

Add documentation on creating AB tests

Why?

We have documentation in Frontend and DCR for how to set up AB tests in each repo. For commercial, it can be hard to know where to start and what to do for each type of test (client-side and server-side), when needing to add an AB test for commercial purposed.

No changeset required

Thanks for adding this @domlander! Fyi I've added a link to the handbook to point to this document:
https://docs.google.com/document/d/10Mxxta6ypxAduVXJFp19uRoWtALQmAubdKtBwq7AqZ0/edit#heading=h.bvlhj6tvmihp


fix(dashboardeditor): need to refactor function to react component so it can be memoized

Need to add lots of memoizing to React Editor components to improve performance
Closes #
Summary

fix(BarChartCard): memoize the sample data creation
fix(DashboardEditor): wrap all function definitions with useCallback and memoize where possible
refactor(DashboardEditorCardRenderer): need to change the getCardPreview to a React component so I have more control over memoizing and rerender cycle
refactor(editorUtils): move the render helper functions to DashboardEditorCardRenderer, ideally they will be all migrated to components rather than render functions

Acceptance Test (how to verify the PR)

Verify the DashboardEditor story

:tada: This PR is included in version 2.141.0-next.63 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.142.0-next.1 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.142.0-next.1 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Provide means to report kernel releases for Linux Operating Systems

Summary
The Operating System (OS) object does not currently have a way to specify kernel information. The motivation behind this issue is that Linux allows the kernel to be “mixed and matched” for a given distribution version. For example, a user running Ubuntu 20.04 could be running the kernel release 5.15.0-118-generic or 5.15.0-122-generic or 5.15.0-100-generic, etc. None of the other existing fields in the OS object seem like a good fit for storing this information. Rather than using an already existing field improperly, I propose we either create a new Linux specific field or object in the OS object to contain the kernel release.
Potential Options
Option A: Add new linux_kernel_info object to os object via Linux extension
Make a new linux_kernel_info object under the Linux extension to contain all of the linux specific kernel information we may want to store, including a field for kernel_release. The benefit of making a new object instead of just a new field is that the object can have many fields added to it and can thus be extended/added to over time. This option can make adding Linux specific kernel info easier in the future. Then we can add the linux_kernel_info object to the os object via a Linux extension.
Pros:

Windows and Linux can have their own specific objects (linux_kernel_info and potentially a future windows_kernel_info)
Extensible

Cons:

We only have one field to populate in linux_kernel_info currently.

Option B: Linux and Windows specific kernel object
There already exists a kernel object, but it represents Kernel Resources, which seems very Windows specific. We could deprecate this object and replace it with new kernel objects that can be specific to Linux and Windows.
Pros:

Windows and Linux can have their own specific implementations of the object
Extensible
kernel object will better match the MITRE definition of kernel: https://d3fend.mitre.org/dao/artifact/d3f:Kernel/

Cons

Do not know if existing kernel object is currently being used

Good addition & idea overall!
Do you have any idea what the Attributes for the new kernel objects would look like?

Do you have any idea what the Attributes for the new kernel objects would look like?

For starters on the Linux side I would be interested in adding a "kernel_release" field, for example:
"kernel_release": {
    "caption": "Kernel Release",
    "description": "The kernel release of the operating system. Determined from the uname -r command output on Unix-based systems.",
    "type": "string_t"
}

We'll probably discuss it tomorrow (5 NOV 2024) for sure, if it's only that one Attribute (or a handful) I can see us just add it to os directly to keep the schema "flatter" so to speak. There is also precedence for OS specific data in there already with os.sp_name and what not
...hell, os.sp_name is where I stick nix kernel info right now 😬

Thanks for raising this. If we need any more time to discuss it, we could always use the Wednesday System Activity sync.

Here is an example of how Option B would be implemented: https://github.com/rebeccasenger/ocsf-schema/pull/1

Spoke about this issue again in the OCSF System Activities call. We decided on an Option C:
Add a new kernel_release attribute to the OS object. It will be available for both Linux and Mac. Then we can have a detailed description on the expected contents for Unix based systems and for Windows. It will be optional.


python36Packages.memory-tempfile: init at 2.2.3, python311Packages.music-assistant: init at 2.0.7, python3Packages.music-assistant-frontend: init at 2.6.3

Description of changes
Add music-assistant, music-assistant-frontend, and memory-tempfile (dependency of music-assistant)
Resolves #310509
Will ultimately be used to get the MusicAssistant plugin in Home Assistant working.
https://music-assistant.io/
https://github.com/music-assistant/server/
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Duplicate of #311927

Closing as duplicate.


Undefined index: name in Propel/Runtime/Util/Profiler.php

When running propel diff I get a notice
PHP Notice:  Undefined index: name in vendor/propel/propel/src/Propel/Runtime/Util/Profiler.php on line 206
And yet, if I give the section a name I get this error:
[Symfony\Component\Config\Definition\Exception\InvalidConfigurationException]
Unrecognized option "name" under "propel.runtime.profiler.details.time"
The docs on propelorm.org here: http://propelorm.org/documentation/07-logging.html#tweaking-the-profiling-information-at-runtime show the name being set programmatically but cannot be set via config.

Are you using version alpha4?

https://github.com/propelorm/Propel2/commit/097b2137be31cb9e45ca1f853b7a8ff22c6364e8
This is fixed, but it will only be in the alpha 5

According to my composer.lock I am using alpha 5
{
"name": "propel/propel",
"version": "2.0.0-alpha5",
"source": {
"type": "git",
"url": "https://github.com/propelorm/Propel2.git",
"reference": "75f775cf6de41595d1240885eea5fa5d475d228d"
},

Try dev-master version.

That worked.
Thank you!


Stick to strict pattern unification

Page 11 of Abel & Pientka reveals that solving non-linear spines is only sound if the type of RHS is also well-formed. Since we don't yet have typed metas or unification, the obvious solution for now is to remove the non-linear voodoo and stick to strict pattern unification.

So this simply means you should throw an error if a meta spine contains duplicate variables, correct?

Correct.

Speaking of typed meta/unify, would you like to address Twin types?

Heterogeneous unification is not a good idea in general.

Major complexity cost.
Minor benefit in unification strength.
Major performance cost, the most problematic is that we cannot skip unification of subterms which are completely determined by the type. For example, Agda does not unify (or even store) parameters of inductive types in constructors, because they are fully determined by the type. Given cons : (A : Set) -> A -> List A -> List A, if use homogeneous unification on cons A x xs and cons A' x' xs', we know already that A is definitionally equal to A'. This optimization can be extended to any rigid symbol (bound variables, postulates) other than constructors, and to definitions which are known to be definitionally injective (by some analysis). With heterogeneous unification, this doesn't work.

There's also a superior possible implementation in type theories with computing transports. For example, assume f : (a : A)  -> B a -> C, and we want to unify f a b with f a' b' at C. Assume that unify a a' returns with unsolved constraints. Vanilla homogeneous unification cannot progress here, and heterogeneous unification can, because it can unify b and b' even though they are not known to have the same type. However, if coercions compute, we can do the following: have p : a = a' as a propositional equality returned by unify a a', then unify coe (ap B p) b with b'.
This way, we keep all benefits of homogeneous unification, and depending on how strongly our coercions compute, we get a precise solutions to heterogeneous equations as well.

This issue is solved now.


fix(db-mongodb): handle null values with exists on clearable fields

Description
The Problem:
When a relationship, upload, or select field is cleared from the UI, the value is not unset - it is set to null which differs from the initial unset value.
This goes against users' expectations when using an operator like exists in the UI. If one of the aforementioned fields is cleared and queried with exists: true, values of null are returned. The inverse is also true (exists: false does not return null values)
Solution:
This PR modifies the functionality of exists in order to handle this. ⚠ This does however diverge from how the exists operator works in MongoDB.

Weighing this PR against the alternative, make unsetting one of these clearable fields back to the default value.


Zones custom inputs

Thank you very much for this integration.
I have a Pioneer VSX-923K receiver and some of the autodetected inputs are not working (they are not present on the receiver).
I tried to customize the sources but those for zone_2 and zone_h are not changing.
In the dashboard I see all the sources from the main zone.
My config is:
- platform: pioneer_async
  name: Pioneer AVR
  host: avr.cr.home.lan
  port: 23
  scan_interval: 60
  timeout: 5.0
  sources:
    "Wii U": "25"
    "HD1": "04"
    "PS4": "06"
    "VE1": "15"
    "PS3": "22"
    "HDMI5/MHL": "23"
    "Switch": "24"
    "XBOX360": "34"
    "Internet Radio": "38"
    "Media Server": "44"
    "Favourites": "45"
    "Ipod/USB": "17"
    "TV": "05"
    "CD": "01"
    "Tuner": "02"
    "Adapter Port": "33"
  params:
    ignore_volume_check: true
    zone_2_sources: ["04", "06", "15", "05", "01", "02", "33"]
    zone_h_sources: ["25", "04", "06", "15", "22", "23", "24", "34"]

There may be another step required to update the HA integration to use the per-zone sources list, that functionality was added to the API module relatively recently. Will be looking into this.
Note that zone_h_sources is currently inconsistent with HDZone references elsewhere, which uses zone Z. This is to be fixed, but as part of that the params item will be renamed at which time you'll need to update the configuration.

The integration needs to be updated to pass the zone information into the function in the API to return the current source, a lot of the recent functionality added to this API hasn't been added to the integration yet.

Thank you for the feedback.
I'll wait for the updates.

This has been implemented in https://github.com/crowbarz/ha-pioneer_async/ release 0.7.3. You can also specify zone subsets via the UI configuration now.
Note that param zone_h_sources has been renamed to zone_z_sources, but I will be renaming that again to hdz_sources in a future release for better consistency. (That will be flagged as a breaking change.)


Edit release notes for v23.1.0-alpha.8 for clarity on mux rangefeed

Edited a release note that referred to mux rangefeeds being "enabled", which may have caused confusion as they are no longer enabled by default. The original release note was edited "too much" and moved away from the meaning.

Thank you Florence.


what is the future of laravel-mix?

this is not a bug but there is no discussions tab in this repo
i am curious what the future of mix is, given that laravel has moved to vite
to be honest, i think mix is vastly superior to vite, but thats just my opinion
what is the future of mix?

A large portion of the ecosystem has/is/will be moving to Vite however there's still a spot for Laravel Mix for projects that need it. Including a lot of non-Laravel projects that happen to use Mix. So, not Mix isn't going anywhere. I can't speak to plans for the the far future but I plan on keeping it updated where possible/feasible and upgrading it to webpack 6 whenever that becomes a thing in the future.
Now, I definitely don't give Mix the attention it needs — mainly because of higher priorities and life stuff — but I've no plans to stop supporting it.


feat: added deploy workflows for staging and production environments

Description
This Pull Requests separates the workflow that deploys to staging should take comparing with production.
In the case of STAGING we want the deployment to be executed when a pull request is merged to the main branch, or when there is a direct commit to that branch.
The tags that must be applied for that environment are those related to the last commit (short sha) and also the tag: latest.
For PRODUCTION, the tag latest shouldn't be applied, instead of that, the word stable is the one to be applied.
Testing Instructions

Merge a Pull Request into main branch (deploy to STAGING)
Create a new release (deploy to PRODUCTION)

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

I am not sure I can really comment on this PR due to my lack of knowledge in this area, but I love the automation!
We have only one staging env, right? It could probably be nice if it was possible to also stage the feature branches (audio integration, redesign) before merging them into main.

I like how you've separated the work here, it makes sense to me. I think if we ever needed more environments we'd just refactor how this works completely and perhaps not even use GitHub actions.

Feel free to undraft this so you can test it!

The pipeline has been fixed and you can consider it ready for review.

The build workflow was moved as an action, in order to be called by other workflows in the following way:
- name: docker build
  uses: ./.github/actions/build


Unable to extract Samsung Firmware

Results in exponential expansion that eventually fills the disk.
https://www.samsungimaging.com/file/download?XmlIdx=280&file=C200GLU0APE4_160519_1848_REV00_user.bin

Try using the -r flag to delete intermediate files that binwalk can't process. This should prevent the disk from filling up.
https://github.com/ReFirmLabs/binwalk/wiki/Usage#-r---rm


File - storage location

Can I change the storage location in $cordovaFile like documented in the official docs of cordova file plugin? I want to store / read all my files in cordova.file.dataDirectory.

The file plugin has been updated to use resolveLocalFileSystemURL (in the master), so read/write/copy/move methods can use the various FileSystem cordova.file.* objects. Docs show changes too. Hopefully that fixes your issues.

can any one reply this thread.
https://forum.ionicframework.com/t/cordova-file-datadirectory-not-creating-file-inside-the-app-folder/76471


[BEAM-14342] Fix wrong default buffer type in fn_runner

The input buffer type can be either ListBuffer or GroupingBuffer, using None instead so that the actual Buffer can be replaced with first input later.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.


Test Flake: istio.io/istio/galley/pkg/runtime.TestProcessor_EventAccumulation_WithFullSync

Describe the bug:
Recent failure for subject test
https://prow.k8s.io/view/gcs/istio-prow/logs/istio-postsubmit/4836
Expected behavior:
test case passes (or code is correct)

I believe this was fixed some time ago. The postsubmit board seems to show all green now:
https://testgrid.k8s.io/istio-postsubmits#unit-tests&include-filter-by-regex=WithFullSync


Fix cross-compile build on Windows

Thanks, I've applied this patch to the devel branch and it will be included in the next release.


About and Methodology Page

Description:
Briefly describe the feature request:  A page that will have long text
What problem does this feature solve for the users? It will have the metadata and host the data methodology.
How the Feature Works: Page
Click link for details
https://docs.google.com/document/d/1TUrdCRnbj6TSqiuwITKUpnDUEi_ktm_3PmgsaD0y2bw/edit?usp=sharing

If we're using a single page (/about?) for both about and methodology, the methodology block/ui is the same as history block in the about (which has already been implemented in 921).
Is there anything else we need to do for this story @RalphOwah ?

You are correct @kilemensi , #921 ticket should suffix, although I am not sure why it's being called a history block by @koechkevin
But we need for this story in consideration is a single page with 2 block sections for long text

About section
Methodology section

Cool, @RalphOwah, what I wanted to confirm is: should those block look like history block or not? If yes, we can add as many blocks as we need already in any page without any extra code.
Please see https://climatemapped-africa.dev.codeforafrica.org/about

Yes @kilemensi the history block format works perfectly, it will also help if it allows for multimedia (images) and tables within the block considering the series of copy/content the ClimateMap team envisages for this page.

With the updated RichText component, this should be done


Mr. Data Coverter not recognizing  excel text as text

What I want is for quotes to wrap the zipcodes when i bring the excel file into Mr. Data Converter. How do I do this please? I've converted them to text in excel.  Thank you

I have cells of numbers and letters follow sometimes. Example = 234A. I changed the format of cells to text in excel and tried doing both that and adding quotes. Example = "234A". Mr. Data Converter takes off the quotes upon conversion back into 234A and invalid JSON.


Can not catch HttpMethod: OPTIONS on a http request

I'm writing an ActionFilterAttribute where I check userId route/query parameters and compare it against the subject of a jwt token. I noticed that my Action Filter gets triggered twice. In chrome I can see that an OPTIONS request is sent to the server and in my debug console output I can see the call with the correct http method:
Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request starting HTTP/1.1 OPTIONS http://localhost:5000/api/v1/users/33417
But when it hits my Action Filter, Http Method is always set as GET so I can not make my filter return on an OPTIONS call.
Here is an  OnActionExecutionAsync override method to reproduce this behavior:
public override Task OnActionExecutionAsync(ActionExecutingContext context, ActionExecutionDelegate next)
{
	if (HttpMethods.IsOptions(context.HttpContext.Request.Method))
	{
		Debug.WriteLine("HTTP METHOD: OPTIONS");
		return base.OnActionExecutionAsync(context, next);
	}
	// Other Code ....
}

Is this an issue or is there any other way I can get the OPTIONS http method. I have searched the issues and googled it with no results.
Thanks.

Options requests are handled by MVC by default. See https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-2.1#enable-cors-in-mvc for details on configuring it.


Ceo and writer

https://github.com/Kboentkuri2

Hi @Kboentkuri2, you've reached the docs team. You haven't provided any information so I am assuming that you filed this issue by mistake. I'll close the issue, but if you do have an issue, feel free to reopen and provide more information. Thanks!

Hi @Kboentkuri2, I still I am not sure I understand your issue. In any event, you have reached the docs team for Power BI. This channel is intended for issues with the  Power BI documentation. If you have a support issue with Outlook, I suggest trying the support link at the bottom or https://support.microsoft.com/en-us/outlook. Good luck!

Well


BadgeNumber is Missing from api

Could you implement set and get badgeNumber ?

This plugin looks very interesting https://www.npmjs.com/package/cordova-plugin-badge
Would you try it and let me know if it works for you?

I'm using this plugin and cordova-plugin-badge.
here is my requirement: when iOS app run in background, i need to increase badge number when fcm receive notification.
But the function 'onNotification' not fired (work fine in foreground).
should i use other way to implement this requirement? like background mode?


Add dependency analysis to tree scanning

This relates to ticket #25.

Add dependency information to database
Capture dependency information from source tree descent
Unit test new capability
Extend system testing to cover dependencies

We need to be consistent with the use of typing - I am in agreement that it's a good idea and we should capitalise on being a brand new project by using it from the offset.  But we ought to be strict about applying it (i.e. if we are going to do it everywhere then it really should be everywhere... if we aren't then we need to be able to give a concrete rule about when it should and shouldn't be used)

I have raised #37 to cover this issue.

It seems as though the plan is that over time we are going to be migrating the contents of the TestCases directory into the system-tests directory (and are doing so gradually, as our testing is updated to cope with the given cases).  Perhaps we should remove the MinimalFortran subfolder from TestCases at this point?

I did consider this but was a little gun-shy of removing one of our functional examples. However we know how to compile such a simple Fortran program and it could lead to confusion having nearly the same thing in two places.

Ready for a second review.


Release process improvement: Auto update core versions

Update local package version references in the repo

@benbp , @jhendrixMSFT The original issue was not super descriptive either. Do you recall what we wanted to bump?

My guess is this is about automatically updating dependencies for a module.


Sync v2

Add sync functionality.
Now syncing actually works 🎉 . It required setting up a sync server for VLCN. This was roughly what the initial p2p implementation was meant to accomplish, but it was ineffective without an always-on peer. Thus we have a server now.
The source is under sync-server if you want to run your own. I've deployed a public instance which can be used without configuration.
This is a beta feature. I've only done light testing on my own system so there may well be issues, especially related to schema migrations.
Sync as backup
The sync server stores a copy of messages and threads and it does so using standard sqlite3 on a standard file system. In other words, it should be more stable than the wasm-sqlite on top of indexedDB that Prompta uses in the browser. Not complaining—i've been very happy with wasm-sqlite so far. However, we've had issues with data corruption in the browser (hopefully solved now with VLCN v0.16).
Point being, enabling sync even if you don't use Prompta on another device will back up your messages. In the case of a corrupted browser database you can reset and re-enter the sync key to pull the data back down.

This also adds in functionality to restore data from a prior database version, although this is likely only useful in dev. If you have to reset the database you can attempt to restore previous data using the cmd+k menu.

Trying this out now. I've copied the sync code from iOS Safari to MacOS Chrome.
On Chrome however, although the copied sync code is shown in the sync panel (and Connection is Active), there is no synced chat, and I've noticed that (undef Cmd-K Settings) the Database code still has a different hex code to the copied sync code, whereas back on iOS Safari the Database code shown has the same hex code as the copied sync code.


Extensions menu parameter is missing

The extensions menu where the "Manage Extensions" button is located is not specified here.

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

ID: 27088666-73eb-b621-253e-1957218cf765
Version Independent ID: da38ef89-6570-a27e-9f9a-eaac22baec07
Content: GUIDs and IDs of Visual Studio Menus - Visual Studio
Content Source: docs/extensibility/internals/guids-and-ids-of-visual-studio-menus.md
Product: visual-studio-windows
Technology: vs-ide-sdk
GitHub Login: @gregvanl
Microsoft Alias: gregvanl

Hi @BigHoss Thank you for pointing this out. PRs welcome.

I would PR that if i knew how to get that information :sweat_smile:

@dgriffen Can you find this value?

The ID is IDM_VS_MENU_EXTENSIONS AFAICT


Move creation of ObjectMapper to JacksonMapperUtilities or companion objects

User Story
Instantiating an ObjectMapper is a pretty heavy operation that should only occur once per configuration. We should hold onto the few ObjectMappers we need rather than creating new ones on the fly all over the codebase.
ObjectMappers are completely thread-safe and do not need to instantiated per read/write.
Risks/Impacts/Considerations
Using the wrong mapper in the initial spot which could cause problems serializing/deserializing.
Dev Notes
Look for the following calls:
ObjectMapper()
jacksonObjectMapper()
jacksonMapperBuilder()

If you are using a plain json mapper use the existing  one in JacksonMapperUtilities.
We should add a default configuration for a YAML ObjectMapper in JacksonMapperUtilities and use it wherever default YAML parsing is needed.
Mappers created in companion objects are generally the best option if the code you are working with needs a custom configuration.
Acceptance Criteria

New default YAML ObjectMapper
Fewer instantiations of ObjectMapper and depending on the existing ones in JacksonMapperUtilities.
Custom ObjectMapper in companion object or investigate if the custom one is really necessary

Hey team! Please add your planning poker estimate with Zenhub @arnejduranovic @jack-h-wang @jalbinson @JessicaWNava @JFU-NAVA-PBC @jimmyfagan @mkalish @thetaurean

Does this include updating tests to follow these new guidelines?


Add theme: Exit Button Right Padding

Add theme: Exit Button Right Padding
This PR adds a new theme to the theme library.
Theme Details

Name: Exit Button Right Padding
Description: A simple theme that adds a bit of padding to the right of the exit button
Homepage: https://github.com/ericmackrodt/zen-themes/
Author: @ericmackrodt

you could use --zen-element-separation

I'll updated it

Hi, is there a place that documents all of the --zen css variables?

Not really, you could look into zen-theme.css in the source code...


BeamGuard not being rechecked when supplying builder to MaterialApp.router

This is probably me doing something wrong but I'm really stuck so figured I would ask for help here. When I supply a builder to MaterialApp.router my BeamGuards are not being rechecked when auth state updates. If I remove the builder auth state works as expected. This is based on the Riverpod Auth example.
// This widget is the root of your application.
@override
Widget build(BuildContext context, WidgetRef ref) {
  final auth = ref.watch(authProvider);

  auth.when(
      loading: () => print('Loading'),
      authenticated: () => print('Authenticated'),
      unauthenticated: () => print('Unauthenticated'));

  return BeamerProvider(
    routerDelegate: routerDelegate,
    child: MaterialApp.router(
        theme: NeatFTTheme.dark(),
        builder: (context, widget) => Navigator(
              onGenerateRoute: (settings) => MaterialPageRoute(
                  builder: (context) => DialogManager(
                        child: widget ?? Container(),
                      )),
            ),
        debugShowCheckedModeBanner: false,
        routeInformationParser: BeamerParser(),
        routerDelegate: routerDelegate),
  );
}

So I was able to get it working by changing my code
return BeamerProvider(
  routerDelegate: routerDelegate,
  child: MaterialApp.router(
      theme: NeatFTTheme.dark(),
      builder: (context, widget) => DialogManager(
            child: widget ?? Container(),
          ),
      debugShowCheckedModeBanner: false,
      routeInformationParser: BeamerParser(),
      routerDelegate: routerDelegate),
);

and then in my dialog code instead of using it's own context I changed it to use Beamer's navigator context, is this the correct way of doing this at all?
void _showDialog(DialogRequest request) {
  showDialog(
    context: Beamer.of(context).navigator.context,
    barrierDismissible: false,
    builder: (context) {
      return AlertDialog(
        title: Text(request.title),
        content: Text(request.description),
        actions: [
          ElevatedButton(
              onPressed: () {
                _dialogService.dialogComplete(DialogResponse(
                    fieldOne: '', fieldTwo: '', confirmed: true));
                Navigator.of(context).pop();
              },
              child: Text(request.buttonTitle))
        ],
      );
    },
  );
}

Hi @wtfspiff :wave:
Thanks for creating an issue.
You are correct. Here are some explanations:
The first approach (building Navigator with onGenerateRoute) didn't work because this is in conflict with Router/Beamer which is responsible for  building the main Navigator.
Using Beamer.of(context).navigator.context is not wrong. In this case, you are not getting the right context by default because you're using the builder which will insert widgets above Router/Navigator, and showDialog needs to be below Navigator. This is also the reason why BeamerProvider is necessary; otherwise the Beamer.of(context) would also not work anywhere in the Widget tree. The child in builder is the Router widget.


feat(data_classes): kinesis firehose data event

Issue number: #1539
Summary
Adding KinesisFirehoseEvent data class for handling Kinesis Firehose Lambda events (for Data Transformation).
Changes

Please provide a summary of what's being changed

Adding KinesisFirehoseEvent data class and respective sub-DictWrapper classes for handling Kinesis firehose event structure
Adding functional test for KinesisFirehoseEvent

This handles both text events and json events

Updating documentation for KinesisFirehoseEvent

User experience

Please share what the user experience looks like before and after this change

This is included in the documentation updates.
Checklist
If your change doesn't seem to apply, please leave them unchecked.

[X] Meet tenets criteria
[X] I have performed a self-review of this change
[X] Changes have been tested
[X] Changes are documented
[X] PR title follows conventional commit semantics

Is this a breaking change?
RFC issue number:
Checklist:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

View rendered docs/utilities/data_classes.md

@ryandeivert it seems we have a couple of failing tests due to mypy errors. Can you take a look at them, please?

hi @rubenfonseca I just pushed a commit that I think will resolve these. would you mind approving the CI job? thanks!

sorry @rubenfonseca - I had some syntax errors (missing :) and just fixed it

@rubenfonseca okay I think the latest commit should do it now - ran make mypy locally to confirm, and pre commit hooks passing. sorry about that!

I've tried to figured out why this is failing here: https://github.com/awslabs/aws-lambda-powertools-python/actions/runs/3117242603/jobs/5057874979
it looks unrelated to my changes, and related to this recently merged change: https://github.com/awslabs/aws-lambda-powertools-python/pull/1526
I have merged the develop branch into this feature branch in hopes that it resolves that failure(s)

Hey Ryan, apologies we missed this linting issue - we’re doing an offsite
on Monday and should get back to you soon after; appreciate your patience
and support.
This feature is one of those we can improve developer experience a lot -
Firehose events expect certain responses too, so this is a great stepping
stone to create an additional Batch Processor after this is merged.
Thank you for helping make everyone’s experience better <3
On Sat, 24 Sep 2022 at 22:05, ryandeivert @.***> wrote:

I've tried to figured out why this is failing here:
https://github.com/awslabs/aws-lambda-powertools-python/actions/runs/3117242603/jobs/5057874979
it looks unrelated to my changes, and related to this recently merged
change: #1526
https://github.com/awslabs/aws-lambda-powertools-python/pull/1526
I have merged the develop branch into this feature branch in hopes that it
resolves that failure(s)
—
Reply to this email directly, view it on GitHub
https://github.com/awslabs/aws-lambda-powertools-python/pull/1540#issuecomment-1257056315,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZPQBFSAGSJHBRNPSXM333V75NJ3ANCNFSM6AAAAAAQTV3YR4
.
You are receiving this because your review was requested.Message ID:
@.***>

Hi all! Just to help here, I created a Kinesis Firehose using a Lambda as a data transform and the payload is as per the documentation (https://docs.aws.amazon.com/lambda/latest/dg/services-kinesisfirehose.html). There are some optional fields which should be fine to create a test for them.

@ryandeivert let me know if you want us to make the changes above, so we can merge your PR and include this in our next release!

Hi @ryandeivert and @rubenfonseca! I'll work to fix small things in this PR and include this feature in the next release, ok?

hi @leandrodamascena / @rubenfonseca -- so sorry I fell off on this. you are welcome to make these changes or I can get to it later this week!

hi @leandrodamascena / @rubenfonseca -- so sorry I fell off on this. you are welcome to make these changes or I can get to it later this week!

No need to apologize! We know everyone is very busy. Be our guest and feel free to fix these small changes :smiley:
We expect to release a new version next week, so we have time to wait for your update. btw, i will add more comments on this PR.
Thanks for the prompt reply.

I made two commits because they only change the type and that reduces the work a little. There was an error in the pipeline, but when you make the final changes, it will be fixed. Thanks

hi @leandrodamascena taking a look at this now. will follow up

hi @leandrodamascena -- I believe I have addressed all of the requests. I merged the develop branch into this and used the new test events provided in the other recently merged PR

hi @leandrodamascena -- I believe I have addressed all of the requests. I merged the develop branch into this and used the new test events provided in the other recently merged PR

Hiiii @ryandeivert! That's amazing that you can handle all the changes quickly! I will check this tomorrow!
I see the pipeline is failing some test, but don't worry, I can fix that.
Thank you!!

@leandrodamascena sorry about that! I think it should be fixed now..

@leandrodamascena sorry about that! I think it should be fixed now..

Hi @ryandeivert pls don't apologize, you did a great job! Everything is working as expected (I tested it locally) and I'm just worried about this.
If we assume that all data is a JSON object can be a problem for those who use Firehose DataClass Events - and maybe others DataClass Events - and can affect the user experience. Let me discuss this internally and I back here with updates.

I'm just worried about this.
If we assume that all data is a JSON object can be a problem for those who use Firehose DataClass Events - and maybe others DataClass Events - and can affect the user experience. Let me discuss this internally and I back here with updates.

@leandrodamascena thanks for all the feedback! when I'd robbed that logic from another data class, I did have this same question. however, my conclusion at the time was that users implementing this event source will likely know whether or not their data is in fact json, and would use the appropriate function accordingly.
In the event (for whatever reason) that users do not know for certain, I would foresee them wrapping the call to data_as_json in a try/except block to handle the JSONDecodeError and simply fall-back on the data_as_text value.
This method simply leverages Python's duck-typing concept and IMO isn't something you need to address in this convenience function (aside from adding documentation that it could raise a JSONDecodeError/ValueError). The other alternative would be dropping the function altogether and leaving all data decoding to be an exercise for the user (maybe the preference here in this new class, but would break backwards compatibility in other classes).
I'm fine with whatever you all land on for this - just let me know the outcome and if you want me to make any additional changes!

In the event (for whatever reason) that users do not know for certain, I would foresee them wrapping the call to data_as_json in a try/except block to handle the JSONDecodeError and simply fall-back on the data_as_text value.

I think it might be a good solution.

This method simply leverages Python's duck-typing concept and IMO isn't something you need to address in this convenience function (aside from adding documentation that it could raise a JSONDecodeError/ValueError). The other alternative would be dropping the function altogether and leaving all data decoding to be an exercise for the user (maybe the preference here in this new class, but would break backwards compatibility in other classes).

We avoid breaking changes without proper communication with our clients, so removing this in other classes isn't a good idea in fact.

I'm fine with whatever you all land on for this - just let me know the outcome and if you want me to make any additional changes!

Let me share your thoughts with others and I'll be back here with updates on Monday/Tuesday.
Thanks.

Hi @blewinter! Let me open a PR for this feature and if you have bandwidth you can do a review with me.
Thank you very much for all the interaction so far and we'll be happy to mention you in the credits for this new feature. :1st_place_medal:

@leandrodamascena thanks for all the feedback! when I'd robbed that logic from another data class, I did have this same question. however, my conclusion at the time was that users implementing this event source will likely know whether or not their data is in fact json, and would use the appropriate function accordingly.

Hi @ryandeivert! We think this is the best approach and users can handle the exception on their side if the data is not json. Using the other solution to fall back to the data_as_text value (if not JSON) can be difficult for users to deal with casting and data type.
So I think this PR is ready to merge. If you don't have any other consideration we can merge it.

@leandrodamascena sounds good to me! nothing else on my end :) feel free to merge when you see fit!


Docs: Remove Elastic references from .md docs

Description

update FAQ to narrow scope, clarify semver, remove why opensource question
reomove reference to Elastic Container Registry
remove links to starter projects
update doc site links
remove backport section from release process doc and add legacy notice (Note: I left this file for now, as it's a useful reference for what release automation exists that we may want to re-use or re-implement)

Issues Resolved
fixes https://github.com/opensearch-project/oui/issues/86
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] All tests pass

[ ] yarn lint
[ ] yarn test-unit

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Could the releasing-versions.md and the RELEASING.md files be combined in some way or is that outside of the scope of this PR?

Could the releasing-versions.md and the RELEASING.md files be combined in some way or is that outside of the scope of this PR?

Yeah - I think the right way to go is to remove releasing-versions.md in favor of RELEASING.md. But I left it for now, because it's interesting to feature compare how the previous system worked with how we plan to do releases.


Good job

hello friend, I like your theme and I make a try, but I met one problem:
the pic on home page is aligned left, large and can not show all

when I install
npm install hexo-renderer-less --save

I met 'npm WARN deprecated<EMAIL_ADDRESS>The major version is no longer supported. Please update to 4.x or newer'


Implement sizeof on objects?

Is your feature request related to a problem? Please describe.
Currently ds.nbytes returns the size of the data.
But sys.getsizeof(ds) returns a very small number.
Describe the solution you'd like
If we implement __sizeof__ on DataArrays & Datasets, this would work.
I think that would be something like ds.nbytes + the size of the ds container, + maybe attrs if those aren't handled by .nbytes?

It seems like the concensus from https://bugs.python.org/issue15436 is that only C extension types should implement __sizeof__.

Mmm for better or worse, Dask relies on sizeof to estimate the memory usage of objects at runtime. We could move that over to some new duck-typed interface like using .nbytes if it's around, but not all objects will want to expose an nbytes attribute in their API.
IMO, I think the best path is for objects to implement __getsizeof__ unless there's some downside I'm missing.

I don't love going against the guidance from Python core developers. My gut is that a Dask-specific protocol may be safer. That said, if Dask is the only library using sys.getsizeof() for some real purpose, then perhaps this is safe enough.
There's still some ambiguity to me about exactly what should be included in "size of" (e.g., do we include lazy values or not?) but we can probably figure that out. I suspect Xarray's implementation would be need to be recursive in some way, to handle nested Dask or lazy arrays.

Should we close?
I would have voted towards having __sizeof__ return our current .nbytes — while it's not perfect, sys.getsizeof already returns a number, which is just completely wrong at the moment.
I wasn't sure whether the consensus at https://bugs.python.org/issue15436 was "non-C-extension-types shouldn't implement __sizeof__", vs. "C-extension-types should implement __sizeof__ but for other types it's not that helpful" ...and then maybe for dask it is helpful so it makes sense for us to do it.
But I don't have a strong view, happy to close if we've decided.

I'll reluctantly close given the weight I put on @shoyer 's view...

I just stumbled over this via https://github.com/dask/distributed/issues/5383 and wanted to add that there is also a way to tell dask what the size of an object is without overloading __sizeof__, e.g.

class MyCustomDataClass:
    def __init__(self, nbytes):
        self.nbytes = nbytes

from dask.sizeof import sizeof

@sizeof.register(MyCustomDataClass)
def sizeof_my_custom_data_class(obj):
    # Do whatever you want here as long as it returns an integer
    return obj.nbytes

I stumbled over this in https://github.com/pydata/xarray/issues/9088 again
Given that...

There appears to be some reluctance of implementing a dunder method
apparently all dask imports in xarray are lazy so implementing the sizeof dispatch might be awkward

I assume this is something that should be implemented in dask?

Looks like we can add an entrypoint: https://docs.dask.org/en/stable/how-to/extend-sizeof.html#extend-sizeof? That seems like it should work with lazy imports?

xarray is important enough that we can put this into dask itself. We can handle lazy registration there as well and are doing this for others important libs as well. The data structures in xarray are a bit complex which is why this stuff living here would make sense but I think if we needed to use endpoints, that wouldn't be worth it.

Thanks @fjetter
Can you post the example you're using to debug this?
There's a conceptual complexity as pointed out above:

There's still some ambiguity to me about exactly what should be included in "size of" (e.g., do we include lazy values or not?) but we can probably figure that out. I suspect Xarray's implementation would be need to be recursive in some way, to handle nested Dask or lazy arrays.

What does dask use this size for? Does it want the size in memory when all buffers are loaded? Or just the in-memory of the Xarray object at present (regardless of whether buffers are loaded or not)? An analog would be a zarr array for example, which is tiny but could become a very large array when loaded in to memory.

What does dask use this size for? Does it want the size in memory when all buffers are loaded? Or just the in-memory of the Xarray object at present (regardless of whether buffers are loaded or not)?

Dask wants to know what is currently in memory. We're using this mostly for scheduler heuristics, e.g. when submitting stuff or writing intermediate results things to disk. For most practical applications the difference will likely not matter much. Accuracy is also not incredibly important. The more accurate, the better, but as long as the rough order is accurate, that's good enough for us.

https://github.com/dask/dask/pull/11166 using .nbytes so it's using the in-memory size after all lazy arrays are loaded. It's also inaccurate for DataArrays sadly but we can fix that once we know what you want.

Yeah, this doesn't sound like what dask wants. We'll likely have to do something more complex then. In an earlier version of that PR I was just estimating sizes of a couple of (internal) attributes but that felt wrong. I'll open another PR with more tests and ping you for feedback.


iOS project with cyrilic workspace unable to build

Hello,
I have iOS project with cyrilic workspace name and when i try to connect it project with bitbucket repo -> Configure build -> I get message "We couldn’t find any iOS Objective-C/Swift projects in your branch."
But if i rename workspace to english everything is ok.
I propose to supplement the documentation for this case, or detect cyrilic symbols in project assocated files and show full description about this case instead of "We couldn’t find any iOS Objective-C/Swift projects in your branch"
Thank you.

Thanks for pointing this out @ivanbogomoloff. It does look like this is a current limitation. We are going to take a further look into this. I'll update the issue when I have more details.

@ivanbogomoloff Could you reach out to support from App Center portal about this? We likely need more details, as I wasn't able to reproduce it.

I will be able to do in the next 2 weeks

@ivanbogomoloff Could you reach out to support from App Center portal about this? We likely need more details, as I wasn't able to reproduce it.

I will be able to do in the next 2 weeks with sample ios project

@ivanbogomoloff Did you get a chance to look at this? No rush. Just checking.

i will try now

Xcode 11.1 which is deprecated as of Nov 5, 2020.


Storage read service should not return a nil cursor [backport 2.0.x]

Backport the fix for  #20952 to the 2.0 branch

Closing this, looks like it was already forward-ported


docs: remove from-source rxcpp_vendor

Package has been released and built by the ROS buildfarm (job) for Kinetic. Melodic release will follow.
If/when the package is synced to the main repositories, documentation and .rosinstall files should be updated to no longer checkout rxcpp_vendor from source and instead depend on the binary artefact.

It's already available for amd64 and i386 in the ros-testing repository.

Melodic release done.
We'll need to wait for the sync for rxcpp_vendor to appear in the main repositories.

Melodic has been synced. rxcpp_vendor is now available as a ROS package.

Compile-tested rxros_examples on Kinetic after configuring the ros-testing repository. Everything seems to be OK with RxCpp installed via rxcpp_vendor.

Fixed in #25.


java.lang.NullPointerException: Attempt to invoke virtual method 'void com.felhr.usbserial.UsbSerialDevice.write(byte[])' on a null object reference

When ever  I try to use  serial port.write("DATA".getbytes)
i got Following issue :java.lang.NullPointerException: Attempt to invoke virtual method 'void com.felhr.usbserial.UsbSerialDevice.write(byte[])' on a null object `reference```
//override method called from fragmentA
public void send(String s){
Log.d("From fragement A",s);
serialPort.write("DATA".getBytes());
}
//
private final BroadcastReceiver broadcastReceiver = new BroadcastReceiver() { //Broadcast Receiver to automatically start and stop the Serial connection.
@Override
public void onReceive(Context context, Intent intent) {
if (intent.getAction().equals(ACTION_USB_PERMISSION)) {
boolean granted = intent.getExtras().getBoolean(UsbManager.EXTRA_PERMISSION_GRANTED);
Toast.makeText(context, "boolean" + granted, Toast.LENGTH_LONG).show();
if (granted) {
connection = usbManager.openDevice(device);
Toast.makeText(context, "connection" + connection, Toast.LENGTH_LONG).show();
serialPort = UsbSerialDevice.createUsbSerialDevice(device, connection);
if (serialPort != null) {
if (serialPort.open()) { //Set Serial Connection Parameters.
Toast.makeText(context, "serialopened", Toast.LENGTH_LONG).show();
serialPort.setBaudRate(9600);
serialPort.setDataBits(UsbSerialInterface.DATA_BITS_8);
serialPort.setStopBits(UsbSerialInterface.STOP_BITS_1);
serialPort.setParity(UsbSerialInterface.PARITY_NONE);
serialPort.setFlowControl(UsbSerialInterface.FLOW_CONTROL_OFF);
} else {
Log.d("SERIAL", "PORT NOT OPEN");
Toast.makeText(context, "PORT NOT OPEN", Toast.LENGTH_LONG).show();
}
} else {
Log.d("SERIAL", "PORT IS NULL");
Toast.makeText(context, "PORT IS NULL", Toast.LENGTH_LONG).show();
}
} else {
Log.d("SERIAL", "PERM NOT GRANTED");
Toast.makeText(context, "PERM NOT GRANTED", Toast.LENGTH_LONG).show();
}
} else if (intent.getAction().equals(UsbManager.ACTION_USB_DEVICE_ATTACHED)) {
serialPort.open();
} else if (intent.getAction().equals(UsbManager.ACTION_USB_DEVICE_DETACHED)) {
serialPort.close();
        } else if(intent.getAction().equals(CUSTOM_INTENT)){
            serialPort.close(); Toast.makeText(getBaseContext(), "HEY BUDDY supper it works", Toast.LENGTH_SHORT).show();}

    }
};

Hey did you find a solution to this ? I am facing the same issue.

You have to check serial object not to be null before using write (byte[]).
On Sep 21, 2017 12:39 AM, "TanayaBhave"<EMAIL_ADDRESS>wrote:

Hey did you find a solution to this ? I am facing the same issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Also use some delay before every continuous write.
On Sep 21, 2017 12:39 AM, "TanayaBhave"<EMAIL_ADDRESS>wrote:

Hey did you find a solution to this ? I am facing the same issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

can you explain what variable is your serial object in the above code. So i get an idea as to what should I check.  I am a beginner !

SerialPort is variable that  i used as serial object
On Thu, Sep 21, 2017 at 10:11 AM, TanayaBhave<EMAIL_ADDRESS>wrote:

can you explain what variable is your serial object in the above code. So
i get an idea as to what should I check.  I
am a beginner !
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/felHR85/UsbSerial/issues/103#issuecomment-331049321,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXTW_PbY_b69VN1kqWfrUoFMpKsFYZOrks5skejpgaJpZM4NfGAi
.


Closest Dessert Cost

Problem Link
https://leetcode.com/problems/closest-dessert-cost/
Coding platform
LeetCode
Programming language

[ ] C
[ ] C++
[ ] Java
[ ] Python

Additional context (OPTIONAL)
Med Level Problem

Assign me in C++.

I would love to implement in python as a part of Cross-woc. Kindly assign it to me.

Hi @Nivedita967
I would like to solve it  in Java. Please assign it to me.

Sure @abhinav5481

will do it in C

@muthuannamalai12 I have requested you some changes in your PR. Check it ASAP.

Hi @Nivedita967
Can I solve it in C?

@Nivedita967 is it open??

@Nivedita967 is it open??

No.


Fix dissect ingest processor parsing empty brackets failed

Description
Fix the bug of dissect ingest processor parse empty brackets failed, and add some unit test code and yaml rest test.
The bug is caused by that when walking through the original string, the cursor i cannot move to next when one or more matches are found because i already jumps to then end of the match(i += lookAheadMatches), so for loop should be changed to while loop.
Related Issues
Relates to https://github.com/opensearch-project/OpenSearch/issues/7223.
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

This looks like a real bug, not sure why we didn't look at it. Maybe @msfroh?

@gaobinlong Apologies for letting this hang here. I've resolved some CHANGELOG conflicts, but maybe you want to rebase the change?

Both the failed test org.opensearch.persistent.PersistentTasksExecutorFullRestartIT.testFullClusterRestart and org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testUpdateOperations  seem to be flaky tests.

Both the failed test org.opensearch.persistent.PersistentTasksExecutorFullRestartIT.testFullClusterRestart and org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testUpdateOperations  seem to be flaky tests.

Find the GitHub issue for those/open one if it doesn't exist. Force push/rebase to retry gradle checks until a green one.

The flaky tests have related issues: https://github.com/opensearch-project/OpenSearch/issues/5145, https://github.com/opensearch-project/OpenSearch/issues/10026. Now all checks have passed yet.

There was a CHANGELOG conflict, so I resolved it changing the language slightly to "Fix failure in dissect ingest processor parsing empty brackets", lmk if that's incorrect.