[Snyk] Upgrade yargs from 17.0.0 to 17.5.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade yargs from 17.0.0 to 17.5.1.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 15 versions ahead of your current version.
The recommended version was released a month ago, on 2022-05-16.

Release notes

Package name: yargs

17.5.1 - 2022-05-1617.5.1 (2022-05-16)
Bug Fixes

add missing entries to published files (#2185) (5685382)
address bug when strict and async middleware used together (#2164) (cbc2eb7)
completion: correct zsh installation instructions (22e9af2)
handle multiple node_modules folders determining mainFilename for ESM (#2123) (e0823dd)
lang: add missing terms to Russian translation (#2181) (1c331f2)
prevent infinite loop with empty locale (#2179) (b672e70)
veriadic arguments override array provided in config (the same as multiple dash arguments). (4dac5b8)

17.5.0 - 2022-05-1117.5.0 (2022-05-11)
Features

add browser.d.ts and check for existence of Error.captureStackTrace() (#2144) (6192990)

Bug Fixes

completion: support for default flags (db35423)
import yargs/yargs in esm projects (#2151) (95aed1c)

17.4.1 - 2022-04-0917.4.1 (2022-04-09)
Bug Fixes

coerce pollutes argv (#2161) (2d1136d)
completion: don't show positional args choices with option choices (#2148) (b58b5bc)
hide hidden options from completion (#2143) (e086dfa), closes #2142
show message when showHelpOnFail is chained globally (#2154) (ad9fcac)

17.4.0 - 2022-03-1917.4.0 (2022-03-19)
Features

completion: choices will now work for all possible aliases of an option and not just the default long option (30edd50)
completion: positional arguments completion (#2090) (00e4ebb)

Bug Fixes

completion: changed the check for option arguments to match options that begin with '-', instead of '--', to include short options (30edd50)
completion: fix for completions that contain non-leading hyphens (30edd50)
failed command usage string is missing arg descriptions and optional args (#2105) (d6e342d)
wrap unknown args in quotes (#2092) (6a29778)

17.3.1 - 2021-12-2317.3.1 (2021-12-23)
Bug Fixes

translations: correct Korean translation (#2095) (c7c2b9e)

17.3.0 - 2021-11-30

17.2.1 - 2021-09-25

17.2.0 - 2021-09-23

17.1.1 - 2021-08-13

17.1.1-candidate.0 - 2021-08-13

17.1.0 - 2021-08-04

17.1.0-candidate.0 - 2021-07-15

17.0.2-candidate.1 - 2021-07-15

17.0.2-candidate - 2021-07-10

17.0.1 - 2021-05-03

17.0.0 - 2021-05-02

    from yargs GitHub release notes

Commit messages

Package name: yargs

850a181 chore: v17.5.1 release
0251511 chore(main): release 17.5.1 (#2187)
22e9af2 fix(completion): correct zsh installation instructions
cbc2eb7 fix: address bug when strict and async middleware used together (#2164)
8912078 refactor: use prototype (#2165)
1c331f2 fix(lang): add missing terms to Russian translation (#2181)
2109bd6 refactor: make isDefaulted private (#2188)
b672e70 fix: prevent infinite loop with empty locale (#2179)
4dac5b8 fix: passed arguments should take precedence over values in config (#2100)
e0823dd fix: handle multiple node_modules folders determining mainFilename for ESM (#2123)
b42e0ca test: remove console.log (#2157)
5685382 fix: add missing entries to published files (#2185)
fcb4d38 chore(main): release 17.5.0 (#2184)
7e85096 Revert "chore: Set permissions for GitHub actions (#2168)" (#2183)
95aed1c fix: import yargs/yargs in esm projects (#2151)
db35423 fix(completion): support for default flags
6192990 feat: add browser.d.ts and check for existence of Error.captureStackTrace() (#2144)
d9fa18c chore: Set permissions for GitHub actions (#2168)
be52515 chore(main): release 17.4.1 (#2147)
2d1136d fix: coerce pollutes argv (#2161)
ad9fcac fix: show message when showHelpOnFail is chained globally (#2154)
b58b5bc fix(completion): don't show positional args choices with option choices (#2148)
0bb49c3 samples: event.keyCode is deprecated, use new `.code` API (#2125)
e086dfa fix: hide hidden options from completion (#2143)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Coverage remained the same at 47.814% when pulling 91dbc8c02ecf78e4dc2bdb8589a34597c020fb7c on snyk-upgrade-0066c03bc8e885948b7146350994d7d6 into 91232ab3b575309b2c06fc63a363347da5713739 on master.


[WIP] Add basic tests for ONNX module

This is a draft PR for the Tests.
Some ONNX Models were not complete e.g Lenet, so I used ResNet instead.
The Transpose class was also incomplete so I could not Test it.
I would like to know how do you generate input data for the Transpose class.
I will appreciate your feedback on the tests and anything that I may add, thanks

I'll do the review this week I comment the proposed draft

It's outdated and probably we don't need these tests for now


Fix missing example project link on Core Dep Management Doc in User Manual

Fixes https://github.com/gradle/gradle/issues/20640
This is a Documentation change ONLY.
Context
This is an improvement upon the What is Dependency Management? section of the Gradle User Manual (specifically core_dependency_management.adoc)

Cleaned up syntax and grammatical errors
Updated diagram and image for branding
Made everything single line
Added links where appropriate
Added a snippet example

@bot-gradle test

I've triggered the following builds for you:

@bot-gradle test and merge

I've triggered a build for you.

Pre-tested commit build failed.

@lkasso FYI there is a mismatch between the milestone and the target branch. Valid values are:

release -> 8.2 RC1
master -> 8.3 RC1

Fixed.

I've triggered the following builds for you:

BuildDistributions build

@bot-gradle test

I've triggered the following builds for you:

I've triggered the following builds for you:

BuildDistributions build

Your PR is queued. See the queue page for details.

I've triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

I've triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

I've triggered a build for you.

Pre-tested commit build failed.

Your PR is queued. See the queue page for details.

@bot-gradle test and merge

I've triggered a build for you.


Does eventing-natss support event source

Should we support event source in eventing-nats like other event sources?

cc @zhaojizhuang

/good-first-issue cc @vaikas @n3wscott @mattmoor

/kind good-first-issue

It is maybe not a good first issue, but yeah we should.

@n3wscott When will we achieve this?

Hello everyone, any updates on the NATS as a K-Native Event Source?
I happen to found this example https://camel.apache.org/camel-kamelets/latest/nats-source.html based on KameletBinding (Camel-K, Apache Camel) and even after following everything with the setup, the KameletBinding always stays in the Error State.
Any leads or support would mean a lot. Cheers!


[l10n] Fix Czech BCP47 in documentation

[x] I have followed (at least) the PR section of the contributing guide.

Thanks for the follow-up.


Modifier parsing bug fix

Currently petite-vue only parses the first modifier in a sequence. The original line 126 in walk.ts slices the string right after the first modifier is set and thus the while loop never continues.

Thanks for the fix! I managed to make it simpler in 15f75e9


Small nits: punctuation changes

Mostly just removing unnecessary commas.

No problem. Thanks for the hard work!
On Mon, Mar 6, 2023, 01:25 Stefan Höck @.***> wrote:

Merged #54 https://github.com/stefan-hoeck/idris2-tutorial/pull/54 into
main.
—
Reply to this email directly, view it on GitHub
https://github.com/stefan-hoeck/idris2-tutorial/pull/54#event-8671922766,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAC3W5EKI52N64XWJDLBQ3W2WUQNANCNFSM6AAAAAAVQOYKUU
.
You are receiving this because you authored the thread.Message ID:
@.***>


New version: Microsoft.ServiceFabricRuntime version 9.1.1583.9590

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

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

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

Manual validation found numerous executables.


Remove initial time from interface functions

LGTM, I am not clear still on what is the usage for get_time_series multiple

I think it is a very helpful debug/interactive function, especially when called on the system.


Don't reexport RenderArgs and UpdateArgs

piston::event::RenderArgs is good enough.

Event and Events can also be under piston::event.


poeditor init command should generate the yml file including the api token

currently token in the generated yml is blank. If it was passed to the command, the token should be written to the file.

implemented now


No report generated if skipClusterDelete is true

What happened:
We're using our own preconfigured kind cluster to run test.
No test report is generated when skipClusterDelete flag is set to true.
The only way to get a report is to set skipClusterDelete to false
What you expected to happen:
Test report should always be generated when reportFormat is set, no matter the skipClusterDelete flag value.
How to reproduce it (as minimally and precisely as possible):
Using the following kutt-test.yaml config file:
apiVersion: kuttl.dev/v1beta1
kind: TestSuite
startKIND: false
kindContext: e2e-tests
skipClusterDelete: true
testDirs:
- tests/
timeout: 600
namespace: default
reportFormat: JSON
parallel: 1

Run one of the test in testDirs with the following command:
kubectl kuttl test --test mytest

No kuttl-test.json file is generated
Anything else we need to know?:
Report is not generated because of the return statement in the h.TestSuite.SkipClusterDelete condition: https://github.com/kudobuilder/kuttl/blob/d2cd0d5ec86a758ca4a13db032a89ae214d3d524/pkg/test/harness.go#L551
Environment:

Kubernetes version (use kubectl version): v1.20.8
KUTTL version (use kubectl kuttl version): 0.11.1
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release): Fedora
Kernel (e.g. uname -a): 5.12.7-200
Install tools:
Others:

Thank you so much for these report...  apologies in the delay


rebasing ocs-ci

ocs-ci is rebased and tested.


The pre-request and training process

I appreciate the great work @xiamengzhou, but sorry that I cannot clearly understand the training process.
q1) could you specify the versions of packages, e.g. datasets, transformers, etc.?
q2) can I get the fine-tuned original BERT by running run_FT.sh with the specification of 'proj_dir' only?

Hi, it should be compatible with transformers==4.3.2 and datasets==1.3.0 but might work with versions beyond.


#202 upgrade to junit 5

PR Checklist

[ ] A description of the changes is added to the description of this PR.
[ ] If there is a related issue, make sure it is linked to this PR.
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added or modified a feature, documentation in docs is updated

Description of changes

made changes from greatly outdated main branch 😞


Comma is not supporting  for exporting named scopes in rails 3

I have following code in my controller
my_controller
def export
@variables = Model.scope
respond_to do |format|
format.html # export.html.haml
format.csv do
send_data(@variables.to_comma(:brief))
end
end

Closing as duplicate of #10


[WIP] Proposal for text selection programmatically

Description
This PR add support for text selection programmatically for the SelectableText widget.
See design doc.
Related Issues
Fixes https://github.com/flutter/flutter/issues/69460
Tests
TODO
Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I signed the [CLA].
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read [Handling breaking changes].

[x] No, no existing tests failed, so this is not a breaking change.

Hi @pedromassango, this has not been updated in a while, and is not in a state for code review, so I am going to close it for now. If you would like to come back and continue working on it, feel free to re-open! thanks!


Modify mod_header, support REQ_COOKIE_ADD and RSP_COOKIE_DEL

Codecov Report

Merging #257 into develop will increase coverage by 0.13%.
The diff coverage is 84.69%.

@@             Coverage Diff             @@
##           develop     #257      +/-   ##
===========================================
+ Coverage     52.5%   52.64%   +0.13%
===========================================
  Files          227      228       +1
  Lines        22172    22250      +78
===========================================
+ Hits         11641    11713      +72
- Misses        9211     9216       +5
- Partials      1320     1321       +1

Impacted Files
Coverage Δ

bfe_modules/mod_header/conf_mod_header.go
75% <ø> (-2.78%)
:arrow_down:

bfe_modules/mod_header/mod_header.go
75% <100%> (+9.72%)
:arrow_up:

bfe_modules/mod_header/action.go
60.19% <50%> (+0.61%)
:arrow_up:

bfe_modules/mod_header/action_cookie.go
82.22% <82.22%> (ø)

bfe_modules/mod_header/header_rule_load.go
68.37% <90.9%> (ø)

bfe_util/fixed_pool.go
83.33% <0%> (-16.67%)
:arrow_down:

bfe_spdy/server_conn.go
77.65% <0%> (-1.33%)
:arrow_down:

bfe_modules/mod_static/mod_static.go
77.46% <0%> (+0.48%)
:arrow_up:

... and 5 more

Continue to review full report at Codecov.

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


Feature Request: Native support on annotationProcessor Gradle Task

Hi bluelinelabs - If you can have this compatible with annotationProcessor as well aside from the apt plugin, it can reduce the dependency on additional 3rd party plugin for the annotation processing natively supported on Android N.
Here's the setup to validate the support:
parent build.gradle should be using
classpath 'com.android.tools.build:gradle:2.2.0-alpha1'
The following line is removed on the application build.gradle
apply plugin: 'com.neenbedankt.android-apt'
Thanks.

The annotationProcessor configuration is compatible with the libraries you used to pull in via android-apt by default and without any required additional work from our side. So, if you like, you can simply change your project to using that configuration, enable Jack, and you're good to go!

Thanks. I'll check and see if there won't be nullified instances. I've reported on Butterknife that the instances on their end are null when using annotationProcessor.

Interesting... I conducted a small example project earlier, just to verify that it still works with the latest plugin version, and it did. Make sure you're up to 2.2.0-alpha3 though, maybe that was the issue with ButterKnife?

You can track the progress of the JACK compiler annotation processor support in the AOSP issue tracker #204065.

Thanks. The new alpha version did it ;)

The new 'com.android.tools.build:gradle:2.2.0-alpha6' addresses the issue. We can close this. Thanks.


How to use the controller?

I am also facing the same issue... There is neither documentation nor example speaking about controller and onchanged function!!!


[Feature Request] Intergrate the new PatchFusion Depth Estimation Model into this project.

The Detail they have achieved looks very impressive, would it be possible to use this model in Automatic1111? :
https://github.com/zhyever/PatchFusion

Is it better than BOOST?

Very Impressive! The hugging faces repo suggests it requires a large amount of VRAM, they suggest 24g. But the results look very good. This might be a more challenging integration.

Ok, then who knows, maybe one day. If somebody can create a MR for this would be a pleasure to integrate. This would require refactoring is_boost boolean type of thing into patching enum kind of thing, with options [no, BOOST, PatchFusion] or something like this. The same for the UI.

It looks like it uses midas, zoedepth, stable diffusion, and controlnet without offload vram though soo it should be possible to significantly reduce the requirement.

Wait, it uses all these things at the same time?


No way to describe operator precedence to assertMacroExpansion

Description
It doesn't seem possible to write tests for macros that visit InfixOperatorExprSyntax. This includes the "add blocker" example from swift-macro-examples.
Steps to Reproduce

Try to write a macro test for: https://github.com/DougGregor/swift-macro-examples/blob/66ded9b2774c06c5a51254b0640a456ef1055a68/MacroExamplesPlugin/AddBlocker.swift
The AddVisitor never visits the node because the node doesn't exist in the test run.

Tracked in Apple’s issue tracker as rdar://114786803

My assumption is:

[ ] The parsed source should be folded using the standard operators defined in the SwiftOperators module
[ ] There may need to be an option to provide custom operators

Thanks for the bug report. I’m fixing it in https://github.com/apple/swift-syntax/pull/2132.
We don’t need an option to provide custom operators in assertMacroExpansion yet because the compiler also only folds operators using the standard operator table. Once the compiler gains support for folding of custom operators, we need to an option to specify a custom operator table in assertMacroExpansion.


dYdX - Upgrade the connector to v4

Description
Objective:
Upgrade the dYdX Connector to the latest standart v4. The connector should meet Hummingbot connector standarts https://hummingbot.org/developers/connectors/perp-connector-checklist/
and Contribution Guidelines
https://hummingbot.org/developers/contributions/
Submission: To submit your proposal, please provide details of your experience, approach to the upgrade, estimated timeline, and any relevant past projects or contributions.
Selection Criteria: Submissions will be evaluated based on technical expertise, experience with blockchain development, understanding of the dYdX protocol, proposed timeline.
For the mention here:
https://dydx.exchange/blog/v4-technical-architecture-overview
https://dydx.exchange/blog?#v4
Bounty

Sponsor: HB foundation (dYdX connector pots)
Bounty amount: 700K HBOT
Developer portion: 4000 USDC or 630K HBOT

I would like to be assigned this ticket

Assigned to @yancong001, please be informed:

Since you’re assigned to this bounty exclusively, please keep us informed on your progress over the next few days
Please review and follow contribution guidelines (https://hummingbot.org/developers/contributions/)
Please review the checklist after PR submitted (https://hummingbot.org/developers/contributions/#checklist)
Let us know if you don’t have time, and we will unassigned and keep it open for other devs
Only one dev can be assigned to one bounty

Thanks for your contribution!

@yancong001
Currently there's a new bounty process.
Assigned developer should choose bounty amount (from advised) when dev assigned, please specify with comment below 4000 USDC or 630K HBOT

i prefer 630K HBOT

Hello @yancong001, Please add your updates on this bounty here

I'm halfway there. I'll submit the code this week.

hi,nikspz
I had some problems with the method dydx placed and canceled orders, which caused me to interrupt the process.

The official recommendation is to use the v4-client-py library, but they removed it some time ago (it is no longer installed). I tried to find the answer from a third-party library, but the process ran into difficulties.

I was just talking to fede about that

The official recommendation is to use the v4-client-py library, but they removed it some time ago (it is no longer installed). I tried to find the answer from a third-party library, but the process ran into difficulties.

I was just talking to fede about that

@yancong001 We asked dYdX and this was their reply:
We don't have an official python client and we are pointing people to the 3rd party forked client
https://twitter.com/LawrenceChiu14/status/1756111223509106831
Also, please take a look at these guides

setup https://docs.google.com/document/d/1ZbVRpAjwdmJ4IOIU6QN0l0jt2sD8f4xGhE3RoCukkFc/edit?usp=sharing
user manual https://docs.google.com/document/d/13aZz9o4g0WyLrteelBYDUOUmzJgOaPouVwRrF0kn-to/edit?usp=sharing

Let me know your Telegram handle and I'll add you to the group for easier communication

got it , i will continue

hi @yancong001 Could you please add your updates / progress info for dydx to v4 bounty here

I am 80% done and I will submit the code in a few days

here https://github.com/hummingbot/hummingbot/pull/6987

This is my test script
from hummingbot.core.data_type.common import OrderType, PositionAction, PositionMode, PositionSide, TradeType

from hummingbot.client.hummingbot_application import HummingbotApplication
from hummingbot.core.data_type.common import OrderType
from hummingbot.strategy.script_strategy_base import ScriptStrategyBase
from decimal import Decimal

class TestLimitOrders(ScriptStrategyBase):
    """
    This is a simple script strategy that buys 0.01 ETH at market price, then sells it at market price.
    The objective is to test the market order functionality of the Binance connector.
    """
    trading_pair = "TRX-USD"
    order_amount = Decimal("100")
    markets = {"dydx_v4_perpetual":{trading_pair}}
    buy_order_id = None
    sell_order_id = None

    def tick(self, timestamp: float):
        """
        Clock tick entry point, is run every second (on normal tick setting).
        Checks if all connectors are ready, if so the strategy is ready to trade.

        :param timestamp: current tick timestamp
        """
        if not self.ready_to_trade:
            self.ready_to_trade = all(ex.ready for ex in self.connectors.values())
            if not self.ready_to_trade:
                for con in [c for c in self.connectors.values() if not c.ready]:
                    print(con.status_dict)
                    self.logger().warning(f"{con.name} is not ready. Please wait...")
                return
        else:
            self.on_tick()
    def on_tick(self):
        if not self.buy_order_id:
            self.buy_order_id = self.connectors["dydx_v4_perpetual"].buy(
                trading_pair=self.trading_pair,
                amount=self.order_amount,
                price=Decimal("0.11"),
                position_action=PositionAction.OPEN,
                order_type=OrderType.LIMIT)
        HummingbotApplication.main_application().stop()

I found the problem.
dydx v4‘s library "v4-proto" and injective's "injective-py" conflict with each other.

At present, orders can be successfully placed when injective connector is removed, but there are still some problems in canceling orders, which I am working on.
Now we need to consider whether not to load injective connector (paper_trade) when hummingbot_appliaction starts.

Now we need to consider whether not to load injective connector (paper_trade) when hummingbot_appliaction starts.

Actually, I just merged in a PR to development that removes InjectiveV2 as a default paper trading connector, so it shouldn't be loaded upon startup anymore. Does that solve the issue?

I noticed that injective is still loaded at this point in the picture, which still causes conflict. @fengtality
With injective_v2 removed（”rm -rf hummingbot/connector/exchange/injective_v2/“, dydx_v4 can now be tested. @nikspz

@yancong001 I am working on a conda v4-proto/v4-client recipe, it would be great if you can integrte it to the environment.yml (instead of pypi) when it is published on conda-forge

The injective SDK is also on conda-forge, that could possibly highlight conflicts at the environment installation instead (there he goes again with his conda rant)

@yancong001 I am working on a conda v4-proto/v4-client recipe, it would be great if you can integrte it to the environment.yml (instead of pypi) when it is published on conda-forge

ok, i can integrte it

The injective SDK is also on conda-forge, that could possibly highlight conflicts at the environment installation instead (there he goes again with his conda rant)

Let me know when you're done

Sure, I will. Are you actually using it (I have not looked at your PR)?
Currently, I have the node-service-base-dev and the v4-proto (Python/JS) in staged-recipe:
https://github.com/conda-forge/staged-recipes/pull/27037
https://github.com/conda-forge/staged-recipes/pull/27076
So, it will depends upon when they get reviewed and approved (I still struggle with the JS installation on windows)
I have the v4-client almost ready and pending both proto and node-service-base-dev
I don't really want to separate the python from the JS/CPP, but if you need it, I could reconsider

Thanks for your participation, the bounty has been sent to @yancong001 . The fix has been deployed on development branch and hummingbot version 2.0.1


[Blazor p8] OnInitializedAsync is executed for twice on pre-render

Issue
OnInitializedAsync is executed for twice when page has been served as  "pre-render".
Version
[dani@localhost tw]$ dotnet --version
3.0.100-preview8-013656

Steps to reproduce and screen shots:
@page "/"
@inject IUriHelper UriHelper

Hello, world!

Welcome to your new app.

@code{

    protected async override Task OnInitializedAsync()
    {
        System.Console.WriteLine("_*   ");
        System.Console.WriteLine("_**************************");
        System.Console.WriteLine("_***** Pre render ******");
        System.Console.WriteLine("_**************************");
        System.Console.WriteLine("_   ");
        return;
    }
}

And I see is executed for twice only on pre-render:

Has it some explanation?
The question on stackoverfow: Blazor UriHelper.NavigateTo is calling the page twice

Related: https://github.com/aspnet/AspNetCore/issues/13172

Thanks for contacting us, @ctrl-alt-d.
We did change the behavior in this area in Preview9.

Hi,
I'm having the same issue but only as I publish my app to Azure App Services. If I switch RenderMode to Server then it gets called only once but then contextAccessor.HttpContext is null when injected into my service class.
On my localhost it works fine in both cases..
Am I doing something wrong here?


some minor cleaning

deprecates a part of #12

We're currently processing your upload.  This comment will be updated when the results are available.


Support for not hidden salesforcedx.yml

salesforcedx.yml is an important project file.  Let's not hide.
To support existing .salesforcedx.yml, we could look for salesforcedx.yml then .salesforcedx.yml.

I propose we replace this issue with https://github.com/wadewegner/salesforce-dx-buildpack/issues/5. I think sfdx.yml is better than salesforcedx.yml, and if we're going to rename it I'd rather do it once.


transport: http2Server.HandleStreams failed to read frame: read tcp [::1]:50051->[::1]:58751: wsarecv: An existing connection was forcibly closed by the remote host.

transport: http2Server.HandleStreams failed to read frame: read tcp [::1]:50051->[::1]:58751: wsarecv: An existing connection was forcibly closed by the remote host.
How does it happen?

Same error.
But only on the first minute, after some times requests on services don't generate this error anymore ??

We are cleaning up the gRPC issue backlog and are unable to address this issue with the current information. If you are still experiencing this issue, please re-open the issue with information on how to reproduce. (If your issue is specifically related to Go or Java implementations, please file an issue on the respective repositories.)


Handling of large FLAC files smaller than 300 MB

Hi James, now skipping of large FALC files works as expected, but now when YTMusicUploader tries to upload a full album FLAC file around 220 MB, it gets an upload error from google and it tries again, again and again..., so we are back in a loop. Maybe you should implemet something like: If the upload fails for a certain number of times, skip the file. It could be desirable to limit this behavior to FLAC files only or in general to files larger than 100MB. Just an idea.

Hey,
You've  highlighted a very good idea!
The initial reasoning behind the looping when it encounters errors was to battle YTMusic's occasional  '500' error, in the expectation that the file would eventually get uploaded. This obviously isn't the case for certain files that YT Music doesn't like.
I've implemented your suggestion... The application will still give a failed upload a few tries, and retry once more after the batch has batch has complete, but then won't keep trying.
Let's see how we get on with the new version here: https://github.com/jamesbrindle/YTMusicUploader/releases/tag/v1.5.2
I found a good few bugs this time while digging into the code after not seeing it for a few weeks... Typically trying to solve one issue while creating another. Lets hope this version is better.
More details below:
Retry on MainProcess When Issues Are Present

When there are issues when uploading and the 'Issue' counter increments, then when all the uploads have finished, the application will once again try to upload the file it had an issue with previously in an attempt to work around YT Music's mysterious '500' error.

Unfortunately this ends up looping for quite some time if not forever, and the application never ends up in an 'idle' state. Therefore a limit of '1' has been put in place for how many times the application will loop through its issues on in the main application process (not to be confused with the n/5 attempts to upload while uploading is taking place which will remain the same).

We do however want to retry the the failed upload at some point, for the following reasons:

YT Music may fix an issue at their end for 500'd-ing certain files
We may re-encode or compress the file and want to retry it

Therefore, the file will once again attempt to upload in 30 days, or if the 'Issue' state of the file is reset via the 'Issues' report form.

Presumed OK now

Presumed OK now


SetBackground does not work together with ToLightTheme

In my WP8 app I use the ToLightTheme to have light theme in my app no matter what color scheme is set by the user. I also use the SetBackground method for setting light blue color as a Frame background color.
The problem is if user has while theme selected, then my custom background color is not applied, probably because the Theme Manager thinks that ToLightTheme does not need to be applied if white theme is already on.
If SetBackground is used, it should not be ignored in ToLightTheme or ToDarkTheme methods.

:+1:


onCancel is fired after onConfirm event on Android

The onCancel event is being fired after the onConfirm event on Android, iOS is fine.

me to also same issue

https://github.com/mmazzarolo/react-native-modal-datetime-picker/assets/70627522/c1f0d448-8819-4442-ac14-e20d78547dcd


Service principal is missing in az ad group owner list after upgrade to 2.37

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az ad group owner list
Errors:
Missing service principal as owner after upgrade to azcli 2.37+
$ az ad group owner list --group c40d6c92-ebf1-46ee-9fd1-99685b281394 --out tsv --query '[].[mail,id]'
<EMAIL_ADDRESS>      7addc286-717c-4590-9ec9-4559d41725f9
<EMAIL_ADDRESS>      c2ddd1d1-8ae8-42e6-aef4-2d7dd44bce65
<EMAIL_ADDRESS>      07930e5c-a4fd-4365-a817-1fb436d7c5c3
<EMAIL_ADDRESS>      aa62e803-6966-4dff-b7f0-0772bf76b0c9
<EMAIL_ADDRESS>      df2f9469-acc3-4bf9-993e-dfa6872903fe

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Authenticate to azure subscription
install azcli 2.37 or higher (includes Microsoft Graph API migration)
az ad group owner list --group ExampleGroup

Expected Behavior
Service principal is display as owner before 2.37
$ az ad group owner list --group c40d6c92-ebf1-46ee-9fd1-99685b281394 --out tsv --query '[].[mail,objectId]'
<EMAIL_ADDRESS>      7addc286-717c-4590-9ec9-4559d41725f9
<EMAIL_ADDRESS>      c2ddd1d1-8ae8-42e6-aef4-2d7dd44bce65
<EMAIL_ADDRESS>      07930e5c-a4fd-4365-a817-1fb436d7c5c3
<EMAIL_ADDRESS>      aa62e803-6966-4dff-b7f0-0772bf76b0c9
<EMAIL_ADDRESS>      df2f9469-acc3-4bf9-993e-dfa6872903fe
None    1d0bb3be-f638-4b53-ac11-4ddd39e0d990

$ az version
{
  "azure-cli": "2.32.0",
  "azure-cli-core": "2.32.0",
  "azure-cli-telemetry": "1.0.6",
  "extensions": {
    "account": "0.2.2",
    "alertsmanagement": "0.2.2",
    "log-analytics": "0.2.2",
    "monitor-control-service": "0.3.0",
    "resource-graph": "2.1.0",
    "scheduled-query": "0.5.0"
  }
}

Environment Summary
Linux-4.4.0-19041-Microsoft-x86_64-with-glibc2.29, Ubuntu 20.04.4 LTS
Python 3.8.10
Installer: PIP

azure-cli 2.40.0

Extensions:
account 0.2.3
alertsmanagement 0.2.2
log-analytics 0.2.2
monitor-control-service 0.3.0
resource-graph 2.1.0
scheduled-query 0.5.1

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

Group owners as display in azure portal

@jiasli for awareness

@jiasli @yonzhan Could you confirm that it's a bug and not something I missed ?

Guys ? Any news, at least an answer if this is a bug or not.

Similar to https://github.com/Azure/azure-cli/issues/22664
According to List group owners API's documentation:
https://learn.microsoft.com/en-us/graph/api/group-list-owners?view=graph-rest-1.0&tabs=http

Note: Currently, service principals are not listed as group owners due to the staged rollout of service principals to the Microsoft Graph v1.0 endpoint.

This is a feature gap between AD Graph and Microsoft Graph. az ad group owner list internally calls that API.
As a workaround, you may try using az rest to call beta API: https://learn.microsoft.com/en-us/graph/api/group-list-owners?view=graph-rest-beta&tabs=http (though I haven't verified that myself)

@jiasli Thank you for the workaround, it's indeed working fine, I'm going to go with that while the bug is fix
$ az rest --method get --url https://graph.microsoft.com/beta/groups/c40d6c92-ebf1-46ee-9fd1-99685b281394/owners | jq -r ".value | .[] | [.mail,.id] | @tsv"
<EMAIL_ADDRESS>   7addc286-717c-4590-9ec9-4559d41725f9
<EMAIL_ADDRESS>c2ddd1d1-8ae8-42e6-aef4-2d7dd44bce65
                                07930e5c-a4fd-4365-a817-1fb436d7c5c3
<EMAIL_ADDRESS>      aa62e803-6966-4dff-b7f0-0772bf76b0c9

versus
$ az ad group owner list -g c40d6c92-ebf1-46ee-9fd1-99685b281394 --out tsv --query '[].[mail,id]'
<EMAIL_ADDRESS>   7addc286-717c-4590-9ec9-4559d41725f9
<EMAIL_ADDRESS>c2ddd1d1-8ae8-42e6-aef4-2d7dd44bce65
<EMAIL_ADDRESS>      aa62e803-6966-4dff-b7f0-0772bf76b0c9

Yup looks like #22664 has regressed somehow

Nearly 2 years on and this still doesn't work - is there any plan to fix this?


Run LowerAffine before LinalgStrategyVectorize

The "TileAndDistributeToWorkgroups" can introduce affine.apply ops into linalg.generic, which then prevents vectorization. One simply solution is to run the "LowerAffine" pass before vectorization.
Here's a simple reproducer:
module {
  func.func @piecewise_linear(%arg0: tensor<80x16xf32>) -> tensor<80x16xf32> {
    %0 = tensor.empty() : tensor<80x16xf32>
    %1 = linalg.generic {indexing_maps = [#map], iterator_types = ["parallel", "parallel"]} outs(%0 : tensor<80x16xf32>) {
    ^bb0(%out: f32):
      %2 = linalg.index 0 : index
      %3 = linalg.index 1 : index
      %extracted = tensor.extract %arg0[%2, %3] : tensor<80x16xf32>
      linalg.yield %extracted : f32
    } -> tensor<80x16xf32>
    return %1 : tensor<80x16xf32>
  }
}

To compile:
iree-compile \
  --iree-llvm-target-triple=aarch64-none-linux-gnu \
  --iree-hal-target-backends=llvm-cpu \
  --iree-llvm-slp-vectorization \
  --iree-llvm-loop-vectorization \
  --iree-llvm-loop-unrolling \
  --iree-llvm-loop-interleaving \
  --iree-llvm-link-embedded=false \
  --iree-input-type=tosa \
  <file.mlir>

Fixes https://github.com/iree-org/iree/issues/10876

I'm cleaning the PR that needs my review. Do we still need the PR or we can close it?

Do we still need the PR or we can close it?

No.  This was effectively implemented in https://reviews.llvm.org/D143429.


Documentation on loading data is wrong

Table isn't an iterator anymore, so [row for row in table] doesn't work. It has to be table.readrow().

@vitorbaptista
Do you use the latest version?

Ops, sorry! My mistake :+1:


Memory and High CPU Usage

I was working on the Tesla package and went to sleep. When I resumed work, I noticed that my computer was almost unresponsive. The extension had consumed all available RAM and spiked the CPU.
This is not the first time it has happened; just that this time, I didn't close it or click on the extension's notification complaining about compilation errors or something else.
Environment

Elixir & Erlang versions: Elixir 1.16.2, Erlang/OTP 26
VSCode ElixirLS version: v0.20.0
Operating System Version: macOS 14.2.1 (Intel)

Troubleshooting

[x] Restart your editor (which will restart ElixirLS) sometimes, fixes issues
[x] Stop your editor, remove the entire .elixir_ls directory, then restart your editor

Crash report template

View Logs
```
[Info  - 12:20:25 AM] Compile took 6920 milliseconds
[Info  - 12:20:25 AM] [ElixirLS WorkspaceSymbols] Updating index...
[Info  - 12:20:25 AM] Starting build with MIX_ENV: test MIX_TARGET: host
[Info  - 12:20:25 AM] [ElixirLS WorkspaceSymbols] 1 modules need reindexing
[Info  - 12:20:25 AM] [ElixirLS WorkspaceSymbols] 2 symbols added to index in 25ms
[Info  - 12:20:32 AM] Compile took 6413 milliseconds
[Info  - 12:20:32 AM] [ElixirLS Dialyzer] Checking for stale beam files
[Info  - 12:20:32 AM] [ElixirLS Dialyzer] Found 1 changed files in 76 milliseconds
[Info  - 12:20:32 AM] [ElixirLS Dialyzer] Analyzing 1 modules: [Tesla.AdapterCase.SSL]
[Info  - 12:20:33 AM] [ElixirLS Dialyzer] Analysis finished in 449 milliseconds
[Info  - 12:20:33 AM] Dialyzer analysis is up to date
[Info  - 12:20:33 AM] Success typings computed in 88ms
[Info  - 12:20:34 AM] [ElixirLS Dialyzer] Writing manifest...
[Info  - 12:20:34 AM] Success typings computed in 46ms
[Info  - 12:20:35 AM] [ElixirLS Dialyzer] Done writing manifest in 1863 milliseconds.
[Info  - 12:20:41 AM] Starting build with MIX_ENV: test MIX_TARGET: host
Compiling 1 file (.ex)
[Info  - 12:20:46 AM] Compile took 5173 milliseconds
[Info  - 12:20:46 AM] [ElixirLS WorkspaceSymbols] Updating index...
[Info  - 12:20:46 AM] [ElixirLS WorkspaceSymbols] 1 modules need reindexing
[Info  - 12:20:46 AM] [ElixirLS WorkspaceSymbols] 2 symbols added to index in 1ms
[Info  - 12:20:46 AM] [ElixirLS Dialyzer] Checking for stale beam files
[Info  - 12:20:46 AM] [ElixirLS Dialyzer] Found 1 changed files in 69 milliseconds
[Info  - 12:20:46 AM] [ElixirLS Dialyzer] Analyzing 1 modules: [Tesla.AdapterCase.SSL]
[Info  - 12:20:47 AM] [ElixirLS Dialyzer] Analysis finished in 373 milliseconds
[Info  - 12:20:47 AM] Dialyzer analysis is up to date
[Info  - 12:20:47 AM] Success typings computed in 76ms
[Info  - 12:20:47 AM] [ElixirLS Dialyzer] Writing manifest...
[Info  - 12:20:48 AM] [ElixirLS Dialyzer] Done writing manifest in 1558 milliseconds.
[Info  - 12:20:52 AM] Starting build with MIX_ENV: test MIX_TARGET: host
Compiling 1 file (.ex)
[Info  - 12:21:01 AM] Compile took 8649 milliseconds
[Info  - 12:21:01 AM] [ElixirLS WorkspaceSymbols] Updating index...
[Info  - 12:21:01 AM] [ElixirLS WorkspaceSymbols] 1 modules need reindexing
[Info  - 12:21:01 AM] [ElixirLS WorkspaceSymbols] 2 symbols added to index in 1ms
[Info  - 12:21:01 AM] [ElixirLS Dialyzer] Checking for stale beam files
[Info  - 12:21:01 AM] [ElixirLS Dialyzer] Found 1 changed files in 197 milliseconds
[Info  - 12:21:01 AM] [ElixirLS Dialyzer] Analyzing 1 modules: [Tesla.AdapterCase.SSL]
[Info  - 12:21:02 AM] [ElixirLS Dialyzer] Analysis finished in 429 milliseconds
[Info  - 12:21:02 AM] Dialyzer analysis is up to date
[Info  - 12:21:02 AM] Success typings computed in 92ms
[Info  - 12:21:03 AM] [ElixirLS Dialyzer] Writing manifest...
[Info  - 12:21:03 AM] Success typings computed in 62ms
[Info  - 12:21:04 AM] [ElixirLS Dialyzer] Done writing manifest in 1872 milliseconds.
Received $/cancelRequest for unknown request id: 2155
[Info  - 12:21:11 AM] Starting build with MIX_ENV: test MIX_TARGET: host
Compiling 1 file (.ex)
[Info  - 12:21:21 AM] Compile took 9616 milliseconds
[Info  - 12:21:21 AM] [ElixirLS WorkspaceSymbols] Updating index...
[Info  - 12:21:21 AM] [ElixirLS WorkspaceSymbols] 1 modules need reindexing
[Info  - 12:21:21 AM] [ElixirLS WorkspaceSymbols] 2 symbols added to index in 1ms
[Info  - 12:21:21 AM] [ElixirLS Dialyzer] Checking for stale beam files
[Info  - 12:21:21 AM] [ElixirLS Dialyzer] Found 1 changed files in 74 milliseconds
[Info  - 12:21:22 AM] [ElixirLS Dialyzer] Analyzing 1 modules: [Tesla.AdapterCase.SSL]
[Info  - 12:21:22 AM] [ElixirLS Dialyzer] Analysis finished in 396 milliseconds
[Info  - 12:21:22 AM] Dialyzer analysis is up to date
[Info  - 12:21:22 AM] Success typings computed in 75ms
[Info  - 12:21:22 AM] [ElixirLS Dialyzer] Writing manifest...
[Info  - 12:21:23 AM] [ElixirLS Dialyzer] Done writing manifest in 1416 milliseconds.
[Info  - 12:21:29 AM] Success typings computed in 136ms
[Info  - 12:21:41 AM] Starting build with MIX_ENV: test MIX_TARGET: host
Compiling 1 file (.ex)
[Info  - 12:21:48 AM] Compile took 6908 milliseconds
[Info  - 12:21:48 AM] [ElixirLS WorkspaceSymbols] Updating index...
[Info  - 12:21:48 AM] [ElixirLS WorkspaceSymbols] 1 modules need reindexing
[Info  - 12:21:48 AM] [ElixirLS WorkspaceSymbols] 2 symbols added to index in 1ms
[Info  - 12:21:48 AM] [ElixirLS Dialyzer] Checking for stale beam files
[Info  - 12:21:48 AM] [ElixirLS Dialyzer] Found 1 changed files in 143 milliseconds
[Info  - 12:21:48 AM] [ElixirLS Dialyzer] Analyzing 1 modules: [Tesla.AdapterCase.SSL]
[Info  - 12:21:49 AM] [ElixirLS Dialyzer] Analysis finished in 576 milliseconds
[Info  - 12:21:49 AM] Dialyzer analysis is up to date
[Info  - 12:21:49 AM] Success typings computed in 81ms
[Info  - 12:21:50 AM] [ElixirLS Dialyzer] Writing manifest...
[Info  - 12:21:50 AM] Success typings computed in 96ms
[Info  - 12:21:51 AM] [ElixirLS Dialyzer] Done writing manifest in 1615 milliseconds.
[Info  - 12:22:17 AM] Success typings computed in 59ms
[Info  - 12:22:23 AM] Starting build with MIX_ENV: test MIX_TARGET: host
Compiling 1 file (.ex)
[Info  - 12:22:30 AM] Compile took 6522 milliseconds
[Info  - 12:22:30 AM] [ElixirLS WorkspaceSymbols] Updating index...
[Info  - 12:22:30 AM] Starting build with MIX_ENV: test MIX_TARGET: host
[Info  - 12:22:30 AM] [ElixirLS WorkspaceSymbols] 1 modules need reindexing
[Info  - 12:22:30 AM] [ElixirLS WorkspaceSymbols] 2 symbols added to index in 2ms
[Info  - 12:22:36 AM] Compile took 5908 milliseconds
[Info  - 12:22:36 AM] [ElixirLS Dialyzer] Checking for stale beam files
[Info  - 12:22:36 AM] [ElixirLS Dialyzer] Found 1 changed files in 180 milliseconds
[Info  - 12:22:36 AM] [ElixirLS Dialyzer] Analyzing 1 modules: [Tesla.AdapterCase.SSL]
[Info  - 12:22:37 AM] [ElixirLS Dialyzer] Analysis finished in 386 milliseconds
[Info  - 12:22:37 AM] Dialyzer analysis is up to date
[Info  - 12:22:37 AM] Success typings computed in 80ms
[Info  - 12:22:37 AM] [ElixirLS Dialyzer] Writing manifest...
[Info  - 12:22:38 AM] Success typings computed in 111ms
[Info  - 12:22:38 AM] [ElixirLS Dialyzer] Done writing manifest in 1640 milliseconds.
[Info  - 12:22:47 AM] Success typings computed in 51ms
[Info  - 12:23:10 AM] Success typings computed in 195ms
[Info  - 12:23:16 AM] Starting build with MIX_ENV: test MIX_TARGET: host
Compiling 1 file (.ex)
[Info  - 12:23:23 AM] Compile took 6846 milliseconds
[Info  - 12:23:23 AM] [ElixirLS Dialyzer] Checking for stale beam files
[Info  - 12:23:23 AM] [ElixirLS WorkspaceSymbols] Updating index...
[Info  - 12:23:23 AM] [ElixirLS WorkspaceSymbols] 1 modules need reindexing
[Info  - 12:23:23 AM] [ElixirLS WorkspaceSymbols] 2 symbols added to index in 1ms
[Info  - 12:23:23 AM] [ElixirLS Dialyzer] Found 1 changed files in 71 milliseconds
[Info  - 12:23:24 AM] [ElixirLS Dialyzer] Analyzing 1 modules: [Tesla.AdapterCase.SSL]
[Info  - 12:23:24 AM] [ElixirLS Dialyzer] Analysis finished in 449 milliseconds
[Info  - 12:23:24 AM] Dialyzer analysis is up to date
[Info  - 12:23:24 AM] Success typings computed in 97ms
[Info  - 12:23:25 AM] [ElixirLS Dialyzer] Writing manifest...
[Info  - 12:23:26 AM] [ElixirLS Dialyzer] Done writing manifest in 1858 milliseconds.
[Info  - 12:24:25 AM] Success typings computed in 60ms
[Info  - 12:24:27 AM] Starting build with MIX_ENV: test MIX_TARGET: host
Compiling 1 file (.ex)
[Info  - 12:24:37 AM] Compile took 9439 milliseconds
[Info  - 12:24:37 AM] [ElixirLS WorkspaceSymbols] Updating index...
[Info  - 12:24:37 AM] Starting build with MIX_ENV: test MIX_TARGET: host
[Info  - 12:24:37 AM] [ElixirLS WorkspaceSymbols] 1 modules need reindexing
[Info  - 12:24:37 AM] [ElixirLS WorkspaceSymbols] 2 symbols added to index in 1ms
Received $/cancelRequest for unknown request id: 2272
[Info  - 12:24:47 AM] Compile took 9905 milliseconds
[Info  - 12:24:47 AM] [ElixirLS WorkspaceSymbols] Updating index...
[Info  - 12:24:47 AM] Starting build with MIX_ENV: test MIX_TARGET: host
[Info  - 12:24:47 AM] [ElixirLS WorkspaceSymbols] 0 modules need reindexing
[Info  - 12:24:47 AM] [ElixirLS WorkspaceSymbols] 0 symbols added to index in 0ms
[Info  - 12:24:58 AM] Compile took 11430 milliseconds
[Info  - 12:24:58 AM] [ElixirLS Dialyzer] Checking for stale beam files
[Info  - 12:24:59 AM] [ElixirLS Dialyzer] Found 1 changed files in 120 milliseconds
[Info  - 12:24:59 AM] [ElixirLS Dialyzer] Analyzing 1 modules: [Tesla.AdapterCase.SSL]
[Info  - 12:24:59 AM] [ElixirLS Dialyzer] Analysis finished in 433 milliseconds
[Info  - 12:24:59 AM] Dialyzer analysis is up to date
[Info  - 12:24:59 AM] Success typings computed in 116ms
[Info  - 12:25:00 AM] [ElixirLS Dialyzer] Writing manifest...
[Warn  - 12:25:00 AM]     warning: redefining module Tesla.Adapter.HttpcTest (current version defined in memory)
    │
  1 │ defmodule Tesla.Adapter.HttpcTest do
    │ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    │
    └─ test/tesla/adapter/httpc_test.exs:1: Tesla.Adapter.HttpcTest (module)
[Warn  - 12:25:01 AM]     warning: redefining module Tesla.Adapter.HttpcTest (current version defined in memory)
│
1 │ defmodule Tesla.Adapter.HttpcTest do
│ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
│
└─ test/tesla/adapter/httpc_test.exs:1: Tesla.Adapter.HttpcTest (module)
[Warn  - 12:25:01 AM]     warning: redefining module Tesla.Adapter.HttpcTest (current version defined in memory)
│
1 │ defmodule Tesla.Adapter.HttpcTest do
│ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
│
└─ test/tesla/adapter/httpc_test.exs:1: Tesla.Adapter.HttpcTest (module)
[Info  - 12:25:01 AM] [ElixirLS Dialyzer] Done writing manifest in 2000 milliseconds.
[Warn  - 12:25:01 AM]     warning: redefining module Tesla.Adapter.HttpcTest (current version defined in memory)
│
1 │ defmodule Tesla.Adapter.HttpcTest do
│ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
│
└─ test/tesla/adapter/httpc_test.exs:1: Tesla.Adapter.HttpcTest (module)
[Warn  - 12:25:02 AM]     warning: redefining module Tesla.Adapter.HttpcTest (current version defined in memory)
│
1 │ defmodule Tesla.Adapter.HttpcTest do
│ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
│
└─ test/tesla/adapter/httpc_test.exs:1: Tesla.Adapter.HttpcTest (module)
[Warn  - 12:25:03 AM]     warning: redefining module Tesla.Adapter.HttpcTest (current version defined in memory)
│
1 │ defmodule Tesla.Adapter.HttpcTest do
│ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
│
└─ test/tesla/adapter/httpc_test.exs:1: Tesla.Adapter.HttpcTest (module)
[Warn  - 12:25:03 AM]     warning: redefining module Tesla.Adapter.HttpcTest (current version defined in memory)
│
1 │ defmodule Tesla.Adapter.HttpcTest do
│ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
│
└─ test/tesla/adapter/httpc_test.exs:1: Tesla.Adapter.HttpcTest (module)
[Warn  - 12:25:04 AM]     warning: redefining module Tesla.Adapter.HttpcTest (current version defined in memory)
│
1 │ defmodule Tesla.Adapter.HttpcTest do
│ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
│
└─ test/tesla/adapter/httpc_test.exs:1: Tesla.Adapter.HttpcTest (module)
[Warn  - 12:25:04 AM]     warning: redefining module Tesla.Adapter.HttpcTest (current version defined in memory)
│
1 │ defmodule Tesla.Adapter.HttpcTest do
│ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
│
└─ test/tesla/adapter/httpc_test.exs:1: Tesla.Adapter.HttpcTest (module)
[Warn  - 12:25:05 AM]     warning: redefining module Tesla.Adapter.HttpcTest (current version defined in memory)
│
1 │ defmodule Tesla.Adapter.HttpcTest do
│ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
│
└─ test/tesla/adapter/httpc_test.exs:1: Tesla.Adapter.HttpcTest (module)
[Warn  - 12:25:05 AM]     warning: redefining module Tesla.Adapter.HttpcTest (current version defined in memory)
│
1 │ defmodule Tesla.Adapter.HttpcTest do
│ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
│
└─ test/tesla/adapter/httpc_test.exs:1: Tesla.Adapter.HttpcTest (module)
[Warn  - 12:25:06 AM]     warning: redefining module Tesla.Adapter.HttpcTest (current version defined in memory)
│
1 │ defmodule Tesla.Adapter.HttpcTest do
│ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
│
└─ test/tesla/adapter/httpc_test.exs:1: Tesla.Adapter.HttpcTest (module)
[Warn  - 12:25:06 AM]     warning: redefining module Tesla.Adapter.HttpcTest (current version defined in memory)
│
1 │ defmodule Tesla.Adapter.HttpcTest do
│ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
│
└─ test/tesla/adapter/httpc_test.exs:1: Tesla.Adapter.HttpcTest (module)
[Error - 10:49:02 AM] Server process exited with signal SIGKILL.
[Info  - 10:49:02 AM] Connection to server got closed. Server will restart.
true
Running /Users/ubi/.vscode/extensions/jakebecker.elixir-ls-0.20.0/elixir-ls-release/launch.sh
Preferred shell is zsh, relaunching
Looking for ASDF install
ASDF install found in /Users/ubi/.asdf/asdf.sh, sourcing
Installing ElixirLS release v0.20.0
Running in /Users/ubi/Developer/github.com/elixir-tesla/tesla
Install complete
[Info  - 10:49:06 AM] Started ElixirLS v0.20.0
[Info  - 10:49:06 AM] Running in /Users/ubi/Developer/github.com/elixir-tesla/tesla
[Info  - 10:49:06 AM] ElixirLS built with elixir "1.16.2" on OTP "26"
[Info  - 10:49:06 AM] Running on elixir "1.16.2 (compiled with Erlang/OTP 24)" on OTP "26"
[Info  - 10:49:06 AM] Protocols are not consolidated
[Info  - 10:49:06 AM] Elixir sources not found (checking in /home/runner/work/elixir/elixir). Code navigation to Elixir modules disabled.
[Info  - 10:49:06 AM] Received client configuration via workspace/configuration
%{"additionalWatchedExtensions" => [], "autoBuild" => true, "autoInsertRequiredAlias" => true, "dialyzerEnabled" => true, "dialyzerFormat" => "dialyxir_long", "dialyzerWarnOpts" => [], "enableTestLenses" => false, "envVariables" => %{}, "fetchDeps" => false, "languageServerOverridePath" => "", "mixEnv" => "test", "mixTarget" => "", "projectDir" => "", "signatureAfterComplete" => true, "suggestSpecs" => true, "trace" => %{"server" => "off"}}
[Info  - 10:49:08 AM] Registering for workspace/didChangeConfiguration notifications
[Info  - 10:49:08 AM] Starting build with MIX_ENV: test MIX_TARGET: host
[Info  - 10:49:08 AM] client/registerCapability succeeded
[Info  - 10:49:08 AM] Registering for workspace/didChangeWatchedFiles notifications
[Info  - 10:49:08 AM] client/registerCapability succeeded
[Warn  - 10:49:08 AM] error: module Tesla.AdapterCase is not loaded and could not be found
└─ nofile: Tesla.Adapter.HttpcTest (module)
[Warn  - 10:49:08 AM] ** (ErlangError) Erlang error: "CompileError during metadata build pre:\nnofile: cannot compile module Tesla.Adapter.HttpcTest (errors have been logged)\nast node: {:use, [end_of_expression: [newlines: 1, line: 4, column: 54], line: 4, column: 3], [{:aliases, [last: [line: 4, column: 13], line: 4, column: 7], [:Tesla, :AdapterCase]}, [adapter: {:aliases, [last: [line: 4, column: 49], line: 4, column: 35], [:Tesla, :Adapter, :Httpc]}]]}"
(elixir 1.16.2) src/elixir_expand.erl:96: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir_expand.erl:548: :elixir_expand.expand_block/5
(elixir 1.16.2) src/elixir_expand.erl:46: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir.erl:478: :elixir.quoted_to_erl/4
(elixir 1.16.2) src/elixir.erl:346: :elixir.eval_forms/4
(elixir 1.16.2) lib/module/parallel_checker.ex:112: Module.ParallelChecker.verify/1
(elixir 1.16.2) lib/code.ex:572: Code.validated_eval_string/3
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:24: ElixirSense.Core.MacroExpander.require_and_expand/2
(elixir 1.16.2) lib/macro.ex:640: anonymous fn/4 in Macro.do_traverse_args/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:18: ElixirSense.Core.MacroExpander.expand_use/4
(elixir_sense 2.0.0) lib/elixir_sense/core/metadata_builder.ex:1301: ElixirSense.Core.MetadataBuilder.pre/2
[Warn  - 10:49:08 AM] error: module Tesla.AdapterCase.Basic is not loaded and could not be found
└─ nofile: Tesla.Adapter.HttpcTest (module)
[Warn  - 10:49:08 AM] ** (ErlangError) Erlang error: "CompileError during metadata build pre:\nnofile: cannot compile module Tesla.Adapter.HttpcTest (errors have been logged)\nast node: {:use, [end_of_expression: [newlines: 1, line: 5, column: 30], line: 5, column: 3], [{:aliases, [last: [line: 5, column: 25], line: 5, column: 7], [:Tesla, :AdapterCase, :Basic]}]}"
(elixir 1.16.2) src/elixir_expand.erl:96: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir_expand.erl:548: :elixir_expand.expand_block/5
(elixir 1.16.2) src/elixir_expand.erl:46: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir.erl:478: :elixir.quoted_to_erl/4
(elixir 1.16.2) src/elixir.erl:346: :elixir.eval_forms/4
(elixir 1.16.2) lib/module/parallel_checker.ex:112: Module.ParallelChecker.verify/1
(elixir 1.16.2) lib/code.ex:572: Code.validated_eval_string/3
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:24: ElixirSense.Core.MacroExpander.require_and_expand/2
(elixir 1.16.2) lib/macro.ex:640: anonymous fn/4 in Macro.do_traverse_args/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:18: ElixirSense.Core.MacroExpander.expand_use/4
(elixir_sense 2.0.0) lib/elixir_sense/core/metadata_builder.ex:1301: ElixirSense.Core.MetadataBuilder.pre/2
[Warn  - 10:49:08 AM] error: module Tesla.AdapterCase.Multipart is not loaded and could not be found
└─ nofile: Tesla.Adapter.HttpcTest (module)
[Warn  - 10:49:08 AM] ** (ErlangError) Erlang error: "CompileError during metadata build pre:\nnofile: cannot compile module Tesla.Adapter.HttpcTest (errors have been logged)\nast node: {:use, [end_of_expression: [newlines: 1, line: 6, column: 34], line: 6, column: 3], [{:aliases, [last: [line: 6, column: 25], line: 6, column: 7], [:Tesla, :AdapterCase, :Multipart]}]}"
(elixir 1.16.2) src/elixir_expand.erl:96: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir_expand.erl:548: :elixir_expand.expand_block/5
(elixir 1.16.2) src/elixir_expand.erl:46: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir.erl:478: :elixir.quoted_to_erl/4
(elixir 1.16.2) src/elixir.erl:346: :elixir.eval_forms/4
(elixir 1.16.2) lib/module/parallel_checker.ex:112: Module.ParallelChecker.verify/1
(elixir 1.16.2) lib/code.ex:572: Code.validated_eval_string/3
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:24: ElixirSense.Core.MacroExpander.require_and_expand/2
(elixir 1.16.2) lib/macro.ex:640: anonymous fn/4 in Macro.do_traverse_args/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:18: ElixirSense.Core.MacroExpander.expand_use/4
(elixir_sense 2.0.0) lib/elixir_sense/core/metadata_builder.ex:1301: ElixirSense.Core.MetadataBuilder.pre/2
[Warn  - 10:49:08 AM] error: module Tesla.AdapterCase.StreamRequestBody is not loaded and could not be found
└─ nofile: Tesla.Adapter.HttpcTest (module)
[Warn  - 10:49:08 AM] ** (ErlangError) Erlang error: "CompileError during metadata build pre:\nnofile: cannot compile module Tesla.Adapter.HttpcTest (errors have been logged)\nast node: {:use, [end_of_expression: [newlines: 2, line: 7, column: 42], line: 7, column: 3], [{:aliases, [last: [line: 7, column: 25], line: 7, column: 7], [:Tesla, :AdapterCase, :StreamRequestBody]}]}"
(elixir 1.16.2) src/elixir_expand.erl:96: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir_expand.erl:548: :elixir_expand.expand_block/5
(elixir 1.16.2) src/elixir_expand.erl:46: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir.erl:478: :elixir.quoted_to_erl/4
(elixir 1.16.2) src/elixir.erl:346: :elixir.eval_forms/4
(elixir 1.16.2) lib/module/parallel_checker.ex:112: Module.ParallelChecker.verify/1
(elixir 1.16.2) lib/code.ex:572: Code.validated_eval_string/3
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:24: ElixirSense.Core.MacroExpander.require_and_expand/2
(elixir 1.16.2) lib/macro.ex:640: anonymous fn/4 in Macro.do_traverse_args/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:18: ElixirSense.Core.MacroExpander.expand_use/4
(elixir_sense 2.0.0) lib/elixir_sense/core/metadata_builder.ex:1301: ElixirSense.Core.MetadataBuilder.pre/2
[Warn  - 10:49:08 AM] error: module Tesla.AdapterCase.SSL is not loaded and could not be found
└─ nofile: Tesla.Adapter.HttpcTest (module)
[Warn  - 10:49:08 AM] ** (ErlangError) Erlang error: "CompileError during metadata build pre:\nnofile: cannot compile module Tesla.Adapter.HttpcTest (errors have been logged)\nast node: {:use, [end_of_expression: [newlines: 1, line: 14, column: 6], line: 9, column: 3], [{:aliases, [last: [line: 9, column: 25], line: 9, column: 7], [:Tesla, :AdapterCase, :SSL]}, [ssl: [verify: :verify_peer, cacertfile: {{:., [line: 13, column: 23], [{:aliases, [last: [line: 13, column: 19], line: 13, column: 19], [:Path]}, :join]}, [closing: [line: 13, column: 90], line: 13, column: 24], [[{:to_string, [closing: [line: 13, column: 66], line: 13, column: 30], [{{:., [line: 13, column: 45], [:code, :priv_dir]}, [closing: [line: 13, column: 65], line: 13, column: 46], [:httparrot]}]}, "/ssl/server-ca.crt"]]}]]]}"
(elixir 1.16.2) src/elixir_expand.erl:96: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir_expand.erl:548: :elixir_expand.expand_block/5
(elixir 1.16.2) src/elixir_expand.erl:46: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir.erl:478: :elixir.quoted_to_erl/4
(elixir 1.16.2) src/elixir.erl:346: :elixir.eval_forms/4
(elixir 1.16.2) lib/module/parallel_checker.ex:112: Module.ParallelChecker.verify/1
(elixir 1.16.2) lib/code.ex:572: Code.validated_eval_string/3
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:24: ElixirSense.Core.MacroExpander.require_and_expand/2
(elixir 1.16.2) lib/macro.ex:640: anonymous fn/4 in Macro.do_traverse_args/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:18: ElixirSense.Core.MacroExpander.expand_use/4
(elixir_sense 2.0.0) lib/elixir_sense/core/metadata_builder.ex:1301: ElixirSense.Core.MetadataBuilder.pre/2
[Info  - 10:49:08 AM] Loaded DETS databases in 137ms
[Warn  - 10:49:08 AM] error: module Tesla is not loaded and could not be found
└─ nofile: Tesla.Middleware.TimeoutTest.Client (module)
[Warn  - 10:49:08 AM] ** (ErlangError) Erlang error: "CompileError during metadata build pre:\nnofile: cannot compile module Tesla.Middleware.TimeoutTest.Client (errors have been logged)\nast node: {:use, [end_of_expression: [newlines: 2, line: 5, column: 14], line: 5, column: 5], [{:aliases, [last: [line: 5, column: 9], line: 5, column: 9], [:Tesla]}]}"
(elixir 1.16.2) src/elixir_expand.erl:96: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir_expand.erl:548: :elixir_expand.expand_block/5
(elixir 1.16.2) src/elixir_expand.erl:46: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir.erl:478: :elixir.quoted_to_erl/4
(elixir 1.16.2) src/elixir.erl:346: :elixir.eval_forms/4
(elixir 1.16.2) lib/module/parallel_checker.ex:112: Module.ParallelChecker.verify/1
(elixir 1.16.2) lib/code.ex:572: Code.validated_eval_string/3
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:24: ElixirSense.Core.MacroExpander.require_and_expand/2
(elixir 1.16.2) lib/macro.ex:640: anonymous fn/4 in Macro.do_traverse_args/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:18: ElixirSense.Core.MacroExpander.expand_use/4
(elixir_sense 2.0.0) lib/elixir_sense/core/metadata_builder.ex:1301: ElixirSense.Core.MetadataBuilder.pre/2
[Warn  - 10:49:08 AM] error: module Tesla is not loaded and could not be found
└─ nofile: Tesla.Middleware.TimeoutTest.DefaultTimeoutClient (module)
[Warn  - 10:49:08 AM] ** (ErlangError) Erlang error: "CompileError during metadata build pre:\nnofile: cannot compile module Tesla.Middleware.TimeoutTest.DefaultTimeoutClient (errors have been logged)\nast node: {:use, [end_of_expression: [newlines: 2, line: 35, column: 14], line: 35, column: 5], [{:aliases, [last: [line: 35, column: 9], line: 35, column: 9], [:Tesla]}]}"
(elixir 1.16.2) src/elixir_expand.erl:96: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir_expand.erl:548: :elixir_expand.expand_block/5
(elixir 1.16.2) src/elixir_expand.erl:46: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir.erl:478: :elixir.quoted_to_erl/4
(elixir 1.16.2) src/elixir.erl:346: :elixir.eval_forms/4
(elixir 1.16.2) lib/module/parallel_checker.ex:112: Module.ParallelChecker.verify/1
(elixir 1.16.2) lib/code.ex:572: Code.validated_eval_string/3
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:24: ElixirSense.Core.MacroExpander.require_and_expand/2
(elixir 1.16.2) lib/macro.ex:640: anonymous fn/4 in Macro.do_traverse_args/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:18: ElixirSense.Core.MacroExpander.expand_use/4
(elixir_sense 2.0.0) lib/elixir_sense/core/metadata_builder.ex:1301: ElixirSense.Core.MetadataBuilder.pre/2
[Warn  - 10:49:08 AM] error: module Tesla is not loaded and could not be found
└─ nofile: Tesla.Middleware.TimeoutTest.OtelTimeoutClient (module)
[Warn  - 10:49:08 AM] ** (ErlangError) Erlang error: "CompileError during metadata build pre:\nnofile: cannot compile module Tesla.Middleware.TimeoutTest.OtelTimeoutClient (errors have been logged)\nast node: {:use, [end_of_expression: [newlines: 2, line: 53, column: 14], line: 53, column: 5], [{:aliases, [last: [line: 53, column: 9], line: 53, column: 9], [:Tesla]}]}"
(elixir 1.16.2) src/elixir_expand.erl:96: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir_expand.erl:548: :elixir_expand.expand_block/5
(elixir 1.16.2) src/elixir_expand.erl:46: :elixir_expand.expand/3
(elixir 1.16.2) src/elixir.erl:478: :elixir.quoted_to_erl/4
(elixir 1.16.2) src/elixir.erl:346: :elixir.eval_forms/4
(elixir 1.16.2) lib/module/parallel_checker.ex:112: Module.ParallelChecker.verify/1
(elixir 1.16.2) lib/code.ex:572: Code.validated_eval_string/3
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:24: ElixirSense.Core.MacroExpander.require_and_expand/2
(elixir 1.16.2) lib/macro.ex:640: anonymous fn/4 in Macro.do_traverse_args/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(stdlib 5.2.1) lists.erl:1706: :lists.mapfoldl_1/3
(elixir 1.16.2) lib/macro.ex:605: Macro.do_traverse/4
(elixir_sense 2.0.0) lib/elixir_sense/core/macro_expander.ex:18: ElixirSense.Core.MacroExpander.expand_use/4
(elixir_sense 2.0.0) lib/elixir_sense/core/metadata_builder.ex:1301: ElixirSense.Core.MetadataBuilder.pre/2
Compiling 48 files (.ex)
Generated tesla app
[Info  - 10:49:13 AM] Compile took 4560 milliseconds
[Info  - 10:49:13 AM] [ElixirLS WorkspaceSymbols] Indexing...
[Info  - 10:49:13 AM] [ElixirLS WorkspaceSymbols] Module discovery complete
[Info  - 10:49:13 AM] [ElixirLS WorkspaceSymbols] 425 symbols added to index in 37ms
[Info  - 10:49:13 AM] [ElixirLS Dialyzer] Checking for stale beam files
[Info  - 10:49:13 AM] [ElixirLS Dialyzer] Found 61 changed files in 109 milliseconds
[Info  - 10:49:13 AM] [ElixirLS Dialyzer] Analyzing 3 modules: [MockClient, Tesla.Env, Tesla]
[Info  - 10:49:14 AM] [ElixirLS Dialyzer] Analysis finished in 792 milliseconds
[Info  - 10:49:14 AM] Dialyzer analysis is up to date
[Info  - 10:49:15 AM] [ElixirLS Dialyzer] Writing manifest...
[Info  - 10:49:16 AM] [ElixirLS Dialyzer] Done writing manifest in 1690 milliseconds.
[Info  - 10:49:17 AM] Success typings computed in 3258ms
[Info  - 10:56:08 AM] Success typings computed in 42ms
[Info  - 10:56:11 AM] Success typings computed in 26ms
[Info  - 11:00:45 AM] Success typings computed in 52ms
[Info  - 11:01:07 AM] Success typings computed in 42ms

</details>

My fan goes crazy for a few seconds every time I save. Even if nothing changed. AFAIK, for me, this only started to occur recently. Not sure if it's related. Some logs attached.

lsp-elixir: INFO: Compile took 1406 milliseconds
lsp-elixir: INFO: [ElixirLS WorkspaceSymbols] Updating index...
lsp-elixir: INFO: [ElixirLS WorkspaceSymbols] 0 modules need reindexing
lsp-elixir: INFO: [ElixirLS WorkspaceSymbols] 0 symbols added to index in 0ms
lsp-elixir: INFO: Updating incremental PLT
lsp-elixir: INFO: Incremental PLT updated in 12279ms, changed 6 modules, analyzed 24, 0 warnings found
lsp-elixir: INFO: Loaded PLT info in 1683ms
lsp-elixir: INFO: Dialyzer analysis is up to date
lsp-elixir: INFO: Success typings computed in 2141ms
lsp-elixir: INFO: Starting build with MIX_ENV: dev MIX_TARGET: host
lsp-elixir: LOG: All deps are up to date
lsp-elixir: WARNING:     warning: unused alias Thread
    │
  7 │   alias Prac.Chat.{Thread, Message}
    │   ~
    │
    └─ lib/prac_web/components/chat_components.ex:7:3
lsp-elixir: INFO: Compile took 1233 milliseconds
lsp-elixir: INFO: [ElixirLS WorkspaceSymbols] Updating index...
lsp-elixir: INFO: [ElixirLS WorkspaceSymbols] 0 modules need reindexing
lsp-elixir: INFO: [ElixirLS WorkspaceSymbols] 0 symbols added to index in 0ms
lsp-elixir: INFO: Updating incremental PLT
lsp-elixir: INFO: Incremental PLT updated in 1128ms, changed 0 modules, analyzed 0, 0 warnings found
lsp-elixir: INFO: Loaded PLT info in 1515ms
lsp-elixir: INFO: Dialyzer analysis is up to date

@princemaple 1.5s for build, 2.6s for dialyzer. OTP incremental dialyzer is slower than the old engine

Interesting: when working on another 10x more complicated project the fan didn't even make a sound.

lsp-elixir: INFO: Starting build with MIX_ENV: dev MIX_TARGET: host
lsp-elixir: LOG: All deps are up to date
lsp-elixir: LOG: Compiling 19 files (.ex)
lsp-elixir: LOG: Generated app app
lsp-elixir: INFO: Compile took 2742 milliseconds
lsp-elixir: INFO: [ElixirLS WorkspaceSymbols] Updating index...
lsp-elixir: INFO: [ElixirLS WorkspaceSymbols] 0 modules need reindexing
lsp-elixir: INFO: [ElixirLS WorkspaceSymbols] 0 symbols added to index in 0ms
lsp-elixir: INFO: Updating incremental PLT
lsp-elixir: INFO: Incremental PLT updated in 6426ms, changed 1 modules, analyzed 1, 1 warnings found
lsp-elixir: INFO: Loaded PLT info in 1246ms
lsp-elixir: INFO: Dialyzer analysis is up to date
lsp-elixir: INFO: Success typings computed in 15ms

I'll try and figure out what's wrong next time I get back to the simpler project.

Seems like when I do "go to definition" to library file, my all CPU cores explodes.
Phoenix, Ash
Erlang/OTP 26 [erts-14.2.5] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [jit:ns]
Mix 1.17.2 (compiled with Erlang/OTP 26)

I am reopening for visibility; let me know if you disagree with it

My fan is also whirring up a storm every time I save in a mix project. Doesn't happen on a standalone Elixir script, only on an Elixir file in a mix project.
In my System Monitor, I see memory usage for the elixir-ls launch script jump from ~330MB to ~1.1GB and down again for a simple Elixir file save in a mix project (no edits) - is that expected?
What's really strange is that elixir-ls sometimes deletes a normal line of code on save (automatic code deletion stops when I stop elixir-ls). I also saw it insert a space randomly in the word alias.
I think the automatic line deleting/space inserting started happening after I wrote and used a custom function async/0 in my mix project, maybe that caused something?
Using neovim on Linux, elixir 1.17.2-otp-27
Erlang/OTP 27 [erts-15.0] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-t
hreads:1] [jit:ns]
Mix 1.17.2 (compiled with Erlang/OTP 27)

Seems like when I do "go to definition" to library file, my all CPU cores explodes. Phoenix, Ash Erlang/OTP 26 [erts-14.2.5] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [jit:ns]
Mix 1.17.2 (compiled with Erlang/OTP 26)

I'm getting this error and then nothing happens when I do cmd+click+<module>. Hover does nothing either. Searching for nofile within a year, this issue is the only hit on Google. Seems to just blow up on use.
Elixir 1.17.2 (compiled with Erlang/OTP 27)

In my case, I'm able to cause the memory usage to spike very quickly using the debugger in VSCode. To reproduce I can start the debugger with no breakpoints, or step through all breakpoints. It takes ~1 min for the beam.smp process to reach 60 GB of memory. My VSCode launch configuration:
        {
            "type": "mix_task",
            "name": "chat: mix test",
            "request": "launch",
            "task": "test",
            "taskArgs": [
                "--trace",
                "--only",
                "run"
            ],
            "startApps": true,
            "projectDir": "${workspaceRoot}/apps/chat",
            "requireFiles": [
                "${workspaceRoot}/apps/chat/apps/chat/**/test_helper.exs",
                "${workspaceRoot}/apps/chat/apps/chat/**/*_test.exs"
            ],
            "debugInterpretModulesPatterns": ["BmvpWeb*"],
            "exitAfterTaskReturns": false
        }

Add this line "debugAutoInterpretAllModules": false to the configuration solves the issue and manually adding all my project files to the "requiredFiles" list solves the issue.
        {
            "type": "mix_task",
            "name": "chat: mix test",
            "request": "launch",
            "task": "test",
            "taskArgs": [
                "--trace",
                "--only",
                "run"
            ],
            "startApps": true,
            "projectDir": "${workspaceRoot}/apps/chat",
            "requireFiles": [
                "${workspaceRoot}/apps/chat/apps/chat/**/test_helper.exs",
                "${workspaceRoot}/apps/chat/apps/chat/**/*_test.exs",
                "${workspaceRoot}/apps/chat/apps/chat/lib/**/*.ex",
            ],
            "debugInterpretModulesPatterns": ["BmvpWeb*"],
            "exitAfterTaskReturns": false
        }

A bunch of errors pop up with this configuration saying: warning: redefining module ... (current version loaded from .elixir_ls/debug_adapter/build/test/lib.
This seems to point to the error being from interpreting some dependency modules.

@jsermeno debug adapter memory leak is another problem not related to this issue, see some investigation in https://github.com/elixir-lsp/elixir-ls/issues/1017
I believe you shouldn't be using requireFiles for ex files. This should be sufficient
"debugAutoInterpretAllModules": false,
debugInterpretModulesPatterns": ["BmvpWeb*"],

The issue occurs very quickly while debugging because it interprets all dependency modules in quick succession.

In your current configuration the modules are indeed loaded twice. First time by mix task and second via requireFiles (which calls Code.require_file)

@lukaszsamson Thanks for getting back so quickly!
Ah I see, thanks for the link to the correct issue. I didn't understand the purpose of debugInterpretModulesPatterns since I had just found it on a Stack Overflow post. Changing that to my module prefix debugInterpretModulesPatterns": ["MyModulePrefix*"], solved the problem without adding any files to the requiredFiles property.
Referring to that other issue though, I don't think it is Cowboy specific. I've created a minimal reproduction in this repo: https://github.com/jsermeno/elixir_ls_debug_failure. The only dependency I need to recreate this issue is {:stream_data, "~> 1.0", only: [:dev, :test]} and the following code:
  def gen_data() do
    StreamData.list_of(StreamData.fixed_map(%{
      "e" => StreamData.string(:utf8)
    }), min_length: 1, max_length: 1)
  end

  def gen_data_all() do
    gen all fixed_map <- gen_data() do
      fixed_map
    end
  end

  test "greets the world" do
    data = Enum.at(gen_data_all(), 0)
    assert ElixirLsFailure.hello() == :world
  end

I'll open an issue with StreamData as well. However, it seems it's likely not something specific this library since I don't believe Phoenix relies on this library.


Fix a few failing live tests

Address #516.
Close #517.

Codecov Report

Merging #518 (27fe9f7) into master (daf121d) will decrease coverage by 0.09%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##           master     #518      +/-   ##
==========================================
- Coverage   86.79%   86.70%   -0.10%
==========================================
  Files          24       24
  Lines        3316     3316
==========================================
- Hits         2878     2875       -3
- Misses        438      441       +3

Impacted Files
Coverage Δ

dwave/cloud/cli.py
64.27% <50.00%> (ø)

dwave/cloud/api/resources.py
89.23% <0.00%> (-3.85%)
:arrow_down:

dwave/cloud/client/base.py
90.51% <0.00%> (+0.24%)
:arrow_up:

Continue to review full report at Codecov.

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


Is it possible to get the ValuePattern value?

Good evening!
I've read some of the  posted questions regarding using some of the patterns with WinAppDriver and Selenium.  I was able to use the Toggle.ToggleSettings with the GetAttribute method but I was still unsure if it's possible to get the value of the ValuePattern pattern.
Here's the reason why I want to get the value of the ValuePattern.  I entered text into a control and the Text method in Selenium won't return the sting value I entered so I can validate the text value.  I was able to get text from other controls using the .Text method in Selenium (I'm using WinAppDriver with Selenium and C#).  The control type is a DataItem so I'm not sure if that plays a role in the way I can retrieve text from the control.
Is it possible to get that ValuePattern value through the GetAttribute method in Selenium or would I have to go through the System.Windows.Automation namespace?  I'm extremely new to windows automation so please be gentle.  lol.

Not a problem I'll add some more details. I clicked on the row element where the control was included and then I was able to get the value of the control.
Another tip I figured out is you might have to click on a control first before getting the value of that control. For example, I had a checkbox that initially showed up in the tree as a DataItem control type but after clicking on the DataItem control it then showed up in the tree as a checkbox, and I was able to get the status of the checkbox, and whether it was checked or not.

Sorry, but I still not understand how could you get value from ValuePattern.Value.
Please explain more


Specify a sequence of scenarios to execute in a configuration file.

Is your feature request related to a problem? Please describe.
No, the request is not related to a problem.
Describe the solution you'd like
We are using Gauge for automated system testing of embedded systems and we would like to run a specific scenario, to program the Device Under Test, before all of the other scenarios. We currently execute Gauge twice. Once to run the programming scenario then again to run the test suite.
We are currently using tags to group scenarios into test suites and we use tag expressions to run the suites. However, as the suites get large and we have more tests, we thought a configuration file would make it easier to visualize and control which scenarios run in which test suite.
We realize that Gauge appears to execute spec-by-spec. We aren't looking to run scenario 1 from spec A, then scenario 2 from spec B then scenario 3 from spec A. Maybe the configuration file is a YAML file where you specify a sequence of specs and then within each spec you specify which scenarios to execute. For example:
specs:
  - Spec Name A
    scenarios:
      - Scenario Name 1
  - Spec Name B
    scenarios:
      - Scenario Name 2

Then to execute Gauge, you might run:
gauge run specs --sequence specs.yaml

Describe alternatives you've considered
We've considered using the BeforeSuite hook for the programming, but still felt that overall it would be nice to specify the complete set of scenarios to execute in a test suite.
We've considered using a script to feed the list of scenarios to Gauge using the --scenario option, but had concerns about the input buffer size on the command line.
Additional context
Nothing at this time.

So far, we've been recommending that Gauge specs/scenarios remain independent and this sort of sequencing leads to temporal coupling. And it increases the complexity in executing a single scenario or even rerun all/failed tests.
But this has been requested too many times, so I am going to consider this. (@zabil - thoughts?)
My take is that

if this were to be implemented, it should not be just a static list (it could be so for a first cut), rather it should be something similar to how build tools work (tasks depend on tasks).

The file should include the ability to either specify a spec or scenario, or a folder, or even a tag expression.

There needs to be a check for cyclic dependencies.

the parallel run needs to be thought over, Does gauge allow users to specify the streams? or does gauge generate parallel streams taking dependencies into consideration? or does gauge just not allow parallel run when it does not control the orchestration?

Alternatively, could we attempt to make gauge honour piping (like unix tools do) so one could do something like cat workflow.txt | gauge run
Thoughts?
/cc @getgauge/core

if this were to be implemented, it should not be just a static list (it could be so for a first cut), rather it should be something similar to how build tools work (tasks depend on tasks).

Preferably a json file. Maybe worth expanding the manifest.json to add something like execution groups roughly something like
groups : [ { name: "sequence1", "specs" : [ { name: "Specification 1", scenarios : []...

gauge run --group "sequence1"

he parallel run needs to be thought over, Does gauge allow users to specify the streams? or does gauge generate parallel streams taking dependencies into consideration? or does gauge just not allow parallel run when it does not control the orchestration?

I assume running in parallel should be disabled as it depends on the order?

Alternatively, could we attempt to make gauge honour piping (like unix tools do) so one could do something like cat workflow.txt | gauge run

If this can also be done on windows/powershell

Did a quick check, and as long as gauge honours stdin, users should be able to pipe in/redirect list of specs/scenarios into gauge.
The challenge though is that gauge does not honour order of scenarios, so this will still be viable only to control the order of execution of specs and not scenarios within the spec.
@raweaver - would this approach work for you? I'll spend some more time once I know that this can be useful.

@sriv @zabil Thank you for the responses and suggestions.
We discussed the options and we feel that a sequence file passed to gauge as a command line argument would be our preferred solution. Also, controlling the order of specs (not scenarios) would be sufficient. It might be beneficial to structure the sequence file such that you could add support for specifying the scenario sequence in the future if desired.
Thank you!

@sriv @zabil - Any update on this? Would love to see this new feature implemented, this would be really useful for us. Any timeline on when we expect to see this feature released? Thank you so much for adding this new feature.

Hi, @zabil @sriv. Do you have any updates about this new feature?
It will be very beneficial for our team


initial push

inverse lookup using NOT instead of NOT IN subquery .

inverse_lookup/lookups.py

current lookup_names are

neexact
neiexact
necontains
neicontains
nestartswith
neistartswith
neendswith
neiendswith

inverse_lookup is django app, import lookup and Field.register_lookup when app is ready.
test sqlite, mysql, postgresql on trvis-ci, sqlite on local (not passed enviroment variable).

tests/test_settings.py
tests/test_inverse_lookups.py

structure based on cookiecutter-pypackage

リポジトリ名をdjango-lookup-extensionsに変えるので一旦in progressへ

renamed repository and package name.
mainly see below.

lookup_extensions/lookups.py
tests/test_settings.py
tests/test_lookup_extensions.py


Use args correctly for coveragepublisher

Task name: Related to PublishCodeCoverageResults@2
Description:
This is using one item in the args array for each argument. When Node.js spawn's the new process it will work as expected.
See:
https://github.com/microsoft/azure-pipelines-task-lib/blob/4086d6bef172fe1329d3006ccacc324e05baac1e/node/toolrunner.ts#L269
Documentation changes required: (N)
Added unit tests: (N - There were none)
Attached related issue: (Y) #17756
Checklist:

[ ] Task version was bumped - please check instruction how to do it
[ ] Checked that applied changes work as expected

Between versions 2.221. and 2.223 our PublishTestResults@2 task stopped working because of this issue. Any news on reviewing this?

@vinayakmsft @karanjitsingh Can we get this merged? The bug this fixes is currently a hard blocker for anyone trying to publish multiple coverage files.

Hi We have already made this change here(Latest master)  https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/Common/coveragepublisher/coveragepublisher.ts
This was the PR - https://github.com/microsoft/azure-pipelines-tasks/commit/7acfb8e566d01fc5c4da820b93a38e59e84e80f2

@vinayakmsft when is this planned to be deployed for Azure DevOps?

Please expect 2 weeks for deployment

@vinayakmsft Why?
You (msft/devops team - this isn't a personal attack) have released software with a showstopping bug, which should have been caught with a test, a lint, or a PR review.
 It was reported to you 5 months ago. People are wasting time on workarounds.
@giggio (your customer) has found the root cause and fixed it for you over a month ago. But you don't want to take his change, because it's already been made, buried in an irrelevant commit without any explanatory comment or link to the issue.
And now it's going to take another 2 weeks to deploy a release? I know AZDO is slow, but there is something very wrong with your processes over there.

As #18281 was already merged and it fixes the same problems I'm closing this PR.


"this.$gtag is not a function" in production but not locally

I have the following google-gtag nuxt config
    ['@nuxtjs/google-gtag', {
      id: process.env.GOOGLE_ANALYTICS_ID,
      debug: process.env.NODE_ENV === 'development', // enable to track in dev mode

      // gtag config https://developers.google.com/analytics/devguides/collection/gtagjs/
      config: {
        send_page_view: false // necessary to avoid duplicated page track on page reload
      }
    }],

It works fine locally; no errors, events are triggered.
My circleCI build puts it all into a Docker container and deploys to heroku. I have those environment variables set in the Heroku dashboard. The NODE_ENV is production on Heroku.
I've logged into the container and made sure the variables are being imported, going as far as to start node and require('./nuxt.config.js') to make sure the id is being set properly.
No matter what, the google tag script element isn't added to the head of the page. As such, I get the following error when trying to access this.$gtag to trigger events.
TypeError: this.$gtag is not a function

I can't give any further instructions without any demo project

Yes, sorry, I've been meaning to follow this up with an explanation of the issue and how we solved it. Hopefully I can clarify that this week.

The solution was that we needed to do a nuxt build && nuxt start so that it picked up the new production environment variables.
Even though nuxt.config.js is dynamic, somewhere along the line the environment variables in its structure get baked into the build.


Add a task to drop the app db and user.

Hey, I'm the user from the Boot.dev discord who was having an issue seeding the db.
Thought I may have screwed up, so I wanted to attempt it again. I found having to manually drop the db and user annoying, so I added a drop task.

much appreciated


Update Landing page to the new design

Assets can be requested through me here or via Discord.
Currently our layout has been outdated by almost three revisions already since we've updated our website's design to fit the Freya language.

It is imperative this should be updated to the new design as soon as possible.

Resolved by:

507e7fc51906b764b0037eb4fcf372fe54f4b3e5.


Fix for Scintilla Views with forecolor with nil

In ScintillaIndicatorStyle>>stbConvertFrom: if  forecolor is nil --> the STB convertion fails.
This fix make Jade (https://github.com/jgfoster/Jade) to be loaded without any problems with Dolphin latest commit.
Maybe the fix should be in other part but with this all Jade IDE seems to work without problems.

There is a fix for this issue among a lot of other Scintilla changes in my latest PR.


Remove sync API

[ ] How do you get validation errors? Use of correlation id or causation id? Or you could store command results in order to be able to see what you did.

I think it would be better to remove the async part of the API and instead add external integration as a side-effect to use the queue.


Internal Server Error

Hi,
first of all: thank You VERY much - I was trying and looking so much for a WORKING solution like this without result.
Well - I still get this error when trying to start the Playback - BUT luckily if I skip over it it DOES work :D
so - the error is from
StackTrace = "   bei OpenSource.UPnP.UPnPService.InvokeSync(String MethodName, UPnPArgument[] InVarArr) in c:\Users\Public\Downloads\DeveloperToolsForUPnP\Global\UPnP\UPnPService.cs:Zeile 3331.\r\n   bei LocalAudioBroadcast.ControlPoint.SetAVTransportURI() in C:...
seems to be in Your precompiled dll ??
the return says:
UPNP = {"Action Failed"}
I got this error with other apps, too.
so I put the service.InvokeSync("SetAVTransportURI", args);
in a try/catch and it's working…
Can You tell me please, where You got this opensource.upnp lib from - so I may take a look at it to resolve the issue...
Thanks & cheers,
Stephan
EDIT:
Another thing is, that I have to select WAV at first, start the Playback (but I don't get Sound) - then stop Playback, switch to LPCM and start Playback...

Hi,
so meanwhile I think the Problem Comes from 'wrong' args, Maybe...?
As I wrote above I 1st have to start with WAV as Streaming Format -
when I start I get following Output:
GET http://<IP_ADDRESS>:10610/capture HTTP/1.1
User-Agent: Music Player Daemon 0.21
Icy-Metadata: 1
remote_addr: <IP_ADDRESS>
remote_port: 60594
Default Playback Capture: Lautsprecher (Realtek High Definition Audio) loopback capture source format: 16 bit PCM: 96kHz 2 channels (2,9 Mb/s)
MetadataEmbedder:SetTrackInfo Metadata set: StreamTitle='N/A';
ICY OK
audio/wav
TransferMode.DLNA.ORG: Streaming
Server: UPnP/1.0 DLNADOC/1.50 LAB/1.0
icy-name: Local Audio Broadcast
icy-metaint: 192000
MetadataEmbedder:SetTrackInfo Metadata set: StreamTitle='N/A';
Ausnahme ausgelöst: "System.Net.Sockets.SocketException" in System.dll
Ausnahme ausgelöst: "System.IO.IOException" in System.dll
sending 38444 bytes = 0,10 secs
sending 42240 bytes = 0,11 secs
Der Thread 0x5a78 hat mit Code 0 (0x0) geendet.
Ausnahme ausgelöst: "System.Net.Sockets.SocketException" in System.dll
Ausnahme ausgelöst: "System.IO.IOException" in System.dll
request processing finished
AVTransport Event 1 urn:upnp-org:serviceId:AVTransport

after this it stops
But if I switch to PCM and start I still get an internal Server error but the Transport is working…
seems like it's hooking onto the initial WAV Transport...
Ausnahme ausgelöst: "OpenSource.UPnP.UPnPInvokeException" in UPnP.dll
GET http://<IP_ADDRESS>:10610/capture HTTP/1.1
User-Agent: Music Player Daemon 0.21
Icy-Metadata: 1
remote_addr: <IP_ADDRESS>
remote_port: 60612
Default Playback Capture: Lautsprecher (Realtek High Definition Audio) loopback capture source format: 16 bit PCM: 96kHz 2 channels (2,9 Mb/s)
MetadataEmbedder:SetTrackInfo Metadata set: StreamTitle='N/A';
ICY OK
audio/L16;rate=96000;channels=2
TransferMode.DLNA.ORG: Streaming
Server: UPnP/1.0 DLNADOC/1.50 LAB/1.0
icy-name: Local Audio Broadcast
icy-metaint: 192000
sending 38400 bytes = 0,10 secs
TransportState Change: PLAYING
sending 38400 bytes = 0,10 secs
sending 38400 bytes = 0,10 secs
sending 38400 bytes = 0,10 secs
sending 38433 bytes = 0,10 secs
sending 38400 bytes = 0,10 secs
sending 42240 bytes = 0,11 secs
sending 38400 bytes = 0,10 secs
sending 38400 bytes = 0,10 secs
sending 38401 bytes = 0,10 secs
...

Hello again ;)
Well, finally I found that my upnp renderer doesn't support L16... they say it supports wav/pcm...
Hmm?
So I dunno - I don't want to dig too deep into the code - after some Experiments I have a Workaround:
I created a new streamingformat in order not to break the former
        class PCMFormat : StreamingFormat {

            public override string Id {
                get { return "pcm"; }
            }

            public override string Name {
                get { return "PCM"; }
            }

            public override string GetFormatDescriptor(int sampleRate, int channels) {
               return "audio/l16;rate=" + sampleRate + ";channels=" + channels;
            }

            public override string GetNetworkFormatDescriptor(int sampleRate, int channels) {
                return "http-get:*:audio/x-wav:*";

            }

            public override bool BigEndian {
                get { return false; }
            }
        }

as You can see I changed the return value for the networkformatdescriptor to
"http-get:*:audio/x-wav:*"
BigEndian is false
I set/left  the FormatDescriptor to the L16 descriptor
"audio/l16;rate=" + sampleRate + ";channels=" + channels; -- it is working - and as I said, I don't want to dig deeper, BUT if I use the WAV descriptor here, it is NOT working...
This seemed to be the same Problem with other Tools like SWYH... Maybe
Cheers,
Stephan

That sounds great! Might help with the issue I have with an old XBOX and XBMC. Could you perhaps share the binaries, so I can try?

@ltGuillaume : well, I tried it with mine - but it doesn't show up in the list… :/
Maybe I'll check this next time

Closing due to repo archival.


http: multiple response.WriteHeader calls

Hi Christian
running swd behind a haproxy sometimes result in an error
swd[15065]: 2018/04/24 07:38:32 http: multiple response.WriteHeader calls
This happens on permission errors.
swd is running as user www-data and www-data has not permission on .gitignore file
Apr 24 08:02:08 het71 swd[15065]: 2018/04/24 08:02:08 http: multiple response.WriteHeader calls
Apr 24 08:02:08 het71 swd[15065]: time="2018-04-24T08:02:08+02:00" level=error msg="open /www/aaa.bbb.de/.gitignore: permission denied"
Jörg

Hej @lingej,
this issue is potentially fixed with 76c23dc. Could you please give it a try?
Thanks a lot! 😃
Best,
Christian

Hi Christian
this issue is now fixed!
Thanks!

Hej @lingej,
I'm glad to hear that :)


[SPARK-23383][Build][Minor]Make a distribution should exit with usage while detecting wrong options

What changes were proposed in this pull request?
./dev/make-distribution.sh --name ne-1.0.0-SNAPSHOT xyz --tgz  -Phadoop-2.7
+++ dirname ./dev/make-distribution.sh
++ cd ./dev/..
++ pwd
+ SPARK_HOME=/Users/Kent/Documents/spark
+ DISTDIR=/Users/Kent/Documents/spark/dist
+ MAKE_TGZ=false
+ MAKE_PIP=false
+ MAKE_R=false
+ NAME=none
+ MVN=/Users/Kent/Documents/spark/build/mvn
+ ((  5  ))
+ case $1 in
+ NAME=ne-1.0.0-SNAPSHOT
+ shift
+ shift
+ ((  3  ))
+ case $1 in
+ break
+ '[' -z /Users/Kent/.jenv/candidates/java/current ']'
+ '[' -z /Users/Kent/.jenv/candidates/java/current ']'
++ command -v git
+ '[' /usr/local/bin/git ']'
++ git rev-parse --short HEAD
+ GITREV=98ea6a7
+ '[' '!' -z 98ea6a7 ']'
+ GITREVSTRING=' (git revision 98ea6a7)'
+ unset GITREV
++ command -v /Users/Kent/Documents/spark/build/mvn
+ '[' '!' /Users/Kent/Documents/spark/build/mvn ']'
++ /Users/Kent/Documents/spark/build/mvn help:evaluate -Dexpression=project.version xyz --tgz -Phadoop-2.7
++ grep -v INFO
++ tail -n 1
+ VERSION=' -X,--debug                             Produce execution debug output'

It is better to declare the mistakes and exit with usage than break
How was this patch tested?
manually
cc @srowen

Test build #87295 has started for PR 20571 at commit 81c1b24.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/781/
Test PASSed.

Test build #87295 has finished for PR 20571 at commit 81c1b24.

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

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

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/797/
Test PASSed.

Test build #87313 has started for PR 20571 at commit 4194658.

Test build #87313 has finished for PR 20571 at commit 4194658.

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

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

Merged build finished. Test PASSed.

Ping @yaooqinn

sorry for not replying in time. the logic here is that firstly unrecognized - -options show warning message and usage information，secondly the - options end the while loop and treat the current one and following options as maven parameters which will be handled later by maven，and finally all other unrecognized options fail the process immediately.

Yes @yaooqinn, it's easy enough to read the logic, but, my question is why treat these cases differently? Why not go all the way to failing on any unexpected input?

OK， i will push a commit very soon

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/957/
Test PASSed.

Test build #87539 has started for PR 20571 at commit b99c43c.

Test build #87539 has finished for PR 20571 at commit b99c43c.

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

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

Merged build finished. Test FAILed.

retest this please

Test build #87540 has started for PR 20571 at commit b99c43c.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/958/
Test PASSed.

Test build #87540 has finished for PR 20571 at commit b99c43c.

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

yes， single dash means the coming ones are all maven options，they will be handled later by mvn command. we do not parse each single option in this while loop from then till now.

Merged to master