Update cookie auth docs to fix missing links

Updated the <seealso> tags to <see> tags so that the links will show up. Currently, anything on the page with <seealso> tags is not displayed.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

aspnet-core/xml/Microsoft.AspNetCore.Authentication.Cookies/CookieAuthenticationOptions.xml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@Rick-Anderson is seems like these have already been updated in the source code, why haven't those changes been synced here automatically? https://github.com/dotnet/aspnetcore/commit/d34dc80e02161369908d8560f550e6e2822807b3

@scottaddie  do you know who is takes care of API updates?

I think it's because  #164 has not been merged. cc @v-alje

The pull request has been merged to master.

@v-alje  @scottaddie  why didn't  #164  contain CookieAuthenticationOptions.cs ?

closing as this was fixed at the source.
@rmarskell  thanks for the PR, sorry we were so slow to respond. We'll try responding more quickly in the future.

@rmarskell thanks for the PR, sorry we were so slow to respond. We'll try responding more quickly in the future.

All good. I had totally forgotten about this anyway. 😅


forge verify-bytecode should not require Etherscan API key

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (f2518c9 2024-08-06T00:19:05.428689000Z)
What command(s) is the bug in?
forge verify-bytecode
Operating System
macOS (Apple Silicon)
Describe the bug
This is a bug report, but it's possible that it's a misunderstanding.
The purpose of forge verify-bytecode is to check whether the contract source code in a local repo matches the bytecode deployed on chain at a specific address. To achieve this, forge could simply compile the contract (using the local compiler, optimizer, etc. configurations), then simulate deployment, then compare the result with the on-chain bytecode.
However, when I run this command I keep getting Etherscan API key is required for verification. Why is Etherscan required for verifying the contract bytecode? Since compiler parameters could be read from foundry.toml, and constructor arguments can be provided by the user, Etherscan should be optional.
Original feature request: https://github.com/foundry-rs/foundry/issues/6893
Original implementation: https://github.com/foundry-rs/foundry/pull/7319
cc @mds1 @yash-atreya

I believe the Etherscan API key is required to also verify the init code, which is harder to fetch than runtime code, therefore it's fetched from Etherscan. The reason you have to also verify the actual initcode used is because malicious initcode can e.g. set storage slots that shouldn't be set, then still return the same runtime code. So only verifying runtime code is not a sufficient safety guarantee.
https://github.com/foundry-rs/foundry/pull/8510 will add a feature to skip initcode verification, and when using that I'd assume you don't need the etherscan API key, but cc @zerosnacks @klkvr to confirm

right, we need etherscan API to be able to fetch contract creation transaction. Knowing creation tx allows us to simulate local creation code execution at the needed block to later compare its result with on-chain runtime code

Marking as not planned given the conversation above, the Etherscan API is a hard requirement.
Please note that in https://github.com/foundry-rs/foundry/pull/8510 we are adding support for additional block explorers, some of who do not require an API key.

The reason you have to also verify the actual initcode used is because malicious initcode can e.g. set storage slots that shouldn't be set, then still return the same runtime code.

That makes sense, thank you! I'd like to use this command to verify a proxy's implementation contract, so storage is not relevant. But I agree it's best to default to full verification.

https://github.com/foundry-rs/foundry/pull/8510 will add a feature to skip initcode verification

Looking forward to it!


feat: OPTIC-3: Enable users to submit and pause their lead time by returning to the dm list

PR fulfills these requirements

[X] Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
[ ] Tests for the changes have been added/updated (for bug fixes/features)
[ ] Docs have been added/updated (for bug fixes/features)
[X] Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
[X] Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)
(check all that apply)

[ ] Product design
[X] Frontend

Describe the reason for change
An option submit/update and exit the stream to stop lead time from running on
What does this fix?
feature
What is the new behavior?
you are able to submit and not load another task and instead return to the datamanager list
What is the current behavior?
if you want to take a break you would have to close the window
What libraries were added/updated?
N/A
Does this change affect performance?
no
Does this change affect security?
no
What alternative approaches were there?
There are likely numerous methods for passing information to the LSF SDK. However, since we were already utilizing query parameters in the 'submit' function, it made sense to continue using this approach for passing a temporary flag to the SDK. This method is convenient because it avoids interfering with the existing chain of functions that have been scaffolded between the two stores.
What feature flags were used to cover this change?
fflag_feat_front_prod_e_111_annotator_workflow_control_short
Does this PR introduce a breaking change?
(check only one)

[ ] Yes, and covered entirely by feature flag(s)
[ ] Yes, and covered partially by feature flag(s)
[X] No
[ ] Not sure (briefly explain the situation below)

What level of testing was included in the change?
(check all that apply)

[ ] e2e
[ ] integration
[ ] unit

Which logical domain(s) does this change affect?
(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)

Codecov Report
Patch coverage: 24.48% and project coverage change: -0.07% :warning:

Comparison is base (41ae765) 65.20% compared to head (b11699c) 65.14%.
Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1541      +/-   ##
==========================================
- Coverage   65.20%   65.14%   -0.07%
==========================================
  Files         442      442
  Lines       28233    28262      +29
  Branches     7377     7389      +12
==========================================
+ Hits        18410    18411       +1
- Misses       9823     9851      +28

Files Changed
Coverage Δ

src/tags/object/AudioUltra/model.js
83.91% <ø> (ø)

src/tags/visual/View.js
92.30% <ø> (ø)

src/components/BottomBar/Controls.js
29.52% <18.18%> (-9.15%)
:arrow_down:

src/mixins/Visibility.js
77.77% <50.00%> (-0.61%)
:arrow_down:

src/regions/Result.js
79.47% <100.00%> (ø)

src/tags/control/Choices.js
74.39% <100.00%> (ø)

src/utils/feature-flags.ts
100.00% <100.00%> (ø)

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


M3 components should have rippleEnabled when clickable

For instance if a view is clickable it should have the ripple enabled. At the same time if we want to turn it off, respectively on we can still use the ripple_enabled attribute

That is indeed useful in some cases. Nice!


Introducing Dropwizard Guru on Gurubase.io

Hello team,
I'm the maintainer of Anteon. We have created Gurubase.io with the mission of building a centralized, open-source tool-focused knowledge base. Essentially, each "guru" is equipped with custom knowledge to answer user questions based on collected data related to that tool.
I wanted to update you that I've manually added the Dropwizard Guru to Gurubase. Dropwizard Guru uses the data from this repo and data from the docs to answer questions by leveraging the LLM.
In this PR, I showcased the "Dropwizard Guru", which highlights that Dropwizard now has an AI assistant available to help users with their questions. Please let me know your thoughts on this contribution.
Additionally, if you want me to disable Dropwizard Guru in Gurubase, just let me know that's totally fine.

Hi everyone,
Have you had a chance to check this out?
Additionally, I’d like to update you on the release of the Maintainer Panel feature on Gurubase. With this panel, you can add, remove, or update data sources, as well as change the logo and more. You can find the details about how to claim a Guru here.
In the near future, I’m planning to include analytics insights in this panel, such as the number of questions asked, the most frequently asked ones, and more. I’ll be sure to update this thread once it’s available. However, in case I miss it, I highly recommend joining our Discord channel to stay updated.
If you’d prefer that I don’t update this thread anymore, please let me know.


Improve keybinding JSON schema

Summary of the Pull Request
The pattern regex in profiles.schema.json now correctly disallows keybindings consisting of only modifiers, modifiers not separated by +, and unknown key names. Certain shift+numpad combinations are also not allowed.
The description lists allowed key names in tabular format (assuming the client renders \t correctly):

PR Checklist

[x] Closes #3856 and #2967
[x] CLA signed.
[ ] Tests added/passed (only manual validation in VSCode)
[ ] Requires documentation to be updated (this is documentation)
[x] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #3856

Detailed Description of the Pull Request / Additional comments
The problem with the current keybinding schema is primarily that it accepts invalid key combinations.
Also, there is no accessible documentation of valid keys and modifiers. Now the regular expression
should be much closer to what the parser in KeyChordSerialization.cpp actually accepts, and the associated description explains the allowed string format.
One possible difference between the regexp and the parser is that the former accepts any single character except + and whitespace (e.g. }) for the key part while the latter relies on the VkKeyScanW Windows API for validation of single-character keys.
The regular expression might be a bit difficult to digest, so here it is with some added whitespace and no JSON string escapes:
^
 (?<modifier> (ctrl|alt|shift)
              (?:\+(ctrl|alt|shift)(?<!\2))?
              (?:\+(ctrl|alt|shift)(?<!\2|\3))?
              \+
 )?
 (?<key> [^\s+]
         |backspace|tab|enter|esc|space|pgup|pgdn|end|home|left|up|right|down|insert|delete
         |(?<!shift.+)numpad_(?:[0-9]|period)
         |numpad_(?:multiply|plus|minus|divide)
         |f[1-9]|f1[0-9]|f2[0-4]
         |plus
 )
$

Q: Is named captures a good idea? It was used by the previous regular expression, but an alternative approach would be to use numbered captures and only capture the individual modifiers (1 to 3) and the key (4).
Q: Would it be better to not list key names and descriptions in an attempted table, which currently isn't rendered very nicely in VS Code? The names are, after all, rather self explanatory.
Validation Steps Performed
I have performed validation of the new schema in VS Code v1.40 by opening the profiles.json settings file and changing the $schema property to https://raw.githubusercontent.com/davidwin/terminal/keychords_schema/doc/cascadia/profiles.schema.json. I'm then able to see that I get a description of how to format the globals.keybingings[].keys strings if I hover over a keys item, and a yellow squiggly if I enter an invalid key combination. All the default key combinations pass without error, and examples of strings that don't validate are: alt, shift+, ctrl++, +, shiftalt+up.
You can try the regular expression and get a deeper understanding of it at Regex101.

(I'm excited about this; sorry I haven't yet reviewed it!)

No problem! I put the PR in draft anyway because I had the two open questions about the style of the regex and the (long) descriptive text.

Q: Is named captures a good idea? It was used by the previous regular expression, but an alternative approach would be to use numbered captures and only capture the individual modifiers (1 to 3) and the key (4).

I personally like named captures, but if we're not actually leveraging the names anywhere to consume the groups... then it's probably unnecessary.

Q: Would it be better to not list key names and descriptions in an attempted table, which currently isn't rendered very nicely in VS Code? The names are, after all, rather self explanatory.

I don't think we need to have a description that is pretty much the same thing as a name. If it's cleaner with just the names, I think we just use the names./

I'll wait one day before marking this ready for review (so that it can be merged)

Great! I noticed that some strings had been added to KeyChordSerialization.cpp since I opened this PR. Just let me rebase the file and add those tweaks, and I'll mark it ready for review tomorrow.

Also, really sorry for the delay :(

I rebased the PR and updated the pattern to match the current KeyChordSerialization.cpp (some synonyms had been added). I also made the descriptive text somewhat more consistent.
And don't worry about the delay!

I'm going to leave this one up to @carlos-zamora. He's the resident regex wizard :)


0.16 incorrect error message when type annotation is too generic

The following
type alias Employee a b =
   ()

jimJones : Employee {} {}
jimJones =
  ()

locateAssociateOfJim : (Employee a b -> c) -> c
locateAssociateOfJim associateLocator =
  associateLocator jimJones

Produces in incorrect message:
-- TYPE MISMATCH ------------------------------------------------------- tmp.elm

The type annotation for `locateAssociateOfJim` does not match its definition.

29│ locateAssociateOfJim : (Employee a b -> c) -> c
                           ^^^^^^^^^^^^^^^^^^^^^^^^
The type annotation is saying:

    (Employee {} {} -> c) -> c

But I am inferring that the definition has this type:

    (Employee {} {} -> c) -> c

Hint: There is some problem with a rigid type variable. It is very likely that a
type annotation is too generic. One type is saying *many* kinds of value can be
given, but the other needs a more specific type.

Detected errors in 1 module.

It should say: The type annotation is saying: (Employee a b -> c) -> c

The original example above only seems to print incorrectly, but actually there are cases where the error is reported completely incorrectly, as follows:
This code
type alias Person a = ()
type alias Employee a b =()
type alias EmployeeAssociateLocator a b c =
    Employee a b -> Person c

jimJones : Employee {} {}
jimJones = ()

locateAssociateOfJim : EmployeeAssociateLocator {} {} c -> Person c
locateAssociateOfJim associateLocator =
    associateLocator jimJones

correctly compiles,  but changing the last {} to b
locateAssociateOfJim : EmployeeAssociateLocator {} b c -> Person c
locateAssociateOfJim associateLocator =
    associateLocator jimJones

produces this error:
-- TYPE MISMATCH ------------------------------------------------------- tmp.elm

The type annotation for `locateAssociateOfJim` does not match its definition.

9│ locateAssociateOfJim : EmployeeAssociateLocator {} b c -> Person c
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The type annotation is saying:

    (Employee {} {} -> ()) -> ()

But I am inferring that the definition has this type:

    (Employee {} {} -> c) -> c

Hint: There is some problem with a rigid type variable. It is very likely that a
type annotation is too generic. One type is saying *many* kinds of value can be
given, but the other needs a more specific type.

Detected errors in 1 module.

which is incorrectly saying that the c type doesn't match, when actually the Employee {} b part is what doesn't match.

@evancz this is perhaps a notable problem with the 0.16 type checking

I think this is the same as #1110, but that one outlines how to resolve it. It should just be a simple syntactic restriction. If that assessment is correct, please close this issue.

I'm not quite sure.  I'll follow the other issue and close if it resolves this one.

This code cannot be written in the latest version of 0.16 so I am going to close. Thanks for the report!


🚀 Deploy storefront

118 images updated 🤔
Does this sound correct @equinor/eds-ux?

@vnys have you looked at the images? Curious how this looks now with changes done in #962

I haven't uploaded nor updated any image on my last documentation update for variants. I have updated the figma links though, does that count as an image in the storefront?

have you looked at the images?

Haven’t checked all the images, but I’ve browsed quickly through a few pages at https://eds-storefront-development.azurewebsites.net

I haven't uploaded nor updated any image on my last documentation update for variants. I have updated the figma links though, does that count as an image in the storefront?

If you make changes in tokens or components in Figma then that results in an updated image when we run the Figma Broker, so maybe the re-organisation is the reason there are so many updated images…

I haven't uploaded nor updated any image on my last documentation update for variants. I have updated the figma links though, does that count as an image in the storefront?

If you make changes in tokens or components in Figma then that results in an updated image when we run the Figma Broker, so maybe the re-organisation is the reason there are so many updated images…

true true, its just based of the unique id that figma has for its images, these changes for each version figma has of a file if something within that image is changed. So either the re-organization or variants...

@vnys A lot of the pages are missing images. Buttons, lists and toc to name a few... Maybe this calls for an issue to investigate...

I haven't uploaded nor updated any image on my last documentation update for variants. I have updated the figma links though, does that count as an image in the storefront?

@lucasveil These are the images exported when using  :)
<FigmaImage
  url="https://www.figma.com/file/0bGXR2sCwMVSDNyyzu5BXrO5/Desktop-UI?node-id=1%3A4"
  alt="Figma design of primary buttons"
/>

drop the updating of images

That commit has now been delegated to the history disposal unit and only exists in a parallel universe


Knockout Support

Include Knockout.js support and provide blue ticks on completed tabs in the month editing screen.

Knockout and MVC interfere a bit.  You can serialize the MVC model to bind to the Knockout model, but it doesn't seem worth the bother.  We'll just stick to using JQuery. 799868d51363b428982e3615cded1a718561da73


Xcode 15 Carthage release built with beta Xcode version

How frequently does the bug occur?
Always
Description
Carthage release for 10.42.3 built with Swift 5.9 (<IP_ADDRESS>.106) which is swift version from Xcode 15 beta release. Current Swift version is Swift 5.9 (<IP_ADDRESS>.108).
Stacktrace & log output
No response
Can you reproduce the bug?
Always
Reproduction Steps

Run Carthage carthage build --no-skip-current --use-xcframeworks --platform iOS

Output
***  Skipped installing realm-swift binary due to the error:
	"Incompatible Swift version - framework was built with 5.9 (swiftlang-<IP_ADDRESS>.106 clang-15<IP_ADDRESS>) and the local version is 5.9 (swiftlang-<IP_ADDRESS>.108 clang-15<IP_ADDRESS>)."

    Falling back to building from the source

Version
10.42.3
What Atlas Services are you using?
Local Database only
Are you using encryption?
Yes
Platform OS and version(s)
iOS 17.0
Build environment
No response

The same problem occurs with v10.42.4.
*** Downloading realm-swift binary at "v10.42.4"
***  Skipped installing realm-swift binary due to the error:
	"Incompatible Swift version - framework was built with 5.9 (swiftlang-<IP_ADDRESS>.106 clang-15<IP_ADDRESS>) and the local version is 5.9 (swiftlang-<IP_ADDRESS>.108 clang-15<IP_ADDRESS>)."

    Falling back to building from the source

swiftlang-<IP_ADDRESS>.106 clang-15<IP_ADDRESS>
swiftlang-<IP_ADDRESS>.108 clang-15<IP_ADDRESS>

It looks like Carthage does not approve of our xcframework having slices built with mixed compiler versions, so we'll need to drop the visionOS build until there's a non-beta Xcode version which supports it.

@tgoyne
still occurs with v10.43.0
*** Downloading realm-swift binary at "v10.43.0"
***  Skipped installing realm-swift binary due to the error:
	"Incompatible Swift version - framework was built with 5.9 (swiftlang-<IP_ADDRESS>.106 clang-15<IP_ADDRESS>) and the local version is 5.9 (swiftlang-<IP_ADDRESS>.108 clang-15<IP_ADDRESS>)."

    Falling back to building from the source

@tgoyne yep, issue is not fixed in latest version

still broken


breaking change in date richvalues in 17.x?

v17 seems to have changed the format of richvalue dates over v16:
wd data --props P569 --simplify --time-converter simple-day --keep qualifiers,ranks,richvalues Q7169784 | jq -r
under 16:
{
  "id": "Q7169784",
  "type": "item",
  "claims": {
    "P569": [
      {
        "value": {
          "time": "1947-01-18",
          "timezone": 0,
          "before": 0,
          "after": 0,
          "precision": 11,
          "calendarmodel": "http://www.wikidata.org/entity/Q1985727"
        },
        "rank": "normal",
        "qualifiers": {}
      }
    ]
  }
}

under 17:
{
  "id": "Q7169784",
  "type": "item",
  "claims": {
    "P569": [
      {
        "time": "1947-01-18",
        "timezone": 0,
        "before": 0,
        "after": 0,
        "precision": 11,
        "calendarmodel": "http://www.wikidata.org/entity/Q1985727",
        "rank": "normal",
        "qualifiers": {}
      }
    ]
  }
}

i.e. there is no longer a separate value object. I don't see anything in the changelog about this, so I'm not sure if this was expected, or is a regression.

The rank and qualifiers are in the value object, that looks like a bug

That should now be fixed in v17.0.10, can you update and retry?

Yep, seems to be working fine. Thanks for the speedy fix!


请问emqx报如下错误的原因是啥？感谢

请问emq报这个错是什么原因？
1、channel received exit from stranger: <0.1554.1>, reason: {resource_handler_not_found；
2、LWM2M-RESOURCE: Reject DELETE from {{10,32,50,174},62741}, Wrong Location: [<<>>], registered location record: {lwm2m_context, <<"jmeter-LAPTOP-R48NLHRI-3143">>,<<"/rd/jmeter-LAPTOP-R48NLHRI-3143">>}

@luyun12you What version of emqx are you using? And please post more info about the error message, it's too short for us to investigate the issue.
The second error message shows your DELETE msg have no location path.

BTW, it would be nice if you change the issue to English.


Update Stack Reference docs to mention GetOutputDetails

Related to https://github.com/pulumi/pulumi/issues/10839.
Update the existing documentation for Stack References to mention the new GetOutputDetails method in each language.
https://www.pulumi.com/docs/intro/concepts/stack/#stackreferences
https://github.com/pulumi/pulumi-hugo/blob/master/themes/default/content/docs/intro/concepts/stack.md

Up at https://github.com/pulumi/pulumi-hugo/pull/2637
This is effectively unusable in Python until https://github.com/pulumi/pulumi/issues/12172
For Java, we need to cut a release before we land the docs https://github.com/pulumi/pulumi-java/issues/1042


Slash Command Autocomplete

Ref: https://discord.com/developers/docs/interactions/application-commands#autocomplete
Design:
{
  "type": 4,
  "data": {
    "id": "816437322781949972",
    "name": "airhorn",
    "type": 1,
    "version": "847194950382780532",
    "options": [
      {
        "type": 3,
        "name": "variant",
        "value": "data a user is typ",
        "focused": true
      }
    ]
  }
}

link to ddocs for description???

link to ddocs for description???

Added it

Dupilcate of #183


UPSTREAM: : add artifact storage api for backend

This change introduces a new api for artifact data retrieval for mlpipeline api server, to be consumed by UI and end users. Two new endpoints are introduced, allowing for 1) collection retrieval and 2) individual artifact metadata retrieval.
When an individaul artifact resource is retrieved, users/ui can specify a share_url option that provides a pre-signed url that with a very short expiry date that can be used as an artifact download link directly from the originating object store provider. This is currently only implemented for s3-compliant object store backends.
Description of your changes:
Checklist:

[x] The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 1 commits between b775d3c0f9dc220b65b0a35b48a3b41a07a9475a...add42934c854190bd254fbe990801a89b1664722

A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-62
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-62
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-62
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-62
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-62
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-62

An OCP cluster where you are logged in as cluster admin is required.
The Data Science Pipelines team recommends testing this using the Data Science Pipelines Operator.  Check here for more information on using the DSPO.
To use and deploy a DSP stack with these images (assuming the DSPO is deployed), first save the following YAML to a file named dspa.pr-62.yaml:
apiVersion: datasciencepipelinesapplications.opendatahub.io/v1alpha1
kind: DataSciencePipelinesApplication
metadata:
  name: pr-62
spec:
  dspVersion: v2
  apiServer:
    image: "quay.io/opendatahub/ds-pipelines-api-server:pr-62"
    argoDriverImage: "quay.io/opendatahub/ds-pipelines-driver:pr-62"
    argoLauncherImage: "quay.io/opendatahub/ds-pipelines-launcher:pr-62"
  persistenceAgent:
    image: "quay.io/opendatahub/ds-pipelines-persistenceagent:pr-62"
  scheduledWorkflow:
    image: "quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-62"
  mlmd:
    deploy: true  # Optional component
    grpc:
      image: "quay.io/opendatahub/mlmd-grpc-server:latest"
    envoy:
      image: "registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2"
  mlpipelineUI:
    deploy: true  # Optional component
    image: "quay.io/opendatahub/ds-pipelines-frontend:pr-62"
  objectStorage:
    minio:
      deploy: true
      image: 'quay.io/opendatahub/minio:RELEASE.2019-08-14T20-37-41Z-license-compliance'

Then run the following:
cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines.git
cd data-science-pipelines/
git fetch origin pull/62/head
git checkout -b pullrequest add42934c854190bd254fbe990801a89b1664722
oc apply -f dspa.pr-62.yaml

More instructions here on how to deploy and test a Data Science Pipelines Application.

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between f5ab037f8a6efd179b7a47cf623c997f43e05907...c4a2dd3f169515dbb66a6028a5f3e6f3611fb4d5

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-62
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-62
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-62
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-62
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-62
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-62

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between f5ab037f8a6efd179b7a47cf623c997f43e05907...7c8e87404d66dce9d1603f3ce11ca778de814cf4

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-62
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-62
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-62
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-62
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-62
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-62

@HumairAK

3. Fetch a single artifact with GET {{dsp-route}}/apis/v2beta1/artifacts/1?share_url=true   the "share_url=true" parameter will provide a signed url link that will last for 15 seconds (configurable via SIGNED_URL_EXPIRY_TIME_SECONDS env var). Evaluate the response object and confirm it matches with the artifact in mlmd.

{
   "error":"InternalServerError: 1: encountered error parsing artifact: secrets \"ds-pipeline-s3-sample\" is forbidden: User \"system:serviceaccount:kubeflow:ds-pipeline-sample\" cannot get resource \"secrets\" in API group \"\" in the namespace \"kubeflow\"",
   "code":13,
   "message":"InternalServerError: 1: encountered error parsing artifact: secrets \"ds-pipeline-s3-sample\" is forbidden: User \"system:serviceaccount:kubeflow:ds-pipeline-sample\" cannot get resource \"secrets\" in API group \"\" in the namespace \"kubeflow\"",
   "details":[
      {
         "@type":"type.googleapis.com/google.rpc.Status",
         "code":13,
         "message":"Internal Server Error"
      }
   ]
}

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between f5ab037f8a6efd179b7a47cf623c997f43e05907...de3a02902bf4c40394329d8ecab7206565b6d5c0

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-62
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-62
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-62
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-62
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-62
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-62

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between f5ab037f8a6efd179b7a47cf623c997f43e05907...805e9db75a1f463caf8fb5e101d7ed9a56331e62

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-62
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-62
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-62
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-62
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-62
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-62

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between f5ab037f8a6efd179b7a47cf623c997f43e05907...f6639cb5195bea3626ca64476ba217d3ce1fafd4

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-62
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-62
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-62
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-62
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-62
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-62

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between f5ab037f8a6efd179b7a47cf623c997f43e05907...428fd897e1146d44bbe6604af35e569147dd4dc4

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-62
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-62
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-62
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-62
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-62
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-62

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between f5ab037f8a6efd179b7a47cf623c997f43e05907...862371cae661c63d6e9428ccf4f79251b8f92705

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between f5ab037f8a6efd179b7a47cf623c997f43e05907...07bb48f4da15ef493b9da1c44747e9691fae2c27

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-62
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-62
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-62
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-62
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-62
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-62

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-62
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-62
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-62
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-62
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-62
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-62

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between f5ab037f8a6efd179b7a47cf623c997f43e05907...0bb20b90f68e980b03137e50acf406024e93f50a

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-62
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-62
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-62
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-62
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-62
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-62

code changes LGTM.

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
ERROR: couldn't find commits from f5ab037f8a6efd179b7a47cf623c997f43e05907..efda3efb6c3de3f136442342c34faaf2084f14d0: error executing git log: fatal: Invalid revision range f5ab037f8a6efd179b7a47cf623c997f43e05907..efda3efb6c3de3f136442342c34faaf2084f14d0
: exit status 128

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between f5ab037f8a6efd179b7a47cf623c997f43e05907...e50520648c0f7cc5e43fa4cded9914b9b5ff7c92

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-62
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-62
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-62
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-62
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-62
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-62

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between f5ab037f8a6efd179b7a47cf623c997f43e05907...3ada8c9ffc73d69d1a53b3b5cd1cdae5850082f7

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-62
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-62
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-62
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-62
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-62
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-62

I'll hold you to the followups :)
/lgtm
/approve

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between 9faafad2fe36119ce5aa8ad9456a4b4e6e71dbad...c04308feb6c2db7b3989a5f70c335076698f4178


Feature request | Show wallpaper/custom image on break

Hey! First of all, thanks for great project.
It'll be awesome if app can switch between tips to show Fullscreen image for break. Custom or random from Unsplash for example.
Thanks!

Hi, I like the idea ;]
I'll keep the issue opened, but it might take some time to implement it as there are many features on my todo.

Hi @hovancik !!
I would like to work on this issue.Can I take this up as no one is working on it.

@bhavya14  Yeah, how would you like to do it? Let's talk about it first

When using Unsplash, I recommend using random featured images from the "nature" category: https://source.unsplash.com/random/featured/?nature. This then uses really nice-looking images (featured) and also cuts out the sometimes appearing NSFW image (slight nudity) because it's only nature.
I use that in the Unsplash app for Nextcloud and it works quite well:

Do note though that neither Unsplash nor Pexels really use CC0 anymore: https://unsplash.com/license / https://www.pexels.com/photo-license/ – it’s basically a modified CC0 with some specific restrictions, which are sensible though.

@Tlazypanda
So first of all, I think we should talk about how this feature should work from user's point of view and then technical part.
How should this work for user?

original request is to show image instead of break text - does this make sense or should this work in different way?
then, how does the user turn this behavior on?
does this interfere or interact with other features?

I love this idea, but my wish is to show customized words.

@Anderbone you can do that now by editing settings file:  https://github.com/hovancik/stretchly#advanced-settings

I suppose a most common way would be just embed an HTML component into the break popup, and allow user to specify the folder with HTML fragments; this way we can display virtually everything. What do you think about this approach?

I guess we will see. My plan is distribute this as github repos, so similar approach. Question is then how to take care of security.

@Tlazypanda
So first of all, I think we should talk about how this feature should work from user's point of view and then technical part.
How should this work for user?

original request is to show image instead of break text - does this make sense or should this work in different way?
then, how does the user turn this behavior on?
does this interfere or interact with other features?
regarding images: do we wanna see one image, or new image every time? do we wanna pick what images we wanna see?

Will it be better if we just allow users to change the background image locally? It might be easier to be developed. And the problem of new image every time and the conflict between image and quote are gone subsequently.

Is there a reason this can't simply show the desktop wallpaper while hiding other windows? I'm thinking how Workrave does it.

I don't know about workrawe but I am not familiar with any node API that would allow that across platforms. There is option in Stretchly to not show any break ideas resulting in empty window.


Kelloggs - Scraper is not working

