Serilog.Sinks.Elasticsearch not sending messages to elasticsearch 6.5.0

Does this issue relate to a new feature or an existing bug?*

[x] Bug

What version of Serilog.Sinks.Elasticsearch is affected?  Please list the related NuGet package.
Serilog.Sinks.Elasticsearch 6.5.0
**What is the target framework and operating system? See [target frameworks]

[ x] netCore 2.1

Please describe the current behavior?
It appears that Serilog's Console sink is logging all messages however the Elasticsearch sink is not.
I do see some messages logged sometimes, but not all of them, only some warnings generated by the AspNet.Core Framework

Please describe the expected behavior?
I expect all logging messages to be sent to Elasticsearch
If the current behavior is a bug, please provide the steps to reproduce the issue and if possible a minimal demo of the problem

appSettings.json
{
  "Serilog": {
    "MinimumLevel": "Debug",
    "WriteTo": [
      {
        "Name": "Console"
      },
      {
        "Name": "Elasticsearch",
        "Args": {
          "nodeUris": "http://elasticsearch:9200",
          "indexFormat": "app-logs-{0:yyyy.MM.dd}",
          "templateName": "app-logs-template",
          "period": 2000,
          "connectionGlobalHeaders": "Content-Type=application/json",
          "autoRegisterTemplate": true,
          "autoRegisterTemplateVersion": "ESv6",
          "overwriteTemplate": true
        }
      }
    ],

    "Properties": {
      "Application": "my-svc",
      "Environment": "Development"
    }
  }
}

Program.cs
    public class Program
    {
        public static void Main(string[] args)
        {
            BuildWebHost(ConfigProvider.BuildConfiguration(null, args), args)
                .Run();
        }

        public static IWebHost BuildWebHost(IConfiguration config, string[] args) =>
            WebHost.CreateDefaultBuilder(args)
                .UseConfiguration(config)
                .UseSerilog((ctx, loggerConfiguration) =>  // Using Serilog.AspNetCore 2.1.1 package
                {
                    loggerConfiguration.ConfigureSerilog(config);
                }, preserveStaticLogger: true)
                .ConfigureServices((services) =>
                {
                    Serilog.Debugging.SelfLog.Enable((msg) => System.Diagnostics.Debug.WriteLine($"SERILOG: {msg}"));
                })
                .UseStartup<Startup>()
                .Build();
    }
}

LoggerConfigurationExtensions.cs
 public static class LoggerConfigurationExtensions
    {
        private const string SerilogMinimumLevelKey = "Serilog:MinimumLevel";
        private const string SerilogSinksKey = "Serilog:WriteTo";

        private static readonly string[] RequiredConfigurationKeys = new[]
        {
            SerilogMinimumLevelKey,
            SerilogSinksKey,
            "Serilog:Properties:Application",
            "Serilog:Properties:Environment"
        };

        public static LoggerConfiguration ConfigureSerilog(this LoggerConfiguration loggerConfiguration, IConfiguration configuration)
        {
            if (configuration == null) throw new ArgumentNullException(nameof(configuration));
            var configSections = configuration.GetChildren();

            var keys = configSections.Select(x => x.Key).ToArray();
            foreach (var key in RequiredConfigurationKeys)
            {
                if(!configuration.GetSection(key).Exists()) throw new ConfigurationException($"Required configuration key [{key}] is missing");
            }

            return loggerConfiguration
                .Configure(configuration)
                .ConfigureEnrichers();
        }

        private static LoggerConfiguration Configure(this LoggerConfiguration loggerConfiguration, IConfiguration configuration)
        {
            return loggerConfiguration
                .ReadFrom.Configuration(configuration)
                .MinimumLevel.Is(MapLogLevel(configuration[SerilogMinimumLevelKey]))
                .MinimumLevel.Override("Microsoft", LogEventLevel.Warning)
                .MinimumLevel.Override("System", LogEventLevel.Warning);
        }

        private static LoggerConfiguration ConfigureEnrichers(this LoggerConfiguration loggerConfiguration)
        {
            return loggerConfiguration
                .Enrich.FromLogContext()
                .Enrich.WithProperty("Hostname", Environment.GetEnvironmentVariable("HOSTNAME"))
                .Enrich.WithProcessId()
                .Enrich.WithThreadId();
        }

        private static LogEventLevel MapLogLevel(string logLevel)
        {
            return (LogEventLevel)Enum.Parse(typeof(LogEventLevel), logLevel);
        }
    }

docker-compose.yml
version: '2.4'

services:
  elasticsearch:
    image: docker.elastic.co/elasticsearch/elasticsearch:6.5.0
  kibana:
    depends_on:
      elasticsearch:
        condition: service_healthy
    image: docker.elastic.co/kibana/kibana:6.5.0

  my-svc
    image: my-svc
    hostname: my-svc
    build:
      context: .
      dockerfile: My.Service/Dockerfile
    depends_on:
      elasticsearch:
        condition: service_healthy

Is this a missconfiguration of the Elasticsearch sink? Or is there an issue with Elasticsearch 6.5.0 ?
Please note that my-svc is capable of resolving the elasticsearch host via docker network dns which is created by docker-compose

@mmisztal1980 did you manage to resolve this? If so, how?  Thanks

I used C# fluent API for configuration. I gave up on the .json config.

Ok so sounds like it was a config issue rather than an issue with the elastic sink.
We have had message drops from the elastic sink though it may be due to too many fields being indexed and elastic silently dropping the messages...


User Streams

Does this lib have the ability to open User streams? Or is it limited to only Public streams?

You can open User streams by following code.
var Twitter = require('twitter');
var twitter = new Twitter({
    consumer_key: 'XXX',
    consumer_secret: 'XXX',
    access_token_key: 'XXX',
    access_token_secret: 'XXX'
});
twitter.stream('user', {}, function(stream) {
    stream.on('data', function(tweet) {
        console.log(tweet);
    });

    stream.on('error', function(error) {
        throw error;
    });
});

Thanks, @IceSofticon30th. Can this be put in the docs somewhere please?


Add an example of Lime text explainer from AIX360 toolkit

What this PR does / why we need it:
This PR added an example of LIME text explainer of AIX360 toolkit
Since there are 3 modes of LIME explainer (image, text and tabular ), but currently there is only a sample of image (MNIST)
We suppose that adding a text example would help others better understanding LIME explainer
Type of changes
Please delete options that are not relevant.

[ ] New feature (non-breaking change which adds functionality)

Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevent result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

[ ] Test A
like the mnist sample of aix and mentioned in README.md , this sample should execute just like mnist sample
The first step is to determine the ingress IP and ports and set INGRESS_HOST and INGRESS_PORT

MODEL_NAME=aix-explainer
SERVICE_HOSTNAME=$(kubectl get inferenceservice ${MODEL_NAME} -o jsonpath='{.status.url}' | cut -d "/" -f 3)
python query_explain.py http://${INGRESS_HOST}:${INGRESS_PORT}/v1/models/${MODEL_NAME}:explain ${SERVICE_HOSTNAME}

Then you will see the explanation result as several charts.

Logs

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

[ ] Have you added unit/e2e tests that prove your fix is effective or that this feature works?
[ ] Has code been commented, particularly in hard-to-understand areas?
[ ] Have you made corresponding changes to the documentation?

Release note:

NONE

@drewbutlerbb4 Can you help review this?

/cc @Tomcli

@C1berwiz I'm not sure do we want to host a big binary file like rfmodel.pickle in the KServe repo. Usually we either provide a simple script to train the model or ask the KServe community to upload it to the community GCS bucket.
@yuzisun do you know a good process for uploading binary as a contributor?

@C1berwiz I'm not sure do we want to host a big binary file like rfmodel.pickle in the KServe repo. Usually we either provide a simple script to train the model or ask the KServe community to upload it to the community GCS bucket.
@yuzisun do you know a good process for uploading binary as a contributor?

We can help upload the model to community GCS bucket.

@C1berwiz Can you help sign the commit?

@yuzisun I've signed the commits,thanks

@C1berwiz I'm not sure do we want to host a big binary file like rfmodel.pickle in the KServe repo. Usually we either provide a simple script to train the model or ask the KServe community to upload it to the community GCS bucket.
@yuzisun do you know a good process for uploading binary as a contributor?

We can help upload the model to community GCS bucket.

@C1berwiz The model has been uploaded to gs://kfserving-examples/models/sklearn/newsgroup/model.pickle

Thanks @C1berwiz for the awesome contribution !!
Can you help move the example to the website under aix explainer?https://github.com/kserve/website/tree/main/docs/modelserving/explainer/aix/mnist
/lgtm
/approve


alternative method for get_gaze_vector_reprojection

Hi, thank you for the great project!
I'm trying to project a 3d gaze on the egocentric image plane, however found that the provided code example can only use the built-in function get_gaze_vector_reprojection to project the pixel location on a 90-deg-rotated rgb image. Such a setting is quite constricted (two different sets of 2880x2880  or 1408x1408 calibration params are sealed in vrs/noimagestreams vrs) which is quite hard to fatch. I want to project a predicted 3d-gaze ray (composed by 2 (x,y,z) numbers) to a down-sampled 224x224 egocentric rgb frame. Since the fisheye camera doesn't have a linear conversion between pixel scales on different resolutions, I didn't find a direct solution to do this, can you share the script/pointers as an alternative to the built-in function? Thank you.

Hello @VJWQ
We are recommending to stick to the original function to avoid having local implementation that would not match calibration of the device.
We are advising you to stick to using the function as it is (with the native calibration) and then downscale the projected point to match your target resolution image: this is what we are doing in the MPS_VIEWER https://github.com/facebookresearch/projectaria_tools/blob/6039d8ba1791e1a5a1acf3e5a802082b2ac5eda3/projectaria_tools/utils/viewer_mps.py#L286
FYI: the get_gaze_vector_reprojection source code can be found here https://github.com/facebookresearch/projectaria_tools/blob/6039d8ba1791e1a5a1acf3e5a802082b2ac5eda3/projectaria_tools/core/mps/utils.py#L131

@VJWQ  any additional feedback?
Please close the issue if you have the required information, else feel free to ask more questions.

Closing due to lack of feedback, feel free to reopen if needed.


Add new-style api reference docs for 1.5

Note: This will be hard to review the source by hand because everything checked in is generated from other files.  I can commit the source for the generated files in a separate PR.
Changes here: https://deploy-preview-1818--kubernetes-io-vnext-staging.netlify.com/docs/reference/
See the "New Beta Docs" links in the Table of Contents

This change is

In general, replace the "These are" constructs in each resource category header as I've specified in the comments, and this is fine for me.

Also, the "Getting Started" section of the kubectl command reference should probably add a paragraph about how "run" and "expose" are the most basic commands to get a workload running on your cluster and exposed to the outside world to serve requests. WDYT?

Also, the "Getting Started" section of the kubectl command reference should probably add a paragraph about how "run" and "expose" are the most basic commands to get a workload running on your cluster and exposed to the outside world to serve requests. WDYT?

Yeah, each of the sections could probably use a brief summary.  I can add that.

Alright, I think that I addressed you comments.  I added some sections for the categories in the kubectl ref section.  I also added a section without the operations since Brian was asking for it.  It is the same as the api, but just missing the operations.

Okay, LGTM.

Woot.


Poetry

pip-tools was cool, but Poetry is the shit! 😄
https://python-poetry.org/

Thank you for your contribution.
We have considered using poetry instead of the current solution, but we have decided we would not like to use it.
Your patch set has a modification, which is useful for us. Could you create a new PR with this patch: https://github.com/OneIdentity/bldr/pull/6/commits/575c65f53d7e96a3528700219e8be99c322e5377 ?


Rename?

"Mac" in the project name might be meaningful for macOS users looking for a macOS like workflow on Windows, but is probably misleading for the rest, suggesting it's a macOS application.
This could be renamed to something like "AltAppSwitcher" for "alternative application switcher".  Project description would still describe the app as a "MacOS-like switcher".
Feedbacks welcome 🙂

Project description would still describe the app as a "MacOS-like switcher".

I guess it could also mention other popular OSs/desktop environments. Before finding this project, I was googling stuff like "gnome style alt tab on windows" 😅


[BUG] Blob container's metadata is always empty when listed

Describe the bug
I'm using the Azure.ResourceManager.Storage sdk and the StorageManagementClient client, and calling client.BlobContainers.ListAsync. The returned list of ListContainerItem has a property called Metadata, which is basically the same as tags. The issue is that the Metadata I see on the blob container in the azure portal isn't in the returned ListContainerItem, instead it is always an empty IDictionary.
On the contrary, when I fetch the blob container with client.BlobContainers.GetAsync, the Metadata is returned correctly.
Expected behavior
The Metadata will be present in the returned ListContainerItem.
Actual behavior (include Exception or Stack Trace)
The Metadata property is an empty IDictionary.
To Reproduce

Create a StorageManagementClient client.
Call client.BlobContainers.ListAsync.
See that the Metadata is always empty

Environment:

Azure.ResourceManager.Storage - 1.0.0-preview.2
Windows 10,  .NET Framework 5
e.g. Visual Studio 16.8.3

Thank you for your feedback. Tagging and routing to the team member best able to assist.

Just tested it, and this also happens for client.FileShares.ListAsync

@GalPillar Could you please provide HTTP request and response?

list request:
request:
GET https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.Storage/storageAccounts//blobServices/default/containers?api-version=2019-04-01
Authorization: Bearer
response is attached
response.txt
get request:
request:
GET https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.Storage/storageAccounts//blobServices/default/containers/?api-version=2019-06-01
Authorization: Bearer
response is attached
getResponse.txt

list request:
request:
GET https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.Storage/storageAccounts//blobServices/default/containers?api-version=2019-04-01
Authorization: Bearer
response is attached
response.txt
get request:
request:
GET https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.Storage/storageAccounts//blobServices/default/containers/?api-version=2019-06-01
Authorization: Bearer
response is attached
getResponse.txt

@zfchen95
This looks a server issue:
List container from SRP won't return container meta data ( But get single container from SRP will return meta data; list container from dataplane will also return meta data)
Would you please help to look?

@zfchen95
This looks a server issue:
List container from SRP won't return container meta data ( But get single container from SRP will return meta data; list container from dataplane will also return meta data)
Would you please help to look?

We currently don't include metadata in list blob containers in management plane API.  We will add it in a future release.
For list file shares, we will need to update the swagger. The feature is available at the server level.

We currently don't include metadata in list blob containers in management plane API.  We will add it in a future release.
For list file shares, we will need to update the swagger. The feature is available at the server level.

@blueww, any updates?

@seankane-msft
This is SRP server issue, not SRP .net SDK issue. So only SRP team can fix it.
You can see  @zfchen95  comments above.
@zfchen95, will SRP team fix the issue from SRP server?

@zfchen95 can you please answer the above query?

Hi! any update on this issue ? @amnguye @zfchen95

@blueww can you help to check with service team if there has any updates?

@ArthurMa1978
I have pinged service team again and included you.

@blueww @ArthurMa1978 Anything? :(

@omri-muszkal
Actually, the issue is on server side instead of Client (SDK) side.  (Both Arthur and me works on client side.)
So we will need server team to update server by return the container metadata to fix this issue?
We have contact server team, and a bug is already opened.
However, it looks the issue is still not fixed on server side.
To make server team understand the importance and priority of this issue, you might can also try to connect to Server team with your channel, such like open a help request from Azure portal.

Close as this is not client-side issue, please file ticket to ask service team to fix it.


Add multiplatform testing to feature/llvm13

This adds multiplatform compilation and testing to the compiler pipeline. Some tests are still skipped for non-Windows environments. QIR execution tests are temporarily skipped until better JIT support can be brought online for them.

@bettinaheim, I've seen intermittent failures with the QIR execution tests on Windows (they are still suppressed for other platforms), and the weird inconsistencies in the failures makes me think that the JIT hack of using LLVMSharp v12 to run QIR from LLVM 13 is not actually working. As previously discussed, we want to get rid of this hack anyway by trying out producing JIT capable binaries ourselves, and this just shows that we need that for Windows as well.

I've simplified the commit history. This should now build clean across all platforms, including QIR execution tests.


No drawing on an Android Nexus 10

I have a web app that I created that has a signature component. I'm using an Samsung Android Nexus 10 for testing purposes (client's request) and I cannot get signature_pad to draw.
I'm having no problems on Desktop or iPads but when it comes to the Android Nexus 10, it won't draw a signature.
I read that someone's solution was that if the signature was at the bottom of the page, the scrolling affect on a Samsung device mucked up the signature_pad and when he moved it into a modal (so the signature pad did not scroll), it worked for him. Sadly, for me, it did not.
Once my modal appears on screen, the signature pad is then drawn. Did not work.
I'm not finding too many people with this specific problem elsewhere though so any potential solutions I could test would be greatly appreciated.

I don't have access to Nexus 10, so it's rather hard for me to figure out what's wrong or fix it without any more info.
Can you post your code to https://jsfiddle.net/ or https://jsbin.com/?
Do you get any JS errors in devtools console?
Is your page scrollable? If it is, can you make a version that only has a canvas, which is smaller than the page, so that the page is not scrollable and check if it works then? Though I guess you already tried it with the modal...


redis-memory-for-key not work for redis cluster

Traceback (most recent call last):
File "/opt/homebrew/bin/redis-memory-for-key", line 8, in
sys.exit(main())
File "/opt/homebrew/lib/python3.10/site-packages/rdbtools/cli/redis_memory_for_key.py", line 42, in main
print_memory_for_key(redis_key, host=options.host, port=options.port,
File "/opt/homebrew/lib/python3.10/site-packages/rdbtools/cli/redis_memory_for_key.py", line 53, in print_memory_for_key
raw_dump = redis.execute_command('dump', key)
File "/Users/evtok/Library/Python/3.10/lib/python/site-packages/redis/client.py", line 901, in execute_command
return self.parse_response(conn, command_name, **options)
File "/Users/evtok/Library/Python/3.10/lib/python/site-packages/redis/client.py", line 915, in parse_response
response = connection.read_response()
File "/Users/evtok/Library/Python/3.10/lib/python/site-packages/redis/connection.py", line 756, in read_response
raise response
redis.exceptions.ResponseError: MOVED 8829 <IP_ADDRESS>:6379

这是来自QQ邮箱的假期自动回复邮件。您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。

您好，我已收到您的邮件，谢谢！！~~


Update credits

Update the pipeline credits to reflect historical and ongoing development work.

What do you think of this, @cavenel ?


More Cheese responses

After a suggestion in chat, also respond to the French word for 'cheese' (and Dutch because I couldn't help myself). Feel free to ignore this one

:+1:


⭐ 18 - Movie Suggestion Bot (Hacktoberfest Demo)

🤩 Thank you for participating in the CopilotKit Hacktoberfest event.
Follow This Link to Get Started!🎉
NOTE: CopilotKit will allow multi-assign issues
Please show your support and give a ⭐ to the CopilotKit repository.
Demo:
Movie Suggestion Bot
Description of app functionality:
Build a bot that recommends movies based on genre, mood, or a user’s previous watch history
Technology Requirements
Using CopilotKit

Required: Your project must utilize CopilotKit as a core component.
Installation: Include CopilotKit by following the installation guide at CopilotKit Quickstart.
Documentation: Familiarize yourself with CopilotKit's features through the Official Documentation.

Styling with Shadcn-UI

Required: All UI components in your project should be styled using Shadcn-UI.
Installation: Install Shadcn-UI documentation

I would like to solve this issue

@NathanTarbert can you assign to me ?

Yes, you can take this Issue and collab on a team in devfest.ai

Just follow the link at the top of the issue to get started

Yes, you can take this Issue and collab on a team in devfest.ai

He is not my team mate. Also he didn't reply ...

@kom-senapati  Hey sorry for the delay, can we proceed together on this project ?

@kom-senapati Hey sorry for the delay, can we proceed together on this project ?

Ok msg me at discord we can proceed together. komsenapati my username

@kom-senapati Hey sorry for the delay, can we proceed together on this project ?

Or you can message in this thread in copilotkit discord channel
https://discord.com/channels/1122926057641742418/1291070835783761991

If you both want to collaborate, I would join DevFest AI and put a team together

If you both want to collaborate, I would join DevFest AI and put a team together

I am in another team and its full lol

I have started working but if he messages me I can share codebase

@NathanTarbert  can u assign me this issue

@quest-bot embark

@quest-bot embark


add created and updated at to AttackDetails

If I read it correctly there is no mention of the AttackDetails in the call. Therefore no updated of the readme required.
resolves #33

If I read it correctly there is no mention of the AttackDetails in the call. Therefore no updated of the readme required.
resolves #33

This is my mistake. I should've mentioned AttackInfo and not AttackDetails. I want it to show up in the GET /api/v1/attack(/<attackID>) endpoint which returns AttackResponse, which is a typedef for AttackInfo.
Should be a quick change, to move it from AttackDetails to AttackInfo in the models package.

Updated the fields. I generally don't like to update fields levels down the hierarchy. But it keeps things simple.
We also have to recognize that the created-at field is having the semantics of a field on the AttackDetails but is found on the AttackInfo. slightly misleading but it fits well into the responses.

Thanks for all the work @enc 🎉 !


feat(targets): Configurable batch size limit for targets

This feature will allow target users the ability to set the batch size used to triggers a drain via the target's meltano confiig.
 batch_size_rows: 100000
When a batch is full and a drain is tirggerd the message logged will now state the size of the batch so the users has a visual confirmation that the batch size they configured is being utilized.
The code for this PR was pulled out of PR 1876.
Closes #2155

📚 Documentation preview 📚: https://meltano-sdk--2248.org.readthedocs.build/en/2248/

@pnadolny13 and @edgarrmondragon I broke out the code from pr 1876 that gives the user of a target the ability to set the batch size in rows which triggers a drain.  Please take a look and let me know what you think.

@edgarrmondragon Thanks 🙏 for all of the comment and documentation edits.  Load better 🥳 than what I had.  🎉


Error Configuring on WSL

Describe the bug
Using amplify configure on WSL without cmd.exe in your path will not work and throws an error which kills the process. I believe this is because the CLI is attempting to open the brower using the opn library @v5.3.0.
To Reproduce
Steps to reproduce the behavior:

Ensure windows path is not in available in WSL by editing wsl.conf in /etc/wsl.conf

[interop]
appendWindowsPath=false # append Windows path to $PATH variable; default is true

In WSL, install @aws-amplify/cli in a fresh (unconfigured) environment
The following error will appear:

Follow these steps to set up access to your AWS account:

Sign in to your AWS administrator account:
https://console.aws.amazon.com/
Press Enter to continue
2019-06-11T14:38:32.027Z - error: uncaughtException: spawn cmd.exe ENOENT date=Tue Jun 11 2019 14:38:30 GMT+0000 (GMT), pid=351, uid=1000, gid=1000, cwd=[redacted] execPath=/home/am-a/.nvm/versions/node/v10.16.0/bin/node, version=v10.16.0, argv=[/home/am-a/.nvm/versions/node/v10.16.0/bin/node, /home/am-a/.yarn/bin/amplify, configure], rss=118603776, heapTotal=95195136, heapUsed=69676128, external=3991707, loadavg=[0.5185546875, 0.57763671875, 0.5859375], uptime=929, trace=[column=19, file=internal/child_process.js, function=Process.ChildProcess._handle.onexit, line=240, method=onexit, native=false, column=16, file=internal/child_process.js, function=onErrorNT, line=415, method=null, native=false, column=19, file=internal/process/next_tick.js, function=process._tickCallback, line=63, method=_tickCallback, native=false, column=11, file=internal/modules/cjs/loader.js, function=Module.runMain, line=832, method=runMain, native=false, column=19, file=internal/bootstrap/node.js, function=startup, line=283, method=null, native=false, column=3, file=internal/bootstrap/node.js, function=bootstrapNodeJSCore, line=622, method=null, native=false], stack=[Error: spawn cmd.exe ENOENT,     at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19),     at onErrorNT (internal/child_process.js:415:16),     at process._tickCallback (internal/process/next_tick.js:63:19),     at Function.Module.runMain (internal/modules/cjs/loader.js:832:11),     at startup (internal/bootstrap/node.js:283:19),     at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)]

Expected behavior
A clear and concise description of what you expected to happen.
The browser will open and the app will wait for the "enter" key to be pressed.
Screenshots
Desktop (please complete the following information):
OS: Ubuntu 18.04.2 LTS on Windows 10 x86_64
Kernel: 4.4.0-17134-Microsoft
Uptime: 22 mins
Packages: 522 (dpkg)
Shell: zsh 5.4.2
Terminal: /dev/tty1
CPU: Intel i7-6850K (12) @ 3.601GHz
Memory: 9072MiB / 32605MiB

Additional context
I believe this is linked a previous issue that was closed but never solved: https://github.com/aws-amplify/amplify-cli/issues/189

@am-a I could not reproduce this even after setting appendWindowsPath to false. Do you have any specific browser installed?

No specific browser - "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe";
Does running cmd.exe work from your command line within WSL? Does launching the browser work?

@yuth:
npm install -g<EMAIL_ADDRESS>node -e "opn = require('opn'); opn('http://foo.bar')"

(node:13956) UnhandledPromiseRejectionWarning: Error: spawn cmd.exe ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
    at onErrorNT (internal/child_process.js:415:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    at evalScript (internal/bootstrap/node.js:592:13)
    at startup (internal/bootstrap/node.js:265:9)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
(node:13956) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:13956) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Looks like pretty much the same error

Probably could be resolved if this is fixed - I'll try to come up with a PR: https://github.com/sindresorhus/open/issues/106

This has been fixed in https://github.com/aws-amplify/amplify-cli/pull/1655

This bug still exists on WSL on CLI version 4.17.2

A workaround is to run $ export PATH=$PATH:/c/Windows/System32 prior to running amplify configure


Bfe tlsfix v1.0

resolve #260

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Fix cipher debug

Commit 3eb2aff renamed a field of ssl_cipher_st from algorithm_ssl -> min_tls but neglected to update the fprintf reference which is included by -DCIPHER_DEBUG

+1  required for 1.1.0

+1

commit a4a18b2 merged.  thank you!


Figure out webview approach.

Rough plan is to only support web-views when native sdk is installed


objc[32648]: Class _TtC3SIL10BranchInst is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f919000) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171ceb0). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtC3SIL14CondBranchInst is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f9190d8) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171cf88). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtC3SIL15SwitchValueInst is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f9191b0) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171d060). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtC3SIL14SwitchEnumInst is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f919288) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171d138). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtC3SIL18SwitchEnumAddrInst is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f919360) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171d210). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtC3SIL18SelectEnumAddrInst is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f919438) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171d2e8). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtC3SIL23DynamicMethodBranchInst is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f919508) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171d3b8). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtC3SIL26AwaitAsyncContinuationInst is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f9195e0) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171d490). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtC3SIL21CheckedCastBranchInst is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f9196b8) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171d568). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtC3SIL25CheckedCastAddrBranchInst is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f919790) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171d640). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtC3SIL5Undef is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f919868) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171d718). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtC3SIL16PlaceholderValue is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f919900) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171d7b0). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtC9Optimizer23LocalVariableAccessInfo is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f919d38) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171dbe0). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtC9Optimizer30LocalVariableReachabilityCache is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f919e40) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171dce8). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtC11swiftASTGen23PluginDiagnosticsEngine is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f924f88) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171fa40). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtC11swiftASTGen13SourceManager is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f9251c8) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171fc78). One of the two will be used. Which one is undefined.
objc[32648]: Class _TtCC11swiftASTGen13SourceManager21MacroExpansionContext is implemented in both /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x10f9252e8) and /Applications/Xcode-16.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/host/lib_InternalSwiftScan.dylib (0x16171fd68). One of the two will be used. Which one is undefined.
Building for debugging...
warning: Could not read SDKSettings.json for SDK at: /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/ubuntu-jammy.sdk
<unknown>:0: warning: libc not found for 'aarch64-unknown-linux-gnu'; C stdlib may be unavailable
<unknown>:0: warning: libc not found for 'aarch64-unknown-linux-gnu'; C stdlib may be unavailable
warning: Could not read SDKSettings.json for SDK at: /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/ubuntu-jammy.sdk
error: link command failed with exit code 1 (use -v to see invocation)
ld.lld: error: /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/ubuntu-jammy.sdk/lib/gcc/aarch64-redhat-linux/7/../../../../lib64/libc.so:5: cannot find /lib/ld-linux-aarch64.so.1 inside /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/ubuntu-jammy.sdk
>>> GROUP ( /lib64/libc.so.6 /usr/lib64/libc_nonshared.a  AS_NEEDED ( /lib/ld-linux-aarch64.so.1 ) )
>>>                                                                   ^
clang: error: linker command failed with exit code 1 (use -v to see invocation)
[7/8] Linking test

Hi @sebsto
I can reproduce this problem.

When I try to follow instruction to generate a SDK with a docker image, it generates files with the name Ubuntu

This is the default, you can override it using the --sdk-name flag e.g. --sdk-name 6.0.1-RELEASE_amazon_linux_2_aarch64

ld.lld: error: /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/ubuntu-jammy.sdk/lib/gcc/aarch64-redhat-linux/7/../../../../lib64/libc.so:5: cannot find /lib/ld-linux-aarch64.so.1 inside /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/ubuntu-jammy.sdk

My initial thought was that this was also caused by the SDK generator's default assumption that it is working with an Ubuntu-derived distribution, whereas it seems Amazon Linux is based on CentOS.   I had hoped that specifying --linux-distribution rhel would fix this - that flag causes it to handle some Ubuntu/RHEL differences.   However I get the same error so I'll need to investigate more.

Yes, that one was fixed in https://github.com/swiftlang/swift/pull/76545

ld.lld: error: /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/ubuntu-jammy.sdk/lib/gcc/aarch64-redhat-linux/7/../../../../lib64/libc.so:5: cannot find /lib/ld-linux-aarch64.so.1 inside /Users/stormacq/Library/org.swift.swiftpm/swift-sdks/6.0.1-RELEASE_ubuntu_jammy_aarch64.artifactbundle/6.0.1-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/ubuntu-jammy.sdk

The problem here is that we are copying /lib64/ld-linux-aarch64.so.1 into the SDK, but not /lib/ld-linux-aarch64.so.1 (they are both symlinks to the same place).
I'll fix this in the generator, but as a workaround we can touch up the generated SDK and get it working:
# Assuming you built and installed the SDK like so...
% swift run swift-sdk-generator make-linux-sdk --from-container-image swift:6.0-amazonlinux2 --with-docker --swift-version 6.0.1-RELEASE --linux-distribution-name rhel --sdk-name 6.0.1-RELEASE_amazon_linux_2_aarch64 --target aarch64
% swift sdk install Bundles/6.0.1-RELEASE_amazon_linux_2_aarch64.artifactbundle

# Create the missing /lib/ld-linux-aarch64.so.1 -> ../lib64/ld-linux-aarch64.so.1 symlink...
% cd ~/.swiftpm/swift-sdks/6.0.1-RELEASE_amazon_linux_2_aarch64.artifactbundle/6.0.1-RELEASE_amazon_linux_2_aarch64/aarch64-unknown-linux-gnu/rhel-ubi9.sdk/lib
% ln -s ../lib64/ld-linux-aarch64.so.1

# Build a binary with it...
% cd /tmp/amazon-linux-test
% swift package init
% swift build --swift-sdk 6.0.1-RELEASE_amazon_linux_2_aarch64
...
% file .build/aarch64-unknown-linux-gnu/debug/amazon-linux-test                                                                                /tmp/amazon-linux-test
.build/aarch64-unknown-linux-gnu/debug/amazon-linux-test: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, with debug_info, not stripped

# Then run it in a swift:6.0-amazonlinux2 container...
bash-4.2# ldd /work/.build/aarch64-unknown-linux-gnu/debug/amazon-linux-test
        linux-vdso.so.1 (0x0000ffffa81a7000)
        libswiftSwiftOnoneSupport.so => /usr/lib/swift/linux/libswiftSwiftOnoneSupport.so (0x0000ffffa80c7000)
        libswiftCore.so => /usr/lib/swift/linux/libswiftCore.so (0x0000ffffa7a3a000)
        libswift_Concurrency.so => /usr/lib/swift/linux/libswift_Concurrency.so (0x0000ffffa797e000)
        libswift_StringProcessing.so => /usr/lib/swift/linux/libswift_StringProcessing.so (0x0000ffffa7881000)
        libswift_RegexParser.so => /usr/lib/swift/linux/libswift_RegexParser.so (0x0000ffffa7752000)
        libc.so.6 => /lib64/libc.so.6 (0x0000ffffa75cc000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x0000ffffa7597000)
        libdl.so.2 => /lib64/libdl.so.2 (0x0000ffffa7576000)
        libstdc++.so.6 => /lib64/libstdc++.so.6 (0x0000ffffa73c1000)
        libm.so.6 => /lib64/libm.so.6 (0x0000ffffa7300000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000ffffa72cf000)
        /lib/ld-linux-aarch64.so.1 (0x0000ffffa8169000)
        libdispatch.so => /usr/lib/swift/linux/libdispatch.so (0x0000ffffa725b000)
        libswiftGlibc.so => /usr/lib/swift/linux/libswiftGlibc.so (0x0000ffffa721d000)
        librt.so.1 => /lib64/librt.so.1 (0x0000ffffa71fc000)
        libBlocksRuntime.so => /usr/lib/swift/linux/libBlocksRuntime.so (0x0000ffffa71db000)
bash-4.2# /work/.build/aarch64-unknown-linux-gnu/debug/amazon-linux-test
Hello, world!

This works for Hello, world!, but unfortunately I'm getting the following error trying to build a Vapor app:
error: emit-module command failed with exit code 1 (use -v to see invocation)
<unknown>:0: error: missing required module '_FoundationCShims'
<unknown>:0: error: missing required module '_FoundationCShims'

I'll dig into that next.

Thank you for the quick initial investigation.
I tested the workwround and it works, except I had to remove the --target aarch64 option when building the custom SDK.
When using that flag, it fails to install the linker
Unpacking and copying `lld` linker...
SwiftSDKGenerator/SwiftSDKGenerator+Unpack.swift:118: Fatal error: Unknown target OS to prepare lld "nil"
[1]    74692 trace trap  swift run swift-sdk-generator make-linux-sdk --from-container-image      rhel

Yes, I've removed it above.   Sorry about that.

@sebsto This should work now.
Build the SDK:
% cd $SWIFT_SDK_GENERATOR
% swift run swift-sdk-generator make-linux-sdk --from-container-image swift:6.0.3-amazonlinux2 --with-docker --swift-version 6.0.3-RELEASE --linux-distribution-name rhel --sdk-name 6.0.3-RELEASE_amazon_linux_2_aarch64
...
Time taken for this generator run: 1:50 seconds.

% swift sdk install ./Bundles/6.0.3-RELEASE_amazon_linux_2_aarch64.artifactbundle

Build a container image:
% cd $SWIFT_CONTAINER_PLUGIN/Examples/HelloWorldVapor
% swift package --swift-sdk 6.0.3-RELEASE_amazon_linux_2_aarch64 --allow-network-connections all \
  build-container-image \
  --architecture arm64 \
  --repository $AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/demo/vapor \
  --from swift:amazonlinux2-slim

There will still be warnings about the C library, SDKSettings.json and so on, but you can ignore those.
% docker run -it --rm --pull=always -p 8080:8080 $AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/demo/vapor:latest
latest: Pulling from demo/vapor
...
2024-12-16T10:10:25+0000 notice codes.vapor.application : [Vapor] Server started on http://<IP_ADDRESS>:8080
2024-12-16T10:13:24+0000 info codes.vapor.application : request-id=24D736B4-970E-43BC-8EFA-53C15C2602D8 [Vapor] GET /
...

@euanh why does this need to be generated using the rhel distribution? Is it just that the SDK generator doesn't support Amazon Linux ?

Amazon Linux is based on RHEL, so if certain logic of Swift SDK creation can be shared between distributions instead of maintaining two separate copies, why not share those?

Okay, clear :)


Added Rollups and Transforms APIs

Description
Added Rollups and Transforms APIs via a generator.
Right now the generator cannot generate the types of these functions, yet. It's a much more complicated task that's in the work. The typing system in this repo also needs an overhaul.
Issues Resolved
closes #744
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[x] Linter check was successfull - yarn run lint doesn't show any errors
[x] Commits are signed per the DCO using --signoff
[x] Changelog was updated.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Add some tests or at least a working sample?

Going to add samples for both namespaces. For now, please double check if the generated code has any issues.

Looks like a CI fail, https://github.com/opensearch-project/opensearch-js/actions/runs/9490778616/job/26154928917?pr=797.


Fix template file extensions typo

Change extension from .html to .cshtml in template filename link text where the referred file is .cshtml.

Good catch on these, @vuorinem, thanks for the contribution!
#sign-off


deleting phase-3/Open Loop Testing Phase: Tips & Lessons Learned file.

using : and & in filenames is not recommended

Why not rename instead of deleting?

i can't rename this on a win32 system, the file is shown as deleted in my Git Gui. Probably due to the :  in the filename. can you rename it for me? I thought the file was stale and giving problems on windows.
It keeps coming back as delted because windows cannot cope with a :  in a filename.
I think this is a best practice:
https://support.apple.com/en-us/HT202808
You should avoid using colons and slashes in the names of files and folders because some operating systems and drive formats use these characters as directory separators. Consider substituting an underline (_) or dash (-) where would normally like to use a slash or colon in a filename.

