{"action":"created","issue":{"url":"https://api.github.com/repos/nats-io/nats-streaming-server/issues/619","repository_url":"https://api.github.com/repos/nats-io/nats-streaming-server","labels_url":"https://api.github.com/repos/nats-io/nats-streaming-server/issues/619/labels{/name}","comments_url":"https://api.github.com/repos/nats-io/nats-streaming-server/issues/619/comments","events_url":"https://api.github.com/repos/nats-io/nats-streaming-server/issues/619/events","html_url":"https://github.com/nats-io/nats-streaming-server/issues/619","id":340625508,"node_id":"MDU6SXNzdWUzNDA2MjU1MDg=","number":619,"title":"Flush SQL cache on SIGTERM/application exit","user":{"login":"powerman","id":1354301,"node_id":"MDQ6VXNlcjEzNTQzMDE=","avatar_url":"https://avatars0.githubusercontent.com/u/1354301?v=4","gravatar_id":"","url":"https://api.github.com/users/powerman","html_url":"https://github.com/powerman","followers_url":"https://api.github.com/users/powerman/followers","following_url":"https://api.github.com/users/powerman/following{/other_user}","gists_url":"https://api.github.com/users/powerman/gists{/gist_id}","starred_url":"https://api.github.com/users/powerman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/powerman/subscriptions","organizations_url":"https://api.github.com/users/powerman/orgs","repos_url":"https://api.github.com/users/powerman/repos","events_url":"https://api.github.com/users/powerman/events{/privacy}","received_events_url":"https://api.github.com/users/powerman/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2018-07-12T12:54:46Z","updated_at":"2018-07-13T16:43:30Z","closed_at":null,"author_association":"NONE","body":"If I restart docker container with nats-streaming:0.10.2 my clients with durable subscription receive several last (already acked) messages once again, which is not expected behaviour with `stan.MaxInflight(1)`. Looks like it's because SQL cache not flushed on application exit."},"comment":{"url":"https://api.github.com/repos/nats-io/nats-streaming-server/issues/comments/404888250","html_url":"https://github.com/nats-io/nats-streaming-server/issues/619#issuecomment-404888250","issue_url":"https://api.github.com/repos/nats-io/nats-streaming-server/issues/619","id":404888250,"node_id":"MDEyOklzc3VlQ29tbWVudDQwNDg4ODI1MA==","user":{"login":"kozlovic","id":13736691,"node_id":"MDQ6VXNlcjEzNzM2Njkx","avatar_url":"https://avatars3.githubusercontent.com/u/13736691?v=4","gravatar_id":"","url":"https://api.github.com/users/kozlovic","html_url":"https://github.com/kozlovic","followers_url":"https://api.github.com/users/kozlovic/followers","following_url":"https://api.github.com/users/kozlovic/following{/other_user}","gists_url":"https://api.github.com/users/kozlovic/gists{/gist_id}","starred_url":"https://api.github.com/users/kozlovic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kozlovic/subscriptions","organizations_url":"https://api.github.com/users/kozlovic/orgs","repos_url":"https://api.github.com/users/kozlovic/repos","events_url":"https://api.github.com/users/kozlovic/events{/privacy}","received_events_url":"https://api.github.com/users/kozlovic/received_events","type":"User","site_admin":false},"created_at":"2018-07-13T16:43:30Z","updated_at":"2018-07-13T16:43:30Z","author_association":"MEMBER","body":"Ok, I think I found what the problem is. Should have a fix for it today. Thanks for the report!"}}
{"actor":{"display_login":"kozlovic"}}