Brew hands asking for github authentication information

Please note that we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

[x] are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
[x] ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new/choose. If it's a brew cask problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[x] ran brew update and can still reproduce the problem?
[ ] ran brew doctor, fixed all issues and can still reproduce the problem?
[ ] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
Trying to install a python library to run the software chirp.
What happened (include command output)
master-blaster:chirp.hg grant$ brew install libxml2 --with-python
Username for 'https://github.com': Updating Homebrew...

The install hangs here. If I enter random username it then asks for password:
master-blaster:chirp.hg grant$ brew install libxml2 --with-python
Username for 'https://github.com': Updating Homebrew...
stupiduser
Password for<EMAIL_ADDRESS>

Once I enter any random password, brew works as normal.
The tab in my terminal indicates git-remote-https * brew install libxml2 --with-python
What you expected to happen
Brew wouldn't need any authentication to install software, or it if did for particular software, it would need to be valid github credentials.
Step-by-step reproduction instructions (by running brew commands)
brew install libxml2

I imagine this won't be instantly reproducible everywhere, but documenting in case other reports roll in.

Running brew update as indicated in the checklist:
master-blaster:chirp.hg grant$ brew update
Username for 'https://github.com': sdfsdafsdf
Password for<EMAIL_ADDRESS>
remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/Homebrew/homebrew-boneyard/'
Error: Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-boneyard failed!

You need to brew untap homebrew/boneyard.


FR: Volvo Trucks Media with Text Single 1 Block

Agile Requirement
As a Business owner, I want to display text and images in different positions and configurations so that my page looks more dynamic and has a nicer design.
Description
Create a Media with Text Block that has the following variants selectable by the editor:
https://www.figma.com/file/Id3nd9kbfh8TpS1SfWhrW2/Volvo-Component-Library?type=design&node-id=1723-10961&mode=design&t=y47m3UK0uZa2NwDF-4
Acceptance Criteria
1- There is a new "Media with text" block available that editors can add to any site.
2- The new block has 4 different variants:
Single 1

Composed by an image or video, a title and some text.
The above-mentioned elements are centered.
If a user clicks on the play button, the video player modal should open and play the video.

Single 2

Composed by an image or video, a title and some text.
The above-mentioned elements can be centered to the left or to the right.

Double 1
Double 2

For the single Media with text block 1 Video with play button variant, we are looking into harmonizing the aspect ratio and using 16:1 across all viewports.
Video Standard should be relabeled as Media Standard, allowing images to be displayed and video. Same for Video Full Width.

Per discussion w/ @cogniSyb This is needed for Digital Reveal, too.

Hi @cogniSyb :)
The component is located within the Exterior details modal on the PDP. you can find it located here.
For the experience, it should open the existing embedded video player modal with the video (as you mentioned - similar to the resource gallery).
Let me know if this helps or if you require any further clarifications!

@DanielaPedrochevd @cogniSyb
None of the seven variants listed in acceptance criteria above don't describe or show "Media with tabs"
variant - https://www.figma.com/file/Id3nd9kbfh8TpS1SfWhrW2/Volvo-Component-Library?node-id=1790%3A15798&mode=dev
Please update the specification with these variants.

@cogniSyb
"The code can be reused partially; the interaction/tabs should be removed." - I thought we should use tabs in Single 2 Left' and 'Single 2 Right' since you mentioned we should reuse code from "Media with tabs".
I got confused by advice to reuse the code from "Media with tabs" because from my perspective the only thing which we can reuse from Media with tabs is 'tabbing' functionality.
All clear now.

@cogniSyb Are the design questions all answered? If so, please clear the label. Thank you!

@cogniSyb thanks for raising - will double check and try get an answer on this today

Hi @cogniSyb I checked with design, there should not be 2 variants, there is only 1 that the margins match other components. It can be located here in the design change log. let me know if you have any further questions! :)

Issues reported and fix received :
Sybren Wartna
2 days ago
This can be retested
Single 1 Video with Play Button – video size updated. Both mobile and tablet have a square aspect ratio
Single 2 Right (and Single 2 Left) – image size is changed, aspect ratio is 4/3 and aligns with Media With Tabs: https://180-media-with-text--vg-volvotrucks-us-rd--netcentric.hlx.page/drafts/syb/media-tabs-vs-media-text
Double 1 Margin between Title and text is 24px whereas expected is 16px – I’m going to check this with design
Double 2 scrolling – fixed
Girish Digrajkar:
1 day ago
Retest summary :
Single 1 Video with Play Button – Desktop, Mobile Width is as expected however, not the Height ; Tablet size is now as expected;
Single 2 Right (and Single 2 Left) –  Desktop Width is 609 whereas required is 698 ;  Tablet size is as expected;   Mobile : Width required is 245 whereas is 257.25
Ok
Double 2 scrolling –  Mobile : Width and Height expected is 335px whereas it is 506 and no padding in between 2 images;
Desktop & Tablet : As expected so, passed

Checked and confirmed with Syb for above observations and pixel size are expected as per his discussion with Agency.  Double 2 block scrolling has been validated and is as expected hence, this issue passed validations thus, could be closed.


[flipt-client-ruby] Unexpected API Response Change Between v0.10.0 and v0.11.0

Hello, thank you for maintaining the flipt_client gem. I've encountered a potential issue regarding response format changes between versions v0.10.0 and v0.11.0, and I’d like to ask for clarification.
Description
In v0.10.0 and v0.11.0, the API response format differs, which seems to break backward compatibility. Since this is a minor version update, I suspect this might be unintentional.
Steps to Reproduce
The difference in behavior can be observed with the following commands:
# flipt_client v0.10.0
bin/rails runner 'p [Flipt::VERSION, Flipt::EvaluationClient.new("default", url: ENV.fetch("FLIPT_URL")).list_flags]'
# => ["0.10.0", {"status"=>"success", "result"=>[{"key"=>"flag_variant", "enabled"=>true, "type"=>"VARIANT_FLAG_TYPE"}], "error_message"=>nil}]

bin/rails runner 'p [Flipt::VERSION, Flipt::EvaluationClient.new("default", url: ENV.fetch("FLIPT_URL")).evaluate_batch([])]'
# => ["0.10.0", {"status"=>"success", "result"=>{"responses"=>[], "request_duration_millis"=>0.00019899999999999999}, "error_message"=>nil}]

# flipt_client v0.11.0
bin/rails runner 'p [Flipt::VERSION, Flipt::EvaluationClient.new("default", url: ENV.fetch("FLIPT_URL")).list_flags]'
# => ["0.11.0", [{"key"=>"flag_variant", "enabled"=>true, "type"=>"VARIANT_FLAG_TYPE"}]]

bin/rails runner 'p [Flipt::VERSION, Flipt::EvaluationClient.new("default", url: ENV.fetch("FLIPT_URL")).evaluate_batch([])]'
# => ["0.11.0", {"responses"=>[], "request_duration_millis"=>0.0}]

Expected Behavior
I would expect the response format to remain consistent across minor version updates. Specifically, the response should include fields like status and error_message, as seen in v0.10.0:
{"status"=>"success", "result"=>..., "error_message"=>nil}

Actual Behavior
In v0.11.0, the response no longer includes the status and error_message fields. The format has changed to the following:
[{"key"=>"flag_variant", "enabled"=>true, "type"=>"VARIANT_FLAG_TYPE"}]

Environment

gem: flipt_client
Versions: v0.10.0 and v0.11.0
Ruby: v3.3.6

Since this change appears in a minor version update, I wanted to check if this was an intentional modification or a possible bug.

Hey @mizoR sorry for the disruption here.
I believe this changed as part of a refactor to bring some consistency between the various language clients:
https://github.com/flipt-io/flipt-client-sdks/pull/376
I think the envelope (status/result/error) we had before we a bit of an implementation detail leaking through the client API.
Now the evaluation will actually raise an exception when an error occurs instead.
I appreciate this is perhaps a little non-traditional for a minor update. While we aim to maintain semver as much as possible, while pre v1 this might happen on rare occassions. No plans to break it again anytime soon though.
Apologies again for the disruption!

Thank you for the explanation. Understood!


Fix IsBinaryRel() check

This small PR fixes wrong binary checks for labels.

The bug was introduced by https://github.com/dmlc/xgboost/pull/8931
The checks should be in range 1.0+eps > label > 0.0-eps, with eps = 1e-6

The errors was cought on TVM autotune process:
File "/usr/lib64/python3.11/site-packages/tvm/autotvm/tuner/xgboost_cost_model.py"
, line 538, in after_iteration
    bst_eval = model.eval_set(self.evals, epoch, feval)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.11/site-packages/xgboost/core.py", line 1995, in eval_set
    _check_call(
File "/usr/lib64/python3.11/site-packages/xgboost/core.py", line 270, in _check_call
    raise XGBoostError(py_str(_LIB.XGBGetLastError()))
xgboost.core.XGBoostError: [15:59:59] /builddir/build/BUILD/xgboost/src/common/ranking_utils.h:378:
Check failed: is_binary: MAP can only be used with binary labels.

Thank you,
~Cristian.
Cc: @trivialfis , @RAMitchell , please help with the review.

Hi, the check was for y \in {0, 1} or y == 0.0f || y == 1.0f, it's written this way for being compatible with floating point.

Hi, the check was for y \in {0, 1} or y == 0.0f || y == 1.0f, it's written this way for being compatible with floating point.

@trivialfis

So you mean y can be only 0.0 (with small eps margin) or y can be only 1.0 (with small eps margin) ?

If so,  I should reconsider the use case.

In that case, we can threshold the label using 0.5. But it's not as rigorous as one might prefer.

I'll do so, will see if resulted MAP impacts beaviour of TVM's internal model evaluation.
To close the discussion I leave here a  way of inplace binarization as per your suggestion.
 dtrain = xgb.DMatrix(data, label=label)
 lbl = dtrain.get_label()
 lbl[lbl>=.5] = 1.0
 lbl[lbl<0.5] = 0.0
 dtrain.set_label(lbl)

Thanks @trivialfis !
~Cristian.

@cbalint13 perhaps a better way would be to move away from the map metric. Since likely we need continuous regression ranking. I assume pair-wise or other metrics could still work for such cases.
@trivialfis can you confirm if that is the case?

It would still be useful to have rank values being continuous. The particular use case in TVM was cost model prediction, where we only care about the relative rank of the cost but not their accurate values.
As a result, the ability to be able to specify the ground truth label sample, rather than the pairs is useful as there can be many such pairs in total.

@trivialfis ,

In the last couple PRs, I have changed NDCG to integer only, meaning it accepts only discrete labels, with an additional option for user to specify custom gain function, which can be continuous. The custom gain function still needs a few more PRs to be merged.

I am interested to track it, is there a tracker for the upcoming custom gain function (as pr or issue) ?

https://github.com/dmlc/xgboost/pull/8822 is the WIP PR, I'm extracting small parts of it for review and merge.
For continuous rank value, NDCG with custom gain seems to be the right choice. Will keep you updated with the progress.


Add twitter banners

add banners for twitter.
link the PR to issue please

@M1zz BTW you do not need to name your branch like that. You could have named just twitter-banners. All contributors is a bot that adds contributors to contributors.md.
@all-contributors add @M1zz for design.


Fixed warn in addOnCollide()

Fixed problem at line 185:
Uncaught ReferenceError: warn is not defined

👍 @jvanroose thanks for catching that!


feat(CI): Email reports

Since we don't have a Jenkins badge on the front page, it might be
difficult to track when builds have failed besides our immediate PR, like
with master.  So emailing relevant people.

[x] This contribution adheres to CONTRIBUTING.md.
[x] New tests have been created for any new features or regression tests for bugfixes.
[x] tox successfully runs, including unit tests and style checks (see CONTRIBUTING.md).

Coverage remained the same at 63.955% when pulling d4d0f665e31c1f40960abd2b9928d5a60a8a0899 on epage:email into 0b0d05d5696f7afcbd3ddf3dba96b75cfce24b74 on ni:master.


Release v2.1.1

:construction_worker: Purpose
Release v2.1.1
:rocket: Changes
See changelog for more details
:warning: Breaking Changes
None

Codecov Report

Merging #341 into master will increase coverage by 0.18%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #341      +/-   ##
==========================================
+ Coverage   53.15%   53.33%   +0.18%
==========================================
  Files          50       49       -1
  Lines        4572     4450     -122
==========================================
- Hits         2430     2373      -57
+ Misses       1646     1597      -49
+ Partials      496      480      -16

Impacted Files
Coverage Δ

api/v2/routes_payment.go
19.78% <0%> (-4.86%)
:arrow_down:

api/v2/routes_rtfs.go
30% <0%> (-0.5%)
:arrow_down:

cmd/temporal/main.go
43.31% <0%> (-0.47%)
:arrow_down:

grpc-clients/bch.go

api/v2/api.go
85.46% <0%> (+0.61%)
:arrow_up:

api/v2/utils.go
58.6% <0%> (+1.37%)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #341 into master will increase coverage by 0.18%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #341      +/-   ##
==========================================
+ Coverage   53.15%   53.33%   +0.18%
==========================================
  Files          50       49       -1
  Lines        4572     4450     -122
==========================================
- Hits         2430     2373      -57
+ Misses       1646     1597      -49
+ Partials      496      480      -16

Impacted Files
Coverage Δ

api/v2/routes_payment.go
19.78% <0%> (-4.86%)
:arrow_down:

api/v2/routes_rtfs.go
30% <0%> (-0.5%)
:arrow_down:

cmd/temporal/main.go
43.31% <0%> (-0.47%)
:arrow_down:

grpc-clients/bch.go

api/v2/api.go
85.46% <0%> (+0.61%)
:arrow_up:

api/v2/utils.go
58.6% <0%> (+1.37%)
:arrow_up:

Continue to review full report at Codecov.

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


Add null checker when publishing to streaming service

This PR mainly add null checker for StreamingDistributionService in PublishEngageWorkflowOperationHandler.
In /modules/distribution-workflowoperation/src/main/resources/OSGI-INF/operations/publish-aws.xml, streaingDistributionService is not binded to PublishEngageWorkflowOperationHandler. So, in such case, 'publish-aws' operation will fail due to a NullPointerException.
By contrast, in /modules/distribution-workflowoperation/src/main/resources/OSGI-INF/operations/publish-engage.xml, StreamingDistributionService is binded. So, publish-engage operation can run without NPE.

[ ] have a concise title
[ ] close an accompanying issue if one exists
[ ] be against the correct branch (features can only go into develop)
[ ] include migration scripts and documentation, if appropriate
[ ] pass automated testing
[ ] have a clean commit history
[ ] have proper commit messages (title and body) for all commits
[ ] have appropriate tags applied

@Gao-Jun good catch, sorry I missed these.  This should go into r/9.x rather than develop.

New PR #2084 is made to go into r/9.x
This PR could be closed.

Done


Fiber Supervision

Allow fibers to be supervised and define semantics for when a fiber outlives its parents.
This will make it more difficult to leak fibers that continue running in the background.
One possible strategy is to force termination of child fibers when their parent exits. Because interruption of a completed fiber is a no-op this is always safe and would eliminate a lot of the usage of bracket in the implementation. There would need to be a new combinator detached or similar that forks in such a way that the resulting fiber is unsupervised.

Initial strategy is to just provide a Managed variant of start. On the exit of the use block the fiber is interrupted.


Expose dispatch action type constants

Feature Request
Describe the suggestion or request in detail
In webchat customization scenarios, to set dispatch events or to intercept events using a middleware, the type has to be set to a string like WEB_CHAT/SET_TEXT.
It would be great if you could expose the list of supported events as part of a constant so that we don't have strings sprayed across the project and devs can check which events are supported.
Also, If the text associated with a particular event is changed here for some reason, devs wouldn't have to update it in their projects too.
[Enhancement]

Thank you for the submission! We will discuss this as a team and get back to you. :)
@compulim, this seems like a good idea to me. Thoughts?

I think it would be nice to expose some of the action functions.
import { sendEvent, sendMessage, sendMessageBack } from 'botframework-webchat-core'

...

store.dispatch(sendMessage('Hello, World!'));

