Package registry PoC

Fixes https://github.com/zeppelinos/labs/issues/132

Looks great @facuspagnuolo! I've yet to understand better the standards around ENS to comment in-depth about the PR, but the architecture looks good. I like having a base registrar, with different "interfaces" depending on the access control for zOS or aOS (though maybe we could switch from Ownable to RBAC down the road).
I have one question pending regarding ENS: can we be sure that, under the new registrar to be deployed next year, there is no way for the domain backing the package registry to be lost? For instance, if we register thebestpackageregistry.eth, and we lose it a year after due to a higher bid, or someone forgetting to pay for the renewal, we are dealing with quite a single point of failure. From what I understand though, domain name assignments are to be permanent, but I wanted to check.

Moving on to a different subject, which is the Registry contract. I different ways of working here:
1- We have an APMRegistry and a ZOSRegistry, both entirely different contracts, but they are both backed by the same Registrar, tied to the same domain. This would allow both organizations, at first, to share the domain where packages are registered, and then move forward by integrating the subsequent contracts.
2- We aim at a single Registry contract that covers the use cases for both. We can extend the APMRegistry contract to have registerRepo methods, that will allow any kind of contract to be registered, including zOS Packages. This would remove the need for having two different contracts writing to the same Registrar, and we could actually upgrade the APMRegistry to this SharedRegistry contract.
Either way, this opens the door for arbitrary contracts to be registered in the registry, not just valid Repos or Packages. We should keep a centralised control to remove malicious registry entries during the beta phase.

Another topic is the Repo itself, which tracks different versions of a lib, and is the aOS equivalent of zOS' Package. Regardless of its validations, its heavily tied to semver, and we should decide whether we want zOS Package to adopt that naming scheme as well.
1- If we modify Package to work only under semver (which I'd not recommend to do now, but later down the road), then we could have a similar public interface to Repo, even if we don't enforce the same validations.
2- Otherwise, we accept the fact that, during the initial beta period, there will be two different kind of animals registered in the same registry, which have different interfaces.
Note that (2) means that a lib developer who wants to develop for both aOS and zOS would need to register two different packages under two different names, at least during this beta phase. On the other hand, even if we do implement a shared interface, then the expected contractAddress linked for a version of the Repo/Package would also need to be different, as it'd be an ImplementationProvider for zOS, and an AragonApp for aOS, until we figure out a common interface at that level for both OSs (which is not that far-fetched, actually).

Nice work @facuspagnuolo! I like the simplification work you have done.
I have a question: where is the Registry contract? I guess it is still on the works, but right now there would be no way to push new Repos/Packages to the registry. I see a mention of ZOSRegistry but didn't find it anywhere.
Other points I wanted to touch upon:
Rich governance
I see most of the logic has been taken from APM, but without the auth modifiers for newVersion and newRepo. I think it is important to have rich governance built in into the package manager, and that's why we made APM a DAO from the start. A decentralized package manager run by a single entity doesn't make sense, since that'd be centralized and there are already plenty of centralized package managers out there.
I think the package manager being a DAO is key for rich governance, since it makes it dead easy.
For example, in Zeppelin's case, if the package manager was a DAO, you could deploy a registry controlled by ZEP holders very easily in X steps:

Deploy the package manager DAO
Deploy the Voting app in Aragon, and give permission to the ZEP holders to cast votes
Give permission to the Voting app to call newVersion and newRepo

With just those 3 steps, we give ZEP token holders right to vote on new versions and repos inside the registry. You could get fancier and create new Token Manager instances for different groups of stakeholders, different Voting apps with different consensus thresholds for different repos, etc. This wouldn't be possible if the package manager wasn't a DAO. We recently wrote a blog post about this.
Upgradeability of the repos
Right now, the contracts for the repo and the registry are not upgradeable, right? I think they should be (no need to argue why upgradeability is important between us haha). Also one of the cool things you get for free if the package manager is a DAO is that you can upgrade all repos in a registry. Otherwise, you'd need to upgrade each one individually. But if it's a DAO, you can just upgrade the reference to the Repo app in the kernel, and all repos in a registry are automatically upgraded.
Repo vs Package naming
Although Package is more intuitive (you push new versions of a package) the technically correct term would be Repo (you push a package to a repo). I guess that calling it Package means that you push new versions to a package, but the new versions pushed packages themselves, so you cannot push a package to a package. That's why I think that, although not as sexy, Repo is the most accurate term. It's also used by package managers in Linux, etc. That being said Package feels more friendly, so I don't have hard feelings, but wanted to point out that question about naming.

That's it! Solid work on this, looking forward to your thoughts.

Hey @luisivan! thanks a lot for your feedback! 😄
Regarding the Registry contract, it would be simple to have some similar contract to the ENSRegistry that acts as a registry for us. But that would mean that either you guys duplicate the effort of publishing Repos in this new Registry given that you're already using ENS, or that you stop using ENS to register Repos and start using the new Registry. Based on what I spoke with @izqui you guys are interested in keeping the ENS integration, so we decided to focus simply on what will be the common interface of Package/Repos that fit for both projects.
Governance
I really like the idea of decentrilizing the governance of the Package/Repos, do you think it should be part of the minimum interface?
Upgradeability of the Repos
AFAIK, given that a Aragon's Repo are an AragonApp I think those are upgradeable. Regarding Zeppelin's Package I haven't tested that in this PoC, but it is on our plans. I do think both should be upgradeable, but I think it shouldn't be part of the standard, do you agree?
Repo vs Package naming
I like your thoughts on this topic :)
I'll discuss this with the rest of the team and let you guys know

Got it, makes sense, thanks for the clarification @facuspagnuolo!
Regarding governance and upgradeability, I think it doesn't need to be a part of the interface, but a part of any of the implementations.
The minimum viable path is to work on a common interface and spec, which I think we are doing a good job at. But ideally we would also work on a canonical implementation that we can all use and build upon. For the spec and interface, we don't need to get into governance or upgradeability, but for the implementation, I think it's very necessary.


proposal: testing: measure benchmark latency distributions

For #18177, we need to make tradeoffs between worst-case latency and average throughput for the functions in question.
It's relatively easy to measure the average throughput today using benchmarks with the testing package.
It would be nice if I could use those same benchmarks to measure the distribution of timings across iterations.  That isn't really feasible using (*B).N with caller-side iteration, but it might at least be possible to tap into (*PB).Next to get some idea of the latency between calls for parallel benchmarks.

/cc @aclements

Related: #7465

That isn't really feasible using (*B).N with caller-side iteration

One possibility is to crank up N only far enough to eliminate clock measurement overhead and then use caller-driven iteration to drive up the number of samples/total iterations to the desired measurement interval. However, this may not work well with benchmarks that perform non-trivial setup and use B.ResetTimer.

benchmarks that perform non-trivial setup and use B.ResetTimer

Also related: #10930. I bring it up because I learned there that you can in fact detect this case--both the case in which b.ResetTimer is called and the case in which b.ResetTimer is (erroneously) not called. Just look at how the total wall time to run the benchmark compares to the time as recorded by the timer.

We can also tell whether b.ResetTimer is in use because we control the implementation of b.ResetTimer.
One of the reasons we've moved from benchcmp to benchstat is that the latter allows multiple data points for a given benchmark. Today those data points are all for roughly the same large size N, but the eventual plan was to emit more lines about smaller N, so that benchstat can do more work with distributions. If anyone wants to experiment with that and let us know how it goes, please do.
I'd also like to have a check somewhere (in package testing or benchstat, probably the former) that b.N really is scaling linearly. If the time for b.N is 4X that of b.N/2 and 16X that of b.N/4, the benchmark function is using b.N incorrectly and shouldn't be reported at all. Doing this in package testing, without printing the smaller runs at all, would let benchstat continue to assume that all the reported runs are about the same size.

Adding a correlation coefficient test to benchmarks seems like a good idea. We could also use the estimated slope of a (weighted?) linear regression as the ns/op instead of straight division, which in theory might yield better results.
I tried hacking in a quick-and-dirty linear regression and got plausible slope numbers. (I didn't mail it because I used a naive rather than a numerically stable calculation.)
I don't plan to work on this further at the moment.

A few years ago I spent a while looking at what Haskell's benchmark tool does. I convinced myself that trying to be clever about slope vs N=0 cost was probably not worthwhile - better to brute force enough iterations that the slope is dominant.
The initial version of Haskell's tool (I forget the name) apparently did fancy things like boosting too, but that seems like overkill too, super subtle and easy to quietly get wrong. Later versions seemed to have backed off some of the complexity.

I convinced myself that trying to be clever about slope vs N=0 cost was probably not worthwhile - better to brute force enough iterations that the slope is dominant.

Fair enough. Looking at the N=0 cost may still be worth doing, if only to catch bugs like https://github.com/golang/go/commit/dbf533a5460d7fcc7d7be77014fd74a8aff8c412. (Of course, one could brute force enough iterations for that, but it seems inadvisable.)

I'd like to move this along, assuming that we're not going to introduce a new API for writing benchmarks (so no equivalent of pb.Next) and that we can't emit extra output lines by default (preserving the current one benchmark = one output line). And when we do emit extra output lines, all the lines need to be about the same thing (no warmups to filter out from averaging calculations in benchstat or other tools).
That implies that we need to add some flag that causes a benchmark to be run multiple times for smaller counts and then with one line of output per each of those runs.
Assuming the default -benchtime=1s, if instead of printing output for one run of 1s we want to print output for 10 runs of 0.1s, this can be specified in two possible ways: by setting the target run duration with the count implicit (-benchtime2=0.1s), or by setting the target number of runs with the duration implicit (-benchsplit=10). We only want to add one of these to package testing.
I don't have a great name for the target run duration (obviously), but I think benchsplit could work if we decide to specify the number of runs instead.
The split factor is subject to change to respect the overall time limit. If, say, one iteration of a benchmark takes 0.6 seconds, then with -benchtime=1s -benchsplit=10, we'll still only run ~2 of them, not 10. This makes it sensible to run go test -benchsplit=10 in the go1 directory, as compared to go test -benchtime=0.1 -count=10. The latter runs even very expensive benchmarks 10 times, while the former only runs them once.
So my proposal for this proposal is to add -benchsplit=N as described above.
I don't know if this really helps @bcmills's original request. If not I apologize for hijacking. We've been talking about getting this data out for years, and it does provide more fine-grained detail about the distribution of runs, just not individual runs. If there are rare high-latency individual runs then hopefully you'd be able to split down to a small enough interval that some are lucky and some are not, and then that would come out in the data as a bimodal distribution.

I don't think that really addresses my original request, unfortunately: for the kinds of latency distributions I'm interested in, one output line per run would be far more data than I want to sift through.
But it does at least seem like a step in the right direction.

Agreed: Seems like a step in the right direction, and I would definitely use this. The interaction between slow benchmarks and -count has always been painful.
To be clear on the (non-)interaction between -benchsplit and -count, if you did -benchtime=1s -benchsplit=10 -count=5, you'd get anywhere between 5 and 50 lines of output?

@bcmills, sifting through the output is for computers.
@josharian, yes.
for 0..count {
    total = 0
    for total < benchtime {
        t = runAndReport(benchtime/benchsplit)
        total += t
    }
}

Objections to adding -benchsplit?
/cc @aclements @mpvl

Sounds like there are no objections to -benchsplit. Anyone want to implement it?

(I've started working on this and plan on having a CL by early next week. Hopefully my recent testing contributions grant me such a runway.)

Has progress on this stalled?

Answering my own question from a year ago: yes, it seems like CL 47411 has stalled out, but the proposal is approved and the details seem to have been mostly ironed out in the extensive discussion on that CL. I think anyone could pick up these changes and take them across the finish line.


Merge branch 'main' of https://github.com/Swifty9/Maverick-AI

Add a screenshot of your change and what you did explain in brief

added the logo and adjusted the width and height of the logos


T265: Still a few more doubts on apriltag pose detection sample....

Required Info

Camera Model
T265

Firmware Version
<IP_ADDRESS>7

Operating System & Version
Ubuntu 16.04

Kernel Version (Linux Only)
4.15.0-66 generic

Platform
PC

SDK Version
2.30.0 pre-release

Language
C++

Segment
others

Issue Description
Oh, man, I have so many issues open, please forgive me if it sucks. But I'm gaining more and more land in this interesting matter, and a lot of questions inevitably arise.
This is again one of the somewhat longer to formulate kind, sorry for that. There is also no tl;dr, unfortunately.
Essentially, it is a request for confirmation/negation of some observations regarding the recognition and positioning of Apriltags with the aim of determining their position in a training, storing it (set_static_node) for later in the map and using the annotated map then for tracking (get_static_node).  The Apriltags are supposed to carry additional context information. This should be sufficient for the formulation of the rough target. I don't know, if I will reach it, but I try :)
So I took the rs-pose-apriltag example and the rs-ar-basic example and combined both, quick and dirty. Basically I won a quaternion and a translation vector from the two poses in the rs-pose-apriltag example, namely the tags.pose_in_camera[t] and the tags.pose_in_world[t]. Then I coded these values into into the function reset_object_pose in the rs-ar-basic example in order to make it visible.
The AprilTag was glued to the door, both scripts were running from the same position one after the other.
Here is the result, shown is the "world pose".  The first shot was taken with the laptop on the ground, roughly a meter away from the tag. All others have been taken from the corner of my desk, roughly 1.5 m away and 1 m high. And a little left shifted. And door opened :)
For the first shot, the pose is pretty ok. It looks as like the middle line of the lower border of the rectangle is the point (the next pictures will show something different, as you will see). At least I could walk around and the pose was stable. It was not the exact distance, but it was acceptably.

These are the values, which formed that image:
frame 726|tag id: 0|camera R: 0.998, 0.002,-0.069,-0.004, 1.000,-0.024, 0.069, 0.024, 0.997,|t:-0.036,-0.315, 0.914,
float f[7] = {-0.0358145,-0.315414,0.913617,0.0118154,-0.0343299,-0.00165176,0.999339};
                    world  R: 0.996,-0.021,-0.083,-0.023,-1.000,-0.022,-0.082, 0.023,-0.996,|t:-0.078, 0.273,-0.929,
float f[7] = {-0.0778453,0.272905,-0.929469,0.999022,-0.011028,-0.0413003,0.0112858};

An explanation of the values: Besides the three inbuilt traces (frame, camera and world), which show the frame number and the rotation matrix and translation vector of both poses, there are two "float" arrays, which I generate and print from the altered rs-pose-apriltag example in order to put it into the rs-ar-basic example.
The array contains the translation x, y and z values first, followed by the quaternion x, y, z and w derived from the rotation matrix. I'm pretty sure, the "Rotation matrix to quaternion" conversion, I'm using, is correct. I have double checked it. The first array describes the camera pose, the second the world pose.
The second run (from the desktop corner) showed a different picture: Now the point was the middle of the upper border of the rectangle and the z-axis (blue) was shown differently. Hmm..  Also the distance error was a bit higher, but still acceptable. I would not make the distance a problem. But the different orientation of the z-axis and the different recognition base could be one, even though maybe just a small one.

Values now:
frame 1092|tag id: 0|camera R: 0.920,-0.001, 0.392,-0.029, 0.997, 0.071,-0.391,-0.076, 0.917,|t: 0.249, 0.444, 1.062,
float f[7] = {0.248763,0.443619,1.06177,-0.0375821,0.19976,-0.00727384,0.979097};
                     world  R: 0.925,-0.043, 0.378,-0.040,-0.999,-0.016, 0.378,-0.001,-0.926,|t: 0.180,-0.368,-1.098,
float f[7] = {0.180378,-0.368166,-1.09798,0.980998,-0.021388,0.192796,0.00386514};

Anything obvious, which would explain the different center and the axis orientation?
Then I made two closer shots, which show the delta in distance:

The camera pose, btw, visualized in both cases to something pretty unexpected, but after some thoughts, I think it is OK. It is not the actual camera pose, but the tag's pose in the camera's coordinate system.

It is noticeable that the axis orientation is correct here.
So my questions:

Is all that plausible at all?
Why is the detection choosing different edges of the tag in different runs?
Why is the axis orientation of z different and can this be a problem?

I will deal with this the next days and report, if I get answers by myself.
Thanks

@neilyoung If I recall, for apriltags, the center of the tag should be the center of the frame (and not one of the edges). Have you had good results with this tag family in general (with, say, the base apriltags library)? I've seen that some tag families have weird detection issues/offsets.
As for your orientation of z-axis, it looks to me that z (blue) is always pointed into the tag in all your images. In fact, the quaternions you reported in your float array for open & closed door scenarios are actually pretty close (and might even correspond to the angle of your door!) :)

@ajshank Thanks for commenting

If I recall, for apriltags, the center of the tag should be the center of the frame (and not one of the edges).

I would expect this too, somehow. But meanwhile I have seen a couple of other detection frames. Most are centered at one of the upper or lower borders, but I also did see one, which was nailed to the bottom/left corner. But none of it have been positioned in the center of the tag so far.

Have you had good results with this tag family in general (with, say, the base apriltags library)? I've seen that some tag families have weird detection issues/offsets.

I have absolutely no experiences with ATs. I just took the one which was bundled with the sample. Will try another family.

As for your orientation of z-axis, it looks to me that z (blue) is always pointed into the tag in all your images.

Wow, you have pretty good eyes. I have totally overseen that in the analysis I did later on. In fact I found yet another screenshot of the first pose setup (with the closed door), and it clearly shows, that the z-axis on all pictures points "into" the tag. It was a perspective issue, obviously. Here the image I found later:

In fact, the quaternions you reported in your float array for open & closed door scenarios are actually pretty close (and might even correspond to the angle of your door!) :)

That I true. The angle of the door was always nicely reflected.
Basically, this angle is finally, what I'm interested in. I'm experimenting with the yaw value (rotation around the green y axis). But I'm not sure if this will help me. Do you know of any magic math, which would allow me to determine the angle between the camera and the tag's z axis.
To be a bit more specific: I would like to know the angle marked with a question mark in the image below. I would estimate it to be around 180 degrees, and around 170 degrees in the photo above the drawing, but I'm missing the correct math here.

EDIT: I think my drawing is not entirely true. The ray angle at the camera must not necessarily be 90 degrees... But I also have the yaw value of the cam in the coord system of the cam, if that would help...

I've forgotten most of the AprilTags-related things I knew, and I don't have a setup lying around that I can quickly test with, sorry. I'm also not very familiar with all the extra stuff that librealsense can report for AprilTags.
But here are a two things to narrow down your problem:

The angle that you marked with a question mark, should be in 2D, i.e., there should be two angles: an elevation and an azimuth. The way you drew it, you are considering a rotation only about y-axis, which would of course make the angle bigger or smaller. There is another possible rotation about x-axis. Perhaps it is easier if you assume in the beginning that xz-plane of the tag is level with the camera, so that you can start with 1D.
The 3D location of the tag (relative to the camera frame) is enough to calculate the angle you've marked with a dot, since you can consider the camera to be at "origin" and use tag's x, y, z to compute this angle. Then the roll, pitch and yaw angles of the tag (in the camera frame) can be added/subtracted to this angle to get what you need.

@ajshank Thanks again for your input. I totally agree with 1) I also saw this little problem arising. I would just change 2D to 3D and 1D to 2D in your comment.  I also agree on 2) I have all the information there. I should be able to crunch that.
In the meantime I have really merged that two applications into one. If I would have a bit more C++ knowledge, I would consider to contribute that to the community. Basically I have now an app, wich does no longer need my manual copy&paste of the found world coordinates of the tag, but one, which displays the found position "as it comes". And you know what I'm seeing? The anchor point is exactly the center of the tag, as you commented. It was just a matter of the sample coordinate I have chosen from the many, which gave me the wrong impression.
As far as I know there is no inbuilt support for ApritTag detection in librealsense.


Fileshare not present required for HA Setup!

We are trying to test a 5 machine deployment of ArcGIS Enterprise as seen in the diagram for the multi-machine deployment https://github.com/Esri/arcgis-powershell-dsc/wiki/Create-a-base-ArcGIS-Enterprise-deployment-on-many-machines.  We want to have portal, webadaptors, datastore and two ArcGIS servers on separate machines with one of the ArcGIS servers acting as the dedicated hosting server and the other as a federated general purpose server.  When running the installation we receive the following error message:
_FileShare not present required for HA Setup!
At C:\Program Files\WindowsPowerShell\Modules\ArcGIS\1.1.0\ArcGIS.psm1:703 char:17

            throw "FileShare not present required for HA Setup!"

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : OperationStopped: (FileShare not p...d for HA Setup!:String) [], RuntimeException
FullyQualifiedErrorId : FileShare not present required for HA Setup!_

We are confused by this message because we are not trying to install a highly available deployment. We made a second attempt at installation and added a file share to one of the ArcGIS Servers in the configuration file.  The installation progressed further but we eventually received another error message:
[]PowerShell DSC resource ArcGIS_FileShare  failed to execute Set-TargetResource functionality with error message: Unable to create Folder C:\portalforarcgis\content\arcgisportal\content -
The network path was not found
Attached are the two configuration files we tried for the installation and the messages from the powershell installation.  Hope you can help us make the proper adjustment to our configuration file. Thanks in advance for any help you can provide!
GSS_enterprise_install_powershell_config_2ndatttempt.TXT
GSS_enterprise_install_powershell_config_initial.txt
GSS_enterprise_install_powershelldsc_output.docx

@croger68 For a base deployment and federated General Purpose server - you need to have two separate json config files. One will be a base deployment template and other would be GIS Server template.
PS. You received the error for the second config file as the portal content directories are also configured to use the file share. As of now, you can't choose to have content directories of server use file share and that of portal use local. Hope that makes sense.

Thank you for the response.  For your information, I tried to seek help through ESRI support but was told that as of now ESRI is not supporting Enterprise installation using powershell DSC?  I generated two separate configuration files as you suggested one for the base deployment and one for the general purpose server.  It looks like the installation progressed further during the base deployment but we received additional error messages.  The initial error received was during configuration of the Server:

PowerShell DSC resource ArcGIS_Server  failed to execute Set-TargetResource functionality with error message: ERROR: ArcGISUtility.psm1 failed. Could not find resource or operation 'deployment' on the system. The SendConfigurationApply function did not succeed.
[GSSRTDSTOR]: LCM:  [ End    Set      ]

I attached the revised config files and powershell messages from the installation. Thanks again for your help.
GSS_enterprise_install_powershell_config.txt
GSS_enterprise_install_powershell_config2.txt
GSS_enterprise_install_powershelldsc_output_run2.docx

@croger68 - can you e-mail me the contact at Esri support who provided the incorrect guidance.
It is incorrect. PowerShell DSC is supported through Esri support channels.
nshampur  @  esri dot com

@croger68  The error message seems to indicate that either licensing was not successful or the site was not created.  Can you check what the state of your server is  https://GSSGISHOST:6443/arcgis/admin

When I go to the  https://GSSGISHOST:6443/arcgis/admin
https://gssgishost:6443/arcgis/admin  url I get the "There is a problem
with this website's security certificate" message.   When I click on
"continue to this website (not recommended)",  I get the ArcGIS Server
Administrator Directory login page and am able to login to the server using
the primary site admin login.
On Tue, Oct 30, 2018 at 12:03 PM Nikhil Shampur<EMAIL_ADDRESS>wrote:

@croger68 https://github.com/croger68 The error message seems to
indicate that either licensing was not successful or the site was not
created. Can you check what the state of your server is
https://GSSGISHOST:6443/arcgis/admin
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Esri/arcgis-powershell-dsc/issues/102#issuecomment-434384549,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYtcgzcCZQCwp0NByrzUoLL_Sok5w0Grks5uqIZWgaJpZM4XUIiB
.

--
Roger Meyer
GeoSpatial Services
OFFICE<PHONE_NUMBER> <(507)%20457-8747>
<EMAIL_ADDRESS>SAINT MARY'S UNIVERSITY OF MINNESOTA
GeoSpatial Services
Prairie Island Field Station
890 Prairie Island Road
Winona, MN 55987-1399 USA
smumn.edu http://www.smumn.edu/* | *GeoSpatial Services
http://www.geospatialservices.org/

Looks like the site did get created.
Are you able to rerun the PowerShell script
Configure-ArcGIS -ConfigurationParametersFile C:\entinst1061dir\GSS_enterprise_install_powershell_config.json
It should skip over actions that were successful.

