Support settings options for pyls

As with many other options, add an ale_python_plys_options variable for defining options for pyls, with documentation and tests.

According to the folks over at Palantir (palantir/python-language-server#312), this needs to be done by sending a workspace/didChangeConfiguration message to pyls once it has been started.  This will allow you to configure which linters are used.

This is useful for RLS as well: https://github.com/rust-lang-nursery/rls#configuration

As I understand the work is not done yet and the value is not passed to ale#linter#Define.
Direct  call to DidChangeConfiguration doesn't make an effect either.
:let a = ale#lsp#message#DidChangeConfiguration(bufnr('%'), g:ale_python_pyls_config)

Maybe 0 value is not equivalent to JSON's false.
Also I struggle to debug pyls without running it with options -vv --log-file ~/pyls.log. Could you hint me what to do?

As I now see ale#lsp#message#DidChangeConfiguration function is only do value wrapping.
The yielding value is consumed by ale#lsp#Send while ale#lsp_linter#StartLSP is executing.
To make all this work the dictionary must be passed as argument lsp_config to function ale#linter#Define.
I've passed a value manually to check my hypothesis.
diff --git a/ale_linters/python/pyls.vim b/ale_linters/python/pyls.vim
index eceb63f6..7b00cc1f 100644
--- a/ale_linters/python/pyls.vim
+++ b/ale_linters/python/pyls.vim
@@ -44,4 +44,5 @@ call ale#linter#Define('python', {
 \   'command_callback': 'ale_linters#python#pyls#GetCommand',
 \   'project_root_callback': 'ale#python#FindProjectRoot',
 \   'completion_filter': 'ale#completion#python#CompletionItemFilter',
+\   'lsp_config': {'pyls': {'plugins': {'pycodestyle': {'enabled': 0}}}},
 \})

I've prepared a patch #2088 to pass more args to pyls. Now debug logging can be forced by a few strings in init.vim:
let g:ale_python_pyls_extra_args = [
\   '-vv',
\   '--log-file', expand('~/pyls.log')
\]

Now I can see that settings are passed correctly
2018-11-18 23:46:40,924 UTC - DEBUG - jsonrpc.endpoint - Handling request from client {'method': 'workspace/didChangeConfiguration', 'jsonrpc': '2.0', 'id': 2, 'params': {'settings': {'pyls': {'plugins': {'pycodestyle': {'enabled': 0}}}}}}
2018-11-18 23:46:40,924 UTC - INFO - pyls.config.config - Updated settings to {'plugins': {'pycodestyle': {'enabled': 0}}}

The main problem I have at this point is passing boolean values. How can I we manage this?

For Boolean values in a dictionary, you should use v:true or v:false, like {'enableWhatever': v:true}. See :help v:true.


Flags For activating AVX Bazel Build CPP Windows

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): Source
TensorFlow version: 1.12.0
Python version: 3.6
Installed using virtualenv? pip? conda?: conda
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

Describe the problem
I successfully managed to build a TensorFlow library for CPP, Windows, but that was without AVX instructions. I want to enable the AVX instructions.  I want to take advantage of it and improve my inference speed.
Provide the exact sequence of commands/steps that you executed before running into the problem
I tried the following flags, but during the build, it doesn't recognize it. Looks like that is only valid for Python package.

bazel build -c opt --copt=-mavx --copt=-mavx2 --copt=-mfma --copt=-mfpmath=both --copt=-msse4.2

Any other info / logs: Error/Warning on the build
cl : Command line warning D9002 : ignoring unknown option '-mavx'
cl : Command line warning D9002 : ignoring unknown option '-mavx2'
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

@amitpandey2194
Just verify, did you the follow the instructions mentioned in this link.
Please take a look at the tested build configuration of Tensorflow 1.12. Thanks!

Yeah I verify I that I used above mentioned build steps.
I have already build tensor flow library, but that is without avx avx2 instructions. I want to know how to build one for cpp with avx instructions enabled using bazel build. Which flags to use?

@amitpandey2194
Does your cpu support AVX instructions?
Please, see hardware requirements.Thanks!

Yeah, it does. Its intel core i5

Afaik, windows compiler flags are with /, not with -. You should consult the flag documentation for the Windows compiler you are using. -copt options get passed verbatim to the compiler.

@mihaimaruseac I am using bazel for building the library. Then what flags should I use for incorporating the avx and avx2 build?
Can you please also point me to the documentation you are referring to?

Please track also https://github.com/tensorflow/tensorflow/issues/42960

@amitpandey2194 To confirm, initial issue description mentions conda, although it's an issue about building from source. Is conda involved here to any capacity?
Is the TF 1.12.0 version number correct, trying to build from a ~2 years old source? Doing this requires a rather old bazel (0.15) and MSVC (v2015). Might be worth considering the option of migrating to TF2.2 or 2.3 :) I've built successfully with AVX2 enabled under Windows since TF2.0 release, for every point release.
Unless the conda is part of the build recipe, normally the configuration parameters are passed using python configure.py. For Windows, /arch:AVX2 optimization flag enables AVX2.

You should be able to use --config flags: https://cs.opensource.google/tensorflow/tensorflow/+/master:.bazelrc;l=368-369

You should be able to use --config flags: https://cs.opensource.google/tensorflow/tensorflow/+/master:.bazelrc;l=368-369


Help Keyword doesn't list all available Help Entries.

When I enter "help" it does not show all Help keywords.
If I set isRelevantForAllStrings for the HelpType to return true it works, but than the fuzzy matching for e.g. "help do" is broken. I'm no expert with the new FuzzyMatcher, but I think this should be an easy fix. 😃
(We should also add a test for this behaviour)

This should be fixed by #103.


Why GatherOperation needs a backward method?

Hello, Erik. Thanks for sharing your pytorch implementation of Pointnet2.  Actually, I want to know why we need a backward method for GatherOperation in ./utils/pointnet2_utils.py. I believe there is no gradient in gather_pointt function, and do we really need gather_point_grad function?
class GatherOperation(Function):
    @staticmethod
    def forward(ctx, features, idx):
        # type: (Any, torch.Tensor, torch.Tensor) -> torch.Tensor
        r"""
        Parameters
        ----------
        features : torch.Tensor
            (B, C, N) tensor
        idx : torch.Tensor
            (B, npoint) tensor of the features to gather
        Returns
        -------
        torch.Tensor
            (B, C, npoint) tensor
        """

        _, C, N = features.size()

        ctx.for_backwards = (idx, C, N)

        return _ext.gather_points(features, idx)

    @staticmethod
    def backward(ctx, grad_out):
        idx, C, N = ctx.for_backwards

        grad_features = _ext.gather_points_grad(grad_out.contiguous(), idx, N)
        return grad_features, None

If I recall correctly, it isn't needed at all for PointNet++ (i.e. that code path is never used), but it is simple enough to include, so I did, incase someone needs it.

Thanks for your reply.
But if we did not need backward, should we set backward method to None, like in furthest sampling?
class FurthestPointSampling(Function):
    @staticmethod
    def forward(ctx, xyz, npoint):
        # type: (Any, torch.Tensor, int) -> torch.Tensor
        r"""
        Uses iterative furthest point sampling to select a set of npoint features that have the largest
        minimum distance
        Parameters
        ----------
        xyz : torch.Tensor
            (B, N, 3) tensor where N > npoint
        npoint : int32
            number of features in the sampled set
        Returns
        -------
        torch.Tensor
            (B, npoint) tensor containing the set
        """
        return _ext.furthest_point_sampling(xyz, npoint)

    @staticmethod
    def backward(xyz, a=None):
        return None, None

furthest_point_sample = FurthestPointSampling.apply

charlesq34/pointnet2 also included the graduate function for gather point in sampling operation.
So I wonder if there is a reason.

The gradient for furthest point sampling is well defined for either input, that is why it returns None for both inputs.

I get it. If I am right. I believe GatherOpearion needs a backward op to make sure gradient can be passed through in backward prop, just like max pooling needs a backward op.

Yep!


refactor(batch): register-style executor builder

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#19742
#19741  👈 (View in Graphite)
#19731
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


SWA API Proxy is not passing X-Forwarded-Host to linked ContainerApp when proxying a direct URL

I have a static web app that is API linked to an Azure Container App which is hosting an ASP.NET Core web app.
When I redirect to an authentiction route in my app like https://[swacustomdomain]/api/auth/login/[provider] it routes to the backend correctly, but because there is no X-FORWARDED-HOST it is using is my container app host, not my SWA host for redirects so I end up with a redirect_url in the authentication request to the external provider (e.g. AAD) that is using the container app host not the SWA host as well as any other redirects I make.
If I then, in my ASP.NET app do the following, passing in the headers 'x-appservice-proto' and 'disguised-host' (this is what I can see in the request headers from logging them out in the container app):
builder.Services.Configure<ForwardedHeadersOptions>(options =>
        {
            // If we have specific headers configured, user them
            var config = builder.Configuration.GetSection("ForwardHeaderNames");

            var protocolForwardHeader = config["Protocol"];
            if (!string.IsNullOrEmpty(protocolForwardHeader))
            {
                options.ForwardedProtoHeaderName= protocolForwardHeader;
            }

            var hostForwardHeader = config["Host"];
            if (!string.IsNullOrEmpty(hostForwardHeader))
            {
                options.ForwardedHostHeaderName = hostForwardHeader;
            }

            options.ForwardedHeaders = ForwardedHeaders.XForwardedHost | ForwardedHeaders.XForwardedProto;
            options.ForwardLimit = 2;
            options.KnownNetworks.Clear();
            options.KnownProxies.Clear();
        });

I then get the correct redirect_uri passed out to the external provider, but all the cookies the authentication process is setting or I am trying to set, pook to be being set for the container app host, not the SWA host.
System.Exception: An error was encountered while handling the remote login.
 ---] System.Exception: Correlation failed.
   --- End of inner exception stack trace ---
   at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1.HandleRequestAsync()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
   at Serilog.AspNetCore.RequestLoggingMiddleware.Invoke(HttpContext httpContext)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)

Expected behavior
This is all seeming to be much harder that I would expect to get it to work.
The expected behaviour is that the X-FORWARDED-HOST header is passed through to be used correctly by ASP.NET Core
Additional context
Container App Log Stream:
2023-01-16T22:19:28.805733753Z 2023-01-16 22:19:28.805 Debug - Connection id "0HMNO1PL2F40U" accepted.
2023-01-16T22:19:28.806111385Z 2023-01-16 22:19:28.805 Debug - Connection id "0HMNO1PL2F40U" started.
2023-01-16T22:19:28.806532959Z 2023-01-16 22:19:28.806 Information - Request starting HTTP/1.1 GET http://[ca_url].azurecontainerapps.io/api/auth/login/Microsoft - 0
2023-01-16T22:19:28.806549450Z 2023-01-16 22:19:28.806 Debug - No response compression available, the Accept-Encoding header is missing or invalid.
2023-01-16T22:19:28.806556252Z 2023-01-16 22:19:28.806 Debug - The request path /api/auth/login/Microsoft does not match a supported file type
2023-01-16T22:19:28.806560440Z 2023-01-16 22:19:28.806 Debug - 1 candidate(s) found for the request path '/api/auth/login/Microsoft'
2023-01-16T22:19:28.807508144Z 2023-01-16 22:19:28.806 Debug - Endpoint 'ai.App.Api.Endpoints.Endpoints.AuthEndpoints.ExternalLogin (ai.app.api.endpoints)' with route pattern 'api/auth/login/{provider}' is valid for the request path '/api/auth/login/Microsoft'
2023-01-16T22:19:28.808093222Z 2023-01-16 22:19:28.806 Debug - Request matched endpoint 'ai.App.Api.Endpoints.Endpoints.AuthEndpoints.ExternalLogin (ai.app.api.endpoints)'
2023-01-16T22:19:28.808362533Z 2023-01-16 22:19:28.806 Debug - Static files was skipped as the request already matched an endpoint.
2023-01-16T22:19:28.808881448Z 2023-01-16 22:19:28.807 Debug - AuthenticationScheme: Cookies was not authenticated.
2023-01-16T22:19:28.809150378Z 2023-01-16 22:19:28.807 Information - Executing endpoint 'ai.App.Api.Endpoints.Endpoints.AuthEndpoints.ExternalLogin (ai.app.api.endpoints)'
2023-01-16T22:19:28.809169814Z 2023-01-16 22:19:28.807 Information - Route matched with {action = "ExternalLogin", controller = "AuthEndpoints"}. Executing controller action with signature Microsoft.AspNetCore.Http.IResult ExternalLogin(System.String) on controller ai.App.Api.Endpoints.Endpoints.AuthEndpoints (ai.app.api.endpoints).
2023-01-16T22:19:28.809175425Z 2023-01-16 22:19:28.807 Debug - Execution plan of authorization filters (in the following order): ["None"]
2023-01-16T22:19:28.809179553Z 2023-01-16 22:19:28.807 Debug - Execution plan of resource filters (in the following order): ["None"]
2023-01-16T22:19:28.809184251Z 2023-01-16 22:19:28.807 Debug - Execution plan of action filters (in the following order): ["Microsoft.AspNetCore.Mvc.ModelBinding.UnsupportedContentTypeFilter (Order: -3000)", "Microsoft.AspNetCore.Mvc.Infrastructure.ModelStateInvalidFilter (Order: -2000)"]
2023-01-16T22:19:28.809188249Z 2023-01-16 22:19:28.807 Debug - Execution plan of exception filters (in the following order): ["None"]
2023-01-16T22:19:28.809198498Z 2023-01-16 22:19:28.807 Debug - Execution plan of result filters (in the following order): ["Microsoft.AspNetCore.Mvc.Infrastructure.ClientErrorResultFilter (Order: -2000)"]
2023-01-16T22:19:28.809202946Z 2023-01-16 22:19:28.807 Debug - Executing controller factory for controller ai.App.Api.Endpoints.Endpoints.AuthEndpoints (ai.app.api.endpoints)
2023-01-16T22:19:28.809206513Z 2023-01-16 22:19:28.807 Debug - Executed controller factory for controller ai.App.Api.Endpoints.Endpoints.AuthEndpoints (ai.app.api.endpoints)
2023-01-16T22:19:28.809210400Z 2023-01-16 22:19:28.807 Debug - Attempting to bind parameter 'provider' of type 'System.String' ...
2023-01-16T22:19:28.809214227Z 2023-01-16 22:19:28.807 Debug - Attempting to bind parameter 'provider' of type 'System.String' using the name 'provider' in request data ...
2023-01-16T22:19:28.809218615Z 2023-01-16 22:19:28.807 Debug - Done attempting to bind parameter 'provider' of type 'System.String'.
2023-01-16T22:19:28.809222292Z 2023-01-16 22:19:28.807 Debug - Done attempting to bind parameter 'provider' of type 'System.String'.
2023-01-16T22:19:28.809226710Z 2023-01-16 22:19:28.807 Debug - Attempting to validate the bound parameter 'provider' of type 'System.String' ...
2023-01-16T22:19:28.809230617Z 2023-01-16 22:19:28.807 Debug - Done attempting to validate the bound parameter 'provider' of type 'System.String'.
2023-01-16T22:19:28.809234364Z 2023-01-16 22:19:28.807 Information - Executing action method ai.App.Api.Endpoints.Endpoints.AuthEndpoints.ExternalLogin (ai.app.api.endpoints) - Validation state: Valid
2023-01-16T22:19:28.809238542Z 2023-01-16 22:19:28.807 Debug - [ExternalLogin] ] Client URL: https://[swa_url]
2023-01-16T22:19:28.809242570Z 2023-01-16 22:19:28.807 Debug - [ExternalLogin] ] Redirect Url: https://[swa_url]/api/auth/signin/Microsoft
2023-01-16T22:19:28.809247369Z 2023-01-16 22:19:28.807 Information - Executed action method ai.App.Api.Endpoints.Endpoints.AuthEndpoints.ExternalLogin (ai.app.api.endpoints), returned result Microsoft.AspNetCore.Mvc.HttpActionResult in 0.0442ms.
2023-01-16T22:19:28.809251476Z 2023-01-16 22:19:28.807 Information - Executing ChallengeResult with authentication schemes (["Microsoft"]).
2023-01-16T22:19:28.809674583Z 2023-01-16 22:19:28.808 Debug - HandleChallenge with Location: https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=cb85a04d-1754-4a21-8396-565f42abf4dd&response_type=code&redirect_uri=https%3A%2F%2F[SWAHOST]%2Fapi%2Fauth%2Fsignin-microsoft&scope=https%3A%2F%2Fgraph.microsoft.com%2Fuser.read&code_challenge=pfmxggldRgT7nqbge88f-bwm3ivUjiSrdw9SiFAnl0E&code_challenge_method=S256&state=CfDJ8PThRPk0fLVHnuW-wqx7dL51GAQpCn35ld7D4LOeDMSVBR-kCPPsbeAjs4F3vEZ-33mU8ESHaGpSt2bcldcNbpj4fIOmhe1jCoefdBhhRu6FjXIvU7MlazbfJZ2RZg2dhZDM2rgCu30ay1VVE0JH_o935u7rNwkftp8lvhx4Bl-rqBEeG-ALDmFmrpPAORzRKM7lSZ48hKltr-Q0hcN_yVJwy9sf-l_4UGOcr2Lf8glu2CHKNRoGk6AtDY3I56xaCmAj58HEwbx2Y1Gr1BzxW2fIm7B5GwVrF7_xALGnm6pDLXN-smCQeizlnWPLWYE80zFnZgMShPnMXagkKRllo-CCPCGZtFHhXOH-z5TiF848; and Set-Cookie: .AspNetCore.Correlation.LCbKxzwLbPD39bXbCXm3xnRD4SSpJ9oeQZhdWZRd7nw=N; expires=Mon, 16 Jan 2023 22:34:28 GMT; path=/api/auth/signin-microsoft; secure; samesite=none; httponly.
2023-01-16T22:19:28.809970003Z 2023-01-16 22:19:28.808 Information - AuthenticationScheme: Microsoft was challenged.
2023-01-16T22:19:28.809977196Z 2023-01-16 22:19:28.808 Information - Executed action ai.App.Api.Endpoints.Endpoints.AuthEndpoints.ExternalLogin (ai.app.api.endpoints) in 0.9118ms
2023-01-16T22:19:28.809981183Z 2023-01-16 22:19:28.808 Information - Executed endpoint 'ai.App.Api.Endpoints.Endpoints.AuthEndpoints.ExternalLogin (ai.app.api.endpoints)'
2023-01-16T22:19:28.809985181Z 2023-01-16 22:19:28.808 Information - HTTP GET /api/auth/login/Microsoft responded 302 in 2.1439 ms
2023-01-16T22:19:28.809988277Z 2023-01-16 22:19:28.808 Debug - Connection id "0HMNO1PL2F40U" completed keep alive response.
2023-01-16T22:19:28.809992194Z 2023-01-16 22:19:28.808 Information - Request finished HTTP/1.1 GET http://[ca_url].azurecontainerapps.io/api/auth/login/Microsoft - 0 - 302 0 - 2.4075ms
[removed for brevity]
2023-01-16T22:19:50.543569987Z 2023-01-16 22:19:50.543 Information - Request starting HTTP/1.1 GET http://[ca_url].azurecontainerapps.io/api/auth/signin-microsoft?code=M.R3_BAY.34fe2b73-b897-6cf5-1ccb-9c04eefa7749&state=CfDJ8PThRPk0fLVHnuW-wqx7dL51GAQpCn35ld7D4LOeDMSVBR-kCPPsbeAjs4F3vEZ-33mU8ESHaGpSt2bcldcNbpj4fIOmhe1jCoefdBhhRu6FjXIvU7MlazbfJZ2RZg2dhZDM2rgCu30ay1VVE0JH_o935u7rNwkftp8lvhx4Bl-rqBEeG-ALDmFmrpPAORzRKM7lSZ48hKltr-Q0hcN_yVJwy9sf-l_4UGOcr2Lf8glu2CHKNRoGk6AtDY3I56xaCmAj58HEwbx2Y1Gr1BzxW2fIm7B5GwVrF7_xALGnm6pDLXN-smCQeizlnWPLWYE80zFnZgMShPnMXagkKRllo-CCPCGZtFHhXOH-z5TiF848 - 0
2023-01-16T22:19:50.543997332Z 2023-01-16 22:19:50.543 Debug - No response compression available, the Accept-Encoding header is missing or invalid.
2023-01-16T22:19:50.544267475Z 2023-01-16 22:19:50.543 Debug - The request path /api/auth/signin-microsoft does not match a supported file type
2023-01-16T22:19:50.544558176Z 2023-01-16 22:19:50.543 Debug - No candidates found for the request path '/api/auth/signin-microsoft'
2023-01-16T22:19:50.544857192Z 2023-01-16 22:19:50.543 Debug - Request did not match any endpoints
2023-01-16T22:19:50.545132133Z 2023-01-16 22:19:50.543 Debug - The request path  does not match the path filter
2023-01-16T22:19:50.546238681Z 2023-01-16 22:19:50.546 Warning - '.AspNetCore.Correlation.LCbKxzwLbPD39bXbCXm3xnRD4SSpJ9oeQZhdWZRd7nw' cookie not found.
2023-01-16T22:19:50.546254521Z 2023-01-16 22:19:50.546 Information - Error from RemoteAuthentication: Correlation failed..
2023-01-16T22:19:50.547234233Z 2023-01-16 22:19:50.546 Error - HTTP GET /api/auth/signin-microsoft responded 500 in 2.9298 ms
2023-01-16T22:19:50.547249441Z System.Exception: An error was encountered while handling the remote login.
2023-01-16T22:19:50.547254861Z  ---] System.Exception: Correlation failed.
2023-01-16T22:19:50.547258859Z    --- End of inner exception stack trace ---
2023-01-16T22:19:50.547262435Z    at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1.HandleRequestAsync()
2023-01-16T22:19:50.547266352Z    at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
2023-01-16T22:19:50.547270200Z    at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
2023-01-16T22:19:50.547297400Z    at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
2023-01-16T22:19:50.547302359Z    at Serilog.AspNetCore.RequestLoggingMiddleware.Invoke(HttpContext httpContext)
2023-01-16T22:19:50.547307219Z    at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)
2023-01-16T22:19:50.547310935Z 2023-01-16 22:19:50.546 Error - An unhandled exception has occurred while executing the request.
2023-01-16T22:19:50.547314673Z System.Exception: An error was encountered while handling the remote login.
2023-01-16T22:19:50.547318329Z  ---] System.Exception: Correlation failed.
2023-01-16T22:19:50.547321796Z    --- End of inner exception stack trace ---
2023-01-16T22:19:50.547325252Z    at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1.HandleRequestAsync()
2023-01-16T22:19:50.547328749Z    at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
2023-01-16T22:19:50.547332526Z    at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
2023-01-16T22:19:50.547336173Z    at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
2023-01-16T22:19:50.547341152Z    at Serilog.AspNetCore.RequestLoggingMiddleware.Invoke(HttpContext httpContext)
2023-01-16T22:19:50.547344778Z    at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)
2023-01-16T22:19:50.548970910Z 2023-01-16 22:19:50.548 Debug - Connection id "0HMNO1PL2F40U" completed keep alive response.
2023-01-16T22:19:50.548984896Z 2023-01-16 22:19:50.548 Information - Request finished HTTP/1.1 GET http://[ca_url].azurecontainerapps.io/api/auth/signin-microsoft?code=M.R3_BAY.34fe2b73-b897-6cf5-1ccb-9c04eefa7749&state=CfDJ8PThRPk0fLVHnuW-wqx7dL51GAQpCn35ld7D4LOeDMSVBR-kCPPsbeAjs4F3vEZ-33mU8ESHaGpSt2bcldcNbpj4fIOmhe1jCoefdBhhRu6FjXIvU7MlazbfJZ2RZg2dhZDM2rgCu30ay1VVE0JH_o935u7rNwkftp8lvhx4Bl-rqBEeG-ALDmFmrpPAORzRKM7lSZ48hKltr-Q0hcN_yVJwy9sf-l_4UGOcr2Lf8glu2CHKNRoGk6AtDY3I56xaCmAj58HEwbx2Y1Gr1BzxW2fIm7B5GwVrF7_xALGnm6pDLXN-smCQeizlnWPLWYE80zFnZgMShPnMXagkKRllo-CCPCGZtFHhXOH-z5TiF848 - 0 - 500 - text/html;+charset=utf-8 5.0435ms

I have the exact same issue, did you ever resolve this @demyte ?

I am missing this as well, which is a real shame. If SWA proxy added an X-Forwarded-For header to the linked API, then multi-tenancy with a SWA+API combo would be very easy and clean.


Debian packaging instructions just create an empty .deb with no dependencies that creates an /opt/ship/bin folder with nothing in it.

See title. Linux build instructions otherwise work fine on Debian Stable.

the zip is empty too!


Ubuntu 16.04 images cannot be pulled

The CI image repository no longer has the CI images that are referenced by .travis.yml anymore. It appears that the clean up script is now too aggressive in deleting them.

I'll be able to look into this next week at the earliest.


Side-by-Side view to compare original and revised applications

This is not a bug. A few team members find it difficult to read revised applications.

Side-by-Side view to compare original and revised text OR 2) change current green and pink highlight over text to increase readability of revised text.

Duplicate of #748


Incomplete relabelling of trajectories in HER

Hi,
First, thanks a lot for releasing such a nice repository. I have been using it for a few months now and I appreciate that it is quite well written and most of the code is self explanatory. I learned a lot just by using it.
I am using SAC-HER and got a lot of divergence issues which I fixed in the end. One of the main problem came from the relabelling of samples in the buffer: https://github.com/vitchyr/rlkit/blob/90195b24604f513403e4d0fe94db372d16700523/rlkit/data_management/obs_dict_replay_buffer.py#L228-L239
Given a batch, a set of new rewards is computed according to the updated set of goals. However the terminals are not updated, whereas some states might be terminal given the new goal.
And this has its importance in the Bellman update where the terminals variable appear https://github.com/vitchyr/rlkit/blob/90195b24604f513403e4d0fe94db372d16700523/rlkit/torch/sac/sac.py#L128
If the reward if of the form -distance(state, goal) and an episode is only finished because of the maximum path length, then not updating the terminals will have little impact. It may be why this bug passed silently. However I am working with a spare reward which is 1 if distance(state, goal) < epsilon. And in this case, if terminals are not updated then the Q-function blows up. Indeed, if we assume that target_q_values = 1 at the goal, if terminals = 0 then q_target = 2, at the next iteration q_target = 3 and so on. If terminals = 1, i.e. if the state is terminal according to the resampled goal then q_target = 1.
So in my fork of your repository, I replaced:
new_rewards = self.env.compute_rewards(
                new_actions,
                new_next_obs_dict,
            )

by
new_rewards, new_terminals = self.env.compute_rewards(
                new_actions,
                new_next_obs_dict,
            )

where terminals is 1 if distance(state, goal) < epsilon in my case. This fixed the Q-function blow-up issue.

I hope this makes sense, I did not propose a PR because it will break compatibility with existing environments.

That's a good point! That also makes a lot of sense as to why updating the termination conditioned would help.
One thing that's ambiguous is whether or not the episode should end when the state is reached. Some authors assume that it should while others assume that it shouldn't. For example, the HER code released by the authors don't seem to update the termination condition.
At this point, I'm not sure if I'd feel comfortable making this change for everyone, since it may not be the intended behavior and it requires changing the compute_rewards interface. Perhaps if you make it an option inside of the HER code in a PR, that could be nice a way to make it optional without requiring the interface to change too drastically.
For now I'll pin this issue so that it has more visibility, and feel free to make a PR as suggested above.

Thanks @vitchyr for this insightful answer.

One thing that's ambiguous is whether or not the episode should end when the state is reached.
Agreed. Indeed, HER authors have tested the algorithm on environments like gym fetch where the episode terminate only once the horizon is reached. Also, both in the sparse and dense setting they use rewards that are negative and converge to 0 when the state is getting closer to the goal, which avoid any obvious blow up issues.

I will probably change my own environments to match this behavior.

@rstrudel Did you find that the horizon termination made a difference in your experiments? (Only that part, not the -1 and 0 part)
Or if anyone knows if this is a big factor/ point me towards some papers that address this, please let me know

@bycn for my application which is neural motion planning, it did make a difference. In my experiments I got the best results setting the termination when the goal is reached and providing a positive reward in this case. It might be quite experiment dependent however.


Documentation problem

The examples from 'filesystem operations' onwards do not include the list indexes in the results.

Fixed as at c4b838b.


Release with JWT support

Hi,
Would it be possible to have a tagged release with JWT support? :)

Yes, it's available now in 0.3.0 version

Thank you!


Split isFulfilledData into isFulfilledBarData and isFulfilledLineData to allow WhitespaceData with extra properties

Type of PR: enhancement
PR checklist:

[x] Addresses an existing issue: fixes #1526
[ ] Includes tests
[ ] Documentation update

Overview of change:
isFulfilledData was used to validate both OhlcData and SingleValueData, but based on different keys. This will cause a false assertion to be thrown when valid WhitespaceData is passed but also includes extra keys which cause it to be considered to be "fulfilled" but for the other series type. Also, this validation only occurs in development.
This PR introduces isFulfilledBarData for OhlcData, and isFulfilledLineData for SingleValueData. Specifically only considering the properties open vs value instead of either being present.
Is there anything you'd like reviewers to focus on?
In the function _convertMouseParams, instead of calling isFulfilled*Data directly, it could reuse the method from before. getChecker(seriesType)(data). Also isFulfilledData could be removed and merged into checkBarItem/checkLineItem and return a boolean so _convertMouseParams can be asserted the same. This seemed beyond the initial intention, let me know.

@SlicedSilver any other thoughts on this?


Fix non-critical typos in comments and JavaDoc

fix typos in several local variables.
Please, look closely at changes in those files:

org/apache/commons/lang3/text/StrSubstitutorTest.java (Anchor)
org/apache/commons/lang3/exception/ExceptionUtils.java (Anchor)

Coverage increased (+0.02%) to 93.67% when pulling aa75c23b2e51c8d42730c8b410e6a7148a7bb094 on Abrasha:fix/non-critical-typos into a49ea7a65b7990b3e6e625bc8bfff7396ee49300 on apache:master.

Great, thank you!


Add scrolling to editors

Certain states that have a lot of information have so much text in the editor that it extends beyond the window’s size. The editors should have vertical scrolling to allow access to all editor text.

Taking care of this at the same time as #74


SUBMARINE-1099. Replace Traefik with Istio in helm-charts

What is this PR for?

Replace Traefik with Istio as gateway.
What type of PR is it?
[Feature]
Todos

[x] - Fix static files
[ ] - Fix minio request
[ ] - Fix experiment request

What is the Jira issue?

https://issues.apache.org/jira/projects/SUBMARINE/issues/SUBMARINE-1099?filter=allissues
How should this be tested?

Screenshots (if appropriate)

Questions:

Do the license files need updating? No
Are there breaking changes for older versions? No
Does this need new documentation? No

Unfortunately, I failed to completely replace Traefik with Istio, some endpoints seem broken. However, I don't understand why. Therefore, I think I need to hand off this issue to another person.

Why not user helm dependency to import istio?
Maybe we should keep the possibility of two kinds of ingress coexisting, and let users choose their own suitable ingress. In addition, if the user's k8s platform already has its own ingress controller, there is no relevant solution at present.


Row header

Hi, I need to create a header (not changing A,B,C...), but adding a row as a header bellow the columns. They need to be edited as well and I need it to be sticky. Is this possible?
Also is it possible to have metadata for all fields, so I can save the spreadsheet in database but not in a json format...?

Hi,
For your first question, you have nestedHeader, you can look that in this page : https://bossanova.uk/jspreadsheet/v4/examples/nested-headers
If that isn't that, can you explain with image ?
for your second question, you have meta for cell : you can look that in this page : https://bossanova.uk/jspreadsheet/v4/examples/meta-information
If you use persistence property, you can defined onbeforesave in property for add metadata in data sended to your server
if you use pro version, it's the same behavior.

Hi,
You can insertRow with style and/or add class for first row with position:sticky;top: 0; but with this configuration, when you get data/json you have a row header on your data.
I will add in new post (today) several example for add this row
currently no, you need to merge informations from getJson and getMeta


line break too early

BookStack 0.30.0

you can slightly adjust the styles and make it more beautiful
extra padding here

there is a lot of extra space here

do at least this way

Thanks for reporting @Statium.
I've made some changes in 328d2514c4873968888022fb8dbf8ca792bbad52 to make these boxes flex to the content instead of fit to a fixed 2/3 + 1/3 layout. These changes will be part of the next patch release.


Analyzer type equality is wrong on nested typedefs.

The attached file has two assignments statements each assigning a rhs to a lhs of an incompatible type.  The two lhs variables have types which are equal up to expansion of typedefs, but the analyzer only warns on one of the assignments.  Based on some printf debugging, I believe that there may be a bug in the element type equality in the presence of nested typedef instantations.
leafp@leafp-linux:~$ ./dart/dart-sdk/bin/dartanalyzer --version
dartanalyzer version 1.8.3
leafp@leafp-linux:~$ ./dart/dart-sdk/bin/dartanalyzer tmp/dart_test/bin/main.dart
Analyzing [tmp/dart_test/bin/main.dart]...
[warning] A value of type 'Function2 (/usr/local/google/home/leafp/tmp/dart_test/bin/main.dart)' cannot be assigned to a variable of type 'Function2 (/usr/local/google/home/leafp/tmp/dart_test/bin/main.dart)' (/usr/local/google/home/leafp/tmp/dart_test/bin/main.dart, line 19, col 12)
[hint] The value of the local variable 'left' is not used (/usr/local/google/home/leafp/tmp/dart_test/bin/main.dart, line 16, col 63)
1 warning found.

Attachment:
main.dart (481 Bytes)

Looks like I forgot to close the bug when I fixed it on June 1.  I've just confirmed that it indeed still fixed.


providing a ui.label_trunc() and ui.label_wrap() and ui.label_rich()

Close #3900
This is an example.
Please modify and use it as you wish.

No, I want to keep https://docs.rs/egui/latest/egui/struct.Ui.html short with only a few convenience helpers for the most used widgets


Documentation error about standard function IF

There is an error on the documentation related to the standard function IF.
The description of the function and the example provided uses the comma (,) as operator separator. It seems that the valid separator is ;
Therefore the correct information for the IF function must be as follow:

if(A1; A2; A3) -> GOOD
if(A1, A2, A3) -> BAD

The example provided must be changed to:
engine.Calculate("if(var1 < var2; 23; 8)", variables);

This depends on your culture settings (so on your machine. Try putting Jace in invariant culture mode:
CalculationEngine engine = new CalculationEngine(CultureInfo.InvariantCulture);


[DEP-197] Bump SDK version to 2.6.1

Description
Release 2.6.1
References
Deployment ticket: DEP-197
Release content: Release 2.6.1
Tagged
@lampkicking/android-dev

LGTM


Update CLI authentication to store login

We use LDAP for authentication. I've been sharing this one-liner with all of our internal users:
export ST2_AUTH_TOKEN=$(st2 auth `whoami` -t)

As a new user this is definitely non-intuitive. It'd be really nice to support a mechanism like
st2 login

While you could require your username, you could also just default to the current user name since thats how many (most?) corporate environments would be setup with ldap anyway.
Or you can prompt with default like:
$ st2 login
Username [default <user>]: <prompt for input>
Password: <prompt for input>

Or skip straight to username and optional password
$ st2 login `whoami` -p $PASSWORD

Lots of ways to skin the cat. But the business objective here is to make it easier for new/occasional end-users to authenticate.

@codyaray It seems like much of what you suggested for st2 login is already supported by the existing st2 auth option - the only thing that's missing is that st2 auth doesn't export to ST2_AUTH_TOKEN by default.
If st2 auth had an option to auto-export this, would that solve this problem in your mind?

Yep. Just didn't know if you wanted to piggyback or not. Either way works
for me. :)
-Cody
On Dec 13, 2016 7:43 PM, "Matt Oswalt"<EMAIL_ADDRESS>wrote:

@codyaray https://github.com/codyaray It seems like much of what you
suggested for st2 login is already supported by the existing st2 auth
option - the only thing that's missing is that st2 auth doesn't export to
ST2_AUTH_TOKEN by default.
If st2 auth had an option to auto-export this, would that solve this
problem in your mind?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/StackStorm/st2/issues/3110#issuecomment-266918014,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACsHuJXzWDbPsul88lAe0M2ormSKvW0ks5rH0mwgaJpZM4LMC-D
.

@codyaray The difficulty is that st2client won't be able to modify the environment of the parent shell due to the way environments work in Linux. This is why many tools that use this approach recommend you set the env yourself first.
We may be able to do something a little different to accomplish the same goal, however. Stay tuned here, I'll let you know if I come up with anything

My thought would be writing the token to disk with a TTL using
filecachetools or something
On Dec 14, 2016 11:46 AM, "Matt Oswalt"<EMAIL_ADDRESS>wrote:

@codyaray https://github.com/codyaray The difficulty is that st2client
won't be able to modify the environment of the parent shell due to the way
environments work in Linux. This is why many tools that use this approach
recommend you set the env yourself first.
We may be able to do something a little different to accomplish the same
goal, however. Stay tuned here, I'll let you know if I come up with anything
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/StackStorm/st2/issues/3110#issuecomment-267103031,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACsHtF8rPFRkLgRCK514H8yBFqo4qzJks5rICuPgaJpZM4LMC-D
.

@codyaray See #3123 - hopefully that is going in the right direction.

awesome!
On Thu, Dec 15, 2016 at 7:39 PM, Matt Oswalt<EMAIL_ADDRESS>wrote:

@codyaray https://github.com/codyaray See #3123
https://github.com/StackStorm/st2/pull/3123 - hopefully that is going
in the right direction.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/StackStorm/st2/issues/3110#issuecomment-267495419,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACsHirQsL1EwEzPb98AyIOQHXNfi77sks5rIevqgaJpZM4LMC-D
.

@codyaray Apologies for the delay on this. Lots of other things came up during the holiday season, but I wanted to make sure this got in before our next release. #3123 has been merged - I encourage you to check out the 2.2 release when it comes out and try the new feature.
Thanks for reporting this!

Thank you!
On Tue, Feb 7, 2017 at 12:10 PM, Matt Oswalt<EMAIL_ADDRESS>wrote:

@codyaray https://github.com/codyaray Apologies for the delay on this.
Lots of other things came up during the holiday season, but I wanted to
make sure this got in before our next release. #3123
https://github.com/StackStorm/st2/pull/3123 has been merged - I
encourage you to check out the 2.2 release when it comes out and try the
new feature.
Thanks for reporting this!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/StackStorm/st2/issues/3110#issuecomment-278089026,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACsHmy68ZiRrgSKpESpl1M5BK25c10pks5raLOJgaJpZM4LMC-D
.


LabProtocol profile works only against LabProtocol DRAFT v0.5 not v0.8

Okay (newest version in subfolder):
https://github.com/BioSchemas/specifications/blob/master/LabProtocol/jsonld/type/LabProtocol_v0.5-DRAFT.jsonld
Not Okay (newest version overall):
https://github.com/BioSchemas/specifications/blob/master/LabProtocol/jsonld/LabProtocol_v0.8-DRAFT.json
What's the truth here and why are these two types so drastically different?

I don't know what you mean. The first one is the type specification, the other one the bioschemas profile. Our profile only has to be coherent with the type, so we're fine.


[libpq] x64-osx-dynamic build error

Host Environment

OS: macOS  12.0.1
Compiler: Apple clang version 13.0.0 (clang-13<IP_ADDRESS>)

To Reproduce
Steps to reproduce the behavior:
vcpkg install libpq:x64-osx-dynamic
Failure logs
Computing installation plan...
The following packages will be built and installed:
libpq[bonjour,core,openssl,zlib]:x64-osx-dynamic -> 12.9#1
Detecting compiler hash for triplet x64-osx-dynamic...
Restored 0 packages from /Users/Apple/.cache/vcpkg/archives in 27.13 us. Use --debug to see more details.
Starting package 1/1: libpq:x64-osx-dynamic
Building package libpq[bonjour,core,openssl,zlib]:x64-osx-dynamic...
-- Using community triplet x64-osx-dynamic. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: /Users/Apple/vcpkg/triplets/community/x64-osx-dynamic.cmake
-- Using cached postgresql-12.9.tar.bz2.
-- Cleaning sources at /Users/Apple/vcpkg/buildtrees/libpq/src/tgresql-12-07bd5aa2da.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /Users/Apple/vcpkg/downloads/postgresql-12.9.tar.bz2
-- Applying patch patches/windows/install.patch
-- Applying patch patches/windows/win_bison_flex.patch
-- Applying patch patches/windows/openssl_exe_path.patch
-- Applying patch patches/windows/Solution.patch
-- Applying patch patches/windows/MSBuildProject_fix_gendef_perl.patch
-- Applying patch patches/windows/msgfmt.patch
-- Applying patch patches/windows/python_lib.patch
-- Applying patch patches/windows/fix-compile-flag-Zi.patch
-- Applying patch patches/windows/minimize_install.patch
-- Using source at /Users/Apple/vcpkg/buildtrees/libpq/src/tgresql-12-07bd5aa2da.clean
-- Getting CMake variables for x64-osx-dynamic-dbg
-- Getting CMake variables for x64-osx-dynamic-rel
-- Configuring x64-osx-dynamic-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:127 (message):
Command failed: /bin/bash -c "V=1 ././configure  "--with-openssl" "--with-zlib" "--without-readline" "--disable-silent-rules" "--verbose" "--enable-shared" "--disable-static" "--enable-debug" "--prefix=/Users/Apple/vcpkg/installed/x64-osx-dynamic/debug" "--bindir=\${prefix}/../tools/libpq/debug/bin" "--sbindir=\${prefix}/../tools/libpq/debug/sbin" "--libdir=\${prefix}/lib" "--includedir=\${prefix}/../include" "--datarootdir=\${prefix}/share/libpq""
Working Directory: /Users/Apple/vcpkg/buildtrees/libpq/x64-osx-dynamic-dbg
Error code: 1
See logs for more information:
/Users/Apple/vcpkg/buildtrees/libpq/config-x64-osx-dynamic-dbg-out.log
/Users/Apple/vcpkg/buildtrees/libpq/config-x64-osx-dynamic-dbg-err.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_make.cmake:796 (vcpkg_execute_required_process)
ports/libpq/portfile.cmake:287 (vcpkg_configure_make)
scripts/ports.cmake:142 (include)
Error: Building package libpq:x64-osx-dynamic failed with: BUILD_FAILED
Additional context
Error in the
/Users/Apple/vcpkg/buildtrees/libpq/x64-osx-dynamic-dbg/config.log file
line 8660: dyld[72665]: Library not loaded: @rpath/libssl.1.1.dylib
config.log
config-x64-osx-dynamic-dbg-err.log
config-x64-osx-dynamic-dbg-out.log

The following packages are already installed: openssl[core]:x64-osx-dynamic -> 1.1.1l#4

This issue hasn’t been updated in 3 month, if it is still an issue, please reopen this issue.

I can confirm that this is still an issue with the latest main, please reopen.
It has been tested here: https://github.com/daschuer/vcpkg/actions/runs/2471345461
creating the same error messages.

Reason: tried: '/usr/local/lib/libssl.1.1.dylib' (no such file), '/usr/lib/libssl.1.1.dylib' (no such file)
It the lookup path for libssl is wrong?

from openssl logs:
-- Installing: /Users/runner/mixxx-vcpkg/packages/openssl_x64-osx-dynamic-min10.12/debug/lib/libssl.3.dylib
-- Installing: /Users/runner/mixxx-vcpkg/packages/openssl_x64-osx-dynamic-min10.12/debug/lib/libssl.dylib
-- Installing: /Users/runner/mixxx-vcpkg/packages/openssl_x64-osx-dynamic-min10.12/debug/lib/libcrypto.3.dylib
-- Installing: /Users/runner/mixxx-vcpkg/packages/openssl_x64-osx-dynamic-min10.12/debug/lib/libcrypto.dylib

This one seems to be related https://github.com/microsoft/vcpkg/issues/24089

I looked at your repo. You are still using an old version of the vcpkg catalogue. Consequently, you're not getting the fix introduced in #24090.

The branch does contain the patch form #24090, see: https://github.com/daschuer/vcpkg/blob/f5c1628f057d433defe6d2ec5b4a5f18cd6c929b/ports/openssl/unix/CMakeLists.txt#L266
But I will merge from microsoft/main and start the build again, just in case.

There is nothing I can do about this because I'm not familiar with makefiles and I can't figure out where 1.1.dylib comes from. What I suspect is that makefile will find your system's openssl first, which then causes autoconf to search for openssl 1.1.
I suggest to open an issue upstream to request support for openssl 3.
Furthermore, you could pin your baseline to openssl 1.1.1. Please note that 1.1.1x won't be updated. Consequently you have to do the updates by yourself.