Yap, I was using DIRECT_LINE/* (internal) and WEB_CHAT/* (external), but probably need to revisit again to see if they are still appropriate.

FYI, I am working on redesigning the Web Chat API for the React side, didn't touch Redux yet.
After that work #2364 is completed, we can look at Redux store. I need to play around to understand more, before hitting too deep, I have some bias, but not well thought out:

If the dev is using Web Chat UI (they are using Redux with React)

Try to hide Redux deeper

Still usable, but you probably don't need it

Devs can use another way to do the work they are doing today, we need to identify these paths, for example,

Transforming outgoing activities before sending out (piggybacking data)
Transforming/filtering activities before process it (backchannel)

Speech is UI, we should move things from speech-related stuff from Redux to React

If the dev is using Web Chat Core (they are using pure Redux without React)

Keep it as-is, or even friendlier
Expose action creators that we support, hide action creators they shouldn't normally need

Loading this up for discussion and prioritization for an upcoming release.


IOS scroll up when load new elements

Hello,
I 've problem like in title, when i load new elements on IOS the list go up each time, new elements appears in list.
Is there any idea to solve that behaviour ?
BR

Hi,
Did you find any solution to this issue? I'm having same issue with listview in IOS. Please share what you did to solve this.
Thanks in Advance

Same issue here. What I've done that seems to prevent the jump is remove the IsRefreshing binding and disable pull to refresh.


Warning when choosing Rows per page

Just a heads up, this warning occurs when choosing a "Rows per page"
"Warning: Don't set .props.resultsPerPage of the React component . Instead, specify the correct value when initially creating the element or use React.cloneElement to make a new element with updated props."
This also occurs at the examples page http://griddlegriddle.github.io/Griddle/quickstart.html
I'm not completely if this is something with no consequence and we should just live with, pretty new to Griddle.

Worth noting that as of now, this is broken (as I remember) with React 0.14.

Fix in v1.


OAuthException - Code was invalid or expired. The session is invalid because the user logged out.

I've just tried a new v3.1.1-beta2 example (http://affinitiz.com/facebook-cf-sdk/examples/website/)
I went to the example logged and granted permission, worked fine. Then go outside the example and logged out from FB, backed to the example refreshed the webpage and...
Sorry, an error occurred.
It has been automatically recorded for further correction.
The installed example on my localhost gives me error report:
OAuthException - Code was invalid or expired. The session is invalid because the user logged out.
The error occurred in C:\ColdFusion9\wwwroot\LEProject_alpha\facebook\sdk\FacebookBase.cfc: line 75
Called from C:\ColdFusion9\wwwroot\LEProject_alpha\facebook\sdk\FacebookGraphAPI.cfc: line 256
Called from C:\ColdFusion9\wwwroot\LEProject_alpha\facebook\sdk\FacebookApp.cfc: line 438
Called from C:\ColdFusion9\wwwroot\LEProject_alpha\facebook\sdk\FacebookApp.cfc: line 254
Called from C:\ColdFusion9\wwwroot\LEProject_alpha\header.cfm: line 23
Called from C:\ColdFusion9\wwwroot\LEProject_alpha\index.cfm: line 1
73 : 					}
74 : 				}
75 : 				throw(errorCode="#exception.getErrorCode()#", message="#exception.getType()# - #exception.getMessage()#", type="#exception.getType()#");
76 : 			}
77 : 		} else if (isSimpleValue(response.fileContent) && response.statusCode == "200 OK") {

Hi Benoit, I have the latest version (3.1.1 b4) and am having a similar issue. Mine is a case of the session timing out, I'm sure... the cookie still exists but FB times out the auth token and it seems I'm left with this error to handle. I still have the FB member ID (#userid#) available to the system but the callAPIService() function throws the "Code was invalid or expired. Session has expired at unix time<PHONE_NUMBER>. The current unix time is<PHONE_NUMBER>." error and I'm not sure how I should be handling this. I would have figured the invalidateUser() would have taken care of this and while the code is clean and easily modified I don't want to start playing around when you are so active in development. Am I missing something?

The invalidateUser should be automatically called in that case, but an error is still thrown for the SDK.
This is normal.
You should always put API calls inside try/catch blocks to catch errors and see if you can ignore them or not.
For example, if the error type is an expired session then you can ignore it.


Release Notes for RTM.

Opening this to track changes for RC2.
OpenIdConnectConfiguration, JsonWebKey, JsonWebKeySet now return collections that users will need to add / remove items rather than setting the entire collection.

We will release notes when releasing RTM.

Let's do this during escrow.


DATETIME FORMAT FAILS W/O TRAILING COMMA FOR EOL

Describe the bug
A clear and concise description of what the bug is.
On my import data file, my last column is a date field. On import django-import-export throws an error saying the DATE format is invalid. Once I add a trailing comma to the end of the line, the error goes away and the import is successful.
To Reproduce
Steps to reproduce the behavior:

Create model with date field.
Create test file with date field as the last header in the CSV
Put in the correct date time format with no trailing comma.
Upload the file.

Versions (please complete the following information):

Django Import Export: 2.5.0
Python 3.9
Django  3.1.6

Expected behavior
A clear and concise description of what you expected to happen.
The date format should be validated and the record created without a trailing comma.
Screenshots
If applicable, add screenshots to help explain your problem.
without the trailing comma

With the trailing comma

Additional context
Add any other context about the problem here.

Hi Drew
thanks for raising this

On import django-import-export throws an error saying the DATE format is invalid.

In your example, the date is invalid according to the default format.  Does it work if you change the date to '2021-01-04'?  You can also add the correct format to your settings file:
DATE_INPUT_FORMATS=("%d-%m-%Y",)

Once I add a trailing comma to the end of the line, the error goes away and the import is successful.

I'm confused about this and I couldn't reproduce it with the test app.  Does the import definitely work?  i.e. a row is created in the db with the correct date set?

@matthewhegarty
Thanks for checking about the date format. I realize it's not the default but I've made the appropriate changes for the import date format to work successfully. As described in the issue, the only difference between a failed import and a successful one is the trailing comma.

Are you able to reproduce this using the example app?

Closing for now. Please post back if you can reproduce this in the example app.


WebSocket error: [object Event]

I just import and compile classes from
http://intersystems-ru.github.io/webterminal/files/WebTerminal-v4.0.0-beta.1.xml
Access to http://localhost:57772/terminal/ get this error
WebSocket error: [object Event]
WebTerminal lost connection with server (code 1006).
I am using this configuration (OSX): 'ENSEMBLE'
directory: /Applications/Ensemble
versionid: 2<IP_ADDRESS>6.0
conf file: cache.cpf  (SuperServer port = 1972, WebServer = 57772)

Hello David!

WebSocket error: [object Event]
WebTerminal lost connection with server (code 1006).

In

[object Event]

Let me fix the error message first. Then, we will have an ability to see what is going wrong.
By the way, check if you have /terminalsocket web application in configuration set up open to anonymous user.

@drechema, now try downloading the latest beta 6 version from here and write the complete WebTerminal's log message.
If you won't see anything more detailed, please, go to Chromium or Google chrome browser, open Developer Tools (F12 or right click - inspect), navigate to the Network tab, and then reload a page (F5).
You will see the next in there, auth?... and WebTerminal.Engine.cls?... requests:

Please check and tell me, which requests are failed or are there any other suspicious / different things.
Thank you!

@drechema, any updates on this? Does the issue appears again and again or does it get solved? Thanks!

@drechema, any updates on this? Does the issue appears again and again or does it get solved? Thanks!

Closed due to inactivity.

I also, currently, see this issue on v4.2.15 ... I don't see any frames returned just (Opcode -1)

Hello @tmaiaroto!

I don't see any frames returned just (Opcode -1)

Could you please check if there is a successful request to /auth?
And if you have UnknownUser enabled in your system (web application /terminalsocket must be with unauthorized access).

Thanks!

Thanks.
UnknownUser is enabled and /terminalsocket seems to allow unauthorized access. It says "Unauthenticated" under Authentication Methods.
However, I can not access /auth there appears to be nothing routed for that, I get a 404.

However, I can not access /auth there appears to be nothing routed for that, I get a 404.

Please, check what happened with this endpoint:
http://<host>/terminal/auth

The /terminal web application should have a dispatch class of WebTerminal.Router. In any case, try to import and compile the latest WebTerminal XML once again and see if there any compilation errors.

Ah, ok. That URL works and I get back plain text/html with JSON {"key":"xxxxxxx"}

That's OK. So does the issue still occurs? (even after re-importing XML file)

Yes, here's the result of the import:
`
Importing Selected Classes from /opt/hie/mgr/Temp/importfromlocal.stream
Import to Namespace USER.
Load started on 05/26/2017 12:50:17
Loading file /opt/hie/mgr/Temp/importfromlocal.stream as xml
Imported class: WebTerminal.Analytics
Imported class: WebTerminal.Autocomplete
Imported class: WebTerminal.Common
Imported class: WebTerminal.Core
Imported class: WebTerminal.Engine
Imported class: WebTerminal.ErrorDecomposer
Imported class: WebTerminal.Handlers
Imported class: WebTerminal.Installer
Imported class: WebTerminal.Router
Imported class: WebTerminal.StaticContent
Imported class: WebTerminal.Trace
Imported class: WebTerminal.Updater
Class WebTerminal.Analytics is up-to-date.
Class WebTerminal.Autocomplete is up-to-date.
Class WebTerminal.Common is up-to-date.
Class WebTerminal.Core is up-to-date.
Class WebTerminal.Engine is up-to-date.
Class WebTerminal.ErrorDecomposer is up-to-date.
Class WebTerminal.Handlers is up-to-date.
Class WebTerminal.Installer is up-to-date.
Class WebTerminal.Router is up-to-date.
Class WebTerminal.StaticContent is up-to-date.
Class WebTerminal.Trace is up-to-date.
Class WebTerminal.Updater is up-to-date.
Load finished successfully.
`

Try to compile WebTerminal.Installer class once more. By the way, what is your $zv?

The reason seems to be in Caché does not accepting the WebSocket handshake. Are you using HTTPS? Some other things to try... Maybe different browser..? Let me know if one of this options works.

Not using HTTPS. Here's the version info:
Cache for UNIX (Red Hat Enterprise Linux for x86-64) 2016.2.1 (Build 806_0_17136U) Tue Mar 7 2017 12:32:06 EST [HealthShare Modules:Core:15.02.9912 + Linkage Engine:15.02.9912 + Patient Index:15.02.9912 + Clinical Viewer:15.02.9912 + Active Analytics:15.02.9912]
I'll try Firefox. IE didn't work (not that anything does in IE).

@tmaiaroto, if you have a moment, could you please try this:
Open a browser's console right on the broken WebTerminal's page, and execute this:
console.log(Date.now());
ws = new WebSocket(`wss://${ location.host }/terminalsocket/WebTerminal.Engine.cls`);
ws.onmessage = (m) => console.log("message", Date.now(), m.data);
ws.onclose = (res) => console.log("close", Date.now(), res.code, res.reason);

(wait until "close" is printed, 5 seconds at max)
And then the same but with another path:
console.log(Date.now());
ws = new WebSocket(`wss://${ location.host }/csp/user/WebTerminal.Engine.cls`);
ws.onmessage = (m) => console.log("message", Date.now(), m.data);
ws.onclose = (res) => console.log("close", Date.now(), res.code, res.reason);

Please, share both outputs. Thank you!

First command I get:<PHONE_NUMBER>065 and then close message saysclose<PHONE_NUMBER>606 1006
Second command I get:<PHONE_NUMBER>734 and then the close message saysclose<PHONE_NUMBER>574 1006

Looks like low-level error during upgrade (switching protocols)... We have heard several times that some users having the same issue but were not able ever to reproduce it. I can try cloning the HealthCare version you mentioned and see if I reach the same (but I think I won't be able to reproduce it anyway).
It may be, but if you are on a dedicated test server with non-sensitive data on in, I can try connecting and figuring out why it doesn't work properly, contact me via e-mail<EMAIL_ADDRESS>in this case.
If not, I will try to clone your hardware configuration and test it soon.

Closing this due to inactivity.
For anyone who encounter such error, please, check first whether WebSocket sample application works with your system. If it does not, then the problem is not in WebTerminal but in WebSockets.
I will be happy to help with both WebTerminal and WebSockets issues, just let me know. Feel free to comment / open new issues.

Hello, just FYI, I saw this problem occur with an InterSystems AP.  I don't know if they'll be using WebTerminal in the future, but in case it helps, this problem probably still exists.   I saw your note to test the WebSockets using the sample app.   I didn't have time to test that.   I'll refer the customer to this page.

Hello!
What is InterSystems AP?
Yup, try to test WebSockets first, that's the most possible case.

I guess AP = Application Partner
David Reche
El 11 jun 2020, a las 19:33, Nikita Savchenko<EMAIL_ADDRESS>escribió:

Hello!
What is InterSystems AP?
Yup, try to test WebSockets first, that's the most possible case.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/intersystems-community/webterminal/issues/75#issuecomment-642828000, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADJQTT6Z7RJWM5E23HQH6M3RWEIP5ANCNFSM4CVBC7LQ.


Roll engine to 63c34d8330536fb570af0661d49d131c04df1bdb

https://github.com/flutter/flutter/issues/13748

Tests fail, and I'm supposed to be OOO, so I'm closing this and gonna let @zanderso look at the test failures, since they look related to https://github.com/flutter/engine/pull/4492


docker build issue

hi, thank you for providing this first-tier tool coverageMaster.
I am trying to install using Docker according to your instruction:

cd coverageMasterfolder (i.e. where coverageMaster.py is)
docker build -t coveragemaster .

but an error occured:
Sending build context to Docker daemon  73.37MB
Step 1/4 : FROM python:3.7-slim
---> 1c3e07edea3f
Step 2/4 : RUN pip3 install numpy==1.16.2 sympy==1.0 PyWavelets==1.0.3 matplotlib==2.2.3 scipy==1.2.1 more_itertools==8.8.0 pandas==1.0.0
---> Running in 7b24dc958fad
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0xffffb55e2110>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/numpy/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0xffffb55e27d0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/numpy/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0xffffb55e2c50>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/numpy/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0xffffb55e2dd0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/numpy/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0xffffb5100410>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/numpy/
ERROR: Could not find a version that satisfies the requirement numpy==1.16.2 (from versions: none)
ERROR: No matching distribution found for numpy==1.16.2
The command '/bin/sh -c pip3 install numpy==1.16.2 sympy==1.0 PyWavelets==1.0.3 matplotlib==2.2.3 scipy==1.2.1 more_itertools==8.8.0 pandas==1.0.0' returned a non-zero code: 1
Could you please help me with this? Thank you so much. : )

It is fixed now


throw grpc failed instead of invalid op on generic failure

It looks like there's been some desire to change the use of invalid operation exception on certain failures.
Making and throwing a new type here that extends InvalidOperationException to not make a breaking change. (under assumption users might currently catch InvalidOperationException).
This is mostly an initial idea to change it. I doesn't seem common to extend something other than Exception. Another idea was adding something new as the inner exception of InvalidOperationException, but seeing how this looked.
cc @jtattermusch @jskeet

What can cause these failures? They sound like IOExceptions just from a brief look at the code throwing them. But yes, that would be a breaking change...

It gets tricky I think because it looks like it can be thrown for invalid operation programming errors (e.g., calling requestStream.WriteAsync() after already calling requestStream.CompleteAsync()), but also for IO errors, like if WriteAsync() fails due to network error. Trying to keep the former but change the latter here.

It seems like extending the current exception would be too much of a breaking change? Closing this to not use the idea, guessing it might just cause problems.


Host video sync

added sync functionality when sending video from the host

Updated, testable using
depthai_demo.py -sync -vid https://www.youtube.com/watch?v=Y1jTEyb3wiI


Password Change

turns out it just works after kasper changed it. Just some other fix I noticed and did earlier on this branch is in here.

Maybe also use this PR to add some docs :slightly_smiling_face:

I will add docs in another PR.


Bot is failing to time a snipe

I was trying to snipe the username Ballroom for later tonight but when I out in the name and the 1000 for delay it failed to time snipe and crashed

Same happened to me! I tried sniping 8ww with a 715 delay, and it said the saim thing! I eaven tried it with a 400 delay but it still dosent work! Please help us!

This will happen on any name, any time namemc is using Cloudflare protection on their website. They recently enabled it, disabled it, and then reenabled it. I'm working on a proprietary droptime server that I'll run which will be able to give droptimes even when namemc is down. I should have it out in a few days.

Sweet! Thank you so much
On Thu., May 13, 2021, 8:33 a.m. Kqzz, @.***> wrote:

This will happen on any name, any time namemc is using Cloudflare
protection on their website. They recently enabled it, disabled it, and
then reenabled it. I'm working on a proprietary droptime server that I'll
run which will be able to give droptimes even when namemc is down. I should
have it out in a few days.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MCsniperPY/MCsniperPY/issues/70#issuecomment-840498756,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGKLU3NRXU3LNOVTOU25W5DTNO2JFANCNFSM44Z3GXUA
.

Fixed on the recode. Check the #announcements channel in discord for a fix. tl;dr download recode (https://docs.mcsniperpy.com) and change timing_system to teun in config.ini.


[Enhancement] Component group

Problem: The number of components is increasing, which makes it increasingly difficult to find what you need.
So I propose grouping some components into a group that displays as a dropdown list.
**Recommended groups: **
//trigger//

Damage: Environment Damage, Physical Damage, Skill Damage, Took Physical Damage, Took Skill Damage
Fishing: Fishing, Fishing Bite, Fishing Fail, Fishing Grab, Fishing Ground, Fishing Reel
Item: Item drop, Item swap, armor equip
Block: Block break, Block place

//Mechanic//

Value: Value Add, Value Atribute, Value Copy, Value Distance, Value Health, Value Location, Value Lore, Value Lore Slot, Value Mana, Value Multiply, Value Placeholder, Value Random
Warp: Warp, Warp Location, Warp Random, Warp Swap, Warp Target, Warp Value
Flag: Flag, Flag Clear, Flag Toggle
Target: Remember Targets, Forget Targets

I'm not sure about drop-downs, but potentially have some sub-groups on things could be beneficial for helping people find things. I have toyed with the idea of making the larger component groups collapsible too.

I don't understand what sub-groups really are. But as long as it benefits my eye longevity, it's great

We're working on making a single Value Mechanic that contains all functionality from the old ones, that's ought to help a bit at least.

I'll use the targets, conditions, and mechanics as an example.
test


Support role graph

Nice, thanks! I like Graph#to_dot :)
But in my opinion #to_png does not belong in the API gem (or our code in general, insofar as it just calls dot, which is much more transparent and convenient to pipe directly using a shell).


New package: WinAuth.WinAuth version 3.5.1

- [X] Have you signed the Contributor License Agreement?

[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.6 schema?

Resolves #142719

Microsoft Reviewers: Open in CodeFlow

For moderators
This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

@Trenly

https://github.com/microsoft/winget-pkgs/issues/142854


container is not set when code is compressed with webpack

There is a line in getContainer:
if (!container && !isDomContentLoaded) {
The problem with this line seems to happen when sweet scroll is minified and loads before the DOM is ready.
Like, I think the test for the container needs to be somehow changed so that it fires before the DOM loads, not sure the best way to do that??
Basically if the container is still null but if the DOM has loaded it skips to this line and then silently fails:
callback.call(this, container); // container is null
I think it should be:
if (!container || !isDomContentLoaded) {
If you want to see by running some logs, here is a quick and dirty test to see what I mean:
{
      key: "getContainer",
      value: function getContainer(selector, callback) {
        var _this3 = this;

        var _options = this.options;
        var verticalScroll = _options.verticalScroll;
        var horizontalScroll = _options.horizontalScroll;

        var container = null;

        if (verticalScroll) {
          container = scrollableFind(selector, "y");
        }

        if (horizontalScroll) {
          container = scrollableFind(selector, "x");
        }
        console.log({
          container: container,
          isDomContentLoaded: isDomContentLoaded
        });
        if (!container && !isDomContentLoaded) {
          console.log('no dom content yet');
          (function () {
            var isCompleted = false;

            addEvent(doc, DOM_CONTENT_LOADED, function () {
              isCompleted = true;
              _this3.getContainer(selector, callback);
            });

            // Fallback for DOMContentLoaded
            addEvent(win, "load", function () {
              if (!isCompleted) {
                _this3.getContainer(selector, callback);
              }
            });
          })();
        } else {
          console.log('dom is ready now, container is not always');
          console.log({
            container: container
          })

          callback.call(this, container);
        }
      }

Also, as a sidenote, you add an Event (addEvent) when the dom hasn't loaded yet, but this doesn't seem to get removed once you reach the callback.call line?

Hi @nicolechung. Thanks you for issues.
I will confirm that afterward 😃

It was confirmed by Chrome (52.0.2743.116 (64-bit)) but was not able to reproduce ... 😢
In the following code have been removed the container, but do you have any reason? (Removed when compiled with webpack?)
if (horizontalScroll) {
  container = scrollableFind(selector, "x");
}

You've got a good point. DOMContentLoaded and load event is likely to need to be canceled 👍

Can you send me a sample code including webpack.config.js?

Here is the webpack config:
base
var path = require('path')

module.exports = {
  entry: {
    app: './src/main.js'
  },
  output: {
    path: path.resolve(__dirname, '../dist/static'),
    publicPath: 'static/',
    filename: '[name].js'
  },
  resolve: {
    extensions: ['', '.js', '.vue'],
    fallback: [path.join(__dirname, '../node_modules')],
    alias: {
      'src': path.resolve(__dirname, '../src'),
      'config': path.join(__dirname, '../config', process.env.NODE_ENV)
    }
  },
  resolveLoader: {
    fallback: [path.join(__dirname, '../node_modules')]
  },
  module: {
    preLoaders: [
      {
        test: /\.vue$/,
        loader: 'eslint',
        exclude: /node_modules/
      },
      {
        test: /\.js$/,
        loader: 'eslint',
        exclude: /node_modules/
      }
    ],
    loaders: [
      {
        test: /\.vue$/,
        loader: 'vue'
      },
      {
        test: /\.js$/,
        loader: 'babel',
        exclude: /node_modules/
      },
      {
        test: /\.json$/,
        loader: 'json'
      },
      {
        test: /\.html$/,
        loader: 'vue-html'
      },
      {
        test: /\.(png|jpg|gif|svg)$/,
        loader: 'url',
        query: {
          limit: 10000,
          name: '[name].[ext]?[hash:7]'
        }
      },
      {
        test: /\.css$/,
        loader: 'style-loader!css-loader'
      },
      {
        test: /\.scss$/,
        loaders: ["style", "css", "sass"]
      }
    ]
  },
  eslint: {
    formatter: require('eslint-friendly-formatter')
  }
}

prod
var webpack = require('webpack')
var config = require('./webpack.base.conf')
var cssLoaders = require('./css-loaders')
var ExtractTextPlugin = require('extract-text-webpack-plugin')
var HtmlWebpackPlugin = require('html-webpack-plugin')

config.bail = true

// naming output files with hashes for better caching.
// dist/index.html will be auto-generated with correct URLs.
config.output.filename = '[name].[chunkhash].js'
config.output.chunkFilename = '[id].[chunkhash].js'

// whether to generate source map for production files.
// disabling this can speed up the build.
var SOURCE_MAP = true

config.devtool = SOURCE_MAP ? '#source-map' : false

config.vue = config.vue || {}
config.vue.loaders = config.vue.loaders || {}
cssLoaders({
  sourceMap: SOURCE_MAP,
  extract: true
}).forEach(function (loader) {
  config.vue.loaders[loader.key] = loader.value
})

config.plugins = (config.plugins || []).concat([
  // http://vuejs.github.io/vue-loader/workflow/production.html
  new webpack.DefinePlugin({
    'process.env': {
      NODE_ENV: '"build"'
    }
  }),
  new webpack.optimize.UglifyJsPlugin({
    compress: {
      warnings: false
    },
    mangle: {
      except: ['SweetScroll']
    }
  }),
  new webpack.optimize.DedupePlugin(),
  new webpack.optimize.OccurenceOrderPlugin(),
  // extract css into its own file
  new ExtractTextPlugin('[name].[contenthash].css'),
  // generate dist index.html with correct asset hash for caching.
  // you can customize output by editing /index.html
  // see https://github.com/ampedandwired/html-webpack-plugin
  new HtmlWebpackPlugin({
    filename: '../index.html',
    template: 'index.html',
    inject: true,
    minify: {
      removeComments: true,
      collapseWhitespace: true,
      removeAttributeQuotes: true
      // more options:
      // https://github.com/kangax/html-minifier#options-quick-reference
    }
  })
])

module.exports = config

this is the result code after webpack (looks like horizontalScroll is not removed for me?)
{
	      key: "getContainer",
	      value: function getContainer(selector, callback) {
	        var _this3 = this;

	        var _options = this.options;
	        var verticalScroll = _options.verticalScroll;
	        var horizontalScroll = _options.horizontalScroll;

	        var container = null;

	        if (verticalScroll) {
	          container = scrollableFind(selector, "y");
	        }

	        if (!container && horizontalScroll) {
	          container = scrollableFind(selector, "x");
	        }

                // note: if container is null HERE but Dom is loaded, it goes to the callback!
	        if (!container && !isDomContentLoaded) {
	          (function () {
	            var isCompleted = false;

	            addEvent(doc, DOM_CONTENT_LOADED, function () {
	              isCompleted = true;
	              _this3.getContainer(selector, callback);
	            });

	            // Fallback for DOMContentLoaded
	            addEvent(win, "load", function () {
	              if (!isCompleted) {
	                _this3.getContainer(selector, callback);
	              }
	            });
	          })();
	        } else {
	          callback.call(this, container);
	        }
	      }

Like, without being to recreate the DOM issue (you need to have a big webpack with lots of JS to recreate) you can see that it's possible for the container to be null AND the dom to be loaded. If so, because the conditional uses && instead of || it's possible for the callback to be called with null container (if that makes sense).
I'm not entirely sure how scrollableFind works (I only scanned the code) but I think it's possible for those functions to not work (because the Dom is still loading), so container is still null, but then by the time you reach the last conditional, the dom might be loaded by then.

Thank you for webpack.config.js.
That makes sense. I think the following code as improvement. (It is the previous code to be compiled)
getContainer(selector, callback) {
  const { verticalScroll, horizontalScroll } = this.options;
  const finalCallback = callback.bind(this);
  let container = null;

  if (verticalScroll) {
    container = Dom.scrollableFind(selector, "y");
  }

  if (!container && horizontalScroll) {
    container = Dom.scrollableFind(selector, "x");
  }

  // Note: End if find a container.
  if (container) {
    finalCallback(container);

  // Note: If container not found, and DOM has not been built, to find the container.
  } else if (!isDomContentLoaded) {
    let isCompleted = false;

    const handleDomContentLoaded = () => {
      isCompleted = true;
      removeEvent(doc, DOM_CONTENT_LOADED, handleDomContentLoaded);
      this.getContainer(selector, callback);
    };

    const handleLoad = () => {
      removeEvent(win, LOAD, handleLoad);
      if (!isCompleted) {
        this.getContainer(selector, callback);
      }
    };

    addEvent(doc, DOM_CONTENT_LOADED, handleDomContentLoaded);
    addEvent(win, LOAD, handleLoad);

  } else {
    finalCallback(null);
  }
}

This seems to solve the previous problem. (I tried this code apply to the demo page. It is operating normally)
What do you think?

Let me test it, I will get back to you in two hours? Thank you for the quick response!

It's getting late over here. I'll try to check tomorrow :)

I tested and this looks good to me.
Can you let me know if / when the Sweet Scroll library is updated?

Thanks for test. And I intend to update sweet-scroll.js.
I will let you know after I released it. Please wait a little 😃
Thank you, too!

A bug fix version has been released.
Please try it if you have the chance :)
sweet-scroll - npm

Hi, you are (I am guessing) sleeping, but since you will be awake when I am sleeping I will leave a note.
I tested this again and pushed it out to another environment, and it did not work (don't ask...it worked in the earlier environment I tested).
But I did notice this line:
else {
        finalCallback(null);
      }```

The problem with that is that it `finalCallback` (mostly) refers to this function:

```JS
function (target) {
      _this.container = target;
      _this.header = $(params.header);
      _this.tween = new ScrollTween(target);
      _this._trigger = null;
      _this._shouldCallCancelScroll = false;
      _this.bindContainerClick();
      _this.hook(params, "initialized");
    }```

If you say `finalCallback(null)` then the `target` will be null, which means the `container` will be set to null. Which means when I try to scroll using `toElement` it won't work (since the container is null).

Hope this makes sense and if you have time to take a look at in in the next few weeks that would be a super awesome help.

One question.
Do you specify a value for the second argument of SweetScroll constructor?
I would be happy if you know anything, please tell ;-)
I want to pursue the cause of the scrollable element not found bug.
thanks!

We tried the following (all different scenarios)
let sweetScroll = new SweetScroll({}, 'body')
let sweetScroll = new SweetScroll({}, document.querySelector('body'))
let sweetScroll = new SweetScroll({})
In each case, the SweetScroll always works when we don't minify our code. But then when we minify it breaks.
Now it works when I minify but it breaks when we move it to our staging environment. I think because it loads at a different speed again (some async condition between the dom being ready and the container getting initialized)
Again, thank you for taking the time to look at this.

My apologies for the late reply.
When do you execute they codes?

Immediately after loading of script
After DOMContentLoaded
After onload
Other...

Thank you for doing...so many times!

I'm using vuejs, it installs as a "vue plugin"...so I think before the DOMContentLoads.
I tried putting it in a domcontentload listener, but then I noticed that the sweet scroll plugin already listens for domloading?

Oh, that makes sense. sweet-scroll.js is listened for DOMContentLoaded.
Would you debug to scrollableFind processing?
PS: In addition, whether it would be better to create a plug-in of Vue.js if necessary?

scrollables for "y" is an empty array (length 0) for "selectors: body".
That happens twice.
For direction "x" that does not occur.

But also, when you use toElement if the container is null, then the scrolling won't work. If you have the final callback with null as a parameter, when can the container not be null after that?

For example, will you work the following code? (getContainer() method)
  getContainer(selector, callback) {
    const { verticalScroll, horizontalScroll } = this.options;
    const finalCallback = callback.bind(this);
    let container = null;

    if (verticalScroll) {
      container = Dom.scrollableFind(selector, "y");
    }

    if (!container && horizontalScroll) {
      container = Dom.scrollableFind(selector, "x");
    }

    if (container) {
      finalCallback(container);

    // Note: Check readyState
    } else if (!/comp|inter|loaded/.test(doc.readyState)) {
      let isCompleted = false;

      const handleDomContentLoaded = () => {
        removeHandlers();
        isCompleted = true;
        this.getContainer(selector, callback);
      };

      const handleLoad = () => {
        removeHandlers();
        if (!isCompleted) {
          this.getContainer(selector, callback);
        }
      };

      const removeHandlers = () => {
        removeEvent(doc, DOM_CONTENT_LOADED, handleDomContentLoaded);
        removeEvent(win, LOAD, handleLoad);
      };

      addEvent(doc, DOM_CONTENT_LOADED, handleDomContentLoaded);
      addEvent(win, LOAD, handleLoad);

    } else {
      setTimeout(() => this.getContainer(selector, callback), 1);
    }
  }

Do not listen of DOMContentLoaded in the sweet-scroll.js. It has been changed so as to determine the loading status of the DOM.

Do you have a built (ES5) version of that code I can drop in and test?
I tried to drop this into the src but I could not build (I think I am
missing some dependencies)
On 21 August 2016 at 23:43, tsuyoshi wada<EMAIL_ADDRESS>wrote:

For example, will you work the following code? (getContainer() method)
getContainer(selector, callback) {
const { verticalScroll, horizontalScroll } = this.options;
const finalCallback = callback.bind(this);
let container = null;
if (verticalScroll) {
  container = Dom.scrollableFind(selector, "y");
}

if (!container && horizontalScroll) {
  container = Dom.scrollableFind(selector, "x");
}

if (container) {
  finalCallback(container);

// Note: Check readyState
} else if (!/comp|inter|loaded/.test(doc.readyState)) {
  let isCompleted = false;

  const handleDomContentLoaded = () => {
    removeHandlers();
    isCompleted = true;
    this.getContainer(selector, callback);
  };

  const handleLoad = () => {
    removeHandlers();
    if (!isCompleted) {
      this.getContainer(selector, callback);
    }
  };

  const removeHandlers = () => {
    removeEvent(doc, DOM_CONTENT_LOADED, handleDomContentLoaded);
    removeEvent(win, LOAD, handleLoad);
  };

  addEvent(doc, DOM_CONTENT_LOADED, handleDomContentLoaded);
  addEvent(win, LOAD, handleLoad);

} else {
  setTimeout(() => this.getContainer(selector, callback), 1);
}

}
Do not listen of DOMContentLoaded in the sweet-scroll.js. It has been
changed so as to determine the loading status of the DOM.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tsuyoshiwada/sweet-scroll/issues/27#issuecomment-241308899,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAvEYl8eRkQUNZQzoJOi6Zw1IUG3XBYBks5qiRrOgaJpZM4JlboO
.

Sorry about that...
I pushed the code in a different branch. Please try to checkout it.
tsuyoshiwada/sweet-scroll at try-fix-issue-#27

This appears to work (locally). I tried setting the throlling on my network tab too.
Can you push it to master? Unfortunately (unless you know how) I can't 100% test because our staging environment builds from it's own package.json, so I think it needs to be in master. Unless you know how to make a package.json pull from a (non-master) branch instead??

Thanks for tests!
But, Can't still merge to master. Because It's to the failure to tests in mocha.
I think the npm doc would be helpful.

Got it...but so, should I wait for the mocha tests to pass first?
On 22 August 2016 at 09:30, tsuyoshi wada<EMAIL_ADDRESS>wrote:

Thanks for tests!
But, Can't still merge to master. Because It's to the failure to tests in
mocha.
I think the npm doc
https://docs.npmjs.com/files/package.json#git-urls-as-dependencies
would be helpful.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tsuyoshiwada/sweet-scroll/issues/27#issuecomment-241412663,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAvEYodfmN-J_EE0gXLAdHXwJYnJEH6iks5qiaRngaJpZM4JlboO
.

No, I think that priority test the work on staging environment. (Sorry about my poor English...)

So I tried
"dependencies": {
"sweet-scroll": "^1.0.4#21bd8a434f",
But I get this error:
npm ERR! No compatible version found<EMAIL_ADDRESS>npm ERR! Valid install targets:
On 22 August 2016 at 10:36, tsuyoshi wada<EMAIL_ADDRESS>wrote:

No, I think that priority test the work on staging environment. (Sorry
about my poor English...)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tsuyoshiwada/sweet-scroll/issues/27#issuecomment-241433181,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAvEYlSeDr8vdAwC8dPghvAp10Pg1528ks5qibQCgaJpZM4JlboO
.

Wait, sorry, got it working with:
"sweet-scroll": "git+https://github.com/tsuyoshiwada/sweet-scroll#21bd8a434f
",
Testing now.
On 22 August 2016 at 10:51, Nicole Chung<EMAIL_ADDRESS>wrote:

So I tried
"dependencies": {
"sweet-scroll": "^1.0.4#21bd8a434f",
But I get this error:
npm ERR! No compatible version found<EMAIL_ADDRESS>npm ERR! Valid install targets:
On 22 August 2016 at 10:36, tsuyoshi wada<EMAIL_ADDRESS>wrote:

No, I think that priority test the work on staging environment. (Sorry
about my poor English...)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tsuyoshiwada/sweet-scroll/issues/27#issuecomment-241433181,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAvEYlSeDr8vdAwC8dPghvAp10Pg1528ks5qibQCgaJpZM4JlboO
.


🔥 v1.0.0-beta.12

Fixed Issues
Closes #649  PR: #965 (Dropdown trigger issue on mobile 🚨)
Closes #969  PR: #965 (Dropdown trigger issue on mobile 🚨)
Closes #920 PR: #923
Closes #958 PR: #961
Features
PR: #934 Focus indicator added to shadow buttons
Refactors
PR: #966
📝 Description
New library version, v1.0.0-beta.12
💣 Is this a breaking change (Yes/No): No

📝 Additional Information

Codecov Report

Merging #997 (836751b) into main (db75d45) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Current head 836751b differs from pull request most recent head 49f8161. Consider uploading reports for the commit 49f8161 to get more accurate results

@@           Coverage Diff           @@
##             main     #997   +/-   ##
=======================================
  Coverage   75.85%   75.85%
=======================================
  Files         223      223
  Lines        3528     3529    +1
  Branches     1116     1116
=======================================
+ Hits         2676     2677    +1
  Misses        841      841
  Partials       11       11

Impacted Files
Coverage Δ

packages/react/src/button/button.styles.ts
100.00% <ø> (ø)

packages/react/src/button/index.ts
100.00% <ø> (ø)

packages/react/src/card/use-card.ts
70.58% <ø> (ø)

packages/react/src/checkbox/checkbox.tsx
100.00% <ø> (ø)

packages/react/src/modal/modal.tsx
95.34% <ø> (ø)

packages/react/src/navbar/navbar-item.tsx
55.42% <ø> (ø)

packages/react/src/progress/progress.styles.ts
100.00% <ø> (ø)

packages/react/src/progress/progress.tsx
100.00% <ø> (ø)

packages/react/src/tooltip/tooltip.tsx
97.36% <ø> (ø)

packages/react/src/input/input.styles.ts
100.00% <100.00%> (ø)

... and 2 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Correct some docs typos

Summary
This PR corrects some typos in the documentations
Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.

[x] I've read and agree to the Code of Conduct.

[ ] I've written tests to cover the new code and functionality included in this PR.

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

Cheers for the documentation updates 🙇


[RESOLVED] High ICMP ping response time

Problem started at 08:37:16 on 2023.04.25
Problem name: High ICMP ping response time
Host: ST-FG
Severity: Warning
Operational data: Value: 801ms
Original problem ID: 19943
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23135&eventid=19943

Problem has been resolved in 1m 0s at 08:38:16 on 2023.04.25
Problem name: High ICMP ping response time
Host: ST-FG
Severity: Warning
Original problem ID: 19943


How to change date?

I want change date by country. How?

calendar.locale=yourLocale

Thanks!
I want to do something like this. How?

It's one of the dataSource methods.
- (NSString *)calendar:(FSCalendar *)calendar subtitleForDate:(NSDate *)date;


osbuild2: new stage authconfig

This pull request includes:

[ ] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

@msehnout this PR needs rebasing. This will become an issue with all of your PRs adding support for new stages. I would suggest to either add them all to a single PR or rebase them on top of each other in some order and then merge in that order to not force you to rebase after each merge.

@msehnout this PR needs rebasing. This will become an issue with all of your PRs adding support for new stages. I would suggest to either add them all to a single PR or rebase them on top of each other in some order and then merge in that order to not force you to rebase after each merge.

Yes, I know. My plan is to merge them into a single PR for simplicity.

Thanks for the reviews, I've merged my PRs into a single one. Please have a look at #2006.


ci: move arm builds from cross compilation

Fix cross-compilation issues by moving to arm-based builders for arm images.
Signed-off-by: Maciej Obuchowski<EMAIL_ADDRESS>

Were you able to test the ARM builds in CI?

Ah, I see https://app.circleci.com/pipelines/github/OpenLineage/OpenLineage/3294/workflows/3bfb87e0-dc92-4ec3-b92e-a19a7fae597b which seems to exercise those builds


Appointments Error with date range End Time, never displays

Expected behavior:
Allow selecting End Time Minutes on Appointments.
Actual behavior:

All types of appointments fail to display the selected minutes.
Clinic Appointments fail to save because of lack of end time minutes, even after the minutes have been selected.
*** Only happens on fresh load of module.  Any additional appointment works as 1) above.

Steps to reproduce:

Select Appointments

Click '+ new appointment'

Chose Type 'Clinic'

Uncheck "All Day'

Fill in the boxes

Click 'Add'
The result is a popup about filling in the required fields.
** This only happens on the 1st try at an appointment.
Screenshots (if applicable):

OS and Browser:
Ubuntu 16.04  & Firefox

I can't reproduce this on beta.hospitalrun.io. Can you try it again?

@garylm I refactored how this component works.  I haven't seen this particular issue, but given the change I just made, the issue you encountered should no longer happen.

Works for me…  I just updated and it now works as expected.
Nice Work
Gary
Gary Miller
gary<EMAIL_ADDRESS>From: John Kleinschmidt<EMAIL_ADDRESS>Sent: Tuesday, December 13, 2016 1:50 PM
To: HospitalRun/hospitalrun-frontend<EMAIL_ADDRESS>Cc: Gary Miller<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [HospitalRun/hospitalrun-frontend] Appointments Error with date range End Time, never displays (#812)
Closed #812https://github.com/HospitalRun/hospitalrun-frontend/issues/812 via c0d191fhttps://github.com/HospitalRun/hospitalrun-frontend/commit/c0d191fa9dd2e7d914b77d8dc3a3dbf1932ba37b.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/HospitalRun/hospitalrun-frontend/issues/812#event-892746037, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABZ3GyPlg4OhPTOfpnhakiRnazxW8ZW9ks5rHxMMgaJpZM4K1M1O.

Now Works for me…  I just updated and it now works as expected.
The problem has been fixed.
Gary
Gary Miller
gary<EMAIL_ADDRESS>From: Quan Chau<EMAIL_ADDRESS>Sent: Monday, December 12, 2016 6:20 PM
To: HospitalRun/hospitalrun-frontend<EMAIL_ADDRESS>Cc: Gary Miller<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [HospitalRun/hospitalrun-frontend] Appointments Error with date range End Time, never displays (#812)
I can't reproduce this on beta.hospitalrun.io. Can you try it again?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/HospitalRun/hospitalrun-frontend/issues/812#issuecomment-266616177, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABZ3Gw9j2Hixn5JlROHWvsVKzajqQmkZks5rHgDEgaJpZM4K1M1O.


Running during yaml BUILd pipeline and v5 results in 'You cannot call a method on a null-valued expression'

During our swap over from classic pipelines we want to do post-deployment tasks for updating apim. This has previously been done in classic releasepipeline so configuration should work and we have used the 'export yaml' part.
Also tested doing adjuments to configuration but i cannot get it to work.
As others have said here I've tested downgrading TLS to 1.0 from 1.2 but this didn't solve anything.
Services: Azure deveops
Agent: Microsoft hosted
Pipeline: Yaml
Pipeline type: build pipe
Task version: 5.0.1
Task: API Management - Create/Update API
checking whether https://management.azure.com/subscriptions/xx/resourceGroups/xx/providers/Microsoft.ApiManagement/service/xx/apis/xx?api-version=2019-01-01 exists
##[debug]GET https://management.azure.com/subscriptions/xx/resourceGroups/xx/providers/Microsoft.ApiManagement/service/xx/apis/xx?api-version=2019-01-01 with 0-byte payload
##[debug]received 1489-byte response of content type application/json; charset=utf-8
found api
##[debug]Leaving D:\a\_tasks\apimversioned_caee5262-b7ce-48c9-b5f7-70c586148ff8\5.0.1\apimversioned.ps1.
##[debug]Caught exception from task script.
##[debug]Error record:
##[debug]D:\a\_tasks\apimversioned_caee5262-b7ce-48c9-b5f7-70c586148ff8\5.0.1\apimversioned.ps1 : You cannot call a method on a null-valued expression.
##[debug]At line:1 char:1
##[debug]+ . 'D:\a\_tasks\apimversioned_caee5262-b7ce-48c9-b5f7-70c586148ff8\5.0 ...
##[debug]+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
##[debug]    + CategoryInfo          : InvalidOperation: (:) [apimversioned.ps1], RuntimeException
##[debug]    + FullyQualifiedErrorId : InvokeMethodOnNull,apimversioned.ps1
##[debug]
##[debug]Script stack trace:
##[debug]at <ScriptBlock>, D:\a\_tasks\apimversioned_caee5262-b7ce-48c9-b5f7-70c586148ff8\5.0.1\apimversioned.ps1: line 367
##[debug]at <ScriptBlock>, <No file>: line 1
##[debug]at <ScriptBlock>, <No file>: line 22
##[debug]at <ScriptBlock>, <No file>: line 18
##[debug]at <ScriptBlock>, <No file>: line 1
##[debug]Exception:
##[debug]System.Management.Automation.RuntimeException: You cannot call a method on a null-valued expression.
##[debug]   at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
##[debug]   at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
##[debug]   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
##[debug]   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
##[debug]   at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)
##[debug]   at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)
##[debug]   at System.Management.Automation.PSScriptCmdlet.RunClause(Action`1 clause, Object dollarUnderbar, Object inputToProcess)
##[debug]   at System.Management.Automation.PSScriptCmdlet.DoEndProcessing()
##[debug]   at System.Management.Automation.CommandProcessorBase.Complete()
##[error]You cannot call a method on a null-valued expression.
##[debug]Processed: ##vso[task.logissue type=error]You cannot call a method on a null-valued expression.
##[debug]Processed: ##vso[task.complete result=Failed]

I have not and i see that i dont have added the configuration(s) tested. Once i start tackle this again i will post configuration updates


Please support computed properties for :disabled props on el-button component

Please elaborate your problem, maybe with an example or online demo.


Update sensitive browsing designs to allow re-blurring of search results

This is blocked until further user feedback or testing indicates it is necessary.

Problem

The sensitive browsing project proposal includes one feature not present in the design files. We discussed and decided to wait on this feature:

Users can unblur and reblur individual results through a simple and clear interaction on the search results page.

This means the desired flow for single results, as described in the plan, is something like this:
graph TB
    A(User searches) --> B(User views results w/ sensitive results)
    B --> C(User unblurs a sensitive result)
    C --> D(User can re-blur the result)  --> B
    C --> E(User visits the single result view) --> B

Description

We need to add this in the search results designs; perhaps with the 👁 button in the bottom corner of results as indicated by Francisco previously.
Alternatives

Additional context

Aside to the discussion, that is an impeccable diagram 👨🍳👌. Nice to know that GitHub supports mermaid natively.

Closing. Single results can be unblurred on the single result page, and will remain blurred when re-visiting the search results. I believe the current flow matches the mermaid chart here.


Restore baseline legend and update line color to match

Put the "1.0" back on the axis and restore the legend box for baseline CRuby.
Make baseline thicker and use it to underline the legend instead of using a box.
refs https://github.com/Shopify/yjit-metrics/pull/257#issuecomment-2132619982

👍
off topic: I kind of miss the ability to see Ruby 3.4 YJIT speedup (CRuby 3.4.0dev / YJIT 3.4.0dev), but I guess that task is for somewhere else now.

Yeah. I don't think we should add more complexity to the graph as it would make it harder to interpret. It seems simpler to have all bars be relative to the same baseline. This graph is designed to give us a good sense of the progress we're making wrt the previous version of CRuby/YJIT.

We can certainly add another graph...
With the home page using previous CRuby as the baseline, maybe we would want a new page with various graphs using a  baseline of current CRuby.
We also could allow you to click on a version and dynamically update the bars to be relative to that, if that was interesting to anyone.

In think in the short term I would rather focus on redesigning the front page to have the info we need the most.
We could do a phase 2 with more improvements after that. If there are going to be more graphs, I would rather they be somewhere else because I think it's easy to overwhelm people with too much data. It's important to focus people's attention on key information (minimalism).


Panic when zooming out a plot too far

I wasn't able to check if it is present on main by reproducing it but the code that causes the panic is still there.
Describe the bug

I was experimenting with zooming using the right mouse button. And while doing so seems I hit an edge case and the program suddenly closed. Checking the console I discovered that it had panicked. Seem I managed to accidentally try to zoom by exactly 0.0 and there is an assert to check that the amount is not 0.0 hence it crashed. While this is hard to recreate it is not impossible, might be worth adding a check before calling next_power so that it doesn't panic but instead does nothing as that seems to make sense for a zoom by 0.
Error message:
thread 'main' panicked at /home/one/.cargo/registry/src/index.crates.io-6f17d22bba15001f/egui_plot-0.23.0/src/lib.rs:1877:5:
assertion `left != right` failed
  left: -0.0
 right: 0.0
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

To Reproduce
Given the nature of the bug I was unable to reproduce it as it requires zooming on a plot with the right mouse button and getting exactly 0 for the amount of zoom.
Expected behavior

I think nothing should happen instead of a panic as the user may trigger this (even though it is unlikely)
Screenshots
N/A

Desktop (please complete the following information):

OS: Ubuntu 22.04.01
Browser: N/A running native when crashed
Version: 23

I think this could be closes with #4637 ?!

I think this could be closes with #4637 ?!

No - I can still reproduce on egui.rs after zooming out for a minute or so


Set a published date on static spec builds to fix search engines

They seem to love promoting old versions of the spec, which is less than helpful

see https://developers.google.com/search/docs/advanced/appearance/publication-dates for example

Looks like the new spec site already has a Last modified date at the bottom of the page


Flutter run crashes when deploying to iOS device

Steps to Reproduce
Using the versions of the software below, flutter run to deploy to an iOS device (I'm using an iPhone 6s running iOS v9.3)
Flutter Doctor
[✓] Flutter (on Mac OS, channel alpha)
• Flutter at /Users/djshuckerow/.flutter
• Framework revision 646b5350d1 (23 hours ago), engine revision 7fab0c350b
[✓] Android toolchain - develop for Android devices (Android SDK 23.0.2)
• Android SDK at /Users/djshuckerow/Library/Android/sdk
• Platform android-N, build-tools 23.0.2
• Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
[✓] iOS toolchain - develop for iOS devices (Xcode 7.3)
• XCode at /Applications/Xcode.app/Contents/Developer
• Xcode 7.3, Build version 7D175
[✓] Atom - a lightweight development environment for Flutter
• Atom installed; Flutter plugin version 0.2.2
Logs and Crash Reports
[....] Waiting for iOS device to be connected
[....] Using N71mAP 'First's iPhone' (a1b07916f5d38432c3e4dde4a427b14a23ee16ab).
------ Install phase ------
[  0%] Found N71mAP 'First's iPhone' (a1b07916f5d38432c3e4dde4a427b14a23ee16ab) connected through USB, beginning install
[  5%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/META-INF/ to device
[  5%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/META-INF/com.apple.ZipMetadata.plist to device
[  6%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/_CodeSignature/ to device
[  6%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/_CodeSignature/CodeResources to device
[  7%] Copying<EMAIL_ADDRESS>to device
[  7%] Copying<EMAIL_ADDRESS>to device
[  8%] Copying<EMAIL_ADDRESS>to device
[  8%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/AppIcon29x29~ipad.png to device
[  9%] Copying<EMAIL_ADDRESS>to device
[ 10%] Copying<EMAIL_ADDRESS>to device
[ 10%] Copying<EMAIL_ADDRESS>to device
[ 11%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/AppIcon40x40~ipad.png to device
[ 11%] Copying<EMAIL_ADDRESS>to device
[ 12%] Copying<EMAIL_ADDRESS>to device
[ 12%] Copying<EMAIL_ADDRESS>to device
[ 13%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/AppIcon76x76~ipad.png to device
[ 14%] Copying<EMAIL_ADDRESS>to device
[ 14%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/embedded.mobileprovision to device
[ 15%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Frameworks/ to device
[ 16%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Frameworks/Flutter.framework/ to device
[ 16%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Frameworks/Flutter.framework/_CodeSignature/ to device
[ 17%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Frameworks/Flutter.framework/_CodeSignature/CodeResources to device
[ 18%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Frameworks/Flutter.framework/Flutter to device
[ 35%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Frameworks/Flutter.framework/icudtl.dat to device
[ 38%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Frameworks/Flutter.framework/Info.plist to device
[ 39%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Frameworks/FlutterApplication.framework/ to device
[ 40%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Frameworks/FlutterApplication.framework/_CodeSignature/ to device
[ 40%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Frameworks/FlutterApplication.framework/_CodeSignature/CodeResources to device
[ 41%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Frameworks/FlutterApplication.framework/app.flx to device
[ 42%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Frameworks/FlutterApplication.framework/FlutterApplication to device
[ 43%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Frameworks/FlutterApplication.framework/Info.plist to device
[ 44%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Frameworks/libGoogleSignIn.dylib to device
[ 45%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Info.plist to device
[ 46%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/LaunchScreen.storyboardc/ to device
[ 46%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/LaunchScreen.storyboardc/01J-lp-oVM-view-Ze5-6b-2t3.nib to device
[ 47%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/LaunchScreen.storyboardc/Info.plist to device
[ 47%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/LaunchScreen.storyboardc/UIViewController-01J-lp-oVM.nib to device
[ 48%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/PkgInfo to device
[ 48%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/Runner to device
[ 49%] Copying appdir/ios/.generated/build/Release-iphoneos/Runner.app/ServiceDefinitions.json to device
[ 52%] CreatingStagingDirectory
[ 57%] ExtractingPackage
[ 60%] InspectingPackage
[ 60%] TakingInstallLock
[ 65%] PreflightingApplication
[ 65%] InstallingEmbeddedProfile
[ 70%] VerifyingApplication
[ 75%] CreatingContainer
[ 80%] InstallingApplication
[ 85%] PostflightingApplication
[ 90%] SandboxingApplication
[ 95%] GeneratingApplicationMap
[100%] Installed package ios/.generated/build/Release-iphoneos/Runner.app
------ Debug phase ------
Starting debug of N71mAP 'First's iPhone' (a1b07916f5d38432c3e4dde4a427b14a23ee16ab) connected through USB...
[  0%] Looking up developer disk image
[ 95%] Developer disk image mounted successfully
[100%] Connecting to remote debug server
Traceback (most recent call last):
File "", line 1, in
File "/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources/Python/lldb/init.py", line 98, in
import six
ImportError: No module named six
(lldb) command source -s 0 '/tmp/fruitstrap-lldb-prep-cmds-a1b07916f5d38432c3e4dde4a427b14a23ee16ab'
Executing commands in '/tmp/fruitstrap-lldb-prep-cmds-a1b07916f5d38432c3e4dde4a427b14a23ee16ab'.
(lldb)     platform select remote-ios --sysroot '/Users/djshuckerow/Library/Developer/Xcode/iOS DeviceSupport/9.3.2 (13F69)/Symbols'
Platform: remote-ios
Connected: no
SDK Path: "/Users/djshuckerow/Library/Developer/Xcode/iOS DeviceSupport/9.3.2 (13F69)/Symbols"
(lldb)     target create "appdir/ios/.generated/build/Release-iphoneos/Runner.app"
Traceback (most recent call last):
File "", line 1, in
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
File "", line 1, in
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
File "", line 1, in
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
File "", line 1, in
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
File "", line 1, in
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
File "", line 1, in
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
File "", line 1, in
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
File "", line 1, in
NameError: name 'run_one_line' is not defined
Current executable set to 'appdir/ios/.generated/build/Release-iphoneos/Runner.app' (arm64).
(lldb)     script fruitstrap_device_app="/private/var/containers/Bundle/Application/81470E90-2EC5-4AD5-8E24-37F315162BB3/Runner.app"
Traceback (most recent call last):
File "", line 1, in
NameError: name 'run_one_line' is not defined
error: python failed attempting to evaluate 'fruitstrap_device_app="/private/var/containers/Bundle/Application/81470E90-2EC5-4AD5-8E24-37F315162BB3/Runner.app"'

For more information about diagnosing and reporting Flutter bugs, please see https://flutter.io/bug-reports/.

See https://github.com/flutter/flutter/issues/4269 where we think the issue is due to a homebrew install of python being in the user's path and that confusing Apple's python code.

Removing the brew python works as a workaround to the issue, but I wouldn't mark this as closed until there's a proper fix.

Presumably the fix is to clear the PATH from the environment before invoking any xcode commands.
Others have hit this or related, btw:
https://github.com/dropbox/dropbox-sdk-python/issues/62
https://github.com/pypa/pip/issues/3165

Yeah, I suspect people usually run Xcode from the app launcher, which probably has a different environment than they use in their shell.

Correct.  If this theory holds xcodebuild should fail similarly from the command line.

Added a doctor check in #7807

Has anyone run into the immediate crash using TestFlight? I'm able to deploy successfully to device via debugging. Deploying via TestFlight causes an immediate crash. Bitcode is set to NO. Tried setting Optimization Level to None too. Any ideas? Doesn't even cause a crash log on the device.

Updated the fix and eliminated the doctor check in #19281.


pagination remains after new search entry

so we should reset to first page if keywords changed, right?

Yes! This would be a better UX