I ran the script again and received the following error message during
configuration of portal:
[]PowerShell DSC resource MSFT_WaitForAll  failed to execute
Set-TargetResource functionality with error message: Resource
'[ArcGIS_Portal]PortalGSSPORTAL' on machine(s) 'GSSPORTAL' is not re
ady after '90' retries with retry interval of '60' second(s).
[]The SendConfigurationApply function did not succeed.
followed by below error message in the federation section of the script:
[]PowerShell DSC resource ArcGIS_Federation  failed to execute
Test-TargetResource functionality with error message: Unable to retrieve
Portal Token for 'admin' from Deployment 'GSSWEBSRV.smu
mn.edu'
[]The SendConfigurationApply function did not succeed.
On Tue, Oct 30, 2018 at 2:22 PM Nikhil Shampur<EMAIL_ADDRESS>wrote:

Looks like the site did get created.
Are you able to rerun the PowerShell script
Configure-ArcGIS -ConfigurationParametersFile
C:\entinst1061dir\GSS_enterprise_install_powershell_config.json
It should skip over actions that were successful.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Esri/arcgis-powershell-dsc/issues/102#issuecomment-434433795,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYtcg1VpxSR9jnPBV-samqxjT20g4X2nks5uqKbYgaJpZM4XUIiB
.

--
Roger Meyer
GeoSpatial Services
OFFICE<PHONE_NUMBER> <(507)%20457-8747>
<EMAIL_ADDRESS>SAINT MARY'S UNIVERSITY OF MINNESOTA
GeoSpatial Services
Prairie Island Field Station
890 Prairie Island Road
Winona, MN 55987-1399 USA
smumn.edu http://www.smumn.edu/* | *GeoSpatial Services
http://www.geospatialservices.org/

@croger68 looks like you are encountering a race condition on a rerun of the json configuration. I will investigate this and get back to you soon.

@croger68 Can you please tell me the version of DSC Module you are using?

from the installation folder it looks like we are using arcgis module 1.1.0
for powershell? ( C:\Program
Files\WindowsPowerShell\Modules\ArcGIS\1.1.0\DSCResources).   I am not that
familiar with powershell so let me know if this is not what you are looking
for.
On Thu, Nov 1, 2018 at 4:29 PM Shailesh Goel<EMAIL_ADDRESS>wrote:

@croger68 https://github.com/croger68 Can you please tell me the
version of DSC Module you are using?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Esri/arcgis-powershell-dsc/issues/102#issuecomment-435193756,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYtcgxsyqH8VNQo4aqm086mTxLJqtyPFks5uq2ewgaJpZM4XUIiB
.

--
Roger Meyer
GeoSpatial Services
OFFICE<PHONE_NUMBER> <(507)%20457-8747>
<EMAIL_ADDRESS>SAINT MARY'S UNIVERSITY OF MINNESOTA
GeoSpatial Services
Prairie Island Field Station
890 Prairie Island Road
Winona, MN 55987-1399 USA
smumn.edu http://www.smumn.edu/* | *GeoSpatial Services
http://www.geospatialservices.org/

Yes, that is the version I was looking for. If possible can you please upgrade it to 1.1.3 just released
Install-Module -Name ArcGIS -RequiredVersion 1.1.3

@croger68 Yes, please.

I get the error message below. how to properly uninstall previous version?
At C:\Program
Files\WindowsPowerShell\Modules\ArcGIS\1.1.3\Configuration\ArcGISInstall.ps1:3
char:5

Import-DscResource -ModuleName ArcGIS

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Multiple versions of the module 'ArcGIS' were found. You can run
'Get-Module -ListAvailable -FullyQualifiedName ArcGIS' to see available
versions on the system, and
then use the fully qualified name '@{ModuleName="ArcGIS";
RequiredVersion="Version"}'.
+ CategoryInfo          : ParserError: (:) [], ParseException
+ FullyQualifiedErrorId : MultipleModuleEntriesFoundDuringParse
On Fri, Nov 2, 2018 at 2:15 PM Shailesh Goel<EMAIL_ADDRESS>wrote:

@croger68 https://github.com/croger68 Yes, please.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Esri/arcgis-powershell-dsc/issues/102#issuecomment-435463031,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYtcg8xW4dBe8hlFHRieWTf1kJrecWJBks5urJnTgaJpZM4XUIiB
.

--
Roger Meyer
GeoSpatial Services
OFFICE<PHONE_NUMBER> <(507)%20457-8747>
<EMAIL_ADDRESS>SAINT MARY'S UNIVERSITY OF MINNESOTA
GeoSpatial Services
Prairie Island Field Station
890 Prairie Island Road
Winona, MN 55987-1399 USA
smumn.edu http://www.smumn.edu/* | *GeoSpatial Services
http://www.geospatialservices.org/

Get-InstalledModule -Name "ArcGIS" -RequiredVersion 1.1.0 | Uninstall-Module

thank you,
I uninstalled and ran the configuration file again.  Received error
messages below:
[GSSWEBSRV]: LCM:  [ End    Set      ]
[[WaitForAll]WaitForAllPortalConfigToCompleteGSSPORTAL]  in 9186.2980
seconds.
[GSSWEBSRV]: LCM:  [ End    Set      ]
[]PowerShell DSC resource MSFT_WaitForAll  failed to execute
Set-TargetResource functionality with error message: Resource
'[ArcGIS_Portal]PortalGSSPORTAL' on machine(s) 'GSSPORTAL' is not re
ady after '90' retries with retry interval of '60' second(s).
[]The SendConfigurationApply function did not succeed.
[]PowerShell DSC resource ArcGIS_Federation  failed to execute
Test-TargetResource functionality with error message: Unable to retrieve
Portal Token for 'admin' from Deployment 'GSSWEBSRV.smu
mn.edu'
[]The SendConfigurationApply function did not succeed.
On Fri, Nov 2, 2018 at 3:46 PM Shailesh Goel<EMAIL_ADDRESS>wrote:

Get-InstalledModule -Name "ArcGIS" -RequiredVersion 1.1.0 |
Uninstall-Module
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Esri/arcgis-powershell-dsc/issues/102#issuecomment-435497247,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYtcg4UOSKxsDIFa9geFX3I9EfuzWMp1ks5urK8lgaJpZM4XUIiB
.

--
Roger Meyer
GeoSpatial Services
OFFICE<PHONE_NUMBER> <(507)%20457-8747>
<EMAIL_ADDRESS>SAINT MARY'S UNIVERSITY OF MINNESOTA
GeoSpatial Services
Prairie Island Field Station
890 Prairie Island Road
Winona, MN 55987-1399 USA
smumn.edu http://www.smumn.edu/* | *GeoSpatial Services
http://www.geospatialservices.org/

@croger68 would you be open to a skype debugging session? I might be able to help you resolve the issues more quickly. My email is<EMAIL_ADDRESS>

This issue was solved in release 1.1.4.


Can We merge two type graph in one? Like in same graph can we draw both column and line graph?

Can We merge two type graph in one? Like in same graph can we draw both column and line graph?

@nv2908 you can use two tables with different options. Also you can mask this table if you don't want to display it twice. Does this answer your question ?

is there any option in which we can plot column and line graph together in one chart


Integration Test - Release - 2021/04/30 15:14:39

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

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


数据集

Thanks for your error report and we appreciate it a lot.
Checklist

I have searched related issues but cannot get the expected help.
I have read the FAQ documentation but cannot get the expected help.
The bug has not been fixed in the latest version.

Describe the bug
A clear and concise description of what the bug is.
Reproduction

What command or script did you run?

A placeholder for the command.

Did you make any modifications on the code or config? Did you understand what you have modified?
What dataset did you use?

Environment

Please run python mmdet/utils/collect_env.py to collect necessary environment information and paste it here.
You may add addition that may be helpful for locating the problem, such as

How you installed PyTorch [e.g., pip, conda, source]
Other environment variables that may be related (such as $PATH, $LD_LIBRARY_PATH, $PYTHONPATH, etc.)

Error traceback
If applicable, paste the error trackback here.
A placeholder for trackback.

Bug fix
If you have already identified the reason, you can provide the information here. If you are willing to create a PR to fix it, please also leave a comment here and that would be much appreciated!

dota数据集遇到点问题  .json文件是很多个，没有合成。您能给一下图片和json文件吗 谢谢作者。


[Bug]: onSubmit event on input widgets does not trigger when submitted from a modal widget

Is there an existing issue for this?

[X] I have searched the existing issues

Description
configuring onSubmit event on any of the input widgets and triggering a submit action from a modal widget does not amount to anything
Steps To Reproduce

Drop any type of input widget on a modal
Configure onSubmit event on the widget, eg: showAlert('')
On preview mode, key in any information on this input widget and hit submit - observe there is no toast message

Public Sample App
No response
Environment
Deploy Preview
Severity
Medium (Frustrating UX)
Issue video log
No response
Version
cloud

In order for everything to work correctly, we will need to implement the form component. This is quite a difficult and big job. We'll do it later.


feat: Add Kinesis lambda event support to Parser utility

This schema is currently supported in the validator utility.
This issue will add the schema to the parser utility and a new envelope.
The envelope will base64 decode the user data and if a model input was given, will also parse the decoded string as a pydantic BaseModel or string.
This will allow full parsing and message extraction by using only one decorator.
If you dont supply a model, the data type of the extracted data is bytes (not base64 encoded string).

Launched in 1.9.0 now


CocoaPods?

I am getting a Swift Compiler Error using XCode 8.  Is the CocoaPods updated?

What's error? Could you show me your Podfile? Or share repro project?

Sorry, I had the fixed version in my Podfile.  I will close this issue now.


Remove PIP_USER="yes"

Remove workaround PIP_USER="yes", because solution is now part of ESP-IDF:
https://github.com/espressif/esp-idf/issues/7910
This environment variable was set on GitPod build machines and it was not possible to bootstrap the environment for ESP-IDF. The solution was applied to all release branches of ESP-IDF.

Shouldn't this be closed now with #96 merged?


Updates to partition config middleware

What changed?

Rename ZonalPartitionConfigMiddleware and the header used by the middleware
Enable ClientPartitionConfigMiddleware and ForwardingPartitionConfig middleware by default

Why?
enable tasklist isolation

How did you test it?
manual test on laptop

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 01890971-4fd3-44fd-9b4c-3a0168dcd5fa

6 of 6 (100.0%)  changed or added relevant lines in 2 files are covered.
113 unchanged lines in 17 files lost coverage.
Overall coverage decreased (-0.03%) to 57.228%

Files with Coverage Reduction
New Missed Lines
%

client/history/client.go
2
38.1%

client/history/metricClient.go
2
45.3%

common/membership/hashring.go
2
83.54%

common/task/fifoTaskScheduler.go
2
87.63%

service/history/handler.go
2
47.15%

common/persistence/nosql/nosqlplugin/cassandra/workflow.go
3
59.1%

common/persistence/statsComputer.go
3
94.29%

common/persistence/serialization/parser.go
4
62.41%

common/persistence/serialization/thrift_decoder.go
4
53.06%

service/frontend/workflowHandler.go
4
60.24%

Totals

Change from base Build 0189088e-cb42-44e0-b004-8c969087ff5b:
-0.03%

Covered Lines:
87097

Relevant Lines:
152192

💛  - Coveralls


Deprecate parser in pkg/lockfile

Parser is no longer being used so we probably should remove it.

I would like to keep this open to remind us to get rid of the code completely in v2.


"Twilio Services Error" for outbound calls

