More clear install instrictions? Package broken?

Running VisualStudio 2013, I created an "Empty Solution". On the solution node I call the "Manage nuget packages" and try to install the "Zurb Foundation for Apps Scaffolding". It fails immediately because "not compatible with any project in the solution".
Ok, I go ahead and add an empty ASP.NET Project to my solution and start the nuget installation again.  Great!
I can open the index.html in a browser from here. Ok.
But the .net side of the project seems incomplete? The Global.asax is missing it's codebehind file and the referenced class inherits="zurb_app.WebApiApplication" is not there?

Ack! I can't believe how this was missed! Many apologies. I also need to get the base ZFA library updated, so I'll work on getting this updated soon.

Hey there,
I'm having the same issue.  Any updates on this?

I was going over the code and my documentation and I think there's a step missing in the README here that was embedded in the NuGet package. Please try these steps and see if it gets you up and running. I'll make sure to update the documentation here if it works:
Update .Net Packages
Once this (being running the npm/bower install and gulp build) is complete, you'll need to update the packages library (to prevent an odd OWIN mismatch). Open the Package Manager Console and enter the following command:
Update-Package
Configure and Update the Database
Next, update your Web.config file and set the connection string to target your database. We will create and run the initial database migration sine leaving an existing migration in the NuGet package will not work. Enter the following commands at the Package Manager Console:
Enable-Migrations Add-Migration CreateInitialTables Update-Database
From here you should be able to build and run the app.
Service Configuration
After the first time you run the app, make note of the base Url of the app. You'll need to update the client/assets/js/factories.js file on line 4 to set the serviceBase variable properly. Make sure to include the trailing slash at the end of the Url.

Isn't that README for your authentication version of the scaffolding?  Does it still apply to this version of the scaffolding?
I did try running Update-Package and nothing need to be updated. This is error I'm getting:

For me to get past this error I have to remove the inherit attribute from the Global.asax.  The at least the page will load...kinda.
It loads the header but none of the views.  When I inspect the console I can see there's an issue with the UI Router:

I spent all day yesterday trying to remedy this but to no avail.  Any help you can provide would be great.  I've been trying to convince my dev team to use foundation for apps on the front end and they seems to be interested...until now.


GOED Broadband - Fall 2024 Provider Updates

Benefit
Updated broadband provider coverage areas including the technology of transmission and associated advertised upload and download speeds.
Acceptance Criteria
Updated broadband provider coverage areas reflected in the https://broadband.ugrc.utah.gov/
Notes
Trello Board
Risks
Provider data quality and necessary communication to resolve issues.
Issue Reference
refs #

Sprint 1

[ ] initiate fall broadband data gathering and preparation
[ ] process provider data
[ ] process FCC data update

duplicate of https://github.com/agrc/planning-queue/issues/454


Fix MU capacity to include 8

Issue : https://github.com/Azure/azure-cli/issues/10912
This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

#sign-off

@haroldrandom please help with this PR.


driver/swift: Fix go vet warning

Driver was passing connections by copying indirectly. Storing swift.Connection as pointer to fix the warnings.
Ref: #2030.
@RichardScothern PTAL

Current coverage is 50.88% (diff: 100%)

Merging #2031 into master will decrease coverage by 10.27%

@@             master      #2031   diff @@
==========================================
  Files           125        125
  Lines         11138      11138
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           6812       5668   -1144
- Misses         3443       4727   +1284
+ Partials        883        743    -140

Powered by Codecov. Last update 994d1a5...a994f35

LGTM


In ResetAdvertiseInterval(), replace assert() with VerifyOrExit().

Fixes #1287.

Codecov Report

Merging #1289 into master will increase coverage by 0.27%.

@@            Coverage Diff             @@
##           master    #1289      +/-   ##
==========================================
+ Coverage    69.6%   69.87%   +0.27%
==========================================
  Files         168      169       +1
  Lines       26491    26504      +13
  Branches     3319     3292      -27
==========================================
+ Hits        18438    18519      +81
+ Misses       6642     6576      -66
+ Partials     1411     1409       -2

Impacted Files
Coverage Δ

src/core/thread/mle_router.cpp
79.49% <100%> (+0.1%)
:white_check_mark:

third_party/mbedtls/repo/library/ecp_curves.c
90.16% <ø> (-3.06%)
:x:

src/ncp/ncp_base.cpp
37.89% <ø> (-0.61%)
:x:

examples/platforms/posix/radio.c
78.48% <ø> (-0.43%)
:x:

...d_party/mbedtls/repo/library/memory_buffer_alloc.c
60.25% <ø> (-0.39%)
:x:

third_party/mbedtls/repo/library/ssl_tls.c
54.34% <ø> (-0.04%)
:x:

src/core/thread/mle.cpp
80.32% <ø> (ø)
:white_check_mark:

examples/apps/ncp/main.c
100% <ø> (ø)

third_party/mbedtls/repo/library/bignum.c
51.09% <ø> (+0.27%)
:white_check_mark:

... and 10 more

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 a6b6751...4c46ec6. Read the comment docs.


Added a pod contributions leaderboard

Please, go through these steps before you submit a PR.

[ ] My Pod Leader knows I'm working on this Pull Request
[ ] I've explained what the Pull Request is adding.
[ ] I've explained why this is important.

Fixes #4. I created a leaderboard to rank members of the team by number of contributions.

I have the basic functionality done but I want to keep working on the look of the leaderboard.


Update KQL query format in tutorial.md

Improved formatting of KQL query for better readability and consistency

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

#sign-off

@YaelSchuster: I'm sorry - only the author of this article, @orspod, 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.


Upgrade to 1.7.6

Fixes #3.
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender.

There's a crash in some of the tests of latte. Not sure if it's the same in the upstream CI, it's all red anyway, see https://github.com/latte-int/latte/issues/38.

I can reproduce this locally when building from source.

Upgrading 4ti2 doesn't change anything here.
@mkoeppe any idea what might be the issue here?

@mkoeppe we are stuck here. Any chance we can discuss what could be the problem in 2024?

@conda-forge-admin, please rerender.


Add description column to personal access token

Preflight Checklist

[X] I could not find a solution in the existing issues, docs, nor discussions
[ ] I have joined the ZITADEL chat

Describe your problem
We can add multiple PERSONAL ACCESS TOKENS. However all of them are saved and displayed as ID. It is very hard to figure out which one is which in case we need to revoke revoke it.
Describe your ideal solution
Can you please add an description column on the page (allow user modify) to indicate the purpose for this access token. Since it is less important to see "CREATION DATE", you can probably replace that column with "Description".

Version
2.4
Environment
Self-hosted
Additional Context
No response

Thank you for sharing your idea.
If there is a significant demand from customers/community, we will carefully consider implementing the feature.
Currently, the issue will be added to our product backlog to collect feedback.
Meanwhile, if you're interested in implementing it yourself, we also welcome pull requests.


Add --permanent option to really delete objects from a versioned s3 bucket

Normally, when running wal-e delete on a versioned s3 bucket, s3 simply adds a "delete marker" over top of each deleted object. This is the intent of bucket versioning, but it is not helpful if backups need to be removed to save storage costs. This PR adds a --permanent flag to the delete command which, when invoked and used with a versioned s3 bucket, will permanently delete the most recent version of each s3 object instead of inserting a delete marker.

Is there any way to make this not-an-option? For example, does anyone not want permanence?

I'd be happy to refactor this PR so objects are always permanently deleted.
However, one caveat is although this code will work just fine on a non-versioned bucket, it does require the s3:ListBucketVersions permission; any users working with non-versioned buckets who don't already have the s3:ListBucketVersions in their policy may be surprised to find wal-e stops working. If that's not a roadblock, then it's simple to make this always-on behavior.

+1 +1 +1
:+1:

:+1: :+1:

Upon consideration, I think permanent should be the only option. The whole point of wal-e delete is to control costs and save space, so I think being overly polite with regard to deletion while versioning is overwrought. Can you streamline the patch to remove the option and make WAL-E handle both versioned and unversioned buckets.

Can anyone modify this patch to make permanent the default behavior and fall back gracefully if one uses an unversioned bucket? If so I'll commit it.

Verified this works with a versioned bucket; still working on getting a non-versioned bucket set up to test.

I know this issue is pretty stale at this point, but I've just experienced this exact issue. My S3 bucket storing my backups and WAL archives is only a few terabytes on disk, but the bucket size is hundreds of terabytes (and costing some serious $$) because of the versioning markers.
Luckily, finding this issue tipped me off as to what might be happening, but it would still be nice to have this feature (or a flag to use it) merged into master.

I'm applying the newly introduced needs-work label to this. That is, there is no problem with the feature in principal, but there's a lack of interest, testing, or changes to complete it. I also apply this label so I can find such closed pull requests easily for future study.


Arabic characters clipped in Chrome on MacOS

PDF files for reproducing the issue:
Characters-clipped.pdf
Characters-rendered-correctly.pdf
Configuration:

Web browser and its version: Chrome 106.0.5249.61
Operating system and its version: MacOS Monterey 12.5.1
PDF.js version: At the moment of writing this, it reports "PDF 110dd61fd57444010b1ab5ff38782f0f [1.4 pdfeTeX-1.21a / TeX] (PDF.js: 3.0.246 [7dc16c237])" in the Developer console of Chrome and the latest release on the pdf.js download page is 2.16.105.
Is a browser extension: No

Steps to reproduce the problem:

Go to https://mozilla.github.io/pdf.js/legacy/web/viewer.html in the latest Chrome (106.0.5249.61) on MacOS (Monterey)
Open the attached pdf (Characters-clipped.pdf)

What is the expected behavior?
All characters are shown without being clipped.

This screenshot is produced from using Characters-rendered-correctly.pdf
What went wrong?
Characters are clipped both horizontally and vertically. A few of the examples of this is circled in red in the following screenshot.

A few notes:
The latest Chrome on the latest MacOS provided by BrowserStack is used to do the test.
The font is different in the version of the PDF that is working fine from the version that has the errors, so it is maybe related to this.
The issue is seen both on the legacy and the "modern" version.
The issue looks similar to what is reported in
https://bugzilla.mozilla.org/show_bug.cgi?id=1756855
and
https://github.com/mozilla/pdf.js/issues/14941
so it could have something to do with variable weight fonts.

Duplicate of #14941


Add zoneout regularization to recurrent neural networks

Implemented zoneout regularization for recurrent neural networks as suggested by:

Zoneout: Regularizing RNNs by Randomly Preserving Hidden Activations
https://twitter.com/udibr/status/740609683090739200

@gw0 cool addition and something I would use. Needs some error checking and unit tests and it is currently conflicting. Are you still working on this or should I pull your changes and make some tweaks?
Cheers

@bstriner Oh, it is conflicting again... Feel free to pull changes and make tweaks.

Closing outdated PR. If you still care about the content of the PR, please submit a new PR to master, updated for the Keras 2.0 API.

Zoneout would be helpful


Improve and autoexecute Generate Assembly Catalog

Automatically generate Assembly Catalog at startup.
Currently, it's not possible because the generation is too long because of the Openedge Implementation.
I made a new implementation in C# :
https://github.com/clement-brodu/PCTTools
Improvements:

faster (for my situation, 20s instead of 8min)
better with Generics Types
provide protected members
provide fields
provide enum values as fields
provide constructors
provide event handler types and invoke signatures
allow to scan only one type or one assembly
catalog file without default values

The catalog format has some differences with current AssemblyCatalog Task.

I'll try to integrate that !

First version merged in pre-release.


Dynamically detect terminal size

The simplest solution is to rely on the LINES and COLUMNS environment variables. (Update: these are bash variables and may not be available as env variables unless explicitly exported...)

In bash, these are set if shopt -s checkwinsize is set. Apparently this is enabled by default.
In zsh, apparently these are set automatically

Alternatively (more advanced), the Lantern project (#633) shows how this can be done with ANSI escape sequences.
Example implementation to get the terminal size:
import java.io.IOException;

public class WinSize {
    /*
      /bin/stty -echo; /bin/stty -icanon; /bin/stty min 1; java WinSize; /bin/stty echo; /bin/stty icanon;
     */
    public static void main(String... args) throws IOException {
        String[] signals = new String[] {
                "\u001b[s",            // save cursor position
                "\u001b[5000;5000H",   // move to col 5000 row 5000
                "\u001b[6n",           // request cursor position
                "\u001b[u",            // restore cursor position
        };
        for (String s : signals) {
            System.out.print(s);
        }
        int read = -1;
        StringBuilder sb = new StringBuilder();
        byte[] buff = new byte[1];
        while ((read = System.in.read(buff, 0, 1)) != -1) {
            sb.append((char) buff[0]);
            //System.err.printf("Read %s chars, buf size=%s%n", read, sb.length());
            if ('R' == buff[0]) {
                break;
            }
        }
        String size = sb.toString();
        int rows = Integer.parseInt(size.substring(size.indexOf("\u001b[") + 2, size.indexOf(';')));
        int cols = Integer.parseInt(size.substring(size.indexOf(';') + 1, size.indexOf('R')));
        System.err.printf("rows = %s, cols = %s%n", rows, cols);
    }
}

API to enable this:

Command: usageHelpAutoWidth: boolean
UsageMessageSpec: autoWidth: boolean
If system property "picocli.usage.width" has value AUTO or TERM or TERMINAL, then autoWidth becomes true
CommandLine: get/setUsageHelpAutoWidth : boolean

FWIW I've done this with https://github.com/yschimke/oksocial-output/blob/master/src/main/kotlin/com/baulsupp/oksocial/output/ConsoleHandler.kt#L179
I'd love to switch to whatever you come up with particularly if it doesn't require launching commands etc.

Thanks for the link, just saw that. (Wasn't aware of the -f vs -F difference for MacOS, that's a good catch!)
I am working on this right now, once I get it to work I'm planning to release 4.0.0-beta-2.
My current approach is similar to what you did in ConsoleHandler, but still experimenting with various approaches to find something that also works in Cygwin. What the Lantern project is doing with the ANSI escape sequences may work, but also depends on executing (a number of) commands: bin/stty -echo; /bin/stty -icanon; /bin/stty min 1; for setup, then /bin/stty echo; /bin/stty icanon; for teardown...

FYI, here are two other ways to get the console width:

Powershell: powershell -command (Get-Host).ui.rawui.windowsize.width
MingwXterm: tput cols

@charphi picocli 4.0.0-beta-2 should work (be able to detect the terminal width) with Powershell and MINGW. Is this not working correctly?

I've not tested it yet.
My comment was just alternatives in case of problem.

I see! That’s good. :-)
I tested MINGW so that should be fine.
I think that the command for Windows will work from Powershell too but I didn’t test.

What a coincidence that I found this after I was looking for a way to detect the console width. Can I find the console width with Java? mentions some of the same techniques mentioned here. fusesource/jansi#24 says to use jline, although I didn't understand why if jline3 used Jansi then why I couldn't use Jansi myself to find the console width. (I'm using Jansi already.)
But it sounds like you've implemented something in this ticket to detect the console width. So how can I access the value picocli detected so that I can use it in my application?

Oh, I see. 😭  You hid all that useful code deep in some private method. I'll open a ticket.