Here is a build with the recent master merged: https://github.com/daschuer/vcpkg/runs/6833707010
After applying the patch that keeps the config.log, I see that the issue has shifted:
dyld: Library not loaded: @rpath/liblz4d.dylib
  Referenced from: /Users/runner/mixxx-vcpkg/buildtrees/libpq/x64-osx-dynamic-min10.12-dbg/./conftest
  Reason: image not found

config.log-x64-osx-dynamic-min10.12-dbg.log

The liblzz4d.dylib is installed:
-- Installing: /Users/runner/mixxx-vcpkg/packages/lz4_x64-osx-dynamic-min10.12/debug/lib/liblz4d.dylib

does anyone have an idea how to fix that?

You are in the land of unsupported triplets... and vcpkg doesn't "support" dynamic linkage because it lacks expert to help resolve the dynamic lib lookup for running artifacts.

vcpkg does properly build all dependencies.
libpq's configure tries to run a test program during the build.
This test program fails to find dependencies (@rpath/<dylib>).

You can try to set environment variable DYLD_LIBRARY_PATH to <vpckg_installed>/[debug/]lib.
Another option might be to patch out this test. (How would it work in cross builds?)

I've hit this same issue - I think it's relevant that it fails when configuring the debug build-type. The release build-type seems to work. Something (perhaps DYLD_LIBRARY_PATH or the rpath?) seems to be be configured so as to find the release libraries but not the debug libraries.
I've tried to just disable the debug build-type since I don't care about it at all using set(VCPKG_BUILD_TYPE release) but oddly it doesn't work - it still fails while trying to configure the debug build-type. Looking into it more...

FYI I moved set(VCPKG_BUILD_TYPE release) out of my root CMakeLists.txt and into vcpkg-overlay-triplets/x64-osx.cmake and now it is taking effect. I'm still too ignorant about my build system to know why but this may help somebody

I can reproduce the issue. I'm afraid this is a more general issue for *-osx-dynamic while maintaining relocatability: Executables compiled during configuration/build cannot resolve vcpkg dylibs immediately.

vcpkg installs dylibs with "unresolved" install name:vcpkg % otool -D installed/x64-osx-dynamic/debug/lib/liblz4d.dylib
installed/x64-osx-dynamic/debug/lib/liblz4d.dylib:
@rpath/liblz4d.dylib

This is fairly okay, but...
When using the dylib in an executable, before applocal deployment as in vcpkg's tools/${PORT}, the default RPATH provided by the executable isn't sufficient to locate the dylibs when running that executable. This is what we see here with conftest:configure:16791: gcc -o conftest -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Werror=vla -Werror=unguarded-availability-new -Wendif-labels -Wmissing-format-attribute -Wcast-function-type -Wformat-security -fno-strict-aliasing -fwrapv -Wno-unused-command-line-argument -Wno-compound-token-split-by-macro -g -fPIC -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk -g -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk  -I/Users/dg0yt/dev/vcpkg/installed/x64-osx-dynamic/debug/lib/pkgconfig/../../../include  -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk -L/Users/dg0yt/dev/vcpkg/installed/x64-osx-dynamic/debug/lib -L/Users/dg0yt/dev/vcpkg/installed/x64-osx-dynamic/debug/lib/pkgconfig/../../lib  conftest.c -L/Users/dg0yt/dev/vcpkg/installed/x64-osx-dynamic/debug/lib/pkgconfig/../../lib -llz4d -L/Users/dg0yt/dev/vcpkg/installed/x64-osx-dynamic/debug/lib/pkgconfig/../../lib -lssl -L/Users/dg0yt/dev/vcpkg/installed/x64-osx-dynamic/debug/lib/pkgconfig/../../lib -lcrypto -L/Users/dg0yt/dev/vcpkg/installed/x64-osx-dynamic/debug/lib/pkgconfig/../../lib -lz -lm  >&5
configure:16791: $? = 0
configure:16791: ./conftest
dyld[73277]: Library not loaded<EMAIL_ADDRESS>  Referenced from: '/Users/dg0yt/dev/vcpkg/buildtrees/libpq/x64-osx-dynamic-dbg/conftest'
  Reason: tried: '/usr/local/lib/liblz4d.dylib' (no such file), '/usr/lib/liblz4d.dylib' (no such file)
././configure: line 2121: 73277 Abort trap: 6           ./conftest$ac_exeext

This might be resolved in various ways, but not for free:

We might set DYLD_LIBRARY_PATH, but this is intrusive and can quickly break system programs.
We might try to set DYLD_LIBRARY_PATH_FALLBACK, but AFAIU macOS has security mechanisms that clean this variable before running system programs, including the shell. It is not enough to set it before starting configure.
We may pass -Wl,-rpath..., but this will lead to absolute paths also in the desired installed libraries and programs. It probably needs install_name_tool -delete_rpath ... to clean this up after installation.
Anything else?
(These types of configuration tests suck. For cross builds, they cannot work at all.)

Well, we can just pass DYLD_FALLBACK_LIBRARY_PATH as a parameter to configure.


fix(blockifier): initial sierra gas max_execute in l1handler tx

This change is

Python side: https://reviewable.io/reviews/starkware-industries/starkware/36507

python side: https://reviewable.io/reviews/starkware-industries/starkware/36507


FFMPEG files missing after starting container

When I start the container, my /usr/local/bin directory is empty. When I pull the logs, I get the following info:
[cont-init.d] 90-sma-config: executing...
xz: (stdin): File format not recognized
tar: Child returned status 1
tar: Error is not recoverable: exiting now
chown: cannot access '/usr/local/bin/ffmpeg': No such file or directory
chown: cannot access '/usr/local/bin/ffprobe': No such file or directory
chmod: cannot access '/usr/local/bin/ffmpeg': No such file or directory
chmod: cannot access '/usr/local/bin/ffprobe': No such file or directory
[cont-init.d] 90-sma-config: exited 0.
Reruns will sometimes fix the issue.

When I switched over building from Dockerhub to Github actions I kept running into issues where the FFMPEG binary download would time out. It would seem https://www.johnvansickle.com/ffmpeg/ which is where the binaries are from has some sort of request limit and it was getting blocked. As a result I moved the ffmpeg download from the build side of the container to startup. Its certainly possible that you may also be having your request blocked intermittently seeing the same issue.
I did contact the developer and provided him the list of IP addresses that makeup github actions since docker hub was apparently given special privileges but I haven't heard back. Fortunately however by timing the build during off-peak hours I am able to get it to work most of the time so I've been able to restore the ffmpeg binaries during the build phase and thus included in the image


Create new page

As a user I want to create a new page inside a project

Pages can be created from two entry points:

Active Page View (via Shortcut and Menu)
Page Overview (same as above and additionally via '+' Button)

Shortcut: Cmd+N / Ctrl+N
Main Menu: File --> 'New Page'
When creating a new page from the page view, the currently active page needs to be saved first, or all changes will be lost.
When creating a new page from the page view, the user will be directed to the new page.
When creating a new page from the page overview, the page will be  added to the already existing pages.
The newly created page will be named "unnamed page" by default.
Flow:


Readme: Correct Manifest Link

The Manifest link was wrong, this fixes the link.

Thank you! :smile:


AWS SDK for Go

Implement recipe for the AWS SDK for Go.
https://github.com/aws/aws-sdk-go

Deprecated SDK will not be implemented as recipe.


Update java9-beta to 1.9,157

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for your contribution.


the label without  alignment

the example

I have a question. When subreads " TGACA" and label "TGACA" are aligned, the first character has a space, result in no alignment. Will this affect the training accuracy?

@one-matrix No this will not affect training accuracy.
After the sequence is predicted, we strip all gaps from both the prediction and the label before passing it to an alignment-based loss function to calculate loss.

I'm not sure I fully understand what the issue is. We encode strand as 0=unknown, 1=forward, 2=reverse
class Strand(int, enum.Enum):
  UNKNOWN = 0
  FORWARD = 1  # read.is_reverse == False
  REVERSE = 2  # read.is_reverse == True

These values are then embedded.

I see - thanks for pointing this out. I'll see if we can get the figure updated.


Explorer CLI for Cell type prediction

Add cell type prediction subcommand to Explorer CLI

Issue moved to chanzuckerberg/cellxgene #2516 via ZenHub


[ios]: HLS (m3u8) vs mp4 - very high energy impact + thermal throttling (display brightness dimming)

Hi,
I did some energy impact testing and also noticed that when I am using HLS vs mp4, mp4 consumes way less CPU (which is kinda expected since it does have less Network and parsing overhead), but my iPhone 13 Pro Max heats up pretty heavy, thermal state jumps from nominal to serious and the energy impact is super high.
Test device

iPhone 13 Pro Max
iOS 16

mp4

HLS

Is there a way to make IVS more battery friendly? My streams just have 2 qualities (480p and 720p).
The screenshot with better energy consumption was achieved with mp4 instead of HLS.
I really couldn't find much information around that.