Hello there,
Im trying to get up and running with Twilio's new Voice Client. I've written a back-end api in NodeJS for generating accessTokens and showing an XML file for the outgoing call route. Now I'm testing my setup on the client side with the Swift Quickstart app.
Now when I make outgoing calls, I get outgoingCall:didFailWithError: Twilio Services Error. Here's all the logs from app starting to the call failing. Any pointers as to whats going wrong would be very appreciated.
2017-01-26 09:01:23.658612 SwiftVoiceCallKitQuickstart[2438:726429] [INFO VoiceClient] Setting log level: Verbose
2017-01-26 09:01:23.700639 SwiftVoiceCallKitQuickstart[2438:726429] Twilio Voice Version: 2.0.0
2017-01-26 09:01:23.836734 SwiftVoiceCallKitQuickstart[2438:726429] [VERBOSE VoiceClient] Application did become active
2017-01-26 09:01:23.837044 SwiftVoiceCallKitQuickstart[2438:726429] [DEBUG TVOReachability] Reachability Flag Status: -R ------- networkStatusForFlags
2017-01-26 09:01:23.837159 SwiftVoiceCallKitQuickstart[2438:726429] [VERBOSE VoiceClient] Internet available, update transport
2017-01-26 09:01:23.837291 SwiftVoiceCallKitQuickstart[2438:726429] [VERBOSE VoiceClient] Inside reconnect, reconnecting ...
2017-01-26 09:01:23.852366 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c !.Module "mod-pjsua-log" registered
2017-01-26 09:01:23.852797 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4):   pjsua_core.c  .Nameserver <IP_ADDRESS> added
2017-01-26 09:01:23.852917 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  .Module "mod-tsx-layer" registered
2017-01-26 09:01:23.852967 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  .Module "mod-stateful-util" registered
2017-01-26 09:01:23.853031 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  .Module "mod-ua" registered
2017-01-26 09:01:23.853134 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  .Module "mod-100rel" registered
2017-01-26 09:01:23.853185 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  .Module "mod-pjsua" registered
2017-01-26 09:01:23.853508 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  .Module "mod-invite" registered
2017-01-26 09:01:23.893161 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): coreaudio_dev.  .. dev_id 0: iPhone IO device  (in=1, out=1) 8000Hz
2017-01-26 09:01:23.894608 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): coreaudio_dev.  ..core audio initialized
2017-01-26 09:01:23.912439 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4):          pjlib  ..select() I/O Queue created (0x1062cc028)
2017-01-26 09:01:23.913585 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(5):   conference.c  ..Creating conference bridge with 40 ports
2017-01-26 09:01:23.913711 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(5):   Master/sound  ..Using delay buffer with WSOLA.
WARNING: no real random source present!
2017-01-26 09:01:23.917111 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  .Module "mod-evsub" registered
2017-01-26 09:01:23.917223 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  .Module "mod-presence" registered
2017-01-26 09:01:23.917276 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(5):        evsub.c  .Event pkg "presence" registered by mod-presence
2017-01-26 09:01:23.917323 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  .Module "mod-mwi" registered
2017-01-26 09:01:23.917369 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(5):        evsub.c  .Event pkg "message-summary" registered by mod-mwi
2017-01-26 09:01:23.917414 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  .Module "mod-refer" registered
2017-01-26 09:01:23.917460 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(5):        evsub.c  .Event pkg "refer" registered by mod-refer
2017-01-26 09:01:23.917518 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  .Module "mod-pjsua-pres" registered
2017-01-26 09:01:23.917600 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  .Module "mod-pjsua-im" registered
2017-01-26 09:01:23.917648 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  .Module "mod-pjsua-options" registered
2017-01-26 09:01:23.917741 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4):   pjsua_core.c  .1 SIP worker threads created
2017-01-26 09:01:23.917802 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(3):   pjsua_core.c  .pjsua version 2.5.1 for iOS-10.2/arm-iPhone7,2/iOS-SDK initialized
2017-01-26 09:01:23.917855 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4):   pjsua_core.c  .PJSUA state changed: CREATED --> INIT
2017-01-26 09:01:23.917939 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(3): sip_endpoint.c  Module "mod-twilio-msg-interceptor" can not be unregistered: Not found (PJ_ENOTFOUND)
2017-01-26 09:01:23.917986 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  Module "mod-twilio-msg-interceptor" registered
2017-01-26 09:01:23.919443 SwiftVoiceCallKitQuickstart[2438:726429] [INFO Twilio] recreateMainTransport, Found valid IPv4 address: <IP_ADDRESS>
2017-01-26 09:01:23.919921 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4):    tlstp:49206  SIP TLS listener is ready for incoming connections at <IP_ADDRESS>:49206
2017-01-26 09:01:23.919979 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4):   pjsua_core.c  PJSUA state changed: INIT --> STARTING
2017-01-26 09:01:23.920056 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  .Module "mod-unsolicited-mwi" registered
2017-01-26 09:01:23.920104 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4):   pjsua_core.c  .PJSUA state changed: STARTING --> RUNNING
2017-01-26 09:01:23.920371 SwiftVoiceCallKitQuickstart[2438:726429] [VERBOSE Twilio] Inside initWithConfig:, codec: speex/16000/1 -> priority: 255
2017-01-26 09:01:23.920490 SwiftVoiceCallKitQuickstart[2438:726429] [VERBOSE Twilio] Inside initWithConfig:, codec: speex/8000/1 -> priority: 254
2017-01-26 09:01:23.920599 SwiftVoiceCallKitQuickstart[2438:726429] [VERBOSE Twilio] Inside initWithConfig:, codec: speex/32000/1 -> priority: 0
2017-01-26 09:01:23.920759 SwiftVoiceCallKitQuickstart[2438:726429] [VERBOSE Twilio] Inside initWithConfig:, codec: PCMU/8000/1 -> priority: 128
2017-01-26 09:01:23.921055 SwiftVoiceCallKitQuickstart[2438:726429] [VERBOSE Twilio] Inside initWithConfig:, codec: PCMA/8000/1 -> priority: 0
2017-01-26 09:01:23.922550 SwiftVoiceCallKitQuickstart[2438:726429] [DEBUG VoiceClient] Inside reconnect, releasing transports ...
2017-01-26 09:01:23.923782 SwiftVoiceCallKitQuickstart[2438:726429] [DEBUG VoiceClient] Inside reconnect, re-creating main transport ...
2017-01-26 09:01:23.924808 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4):    tlstp:49206  SIP TLS transport destroyed
2017-01-26 09:01:23.924897 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  Module "mod-twilio-msg-interceptor" unregistered
2017-01-26 09:01:23.924972 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): sip_endpoint.c  Module "mod-twilio-msg-interceptor" registered
2017-01-26 09:01:23.925503 SwiftVoiceCallKitQuickstart[2438:726429] [INFO Twilio] recreateMainTransport, Found valid IPv4 address: <IP_ADDRESS>
2017-01-26 09:01:23.925715 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4):    tlstp:49207  SIP TLS listener is ready for incoming connections at <IP_ADDRESS>:49207
2017-01-26 09:01:23.998294 SwiftVoiceCallKitQuickstart[2438:726429] providerDidBegin
2017-01-26 09:01:23.998652 SwiftVoiceCallKitQuickstart[2438:726429] pushRegistry:didUpdatePushCredentials:forType:
2017-01-26 09:01:24.454479 SwiftVoiceCallKitQuickstart[2438:726429] <73604f61 e0d77bb8 f29d5fd2 cf6c07a6 484a6a51 86c0bdff 6fecb2cd 1387f9ef>
2017-01-26 09:01:24.454961 SwiftVoiceCallKitQuickstart[2438:726429] [VERBOSE VoiceClient] Registering for Twilio push notifications
Access Token:	eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiIsImN0eSI6InR3aWxpby1mcGE7dj0xIn0.eyJqdGkiOiJTSzY3OTNhYmQ3ZDY3YzRjMDQ2ZmM4MDdmMTU2NmNjZjZiLTE0ODU0MzkyODQiLCJncmFudHMiOnsiaWRlbnRpdHkiOiJtYWh5YXJAaWxsdXNpdmUuY2EiLCJ2b2ljZSI6eyJvdXRnb2luZyI6eyJhcHBsaWNhdGlvbl9zaWQiOiJBUDgzODAyMjIyODc2Nzg1N2I1ODM4ZjIwMDI5NGJiYTdmIn19fSwiaWF0IjoxNDg1NDM5Mjg0LCJleHAiOjE0ODU0NDI4ODQsImlzcyI6IlNLNjc5M2FiZDdkNjdjNGMwNDZmYzgwN2YxNTY2Y2NmNmIiLCJzdWIiOiJBQzNhYzNhNjA0MDczNDIwZjc1ZDU2MmQwZjI4NWE4YjUzIn0.5PBOF19ySB-1SIyO0QKnTPottIrlWGf7TTvBaQAslJ4
VoIP Registry Token:	<73604f61 e0d77bb8 f29d5fd2 cf6c07a6 484a6a51 86c0bdff 6fecb2cd 1387f9ef>
2017-01-26 09:01:24.468879 SwiftVoiceCallKitQuickstart[2438:726429] TNNotificationClient[4]:        0x1af71dc40 | 01/26/09:01:24.468 | DEBUG    | 1      | TNNotificationClient | Default thread pool: Available: 16; Capacity: 16
2017-01-26 09:01:24.469135 SwiftVoiceCallKitQuickstart[2438:726429] TNNotificationClient[4]:        0x1af71dc40 | 01/26/09:01:24.468 | DEBUG    | 1      | TNNotificationClient | Not enough free threads in the default pool. Available: 16; Capacity: 16. Increasing capacity on 20
2017-01-26 09:01:24.469491 SwiftVoiceCallKitQuickstart[2438:726429] TNNotificationClient[4]:        0x1af71dc40 | 01/26/09:01:24.469 | DEBUG    | 1      | TNNotificationClient | New capacity of default thread pool: 36
2017-01-26 09:01:24.470799 SwiftVoiceCallKitQuickstart[2438:726517] TNNotificationClient[4]:        0x16e43f000 | 01/26/09:01:24.470 | DEBUG    | 1      | TNNotificationClient | Initializing...
2017-01-26 09:01:24.471487 SwiftVoiceCallKitQuickstart[2438:726517] TNNotificationMgr[4]:        0x16e43f000 | 01/26/09:01:24.470 | DEBUG    | 2      | TNNotificationMgr | Starting...
2017-01-26 09:01:24.475234 SwiftVoiceCallKitQuickstart[2438:726517] TNNotificationMgr[4]:        0x16e43f000 | 01/26/09:01:24.475 | DEBUG    | 2      | TNNotificationMgr | Started
2017-01-26 09:01:24.475448 SwiftVoiceCallKitQuickstart[2438:726517] TNRegistrationMgr[4]:        0x16e43f000 | 01/26/09:01:24.475 | DEBUG    | 9      | TNRegistrationMgr | Starting...
2017-01-26 09:01:24.475759 SwiftVoiceCallKitQuickstart[2438:726517] TNRegistrationMgr[4]:        0x16e43f000 | 01/26/09:01:24.475 | DEBUG    | 9      | TNRegistrationMgr | Started
2017-01-26 09:01:24.476053 SwiftVoiceCallKitQuickstart[2438:726517] TNNotificationClient[4]:        0x16e43f000 | 01/26/09:01:24.475 | DEBUG    | 1      | TNNotificationClient | Inited!
2017-01-26 09:01:24.476326 SwiftVoiceCallKitQuickstart[2438:726517] TNNotificationClient[2]:        0x16e43f000 | 01/26/09:01:24.476 | WARNING  | 1      | TNNotificationClient | Twilsock is not used!
2017-01-26 09:01:24.476607 SwiftVoiceCallKitQuickstart[2438:726517] TNNotificationClient[4]:        0x16e43f000 | 01/26/09:01:24.476 | DEBUG    | 1      | TNNotificationClient | Creating subscription..., mt: twilio.voice.call, channel: apn
2017-01-26 09:01:24.477274 SwiftVoiceCallKitQuickstart[2438:726517] TNRegistrationMgr[4]:        0x16e43f000 | 01/26/09:01:24.477 | DEBUG    | 9      | TNRegistrationMgr | New message type: twilio.voice.call, for channel: apn
2017-01-26 09:01:24.477799 SwiftVoiceCallKitQuickstart[2438:726517] TNNotificationClient[4]:        0x16e43f000 | 01/26/09:01:24.477 | DEBUG    | 1      | TNNotificationClient | Subscription is created, mt: twilio.voice.call
2017-01-26 09:01:24.478056 SwiftVoiceCallKitQuickstart[2438:726517] TNNotificationClient[4]:        0x16e43f000 | 01/26/09:01:24.477 | DEBUG    | 1      | TNNotificationClient | Creating subscription..., mt: twilio.voice.cancel, channel: apn
2017-01-26 09:01:24.478236 SwiftVoiceCallKitQuickstart[2438:726517] TNRegistrationMgr[4]:        0x16e43f000 | 01/26/09:01:24.478 | DEBUG    | 9      | TNRegistrationMgr | New message type: twilio.voice.cancel, for channel: apn
2017-01-26 09:01:24.478487 SwiftVoiceCallKitQuickstart[2438:726517] TNNotificationClient[4]:        0x16e43f000 | 01/26/09:01:24.478 | DEBUG    | 1      | TNNotificationClient | Subscription is created, mt: twilio.voice.cancel
2017-01-26 09:01:24.478836 SwiftVoiceCallKitQuickstart[2438:726517] TNNotificationClient[4]:        0x16e43f000 | 01/26/09:01:24.478 | DEBUG    | 1      | TNNotificationClient | Starting registration..., id: <73604f61 e0d77bb8 f29d5fd2 cf6c07a6 484a6a51 86c0bdff 6fecb2cd 1387f9ef>
2017-01-26 09:01:24.480562 SwiftVoiceCallKitQuickstart[2438:726517] TNRegSession[4]:        0x16e43f000 | 01/26/09:01:24.480 | DEBUG    | 10     | TNRegSession | Started
2017-01-26 09:01:24.481619 SwiftVoiceCallKitQuickstart[2438:726521] TNRegSession[3]:        0x16e66f000 | 01/26/09:01:24.481 | INFO     | 10     | TNRegSession | startRegistrationImpl >> Unregistered
2017-01-26 09:01:24.483437 SwiftVoiceCallKitQuickstart[2438:726521] TNUnregisteredState[3]:        0x16e66f000 | 01/26/09:01:24.482 | INFO     | 11     | TNUnregisteredState | Leaving state: Unregistered
2017-01-26 09:01:24.483516 SwiftVoiceCallKitQuickstart[2438:726522] TNRegTransport[4]:        0x16e6fb000 | 01/26/09:01:24.482 | DEBUG    | 12     | TNRegTransport | Creating registration: apn - <73604f61 e0d77bb8 f29d5fd2 cf6c07a6 484a6a51 86c0bdff 6fecb2cd 1387f9ef>
2017-01-26 09:01:24.483611 SwiftVoiceCallKitQuickstart[2438:726521] TNRegSession[3]:        0x16e66f000 | 01/26/09:01:24.483 | INFO     | 10     | TNRegSession | Change state: Unregistered --> Registering
2017-01-26 09:01:24.484062 SwiftVoiceCallKitQuickstart[2438:726521] TNRegisteringState[3]:        0x16e66f000 | 01/26/09:01:24.483 | INFO     | 15     | TNRegisteringState | Entering state: Registering
2017-01-26 09:01:24.486628 SwiftVoiceCallKitQuickstart[2438:726522] TNRegTransport[4]:        0x16e6fb000 | 01/26/09:01:24.486 | DEBUG    | 12     | TNRegTransport | Send post request to: https://ers.twilio.com/v1/registrations?productId=voice
2017-01-26 09:01:24.486884 SwiftVoiceCallKitQuickstart[2438:726522] TNHttpTransportClient[3]:        0x16e6fb000 | 01/26/09:01:24.486 | INFO     | 13     | TNHttpTransportClient | trying to send request to: https://ers.twilio.com/v1/registrations?productId=voice
2017-01-26 09:01:24.487241 SwiftVoiceCallKitQuickstart[2438:726522] TNRawHttp[3]:        0x16e6fb000 | 01/26/09:01:24.487 | INFO     | 14     | TNRawHttp | trying to sendRequest to https://ers.twilio.com/v1/registrations?productId=voice
2017-01-26 09:01:24.490104 SwiftVoiceCallKitQuickstart[2438:726523] TNRawHttp[4]:        0x16e787000 | 01/26/09:01:24.489 | DEBUG    | 14     | TNRawHttp | sendRequestImpl: ec60c42ae3cf11e695cd0200000000000000
2017-01-26 09:01:24.490880 SwiftVoiceCallKitQuickstart[2438:726523] TNRawHttp[4]:        0x16e787000 | 01/26/09:01:24.490 | DEBUG    | 14     | TNRawHttp | Sending request ec60c42ae3cf11e695cd0200000000000000 - 1
2017-01-26 09:01:24.754265 SwiftVoiceCallKitQuickstart[2438:726523] TNRawHttp[4]:        0x16e787000 | 01/26/09:01:24.716 | DEBUG    | 14     | TNRawHttp | Sending request ec60c42ae3cf11e695cd0200000000000000 - 2
2017-01-26 09:01:24.832484 SwiftVoiceCallKitQuickstart[2438:726523] TNRawHttp[4]:        0x16e787000 | 01/26/09:01:24.832 | DEBUG    | 14     | TNRawHttp | sendResponse: 201: Created for: ec60c42ae3cf11e695cd0200000000000000, payload: present
2017-01-26 09:01:24.834851 SwiftVoiceCallKitQuickstart[2438:726523] TNRawHttp[4]:        0x16e787000 | 01/26/09:01:24.834 | DEBUG    | 14     | TNRawHttp | Free sessions pool has 1 keys
2017-01-26 09:01:24.837061 SwiftVoiceCallKitQuickstart[2438:726523] TNRawHttp[4]:        0x16e787000 | 01/26/09:01:24.834 | DEBUG    | 14     | TNRawHttp | key: https://ers.twilio.com443 has 1 sessions
2017-01-26 09:01:24.838960 SwiftVoiceCallKitQuickstart[2438:726522] TNRegTransport[4]:        0x16e6fb000 | 01/26/09:01:24.837 | DEBUG    | 12     | TNRegTransport | Registration is created, location: https://ers.us1.twilio.com/v1/registrations/1e7c977e16394c3dabfc8839854a8aef
2017-01-26 09:01:24.840419 SwiftVoiceCallKitQuickstart[2438:726521] TNRegSession[3]:        0x16e66f000 | 01/26/09:01:24.839 | INFO     | 10     | TNRegSession | regCreatedImpl >> Registering
2017-01-26 09:01:24.840665 SwiftVoiceCallKitQuickstart[2438:726521] TNRegisteringState[3]:        0x16e66f000 | 01/26/09:01:24.840 | INFO     | 15     | TNRegisteringState | Leaving state: Registering
2017-01-26 09:01:24.840835 SwiftVoiceCallKitQuickstart[2438:726521] TNRegSession[3]:        0x16e66f000 | 01/26/09:01:24.840 | INFO     | 10     | TNRegSession | Change state: Registering --> Registered
2017-01-26 09:01:24.841000 SwiftVoiceCallKitQuickstart[2438:726521] TNActiveState[3]:        0x16e66f000 | 01/26/09:01:24.840 | INFO     | 16     | TNActiveState | Entering state: Registered
2017-01-26 09:01:24.841849 SwiftVoiceCallKitQuickstart[2438:726478] [INFO VoiceClient] Inside register:deviceToken:completion:, registered for Twilio push notifications.
2017-01-26 09:01:24.842246 SwiftVoiceCallKitQuickstart[2438:726478] Successfully registered for VoIP push notifications.
2017-01-26 09:01:24.843324 SwiftVoiceCallKitQuickstart[2438:726478] TNNotificationClient[4]:        0x16dec7000 | 01/26/09:01:24.843 | DEBUG    | 1      | TNNotificationClient | Default thread pool: Available: 33; Capacity: 36
2017-01-26 09:01:24.843902 SwiftVoiceCallKitQuickstart[2438:726517] TNNotificationClient[4]:        0x16e43f000 | 01/26/09:01:24.843 | DEBUG    | 1      | TNNotificationClient | Shutting down...
2017-01-26 09:01:24.844169 SwiftVoiceCallKitQuickstart[2438:726517] TNRegistrationMgr[4]:        0x16e43f000 | 01/26/09:01:24.844 | DEBUG    | 9      | TNRegistrationMgr | Stopping...
2017-01-26 09:01:24.844617 SwiftVoiceCallKitQuickstart[2438:726521] TNRegSession[4]:        0x16e66f000 | 01/26/09:01:24.844 | DEBUG    | 10     | TNRegSession | Stopping... : apn
2017-01-26 09:01:24.845016 SwiftVoiceCallKitQuickstart[2438:726521] TNRegSession[4]:        0x16e66f000 | 01/26/09:01:24.844 | DEBUG    | 10     | TNRegSession | Stopped
2017-01-26 09:01:24.845481 SwiftVoiceCallKitQuickstart[2438:726517] TNRegSession[4]:        0x16e43f000 | 01/26/09:01:24.845 | DEBUG    | 10     | TNRegSession | ~TNRegSession - begin
2017-01-26 09:01:24.845868 SwiftVoiceCallKitQuickstart[2438:726517] TNRegSession[4]:        0x16e43f000 | 01/26/09:01:24.845 | DEBUG    | 10     | TNRegSession | ~TNRegSession - end
2017-01-26 09:01:24.846185 SwiftVoiceCallKitQuickstart[2438:726517] TNRegTransport[4]:        0x16e43f000 | 01/26/09:01:24.846 | DEBUG    | 12     | TNRegTransport | ~TNRegTransport - begin
2017-01-26 09:01:24.846369 SwiftVoiceCallKitQuickstart[2438:726517] TNHttpTransportClient[3]:        0x16e43f000 | 01/26/09:01:24.846 | INFO     | 13     | TNHttpTransportClient | shutting down...
2017-01-26 09:01:24.846644 SwiftVoiceCallKitQuickstart[2438:726517] TNRawHttp[4]:        0x16e43f000 | 01/26/09:01:24.846 | DEBUG    | 14     | TNRawHttp | ~TNRawHttp - start
2017-01-26 09:01:24.846819 SwiftVoiceCallKitQuickstart[2438:726517] TNRawHttp[4]:        0x16e43f000 | 01/26/09:01:24.846 | DEBUG    | 14     | TNRawHttp | ~TNRawHttp - end
2017-01-26 09:01:24.847082 SwiftVoiceCallKitQuickstart[2438:726522] TNRegTransport[4]:        0x16e6fb000 | 01/26/09:01:24.845 | DEBUG    | 12     | TNRegTransport | Stop() - begin
2017-01-26 09:01:24.848450 SwiftVoiceCallKitQuickstart[2438:726522] TNHttpTransportClient[3]:        0x16e6fb000 | 01/26/09:01:24.848 | INFO     | 13     | TNHttpTransportClient | shutting down...
2017-01-26 09:01:24.849558 SwiftVoiceCallKitQuickstart[2438:726517] TNHttpTransportClient[3]:        0x16e43f000 | 01/26/09:01:24.849 | INFO     | 13     | TNHttpTransportClient | shutdown complete
2017-01-26 09:01:24.849669 SwiftVoiceCallKitQuickstart[2438:726522] TNHttpTransportClient[3]:        0x16e6fb000 | 01/26/09:01:24.849 | INFO     | 13     | TNHttpTransportClient | shutdown complete
2017-01-26 09:01:24.849992 SwiftVoiceCallKitQuickstart[2438:726522] TNRegTransport[4]:        0x16e6fb000 | 01/26/09:01:24.849 | DEBUG    | 12     | TNRegTransport | Stop() - end
2017-01-26 09:01:24.851028 SwiftVoiceCallKitQuickstart[2438:726522] TNRegTransport[4]:        0x16e6fb000 | 01/26/09:01:24.850 | DEBUG    | 12     | TNRegTransport | Stop() - begin
2017-01-26 09:01:24.851422 SwiftVoiceCallKitQuickstart[2438:726522] TNRegTransport[4]:        0x16e6fb000 | 01/26/09:01:24.851 | DEBUG    | 12     | TNRegTransport | Stop() - end
2017-01-26 09:01:24.851847 SwiftVoiceCallKitQuickstart[2438:726517] TNRegTransport[4]:        0x16e43f000 | 01/26/09:01:24.851 | DEBUG    | 12     | TNRegTransport | ~TNRegTransport - end
2017-01-26 09:01:24.852134 SwiftVoiceCallKitQuickstart[2438:726517] TNHttpTransportClient[4]:        0x16e43f000 | 01/26/09:01:24.851 | DEBUG    | 13     | TNHttpTransportClient | ~TNHttpTransportClient - begin
2017-01-26 09:01:24.852505 SwiftVoiceCallKitQuickstart[2438:726517] TNHttpTransportClient[4]:        0x16e43f000 | 01/26/09:01:24.852 | DEBUG    | 13     | TNHttpTransportClient | ~TNHttpTransportClient - end
2017-01-26 09:01:24.854081 SwiftVoiceCallKitQuickstart[2438:726517] TNRegistrationMgr[4]:        0x16e43f000 | 01/26/09:01:24.853 | DEBUG    | 9      | TNRegistrationMgr | Stopped
2017-01-26 09:01:24.854601 SwiftVoiceCallKitQuickstart[2438:726517] TNNotificationMgr[4]:        0x16e43f000 | 01/26/09:01:24.854 | DEBUG    | 2      | TNNotificationMgr | Stopping...
2017-01-26 09:01:24.855164 SwiftVoiceCallKitQuickstart[2438:726517] TNNotificationMgr[4]:        0x16e43f000 | 01/26/09:01:24.854 | DEBUG    | 2      | TNNotificationMgr | Stopped
2017-01-26 09:01:24.855501 SwiftVoiceCallKitQuickstart[2438:726518] Notification queue worker[4]:        0x16e4cb000 | 01/26/09:01:24.855 | DEBUG    | Notification queue worker | Exit
2017-01-26 09:01:24.855767 SwiftVoiceCallKitQuickstart[2438:726517] TNNotificationClient[4]:        0x16e43f000 | 01/26/09:01:24.855 | DEBUG    | 1      | TNNotificationClient | Shut down complete!
2017-01-26 09:01:24.855972 SwiftVoiceCallKitQuickstart[2438:726519] Notification queue worker[4]:        0x16e557000 | 01/26/09:01:24.855 | DEBUG    | Notification queue worker | Exit
2017-01-26 09:01:24.856666 SwiftVoiceCallKitQuickstart[2438:726520] Notification queue worker[4]:        0x16e5e3000 | 01/26/09:01:24.855 | DEBUG    | Notification queue worker | Exit
2017-01-26 09:01:24.857185 SwiftVoiceCallKitQuickstart[2438:726478] TNNotificationClient[4]:        0x16dec7000 | 01/26/09:01:24.856 | DEBUG    | 1      | TNNotificationClient | ~TNNotificationClient - begin
2017-01-26 09:01:24.857636 SwiftVoiceCallKitQuickstart[2438:726478] TNNotificationClient[4]:        0x16dec7000 | 01/26/09:01:24.857 | DEBUG    | 1      | TNNotificationClient | ~TNNotificationClient - end
2017-01-26 09:01:24.857996 SwiftVoiceCallKitQuickstart[2438:726478] TNNotificationMgr[4]:        0x16dec7000 | 01/26/09:01:24.857 | DEBUG    | 2      | TNNotificationMgr | ~TNNotificationMgr - begin
2017-01-26 09:01:24.858339 SwiftVoiceCallKitQuickstart[2438:726478] TNNotificationMgr[4]:        0x16dec7000 | 01/26/09:01:24.858 | DEBUG    | 2      | TNNotificationMgr | ~TNNotificationMgr - end
2017-01-26 09:01:33.060437 SwiftVoiceCallKitQuickstart[2438:726480] StartCallAction transaction request successful
2017-01-26 09:01:33.090295 SwiftVoiceCallKitQuickstart[2438:726429] provider:performStartCallAction:
2017-01-26 09:01:33.350987 SwiftVoiceCallKitQuickstart[2438:726429] [VERBOSE VoiceClient] Inside configureAudioSession, preparing audio session.
2017-01-26 09:02:01.371252 SwiftVoiceCallKitQuickstart[2438:726429] [DEBUG TVOReachability] Reachability Flag Status: -R ------- networkStatusForFlags
2017-01-26 09:02:01.372507 SwiftVoiceCallKitQuickstart[2438:726429] [DEBUG TVOCommandHandler] Inside postCommand:, received command of type TVOMakeCallCommand
2017-01-26 09:02:01.378921 SwiftVoiceCallKitQuickstart[2438:726671] [VERBOSE Twilio] Inside constructUri: Registration URL: sip:None@chunderm.gll.twilio.com;transport=tls
2017-01-26 09:02:01.379315 SwiftVoiceCallKitQuickstart[2438:726671] [INFO TVOMakeCallCommand] Call URI: sip:None@chunderm.gll.twilio.com;transport=tls
2017-01-26 09:02:01.384037 SwiftVoiceCallKitQuickstart[2438:726671] [DEBUG TVOConstants] X-Twilio-Client string: {"p":"ios","v":"2.0.0","mobile":{"arch":"arm64","product":"iPhone","name":"iPhone7,2","v":"10.2"}}, inside TVOConstants clientString
2017-01-26 09:02:01.406393 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(4):    pjsua_acc.c !Adding account<EMAIL_ADDRESS>2017-01-26 09:02:01.423636 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(4):    pjsua_acc.c  .Account<EMAIL_ADDRESS>added with id 0
2017-01-26 09:02:01.457294 SwiftVoiceCallKitQuickstart[2438:726671] [VERBOSE TVOCall] Inside makeCall, record permission was granted
2017-01-26 09:02:01.457485 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(4):   pjsua_call.c  Making call with acc #0 to sip:None@chunderm.gll.twilio.com;transport=tls
2017-01-26 09:02:01.458775 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(4):    pjsua_acc.c  .Warning: cannot use source TCP/TLS socket address for Contact when nameserver is configured.
2017-01-26 09:02:01.459504 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5): dlg0x103845ea8  .UAC dialog created
2017-01-26 09:02:01.459818 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5): dlg0x103845ea8  ..Session count inc to 2 by mod-pjsua
2017-01-26 09:02:01.460118 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(4):  pjsua_media.c  .Call 0: initializing media..
2017-01-26 09:02:01.460479 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(4):  pjsua_media.c  ..RTP socket reachable at <IP_ADDRESS>:4320
2017-01-26 09:02:01.460594 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(4):  pjsua_media.c  ..RTCP socket reachable at <IP_ADDRESS>:4321
2017-01-26 09:02:01.460912 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(4):  pjsua_media.c  ..Media index 0 selected for audio call 0
2017-01-26 09:02:01.461051 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5): dlg0x103845ea8  ..Session count dec to 2 by mod-pjsua
2017-01-26 09:02:01.461697 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5): dlg0x103845ea8  .Module mod-invite added as dialog usage, data=0x102dc9f88
2017-01-26 09:02:01.461840 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5): dlg0x103845ea8  ..Session count inc to 4 by mod-invite
2017-01-26 09:02:01.462148 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5): dlg0x103845ea8  .Module mod-100rel added as dialog usage, data=0x102dca1b4
2017-01-26 09:02:01.462259 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5): dlg0x103845ea8  .100rel module attached
2017-01-26 09:02:01.462424 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5): inv0x103845ea8  .UAC invite session created for dialog dlg0x103845ea8
2017-01-26 09:02:01.463964 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5):       endpoint  .Request msg INVITE/cseq=18187 (tdta0x10307c800) created.
2017-01-26 09:02:01.464810 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5): inv0x103845ea8  ..Sending Request msg INVITE/cseq=18187 (tdta0x10307c800)
2017-01-26 09:02:01.464946 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5): dlg0x103845ea8  ...Sending Request msg INVITE/cseq=18187 (tdta0x10307c800)
2017-01-26 09:02:01.465267 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5): tsx0x10307d8a8  ....Transaction created for Request msg INVITE/cseq=18186 (tdta0x10307c800)
2017-01-26 09:02:01.465532 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5): tsx0x10307d8a8  ...Sending Request msg INVITE/cseq=18186 (tdta0x10307c800) in state Null
2017-01-26 09:02:01.465792 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5):  sip_resolve.c  ....Starting async DNS SRV query: target=_sips._tcp.chunderm.gll.twilio.com, transport=TLS, port=0
2017-01-26 09:02:01.467052 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5): _sips._tcp.chu  ....Starting async DNS SRV query_job: target=_sips._tcp.chunderm.gll.twilio.com:5061
2017-01-26 09:02:01.470075 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5): tsx0x10307d8a8  ....State changed from Null to Calling, event=TX_MSG
2017-01-26 09:02:01.470219 SwiftVoiceCallKitQuickstart[2438:726671] PJSIP(5): dlg0x103845ea8  .....Transaction tsx0x10307d8a8 state changed to Calling
2017-01-26 09:02:01.470650 SwiftVoiceCallKitQuickstart[2438:726671] [DEBUG Twilio] Inside on_call_state(), call: 0x1700cdac0, internal state: 1
2017-01-26 09:02:01.470853 SwiftVoiceCallKitQuickstart[2438:726671] [VERBOSE Twilio] Inside on_call_state(), PJSIP_INV_STATE_CALLING
2017-01-26 09:02:01.471044 SwiftVoiceCallKitQuickstart[2438:726671] [VERBOSE TVOOutgoingCall] handlePJSIPInviteStateCalling. Error: (null)
2017-01-26 09:02:01.471213 SwiftVoiceCallKitQuickstart[2438:726671] [VERBOSE Twilio] on_call_tsx_state(), state: 1, status_code: 0: (null)
2017-01-26 09:02:01.508177 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5):     resolver.c !Received 208 bytes DNS response from <IP_ADDRESS>:0
2017-01-26 09:02:01.512866 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5): _sips._tcp.chu  SRV query_job for _sips._tcp.chunderm.gll.twilio.com completed, 2 of 2 total entries selected:
2017-01-26 09:02:01.513147 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5): _sips._tcp.chu   0: SRV 10 100 10194 chunderm1.us1.twilio.com (-)
2017-01-26 09:02:01.513210 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5): _sips._tcp.chu   1: SRV 10 100 10194 chunderm0.us1.twilio.com (-)
2017-01-26 09:02:01.513256 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5): _sips._tcp.chu  Starting async DNS A query_job for chunderm1.us1.twilio.com
2017-01-26 09:02:01.514943 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5): _sips._tcp.chu  Starting async DNS A query_job for chunderm0.us1.twilio.com
2017-01-26 09:02:01.516053 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5):     resolver.c  Received 82 bytes DNS response from <IP_ADDRESS>:0
2017-01-26 09:02:01.516131 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5): _sips._tcp.chu  DNS A for chunderm1.us1.twilio.com: <IP_ADDRESS>
2017-01-26 09:02:01.516262 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5):     resolver.c  Received 82 bytes DNS response from <IP_ADDRESS>:0
2017-01-26 09:02:01.516314 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5): _sips._tcp.chu  DNS A for chunderm0.us1.twilio.com: <IP_ADDRESS>
2017-01-26 09:02:01.516358 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5): _sips._tcp.chu  Server resolution complete, 2 server entry(s) found
2017-01-26 09:02:01.516436 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(4): tlsc0x1038fe22  TLS client transport created
2017-01-26 09:02:01.516959 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(4): tlsc0x1038fe22  TLS transport <IP_ADDRESS>:49210 is connecting to chunderm.gll.twilio.com:10194...
2017-01-26 09:02:01.519940 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(4): \367
2017-01-26 09:02:01.682592 SwiftVoiceCallKitQuickstart[2438:726429] provider:didActivateAudioSession:
2017-01-26 09:02:01.682792 SwiftVoiceCallKitQuickstart[2438:726429] [VERBOSE VoiceClient] Inside startAudioDevice, starting audio device.
2017-01-26 09:02:01.682904 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4):    pjsua_aud.c !Set sound device: capture=-1, playback=-2
2017-01-26 09:02:01.682983 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4):    pjsua_aud.c  .Opening sound device (speaker + mic) PCM@16000/1/20ms
2017-01-26 09:02:01.683088 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): coreaudio_dev.  ..Using VoiceProcessingIO audio unit
2017-01-26 09:02:01.982398 SwiftVoiceCallKitQuickstart[2438:726429] PJSIP(4): coreaudio_dev.  ..core audio stream started
2017-01-26 09:02:02.004378 SwiftVoiceCallKitQuickstart[2438:726716] PJSIP(5): coreaudio_dev. !Recorder thread started, (372 frames)
2017-01-26 09:02:02.004561 SwiftVoiceCallKitQuickstart[2438:726716] PJSIP(4): os_core_unix.c  Info: possibly re-registering existing thread
2017-01-26 09:02:02.004617 SwiftVoiceCallKitQuickstart[2438:726716] PJSIP(5): coreaudio_dev. !Player thread started, (372 frames)
2017-01-26 09:02:33.472233 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5): tsx0x10307d8a8 !Timeout timer event
2017-01-26 09:02:33.472635 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5): tsx0x10307d8a8  .State changed from Calling to Terminated, event=TIMER
2017-01-26 09:02:33.472804 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5): dlg0x103845ea8  ..Transaction tsx0x10307d8a8 state changed to Terminated
2017-01-26 09:02:33.474033 SwiftVoiceCallKitQuickstart[2438:726502] [VERBOSE Twilio] on_call_tsx_state(), state: 6, status_code: 408: Request Timeout
2017-01-26 09:02:33.479079 SwiftVoiceCallKitQuickstart[2438:726502] [DEBUG Twilio] Inside on_call_state(), call: 0x1700cdac0, internal state: 1
2017-01-26 09:02:33.479643 SwiftVoiceCallKitQuickstart[2438:726502] [VERBOSE Twilio] Inside on_call_state(), PJSIP_INV_STATE_DISCONNECTED, internal state: 1, last_status: 408
2017-01-26 09:02:33.480623 SwiftVoiceCallKitQuickstart[2438:726502] [WARN Twilio] Inside Twilio.transportToTwilioErrorCode(): 408
2017-01-26 09:02:33.481897 SwiftVoiceCallKitQuickstart[2438:726502] [VERBOSE TVOOutgoingCall] handlePJSIPInviteStateDisconnected. Error: <TwilioError: 0x17005b510>
2017-01-26 09:02:33.483449 SwiftVoiceCallKitQuickstart[2438:726502] [DEBUG VoiceClient] Inside removeFromActiveOutgoingCalls:, remove outgoing call <TVOOutgoingCall: 0x1700cdac0> from active outgoing calls
2017-01-26 09:02:33.485162 SwiftVoiceCallKitQuickstart[2438:726502] [DEBUG TVORTCMonitorThresholds] No thresholds specified. Default values will be applied.
2017-01-26 09:02:33.487324 SwiftVoiceCallKitQuickstart[2438:726502] [VERBOSE TVORTCMonitorThresholds] Thresholds for the RTC-monitor: {
    "audio_input_level" =     {
        TVOEndpointAnalyticsThresholdMaxDuration = 10;
    };
    "audio_output_level" =     {
        TVOEndpointAnalyticsThresholdMaxDuration = 10;
    };
    jitter =     {
        TVOEndpointAnalyticsThresholdMax = 30;
    };
    mos =     {
        TVOEndpointAnalyticsThresholdMin = 3;
    };
    "packets_lost_fraction" =     {
        TVOEndpointAnalyticsThresholdMax = 1;
    };
    rtt =     {
        TVOEndpointAnalyticsThresholdMax = 400;
    };
}
2017-01-26 09:02:33.490076 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(4):  pjsua_media.c  ....Call 0: deinitializing media..
2017-01-26 09:02:33.490349 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(4):  pjsua_media.c  .....Call 0: cleaning up provisional media, prov_med_cnt=1, med_cnt=0
2017-01-26 09:02:33.492870 SwiftVoiceCallKitQuickstart[2438:726429] outgoingCall:didFailWithError: Twilio Services Error
2017-01-26 09:02:33.493068 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5): dlg0x103845ea8  ....Session count dec to 1 by mod-invite
2017-01-26 09:02:33.493229 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5): dlg0x103845ea8  ...Dialog destroyed
2017-01-26 09:02:33.498636 SwiftVoiceCallKitQuickstart[2438:726672] EndCallAction transaction request successful
2017-01-26 09:02:33.502648 SwiftVoiceCallKitQuickstart[2438:726429] provider:performEndCallAction:
2017-01-26 09:02:33.502968 SwiftVoiceCallKitQuickstart[2438:726429] [VERBOSE VoiceClient] Inside stopAudioDevice, stopping audio device.
2017-01-26 09:02:33.509942 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5): tsx0x10307d8a8  Timeout timer event
2017-01-26 09:02:33.510275 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(5): tsx0x10307d8a8  .State changed from Terminated to Destroyed, event=TIMER
2017-01-26 09:02:35.273829 SwiftVoiceCallKitQuickstart[2438:726429] provider:didDeactivateAudioSession:
2017-01-26 09:02:36.493350 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(4):    pjsua_aud.c  Closing sound device after idle for 3 second(s)
2017-01-26 09:02:36.500867 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(4):    pjsua_aud.c  .Closing iPhone IO device sound playback device and iPhone IO device sound capture device
2017-01-26 09:02:36.502761 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(4): coreaudio_dev.  .core audio stream stopped
2017-01-26 09:02:43.749380 SwiftVoiceCallKitQuickstart[2438:726502] [DEBUG Twilio] on_transport_state(): 0
2017-01-26 09:02:43.749948 SwiftVoiceCallKitQuickstart[2438:726502] [DEBUG Twilio] ------>Transport connected: 0x38fe228, inside transportConnected:
2017-01-26 09:02:43.751071 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(4): tlsc0x1038fe22  TLS transport <IP_ADDRESS>:49210 is connected to chunderm.gll.twilio.com:10194
2017-01-26 09:02:57.728455 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(4): tlsc0x1038fe22  TLS connection closed
2017-01-26 09:02:57.728920 SwiftVoiceCallKitQuickstart[2438:726502] [DEBUG Twilio] on_transport_state(): 1
2017-01-26 09:02:57.729574 SwiftVoiceCallKitQuickstart[2438:726502] [DEBUG Twilio] ------>Transport disconnected: 0x1038fe228, inside transportDisconnected:
2017-01-26 09:02:57.729802 SwiftVoiceCallKitQuickstart[2438:726502] PJSIP(4):    pjsua_acc.c  Disconnected notification for transport tlsc0x1038fe228
2017-01-26 09:02:57.730643 SwiftVoiceCallKitQuickstart[2438:726502] [DEBUG Twilio] on_transport_state(): 2
2017-01-26 09:02:57.731710 SwiftVoiceCallKitQuickstart[2438:726502] [DEBUG Twilio] ------>Transport disconnected: 0x1038fe228, inside transportDisconnected:

Hi @mahyarr
2019-02-07 18:53:37.801754+0530 Happy App [1412:635354] [ERROR TVOCall] Inside provideStats, failed to get call signal level
how to do fix this issue.
Can help on this

Hi @ramohanreddy
Sorry this might look scary but this is an internal error when the SDK is trying to get the audio level of the call. The application should not have to worry about this.
Thanks.


Refresh docs for 1.0.0

1.0.0 will have new features that need to be explained in the docs.
We need to continue evaluating how well the docs convey the team's vision for AppScope and how to use it; and, improving the docs based on that assessment.
As for every release, we need to clean up little things that need fixing, like an image that doesn't work in dark mode, etc.

Requested priority
High

Fixed in https://github.com/criblio/appscope/pull/784


For HandlerTypePredicate, provide support for knife4j-springdoc-ui's ui

This issue may be related to https://github.com/springdoc/springdoc-openapi/issues/1258 .
Below are the relevant JAR versions.
<!-- https://mvnrepository.com/artifact/org.springdoc/springdoc-openapi-ui -->
        <dependency>
            <groupId>org.springdoc</groupId>
            <artifactId>springdoc-openapi-ui</artifactId>
            <version>1.6.4</version>
        </dependency>
        <dependency>
            <groupId>org.springdoc</groupId>
            <artifactId>springdoc-openapi-security</artifactId>
            <version>1.6.4</version>
        </dependency>
        <!-- https://mvnrepository.com/artifact/com.github.xiaoymin/knife4j-springdoc-ui -->
        <dependency>
            <groupId>com.github.xiaoymin</groupId>
            <artifactId>knife4j-springdoc-ui</artifactId>
            <version>3.0.3</version>
        </dependency>