Include generateNeverlink in format-deps (#298)

This fixes #298.
New behavior does not drop generateNeverlink during formatting.

I'll merge, but if you have time to add a test, I would really appreciate it.
(this is exercised, I think by a format command that the repo runs in CI, but I don't think there are any generateNeverlink in there.)


Change the XfaLayerBuilder.render method to be asynchronous

This is consistent with the render methods of the other layers, and reduces overall indentation in the method.
Furthermore, don't "swallow" errors since the PDFPageView._renderXfaLayer method is already able to deal with that.

/botio integrationtest


Remove "control-block" class as it is no longer of use and did not work well, even in older browsers.

Completed.


Wrong calculator function

All functions just return addition of the number instead of their respective operations

I would like to do this.

Hi! Can I take this?

Sure :)

Oh! I just realised that this was already fixed in https://github.com/IEEE-VIT/Calci-Android/pull/10. This issue can be closed.

Hi, Please assign me this issue if it still exists?


Errors using --args-json in Windows Powershell

Problem
I'm unable to find a way to pass arguments to a transaction using --args-json in Powershell/Windows Terminal.
Steps to Reproduce
tx.cdc:
transaction(amount: UFix64, address: Address) {
        prepare(signer: AuthAccount){
                log(amount)
                log(address)
        }
}

Using CLI 0.18.0 in Powershell on Windows:
flow transactions send tx.cdc --args-json "[{'type':'UFix64', 'value': '1.0'}, {'type': 'Address', 'value': '0x179b6b1cb6755e31'}]"
This format produces the error:
Command Error: invalid character '\'' looking for beginning of object key string - referring to the single quote around type. Changing to use single quotes around the JSON string and double quotes around the object keys changes the error message to Command Error: invalid character 't' looking for beginning of object key string.
I've tried every way I can think of to produce the string - using all double quotes, using escaped quote s(\") inside the string, etc. They all produce some kind of error.
I am able to run a transaction with the standard Windows command line by using escaped double quotes:
flow transactions send tx.cdc --args-json "[{\"type\":\"UFix64\", \"value\": \"1.0\"}, {\"type\": \"Address\", \"value\": \"0x179b6b1cb6755e31\"}]"
Acceptance Criteria
There should be some way of using --args-json in Powershell/Windows Terminal. If there's a format I'm missing that works, that would be great. Another option would be to support passing in a .json file with the arguments.
Context
Since I can run this in cmd.exe it's not blocking anything for me, but I spent a long time trying to get this figured out. Powershell/Terminal is widely used by Windows developers and would be good to support. If this is not going to get fixed, documentation indicating that it is unsupported would be helpful.

I found something that works in Powershell:
flow transactions send tx.cdc --args-json '"[{\"type\":\"UFix64\", \"value\": \"1.0\"}, {\"type\": \"Address\", \"value\": \"0x179b6b1cb6755e31\"}]"'
I'm not totally sure why this is needed, but I think this works because "string" in PS just results in string and '"string"' produces "string".  So the wrapping single quotes get the value to turn up in double quotes, and the escaped double quotes inside keep from breaking the string.


Expose display as an API?

Hi, I love grid-styled. Its really great. Thank you.
I wonder whether you would consider to expose display as an API? It would e.g. be nice to be able to hide boxes at certain breakpoints.
<Box display={["none", "block"]}>

As an example please consider the following: I would like to display some thumbnails as a teaser, 4 for large screens, 2 for medium screens, 1 for small screens.
In a react component I have:
  renderThumbs = thumbs => {
    let gallery = []
    const start = 1
    const end = 4

    for (let i = start; i <= end; i++) {
      gallery.push(
        <MyBox
          width={[1, 1 / 2, 1 / 4]}
          key={i}
          px={1}
          display={[`${i < 2 ? "block" : "none"}`, `${i < 3 ? "block" : "none"}`, "block"]}
        >
          <Img
            data-sizes="360px"
            src={thumbs[i]["0360"]}
            className="lazyload blur-up"
            alt={"Thumb " + i}
          />
        </MyBox>
      )
    }
    return gallery
  }

where <MyBox /> is extending <Box />:
import styled from "styled-components"
import { Box } from "grid-styled"

const MyBox = styled(Box).attrs({
  display: props => props.display || "block"
})`
  display: ${props => props.display[0]};
  @media (min-width: ${props => props.theme.breakpoints[0]}em) {
    display: ${props => props.display[1]};
  }
  @media (min-width: ${props => props.theme.breakpoints[1]}em) {
    display: ${props => props.display[2]};
  }
`

export default MyBox

I think this is outside of the scope of this library and goes against responsive web design principles a bit. You might be interested in this component though: https://github.com/jxnblk/hidden-styled


Declare AUDIO_OUT once and in audio_out.h

Silences redefinition errors on some compilers
GCC 4.5.3 for some reason is more loud than other versions.
Build log

That works!


(Critical) Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code

Effected repos:
https://github.com/US-EPA-CAMD/easey-campd-ui/security/dependabot
https://github.com/US-EPA-CAMD/easey-emissions-api/security/dependabot
https://github.com/US-EPA-CAMD/easey-facilities-api/security/dependabot
https://github.com/US-EPA-CAMD/easey-account-api/security/dependabot
https://github.com/US-EPA-CAMD/easey-mdm-api/security/dependabot
https://github.com/US-EPA-CAMD/easey-streaming-services/security/dependabot
https://github.com/US-EPA-CAMD/easey-camd-services/security/dependabot
https://github.com/US-EPA-CAMD/easey-auth-api/security/dependabot

@ergjustin plz review these
https://github.com/US-EPA-CAMD/easey-campd-ui/pull/614
https://github.com/US-EPA-CAMD/easey-emissions-api/pull/430
https://github.com/US-EPA-CAMD/easey-facilities-api/pull/153
https://github.com/US-EPA-CAMD/easey-account-api/pull/145
https://github.com/US-EPA-CAMD/easey-mdm-api/pull/172
https://github.com/US-EPA-CAMD/easey-streaming-services/pull/93
https://github.com/US-EPA-CAMD/easey-camd-services/pull/197
https://github.com/US-EPA-CAMD/easey-auth-api/pull/160

@shahbazkhan1999
I don’t believe that it’s necessary to install "@babel/traverse": "^7.23.2" package to fix the Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code. It was already fixed 4 days before.

easey-emissions-api:- https://github.com/US-EPA-CAMD/easey-emissions-api/security/dependabot/29
Image
easey-facilities-api:- https://github.com/US-EPA-CAMD/easey-facilities-api/security/dependabot/25
Image
easey-account-api:-  https://github.com/US-EPA-CAMD/easey-account-api/security/dependabot/28
Image
easey-mdm-api: https://github.com/US-EPA-CAMD/easey-mdm-api/security/dependabot/31
Image
easey-streaming-services:- https://github.com/US-EPA-CAMD/easey-streaming-services/security/dependabot/19
Image
easey-auth-api : -  https://github.com/US-EPA-CAMD/easey-auth-api/security/dependabot/33
Image

Can you please recheck this issue?

@shahbazkhan1999
Revert "Babel vulnerable" changes that you did.
There is no need for code change.

Already issue solve. so, code riveted


no-redundant-story-name case insensitivity

Is your feature request related to a problem? Please describe.
Warn/error when storyName is a case-insensitive variant of the name generated by the export name:
e.g. WithText.storyName = 'With Text'; will currently warn/error but WithText.storyName = 'with text'; will not
Describe the solution you'd like
The ability to configure the no-redundant-story-name rule to use/ignore case when determining in the name is redundant
Describe alternatives you've considered
Would also be open to this being the default behaviour if that's easier.
Additional context
I am working on a codebase where we used the storybook provided codemon to migrate our old storiesOf stories to CSF. Due to most of our old story names being all in lower-case, we now have a lot of instances where PascalCase.storyName = 'lower case'. Engineers are then copying this format and spreading the issue. So while I can fix the existing set, I'd like a way to catch any future instances

Hey @benedfit thanks for opening this issue! I am not sure how valid this request is, given that there is a difference between the scenarios which you described:

WithText.storyName = 'With Text';
WithText.storyName = 'with text';

They will yield different results in the sidebar. People might actually want to specify names to be lower case, whilst the story name is upper case.

@yannbf I agree that there would be scenarios where folks want to specify lower case, so that's why it would be great for it to be an optional settings, and for it to work as it currently does by default


moved multiagent environment to a new folder

resolves #337
The new multiagent environments enforced a ray dependency, which needs to imported every time an environment is used and takes a while to import.

Pull Request Test Coverage Report for Build 2352

48 of 83 (57.83%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 86.563%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

flow/multiagent_envs/loop/loop_accel.py
21
23
91.3%

flow/multiagent_envs/loop/wave_attenuation.py
16
49
32.65%

Totals

Change from base Build 2346:
0.03%

Covered Lines:
7041

Relevant Lines:
8134

💛  - Coveralls

Update: this also ensures that you don't need to install ray if u want to run the single agent exps (e.g. if u are using rllab instead)


cluster create/import existing cancel button not working (uncaught promise)

on the pages manager/provisioning.cattle.io.cluster Cluster Management create/import existing, uncaught promise occurs when clicking the cancel button
vue-router.esm.js:1958 Uncaught (in promise) NavigationDuplicated: Avoided redundant navigation to current location: "/c/c-m-b4ddf01c/manager/provisioning.cattle.io.cluster/create".
    at $t (https://releases.rancher.com/dashboard/latest/commons/app.48b70279e3d5c2318c97.js:2:66970)
    at e.Ut.confirmTransition (https://releases.rancher.com/dashboard/latest/commons/app.48b70279e3d5c2318c97.js:2:69936)
    at e.Ut.transitionTo (https://releases.rancher.com/dashboard/latest/commons/app.48b70279e3d5c2318c97.js:2:69265)
    at e.replace (https://releases.rancher.com/dashboard/latest/commons/app.48b70279e3d5c2318c97.js:2:72629)
    at https://releases.rancher.com/dashboard/latest/commons/app.48b70279e3d5c2318c97.js:2:77601
    at new Promise (<anonymous>)
    at Qt.replace (https://releases.rancher.com/dashboard/latest/commons/app.48b70279e3d5c2318c97.js:2:77564)
    at f.emitOrRoute (https://releases.rancher.com/dashboard/latest/app.b6ea214e6bfe6c17815a.js:2:440440)
    at f.confirmCancel (https://releases.rancher.com/dashboard/latest/app.b6ea214e6bfe6c17815a.js:2:440156)
    at Qt (https://releases.rancher.com/dashboard/latest/commons/app.48b70279e3d5c2318c97.js:2:173549)

  | $t | @ | vue-router.esm.js:1958
-- | -- | -- | --
  | Ut.confirmTransition | @ | vue-router.esm.js:1928
  | Ut.transitionTo | @ | vue-router.esm.js:2152
  | e.replace | @ | vue-router.esm.js:2531
  | (anonymous) | @ | vue-router.esm.js:2963
  | Qt.replace | @ | vue-router.esm.js:2962
  | emitOrRoute | @ | CruResource.vue:174
  | confirmCancel | @ | CruResource.vue:160
  | Qt | @ | vue.runtime.esm.js:1854
  | n | @ | vue.runtime.esm.js:2179
  | Qt | @ | vue.runtime.esm.js:1854
  | t.$emit | @ | vue.runtime.esm.js:3888
  | click | @ | CruResourceFooter.vue?82b2:1
  | Qt | @ | vue.runtime.esm.js:1854
  | n | @ | vue.runtime.esm.js:2179
  | c._wrapper | @ | vue.runtime.esm.js:6917

on master-head (909237a)

I can't reproduce this bug; the cancel behavior appears to be fixed as of this pr: https://github.com/rancher/dashboard/pull/3102

on master head (62aef76):
cancel buttons appear to be working normally on the create page

also tested cancel button on each rke2 provisioner page -- pass

also tested cancel button on rke2 provision page for cloud credentials -- pass


The right-click options  are very slow.

What feature or improvement do you think would benefit Files?
The right-click options always delay when i right-click any file/folder. If this was faster, it would be very nice... My previous issues were like an unnecessary report..... And i am sorry for that.
Requirements

This proposal will accomplish X
This proposal will accomplish Y
This proposal will accomplish Z

Files Version
<IP_ADDRESS>
Windows Version
20H2
Comments
No response

Sorry but this is the SDK problem.
Probably asking WinAppSdk repo team would be good.

@pranavinsight thank you for your feedback, improving the performance when loading shell extensions is on the ToDo list (#11112). In the meantime, you can work around this by enabling the option to move them to a sub menu.

Oh, okay! So, you can fix that in an update maybe? That's nice! And also I forgot to mention that it takes alot of memory from my PC. In short words, this is too hot for my potato windows 10🤣🤣🤣

Thank You @yaira2 ! I can try that maybe...

Oh... and also, for people using installer version of Files should get like some kinda alert message or an updating executable.... I see you are releasing a new version of files rn.
I don't want to be having an outdated version like that!

Maybe i should create a new issue about it?

@yaira2 and @0x5bfa , it's in your hands to decide and solve the issue. Or atleast someone solve it(i am not being rude). And thank you for supporting me for installation of Files!

And for a surprise, I forked you!!!!!!!! 🎉🎉🎉🎉

And i am creating a new website.

Oh... and also, for people using installer version of Files should get like some kinda alert message or an updating executable.... I see you are releasing a new version of files rn. I don't want to be having an outdated version like that!

The sideload version of Files has built-in auto update.

Where is it?

The sideload version of Files has built-in auto update.

Where is that 'sideload' version?

Put it here. I need it. It's essential!

All versions have auto update, the installer is also the sideloaded version.

Oh! Okay, how to update then? This file manager is gonna be intresting! 😄

It will do it in the background and/or show a install button next to settings if there is an update

Okay...

That's nice!

Btw, check my new website! MatrixType Second Generation(v.2.0.0

Btw, check my new website MatrixType 2.0

Btw, check my new website! MatrixType Second Generation(v.2.0.0

Uhh, why is my link going crazy???

In the worst case scenario like this, i have another repository! MatrixType 2.0

Btw, check my new website! MatrixType Second Generation(v.2.0.0

Noooo! This is also NOT working! Seriously GitHub? I guess it's just not the correct time to discuss another topic.
Another website link:
https:://pranavinsight.github.io/fivestarcoffeemakers2.0/
This is having a specialised theme, not to mention that it has an unavoidable bug that we will later fix in an update.

Wait a minute, now i realized that only the MS Store version has the updating feature and they mentioned that only in that version you can recieve updates...
Can i believe you?

No where does it say Files only has auto update on the store. All version have auto update.

Please stop post random website links here.

Oh! I am sorry. Just for you to check one of my repos. I am sorry if it bothers you 😇

No where does it say Files only has auto update on the store. All version have auto update.

Ok, then when another update is coming? I am going to test that feature!

Is that 3.0.2 or 3.0.1?

<IP_ADDRESS> Is out now, It should have updated if you check Files settings > About, but if not you can try using the installer https://files.community/download as sometimes Windows causes issues with built in updater.

Wait. I already have it
This? I installed that  when i was testing it, ( #15295)
Files Version: <IP_ADDRESS>


Delete zero element on destroy of all tethers

Related to this issue https://github.com/HubSpot/drop/issues/114
I realize that it's pretty edge case, but ideally there should be a way to totally clean up the page if needed.

Good idea. I've reimplemented this as 29ce742facc997149ebdfbf1c76bd8d62c88aae0.


ROPC Blazor

Description
See #33504
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/components/data-binding?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/data-binding.md
Document ID
3f912dfc-5ba5-6c6c-ba93-1ae78508a5cc
Article author
@guardrex

Moved to #33523 to place correct metadata. We don't have an easy cut-'n-paste way to handle metadata any longer.


AttributeError: module 'lib' has no attribute 'X509_CHECK_FLAG_NEVER_CHECK_SUBJECT'

Problem Description
This error is reported when I use mitmWeb or mitmproxy to start and use the proxy (I have installed and trusted the mitm.it certificate)
Steps to reproduce the behavior:
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/mitmproxy/proxy/server.py", line 121, in handle
root_layer()
File "/usr/local/lib/python3.6/site-packages/mitmproxy/proxy/modes/http_proxy.py", line 9, in call
layer()
File "/usr/local/lib/python3.6/site-packages/mitmproxy/proxy/protocol/tls.py", line 285, in call
layer()
File "/usr/local/lib/python3.6/site-packages/mitmproxy/proxy/protocol/http1.py", line 83, in call
layer()
File "/usr/local/lib/python3.6/site-packages/mitmproxy/proxy/protocol/http.py", line 190, in call
if not self._process_flow(flow):
File "/usr/local/lib/python3.6/site-packages/mitmproxy/proxy/protocol/http.py", line 262, in _process_flow
return self.handle_regular_connect(f)
File "/usr/local/lib/python3.6/site-packages/mitmproxy/proxy/protocol/http.py", line 208, in handle_regular_connect
layer()
File "/usr/local/lib/python3.6/site-packages/mitmproxy/proxy/protocol/tls.py", line 278, in call
self._establish_tls_with_client_and_server()
File "/usr/local/lib/python3.6/site-packages/mitmproxy/proxy/protocol/tls.py", line 358, in _establish_tls_with_client_and_server
self._establish_tls_with_server()
File "/usr/local/lib/python3.6/site-packages/mitmproxy/proxy/protocol/tls.py", line 448, in _establish_tls_with_server
**args
File "/usr/local/lib/python3.6/site-packages/mitmproxy/connections.py", line 292, in establish_tls
self.convert_to_tls(cert=client_cert, sni=sni, **kwargs)
File "/usr/local/lib/python3.6/site-packages/mitmproxy/net/tcp.py", line 386, in convert_to_tls
**sslctx_kwargs
File "/usr/local/lib/python3.6/site-packages/mitmproxy/net/tls.py", line 290, in create_client_context
SSL._lib.X509_CHECK_FLAG_NO_PARTIAL_WILDCARDS | SSL._lib.X509_CHECK_FLAG_NEVER_CHECK_SUBJECT
AttributeError: module 'lib' has no attribute 'X509_CHECK_FLAG_NEVER_CHECK_SUBJECT'
mitmproxy has crashed!
Please lodge a bug report at: https://github.com/mitmproxy/mitmproxy
System Information
device:NanoPi_NEO_Plus2 (http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Plus2)
Mitmproxy: 5.1.1
Python:    3.6.1
OpenSSL:   OpenSSL 1.0.2g  1 Mar 2016
Platform:  Linux-4.11.2-aarch64-with-debian-kali-rolling

How did you install mitmproxy? This looks like your version of cryptography is outdated.

How did you install mitmproxy? This looks like your version of cryptography is outdated.

"pip3 install mitmproxy"  How should I solve this problem?

According to https://github.com/pyca/cryptography/pull/4492, the problem is your outdated OpenSSL version. So you'd need to update that. I'm closing this here as it's not really a mitmproxy bug. :)

Hello, I update OpenSSL to OpenSSL 1.1.1g  21 Apr 2020 (Library: OpenSSL 1.1.1d  10 Sep 2019)
But the same error occurs
Can you help me?

I assume your output of mitmproxy --version still lists your old OpenSSL version? You need to have cryptography installed with the proper version.


Contents in main view panel flicker/vanish on button mouseover

System information:

Ubuntu 18.04.1 LTS
DBeaver version <IP_ADDRESS>901062110
openjdk version "10.0.2" 2018-07-17
OpenJDK Runtime Environment (build 10.0.2+13-Ubuntu-1ubuntu<IP_ADDRESS>)
OpenJDK 64-Bit Server VM (build 10.0.2+13-Ubuntu-1ubuntu<IP_ADDRESS>, mixed mode)
KDE plasmashell 5.12.7 with OpenGL 2.0 set as compositor (same problem with XRender, though)

Connection specification:

psql (PostgreSQL) 10.6 (Ubuntu 10.6-0ubuntu<IP_ADDRESS>)
Driver name: PostgreSQL
Do you use tunnels or proxies (SSH, SOCKS, etc)?  No, the database runs locally (i.e. from localhost)

Describe the problem you're observing:
The main view panel which displays properties of the database, data tables, the SQL editor, etc. goes completely blank when hovering the mouse over a clickable control (buttons, tabs) within the panel. It comes back into view when hovering over a button again. Effectively, the view panel is thus flickering horribly as you move your mouse across the screen. This is very annoying and has persisted for the past 2 or 3 sub-versions.
Steps to reproduce, if exist:

Open DBeaver
Double-click on database
Move mouse across screen
Hover mouse over a button in the main view panel

Include any warning/errors/backtraces from the logs
https://gist.github.com/carbeck/ed97949cde2e693c0a34eee1c5fb96ca

I have had the same bug.
To make BÉPO keyboard layout works properly, I switched from ibus to xim, but this have made DBeaver tabs blinking (especially SQL scripts).
To fix this, I needed to do two things (need to restart the computer afterward):

export GTK_IM_MODULE=ibus as mentionned above, but also
im-config to rollback from xim to ibus

My configuration:

DBeaver Version <IP_ADDRESS>305211610 (but same blinking bug with xim on previous version 22.3.3)
Ubuntu 22.04.2 LTS
GNOME 42.5
X11


Tab bar and navbar in popup

Is it possible to have a tab bar and/or navbar in a popup?

Yes, as in any other View:
.popup
  .view
     .pages
       .page
         ...etc

Just follow Layout types documentation http://www.idangero.us/framework7/docs/navbar-toolbar-layouts.html
By the way, as you may see in any demo app/kitchen sink, popups have navbar, look at least there

As soon as is add a class .page into my popup it is no longer possible to use a back link from the site with the popup when i came back from a following site.


 We should be using pytest

Agreed, never done that though. Im gonna read up on it.

I'll have to read up on pytest as well.


Can we use httpd on the base stack?

Summary
The HTTPD dependency that this buildpack installs appears to be unable to run on the base stack. Can we complete an exploration to determine why we cannot run this on base and if it might be reasonable for us to get this to run on base?

@ryanmoran Adding libexpat1 to mixins for the base stack seems to work. I didn't see that any other package was required to get the httpd integration test to work (unless I'm missing something). I created this draft pull-request for the stacks repo. And here's a draft for the base-builder.
If we want to add support for the php-httpd use case, we'll need to add the following: libargon2-0, libcurl4, libedit2, libgd3, libmagickwand-6.q16-3, libonig4, libxml2
Should I update the stacks PR to include these as well?

No need for the extra dependencies to support php-httpd since the PHP buildpack isn't supported on Base.

libexpat1 is added to both build and run for symmetry.
The difference between the sizes of the build and run images after including libexpat1 is negligible:

w/ libexpat1
w/o libexpat1

Run
88.996 MB
88.595 MB

Build
326.075 MB
326.101 MB

The PR for the base builder: https://github.com/paketo-buildpacks/base-builder/pull/485/files

Closing. This was resolved when the PR to base-builder was merged.


SP-3203 - Backport of PDI-15059 - Spoon startup: Multiple and different slf4j-log4j jar files in the class path

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f plugins/kettle-json-plugin/build.xml clean-all resolve jacoco && ant -f plugins/kettle-json-plugin/build.xml checkstyle publish-local
ant -Dtestreports.dir=bin/reports/unit-test -f plugins/pdi-pur-plugin/build.xml clean-all resolve jacoco && ant -f plugins/pdi-pur-plugin/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  assembly/ivy.xml
  plugins/kettle-json-plugin/ivy.xml
  plugins/pdi-pur-plugin/ivy.xml

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.ui.repository.pur.repositoryexplorer.model.UISecurityRole

Branch Change:  + 1.79%
Complexity Change:  + 1.54%
Instruction Change:  + .16%
Line Change:  + .58%


Bug in ClientEnvironment

I get this when importing BlokusEnvironment:
File "/home/mcaleste/Documents/Research/Multiagent/TicTacToe/env/lib/python3.5/site-packages/colosseumrl/init.py", line 4, in
from .ClientEnvironment import ClientEnvironment
File "/home/mcaleste/Documents/Research/Multiagent/TicTacToe/env/lib/python3.5/site-packages/colosseumrl/ClientEnvironment.py", line 46
self.player_df: Dataframe = dataframe
^
SyntaxError: invalid syntax
MWE:
from colosseumrl.envs.blokus.BlokusEnvironment import BlokusEnvironment

Oh I need python 3.6. We should update the description to say you need 3.6 and up instead of 3.5 and up

Done. It was correct on the docs but not the README for some reason.


[Migrator] Conservative and Minimal @objc inference workflows

Based on recommendations in SE-0160, there are two migration workflows:

Conservative: Maintain @objc visibility that was inferred in Swift 3
by adding @objc to all declarations that were implicitily visible to
the Objective-C runtime. This is invoked in the migrator by adding the
-migrate-keep-objc-visibility flag.
Minimal: Only declarations that must be visible to Objective-C based
on their uses (or in cases like dynamic vars) are migrated.

rdar://problem/31876357

@swift-ci Please smoke test and merge

@swift-ci Please smoke test


Use bash as the bonnyci user shell

Using sh is so outdated. Let's use bash instead.
Signed-off-by: Jamie Lennox<EMAIL_ADDRESS>

Build failed.

http://logs.bonnyci.com/check_github/BonnyCI/hoist/50/1484026099.59/ubuntu-hoist : FAILURE in 50s

This needs to be rebased since another PR merged.

Build failed.

http://logs.bonnyci.com/check_github/BonnyCI/hoist/50/1484086977.45/ubuntu-hoist : FAILURE in 3m 53s

recheck

Build failed.

http://logs.bonnyci.com/check_github/BonnyCI/hoist/50/1484087493.18/ubuntu-hoist : FAILURE in 3m 48s

recheck

Build failed.

http://logs.bonnyci.com/check_github/BonnyCI/hoist/50/1484088426.74/ubuntu-hoist : FAILURE in 3m 51s

recheck

Build failed.

http://logs.bonnyci.com/check_github/BonnyCI/hoist/50/1484173450.09/ubuntu-hoist : FAILURE in 3m 47s

recheck


update_one/3 does not accept replacement documents

The Mongo docs state that update can be used with a replacement document:
https://docs.mongodb.com/manual/reference/method/db.collection.update/#update-method-replacement-document
However, this line makes it so Mongo.update_one/3 only accepts update operator expressions:
https://github.com/zookzook/elixir-mongodb-driver/blob/0e1487842f107839e6ea3165a24c8bb55afadf3c/lib/utils.ex#L39
Is this intentional?

I missed the replace_one/5 function, sorry!


driverDir CLI; revamp CLI usage printing

Background
In order for the DriverLauncher to work, it must have a directory that is writeable by the DriverLauncher and readable by the launched Driver, on whatever node that Yarn allocates the Driver to.  The DriverLauncher places the myria jar and other configuration information inside this location, for transfer to the Driver itself.
The default file system this directory exists in is given by the fs.defaultFS parameter in core-site.xml.  If the defaultFS parameter is not specified, it defaults to file:///.  If you need to change the filesystem (say, to HDFS or to S3). then modify core-site.xml.
The default file location within the filesystem is /tmp.  If you need to change this, then specify the -driverDir parameter on the command line when you start Myria.
*** This will allow you to use Myria without HDFS. ***  (if you have a directory visible to both the driver launcher and the driver, wherever it is launched. For example, this is easy with a Lustre parallel file system.)
CLI usage
The driver launcher will now log what parameters were expected along with their doc strings, and what parameters were given.

@senderista This should be good to go.

Coverage increased (+0.01%) to 26.797% when pulling de233e9deeec511793d4ce48618f13a0c5272367 on add-driver-dir into 2918e59d9c686bf8b9f5296ea691cd24afa7d865 on master.

Coverage decreased (-0.06%) to 26.727% when pulling c59c2c0ec1ffca717a1695939506173064c20b5e on add-driver-dir into 2918e59d9c686bf8b9f5296ea691cd24afa7d865 on master.

Coverage decreased (-0.007%) to 26.778% when pulling c59c2c0ec1ffca717a1695939506173064c20b5e on add-driver-dir into 2918e59d9c686bf8b9f5296ea691cd24afa7d865 on master.

Coverage decreased (-0.07%) to 26.743% when pulling f17ed575bc4466de93259838b3fedc9cc94f219b on add-driver-dir into 63bcd9d05be90c3b3a52ee2f15523668269eca77 on master.

Addressed comments

Coverage decreased (-0.005%) to 26.808% when pulling a8f1a29ef00477d2e8c469567340ba4c5eddd507 on add-driver-dir into 63bcd9d05be90c3b3a52ee2f15523668269eca77 on master.

Coverage decreased (-0.001%) to 26.812% when pulling 963dcbb49421690e374234b87196ef5b005abe28 on add-driver-dir into 63bcd9d05be90c3b3a52ee2f15523668269eca77 on master.

Coverage decreased (-0.03%) to 26.781% when pulling 3588946c85843e2e145922c94c084e645e460e28 on add-driver-dir into 63bcd9d05be90c3b3a52ee2f15523668269eca77 on master.


Adaptive quality for volume rendering

References and relevant issues
I paired for a bit with @kevinyamauchi to try to resurrect #4764. I think this
is an extremely high-value contribution and we should aim to get it in ASAP and
certainly for 0.5.0. I've been playing around with it today and it makes
working with large volumes much more pleasant. It's also a good general
framework on which we can build with other layers, including adding support
e.g. for multiscale meshes, subsampling point clouds, etc.
Description
This PR adds a change_render_quality method to the base layer, that is
do-nothing by default, but emits a render_quality event that can be listened
to. It also connects the VispyImageLayer to this event and changes the node
step_size to be larger (coarser) when the framerate drops below a desired
value, or smaller (finer) when it is very fast. Finally, when a user stops
moving the camera for long enough, it makes a final high-quality render pass.
With this combination of settings, volumes that are previously unusably choppy
render smoothly when panning and zooming the camera, then render with maximum
(or rather default) level of detail when pausing in a certain view.
There are a lot of cool improvements to make here, including UI for manually
setting automatic quality adjustment or setting a specific quality level
manually, but imho those should come in subsequent PRs.

I agree this would be really high value.
Started playing with it, after a zoom in zoom out, I get a traceback:
ValueError                                Traceback (most recent call last)
File ~/micromamba/envs/napari-dev/lib/python3.11/site-packages/superqt/utils/_throttler.py:249, in ThrottledCallable._set_future_result(self=<superqt.utils._throttler.ThrottledCallable object>)
    248 def _set_future_result(self):
--> 249     result = self._func(*self._args[: self._max_args], **self._kwargs)
        self._func = <bound method QtViewer.redraw_at_higher_resolution of <napari._qt.qt_viewer.QtViewer object at 0x16a86f880>>
        self = <superqt.utils._throttler.ThrottledCallable object at 0x3281104c0>
        self._args[: self._max_args] = (<Event blocked=False handled=False native=None source=None sources=[] type='moving_finished'>,)
        self._kwargs = {}
        self._args = (<Event blocked=False handled=False native=None source=None sources=[] type='moving_finished'>,)
        self._max_args = 1
    250     self._future.set_result(result)

File ~/Documents/dev/napari/napari/_qt/qt_viewer.py:1082, in QtViewer.redraw_at_higher_resolution(self=<napari._qt.qt_viewer.QtViewer object>, event=<Event blocked=False handled=False native=None source=None sources=[] type='moving_finished'>)
   1080 logging.info('redraw at higher res')
   1081 for v_layer in self.viewer.layers:
-> 1082     v_layer.change_render_quality(RenderQualityChange.MAX)
        v_layer = <Image layer 'Image' at 0x329cd3350>
        RenderQualityChange.MAX = <RenderQualityChange.MAX: 'max'>
        RenderQualityChange = <enum 'RenderQualityChange'>
   1083 self._fps_monitor._final_redraw = True
   1084 self.canvas._scene_canvas.update()

File ~/Documents/dev/napari/napari/layers/base/base.py:2139, in Layer.change_render_quality(self=<Image layer 'Image'>, render_quality=<RenderQualityChange.MAX: 'max'>)
   2136 self._change_render_quality(render_quality)
   2138 # event that triggers the vispy visual to change render quality
-> 2139 self.events.render_quality(render_quality=render_quality)
        render_quality = <RenderQualityChange.MAX: 'max'>
        self.events.render_quality = <napari.utils.events.event.EventEmitter object at 0x329deb090>
        self = <Image layer 'Image' at 0x329cd3350>
        self.events = <napari.utils.events.event.EmitterGroup object at 0x329ddec50>

File ~/Documents/dev/napari/napari/utils/events/event.py:764, in EventEmitter.__call__(self=<napari.utils.events.event.EventEmitter object>, *args=(), **kwargs={'render_quality': <RenderQualityChange.MAX: 'max'>})
    761     self._block_counter.update([cb])
    762     continue
--> 764 self._invoke_callback(cb, event if pass_event else None)
        event = <Event blocked=False handled=False native=None source=None sources=[] type='render_quality'>
        self = <napari.utils.events.event.EventEmitter object at 0x329deb090>
        cb = <bound method VispyBaseLayer._on_render_quality_change of <napari._vispy.layers.image.VispyImageLayer object at 0x39eb36d50>>
        pass_event = True
    765 if event.blocked:
    766     break

File ~/Documents/dev/napari/napari/utils/events/event.py:802, in EventEmitter._invoke_callback(self=<napari.utils.events.event.EventEmitter object>, cb=<bound method VispyBaseLayer._on_render_quality_...pari._vispy.layers.image.VispyImageLayer object>>, event=<Event blocked=False handled=False native=None source=None sources=[] type='render_quality'>)
    800     self.disconnect(cb)
    801     return
--> 802 _handle_exception(
        self = <napari.utils.events.event.EventEmitter object at 0x329deb090>
        event = <Event blocked=False handled=False native=None source=None sources=[] type='render_quality'>
        cb = <bound method VispyBaseLayer._on_render_quality_change of <napari._vispy.layers.image.VispyImageLayer object at 0x39eb36d50>>
        (cb, event) = (<bound method VispyBaseLayer._on_render_quality_change of <napari._vispy.layers.image.VispyImageLayer object at 0x39eb36d50>>, <Event blocked=False handled=False native=None source=None sources=[] type='render_quality'>)
    803     self.ignore_callback_errors,
    804     self.print_callback_errors,
    805     self,
    806     cb_event=(cb, event),
    807 )

File ~/Documents/dev/napari/napari/utils/events/event.py:789, in EventEmitter._invoke_callback(self=<napari.utils.events.event.EventEmitter object>, cb=<bound method VispyBaseLayer._on_render_quality_...pari._vispy.layers.image.VispyImageLayer object>>, event=<Event blocked=False handled=False native=None source=None sources=[] type='render_quality'>)
    787 try:
    788     if event is not None:
--> 789         cb(event)
        event = <Event blocked=False handled=False native=None source=None sources=[] type='render_quality'>
        cb = <bound method VispyBaseLayer._on_render_quality_change of <napari._vispy.layers.image.VispyImageLayer object at 0x39eb36d50>>
    790     else:
    791         cb()

File ~/Documents/dev/napari/napari/_vispy/layers/base.py:292, in VispyBaseLayer._on_render_quality_change(self=<napari._vispy.layers.image.VispyImageLayer object>, event=<Event blocked=False handled=False native=None source=None sources=[] type='render_quality'>)
    288 def _on_render_quality_change(self, event=None):
    289     """
    290     Passthrough for the render quality change event.
    291     """
--> 292     self.change_render_quality(quality_change=event.render_quality)
        self = <napari._vispy.layers.image.VispyImageLayer object at 0x39eb36d50>
        event.render_quality = <RenderQualityChange.MAX: 'max'>
        event = <Event blocked=False handled=False native=None source=None sources=[] type='render_quality'>

File ~/Documents/dev/napari/napari/_vispy/layers/image.py:215, in VispyImageLayer.change_render_quality(self=<napari._vispy.layers.image.VispyImageLayer object>, quality_change=<RenderQualityChange.MAX: 'max'>)
    213 elif quality_change == RenderQualityChange.MAX:
    214     new_step_size = self.min_step_size
--> 215 self.node.relative_step_size = new_step_size
        new_step_size = 0.0625
        self.node = <Volume at 0x39eb45a90>
        self = <napari._vispy.layers.image.VispyImageLayer object at 0x39eb36d50>
    217 # update the minimum step size based on current performance
    218 # we don't go below 1 because we want to be able to render accurately
    219 # to the level of a single data pixel
    220 self.min_step_size = np.clip(new_step_size / 4, 0.05, 1)

File ~/micromamba/envs/napari-dev/lib/python3.11/site-packages/vispy/util/frozen.py:17, in Frozen.__setattr__(self=<Volume>, key='relative_step_size', value=0.0625)
     13 if self.__isfrozen and not hasattr(self, key):
     14     raise AttributeError('%r is not an attribute of class %s. Call '
     15                          '"unfreeze()" to allow addition of new '
     16                          'attributes' % (key, self))
---> 17 object.__setattr__(self, key, value)
        self = <Volume at 0x39eb45a90>
        key = 'relative_step_size'
        value = 0.0625

File ~/micromamba/envs/napari-dev/lib/python3.11/site-packages/vispy/visuals/volume.py:1170, in VolumeVisual.relative_step_size(self=<Volume>, value=0.0625)
   1168 value = float(value)
   1169 if value < 0.1:
-> 1170     raise ValueError('relative_step_size cannot be smaller than 0.1')
   1171 self._relative_step_size = value
   1172 self.shared_program['u_relative_step_size'] = value

ValueError: relative_step_size cannot be smaller than 0.1

This interacts oddly with attenuated_mip . The model de-attentuates when rotated -- because of the step change I assume. This makes this get suddenly brighter and then after stopping --after a second -- dim again.

Related to this is: https://github.com/napari/napari/issues/3550
BTW, the relative_step_size default in vispy, which napari is using outside this PR as far as I can tell, is 0.8 and the recommended range is 0.5 to 1.5. So the final render pass at 0.1 is probably why I see the 2-3 s lag.

Gah, I thought the minimum step size in vispy was 0.05. (And I have wanted to remove it since #3550.) @brisvag any chance I could deputise you to review vispy/vispy#2587? 😬
I had a chance to think about the PR a bit more while I was sleeping. 😂 Another place where this would currently break some stuff is napari-animation, where you want to make sure the quality stays high even if it takes a long time to render. So I'll add another setting, RenderQuality.DEFAULT, which goes to the default value of 0.8 (here I had also thought it was 1).
The attenuated mip artifacts probably need some correction in the shader, but maybe we can change the effective attenuation based on the quality. Will investigate, thank you for testing @psobolewskiPhD!

Bah, the attenuation is already scaled by the step size???
https://github.com/vispy/vispy/blob/3e2aadacdc320fffa6b251d96de3c75ceed76065/vispy/visuals/volume.py#L421
Something is probably going wrong there... I think actually the sumval should be multiplied by the step size in the line above:
https://github.com/vispy/vispy/blob/3e2aadacdc320fffa6b251d96de3c75ceed76065/vispy/visuals/volume.py#L420
If someone more familiar with attenuated mip than me can chime in here (@aganders3?) I would be super grateful! I'll try to think about it a bit more... As it is, it definitely can be very jarring for some combinations of step size and attenuation.

Ok I've opened vispy/vispy#2588 which fixes the attenuation issues completely. (There is a slight brightness flicker but I think this is just within the error bounds of the integral being computed with different precisions.)

Ah, tests are failing because of dangling QTimers:

AssertionError: If you see this error, it means that a QTimer was started but not stopped. This can cause tests to fail, and can also cause segfaults. If this test does not require a QTimer to pass you could monkeypatch it out. If it does require a QTimer, you should stop or wait for it to finish before test ends. The QTimers were started in:

I guess it's the final-pass debouncer. The error message is pretty good:

it's possible that there was a problem with unfinished work by a qthrottler; to solve this, you can either try to wait (such as with qtbot.wait) or disable throttling with the disable_throttling fixture

I can do that, and/or (probably better) make make_napari_viewer return a viewer with auto_quality=False.
@Czaki any suggestions about this?

I can do that, and/or (probably better) make make_napari_viewer return a viewer with auto_quality=False.

It looks like bast approach. As it should speed up tests in general (or prevent slowing down).
Please execute benchmarks on this PR when it be ready.

I've been playing with this a lot with various biological data sets.
I know we'd love 60 fps, but:
I find 20-30 but still providing detail to find what I am looking for to be much better.
So I've capped the max at 8, which for the data I'm looking at looks degraded, but not hopeless. And I've tweaked the fps targets down so it's less aggressive.
I've also bumped up the minimum step to 0.5 to make things more responsive, both at start ad finish.
And I've tweaked the fps window to be shorter as well (0.15), which also seems to make it more responsive: the first value is more reliable quickly?
So I think this mode and these values will need to be in the settings, because what is good (enough) will vary with dataset and hardware?

Thanks both for the thorough testing!
In the last few commits I've:

stopped updating the minimum value (I agree that seemed iffy and in practice was iffy). For now, I've left it as the current default — we can address #3550 in another PR 😅.
allowed an auto_quality=False setting on the viewer which gets rid of all the auto-updates, including the final update.

The other thing I might do is store the lowest quality setting yet seen. Or the average quality while moving. Then, after the final high quality update, we can immediately skip to that one when we move again, which should help with the initial responsiveness?
I'm not sure how to deal with the initial jerkiness — maybe we start with the lowest quality (after initial draw), and then adjust to higher quality?

The other thing I might do is store the lowest quality setting yet seen. Or the average quality while moving. Then, after the final high quality update, we can immediately skip to that one when we move again, which should help with the initial responsiveness?

I like this idea. It's likely the user is using the same hardware and same dataset, so if step of 4 was good previously to rotate the model, step of 4 would likely be good-ish now.
But I think simply using an initial value that's >1 would be fine. E.g. using 2 or 4 markedly improves responsiveness with relatively low degradation. I wouldn't use the worst setting right off I don't think, just because there will be a jarring drop in quality.
I'd even think about debouncing the quality changes, so short drags don't proc so many changes.
Or the other way around, sample frequently and use smaller step changes so the changes in quality are more subtle and smooth.

I had a phone chat with @royerloic about this one and he had the following advice to give:

Visualise what's happening. That's a little bit what the logging and fps/stepsize display are doing but it's hard to look at it all together. Probably a few plot widgets (either as an overlay or just mpl/PyQtGraph docked widgets) would make the experience much nicer.
Don't make huge jumps in quality — they are jarring. It's better to (a) calculate the stepsize change needed to achieve the target framerate — this is possible because framerate scales linearly with step size; then (b) take half that step towards the target framerate. (Zeno's Approach?) This takes longer to converge but will result in smooth steps towards the target, and, importantly, it won't repeatedly jump up and down in quality as it does now.
For this to work you need a stable estimate of the framerate, which we currently don't have. But we can use an exponential filter: with each new measurement, make your estimate 0.9 * previous estimate + 0.1 * new measurement. This filters out the noise and naturally creates a smooth running average of the framerate measurements.
Finally (but this might not be needed with all of the above), if reject new values if they are way different from the previous estimates. This would be useful e.g. to reject that first estimate from VisPy after a long stationary period, since VisPy only tells you the time between draws.

I'm not sure I understand point 1, is that to like not render the back of the model or something? where does matplotlib come in? Sorry i'm dense.
The others sounds great. As I mentioned before, I don't see huge value in hitting 60 fps immediately, rather that the process of rotating/moving is less choppy. So using smaller jumps would make it less jarring. I ended up dropping the cap a lot and just enjoying 30 fps and almost perfect rendering.
I think the other important thing is to make the initial render when moving be not at the final high quality. And if the final render is super high, it makes other interactions laggy, like adjusting gamma. So striking a balance here is important.

Maybe there's a way to improve vispy's FPS monitoring? For example we could use glFinish to sync with the CPU every N frames to get a better estimate of the draw time. I guess this makes me a little nervous about blocking the main thread for very slow renders. I think we're stuck with older OpenGL that doesn't have the necessary timer queries for GPU-based measurement.
I cheated and hacked in an FPS measurement using canvas.render() and just discarding the result, and (ignoring the wasted work) it seemed to work well. I think this could be a big help.

@psobolewskiPhD sorry the first point is not for the feature but for development of the feature — Loic's advice was to always visualise in real time what is going on with your estimates and adjustments because it's very easy to get wrong. (Viz will help you eg instantly spot big jumps in your estimates etc.)

I cheated and hacked in an FPS measurement using canvas.render() and just discarding the result, and (ignoring the wasted work) it seemed to work well. I think this could be a big help.

@aganders3 I'm sorry I don't really understand the approach or how it could be used here... Perhaps some code would help? 😬

Yeah sorry - I was not clear. What I mean is I rendered the whole canvas offscreen and timed it, then used that time to estimate what the FPS would be.
Here's a diff:
diff --git a/napari/_qt/qt_viewer.py b/napari/_qt/qt_viewer.py
index 6c3d6be8a..e8006d8ad 100644
--- a/napari/_qt/qt_viewer.py
+++ b/napari/_qt/qt_viewer.py
@@ -2,6 +2,7 @@ from __future__ import annotations

 import logging
 import sys
+import time
 import traceback
 import warnings
 import weakref
@@ -1077,7 +1078,11 @@ class QtViewer(QSplitter):
             or not self._camera_monitor.camera_moving
         ):
             return
-        fps = event.fps
+        # fps = event.fps
+        start = time.perf_counter()
+        self.canvas._scene_canvas.render()  # discarded off-screen render
+        fps = 1 / (time.perf_counter() - start)
+        logging.info(f'estimated fps: {fps}')
         if fps < self.viewer.target_fps[0]:
             logging.info('decrease render quality')
             for layer in self.viewer.layers:

This very obviously wastes work (a full rendering frame worth of it), but it also makes it so I can't fake out the FPS timer with subtle mouse and/or scroll movements.
If vispy are open to changes, my idea is (something like) rendering every 10th frame with glFinish. This would allow timing the actual draw time on that frame. The vispy canvas could store the previous 10 draw times (data from 100 frames worth) and average them, reported in a new event. (This could all be configurable, off by default.) The performance hit is in the synchronization of GPU and CPU. There may be some more edge cases/gotchas in there, but I think it's a more accurate measure of the "FPS" we're interested in.
Whatever changes you made since the last time I tested (camera monitor?) mostly do seem to help as well!

One other thought: maybe it should adjust quality on visible layers?

Whatever changes you made since the last time I tested (camera monitor?)

That was @kevinyamauchi. 😊 Honestly I think that gets us 90% of what we want, then discarding the very first frame read after a camera move gets us another 9%, and then your stuff would be the final 1%? Maybe?

One other thought: maybe it should adjust quality on visible layers?

Good thinking indeed. Actually I realised that this PR actually needs a lot of work — for example, if we have a tiny image and tons of points, the fps will be garbage, but changing the quality of the image will change nothing, and we'll get crappy image quality for no benefit. So I think I'll make auto_quality=False by default and we can then tweak things at a more leisurely pace as we get more user testing...

So I think I'll make auto_quality=False by default and we can then tweak things at a more leisurely pace as we get more user testing...

This seems reasonable. Another issue I had was with the max_observed_step_size - I think it should be reset if you update the data on a layer, otherwise I have a perfectly fast layer jumping to a step size of 80 whenever I move it.

Oh! you probably want to disable this for rendering planes -- pan or zoom triggers the step change and the plane disappears!

FYI: I'm getting a RuntimeError when I quit napari:
Exception ignored in: <function CameraMonitor.__del__ at 0x158a44180>
Traceback (most recent call last):
  File "/Users/piotrsobolewski/Dev/napari/napari/_qt/qt_viewer.py", line 1387, in __del__
    self._reset_camera_moving.cancel()
    ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/piotrsobolewski/Dev/miniforge3/envs/napari-dev/lib/python3.12/site-packages/superqt/utils/_throttler.py", line 291, in __get__
    parent = self.parent()
             ^^^^^^^^^^^^^
RuntimeError: wrapped C/C++ object of type ThrottledCallable has been deleted

Yeah that's why the tests are failing also... 😢 I'm gonna mark this as draft while I figure out what the deal is with timers...

if we have a tiny image and tons of points, the fps will be garbage, but changing the quality of the image will change nothing, and we'll get crappy image quality for no benefit

We can try some heuristics using the size of the (displayed) image and the number of (displayed) points, giving priority to the big one.


build: update Cargo.lock

#757  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Added accessors to quaternion elements

Hi,
A small improvement for accessing quaternion elements.

Codecov Report

Merging #89 (7df22b1) into main (2458446) will decrease coverage by 0.51%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #89      +/-   ##
==========================================
- Coverage   57.42%   56.90%   -0.52%
==========================================
  Files          38       38
  Lines         876      884       +8
==========================================
  Hits          503      503
- Misses        373      381       +8

Impacted Files
Coverage Δ

src/quaternion.rs
0.00% <0.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 2458446...7df22b1. Read the comment docs.

Thank you!


Update to latest upstream yosys.

Fixes #1161

LGTM if CI goes green.

Vendor test failure are pre-existing failures.


Regarding Production Build

I have cloned the repo and was trying the command 'gulp build.prod' which creates the production release however I am a little puzzled as I see one app.js file which has all the code for different components minified and uglified in it. Does it mean when I have say 100 components in the application along with their html , js files , all these components will be put into one app.js file. This means the size of this app.js file will always increase and we are not then using lazy loading as we do not load components which we need, in this way we will be loading all the components which index.html file is loaded.

Yes, at the moment that is the case. More advanced production build will be considered in future.
For sure we'll include tree-shaking and offline compilation in near future when we'll reduce the app size to ~50kb gzipped and minified.


How to override message "No results found" ?

I want to set message when no results, how can I do this ?

By setting the notFoundMsg property to the text you want to show:
<ng-select
    notFoundMsg="No characters found"
    [options]="characters">
</ng-select>

Please stick to reporting issues here. Use Stackoverflow or a similar forum for asking quentions. And consult the documentation, you could have found it there as well.


Feature/2023/04

Codecov Report
Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (4cd406b) 66.28% compared to head (43951e6) 67.47%.

Files
Patch %
Lines

solution-runner/src/main.rs
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
+ Coverage   66.28%   67.47%   +1.18%
==========================================
  Files          36       38       +2
  Lines        1148     1193      +45
==========================================
+ Hits          761      805      +44
- Misses        387      388       +1

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


Setting UAA session timeout (backend) in config

As described in #319, it is currently not possible to configure the UAA's backend session timeout - it falls back to Tomcat's default setting of 30 minutes.
It would be nice if we could specify this session timeout as part of login.yml or uaa.yml (and the equivalent uaa-boshrelease templates so that we can set it in the cf-release).

@MatthiasWinzeler
Starting with UAA 3.2.0 & CF - Release 232 setting a session timeout for UAA is now possible.
Please refer to :  https://github.com/cloudfoundry/uaa-release/releases/tag/v7 for more details

@sreetummidi we have implemented cookie timeout, but not session timeout. They are slightly different. The cookie timeout is a hard date. The browser will discard the cookie after that time.
The session timeout is an idle server timeout. If the server hasn't received a request in so long, it will discard the server side session. Unrelated to the cookie.


Review handling of the environment variables in the react applications

Review handling of the environment variables in the react applications, currently our application includes some sensitive data into the html pages. We need to pass environment variables by a safe way (check https://nextjs.org/docs/pages/building-your-application/configuring/environment-variables). Note: it may require update of the pipelines. It also may be a one of reasons of hydration errors generated by NextJs

Hi @hlayisanimazuze. It was implemented earlier. Currently front-end application uses environment variable BACKEND_URL


Possible Licensing Violation

Ungoogled Chromium's name includes the "Chromium" branding of the upstream Chromium project. Under BSD 3-Clause License, this is not permitted, as stated in the license file itself:
"A permissive license similar to the BSD 2-Clause License, but with a 3rd clause that prohibits others from using the name of the project or its contributors to promote derived products without written consent."
Has Ungoogled Chromium received permission from upstream Chromium to use the "Chromium" branding? If not, the Ungoogled Chromium project seems to be in violation of the upstream project's licensing.

Ungoogled Chromium also includes "google" in its name; this seems to also be a licensing violation.

And google will try to sue undoxxed devs? lmao
This has been discussed before https://github.com/ungoogled-software/ungoogled-chromium/discussions/1757 but nothing has been done yet afaik.

Being "undoxxed" means nothing; it's obscurity. The only thing Google/Chromium has to do is contact GitHub about the issue and this project is over. You're pretty naive.

You are naive if you think this project dies if this repository is removed. Trying to shut down an open source project with undoxxed devs is a cat and mouse problem that google can't win. They can certainly try and lose money in the process.

this is not permitted, as stated in the license file itself

Please provide references baking that claim, because LICENSE file looks as follows:
// Copyright 2015 The Chromium Authors
//
// Redistribution and use in source and binary forms, with or without
// modification, are permitted provided that the following conditions are
// met:
//
//    * Redistributions of source code must retain the above copyright
// notice, this list of conditions and the following disclaimer.
//    * Redistributions in binary form must reproduce the above
// copyright notice, this list of conditions and the following disclaimer
// in the documentation and/or other materials provided with the
// distribution.
//    * Neither the name of Google LLC nor the names of its
// contributors may be used to endorse or promote products derived from
// this software without specific prior written permission.

Which looks to me like a pretty normal BSD 3-Clause License which prohibits promotion in the name of Google or contributors.

This is an old issue, that didn't show much activity recently — closing.
If you have any more information to add, let us know.


Step 7 in Add a web API application seems wrong

In step 7 up there it says to set the redirect URL to https://localhost:44332 but that's the service. When I do that and click  the to-do list button, I get redirected to https://localhost:44332 but that's just the service so it doesn't seem to work.
On the other hand if I put https://localhost:44316/ into the redirect URL, my browser gets into what looks like a redirect cycle and just continuously reloads.
In neither case does this tutorial get me to the to-do list. I got through the previous ones and sign-up / login works but this API access bit doesn't seem to.

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

ID: 469d2731-66dd-4490-89bd-4a36f893e7be
Version Independent ID: 11f4ae00-d1e9-1355-a0c3-2435f90b17d8
Content: Tutorial - Grant access to an ASP.NET web API - Azure Active Directory B2C
Content Source: articles/active-directory-b2c/active-directory-b2c-tutorials-web-api.md
Service: active-directory
Sub-service: b2c
GitHub Login: @mmacy
Microsoft Alias: marsma

@madtownchris  Thanks for your feedback! We will investigate and update as appropriate.

When I revert the web.configs to the sample, it works as expected (i.e. using fabrikamb2c.onmicrosoft.com) so something is obviously wrong with the way I configured my B2C application but I've reviewed the steps here several times and it seems like I did it right. Screenshots of the Azure configuration might be helpful.

What changes did you do to the github sample? It should be working properly,

@madtownchris I was just able to run the tutorial properly. With the end result working with the todo list application.
Please remember to xml encode the client secret. I will make a request to add this in the https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-tutorials-web-app
doc.
My suggestion is to review the docs more closely, if there are anymore questions within the scope of this issue please let me know, otherwise I will be closing out this git issue.

Hey Madtown, I'm following up on this. I will be closing this issue out if there's no response by end of day today. If you have anymore questions within the scope of this issue please reopen it and we can continue working on the issue.

Well as I said the tutorial and client code works fine when connected to
the fabrikamb2c but for whatever reason with my own B2C tenant, I get the
redirection.
I've gone through the steps several times to no avail.
What seems to make more sense is the instructions here:
https://docs.microsoft.com/en-us/aspnet/core/security/authentication/azure-ad-b2c?view=aspnetcore-2.2
and
https://docs.microsoft.com/en-us/aspnet/core/security/authentication/azure-ad-b2c-webapi?view=aspnetcore-2.2
I got both of those examples working.
On Wed, Jul 17, 2019 at 3:40 PM Frank Hu<EMAIL_ADDRESS>wrote:

Hey Madtown, I'm following up on this. I will be closing this issue out if
there's no response by end of day today. If you have anymore questions
within the scope of this issue please reopen it and we can continue working
on the issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/35232?email_source=notifications&email_token=AETQED3WDG2QKPDAJXE6C5TP757SVA5CNFSM4IEDCYV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2GQU7I#issuecomment-512559741,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AETQED3KPC4A2J6VGBOLDNDP757SVANCNFSM4IEDCYVQ
.

When you use the fabrikamb2c tenant? You would have needed to change the app id, secrets, etc... It's not just a b2c tenant name change. Did you change all the other values?

Hey @madtownchris it looks like similar users are having issues. Per the so post : https://stackoverflow.com/questions/56993058/iconfidentialclientapplication-getaccountsasync-returns-nothing
Did you change the values in the web.config in the taskwebapp?

That's the exact problem I'm seeing but adding the TenantId doesn't seem to
fix it.
When I use the fabrikamb2c tenant, I use the values as provided in the
sample source. I have commented those values all out and have a whole
section with values for my tenant.
I've tried both

and

since I found the second works in some situations (celpidgepost is my . But
here neither works.
On Wed, Jul 17, 2019 at 6:09 PM Frank Hu<EMAIL_ADDRESS>wrote:

Hey @madtownchris https://github.com/madtownchris it looks like similar
users are having issues. Per the so post :
https://stackoverflow.com/questions/56993058/iconfidentialclientapplication-getaccountsasync-returns-nothing
Did you change the values in the web.config in the taskwebapp?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/35232?email_source=notifications&email_token=AETQED4WE2767UAIZFQJ2BLP76RDLA5CNFSM4IEDCYV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2G2ZNA#issuecomment-512601268,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AETQED26ETHH6ZYHLEHHCOTP76RDLANCNFSM4IEDCYVQ
.


Some authentication changes for improving documentation

This is about improving the documentation on authentication backends and object permissions. See also
#10600 and #10601.
This is work in progress. It is supposed to illustrate current issues and how they could be fixed.

Hi @xi. Thanks for this. It makes it easier to review the combined changes together if we can.
How good are you with managing your git history? Ideally we want exactly 3 commits here:

Fixed #29918 -- Added support for object permissions in PermissionRequiredMixin.
Fixed #20218 -- Added DefaultObjectPermissionsBackend.
Refs #29918, #20218 -- Improved Authentication Docs.

Are you able to adjust for this?

Hi @carltongibson. I rebased my changes. The history is now slightly different than what you suggested:
f536a2f  is about general doc improvements that are not related to the further changes.
fe9a441 is about changes as discussed in this mailing list thread

OK, no problem — it's the general idea that matters just now. Thanks!

As for me, I'd rather have separate PRs to review and merge separately unless the commits are tightly coupled which doesn't seem to be the case here.

As for me, I'd rather have separate PRs to review and merge separately unless the commits are tightly coupled which doesn't seem to be the case here.

I think this is something you as reviewers have to decide. For me it is fine either way. Feel free to re-open and comment/merge #10600 and #10601. I can rebase this pull request afterwards.

Sorry @timgraham — I asked to have it in one place. I thought #10600 and #10601 required docs changes; @xi made reasonable points that a bit of a re-write was needed; at that point it became coupled such that I wanted to address it as one. It's in my queue for this week.

Thanks for the extensive feedback!
I removed the last commit and incorporated some of your suggestions.  Maybe you can mark some comments as resolved or add further feedback and I will do a second round of changes.
I am not completely sure how the review process usually works: Am I expected to amend/rebase my commits or add additional commits on top? Should I mark comments as resolved, should I comment with "done", or should I leave that completely to you? I am appy to adapt to any process you prefer :smiley:

Hi @xi. Process isn't that important. We're just trying to make it as good as we can. 🙂 I'll take another look later.

Oh, Once the docs are right...
I'm inclined to see this as a single fix/improvement: for example, I understand your point but, I can't really see the benefit of the get_permissions_object() hook if we don't add the rest. (Better leaving third-parties the API-surface-area.)
As such, I'd check with Tim to see what he thinks but, I'd be inclined to pull it in as a single commit. At that point I might think the BaseBackend commit is worth adding as part of that too — if we go that way, it's part of the same improvement. (Not sure about that: just thinking.)
Thanks again for your effort here! #20218 is 6 years old, so it's a nice win. 🙂

@paulayo https://docs.djangoproject.com/en/dev/internals/contributing/ follow this

Ok, I think I am now much closer to what you are thinking. I restored much of the documentation to its original state, only adding the incremental examples at the end.
Before we forget about it: I am not completely happy with the name "DefaultObjectPermissionBackend". Now is the last time we can change it. Any ideas? What about "InheritGlobalPermissionBackend"?

Hi @xi. Sorry for the slow follow-up here, I needed a moment to get to this properly.
I have comments relating to four points:

The docs changes here.
#20218 Adding DefaultObjectPermissionsBackend.
#29918 PermissionRequiredMixin changes.
The simplifications to the API you originally discussed on the mailing list.

Docs Changes
I (still) don't think these are clear enough. The BlogPostBackend seems misleading. It's seems contrived to justify the need for DefaultObjectPermissionsBackend, which only really arrises because of inter-op with django-guardian.
For me you'd write it something like this:
def get_all_permissions(self, user_obj, obj=None):
    """Owner can edit/delete posts, others can only view"""
    perms = {'blog.view_blogpost'}
    if user_obj.is_active and not user_obj.is_anonymous:
        if isinstance(obj, BlogPost) and obj.owner == user_obj:
            perms += {'blog.change_blogpost', 'blog.delete_blogpost'}
    return perms

... and then the permission checks work as expected. As such, I don't think the additions are all that helpful.
Adding DefaultObjectPermissionsBackend
Adding a third backend (ModelBackend, django-guardian's and then the new DefaultObjectPermissionsBackend) seems like overkill. Why aren't we just subclassing ModelBackend and using that instead of, rather than as well as, ModelBackend?
Something like...
from django.contrib.auth.backends import ModelBackend

class ImpliedObjectPermissionsBackend(ModelBackend):
    """
    Ignores `obj` parameter to permission checks to apply general permissions
    at object-level.

    Use in place of `ModelBackend` in settings.AUTHENTICATION_BACKENDS to avoid
    the need to check permissions twice when using Guardian:

        user.has_perm('foo.change_bar', obj=bar)

    Rather than:

        user.has_perm('foo.change_bar', obj=bar) or user.has_perm('foo.change_bar')

    ...when using ModelBackend.
    """
    def has_perm(self, user, perm, obj=None):
        return super().has_perm(perm)

    ...

This would be a small little class, and since the need for this only comes up when using (e.g.) django-guardian I would suggest it would make an excellent contribution to guardian.backends there.
I think if this were part of django-guardian the weirdness of explaining the use-case would also disappear.
It seems to me it's natural home is there. I'll comment on the ticket as such.
PermissionRequiredMixin changes
On review I realise that the code suggested here already exists in guardian.mixins.PermissionRequiredMixin. (I should have noticed this before.)
Rather than pulling this out of its natural home in django-guardian, we should just say "Use that".
I'll comment on the ticket but, unless we're going to adopt a much more fully-featured implementation (which we're likely not) I think it's an error to try and pull bits and pieces in.
In general, we probably want less code here rather than more, to wit...
Simplifications to the API
Your original ideas appear to have got lost somewere in the existing old tickets.
Make get_user_permissions() public? (i.e. document it) — Yeah, why not? What other small changes?
I think there's too much going on here to pursue those here. I think we should close this one and try afresh with new Trac tickets and/or PRs. I hope that seems fair.
Closing on that basis but happy to discuss. Thanks!

Thanks again for the extensive feedback.
To be honest, I don't really get your argument. I am not sure why you think that django guardian is the only relevant backend. Agreed, many projects are not actively maintained (e.g. django-permission), but at least django-rules is.
More importantly, django-guardian only covers a very specific usecase (checking permissions on View.object). So people might have to write their own backends. For example, I wrote a custom backend for membership roles for a project I am working on. In order to do that I had to duplicate quite some code from other projects (such as django-guardian). In fact, every new backend will have to duplicate the exact same code.
Please don't get me wrong. I understand that this is a rarely used feature and you would prefer to keep it simple. I am just not sure how to continue: Do you think that django-guardian should be the only supported backend? Or do you think that custom backends should be supported? In that case I cannot follow your argument.
I could get into more detail about your comments, but I think this fundamental question needs to be answered first.

Hi @xi. No problem with supporting custom backends. (The extension point is already there.) But django-guardian is by far the biggest beast in this area: I'm quite happy to recommend people in install it even if all they want to use are the permissions mixin and (if it were to be added) the new suggested ModelBackend subclass.
Ultimately, having gone over this with you here extensively, I just can't see how these changes fit comfortably in Django itself, whereas adding them to Guardian (or in the case of the mixin, just leaving it where it is) is entirely natural. If it were code, we'd likely call the difficulty in spelling out the docs changes a smell — i.e. a warning we weren't putting it in the right place. I think the same thing occurs here.
For me, the bottom-line is that we've explicitly ruled this stuff out-of-scope and, so, given that sneaking in small parts of it just doesn't fit.
I hope that makes sense.

Even though I don't follow, I can accept your decision. Just let me try one final argument., maybe it convices you to think about it again:
What if I use django-guardian and django-rules in the same project? They both ship their own PermissionRequiredMixin, so which one am I supposed to use. In practice, either one will probably do the job, but to me this is a strong pointer that the mixin (and some other parts) actuelly does belong in django core.
In the case this does not convice you, do you want me to make a new pull request for any changes I proposed here or on the mailinglist? (You mentioned adding get_user_permissions() but as get_group_permissions() is already not being used I think that would be a step in the wrong direction)

Hi @xi. I'm not anti-improvements here. 🙂
I just don't think the suggestions in this PR, as we've arrived at, make sense. (They are, add the mixin from DG, the backend, and the docs example, which I think clouds the situation...)
Now maybe you are right, and we should extend the support for object permissions in core. Maybe.
But if so it should be feasible to come up with changes, starting with the docs I think, that are "Yes, that's obviously much clearer". In such a situation I'm all for it. But I don't think we're there.
For me, your initial email was "Let's improve/simplify the permissions API". So what does the new API look like, and what's the migration path to it? (This doesn't sound like a little project, but it could be a worthy one.)
At it stands, what I'm not keen on, is just pulling features out of a maintained third-party package to include them here. Unless there's an improvement on the cards, leave them where they are.

... already not being used...

I don't have a suggestion in hand. (I don't mind the existing system.) But get_group_permissions() is used by get_all_permissions() which is used by has_perm(), which is the main entry point, so I'm not sure what you mean.
Elsewhere, not here, blue skies: what do you think the permission system should look like? How is that clearer than what we have?

But get_group_permissions() is used by get_all_permissions() which is used by has_perm(), which is the main entry point, so I'm not sure what you mean.

Yes, it is used internally. But it is not used as an extension point by either django-guardian or django-rules. (Note that django-guardian has a similar function somewhere internally, but it is not exposed on the backend)
I will try to create a new, clean merge request.


Make Override System Portable

Is your feature request related to a problem? Please describe.
It would be very beneficial if RNV's override system was more standardised and could be applied via other methods.
On the most part this is ok for building static deployables (which can then be deployed independently) but presents a problem when runtime dependencies are in need of patching also (i.e. Next)
An example concrete use case would be building Docker containers
Describe the solution you'd like
A probable format here would be git diffs. Example uses of this are patch package, git apply or even yarn2's patch protocol
Creating the patches would be much easier also via git diff etc
Describe alternatives you've considered
For our specific use case contributing upstream to Next isn't an option. This proposal is obviously more generic however

@elmpp yes, as rnv plugin support grows, more robust override system will be needed. especially when it comes to

versioning
diffing / patching
compiled files overrides
dist regeneration

standard RN plugins are not affected as badly due to their simplicity and non compiled code nature and so it was generally manageable. nextjs is much bigger beast. forking was proven not viable either.
we investigated this before and https://github.com/ds300/patch-package should be good starting point
target for such a feature is around 0.32.x after 1st phase of engine introduction (0.31.x)


Add a sample how to create a keyboard with ndk

Hi, was looking for a way to create lightweight keyboard(ime) using ndk, unfortunately there is no such sample.

yes, I do not remember knowing that: a while back mentioned among us about that and the conclusion was using keyboard from java side, and via JNI to communicate back and forth.

@ggfan, thanks.
that looks not so good

will ask around to see what the current status is.

https://github.com/googlesamples/android-ndk/pull/137 was showing how do this using JNI.

@seniorivn oups, sorry for the missunderstanding!

closing this one as no info from native side found/available (probably go through jni to use java side api ). Please re-open it at any time as appropriate. thanks for bringing it up

this is a den of vipers
dude pk
ls ...
On 28 Dec 2016 19:14, "Gerry"<EMAIL_ADDRESS>wrote:

closing this one as no info from native side found/available (probably go
through jni to use java side api ). Please re-open it at any time as
appropriate. thanks for bringing it up
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googlesamples/android-ndk/issues/323#issuecomment-269553287,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABMdW5YsaNd8xmHd4hRmubZX85Z0bPKTks5rMuYygaJpZM4KufLI
.

THB: there is no native-side interface for this, I am sorry for not being direct if you were looking for a confirmative-direct answer.

@ggfan i got it, no problem


Allow for included modules with mirrored names

Hey 👋 checking out Gradle 7 and am a big fan so far.  One thing that is fantastic is the type safe project accessors.  However, I think there is a restriction that is a little short sighted, and that I think will cause many backwards compatibility issues.
Currently, the generated sources seem unable to handle the case where the rootProject.name is equal to the name of an included project.  A pretty standard scenario is to have a library repository, with the actual library as a child module.
For example, I am starting work on a library named kompendium.  I want to have (at least) two child projects, one for the actual library, also (hopefully 😄) named kompendium and a testing bench named playground.  So my settings.gradle.kts would look something like this
rootProject.name = "kompendium"
include("kompendium")
include("playground")

// Feature Previews
enableFeaturePreview("TYPESAFE_PROJECT_ACCESSORS")
enableFeaturePreview("VERSION_CATALOGS")

Unfortunately, this spits out the following error on build
org.gradle.api.internal.catalog.GeneratedClassCompilationException: Unable to compile generated sources:
  - File RootProjectAccessor.java, line: 29, method getKompendium() is already defined in class org.gradle.accessors.dm.RootProjectAccessor
> Unable to compile generated sources:
    - File RootProjectAccessor.java, line: 29, method getKompendium() is already defined in class org.gradle.accessors.dm.RootProjectAccessor

Is it the end of the world?

Expected Behavior

Projects and child modules should be allowed to have the same name, without the need for workarounds like renaming.
Current Behavior

Currently this is not possible
Context

Hopefully this is enough context 😸

it looks like a duplicate of https://github.com/gradle/gradle/issues/16608

indeed 👍