-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/proc/<pid>/maps is incorrect #5090
Comments
/schedule |
/assign @mrsimonemms |
/assign |
@csweichel there is nothing to fix here besides upgrading the kernel.
From EKS (using kernel 4.13)
|
@kreditor0815 this issue only persists on GKS. If you self hosted you'll likely have a different kernel. |
When I start this Repo I got errors |
@murratore I just modified my proposed solution (see gitpod-samples/template-dotnet-core-cli-csharp#5) with this I don't receive the same error as you mentioned. Maybe this change solves your problem. |
Signed-off-by: Patrick Dwyer <[email protected]>
Signed-off-by: Patrick Dwyer <[email protected]>
Just tested the .NET 6 default template and it seems to work without the workaround! |
So just |
Doesn't seem that way, have a look at https://github.com/gitpod-io/template-dotnet-core-cli-csharp, it uses a task to install .NET as a workaround. EDIT: Oh my, I didn't see the comment by @woehrl01 that refers to the aforementioned workaround. I guess the kernel issue is still not fixed. Workaround seems good enough that it won't bother me going forward though! |
That link is the workaround?
…On Wed, 10 Nov 2021 at 19:44, Benjamin Bartels ***@***.***> wrote:
Doesn't seem that way, have a look at
https://github.com/gitpod-io/template-dotnet-core-cli-csharp, it uses a
task to install .NET as a workaround.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5090 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAZVJQMEFZKFXIHDDITC23ULLDQ5ANCNFSM5BVWUNZA>
.
|
Yeah, if you have a look at the |
Literally no idea what you're saying. There's an existing bug with a workaround which you linked to but your original comment says you've tried a template without the workaround so not sure what you're getting at |
I created a new Gitpod workspace with the predefined I think because you responded from email you didn't see the edit I made to the comment that should have cleared up the misunderstanding (At least was supposed to). Apologies for not being precise enough in my initial wording! |
Ha ha no worries. Thanks for explaining that as there was a high chance I
was missing something :)
…On Wed, 10 Nov 2021 at 20:30, Benjamin Bartels ***@***.***> wrote:
I created a new Gitpod workspace with the predefined
template-dotnet-core-cli-csharp template and the hello world project
built without issues. This was not the case just two weeks ago. I thought
this meant that the kernel issue was fixed as I didn't have to manually add
the workaround. It turns out I missed the comment by @woehrl01
<https://github.com/woehrl01> that modified the
template-dotnet-core-cli-csharp template to include the workaround.
I think because you responded from email you didn't see the edit I made to
the comment that should have cleared up the misunderstanding (At least was
supposed to). Apologies for not being precise enough in my initial wording!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5090 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAZVJTSFBOTVPAVIUSWERLULLI7FANCNFSM5BVWUNZA>
.
|
I was able to use https://github.com/gitpod-io/template-dotnet-core-cli-csharp as suggested and run the hello world, after switching to .net6 in the csproj. When I attempted to create an ASP.NET app using dotnet new, I was never able to get port mapping correct. The app ran in the commandline and exposed 2 local ports, and a popup asked if I wanted to make them public. I did so, but when I attempted to open browser, it would send to localhost:. Going to - returned a 502. Is there some other foo to control the port mapping? Let me know if I should open a separate issue for this - it's all related in my mind, but may be a separate issue or just me not understanding how the port mapping works. |
Hey folks, Have some great news. Gitpod has almost moved off GKE. We are currently running a canary deployment of new infrastructure and are at 40% load. Within the next couple days we will be 100% out of GKE. If your workspace opens in http://ws-prod-ws-us19.gitpod.io / http://ws-prod-ws-eu19.gitpod.io then you are on the new infrastructure which resolves this problem. |
Closing. We are now 100% out of GKE. So this is not an issue anymore. Also, apologies for the time it took to fix this issue. |
Should this be working worldwide now? I think I still have the problem in |
@nojaf please post the output of running |
Oh, one thing to confess, I am installed additional SDKs.
This might be related. |
It is. Please open a new issue and include the error you get |
I still have .NET issues on a fresh container, fresh empty repo, I just upgraded all default packages and installed .NET as per here, but get the following output: I am simply using building default template for
|
@yellowsink Can you open a new issue, please? |
Okay will do |
I also encountered issues and I created a new Issue here: #8901 |
Bug description
The
/proc/<pid>/maps
file is incorrect. It's unclear what causes this.When running a Docker container in Gitpod,
/proc/<pid>/maps
is correct.This is a possible cause of #5064
Possibly relevant issues:
Steps to reproduce
cat /proc/self/maps
contains paths that don't really exist or make sense in the workspace.
Expected behavior
It should show the proper maps.
Example repository
https://github.com/ghuntley/gitpod-dotnet-csharp-breakpoints
The text was updated successfully, but these errors were encountered: