[atom-elixir] Error: This socket has been ended by the other party

Hello.
Thanks for great plugin !
But I get error after some time working in Atom:
[atom-elixir] Error: This socket has been ended by the other party -  elixir-sense-client.js:41

Last commit: 730944b4279eab30a1967db66795d43b25500979

Hi, @JohnBat26.
I afraid I'll need some more information:

What OS? Env (dev or test)?
Any other messages in the console?
Is there a stacktrace somewhere?
Can you identify after which action it happens? Autocomplete? From which module? Go to definition? From what file?

The more information I have, the easier it is to reproduce and solve the problem.
Thanks!

Hi @msaraiva

atom-elixir: 0.2.2
OS: Gentoo Linux x86-64
Atom: 1.15.0
Electron: 1.3.13
Chrome  : 52.0.2743.82
Node    : 6.5.0

This sutiation reproduces periodically and incidentally. Especially reproduces after opening several projects in the same atom application. After restart of Atom plugin works good for some time.
And if I try use atom-elixir:goto-definition and it didn't work, then all plugin functional stop the work.
This is log: Atom-elixir issue log
This is my list atom packages: My atom packages

@msaraiva Todat I get this problem again.
I install last git version of atom-elixir (commit: 4534a1c33fb5f2134e59d30eaf91f279e142872c) and just open clear phoenix project.
Atom log

@JohnBat26, please try v0.2.3 and let me know how it goes. I'll fix on master during the weekend. BTW, what file from the new phoenix project have you opened and what was the first action you've tried to run before the error?
Thanks again!

@msaraiva I've installed v.0.2.3 and it begin to work better but when I add two phoenix project into Atom I get error and plugin stop moving between modules with help Alt+Down.
My code: phoenix_commerce.ex
Error: Atom log for atom-elixir plugin
Can I add Elixir source code and use alt+down functional for Elixir modules and functions?

@msaraiva hello. Add new log with errors: Atom-elixir can't controller
Example code into routes.ex:
  scope "/", Pxblog do
    pipe_through :browser # Use the default browser stack

    get "/", PageController, :index
    resources "/posts", PostController
  end

PostController exist, but plugin doesn't move to it with Alt+Down

@msaraiva and again:


[OpenCL] Registers AvgPool and AvgPoolGrad (#105)

Can one of the admins verify this patch?

@benoitsteiner any cycles to take a look?

@benoitsteiner ping

Pong

@benoitsteiner any cycles to take a look?

Nagging Assignee: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @benoitsteiner: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @benoitsteiner: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @benoitsteiner: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Reviewer @benoitsteiner: It has been 14 days with no activity and the awaiting review label was assigned. Can you please take a look?

Nagging Reviewer @benoitsteiner: It has been 16 days with no activity and the awaiting review label was assigned. Can you please take a look?

Nagging Reviewer @benoitsteiner: It has been 150 days with no activity and the awaiting review label was assigned. Can you please take a look?

Nagging Reviewer @benoitsteiner: It has been 165 days with no activity and the awaiting review label was assigned. Can you please take a look?

Nagging Reviewer @benoitsteiner: It has been 180 days with no activity and the awaiting review label was assigned. Can you please take a look?

Nagging Reviewer @benoitsteiner: It has been 195 days with no activity and the awaiting review label was assigned. Can you please take a look?

Nagging Reviewer @benoitsteiner: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 210 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @benoitsteiner: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 225 days with no activity and the awaiting review label has been applied.

I believe this PR is outdated.
@Rbiessy will replace it with smaller one when it is ready.


Allow lorri watch --once to be executed from a sub-directory

Feature description
I have often tried to execute lorri watch --once from a sub-directory and realized that I need to run it from project root directory.
Possible implementation
We can add env = "IN_LORRI_SHELL" for the command line option --shell-file and change locate_file::in_cwd to handle the absolute path to shell.nix file.
I am happy to work on a PR if you are OK with this direction.

lorri doesn’t have a notion of a project, checking for a shell.nix in the current directory was more of a convenience.
IN_LORRI_SHELL would only be set if you are already in a lorri shell, no?

I have created https://github.com/target/lorri/pull/410 to illustrate the approach. I have found that IN_LORRI_SHELL is also set after $(lorri direnv) is evaluated in .envrc

Hi @surajbarkale! I think that understanding your use case better helps us evaluate this issue and your PR. What is that you are trying to achieve by running lorri watch --once inside a lorri shell?

Here is my workflow:

Run lorri init within a monorepo ~\Documents\monoproj
Open VS Code to edit stuff within ~\Documents\monoproj
Change to a project in a subdirectory ~\Documents\monoproj\nodejs\proj
At some point I realize that extra setup is needed. So edit ~\Documents\monoproj\shell.nix
Run lorri watch --once in terminal. To get error "ERRO shell.nix does not exist"
Run cd ~\Documents\monoproj; lorri watch --once; cd - to wait for evaluation.

Since I am working on different projects, I run through this at least twice a week. Note that I am not using lorri shell.

This sounds like a perfect use-case for lorri daemon, any reason why you
don’t want to use that? lorri watch --once is more of a debugging tool,
we want the daemon to be good enough to be usable in 95% percent of
use-cases.
On Thu, May 28, 2020 at 2:07 AM Suraj Barkale<EMAIL_ADDRESS>wrote:

Here is my workflow:

Run lorri init within a monorepo ~\Documents\monoproj
Open VS Code to edit stuff within ~\Documents\monoproj
Change to a project in a subdirectory
~\Documents\monoproj\nodejs\proj
At some point I realize that extra setup is needed. So edit
~\Documents\monoproj\shell.nix
Run lorri watch --once in terminal. To get error "ERRO shell.nix
does not exist"
Run cd ~\Documents\monoproj; lorri watch --once; cd - to wait for
evaluation.

Since I am working on different projects, I run through this at least
twice a week. Note that I am not using lorri shell.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/target/lorri/issues/409#issuecomment-635009566, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYB5ZVLJR6Q75XIMAQJCETRTWTKJANCNFSM4NJ77HQA
.

I am using the daemon on macOS with launchctl. However, I just realized that it is unable to access files in ~/Documents folder. So I had to resort to lorri watch --once. I shall update here after diagnosing the daemon issues.

What happens if you run the daemon in a terminal? I assume launchctl
sandboxes it too strongly by default.
On Thu, May 28, 2020 at 12:58 PM Suraj Barkale<EMAIL_ADDRESS>wrote:

I am using the daemon on macOS with launchctl. However, I just realized
that it is unable to access files in ~/Documents folder. So I had to
resort to lorri watch --once. I shall update here after diagnosing the
daemon issues.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/target/lorri/issues/409#issuecomment-635269848, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYB5ZX2LPDSHVKVDZVD42DRTY7VJANCNFSM4NJ77HQA
.

I was able to get the permissions under control by granting /bin/zsh Full Disk Access in macOS. I got into the habit of using lorri watch --once as there is no feedback from the daemon about availability of shell. If everything in shell.nix is already in store then daemon takes only a couple of seconds on my machine. However, if some derivation is getting built then there is no indication to user when the environment is ready. I have to hit enter and hope for a new evaluation from direnv. Since I routinely work on multiple projects, I may be hitting this issue often.
To summarize, I have had following issues with daemon:

Lack of feedback from daemon when shell.nix evaluation is in progress. This
is also an issue without the daemon since there is no indication that
shell.nix needs to be re-evaluated. For me lorri watch --once guaranties
that I am using the right environment.
The macOS peculiarities that make daemon management painful. This is no fault
of lorri.

I got into the habit of using lorri watch --once as there is no feedback from the daemon about availability of shell.

What kind of feedback would you prefer to get from the daemon if you could dream about your perfect setup with lorri?


Fix commons to use new relpath syntax + add example for input

relpath syntax (see tjd/blah)
split the content over two page with the first one being "basic" second one being "Interacting with code" or something where you discuss the different ways.

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/1142
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.1 -m "<description of version>" 8a499dcdbed13506b2d08d39eb743df4862f1262
git push origin v0.2.1


Display top-level stop reason when StoppedEvent specifies no threadId

In Go sometimes we do not have a user thread id to specify in the stopped event. But if we issue a stopped event with a missing thread id, vscode will not show our stop reason at all.
{"seq":0,"type":"event","event":"stopped","body":{"reason":"pause","allThreadsStopped":true}}
Instead it would be great if it the stop reason was either applied to all threads or even better displayed at the top level in line with CALL STACK like when there is only a single thread.

Ok, so the request is to introduce a rule: if a stopped event has not threadId then the reason should be shown top level or at the session level if there are multiple sessions.
This in general makes sense to me. Let's see what @weinand thinks
Also if we agree to change this I would be open to a PR that fixes this.
Here's a code pointer https://github.com/microsoft/vscode/blob/main/src/vs/workbench/contrib/debug/browser/callStackView.ts#L166

Since the threadId property of the stopped event is optional, we should not ignore showing the reason in that case.
I like @polinasok's proposal.

Let's assign to June to investigate.
Adding help wanted. If nobody jumps on this I can look into it end of June

Thanks @suzmue for tackling this via a PR 👏


NavigationView can't be used without Content Area

Describe the bug
In a scenario where the NavigationView wants to be used more for navigation only (for instance like a file or layer browsing in folders) it is difficult to customize its behavior and NOT use the built-in content area. Think of scenarios like VS Code as well where the side bar can be collapsed.
With the current template, it assumes there will be a content area and the control cannot be forced to act as a navigation display only vs. driving navigation of its content area (which it doesn't do by default anyway without app logic).
It should be possible to get the content area to be collapsed so that more complex arrangements can be composited with the control and driven outside of its content area.
Steps to reproduce the bug
  <Grid x:Name="RootGrid">
    <!-- Just to separate our two examples -->
    <Grid.ColumnDefinitions>
      <ColumnDefinition Width="Auto"/>
      <ColumnDefinition/>
    </Grid.ColumnDefinitions>

    <muxc:NavigationView x:Name="nvSample" HorizontalAlignment="Left"
                        PaneDisplayMode="Left">
      <muxc:NavigationView.MenuItems>
          <muxc:NavigationViewItem Icon="Play" Content="Menu Item1" Tag="SamplePage1" />
          <muxc:NavigationViewItem Icon="Save" Content="Menu Item2" Tag="SamplePage2" />
          <muxc:NavigationViewItem Icon="Refresh" Content="Menu Item3" Tag="SamplePage3" />
          <muxc:NavigationViewItem Icon="Download" Content="Menu Item4" Tag="SamplePage4" />
      </muxc:NavigationView.MenuItems>
    </muxc:NavigationView>

    <Border Grid.Column="1" Background="Red"/>
  </Grid>

https://github.com/microsoft/microsoft-ui-xaml/blob/e4c5d3443caa0242be0953010dd5ab3ddb4c2925/dev/NavigationView/NavigationView.xaml#L648-L651
I believe it is this code in the XAML Template which forces the Content pane to be visible even when there is no content in the panel.
Expected behavior
Able to use the NavigationView as a Pane only without a forced content area. Thus it can then be used to control content from outside of the NavigationView itself.
For instance imagine if the Navigation view is only showing objects within a canvas in an art tool. No navigation or pages may be involved, instead the behavior may be to select/highlight the selected item in the NavigationView in the canvas on the right. Mind you this canvas may be in the Content Area of the Navigation View, but if you want to manipulate the size of the open pane in relation to the content area, this becomes challenging.
Screenshots

NuGet package version
Microsoft.UI.Xaml 2.7.0
Windows app type

[X] UWP
[ ] Win32

Device form factor
Desktop
Windows version
May 2021 Update (19043)
Additional context
No response

Actually maybe this is from SplitView itself? I'm not sure. Messing around with the Visual Tree in debug mode made me find this Grid to be the issue, but not sure where that's defined:

Bumping, based on https://github.com/microsoft/microsoft-ui-xaml/discussions/8638


Various pipelines evaluation errors during composing

The following errors occurs in the log for classification tasl:

This problem should be sovled and covered by tests.
#785 can be also relevent here.

Также много вот таких:


Consider adding recommended packages

Currently Weblate only covers base packages, we could consider adding recommended packages.
I guess the logistics are more difficult as they have different maintainers and the source is different places. We could start with the ones maintained on the R Project SVN (https://svn.r-project.org/R-packages/trunk/) and/or packages whose maintainers are at the sprint.

Definitely.  They have "always" received translations and translation updates in the past.

Summarizing discussion with @daroczig and @lawremi today:
There are three basic approaches here:

Put each Recommended package in its own project
Make one new project for all the Recommended packages
Put all the Recommended packages inside the existing project as new components

I think there are two drawbacks to 1 and 2:

discoverability -- it's not clear how much attenuation we'd expect if translators have to navigate around the site to find missing translations for Recommended packages, vs. them being alongside the base packages. This is less a problem for (2) because there's only one new place to "discover" incomplete translations
maintenance -- there is an added burden of delegating ownership/admin rights over new projects, vs. sharing the ownership structure in a single project

There are two drawbacks to 3 as well:

Overhead for patch generation. As confirmed with Michael L., canonical maintenance of the .po files for the Recommended packages is up to the respective maintainers. That means we need to send each maintainer a patch (patches) for the specific Recommended package(s) they maintain (last update):

Brian Ripley: KernSmooth (2023-07-10), MASS (2023-05-04), boot (2022-11-22), class (2023-05-03), nnet (2023-05-03), spatial (2023-07-20)
Martin Maechler: Matrix (2023-08-14), cluster (2022-08-22)
~CRAN team: RCurl, RJSONIO, XML~
~Miguel Manese: SQLiteDF~
~Thomas Lumley: adapt, biglm~
~Martyn Plummer: coda~
R Core Team: foreign (2022-12-06), nlme (2023-08-09)
Deepayan Sarkar: lattice (2023-04-05), ~rcompgen~
Simon Wood: mgcv (2023-07-11)
Terry Therneau: survival (2023-08-14)
Luke Tierney: codetools (2023-02-01)
Beth Atkinson: rpart (2022-10-21)

bold packages are not present in Heather's SVN link in https://github.com/r-devel/translations/issues/21#issue-1816143240. Canonical source of what's "Recommended" taken fromhttps://github.com/r-devel/r-svn/blob/5ec122aee4f616d6cc6bcd6479d1edcc45a7c5ea/share/make/vars.mk#L12.

Possible confusion of associating the components too closely together with the main R devel translation components, overly blurring the line of distinction between the default & Recommended packages.

On balance, I think 3 is the best choice. I will add the components tomorrow & work out the script for generating multiple patches.

I would be more in favour of Option 2.
Response to drawbacks:

Discoverability issue can be solved with documentation and mentoring - easier with just one project for all Recommended packages.
Maintenance is a bit of an issue, but again easier with just one project for all Recommended packages.

More pros of Option 2:

Treating them as a separate bundle mirrors how they are treated elsewhere; e.g. we can build R with/without the recommended packages.
Adding/removing Recommended packages would not change the places translators need to look (also applies to Option 3)
Recommended packages may potentially operate on a different timeline to the rest of base R, e.g. update of POT files, deadline for updates.
I think the perception of what is maintained by R Core is important and we should avoid confusion. The Recommended packages do not need to be maintained by a member of R Core (and are not, in some cases).
We would want translators to prioritise base packages first; separating the Recommended packages helps with this.

If you still think Option 3 is better (easier to maintain), it would be good if Recommended packages could be clearly marked in some way and perhaps ordered together when looking at the list of components (perhaps after everything maintained by R Core).

Sounds good, thanks Heather! I'm swayed -- we'll do a project for recommended packages.

Update at lunch: finished all packages maintained on the main SVN repo (except for lattice, which has an error).

Update from Deepayan: lattice is not maintained on that SVN repo, but GitHub:
https://github.com/deepayan/lattice
The other packages' sources may also be outdated there if the DESCRIPTION URL does not match.

The following packages are linked to the github cran mirror as a source since I'm not aware of a public source control for them:

MASS
class
nnet
spatial
Matrix*

Actually, Matrix is on R Forge, but Weblate doesn't support the SCM system.

OK, recommended packages are available for translation:
https://translate.rx.studio/projects/the-r-project-recommended-packages/
One potential avenue for improvement: {lattice} and {rpart} are maintained on GitHub; we might consider setting up a workflow similar to that done for the Mac GUI files whereby we set up the push configuration to send patches directly as PRs to the upstream maintainers.


[WIP] CRD backed identity allocation

This change is

@tgraf this one isn't dead or?

@raybejjani has taken over the work in a separate PR. It is still targeted for 1.6


Dev: Open workspace admin from deep link shows skeleton forever if user isn't a member of that workspace.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Login with account A.
Create a new workspace, copy the workspace admin url and send to account B
From account B, click on that workspace admin deep link.
Notice that App shows skeleton forever.

Expected Result:
App should show Not Found page.
Actual Result:
App shows skeleton forever.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: dev
Reproducible in staging?: needs reproduction
Reproducible in production?: needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/7e9db3ae-e7de-4134-a745-1a53774c7b06
Expensify/Expensify Issue URL:
Issue reported by: @hungvu193
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684322982976969
View all open jobs on GitHub

@slafortune Seems it is good to close. Contributor couldn't reproduce this bug as per this comment.


[Icon Request] Support for Dylan-lang

[x] I'm sure this issue is not a duplicate?
[x] I want to create an icon request:
- Type: extension
- Icon Name: dylanlang
- Sample original Icon:
- Extensions: .dylan, .intr

Where did you see these extension? I've never seen them. I didn't know that sooo much languages exists.

I didn't know either. My head hurts. I'm just browsing the language support that exists for vscode and adding those we are missing.
To answer your question: https://github.com/dylan-lang/vscode-dylan/blob/master/package.json#L39

Thanks to you. I couldn't do that. 😉


Unable to use IFormFile with ApiController in 2.1

From @mitchellj on Thursday, 09 August 2018 20:06:10
When we are trying to use IFormFile it works perfectly when we are not using [ApiController], as soon as we introduce ApiController one of two things happens

If we do not prefix with [FromForm] we get a Serialization exception which generates a Bad Request response.
If we do prefix FromForm to the IFormFile then it becomes null

In order to get IFormFile to work we need to remove ApiController completely in which case the IFormFile becomes completely propagated correctly.
Copied from original issue: aspnet/Home#3403

Thanks for contacting us, @mitchellj.
This is because we do not special case the IFormFile type and treat it as a complex type. ApiController conventions for complex types are that by default they're treated as FromBody.
@pranavkm, seems this is a good candidate to be special-cased.

Do you have your compatibility version set to 2.1? See https://docs.microsoft.com/en-us/aspnet/core/migration/20_21?view=aspnetcore-2.1#changes-to-startup
We had an issue specifically with collection of IFormFile - https://github.com/aspnet/Mvc/issues/7770 that was fixed in 2.2

I ran into the same problem. And strangely, when not using any controller parameter and trying to access or iterate Request.Form.Files the thread would just die without ever responding to the browser or even entering any exception blocks that are around the code. Feels kind of weird. My ASP.NET Core version was 2.1.2.
Until this is solved, I was able to help myself with a workaround by explicitly stating the name of the form parameter using the [FromForm] attribute like this:
public async Task<IActionResult> UploadLogo([FromForm(Name = "file")] IFormFile file)
{
     ...
}

After that for some reason the binding worked. I discovered this behavior by accident after having a hard time getting the file upload from an angular 6 application to work.  Hope it helps someone else. The link to the corresponding stackoverflow answer is: https://stackoverflow.com/a/52017637/8007572

@Schmaga did the compat switch work for you?

Sorry I was out of the country for a while, I will be back in a couple of days and try the compat switches and report back. Compatibility was NOT set previously so that is most likely the issue will confirm though.

@mitchellj feel free to reopen this issue if you still see it after changing the compat version.

I am also still on vacation. Will check as soon as I am back home.
Am 28.08.2018 23:26 schrieb Pranav K<EMAIL_ADDRESS>@Schmagahttps://github.com/Schmaga did the compat switch work for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/aspnet/Mvc/issues/8311#issuecomment-416746295, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AG6j0M1Zf4DviMQBizOKeFgZyC54Nzssks5uVbWOgaJpZM4WIau4.

@pranavkm I returned from vacation and checked with the compat switch set to 2.1.
It now works, but I also have to remove the [FromForm] Attribute completely from the controller IFormFrile parameter, otherwise it is still "null".
I think it might make sense to better document what exactly the compat switch affects, because I would not have thought it would produce such strange behavior as described in my above post.

It now works, but I also have to remove the [FromForm] Attribute completely from the controller's IFormFile parameter, otherwise it is still null.

That isn't intended. Do you have a repro app for this?

Not yet, but I could extract it from our project for you. What format is best? Will it be enough to paste the relevant snippets here or do you need a zip file with a project or something?
This is my first .NET OSS issue, so sorry if the answer might be obvious. And I didn't find anything specific about providing example code in the contribution guidelines :)

A sample repo on github works really well to share code. If that's difficult, any of your suggestions work fine.

Moved to preview3 for now.

Sorry back now, I can confirm as @pranavkm has found as well that

Decorating the controller with [ApiController] and the IFormFile with [FromForm] gives us a null IFormFile.
Decorating the controller with [ApiController] and not decorating the IFormFile parameter binds the IFormFile correctly

Thanks @pranavkm. Will provide a repo then, hopefully in the next few days.

Looks like yet another case that we need to special case in https://github.com/aspnet/Mvc/blob/release/2.2/src/Microsoft.AspNetCore.Mvc.Core/Internal/ApiBehaviorApplicationModelProvider.cs#L215-L233. FormFileModelBinder requires the model name to match which the provider messes with.
For 2.1, I'd recommend not specifying the attribute or if you do specify the attribute, also specify the name .e.g [FromForm("file")].

@pranavkm here is the link to the repositry: https://github.com/Schmaga/aspnet_issue_8311
You can play around with removing the compat switch and/or the attribute a bit.
A bit late, but I hope it still helps.

I have made a repo to reproduce the problem and thanks to @dougbu we have found the solution. Let take a lool there: https://github.com/ranouf/TestMultipleUpload


Use ssl for db connection

Add the rds root certificate. This is a public certificate, available from aws and isn't secret. It's needed here so the lambda can access it when connecting.
Set ssl params on the flyway url

I think if we put it in there we'd have to clone the project in the jenkins build and then copy the file but then I was thinking about doing that and it's better I think to have Jenkins wget the file from AWS into the resources directory and then build it from there. This means we don't need to keep the certificate in the repo. It's not a security risk but it is a bit rubbish.


[TEST][MINOR] remove redundant EliminateSubqueryAliases in test code

What changes were proposed in this pull request?
The analyze method in implicit class DslLogicalPlan already includes EliminateSubqueryAliases. So there's no need to call EliminateSubqueryAliases again after calling analyze in some test code.
How was this patch tested?
Existing tests.

Test build #85542 has started for PR 20122 at commit 79daa55.

Test build #85542 has finished for PR 20122 at commit 79daa55.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/85542/
Test FAILed.

retest this please

Test build #85544 has started for PR 20122 at commit 79daa55.

Test build #85544 has finished for PR 20122 at commit 79daa55.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Thanks! Merged to master.


Add dnd-character exercise

@glennj @axtens I was wondering how to best write the "check if a value is between a certain range" tests. Especially for the character generation, which generates a map (I haven't used an object here as we don't really update/do anything with the character).

: ability-valid? \ n -- t
    3 18 n:between
;

"random ability is within range"
     ( ability
       ability-valid? )
     true?

"random character is valid"
     ( character >r
        r@ "strength" m:@     ability-valid?
        r@ "dexterity" m:@    ability-valid? and
        r@ "constitution" m:@ ability-valid? and
        r@ "intelligence" m:@ ability-valid? and
        r@ "wisdom" m:@       ability-valid? and
        r@ "charisma" m:@     ability-valid? and
        r@ "constitution" m:@ modifier 10 n:+ r> "hitpoints" m:@ n:= and
     )
     true?

?


Fix health status effects for health cross customization

Fixed in https://github.com/rbjaxter/budhud/commit/e1bd7c49bb02ceee4dc03f005a07ad2f1b10eb0b.


#32 added cursor and background-color property to the button of dark mode

The solution of the #32  The dark mode button doesn't has the background color

@vaishnav-sh done. It wasn't my that changes, that happened because when i forked and did the PR it was an older version of the file. It's all OK now. Thanks!


[core] Adjust create partition interface

Purpose

Adjust https://github.com/apache/paimon/pull/4323

Tests

API and Format

Documentation

+1 look good to me！thanks @JingsongLi


Fontmake assumes there is no mark feature in UFO’s features.fea

When fontmaking TTF from UFO instances, I get the following report. I think it is because fontmake simply adds mark feature to the other features and does not check if mark feature is already there.
  File "/usr/local/bin/fontmake", line 11, in <module>
    load_entry_point('fontmake==1.2.5', 'console_scripts', 'fontmake')()
  File "/usr/local/lib/python2.7/site-packages/fontmake/__main__.py", line 195, in main
    ufo_paths, is_instance=args.pop('masters_as_instances'), **args)
  File "/usr/local/lib/python2.7/site-packages/fontmake/font_project.py", line 481, in run_from_ufos
    **kwargs)
  File "/usr/local/lib/python2.7/site-packages/fontmake/font_project.py", line 193, in build_ttfs
    self.save_otfs(ufos, ttf=True, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/fontTools/misc/loggingTools.py", line 372, in wrapper
    return func(*args, **kwds)
  File "/usr/local/lib/python2.7/site-packages/fontmake/font_project.py", line 293, in save_otfs
    font = compileTTF(ufo, convertCubics=False, **compiler_options)
  File "/usr/local/lib/python2.7/site-packages/ufo2ft/__init__.py", line 67, in compileTTF
    featureCompiler.compile()
  File "/usr/local/lib/python2.7/site-packages/ufo2ft/featureCompiler.py", line 40, in compile
    self.setupFile_featureTables()
  File "/usr/local/lib/python2.7/site-packages/ufo2ft/featureCompiler.py", line 141, in setupFile_featureTables
    filename=feapath)
  File "/usr/local/lib/python2.7/site-packages/fontTools/feaLib/builder.py", line 25, in addOpenTypeFeaturesFromString
    addOpenTypeFeatures(font, featurefile)
  File "/usr/local/lib/python2.7/site-packages/fontTools/feaLib/builder.py", line 16, in addOpenTypeFeatures
    builder.build()
  File "/usr/local/lib/python2.7/site-packages/fontTools/feaLib/builder.py", line 78, in build
    self.parseTree = Parser(self.file, self.glyphMap).parse()
  File "/usr/local/lib/python2.7/site-packages/fontTools/feaLib/parser.py", line 53, in parse
    statements.append(self.parse_markClass_())
  File "/usr/local/lib/python2.7/site-packages/fontTools/feaLib/parser.py", line 507, in parse_markClass_
    markClass.addDefinition(mcdef)
  File "/usr/local/lib/python2.7/site-packages/fontTools/feaLib/ast.py", line 336, in addDefinition
    definition.location)