Due to business requirements, I need to override configurePathMatch() in a subclass of WebMvcConfigurer, the code is as follows
@Configuration
public class MyWebMvcConfig implements WebMvcConfigurer {
    @Override
    public void configurePathMatch(PathMatchConfigurer configurer) {
        configurer
                .addPathPrefix("/rest", c -> c.isAnnotationPresent(RestController.class))
        ;
    }
}

At this point for springdoc, I need to configure springdoc.swagger-ui.url to /rest/v3/api-docs.
So far everything is fine and springdoc-ui works fine. However, the documentation of knife4j reports an error.

Hope knife4j can adapt to springdoc's ui to allow users to configure the path of custom OpenAPI file.

It was my fault, I found out that I can qualify the package like below. The limitation solved the problem.
@Override
     public void configurePathMatch(PathMatchConfigurer configurer) {
         configurer.addPathPrefix("/rest", HandlerTypePredicate.forAnnotation(RestController.class)
                 .and(HandlerTypePredicate.forBasePackage("com.lingh.controller")));
     }


Download button should be shown by default

Would it be possible to show the "Download" button by default when an Instagram page loads?
This will certainly save some hassle.

Actually, reading about it and also thinking that on what basis should we do that, as it only grabs posts at a time. 😅


Removed package-lock.json file it should not be added to repository

@tskorupka Thank You for your time so much. Today your fixes was published to npm. New version is available v1.0.3. You can try using it! In my case component works fine. If anything goes wrong please write there. Thank you.


Consider adding APB to CRD conversion command

For APB as operator use-cases, we may want the ability to turn known APB specs into CRDs so that they can be loaded into OLM.
@fabianvf and @shawn-hurley hoping you can flesh out the details of what is desired here for future consideration.

Sounds like @fabianvf already has some code for this in the works, but no plans to add until after 3.11 unless something changes.


send ERR_SUMMONDISABLED and ERR_USERSDISABLED?

@koraggknightwolf points out that we do not send these:
       445    ERR_SUMMONDISABLED
              ":SUMMON has been disabled"

         - Returned as a response to the SUMMON command.  MUST be
           returned by any server which doesn't implement it.

       446    ERR_USERSDISABLED
              ":USERS has been disabled"

         - Returned as a response to the USERS command.  MUST be
           returned by any server which does not implement it.

SUMMON and USERS are weird really old commands designed around the assumption that users are accessing IRC locally and all that sorta junk. I'd rather not special-case those two commands just because a 20 year ago document said we MUST, clients will get the message either way. I think Insp also sends the unknown command numeric for at least summon when the module isn't loaded, but that's more of a side note and not a reason why I reckon we should leave our behaviour as-is.

I checked the inspircd testnet and they send 445 and 446 in these cases. As discussed, I wouldn't mind sending these, it's sort of a cute easter egg :-)


Update product support rotation docs

Follow-up action:

[x] document a way to submit bugs, and that the PM on rotation needs to assign those to the right team
[x] update Zapier automation to only post to productboard for non-trivial feedback items

[ ]  work with analytics to get NPS ingested into a dashboarding solution

One thing I realized doing this is ...  productboard is bad. There is no API for processing notes no automation. Integrations are broken.
The workflow for triaging notes is horrible, and it's hard to customized.
I'm wondering if all suggestions shouldn't be in a GitHub repo, that would be much easier to triage. This is obviously out of scope for this PR.

Serina: From my perspective both NPS as well as the happiness score would be more helpful in an aggregated dashboard type view.  I think we could do some interesting cloud mapping etc from the text feedback and review the txt feedback in a bulk fashion somewhere besides slack.  I personally find each NPS and happiness score being pumped into the #feedback channel noisy.

Having a stream of feedback in #feedback channel is perceived as very useful by majority, although folks agree that monthly rollup would be useful as well

@macraig @Joelkw I made a few suggestions, and merged everything into the handbook. AS ice cream machine experts, would love your feedback. In particular, sounds like we only asked the PM on feedback rotation to triage NPS/widget productboard notes, but manually submitted notes do not get triaged, so this should be included.

@benvenker as a user that had to onboard this, does this page help? Anything that is unclear? I will record a loom in addition to the written doc to make sure this is as easy as possible.

Follow-up action:

[x] document a way to submit bugs, and that the PM on rotation needs to assign those to the right team
[x] update Zapier automation to only post to productboard for non-trivial feedback items

[ ]  work with analytics to get NPS ingested into a dashboarding solution

One thing I realized doing this is ...  productboard is bad. There is no API for processing notes no automation. Integrations are broken.
The workflow for triaging notes is horrible, and it's hard to customized.
I'm wondering if all suggestions shouldn't be in a GitHub repo, that would be much easier to triage. This is obviously out of scope for this PR.

@benvenker as a user that had to onboard this, does this page help? Anything that is unclear? I will record a loom in addition to the written doc to make sure this is as easy as possible.

@malomarrec it was unclear to me (at least on first reading) the main was who exactly fell into the category of people I should reach out to.

Just to copy them here @malomarrec  – my feedback on productboard and why I'd be against moving those issues to GH: https://sourcegraph.slack.com/archives/C01SD4A49E1/p1644370854804699?thread_ts=1644320408.794419&cid=C01SD4A49E1


Review custom styles on www.nhs.uk and NHS digital service manual

What
Review custom styles on www.nhs.uk and NHS digital service manual.
Why
The NHS website and NHS digital service manual has a lot of custom styles on top of the core NHS.UK frontend library. Some of these styles will be hot fixes that should really be in the frontend library, but some will be new components or styles specific to these websites.
Tasks

[ ] Move any hotfixes into the NHS.UK frontend
[ ] Determine if there are any common custom components and consolidate them
[ ] Determine whether we need to add these custom components to the frontend library
[ ] Reduce the number of custom styles within these 2 code bases

To do this sprint

To do this sprint

NHS website custom styles
General styles (css/components)

[ ] Can we remove the guides navigation?
[ ] Can we remove the feedback banner?
[ ] Do we need to add the video and related nav components to the frontend library?
[ ] Refactor the Homepage styles

Shame specific (_shame.scss)

[ ] Review promo styles when Card is implemented (nhsuk-promo--mute)
[ ] Custom NDOP styles (ndop-download__link, ndop-download__thumbnail) - can these be removed?
[ ] Top tasks styles (nhsuk-top-tasks) - speak with IA about the future of these
[ ] Default image styling (max-width: 100%;) - does this need adding to frontend library?
[ ] Image credit styles - does this need adding to frontend library?
[ ] Review tools block spacing
[ ] Review App store download styles
[ ] Review table styles (nhsuk-table-responsive and table-image)

IA specific (_ia-beta.scss)

[ ] What are the next steps for the IA syles?

Print styles (_print.scss)

[ ] Refactor / remove / add to frontend library

NHS website custom styles
General styles (css/components)

[ ] Can we remove the guides navigation?
[ ] Can we remove the feedback banner?
[ ] Do we need to add the video and related nav components to the frontend library?
[ ] Refactor the Homepage styles

Shame specific (_shame.scss)

[ ] Review promo styles when Card is implemented (nhsuk-promo--mute)
[ ] Custom NDOP styles (ndop-download__link, ndop-download__thumbnail) - can these be removed?
[ ] Top tasks styles (nhsuk-top-tasks) - speak with IA about the future of these
[ ] Default image styling (max-width: 100%;) - does this need adding to frontend library?
[ ] Image credit styles - does this need adding to frontend library?
[ ] Review tools block spacing
[ ] Review App store download styles
[ ] Review table styles (nhsuk-table-responsive and table-image)

IA specific (_ia-beta.scss)

[ ] What are the next steps for the IA syles?

Print styles (_print.scss)

[ ] Refactor / remove / add to frontend library


GPU out of memory issue on full day demand (~20M trips)

There are ~20M trips for the full day, but when we run it in MANTA from 0-24 hr time range, it produces a GPU out of memory error. The la
@julianpalladino has run a couple of things already to understand what is going on:

Test on both his PC and beirut. Both produce the out of memory error.
Memory check on beirut, which produced no errors or leaks. There's nothing wrong the GPU itself.

This has revealed no hardware or system issues. Further investigation notes that the data structures going between CPU and GPU are at most ~1.3GB:
trafficPersonVec size = 20146022
indexPathVec size =<PHONE_NUMBER>
edgesData size = 627199
laneMap size =<PHONE_NUMBER>

Beirut has 8GB of GPU memory, so this shouldn't be an issue, but it's unclear. This requires more investigation.

This is going to be tested once we get the GCP server up and running with MANTA. We are currently running into persistent storage and CUDA installation issues.

This has been tested on GCP and the new workstation, and there is no longer a memory issue. It was due purely to the GCP memory capabilities of Beirut. We can now run a full day's worth of demand (20.1M trips) on either GCP or the new workstation.


Update to Cats 1.0.0

Is this blocked by https://github.com/47deg/sbt-org-policies/issues/655 or can cats be upgraded independently from sbt-org-policies?


callsigns  that start with "A" log with the "A" removed

example
callsign:   AB1BB is reported as B1BB
I noted this behavior on two different callsigns in in area.

It's possible this is a weird result from the decoder of weaker signals or a squelch setting on the RTL-SDR. At the moment, I'm not able to reproduce this in my test environment, but please let me know if you have any additional details or raw log output. thank you!

@LarsenDR If you're interested, there's a new release you could take for a spin https://github.com/cceremuga/ionosphere/releases/tag/v1.0.1
I have no positive confirmation that anything in the release will resolve the issue you experienced, but I also have not been able to replicate it on this release. If you're still experiencing it, please send along some relevant log entries (in ./logs folder) if possible. Thanks!


TODO Fix tests to catch missing dlls

Fix tests to catch missing dlls. Currently the executable must be pulling it from somewhere because they run when there is a missing dll.

Fixed in #39


Fix ld error: Undefined symbol eh_personality.

This can be fixed by telling the compiler not to mangle the function. Maybe something was changed so that you have to explicitly state to the compiler not the optimise the function away? I don't know. Point is, this builds for me now, whereas before cloning the repo fresh would throw up link errors.

Thanks! I don't know why this is suddenly required either, but I try to investigate this. For now, no_mangle seems like the best solution.


App crashes when credentials are set

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
8.0b1
Where did you get the app from?
Other
Android version
12
Device model
Redmi note 9 pro
Steps to reproduce

Import a settings file from K9
Do not set credentials yet
Then set missing password
Refresh emails (slide down)

Expected behavior
The sync starts to happens
Actual behavior
The app just closes itself, no message error, no crash report to send.
Logs
After restarting the app, everything works fine.
k9mail-logs.txt

The log contains information about an IMAP connection to an Exchange server. It looks like the app successfully establishes the connection and authenticates, but doesn't perform any useful operation. That's not the expected behavior. However, the log doesn't contain information about a crash.
It's possible that the app installation got corrupted. Try uninstalling and reinstalling the app. If you can still reproduce the issue, please provide more detailed steps on what you did exactly.

I tried it twice (uninstalling/reinstalling), the result is always the same.
Steps to reproduce

From K9 export the settings
Install Thunderbird 8.0b1
Select "Import parameters from file" (something like that, the app is in French)
Select the previously exported file
Keep "General parameters" &<EMAIL_ADDRESS>checked  and tap on the "Import" button
On the "Enter your passwords" click on the "Later" button
Ignore contacts authorization (or do, does not matter)
Inbox screen is now showing, empty. The left menu show my unified inbox and at the top my<EMAIL_ADDRESS>account
Slide down to refresh inbox: a notification appears
Click on notification to set incoming server parameters
Enter the password (only field missing)
Click on "Next" button

->  The thunderbird app is closed: no error message, no crash report, nothing.
Steps to then get the emails:

Open app drawer
Click on Thunderbird icon
Inbox is empty
Slide down: everything works fine

Thanks for the additional information :+1:
This kind of is the (developer) expected behavior. Tapping the notification starts a new task that ends with the server settings being successfully verified. Android then returns to the home screen and not to the app that was showing when you tapped the notification. It should be possible to change that. However, I don't think this is a high priority issue and it might take us quite some time until we get to it. If anyone wants to look into this, please do. Pull requests are very welcome.


Add zlib-ng and refactor gzip open functions.

I added zlib-ng. This is great, but now we also have three competing implementations for opening deflate compressed files:

zlib
ISA-L
zlib-ng

This means the choice for the "best" application becomes more situational. Also it is hard to correctly set all the initialization options.
I have therefore refactored the code. A list of preferred implementations is made. Then using a for loop and a try except the list is tried in order for an application that works. Application-specific options are set using functool.partial
This leads to more verbose code, but also in much simpler logic. Therefore this solution scales better. Since I expect crabz to be added soon, it is much easier to do that in this codebase.
Also this will work wonders for coverage as all the individual PipedCompression Readers and Writers are tested separately anyway and (almost) all the code in the opening functions is touched as there is only a single opening code line within a for loop.
It should be much more robust this way.

benchmarks again:
Before
Compressed at level 1 with 0 threads; filesize: 405313510, time: 3.0943868160247803 seconds
Compressed at level 2 with 0 threads; filesize: 404989250, time: 3.2503600120544434 seconds
Compressed at level 3 with 0 threads; filesize: 407253483, time: 8.559628248214722 seconds
Compressed at level 4 with 0 threads; filesize: 386930500, time: 22.203505277633667 seconds
Compressed at level 5 with 0 threads; filesize: 374207207, time: 39.5833375453949 seconds
Compressed at level 6 with 0 threads; filesize: 355347468, time: 98.56518363952637 seconds
Compressed at level 1 with 1 threads; filesize: 405313274, time: 3.134148597717285 seconds
Compressed at level 2 with 1 threads; filesize: 404989061, time: 3.2902400493621826 seconds
Compressed at level 3 with 1 threads; filesize: 407251397, time: 8.680283308029175 seconds
Compressed at level 4 with 1 threads; filesize: 387016236, time: 22.396305322647095 seconds
Compressed at level 5 with 1 threads; filesize: 374290891, time: 40.33376383781433 seconds
Compressed at level 6 with 1 threads; filesize: 355500797, time:<PHONE_NUMBER>3263245 seconds
Compressed at level 1 with 4 threads; filesize: 405313274, time: 3.1683871746063232 seconds
Compressed at level 2 with 4 threads; filesize: 404989061, time: 3.349888563156128 seconds
Compressed at level 3 with 4 threads; filesize: 407251397, time: 8.81507396697998 seconds
Compressed at level 4 with 4 threads; filesize: 387016236, time: 5.959070682525635 seconds
Compressed at level 5 with 4 threads; filesize: 374290891, time: 11.105888366699219 seconds
Compressed at level 6 with 4 threads; filesize: 355500797, time: 27.333863973617554 seconds

After:
Compressed at level 1 with 0 threads; filesize: 405313510, time: 3.118347406387329 seconds
Compressed at level 2 with 0 threads; filesize: 404989250, time: 3.301008939743042 seconds
Compressed at level 3 with 0 threads; filesize: 376289859, time: 20.477195024490356 seconds
Compressed at level 4 with 0 threads; filesize: 368802018, time: 17.948566198349 seconds
Compressed at level 5 with 0 threads; filesize: 359170597, time: 24.44700598716736 seconds
Compressed at level 6 with 0 threads; filesize: 347379910, time: 41.21350431442261 seconds
Compressed at level 1 with 1 threads; filesize: 405313274, time: 3.2212672233581543 seconds
Compressed at level 2 with 1 threads; filesize: 404989061, time: 3.3104476928710938 seconds
Compressed at level 3 with 1 threads; filesize: 376289859, time: 20.57276463508606 seconds
Compressed at level 4 with 1 threads; filesize: 368802018, time: 17.815391063690186 seconds
Compressed at level 5 with 1 threads; filesize: 359170597, time: 24.02311873435974 seconds
Compressed at level 6 with 1 threads; filesize: 347379910, time: 40.91991400718689 seconds
Compressed at level 1 with 4 threads; filesize: 405313274, time: 3.207160472869873 seconds
Compressed at level 2 with 4 threads; filesize: 404989061, time: 3.3800032138824463 seconds
Compressed at level 3 with 4 threads; filesize: 376289859, time: 20.435675144195557 seconds
Compressed at level 4 with 4 threads; filesize: 368802018, time: 17.669416427612305 seconds
Compressed at level 5 with 4 threads; filesize: 359170597, time: 23.864430904388428 seconds
Compressed at level 6 with 4 threads; filesize: 347379910, time: 40.691060066223145 seconds

I am much more happy with the compression gradient. Level 3 is now actually an improvement over level 2 (albeit much slower). Zlib-ng does some really nice work. Only threads are missing, but it looks crabz will provide these when ready.
I am also quite happy about how this PR turns out technically. It should be quite easy to add crabz after this and the logic has gotten a bit simpler.

Superseded by #135