Adds possibility to override the built-in report printer

The built-in default is used if none is explicitly configured.
The reason for this is to be able to produce e.g. TAP output so the
library theoretically can be used with existing pretty printers.

I am willing to improve the patch if you have any suggestions? I think it could be nice if it was possible to "stream" results to a plugin. I.e. for each assert, there could be a callback invoked or something.

@roobie This is awesome! Thanks so much for submitting the PR :D I made some minor changes to make the style consistent with the remainder of the code. Let me know what you think!

@roobie Streaming results could be interesting. Would your idea be to add a variable that would be called instead of compose-and-record-result (but with that set as the default)? Similar to how the report printer works. Or would there need to be broader architectural changes?

:+1: Looks much better now! Sorry for being sloppy :) - I'll do better next time. I think your idea about making the compose-and-record-result configurable will cover the use case. If you don't mind, I'll take a stab at making it so and also implement a TAP-style printer.

Actually, having taken a closer look, I don't think we need to make the compose-and-record-result configurable, but instead we can have a (var- compose-and-record-result-hook)-function that can be set, and in the compose-and-record-result we call the hook, if set to a function.

@roobie Oh nice idea! I'll merge this now but please feel free to add that as a separate PR :)


Refactoring

Description
As a software developer, I want the PDXFinder resource to be a toolkit of microservices.

Refactoring is done.


Fix formatting for payload and context

Description
Fix formatting for payload and context in order to send json objects instead of strings.
Fixes # (issue)
Type of change
What is it?

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I run make pre-commit to check fmt/vet/lint/test-no-fdo

Codecov Report
Base: 49.59% // Head: 49.62% // Increases project coverage by +0.03% :tada:

Coverage data is based on head (7883499) compared to base (97c2429).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1839      +/-   ##
==========================================
+ Coverage   49.59%   49.62%   +0.03%
==========================================
  Files          70       70
  Lines        9847     9847
==========================================
+ Hits         4884     4887       +3
+ Misses       4499     4497       -2
+ Partials      464      463       -1

Impacted Files
Coverage Δ

pkg/services/images.go
32.70% <0.00%> (ø)

pkg/services/devices.go
51.11% <0.00%> (+0.31%)
:arrow_up:

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Corrected readme run command

What does this PR do?
The command for running the agent was missing "run" By using the command as is, users will see the datadog agent help information rather than starting the agent. This PR corrects the command so that it will actually start the agent.
Motivation
I was following your documentation to use the agent and noticed a typo
Additional Notes
Anything else we should know when reviewing?

Thanks @hudsonmd!


Make "support" a property of TreeNode

Please complete the following checklist:

[x] I have read the guidelines in CONTRIBUTING.md.

[x] I have documented all public-facing changes in CHANGELOG.md.

[ ] This pull request includes code, documentation, or other content derived from external source(s). If this is the case, ensure the external source's license is compatible with scikit-bio's license. Include the license in the licenses directory and add a comment in the code giving proper attribution. Ensure any other requirements set forth by the license and/or author are satisfied. It is your responsibility to disclose code, documentation, or other content derived from external source(s). If you have questions about whether something can be included in the project or how to give proper attribution, include those questions in your pull request and a reviewer will assist you.

[x] This pull request does not include code, documentation, or other content derived from external source(s).

Note: REVIEWING.md may also be helpful to see some of the things code reviewers will be verifying when reviewing your pull request.

This pull request involves a notable change to the original logic of TreeNode. Please read and think carefully. Following our previous discussions @wasade @RNAer @mortonjt , I changed support from a method to a property. Along with this change,

The support property has a default value of None. It will not be assigned when a Newick tree is read. This is because branch support values are not part of the Newick standard. They are just denoted as node labels in most practices.
A new method assign_supports. It traverses a tree and attempts to extract support values from all internal node labels. The logic is similar to assign_ids. Therefore, if the user wants to get support values from a Newick tree, they need to execute tree.assign_supports() once.
The way a node label is printed is revised. It becomes support:name if both apply, or support or name if either applies. This affects both str and ascii_art. The way a node label is printed is consistant before and after assign_supports. This ensures backward compatibility with previous versions of scikit-bio.

For example, a Newick tree is ((a,b)'75:Ecoli':1.6,(c,d)Mtb:1.4,(e,f)80)root;. In this case, node Ecoli has a support value of 75, the node Mtb has no support value, and the node joining e and f has a support value of 80. After assign_supports is executed, the name of node Ecoli becomes 'Ecoli', and the support property is assigned integer 75. When one prints the manipulated tree, the output is consistent with the original form.
IMPORTANT: Mathematically, "support value" is a property of a branch, not a node. It is usually marked as a node label because of historical and convenience reasons. This practice has caused confusions in many studies and bioinformatics tools, especially in the re-rooting operation, which is necessary in many applications. Please check out this article in 2017:
A Critical Review on the Use of Support Values in Tree Viewers and Bioinformatics Toolkits
The current PR does not address the re-rooting problem. But as we proceed we will have to consider it seriously. I already have a working prototype that can correctly handle re-rooting with support values. It is quite complicated.
So please read and decide whether we should seriously go down this path (making support a property). Then we can take care of rooting.

Hi @wasade @antgonza @charles-cowart This is the scikit-bio pull request we discussed during Monday's code review. I resolved the conflicts. Could anyone merge it? Thanks!


What does this statement means - "The designed Windows for Business configuration has you give the Key Admins "

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

ID: 6ca080bd-ed37-60a8-ec22-b1929166ff0c
Version Independent ID: d2742e0c-9d66-4b1f-8555-a1fb1546455b
Content: Passwordless Strategy - Microsoft 365 Security
Content Source: windows/security/identity-protection/hello-for-business/passwordless-strategy.md
Product: w10
Technology: windows
GitHub Login: @mapalko
Microsoft Alias: mapalko

@rishtech . From my knowledge based,  passwordless configuration will be configured by the
organization systm admin. if device is joined in azure.
For standard device, that is not joined to azure, hence the users will configure as their their needs, hence there is no interaction between users and system administrator

It seems that the question has been answered by the community,  and thus the issue is being marked as resolved.
Thank you.

Dear @e0i , @raju2529.
I believe that @rishtech is telling about article https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-feature-dual-enrollment as the mentioned wording is not presented in the Password Strategy article.
"The designed Windows for Business configuration has you give the Key Admins (or KeyCredential Admins when using domain controllers prior to Windows Server 2016) group read and write permissions to the msDS-KeyCredentialsLink attribute." means that Key Admins group got the permission to change msDS-KeyCredentialsLink attribute in the AD during the configuration of Windows Hello for Business. I think that the wording should be changed as the correct one incorrect and confusing.
I will create a PR.
Thank you

Its beyond my knowledge

@MaratMussabekov , Thanks for understand the exact issue.
@e0i , First of all I would like to understand, what do you mean by it seems, is there any review process for feedback closure, or it is an autonomous function.
FYI, the question and answer is nowhere related.

@MaratMussabekov , Thanks for understand the exact issue.
@e0i , please read @MaratMussabekov response.

I would also like to note that the phrasing in the first sentence

The designed Windows for Business configuration has you give the Key Admins

uses poorly phrased English grammar (I am pretty certain that @JohanFreelancer9 will agree), as if the phrasing has been translated word-for-word from a different language.
I would have suggested a better syntax right now, but I need to consider the implications for a while.


wireframe example: use FixedUpdate instead of a timer

Objective

Since #7328, wireframe screenshot in CI is not deterministic

Solution

Use FixedUpdate instead of a timer

Wait, I thought I removed that timer in the colored wireframe PR. Was it not merged?

Nice, thanks!


Revamp simulation comparison barcharts

User Story
Follow-up from #28, work in progress…

Patch is testable here https://wikicarbone.beta.gouv.fr/branches/revamp-simulation-summary/#/simulator


Add Jojo Stone Ocean Part 3 and Update Part 2

Note: Part 2 and Part 3 are combined in AniList

Hey @sitiom, thanks for the PR. Two questions before merging this:

Was removing the ! from the first rule intentional? (Usually happens by mistake, but still wanted to ask before adding it back.)
What's the purpose of redirecting Part 2 to Part 3? (I don't think we have any other rules similar to that.)

2. What's the purpose of redirecting Part 2 to Part 3? (I don't think we have any other rules similar to that.)

I was thinking about AniList, but so far no release group has combined parts 2 and 3 together. So I'll remove it.

Was removing the ! from the first rule intentional? (Usually happens by mistake, but still wanted to ask before adding it back.)

Part 2 -> 3 redirect doesn't work without it. But I'll bring it back since the redirect will be removed.


Salesforce Disabling TLS 1.0 Encryption (..in 2016)

Just cleaning out my email inbox and wanted to make sure this is on the radar.
This email from Salesforce June 15 alerts that they are phasing out TLS 1.0 support
Not super familiar with the internal workings of django-salesforce or python's ssl packages but took a spin and spotted ssl_version = ssl.PROTOCOL_TLSv1 in adapter.py. Not sure if it defaults to 1.1 or it needs to be named explicitly? Would this be an issue?

Well, the constants for the newer versions of TLS don't exist until Python 2.7.9. I'm not opposed to dropping 2.6 support, but I'm not sure how I feel about dropping pre-2.7.9 Python 2.7 support.
Of course, if there's no other option, it is what it is.