ENVIROMENT: production
URL: https://scrapers.peviitor.ro/
Browser: Chrome
Device: laptop
OS: Windows 10
STEPS TO REPRODUCE:

Open URL: https://scrapers.peviitor.ro/src/kelloggs/index.html/
Click: "Run scraper" button

EXPECTED RESULTS:
Scraper should be active and functional
ACTUAL RESULTS:
Scraper status: INACTIVE -- and the page is displaying this error: "python3: can't open file 'kelloggs.py': [Errno 2] No such file or directory"

Nu mai exista firma


Fix some code

bors r+

       // don't infer
-     if (localCtx == null) throw new Mismatch(true);
-     var bindSubst = new PatTraversal.MetaBind(this.subst, metaPat.ref().fakeBind().definition());
+     var bindSubst = new PatTraversal.MetaBind(subst, metaPat.ref().fakeBind().definition());

I don't think we can drop this case, consider this code:
open data Nat | O | S Nat
open data Vec (n : Nat)
| O => vnil
| S n => vcons (Vec n)

def inferMeta (n : Nat) : Nat
| O => O
| S n' => S n'

def justMatch {n : Nat} (xs : Vec (inferMeta n)) : Nat
| vnil => O
| vcons xs' => S O

When we are trying to tyck the Pat: vcons xs', the corresponding signature is Vec (inferMeta <O>) instead of Vec (inferMeta <n>), because the Pat.Meta <n> was inferred when normalizing Vec (inferMeta <n>)

Sorry, my brain went into short circuit...

the corresponding signature is Vec (inferMeta )

Why O? Shouldn't it be S n?

Sorry, my brain went into a short circuit...

What do you mean shortcut? Do you still agree with yourself?

the corresponding signature is Vec (inferMeta )

Why O? Shouldn't it be S n?

There may be some problems which I haven't found out.

the corresponding signature is Vec (inferMeta )

Why O? Shouldn't it be S n?

There may be some problems which I haven't found out.

IMO, Pat.Meta will be always inlined after PatTycker, so why bother handling them in PatClassifier?

the corresponding signature is Vec (inferMeta )

Why O? Shouldn't it be S n?

There may be some problems which I haven't found out.

IMO, Pat.Meta will be always inlined after PatTycker, so why bother handling them in PatClassifier or PatMatcher?

It is probably used during pat tyck, and it should not be inferred when used as an argument to another function.

I see now! Tyvm!

I see now! Tyvm!

But the code doesn't work as expected... I am trying to figure out the reason.


add allow-same-origin

I'm getting this error when trying to access sessionStorage inside the iframe.
Uncaught DOMException: Failed to read the 'sessionStorage' property from 'Window': The document is sandboxed and lacks the 'allow-same-origin' flag.

I don't see any security risk as this is under a controlled environment. Cheers.

Thanks


v0.10.5-18: [Violation] 'requestAnimationFrame' handler took 96ms

I am not sure if this is an issue.

(got this with
nglview.demo()

not too much, I should probably use setTimeout in some instances instead of requestAnimationFrame

seems like there's a bit lagging in displaying.

well, things have to be created... the 'Violation' are about the user experience, about how laggy or interactive it feels, how responsive the page is/can be.

Hey @hainm, would you say 0.10.5-21 lags less?

I can't tell if it's less. Seems similar.

But I do see
NEW

'requestAnimationFrame' handler took 77ms

OLD

'requestAnimationFrame' handler took 130ms

handled some of the violation, see fa0b59536badb3282765338876852f9c4c457c78
as long as the 'requestAnimationFrame' handler took ... does not occur regularly when rendering it is fine


Chinese version first release

Hi, @nbarbettini , finally, the first release of Chinese version come out, if you like, you can add the link on your site:
https://windsting.github.io/little-aspnetcore-book/book/
I've add some gitbook plugins, to enhance the reading experience, check this file for the detials:
https://github.com/windsting/little-aspnetcore-book/blob/zh-cn/book.json

谢谢 @windsting! This is awesome. 😄 I will add a link on the readme.
I won't merge this since a PR isn't necessary. You can maintain your translation in your fork. If you have any questions just let me know.


Parse abstract and short abstract as Markdown

The mdEditor provides an inline markdown editor for the abstract properties. It would be nice to parse this for rendering in the HTML writer.
https://github.com/gettalong/kramdown

I think I've also seen HTML tags embedded in the abstract, probably from copy paste by data managers.  Just something to be aware of.


Fix clip model loading with unicode paths

On windows, if the model dir contained unicode characters clip models would fail to load.  This fixes the file name handling in clip.cpp to support utf16 on windows.
Fixes #5329 #4365

Thanks for fixing


Non-standard characters in path trip MIB reader

How to reproduce
Try to open an MIB dataset via the HDR file where the path contains, for example, square brackets.
What happens
get_filenames()
https://github.com/LiberTEM/LiberTEM/blob/6b6ca850fd71ba3f00ed420267b7d97311343394/src/libertem/io/dataset/mib.py#L94-L107
fails to find the MIB files and returns an empty list:

from libertem.io.dataset.mib import get_filenames

get_filenames(r'E:\LargeData\LargeData\ER-C-1\groups\data_science\data\reference\MIB[FAIL]\20200518 165148\default.hdr')

[]

It works if the folder MIB[FAIL] is renamed to MIB.
What should happen
All characters that can "legally" be part of a file system path work.
We should also check other multi-file datasets such as K2IS and FRMS6 if they suffer from a similar issue. Probably the globs or regexp should be fixed. We should also test that in CI.

Ah, that makes sense! Thanks for looking into this. We can glob.escape the prefix, before adding the *.mib.


Editor + Dotnet ProjectSystem ---- When opening a project with a .fs initially opened.  the .fs is opened as a StandAloneFile.  Roslyn has yet to open a project.

When opening a dotnet sdk project.  SetupNewTextView is called before the project is loaded.
This causes it to be loaded as a Standalone project thus intellisense, file ordering and references are broken.
Probably ...
Need to figure out how Roslyn deals with this !!!!!

Is this something you'll be addressing in #3564?

fixed with:  https://github.com/Microsoft/visualfsharp/pull/3564


Can't parse webkit-keyframes

Well, less.js does parse some keyframes. This for example works:
@-webkit-keyframes spin {
from {
-webkit-transform: rotate(0deg);
-moz-transform: rotate(0deg);
}
to {
-webkit-transform: rotate(360deg);
-moz-transform: rotate(360deg);
}
}
But this will fail to compile on the "0%" line.
@-webkit-keyframes zoom-zoom {
0% {
-webkit-transform: scale(.1);
opacity: 0;
}
70% {
-webkit-transform: scale(1.2);
opacity: 1;
}
100% {
-webkit-transform: scale(1);
}
}

There was a fix in 1.1.6 which was released recently, it parses fine now!


pull request for e2e test at 12/09/2016 21:56:03

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


The account cannot be activated because I was asked to add an organization email address, but I don't have an organization email address at the moment

My non-organization mailbox has not been activated successfully, and the corresponding URL link has been added, what is the reason?

Hello @ghaochen,
This repo is for issues related to the openreview-py library. Because it is necessary for you to show personal information like your email/username, please send us an email to<EMAIL_ADDRESS>Thanks


[firebase_auth: phone auth] In flutter for web app firebase phone auth implementation has an UnimplementedError for firebase_auth_web.FirebaseAuthWeb.new.verifyPhoneNumber method

Describe the bug
In flutter for web app firebase phone auth implementation has an UnimplementedError for firebase_auth_web.FirebaseAuthWeb.new.verifyPhoneNumber method. The same code runs fine when testing on android or iOS device.
Thank you

hello, I face this error also,
my flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel master, v1.15.22-pre.24, on Microsoft Windows [Version 10.0.18362.719], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[√] Chrome - develop for the web
[√] Android Studio (version 3.5)
[√] Connected device (3 available)
• No issues found!
my pubspec
version: 1.0.0+1
environment:
sdk: ">=2.1.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
firebase_core: ^0.4.4+2
firebase_auth: ^0.15.5+2
cloud_firestore: ^0.13.4
firebase_storage: ^3.0.8
The following adds the Cupertino Icons font to your application.
Use with the CupertinoIcons class for iOS style icons.
cupertino_icons: ^0.1.2
font_awesome_flutter: ^8.5.0
smooth_star_rating: ^1.0.3
intl: ^0.16.0
share: ^0.6.3+4
shared_preferences: ^0.5.6
timeago: ^2.0.24
carousel_slider: ^1.4.1
http: ^0.12.0+4
image_picker: ^0.6.3+1
fluttertoast: ^3.1.3
dev_dependencies:
flutter_launcher_icons: "^0.7.0"
flutter_test:
sdk: flutter

HI @yuyenkan
can you please provide your flutter run -d chrome --verbose
as well
Thank you

Uncaught (in promise) Error: UnimplementedError: verifyPhoneNumber
at Object.throw_ [as throw] (errors.dart:196)
at verifyPhoneNumber (firebase_auth_web.dart:358)
at verifyPhoneNumber.next ()
at runBody (async_patch.dart:86)
at Object._async [as async] (async_patch.dart:125)
at firebase_auth_web.FirebaseAuthWeb.new.verifyPhoneNumber (firebase_auth_web.dart:347)
at firebase_auth.FirebaseAuth.__.verifyPhoneNumber (firebase_auth.dart:266)
at Function.initOTP (auth_service.dart:16)
at otp_screen._OTPScreenState.new.initState (otp_screen.dart:38)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4640)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at framework.StatelessElement.new.inflateWidget (framework.dart:3446)
at framework.StatelessElement.new.updateChild (framework.dart:3214)
at framework.StatelessElement.new.performRebuild (framework.dart:4527)
at framework.StatelessElement.new.rebuild (framework.dart:4218)
at framework.StatelessElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatelessElement.new.mount (framework.dart:4476)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.MultiChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.MultiChildRenderObjectElement.new.mount (framework.dart:5947)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.StatelessElement.new.inflateWidget (framework.dart:3446)
at framework.StatelessElement.new.updateChild (framework.dart:3214)
at framework.StatelessElement.new.performRebuild (framework.dart:4527)
at framework.StatelessElement.new.rebuild (framework.dart:4218)
at framework.StatelessElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatelessElement.new.mount (framework.dart:4476)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at _InheritedNotifierElement.new.inflateWidget (framework.dart:3446)
at _InheritedNotifierElement.new.updateChild (framework.dart:3214)
at _InheritedNotifierElement.new.performRebuild (framework.dart:4527)
at _InheritedNotifierElement.new.rebuild (framework.dart:4218)
at _InheritedNotifierElement.new.[_firstBuild] (framework.dart:4481)
at _InheritedNotifierElement.new.mount (framework.dart:4476)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.StatelessElement.new.inflateWidget (framework.dart:3446)
at framework.StatelessElement.new.updateChild (framework.dart:3214)
at framework.StatelessElement.new.performRebuild (framework.dart:4527)
at framework.StatelessElement.new.rebuild (framework.dart:4218)
at framework.StatelessElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatelessElement.new.mount (framework.dart:4476)
at basic._OffstageElement.new.inflateWidget (framework.dart:3446)
at basic._OffstageElement.new.updateChild (framework.dart:3214)
at basic._OffstageElement.new.mount (framework.dart:5830)
at framework.InheritedElement.new.inflateWidget (framework.dart:3446)
at framework.InheritedElement.new.updateChild (framework.dart:3214)
at framework.InheritedElement.new.performRebuild (framework.dart:4527)
at framework.InheritedElement.new.rebuild (framework.dart:4218)
at framework.InheritedElement.new.[_firstBuild] (framework.dart:4481)
at framework.InheritedElement.new.mount (framework.dart:4476)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.InheritedElement.new.inflateWidget (framework.dart:3446)
at framework.InheritedElement.new.updateChild (framework.dart:3214)
at framework.InheritedElement.new.performRebuild (framework.dart:4527)
at framework.InheritedElement.new.rebuild (framework.dart:4218)
at framework.InheritedElement.new.[_firstBuild] (framework.dart:4481)
at framework.InheritedElement.new.mount (framework.dart:4476)
at framework.StatelessElement.new.inflateWidget (framework.dart:3446)
at framework.StatelessElement.new.updateChild (framework.dart:3214)
at framework.StatelessElement.new.performRebuild (framework.dart:4527)
at framework.StatelessElement.new.rebuild (framework.dart:4218)
at framework.StatelessElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatelessElement.new.mount (framework.dart:4476)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at overlay$._TheatreElement.new.inflateWidget (framework.dart:3446)
at overlay$._TheatreElement.new.updateChild (framework.dart:3214)
at overlay$._TheatreElement.new.updateChildren (framework.dart:5580)
at overlay$._TheatreElement.new.update (framework.dart:5957)
at framework.StatefulElement.new.updateChild (framework.dart:3201)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.update (framework.dart:4707)
at _InheritedNotifierElement.new.updateChild (framework.dart:3201)
at _InheritedNotifierElement.new.performRebuild (framework.dart:4527)
at _InheritedNotifierElement.new.rebuild (framework.dart:4218)
at _InheritedNotifierElement.new.update (framework.dart:4862)
at _InheritedNotifierElement.new.update (inherited_notifier.dart:181)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3201)
at framework.SingleChildRenderObjectElement.new.update (framework.dart:5837)
at framework.StatefulElement.new.updateChild (framework.dart:3201)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.update (framework.dart:4707)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3201)
at framework.SingleChildRenderObjectElement.new.update (framework.dart:5837)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3201)
at framework.SingleChildRenderObjectElement.new.update (framework.dart:5837)
at framework.StatelessElement.new.updateChild (framework.dart:3201)
at framework.StatelessElement.new.performRebuild (framework.dart:4527)
at framework.StatelessElement.new.rebuild (framework.dart:4218)
at framework.StatelessElement.new.update (framework.dart:4583)
at framework.StatefulElement.new.updateChild (framework.dart:3201)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.BuildOwner.new.buildScope (framework.dart:2627)
at binding$5.WidgetsFlutterBinding.new.drawFrame (binding.dart:883)
at binding$5.WidgetsFlutterBinding.new.[_handlePersistentFrameCallback] (binding.dart:283)
at binding$5.WidgetsFlutterBinding.new.[_invokeFrameCallback] (binding.dart:1108)
at binding$5.WidgetsFlutterBinding.new.handleDrawFrame (binding.dart:1047)
at binding$5.WidgetsFlutterBinding.new.[_handleDrawFrame] (binding.dart:963)
at engine.dart:191

the log from console
Uncaught (in promise) Error: UnimplementedError: verifyPhoneNumber
at Object.throw_ [as throw] (errors.dart:196)
at verifyPhoneNumber (firebase_auth_web.dart:358)
at verifyPhoneNumber.next ()
at runBody (async_patch.dart:86)
at Object._async [as async] (async_patch.dart:125)
at firebase_auth_web.FirebaseAuthWeb.new.verifyPhoneNumber (firebase_auth_web.dart:347)
at firebase_auth.FirebaseAuth.__.verifyPhoneNumber (firebase_auth.dart:266)
at Function.initOTP (auth_service.dart:15)
at otp_screen._OTPScreenState.new.initState (otp_screen.dart:38)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4640)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at framework.StatelessElement.new.inflateWidget (framework.dart:3446)
at framework.StatelessElement.new.updateChild (framework.dart:3214)
at framework.StatelessElement.new.performRebuild (framework.dart:4527)
at framework.StatelessElement.new.rebuild (framework.dart:4218)
at framework.StatelessElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatelessElement.new.mount (framework.dart:4476)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.MultiChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.MultiChildRenderObjectElement.new.mount (framework.dart:5947)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.StatelessElement.new.inflateWidget (framework.dart:3446)
at framework.StatelessElement.new.updateChild (framework.dart:3214)
at framework.StatelessElement.new.performRebuild (framework.dart:4527)
at framework.StatelessElement.new.rebuild (framework.dart:4218)
at framework.StatelessElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatelessElement.new.mount (framework.dart:4476)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at _InheritedNotifierElement.new.inflateWidget (framework.dart:3446)
at _InheritedNotifierElement.new.updateChild (framework.dart:3214)
at _InheritedNotifierElement.new.performRebuild (framework.dart:4527)
at _InheritedNotifierElement.new.rebuild (framework.dart:4218)
at _InheritedNotifierElement.new.[_firstBuild] (framework.dart:4481)
at _InheritedNotifierElement.new.mount (framework.dart:4476)
at framework.SingleChildRenderObjectElement.new.inflateWidget (framework.dart:3446)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3214)
at framework.SingleChildRenderObjectElement.new.mount (framework.dart:5830)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.StatelessElement.new.inflateWidget (framework.dart:3446)
at framework.StatelessElement.new.updateChild (framework.dart:3214)
at framework.StatelessElement.new.performRebuild (framework.dart:4527)
at framework.StatelessElement.new.rebuild (framework.dart:4218)
at framework.StatelessElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatelessElement.new.mount (framework.dart:4476)
at basic._OffstageElement.new.inflateWidget (framework.dart:3446)
at basic._OffstageElement.new.updateChild (framework.dart:3214)
at basic._OffstageElement.new.mount (framework.dart:5830)
at framework.InheritedElement.new.inflateWidget (framework.dart:3446)
at framework.InheritedElement.new.updateChild (framework.dart:3214)
at framework.InheritedElement.new.performRebuild (framework.dart:4527)
at framework.InheritedElement.new.rebuild (framework.dart:4218)
at framework.InheritedElement.new.[_firstBuild] (framework.dart:4481)
at framework.InheritedElement.new.mount (framework.dart:4476)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at framework.InheritedElement.new.inflateWidget (framework.dart:3446)
at framework.InheritedElement.new.updateChild (framework.dart:3214)
at framework.InheritedElement.new.performRebuild (framework.dart:4527)
at framework.InheritedElement.new.rebuild (framework.dart:4218)
at framework.InheritedElement.new.[_firstBuild] (framework.dart:4481)
at framework.InheritedElement.new.mount (framework.dart:4476)
at framework.StatelessElement.new.inflateWidget (framework.dart:3446)
at framework.StatelessElement.new.updateChild (framework.dart:3214)
at framework.StatelessElement.new.performRebuild (framework.dart:4527)
at framework.StatelessElement.new.rebuild (framework.dart:4218)
at framework.StatelessElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatelessElement.new.mount (framework.dart:4476)
at framework.StatefulElement.new.inflateWidget (framework.dart:3446)
at framework.StatefulElement.new.updateChild (framework.dart:3214)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4481)
at framework.StatefulElement.new.[_firstBuild] (framework.dart:4666)
at framework.StatefulElement.new.mount (framework.dart:4476)
at overlay$._TheatreElement.new.inflateWidget (framework.dart:3446)
at overlay$._TheatreElement.new.updateChild (framework.dart:3214)
at overlay$._TheatreElement.new.updateChildren (framework.dart:5580)
at overlay$._TheatreElement.new.update (framework.dart:5957)
at framework.StatefulElement.new.updateChild (framework.dart:3201)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.update (framework.dart:4707)
at _InheritedNotifierElement.new.updateChild (framework.dart:3201)
at _InheritedNotifierElement.new.performRebuild (framework.dart:4527)
at _InheritedNotifierElement.new.rebuild (framework.dart:4218)
at _InheritedNotifierElement.new.update (framework.dart:4862)
at _InheritedNotifierElement.new.update (inherited_notifier.dart:181)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3201)
at framework.SingleChildRenderObjectElement.new.update (framework.dart:5837)
at framework.StatefulElement.new.updateChild (framework.dart:3201)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.StatefulElement.new.update (framework.dart:4707)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3201)
at framework.SingleChildRenderObjectElement.new.update (framework.dart:5837)
at framework.SingleChildRenderObjectElement.new.updateChild (framework.dart:3201)
at framework.SingleChildRenderObjectElement.new.update (framework.dart:5837)
at framework.StatelessElement.new.updateChild (framework.dart:3201)
at framework.StatelessElement.new.performRebuild (framework.dart:4527)
at framework.StatelessElement.new.rebuild (framework.dart:4218)
at framework.StatelessElement.new.update (framework.dart:4583)
at framework.StatefulElement.new.updateChild (framework.dart:3201)
at framework.StatefulElement.new.performRebuild (framework.dart:4527)
at framework.StatefulElement.new.performRebuild (framework.dart:4675)
at framework.StatefulElement.new.rebuild (framework.dart:4218)
at framework.BuildOwner.new.buildScope (framework.dart:2627)
at binding$5.WidgetsFlutterBinding.new.drawFrame (binding.dart:883)
at binding$5.WidgetsFlutterBinding.new.[_handlePersistentFrameCallback] (binding.dart:283)
at binding$5.WidgetsFlutterBinding.new.[_invokeFrameCallback] (binding.dart:1108)
at binding$5.WidgetsFlutterBinding.new.handleDrawFrame (binding.dart:1047)
at binding$5.WidgetsFlutterBinding.new.[_handleDrawFrame] (binding.dart:963)
at engine.dart:191

I've got the same issue

I believe this ain't implemented yet.
From https://github.com/FirebaseExtended/flutterfire/blob/master/packages/firebase_auth/firebase_auth_web/lib/firebase_auth_web.dart
 @override   Future<void> verifyPhoneNumber(String app,       {String phoneNumber,       Duration timeout,       int forceResendingToken,       PhoneVerificationCompleted verificationCompleted,       PhoneVerificationFailed verificationFailed,       PhoneCodeSent codeSent,       PhoneCodeAutoRetrievalTimeout codeAutoRetrievalTimeout}) async {     // TODO(hterkelsen): Figure out how to do this on Web. We need to display     // a DOM element to contain the reCaptcha.     // See https://github.com/flutter/flutter/issues/46021     throw UnimplementedError('verifyPhoneNumber');   }

I am also facing the same issue, is there any workaround for now?

@arpitmantri7501 I ended up doing a pure JS implementation based on https://firebase.google.com/docs/auth/web/phone-auth, and then calling all of the JS functions using universal_html. Hope this helps!

same issue any fix?

same error .. only way to solve this is by using firebase package instead of firebase_auth, then implementing RecaptchaVerifier... but then it wont use FirebaseAuth object, it will require Firebase object.. which defeats the purpose of using Firebase_auth for web.
Any work around?

This is correct, verifyPhoneNumber is an Android & iOS/MacOS only API, for web please see signInWithPhoneNumber. Thanks

I can't find signInWithPhoneNumber in master.  Is it in some branch?

@burtonmiller - he is talking about using https://pub.dev/packages/firebase instead for the web phone auth. I dont think it is a good option. I removed phone auth from the web because of this.

Thanks for clarifying.
So -- the only option for Flutter Web phone auth for the
foreseeable future is using  the web-only  (
https://pub.dev/packages/firebase) implementation? Because this creates
complications if your code runs on mobile and web...
On Mon, Jun 29, 2020 at 10:00 AM Dheeraj Sarwaiya<EMAIL_ADDRESS>wrote:

@burtonmiller https://github.com/burtonmiller - he is talking about
using https://pub.dev/packages/firebase instead for the web phone auth. I
dont think it is a good option. I removed phone auth from the web because
of this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FirebaseExtended/flutterfire/issues/2117#issuecomment-651244279,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAARWRJO4ADZ755EJUPEC6DRZDCEXANCNFSM4LA54OBQ
.

--
Burton Miller |<PHONE_NUMBER>

I can't find signInWithPhoneNumber , Can you please tell in detail how to implement phone auth in flutter web?

https://pub.dev/packages/firebase  is a separate plugin, not
firebase_auth.  The names are confusing.
On Fri, Jul 3, 2020 at 11:58 AM Sandeep Gurram<EMAIL_ADDRESS>wrote:

I can't find signInWithPhoneNumber , Can you please tell in detail how to
implement phone auth in flutter web?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FirebaseExtended/flutterfire/issues/2117#issuecomment-653651463,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAARWRPET2UQEY3BV55K7CLRZYS55ANCNFSM4LA54OBQ
.

--
Burton Miller |<PHONE_NUMBER>

Looks that this thread solves: https://github.com/flutter/flutter/issues/46021

@Salakar verifyPhoneNumber is not an Android & iOS/MacOS only API, please check the example from main branch. It doesn't work yet. The method 'verifyPhoneNumber' is not implemented yet, the problem is not solved. Please open the issue back.

If I am wrong, сan you fix an example or explain how to use a web API correctly for phone number auth without verifyPhoneNumber?
@hterkelsen @yjbanov please merge any solution, i know several developers and customers who really need it too. We have been waiting for a good solution for half a year.
I have a solution for web with login.html + js code, but it is a very ugly and uncomfortable code.
Why was the firebase_auth module checked as "web support" if the most interesting auth method is not implemented yet? This is confusing to developers.


How do you save a stream object without playing it?

[Enter feedback here]
I want to convert a book to audio, and save the file, so naturally I don't want my computer to be speaking the book out loud while the conversion happens, but looking at the Azure documentation, I frankly don't see a way to get a stream object without speaking the text first.  I've already got the code set up so that I can save the file, but I can't save the file unless I play that audio first.  I want to convert some text to a stream object without having to listen to my computer utter the text. I realize a very inelegant solution is to simply mute my computer, but still, suppose the conversion takes an hour and I need to take a phone call on it.
    import azure.cognitiveservices.speech as speechsdk

    speech_config = speechsdk.SpeechConfig(subscription=subscription_key,
                                           region=service_region)
    audio_config = speechsdk.audio.AudioOutputConfig(use_default_speaker=True)
    speech_config.speech_synthesis_voice_name = 'ar-EG-SalmaNeural'
    speech_synthesizer = speechsdk.SpeechSynthesizer(speech_config=speech_config, audio_config=audio_config)

    speech_synthesizer = speechsdk.SpeechSynthesizer(speech_config=speech_config, audio_config=None)

In the following line, I don't want to do this step because this utters the audio:
 result = speech_synthesizer.speak_text_async("I'm excited to try text to speech").get()
But I have to do that step in order to get the following steps:
stream = AudioDataStream(result)

 stream.save_to_wav_file(path)

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

ID: 3a010d36-e5df-8f34-8c91-b2335208a496
Version Independent ID: 58a0d8bf-1687-7fd7-d990-b9f768507a6c
Content: How to synthesize speech from text - Speech service - Azure AI services
Content Source: articles/ai-services/speech-service/how-to-speech-synthesis.md
Service: azure-ai-speech
GitHub Login: @eric-urban
Microsoft Alias: eur

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

@kylefoley76
I understand your concern. You can use the SpeechSynthesizer class to synthesize speech without playing it through the computer's speakers. Instead of using the speak_text_async() method, you can use the synthesize_speech_to_stream_async() method to synthesize speech to a stream object. Here's an example:
import azure.cognitiveservices.speech as speechsdk
speech_config = speechsdk.SpeechConfig(subscription=subscription_key, region=service_region)
speech_config.speech_synthesis_voice_name = 'ar-EG-SalmaNeural'
Create a memory stream to store the audio data
stream = speechsdk.AudioDataStream(format=speechsdk.AudioStreamFormat(pcm_data_format=speechsdk.PcmDataFormat.Pcm16Bit, sample_rate_hertz=16000, channel_count=1))
Synthesize speech to the memory stream
result = speechsdk.SpeechSynthesizer(speech_config=speech_config).synthesize_speech_to_stream_async("I'm excited to try text to speech", stream).get()
Save the audio data to a file
stream.save_to_wav_file(path)
In this example, we create a AudioDataStream object to store the audio data in memory. We then use the synthesize_speech_to_stream_async() method to synthesize speech to the memory stream. Finally, we save the audio data to a file using the save_to_wav_file() method.
I hope this helps! Let me know if you have any further questions.

This line
        stream = speechsdk.AudioDataStream(
            format=speechsdk.AudioStreamFormat(
                pcm_data_format=speechsdk.PcmDataFormat.Pcm16Bit,
                sample_rate_hertz=16000, channel_count=1))

threw an error and said  there was no method 'AudioStreamFormat' in speechsdk, did you mean AudioStreamWaveFormat, so I then used:
        stream = speechsdk.AudioDataStream(
            format=speechsdk.AudioStreamWaveFormat(
                pcm_data_format=speechsdk.PcmDataFormat.Pcm16Bit,
                sample_rate_hertz=16000, channel_count=1))

Now, I'm getting: AttributeError: module 'azure.cognitiveservices.speech' has no attribute 'PcmDataFormat'
I'm also a little concerned that the result object seems to not be used. Would the result line alter the stream object?

Any idea on the answer to this?

@kylefoley76
I'd recommend posting your question in https://azure.microsoft.com/en-us/support/community/. We'll follow up there. We will now proceed to close this thread. If there are further questions regarding this matter,


Support for Mac or Docker?

This looks like a promising app. I was unfortunately not able to try as it looks like it is only available for Windows at the moment.
Are you considering to make it available for Mac as well? Or maybe a docker container?

Docker would indeed be amazing. Ideally even an Unraid docker container. You familiar or even using Unraid?
This script seems to do exactly what I have been waiting for a long while. Do I understand it correctly that this will allow me to sync my personally created Spotify playlists with Plex? Even both ways?

I'm interested in this as well. I recently created a new Plex server running Ubuntu and Plex in a Docker container. Your tool was great for exporting my Plex music playlists from my old Windows server. I tried several times to import them to my new Plex server with no success. I did reformat the M3U's to reflect the path on the new server which also included changing the \ to / and so on.
Am I correct in assuming this shouldn't work yet until code changes are made? Thanks for your hard work since this may be the best option to add this support to Plex :)