It looks like the CPU usage is different when I use a live stream (energy Consumption is very high but I never reach the point where my screen brightness dims and I don't feel like the device is heating up).
It's more like it has issues with very simple and default m3u8 files, even though when you only deliver one quality. The live video example URL on the README does not heat up the phone. There is some heavy CPU usage going on - I think related to how the m3u8 is built.

After comparing this to native AVAsset/AVFoundation and react-native-video vs expo-av, I can tell you that this is only happening with this library. There is an internal issue with the IVS SDK on iOS which causes HLS to go nuts on the CPU. Turning logLevel to 1 did not gave me any useful insights and since the source for IVS is not open, I could not dig into this any further. I'd really appreciate if this could be investigated.

We have seen “Very High” energy usage during normal playback of IVS streams possibly due to the network activity needed for low latency playback.
Are you able to reproduce the high CPU usage issue using any of the example IVS test streams?

@maxstoller I see better results with the IVS test streams (as also pointed out in my posts already) but I see very bad results with anything thats not IVS. I really don't want to have an App with multiple players included for video coming from IVS and non-ivs. The issue is iOS only and Android works fine with HLS and Mp4. iOS on the other hand works fine only for direct mp4 urls, while it has okish results for IVS streams and terribe results for anything else.
Is it possible to disable the low latency playback to circumvent this? The available flags (I tested really all of them) do not change anything. And what I also figured for non ivs-hls streams in 95% of the times that the audio has a small stutter between 3 and 5 seconds, mostly 5 seconds exactly.

Any update on that? Temperature of my iphone is rising from 23 to 30 degrees while reading HLS streams.


STUD-4492: Read Only Mount Support

Purpose
Add backend support to use read-only mounts on docker and containerd
This will be used when mounting the shared library mounts
Semantic Versioning (check one)

[x] The following were changed in a non-backward compatible way and requires a major version bump:

[link to the breaking change in the diff]

[ ] Something public was added or changed in backward compatible way, this requires a minor version bump
[ ] No public changes nor new features (backwards-compatible refactor or bug fix), so this can be included in a patch
release

How to QA

[ ] run the following related examples: (fill in)
[ ] Other necessary steps needed to fully exercise the solution should be added here. (fill in)

Security Insights
No security relevant content was detected by automated scans.
Action Items

Review PR for security impact; comment "security review required" if needed or unsure
Verify aviary.yaml coverage of security relevant code

Questions or Comments? Reach out on Slack: #support-infosec.

QA +1

@Workiva/release-management-p


cmd/compile: expected "not used" error

What version of Go are you using (go version)?

$ go version
go version go1.13.1 linux/amd64

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/me/.cache/go-build"
GOENV="/home/me/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/me/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build399130454=/tmp/go-build -gno-record-gcc-switches"
GOROOT/bin/go version: go version go1.13.1 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.13.1
uname -sr: Linux 5.0.0-31-generic
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.3 LTS
Release:	18.04
Codename:	bionic
/lib/x86_64-linux-gnu/libc.so.6: GNU C Library (Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27.
gdb --version: GNU gdb (Ubuntu 8.1-0ubuntu3.1) <IP_ADDRESS>80409-git

What did you do?

https://play.golang.org/p/O_76qweGQ0g
package main

func main() {
	var x int
	x = 7 - x
}

What did you expect to see?
Although x is used in assignment over itself, there is no usage of x, it is nice to get "not used" error for preventing unnecessary computations.
What did you see instead?
Nothing, run successfully

At this date I would worry that making this change would cause many correct Go programs to stop compiling.
See #20802 for a related issue.

What version of Go are you using (go version)?
$ go version
go version go1.13.1 linux/amd64
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
What did you do?
https://play.golang.org/p/O_76qweGQ0g
package main

func main() {
	var x int
	x = 7 - x
}

What did you expect to see?
Although x is used in assignment over itself, there is no usage of x, it is nice to get "not used" error for preventing unnecessary computations.
What did you see instead?
Nothing, run successfully

H


test framework: comprehend subsystem_vendor/device IDs

Adds subsystem_vendor/device to the platform identification
logic in the test framework.
Signed-off-by: Tim Whisonant<EMAIL_ADDRESS>

Coverage remained the same at 65.386% when pulling 6e6cfe3b259d67ff6c8012006cb8e72bb93b9643 on tswhison/test_infra into 0a3920c588d0aeccdf6a5de0183b3498d945b510 on master.


Add downloads page with presentations

This adds a downloads page with several of the connectathon powerpoints.

I passed the test!


Does the.Net Core version no longer support self hosting mode?

Does the.Net Core version no longer support self hosting mode?
Do you only provide API, no longer provide Web interface similar to.NetFramework mode?

Yes, it still supports it and will have a ui, we are however will be moving to a docker only release in the future.

@niemyjski I really hope to arrive as soon as possible.

We got configuration done and are testing it in dev environments running inside of k8, should be soon enough


SubsamplingScaleImageView: Failed to initialise bitmap decoder     java.io.IOException: Image failed to decode using JPEG decoder

I encounter an issue with android 6 (samsung note 4). When using BIV in recyclerview, some url does not show, and the exception will throw.
Ex: http://imageinstant.com/data/images/17023/544550/009-fix.jpg
Try in demo and the same error. I dont know why this happen, please help

Maybe you could try to debug in the demo app :)

Maybe you could try to debug in the demo app :)

If not use in recyclerview, the BIV shows image normally, this issue only happens in recyclerview

I'm not facing this issue and I'm using both recyclerview and viewpager for my project


Improved readability of 'description'

added a br element in front of 'notes' to start it on a new line

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

successfully tested locally

successfully tested locally


[PRR-01C] Inefficient Bit Shift Operation

PRR-01C: Inefficient Bit Shift Operation

Type
Severity
Location

Gas Optimization

PearlRouter.sol:L261

Description:
The referenced assembly operation will perform a div operation with a multiple of 2 acting as a bit shift.
Example:
function _firstAddressInPath(bytes memory path) internal view returns (address firstAddress) {
    require(path.length >= 20, "OB");
    assembly {
        firstAddress := div(mload(add(path, 0x20)), 0x1000000000000000000000000)
    }
}

Recommendation:
We advise a bit shift to be utilized in stead, optimizing the statements gas cost.

Thanks for pointing that out, those 2 wasted gas units kept haunting me (I'm serious).


{"port":80} directive does not pick up the right port when more then one port is published and containers are added and/or removed

docker run -p 80:80 --name interlock --restart=always --hostname interlock -e INTERLOCK_DATA='{"port":80}' -e HAPROXY_PROXY_BACKEND_OVERRIDE_ADDRESS=<IP_ADDRESS> -e HAPROXY_CLIENT_TIMEOUT=2000000 -e HAPROXY_SERVER_TIMEOUT=2000000 ehazlett/interlock -s tcp://<IP_ADDRESS>:2375 --plugin haproxy start
does not always pick up port 80 of a container
log snippet:
works and publishes correct: ( chance ~ 1 in 10 )
"2016-02-29T11:34:37.669957771Z time="2016-02-29T11:34:37Z" level="info" msg="[haproxy] []: upstream=:30001 container="
but when a container is added or removed the following pops up:
2016-02-29T12:15:05.495103290Z time="2016-02-29T12:15:05Z" level="info" msg="[haproxy] : upstream=:30003 container="
port 30001 is port 80, 30003 is MySQL and 30002 is ssh
We see similar behaviour when ports are dynamically allocated and with fewer ports publised ( eg: 80 & ssh ) with only one port this does work.

This looks like it is working as expected:
The following gets port "80" exposed as it's the only port.
docker run --rm -ti -p 80:80 --hostname foo.local alpine ash
interlock:ehazlett interlock> ./cmd/interlock/interlock -D run -c ~/Sync/interlock.conf.haproxy
INFO[0000] interlock 1.0.0 (0f87cb0)
DEBU[0000] docker client: url=unix:///var/run/docker.sock
DEBU[0000] loading extension: name=haproxy configpath=/tmp/haproxy.cfg
DEBU[0000] starting event handling
DEBU[0000] checking to reload
DEBU[0000] reloading
DEBU[0000] updating load balancers
DEBU[0000] generating proxy config                       ext=haproxy
INFO[0000] configuration updated                         ext=haproxy
DEBU[0000] dropping SYN packets to trigger client re-send  ext=haproxy
DEBU[0000] &{/sbin/iptables [/sbin/iptables -I INPUT -p tcp --dport 80 --syn -j DROP] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>}  ext=haproxy
WARN[0000] error signaling clients to resend; you will notice dropped packets: exit status 3  ext=haproxy
DEBU[0000] resuming SYN packets                          ext=haproxy
DEBU[0000] &{/sbin/iptables [/sbin/iptables -I INPUT -p tcp --dport 80 --syn -j DROP] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>}  ext=haproxy
WARN[0000] error signaling clients to resume; you will notice dropped packets: exit status 3  ext=haproxy
DEBU[0000] reload duration: 14.13ms
DEBU[0010] event received: type=create id=701d1aedb4fc3777bc4e95815918ce0ec2b86ad867fe3f34ab5e033bcb946943
DEBU[0010] event received: type=attach id=701d1aedb4fc3777bc4e95815918ce0ec2b86ad867fe3f34ab5e033bcb946943
DEBU[0010] event received: type= id=
DEBU[0010] event received: type=start id=701d1aedb4fc3777bc4e95815918ce0ec2b86ad867fe3f34ab5e033bcb946943
DEBU[0010] inspecting container: id=701d1aedb4fc3777bc4e95815918ce0ec2b86ad867fe3f34ab5e033bcb946943
DEBU[0010] checking container labels: id=701d1aedb4fc3777bc4e95815918ce0ec2b86ad867fe3f34ab5e033bcb946943
DEBU[0010] checking container ports: id=701d1aedb4fc3777bc4e95815918ce0ec2b86ad867fe3f34ab5e033bcb946943
DEBU[0010] container is monitored; triggering reload: id=701d1aedb4fc3777bc4e95815918ce0ec2b86ad867fe3f34ab5e033bcb946943
DEBU[0010] triggering reload
DEBU[0010] event received: type=resize id=701d1aedb4fc3777bc4e95815918ce0ec2b86ad867fe3f34ab5e033bcb946943
DEBU[0011] reaping key: reload
DEBU[0011] triggering reload from cache
DEBU[0011] checking to reload
DEBU[0011] reloading
DEBU[0011] updating load balancers
DEBU[0011] generating proxy config                       ext=haproxy
INFO[0011] foo.local: upstream=<IP_ADDRESS>:80 container=determined_wozniak  ext=haproxy
DEBU[0011] alias domains: []                             ext=haproxy
DEBU[0011] adding host name=foo_local domain=foo.local   ext=haproxy
INFO[0011] configuration updated                         ext=haproxy

If more than one port is published I can specify which port to use:
docker run --rm -ti -p 80:80 -p 3000:3000 --label interlock.port=80 --hostname foo.local  alpine ash
You can see the upstream is <IP_ADDRESS>:80
INFO[0000] interlock 1.0.0 (0f87cb0)
DEBU[0000] docker client: url=unix:///var/run/docker.sock
DEBU[0000] loading extension: name=haproxy configpath=/tmp/haproxy.cfg
DEBU[0000] starting event handling
DEBU[0000] checking to reload
DEBU[0000] reloading
DEBU[0000] updating load balancers
DEBU[0000] generating proxy config                       ext=haproxy
INFO[0000] configuration updated                         ext=haproxy
DEBU[0000] dropping SYN packets to trigger client re-send  ext=haproxy
DEBU[0000] &{/sbin/iptables [/sbin/iptables -I INPUT -p tcp --dport 80 --syn -j DROP] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>}  ext=haproxy
WARN[0000] error signaling clients to resend; you will notice dropped packets: exit status 3  ext=haproxy
DEBU[0000] resuming SYN packets                          ext=haproxy
DEBU[0000] &{/sbin/iptables [/sbin/iptables -I INPUT -p tcp --dport 80 --syn -j DROP] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>}  ext=haproxy
WARN[0000] error signaling clients to resume; you will notice dropped packets: exit status 3  ext=haproxy
DEBU[0000] reload duration: 12.87ms
DEBU[0007] event received: type=create id=07223ce67654856216f540cfcf5d1b08af79c9766f61671578d554d7e796cd5c
DEBU[0007] event received: type=attach id=07223ce67654856216f540cfcf5d1b08af79c9766f61671578d554d7e796cd5c
DEBU[0007] event received: type= id=
DEBU[0007] event received: type=start id=07223ce67654856216f540cfcf5d1b08af79c9766f61671578d554d7e796cd5c
DEBU[0007] inspecting container: id=07223ce67654856216f540cfcf5d1b08af79c9766f61671578d554d7e796cd5c
DEBU[0007] checking container labels: id=07223ce67654856216f540cfcf5d1b08af79c9766f61671578d554d7e796cd5c
DEBU[0007] checking container ports: id=07223ce67654856216f540cfcf5d1b08af79c9766f61671578d554d7e796cd5c
DEBU[0007] container is monitored; triggering reload: id=07223ce67654856216f540cfcf5d1b08af79c9766f61671578d554d7e796cd5c
DEBU[0007] triggering reload
DEBU[0007] event received: type=resize id=07223ce67654856216f540cfcf5d1b08af79c9766f61671578d554d7e796cd5c
DEBU[0008] reaping key: reload
DEBU[0008] triggering reload from cache
DEBU[0008] checking to reload
DEBU[0008] reloading
DEBU[0008] updating load balancers
DEBU[0008] generating proxy config                       ext=haproxy
DEBU[0008] foo.local: found specified port 80 exposed as 80  ext=haproxy
INFO[0008] foo.local: upstream=<IP_ADDRESS>:80 container=admiring_ptolemy  ext=haproxy
DEBU[0008] alias domains: []                             ext=haproxy
DEBU[0008] adding host name=foo_local domain=foo.local   ext=haproxy
INFO[0008] configuration updated                         ext=haproxy
DEBU[0008] dropping SYN packets to trigger client re-send  ext=haproxy
DEBU[0008] &{/sbin/iptables [/sbin/iptables -I INPUT -p tcp --dport 80 --syn -j DROP] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>}  ext=haproxy
WARN[0008] error signaling clients to resend; you will notice dropped packets: exit status 3  ext=haproxy
DEBU[0008] resuming SYN packets                          ext=haproxy
DEBU[0008] &{/sbin/iptables [/sbin/iptables -I INPUT -p tcp --dport 80 --syn -j DROP] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>}  ext=haproxy
WARN[0008] error signaling clients to resume; you will notice dropped packets: exit status 3  ext=haproxy
DEBU[0008] reload duration: 13.90ms

I can change the port specification for interlock and it adheres:
docker run --rm -ti -p 80:80 -p 3000:3000 --label interlock.port=3000 --hostname foo.local  alpine ash
Here I'm specifying port 3000 instead of 80.
INFO[0000] interlock 1.0.0 (0f87cb0)
DEBU[0000] docker client: url=unix:///var/run/docker.sock
DEBU[0000] loading extension: name=haproxy configpath=/tmp/haproxy.cfg
DEBU[0000] starting event handling
DEBU[0000] checking to reload
DEBU[0000] reloading
DEBU[0000] updating load balancers
DEBU[0000] generating proxy config                       ext=haproxy
INFO[0000] configuration updated                         ext=haproxy
DEBU[0000] dropping SYN packets to trigger client re-send  ext=haproxy
DEBU[0000] &{/sbin/iptables [/sbin/iptables -I INPUT -p tcp --dport 80 --syn -j DROP] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>}  ext=haproxy
WARN[0000] error signaling clients to resend; you will notice dropped packets: exit status 3  ext=haproxy
DEBU[0000] resuming SYN packets                          ext=haproxy
DEBU[0000] &{/sbin/iptables [/sbin/iptables -I INPUT -p tcp --dport 80 --syn -j DROP] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>}  ext=haproxy
WARN[0000] error signaling clients to resume; you will notice dropped packets: exit status 3  ext=haproxy
DEBU[0000] reload duration: 14.54ms
DEBU[0004] event received: type=create id=e6cbd64c80f8e5577662ee806d6a3a321040b1230478c836dc9b58feb6b9326c
DEBU[0004] event received: type=attach id=e6cbd64c80f8e5577662ee806d6a3a321040b1230478c836dc9b58feb6b9326c
DEBU[0004] event received: type= id=
DEBU[0004] event received: type=start id=e6cbd64c80f8e5577662ee806d6a3a321040b1230478c836dc9b58feb6b9326c
DEBU[0004] inspecting container: id=e6cbd64c80f8e5577662ee806d6a3a321040b1230478c836dc9b58feb6b9326c
DEBU[0004] checking container labels: id=e6cbd64c80f8e5577662ee806d6a3a321040b1230478c836dc9b58feb6b9326c
DEBU[0004] checking container ports: id=e6cbd64c80f8e5577662ee806d6a3a321040b1230478c836dc9b58feb6b9326c
DEBU[0004] container is monitored; triggering reload: id=e6cbd64c80f8e5577662ee806d6a3a321040b1230478c836dc9b58feb6b9326c
DEBU[0004] triggering reload
DEBU[0004] event received: type=resize id=e6cbd64c80f8e5577662ee806d6a3a321040b1230478c836dc9b58feb6b9326c
DEBU[0005] reaping key: reload
DEBU[0005] triggering reload from cache
DEBU[0005] checking to reload
DEBU[0005] reloading
DEBU[0005] updating load balancers
DEBU[0005] generating proxy config                       ext=haproxy
DEBU[0005] foo.local: found specified port 3000 exposed as 3000  ext=haproxy
INFO[0005] foo.local: upstream=<IP_ADDRESS>:3000 container=sleepy_almeida  ext=haproxy
DEBU[0005] alias domains: []                             ext=haproxy
DEBU[0005] adding host name=foo_local domain=foo.local   ext=haproxy
INFO[0005] configuration updated                         ext=haproxy
DEBU[0005] dropping SYN packets to trigger client re-send  ext=haproxy
DEBU[0005] &{/sbin/iptables [/sbin/iptables -I INPUT -p tcp --dport 80 --syn -j DROP] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>}  ext=haproxy
WARN[0005] error signaling clients to resend; you will notice dropped packets: exit status 3  ext=haproxy
DEBU[0005] resuming SYN packets                          ext=haproxy
DEBU[0005] &{/sbin/iptables [/sbin/iptables -I INPUT -p tcp --dport 80 --syn -j DROP] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>}  ext=haproxy
WARN[0005] error signaling clients to resume; you will notice dropped packets: exit status 3  ext=haproxy
DEBU[0005] reload duration: 15.45ms

You can see the upstream selected is using port 3000.

Ah so the example I used is for the new version.  Let me debug the legacy version to see if I can re-create.

Thank you for the response, really grateful for this. The "--label interlock.port=3000" is a new one, looks as though it's usefull for the static mapped ports.
However, mapping is mostly done on a dynamic port eg:
docker run --rm -ti -p 80 -p 8022 --hostname foo.local alpine ash
With the 'port'=80 directive oftentimes port 8022 or port 3306 instead of port 80 is relayed through HAPROXY

Ok this is what the {"port":80} is supposed to fix.  Let me see if I can re-create on legacy.
As another thought, you might want to try the new version (1.0) although this does require the load balancing container be external (i.e. another nginx or haproxy container).
I will see if I can re-create this scenario.  Thanks!

This looks like it's working in legacy (0.3.3) as well:
time="2016-03-03T09:29:50Z" level=debug msg="[interlock] event: date=1456997390 type=resize image=alpine container=4486035da8d05138d8efea0fc65da11e1e17c305ae0c3a14511839d8990de449"
time="2016-03-03T09:29:50Z" level=info msg="[interlock] dispatching event to plugin: name=nginx version=0.1"
time="2016-03-03T09:29:50Z" level=info msg="[nginx] action=received event=4486035da8d05138d8efea0fc65da11e1e17c305ae0c3a14511839d8990de449 time=1456997390"
time="2016-03-03T09:29:50Z" level=debug msg="[nginx] foo.local: found specified port 8000 exposed as 32775"
time="2016-03-03T09:29:50Z" level=info msg="[nginx] foo.local: upstream=<IP_ADDRESS>:32775"
time="2016-03-03T09:29:50Z" level=debug msg="[nginx] writing config:  /etc/nginx/nginx.conf"
time="2016-03-03T09:29:50Z" level=debug msg="[nginx] reloading nginx process"
time="2016-03-03T09:29:50Z" level=info msg="[nginx] nginx reloaded and ready"

You can see in the logs "found specified port 8000...".  Can you give the version of Interlock you are using as well as the logs from Interlock when you run one of these containers having issues?

version obtained with the docker run command as mentioned in the first post ( pulls the default version )
Below a fail ( publishing port 30003 )

And here good one ( publishing 30001 )

Thanks. This looks like an older version of interlock. Could you pull the
latest (docker pull ehazlett/interlock:latest) and try again?
On Mar 3, 2016 9:54 AM, "twobombs"<EMAIL_ADDRESS>wrote:

[image: screenshot 2016-03-03 15 41 39]
https://cloud.githubusercontent.com/assets/12692227/13497584/7459edde-e156-11e5-8f74-f2ad835b0161.png
version obtained with the docker run command as mentioned in the first
post ( pulls the default version )
Below a fail ( publishing port 30003 )
[image: screenshot 2016-03-03 15 44 17]
https://cloud.githubusercontent.com/assets/12692227/13497913/eb8a7f4e-e157-11e5-9af6-8dd857e94e61.png
And here good one ( publishing 30001 )
[image: screenshot 2016-03-03 15 44 17]
https://cloud.githubusercontent.com/assets/12692227/13497917/f10cc65c-e157-11e5-9b3e-7fb16933c018.png
—
Reply to this email directly or view it on GitHub
https://github.com/ehazlett/interlock/issues/79#issuecomment-191799218.

We see it also failing with v0.33 :
2016-03-04T10:49:11.721971460Z time="2016-03-04T10:49:11Z" level=info msg="[haproxy]  upstream=<IP_ADDRESS>:32768 container=
2016-03-04T10:49:40.303193956Z time="2016-03-04T10:49:40Z" level=info msg="[haproxy] upstream=<IP_ADDRESS>:32769 container=
flipping between the two published ports

Hmm.  Can you give the entire log?  I cannot re-create when I specify the port in the environment variable.  If you do not set that it will select the first published port which would cause this action.

yupz, 0.33 has this fixed IMHO, all this time we ran with 0.31, the 0.33 version works(tm)
thank you very much for the information, we can now more ahead with mass-deployment ! :)

update: dynamic allocated ports works
static ports do not
log:
2016-03-08T13:18:45.649614494Z time="2016-03-08T13:18:45Z" level=warning msg="***** THIS VERSION IS DEPRECATED.  PLEASE UPDATE *****"
2016-03-08T13:18:45.649780736Z time="2016-03-08T13:18:45Z" level=warning msg="See https://github.com/ehazlett/interlock for details"
w2016-03-08T13:18:45.650604038Z time="2016-03-08T13:18:45Z" level=info msg="interlock running version=0.3.3 (31890d8)"
u2016-03-08T13:18:45.650821425Z time="2016-03-08T13:18:45Z" level=info msg="loading plugin name=haproxy version=0.1"
2016-03-08T13:18:45.650838342Z time="2016-03-08T13:18:45Z" level=info msg="[interlock] dispatching event to plugin: name=haproxy version=0.1"
2016-03-08T13:18:45.666240480Z time="2016-03-08T13:18:45Z" level=info msg="[haproxy] : upstream=<IP_ADDRESS>:30003

Hmm can you give a little more logs?  As you can see in my previous log output I have both dynamic and manually specified ports and they both are working.

It also looks like those are dynamic only as in they are allocating high ports.

The port is high yet static, however, as the dynamic port allocation now works i regard this issue as closed, also because v1.0 has been released ( and this version is no longer maintained ) Will look into a 1.0 migration in the coming months. Thank you very much for all your hard work.

Sounds good thank you!


.genm file export

Add the ability to export .genm files

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


fix: restore custom styling to table format

I mistakenly changed the order that styles are applied in #1087 for the table formatter so our custom styles were immediately overridden when the rounded style was applied

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 66.46%. Comparing base (fcc7afb) to head (1c07b6a).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1094      +/-   ##
==========================================
+ Coverage   65.94%   66.46%   +0.52%
==========================================
  Files         159      159
  Lines       12758     9895    -2863
==========================================
- Hits         8413     6577    -1836
+ Misses       3885     2855    -1030
- Partials      460      463       +3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Ethers not showing up in Rinkeby Testnet Etherscan or MetMask https://faucet.rinkeby.io/. I get the green message stating approval but the Ethers don't show up. What am I doing wrong?

I have tried tweeter a few time to get test Ethers from

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

Ganache version:
Node version:
Operating System and version:
Truffle version:
Link to your project:

Sorry place to put this issue.


question about xSort function

