Major - P3 If a user opens up a backup cursor to take the initial full backup for incremental (i.e. specifying a configuration string something like incremental=(enabled,this_id="ID1") and then tries to open a duplicate/incremental cursor on that we hit an assertion failure instead of returning an error.
The usage is a user error as a src_id= must be specified to use a top-level backup cursor as the source for incremental backups. This usage should be caught and EINVAL returned with a helpful message.
Currently the assertion stack is:
#3 0x00007f760ef23e4e in __wt_curbackup_open_incr (session=0x9b0c00, uri=0xb974b0 "backup:", other=0xb97bc0, cursor=0xb99c00,
cfg=0x7ffd233ce980, cursorp=0x7ffd233ce998) at ../src/cursor/cur_backup_incr.c:177
#4 0x00007f760ef20aa9 in __wt_curbackup_open (session=0x9b0c00, uri=0xb974b0 "backup:", other=0xb97bc0, cfg=0x7ffd233ce980,
cursorp=0x7ffd233ce998) at ../src/cursor/cur_backup.c:283
#5 0x00007f760effc45e in __session_open_cursor_int (session=0x9b0c00, uri=0xb974b0 "backup:", owner=0x0, other=0xb97bc0,
cfg=0x7ffd233ce980, cursorp=0x7ffd233ce998) at ../src/session/session_api.c:472
#6 0x00007f760effce08 in __session_open_cursor (wt_session=0x9b0c00, uri=0xb974b0 "backup:", to_dup=0xb97bc0,
config=0x7f760e1d1fa4 "incremental=(file=WiredTigerLog.0000000001)", cursorp=0x7ffd233cea40) at ../src/session/session_api.c:577