Sf3.4 - Warning: count(): Parameter must be an array or an object that implements Countable

This is happening for all coccorico ADMIN context menus - using cocorico with docker container
After correcting exception errors when accessing the admin area, as this commit:
https://github.com/Cocolabs-SAS/cocorico/commit/813dd0fdcecb133162a27e15efc2c2808607919a
I can connect in admin, but all admin pages are still incompatible with this error:
Logs below:
Warning: count(): Parameter must be an array or an object that implements Countable
500 Internal Server Error - ContextErrorException
Stack Trace
in vendor/symfony/symfony/src/Symfony/Component/Validator/Validator/RecursiveContextualValidator.php at line 740   +
at ErrorHandler ->handleError ('2', 'count(): Parameter must be an array or an object that implements Countable', '/cocorico/vendor/symfony/symfony/src/Symfony/Component/Validator/Validator/RecursiveContextualValidator.php', '740', array('value' => object(OrderedHashMap), 'object' => object(Form), 'cacheKey' => '0000000026ace9d7000000005ef9bc0d:children', 'metadata' => object(PropertyMetadata), 'propertyPath' => 'children', 'groups' => array('Default'), 'cascadedGroups' => null, 'traversalStrategy' => '1', 'context' => object(ExecutionContext), 'group' => 'Default', 'key' => '0', 'cascadingStrategy' => '2'))
at count (null)
in vendor/symfony/symfony/src/Symfony/Component/Validator/Validator/RecursiveContextualValidator.php at line 740   +
at RecursiveContextualValidator ->validateGenericNode (object(OrderedHashMap), object(Form), '0000000026ace9d7000000005ef9bc0d:children', object(PropertyMetadata), 'children', array('Default'), null, '1', object(ExecutionContext))
in vendor/symfony/symfony/src/Symfony/Component/Validator/Validator/RecursiveContextualValidator.php at line 608   +
at RecursiveContextualValidator ->validateClassNode (object(Form), '0000000026ace9d7000000005ef9bc0d', object(ClassMetadata), '', array('Default'), null, '1', object(ExecutionContext))
in vendor/symfony/symfony/src/Symfony/Component/Validator/Validator/RecursiveContextualValidator.php at line 364   +
at RecursiveContextualValidator ->validateObject (object(Form), '', array('Default'), '1', object(ExecutionContext))
in vendor/symfony/symfony/src/Symfony/Component/Validator/Validator/RecursiveContextualValidator.php at line 154   +
at RecursiveContextualValidator ->validate (object(Form), null, array('Default'))
in vendor/symfony/symfony/src/Symfony/Component/Validator/Validator/RecursiveValidator.php at line 134   +
at RecursiveValidator ->validate (object(Form))
in vendor/symfony/symfony/src/Symfony/Component/Form/Extension/Validator/EventListener/ValidationListener.php at line 68   +
at ValidationListener ->validateForm (object(FormEvent), 'form.post_bind', object(EventDispatcher))
at call_user_func (array(object(ValidationListener), 'validateForm'), object(FormEvent), 'form.post_bind', object(EventDispatcher))
in app/cache/dev/classes.php at line 1853   +
at EventDispatcher ->doDispatch (array(array(object(ValidationListener), 'validateForm'), array(object(DataCollectorListener), 'postSubmit')), 'form.post_bind', object(FormEvent))
in app/cache/dev/classes.php at line 1771   +
at EventDispatcher ->dispatch ('form.post_bind', object(FormEvent))
in vendor/symfony/symfony/src/Symfony/Component/EventDispatcher/ImmutableEventDispatcher.php at line 43   +
at ImmutableEventDispatcher ->dispatch ('form.post_bind', object(FormEvent))
in vendor/symfony/symfony/src/Symfony/Component/Form/Form.php at line 660   +
at Form ->submit (array())
in app/cache/dev/classes.php at line 12154   +
at Datagrid ->buildPager ()
in app/cache/dev/classes.php at line 12247   +
at Datagrid ->getForm ()
in vendor/sonata-project/admin-bundle/Controller/CRUDController.php at line 217   +
at CRUDController ->listAction ()
at call_user_func_array (array(object(CRUDController), 'listAction'), array())
in vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php at line 139   +
at HttpKernel ->handleRaw (object(Request), '1')
in vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php at line 62   +
at HttpKernel ->handle (object(Request), '1', true)
in vendor/symfony/symfony/src/Symfony/Component/HttpKernel/DependencyInjection/ContainerAwareHttpKernel.php at line 69   +
at ContainerAwareHttpKernel ->handle (object(Request), '1', true)
in vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php at line 185   +
at Kernel ->handle (object(Request))
in web/app_dev.php at line 30   +

Logs   - 1 error
INFO - The Symfony\Component\Form\Extension\Core\ChoiceList\ChoiceList class is deprecated since version 2.7 and will be removed in 3.0. Use Symfony\Component\Form\ChoiceList\ArrayChoiceList instead.
INFO - The Symfony\Component\Form\Extension\Core\ChoiceList\SimpleChoiceList class is deprecated since version 2.7 and will be removed in 3.0. Use Symfony\Component\Form\ChoiceList\ArrayChoiceList instead.
INFO - Matched route "admin_cocorico_core_listing_list".
DEBUG - Read existing security token from the session.

DEBUG - User was reloaded from a user provider.
DEBUG - Notified event "kernel.request" to listener "Symfony\Component\HttpKernel\EventListener\DebugHandlersListener::configure".
DEBUG - Notified event "kernel.request" to listener "Symfony\Component\HttpKernel\EventListener\ProfilerListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Symfony\Bundle\FrameworkBundle\EventListener\SessionListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Symfony\Component\HttpKernel\EventListener\FragmentListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Symfony\Component\HttpKernel\EventListener\RouterListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Lexik\Bundle\CurrencyBundle\EventListener\LocaleListener::setCurrencyFormatterLocale".
DEBUG - Notified event "kernel.request" to listener "Symfony\Component\HttpKernel\EventListener\LocaleListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Symfony\Component\HttpKernel\EventListener\TranslatorListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Symfony\Component\Security\Http\Firewall::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Cocorico\CoreBundle\Listener\UserTypeCookieListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Knp\Bundle\MenuBundle\EventListener\VoterInitializerListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "SimpleThings\EntityAudit\Request\CurrentUserListener::handle".
DEBUG - Notified event "kernel.controller" to listener "Symfony\Bundle\FrameworkBundle\DataCollector\RouterDataCollector::onKernelController".
DEBUG - Notified event "kernel.controller" to listener "Symfony\Component\HttpKernel\DataCollector\RequestDataCollector::onKernelController".
DEBUG - Notified event "kernel.controller" to listener "Sensio\Bundle\FrameworkExtraBundle\EventListener\ControllerListener::onKernelController".
DEBUG - Notified event "kernel.controller" to listener "Sensio\Bundle\FrameworkExtraBundle\EventListener\ParamConverterListener::onKernelController".
DEBUG - Notified event "kernel.controller" to listener "Sensio\Bundle\FrameworkExtraBundle\EventListener\HttpCacheListener::onKernelController".
DEBUG - Notified event "kernel.controller" to listener "Sensio\Bundle\FrameworkExtraBundle\EventListener\SecurityListener::onKernelController".
DEBUG - Notified event "kernel.controller" to listener "Sensio\Bundle\FrameworkExtraBundle\EventListener\TemplateListener::onKernelController".
INFO - Returning a type name from Sonata\AdminBundle\Form\Extension\Field\Type\FormTypeFieldExtension::getExtendedType() is deprecated since version 2.8 and will be removed in 3.0. Return the fully-qualified type class name instead.
INFO - Accessing type "form" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\FormType" instead.
INFO - Sonata\AdminBundle\Form\Extension\Field\Type\FormTypeFieldExtension: The FormTypeExtensionInterface::setDefaultOptions() method is deprecated since version 2.7 and will be removed in 3.0. Use configureOptions() instead. This method will be added to the FormTypeExtensionInterface with Symfony 3.0.
INFO - Sonata\AdminBundle\Form\Extension\Field\Type\MopaCompatibilityTypeFieldExtension: The FormTypeExtensionInterface::setDefaultOptions() method is deprecated since version 2.7 and will be removed in 3.0. Use configureOptions() instead. This method will be added to the FormTypeExtensionInterface with Symfony 3.0.
INFO - Sonata\AdminBundle\Form\Extension\Field\Type\FormTypeFieldExtension: The FormTypeExtensionInterface::setDefaultOptions() method is deprecated since version 2.7 and will be removed in 3.0. Use configureOptions() instead. This method will be added to the FormTypeExtensionInterface with Symfony 3.0.
INFO - Accessing type "hidden" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\HiddenType" instead.
INFO - Sonata\AdminBundle\Form\Type\Filter\DefaultType: The FormTypeInterface::getName() method is deprecated since version 2.8 and will be removed in 3.0. Remove it from your classes. Use getBlockPrefix() if you want to customize the template block prefix. This method will be added to the FormTypeInterface with Symfony 3.0.
INFO - Accessing type "sonata_type_filter_default" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\AdminBundle\Form\Type\Filter\DefaultType" instead.
INFO - Sonata\AdminBundle\Form\Type\Filter\DefaultType: The FormTypeInterface::setDefaultOptions() method is deprecated since version 2.7 and will be removed in 3.0. Use configureOptions() instead. This method will be added to the FormTypeInterface with Symfony 3.0.
INFO - Sonata\AdminBundle\Form\Type\Filter\ChoiceType: The FormTypeInterface::getName() method is deprecated since version 2.8 and will be removed in 3.0. Remove it from your classes. Use getBlockPrefix() if you want to customize the template block prefix. This method will be added to the FormTypeInterface with Symfony 3.0.
INFO - Accessing type "sonata_type_filter_choice" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\AdminBundle\Form\Type\Filter\ChoiceType" instead.
INFO - Sonata\AdminBundle\Form\Type\Filter\ChoiceType: The FormTypeInterface::setDefaultOptions() method is deprecated since version 2.7 and will be removed in 3.0. Use configureOptions() instead. This method will be added to the FormTypeInterface with Symfony 3.0.
INFO - Accessing type "sonata_type_filter_choice" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\AdminBundle\Form\Type\Filter\ChoiceType" instead.
INFO - Accessing type "sonata_type_filter_default" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\AdminBundle\Form\Type\Filter\DefaultType" instead.
INFO - Accessing type "sonata_type_filter_choice" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\AdminBundle\Form\Type\Filter\ChoiceType" instead.
INFO - Accessing type "sonata_type_filter_default" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\AdminBundle\Form\Type\Filter\DefaultType" instead.
INFO - Accessing type "sonata_type_filter_default" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\AdminBundle\Form\Type\Filter\DefaultType" instead.
INFO - Accessing type "sonata_type_filter_default" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\AdminBundle\Form\Type\Filter\DefaultType" instead.
INFO - Accessing type "sonata_type_filter_default" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\AdminBundle\Form\Type\Filter\DefaultType" instead.
INFO - Accessing type "sonata_type_filter_default" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\AdminBundle\Form\Type\Filter\DefaultType" instead.
INFO - Accessing type "sonata_type_filter_default" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\AdminBundle\Form\Type\Filter\DefaultType" instead.
INFO - Accessing type "hidden" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\HiddenType" instead.
INFO - Accessing type "hidden" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\HiddenType" instead.
INFO - Accessing type "hidden" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\HiddenType" instead.
INFO - Accessing type "hidden" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\HiddenType" instead.
INFO - Accessing type "text" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\TextType" instead.
INFO - Accessing type "choice" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\ChoiceType" instead.
INFO - The value "false" for the "choices_as_values" option of the "choice" form type (Symfony\Component\Form\Extension\Core\Type\ChoiceType) is deprecated since version 2.8 and will not be supported anymore in 3.0. Set this option to "true" and flip the contents of the "choices" option instead.
INFO - The Symfony\Component\Form\ChoiceList\ArrayKeyChoiceList class is deprecated since version 2.8 and will be removed in 3.0. Use Symfony\Component\Form\ChoiceList\ArrayChoiceList instead.
INFO - Accessing type "text" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\TextType" instead.
INFO - Accessing type "choice" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\ChoiceType" instead.
INFO - The value "false" for the "choices_as_values" option of the "choice" form type (Symfony\Component\Form\Extension\Core\Type\ChoiceType) is deprecated since version 2.8 and will not be supported anymore in 3.0. Set this option to "true" and flip the contents of the "choices" option instead.
INFO - Accessing type "text" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\TextType" instead.
INFO - Accessing type "choice" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\ChoiceType" instead.
INFO - Accessing type "sonata_type_equal" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\CoreBundle\Form\Type\EqualType" instead.
INFO - The value "false" for the "choices_as_values" option of the "choice" form type (Symfony\Component\Form\Extension\Core\Type\ChoiceType) is deprecated since version 2.8 and will not be supported anymore in 3.0. Set this option to "true" and flip the contents of the "choices" option instead.
INFO - Accessing type "entity" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Bridge\Doctrine\Form\Type\EntityType" instead.
INFO - Accessing type "choice" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\ChoiceType" instead.
INFO - The value "false" for the "choices_as_values" option of the "choice" form type (Symfony\Component\Form\Extension\Core\Type\ChoiceType) is deprecated since version 2.8 and will not be supported anymore in 3.0. Set this option to "true" and flip the contents of the "choices" option instead.
INFO - Accessing type "choice" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\ChoiceType" instead.
INFO - Accessing type "hidden" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\HiddenType" instead.
INFO - Accessing type "date" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\DateType" instead.
INFO - Accessing type "sonata_type_date_picker" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\CoreBundle\Form\Type\DatePickerType" instead.
INFO - Accessing type "hidden" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\HiddenType" instead.
INFO - Accessing type "sonata_type_date_picker" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\CoreBundle\Form\Type\DatePickerType" instead.
INFO - Accessing type "choice" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\ChoiceType" instead.
INFO - The value "false" for the "choices_as_values" option of the "choice" form type (Symfony\Component\Form\Extension\Core\Type\ChoiceType) is deprecated since version 2.8 and will not be supported anymore in 3.0. Set this option to "true" and flip the contents of the "choices" option instead.
INFO - Accessing type "text" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\TextType" instead.
INFO - Accessing type "choice" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\ChoiceType" instead.
INFO - The value "false" for the "choices_as_values" option of the "choice" form type (Symfony\Component\Form\Extension\Core\Type\ChoiceType) is deprecated since version 2.8 and will not be supported anymore in 3.0. Set this option to "true" and flip the contents of the "choices" option instead.
INFO - Accessing type "text" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Component\Form\Extension\Core\Type\TextType" instead.
INFO - Accessing type "sonata_type_equal" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\CoreBundle\Form\Type\EqualType" instead.
INFO - The value "false" for the "choices_as_values" option of the "choice" form type (Symfony\Component\Form\Extension\Core\Type\ChoiceType) is deprecated since version 2.8 and will not be supported anymore in 3.0. Set this option to "true" and flip the contents of the "choices" option instead.
INFO - Accessing type "entity" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Bridge\Doctrine\Form\Type\EntityType" instead.
INFO - Accessing type "sonata_type_equal" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Sonata\CoreBundle\Form\Type\EqualType" instead.
INFO - The value "false" for the "choices_as_values" option of the "choice" form type (Symfony\Component\Form\Extension\Core\Type\ChoiceType) is deprecated since version 2.8 and will not be supported anymore in 3.0. Set this option to "true" and flip the contents of the "choices" option instead.
INFO - Accessing type "entity" by its string name is deprecated since version 2.8 and will be removed in 3.0. Use the fully-qualified type class name "Symfony\Bridge\Doctrine\Form\Type\EntityType" instead.
CRITICAL - Uncaught PHP Exception Symfony\Component\Debug\Exception\ContextErrorException: "Warning: count(): Parameter must be an array or an object that implements Countable" at /cocorico/vendor/symfony/symfony/src/Symfony/Component/Validator/Validator/RecursiveContextualValidator.php line 740
DEBUG - Notified event "kernel.request" to listener "Symfony\Component\HttpKernel\EventListener\DebugHandlersListener::configure".
DEBUG - Notified event "kernel.request" to listener "Symfony\Component\HttpKernel\EventListener\ProfilerListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Symfony\Bundle\FrameworkBundle\EventListener\SessionListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Symfony\Component\HttpKernel\EventListener\FragmentListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Symfony\Component\HttpKernel\EventListener\RouterListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Lexik\Bundle\CurrencyBundle\EventListener\LocaleListener::setCurrencyFormatterLocale".
DEBUG - Notified event "kernel.request" to listener "Symfony\Component\HttpKernel\EventListener\LocaleListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Symfony\Component\HttpKernel\EventListener\TranslatorListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Symfony\Component\Security\Http\Firewall::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Cocorico\CoreBundle\Listener\UserTypeCookieListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "Knp\Bundle\MenuBundle\EventListener\VoterInitializerListener::onKernelRequest".
DEBUG - Notified event "kernel.request" to listener "SimpleThings\EntityAudit\Request\CurrentUserListener::handle".
INFO - The possibility to register the same extension twice ("Text") is deprecated since version 1.23 and will be removed in Twig 2.0. Use proper PHP inheritance instead.
INFO - The "security.context" service is deprecated since Symfony 2.6 and will be removed in 3.0.
INFO - The Symfony\Component\Security\Core\SecurityContext class is deprecated since version 2.6 and will be removed in 3.0. Use Symfony\Component\Security\Core\Authentication\Token\Storage\TokenStorage or Symfony\Component\Security\Core\Authorization\AuthorizationChecker instead.
DEBUG - Notified event "kernel.controller" to listener "Symfony\Bundle\FrameworkBundle\DataCollector\RouterDataCollector::onKernelController".
DEBUG - Notified event "kernel.controller" to listener "Symfony\Component\HttpKernel\DataCollector\RequestDataCollector::onKernelController".
DEBUG - Notified event "kernel.controller" to listener "Sensio\Bundle\FrameworkExtraBundle\EventListener\ControllerListener::onKernelController".
DEBUG - Notified event "kernel.controller" to listener "Sensio\Bundle\FrameworkExtraBundle\EventListener\ParamConverterListener::onKernelController".
DEBUG - Notified event "kernel.controller" to listener "Sensio\Bundle\FrameworkExtraBundle\EventListener\HttpCacheListener::onKernelController".
DEBUG - Notified event "kernel.controller" to listener "Sensio\Bundle\FrameworkExtraBundle\EventListener\SecurityListener::onKernelController".
DEBUG - Notified event "kernel.controller" to listener "Sensio\Bundle\FrameworkExtraBundle\EventListener\TemplateListener::onKernelController".

Stack Trace (Plain Text)   -
[1] Symfony\Component\Debug\Exception\ContextErrorException: Warning: count(): Parameter must be an array or an object that implements Countable
    at n/a
        in /cocorico/vendor/symfony/symfony/src/Symfony/Component/Validator/Validator/RecursiveContextualValidator.php line 740

    at Symfony\Component\Debug\ErrorHandler->handleError('2', 'count(): Parameter must be an array or an object that implements Countable', '/cocorico/vendor/symfony/symfony/src/Symfony/Component/Validator/Validator/RecursiveContextualValidator.php', '740', array('value' => object(OrderedHashMap), 'object' => object(Form), 'cacheKey' => '0000000026ace9d7000000005ef9bc0d:children', 'metadata' => object(PropertyMetadata), 'propertyPath' => 'children', 'groups' => array('Default'), 'cascadedGroups' => null, 'traversalStrategy' => '1', 'context' => object(ExecutionContext), 'group' => 'Default', 'key' => '0', 'cascadingStrategy' => '2'))
        in  line

    at count(null)
        in /cocorico/vendor/symfony/symfony/src/Symfony/Component/Validator/Validator/RecursiveContextualValidator.php line 740

    at Symfony\Component\Validator\Validator\RecursiveContextualValidator->validateGenericNode(object(OrderedHashMap), object(Form), '0000000026ace9d7000000005ef9bc0d:children', object(PropertyMetadata), 'children', array('Default'), null, '1', object(ExecutionContext))
        in /cocorico/vendor/symfony/symfony/src/Symfony/Component/Validator/Validator/RecursiveContextualValidator.php line 608

    at Symfony\Component\Validator\Validator\RecursiveContextualValidator->validateClassNode(object(Form), '0000000026ace9d7000000005ef9bc0d', object(ClassMetadata), '', array('Default'), null, '1', object(ExecutionContext))
        in /cocorico/vendor/symfony/symfony/src/Symfony/Component/Validator/Validator/RecursiveContextualValidator.php line 364

    at Symfony\Component\Validator\Validator\RecursiveContextualValidator->validateObject(object(Form), '', array('Default'), '1', object(ExecutionContext))
        in /cocorico/vendor/symfony/symfony/src/Symfony/Component/Validator/Validator/RecursiveContextualValidator.php line 154

    at Symfony\Component\Validator\Validator\RecursiveContextualValidator->validate(object(Form), null, array('Default'))
        in /cocorico/vendor/symfony/symfony/src/Symfony/Component/Validator/Validator/RecursiveValidator.php line 134

    at Symfony\Component\Validator\Validator\RecursiveValidator->validate(object(Form))
        in /cocorico/vendor/symfony/symfony/src/Symfony/Component/Form/Extension/Validator/EventListener/ValidationListener.php line 68

    at Symfony\Component\Form\Extension\Validator\EventListener\ValidationListener->validateForm(object(FormEvent), 'form.post_bind', object(EventDispatcher))
        in  line

    at call_user_func(array(object(ValidationListener), 'validateForm'), object(FormEvent), 'form.post_bind', object(EventDispatcher))
        in /cocorico/app/cache/dev/classes.php line 1853

    at Symfony\Component\EventDispatcher\EventDispatcher->doDispatch(array(array(object(ValidationListener), 'validateForm'), array(object(DataCollectorListener), 'postSubmit')), 'form.post_bind', object(FormEvent))
        in /cocorico/app/cache/dev/classes.php line 1771

    at Symfony\Component\EventDispatcher\EventDispatcher->dispatch('form.post_bind', object(FormEvent))
        in /cocorico/vendor/symfony/symfony/src/Symfony/Component/EventDispatcher/ImmutableEventDispatcher.php line 43

    at Symfony\Component\EventDispatcher\ImmutableEventDispatcher->dispatch('form.post_bind', object(FormEvent))
        in /cocorico/vendor/symfony/symfony/src/Symfony/Component/Form/Form.php line 660

    at Symfony\Component\Form\Form->submit(array())
        in /cocorico/app/cache/dev/classes.php line 12154

    at Sonata\AdminBundle\Datagrid\Datagrid->buildPager()
        in /cocorico/app/cache/dev/classes.php line 12247

    at Sonata\AdminBundle\Datagrid\Datagrid->getForm()
        in /cocorico/vendor/sonata-project/admin-bundle/Controller/CRUDController.php line 217

    at Sonata\AdminBundle\Controller\CRUDController->listAction()
        in  line

    at call_user_func_array(array(object(CRUDController), 'listAction'), array())
        in /cocorico/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php line 139

    at Symfony\Component\HttpKernel\HttpKernel->handleRaw(object(Request), '1')
        in /cocorico/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php line 62

    at Symfony\Component\HttpKernel\HttpKernel->handle(object(Request), '1', true)
        in /cocorico/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/DependencyInjection/ContainerAwareHttpKernel.php line 69

    at Symfony\Component\HttpKernel\DependencyInjection\ContainerAwareHttpKernel->handle(object(Request), '1', true)
        in /cocorico/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php line 185

    at Symfony\Component\HttpKernel\Kernel->handle(object(Request))
        in /cocorico/web/app_dev.php line 30

Please help me
My project is stopped because of these errors, I need a lot of progress in my project.
Unfortunately I still do not have enough knowledge in the cocorico to be able to solve this problem alone.
Thanks again!

Hello @Saraivahost ,
This issue is now fixed, so can you please pull your cocorico repositories (image and source code) ?


Support for Spotify Playlist

Would it be possible to add support for Spotify Playlist?
I tried by either entering the url but receiving this message I'm sorry, but I can't access or provide content from specific URLs, including Spotify playlists. Or by giving the description e.g. Spotify Playlist Rock Classics doesn't give the result.
Would be great if it would be able to lookup the playlist by url or description.

Great idea, the website actually already has a Spotify connection. So it should be fairly easy to include an "import playlist" page in the extension. Will add it soon.

@Eric-sson The feature has been added. When you update your installment to the latest version you will find an "import playlist" option in the main menu. Here you can add spotify playlists.

Thanks for adding this. I have tried a few playlists and it's working.
However I noticed that there is a limitation of 100 tracks. Playlists with over 100 tracks will just stop and only show the first 100 tracks. I believe that this is a limitation of the Spotify API. I am not a developer myself but maybe something can be implemented to load the playlist from Spotify in batches, first 100 tracks and then the next 100 tracks till there are no new tracks anymore?

@Eric-sson Can you share the playlist link we me? I haven't tried with playlists of that size!

This one has 200 songs: https://open.spotify.com/playlist/37i9dQZF1DWXRqgorJj26U
It will stop at track 100 which Metallica - Seek & Destroy
And this one might be really challenging as it has 1,996 songs: https://open.spotify.com/playlist/37i9dQZF1DWTmvXBN4DgpA
It will stop at track 100 which is U2 - One

@Eric-sson The code has been updated to support infinite amount of tracks. Keep in mind though that the more tracks - the worse the performance is. For the Top 2000: To get the tracks from Spotify takes about 40 seconds. Than to match it with your Plex takes about 120 seconds.
And then to create the playlist in Plex takes minutes 🤯  I just did a test run and it matched almost all tracks which then resulted in a Plex playlist of 1949 tracks.

Hahaha awesome to hear ❤  You can always buy me a coffee. You would be the first 😂

I tried this morning to import the Top 2000 playlist but I receive the below error.
_@http://<IP_ADDRESS>:9010/_next/static/chunks/319-15fb403c6d4018d7.js:123:6212
5121/ez.xhr</</u.onerror@http://<IP_ADDRESS>:9010/_next/static/chunks/319-15fb403c6d4018d7.js:123:20439
Any idea what is causing this? Another playlist with 290 songs was working fine.

@Eric-sson Could you include a screenshot?

@jjdenhertog that's for the below Top 2000 playlist
https://open.spotify.com/playlist/37i9dQZF1DWTmvXBN4DgpA

@Eric-sson it might be a connection time-out because it takes such a long time to handle the request. I will check do an extra check and see if I can create a more meaningful error message 😂

@Eric-sson It turned out to be a limitation at the website. Where there is a maximum request time of 30 seconds. To cover this I have moved the loading of the Spotify data to the extension. In order to get this to work you need to setup a Spotify App and add the client_id / client_secret to the environment variables.
I have updated the readme:
https://github.com/aiguestdj/plex-extension?tab=readme-ov-file#spotify-import

Thanks it's working now! 👍


[BUG] Broken on Python 3.8.0?

Describe the bug
After a big update to my system, the game refuses to start now with this error
play.py:161: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if len(story_manager.story.actions) is 0:
Traceback (most recent call last):
  File "play.py", line 2, in <module>
    from generator.gpt2.gpt2_generator import *
  File "/Fast-Games/AI Dungeon 2/generator/gpt2/gpt2_generator.py", line 5, in <module>
    import tensorflow as tf
ModuleNotFoundError: No module named 'tensorflow'

I think it may be because python updated, now python -V returns Python 3.8.0 as the version
To Reproduce
Steps to reproduce the behavior:

Attempt to start the script with python play.py

Expected behavior
It should start
Additional context

OS - Linux Kiko-LM 5.4.2-1-MANJARO #1 SMP PREEMPT Thu Dec 5 09:55:57 UTC 2019 x86_64 GNU/Linux

