enabling callback functions for modal show or hide.

I'm just wondering that if .modal('show') or .modal('hide') takes callback function, then it might be convenient for some cases.
Here is full context of my issue: http://stackoverflow.com/questions/21316834/is-there-any-reason-that-bootstrap-supports-only-event-emitting-rather-than-cal
To summarize the question above, I'm trying to build something like http://jsfiddle.net/theeluwin/dva6L/1/ to implement situations like http://jsfiddle.net/theeluwin/r7Qa2/6/, http://jsfiddle.net/theeluwin/8Vagr/1/ or http://jsfiddle.net/theeluwin/9uFsp/1/.
This stuffs can be done by https://github.com/theeluwin/bootstrap/commit/d48ca2b9ab787fec695b6b44b362844c3438df4e, and I do know that this is just tricky compromise, but at least grunt test gave no errors.
I'm submitting this as an issue rather than pull request because I'm not very sure about my works.

My two cents here, I am facing the same situation that started this thread.
I my case I have a Modal (M1) with some elements that open another Modal (M2). In case the M2 should be shown I have to first hide M1, and when it is hidden then I can show M2. Same thing, when M2 finished its closed action I want to show M1 again.
Playing with events here could be insane because not all M1.hide should trigger a M2.show, and there are multiple M2 so I can't really set up a general M1.hide event to show the proper M2.. All hide/show chains have to be configured individually.
Callbacks here would be very useful.
I am playing with TimeOuts now, which is very fragile solution
Thanks
f.

Just want to drop in and say, I also found my way here after coming across the same problem OP had.

need some clarity

@pushpendraraj : You can direct check using jQuery Model Box  is visible then you add bootstrap  js of hiding the model that you can use


fix: 'type XXXX int' will print wrong sql to terminal

[x] Do only one thing
[x] Non breaking API changes
[x] Tested

What did this pull request do?
ref: https://github.com/go-gorm/gorm/issues/6898
The wrong sql printed to the terminal can be confusing when use type XXX int, so fix it.

User Case Description

type UserStatus int

const (
	Normal UserStatus = 1
	Forbid UserStatus = 2
)

DB.Where("status = ?", Normal).Find(&users)

It print:
SELECT * FROM `users` WHERE status = '1' AND `users`.`deleted_at` IS NULL

The expected print is:
SELECT * FROM `users` WHERE status = 1 AND `users`.`deleted_at` IS NULL

thank you for your PR


Feature/add i18n

Closes #30.
Has translation file for Spanish in app/js/i18n/es.json. The strings starting with exclamation points will need to be replaced with human translations.

I'm confused. I forked and cloned down to my laptop. I don't see any file to translate. There is no es.json file. There's no app/js/i18n/ folder. I forked and cloned again and it's still not there. Am I misunderstanding something?

I'll go ahead and merge this PR. Then you will be able to check out the develop branch to see the changes here (currently on a feature branch).

got it. Thanks.


Rename keywords

Closes #269
Minor fixes in documentation

Codecov Report

Merging #270 (6197b98) into main (7b159a0) will increase coverage by 0.04%.
The diff coverage is 98.12%.

:exclamation: Current head 6197b98 differs from pull request most recent head f681a22. Consider uploading reports for the commit f681a22 to get more accurate results

@@            Coverage Diff             @@
##             main     #270      +/-   ##
==========================================
+ Coverage   97.30%   97.35%   +0.04%
==========================================
  Files          35       35
  Lines        2304     2306       +2
==========================================
+ Hits         2242     2245       +3
+ Misses         62       61       -1

Impacted Files
Coverage Δ

robotidy/utils.py
97.11% <93.75%> (ø)

robotidy/transformers/InlineIf.py
98.10% <99.05%> (ø)

robotidy/transformers/RenameKeywords.py
97.43% <100.00%> (+2.84%)
:arrow_up:

robotidy/transformers/SplitTooLongLine.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


⚠ Young Discoverers has degraded performance

In 79174b1, Young Discoverers (https://youngdiscoverers.org.au) experienced degraded performance:

HTTP code: 200
Response time: 5738 ms

Resolved: Young Discoverers performance has improved in e4e71f2.


Publish app error: Unsupported symbol type 393321

Describe the issue
When publishing an App an "unsupported symbol" error is thwoned
Scripts used to create container and cause the issue
`Publish-NAVApp -ServerInstance BC -Path 'c:\Extensions\locpt.app' -PassThru -SkipVerification
Full output of scripts
Publish-NAVApp : Unsupported symbol type 393321
At line:1 char:1

Publish-NAVApp -ServerInstance BC -Path 'c:\Extensions\locpt.app' -Pa ...

  + CategoryInfo          : InvalidOperation: (:) [Publish-NAVApp], InvalidOperationException
  + FullyQualifiedErrorId : MicrosoftDynamicsNavServer$BC/nav-systemapplication,Microsoft.Dynamics.Nav.Apps.Manageme
 nt.Cmdlets.PublishNavApp

What version of Business Central?
What version of BcContainerHelper?
Is the app a runtime package or a "real" app file?

What version of Business Central?
W1 18.0 (Plataform 18.0.22893.24464 + Aplication 18.0.23013.24471)
What version of BcContainerHelper?
2.0.10
Is the app a runtime package or a "real" app file?
"real"

and was the app built for 18.0?

I probably need the .app file - if you can email me a link where I can download the app (freddyk at microsoft dot com)

GRRR... Sorry Freddy, my fault... it was an issue with the version of BC (solved now). Thanks for your quick answer.


Trimming down UGDG

Pull Request Test Coverage Report for Build 7

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 86.449%

Totals

Change from base Build 533:
0.0%

Covered Lines:
3024

Relevant Lines:
3498

💛  - Coveralls


noarch leads to ImportError (on windoze)

https://ci.appveyor.com/project/marscher/pyemma/build/1.0.3063/job/wrepwjo9ehgmiki2#L113
pinning to 1.10 avoids the problem, since these pkgs have been built with python arch dependency.
https://ci.appveyor.com/project/marscher/pyemma/build/job/8ajksepqxn2rpecg
Updating conda also drags in six, so one would have to reinstall six after conda update (I think the old conda-version on Appveyor is not capable of noarch pkgs)

six probably does something under the hood that is not conda noarch safe. I'll rever that and pull the package. Thanks for the report.

Out of curiosity, what happens if you upgrade conda only first and then upgrade everything else?

@jjhelmus I guess that until AppVeyor upgrades their miniconda it is better if we don't use noarch in the packages that will cause that conda update issue.

Agreed. I've been avoiding noarch: python in packages that conda depends on in berryconda to avoid update issues as well as to facilitate the creation of installers using constructor which does not support noarch packages at this time.

Would add that it appears the Miniconda being used on AppVeyor is C:\Miniconda3, which is a 32-bit Python 3.4 based Miniconda. Discussed with AppVeyor about getting this one upgraded some time ago and basically they said they would only update it if a new Miniconda for Python 3.4 was released. As that is not going to happen, that Miniconda will stay old. Good new is there are newer Minicondas available with newer Pythons. Recommend switching over to one of these, @marscher.

On 09/21/2017 03:37 PM, jakirkham wrote:

Out of curiosity, what happens if you upgrade |conda| only first and
then upgrade everything else?
I've tried that, without success.

On 09/21/2017 04:22 PM, jakirkham wrote:

Would add that it appears the Miniconda being used on AppVeyor is
|C:\Miniconda3|, which is a 32-bit Python 3.4 based Miniconda. Discussed
with AppVeyor about getting this one upgraded some time ago and
basically they said they would only update it if a new Miniconda for
Python 3.4 was released. As that is not going to happen, that Miniconda
will stay old. Good new is there are newer Minicondas available with
newer Pythons
https://www.appveyor.com/docs/build-environment/#miniconda. Recommend
switching over to one of these, @marscher https://github.com/marscher.
Thank you so much for this advice, will do that soon.

Agreed. I've been avoiding noarch: python in packages that conda depends on in berryconda to avoid update issues as well as to facilitate the creation of installers using constructor which does not support noarch packages at this time.

Interesting. Was not aware of that. For reference, issue ( https://github.com/conda/constructor/issues/86 ) is requesting noarch: python support.


Support for app.config files

It would be really awesome if we could use this in combination with something like FSharp.Configuration. Do you have plans for any further functionality?

I'm definitely open to more functionality!
App.config is normally meant for runtime configuration, so this would probably have much more limited use than FSharp.Configuration, but I guess it can still be useful.

JSON/YAML works too, just something a bit more refined than a text file I think would be a great feature.

+1. Would be great if you could use this to pull individual values out of a json and/or yaml file.


New version: DocumentFormat v1.0.0

Registering package: DocumentFormat
Repository: https://github.com/julia-vscode/DocumentFormat.jl
Created by: @davidanthoff
Version: v1.0.0
Commit: 079549f9fb8e096f3e4e87bc51703a597f975fb7
Reviewed by: @davidanthoff
Reference: https://github.com/julia-vscode/DocumentFormat.jl/commit/079549f9fb8e096f3e4e87bc51703a597f975fb7#commitcomment-35702376

Your new version pull request met all of the guidelines for automatic merging.
I will automatically merge this pull request during the next cron job.
If you want to prevent this pull request from being auto-merged, simply leave a comment.
(If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.)

[noblock]


Fix image analyzer report false positive messages when the imageType is distroless

Please provide a description of this PR:
Fix https://github.com/istio/istio/issues/47964

@hanxiaop: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
68616e304038fc2e27148ef8db0baac0f45666d1
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
fd82c6bffd0c1cc67e6d368d4b05d49e11a31b57
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
fd82c6bffd0c1cc67e6d368d4b05d49e11a31b57
link
true
/test gencheck

lint_istio
fd82c6bffd0c1cc67e6d368d4b05d49e11a31b57
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

weird - how did this one merge with the pending review request from UX maintainers?


Is it possible to get display url and comments?

I am using this framework on my application.
Is it possible to get display url and all comments of this post?
https://www.instagram.com/p/CY6dfn4oks5/?utm_source=ig_web_button_share_sheet
If yes, can you please share codes for it?
Thanks.
Vasyl.

I have an alternate framework for this purpose:
package main
import "github.com/89z/mech/instagram"

func main() {
   log, err := instagram.NewLogin("USERNAME", "PASSWORD")
   if err != nil {
      panic(err)
   }
   med, err := log.Media("CY6dfn4oks5")
   if err != nil {
      panic(err)
   }
   println(med.Display_URL)
   for _, edge := range med.Edge_Media_To_Parent_Comment.Edges {
      println(edge.Node.Text)
   }
}

https://github.com/89z/mech

I have an alternate framework for this purpose:
package main
import "github.com/89z/mech/instagram"

func main() {
   login, err := instagram.NewLogin("USERNAME", "PASSWORD")
   if err != nil {
      panic(err)
   }
   media, err := login.Media("CY6dfn4oks5")
   if err != nil {
      panic(err)
   }
   println(media.Display_URL)
   for _, edge := range media.Edge_Media_To_Parent_Comment.Edges {
      println(edge.Node.Text)
   }
}

https://github.com/89z/mech

@89z
Thank you for your quick help.
Is there any Objective-c or Swift codes for this?
Regards
Vasyl

Hey @vasylboy90,
Swiftagram is a Swift client for the Instagram Private API, meaning you need to log in and then find the media you're referring to within the API.
Once you have that, let's call identifier, you can then access all comments by using Endpoint.Media.Posts.comments(for:startingAt:), and all media-related info by calling Endpoint.Media.summary(for:).
Also, please make sure to use the Discussions page of the repo next time you're looking for help, please.


[aurora] Adjust naming to support dot notation, terser imports, clearer Main

1234567890

Resolved by #3341


Release v2.0.7

@resin-jenkins retest this please

@resin-jenkins retest this please

@resin-jenkins retest this please


Vendored Guava hits some errorprone issues

sdks/java/core/src/main/java/org/apache/beam/sdk/io/Compression.java:145: warning: [ImmutableEnumChecker]
enums should be immutable: 'Compression' has field 'detectedSuffixes' of type 'org.apache.beam.vendor.guava.v20_0.com.google.common.collect.ImmutableList<java.lang.String>',
the declaration of type 'org.apache.beam.vendor.guava.v20_0.com.google.common.collect.ImmutableList<java.lang.String>'
is not annotated with @com.google.errorprone.annotations.Immutable or @javax.annotation.concurrent.Immutable

 private final ImmutableList<String> detectedSuffixes;
                                      ^

 (see http://errorprone.info/bugpattern/ImmutableEnumChecker)
error: warnings found and -Werror specified

The annotations should be preserved, so it may be that errorprone has an allowlist of classes and the relocation fools it. Probably should be fixed in errorprone if that is the case. If there is something we need to preserve about the rewritten class files, we should do that.
Imported from Jira BEAM-6420. Original Jira may contain additional context.
Reported by: kenn.

obsolete


Automatically use requirements.in if the project uses a requirements.txt + requirements.in-setup

PR Checklist

[x] A description of the changes is added to the description of this PR.
[x] If there is a related issue, make sure it is linked to this PR.
[x] If you've fixed a bug or added code that should be tested, add tests!
[x] Documentation in docs is updated

Description of changes
This implements a solution that was proposed by @mkniewallner for the issue described in https://github.com/fpgmaas/deptry/issues/608. That is; use a same approach as we use for the exclude parameter to determine if a user specified the argument requirement-files. If no input is provided by the user for this argument and the project contains both a requirements.txt and a requirements.in, use the requirements.in.
Considerations:

When do we perform the check for a requirements.in file?

Before DependencySpecificationDetector().detect(): This would make sure that deptry also works if the project only contains a requirements.inand no requirements.txt. But this will log to the user that the requirements.in will be used before theDependencySpecificationDetector has run. This will be a lie if the project detects that Poetry is used for dependency management in the DependencySpecificationDetector.
In the DependencySpecificationDetector -> this seems to violate SRP; now it not only detects, but also overwrites the requirements_files argument if it decides that is necessary.
After DependencySpecificationDetector().detect(): This means it does not work automatically if the project only contains a requirements.inand no requirements.txt. This should be a rare case, so this solution seems like the best solution to me.

If the user does not explicitly set the requirements-files argument, the dependency format is detected as requirements-file because the project contains a requirements.txt, and requirements.in is detected, the user will see the following message:

Detected a 'requirements.in' file in the project and no 'requirements-files' were explicitly specified. Automatically using 'requirements.in' as the source for the project's dependencies. To specify a different source for the project's dependencies, use the '--requirements-files' option.

Reviewing this made me think that we could simplify a bit the dependency specification detector by getting rid of the intermediate DependencyFormat enum: https://github.com/fpgmaas/deptry/pull/654.
Aside from this refactoring, I'm wondering about 2 things:

In case requirements_files is not set by the user, should we first try to parse a requirements.in even if there is no requirements.txt, as it's possible to manually set a different name for the resulting .txt file (for instance with pip-compile -o requirements-prod.txt)?
Should we apply the same logic of trying to find .in first for requirements_files_dev in case the default value is left untouched by the user?

In case requirements_files is not set by the user, should we first try to parse a requirements.in even if there is no requirements.txt, as it's possible to manually set a different name for the resulting .txt file (for instance with pip-compile -o requirements-prod.txt)?

Yes, definitely! In the earlier approach I did not do that because of the way we had the DependencySpecificationDetector set-up, see also the considerations in the PR description about when the check should run. With your addition of the DependencyGetterBuilder, this is now solved and we can just do a check for a requirements.in file.

Should we apply the same logic of trying to find .in first for requirements_files_dev in case the default value is left untouched by the user?

I think we should not do that, for two reasons:

The impact of using the incorrect requirements file is much larger than using the incorrect requirements-dev file; in the first case, deptry will raise a DEP002 error for all transitive dependencies. In the latter case, there will only be an incorrect violation raise if a transitive development dependency is used as a regular import in the project.
i think it is quite uncommon to pin the development requirements files like this [citation needed]. I think with the current implementation we tackle >90% of cases by default, if people really want to have their development dependencies read from a different file they can of course always still use the CLI arguments.


ADC0 not clear

'ADC0' doesn't match any pin label printed on pico (perhaps add 'GP26')
https://github.com/RaspberryPiFoundation/picozero/blob/762096f615cb08ca5542c24f3e26d7693f261c17/docs/examples/potentiometer.py#L9

Thank you.
I have changed to
# Potentiometer connected to GP26 (ADC0), GND and 3V

from time import sleep
from pico import Pot

pot = Pot(26)

while True:
    print(pot.value, pot.voltage)
    sleep(0.1)

It is in dev

released


Change branch from git package

Have you checked for existing feature requests?

[X] Completed

Summary
Currently git packages are limited to the default branch but for example here it would be useful to install from other branches.
Enter your response below:
When you want to test a patch or something without manually setting up the package. It would also allow maintainers of git only packages to have a stable and a dev branch where people can select what they want.
Any alternatives?
Currently you have to clone the package, change the branch and then link it with ppm
Other examples:
No response

Ok, I should have checked the code before. It seems to be possible


APP-1536 Add protos for app billing service that will interface with the Stripe API

Notes:

Stripe can take as input way more information than the request objects take here -- I've included the bare minimum
Similarly, Stripe returns way more information than response objects return here

We can update these as necessary, we will probably need to do so as we work through all possible billing flows and levels of customization

@edaniels brought up a good point that any third-party specific APIs should not live in the public API repo. These kind of implementations should probably just exist in the app. Any of the non-stripe billing APIs should live here.

I'd suggest keeping this in a private proto namespace in our API (either in this repo or in app). That way, people know this isn't part of the standard usage of the API and is very much cloud implementation specific.

I agree with this ^ We should create a new file in APP with protos in it for this integration purpose. My only concern is adding the right tooling so the bufs generate correctly, but copying the commands from rover-rental or api to generate buf files should be fine.

decided to move these protos into app -- closing this PR


Prevent index out ouf bunds error

I'm reusing this for disque client... and get index out of bounds error because there really are just 2 items in array not 3.
BTW.. is it possible to merge this down to 6.x series as we really don't want to do an upgrade

Thanks. I wll make sure to update v6 too.


[refactor] manifest v2 --> manifest v3

Mark this PR draft because I want to test github workflow first. And related docs will be added or updated later.
This PR contais a lot lot lot of changes, but I have trouble in spliting them into minor independent PRs. So I plan to use GitHub review PR features to explain the changes at my best.
Description
Part1:
New manifest v2 extesnsions are no longer accpeted by chrome extension store since January 2022, and exsiting MV2 extensions will not be able to updated when January 2023 comes. So just update to MV3.
Part2:
More comfortable developing experience with more accurate HMR & hot-reload support.
Part3:
webpack4 --> webpack5
Part4:
Update docs.
Types of changes

[x] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation Update (if none of the other choices apply)

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

Just updated README and CONTRIBUTING. Not finished yet...

I'm tring to explain what I did in this PR by using GitHub review feature.
This is the first time I used the review feature, good luck to me.

@frank-zsy @LiuChangFreeman @heming6666
Hi guys, I've made some changes in this PR and written comments to explain why I made these proposed changes. Can you spend some time to review them?

LGTM.
@tyn1998 Good work!

Thanks @tyn1998 for your great work! These changes will make this project  be better and more efficient.
We can wait further reviews from @frank-zsy @LiuChangFreeman until 2022/3/1 (next MONDAY).

/approve


Add Feature: Write Summary as comment to the pull request

This Pull-Requests adds the feature to also put the summary of the dependency review as a comment into a pull-request. This makes it easier and more intuitive to surface the information.
To be backwards-compatible, it is turned off by default and can be turned on via an action-input.
A live example of how it looks like can be seen in this pull request in davelosert/action-test-repository:

If permissions are missing, a warning is printed as can be seen in this workflow run in davelosert/action-test-repository:

I wasn't sure if I should write any tests for the comment-pr.ts-file, as it would involve mostly mocking the octokit-library. Happy to do it on request. 🙂

Thanks, this looks pretty cool! I'll try to test things out and merge before end of week.

@courtneycl will wait on feedback before merging this.

@febuiles , @courtneycl : Any update on this?
I can fix the merge conflicts as soon as you give me a green light. 🙂

Hi @davelosert! Thanks so much for this contribution, having greater visibility in the summary is great.
I think this is okay to merge as-is since it's a configuration option. I'd like to modify the format of the summary file to be more compact--it's really quite large when used as a comment--but I won't get to that in the immediate future and don't want to stand in the way of folks using this in the mean time if they're okay with the sizeable comment. 🤓

Merging as is. I understand that a few changes in the comment formatting are coming in another PR so I'll hold on releasing a new version until this is fully fleshed out.


Add "higher versions" for Auditpol utility

Auditpol.exe utility is available in higher versions of Windows after Vista and Server 2008.

@rezazein : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks @rezazein! I'll approve these changes.
#sign-off

@VanMSFT: I'm sorry - only the author of this article, @davidtrigano, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Thanks @VanMSFT


linker command failed with exit code 1 (use -v to see invocation

ld: '/Users/apple/Documents/papasong/platforms/ios/xxx/Plugins/co.airsia.cordova.pingpp/libpingpp+alipay.a(PingppInternal+Alipay.o)' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I resolve it. close the xcode build setting->ENABLE_BITCODE


Editorial overrides: consider marking non-essential parts of a feature

We might want to identify features as part of a group, but not let it contribute to a status calculation. This is issue describes a specific kind of editorial override and how we might want to handle it.
Problem description
Some features are plausibly part of a group, but contribute to misleading statuses.
It's likely that some feature members meet the following criteria:

It is genuinely part of a wider feature group (i.e., developers wouldn't recognize it as independent feature).
It was introduced to one or more browsers around the same time as the majority of the other members of that feature (i.e., web developers wouldn't recognize it as a later addition to a feature — its history starts around the same time as the history of the feature as a whole).
Its data uniquely holds back the status of the wider feature (e.g., but for this one member, the wider feature would have Baseline status).

It's likely that we will want to overlook such features for the purposes of calculating a status, to avoid producing a dubious result (e.g., my initial calculation for fetch() reported that it is not Baseline, even though it's a widely-used web platform feature).
These are likely candidates for editorial overrides. But it's already a common enough occurrence that we probably ought to have some tool to handle these cases, rather than resorting to the blunt instrument of simply dictating a status. Plus, it would be desirable to not completely untether the feature from the underlying data.
Candidates for this kind of treatment

Minor corners of a large feature group (e.g., a missing, little-used property or method)

Example: fetch — api.Request.body — https://github.com/web-platform-dx/web-features/pull/478 — not implemented in Firefox
Example: web-animations — api.KeyframeEffect.composite — https://github.com/web-platform-dx/web-features/pull/467

At-risk features

Example: offscreen-canvas — api.OffscreenCanvasRenderingContext2D.commit — https://github.com/web-platform-dx/web-features/pull/462 — proposed for removal from the spec, but not actually removed

Incorrect data from BCD (e.g., an incorrectly un-mirrored feature)

Example: :read-only and :read-write pseudos — https://github.com/web-platform-dx/web-features/pull/462#discussion_r1413636269 —  faulty Firefox for Android data in BCD (at the time I'm writing this)

Potential approaches
Instead, we might consider flagging certain features as being non-contributors to status calculations and perhaps set up tooling around those features, so that those exceptions are re-reviewed when underlying data changes. Some options include:

pragma comments or annotations in feature lists
ignore lists per feature
an inventory of no-op BCD keys

Generally, I agree that this ability is needed. But I'm worried about this particular case:

Minor corners of a large feature group (e.g., a missing, little-used property or method)

Candidly, if a method/attribute/piece is really part of the feature, then its status should really count towards the entire feature, like the other pieces of the feature.
Giving the governance group the ability to arbitrarily decide to remove some pieces feels risky. How will the group make the decision? How will the group know that a piece isn't being used much? Maybe it's not used because it's not interoperable in the first place.
If we do this, I would suggest considering:

Documenting the decision, maybe directly within the feature data, as a field of the YAML file that could be exposed in the UI.
Naming the group in a way that makes this visible. E.g. FeatureXWithoutFooPiece would be a group that's high baseline but that doesn't contain Foo. Versus FullFeatureX which might not be baseline, but would contain each and every little detail of the feature X.

Using data like this, baseline statuses that appear on websites out there would be able to show what, exactly, does a feature contain. Or, more important, what it doesn't contain. Like Fetch, baseline 2023 (except Request.body) (just making up an example).
I would hate for this to become an escape hatch for a browser vendor that doesn't want to implement one little missing thing for whatever reason, when developers out there really need it, but haven't been able to express it loudly.
In my ideal world, stuff like this would be easily visible and linked to each browser vendor's bug tracker so that people can ask for it.
What do you think?

Giving the governance group the ability to arbitrarily decide to remove some pieces feels risky. How will the group make the decision? How will the group know that a piece isn't being used much? Maybe it's not used because it's not interoperable in the first place.

Right, still building on our experience with patching data in Webref, a key reason why we try to make sure that there is an issue open against the spec, and that we link to it from the patch, is that there may be different ways to fix the problem, and we don't feel that we should choose one: the group responsible for the spec has the authoritative power. In such cases, we try to err on the conservative side of things while the group resolves the issue, e.g. rolling back the data in Webref to what it was before the problem was introduced.
Back to features, if the feature was introduced or changed recently (not what this issue is about, I know), we're dealing with an upcoming feature and the problem seems more a naming/versioning issue. E.g. what Media Source Extensions (MSE) means today vs. what it will mean in a few years from now ("MSE in workers" was introduced more recently. The upcoming ManagedMediaSource interface is not even yet in the spec. Both features should be part of MSE down the road).
If the feature has been around for some time, it signals an issue with the spec. And I think the issue needs to be raised with the working group in charge of the spec and with implementers before it gets dropped from the status calculation. We're already used to doing that, I think (see https://github.com/web-platform-dx/web-features/pull/462#discussion_r1413633002 for the investigation on commit()), I'm just suggesting to continue!
For Fetch, I note that there have been renewed discussions last year on request.body that resulted in updates to the spec (to drop support for the feature when HTTP/1.1 is used), and concluded that the feature should be kept around. In other words, this should probably still be treat as an upcoming feature. It seems fine to call "Fetch" today is "Fetch without request.body" in the same way as we would define MSE as "MSE without ManagedMediaSource".

In my ideal world, stuff like this would be easily visible and linked to each browser vendor's bug tracker so that people can ask for it.

+1 to linking to relevant places. To bug trackers and/or to an issue raised against the spec itself.
Side note: we should probably not categorize the features we're considering here as "minor" (for whom? The Fetch discussion linked above shows that some developers consider the feature as crucial) or "little-used" (of course they are, they're not widely available!). We're more dealing with advanced features that can be considered non-essential in the sense that the global feature is already useful and usable without them.

Discussed in last week's WebDX CG baseline meeting.
General feeling in the group is that features "excluded" from a feature group should be flagged somehow. There are different ways to do this. One idea raised would be to create specific groups for them right away to:

record why they were left out of the other feature group
create an identifier that can be used to talk about them


[KEYCLOAK-9885] Force cookie lookup for access token and allow raw Authorization headers to be sent "AS IS"

Hello,
This pull request has been created in order to solve my issue available here : https://issues.jboss.org/browse/KEYCLOAK-9885
The goal if this pull request is to bring more behavior tuning to Keycloak-Gatekeeper :

Being able to configure the Keycloak token lookup (for example force cookie lookup for the access token).
Being able to forward Authorization header "as-is" to the upstream application (without altering it, transparent way).

Motivations are discribed in issue KEYCLOAK-9885.
Tell me if I am required to create the unit tests related to the newly added code.
I'm open to any suggestions / code improvements in order to accept this PR.
Best regards,
Nikita

@nirousseau some considerations before people start to review:

Before implementing features that you would like to include in Gatekeeper, I'd suggest to first give a heads up on keycloak-dev mailing list with your proposal. That's the way of getting people's feedback.
Tests and documentation are mandatory.
Please, squash your commits in a single one.

Thanks for submitting this and have a great weekend.

@nirousseau I've had a similar requirement at my place with mixed credentials, e.g. cookies vs token in header.
This normally works fine: if header is present, it is preferred over cookie.
What may be confusing is when token is assumed to be encrypted (e.g. in cookie): then the raw taken in header is no more usable (because gatekeeper tries to decrypt this).
My PR #445 solves this issue, I think in a simple way: config states that access token is not encrypted but we also specify that token in cookies is always encrypted. So this way I could get access either from clients using cookies, or from clients (e.g. apps) using access token in headers.

Hello @abstractj,
Thank you for the general process for contributing to Gatekeeper.
I have subscribed to to mailing list ; I will send an email asap exposing the challenges I am trying to resolve with this PR.
Documentation is done (code + issue tracker).
I need to write unit test (I'm a newbie with golang).
Thank you for your feedback 💯

Hello @fredbi,
This normally works fine: if header is present, it is preferred over cookie.
Yes, I agree. That's the source of my problem : my upstream application is sending its own token with the Authorization header once the authentication is done (I.e the keycloak access token located in the cookie is verified by the proxy), the proxy will look for the header first (as expected). However, the Authorization header does not contain the access token, so it will drop the token and redirect.
I see two approaches :

Fallback to the cookie checkup if the authorization header is not valid/present
Help the proxy by specifying where to look at (my approach with this PR #473 )

We should be able to fallback to cookie inspection if the Authorization header does not contain the access token from keycloak. is PR #445 allow this ?
config states that access token is not encrypted but we also specify that token in cookies is always encrypted. So this way I could get access either from clients using cookies, or from clients (e.g. apps) using access token in headers
It is quite confusing to specify that tokens are "plaintext" with one parameter, but "cyphered" with another one, but only for cookies. If I'm not mistaken, your PR is more related to encrypted token handling. The changes I submit are not depending on encryption parameters.
I'm very new to Keycloak, maybe I don't get something. Should I draw a sagittal diagram ?
Anyway, thank you for your feedback.
Regards,
Nikita

my upstream application is sending its own token
I think this sentence is very confusing and I can feel some design issue behind this, unless you may clarify this better. Upstream means = behind proxy, so this does not make sense if this app already handles token exchange.

We should be able to fallback to cookie inspection if the Authorization header does not contain the access > token from keycloak.
As far as I could test things this is already working like this, only I did not have the case where both cookie and authorization header were present.

Is PR #445 allow this ?
It allows this specifically for the case when you want access token in cookie to be encrypted, while letting token in header to remain in-the-clear

I think this sentence is very confusing and I can feel some design issue behind this, unless you may clarify this better. Upstream means = behind proxy, so this does not make sense if this app already handles token exchange.

Ok I will try to explain it more clearly :thumbsup:
Background : The upstream application (the app behind the proxy) does not have official openid support. It relies only on HTTP Headers sent by Gatekeeper. I don't belong to the development team of this application, I'm working with a black box approach.
End-user authentication with Keycloak : Once the proxy has validated the request against keycloak (i.e redirection to the SSO login page if no valid session is found), it forwards all requests to the upstream application. Exchanged tokens are stored encrypted in the cookie (kc-access, kc-state). This is the normal behavior, no issues here.
End-user authentication with the app itself :
Once the user is landing on the application, forwarded by the proxy, the Javascript of the frontend is querying the application API. It touches a "/login" endpoint that generates a token. Sample : https://gist.github.com/nirousseau/33bb767ada8761fe823fca37d84f94bf
This is a Bearer token that is sent in HTTP Authorization header. It is used by the frontend when querying the API of this application. It contains the user role and business logic information. Since this token is not issued by keycloak, but by the application itself, gatekeeper is confused. This is the root cause of my problem.

As far as I could test things this is already working like this, only I did not have the case where both cookie and authorization header were present.

I agree. However, from my experiments, when the Authorization Bearer token is set, but not issued by keycloak, gatekeeper does not look for the cookie token. It just fails with error no session found in request, redirecting for authorization {"error": "missing required claim: sub"} and redirect the request to the SSO login page. (tested in my environment with enable-encrypted-token=false, Authorization header is set along with tokens in cookie kc-access, kc-state.)

It allows this specifically for the case when you want access token in cookie to be encrypted, while letting token in header to remain in-the-clear

Ok, I guess this PR will solve partially my issue. As explained above, your PR combined with a mechanism that also looks for the cookie if the Authorization Bearer provided is not valid for gatekeeper (a new case when the exception  missing required claim: sub is raised) will address my issue.
Is that clearer ? What strategy do you want I investigate ?
Thank you very much for your support,
Regards,
Nikita

@nirousseau yes much clearer now.
My two cents on this is that the heart of your problem is that several apps are competing for the "Authorization" header. This is a source of confusion indeed, but now I think I understand the point.
I don't think this proxy should be twisted to the point of supporting this kind of mismatches.
Authorization headers passing through this should only be valid, keycloak-issued headers.
IMHO, letting traffic passing through with such headers from other issuers would cause confusion and security issues with other users of this proxy.
There are other ways to work around this particular issue, without twisting the proxy's logics.

For one, an acceptable solution close to what you did would be to set a config parameter like "cookie-only-auth": then whatever the headers say, cookie is used.
For another (personally I would have done it this way), upstream passes through a more capable reverse-proxy (e.g. nginx) which rewrites headers back and forth and isolate this specifics of your legacy app: your upstream Authorization header becomes something like X-App-Authorization when received by front-end and sent back to gatekeeper proxy,  then is transformed back to Authorization just before reaching your app

I think the second approach is more flexible, at the cost of an additional proxying, which will eventually disappear when this app has eventually migrated to fully integrated authZ with your IDP.

Hello,
Indeed, letting the Authorization going through the proxy can be a security issue : we are delegating the authentication role to the application, where the SSO should be the only trusted token issuer.
Pros/Cons PR473 :
Pros : it is convenient for non-mature applications, we are not required to add another proxy in order to modify headers.
Cons : add more complexity to Gatekeeper decision tree, requires more tests, can lead to security issues.
Mitigation : We can notify at launch that the option can lead to security issues.
To my mind, I prefer not adding another proxy for my case. Even if the second approach is more flexible, I prefer limiting the number of proxy because of latency issues.
For now, is this PR still relevant for Gatekeeper as a community contribution ? What can I do ?


People you might be intereseted section, need more attention

The username for the authors isn't looking good, maybe shorten that, and make it with @

You need also to be able to click on the user you're interested in following and be redirected to his profile


add qtbase to PATH of flameshot

I've found the flameshot service not working for me.
After some debugging, it seems that flameshot requires qtbase to be in PATH. (which on my system, as I don't have kde installed, is not the default)
This patch is working, but I'm not 100% sure if this is the right approach. This might also be regarded as an impurity in the flameshot dervation. What do you think?

Can confirm that this patch makes flameshot work for me.

Sorry this took a while, had a lot on my mind. I've changed it to use %h/.nix-profile/bin. I have a basic understanding of propagatedBuildInputs now :)

Cool, thanks! I've rebased to master in 965bad626adba63a579a31ef1688d912d0cf820b with a slightly change commit message.
Hopefully we can come up with a better solution in the future.


Mount-DiskImage does not respect the WhatIf parameter

Mount-DiskImage does not respect the WhatIf parameter
Example

Input: Mount-DiskImage -ImagePath c:\iso\MyImage.iso -WhatIf
Output:

Expected: no mounted image

Actual: mounted image

$PSVersionTable
PSVersion                      6.2.0
PSEdition                      Core
GitCommitId                    6.2.0
OS                             Microsoft Windows 10.0.18362
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

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

ID: 543feba4-c3b8-188e-f53f-614763723f26
Version Independent ID: b8b6b157-df42-8b88-43d3-41ae0f865d91
Content: Mount-DiskImage (storage)
Content Source: docset/windows/storage/mount-diskimage.md
Product: w10
Technology: powershell-windows
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

@officedocsbot assign @e0i

@MCTSQL
The issues section of this repository is intended for documentation feedback.
Please consider checking any relevant resources and asking the community about your problem via the following link.
PowerShell Community
Thanks.

@officedocsbot close


Will this work on windows 11?

Would you like have a tool or script added? Please include a link
Name of the tool requested and a link to the tool
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
If related to a problem, describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Windows 11 is currently not supported, so a number of tools will not be installed and certain changes applied in Windows 10 will not happen in Windows 11.
There are some features still being worked on before we officially support Windows 11.
That being said, I do have it installed on my Windows 11 VM and it hasn't been an issue to use.


chore(main): release picom 1.15.5

:robot: I have created a release beep boop
1.15.5 (2024-08-22)
Bug Fixes

picom: missing comma in opaticty rule (2992f64)
picom: no trailing comma (9cbcdf0)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

picom-v1.15.5
:sunflower:


fix error when active text editor does not belong to any of the workspace folders of a multiroot workspace

Overview
When you have a multiroot workspace and the active text editor is something that does not belong to any of the workspace folders (like when you open a file directly from your desktop) you get an error Explorer Exclude: Workspace Folder Not Found. Open Folder or Workspace and try again.
Reviewer

Where should the reviewer start? How to Test? Background Context? etc ( required )

Open a vscode window with a multiroot workspace
Open the file from your desktop (like a markdown file)
Reload the window
Wait until vscode finish to startup and you should not see any error now.

Checklist

I have tested each of the following, and they work as expected: ( required )

[x] Meets Contributing Guide Requirements
[x] Pulled in the Latest Code from the develop branch
[x] Works on a Desktop / Laptop Device

Documentation

Screenshots, Attachments, Linked GitHub Issues, etc ( optional )

fixes #37
What GIF best describes this PR or how it makes you feel?

seems i missed to add the Ready for Code Review tag, but I don't see how to update it now, anyway hope you see this fix 😁

Man, I keep finding new ways that Workspace messes things up for people.  I will get a release out for this today with your fix :)


Reset lastnr on client when mower is restarted

otherwise we are stuck with old logmessages

Fixed since we now reload client when uptime is lower than last time we checked.


Can't drag to select text anywhere on site

It's impossible to use the cursor to select any text on the website, including on the About page.
This is due to a CSS rule that applies user-select: none; to the whole body of every page. That rule was added in 6112b277fa7521add5a06782144cf92387ca062f, but based on the commit message ("disable touch selection of axis labels") I'm guessing the intention was not to disable selection everywhere?
Maybe the old class-based selectors replaced in that commit weren't covering all the required elements, but I imagine a reasonable middle ground would be a selector like #mainplot, so selection is disabled only inside the graph container?

Thank you for bringing up this issue, and for offering a solution! Text is selectable in the new version of the viewer.


ng2-dnd sorting in droppable list

I'm submitting a ... feature request

Do you want to request a feature or report a bug?

Is there any other alternative for this ?

What is the current behavior?
I have 2 lists.. one is Names and other one Target list. Name can be dragged from Names list and dropped in Target list. I want to sort the names in Target list , also i want the name 'john' in the first position always. Is there an alternative or have I done it incorrectly ?

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar.
I have referred from http://embed.plnkr.co/JbG8Si but the multi-sortable drop down isnt working for me when i implement it in my code! Thanks in advance.

Please tell us about your environment:

Angular version: 5.X.X
Browser: [ Chrome ]

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
`Simple sortable With Drop into recycle bin

              Names

{{item.name}}

Target List

                            {{target.name}}

                Recycle bin: Drag into me to delete it

Recycled: {{ listRecycled.toString()}}

export class SwitchComponent {
	 listOne: List[] =
	[  {
		  "id": 3067696,
		  "name": "john",
		  "iscarousel": true
		},
		{
		  "id": 3067696,
		  "name": "jacob",
		  "iscarousel": false
		},
		{
		  "id": 3067696,
		  "name": "dona",
		  "iscarousel": false
		},
		{
		  "id": 3067696,
		  "name": "david",
		  "iscarousel": false
		},
		{
		  "id": 3067696,
		  "name": "eva",
		  "iscarousel": false
		}
 	];
    listRecycled: List[]  = [];
    addTo($event: any) {
    	if ($event.dragData.iscarousel == 1){
    		this.listTarget.unshift($event.dragData);
    	}
      	else {
      		this.listTarget.push($event.dragData);
      	}
      console.log($event.dragData);
  }
  listTarget: List[] = [];
}
export interface List {
  id: number,
  name: string,
  iscarousel: boolean
}`

@akserg Please help..

Need the same feature @akserg , @vaishnavi-baliga  can I know how did you resolve this ?

i need this feature too. Please inform us how can we resolve this.

@ikismail @argygkou refer this https://github.com/akserg/ng2-dnd/issues/249

here is my solution, support sorting in droppable list
online demo:http://blog.giscafer.com/ngx-dnd-demo/#/target-sortable
source code: https://github.com/giscafer/ngx-dnd-demo
Hope can help you


Update VM templates after renaming the components referenced

Description
After issuing a rename API Call, like one.image.rename, the object new name doesn't appear updated on the VM Templates that reference it.
Use case
The calls could issue the name update for consistency purposes. Even though the operation remains fully functional due to the object ID being used for it.
Additional Context
This behavior can be implemented with API Hooks triggering on the rename calls.

Progress Status

[ ] Code committed
[ ] Testing - QA
[ ] Documentation (Release notes - resolved issues, compatibility, known issues)

OpenNebula uses ID as cananonical references. Names are provided for convenience, scoped to the the user namespace. As an image can be potentially shared  across users (e.g. ACLs) updating original templates will not be always possible. We recommended to use ID's in such cases
We'll close this as won't fix, if another use cases show up we'll reopen....


Coding Day 1

Goal

[x] Basic Window (Aspect Ratio 16:9)
[ ] Working scrolling background
[x] Player character with movement (WASD/Arrow Keys)
[ ] Enemies appearing from the right, moves to the left and disappears

Extra

[ ] Player shooting (Spacebar/Left Click)
[ ] Enemy getting shot takes damage and dies
[ ] Different paths for enemy (different start positions and end positions, for e.g start top right, end bottom screen)

done for now

ab094064bc5eb843efa48011376b1fee7ee83c20
d0fb96d6a874a35e446b3feffdfe46c0430f1ab3
001296f7058364e67a4760e216dcc4af1aea33c1
801c445f1194a2b179528303b1f7f76cc7602600
81cd06b46da3731f0f0508fde3d115444ed728a1
05b25e25ec77e5c3207eb42d00f87df2a974fd72
1ce4d014843cfbbaa8496a711648b716bbb38f50
7c0c8713b25184fc6b7604b92ceac6960db8afd4
01143077a1790683bcd31fa8741f8b79b1d9db94
4aca5f960628b90e9bd2f07a3485a375a00a799e
5119a8fa8187d2b0d98e09ff1fcc15fc66202776
680441f4e520b11678100abc19ff9b368a539a6f
3139289ba517ad184284d14e6d12b19f35cb1b0e
b69a86f08bbd7cbbc7a5acf6394ee02a04dbc5ef


add beforeReplace option

Idea from #274 issue.
Tried to add a beforeRequest option (function) to change HTML before appending it to the DOM.
I use jquery-pjax in my laravel5/angular application and I need to $compile HTML before insert it to the DOM. It's my first experience with jquery-pjax. So, maybe it's not right way, especially solution to provide beforeRequest option to onPjaxPopstate() (back/forward). But it's working fine for me now. Probably, it would be useful.

Any plan to accept/review this PR?

Sorry for no reply. I won't accept this right now as it adds yet another option on top of what is already becoming a messy implementation. The PR is alright and I understand the use-case, but this isn't something I want to go ahead maintaining right now. Instead, we will explore an alternative pjax implementation that will allow for a greater deal of flexibility regarding pre-processing of inserted HTML. Stay tuned.


⚠ Fortnite has degraded performance

In b103656, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1522 ms

Resolved: Fortnite performance has improved in b275d8b.


Laser & Region Lock Removal?

Any chance this fix can add those two things to the patch? The old community fix still hasn't been updated, so you still have to deal with region-locked pubs and not being able to switch to a laser with M+KB. I was hoping someone would update the old community fix, but it's been half a year now, so that project seems to be dead in the water.

Bump, been almost 2 years but a non-invasive way to enable laser signs for mouse while maintaing steam online play would be great.


Remove duplicated widget of the week video embed

The ScaffoldMessenger widget embeds its widget of the week video twice: https://main-api.flutter.dev/flutter/material/ScaffoldMessenger-class.html

The ScaffoldMessenger widget embeds its widget of the week video twice: https://main-api.flutter.dev/flutter/material/ScaffoldMessenger-class.html

Maybe it represents how ScaffoldMessenger can show a banner at the top of the page, and a snack bar at the bottom…

That makes sense - excellent docs show, don't tell. We should add a spinning video to RotationTransition's docs 😂


Detect "i3/config" filename

Detect "i3/config" which is the default for i3
Remove redundant filenames.

Please consider making changes to the upstream vim repo directly as this code is there as of https://github.com/vim/vim/commit/8176be159859deb9cf6455565bd7b24b3dcf17b9

@hiqua Oh, thanks for letting me know.


Implement Firestore numeric transforms

Sorry, as I'm new to this repo and it wasn't clear from PROCESS.md or travis.yml, but when will this appear in the nuget repo please? The packages haven't been updated in 2-months and I'm really hoping to use Increment in my .net project. M thanks.

I've just received an email comment asking when this will appear in NuGet, but I can't see it here... not sure what's going on. I'll try to do a release next week.


Bluedroid Ble encrypted MITM communication  (IDFGH-3273)

Environment

Development Kit:     ESP32 DOIT (ESP32 WROOM 4MB)
Kit version :  DevKit: v1
Module or chip used:   ESP32-WROOM-32
IDF version :  v4.2-dev-532-g6f7be93
Build System:  CMake | idf.py
Compiler version : xtensa-esp32-elf-gcc (crosstool-NG esp-2019r2) 8.2.0
Operating System: Linux
Using an IDE?: Yes ( Eclipse IDE [Version: 2019-06 (4.12.0)] with ESP-IDF Eclipse plugin v1.0.1 )
Power Supply:    USB

Problem Description
Need to know about the process for communication using Bluedroid stack with ESP_GATT_AUTH_REQ_MITM in Central BLE device.
//Detailed problem description goes here.
I am testing the ESP32 BLE communication with Android device with nRF Connect Application.
I have configured Bluedroid stack as Central/Client BLE and I am Able to perform Bonding and communication with the characteristics having read/write permissions.
Now when the permission is change to read encrypted MITM in nRF Connect App, ESP32 is unable to perform read and write operation though we have set auth request type as "ESP_GATT_AUTH_REQ_MITM".
Please update me, if there is any change required in procedure of encrypted MITM communication to make it possible.
Please check the attached logs as well as source and sdkconfig files for reference.
Expected Behavior
The device must able to perform read and write operation with characteristics having permissions Read/Write Encrypted MITM.
Actual Behavior
The device is unable to communicate and gives error on calling read and write api.
Steps to reproduce

Configure the bluedroid gatt secure client example code or use the attached sdk config and test code.
Change the read write permission to ESP_GATT_AUTH_REQ_MITM.
change the permission in nRF Connect app for the current selected characteristics.Uncheck read and write permission and check read encrytped MITM  and write encrytped MITM in app.
Start the Advertiser with name as fixed in Code.
Wait for the pairing request (if done for first time).
As per the test code, device will perform read and write after 10 seconds.
here as soon as device performs read and write operation, it gets error.

Debug Logs
I (5365) GATTC_DEMO: ESP_GATTC_SEARCH_CMPL_EVT
I (5365) AppBle: Received event: eAppBleSearchServices!
I (20935) AppBle: Received event: eAppBleWrite!
I (20935) GATTC_DEMO: Writing handle:42, connid:0
E (20935) BT_GATT: Unknown operation encryption completed
W (34975) BT_APPL: bta_gattc_conn_cback() - cif=1 connected=0 conn_id=1 reason=0x0013
E (34975) GATTC_DEMO: write char failed, error status = 85
E (34975) GATTC_DEMO: Write Failed
I (34975) GATTC_DEMO: ESP_GATTC_DISCO

Other items if possible
gatt_client_demo.elf.zip
bludroid_central.zip
Bluedroidble_errlog11052020.txt

@promptps Thanks for the detailed report, we will look into.

Has your issue been resolved?


Simplify class section under persistent-volumes.md

This closes #42137
Simplified the documentation.

/auto-cc

Hi @Affan-7 , I'm closing this PR because needs rebase as there is a merge conflict
When you have time to rebase, feel free to reopen this PR with /reopen in a comment
/close


dont use empty

mild improvement to use langchain prompts a bit more - will work on larger improvements tho!

Thanks!
Mine was a workaround to have an f-string instead of normal string...
Did not think of just putting the whole prompt inside the bracket.


Default webpack excludes .jsx files in 'node_modules' from being compiled by Webpack

If I have a set of JSX modules in an npm package and I want to import them to use in a story, I get an error that says I need the appropriate loader. In our default webpack config, we exclude node_modules from our JSX loader.
https://github.com/storybooks/storybook/blob/master/app/react/src/server/config/webpack.config.js#L37
https://github.com/storybooks/storybook/blob/master/app/react/src/server/config/utils.js#L5
Most component modules like Airbnb's React Datepicker actually transpile to ES5 when exporting to CommonJS so both the original JSX and the ES5 version are available. If we import the transpiled ES5 file, we lose the ability to use react-docgen to provide automatic documentation generation.
The question is, should I just reconfigure the loader on my end or is it beneficial if I remove the excludePaths from .jsx in our default config in our codebase?

Really good question! I would like to ask more webpack experts on this matter.

Definitely NOT a webpack expert, but I would be concerned about the performance implications of this change. Have noticed (I think! Have not tested rigorously!) increased build times when I remove excludePaths, etc. So we would probably want to make sure that's not the case before loosening anything up.

Iirc according to webpack it is a bad idea to include node_modules to the compilation (as shilman said because of performance and compilation time issues). Users should manually include those node modules that they want to be compiled.

I'm gonna close this issue since I think it's better to leave as is than to remove the excluded node_modules.


compatibility with react-scripts-ts?

Hi there! Thanks for this library.
I'm wondering if it's possible to use it along with react-scripts-ts, too?


Fix license headers - part 2

Fix (again) license headers
This PR is created automatically by Matks PrestaShop Repositories Bulk Editor

Travis complains, I'll redo this PR


Dataframes: divisions vs partition (min, max) and other partfile stats?

This is less of an issue and more a structural question that has bothered me for a while and I'm wondering if it make sense at all for a future version of dask, or if this is better solved by other approaches.
Dataframe divisions are lossy by design:
from dask.dataframe import from_pandas, concat
ddfs = [
    from_pandas(pd.DataFrame({'a':range(5)}), npartitions=1),
    from_pandas(pd.DataFrame({'a':range(5)}, index=range(10, 15)), npartitions=1)]
"""
In [6]: ddfs
Out[6]:
[Dask DataFrame Structure:
                    a
 npartitions=1
 0              int64
 4                ...
 Dask Name: from_pandas, 1 tasks, Dask DataFrame Structure:
                    a
 npartitions=1
 10             int64
 14               ...
 Dask Name: from_pandas, 1 tasks]
"""

concat(ddfs).get_partition(0)
"""
Dask DataFrame Structure:
                   a
npartitions=1
0              int64
10               ...
Dask Name: get-partition, 5 tasks
"""

In the above example, we lose the fact that the initial partition has a max value of 4 - there are no rows between 4 and 10.  We also lose the symmetry given that the last division is an inclusive end (index <= divisions[i+1]) where others are exclusive (index < divisions[i+1])
When dealing with indices that are relatively dense within ranges, this is fine.  However, there are plenty of cases where an index is relatively sparse - I deal with geospatial indices a lot, for instance, where a partition might contain data from a certain region of a map, which is nicely indexed by something like a https://en.wikipedia.org/wiki/Geohash - but there may be a lot of space between the bounds of their hashes depending on how close the regions are.  Datetime ranges also make sense here, if you have big data sets with lots of time gaps in between.  Many algorithms could benefit by knowing the precise span of data within a partition, ie to know that no partitions/rows are impacted by a filter/query etc or to do some math on duration/span of a partition via the metadata alone.  I can leverage this to some extent by operating on lists of single partition dask dataframes, but it would be nice to let dask handle that kind of complexity for me.
This information exists in parquet partfiles and row group statistics for instance (don't know off the top of my head about other data stores) and to my knowledge is better leveraged by spark in its dataframes.  It is thrown out after reading the metadata, as opposed to if I read one part file at a time into separate dask dataframes.  Some of the functionality is also exposed via parquet filters on read, but it seems like dask could incorporate this better at the dataframe level if it kept the stats around.
Similarly, other column min/max stats can be useful for accelerated filtering etc, though obviously are more distant from what dask already exposes via the divisions.
Do you think switching from divisions to index ranges, for instance, would be an appropriate thing for dask? Is it even achievable with a realistic amount of work?

Another small case where this is an annoying, albeit fixable, error:
together = concat(ddfs)

concat([together.get_partition(i) for i in range(together.npartitions)])

ValueError: All inputs have known divisions which cannot be concatenated in order. Specify interleave_partitions=True to ignore order

It looks like the difference here isn't with get_partitions losing data, its with the first two partitions of the two dataframes being merged.
In [5]: concat(ddfs)
Out[5]:
Dask DataFrame Structure:
                   a
npartitions=2
0              int64
10               ...
14               ...
Dask Name: concat, 4 tasks

The question then becomes, when we have two dataframes with overlapping divisions, how should we merge them?

I get the concern about adding more metadata in general, but I don't understand your prior comment about merging.  Knowing the max value of an index in a partition can only help a merge, since it's possible that there are more non-overlapping partitions that can be interleaved.  When the values of indices overlap for two partitions in different dataframes, you are no worse off than you currently are - the partitions either have to be split or merged:
ddfs = [ # A dataframe from the concatenation of these
    from_pandas(pd.DataFrame({'a':range(5)}), npartitions=1),
    from_pandas(pd.DataFrame({'a':range(5)}, index=range(10, 15)), npartitions=1)]

# Should be mergeable with :
from_pandas(pd.DataFrame({'a':range(5)}, index=range(5, 10)), npartitions=1)]
# So long as interleave_partitions=True and dask knows the max of each partition index values

On your first comment, yes it is the merge which is lossy (and only lossy for the ddf.divisions, not the computed frame itself).
I can imagine something like:
class DataFrame():
    ...
    index_bounds = [(0, 4), (10, 14)]
    @property
    def divisions(self):  # Backwards compat, but should be unnecessary
        return tuple([b[0] for b in self.index_bounds] + [self.index_bounds[-1][1]])

There may even be sane default values for index max values, such as div[i+1]-1 for integers, etc for various dtypes, if we don't know them but do know the divisions.  I've seen that approach in hbase/happybase as well with byte decrements for max value of a row key in a chunk.
Do you think its worth even attempting just for the index/divisions case, or would all of this just be way too hard given the current design?

It's doable, but would be a non-trivial amount of work.  I think that, in the common case, it also won't be informative.  In my experience data is usually pretty continuous, and so the minimum value of the next partition is usually a very good estimate for the minimum value of the previous partition.  I'm actually somewhat surprised that you have a real-world situation where this is not the case.
You're more than welcome to try to implement this.  I think that seeing the difficulty or ease with which this can be implemented would help to determine if it should go in or not.
Alternatively, if you're interested in partitioning data along geospatial lines, you might consider taking up a project like dask-geopandas (also see the second half of this blogpost).  This seems like a cleaner solution to me than relying on geo-hashing tricks.

Thank you, yes, I've been following the dask-geopandas bit and would probably already be using it if it were released and production ready.  Right now my team is doing a poor approximation of that with normal parquet-backed dask dataframes w/ a WKT column and going to/from geopandas w/in a function, say:
def as_geopandas(func):
    def wrapped(df):
        gdf = func(deser_pandas_to_geopandas(df))
        return ser_geopandas_to_pandas(gdf)
    return wrapped

some_dask_df.map_partitions(as_geopandas(lambda gdf: gdf.buffer(10))

This is obviously not as fast but works very well otherwise - and maintains clean compatibility with spark and tools like geospark and magellan (i haven't seen any geopandas work w/ parquet, just shapefiles!).  The main advantage of using a geospatial index is to enable predicate pushdowns for spatial joins or queries either via the dask/pandas index or even to filters in read_parquet.  I can imagine dask-geopandas could do something similar by writing total_bounds for a partition into the parquet metadata (?) and having something like dask_gdf.partition_bounds=[bbox0, bbox1, ...] but then that would be geopandas specific and not work elsewhere.  With my approach I can also use normal dask stuff too w/o caring about the GEOS interface or extra ser/deser steps w/ shapely or whatever, and just treat the geometry as a text column (or not load it at all!).  This is a very interesting topic but beyond the scope of this issue :).
I'll keep thinking about this and poke through the code to see if it makes sense to continue or not.

@gorlins , what you are asking sounds like a great idea. But as you say, the data is stored as binary strings, and so the chunk statistics' min/max are meaningless as there is no geo type in parquet.
You can store arbitrary extra metadata in both a global key/value store or a column-chunk specific one (which is also saved in the same file footer), and we use this for some pandas-specific type information. In theory the per-chunk divisions could go here, or the whole set in the global store. In order to make use of this, any loader must know that the column type is geo, and know to look for the extra metadata. Any filtering must then know to use logical operations like in and not in (and something for 'overlap'?). It's no obvious how dask or geopandas would push that down except in the initial set-up of the dataset object (filters=-style).
I could imagine coding that up in fastparquet, but there ought to be agreement on exactly what should be stored, where, the operations to support, etc.
In addition, there are other types with complex filtering that could be considered (e.g., filtering IP addresses by a mask), it doesn't really feel like any of this belongs in the data ingest layer when the number of logical types explicitly supported is limited.

I tried in both way , gettting error,
dateRange=list(range(1989,2020))
years=[]
for year in dateRange:
str_year=str(year)
years.append(str_year)
repartition the data - takes 0.001 seconds
permits_repartitioned=permits_indexed.repartition(divisions=years)
ValueError: right side of old and new divisions are different
divisions = pd.date_range('2009-01-23', ' 2012-04-02', freq='YS').tolist()
divisions[0] = permits_indexed.divisions[0]
divisions[-1] = permits_indexed.divisions[-1]
permits_repartitioned =permits_indexed.repartition(divisions=divisions)
TypeError: '<' not supported between instances of 'Timestamp' and 'str'

@hafez-ahmad your comment seems unrelated.


Set up Selenium web testing with Travis CI

Mainly for POST|PUT|PATCH where we want to confirm the result on the website.
Research:
https://testingbot.com/support/other/travis-ci

I don't know if I need to do this, honestly. I can check the results via the API.


lets have a canonical URL in the UI we can link to view/open/create a workspace for a given set of parameters

e.g. on a Pipeline / BuildConfig / Deployment / Work Item we may be able to find the github URL, branch and possibly Che stack ID.
It would be nice to be able to link to a single page via "Open In Che" links around the UI which would then:

check to see if there is a workspace already for the given git URL, branch and stack ID and if so open it
if not prompt the user to create a workspace; when its ready let them open it.

i.e. similar to the behavior of the Codebases UI; but letting folks link to a codebase page without knowing what the codebase is yet - just knowing the git URL, branch, stack
Once we've something like this we can then add an 'Open in Che' link to the Pipelines page for example

@dlabrecq wonder if you had a clue here? the basic issue is when viewing, say, a Pipeline, WorkItem, Deployment or some other resource we may find a git URL / branch / che stack; but not be aware if there's a Codebase/Workspace for it yet.
So figure we could just have a page we link to that then wraps up looking for the corresponding codebase/workspace and supports lazily creating one on the fly (maybe with the user confirming if they wanna add the codebase etc).
We can also then link to this page when using the Space wizard to create a new page?

We currently have the ability to retrieve a list of the user's codebases which can be iterated over to match a GitHub URL. If a match is found, we can easily open Che.
(It's my understanding that the Che APIs don't accept a branch. The user must select a branch within Che.)
If there is no matching codebase, you can create one providing you have a GitHub URL. If you're suggesting a GitHub URL is always available, I suspect all this could be done via a service instead of a new page.
If not, a modal could prompt the user to enter one? Although, I'll defer to the @catrobson here.

I wonder if for now we can create a component like:
'''
Open Che<...
'''
Where everything but git URL is optional - we can then use this markup on pages like the pipelines & work items - then the implementation can lazily load the codebases to open a modal or whatever?

Though a service to open the link may be easier too ;)

@jstrachan is this still something you think we should pursue? I'm not clear on how this would work.
cc @maxandersen @catrobson

yes I think we should still do it as there are going to be many places in the UI we need to 'open in Che'. In terms of how it would work I'm assuming its an angular component along the lines of
<open-in-che-link [gitUrl]="foo" [branch]="bar">Open in Che</open-in-che-link>

or something like that.
We'd like to use this on multiple Pipeline / Build / Deployment / Pod UIs for a start; am sure we could use it in the planner when we start supporting PRs or commits too.

This issue was moved to openshiftio/openshift.io#919


Update NumericalSpatialJoin.py

Add "last" as a merge rule. You will also have to edit the Parameters in the Tool Properties but I am not sure how to do that in the script if anywhere.

I like that you contributed the easy part though.

Addressed in 07fac03c5123915781f0b8fe6718f7a122acb859


settings: lcd calibration bug

The code logic does not work because the function with no return, returns undefined. Ends up that both prependListener and on are called, creating 2 callbacks, yet only 1 is removed.
Noticed it from running lcd calibration, then touch anything else and it goes back into calibration.

I could trigger the bug just now and it was resolved when I switched to your suggested change.
Thanks!


Rails 7: logout redirect not working

Set this in application_controller.rb:
  def after_sign_out_path_for scope
    root_path
  end

You expect the logout to redirect the user to root.
However Devise returns a redirect with status 302, which does not work with Turbo.
All redirects must return 303 (i.e. status: :see_other) in order to work with Turbo.
This should be fixed in Devise in order to work with Rails 7.
Related: https://github.com/rails/rails/issues/44170

Not only the redirect for logout, but also the other redirects should use the status 303 in order to work with Turbo.
(The only other alternative would be to make Turbo accept the 302, but from the related issue linked above it seems that Rails team won't fix that)

Also note that by using 302, after logout response, you also get an "extra" DELETE request to root path, which results in a 404.
This is quite scary, since you get an unexpected DELETE request on random path!

I think this is related to https://github.com/heartcombo/devise/pull/5453
While the PR isn't merged I would just disable turbo on devise views

You have to change from:
<%= link_to "Sign out", destroy_user_session_path, method: delete %>
to
<%= link_to "Sign out", destroy_user_session_path, data: { turbo_method: :delete" } %>

@designium Yes, sure, I already use the correct code for Turbo... However there is the bug described in the original post.

I have found simple hotfix
# app/controllers/sessions_controller.rb
class SessionsController < Devise::SessionsController
  def respond_to_on_destroy
    respond_to do |format|
      format.all { head :no_content }
      format.any(*navigational_formats) { redirect_to after_sign_out_path_for(resource_name), status: :see_other}
    end
  end
end

# config/routes.rb
Rails.application.routes.draw do
  # ...
  devise_for :users, controllers: { sessions: 'sessions' }
  # ...
end

You just need add status: :see_other (303) to redirect_to method arguments to make it works correctly

I fixed this as follows:
<%= link_to("Log out", destroy_user_session_path, method: :delete, data: { turbo_method: :delete }) %>

module Users
  class SessionsController < Devise::SessionsController
    def destroy
      super do
        # Turbo requires redirects be :see_other (303); so override Devise default (302)
        return redirect_to after_sign_out_path_for(resource_name), status: :see_other
      end
    end
  end
end

@mattbrictson you can also add notice: I18n.t('devise.sessions.signed_out') to show the successful sign out message
return redirect_to after_sign_out_path_for(resource_name), status: :see_other, notice: I18n.t('devise.sessions.signed_out')

I just notice that when you are using a button to log out:
<%= button_to "Log Out", destroy_user_session_path, method: :delete %> the the redirect works as expected and the user is taken to the root_path.
However as soon as you are using a link things are not working (mostly due to the status issue mentioned above).

Also, overriding the after_sign_out_path_for(resource_or_scope) method in the ApplicationController does not work when using a link... so there is no way to fix this issue without first fixing the status problem.

any news?

nope...

This worked for me initially:
<%= link_to "Logout", destroy_user_session_path, data: { turbo_method: :delete } %>

But after making these turbo changes from:
// app/javascript/application.js
import "@hotwired/turbo-rails"

to this
// app/javascript/application.js
import { Turbo } from "@hotwired/turbo-rails"
Turbo.session.drive = false

then logout broke.
However, this worked:
<%= button_to "Log out", destroy_user_session_path, method: :delete, data: { turbo: false } %>

Hope it's useful.

I ended up with this which makes a mini form:
<%= button_to "Logout", destroy_user_session_path, method: :delete, form: {  data: { turbo: :false } } %>

It works for me
<%= button_to 'Logout', destroy_user_session_path, method: :delete, form: {turbolink: false} %>

Looking at the patch by @mattbrictson I see it looks really similar to the PR here https://github.com/heartcombo/devise/pull/5410

Disabling Turbo is the wrong answer here.  This issue is specific to an incorrect redirect being returned by Devise::SessionController.
My Selenium tests fail like this:
2) Authentication as a User allows a user to Log In and Out
     Failure/Error: raise ActionController::RoutingError, "No route matches [#{env['REQUEST_METHOD']}] #{env['PATH_INFO'].inspect}"

     ActionController::RoutingError:
       No route matches [DELETE] "/"

The Rails log will follow a pattern similar to this:
Started DELETE "/users/sign_out" for <IP_ADDRESS> at 2022-09-02 17:00:43 -0600
Processing by Devise::SessionsController#destroy as TURBO_STREAM
  User Load (1.6ms)  SELECT "users".* FROM "users" WHERE "users"."id" = $1 ORDER BY "users"."id" ASC LIMIT $2  [["id", 1], ["LIMIT", 1]]
Redirected to http://<IP_ADDRESS>:57460/
Completed 302 Found in 10ms (ActiveRecord: 1.6ms | Allocations: 1787)
Started DELETE "/" for <IP_ADDRESS> at 2022-09-02 17:00:43 -0600

The issue is that Turbo is attempting to render after_sign_out_path with the incorrect HTTP Verb (DELETE, in this case).  You want your Devise controller to respond with HTTP 303 See Other.  The solutions that override Devise's default behavior and return 303 See Other should be used.

I fixed this as follows:
<%= link_to("Log out", destroy_user_session_path, method: :delete, data: { turbo_method: :delete }) %>

module Users
  class SessionsController < Devise::SessionsController
    def destroy
      super do
        # Turbo requires redirects be :see_other (303); so override Devise default (302)
        return redirect_to after_sign_out_path_for(resource_name), status: :see_other
      end
    end
  end
end

None of the other replies actually fix the OP's original issue.

module Users
  class SessionsController < Devise::SessionsController
    def destroy
      super do
        # Turbo requires redirects be :see_other (303); so override Devise default (302)
        return redirect_to after_sign_out_path_for(resource_name), status: :see_other
      end
    end
  end
end

I'm sorry, can anyone - maybe @mattbrictson or @danielricecodes - tell me, where to put that?
Thanks in advance.

This issue is not specific to Turbo, it's how the Fetch API behaves: when the HTTP status is 302, the browser will send another request to the redirect URL using the same HTTP method as the initial request. Turbo wraps the Fetch API, but I ran into the same issue in our app which doesn't use Turbo.
In our case we solved this by changing the HTTP method for the sign out route from DELETE to GET.
In config/initializers/devise.rb:
  # The default HTTP method used to sign out a resource. Default is :delete.
  config.sign_out_via = :get

Then you can use a regular link in your view, no Turbo/JS needed at all:
<%= link_to "Sign Out", destroy_user_session_path %>

@Havoc85
You need to generate or create an inherited Devise controller for sessions first. You can do that by running the following command (assuming that "user" is your Devise model):
rails generate devise:controllers users -c=sessions`

Uncomment the destroy method in the new file that gets created and place the above code inside the method.
Don't forget to update your Devise routes for the changes to take effect.

@Havoc85
You need to generate or create an inherited Devise controller for sessions first. You can do that by running the following command (assuming that "user" is your Devise model):
rails generate devise:controllers users -c=sessions

Uncomment the destroy method in the new file that gets created and place the above code inside the method.
Don't forget to update your Devise routes for the changes to take effect.

Thank you for that description! That helps a lot.

@Havoc85
You need to generate or create an inherited Devise controller for sessions first. You can do that by running the following command (assuming that "user" is your Devise model):
rails generate devise:controllers users -c=sessions

Uncomment the destroy method in the new file that gets created and place the above code inside the method.
Don't forget to update your Devise routes for the changes to take effect.

I followed all the instruction and still face with the actionController::RoutingError (No route matches [GET] "/users/sign_out"): Not sure if there is anyway to find the root cause

This worked for me initially:
<%= link_to "Logout", destroy_user_session_path, data: { turbo_method: :delete } %>

But after making these turbo changes (to fix an unrelated issue of some bootstrap javascripts not working) from:
// app/javascript/application.js
import "@hotwired/turbo-rails"

to this
// app/javascript/application.js
import { Turbo } from "@hotwired/turbo-rails"
Turbo.session.drive = false

then logout broke.
However, this worked:
<%= button_to "Log out", destroy_user_session_path, method: :delete, data: { turbo: false } %>

Hope it's useful.

👍 Thanks

false

Not a correct way because we want to use turbo

My solution:
sessions_controller.rb
class Users::SessionsController < Devise::SessionsController
  def destroy
    super do
      # Turbo requires redirects be :see_other (303); so override Devise default (302)
      return redirect_to new_user_session_path, status: :see_other, notice: I18n.t("devise.sessions.signed_out")
    end
  end
end

<%= link_to "Sign out", "/users/sign_out", method: :delete, data: { turbo_method: :delete, turbo_confirm: 'Are you sure?' } %>

<%= button_to "Sign Out", destroy_user_session_path, method: :delete %> Did not work.
<%= button_to "Log out", destroy_user_session_path, method: :delete, data: { turbo: false } %> Did work; thank you @stevecondylios
However, I ended up using @revskill10 's solution as I wanted use a link_to rather than a button. Thanks everyone for your wisdom!

data: { turbo_method: :delete }

Using the first line of codes works perfectly for me! Thank you! I highly recommend everyone to have a try.

Setting config.navigational_formats = ['*/*', :html, :turbo_stream] in devise.rb seemed to work for me

The main branch should contain all that's necessary for fully working with Turbo now, which should fix this. A new version will be released soon, but feel free to test it out from the main branch in the meantime, and report back on any issues. Thanks.

You have to change from:
<%= link_to "Sign out", destroy_user_session_path, method: delete %>
to
<%= link_to "Sign out", destroy_user_session_path, data: { turbo_method: :delete" } %>

typo  data: { turbo_method: :"delete" }

I just started working on Rails 7 app and experienced same issue.  My issue was login and logout works. It just renders the new page at the bottom of the login page instead of redirecting. I was able to fix by:
For login button: = f.submit('Login', class: 'btn', params: { prompt: 'login' }, data: { turbo: 'false' })
For Logout: = button_to('Log out', user_session_path(current_user), class: 'btn', method: :delete, data: { turbo: 'false' })

This worked for me initially:
<%= link_to "Logout", destroy_user_session_path, data: { turbo_method: :delete } %>

But after making these turbo changes (to fix an unrelated issue of some bootstrap javascripts not working) from:
// app/javascript/application.js
import "@hotwired/turbo-rails"

to this
// app/javascript/application.js
import { Turbo } from "@hotwired/turbo-rails"
Turbo.session.drive = false

then logout broke.
However, this worked:
<%= button_to "Log out", destroy_user_session_path, method: :delete, data: { turbo: false } %>

Hope it's useful.

This worked for me. Thanks a lot!!!


Validate Orchard, Sapling, Sprout anchors

Motivation
Once we are calculating the Orchard, Sapling, and Sprout note commitment trees and tracking the roots of those trees as they exist for a validated block, we can use that to look them up when validating that the anchors in new transaction refer to treestates we have validated.
Specifications

Designs

https://github.com/ZcashFoundation/zebra/issues/2425
https://github.com/ZcashFoundation/zebra/blob/main/book/src/dev/rfcs/drafts/0005-treestate.md
https://github.com/ZcashFoundation/zebra/issues/1320
State Query Design
In the transaction verifier service, with access to an instance of the state service, when Orchard Action, Sapling Spend, and JoinSplit anchors are parsed out, make a Request::AwaitAnchor request, and make sure that returns with an Ok() , along with all the other async checks.
We need to make sure we are looking up anchors in the set of valid roots for this transaction's chain. This requires some design work.
Alternative Design
Check the anchors in the non-finalized state, when updating the chain (UpdateWith<Transaction>).
Interstitial Sprout Anchors
For Sprout, interstitial treestates between JoinSplits in the same transaction are legal. For this piece of work, we can skip doing that for now, and just try to look up anchors in the set of Sprout roots at the end of blocks, which are also valid possible anchors. As part of this work, we should log loudly if we see a Sprout anchor that we try to look up and do not find in our state, as it may not be an invalid anchor, it may be an  interstitial one we aren't computing yet.
As an alternative, we could split the sprout work out of this ticket, and only check sprout anchors after we've implemented interstitial treestates.
Related Work
Blocked on https://github.com/ZcashFoundation/zebra/pull/2458 merging

Closed Draft PR: https://github.com/ZcashFoundation/zebra/pull/2536


0.40.0 missing ability to set/update priority

How can i set the priority on 0.40 branch

Still a wip so I probably just missed this, am on leave for another two weeks but have a little time in a few days to check this out.

@zhouxl this is now in tag 0.40.0.beta3 I can't release to Cocoapods due to Cocoapods issues.


Add Pavithradevadiga's file

I am new to github and i have made some basic stuffs 😁

I merged the FirstBranch


PWA for Desktops

Feature Request

i dont knwo what PWA is .
But i am guessing that you can just use electron should be enough, just like using cordova for mobile.

Progressive Web App

ah yes i see.
So if its for Desktops, i guess its electron to contain it ?

It think PWA for desktop is not "an issue" related to Polymer. If you are able to run an web app on a desktop Polymer should work.
The question is "How can I create a web app that follows the PWA spec?".
And you're right, Electron could be a really good choice! 💯

@LM450N thanks, wil try it out


Confused about this as well. Is there anyway to throw an uncaught exception anymore?

I ended up replacing the Promise library as described above...now the errors get logged but still not thrown. Also tried the catch addition but that didn't help particularly - and the  multiple catches in case there was some weirdness with using co's within co'a in large call
On Sun, Jan 11, 2015 at 5:24 PM, Matthew Mueller<EMAIL_ADDRESS>wrote:

Confused about this as well. Is there anyway to throw an uncaught exception anymore?
Reply to this email directly or view it on GitHub:
https://github.com/tj/co/issues/174#issuecomment-69485168

why do you actually want to throw uncaught exceptions? either way, that's a promise issue, not a co issue.


control text format problem

Tested versions
godot 4.2.1 stable
System information
windows11 godo4.2.1 stable
Issue description
I want to edit label text in editor and add %s in it to use stringformat.
However, it didn't work in programs.

Steps to reproduce
UI_datalevel.text = "%s cm" (edited in editor)

var UI_datalevel:Label
var base_datalevel:float = 10.2
...

print(UI_datalevel.text%str(base_datalevel).pad_decimals(1)) #data is ok
UI_datalevel.text = UI_datalevel.text%str(base_datalevel).pad_decimals(1) #wrong

Minimal reproduction project (MRP)
UI_datalevel.text = "%s cm" (edited in editor)

var UI_datalevel:Label
var base_datalevel:float = 10.2
...

print(UI_datalevel.text%str(base_datalevel).pad_decimals(1)) #data is ok
UI_datalevel.text = UI_datalevel.text%str(base_datalevel).pad_decimals(1) #wrong

You are calling this method multiple times and you don't restore the text to the format string, this means it won't have any %s in it when you run it the second time
You need to make sure the input is correct
In the future please ask support questions in the forums, this is for bug reporting and please check that you are seeing a bug and not user error


Add method to ping store sessions; verify profile existence when opening a session

Fixes #163
For Postgres, this also ensures that a profile cannot be removed while there is an active transaction against it.
Includes a fix for the persistent test failure copying a Store instance on Windows.

#178 should fix the test failure on Windows and it might be best to merge that PR first.


API Compliance || Discrepancies Between Hearing API Spec and POJOs

Description:
There are discrepancies observed between Hearing APIs and its documented specification.
Details:
Hearing POJO:

hearingId field present in POJO but not documented in the API spec

Expected Behavior:
The Hearing service API responses should accurately reflect the fields and data types as specified in the API documentation.
Actual Behavior:

Hearing POJO:

hearingId field is present in the response but not documented in the API spec.

Proposed Solution:

Update the Hearing service API specification to include all fields consistently returned in the API responses (hearingId).

Additional Information:
API Specification

https://github.com/pucardotorg/dristi/pull/784
@varunreddy-egov  please verify this pr


Groovy issues with Strings in parentheses

What's changed?

What's your motivation?
Resolve Groovy parser issues affecting Gradle projects ;
some of the tests here fare worse on Groovy 2.5.
Anything in particular you'd like reviewers to focus on?

Anyone you would like to review specifically?

Have you considered any alternatives or workarounds?

Any additional context

Follows https://github.com/openrewrite/rewrite/pull/4430

I'd like to get this smaller increment in already, as this fixes things for Gradle 7+, before continuing to explore a fix for older gradle versions too. Then we can already do a patch release to get the first fixes out.

Merging already for the fix to LiteralTest.stringLiteralInParentheses() on Groovy 3+.


Please checkout other repos in my profile

Some repos are also taking part in hacktoberfest. If you want to contribute, please do it.

Hello @SanthoshS20 ;
can I add leetcode ProblemID_43 (multiply string) in python language, please assign this to me.

@Mayankjha997 Sure. Before contributing kindly check 2 things,

The format which i have used for a solution (problem link, description, time complexity and solution). Please follow it.
Kindly check whether the problem you are working is already exist or not in the specific language.


Refactor line chart for aggregation

Refactoring the line chart operator based on template on bar chart (link to PR: https://github.com/Texera/texera/pull/1384)
Demo
Data used for demo:

1. If given the below parameters (only name column and no data column):

Result looks like this (the occurrences of each name label is returned):

2. If a data column is added:

Result sums the given data column over each name label:

If multiple data columns is provided:

Result does the same thing, except on multiple columns:

Chart style
If "spline" is chosen, the line chart will use curve to connect data points.

The result for multiple data columns for spline chart style:

Looks good now, should be able to merge.


Include README files for the .NET Templates

It wouldn't hurt to include a README file with the templates, clarifying that the provided certificates are for testing purposes.

Originally posted by @pepone in https://github.com/icerpc/icerpc-csharp/pull/3955#pullrequestreview-1961299352

Closed by #3967


How to trigger a HomeKit Event with a physical button connected to the raspberry?

hello.
i can control my nightstand light via HomeKit and a physical button connected to my raspberry.
but when i press the button (toggles GPIO status) it wont change the status in HomeKit.
the button simply executes a python script that directly controls the GPIO state. i want to add a command to this script to change the status in HomeKit too.

Try Characteristic.setValue()
https://github.com/KhaosT/HAP-NodeJS/blob/master/lib/Characteristic.js#L150

that looks complicated. I'll do my best to read me through all the comments.  do i need to execute the whole js-file ? I'm a total noob in js sorry :(

One "easy way" is to use node-red (preinstalled on jessie) and homebridge-mqtt.
https://github.com/cflurin/homebridge-mqtt.
If you don't know node-red, mqtt, you'll probably have to invest a couple of hours.
But as soon as you have installed and learned how to use node-red and mqtt you'll be able to do almost everything.

@mrcsmxms An example how to use the setValue() call. I have a impulse type of button which I set back to "off" state after a timer has expired. Hope this helps to clarify how to use the setValue() call on an on/off characteristic.
https://github.com/exsilium/homebridge-xbee/blob/master/index.js#L60

Hi I would like to implement accessory light so that switch status is changed to Homekit when a switch is manually pressed.
A solution could be adaptable as for the garage sensor, in input on the gpio of raspberry with wirinpi.
Someone has solutions to create this accessory?
thank you

@marcgrc Maybe I'm missing a bit on what you would like to achieve but I think reading back the switch state depends more on your specific actuator, how it is wired or how it reports back a state.
For example, if you are using a RPi and the switch is wired physically to your board, you can just detect the pin change at the GPIO and setValue() of the switch based on that change.
Another example, when you are using some more sophisticated switch like a ZigBee enabled one - they tend to send the state change information via a 0x0a Report attributes cmd frame that you would need to read back via serial and similarly set the value of the switch based on the frame received.
Altough both examples are very different when it comes to physically interacting with the switch, from HomeKit point of view they both are based on @snowdd1 answer to use Characteristic.setValue() to set the state to whatever the physical device tends to be.

Thank you for the reply.
I want to give input to the lamp in the raspberry when I push the wall switch by intercepting the electrical wires that, before coming to the relays, pass from the acs712 module which will return the input lamp to the lamp in the raspberry.
I do not know how to upgrade
The light accessory to make it change was all homekit.
Could you send me a script that I clen in my light accessory ??
I would be grateful to you

Hello everyone,
This is what I'm trying to do. Bu there is no information about what margrc try to do.
Can you help us?

I continue searches. If anyone find a solution. Please show us a way to solution.
I hope  someone finds