Intent to backport OAK-6339

[Chetan Mehrotra]

I would like to backport OAK-6339 to 1.6 branch. This change would be
backported to both segment implementation as its impacting collection
of repo stats for large repo via oakRepoStats script

Chetan Mehrotra

Re: Test-only utility for dumping the repository?

[Robert Munteanu]

Hi Alex,

On Thu, 2017-08-31 at 16:50 +0200, Alex Deparvu wrote:
> Hi Robert,
> 
> Have you tried NodeStateUtils#toString?
> 


That looks like exactly what I was looking for, thanks!

Robert

> 
> 
> 
> 
> On Thu, Aug 31, 2017 at 4:37 PM, Robert Munteanu 
> wrote:
> 
> > Hi,
> > 
> > When I have a test issue that relies on inspecting the repository I
> > usually write a small method that prints the contents of the
> > repository.
> > 
> > Today, as I wrote that method for the third time, I was wondering
> > whether we should add it to test-only utility class.
> > 
> > The problem with that is that we don't have something like oak-
> > test-
> > support which contains only testing classes. Would that make sense,
> > and
> > also maybe start breaking out 'test-jar' dependencies between
> > modules?
> > 
> > Thanks,
> > 
> > Robert
> > 

Re: Test-only utility for dumping the repository?

[Alex Deparvu]

Hi Robert,

Have you tried NodeStateUtils#toString?

best,
alex




On Thu, Aug 31, 2017 at 4:37 PM, Robert Munteanu  wrote:

> Hi,
>
> When I have a test issue that relies on inspecting the repository I
> usually write a small method that prints the contents of the
> repository.
>
> Today, as I wrote that method for the third time, I was wondering
> whether we should add it to test-only utility class.
>
> The problem with that is that we don't have something like oak-test-
> support which contains only testing classes. Would that make sense, and
> also maybe start breaking out 'test-jar' dependencies between modules?
>
> Thanks,
>
> Robert
>

Test-only utility for dumping the repository?

[Robert Munteanu]

Hi,

When I have a test issue that relies on inspecting the repository I
usually write a small method that prints the contents of the
repository.

Today, as I wrote that method for the third time, I was wondering
whether we should add it to test-only utility class.

The problem with that is that we don't have something like oak-test-
support which contains only testing classes. Would that make sense, and
also maybe start breaking out 'test-jar' dependencies between modules?

Thanks,

Robert

Oak 1.6.5 release plan

[Davide Giannella]

Hello team,

I'm planning to cut Oak on Monday 4th September.

If there are any objections please let me know. Otherwise I will
re-schedule any non-resolved issue for the next iteration.

Thanks
Davide