Fix client creation bugs

Fixes a bug where specifying device path and type instead of fingerprint would not work. Fixes #59.
Return the connection error message from get_client() instead of printing it. Additionally, detect when get_client() fails and error on that instead of having something else error when a non-client object is returned.

much easier to think about, concept ACK. Will test.

tACK


React native with detox

Context
https://input-output.atlassian.net/browse/LW-5012
Proposed Solution
Important Changes Introduced

Thanks for the contribution @wklos-iohk!
I need to review this in more depth, but from my quick scan, this code should be added to the e2e package, as it's here only to support testing IIUC. The only time we'd need a mobile packages is if there's code that applications will use. Is that the case?

@rhyslbw
It's related to https://input-output.atlassian.net/browse/LW-5012
Should I put the mobile folder directly under /cardano-js-sdk/tree/master/packages/e2e?

@wklos-iohk yes, that's where we we're expecting this :+1:

I think the setup should be the same as with our web-extension test: packages/e2e/test/mobile

CI is failing @wklos-iohk


proposal: all, x/build/cmd/relui: automate go directive maintenance in golang.org/x repositories

Abstract
The value of the go directive in golang.org/x repositories is automatically maintained to be at least 1.(N-1).0, where Go 1.N is the most recent major Go release, and Go 1.(N-1) is the previous major Go release.
Background
In the beginning, there was the GOPATH mode and versions of dependencies of golang.org/x repositories weren't explicitly tracked. Go 1.11 introduced the module mode, and over time it became the default mode. All golang.org/x repositories had an initial go.mod file checked in, and that file was maintained manually. This meant that a bug fix or a new feature in one golang.org/x repository didn't benefit another golang.org/x repository until someone chose to manually update that dependency. It also meant that eventual updates sometimes jumped many versions at once to catch up. This was resolved in 2022, when an automated monthly relui workflow began to create tags and update golang.org/x dependencies across all golang.org/x repositories (issue #48523).
At this point there are upwards of 35 golang.org/x repositories. Owners of each repository update the "go" directive manually, ad-hoc, so golang.org/x repositories may receive different levels of "go" directive maintenance. For example, owners of the golang.org/x/mod module wished to use the new-to-Go-1.22 go/version package as soon as Go 1.23 came out, and so its "go" directive was recently updated to "1.22.0". On the other hand, golang.org/x/image hasn't been updated in a while, and its "go" directive is currently still at "1.18", which itself was an upgrade from "1.12" in CL 526895 as part of bringing all golang.org/x repos to use at minimum Go 1.18 language version (issue #60268).
Leaving go directive maintenance to be done entirely manually creates the possibility of some repositories staying on an older Go language version longer. When there's enough of a need to finally upgrade it to a recent Go language version, this requires a change across multiple major Go releases at once, which can be harder to review. Having continuous, smaller incremental upgrades requires creating many CLs for all of golang.org/x repositories every 6 months, which is toilsome if always done manually.
Design
Design document at go.dev/design/69095-x-repo-continuous-go.
CC @golang/release.

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

I think we should perhaps emphasize that once the go.mod go directive is updated to Go version 1.N-1.X, is our policy is going to be that package maintainers in that module should feel free to also break the build at older Go versions. This is  implied by the reference to using the go/version package, but should be highlighted.
For example, right now x/telemetry has 1.20 in its go.mod file, but still builds with 1.19 (and this "feature" will still be relied upon by v0.16.2 of gopls, which is the final version of gopls supporting building with 1.19, before #65917 takes effect).
With that said, I think this proposal is good for the Go overall. Not only will it reduce the toil of go directive maintenance, but it will also help eliminate significant complexity in these repositories related to build support for older Go versions. Additionally, with the help of all the work that has been done to make it easier to use a recent Go toolchain, I think this policy may indirectly help nudge the ecosystem away from using unsupported versions of Go.

Based on the discussion above, this proposal seems like a likely accept.
— rsc for the proposal review group
The proposal is https://github.com/golang/go/issues/69095#issue-2490518612.

If/when this proposal is accepted, we should add links to the statement of the new policy from the Go 1 compatibility promise and from the Go release policy, to ensure it is discoverable. (And perhaps from the README or go.mod file  in the root of each x/ repo.)

For libraries, I think not aggressively forcing upgrades on dependencies is a good thing, and so is staying compatible for more than 2 versions, when 1.23 is just released for instance, probably 1.20 should still be the most recent "forced" upgrade
So imo go.mod go line should just be the language features, not compiler bug fixes etc... that's handled by toolchain and build in final product and govulncheck.
An example of disruptive forced upgrade is x/tools 0.25 which suddenly jumped form go 1.19 to go 1.22(.0) for seemingly no "need"
Specifically I think a lot of even the newer libraries really only need "go 1.18", ie generics and should stay that way.
That is not to say that people shouldn't be using a recent, supported, fully patched go version (eg 1.22.7 at time of this writing), yet libraries should indicate language issue (ie that they are or are not yet using a new iterator etc) not push a cascade of updates downstream

An example of disruptive forced upgrade is x/tools 0.25 which suddenly jumped form go 1.19 to go 1.22(.0) for seemingly no "need"

It might appear that there was no need because x/tools was working fine with go1.19 only a few weeks ago. But the fact that it was continuing to build with go1.19, when the only supported Go toolchains at that time were go1.21 and go1.22 (and pre-go1.23), was imposing a significant burden on those of us who work in x/tools and those who work on the toolchain (since they had to be careful not to break x/tools). It has been a significant drag on the whole team for a number of years, and was in fact part of the genesis of the forward compatibility system.


Send client user-agent during connection, via CLIENT SETINFO

Description

Describe your pull request here

client is able to provide it's "user agent" to redis server.
Checklist

[x] Does npm test pass with this change (including linting)?
[x] Is the new or changed code fully tested?
[ ] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

closes #2573
closes #2612
closes #2456

@sjpotter please add the new options to the options table here


WebJob Environment Variables

It would be very helpful to support at least Environment Variables that can be utilized within the scripts.
Is there a way to do this now, or is this a feature request?

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

ID: 24523dbf-010f-b844-5ff0-88192eac8849
Version Independent ID: d7ef5962-d94c-96d0-bf08-1efffc6d402b
Content: Run Background tasks with WebJobs - Azure App Service
Content Source: articles/app-service/webjobs-create.md
Service: app-service
GitHub Login: @ggailey777
Microsoft Alias: glenga;msangapu;david.ebbo;suwatch;pbatum;naren.soni;

@ericnewton76 Thanks for the feedback! We are currently investigating and will update you shortly.

Create a powershell script with Get-ChildItem Env: and upload that as a webjob. Check the logs to see what's there. I guess there are no promises they will stick around...

@ericnewton76 Please let us know if Joseph's response does not resolve the question.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Correct erroneous defaults in some speed attrs.

What's New?

Correct some old values that had speed set to 800 to 100. These are relics from the days when speed was step/mm rather than a percentage.

Coverage remained the same at 80.426% when pulling 75c86169680035c728e30a16e35f168929bcb119 on RickCarlino:staging into 0080ec87a8f396552befe64d2f17882f68abc4a9 on FarmBot:staging.

Coverage remained the same at 80.426% when pulling 75c86169680035c728e30a16e35f168929bcb119 on RickCarlino:staging into 0080ec87a8f396552befe64d2f17882f68abc4a9 on FarmBot:staging.


Being able to create k8s internal service to custom process types

The use case is the following, I have an app that I want to put behind a oauth2_proxy, I wanted it to work this way:
I create an app in Deis, e.g. my-app
I have 2 process types in my-app, cmd: running oauth2_proxy and backend: running the app itself
If it was possible to have an internal k8s service for backend process, I would be able to expose cmd normally and proxy requests from cmd to backend internally.
Is it possible today? If not, I think that it would be a nice feature to add.
regards

We had looked at that and decided each application would get a service but not the various process types within the application.
You'd have to split this into 2 apps and use routing:disable to keep one of them from the public

I see, what a pity then, I think it would be cleaner to have all my app's components contained only in one app
Can't this be reconsidered? Is there any strong technical reason for not doing this?

@felipejfc One of the problems is do we create a service for all process types or not? Which then turns into do you have enough IPs available to you to support that?
Do we make it an opt-in for non-web/cmd (the ones that get a Service for now) to get past the IP problem mentioned above. This could be a viable option but is a complication as well

I think that a opt-in would be awesome, because it is not an essential feature in most of the cases but can be VERY handy in some others... We're using Deis for 1 month now and already hitted this issue twice, for now we are solving the problem running 2 processes inside the same container (because we didn't wanted to create 2 apps), but running 2 processes within the same container is dirty too...
Doesn't sound like something so hard to implement I think I could try to make a PR here if you guys agree and maybe give a little direction.

@felipejfc If you want to try it then that's great! But any functionality that has to do with process types is inherently more complicated than at first blush since you need to handle internal data much differently.
This would involve changes to the Controller, the SDK and CLI
What is the downside of creating 2 apps to solve for this? Additional images created and such management problems?

Here are two tickets worth reading: https://github.com/deis/controller/issues/883 and https://github.com/deis/controller/issues/656

Having to deal with 2 apps instead of one, 2 deploys instead of one, and most a question of principles, I guess. I'm not confortable with having to split the same app's components in two apps.
Hmm, I see, the port's question is really something that we would need to deal with. I don't like the solution of just opening all ports because of security... but maybe leaving this decision to the user would be enough. I'll give it some thinking and will close this issue for now, if I come with something good I'll reopen it. Thanks!

@felipejfc Sounds good! Thanks for understanding. If we get past a few of these hurdles then it would probably be viable.


Improve Navbar and Scroll Effect

close #354
Hi, I've Improve the margin and padding in Navbar and add smooth scrolling animation.
Please consider merging the pull request in the main branch, and If any changes required please let me know.

Hi @raj03kumar, can you please explain in which file merge conflicts are showing ? so I can work on fixing the issue

Just go to your fork and it will come that your repo is behind the main branch or something and sync your branch and then create a pull request. I hope it will work.

ok @raj03kumar, I checked merge conflicts are in package-lock.json file. If I remove this file before I made a commit and send a pull request will It work ?

No. You should not remove.  And then send the pull request.

Someone may have made changes in package-lock.json and you haven't pulled those changes that's why merge conflict arised. Kindly pull those changes and then proceed.

for pulling the changes sync your fork.

ok @raj03kumar I'll try with sync fork


failed with error 11000: "E11000 duplicate key error index

After updating to rails 4 i got this strange issue. Im using mongoid 4.0.0.
Here is stacktrace for error
Error while toggling environment: The operation: #<Moped::Protocol::Command
@length=89
@request_id=16
@response_to=0
@op_code=2004
@flags=[]
@full_collection_name="feedbackzilla_development.$cmd"
@skip=0
@limit=-1
@selector={:getlasterror=>1, :w=>1}
@fields=nil>
failed with error 11000: "E11000 duplicate key error index: feedbackzilla_development.activity_logs.$_id_  dup key: {     : ObjectId('5280dc64416c65109e780000') }"

See https://github.com/mongodb/mongo/blob/master/docs/errors.md
for details about this error.

I'm using sidekiq to do some background job, here is code that causing this issue:

user.sim_customers.destroy_all
user.sim_activity_logs.destroy_all
....
sim_customer = SimCustomer.create!(live_customer.attributes)

I have deleted everything from SimCustomer model, so there were no indices to conflict with

Getting the same error as @Jonybang, please fix. I believe it wasn't there before.

Actually, I just realized that I had bson_ext and bson in my Gemfile. I fixed it by removing both from Gmefile and rerun bundle
http://mongoid.org/en/mongoid/v3/upgrading.html

@arthurnn Why did this issue get closed?

my problem was solved thaks to the solution of @pencilcheck

I am getting the same error, but I am also using the 'mongo' gem (https://github.com/mongodb/mongo-ruby-driver/tree/1.x-stable), which advises adding "bson_ext" to Gemfile for a significant performance boost.
I think the Issue at hand isn't actually solved.

I'm also getting the same error, @pencilcheck's solution didn't work.
Gems in use:
rails 4.1.9
mongoid 4.0.1
moped 2.0.3
bson 2.3.0 (also tried master)

To make Mongoid work, you should only add mongoid gem to your Gemfile, and not other gems. Mongoid will handle the dependencies.

I only added mongoid to the Gemfile, the other gem versions are just listed to show that the other gems are on their latest version and that the issue still exists.

@hobofan can you use https://github.com/mongoid/mongoid/blob/master/examples/mongoid_test.rb to simulate the error? thanks

same error when
u = User.first
u.avatar_attributes= {id: "54fe95d174616e1a75000000"}

Moped::Errors::OperationFailure: The operation: #<Moped::Protocol::Command
  @length=95
  @request_id=8
  @response_to=0
  @op_code=2004
  @flags=[]
  @full_collection_name="zhang_shang_ban_you_development.$cmd"
  @skip=0
  @limit=-1
  @selector={:getlasterror=>1, :w=>1}
  @fields=nil>
failed with error 11000: "insertDocument :: caused by :: 11000 E11000 duplicate key error index: zhang_shang_ban_you_development.images.$_id_  dup key: { : ObjectId('54fe95d174616e1a75000000') }"

@arthurnn
the example runs ok:
Run options: --seed 26629
Running:
.
Finished in 0.098992s, 10.1018 runs/s, 10.1018 assertions/s.
1 runs, 1 assertions, 0 failures, 0 errors, 0 skips

The issue happened for me with the following configuration:

ruby-1.9.3-p551
mongo (1.9.2)
mongoid (3.1.7)
moped (1.5.3)
bson (1.9.2)
bson_ext (1.9.2)

My use case was to run a daemon process which forked a large number of child processes. These child processes regularly inserted records through Mongoid/Moped into the database.
Occasionally, but usually shortly after the daemons had started up, I got this error.
Digging deeper it turned out that moped was indeed generating duplicate id's in parallel processes.
Relevant code: https://github.com/mongoid/moped/blob/v1.5.3/lib/moped/bson/object_id.rb#L293:
def generate(time, counter = 0)
  process_thread_id = "#{Process.pid}#{Thread.current.object_id}".hash % 0xFFFF
  [time, @machine_id, process_thread_id, counter << 8].pack("N NX lXX NX")
end

The returned value should be unique across processes, but under special circumstances isn't. The only way it can happen is if all Array members passed to Array#pack are identical.
Since the processes are running on the same OS, the @machine_id is the same across processes. time will often be identical as well, due to the second-precision of Time.now.to_i. counter will occasionally be equal between different processes as well, as all processes initially start from 0 and start incrementing it after every insert.
The final variable that shouldn't be equal (in order to not generate id collisions) is process_thread_id. However, it quite often happened that there were collissions for this variable as well, resulting in identical Moped::BSON::ObjectId being generated in 2 separate processes. The calculation would use an identical Thread.current.object_id, because it is identical accross forked processes - only Process.pid would be different, but that doesn't guarantee that String#hash would return a well distributed random result.
My use case is probably extreme and should consider the limitations of the Moped::BSON::ObjectId::Generator, but for anyone else experiencing this problem, you might get away with the following workaround:
Add this code to your config/initializers/moped_objectid_generator_patch.rb:
raise "Confirm monkeypatch validity" if Gem.loaded_specs["moped"].version.to_s != '1.5.3'

Moped::BSON::ObjectId.class_variable_get(:@@generator).instance_eval do
  def generate(time, counter = 0)
    SecureRandom.random_bytes(12)
  end
end

This generates a much more well distributed random data chunks used for generating Moped::BSON::ObjectId records, at the expense of being slightly slower.
I am adding this note here, because this Issue has quite an extensive discussion associated with it already, instead of opening a new Issue under mongoid/moped.


[5.2] Allow for implicit model binding with arbitrary variable names

Basically, previously, if we wanted to use implicit model binding, we had to use the same name for our variable as for the wildcard name. With this PR, we can use any variable name, and, as long as we type hint our model, it will be implicitly bound.
As a side effect, this makes #11984 non-breaking, meaning it could then be done for 5.2 instead of 5.3, success.
This works in several steps, since we don't know exactly what's bound and what isn't.

Loop through all function signature parameters
If it is typehinted with something that’s not a class (or not at all) or a model, add it to an array
We now have a list of items that should be mapped to route variables, so just do that, and if an item is already bound or not a Model, ignore it and go ahead with the next

Step 2 is necessary so that we don't accidentally include something that should have been bound by the IOC container. The reason for including non-models, rather than just doing $route->signatureParameters(Model::class) is so that we can keep our array of wildcards aligned with that of the function signature of the called method. Basically, a route foo/{bar}/{baz} needs to map bar and baz, so we keep track of all things that should be mapped, even those that are done so explicitly, and those that aren't at all, in order to determine to which route parameter we should bind the model.

Slick.  I like it.  I would think it should be non breaking to 5.2 as well :+1:

Cool, im going to check it out. :)

Does Travis need to be nudged again?

@JesseLeite looks like it...

I dunno. I kinda prefer having to explicitly match the variable names with the route variable.

Ah dang. I thought you'd go for this @taylorotwell, since manually route binding models in RouteServiceProvider allows for arbitrary var names that don't match the URI segments.  I find your lack of consistency disturbing [cue Vader breathing here]


Add minimum required version to README.md

I've truied to build this with sqlite v 3.7 and failed: sqlite3_errstr not found. Minimum required version on readme page will be good

Right, thanks!


$(D ) for code in changelog

Would you want to use backticks instead?

Good.

Would you want to use backticks instead?

Next time


Automate releases

Describe the feature
dbt releases should be as automated as possible. Some ideas:

Provide a version number (and other info) in structured files (eg. release.md)
Generate a commit which bumps the version number
Call the GitHub API to publish a release

Describe alternatives you've considered
Do it manually

Some notes I have locally regarding future steps:
Two scripts: A tagger and a CI script
Tagger:

give the script three arguments: a commit to base off, a new version tag, and a release.md file of some sort
bumpversion to the tag version
commit + push + tag
use the github API to create a new release with the contents of release.md, on the tag

CI script:

run on tag builds. Version == the tag name.
generate frozen requirements file, save it for use in later steps. The requirements file should not include dbt itself (or dbt-core/plugins).

commit this?
should tests/merges generate this every time as an artifact for builds to pull

generate .whl/.tar.gz files for pypi
(before uploading to pypi!): recursively obtain all the dependency files for the requirements file, like poetry does.

this will detect any dependency errors
grab the shasums and urls while we're doing this to build the homebrew formula

upload to testpypi, then pypi
build homebrew + push it, triggering its CI process

instead of using the homebrew-pypi-poet script, just extract the URLs for what we uploaded, since we already got them for the dependencies
fix homebrew-dbt so it handles default homebrew version changes

build the docker images + push them to docker hub

Homebrew automation:

fix the homebrew script to look back multiple changes for commits.

Dockerfile automation:

should we move the dockerfile generation and release dockerfiles to a separate repository?
Should the requirements files move there, too?
Would still generate + push the docker file, like it does for homebrew. But the repository holding the dockerfiles would build the docker image itself in its CI (like homebrew)

closing in favor of https://github.com/fishtown-analytics/dbt/issues/2436


#983 - 'Send' button incorrect color when no text is entered into the…

Add a numbered list of manual tests you performed that validates your changes work on all platforms, and that there are no regressions present.
Add any additional test steps if test steps are unique to a particular platform.
Manual test steps should be written so that your reviewer can repeat and verify one or more expected outcomes.
For example:

Click on the text input to bring it into focus
Upload an image via copy paste
Verify a modal appears displaying a preview of that image

I have read the CLA Document and I hereby sign the CLA

Please re-write the original post to use this template:
<If necessary, assign reviewers that know the area or changes well. Feel free to tag any additional reviewers you see fit.>

### Details
<Explanation of the change or anything fishy that is going on>

### Fixed Issues
<Please replace GH_LINK with the link to the GitHub issue this Pull Request is fixing>
Fixes GH_LINK

### Tests
<!---
Add a numbered list of manual tests you performed that validates your changes work on all platforms, and that there are no regressions present.
Add any additional test steps if test steps are unique to a particular platform.
Manual test steps should be written so that your reviewer can repeat and verify one or more expected outcomes.

For example:
1. Click on the text input to bring it into focus
2. Upload an image via copy paste
3. Verify a modal appears displaying a preview of that image
--->

### Screenshots
<Add any necessary screenshots for all platforms if your change added or updated UI>

Please refer to this example. The button color should be green when initialized with a "draft comment". Thanks !
https://user-images.githubusercontent.com/32969087/103046307-de466e00-452b-11eb-8cfa-bf9d444dba8b.mp4

@marcaaron I done changes please check.

#1071 Changes done check again.

#983  Changes done check again.

@marcaaron Changes done check again.

#983 Issue fixed please check and let me know if any changes.

#983 Issue fixed please check and let me know if any changes.

@marcaaron changes done.

@marcaaron changes done.

@BharatVasoya please resolve the conflicts that have arisen in this PR, thanks!

@BharatVasoya please resolve the conflicts that have arisen in this PR, thanks!

Lots of conflicts, and I'm also not sure how this PR grew to having 131 file changes?

Lots of conflicts, and I'm also not sure how this PR grew to having 131 file changes?

https://github.com/Expensify/Expensify.cash/pull/1071 has been merged, we can close this off.

https://github.com/Expensify/Expensify.cash/pull/1071 has been merged, we can close this off.


BioNetGen installation script, with setuptools --install-bng option

This PR adds a script for downloading and installing BioNetGen into the
platform-specific location expected by PySB (or any other specified location).
This option reduces hassle for new users, facilitates cross-platform unit
testing (by installing the correct BNG binary for the current platform) and
moves us closer to a one step install:
pip install --install-option="--install-bng" pysb.
Untested on Windows as yet.

Coverage decreased (-0.04%) to 72.884% when pulling 187ee5bfb70517cca7ff983c47e2c07f2f2ab178 on alubbock:bng_installer into 36379dc2451043a1c69d8b03cc21c6d7961ec861 on pysb:master.

Coverage decreased (-2.6%) to 70.336% when pulling dd3ef89f77839d34a1ad5c2b42b7371c822268cd on alubbock:bng_installer into 36379dc2451043a1c69d8b03cc21c6d7961ec861 on pysb:master.

Coverage decreased (-2.6%) to 71.842% when pulling 8f9f63eaf8a316122f9ab8c701cad26a65377fee on alubbock:bng_installer into 77c81599403cd8c69b583ebceba1a2b96c9a3273 on pysb:master.

Closing this PR - Anaconda seems a better way to go. See #324.


Compatibility with third party packages

Hey guys, the project is amazing!
But I'm having some troubles integrating it with some 3rd party packages, like django-fsm-admin or django-celery-beat (being this the most important)
The errors I get on the admin with these packages are like this one:
'PeriodicTaskAdmin' object has no attribute 'readonly_preprocess_fields'

Do you have any idea why? Do you know any way to solve it?

I could work around the problem with django-celery-beat this way:
# this fixes the admins of django-celery-beat
# to use the unfold model admin as a base class
PeriodicTaskAdmin.__bases__ = (ModelAdmin,)  # noqa
CrontabScheduleAdmin.__bases__ = (ModelAdmin,)  # noqa
ClockedScheduleAdmin.__bases__ = (ModelAdmin,)  # noqa

admin.site.unregister(PeriodicTask)
admin.site.unregister(IntervalSchedule)
admin.site.unregister(CrontabSchedule)
admin.site.unregister(SolarSchedule)
admin.site.unregister(ClockedSchedule)

admin.site.register(PeriodicTask, PeriodicTaskAdmin)
admin.site.register(IntervalSchedule, ModelAdmin)
admin.site.register(CrontabSchedule, CrontabScheduleAdmin)
admin.site.register(SolarSchedule, ModelAdmin)
admin.site.register(ClockedSchedule, ClockedScheduleAdmin)

hey, I just checked django-celery-beat  and you are right about readonly_preprocess_fields. I will try to take a look and address this issue.
Regarding the site unregister and register, this seems to be a right approach to me. It is needed to add custom ModelAdmin from Unfold to get proper behavior and visual.

This seems to be fixed now by #110 (tag 0.8.0), so I'm closing it, thanks @lukasvinclav!

I ran across this issue with dj-stripe and had to solve it in a similar way. Below should work for just about any app that doesn't immediately work with unfold, and doesn't make you monkey around with __bases__:
from django.contrib import admin
from djstripe.admin import StripeModelAdmin
from unfold.admin import ModelAdmin

class StripeModelAdminOverride(ModelAdmin, StripeModelAdmin):
    pass

for model, _model_admin in dict(admin.site._registry).items():
    if model._meta.app_label != "djstripe":
        continue

    admin.site.unregister(model)
    admin.site.register(model, StripeModelAdminOverride)

I just stuck this in a utility app's admin.py

from django.contrib import admin
from unfold.admin import ModelAdmin

for model, model_admin in dict(admin.site._registry).items():
    if model._meta.app_label not in [
        "djstripe",
        "knox",
        "socialaccount",
        "usersession",
    ]:
        continue

    admin.site.unregister(model)

    new_admin_class = type(
        f"{model.__name__}AdminOverride",
        (model_admin.__class__, ModelAdmin),
        {},
    )

    admin.site.register(model, new_admin_class)

I improved upon @samamorgan's solution. This one preserves the attributes of admin class and works for any package.


Dataflow templates mixing camelCase and snake_case

The documentation on traditional Dataflow templates  has the parameter fields in "snake_case" style, but the immediately proceeding example uses camelCase for the field names, specifically helpText.
This applies to the following files in this repo:

dataflow/flex-templates/kafka_to_bigquery/metadata.json
dataflow/flex-templates/streaming_beam_sql/metadata.json

Both of the above also include the field is_optional in snake_case despite helpText being in camelCase form which contradicts the documentation.
Are both camelCase and snake_case allowed for these fields?  If so, the documentation should probably state as much.  Regardless, the style within a single file should remain consistent.

I just asked, and it looks like both camelCase and snake_case are allowed. It's just a matter of style depending, usually camelCase for Java and snake_case for Python.
I'll update the docs and samples to reflect it.


Remove UT support for Python 2.6.

Also remove now-unneeded pins in tox.ini.
As of python-etcd 0.4.3, python-etcd fails at install time on Python 2.6.
Impacts difficulty of re-instating RHEL6.5 support: #455.

Pypy UTs failed.  Happy to merge once those are fixed up.

I removed pypy support for now, until the gevent/pypy bug is resolved.

A bit sad, but yeah.


cqinclude Namespace should support multi-level includes

cqinclude should handle inclusion of cqinclude namespace includes that themselves have cqinclude namespaces.

Fixed via #767


Branch selection for Event Driven Ansible Controller Projects

Please confirm the following

[X] I agree to follow this project's code of conduct.
[X] I have checked the current issues for duplicates.
[X] I understand that ansible-rulebook is open source software provided for free and that I might not receive a timely response.

Feature type
New Feature
Feature Summary
Currently I could not find a way to specify the branch name when creating a project inside of EDA, by default it seems to use main/master branch. And when I try to use https://urlname.com/groupname/reponame/-/tree/branch_name I get a failure to login.
I'm using gitlab as my Git repo.
Steps to reproduce
Go into projects and create a new project with a Git link. Then try and use code from a different branch other than main.
Current results
extensions/eda/rulebooks location cant be found, (since I have not merge testing changes to main branch)
Sugested feature result
There should be an option or a way of selecting branches, same as automation controller.
Additional information
No response

Hello @felipe4334 This feature is already implemented
For commercial subscriptions of Ansible Automation Platform, please contact with your Red Hat Support.


Find Other Hybrid Encryption Library in C# for benchmark on README

ChatGPT gave me the following examples none of which are extremely used.
Here are some C# libraries on GitHub that implement AES/RSA hybrid encryption:
Cryptography by chriscdev: This library includes an implementation called FastRsa, which uses AES for data encryption and RSA for encrypting the AES key and IV. It provides detailed steps for encryption and decryption, as well as performance tips for optimizing the process (GitHub).
cryptocsharp by nagilum: This library offers both symmetric (AES) and asymmetric (RSA) encryption functionalities. It provides examples for generating RSA keys, encrypting and decrypting data using RSA, and encrypting and decrypting text using AES (GitHub).
Hybrid-File-Encryption by HarryCS98: This project is a file encryption program that uses AES for encrypting files and RSA for encrypting the AES key. It includes a GUI for ease of use and addresses security concerns related to remote work environments (GitHub).

I implemented HPKE.


In logical planning, order by columns are pruned from schema too early

Describe the bug
This will err:
select c2 from test order by c9;

To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
The same expression will work in Postgres.
Additional context
Add any other context about the problem here.

@jorgecarleitao this is causing #608 to fail as well

dup of #1372
cc @houqp


Added Java snippet for SQS Process message

Issue #, if available:
https://github.com/aws-samples/serverless-snippets/issues/78
Description of changes:
Added java snippet for processing SQS message
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thank you @thetuxwhocodes , just waiting for our SME to do a review of the code, then I can merge it into the project and on Serverless Land.


Initial version of the spec text

Essentially copied from
https://github.com/tc39/proposal-decimal/pull/177 .

Thanks! I'll merge as-is and follow up with changes.


Use romfs for audio on Switch when the program is qlaunch

We talked about this on Discord. When Borealis is being used for a qlaunch replacement there is no need to mount qlaunch's romfs on to another mount point. Because of layeredfs we can access the sound file through the romfs mount point.

Thanks for the PR!
Is there the need to redefine the whole path? Only the mount point changes, romfs: or qlaunch. The path behind stays the same.
Wouldn't it be better to define once and use the same "path" and just change the mount point "prefix" depending on tid?

Updated it with the changes you recommended.


Add OpenStreetMap example using TileLayer and BitmapLayer

For #2802
Change List

example

Screenshot?

Coverage increased (+0.005%) to 59.31% when pulling bbf392ec020d9b8f3c6984240dc5bd314bdda9ac on xx/tile-bitmap into f6ace6a0c4949d93df88cfa4579f004212f31191 on master.

I tried to run your openstreet-map example and got an error shown in the attached image. To use the example standalone I deleted the bottom line module.exports = env... in the file webpack.config.js according the description within that file.

Any Idea?

@TrantorM FWIW:
If you are testing things on master, you probably want to use npm run start-local to build the example against the local source on master rather than against installed modules.
The reason is that since deck.gl v7 is still in development the published modules may not contain what you need.

Not able to build it on master with npm run start-local either. Can't resolve<EMAIL_ADDRESS>
A git checkout tags/v7.0.0-beta.1  results in the same problem.


master - cloning host is missing name in all host except Amazon

Version - master 4-21
Steps to Reproduce:

Add any host except Amazon
Clone host

Results: Name field is missing
Expected: Name should be there

Version - master 4/28


Error loading b-file

While running the loda mine client, the following message appeared. The file exists in the path and it didn't look corrupted to the naked eye (I did not look carefully or specifically around the given index).
2021-09-22 15:25:12|INFO |Fetched https://oeis.org/A163960/b163960.txt
2021-09-22 15:25:13|WARN |Unexpected index 9675 in b-file /home/jon/loda/oeis/b/123/b123329.txt
2021-09-22 15:25:13|ERROR|Error loading b-file /home/jon/loda/oeis/b/123/b123329.txt
terminate called after throwing an instance of 'std::runtime_error'
  what():  Error loading b-file /home/jon/loda/oeis/b/123/b123329.txt
2021-09-22 15:25:14|INFO |Generated 4096 programs

The error message is expected. The b-file looks like this:
...
9672<PHONE_NUMBER>8
9673<PHONE_NUMBER>2
9675<PHONE_NUMBER>8
9676<PHONE_NUMBER>4
...

Notice that 9674 is missing. Not sure how to handle it. We could stop at 9673 and log a warning message(?).

File was fixed on OEIS side. Please reopen if it occurs again.


NormalizedName

NormalizedName is null when creating a new role, which results in an error when assigning a role to user

Hi @mrehman29, you’re right. I just saw your PR.
Approved 🙂


error LNK2001: unresolved external symbol starts from windows-2022 (20231002.1.0)

Description
Not sure whether it is really a bug in the image, but the failure (error LNK2001: unresolved external symbol from protobuf) only happened after Windows Server 2022 (20231002.1.0). The base code is same in ONNX and the dependency is almost the same as well. The only significant variance is the image version from GitHub Action (20231002.1.0 failed, but 20230924.1.0 worked). Also the latest Windows Server 2019 works fine. I checked both https://github.com/actions/runner-images/pull/8444 and https://github.com/actions/runner-images/pull/8443, but I didn't notice any crucial change that would possibly cause this unresolved external symbol error.
Therefore, I was wondering is there any significant change from 20230924.1.0 to 20231002.1.0 on Windows Server 2022? Any input is welcome. Thank you for looking into it!
Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
CI failure: https://github.com/onnx/onnx/actions/runs/6414801812/job/17415759304.
Issue: https://github.com/onnx/onnx/issues/5659.
Is it regression?
Version: 20231002.1.0
Expected behavior
Build the original project (onnx) successfully
Actual behavior
Build fails after windows 2022: 20231002.1.0: onnx.lib(checker.obj) : error LNK2001: unresolved external symbol "public: int __thiscall google::protobuf::RepeatedField<int>::size(void)const " (?size@?$RepeatedField@H@protobuf@google@@QBEHXZ) [D:\a\onnx\onnx\onnx\.setuptools-cmake-build\onnx_cpp2py_export.vcxproj]
Build success before windows 2022 20230924.1.0.
Also, build always succeed on windows 2019 regardless of versions (even the latest one works)
Repro steps
Follow the same process to build ONNX from source on a Windows Server 2022 machine: https://github.com/onnx/onnx/blob/5f908a9c433d86c4f1dbf6b963f51daf68daa86e/.github/workflows/release_win.yml#L60-L77.
git clone onnx
git submodule update --init --recursive
. .\onnx\workflow_scripts\protobuf\build_protobuf_win.ps1
cd onnx
set ONNX_ML=1
set CMAKE_ARGS="-DONNX_USE_PROTOBUF_SHARED_LIBS=OFF -DONNX_USE_LITE_PROTO=ON"
python -m build --wheel

Hello @jcwchen. We will take a look.

thank you @sergei-pyshnoi ! we are scheduled to release onnx and hit this blocking issue. Please help prioritize this work item for us.

We have deployed new i new image version version for Windows 2022 https://github.com/actions/runner-images/releases/tag/win22%2F20231016.1 . Is problem still persist on new images?

Thank you @sergei-pyshnoi for looking into issue! @liqunfu and I have just found out there is a new introduced library from "C:\Program Files\MySQL\MySQL Server 8.0\lib\libprotobuf-lite.lib which causes Protobuf library conflict. We have fixed our build script by prioritizing our installed Protobuf path instead of the prebuilt one. I will close this issue since the root cause has been identified.
Still, it would be super great if we can have an option to pin image version in the future when running GitHub Action to fast unblock some unexpected failure.


frame_support::storage: Add StorageStreamIter

This pr adds the StorageStreamIter trait. This trait is currently only implemented for StorageValue which store "SCALE container type" e.g. Vec, BTreeMap etc. A SCALE container type is a type that follows the following encoding structure Compact<u32>(len) ++ #( item.encode() )*. The streaming iterator is a way to decode container values using an almost constant memory usage in contrast to decoding the entire value once into memory. The memory of a runtime is constrained, especially when it comes to a single allocation. This can be used for stuff like decoding events in an offchain worker or other huge data. It could probably also used for on chain operations, but will may require some more performance optimizations.
Internally this works by using sp_io::storage::read to read chunks from the state as requested by the decoder. As each call to read is a host function call there is some internal cache that currently stores 2048 bytes. This reduces the number of host calls and improves the performance of the iterator.

bot merge

bot merge

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable-int
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2170210

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2170214

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2170205

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2170204

bot merge

This pull request has been mentioned on Polkadot Forum. There might be relevant details there:
https://forum.polkadot.network/t/polkadot-release-analysis-v0-9-37/1736/1


Fields not showing required class with conditional validator in model

If I add a conditional validator to a rule in a model using 'when' or 'whenClient', it doesn't add the 'required' css class. Does commit feec6dc mean that's done on purpose?
I'm using the required class to visually cue users which fields are required by adding an asterisk with js. Should I just be manually adding the 'required' class in these cases or is there a better way?

please show your view code

please show your view code

i have similliar issue while adding id to options attribute
like this
echo $form->field($user, 'name')->textInput(['id' => 'userName']);

@jhebb yeah, it seems to be done not accidentally.
We can't mark the field as required since we don't really know, whether it is.
You can add a required class to the field dynamically on validation of depend attributes.

@SilverFire Thanks for the update!
For adding the required class dynamically, do you mean just some custom js, or is there a better Yii way to do this?
Any chance the Yii js validation will be updated to do this automatically in the future?

I meant custom JS.

Any chance the Yii js validation will be updated to do this automatically in the future?

Of course if this feature is requested by more developers, we will consider adding it.

Awesome, well count me in for a vote!

Count me in too

Won't happen in 2.0 but we'll keep that in mind for 3.0.


Snapshot not updating PlayerContextProvider state if playlist contains different track urls

In reference to https://github.com/benwiley4000/cassette/issues/437 I'm trying to ensure the player remembers the user's location in the playlist.
This works perfectly when using the playlist in this demo https://github.com/benwiley4000/cassette-demo-app located here https://github.com/benwiley4000/cassette-demo-app/blob/forward/src/playlist.js. However, if the track urls are different, for example have different url parameters, I believe the snapshot functionality resets the position to beginning of the playlist rather than continuing from the position saved in the snapshot. The track indexes will always be the same but the url pointing to the media may change.
Is there anyway around this?
Thanks
Ross

Hey Ross, just to be clear, could you give me an example of two URLs that are different but you consider to be pointing to the same piece of media? Is it a query string that is changing? I'm happy to think about a solution for a smarter "equivalence" check than strict url equality, but I hope it makes sense that you can't always assume that a track is the same as before just because the index in the loaded playlist is the same.

@benwiley4000 thanks again for your quick reply!
To confirm it is the query string that is changing rather than the url specifically. Two examples are shown below they do have an expiry date.
https://content.bookboon.com/audio-branding/2a98e7e1-559f-4be2-8df2-4fa1a35fe8c6/start?response-content-type=audio%2Fmp4&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=BV997TAV5RI6P88ZDTV8%2F20200504%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200504T155104Z&X-Amz-SignedHeaders=host&X-Amz-Expires=86400&X-Amz-Signature=f7a8bdace9580136610e98c4a60d56ea8083a3f5cd8d324f4be28fffc808bbf1
https://content.bookboon.com/audio-branding/2a98e7e1-559f-4be2-8df2-4fa1a35fe8c6/start?response-content-type=audio%2Fmp4&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=BV997TAV5RI6P88ZDTV8%2F20200504%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200504T154722Z&X-Amz-SignedHeaders=host&X-Amz-Expires=86400&X-Amz-Signature=12b495d80d62a6b79abc074ff8113651520b0cae54bf63b9f68093e9bcd9ebd8

I see! I think to solve this maybe we could have a new prop passable to the PlayerContextProvider that is called areTracksEqual or something, not sure what the best name is. It takes two tracks as arguments and returns true if the tracks are equivalent. In your case it could be:
function areTracksEqual(a, b) {
  const [pathnameA, pathnameB] = [a, b].map(track =>
    new URL(track.url || track.sources[0].src).pathname
  );
  return pathnameA === pathnameB;
}

Does that seem like it could work?

@robo220 Ok so finally this is what I came up with: https://github.com/benwiley4000/cassette/pull/439/files#diff-85f3673c9affae062acd5232f1e0243bR1387-R1430
This is what you would need to add to your Player or PlayerContextProvider:
function areTrackSourceUrlsEqual(urlA, urlB) {
  const [pathnameA, pathnameB] = [urlA, urlB].map(url => new URL(url).pathname);
  return pathnameA === pathnameB;
}
// ...
areTrackSourceUrlsEqual={areTrackSourceUrlsEqual}

Does this seem good?

@benwiley4000 This seems good to me, thank you!


Started adding support for cartesian coordinates

Currently this doesn't actually work yet, in part due to https://github.com/WorldWideTelescope/wwt-web-client/issues/189. I need to investigate further.

@pkgw - this is good to go, so just wanted to check if you wanted to have a look before we merge this?


Making cgSpan mine closed graphs as defined in the CloseGraph paper

Hey all,
I would be super interested in using this tool to a project I'm working on.
I was wondering how difficult it would be to change cgspan to mine closed graphs as defined in the CloseGraph paper (i.e. disregard the number of isomorphisms when determining if a graph is closed or not). I guess I would have to change the way the _early_termination and check_equivalent_occurence work, by disregarding finding the isomorphisms in those functions. However, I am unsure if the algorithm would still be correct in this case. I tried to read the associated papers, however I am not sure I quite grasp the details to the point I would understand the consequences of such a change.
Sincerely,
Nikolai

Hey Shaun,
Thanks for the reply! From the cgSpan paper here on Figure 1 I am only interested in the mining of g'_1 and not g'_2 (as g'_1 is a supergraph of g'_2 and they share the same support). The formal definition of such closed graphs are given in the paragraph just above Figure 1:
CS = {g|g ∈ FS and ∄g′ ∈FS such that g ⊂ g′ and support(g) = support(g′)}
Sincerely,
Nikolai

Hi Nikolai,
One thing you can easily do is to replace _has_equivalent_extended_occurrence_projections call in cgspan.py with _has_equivalent_extended_occurrence_graphs.
This will not solve your example. I can not see an easy way to modify the code so it will output closed subgraphs according to ClosedGraph definition.
Even if we modify _early_termination and check_equivalent_occurence to consider support and not projections, we cannot guarantee that check_equivalent_occurence will be invoked, since the hash key may not be found.
For example consider two database graphs:
A-B-C-D-B-C
A-B-C-E-B-C
By ClosedGraph definition only A-B-C is a closed subgraph. We need  check_equivalent_occurence of A-B-C to be called with
B-C, but that will not happen because B-C hashkey is different (contains 4 edges) from that of A-B-C (contains only two edges).
Thanks,
Shaul

Hey Shaul,
Thanks for the answers, they have been of great help! I will try and see if I can incorporate these changes into a fork. :)
Sincerely,
Nikolai


Anomaly annotation shows on wrong date range on feature breakdown chart

We show anomaly result as line plot on AD history chart and show annotation on feature breakdown chart. When zoom in some period, feature breakdown may show annotation on normal detection intervals.

@ylwu-amzn I'm not able to reproduce this, in the real-time or historical case anymore.

Not sure if we have fixed this in historical detector changes, let's do more test and close this if not able to reproduce it.

Have been testing different edge cases, still cannot reproduce. Would have been caused by an issue in calculating the anomaly's endTime which determines the x coordinates of the annotation. Closing.


RemoveParentModulesPlugin performance

What kind of change does this PR introduce?
Performance enhancing.
Did you add tests for your changes?
No, but I did update some tests related to my changes.
If relevant, link to documentation update:
N/A
Summary
There were two commits here, both related to performance. This change reduces our build time by roughly ~10%.
[Module.getChunkIdsIdent] Remove getChunkIdsIdent from Module.
This function appears to only have been used to generate a cache key inside
RemoveParentModulesPlugin. With the recent change to using sets, it is actually
faster to find parent chunks containing a module than it is to generate this
cache key.
To profile this, I added a wrapper function temporarily in my branch and timed
the duration of the RemoveParetModulesPlugin.
Before this change it took ~6113 ms when building our config.
After this change it takes ~3160 ms against the same config.
[ModuleReasons] Remove ModuleReason chunk list.
I didn't see a need for ModuleReason's to track their chunks separate from the
module's list of chunks. Having a single source of truth seems beneficial. This
has a double benefit of speeding up the RemoveParentModulesPlugin.
Before making this change, but including the previous commit: 3160ms
After making this change: 340ms

Does this PR introduce a breaking change?
Yes, but for undocumented features.  Module.rewriteChunkInReasons, Module.getChunkIdsIdent and ModuleReasons.rewriteChunks have all been removed. I couldn't find any documentation on any of these methods, and I believe that they're only used internally by webpack.

Other information

@sokra @TheLarkInn I can't seem to get this failing test passing even in master... any idea what's going on?
This is the command that I attempted to run after failing with just npm install. I basically tried to mirror the ci steps.
rm -rf node_modules; npm install -g yarn; yarn install; yarn link webpack; yarn run circleci:test
The test fails on both my branch as well as master.

Closing this out, I can't figure out why ModuleReason.chunks should be different than ModuleReason.module._chunks or ModuleReason.dependency.module._chunks. In my mind only one of these should be the source of truth, but using either breaks tests and I've got no clue as to why. Opening a different PR with just the first commit.

Gary let's try and get this tackled with some help. Do you have a good email I can have you shoot me?

Don't feel bad. When I first converted moduleReason to have a map impl, I tried this very same thing and had failing tests. The reason is due to the lazy caching of modules and the conditional removal from of Chunks. The slight difference adds up to real differences at other stages of compilation.
You can't assume that a reason is the same as the module itself because the reason only counts


New Sample: Display content of utility network container

