drivers: can: rcar: remote transmission request filters are not supported

Some CAN controllers do not support all filter combinations (standard 11-bit ID filters, extended 29-bit filter, data frame filters, remote transmission request). Document the expected return value (-ENOTSUP) for unsupported filter types/combinations.
The receive path for the Renesas R-Car CAN controller supports two RX FIFOs, which are currently configured for standard 11-bit CAN ID data frames in FIFO0, and extended 29-bit CAN ID data frames in FIFO1. As this leaves no room for matching remote transmission request (RTR)frames, have the driver return -ENOTSUP instead of silently accepting RTR filters.
Skip the Remote Transmission Request (RTR) frame tests if the CAN controller driver does not support RTR filters.

Fixes: #50218

Marking as DNM until @aaillet has had a chance to test on R-Car hardware.

Another approach could be to configure the two RX FIFOs dynamically according to the first two filter types added and return -ENOSPC if trying to add additional filter types, but that would require much more house keeping for very little gain IMO. Using RTR is not recommended after all.


Make literal_pow generic on quantities, but specialize for dimensions

Also adds a broadcasting benchmark

Just missing the literal_pow for generic p for AbstractDimensions. But other than that looks good!

Thanks!


Add option to add "implicit" custom validation rules.

Hello,
First of all, great work with this library, it's made my life validating forms both server and client side a whole lot easier.
Since my goal is to use the same rules both server and client side there is only one feature I missed from Laravel's validator, which is the possibility to add what they call "Implicit rules" (it's in the docs at https://laravel.com/docs/5.4/validation under "Implicit Extensions", but it's basically custom rules which are run even when the attribute is null, undefined or empty).
I noticed you already had implemented the default implicit rules in your code, so I took the liberty to add a registerImplicit function which besides registering the rule adds it to the implicitRules array. Seems simple enough, and I tried to keep to the same API that was being used by registerAsync, and also added the same function for async rules.
As can be seen in the commit history, my first approach was to add an "implicit" argument to the register function, but to mirror Laravel Validator's API I thought separate functions was the way to go.
Anyway, I'll wait for feedback :)
I hope it can be merged and I'll be able to stop using my fork because I need these implicit rules.

@lordalaqua Thank you for this PR, it has been on the backlog for quite some time so this is a welcome addition.   If you wouldn't mind, can you please create an associated test to cover this PR and submit an update.
Thanks in advance...

Hi, I have added the tests as asked, I took a brief look over the existing tests and tried to follow them. I kept it minimal to try test only the "implicit" feature, that is, if the rules are checked when the value is undefined or null, so please let me know if you think these tests are enough or if there is anything else I can do. Glad to be of help :)

Any update on this?

@lordalaqua Sorry for delay, I will have a look at this a bit later today and act accordingly.

@lordalaqua Just merged, thanks for the PR :-)

Awesome, glad it was ok :smile: Thanks for the great work on the library!

Hi @lordalaqua  and @mikeerickson,
This new implementation was not added in the documentation

@alanhr want to add it for us? :)

@alanhr Thanks for information, I will get it added in due time :-)
In the meantime, if you are keep to post a PR, it will gladly be accepted!


Deprecate proof methods to prevent their usage [ECR-3786]:

Overview
The proof methods are temporarily deprecated till ECR-3666/ECR-2545.
All proof tests are disabled.
The tests of ProofList are re-enabled.

See: https://jira.bf.local/browse/ECR-3786
Definition of Done

[ ] There are no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

Coverage decreased (-0.1%) to 85.841% when pulling 9d0a9c1b9f1f182a77fd230c89fd2ef462ebe9b0 on dmitry-timofeev:deprecate-proofs-ECR-3786 into 4a8fabb8e22f7aa483d823447335657e4c172fd2 on exonum:master.


Deploy on github pages

So that the product owner can review :smile:

Move index.html file outside html folder to be able to deploy on github pages.

I'd set this as high priority as I think the aim is to hand the prototype over to the POs this evening.


beta JSON podspec is fetched with wrong 'source'

When I publish a beta podspec in JSON format, the pod repo-art update command fetches it with the source attribute wrongly pointing to the previous release.
Let me explain the steps to reproduce:

publish a pod with version 3.0.0 using a Ruby podspec (Framework-bin.podspec) like this:

Pod::Spec.new do |spec|

  spec.name                = 'Framework-bin'
  spec.version             = '3.0.0'
  spec.license             = 'MIT'
  spec.homepage        = 'https://www.mysite.com'
  spec.authors             = { 'Foo' =><EMAIL_ADDRESS>}
  spec.summary             = 'Framework'
  spec.platform            = :ios, '8.0'
  spec.ios.vendored_frameworks = 'Framework.framework'
  spec.source = { :http => "https://myartifactoryserver.com/artifactory/api/pods/mylocalrepo/pod/pkg/Framework-bin/3.0.0", :type => 'tgz'}

end

publish a pod with version 3.1.0-beta using a JSON podspec  (Framework-bin.podspec.json) like this:

{
  "name" : "Framework-bin",
  "version" : "3.1.0-beta",
  "summary" : "Framework",
  "homepage" : "https://www.mysite.com",
  "source": {
		"http": "https://myartifactoryserver.com/artifactory/api/pods/mylocalrepo/pod/pkg/Framework-bin/3.1.0-beta",
		"type": "tgz"
	},
  "license" : "MIT",
  "ios" : {
    "vendored_frameworks" : "Framework.framework"
  },
  "authors" : {
    "Foo"<EMAIL_ADDRESS>  },
  "platforms" : {
    "ios" : "8.0"
  }
}

update the local podspecs repo

pod repo-art update mylocalrepo

check the podspecs in the ~/.cocoapods/Repos/mylocalrepo/Specs folder. The podspec
for version 3.1.0-beta will have a source that points to 3.0.0!

{
  "name" : "Framework-bin",
  "version" : "3.1.0-beta",
  "summary" : "Framework",
  "homepage" : "https://www.mysite.com",
  "source": {
		"http": "https://myartifactoryserver.com/artifactory/api/pods/mylocalrepo/pod/pkg/Framework-bin/3.0.0",
		"type": "tgz"
	},
  "license" : "MIT",
  "ios" : {
    "vendored_frameworks" : "Framework.framework"
  },
  "authors" : {
    "Foo"<EMAIL_ADDRESS>  },
  "platforms" : {
    "ios" : "8.0"
  }
}

Notice that browsing the repo using the Artifactory repository browser, the tar.gz published have the correct source in the JSON podspec.
Therefore my guess is that the issue is in the REST API that downloads the full specs repo from Artifactory.

did you ever solve this? I have the same problem right now, and I would really like to release podspec.json files

I had this issue, and it would actually retrieve an entirely different CocoaPod instead of the one specified. I spent over three hours with JFrog support and they were never able to resolve it.
Artifactory indeed rewrites podspecs to change the source to the Artifactory instance, and in some cases it chooses the wrong artifact version, or even the wrong artifact.

Artifactory indeed rewrites podspecs to change the source to the Artifactory instance, and in some cases it chooses the wrong artifact version, or even the wrong artifact.

Just ran into this as well. This is undocumented and entirely unnecessary. It appears when the repo index is fetched from /api/pods/<repo-name>/index/fetchIndex the download includes podspecs that are modified.

Are you still seeing this? Also curious if you have multiple podspec files in your pod. I'm wondering because I am seeing this issue specifically with Firebase iOS SDK.
That project has many podspec files for a bunch of different stuff, and each one has its own tag. So FirebaseCrashlytics-8.2.0 will point to the tag Crashltyics-8.2.0. I will upload the correct podspec to artifactory, and it will look like this if you download it straight from the browser:
  "source": {
    "git": "https://github.com/firebase/firebase-ios-sdk.git",
    "tag": "CocoaPods-8.2.0"
  },

But when you run pod repo-art update <my-repo> and it changes the source to the pkg in artifactory, it looks like this:
"source": {
  	"http": "https://myartifactoryserver.com/artifactory/api/pods/mylocalrepo/pod/pkg/FirebaseABTesting/8.2.0",
  	"type": "tgz"
  },

And that is the case for all other Firebase iOS SDK podspecs too. They all get changed to FirebaseABTesting. Furthmore, if I try to use the following url to download FirebaseCrashlytics, it doesn't exist:
https://myartifactoryserver.com/artifactory/api/pods/mylocalrepo/pod/pkg/FirebaseCrashlytics/8.2.0

And if I try hitting the other FirebaseABTesting url, it gives me the last Firebase iOS SDK pod I uploaded. So it appears that https://myartifactoryserver.com/artifactory/api/pods/mylocalrepo/pod/pkg/FirebaseABTesting/8.2.0 is just being overwritten by whatever I uploaded last.
Not sure if this is the same as your issue, but it leads me to believe that cocoapods-art doesn't do well with multi podspec projects. Still looking to see if I can find more info that I've overlooked, but feel free to let me know if I'm missing something.

Hello,
this - reported 6 years ago - behaviour cost me multiple hours. As stated, this is not documented in any way.
In my case we have a big pod containing multiple vendored frameworks. The file structured looks like this:
A.podspec
frameworks/B.xcframework
frameworks/C.xcframework

Instead of this I now want to publish the frameworks separately:
B.podspec.json
frameworks/B.xcframework

C.podspec.json
frameworks/C.xcframework

But the fetchIndex endpoint always returns C.podspec.json with a source pointing to A even tho the name and version of the pod is different. When switching from C.podspec.json to the ruby format C.podspec it works as expected.
The artifactory documentation states that JSON format is supported therefore I would expect this to get fixed (especially for a paid software)
Current workaround: Don't use JSON format.


OperServ

