Skip to content

Conversation

@kamalesh0406
Copy link

patch by Kamalesh Palanisamy;

final List<Instance> instances = new CopyOnWriteArrayList<>();

public SimpleProgressLog(Node node)
public SimpleProgressLog(Node node, AccordConfig config)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should Node expose config? That way you don't need to pass all over?


import javax.annotation.Nullable;

import accord.utils.AccordConfig;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel we should have accord.config package, this is likely to expand over time


isScheduled = true;
node.scheduler().once(() -> commandStore.execute(PreLoadContext.empty(), ignore -> run()).begin(commandStore.agent()), 200L, TimeUnit.MILLISECONDS);
node.scheduler().once(() -> commandStore.execute(PreLoadContext.empty(), ignore -> run()).begin(commandStore.agent()), config.progress_log_scheduler_delay_in_ms, TimeUnit.MILLISECONDS);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we are trying to move away from _in_ms postfix... this may call out that we should likely move some of the config classes to accord?

Comment on lines +6 to +8
public AccordConfig(long progress_log_scheduler_delay_in_ms) {
this.progress_log_scheduler_delay_in_ms = progress_log_scheduler_delay_in_ms;
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this constructor isn't something we can maintain, as we add more and more configs this will become an issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants