These are chat archives for spring-cloud/spring-cloud

13th
Mar 2017
Mark Bonnekessel
@marbon87
Mar 13 2017 08:10
Hi there, can you estimate the date by when the spring-cloud-config-server will be released with version 1.3.0?
Dave Syer
@dsyer
Mar 13 2017 09:43
We are waiting for Spring Cloud Stream
Hopefully today
No, sorry
Hopefully today for RC1
RC1 -> RELEASE is usually 1-2 weeks
Mark Bonnekessel
@marbon87
Mar 13 2017 09:44
Great! Thanks for the info
Dave Syer
@dsyer
Mar 13 2017 11:04
@joshiste that sample is stream turbine sample (not a regular "pull" turbine)
So, while it could register with Eureka, it doesn't need to in order to work
Dave Syer
@dsyer
Mar 13 2017 11:24
I can see that it doesn't. Perhaps you could raise an issue in spring-cloud-netflix?
Dave Syer
@dsyer
Mar 13 2017 11:33
You can work around it by setting eureka.instance.non-secure-port explicitly
Johannes Edmeier
@joshiste
Mar 13 2017 12:14
@dsyer thx
suren343
@suren343
Mar 13 2017 15:46
in JGitEnvironmentRepository.java (spring-cloud-config), we have a method refresh (for Get the working directory ready)..how often spring cloud config refreshes this working directory? Or each time , a merge happens it checks and refreshes? Also what may cause !isClean(git) to occur?
Dave Syer
@dsyer
Mar 13 2017 16:06
refresh() is called every time the repository is accessed (should be obvious from the source code)
isClean() should never be true unless some other process changes the working tree
(e.g. if you edit by hand, or if the OS deletes files)
It's just what you'd expect from git status on the command line

Form the javadocs:

true if no differences exist between the working-tree, the index, and the current HEAD, false if differences do exist

suren343
@suren343
Mar 13 2017 16:16
@dsyer Thanks..We have identified the local directory is getting stale..seeing cases where missing files, out of date when compared with actual repo..we do have changes to our actaul repo once in few days with new config being pushed and observing local directory getting corrupted..we are using spring cloud config 1.1.2 ..Any issues with this version or do we need to use basedir along with git uri ?
Dave Syer
@dsyer
Mar 13 2017 16:17
basedir is probably a good idea
The global TEMP dir is likely to be purged by the OS without you being able to control it.
In general it is better to be on the latest release though as well
So if I were you I'd upgrade as well.
suren343
@suren343
Mar 13 2017 16:21
@dsyer Thanks we will try..
Bill Bauernschmidt
@wbauern
Mar 13 2017 20:10
Where can I find what specific exceptions will be retried when using RestTemplate configured to use Ribbon retries (ie. spring.cloud.loadbalancer.retry=true)? I've been looking through the code but haven't had luck tracking it down.
suren343
@suren343
Mar 13 2017 20:57
@dsyer I have used basedir in one of the application folders, and able to see its replicating the git config changes, and even updates whenever we push some changes to git (but with little delay of 5-10mins) ...Thanks for the help..Have one more query...if we kill the application and restart, whether the basedir gets deleted and recreated again or its just one dir always appended?