Dapr GRPC connection Refused while getting state using .net DaprClient

Hello,
I tried a few links (and trying out suggestions posted https://github.com/dapr/dotnet-sdk/issues/609)  before posting this question , so apologies in advance if this has been repeated before. Would appreciate any pointers . Thanks in advance.

I have a .net core application and I am able to save, store and retrieve the state in the self hosted dapr dev environment that comes with dapr_Redis , dapr_zipkin and dapr_placement containers. The app however is running locally and everything works great. I am able to retrieve all the keys from dapr_redis and use them in the application. The command I used to test all this is------------------> dapr run --app-id DaprMyApp  --dapr-http-port 3500 --components-path ./components dotnet run.

Now , I  have them in a docker-compose file and my app is also containerized (ps: without any Dapr the app runs perfectly fine in docker).  When this line executes ----->await daprClient.GetStateEntryAsync <IList >(storeName, "LightApplications");
The following error is displayed
Dapr.DaprException: State operation failed: the Dapr endpoint indicated a failure. See InnerException for details.
---> Grpc.Core.RpcException: Status(StatusCode="Internal", Detail="Error starting gRPC call. HttpRequestException: Connection refused SocketException: Connection refused", DebugException="System.Net.Http.HttpRequestException: Connection refused
---> System.Net.Sockets.SocketException (111): Connection refused

From the daprd container logs
time="2022-03-30T22:23:13.1586783Z" level=info msg="all outstanding components processed" app_id=DaprMyApp  instance=6e094eaea3b2 scope=dapr.runtime type=log ver=1.6.1
time="2022-03-30T22:23:13.1588662Z" level=info msg="enabled gRPC tracing middleware" app_id=DaprMyApp   instance=6e094eaea3b2 scope=dapr.runtime.grpc.api type=log ver=1.6.1
time="2022-03-30T22:23:13.1589773Z" level=info msg="enabled gRPC metrics middleware" app_id=DaprMyApp  instance=6e094eaea3b2 scope=dapr.runtime.grpc.api type=log ver=1.6.1
time="2022-03-30T22:23:13.1592719Z" level=info msg="API gRPC server is running on port 50001" app_id=DaprMyApp   instance=6e094eaea3b2 scope=dapr.runtime type=log ver=1.6.1
time="2022-03-30T22:23:13.1598482Z" level=info msg="enabled metrics http middleware" app_id=DaprMyApp  instance=6e094eaea3b2 scope=dapr.runtime.http type=log ver=1.6.1
time="2022-03-30T22:23:13.1599458Z" level=info msg="enabled tracing http middleware" app_id=DaprMyApp  instance=6e094eaea3b2 scope=dapr.runtime.http type=log ver=1.6.1
time="2022-03-30T22:23:13.1601179Z" level=info msg="http server is running on port 3500" app_id=DaprMyApp  instance=6e094eaea3b2 scope=dapr.runtime type=log ver=1.6.1
time="2022-03-30T22:23:13.1601313Z" level=info msg="The request body size parameter is: 4" app_id=DaprMyApp   instance=6e094eaea3b2 scope=dapr.runtime type=log ver=1.6.
......
time="2022-03-30T22:23:13.1609711Z" level=info msg="dapr initialized. Status: Running. Init Elapsed 175.1433ms" app_id=DaprCirrus instance=6e094eaea3b2 scope=dapr.runtime type=log ver=1.6.1

The docker-compose file looks like

version: "3.8"
services:
app:
image: DaprMyApp:latest
deploy:
replicas: 1
ports:
- "5001:5001"
- "50001:50001"
depends_on:
- redis
volumes:
- type: bind
source: c:\trust
target: /root/.dotnet/https
environment:
- DAPR_HOST=host.docker.internal
- DAPR_GRPC_PORT=50001
- ASPNETCORE_URLS=https://+:5001;http://+:5000
networks:
- hello-dapr
app-dapr:
image: "daprio/daprd:latest"
#command: [ "./daprd", "-app-id", "DaprMyApp", "-components-path", "/components" ]
command: ["./daprd",
"-app-id", "DaprMyApp",
"-placement-host-address", "placement:50006",
"-dapr-http-port", "3500",
"-dapr-grpc-port", "50001",
"-components-path", "/components"]
ports:
- "3500:3500"
- "50001:50001"
volumes:
- "./components/:/components"
depends_on:
- redis
network_mode: "service:app"
redis:
image: "redis:alpine"
ports:
- "6379:6379"
networks:
hello-dapr:
StateStore Yaml from Components folder WHen tested in use case 1 redis:6379 was replaced by localhost:6379 when the app was running locally .
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: statestore
spec:
type: state.redis
version: v1
metadata:

name: redisHost
value: redis:6379
name: redisPassword
value: ""
name: actorStateStore
value: "true"

DataPoint2
When all the containers come up as described in the docker compose file. the following command also works fine (test as described in https://github.com/dapr/dapr/issues/2838)
Invoke-RestMethod -Method Post -ContentType 'application/json' -Body '[{ "key": "name", "value": "Bruce Wayne"}]' -Uri 'http://localhost:3500/v1.0/state/statestore'
DataPoint3
If i start the sidecar separately ->

dapr run --app-id DaprMyApp  --dapr-http-port 3500 --components-path ./components

Check the port displayed for GRPC from above logs
Checking if Dapr sidecar is listening on GRPC port 54799
Dapr sidecar is up and running.
You're up and running! Dapr logs will appear here.

Then add this port to the DAPR_GRPC_PORT to the environment variable of the machine

Then run the application separately in another window using dotnet run. Works perfectly,

--Also was able to telnet to app-dapr container on port 50001 from the app container after checking the ips of the various containers in docker compose using docker network inspect
-- Also was able to enable profiler on dapr using --enable-profiling and then connect to the app-daprcontainer from the app container using curl "http://<IP_ADDRESS>:7777/debug/pprof/profile?seconds=120" > cpu.pprof  (<IP_ADDRESS> was the ip of the app-dapr container) and  curl connects.
--Also running curl from  the app container to check the healthiness of the app-dapr sidecar container also shows fine status 204
curl -i http://<IP_ADDRESS>:3500/v1.0/healthz
HTTP/1.1 204 No Content
Server: fasthttp
Date: Thu, 07 Apr 2022 00:20:33 GMT
--So not sure why daprclient cannot connect

I was able to get this working running with docker-compose up and turn off the swarm mode on my local docker. All 3 containers work fine (daprd, app and redis) and was able to save and retrieve the state from the application in redis. I was previously using docker stack deploy to test .

@rvittal-btig - Thanks for opening this issue! It looks like you may have already figured this out yourself? It looked like it was going to be a port issue, but it also looked like you had most things specified correctly so I was thinking it may have been a start up/connection issue.
Do you need anything else? Or can we close this issue?

Thank you @halspang  for your response . I am good for now, so please close the issue.
Cheers!


add Francis Crick Institute domain

https://www.crick.ac.uk/

@Swarchal Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please notice that the educational license is for educational use only. If the employees of the Institute, who are neither students nor teachers, need the license, please ask them to send a message to<EMAIL_ADDRESS>to get an academic discount for a paid license.


Typo in example in 17.6. Whole Vector Register Move

There is an example in 17.6 Whole Vector Register Move

vmv4r.v v4, v8   #  Copy v4=v8; v5=v9; v6=v10; v7=v12

Should it be  ?

vmv4r.v v4, v8   #  Copy v4=v8; v5=v9; v6=v10; v7=v11

Yeah, thanks for catching the typo.

Closed by 181f232439496fe7d3ab54672884512947379f22


can't immediately click reveal after data change

try it out here: https://the-pudding.github.io/crossword-puzzles/
click reveal, change dropdown, click reveal (doesn't work, have to hit clear first)


Major update to the existing documentation

Complete this sentence
THIS PULL REQUEST IS NOT READY TO MERGE, but at this point I'd like to solicit feedback.
Feature or improvement description
This pull request provides a major update to the online documentation in the form of general tidying and cleanup plus some restructuring of the layout and organization. All sections were modified except the user guide which will be updated in a subsequent pull request.
Installation

The Getting Started section was removed and incorporated into this section as it was mostly redundant
A higher level structure was added
The availability of precompiled binaries for Windows is made more explicit and clear
The CygWin compile instructions have been removed Lets discuss this in the comments
A deeper explanation of CMake is provided

Testing
This is all structurally the same, but the content has been cleaned up and improved. Better examples for running the regression test are given.
Developer Guide

The Doxygen API reference is enabled (it was previously off)
Subsections were cleaned up and content updated

Sections yet to be improved:

Adding Documentation
Compiling on Windows Linux Subsystem, CygWin, or MinGW in installation appendix

Related issue, if one exists
None
Impacted areas of the software
Documentation
Test results, if applicable
A live version of these updates is available at: https://raf-openfast.readthedocs.io/en/docs-general_updates/

@andrew-platt @ashesh2512 Could you take a look at the changes here and provide some feedback?

Hearing no objections, I'm going to merge this pull request today.
@michaelasprague @jjonkman have you had a chance to look at it?
@bjonkman any further feedback?

@rafmudaf , I haven't had time to read much of this and probably won't have time any time soon. I don't have any objections to you merging it.

I have no objections to merging it.
There are a few items related to BeamDyn that need updating. I will include those in the BeamDyn PR.

Ok, sounds good. This pull request does not change the user documentation, but I have some other ones coming regarding that portion of the docs.


Stop build on errors

If dnf fails in the Dockerfile, don't continue the build.

lgtm

Error deleting container: Error response from daemon: Driver btrfs failed to remove root filesystem f4f039576dc9e3129509936303ce9a181e08935c1f5c8b7954b04d538d69a128: Failed to destroy btrfs snapshot /var/lib/docker/btrfs/subvolumes for f4f039576dc9e3129509936303ce9a181e08935c1f5c8b7954b04d538d69a128: operation not permitted

It seems CircleCI does not give us the rights to delete images.
I will stop doing it by default. I keep the target make delete-docker-image but it is not executed by default anymore.
PTAL
/cc @schu

lgtm


esphomebtproxy

Hi,
Does this add on work with the esphomebtproxy?
https://esphome.github.io/bluetooth-proxies/

Probably not. This is not a native HA integration, even as a custom component, but a stand-alone script that communicates with HA vi aMQTT. As such the device that runs the script needs bluetooth communication and the scale needs to be within reach


First cell of magic code input is marked green when authenticating with expired magic code

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

Action Performed:

Navigate to sign in page
Enter email and click on continue
Copy an expired magic code from email
Open new tab on the same window you opened the app
Paste the magic sign-in link > prefix the link with 'staging' > press enter key
Open the tab where you originally singed in

Expected Result:
All magic code input cells should be marked with red
Actual Result:
First cell of the magic input field is marked green
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

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

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

Version Number: 1.3.30-5
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/6e660fc9-31b2-4e70-872e-90f9d0496bcf
https://github.com/Expensify/App/assets/43996225/63eea045-846f-483b-8286-6a6925b732b2
Expensify/Expensify Issue URL:
Issue reported by: @Natnael-guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686833554570519
View all open jobs on GitHub

Hey, I am heading OOO shortly, so assigning another bug0 team member to help watch over this issue whilst I am OOO. thank you!

Proposal
Please re-state the problem that we are trying to solve in this issue.
First cell of magic code input is marked green when authenticating with expired magic code
What is the root cause of that problem?
There are two main issues here.

The "Focus styling" is added after "Error styling"

https://github.com/Expensify/App/blob/6183609c577f2310928bb4e8ee23b52f6dd28e00/src/components/MagicCodeInput.js#L316-L317

The default behaviour when users enter the Magic Code, the code is displayed. When the users click the expired magic code URL, the code is not carried on to the screen

The root cause is because validateCode is not passed in ONYXKEYS.CREDENTIALS in src/libs/actions/Session/index.js on failure in the function signInWithValidateCode
https://github.com/Expensify/App/blob/6183609c577f2310928bb4e8ee23b52f6dd28e00/src/libs/actions/Session/index.js#L431-L445
What changes do you think we should make in order to solve the problem?
To solve the first issue we need to move the "Focus styling" before "Error styling"
focusedIndex === index ? styles.borderColorFocus : {},
props.hasError || props.errorText ? styles.borderColorDanger : {},

To copy the magic code add validateCode to ONYXKEYS.CREDENTIALS
    const failureData = [
        {
            onyxMethod: Onyx.METHOD.MERGE,
            key: ONYXKEYS.ACCOUNT,
            value: {
                isLoading: false,
                loadingForm: null,
            },
        },
        {
            onyxMethod: Onyx.METHOD.MERGE,
            key: ONYXKEYS.SESSION,
            value: {autoAuthState: CONST.AUTO_AUTH_STATE.FAILED},
        },
        {
            onyxMethod: Onyx.METHOD.MERGE,
            key: ONYXKEYS.CREDENTIALS,
            value: {validateCode: validateCode},
        },
    ];

Result of the above changes can be seen in the video
https://github.com/Expensify/App/assets/2232432/616a3f15-e1d2-421e-9905-41f44a3d1ebd
What alternative solutions did you explore? (Optional)
None

This is a pretty wild one to reproduce, but I do think we can fix that green in the first input. Opening this up to the community.

Sounds good to me, closing!


Need Help on Keci embedding tool

Hello Dr. Caglar Demir,
My name is Happi Happi Bill Gates and I'm a Phd student in Computer Science at the University of Montpellier in France.
I'm writing to you about your work on embeddings. I want to use it to generate a set of feature vectors for alignable and non-alignable instances or entities.
I've been able to install and run it but I'd like to know if keci can really allow me to generate a feature vector from two instances (with properties) that are alignable or not.
I will  give you an example to understand.

source.d
entity1 property1 value1
entity1 property2 value2
entity1 property3 value3
...

target.d
entity-1 property1 value-1
entity-1 property2 value-2
entity-1 property3 value-3
...

same_as.d
entity1 aligned_with entity-1

What i want is something like that in terms of embeddings :

embeddings.d
E(entity1-entity-1) = [f1,..., f_d]

I hope I've made myself clear
Best regards
Bill

Caglar answer by mail :
As mentioned earlier, please open an issue in the repository next time if you want to ask a question or a feature request.
I am afraid your question is ill-defined given that entity1 and entity2 are discrete values, subtraction is not defined.
Yet, you can E(entity-a) - E(entity-b) where entity-a aligned_with entity-b and entity-a and entity-b do occur in the source and target knowledge graphs, respectively.

Runing this example code https://github.com/dice-group/dice-embeddings/tree/robust#how-to-train results in creating a folder, where embedding files are stored.
To tackle the embedding alighment problem, you can very well directly these files.
The problem of your interest does not depend on a specific  knowledge graph embedding model.
If you face any issue in training a KG model, please feel free to open an issue :)


Create client module for managing blobs

create a client lib using Azure SDK for uploading images to blob storage

create a client lib using Azure SDK for uploading images to blob storage

add option to add guid, but default to the given file name.


Optimizing Git Artifact Handling

Summary
I'm a very enthusiastic fan of argo.  It takes care of so many useful things.  However, I'm wondering if there has been any discussion around optimizing the handling of git artifacts?  I looked through the issues (open and closed) and didn't really see any mention specifically how argo could cache git repos in the cluster to improve performance.
Motivation
When using git artifacts from git repos outside the cluster (e.g., Github), the clone process can be quite time consuming and you can even run into rate limiting issues.  In practice, you can quickly get to a point where the vast majority of information traveling over the wire is repeated.
It strikes me that one could use a PVC as a place to mirror git repos.  In this way, the use of a git artifact would first be to sync the mirror and then perform a checkout by mounting the mirror read only into the container.  The initial "sync" of this mirror would be effectively involve the same time and data as the current approach.  But the subsequent sync operations would simply involve one or more fetch operations to ensure things were in sync which is far less data.  Keeping the mirror cluster local just seems like a huge potential efficiency gain.
Now, this clearly would require some development effort.  I guess my main question is whether this has been discussed before and whether any faults were identified?  One obvious issue that occurs to me would be around security.  But since git repos don't have fine grained authorization machinery, the only real question is whether a given workflow should have access to the mirror or not and that can be answered by whether the "sync" fetching is successful (if so, there is no reason not to give the user access to the entire local git mirror).
 ;-)

To improve performance do two things:

Shallow clone using depth: 1.
Clone once to a volume as per the the CI example.

Shallow clone does help.  But we have use cases where we aren't necessarily working on a branch tip.  We'd like the flexibility to clone an arbitrary commit (may not be a branch or even tagged) and that isn't really possible.
As for the CI case, it looks to me from that example that it is creating a temporary PVC for this individual workflow and then reusing it across steps.  That's fine.  But it doesn't really address my concern which is that we run lots of workflows that share the same git repo.  So we can't cache the result within a workflow.
I completely recognize that you could take care of all this within your workflow.  You could have the first step of the workflow be to trigger a syncing of the repo and then mount the synced git repo read only and locally, much as I've described.  So I realize it can be done in argo.  It just seems like, from the user's perspective, such mirroring/caching could provide benefits for nearly anybody using git artifacts vs. having to roll their own solution one user at a time.
But talk it cheap, I realize it would be a lot of work to implement.  I'm just trying to figure out whether the concept itself is flawed in some way I can't see or if it is only the effort required that has prevented people from implementing it.

You're correct. We could expose the git clone --depth 1 -b branch ... - but this does not work for tags or hashes.
Could you run a Git proxy in your cluster?

I'm not sure what you mean by a "git proxy".  If I search for "git proxy", all I get are articles about running git behind an http proxy.  Is there a specific tool you were thinking of here, because I've been unable to find something that does what I describe "out of the box".

I did come across this.  I'll look into it more closely tomorrow.

https://github.com/google/goblet?

I saw that.  The repo has exactly one commit.  It doesn't really inspire a lot of confidence.  I also looked a bit more into git-cache-http-server.  I'm giving that a go.  Definitely useful, but doesn't quite solve the whole problem. With git-cache-http-server, I can keep a cluster local mirror (effectively).
I can't speak for others, but most of the time in my workflows what I really want in my workflow is to do a checkout, not a clone/fetch of a specific commit (not necessarily a branch or tag).  The depth settings, etc. kind of mimic this, but they don't work for commits in general.  So what I really need is not just a local server that optimizes bandwidth (which is what git-cache-httpserver helps with), but I'd like to actually have a read-only repo directly accessible from the container so that I can simply checkout just the files I need (vs. replicating a whole repo just for the sake of a few files).  As far as I can tell, argo always does a clone/fetch followed by a checkout.  This is a lot more data than I really need for my workflow.  So having a read-only repo already mounted to my container would allow for just a checkout which is really just what I need.
Even better would be a cache of the last checkout so I could just refresh that checkout (because the files won't change that much).  But that may be asking a bit much and introduce a bunch of "statefulness" that could lead to odd errors related to side effect.

I'm sure you're not alone in this. If you come up with a solution, especially one that can deal with auth, then I'd love to share that with the communit.


Can I dynamically execute pip install after starting the docker service to install new packages without terminating the service?

Hello! Can I dynamically execute pip install after starting the docker service to install new packages without terminating the service?
I can now install the package via python-requirements.txt, but it requires recompiling and building the docker container, Is there any way to pip install directly in the started container?

fixed #75


Imperfect recipes tree-shaking

Description
I just created a Vite project,
then created two recipes:

Button
Chip

After that, I used the Button recipes in App.tsx file.
By running the npx vite-bundle-visualizer, following result created:

As can be seen, the Chip and Button recipes are placed inside the bundle.
I wonder why this happens. The correct behaviour would be purging and removing Chip recipe from the bundle since only Button component is used in the app.
Link to Reproduction
https://stackblitz.com/edit/vitejs-vite-n4krty
Steps to reproduce

Create a project and setup PandaCSS
Create two recipes and add them to the config
Use only one of them in App
Build and analyze the bundle size.set up

JS Framework
React (TS)
Panda CSS Version
^0.15.4
Browser
No response
Operating System

[X] macOS
[ ] Windows
[ ] Linux

Additional Information
No response

Good catch @theMasix
I just pushed a fix for this. Here's what it looks like now:

We'll release an update shortly. If the issue persists after upgrading, I'll re-open it.

Any update on the package release? Is it fixed?

@theMasix Will be released today


Machine Configuration

What's the Machine Configuration when you run the program run_rt.py（WSPred）, I run this code and it's always tell me memory error

We use a Linux server for testing, which has 160G memory. If you run the code for 20 rounds in parallel, it will need about 40G memory due to the parallelization of tasks. So you would better to run 1 round instead.

Thanks for your reply. Now I use a Linux server for running the program, for 20 rounds and 300 iteration in parallel. But it took about 5 days to finish. May I ask how long you run the program for 20 rounds and 300 iteration in parallel?


Release notes tab does not remember scroll position

VSCode Version: 1.11.1
OS Version: Ubuntu 16.19

Steps to Reproduce:

Open release notes
Scroll
Change tab
Change tab back to release notes
Scroll position of release notes tab is not preserved

Duplicate of #15214


Hint that painting shadows are complex

Previously, we considered them one operation in the compositor, which didn't
trigger caching. Now we have a way to explicitly hint that the compositor
should cache a layer.

@Hixie @HansMuller

lgtm

LGTM


🔥How to return updated bundle when app resumes

Is there any way in rn to send updated props when the app resumes from background state.
I want that if my app is called from any other image sharing app (like gallery), so the app should get the updated props.
The current situation is,  when user share an image from the gallery, rn app opens and receives the image path in initial props and navigate to image upload screen just like as uploading a new tweet with image

Here is the code setup for this
Manifest file
 <intent-filter>
        <action android:name="android.intent.action.SEND" />
         <category android:name="android.intent.category.DEFAULT" />
        <data android:mimeType="image/*" />
    </intent-filter>

MainActivity.java
package com.myN;

import com.facebook.react.ReactActivity;

//try
import com.facebook.react.ReactActivityDelegate;
import android.content.Intent;
import android.os.Bundle;
import android.net.Uri;
import java.io.InputStream;
// another try
import java.io.File;
import android.provider.MediaStore;
import com.facebook.react.ReactRootView; //change

public class MainActivity extends ReactActivity {

  /**
   * Returns the name of the main component registered from JavaScript. This is used to schedule
   * rendering of the component.
   */

  private ReactRootView mReactRootView; //change
  @Override
  protected String getMainComponentName() {
    return "myN";
  }

  //try
 @Override
    protected ReactActivityDelegate createReactActivityDelegate() {
        return new ReactActivityDelegate(this, getMainComponentName()) {

            @Override
            protected Bundle getLaunchOptions() {

                Intent intent = MainActivity.this.getIntent();
                Bundle bundle = new Bundle();
                Uri imageUri = intent.getParcelableExtra(Intent.EXTRA_STREAM);

                if (imageUri != null ) {
                    bundle.putString("image", imageUri.toString());
                    return bundle;
                }else{
                    bundle.putString("image", "");
                    return bundle;
                }

            }

        };

    }

}

I know this is not the place for asking questions but the documentation does not provide much details about how to communicate between native and react-native,
I have already tried AppState and I am using this,
It logs the same image file path when user shares the image with my app ( the app was in the background ), (obviously app opens but app shows the old image when new image get shared), but the result what I am expecting is, it should receive the updated props and return the updated the bundle.
I have read the documentation
here https://reactnative.dev/docs/communication-android#passing-properties-from-native-to-react-native , but I am not getting where should I write getAppProperties(); which updates the props and return a newly updated bundle.
I have asked the same question on stack overflow: https://stackoverflow.com/questions/62661326/how-to-return-a-new-bundle-in-react-native-when-app-resumes
React Native version:
Run react-native info in your terminal and copy the results
System:
OS: Windows 10 10.0.18363
CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
Memory: 5.25 GB / 15.88 GB
Binaries:
Node: 12.16.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.4 - C:\Users\user\AppData\Roaming\npm\yarn.CMD
npm: 6.13.4 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
IDEs:
Android Studio: Version  <IP_ADDRESS> AI-193.69<IP_ADDRESS>14223
Languages:
Java: 1.8.0_211
Python: 3.8.0
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: 0.62.2 => 0.62.2
npmGlobalPackages:
react-native: Not Found

Another user on StackOverflow with the same question
https://stackoverflow.com/questions/61991543/react-native-android-launchmode-singletask-getlaunchoptions-doesnt-get-called-a

Solved this issue, by using a third-party package,  react-native-share-extension, it did all the work for you :)
Also, use launchMode to singleTask, this will prevent creating a new instance of the app.


Fixed Overlapping of download and mode changing button .

I fixed the overlapping of mode changing and the download button .
closes : #537

Hii @arghadipmanna101 please add gsoc and level in labels


Make indentation consistent in pyguide.md

Since the guide's indentation is 4, it is good to have 4-space indentation in all examples through out the document. There were 2-space examples which made me confused.

Thanks.  Agreed this looks odd to people.
For what it's worth, the reason our guide is a bit messy this way is that we use two space indentation for our internal style but don't recommend that to the rest of the world which standardizes on four.  We currently do not have an appropriate transformation setup to fix all of this in the examples as we publish the external version of the guide from our internal master.
I'm leaving this PR open assigned to me to deal with that one way or another.


[Flutter 2.5.0] ThemeData.primaryColor does not take effect

Steps to Reproduce
Just run app on Flutter 2.5.0
 static final global = ThemeData(
    primaryColor: ColorsX.primary,
)

There is no problem on 2.2.3, but 2.5.0 is displayed as the default blue color and does not work.
Env
[√] Flutter (Channel stable, 2.5.0, on Microsoft Windows [Version 10.0.18362.1082], locale zh-CN)
    • Flutter version 2.5.0 at F:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4cc385b4b8 (2 days ago), 2021-09-07 23:01:49 -0700
    • Engine revision f0826da7ef
    • Dart version 2.14.0
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at F:\android\SDK
    • Platform android-30, build-tools 31.0.0
    • ANDROID_HOME = F:\android\SDK
    • Java binary at: F:\jetbrains\apps\AndroidStudio\ch-0\202.7351085\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.10.4)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.10.31515.178
    • Windows 10 SDK version 10.0.18362.0

[√] Android Studio (version 4.2)
    • Android Studio at F:\jetbrains\apps\AndroidStudio\ch-0\202.7351085
    • Flutter plugin version 59.0.1
    • Dart plugin version 202.8531
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.18362.1082]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 93.0.4577.63
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 92.0.902.84

• No issues found!

Hi @ggdream, Thanks for filing the issue. I can reproduce the issue, primary color does not take effect. There's an ongoing change in progress to migrate to ColorScheme. But I believe this bug is not intentional.
However, you can set the primaryColor as of now using ColorScheme
theme: ThemeData(
        colorScheme: ColorScheme.light().copyWith(primary:  ColorsX.primary,),
      ),

Labeling this issue as a bug for further investigation
cc @HansMuller

Hi @ggdream, Thanks for filing the issue. I can reproduce the issue, primary color does not take effect. There's an ongoing change in progress to migrate to ColorScheme. But I believe this bug is not intentional.
However, you can set the primaryColor as of now using ColorScheme
theme: ThemeData(
        colorScheme: ColorScheme.light().copyWith(primary:  ColorsX.primary,),
      ),

Labeling this issue as a bug for further investigation
cc @HansMuller

I will try it, thank you for the reply and the solution.

When setting the primary color via primaryColor, did it take into account text that would be affected by the change? With colorScheme it definitely does not.

Hi @ggdream, Thanks for filing the issue. I can reproduce the issue, primary color does not take effect. There's an ongoing work in progress to migrate to ColorScheme. But I believe this change (primaryColor) is not intentional.
However, you can set the primaryColor as of now using ColorScheme
theme: ThemeData(
        colorScheme: ColorScheme.light().copyWith(primary:  ColorsX.primary,),
      ),

