{"task": {"agent_timeout": 3000, "task": "codegen__spotbugs__spotbugs-2694", "verifier_timeout": 3000, "instruction": "This is a code generation task. You are expected to write working code that solves the described problem.\n<issue>\n      Version: 4.7.3\n\nI found a false positive about the rule [NP_EQUALS_SHOULD_HANDLE_NULL_ARGUMENT](https://spotbugs.readthedocs.io/en/latest/bugDescriptions.html#np-equals-method-does-not-check-for-null-argument-np-equals-should-handle-null-argument).\n\nIn the example below, SpotBugs reports no warning. The `equals` method takes a parameter that is marked as `@javax.annotation.Nonnull` . So it obeys this rule correctly. \n\n```java\npublic class Test {\n  public boolean equals(@javax.annotation.Nonnull Object a) {\n    return a.hashCode() == this.hashCode();\n  }\n}\n```\n\nHowever, in the example below, SpotBugs reports a warning at line 3 if we use `@org.netbeans.api.annotations.common.NonNull` instead. Actually, `@javax.annotation.Nonnull` and `@org.netbeans.api.annotations.common.NonNull` are equivalent. So, this exmaple does not violate the rule NP_EQUALS_SHOULD_HANDLE_NULL_ARGUMENT and the warning is a false positive.\n\n```java\npublic class Test {\n  public boolean equals(@org.netbeans.api.annotations.common.NonNull Object a) { //report a warning, but it is an FP\n    return a.hashCode() == this.hashCode();\n  }\n}\n\n```\n\nI use the cmd `spotbugs -textui -low -xml -output= report.xml -auxclasspath org.eclipse.jdt.annotation-2.2.700.jar Test.class`\n\n</issue>\nFocus on implementing the required functionality correctly and efficiently. Treat this as a programming challenge.\nYou are not allowed to read git history.\n", "memory": "8192m", "runnable": false, "difficulty": "hard", "language": "", "cpus": "", "instruction_truncated": false, "category": "code-generation", "compose": false, "has_solution": true, "oracle": null, "docker_image": "", "taskset": "devopsgym", "tags": ["code-generation", "devops-bench"]}, "runs": []}