Yeah, this is because tensorflow v1.15 only works up to python 3.6 :(
You'll have to manually install python 3.6 for this to work.


MySQL Error when helm install

Hi,
I tried to install tuleap on my K8S cluster. I realize that MySQL and Redis have been successfully deployed. However, tuleap would report such error.
Invalid SQL modes: ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, check MySQL server configuration
K8S version: 1.24
Storage: NAS
Thanks in advance.

Same for me
Start init sequence for Tuleap Community Edition — Dev Build <IP_ADDRESS>
Setup database
Invalid SQL modes: STRICT_TRANS_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, check MySQL server configuration

K8S version: v1.26
Storage: NAS

run the following command in the mysql and restart the deployment for the tuleap
mysql -u  -p -e "SET GLOBAL sql_mode = 'NO_ENGINE_SUBSTITUTION';"


Add no-irregular-whitespaces rule

PR checklist

[ ] Addresses an existing issue: #0000
[x] New feature, bugfix, or enhancement

[x] Includes tests

[ ] Documentation update

Overview of change:
Implementation of no-irregular-whitespaces rule from eslint
Especially useful on macOS where pressing Alt + Space adds in a non breaking space.
Is there anything you'd like reviewers to focus on?

Shall we consider ignoring comments/strings? If so I'd like advice on how to achieve this through specific walkers 😄
In the tests, I tried to specify directly unicode characters for invalid whitespaces, but they were escaped when using node.getText(). Is there another way?

CHANGELOG.md entry:

[new-rule] no-irregular-whitespaces

You don't need a RuleWalker for this, since you aren't actually traversing the AST.
This could be:
...
export class Rule {
	...
    public apply(sourceFile: ts.SourceFile): Lint.RuleFailure[] {
        return this.applyWithFunction(sourceFile, walk);
    }
}

function walk(ctx: Lint.WalkContext<void>): void {
    IRREGULAR_WHITESPACE.lastIndex = 0;
    let match: RegExpExecArray | null;
    while ((match = IRREGULAR_WHITESPACE.exec(ctx.sourceFile.text)) !== null) {
        const start = match.index;
        const len = match[0].length;
        const fix = new Lint.Replacement(start, len, " "); // Note: probably want to replace vertical whitespace with "\n" instead.
        ctx.addFailureAt(start, len, Rule.FAILURE_STRING, fix);
    }
}

// Inspired by: https://github.com/eslint/eslint/blob/master/lib/rules/no-irregular-whitespace.js
// tslint:disable-next-line max-line-length
const IRREGULAR_WHITESPACE = /[\f\v\u0085\u00A0\ufeff\u00a0\u1680\u180e\u2000\u2001\u2002\u2003\u2004\u2005\u2006\u2007\u2008\u2009\u200a\u200b\u202f\u205f\u3000\u2028\u2029]+/mg;

Be sure to include a test with multiple unusual spaces in a row, and a test with vertical whitespace (if that's in the regex there).

In the tests, I tried to specify directly unicode characters for invalid whitespaces, but they were escaped when using node.getText().
As far as I can tell, the space in your test.ts.lint is a normal space. I pasted it into the console with " ".charCodeAt(0) and got 32 (normal space). Either git is doint something funny or you created the test wrong. You can generate copy-pastable wierd spaces by using e.g. "\u2000" in a node console.

I'm still trying to generate a proper test file, do not review now :)
(Unless you can give me clues :D)


I just tried it, and it seems to work.

Did you happen to put the amount in Total Amount vs Refund Amount?

Yes, I used refund amount field.
Investigating why a refund is not displayed further, checked meta keys in the table (refund amount is recorded):


Cleanup Transport (mostly) and Cluster code

Main changes:

Introduce Protocol API and default implementation ProtostuffProtocol (refactoring)
Make Cluster send/listen methods work with ClusterMember instead of TransportEndpoint
Clean TransportSettings code
Change cluster member data model to ClusterMember (cluster) -> TransportEndpoint (transport) -> TransportAddress (transport)
Added get member by id method to cluster membership API
Removed from public API ITransportChannel (fixing issue #27)
Cleanup code and logic of TransportPipelineFactory and its handlers
Added connect/disconnect logic to Transport API
Replace to() method with send() on Transport API
Transport instantiation changed from TransportBuilder to factory methods

squash commit

@antonkharenko let's make desription of such huge changes in a following form:
Motivation  ......
Result ......

The build fails

Squashed commits and going to merge after tests passed...


Remove quay login from release shell script

What this PR does / why we need it:
Can't work currently as the env vars from the job configuration are pointing to files that need to get passed in. Sp this PR removes the login to quay.io in the release script. Another PR in project-infra adds it to the job configuration.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
/cc @davidvossel
Release note:

NONE

/lgtm
/approve

@dhiller is there a corresponding prow job being created for the release automation now?


improvement: latest version

Please consider my idea to add 'latest version' release for semver compatibility, so that not to add versions manually.
eg.
curl -Ls -o /dev/null -w %{url_effective} https://github.com/docker/compose/releases/latest

returns latest version v<sem_version> automatically
curl -fsSLI -o /dev/null -w %{url_effective} https://github.com/hectorm/hblock/releases/latest

I just created a release through the GitHub UI, is this okay now?

yes, thanks a lot


Issues triggering IFTTT

Hi guys,
I think there might be an issue triggering IFTTT events with this library currently.
//Firing off the IFTTT event
IFTTTWebhook hook(IFTTT_API_KEY, IFTTT_EVENT_NAME);
hook.trigger();
This is my event to fire off the IFTTT event (I also note in your documentation, you call as IFTTTWeb, this doesn't work and should be IFTTTWebhook).
Obviously initiating WiFi connection prior and confirming WiFi is operational before firing off IFTTTWebhook.

Not seeing the event being triggered in IFTTT, confirmed IFTTT_API_KEY and IFTTT_EVENT_NAME are correct.

@stephenmorton maybe the issue is the secure connection with IFTTT. The new IFTTT fingerprint is AA:75:CB:41:2E:D5:F9:97:FF:5D:A0:8B:7D:AC:12:21:08:4B:00:8C
@romkey may change the examples to clarify this connection issue to less advanced users including e.g. a line such as:
#define IFTTT_FINGERPRINT "AA:75:CB:41:2E:D5:F9:97:FF:5D:A0:8B:7D:AC:12:21:08:4B:00:8C"   //Update this number with the one provided at e.g., https://www.grc.com/fingerprints.htm
I'm sure he is aware of this situation since he defined the IFTTTWebhook method with 2 or 3 parameters, being the latest one when 3 parameters are specified the fingerprint fo SSL connections.
So, the connection could be something like this:
#define IFTTT_API_KEY "your API key here"
#define IFTTT_EVENT_NAME "your IFTTT event here"
#define IFTTT_FINGERPRINT "AA:75:CB:41:2E:D5:F9:97:FF:5D:A0:8B:7D:AC:12:21:08:4B:00:8C"   //Update this number with the one provided at e.g., https://www.grc.com/fingerprints.htm
WiFiClientSecure client;
IFTTTWebhook webhook(IFTTT_API_KEY, IFTTT_EVENT_NAME, IFTTT_FINGERPRINT);
By the way: is there @romkey a way to update this fingerprint without changing, recompiling an upload the code? (I didn't find a way to do it, no simple API to do it out there in my knowledge).
Best,

You can check [https://github.com/mlinaje/wemos/tree/master/WebCaptive_Portal_-_IFTTT_button] that is currently working

The new fingerprint key works.....
Thanks,


Remote "microsoft" seems redundant

Testing #4961
In this example I would not have expected to see the remote:

If you only have 1 remote, you would like the remote to be hidden?

Yes ✅

Seems like a good idea. I do think we should only hide the repository part when there is only one remote like Alex says, but not when just comparing inside a single fork when there are multiple remotes.

Fixed by bfc07690e0072a0286a36dbd04ea3126834c4386


Add activation result integration test

Provides an integration test for the activation result API.
Description

Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[x] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[x] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

@mdeuser, can you review?

@dubee do you need the inner retry per my comment? Otherwise the test LGTM.

Codecov Report

Merging #3568 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3568   +/-   ##
=======================================
  Coverage   74.94%   74.94%
=======================================
  Files         128      128
  Lines        6086     6086
  Branches      388      388
=======================================
  Hits         4561     4561
  Misses       1525     1525

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f55af05...d016b88. Read the comment docs.

@rabbah, removed  the retry loop as it will not be need with the future ActivationStore changes.


use UTF-8 as the default encoding for multipart text parts

After some tests on Chrome, it seems in multipart/form-data bodies, regular field=value parts are encoded using utf-8, not latin1
https://www.w3.org/TR/html5/forms.html#multipart/form-data-encoding-algorithm
https://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html#dom-xmlhttprequest-send

Current coverage is 98.85% (diff: 100%)

Merging #1484 into master will not change coverage

@@             master      #1484   diff @@
==========================================
  Files            30         30
  Lines          6984       6984
  Methods           0          0
  Messages          0          0
  Branches       1163       1163
==========================================
  Hits           6904       6904
  Misses           40         40
  Partials         40         40

Powered by Codecov. Last update 8155889...faa8c4e

Sounds reasonable

It's good to see more UTF-8 defaults around (: Thanks!


ingress.annotations no longer working

Chart Version: netbox-5.0.0-beta9
Input:
ingress:
  enabled: true
  className: azure-application-gateway
  annotations:
    "appgw.ingress.kubernetes.io/use-private-ip": "true"
    "appgw.ingress.kubernetes.io/backend-protocol": "http"
    "appgw.ingress.kubernetes.io/appgw-ssl-certificate": "some-cert"
  hosts:
    - host: netbox.local
      paths:
        - path: /
          pathType: Prefix
          backend:
            service:
              name: netbox
              port:
                name: http

Output:
---
# Source: netbox/templates/ingress.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: netbox
  namespace: "netbox"
  labels:
    app.kubernetes.io/instance: netbox
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: netbox
    app.kubernetes.io/version: v4.0.0
    helm.sh/chart: netbox-5.0.0-beta9
spec:

From testing a few variations setting commonAnnotations will add ingress.annotations but if commonAnnotation is default it will never add annotations to ingress.

git bisect shows this as being introduced in de1a5239ad08fa61b878a5c942556d0ea04534b2.

@rjhenry Indeed. There is already a PR fixing this: #207.


Verify SKIP_MAX + trusted_block > target_block > trusted_block

This is correctly constrained by the contract, but if developers use the TendermintX circuit with a different smart contract, it's probable they'll underconstrain.

Verify target header height > trusted header height.
Verify target header height < trusted header height + SKIP_MAX for skip circuits. Add this as a constant to consts.

https://github.com/succinctlabs/tendermintx/pull/39


Early Adopter Plan

What is the bonus for having the Early Adopter Plan?

Early Adopter Plan gives you access to use ImgBot on both public and private repos and behaves the same as the premium plan.
See https://github.com/dabutvin/ImgBot/blob/master/WebHook/WebHookFunction.cs#L212-L218
Early adopter is 781
Premium is 1750

Basically just a thank you for being a early user.
On Fri, Dec 7, 2018 at 4:09 PM Dan Butvinik<EMAIL_ADDRESS>wrote:

Early Adopter Plan gives you access to use ImgBot on both public and
private repos and behaves the same as the premium plan.
See
https://github.com/dabutvin/ImgBot/blob/master/WebHook/WebHookFunction.cs#L212-L218
Early adopter is 781
Premium is 1750
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dabutvin/ImgBot/issues/258#issuecomment-445366127,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AiKfuDmYza7exm0nDP-d7XgVvCHfMmb7ks5u2tj4gaJpZM4ZIi3u
.


Upgrade mediaflux to 4.16.071 in our ansible build

What maintenance needs to be done?
Upgrade mediaflux to 4.16.071 in our ansible build so we can match what RC is using. This version fixes the issue with NFS mounts.
Level of urgency

[ ] High
[x] Moderate
[ ] Low

Acceptance critera

[x] Create a new docker image with the newest version (Creates a fresh build, not upgrade the existing build)
[ ] Assume the servers will be rebuilt when upgraded so no separate path is needed
[ ] Created documentation on how to upgrade the version for docker
[x] Let the team know so everyone can upgrade the local mediaflux image

Hey team! Please add your planning poker estimate with Zenhub @bess @JaymeeH @jrgriffiniii @kelynch @leefaisonr

We are going to upgrade our docker build and server build separately.


eas build failed with Namespace 'androidx.versionedparcelable' is used in multiple modules

Build/Submit details page URL
No response
Summary
In react native expo app.
I run eas build --platform android
The build went through but started to fail in run gradlew step after i upgraded expo to 52:

Task :app:processReleaseMainManifest FAILED
[androidx.versionedparcelable:versionedparcelable:1.1.1] /home/expo/.gradle/caches/8.10.2/transforms/e74c4937cd2099f316b2ffa87c1bebf3/transformed/versionedparcelable-1.1.1/AndroidManifest.xml Warning:
Namespace 'androidx.versionedparcelable' is used in multiple modules and/or libraries: androidx.versionedparcelable:versionedparcelable:1.1.1, com.android.support:versionedparcelable:28.0.0. Please ensure that all modules and libraries have a unique namespace. For more information, See https://developer.android.com/studio/build/configure-app-module#set-namespace
See https://developer.android.com/r/studio-ui/build/manifest-merger for more information about the manifest merger.
Task :react-native-gesture-handler:bundleLibRuntimeToDirRelease
/home/expo/workingdir/build/android/app/src/main/AndroidManifest.xml:28:18-86 Error:
Attribute application@appComponentFactory value=(androidx.core.app.CoreComponentFactory) from [androidx.core:core:1.13.1] AndroidManifest.xml:28:18-86
is also present at [com.android.support:support-compat:28.0.0] AndroidManifest.xml:22:18-91 value=(android.support.v4.app.CoreComponentFactory).
Suggestion: add 'tools:replace="android:appComponentFactory"' to  element at AndroidManifest.xml:14:3-34:17 to override.
Task :app:mergeReleaseResources
FAILURE:
Build failed with an exception.

What went wrong:
Execution failed for task ':app:processReleaseMainManifest'.

Managed or bare?
Managed
Environment
npx expo-doctor
WARNING: We recommend using PowerShell or Bash via WSL 2 for development with Expo CLI on Windows. You may encounter issues using cmd.exe.
Enabled experimental React Native Directory checks. Unset the EXPO_DOCTOR_ENABLE_DIRECTORY_CHECK environment variable to disable this check.
✔ Check package.json for common issues
✔ Check Expo config for common issues
✔ Check native tooling versions
✔ Check if the project meets version requirements for submission to app stores
✔ Check for common project setup issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for app config fields that may not be synced in a non-CNG project
✔ Check npm/ yarn versions
✔ Check for issues with Metro config
✔ Check Expo config (app.json/ app.config.js) schema
✖ Validate packages against React Native Directory package metadata
✔ Check that native modules do not use incompatible support packages
✔ Check for legacy global CLI installed locally
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules use compatible support package versions for installed Expo SDK
Detailed check results:
The following issues were found when validating your dependencies against React Native Directory:
Untested on New Architecture: react-native-iap, tamagui
Advice:

Use libraries that are actively maintained and support the New Architecture. Find alternative libraries with https://reactnative.directory.
Add packages to expo.doctor.reactNativeDirectoryCheck.exclude in package.json to selectively skip validations, if the warning is not relevant.
Update React Native Directory to include metadata for unknown packages. Alternatively, set expo.doctor.reactNativeDirectoryCheck.listUnknownPackages in package.json to false to skip warnings about packages with no metadata, if the warning is not relevant.

One or more checks failed, indicating possible issues with the project.
Error output
No response
Reproducible demo or steps to reproduce from a blank project
My package.json:
"dependencies": {
"@expo-google-fonts/inter": "^0.2.3",
"@expo-google-fonts/varela-round": "^0.2.3",
"@expo/vector-icons": "^14.0.2",
"@react-navigation/native": "^7.0.0",
"@react-navigation/stack": "^7.0.0",
"@reduxjs/toolkit": "^2.3.0",
"@tamagui/config": "^1.110.0",
"axios": "^1.7.9",
"expo": "~52.0.17",
"expo-constants": "~17.0.3",
"expo-font": "~13.0.1",
"expo-linking": "~7.0.3",
"expo-localization": "~16.0.0",
"expo-router": "~4.0.11",
"expo-secure-store": "~14.0.0",
"expo-splash-screen": "~0.29.16",
"expo-status-bar": "~2.0.0",
"expo-system-ui": "~4.0.5",
"expo-updates": "~0.26.10",
"expo-web-browser": "~14.0.1",
"react": "18.3.1",
"react-dom": "18.3.1",
"react-native": "0.76.3",
"react-native-gesture-handler": "~2.20.2",
"react-native-iap": "^12.15.7",
"react-native-localize": "^3.3.0",
"react-native-progress": "^5.0.1",
"react-native-reanimated": "^3.16.4",
"react-native-safe-area-context": "4.12.0",
"react-native-screens": "~4.1.0",
"react-native-web": "~0.19.13",
"react-query": "^3.39.3",
"react-redux": "^9.1.2",
"tamagui": "^1.120.1"
}

Having the exact same error :(
Cant find a solution anywhere

https://github.com/expo/expo/issues/30725#issuecomment-2259404082 - it seems like it was fixed in some of the newest versions of SDK 51, please upgrade bump your SDK version it

do you know what, i never find a soultion on github question and answers,, it's the place of worst experts,, stakeoverflow is the GOAT

have you tried removing non-expo deps such as "react-native-iap" ?


Remove DL context (superseded by mDL)

Remove https://github.com/trustbloc/context/blob/master/vc/examples/driving-license-v1.jsonld once edge-sandbox is updated to use mDL type - https://github.com/trustbloc/edge-sandbox/issues/473.

This was removed as part of https://github.com/trustbloc/context/pull/50/files#diff-29cace89d3017d824ccf9fdd1730e25a.


Filtering an array via cursor

Hi, first of all, thanks a lot for your work on baobab.
I'm wondering if it would be possible to filter an array via a cursor like this:
export default branch({  filteredChats: [ 'chats', { active: true } ], }, ChatList);
Currently, the library returns the first item it encounters that matches the condition, but it would be cool to be able to filter the array based on the condition instead.
Thanks!

Why not use a monkey?
Den tis 13 mars 2018 18:38Shola Anozie<EMAIL_ADDRESS>skrev:

Hi, first of all, thanks a lot for your work on baobab.
I'm wondering if it would be possible to filter an array via a cursor like
this:
export default branch({ filteredChats: [ 'chats', { active: true } ], },
ChatList);
Currently, the library returns the first item it encounters that matches
the condition, but it would be cool to be able to filter the array based on
the condition instead.
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Yomguithereal/baobab-react/issues/129, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ADYLwBdIurvtysu2k4qBT7721oMAMOjpks5teAP-gaJpZM4SpJIH
.

Hello @soulprovidr. @Zache is right. The right tool for the job is probably a monkey. The fact is a cursor cannot be ambiguous and point to several parts of the tree at once.

Thanks a lot, I appreciate your input. I'll use a monkey for this. 👍


Matrix multiplication discrepancy

          I will piggy back off of this comment, I think there might be a bug in how matrix multiplication is performed by the crate?

I have this snippet:
 let laplacian: CsMat<_> = triplets.to_csr();

    let mut dbg_check = HashMap::new();
    for (v, (r, c)) in laplacian.iter()
    {
        if dbg_check.contains_key(&(c, r))
        {
            let o = *dbg_check.get(&(c, r)).unwrap();
            assert!(o == v, "{} {} {} {}", v, o, r, c);
        }
        dbg_check.insert((r, c), v);
    }

    let mass: CsMat<_> = mass.to_csr();

    for (_, (r, c)) in mass.iter()
    {
        assert!(r == c);
    }

    let high_laplacian = &mass * &laplacian;

    let mut dbg_check = HashMap::new();
    for (v, (r, c)) in high_laplacian.iter()
    {
        if dbg_check.contains_key(&(c, r))
        {
            let o = *dbg_check.get(&(c, r)).unwrap();
            assert!(o == v, "{} {} {} {}", v, o, r, c);
        }
        dbg_check.insert((r, c), v);
    }

According to the first check, the matrix laplacian is symmetric. Accordfing to the mid check, the matrix mass is diagonal. But the last check fails with:
thread 'convex_polytope::tests::test_topologize_skeleton' panicked at '0.2576181530716957 0.12738811865592223 512 0', src/differential_geometry.rs:270:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: test failed, to rerun pass `--lib`

So the product &mass * &laplacian is producing a non-symmetric matrix despite being the product of a diagonal and a syemmtric matrix?
How is that possible?
Originally posted by @Makogan in https://github.com/sparsemat/sprs/issues/335#issuecomment-1720213112

@Makogan counterexample
M = [0, 1; 1, 0]
D = [1, 0; 0, 9]
M*D
% ans = [0, 9; 1, 0]


[Events. Create event] Error message is not appeared below the empty 'Start time' field when user click on 'Publish' button

Environment: OS: Windows 11 Pro, version 22H2, build 22621.2861
Browser: Firefox version 121.0
Reproducible: always
Build found: 06.01.2024
Preconditions

The site GreenCity is opened
User is logged in
The 'Events' page is opened

Steps to reproduce

Click on the 'Create event' button
Fill in mandatory fields 'Title', 'Events Description', pick 'Initiative type'
In the 'Duration' dropdown list pick 2 days
Choose dates for both dates
Add a location for both days
Choose time from the 'Start time' and 'End Time' dropdown list for the 1st day
Choose time from the 'End Time' dropdown list for the 2nd day. The 'Start time' field is empty.
Click on the 'Publish' button

Actual result
'Start Time' for the 2nd day is highlighted in red. User can`t create an event.

Expected result
'Start Time' for the 2nd day is highlighted in red. Error message "This field can’t be empty" appears below the empty 'Start Time' field. User can`t create an event.
User story and test case links
User story #4231
Test case GC-3173"

When 'Start Time' isn't chosen, it is highlighted in red, but the error message "This field can’t be empty" doesn't appear.

Doesn't reproduce

The bug is still reproduced.When 'Start Time' isn't chosen, it is highlighted in red, but the error message "This field can’t be empty" doesn't appear.


Events / Messages?

I think you mention somewhere that events are not needed in your library, I am new to ECS - can you show some example of how you handle communication between systems? Do events not help keep each system, behaviour without interdependencies?

Do events not help keep each system, behaviour without interdependencies?

Yes but most of time this is overkill.
Here is an example with communication between systems without event dispatcher.
const CollisionSystem = (em, explosionSystem) => {
  const collides = (a, b) => {
    // Check if box colliders overlap
    // ...
  }

  return () => {
    // Dummy collision check. Don't do this in a real game!
    const entities = em.query(Body, Collideable)

    for (let i = 0; i < entities.length; i++) {
      for (let j = i + 1; j < entities.length; j++) {
        if (collides(entities[i], entities[j])) {
          // Observer, kinda
          explosionSystem.onCollide(entities[i], entities[j])
        }
      }
    }
  }
}

const ExplosionSystem = () => {
  const collided = new Set()
  const update = () => {
    for (const entity of collided) {
      entity.destroy()

      // Emit particles ?
      // ...
    }

    collided.clear()
  }

  update.onCollide = (left, right) => {
    collided.add(left)
    collided.add(right)
  }

  return update
}

// Create entity manager
const em = makr(/* Your components */)

// Create systems
const explosionSystem = ExplosionSystem()
const collisionSystem = CollisionSystem(em, explosionSystem)

// Main loop
raf(() => {
  collisionSystem()
  explosionSystem()
})

I close the issue but feel free to continue the conversation!

That makes great sense passing in dependencies to the constructor, thanks! The recipes/docs is a bit sparse, maybe a demo app or links to apps made with makr would be good to give some tips on how to use the library, thanks.


Contains is NOT case sensitive [BUG]

At the extension level (where I have picked it up):
using the provided option Indicator Item Extension,
Contains Text
if you do not enter the text value as in the field, extension will not be activated.
EG
Contains Text "partner" will not display partner icon, but
Contains Text "Partner" will display icon.
Tested against Type on Account on dev org with values such as "Technology Partner"
IMHO not necessarily an issue as long as it is made crystal clear in the documentation - I am used to searching with contains being case sensitive on some platforms but for Indicators Jodie said the intent was for it to be case insensitive!
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Thanks for this!
We will have a fix in the works already (without realizing this bug) when we add support for other matching criteria

Equals
Does Not Equal
Starts With

For interested parties - the code is here where we will be converting to lowercase and then comparing (even for Equals, based on feedback from the Oct 2023 Chicago Sprint team) :
https://github.com/SFDO-Community/Salesforce-Indicators/blob/66778d074ca4123db35cb513170632438bfb7936/force-app/main/default/lwc/indicatorBundle/indicatorBundle.js#L215-L237


ChangeTip Backend

Support for Login with ChangeTip, including docs.
https://www.changetip.com/api

Merged. Thanks!
I've also made an small change, replaced the json.loads(urlopen(...)) with the get_json() helper method that simplifies the task.

Thanks omab! 1 high five @changetip

Thanks @omab! 1 high five @changetip

Hi @omab, I've delivered a Bitcoin tip worth 1 high five (22,228 bits/$5.00) from @gorillamania to your ChangeTip wallet.
Learn about ChangeTip


[info arch] Rework Tag in ProductMenu

This PR solves an issue where the Tag in ProductMenu causes the title to be too truncated:

Move the Tag above the title in ProductMenu
Add new small prop/variant to Tag that condenses the tag and removes the border. Is small a good prop name? Suggestions welcome!
Removes truncation from ProductMenu. We truncated this component to keep the ProductMenu content on one line because it lived in the TopbarSticker, but now the ProductMenu has lots of room to flow below.

Current
Proposed

How to test

Try out the /PageLayout "full" test case (npm start)
Try out the the /ProductMenu test cases (npm start)

QA checklist

[x] No errors logged to console.
[x] Accessibility score in Chrome DevTools Audit/Lighthouse is 100% with Lighthouse version: 6.2.0.
[x] Component is accessible at mobile-size viewport.
[x] Component is accessible at tablet-size viewport.
[x] Component is accessible at laptop-size viewport.
[x] Component is accessible at big-monitor-size viewport.
[x] Create a PR in a site repo, copy the component, and test it. Push to staging and let the reviewer know they can also test the component there.

@danswick ty! I just added some test cases to Themes to show off the new variant


Fix build warnings due to un-escaped single backslashes in strings

Quick fix for the current build warnings due to single backslashes in strings

Made the changes on my end


run_export without build/host does not makes sense

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

It looks like the 'damask' output doesn't have any tests.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender


Minerva configuration file for encryption key

Created minerva configuration files (conf/minerva.dist.cfg, conf/minerva.local.cfg), moved the crypto_key setting out of constants.py into the minerva.dist.cfg file, and added code to read in the configuration.
Also removed some duplicate code from the WmsProxy class.
@mgrauer This PR addresses https://github.com/Kitware/minerva/issues/131

Thanks @mbertrand, this LGTM.
I made two minor changes
* gitignoring and removing minerva.local.cfg and explaining the local vs dist in readme
* namespaced the config to minerva, to give it a bit of separation from the girder config

Do these seem ok to you?
I would like to test the encryption when creating a wms_source, but that would require us having a known endpoint that we can connect to from travis, with authentication.

@mgrauer those changes look good to me.  I will create a test for the encryption.

@mbertrand  I'm going to merge this PR.  Encryption testing can come in a separate PR.  That's probably what you intended anyway, rereading your comment.


How to select with like ???

Hello, I tried to add like param to the query as below, but it didn't work.
@Query( 'SELECT * Person WHERE name LIKE "%:key%"') --> key = "abc"
@Query( 'SELECT * Person WHERE name LIKE :key') --> key = "%abc%"
It threw an exception that cannot bind the argument key
However, it still work when I hard code by @Query( 'SELECT * Person WHERE name LIKE "%abc"')
Can you pls check it?

I tested this myself and your example works fine for me. Is there a chance you might have made a mistake in your code? Here is how I have implemented it:
PersonDao:
@Query('SELECT * FROM persons WHERE name LIKE :key')
Future<List<Person>> findPersonsByName(String key);

main.dart:
persons = widget.personDao.findPersonsByName('%${searchController.text}%');

Could you try this approach and see if it resolves the issue?

@Query('SELECT * FROM persons WHERE name LIKE '%:key%'')
Future<List<Person>> findPersonsByName(String key);

For this approach in SQLite you can't directly include the % wildcard characters inside the annotation of a query with bound parameters in the manner you've described.

It works. Thanks a lot


404 pages will not be displayed with fallback routes in config

Describe the bug
Vue.js app are served with 0.3.0 CLI.
When put the fallback routes in config, 404 page is not displayed.
Defined fallback routes following in  staticwebapp.config.json.
{
    "navigationFallback": {
        "rewrite": "/index.html",
        "exclude": ["/js/*.{js,map}", "/img/*.{png,jpg,gif}", "/css/*"]
    }
}

To Reproduce

Build the Vue application with npm run build
Run swa start ./dist
Enter the URL of a path that does not exist, for example, http://localhost:4280/abc.
You will see a screen with nothing rendered.

Expected behavior
404 page will be displayed.
Desktop (please complete the following information):

OS: Windows 10
Browser: Chrome
Version: 89.0.4389.114

Additional context
SWA CLI is 0.3.0 installed via npm

Thank you @k-miyake for creating this issue. it looks like this is a duplicate or related to #168 that I am already working on. Will keep you posted.

@k-miyake I tried your steps on a local Vue app and I can see my custom message. Can you share a screenshot of your issue?

btw, in my Vue router configuration, I've setup a custom 404 component:

export default new Router({
  mode: 'history',
  base: process.env.BASE_URL,
  routes: [
   ...
    {
      path: '*',
      component: PageNotFound,
    },
  ],
});

@manekinekko
My explanation may have been bad.
I wanted to know how to get the default 404 page of the SWA CLI to show up, not the custom 404 page not showing up.
If you remove the fallback setting, the SWA CLI's 404 page will be displayed.

@manekinekko
I realized that since it's an SPA, it's impossible to display the SWA 404 page as long as I set a fallback.
I'll wait for the #168 fix and use custom 404.
Thanks.

Fixed by https://github.com/Azure/static-web-apps-cli/pull/179. @k-miyake  can you confirm it's working for you as expected?

@manekinekko
I installed CLI from main branch, and the 404 page is displayed, but fallback does not work.


New annotate position and justification options

More a heads up that the annotation now has options for justify, x_offset, and y_offset. There's an MMAL_PARAMETER_CAMERA_ANNOTATE_V4_T structure that adds these in.

Thanks for the heads up!

Note to self: test repeated captures with coloured background on the v2 module (possible issue?)


[v2] Can't migrate REPv1->REPv2 if user changes allowance to less than their full balance

Describe the bug
Using Firefox and Metamask.
Migrating REP from v1 to v2 requires setting the allowance to the migration contract via approve(address,uint256) (1st tx), then calling migrateFromLegacyReputationToken() (2nd tx) - all available in the UI, using the button in the top right corner.
The user is warned of the fact this will require 2 transactions; however, if the user edits the approve() permission to something less than their full REPv1 balance, they'll never get the second transaction signing window in Metamask.
To Reproduce

Get REPv1 ("Account summary" tab on top -> "Legacy REP Faucet" button on bottom right).
Once tx is confirmed, a button will appear top-right: "Migrate V1 to V2 REP". Click it.
Take notice of the REPv1 balance - say it's 10. Click "Convert".
Click "Edit Permission" in Metamask, and set the "Custom Spend Limit" to something less than the balance above - say, 5. Confirm the tx and wait 'till it's mined.
Observe errors in console:

MetaMask - RPC Error: The execution failed due to an exception. (x5)
Error: "convertV1ToV2"

Expected behavior
At the very least, user is given the option to convert the amount they approved.
However, considering the function's implementation, the simplest "solution" here is to add a note that "only your entire balance can be migrated", and passing the exact amount in tx data to Metamask (so that the user is discouraged from editing it).
Screenshots
None.
Desktop (please complete the following information):

OS: Arch Linux
Browser: Firefox 72.0.2
Metamask: 7.7.4
Augur: whatever's currently served at https://v2.augur.net/

The dialog says it will migrate N rep, and doesn't mention that will will try to only migrate your manually approved balance or anything.
Thus I don't believe this is a bug but I'm okay with a text clarification saying it will migrate your total balance.

@petervecchiarelli @Chwy5 --
Your call on words to explain things to people. Do you agree it should somehow say that it will always attempt to do the full balance or do you think this is clear enough?

@pgebheim I think he is still referring to the old migrate modal design, the new one hasnt been added yet...see ticket 5237 (let me know if this helps with the issue).  As far as I am aware the user inputs the amount of Rep they wish to migrate


Embedded projection for Windows.ApplicationModel.AppService.AppServiceConnection.OpenAsync throws InvalidOperationException

Describe the bug
With CsWinRT 1.6.1 a .Net Standard 2.0 embedded projection for Windows.ApplicationModel.AppService.AppServiceConnection.OpenAsync can now be generated correctly and invokes the WinRT ABI successfully but fails to project the IAsyncOperation<AppServiceConnectionState> return value, instead throwing an InvalidOperationException with message 'Target type is not a projected type: AppServiceConnectionState'.
Stepping through the generated code the problem appears to be thatIAsyncOperation<T>has a static initializer of Marshaler<T> which calls TypeExtensions.GetHelperType(T) which expects to find a type called ABI.Windows.ApplicationModel.AppService.AppServiceConnectionState but ABI types are not generated for enums and so this returns null and causes the exception.
To Reproduce

Create an embedded .NetStandard2.0, Any CPU, library with a test method that calls 'AppServiceConnection m_appServiceConnection = new(); m_appServiceConnection.AppServiceName = "com.test1";          m_appServiceConnection.PackageFamilyName = "test1"; var result = await m_appServiceConnection.OpenAsync();
See Additional Context for the CsWinRTIncludes to make this build
Call the test method from a test app. It might be necessary to have another app installed that supports the requested AppServiceName/Package but I don't think this is required for the repro since it will fail returning the enum error value AppServiceConnectionState.AppServiceUnavailable.

Expected behavior
An awaitable object of type IAsyncOperation<AppServiceConnectionState> should be returned
Version Info
CsWinRT 1.6.1, VS2022, .NetStandard2.0, Unity 2020.3.27f, Win SDK 10.18362
Additional context
Note the use of Unity / Mono as the runtime test here, but this doesn't appear to be a factor in the code generation issue.
Required project config is;
  <PropertyGroup>     <CsWinRTIncludes>       Windows.ApplicationModel.AppInfo;       Windows.ApplicationModel.IAppInfo;       Windows.ApplicationModel.AppDisplayInfo;       Windows.ApplicationModel.IAppDisplayInfo;       Windows.ApplicationModel.AppService;       Windows.Data.Text.TextSegment;       Windows.Devices.Geolocation;       Windows.Foundation.Deferral;       Windows.Foundation.IDeferral;       Windows.Foundation.Metadata;       Windows.Foundation.UniversalApiContract;       Windows.Foundation.IAsyncOperation;       Windows.Foundation.TypedEventHandler;       Windows.Foundation.UniversalApiContract;       Windows.Foundation.FoundationContract;       Windows.Foundation.IAsyncInfo;       Windows.Foundation.IAsyncAction;       Windows.Foundation.AsyncStatus;       Windows.Foundation.AsyncActionCompletedHandler;       Windows.Foundation.AsyncActionProgressHandler;       Windows.Foundation.AsyncActionWithProgressCompletedHandler;       Windows.Foundation.AsyncOperationProgressHandler;       Windows.Foundation.AsyncOperationCompletedHandler;       Windows.Foundation.AsyncOperationWithProgressCompletedHandler;       Windows.Foundation.Collections;       Windows.Foundation.IStringable;       Windows.Foundation.MemoryBuffer;       Windows.Foundation.IMemoryBuffer;       Windows.Globalization.DayOfWeek;       Windows.Networking.Connectivity;       Windows.Networking.DomainNameType;       Windows.Networking.EndpointPair;       Windows.Networking.IEndpointPair;       Windows.Networking.HostName;       Windows.Networking.IHostName;       Windows.Security.Credentials.WebAccount;       Windows.Security.Credentials.IWebAccount;       Windows.Storage;       Windows.Storage.Streams.RandomAccessStreamReference;       Windows.Storage.Streams.IRandomAccessStreamReference;       Windows.Storage.Streams.IRandomAccessStream       Windows.Storage.Streams.IBuffer;       Windows.Storage.Streams.InputStreamOptions;       Windows.Storage.Streams.IInputStream;       Windows.Storage.Streams.IOutputStream;       Windows.System.RemoteSystems;       Windows.System.IUser;       Windows.System.User;     </CsWinRTIncludes>   </PropertyGroup>

One quick follow up on this; although I didn't explicitly call this out in the original bug report, given the way in which the generated code is failing it seems likely that any WinRT asynchronous method that returns just an enum value will fail in the same way.


Fix checkbox array and radio primitives

closes #1382
The unchecked value caused a little headache, but hopefully this is ok.

@VividLemon do you see any problems with this one?

https://stackblitz.com/edit/vitejs-vite-pqd3b7?file=src%2FApp.vue
A demo using this build


Add remember option to registration

Following #312
On registration, in case the automatic Activation is ON or the settings do not require activation, shouldn't we add the remember option in the registration as well? So we don't get the persistent session by default in the first login?

@bernardotavares What do you propose will happen if the "Remember login mode" setting is set to "Ask", as there is currently no field in the registration form to ask them if they wish to set up a "remembered" session. Should we assume that it's not a remembered session for registration?

Yes I agree with that. Asking about the session in the registration form its a bit uncommon right? And a non-persistent session by default seems like the best practice security-wise.

Fixed v1.5.5


Many tests failing with TypeError: Unsupported type as file input: <class '_io.BytesIO'>

Appears to have been introduced in https://github.com/wagtail/Willow/commit/084a112aac21af97d0924c9447c739722cd4539e, which replaced imghdr with filetype. filetype does not handle BytesIO as input.
Opening this to track the issue, I've also opened https://github.com/h2non/filetype.py/issues/140 and will submit a patch if filetype maintainers are into it.

Fixed in #101


UPDATE test cases from problem specifications for prime-factors

Updated all the test cases including new ones added
Regenerated test.toml with configlet
Configlet test says all filepaths, metadata, and tests for prime-factors are up to date

Missed some semicolons and formatting will fix that right away

The issue is specifically with the last test case, and I am unsure as per what to do with this, because the number is a long and the test cases need to be int from my understanding

The clang fails up because the number ends up to be some negative number

According to the test.toml, the "large prime" test is not new. That might have been a mistake, as you are the one who included the test just now.
I see three options:

skipping the test, as it does not fit the current status quo. The old example solution is for int type, thus, it would not allow such a big number. This has the advantage that old solutions are still valid.
adding the test, but changing the number to something below 2^31. This would be a "big number", but I am not sure it is in the spirit of the exercise.
changing the example solution from int to long. This would allow us to keep to the exercise spec, but old solutions might become invalid.

I prefer option 3. Number 2 is "more of the same" as the other test.
Do you have an opinion @siebenschlaefer @ErikSchierboom?

The issue is specifically with the last test case, and I am unsure as per what to do with this, because the number is a long and the test cases need to be int from my understanding.

I don't think that int is somehow required by the instructions or the tests.
To be able to implement this test with the 37-bit number<PHONE_NUMBER>1 we could change to long long or std::int64_t.
But the real problem is that it would invalidate all existing solutions when we change the expected result from std::vector<int> to std::vector<long long>.

I see three options: [...]

I agree.
I think option three is the best one in the long run because we can implement all tests without deviating from the problem specification.
If we don't want to invalidate old solutions I would vote for option two with something like 11 * 13901 * 14033 ==<PHONE_NUMBER> because that's at least somewhat large.

If we don't want to invalidate old solutions

That would touch ~1300 solutions. I could live with that, the fix is easy for everyone who understands the widening from int to long long. So if they want to fix it, it would not cost them a lot of time.

Well if it is good with long long, I can work on updating the test cases to rather support long long instead of int, Because adding more test cases in this problem and we would encounter this problem sooner or later.

Well if it is good with long long, I can work on updating the test cases to rather support long long instead of int, Because adding more test cases in this problem and we would encounter this problem sooner or later.

You would also need to update the source and header files accordingly in the .meta directory. Is that okay?

Well if it is good with long long, I can work on updating the test cases to rather support long long instead of int, Because adding more test cases in this problem and we would encounter this problem sooner or later.

You would also need to update the source and header files accordingly in the .meta directory. Is that okay?

Yup, seems good! I see the examples use int too, I'll update that. I think it could work as a clear example of what's been changed.

I'm fine with option 3, just as long as the PR contains [no important files changed] in the commit message to prevent re-testing of all the existing solutions. See https://exercism.org/docs/building/tracks#h-avoiding-triggering-unnecessary-test-runs


Docker documentation missing for new Config and HostConfig fields in Docker Remote API

Looking through the documentation for the Docker Remote API v1.22 and v1.23, I don’t see any mention of the following fields which were added to the [Config](https://github.com/docker/engine-api/blob/release/1.11/types/container/conf... ... ) and [HostConfig](https://github.com/docker/engine-api/blob/release/1.11/types/container/host... ... ) types in docker/engine-api from version [1.10]
(https://github.com/docker/engine-api/tree/release/1.10/types/container ) to 1.11.

[ArgsEscaped - Config](https://github.com/docker/engine-api/blob/release/1.11/types/container/conf... ... )
[AutoRemove - HostConfig](https://github.com/docker/engine-api/blob/release/1.11/types/container/host... ... )
[Cgroup - HostConfig](https://github.com/docker/engine-api/blob/release/1.11/types/container/host... ... )

I'd like to make a contribution, but I'm not sure how/if these fields are supported; I'd like to get someone to chime in on this. If the information is provided I can file the PR to update the docs.

@juanrhenals autoremove and args escaped are not being used by Docker yet.

This as been addressed and is now documented at https://docs.docker.com/engine/api/v1.41/#tag/Container/operation/ContainerInspect


Project import generated by Copybara.

GitOrigin-RevId: 81d36f76344f2948e8a105a1413688359c952496

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[GEN-1927]: add a Cypress test for onboarding-flow

This pull request includes several changes to improve the identification of elements in the frontend, update Cypress configuration, and enhance Cypress tests. The most important changes are listed below:
Improved identification of elements:

frontend/webapp/containers/main/destinations/destination-modal/choose-destination-body/destinations-list/destination-list-item/index.tsx: Added id attribute to ListItem for better identification of destination items.
frontend/webapp/containers/main/destinations/destination-modal/choose-destination-body/destinations-list/index.tsx: Changed key attribute of DestinationListItem to use item.type instead of item.displayName.
frontend/webapp/containers/main/sources/choose-sources/choose-sources-body/choose-sources-body-fast/sources-list/index.tsx: Added id attribute to Group for better identification of namespace items.
frontend/webapp/reuseable-components/no-data-found/index.tsx: Added id attribute to Container for better identification of "No data found" component.

Cypress configuration and tests:

frontend/webapp/cypress.config.ts: Updated Cypress configuration to use a dynamic BASE_URL based on the PORT variable.
frontend/webapp/cypress/e2e/connection.cy.ts: Added a new test to check the root connection and confirm frontend and backend connections using GraphQL.
frontend/webapp/cypress/e2e/onboarding.cy.ts: Updated onboarding tests to include checks for the existence of a "default" namespace and a "Jaeger" destination, and to verify the user can complete the onboarding process.

WIP - struggling to get namespaces in GitHub environment


only/not-simplepdf directive

As SimplePDF is using HTML, it may be hard to tell Sphinx to not render specific elements, which would not be nice-looking in PDF.
E.g. grids, tabs, videos and so on.
So there shall be 2 new directives, which are able to provide their content only for specific builders:

only-simplepdf: Adds content only if simplepdf builder is used
not-simplepdf:  Adds content only if *not *simplepdf builder is used.

done by the if-builder directive


6502: SBC instruction carry/borrow handling is incorrect

Describe the bug
Ghidra incorrectly handles the carry flag when decompiling an 'SBC' instruction on the 6502 processor.
To Reproduce
Steps to reproduce the behavior:

Disassemble and decompile any code which uses the 6502 "SBC" instruction preceded by a "SEC" (set carry) instruction.
On a 6502 SEC + SBC results in a direct subtract from the accumulator.
Note that the value Ghidra shows (in the decompilation) for the subtraction is one less than it should be.

For example:
   LDA #$34
   SEC
   SBC #$12

Should result in #$12 being subtracted from the A register (initialised to #$34) -- giving #$22 after execution on a real 6502.
Ghidra's decompilation shows that #$13 is being subtracted, which leaves A-reg with an incorrect value.
References showing correct behaviour:

https://wiki.cdot.senecacollege.ca/wiki/6502_Math
http://www.righto.com/2012/12/the-6502-overflow-flag-explained.html

The dreaded add-with-carry and subtract-with-borrow instructions. We've found several errors in them in recent months, but this one is definitely the most egregious because it will always be wrong. I'll take a look. Thanks @philpem


Rewrite/Migration 👷 🚗 (WIP)

Please don't merge this yet, as this is a work in progress

[ ] Add initial browser tests
[ ] Rewrite
[ ] Create different node and browser builds

This is far from being finished. I changed the title of this pr to make it more accurate.

What's the status of this PR? Is there a plan to merge it?

I've been held back by other projects. Haven't had time to look into this project a lot anymore. But when JS gets multithreading primitives, I will be sure to look into this PR rewrite this entire project. Also doesn't have any real tests so its hard for us to find out if this works or not

Wow - when are multithreaded primitives expected?

Sorry, didn't mean to make you google something that I can google.
https://hacks.mozilla.org/2016/05/a-taste-of-javascripts-new-parallel-primitives/
I read that article about a year ago, but I haven't heard we were close to getting it (or Babel being able to polyfill it). When I read your response I got the impression it was imminent.

ES2018 I think. They're stage 4 I think

Cant find it on the proposals page but here's a short discussion between a tc39 member and I


Using vim.eval to eval a variable value will fail the first time.

Steps to reproduce:
Create a plugin like so and name it foo.py or whatever you want to call it:
import neovim

@neovim.plugin
class Foo(object):
    def __init__(self, vim):
        self.vim = vim

    @neovim.command('TestFoo', sync=True, nargs=1)
    def foo_test(self, args):
        foovar = self.vim.eval(args[0])
        self.vim.command("echom 'result %s'" % foovar)

Update plugins:
nvim -c 'UpdateRemotePlugins' -c 'q'

Start neovim.
$  nvim

Set a variable on the input prompt:
:let foo = 'bar'

Verify it is set:
:echom foo

That should echo "bar" to :messages
Now try the plugin:
:TestFoo foo

This will show an error like so:
Error detected while processing function remote#define#CommandBootstrap:
line    5:
NvimError('Vim:E121: Undefined variable: foo',)

Try it again.
:TestFoo foo

See that it works:
result bar

I have followed vim_eval.c all the way down to eval7 and find_var with lldb and it's definitely trying to find the variable, but it just doesn't find it, it's not where it's looking. It creates a hash from the variable name, which looks like it's just an integer and sees if it's in a hash table and it isn't there.  nvim can find it from the input prompt, but the plugin can't until after the first failure.

right, always use scopes with eval()


The entities are missing in UmlsEntityLinker

Hi,
I have a biomedical medical text document and trying to extract medical concepts out of it. There are medical terms like "transient ischemic attack, aortic dissection," are detected using "display_entities" function. When I perform "unified_medical_language_entity_linker" they are not resulting as an entity, Concept_Id, Score. What are the parameters to be fined to get in UMLSLinker.
I am using "en_core_sci_md" model.

The entity linker is quite naive, so it may not link all of your entities that are extracted. You can play around with some of the linker parameters here: https://github.com/allenai/scispacy#umlsentitylinker-alpha-feature
You might want to try lowering the thresholds for the score at which an entity is linked - be aware that this will probably increase your false positives also.

Yes, I tried same and faced false positive as you said.
By the way, is there any way to find negations using this.

Not in scispacy. I haven't used this package myself, but I have seen it used in a couple place, might be worth checking out: https://github.com/jenojp/negspacy

@danielkingai2 Thanks,  negspacy worked for me.
Can I gent information which method was used for text matching? like levenshtein distance (fuzzy ratio, partial, or any other) -- ShouldI open new issue for this different question?

The details are described in the paper (https://www.semanticscholar.org/paper/ScispaCy%3A-Fast-and-Robust-Models-for-Biomedical-Neumann-King/de28ec1d7bd38c8fc4e8ac59b6133800818b4e29) in section 5. It is an approximate nearest neighbors search over tfidf character 3-grams.

Thanks for the article.
How do we print "Canonical Name"? as it shows in here https://scispacy.apps.allenai.org/

print(linker.umls.cui_to_entity[concept_id]) all the entity attributes can be found on the entity objects in linker.umls.cui_to_entity. I'd encourage you to read through the README, as there is lots of good information in there.


fix: add max number of concurrent calls allowed for the C method configuration item

Codecov Report
Attention: Patch coverage is 92.85714% with 9 lines in your changes missing coverage. Please review.

Project coverage is 64.63%. Comparing base (de3691f) to head (8b97b79).

Files with missing lines
Patch %
Lines

db/async/row.go
73.91%
5 Missing and 1 partial :warning:

controller/ws/query/ws.go
66.66%
2 Missing :warning:

controller/ws/tmq/tmq.go
66.66%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #354      +/-   ##
==========================================
- Coverage   69.29%   64.63%   -4.66%
==========================================
  Files          88      105      +17
  Lines       11245    13908    +2663
==========================================
+ Hits         7792     8990    +1198
- Misses       2721     4119    +1398
- Partials      732      799      +67

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


In the tutorials, the colcon build tutorial is about 1/2 the intermediate tutorial while the colcon build process is used near the start of the biginners tutorials

In the tutorials, the colcon build tutorial is about 1/2 down the intermediate tutorials while the colcon build process is used in creating your first ROS2 package at the start of the beginner's tutorials.
If the intention is for the tutorials to flow in order colcon build should be moved to just after creating your first ROS 2 package.

We ended up revamping this when we revamped the full tutorials, and colcon is now right at the beginning of the Client Library tutorials: http://docs.ros.org/en/rolling/Tutorials/Beginner-Client-Libraries.html
With that, I'm going to close this out.  Thanks for the issue.


Add KeyVault encryption to DataProtection

ProtectKeysWithAzureKeyVault
https://github.com/aspnet/DataProtection/pull/273
Probably for Configuring Data Protection in ASP.NET Core

Copy from @blowdart  dup #5467
KeyVault key wrapping will come in 2.1
Data Protection documentation needs updating to describe this and a simpler, recipe type page should be created to explain to people what they'd use in what circumstances.


Add Python binomial test

Draft PR to add Python binomial test - I think we'll need to update requirements.txt as well.
We could also add guidance around how to update requirements.txt.

Looks like the build failure might be down to a scipy version issue.
In the requirments.txt scipy is at version 1.13.0, and from looking online it looks like the binom_test module was refactored in version 1.12.0.

In the end I removed the additional dependency which was needed for the dataset and just used the CSV file instead!