Labeling this issue as a bug for further investigation
flutter doctor -v
cc @HansMuller

This was part of the work that we are doing to clean up the Theme system and make everything more consistent and based off of the ColorScheme colors.
In this case the AppBar's default background color was changed to use ColorScheme.primary as part of #71184.
We will eventually be moving all components away from ThemeData.primaryColor. As mentioned by @maheshmnj above, you can fix this by also providing a color scheme with the same primary color that you desire:
   theme: ThemeData(
     primaryColor: ColorsX.primary,
     colorScheme: ColorScheme.light().copyWith(primary: ColorsX.primary),
  );

Closing this as it is working as intended.

One can temporarily use backwardsCompatibility: true, in the app bar to revert to ThemeData.primaryColor.

@darrenaustin When using ThemeData.primaryColor for the app bar the text color is automatically set to something that contrasts with it, but when using ColorScheme that is not the case. Is something like colorScheme: ColorScheme.light().copyWith(primary: ColorsX.primary) considered bad practice as one should always be using a complementing and complete ColorScheme rather than just overriding one of a given one's properties?

I'm not sure whose responsibility this is, but you guys should consider updating the reference to ThemeData.primaryColor in codelabs

Thanks all.


Munkii 444 OG Collection - Minting issue

Same as every other issue:
The Munkii 444 OG Collection is in MINT FREEZE.
https://soonaverse.com/collection/0x35edbce12110b233441a11847ab72cd2eac7ed49

related to https://github.com/soonaverse/app/issues/182

related to https://github.com/soonaverse/app/issues/182


[event-hubs] Use Long when representing sequence number (and offset)

ServiceBus uses a Long class to represent the sequence number in messages.
According to the docs the sequence number is a 64-bit integer. Javascript, through number can only handle 53-bits.
The documentation for ServiceBus states:
The SequenceNumber value is a unique 64-bit integer assigned to a message as it is accepted and stored by the broker and functions as its internal identifier. For partitioned entities, the topmost 16 bits reflect the partition identifier. Sequence numbers roll over to zero when the 48/64-bit range is exhausted.

Which would seem to indicate that we might be okay since part of the 64-bit range is redundantly used to store off information that we already have (ie, the partition identifier, assuming they match what we think of as the partition ID).
This issue is a reminder for us to follow up with the EventHubs team and make sure that we're not creating a potential issue here and possibly just move over to the same Long type and avoid the issue entirely.

@chradek, Please do the required follow up here to help come to a decision on whether we want to make this change or not