Yes, we must fix it.
The request package doesn't allow to specify what is the minimal required SSL version together with the directive to allow to use the highest SSL/TLS version available for both sides. (requests issue 2118)  I think that it is more secure to require explicitely the lowest version supported by SFDC than to allow an arbitrary (old broken) version that can be false reported by "man in the middle" attacker as the highest supported by the server. I implemented the restriction after the last change made by SFDC and I did set it to curent TLS v 1.0. Now we must make the TLS version configurable and set the default version to TLS 1.1 to be easy to verify readiness of deploments of django-salesforce in advance.
The standard solution of TLS 1.1 and 1.2 for Python older than 2.7.9 is by installing additional packages:
pip install pyopenssl ndg-httpsclient pyasn1

More information can be found in requests package in docs string site-packages/requests/packages/urllib3/contrib/pyopenssl.py
Now we must check the presence of ssl.PROTOCOL_TLSv1_1 and recommend these packages if the constant is not found (that means Python is old).

Fixed.
There is no reason to add that warning above. This installation seems entirely at the discretion of the user now.

I wrote tests for SSL/TLS in PR #119 with useful suggestions and additional logic if it fails.
I presume now that, though enabled SSL 3 is a big problem generally, it is not a big threat if we know that SFDC disabled that protocol completely without any "safe" downgrade mechanism. I can not reproduce the re-enabled SSL3 problem with pyOpenSSL again after writing more tests and compilated more Python versions etc. Yes, I know one way how pyOpenSSL can re-enable it, but it can be disabled now by more ways.


yaqc-bluesky Binder  fails to launch

https://github.com/bluesky/yaqc-bluesky

Binder has gotten quite a bit more limited in available resources, and is not regularly used... If its easy to fix, I'm all for it, but may have to look elsewhere (or focus on better local install docs...)
I tried removing the extension things, but it still got the last/fatal error, which is rather inscrutable, as it says it got what it expected, but then says they are a mismatch... that may be an upstream bug?
Looks like @untzag is doing a bit more extensive of a look into it than I did yet...
Unfortunately I expect the multiprocess nature of yaq is a poor candidate for some newer solutions like pyscript/pyodide/jupyterlite, but may be worth experimenting with...

https://github.com/bluesky/yaqc-bluesky/pull/95

To be honest @nfortune we never use binder. If it ends up working again and you use it, I'd be curious if you find it useful or if you would prefer a different form of documentation for yaqc-bluesky. I just don't use notebooks for running instruments.

I appreciate the effort that was made to make a binder example available,
but my interest is in the  documentation and examples, not in binder
itself. Rather than putting more time into debugging binder, could you
please post  the  material from that non working setup   in some other form
(for example, in the form of a yaq fyi blog post or static notebook) ? I am
new to blue sky as well as yaq and could use more information  on how  the
two commands shown in the read me are embedded in a blue sky script or
setup. Thanks!
On Wed, Aug 2, 2023 at 03:17 Blaise Thompson @.***>
wrote:

To be honest @nfortune https://github.com/nfortune we never use binder.
If it ends up working again and you use it, I'd be curious if you find it
useful or if you would prefer a different form of documentation for
yaqc-bluesky. I just don't use notebooks for running instruments.
—
Reply to this email directly, view it on GitHub
https://github.com/yaq-project/yaq-fyi/issues/75#issuecomment-1661318651,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACDUMELJJCT3HNKELWFT5D3XTGTBPANCNFSM6AAAAAA27XUBEE
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Professor Nathanael Fortune
315 McConnell Hall
44 College Lane
Smith College
Northampton MA 01063
https://www.smith.edu/academics/faculty/nathanael-fortune
http://www.smith.edu/physics/
(413) 585-3980 (office)
(413) 585-3919 (lab)
@.***
gendered pronouns: he/him/his
There’s only one thing more painful than learning from experience, and
that is not learning from experience. — Archibald MacLeish.

That's good feedback @nfortune, I actually think you're right that a blog post might be a better form of documentation. You could also run the notebooks locally if you wish (in the "binder" directory).
I'll try to give a few sentences here about how these pieces fit together, in case it's helpful to you. Bluesky handles orchestration and data collection in a really sophisticated way, but doesn't have any built-in direct hardware support. To do an experiment in Bluesky you provide the plan with "device" objects that have certain special methods that Bluesky needs (read, set, describe, etc). yaqc-bluesky provides a Device class which is a yaq client that's made to be plugged into Bluesky plans.
https://blueskyproject.io/bluesky/hardware-interfaces.html

Got it.  You're saying that yacq-bluesky provides the interface to BlueSky
---  replacing *ophyd * ---- and the yaq daemons correspondingly replace
EPICS in the BlueSky project hierarchy.  You wouldn't use ophyd to
communicate with a daemon. This differs from say, InstrBuilder (an
apparently abandoned alternative hardware interface) which replaces EPICS
but still uses ophyd as its interface to  Bluesky.
Nat Fortune

On Wed, Aug 2, 2023 at 2:11 PM Blaise Thompson @.***>
wrote:

That's good feedback @nfortune https://github.com/nfortune, I actually
think you're right that a blog post might be a better form of
documentation. You could also run the notebooks locally if you wish (in the
"binder" directory).
I'll try to give a few sentences here about how these pieces fit together,
in case it's helpful to you. Bluesky handles orchestration and data
collection in a really sophisticated way, but doesn't have any built-in
direct hardware support. To do an experiment in Bluesky you provide the
plan with "device" objects that have certain special methods that Bluesky
needs (read, set, describe, etc). yaqc-bluesky provides a Device class
which is a yaq client that's made to be plugged into Bluesky plans.
https://blueskyproject.io/bluesky/hardware-interfaces.html
—
Reply to this email directly, view it on GitHub
https://github.com/yaq-project/yaq-fyi/issues/75#issuecomment-1662096764,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACDUMEK5DWRHG2LISFK2GK3XTI7VNANCNFSM6AAAAAA27XUBEE
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Professor Nathanael Fortune
315 McConnell Hall
44 College Lane
Smith College
Northampton MA 01063
https://www.smith.edu/academics/faculty/nathanael-fortune
http://www.smith.edu/physics/
(413) 585-3980 (office)
(413) 585-3919 (lab)
@.***
gendered pronouns: he/him/his
There’s only one thing more painful than learning from experience, and
that is not learning from experience. — Archibald MacLeish.

You got it, 100%


calculate_energy_used is probably incorrect with 3 phase-charging

Describe the bug
The formula on line https://github.com/adriankumpf/teslamate/blob/382a63de15dca5837acb807c8a2dc969b6a58889/priv/repo/migrations/20191026185642_calculate_charge_energy_used.exs#L81
c.charger_actual_current * c.charger_voltage * c.charger_phases / 1000.0

should be
c.charger_actual_current * c.charger_voltage * sqrt(c.charger_phases) / 1000.0

as per https://www.engineeringtoolbox.com/three-phase-electrical-d_888.html.
In any case it probably is incorrect. I charged yesterday evening. I measured 8.51 kWh on the Watt-counter for my tesla charging station. Teslamate tells me that for 8.48 kWh added charge, 15.44 kWh electricity was used. If I divide 15.44 kWh by sqrt(3) I get to 8.914 kWh which would be really close to what was measured.

I'm not an expert on the subject but the phase to phase voltage is different from the phase to neutral voltage. E.g. in Europe the phase to phase voltage is 400V, which gives 230V phase to neutral voltage: 400/sqrt(3) = 230. That is why the used formula works.
Of course, that doesn't explain the discrepancy you're seeing. I can think of a few causes of error:

There was no stable internet connection at the charge location (missing data)
There was an incorrectly configured 'phase correction' for the geo-fence at the charge location
The API has (temporarily) reported wrong values

What's the reported 'energy used' for your other charges?

I just started using it now so I only have one charge. The technician who installed my wall box assured me that I don't have 400V, only 230V. 400V is only for industrial users. I'll see how my other charges are being reported and report back.

Well, now this is not so correct. After my second charge, I see the attached in charges:

I started charging at 18:24 with SOC about 16% or something. My counter reads 56.64kWh.

In my teslamate output:
> 18:46:48.793 [info] GET /
> 18:46:48.871 [info] Sent 200 in 77ms
> 20:01:22.371 car_id=1 [warn] Error / upstream timeout
> 20:06:29.853 [error] Task #PID<0.11235.8> started from :"1" terminating
> ** (stop) exited in: GenServer.call(TeslaMate.Api, {:get_with_state,<PHONE_NUMBER>5359560}, 35000)
>     ** (EXIT) time out
>     (elixir) lib/gen_server.ex:1009: GenServer.call/3
>     (teslamate) lib/teslamate/vehicles/vehicle.ex:727: TeslaMate.Vehicles.Vehicle.fetch_with_reachable_assumption/2
>     (elixir) lib/task/supervised.ex:90: Task.Supervised.invoke_mfa/2
>     (elixir) lib/task/supervised.ex:35: Task.Supervised.reply/5
>     (stdlib) proc_lib.erl:249: :proc_lib.init_p_do_apply/3
> Function: #Function<2.116134789/0 in TeslaMate.Vehicles.Vehicle.handle_event/4>
>     Args: []
> 20:07:00.794 car_id=1 [warn] Error / upstream timeout
> 20:07:36.955 car_id=1 [warn] Error / upstream timeout
> 20:08:20.209 car_id=1 [warn] Error / upstream timeout
> 20:08:56.183 car_id=1 [warn] Error / upstream timeout
> 20:09:20.447 car_id=1 [info] Start / :online
> 20:09:20.556 [info] Querying location for elevation takes longer than 100ms ...
> 20:09:23.400 car_id=1 [info] Charging / SOC: 34% / Home
> 20:10:51.767 car_id=1 [warn] Error / upstream timeout
> 20:11:27.856 car_id=1 [warn] Error / upstream timeout
> 20:52:28.122 [info] GET /geo-fences/new
>

Another charge and again wildly off the mark. I measured 40.04 kWh. It says used 70.41 kWh.

In my teslamate output:
...

It looks like the internet connection wasn't very good at the time/location. The estimation of the kWh used relies on a stable connection. So that could be the issue.
I'll need your charge data and the application logs at the time of your last charge(s) to find out more. To export the data run these commands (while the database container is running):
docker-compose exec db psql teslamate teslamate -c \
   "COPY (select * from charges) TO STDOUT WITH CSV" > charges.csv && \
docker-compose exec db psql teslamate teslamate -c \
   "COPY (select * from charging_processes) TO STDOUT WITH CSV" > charging_processes.csv

Hi, the charge yesterday was with a perfect connection so that should not have been an issue. The second charge indeed had an interrupted internet connection twice which you see in the charges.
charges.zip

Something is wrong with the reported data. It doesn't add up. For example, your car reports
218V * 19A * 3 Phases = 12426W but it effectively charges with 7 kW. You can see for yourself in the Charge Details. If the input values are incorrect, the result can of course not be correct. I guess there's nothing we can do about that, unfortunately.

Hi Adrian, that's why I think the used formula is incorrect. 218V * 19A * sqrt(3) phases = 7174.
Also the measured charge (40.04) almost exactly matches the reported charge (70.41) / sqrt(3) = 40.65.
I'm quite sure that it charges at 19A (that's reported on the screen in my car) and I'm also sure that it's three phases @ 220 V.
Do you have anybody else charging at home with a wall charger at 3 phases?

Do you have anybody else charging at home with a wall charger at 3 phases?

Well, I am ;) And I know of others TM users who also have a 3-phase charger at home. And the estimates are accurate in all of these cases (some Model 3 owners need to manually enable the phase correction). If anyone with more expertise on this subject could explain the measurements you are seeing, I'd like to know.

At what wattage and voltage are you charging?

Looking into it, Belgium (and other countries) have 127/230V three-phase networks. You're effectively charging with 127V and that's why dividing by sqrt(3) gives you the correct result. To me, it feels like the car should report 127V instead of 220V then? But there's probably a good reason for that ...
I don't have the time to implement a country-specific workaround at the moment. You can, however, customize the dashboard and do the calculation yourself:

sign in with the default user admin (password is admin)
Click edit on the table and update the SQL query
Save the dashboard as JSON and import it as a new dashboard

Mmm, indeed but this is only going to work for my home set up. I would probably have to code it in https://github.com/adriankumpf/teslamate/blob/382a63de15dca5837acb807c8a2dc969b6a58889/priv/repo/migrations/20191026185642_calculate_charge_energy_used.exs#L81
Should there not be a way to recover from bad internet connections during charging?

Good news: I had the idea for an automatic and generic phase/voltage correction mechanism. I used your charge data to test it and It turned out to work surprisingly well. It'll ship with the next release.

Thanks!


Container won't run if domain doesn't exist

When setting the registry with -r, if there's nothing in the domain you run, the container won't run. This is ok if you run the image as is, but if you want to use a reverse proxy like nginx it's a problem. This change is recent, in the verson v0.9.0 it did work.
PD: Thanks for your work! This UI is awesome.

Hey @drym3r if I get it right you have the issue where when you run reg-server -r my.privateregistry.com with my.privateregistry.com not being reachable, the server doesn't start. right?
To me this is a normal usecase since the reg-server needs to be able to contact the registry to get images informations. Maybe I'm misunderstanding...

more details would help here for sure

but I agree if the domain does not exist it should fail so closing for now until we get more information


Make sure the next request after refreshing the auth token starts a n…

…ew session with the new token.
Otherwise the subsequent requests still use the old token and continue to bomb.

Coverage increased (+0.004%) to 91.09% when pulling 5db47dece1563f4028e27374e406e55f8b0099a2 on zgohr:refresh-restart-session into 4cb2b6da46423bad8b32b85d87f9a97b698144fd on sidecars:master.


Using Catch All parameters with ui-sref

I currently have a n-level deep route which can consist of a variable number of segments (ie directory browser).  I have the following state set up:
.state("folders", {
    url: "system/*folderPath",
    controller: "FolderController",
    templateUrl: "folders.html"
})

The transition is then navigated through an ui-sref
Link
The ui-sref works fine and the location is changed to system/folder1/folder2 however the link that shows up in the browser when you hover over it is system/folder1%2Ffolder2 because the value is passed through encodeURIComponent
What I am proposing is that for catch all route parameters, the value gets uri encoded, but should leave any forward slashes in, or at least have an option to make it work like that.
I can get around it by using ng-href to compose the uri, however then I lose the funtionality of ui-sref-active.
I did a quick and dirty hack of changing UrlMatcher.prototype.format to use
if (value != null) {
        if (this.sourcePath.indexOf("*" + params[i]) >= 0)
            result += value;
        else
            result += encodeURIComponent(value);
    }

but that only works for the shorthand *parameterName syntax.  The better way would probably be to keep a record of the catch-all parameters when the url format is parsed and use that to determine how to encode the value.
Let me know your thoughts

Encountered a similar problem like @dmitry-dedukhin. Navigating to a state that has an url like: '/someAction/{id}/*params', makes two calls to the server for the template associated with the state.

Just wanted to add that I have the same issue with the URLs. Does anyone have a hacky workaround until someone creates a core-modification to resolve this?

Ignore that, spoke too soon. It works as far as clicking the links in the browser works, but inspecting/copying the generated href shows it is still encoded. I still need a workaround like @Xiot suggested, although in keeping with the any type I used this:
result += param.type.name == 'any' ? encoded : encodeURIComponent(encoded);

I like the idea of basing it off of the type.
Maybe we would want a special 'path' type as well that would encode everything except for the slashes. That way we would get the benefits of both worlds

@Xiot I think this should do it. I've set up a new type which, on encoding, splits it by / and then in the format function still uses the encodeURIComponent for each path component and then joins it by / again.

I've hit this same issue, the fix from @lopsided works a treat.  Any chance of it getting merged in @nateabele? It really does make the URLs much more pleasant

Unfortunately, this problem got a whole lot worse with the new release.
Urgh, can anyone think of a good fix other than using someone else's branch?

I use commas instead of slashes for this very case.

+1


Pascals Triangle

Detailed description
Demonstrating Pascal's triangle using C++
Context
operations on a data structure can be performed to implement Pascal's triangle.
please allow me with this issue with relevant tags under hacktoberfest

pascals triangles is not really an algorithm

pascals triangles is not really an algorithm

isn't it technically more of a math problem?

pascals triangles is not really an algorithm

isn't it technically more of a math problem?

The question is should we put it in the repo?

pascals triangles is not really an algorithm

isn't it technically more of a math problem?

The question is should we put it in the repo?

I do think it won't be a bad idea to add it, it has lots of interesting implementations with recursion, stacks ...


[BUG] Issue with firebase firestore

Describe the bug
It's shifting build directory inside android/app/ and Firestore not working in release. After remove agora, Firestore starts working normally and build directory is also in normal place.
To Reproduce
Steps to reproduce the behavior:
Just simple single line firestore operation.
Desktop (please complete the following information):

OS: Mac OS Big Sur 11.0

Smartphone (please complete the following information):

Device: Tried on android 11, real device & emulator

Sorry for the late reply. Can you describe what you mean by shifting build directory? And can you send the logs as well

Normally the build directory is /build but after adding the package the build directory going inside /android/app
There's nothing unnecessary in the log.

@holy-dev Can you please confirm if this occurs with iOS as well? And, for Android, you can try changing your project directory inside build.gradle

@holy-dev Closing this issue for now. Feel free to open it again if you're still facing this issue.


updated the client listener

now it checks that locusts started spawning (user_count > 0) and checks when they all finished hence the execution can quit (user_count == 0)

Hi @IgalKorb ! Maybe I am confused, but what problem does this PR solve?


consistent sorting on event time / name

Most pages doesn't seem to enforce any kind of consistent sorting on the data.
E.g. members page change sorting randomly.
My suggesting is to apply ordering like this where possible (order of importance)

sort by event time with newest first on resources where such an event time is present
sort by criticality (running/status, with bad states first) and then on name
sort by name

ideally i would like to change the sorting in the UI as well

duplicate of #4


Add documentation for the order of client decoration

Related: #1117
To-do:
Add documentation for server side

Thanks, @minwoox !

Thanks, reviewers!


feat: add CollectionGroup#getPartitions(long)

Add new method to CollectionGroup allowing getPartitions to return a Future<List<QueryPartition>>. This new method behaves similar to the CollectionGroup#getPartitions(long, ApiStreamObserver<QueryPartition>) providing a Future centric api.