Hello,
I have a BarChart in this link:
http://jsfiddle.net/ranucame/f52hLnx3/3/
I want order the items, but when I use .xSort((a, b) => a.x - b.x) (which is with //) the chart is showed wrongly.
What is the mistake?
Thanks

what output are you expecting? if you are trying to show bars in ascending/descending order, you need to sort based on the Y: http://jsfiddle.net/f52hLnx3/5/
also, please label issues with more descriptive titles.

sorry for the inconveniences.
Thank you so much
On Thu, Sep 13, 2018 at 7:49 AM Dave Landry<EMAIL_ADDRESS>wrote:

what output are you expecting? if you are trying to show bars in
ascending/descending order, you need to sort based on the Y:
http://jsfiddle.net/f52hLnx3/5/
also, please label issues with more descriptive titles.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alexandersimoes/d3plus/issues/658#issuecomment-420994440,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aovu1uTHoJ47en29pO1BHd16Pmo7PQEjks5ualREgaJpZM4WmlIj
.


Version Query Continuation Token

It just makes it easier to let the user know that the continuation token is no longer valid across some versions of the SDK.

This is done in #839


Question about COLMAP Init Points

Hi,
Thank you for your outstanding work! While running the HyperNeRF dataset, I noticed that I achieved a PSNR of 27.94, surpassing the reported 26.98 in your paper. Therefore, I would like to inquire if there might be an issue with my settings. In your code, you use every fourth image as training data, whereas COLMAP's image input is every nth image, ensuring that len(cam) // n is less than 200. Could this setting potentially impact the training results?

I don't test that .... Estimating all points by input images are time-consuming and I (and my test computer) have no time to calculate all the sfm point from all the hypernerf dataset. I have to strike a balance between training speed(including preprocessing), rendering quality, and rendering speed.
But ensuring more input images will indeed perfrom a better sfm initialization.

Thanks for your reply!
By the way, I observed that initializing dynamic scene point clouds with COLMAP sometimes leads to matching points of the same object across multiple time frames, as shown below:

It's interesting because there won't be two lemons in the final rendered images. What could be the reason behind the 4D Gaussian effectively capturing the motion of redundant points?


Make the bindService method final

Thanks for your amazing work on Wire.
I noticed an inconsistency between gRPC-java and Wire's output that, if resolved, enables Wire to be integrated with tools that expect gRPC-java's output.
Since 2016, grpc-java's generated bindService method has been final. See the grpc-java issue for related discussion.
Making wire's generated code consistent with this makes it compatible with related tooling that depends on this, such as gRPC-Spring's support for Spring's method security.

@jvmakine can you have a look?


feat: linter and formatter

Closes https://github.com/weaviate/typescript-client/issues/2
Closes https://github.com/weaviate/typescript-client/issues/3
Adds eslint and prettier with TypeScript plugins. All configuration is adopted from https://github.com/stripe/stripe-node with some smaller modifications (e.g. changing errors to warnings, personal format preferences). Fixed all issues given by the linter, but there are still 57 warnings left (besides use of any).
This pull request also moves most of the source code into src/ for better separation of project artifacts (https://github.com/weaviate/typescript-client/commit/41e2bc9ab963430d8049798d914d5a4d71f9feae).
@parkerduckworth (or @dirkkul, as you added the original issues) - can you assist with the CI and precommit integration? I can add it if I get some pointers 🙂
TODO

[x] CI
[x] Pre-commit
[ ] Fix tests

The linter complains quite a bit more after the recreation, so I think something is off. Will look at it again tomorrow (midnight here).

Ok, found the issue - only warnings now, like before 😄

HI @mloenow
thanks a bunch for your contribution!
Here is a pointer for github actions with eslint and prettier. Just add a new linting workflow file :)
For precommit, have a look here for prettier. I can't find anything easy for eslint, here is a bit more complex one. I am not familiar with TS, so I don't have a feeling how complex that is. Just ignore this one if it is too annoying.
For pre-commits in general: It allows you to run linters/formatters automatically at each commit, avoiding annoying CI failures. SImply install on your system (brew install pre-commit / apt install pre-commit) go to the repo folder and do pre-commit install and it is enabled :)

I think we should merge this quickly before we get any conflicts. we can always do pre-commit/CI later

OK. I will set it ready for review and you guys can get it merged if all is good.

Formatting + linting CI integration added now, but some tests are failing it seems.

As far as the failing tests go, can you see the [test logs](https://github.com/weaviate/typescript-client/actions/runs/4386254279/jobs/7680081974?
The failures are due to some of the expected responses from the server coming back slightly different.
For example, some tests are just checking for a status code, but the server is returning the full error object (with the expected status code), etc

The pre-commit lint check now won't let you commit due to excessive warnings, but this can be ignored with --no-verify.
I will look and the remaining things in a few hours.

The pre-commit lint check now won't let you commit due to excessive warnings, but this can be ignored with --no-verify.

Then let's disable it for now :) There is no point in a checker that is failing by default
Just rename the file then we can enable it once the warnings are reduced?

Just rename the file then we can enable it once the warnings are reduced?

It's part of package.json - but can easily be re-added 🙂

The module.exports = app; export recently added in src/index.ts might not be the best way to go about it for CommonJS support, as esbuild now gives a warning:
▲ [WARNING] The CommonJS "module" variable is treated as a global variable in an ECMAScript module and may not work as expected [commonjs-variable-in-esm]

    src/index.ts:98:0:
      98 │ module.exports = app;
         ╵ ~~~~~~

  This file is considered to be an ECMAScript module because of the "export" keyword here:

    src/index.ts:100:0:
      100 │ export { AuthUserPasswordCredentials, AuthAccessTokenCredentials, Operator };
          ╵ ~~~~~~

I don't have experience with esbuild, so I don't know how this can be improved.

As far as the failing tests go, can you see the test logs?
The failures are due to some of the expected responses from the server coming back slightly different.
For example, some tests are just checking for a status code, but the server is returning the full error object (with the expected status code), etc

Tests have been fixed. The after lint fixes Promise rejection are using proper Error objects instead of just messages. I think it's consistent now.
@parkerduckworth @dirkkul could you take another look? 🍻

I agree to the CLA 👍

@mloenow nice job, tests are passing :)
WRT to the module.exports, the problem is that the index.ts uses a default export. Without module.exports, importing the client from a compiled TS project is broken, because the TS compiler does not add in the extra default qualifier in when calling weaviate.client({...}), resulting in weaviate.client is not a function.
The correct usage in this case would be weaviate.default.client({...}), or the import would need to be const weaviate = require('weaviate-ts-client').default.
Maybe there is a way to get tsc to include this in the output .js files, but if so I am not aware of it.

So, aside from just leaving module.exports in this library's index.ts, which is arguably bad style by mixing CommonJS and ESM modules in the same file, I have found a workaround: not using any default exports.
Check out this branch to see the changes.
I'm curious to know what you think about this change.
The one thing I am unsure about is that by going this route, all TS projects wanting to use the client would have to import the client like this:
import pkg from 'weaviate-ts-client';
const { weaviate } = pkg;

Which seems like prioritizing CommonJS over ESM. Not sure if that is a good or bad thing.


Fix useObjectState typing

useObjectState accepts a partial object to update a property state, but the type definition was expecting the whole object to be updated.

This is turbo annoying that this bug exist. Tried to use hook today, but left it for simple useState, just because this TS error.


PersonaCard overflows

Good catch - we're on it to add truncation to the name text.

@ericthompson I think all the fields (primaryText, secondaryText, tertiaryText, optionalText) overflow, so it may be worth adding truncation to all of them.
Thanks!

@unindented - gotcha and noted. Agreed!

PersonaCard overflow issue has been resolved in pull request https://github.com/OfficeDev/Office-UI-Fabric/pull/177

:+1:


Add kilopound per square inch (ksi) and megapound per square inch to UnitPressure

The goal of this PR is to extend the available measure units for UnitPressure by adding ksi (kilopound per square inch) and Mpsi (megapound per square inch) to the available measure units.

@swift-ci test

@swift-ci test linux

I appreciate the intent, but if it’s not in Darwin (https://developer.apple.com/documentation/foundation/unitpressure/1856093-millibars), it’s not something I will be able to merge as-is. What’s your use case?

Redo for incorrect link:
Hi! In general, I appreciate PRs that add useful API, but those cannot be merged as-is unless they’re implementing API that already exists on Darwin. In this case it doesn’t: https://developer.apple.com/documentation/foundation/unitpressure
What’s your use case?

Hi! Those measure units are used in material science / civil engineering, so I thought it would be beneficial to add them (same for UnitForce which is missing as well), but I understand that we need first to have an alignment with Darwin.
I can extract the unit tests for the existing methods for UnitPressure in another PR. What do you think?

To be clear: we don’t have alignment with Darwin first, we have alignment with Darwin in full. If Darwin doesn’t offer an API surface, we don’t want to offer it here (so that we minimize the amount of incompatible code between platforms for the API surface we use).
You can create a SwiftPM module with an extension that vends these types for the time being!

(On the other hand, if Darwin has something and it’s missing here, it’s a bug that needs fixing.)

Given that I'm not taking this, closing.


Adding IPv6 support

Added support for IPv6 and a switch in UI. Also updated server list for intelnetip() in the main script

TKs a lot

TKs a lot


Document method argument annotations

Client method documentation should show whether the arguments are input only, required, or optional. We should not show arguments for fields that are output only.

We have reconsidered the method signatures, and are currently using positional arguments for both the request object/hash and the options object/hash. This means that we are no longer generating named arguments for the request fields. But, users can still make calls using named argument syntax, and Ruby will collect the named arguments into a hash and pass that as the request argument.
We are documenting the fields/named arguments for the request that users can use, and we are excluding the fields with output-only annotations.

@blowmage So is this issue relevant anymore?

I don’t think we document whether an argument’s field is required or not. I’ll look st this tomorrow.

The current generated client method argument documentation does not specify whether the argument (proto message field) is required or optional. It does not, however, document fields that are marked as output-only.
The generated class attribute documentation (proto message) also does not indicate which attributes (proto message fields) are required vs. optional, input vs. output, etc.


feat: add title tag via React Helmet to all pages

Fixes #37.
I tried to use an SEO component approach via a custom hook but that would not work since we are using name's instead of title's for the actual page titles, so have settled on using React Helmet and gatsby-plugin-react-helmet as described here instead: https://v3.gatsbyjs.com/docs/add-page-metadata/.

@kmartens27 You may want to give this a review when you have the time. So basically this fixes the title showing up in the tab of the browser when you go to a contributor details page.


Requiring that Arch Board reviews only use automatic ApiView listings.

Consider start with an automatic API View listing by default and manually grant exceptions after discussing with the team.
If so, the Scheduling tool should support this.

Is this a process or tooling improvement?  Update Issue to reflect correct Area please

Great question. The way I see it is to modify tooling and drive process change with it. For now I will put it in Tooling

I wonder if this is a requirement for the scheduling tool? @maririos I added 'Scheduling tool' label per my understanding. If it is not only for the scheduling tool, feel free to remove it.

Thank you @josefree  I agree tha thte scheduling tool can help with this

@ronniegeraghty form your experience with the arch boards, do you know how many reviews happen from people manually uploading their APIViews vs automatic APIViews?

Thank you @ronniegeraghty . Great point.
The easiest way to see this will be to look directly in APIView in the Revisions tab. If the revision says Created for PR or Auto Review then it is automatic.
Ted has been one of the architects asking for this. Maybe a topic that could be brought up for the discussions with the arch board?

FYI @praveenkuttappan

Closing issue for now as this is not a real scenario or restriction we want to have