Draft spec from @bogdomania:
/* ================ This is subject to change, at any time ====================
 *
 * All plausible commands, needed by the administrator and the tehnical staff.
 * More could be added, as a result of case-study, later on. Because OperServ
 * usage is available only to the staff, I belive that it should provide a
 * useful tool to manage the network health & security.
 * ----------------------------------------------------------------------------
   ADD          - adds a registered NickServ account to OperServ's staff list.
				  Network admin only.
 *-----------------------------------------------------------------------------
   AUTH         - Allows to an account to authenticate to OperServ.
 *-----------------------------------------------------------------------------
   DEL          - deletes an account from OperServ's staff list.
				  Network admin only.
 *-----------------------------------------------------------------------------
   EDIT         - modifies an existing account's entries, such as role, status
				  Network admin and OperServ admin only.
 *-----------------------------------------------------------------------------
   GLOBAL       - Sends a global announcement to the whole network, as a notice,
				  maybe useful for planned shutdowns, restarts, etc.
 *-----------------------------------------------------------------------------
   HUNT         - Hunts down a given user/account/hostmask/ident or all at once.
				  Initially, was a failsafe for a user that evades GLINE, but
				  this ideea could be implemented in ircd itself, rather than
				  OperServ. It could de CPU intensive, while active, to monitor
				  all the incoming connections, for a medium-large network.
				  With some things in place, such as +Z for connections,
				  SSL only and DNSBL working, most of these things should be
				  kept in control. Therefore, I'm not sure about this command.
 *-----------------------------------------------------------------------------
   LIST         - Lists all OperServ staff members along with their infos.
 *-----------------------------------------------------------------------------
   MEMO         - sends a persistent message to another OperServ staff, useful
  				  for when other members are offline, they will receive the
                  message as soon as they will log in.
 *-----------------------------------------------------------------------------
   SECLVL       - Implements a security level, in order to mitigate threats.
				  0 - Defaults to normal ( if a previous level was set )
				  1 - SCAN -> Just like below THREATMATRIX
				  2 - Monitors suspicious targets
				  3 - Disables services functionalities, like accounts
				      registrations and channels registration
				  4 - As above and sends to tehnical staff infos about every
					  future attempt of auth or service usage by other users !?
				  5 - Shuts down services functionalities alltogheter. Nothing
					  works for regular users, just for network staff. Also, it
					  logs all network traffic. It also blocks any future
					  incoming connections, except for excepted hosts.
 *-----------------------------------------------------------------------------
   THREATMATRIX - Now, this is my favourite. While scanning, it auto-detects
				  any incoming threats, like clone/bots attack, DoS, DDoS, etc.
				  After that, it informs the staff about it and either goes
				  straight to mitigate the attacks or asks for permission. Maybe
				  it can auto-set SECLVL to a predefined level? Oh, and most
				  important, it logs all the traffic, while in SecLvl mode.
				  Or, this can be passed to SecLvl, as in:
				  /OS SecLvl [mode] (0 to 5) 0 is off(if activated before) at 1
				  it just scans and if it detects something, it switches on to
				  the next level, or top level, depending on the threath.
				  It could also compare nickname/account/channels registered by
				  existing user(s) to hostmasks/ident/etc. of an attacker, as a
				  cross reference, so that the admin knows that an existing user
				  is (part of) the trouble.
 *-----------------------------------------------------------------------------

*/

See also #328.

Makes sense, I like these. As much as we can, let's keep our syntax similar to Anope/Atheme's OperServs

/msg OperServ list [param1] [param2]  where
[param1] is:
users         -   it will list all regular users registered
staff           -   it will list all staff members
channels   -   it will list all channels registered
[param2] is:
first            -   in ordered sequence, from oldest to newest (date wise)
last            -   in ordered sequence, from newest to oldest (date wise)
ordered     -   in ordered sequence, alphabetically (starting with letter A -> Z)
unordered -   in ordered sequence, alphabetically (starting with letter Z -> A)
Example:
/msg OperServ list users first

Username
Registered at

1 dan
Sun, 29 Dec 2019 11:04:14 UTC

2 slingman
Sun, 29 Dec 2019 11:04:14 UTC

3 turtlex
Sat, 04 Jan 2020 08:44:32 UTC

Example:
/msg OperServ list staff ordered

Username
Role
Flags

1 Anna
IRCop
+acjknoqtux

2 slingman
Admin
+acjknoqtux

Example:
/msg OperServ list channels unordered

Channel name
Registered at
Registered by
Successor

1 #Zone Gray
Tue, 24 Dec 2019 19:32:27 UTC
Benny
Nicole

2 #Gecko
Fri, 03 Jan 2020 14:44:52 UTC
turtlex
NONE

In case of thousands of nicknames (and maybe channels) should a filter be applied? like max=100?
Example:   /msg OperServ list users ordered max=200(or first 200), so that the output is not hairy?

This should be closed, since most if not all commands will be implemented directly in to ircd.

