JSON Converter support in v4?

We're in the process of migrating our microservices to .NET Core 3.1.
One of the big changes is ofcourse the migration to system.text.json. We'd rather do it now instead of do the work twice, as such we're investigating the impact of using the v4 version instead of the Cosmonaut package we're very happy to use, to prevent any remaining discrepancies between JSON serializers.
However, I noticed that for v4, we're still not completely using an existing system.text.json serializer, but something that's similar, CosmosSerializationOptions.
2 Questions;

Why has there been chosen to use a new serializer options instead of using the existing System.Text.Json/Newtonsoft one?
How can we pass custom converters to this new serializer option? Without this we can basically never do custom conversions for anything that's not natively supported in STJ (which is quite a big list until .NET 5 :( )

Thanks!

The reason CosmosSerializationOptions was chosen for v3 is it reduced dependencies on Newtonsoft. As part of v4 it will be removing all Netwonsoft dependencies. I believe the reason it still CosmosSerializationOptions is it allows easier upgrades from v3 and again reduces the exposure of an external library.
@ealsur any suggestions on creating custom converters in v4?

The reason CosmosSerializationOptions was chosen for v3 is it reduced dependencies on Newtonsoft. As part of v4 it will be removing all Netwonsoft dependencies. I believe the reason it still CosmosSerializationOptions is it allows easier upgrades from v3 and again reduces the exposure of an external library.
@ealsur any suggestions on creating custom converters in v4?

Since system.text.json is now a native lib compared to the external Newtonsoft, wouldn't V4 be a good moment to align?

v4 is still in preview so it's still possibility still. @ealsur is there any plans for this?

V4 is on System.Text.Json, there are no Newtonsoft.Json classes or types that are used.
The CosmosSerializationOptions is just an option for serialization customization. If you were using CosmosSerializationOptions on V3 to customize the Newtonsoft.Json serializer, then you can use the same option values to obtain the same effect but through System.Text.Json.
You can either:

Customize the System.Text.Json serializer behavior through CosmosSerializationOptions
Use your own custom serializer by implementing CosmosSerializer
Decorate your classes with custom System.Text.Json converters and they will be honored by the default serializer

If what you want is create custom System.Text.Json converters for classes, you can either take a look at one of ours or follow the official docs at https://docs.microsoft.com/dotnet/standard/serialization/system-text-json-converters-how-to

V4 is on System.Text.Json, there are no Newtonsoft.Json classes or types that are used.
The CosmosSerializationOptions is just an option for serialization customization. If you were using CosmosSerializationOptions on V3 to customize the Newtonsoft.Json serializer, then you can use the same option values to obtain the same effect but through System.Text.Json.
You can either:

Customize the System.Text.Json serializer behavior through CosmosSerializationOptions
Use your own custom serializer by implementing CosmosSerializer
Decorate your classes with custom System.Text.Json converters and they will be honored by the default serializer

If what you want is create custom System.Text.Json converters for classes, you can either take a look at one of ours or follow the official docs at https://docs.microsoft.com/dotnet/standard/serialization/system-text-json-converters-how-to

I think I'm following; we're registering all our custom converters in the JsonOptions object upon startup.cs. If I want to reuse these settings, I'd only have options 2, as option 1 does not cover all settings (more specifically, if I read https://github.com/Azure/azure-cosmos-dotnet-v3/blob/v4/Microsoft.Azure.Cosmos/azuredata/Serializer/CosmosJsonDotNetSerializer.cs I can see no converters being copied over)?
It's not a matter of creating converters/decorators, we all have that in place for the system.text.json migration now. I'm just trying to understand what would be the most efficiënt/solid approach to not register my converters and settings multiple times. So is option 2 in that case still the way forward?

Currently we have no public API that will take your existing JsonOptions. But one thing would be, if you can decorate your classes with the JsonConverter, then that would work anywhere, as long as System.Text.Json is the engine being used.

Currently we have no public API that will take your existing JsonOptions. But one thing would be, if you can decorate your classes with the JsonConverter, then that would work anywhere, as long as System.Text.Json is the engine being used.

I'll try this, thanks!

Just finished updating our queries using the QueryDefinition classes (500+ queries, what a work :D)
So I'm now able to test the converters. I tried following the pattern of creating a custom serializer, because I don't like the idea of cluttering my domain layer with JsonConverter attributes.
Some possible improvements for v4:

Make the CosmosSerializer accept JsonConverters/JsonOptions (why make this even internal sealed?)
Make the existing converters public (I cannot create a custom serializer without copying over all your custom converters and registering them. In essence I have now much duplicated SDK code)

What are your thoughts @ealsur ?

I'm sorry @Mortana89 but I don't understand the issue.
You don't need to pass Converters into the Serializer options unless the classes you are dealing with are not yours or you don't have access to the code.
If I have MyClass and I want to provide a converter for it, I just decorate the class:
[JsonConverter(typeof(MyClassConverter))]
public class MyClass
{

}

Why do you need the existing converters public? The existing converters just deal with the REST API Contract types, like https://github.com/Azure/azure-cosmos-dotnet-v3/blob/v4/Microsoft.Azure.Cosmos/azuredata/Resource/Settings/AccountProperties.cs#L17
The serialization of these REST API types is controlled by the SDK and thus they have their own Converters. Why do you need access to them?

I'm sorry @Mortana89 but I don't understand the issue.
You don't need to pass Converters into the Serializer options unless the classes you are dealing with are not yours or you don't have access to the code.
If I have MyClass and I want to provide a converter for it, I just decorate the class:
[JsonConverter(typeof(MyClassConverter))]
public class MyClass
{

}

Why do you need the existing converters public? The existing converters just deal with the REST API Contract types, like https://github.com/Azure/azure-cosmos-dotnet-v3/blob/v4/Microsoft.Azure.Cosmos/azuredata/Resource/Settings/AccountProperties.cs#L17
The serialization of these REST API types is controlled by the SDK and thus they have their own Converters. Why do you need access to them?

Sorry if I'm not explaining correctly, the System.Text.Json provides a few options of configuring converters. One of those options is indeed using an attribute above the property needing conversion.
Another option is registering the converter in the jsonoptions. This is possible because a converter has a method CanConvert, built-into the System.Text.Json framework.
As we have a few thousand properties that all use the same converter (Enumeration classes converted to string upon serialization), it's very error-prone to annotate each property that is of the type enumeration (we have roughly 150 enumeration classes). We used this approach in the Newtonsoft ages, and it's supported in the System.Text.Json age. It's however not supported in the Cosmos SDK, as such we're trying to find a work-around.
One of those workaround is, as you suggested, a custom cosmos serializer. That is cool, but if we make a custom cosmos serializer, we still want to be able to use the converters you set up in your internal serializer. Since these converters are internal sealed, that makes things even more complicated. A work-around what we now have done, is using reflection to actually under the bonnet get the converters you initialize in the Cosmos serializer, and add these at runtime to our custom cosmos serializer (done once in startup).
Would your cosmos serializer just take over the converters from the JsonOptions instead of assigning an empty list and then adding your two converters, I'd think this would solve it, no?

When you create a custom converter, that only applies to your type operations, it does not apply to the Cosmos DB SDK specific REST contracts.
For example, if you do a CreateContainer, we use our own serializer, not the one you provide, because the types involved are part of the service definition.
If you do user data operation, like CreateItem, then your serializer applies.
Exposing the JsonOptions is good feedback. Currently V4 is aligning with the Azure Core SDK guidelines, and they are investigating based on our case, which would be a good serializer API, so things might change between now and GA (we might end up exposing JsonOptions if it becomes the recommendation from Azure Core).

I'm not completely sure I'm seeing the behavior that type operations are using our own converters. The behavior I'm seeing is that all conversions from e.g. GetItemQueryIterator are being done through the CosmosSerializer class, which is using it's own JsonOptions, not knowing anything about setup converters in the JsonOptions configured during ASP.net app startup :/ Could you point me to the mentioned behavior in code perhaps?
Sorry for making this a quite lengthy thread! If you'd prefer to take this offline, let me know!

GetItemQueryIterator, being a user data operation, will use the CosmosSerializer implementation you pass.
Onhttps://github.com/Azure/azure-cosmos-dotnet-v3/blob/v4/Microsoft.Azure.Cosmos/azuredata/Resource/Container/ContainerCore.Items.cs#L374 we create a stream iterator.
And pass that iterator to the PageIteratorCore with this.ClientContext.ResponseFactory.CreateQueryFeedResponse as the factory to generate the item instances. Which is here https://github.com/Azure/azure-cosmos-dotnet-v3/blob/v4/Microsoft.Azure.Cosmos/azuredata/Resource/CosmosResponseFactory.cs#L41
and uses the serializer defined by the user https://github.com/Azure/azure-cosmos-dotnet-v3/blob/v4/Microsoft.Azure.Cosmos/azuredata/Resource/CosmosResponseFactory.cs#L32 and https://github.com/Azure/azure-cosmos-dotnet-v3/blob/v4/Microsoft.Azure.Cosmos/azuredata/CosmosClient.cs#L648
There is another serializer in that file which is the one we use for REST API contracts, but its not used in that operation.

I understand.
When exposing the JsonOptions, we can add our own custom converters. For now, reflection came to the rescue and we're able to use our own constructors.
For anybody else still facing issues with System.Text.Json due to missing functionality, I can suggest Dahomey as a nice library.

I tried this
Type CosmosTextJsonSerializerType = typeof(CosmosClientOptions)
                .Assembly.GetTypes()
                .First(t => t.FullName == "Azure.Cosmos.CosmosTextJsonSerializer");
            var serializerConstructor =
                CosmosTextJsonSerializerType
                .GetConstructor(BindingFlags.NonPublic | BindingFlags.Instance, null,
                    new[] { typeof(JsonSerializerOptions) }, null);
            var jsonOptions = Json.getJsonSerializerOptions();
            var converters = jsonOptions.Converters;
            var serializer = serializerConstructor.Invoke(new object[] { jsonOptions }) as CosmosSerializer;
            var options = new CosmosClientOptions() { Serializer = serializer };
            options.Diagnostics.IsLoggingEnabled = true;
            var client = new CosmosClient("https://localhost:8081", "", options);

But get Value cannot be null
Because feedResponse.Value is null.
        private IReadOnlyList<T> CreateQueryFeedResponseWithSerializer<T>(
            Response cosmosResponseMessage,
            CosmosSerializer serializer)
        {
            FeedResponse<T> feedResponse = this.CreateQueryFeedResponseHelper<T>(
                cosmosResponseMessage,
                serializer);

            return feedResponse.Value.ToList().AsReadOnly();
        }

How could this happen???
let getJsonSerializerOptions() =
    let options = JsonSerializerOptions(PropertyNamingPolicy = JsonNamingPolicy.CamelCase)
    let converters = options.Converters
    converters.Add (System.Text.Json.Serialization.JsonStringEnumConverter ())
    converters.Add (System.Text.Json.Serialization.JsonFSharpConverter ())
    options

At the beginning, I tried
type CosmosJsonSerializer() =
    inherit CosmosSerializer()
    let options = getJsonSerializerOptions()

    override __.FromStream<'T> (stream: Stream) =
        use memoryStream = new MemoryStream()
        stream.CopyTo(memoryStream)
        stream.Close()
        let item: 'T = JsonSerializer.Deserialize<'T>(new ReadOnlySpan<byte>(memoryStream.ToArray()), options)
        item

    override __.ToStream<'T>(input: 'T) =
        let bytes = JsonSerializer.SerializeToUtf8Bytes(input, options)
        new MemoryStream(bytes) :> Stream

But result is the same...

@Mortana89 what is your solution?

I localized exception to CosmosJsonSerializerWrapper.cs
        public override T FromStream<T>(Stream stream)
        {
            T item = this.InternalJsonSerializer.FromStream<T>(stream);
            if (stream.CanRead)
            {
                throw new InvalidOperationException("Json Serializer left an open stream.");
            }

            return item;
        }

@ealsur, how is this possible?

OK, so the issue is that I try to deserialize F# record using FSharp.TextJson but Azure.Cosmos tries to deserialize whole collection of my F# records. But Azure.Cosmos's serializer does not know how to deserialize a collection of F# records.

@xperieandri can you create a new issue for the specific issue you are seeing.

