Django stubs completely broken after upgrade to 2022.4.0

Environment data

Language Server version: 2022.4.0
OS and version: Linux Mint 20.2 (reproduced on Ubuntu 20.04 also)
Python version (& distribution if applicable, e.g. Anaconda): 3.10.4
Pylance with "basic" mode

Expected behavior
Django stubs were updated in new version 2022.4.0. I expected at least the same as in 2022.3.4. They were not perfect, right, but now it yields about hundreds of type errors, most of them without. My project (in last version) had 0 issues on "basic" mode (therefore I can easily see a difference). So it should after upgrade, or difference should not be big.
After updating stubs, i would expect BETTER type, autocompletion etc. support and smarter detection of django specifix syntax, but obviously we have regression.
Actual behavior
574 type  issues from pylance after upgrade, there are so many cases i won't address every of them.

Weird type of every model field, this is just broken

django.test.Client inside TestCase broken, no methods url, context etc

form instance fields attribute is now Field, but not have attrs that are appended magically

No color for some of models fields

Accessing foreign key field and then its attributes now yields errors, it used to be (better i think) Unknown

Logs

[Info  - 8:56:42 PM] (1770211) No configuration file found.
[Info  - 8:56:42 PM] (1770211) pyproject.toml file found at /home/rafsaf/projects/Tribal-Wars-Planer.
[Info  - 8:56:42 PM] (1770211) Setting pythonPath for service "Tribal-Wars-Planer": "/home/rafsaf/.cache/pypoetry/virtualenvs/tribal-wars-planer-vh1zxFkQ-py3.10/bin/python"
[Info  - 8:56:42 PM] (1770211) Loading pyproject.toml file at /home/rafsaf/projects/Tribal-Wars-Planer/pyproject.toml
[Error - 8:56:42 PM] (1770211) Pyproject file "/home/rafsaf/projects/Tribal-Wars-Planer/pyproject.toml" is missing "[tool.pyright]" section.
[Warn  - 8:56:42 PM] (1770211) stubPath /home/rafsaf/projects/Tribal-Wars-Planer/typings is not a valid directory.
[Info  - 8:56:42 PM] (1770211) Assuming Python version 3.10
[Info  - 8:56:42 PM] (1770211) Assuming Python platform Linux
[Info  - 8:56:42 PM] (1770211) Search paths for /home/rafsaf/projects/Tribal-Wars-Planer
[Info  - 8:56:42 PM] (1770211)   /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/typeshed-fallback/stdlib
[Info  - 8:56:42 PM] (1770211)   /home/rafsaf/projects/Tribal-Wars-Planer
[Info  - 8:56:42 PM] (1770211)   /home/rafsaf/projects/Tribal-Wars-Planer/typings
[Info  - 8:56:42 PM] (1770211)   /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/typeshed-fallback/stubs/...
[Info  - 8:56:42 PM] (1770211)   /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/bundled/stubs
[Info  - 8:56:42 PM] (1770211)   /usr/lib/python3.10
[Info  - 8:56:42 PM] (1770211)   /usr/lib/python3.10/lib-dynload
[Info  - 8:56:42 PM] (1770211)   /home/rafsaf/.cache/pypoetry/virtualenvs/tribal-wars-planer-vh1zxFkQ-py3.10/lib/python3.10/site-packages
[Info  - 8:56:42 PM] (1770211)   /home/rafsaf/projects/Tribal-Wars-Planer
[Info  - 8:56:42 PM] (1770211) Adding fs watcher for library directories:
 /usr/lib/python3.10
/usr/lib/python3.10/lib-dynload
/home/rafsaf/.cache/pypoetry/virtualenvs/tribal-wars-planer-vh1zxFkQ-py3.10/lib/python3.10/site-packages
[Info  - 8:56:42 PM] (1770211) Adding fs watcher for directories:
 /home/rafsaf/projects/Tribal-Wars-Planer