fontTools.feaLib.error.FeatureLibError: /Users/davidbrezina/Typefaces (retail)/Avory/production/Avory/instance_ufo/Avory-Regular.ufo/features.fea:5464:1: Glyph apostrophemodifier already defined at /Users/davidbrezina/Typefaces (retail)/Avory/production/Avory/instance_ufo/Avory-Regular.ufo/features.fea:3934:8

The problem is in ufo2ft MarkFeatureWriter, which writes not only mark but also mkmk features, based on the presence of anchors in the UFO, and also based on whether the features are not already there in the features.fea or any included files.
I think you have generated your own mark feature with other tools, but did not also add a mkmk feature, which is fine. Now, the MarkFeatureWriter sees you added a mark feature so it doesn't write that; however it sees some of the mark glyphs have mark-to-mark anchors and thus automatically generates a mkmk feature; but the mark classes ufo2ft creates to make its mkmk feature enter in conflict with the existing mark classes you have already defined for your mark feature, hence the feaLib error above.
Basically, the way things work at the moment, either you don't define neither mark nor mkmk manually and let both be generated by the toolchain, or you define both of them yourself. Only having a mark feature, but also some glyphs containing e.g. both "_top" and "top", will make so that an mkmk feature will be created, which will likely clash with the existing mark classes,  (they usually overlap and are shared by the two features).
I can look at this early next week. One workaround admittedly hackish you have, would be to add an empty feature mkmk {}; statement in your features so that ufo2ft will not attempt to write one (as you remember, feaLib ignores those, but makeotf will crash with syntax error).

Actually the problem arises also if one does not have any mark-to-mark anchors in the font; it is enough to just have one mark (or mkmk) feature already defined; the markFeatureWriter will then attempt to create the other missing feature; but the problem is it will unconditionally write its own conflicting markClass definitions, even if at the end the feature block itself turns out to be empty and therefore skipped altogether.
I think it would be better if we skip the whole markFeatureWriter if any of mark or mkmk feature are already defined, rather than treating them separately.

Ha, funnily, I used ufo2ft to generate mark and mkmk so I could use it for makeotf, but it correctly did not write any mkmk because there were no anchors for that. Bit silly that it does not consider its own output as “complete”. Adding a few anchors to have some mkmk fixed it. Thanks.

I think a more robust fix is for the feature writer to check the existing mark classes and make sure the new ones are unique. ufo2ft already parses the features using feaLib so it is shouldn’t add too much overhead to do such checks.

I think a more robust fix is for the feature writer to check the existing mark classes and make sure the new ones are unique.

You're right, but we can do that later. The current functionality of trying to write mark and mkmk independently from each other is broken anyway, so we may well just accept the fact that the current MarkFeatureWriter can either write both mark+mkmk or none if any of the two is already present.


[Regression] "no implicit conversion of nil into String" in match during cert install after updating to 2.57

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
After updating to version 2.57 the match step now fails with the error no implicit conversion of nil into String when trying to install certificates. Running the same command in 2.56 succeeds.
From the debug output it looks to be choking when installing the Apple Worldwide Developer Relations Certification Authority.
Complete output when running fastlane, including the stack trace and command used

You can use: --capture_output as the last commandline argument to get that collected for you

Captured Output
Command Used: refreshCertificates --env DEV
Output/Log

DEBUG [2017-09-18 13:22:54.06]: Checking if there are any plugins that should be loaded...
INFO [2017-09-18 13:22:54.18]: -------------------------------------------------
INFO [2017-09-18 13:22:54.18]: --- Step: Verifying required fastlane version ---
INFO [2017-09-18 13:22:54.18]: -------------------------------------------------
INFO [2017-09-18 13:22:54.18]: Your fastlane version 2.57.0 matches the minimum requirement of 2.56.0  ✅
INFO [2017-09-18 13:22:54.19]: ------------------------------
INFO [2017-09-18 13:22:54.19]: --- Step: default_platform ---
INFO [2017-09-18 13:22:54.19]: ------------------------------
INFO [2017-09-18 13:22:54.19]: Loading from './fastlane/.env.DEV'
INFO [2017-09-18 13:22:54.19]: Driving the lane 'ios refreshCertificates' 🚀
INFO [2017-09-18 13:22:54.20]: -------------------
INFO [2017-09-18 13:22:54.20]: --- Step: match ---
INFO [2017-09-18 13:22:54.20]: -------------------
DEBUG [2017-09-18 13:22:54.21]: Taking value for 'git_url' from environment variable 'MATCH_GIT_URL'
DEBUG [2017-09-18 13:22:54.21]: Taking value for 'git_branch' from environment variable 'MATCH_GIT_BRANCH'
DEBUG [2017-09-18 13:22:54.21]: Taking value for 'type' from environment variable 'MATCH_TYPE'
DEBUG [2017-09-18 13:22:54.21]: Taking value for 'app_identifier' from environment variable 'MATCH_APP_IDENTIFIER'
DEBUG [2017-09-18 13:22:54.21]: Taking value for 'username' from environment variable 'MATCH_USERNAME'
DEBUG [2017-09-18 13:22:54.21]: Taking value for 'readonly' from environment variable 'MATCH_READONLY'
DEBUG [2017-09-18 13:22:54.21]: Taking value for 'team_id' from environment variable 'FASTLANE_TEAM_ID'
DEBUG [2017-09-18 13:22:54.21]: Taking value for 'platform' from environment variable 'MATCH_PLATFORM'

+-----------------------+--------------------------------------+
|                   Summary for match 2.57.0                   |
+-----------------------+--------------------------------------+
| git_url               | git@github.com:CompanyName/ios-code-si  |
|                       | gning.git                            |
| git_branch            | team1                                |
| type                  | enterprise                           |
| app_identifier        | com.team1.appName,com.team1.appName.          |
|                       | keyboard                             |
| username              |<EMAIL_ADDRESS>                 |
| keychain_name         | login.keychain                       |
| readonly              | false                                |
| team_id               | <MyTeamId>                           |
| verbose               | false                                |
| force                 | false                                |
| skip_confirmation     | false                                |
| shallow_clone         | false                                |
| clone_branch_directly | false                                |
| force_for_new_devices | false                                |
| skip_docs             | false                                |
| platform              | ios                                  |
+-----------------------+--------------------------------------+

INFO [2017-09-18 13:22:54.22]: Cloning remote git repo...
INFO [2017-09-18 13:22:54.22]: If cloning the repo takes too long, you can use the `clone_branch_directly` option in match.
INFO [2017-09-18 13:22:54.22]: $ GIT_TERMINAL_PROMPT=0 git clone 'git@github.com:team1/ios-code-signing.git' '/var/folders/7g/qgyrmc1x0_g313fqrlx9jvbc0000gn/T/d20170918-83722-1pgtozg'
INFO [2017-09-18 13:22:54.24]: ▸ Cloning into '/var/folders/7g/qgyrmc1x0_g313fqrlx9jvbc0000gn/T/d20170918-83722-1pgtozg'...
INFO [2017-09-18 13:22:55.14]: ▸ remote: Counting objects: 87, done.
INFO [2017-09-18 13:22:55.26]: ▸ remote: Compressing objects: 100% (41/41), done.
INFO [2017-09-18 13:22:56.02]: ▸ remote: Total 87 (delta 7), reused 55 (delta 5), pack-reused 30
INFO [2017-09-18 13:22:56.02]: ▸ Receiving objects: 100% (87/87), 218.73 KiB | 293.00 KiB/s, done.
INFO [2017-09-18 13:22:56.02]: ▸ Resolving deltas: 100% (7/7), done.
INFO [2017-09-18 13:22:56.07]: $ git branch --list origin/team1 --no-color -r
INFO [2017-09-18 13:22:56.08]: ▸ origin/team1
INFO [2017-09-18 13:22:56.08]: Checking out branch team1...
INFO [2017-09-18 13:22:56.08]: $ git checkout team1
INFO [2017-09-18 13:22:56.09]: ▸ Branch team1 set up to track remote branch team1 from origin.
INFO [2017-09-18 13:22:56.09]: ▸ Switched to a new branch 'team1'
INFO [2017-09-18 13:22:56.14]: 🔓  Decrypted 'H6K9EUZN9S.cer'
INFO [2017-09-18 13:22:56.18]: 🔓  Decrypted 'H6K9EUZN9S.p12'
INFO [2017-09-18 13:22:56.23]: 🔓  Decrypted 'InHouse_com.team1.appName.mobileprovision'
INFO [2017-09-18 13:22:56.28]: 🔓  Decrypted 'InHouse_com.team1.appName.keyboard.mobileprovision'
INFO [2017-09-18 13:22:56.38]: 🔓  Successfully decrypted certificates repo
INFO [2017-09-18 13:22:56.42]: Verifying that the certificate and profile are still valid on the Dev Portal...
INFO [2017-09-18 13:22:57.84]: Installing certificate...
INFO [2017-09-18 13:22:57.84]: $ security list-keychains -d user
INFO [2017-09-18 13:22:57.86]: ▸     "/keychainDir/Library/Keychains/login.keychain-db"
INFO [2017-09-18 13:22:57.86]: $ security find-certificate -c 'Apple Worldwide Developer Relations Certification Authority' /keychainDir/Library/Keychains/login.keychain-db
INFO [2017-09-18 13:22:57.89]: ▸ keychain: "/keychainDir/Library/Keychains/login.keychain-db"
INFO [2017-09-18 13:22:57.89]: ▸ version: 512
INFO [2017-09-18 13:22:57.89]: ▸ class: 0x80001000
INFO [2017-09-18 13:22:57.89]: ▸ attributes:
INFO [2017-09-18 13:22:57.89]: ▸     "alis"<blob>="Apple Worldwide Developer Relations Certification Authority"
INFO [2017-09-18 13:22:57.89]: ▸     "cenc"<uint32>=0x00000003
INFO [2017-09-18 13:22:57.89]: ▸     "ctyp"<uint32>=0x00000001
INFO [2017-09-18 13:22:57.89]: ▸     "hpky"<blob>=0x88271709A9B618608BECEBBAF64759C55254A3B7  "\210'\027\011\251\266\030`\213\354\353\272\366GY\305RT\243\267"
INFO [2017-09-18 13:22:57.89]: ▸     "issu"<blob>=0x3062310B300906035504061302555331133011060355040A130A4150504C4520494E432E31263024060355040B131D4150504C452043455254494649434154494F4E20415554484F52495459311630140603550403130D4150504C4520524F4F54204341  "0b1\0130\011\006\003U\004\006\023\002US1\0230\021\006\003U\004\012\023\012APPLE INC.1&0$\006\003U\004\013\023\035APPLE CERTIFICATION AUTHORITY1\0260\024\006\003U\004\003\023\015APPLE ROOT CA"
INFO [2017-09-18 13:22:57.89]: ▸     "labl"<blob>="Apple Worldwide Developer Relations Certification Authority"
INFO [2017-09-18 13:22:57.89]: ▸     "skid"<blob>=0x88271709A9B618608BECEBBAF64759C55254A3B7  "\210'\027\011\251\266\030`\213\354\353\272\366GY\305RT\243\267"
INFO [2017-09-18 13:22:57.89]: ▸     "snbr"<blob>=0x01DEBCC4396DA010  "\001\336\274\3049m\240\020"
INFO [2017-09-18 13:22:57.89]: ▸     "subj"<blob>=0x308196310B300906035504061302555331133011060355040A0C0A4170706C6520496E632E312C302A060355040B0C234170706C6520576F726C647769646520446576656C6F7065722052656C6174696F6E733144304206035504030C3B4170706C6520576F726C647769646520446576656C6F7065722052656C6174696F6E732043657274696669636174696F6E20417574686F72697479  "0\201\2261\0130\011\006\003U\004\006\023\002US1\0230\021\006\003U\004\012\014\012Apple Inc.1,0*\006\003U\004\013\014#Apple Worldwide Developer Relations1D0B\006\003U\004\003\014;Apple Worldwide Developer Relations Certification Authority"
WARN [2017-09-18 13:22:58.19]: Lane Context:
INFO [2017-09-18 13:22:58.19]: {:DEFAULT_PLATFORM=>:ios, :ENVIRONMENT=>"DEV", :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios refreshCertificates"}
ERROR [2017-09-18 13:22:58.19]: no implicit conversion of nil into String
INFO [2017-09-18 13:22:58.19]: Successfully generated documentation at path '/keychainDir/Dev/team1/AppName/fastlane/README.md'

+------+---------------------+-------------+
|             fastlane summary             |
+------+---------------------+-------------+
| Step | Action              | Time (in s) |
+------+---------------------+-------------+
| 1    | Verifying required  | 0           |
|      | fastlane version    |             |
| 2    | default_platform    | 0           |
| 💥   | match               | 3           |
+------+---------------------+-------------+

ERROR [2017-09-18 13:22:58.21]: fastlane finished with errors

Looking for related GitHub issues on fastlane/fastlane...
Search query: no implicit conversion of nil into String

URL: https://api.github.com/search/issues?q=no%20implicit%20conversion%20of%20nil%20into%20String+repo:fastlane/fastlane
➡  "no implicit conversion of nil into String" when executing snapshpt
    https://github.com/fastlane/fastlane/issues/7433 [closed] 8 💬
    5 days ago

➡  Fastfile:3:in `+': [!] no implicit conversion of nil into String (TypeError)
    https://github.com/fastlane/fastlane/issues/9335 [closed] 2 💬
    3 weeks ago

➡  [!] no implicit conversion of nil into String (TypeError) in Hockey acktion
    https://github.com/fastlane/fastlane/issues/9622 [closed] 7 💬
    29 Jun 2017

and 59 more at: https://github.com/fastlane/fastlane/search?q=no%20implicit%20conversion%20of%20nil%20into%20String&type=Issues&utf8=✓

🔗  You can ⌘ + double-click on links to open them directly in your browser.

✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.6

Ruby
2.3.3

Bundler?
true

Git
git version 2.14.1

Installation Source
~/Dev/team1/AppName/vendor/bundle/bin/fastlane

Host
Mac OS X 10.12.6 (16G29)

Ruby Lib Dir
~/.rbenv/versions/2.3.3/lib

OpenSSL Version
OpenSSL 1.0.2j  26 Sep 2016

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
~/Dev/team1/Xcode.app/Contents/Developer/

Xcode Version
8.3.3

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://docs.fastlane.tools/actions
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.56.0"

default_platform :ios

platform :ios do
  before_all do
    # ENV["SLACK_URL"] = "https://hooks.slack.com/services/..."
  end

  desc "Runs all the tests"
  lane :test do
    scan
  end

  # You can define as many lanes as you want

  desc "Pull and install latest certificates and provisioning profiles based on environment using match"
  lane :refreshCertificates do
    match
  end

  desc "Build the app based on environment using gym"
  lane :buildAndArchive do
    gym
  end

  desc "Submit to Hockey App portal using configured Hockey App api using configured token"
  lane :submitHockey do
    hockey(api_token: ENV["HOCKEYAPP_API_TOKEN"],
          notes: "Build from fastlane")
  end

  desc "Update cocoapods, refresh certs, build app but DO NOT upload to Hockey App. Built app will be in 'GYM_OUTPUT_DIRECTORY' ENV variable"
  lane :buildWithoutDeployment do
    puts "Updating cocoapods"
    cocoapods(use_bundle_exec: true)

    refreshCertificates

    buildAndArchive
  end

  desc "Update cocoapods, refresh certs, build app and deploy to Hockey App portal. Use --env <EnvironmentName> when running"
  lane :deployBuild do
    puts "Updating cocoapods"
    cocoapods(use_bundle_exec: true)

    refreshCertificates

    buildAndArchive

    submitHockey
  end

  after_all do |lane|
    # This block is called, only if the executed lane was successful

    # slack(
    #   message: "Successfully deployed new App Update."
    # )
  end

  error do |lane, exception|
    # slack(
    #   message: exception.message,
    #   success: false
    # )
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://docs.fastlane.tools/actions

# fastlane reports which actions are used. No personal data is recorded.
# Learn more at https://github.com/fastlane/fastlane#metrics

No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.57.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.0.0

bundler
1.15.4

io-console
0.4.5

CFPropertyList
2.3.5

ZenTest
4.11.1

RubyInline
3.12.4

i18n
0.8.6

minitest
5.10.3

thread_safe
0.3.6

tzinfo
1.2.3

activesupport
4.2.9

public_suffix
2.0.5

addressable
2.5.2

babosa
1.0.2

claide
1.0.2

fuzzy_match
2.0.4

nap
1.1.0

cocoapods-core
1.3.1

cocoapods-deintegrate
1.0.1

cocoapods-downloader
1.1.3

cocoapods-plugins
1.0.0

cocoapods-search
1.0.0

cocoapods-stats
1.0.0

netrc
0.7.8

cocoapods-trunk
1.2.0

cocoapods-try
1.1.0

colored2
3.1.2

escape
0.0.4

fourflusher
2.0.1

gh_inspector
1.0.3

molinillo
0.5.7

ruby-macho
1.1.0

nanaimo
0.2.3

xcodeproj
1.5.1

cocoapods
1.3.1

dotenv
2.2.1

osx_keychain
1.0.1

cocoapods-keys
2.0.0

colored
1.2

highline
1.7.8

commander-fastlane
4.4.5

declarative
0.0.10

declarative-option
0.1.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

excon
0.59.0

multipart-post
2.0.0

faraday
0.13.1

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.12.2

fastimage
2.1.0

jwt
1.5.6

little-plugger
1.1.4

multi_json
1.12.2

logging
2.2.2

memoist
0.16.0

os
0.9.6

signet
0.7.3

googleauth
0.5.3

httpclient
2.8.3

mime-types-data
3.2016.0521

mime-types
3.1

uber
0.1.0

representable
3.0.4

retriable
3.1.1

google-api-client
0.13.6

json
2.1.0

mini_magick
4.5.1

multi_xml
0.6.0

plist
3.3.0

rubyzip
1.2.1

security
0.1.3

slack-notifier
1.5.1

terminal-notifier
1.8.0

unicode-display_width
1.3.0

terminal-table
1.8.0

tty-screen
0.5.0

word_wrap
1.0.0

rouge
2.0.7

xcpretty
0.2.8

xcpretty-travis-formatter
0.0.4

generated on: 2017-09-18

+1

+1

Also affected by this when running workflows with match

+1

+1

+1: I'm getting this with sighas well.  Version 2.57.0

+1 Yup, we're getting that as well

+1 I'm getting this with match and sigh.

Comparing with --verbose output from 2.56 the last few lines here may be the issue:
INFO [2017-09-18 14:09:53.45]: 🔓  Decrypted 'H6K9EUZN9S.cer'
INFO [2017-09-18 14:09:53.50]: 🔓  Decrypted 'H6K9EUZN9S.p12'
INFO [2017-09-18 14:09:53.56]: 🔓  Decrypted 'InHouse_com.team1.AppName.mobileprovision'
INFO [2017-09-18 14:09:53.61]: 🔓  Decrypted 'InHouse_com.team1.AppName.Keyboard.mobileprovision'
INFO [2017-09-18 14:09:53.71]: 🔓  Successfully decrypted certificates repo
INFO [2017-09-18 14:09:53.76]: Verifying that the certificate and profile are still valid on the Dev Portal...
INFO [2017-09-18 14:09:55.00]: Installing certificate...
INFO [2017-09-18 14:09:55.00]: $ security list-keychains -d user
INFO [2017-09-18 14:09:55.02]: ▸     "/KeychainDir/Library/Keychains/login.keychain-db"
INFO [2017-09-18 14:09:55.02]: $ security find-certificate -c 'Apple Worldwide Developer Relations Certification Authority' /KeychainDir/Library/Keychains/login.keychain-db
INFO [2017-09-18 14:09:55.05]: ▸ keychain: "/KeychainDir/Library/Keychains/login.keychain-db"
INFO [2017-09-18 14:09:55.05]: ▸ version: 512
INFO [2017-09-18 14:09:55.05]: ▸ class: 0x80001000
INFO [2017-09-18 14:09:55.05]: ▸ attributes:
INFO [2017-09-18 14:09:55.05]: ▸     "alis"<blob>="Apple Worldwide Developer Relations Certification Authority"
INFO [2017-09-18 14:09:55.05]: ▸     "cenc"<uint32>=0x00000003
INFO [2017-09-18 14:09:55.05]: ▸     "ctyp"<uint32>=0x00000001
INFO [2017-09-18 14:09:55.05]: ▸     "hpky"<blob>=0x88271709A9B618608BECEBBAF64759C55254A3B7  "\210'\027\011\251\266\030`\213\354\353\272\366GY\305RT\243\267"
INFO [2017-09-18 14:09:55.05]: ▸     "issu"<blob>=0x3062310B300906035504061302555331133011060355040A130A4150504C4520494E432E31263024060355040B131D4150504C452043455254494649434154494F4E20415554484F52495459311630140603550403130D4150504C4520524F4F54204341  "0b1\0130\011\006\003U\004\006\023\002US1\0230\021\006\003U\004\012\023\012APPLE INC.1&0$\006\003U\004\013\023\035APPLE CERTIFICATION AUTHORITY1\0260\024\006\003U\004\003\023\015APPLE ROOT CA"
INFO [2017-09-18 14:09:55.05]: ▸     "labl"<blob>="Apple Worldwide Developer Relations Certification Authority"
INFO [2017-09-18 14:09:55.05]: ▸     "skid"<blob>=0x88271709A9B618608BECEBBAF64759C55254A3B7  "\210'\027\011\251\266\030`\213\354\353\272\366GY\305RT\243\267"
INFO [2017-09-18 14:09:55.05]: ▸     "snbr"<blob>=0x01DEBCC4396DA010  "\001\336\274\3049m\240\020"
INFO [2017-09-18 14:09:55.05]: ▸     "subj"<blob>=0x308196310B300906035504061302555331133011060355040A0C0A4170706C6520496E632E312C302A060355040B0C234170706C6520576F726C647769646520446576656C6F7065722052656C6174696F6E733144304206035504030C3B4170706C6520576F726C647769646520446576656C6F7065722052656C6174696F6E732043657274696669636174696F6E20417574686F72697479  "0\201\2261\0130\011\006\003U\004\006\023\002US1\0230\021\006\003U\004\012\014\012Apple Inc.1,0*\006\003U\004\013\014#Apple Worldwide Developer Relations1D0B\006\003U\004\003\014;Apple Worldwide Developer Relations Certification Authority"
DEBUG [2017-09-18 14:09:55.42]: Certificate 'H6K9EUZN9S.cer' is already installed on this machine
INFO [2017-09-18 14:09:55.42]: $ security import /var/folders/7g/qgyrmc1x0_g313fqrlx9jvbc0000gn/T/d20170918-84261-roys8a/certs/enterprise/H6K9EUZN9S.p12 -k '/KeychainDir/Library/Keychains/login.keychain-db' -P '' -T /usr/bin/codesign -T /usr/bin/security
security: SecKeychainItemImport: The specified item already exists in the keychain.
INFO [2017-09-18 14:09:55.52]: $ security set-key-partition-list -S apple-tool:,apple: -k '' /KeychainDir/Library/Keychains/login.keychain-db
security: SecKeychainItemSetAccessWithPassword: The user name or passphrase you entered is not correct.

SecKeychainItemSetAccessWithPassword: The user name or passphrase you entered is not correct.
Fastlane should have my account password and be configured with permissions to access the default login keychain. However, this output makes it seem like something is failing. The match command still succeeds in 2.56.
I'm thinking this commit may be the culprit: https://github.com/fastlane/fastlane/commit/1925620e4b1ea196088773d5f0d119afa34e3b6f#diff-267555e817b0829e97d4e957a8824667.
It seems like this commit has either started failing (correctly) when there's an error accessing the keychain for the WWDR cert, or has introduced a new issue. Specifically the change on line 20 to the installed_identities(keychain, password) method.

+1

+1

+1

+1. Same issue using Xcode 9

+1

We just ended up downgrading to 2.56 and everything worked again. I suggest trying this if anyone else is stuck.

+1

+1
works with 2.56

+1
Is there a clean way to downgrade fastlane installed via the installer script?

@DerekBounceChat if you're using a Gemfile and bundler just add the version to the fastlane line:
gem "fastlane", "2.56"
then bundle install
If your just using the default gem sudo gem install fastlane --version 2.56 will do the trick.
IDK a good way if you're using homebrew or some other way.

+1 when running fastlane certs.

No luck downgrading to 2.56 for me.

An if keychain conditional was left out of the code.
In file fastlane_core/lib/fastlane_core/cert_checker.rb
change line 48 from
keychain = File.expand_path(keychain)
to
keychain = File.expand_path(keychain) if keychain
After changing that match went back to working perfectly.
Someone should make a pull request.

@pajama I also had to run
sudo gem uninstall fastlane --version 2.57

then when you run fastlane --version it should say you are using 2.56 which should work.

+1

+1

+1

+1

No need for more +1's. Just give a thumbs up on the initial issue report if you're experiencing the same. It will be handled soon.

Thanks @snelson21, I've submitted a PR: https://github.com/fastlane/fastlane/pull/10359, with your suggested change.

Any workarounds?

+1

+1

+1

+1

Is there workaround available for now

Workaround: Downgrade to 2.56

Is there a way to smoothly downgrade fastlane?

is there pod command to downgrade fastlane

how to downgrade with brew cask? can't upload build with major bug... :'(

Is it possible to get a hold of the installer zip for fastlane 2.56.0 ?

Check this:
https://devforgalaxy.github.io/en/2016/11/05/use-homebrew-cask-to-downgrad-or-install-en.html
Change version line to:
version '2.56.0'

The real issue is here: https://github.com/fastlane/fastlane/blob/c9b5cdbd7ec2d8714723cb737985fd07134c8f0c/match/lib/match/runner.rb#L89
it is not passing the params[:keychain_name]
https://github.com/fastlane/fastlane/blob/6aa27ae3cd2ca62d19825a13d64dd9aaf3ede8b9/match/lib/match/options.rb#L42-L46
Causing nil since the installed? methods defaults to nil keychain.
https://github.com/fastlane/fastlane/blob/1925620e4b1ea196088773d5f0d119afa34e3b6f/fastlane_core/lib/fastlane_core/cert_checker.rb#L6

whether its fixed

PR #10362 and PR #10359 are created to hopefully fix the issue.

Is it possible to get a hold of the installer zip for fastlane 2.56.0 ?

@agfa555
gem uninstall fastlane --version 2.57.0
gem install fastlane --version 2.56.0

As mentioned above the simplest fix is to reinstall fastlane 2.56. If you for any reason do not use bundler, then following commands can do the job:
gem install fastlane --version 2.56
gem uninstall fastlane --version 2.57

I have installed through brew cask cause through gems it caused errors...
Any way for a standalone version zip??

I suppose that version 2.57 is broken for both match and cert 😄

@agfa555 I am not familiar with "standalone zip version" nor installation of fastlane through brew cask. Unless anyone else is able to help you, I suggest to try the workaround mentioned by @casz and me just above. If that does not work, you may try to put sudo in front of the commands. I do not know how your gems are installed, for system ruby the sudo might be necessary.

@agfa555 consider using gemfile https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
@HristiyanZahariev it should work for cert otherwise please post the error stack.

@casz & @GoodMirek thank you, but I had to upload through altools instead...
cert is failing too:
8:in expand_path': [!] no implicit conversion of nil into String (TypeError)
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane_core/lib/fastlane_core/cert_checker.rb:48:in list_available_identities' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane_core/lib/fastlane_core/cert_checker.rb:23:in installed_identies'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane_core/lib/fastlane_core/cert_checker.rb:9:in installed?' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/cert/lib/cert/runner.rb:88:in block in find_existing_cert'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/cert/lib/cert/runner.rb:80:in each' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/cert/lib/cert/runner.rb:80:in find_existing_cert'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/cert/lib/cert/runner.rb:31:in run' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/cert/lib/cert/runner.rb:6:in launch'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/actions/cert.rb:17:in run' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/runner.rb:252:in block (2 levels) in execute_action'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in execute_action' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/runner.rb:230:in block in execute_action'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/runner.rb:226:in chdir' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/runner.rb:226:in execute_action'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/runner.rb:148:in trigger_action_by_name' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/fast_file.rb:146:in method_missing'
from Fastfile:58:in block (2 levels) in parsing_binding' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/lane.rb:33:in call'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/lane.rb:33:in call' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/runner.rb:49:in block in execute'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/runner.rb:45:in chdir' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/runner.rb:45:in execute'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/lane_manager.rb:52:in cruise_lane' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/command_line_handler.rb:30:in handle'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/commands_generator.rb:104:in block (2 levels) in run' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.5/lib/commander/command.rb:178:in call'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.5/lib/commander/command.rb:178:in call' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.5/lib/commander/command.rb:153:in run'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.5/lib/commander/runner.rb:476:in run_active_command' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:64:in run!'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.5/lib/commander/delegates.rb:15:in run!' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/commands_generator.rb:303:in run'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/commands_generator.rb:42:in start' 	from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/fastlane/lib/fastlane/cli_tools_distributor.rb:66:in take_off'
from /Users/agfa555/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.57.0/bin/fastlane:20:in <top (required)>' 	from /Users/agfa555/.fastlane/bin/bundle/bin/fastlane:22:in load'
from /Users/agfa555/.fastlane/bin/bundle/bin/fastlane:22:in <main>

Hey everyone, I'm incredible sorry this happened - we should have reacted faster. Unfortunately we didn't receive any Twitter messages that would ping us outside of working hours, so I only saw that just now 😢
I reverted the commit that caused the error with https://github.com/fastlane/fastlane/commit/36f18a568a48eaca615a0998f0cb85f293e29493 and I'm pushing a new release right now.
Again super sorry for the troubles, thanks everyone for helping out 👍

Alright, new release is live, please update and let me know if that works for you 👍

@KrauseFx no worries!!!! your system is awesome, it happens to the best of us...

I can confirm it now works fine with version 2.57.1 (at least in our case)

@KrauseFx confirmed fixed for me in 2.57.1. Closing issue and thanks for jumping on this! This tool is wonderful.

With newest beta problem exists. When I switched to 2.57.2 it's OK.

Still getting this issue with the beta version I'm on: 2.58.0.beta.20170919010003.
I have tried downgrading to 2.57.2 but for some reason Ruby Gem won't play well and uninstall the beta version. Can this push be fixed out to the nightly?

@johnrogers try to uninstall like this:
sudo gem uninstall fastlane --version "2.58.0.beta.20170919010003"

Awesome, thanks! Yeah, beta builds are only distributed once a day, by now, the new release should be ready 👍


MailboxProcessor.Receive () doesn't handle CancellationToken properly

In this example:
open System
open System.Threading

[<EntryPoint>]
let main argv =
    let cts = new CancellationTokenSource ()

    let mb =
        MailboxProcessor.Start (
            fun inbox -> async {
                use disp =
                    { new IDisposable with
                        member this.Dispose () =
                            printfn "Disposed"
                    }

                while true do
                    let! (msg : int) = inbox.Receive ()
                    printfn "Received %i" msg
            }, cancellationToken = cts.Token)

    mb.Post 1
    Thread.Sleep 1000
    cts.Cancel ()
    Thread.Sleep 4000
    0

expected output is:
Received 1
Disposed

but for some reason Dispose is not getting called. If line:
let! (msg : int) = inbox.Receive ()

is changed for something like:
let! (msg : int) = inbox.Receive 1000000

everything works as it should. Looks like at least TryReceive has the same problem.
I've tested it under Visual Studio Community 2017. Not sure if it is the right place to create this issue :)

@mishun The right place for the issue is http://github.com/Microsoft/visualfsharp, thanks

Whoops. Should I close this one then?

I'll close, thanks. Link is https://github.com/Microsoft/visualfsharp/issues/3337


Drop duplicate resources on the way into the resourcefetcher.

In some cases (related to overlapping watch terms) watt can hand duplicates of the same resource to the Python side of Ambassador. This causes problems.
While the right longer-term answer is to make sure watt doesn't do that, changing watt is a pretty high-risk sort of thing for right now. Filtering the duplicates out is a lot safer.

Looks good to me!


Gulp DICSS?

Please make this a task plugin so I can  gulp DICSS, grunt optional.

What a great idea!

Unfortunately, DICSS isn't designed to be used when gulping or grunting. DICSS should only be used during your runtime. There is a conversation about using DICSS in a backend at #7 which, if implemented, would make it possible to gulp or grunt your DICSS.


Video downloaded in mkv when mime is set to video/webm

How can I fix this?

When I do invokeSaveAsDialog it now says x-matroska as the file extension.

This might be the logical issue causing the problem you are facing RecordRTC Issue 825


[Issue 228] [fix] Extension- Handle FinalizeInput Psbt when sign psbt

🚀 Deployed on https://pr-253--papaya-melba-f5c160.netlify.app


fixes tensors not hashing correctly

This issue was caused from using __dict__ which converted the Tensor object into one with just its datatype and shape values, disregarding the actual buffer or content within the Tensor.
The Axon.py file when it was trying to decode the response from the sender would then compare the hash using the buffer that was sent, causing a mismatch of hashes.
This change fixes that by utilizing .dict() instead.

See: https://github.com/opentensor/bittensor/pull/1548


Allow specific types to be excluded

Hi
I've just started to use this library but have encountered an unfortunate issue.
In our API, we expose a public type that is shared between our consumers. However, it is not technically public in the same sense as methods and other types in our API. Our consumers use this type to communicate the global availability of features used for feature flagging, and the type resides in our API to allow easier distribution.
As I can understand from this issue #24, it was decided that such functionality should not be added because any change to the public API is considered a breaking change.
While that makes sense, it's more complex in my specific case.
Right now, I'm using a workaround where I manually remove the type using regex. Still, I'd be more comfortable simply excluding the type directly through the options, similar to how attributes can be excluded (#45).
Are there any plans to extend the options to allow excluding specific types?
From the implementation, adding support for this would be relatively straightforward, and I would also be willing to provide a pull request if the request sounds reasonable.

@siewers @danielmarbach @adamralph I've read and decided to implement this feature. I see no burden from design and maintanability perspective. We already have ApiGeneratorOptions.IncludeTypes so IMO ApiGeneratorOptions.ExcludeTypes looks well.

https://github.com/PublicApiGenerator/PublicApiGenerator/releases/tag/11.2.0
https://www.nuget.org/packages/PublicApiGenerator/11.2.0


ARTEMIS-4366 Missing Mirrored ACKs with MULTICAST and subscriptions

Its odd/confusing that the ReferenceNodeStoreFactory is still named to in most parameters and fields as 'referenceIDSupplier' or 'nodeStore', especially the latter with there being an actual seperate ReferenceNodeStore. Its mixing roles and field/param names up in a confusing manner. Feels like the behaviours should be split into separate concerns, as they largely were originally.
Alternatively many of the ID methods now on ReferenceNodeStoreFactory could perhaps just be made static helpers rather than being 'passed around on the side of a factory', since they only pull details from the message[reference] rather than the factory itself.


Keywords like describe, browser are not reflecting in vs code

When I type browser inside it() test, bhxBrowser is auto suggested. On navigating to go to definition for describe it says "no definition found for describe". Any help would be much appreciated. Not sure why auto suggestions are not reflecting.

Bug report

Node Version: 14.16.1
Protractor Version: 6.14.12
Operating System and Version macOS Big Sur 11.3

Do you have a project or isolated files?
You can see my project:
https://github.com/andredesousa/essential-angular-scaffold
Go to the e2e folder.

thanks for your input. I just executed example_spec.js and conf.js available in the path /usr/local/lib/node_modules/protractor/example in vscode and it worked.


Draft for snippet instrumentation

@jrieken I am trying to extend @JacksonKearl's instrumentation to understand extension snippets. I got the property into the Snippets instance but my TS foo fails to access the snippets object on the CompletionItem | SnippetCompletion. Maybe I am holding it wrong.
Can you confirm if this approach is generally sane and how I solve the TS puzzle to access .snippets.

@jrieken I got your recommendation to track extensions in CompletionItem working. It seems lean enough, but what do you think?


add (client) socket options

[ ] This is a bugfix
[x] This is a new feature
[ ] This is a code refactor
[ ] This is a test update
[ ] This is a typo fix
[ ] This is a metadata update

For Bugs and Features; did you add new tests?
There aren't currently any client tests.  This should check that __hotClientOptions__ received the overridden values somehow.

Motivation / Use-Case
#30

Breaking Changes

Additional Info
See https://github.com/nmschulte/docker-webpack-hmr-test/tree/whc-socket-options.

Aye. Cheers. We're going to close this, but it won't go anywhere, it'll still be in the PRs.


How to get the cell value onClick?

Hi, I have a multi-column table and I want the cell values of only one particular column when clicked. I tried the column event but it was not fruitful. Any advice on that?

My bad. Achieved it through e.target.innerHTML. Thanks.


SRT not working when over 200-250ms latency between server and publisher/reader

I have mediamtx running on a VPS in London, UK and I am in Australia. When sending via SRT the log shows constant connects and disconnects. I have tried multiple VPS in London and the same problem occurs. It does not happen to my servers in Australia and USA.
Everything is pointing towards an issue when the latency between client and server is high, in this case, over 250ms. The same issue also occurs when trying to read a stream via SRT.
Looking at it further, mediamtx seems to show the source connecting multiple times which appears to be breaking it. The same occurs for clients reading. If I set mediamtx to disallow publish override then publish starts working, but read still does not.
2024/09/10 13:45:58 INF [SRT] [conn 159.196.xxx.xxx:48962] opened
2024/09/10 13:45:59 INF [SRT] [conn 159.196.xxx.xxx:48962] opened
2024/09/10 13:45:59 INF [path zowie2] closing existing publisher
2024/09/10 13:45:59 INF [SRT] [conn 159.196.xxx.xxx:48962] closed: terminated
2024/09/10 13:45:59 INF [SRT] [conn 159.196.xxx.xxx:48962] opened
2024/09/10 13:45:59 INF [path zowie2] closing existing publisher
2024/09/10 13:45:59 INF [SRT] [conn 159.196.xxx.xxx:48962] closed: terminated
2024/09/10 13:46:01 INF [SRT] [conn 159.196.xxx.xxx:48962] closed: astits: no more packets

Which version are you using?
v1.9.0
Which operating system are you using?

[x] Linux amd64 standard
[x] Linux amd64 Docker
[x] Linux arm64 standard
[x] Linux arm64 Docker
[ ] Linux arm7 standard
[ ] Linux arm7 Docker
[ ] Linux arm6 standard
[ ] Linux arm6 Docker
[ ] Windows amd64 standard
[ ] Windows amd64 Docker (WSL backend)
[ ] macOS amd64 standard
[ ] macOS amd64 Docker
[ ] Other (please describe)

Describe the issue
Description
Describe how to replicate the issue

start the server
publish with ...
read with ...

Did you attach the server logs?

yes / no
Did you attach a network dump?

yes / no

If I leave the source (OBS or Encoder) to try and constantly connect, eventually after a few mins they will be successful and maintain connection until stopped. I can't seem to make it work for reading clients however.

I have been doing some testing using various VPN servers around the world to try and test at what latency SRT fails to connect. It seems to be somewhere between 200-250ms. Anything with a static latency over that then SRT just completely refuses to work on Mediamtx.

Some further testing shows the problem doesn't occur with the sample server over at gosrt: https://github.com/datarhei/gosrt/blob/f2ff8a3cc35debc3f7080d6f0a94a93cac609940/contrib/server/main.go#L192
It shows something somewhat similar in the logs when the delay is somewhere above 200 ms, but it manages to get past it.
PUBLISH         START /myapp/stream1 (<IP_ADDRESS>:36117) publishing
CONNECT      CONFLICT /myapp/stream1 (<IP_ADDRESS>:36117) already publishing
CONNECT      CONFLICT /myapp/stream1 (<IP_ADDRESS>:36117) already publishing
CONNECT      CONFLICT /myapp/stream1 (<IP_ADDRESS>:36117) already publishing

That program works slightly differently. You need something like server -addr :8890 -app /myapp coupled with ffmpeg -re -i /home/root/some-video.mp4 -c copy -f mpegts "srt://<IP_ADDRESS>:8890?streamid=publish:/myapp/stream1&latency=4000000", and then for example srt://localhost:8890?streamid=/myapp/stream1 to view the result.

I am having a similar problem - when latency is too high, the publisher terminates and my streaming software (e.g. OBS Studio) hangs up and shows "Connecting" (instead of throwing an error message that it is not possible to publish the stream or showing "Stop stream"). If I try to embed the same stream into OBS Studio I also do not see it.
Sometimes something weird happens though. The mediaMTX logs no longer show that the publisher has been terminated, but at the same time there is no message that a publisher is available. In addition, according to the logs, the reader connection is closed because no one is publishing. However, when I try to embed the same stream into OBS Studio, I can see the stream even if the button in OBS Studio still shows "Connecting". So basically OBS Studio somehow does not seem to get any feedback from mediaMTX about a stream being published and at the same time I also do not see in the mediaMTX logs that a stream is being published.

Any devs able to comment on this issue? Doesn't seem to be an isolated issue and makes cross continent streaming near impossible via SRT.

I have the same issue. My latency on the connection between the MediaMTX instances is around 350ms. I'm using FFMPEG to forward SRT streams, but get the exact same error output as @Frenzie.
I'm trying to tweak the SRT timeout and other parameters, but can't get this to work... Anyone that has input? Would be highly appreciated. Thanks.
ffmpeg -i srt://<IP_ADDRESS>:8890?streamid=read:STRID01 -c copy -fflags nobuffer -f mpegts srt://<IP_ADDRESS>:8890?streamid=publish:STRID01

Jumping in on this one as well. I have this running on a pretty powerful machine in a datacenter with a fiber connection. I've had 5 or 6 clients publishing with no issue for hours at a time, but one of the clients who has latency that spikes every once in awhile gets disconnected every so often. The disconnect is typically just a hard cut that returns after about 2-3 seconds, goes out a second time and then comes back to normal after another 2-3 seconds. I have another SRT server running on a box next to this one that they can push into without any issues. There doesn't seem to be any quality loss on audio or video which makes me believe this is just a disconnect from MTX.

It might be worth retesting with #3992. I think I tested https://github.com/datarhei/gosrt/commit/f2ff8a3cc35debc3f7080d6f0a94a93cac609940 when I said the sample server at gosrt works fine, but I overlooked that's not the same as 0.7.0. The commits on 28 August sound like they may be relevant.

i merged #3992, let me know if it makes a difference.

@aler9 - I'm just jumping into this project and haven't compiled it on my own machine. I'm using the docker image to install onto a linux box. Any chance you or someone else can get the new build published to Docker?
I can try to take a swing at building locally tomorrow morning if not. I see instructions for compiling, cross-compiling, and making all binaries. Will the command to make binaries with Docker also create a usable docker-ffmpeg image?

If you set this to false there's no problem:
https://github.com/bluenviron/mediamtx/blob/cf01683168b6fd525c1c3e68d05ef90f665dead8/mediamtx.yml#L477-L478
https://github.com/bluenviron/mediamtx/blob/cf01683168b6fd525c1c3e68d05ef90f665dead8/internal/core/path.go#L476-L479
Thinking aloud, and keep in mind I don't know Go, that suggests something along these lines should do the trick:
diff --git a/internal/core/path.go b/internal/core/path.go
index 4eeae3a4..7dbda1ec 100644
--- a/internal/core/path.go
+++ b/internal/core/path.go
@@ -83,6 +83,7 @@ type path struct {
        confMutex                      sync.RWMutex
        source                         defs.Source
        publisherQuery                 string
+       publisherAddedAt               time.Time
        stream                         *stream.Stream
        recorder                       *recorder.Recorder
        readyTime                      time.Time
@@ -473,6 +474,11 @@ func (pa *path) doAddPublisher(req defs.PathAddPublisherReq) {
        }

        if pa.source != nil {
+               if time.Since(pa.publisherAddedAt) < 2*time.Second {
+                       req.Res <- defs.PathAddPublisherRes{Err: fmt.Errorf("current publisher has been active for less than 2 seconds")}
+                       return
+               }
+
                if !pa.conf.OverridePublisher {
                        req.Res <- defs.PathAddPublisherRes{Err: fmt.Errorf("someone is already publishing to path '%s'", pa.name)}
                        return
@@ -485,6 +491,7 @@ func (pa *path) doAddPublisher(req defs.PathAddPublisherReq) {

        pa.source = req.Author
        pa.publisherQuery = req.AccessRequest.Query
+       pa.publisherAddedAt = time.Now()

        req.Res <- defs.PathAddPublisherRes{Path: pa}
 }

I already set "overridepublisher" to "no" and still face this issue. So at least for me this is not the solution.

You're right, it looks like the connection still fails if you up the latency to 2 seconds, but it remains successfully connected at 1.5. But in any case not closing the existing publisher quite so enthusiastically does a lot of good already.

Setting to false did help with one of the feeds, but I then found feeds with needs for longer latency settings and ran into the same problem again. I'm about to just fallback to RTMP... It seems like the SRT functionality here isn't working quite right just yet.


[Bug] One-way bound '[ngModel]' changes when adding a new tag

Hello, I think I found a bug.
Imagine that you have tag-input in your form with one-way bound [ngModel]=myarray.
Case 1:
Load the page and add a new tag, this tag adds to this one-way bound model. That's not correct behavior. The correct behavior is that tag should only add to form's.value.name, but ngModel should stay unchanged.
Case 2:
Load the page and delete some tag, the ng-model stays unchanged (that's correct) and that tag is removed in the form's array only (that's correct too).
After one tag is removed, you can add a new tag and that new tag won't add to the ngModel (that's correct) and only adds to the form's model (that's correct too).
So I think there could be a little bug in your code, with ngModel binding to a tag's input text input. It's fixed when you delete some tag and then add new, so I think somewhere in that delete function is declared something that's missing initially.
You can see the problem here.
Thank you so much for your help!

I think I found a fix, I wanted to PR but I haven't found /dist/ng2-tag-input.bundle.js file, so I can paste my solution here.
In this file, replace TagInput.prototype.addItem function with this:
TagInput.prototype.addItem = function (isFromAutocomplete) { 	        if (isFromAutocomplete === void 0) { isFromAutocomplete = false; } 	        var item = this.setInputValue(this.form.value.item); 	        var isDupe = this.items.indexOf(item) !== -1; 	        var isValid = this.form.valid && 	            isDupe === false && 	            !this.maxItemsReached && 	            ((isFromAutocomplete && this.onlyFromAutocomplete === true) || this.onlyFromAutocomplete === false); 	        if (isValid) { 	            this.items = this.items.filter(function (_item) { return _item }); 	            this.items.push(item); 	            this.onAdd.emit(item); 	        } 	        this.setInputValue(''); 	    };
The trick is in this filtering array function on item add:
this.items = this.items.filter(function (_item) { return _item });
With my not so much experience with javascript I assume that it can be problem with some reference, this should filter the array and delete the reference.
I tested it and it seems it works like a charm now.

Hi! I see the issue, If you want to submit a PR, have a look at ./components/tag-input.ts. That is the source file. Otherwise I'll release a fix soon :)

PR https://github.com/Gbuomprisco/ng2-tag-input/pull/26

Published a version that should fix this! Let me know :)


error for R200, Timeout waiting for frames.

I was trying to use a R200 camera with firmware version <IP_ADDRESS>.
My system is ubuntu 14.04 with a patched 4.4 kernel.
After I run cpp-capture. A graphic window comes out and freezes in the first frame.
The program crashes after a few seconds with the following outputs on terminal:
Capturing DEPTH at 480 x 360, fov = 56.5 x 43.9, distortion = NONE
Capturing COLOR at 640 x 480, fov = 54.1 x 41.5, distortion = MODIFIED_BROWN_CONRADY
Capturing INFRARED at 480 x 360, fov = 56.5 x 43.9, distortion = NONE
Capturing INFRARED2 at 480 x 360, fov = 56.5 x 43.9, distortion = NONE
RealSense error calling rs_wait_for_frames(device:0x8351f0):
Timeout waiting for frames.

Timeout waiting for frames is most often a symptom of an unsupported USB 3.0 host controller. We have also encountered plenty of systems where only 2 out of the 4 available physical USB 3.0 ports on a given machine will work! So, in order of priority:

Only stream depth (remove extra bandwidth)
Try a different (possibly thicker or shorter) USB 3.0 cable. Skip this step if you are using the one that came bundled with the R200.
Try all the different 3.0 ports available to you
Attempt to use a powered USB 3.0 hub (sometimes controllers don't negotiate enough power to the camera to actually stream data).
Hop over to a Windows 8/10 machine to double check that the camera can stream at all

I have the same problem.
I had a working R200 in ubuntu 14.04 on my workstation. i wanted to test it on laptop, so I performed the same process on it and R200 never worked in it. I gave up on the laptop and returned to my workstation and all of a sudden the R200 now does not work. The F200 works without any issue on the same computer. Is there anyway to reflash the firmware?

@bpwiselybabu 'suddently does not work' needs some more clarification! What errors are you encountering?
This library does not write any permanent data back to the camera so it's unlikely the firmware went corrupt. You can always plug it into a Windows 10 machine and install the Intel RealSense DCM to reflash the firmware.

@ddiakopoulos
I tried a powered usb 3.0 port. The program works well if only depth or only color stream is enabled, but still crashes with all streams enabled. It seems that the usb port on my laptop is not fast enough.
I want to change the framerate, but I didnot find the config interface from cpp-config-ui or corresponding rs-option in file "rs.h". Would you help me with that?

@ddiakopoulos I am sorry, I was not very clear about my problem as I was working for a conference deadline. I resolved the situation using some of the old driver that was published in the RealSense_ROS package but I will explain the issue I faced and the way I resolved it a bit more in detail.

When I encountered this issue, I had a working R200 on my workstation with no issues. The workstation runs Linux 14.04 with 3.19.0-49-generic kernel.
I wanted to get the R200 that I have working on a Linux laptop(portability duh). So I updated the firmware on the R200 using a windows machine and then progressively updated the kernel on my linux laptop from trusty kernel(3.16) to 3.18 and then to whily-lts(4.2) and then to custom kernel 4.4.4. During each iteration, i followed all the instructions presented in this respo for installation with no success. At some point I was able to get the RGB camera working but not the depth camera but later ended up in a point where it would give a timeout error.
I gave up on my laptop and returned to my workstation and to my surprise, the R300 stopped working on my workstation on which I have not done any significant changes. F200 continued to work without any issues. (This is where I suspected a possible corruption to the firmware as I had attempted multiple installs and had encountered multiple timeouts with different sync errors). I decided to reinstall the driver on my workstation and change the backend to UVC from V4L with no success.
Finally based on my memory about how I had installed the realsense first time. I found the install script presented in https://github.com/PercATI/RealSense_ROS/tree/master/r200_install and recompile the driver with V4L backend. This resolved my issue on the workstation.

The cake is a Lie! No, wait a minute... This is not a cake, this is an e-mail account.
The e-mail account is a lie.
Im sorry.

It might seem like a lie but I am pretty certain there is some issue in your install instructions that could have stopped R200 from working. If you are not writing back to R200. It means the drivers on my workstation got corrupted. And the only possibility of it is repeated reinstall of your drivers.

I change the fps to 30, then everything if fine.
It seems that R200 is strict with speed of USB port.
But I still don't understand why it is OK to stream at 60fps on a Windows laptop.
Thank you for your help! @ddiakopoulos

@bpwiselybabu Our installer script is a modified version of the one you linked in the RealSense_ROS repo (just take a look at the source). I think this prompts a need to introduce an installation script so we can reset the state of any possibly failed or incomplete installation sub-steps. As you noted, backing out entirely and just trying it all again often fixes any possible mis-steps along the installation process.
@sclin-loauas Yes, R200 will happily time out if your USB controller can't handle the bandwidth. The 60/30 behavior is odd to me, but there's many variables which could make an impact.
Closing this out.

Hi @sclin-loauas , how do you change the fps to 30? I am having the same problem.

@sclin-loauas Could you please detail on how to change the fps? I am experiencing the same issue. Thanks in advance!

I had the same problem with an SR300 camera on a newly built computer. SR300-live-test reported "Timeout waiting for frames" on all of the colour image tests. Problem was solved with a powered USB 3.0 hub.

I had the same problem with an SR300 camera on a newly built computer. SR300-live-test reported "Timeout waiting for frames" on all of the colour image tests. Problem was solved with a powered USB 3.0 hub.


Query: Investigate perf regressions from 2.0 in QueryCompilationTests.ToList()

@AndriySvyryd ?

@roji Would it be possible to compare results for this test between 2.0 and 3.x?

Sure, if we have a benchmark for it we should be able to run it against 2.x and against 3.x and compare. Catch me tomorrow or Friday and we can look at it together.

@roji ran the benchmark and master is better than 2.0 in both runtime and memory allocations

Here are the 2.0 vs. master (3d94a7dcd5aa0cc5568a62945affa85bfc56c382) results, for the record:
2.0

BenchmarkDotNet=v0.11.3, OS=ubuntu 19.10
Intel Core i7-9750H CPU 2.60GHz, 1 CPU, 12 logical and 6 physical cores
.NET Core SDK=5.0.100-alpha1-015536
  [Host] : .NET Core 2.0.9 (CoreCLR <IP_ADDRESS>, CoreFX 4.6.26614.01), 64bit RyuJIT

Toolchain=InProcessToolchain

Method
Mean
Error
StdDev
Gen 0/1k Op
Gen 1/1k Op
Gen 2/1k Op
Allocated Memory/Op

ToList
18.84 ms
0.3264 ms
0.3053 ms
187.5000
62.5000
-
1.23 MB

FilterOrderProject
23.65 ms
0.5232 ms
0.6228 ms
375.0000
93.7500
-
2.4 MB

MultipleJoins
95.60 ms
1.3481 ms
1.1257 ms
1333.3333
500.0000
-
8.79 MB

master (3d94a7dcd5aa0cc5568a62945affa85bfc56c382)

BenchmarkDotNet=v0.11.3, OS=ubuntu 19.10
Intel Core i7-9750H CPU 2.60GHz, 1 CPU, 12 logical and 6 physical cores
.NET Core SDK=  3.0.100 [/usr/share/dotnet/sdk]
  [Host] : .NET Core 5.0.0-alpha.1.19551.1 (CoreCLR <IP_ADDRESS>501, CoreFX <IP_ADDRESS>113), 64bit RyuJIT

Toolchain=InProcessToolchain

Method
Mean
Error
StdDev
Gen 0/1k Op
Gen 1/1k Op
Gen 2/1k Op
Allocated Memory/Op

ToList
13.86 ms
0.2721 ms
0.3988 ms
156.2500
78.1250
-
975.95 KB

FilterOrderProject
12.70 ms
0.2509 ms
0.2789 ms
171.8750
46.8750
-
1113.04 KB

MultipleJoins
84.36 ms
0.3289 ms
0.3077 ms
1000.0000
500.0000
-
6637.03 KB

Very nice!


v2.1.3 seems to break @vitest/web-worker path in NX Monorepos

Describe the bug
I've been upgrading our dependencies to the most recent versions lately and I've started receiving the following error in our NX Monorepo related to @vitest/web-worker that is breaking all of our unit tests:
Error: Failed to load url<EMAIL_ADDRESS>(resolved id: /Users/kether/frontend/node_modules/@vitest/web-worker/dist/index.js). Does the file exist?

What's particularly weird is that the file is there as expected:

The unit tests run fine up to and including 2.1.2. But as soon as I upgrade to 2.1.3 or above, I start getting the error which breaks our test suites. If I leave<EMAIL_ADDRESS>I can continue to upgrade @vitest/web-worker up to 2.2.0-beta.1 with the unit tests continuing to run as expected.
Config:
{
  root: '/Users/kether/frontend/apps/cloud/app',
  cacheDir: '../../../node_modules/.vite/./apps/cloud/app',
  plugins: [
    {
      name: 'nx-vite-ts-paths',
      enforce: 'pre',
      configResolved: [AsyncFunction: configResolved],
      resolveId: [Function: resolveId],
      writeBundle: [AsyncFunction: writeBundle]
    },
    {
      name: 'unplugin-vue-router',
      enforce: 'pre',
      resolveId: [Function: resolveId],
      buildStart: [Function: buildStart],
      buildEnd: [Function: buildEnd],
      transformInclude: [Function: transformInclude],
      transform: [Function (anonymous)],
      loadInclude: [Function: loadInclude],
      load: [Function (anonymous)],
      vite: {
        configureServer: [Function: configureServer],
        handleHotUpdate: { order: 'post', handler: [Function: handler] }
      },
      configureServer: [Function: configureServer],
      handleHotUpdate: { order: 'post', handler: [Function: handler] }
    },
    {
      name: 'unplugin-vue-i18n:resource',
      enforce: 'pre',
      vite: {
        config: [Function: config],
        configResolved: [Function: configResolved],
        handleHotUpdate: [AsyncFunction: handleHotUpdate]
      },
      webpack: [Function: webpack],
      resolveId: [Function: resolveId],
      load: [AsyncFunction: load],
      transformInclude: [Function: transformInclude],
      transform: [Function (anonymous)],
      config: [Function: config],
      configResolved: [Function: configResolved],
      handleHotUpdate: [AsyncFunction: handleHotUpdate]
    },
    {
      name: 'vite:vue',
      api: { options: [Getter/Setter], version: '5.2.0' },
      handleHotUpdate: [Function: handleHotUpdate],
      config: [Function: config],
      configResolved: [Function: configResolved],
      configureServer: [Function: configureServer],
      buildStart: [Function: buildStart],
      resolveId: [AsyncFunction: resolveId],
      load: [Function: load],
      transform: [Function: transform]
    },
    { name: 'svg-loader', enforce: 'pre', load: [AsyncFunction: load] }
  ],
  build: {
    target: 'esnext',
    outDir: '../../../dist/apps/cloud/app',
    reportCompressedSize: true,
    commonjsOptions: { transformMixedEsModules: true },
    assetsDir: 'd/frontend',
    rollupOptions: {
      input: {
        app: '/Users/kether/frontend/apps/cloud/app/index.html'
      },
      output: {
        manualChunks: [Function: manualChunks],
        assetFileNames: [Function: assetFileNames]
      }
    }
  },
  test: {
    globals: true,
    mockReset: true,
    environment: 'happy-dom',
    passWithNoTests: true,
    globalSetup: '../../../libs/configs/src/lib/vitest.global-setup.ts',
    setupFiles: [
      '../../../libs/configs/src/lib/vitest.setup-time-globals.ts',
      '@vitest/web-worker',
      '../../../libs/configs/src/lib/vitest.setup-dom-matchers.ts'
    ],
    include: [ 'src/**/*.{test,spec}.{js,ts}' ],
    reporters: [ 'default' ],
    watch: false,
    pool: 'threads',
    poolOptions: { threads: { singleThread: true } },
    coverage: {
      provider: 'v8',
      reporter: [ 'json', 'html' ],
      reportsDirectory: '../../../coverage/./apps/cloud/app',
      include: [ 'src/**' ],
      exclude: [
        '**/*.spec.js',
        '**/*.spec.ts',
        '**/*.spec.data.ts',
        '**/*.stories.ts',
        '**/*.mdx',
        '**/*.json',
        '**/*.types.ts',
        '**/*.typegen.ts',
        '**/*.bus.ts',
        '**/index.ts',
      ]
    }
  },
  server: { fs: { allow: [ '../../../libs/configs/src/lib' ] } },
  define: {
    __VUE_OPTIONS_API__: 'false',
    __VUE_PROD_DEVTOOLS__: 'false',
    __VUE_PROD_HYDRATION_MISMATCH_DETAILS__: 'false'
  },
  optimizeDeps: { exclude: [ 'vue-i18n' ] }
}

Reproduction

git clone git@github.com:K3TH3R/ts-issue-starter-template.git vitest-path-issue
cd vitest-path-issue && git checkout vitest-2.1.2 && yarn install
yarn app1:test -> everything runs as expected
git checkout vitest-2.1.3 && rm -rf node_modules && yarn install
yarn app1:test -> fails with the @vitest/web-worker error

System Info
System:
    OS: macOS 15.1
    CPU: (10) arm64 Apple M2 Pro
    Memory: 121.14 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.9.0 - /opt/homebrew/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 10.8.3 - /opt/homebrew/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 131.0.6778.70
    Edge: 131.0.2903.51
    Safari: 18.1
  npmPackages:
    @vitejs/plugin-vue: 5.2.0 => 5.2.0
    @vitest/coverage-v8: 2.1.5 => 2.1.5
    @vitest/ui: 2.1.5 => 2.1.5
    @vitest/web-worker: 2.1.3 => 2.1.3
    vite: 5.4.11 => 5.4.11
    vitest: 2.1.3 => 2.1.3

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

@AriPerkkio Okay, I've added a reproduction with the instructions in the original comment above.


##[warning]File name doesn't indicate a full path to a executable file.

The Command Line task print this warning even if the full path is used:
##[warning]File name doesn't indicate a full path to a executable file.
This warning is not important. It just fills up the issues log on the build summary page. Please remove it.

It's fixed in the 2.x agent.


Adapt argument parser, add fastq2fasta conversion

Adapt argument parser, so positional argument, optional argument and a flag is used. Plus use arguments by implementing a fastq2fasta conversion.

Probably the api test will fail after removal of the give_me_five. You can either remove the test or replace it with a tiny new one for the converter.

What kind of small test do you want me to write? Can I store a small fastq file (like two seqs of length 15 or something like that) in data and can I put the output there as well? Or do you want me to store the output file in a tmp dir?

I see it's a bit tricky, because the only function of the application needs file paths.
Yes, it's a good idea to have a little fastq file in the test/data/ directory that can be read. As there is a branch in the function we need two tests: with out.empty() either true or false. You can define the expected output as a string and then use (1) a tempfile to write into (example) and (2) capture stdout (example).