Description
PR to add a new Kotlin sample "Display content of utility network container" in the Utility Networks category.
Links and Data
Sample Epic: runtime/common-samples/issues/2738
What To Review

Review the code to make sure it is easy to follow like other samples on Android
README.md and README.metadata.json files
Sample loads features with associations and gracefully handles the opposite

How to Test
Run the sample on the sample viewer or the repo.

Thanks for the helpful feedback, ready for re-review @fpearson1111


Images

Is it possible to add images? Send photo from camera? Or is it only text messaging that is supported?
Best regards
Björn

Hello @jonisak !
Yes, it possible right now (in v.0.1.2) via custom view holder object (see here )
But I would advise you to wait just a few days for library update, where we have added default logic for images.
Best regards, Alexander

Hi Alexander,
Thank you! ChatKit looks great.
Will you update the example project as well?
Best regards
Björn @jonisak

Thank you for your feedback!
Of course we will. Moreover - it will have its own documentation 😉

Great!
I look forward to take a look at it! :)  Will it come this week?

Yep :)

Fantastic!

How does it look? Close to a release?

Hello @jonisak !
Version 0.2.0 is finally out :)
You can see how to use default images here, and how to add custom content types here.
Also, don't forget to check out the changelog.
Best regards, Alexander
P.S. There is no demo images in docs yet, but they'll appear soon. Nevertheless, sample app is already updated :) Have a nice weekend!

