It can be used by the frontend team (that can also be yourself).

It can be used by third party applications and systems.

And it can also be used by yourself, to debug, check and test the same application.

## The `password` flow { #the-password-flow }

Now let's go back a bit and understand what is all that.

            boolean isAllowed = false;
            final List<String> allowedPaths = new ArrayList<>();
            for (final String prop : allowedPathProperties) {
                final String basePath = System.getProperty(prop);
                if (basePath != null) {
                    final String baseCanonicalPath = new File(basePath).getCanonicalPath();
                    allowedPaths.add(baseCanonicalPath);

        @Override
        public String getMailFromAddress() {
            return "******@****.***";
        }

        @Override
        public String getMailFromName() {
            return "Fess System";
        }

        @Override
        public String getMailReturnPath() {
            return "******@****.***";
        }
    }

        assertEquals(0xFFFFFFFFL, pdis.readUnsignedInt());
    }

    @Test
    public void testReadFiletime() throws IOException {
        // A non-null date
        long time = System.currentTimeMillis();
        BigInteger filetime = BigInteger.valueOf(time)
                .add(BigInteger.valueOf(SmbConstants.MILLISECONDS_BETWEEN_1970_AND_1601))
                .multiply(BigInteger.valueOf(10000L));

        ParserRequest parserRequest = mock(ParserRequest.class);
        Logger logger = mock(Logger.class);

        // Capture error messages for debugging
        doAnswer(invocation -> {
                    System.err.println("[ERROR] " + invocation.getArgument(0));
                    return null;
                })
                .when(logger)
                .error(anyString());

# Classes as Dependencies { #classes-as-dependencies }

Before diving deeper into the **Dependency Injection** system, let's upgrade the previous example.

## A `dict` from the previous example { #a-dict-from-the-previous-example }

In the previous example, we were returning a `dict` from our dependency ("dependable"):

{* ../../docs_src/dependencies/tutorial001_an_py310.py hl[9] *}

	}

	// As policy is not available for given bucket name, returns IsOwner i.e.
	// operation is allowed only for owner.
	return args.IsOwner
}

// NewPolicySys - creates new policy system.
func NewPolicySys() *PolicySys {
	return &PolicySys{}
}

func getSTSConditionValues(r *http.Request, lc string, cred auth.Credentials) map[string][]string {
	m := make(map[string][]string)

## Tips and Best Practices

To get realistic results, you should exercise care when running benchmarks. Here are a few tips:

### Do

* Ensure that the system executing your microbenchmarks has as little load as possible. Shutdown every process that can cause unnecessary
  runtime jitter. Watch the `Error` column in the benchmark results to see the run-to-run variance.

        Task task,
        Project fixtureProject,
        boolean enableFilter,
        BiConsumer<String, Integer> consumer
    ) {
        // Configure ports for the tests as system properties.
        // We only know these at execution time so we need to do it in doFirst
        task.doFirst(new Action<Task>() {
            @Override
            public void execute(Task theTask) {

        if command -v invoke-rc.d >/dev/null; then
            invoke-rc.d fess stop || true
        else
            /etc/init.d/fess stop || true
        fi

    # older suse linux distributions do not ship with systemd
    # but do not have an /etc/init.d/ directory
    # this tries to start the fess service on these
    # as well without failing this script
    elif [ -x /etc/rc.d/init.d/fess ] ; then