title,body,link,tags,view_count,is_answered,score,answer_count
"Trying to update to PHP 7.4 but getting this error in an element, Warning: count(): Parameter must be an array or an object that implements Countable","<p>Hey there I am new here heard a lot about this helpful community. I'm trying to update my custom build a theme to PHP 7.4 but during compatibility testing I found this error, any help would be appreciated.</p>
<p>I have 0 knowledge of PHP (currently)</p>
<p>Here is the code.</p>
<pre><code>$type_terms = get_the_terms( $post-&gt;ID,&quot;property-type&quot; );
$type_count = count($type_terms);
if(!empty($type_terms)){
    echo '&lt;small&gt; - ';
    $loop_count = 1;
    foreach($type_terms as $typ_trm){
        echo $typ_trm-&gt;name;
        if($loop_count &lt; $type_count &amp;&amp; $type_count &gt; 1){
            echo ', ';
        }
        $loop_count++;
    }
    echo '&lt;/small&gt;';
}else{
    echo '&amp;nbsp;';
}
?&gt;
            &lt;/span&gt;
        &lt;/h5&gt;
    &lt;/div&gt;

    &lt;div class=&quot;property-meta clearfix&quot;&gt;
        &lt;?php
</code></pre>
<p>Thanks</p>
",https://stackoverflow.com/questions/70654096/trying-to-update-to-php-7-4-but-getting-this-error-in-an-element-warning-count,"['php', 'wordpress', 'wordpress-theming', 'php-7.3']",375,True,0,1
USB Debugging Re-Authorization Required After &quot;Always Allow&quot;,"<p>I use an Android phone to do some basic Bluetooth compatibility testing in a remote testing environment.</p>
<p>In order to automate the test phone with Appium or view it's interface using Vysor, I have to allow a &quot;USB Debugging&quot; pop-up. This pop up gives the option to &quot;Always Allow Connections from this PC&quot; which I select each time. However, this authorization seems to reset after some period of time and I can't figure out why.</p>
<p>Multiple users access the phone from their own user accounts, and USB Debugging has to be authorized for each of these users individually, but whenever the authorization resets, it resets for all users and all users must be individually re-authorized.</p>
<p>These resets tend to happen on average about once per month.</p>
<p>My first thought was the phone must be updating, but Automatic Security Updates are disabled on the test phone, so I don't think that is the issue.</p>
<p>The last time I had to re-authorize USB Debugging, I noticed this pop-up on windows which occurred suspiciously the day before I had to re-authorize, but I don't know what caused this.</p>
<p><a href=""https://i.stack.imgur.com/75nRY.png"" rel=""nofollow noreferrer""><img src=""https://i.stack.imgur.com/75nRY.png"" alt=""Potentially related pop-up in Windows"" /></a></p>
<p>Does anyone know what might be causing these resets? Given how our testing is remote, it can be a major inconvenience to re-authorize the phone since the resets occur unpredictably.</p>
",https://stackoverflow.com/questions/74117749/usb-debugging-re-authorization-required-after-always-allow,"['android', 'debugging', 'usb', 'appium', 'adb']",185,False,0,0
Do we need to do Consumer Driven Contract Testing Kafka Driven Micro-services when we have the Scheme Registry?,"<p>I am trying to understand if the concept of Consumer-Driven Contracts ( <a href=""https://martinfowler.com/articles/consumerDrivenContracts.html"" rel=""nofollow noreferrer"">CDC</a> ) is still valid in the context of Kafka based Event Driven Architecture.</p>
<p>In the RESTful world, Consumer-Driven Contract verification is vital, because there is no concept of schema evolution based compatibility testing that happens at runtime. A bad producer may be free to change the schema and deploy without notifying consumers and if the APIs are not versioned properly, that may break your consumers if the producer hasn't paid attention to the consumer patterns. So the concept of CDC provides the best way in my opinion to ensure that producers stay consumer compliant as they evolve their schemas.</p>
<p>Now, focusing on the Kafka based EDA, the concept of Schema Registry plays a bigger role in consumer - producer relationships. It acts as the coordinator between consumers and producers helping to evolve schemas with a level of compatibility you desire so that producers won't break consumers or at least it has been made very difficult to do so. With that trust in place, I am trying to understand if the concept of CDC is still applicable for Kafka / Schema Registry driven micro-service architectures?</p>
<p>Referring: <a href=""https://docs.confluent.io/cloud/current/client-apps/testing.html#schema-management-and-evolution"" rel=""nofollow noreferrer"">https://docs.confluent.io/cloud/current/client-apps/testing.html#schema-management-and-evolution</a></p>
<blockquote>
<p>After your applications are running in production, schemas may evolve but still need to be compatible for all applications that rely on both old and new versions of a schema. Confluent Schema Registry allows for schema evolution and provides compatibility checks to ensure that the contract between producers and consumers is not broken.&quot;&quot;&quot;</p>
</blockquote>
<p><strong>Update:</strong> Further more, In Kafka, we mostly use Avro like Schema Oriented Serialization formats, it seems the support within the Contract Testing Frameworks for such formats is limited too.</p>
<ul>
<li><a href=""https://github.com/pact-foundation/pact-jvm/issues/603"" rel=""nofollow noreferrer"">https://github.com/pact-foundation/pact-jvm/issues/603</a></li>
<li><a href=""https://stackoverflow.com/questions/66654842/spring-cloud-contract-tests-for-avro-messages-using-schema-registry"">Spring cloud contract tests for avro messages using Schema Registry</a></li>
</ul>
",https://stackoverflow.com/questions/71028845/do-we-need-to-do-consumer-driven-contract-testing-kafka-driven-micro-services-wh,"['apache-kafka', 'confluent-platform', 'confluent-schema-registry', 'pact', 'spring-cloud-contract']",664,True,1,2