Awsome!
Thank you!
Skickat från min iPhone

7 apr. 2017 kl. 17:08 skrev Alexander Krol<EMAIL_ADDRESS>Hello @jonisak !
Version 0.2.0 is finally out :)
You can see how to use default images here, and how to add custom content types here.
Also, don't forget to check out the changelog.
Best regards, Alexander
P.S. There is no demo images in docs yet, but they'll appear soon. Nevertheless, sample app is already updated :) Have a nice weekend!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Rust support

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

@backpackerjmk here we are ! Better late than never :)

@fibonacci1729 or @michelleN would one of you two mind taking a look at this?

This fails for me when manually testing so I'm just looking into what is going on right now

would you please tell me what went wrong.

This is what I'm getting @FGRibreau
example-rust [master*]$ ../../bin/draft up
WARNING: no registry has been set, therefore Draft will not push to a container registry. This can be fixed by running `draft config set registry docker.io/myusername`
Hint: this warning can be disabled by running `draft config set disable-push-warning 1`
Draft Up Started: 'example-rust'
example-rust: Building Docker Image \buildApp: buildImg error: COPY failed: stat /var/lib/docker/tmp/docker-builder836933684/package.json: no such file or directory
complete: failed to write logs to file for build "01C9HKWCRCYDJYH5MT0WCSMMCD": open /Users/admin/.draft/logs/01C9HKWCRCYDJYH5MT0WCSMMCD: no such file or directory
example-rust: Building Docker Image: FAIL ❌  (76.1124s)
example-rust: Build ID: 01C9HKWCRCYDJYH5MT0WCSMMCD
Inspect the logs with `draft logs 01C9HKWCRCYDJYH5MT0WCSMMCD`

@bacongobbler @fibonacci1729 let me know if ya'll have any suggestions on this error

This is interesting!

example-rust: Building Docker Image \buildApp: buildImg error: COPY failed: stat /var/lib/docker/tmp/docker-builder836933684/package.json: no such file or directory

The rust Dockerfile doesn't contain any COPY package.json args! Did the rust app get detected as javascript or something? What was the output of draft create?

oh right. This is taking packs from master and I just need to pass in the path to the draft pack for rust that was created in this PR to make sure things are working. Because there is no pack for rust in master, draft create opted to use the javascript pack.

Okay so I just coped the rust pack to to DRAFT_HOME and then filed #607 to talk about how to test packs in dev more easily.
Now, I'm getting:
Draft Up Started: 'example-rust'
example-rust: Building Docker Image: SUCCESS ⚓  (152.1882s)
example-rust: Releasing Application |buildApp: release error: could not install release: rpc error: code = Unknown desc = render error in "rust/templates/ingress.yaml": template: rust/templates/ingress.yaml:1:14: executing "rust/templates/ingress.yaml" at <.Values.ingress.enab...>: can't evaluate field enabled in type interface {}
example-rust: Releasing Application: FAIL ❌  (0.1147s)
example-rust: Build ID: 01C9HSMJ4BWSQW6CS6WR37ZX77
Inspect the logs with `draft logs 01C9HSMJ4BWSQW6CS6WR37ZX77`

This is because we need to add a default value for .Values.ingress.enabled in the values.yaml file like we did for the other packs recently.
I believe after that addition/change this pack will work like a charm ✨

@michelleN done!

Nice catch @michelleN. LGTM!

Thank you @FGRibreau !!


Make attribute names lowercase

Motivation

There're some implementations which uses DataClass and relies on parameter naming style (e.g. CamelCase, snake_case, ...) to determine its type. For such functionalities, it's quite confusing to reference or use them paying attention to the styling.

What should be realised
Introduce case insensitive getitem to DataClass

Attribute name stored in __dict__ are unchanged
Measures against namespace pollution:

getattr only supports the original names
implement __dict__ key checking on setattr

>>> parameters = DataClass(aBC=1, BCD="b")
>>> parameters.abc
1
>>> parameters["abc"]
1
>>> parameters["aBC"]
1

This is not a very good idea, since inconsistent key name would certain be a seed of confusion, and forcibly lowered CamelCase will result in ugly parameter names.


Cannot read property 'indexOf' of null

