*/
    public int getCrawlDelay(final String userAgent) {
        final Directive directive = getMatchedDirective(userAgent);
        if (directive == null) {
            return 0;
        }
        return directive.getCrawlDelay();
    }

    /**
     * Returns the most specific directive matching the given user agent.
     * The method finds the longest matching user agent pattern in the directives,

# Test file for malformed robots.txt parsing
# This file contains various malformed directives that should be handled gracefully

# Case 1: Directives before any User-agent (should be ignored)
Disallow: /orphaned1/
Allow: /orphaned2/

# Case 2: Valid user-agent with various malformed directives
User-agent: GoodBot
Disallow: /admin/
InvalidDirective: some-value
unknown-field: test
Disallow /missing-colon

                            for (final Directive directive : currentDirectiveList) {
                                directive.addAllow(value);
                            }
                        }
                        continue;
                    }

                    // Try to parse as Crawl-delay directive
                    value = getValue(CRAWL_DELAY_RECORD, line);

        assertNotNull(robotsTxt);

        // Test that orphaned directives (before any User-agent) are ignored
        // These should not affect any bot
        assertTrue(robotsTxt.allows("/orphaned1/", "AnyBot"));
        assertTrue(robotsTxt.allows("/orphaned2/", "AnyBot"));

        // Test GoodBot - should parse valid directives and ignore invalid ones
        assertNotNull(robotsTxt.getDirective("goodbot"));

own source code, making it easier to move the code from one location to another.
</p>

<h3 id="directives">Directives</h3>

<p>
The assembler uses various directives to bind text and data to symbol names.
For example, here is a simple complete function definition. The <code>TEXT</code>
directive declares the symbol <code>runtime·profileloop</code> and the instructions
that follow form the body of the function.

Only the work module's `go.mod` is consulted for `godebug` directives.
Any directives in required dependency modules are ignored.
It is an error to list a `godebug` with an unrecognized setting.
(Toolchains older than Go 1.23 reject all `godebug` lines, since they do not
understand `godebug` at all.) When a workspace is in use, `godebug`
directives in `go.mod` files are ignored, and `go.work` will be consulted

        Directive directive = new Directive("MyBot");

        assertNotNull(directive);
        assertEquals("MyBot", directive.getUserAgent());
        assertEquals(0, directive.getCrawlDelay());
    }

    public void test_directiveCrawlDelay() {
        // Test Directive crawl delay
        Directive directive = new Directive("MyBot");

        directive.setCrawlDelay(10);

        }
    }

    /**
     * Processes robots meta tags in the HTML document.
     * Handles noindex, nofollow, and none directives.
     *
     * @param responseData the response data from crawling
     * @param resultData the result data to store processed information
     * @param document the parsed HTML document
     */

- Introduced the alpha `MutableSchedulingDirectivesForSuspendedJobs` feature gate (disabled by default), which allows mutating a Job's scheduling directives while the Job is suspended. 

pkg go/ast, func ParseDirective(token.Pos, string) (Directive, bool) #68021
pkg go/ast, method (*Directive) End() token.Pos #68021
pkg go/ast, method (*Directive) ParseArgs() ([]DirectiveArg, error) #68021
pkg go/ast, method (*Directive) Pos() token.Pos #68021
pkg go/ast, type BasicLit struct, ValueEnd token.Pos #76031
pkg go/ast, type Directive struct #68021
pkg go/ast, type Directive struct, Args string #68021