With the code that is in the PR right now, the future transform takes place on one of the gax threads leaving the invoking thread unblocked as can be seen in the following log snippet.
2021-01-07T21:38:31.080 [main] com.google.cloud.firestore.CollectionGroup - getPartitions(3)...
2021-01-07T21:38:31.098 [main] com.google.cloud.firestore.CollectionGroup - getPartitions(3) complete
2021-01-07T21:38:31.098 [main] com.google.cloud.firestore.CollectionGroup - calling future.get()...
2021-01-07T21:38:31.255 [Gax-4] com.google.cloud.firestore.CollectionGroup - transform->apply()
2021-01-07T21:38:31.260 [main] com.google.cloud.firestore.CollectionGroup - calling future.get() complete

If I change the implementation to adapt the existing ApiStreamObserver method like so
  public ApiFuture<List<QueryPartition>> getPartitionss(long desiredPartitionCount) {
    final SettableApiFuture<List<QueryPartition>> future = SettableApiFuture.create();
    getPartitions(desiredPartitionCount, new ApiStreamObserver<QueryPartition>() {
      final List<QueryPartition> accumulator = new ArrayList<>();
      @Override
      public void onNext(QueryPartition value) {
        accumulator.add(value);
      }

      @Override
      public void onError(Throwable t) {
        future.setException(t);
      }

      @Override
      public void onCompleted() {
        future.set(accumulator);
      }
    });
    return future;
  }

The invocations on the observer are done from the invoking thread meaning the future isn't really effective.
2021-01-07T21:38:50.196 [main] com.google.cloud.firestore.CollectionGroup - getPartitions(3)...
2021-01-07T21:38:50.301 [main] com.google.cloud.firestore.CollectionGroup - CollectionGroup.onNext
2021-01-07T21:38:50.303 [main] com.google.cloud.firestore.CollectionGroup - CollectionGroup.onNext
2021-01-07T21:38:50.303 [main] com.google.cloud.firestore.CollectionGroup - CollectionGroup.onCompleted
2021-01-07T21:38:50.303 [main] com.google.cloud.firestore.CollectionGroup - getPartitions(3) complete
2021-01-07T21:38:50.304 [main] com.google.cloud.firestore.CollectionGroup - calling future.get()...
2021-01-07T21:38:50.304 [main] com.google.cloud.firestore.CollectionGroup - calling future.get() complete

I thought about using rpcContext.getClient().getExecutor().submit(...) to wrap the call to getPartitions but that executor is the grpc-transport threadpool which we definitely don't want to block.
2021-01-07T21:44:20.290 [main] com.google.cloud.firestore.CollectionGroup - getPartitions(3)...
2021-01-07T21:44:20.292 [main] com.google.cloud.firestore.CollectionGroup - getPartitions(3) complete
2021-01-07T21:44:20.293 [main] com.google.cloud.firestore.CollectionGroup - calling future.get()...
2021-01-07T21:44:20.453 [grpc-transport-0] com.google.cloud.firestore.CollectionGroup - CollectionGroup.onNext
2021-01-07T21:44:20.455 [grpc-transport-0] com.google.cloud.firestore.CollectionGroup - CollectionGroup.onNext
2021-01-07T21:44:20.455 [grpc-transport-0] com.google.cloud.firestore.CollectionGroup - CollectionGroup.onCompleted
2021-01-07T21:44:20.455 [main] com.google.cloud.firestore.CollectionGroup - calling future.get() complete

With the code that is in the PR right now, the future transform takes place on one of the gax threads leaving the invoking thread unblocked as can be seen in the following log snippet.
2021-01-07T21:38:31.080 [main] com.google.cloud.firestore.CollectionGroup - getPartitions(3)...
2021-01-07T21:38:31.098 [main] com.google.cloud.firestore.CollectionGroup - getPartitions(3) complete
2021-01-07T21:38:31.098 [main] com.google.cloud.firestore.CollectionGroup - calling future.get()...
2021-01-07T21:38:31.255 [Gax-4] com.google.cloud.firestore.CollectionGroup - transform->apply()
2021-01-07T21:38:31.260 [main] com.google.cloud.firestore.CollectionGroup - calling future.get() complete

If I change the implementation to adapt the existing ApiStreamObserver method like so
  public ApiFuture<List<QueryPartition>> getPartitionss(long desiredPartitionCount) {
    final SettableApiFuture<List<QueryPartition>> future = SettableApiFuture.create();
    getPartitions(desiredPartitionCount, new ApiStreamObserver<QueryPartition>() {
      final List<QueryPartition> accumulator = new ArrayList<>();
      @Override
      public void onNext(QueryPartition value) {
        accumulator.add(value);
      }

      @Override
      public void onError(Throwable t) {
        future.setException(t);
      }

      @Override
      public void onCompleted() {
        future.set(accumulator);
      }
    });
    return future;
  }

The invocations on the observer are done from the invoking thread meaning the future isn't really effective.
2021-01-07T21:38:50.196 [main] com.google.cloud.firestore.CollectionGroup - getPartitions(3)...
2021-01-07T21:38:50.301 [main] com.google.cloud.firestore.CollectionGroup - CollectionGroup.onNext
2021-01-07T21:38:50.303 [main] com.google.cloud.firestore.CollectionGroup - CollectionGroup.onNext
2021-01-07T21:38:50.303 [main] com.google.cloud.firestore.CollectionGroup - CollectionGroup.onCompleted
2021-01-07T21:38:50.303 [main] com.google.cloud.firestore.CollectionGroup - getPartitions(3) complete
2021-01-07T21:38:50.304 [main] com.google.cloud.firestore.CollectionGroup - calling future.get()...
2021-01-07T21:38:50.304 [main] com.google.cloud.firestore.CollectionGroup - calling future.get() complete

I thought about using rpcContext.getClient().getExecutor().submit(...) to wrap the call to getPartitions but that executor is the grpc-transport threadpool which we definitely don't want to block.
2021-01-07T21:44:20.290 [main] com.google.cloud.firestore.CollectionGroup - getPartitions(3)...
2021-01-07T21:44:20.292 [main] com.google.cloud.firestore.CollectionGroup - getPartitions(3) complete
2021-01-07T21:44:20.293 [main] com.google.cloud.firestore.CollectionGroup - calling future.get()...
2021-01-07T21:44:20.453 [grpc-transport-0] com.google.cloud.firestore.CollectionGroup - CollectionGroup.onNext
2021-01-07T21:44:20.455 [grpc-transport-0] com.google.cloud.firestore.CollectionGroup - CollectionGroup.onNext
2021-01-07T21:44:20.455 [grpc-transport-0] com.google.cloud.firestore.CollectionGroup - CollectionGroup.onCompleted
2021-01-07T21:44:20.455 [main] com.google.cloud.firestore.CollectionGroup - calling future.get() complete


Add Firewall Versioning and Improve Config Management

Features

Store firewall version and updatedAt in local config for better tracking and management. (47f81a2)
Replace retryOperation with a new retry utility to enhance retry handling. (47f81a2)
Update FirewallService to use fetchActiveFirewallRules for fetching rules, ensuring up-to-date rule sets. (47f81a2)
Add validateAndUpdateConfig to ensure configuration consistency after synchronization. (47f81a2)
Enhance download and sync commands to handle updated config metadata, improving operational reliability. (47f81a2)
Improve error handling and logging for better debugging and traceability. (47f81a2)

Refactoring

Remove extra newline character in logged output to streamline log readability. (bd0e8ed)

Resolves of #12


+OrderedSet add filter #158

Resolves #158
This adds a missing operation on OrderedSet: filter that keeps the return type an OrderedSet.
The dictionary in this package already had such operation, so I followed its prior art.
One could debate if we want to preallocate the size as "same" of the current set before filtering or if not etc... Open to suggestions, it's a bit tricky to know if the result of the filter will be almost empty, or almost full after all.
Checklist

[x] I've read the Contribution Guidelines
[x] My contributions are licensed under the Swift license.
[x] I've followed the coding style of the rest of the project.
[x] I've added tests covering all new code paths my change adds to the project (if appropriate).
[ ] I've added benchmarks covering new functionality (if appropriate).

dictionary filter didn't seem to have one either

[x] I've verified that my change does not break any existing tests or introduce unexplained benchmark regressions.
[x] I've updated the documentation if necessary.

docc

@swift-ci please smoke test

@swift-ci please test

@swift-ci please test

Fixed the formatting, thanks @xwu -- though on that note I'd really suggest adding a CI step to verify formatting.
Manually maintaining and checking these isn't tangible. We do this in all server projects we maintain with a "soundness" CI step: https://github.com/apple/swift-distributed-actors/blob/main/scripts/soundness.sh Feel free to take those scripts (validate_format), we're using them in all server side repos we maintain.

@swift-ci please test


[BUG] <starknet_py.abi.v2.parser.AbiParsingError>

What happened
starknet_py.abi.v2.parser.AbiParsingError: L1 handler in ABI must be defined '
'at most once
Stack trace
address = '0x06b4a7b1a9e8addfbf3b36ffe95033187a0116fc7c7b52adfd5590b26359ec3b'
contract = await Contract.from_address(address=address, provider=account)
this went wrong
address = '0x02e0af29598b407c8716b17f6d2795eca1b471413fa03fb145a5e33722184067'
contract = await Contract.from_address(address=address, provider=account)
this is okay
Steps to reproduce

Mainnet

SDK Version
0.19.0
Python version
3.10.13
What operating system are you using?
Mac
Is there an existing issue for this?

[ ] I have searched the existing issues and verified no issue exits for this problem.

Currently, starknet.py parser doesn't parse correctly if a contract has more than one l1_handler


Draft : [ONEToolchain] Implement compiler of ONEToolchain

This commit implements compiler of ONEToolchain.
related issue: #1272  #1285
ONE-vscode-DCO-1.0-Signed-off-by: Nakhyun Kim<EMAIL_ADDRESS>Co-authored-by: Yeonjeong Lee<EMAIL_ADDRESS>Co-authored-by: Hyeryeong Jeong<EMAIL_ADDRESS>

We pulled the changes from the main branch and they are merged to our branch. So every changed file in main branch is now in our file chages. Is it okay to have another files from merge in our file chages?

We pulled the changes from the main branch and they are merged to our branch. So every changed file in main branch is now in our file chages. Is it okay to have another files from merge in our file chages?

Sure, draft PR can include anything you want. :)

PR test fails because of OneExplorer. Do we have to consider this file too...?


How do you close all open cells programmatically?

How do you close all open cells programmatically?

You can take all visible cells and use unfold function
@objc open func unfold(_ value: Bool, animated: Bool = true, completion: (() -> Void)? = nil)
Hope it will help you, otherwise you can reopen this issue and provide more information


Passing arguments to test.py shell command

Hello I am using test.py to generate prediction json file.
For some reason the shell can't read the arguments.
Can anyone help me please ??
`path='/home/ranim/Documents/mmdet/media/Page_00287_jpg.rf.6a823c5ce3894f223a0e8f4ec20b11b2/article1'
save='/home/ranim/Documents/mmdet/media/Page_00287_jpg.rf.6a823c5ce3894f223a0e8f4ec20b11b2/article1/annotations.json'
call('python "/home/ranim/Documents/mmdet/mmdetection/tools/test.py"
"/home/ranim/Documents/mmdet/models/second_model_conf.py"
"/home/ranim/Documents/mmdet/models/second_model_checkpoint.pth"
--cfg-options data.test.ann_file=save
data.test.img_prefix=path
--format-only
--options "jsonfile_prefix=path"', shell=True)`

My bad i just used fstring and the problem is solved.


"HTTPClient::KeepAliveDisconnected: Broken pipe" error

After upgrading my MacOS to 10.15.7, the error started.
The error message is below.
"HTTPClient::KeepAliveDisconnected: Broken pipe"
[15:06:24]: ----------------------------------
[15:06:24]: --- Step: upload_to_play_store ---
[15:06:24]: ----------------------------------

+---------------------------------+-----------------------------------------------------+
|                              Summary for supply 2.169.0                               |
+---------------------------------+-----------------------------------------------------+
| aab                             | ../build/app/outputs/bundle/release/app-release.aab |
| skip_upload_metadata            | true                                                |
| skip_upload_changelogs          | true                                                |
| skip_upload_screenshots         | true                                                |
| skip_upload_images              | true                                                |
| skip_upload_apk                 | true                                                |
| package_name                    | com.raymond.sudoku9flutter2                         |
| release_status                  | completed                                           |
| track                           | production                                          |
| metadata_path                   | ./fastlane/metadata/android                         |
| json_key                        | key.json                                            |
| skip_upload_aab                 | false                                               |
| validate_only                   | false                                               |
| check_superseded_tracks         | false                                               |
| timeout                         | 300                                                 |
| deactivate_on_promote           | true                                                |
| ack_bundle_installation_warning | false                                               |
+---------------------------------+-----------------------------------------------------+

[15:06:29]: Preparing aab at path '../build/app/outputs/bundle/release/app-release.aab' for upload...
+-------------------------------------+-----------------+
|                     Lane Context                      |
+-------------------------------------+-----------------+
| DEFAULT_PLATFORM                    | android         |
| PLATFORM_NAME                       | android         |
| LANE_NAME                           | android release |
| GRADLE_ALL_APK_OUTPUT_PATHS         | []              |
| GRADLE_ALL_AAB_OUTPUT_PATHS         | []              |
| GRADLE_ALL_OUTPUT_JSON_OUTPUT_PATHS | []              |
| GRADLE_ALL_MAPPING_TXT_OUTPUT_PATHS | []              |
+-------------------------------------+-----------------+
[15:06:59]: HTTPClient::KeepAliveDisconnected: Broken pipe

$ fastlane env
[✔] 🚀
[15:20:53]: fastlane detected a Gemfile in the current directory
[15:20:53]: However, it seems like you didn't use `bundle exec`
[15:20:53]: To launch fastlane faster, please use
[15:20:53]:
[15:20:53]: $ bundle exec fastlane env
[15:20:53]:
[15:20:53]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[15:21:00]: Generating fastlane environment output, this might take a few seconds...
<details><summary>🚫 fastlane environment 🚫</summary>

### Stack

| Key                         | Value                                                   |
| --------------------------- | ------------------------------------------------------- |
| OS                          | 10.15.7                                                 |
| Ruby                        | 2.7.2                                                   |
| Bundler?                    | false                                                   |
| Git                         | git version 2.24.3 (Apple Git-128)                      |
| Installation Source         | /usr/local/Cellar/fastlane/2.169.0/libexec/bin/fastlane |
| Host                        | Mac OS X 10.15.7 (19H114)                               |
| Ruby Lib Dir                | /usr/local/Cellar/ruby/2.7.2/lib                        |
| OpenSSL Version             | OpenSSL 1.1.1g  21 Apr 2020                             |
| Is contained                | false                                                   |
| Is homebrew                 | true                                                    |
| Is installed via Fabric.app | false                                                   |
| Xcode Path                  | /Applications/Xcode.app/Contents/Developer/             |
| Xcode Version               | 12.2                                                    |

### System Locale

| Error                       |
| --------------------------- |
| No Locale with UTF8 found 🚫 |

### fastlane files:

<details><summary>`./fastlane/Fastfile`</summary>

```ruby
default_platform(:android)

platform :android do
  def increment_version_code()
    path = '../app/build.gradle'
    re = /versionCode\s+(\d+)/

    s = File.read(path)
    versionCode = s[re, 1].to_i
    s[re, 1] = (versionCode + 1).to_s

    f = File.new(path, 'w')
    f.write(s)
    f.close
  end

  def increment_version_number(bump_type: nil, version_number: nil)
    path = '../app/build.gradle'
    re = /versionName\s+("\d+.\d+.\d+")/
    s = File.read(path)
    versionName = s[re, 1].gsub!('"','').split('.')

    major = versionName[0].to_i
    minor = versionName[1].to_i
    patch = versionName[2].to_i

    if (bump_type == 'major')
        major += 1
        minor = 0
        patch = 0
    elsif (bump_type == 'minor')
        minor += 1
        patch = 0
    elsif (bump_type == 'patch')
        patch += 1
    end

    if(version_number)
      s[re, 1] = "\"#{version_number}\""
    else
      s[re, 1] = "\"#{major}.#{minor}.#{patch}\""
    end

    f = File.new(path, 'w')
    f.write(s)
    f.close
    increment_version_code()
  end

  def updateVersion(options)
    if options[:version]
      version = options[:version]
    else
      version = prompt(text: "Enter the version type or specific version\n(major, minor, patch or 1.0.0): ")
    end

    re = /\d+.\d+.\d+/
    versionNum = version[re, 0]

    if (versionNum)
      increment_version_number(
        version_number: versionNum
      )
    elsif (version == 'major' || version == 'minor' || version == 'patch')
      increment_version_number(
        bump_type: version
      )
    else
      UI.user_error!("[ERROR] Wrong version!!!!!!")
    end
  end

  desc "Submit a new Beta Build to Crashlytics Beta"
  lane :beta do |options|
    updateVersion(options)

    gradle(task: "clean bundleRelease")
    upload_to_play_store(
      aab: "../build/app/outputs/bundle/release/app-release.aab",
      skip_upload_metadata: true,
      skip_upload_changelogs: true,
      skip_upload_screenshots: true,
      skip_upload_images: true,
      skip_upload_apk: true,
      track: 'internal'
    )
  end

  desc "Deploy a new version to the Google Play"
  lane :release do |options|
    updateVersion(options)

    gradle(task: "clean bundleRelease")
    upload_to_play_store(
      aab: "../build/app/outputs/bundle/release/app-release.aab",
      skip_upload_metadata: true,
      skip_upload_changelogs: true,
      skip_upload_screenshots: true,
      skip_upload_images: true,
      skip_upload_apk: true
    )
    notification(title: "Finished", message: "The build was successfully uploaded",  sound: "Hero")
  end

  desc "Deploy a new version to the Google Play"
  lane :newbuild do
    increment_version_code()

    gradle(task: "clean bundleRelease")
    upload_to_play_store(
      aab: "../build/app/outputs/bundle/release/app-release.aab",
      skip_upload_metadata: true,
      skip_upload_changelogs: true,
      skip_upload_screenshots: true,
      skip_upload_images: true,
      skip_upload_apk: true
    )
    notification(title: "Finished", message: "The build was successfully uploaded",  sound: "Hero")
  end

end

`./fastlane/Appfile`
json_key_file("key.json")
package_name("com.raymond.sudoku9flutter2")

fastlane gems

Gem
Version
Update-Status

fastlane
2.169.0
🚫 Update available

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.4.0

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
3.0.2

claide
1.0.3

colored2
3.1.2

nanaimo
0.3.0

xcodeproj
1.19.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
4.0.6

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

babosa
1.0.4

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.78.0

ruby2_keywords
0.0.2

faraday
1.1.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

fastimage
2.2.0

gh_inspector
1.1.3

mini_magick
4.11.0

rubyzip
2.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.6

bundler
2.1.4

naturally
2.2.0

simctl
1.6.8

jwt
2.2.2

uber
0.1.0

declarative
0.0.20

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mini_mime
1.0.2

multi_json
1.15.0

signet
0.14.0

memoist
0.16.2

os
1.1.1

googleauth
0.14.0

httpclient
2.8.3

google-api-client
0.38.0

google-cloud-env
1.4.0

google-cloud-errors
1.0.1

google-cloud-core
1.5.0

rake
13.0.1

digest-crc
0.6.1

google-cloud-storage
1.29.1

emoji_regex
3.2.1

jmespath
1.4.0

aws-eventstream
1.1.0

aws-sigv4
1.2.2

aws-sdk-core
3.109.3

aws-sdk-kms
1.39.0

aws-sdk-s3
1.86.0

uri
0.10.0

json
2.3.1

aws-partitions
1.402.0

forwardable
1.3.1

logger
1.4.2

cgi
0.1.0

timeout
0.1.0

stringio
0.1.0

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.2.0

strscan
1.0.3

date
3.0.0

delegate
0.1.0

fileutils
1.4.1

io-console
0.5.6

zlib
1.1.0

singleton
0.1.0

rexml
3.2.3

open3
0.1.0

yaml
0.1.0

psych
3.1.0

mutex_m
0.1.0

webrick
1.6.0

generated on: 2020-12-16

[15:21:01]: Take notice that this output may contain sensitive information, or simply information that you don't want to make public.
/usr/local/Cellar/fastlane/2.169.0/libexec/gems/highline-1.7.10/lib/highline.rb:624: warning: Using the last argument as keyword parameters is deprecated
[15:21:01]: 🙄  Wow, that's a lot of markdown text... should fastlane put it into your clipboard, so you can easily paste it on GitHub?
(y/n)
/usr/local/Cellar/fastlane/2.169.0/libexec/gems/highline-1.7.10/lib/highline.rb:624: warning: Using the last argument as keyword parameters is deprecated
             y
[15:21:25]: Successfully copied markdown into your clipboard 🎨
[15:21:25]: Open https://github.com/fastlane/fastlane/issues/new to submit a new issue ✅
#######################################################################
fastlane 2.170.0 is available.
You should use the latest version.
Please update using fastlane update_fastlane.
#######################################################################
Run sudo gem cleanup from time to time to speed up fastlane
#######################################################################
2.170.0 Improvements and Upload App Privacy Details

[Fastlane.swift] fixed potential undefined method `action_name' in generator (#17660) via phil zhang
[action] onesignal - update onesignal.rb to include optional organization_id (#17696) via Brandon Carpenter
[deliver] fix a regression in language detection in Deliver::UploadMetadata (#17730) via Satoshi Namai
[action] NEW ACTION for App Data Usages: upload_app_privacy_details_to_app_store (#17592) via Josh Holtz
[match] only include enabled devices for force_for_new_devices (#17695) via Steven Roebert

For more information on uploading App Privacy Details, go to https://docs.fastlane.tools/uploading-app-privacy-details/
Please update using fastlane update_fastlane

The error message from Apple AppStore is below. I think it is related to the error when uploading to Google play store.
303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 8)
[15:30:44]: [Transporter Error Output]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 9)
[15:30:44]: [Transporter Error Output]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 12)
[15:30:44]: [Transporter Error Output]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 17)
[15:30:44]: [Transporter Error Output]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 7)
[15:30:45]: [Transporter Error Output]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 10)
[15:30:45]: [Transporter Error Output]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 15)
[15:30:45]: [Transporter Error Output]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 19)
[15:30:45]: [Transporter Error Output]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 18)
[15:30:46]: [Transporter Error Output]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 20)
[15:30:46]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:46]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:46]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:46]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:46]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:46]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:46]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Protocol wrong type for socket
[15:30:46]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:46]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:46]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:46]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:46]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:46]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:46]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:47]: [Transporter Error Output]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 6)
[15:30:47]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:47]: [Transporter Error Output]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 3)
[15:30:47]: [Transporter Error Output]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 2)
[15:30:48]: [Transporter Error Output]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 4)
[15:30:48]: [Transporter Error Output]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 5)
[15:30:48]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:48]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:48]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:48]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:49]: [Transporter Error Output]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 1)
[15:30:49]: [Transporter Error Output]: java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
[15:30:49]: [Transporter Error Output]: Could not upload 1 file(s):
[15:30:49]: [Transporter Error Output]: Could not upload file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa 20 parts failed: [20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1]
[15:30:49]: [Transporter Error Output]: Please retry your upload later.
[15:33:17]: iTunes Transporter successfully finished its job
[15:33:17]: [iTMSTransporter] [2020-12-16 15:33:17 KST] <main> DBG-X: JSON-START>>{"dev-id-results":{"upload_id":"2132f286-1cde-4fed-8732-9d72da3ccf64"}}<<JSON-END

[15:33:17]: [iTMSTransporter] [2020-12-16 15:33:17 KST] <main> DBG-X: Unlocking token at path /Users/gracegyu/Library/Caches/com.apple.amp.itmstransporter/UploadTokens/MacBook-Pro.local_RaymondJeon1315681454_1541576451.itmsp.token

[15:33:17]: [iTMSTransporter] [2020-12-16 15:33:17 KST] <main> DBG-X: Releasing token file lock

[15:33:17]: [iTMSTransporter] [2020-12-16 15:33:17 KST] <main> DBG-X: Removing token at path /Users/gracegyu/Library/Caches/com.apple.amp.itmstransporter/UploadTokens/MacBook-Pro.local_RaymondJeon1315681454_1541576451.itmsp.token

[15:33:17]: [iTMSTransporter] [2020-12-16 15:33:17 KST] <main>  INFO: Done performing uploadDone notification to Apple.

[15:33:17]: [iTMSTransporter] [2020-12-16 15:33:17 KST] <main>  INFO: Transporter's command line arguments are: -m upload -u<EMAIL_ADDRESS>-p **hidden value** -f /tmp/1541576451.itmsp -k 100000

[15:33:17]: [iTMSTransporter] [2020-12-16 15:33:17 KST] <main>  INFO: The package: /tmp/1541576451.itmsp has been successfully uploaded.

[15:33:17]: [iTMSTransporter]

[15:33:17]: [iTMSTransporter]

[15:33:17]: [iTMSTransporter]

[15:33:17]: [iTMSTransporter] Package Summary:

[15:33:17]: [iTMSTransporter]

[15:33:17]: [iTMSTransporter] 1 packages were uploaded successfully:

[15:33:17]: [iTMSTransporter]   /tmp/1541576451.itmsp

[15:33:17]: [iTMSTransporter] [2020-12-16 15:33:17 KST] <main> DBG-X: Returning 0

[15:33:17]: iTunes Transporter output above ^
[15:33:17]: An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 13)
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 16)
An un-handled exception occurred: java.net.SocketException: Protocol wrong type for socket for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 14)
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 11)
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 8)
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 9)
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 12)
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 17)
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 7)
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 10)
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 15)
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 19)
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 18)
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 20)
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
java.util.concurrent.ExecutionException: java.net.SocketException: Protocol wrong type for socket
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 6)
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 3)
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 2)
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 4)
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 5)
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
An un-handled exception occurred: java.net.SocketException: Broken pipe for (id: CPUSource124/v4/34/c3/a1/34c3a1cb-09bb-b88c-e763-9059f58b4cdd/d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa part: 1)
java.util.concurrent.ExecutionException: java.net.SocketException: Broken pipe
Could not upload 1 file(s):
Could not upload file: d5e3378303fac4ba49bb00475d24b75b2c6a9901fa4e3b09b6a1062e48bd1f9e.ipa 20 parts failed: [20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1]
Please retry your upload later.
[15:33:17]: Although errors occurred during execution of iTMSTransporter, it returned success status.
[15:33:17]: ------------------------------------------------------------------------------------------------------------------
[15:33:17]: --- Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online. ---
[15:33:17]: ------------------------------------------------------------------------------------------------------------------
[15:33:17]: Finished the upload to App Store Connect
[15:33:17]: Running precheck before submitting to review, if you'd like to disable this check you can set run_precheck_before_submit to false
[15:33:17]: Running precheck 👮♀ 👮

I don't think this is related to fastlane as those are 2 different tolls/API we use. I think it's more related to your connection.

I don't think this is related to fastlane as those are 2 different tolls/API we use. I think it's more related to your connection.

I am also encountering this error. I do not believe it to be related to the connection. For me, this runs fine when uploading to the Apple Store but fails when trying the same for Android/Play Store.

I am also encountering this error. I do not believe it to be related to the connection. For me, this runs fine when uploading to the Apple Store but fails when trying the same for Android/Play Store.


Empty space on the right side of the grid

Hello, awesome library, I'm really looking forward to see how it evolves.
Found a little issue: the grid doesn't fill the screen when running on the iPhone 6 Simulator

Thanks for your contribution @eljago. It should be fixed now.


Text doesn't copy

Describe the bug

Copy doesn't copy text onto the clipboard.  Neither the right-click context menu nor selecting "Copy" from the "Edit" menu.