Why would this happen?
2018-04-18T08:58:53.5803000Z ##[section]Starting: Update config variables
2018-04-18T08:58:53.5807522Z ==============================================================================
2018-04-18T08:58:53.5807730Z Task         : Update config
2018-04-18T08:58:53.5807880Z Description  : Update config variables in files
2018-04-18T08:58:53.5808069Z Version      : 1.2.2
2018-04-18T08:58:53.5808208Z Author       : Digitalmedia34
2018-04-18T08:58:53.5808439Z Help         : v1.2.2 - [More Information](https://github.com/digitalmedia34/updateconfig#readme)
2018-04-18T08:58:53.5808632Z ==============================================================================
2018-04-18T08:58:53.9821940Z ##[error]Cannot read property 'indexOf' of null
2018-04-18T08:58:53.9857085Z ##[section]Finishing: Update config variables

Here's my config file:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <appSettings>
    <add key="UITest_AppURL" value="uat-app-01:81/#/" />
    <add key="UITest_Username" value="" />
    <add key="UITest_Password" value="" />
  </appSettings>
</configuration>

I have defined UITest_AppURL, UITest_Username and UITest_Password as VSTS Release Process Variables.
UITest_Password type is a secret.
How to find and fix this problem?

I have deleted and recreated variables on VSTS and it solved the problem. Feel free to close this, but better error message would be nice.

Thanks for feedback. I'm still working on improvements


Getting ValueError: NULL COM pointer access followed by _ctypes.COMError: -2147220991

Trying to automate a proprietary application and getting the ValueError: NULL COM pointer access while calling menu_select() with File->Open File. This is followed by _ctypes.COMError: -2147220991 error.
I can see that the "Open File" dialog is opened. However the python interpreter gets hung and finally exception is raised.
Here is a code sample,
>>> from pywinauto.application import Application
>>> app = Application(backend='uia').start('software.exe')
>>> main_window = app.window(title_re='.*My App Title.*')
>>> main_window_actionable = main_window.wait('visible', timeout=30)
>>> windows = main_window_actionable.children()
>>> [print(w.window_text()) for w in windows]

panelContainer1

Dock Bottom
Dock Top

[None, None, None, None, None, None]

>>> children = main_window_actionable.children()
>>> dock_top = None
>>> for child in children:
...     if child.window_text() == 'Dock Top':
...         dock_top = child
...         break
...

>>> dock_top
<uiawrapper.UIAWrapper - 'Dock Top', GroupBox, -5332403040449452796>
>>> dock_top.menu_select("File->OpenFile")
Traceback (most recent call last):
  File "D:\venv\personal\lib\site-packages\pywinauto\uia_defines.py", line 234, in get_elem_interface
    iface = cur_ptrn.QueryInterface(cls_name)
  File "D:\venv\personal\lib\site-packages\comtypes\__init__.py", line 1152, in QueryInterface
    self.__com_QueryInterface(byref(iid), byref(p))
ValueError: NULL COM pointer access

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "D:\venv\personal\lib\site-packages\pywinauto\controls\uia_controls.py", line 949, in select
    self.iface_selection_item.Select()
  File "D:\venv\personal\lib\site-packages\pywinauto\controls\uiawrapper.py", line 132, in __get__
    value = self.fget(obj)
  File "D:\venv\personal\lib\site-packages\pywinauto\controls\uiawrapper.py", line 224, in iface_selection_item
    return uia_defs.get_elem_interface(elem, "SelectionItem")
  File "D:\venv\personal\lib\site-packages\pywinauto\uia_defines.py", line 236, in get_elem_interface
    raise NoPatternInterfaceError()
pywinauto.uia_defines.NoPatternInterfaceError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "D:\venv\personal\lib\site-packages\pywinauto\controls\uiawrapper.py", line 723, in menu_select
    menu.item_by_path(path, exact).select()
  File "D:\venv\personal\lib\site-packages\pywinauto\controls\uia_controls.py", line 952, in select
    self.iface_invoke.Invoke()
_ctypes.COMError: (-2147220991, 'An event was unable to invoke any of the subscribers', (None, None, None, 0, None))

I can see the open file dialog is opened successfully but the control is not returned.
Specifications

Pywinauto version: 0.6.8
Python version and bitness: Python 3.8.10 (tags/v3.8.10:3d8993a, May  3 2021, 11:48:03) [MSC v.1928 64 bit (AMD64)] on win32
Platform and OS: Windows 10

Additional info: If I click "Cancel" manually on the open file dialog box, the interpreter control returns immediately without any exception.

Also getting same issue with this code:
import pywinauto, datetime, sys

appPath = r"app.exe"
mainWinRe = "menu regex"
buttonText = "Button Title"
subWinRe = r"Window Title"

print(f"Python version:    {sys.version}")
print(f"Pywinauto version: {pywinauto.__version__}")
print(f"{datetime.datetime.now()} Starting app")
app = pywinauto.application.Application(backend="uia").start(appPath)

mainWin = app.window(title_re=mainWinRe)
button = mainWin[buttonText]
print(f"{datetime.datetime.now()} Clicking button {button}")
button.click()

listDispWin = app.window(title_re=subWinRe)
print(f"{datetime.datetime.now()} Begin menu select on window {listDispWin}")
try:
    x = listDispWin.menu_select("File -> Open")
except Exception as e:
    print(f"{datetime.datetime.now()} Exception in menu_select")
    raise e
else:
    print(f"{datetime.datetime.now()} End menu_select")

Gives this:
Python version:    3.8.8 (default, Apr 13 2021, 15:08:03) [MSC v.1916 64 bit (AMD64)]
Pywinauto version: 0.6.8
2023-11-12 14:17:28.085878 Starting app
2023-11-12 14:17:28.289923 Clicking button <pywinauto.application.WindowSpecification object at 0x00000263A5DF5F10>
2023-11-12 14:17:32.330806 Begin menu select on window <pywinauto.application.WindowSpecification object at 0x00000263A86AAF40>
2023-11-12 14:18:35.059771 Exception in menu_select
Traceback (most recent call last):
  File "C:\Anaconda3\lib\site-packages\pywinauto\uia_defines.py", line 234, in get_elem_interface
    iface = cur_ptrn.QueryInterface(cls_name)
  File "C:\Anaconda3\lib\site-packages\comtypes\__init__.py", line 1152, in QueryInterface
    self.__com_QueryInterface(byref(iid), byref(p))
ValueError: NULL COM pointer access

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Anaconda3\lib\site-packages\pywinauto\controls\uia_controls.py", line 949, in select
    self.iface_selection_item.Select()
  File "C:\Anaconda3\lib\site-packages\pywinauto\controls\uiawrapper.py", line 132, in __get__
    value = self.fget(obj)
  File "C:\Anaconda3\lib\site-packages\pywinauto\controls\uiawrapper.py", line 224, in iface_selection_item
    return uia_defs.get_elem_interface(elem, "SelectionItem")
  File "C:\Anaconda3\lib\site-packages\pywinauto\uia_defines.py", line 236, in get_elem_interface
    raise NoPatternInterfaceError()
pywinauto.uia_defines.NoPatternInterfaceError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "e:/Downloads/foo.py", line 24, in <module>
    raise e
  File "e:/Downloads/foo.py", line 21, in <module>
    x = listDispWin.menu_select("File -> Open")
  File "C:\Anaconda3\lib\site-packages\pywinauto\controls\uiawrapper.py", line 723, in menu_select
    menu.item_by_path(path, exact).select()
  File "C:\Anaconda3\lib\site-packages\pywinauto\controls\uia_controls.py", line 952, in select
    self.iface_invoke.Invoke()
_ctypes.COMError: (-2147220991, 'An event was unable to invoke any of the subscribers', (None, None, None, 0, None))

The File -> Open dialog does appear.  If Cancelled manually, menu_select() returns (without exception).  This is Anaconda under Windows 10.

Any solutions?


Refactor/clean score

Codecov Report
Attention: Patch coverage is 66.66667% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 88.99%. Comparing base (859e465) to head (5107445).

Files
Patch %
Lines

multilayer_alignment/consensus.py
50.00%
3 Missing :warning:

multilayer_alignment/score.py
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main       #4      +/-   ##
==========================================
- Coverage   89.26%   88.99%   -0.28%
==========================================
  Files           9        9
  Lines         326      327       +1
==========================================
  Hits          291      291
- Misses         35       36       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Auto pause and play when interrupted by a call or other apps' media

Checklist

[X] I read the troubleshooting guide before raising this issue
[X] I made sure that the issue I am raising doesn't already exist

Current bug behaviour
Keeps playing when interrupted by a call or other apps' media
Expected behaviour

Audio players should pause when something played on other apps'
Audio players should pause when interrupted by a call thereafter it must auto-play

Steps to reproduce

Execute flutter run on the code sample
...
...

Code sample

Code sample
void main() {
}

Affected platforms
Android
Platform details
No response
AudioPlayers Version
6.1.0
Build mode
No response
Audio Files/URLs/Sources
No response
Screenshots
No response
Logs

my relevant logs

Full Logs

my full logs or a link to a gist

Flutter doctor:
Output of: flutter doctor -v

Related issues / more information
No response
Working on PR
yeah

same issue here


Improve application deployment/undeployment

Create the same scenario "https://github.com/WASdev/ci.ant/issues/2" but in gradle.

There have been no additional requests for this in 7+ years. So I am closing the issue.


Update de.op

Added missing translations and changes of some erroneous translations

Looks good, merged manually :)

https://github.com/MultiMC/MultiMC5-translate/commit/3234ec5e69e5f3940a518e0ded73bd46f68e1d17


removing mdivide_left_spd and mdivide_right_spd

Summary:
Removes mdivide_left_spd and mdivide_right_spd from Stan. These functions were never exposed to users and are not used within Stan.
Intended Effect:
Code cleanup. The implementation looked a bit off and at the very least, the error checking wasn't efficient. Just removing code that we aren't actively using / maintaining.
How to Verify:
Check the code diff.
Side Effects:
None.
Documentation:
None.
Reviewer Suggestions:
@bgoodri. Can you tell me if we need to keep this around for any reason?

My guess is that these need to be fixed up and exposed rather than deleted.
Not having efficient ways to solve Ax = b for x (unless A is triangular) is
a bug.
On Wed, Mar 25, 2015 at 5:48 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

Summary:
Removes mdivide_left_spd and mdivide_right_spd from Stan. These functions
were never exposed to users and are not used within Stan.
Intended Effect:
Code cleanup. The implementation looked a bit off and at the very least,
the error checking wasn't efficient. Just removing code that we aren't
actively using / maintaining.
How to Verify:
Check the code diff.
Side Effects:
None.
Documentation:
None.
Reviewer Suggestions:
@bgoodri https://github.com/bgoodri. Can you tell me if we need to keep
this around for any reason?
You can view, comment on, or merge this pull request online at:
https://github.com/stan-dev/stan/pull/1409
Commit Summary

removing mdivide_left_spd and mdivide_right_spd. fixes #1407. closes
#227.

File Changes

M src/stan/math/prim/mat.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-0 (2)
D src/stan/math/prim/mat/fun/mdivide_left_spd.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-1 (44)
D src/stan/math/prim/mat/fun/mdivide_right_spd.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-2 (44)
M src/stan/math/prim/mat/prob/multi_normal_cholesky_log.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-3 (1)
M src/stan/math/prim/mat/prob/multi_normal_cholesky_rng.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-4 (1)
M src/stan/math/prim/mat/prob/multi_normal_prec_log.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-5 (1)
M src/stan/math/rev/mat.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-6 (1)
D src/stan/math/rev/mat/fun/mdivide_left_spd.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-7 (318)
D src/test/unit/math/fwd/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-8 (415)
D src/test/unit/math/fwd/mat/fun/mdivide_right_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-9 (414)
D src/test/unit/math/mix/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-10 (1496)
D src/test/unit/math/mix/mat/fun/mdivide_right_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-11 (1489)
D src/test/unit/math/prim/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-12 (24)
D src/test/unit/math/prim/mat/fun/mdivide_right_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-13 (24)
D src/test/unit/math/rev/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-14 (182)

Patch Links:

https://github.com/stan-dev/stan/pull/1409.patch
https://github.com/stan-dev/stan/pull/1409.diff

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1409.

Yes, we should expose these, not delete them.
Not exposing them was a lack of an important feature.
I'd reserve the term "bug" for when behavior doesn't match
the doc (it can then be a bug on either the doc or
code side or both).

Bob

On Mar 26, 2015, at 9:05 AM, bgoodri<EMAIL_ADDRESS>wrote:
My guess is that these need to be fixed up and exposed rather than deleted.
Not having efficient ways to solve Ax = b for x (unless A is triangular) is
a bug.
On Wed, Mar 25, 2015 at 5:48 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

Summary:
Removes mdivide_left_spd and mdivide_right_spd from Stan. These functions
were never exposed to users and are not used within Stan.
Intended Effect:
Code cleanup. The implementation looked a bit off and at the very least,
the error checking wasn't efficient. Just removing code that we aren't
actively using / maintaining.
How to Verify:
Check the code diff.
Side Effects:
None.
Documentation:
None.
Reviewer Suggestions:
@bgoodri https://github.com/bgoodri. Can you tell me if we need to keep
this around for any reason?
You can view, comment on, or merge this pull request online at:
https://github.com/stan-dev/stan/pull/1409
Commit Summary

removing mdivide_left_spd and mdivide_right_spd. fixes #1407. closes
#227.

File Changes

M src/stan/math/prim/mat.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-0 (2)
D src/stan/math/prim/mat/fun/mdivide_left_spd.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-1 (44)
D src/stan/math/prim/mat/fun/mdivide_right_spd.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-2 (44)
M src/stan/math/prim/mat/prob/multi_normal_cholesky_log.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-3 (1)
M src/stan/math/prim/mat/prob/multi_normal_cholesky_rng.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-4 (1)
M src/stan/math/prim/mat/prob/multi_normal_prec_log.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-5 (1)
M src/stan/math/rev/mat.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-6 (1)
D src/stan/math/rev/mat/fun/mdivide_left_spd.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-7 (318)
D src/test/unit/math/fwd/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-8 (415)
D src/test/unit/math/fwd/mat/fun/mdivide_right_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-9 (414)
D src/test/unit/math/mix/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-10 (1496)
D src/test/unit/math/mix/mat/fun/mdivide_right_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-11 (1489)
D src/test/unit/math/prim/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-12 (24)
D src/test/unit/math/prim/mat/fun/mdivide_right_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-13 (24)
D src/test/unit/math/rev/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-14 (182)

Patch Links:

https://github.com/stan-dev/stan/pull/1409.patch
https://github.com/stan-dev/stan/pull/1409.diff

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1409.

—
Reply to this email directly or view it on GitHub.

I would include "accidentally unexposed" under bug :)
On Wed, Mar 25, 2015 at 6:51 PM, Bob Carpenter<EMAIL_ADDRESS>wrote:

Yes, we should expose these, not delete them.
Not exposing them was a lack of an important feature.
I'd reserve the term "bug" for when behavior doesn't match
the doc (it can then be a bug on either the doc or
code side or both).

Bob

On Mar 26, 2015, at 9:05 AM, bgoodri<EMAIL_ADDRESS>wrote:
My guess is that these need to be fixed up and exposed rather than
deleted.
Not having efficient ways to solve Ax = b for x (unless A is triangular)
is
a bug.
On Wed, Mar 25, 2015 at 5:48 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

Summary:
Removes mdivide_left_spd and mdivide_right_spd from Stan. These
functions
were never exposed to users and are not used within Stan.
Intended Effect:
Code cleanup. The implementation looked a bit off and at the very
least,
the error checking wasn't efficient. Just removing code that we aren't
actively using / maintaining.
How to Verify:
Check the code diff.
Side Effects:
None.
Documentation:
None.
Reviewer Suggestions:
@bgoodri https://github.com/bgoodri. Can you tell me if we need to
keep
this around for any reason?
You can view, comment on, or merge this pull request online at:
https://github.com/stan-dev/stan/pull/1409
Commit Summary

removing mdivide_left_spd and mdivide_right_spd. fixes #1407. closes
#227.

File Changes

M src/stan/math/prim/mat.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-0 (2)
D src/stan/math/prim/mat/fun/mdivide_left_spd.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-1 (44)
D src/stan/math/prim/mat/fun/mdivide_right_spd.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-2 (44)
M src/stan/math/prim/mat/prob/multi_normal_cholesky_log.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-3 (1)
M src/stan/math/prim/mat/prob/multi_normal_cholesky_rng.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-4 (1)
M src/stan/math/prim/mat/prob/multi_normal_prec_log.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-5 (1)
M src/stan/math/rev/mat.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-6 (1)
D src/stan/math/rev/mat/fun/mdivide_left_spd.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-7 (318)
D src/test/unit/math/fwd/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-8 (415)
D src/test/unit/math/fwd/mat/fun/mdivide_right_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-9 (414)
D src/test/unit/math/mix/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-10 (1496)
D src/test/unit/math/mix/mat/fun/mdivide_right_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-11 (1489)
D src/test/unit/math/prim/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-12 (24)
D src/test/unit/math/prim/mat/fun/mdivide_right_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-13 (24)
D src/test/unit/math/rev/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-14 (182)

Patch Links:

https://github.com/stan-dev/stan/pull/1409.patch
https://github.com/stan-dev/stan/pull/1409.diff

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1409.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1409#issuecomment-86243814.

To paragraphse Andrew, when you poke a former semanticist's buttons,
he'll beep.
The Wikipedia has the usual definition as I understand
it:
A software bug is an error, flaw, failure, or
fault in a computer program or system that causes it
to produce an incorrect or unexpected result, or to
behave in unintended ways.

It doesn't include things like "I sure wish they had banded
matrices built into Stan."
Reminds me of the quote that's so popular among semantics
Ph.D. students who put quotes at the beginning of chapters:
"When I use a word," Humpty Dumpty said, in rather a scornful tone,
"it means just what I choose it to mean --- neither more nor less."
In fact, I think "Humpty Dumpty" would be a good alternative nickname
for Andrew, and having one person playing fast and loose with conventional
meanings in a project is already confusing enough!

Bob

On Mar 26, 2015, at 9:56 AM, bgoodri<EMAIL_ADDRESS>wrote:
I would include "accidentally unexposed" under bug :)
On Wed, Mar 25, 2015 at 6:51 PM, Bob Carpenter<EMAIL_ADDRESS>wrote:

Yes, we should expose these, not delete them.
Not exposing them was a lack of an important feature.
I'd reserve the term "bug" for when behavior doesn't match
the doc (it can then be a bug on either the doc or
code side or both).

Bob

On Mar 26, 2015, at 9:05 AM, bgoodri<EMAIL_ADDRESS>wrote:
My guess is that these need to be fixed up and exposed rather than
deleted.
Not having efficient ways to solve Ax = b for x (unless A is triangular)
is
a bug.
On Wed, Mar 25, 2015 at 5:48 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

Summary:
Removes mdivide_left_spd and mdivide_right_spd from Stan. These
functions
were never exposed to users and are not used within Stan.
Intended Effect:
Code cleanup. The implementation looked a bit off and at the very
least,
the error checking wasn't efficient. Just removing code that we aren't
actively using / maintaining.
How to Verify:
Check the code diff.
Side Effects:
None.
Documentation:
None.
Reviewer Suggestions:
@bgoodri https://github.com/bgoodri. Can you tell me if we need to
keep
this around for any reason?
You can view, comment on, or merge this pull request online at:
https://github.com/stan-dev/stan/pull/1409
Commit Summary

removing mdivide_left_spd and mdivide_right_spd. fixes #1407. closes
#227.

File Changes

M src/stan/math/prim/mat.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-0 (2)
D src/stan/math/prim/mat/fun/mdivide_left_spd.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-1 (44)
D src/stan/math/prim/mat/fun/mdivide_right_spd.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-2 (44)
M src/stan/math/prim/mat/prob/multi_normal_cholesky_log.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-3 (1)
M src/stan/math/prim/mat/prob/multi_normal_cholesky_rng.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-4 (1)
M src/stan/math/prim/mat/prob/multi_normal_prec_log.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-5 (1)
M src/stan/math/rev/mat.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-6 (1)
D src/stan/math/rev/mat/fun/mdivide_left_spd.hpp
https://github.com/stan-dev/stan/pull/1409/files#diff-7 (318)
D src/test/unit/math/fwd/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-8 (415)
D src/test/unit/math/fwd/mat/fun/mdivide_right_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-9 (414)
D src/test/unit/math/mix/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-10 (1496)
D src/test/unit/math/mix/mat/fun/mdivide_right_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-11 (1489)
D src/test/unit/math/prim/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-12 (24)
D src/test/unit/math/prim/mat/fun/mdivide_right_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-13 (24)
D src/test/unit/math/rev/mat/fun/mdivide_left_spd_test.cpp
https://github.com/stan-dev/stan/pull/1409/files#diff-14 (182)

Patch Links:

https://github.com/stan-dev/stan/pull/1409.patch
https://github.com/stan-dev/stan/pull/1409.diff

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1409.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1409#issuecomment-86243814.

—
Reply to this email directly or view it on GitHub.

Ok. I'll close this pull request.
@bgoodri, I'm going to assign the issue original to you. I'll outline what
I need from you to get this done.


Deleted page appear on search

i start by cloning nextra-docs-template and created mdx file on page folder and deleted.
but it still appear on search and when i click this deleted one, it routes to 404 page.
also when i type a word on search, there's error message on console :
next-dev.js?7e00:20 Warning: React has detected a change in the order of Hooks called by Search. This will lead to bugs and errors if not fixed. For more information, read the Rules of Hooks: https://reactjs.org/link/rules-of-hooks
Previous render            Next render

useState                   useState

useContext                 useContext

useState                   useState

useContext                 useContext

useContext                 useContext

useRef                     useRef

useRef                     useRef

useEffect                  useEffect

useEffect                  useEffect

useEffect                 useEffect

useCallback               useCallback

useState                  useState

useEffect                 useEffect

useCallback               useCallback

useContext                useContext

undefined                 useContext
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
at Search (webpack-internal:///./node_modules/.pnpm/nextra-theme-docs@2.0.1_6jx7hpii6hgsrmhxgqrmo3277u/node_modules/nextra-theme-docs/dist/index.js:1116:3)
at Flexsearch (webpack-internal:///./node_modules/.pnpm/nextra-theme-docs@2.0.1_6jx7hpii6hgsrmhxgqrmo3277u/node_modules/nextra-theme-docs/dist/index.js:1416:3)
at component (webpack-internal:///./node_modules/.pnpm/nextra-theme-docs@2.0.1_6jx7hpii6hgsrmhxgqrmo3277u/node_modules/nextra-theme-docs/dist/index.js:2561:17)
at nav
at div
at Navbar (webpack-internal:///./node_modules/.pnpm/nextra-theme-docs@2.0.1_6jx7hpii6hgsrmhxgqrmo3277u/node_modules/nextra-theme-docs/dist/index.js:1832:19)
at div
at InnerLayout (webpack-internal:///./node_modules/.pnpm/nextra-theme-docs@2.0.1_6jx7hpii6hgsrmhxgqrmo3277u/node_modules/nextra-theme-docs/dist/index.js:3093:3)
at f (webpack-internal:///./node_modules/.pnpm/next-themes@0.2.1_6jx7hpii6hgsrmhxgqrmo3277u/node_modules/next-themes/dist/index.module.js:8:597)
at $ (webpack-internal:///./node_modules/.pnpm/next-themes@0.2.1_6jx7hpii6hgsrmhxgqrmo3277u/node_modules/next-themes/dist/index.module.js:8:348)
at ConfigProvider (webpack-internal:///./node_modules/.pnpm/nextra-theme-docs@2.0.1_6jx7hpii6hgsrmhxgqrmo3277u/node_modules/nextra-theme-docs/dist/index.js:154:3)
at Layout (webpack-internal:///./node_modules/.pnpm/nextra-theme-docs@2.0.1_6jx7hpii6hgsrmhxgqrmo3277u/node_modules/nextra-theme-docs/dist/index.js:3168:75)
at App (webpack-internal:///./node_modules/.pnpm/next@13.0.6_biqbaboplfbrettd7655fr4n2y/node_modules/next/dist/pages/_app.js:27:1)
at PathnameContextProviderAdapter (webpack-internal:///./node_modules/.pnpm/next@13.0.6_biqbaboplfbrettd7655fr4n2y/node_modules/next/dist/shared/lib/router/adapters.js:62:11)
at ErrorBoundary (webpack-internal:///./node_modules/.pnpm/next@13.0.6_biqbaboplfbrettd7655fr4n2y/node_modules/next/dist/compiled/@next/react-dev-overlay/dist/client.js:301:63)
at ReactDevOverlay (webpack-internal:///./node_modules/.pnpm/next@13.0.6_biqbaboplfbrettd7655fr4n2y/node_modules/next/dist/compiled/@next/react-dev-overlay/dist/client.js:850:919)
at Container (webpack-internal:///./node_modules/.pnpm/next@13.0.6_biqbaboplfbrettd7655fr4n2y/node_modules/next/dist/client/index.js:60:1)
at AppContainer (webpack-internal:///./node_modules/.pnpm/next@13.0.6_biqbaboplfbrettd7655fr4n2y/node_modules/next/dist/client/index.js:173:11)
at Root (webpack-internal:///./node_modules/.pnpm/next@13.0.6_biqbaboplfbrettd7655fr4n2y/node_modules/next/dist/client/index.js:346:11)
window.console.error @ next-dev.js?7e00:20

It seems that you are using<EMAIL_ADDRESS>This bug was fixed in latest version already.


Make the Cmdline class the default commandListener for the parser.

Make the Cmdline class the default commandListener for the parser.  Add a method to retrieve the Command instances from the Cmdline, such as getCommands() : List.

Updated the parse methods to return a List instance.
This change will be released in 0.4.alpha


CUDA Out Of Memory

Hi,
In my case  I tried to validate the Middlebury 2014 (Quarter) model using ./predict_md.sh script. I tried with RTX 3070 or 1660Ti GPUs, everytime I get the CUDA oom error.
Any idea why this happen?
btw, because of the apex size, I have to use following versions (inside the conda env):
python=3.7
pytorch=1.7.1 torchvision=0.8.2 cudatoolkit=11.0
and my nvcc -V returns 11.0
Error:
(leastereo) alisvndk@alisvndk-G3-3500:~/Desktop/LEA/LEAStereo(master)$ ./predict_md.sh
Namespace(cell_arch_fea='run/sceneflow/best/architecture/feature_genotype.npy', cell_arch_mat='run/sceneflow/best/architecture/matching_genotype.npy', crop_height=1008, crop_width=1512, cuda=True, data_path='./dataset/MiddEval3/testQ/', fea_block_multiplier=4, fea_filter_multiplier=8, fea_num_layers=6, fea_step=3, kitti2012=0, kitti2015=0, mat_block_multiplier=4, mat_filter_multiplier=8, mat_num_layers=12, mat_step=3, maxdisp=408, middlebury=1, net_arch_fea='run/sceneflow/best/architecture/feature_network_path.npy', net_arch_mat='run/sceneflow/best/architecture/matching_network_path.npy', resume='./run/MiddEval3/best/best.pth', save_path='./predict/middlebury/images/', sceneflow=0, test_list='./dataloaders/lists/middeval3_test.list')
===> Building LEAStereo model
Feature network path:[1 0 1 0 0 0]
Matching network path:[1 1 2 2 1 2 2 2 1 1 0 1]

Total Params = 1.81MB
Feature Net Params = 0.10MB
Matching Net Params = 1.71MB
Traceback (most recent call last):
  File "predict.py", line 48, in <module>
    mult_adds = comp_multadds(model, input_size=(3,opt.crop_height, opt.crop_width)) #(3,192, 192))
  File "/home/alisvndk/Desktop/LEA/LEAStereo/utils/multadds_count.py", line 21, in comp_multadds
    _ = model(input_data, input_data)
  File "/home/alisvndk/anaconda3/envs/leastereo/lib/python3.7/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/alisvndk/Desktop/LEA/LEAStereo/retrain/LEAStereo.py", line 32, in forward
    cost = x.new().resize_(x.size()[0], x.size()[1]*2, int(self.maxdisp/3),  x.size()[2],  x.size()[3]).zero_()
RuntimeError: CUDA out of memory. Tried to allocate 5.49 GiB (GPU 0; 5.81 GiB total capacity; 66.60 MiB already allocated; 285.50 MiB free; 4.00 GiB reserved in total by PyTorch)

Could you please give me a hand about this problem?
Thanks.

This is duplicate of the :https://github.com/XuelianCheng/LEAStereo/issues/14
As far as I understand, your repository requires a lot of memory. ./predict_md.sh will not work on my machines. RTX3070 ?
You can close the issue.


[antlr4:x64-windows] Link failure with a freshly installed library

Describe the bug
While trying to link to a freshly installed antlr4 C++ runtime, a linker error occurs. The bug occurred on two machines, one with VS 2022, one with VS 2019.
Environment

OS: Windows 10 64-bit, locale pl-PL, used vcpkg before with no issues.
Compiler: MSVC, Visual Studio Enterprise 2022, 17.4.4 (the bug also occurred in VS Community 2019)

To Reproduce
Steps to reproduce the behavior:

./vcpkg install antlr4:x64-windows
Create a simple project consisting of lexer and parser grammars (can be default grammars from here). Contents doesn't matter as long as they're valid. They'll be referred to as ExprLexer and ExprParser respectively.
Add a dummy main code.
Add CMake calls to antlr4 for lexer and parser file generation.
Build.
Repro code when
Final CMake file code:

cmake_minimum_required(VERSION 3.16)

project(ExprRepro)

find_package(antlr4-runtime CONFIG REQUIRED)
find_package(antlr4-generator CONFIG REQUIRED)

antlr4_generate(
	ExprLexer
	${PROJECT_SOURCE_DIR}/antlr4/ExprLexer.g4
	LEXER
	FALSE
	FALSE
	"Expr"
)
antlr4_generate(
	ExprParser
	${PROJECT_SOURCE_DIR}/antlr4/ExprParser.g4
	PARSER
	FALSE
	FALSE
	"Expr"
	"${ANTLR4_TOKEN_FILES_ExprLexer}"
	"${ANTLR4_TOKEN_DIRECTORY_ExprLexer}"
)

add_executable(ExprMain "Main.cpp") # Main.cpp is just an empty main function

target_include_directories(ExprMain PRIVATE "${ANTLR4_INCLUDE_DIR_ExprLexer}" "${ANTLR4_INCLUDE_DIR_ExprParser}")
target_sources(ExprMain PRIVATE ${ANTLR4_SRC_FILES_ExprLexer} ${ANTLR4_SRC_FILES_ExprParser})
target_include_directories(ExprMain PRIVATE "${ANTLR4_INCLUDE_DIR}")
add_dependencies(ExprMain antlr4_shared)
target_link_libraries(ExprMain PRIVATE antlr4_shared)
target_compile_features(ExprMain PUBLIC cxx_std_17)

Expected behavior
The code should compile.
 && "E:\Programy\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -E vs_link_exe --intdir=CMakeFiles\ExprMain.dir --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100190~1.0\x64\rc.exe --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100190~1.0\x64\mt.exe --manifests  -- "E:\Programy\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.34.31933\bin\Hostx64\x64\link.exe" /nologo CMakeFiles\ExprMain.dir\Main.cpp.obj CMakeFiles\ExprMain.dir\antlr4_generated_src\ExprLexer\ExprLexer.cpp.obj CMakeFiles\ExprMain.dir\antlr4_generated_src\ExprParser\ExprParser.cpp.obj  /out:ExprMain.exe /implib:ExprMain.lib /pdb:ExprMain.pdb /version:0.0 /machine:x64 /debug /INCREMENTAL /subsystem:console  D:\vcpkg\installed\x64-windows\debug\lib\antlr4-runtime.lib  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cmd.exe /C "cd /D "D:\TheReclif\Documents\C++\GSIL Standalone\out\build\x64-Debug" && C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -noprofile -executionpolicy Bypass -file D:/vcpkg/scripts/buildsystems/msbuild/applocal.ps1 -targetBinary "D:/TheReclif/Documents/C++/GSIL Standalone/out/build/x64-Debug/ExprMain.exe" -installedDir D:/vcpkg/installed/x64-windows/debug/bin -OutVariable out""
  LINK Pass 1: command "E:\Programy\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.34.31933\bin\Hostx64\x64\link.exe /nologo CMakeFiles\ExprMain.dir\Main.cpp.obj CMakeFiles\ExprMain.dir\antlr4_generated_src\ExprLexer\ExprLexer.cpp.obj CMakeFiles\ExprMain.dir\antlr4_generated_src\ExprParser\ExprParser.cpp.obj /out:ExprMain.exe /implib:ExprMain.lib /pdb:ExprMain.pdb /version:0.0 /machine:x64 /debug /INCREMENTAL /subsystem:console D:\vcpkg\installed\x64-windows\debug\lib\antlr4-runtime.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTFILE:CMakeFiles\ExprMain.dir/intermediate.manifest CMakeFiles\ExprMain.dir/manifest.res" failed (exit code 1120) with the following output:
     Creating library ExprMain.lib and object ExprMain.exp
D:\TheReclif\Documents\C++\GSIL Standalone\out\build\x64-Debug\Main.cpp.obj : error LNK2019: unresolved external symbol "const antlr4::atn::SetTransition::`vftable'" (??_7SetTransition@atn@antlr4@@6B@) referenced in function "public: __cdecl antlr4::atn::SetTransition::SetTransition(class antlr4::atn::ATNState *,class antlr4::misc::IntervalSet)" (??0SetTransition@atn@antlr4@@QEAA@PEAVATNState@12@VIntervalSet@misc@2@@Z)
D:\TheReclif\Documents\C++\GSIL Standalone\out\build\x64-Debug\ExprLexer.cpp.obj : error LNK2001: unresolved external symbol "const antlr4::atn::SetTransition::`vftable'" (??_7SetTransition@atn@antlr4@@6B@)
D:\TheReclif\Documents\C++\GSIL Standalone\out\build\x64-Debug\ExprParser.cpp.obj : error LNK2001: unresolved external symbol "const antlr4::atn::SetTransition::`vftable'" (??_7SetTransition@atn@antlr4@@6B@)
D:\TheReclif\Documents\C++\GSIL Standalone\out\build\x64-Debug\ExprMain.exe : fatal error LNK1120: 1 unresolved externals

  ninja: build stopped: subcommand failed.

Build failed.

Additional context
It's possible to build the project with manually built libraries (i.e. directly from antlr4 Github repo) using target_link_libraries(ExprMain PRIVATE "${PATH_TO_ANTLR4_LIB_DIR}/dist/antlr4-runtime.lib") so I assume the issue lays somewhere on the port side.
The unresolved symbol ??_7SetTransition@atn@antlr4@@6B@ can be found both in the DLL and static library that's used to link to it using dumpbin /EXPORTS.
The bug persists in both Debug and Release configurations.
EDIT Bug description

I found the issue, it lays in the antlr4 CMake code. I'll report it to the antlr4 team, as for now I'll just create a patch that fixes this bug and a PR so that the package works in vcpkg.


Error without Throwable crashes

Is this valid?
I want to send all log messages of level ERROR to raygun but not all have exceptions. Currently RaygunClient.Send requires a Throwable and if it is null it crashes...

My apologies for the delay in the response to this ticket. Just an update on this one, Raygun Crash Reporting currently requires an Exception-type object (e.g inheriting from Throwable in Java) as the backend requires a stack trace to perform the auto-grouping and to get the best value out of the interface and product (which is highly tuned for surfacing and exploring exceptions). A system to handle generic logging is currently out of scope for Crash Reporting so log messages aren't really supported as a first-class citizen by Raygun.
We may look into a system which has support for this in the future, but we currently don't have any plans around this today.


Add: PWM support relay mode

Check if PWM crate support relay mode like ardupilot

relay mode can be accomplish using a 0xffff as channel value

We added this function with previous PR.


"Mouting" -> "Mounting"

Very awesome package! Just saw a little typo in the README.

Great! Thank you!