[Info  - 8:56:42 PM] (1770211) Searching for source files
[Info  - 8:56:42 PM] (1770211) Found 237 source files
(1770211) Background analysis message: setConfigOptions
(1770211) Background analysis message: setImportResolver
(1770211) Background analysis message: ensurePartialStubPackages
(1770211) Background analysis message: setTrackedFiles
(1770211) Background analysis message: markAllFilesDirty
[Info  - 8:56:42 PM] (1770211) SourceFile: Received fs event 'change' for path '/home/rafsaf/projects/Tribal-Wars-Planer/.vscode/settings.json'
[Info  - 8:56:42 PM] (1770211) SourceFile: Received fs event 'change' for path '/home/rafsaf/projects/Tribal-Wars-Planer/.vscode/settings.json'
[Info  - 8:56:42 PM] (1770211) SourceFile: Received fs event 'change' for path '/home/rafsaf/projects/Tribal-Wars-Planer/.vscode/settings.json'
(1770211) Background analysis message: getSemanticTokens delta
(1770211) [BG(1)] getSemanticTokens delta previousResultId:1649703254362 at /home/rafsaf/projects/Tribal-Wars-Planer/utils/basic/dictionary.py ...
(1770211) [BG(1)]   parsing: /home/rafsaf/projects/Tribal-Wars-Planer/utils/basic/dictionary.py (72ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 0ms] (131ms)
(1770211) [BG(1)]   binding: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/typeshed-fallback/stdlib/builtins.pyi (20ms)
(1770211) [BG(1)]   binding: /home/rafsaf/projects/Tribal-Wars-Planer/utils/basic/dictionary.py (1ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 1ms] (6ms)
(1770211) [BG(1)]   binding: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/typeshed-fallback/stdlib/typing_extensions.pyi (1ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/typeshed-fallback/stdlib/typing.pyi [fs read 0ms] (79ms)
(1770211) [BG(1)]   binding: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/typeshed-fallback/stdlib/typing.pyi (21ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 1ms] (18ms)
(1770211) [BG(1)]   binding: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (4ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/typeshed-fallback/stdlib/types.pyi [fs read 0ms] (21ms)
(1770211) [BG(1)]   binding: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/typeshed-fallback/stdlib/types.pyi (10ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/typeshed-fallback/stdlib/abc.pyi [fs read 1ms] (2ms)
(1770211) [BG(1)]   binding: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/typeshed-fallback/stdlib/abc.pyi (1ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/bundled/stubs/django/db/models/query.pyi [fs read 0ms] (13ms)
(1770211) [BG(1)]   binding: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/bundled/stubs/django/db/models/query.pyi (1ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/projects/Tribal-Wars-Planer/base/models/__init__.py [fs read 1ms] (2ms)
(1770211) [BG(1)]   binding: /home/rafsaf/projects/Tribal-Wars-Planer/base/models/__init__.py (0ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/projects/Tribal-Wars-Planer/base/models/outline.py [fs read 0ms] (25ms)
(1770211) [BG(1)]   binding: /home/rafsaf/projects/Tribal-Wars-Planer/base/models/outline.py (8ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/bundled/stubs/django/db/__init__.pyi [fs read 1ms] (4ms)
(1770211) [BG(1)]   binding: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/bundled/stubs/django/db/__init__.pyi (0ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/bundled/stubs/django/db/models/__init__.pyi [fs read 0ms] (13ms)
(1770211) [BG(1)]   binding: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/bundled/stubs/django/db/models/__init__.pyi (2ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/bundled/stubs/django/db/models/base.pyi [fs read 0ms] (14ms)
(1770211) [BG(1)]   binding: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/bundled/stubs/django/db/models/base.pyi (1ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/projects/Tribal-Wars-Planer/base/models/player.py [fs read 0ms] (4ms)
(1770211) [BG(1)]   binding: /home/rafsaf/projects/Tribal-Wars-Planer/base/models/player.py (0ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/projects/Tribal-Wars-Planer/base/models/village_model.py [fs read 0ms] (2ms)
(1770211) [BG(1)]   binding: /home/rafsaf/projects/Tribal-Wars-Planer/base/models/village_model.py (0ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/projects/Tribal-Wars-Planer/base/models/world.py [fs read 0ms] (4ms)
(1770211) [BG(1)]   binding: /home/rafsaf/projects/Tribal-Wars-Planer/base/models/world.py (0ms)
(1770211) [BG(1)]   parsing: /home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/bundled/stubs/django/db/models/manager.pyi [fs read 0ms] (9ms)
[Info  - 8:56:43 PM] (1770211) Could not import 'django_stubs_ext' in file '/home/rafsaf/.vscode/extensions/ms-python.vscode-pylance-2022.4.0/dist/bundled/stubs/django/db/models/manager.pyi'
[Info  - 8:56:43 PM] (1770211)   Looking in stubPath '/home/rafsaf/projects/Tribal-Wars-Planer/typings'
[Info  - 8:56:43 PM] (1770211)   Attempting to resolve stub package using root path '/home/rafsaf/projects/Tribal-Wars-Planer/typings'
[Info  - 8:56:43 PM] (1770211)   Attempting to resolve using root path '/home/rafsaf/projects/Tribal-Wars-Planer/typings'
[Info  - 8:56:43 PM] (1770211)   Looking in root directory of execution environment '/home/rafsaf/projects/Tribal-Wars-Planer'
[Info  - 8:56:43 PM] (1770211)   Attempting to resolve stub package using root path '/home/rafsaf/projects/Tribal-Wars-Planer'
[Info  - 8:56:43 PM] (1770211)   Attempting to resolve using root path '/home/rafsaf/projects/Tribal-Wars-Planer'
[Info  - 8:56:43 PM] (1770211)   Looking in python search path '/usr/lib/python3.10'
[Info  - 8:56:43 PM] (1770211)   Attempting to resolve stub package using root path '/usr/lib/python3.10'
[Info  - 8:56:43 PM] (1770211)   Attempting to resolve using root path '/usr/lib/python3.10'
[Info  - 8:56:43 PM] (1770211)   Looking in python search path '/usr/lib/python3.10/lib-dynload'
[Info  - 8:56:43 PM] (1770211)   Attempting to resolve stub package using root path '/usr/lib/python3.10/lib-dynload'
[Info  - 8:56:43 PM] (1770211)   Attempting to resolve using root path '/usr/lib/python3.10/lib-dynload'
[Info  - 8:56:43 PM] (1770211)   Looking in python search path '/home/rafsaf/.cache/pypoetry/virtualenvs/tribal-wars-planer-vh1zxFkQ-py3.10/lib/python3.10/site-packages'
[Info  - 8:56:43 PM] (1770211)   Attempting to resolve stub package using root path '/home/rafsaf/.cache/pypoetry/virtualenvs/tribal-wars-planer-vh1zxFkQ-py3.10/lib/python3.10/site-packages'
[Info  - 8:56:43 PM] (1770211)   Attempting to resolve using root path '/home/rafsaf/.cache/pypoetry/virtualenvs/tribal-wars-planer-vh1zxFkQ-py3.10/lib/python3.10/site-packages'

Code Snippet / Additional information

Downgrade to 2022.3.4 (30 March 2022) and stopping auto upgrading to latest version solves the issues

Update should be out wed. thanks

if you go declaration on your field types it should take you to our bundled stubs. You can try replacing django/db/models/fields/__init__.py with this below
import decimal
import sys
import uuid
from datetime import date
from datetime import datetime as real_datetime
from datetime import time, timedelta
from typing import (
    Any,
    Callable,
    Dict,
    Generic,
    Iterable,
    List,
    Optional,
    Sequence,
    Tuple,
    Type,
    TypeVar,
    Union,
    overload,
)

from django.core import validators  # due to weird mypy.stubtest error
from django.core.checks import CheckMessage
from django.core.exceptions import FieldDoesNotExist as FieldDoesNotExist
from django.db.backends.base.base import BaseDatabaseWrapper
from django.db.models import Model
from django.db.models.expressions import Col, Combinable
from django.db.models.fields.reverse_related import ForeignObjectRel
from django.db.models.query_utils import Q, RegisterLookupMixin
from django.forms import Field as FormField
from django.forms import Widget
from django.utils.datastructures import DictWrapper
from django.utils.functional import _Getter

if sys.version_info < (3, 8):
    from typing_extensions import Protocol
else:
    from typing import Protocol

class Empty: ...
class NOT_PROVIDED: ...

BLANK_CHOICE_DASH: List[Tuple[str, str]] = ...

_Choice = Tuple[Any, Any]
_ChoiceNamedGroup = Tuple[str, Iterable[_Choice]]
_FieldChoices = Iterable[Union[_Choice, _ChoiceNamedGroup]]
_ChoicesList = List[Union[_Choice, _ChoiceNamedGroup]]
_LimitChoicesTo = Union[Q, Dict[str, Any]]

class _ChoicesCallable(Protocol):
    def __call__(self) -> _FieldChoices: ...

_AllLimitChoicesTo = Union[_LimitChoicesTo, _ChoicesCallable]
_ErrorMessagesT = Dict[str, Any]

_T = TypeVar("_T", bound="Field")
# __set__ value type
_ST = TypeVar("_ST", contravariant=True)
# __get__ return type
_GT = TypeVar("_GT", covariant=True)

class Field(RegisterLookupMixin, Generic[_ST, _GT]):
    """
    Typing model fields.

    How does this work?
    Let's take a look at the self-contained example
    (it is way easier than our django implementation, but has the same concept).

    To understand this example you need:
    1. Be familiar with descriptors: https://docs.python.org/3/howto/descriptor.html
    2. Follow our explanation bellow

    Let's start with defining our fake model class and fake integer field.

    .. code:: python

        from typing import Generic, Union

        class Model(object):
            ...

        _SetType = Union[int, float]  # You can assign ints and floats
        _GetType = int  # access type is always `int`

        class IntField(object):
            def __get__(self, instance: Model, owner) -> _GetType:
                ...

            def __set__(self, instance, value: _SetType) -> None:
                ...

    Now, let's create our own example model,
    this would be something like ``User`` in your own apps:

    .. code:: python

        class Example(Model):
            count = IntField()

    And now, lets test that our reveal type works:

    .. code:: python

        example = Example()
        reveal_type(example.count)
        # Revealed type is "builtins.int"

        example.count = 1.5  # ok
        example.count = 'a'
        # Incompatible types in assignment
        # (expression has type "str", variable has type "Union[int, float]")

    Notice, that this is not magic. This is how descriptors work with ``mypy``.

    We also need ``_pyi_private_set_type`` attributes
    and friends to help inside our plugin.
    It is required to enhance parts like ``filter`` queries.
    """

    _pyi_private_set_type: Any
    _pyi_private_get_type: Any
    _pyi_lookup_exact_type: Any

    widget: Widget
    help_text: str
    attname: str
    auto_created: bool
    primary_key: bool
    remote_field: Optional[ForeignObjectRel]
    is_relation: bool
    related_model: Optional[Type[Model]]
    one_to_many: Optional[bool] = ...
    one_to_one: Optional[bool] = ...
    many_to_many: Optional[bool] = ...
    many_to_one: Optional[bool] = ...
    max_length: Optional[int]
    model: Type[Model]
    name: str
    verbose_name: str
    description: Union[str, _Getter[str]]
    blank: bool
    null: bool
    editable: bool
    empty_strings_allowed: bool = ...
    choices: Optional[_ChoicesList] = ...
    db_column: Optional[str]
    column: str
    concrete: bool
    default: Any
    error_messages: _ErrorMessagesT
    empty_values: Sequence[Any] = ...
    creation_counter: int
    auto_creation_counter: int
    default_validators: Sequence[validators._ValidatorCallable]
    default_error_messages: Dict[str, str]
    hidden: bool
    system_check_removed_details: Optional[Any]
    system_check_deprecated_details: Optional[Any]
    def __init__(
        self,
        verbose_name: Optional[str] = ...,
        name: Optional[str] = ...,
        primary_key: bool = ...,
        max_length: Optional[int] = ...,
        unique: bool = ...,
        blank: bool = ...,
        null: bool = ...,
        db_index: bool = ...,
        rel: Optional[ForeignObjectRel] = ...,
        default: Any = ...,
        editable: bool = ...,
        serialize: bool = ...,
        unique_for_date: Optional[str] = ...,
        unique_for_month: Optional[str] = ...,
        unique_for_year: Optional[str] = ...,
        choices: Optional[_FieldChoices] = ...,
        help_text: str = ...,
        db_column: Optional[str] = ...,
        db_tablespace: Optional[str] = ...,
        auto_created: bool = ...,
        validators: Iterable[validators._ValidatorCallable] = ...,
        error_messages: Optional[_ErrorMessagesT] = ...,
    ): ...
    def __set__(self, instance, value: _ST) -> None: ...
    # class access
    @overload
    def __get__(self: _T, instance: None, owner) -> _T: ...
    # Model instance access
    @overload
    def __get__(self, instance: Model, owner) -> _GT: ...
    # non-Model instances
    @overload
    def __get__(self: _T, instance, owner) -> _T: ...
    def deconstruct(self) -> Any: ...
    def set_attributes_from_name(self, name: str) -> None: ...
    def db_type_parameters(self, connection: BaseDatabaseWrapper) -> DictWrapper: ...
    def db_check(self, connection: BaseDatabaseWrapper) -> Optional[str]: ...
    def db_type(self, connection: BaseDatabaseWrapper) -> Optional[str]: ...
    def db_parameters(self, connection: BaseDatabaseWrapper) -> Dict[str, Optional[str]]: ...
    def pre_save(self, model_instance: Model, add: bool) -> Any: ...
    def get_prep_value(self, value: Any) -> Any: ...
    def get_db_prep_value(self, value: Any, connection: BaseDatabaseWrapper, prepared: bool = ...) -> Any: ...
    def get_db_prep_save(self, value: Any, connection: BaseDatabaseWrapper) -> Any: ...
    def get_internal_type(self) -> str: ...
    # TODO: plugin support
    def formfield(self, form_class: Optional[Any] = ..., choices_form_class: Optional[Any] = ..., **kwargs) -> Any: ...
    def save_form_data(self, instance: Model, data: Any) -> None: ...
    def contribute_to_class(self, cls: Type[Model], name: str, private_only: bool = ...) -> None: ...
    def to_python(self, value: Any) -> Any: ...
    @property
    def validators(self) -> List[validators._ValidatorCallable]: ...
    def run_validators(self, value: Any) -> None: ...
    def validate(self, value: Any, model_instance: Optional[Model]) -> None: ...
    def clean(self, value: Any, model_instance: Optional[Model]) -> Any: ...
    def get_choices(
        self,
        include_blank: bool = ...,
        blank_choice: _ChoicesList = ...,
        limit_choices_to: Optional[_LimitChoicesTo] = ...,
        ordering: Sequence[str] = ...,
    ) -> _ChoicesList: ...
    def has_default(self) -> bool: ...
    def get_default(self) -> Any: ...
    def check(self, **kwargs: Any) -> List[CheckMessage]: ...
    def get_col(self, alias: str, output_field: Optional[Field] = ...) -> Col: ...
    @property
    def cached_col(self) -> Col: ...
    def value_from_object(self, obj: Model) -> _GT: ...
    def get_attname(self) -> str: ...
    def value_to_string(self, obj: Model) -> str: ...

class IntegerField(Field[Union[float, int, str, Combinable], int]):
    _pyi_private_set_type: Union[float, int, str, Combinable]
    _pyi_private_get_type: int
    _pyi_lookup_exact_type: Union[str, int]

class PositiveIntegerRelDbTypeMixin:
    def rel_db_type(self, connection: BaseDatabaseWrapper) -> str: ...

class PositiveIntegerField(PositiveIntegerRelDbTypeMixin, IntegerField): ...
class PositiveSmallIntegerField(PositiveIntegerRelDbTypeMixin, SmallIntegerField): ...
class PositiveBigIntegerField(PositiveIntegerRelDbTypeMixin, BigIntegerField): ...
class SmallIntegerField(IntegerField): ...
class BigIntegerField(IntegerField): ...

class FloatField(Field[Union[float, int, str, Combinable], float]):
    _pyi_private_set_type: Union[float, int, str, Combinable]
    _pyi_private_get_type: float
    _pyi_lookup_exact_type: float

class DecimalField(Field[Union[str, float, decimal.Decimal, Combinable], decimal.Decimal]):
    _pyi_private_set_type: Union[str, float, decimal.Decimal, Combinable]
    _pyi_private_get_type: decimal.Decimal
    _pyi_lookup_exact_type: Union[str, decimal.Decimal]
    # attributes
    max_digits: int = ...
    decimal_places: int = ...
    def __init__(
        self,
        verbose_name: Optional[str] = ...,
        name: Optional[str] = ...,
        max_digits: Optional[int] = ...,
        decimal_places: Optional[int] = ...,
        *,
        primary_key: bool = ...,
        unique: bool = ...,
        blank: bool = ...,
        null: bool = ...,
        db_index: bool = ...,
        default: Any = ...,
        editable: bool = ...,
        auto_created: bool = ...,
        serialize: bool = ...,
        choices: Optional[_FieldChoices] = ...,
        help_text: str = ...,
        db_column: Optional[str] = ...,
        db_tablespace: Optional[str] = ...,
        validators: Iterable[validators._ValidatorCallable] = ...,
        error_messages: Optional[_ErrorMessagesT] = ...,
    ): ...

class CharField(Field[Union[str, int, Combinable], str]):
    _pyi_private_set_type: Union[str, int, Combinable]
    _pyi_private_get_type: str
    # objects are converted to string before comparison
    _pyi_lookup_exact_type: Any
    def __init__(
        self,
        verbose_name: Optional[str] = ...,
        name: Optional[str] = ...,
        primary_key: bool = ...,
        max_length: Optional[int] = ...,
        unique: bool = ...,
        blank: bool = ...,
        null: bool = ...,
        db_index: bool = ...,
        default: Any = ...,
        editable: bool = ...,
        auto_created: bool = ...,
        serialize: bool = ...,
        unique_for_date: Optional[str] = ...,
        unique_for_month: Optional[str] = ...,
        unique_for_year: Optional[str] = ...,
        choices: Optional[_FieldChoices] = ...,
        help_text: str = ...,
        db_column: Optional[str] = ...,
        db_tablespace: Optional[str] = ...,
        validators: Iterable[validators._ValidatorCallable] = ...,
        error_messages: Optional[_ErrorMessagesT] = ...,
        *,
        db_collation: Optional[str] = ...,
    ): ...

class CommaSeparatedIntegerField(CharField): ...

class SlugField(CharField):
    def __init__(
        self,
        verbose_name: Optional[str] = ...,
        name: Optional[str] = ...,
        primary_key: bool = ...,
        unique: bool = ...,
        blank: bool = ...,
        null: bool = ...,
        default: Any = ...,
        editable: bool = ...,
        auto_created: bool = ...,
        serialize: bool = ...,
        unique_for_date: Optional[str] = ...,
        unique_for_month: Optional[str] = ...,
        unique_for_year: Optional[str] = ...,
        choices: Optional[_FieldChoices] = ...,
        help_text: str = ...,
        db_column: Optional[str] = ...,
        db_tablespace: Optional[str] = ...,
        validators: Iterable[validators._ValidatorCallable] = ...,
        error_messages: Optional[_ErrorMessagesT] = ...,
        *,
        max_length: Optional[int] = ...,
        db_index: bool = ...,
        allow_unicode: bool = ...,
    ): ...

class EmailField(CharField): ...

class URLField(CharField):
    def __init__(
        self,
        verbose_name: Optional[str] = ...,
        name: Optional[str] = ...,
        *,
        primary_key: bool = ...,
        max_length: Optional[int] = ...,
        unique: bool = ...,
        blank: bool = ...,
        null: bool = ...,
        db_index: bool = ...,
        rel: Optional[ForeignObjectRel] = ...,
        default: Any = ...,
        editable: bool = ...,
        serialize: bool = ...,
        unique_for_date: Optional[str] = ...,
        unique_for_month: Optional[str] = ...,
        unique_for_year: Optional[str] = ...,
        choices: Optional[_FieldChoices] = ...,
        help_text: str = ...,
        db_column: Optional[str] = ...,
        db_tablespace: Optional[str] = ...,
        auto_created: bool = ...,
        validators: Iterable[validators._ValidatorCallable] = ...,
        error_messages: Optional[_ErrorMessagesT] = ...,
    ): ...

class TextField(Field[Union[str, Combinable], str]):
    _pyi_private_set_type: Union[str, Combinable]
    _pyi_private_get_type: str
    # objects are converted to string before comparison
    _pyi_lookup_exact_type: Any
    def __init__(
        self,
        verbose_name: Optional[str] = ...,
        name: Optional[str] = ...,
        primary_key: bool = ...,
        max_length: Optional[int] = ...,
        unique: bool = ...,
        blank: bool = ...,
        null: bool = ...,
        db_index: bool = ...,
        default: Any = ...,
        editable: bool = ...,
        auto_created: bool = ...,
        serialize: bool = ...,
        unique_for_date: Optional[str] = ...,
        unique_for_month: Optional[str] = ...,
        unique_for_year: Optional[str] = ...,
        choices: Optional[_FieldChoices] = ...,
        help_text: str = ...,
        db_column: Optional[str] = ...,
        db_tablespace: Optional[str] = ...,
        validators: Iterable[validators._ValidatorCallable] = ...,
        error_messages: Optional[_ErrorMessagesT] = ...,
        *,
        db_collation: Optional[str] = ...,
    ): ...

class BooleanField(Field[Union[bool, Combinable], bool]):
    _pyi_private_set_type: Union[bool, Combinable]
    _pyi_private_get_type: bool
    _pyi_lookup_exact_type: bool

class NullBooleanField(BooleanField):
    _pyi_private_set_type: Optional[Union[bool, Combinable]]  # type: ignore
    _pyi_private_get_type: Optional[bool]  # type: ignore
    _pyi_lookup_exact_type: Optional[bool]  # type: ignore

class IPAddressField(Field[Union[str, Combinable], str]):
    _pyi_private_set_type: Union[str, Combinable]
    _pyi_private_get_type: str

class GenericIPAddressField(Field[Union[str, int, Callable[..., Any], Combinable], str]):
    _pyi_private_set_type: Union[str, int, Callable[..., Any], Combinable]
    _pyi_private_get_type: str

    default_error_messages: Dict[str, str] = ...
    unpack_ipv4: bool = ...
    protocol: str = ...
    def __init__(
        self,
        verbose_name: Optional[Any] = ...,
        name: Optional[Any] = ...,
        protocol: str = ...,
        unpack_ipv4: bool = ...,
        primary_key: bool = ...,
        unique: bool = ...,
        blank: bool = ...,
        null: bool = ...,
        db_index: bool = ...,
        default: Any = ...,
        editable: bool = ...,
        auto_created: bool = ...,
        serialize: bool = ...,
        choices: Optional[_FieldChoices] = ...,
        help_text: str = ...,
        db_column: Optional[str] = ...,
        db_tablespace: Optional[str] = ...,
        validators: Iterable[validators._ValidatorCallable] = ...,
        error_messages: Optional[_ErrorMessagesT] = ...,
    ) -> None: ...

class DateTimeCheckMixin: ...

class DateField(DateTimeCheckMixin, Field[Union[str, date, Combinable], date]):
    _pyi_private_set_type: Union[str, date, Combinable]
    _pyi_private_get_type: date
    _pyi_lookup_exact_type: Union[str, date]
    def __init__(
        self,
        verbose_name: Optional[str] = ...,
        name: Optional[str] = ...,
        auto_now: bool = ...,
        auto_now_add: bool = ...,
        *,
        primary_key: bool = ...,
        max_length: Optional[int] = ...,
        unique: bool = ...,
        blank: bool = ...,
        null: bool = ...,
        db_index: bool = ...,
        default: Any = ...,
        editable: bool = ...,
        auto_created: bool = ...,
        serialize: bool = ...,
        choices: Optional[_FieldChoices] = ...,
        help_text: str = ...,
        db_column: Optional[str] = ...,
        db_tablespace: Optional[str] = ...,
        validators: Iterable[validators._ValidatorCallable] = ...,
        error_messages: Optional[_ErrorMessagesT] = ...,
    ): ...

class TimeField(DateTimeCheckMixin, Field[Union[str, time, real_datetime, Combinable], time]):
    _pyi_private_set_type: Union[str, time, real_datetime, Combinable]
    _pyi_private_get_type: time
    def __init__(
        self,
        verbose_name: Optional[str] = ...,
        name: Optional[str] = ...,
        auto_now: bool = ...,
        auto_now_add: bool = ...,
        *,
        primary_key: bool = ...,
        unique: bool = ...,
        blank: bool = ...,
        null: bool = ...,
        db_index: bool = ...,
        default: Any = ...,
        editable: bool = ...,
        auto_created: bool = ...,
        serialize: bool = ...,
        choices: Optional[_FieldChoices] = ...,
        help_text: str = ...,
        db_column: Optional[str] = ...,
        db_tablespace: Optional[str] = ...,
        validators: Iterable[validators._ValidatorCallable] = ...,
        error_messages: Optional[_ErrorMessagesT] = ...,
    ): ...

class DateTimeField(DateField):
    _pyi_private_set_type: Union[str, real_datetime, date, Combinable]
    _pyi_private_get_type: real_datetime
    _pyi_lookup_exact_type: Union[str, real_datetime]

class UUIDField(Field[Union[str, uuid.UUID], uuid.UUID]):
    _pyi_private_set_type: Union[str, uuid.UUID]
    _pyi_private_get_type: uuid.UUID
    def __init__(
        self,
        verbose_name: Optional[str] = ...,
        *,
        name: Optional[str] = ...,
        primary_key: bool = ...,
        max_length: Optional[int] = ...,
        unique: bool = ...,
        blank: bool = ...,
        null: bool = ...,
        db_index: bool = ...,
        rel: Optional[ForeignObjectRel] = ...,
        default: Any = ...,
        editable: bool = ...,
        serialize: bool = ...,
        unique_for_date: Optional[str] = ...,
        unique_for_month: Optional[str] = ...,
        unique_for_year: Optional[str] = ...,
        choices: Optional[_FieldChoices] = ...,
        help_text: str = ...,
        db_column: Optional[str] = ...,
        db_tablespace: Optional[str] = ...,
        auto_created: bool = ...,
        validators: Iterable[validators._ValidatorCallable] = ...,
        error_messages: Optional[_ErrorMessagesT] = ...,
    ): ...

class FilePathField(Field[_ST, _GT]):
    path: Any = ...
    match: Optional[str] = ...
    recursive: bool = ...
    allow_files: bool = ...
    allow_folders: bool = ...
    def __init__(
        self,
        verbose_name: Optional[str] = ...,
        name: Optional[str] = ...,
        path: Union[str, Callable[..., str]] = ...,
        match: Optional[str] = ...,
        recursive: bool = ...,
        allow_files: bool = ...,
        allow_folders: bool = ...,
        *,
        primary_key: bool = ...,
        max_length: int = ...,
        unique: bool = ...,
        blank: bool = ...,
        null: bool = ...,
        db_index: bool = ...,
        default: Any = ...,
        editable: bool = ...,
        auto_created: bool = ...,
        serialize: bool = ...,
        choices: Optional[_FieldChoices] = ...,
        help_text: str = ...,
        db_column: Optional[str] = ...,
        db_tablespace: Optional[str] = ...,
        validators: Iterable[validators._ValidatorCallable] = ...,
        error_messages: Optional[_ErrorMessagesT] = ...,
    ): ...

class BinaryField(Field[_ST, _GT]):
    _pyi_private_get_type: Union[bytes, memoryview]

class DurationField(Field[_ST, _GT]):
    _pyi_private_get_type: timedelta

class AutoFieldMixin:
    db_returning: bool = ...

class AutoFieldMeta(type): ...

class AutoField(AutoFieldMixin, IntegerField, metaclass=AutoFieldMeta):
    _pyi_private_set_type: Union[Combinable, int, str]
    _pyi_private_get_type: int
    _pyi_lookup_exact_type: Union[str, int]

class BigAutoField(AutoFieldMixin, BigIntegerField): ...
class SmallAutoField(AutoFieldMixin, SmallIntegerField): ...

Hi, it did not resolve mentioned type issues.
I prepared some more precise piece of code, most of the errors are caused by number 2 and 3 below where 3 looks like just a bug and 2 is more like django foreign key magic that is not understood by pylance (it used to be just Unkown without any error raised and also without auto completion help, now we not only has no auto completion but additionally: errors -.-)
from django.db import models
from django.urls import reverse
from django.test import TestCase
from django import forms

class ExampleParent(models.Model):
    field = models.CharField(max_length=5)

class ExampleChild(models.Model):
    parent = models.ForeignKey(ExampleParent, on_delete=models.CASCADE)

parent: ExampleParent = ExampleParent.objects.create(field="xx")

child: ExampleChild = ExampleChild.objects.create(parent=parent)

### 1. foreign key type ###
parent: ExampleParent = child.parent  # parent: _GT@__get__ ?? should be ExampleParent

### 2. foreign key attributes unknonw ###
child.parent.field  # unknown member for type object*, should be Any, or Unknown but with no error
child.parent.pk  # unknown member

### 3. test client ###
class TestTestTest(TestCase):
    def test_test_test(self):
        PATH = reverse("app:test_view")

        response = self.client.get(PATH)

        assert response.status_code == 500  # fine
        assert response.url == "xxx"  # unkown member, should be defined str
        assert response.context == "xxx"  # unkown member, should be defined dict

### 4. forms fields magic attribute fields ###
class FormXYZ(forms.Form):
    wwwww = forms.CharField(max_length=5)

form = FormXYZ({})
form.fields["wwwww"].choices = [("zzz", "zzz")]  # member unknown

thanks.
i'm going to revert my change and just pull  https://github.com/typeddjango/django-stubs
and I'll test your example.
also considering switching to a more pyright friendly fork https://github.com/sbdchd/django-types

the fork seems to do better. all except #4  sbdchd/django-types

Thanks 👍 for working on this issue so fast, I really appreciate that, well this fork indeed looks even better than pylance used to have by default in older versions, at least there is no regression (looking at your screen), number 4 was always broken but this is not really important.
I will find a minute today to try it also on my side, just to give you some feedback how many of 570 errors are resolved with new stubs.

@bschnurr
I've just tried out sbdchd/django-types, works for me! Much better stuff than one that was bundled in pylance before 2022.4.0 (probably some old django-stubs or smth).
Ofc there are some type issues, 574 --> 56 in one of my project mentioned earlier, but now those errors are legit and I should update the code and solve issues, the tool is absolutely right and extra typing for foreign keys rules.
Looking forward the next release :)

Looking at the actual django source it sees url is no longer a property on a response.
https://github.com/django/django/blob/62ffc9883afdc0a9f9674702661062508230d7bf/django/http/response.py#L361
so maybe that's related to change in django.  I'm leaning towards using https://github.com/typeddjango/django-stubs   still but asking them to fix issues we see

hmm. Maybe we should switch to the fork version

Nope, I'm using 4.0+ and this code is working just fine, they didn't removed the attribute url, not at all, note, in docs you pastes, see HttpResponseRedirect. The URL param is specific for redirect, but in tests this should be typed as sometimes you want to test 3xx where this attribute exists (In case of 4xx trying to accessing url probably end up having a
AttributeError or maybe None, I'm not sure)
The decision is yours 😉, but I would prefer the fork a bit more, they claim to do better with pyright and actually I confirmed they really do.
Anyway moving to my own stubs is not a big deal also so django-stubs will also be fine in new pylance releases for me, much better than current broken stubs.


feat(dal, sdf): Update list_pkgs to use Modules on the graph

We are going to read the modules on the graph as the list packages now

bors merge


Triggering policy evaluation

How frequently the policy gets evaluated? can we change that frequency? or trigger it manually somehow? Its taking huge effort to test authored policies and assignments and results are not consistent, dev, test and fix cycles are taking long time

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 07fab47b-3b7a-c02e-c863-2c60f0e06f94
Version Independent ID: f1643e7a-14eb-c372-8099-2f412c954717
Content: Overview of Azure Policy
Content Source: articles/governance/policy/overview.md
Service: azure-policy
GitHub Login: @DCtheGeek
Microsoft Alias: dacoulte

@badalk Thanks for the Comment. We are actively investigating and will get back to you soon.

@badalk Thanks for the question!  Details about when policy is evaluated is documented here.  Triggering evaluation is now possible, but the doc hasn't yet been published.  I'm working on it and hope to have it ready shortly.  I'll update this Issue when it is published.  Thanks!
@MicrosoftDocs/azure-cxp-triage Please assign to me, add label 'doc-enhancement', and #in-progress.

Please share details about manual triggers since it would really help while testing custom policy definitions.

@diwsun I apologize for the delay.  I'll have it posted by mid-week!

Is not this do what is being asked without complexity of manually invoking it via POST method?
Invoke-AzureRmResourceAction  -ResourceType Microsoft.PolicyInsights/policyStates -Action triggerEvaluation -ResourceName latest -ApiVersion 2018-07-01-preview


add "exports" top level field to package.json

why

Export Maps help package authors accomplish two things: transition from Common.js (CJS)  to ESM & make a package's internal files private.
Historically, it has been impossible for some packages to reliably support multiple module systems (UMD, CJS, ESM) and multiple environments (Web, Node.js, Deno). Past efforts to standardize have relied solely on community buy-in, with little official support from Node.js or npm. Export Maps aim to solve this problem as the official Node.js standard to define package entrypoints per-environment.

source: https://docs.skypack.dev/package-authors/package-checks#export-map
see also:
https://docs.skypack.dev/package-authors/package-checks#esm
https://nodejs.org/api/packages.html#packages_subpath_exports
Might help w/ #1625

This is a breaking change - we'll consider adding this in v5 but there are some subtle details that we need to consider.


TensorFlow pre-built package not available for download

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 16.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: NA
TensorFlow installed from (source or binary): NA
TensorFlow version: 2.0
Python version: 3.6
Installed using virtualenv? pip? conda?: pip using wheel
Bazel version (if compiling from source): NA
GCC/Compiler version (if compiling from source): NA
CUDA/cuDNN version:
GPU model and memory:

Describe the problem
We are not able to download the wheels given on page -> https://www.tensorflow.org/install/pip. We are getting the following error when we try to get the *.whl in a browser:

NoSuchKey
The specified key does not exist.

No such object: tensorflow/linux/gpu/tensorflow_gpu-2.0.0-cp36-cp36m-linux_x86_64.whl

The issue occurs with all the links. We tried wget command on linux and get 404 error.
Provide the exact sequence of commands / steps that you executed before running into the problem
wget https://storage.googleapis.com/tensorflow/linux/gpu/tensorflow_gpu-2.0.0-cp36-cp36m-linux_x86_64.whl
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

Oops, I've accidentally closed this issue. (Don't know why exactly yet...) Sorry for the inconvenience.

Strange! I meant to auto close it with  tensorflow/docs@89c6bbf56262. I'm not sure why github only noticed the copy in your fork... I do think this is fixed now.


Merge artifacts in index.html and _includes/svg-icons.html

In both files, there are unresolved merge conflicts committed.

Line#s in index.html: 111,113 and 117
Line#s in _includes/svg-icons.html: 1,14,27

Since I am not sure which parts are intended to include and exclude, I could not fix that and send a pull request.

Thanks for pointing it out.. I have fixed it..


Run every two days on odd "day"

Hey!
I don't know if it's a bug, but I need to have two crons, one on odd day, one on even.
I have this cron definition:
CronJob A: 0 12 1-31/2 * *
CronJob B: 0 12 2-30/2 * *

It seemed to work for the first execution, but two days after, it didn't run... Don't know if it's a known bug or a misuse of us :)
Thanks!

I think that should work. Is it possible that the process exited? If so, a goroutine dump (via SIGQUIT) should be able to identify if any goroutines are blocked in the cron library and where they are. If you see that again, please collect that information, because as-is I don't have enough to investigate with. Feel free to re-open, but closing as inactionable for now.


Generates Next Page link to unlisted doc from prev Doc (from prev folder)

Description
Generates Next Page link to unlisted doc from prev Doc (from prev folder) on prod server
Your environment

Docusaurus version used: 3.4
Environment name and version (e.g. Chrome 89, Node.js 16.4): Chrome, Node v20
Operating system and version (e.g. Ubuntu 20.04.2 LTS): Win10

Sorry but it's impossible to understand your issue, please provide a docusaurus.new repro showing the problem, and explain it a bit more. Until then I'm closing this as a low-quality invalid bug report.

The unlisted feature works as expected to me.
The original init template:

When I mark the "create a blog post" doc as unlisted, and build the site in prod mode, it disappears from both the sidebar and the bottom navigation (and that's the expected behavior, not a bug)

Sandbox: https://stackblitz.com/edit/github-tftxuf?file=docs%2Ftutorial-basics%2Fcreate-a-blog-post.md

At best what we could consider as a bug is that when accessing an unlisted doc, it doesn't have bottom navigation, although it's likely not a big deal.


Use new Caddy Github organization

Fixes #13

The CI issues are unrelated. I think I know the cause of those and will make a PR if the fix works out.
Anyway this looks good - merging!


Add support for custom database prefixes.

WordPress database prefixes were hardcoded into search functions. Anyone using a custom database prefix would experience table not found errors. This change grabs the current database prefix and uses it in the functions.

smart! thanks for the work


Comet Leonard

Any chance that comet Leonard will be added for a few weeks?

Hi!
Thanks for bringing that to my attention.  I'll see what I can do. Last
time we added a comet it was a bit unsophisticated...just a few points
showing its location at intervals.  Might have to do the same for now.
John
On Tue, Dec 7, 2021 at 3:06 PM TheReverendCard @.***>
wrote:

Any chance that comet Leonard will be added for a few weeks?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sky-map-team/stardroid/issues/435, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD5LWC6FWZWBRFXE7NXMYG3UPZSNLANCNFSM5JSDC6FQ
.

Hi - OK this is perhaps a little late, but I added the comet. And the good news is that it should be easier to add the next comet as I'm gradually cleaning up the code.  If you register as a beta tester at https://play.google.com/apps/testing/com.google.android.stardroid
then you should get access to the app in a few hours.  I'm reluctant to roll this out to general users too quickly as it contains a lot of fairly risky changes.


:bug: Added error for invalid checks

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[x] PR title follows the guidelines defined in  https://github.com/ossf/scorecard/blob/main/CONTRIBUTING.md#pr-process

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Fixes #673

What is the current behavior? (You can also link to an open issue here)
No error is returned if invalid checks are provided.

What is the new behavior (if this is a feature change)?
An error is returned if an invalid check is provided.

scorecard --repo=github.com/ossf/scorecard --checks=invalid-check
2021/07/13 08:44:22 Invalid check: invalid-check

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Maybe, but only if users are providing checks arguments which are invalid anyway.

Other information:

/ok-to-test sha=f678771


Added hover background to room cards

also removed duplicates and order of the tailwind classes

@princejoogie could you please attach a screenshot or a small video showing what exactly is changed here?

https://user-images.githubusercontent.com/47204120/113752607-bb893f80-973f-11eb-9ff1-3129bd36702f.mp4
matched the hover states of other buttons to the room cards


Development: Add Docker Compose setups as IntelliJ run configurations

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[x] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

This is a nice-to-have for developers who prefer using the GUI of IntelliJ than using the CLI or Docker Desktop externally.
Description

This PR just creates IntelliJ run configurations for the most commonly used Docker Compose setups and shows those in the run configurations.

When selecting such a configuration, IntelliJ shows the started Docker services in its GUI in the window Services.
Steps for Testing

Prerequisites:

Docker and Docker Compose or Docker Desktop installed
IntelliJ

Open IntelliJ
select a desired Docker run configurations
start the run configuration

Review Progress

Code Review

[ ] Code Review 1
[ ] Code Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Codecov Report

Merging #6574 (14e4ed8) into develop (930b704) will decrease coverage by 0.01%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #6574      +/-   ##
=============================================
- Coverage      80.51%   80.51%   -0.01%
  Complexity     13293    13293
=============================================
  Files           2362     2362
  Lines          90526    90526
  Branches       13355    13355
=============================================
- Hits           72885    72884       -1
  Misses          9710     9710
- Partials        7931     7932       +1

see 3 files with indirect coverage changes

Flag
Coverage Δ

client
76.50% <ø> (-0.01%)
:arrow_down:

server
84.98% <ø> (+<0.01%)
:arrow_up:

Continue to review full report in Codecov by Sentry.

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

Codecov Report

Merging #6574 (85a3dc8) into develop (d9fd495) will decrease coverage by 4.68%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #6574      +/-   ##
=============================================
- Coverage      85.10%   80.42%   -4.68%
+ Complexity     13643    13642       -1
=============================================
  Files           1133     2410    +1277
  Lines          43941    91893   +47952
  Branches        4513    12886    +8373
=============================================
+ Hits           37396    73906   +36510
- Misses          4077     9887    +5810
- Partials        2468     8100    +5632

see 1279 files with indirect coverage changes

Flag
Coverage Δ

client
76.14% <ø> (?)

server
85.10% <ø> (-0.01%)
:arrow_down:

Continue to review full report in Codecov by Sentry.

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


Adding the support of SHAPE operator in armnn

Hi @hosahm01
This has been satisfied.
ArmNN now has support for Shape operator in CpuRef, TfLiteParser and Delegate
TfLite/Delegate Support:  0176fd81
CpuRef Support: 3ae3f978
Closing


enable search on docs site

Search functionality was previously disabled in 8b26365 to prevent merge
conflicts during initial development phase.
This patch re-enables search for a better experience.

I'm a little hesitant about this one. Especially since our docs include API spec now. This would mean any change to API types or docs (99% of PRs) would conflict with each other. I agree that search would be helpful, but I'm hesitant to add that kind of overhead to the dev workflow.

As I recall, the issue was that all docs content was stored in the single line index.json file. That meant any change to docs would automatically conflict.

As I recall, the issue was that all docs content was stored in the single line index.json file. That meant any change to docs would automatically conflict.

Indeed. This certainly increases the overhead. I do find search useful but we can chose to hold this until we settle on #447.

/close


Tighten wording in mutable data members

Add missing "non-reference" constraint, since mutable is not allowed on reference data members. The empty main function is removed as it does not serve any purpose.

It is already 14 march in my timezone.

It is already 14 march in my timezone.

The system only cares about its timezone. We can either wait a day or back the date up 1 day.

I don't mind waiting till tomorrow. Will take note of the date in the future.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


fix(opapi): exportTypesBySection function throws error while parsing refs

 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.


Docker image

More and more Docker is used to "just try" a software, or to really run an app.
It would be really interesting to have a Docker image with all features working out-of-the-box. Someone who would like to tries Camaleon CMS would do the following:
$ docker run -p 3000:3000 owen2345/camaleon-cms

Or something like that, and then he would have to point his web browser to the running app.

Hi @zedtux thanks for your suggestion, I will review docker because I didn't use until now.

I can prepare something for you if you'd like to.

yeah, it would help me a lot!

Alright, let's do it ! :)

:+1:

As this repos is a gem, I'm doing a new repo with a Rails app and the gem.

I'm stuck on the following:
/usr/local/bundle/gems/activerecord-4.2.4/lib/active_record/connection_adapters/sqlite3_adapter.rb:511:in `table_structure': Could not find table 'term_taxonomy' (ActiveRecord::StatementInvalid)
	from /usr/local/bundle/gems/activerecord-4.2.4/lib/active_record/connection_adapters/sqlite3_adapter.rb:385:in `columns'
	from /usr/local/bundle/gems/activerecord-4.2.4/lib/active_record/connection_adapters/schema_cache.rb:43:in `columns'
	from /usr/local/bundle/gems/activerecord-4.2.4/lib/active_record/attributes.rb:93:in `columns'
	from /usr/local/bundle/gems/activerecord-4.2.4/lib/active_record/attributes.rb:98:in `columns_hash'
	from /usr/local/bundle/gems/activerecord-4.2.4/lib/active_record/inheritance.rb:73:in `descends_from_active_record?'
	from /usr/local/bundle/gems/activerecord-4.2.4/lib/active_record/inheritance.rb:79:in `finder_needs_type_condition?'
	from /usr/local/bundle/gems/activerecord-4.2.4/lib/active_record/core.rb:256:in `relation'
	from /usr/local/bundle/gems/activerecord-4.2.4/lib/active_record/scoping/named.rb:33:in `default_scoped'
	from /usr/local/bundle/gems/activerecord-4.2.4/lib/active_record/scoping/named.rb:28:in `all'
	from /usr/local/bundle/gems/camaleon_cms-2.1.1/app/apps/plugins/front_cache/config/initializer.rb:1:in `<top (required)>'
	from /usr/local/bundle/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:274:in `require'
	from /usr/local/bundle/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:274:in `block in require'

when I'm running the rails generate camaleon_cms:install.

Hi @zedtux
it is strange, I tried several times and it works well:
Gemfile:
gem "camaleon_cms", github: 'owen2345/camaleon-cms'

Results:

I'm wondering if this is not related to the database I'm using ... (sqlite3)
I will try it with MySQL or PostgreSQL.

I tested with the sqlite3 too.

fast solution:
comment all lines from here:
/usr/local/bundle/gems/camaleon_cms-2.1.1/app/apps/plugins/front_cache/config/initializer.rb

after install revert the changes.

Okay, I'll do so. Should I open an issue somewhere else ?

yes, please open on this github.


Automated Package Upgrade

:tada: This PR is included in version 25.4.136 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add the text "Search" ("Søk" in Norwegian) to the search icon in the top menu

Comprend has suggested that we add the text Search/Søk to the search icon, and we would like to implement that.
@NickHaggerty1 can you please specify the details?

Also suggest when at this, take a look at making the other actions in the top bar have similar interactive states.
With visible Search text in a ghost button the hover is rounded rectangle;

the Localization button links should have rounded ghost button styling

Review if this ControlChild is necessary around the topbar search icon and the comment:
This div is needed because of the grid layout to wrap focus lock panes. We might look into to improve this at some point.

Done in #2148

@meols This is ready for review.

@padms great. Approved @meols FYI


Investigate Firefox Support

User request:

lighthawk16
Firefox?

Check into effort involved to add Firefox support
+1 for firefox

Sorry I haven't posted any update to this... I feel at this time it doesn't make a lot of sense to invest effort into until the manifest issue has been resolved. My rationale is it would be ideal to do this at the same time as I move to manifest v3 assuming Firefox fully adopts it and it does become mandatory by the threatened date.
Relevant issue: https://github.com/ChadBailey/Humble_Pal/issues/6


Update 7.6.0 known issue

Please merge after the release of 7.6.1

To be canceled and added to 7.7.0 RN?

Yes, the fix will come in 7.7.

Closing. Please send new PR for addition to Known Issues for the release of 7.7.0.


move gen component out of makefile

Signed-off-by: hejianpeng<EMAIL_ADDRESS>What type of PR is this?

/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #80
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

/lgtm


Add an IntelliJ runConfig for the Gallery example

Fixes #6666

travis is sad, not sure why?

It's failing many PRs back from this one...

lgtm modulo the .gitignore change

Thanks Devon, added back .idea to .gitignore

Travis passes after merging with master. Submitting.

I doesn't look like the .gitignore change was included in the merge.

Yup, we didn't want that change, just the addition of the run configuration (there are still several files in .idea that we want to ignore).


Investigate postgres performance for matviews

Materialized views are very slow to update. Spend an hour or so looking into why.

I suspect the most likely reason will be lots of indexes to update. I had a check a while ago for unused indexes, but most of the existing ones seem to be used.
We could see if deleting the indexes, updating, and then re-creating the indexes is any faster.

Creating indexes is also very slow, sometimes.
During high-impact operations on large tables, there are two different bottlenecks, at different times:

Disk writing at 100% utilisation (at around 39686 wkB/s and 79 w/s)
CPU at 100% utilisation

Regarding CPU, the problem is that postgres doesn't allow splitting a query across more than one core, so although we have 20 cores, we can only use one of them. Each core is an Intel(R) Xeon(R) CPU E5-2630L v2 @ 2.40GHz
Mitigation strategies:

Fewer cores, higher performance
Postgres 9.6 should support parallel sequential scans, but won't be released until Q3 this year.

Regarding disk, the write throughput we're seeing is surprisingly low for a modern controller - 85 mB/sec for sequential 4k blocks (compare with 242 mB/Sec on my laptop) (although better for random reads).  I'm more bothered about this as I've noticed I've not been able to other things on the console sometimes, presumably because everything is waiting for IO.
Mitigation strategies:

Write to Digital Ocean about the expected max throughput

I agree that if this becomes a big issue we should also review the application design for performance.
Just wanted to keep some notes somewhere about it, in preparation for when it does become an issue. Might be worth clarifying the disk issue with Digital Ocean now.

From a quick look, most of the matviews do a few sequence scan of, typically, 66 million records, and this is mostly CPU-bound.  Don't think there's a way round this apart from either changing hardware or awaiting 9.6

Brilliant thank you. Please do send a ticket to DigitalOcean support and let's see what they say!

A bit more investigation:
A disk scan is required whenever a sort can't be done in memory, and that's certainly the case for most of the materialized views: they typically take 43B per row, which, with other related data structures (ref), adds up to about 66GB across the entire prescribing table.
Here is the query plan for vw__presentation_summary_by_ccg:
prescribing=> EXPLAIN SELECT processing_date, pct_id, presentation_code, SUM(total_items) AS items, SUM(actual_cost) AS cost, CAST(SUM(quantity) AS bigint) AS quantity FROM frontend_prescription GROUP BY processing_date, pct_id, presentation_code;
                                           QUERY PLAN
-------------------------------------------------------------------------------------------------
 GroupAggregate  (cost=136764033.26..149193863.66 rows=66292429 width=43)
   Group Key: processing_date, pct_id, presentation_code
   ->  Sort  (cost=136764033.26..138421343.98 rows=662924288 width=43)
         Sort Key: processing_date, pct_id, presentation_code
         ->  Seq Scan on frontend_prescription  (cost=0.00..19238784.88 rows=662924288 width=43)

In terms of improving the query time, I guess we'd do best to make the sorting as fast as possible, which means reducing the row size, normalising further, etc. I can't see any obvious candidates for this.
Given this is a once-a-month operation, is this perhaps better achieved using bigquery? AFAICT the following would be equivalent to the above:
SELECT month, pct, bnf_code, SUM(items) AS total_items, SUM(actual_cost) AS cost, SUM(quantity) AS quantity FROM [hscic.prescribing] GROUP BY month, pct, bnf_code LIMIT 100;

Given we don't actually need to recompute data for every month, but just the latest month, could we add a WHERE month > '2016-01-01' to the query above, then append the results to a static table (rather than a materialized view)?
Alternatively, we could do the same thing without involving bigcloud at all.

Update: refreshing vw__presentation_summary_by_ccg took 7 hours 43 mins (27800533.211ms to be precise).

Is that for a concurrent refresh?
BigQuery could be a good way to go. It would mean we could get rid of raw SQL queries in views. It would be a good test step for the measure-calculating process too, where we will definitely need to use BigQuery if we are doing personalised measures.
For BigQuery, the results will be too large to download directly, so the process will be: (1) calculate on BigQuery (2) export to temp table (3) export to GCS (4)COPY to Postgres.

Yes it is for a concurrent refresh.
Which raw SQL queries are you thinking of?

Cool, that's faster than I expected. Was that after the underlying data had
changed?
All the queries to matviews in all the views are raw SQL, which is not
ideal, if they were tables we could use the Django ORM.
On 17 Jun 2016 09:58, "Seb Bacon"<EMAIL_ADDRESS>wrote:

Yes it is for a concurrent refresh.
Which raw SQL queries are you thinking of?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ebmdatalab/openprescribing/issues/82#issuecomment-226717430,
or mute the thread
https://github.com/notifications/unsubscribe/AAExTEyzgUZCE6ulvK8c4_CGwT9W79H7ks5qMmHEgaJpZM4I3QDS
.

Oddly (given updating one view took about the same time), updating all the materialized views took less than 8 hours. Perhaps because the indexes for the prescribing table are loaded into memory by the first view refresh?

Next steps: "Write to Digital Ocean about the expected max throughput"

Have submitted a support request using the account associated with Anna's email address -- please let me know when you get a substantive reply.

Have forwarded reply...

The disk was indeed running too slowly. DigitalOcean have migrated us to a different server. Closing as the only outstanding point is whether we can use BQ for calculating matviews, which comes under the heading of other work.

See also #148 for further comments about performance


Misleading chi-squared values when output.subtract_directions is in use.

Describe the bug
Misleading/incorrect chi-squared values when output.subtract_directions is in use. This is because the post-solve chi-squared values are computed using the residual which in turn is affected by output.subtract_directions. The solution is already partially in place in #212 which also reduces memory footprint.
To Reproduce
Run a DD calibration with output.subtract_directions set to a subset of directions.
Expected behavior
Chi-squared values should decrease/remain the same in places where gain solutions where successful.
Version
main

Fixed by #212.


How to change AppService Language config?

Hello guys, i'm running an appservice (node lts) using a linux appplan. I already have figured out how to change the timzone, but now i need to change the language of the appservice to pt-br.
It's possible to change the language? I have searched all docs about and didn't find anything about it.
Thanks

Thanks for the feedback. We are investigating the issue and will update you shortly.

@rafaelberrocalj, Apologies for the delay! If I have understood your scenario correctly.   You could override the web.config with the location globalization setting.
   <configuration>

   <system.web>

   <globalization culture="pt-BR" uiCulture="pt" />

   </system.web>

 </configuration>

The Culture value determines the results of culture-dependent functions, such as the date, number, and currency formatting, and so on. The UICulture value determines which resources are loaded for the page.
ASP.NET has some native support for automatic locale switching via the web.config section. If your requirement fits then the following setting can be made in web.config: For automatic localization based on the browser’s language. This tries to switch to client locale else switches to en-us.
<configuration>

 <system.web>

   <globalization culture="auto:en-US" uiCulture="auto:en-US" />

   </system.web>

</configuration>

You could also implement this using a custom deployment script as mentioned in this discussion thread.

Hello @AjayKumar-MSFT , i need to change the globalization on the app service.
I'm not running an .net solution.
The timezone can be set using TZ on azure portal, but cant change the langague.
I'm running an docker linux app (metabase).

@rafaelberrocalj, Thanks for sharing additional details. I'm checking on this internally and will get back to you shortly.

@rafaelberrocalj, Apologies for the delay!
You will have to leverage startup scripts to install locale packages and set your environment to language of your choice. These are the packages needed: locales and locale-all.
To do this, please follow the steps outlined here: https://azureossd.github.io/2020/01/23/custom-startup-for-nodejs-python/ and install locales and locale-all packages. Then configure these application settings on the web app. LC_ALL, LANG, LANGUAGE all set to pt_BR.UTF-8.
That should set the language for the container to pt-BR.

Rafael, We will close this out, but if you feel you need more information please just let us know.


WIP Alternative solution for users with old OpenSSL installs

uses info from PR #202 from jdiazdelrio
users can use pip install spiceypy[security]

Coverage decreased (-0.03%) to 99.974% when pulling a7d2a5eab96497e1efc6c5b996e46e91844401e2 on add_extras_for_old_openssl into 64fb6e428155df6c38f18e3f747a8a3818e63f90 on master.

Coverage remained the same at 100.0% when pulling a7d2a5eab96497e1efc6c5b996e46e91844401e2 on add_extras_for_old_openssl into 64fb6e428155df6c38f18e3f747a8a3818e63f90 on master.

@AndrewAnnex
I have tried your solution on my development platforms, by running "pip install ." The first time (Mac, Python2.7.14), i got the message:

ImportError: No module named six.moves.urllib
After installing six, I got the error message:
ImportError: No module named requests
After installing requests, I got the error message:
requests.exceptions.SSLError: HTTPSConnectionPool(host='naif.jpl.nasa.gov', port=443): Max retries exceeded with url: /pub/naif/misc/toolkit_N0066/C/MacIntel_OSX_AppleC_64bit/packages/cspice.tar.Z (Caused by SSLError(SSLError(1, u'[SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:661)'),))
which is the same I was getting in September with the current released version of SpiceyPy

very odd, I am going to try clearing some state maybe that is causing some issues. The import error for requests I fixed in the 2nd commit to this pr so maybe you need to pull those changes.

hmm something non obvious is happening here where pip appears to be skipping the setup_requires parameter which should ensure six is installed, OR, it never gets the chance to make that check as I have to download cspice before I make the call to setup and that depends on six/optionally requirements.

Yes, it never gets the chance to make the checks,
that is why I decided to create a class that encapsulates the setup/build/install
process, so that the setup is first called, and then the class is executed.  I still don't
understand why my PR only fails for the Python3.4 :(

On Oct 25, 2017, at 5:21 PM, Andrew Annex<EMAIL_ADDRESS>wrote:
hmm something non obvious is happening here where pip appears to be skipping the setup_requires parameter which should ensure six is installed, OR, it never gets the chance to make that check as I have to download cspice before I make the call to setup and that depends on six/optionally requirements.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

ah. ok I will take a look at that again. it looks like this also partially because #198 didn't resolve the 'build time' dependency issue. Matplotlib has a fairly complicated work around and this is discussed a bit at https://github.com/scikit-learn/scikit-learn/issues/7867,

The solution I have proposed on my PR resolves the issue you
are having on your PR.  It actually builds/install in all
platforms and passes the pytests.  It also install from a clean
install on my Mac/Linux development environments.  I think it
would be worth checking why it does not manage to build the conda
package for Python 3.4 as that is the only problem we have for
having a fully functional setup file.  Unfortunately, I will not
have time this week...

On Oct 25, 2017, at 6:00 PM, Andrew Annex<EMAIL_ADDRESS>wrote:
ah. ok I will take a look at that again. it looks like this also partially because #198 didn't resolve the 'build time' dependency issue. Matplotlib has a fairly complicated work around and this is discussed a bit at scikit-learn/scikit-learn#7867,
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@jdiazdelrio now I think I understand your PR a lot better now. I will look into it


REST routes formats are inconsistent

Some components ignore the leading slash in routes, some don't.
This works:
'urlManager' => [
    'enablePrettyUrl'     => true,
    'enableStrictParsing' => true,
    'showScriptName'      => false,
    'rules'               => [
        '/rest/v1/tasks'  => '/rest/v1/task/index', // note the leading slash in the value

This doesn't work because of the leading slash:
'as authenticator' => [
    'class'  => 'yii\filters\auth\HttpBasicAuth',
    'except' => [
        '/rest/v1/task/options', // note the leading slash

where did you put the second code for authenticator?
Note that except property of ActionFilter contains action ID only when applied to a controller. e.g. options instead of /rest/v1/task/options

@cebe 'as authenticator' is in the main.php config of my app, 'rest' and 'v1' are modules
api -- application root
    config
        main.php -- 'as authenticator' is here in my config array
    modules
        rest
            modules
                v1
                    controllers
                        TaskController.php -- here is my 'options' action

I want to bypass the authenticator when accessing the 'options' action.
Am I doing it right?

I am no longer interested in this. Feel free to reopen if needed.


Multi-node failure on parallelize_tasks_image3.rg

Here is another multi-node failure. I believe this is a runtime bug because it only reproduces with -finner 1 (not -finner 0) and Legion Spy reports an error. (Also, the test passes with bounds checks enabled, so I don't think the parallelized kernels themselves can be doing anything bad.)
./install.py --debug --gasnet
LAUNCHER='mpirun -n 2 -H localhost --bind-to none -x REALM_SYNTHETIC_CORE_MAP= -x INCLUDE_PATH -x LD_LIBRARY_PATH -x TERRA_PATH' ./regent.py ./tests/regent/run_pass/parallelize_tasks_image3.rg -ll:cpu 4 -fbounds-checks 1 -fparallelize-dop 4,4 -finner 1

Legion Spy reports:
ERROR: Missing source precondition for Realm Copy (220) on field f (101) for op region requirement 3 of stencil.parallelized on init.parallelized

Log files:

spy_0.txt
spy_1.txt

This appears to be related to whether you're using small or large instances for the regions.
If you go to DefaultMapper::default_policy_select_instance_region at default_mapper.cc:1996 and change the line if (total_nodes == 1) to if (true), then the test passes even with -finner 1. Normally, -finner 1 would cause Regent to avoid mapping a large instance of the data, whereas -finner 0 would cause Regent to create an inline mapping up front. Thus the failure appears to be correlated with whether or not Regent is using small or big instances.

You can also use this to reproduce the failure on a single node.
Go to default_mapper.cc:1996 and change the condition to if (false). This disables the special case for single node execution. Then run:
./regent.py ./tests/regent/run_pass/parallelize_tasks_image3.rg -ll:cpu 4 -fbounds-checks 1 -fparallelize-dop 4,4 -finner 1

Legion Spy validates the single node execution of this application.  Furthermore it runs correctly on the olddma branch.  Therefore I'm going to assign this bug to @jiazhihao to fix on a single node. Zhihao, once you get this fixed on a single node then assign the bug back to me and I will check the multi-node behavior.

The problem on a single node was not a DMA bug, but instead was a case where the runtime was allowing the mapper to choose an empty instance for a region that was not actually empty.  This problem is fixed with 818f4f9 and we should see no more problems on a single node.
However, I don't think this fixes the original multi-node bug that we saw of the missing precondition.  My guess is that this bug still exists.  However, I also think that this issue is the same as #246.  Assigning back to myself for now.

I think you did actually fix the multi-node bug. The original bug reproduced 100% for me, and after the change I can't repro after 200 runs. Gitlab also doesn't repro anymore, and it was again reproing 100% before the change.
Meanwhile, #246 is still reproing just fine. I think these are actually different bugs.
I'll leave this open for the moment, but I think this bug is fixed.

Definitely not fixed.  The error message in the logs above has nothing to do with the thing that I fixed for single node.  Here is an experiment, try running the multi-node version, but run Legion Spy on the log files regardless of whether the run passes or fails.  I bet it fails every single time (#246 definitely does).

Yeah, it is still there:
ERROR: Missing source precondition for Realm Copy (106) on field f (101) for op region requirement 0 of stencil_serial on init.parallelized

I suppose we should be running multi-node spy tests....

This should be fixed with 85083a4.  Assigning back to @elliottslaughter to confirm.

Confirmed.


Returns multiple records for some ZCTAs

Appears to be those that cross state lines. Examples: 69201, 51360, 59270

Good call out--thanks.
I'm adding the following line to fetch_geography.ipynb ...
df = df.groupby(df.index).apply(sum)
... which should sum the files on an index (zcta) basis prior to processing. Will run overnight and see what shakes out.


Add unit tests for Singularity

Will need to add in unit tests for testing out Singularity functionality. This is limited by the inability to call Singularity images remotely from quay.io. Until that feature is supported by Singularity, this issue will remain opened.

Note to self: Singularity version 2.3 was just released (https://github.com/singularityware/singularity/releases/tag/2.3).
I've tested it's functionality locally on a Biowulf machine and it does indeed pull and run docker containers from remote quay.io repositories! This should now make unit tests possible. Hopefully this greatly simplifies the use of Singularity containers and maintaining unit tests.
An example of a working command when installing singularity 2.3 on a machine running CentOS version 6.8:
singularity exec docker://quay.io/vgteam/vg:v1.5.0-303-gb1a6cc8c-t62-run vg
@glennhickey Singularity version 2.3 will need to be installed on the Jenkins machine in order to implement singularity unit tests. Do you know how I could do that? What credentials would I need to access the Jenkins server?

Note to self: The use of remote singularity images means I no longer have as much control over them as I did when I created local images. This means that I may need the /data bind point to be available on each container. However, it does appears that in singularity 2.3 that if the bind point does not exist it will by default use src as the mount point within the container.
Example:
singularity exec --bind $PWD:/data docker://realtimegenomics/rtg-tools rtg vcfeval
since the /data mount point doesn't exist within the rtg-tools container, singularity will instead set the mount point to $PWD within the container.

Guess you'd need to update the toil-jenkins-slave AMI image?  There's
source on cgcloud
https://github.com/BD2KGenomics/cgcloud/blob/master/jenkins/src/cgcloud/jenkins/toil_jenkins_slave.py
but I don't know if it's used anymore.
You'd need to talk to whoever;s in charge of the Jenkins server to find
out.  Maybe Edwin now that CJ's gone..  May be more hassle than it's worth
at this point

No, I think it's worth supporting singularity especially if we want NIH people to actually use these tools. I'll ping Edwin about this.


⚠ Bofrost.com has degraded performance

In c50f71b, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 1825 ms

Resolved: Bofrost.com performance has improved in bee8587.


Collect costs of failed fill transactions for determine contract parameters

Currently we multiply only the fill transaction cost with the failed_fill_transactions factor.
For Ethereum costs of a failed fill transaction are only 25% of a successful fill. We can easily extend the query to get the average costs of the failed fill transactions and add the multiplied value to the transfer cost. Therefore estimated costs are more close to real costs.
Acceptance criteria

[x] Get avg and median failed fill transaction cost
[x] Get avg and median successful fill transaciton cost
[x] Make sure that the failed fill factor is only counting failed fills per successful
[x] Update the Google Sheet for correct transfer cost calculation

Dune queries are ready for review:
ETH: https://dune.com/queries/2378580
ARB: https://dune.com/queries/2378578
OP: https://dune.com/queries/2378576
What has changed from the previous queries:

Updated the queries to include the avg/median for both failed & successful fill transaction cost
Included these values in the final transfer_cost calculation
Extended the output columns to show all the newly added values
Slight refactor of the name abbreviations as they proved to be confusing (fpw, fpc, fpf etc.)

Would like to get these forked queries reviewed first by the Dune Wizard @compojoom before overwriting the code in the original queries.

@compojoom please close this issue if done

I think it's ok. Padawan @GabrielBuragev has outgrown his master. 😛


Blocking issue after upgrade to 2.0.20

I upgraded yesterday my Miniflux from 2.0.18 to 2.0.20. And now I'm facing a blocking issue, a violation of a "not null constraint"
Unable to create entry "http://www.phoronix.com/scan.php?page=news_item&px=GCC-8.4-Released" (feed #20): pq: null value in column "changed_at" violates not-null constraint
Unable to create entry "https://arstechnica.com/?p=1656979" (feed #4): pq: null value in column "changed_at" violates not-null constraint
Whatever feed I click on, I get this error.
My miniflux runs through a docker container. I just pulled the new image, stopped the previous one, and started this new one. I did this yesterday night. And this morning, everything seems pretty normal, I was able to read my feeds as I do on a daily routine.
Any idea?

I have the exact same issue....

The error prevents the feeds to be updated. I rollback to 2.0.18.

I found my problem. I kept the old 2.0.18 container, which was on "auto restart". And then, it was this one which created the error. Once removed for good, no more problem. I keep the ticket open for @ctschach. Feel free to close it.

Had to run
miniflux -migrate
Looks like it's working now...

Ok. So I close the ticket.


[SPARK-10903] followup - update API doc for SqlContext

What changes were proposed in this pull request?
Follow up on the earlier PR - in here we are fixing up roxygen2 doc examples.
Also add to the programming guide migration section.
How was this patch tested?
SparkR tests

@shivaram @sun-rui

Test build #59431 has started for PR 13340 at commit f0b7d41.

Test build #59431 has finished for PR 13340 at commit f0b7d41.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59431/
Test PASSed.

Merged build finished. Test PASSed.

LGTM

LGTM. Merging into master and branch-2.0


Failed to execute plugin which contains dependency unresolve external:<...>

I am using go-loader as my plugin system. The plugin that I want to use is available here. I build the object file with following commands as is described in the docs:
go list -export -f '{{if .Export}}packagefile {{.ImportPath}}={{.Export}}{{end}}' std \
  $(go list -f '{{.Imports}}' ./... \
  | awk '{sub(/^\[/, ""); print }' \
  | awk '{sub(/\]$/, ""); print }') > importcfg
find . -name "*.go" -type f -print | xargs go tool compile -importcfg importcfg -o ethereum.o

I tried to use that object file in my other project but am I getting the following error:
go build main.go
./main

unresolve external:github.com/ethereum/go-ethereum/ethclient.(*Client).NetworkID

System information:

Go: 1.20
OS: Ubuntu 22.04

Hi, have you tried building/loading a JIT package using my fork https://github.com/eh-steve/goloader ?

I am using go-loader as my plugin system. The plugin that I want to use is available here. I build the object file with following commands as is described in the docs:

pkujhd/goloader branch not support for obj file with cgo.  you can try eh-steve/goloader branch
unresolve external:github.com/ethereum/go-ethereum/ethclient.(*Client).NetworkID
you use a .o not package main, so you  need set path for goloader


Network transmissions can get interrupted on shutdown

When the process within an enclave sends a large amount of data over an open socket and then exits, not all of the data will be sent before the enclave exits. From the client's point of view, the response to their request is prematurely terminated. I'm guessing this is because odyn isn't flushing its buffers before exiting, but I haven't had a chance to investigate.

Your theory sounds correct. You can see here that it spawns a next task but doesn't store the handle and therefore doesn't join on exit. And I suppose the tokio runtime does not wait for the tasks to complete on exit.


Deliver tell when the user say something in the channel for the first time after the tell

I'm migrating to hubot from a drupal bot that had the tell functionality.
There is people in my chat room who never enter the IRC room they just change the to bob_away or similar.
Can the bot react on nick changes to?

First you should punch those people because that's bad practice ;)
Second thing would be to figure out if hubot sends us an event when someone changes their nick and react to that as well. I can't see one in https://github.com/github/hubot/blob/master/src/robot.coffee at the moment so this might be a bit difficult.

To not ever leave a channel is one of the main features of irssi IRC client. They are the NSA of IRC.
As an example of what youcommented I found this:
https://github.com/bobsilverberg/hubot-welcome/blob/master/src/welcome.coffee
That reacts on nick change.
But I have been thinking about when this plugin should tell the message. Why not on the first time the user says something after the tell command happenend?
This covers my use case and problems with users leaving their irc open and not paying attention, users entering the channel and leaving because a quick restart of the IRC client, other hubot adapters where users never actually leave like telegram. Also, this plugin will deliver the message when they are paying attention to the channel.
We just have to listen to the username of every message.

I'm familiar with IRC, my WeeChat runs in a tmux and I never quit.
The problem with detecting nick changes is just that the matching is done on a prefix basis because some people use different suffixes to their nick depending on the machine they're using and whatnot, so it's not always possible to know the exact nickname they will be using (like "foo", "foo2", and "foo_work"). This obviously doesn't work with "foo" and "foo_away".
I thought someone had already built what you suggested, sending the messages when the recipient speaks again, it's definitely a very good idea. We should probably go this route instead of trying to detect nick changes.

Changed issue title to reflect what we talked about.
I think we should decide on replacing the old behavior of delivering the tell when the user enters or maintain both.
I'm more inclined to replace but I'm aware that will break what current users expect of this plugin.
What do you think?

Definitely both, breaking existing use cases for such a limited script sounds like a bad idea.
Code-wise it's not hard, we factor the retrieval of stored messages and sending thereof into a method and call it in both scenarios. Should be easy.

any thoughts on adding this?

This repo doesn't see a commit for a long time. Maybe it needs new maintainers before this can be implemented.

I'd be happy to merge a pull request that does this as outlined here. However, I'm not using Hubot any more myself, so I probably won't implement it myself.


Update version of Capsule and the plugin itself

Ran the tests...but they didn't pass.
./gradlew check
FAILURE: Build failed with an exception.

* Where:
Build file 'C:\git\gradle-capsule-plugin\build.gradle' line: 64

* What went wrong:
Execution failed for task ':testIntegration'.
> Cannot run program "C:\git\gradle-capsule-plugin/src/test/gradle/gradlew" (in directory "C:\git\gradle-capsule-plugin\src\test\gradle"): CreateProcess error=193, %1 is not a valid Win32 application

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

I think it was just due to me running it on Windows....
Addresses issue https://github.com/danthegoodman/gradle-capsule-plugin/issues/16

@telekenetix I'm afraid I hardcoded my os into the tests, so the integration tests won't run without some additional work on my end. Thanks for at least giving it a shot though! I'll run the tests on my end and merge it in here in a little bit.

@telekenetix Thanks again! These changes have been applied to master and a new release is out.

No problem :)


NIFI-2732 ensure session and consumer aligned and has registered reba…

…lance listener. Make consumption far more memory and process efficient.

With the new commit, all looks good from a code review perspective. I haven't yet had a chance to test ConsumeKafka0_10, though I did test ConsumeKafka and that all worked as expected. Once I've had a chance to test ConsumeKafka0_10 I'll be happy to merge. Or if anyone else has a chance to verify it, please feel free to merge it as well.

I performed the same test as I did when reworking the processors... everything worked with 0.9 plaintext, ssl, and SASL, and 0.10 plaintext, ssl, and SASL I'll go ahead and merge.


Crf decode cell serialize functions

This PR fixes #1934 by adding get_config and from_config methods to CrfDecodeForwardRnnCell.
A test case that fails before the implementation and passes afterwards is also added. The test uses an example similar to the issue. However, I'm unsure if instead it would make more sense to create a simpler test that instantiates the object and then reconstruct it from the methods.

@WindQAQ

@googlebot I signed it!

@googlebot I fixed it.

Can't seem to be able to add a reviewer so I'm tagging you here. @WindQAQ

@googlebot I fixed it.

Thanks for the PR.


Mind the Gap Portfolio project

Background
from minutes https://curriculum.codeyourfuture.io/guides/contributing/minutes/
Sally’s proposed Portfolio project
People didn’t feel that they have a driver to diversify their portfolio (e.g. try picking up a new library/language)
Based around the TV Show Project
Which is built around user stories/acceptance criteria
Suggested steps:

Rewrite the TV Show Project in TypeScript
Identify the gap between previous iteration (i.e. in JS) and TS
Reflect on what did trainees need to learn to achieve this
Rebuild in Python
Reflect again on what did trainees need to learn to learn this

Etc
Ali: I really like this model, it feels like a healthy “push out the door”
Historically, a Redux module has been requested but we deliberately never implemented it specifically for this reason
Ali: small risk of keen-on-Python volunteers turning this into a “learn Python from the ground up” module
Daniel: suggest delivering a project within a short timebox to make it clear that we want to focus on the simple outcome rather than the specifics in depth
Acceptance criteria

Typescript example in /dir
Reflective workshop in workshops
Identify/scoping workshop in workshops
Reviewed samples in repo

Owner
SallyMcGrath
Stakeholder
?
Approver
Syllabus team

Oh god this got lost -- I'm moving it to curriculum where it's more likely to surface


UWP IsGeoLocationEnabled returns true even when location is disabled

Note: This bug also affects the CrossPermissions plugin.
Bug Information
Version Number of Plugin: 4.0.1
Simulator Tested On: Visual Studio Emulator
Version of VS: 15.3
Version of Xamarin: <IP_ADDRESS>9 (Android SDK: <IP_ADDRESS>)
Steps to reproduce the Behavior
In an UWP app:

Request location permission. Grant it in the app when prompted.
Disable location in the device settings.
Check the permission. It is Denied; it should be Granted.
Request permission. It will automatically return Granted without any prompt to the user.
Check CrossGeolocator.Current.IsGeolocationEnabled. It returns true; it should return false since locationing is disabled.

IsGeolocationEnabled only checks to see if it is disabled and available.
via:  https://docs.microsoft.com/en-us/uwp/api/windows.devices.geolocation.positionstatus
Disabled | Location settings are turned off. This status indicates that the user has not granted the application permission to access location.
NotAvailable | Location services is not available on this version of Windows.
To check permission RequestAccessAsync always has to be called like the permission plugin does: https://github.com/jamesmontemagno/PermissionsPlugin/blob/master/src/Plugin.Permissions.UWP/PermissionsImplementation.cs#L88
This is most likely why the permission is coming back denied, which makes sense if that is what UWP is telling me. The permissions plugin for UWP does not implement the request and always returned granted .
Implementation here is correct though.

Specifically now reading this: https://docs.microsoft.com/en-us/uwp/api/windows.devices.geolocation.geolocator#Windows_Devices_Geolocation_Geolocator_RequestAccessAsync
There is no way to find out this information unless you are actively tracking it. Assumption here is that perhaps every single Windows device has geolocator capabilities....
he LocationStatus property is updated dynamically only when a tracking session is active. Otherwise, it is either NotInitialized or Disabled.
Seeing this it does look like it should return disabled if it is disabled.


Add Sujeevan to Contributors list

Please revise and add Sujeevan to the Contributors list

Hi  @sujeevan81, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.


Avoid multiple writes and prints on distributed settings

ExtensionsManager now holds the distributed rank information.
Some extensions that write to files or print to stdout do that action only in the master rank. However, they can be executed in the worker ranks without side-effects.
There are some issues such as, if in a distributed environment, maybe there is some scenario where we want the workers to write to a specific folder each, and abstract that through a writer. So I wonder if enforcing an only rank==0 writing in the code base is good.

I think it is a responsibility of users to decide which extensions need to be activated on each node, like as designed in Chainer:
https://github.com/chainer/chainer/blob/8b9e9c014716077366845fdb5bf780644c067952/examples/chainermn/mnist/train_mnist.py#L114-L116
We need to document and/or add examples this point.

@emcastillo Do you think we can close this PR?


Aliased method disapper on rspec-mocks 3.4.1

class A
  def g1
    1
  end
end

class B < A
  def f
    g2
  end

  alias g2 g1
end

describe '#f', order: true do
  let(:b) { B.new }

  it 'call B#g2' do
    expect_any_instance_of(B).to receive(:g2).with(no_args)
    b.f
  end

  it { expect(b.f).to eq 1 }
end

This works fine on rspec-mocks 3.4.0.
But on rspec-mocks 3.4.1, below error occurs.
Failures:

  1) #f
     Failure/Error: g2

     NameError:
       undefined local variable or method `g2' for #<B:0x007fd11f2f15c8>
     # ./test_spec.rb:9:in `f'
     # ./test_spec.rb:23:in `block (2 levels) in <top (required)>'

The version of Ruby is 2.1.5 and 2.2.3.

I think #1043 is the source of the problem.  I don't understand how it causes the failure yet, though.

I'll try to take a look at this @myronmarston since I added #1043.  I agree, that change is probably at fault.

Ok, I figured out what's happening.
It turns out Method#owner is terribly inconsistent to determine which class implements an aliased method.
See here

@myronmarston this "hack" fixes it for ruby 2.1.x, 2.2.x but Method#original_name doesn't exist in ruby 2.0 and earlier.
diff --git a/lib/rspec/mocks/any_instance/recorder.rb b/lib/rspec/mocks/any_instance/recorder.rb
index 8651e02..691f8a4 100644
--- a/lib/rspec/mocks/any_instance/recorder.rb
+++ b/lib/rspec/mocks/any_instance/recorder.rb
@@ -208,7 +208,9 @@ module RSpec
           return unless public_protected_or_private_method_defined?(method_name)

           alias_method_name = build_alias_method_name(method_name)
-          @backed_up_method_owner[method_name.to_sym] ||= @klass.instance_method(method_name).owner
+          method = @klass.instance_method(method_name)
+          owner = method.original_name == method ? @klass.instance_method(method_name).owner : @klass
+          @backed_up_method_owner[method_name.to_sym] ||= owner
           @klass.class_exec do
             alias_method alias_method_name, method_name
           end
diff --git a/spec/rspec/mocks/any_instance_spec.rb b/spec/rspec/mocks/any_instance_spec.rb
index a3b6a7e..1097fe9 100644
--- a/spec/rspec/mocks/any_instance_spec.rb
+++ b/spec/rspec/mocks/any_instance_spec.rb
@@ -5,12 +5,22 @@ module AnyInstanceSpec
     def foo(_a)
       'bar'
     end
+
+    def g1
+      1
+    end
   end

   class ParentClass < GrandparentClass
     def foo
       super(:a)
     end
+
+    def f
+      g2
+    end
+
+    alias g2 g1
   end

   class ChildClass < ParentClass
@@ -40,6 +50,17 @@ module RSpec
         end
       end

+      context  '#f' do
+        let(:parent) { AnyInstanceSpec::ParentClass.new }
+
+        it 'call ParentClass#g2' do
+          expect_any_instance_of(AnyInstanceSpec::ParentClass).to receive(:g2).with(no_args)
+          parent.f
+        end
+
+        it { expect(parent.f).to eq 1 }
+      end
+
       context "invocation order" do
         context "when stubbing" do
           it "raises an error if 'with' follows 'and_return'" do

So, owner for aliased methods isn't consistent per ruby versions... We can check if the method is an alias by comparing the method name vs. original_name but then original_name was added in 2.1 so we'd have to figure out a different solution for 2.0 and earlier.

To be honest, I don't know what owner should say for an aliased method or a class that subclasses a class with the aliased_method.

Given that the bug addressed by #1043 only manifested on Ruby 2.3, can we restore the original pre-#1043 behavior for RUBY_VERSION < '2.3.0' and then have the fix from #1043 in effect only on Ruby 2.3? On 2.3 you could also use original_name to guard against the alias issue, right?

@myronmarston opened #1060 to fix this. Note, since we only check owner for ruby 2.3+ and owner for aliased methods appears to do the right thing in ruby 2.3.0, we don't need to check original_name.  Namely, we only need to restore the aliased method to the class if that class added the alias, which is what owner does for us with ruby 2.3+. See: https://gist.github.com/jrafanie/0e5b8a9f4e8b4f84913f#file-output-txt-L43

@shigi can you try master now?

Thank you for your fix!

@shigi Great!  Thank you for reporting the issue and confirming it worked for you.
The (allow|expect)_any_instance_of(...) code is quite complicated so I appreciate your confirmation!


Update fs2-core, fs2-io to 3.0.3

Updates

co.fs2:fs2-core
co.fs2:fs2-io

from 2.5.6 to 3.0.3.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "co.fs2" } ]

labels: library-update, semver-major

Superseded by #219.


Change data-column to something like data-flow="column"

So we’re consistent about when to use data-.
(see https://github.com/EagerIO/App/issues/500)

lol, thanks @renandincer