Link to the blitz that caused the error
https://stackblitz.com/run?file=src%2Fapp%2Fcdk-drag-drop-axis-lock-example.html
Steps to reproduce
go to the blitz
Select some text
Right click the text (or) press Ctrl+c (or) select Copy from the Edit menu
Expected behavior
The text should be copied to the clipboard.
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform
Browser name  = Firefox
Full version  = 99.0
Major version = 99
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:99.0) Gecko/20100101 Firefox/99.0
performance.memory = undefined
Hash = be57dda01bcfe1c4973d7980b1ec44aabd3a6863

Additional context
No response

Could you close your browser, reopen it and try again? Or maybe even reboot your computer? I noticed that I sometimes have the same issue in other apps as well. To met it feels like a macOS bug, but I could be wrong. We don't do anything to prevent copy pasting at all.

I'm not using Apple products.  I have since rebooted, but now following the link above no longer works.  So now, it's a new problem.

The project no longer seems to be available and was deleted.

The problem with the link is that it's pointing to stackblitz.com/run which are dynamic projects and don't really exist. Can you remember where you clicked this link? Seems like something in the Angular Material docs maybe?

That sounds about right, yes.  Unfortunately, the moment has passed.  I only even opened the issue since copy/paste not working is such a major problem, the platform is practically unusable without that functionality.

Hi @b264. Not being able to copy/paste is definitely an issue. However, this is not something we actively block and it should work. I currently have no clue why it doesn't work for you, because it works perfectly fine for me. Maybe it's something in the specific example that you opened. Do you have this on every project you open? Do you also experience this issue in Chrome?

@b264 try now... There was a copy shortcut bug that broke the shortcut outside MacOS.


[ENHANCEMENT] Try best to keep grafana PV when upgrading from v112 to v120

Is your enhancement related to a problem? Please describe.

The rancher-monitoring managedchart is converted to addon in  https://github.com/harvester/harvester/issues/2992, and the grafana PV is deleted and re-created. When user have customized data, which may be a loss.
PR: https://github.com/harvester/harvester/pull/3380#issuecomment-1588746799

This should not be a blocker, but may be we should still look at additional logic in the upgrade path to patch the grafana pv's volume retention policy: https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/

This existing pv can then be re-purposed for the upgrade path, but will mean some additional changes to be generated for the values of the addon.

Or we can document how to export/import custom dashboards from grafana, which user may have to perform post the upgrade.

Describe the solution you'd like

First, add this to document.
Second, try to keep the PV.
Describe alternatives you've considered

Additional context

Plan:
(1) In upgrade, patch the ClaimPolicy of Grafana PV, and deleting rancher-monitoring managedchart, remove the ClaimRef to PVC.  Create new addon, it will reuse the PV.
(2) In v1.2.0, via #4108, repeat the actions in (1) when addon is disabled, enabled. Thus the grafana PV will remain there even when rancher-monitoring addon is disabled.

Verified this bug has been fixed.
Test Information

Environment: qemu/KVM 3 nodes
Harvester Version: v1.1.2 -> v1.2.0-rc3
ui-source Option: Auto

Verify Steps

Install Harvester with any nodes
Login to console, record current PVs and PVCs by executing following commands:

kubectl get pv -A | awk '{print $1" "$6}' > pvs
kubectl get pvc -A | awk '{print $2" "$4}' > pvcs

Perform upgrade^1
Upgrade should completed successfully
Login to console, compare upgrade PVs and PVCs by executing following commands:

kubectl get pv -A | awk '{print $1" "$6}' | diff pvs -, output should be empty
kubectl get pvc -A | awk '{print $2" "$4}' | diff pvcs -, output should be empty


Update react-native-webview version

i guess it will be better if this dependency makes as a peer dependency

@ThomasHenrissat could you review it?

I am closing because WebView is a peer dependency since v4.2.0


[language][prover] Restructuring tests, and verifying that the div-by-zero bug is gone.

Motivation
The div-by-zero bug is not longer reproducible, or never was. Also restructures the tests so verification problems are isolated in single files. This avoids mistakes in the tests resulting from inprecise diagnostics, which may have been the reason for the div-by-zero issue.
Have you read the [Contributing Guidelines on pull requests]
Yes
Test Plan
Reorganized tests
Related PRs
NA

@bors-libra r=shazqadeer

:pushpin: Commit 02d40ef has been approved by shazqadeer

:hourglass: Testing commit 02d40ef5ca68e71bfa1ed33092997cc065e27ca9 with merge 35e3801a1f9c91d850f5293d74bc92a825de922c...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: shazqadeer
Pushing 35e3801a1f9c91d850f5293d74bc92a825de922c to master...


cff added

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

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

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
6324

Relevant Lines:
7172

💛  - Coveralls


Fails to build

readline: https://ci.bobbuildtool.dev/jenkins/view/basement/job/basement-libs__readline-1/25/
x86_64-wendy-linux-gnu-gcc -shared -Wl,-soname,libhistory.so.8.0 -Wl,-O1 -Wl,--hash-style=gnu -L/home/jenkins/workspace/basement-libs__readline-1/libs/ncurses-dev/x86_64-wendy-linux-gnu/dist/17-7590-3fdb/usr/lib -L./lib/termcap -Wl,-rpath,/usr/lib -Wl,-soname,`basename libhistory.so.8.0 .0` -o libhistory.so.8.0 history.so histexpand.so histfile.so histsearch.so shell.so mbutil.so xmalloc.so xfree.so -ltinfo
mv compat.o compat.so
mv parse-colors.o parse-colors.so
/home/jenkins/bob/bc/d8bc613012ef866187e74fd2318b08476bc549450a9387162ea23ee9799e2aad55f4a07b4df216-2/content/usr/bin/../lib/gcc/x86_64-wendy-linux-gnu/9.2.0/../../../../x86_64-wendy-linux-gnu/bin/ld: cannot find -ltinfo
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:181: libhistory.so.8.0] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/home/jenkins/workspace/basement-libs__readline-1/libs/readline-tgt/x86_64-wendy-linux-gnu/build/17-7590-3fdb/build/shlib'
make: *** [Makefile:219: shared] Error 2

Python3: https://ci.bobbuildtool.dev/jenkins/view/basement/job/basement-python__python3-1/26/
Failed to build these modules:
_curses               _curses_panel

make: *** [Makefile:616: sharedmods] Error 1

Most probably regression from #51.

@daxcore Could you please have a look at this?

@daxcore Could you please have a look at this?

Hey, i detected the problem, there is a patch file for readline, with statically searchs for tinfo library.
The name of the library with widec feature is suffixed with a 'w' now .
https://github.com/BobBuildTool/basement/blob/7b4528fb883caa9376256da291e6f9201a360ee5/recipes/libs/readline/0000-curses-link.patch#L13
maybe we can remove that patch file and use pkg-config to get the linker flags, if not already fixed in this package version (or we could try to update the package).
I have a wsl ubuntu 16 lts without installed tinfo library. i will fix it, hopefully :)

Hey, i detected the problem, there is a patch file for readline, with statically searchs for tinfo library.
The name of the library with widec feature is suffixed with a 'w' now .
https://github.com/BobBuildTool/basement/blob/7b4528fb883caa9376256da291e6f9201a360ee5/recipes/libs/readline/0000-curses-link.patch#L13
maybe we can remove that patch file and use pkg-config to get the linker flags, if not already fixed in this package version (or we could try to update the package).
I have a wsl ubuntu 16 lts without installed tinfo library. i will fix it, hopefully :)

the second issue occurs because of missing -fPIC while building ncurses.
ofc i could add it to the CFLAGS of the package, but imo we should add this to the global compiler flags.
if i have understood -fPIC correctly, every package in bob should/could have it :)
@jkloetzke  what do u think?

the second issue occurs because of missing -fPIC while building ncurses.
ofc i could add it to the CFLAGS of the package, but imo we should add this to the global compiler flags.
if i have understood -fPIC correctly, every package in bob should/could have it :)
@jkloetzke  what do u think?

Fails to build:
[  20] BUILD     libs::readline-tgt - dev/build/libs/readline-dev/x86_64-wendy-linux-gnu/1/workspace
[  20] |libs::readline-tgt| make[1]: warning: -j4 forced in submake: resetting jobserver mode.
[  20] |libs::readline-tgt| /home/jkloetzke/src/bob/playground/basement/tests/linux/dev/dist/devel/cross-toolchain/1/workspace/usr/bin/../lib/gcc/x86_64-wendy-linux-gnu/9.2.0/../../../../x86_64-wendy-linux-gnu/bin/ld: cannot find -ltinfo
[  20] |libs::readline-tgt| collect2: error: ld returned 1 exit status
[  20] |libs::readline-tgt| make[1]: *** [Makefile:177: libreadline.so.8.0] Error 1
[  20] |libs::readline-tgt| make[1]: *** Waiting for unfinished jobs....
[  20] |libs::readline-tgt| /home/jkloetzke/src/bob/playground/basement/tests/linux/dev/dist/devel/cross-toolchain/1/workspace/usr/bin/../lib/gcc/x86_64-wendy-linux-gnu/9.2.0/../../../../x86_64-wendy-linux-gnu/bin/ld: cannot find -ltinfo
[  20] |libs::readline-tgt| collect2: error: ld returned 1 exit status
[  20] |libs::readline-tgt| make[1]: *** [Makefile:181: libhistory.so.8.0] Error 1
[  20] |libs::readline-tgt| make: *** [Makefile:219: shared] Error 2
[  20] |libs::readline-tgt| Step failed with return status 2; Command: make "$@"
[  20] |libs::readline-tgt| Call stack (most recent call first)
[  20] |libs::readline-tgt|     #0: Class  make, layer self, line 7, in makeParallel
[  20] |libs::readline-tgt|     #1: Class  autotools, layer self, line 77, in autotoolsBuild
[  20] |libs::readline-tgt|     #2: Recipe libs::readline#1, layer self, line 3, in main

About -fPIC: what is the actual problem? Unconditionally adding this switch is certainly not the right thing.

Fails to build:
[  20] BUILD     libs::readline-tgt - dev/build/libs/readline-dev/x86_64-wendy-linux-gnu/1/workspace
[  20] |libs::readline-tgt| make[1]: warning: -j4 forced in submake: resetting jobserver mode.
[  20] |libs::readline-tgt| /home/jkloetzke/src/bob/playground/basement/tests/linux/dev/dist/devel/cross-toolchain/1/workspace/usr/bin/../lib/gcc/x86_64-wendy-linux-gnu/9.2.0/../../../../x86_64-wendy-linux-gnu/bin/ld: cannot find -ltinfo
[  20] |libs::readline-tgt| collect2: error: ld returned 1 exit status
[  20] |libs::readline-tgt| make[1]: *** [Makefile:177: libreadline.so.8.0] Error 1
[  20] |libs::readline-tgt| make[1]: *** Waiting for unfinished jobs....
[  20] |libs::readline-tgt| /home/jkloetzke/src/bob/playground/basement/tests/linux/dev/dist/devel/cross-toolchain/1/workspace/usr/bin/../lib/gcc/x86_64-wendy-linux-gnu/9.2.0/../../../../x86_64-wendy-linux-gnu/bin/ld: cannot find -ltinfo
[  20] |libs::readline-tgt| collect2: error: ld returned 1 exit status
[  20] |libs::readline-tgt| make[1]: *** [Makefile:181: libhistory.so.8.0] Error 1
[  20] |libs::readline-tgt| make: *** [Makefile:219: shared] Error 2
[  20] |libs::readline-tgt| Step failed with return status 2; Command: make "$@"
[  20] |libs::readline-tgt| Call stack (most recent call first)
[  20] |libs::readline-tgt|     #0: Class  make, layer self, line 7, in makeParallel
[  20] |libs::readline-tgt|     #1: Class  autotools, layer self, line 77, in autotoolsBuild
[  20] |libs::readline-tgt|     #2: Recipe libs::readline#1, layer self, line 3, in main

About -fPIC: what is the actual problem? Unconditionally adding this switch is certainly not the right thing.

if the -ltinfo is fixed, than just this error is breaking the build for me:
/home/jenkins/bob/bc/d8bc613012ef866187e74fd2318b08476bc549450a9387162ea23ee9799e2aad55f4a07b4df216-2/content/usr/bin/../lib/gcc/x86_64-wendy-linux-gnu/9.2.0/../../../../x86_64-wendy-linux-gnu/bin/ld: /home/jenkins/workspace/basement-python__python3-1/libs/ncurses-dev/x86_64-wendy-linux-gnu/dist/17-7590-3fdb/usr/lib/libncursesw.a(lib_set_term.o): relocation R_X86_64_32S against undefined symbol `_nc_outch_sp' can not be used when making a shared object; recompile with -fPIC

oups. i failed :-/ thx!


changed default sprite size to 32 to work better with large datasets

I changed the default sprite size to 32 to fix issues that I was having facets crash when trying to display a dataset with 33 columns and 90k records.  It was suggested by @jimbojw to set the sprite to 32 pixels, so here is the PR for that.  The Issue (reported by me) is located here:
https://github.com/PAIR-code/facets/issues/115#issuecomment-378941849
I tested the suggest change on my dataset (no longer crashes) and tested just this change locally on the default dataset in facets. Let me know if there is anything else I need to do.

I signed it!

Thanks for sending us a PR. Unfortunately, the smaller the sprite size, the fewer pixels are available for rendering text, causing it to appear pixelated. I'm concerned that this would make smaller data sets look worse. Is there any way we could dynamically compute a good default based on the data set size?

@jimbojw yeah I can do that, I just worry about adding the additional complexity to a code sample.  This is the first time I really used this but for mine I was just using "credit score" to fill the display which is only 3 digits and looks fine at 32px, but i don't know what kind of items other people would be filling each dot with.  Can you give me some examples that you are using on the "display" so I can imagine it better?  Ill adjust this PR, what would you suggest the breakpoint should be when switching between 64 and 32px? 50k records?

I made a new PR integrating your concerns and making it dynamic:
https://github.com/PAIR-code/facets/pull/119

let me know if that doesnt work


Resourceful Caster + Destructive Dispel + dispel magic bug

So when you have destructive dispel and resourceful caster and you cast on a target and they save from all the destructive dispel saves it gives you the spell back per resourceful caster. Probably not the worst bug ever, and I guess debatable if that's not intended but I figure since it's a spell rider instead of the spell itself it might not be what you were going for.

Yeah that is undesirable. Including the dispel action into the logic should be no problem.

Fixed in 1.2.4


FCOS3D on Waymo

Have you tried to train FCOS3D model on the Waymo dataset? Or could you provide a config file for this setting? Many thanks in advance!

Not yet. Our dataset APIs and models generally support KITTI-style settings, so you can basically follow that way to have some attempts on Waymo.


Add error messages for invalid status/query types and add the new types.

This is the fix for #23
Let me know if you would rather raise the exception in the case of an invalid Status/Query type.
Other option I see are to pass the query/status type integer as is.

Looks good to me! Merged.


Design and preview window very different

I created a view hierarchy using Boxsizers. The layout looks correct on the Design window. In the preview window most of the widgets are missing.
The design window is on top. The preview window is on the bottom.

This is the wxg file:
example.zip
My info:
wxGlade 1.0.0b1
wxPython 4.1.0
Python 2.7.18
Windows XP

The structure of a scrolled window in a sizer etc. will not work. By incident wxGlade does display better than what will come out finally.
See this update with a more useful structure:
example_update.zip

P.S.: Don't use (grid) sizers to present data. Use proper structures like grid or listctrls.


[DC-324] accessing google buckets can fail resulting in error notifications for users

When using Terra UI we get a lot of error notifications around google buckets not being accessible.
This can cause test flakiness and also manifests in production, where users tend to see error notifications.
Google recommends retry logic for these requests
Where to Start
Take a look at the ajax.js file, specifically at some of the wrapper functions. withErrorRejection is a simple example to start with.
Create a wrapper function that will retry a request after failure. A key property of a wrapper function is that it should return a function with the same signature as the function that was passed in (again see withErrorRejection)
This is something that can be done in a standalone fashion, if that makes it easier. You can create a wrapper that retries any function upon receiving an error.
It’s Done when
Our google api calls in ajax.js are wrapped in retry logic.
For testing, you can use the browser dev tools to block access to API’s to simulate a failed request

Do we have reason to believe that retrying is going to help? I know that in our dev environment, we have many workspaces where the bucket information never will load properly. In your testing, are you seeing cases where the retrying does help?

When this changes goes in, I am thinking that we might be able to remove https://github.com/DataBiosphere/terra-ui/blob/e69798efefbadf368f737876d84fd8358b45f6ad/integration-tests/utils/integration-helpers.js#L72 which was added in an attempt to work around permissions not appearing fast enough.

When this changes goes in, I am thinking that we might be able to remove
https://github.com/DataBiosphere/terra-ui/blob/e69798efefbadf368f737876d84fd8358b45f6ad/integration-tests/utils/integration-helpers.js#L72
which was added in an attempt to work around permissions not appearing fast enough.

We added DC-357 to investigate whether we can remove the code.


[starter-stack] Improve README and name

Give more details on how to use this starter in the README, and provide a better name for the tile on the main web site.
Fixes #436

@helenmasters Thanks for your comments - agreed, will include in a new PR. FYI there is new version of the "create appsody stack" tutorial that uses the new appsody stack commands about to be published. See: https://github.ibm.com/IBMCode/Code-Tutorials/pull/2209


Fix log scale death toll

This fixes the #3. What it does is it checks whether there are values in the range (0.1, 1) in the data from day zero onward. If yes, then it sets the lower y-limit of the death toll graph to 0.1.
The result looks like this:

Thanks!


ENH: early stopping in replay scripts

related to #81
the replay scripts have comment lines and placeholders for unknown parameters and filepaths. This is great!
But this also creates a problem, namely that the scripts are then not executable "out of the box". This is fine, they should not be expected to be (nor is "touchless replay" necessarily even the goal here), but it could create issues if a user naively attempts to run a script that has not yet been adapted.
this could be partially fixed by including instructions for making the script executable (#81 )
but it would also be nice to insert an exit line or similar (with comments/instructions to remove after other edits are made), so that users do not attempt to run a broken provenance replay script.

Great idea, @nbokulich! A couple minor clarifications:

instructions for making scripts executable are already written to script headers. #81 targets end users who need to execute scripts that have already been prepared according to these instructions. I've clarified this at #81.
this should probably raise (or echo) some kind of explanatory error message, and for bash scripts use a somewhat meaningful unique error code (i.e. more searchable than exit 1). There is limited standardization of error codes in bash, but I propose exit 66. 66 codes EX_NOINPUT in C's sysexits, generally indicating a missing or unreadable input file.


authentik

hello, can i use this with authentik oauth?

Closed due to time.
Thank you for your inquiry.