@jesopo suggests that global notices (#1153) could be given a friendlier interface as an OperServ command.


Example code in docs for Python code is rendered as markdown

Body
We use comments in some examples provided in the pydoc strings, e.g. in the client base class.
This is recognized by mkdocs as markdown syntax and therefore wrongly formatted as headings.
See the screenshot below:

Mentoring
As this ticket is marked as good first issue: @bossenti  or @kulbachcedric are happy to provide help for getting started, just tag (one of) them if you want to start working on this issue and need some help.
This issue might be a good issue for people interested in the StreamPipes Python client that already have some experience with Mkdocs.
StreamPipes Committer
I acknowledge that I am a maintainer/committer of the Apache StreamPipes project.

Hello, I would like to try and work on this issue. Are the comments supposed to be displayed on the page at all?

Hi @CryoSolace,
great that you are interested in contributing to StreamPipes 🚀
Here is one of the examples given in the pydocs:
Examples
--------

>>> from streampipes_client.client import StreamPipesClient
>>> from streampipes_client.client.client_config import StreamPipesClientConfig
>>> from streampipes_client.client.credential_provider import StreamPipesApiKeyCredentials

>>> client_config = StreamPipesClientConfig(
...     credential_provider=StreamPipesApiKeyCredentials(
...         username="test-user",
...         api_key="api-key"
...     ),
...     host_address="localhost",
...     https_disabled=True
... )

>>> client = StreamPipesClient.create(client_config=client_config)

# The above way of instantiating a client instance is intended
# to be consistent with the StreamPipes Java client.
# If you prefer a more pythonic way, you can simply write:
>>> client = StreamPipesClient(client_config=client_config)

# Interact with an endpoint
>>> data_lake_measures = client.dataLakeMeasureApi.all()

# Inspect returned data as a pandas dataframe
>>> data_lake_measures.to_pandas()

    measure_name timestamp_field  ... pipeline_is_running num_event_properties
0           test   s0::timestamp  ...               False                    2
[1 rows x 6 columns]

Would be great if the whole code snippet would be rendered correctly in the docs.
Please note our make commands for building the docs conventiently: make doc and make livedoc (see also here)
Is there anything else you need to get started?

Hi,
Thank you for responding. I would like to know how I can replicate and work
on the issue. I've tried cloning the project but I can't seem to get the
software running or open the docs.
In the mean time, would something like adding # # or # work?
Thanks.
On Sun, 1 Jan 2023, 17:24 Tim, @.***> wrote:

Hi @CryoSolace https://github.com/CryoSolace,
great that you are interested in contributing to StreamPipes 🚀
Here is one of the examples given in the pydocs:
Examples

from streampipes_client.client import StreamPipesClient
from streampipes_client.client.client_config import StreamPipesClientConfig
from streampipes_client.client.credential_provider import StreamPipesApiKeyCredentials

client_config = StreamPipesClientConfig(

...     credential_provider=StreamPipesApiKeyCredentials(
...         username="test-user",
...         api_key="api-key"
...     ),
...     host_address="localhost",
...     https_disabled=True
... )

client = StreamPipesClient.create(client_config=client_config)

The above way of instantiating a client instance is intended
to be consistent with the StreamPipes Java client.
If you prefer a more pythonic way, you can simply write:

client = StreamPipesClient(client_config=client_config)

Interact with an endpoint

data_lake_measures = client.dataLakeMeasureApi.all()

Inspect returned data as a pandas dataframe

data_lake_measures.to_pandas()

measure_name timestamp_field  ... pipeline_is_running num_event_properties

0           test   s0::timestamp  ...               False                    2
[1 rows x 6 columns]
Would be great if the whole code snippet would be rendered correctly in
the docs.
Please note our make commands for building the docs conventiently: make
doc and make livedoc (see also here
https://github.com/apache/streampipes/blob/dev/streampipes-client-python/Makefile
)
Is there anything else you need to get started?
—
Reply to this email directly, view it on GitHub
https://github.com/apache/streampipes/issues/962#issuecomment-1368492975,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX52KSTNPRG7LNFJN6CJGDDWQG4WPANCNFSM6AAAAAATNO2AHU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Alright, so let's assume you have cloned the streampipes repo in a directory called streampipes.
Then you can follow this steps:

go to /streampipes/streampipes-client-python
run pip install ".[docs]" to install the requirements for the docs ( as far as I know you can leave out the " in case you are on windows
run make livedoc to get the live docs served on http://<IP_ADDRESS>:8000/
In case make does not work for you, run the following commands:

mkdocs build
mkdocs serve --dirtyreload

Does that work for you?
Yes, or maybe just leave the # out... Feel free to try a few combinations if you want to :)
PS: I've assigned the ticket to you to indicate that you are on it
Thanks for your interest so far 👍🏼

Hi! Thanks for assigning the ticket. I was able to get it working, attached are some ideas. Which one would you rather have in?

I like the second one more, but how about you?
Which one would you prefer? Or would you make something completely different.
I'm happy to here your thoughts

I agree. I think it feels more like documentation and less like comments in the code. I have made a pull request for this. Let me know if I've made any mistakes or if you want to change anything. Thanks for letting me contribute.


Support for self service ui dynamic dialogs

This depends on both #6097 and #5872.
Something funky was happening with the specs so I'm still working on figuring that out, and since it depends on those other two PRs, I've marked this as WIP. However, with those other two PRs, this can still be tested in the UI to see if everything behaves properly.

@gmcculloug Specs have been updated. I'm still working on figuring out exactly what was going on with the issue you pointed out to me regarding the dialog not updating with the correct values, but if you wanted to open a separate bug around that instead of waiting, this should be ready to go once all checks are completed and green.


The convention invocations have reached the recursion limit.

When an owned entity (one that is marked with ComplexType attribute) that is a singleton property in a class and a list element in another class, Add-Migration will fail with the error 'The convention invocations have reached the recursion limit. This is likely an issue in EF Core, please report it.'
I have attached a zip file that contains a project that can reproduce this problem. It is at the bottom of this post. Just open the Package Manager console and type 'Add-Migration "testing"'. It should attempt to run but then cause an error.
Exception message: The convention invocations have reached the recursion limit. This is likely an issue in EF Core, please report it.
Stack trace:
System.InvalidOperationException: The convention invocations have reached the recursion limit. This is likely an issue in EF Core, please report it.
   at Microsoft.EntityFrameworkCore.Metadata.Conventions.Internal.ConventionDispatcher.ConventionBatch.Run()
   at Microsoft.EntityFrameworkCore.Metadata.Conventions.Internal.ConventionDispatcher.ConventionBatch.Dispose()
   at Microsoft.EntityFrameworkCore.Metadata.Builders.EntityTypeBuilder`1.OwnsOneBuilder[TRelatedEntity](PropertyInfo navigation)
   at Microsoft.EntityFrameworkCore.Metadata.Builders.EntityTypeBuilder`1.OwnsOne[TRelatedEntity](Expression`1 navigationExpression)
   at ConventionInvocationErrorExample.DatabaseContext.OnModelCreating(ModelBuilder builder) in C:\Users\User\Documents\Visual Studio 2015\Projects\ConventionInvocationErrorExample\ConventionInvocationErrorExample\DatabaseContext.cs:line 19
   at Microsoft.EntityFrameworkCore.Infrastructure.ModelCustomizer.Customize(ModelBuilder modelBuilder, DbContext dbContext)
   at Microsoft.EntityFrameworkCore.Infrastructure.ModelSource.CreateModel(DbContext context, IConventionSetBuilder conventionSetBuilder, IModelValidator validator)
   at Microsoft.EntityFrameworkCore.Infrastructure.ModelSource.<>c__DisplayClass5_0.<GetModel>b__0(Object k)
   at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
   at Microsoft.EntityFrameworkCore.Infrastructure.ModelSource.GetModel(DbContext context, IConventionSetBuilder conventionSetBuilder, IModelValidator validator)
   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.CreateModel()
   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.get_Model()
   at Microsoft.EntityFrameworkCore.Infrastructure.EntityFrameworkServicesBuilder.<>c.<TryAddCoreServices>b__7_1(IServiceProvider p)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitFactoryService(FactoryService factoryService, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.<>c__DisplayClass17_0.<RealizeService>b__0(ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetService[T](IServiceProvider provider)
   at Microsoft.EntityFrameworkCore.Design.Internal.DesignTimeServicesBuilder.<>c__DisplayClass6_0.<ConfigureContextServices>b__11(IServiceProvider _)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitFactoryService(FactoryService factoryService, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitTransient(TransientCallSite transientCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.<>c__DisplayClass17_0.<RealizeService>b__0(ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetService[T](IServiceProvider provider)
   at Microsoft.EntityFrameworkCore.Design.Internal.MigrationsOperations.EnsureServices(IServiceProvider services)
   at Microsoft.EntityFrameworkCore.Design.Internal.MigrationsOperations.AddMigration(String name, String outputDir, String contextType)
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.AddMigrationImpl(String name, String outputDir, String contextType)
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.AddMigration.<>c__DisplayClass0_1.<.ctor>b__0()
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.<>c__DisplayClass3_0`1.<Execute>b__0()
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.Execute(Action action)
The convention invocations have reached the recursion limit. This is likely an issue in EF Core, please report it.

Steps to reproduce
The Owned Entity:
namespace ConventionInvocationErrorExample
{
    [ComplexType]
    public class OwnedEntity
    {
        public string ExampleProperty { get; set; }
        public double ExampleProperty2 { get; set; }
    }
}

The Owning Entity 1 (has the OwnedEntity as a singleton):
namespace ConventionInvocationErrorExample
{
    /// <summary>
    /// This entity will only have the owned entity as a property
    /// </summary>
    public class OwningEntity1
    {
        public int ID { get; set; }
        public OwnedEntity OwnedEntity { get; set; }
    }
}

The Owning Entity 2 (has the Ownedentity as a list element):
namespace ConventionInvocationErrorExample
{
    /// <summary>
    /// This entity will only have the owned entity as a list of said entity
    /// </summary>
    public class OwningEntity2
    {
        public int ID { get; set; }
        public List<OwnedEntity> OwnedEntities { get; set; }
    }
}

The database context:
namespace ConventionInvocationErrorExample
{
    public class DatabaseContext : DbContext
    {
        protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        {
            optionsBuilder.UseSqlite("Data Source=database.db");
        }
        protected override void OnModelCreating(ModelBuilder builder)
        {
            // OwningEntity has OwnedEntity as a property
            builder.Entity<OwningEntity1>().OwnsOne(c => c.OwnedEntity);
        }
        public DbSet<OwningEntity1> OwningEntities1 { get; set; }
        public DbSet<OwningEntity2> OwningEntities2 { get; set; }
    }
}

Further technical details
EF Core version: 2.0.0-preview2-24617
Database Provider: Microsoft.EntityFramework.Sqlite
Operating system: Windows 10 Pro v. 15063
IDE: Visual Studio 2015
Convention Invocation Error Example.zip

@op-erator Owned type collections are not currently supported. Remove this line:
public List<OwnedEntity> OwnedEntities { get; set; }

Thank you. Currently, I changed OwnedEntity to a entity that has an ID property. While it doesn't create the database that we wanted, at least when owned type collections are supported, it will be easier to migrate to the correct database form as the application isn't in production yet.
Thank you for working on it. I am glad you guys are actively working on this project.

@op-erator If you just want an entity without a key property you can create a shadow property for it:
builder.Entity<OwnedEntity>(b =>
{
    b.Property<int>("ID");
    b.HasKey("ID");
});

and then configure the foreign key to use this property. This is what is done for owned entity types by convention.


ES6 modules!

The goal for ECMAScript 6 modules was to create a format that both users of CommonJS and of AMD are happy with:
Similar to CommonJS, they have a compact syntax, a preference for single exports and support for cyclic dependencies.
Similar to AMD, they have direct support for asynchronous loading and configurable module loading.
Being built into the language allows ES6 modules to go beyond CommonJS and AMD (details are explained later):
Their syntax is even more compact than CommonJS’s.
Their structure can be statically analyzed (for static checking, optimization, etc.).
Their support for cyclic dependencies is better than CommonJS’s.
The ES6 module standard has two parts:
Declarative syntax (for importing and exporting)
Programmatic loader API: to configure how modules are loaded and to conditionally load modules
so, is it possible to use ES6 modules with this starter kit? it will be awesome, thanks man.

You mean import Something from "something"; ? I have plans to use that syntax in the future, when Babel.js supports importing it like Something is an const/immutable symbol.

Relates to https://github.com/babel/babel/issues/954

great @RickWong
keep it up! :+1:


org_inventory_backup.py doesn't backup switches and gateways

When I try to execute the org_inventory_backup, I'm expecting to get the full list of inventory. That should include the devices (ap), the switches and the gateways.
Current implement seams to only backup the devices (ap) without any listing of the switch and gateway.

Hi Patrik,
I'll add the switches and gateways this week.

ok great, can't way to test it.


Permanently disable

Currently there are API methods for enable/disable/toggle, but it "auto enables" at least on ModeChanged, si it is a little bit confusing (or at least it was for me). It would be great if there would be an option to permanently disable diagnostics.
Also, it would be nice if there would be an option to disable by default, although it might be something more specific for my use case.
I use this plugin in conjunction with lsp_lines. I have a keymap that toggles both, so when I need the verbosity (and that fancy line to a specific part of the code) I use lsp_lines but when it is too much noise (and takes up too much space) I toggle both and use this awesome plugin to nicely show the diag message.

That was a bug, thanks for pointing it out.
Can you try updating and tell me if it is good on your side? The API should now do what it is supposed to do!

Yes, it is working now, thank you for the quick fix! I thought it is a feature :smile:


Generated Go *.pb.go refers to a non-go-getable package.

What version of CUE are you using (cue version)?

$ cue version
cue version devel linux/amd64

Does this issue reproduce with the latest release?
Yes
What did you do?
Created a proto file for my dataset. This can be reproduces with the following proto:
"dataset.proto"
syntax = "proto3";
package protos;

import "cue/cue.proto";
option go_package = "my.org/protos";

message Test {
  string test = 1;
}

I ran protoc on this with the following commands:
include = ${GOPATH}/src/cuelang.org/go/encoding/protobuf

protoc \
  -I=./protos \
  -I=${include} \
  --go_out=./protos \
  --go_opt=paths=source_relative \
  dataset.proto

Note: I tried withouth source_relative as well.
This created the following (abridged) dataset.pb.go:
// Code generated by protoc-gen-go. DO NOT EDIT.
// versions:
// 	protoc-gen-go v1.25.0
// 	protoc        v3.6.1
// source: dataset.proto

package protos

import (
	_ "cuelang.org/cueproto"
	proto "github.com/golang/protobuf/proto"
	protoreflect "google.golang.org/protobuf/reflect/protoreflect"
	protoimpl "google.golang.org/protobuf/runtime/protoimpl"
	reflect "reflect"
	sync "sync"
)

const (
	// Verify that this generated code is sufficiently up-to-date.
	_ = protoimpl.EnforceVersion(20 - protoimpl.MinVersion)
	// Verify that runtime/protoimpl is sufficiently up-to-date.
	_ = protoimpl.EnforceVersion(protoimpl.MaxVersion - 20)
)

// This is a compile-time assertion that a sufficiently up-to-date version
// of the legacy proto package is being used.
const _ = proto.ProtoPackageIsVersion4

type Test struct {
	state         protoimpl.MessageState
	sizeCache     protoimpl.SizeCache
	unknownFields protoimpl.UnknownFields

	Test string `protobuf:"bytes,1,opt,name=test,proto3" json:"test,omitempty"`
}

What did you expect to see?
The problem is the import  "cuelang.org/cueproto" refers to a package that's not go-getable.
$ go get cuelang.org/cueproto
go get cuelang.org/cueproto: unrecognized import path "cuelang.org/cueproto": reading https://cuelang.org/cueproto?go-get=1: 404 Not Found

What did you see instead?
I would expect the generated pb to refer to a path that I could access, but that module doesn't appear to be accessible.
I'm guessing that refers to a package under "cuelang.org/go/encoding/protobuf", as that's where the proto file was, but that refers to it's go_package as "cuelang.org/cueproto".
Perhaps I am missing something, but I am stumped.

Where are you doing your protobuf work from?
Are you accidentally picking up this file? https://github.com/cuelang/cue/blob/master/encoding/protobuf/cue/cue.proto

@verdverm, sorry, somehow I didn't notice this...
I didn't make this clear in my original description, but I'm applying cue constraints in my actually application and using that to generate a schema. E.g.:
message Dataset {
  // machine parsable dataset name
  string name = 1 [(cue.val) = '=~"^[a-z0-9]+(?:-[a-z0-9]+)*$"'];
}

So I guess I'm not accidentally picking up that file, that's an explicit import since I need it for my constraints/schema gen.

This is probably related to #450.
The respective proto is in encoding/protobuf/cue/cue.proto, so you'll have to include that in your path when evaluating.
Suggestions on how to make this clearer or what would be a better approach is welcome.

This issue has been migrated to https://github.com/cue-lang/cue/issues/581.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


ext-TimeInterval

Previously known as ext-PeriodOfUse. It is incorporated in the branches for:

zib-AdministrationAgreement
zib-MedicationAgreement
zib-MedicationUse
zib-DispenseRequest

Merge into branch MedicationProfiles.


UndoRedo.add_do_method fails when arguments are null

Godot version:
3.2.4
Issue description:
UndoRedo.add_do_method throws an error:
add_do_method: Condition "action_level <= 0" is true.
<C++ Source>  core/undo_redo.cpp:112 @ add_do_method()
if any parameter is null:
func create_action():
	call("multiple_parameters") # fails, not enough arguments
	call("multiple_parameters", null, null) # works

	undo_redo.add_do_method(self, "multiple_parameters") # fails, as expected
	undo_redo.add_do_method(self, "multiple_parameters", null, null) # also fails
	undo_redo.add_do_method(self, "multiple_parameters", null, "some value") # also fails

func multiple_parameters(arg1, arg2):
	pass

Steps to reproduce:
Call UndoRedo.add_do_method with null as one parameter.

Similar to https://github.com/godotengine/godot/issues/36895 ?

Similar to #36895 ?

Yep :D


Add serve config and update routes

Made two changes:

added directories with index.html for routes like testnet & jobs so that going to codaprotocol.com/testnet doesn't 404 like it does now -> tested on staging (see screenshot below)
added serve.json config to add trailing slashes so that testing locally mirrors prod more (still not 100% consistent, but it helps)

This is pretty cool, I wonder if it accomplishes a similar purpose to change the serve config to closer match firebase's behaviour
{
  "trailingSlash": true,
  "cleanUrls": false,
  "rewrites": [
    {"source": "/", "destination": "/index.html"},
    {"source": "/blog", "destination": "/blog/index.html"},
    {"source": "/docs", "destination": "/docs/index.html"}
  ]
}

(Probably can do something regex-y for those rewrites but I was too lazy and I think that's all of them for now, was too lazy to figure out https://github.com/pillarjs/path-to-regexp)

Resolved merge conflicts, and also updated header links


throw VE when attacks to run is specified but version is not 'custom'

it was quite confusing to me that when i specified attacks to run, it would just overwrite that unless i also specified another argument.

Hi,
thanks for the contribution! Sounds a good idea to me. However, the attacks get overridden if the version is one of those predefined here https://github.com/fra31/auto-attack/blob/6482e4d6fbeeb51ae9585c41b16d50d14576aadc/autoattack/autoattack.py#L65
Then, I'd replace version != 'custom' with version in <list of versions> as condition to raise the VE. What do you think?

agreed :)

Any version which is non predefined shouldn't override it. The idea was to leave the option to each user of adding new versions, on top of the default ones.


python3Packages.{pygtrie, betacode}: init

Motivation for this change
Things done

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

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

[x] 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 nixpkgs-review --run "nixpkgs-review wip"
[ ] 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)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

getting this error for betacode on python2:
builder for '/nix/store/7cc9snhy0kjsskb77mb23fm2z8f03rr9-python2.7-betacode-1.0.drv' failed with exit code 1; last 10 log lines:
  Executing setuptoolsBuildPhase
  Traceback (most recent call last):
    File "nix_run_setup", line 8, in <module>
      exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\\r\\n', '\\n'), __file__, 'exec'))
    File "setup.py", line 22, in <module>
      long_description = read('README.rst'),
    File "setup.py", line 14, in read
      with open(os.path.join(os.path.dirname(__file__), fn), encoding='utf-8') as f:
  TypeError: 'encoding' is an invalid keyword argument for this function
  builder for '/nix/store/7cc9snhy0kjsskb77mb23fm2z8f03rr9-python2.7-betacode-1.0.drv' failed with exit code 1
cannot build derivation '/nix/store/shllrgfahfx5di0vpkigkq0s5znwncp5-env.drv': 1 dependencies couldn't be built

maybe disable it on python2?

maybe disable it on python2?

done :heavy_check_mark:


Improvement/modernizing keep deep reference equality

Problem:
The keepDeepReferenceEqualityIfPossible utility function did not support ES6 maps.
Fix:
A new version of the original https://github.com/epoberezkin/fast-deep-equal/ have been released since then. I copied the new source code and adopted it the same way we did with the original keepDeepReferenceEqualityIfPossible
Commit Details:

keepDeepReferenceEqualityIfPossible now supports ES6 Maps and Sets
I changed the valueStackSoFar to be a Set to avoid having Array.prototpye.includes iterate over the entire array. I also mutate the valueStackSoFar to avoid having to clone the object for every recursion

I believe I fixed all outsanding requests


[Feature] Min-cut / Max-flow

Potential implementations:

A Distributed Mincut/Maxflow Algorithm Combining Path Augmentation and Push-Relabel
A distributed algorithm for min-max tree and max-min cut problems in communication networks

Hi @drfloob,
thanks for opening this issue. Are the proposed algorithms single-pass and streaming? Or can they somehow be extended to work in the gelly-stream model?


Update README.md

update readme file to reflect the big changes we're making to incuna-sass by removing compass and moving legacy files to their own folder
@incuna/frontend please review :)

@pandalion fixed :)


VW: add MY23 Crafter FW

Update Fingerprint with MY23 Crafter,
The route is here: af1bf21a07172228|2023-06-28--21-00-49--0

@chzollib if you have a route for the other FW, we can add that in a new PR


Status Field: is being referred to Enabled Field: in UI after Auth

Rancher Version: master 6/15
Steps to Reproduce:

Authenticate using AD or LDAP

Results: In the Authentication section under Users columns, there is a field called "Enabled Field:", this field is called "Status Field:" before you auth.

Expected:  Either call both Status Field or Enabled Field

@tfiduccia Looks like it was resolved with commit #413d73b

Version - v1.1.0-rc3
Verified fixed


Check translation into Japanese

#952

Guide: https://pr-preview-962-ja-quarkusio.surge.sh/guides/quartz


Use SQL DB to store TODOs

Instead of using dict to store TODOs, use a sql db instead.

@devloai review this pull request

@devloai review this pull request. Include code suggestions where applicable


Remove namespace from ContentPacketExtension

This commit sets the namespace of the ContentPacketExtension to null. This was causing issues when parsing the jingle session-initiate message with stanza.io. The namespace was being set on content elements inside a group which stanza.io would fail to parse.
According the group XEP there usually isn't a namespace on the content elements (https://xmpp.org/extensions/xep-0338.html), and the namespace currently doesn't show up on the content elements inside the jingle element in the session-initiate message. (smack 4.2 might be doing something smart to remove a child element's namespace if it is the same as the parent).
More details in this discussion: https://community.jitsi.org/t/jitsi-dev-custom-client-fails-to-parse-jingle-session-initiate-with-new-jicofo/13992
Ran tests in jitsi-videobridge, jicofo, jicoco, and jigasi and all passed.

@bgrozev @bbaldino WDYT?
I think this is safe and this was the way it used to be prior smack4 update.

so do we not need to set the namespace based on its usage? (i.e. ingo's comment here)

Yep, I'm not sure about that.
But if smack is removing namespace when they match the parent as @jahndis reported,
then defining two namespaces in ContentPacketExtension and make namespace as a required constructor parameter and passing the correct one depending on the usage will be a better approach. WDYT?
@jahndis can you try that?

How does this affect parsing?

Sorry for the delay in response. I was sick for a couple days and then on vacation through the rest of the week.
I made the changes you recommended, and reran the tests (all passed). Let me know if there's anything else needed.


Multiple select height issue

When using a multi select, I  can't properly change the height.
.select2-container--default .select2-selection--multiple {
.select2-container .select2-selection--multiple {
min-height: ;
}
doesn't go below its default 32px; when changed to anything lower ie 26px;
changing all margin-top to 0px; and removing all padding from the stylesheet doesn't help. and I use a reset stylesheet.
Not being able to change the height I have to align the selected grey boxes and the input height to vertical align with margin-top, but this always results in extra "padding" on the bottom, adding anything bigger than margin-top: 5px; and the select box gets bigger, meaning the padding still stays.
tldr; min-height does nothing, and centering the crap inside still results in extra "padding-bottom" and the select2.css stylesheet is an unfathomable nightmare.
Would just like a 26px height multi select box, with the selected options being 22 - 24px height and vertical centered.

If you want to disable the "extra" height (the 7px) select2 adds when using multi-select option I think this css might do the trick and it won't mess up the style of your dropdown list. Took me a while to figure it out.
.select2-container--open .select2-selection__rendered{
border: none;
}
.select2-container .select2-search--inline{
display: none;
}

The only way I found is to set something like:

@korent Hi! Your code worked for me but because of display: none, the placeholder text is not showing. I tried to add it to data-placeholder with jQuery, but initiating select2 seems to ignore prior javascript set on the select input... any ideas to show the placeholder text?

Can reproduce the issue with this JSFiddle. Do you know if you plan on fixing this issue?

up

FOUND CSS SOLUTION:
The issue is with
.select2-container .select2-search--inline .select2-search__field {
box-sizing: border-box;
border: none;
font-size: 100%;
margin-top: 5px; <!---- THAT GUY
padding: 0;
}
TO FIX:
Simple set it to 0px. Very odd behavior. Works in Chrome, Firefox, Safari (latest versions on windows)

Codepwned2  has the best answer. It is working like a charm now.

I think the Codepwned2 answer does not apply any longer.

I have fixed it with this
body .select2-container .select2-selection--multiple .select2-selection__rendered {
display: inline;
}
body .select2-container--default .select2-selection--multiple .select2-selection__rendered li {
margin: 3px;
}
body .select2-container--default .select2-search--inline .select2-search__field {
margin: 0;
max-height: 1em;
padding: calc(1em - 2px);
}
.select2-container {
min-width: 100%;
max-width: 100%;
border: 1px solid #aaa;
border-radius: 4px;
}
.select2-container--default.select2-container--focus .select2-selection--multiple, .select2-container--default .select2-selection--multiple {
border: none;
}


Compiler doesn't work offline neither in PWA.

Shifting compilation from online to client side is very crucial..
Otherwise it makes the PWA app useless...
Please allow the Service worker to handle compilation offline on the Client side once the resources are loaded..

Right now the playground is in a good enough shape to be as accessible as possible to most users. On slow connection it might take a while on first load but then should be rather fine on subsequent ones.
Making it 100% offline requires quite some tinkering that I simply do not have the time to tackle as of now.
That being said, I'm 100% open to PR :)

I understand the first load is a bit slow.. but its not all that kind of a big deal.. my problem is after making changes to the code after going offline, i realized each compilation cycle per code change required some form of network access.. 😅.. anyway.. hoping it becomes 100%  offline soon in the future


Deploy not completing with s3 as object store

$ git push deis master
Warning: Permanently added '[deis.krancour.deis.ninja]:2222,[<IP_ADDRESS>]:2222' (RSA) to the list of known hosts.
Counting objects: 75, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (48/48), done.
Writing objects: 100% (75/75), 18.28 KiB | 0 bytes/s, done.
Total 75 (delta 30), reused 58 (delta 22)
remote: 2016/03/18 03:47:28 Running in debug mode
Running git hook
read [0000000000000000000000000000000000000000,5450cbcdaaf9afe6fadd219c94ac9c449bd62413,refs/heads/master]
Controller request /v2/hooks/push (body elided)
Controller request POST /v2/hooks/config
{"receive_user":"kent","receive_repo":"linear-mackinaw"}
got the following config back for app linear-mackinaw: {Owner:kent App:linear-mackinaw Values:map[] Memory:map[] CPU:map[] Tags:map[] UUID:04cb6424-56ad-4646-98c1-da1641df793c Created:2016-03-18 03:47:20 +0000 UTC Updated:2016-03-18 03:47:20 +0000 UTC}
running [git archive --format=tar.gz --output=linear-mackinaw.tar.gz 5450cbcd] in directory /home/git/linear-mackinaw.git
running [tar -xzf linear-mackinaw.tar.gz -C /home/git/linear-mackinaw.git/build/tmp051936082/] in directory /home/git/linear-mackinaw.git
create bucket error: Your previous request to create the named bucket succeeded and you already own it.
Uploading tar to https://s3.amazonaws.com/kents-builder/home/linear-mackinaw:git-5450cbcd/tar
Starting build... but first, coffee!
Starting pod slugbuild-linear-mackinaw-5450cbcd-0dda850a
Pod spec: {
  "metadata": {
    "name": "slugbuild-linear-mackinaw-5450cbcd-0dda850a",
    "namespace": "deis",
    "creationTimestamp": null,
    "labels": {
      "heritage": "slugbuild-linear-mackinaw-5450cbcd-0dda850a"
    }
  },
  "spec": {
    "volumes": [
      {
        "name": "minio-user",
        "secret": {
          "secretName": "minio-user"
        }
      }
    ],
    "containers": [
      {
        "name": "deis-slugbuilder",
        "image": "quay.io/deisci/slugbuilder:git-6dce113",
        "env": [
          {
            "name": "DEBUG",
            "value": "1"
          },
          {
            "name": "TAR_URL",
            "value": "https://s3.amazonaws.com/kents-builder/home/linear-mackinaw:git-5450cbcd/tar"
          },
          {
            "name": "put_url",
            "value": "https://s3.amazonaws.com/kents-builder/home/linear-mackinaw:git-5450cbcd/push"
          }
        ],
        "resources": {},
        "volumeMounts": [
          {
            "name": "minio-user",
            "readOnly": true,
            "mountPath": "/var/run/secrets/object/store"
          }
        ],
        "imagePullPolicy": "Always"
      }
    ],
    "restartPolicy": "Never",
    "serviceAccountName": ""
  },
  "status": {}
}

+ app_dir=/app
+ build_root=/tmp/build
+ cache_root=/tmp/cache
+ buildpack_root=/tmp/buildpacks
+ mkdir -p /app
+ mkdir -p /tmp/cache
+ mkdir -p /tmp/buildpacks
+ mkdir -p /tmp/build/.profile.d
+ gcs=storage.googleapis.com
+ MC_PREFIX='mc --quiet -C /app/mc_config'
+ [[ -z https://s3.amazonaws.com/kents-builder/home/linear-mackinaw:git-5450cbcd/tar ]]
+ [[ -e /var/run/secrets/object/store/access-key-id ]]
+ [[ -e /var/run/secrets/object/store/access-secret-key ]]
++ cat /var/run/secrets/object/store/access-key-id
+ keyID=AKIAIUHEZQS3NI4TN4LQ
++ cat /var/run/secrets/object/store/access-secret-key
+ secretKey=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
++ echo https://s3.amazonaws.com/kents-builder/home/linear-mackinaw:git-5450cbcd/tar
++ awk -F/ '{print $1}'
+ protocol=https:
++ echo https://s3.amazonaws.com/kents-builder/home/linear-mackinaw:git-5450cbcd/tar
++ awk -F/ '{print $3}'
+ domain=s3.amazonaws.com
+ '[' s3.amazonaws.com = storage.googleapis.com ']'
+ mc --quiet -C /app/mc_config config host add https://s3.amazonaws.com AKIAIUHEZQS3NI4TN4LQ 3QEZwQr4vaMl2ZqHXaak34xodfjmr8WAEmgSMBXE
+ mc --quiet -C /app/mc_config cp https://s3.amazonaws.com/kents-builder/home/linear-mackinaw:git-5450cbcd/tar /tmp/slug.tgz
size of streamed logs 1229
Waiting for the deis/slugbuild-linear-mackinaw-5450cbcd-0dda850a pod to end. Checking every 100ms for 15m0s
Done
remote: 2016/03/18 03:47:41 Error running git receive hook [Build pod exited with code 1, stopping build.]
Checking for builder pod exit code
To ssh://git@deis.krancour.deis.ninja:2222/linear-mackinaw.git
 * [new branch]      master -> master

@krancour the line that reads + '[' s3.amazonaws.com = storage.googleapis.com ']' is suspect. Can you show what environment variables you've set on the builder RC?

I uninstalled a while ago and have re-installed since with minio as the object storage.  Let me try this again... that said... yes... that line looks a lot like I botched the config!  :frowning:

@krancour command will fail if kents-builder is not in us-east-1

Oh... @smothiki nice catch.  That;s probably it.

@smothiki after further testing, I don't think the region is the problem-- builder actually is successful at putting the tarred up application source into the bucket.  I think, perhaps, the problem is slugbuilder isn't successfully retrieving from there?
@arschles this problem is persisting with good configuration-- or I think it's good.  Have a gander... these are what I added to the builder container:
            - name: DEIS_OUTSIDE_STORAGE
              value: s3.amazonaws.com
            - name: BUCKET
              value: kents-builder

For  slugbuilder we need region specific URLs. Also I'm not getting why builder is successful. Might be some logic added to identify bucket region in minio-go cli .

I'll try this with a bucket in a different region to see how that goes.

can you try with a bucker from us-east-1

Yep.  Just tried with a bucket in us-standard (which is use-east-1) and everything worked fine.  I'm going to close this since we're already tracking multi-region bucket in a different issue.  We should probably just note this limitation in the documentation.

thanks @krancour!


Use LazyPromise?

public function __invoke(Message $message, Deferred $deferred = null):?Promise
{
    $needReply = (bool) $deferred;
    // stripped code.
    if ($needReply) {
        return new LazyPromise(function() use ($deferred, $reply) {
            $value = JSON::decode($reply->receive($this->replyTimeout)->getBody());

            try {
                $deferred->resolve($value);
            } catch (TimeoutException $e) {
                $deferred->reject($e->getMessage());
            }
        });
    }

But this is a BC an can only be done with a new major release.

for ref https://github.com/reactphp/promise/issues/95

'''
(bool) $deferred;
'''
?

Added a comment in the linked reactphp issue. LazyPromise does not really help and the code above won't work I guess.
See the reactphp example of LazyPromise
The factory (callback passed to LazyPromise) needs to create its own deferred and return the promise of that deferred.
So you cannot resolve the deferred injected by the query bus. But only the injected deferred has a connection to the promise returned by the query bus. I <3 async code ...

Can this be closed then?

issue is still discussed. Own LazyPromise implementation could provide the wanted behavior. See linked reactphp issue

There is no possibility to set a custom promise to the deferred given as argument (the interface does not allow it). We could achieve what we want if prooph producer interface defines a promise as a return value. I guess the deferred could be removed in that case.
It is BC break though


TypeError: nextytext.toDelta is not a function or its return value is not iterable

Crash caused by upgrading to 1.2.11
Checklist

[X] Are you reporting a bug? Use github issues for bug reports and feature requests. For general questions, please use https://discuss.yjs.dev/
[X] Try to report your issue in the correct repository. Yjs consists of many modules. When in doubt, report it to https://github.com/yjs/yjs/issues/

Describe the bug
TypeError: nextytext.toDelta is not a function or its return value is not iterable shows on performing a specific action in the editor.
This caught error escalates to a crash on other actions (eg changing page)
I added some console logging in sync-plugin.js on my machine (logging out the type & nextytext):

And get these logs - showing an instance where nextytext does not have a toDelta function.

The command function here is the one that triggers the error for me. There must be more than one user collaborating at the same time for the bug to occur

I've patched the error locally via

To Reproduce
Apologies that I don't have a simple example case for this
Steps to reproduce the behavior:

Two users in collaboration
Open console
Perform action that results in a nextytext that does not have a toDelta function (eg a YXmlElement)
See error

Expected behavior
Would not expect a strict requirement for nextytext to have a toDelta function
Screenshots
Added above
Environment Information

node v22.4.0
chrome 127.0.6533.99 (Official Build) (arm64) (but it occurs across many setups
yjs 13.6.18
y-indexeddb 9.0.12
y-partykit 0.0.31
y-protocols 1.0.6
<EMAIL_ADDRESS>
Additional context

[ ] I'm a sponsor 💖
[ ] This issue is a blocker for my project.

I am also getting this issue when trying to copy an editor's contents to another using this:
xml2.insert(
    0,
    xml1
	.toArray()
	.filter((item) => !(item instanceof XmlHook))
	.map((item) => item.clone()),
);

Thank you for the bug report. The issue should be fixed in the latest release (1.2.12). Thanks to @manstie  we have a bugfix.  Please let me know if there is still an issue.


fix: Update CI/CD pipeline and semantic-release configuration

Description
This pull request updates the GitHub Actions workflow and semantic-release configuration to improve the release automation process.

GitHub Actions Workflow (.github/workflows/release.yml):

Added a step to create a Pull Request for automated releases, ensuring better control and review before merging.

semantic-release Configuration (.releaserc.json):

Adjusted plugin settings to ensure correct commit and push behavior.
Configured the @semantic-release/github plugin to include CHANGELOG.md as an asset in the GitHub release.

Type of Change

[ ] New feature
[x] Bug fix
[ ] Refactor
[ ] Documentation update
[ ] Other (please describe):

Checklist

[x] My code follows the project’s coding style
[x] I have performed a self-review of my code
[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have updated the documentation as necessary
[x] My changes generate no new warnings or errors
[x] I have checked my code and corrected any misspellings
[ ] Any dependent changes have been merged and published in downstream modules

Related Issues

No related issues.

Additional Information
These changes enhance the automation of the release process by ensuring that Pull Requests are created for all automated releases and that the CHANGELOG.md is correctly managed and included in GitHub releases.

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add feature to find "stale" containers

If the assets are updated (kernel + rootfs image), there should be a way to determine which containers that were running at the time of the asset updated are now "stale" (really need to be restarted to take advantage of the new assets for functionality/performance/security improvements).
The simplest solution is a script, but a better way is to modify list --cc-all to show whether the assets used for each container are current or not.

@grahamwhaley - as discussed on #631, I know your view on making the list output even longer. However, the output is already wrapping for me so I'm inclined to just add the extra fields. What we can do to alleviate the problem of long output lines:

Once #668 lands, the output of list will be saner as the number of columns will be fixed. It's then a simple matter of (ironically :-) running a 1-line awk script on the output of list --cc-all to pull out the fields you only want to see.

Alternatively, we could consider a separate PR to add a new list --format=csv for example to make it even easier to parse.

A potentially better alternative to list --format=csv might be to add a list --separator=<char> which would only apply to the default table output and would allow you to specify say a single space or a single tab to separate columns. This coupled with a CC_RUNTIME_SEPARATOR=char would allow you to have a persistent way not having to type lots of cli options to get the output you want.

we could go crazy and offer a --cc-format-string="%s\t%s ..." type feature.

As it minimises adding extra code paths, I'm going to raise a PR that just adds the extra fields for now.

tailing note after merge/close...
I'm not that against the long output - just noted that it is already rather long :-)
As you've now fixed the format, we can call it 'parseable', and thus I don't think at this point in time we need to add any more format output options - let's reserve that for the future if we get any user requests for it etc.

Agreed.


Should 0.6.0-alpha still be used?

Hi,
When i started using this crate, version 0.6.0-alpha was the latest stable release on crates. Now 0.5.0 is marked as the latest stable release. Is 0.6.0-alpha abandoned?

@gengliqi will help release 0.6.0 in this month.

Hi
Is there any new progress? Is 0.6.0 safe to use now?

0.6.0 was just released.


RNGoogleSignInEvents.swift:11:29: Use of undeclared type 'RCTEventEmitter'

Can't get past this error on iOS.
Have followed all given instructions, but this doesn't seem to be working.

@heroic As per the README, add to your Swift Bridging Header, {YourApp}/ios/{YourApp}-Bridging-Header.h:
#import <React/RCTBridgeModule.h>
#import <React/RCTViewManager.h>
#import <React/RCTEventEmitter.h>
#import <GoogleSignIn/GoogleSignIn.h>

Or, if you are using RN <= 0.39:
#import "RCTBridgeModule.h"
#import "RCTViewManager.h"
#import "RCTEventEmitter.h"
#import <GoogleSignIn/GoogleSignIn.h>


Visualize Interactions

Given a file containing a list of bacteria and the phages they interact with ( #16 ), it would be very cool to have a way of visualizing this. The best practical implementation might depend on how many bacteria and phages we're dealing with. This issue is wide open to all kinds of ideas and playing around.
Nice features would include a way of indicating the number of hits between each bacteria and phage, i.e. if one bacteria species contains many spacers from the same phage, this should show up in the visualization as a "strong" interaction. One idea, suggested by @BillMills, is a colour scale indicating strength of interaction.
One of the relevant biological answers to gain from a visualization like this is whether or not there are clusters - are there small subsets of bacteria and phages that only interact with each other? The answer we expect is yes, since bacteria and phages typically inhabit small environmental niches and few species inhabit many different environments.
@BillMills has created a demo visualization in webGL for a few bacteria and phages that can be found at visualization/demo.html.

A good first pass at visualization was completed with the help of cytoscape.js during the Toronto Open Science Code Sprint. Relevant files can be found in the visualization folder, and instructions for use are in the ReadMe.
Future work along these lines will probably involve just a bipartite matrix, so this issue can be closed.

Check out the 'concentric' layout in cytoscape.js - it seems like a good one to work with bipartite data.


boxes: 2.3.0 -> 2.3.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ascii-boxes/boxes/releases.
meta.description for boxes is: Command line program which draws, removes, and repairs ASCII art boxes
meta.homepage for boxes is: https://boxes.thomasjensen.com
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.3.1 with grep in /nix/store/0yv2gmfcgkcgyajp4d5gkmy364v996vp-boxes-2.3.1
found 2.3.1 in filename of file in /nix/store/0yv2gmfcgkcgyajp4d5gkmy364v996vp-boxes-2.3.1

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

boxes

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0yv2gmfcgkcgyajp4d5gkmy364v996vp-boxes-2.3.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/7159ef060a63249b7b7640c244b97efaf9f20f40#boxes

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0yv2gmfcgkcgyajp4d5gkmy364v996vp-boxes-2.3.1
ls -la /nix/store/0yv2gmfcgkcgyajp4d5gkmy364v996vp-boxes-2.3.1/bin

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

1 package built:

boxes

Maintainer pings
cc @waiting-for-dev for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

Result of nixpkgs-review pr 346166 run on x86_64-linux 1

1 package built:

boxes


The demo.rs example crashes

If I do cargo run --example demo
it crashes immediately, like this:

Hey! I didn't actually expect anyone to test this project out so soon :sweat_smile:. Yes, not everything is implemented yet (mainly support for dynamic generation of nodes, and most style properties). Things like ECS access, the ECS hooks, click event handlers, and support for basic nodes and the rsx! macro works. For loops do not. If you want to test this project out, try reducing the example a bit and remove the for loop. It'll take some time, but I've been fleshing things out pretty quickly :)

hahah no worries, I just stumbled upon your post in the thread about UI support in the Bevy repo and I wanted to give it a quick try. Just to try out this dioxus library, as I've heard of it but never used it
I will give a try to simplify the demo and play with it. Thx!

I've fixed a bunch of bugs and implemented some more missing features. Please try the demo now. Note, that it's expected that it will segfault when closing the app.


Method (78) requires at least one network adapter available

Repro:

On already installed windows:

open device manager
click View -> Show hidden devices
uninstall all devices under Network Adapters section

By creating new VM:
in network type section choose Do not use a network connection

Hello,
it is obvious that network authentification will not work without actual network and it is assumed by default just like if target machine should have monitor or CPU. The real drawback of this method is password requirement, everything else does not. In any case if there is no network adapter this method will simple fail with API returned status which I can add as method result in the next update.


PR: Enforce 150ms delay when starting conda qprocess

Stops immediate call to _communicate when making a conda worker, and lengthens the timer check on the same; may solve https://github.com/ContinuumIO/navigator/issues/289 , @goanpeca

@goanpeca, please don't forget to tag things with the current Milestone so we can create Changelogs with the script I mentioned :-)

Ok :-)


display settings: Change twenty four hour time label to timeformat

This PR change display settings label "24-hour time (17:00 instead of 5:00 PM)" to dropdown box "Timeformat". I've made change for backend and frontend. I created new model field timeformat with string type and deleted old twenty_four_hour_time. By default user get timeformat from default_twenty_four_hour_time in Organization settings.
Testing
I changed backend and frontend tests for new model field. All tests are successful.
GIF

@krotovkk thanks for working on this!  A few notes:

Can you include a link to the issue in the PR description and mark this as closing that in the commit message?  Check out the Zulip commit message guidelines for more details: https://zulip.readthedocs.io/en/latest/contributing/version-control.html#commit-messages
I had been imagining we'd just change the UI model to a dropdown, keeping the data model both in the database and in the API as a boolean; which I think lets us skip about half the changes in this PR.  @rishig just to confirm, was that what you had in mind as well?  If so, @krotovkk it'd be great if you can remove that part of the changes.

I think eventually we will want it to be non-boolean, to support different date formats as well. But for the immediate issue leaving it as a boolean is fine.
We should also remember to change the organization settings version of this to a dropdown.

@rishig I don't think that reasoning applies for this setting.  First, there are really only 2 valid "time format"s: 12-hour and 24-hour, and that's what this field is.  For displaying dates, we use the browser's configured locale, and there isn't really a standard format for specifying those other than a locale or a format string (%YYYY %MM %DD sort of thing).  So I don't think there's a world in which we'd ever want this "Time format" field to have an enumerated list of time formats (which is why I can't think of other products that do that).
Hence, we should keep our time format field in the original boolean form in the database.

Makes sense. Let's go with boolean.

@timabbott thanks for review, I'll remove wrong part and make changes, that you noted


Use pkg/compare generated comparison functions in newResourceDelta

Part of https://github.com/aws-controllers-k8s/community/issues/757
This patch links pkg/compare and pkg/resource/delta.go, by importing
and reusing the generated comparison functions in delta.go. For now it
only import/reuse struct type comparison functions.
Example of the new generated Go code:
if !svccompare.IsEqualCodeSigningPolicies(a.ko.Spec.CodeSigningPolicies, b.ko.Spec.CodeSigningPolicies) {
	delta.Add("Spec.CodeSigningPolicies", a.ko.Spec.CodeSigningPolicies, b.ko.Spec.CodeSigningPolicies)
}

Example of the old generated Go code for the same service/block:
if ackcompare.HasNilDifference(a.ko.Spec.CodeSigningPolicies.UntrustedArtifactOnDeployment, b.ko.Spec.CodeSigningPolicies.UntrustedArtifactOnDeployment) {
	delta.Add("Spec.CodeSigningPolicies.UntrustedArtifactOnDeployment", a.ko.Spec.CodeSigningPolicies.UntrustedArtifactOnDeployment, b.ko.Spec.CodeSigningPolicies.UntrustedArtifactOnDeployment)
} else if a.ko.Spec.CodeSigningPolicies.UntrustedArtifactOnDeployment != nil && b.ko.Spec.CodeSigningPolicies.UntrustedArtifactOnDeployment != nil {
	if *a.ko.Spec.CodeSigningPolicies.UntrustedArtifactOnDeployment != *b.ko.Spec.CodeSigningPolicies.UntrustedArtifactOnDeployment {
		delta.Add("Spec.CodeSigningPolicies.UntrustedArtifactOnDeployment", a.ko.Spec.CodeSigningPolicies.UntrustedArtifactOnDeployment, b.ko.Spec.CodeSigningPolicies.UntrustedArtifactOnDeployment)
	}
}

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/hold

/close


suppress(ImportError) vs ModuleNotFoundManager

... and other tricks to

handle errors wit less of the try/except boilerplate
manage package dependencies dynamically (i.e. without imposing them in the install requirements)

see (for example in oui):
ModuleNotFoundIgnore
ModuleNotFoundManager

contextlib.suppress does "exactly" what ModuleNotFoundIgnore does -- use that instead.
contextlib doesn't seem to have the equivalent of ModuleNotFoundManager


Way to Use Playlist Instead of Artist List?

Is there a way to use a playlist ID from the iTunes API instead of several artist ID's?
This would make it a lot easier to add songs to the game and be more specific with the songs that we want in there instead of just having it randomly do artist's songs.
Any help with implementing this would be much appreciated!
Thank you!

It should be possible but you have to write your own script to do that. For example https://itunes.apple.com/lookup?id=303171368 returns a specific track by its id. The tool included in this repo was only added to show how songs are saved in the database. How to pick songs it's completely up to you.
The example script is not very hard to understand, the important part is this https://github.com/lpinca/binb/blob/e2c700da189b64fa4b8728ae8ae3e816a1904a42/util/load_sample_tracks.js#L61-L73. For simplicity assume that only the 'mixed' exists and it should be straightforward.


feat!: remove dataprocessor checks and support bundle tasks

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact<EMAIL_ADDRESS>with any additional questions or comments.
Thank you for contributing to Azure IoT Operations tooling!
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
Intent for Production

[ ] It is expected that pull requests made to default or core branches such as dev or main are of production grade. Corollary to this, any merged contributions to these branches may be deployed in a public release at any given time. By checking this box, you agree and commit to the expected production quality of code.

Basic expectations

[ ] If introducing new functionality or modified behavior, are they backed by unit and/or integration tests?
[ ] In the same context as above are command names and their parameter definitions accurate? Do help docs have sufficient content?
[ ] Have all the relevant unit and integration tests pass? i.e. pytest <project root> -vv. Please provide evidence in the form of a screenshot showing a succesful run of tests locally OR a link to a test pipeline that has been run against the change-set.
[ ] Have linter checks passed using the .pylintrc and .flake8 rules? Look at the CI scripts for example usage.
[ ] Have extraneous print or debug statements, commented out code-blocks or code-statements (if any) been removed from the surface area of changes?
[ ] Have you made an entry in HISTORY.rst which concisely explains your user-facing feature or change?

Azure IoT Operations CLI maintainers reserve the right to enforce any of the outlined expectations.
A PR is considered ready for review when all basic expectations have been met (or do not apply).

int tests: https://github.com/c-ryan-k/azure-iot-ops-cli-extension/actions/runs/9780324132

Also looks like the title regex check isn't happy about the ! breaking change signifier (though it is valid), will fix

will we remove --include-dp from init?

Yes

will we remove --include-dp from init?

We'll likely need to do some other init updates so that can happen in a separate PR - this won't stop it from deploying, it will just remove the checks and support bundles for it.


PSR-1298 PoC for separate no view in same controller

Closed, as different approach has been taken


incorporate autotag into CI

Currently when we sync from gitlab to github this function is called which creates the needed tag and propagates it further. When we sync from github to gitlab it doesn't happen - https://github.com/manticoresoftware/columnar/blob/975172c5920292921f503f6e49b4ffde26624626/.github/workflows/mirror.yml#L28-L33
The task is to fix it.

Done in https://github.com/manticoresoftware/columnar/commit/5578d8326e68d627ae6c1c75d120c91877f4d2aa

Please fix the issues https://github.com/manticoresoftware/columnar/commit/5578d8326e68d627ae6c1c75d120c91877f4d2aa

Done in https://github.com/manticoresoftware/columnar/pull/45
I didn't use there --follow-tags flag, because it doesn't work property .


Delay when using Transport.start() and Midi files

I am aware of Issue #369 but this may be slightly different as I am using a Tone.Sampler and Midi files.
I have created a minimal page in the fiddle, where you can upload a MIDI file and have the Tone.Sampler play the track after creating a piano.
It works perfectly, except there seems to be a huge delay between starting the transport, and the library actually playing the track.
https://jsfiddle.net/p7renax0/11/
Is there something I should be doing differently to mitigate the issue?
Notes:

I am using the latest Google Chrome on windows

The longer the page stays open, the longer the delay is. Sometimes it appears to not be working.

You're scheduling the transport time relative to Tone.now(). Tone.now() is the AudioContext time which starts from 0 and counts up while the context is running. Transport.schedule has it's own time scale which it controls. So if you change line 23 from }, note.time + now); to }, note.time); when scheduling the event, it should work.

Makes sense. Worked beautifully, thank you!


Cast error

Class: SumLambdaExample
line: final KStream<Void, Integer> input = builder.stream(NUMBERS_TOPIC);
this declaration makes application crash due to a ClassCastException when SumLambdaExampleDriver sends data. It tries to convert Integer (the type of the key) to type Void.

PR: https://github.com/confluentinc/kafka-streams-examples/pull/403


fix(jsx-email): revert excluding jsx-email+react during build. fixes #137

Component / Package Name: jsx-email
This PR contains:

[x] bugfix
[ ] feature
[ ] refactor
[ ] documentation
[ ] other

Are tests included?

[ ] yes (bugfixes and features will not be merged without tests)
[x] no

Breaking Changes?

[ ] yes (breaking changes will not be merged unless absolutely necessary)
[x] no

If yes, please include "BREAKING CHANGES:" in the first commit message body, followed by a description of what is breaking.
List any relevant issue numbers: fixes #137

Description
This commit https://github.com/shellscape/jsx-email/commit/e0a7eb44a96b85fed54d918bd3a05b788606267d#diff-956e216fa7df03ccf64dcfcbe8fdacf5560897b6726255ff29c1c3c8cc757721R124 had the goal of reducing the size of the intermediary template output file which esbuild produces, and thus increasing speed. Unfortunately the way that pnpm, yarn, and npm differ in how they create binaries in node_modules/.bin causes an issue where yarn and npm have no idea about the path context of where the intermediate file will be run, hence it can't find node_modules and jsx-email.
Under pnpm, the binary file in node_modules/.bin contains path information whereas npm and yarn are just straight up copies of the target file. Under pnpm, the compiled template file has context as to where it's being run, so it can use the local node_modules. Apparently on npm/yarn, this is not the case.

Should be all set on 1.7.3


Preserve space and comments after import in RemoveImport

If the removed import was a static import and was followed by a separating blank line, that blank line would be collapsed. Also if the removed import was followed by a comment, that comment would be lost.
This commit addresses these two issues by:

not overwriting the prefix spacing if it'd remove whitespace
only copy whitespace from removed import, don't overwrite comments

Checklist

[x] I've added unit tests to cover both positive and negative cases
[x] I've read and applied the recipe conventions and best practices
[ ] I've used the IntelliJ IDEA auto-formatter on affected files

Quality work here @tobli ! Thanks for adding these fixes and the detailed description of your intention here and in the test cases added. I'm tagging @traceyyoshima just in case I'd missed something; he seems to have added the conditional on line 146 that's removed.
https://github.com/openrewrite/rewrite/blob/3da2178f7ca70d421175e9cc6471e478ff63081e/rewrite-java/src/main/java/org/openrewrite/java/RemoveImport.java#L145-L149
Otherwise ok to merge on my end; appreciate you matching our code style too in your changes!

Thanks!
I replaced the conditional, and the counting of line breaks, with the length check when applying the leftover white space. It's not exactly identical, the new code handled some scenarios better. That said, there are some edge cases where some more complex conditionals (combining the two approaches) would be even more correct, but I found this to be a pragmatic trade off. Very much open to tweaking that however, so appreciate the review.

Hi @tobli, thank you for creating this PR! I think Jonathan added the condition, regardless, the case that the original code covers is mixed CRLF and LF, and trailing whitespace.
I.E. if the removed prefix is \n\n and the current prefix is \r\n or \n  \n, the condition will fail. I think mixed whitespace is common enough that we should cover those cases.

@traceyyoshima totally valid points, I adapted and added some test cases that should cover those cases.

@traceyyoshima @timtebeek anything more you'd like to see in this PR for it to be ready?


XLA Operation Semantics documentation has self-conflict

URL(s) with the issue:
https://www.tensorflow.org/xla/operation_semantics#slice
Description of issue (what needs changing):
Clear description
the number of parameters are not match.

Hey, stride is an optional argument here, it can be used if you want to slice your array with some step-gaps

@junqinyang, Sorry for the late response.
Thank you for reporting the bug. PR has been submitted internally on successful merge this issue will be closed automatically.


feat: add --tmux flag (deprecates sk-tmux, fixes #596)

The e2e are pretty basic but they should let us check the most delicate edge cases together with the unit tests

Locking the PR until the tests are there

@LoricAndre, FYI https://github.com/ibhagwan/fzf-lua/commit/d9db3b684384bcfd1393914b76f89f0205f183a3 added tmux support, all that's needed is to add the --tmux flag, either to setup or via command line, for example:
:FzfLua files fzf_opts.--tmux=center,40%,40%  fzf_bin=sk

The result:

I did discover one issue with tmux integration regarding the customization of the bg color which doesn't cover the entrire tmux popup, for example:
sk --height=100% --tmux center,40%,40% --color="bg:#ffcb8b"

Doing so with fzf yields:

TYSM for being so quick to react !
The BG thing is a bit weird, looks like the text is colored, not the window.
Given that I'm rewriting the entire UI right now, I think it will stay that way for now unfortunately, unless someone else opens an issue about it.

TYSM for being so quick to react ! The BG thing is a bit weird, looks like the text is colored, not the window. Given that I'm rewriting the entire UI right now, I think it will stay that way for now unfortunately, unless someone else opens an issue about it.

No biggie as this is easily avoidable by not theming the background, just FYI.
Good luck on the rewrite and ty for your hard work  🙏


Support old Exif Versions

Currently Exif Version 3.0 is supported.
Its published in May, 2023.
A lot of images might be taken before May, 2023.
So, Old Exif Versions should be supported.
For example, GPSAltitudeRef takes different meaning between Exif Version 3.0 and older version Exif.

Exif Version 3.0:

0: above ellipsoidal surface
1: below ellipsoidal surface
2: above sea level
3: below sea level

Exif Version 2.3 or older:

0: above sea level
1: below sea level

I've found Exif Versions from my image stock:

0210
0220
0221
0230
0231
0232


[tool_crash] ArgumentError: Invalid argument(s): Cannot find executable for /Users/apple/MyComputer/DriveA/FlutterSDK/bin/cache/artifacts/engine/android-arm64-release/darwin-x64/gen_snapshot.

Command
flutter --quiet assemble --depfile /Users/apple/MyComputer/DriveC/FlutterProjects2021/OpenGovFlutter/build/app/intermediates/flutter/release/flutter_build.d --output /Users/apple/MyComputer/DriveC/FlutterProjects2021/OpenGovFlutter/build/app/intermediates/flutter/release -dTargetFile=lib/main.dart -dTargetPlatform=android -dBuildMode=release -dTrackWidgetCreation=true -dTreeShakeIcons=true android_aot_bundle_release_android-arm android_aot_bundle_release_android-arm64 android_aot_bundle_release_android-x64

Steps to Reproduce

...
...
...

Logs
ArgumentError: Invalid argument(s): Cannot find executable for /Users/apple/MyComputer/DriveA/FlutterSDK/bin/cache/artifacts/engine/android-arm64-release/darwin-x64/gen_snapshot.
#0      _getExecutable (package:process/src/interface/local_process_manager.dart:124:5)
#1      LocalProcessManager.start (package:process/src/interface/local_process_manager.dart:40:30)
#2      ErrorHandlingProcessManager.start.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:638:33)
#3      _run (package:flutter_tools/src/base/error_handling_io.dart:532:20)
#4      ErrorHandlingProcessManager.start (package:flutter_tools/src/base/error_handling_io.dart:638:12)
#5      _DefaultProcessUtils.start (package:flutter_tools/src/base/process.dart:472:28)
#6      _DefaultProcessUtils.stream (package:flutter_tools/src/base/process.dart:491:35)
#7      GenSnapshot.run (package:flutter_tools/src/base/build.dart:73:26)
#8      AOTSnapshotter.build (package:flutter_tools/src/base/build.dart:194:56)
#9      AndroidAot.build (package:flutter_tools/src/build_system/targets/android.dart:232:52)
#10     _BuildInstance._invokeInternal (package:flutter_tools/src/build_system/build_system.dart:796:27)
<asynchronous suspension>
#11     Future.wait.<anonymous closure> (dart:async/future.dart)
<asynchronous suspension>
#12     _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:734:32)
<asynchronous suspension>
#13     Future.wait.<anonymous closure> (dart:async/future.dart)
<asynchronous suspension>
#14     _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:734:32)
<asynchronous suspension>
#15     FlutterBuildSystem.build (package:flutter_tools/src/build_system/build_system.dart:563:16)
<asynchronous suspension>
#16     AssembleCommand.runCommand (package:flutter_tools/src/commands/assemble.dart:220:32)
<asynchronous suspension>
#17     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1157:12)

[✓] Flutter (Channel stable, 2.0.3, on macOS 11.2 20D64 darwin-x64, locale en-GB)
    • Flutter version 2.0.3 at /Users/apple/MyComputer/DriveA/FlutterSDK
    • Framework revision 4d7946a68d (5 months ago), 2021-03-18 17:24:33 -0700
    • Engine revision 3459eb2436
    • Dart version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/apple/Library/Android/sdk
    • Platform android-S, build-tools 30.0.3
    • Java binary at: /Users/apple/Library/Java/JavaVirtualMachines/corretto-1.8.0_292/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment Corretto-8.292.10.1 (build 1.8.0_292-b10)
    • All Android licenses accepted.

[✗] Xcode - develop for iOS and macOS
    ✗ Xcode installation is incomplete; a full installation is necessary for iOS development.
      Download at: https://developer.apple.com/xcode/download/
      Or install Xcode via the App Store.
      Once installed, run:
        sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
        sudo xcodebuild -runFirstLaunch
    ✗ CocoaPods not installed.
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To install see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 92.0.4515.107

! Doctor found issues in 2 categories.

Flutter Application Metadata
Type: null
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: null
Creation framework version: null
Plugins
cloud_firestore-0.12.11
firebase_auth-0.11.1+12
firebase_core-0.4.5
firebase_core_web-0.1.1+2
firebase_messaging-6.0.16
flutter_inappwebview-4.0.0+4
flutter_plugin_android_lifecycle-1.0.11
fluttertoast-3.1.3
image_picker-0.6.7+22
path_provider-1.6.28
path_provider_linux-0.0.1+2
path_provider_macos-0.0.4+8
path_provider_windows-0.0.5
share-0.6.5+4
shared_preferences-0.5.12+4
shared_preferences_linux-0.0.2+4
shared_preferences_macos-0.0.1+11
shared_preferences_web-0.1.2+7
shared_preferences_windows-0.0.2+3
url_launcher-5.7.10
url_launcher_linux-0.0.1+4
url_launcher_macos-0.0.1+9
url_launcher_web-0.1.5+3
url_launcher_windows-0.0.1+3
webview_flutter-1.0.7
youtube_api-0.8.0

@AnkitInvoked
This issue was fixed as part of #68475.
I recommend you to upgrade to latest stable (2.2.3) or latest master and try again to see it work properly.
Closing as this is already fixed. If after upgrading to latest versions, you still see the issue, write in comments and I'll reopen.


New AMQP binding and transport.

Improved pkg/bindings/amqp based on the pkg/binding toolkit
Re-implemented cloudevents/transport/amqp over the binding, deprecate eventually.
Future AMQP features to consider:

generic and AMQP support for request/response special case used by knative filters.
support for QoS1 with AMQP
security TLS/SASL
easy access configuration (JSON mashallable config struct)

Fixes #180

Current commit 7f74b22 is a working pkg/bindings/amqp binding using the new pkg/binding API. I will replace the pkg/cloudevents/transport/amqp transport with it next, that will complete this issue.

Snuck one more doc update doc/README.md - was out of date wrt recent changes.
I think I need an LGTM to merge this?

/lgtm
On Wed 9. Oct 2019 at 20:21, Alan Conway<EMAIL_ADDRESS>wrote:

Snuck one more doc update doc/README.md - was out of date wrt recent
changes.
I think I need an LGTM to merge this?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/cloudevents/sdk-go/pull/208?email_source=notifications&email_token=AABGPTW7KHGDTUURTXEAH4TQNYOLBA5CNFSM4I2FEQ6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAY2YYI#issuecomment-540126305,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABGPTRQ7O4JP7FTDZZ24QLQNYOLBANCNFSM4I2FEQ6A
.

--
Sent from Gmail Mobile


D401 raised on classes and modules in v 0.0.230

Hi, just reporting that v. 0.0.230 raises a D401 for classes and modules too. Is this on purpose?

Ah I thought we had fixed that in #2071! Do you mind linking a snippet to reproduce? Thanks :)

Oh wait, sorry, that commit didn't make it into v0.0.230.

I will cut v0.0.231 now.

@charliermarsh I think the v0.0.231 release failed because github terminated it after 6 hours: https://github.com/charliermarsh/ruff/actions/runs/3989207120/jobs/6841354318

Oh thank you, let me try it again.

Ok, release is out, hopefully fixed!