Is is used (linked) anywhere? Have you tried doing it through the Github GUI, or on your Pi?

i used git-gui https://git-scm.com/docs/git-gui (this is not GitHub Gui btw).
git-gui version 0.19.GITGUI
git version 1.9.5.msysgit.0
but I think other windows git clients also will have problems with : (colon) in the filename.
you can't write those files on disk with Windows (because it's resereved for the drive indicator, e.g. C:\path )


Refactor vacation.Executable

NopArchive will now no longer write directly to the destination if a
name is not given because it now set a default name (artifact). If you
were using the generic Archive type you will see no difference but those
who were using the type directly must now specify a directory as the
destination, not a file name.
NewExecutable() now conforms to the same api as the other archive
instantiation functions excepting only a reader and allowing individuals
to set the file name using a WithName() option with mirrors the
behavior of all other archive objects.
-Executable now has a default file name (artifact) if you were using
the generic Archive type you will see no difference however because the
Executable instantiation function no longer requires a name a default is
now assigned on instantiation the same way it is done for the
NopArchive.
Executable no longer places the executable in a directory name bin
nor does it create all directories in the destination path. I felt that
automatically placing the executable in a bin directory felt to
opinionated, I think that it is more than reasonable for a user to want
to download and executable and not want to have it placed in a directory
named bin and this default behavior hinders that user. I think that it
is more than reasonable to expect that the destination given is a bin
directory if that is the desired effect. As for no longer creating all
of directories in the destination path, NopArchive is precedent setting
as it expects to write files only to destinations that exist already.

Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[x] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

@mboldt I have made a couple of changes to you initial API in this PR. I would love if you were to take a look and give me any feedback/disagreements that you might have with my changes. I am more than open for conversation on this one bearing in mind that the generic Archive api for executables have not changed at all just the underlying Executable api meaning that it should behave identically if you are using something like postal.Service.Deliver().

All makes sense.
I did the bin/ dir thing since it ends up on the PATH for buildpacks, which I expect is the common case. But, I agree with your argument that it breaks precedent and is presumptuous! Perhaps renaming the postal.Service.Deliver() arg from layerPath to destinationDirectory or somesuch would make it clear that one can pass in the bin/ directory instead of the root layer path.
Thank you for checking in, and appreciate the cleanup!


Firebase/Performance logs "Dispatching 25 gauge metrics" every second until app is killed

[REQUIRED] Step 1: Describe your environment

Xcode version: 11.3
Firebase SDK version: 6.14.0
Firebase Component: Performance
Component version: 6.14.0
Installation method: CocoaPods

[REQUIRED] Step 2: Describe the problem
On occasion, Firebase/Performance will immediately start logging "Dispatching 25 gauge metrics." on app launch every second and will not stop until the app is terminated. It's happened to me twice so far in approximately 50 launches.
Steps to reproduce:
No clue how to consistently reproduce this.
At the very least, I would like to know what exactly firebase is doing when it is logging this message.

@ImanuelChen Firebase Performance has a feature to give the developer a detailed input on how a specific instance of the trace is performing [Refer(https://firebase.google.com/docs/perf-mon/custom_traces-metrics#more-detail-trace-samples)].
The above mentioned logging message arises because of the same. We do not collect such detailed performance details all the time. We collect them on a small percentage of the instance runs. This explains why you don't see these messages consistently.
We also hope that you have the logging level set to be verbose to see these messages. To avoid such log spam, consider changing the logging level to error.

Ohh okay got it. Thanks!


Ads play

🧐 Have you read the FAQ and viewed similar issues?

[X] I have read the FAQ
[X] I have checked older issues, open and closed
[X] I did a clean install of SpotX as described in the FAQ

Сountry of your account
New Zealand
What is your Spotify Plan?
Free
Do you have Spicetify installed?
No
ℹ Computer information
- Spotify: <IP_ADDRESS>3.g85d9593d
- Windows: Windows 11 Pro 22H2 22621.1555
- PowerShell: N/A

📝 Description
Ads play like they would on the free plan
📸 Screenshots
No response

what type of ads you get, you also need a full screenshot of your client

15/30-second ads after a few songs/skips. interestingly, it only plays one batch of ads and never again until I restart the client

We recently received a similar message about audio advertising, perhaps Spotify has selectively started testing on some users.
You can help us determine this by doing the following:

Log in to the remote configuration using these instruction
Then select and copy all the text, for example using Ctrl + A (select all) Ctrl + C (copy), and paste it into a new text file,
Then send the file here.

right, wait, I need time to study your remote config

As soon as we get closer to the core of the problem, we may need your help again, please stay in touch, thank you for your assistance.

Do the following:

Clean install (perform as described in the FAQ)
Run SpotX installation
Log in to the client and check that the audio ads still appear
Log in to the remote configuration using these instruction
Record a video of your remote configuration while viewing it on your screen and send it here. You can record it as either a GIF or a video; it doesn't matter, example:

I haven't done anything and can't reproduce it anymore, which is strange because it was 100% consistent yesterday. The version is still <IP_ADDRESS>3.g85d9593d and nothing changed in the remote config either. I can reopen the issue if it returns, thanks for your help.


ID field for content block

Issue found in 3aa3355b83e800980c602cfab5f1548b15f81d0f
It would be really useful if we could easily add an ID to a block of content. I am going through deep-linking the concepts and questions and it is slow going having to read through the json and find which block of text it is you wanted and so on. If in the first instance you could add IDs to an accordion section, that would already be a huge help!

Fixed in 61203403e01e3e19ee62e2f285be4e8fc9143f29.


fix(helia-coord): Updating to v1.5.3

:tada: This PR is included in version 5.2.6 :tada:
Your semantic-release bot :package::rocket:


[Darwin] Figure out a better fix for the writability of the ApplicationLauncher cluster's CurrentApp attribute

Reproduction steps
https://github.com/project-chip/connectedhomeip/pull/30174 added a backwards compat shim, but it might be better if we can either remove this (needs some checking to see whether we can) or just move it into the compat shims bits (and presumably just make the write attempts fail client-side if we do that, and deprecate the API).
Platform
darwin
Platform Version(s)
No response
Type
Manually tested with SDK
(Optional) If manually tested please explain why this is only manually tested
No response
Anything else?
No response

At a minimum this API should now be marked "deprecated" already so it is not used by clients. As it stands right now after that PR, the API shows up as if it is a totally normal write.


docs: remove justmint.xyz (site not resolving)

Sorry I missed this. Looks like NFT Armory is also not resolving now. :-( Let me see if I can find some other mint site to reference instead, otherwise this looks good and I appreciate the PR!

https://sol-tools.tonyboyle.io/nft-tools/create-nft is working fine and Tony is working on improvements and additional features regularly. Maybe this should be added instead.

Good suggestion! @statikdev when you get a chance if you want to update this to replace those two links that don't resolve with Tony's tool I'll merge the PR. Thanks!

@samuelvanderwaal | my bad, i never saw this notification.

@samuelvanderwaal | my bad, i never saw this notification.

No worries!


Wait Until Keyword Fails

There are use case test where we are expecting a test to fail if there is a failure in a loop which keep checking every x interval basically the inverse logic of Wait Until Keyword Succeeds.
So we ended up writing a similar code for it taking cue from existing Wait Until Keyword Succeeds .
If this new propose keyword Wait Until Keyword Fails could be added in the latter release version it would be really cool.
Sample Code currently we are using in our test
###############################################################################
def run_until_keyword_fails(retry, retry_interval, name, *args):

    r"""
    Execute a robot keyword repeatedly until it either fails or the timeout
    value is exceeded.
    Note: Opposite of robot keyword "Wait Until Keyword Succeeds".
    Description of argument(s):
    retry              Max timeout time in hour(s).
    retry_interval     Time interval in minute(s) for looping.
    name               Robot keyword to execute.
    args               Robot keyword arguments.
    """

    # Convert the retry time in seconds
    retry_seconds= DateTime.convert_time(retry)
    timeout = time.time() + int(retry_seconds)

    # Convert the interval time in seconds
    interval_seconds=  DateTime.convert_time(retry_interval)
    interval = int(interval_seconds)

    BuiltIn().log(timeout)
    BuiltIn().log(interval)

    while True:
        status= BuiltIn().run_keyword_and_return_status(name, *args)

        # Return if keywords returns as failure.
        if status==False:
            BuiltIn().log("Failed as expected")
            return  False
        # Return if retry timeout as success.
        elif time.time() > timeout > 0:
            BuiltIn().log("Max retry timeout")
            return  True
        time.sleep(interval)
        BuiltIn().log(time.time())

    return  True

###############################################################################

Seems like a logical extension of the keyword structure.  I'm not sure how useful it would be for the general use cases.  I've never needed anything like this but that doesn't mean that no one does (obviously at least one person does :-).
Only change I would suggest is to allow the log messages to be included as optional input arguments, so that the function could be just a little more flexible for the general use case.

This sounds somewhat special keyword for me. Could you clarify what kind of use cases you have?

Have you tested would using this Wait Until Keyword Succeeds with Run Keyword And Expect Error work instead? Something like this:
*** Keywords ***
Wait Until Keyword Fails
    [Arguments]    ${timeout}    ${retry}    ${keyword}    @{args}
    Wait Until Keyword Succeeds    ${timeout}    ${retry}
    ...    Run Keyword And Expect Error    *
    ...    ${keyword}    @{args}

@pekkaklarck

[x] 1. This sounds somewhat special keyword for me. Could you clarify what kind of use cases you have?

Yeah sort of, use cases while testing systems we got scenario.
a) where we need to wait on an error condition but doesn't necessarily fail the test if that error doesn't occur in X time. (GOOD PATH scenario)
- If err's within X time test fails
- If doesn't err's within X timed out, don't fail
b) where we know for sure that there will be an error due to error injection within X time.  (BAD PATH scenario)

[x] 2. Really appreciated.  This works well for b) case but not really for a specific case a).

Any cleaner way to do to monitor a) failure scenarios.

To support your scenario a), you could wrap my example keyword into one more Run Keyword And Expect Error and expect to get the specific error about timeout. That get's a bit complicated, so having the logic in a custom library like you already have is probably a better idea. I still don't think this is useful and generic enough to be added into BuiltIn.


Question: prohibit remove of contenteditable="false" element

I have text within a "p" element which shall not be editable nor removable. However, if all following elements are removed (with delete button), the non-editable element finally gets deleted too and I end up with an empty page. I do not wish that.
Any chance this can prohibited?

There is only a way to prevent the whole selection.
However, it can be deleted by selecting it by dragging the mouse if "non-editable" element is in the middle.


Fixes bug which makes restoring endpoint mess

Fixes bug that mistakes gw6 for gw
which causes this bug https://github.com/moby/moby/issues/25981
Signed-off-by: Frank Yang<EMAIL_ADDRESS>

Thanks!

LGTM


dataset BackgroundColor hover block incorrect

Expected Behavior

BackgroundColor is inconsistent, let me explain, it takes an array but at the same time it take a single value. in other words it should be able to handle ["rgb(54, 162, 235)"] but wants it as "rgb(54, 162, 235)" but when there is multiple then it wants an array. What its not doing updating the hover colour indicator.
Current Behavior

no errors, but the hover info block colour does not match the legend!.
Possible Solution

Forcing unnecessary coding! write extra logic.
Steps to Reproduce (for bugs)

create bar graph
have 1 legend, multiple labels
Set the legend to 1 colour but with an array of colours, yes with only 1 in the array
4.the hover info colour will not match the legend colour

Context