I reached out to the service team and got the following response:

For Event Hubs case, Sequence number is long data type and it provides the logical sequence number of an incoming event. And, the value doesn’t contain the partition Id.

So it appears we do need to use Long instead of number.

Just assigning some people since this issue was orphaned with no owner.


feat(next-queries): next queries group within results

EX-4528
Adds groups of Next Queries within the results in the result grid based on this designs.
For testing search a query that returns next queries (ex: shirt) and scroll a couple of pages.

FYI: We have detected some increased disk usage in our Jenkins master and have traced it to the builds of this PR generating logs between 2GB-4GB in size.
As you can see, the Jenkins UI can't even display them
https://jenkins.internal.shared.empathy.co/job/GitHub X/job/x-archetype/view/change-requests/job/PR-63/2/console
but here's a screencap of the log

Looks like you've been hit with the colors.js issue 😄
https://www.theregister.com/2022/01/10/npm_fakerjs_colorsjs/

Deleted colors.js 1.4.2 which was cached on our Nexus

FYI: We have detected some increased disk usage in our Jenkins master and have traced it to the builds of this PR generating logs between 2GB-4GB in size.
As you can see, the Jenkins UI can't even display them https://jenkins.internal.shared.empathy.co/job/GitHub X/job/x-archetype/view/change-requests/job/PR-63/2/console
but here's a screencap of the log

Looks like you've been hit with the colors.js hijack issue 😄
GHSA-5rqg-jm4f-cqx7
https://www.theregister.com/2022/01/10/npm_fakerjs_colorsjs/

F$%k!, thanks @Roberdvs  we will try to update the dependency ASAP to avoid this


Does not work with jQuery 3.1.1

Drop down is missing flags and countries when using jQuery 3.1.1
Error:
    jquery.min.js:4 Uncaught TypeError: a.indexOf is not a function
r.fn.load @ jquery.min.js:4
(anonymous function) @ countrySelect.min.js:1
(anonymous function) @ countrySelect.min.js:1
(anonymous function) @ countrySelect.min.js:1
..... Uncaught TypeError: $(...).countrySelect is not a function(anonymous function) @

Pull https://github.com/mrmarkfrench/country-select-js/pull/34 fixes this issue.


Added tests for flat creation and member retrieval

Pull Request Information
Relates to Github Issue: #183
What is the PR Type:

feature

Describe the added/fixed behaviour:
Tests have been added to FlatControllerTests to ensure flat creation and retrieving flat members works as intendecd
Checklist

[x] Pull request has suitable title, adequately described and associated with a github issue
[x] Branch name follows correct convention (e.g. feature/[id]-some-feature)
[x] Branch builds and executes with no errors
[x] Test cases has been generated for the feature and test cases pass
[x] Updated relevant wiki/documentation

Additional Information
Although This pull request comes from @NathanMills1, this work was undertaken by @Vaibhavnz

Remove testdb.db please.

Closed by #196 instead :)


enh(javascript) allow leading # for private class fields (stop treating as illegal)

As of an upcoming release of ECMAScript (almost certainly 2021), private class fields may be defined with this syntax:
class Demo {
  #neato;
}

Accordingly, treating all non-shebang # as illegal markers for JavaScript is no longer viable. Instead, support $, _, and [A-z] as well as ! as legal identifiers here.
Note that this will still fail in cases where Unicode characters are used as the first character of a private class field name.
Fixes #2700

Right idea, but we can't just remove this.  It needs to be updated to be aware of what private fields look like. So I think that means it would be a # followed by anything other than a valid symbol [a-z_] would still be illegal?  So, same idea but update the negative look-ahead... the ! check isn't needed anymore since we now have a feature to handle shebang lines individually.
The illegal checks are part of the reason our auto-detect is so fast and accurate... this type of check immediately prevents JS from flagging Ruby, Python, or MANY other languages that use # for commenting... instead when it sees them it can immediately stop processing and be sure they are not Javascript.

Thank you! That makes sense, and I figured we might need to iterate on this extremely naïve first pass. I'll check the actual spec text and make sure the negative lookahead matches that.

@joshgoebel worth note that if the rule you're using for highlighting is just expecting [_A-z], it's going to miss a lot. The actual spec allows a full range of Unicode characters and also $. So #$α is totally a legitimate name for a private class field. And in a project I'm working on, we actually do use Greek letters in certain spots. 😬 Not sure how to tackle that with a regex that handles it via negative lookahead.

@chriskrycho I'm carrying this one to the home plate so I can get it merged!  Thanks for the PR!

Ah, thank you, and so sorry for the delay. 2020 has been a year.


ruff: docstring-code-format = true

coverage: 85.462% (-0.01%) from 85.476%
when pulling dad1511eaab98ed79af1c003d48f109926db6161 on bact:dev
into fcef21c71a449740e8f2f80722393527dbe49cbf on PyThaiNLP:dev.


[COPY] Add profiler memory.enabled option

This is identical to @agoallikmaa's #573 in hopes that we can get it merged sooner rather than later. Feel free to close and accept #573 if the commit signing gets worked out first.

Actually, this probably won't work as well since the commits got brought over instead of recreated. Ugh.


How can I order by rand() using this library?

I'm trying to call a query which select {{x}} random rows.
Thanks in advance.

@ikhanhmai use the documentation from this Github repo


ROADMAP for image-tools

Hi everyone,
In order to achieve the release as soon as possible, I made the following roadmap, any comments are welcome. cc @opencontainers/image-tools-maintainers @wking
Currently, image-tools has implemented the following functions:
1.Validate one or more image files
2.Unpack an image or image source layout
3.Create an OCI runtime bundle
image-tools has implemented the most important verification function, so I think image-tools can already prepare v1.0 release.
The following a roadmap draft, any comments are welcome.
v1.0: Solve image-tools problems.
There are two known problems with image-tools:
1.How to handle multiple manifests with the same ref.name:
We discussed this problem in #164  and proposed a solution waiting for review in #169.
2.Autodetect problem:
The main reason for this problem is that the main judgment in the Autodetect function is that the Mediatype field becomes a non-required field in spec. So that leads to validation errors.
We discussed this problem in #62  an proposed a solution waiting for review in #184 and #62 (Two different solutions).
v1.x: Add additional functionality.
Add create-layer sub command #8
Add create-image sub command
Add oci-cas sub command #40  (This still need to discuss, the current views are not uniform.)
These above features are additional features. We can wait until later.
Most of the plans have a corresponding patch, but we need to discuss and optimize.Please come up with anything to add.

ping @opencontainers/image-tools-maintainers

@coolljt0725 UI in #169 needs to be fixed: these images don't have a name, they have a tag. The API should allow for arbitrary label selection. The current situation prevents us from ever adding a name in the future. I described the desired behavior and syntax in https://github.com/opencontainers/image-tools/issues/164#issuecomment-317904913.
Something like this:
oci-image-tool validate --select annotations."org.opencontainers.ref.name"=latest --select platform.os=linux ubuntu.tar

Fine. I'll modify it.


xenvm_gicv3: Enable config parameters in gicv3 to match xenvm board

The same config paramters should be enabled in xenvm_gicv3 as in xenvm. Otherwise there is no posibility to build it.

Closing as not relevant anymore


Add From implementation for SdkConfig to Builder

Motivation and Context
This example context is if you're building a CLI that allows arguments to change something like AWS Profile, and then you pass that SdkConfig to your library for dealing with AWS Services, you may want to change fields in the SdkConfig, but there are no setter methods and the fields are private, and you also can't convert back to a builder.
The example below is a common requirement, when using LocalStack we want to change all endpoints to our local machine:
/// Checks for LOCALSTACK_ENDPOINT env var, if it exists build a new SdkConfig from the old one
/// then apply the endpoint from the env var.
/// SdkConfig has no public fields or setter methods, so we must build a new one
pub fn check_localstack_bad(config: SdkConfig) -> SdkConfig {
    if let Ok(endpoint) = std::env::var("LOCALSTACK_ENDPOINT") {
        let mut builder = aws_types::SdkConfig::builder();

        if let Some(x) = config.credentials_provider() {
            builder = builder.credentials_provider(x.clone());
        }
        if let Some(x) = config.http_connector() {
            builder = builder.http_connector(x.clone());
        }
        if let Some(x) = config.region() {
            builder = builder.region(x.clone());
        }
        if let Some(x) = config.retry_config() {
            builder = builder.retry_config(x.clone());
        }
        if let Some(x) = config.timeout_config() {
            builder = builder.timeout_config(x.clone());
        }

        let e = Endpoint::immutable(
            Uri::from_str(&endpoint).expect("LOCALSTACK_ENDPOINT is not a valid uri"),
        );
        return builder.endpoint_resolver(e).build();
    }
    config
}

Which are extra allocations and also takes a long time for a user to look through aws_smithy_types, aws_types, and aws_config before realizing there is no better way (maybe there is, but I couldn't find one).
Description
This change allows you to:
pub fn check_localstack(config: SdkConfig) -> SdkConfig {
    if let Ok(endpoint) = std::env::var("LOCALSTACK_ENDPOINT") {
        let e = Endpoint::immutable(
            Uri::from_str(&endpoint).expect("LOCALSTACK_ENDPOINT is not a valid uri"),
        );
        return Builder::from(config).endpoint_resolver(e).build();
    }
    config
}

And also is idiomatic for Rust, allowing other associated conversion methods:
let builder: Builder = config.into();

This doesn't compromise the builder pattern that's being used but makes SdkConfig much more ergonomic.
Testing
On Arch Linux x86_64 with toolchain:
stable-x86_64-unknown-linux-gnu (default)
rustc 1.61.0 (fe5b13d68 2022-05-18)

Tested using client code that makes use of aws-types, aws-smithy-types and aws-config which didn't break anything.
Did a cargo test, all passing

Checklist

[x] I have updated CHANGELOG.next.toml if I made changes to the smithy-rs codegen or runtime crates
[x] I have updated CHANGELOG.next.toml if I made changes to the AWS SDK, generated SDK code, or SDK runtime crates

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

What if instead of passing an SdkConfig into your library, you passed the ConfigLoader instead?:
fn main() {
  // Load config by reading env but don't finalize it
  let mut loader = aws_config::from_env();
  // conditionally set the localstack endpoint, then build the config
  let config = check_localstack(loader).load().await;
}

pub fn check_localstack(mut config: ConfigLoader) -> ConfigLoader {
    if let Ok(endpoint) = std::env::var("LOCALSTACK_ENDPOINT") {
        let e = Endpoint::immutable(
            Uri::from_str(&endpoint).expect("LOCALSTACK_ENDPOINT is not a valid uri"),
        );
        config.endpoint_resolver(e)
    }
    config
}

What if instead of passing an SdkConfig into your library, you passed the ConfigLoader instead?

Haha yeah, this is much a better idea, appreciate the response thanks


Add Provider.orElse(Callable)

When the user wants to fall back to a calculated value in case a Provider has no value associated with it, currently they have the following options:

Rely on Project to create the provider, which means we are introducing a dependence on the whole of the project state that is unnecessary:

public DependencyReportTask() {
    getConfigurations().convention(
        getDefaultConfigurationName()
            .map(this::lookupConfigurationByName)
            .orElse(
                getProject().provider(this::getNonDeprecatedTaskConfigurations)
            )
    );
}

Inject ProviderFactory which adds a lot of boilerplate:

@Inject
public DependencyReportTask(ProviderFactory providerFactory) {
    getConfigurations().convention(
        getDefaultConfigurationName()
            .map(this::lookupConfigurationByName)
            .orElse(
                // Use ProviderFactory to create a provider
                providerFactory.provider(this::getNonDeprecatedTaskConfigurations)
            )
    );
}

This would be a lot nicer:
public DependencyReportTask() {
    getConfigurations().convention(
        getDefaultConfigurationName()
            .map(this::lookupConfigurationByName)
            .orElse(
                // Just pass a Callable
                this::getNonDeprecatedTaskConfigurations
            )
    );
}

And given that ProviderFactory.provider(Callable) does nothing else, just wraps the Callable in a DefaultProvider, we could easily add this method.

Maybe a static provider(Callable) method would be enough?

I think we should try to move away from using Callable to provide calculated values, as it is very error prone. It is easy for build dependencies and provenance to go missing, and we've seen this cause strange, difficult to diagnose problems in practice many times. Of course, there are ways to address this, but in general I think it might be cheaper overall to not use Callable.
So, in the example above, I would have getNonDeprecatedTaskConfigurations() return a Provider and use orElse(getNonDeprecatedTaskConfigurations()).

I agree that in this case it would be better to have getNonDeprecatedTaskConfigurations() return a Provider -- that way we could track where the value comes from all the way back to the configurations themselves.


1.0.1974 broke the mod

Something with custom work types was changed and since this mod includes roof maintenance it also broke.

Fixed in Commit 48831e61e1b14320654ccf8053c82c82cda559f3


Tests don't run out of the box due to missing /etc/aclhound/aclhound.conf

Setting up ACLHound locally following the config documentation - some deviations from the instructions actually, but should be ok:
$ git clone git@github.com:job/aclhound.git
$ cd aclhound
$ virtualenv venv
$ source venv/bin/activate
$ pip install -r requirements.txt
$ make test

snip some outputs, and get failures:
======================================================================
ERROR: test_01__build_ios (tests.test_regression.TestAclhound)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/jzohrab/Documents/Projects/aclhound/tests/test_regression.py", line 68, in test_01__build_ios
    u'debug': False, u'jenkins': True})
  File "/Users/jzohrab/Documents/Projects/aclhound/aclhound/cli.py", line 215, in __init__
    self._settings = Settings()
  File "/Users/jzohrab/Documents/Projects/aclhound/aclhound/cli.py", line 82, in __init__
    sys.exit(2)
SystemExit: 2

======================================================================
ERROR: test_02__build_asa (tests.test_regression.TestAclhound)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/jzohrab/Documents/Projects/aclhound/tests/test_regression.py", line 87, in test_02__build_asa
    u'debug': False, u'jenkins': True})
  File "/Users/jzohrab/Documents/Projects/aclhound/aclhound/cli.py", line 215, in __init__
    self._settings = Settings()
  File "/Users/jzohrab/Documents/Projects/aclhound/aclhound/cli.py", line 82, in __init__
    sys.exit(2)
SystemExit: 2

The failure is due to cli.py's lines:
        if not os.path.exists('/etc/aclhound/aclhound.conf'):
            print("ERROR: Could not open /etc/aclhound/aclhound.conf")
            print("Has ACLHound been properly installed? Contact your admin")
            sys.exit(2)

The fresh install creates /etc/aclhound/aclhound.conf.dist, but not /etc/aclhound/aclhound.conf.
If you give some notes on how this should be resolved here, I can fork and PR back to master.  Should I just copy the .dist file to .conf?

Have copied .dist file to .conf, running into further errors.  Will add comments to this issue as I run into them and resolve them.  Ideally, the tests would run successfully on initial check out.

A PR is most welcome when you have resolved the issues. While the project is mostly OS agnostic, I'd prefer to at least properly support Debian in a documented way. Thank you

Np, may need some guidance/feedback on my submission, and I'll make whatever adjustments needed.  Happy to contribute, thanks @job.

When PR #55 is closed, this issue can be closed.


Undefined index: username {"exception":"[object] (ErrorException(code: 0): Undefined index: username at /u02/html/works/vendor/adldap2/adldap2-laravel/src/Auth/Resolver.php:46)

Laravel Version: 5.5
Adldap2-Laravel Version: 3.0
PHP Version: 7.1
LDAP Type: Active Directory

Description:
Undefined index: username {"exception":"[object] (ErrorException(code: 0): Undefined index: username at /u02/html/works/vendor/adldap2/adldap2-laravel/src/Auth/Resolver.php:46).
Hi
i'm using this package since 5 months on wards it works great.suddenly i got the above error.can any one guide me to solve this.

Steps To Reproduce:

Hi @bmadala33, did you modify your LoginController.php? It looks like you're not passing in the proper array into the Auth::attempt() method.
Are you using a username to authenticate? If so, you must provide the users username in the username array key when passing the credentials into Laravel's Auth::attempt() method:
$credentials = [
    'username' => 'jdoe',
    'password' => 'pwd123',
];

if (Auth::attempt($credentials)) {
   //
}

See this line:
https://github.com/Adldap2/Adldap2-Laravel/blob/8c79a01014dc16137a7e2b0c215663c640182f6d/src/Auth/Resolver.php#L46

Hi @stevebauman,
i have modified my login controller
here is my LoginController.php
`class LoginController extends Controller
{
/*
|--------------------------------------------------------------------------
| Login Controller
|--------------------------------------------------------------------------
|
| This controller handles authenticating users for the application and
| redirecting them to your home screen. The controller uses a trait
| to conveniently provide its functionality to your applications.
|
*/
use AuthenticatesUsers;

/**
 * Where to redirect users after login.
 *
 * @var string
 */
protected $redirectTo = '/home';

/**
 * Create a new controller instance.
 *
 * @return void
 */
public function __construct()
{
    $this->middleware('guest')->except('logout');
}

public function username()
{
    return 'username';
}

protected function credentials(Request $request)
{
    $credentials = $request->only($this->username(), 'password');

    $credentials['status'] = 1;

    return $credentials;
}

}
`

Strange, this should work with your given controller code.
Is the HTML input form of your username named username?

Hi @stevebauman ,
YES, my HTML input of username is named as username. it was working fine before. suddenly today morning i got this error. is there another way to debug.

To debug, simply dump and die throughout the entire authentication request to see where the issue might be coming from.
For example, edit the vendor/adldap2/adldap2-laravel/src/Auth/Resolver.php file at line 46, and add a dd($credentials) to see what credentials are being passed to Adldap2.

Hi  @stevebauman,
its working in my test environment. but it's giving error in my production environment.

Okay, but you will still need to debug this yourself, as I have no idea of the differences in your environment.
Perform the actions I've mentioned above and see if your username and password is correctly being passed into Adldap2.

Hi @stevebauman ,
i have tried the same way which you have told by dumping the $credentials array.it's repeating the same error.


docs: update README to reflect the new API

Fixes: #50

Also, nit: it's rather docs: than chore: :)

@alexander-fenster Previously I updated the samples manually, but I didn't run npm run generate-scaffolding which is why the README wasn't updated.
I just ran npm run generate-scaffolding and it updated some of the other files.


demo gitops

add EKS Cluster

Ran Plan for project: vntechies-gitops dir: terraform/ap-southeast-1 workspace: default
Show Output
data.aws_subnets.eks_vpc_subnets: Reading...
module.eks.data.aws_caller_identity.current: Read complete after 1s [id=010352592457]
data.aws_subnets.eks_vpc_subnets: Read complete after 0s [id=ap-southeast-1]
data.aws_eks_cluster_auth.eks: Reading...
data.aws_eks_cluster_auth.eks: Read complete after 0s [id=thodung-vntechies-eks-demo-eks]

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+ create
 <= read (data resources)

Terraform will perform the following actions:

  # data.aws_eks_cluster.eks will be read during apply
  # (depends on a resource or a module with changes pending)
 <= data "aws_eks_cluster" "eks" {
      + arn                       = (known after apply)
      + certificate_authority     = (known after apply)
      + cluster_id                = (known after apply)
      + created_at                = (known after apply)
      + enabled_cluster_log_types = (known after apply)
      + endpoint                  = (known after apply)
      + id                        = (known after apply)
      + identity                  = (known after apply)
      + kubernetes_network_config = (known after apply)
      + name                      = "thodung-vntechies-eks-demo-eks"
      + outpost_config            = (known after apply)
      + platform_version          = (known after apply)
      + role_arn                  = (known after apply)
      + status                    = (known after apply)
      + tags                      = (known after apply)
      + version                   = (known after apply)
      + vpc_config                = (known after apply)
    }

  # module.eks.data.aws_eks_addon_version.this["aws-ebs-csi-driver"] will be read during apply
  # (depends on a resource or a module with changes pending)
 <= data "aws_eks_addon_version" "this" {
      + addon_name         = "aws-ebs-csi-driver"
      + id                 = (known after apply)
      + kubernetes_version = "1.25"
      + version            = (known after apply)
    }

  # module.eks.data.aws_eks_addon_version.this["cni"] will be read during apply
  # (depends on a resource or a module with changes pending)
 <= data "aws_eks_addon_version" "this" {
      + addon_name         = "vpc-cni"
      + id                 = (known after apply)
      + kubernetes_version = "1.25"
      + version            = (known after apply)
    }

  # module.eks.data.tls_certificate.this will be read during apply
  # (config refers to values not yet known)
 <= data "tls_certificate" "this" {
      + certificates = (known after apply)
      + id           = (known after apply)
      + url          = (known after apply)
    }

  # module.eks.aws_eks_addon.this["aws-ebs-csi-driver"] will be created
+ resource "aws_eks_addon" "this" {
      + addon_name               = "aws-ebs-csi-driver"
      + addon_version            = (known after apply)
      + arn                      = (known after apply)
      + cluster_name             = "thodung-vntechies-eks-demo-eks"
      + configuration_values     = (known after apply)
      + created_at               = (known after apply)
      + id                       = (known after apply)
      + modified_at              = (known after apply)
      + resolve_conflicts        = "OVERWRITE"
      + service_account_role_arn = (known after apply)
      + tags_all                 = {
          + "component"   = "thodung"
          + "env"         = "vntechies"
          + "github_repo" = "github.com/vntechies/013-demo-gitops"
          + "project"     = "013-demo-gitops"
        }
    }

  # module.eks.aws_eks_addon.this["cni"] will be created
+ resource "aws_eks_addon" "this" {
      + addon_name               = "vpc-cni"
      + addon_version            = (known after apply)
      + arn                      = (known after apply)
      + cluster_name             = "thodung-vntechies-eks-demo-eks"
      + configuration_values     = (known after apply)
      + created_at               = (known after apply)
      + id                       = (known after apply)
      + modified_at              = (known after apply)
      + resolve_conflicts        = "OVERWRITE"
      + service_account_role_arn = (known after apply)
      + tags_all                 = {
          + "component"   = "thodung"
          + "env"         = "vntechies"
          + "github_repo" = "github.com/vntechies/013-demo-gitops"
          + "project"     = "013-demo-gitops"
        }
    }

  # module.eks.aws_eks_cluster.eks will be created
+ resource "aws_eks_cluster" "eks" {
      + arn                   = (known after apply)
      + certificate_authority = (known after apply)
      + cluster_id            = (known after apply)
      + created_at            = (known after apply)
      + endpoint              = (known after apply)
      + id                    = (known after apply)
      + identity              = (known after apply)
      + name                  = "thodung-vntechies-eks-demo-eks"
      + platform_version      = (known after apply)
      + role_arn              = (known after apply)
      + status                = (known after apply)
      + tags_all              = {
          + "component"   = "thodung"
          + "env"         = "vntechies"
          + "github_repo" = "github.com/vntechies/013-demo-gitops"
          + "project"     = "013-demo-gitops"
        }
      + version               = "1.25"

      + vpc_config {
          + cluster_security_group_id = (known after apply)
          + endpoint_private_access   = false
          + endpoint_public_access    = true
          + public_access_cidrs       = (known after apply)
          + subnet_ids                = [
              + "subnet-01e3f6f9b10806e66",
              + "subnet-04b56904e52bb2431",
              + "subnet-079fc1ee9fbb1f5fc",
            ]
          + vpc_id                    = (known after apply)
        }
    }

  # module.eks.aws_eks_node_group.node["workers-1-23"] will be created
+ resource "aws_eks_node_group" "node" {
      + ami_type               = (known after apply)
      + arn                    = (known after apply)
      + capacity_type          = "SPOT"
      + cluster_name           = "thodung-vntechies-eks-demo-eks"
      + disk_size              = (known after apply)
      + id                     = (known after apply)
      + instance_types         = [
          + "t3a.medium",
        ]
      + node_group_name        = "workers-1-23"
      + node_group_name_prefix = (known after apply)
      + node_role_arn          = (known after apply)
      + release_version        = (known after apply)
      + resources              = (known after apply)
      + status                 = (known after apply)
      + subnet_ids             = [
          + "subnet-01e3f6f9b10806e66",
          + "subnet-04b56904e52bb2431",
          + "subnet-079fc1ee9fbb1f5fc",
        ]
      + tags_all               = {
          + "component"   = "thodung"
          + "env"         = "vntechies"
          + "github_repo" = "github.com/vntechies/013-demo-gitops"
          + "project"     = "013-demo-gitops"
        }
      + version                = "1.25"

      + scaling_config {
          + desired_size = 3
          + max_size     = 5
          + min_size     = 3
        }

      + update_config {
          + max_unavailable_percentage = 40
        }
    }

  # module.eks.aws_iam_openid_connect_provider.oidc_provider[0] will be created
+ resource "aws_iam_openid_connect_provider" "oidc_provider" {
      + arn             = (known after apply)
      + client_id_list  = [
          + "sts.amazonaws.com",
        ]
      + id              = (known after apply)
      + tags_all        = {
          + "component"   = "thodung"
          + "env"         = "vntechies"
          + "github_repo" = "github.com/vntechies/013-demo-gitops"
          + "project"     = "013-demo-gitops"
        }
      + thumbprint_list = (known after apply)
      + url             = (known after apply)
    }

  # module.eks.aws_iam_policy.ebs_csi["aws-ebs-csi-driver"] will be created
+ resource "aws_iam_policy" "ebs_csi" {
      + arn         = (known after apply)
      + description = "Custom Manged Policy for IRSA for the Kubernetes service account ebscsi-controller-sa."
      + id          = (known after apply)
      + name        = "thodung-vntechies-demo-eks-ebs-csi"
      + name_prefix = (known after apply)
      + path        = "/"
      + policy      = jsonencode(
            {
              + Statement = [
                  + {
                      + Action   = [
                          + "ec2:CreateSnapshot",
                          + "ec2:AttachVolume",
                          + "ec2:DetachVolume",
                          + "ec2:ModifyVolume",
                          + "ec2:DescribeAvailabilityZones",
                          + "ec2:DescribeInstances",
                          + "ec2:DescribeSnapshots",
                          + "ec2:DescribeTags",
                          + "ec2:DescribeVolumes",
                          + "ec2:DescribeVolumesModifications",
                        ]
                      + Effect   = "Allow"
                      + Resource = "*"
                    },
                  + {
                      + Action    = [
                          + "ec2:CreateTags",
                        ]
                      + Condition = {
                          + StringEquals = {
                              + "ec2:CreateAction" = [
                                  + "CreateVolume",
                                  + "CreateSnapshot",
                                ]
                            }
                        }
                      + Effect    = "Allow"
                      + Resource  = [
                          + "arn:aws:ec2:*:*:volume/*",
                          + "arn:aws:ec2:*:*:snapshot/*",
                        ]
                    },
                  + {
                      + Action   = [
                          + "ec2:DeleteTags",
                        ]
                      + Effect   = "Allow"
                      + Resource = [
                          + "arn:aws:ec2:*:*:volume/*",
                          + "arn:aws:ec2:*:*:snapshot/*",
                        ]
                    },
                  + {
                      + Action    = [
                          + "ec2:CreateVolume",
                        ]
                      + Condition = {
                          + StringLike = {
                              + "aws:RequestTag/ebs.csi.aws.com/cluster" = "true"
                            }
                        }
                      + Effect    = "Allow"
                      + Resource  = "*"
                    },
                  + {
                      + Action    = [
                          + "ec2:CreateVolume",
                        ]
                      + Condition = {
                          + StringLike = {
                              + "aws:RequestTag/CSIVolumeName" = "*"
                            }
                        }
                      + Effect    = "Allow"
                      + Resource  = "*"
                    },
                  + {
                      + Action    = [
                          + "ec2:DeleteVolume",
                        ]
                      + Condition = {
                          + StringLike = {
                              + "ec2:ResourceTag/ebs.csi.aws.com/cluster" = "true"
                            }
                        }
                      + Effect    = "Allow"
                      + Resource  = "*"
                    },
                  + {
                      + Action    = [
                          + "ec2:DeleteVolume",
                        ]
                      + Condition = {
                          + StringLike = {
                              + "ec2:ResourceTag/CSIVolumeName" = "*"
                            }
                        }
                      + Effect    = "Allow"
                      + Resource  = "*"
                    },
                  + {
                      + Action    = [
                          + "ec2:DeleteVolume",
                        ]
                      + Condition = {
                          + StringLike = {
                              + "ec2:ResourceTag/kubernetes.io/created-for/pvc/name" = "*"
                            }
                        }
                      + Effect    = "Allow"
                      + Resource  = "*"
                    },
                  + {
                      + Action    = [
                          + "ec2:DeleteSnapshot",
                        ]
                      + Condition = {
                          + StringLike = {
                              + "ec2:ResourceTag/CSIVolumeSnapshotName" = "*"
                            }
                        }
                      + Effect    = "Allow"
                      + Resource  = "*"
                    },
                  + {
                      + Action    = [
                          + "ec2:DeleteSnapshot",
                        ]
                      + Condition = {
                          + StringLike = {
                              + "ec2:ResourceTag/ebs.csi.aws.com/cluster" = "true"
                            }
                        }
                      + Effect    = "Allow"
                      + Resource  = "*"
                    },
                ]
              + Version   = "2012-10-17"
            }
        )
      + policy_id   = (known after apply)
      + tags_all    = {
          + "component"   = "thodung"
          + "env"         = "vntechies"
          + "github_repo" = "github.com/vntechies/013-demo-gitops"
          + "project"     = "013-demo-gitops"
        }
    }

  # module.eks.aws_iam_role.cluster will be created
+ resource "aws_iam_role" "cluster" {
      + arn                   = (known after apply)
      + assume_role_policy    = jsonencode(
            {
              + Statement = [
                  + {
                      + Action    = "sts:AssumeRole"
                      + Effect    = "Allow"
                      + Principal = {
                          + Service = "eks.amazonaws.com"
                        }
                    },
                ]
              + Version   = "2012-10-17"
            }
        )
      + create_date           = (known after apply)
      + force_detach_policies = false
      + id                    = (known after apply)
      + managed_policy_arns   = (known after apply)
      + max_session_duration  = 3600
      + name                  = "eks-cluster-thodung-vntechies-demo-eks"
      + name_prefix           = (known after apply)
      + path                  = "/"
      + tags_all              = {
          + "component"   = "thodung"
          + "env"         = "vntechies"
          + "github_repo" = "github.com/vntechies/013-demo-gitops"
          + "project"     = "013-demo-gitops"
        }
      + unique_id             = (known after apply)
    }

  # module.eks.aws_iam_role.irsa["aws-ebs-csi-driver"] will be created
+ resource "aws_iam_role" "irsa" {
      + arn                   = (known after apply)
      + assume_role_policy    = (known after apply)
      + create_date           = (known after apply)
      + description           = "AWS IAM Role for the Kubernetes service account ebscsi-controller-sa."
      + force_detach_policies = false
      + id                    = (known after apply)
      + managed_policy_arns   = (known after apply)
      + max_session_duration  = 3600
      + name                  = "aws-ebs-csi-driver"
      + name_prefix           = (known after apply)
      + path                  = "/"
      + tags_all              = {
          + "component"   = "thodung"
          + "env"         = "vntechies"
          + "github_repo" = "github.com/vntechies/013-demo-gitops"
          + "project"     = "013-demo-gitops"
        }
      + unique_id             = (known after apply)
    }

  # module.eks.aws_iam_role.node will be created
+ resource "aws_iam_role" "node" {
      + arn                   = (known after apply)
      + assume_role_policy    = jsonencode(
            {
              + Statement = [
                  + {
                      + Action    = "sts:AssumeRole"
                      + Effect    = "Allow"
                      + Principal = {
                          + Service = "ec2.amazonaws.com"
                        }
                    },
                ]
              + Version   = "2012-10-17"
            }
        )
      + create_date           = (known after apply)
      + force_detach_policies = false
      + id                    = (known after apply)
      + managed_policy_arns   = (known after apply)
      + max_session_duration  = 3600
      + name                  = "eks-node-group-thodung-vntechies-demo-eks"
      + name_prefix           = (known after apply)
      + path                  = "/"
      + tags_all              = {
          + "component"   = "thodung"
          + "env"         = "vntechies"
          + "github_repo" = "github.com/vntechies/013-demo-gitops"
          + "project"     = "013-demo-gitops"
        }
      + unique_id             = (known after apply)
    }

  # module.eks.aws_iam_role_policy_attachment.AmazonEC2ContainerRegistryReadOnly will be created
+ resource "aws_iam_role_policy_attachment" "AmazonEC2ContainerRegistryReadOnly" {
      + id         = (known after apply)
      + policy_arn = "arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
      + role       = "eks-node-group-thodung-vntechies-demo-eks"
    }

  # module.eks.aws_iam_role_policy_attachment.AmazonEKSClusterPolicy will be created
+ resource "aws_iam_role_policy_attachment" "AmazonEKSClusterPolicy" {
      + id         = (known after apply)
      + policy_arn = "arn:aws:iam::aws:policy/AmazonEKSClusterPolicy"
      + role       = "eks-cluster-thodung-vntechies-demo-eks"
    }

  # module.eks.aws_iam_role_policy_attachment.AmazonEKSVPCResourceController will be created
+ resource "aws_iam_role_policy_attachment" "AmazonEKSVPCResourceController" {
      + id         = (known after apply)
      + policy_arn = "arn:aws:iam::aws:policy/AmazonEKSVPCResourceController"
      + role       = "eks-cluster-thodung-vntechies-demo-eks"
    }

  # module.eks.aws_iam_role_policy_attachment.AmazonEKSWorkerNodePolicy will be created
+ resource "aws_iam_role_policy_attachment" "AmazonEKSWorkerNodePolicy" {
      + id         = (known after apply)
      + policy_arn = "arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy"
      + role       = "eks-node-group-thodung-vntechies-demo-eks"
    }

  # module.eks.aws_iam_role_policy_attachment.AmazonEKS_CNI_Policy will be created
+ resource "aws_iam_role_policy_attachment" "AmazonEKS_CNI_Policy" {
      + id         = (known after apply)
      + policy_arn = "arn:aws:iam::aws:policy/AmazonEKS_CNI_Policy"
      + role       = "eks-node-group-thodung-vntechies-demo-eks"
    }

  # module.eks.aws_iam_role_policy_attachment.AmazonSSMManagedInstanceCore will be created
+ resource "aws_iam_role_policy_attachment" "AmazonSSMManagedInstanceCore" {
      + id         = (known after apply)
      + policy_arn = "arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore"
      + role       = "eks-node-group-thodung-vntechies-demo-eks"
    }

  # module.eks.aws_iam_role_policy_attachment.irsa_ebs_csi_policy["aws-ebs-csi-driver"] will be created
+ resource "aws_iam_role_policy_attachment" "irsa_ebs_csi_policy" {
      + id         = (known after apply)
      + policy_arn = (known after apply)
      + role       = "aws-ebs-csi-driver"
    }

  # module.eks.kubernetes_config_map_v1_data.aws_auth[0] will be created
+ resource "kubernetes_config_map_v1_data" "aws_auth" {
      + data          = (known after apply)
      + field_manager = "Terraform"
      + force         = true
      + id            = (known after apply)

      + metadata {
          + name      = "aws-auth"
          + namespace = "kube-system"
        }
    }

Plan: 17 to add, 0 to change, 0 to destroy.

:arrow_forward: To apply this plan, comment:

atlantis apply -p vntechies-gitops

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -p vntechies-gitops

Plan: 17 to add, 0 to change, 0 to destroy.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

atlantis apply

Ran Apply for project: vntechies-gitops dir: terraform/ap-southeast-1 workspace: default
Apply Failed: Pull request must be approved by at least one person other than the author before running apply.

atlantis apply

Ran Apply for project: vntechies-gitops dir: terraform/ap-southeast-1 workspace: default
Apply Error
Show Output
running "/home/atlantis/.atlantis/bin/terraform1.5.3 apply -input=false \"/home/atlantis/.atlantis/repos/vntechies/013-demo-gitops/9/default/terraform/ap-southeast-1/vntechies-gitops-default.tfplan\"" in "/home/atlantis/.atlantis/repos/vntechies/013-demo-gitops/9/default/terraform/ap-southeast-1": exit status 1
module.eks.aws_iam_role.node: Creating...
module.eks.aws_iam_policy.ebs_csi["aws-ebs-csi-driver"]: Creating...
module.eks.aws_iam_role.cluster: Creating...
module.eks.aws_iam_policy.ebs_csi["aws-ebs-csi-driver"]: Creation complete after 1s [id=arn:aws:iam::010352592457:policy/thodung-vntechies-demo-eks-ebs-csi]
module.eks.aws_iam_role.node: Creation complete after 1s [id=eks-node-group-thodung-vntechies-demo-eks]
module.eks.aws_iam_role_policy_attachment.AmazonEC2ContainerRegistryReadOnly: Creating...
module.eks.aws_iam_role_policy_attachment.AmazonSSMManagedInstanceCore: Creating...
module.eks.aws_iam_role_policy_attachment.AmazonEKSWorkerNodePolicy: Creating...
module.eks.aws_iam_role_policy_attachment.AmazonEKS_CNI_Policy: Creating...
module.eks.aws_iam_role.cluster: Creation complete after 1s [id=eks-cluster-thodung-vntechies-demo-eks]
module.eks.aws_iam_role_policy_attachment.AmazonEKSClusterPolicy: Creating...
module.eks.aws_iam_role_policy_attachment.AmazonEKSVPCResourceController: Creating...
module.eks.aws_iam_role_policy_attachment.AmazonEKSWorkerNodePolicy: Creation complete after 1s [id=eks-node-group-thodung-vntechies-demo-eks-20230715074443753500000001]
module.eks.aws_iam_role_policy_attachment.AmazonSSMManagedInstanceCore: Creation complete after 1s [id=eks-node-group-thodung-vntechies-demo-eks-20230715074443757500000002]
module.eks.aws_iam_role_policy_attachment.AmazonEC2ContainerRegistryReadOnly: Creation complete after 1s [id=eks-node-group-thodung-vntechies-demo-eks-20230715074443760100000003]
module.eks.aws_iam_role_policy_attachment.AmazonEKSClusterPolicy: Creation complete after 1s [id=eks-cluster-thodung-vntechies-demo-eks-20230715074444022200000004]
module.eks.aws_iam_role_policy_attachment.AmazonEKS_CNI_Policy: Creation complete after 1s [id=eks-node-group-thodung-vntechies-demo-eks-20230715074444027700000005]
module.eks.aws_iam_role_policy_attachment.AmazonEKSVPCResourceController: Creation complete after 1s [id=eks-cluster-thodung-vntechies-demo-eks-20230715074444039100000006]
module.eks.aws_eks_cluster.eks: Creating...
module.eks.aws_eks_cluster.eks: Still creating... [10s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [20s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [30s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [40s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [50s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [1m0s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [1m10s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [1m20s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [1m30s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [1m40s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [1m50s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [2m0s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [2m10s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [2m20s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [2m30s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [2m40s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [2m50s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [3m0s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [3m10s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [3m20s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [3m30s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [3m40s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [3m50s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [4m0s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [4m10s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [4m20s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [4m30s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [4m40s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [4m50s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [5m0s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [5m10s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [5m20s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [5m30s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [5m40s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [5m50s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [6m0s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [6m10s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [6m20s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [6m30s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [6m40s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [6m50s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [7m0s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [7m10s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [7m20s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [7m30s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [7m40s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [7m50s elapsed]
module.eks.aws_eks_cluster.eks: Still creating... [8m0s elapsed]
module.eks.aws_eks_cluster.eks: Creation complete after 8m1s [id=thodung-vntechies-eks-demo-eks]
module.eks.data.aws_eks_addon_version.this["cni"]: Reading...
data.aws_eks_cluster.eks: Reading...
module.eks.data.aws_eks_addon_version.this["aws-ebs-csi-driver"]: Reading...
module.eks.data.tls_certificate.this: Reading...
module.eks.data.tls_certificate.this: Read complete after 0s [id=5f0630e8a1c4ee9bd3e7e715837e311bdbd1cd3d]
module.eks.aws_iam_openid_connect_provider.oidc_provider[0]: Creating...
data.aws_eks_cluster.eks: Read complete after 0s [id=thodung-vntechies-eks-demo-eks]
module.eks.data.aws_eks_addon_version.this["cni"]: Read complete after 0s [id=vpc-cni]
module.eks.kubernetes_config_map_v1_data.aws_auth[0]: Creating...
module.eks.aws_eks_node_group.node["workers-1-23"]: Creating...
module.eks.data.aws_eks_addon_version.this["aws-ebs-csi-driver"]: Read complete after 0s [id=aws-ebs-csi-driver]
module.eks.aws_iam_openid_connect_provider.oidc_provider[0]: Creation complete after 1s [id=arn:aws:iam::010352592457:oidc-provider/oidc.eks.ap-southeast-1.amazonaws.com/id/1470FBE09E07236EE4CF9E9295AE3126]
module.eks.aws_iam_role.irsa["aws-ebs-csi-driver"]: Creating...
module.eks.aws_iam_role.irsa["aws-ebs-csi-driver"]: Creation complete after 1s [id=aws-ebs-csi-driver]
module.eks.aws_iam_role_policy_attachment.irsa_ebs_csi_policy["aws-ebs-csi-driver"]: Creating...
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Creating...
module.eks.aws_eks_addon.this["cni"]: Creating...
module.eks.aws_iam_role_policy_attachment.irsa_ebs_csi_policy["aws-ebs-csi-driver"]: Creation complete after 1s [id=aws-ebs-csi-driver-2023071507524734500000000a]
module.eks.aws_eks_addon.this["cni"]: Creation complete after 8s [id=thodung-vntechies-eks-demo-eks:vpc-cni]
module.eks.aws_eks_node_group.node["workers-1-23"]: Still creating... [10s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [10s elapsed]
module.eks.aws_eks_node_group.node["workers-1-23"]: Still creating... [20s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [20s elapsed]
module.eks.aws_eks_node_group.node["workers-1-23"]: Still creating... [30s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [30s elapsed]
module.eks.aws_eks_node_group.node["workers-1-23"]: Still creating... [40s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [40s elapsed]
module.eks.aws_eks_node_group.node["workers-1-23"]: Still creating... [50s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [50s elapsed]
module.eks.aws_eks_node_group.node["workers-1-23"]: Still creating... [1m0s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [1m0s elapsed]
module.eks.aws_eks_node_group.node["workers-1-23"]: Still creating... [1m10s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [1m10s elapsed]
module.eks.aws_eks_node_group.node["workers-1-23"]: Still creating... [1m20s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [1m20s elapsed]
module.eks.aws_eks_node_group.node["workers-1-23"]: Still creating... [1m30s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [1m30s elapsed]
module.eks.aws_eks_node_group.node["workers-1-23"]: Still creating... [1m40s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [1m40s elapsed]
module.eks.aws_eks_node_group.node["workers-1-23"]: Creation complete after 1m48s [id=thodung-vntechies-eks-demo-eks:workers-1-23]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [1m50s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [2m0s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [2m10s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [2m20s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [2m30s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [2m40s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [2m50s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [3m0s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [3m10s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [3m20s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [3m30s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [3m40s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [3m50s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [4m0s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [4m10s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [4m20s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [4m30s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [4m40s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [4m50s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [5m0s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [5m10s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [5m20s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [5m30s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [5m40s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [5m50s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [6m0s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [6m10s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [6m20s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [6m30s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [6m40s elapsed]
╷
│ Error: The configmap "aws-auth" does not exist
│
│   with module.eks.kubernetes_config_map_v1_data.aws_auth[0],
│   on .terraform/modules/eks/main.tf line 76, in resource "kubernetes_config_map_v1_data" "aws_auth":
│   76: resource "kubernetes_config_map_v1_data" "aws_auth" {
│
╵
╷
│ Error: unexpected EKS Add-On (thodung-vntechies-eks-demo-eks:aws-ebs-csi-driver) state returned during creation: unexpected state 'UPDATING', wanted target 'ACTIVE'. last error: %!s(<nil>)
│ [WARNING] Running terraform apply again will remove the kubernetes add-on and attempt to create it again effectively purging previous add-on configuration
│
│   with module.eks.aws_eks_addon.this["aws-ebs-csi-driver"],
│   on .terraform/modules/eks/main.tf line 103, in resource "aws_eks_addon" "this":
│  103: resource "aws_eks_addon" "this" {
│
╵

Ran Plan for project: vntechies-gitops dir: terraform/ap-southeast-1 workspace: default
Show Output
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+ create
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # module.eks.aws_eks_addon.this["aws-ebs-csi-driver"] is tainted, so must be replaced
-/+ resource "aws_eks_addon" "this" {
      ~ arn                      = "arn:aws:eks:ap-southeast-1:010352592457:addon/thodung-vntechies-eks-demo-eks/aws-ebs-csi-driver/9ec4ac44-da83-8062-82fc-621f024527bd" -> (known after apply)
      + configuration_values     = (known after apply)
      ~ created_at               = "2023-07-15T07:52:47Z" -> (known after apply)
      ~ id                       = "thodung-vntechies-eks-demo-eks:aws-ebs-csi-driver" -> (known after apply)
      ~ modified_at              = "2023-07-15T07:59:43Z" -> (known after apply)
      - tags                     = {} -> null
        # (6 unchanged attributes hidden)
    }

  # module.eks.kubernetes_config_map.aws_auth[0] will be created
+ resource "kubernetes_config_map" "aws_auth" {
      + data = {
          + "mapRoles" = <<-EOT
                - groups:
                  - system:bootstrappers
                  - system:nodes
                  rolearn: arn:aws:iam::010352592457:role/eks-node-group-thodung-vntechies-demo-eks
                  username: system:node:{{EC2PrivateDNSName}}
            EOT
        }
      + id   = (known after apply)

      + metadata {
          + generation       = (known after apply)
          + name             = "aws-auth"
          + namespace        = "kube-system"
          + resource_version = (known after apply)
          + uid              = (known after apply)
        }
    }

Plan: 2 to add, 0 to change, 1 to destroy.

:arrow_forward: To apply this plan, comment:

atlantis apply -p vntechies-gitops

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -p vntechies-gitops

Plan: 2 to add, 0 to change, 1 to destroy.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

atlantis apply

Ran Apply for project: vntechies-gitops dir: terraform/ap-southeast-1 workspace: default
Apply Error
Show Output
running "/home/atlantis/.atlantis/bin/terraform1.5.3 apply -input=false \"/home/atlantis/.atlantis/repos/vntechies/013-demo-gitops/9/default/terraform/ap-southeast-1/vntechies-gitops-default.tfplan\"" in "/home/atlantis/.atlantis/repos/vntechies/013-demo-gitops/9/default/terraform/ap-southeast-1": exit status 1
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Destroying... [id=thodung-vntechies-eks-demo-eks:aws-ebs-csi-driver]
module.eks.kubernetes_config_map.aws_auth[0]: Creating...
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Destruction complete after 7s
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Creating...
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [10s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [20s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [30s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [40s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Creation complete after 45s [id=thodung-vntechies-eks-demo-eks:aws-ebs-csi-driver]
╷
│ Error: configmaps "aws-auth" already exists
│
│   with module.eks.kubernetes_config_map.aws_auth[0],
│   on .terraform/modules/eks/main.tf line 51, in resource "kubernetes_config_map" "aws_auth":
│   51: resource "kubernetes_config_map" "aws_auth" {
│
╵

Ran Plan for project: vntechies-gitops dir: terraform/ap-southeast-1 workspace: default
Show Output
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+ create

Terraform will perform the following actions:

  # module.eks.kubernetes_config_map_v1_data.aws_auth[0] will be created
+ resource "kubernetes_config_map_v1_data" "aws_auth" {
      + data          = {
          + "mapRoles" = <<-EOT
                - groups:
                  - system:bootstrappers
                  - system:nodes
                  rolearn: arn:aws:iam::010352592457:role/eks-node-group-thodung-vntechies-demo-eks
                  username: system:node:{{EC2PrivateDNSName}}
            EOT
        }
      + field_manager = "Terraform"
      + force         = true
      + id            = (known after apply)

      + metadata {
          + name      = "aws-auth"
          + namespace = "kube-system"
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

:arrow_forward: To apply this plan, comment:

atlantis apply -p vntechies-gitops

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -p vntechies-gitops

Plan: 1 to add, 0 to change, 0 to destroy.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

atlantis apply

Ran Apply for project: vntechies-gitops dir: terraform/ap-southeast-1 workspace: default
Show Output
module.eks.kubernetes_config_map_v1_data.aws_auth[0]: Creating...
module.eks.kubernetes_config_map_v1_data.aws_auth[0]: Creation complete after 1s [id=kube-system/aws-auth]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

Outputs:

subnet_ids = {
  "demo-vpc" = {
    "public_subnet1" = "subnet-04b56904e52bb2431"
    "public_subnet2" = "subnet-01e3f6f9b10806e66"
    "public_subnet3" = "subnet-079fc1ee9fbb1f5fc"
  }
}
vpc_ids = {
  "demo-vpc" = "vpc-07122a6282808ede1"
}

Locks and plans deleted for the projects and workspaces modified in this pull request:

dir: terraform/ap-southeast-1 workspace: default


Reduce Execution Context Save+Restore

Update to https://github.com/dotnet/corert/pull/5323
Resolves: https://github.com/dotnet/corert/pull/5323
/cc @jkotas

Thanks @benaadams ! This looks good. I have squashed this into https://github.com/dotnet/corert/pull/5323


Set platform and platformVersion in telemetry

What type of PR is this:
/kind feature
What does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes partially #6508
PR acceptance criteria:

[x] Unit test

[x] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:

/override OpenShift-Integration-tests/OpenShift-Integration-tests
Flaky e2e test
/override windows-integration-test/Windows-test
Flaky logs test

Rebased

/override Kubernetes-Integration-Tests/Kubernetes-Docs-Integration-Tests
Fixed by https://github.com/redhat-developer/odo/pull/6545

/override ci/prow/v4.11-integration-e2e