FWIW this custom CosmosJsonSerializer integration (in F#)  is working for me (don't forget to configure it to be used)
The Cosmos SDK sample illustrates some deeper scenarios for Azure.Core integration.


Use Material icons

Icons are here: https://fonts.google.com/icons

We are migrating to a whole new set of icons. Closing this issue.


Added InstallAware

InstallAware is now included among the InstallShield and WiX third parties.
InstallAware
This Pull Request (PR) adds information about the InstallAware third party installer, alongside the existing third parties InstallShield and WiX.
Summary
InstallAware features one-click inclusion of all Microsoft .NET Framework versions in setups it creates. InstallAware's runtime installation mechanism is fully editable and includes scripts which help avoid common installation pitfalls (for example, for the latest Microsoft .NET 4.7 Framework, the InstallAware runtime automatically updates Windows 7 certificates, installs DirectX DLLs, where these would otherwise break the installation with other third parties like InstallShield or WiX).
Details
InstallAware's runtime installation mechanism features one-click runtime inclusion into setup projects, as well as partial web deployment, and 64-bit compression (maintaining full extraction compatibility on 32-bit systems) which often reduces runtime sizes to 50% of their already-compressed sizes - resulting in an improved user experience and developer experience at the same time.

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

Thanks for your contribution @msintle. I sent a request for feedback internally and I'll respond once I hear back.

Hi @msintle, I've discussed this with the team.  We're happy to add InstallAware to the topic, however we'd have to remove the marketing tone of the changes and instead do one of the two options:

Follow the WIX model, where you give a background about the product and link to the company's page for more info
Follow the InstallShield model, where you have a how-to/step-by-step guidance.

Thanks!
/cc @unniravindranathan

Sounds good. Shall we create a new edit and then submit a new pull request?
Thank you.
On Wed, Aug 16, 2017 at 10:27 AM, Maira Wenzel<EMAIL_ADDRESS>wrote:

Hi @msintle https://github.com/msintle, I've discussed this with the
team. We're happy to add InstallAware to the topic, however we'd have to
remove the marketing tone of the changes and instead do one of the two
options:

Follow the WIX
https://github.com/dotnet/docs/blob/master/docs/framework/deployment/deployment-guide-for-developers.md
model, where you give a background about the product and link to the
company's page for more info
Follow the InstallShield
https://github.com/dotnet/docs/blob/master/docs/framework/deployment/deployment-guide-for-developers.md#installshield-deployment
model, where you have a how-to/step-by-step guidance.

Thanks!
/cc @unniravindranathan https://github.com/unniravindranathan
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/docs/pull/2823#issuecomment-322689160, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AdPWHf0FQMxmllhEruz9b2Ic8juyZ7GAks5sYpnsgaJpZM4OryXT
.

@msintle You can add the new commits on the current branch. When you push the changes to GitHub the PR will be automatically updated with the new changes. There's no need to close this and make a new PR.

We have followed the WiX example and committed a new set of changes.
WiX Word Count: 71
WiX Link Count: 3
InstallAware Word Count: 67
InstallAware Link Count: 3
Please let us have your thoughts.
On Wed, Aug 16, 2017 at 11:19 AM, Bill Wagner<EMAIL_ADDRESS>wrote:

@msintle https://github.com/msintle You can add the new commits on the
current branch. When you push the changes to GitHub the PR will be
automatically updated with the new changes. There's no need to close this
and make a new PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/docs/pull/2823#issuecomment-322700094, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AdPWHdkr1M1-FtV1jeAOrYFURE5fNovsks5sYqYUgaJpZM4OryXT
.

Thank you for your feedback @mairaw. We have committed the changes
requested. Please let us know if this is ready to merge. Thank you.
On Tue, Aug 29, 2017 at 4:44 AM, Maira Wenzel<EMAIL_ADDRESS>wrote:

@mairaw requested changes on this pull request.
Thanks for working on the feedback. I think it's almost good to merge.
I've left a few comments to be addressed.
@unniravindranathan https://github.com/unniravindranathan would you
like to review this as well? Internal review URL is:
https://review.docs.microsoft.com/en-us/dotnet/framework/
deployment/deployment-guide-for-developers?branch=pr-en-us-2823
In docs/framework/deployment/deployment-guide-for-developers.md
https://github.com/dotnet/docs/pull/2823#discussion_r135675943:

@@ -70,8 +70,8 @@ For download links, see the section [Redistributable Packages](#redistributable-

on line 4, please update ms.date to reflect we're making important changes
In docs/framework/deployment/deployment-guide-for-developers.md
https://github.com/dotnet/docs/pull/2823#discussion_r135676159:

@@ -137,6 +139,10 @@ If you use ClickOnce, InstallShield, or WiX to deploy your app, you can add a de

In the Property Pages dialog box, choose OK.

+
+### InstallAware deployment
+InstallAware builds Windows app (APPX), Windows Installer (MSI), Native Code (EXE), and App-V (Application Virtualization) packages from a single source. Easily include any version of the .NET Framework in your setup, optionally customizing the installation by editing the default scripts (for example, InstallAware pre-installs certificates on Windows 7, without which the .NET 4.7 setup fails). For more information on InstallAware, see the InstallAware for Windows Installer website.
remove the for example sentence from the parentheses and put it in a new
sentence. Such as:
... in your setup, optionally customizing the installation by editing the
default scripts https://www.installaware.com/msicode.htm. For example,
InstallAware pre-installs certificates on Windows 7, without which the .NET
4.7 setup fails.
Also change .NET 4.7 to .NET Framework 4.7.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/docs/pull/2823#pullrequestreview-59112434, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AdPWHXIvs8IUp8-7OuRgGljGnCJ_Ww79ks5sc20UgaJpZM4OryXT
.


ReferenceError: regeneratorRuntime is not defined

This is a:

[x] Bug Report
[ ] Feature Request
[ ] Question
[ ] Other

Which concerns:

[x] flow-runtime
[ ] babel-plugin-flow-runtime
[ ] flow-runtime-validators
[ ] flow-runtime-mobx
[ ] flow-config-parser
[ ] The documentation website

What is the current behaviour?

When I run code compiled with regenerator runtime, it throws "ReferenceError: regeneratorRuntime is not defined"

What is the expected behaviour?

It should not throw an error.
Which package versions are you using?

0.10.0
I'm using it in a browserify bundle.
My guess is that flow-runtime needs to be compiled with the babel-plugin-transform-runtime package.

see: https://github.com/codemix/flow-runtime/issues/35
tl;dr, add  import 'regenerator-runtime/runtime'; somewhere before flow-runtime gets imported

Thanks, yes sorry this is a dupe of #35, I misread it. I don't want to include regenerator runtime directly because any projects that use generators will already be including it and it won't get deduped, it's a bit unfortunate and really I'd rather just ship the generators, but that causes even more tooling problems.


Plag checker

Every code that has been written by a user, together with the submission time, is stored in our database.
If this website provides a feature that allows us to determine how many times a specific code has been sent, or if that number surpasses a predetermined threshold, we may label it red to indicate that the code has been copied.
We can simply use Plagiarism detection techniques-

Text-Based Plagiarism Detection - Some popular tools include Turnitin, Copyscape, and MOSS (Measure Of Software Similarity).
Code Similarity Algorithms - Libraries like Simian and JPlag are examples.

ML Integration : Train machine learning models to identify code plagiarism. You can use techniques like natural language processing (NLP) and deep learning to analyze and compare code submissions.

Hi, @pratt0007 Thank you very much for your suggestion. I genuinely appreciate your input.
I did consider this feature, but at this time, we don't have the capability to implement it as effectively as the LeetCode platform. For now, we don't save users' submission code; we only have their datetime, and the LeetCode platform has much more informative data, such as users' IP addresses (many cheating incidents happened in the same school or with someone using two accounts).

Thank You so much @baoliay2008 going through my suggestions. I think we can scrape data from Leetcode by making a package in Python or something like that, and then, after having the database, we can apply some specific algorithms to check code plagiarism.


pfTableView: does not work with items retrieved via AJAX call

When I initialize the items array with an empty array and invoke a service to retrieve the items, the table component does not show the retrieved items when they are available. It shows a message saying "No Items Available".
Plunker code: http://plnkr.co/edit/UxZ0TizJJr7Dx5hi4TMO?p=preview

I'm working on it


size is 0 in xml annotations.

OS: Windows 7
**PyQt version:**5

for some images ,the xml annotations file created by using labelImg has problems that: the width and height in size node is 0.
My guess is that the image is maybe not a jpg format file.

@makefile
I get the same problem and haven't solved it.

MacOS Sierra
python 3.5
PyQt 5


Add Rust Docs examples for UnionArray

Signed-off-by: remzi<EMAIL_ADDRESS>Which issue does this PR close?

Closes #751
Rationale for this change

Add 2 docs examples of building UnionArray using the function UnionArray::try_new,
so that users can easily understand the data structure of UnionArray.
What changes are included in this PR?

Are there any user-facing changes?

Codecov Report

Merging #1241 (ff23910) into master (7949298) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1241      +/-   ##
==========================================
- Coverage   82.94%   82.94%   -0.01%
==========================================
  Files         178      178
  Lines       51420    51420
==========================================
- Hits        42651    42650       -1
- Misses       8769     8770       +1

Impacted Files
Coverage Δ

arrow/src/array/array_union.rs
90.76% <ø> (ø)

arrow/src/datatypes/datatype.rs
66.38% <0.00%> (-0.43%)
:arrow_down:

arrow/src/array/transform/mod.rs
84.51% <0.00%> (-0.13%)
:arrow_down:

parquet_derive/src/parquet_field.rs
66.21% <0.00%> (+0.22%)
: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 7949298...ff23910. Read the comment docs.

thank you @HaoYang670


[vcpkg] Bootstrap should use Get-CimInstance instead of Get-WmiObject.

This lets it work with both Powershell 5.x and Powershell Core 6.0.
It's not clear if Powershell 7.0 will remain compatible for other reasons.

Thanks for the PR!
Also, looks like it's available down to 3.0[1] (the earliest version listed in the docs). However, we need testing to ensure this is available for Windows 7, which iirc has 2.0 by default.
[1] https://docs.microsoft.com/en-us/powershell/module/cimcmdlets/get-ciminstance?view=powershell-3.0

Would it be better to have a version check for Powershell 2 and opt to fall back to use WMIObject in that case?

@TheGoddessInari that sounds good, could you add the logic to fall back for 2.0?


Git -> Radicle -> Publish

can you remind me about this task ?

@Stelios123 this is the action someone would invoke in order to publish their repo to radicle for the first time.

It needs to check if the project has already been rad init -ed :

if it hasn't it brings up the radicle -> init dialog : https://www.figma.com/proto/9h2suLnyckUXGmMyReMiYP/LF-Wireframe---Milestone-1?node-id=472119%3A15937&scaling=contain&page-id=77%3A432&starting-point-node-id=472119%3A11764&show-proto-sidebar=1
once it has been initialised: https://www.figma.com/proto/9h2suLnyckUXGmMyReMiYP/LF-Wireframe---Milestone-1?node-id=472119%3A15350&scaling=contain&page-id=77%3A432&starting-point-node-id=472119%3A11764&show-proto-sidebar=1

If a project hasn't been initialised, the Radicle sub-menu will only show: "Share Project on Radicle".
That brings up a single dialog with the necessary fields for rad init + the seed node, so that the project can be pushed.
Once a project has been initialised, the Radicle sub-menu shouldn't show this option again.


Change license in uv_inet.c file.

This is related https://github.com/Samsung/libtuv/issues/29.
It was wrong license in there.
libtuv-DCO-1.0-Signed-off-by: Jaechul Yang<EMAIL_ADDRESS>

LGTM

LGTM


list methods in vkit generated code should support page_token

In all cases in which underlying Google Cloud service APIs support pagination with tokens, google-cloud  has exposed this functionality, which @blowmage and I feel is very important for web development use cases in which only minimal state may be available between page requests. Here is an example:
page_1 = pubsub.topics
token = page_1.token
# In a new context, in which only the literal value of `token` has been preserved...
page_2 = pubsub.topics token: token

gax-ruby's PagedEnumerable exposes the page_token, but we need to be able to pass it back to list methods in vkit-generated code that has been added to google-cloud.
The following list methods should be modified to accept an optional page_token parameter:

google-cloud-logging

ConfigServiceV2Api#list_sinks
LoggingServiceV2Api#list_log_entries
LoggingServiceV2Api#list_monitored_resource_descriptors
MetricsServiceV2Api#list_log_metrics

google-cloud-pubsub

PublisherApi#list_topics
PublisherApi#list_topic_subscriptions
SubscriberApi#list_subscriptions

/cc @jmuk @swcloud

We provides page_token as in a part of options actually (see https://github.com/googleapis/gax-ruby/blob/master/lib/google/gax.rb#L164), so it would work as
page_2 = pubsub.topics options: Google::Gax::CallOptions.new(page_token: token)

This design is borrowed from Python's one.
What would be the better way here?  Unflatten all of the call-options field as the keyword arguments to the method?

@jmuk Thank you, the page_token option in CallOptions works perfectly. I was so certain I knew everything in CallOptions that I didn't look there.
As for the API design, the only thing that I find non-intuitive is that it will be present for all methods, not just list methods, correct?
Thank you for responding, very happy to now close this issue.


Connectivity between containers that are linked by multi level links are denied when network policy is set to "allow within linked".

Rancher Versions: Build from master
Steps to reproduce the problem:
Set network policy to "allow within linked" and defaultNetworkPolicy to "deny".
Create service S1, S2,S3.
Link service S1->S2.
Link S2->S3.
Containers from service S1 are not able to reach containers in S3.
Expected Behavior:
Containers from service S1 should be able to reach containers in S3.

This is by design, we do not want to allow communication from S1->S3.


npm db new --indexName

The npm db new --indexName=<indexName> command never ends in case of success, since it is missing a process.exit(0) in scripts/db.js on line 68.

Could You create a PR with fix for that Please?:)
Thanks for reporting

Done =)


How to publish releases from one repository to another

I have a private repository with this github action file content:
name: "tauri-release"
on:
  push:
    branches:
      - tauri-release

jobs:
  publish-tauri:
    permissions:
      contents: write
    strategy:
      fail-fast: false
      matrix:
        platform: [macos-latest, ubuntu-20.04, windows-latest]

    runs-on: ${{ matrix.platform }}
    steps:
      - uses: actions/checkout@v3
      - name: install Rust stable
        uses: dtolnay/rust-toolchain@stable
      - name: install dependencies (ubuntu only)
        if: matrix.platform == 'ubuntu-20.04'
        run: |
          sudo apt-get update
          sudo apt-get install -y libgtk-3-dev libwebkit2gtk-4.0-dev libappindicator3-dev librsvg2-dev patchelf
      - name: setup node
        uses: actions/setup-node@v3
        with:
          node-version: 18
      - name: Setup pnpm
        uses: pnpm/action-setup@v2
        with:
          version: 8.5.0
      - name: Install dependencies
        run: pnpm install
      - uses: tauri-apps/tauri-action@v0
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          TAURI_PRIVATE_KEY: ${{ secrets.TAURI_PRIVATE_KEY }}
        with:
          tagName: app-v__VERSION__ # the action automatically replaces \_\_VERSION\_\_ with the app version
          releaseName: "App v__VERSION__"
          releaseBody: "See the assets to download this version and install."
          releaseDraft: true
          prerelease: false
          owner: "kuskusapp"
          repo: "kuskus"
          releaseCommitish: "94bc1cc4cb560e91583d530683f55c48c3fc6eec"

The private repo is kuskusapp/code. The release I want to publish is on https://github.com/kuskusapp/kuskus
Above action should in theory take care of this with this addition:
          owner: "kuskusapp"
          repo: "kuskus"
          releaseCommitish: "94bc1cc4cb560e91583d530683f55c48c3fc6eec"

However I get this error:

And I don't know how to get around it.
I tried to even create a personal access token with these permissions

Then try to put that token in secrets

But it failed

Not sure what else to do. The 2 repos are on the same organisation. Just one is private repo but I want the releases to be on the public repo.
Thank you.

@FabianLars had the idea to rename the personal token to not start with github_ but even then it failed.
Unless I have not used some right scopes for it.

Small update from Discord: The issue is that the target repo is in an org and not the personal account.
A "classic" PAT worked for me to upload it in an organization while beta PATs didn't. So that's a potential solution here, but looks like GitHub prefers setting up a "GitHub App" for this.
Anyway, going to close this then.

@nikitavoloboev You find solution

FYI I can publish releases to repo under organization from personal account. It is required to properly set token, permission and releaseCommitish.  I use fine-grained permission, just read and write for "contents".
Error: Validation Failed: {"resource":"Release","code":"invalid","field":"target_commitish"} - https://docs.github.com/rest/releases/releases#create-a-release

I was looking for this error. I believe it default to SHA of current commit which is invalid SHA on the current repo. I have to explicitly set releaseCommitish: main in my case.

BTW, Don't use GITHUB_, some example come with GH_PAT or any name. So just put this GITHUB_TOKEN: ${{ secrets.GH_PAT_RELEASE }}
Example
  steps:
      - name: Build Tauri and Publish Release Draft
        uses: tauri-apps/tauri-action@v0
        env:
          GITHUB_TOKEN: ${{ secrets.GH_PAT_RELEASE }}
          TAURI_SIGNING_PRIVATE_KEY: ${{ secrets.TAURI_SIGNING_PRIVATE_KEY }}
          TAURI_SIGNING_PRIVATE_KEY_PASSWORD: ${{ secrets.TAURI_SIGNING_PRIVATE_KEY_PASSWORD }}
        with:
          # Build Options
          updaterJsonPreferNsis: true
          tauriScript: pnpm tauri

          # Release Configuration
          # the action automatically replaces \_\_VERSION\_\_ with the app version.
          tagName: app-v__VERSION__
          releaseName: "App v__VERSION__"
          releaseBody: "Release details"
          releaseDraft: true
          prerelease: false
          releaseCommitish: main
          owner: an-org
          repo: my-repo

@CallMeLaNN Thx <3


PROTON-2095 Initial content and proposed project structure for the CFFI Python work

Uh, I must've been more tired than I realized; I completely missed the failure log line in the AppVeyor build output when I pushed this. Let me do the obvious fix right away
[00:02:15]          ModuleNotFoundError: No module named 'cffi'


Schema doesn't work when implementing tabs in a subcomponent

When tabs are in a subcomponent of the main router, schema doesn't work. Trying to inherit a schema defined in the main router gives the error: No schema=tab is defined for route=tab.
Example code is here.
If instead I try to insert the schema in the tab component's own router I get the error: console.error: No icon class is defined for undefined. Example code is here.

You must pass 'schemas' prop to Router to make it work:
          <Router footer={TabBar} showNavigationBar={false} navigator={this.props.navigator} schemas={this.props.schemas}>


squash internal root models in .dict()

Change Summary

This change squashes {'__root__': X} → X when converting a nested model to dict. This does not make that change at the outermost level, so .dict() still always returns a dict (as discussed in #1193).
Related issue number

#1414
Checklist

[ ] Unit tests for the changes exist
[ ] Tests pass on CI and coverage remains at 100%
[ ] Documentation reflects the changes where applicable
[ ] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

This solution is an alternative to #1429 by @silversurfer34, which is a bit more involved and only impacts .json().


Added graphs for highest deaths and recovered rates into the dashboar…

Pursuant to @hamelsmu's suggestion on #327 , the graphs for highest Recovery & Death rates are merged into existing dashboard "COVID-19 Deaths & Cases Per Capita"
A review and pull is requested for.
Best
Arun

Hi Arun, do you mind resolving conflicts

Hi Arun, do you mind resolving conflicts

Hi Hamel,
I tried to resolve the conflicts. There are still 3 of them that are appearing.
They don't look like real conflicts. Can you have a look once and advise?
Regards


bug: Apache package differences in CentOS and Ubuntu break horizon and keystone charts

Ubuntu <--> CentOS
/usr/sbin/apache2  <--> /usr/sbin/httpd
/etc/apache2/envvars  <--> /etc/sysconfig/httpd
/etc/apache2  <--> /etc/httpd
/var/log/apache2  <--> /var/log/httpd
All the files referencing Ubuntu apache specifics
% grep -r apache2 *
horizon/templates/bin/_start.sh.tpl:source /etc/apache2/envvars
horizon/templates/bin/_start.sh.tpl:rm -rf /var/run/apache2/*
horizon/templates/bin/_start.sh.tpl:APACHE_DIR="apache2"
horizon/templates/bin/_start.sh.tpl:apache2 -DFOREGROUND
horizon/templates/deployment.yaml:              mountPath: /etc/apache2/sites-enabled/000-default.conf
horizon/templates/etc/_horizon.conf.tpl:    ErrorLog /var/log/apache2/horizon.log
horizon/templates/etc/_horizon.conf.tpl:    CustomLog /var/log/apache2/horizon-access.log combined
keystone/templates/bin/_start.sh.tpl:if [ -f /etc/apache2/envvars ]; then
keystone/templates/bin/_start.sh.tpl:   source /etc/apache2/envvars
keystone/templates/bin/_start.sh.tpl:exec apache2 -DFOREGROUND
keystone/templates/deployment.yaml:              mountPath: /etc/apache2/conf-enabled/wsgi-keystone.conf
keystone/templates/deployment.yaml:              mountPath: /etc/apache2/mods-available/mpm_event.conf

Perhaps it's worth discouraging people to use CentOS based images until it's been vetted more. I suspect the mariadb chart also suffers from distro related issues (haven't tracked down the exact issue yet) and we've barely started. I understand the project goal is to be image agnostic but distro quirks have been the bane of Linux for as long as people have been downloading stacks of Slackware floppies.

@wilreichert I've been doing some work on this issue, and hope to have a PR available soon that resolves this. As you have identified the primary issue is the naming of the primary apache binary as either httpd or apache2, though there are also directory layout differences that we need to take into account. In the meantime, I've been testing with the CentOS Yaodu Image that has been set up to allow drop in replacement of .deb based images: https://github.com/yaodu/docker-keystone. This solution is obviously far from ideal and breaks SELinux support.
The PR I'm working on essentially provides mounting of the configMaps following the locations I setup within the Yaodu Image, which will enable us to use any RHEL related .rpm based distro: https://github.com/yaodu/docker-keystone/blob/master/dockerfiles/Dockerfile-centos#L58-L63, without breaking SELinux support, and restoring true Image agnostic operation.

I suppose it's impossible to identify the distro an image is using at chart make time? I don't see any other information to use besides a name which refers to an image in a repo that may or may not be accessible to the build machine.

Ultimate flexibility would mean allowing the operator to specify the binary paths and directories leveraged by scripts as well as configmap mount destinations, and so on as overrides.   There is already a plan to make the mounts values driven, but we want needing to override that to be a rare case not an every day use case.  This level of flexibility could potentially result in an unsightly set of overrides of the assumptions started as Debian and needed to be changed to Redhat to operate that type of image.
Another alternative would be a set of supported FHS approaches, and in addition to the image itself, you must also elect one of these standard "blueprints" for us to follow on top of it and we will simply case all binary, mounts, and directories assumed around options such as "debian" or "redhat" or "suse" and so on.
Just some thoughts.
Alan Meadows

When it comes to supporting multiple distros, setting a single parameter makes a lot more sense than multiple volume overrides. Especially if there was a standard case pattern for dealing with the differences as they arise. Apache is likely the worst offender here but undoubtedly others distro diffs are present. Beyond vendoring, what about the case of native packaged vs. pip source installs placing files in completely random locations? Does that have the potential to cause issues as well? i.e. pip defaults to /usr/local/lib/python2.7, kolla uses /var/lib/kolla/venv/lib/python2.7, native packages use /usr/lib/python2.7, etc.

@wilreichert are you still working on this?

I was holding off until #262 is merged since that would resolve a number of the mount issues. I'm happy to do a WIP PR to address Horizon though.

i'm going to push this item out for a future roadmap (by then we'll be in openstack proper, @wilreichert). but to address what you're asking for is going to take some planning. i'll be looking for some input on #262 from you, once you've had a chance to cut into it.


How to bind server to end points?

I want to add a rule that, if i receive HL7 on Port xxxx, send message YYY endpoint only. is it supported ?

Hi!
Yes that is certainly possible. HL7Fuse can receive messages on multiple endpoints and process them. And the send the messages to the different endpoints using routing rules. You can use the different rules to filter the messages and choose the endpoint.
Or do you want to send all the messages from xxxx to yyyy only (so recognize the incoming endpoint)? That is not possible with the standard routing rules. You could have a look at the possibility of filtering the source system (in the MSH). Of you can implement you own routing rule, but at this moment there is no information added on the source endpoint.


Doesn't seem to automatically find index.d.ts for imports of depth 2 (or more)

VSCode Version: 1.7.2
OS Version: Windows 8

Steps to Reproduce:

Import something from node_modules//<folder 1>/<folder 2> within a file, e.g. 'import { inject, TestBed }  from "@angular/core/testing"'.
VSCode keeps saying cannot find module, yet executing the transpiled source works as expected.

Can resolve it if I explicitly specify index.d.ts:
'import { inject, TestBed }  from "@angular/core/testing/index".
I'm also using node moduleResolution and every other import works fine.

Can you share your workspace?

I see this work properly now.

@shiptoncraig If you are still running into this, please provide some additional info about your project so we can investigate.
Thanks


No eligible build targets

Packages are atom-build, atom-language-rust, language-rust, linter, linter-rust, and racer. What do I need to do to build?

I have build-cargo installed.

Do you have a file named Cargo.toml in your project root? Add one and do Build: Refresh Targets to get started.

I didn't. Thanks.


Add --allow-staged to cargo fix

In addition to cargo fix --allow-dirty, a user should also be able to pass --allow-staged that lets them run cargo-fix even if there are no unstaged changes[^1].
The rationale is that content that has been git added isn't actually in danger of being permanently eaten by a poor suggestion application, because you can git checkout -- . to back out the changes.
[^1]: That's git terminology; it should behave similar similarly if Mercurial, Pijul, or Fossil have an analogue of Git's staging area—I'm not familiar

Originally reported as https://github.com/rust-lang-nursery/rustfix/issues/127

This should be a pretty isolated change in this function:
https://github.com/rust-lang/cargo/blob/6a7672ef5344c1bb570610f2574250fbee932355/src/cargo/ops/fix.rs#L79
It will require some, but not very intimate, knowledge of the supported version control systems.
It does not require knowledge about cargo internals.
You should add a few tests similar to ones found here.

@JoshBrudnak: Ah. I should have replied earlier. I worked on this a bit on Saturday, and was going to reply saying I would be interested in working on it. Any chance I could try looking at this, and you could take #5740? I see you mentioned you were interested in both.

@jljusten I have already opened a pull request fixing this issue (#5910) but if you want to take #5740 that's fine with me. :100:

@JoshBrudnak: Ah, ok.
FWIW, my changes are in this branch: https://github.com/jljusten/cargo/commits/fix-allow-staged
Maybe I'll re-work them as a follow-on to your change.

Hey, this is now assigned to me to remind me to check in with you how this is going :)
#5910 looks pretty good so far, @JoshBrudnak, and @jljusten's https://github.com/jljusten/cargo/commit/2bbbca31265cc7fddee3ba2d4f14e66517a3aadc also contains a test -- would be great to combine the two! (For example: If you add each other to the forked repos as contributors, you can both push to each others PRs. Or you could cherry-pick the commits.)
Both approaches are specific to git as far as I can see. Did you check if the other VCSs have something similar? We don't need to add support for that at first but it'd be great to know what we might also want to do.

I haven't checked other VCSs yet. @jljusten do you want me to cherry-pick jljusten@2bbbca3?

@JoshBrudnak: If you cherry-pick just that patch, the test would fail. I changed the code to print out the list of staged files with (staged) after each staged filename. (I also added (dirty) for the non-staged files.) So, our implementations were a bit different. My thought was this would help the user to know if they needed --allow-dirty, --allow-staged, or both.


Python3

Hey ! is any form of life here ?

Four months without response. Too much work, I guess.

Hi,
I'm super busy and sometimes miss notifications. Sorry for that.
That being said, I don't have a lot of spare time to work on this project. I'll try to approve PRs nonetheless, so feel free to port it :-)
If I remember correctly, there was a reason for choosing python2. I think back then one library was not python3 ready or so, but I could be mistaken here.

Yeah, I see a point here.
I'll try to find time to make a rewrite to python3, but on the other hand I'm always happy to merge PRs that fix and maintain/update the project :-)

@gehaxelt Sure. Now that I am using it I will probably start adding PRs. Usually adding py3 support should be made in smaller chunks, as they are easier to review.

I have just translated the bot to Python3 and it uses the latest libraries available. I would like some users to help me test it on different systems before making the Pull Request, as this is a major change.
The Python3 edition of the bot and the new installation instructions are available at my repository. You can still use your current "feeds.sql" file, but the database needs to be recreated, so it would be advisable before running it:
mv feeds.db feeds.db.old
Thanks.
Translated with www.DeepL.com/Translator (free version)

#62 was just merged. Thank you @Wibol for the contribution!


feat: Add Git Linter

This PR takes advantage of the gitlint made by jorisroovers in order to add more consistency to the commit history of the repo.
Contributes to: #48
Signed-off-by: Stelios Gkiokas<EMAIL_ADDRESS>

New PR to be raised.

New PR to be raised.


Underscore placeholder variable

It would be useful to be able to write _ for an existentially-quantified placeholder. Eg. in lclist-grasshopper:
{| isList(v) * has1Lock(curr, _) * isVal(curr, cv) |}

Right now I'm declaring _ as a named variable, but this doesn't have the right semantics. E.g.
{| foo(x,_) * bar(y,_) |}

This requires the second arguments of foo and bar to be equal.
This is a relatively safe use of existential quantification (basically a 'don't-care' quantification) so it shouldn't blow up Z3 or HSF.
How hard would it be to add this, @CaptainHayashi?

Duplicate of #28, I think.  Will comment on there.


no events are trigger when hover on the area chart and stacked area chart

Version
5.5.0
Link to Minimal Reproduction
https://github.com/karthik-noveau/e-charts
Steps to Reproduce

clone this repository in local
npm install
npm start
hover on area chart
no events are triggered

Current Behavior
when hover on the area chart , no events are triggered.
I already raised the ticket for area chart hover issue, so you given  one solution .
but, after add the triggerEvents in area and stacked area chart, no events are triggered as your suggestion used
I added in my code , you can check
Here the problem is , you are giving the events for circle of top of each area chart part only , not for area chart part
this is the previous raised ticket: https://github.com/apache/echarts/issues/19736
Expected Behavior

Environment
- OS: macOs
- Browser: chrome
- Framework: React Js

Any additional comments?
No response

Duplicate of #19811


support fetching videos from the camera roll

This adds a parameter for fetching videos from the camera roll. It also changes the default to fetch both videos and photos.

cc @sahrens

 what happens when you display a video element in ? Does it fatal? or shows the thumbnail?
 shows a thumbnail

The latest commit makes Photos the default, fixes the propTypes, and adds support for this property to CameraRollView.

Can you squash your commits?

Can you add another selector thingy for assetType to CameraRollViewExample in a followup PR?


init openra-mods

Motivation for this change
There are many more OpenRA mods than those supplied by default in the OpenRA engine, 10 of those are included in this PR (thanks to @fusion809). All of the included mods follow the same structure, so a generic package definitions has been defined.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Closing in favor of https://github.com/NixOS/nixpkgs/pull/53300.


Supply UI on lending markets do not show info about what lending market you are on

As poweruser I don't know on what supply market I'am. Even worse if I have tabs open and switch/relaod. I read data from this regularly.

This can be alleviated by adding a page title.
However before we're able to do this consistently across the different pages, we could add the collateral token in the supply tab as it's missing. As a lender, I have no way of knowing what collateral I'm lending against.
@ignromanov Is this something you could do?


gpslogger error

Home Assistant release with the issue:    0.71.0

Last working Home Assistant release (if known):
I'm sure since version 0.69 does not work.
Operating environment (Hass.io/Docker/Windows/etc.): Hass.io

Component/platform:  gpslogger

Description of problem:
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
My gpslogger config:
- platform: gpslogger
  password: !secret http_password

My gpslogger custom log:
https://XXXXX.duckdns.org:8123/api/gpslogger?latitude=%LAT&longitude=%LON&device=%SER&accuracy=%ACC&battery=%BATT&speed=%SPD&direction=%DIR&altitude=%ALT&provider=%PROV&activity=%ACT&api_password=XXXX

Traceback (if applicable):
Log Details (ERROR)
Tue Jun 12 2018 09:13:14 GMT-0300 (Horário Padrão de Brasília)

Error handling request
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 385, in start
    resp = await self._request_handler(request)
  File "/usr/lib/python3.6/site-packages/aiohttp/web_app.py", line 338, in _handle
    resp = await handler(request)
  File "/usr/lib/python3.6/site-packages/aiohttp/web_middlewares.py", line 88, in impl
    return await handler(request)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/http/static.py", line 68, in staticresource_middleware
    return await handler(request)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/http/real_ip.py", line 27, in real_ip_middleware
    return await handler(request)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/http/ban.py", line 68, in ban_middleware
    return await handler(request)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/http/auth.py", line 54, in auth_middleware
    return await handler(request)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/http/view.py", line 98, in handle
    result = await result
  File "/usr/lib/python3.6/site-packages/homeassistant/components/device_tracker/gpslogger.py", line 85, in get
    accuracy = int(float(data['accuracy']))
ValueError: could not convert string to float: '�C'

Additional information:
when I remove param accuracy=%ACC I get the error:
attrs[‘direction’] = float(data[‘direction’])
ValueError: could not convert string to float: ‘%DIR’

Remove direction=%DIR:
I get the error:
accuracy = int(float(data[‘accuracy’]))
ValueError: could not convert string to float: ‘�C’

remove accuracy=%ACC:
error:
attrs[‘speed’] = float(data[‘speed’])
ValueError: could not convert string to float: ‘%SPD’

remove: speed=%SPD
error:
attrs[‘altitude’] = float(data[‘altitude’])
ValueError: could not convert string to float: ‘%ALT’

remove altitude=%ALT
error:
battery = float(data[‘battery’])
ValueError: could not convert string to float: ‘�TT’

remove battery=%BATT
And finally work with:
https://xxxx.duckdns.org:8123/api/gpslogger?latitude=%LAT&longitude=%LON&device=%SER&altitude=%ALT&provider=%PROV&activit=�T&api_password=XXXX

Mines working
https://MY-URL.duckdns.org/api/GPSLOGGER? \\
latitude=%LAT& \\
longitude=%LON& \\
device=%SER& \\
accuracy=%ACC \\
&battery=%BATT& \\
speed=%SPD& \\
direction=%DIR& \\
altitude=%ALT& \\
provider=%PROV& \\
activity=%ACT& \\
api_password=MY-PASSWORD

(Gaps added for readability)

maybe it's the language of my smartphone? Pt-BR. I understood error is going some character that is not converted correctly.

Yeah, the only thing I noticed from your report is that there's a weird question-mark character appearing in a few places, which would suggest a translated character that is causing a problem.
I don't know what can be done about it though. :confused:

I have the same problem, looks like some weird character encoding, guessing the system assumes utf-8 and doesn't get it.
Error handling request
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 378, in start
    resp = await self._request_handler(request)
  File "/usr/lib/python3.6/site-packages/aiohttp/web_app.py", line 341, in _handle
    resp = await handler(request)
  File "/usr/lib/python3.6/site-packages/aiohttp/web_middlewares.py", line 88, in impl
    return await handler(request)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/http/static.py", line 68, in staticresource_middleware
    return await handler(request)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/http/real_ip.py", line 27, in real_ip_middleware
    return await handler(request)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/http/ban.py", line 68, in ban_middleware
    return await handler(request)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/http/auth.py", line 54, in auth_middleware
    return await handler(request)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/http/view.py", line 98, in handle
    result = await result
  File "/usr/lib/python3.6/site-packages/homeassistant/components/device_tracker/gpslogger.py", line 85, in get
    accuracy = int(float(data['accuracy']))
ValueError: could not convert string to float: '�C'

My system run en-us with en-us as keyboard

I have the same problem. However, it appears to only happen when using the Test option during the setup. Once I use the app, it works fine.

Same, testing doesn't work, but otherwise it does.
What is clear from the error log is that the parameters are being separated correctly. Could someone add some try:except so that the other non-erroring parameters get updated, please? This error can be easily handled and treated as if the parameter wasn't passed in.


Adding initial version of Torch for R Docker image

Description

Recently received a request from Stephen Salerno for a Docker image containing Posit's torch package for R.
Might need additional customization for Stephen's exact application, but this will serve as a great starting point for him and a great starting point for future GPU-related images.

Related Issue

Fixes #43

Testing

Successfully built the image locally and was able to successfully load the torch library within the container, but no functionality testing yet.

Merging without review for now, eventually need to add someone else as an additional maintainer moving forward.


trouble with running the example dataset

First time trying to use the pipeline on a server.
OS is Linux Mint 18.1
Python 3.5.2
Snakemake installed (pip3), conda installed.
I'm trying to run the example set, but when I run snakemake --use-conda, I get the following error.
File "/usr/local/lib/python3.5/dist-packages/snakemake/init.py", line 624, in snakemake
batch=batch,
File "/usr/local/lib/python3.5/dist-packages/snakemake/workflow.py", line 728, in execute
quiet=list_conda_envs,
File "/usr/local/lib/python3.5/dist-packages/snakemake/dag.py", line 260, in create_conda_envs
env.create(dryrun)
File "/usr/local/lib/python3.5/dist-packages/snakemake/conda.py", line 227, in create
conda = Conda(self._singularity_img)
File "/usr/local/lib/python3.5/dist-packages/snakemake/conda.py", line 338, in new
inst.init(singularity_img=singularity_img)
File "/usr/local/lib/python3.5/dist-packages/snakemake/conda.py", line 352, in init
self.info = json.loads(shell.check_output(self._get_cmd("conda info --json")))
File "/usr/lib/python3.5/json/init.py", line 312, in loads
s.class.name))
TypeError: the JSON object must be str, not 'bytes'
Any ideas on what could be wrong?

Judging from e.g. https://stackoverflow.com/questions/42683478/typeerror-the-json-object-must-be-str-not-bytes/42683509 it might be a Python version issue. Could you try updating to Python >= 3.6?

right, just thought you may have come across this before and maybe have another solution. will get back after we try with the update.

Hi Charlotte,
sorry for not bringing this to an end sooner, it turns out the problem was with the anaconda server, which was not available on the couple of days in question (blacklisted by our firewall because of an earlier hacking attack). Everything working fine.

Great, thanks for letting us know!


HowTorun

Sorry for being a noob to coding but i just recently installed cargo and im looking through all of the files, Which file do i run on cargo to see the ball predictions on rocket league ?

This actually isn't attached in any way to the game, but it is possible! Check out https://github.com/VirxEC/rl_ball_sym_pybinds/ (it might say 0.6 but that's wrong I'll update everything soon) and https://rlbot.org/ - tldr download the repo, load the folder into rlbot, and check off running the rl_ball_sym script and launch the game.

ohh lmao thought it was :D thanks for responding <3


directory separator

I found this issue already (#16). But for me it is unsolved.
On an IIS-server storing a csv-file tries to save into
C:\ngwebcrm\ngwebcrm\storage\exports/02-25-16_08:50:55.csv
which uses backslashes, but for the last one a regular slash (unix style).
I guess to fix, just use php constant DIRECTORY_SEPARATOR.
So the Exception goes:
ErrorException in CSV.php line 111:
fopen(C:\ngwebcrm\ngwebcrm\storage\exports/02-25-16_08:50:55.csv): failed to open stream: Invalid argument

Actually the slash was not the problem, but the file name having colons, which are not allowed in windows. Colon has probably been switched in PhpExcel.

Same error I am getting in Windows. I am using XAMPP and Laravel 4.2. Following is my code
public function excelupload(){ 		try {			 			$result = Excel::load("public\\upload\\text.xls",function($reader){ 			})->get(); 		} catch (Exception $e) { 			echo "<br>".$e->getMessage(); 		} 	}
and the error is
Could not open C:\xampp\htdocs\campusc/public\upload\text.xls for reading! File does not exist.
Error is in directory separator.


add HKTool and ShieldParry

I think you need to add <Dependencies /> to the entry for HKTool (to indicate that there are no dependencies).


Cover art and song info doesnt show

Rainmeter Version: 4.2 Final Release - r3111
OS Version: 10.0.17134 Build 17134
Skin Version: 2.0.2
Spotify Version: <IP_ADDRESS>7.ga8d5cef9

ive tried reinstalling everything on rainmeter and restarting my pc but the cover art and song info doesnt show up and it randomly stopped working one day for no reason

can confirm, stopped working about a week and half ago?

Duplicate of #191.


chore: release main

:robot: I have created a release beep boop
1.4.2
1.4.2 (2024-01-30)
Bug Fixes

doppler: Set remote user as owner (05fbcb6)

doppler: 2.1.3
2.1.3 (2024-01-30)
Bug Fixes

doppler: Set remote user as owner (05fbcb6)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/itsmechlark/features/releases/tag/v1.4.2 :sunflower:

:robot: Release is at https://github.com/itsmechlark/features/releases/tag/doppler-v2.1.3 :sunflower:


Update pylontech to 0.0.7

Please update my adapter ioBroker.pylontech to version 0.0.7.
This pull request was created by https://www.iobroker.dev c0726ff.

0.0.7 created 01.11.2023
OK


security issue:fake remote id message

people can use transmitter broadcast customized fake remote id easily.This will cause false drone swarms to show up on the app.Will this be fixed in the future?

It  is not possible to prevent this from the perspective of the application. Any transmitter that sends out signals that are compliant with the drone ID standards will be picked up and shown.
The current drone ID standards do not have any form of security/authentication built in. The IETF DRIP working group have work in progress to propose methods for adding this:
https://datatracker.ietf.org/wg/drip/about/

谢谢，您的邮件梁子益已收到祝好!


Prometheus: Rollup not reset after each dump interval ?

This is the command i use
command: "-format prometheus -kentik_email<EMAIL_ADDRESS>-format_rollup prometheus -sinks prometheus -prom_listen=:8084 -rollup_interval 60 -rollups s_sum,in_bytes,in_bytes,device_name,src_as,dst_as,protocol,application,src_geo,dst_geo,input_port -rollups s_sum,in_pkts,in_pkts,device_name,src_as,dst_as,protocol,application,src_geo,dst_geo,input_port"
And instead of the traffic at each point, I have the sum of traffic starting from ktranslate launch.

Can you use the rate() function to calculate traffic over time? That's how we seem most people query this data.


(Required) Updated status of issues in Project board

mark tasks that need to be done, tasks that are in progress and, tasks that are complete in project board

https://github.com/orgs/Codepath-Android-2022-Group-1/projects/1. Task has been done just not properly recorded in the sprint milestone until now. Now updated with progress of sprint 2 tasks


Procedure Expansion Patch

Goal: Show the overlapping procedure with a list expansion on selection

[x] Change the procedure component, expand with overlapping procedures when selected
[x] the interaction can handle select/deselect overlapped procedure
[x] a new data type to handle procedure + overlap list
[x] Update backend on procedure retrieval and case retrieval so that 1. it provides the overlap list 2. when calling to get cases, it has the proper filters

@JackWilb I got most of the front end stuff finished. We will need to have the backend to provide the lists and work with new filters.

As a start for this new feature, we will assume a selection of overlap, for example, under CABG, user selected TAVR and ECMO, and then the user selected another procedure Heart Transplant, the query logic for the cases would be:
(CABG and TAVR) or (CABG and ECMO) or (Heart Transplant)
a patient's case would have to fulfill the requirement above to be selected as part of the query result.

Also get_attributes sounds like a bad name for a query that only gets procedures.
Can we rename it :)

Also get_attributes sounds like a bad name for a query that only gets procedures.
Can we rename it :)

Changed to get_procedure_counts


Missing objects in overwrite confirmation popup

Closes https://github.com/larshp/abapGit/issues/3550

Small remark, otherwise looks good. Thump up for the unit test.


Support running LaraDock for multiple projects in parallel

This repository is so good it replaced all my homestead instances....
The problem I am facing is that laradock only runs once with docker-compose up on machine default. If I have several sites I want to work on, docker-compose-up will shut down the other containers.
What is the best solution - do I want a docker-machine for each docker-compose? I thought changing ports would work but it does not.

@iannazzi Great request.
Right now when you run docker-compose up in different project it restart the containers and switch to the new project.
One quick way to do it for now is to rename the services/containers and change the ports: in the example below I appended everything with -b and added +1 to every port number:
# PHP + NGINX Container #----------------------------------
php-nginx-b:
  image: laradock/php56nginx:0.1.0
  container_name: php-nginx-b
  ports:
    - "81:80"
  volumes:
    - ./settings/nginx:/etc/nginx/sites-available
    - ../:/var/www
    - ./logs/nginx:/var/log/nginx
  links:
    - mysql-b
    - redis-b
  privileged: true

# MySQL Container #----------------------------------------
mysql-b:
  image: laradock/mysql:0.1.0
  container_name: mysql-b
  ports:
    - "3307:3306"
  volumes_from:
    - data-b
  environment:
    MYSQL_DATABASE: homestead
    MYSQL_USER: homestead
    MYSQL_PASSWORD: secret
  privileged: true

# Redis Container #----------------------------------------
redis-b:
  image: laradock/redis:0.1.0
  container_name: redis-b
  ports:
    - "6380:6379"
  volumes_from:
    - data-b
  volumes:
    - ./logs/redis:/var/log/redis
  restart: always
  privileged: true

# Data Volume Container #----------------------------------
data-b:
  image: laradock/data:0.1.0
  container_name: data-b
  volumes:
    - /var/lib/mysql
    - /var/lib/redis

I will upgrade the yaml file syntax to version 2 soon. And will work on the Multi-LaraDock feature to make it much simpler.

Great, that is just perfect.
I am assuming we don't want to use multiple virtual box machines, and we do want to use one machine with multiple containers.

I think you wouldn't need to suffix the names if you are using docker-compose v2 as you can use networks. It now has multi networks, so if you have an app and compose file in a folder "larasite" and another "greatapp" you would get the app in the compose in network name larasite_default and the other greatapp_default.
Also you can set this in the conf:
Note: Your app’s network is given a name based on the “project name”, which is based on the name of the directory it lives in. You can override the project name with either the --project-name flag or the COMPOSE_PROJECT_NAME environment variable.
https://docs.docker.com/engine/userguide/networking/get-started-overlay/

@tristanbailey thanks for the info. I'm working on this right now. Will update the docs soon.

While six years have passed after the opening of this ticket, I hope this helps someone.
Problem
You have multiple projects, each of them has Laradock installed as a submodule and you want those projects to run in paralell. You launch one project telt's say - project1.test and all is fine, you launch another project2.test and it refuses to launch as ports are already bound to the host.
What you want to achieve
Adding a new projectN.test to your dev machine should be as close to docker compose up -d nginx mysql as possible.  This solution however only partially addresses this issue and you should decide if this works for your workflow.

After writing this i realised that initial setup might be a a tiny bit on the long side.

What you need

A reverse proxy container. I'm using jwilder/nginx-proxy.
Each new project having a separate Laradock container group.

What to do
Setting up the reverse proxy
Run docker network create nginx-proxy
Create a new folder for nginx-proxy in a place of your choosing, I usually host all my projects in /var/www/[projectX] so I put it next to them in /var/www/nginx-proxy. In that folder create a docker-compose.yml with the contents:
version: "3.5"
services:
  nginx-proxy:
    image: jwilder/nginx-proxy
    container_name: nginx-proxy
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock:ro

networks:
  default:
    external: true
    driver: bridge
    name: nginx-proxy

And go for docker compose up -d in that folder.
This reverse proxy will bind to hosts ports 80 and 443 and will be used to accept all incoming reqests to your hodt and then forward them to the appropriate Laradock instance. If this concept is unclear, I suggest some reading of jwilder/nginx-proxy docs.
Source & inspiration from here.
Creating/adding the first project
Go to the folder of your existing/new project.
Let's assume you have a new project in /var/www/projectN
in that folder go for a quick git submodule add https://github.com/Laradock/laradock.git laradock-projectN as Laradock docs say. Notice the folder name laradock-projectN rather than just laradock. While both can be used there may be some conflicts when there are multiple projects if going without the -projectN. See this if you don't want to add -projectN suffix so you can define the prefix in the .env file rather than the folder name.
Then goes cp .env.example .env as per the docs. the, open the new .env file.
It should go somewhat like this:
### Paths #################################################

# Point to the path of your applications code on your host
APP_CODE_PATH_HOST=../

# Point to where the `APP_CODE_PATH_HOST` should be in the container
APP_CODE_PATH_CONTAINER=/var/www

# You may add flags to the path `:cached`, `:delegated`. When using Docker Sync add `:nocopy`
APP_CODE_CONTAINER_FLAG=:cached

# Choose storage path on your machine. For all storage systems
DATA_PATH_HOST=~/.laradock/data

As Laradock is installed as a submodule in this case APP_CODE_PATH_HOST stays the same. In my case so do both APP_CODE_PATH_CONTAINER and APP_CODE_CONTAINER_FLAG.
However I change DATA_PATH_HOST=~/.laradock/data to DATA_PATH_HOST=~/.laradock/projectN-data as I do not want database failiure, this is important.
After the above environment variables this should be added
# Nginx proxy config
VIRTUAL_HOST=projectN.test
NGINX_PROXY_NETWORK=nginx-proxy

VIRTUAL_HOST is the environment variable our reverse proxy is looking for in every container in the nginx-proxy network. This also doubles as the hostname for the project. Don't forget to add this hostname to your hosts file or it won't work.
The last thing you need to do in this file is change
COMPOSE_FILE=docker-compose.yml
to
COMPOSE_FILE=docker-compose.yml;docker-compose.reverse-proxy.yml.
Please notice the semicilon (;) between the filenames. If you're using Windows as your host it should stay, otherwise change it to a colon (:) here and in COMPOSE_PATH_SEPARATOR.
If you wish, you can also change COMPOSE_PROJECT_NAME value to projectN. This will remove the necessity to change container names as suggested above.
Now we're done with .env for now but we'll return.
In the same directory create a file docker-compose.reverse-proxy.yml (this is the one referenced in COMPOSE_FILE above)
and paste in it the following:
services:
  nginx:
    expose:
      - 80
      - 443
    environment:
      - VIRTUAL_HOST=${VIRTUAL_HOST}
    networks:
      - nginx-proxy

networks:
  nginx-proxy:
    external: true
    driver: ${NETWORKS_DRIVER}

This will effectively append this configuration to the default nginx configuration in docker-compose.yml and expose both ports 80 (HTTP) and 443 (HTTPS) to the networks nginx-proxy that is defined here and frontend and backend that are defined in the default config. Also it will set the VIRTUAL_HOST environment variable that our reverse proxy is looking for.
At this point it will almost work, if you do a docker compose up -d nginx mysql in you project's directory only nginx launch should fail as port 80 is already allocated (bound) to the reverse proxy.
Now for the voodoo part.
Every guide I found on the Internet on the topic of running multiple laradocks in parallel (this issue included) adresses Bind for <IP_ADDRESS>:80 failed: port is already allocated issue by saying just change the port numbers. Tried that and discovered that it is not easily scalable as for every project you'd need to change a lot of ports.
At this point i was sure that i really don't need Laradock's ports to be bound to host's, exposed is just fine.
After some struggling with services.nginx.ports must be a list and services.nginx.ports.0 must be a number (I tried to reset the ports list in docker-compose.reverse-proxy.yml which didn't work) I also tried commenting out ports lists in the Laradock's docker-compose.yml which worked but I wanted as little or preferably no modifications to docker-compose.yml.
After that,
the time was 5AM, the sleepless madness consumed me and I just tried changing .env's NGINX_HOST_HTTP_PORT=80 to NGINX_HOST_HTTP_PORT=0 and also couple other ports that were already allocated and it worked. I guess Docker internally just ignores people trying bind something to port 0.
Return to the .env
and change whatever these ports there are set to:
NGINX_HOST_HTTP_PORT=0
NGINX_HOST_HTTPS_PORT=0
MYSQL_PORT=0
WORKSPACE_SSH_PORT=0
WORKSPACE_BROWSERSYNC_HOST_PORT=0
WORKSPACE_BROWSERSYNC_UI_HOST_PORT=0
WORKSPACE_VUE_CLI_SERVE_HOST_PORT=0
WORKSPACE_VUE_CLI_UI_HOST_PORT=0
WORKSPACE_ANGULAR_CLI_SERVE_HOST_PORT=0

Now do a docker compose up -d nginx mysql and it should launch without any issues. But only nginx, mysql, workspace and php-fpm will launch clean. If you want additional services that have ports that bind to host, e.g., phpmyadmin, the first instance will launch no problems but the second one will throw back the port problem. I will address this further below.
Creating/adding the second project

Add Laradock submodule to the project
Copy .env from the first project
In the new .env

Change the project specific paths if necessary
Change the VIRTUAL_HOST to the new projects hostname.

Copy docker-compose.reverse-proxy.yml from the first project
Do a docker compose up -d nginx mysql

How do I run and connect to to my phpMyAdmin?

or other services that are usually  bound  to host.

No other way that I know of than to bind them to a free port that is dedicatad to that specific project. If there are three projects, there'd be 3 ports necessary to be allocated to be bound. E.g. PMA_PORT=8081 for project1, PMA_PORT=8082 for project2, PMA_PORT=8083 for project3 and so on.
While you might be able to configure nginx-proxy to forward phpmyadmin (or other HTTP protocol based services) to the correct container similarly as project's Laradock's nginx by adding necessary directives to docker-compose.reverse-proxy.yml I'm not sure yet how to do it or whether this could be done to all services so you could just connect to e.g. MySQL server as project1.test:3306 and nginx-proxy would do all the magic of figuring you which container to proxy the request to. Would be nice though. Please let me know if you know how to do it 😄
Possible issues
HTTP 502 Bad gateway
Solution: check if this particular Laradock instance's nginx is in the nginx proxy network docker network inspect nginx-proxy might help.
HTTP 503 Service Temporarily Unavailable
Solution: either VIRTUAL_HOST is not set properly or Laradock is not launched for this project.


What should we do with math.citeplag.org?

http://math.citeplag.org still has a version online from 03/2017. At the moment the citeplag frontend relies on this URL API. I would like to change this towards (https://vmext.wmflabs.org/).
But what should we do with math.citeplag.org?

Keep a second separate server online (of course updated)
redirect towards vmext.wmflabs
close this url down
leave it be

@AndreG-P @physikerwelt @nmeuschke what is preferred by you?
I would go for a redirect at the moment.

@vstange redirect is ok. maybe use our own domain vmext.formulasearchengine.com which is more stable

@vstange I think andre can't do the redirect. so I unassigned andre from the task.

Redirect is active for:
http://math.citeplag.org/? > https://vmext.formulasearchengine.com
https://math.citeplag.org/? > https://vmext.formulasearchengine.com
Small problem: it seems the wmflabs server will not allow redirects with a subpath or query attached, every request lands on the main page. As far as I can see this happens when we are rediected from formulasearchengine-domain to wmflabs-domain.
The citeplag frontend will use the https://vmext.wmflabs.org address directly.

thank you great job

This could produce some site effects. It destroys the AST rendering of vmext-demo. I just fixed it by using the vmext.wmflabs location now. (https://github.com/ag-gipp/vmext-demo/issues/18)
mast.url: https://vmext.wmflabs.org/

It works. But is this correct or should it be https://vmext.formulasearchengine.com?

@AndreG-P Like I mentioned, it seems the wmflabs server will not allow redirects with a subpath or query attached.
For example: if you call https://vmext.formulasearchengine.com/api-docs you will be redirected to https://vmext.wmflabs.org/ instead.


Fixes hanging jobs when glob pattern is non-existant static file.

Escapes PathNotFound db lookup errors so that a non-existent glob pattern still enables successful jobs ran over 0 datum. Adds server tests for non-existent glob patterns.

 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.


Danke Hacktoberfest!

new Html file has been added

This pull request exceeds the max deletion limit. Please fix it and reopen


Changes My Publisher List / Dapp Store

changes in the table with My publisher List
About, social media, settings located on the same level as a short description
https://www.figma.com/file/iu2QNG0VK2MpSLn0aokFjZ/DApp-Store-v2?node-id=7%3A1571

approved by @VikMaevskaya

Checked


Disable prop types rule

We don't use prop-types and it adds no value at all just creates a visual noise for developers.
Also it spams with lots of warning when you run yarn lint so you can easily miss the important things.
We have no plans of using prop-types.
So this rule makes no sense.

Will merge and integrate today, thanks for this!


CASSANDRA-12937

Thanks for sending a pull request! Here are some tips if you're new here:

Ensure you have added or run the appropriate tests for your PR.
Be sure to keep the PR description updated to reflect all changes.
Write your PR title to summarize what this PR proposes.
If possible, provide a concise example to reproduce the issue for a faster review.
Read our contributor guidelines
If you're making a documentation change, see our guide to documentation contribution

Commit messages should follow the following format:
<One sentence description, usually Jira title or CHANGES.txt summary>

<Optional lengthier description (context on patch)>

patch by <Authors>; reviewed by <Reviewers> for CASSANDRA-#####

Co-authored-by: Name1 <email1>
Co-authored-by: Name2 <email2>

The Cassandra Jira

why are we changing sstable_compression to class in the cql table properties? (this is a compatibility break)
we need more tests:

tests around yaml-to-schema overrides,
tests around schema compression profiles over upgrade paths with new different yaml profiles,

@michaelsembwever sstable_compression was marked as deprecated since 3.0 at minimum, maybe even earlier. That one is eligible for removal in 5.0, no?

sstable_compression was marked as deprecated since 3.0 at minimum, maybe even earlier. That one is eligible for removal in 5.0, no?

ah, so class as a replacement for sstable_compression is not something new.
Yes, definitely it is time for removal. Thanks, for the work and the explanation.

Where are we with the change?

the class change is good.
it would be great to see a test around these settings being applied on a table at creation time, and then that changing the yaml settings never interferes (even if you recreate the table from its DDL).  there's a few variations here, and the consequences can be bad.

@michaelsembwever I have been looking for examples similar to the testing your requested in your comments but I haven't found anything.  Can you point me to a test that is similar in that it is testing the change in Yaml doesn't interfere with some operation?  Or some other test upon which I can model the tests you ask for?

Can you point me to a test that is similar in that it is testing the change in Yaml doesn't interfere with some operation? Or some other test upon which I can model the tests you ask for?

maybe ConfigCompatabilityTest and CreateTableValidationTest are starting points…

your PRs need more informative titles @smiklosovic :)


Add dotnet CVEs to fetcher

Only .NET Core and .NET Framework vulns are getting scanned.  Add new URL and detailUpdate call to pull the data into the scanner.

We found some cvedetails' report are problematic, also I assume the scanner side of logic need to be updated as well to pickup the new data.

This is replaced by #20


Add continuous deployment to the maker

Automatically deploy the maker (upon merge to master) to the testnet vm.

For simplicity reasons I would use the watchtower again which simply polls regularly to see if a new container is available.


Relationship between seq_len and label_len

Hi, thanks for this thoughtful paper and sharing code base.
Based on my understanding, seq_len is used for sequence length of encoder inputs, while label_len is used for sequence length of decoder inputs. More importantly, it seems that seq_len always larger than label_len, such as @cookieminions wonderful graph demonstration at https://github.com/zhouhaoyi/Informer2020/issues/44#issuecomment-798897147, and code base, etc
https://github.com/zhouhaoyi/Informer2020/blob/99b59c181f871a1521a798a37287a27ba5b742a7/data/data_loader.py#L22-L23
However, in other time-series encoder-decoder paper, such as highly-cited one "A Dual-Stage Attention-Based Recurrent Neural Network for Time Series Prediction“ at https://arxiv.org/abs/1704.02971, authors use setting of seq_len == label_len.
Thus, I am wondering is there any specific reasons for NOT setting seq_len == label_len?? Any help is greatly appreciated.

The label_len is the length of Decoder start token, it can be any value (greater than 0). Sometimes we may have a very long Encoder input, and set label_len==seq_len may cause large memory cost. So it will be better to set label_len according to the specific tasks.

Get it.


Include branch coverage in submission too

This adds the branch coverage that LCOV extracts to the JSON submitted to coveralls. This should provide branch coverage in your coveralls output.

Could you show me sample output before and after on coveralls.io?

Just before: https://coveralls.io/jobs/28800222
First build using this change: https://coveralls.io/jobs/28804861
Note the difference in the "run details" section. Without this change it only mentions "X hits per line" and "X of Y relevant lines covered". Using this change it also mentions "X of Y branches covered".

Wow! Cool! I will merge this PR and release new version as soon as possible.

Relased v1.5.0. Thanks!


MacOS packages missing for current stable release

Description
Missing MacOS packages for current stable release (2.3.1) on https://downloads.chef.io/chefdk/current & https://downloads.chef.io/chefdk/2.3.1. Also MIA via omnitruck:
$ curl -skL 'https://omnitruck.chef.io/stable/chefdk/metadata?p=mac_os_x&pv=10.12&m=amd64'
sha1	e5a0199ba63f732a5c904974fe5b2aa3de0084de
sha256	d140708f6b41dc5bd25b3e4f8a2f277ad0f26f7bd3f0ce4331bb2f8676993ca7
url	https://packages.chef.io/files/stable/chefdk/2.2.1/mac_os_x/10.12/chefdk-2.2.1-1.dmg
version	2.2.1

Thanks for the report, but we announced that this was the case in the release announcement; https://discourse.chef.io/t/chefdk-2-3-1-released/11515/2 . Closing this since it's not a bug, and it's intentional.


[Foundation] Scale back struct Notification's userInfo to be in-line …

What's in this pull request?
This simplifies the bridging story for Notifications to their objc counterparts since the id -> Any and AnyHashable changes have now been applied (which makes the previous boxing strategy no longer needed). Previous consumers of Notification that were using String keys should still work, however any explicit dictionary types should migrate from Swift 2.2 -> Swift 3 from userInfo as [NSObject:AnyObject] to [AnyHashable:Any]. The condition of distributed notifications (in non sandboxed apps) requiring plist types still applies and will fail at runtime if incorrect types are passed into the objective-c layer, and in the case of sandboxed apps userInfo still is forbidden (this change is a non functional change in the respect to those behaviors). And this time on the right branches!
Resolved bug number:

rdar://problem/27426757
rdar://problem/27561621
rdar://problem/27259984

@swift-ci test os x

@swift-ci test linux

Linux failure is an infrastructure issue: --jobs option was not cherry-picked to build-script on swift-3.0-branch.  Re-running.


Tjmadonna/236 visualization v1.0.1

Changes

Fixed left margin for x-axis labels in bar chart
Fixed x-axis labels overlap in bar chart when screen height is too small (scrolls now if necessary)

@tjmadonna does this PR also filter out the datasets with empty "organ" associated with? Those 5 datasets you identified are available on both DEV and PROD, we've asked Brendan to verify, but I don't think we'll hear back any time soon. So we can filter out those offending data for now.

@yuanzhou Yes it does. Just updated the changes

@tjmadonna thanks for the tweaks, looks good to me against the HuBMAP DEV data now. @maxsibilla once you also approve this PR, we can merge and deploy on DEV.


Vulkan: Shader debugging with input attachments

Description
Hello,
I have a render pass which consists of 4 subpasses (implementation of order independent transparency), 2 of these subpasses reads from the other two subpass color attachments as input attachments.
Now, I want to debug the shader of one of these subpass that has two input attachments. The problem is that the displayed values in the shader do not reflect what the input attachment actually contains (texture viewer shows correct values though).
Steps to reproduce

In provided capture, select any draw event in color pass #2, preferably near end of pass, e.g. event 666
In texture viewer, show output color attachment
Select any pixel (right click) in drawing zone, e.g. 560;449
Show history (first issue: history is showing input/output pixel values as 'Unavailable')
Debug pixel of any event related to a draw command, e.g. EIG 616
In shader debugging, press Run forwards
In high level variables, b0 = (0, 0, 0, 0), but should be (4.52353, 0.71981, 0.41018, 0.16476) (can be checked in texture viewer)

Capture file:
DebugInputAttachment.zip
Environment

RenderDoc version: 1.13
Operating System: Windows 10
Graphics API: Vulkan <IP_ADDRESS>
GPU: NVidia quadro P2000
Driver version: 451.48

This was caused by the pixel-relative co-ordinates not being properly transformed, so it was reading from 0,0 in the source texture. That commit should fix it.


⚠ Bofrost.be has degraded performance

In 948ed63, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1022 ms

Resolved: Bofrost.be performance has improved in 414aef0.


Using ThermofluidQuantities.jl for definitions of quantities

Codecov Report

Merging #6 (6662031) into main (3ecb5a3) will decrease coverage by 29.55%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #6       +/-   ##
==========================================
- Coverage   32.50%   2.94%   -29.56%
==========================================
  Files           6       5        -1
  Lines         160     136       -24
==========================================
- Hits           52       4       -48
- Misses        108     132       +24

Impacted Files
Coverage Δ

src/MAE103.jl
44.44% <ø> (-10.11%)
:arrow_down:

src/utils.jl
0.00% <0.00%> (-63.05%)
:arrow_down:

src/gases.jl
0.00% <0.00%> (-39.14%)
:arrow_down:

src/liquids.jl
0.00% <0.00%> (-35.00%)
:arrow_down:

Continue to review full report at Codecov.

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


Packaging request: wldash

Project description
A dashboard/launcher/control-panel thing for Wayland.

Metadata

homepage URL: https://github.com/kennylevinsen/wldash
source URL: https://github.com/kennylevinsen/wldash
license: GPL 3.0
platforms: linux, only wayland, only wlroots compositors

it's available in https://github.com/nix-community/nixpkgs-wayland

Added by https://github.com/NixOS/nixpkgs/pull/313098, closing 🙂


automatically merge master into next-moc

Test run: https://github.com/dfinity/motoko-base/pull/158/checks?check_run_id=934007373
If this works, we can also merge next-moc back to master when tagged

This is going to create one merge commit on next-moc per push to master, right? The history basically becomes useless at that point, as half of it will be noise. If we're automating this on every push I'd rather have it try to rebase and let us know when it fails.

I'm open to other suggestions. We can change this to a daily or bi-weekly job to reduce the noise. I would argue that the history is clean if we filter out commits from actions-user . I never used rebase myself, but my concern is that when merging next-moc back to master, will the master history be tainted by the rebase?

Ah! I just realized we don't need next-moc anymore, since we publish motoko release in the CDN! It always make sense to make a compiler release before developing new base libraries, and we can make sure CI is always run. WDYT?

Ah! I just realized we don't need next-moc anymore, since we publish motoko release in the CDN! It always make sense to make a compiler release before developing new base libraries, and we can make sure CI is always run. WDYT?

I think we still need next-moc – we want to be able to test and stage changes to motoko-base that correspond to breaking changes in the compiler before we release motoko, don’t we?

I think we still need next-moc – we want to be able to test and stage changes to motoko-base that correspond to breaking changes in the compiler before we release motoko, don’t we?

I would expect we already have some tests on the compiler side when having breaking changes. In the base repo, we will create a PR to bump the compiler release, making necessary changes for the library. The PR serves the purpose of testing and staging for motoko-base. Do I miss anything?

I think we still need next-moc – we want to be able to test and stage changes to motoko-base that correspond to breaking changes in the compiler before we release motoko, don’t we?

I would expect we already have some tests on the compiler side when having breaking changes. In the base repo, we will create a PR to bump the compiler release, making necessary changes for the library. The PR serves the purpose of testing and staging for motoko-base. Do I miss anything?

Or I miss something…
We want to be able  to run the test suite of motoko-base as part of compiler QA.
Now let’s say I rename func to function in our syntax. This requires motoko-base to change.
We cannot do these changes in motoko-base master, because then we would break everybody out there, there is no moc release that uses function.
We cannot do a release unless we test these changes.
So somewhere (not master) we need to stage the changes to motoko-base to test our current motoko/master before we release that. next-moc is the place to stage these changes… Is there a better place?

We cannot do a release unless we test these changes.

This is the part I don't understand. We have tests on the compiler side already. With these tests, we are already confident to merge the feature into master. Why afraid of doing a release? motoko-base is mostly a wrapper for Prim, and having this as part of the compiler QA doesn't add much to what we have already tested. If we are still concerned, we can release a internal/alpha version for moc, so the staging happens on the Motoko side, not in base.

This is the part I don't understand. We have tests on the compiler side already. With these tests, we are already confident to merge the feature into master.

We currently run motoko-base tests on every PR, too.

Why afraid of doing a release? motoko-base is mostly a wrapper for Prim, and having this as part of the compiler QA doesn't add much to what we have already tested. If we are still concerned, we can release a internal/alpha version for moc, so the staging happens on the Motoko side, not in base.

Andreas explicitly asked for this, and I tend to agree: Our tests in motoko/test are not that great, and not running the base test suite is a wasted opportunity. I remember at least one bug that only manifested due to including motoko-base tests (forgot which one).
Also, Prim doesn’t have a stable, document interface that could be tested against. Anst it is tied to motoko-base.
But yes, if we’d agree that motoko/test is sufficient, we would not need any of this.

We currently run motoko-base tests on every PR, too.

Ah this is what I missed. Yeah, then we do need next-moc. On the plus side, the two branches can be synced more frequently, as we control the release now.

So should we do this for each PR or as a daily sync?

Do we have to use a custom action, or can we avoid dragging such code around?
OTOH maybe I should learn how to write GitHub Actions, there is plenty for us to automize  :-)

Yeah, this is mostly me learning to write a custom action, and after I wrote it, I think we don't need custom action for this. Running a bash script directly in CI is probably enough.

Yeah, this is mostly me learning to write a custom action, and after I wrote it, I think we don't need custom action for this. Running a bash script directly in CI is probably enough.

What I meant was: Is there no off-the-shelf action that we can just invoke? I thought you started with one of those. Did it lack some feature we need? If so, maybe report that to the author of that Github action, maybe they can fix it.


List Index out of Range

Hi,
I ran your program on notebooks.zure.com. It worked fine when I used your bvh file but it thrown an IndexError: list index out of range. How can I fix this? My bvh file have a frame of 6000+
aaa.zip

ModuleNotFoundError: No module named 'pymo.parsers'?


Allow installation with php 7 (again)

This is currently possible up to v2.0.7 and was then blocked due to requiring ^5.5. So it is not possible to install the latest version for php 7 without --ignore-platform-reqs option.

@TheFrozenFire Can this be merged in 2.0 and be released?

@TheFrozenFire Thanks for merging. Is there a schedule for a 2.0.11 release to make all the latest changes available in a official version?


chore: replace standard version with custom script

What kind of change does this PR introduce?

Replacing standard version with a custom script. Move the changelog up to the root of the repository. This reduces the number of dependencies and allows us to create more tailored workflows in the future.
Status

[ ] Code documentation for the relevant parts in the code have been added/updated by the PR author
[ ] The functionality has been tested by the PR author
[ ] The functionality has been tested by NRK

Codecov Report

Merging #697 (7ad18aa) into release41 (654ab4a) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           release41     #697   +/-   ##
==========================================
  Coverage      69.75%   69.75%
==========================================
  Files            301      301
  Lines          33961    33961
  Branches        4624     4624
==========================================
  Hits           23690    23690
  Misses          9824     9824
  Partials         447      447

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 654ab4a...7ad18aa. Read the comment docs.

Ive only skimmed it while curious for how things had been approached, but looks like a good start :)

We intend to overhaul the changelogs in a different way than this PR, to be continued...


Reverting platform / custom call registration logic changes from the …

…22/05/30 sync

jenkins: retest Ubuntu-CPU please

jenkins: retest Ubuntu-CPU please

@ekuznetsov139 I wonder is this commit for fixing xla_jit_test?
As I am checking why this failed unit test (on upstream) can pass in our develop-upstream, it seems because this commit with platform instead of cuda.
But now this commit failed to light_outside_compilation after I cherry-pick this commit for upstream.


Rewrite sourcegen so we run it from bleep. Stabilize and polish

Things seem to work much, much better now.
The way I see it now there is only one problem left. When working with intellij and you update the build file and/or project selection, bleep will automatically reload it while intellij won't. A desync like this may obviously cause some grief. Bleep may for instance refuse to compile if you deselected a project which is still active in intellij.
I'll open a separate issue for that, not sure what to do about it for now.