Why.... well if your mapping this back to a concrete type (java, c#), then its impossible as is it an "array" or a "string". makes it very hard to make class helpers.
Environment

Chart.js version: 2.6, but i think its also in latest, need to check
Browser name and version: chrome

@Seabizkit I'm not sure that this is a good idea. When the background colour is an array, it applies to  bars by index. If you want all bars to be the same colour, you can either set an array with the same colour for each bar or just set the colour as a string and it will apply to all indexes.

What I'm suggesting is; instead of having both string and string[array] have it only take a one "type" string[array] and if there is only one item in the array then this is the colour, as in "bars to be the same colour". Hope that make sense.

@Seabizkit gotcha. Not sure how feasible that is to implement in a backwards compatible way. I think we'll always support just setting a string because that feels more Javascript-y to change the type

don't know the implications of changing it but my suggestion, is that its coded to support typed languages (C#), so in java-script i don't have to do things  like below, where 'res' is a return back from ajax with a model which mimic the chartjs structure.
 res.dataSet[0].backgroundColor = res.dataSet[0].backgroundColor[0];
Im guessing the backwards compatible way, would be if the array size is 1 then use this. otherwise default implementation.
on a side note awesome! work!

This is still working the same in v3.0.0-alpha https://jsfiddle.net/w8kyt2mf/
@benmccann @kurkle any opinions on this?

As a Java user I do see it being easier to make a typed backend APIs to generate data for a Chart.js frontend. And it seems fair to say that indexable options should have as many indexes as there is data I suppose.
From the JS perspective though it seems a bit odd perhaps? And I use scriptable options way more than indexable options and that's not so easy to send from a Java backend anyway. So I'm a bit split on this.

mmm could you give more insights to how Js works in regards to how this would make sense, as i cant wrap my head around it.
how does the js code, know that when there is only 1 then its not an array and then when there is more than 1 it must be an array, surely you have to check and code for this.
and considering this i would of thought it would make more sense to be consistent.
aka it cant be an array and not an array as the same time. well at least not in typed languages.
--valid
res.dataSet[0].backgroundColor  = "blue"

--not valid
res.dataSet[0].backgroundColor  = ["blue"]

--valid
res.dataSet[0].backgroundColor  = ["blue", "Red"]

vs
--not valid
res.dataSet[0].backgroundColor  = "blue"

--valid
res.dataSet[0].backgroundColor  = ["blue"]

--valid
res.dataSet[0].backgroundColor  = ["blue", "Red"]


Need turnstiles for arrivals docks

One-way entry.
Maybe use one-sided edge shape and when the person loses pendingclockin make the turnstile hard collidable.

need turnstiles for a lot of things it should be genericized

Okay thought about it again and edgeshape probably bad. Instead I would just check the contact normal on StartCollideEvent and if it's the forbibben direction collide as normal but if not then chuck PreventCollide on them and allow them free movement until they stop colliding.


Breakpoints don't fire after setOption('responsive', …) + refresh()

When using setOption('responsive', [{ … }]) to set a new set of breakpoints, I'm calling refresh to make the slider adjust to the new settings.
Apparently the new responsive settings are registered, as I can check with getOption('responsive'), but the new breakpoints are not being applied – the settings are the ones defined outside the breakpoints.
If I call checkResponsive(false, true) after applying the new responsive settings, and before refresh(), it works.
So I guess either the setOption('responsive', …) or the refresh() should call registerBreakpoints() at some point.

Can you recreate in a fiddle?

@leggomuhgreggo voilà http://jsfiddle.net/uudkqn7q/


Feature/freebsd

Added FreeBSD support.
Added support for distributions where the desktop package conflicts (contains) the base open-vm-tools package.

The last difference between the environments eludes me. What's up with facter 1.6?

Fixed by #14


merge from template-node-app

.github/workflows/ci.yml

chore: (jobs.test.strategy)

:tada: This PR is included in version 6.1.5 :tada:
The release is available on:

npm package (@latest dist-tag)
v6.1.5
GitHub release

Your semantic-release bot :package::rocket:


Can't build for watchos simulator using Xcode 12 GM

New Issue Checklist

[X] I have read and understood the CONTRIBUTING guide
[X] I have read the Documentation or CocoaDocs
[X] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
watchos

Platform Version
6.0

CocoaLumberjack Version
3.6.2

Integration Method
carthage

Xcode Version
Xcode 12.0

Repro rate
100%

Issue Description and Steps
When I import CocoaLumberjackSwift and compile my project for tests I get the following error:
Could not find module 'CocoaLumberjackSwift' for target 'arm64-apple-watchos-simulator'; found: x86_64-apple-watchos-simulator, i386, i386-apple-watchos-simulator, x86_64, arm64_32-apple-watchos, armv7k, armv7k-apple-watchos, arm, arm64_32

I am able to build and run for my iOS 13.7 device, and I am able to build/run on the iOS 14.0 simulator, but not for my watch extension on simulator.

That is strange. 'arm64-apple-watchos-simulator' is not a valid target (unless you're on a Apple Silicon DTK). Simulators are either x86_64 or i386 - both of which are available (according to the message).
I assume that something is wrong with the ARCHS build settings. Are you setting any VALID_ARCHS (or the new EXCLUDED_ARCHS)?

I am not setting either VALID_ARCHS or EXCLUDED_ARCHS. Do you have Xcode 12 to try to reproduce?
I am able to build and run my iOS app. I can build my watchOS app for a real device and for 'Any watchOS Device'. But I can't build for watch OS simulator.

I confirmed I was able to build a small sample project and import CocoaLumberjackSwift.

Info
Value

Platform Name
watchOS

Platform Version
7.0

CocoaLumberjack Version
3.6.2

Integration Method
Carthage 0.36.0

Xcode Version
Xcode 12.0.1

How to repro

Create a Watch App project using Xcode 12.0.1.
Add Cartfile.
Execute Carthage command.
Add CocoaLumberjack.framwork and CocoaLumberjackSwift.framwork to the target.

github "CocoaLumberjack/CocoaLumberjack"

carthage update --platform watchOS --no-use-binaries

I hope this information is helpful for you.
Thanks.

@sushichop Were you able to build for the watchOS simulator? Like I said, I can build for most targets just not the watchOS simulator specifically.

@mozeryansky
I was able to build for the simulator(Apple Watch Series 6 - 44mm).
Do you still encounter this issue even if you create a new project using Xcode 12.0.1?

@sushichop Thanks for verifying. I recreated a watch only project as you described and that worked. Except my project is not watch only.

Created a "iOS App with Watch App"
Add Cartfile: github "CocoaLumberjack/CocoaLumberjack"
Carthage: carthage update --platform watchOS --no-use-binaries
Add CocoaLumberjack.framwork and CocoaLumberjackSwift.framwork to the target.

Build for "Apple Watch Series 6 - 44mm" Xcode fails with "Building for iOS Simulator, but the linked framework 'CocoaLumberjackSwift.framework' was built for watchOS + watchOS Simulator."

Carthage: carthage update --platform iOS,watchOS --no-use-binaries

Carthage fails during /usr/bin/xcrun lipo.

Create Carthage workaround script (https://github.com/Carthage/Carthage/issues/3019) (copied below)
./carthage-xc12.sh update --platform iOS,watchOS --no-use-binaries

"Cannot retrive binary file from bundle at file:///Users/michaelozeryansky/Desktop/Sample/Carthage/Build/watchOS/CocoaLumberjack.framwork/"
My main project has a much larger setup and I'm running into a lot of problems trying to make a new sample, but are you able to build and iOS app with a watch app? Thanks for helping!
Carthage workaround: carthage-xc12.sh
#!/bin/sh -e
echo "Carthage wrapper"
echo "Applying Xcode 12 workaround..."
xcconfig="/tmp/xc12-carthage.xcconfig"
CURRENT_XCODE_VERSION=$(xcodebuild -version | grep "Build version" | cut -d' ' -f3)
echo "EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1200__BUILD_$CURRENT_XCODE_VERSION = arm64 arm64e armv7 armv7s armv6 armv8" >> $xcconfig
echo 'EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1200 = $(EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1200__BUILD_$(XCODE_PRODUCT_BUILD_VERSION))' >> $xcconfig
echo 'EXCLUDED_ARCHS = $(inherited) $(EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_$(EFFECTIVE_PLATFORM_SUFFIX)__NATIVE_ARCH_64_BIT_$(NATIVE_ARCH_64_BIT)__XCODE_$(XCODE_VERSION_MAJOR))' >> $xcconfig

echo 'ONLY_ACTIVE_ARCH=NO' >> $xcconfig
echo 'VALID_ARCHS = $(inherited) x86_64' >> $xcconfig
export XCODE_XCCONFIG_FILE="$xcconfig"
echo "Workaround applied. xcconfig here: $XCODE_XCCONFIG_FILE"

carthage $@

@mozeryansky
The workaround for Carthage is only for iOS target. Then you need a more complex solution when you choose iOS App with Watch App.
In short words, my solution is as followings.
carthage-workaround.sh
#!/bin/sh

set -euo pipefail

xcconfig=$(mktemp /tmp/static.xcconfig.XXXXXX)
trap 'rm -f "$xcconfig"' INT TERM HUP EXIT

CURRENT_XCODE_VERSION=$(xcodebuild -version | grep "Build version" | cut -d' ' -f3)
echo "EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1200__BUILD_$CURRENT_XCODE_VERSION = arm64 arm64e armv7 armv7s armv6 armv8" >> $xcconfig

echo 'EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1200 = $(EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1200__BUILD_$(XCODE_PRODUCT_BUILD_VERSION))' >> $xcconfig
echo 'EXCLUDED_ARCHS = $(inherited) $(EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_$(EFFECTIVE_PLATFORM_SUFFIX)__NATIVE_ARCH_64_BIT_$(NATIVE_ARCH_64_BIT)__XCODE_$(XCODE_VERSION_MAJOR))' >> $xcconfig

export XCODE_XCCONFIG_FILE="$xcconfig"
carthage "$@"

IMPORTANT: You need to execute command for each platform as follows.
carthage update --platform watchOS --no-use-binaries
./carthage-workaround.sh update --platform iOS --no-use-binaries

And I was able to build iOS app with a watch app.
I hope this information is helpful for you🙂

This did work! Thank you.


Request: Elementor Pro Form

Hello,
it would be very nice, to have the plugin integrate into Elementor Pro Forms.
I am not experienced enough to so it myself, that why the request.
As a reference, maybe this could help: https://github.com/hCaptcha/hcaptcha-wordpress-plugin/tree/master/src/php/ElementorPro
Thanks for the lovely work!

As suggested by @pBrambi, we've investigated the Elementor Pro Form Builder and added a module to the mosparo Integration plugin to use mosparo in the Elementor Form Builder.
We've just released v1.4 of the mosparo Integration plugin, which contains the Elementor Form module.
@pBrambi Thank you for your suggestion and help to test the new module.


Add feature: Write Name text component

Hi Hasin,
Thanks for waiting, this is a bit difficult for me, because I am not yet proficient in Reactjs. I have added a Text Component to the project following the instructions in the CONTRIBUTED.md file. This Text Component is called writeName-text(Write Name), which allows users to write their name. I also added an animation effect to make it look nice.
I hope you like it, and if there are any mistakes, I would love to receive your feedback.
I hope your project will develop more and more.
Best regards.

Hi @hasin-zaman ,
Thanks for your feedback. I have made some changes as suggested.
This includes:

Changing the Component name to Animated Text
Changing the Route to texts/animated-text
Adding some comments to make the code more readable
Removing unused code and imports.

I look forward to your feedback and further instructions.
Here are some greenshots you will need:

This is perfect! Great job! @Giang0402

@Giang0402 you haven't pushed your changes. Let me assign you another issue and you can push your changes there. Also, there is one more issue you need to address. So the component you have developed is an input text field and not a text which means it should be in the category of input fields. Just go to navlinks add another category "Input Fields", in reusable-components add another folder "input-fields" and make required changes to move from texts category to input fields category. Everything else is great. Thanks

@hasin-zaman  Thanks for your feedback, I will complete this task soon.


ZSchema should be able to validate DateTime ranges

E.g., when running validate and compiling to big query, no times should be past 9999-12-31. https://cloud.google.com/bigquery/docs/reference/standard-sql/migrating-from-legacy-sql#timestamp_differences

good call!

we should probably set a reasonable minimum date on fields too

BQ also defines a minimum date, which I think is the same as the Golang one.


fixslot comparison bug

Proposed changes
slot comparison should be based on exprId, not name
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run p0

run p0


neoplot:0.0.1

I am submitting

[x] a new package
[ ] an update for a package

Description:  a package to use gnuplot in Typst.
I have read and followed the submission guidelines and, in particular, I

[x] selected a name that isn't the most obvious or canonical name for what the package does
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] tested my package locally on my system and it worked
[x] excluded PDFs or README images, if any, but not the LICENSE

Thanks !


infer "of" narrowing

Let's face it: it's totally weird that this is well-typed:
alias Bool => \Itrue|\Ifalse;
void fun(Bool bool) {}
Boolean t = true;
fun(t of Bool);

But this is not:
alias Bool => \Itrue|\Ifalse;
void fun(Bool bool) {}
Boolean t = true;
fun(t);

In such cases, instead of producing an error, we could, completely safely and reasonably, just infer the of Bool bit. I'm conflicted about that because while it works perfectly nicely here, I guess it would create the expectation in the user's head that \Itrue|\Ifalse and Boolean are the same type, which is an expectation that is violated as soon as these types are used as type arguments. (A List<Boolean> is not a List<\Itrue|\Ifalse> in Ceylon!

What exactly does the inference do? Given a parameter of type T, try adding of T to the argument? Or is it based on the argument?

@lucaswerkmeister right, that, approximately.

I really dislike this. I find it to be really intuitive that sub-typing means the same as assignability, and I think this is what most people would strongly expect.

Even if the compiler didn't infer the of Bool, it could still generate an error message which suggests it as a possible fix!

Even if the compiler didn't infer the of Bool, it could still generate an error message which suggests it as a possible fix!

Looks like this was done in 1d5db0b2fe4f92aa4e2aaf6dd748bc295247305a.

Ah, that's the one. It would be nice to dial it back a bit for refinement:
class A() {
    shared \Itrue | \Ifalse foo() => true;
}
class B() extends A() {
    shared Boolean foo() => true;
    // type of member must be assignable to type of refined member 'foo' in 'A':
    // the assigned type 'Boolean' is covered by, but not assignable to, the type
    // 'true|false' (explicitly narrow assigned expression using 'of true|false')
}


Add a way (annotations?) to mark a Tekton Resource to be skipped=

Feature request

Provide a way to mark a Tekton resources (TaskRun or PipelineRun) to be skipped by the controller.
On of the possible idea would be to add an extra value to chains.tekton.dev/signed with a skip value, or an entirely new annotations (chains.tekton.dev/skip).
Use case

One of the use case for this is, if we enable chains on a very Tekton resources heavy cluster (like 5000s existing PipelineRun, or more…). At start, the chains controller will load them all and try to sign them all (more or less at once). This will possible generate a crazy amount of load if not completely kill the controller. One idea to reduce this, would be to allow a user to mark previous / existings resources to not be signed, making chains work essentially no-op when it starts (or very low).
It could also, probably, be useful if one is experimenting with some Pipeline or Task and doesn't want chains to sign it.
cc @lcarva @concaf

@concaf the trick would be, what happens if the chains controller is shut down for an hour or two ? (during an upgrade or something). One would have to enable that field, and disable it later on. In addition, how do we "decide" what is "existing" ? The one that were created before the controller started, the one that were done at the point ?
I do think the skip annotation approach does not necessarily prevent a "controller's configuration" to be set/put in place later on.

i agree with the feature request but not sure if it's the right solution for the use case - if i install / enable chains on a cluster with a heavy load of tekton workloads, then i need to annotate all the older workloads, which is... weird and clunky??

This is relatively easy to script and it has the additional benefit of easily know that those resources were skip on purpose (versus having to look kind-of deep to understand why some resources are signed and some not ?).

An alternative is to introduce a new Chains configuration to ignore any resource created prior to a given date, e.g.
ignore-older-resources: 2023-01-01T00:00:00Z

That could potentially give a hook for an installer to better match the user's expectations.

cc @tektoncd/chains-maintainers 🙏🏼

@concaf the trick would be, what happens if the chains controller is shut down for an hour or two ? (during an upgrade or something). One would have to enable that field, and disable it later on. In addition, how do we "decide" what is "existing" ? The one that were created before the controller started, the one that were done at the point ?

we could go via a timestamp approach as well, i.e. "don't sign anything that was created before 5 pm, 31 oct 2023"

This is relatively easy to script and it has the additional benefit of easily know that those resources were skip on purpose (versus having to look kind-of deep to understand why some resources are signed and some not ?).

i agree that it's easy to script, however it feels a bit incessant to me; building on your approach, there could also be a whitelisting flag that can help which would be both, explicit and obvious.
if you set chains.tekton.dev/skip: true, then you effectively blacklist that workload from getting signed; what do you think about chains.tekton.dev/allow: true which will act as a whitelist - it would mean that only the workloads with this annotation get signed by chains; this also reduces pressure on the controller to sign everything and transfers control over to the user - say i want only specific workloads to be signed and not others, then i can whitelist those.
there can be prioritization of sorts - by default, chains watches and signs all workloads - then there should a configuration that tells chains only to sign the workloads with the whitelist annotation / label.
another reason why i prefer whitelisting is that it's more explicit than blacklisting - say that a user (who knows nothing about chains) creates a tekton workload, then chains is going to sign it implicitly - in order to deny chains, they need to add an annotation; while on the other hand if whitelisting is "enabled", then only the workloads with that explicit annotation / label will be signed.
wdyt?

On of the possible idea would be to add an extra value to chains.tekton.dev/signed with a skip value, or an entirely new annotations (chains.tekton.dev/skip).

In general I would not recommend allowing pipeline users have a skip mode - you don't want nefarious users to be able to suppress provenance generation to mask what they're doing.
Opt-in for testing things out / ramp up seems reasonable (like we do for manual mode), but you don't want users to have control over this for normal operation.

At start, the chains controller will load them all and try to sign them all (more or less at once). This will possible generate a crazy amount of load if not completely kill the controller.

Are you seeing CPU load, memory load, both? Any metrics you can share? 👀
What resource requests/limits is the controller being subjected to?
By default, Knative controllers are rate limited (default 10 qps / 100 burst). If this is taking up a crazy amount of resources then this may be a sign of a leak.
My first thought would be to try and profile the controller and see if there's any low hanging fruit here.

An alternative is to introduce a new Chains configuration to ignore any resource created prior to a given date

I'd be okay with this, though the same problem could still pop up in other scenarios. 🤷

Opt-in for testing things out / ramp up seems reasonable (like we do for manual mode), but you don't want users to have control over this for normal operation.

That could be an option I guess, but as soon as the user would switch to true, it would probably generate that load again ? Also, isn't it only on transparency log upload (and not on the signing) ?

Are you seeing CPU load, memory load, both? Any metrics you can share? 👀
What resource requests/limits is the controller being subjected to?

I don't have all the detail, but it's happening on a cluster with about 4000 to 5000 (if not more) existing PipelineRun when they switch chains on (and a bit less 1000 PipelineRun per hours). They had to up they resource request to at least 4G of memory for the controller to not be killed. However, the controller takes.. a lot of time to handle all the existing PipelineRuns, and thus the queue to sign any "live" / new PipelineRun (or TaskRun) keeps growing.
There is probably some exploration to do around the HA setup (similar to Pipeline, with multiple replicas, …), and fiddling with the controller's flag around the ratelimits, etc...

thinking out loud here - another implicit way to accommodate this use case would be that the chains controller processes the current / active / incoming workloads first before moving to older workloads on the cluster which get queued up; chains can start processing older workloads when it gets some free cycles and a chance to breathe - wdyt?

thinking out loud here - another implicit way to accommodate this use case would be that the chains controller processes the current / active / incoming workloads first before moving to older workloads on the cluster which get queued up; chains can start processing older workloads when it gets some free cycles and a chance to breathe - wdyt?

I don't think there is any way to control this from knative/pkg code though.

You can! Knative has slow/fast queues built in - active items come in on the fast queue, resyncs come in on the slow queue and are picked off as needed.

Ohh that's interersting 🙃


Invoke-RestMethod : 401: Unauthorized

I didn't get this message with the exact same settings in the older, non-forked version.  I have the long lived token in the Settings.ps1 file.  Is this failing on the token?
Invoke-RestMethod : 401: Unauthorized
At C:\scripts\TSFunctions.ps1:25 char:5

Invoke-RestMethod -Uri "https://landgravelake.duckdns.org/api/sta ...

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

CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException
FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

I tried replicating the problem and the only way I was able to is by
inputting an incorrect token.
I have renamed the variables since the non-forked version, is it possible
you are using the old variable names?
I would also recommend using system variables as it will be easier to
update the project if ever you need to.
If that does not work then I will see about sending you the steps to call
the HA API from Postman to take the application out of the equation.
Antoine Gaudreau Simard
On Mon, 18 Jul 2022 at 11:31, John Landgrave (Empowermentoring) <
@.***> wrote:

I didn't get this message with the exact same settings in the older,
non-forked version. I have the long lived token in the Settings.ps1 file.
Is this failing on the tokem?
—
Reply to this email directly, view it on GitHub
https://github.com/AntoineGS/TeamsStatusV2/issues/5, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBAYJ2WQUPS37DVIUSW2QTVUV2D3ANCNFSM534VSF5A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

DOH!!! I copied the settings from the V1 Settings file and didn't notice that you had changed the variables.  Once I configured the variables properly it works.  The other issue I had is that the machine I'm using is a corporate machine and when I log into the machine I have to login with a DomainName\SAMAccount name.  But when you use the environment variable for a user name (to register the webcam piece) it only brings back the SAMAccount name and NOT the domain name.  I created a local user with the same name as my enterprise account but that's not the ideal solution.

If I were to create a config for it, would the same value work for both instances of $Username below?

C:\Users\$Username\AppData\Roaming\Microsoft\Teams\logs.txt
HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\webcam\NonPackaged\C:#Users#$Username#AppData#Local#Microsoft#Teams#current#Teams.exe

If so I'll commit the change and you will be able to create a System Variable to override the Windows' one

PS: I committed the change to the development branch if you want to test it out, including the updated doc with the new variable name!

I’ll try it tonight and report back!
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows
From: Antoine Gaudreau @.>
Sent: Thursday, August 4, 2022 6:02 PM
To: @.>
Cc: John @.>; @.>
Subject: Re: [AntoineGS/TeamsStatusV2] Invoke-RestMethod : 401: Unauthorized (Issue #5)
PS: I committed the change to the development branch if you want to test it out, including the updated doc with the new variable name!
—
Reply to this email directly, view it on GitHubhttps://github.com/AntoineGS/TeamsStatusV2/issues/5#issuecomment-1205812959, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARFPWXE3QJEO5CCHPRFAHYLVXQ4XBANCNFSM534VSF5A.
You are receiving this because you authored the thread.Message ID: @.***>

@jlandgrave did it end up working?
I did merge the changes into the official v1.0.2 release so no need to get the dev branch.

Sorry for my lack of response.  Yes, it worked.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows
From: Antoine Gaudreau @.>
Sent: Wednesday, October 5, 2022 11:57 AM
To: @.>
Cc: John @.>; @.>
Subject: Re: [AntoineGS/TeamsStatusV2] Invoke-RestMethod : 401: Unauthorized (Issue #5)
@jlandgravehttps://github.com/jlandgrave did it end up working?
I did merge the changes into the official v1.0.2 release so no need to get the dev branch.
—
Reply to this email directly, view it on GitHubhttps://github.com/AntoineGS/TeamsStatusV2/issues/5#issuecomment-1268624280, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARFPWXDGNJHC7JTYRB6VOBDWBWQMPANCNFSM534VSF5A.
You are receiving this because you authored the thread.Message ID: @.***>

No worries, just cleaning up open issues, glad to hear it worked!


⚠ Bofrost.at has degraded performance

In 00e7e6f, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2338 ms

Resolved: Bofrost.at performance has improved in 5f477b7.


Store the Funding Trading Bridge smart contract as part of the umber upgrade.

Description
This PR updates the umber upgrade to also store a smart contract provided by Figure.

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[x] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[x] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

surprisingly small/tidy update to make this happen

Yeah. It ended up being a lot easier than I expected.

I forced the umber upgraded on a mainnet quicksync and it has these lines in the log:
4:55PM INF Storing the Funding Trading Bridge smart contract.
4:55PM INF Smart contract stored with codeID: 39 and checksum: "ffaa4f5827f722ce12af244bf8c795217c532fbc4e3b6ff80f305cbd8f7364a3".
4:55PM INF Done storing the Funding Trading Bridge smart contract.

That's using the non-release version of the smart contract, though, so the actual checksum will end up being different. But it looks like it works just fine.


Added Sieve of Eratosthenes in Java

Added a new Algorithm Sieve of Eratosthenes to find all the Prime numbers between 1 and the given number as input.

Please add hacktoberfest-accepted label.

@bhaveshlohana Please add hacktoberfest-accepted label.


build: do not cache output of NPX tasks if package-lock.json changes

A PR with a new Redocly version should have failed because of a bug, but it did not because we cached the results.
See https://github.com/modelix/modelix.core/pull/1037
See https://github.com/Redocly/redocly-cli/issues/1715
To be verified by reviewers

[ ] Relevant public API members have been documented
[ ] Documentation related to this PR is complete

[ ] Boundary conditions are documented
[ ] Exceptions are documented
[ ] Nullability is documented if used

[ ] Touched existing code has been extended with documentation if missing
[ ] Code is readable
[ ] New features and fixed bugs are covered by tests

Why was this closed?

Why was this closed?

It is part of https://github.com/modelix/modelix.core/pull/1042
I should have mentioned that.