microsoft / microsoft/azure-tools-for-java

Azure Function Debugging: no stopping at a debug breakpoint in IntelliJ

Open
#9,485 0 comments 0 reactions 1 assignee View on GitHub

@Flanker32 is already working on this.

Since Oct 9, 2024.

Module: Azure Functions Type: Bug
Dominant language
Java
Stars
262
Forks
185
Avg merge
2d 21h
Merged PRs (30d)
1

Description

Hi,

Recently, my colleagues and I have been having the problem that we can no longer debug Azure Functions locally in IntelliJ. The Function App starts, but there doesn't seem to be a connection to the debugger. For example, when an HttpTrigger is triggered, the function is executed, but it doesn't stop at any breakpoint.

In the IntelliJ logs there are some entries like this (although I was logged into Azure from within IntelliJ):

2024-09-25 08:28:25,777 [6307173] WARN - com.microsoft.alm.plugin.operations.BuildStatusLookupOperation - getServerContext: failed to get authenticated server context 2024-09-25 08:28:25,777 [6307173] WARN - com.microsoft.alm.plugin.operations.BuildStatusLookupOperation - doWork: failed with an exception javax.ws.rs.NotAuthorizedException: HTTP 401 Unauthorized at com.microsoft.alm.plugin.operations.Operation.getServerContext(Operation.java:215) at com.microsoft.alm.plugin.operations.BuildStatusLookupOperation.doWork(BuildStatusLookupOperation.java:149) at com.microsoft.alm.plugin.operations.OperationExecutor$1.run(OperationExecutor.java:56) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1583)

We use different IntelliJ and plugin versions, but with the same behavior.

Do you have a hint?

Best regards,

Heiko

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.