Mavlink instance does not start on telem2 automatically

My copter is equipped with Odroid computer with web camera dedicated to detect Aruco marker, on Odroid side i have Python script establishing connection with Pixhawk , waiting a heratbeat from flight controller and then starting to send vision_position_estimate messages if marker is visible.
It work fine with stable firmware, but when i tried to do the same  with Master - i discovered than the i need to manually start Mavlink instance for /dev/ttyS2 manually in console of QGC.
To Reproduce
Connect any device with Python and Mavlink library to telem2 port of Pixhawk, then execute following code
...
master = mavutil.mavlink_connection(opts.device, baud=opts.baudrate)
print "Waiting for PX4 heartbeat..."
master.wait_heartbeat()
print "PX4 connected!"
...
Code will stop on this waiting until you connect via QGC to telem1 port and in console executo following command
mavlink start -d /dev/ttyS2
After that Python script will output message "PX4 connected!"
Expected behavior
Mavlink instance on telem2 should start automaticly, like in Stable version of Firmware

All UARTs are now configurable on master: https://dev.px4.io/master/en/companion_computer/pixhawk_companion.html


[19.03 backport] info: report cgroup driver as "none" when running rootless

backport of https://github.com/moby/moby/pull/39299 for 19.03
Signed-off-by: Akihiro Suda<EMAIL_ADDRESS>
- What I did
Previously docker info had reported "cgroupfs" as the cgroup driver
but the driver wasn't actually used at all.
This PR reports "none" as the cgroup driver so as to avoid confusion.
e.g. kubeadm/kubelet will detect cgroupless-ness by checking this docker
info field. https://github.com/rootless-containers/usernetes/blob/297f077e9a062778e1cadba962b7b5e04cdc27eb/src/patches/kubernetes/0004-kubelet-new-feature-gate-SupportNoneCgroupDriver.patch#L319
Note that user still cannot specify native.cgroupdriver=none manually.
- How I did it
See daemon/daemon_unix.go
- How to verify it
$ docker info
Cgroup Driver: none

- Description for the changelog

info: report cgroup driver as "none" when running rootless
- A picture of a cute animal (not mandatory but encouraged)

https://en.wikipedia.org/wiki/Southern_rockhopper_penguin#/media/File:Gorfou_sauteur_-_Rockhopper_Penguin.jpg

ping @tiborvass @tonistiigi PTAL

failure is unrelated; merging


Add typescript support

Is your feature request related to a problem? Please describe.
As an engineer, I want to be able to write my code in typescript, so I can find out possible bugs at compile time.
Describe the solution you'd like
Typescript being a supported language in this repo
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
This was attempted before (https://github.com/intuit/user-data-for-fraud-prevention/pull/28) but due to a series of merge conflicts, was closed without merging. I recommend approaching this in a piecemeal fashion. However, the previous PR is a good reference point for this work still.

@reubenae @skodamarthi Can I give it a shot?

@reubenae Is this issue still available. If yes, I'd like to work on this.

@nsinghal12 absolutely! We had some snagging issues on Adam's PR, which never got merged. You can refer to that for next steps if you get stuck. I recommend raising small, incremental PR's so we can avoid big merge conflicts. Looking forward to your contribution!

Hi @skodamarthi is this issue apart of this year's hacktoberfest in addition to Grace Hopper?

Hi @regromrob Yes...this is open for hacktoberfest as well. Contributions are welcome!

Awesome @skodamarthi I would love to be assigned to this issue please.

Hi @reubenae @skodamarthi Would this be part of this hacktoberfest ?

@reubenae I think we can close this issue since #164 was merged. Do we also want to create a new issue to start migrating files from JavaScript to TypeScript? Or do you prefer to just have that happen naturally?

I won't have access to my laptop for a couple of days so can't add an issue for the file migration - but absolutely happy for that to happen deliberately rather than over time. So if you fancy a crack at that, go ahead! Small PR's better than large ones though please!

@pmaidens I'm back with laptop access now so feel free to make a PR and/or new issue as you wish, and I will review!

This issue is being worked on, but there is lots of work to go around. If you're looking at this for some work, please keep your PR's small so that merge conflicts are avoided and wasted work limited.
Thanks to Peter who has been leading the charge on this!

One of the most important things left for us to do here is that we need to publish our types for external consumption, and tie that into the exported functions to ensure we maintain those contracts.
The other major piece left is to migrate tests to TypeScript as well.


Adds migration scheduling to complete mapping list

~No issue to close here, this was just work for works sake 😬~
Fixes #515
its a long video, but worth a watch!

Edit: if this seems clunky, having to unschedule to re schedule, s' something that can be improved upon, but I don't want to make any promises before that it could be done by friday, so here seems like a good stopping spot... 🤞

@Yadnyawalkya should this be gaprindashvili/yes? piggy back off that same bz?

@AllenBW I'm a little confused as to why Unschedule is required before the plan can be scheduled again. Does running the plan not get rid of its schedule? I think this will be very confusing to the user. If an Unschedule button needs to appear for every completed plan, then I don't want to merge this before GA. Let's take the time to do it right.

@vconzola no need for confusion,  When we have a schedule on the record, something that was used to kick off a migration, it stays on the record until removed. But that makes sense, we might want to know when the last migration was scheduled to run, or maybe not?
UX guidance on how to "do this right" would be most appreciated.  Do we clear the past schedule upon migration completion, losing that record? Provide an edit button to modify the existing schedule? Do we ignore all past schedules and treat it as a new one?

@AllenBW I think the best UX is to clear the past schedule upon migration completion so that the options on a Completed plan become Schedule, Retry, and Archive with Archive being hidden under a kebab. I'll create a mockup.

@AllenBW Thinking about this does make me think of another edge case, however. Any idea what happens today if a scheduled migration fails to run for some reason, e.g., network problem? Do we indicate that in the UI at all? Leads me to think that we need an error in the plan list view and also to prioritize rescheduling migrations (vs. unschedule and schedule again like we have today).

@vconzola 👍 ok can clear upon completion, will have that change up in a few shakes. To your other question I believe this would fail just as a normal migration, to my knowledge we aren't provided any indication as to why a schedule failed to run.

@AllenBW I'm talking about the case where the request is never sent so the migration never starts at the scheduled time. Is this possible and a case we need to consider?

@vconzola Not sure I follow, the request is never sent? All api errors are handled by miq, so if theres an issue with setting the schedule we'll know then.  If your saying what happens in the case the schedule fails to run? Not sure we get any feedback to that effect.

@AllenBW That's the case I was thinking of - the schedule fails to run. Do we need to address this possibility?

@vconzola how abouts we chat this over in the standup 👍

@AllenBW Here's a mockup with a schedule button added for failed Completed plans and the Archive feature added under a kebab.

Late to the party, but this was a red flag for me:

Do we clear the past schedule upon migration completion, losing that record?

I agree with @vconzola that the remaining options should be Schedule, Retry, and Archive, and we shouldn't have to unschedule. But I don't know how I feel about losing the history of what happened. Maybe a new feature for down the line should be Migration History?  I can just imagine a user realizing something was wrong with a completed migration and wanting to go look at how it was configured.

@vconzola
Archive as a kebab is a problem because we have a whole list item wrapped in a click event.  So when you click on the kebab, rather than seeing the dropdown you are redirected to the completed migration. Working on getting the kebab to behave like the rest of the buttons, independent of the row click event, but just in case thats not immediately possible... we can either,

change the completed migration name into the redirect to the page
swap a kebab for the tried and true button till this gets resolved

@AllenBW have you tried stopping propagation on the kebab's event handler?  event.stopPropagation() is your friend when you have event handlers on nested elements. https://developer.mozilla.org/en-US/docs/Web/API/Event/stopPropagation

@mturley yes. and about a billon other things.

https://github.com/ManageIQ/manageiq-api/pull/436 is the pr we need for this to work...
Is ready for review from other parties whenever they can spare the cycles

Looks like https://github.com/ManageIQ/manageiq-api/pull/436 has been merged.  I've looked at the new kebab code, and it looks good to me.
In the interest of time, I've gone ahead and taken a look at the CI failure.  We can replace this line with something like
const archiveButton = item.find('a').filterWhere(link => link.text() === 'Archive');

to fix the failing test case

Updated! @michaelkro

🎉


Removed method channel.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 21.77%. Comparing base (ad61234) to head (9bf028c).
Report is 1 commits behind head on develop.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #423   +/-   ##
========================================
  Coverage    21.77%   21.77%
========================================
  Files          297      297
  Lines         9272     9266    -6
========================================
- Hits          2019     2018    -1
+ Misses        7253     7248    -5

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


⚠ PrivateHD has degraded performance

In 39c3f9c, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 9350 ms

Resolved: PrivateHD performance has improved in cefa06e.


Enterprise users can see all the projects that their admin has given to Cody as context (including projects that are in the process of being indexed for embedding, graph, or local context)

Closing this because the multi-repo UX includes a list of all the projects on the instance, and then only "indexing" is keyword search. We'll continue to iterate on UX.


update deployment walk through documentation

When following Deployment Walk Through steps, I noticed that:
-ngsa app uses port 8080 instead 4120
-DS is not getting deployed

file "/loderunner/helm-config.example.yaml" still utilizing port 4120

I missed this issue when I created a new one. The ngsa app port got updated in: #575 but I'm not sure what the DS is for getting deployed


Updates for SDK 1.1.108 release.

Updates for SDK 1.1.108 release.
Fixes to clearing attachments.
Report image layer limits for attachments in vkGetPhysicalDeviceImageFormatProperties().

Fixes #641.

Travis CI failing on latest glslang for some reason. Merging anyway.


angular cli 8.0.3 , nodejs 12.16.1

[Container] 2020/06/30 08:33:42 Command did not exit successfully node --max-old-space-size=4096 node_modules/@angular/cli/bin/ng build --prod exit status 1
270 | [Container] 2020/06/30 08:33:42 Phase complete: BUILD State: FAILED
271 | [Container] 2020/06/30 08:33:42 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: node --max-old-space-size=4096 node_modules/@angular/cli/bin/ng build --prod.  However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out our submission guidelines to understand why we can't act on issues that are lacking important information.
If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template.


Monthly newsletter for February 2021

I put together a draft for the February monthly newsletter and populated it from the repository activities.

[x] collect PRs from stdlib
[x] collect PRs from fpm, setup-fpm and fpm-registry
[x] collect PRs from fortran-lang.org
[x] add link to Fortran monthly call recording
[x] update contributor data (@LKedward)
[x] add call info for next GSoC discussion meeting (@milancurcic)
[x] add updates on classic flang
[x] add updates on LLVM flang
add updates on LFortran (@certik)

Please review and edit if needed. As usual, please add your name to the authors list if you add, edit, or review content.

Thanks for starting! I'll update contributor data tomorrow.

Thanks for starting! I'll update contributor data tomorrow.

Thanks for starting it. Do you think we should mention GSoC to try gather early interest from prospective students? Something like:

This year fortran-lang will be applying as an Org for Google Summer of Code. We started working on the application and the project ideas. If you'd like to help us flesh them out, please join our video call on (Milan TODO). If you're a student and you'd like to help build the Fortran ecosystem, or have a project idea you'd like to work on, please reach out and let us know (how exactly? Milan TODO).

I think this would go in the Events section.

Thanks for starting it. Do you think we should mention GSoC to try gather early interest from prospective students? Something like:

This year fortran-lang will be applying as an Org for Google Summer of Code. We started working on the application and the project ideas. If you'd like to help us flesh them out, please join our video call on (Milan TODO). If you're a student and you'd like to help build the Fortran ecosystem, or have a project idea you'd like to work on, please reach out and let us know (how exactly? Milan TODO).

I think this would go in the Events section.

Regarding news from Classic Flang and LLVM Flang: @AlexisPerry, would you like to provide updates from both Flang projects for the monthly newsletter? We distribute these on the mailing list (131 subscribers), Discourse, and Twitter (604 followers). Flang updates in the newsletter may bring new users, and who knows, maybe even new contributors.
Previously @gklimowicz has been helping with these, but he stepped back and mentioned your name. It would be very helpful if you agreed to do it! :)

Regarding news from Classic Flang and LLVM Flang: @AlexisPerry, would you like to provide updates from both Flang projects for the monthly newsletter? We distribute these on the mailing list (131 subscribers), Discourse, and Twitter (604 followers). Flang updates in the newsletter may bring new users, and who knows, maybe even new contributors.
Previously @gklimowicz has been helping with these, but he stepped back and mentioned your name. It would be very helpful if you agreed to do it! :)

@certik Are there any updates from LFortran? It'd be great if this newsletter can go out today.
I suggest we drop the Flang updates this month, and continue next month if we find a contributor.

Let's drop LFortran also for this month.

Sorry for the delay in response.  I did not realize this was due today.  Since I'm new to this project, haven't learned the workflow yet, and we're on a short deadline, I'll just put my Flang updates here for now and would appreciate it if someone could integrate them into the document for me just this once.  If that's not a workable solution, please let me know how best to contribute and I will do so ASAP. Thanks!
### Classic Flang

There are a number of pull requests out for evaluation.

A total of 12 pull requests were merged in January.

* [PR#932 Do not assume unempty derived types](https://github.com/flang-compiler/flang/pull/932)
* [PR#957 Support Prefetch Directive](https://github.com/flang-compiler/flang/pull/957)
* [PR#947 Fix gcc-10 compilaton issues](https://github.com/flang-compiler/flang/pull/947)
* [PR#948 Expand CI to run with GCC-9/10 and LLVM-9/10/11](https://github.com/flang-compiler/flang/pull/948)
* [PR#949 USE rename should check if renamed sptr is available in the scope](https://github.com/flang-compiler/flang/pull/949)
* [PR#971 Remove dwarfdump_prolog.f90 test since it is dependent on codegen](https://github.com/flang-compiler/flang/pull/971)
* [PR#940 Flang should generate debug location for limited instructions in prolog](https://github.com/flang-compiler/flang/pull/940)
* [PR#977 Update apt data before installing sphinx](https://github.com/flang-compiler/flang/pull/977)
* [PR#751 Fix for len intrinsic returning int*8 in some cases](https://github.com/flang-compiler/flang/pull/751)
* [PR#956 Minor FileCheck pattern fixes](https://github.com/flang-compiler/flang/pull/956)
* [PR#978 Fix the readme to point to the correct flang-dev list](https://github.com/flang-compiler/flang/pull/978)
* [PR#979 Rename direct header to avoid windows conflict](https://github.com/flang-compiler/flang/pull/979)

### LLVM Flang

Recent development updates:

* OpenMP semantic checks: private, firstprivate, lastprivate, Workshare Construct, `DO` loop restrictions
* Detect call to abstract interface
* OpenMP - add task_reduction clause, make reduction clause part of OmpClause
* New Driver - adding support for various options, testing improvements, standard macro pre-definitions, fixed-form detection, CMake improvements
* OpenACC - semantic checks to enforce declare directive restrictions
* Internal subprogram improvements
* OpenMP/OpenACC - Extend CheckNoBranching to handle branching provided by LabelEnforce
* Disallow `INTENT` attribute on procedure dummy arguments
* Module file improvements and bug fixes
* Add tests for procedure arguments with implicit interfaces

Call notes will be sent to the _flang-dev_ email list and also recorded [here]( https://docs.google.com/document/d/10T-S2J3GrahpG4Ooif93NSTz2zBW0MQc_RlwHi0-afY)\
.

Thank you, @AlexisPerry!

Thanks @AlexisPerry, I added the flang updates to the newsletter. One way to contribute content to the newletter is by creating a review comment on the respective section and add the updates using GitHub's suggestion feature:
```suggestion
...
```

I think this is good to go. @awvwgk please merge when ready, and thank you all!

Thanks @AlexisPerry, I added the flang updates to the newsletter. One way to contribute content to the newletter is by creating a review comment on the respective section and add the updates using GitHub's suggestion feature:
```suggestion
...

Thank you so much!  I'll go that route next month.  :-)


Various Bug fixes

What kind of change does this PR introduce?
This PR fixes various bugs:

Second infinite on a layer within a part doesnt get extended
Copy expectedDuration to inserted adlibs
Don't throw error using github branches as packages
Typings
Bugfix: don't die if the previous part doesn't exist anymore
Safeguard for first part(s) being invalid on reset and activate user action
Proper handling of setting the first valid part on activation
Use adlibPrerollDuration when converting adlib to a part
Exception when converting adlib to part if preroll not defined
Guard warning
Infinite pieces started in an autonext part would disappear briefly between the take and the new timeline resolving
Parsing versions
Allow Next:ing past an empty segment.
Bugfix: not able to reset rundown when first part was playing
Remove leftover properties unlimited & onPGMClean
Block alt key default action
Change UI settings to a Meteor-standard
Removes un-used properties from the source layers to clean up the UI and avoid confusions this introduce

41b696ec64d4d16b0567592284d1c9db244e63ae and b033b056f643a910904550235e5b97fed3535196 from this PR have been rewritten and pulled into #193. Hopefully this wont conflict or cause the original commits to be merged, as that will cause some work to be done twice


Limited revision to B cell hierarchy and class definitions

Based on discussions with HIPC panel of expert immunologists, the following changes are proposed.
Existing hierarchy
lymphocyte
--'lymphocyte of B lineage'
----'antibody secreting cell'
------'plasma cell'
-------plasmablast
----'B cell'
------'immature B cell'
------'mature B cell'
------'precursor B cell'
------'transitional stage B cell'
Goal 1:  Introduce subclasses of 'lymphocyte of B lineage' and 'B cell' that bear the mammalian CD19 marker and are taxon restricted.  This will allow annotators in non-mammalian species to use the highest level terms for identifiable B cells in their respective species without concern about whether a CD19 ortholog is expressed in those species.
New hierarchy
lymphocyte
--'lymphocyte of B lineage'
----'B cell'
----'lymphocyte of B lineage, CD19-positive' [only_in_taxon some Mammalia]
------'B cell, CD19-positive' [only_in_taxon some Mammalia]
--------'immature B cell'
--------'mature B cell'
--------'precursor B cell'
--------'transitional stage B cell'
----'antibody secreting cell'
------'plasma cell'
-------plasmablast
Appropriate subsumption and logical definitions will enable inference of a correct polyhierachy (not shown above due).
Textual definitions
'lymphocyte of B lineage'
EXISTING A lymphocyte of B lineage is a lymphocyte that expresses CD19 on the cell surface. An additional defining characteristic is the commitment to express an immunoglobulin complex.
NEW A lymphocyte of B lineage with the commitment to express an immunoglobulin complex.
[not sure how to capture this logically for now]
'lymphocyte of B lineage, CD19-positive'
NEW A lymphocyte of B lineage that expresses CD19 on the cell surface. An additional defining characteristic is the commitment to express an immunoglobulin complex.
'B cell'
EXISTING A lymphocyte of B lineage with the phenotype CD19-positive, CD20-positive, and capable of B cell mediated immunity.
NEW A lymphocyte of B lineage capable of B cell mediated immunity.
'B cell, CD19-positive'
NEW A lymphocyte of B lineage that is CD19-positive and capable of B cell mediated immunity.
Goal 2 Add synonyms and classes to more fully represent plasmablasts
plasmablast (CL:0000980) will receive the following synonyms:
"CD20-negative B cell" (broad)
"CD27-positive, CD38-positive, CD20-negative B-cell" (exact)
A subclass of plasmablast
label 'CD86-positive plasmablast'
Definition "A plasmablast that is CD86-positive" [PMID:20398308]
synonym "CD86-positive, CD20-negative B cell" (broad)
logical definition per the textual definition

relaxed only_in_taxon to 'in taxon' to allow for the possibility that CD19 is more broadly expressed on other vertebrate B cells

Also simplified textual definitions to be more strictly Aristotelian.


[Ext] Insight Report: Tooltip

Description
Fill out the Tooltip insight report from your findings from the audit
The insight report will be part of our decision making framework and is intend to:

Document all findings from the component audit
Confirm as many component details as possible
Mitigate component inconsistencies across Figma, Mobile and Extension

Include your thoughts on component name, description, api and any comments or topic to discuss relating to the component or it's make up. We will review the audit and insight report in our Wednesday technical sync to finalize the details of the component for all platforms.
Technical Details
The insight report should include the following for the component

name
description
variants/props
requirements (optional)
discussion/questions (optional)

Acceptance Criteria

name, description variants/props is filled out and matches with other platforms where possible

References

FigJam
Read exercised #05 Identify Existing Paradigms in Design and Code and #06 IdentifyEmergingandInteresting Paradigms in Design and Code in the Design System in 90 Days workbook

Hey team! Please add your planning poker estimate with Zenhub @Akatori-Design @brianacnguyen @garrettbear

Completed https://www.figma.com/file/KP10I7OHiuUsGZ53xAgZTj/Popover%2FTooltip-Audit?node-id=0%3A1&t=PN3ElOc15sMY29NY-1


Add util to get version from Creek jar file.

Coverage decreased (-0.6%) to 98.824% when pulling 8e368a6469c0d0acac1aa9a7848443afce483844 on jar_ver into 796d504a21679c475bfe7af48e4cde89a857cb2c on main.


Remove Documentation-Needed label from issue management

PR Summary
From now on, no code PR should be merged without, at bare minimum, a relevant issue being created in PowerShell/PowerShell-Docs.
In the future, we may introduce additional process around documentation requirements for code changes, but for now this is an incremental change that makes PowerShell-Docs the source of truth for doc debt/gaps.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[x] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

You need to update https://github.com/PowerShell/PowerShell/blob/8a0abf459c31ce99d6ecc81ebb165179fe192d28/docs/maintainers/best-practice.md#review-prs


feat(payment): PAYPAL-1545 added translation for PaypalCommerce RatePay payment component

What?
Added translation for PaypalCommerce RatePay payment component
Why?
To translate RatePay component form fields strings
Testing / Proof
...
@bigcommerce/checkout

Hey @andriiVitvitskyi1990 can you please attach some testing proof to the PR.


empty space at bottom on first start

When starting the view controller the first time, I have an empty space at the bottom.
When resizing or opening the keyboard, the empty space is gone.
After same researching I found the problem:
In jsq_updateCollectionViewInsets, the topLayoutGuide does not seem to be fixed.
According to http://stackoverflow.com/questions/19140530/toplayoutguide-in-child-view-controller
the topLayoutGuide should be accessed in viewWillLayoutSubviews.
So adding this code in my viewcontroller fixed the issue for me:

(void)viewWillLayoutSubviews
{
[super viewWillLayoutSubviews];
[self jsq_updateCollectionViewInsets];
}

I hope this info might be helpful to someone.
I am new to github and not familiar with pull requests. If you guide me through I could do one.

This is pretty old, should be fixed with some other recent changes.
Also, haven't had any other reports of this.
Closing out.

I am having the same issue, though.
First load -> extra space on bottom under last message (regardless of how big it is).
When showing then hiding keyboard, the space is gone.
Another note is this extra space is also affecting the scroll bar. In other words, when scrolling, you can see that even the scroll bar stops at this space. It's not really an "extra space", but the view ends there.

Is there a solution in swift for this issue? @plenio @jessesquires @quanvo87 @atroutt @ghazel

https://github.com/jessesquires/JSQMessagesViewController/issues/1850 Take a look at this issue

https://github.com/jessesquires/JSQMessagesViewController/issues/1850

I have this issue too!

I have this issue too


Removing min.js file from bower's main property

Avoid having both the minified and non-minified files imported (see: bower.json-spec) when using the library.

Thanks for the contribution. Update to v0.0.7 to incorporate this change.

@ninjatronic Thanks to you for the lib.


Added retryable errors.

Looks good. Please get some feedback from the DNS team before merge.

Can we get some input here? Are there any retryable errors that you know of and we are forgetting?
/cc @benvitale @blowmage @stephenplusplus

The only guidance we've gotten for retries is a 500 or 503 response, and an error message reason for [https://github.com/GoogleCloudPlatform/gcloud-ruby/blob/5bc3364ec4b962b90f184c6fa96a047d0c1a14e0/lib/gcloud/backoff.rb#L63](exceeding rate limits).

Thanks @blowmage, I added the exceeding limits.

Here are the codes that we use: https://github.com/GoogleCloudPlatform/gcloud-node/blob/058d7623ea3d54c0efc7db4757510fd53eabc492/lib/common/util.js#L271

@stephenplusplus 429 is the error code for rateLimitExceeded and userRateLimitExceeded, right? Is there any reason why you are double checking first via code and then via error message?

This code has been around for a while, so I'm a little rusty on why we went with the specific codes and ways of checking. But, the code check is when a response has the HTTP status code of 429, 500, 502, or 503. The other check isn't actually checking the HTTP status message, but a message that is contained in JSON response body errors object. I'm not sure if a situation exists where the status code could be 2xx, but the response body would return errors that occurred, but this check would handle it.

Jacob, David for additional comments

Retrying on 500 seems valuable; as this error could indicate a problem
between Apiary and our backend server.
I can't think of other cases. We generally have retry-loops around our
Spanner transactions, so if our server says things are errors, they are
unlikely to be temporary errors that could succeed if retried.
On Wed, Mar 2, 2016 at 7:33 PM, Martin Derka<EMAIL_ADDRESS>wrote:

Merged #700 https://github.com/GoogleCloudPlatform/gcloud-java/pull/700.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/gcloud-java/pull/700#event-575538162
.


Verify test for getConversations method

Ensure tests are written properly and successfully pass once the getConversations method is debugged.

@vherrin: Any word from the Dialog team? I'll also follow-up in our email chain.

Looks like the timestamp of the received conversation history is still 17 hours in the future. Waiting to hear from the Watson team about a resolution to the problem.

This seems to be a problem with production environment VMs and probably won't be fixed anytime soon. I'll go ahead and change the getConversations method to adjust the time so that we can move forward on resolving this problem.

Complete with 6fbf2c6b98c8ef2ee652f80cdf2d6e6a576de639

you can set/view the timezone for a particular dialog service
in the XML or applet in Account-->Settings
and the dates you provide in this API endpoint are assumed to be in the same timezone
so no need to specify timezone or worry about it in any way

@sanjayko That's excellent to know, thank you!
It would be really helpful if the Swagger documentation was updated to note that assumption about the date_from and date_to parameters.
We'll back out the changes from 6fbf2c6 and add comments about the date_from and date_to arguments to make the timezone assumption clear to users of the SDK.

yes, Have requested the dialog and documentation team to update.

Thanks, @sanjayko! We really appreciate that.

Complete with 48317cba2319ad89c4b6599cf3ec727a14bf7caa


LibWeb: Remove set_event_characteristics()

These methods were overriding properties specified by the EventInit property bags in the constructor for WheelEvent and MouseEvent.
They appear to be legacy code and no longer relevant, as they would have been used for ensuring natively dispatched events had the correct properties --- This is now done in separate create methods, such as MouseEvent::create_from_platform_event.
This fixes a couple WPT failures (e.g. in /dom/events/Event-subclasses-constructors.html)

it seems that the change breaks mouse-events.html where mouseover event no longer bubbles:
798/1176: Text/input/UIEvents/mouse-events.html
Test failed: /Users/kalenik/ladybird/Tests/LibWeb/Text/input/UIEvents/mouse-events.html
--- /Users/kalenik/ladybird/Tests/LibWeb/Text/expected/./UIEvents/mouse-events.txt
+++ /Users/kalenik/ladybird/Tests/LibWeb/Text/expected/./UIEvents/mouse-events.txt
@@ -1,6 +1,5 @@
    > move pointer over #inner
 mouseover target.id=(inner) currentTarget.id=(inner), relatedTarget.id=(body)
-mouseover target.id=(inner) currentTarget.id=(outer), relatedTarget.id=(body)
 mouseenter target.id=(inner) currentTarget.id=(inner), relatedTarget.id=(body)
 mouseenter target.id=(outer) currentTarget.id=(outer), relatedTarget.id=(body)
 > move pointer over #outer
@@ -5,7 +4,6 @@
 mouseenter target.id=(outer) currentTarget.id=(outer), relatedTarget.id=(body)
 > move pointer over #outer
 mouseout target.id=(inner) currentTarget.id=(inner), relatedTarget.id=(outer)
-mouseout target.id=(inner) currentTarget.id=(outer), relatedTarget.id=(outer)
 mouseleave target.id=(inner) currentTarget.id=(inner), relatedTarget.id=(outer)
 mouseover target.id=(outer) currentTarget.id=(outer), relatedTarget.id=(inner)
 > click document.body

Yes, it turns out there are some internal events created with MouseEvent::create() instead of create_from_platform_event(), so this doesn't fully work. :(


unbound: clean up references to legacy code, use mvc instead. also minor style fix

Migrating to MVC means we can use the existing get/set API calls without having to manually manipulate the legacy configuration.
This PR also adds a migration for the legacy unbound->forwarding configuration.
I'm not sure what the original intent behind https://github.com/opnsense/core/blob/master/src/wizard/system.xml#L158-L159 was, but i'm removing it here.

Just quickly up front: the wizard tries to set non-forward mode on reconfigure to ensure consistency with a default configuration. If we need it or simply discard I’m not sure, but it’s more work than necessary most likely to emulate it.

merged, thanks!


CY-317: Add more Alerts

CY-317: Add below alerts and it's filter macro

Name
Cron

AD - Password Change Outside Working Hour
Runs every day

Palo Alto Firewall - Commits
Runs every 15 minutes

O365 - Security Compliance Alert
Runs every hour

Email- Hourly Increase In Emails Over Baseline
Runs evert hour

Email- Daily Spam Email
Runs every day

Authentication - Successful VPN Login Outside Home Country
Runs every hour

Cisco IOS - New Connection For User
Runs every 30 minute

Cisco IOS - Device Failed Login
Runs every 30 minute

All the suggested changes are done.


Pkg 4023: v12.3 - initial

{package} {version} {:snowflake:}
Destination channel: {Snowflake | defaults}
Links

{ticket_number}
Upstream repository
Upstream changelog/diff
Relevant dependency PRs:

...

Explanation of changes:

...

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_feg7a3zf8n/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:344: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:344: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:344: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:289: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_99wgzstjc3/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:344: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:289: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:344: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:344: missing_license_family: The recipe is missing the about/license_family key.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_6fl884wpq4/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:344: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:289: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:344: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:344: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_73jdk5s4mf/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:345: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:345: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:290: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:345: missing_dev_url: The recipe is missing a dev_url
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_93fbzygcgd/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:345: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:345: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:345: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:290: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_9d0w662p1q/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:344: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:344: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:289: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:344: missing_license_family: The recipe is missing the about/license_family key.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_592w1ocwvz/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:344: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:289: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:344: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:344: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_201vu81wk8/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:345: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:345: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:345: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:290: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_cev6qcbw4x/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:344: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:344: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:344: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:289: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_f4dwcr_3jc/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:344: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:344: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:289: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:344: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_55j8_62r4b/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:344: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:289: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:344: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:344: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_0a0l_1dos0/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:344: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:289: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:344: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:344: missing_license_family: The recipe is missing the about/license_family key.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_a3c_elz3vj/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:349: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:294: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:349: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:349: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_0dyjf7efqa/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:351: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:296: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:351: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:351: missing_dev_url: The recipe is missing a dev_url
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_earl8o_xkw/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:349: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:349: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:349: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:294: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_a1d6dampwu/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:349: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:349: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:349: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:294: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_09x2q80dj2/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:349: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:294: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:349: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:349: missing_dev_url: The recipe is missing a dev_url
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_f462mw6k0l/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:352: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:352: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:352: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:297: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_a9els_1yyr/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:352: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:297: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:352: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:352: missing_license_family: The recipe is missing the about/license_family key.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_336g2hsnkw/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:352: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:352: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:352: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:297: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_15cha6_pno/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:352: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:352: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:297: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:352: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_fc2moenvjf/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:352: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:352: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:352: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:297: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
===== Final Report: =====
5 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_17iaksotn2/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:352: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-aarch64": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:96: host_section_needs_exact_pinnings: output "cuda-nvcc-dev_linux-ppc64le": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: output "cuda-nvcc-impl": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:352: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:58: missing_tests: output "cuda-nvcc-tools": No tests were found.
clone/recipe/meta.yaml:352: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:1: patch_must_be_in_build: patch must be in build when source/patches is set.
clone/recipe/meta.yaml:297: missing_tests: output "cuda-nvvm-dev_win-64": No tests were found.
===== Final Report: =====
5 Errors and 5 Warnings were found


Any plans to make Order placement via socket connection?

Would be great to hear from you on order placement via socket connection!
Thank you

You're right

Great news! have an approx ETA on this feature?)

Released in version 1.7.0. Thank you for your patience.


Performance Overlay hides App with Grey Screen

Steps to Reproduce

When activating the Performance Overlay in Profiling Mode while using an iPad, the grey overlay takes the entire screen and I can't use the app anymore. Whats the problem here?

Expected results:
I expected to see my app with a performance overlay, not a grey screen.
Actual results:
A grey screen with a performance overlay.

Logs

No issues found! (ran in 3.8s)

[✓] Flutter (Channel stable, 2.2.3, on macOS 11.5.1 20G80 darwin-x64, locale de-DE)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.2)
[✓] Connected device (2 available)

Hi @Wizzel1
Thanks for filing the issue
Can you please provide a screenshot and a minimal code sample?
I just tried the on the stable channel. it looks fine in profile mode

minimal code sample
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      showPerformanceOverlay: true,
      title: 'Material App',
      theme: ThemeData.dark(),
      home: Home(),
    );
  }
}

class Home extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Material App Bar'),
      ),
      body: Center(
        child: Container(
          child: Text('Hello World'),
        ),
      ),
      floatingActionButton: FloatingActionButton(
        child: Icon(Icons.add),
        onPressed: () {},
      ),
    );
  }
}

preview

flutter doctor -v
[✓] Flutter (Channel stable, 2.2.3, on macOS 12.0 21A5304g darwin-x64, locale en-GB)
    • Flutter version 2.2.3 at /Users/tahatesser/Code/flutter_stable
    • Framework revision f4abaa0735 (6 weeks ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/tahatesser/Code/SDK
    • Platform android-31, build-tools 30.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/SDK
    • Java binary at: /Users/tahatesser/Code/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment Temurin-11.0.12+7 (build 11.0.12+7)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode-beta.app/Contents/Developer
    • Xcode 13.0, Build version 13A5212g
    • CocoaPods version 1.10.1

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

[!] Android Studio (version 2020.3)
    • Android Studio at /Users/tahatesser/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/203.7583922/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] VS Code (version 1.59.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.25.0

[✓] Connected device (4 available)
    • Taha’s iPad (mobile) • 00008020-000255113EE8402E            • ios            • iOS 15.0
    • iPhone 12 (mobile)   • 7CC8A747-CD39-4C42-871C-2D1CCEAE2AE2 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-0 (simulator)
    • macOS (desktop)      • macos                                • darwin-x64     • macOS 12.0 21A5304g darwin-x64
    • Chrome (web)         • chrome                               • web-javascript • Google Chrome 92.0.4515.131

! Doctor found issues in 1 category.

Thank you

Actually I found that the issue has to be on my side. There seems to be something wrong with the state of my app as I am getting an error "this stream has already been listened to" when I activate the overlay.

Hi @Wizzel1
Can you please provide a complete reproducible minimal code sample, and complete flutter run --verbose logs running the minimal code sample?
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


MSAL library state mismatch issue

Please follow the issue template below. Failure to do so will result in a delay in answering your question.

Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[x]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Important: Please fill in your exact version number above, e.g<EMAIL_ADDRESS>We are using below  version of msal library
https://alcdn.msauth.net/browser/2.6.1/js/msal-browser.js
Framework
Description:
We are using msal OAuth2.0 + PKCE implementation for B2C integration with Angular SPA.  Our company has UI/UX design which you can see from here https://beta-aemtest.amtrak.com/home.html
On B2C login/enroll page, we want to allow user be able to flip between signin and signup. The problem is: if flip, the token that is sending back to our page is rejected due to state mismatch issue.
We want to know the options to resolve this issue.  Is there any way to catch state mismatch error?  What's the function we need to invoke if we have to implicitly re-send the request without prompting user to enter username/password
Error Message:
state mismatched error is received
Security

[ ] Is this issue security related?  Maybe

Regression

[ ] Did this behavior work before? No, this is our first implementation
Version:

MSAL Configuration
// Provide configuration values here.
// For Azure B2C issues, please include your policies.

Reproduction steps

Go to https://beta-aemtest.amtrak.com/home.html
Click on "Join"
On B2C page, click on "Sign In" blue button
Login with test account
On Amtrak home page, you will see user is not login and state mismatch error when inspect the browser error

// Provide relevant code snippets here.
// For Azure B2C issues, please include your policies.

## Expected behavior

## Browsers/Environment
 Chrome

@zhangxAmtrak This is happening because we do not support switching policies mid-stream. We recommend you resolve this in one of 2 ways:

Use a single policy for both sign up and sign in
When a user changes the policy, first redirect back to your app and have your app call loginRedirect again with the new policy

@tnorling After the user lands on the home page with the state mismatch error, a subsequent user action for login, is handled by the msal plugin and it logs the user in. What is the expected behavior for msal here? If this the current flow of msal to login the user on the user action is acceptable, then I assume handling the state_mismatch error to retry the msal login action is good too and a future fix from msal to allow retry in this case can be expected too?

@kalyansury Not sure I understand what you're asking. The issue here is that msal makes a request out to policy "signin" and receives a response from policy "sign-up", resulting in a mismatch. To clarify, it's fine to catch the state mismatch error and make a new login call to the other policy but you should not try to process the response from the first login call. A cleaner solution would be: app calls policy "signin" -> user selects policy "sign-up" -> custom policy returns to app with a meaningful error -> app catches this error and calls policy "sign-up".
As long as the policy that msal calls is the same as the policy that issues the token there should not be an issue.


System test over http

This PR switches from MockMvc toTestRestTemplate for System Tests. Another option would be using RestAssured (if verifying the HTTP responses is required).

Thank you!


fix(GUI): pass empty string fallback to middle-ellipsis filter

We ensure that the middle-ellipsis filter doesn't explode when it's
passed an undefined value by passing a default empty string in those
template functions.
Change-Type: patch

Would modifying the middle-ellipsis filter itself be a more robust solution? *shrug*

This can be closed now, right @Shou?


unwrap method

Moved unwrap method in Result class to make it more C++ like and also consistent with Rust .unwrap() function

@alexcrichton Please, take a look ;)

Thanks!


DataFrame (Polars) support

https://github.com/emilk/egui/discussions/2222
Is this possible? I am actually rebuilding a project I did in Python with Streamlit. Gives great possibilities for data dashboards. Perhaps worth looking into.

you need to format the data yourself. egui already has examples in demo for table/grid, polars dataframe implements iterators / indexing etc.. and you can use it as the source data for table / grid widgets. look at https://egui.rs for the table demo and it will also have a source link at the bottom of the demo widget.

this is not a feature request btw. just a question.

this is not a feature request btw. just a question.

Well, I asked if it was possible to support so you might consider my question elevated into a feature request. Anyway thanks, I have already been working on a general dataframe table but new to Rust and struggling (also with Polars btw).

But since you say I have to format the data myself, could you at least give some info why the console is able to pretty-print a polars dataframe but it seems egui doesn't?

But since you say I have to format the data myself, could you at least give some info why the console is able to pretty-print a polars dataframe but it seems egui isn't?

These kinds of questions are better answered in discord. Both egui and plars got their own discord servers where you can get help.
Anyway,  this could be an issue with fonts. First,  terminal fonts are monospace, so the columns always align. I think ui label doesn't do that. Second, polars could be printing different strings in egui vs terminals based on the env as seen here https://pola-rs.github.io/polars/src/polars_core/fmt.rs.html#353 . In particular,  the chars used for egui dont seem like ... or === which seem to be used for console. Because egui already supports those chars.
I am on mobile, so hard to test atm.

An integration between Polars and Table is best left to a 3rd party crate


Remove singleton for VFIO container

already merged such a fix.

This PR also adds some more ::Ptr type aliases. Lets merge those at least.

I think this is bad practice. See https://www.fluentcpp.com/2019/01/22/pitfalls-of-aliasing-a-pointer-in-modern-cpp/
I see no advatage in aliasing pointer types. If you know some please share.


kahoot updated their system again

I just started getting this error today:
request error: { Error: socket hang up
did kahoot change their system again?

Looks like your PR fixed it! Thanks :)

Looks like your PR fixed it! Thanks :)
Do you mean to say that the bug is fixed? The issue is closed...

Yes, the bug is fixed
Sent over the interblag from a GUI.
https://github.com/theusaf
https://shortr.github.io/?llorkcir

On Dec 19, 2019, at 8:26 AM, Maxim<EMAIL_ADDRESS>wrote:

Looks like your PR fixed it! Thanks :)
Do you mean to say that the bug is fixed? The issue is closed...
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.


Flutter Project Causing Entire System To Lagg Severely.

Steps to Reproduce

I installed flutter SDK on my PC at work via android studio's "install flutter sdk" button, and booted a fresh flutter project inside of android studio 4.0. Immediately my entire system seems to freeze, as if there is a massive memory leak. It spends literal minutes "Analyzing". Anytime I boot a flutter project, the system comes to a halt, and again immediately solves itself if android studio is closed.
It's certainly not a system resources issue, I've been doing android studio development with java for months on this computer with no issues. Task Manager also shows no excessive memory or CPU usage.
Logs

flutter doctor -v:
[√] Flutter (Channel beta, 1.19.0-4.1.pre, on Microsoft Windows [Version 10.0.17763.1282], locale en-US)
• Flutter version 1.19.0-4.1.pre at C:\flutter
• Framework revision f994b76974 (2 weeks ago), 2020-06-09 15:53:13 -0700
• Engine revision 9a28c3bcf4
• Dart version 2.9.0 (build 2.9.0-14.1.beta)
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
• Android SDK at C:\Users\timothy.bender\AppData\Local\Android\sdk
• Platform android-29, build-tools 29.0.3
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
• All Android licenses accepted.
[√] Android Studio (version 4.0)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 46.0.2
• Dart plugin version 193.7361
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
[√] Connected device (1 available)
• moto g 7 play • ZY326NQKG7 • android-arm • Android 9 (API 28)
• No issues found!

Hi @TimothyBender
Please check your system resources when running the app and try switching to stable channel or dev channel
Can you please provide your flutter run --verbose and a complete reproducible minimal code sample
Thank you

Without additional information we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Bump travis image to Trusty.

will TBR on greenish CI.

hmm, I didn't see the "too many open files" thing in several CI runs - then just started seeing it last night. more work to be done there, I guess.


Add bare metal OS requirements

Also update the NPM arg so we can run make server.

/approve
/cherry-pick release-0.18

/lgtm


Fix failing on_failure export tasks method

Fix failing on_failure csv tasks method
Refactor csv tasks file - introduce ExportTask - basic celery task class for exports

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-5924 Fix problem with sending export failed notification


[BugFix] Use default filesystem to manipulate jdbc driver

For files with : in filenames (e.g. /path/to/jdbc_drivers/a:b.jar), we will create an HDFS filesystem.
But a local filesystem is expected.
This is because of is_posix_uri returning false if filename contains :
inline bool is_posix_uri(std::string_view uri) {
    return (memchr(uri.data(), ':', uri.size()) == nullptr) || starts_with(uri, "posix://");
}

To resolve this issue, this PR uses default FS to conduct related operations.
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[x] Yes, this PR will result in a change in behavior.
[ ] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 0 / 10 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/runtime/jdbc_driver_manager.cpp
0
10
00.00%
[61, 91, 92, 93, 94, 97, 98, 107, 108, 142]

Can we use normally when jdbc driver url is hdfs:// or http://

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 0 / 11 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/runtime/jdbc_driver_manager.cpp
0
11
00.00%
[61, 90, 91, 92, 93, 97, 98, 107, 108, 109, 143]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

Can we use normally when jdbc driver url is hdfs:// or http://

url is used to download driver, which not influenced by this PR

@mergify backport branch-3.2

@mergify backport branch-2.5
@mergify backport branch-3.0
@mergify backport branch-3.1

@mergify backport branch-3.1

@mergify backport branch-3.0


Error code: 429 - Whisper AI (Free Tier) Issue and Potential Solution

Hi,
I ran into an issue that I think may have been addressed in issue 101 and 84 before.
Details:

I am using a free OpenAI account.
I added my API key to the overide.yaml file (the key is sandwiched between single quotes)
I am using python 3.11.7
OS: Windows 11
I am not using this on my main PC at the moment. I downloaded this by extracting the .zip file. I did not download the executable hosted on Google Drive.

Please let me know if you think using the .exe would provide data in the right window of the GUI.

Functionality
When I execute the command python main.py in my command prompt, the GUI opens successfully. The console displays the following information:
[INFO] Listening to sound from Microphone: #29 - Microphone (REDACTED)
[INFO] Adjusting for ambient noise from Default Mic. Please make some noise from the Default Mic...
[INFO] Completed ambient noise adjustment for Default Mic.
[INFO] Listening to sound from Speaker: #25 - Speakers (REDACTED) [Loopback]
[INFO] Adjusting for ambient noise from Default Speaker. Please play sound from Default Speaker...
[INFO] Completed ambient noise adjustment for Default Speaker.
[INFO] Whisper using GPU: True
READY
All things seem to start fine. The 'issue' comes when I attempt to use the application in a conversational setting. In the GUI, the window on the

left displays a transcription (not always correctly) of what was picked up by the microphone.
right displays "Welcome to Transcribe" at the top, and no text/response is populated. Other than the banner at the top, the window is completely blank.

After the application interprets what was picked up by the microphone, the command prompt displays the response:
Error when attempting to get a response from LLM. Error code: 429 - {'error': {'message': 'You exceeded your current quota, please check your plan and billing details. For more information on this error, read the docs: https://platform.openai.com/docs/guides/error-codes/api-errors.', 'type': 'insufficient_quota', 'param': None, 'code': 'insufficient_quota'}} [INFO] Exiting gracefully..
When I view my usage details at https://platform.openai.com/usage, the balance displays $0.00. I take this to mean that generating 'responses' requires a paid account. FWIW, I am not too surprised by this.
Items of Consideration

It may be helpful to see something in the README.md addressing response generation not displaying without a paid OpenAI/Whisper API key.

This is your project. I am not telling you how to run it. I just wanted to provide a way of getting ahead of this question as this project becomes more popular.

Have you considered using other open source models?

When attempting to identify something that could leveraged to avoid paying for Whisper AI, I initially found https://github.com/mudler/LocalAI.
This may be useful https://github.com/sindresorhus/awesome-whisper.
I also found https://github.com/ideasman42/nerd-dictation, which uses https://github.com/alphacep/vosk-api. I am not seeing anything about pricing. There is a chance that this could be a truly 'FREE' workaround.

These may be helpful https://github.com/projecte-aina/oTranscribe-plus-desktop and https://github.com/oTranscribe/oTranscribe.

Would it be possible to edit/comment on the text that is displayed in the left window of the GUI?

To allow users the chance to correct some of the dialogue that may not have been recorded accurately.

When I view my usage details at https://platform.openai.com/usage, the balance displays $0.00. I take this to mean that generating 'responses' requires a paid account. FWIW, I am not too surprised by this.

You are correct. Generating a response requires openAI credits. If your usage is limited, a couple of hours a day, you can get by with spending under USD 5 a month.
Thank you for directions. I will look into the suggestions.

@BetaMaxHeadroom
https://github.com/vivekuppal/transcribe/pull/119
Thoughts, comments, suggestions, commits in the PR are all welcome

Would it be possible to edit/comment on the text that is displayed in the left window of the GUI?
To allow users the chance to correct some of the dialogue that may not have been recorded accurately.

This will be included in an updated version of the GUI soonish.
Any further feedback on the user Interface is appreciated

Started a discussion about User Interface
https://github.com/vivekuppal/transcribe/discussions/121

Happy holidays. Thank you again for making such an incredible tool. I had another question.
Please spend time with your family instead of responding to me today. Don't spend time on this. I just thought of it now, and I wanted to ask this before I forgot about it. This is likely something I should figure out on my own. I mostly just want to make a note.

Would it be possible to use a different AI solution? I have recently discovered https://www.perplexity.ai/, and the responses seem better than the responses generated by text from OpenAI (on average).

Would I simply need to use the perplexity API key (in lieu of the OpenAI API key) to use perplexity? Or, is there something else that I would need to do?

Happy holidays.
Good suggestion on Perplexity AI.
There are a multitude of potential solutions for LLM responses

A local RAG / LLM implementation, E.g. Mistral
Perplexity AI
Azure hosted OpenAI

For Perplexity, would have to make the following changes

Create a new section in parameters.yaml for the specific LLM and store the key there. Would have to plumb the api key appropriately to the necessary parts of the code
Make changes in the class class GPTResponder: in gpt_responder.py file. This class currently interacts with chatgpt, make changes to have it interact with Perplexity AI instead.

Azure Hosted OpenAI I believe should be simple, just need to work out the mechanics of setting it up.
Local RAG / LLM implementation I anticipate would be fairly engaged and might take some doing.

Azure Hosted OpenAI I believe should be simple, just need to work out the mechanics of setting it up.

Should be able to use Azure Hosted OpenAI or Perplexity with relative ease with the latest code base.
Add the following 2 parameters to override.yaml file
OpenAI:
  api_key: 'API_KEY_FOR_THE_PROVIDER'
  base_url: 'BASE_URL_FOR_PROVIDER'

For OpenAI base_url is https://api.openai.com/v1

The proposal to incorporate editing of transcription has been incorporated into the product.
The proposals to have other features like a local rag etc, will be considered for future.


Full copy?

lol
even the readme have you copied from @lucasbesen repo?
https://github.com/lucasbesen/react-kanban-dnd

Honestly, I don't remember. I tried to use a lot of kanban like libs, but they're very limited for my purpose.
I really don't understand the problem here. Isn't that repo under MIT licence?
Feel free to use any of them, anyway you want.

Sorry, I haven't catch that you are talking about the entire repo. I was thinking about the README.
Even I could copy and do "whatever" I want (MIT) with that repo, there is no copy here, the code is mine all the way. :)
One of the purpose with this repo is to having fun. Copy is not fun.


I found the path is not correct for the case of the C drive.

The following the what i get:

Selected file: Some("\\?\C:\Users\nil_l\Documents\DSeeTem\minifiles.ini"),
Selected file: Some("D:\Amesim\LMS_RLM_Server\LMS.lic")
Selected file: Some("E:\rust_workspace\egui-test\Cargo.toml")
Selected file: Some("F:\nil_Blog\nil_all.bib")

I wonder what might be causing this?

Hi, thanks for your issue!
This is actually the correct behavior since std::fs::canonicalize is used to generate the absolute path from relative paths.
See the Rust Docs:
https://doc.rust-lang.org/std/fs/fn.canonicalize.html#
And the Windows Docs:
https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#win32-file-namespaces
However, I'm currently unsure why this only happens with the C directory. I'll have to take a closer look.
Although I'm not sure whether I should keep using std::fs::canonicalize and instead also allow relative paths to be used.

Thank you very much for your reply, your work has helped me a lot.

Thank you very much for your reply, your work has helped me a lot.

I'm glad I could help you out :D
Let me know if you have any other bugs or features requests!

I have now fixed that not every path on Windows has the \\?\ prefix and not every path has been canonicalized.
I will also add the feature that fs::canonicalize can be disabled to be able to use relative paths and prevent the prefix on Windows.