python azure-search-documents: Unable to pass vector search field dimensions in JSON

Package Name:  azure-search-documents
Package Version:  11.4.0
Operating System: macOS 14.3.1
Python Version: 3.11.7

Describe the bug
Given an Search Index definition in JSON format with a vector field dimensions defined as follows:
{
    "name": "textEmbedding",
    "type": "Collection(Edm.Single)",
    "searchable": true,
    "filterable": false,
    "retrievable": false,
    "sortable": false,
    "facetable": false,
    "key": false,
    "dimensions": 1536,
    "vectorSearchProfile": "default-vector-profile"
}

When using SearchIndexClient.create_index(), I am getting:
Code: InvalidRequestParameter
Message: The request is invalid. Details: definition : The vector field 'textEmbedding' must have the property 'dimensions' set.
Exception Details:	(InvalidField) The vector field 'textEmbedding' must have the property 'dimensions' set. Parameters: definition
	Code: InvalidField
	Message: The vector field 'textEmbedding' must have the property 'dimensions' set. Parameters: definition

Keyword dimensions is specified in REST API version: 2023-11-01
Workaround
When specifying dimensions using keyword 'vectorSearchDimensions' or 'vector_search_dimensions', the request succeeds without an error.
To Reproduce
Steps to reproduce the behavior:

create JSON file vector-index.json:

{
	"name": "vector-index",
	"fields": [
		{
			"name": "key",
			"type": "Edm.String",
			"key": true,
			"searchable": true,
			"filterable": false,
			"sortable": false,
			"facetable": false
		},
		{
			"name": "textEmbedding",
			"type": "Collection(Edm.Single)",
			"searchable": true,
			"filterable": false,
			"retrievable": false,
			"sortable": false,
			"facetable": false,
			"key": false,
			"dimensions": 1536,
			"vectorSearchProfile": "default-vector-profile"
		}
	],
	"scoringProfiles": [],
	"corsOptions": {
		"allowedOrigins": [
			"*"
		],
		"maxAgeInSeconds": 60
	},
	"vectorSearch": {
		"algorithms": [
			{
				"name": "hnsw-config-1",
				"kind": "hnsw",
				"hnswParameters": {
					"m": 4,
					"efConstruction": 400,
					"efSearch": 500,
					"metric": "cosine"
				}
			},
			{
				"name": "hnsw-config-2",
				"kind": "hnsw",
				"hnswParameters": {
					"m": 8,
					"efConstruction": 800,
					"efSearch": 800,
					"metric": "cosine"
				}
			}
		],
		"profiles": [
		  {
			"name": "default-vector-profile",
			"algorithm": "hnsw-config-1"
		  },
		  {
			"name": "high-vector-profile",
			"algorithm": "hnsw-config-2"
		  }
		]
	}
}

Execute following code:

from azure.search.documents import SearchClient
from azure.search.documents.indexes import SearchIndexClient

api_version="2023-11-01"
file_path="vector-index.json"

with open(file_path, "rt") as f:
    data = json.load(f)

index = SearchIndex.from_dict(data=data)

with SearchIndexClient(
    endpoint=service_endpoint,
    credential=credential,
    api_version=api_version
) as client:
    result = client.create_index(index)

Expected behavior
'dimensions' property is correctly accepted
Additional context
The _attribute_map of the class SearchField wrongly references attribute "vector_search_dimensions" instead of just "dimensions" as found in stable API version documentation.

Thank you for the feedback @peto-ivanov . We will investigate and get back to you asap.

The fix is merged and will be available in next release.


In awq_int4_group_128  mode, why is the weight converted into int8 after rounding to [-8,7]?

When building AWQ_int4_group_128 engine, the code here seems to convert the weights which are already rounded to [-8,7] into int8, using  the following two command defined [here] and here.
packer = torch.ops.trtllm.pack_int8_tensor_to_packed_int4
preprocessor = torch.ops.trtllm.preprocess_weights_for_mixed_gemm

int4_weight = preprocessor(packer(qweight_int8.cpu()), torch.quint4x2)

Isn't this INT4 weight quantization? Why is int8 engaged here? This is confusing to me.

Looks like we pack 2 int4 weights into one int8 number.

@brisker Do you still have the question? If not, we will close it soon.


gam.coef_ shape not matching documentation description

Hi @dswah,
thank you for this great package!
According to the documentation, the gam.coef_ matrix should have a shape that is (n_samples, m_features). However, in my case the gam.coef_ is a 1-d array with a completely different size.
Am I missing something or is there an error somewhere?

hey @zmcode,
oh wow that does seem wrong! thanks for pointing that out.
the shape of the gam. coef_ should be a vector of length:
(intercept==True) + n_splines_feature_1 + n_splines_feature_2 + ...+ n_splines_feature_n
does that match what you're seeing?
-dani

I am using a LinearGAM() with default parameters, so n_splines should be 25.
Each entry in my dataset has 6 features and intercept is set to True.
So if I am understanding your definition correctly, the length of gam.coef_ should be 151 but len(gam.coef_) outputs 132.

ok cool. this is good information.
pyGAM also tries to automatically infer if you have any categorical feature(s) and will use one indicator feature for each category.
could you check gam.dtypes_ for your fitted model? it should return a list with the inferred data type for each feature.

Yep I have two categorical features, the content of gam._dtype is
['categorical',
 'categorical',
 'numerical',
 'numerical',
 'numerical',
 'numerical']

alright. that makes some sense.
i forgot that you can check the number of splines per feature by inspecting gam._n_splines. this should help you decide if the number of categories is appropriate for your data.
if instead you want to force pyGAM to use numerical features, you can start your LinearGAM with dtype="numerical" to set all features at once, or specify a list with entries per feature like dtype=["numerical", "categorical", ...]

I have checked the gam._n_splines attribute and it confirms the output of len(gam.coef_) as well as being appropriate for my data. Thank you for your help :)

cool :)


can't edit the node

After i installed the longhorn from the catalog ,i can't edit the node.

Version: v0.6.2

Can you elaborate the reproduce steps?

i installed the longhorn from the catalog, and this is my settings

I meant, when you said can't edit the node, what operation you've taken and what's the response of the UI? For example, did you mean clicking node page has no response inside Longhorn UI? or clicking edit node has no response inside Longhorn UI? Or edit node has no response for Rancher UI?

i found no button in the page to edit


How can I scroll to X element onload?

For example my goal is to have
example.com/page/element -> redirect to example.com/page and scroll to element
I do not want to use #links

Hashes are what browsers invented for this exact behavior, it's definitely the way to go for this kind of behavior.
Please post questions on https://spectrum.chat/next-js.


$#target

Maybe add that handy exception? Returning a single element.
Too frequent use-case, can't find somebody expecting list as result here. Inconsistency, though, yes. Also - not real live list in result.

Nope, window already exposes id elements.


Support for UTorrent web api

Since Utorrent is still the most popular torrent client, adding support seems like a good idea

Feature has been implemented. Will create pull request after python 3 is merged.


OTTF sival library + example

This PR does several things:

modify the test framework status so that it can call a custom abort function
modify ottf to override the status abort function so it can report status in all case and run the debugger
implement a ujson debugger that is called when a test passes or failed, this debugger accepts the memory commands
the debugger also has an exit command to exit the loop
a test can use the OTTF_DEBUG_UNTIL macros to call the debugger and wait until a condition is true, for example OTTF_DEBUG_UNTIL(kPhase != kWaitHost1);
there is an example to put everything together, the device having four phases that require host intervention

Run with
./bazelisk.sh test --test_output=streamed --cache_test_results=no //sw/device/tests:example_sival_fpga_cw310_test_rom

Further thoughts:

If convenient, we could extend ottf_debugger to take a function pointer to handle custom commands while in debugger mode. This could be convenient for tests that requires more complex interactions and where maybe poking at many registers and memory is not ideal.

NOTE:
The whole check, status, ottf_main situation is a mess, this PR maybe makes it worse. I don't think it's right that the status library should abort on test_status_set(kFailed) since this is a DV-only status reporting functionality. Ideally, we would want a unified framework to wait for the host to do something, remove test_status entirely, make sure that only check can abort and when that happens, it call into ottf.

Can we merge this or are there are any more changes to do?


doc: issue #17 added the description of the algorithm

I wrote the description of the algorithm. That includes the explanations about bitmasking and the DP formula

Looks good.


Support upgrades and consul service registration (bis)

Pull Request (PR) description
This PR adds the changes we made from the jsok repo.
This is a new version of PR #7 because acceptance tests were failing.
This Pull Request (PR) fixes the following issues
n/a

Thanks @jonasdemoor  ;-)


SOFTReopenDevice#alcReopenDeviceSOFT doesn't allow null deviceName

Version
3.3.2 (nightly)
Platform
macOS arm64
JDK
graalvm 22.2 Java 11
Module
OpenAL
Bug description
The function SOFTReopenDevice#alcReopenDeviceSOFT should accept a null deviceName as parameter, as it is described  in the OpenAL-soft docs https://openal-soft.org/openal-extensions/SOFT_reopen_device.txt.
However the source looks like this:
    public static boolean alcReopenDeviceSOFT(@NativeType("ALCdevice *") long device, @NativeType("ALCchar const *") ByteBuffer deviceName, @Nullable @NativeType("ALCint const *") IntBuffer attribs) {
        if (CHECKS) {
            checkNT1(deviceName);
            checkNTSafe(attribs);
        }
        return nalcReopenDeviceSOFT(device, memAddress(deviceName), memAddressSafe(attribs));
    }

However it should be:
    public static boolean alcReopenDeviceSOFT(@NativeType("ALCdevice *") long device, @NativeType("ALCchar const *") ByteBuffer deviceName, @Nullable @NativeType("ALCint const *") IntBuffer attribs) {
        if (CHECKS) {
            checkNT1Safe(deviceName);
            checkNTSafe(attribs);
        }
        return nalcReopenDeviceSOFT(device, memAddressSafe(deviceName), memAddressSafe(attribs));
    }

Calling the nalc method directly with SOFTReopenDevice.nalcReopenDeviceSOFT(device, memAddressSafe((ByteBuffer)null), memAddressSafe((IntBuffer)null))
works as expected.
Stacktrace or crash log output
Caused by: java.lang.NullPointerException
	at org.lwjgl.system.Checks.checkNT1(Checks.java:226)
	at org.lwjgl.openal.SOFTReopenDevice.alcReopenDeviceSOFT(SOFTReopenDevice.java:57)
	... 18 more

or when disabling checks:
Caused by: java.lang.NullPointerException
	at org.lwjgl.system.MemoryUtil.memAddress(MemoryUtil.java:737)
	at org.lwjgl.openal.SOFTReopenDevice.alcReopenDeviceSOFT(SOFTReopenDevice.java:60)
	... 18 more

Thank you @Berstanio!


Completion rewrite

resolves #91

Woahh this looks interesting, I'm looking forward to seeing this land.

Thanks! What about it specifically, if you don't mind?

Just reading through the commit messages it looks like a lot of QOL features and stability is being added. Things like that are always worth celebrating imo


Task 522 News Editorials

From paper https://aclanthology.org/2020.coling-main.470.pdf
(I made a mistake and created this branch from another branch instead of the master, so I have commits from other tasks here. sorry)

@gkaramanolakis wondering if you can help review this PR?

This PR contains two tasks: 521 and 522. I see that task 521 is reviewed separately at #263, so I will review task 522.
Task 522 looks good but quite hard, so below are a few comments attempting to make it a bit easier.
In the task definition, could you copy the requirements for the summaries as they are stated in the paper? i.e., replace "concise, self-contained, persuasive, and useful for others" with the following: "thesis-indicative, persuasive, reasonable, concise, and self-contained" (except if I am missing something from the task definition/instructions).
The paper provides more instructions for the annotators, which I believe should be included in the task definition, otherwise, the task is under-constrained and hard to address automatically. Here is an example of additional instructions mentioned in the paper: "Summary length was limited to be 20% of an editorial’s segments. In many editorials, the thesis may not be explicitly stated but rather implied by the author. For this reason, we allowed up to two segments to be labeled as thesis"
Do you think it makes sense to remove the "justification" part of the output summary and keep just the "thesis" part? If not, then I would suggest adding a few more negative examples to indicate the expected output format, e.g., an output without a "justification" field and an explanation mentioning that the output is wrong.
Alternatively, could "justification" and "thesis" be merged into a single output? Given both "justification" and "thesis" fields, we should construct a special evaluation function just for this task, as generation metrics like BLUE cannot be directly applied to the outputs.
Hope this helps, and pls lmk if anything is unclear.

@gkaramanolakis Thanks for the review! I will update the task.

So I did what you suggested, and removed the justification, as it didn't have a good agreement between annotators. Can you check the task again? Thanks.

So I removed the "thesis:" from outputs, but for the second point, I don't know which ones I should keep because all of them have the maximum IAA score.

So I removed the "thesis:" from outputs, but for the second point, I don't know which ones I should keep because all of them have the maximum IAA score.

Thanks for addressing the first comment! Regarding the second comment, I am also not sure about what selection criterion to use and couldn't find any paper that uses this dataset to train models. Everything else looks good to me, so if @danyaljj agrees we can commit the task as is. Thanks!

So I removed the "thesis:" from outputs, but for the second point, I don't know which ones I should keep because all of them have the maximum IAA score.

Thanks for addressing the first comment! Regarding the second comment, I am also not sure about what selection criterion to use and couldn't find any paper that uses this dataset to train models. Everything else looks good to me, so if @danyaljj agrees we can commit the task as is. Thanks!

Yeah, it is fine.
One more:  for task521_trivia_question_classification, clarify whether we can have more than one category for one input or not.

@danyaljj Sorry it was my mistake to include the file for task 521 in this PR. I updated the task in its original PR #263  and merged it onto this branch. So I think it'll suffice to just merge this PR into master.

Looks good to me! Leaving it for @swarooprm to review before merging.


Template validation failed. The  template deployment failed because of policy violation.

Received  the below mentioned error message, during the AMS deployment validation. Unable to view " details for more information"
Template validation failed. The  template deployment failed because of policy violation. Please see details for more information.

Hey @sathya7474 , Can you share some more details like CorrelationID ?

Hi,
I received only the below mentioned message without any id.
@.***
With Regards,
Sathya
From: amitms2103 @.>
Sent: Thursday, April 21, 2022 11:07 AM
To: Azure/Azure-Monitor-for-SAP-solutions-preview @.>
Cc: Sathyanarayanan Muthukrishnan (external) @.>; Mention @.>
Subject: Re: [Azure/Azure-Monitor-for-SAP-solutions-preview] Template validation failed. The template deployment failed because of policy violation. (Issue #19)
Hey @sathya7474https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsathya7474&data=05|01|Sathyanarayanan_Muthukrishnan%40swissre.com|a8bafdb4a76344357c5108da2359067b|45597f606e374be7acfb4c9e23b261ea|1|0|637861162550587032|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=LqgmCHNbJ%2BJDICDHfPu15KkG7Y83rF8ESQ9SKkxBD2Q%3D&reserved=0 , Can you share some more details like CorrelationID ?

Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FAzure-Monitor-for-SAP-solutions-preview%2Fissues%2F19%23issuecomment-1104732083&data=05|01|Sathyanarayanan_Muthukrishnan%40swissre.com|a8bafdb4a76344357c5108da2359067b|45597f606e374be7acfb4c9e23b261ea|1|0|637861162550587032|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=%2BeMFIMhzIACvfyMs%2FDGP8%2BkNnBmJ9CSS4t4G52yrjsw%3D&reserved=0, or unsubscribehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAY2MR3F5SGFHCA4B33YLNCLVGDSRRANCNFSM5T6B5TYA&data=05|01|Sathyanarayanan_Muthukrishnan%40swissre.com|a8bafdb4a76344357c5108da2359067b|45597f606e374be7acfb4c9e23b261ea|1|0|637861162550587032|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=4TwJzkbAX1DLp9agVGU9ESXBL%2FeA66E2%2Fm54hRZeVN0%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>This e-mail, including attachments, is intended for the person(s) or company(s) named and may contain confidential and/or legally privileged information. Unauthorized disclosure, copying or use of this information may be unlawful and is prohibited. If you are not the intended recipient, please delete this message and notify the sender. All incoming and outgoing e-mail messages are stored in the Swiss Re Electronic Message Repository. If you do not wish the retention of potentially private e-mails by Swiss Re, we strongly advise you not to use the Swiss Re e-mail account for any private, non-business related communications.

Can you share the name of the resource you were trying to create? ?

Hi,
Please find the below screenshot for the same.
@.***
With Regards,
Sathya
From: amitms2103 @.>
Sent: Thursday, April 21, 2022 4:51 PM
To: Azure/Azure-Monitor-for-SAP-solutions-preview @.>
Cc: Sathyanarayanan Muthukrishnan (external) @.>; Mention @.>
Subject: Re: [Azure/Azure-Monitor-for-SAP-solutions-preview] Template validation failed. The template deployment failed because of policy violation. (Issue #19)
Can you share the name of the resource you were trying to create? ?

Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FAzure-Monitor-for-SAP-solutions-preview%2Fissues%2F19%23issuecomment-1105079818&data=05|01|Sathyanarayanan_Muthukrishnan%40swissre.com|1161d089bd924f3f0bed08da238911e9|45597f606e374be7acfb4c9e23b261ea|1|0|637861368893861056|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=5GjJw8w%2FGwo3MLxNLeKKlGidZiNHylcMe%2FoeIZ22270%3D&reserved=0, or unsubscribehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAY2MR3EB556GGVPHSBS4XR3VGE23FANCNFSM5T6B5TYA&data=05|01|Sathyanarayanan_Muthukrishnan%40swissre.com|1161d089bd924f3f0bed08da238911e9|45597f606e374be7acfb4c9e23b261ea|1|0|637861368893861056|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Kvn1xbE9v2EGxJQiGnEXRP54MP0oFkJ2y%2FdvEvGbJYU%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>This e-mail, including attachments, is intended for the person(s) or company(s) named and may contain confidential and/or legally privileged information. Unauthorized disclosure, copying or use of this information may be unlawful and is prohibited. If you are not the intended recipient, please delete this message and notify the sender. All incoming and outgoing e-mail messages are stored in the Swiss Re Electronic Message Repository. If you do not wish the retention of potentially private e-mails by Swiss Re, we strongly advise you not to use the Swiss Re e-mail account for any private, non-business related communications.

@sathya7474, I do not see any screenshots.
You can try attaching it in GitHub directly.

Reopening it.

Hi All,
We are waiting for your update. If required, we are ready to setup a meeting with you. I will be available until 9 PM IST.
With Regards,
Sathya
From: archanak-msft @.>
Sent: Tuesday, April 26, 2022 11:46 AM
To: Azure/Azure-Monitor-for-SAP-solutions-preview @.>
Cc: Sathyanarayanan Muthukrishnan (external) @.>; State change @.>
Subject: Re: [Azure/Azure-Monitor-for-SAP-solutions-preview] Template validation failed. The template deployment failed because of policy violation. (Issue #19)
Reopening it.

Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FAzure-Monitor-for-SAP-solutions-preview%2Fissues%2F19%23issuecomment-1109387619&data=05|01|Sathyanarayanan_Muthukrishnan%40swissre.com|86375874c78b47723ea108da274c2dda|45597f606e374be7acfb4c9e23b261ea|1|0|637865505404602293|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=8uiC8MQenyhVipJdBt868bA8h3W%2Fpx8d5Ysl1iAiAiE%3D&reserved=0, or unsubscribehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAY2MR3AQUUI3B6GV4MI3XDLVG6CYPANCNFSM5T6B5TYA&data=05|01|Sathyanarayanan_Muthukrishnan%40swissre.com|86375874c78b47723ea108da274c2dda|45597f606e374be7acfb4c9e23b261ea|1|0|637865505404602293|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=gg6%2Fs418q%2FFszAJ85o%2FzHBNNS3pWe%2F%2BRieGiFU1Hvfk%3D&reserved=0.
You are receiving this because you modified the open/close state.Message ID<EMAIL_ADDRESS>This e-mail, including attachments, is intended for the person(s) or company(s) named and may contain confidential and/or legally privileged information. Unauthorized disclosure, copying or use of this information may be unlawful and is prohibited. If you are not the intended recipient, please delete this message and notify the sender. All incoming and outgoing e-mail messages are stored in the Swiss Re Electronic Message Repository. If you do not wish the retention of potentially private e-mails by Swiss Re, we strongly advise you not to use the Swiss Re e-mail account for any private, non-business related communications.

Hi @sathya7474 ,
Thanks for the ping. We are looking into this and one of my team members will share the detailed analysis shortly.

Azure Policy enforces organization standards and check compliance of resources.
Based on the information, there seems to be a Azure Policy Definition which allows only App Service Plan with specific tiers among the available tiers ( Free ,Shared (preview) ,Standard, Premium, PremiumV2, PremiumV3, Isolated). Kindly check the allowed tiers in your subscription. For more information , on how to check tiers allowed, refer doc
It can also happen for any other resource which AMS v2 uses. Try to check this, otherwise we can get on the call to resolve this.

Hi,
Shall we connect today to isolate the issue? I will be available until 9:00 PM IST. Kindly send a meeting request for it.
We are unable to find the exact blocker.
With Regards,
Sathya
From: Basant2619 @.>
Sent: Thursday, April 28, 2022 11:09 PM
To: Azure/Azure-Monitor-for-SAP-solutions-preview @.>
Cc: Sathyanarayanan Muthukrishnan (external) @.>; Mention @.>
Subject: Re: [Azure/Azure-Monitor-for-SAP-solutions-preview] Template validation failed. The template deployment failed because of policy violation. (Issue #19)
Azure Policy enforces organization standards and check compliance of resources.
Based on the information, there seems to be a Azure Policy Definition which allows only App Service Plan with specific tiers among the available tiers ( Free ,Shared (preview) ,Standard, Premium, PremiumV2, PremiumV3, Isolated). Kindly check the allowed tiers in your subscription. For more information , on how to check tiers allowed, refer dochttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-resource-manager%2Ftroubleshooting%2Ferror-policy-requestdisallowedbypolicy&data=05|01|Sathyanarayanan_Muthukrishnan%40swissre.com|2ff3a7aac651453d9f2408da293e011b|45597f606e374be7acfb4c9e23b261ea|1|0|637867643573689194|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Z0wI5yeqbTTi6Oad%2Ftx79CdRtU9gbnTMIUC0DDSrjsQ%3D&reserved=0
It can also happen for any other resource which AMS v2 uses. Try to check this, otherwise we can get on the call to resolve this.

Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FAzure-Monitor-for-SAP-solutions-preview%2Fissues%2F19%23issuecomment-1112487596&data=05|01|Sathyanarayanan_Muthukrishnan%40swissre.com|2ff3a7aac651453d9f2408da293e011b|45597f606e374be7acfb4c9e23b261ea|1|0|637867643573689194|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=t%2BZzXA3orqi4mmSFsuV8SBdOpLRInLkIcl2GnE0NWJ8%3D&reserved=0, or unsubscribehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAY2MR3D2VTBO2AZUOZ4FBKLVHLEL3ANCNFSM5T6B5TYA&data=05|01|Sathyanarayanan_Muthukrishnan%40swissre.com|2ff3a7aac651453d9f2408da293e011b|45597f606e374be7acfb4c9e23b261ea|1|0|637867643573689194|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=hMB4KCa6lAX%2Fmu4KAVLYt2TLnB43PxHTZ9h%2BWklaxDg%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>This e-mail, including attachments, is intended for the person(s) or company(s) named and may contain confidential and/or legally privileged information. Unauthorized disclosure, copying or use of this information may be unlawful and is prohibited. If you are not the intended recipient, please delete this message and notify the sender. All incoming and outgoing e-mail messages are stored in the Swiss Re Electronic Message Repository. If you do not wish the retention of potentially private e-mails by Swiss Re, we strongly advise you not to use the Swiss Re e-mail account for any private, non-business related communications.

Hi,
Uploaded the attached file.
With Regards,
Sathya
From: amitms2103 @.>
Sent: Thursday, April 21, 2022 6:09 PM
To: Azure/Azure-Monitor-for-SAP-solutions-preview @.>
Cc: Sathyanarayanan Muthukrishnan (external) @.>; Mention @.>
Subject: Re: [Azure/Azure-Monitor-for-SAP-solutions-preview] Template validation failed. The template deployment failed because of policy violation. (Issue #19)
@sathya7474https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsathya7474&data=05|01|Sathyanarayanan_Muthukrishnan%40swissre.com|b023abc4923c486bbc8808da2393d884|45597f606e374be7acfb4c9e23b261ea|1|0|637861415174589965|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=HJwrEklyU9W1TffuzfoJJRaE4WJMFGyuPu%2B9ywhgZAQ%3D&reserved=0, I do not see any screenshots.
You can try attaching it in GitHub directly.

Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FAzure-Monitor-for-SAP-solutions-preview%2Fissues%2F19%23issuecomment-1105157742&data=05|01|Sathyanarayanan_Muthukrishnan%40swissre.com|b023abc4923c486bbc8808da2393d884|45597f606e374be7acfb4c9e23b261ea|1|0|637861415174589965|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=i%2F6D6mxcCT7qf6frdPfItAtcQ4FGzhysi%2BqW6nuzPuo%3D&reserved=0, or unsubscribehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAY2MR3EET7CDCYCFF6AUIWDVGFD4PANCNFSM5T6B5TYA&data=05|01|Sathyanarayanan_Muthukrishnan%40swissre.com|b023abc4923c486bbc8808da2393d884|45597f606e374be7acfb4c9e23b261ea|1|0|637861415174589965|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=wNPiglpQpIfuU5juyjBAcwPUx%2FTfL2s%2F9P8ftsMVuwQ%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>This e-mail, including attachments, is intended for the person(s) or company(s) named and may contain confidential and/or legally privileged information. Unauthorized disclosure, copying or use of this information may be unlawful and is prohibited. If you are not the intended recipient, please delete this message and notify the sender. All incoming and outgoing e-mail messages are stored in the Swiss Re Electronic Message Repository. If you do not wish the retention of potentially private e-mails by Swiss Re, we strongly advise you not to use the Swiss Re e-mail account for any private, non-business related communications.


Add support for BedMachine Greenland

By analogy of Antarctica.

https://doi.org/10.1002/2017GL074954
https://nsidc.org/data/idbmg4/versions/5

Here the file https://n5eil01u.ecs.nsidc.org/ICEBRIDGE/IDBMG4.005/1993.01.01/BedMachineGreenland-v5.nc
(needs earth data login)


License

Hey, nice work! Before people invest more energy, they usually take a look at the license.
E.g. Linux support or emscripten etc. using Gamepad API etc.
Do you mind to pick a license?

Sure thing, added MIT license.


Add Polars blog post by Itamar

Link to suggestion
https://pythonspeed.com/articles/polars-exploratory-data-analysis-vs-production/
Targeted section
Blog posts
Describe your suggestion

Polars for initial data analysis, Polars for production - A blog post that shows how to use Polars for initial data analysis and then effectively in production by @itamarst.

Checklist

[X] checked if your suggestion is not already listed in Awesome Polars list.
[X] checked if it can fit in an existed section or suggest a new section and explain why your item does not fit into one and what would be the interest of your new section.
[X] checked when it's a repository if it's maintained (archived repository will be rejected).

Thanks!


Production build fails when dev build succeeds.

Describe the bug
Optional chaining works as intended in development, however the terser plugin throws an error in production build.
Reproduction
https://github.com/reed-jones/vite-optional-chaining-repro
yarn dev # works
yarn build # fails

System Info

required vite version: 0.20.8
required Operating System: 10.14.6
required Node version: v14.4.0
Optional:

yarn version: 1.22.4
Installed vue version (from yarn.lock or package-lock.json) 3.0.0-beta.15
Installed @vue/compiler-sfc version: '3.0.0-beta.15'

Logs (Optional if provided reproduction)

Run vite or vite build with the --debug flag.
Provide the error log here.

Building for production...
  vite:build:resolve /favicon.ico --> /Users/......../optional-chaining-repro/public/favicon.ico +0ms
  vite:build:resolve /src/main.js --> /Users/......../optional-chaining-repro/src/main.js +0ms
  vite:build:asset /Users/......../optional-chaining-repro/public/favicon.ico -> /favicon.ico +0ms
  vite:build:asset /Users/......../optional-chaining-repro/src/assets/logo.png -> /_assets/logo.e327c6ba.png +333ms
  5187 |
  5188 | const failed = {};
> 5189 | console.warn(failed?.will?.not?.have?.an?.issue?.in?.dev ?? 'but will fail in production');
       |                    ^ Unexpected token: punc (.)
  5190 |
  5191 | createApp(script$1).mount('#app');
[vite] Build errored out.
Error [SyntaxError]: Unexpected token: punc (.)
   at ee (/Users/......../optional-chaining-repro/node_modules/terser/dist/bundle.min.js:1:19541)
    //
    // .. more lines cut
    //
    at qe (/Users/......../optional-chaining-repro/node_modules/terser/dist/bundle.min.js:1:50653) {
  type: 'Q',
  filename: '0',
  line: 5734,
  col: 11,
  pos: 207945,
  code: 'PLUGIN_ERROR',
  plugin: 'terser',
  hook: 'renderChunk'
}

The optional chaining can work in dev, because the js file isn't compiled in dev and  the browser support this feature.
If you want use this advance js feature, you can add customer transform plugin for this.
See similar example in https://github.com/vitejs/vite/blob/master/playground/plugins/jsPlugin.ts.


#US 13 As a returning customer, I want to make a new reservation

As a returning customer, I want to make a new reservation


Minimize and close window control layout

Hi there Adwaita for Steam devs, could you add the minimize and close on the right button layout to the skin? although I love the default GNOME way of doing things I am a fervent lover of the vanilla plus conept, I usually use Dash to dock + Blur my shell + minimize button to get the most complete version of the vanilla UX while still having nice things

Could this be done?

How are you installing the skin and are you using the latest version?
Adwaita for Steam v3.0 or later supports custom button layouts and should read your current layout from system settings by default.
If installer can't read your layout for some reason, use --windowcontrols-layout :minimize,close option to get the layout you want.
If you're using AdwSteamGtk, it should also support new layout options and it should read your system settings, but I don't think it exposes an option to use a custom layout.

Thanks, it even worls on AdwSteamGtk if you allow it to access user configs on Flatseal, I suggest you adding a small explanation on your read me or flathub page

AdwSteamGtk should also read settings using the desktop portal. Looks like a bug, report it to AdwSteamGtk if it doesn't work or requires additional permissions on your system.

Not a bug, what I meant is... You said

If you're using AdwSteamGtk, it should also support new layout options and it should read your system settings, but I don't think it exposes an option to use a custom layout.

I was only telling you it does and it is exposed as auto, I just exposed the settings via Flatseal

AdwSteamGtk should read settings through the portal without having to expose anything manually and without any additional permissions. If it can't read settings after installing it's probably still a bug.


Check if a widget is focused from within the widget

I'm trying to make a privacy browse as my first Flutter app. I've finished designing the layout, look, and everything else of the app. But as you know, many pages redirect the user to other pages. This is why I want to check if the TextField (the one that you use to go to a URL, or search DuckDuckGo) is focused, and if it isn't, I need to get WebViewController.currentUrl() and set TextEditingController.text to the current URL. But how do I check if the TextField (I've created a stateful widget called AddressTextField for this) is focused from within the AddressTextField class (this is the only class that has access to the TextEditingController)?

Hi @Python3-8
You should use the FocusNode API for this, see https://flutter.dev/docs/cookbook/forms/focus.
It seems you are asking for assistance on personal code. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


[💡 FEATURE REQUEST]: Driver in the queue task

Plugin
JOBS
I have an idea!
When RR sends a task to an application, the task contains body, header, eos.
The header array contains information about the job: id, job, pipeline...
It would be great to have the driver in the header array. Tasks from some drivers may have additional information. For example, Kafka driver tasks additionally receive fields in the header: topic, partition, offset. It would be great to have a driver value in the received data to understand what data structure needs to be processed on the PHP side. Thanks.

RR will return the following driver's names:

memory
kafka
amqp
beanstalk
sqs
nats

Done


[REQUEST] Is the cuda unified memory technology used in deepspeed? Where is its API?

such as that title, Is the cuda unified memory technology used in deepspeed? Where is its API?

No, cuda unified memory is not used in deepspeed.

@tjruwase Thank you for solving the puzzle. There are two questions:

What are the heterogeneous memory optimizations performed by DeepSpeed? Which of the following APIs is used?
2, Does it provides the
GPU memory swapping mechanism with the CPU main memory ? What is this mechanism like? What about APIs?


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_0941mkpima/clone/recipe/meta.yaml:17: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_0941mkpima/clone/recipe/meta.yaml:23: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_0941mkpima/clone/recipe/meta.yaml:31: missing_pip_check: For pypi packages, pip check should be present in the test commands
INFO: /tmp/abs_0941mkpima/clone/recipe/meta.yaml:54: invalid_url: https://crochet.readthedocs.org/ : URL domain redirect crochet.readthedocs.org ->  crochet.readthedocs.io
Errors were found


Update Hackage and remove a few unneeded constraints

In particular, thanks to the recent release of monoidal-containers,
we now build with aeson 2.

Pre-submit checklist:

Branch

[ ] Tests are provided (if possible)
[ ] Commit sequence broadly makes sense
[ ] Key commits have useful messages
[ ] Relevant tickets are mentioned in commit messages
[ ] Formatting, materialized Nix files, PNG optimization, etc. are updated

PR

[ ] Self-reviewed the diff
[ ] Useful pull request description
[ ] Reviewer requested

Ah no, we can't currently do aeson-2 thanks to cardano-crypto-class.

I had to insert a few gross shims in our gross object manipulation stuff, and fix cardano-base, but it works now!


Duplicate paired controller ID?

I had been running a light strip with HS 2.0.0r1 for 45+ days with no issues, no reboot, no power loss, no hand, perfectly stable.
Then it started showing non-responsive, and/or taking ~30 seconds to respond, even though I have my router set to disable mesh routing & force this device to remain connected to a specific AP.
Disconnecting from power and connecting to laptop's USB, all seemed "normal".
I checked both of my AppleTV (gen3 and gen4), both updated to AppleTV OS 18.1.
Then I noticed in the Home.app that in Home Settings, Home Hubs and Bridges, it was set to "Automatic selection". I forced it to my gen4, then the strip started working fine again. But looking at "Connection Info" in HomeSpan CLI, it currently show two admin clients with the same controller ID.
*** HomeSpan Status ***

IP Address:        192.168.xx.xx
Web Logging:       http://mezzanine.local:80/status

Accessory ID:      1A:72:86:5C:D4:C2                               LTPK: FB664AC0ADD8F6A295FFF46B5B5F0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Paired Controller: F39B0A91-0F77-4889-AE9F-C942A1E6E9FE   (admin)  LTPK: 86ED9F58BF4CDB23D76088FC6A7BCxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Paired Controller: E66112C1-2B7E-48DC-9FB8-B1B6D7CE235E   (admin)  LTPK: 4D5FBF74118F779740C91FC21CF88xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Paired Controller: 2B9A4486-CC18-44B8-BEB0-5AC2BCD5B3CB (regular)  LTPK: EF883D81C9157772D5982EA2908E3xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Client #5: 192.168.xx.105  ID=E66112C1-2B7E-48DC-9FB8-B1B6D7CE235E   (admin)
Client #2: 192.168.xx.104  ID=E66112C1-2B7E-48DC-9FB8-B1B6D7CE235E   (admin)

*** End Status ***

Is this normal?

Yes, multiple clients can use the same controller IDs. Apple does not provide any docs on how or when it uses different clients to connect to a device.

So when HS needs to notify controllers, do you notify "by controller ID", or by client IP connected and not really use ControllerID ?

Controller ID is only used to verify a connection when first made (you can see this in the Log files).  Once a socket connection has been verified the Controller ID is no longer used during normal communication.  Notifications are sent to all open socket connections (without regard to the Controller ID), if that socket connection has subscribed to notifications for any given service/characteristic.

Anything more on this, or can I close?

Things seems to have been somewhat stabilized for a while. ok to close, and I will update to the most recent release. I wonder if I will still have to move the #include <DNSServer.h> to HomeSpan.cpp to get things to compile with PIO, but that is a separate topic.


small fixes to integrate with new metadata appending scheme

Sending contract one event at a time, rather than all of funder metadata, as per this contract PR

merged here


Build Windows V1 and V2 runtimes always

Signed-off-by: Justin Terry (VM<EMAIL_ADDRESS>

Codecov Report

Merging #2761 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2761   +/-   ##
=======================================
  Coverage   43.72%   43.72%
=======================================
  Files         100      100
  Lines       10734    10734
=======================================
  Hits         4693     4693
  Misses       5311     5311
  Partials      730      730

Flag
Coverage Δ

#linux
47.39% <ø> (ø)
:arrow_up:

#windows
40.91% <ø> (+0.02%)
:arrow_up:

Continue to review full report at Codecov.

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

@crosbymichael - You ok with this? I will rebase #2756 when done

LGTM


Support Docker private images on docker hub

Is there a plan to support these types of images? Or is there already a way to pull those that I've missed?
Thanks,
Yaron.

Could you please elaborate what is missing now to have this feature
supported?
Best regards,
Eugene Petrenko
On Wed, Feb 22, 2017 at 3:33 PM, Yaron Idan<EMAIL_ADDRESS>wrote:

Is there a plan to support these types of images? Or is there already a
way to pull those that I've missed?
Thanks,
Yaron.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jonnyzzz/TeamCity.Virtual/issues/52, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAPpr7ScCLy-r8QOXwYCxWrL4v95D3xVks5rfEclgaJpZM4MItzz
.

@yaron-idan are you talking about authorization?

Indeed.
I'm guessing I could add a command line step before the pull command in which I run docker login but would prefer a way to authorize the plugin (using .dockercfg or similar methods).

Since authenticating using docker login as a previous step/any other authentication method works for pulling private images, I'm gonna go ahead and close this issue.


TypeError (no implicit conversion of nil into String):

SDK Version 0.20
payload = {
:referenceId => "34",
:type => "business",
:name => "Adams Company",
:firstName => "fish",
:lastName => "frako",
:email =><EMAIL_ADDRESS>:address => {
:street1 => "123 Main Street",
:street2 => "",
:postalCode => "53719",
:city => "Madison",
:country => "US",
:region => "Wisconsin",
:phone => "123-123-1234"
},
:payout => {
"accountNum" => "123",
"branchId" => "123",
"type" => "bank-transfer",
"currency" => "USD",
"country" => "US",
"accountHolderName" => "fish frako"
}
}
result = client.recipient.update(payment_rails_id, payload)
Error message TypeError (no implicit conversion of nil into String):

Can't reproduce this with the same payload. Can you provide more context (payment_rails_id, ruby version, etc)?
Also worth noting that :payout => Object is not a recognized part of the recipient update body. You'll have to use client.recipient_account.(create or update) to manipulate payout methods directly.
However, when creating a recipient (client.recipient.create) you can attach an :account => Object value, in place of your :payout one, and it will create a recipient with that payout method so long as the account information is correct.

Thanks for the clarification.  You have some old documentation with that "payout" object specified
https://docs.paymentrails.com/api/#recipient-attributes
:payment_rails_id => "R-RSDftzRsEs2ppky25vNDSu"
Ruby 2.5.3
Rails 5.2.1
Thanks

Documentation updated ;)

That wasn't the issue as im still getting this error

Hmm.. I've copied your exact payload and am having no issues (other using Ruby 2.5.3. Try uninstalling the paymentrails gem and reinstalling it (maybe version is cached)


[to be merged after #1791 - #1794] Gen5 instance types with enhanced networking

Fix AMP-133 (enable enhanced networking)
Fix AMP-99 (enable gen5 instance types: m5 and c5)

To be rebased once #1791, #1792, #1793 and #1794 are merged, and AMI should be rebuilt.
Verification
create a cluster on AWS (see https://github.com/appcelerator/amp/wiki/Deploy-a-dev-cluster-on-AWS) with default settings (means: m5.large instances).
Connect to an instance and run ethtool -i eth0, it should display driver: ena and not driver: vif.

superseded by #1802


Time drift in virtual machine causing TLS: AuthFailure with amazonec2 driver

I use a long running Linux VM for development.   For a few days after a restart, docker-machine works flawlessly.   Then suddenly, docker-machine would fail to connect to the instance with a TLS: AuthFailure.   After debugging for awhile, I noticed that my clock had drifted about 5 minutes from real time and AWS I believe uses the current time as part of the authentication process.   I installed ntp to keep my time in sync and resolved the issue, but it may be useful to display a warning message if possible when local time has drifted too far from real time.

Is the VM managed by Docker Machine or other software?

As you noted, proper use of ntp is the correct fix here.  Would be happy to merge in a PR that suggested clock skew as one reason AWS calls might be failing though.

I can do that.  Where in the docs should this go?
On Fri, Jul 8, 2016 at 1:14 PM Nathan LeClaire<EMAIL_ADDRESS>wrote:

As you noted, proper use of ntp is the correct fix here. Would be happy to
merge in a PR that suggested clock skew as one reason AWS calls might be
failing though.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/docker/machine/issues/3574#issuecomment-231417735,
or mute the thread
https://github.com/notifications/unsubscribe/ABW4EgWZeLhRwcMk_ZTPi5onv-lcHSQzks5qToVYgaJpZM4JHqAh
.

Oh, I meant in the amazonec2 driver code.  Basically if an error of that type occurs we could be more helpful suggesting clock skew as a suspect.


Refact on HTTP POST on Point

Background
To parse Point body on HTTP, we currently have 2 options:

Use JSON
Use Line-Protocol

The JSON way that can't show all info about the point, especially the field. Currently, field are dynamic-typed and got some other attributes (such as Unit/Type)

We can POST 2 types of JSON body to build point now, but we need more documents on them.

The Line-Protocol way got bad parse-error message, and we have no way to use pool-based unmarshal.
Solution

Add more documents on 2-types of JSON body
Refract line-protocol parser or rewrite the parser

The new JSON body seems like this:
{
  "name": "abc",
  "fields": [
    {
      "key": "f",  # float
      "f": 3.14
    },
    {
      "key": "s", # string
      "s": "hello"
    },
    {
      "key": "bool", # boolean
      "b": false
    },
    {
      "key": "d", # binary data, and value is base64 encoded
      "d": "aGVsbG8gd29ybGQ="
    },
    {
      "key": "int-arr",
      "a": {  # array type, and the elements are same type
        "@type": "type.googleapis.com/point.Array",
        "arr": [
          {
            "i": "1"
          },
          {
            "i": "2"
          },
          {
            "i": "3"
          }
        ]
      }
    },
    {
      "key": "mixed-arr",
      "a": { # array type, and the elements are mixed type
        "@type": "type.googleapis.com/point.Array",
        "arr": [
          {
            "i": "1"
          },
          {
            "f": 2
          },
          {
            "s": "hello"
          },
          {
            "b": false
          }
        ]
      }
    },
    {
      "key": "i", # signed int, NOTE: the value are string-wrapped number
      "i": "1234567890"
    },
    {
      "key": "u", # unsigned int
      "u": "1234567890"
    },
    {
      "key": "t1",
      "s": "v1",
      "is_tag": true # tags are string-valued, and got a boolean is_tag
    },
    {
      "key": "f2",
      "f": 3.14,
      "type": "COUNT", # extra field aboud the field(type & unit)
      "unit": "kb"
    }
  ],
  "time": "1709523668830398000" # timestamp, always nano-second and string-wrapped int
}


Images service support

would be nice to have access to Images service like in python.
specifically looking to get a servingUrl.
see here.
thanks!

We autogenerate this library, so for some reason the images service is not exposed to the library. I'll create a bug with the API here.


Need filter for county in summary to show highlights

For the summary of the dashboard, when you click a county the list is filtered by that county.  It's not super clear that it's a filter that you can click again to turn off to see all the appointments.
We need some sort of highlight for the filter that's selected that clearly indicates it can be deselected to show all the appointments again.


fix: [Inheritance] Sealed Class Hierarchy Generation Limited to Same Directory

This fixes the limitation that all members of a sealed hierarchy can only be located in the same directory.
Changes:

Remove the restriction and corresponding test disallowing sealed hierarchy members in separate directories

custom_allocators.dart  extract the functionality collecting and aliasing imports  into a ImportCollector, which is to be instantiated with the allocators and is passed the path of the corresponding model. It normalizes the path to avoid duplication and then set's it relative to the top node

class_generators_util.dart adds a function getGeneratedModelPath(...) returning a String with the models path

model_library_generator.dart add part and part of directive with relative paths

server_code_generator.dart and client_code_generator.dart instantiate ImportCollector and for each sealed hierarchy and use getGeneratedModelPath to avoid repetition.

sealed_class_test.dart adds 3 tests checking if the directives (part and part of) are generated with the correct uri

closes #2893
Pre-launch Checklist

[x] I read the Contribute page and followed the process outlined there for submitting PRs.
[x] This update contains only one single feature or bug fix and nothing else. (If you are submitting multiple fixes, please make multiple PRs.)
[x] I read and followed the Dart Style Guide and formatted the code with dart format.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///), and made sure that the documentation follows the same style as other Serverpod documentation. I checked spelling and grammar.
[x] I added new tests to check the change I am making.
[ ] All existing and new tests are passing.
[x] Any breaking changes are documented below.

If you need help, consider asking for advice on the discussion board.
Breaking changes
No breaking changes

Sorry for all the failed workflows :x:
it was a bit hard to debug the failing tests only for windows.
I ended up adding the following to tryFindPartDirective and tryFindPartOfDirective:
 // Windows-specific: separator fix
if (Platform.isWindows) {
    directiveUri = directiveUri.replaceAll('/', '');
    uri = uri.replaceAll('/', '');
 }

as CompilationUnit.directive.uri.stringValue on windows returns a path without separators, so
so what is ../filename.dart on linux
is returned as ..filename.dart on windows
therefore all conventional attempts  to normalize and then compare the paths failed, so I went with a less conventional attempt that is only used on windows


Add mention about LinkORB PHP library to README

Based on discussions on this PR current one aims to add mention about new PHP SpiceDB library. As we have another WIP library for SpiceDB I added mentions about author of libs like I saw for .NET
For linkorb library it's also Symfony bundle WIP, but that'll be added later once it's finished

I fixed this in 1825f39f724b072e9a2a8ef439493976109fe468.
Sorry the README got reorganized and broke your diff, so I just added it myself.


augmentation including axial direction

since we are working with isotropic image datasets, we can actually augment by rotation in 3D.

this might too complicated and computationally heavy.
skip for now.


Display the compatibility matrix

Linked issue
Closes #355
TODO

[x] Specify the actual URL of the service in .env

[x] Specified the URL of the test deployment of the service

[x] Display the matrix in an appropriate place in the docs
[x] Describe new ENV var in the README

Updated instructions in README
Removed "Language-specific Guides" page, created a nested "Compatibility Matrix" section instead
Updated the look and text in compat matrix section


Cow: Watch jpost.com

Cow requests the watch of the watch_keyword jpost\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

jpost\.com has been seen in 41 true positives, 5 false positives, and 0 NAAs.

Rejected by Dragonrage in Charcoal HQ. Reason: 'has 200+ FPs on SE'


Compilation error with -Wall -Wextra -Werror -Wpedantic

Projects that treats warnings as errors and uses higher warning levels can't be build with the SDK.
There are several issues in the header files, like these (and many more):
[build] ../pico-sdk/src/rp2_common/hardware_pio/include/hardware/pio.h:301:17: error: comparison is always true due to limited range of data type [-Werror=type-limits]
[build]   301 |     assert(join >= 0 && join <= 2);
[build]       |                 ^~

[build] ../pico-sdk/src/rp2_common/hardware_pio/include/hardware/pio.h:358:5: error: missing initializer for field 'pinctrl' of 'pio_sm_config' [-Werror=missing-field-initializers]
[build]   358 |     pio_sm_config c = {0, 0, 0};
[build]       |     ^~~~~~~~~~~~~
[build] ../pico-sdk/src/rp2_common/hardware_pio/include/hardware/pio.h:104:14: note: 'pinctrl' declared here
[build]   104 |     uint32_t pinctrl;
[build]       |              ^~~~~~~

[build] ../pico-sdk/src/rp2_common/hardware_pwm/include/hardware/pwm.h:143:31: error: comparison is always true due to limited range of data type [-Werror=type-limits]
[build]   143 |     valid_params_if(PWM, mode >= PWM_DIV_FREE_RUNNING && mode <= PWM_DIV_B_FALLING);
[build]       |                               ^~

[build] ../pico-sdk/src/rp2_common/hardware_vreg/include/hardware/vreg.h:31:25: error: binary constants are a GCC extension [-Werror]
[build]    31 |     VREG_VOLTAGE_1_05 = 0b1010,    ///< 1.05v
[build]       |                         ^~~~~~

Since compiling with higher warning levels is considered to be a best practice, the SDK should support this case.
GCC: arm-none-eabi-gcc (GNU Arm Embedded Toolchain 10-2020-q4-major) 10.2.1 20201103 (release)

I believe some of these have already been fixed on the develop branch, if you'd like to check that out and re-test?

@lurch Some of them are fixed, but there are still a lot of issues.
I've made a Gist with all the warnings to help locating them: https://gist.github.com/tomikaa87/8a838a2c1608b70c9e4210616c956825

We are unlikely to fix -Wpedantic. Do you see any issues without that.

@kilograham
There are a few:
[build] /opt/homebrew/bin/arm-none-eabi-gcc -DCFG_TUSB_DEBUG=1 -DCFG_TUSB_MCU=OPT_MCU_RP2040 -DCFG_TUSB_OS=OPT_OS_PICO -DPICO_BIT_OPS_PICO=1 -DPICO_BOARD=\"pico\" -DPICO_BOOT2_NAME=\"boot2_w25q080\" -DPICO_BUILD=1 -DPICO_CMAKE_BUILD_TYPE=\"Debug\" -DPICO_COPY_TO_RAM=0 -DPICO_CXX_ENABLE_EXCEPTIONS=0 -DPICO_DIVIDER_HARDWARE=1 -DPICO_DOUBLE_PICO=1 -DPICO_FLOAT_PICO=1 -DPICO_INT64_OPS_PICO=1 -DPICO_MEM_OPS_PICO=1 -DPICO_NO_FLASH=0 -DPICO_NO_HARDWARE=0 -DPICO_ON_DEVICE=1 -DPICO_PRINTF_PICO=1 -DPICO_STDIO_UART=1 -DPICO_STDIO_USB=1 -DPICO_TARGET_NAME=\"pico_bufferless_oled\" -DPICO_USE_BLOCKED_RAM=0 -I../pico-sdk/src/common/pico_stdlib/include -I../pico-sdk/src/rp2_common/hardware_gpio/include -I../pico-sdk/src/common/pico_base/include -Igenerated/pico_base -I../pico-sdk/src/boards/include -I../pico-sdk/src/rp2_common/pico_platform/include -I../pico-sdk/src/rp2040/hardware_regs/include -I../pico-sdk/src/rp2_common/hardware_base/include -I../pico-sdk/src/rp2040/hardware_structs/include -I../pico-sdk/src/rp2_common/hardware_claim/include -I../pico-sdk/src/rp2_common/hardware_sync/include -I../pico-sdk/src/rp2_common/hardware_uart/include -I../pico-sdk/src/rp2_common/hardware_divider/include -I../pico-sdk/src/common/pico_time/include -I../pico-sdk/src/rp2_common/hardware_timer/include -I../pico-sdk/src/common/pico_sync/include -I../pico-sdk/src/common/pico_util/include -I../pico-sdk/src/rp2_common/pico_runtime/include -I../pico-sdk/src/rp2_common/hardware_clocks/include -I../pico-sdk/src/rp2_common/hardware_resets/include -I../pico-sdk/src/rp2_common/hardware_watchdog/include -I../pico-sdk/src/rp2_common/hardware_xosc/include -I../pico-sdk/src/rp2_common/hardware_pll/include -I../pico-sdk/src/rp2_common/hardware_vreg/include -I../pico-sdk/src/rp2_common/hardware_irq/include -I../pico-sdk/src/rp2_common/pico_printf/include -I../pico-sdk/src/rp2_common/pico_bootrom/include -I../pico-sdk/src/common/pico_bit_ops/include -I../pico-sdk/src/common/pico_divider/include -I../pico-sdk/src/rp2_common/pico_double/include -I../pico-sdk/src/rp2_common/pico_int64_ops/include -I../pico-sdk/src/rp2_common/pico_float/include -I../pico-sdk/src/rp2_common/pico_malloc/include -I../pico-sdk/src/common/pico_binary_info/include -I../pico-sdk/src/rp2_common/pico_stdio/include -I../pico-sdk/src/rp2_common/pico_stdio_uart/include -I../pico-sdk/src/rp2_common/pico_stdio_usb/include -I../pico-sdk/lib/tinyusb/src -I../pico-sdk/lib/tinyusb/src/common -I../pico-sdk/lib/tinyusb/hw -I../pico-sdk/src/rp2_common/pico_fix/rp2040_usb_device_enumeration/include -I../pico-sdk/src/rp2_common/hardware_i2c/include -I../pico-sdk/src/rp2_common/hardware_adc/include -I../pico-sdk/src/rp2_common/hardware_dma/include -I../pico-sdk/src/rp2_common/hardware_flash/include -I../pico-sdk/src/rp2_common/hardware_interp/include -I../pico-sdk/src/rp2_common/hardware_pio/include -I../pico-sdk/src/rp2_common/hardware_pwm/include -I../pico-sdk/src/rp2_common/hardware_rtc/include -I../pico-sdk/src/rp2_common/hardware_spi/include -march=armv6-m -mcpu=cortex-m0plus -mthumb -Og -g -Wall -Wextra -Werror -ffunction-sections -fdata-sections -MD -MT CMakeFiles/pico_bufferless_oled.dir/main.c.obj -MF CMakeFiles/pico_bufferless_oled.dir/main.c.obj.d -o CMakeFiles/pico_bufferless_oled.dir/main.c.obj -c ../main.c
[build] In file included from ../pico-sdk/src/common/pico_base/include/pico/assert.h:18,
[build]                  from ../pico-sdk/src/common/pico_base/include/pico.h:20,
[build]                  from ../pico-sdk/src/common/pico_stdlib/include/pico/stdlib.h:10,
[build]                  from ../main.c:5:
[build] ../pico-sdk/src/rp2_common/hardware_pio/include/hardware/pio.h: In function 'sm_config_set_fifo_join':
[build] ../pico-sdk/src/rp2_common/hardware_pio/include/hardware/pio.h:307:17: error: comparison is always true due to limited range of data type [-Werror=type-limits]
[build]   307 |     assert(join >= 0 && join <= 2);
[build]       |                 ^~
[build] ../pico-sdk/src/rp2_common/hardware_pwm/include/hardware/pwm.h: In function 'pwm_config_set_clkdiv_mode':
[build] ../pico-sdk/src/rp2_common/hardware_pwm/include/hardware/pwm.h:147:31: error: comparison is always true due to limited range of data type [-Werror=type-limits]
[build]   147 |     valid_params_if(PWM, mode >= PWM_DIV_FREE_RUNNING && mode <= PWM_DIV_B_FALLING);
[build]       |                               ^~

those seem to be as a result of enums being unsigned! did you add a compile flag to do that?

@kilograham No, I only added those that mentioned in the title.

#182 has recently been merged which fixes some more warrnings :slightly_smiling_face:  Nice one @kilograham !

A comment. Treating warnings as errors is dangerous. Some practices to get rid of warnings (such as casts) hide problems that need attention. The compiler cannot realize that the double value I put into a single will never overflow, but it will give a warning nonetheless.  That warning shoudl remain to draw attention in a recompilation that there is a possible problem. So "considered best practice" maybe. Considered a "problem caused by bad management" by some people with 50+ years of experience. Unless your management has you in a clinch, the best practice is dutyfully inspect all warnings, head the warnings where justified and ignore them where not.

@albertvanderhorst
I agree that if there is a warning, it must be treated properly and avoid hiding it with a cast or something like that.
But why I prefer treating warnings as errors is because if you work on a larger project that uses a CI system and builds for multiple platforms on various compilers (that can differ from the ones used by the developers themselves), these warnings can be lost in the build log, but an error will break the build and this must be investigated by the author of the actual modification. There were cases when the code compiled without issues on the developer's machine on one platform, but the same code thrown warnings on another platform. IMHO treating warnings as errors is a pretty cheap solution to protect us from such problems, and I don't say that this should be the only way to ensure that the code is fine, but it helps.

those seem to be as a result of enums being unsigned! did you add a compile flag to do that?

It seems arm-none-eabi-gcc does that by default if there is no enumeration with a negative value. In other compilers (even in arm-linux-eabi-gcc) they are always signed integers.


Add array and dir support in the constructor.

Now the Config class accepts also:

an array of files from which it gets all the keys using array_replace_recursive;
a directory of files.

It refers to #18.

I really like it, if you could just do those little fixes I asked form I'm definitely :+1: nice job!

@hassankhan thanks for your suggestions. I removed the else clauses and that causes errors in test. I also added a note in the README.

I actually meant refactor the code so it doesn't need else clauses, but no matter, I've done the necessary work on my own fork. If it all looks good to @noodlehaus, I'm happy to merge into master and tag a release.

@hassankhan you practically own this project :D but yes, i'm really all in on this. thanks David and Hassan :+1:

Haha thanks for saying so, still like to make sure you approve :smile:

All merged in #21


Fixed onModalHide being called early

Overview
The onModalHide is being called too early (i.e. before actually hiding the modal) and if we try to focus an element on that callback it will fail due to RN focus trap.
Unfortunately there is no easy way to know when the modal has been hidden (RN does not have onHide prop). But I found that we can fix this be delaying the callback by 2 cycles, first one to ensure that the modal content has been unmounted and the second to ensure that the focus trap is no longer active (after refocusing the element that triggered opening the modal).
Test Plan
Consider the example stated above where we try to focus an element onModalHide callback.

Before
After

@masarusanjp @alimek Would you please take a look at this one?

@ancyrweb Can you please check this when you get the time. Thanks!

The onModalHide callback is called right after setting isVisible to false. But we will still render the <Modal /> from RNW. And it uses hooks that apply after such changes. So even that isVisible=false the modal content is still there and hooks will still be executed. Calling onModalHide at this point is too early. We need to delay that call after the hooks are executed. To be specific we need to ensure that the call is made after this hook. Looking here we need to wait 2 cycles for that to happen. First one for ModalContent and second for ModalFocusTrap (where the hook is located).

Any updates on this? @mmazzarolo
Is this still an active repo? asking since no PRs have been merged since almost a year despite having 34 PRs open.

@priyeshshah11
https://github.com/react-native-modal/react-native-modal/discussions/738
https://github.com/react-native-modal/react-native-modal/discussions/598

Thanks for the reference @mmazzarolo. There seems to be good amount of interest from everyone on that thread

Sadly 99% of the interest in that thread comes from folks who just say "I'm interested" without ever having contributed. There have been a few people who were contributed (e.g., @ancyrweb, who became a maintainer and a couple of other who declined the invite to become contributors), so I'm definitely open to it if anyone is willing to commit to it 👍
With regard with this PR, I appreciate @s77rt work, and a good way to make it easy to merge it would be for other persons to review this changes by actually trying this fix and letting me know if it works — possibly not on the same use-case @s77rt is trying it out (which I assume it's expensify). This is especially true for PRs that introduce hacks.


Android dependencies error

When I try to build my app I get this error
* What went wrong:
Execution failed for task ':app:mergeDebugAssets'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not find com.bytedance.ies.ugc.aweme:opensdk-oversea-external:<IP_ADDRESS>.
     Searched in the following locations:
       - file:/Users/aykutsaki/.m2/repository/com/bytedance/ies/ugc/aweme/opensdk-oversea-external/<IP_ADDRESS>/opensdk-oversea-external-<IP_ADDRESS>.pom
       - file:/Users/aykutsaki/Desktop/fizz/client/node_modules/react-native/android/com/bytedance/ies/ugc/aweme/opensdk-oversea-external/<IP_ADDRESS>/opensdk-oversea-external-<IP_ADDRESS>.pom
       - https://maven.google.com/com/bytedance/ies/ugc/aweme/opensdk-oversea-external/<IP_ADDRESS>/opensdk-oversea-external-<IP_ADDRESS>.pom
       - file:/Users/aykutsaki/Desktop/buzz/client/node_modules/jsc-android/dist/com/bytedance/ies/ugc/aweme/opensdk-oversea-external/<IP_ADDRESS>/opensdk-oversea-external-<IP_ADDRESS>.pom
       - https://dl.google.com/dl/android/maven2/com/bytedance/ies/ugc/aweme/opensdk-oversea-external/<IP_ADDRESS>/opensdk-oversea-external-<IP_ADDRESS>.pom
       - https://jcenter.bintray.com/com/bytedance/ies/ugc/aweme/opensdk-oversea-external/<IP_ADDRESS>/opensdk-oversea-external-<IP_ADDRESS>.pom
       - https://www.jitpack.io/com/bytedance/ies/ugc/aweme/opensdk-oversea-external/<IP_ADDRESS>/opensdk-oversea-external-<IP_ADDRESS>.pom
       -<EMAIL_ADDRESS>     Required by:
         project :app > project :react-native-tiktok

It cannot find the dependency even though maven url included
react-native-tiktok > android > build.gradle
buildscript {
    if (project == rootProject) {
        repositories {
            google()
            jcenter()
        }

        dependencies {
            classpath 'com.android.tools.build:gradle:3.5.3'
        }
    }
}

apply plugin: 'com.android.library'

def safeExtGet(prop, fallback) {
    rootProject.ext.has(prop) ? rootProject.ext.get(prop) : fallback
}

android {
    compileSdkVersion safeExtGet('Tiktok_compileSdkVersion', 30)
    buildToolsVersion safeExtGet('Tiktok_buildToolsVersion', '30.0.2')
    defaultConfig {
        minSdkVersion safeExtGet('Tiktok_minSdkVersion', 16)
        targetSdkVersion safeExtGet('Tiktok_targetSdkVersion', 30)
        versionCode 1
        versionName "1.0"

    }

    buildTypes {
        release {
            minifyEnabled false
        }
    }
    lintOptions {
        disable 'GradleCompatible'
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
}

repositories {
    mavenLocal()
    maven {
        // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
        url("$rootDir/../node_modules/react-native/android")
    }
    maven { url "https://artifact.bytedance.com/repository/AwemeOpenSDK" }
    google()
    jcenter()
}

dependencies {
    //noinspection GradleDynamicVersion
    implementation "com.facebook.react:react-native:+"  // From node_modules
    implementation 'com.bytedance.ies.ugc.aweme:opensdk-oversea-external:<IP_ADDRESS>'
}

downgrading to 1.0.1 fixed it for us


Issue pickle loss of parent properties

fix for Epoch, Event, IrregularlySampledEvent and tests associated

Coverage increased (+0.1%) to 50.213% when pulling 4bfca044fc5da6b8ce1a322e988539ffce3cc37f on HFragnaud:issuePickleEpoch into f935a9589ff6c01797ae405a3981aaa68498561c on NeuralEnsemble:master.

@apdavison could you review this please?

Looks great, just a couple of PEP8 formatting issues to fix then it can be merged.

Coverage increased (+0.1%) to 50.213% when pulling dd97e85bbbd9970837b80d1de02e2f62ebb3dd60 on HFragnaud:issuePickleEpoch into f935a9589ff6c01797ae405a3981aaa68498561c on NeuralEnsemble:master.

Coverage increased (+0.1%) to 50.213% when pulling dd97e85bbbd9970837b80d1de02e2f62ebb3dd60 on HFragnaud:issuePickleEpoch into f935a9589ff6c01797ae405a3981aaa68498561c on NeuralEnsemble:master.


RidesAuthenticationError Code 18: "The Redirect URI provided did not match what was expected."

I have the URL Scheme in my .plist configured with the traditional URI but I am unable to set this in the Uber dashboard as is needs an HTTPS URL. Am I missing something?

Hi @aasatt, sorry to hear you're having trouble. Could you provide a little more information on your URL Scheme?
You should be able to set your app specific URI in the developer dashboard, however, it does require an authority. So for example, sample://connect would be valid, but just sample:// would not. (You would then also use sample://connect as your UberCallbackURI in your .plist)

@jbrophy17 Awesome thanks. Works now.

Glad I could help! Opened #43 in relation to this


Compression of Images and Making the Small Versions Match the Larger Icon Counterparts

@GaelicGamer what other options regarding Pokemon icons are there? Those are fine, but I think current ones are more readable. Though definitely going down from 16KB to 0.2KB per icon is another story.

If you prefer the other Icons I could run those through it instead, just wasn't sure which were preferred honestly, additionally might want to look into loading the icons externally due to possible copyright claims that could stem from them.

@GaelicGamer sorry for delay. Either BW or HGSS sprites look nice.

No just pngcrushing them atm, they were already made correctly so there wasn't any need for that icon set to need any other alterations, I'll take a look at the BW and HGSS sprites when I can and do those instead.


HTTP/2 traffic in https mode is not being traced

Describe the bug
Following a thread in slack @oazizi000 and @chengruizhe discovered that HTTP/2 traffic in https mode is not being traced properly.
To Reproduce

Deploy GO demo app in a K8s environment.
Look for HTTPs traffic in Pixie UI

Expected behavior
I would expect to see the https traffic
App information:

Pixie version

$ px version
Pixie CLI
0.7.2+Distribution.91e72cd.20211217211220.1

K8s cluster version

Server Version: version.Info{Major:"1", Minor:"20+", GitVersion:"v1.20.12-gke.1500", GitCommit:"d32c0db9a3ccd0ac73b0b3abd0532505217b376e", GitTreeState:"clean", BuildDate:"2021-11-17T09:30:02Z", GoVersion:"go1.15.15b5", Compiler:"gc", Platform:"linux/amd64"}

@FrimIdan We have a fix for this that's on its way (thanks to @chengruizhe). Essentially, this case turned out to be an instance of a Go program generating HTTP/2 traffic using Go's net/http library (vs the alternative net/http2 library). We actually support both, but because of a bug, the uprobes were not getting properly deployed on the net/http instances in some binaries, including the one here.
Stay tuned for the fix.

@FrimIdan Have you had a chance to check whether the latest release has fixed the issue for you?

@oazizi000 Sorry for the late response, I've tested the fix and it did solved the issue.
For some reason I see the same req/resp body multiple times but it might be an issue with my demo app. (it suppose to be req-{"body":"test"} and resp-{"id":1})
{
time_:<PHONE_NUMBER>626,
source: {
  label: default/https-client-77b4d59b5d-v8bsq,
  script: px/pod,
  args: {
    start_time: -5m,
    pod: default/https-client-77b4d59b5d-v8bsq
  }
},
destination: {
  label: default/server-7d4f5b4d7d-s56pj,
  script: px/pod,
  args: {
    start_time: -5m,
    pod: default/server-7d4f5b4d7d-s56pj
  }
},
latency: 1175920,
major_version: 2,
req_path: /api/test,
req_method: POST,
req_headers: {
  :authority: server:8433,
  :method: POST,
  :path: /api/test,
  :scheme: https,
  accept: application/json,
  accept-encoding: gzip,
  content-length: 16,
  content-type: application/json,
  user-agent: Go-http-client/2.0,
  x-api-key: allow
},
req_body: {"body":"test"}
  {"body":"test"}
  {"body":"test"}
  {"body":"test"}
  {"body":"test"}
  ,
req_body_size: 80,
resp_status: 201,
resp_message: OK,
resp_headers: {
  :status: 201,
  content-length: 9,
  content-type: application/json,
  date: Mon, 11 Apr 2022 12:57:39 GMT
},
  resp_body: {"id":1}
  {"id":1}
  {"id":1}
  {"id":1}
  {"id":1}
  ,
resp_body_size: 45
}


Issues with symbol instance keys

Currently, syncing symbol instances does behave as expected. Details below:
Example
Given
A text layer text with a symbol subsymbol within another symbol symbol as represented by symbol > subsymbol > text.
Expectation
It should first look for a key name text[symbol][subsymbol]. If this is not found, then it should look for text[symbol] followed by text. This is known as key qualifiers and it should try the most specific one first, followed by less and less specific ones.
Issue
Currently, it only looks for the most specific key text[symbol][subsymbol] and does not look for the other qualifier variants.
Impact
This will cause issues on both pushing and pulling. It will cause blank fields on a push and cause improper values on a pull.
Status
We are currently looking into this and expect to have a solution by Monday, April 24th.

Update
Since this feature is only for symbol instances, it can use the standard functionality of symbol overrides to accomplish the same desired affect.
Implementation
Symbol instances by default take the value of their master unless an override is given. So by setting an override to blank if there is no matching key, a text layer will be given its parent symbol's value.
So in the example above, if the key text[symbol][subsymbol] is not found, it will instead set that override for that text layer to blank. This in effect, will let the override text[symbol] take next precedence followed by text. This makes use of the standard way in which Sketch overrides work.
Status
We are currently implementing this fix.

This is now fixed as of 2.4.2.


[Bug] Query escaping the % Percent char / interpreting following chars as hex number

Describe the bug
When trying to send a field in Query GUI, the value cannot contain a %-char followed by valid hex chars without being quoted.
Same in URL Field
%25ff => %ff - interpreted as hex - changes wrongly the query
%25xx => %25xx - not interpreted as hex - stays valid
To Reproduce
Steps to reproduce the behavior:

Start a new GET request
Enter some URL with Querystring like http://example.com?_filter=email%3Dlike%3D"%25ffg%25"
Look at Preview: http://example.com/?_filter=email%3Dlike%3D"�g%25"
As you can see, the %25 before ffg was converted to a % -- this only happens when the following string is a valid hex string. so if I would use xxg it would be valid behavior.

Expected behavior
The % in the URL should not be interpreted.
Desktop (please complete the following information):

OS: Windows 10
Installation Method: setup
App Version v7.0.6

This also affects fetching access tokens when the user password contains such a sequence.
When I create a user in keycloak with "foo%6cbar" and try to get a token with resource owner password credentials, it fails. "foo$6cbar" or "foo%!Ubar" for example are working fine.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Still open. Is it?

I experience this issue with Insomnia 2022.6.0.


[site] Run RayJobs

What type of PR is this?
/kind documentation

What this PR does / why we need it:
Adds documentation on how to run a RayJob
Which issue(s) this PR fixes:

Ralates to  #666
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

/cc @alculquicondor
Should I target this to main or website-v0.4.0 ?

/lgtm
/assign @alculquicondor

/approve
/hold
Let's wait for the implementation PR to merge (it's in my review queue)

/milestone v0.4

/lgtm
/approve

/hold cancel


Support ACLs in database

Add new field - ACLField which is used to store Pyramid ACLs in mongo.
Add new type - ACLType which is responsible for conversion of Pyramid ACL to strings and vice versa and validation.
ACL elements are validated before saving to database.
Skip fields _version and _acl when generating null values for fields.
Add BaseDocument property __acl__ that decodes string DB representation of ACL to valid Pyramid ACL.
When _acl field is not provided BaseDocument.__item_acl__ is used as default item ACL.

Fails because it relies on old version of nefertari (where ES type was lowercased)

created separate branch: acls_in_db


Providing context for the constructor callback

Is there any better way to do the following:
new Promise(function(resolve, reject) { ... }.bind(this));
The reason I ask is because so far Promise.try, Promise.bind, and Promise.method have taken care of preserving the value of "this" for me, without having to resort to Function.prototype.bind. And lodash does the same - _.each takes a context argument for example. So it seems to me that libraries are almost encouraging me to not use Function.prototype.bind, and I was surprised to come across a construct that requires it.

new Promise is almost always an anti-pattern, if I can make its use hard then I'll take it. It is only needed in library level code to wrap non-standard async APIs.

Thanks. Just to doublecheck, is there a better way to obtain a promise for, say, an XMLHttpRequest?

If you are using jQuery $.ajax returns a promise which you can convert to bluebird using Promise.resolve($.ajax(..:)), similar with angular or any framework you are using.
If you are using pure XMLHttpRequest you should implement a wrapper in your utility library, this will require using new Promise once. Application code should simply call the wrapper and chain the returned promise instead of using new Promise.

@gcaini the new DOM HTTP request API (called fetch) already returns promise so you can just resolve them - that said binding is fine here.

Since fetch is basically ungooglable - https://www.npmjs.com/package/whatwg-fetch

@phpnode it's the first google result for "fetch API" :dancer:


Dynamic Background Opacity for Lightbox

Is your feature request related to a problem? Please describe.
Currently the background opacity for the lighbox is 100%. It would be good to have an easy way to customise that, and make other things in the background more visible.
Describe the solution you'd like
A background Opacity prop for the Lightbox would make things easy. Alternatively, adding support for className would make it more flexible.
Describe alternatives you've considered
No response
Additional context
No response

You can change the background opacity by targeting yarl__container css class.
.yarl__container {
    background-color: rgba(0 0 0 / 80%);
}

Does this address your case?

You can change the background opacity by targeting yarl__container css class.
.yarl__container {
    background-color: rgba(0 0 0 / 80%);
}

Does this address your case?

Yes this is what I am currently using as well. However since these classes seem to be undocumented, I thought there were no guarantees for the class name staying the same. and a future version breaking my opacity implementation.
If these classes are guaranteed to stay the same, then this solves my problem!
PS: Great work on the library! This seems to be the only simple and minimal updated package for the job. Thanks for building this :)

I hear your concern, but here is my dilemma. Given the amount of CSS in this library, I decided not to use CSS-in-JS (or at least keep it to a bare minimum) in favor of pure CSS styling. The only exception to this rule is the properties the JS code needs to be aware of (e.g., fade animation duration or padding around slides). I'm very reluctant to add any additional style-related customization options as React component props because there are just way too many things to customize, and CSS is a perfect tool for the job.
And you are absolutely correct that CSS classes are technically undocumented. I'll obviously do my best to release any significant CSS-related changes through a major version bump, but there is always a chance some refactoring may break CSS customizations for some users in the future.
Do you have any suggestions on how to solve this problem?

I'm reopening this feature request since I feel that I need to implement a more robust solution here. @d4mr, I'll share a draft with you when it's ready.

@d4mr, I decided to proceed with the following customization approach.

I'll define a set of customization slots ("root", "container", "button", "icon", etc.) that library consumers would typically want to style / customize
each slot will allow styling from the JS code via CSS-in-JS styles
each slot will be tagged with a stable CSS class name ("yarl__root", "yarl__container", etc.), these classes will be documented and considered a part of the public API
each slot will allow attaching custom classes (for example, if you want to use Tailwind CSS utility classes)

So in total, there will be 3 customization options.

Directly in the JS code:

<Lightbox
  styles={{ container: { backgroundColor: "rgb(0 0 0 / 70%)" } }}
/>

CSS (target lightbox slots):

.yarl__container {
  background-color: rgb(0 0 0 / 70%);
}

CSS (attach custom classes):

<Lightbox
  classes={{ container: "bg-black/70" }}
/>

Please let me know if you have any feedback.


Support “nightly-latest” version

Resolves #12

While you are at it, put in latest release as well

While you are at it, put in latest release as well

Actually, I'm going to leave that out for now. It goes against repeatable builds, and especially in Dafny's case automatically picking up the latest version just means being forced to immediately deal with verification variability.


✨ Overhaul save_vitessce_config() to support multiple artifacts and non-.zarr

Support multiple artifacts and non-.zarr
If the VitessceConfig object references multiple artifacts, save_vitessce_config will now create a Collection and attach the config file to the collection. This makes the "Vitessce button" appear next to the collection rather than the artifact.
Simplified interface
One can now directly pass Artifact objects to the VitessceConfig wrapper classes via

https://github.com/vitessce/vitessce-python/pull/371
https://github.com/vitessce/vitessce-python/pull/373

This simplifies the interface for constructing VitessceConfig objects:
vit.AnnDataWrapper(
- adata_url=my_artifact.path.to_url(),
+ adata_artifact=my_artifact,
)

Also: The internals of save_vitessce_config are now much cleaner as there is no longer a need to do lookups based on urls which were previously needed as the flow was (artifact -> url -> artifact).

Fantastic, Mark!
I also see that this is already released in: https://pypi.org/project/vitessce/3.4.0/
I'll merge it here and release it in lamindb.

Note that this is a breaking change (will break existing notebooks that use save_vitessce_config if the config was using adata_url (would need to switch to adata_artifact). Is that ok? If not I can work on a fallback code path that would still do the artifact lookups as well

Awesome, @keller-mark!
Can you help me understand whether this will break things for non-anndata-like datasets?

Also, do you have an example for a spatialdata dataset that we could show in the guide?
https://docs.lamin.ai/vitessce (source: https://github.com/laminlabs/lamin-spatial/blob/main/docs/vitessce.ipynb)
I think they're almost exclusively working with spatialdata on the Hackathon.

@zimea, if you call ln.finish(), we could take a look at the source code that you've used to ingest the Heise 2023 dataset 😄
https://lamin.ai/scverse/spatialdata-db/transform/qQ5IQkXWOgt90000/

Can you help me understand whether this will break things for non-anndata-like datasets?

In https://github.com/vitessce/vitessce-python/pull/371/ I added support for:

AnnDataWrapper.adata_artifact
ImageOmeZarrWrapper.img_artifact
ImageOmeTiffWrapper.img_artifact
ObsSegmentationsOmeZarrWrapper.img_artifact
ObsSegmentationsOmeTiffWrapper.img_artifact

In https://github.com/vitessce/vitessce-python/pull/373 (not yet merged) I added support for SpatialDataWrapper.sdata_artifact but some things depend on the JS PR https://github.com/vitessce/vitessce/pull/1849 (e.g., Parquet-formatted Shapes)

@timtreis, Mark's changes here make working with the VitessceConfig object and lamindb more convenient and robust.
Do you happen to be either working with AnnData-like datasets or already working off of

https://github.com/vitessce/vitessce-python/pull/373

during the Hackathon? Either way, we could merge and release this PR and you'd have an improvement.
FYI: @ilan-gold @Zethson

@falexwolf done, but it was simply a POC that I can write to the spatialdata-db lamin instance and I planned to delete the artifacts and code.

Hey Alex,
we won't be directly working with AnnData-like objects, but the SpatialData objects can contain n AnnDatas. So we might have to perform hierarchical validation, but @Zethson is aware of that and is thinking hard from what I can see right now.
So far I've been working on Ilan's branch which Mark's new one is based on, but will check out the other one

@keller-mark, updating the main user guide within the lamin docs here:

https://github.com/laminlabs/lamin-spatial/pull/24


chore(consensus): Re-export and Hardfork Cleanup

Description
Cleans up re-exports in op-alloy-consensus.
Moves towards a world where addresses can be customizable for Hardforks.
Would like to see the AddressList come into play here in there future for extensibility.
Should also update Hardforks to provide a more extensible pattern to add future hardforks.
Might be worth renaming Hardforks to "Protocol Upgrades" to be in-line with the OP Stack specs.

📚 $\text{Stack Overview}$
Pulls submitted in this stack:

#274 👈
main

This comment was automatically generated by st.


Update mastodon extension

Description
Remove space that break word and update Raycast API version.
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Okay, maybe I know what's wrong.


Base Product Has_ attributes removed as redundant.

    public bool HasCropProtection { get; set; }

    public bool HasCropNutrition { get; set; }

    public bool HasCropVariety { get; set; }

    public bool HasHarvestCommodity { get; set; }

Closing this as this implementation is obviated by the compositional approach used in modeling product going forward.  E.g., the presence of Product.CropProtectionAttributes is the logical equivalent of HasCropProtection.


Allow custom migrators, so that structured store backends like parse can be used

There are many BaaSes. They have basic entity models. They could be leveraged by mirroring the ensembles internal model. This could be done at the migrator level.

Hi @drewmccormack
Revisiting this old thread, i had a question about.
Recently, Ensembles has included CloudKit support, which works more or less like Parse (both being record-based instead of file based),
Based on your experience implementing it, do you think now Parse could be an option as a store backend?
it would be a great option for Mac apps that require syncing, but do not want to be in the Mac App Store.
cheers

Yes, Parse could certainly be used. Note that Ensembles doesn't work directly with the CloudKit/Parse records. Instead it just uses the records to store blobs of data, i.e. files. So it uses it more like a file store than the way it was intended to be used.
But yes, you could quite easily take the CloudKit backend, and rewrite it to work with Parse calls instead. If you want to try it yourself, I am happy to offer guidance, but I don't really have time to do this at the moment.
Dropbox Core API is not a bad option if iCloud is off limits.

great! i am working on a mac app, and will definitely use ensembles for syncing.
when it's ready to implement syncing, i'll give it a go and will try to add parse support.
thanks!

Sounds great!
Like I said, when you come to adding Parse, I strongly recommend just copying CDECloudKitFileSystem, and adapting that with calls to Parse instead.


Support for egress gateway component

Description
Atm Kyma Istio comes with Istiod and Ingress gateway enabled by default. Add possibility to enable and configure Istio egress gateway component in similar way as other components. There should be possibility to configure kubernetes resources, HPA.
ACs:

[ ] egress disabled by default
[ ] it's possible to enable egress
[ ] it's possible to configure k8s resources and HPA
[ ] integration test
[ ] documentation

Reasons
Adding possibility to enable egress gateway
DoD:

[ ] Create a follow-up issue.
[ ] Provide unit tests.
[ ] Provide integration tests.
[ ] Provide documentation.
[ ] Test on a production-like environment.
[ ] Check the outcome of all related pipelines.
[ ] Verify resource limits.
[ ] As a PR reviewer, verify code coverage and evaluate if it is acceptable.
[ ] Create a release and bump in Kyma.
[ ] Add release notes and What's New notes for Kyma customers.

Attachments
https://github.com/kyma-project/istio/blob/main/docs/user/03-technical-reference/istio-custom-resource/01-30-istio-custom-resource.md

One requirement from a team:

We need working example on how to configure Istio egress mTLS
When java application makes external call to some URL istio should make HTTPS connection and if server has appropriate CA attach our client certificate

@strekm, please comment if this would be feasible or not.
if not, what are the alternates

@strekm  could you please help us with a working example on how to configure Istio egress mTLS

We need to understand if the egress gateway is also just another envoy proxy where access logs can be enabled the same way as with ingress gateway, and enrich the documentation accordingly.

@a-thaler egress is just another proxy. i did not find any ingress / egress specific configuration where it comes to access logs so it is safe to assume this is common.


add acceptance filter configuration helper

Briefly tested all 3 functions on a test project with yakut. Appears to work, and it's super simple.
@pavel-kirienko Does it make more sense from an API perspective to use the CanardInstance itself as an argument for the service generator and pull the local node id from that?
Closes #169

Everything other than tests have been fixed. Still trying to figure out how/what tests to write :smile: The new Github Actions CI is also almost ready.

Add a new file like test_acceptance_filter.cpp under /tests. Write a test function that invokes canardMakeAcceptanceFilterConfigForSubject() with a few different values and ensures that the output matches the expected value. Likewise for canardMakeAcceptanceFilterConfigForService() and canardConsolidateAcceptanceFilterConfigs(). These are simple functions so I don't expect the test to be longer than a couple dozen of lines.

@coderkalyan please rebase this to my v2 branch.

@pavel-kirienko This has been rebased onto your v2 branch, and I wrote a few lines of tests, but I'm not fully sure if they meet the requirements. Could you take a look and send feedback?

Ready for review again. I believe all the comments have been addressed and the CI is passing now. Other than the sonarcloud, that is, which is addressed in #186


test house-of-representative: reduce checking

GitHub: GH-188
Because csv file is too big (10,779 rows and 41 columns).
Before this change:
$ time ruby test/run-test.rb -t HouseOfRepresentativeTest --verbose=important-only
Finished in 2.679117 seconds.
1 tests, 1 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0
notifications

real    0m3.295s
user    0m3.031s
sys     0m0.152s

After this change:
$ time ruby test/run-test.rb -t HouseOfRepresentativeTest --verbose=important-only
Finished in 0.095506 seconds.
1 tests, 1 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0
notifications

real    0m0.659s
user    0m0.465s
sys     0m0.103s

Thanks.

Thanks for your review!


observeParents doesn't appear to work in IE10

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: Swiper 3.4.1

Platform/Target and Browser Versions: IE10

var swiperEventsReelPhotos = new Swiper('.events-swiper-reel', {
centeredSlides: true,
initialSlide: 1,
slidesPerView: 'auto',
paginationClickable: true,
nextButton: '.next-reel',
prevButton: '.prev-reel',
spaceBetween: 0,
observer: true,
observeParents: true,
loop: true,
pagination: '.pagination-reel'
});
What you did
Tested in IE10 and the slider is broken (won't switch slides at all)
Expected Behavior
I expect to be able to have the parent of the slider be display: none by default, then display: block and have the swiper work as expected

Observers are not supported in IE10
http://caniuse.com/#feat=mutationobserver


ForwardedHeadersFilter is not properly encoding IPV6 address

After an upgrade to Spring Boot 2.4.5 we started to see an issue when we used IPV6 protocol. reactor-netty 1.0.6 has introduced strict decoding of "Forwarded" header that cause IllegalStateException and request is not processed. ForwardedHeadersFilter is simply concatenating string, but standard required brackets around IPV6.
More details here:
https://github.com/reactor/reactor-netty/issues/1637
https://github.com/reactor/reactor-netty/pull/1589
java.lang.IllegalArgumentException: Invalid IPv4 address 0:0:0:0:0:0:0:1:50532
    at reactor.netty.transport.AddressUtils.parseAddress(AddressUtils.java:132)
    at reactor.netty.http.server.DefaultHttpForwardedHeaderHandler.parseForwardedInfo(DefaultHttpForwardedHeaderHandler.java:66)
    at reactor.netty.http.server.DefaultHttpForwardedHeaderHandler.apply(DefaultHttpForwardedHeaderHandler.java:47)

see #2214 :-)


Provide more TypeInfo for AA allocations

This is needed for precise scanning of heap objects allocated by the AA implementation.

add _aaGetY with full type info
supply more type info to _aaValues, _aaKeys
return normal dynamic array, not "raw" array

I'm not sure how obsolete this becomes with the new AA implementation, though.

Auto-merge toggled on

Looks like this causes a problem with shared AA: https://issues.dlang.org/show_bug.cgi?id=14192
If I print ti.toString() inside _aaGetY, it prints:
shared(shared(int)[int])

But ti is statically typed as TypeInfo_AssociativeArray. I think we have to check whether it's TypeInfo_Shared or not first. I don't know if any other wrappers would be something needed to check, I don't understand fully the rules for how dmd calls these.

We could fix it by using taa->nullAttributes() instead of taa->nutableOf() in https://github.com/D-Programming-Language/dmd/blob/master/src/e2ir.c#L4593. Or will _aaGetYhave to work differently for shared AAs?
It seems _d_assocarrayliteralTX could also be affected as it also just uses mutableOf. I'm not sue if you can create a shared AA literal, though.

"in" doesn't work any differently for shared AA I don't think. But that's not necessarily going to be true forever. I think that dmd really should be passing the full type info, and letting the runtime deal with peeling the layers off.

If you make a link to a line reference a commit instead of master, or the link will soon point somewhere else. Github has a handy keyboard shortcut y for this.
https://help.github.com/articles/getting-permanent-links-to-files/

It seems _d_assocarrayliteralTX could also be affected as it also just uses mutableOf. I'm not sue if you can create a shared AA literal, though.

Don't rely on subtleties, it might become possible at some point and it will be much harder to find this implicit assumptions.


Bookshelves: backend fully connected

This branch updates the backend when books move within the same shelf and between shelves.
Things to note

you can test using my account with user: kay45 and pass: kay45. BE CAREFUL though not to fully empty the bookshelves, because the backend will be updated properly, and since empty bookshelves aren't droppable, you would have to directly call API to populate it again. (if you accidentally do this just lmk and I can configure the account again)

(I mentioned this in comments as well, but...)
-> currently there's a bug where moving a book between two diff shelves results in the book being inserted at one index past where it is supposed to be (@kimcharlene is looking into it)
-> this code is not affected by that bug; it inserts the book where it's supposed to be in the DB. so once that visual bug is fixed, all will be good

this looks so great!!! good work kaylee!