<p>As I wrote on the mailing list, flags should not be migrated to the transaction after t_newtran() unless one uses t_flush_flags() -- that was the desired functionality, otherwise t_flush_flags() has no purpose.</p>
<p>You opened another item on this tracker related to this unexpected behaviour (<a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="310411121" data-permission-text="Issue title is private" data-url="https://github.com/kamailio/kamailio/issues/1490" href="https://github.com/kamailio/kamailio/issues/1490">#1490</a>), and I think it is better to sort this out there, because that is the unexpected behaviour. xflags behave as expected. Whatever will be the conclusion of <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="310411121" data-permission-text="Issue title is private" data-url="https://github.com/kamailio/kamailio/issues/1490" href="https://github.com/kamailio/kamailio/issues/1490">#1490</a> will be applied to both flags and xflags, but makes no sense to track an issue with two separate items.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/kamailio/kamailio/issues/1288#issuecomment-378834818">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AF36ZawNtjeiNl7QRU0kBDktg0baFRstks5tlbuHgaJpZM4QKR-M">mute the thread</a>.<img src="https://github.com/notifications/beacon/AF36ZQSSUx5cDFAIh58jUEekt0PJO-Wpks5tlbuHgaJpZM4QKR-M.gif" height="1" width="1" alt="" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/kamailio/kamailio/issues/1288#issuecomment-378834818"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/kamailio/kamailio","title":"kamailio/kamailio","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/kamailio/kamailio"}},"updates":{"snippets":[{"icon":"PERSON","message":"@miconda in #1288: As I wrote on the mailing list, flags should not be migrated to the transaction after t_newtran() unless one uses t_flush_flags() -- that was the desired functionality, otherwise t_flush_flags() has no purpose.\r\n\r\nYou opened another item on this tracker related to this unexpected behaviour (#1490), and I think it is better to sort this out there, because that is the unexpected behaviour. xflags behave as expected. Whatever will be the conclusion of #1490 will be applied to both flags and xflags, but makes no sense to track an issue with two separate items."}],"action":{"name":"View Issue","url":"https://github.com/kamailio/kamailio/issues/1288#issuecomment-378834818"}}}</script>