feat: add support for whereNotInUnnest

Summary by CodeRabbit

New Features

Introduced whereNotInUnnest method to enhance query filtering capabilities.
Updated whereInUnnest method to support both inclusion and exclusion scenarios.

Bug Fixes

Improved clarity and robustness of the whereInUnnest method's parameter handling.

Chores

Cleaned up unused import statements in tests to enhance code readability.

Tests

Added a new test for the whereNotInUnnest method to ensure correct functionality.

Thank you for the review


Update index.md

Title
Link about creating an azure function in f#
Summary
Add link to a post which has a short introduction to creating an azure function in f#
Details
As I saw there is already a link for hosting suave.io as an azurefunction on azure. But I think someone could be interest on how to create a simple azure function in F#.
Suggested Reviewers
If you know who should review this, use '@' to request a review.
add link to simple introduction to creating an azure function in f# on azure

Hi @MNie, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

Open Publishing Build Service: The pull request content has been published and here are some changed files links of this time:

Docset 1 - core-docs
https://review.docs.microsoft.com/en-us/dotnet/articles/fsharp/using-fsharp-on-azure/index?branch=pr-en-us-1151

Status: Succeeded.
Open Publishing Report.

Closing and reopening to kick off the CI build again. (This PR should not have caused a build failure)

Hi @MNie, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

Open Publishing Build Service: The pull request content has been published and here are some changed files links of this time:

Docset 1 - core-docs
https://review.docs.microsoft.com/en-us/dotnet/articles/fsharp/using-fsharp-on-azure/index?branch=pr-en-us-1151

Status: SucceededWithWarning. Message: Warning occurred: articles/standard/base-types/extract-day.html contains illegal link: core/api/System.DateTime.html#System.DateTime.Parse(System.String). The file core/api/System.DateTime.html doesn't contain a bookmark named System.DateTime.Parse(System.String), please check the src file docs/standard/base-types/extract-day.md and src linkedTo file api_ref/System.DateTime.yml or the template you applied...
Open Publishing Report.

@cartermp Do you want to approve and merge this?

LGTM.  Thanks, @MNie!


Failing gracefully

Is there a good way to fail gracefully - e.g. if I don't have enough balance, just ignore the error and continue with the minute callbacks without needing to completely restart the algorithm?

You can try ... except anything inside of your handle_data method, but
things like not enough balance are raised outside so you may not be able to
catch it. We can add an option to ignore these types of errors and warn
instead.
On Fri, Feb 2, 2018 at 2:30 PM Ericxgao<EMAIL_ADDRESS>wrote:

Is there a good way to fail gracefully - e.g. if I don't have enough
balance, just ignore the error and continue with the minute callbacks
without needing to completely restart the algorithm?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/enigmampc/catalyst/issues/202, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABZ-Qs-4SAVf635Qo1jqSZYMJpdIc7dgks5tQ4yVgaJpZM4R33g_
.

Yeah, unfortunately I have to restart the algo if it fails outside of that handler. Would be a nice option to have a warning - thanks.


Not working in Godot 4 beta 10

Hi im using  this version https://godotengine.org/article/dev-snapshot-godot-4-0-beta-10 and I-m getting this error.
Parser Error: The function signature doesn't match the parent. Parent signature is "property_can_revert(StringName) -> bool".

You have to change those two lines to:
func property_can_revert(property: StringName):

and then it will work.

thank you!

Thanks to @fskfskfsk !! 4.x is now fixed


Migrate to Vite

Use Vite for packaging of the Quasar app.

Closing this issue before archiving the project.


Support for building OCMock as a framework for iOS

This allows simpler addition to other projects, and also allows "#import <OCMock/OCMock.h>" style imports in XCode 4.3.2.
To use, build the MakeOCMockFrameworkIOS target, and retrieve the OCMock.framework from the Products directory.
Referenced and modded instructions from:
http://db-in.com/blog/2011/07/universal-framework-iphone-ios-2-0/#framework_ios

Finally solved, years later, with Apple officially introducing frameworks in iOS 8. See #194.


Can not open 4.1.1 project with 4.1.2 on Mac OS

Godot version
4.1.2
System information
Mac OS M1 Sonoma
Issue description
I been working on a project using Godot 4.1.1 and I tryed to open it on 4.1.2 and it get stuck on a black screen.
Steps to reproduce
-Open the project laucher
-Select project
-Double click on it
This is the project I'm using: https://github.com/walterpalladino/godot-shaders
Minimal reproduction project
https://github.com/walterpalladino/godot-shaders

Can you confirm that the same project still works if you try to open it now with 4.1.1? Just to exclude issues caused by a system update independently from Godot's own update.
I don't reproduce the issue on Linux with Mesa drivers for AMD Radeon RX Vega M.
CC @bruvzg

I was able to open the same project on Godot 4.1.1.

I can't reproduce it, neither with 4.1.2, nor with current master. Projects opens, and all test scenes under shaders subfolder looks functional (based on shader names, I have not compared rendering with other platforms).
Try deleting .godot folder and reimport resources after switching the versions.

Yes, that did the trick.
Thank You.


subdomainOfPfx should take into account hostname with port number

Fixes #839

Thanks, @fantayeneh!

Thanks, @fantayeneh. This looks good to me. I'm going to wait a little on pulling this, as I want to think about #904 at the same time.  But this will make the next release.


Should we standardize on family names suffixes for static vs variable font families?

Current issue
Because variable fonts are new and still gaining support, some users need static fonts in software like InDesign or older environments (still very widely used).
Though we have standardized on an approach for variable font file naming, we have yet to standardize on a system for the typographic family names of fonts.
Currently, it is common for type designers to suffix family names with "Var" or "Variable," to indicate to users that these fonts are special. For instance, the latest version (3.4) of Inter builds to "Inter" (static) and "Inter Variable." Another example (not libre) is Upgrade & Upgrade Var from TYPETR.
Of course, @davelab6 has expressed the goal of showing variable fonts as the current standard, and showing static font as a legacy format.
Potential challenges with using "static" as a suffix, however, are:

"Variable fonts" are getting a marketing / blogpost buzz, so users probably have a better chance to understand the suffix "Variable" than "Static." For a typical user, the term "static" may be even more ambiguous than "variable," and far less useful as a Google query.
Static fonts enjoy wider support, so if we aim to keep things simple for everyday font users, it may make sense (for the time being) to keep these "legacy" versions as the current "main" / non-suffixed versions of fonts.

Question
Should we enforce a "Static" or "Variable" suffix in font names, or should we allow font designers to make the decision on their own?

I think its a upstream project decision what to call the fonts, but Google Fonts will have VFs that use the family name, unadorned, as the latest version of the family, and the API will transform the VF into static fonts for API clients who need static fonts; and in Github we'll include static fonts that have the same family name.
If upstream projects want to have their name tables set up as "Family Variable" and "Family Static" or any other appended names, that is entirely up to them.
The same situation has been around for 20 year for OTF and TTF versions that share the same family name; I think its better for our upstream projects to also have "Family" as the name with nothing appended, have the filenames indicate the status, and let users manage their font installation themselves.
(Even could be .ttf and .ttv since .otf has never been formally standardized, although at GF we did not decided to do that, and keep the .ttf extension)

@felipesanches I think the Fontbakery action here is to add GF-profile VF-section checks that ensure 'variable' and 'static' don't enter our collection.


Buggy on Motorola devices

The build provided in instant tracking page will not work in any Motorola devices, but it can be solved by this fix
https://github.com/google/mediapipe/pull/1799
Even after applying the above fix, Moto G5+ camera preview was lagging and crashes after few seconds
Orientation of 3D is different from rest of devices.
I am unable to provide any crash logs since the device is not with me. Will update this thread if I manage to get crash in any online testing platforms.

Hi @atul109  Without error logs, We will not able to answer your query. Need logs and Complete device details  to verify. Thanks!

Moto G (5S) Plus
Android 8.1.0
Fatal Exception: java.lang.RuntimeException: Error during updateTexImage (see logcat for details)        at android.graphics.SurfaceTexture.nativeUpdateTexImage(SurfaceTexture.java)        at android.graphics.SurfaceTexture.updateTexImage(SurfaceTexture.java:243)        at com.google.mediapipe.glutil.ExternalTextureRenderer.render(ExternalTextureRenderer.java:116)        at com.google.mediapipe.components.ExternalTextureConverter$RenderThread.updateOutputFrame(ExternalTextureConverter.java:448)        at com.google.mediapipe.components.ExternalTextureConverter$RenderThread.renderNext(ExternalTextureConverter.java:350)        at com.google.mediapipe.components.ExternalTextureConverter$RenderThread.lambda$onFrameAvailable$0$ExternalTextureConverter$RenderThread(ExternalTextureConverter.java:309)        at com.google.mediapipe.components.-$$Lambda$ExternalTextureConverter$RenderThread$Y1vV_XyLsWZ0ebOvq-iwjQ0H3Sw.run(:4)        at android.os.Handler.handleCallback(Handler.java:790)        at android.os.Handler.dispatchMessage(Handler.java:99)        at android.os.Looper.loop(Looper.java:164)        at com.google.mediapipe.glutil.GlThread.run(GlThread.java:141)

Can you provide a full bugreport?

Logs from MotoG5 attached
crash_report.txt

Looking at the crash log, it looks like it's successfully running for a bit, but then running into some errors.  Specifically, it looks like the external texture converter crash is probably caused by the surface errors earlier which might be because the graphics driver is failing to create glFenceSync objects (possibly connected to that "too many open files" error)?  So I'd see if you can limit the number of frames in-flight or the framerate, to see if throttling can help workaround the issue.  Otherwise, I think this would require a deeper dive into the Android graphics stack, so reassigning for follow-ups.

The issue was present in a build pulled from master branch, building from Mediapipe 0.8.2 release appears to have solved this. Also reduced camera preview resolution so that these devices are able to smoothly handle this, if resolution is not reduced sometimes there is a significant lag in camera preview which ends up crashing.


[Bug] SQL throws timeout/sql locked on Kernel Memory operation (add multiple documents, delete index)

Context / Scenario
Hello,
We are having issues with SQL, most likely with the table [dbo].[KMMemories]. It's hard to perform any operations on it. Retrieving a large number of entries takes quite some time. For instance, getting 1000 items takes 25 seconds on the first attempt and 10 seconds on subsequent runs, which is quite a lot for such a small number of items (I know the JSONs are big). Deleting an item takes about a second. This wouldn't be the biggest problem if Kernel memory operations didn't cause locks and rollbacks, essentially killing the database for a while.
There are two use cases that cause a problem:

Ingestion deadlock retry spiral: If we put too many items in the queue to be uploaded in a short span of time, the database table gets temporarily SQL deadlocked or the timeouts are extremely low (we have schedule job that consumes our repository and puts everything to KM in short time). This results in failed uploads and retriggers, which end up in the same failed result. This basically happens after every single retry again and again. We need to wait for all auto retries to fail or forcefully cut the KM app and keep it down for few mins, which we cannot do in production. Only after letting it rest for a while (after the last attempt) can we try to upload again. Also, it will leave residues, as Storage or Search is able to be loaded fully, but the SQL fails and is not loaded.

Unable to delete index with just 150 items: If we call the delete index API, it just times out on SQL, most likely due to the slowness of the delete. This results in rollback and retry, and we get into the retry->lock/timeout->fail loop again. We need to manually go to SQL and call delete all for the index, which took 45 minutes for 1400 items.

The main table has 4800 items, and the index that fails to delete is in the screenshot with just 150 entries.
PS: I suspect you are already working on improving performance, but I just wanted to point out a few annoying use cases.
What happened?
Expectations are: We should at least be able to delete the index properly without getting a timeout, or upload without getting timeout (it feels like the current timeout is hardly a few seconds).
Additionally, it would be great if you are able to optimize the table to handle performance better and ensure that multiple indexes do not affect each other (having a DB read/write issue on one index should not block all the indices). Finally, it would be beneficial to handle the retry logic related to SQL of KM better, although that might be challenging to achieve.
Importance
edge case
Platform, Language, Versions
Kubernetes App hosting, C# version, Kernel Memory and SQL 0.92.241112.1 (never version has no mention of SQL in changelog)
DB: Azure SQL DB Elastic pool Standard v2 cores
Relevant log output
[14:45:09.889] warn: Microsoft.KernelMemory.Orchestration.AzureQueues.AzureQueuesPipeline[0] Message '5139450a-2350-4e3c-8bfd-29246b9420ad' processing failed with exception, putting message back in the queue with a delay of 4000 msecs Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.  ---> System.ComponentModel.Win32Exception (258): Unknown error 258

Microsoft.Data.SqlClient.SqlException:
   at Microsoft.Data.SqlClient.SqlConnection.OnError (Microsoft.Data.SqlClient, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning (Microsoft.Data.SqlClient, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.SqlClient.SqlCommand.InternalEndExecuteNonQuery (Microsoft.Data.SqlClient, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.SqlClient.SqlCommand.EndExecuteNonQueryInternal (Microsoft.Data.SqlClient, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.SqlClient.SqlCommand.EndExecuteNonQueryAsync (Microsoft.Data.SqlClient, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.KernelMemory.MemoryDb.SQLServer.SqlServerMemory+<DeleteIndexAsync>d__10.MoveNext (Microsoft.KernelMemory.MemoryDb.SQLServer, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=f300afd708cefcd3)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.KernelMemory.MemoryDb.SQLServer.SqlServerMemory+<DeleteIndexAsync>d__10.MoveNext (Microsoft.KernelMemory.MemoryDb.SQLServer, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=f300afd708cefcd3)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.KernelMemory.Handlers.DeleteIndexHandler+<InvokeAsync>d__7.MoveNext (Microsoft.KernelMemory.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=f300afd708cefcd3)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.KernelMemory.Pipeline.DistributedPipelineOrchestrator+<RunPipelineStepAsync>d__8.MoveNext (Microsoft.KernelMemory.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=f300afd708cefcd3)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.KernelMemory.Pipeline.DistributedPipelineOrchestrator+<>c__DisplayClass5_0+<<AddHandlerAsync>b__0>d.MoveNext (Microsoft.KernelMemory.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=f300afd708cefcd3)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.KernelMemory.Orchestration.AzureQueues.AzureQueuesPipeline+<>c__DisplayClass20_0+<<OnDequeue>b__0>d.MoveNext (Microsoft.KernelMemory.Orchestration.AzureQueues, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=f300afd708cefcd3)
Inner exception System.ComponentModel.Win32Exception handled at Microsoft.Data.SqlClient.SqlConnection.OnError:

@marcominerva thoughts?

We need to manually go to SQL and call delete all for the index, which took 45 minutes for 1400 items.

According to this statement, this seems a problem related to SQL itself, than directly depending on Kernel Memory.  From your log, I see you're using Azure SQL Database. Could you try using a local SQL Server instance?
The original SQL scripts where authored by @kbeaugrand, do you have any additional idea?

Just FIY: We do not have this problems on the secondary tables holding the contents of the jsons.
KMEmbeddings_botone
KMMemoriesTags_botone
I would still consider looking into SQL timeouts settings, and if possible slightly increase them to some more reasonable thresholds so "weaker" Database can still manage bigger concurrent load or big amount of data.
In regards to the delete of index, I might try to check the code to see the logic whether the delete really tries to create just one single call to DB to delete everything for that index. Because if that is the case, with the timeout now, which seemed like only few seconds after the delete request was fetched from queue, I don't think even fast DB would be able to make it time, especially if we talk about 10k, 100k items.


Renaming breaks the concerned log

Steps:

open the app
hit "save"
saved logs
go to the lasts
rename to anything
see that the name hasn't changed
see that the size is 0
click on it
see that it's empty
try to delete it
see that it's still here
open the rename prompt
validate without changing anything
see that there is an "Error" toast message

Context:
version: 1.5.3
Nexus 5
Android 7.1.2 (LineageOS for microG)
Logcat:
logcatReader-rename-bug.txt

Please update to v1.5.4 and let me know if the issue still exists. Thanks!


Updates to SimPleAC, based on AIAAJ paper.

These tests are failing because of motor_test.py, but really need them to pass robust. I will squash and merge, but fixed are needed for gplibrary testing.


TGP-2670: updated checklist template for PR

Checklist for developers before reviewing

[x] I have merged in main
[x] I have run  sbt prePR to run all tests, format and check the code coverage
[x] I have written unit tests to cover any code that I wrote, where necessary
[x] I have ran the microservices with the latest SM2 config
[x] I have checked all the Acceptance Criteria pass
[x] I have run the pipeline journey tests
[x] I have run the local journey tests
[x] I have moved the ticket to Review in Jira
[x] I have left a message in tgp-prs on slack to alert other Devs that this ticket is ready for review

Checklist for developers before merging

[ ] The PR has been approved by 2 other developers
[ ] I have merged in main
[ ] I have run  `sbt preMerge' to run all tests, check formatting and code coverage
[ ] I have ran the microservices with the latest SM2 config
[ ] I have checked all the Acceptance Criteria pass
[ ] I have run the pipeline journey tests
[ ] I have run the local journey tests
[ ] I have spoken to the QAs about any changes that may need to be made to the journey tests OR no changes to the journey tests are necessary

Reminders for developers after merging

Wait for pipeline to pass
Move ticket to QA column in Jira
Leave message in tgp-qa on slack to alert QAs that this ticket is ready for testing

Looks good to me, quite like the check list for reviewers
I noticed there was a flaky test and have actioned that as part of this PR https://github.com/hmrc/trader-goods-profiles-frontend/pull/498


Synthesis and SOLR - ArgumentNullException

When requesting /synthesis.aspx it throws this exception. Unfortunately I don't have some steps to reproduce:
[ArgumentNullException: Value cannot be null. Parameter name: fieldTypeName]    Sitecore.Diagnostics.Assert.ArgumentNotNull(Object argument, String argumentName) +63    Sitecore.ContentSearch.SolrProvider.SolrFieldMap.GetFieldConfigurationByFieldTypeName(String fieldTypeName) +40    Sitecore.ContentSearch.SolrProvider.SolrFieldNameTranslator.ProcessFieldName(String fieldName, Type returnType, CultureInfo culture, String returnTypeString, Boolean aggressiveResolver) +1319    Sitecore.ContentSearch.SolrProvider.SolrFieldNameTranslator.GetIndexFieldName(String fieldName) +31    Synthesis.Generation.MetadataGenerator.GenerateMetadata() +868    Synthesis.SynthesisHelper.ExecMetadataWithAutoFriending(IEnumerable1 configurations, Action2 processAction) +467    Synthesis.SynthesisHelper.CheckSyncAll() +181    Synthesis.ControlPanel.ControlPanelPipelineProcessor.CreateSyncSummary() +110

It seems like this happened because i didn't have any fields on my template. It only had some base templates. When i added a field directly on it, it worked.

As a longer term enhancement, Synthesis really should modularize the content search stuff out of the core and into Lucene and Solr specific packages. Or maybe a shorter term one, if I can find the time (what's spare time again?)

This isn't a complete fix but https://github.com/kamsar/Synthesis/commit/306aac569cea3efd4c9667c14c18d6110f6fbca8 makes it not error (and generated no [IndexField] when the Solr name translator fails), as well as the option to disable content search integration entirely. This is in 8.2.2-RC01 on NuGet.

This is fixed in 8.2.2 with an improved method from RC01


Add Dockerfile

Added Dockerfile to obviate the need for people to install dependencies locally.

The direction we want to go in re: easing installation is to use git submodules, do you think that could be a viable alternative to Docker?

I think submodules are really brittle and hard to use. But there's no reason you couldn't do both. I"m happy to maintain this Dockerfile.
In fact, this Dockerfile probably needs to specify git commit IDs so that it's reproducible.

@huslage would you be interested in bringing this up to date? :)

Sure

We ended up using pip to make setup easier, so I don't think we're going to merge this.


made the changes!

By submitting this pull request I confirm I've read and complied with the below requirements.

[ ] I have read the Contribution guidelines and I am confident that my PR reflects them.
[ ] I have followed the coding guidelines for this project.
[ ] My code follows the skeleton code structure.
[ ] This pull request has a descriptive title. For example, Added {Algorithm/DS name} [{Language}], not Update README.md or Added new code.

I've made the relevant requested changes


bug end-connector change dynamically

hi susie,
i just found a bug with the end-connector :
after 1st setup, if i want to change the end-connector dynamically, the new end-connector is displayed but the old one is not removed.
1st setup : annotation.connector.end = 'dot';
....
annotation = makeAnnotations.annotations.collection().annotations[annotation_idx];
annotation.connector.end = 'arrow'
makeAnnotations.annotations.update();

I believe this is resolved in 1.17.0, let me know if you have any problems with it.

it works when i switch between arrow & dot, but not if i switch to 'none'

This should be working now in 2.2.2


Add draft content for Command step type

Adding more representative draft content for Command step type (mostly copied wholesale from existing docs content) to ensure there's nothing we're missing with regards to how we want to serve up and display sidebar content.

Hey @scopegate but what if we wrote a little bit of code to parse out each H3 from the doc and populate these files from that? Similar to how the update-agent-help.sh works? That way we wouldn't be maintaining two sets of content.
We could even mark out the chunks with kramdown ids, or custom divs which have no effect on the display to make them less error prone.
I'd be super happy to restructure the docs to help make that work.
CC @harrietgrace do you have any other ideas about ways to do this?

Hey @plaindocs, that could work! @blaknite and I spoke about a slightly different path though, which is essentially flipping it the other way, and updating the docs pages down the track to pull from the structured content, as it'll probably be less prone to error that way and feels a little cleaner. It would also mean we have a single content source feeding:

Docs pages
In-app sidebar content
Pipeline schema/descriptions

Are you ok with this approach? @harrietgrace seemed to think it sounded ok, but I'd be really happy to talk it over and reconsider as a group if anyone has reservations.

Yeah, that would work also. Miiight be worth double checking that we're happy with the overall structure of that particular doc before we do that, as it'll be a PITA work with for major organizational changes.

I assembled some “fake” content over in https://github.com/buildkite/buildkite/pull/5176, because I needed more stuff to test the filtering. What’s the plan with integrating existing content?

What’s the plan with integrating existing content?

So long as everyone's comfortable with this approach, I'll keep going today and try to get all the other content up, at least in a draft state, which should obviate the need for local placeholder data.

So long as everyone's comfortable with this approach

Has the approach been discussed? The original PR seems to have been merged with no review and I don’t remember any broader discussions of the format?


Disable single-column mode for appendix

In some circumstances (e.g., camera-ready submissions which include an appendix), it is useful to leave the appendix in two-column mode. Would it be possible to have an option to do this?

This should now be possible with the option appendixcol=same, from the develop mode (commit  	1ac4b6e). Can you test?

Seems to work, thanks!


repair bug: when load normal data to questdb,remove redundant check

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


[Apache] Committer: How to bind GitHub account to Apache account

Feature Description (功能描述)

Login apache gitbox:

https://gitbox.apache.org/boxer/

Accept the invitation to join the apache team on GitHub:

https://github.com/apache/

Linked successfully:

NOTE:
PPMC need to subscribe to the private mailing list. Please subscribe to<EMAIL_ADDRESS>by sending an email to<EMAIL_ADDRESS>Reference：

https://doris.apache.org/branch-0.13/zh-CN/community/committer-guide.html#committer新人指南
https://doris.apache.org/branch-0.13/community/committer-guide.html#new-committer-guidelines

committer should enable Github 2FA first, refer dubbo-doc here to finish it

done

done

done

done

done

done

committer should enable Github 2FA first, refer dubbo-doc here to finish it
Also fine with write permission in all repos

update refer dubbo-doc here

done

done

done


Problem in exporting and viewing

Hi, after a couple of updates the "x" and "l" stopped working

please try using -attr switch

please try using -attr switch

если использовать -715, то всё работает

Can you please make a
zpaqfranz upgrade -force

?
This will update to 59.9b (pre-release)
Thank you

Please try the pre-release 59.9b, running a
zpaqfranz upgrade -force

Please try the pre-release 59.9b, running a
zpaqfranz upgrade -force

Yep, its work


More test models

There needs to be a lot more test models of varying complexity.

(7) node grip (no reactions) with different colors and shapes: node_grid.xml
(8) four types of mass actions with different colors: mass_action_rxn.xml


'sql_server.pyodbc' isn't an available database backend.

Hi all,
I get the following error when doing runserver:
django.core.exceptions.ImproperlyConfigured: 'sql_server.pyodbc' isn't an available database backend.
Try using 'django.db.backends.XXX', where XXX is one of:
    'mysql', 'oracle', 'postgresql', 'sqlite3'

My configuration in settings is like that:
{'NAME': '***',
  'USER': '***',
  'PASSWORD': '***',
  'HOST': '<IP_ADDRESS>',
  'PORT': '',
  'ENGINE': 'sql_server.pyodbc',
  'OPTIONS': {'driver': 'ODBC Driver 17 for SQL Server'}
}

The library seems to be installed, this import works without errors:
import sql_server.pyodbc
Any help appreciated.

Did you manage to resolve this problem?

I had the same issue and symptoms on Django 3.0.3, packages installed via pipenv.  In my case, I was using the original django-pyodbc-azure package and switched over to django-mssql-backend.  For me, I had installed the new package and then uninstalled the old one, meaning that I had a conflict because both packages use the same namespace.  In other words, sql_server.pyodbc could be imported fine but it was an empty module which caused Django to error here as sql_server.pyodbc.base couldn't be imported.  I solved my issue with:
pipenv uninstall django-mssql-backend
pipenv install django-mssql-backend

Same Here.
django.core.exceptions.ImproperlyConfigured: 'sql_server.pyodbc' isn't an available database backend.
Try using 'django.db.backends.XXX', where XXX is one of:
'mysql', 'oracle', 'postgresql', 'sqlite3'
I installed below Package:
django
django-redis-cache
django-mssql-backend
Is below Package requried?
pyodbc (also try to add and remove this package but raise the same exception)
Any idea?

Thanks.

Facing the same problem. The workaround provided by @davidjb didn't worked for me.

There is a fork of this project that supports Django 3.2 : https://github.com/microsoft/mssql-django

I had the same issue and symptoms on Django 3.0.3, packages installed via pipenv. In my case, I was using the original django-pyodbc-azure package and switched over to django-mssql-backend. For me, I had installed the new package and then uninstalled the old one, meaning that I had a conflict because both packages use the same namespace. In other words, sql_server.pyodbc could be imported fine but it was an empty module which caused Django to error here as sql_server.pyodbc.base couldn't be imported. I solved my issue with:
pipenv uninstall django-mssql-backend
pipenv install django-mssql-backend

This one worked for me


Feature/war 2186(Option for time diff keyword to pass or fail based on the value)

Hi @sanikakulkarni
We have already created the Jira ticket for commented code and updated the same in the respective ticket.


Re-exported commonjs module causes stack overflow during build

Bug report
Bundle the following sample project:
// commonModule.js
module.exports = {
  common: function () { console.log("called common"); }
}

// otherModule.js
export { common } from './commonModule';

// index.js
import { common } from './otherModule';
common();

What is the current behavior?
Webpack outputs an error:
Hash: 1e4da8fbb268235bd31c
Version: webpack 4.12.0
Time: 151ms
Built at: 06/16/2018 10:03:47 AM
[0] ./index.js + 1 modules 92 bytes {0} [built]
    | ./index.js 51 bytes [built]
    | ./otherModule.js 41 bytes [built]

ERROR in chunk main [entry]
[name].js
/Users/rikkigibson/src/webpack-bug/index.js<PHONE_NUMBER>b416e760e649c61eaacfa7
Maximum call stack size exceeded

Note that changing the import in index.js to import from ./'commonModule' results in a successful build.
If the current behavior is a bug, please provide the steps to reproduce.
Reproducer can be found at https://github.com/rikkigibson/webpack-bug.

Webpack should successfully emit a bundle containing the common function.

Other relevant information:
webpack version: 4.12
Node.js version: v9.10.1
Operating System: macOS 10.13.4
Additional tools: n/a

Oops, this was an environment issue! Was failing to use the node_modules-scoped webpack.

OK, I was unsure whether this was due to something wrong in my environment, but am now pretty confident that others should be able to repro this when using webpack@latest. Apologies for any confusion.

Note that in your repro otherModule points to itself
// otherModule.js
export { common } from './otherModule';

It's probably still not good, but it's so bad...

Hah, that's probably the actual problem, and would definitely explain a stack overflow.


Support SASL and GSSAPI options in ldap.conf

Based on https://linux.die.net/man/5/ldap.conf

Hello Camptocamp,
Any chance to get this merged? Those are exactly the features i would need...
Thanks!


[External] [ObjectLiteral] in ObjectCreateMode.Constructor to emit its class name

Expected
Generated code to instantiate literal object should use its class name:
var c1 = Bridge.merge(Config1(), {
    name: "Config1"
} );

Actual
Object is used:
var c1 = Bridge.merge(Object(), {
    name: "Config1"
} );

Steps To Reproduce
http://deck.net/041466c8622a2a89010bbb5378fda3fb
public class Program
{
    public static void Main()
    {
        /*@
        // This emulates external Config2
        var Config2 = function()
        {
        	return { id: 2 };
        }
        */

        // Uses Object in Bridge.merge(Object(),...
        var c1 = new Config1() { Name = "Config1" };

        // Config2 has [Name("Config2")]
        // to emulate the Expected result
        // The instance contains Id = 2
        var c2 = new Config2() { Name = "Config2" };
        Console.WriteLine(c2.Name);
        Console.WriteLine(c2.Id);
    }
}

[External]
[ObjectLiteral(ObjectCreateMode.Constructor)]
public class Config1
{
    public string Name
    {
        get; set;
    }
}

[External]
[ObjectLiteral(ObjectCreateMode.Constructor)]
[Name("Config2")]
public class Config2
{
    public string Name
    {
        get; set;
    }

    public int Id;
}

This feature has been implemented and a pull request has been submitted. The feature is expected to be included in the Bridge 15.7 release.


feat: add support for AssumeRoleWithWebIdentity for lambda plugin

Summary
This PR adds support for using IAM Roles for Service Account credentials within the AWS Lambda plugin. This allows users on EKS to invoke the lambda plugin without static credentials.

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

Functionality wise this looks good.
Implementation wise I'm wondering whether we should replace all the auth related stuff with the SDK, see https://github.com/Kong/lua-resty-aws . It features full configuration support based on AWS CLI compatible settings, including profiles etc. As well as multiple authentications, most notably the ProviderCredentialChain.
@RobSerafini fyi; the aws sdk will be included in 3.0 as an underlying lib for accessing AWS Secrets Manager afaik, but @bungle probably knows best.

we have implemented this functionality as its own plugin https://github.com/lego/kong-aws-request-signing


Improve pricing form module

Add a bit of space between the main hint and the field hints
Make the word Optional in the field hints grey
Fix typo in visually-hidden class name

Before

After

:+1:


Blake2b

Hi, I found a link for blake2b in java. Maybe you can add it when you have time!
https://github.com/0xShamil/blake2b
Thank you!

@fartem I would like to work on these

@ManishDait, sure.

@ManishDait, if you can and if you have a time for another task, this is other request for new hash type.

@ManishDait, if you can and if you have a time for another task, this is other request for new hash type.

Yeah Sure