Skip to content
TheChatArchiveThe Chat Archive
xiaomi/mimo-v2.5-pro· unknownHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION [BUG] ELBv2 DescribeListenerAttributes and DescribeCapacityReservation…

  1. User

    ISSUE DESCRIPTION

    [BUG] ELBv2 DescribeListenerAttributes and DescribeCapacityReservation return UnsupportedOperation (breaks @pulumi/aws refresh)

    Service

    ELBv2 (Elastic Load Balancing v2)

    AWS API Action

    DescribeListenerAttributes and DescribeCapacityReservation

    Expected behavior

    • DescribeListenerAttributes returns the listener's attribute list (empty by default until attributes are set).
    • DescribeCapacityReservation returns the load balancer's capacity reservation status (empty/none when no capacity is reserved).

    Both are normal management-plane reads that the AWS SDKs issue during resource refresh.

    Actual behavior

    Both actions return:

    api error UnsupportedOperation: Action DescribeListenerAttributes is not supported.
    api error UnsupportedOperation: Action DescribeCapacityReservation is not supported.
    

    @pulumi/aws 6.66.0+ (and recent Terraform AWS provider versions) call these two actions when refreshing existing LoadBalancer / Listener resources. Because Floci returns UnsupportedOperation, the provider errors out on refresh. The only workaround today is pinning @pulumi/aws to a version that predates these calls (e.g. 6.30.0).

    ELBv2 is otherwise well supported in Floci — only these two read actions are missing from ElbV2QueryHandler's action switch.

    Reproduction

    # Assuming a load balancer + listener already exist (CreateLoadBalancer / CreateListener):
    aws --endpoint-url http://localhost:4566 elbv2 describe-listener-attributes \
      --listener-arn arn:aws:elasticloadbalancing:us-east-1:000000000000:listener/app/my-lb/abc/def
    # -> UnsupportedOperation: Action DescribeListenerAttributes is not supported.
    
    aws --endpoint-url http://localhost:4566 elbv2 describe-capacity-reservation \
      --load-balancer-arn arn:aws:elasticloadbalancing:us-east-1:000000000000:loadbalancer/app/my-lb/abc
    # -> UnsupportedOperation: Action DescribeCapacityReservation is not supported.
    

    Environment

    • Floci version / image tag: 1.5.18 (floci/floci:latest); also present on current main
    • AWS provider that triggers it: @pulumi/aws 6.66.0+ (works when pinned to 6.30.0)
    • How you're running Floci: Docker / Docker Compose

    A PR implementing DescribeListenerAttributes, ModifyListenerAttributes, and DescribeCapacityReservation (mirroring the existing load balancer / target group attribute handlers) will reference this issue.

    Interface

    Type: Function Name: describeListenerAttributes Path: src/main/java/io/github/hectorvent/floci/services/elbv2/ElbV2Service.java Input: region: String, arn: String Output: Map<String, String> Description: Returns a copy of the attributes map for the listener identified by the given ARN.

    Type: Function Name: modifyListenerAttributes Path: src/main/java/io/github/hectorvent/floci/services/elbv2/ElbV2Service.java Input: region: String, arn: String, newAttrs: Map<String, String> Output: void Description: Merges the provided key-value pairs into the listener's existing attributes.

    Type: Record Name: CapacityReservation Path: src/main/java/io/github/hectorvent/floci/services/elbv2/ElbV2Service.java Public API: CapacityReservation(Integer decreaseRequestsRemaining, Integer minimumCapacityUnits, Instant lastModifiedTime) Description: Stable representation of load-balancer capacity-reservation state. Floci returns null fields when no capacity is reserved.

    Type: Function Name: describeCapacityReservation Path: src/main/java/io/github/hectorvent/floci/services/elbv2/ElbV2Service.java Input: region: String, arn: String Output: CapacityReservation Description: Validates the load balancer and returns its capacity-reservation state.

    ADDITIONAL ADVICE

    Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use git checkout <file> to restore the file to its original state. You can also reset all changes in the repository using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to get the changes that need to be submitted.

    CHECKLIST

    Before submitting your solution, please go over the following checklist and make sure you've done everything:

    • If an error was reported in the issue description, I have successfully reproduced it.
    • If an error was reported in the issue description, I have confirmed that my fix resolves the error.
    • I have thought about edge cases and made sure my fix handles them as well.
    • I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.

    Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!

    (Current directory: /floci, current file: none) bash-$

  2. Assistant

    I'll start by exploring the repository structure to understand the codebase and locate the relevant files for ELBv2. First, let's check the current directory and see what's available.

  3. Assistant

    Let me explore the repository structure to understand the codebase and then look at the specific files mentioned in the issue.

  4. Assistant

    Let me first look at the main service file and the query handler to understand the current structure.

  5. Assistant

    Now let me look at the query handler to see how actions are dispatched:

  6. Assistant

    Now let me look at the Listener model to see if it has an attributes map:

  7. Assistant

    Now let me look at the LoadBalancer model to see if it has capacity reservation:

  8. Assistant

    Let me check the existing target group attribute handlers to understand the pattern:

  9. Assistant

    Let me look at the full handler code for target group attributes:

  10. Assistant

    Now I understand the codebase. Let me plan my changes:

    1. Add describeListenerAttributes and modifyListenerAttributes methods to ElbV2Service.java
    2. Add describeCapacityReservation method to ElbV2Service.java (with a capacity reservation state concept on the LoadBalancer)
    3. Add corresponding handler cases in ElbV2QueryHandler.java for DescribeListenerAttributes, ModifyListenerAttributes, and DescribeCapacityReservation

    Let me look at the existing tests to understand the test patterns:

  11. Assistant

    Let me look at the Listener creation in the service:

  12. Assistant

    Let me see the createListener method to understand how attributes are initialized.

  13. Assistant

    Now let me look at the AGENT.md file for conventions and also check how existing attribute handlers work for listeners:

  14. Assistant

    Let me check the existing tests to see if there are any tests related to listener attributes or capacity reservation:

  15. Assistant

    Let me also look at the full test file:

  16. Assistant

    Now I have a complete understanding of the codebase. Let me implement the changes:

    1. Add describeListenerAttributes, modifyListenerAttributes, and describeCapacityReservation methods to ElbV2Service.java
    2. Add DescribeListenerAttributes, ModifyListenerAttributes, and DescribeCapacityReservation handler cases in ElbV2QueryHandler.java

    Let me start implementing. First, I'll add the service methods:

  17. Assistant

    Let me look at the area around the listener certificates to find a good place to add the listener attributes methods:

  18. Assistant

    Let me look at the listener section and the listener certificates section to understand where to add the new methods:

  19. Assistant

    Now I have a clear picture. Let me implement the changes:

    1. Add describeListenerAttributes and modifyListenerAttributes to ElbV2Service.java
    2. Add describeCapacityReservation to ElbV2Service.java (with a simple capacity reservation model)
    3. Add corresponding handler methods in ElbV2QueryHandler.java

    Let me start with the service changes. I'll add the listener attributes methods after the listener certificates section:

  20. Assistant

    Let me use the edit command directly:

  21. Assistant

    Now let me add the new methods to ElbV2Service.java. I'll add them after the listener certificates section (line 636):

  22. Assistant

    Now let me add the handler cases in ElbV2QueryHandler.java. First, let me find where to add them:

  23. Assistant

    Let me add the new cases to the switch statement. I'll add DescribeListenerAttributes and ModifyListenerAttributes after ModifyListener, and DescribeCapacityReservation under Load Balancers:

  24. Assistant

    Now add DescribeCapacityReservation under Load Balancers:

  25. Assistant

    Now I need to add the handler methods. Let me find where the Load Balancer handlers end and the Target Group section begins:

  26. Assistant

    Let me add the handleDescribeCapacityReservation method before the Target Groups section.

  27. Assistant

    Now let me add the handler methods. I'll add handleDescribeCapacityReservation after handleSetIpAddressType (line 252) and before the Target Groups section.

  28. Assistant

    Now I need to add the handleDescribeListenerAttributes and handleModifyListenerAttributes methods. Let me find where the Listener handlers are:

  29. Assistant

    Let me look at the area after handleModifyListener:

  30. Assistant

    Now add the listener attributes handler methods after handleModifyListener and before the Rules section:

  31. Assistant

    I notice there's an extra } on line 491. Let me check and fix that:

  32. Assistant

    There's an extra closing brace on line 491. Let me remove it:

  33. Assistant

    Now let me verify the changes compile correctly. Let me run a quick build check:

  34. Assistant

    Let me set the HOME variable first:

  35. Assistant

    Great, compilation passed. Now let me run the existing tests:

  36. Assistant

    The output doesn't show test results. Let me check more:

  37. Assistant

    All 27 existing tests pass. Let me also run the Lambda target test and any other tests:

  38. Assistant

    All tests pass. Now let me write a quick test script to verify the new functionality works:

  39. Assistant

    Let me write a proper integration test as a temporary script (since we can't modify existing tests):

  40. Assistant

    Now let me copy the test file to the test directory and run it:

  41. Assistant

    All 9 new tests pass. Let me clean up the temporary test file since we shouldn't add tests to the repository:

  42. Assistant

    Now let me verify that all the original tests still pass:

  43. Assistant

    All 36 existing tests pass. Let me also run the compatibility test:

  44. Assistant

    The compatibility tests seem to be failing because they need a running server. Let me check if these were already failing before my changes:

  45. Assistant

    Good, the existing tests pass without my changes too. The compatibility tests likely need a running server. Let me restore my changes.

  46. Assistant

    Let me verify the final state of my changes:

  47. Assistant

    Let me view the full diff to review the changes:

  48. Assistant

    The diff looks clean. Let me run the full test suite one more time to ensure everything passes:

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.