Tarantool development patches archive
 help / color / mirror / Atom feed
From: Kirill Yukhin <kyukhin@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 1/1] Fix bootstrap.snap corrupted file.
Date: Tue, 26 Nov 2019 10:40:27 +0300	[thread overview]
Message-ID: <20191126074027.iqgcddcc7us3cttl@tarantool.org> (raw)
In-Reply-To: <b93777432dac1620878987f4eeb3f9bce2898b37.1574616237.git.v.shpilevoy@tarantool.org>

Hello,

On 24 ноя 18:24, Vladislav Shpilevoy wrote:
> Bootstrap.snap is created from a normal snapshot file, but with
> erased VClock option in the header:
> 
>     SNAP
>     0.13
>     Version: 2.2.1-122-g1146bb78d
>     Instance: 03d3836a-e608-421c-9f8d-ad9beefe7440
>     VClock: {}
> 
> In a normal snapshot it is 'VClock: {1: ...}'. To erase the option
> usually developers use 'vim'. But when a binary file is opened in
> vim without any arguments, like this:
> 
>     vim bootstrap.snap
> 
> on close it will edit some parts of the file in unexpected ways,
> depending on local vim settings.
> 
> To forbid any implicit changes binary mode should be used:
> 
>     vim -b bootstrap.snap
> 
> The patch regenerates bootstrap.snap and drops VClock using binary
> mode vim.
> 
> Closes #4510
> ---
> Branch: https://github.com/tarantool/tarantool/tree/gerold103/gh-4510-bootstrap-corrupt-2.2
> Issue: https://github.com/tarantool/tarantool/issues/4510

Your patch LGTM.
I've checked your patch into 2.2

--
Regards, Kirill Yukhin

      parent reply	other threads:[~2019-11-26  7:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-24 17:24 Vladislav Shpilevoy
2019-11-24 20:21 ` Vladislav Shpilevoy
2019-11-26  7:40 ` Kirill Yukhin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191126074027.iqgcddcc7us3cttl@tarantool.org \
    --to=kyukhin@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH 1/1] Fix bootstrap.snap corrupted file.' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox