Enable requests and assignments

The current version of the feature has "Enable requests and assignments" toggle instead of "Enable request", can you please update the documentation accordingly? In particular, can you confirm whether setting this to No disables the package for both end users and admins alike?

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

ID: 066dbfa5-08ba-8b7a-845b-854c873362b6
Version Independent ID: 97d7f2b3-904a-574f-3732-9f6851291890
Content: Create a new access package in entitlement management - Azure AD
Content Source: articles/active-directory/governance/entitlement-management-access-package-create.md
Service: active-directory
Sub-service: compliance
GitHub Login: @msaburnley
Microsoft Alias: ajburnle

Hi @michevnew Thanks for your feedback. We will review and update as appropriate.

@michevnew  Yes, the feature when switched to No would affect the Users and Admins as well.
And thank you for the feedback, we are assigning the thread to the author to have it changed.
@msaburnley Kindly have the screenshot and the sub-titles updated in the "Enable Request" section of the document.

Hey @michevnew
I have updated the screenshots and content. I left the title of the subsection the same because it doesn't have the match the UI in this case because it's not a step and is about enabling requests in general.
Thanks for your feedback and let me know if you have any questions. #please-close


analytics: Fix count_stream_by_realm.

Add a join clause on zerver_message in count_stream_by_realm,
otherwise we only output the final total streamcount for a realm
for every time entry.

Automated message from Dropbox CLA bot
@umkay, it looks like you've already signed the Dropbox CLA. Thanks!

@rishig

@umkay let me know when this gets updated. Thanks!

Looks like a new version was posted; @rishig can you review?

@umkay @timabbott made two minor comments, can be merged after that!

fixed

awesome, thanks! @timabbott ready for merge.

Merged, thanks @umkay and @rishig!  This logic isn't quite correct because it doesn't handle streams that are deactivated, but that issue is actually because we don't even track when streams are deactivated, not an issue with this logic.  We'll probably want to change that; streams aren't the only place we have the issue anyway, so let's just add that to the TODO list for the future.

Just making a note-- we might have some code cleanup involved here in the future, but the way we would handle the streams that are deactivated is by creating the following CountStat:
CountStat('active_streams', zerver_stream_by_realm,                                {'deactivated': False},...)


Lookup Symbol shortcut cannot be specified in the Editor shortcut settings

Tested versions
Repro in 4.2
System information
macOS Sonoma non-mono version
Issue description
" Lookup Symbol" shortcut cannot be specified in the Editor shortcut settings, and I think it's probably just being overlooked. So I could use my preferred shortcut to look at the definition. It's supported in all major IDEs and I'm not the only one needing this in Godot: https://www.reddit.com/r/godot/comments/150ej30/shortcut_for_go_to_definitionlook_up_symbol/
Steps to reproduce
Go to Editor > Editor Settings > shortcuts and search for Lookup Symbol and nothing shows
Minimal reproduction project (MRP)
NA

+1

@tpcmurray Please don't bump issues without contributing significant new information. Use the :+1: reaction button on the first post instead.

This might close godotengine/godot-proposals#4577 (forgive if this was obvious -- I came considering fixing and thought it useful to cross link these two.)
p.s. thx for fixing already -- keenly awaiting this landing!


feat: created initial setup for contributors page

This PR will close this issue
This PR will implement the contributors page for the project.

ok i got your point


Fix(Extendable): Fix TS decorators breaking Extendables

Description of the PR
When an extendable is decorated, Object.getOwnPropertyKeys() no longer returns the property names, not even the built in ones (constructor, prototype, name, length)
The fix in action can be viewed here
Changes Proposed in this Pull Request (List new items in CHANGELOG.MD)

Semver Classification

[ ] This PR only includes documentation or non-code changes.
[x] This PR fixes a bug and does not change the (intended) framework interface.
[ ] This PR adds methods or properties to the framework interface.
[ ] This PR removes or renames methods or properties in the framework interface.

It should be noted that if a class being passed to appliesTo has been decorated, then Object.getOwnPropertyDescriptor will return undefined unless it is also made with this fix, which I haven't included but can if needed

Does this break "normal" extendables?

@tech6hutch fixed in 866153d151e9f30fb11d5461d31305f9e64d5d3a

As per discord discussion, this shouldn't be merged, and should instead wait for decorators to land in JS


restore fails

Hi New to this backup have issue on restore,
Want to know my pvc backup completed sucessfully or not and why restore fails
I created a mongodb pod with pvc running once backup executed deleted some files in mongodb pvc and try to restore in same pod please advice were its failing
I have't configure restic
1, Executed "velero describe backup pvc-backup" Snapshot PVs:  true but Persistent Volumes:  ?
hostname:~# velero version
Client:
Version: v1.0.0
Git commit: 72f5cadc3a865019ab9dc043d4952c9bfd5f2ecb
Server:
Version: v1.0.0
Steps followed for backup
1, kubectl -n velero-backup-test annotate pod/mongodb-appops-ibm-mongodb-dev-575b49dcdc-9wh69 backup.velero.io/backup-volumes=mongodb-mongodb-ibm-appops-pvc --overwrite
2, velero create backup pvc-backup --selector release=mongodb-appops-ibm-mongodb-dev-575b49dcdc-9wh69 --snapshot-volumes=true
hostname:~# velero backup get
NAME         STATUS      CREATED                         EXPIRES   STORAGE LOCATION   SELECTOR
pvc-backup   Completed   2019-09-04 17:18:01 +0530 IST   29d       default            release=mongodb-appops-ibm-mongodb-dev-575b49dcdc-9wh69
hostname:~# velero describe backup pvc-backup
Name:         pvc-backup
Namespace:    velero
Labels:       velero.io/storage-location=default
Annotations:
Phase:  Completed
Namespaces:
Included:  *
Excluded:
Resources:
Included:        *
Excluded:
Cluster-scoped:  auto
Label selector:  release=mongodb-appops-ibm-mongodb-dev-575b49dcdc-9wh69
Storage Location:  default
Snapshot PVs:  true
TTL:  720h0m0s
Hooks:
Backup Format Version:  1
Started:    2019-09-04 17:18:01 +0530 IST
Completed:  2019-09-04 17:18:08 +0530 IST
Expiration:  2019-10-04 17:18:01 +0530 IST
Persistent Volumes:

Steps for restore
1, velero restore create --from-backup pvc-backup --restore-volumes=true
hostname:~# velero restore get
NAME                        BACKUP       STATUS            WARNINGS   ERRORS   CREATED                         SELECTOR
pvc-backup-20190904180916   pvc-backup   PartiallyFailed   0          1        2019-09-04 18:09:17 +0530 IST
hostname:~# velero describe restore pvc-backup-20190904180916
Name:         pvc-backup-20190904180916
Namespace:    velero
Labels:
Annotations:
Phase:  PartiallyFailed (run 'velero restore logs pvc-backup-20190904180916' for more information)
Errors:
Velero:   backup does not contain top level resources directory
Cluster:
Namespaces:
Backup:  pvc-backup
Namespaces:
Included:  *
Excluded:
Resources:
Included:        *
Excluded:        nodes, events, events.events.k8s.io, backups.velero.io, restores.velero.io, resticrepositories.velero.io
Cluster-scoped:  auto
Namespace mappings:
Label selector:
Restore PVs:  true
hostname:~# velero restore logs pvc-backup-20190904180916
time="2019-09-04T12:39:18Z" level=info msg="starting restore" logSource="pkg/controller/restore_controller.go:440" restore=velero/pvc-backup-20190904180916
time="2019-09-04T12:39:18Z" level=info msg="Not including resource" groupResource=nodes logSource="pkg/restore/restore.go:128" restore=velero/pvc-backup-20190904180916
time="2019-09-04T12:39:18Z" level=info msg="Not including resource" groupResource=events logSource="pkg/restore/restore.go:128" restore=velero/pvc-backup-20190904180916
time="2019-09-04T12:39:18Z" level=info msg="Not including resource" groupResource=events.events.k8s.io logSource="pkg/restore/restore.go:128" restore=velero/pvc-backup-20190904180916
time="2019-09-04T12:39:18Z" level=info msg="Not including resource" groupResource=resticrepositories.velero.io logSource="pkg/restore/restore.go:128" restore=velero/pvc-backup-20190904180916
time="2019-09-04T12:39:18Z" level=info msg="Not including resource" groupResource=restores.velero.io logSource="pkg/restore/restore.go:128" restore=velero/pvc-backup-20190904180916
time="2019-09-04T12:39:18Z" level=info msg="Not including resource" groupResource=backups.velero.io logSource="pkg/restore/restore.go:128" restore=velero/pvc-backup-20190904180916
time="2019-09-04T12:39:18Z" level=info msg="Starting restore of backup velero/pvc-backup" logSource="pkg/restore/restore.go:364" restore=velero/pvc-backup-20190904180916
time="2019-09-04T12:39:18Z" level=info msg="restore completed" logSource="pkg/controller/restore_controller.go:442" restore=velero/pvc-backup-20190904180916
hostname:~#

@vkrishr it doesn't look like you have snapshots for your PVs -- you likely need to configure restic (see https://velero.io/docs/v1.1.0/restic/). Also, to do a restore, you'll need to first delete the app (i.e. the deployment), as Velero won't overwrite existing resources in the cluster.

Thanks Skriss, l will configure restic and delete mongodb and redeploy

Hi Skriss, have tried but still, no luck can you pls advice
Reinstalled the velero with restic as below, redeployed the mongodb but still pvc is not backup
velero install --provider aws --bucket appops-backup --secret-file ./minio.credentials --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://<IP_ADDRESS>:32252 --use-restic --wait
kubectl -n velero-backup-test annotate pod/mongodb-app-ibm-mongodb-dev-b9bb86f56-qqfr4 backup.velero.io/backup-volumes=mongodb-mongodb-ibm-appops-pvc-new
velero create backup devtest-mongodb --selector release=mongodb-app-ibm-mongodb-dev-b9bb86f56-qqfr4 --snapshot-volumes=true
hostname:~# kubectl get pod -n velero
NAME                     READY   STATUS    RESTARTS   AGE
minio-6db48c5f4d-vb9f5   1/1     Running   0          14d
restic-8fc5p             1/1     Running   0          3h35m
restic-9hdxr             1/1     Running   0          3h35m
restic-gwfg9             1/1     Running   0          3h35m
velero-db6459bb-9cbfb    1/1     Running   0          3h35m
hostname:~#
hostname:~# kubectl get pod -n velero-backup-test
NAME                                          READY   STATUS    RESTARTS   AGE
mongodb-app-ibm-mongodb-dev-b9bb86f56-qqfr4   1/1     Running   0          140m
hostname:~# kubectl get pvc -n velero-backup-test
NAME                                 STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
mongodb-mongodb-ibm-appops-pvc-new   Bound    pvc-c92d61ad-d0ab-11e9-8dc5-005056bf5e2a   2Gi        RWO            glusterfs      3h12m
hostname:~# kubectl describe pod mongodb-app-ibm-mongodb-dev-b9bb86f56-qqfr4 -n velero-backup-test
Name:               mongodb-app-ibm-mongodb-dev-b9bb86f56-qqfr4
Namespace:          velero-backup-test
Priority:           0
PriorityClassName:
Node:               <IP_ADDRESS>/<IP_ADDRESS>
Start Time:         Fri, 06 Sep 2019 20:02:01 +0530
Labels:             app=mongodb-app-ibm-mongodb-dev
chart=ibm-mongodb-dev
heritage=Tiller
pod-template-hash=b9bb86f56
release=mongodb-app
Annotations:        backup.velero.io/backup-volumes: mongodb-mongodb-ibm-appops-pvc-new
kubernetes.io/psp: ibm-anyuid-hostpath-psp
productID:
productName: MongoDB
productVersion: 3.6.0
Status:             Running
IP:                 <IP_ADDRESS>
Controlled By:      ReplicaSet/mongodb-app-ibm-mongodb-dev-b9bb86f56
Containers:
mongodb-app-ibm-mongodb-dev:
Container ID:   docker://51a0c2cfbb2a326c71a1e8dc98073043646ae9c31cd25939d248e2c82df17838
Image:          ibmcom/mongodb:3.6.0
Image ID:       docker-pullable://ibmcom/mongodb@sha256:e9e6d153d05c2500922d1c159fdf11303e3cc4d0eda66fbea5d832883f383d87
Port:           27017/TCP
Host Port:      0/TCP
State:          Running
Started:      Fri, 06 Sep 2019 20:02:03 +0530
Ready:          True
Restart Count:  0
Limits:
cpu:     2
memory:  4Gi
Requests:
cpu:      100m
memory:   256Mi
Liveness:   exec [mongo --eval db.adminCommand('ping')] delay=180s timeout=5s period=10s #success=1 #failure=3
Readiness:  exec [mongo --eval db.adminCommand('ping')] delay=180s timeout=1s period=10s #success=1 #failure=3
Environment:
LICENSE:           accept
MONGODB_USERNAME:  mongo
MONGODB_PASSWORD:  <set to the key 'password' in secret 'mongodb-app-ibm-mongodb-dev'>  Optional: false
MONGODB_DATABASE:  admin
Mounts:
/data/db from mongodb-app-ibm-mongodb-dev-datavolume (rw)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-6g7p4 (ro)
Conditions:
Type              Status
Initialized       True
Ready             True
ContainersReady   True
PodScheduled      True
Volumes:
mongodb-app-ibm-mongodb-dev-datavolume:
Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName:  mongodb-mongodb-ibm-appops-pvc-new
ReadOnly:   false
default-token-6g7p4:
Type:        Secret (a volume populated by a Secret)
SecretName:  default-token-6g7p4
Optional:    false
QoS Class:       Burstable
Node-Selectors:
Tolerations:     node.kubernetes.io/memory-pressure:NoSchedule
node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
hostname:~# velero backup get
NAME              STATUS      CREATED                         EXPIRES   STORAGE LOCATION   SELECTOR
devtest-mongodb   Completed   2019-09-06 20:20:58 +0530 IST   29d       default            release=mongodb-app-ibm-mongodb-dev-b9bb86f56-qqfr4
hostname:~# velero describe backup devtest-mongodb
Name:         devtest-mongodb
Namespace:    velero
Labels:       velero.io/storage-location=default
Annotations:
Phase:  Completed
Namespaces:
Included:  *
Excluded:
Resources:
Included:        *
Excluded:
Cluster-scoped:  auto
Label selector:  release=mongodb-app-ibm-mongodb-dev-b9bb86f56-qqfr4
Storage Location:  default
Snapshot PVs:  true
TTL:  720h0m0s
Hooks:
Backup Format Version:  1
Started:    2019-09-06 20:20:58 +0530 IST
Completed:  2019-09-06 20:21:04 +0530 IST
Expiration:  2019-10-06 20:20:58 +0530 IST
Persistent Volumes:
hostname:~#

Can you show the output of kubectl -n velero-backup-test describe pod mongodb-app-ibm-mongodb-dev-b9bb86f56-qqfr4?
Also, you don't need the --snapshot-volumes flag on velero backup create - I don't think it should be causing an issue, but please drop it from the command just to be sure.

hostname:~# kubectl -n velero-backup-test describe pod mongodb-app-ibm-mongodb-dev-b9bb86f56-5w9d2
Name:               mongodb-app-ibm-mongodb-dev-b9bb86f56-5w9d2
Namespace:          velero-backup-test
Priority:           0
PriorityClassName:
Node:               <IP_ADDRESS>/<IP_ADDRESS>
Start Time:         Sat, 07 Sep 2019 23:52:08 +0530
Labels:             app=mongodb-app-ibm-mongodb-dev
chart=ibm-mongodb-dev
heritage=Tiller
pod-template-hash=b9bb86f56
release=mongodb-app
Annotations:        kubernetes.io/psp: ibm-anyuid-hostpath-psp
productID:
productName: MongoDB
productVersion: 3.6.0
Status:             Running
IP:                 <IP_ADDRESS>
Controlled By:      ReplicaSet/mongodb-app-ibm-mongodb-dev-b9bb86f56
Containers:
mongodb-app-ibm-mongodb-dev:
Container ID:   docker://9113a7fec5273e1b2edb3a1a2101b94b05dfcc48f2640a7bd3384c6f163fa877
Image:          ibmcom/mongodb:3.6.0
Image ID:       docker-pullable://ibmcom/mongodb@sha256:e9e6d153d05c2500922d1c159fdf11303e3cc4d0eda66fbea5d832883f383d87
Port:           27017/TCP
Host Port:      0/TCP
State:          Running
Started:      Sat, 07 Sep 2019 23:53:31 +0530
Last State:     Terminated
Reason:       Error
Exit Code:    100
Started:      Sat, 07 Sep 2019 23:53:10 +0530
Finished:     Sat, 07 Sep 2019 23:53:10 +0530
Ready:          True
Restart Count:  3
Limits:
cpu:     2
memory:  4Gi
Requests:
cpu:      100m
memory:   256Mi
Liveness:   exec [mongo --eval db.adminCommand('ping')] delay=180s timeout=5s period=10s #success=1 #failure=3
Readiness:  exec [mongo --eval db.adminCommand('ping')] delay=180s timeout=1s period=10s #success=1 #failure=3
Environment:
LICENSE:           accept
MONGODB_USERNAME:  mongo
MONGODB_PASSWORD:  <set to the key 'password' in secret 'mongodb-app-ibm-mongodb-dev'>  Optional: false
MONGODB_DATABASE:  admin
Mounts:
/data/db from mongodb-app-ibm-mongodb-dev-datavolume (rw)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-6g7p4 (ro)
Conditions:
Type              Status
Initialized       True
Ready             True
ContainersReady   True
PodScheduled      True
Volumes:
mongodb-app-ibm-mongodb-dev-datavolume:
Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName:  mongodb-mongodb-ibm-appops-pvc-new
ReadOnly:   false
default-token-6g7p4:
Type:        Secret (a volume populated by a Secret)
SecretName:  default-token-6g7p4
Optional:    false
QoS Class:       Burstable
Node-Selectors:
Tolerations:     node.kubernetes.io/memory-pressure:NoSchedule
node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:

@vkrishr I don't see the Velero restic annotation on your pod. You need to do something like the following:
kubectl -n velero-backup-test annotate po/mongodb-app-ibm-mongodb-dev-b9bb86f56-5w9d2 backup.velero.io/backup-volumes=mongodb-app-ibm-mongodb-dev-datavolume
Once you do that, you should be able to get restic backups.

@skriss Found what is the issue
have used --selector =pvc name hence failed to take volume backup
Now corrected with as below
velero create backup new-deployment-mongo  --selector app=mongodb-app-ibm-mongodb-dev
hostname:~# velero backup describe new-deployment-mongo
Name:         new-deployment-mongo
Namespace:    velero
Labels:       velero.io/storage-location=default
Annotations:
Phase:  Completed
Namespaces:
Included:  *
Excluded:
Resources:
Included:        *
Excluded:
Cluster-scoped:  auto
Label selector:  app=mongodb-app-ibm-mongodb-dev
Storage Location:  default
Snapshot PVs:  auto
TTL:  720h0m0s
Hooks:
Backup Format Version:  1
Started:    2019-09-10 15:42:16 +0530 IST
Completed:  2019-09-10 15:45:44 +0530 IST
Expiration:  2019-10-10 15:42:16 +0530 IST
Persistent Volumes:
Restic Backups (specify --details for more information):
Completed:  1

OK great - looks like you were able to get the restic backup taken! I'm going to close this issue, but feel free to reach out again as needed.


[BUG] 'builtin_function_or_method' object is not subscriptable

To Reproduce
class BaseIterator(abc.ABC):
    """Base iterator class for all `*Iterator` classes."""

    _first_fn: Callable[[wt.HANDLE, ctypes.pointer[SizedStructure]], wt.BOOL]
    """Retrieves the first element from an iterator, akin to `iter()`."""

    _next_fn: Callable[[wt.HANDLE, ctypes.pointer[SizedStructure]], wt.BOOL]
    """Retrives the next element from an iterator every time until the end."""

    _dt_type: Type[DataclassMixin]
    """The type of dataclass returned by this iterator."""

    def __init__(self, handle: wt.HANDLE, first_struct: SizedStructure) -> None:
        """Create an iterator wrapping `_first_fn` and `_next_fn`.

        Args:
            handle (wt.HANDLE): Handle to the snapshot.
            first_struct (SizedStructure): Handle to the first instance of the
                underlying structure.
        """
        self._first = True
        self._handle = handle
        self._initial = first_struct

    def _build_dataclass(self) -> _dt_type:
        d = self._dt_type.build(self._initial)
        self._initial.reset_size()
        return d

    def __next__(self) -> _dt_type:
        if self._first:
            if not self._first_fn(
                self._handle, ctypes.byref(self._initial)
            ):  # pragma: no cover
                raise RuntimeError
            self._first = False
            return self._build_dataclass()
        if not self._next_fn(
            self._handle, ctypes.byref(self._initial)
        ):  # pragma: no cover
            if ctypes.get_last_error() == ERROR_NO_MORE_FILES:
                raise StopIteration
            raise RuntimeError
        return self._build_dataclass()

    def __iter__(self) -> Self:
        return self

fails with:
mkdocstrings: 'builtin_function_or_method' object is not subscriptable
  Traceback (most recent call last):
    File "\pytkdocs\cli.py", line 205, in main
      output = json.dumps(process_json(line))
    File "\pytkdocs\cli.py", line 114, in process_json
      return process_config(json.loads(json_input))
    File "\pytkdocs\cli.py", line 91, in process_config
      obj = loader.get_object_documentation(path, members)
    File "\pytkdocs\loader.py", line 360, in get_object_documentation
      root_object = self.get_class_documentation(leaf, members)
    File "\pytkdocs\loader.py", line 483, in get_class_documentation
      merge(attributes_data, get_class_attributes(parent_class))
    File "\pytkdocs\parsers\attributes.py", line 115, in get_class_attributes
      type_hints = get_type_hints(cls)
    File "\Python310\lib\typing.py", line 1804, in get_type_hints
      value = _eval_type(value, base_globals, base_locals)
    File "\Python310\lib\typing.py", line 324, in _eval_type
      return t._evaluate(globalns, localns, recursive_guard)
    File "\Python310\lib\typing.py", line 688, in _evaluate
      eval(self.__forward_code__, globalns, localns),
    File "<string>", line 1, in <module>
  TypeError: 'builtin_function_or_method' object is not subscriptable

Expected behavior
No errors
System (please complete the following information):

pytkdocs version 0.16.1
Python version: 3.10.0
OS: Windows

It seems that ctypes.pointer is simply not subscriptable: you can't use it as a type.

Ahh yes, I changed ctypes.POINTER to ctypes.pointer trying to fix a mypy error, my bad. I think ctypes._PointerLike is what I should use there.


Rails 4.2.1 Header 404 error

Rails 4.2.1 + grape
HTTP/1.1 404 Not Found
Server: openresty
Date: Tue, 05 May 2015 16:15:27 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 183884
Connection: keep-alive
Keep-Alive: timeout=5
Vary: Accept-Encoding
Status: 404 Not Found
X-Request-Id: 883ad0d1-9add-4a0d-bf4e-d45b580a894d
X-Runtime: 0.514069
====================
Rails 4.2  is OK

What's the question?

grape run at Rails 4.2.1 , always responder 404 status
but same app run at  Rails 4.2 is ok.

I upgraded https://github.com/dblock/grape-on-rails to Rails 4.2.1 and everything works as before. Show us the problem please.

Are you trying to demonstrate https://github.com/intridea/grape/issues/1014?

After upgrading to Rails 4.2.1 from 4.2.0
I had to explicitly add format in root api class regardless of format in mounted classes
https://github.com/dblock/grape-on-rails/blob/master/app/api/api.rb

After upgrading to Rails 4.2.1 from 4.2.0
I had to explicitly add format in root api class regardless of format in mounted classes
https://github.com/dblock/grape-on-rails/blob/master/app/api/api.rb

Bump @oncity

Closing, please reopen if you can describe the issue.


Add multi-thread ver olaptablesink for LOAD

Ref https://github.com/apache/incubator-doris/issues/2780#issuecomment-588156273
So we can use
LOAD LABEL ...
        PROPERTIES
        (
        "buffer_num"="5",
        "mem_limit_per_buf"="5368709120",
        "size_limit_per_buf"="62914560"
        );

to use multi-thread version olaptablesink,  to accelerate the time-consuming load.
If we don't set buffer_num or set it to 0, use the origin version(single-thread).

[x] add configuration references

[x] add doc

After talking the matter over, we decided against this multi-thread version. I will submit a new design, just use one sender thread send batches asynchronously.
Thanks for the reviews!


python311Packages.id: 1.3.0 -> 1.4.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.id is: A tool for generating OIDC identities
meta.homepage for python311Packages.id is: https://github.com/di/id
meta.changelog for python311Packages.id is: https://github.com/di/id/blob/1.4.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.4.0 with grep in /nix/store/ry5xnk9k6pkyf7nb478vlnf5svf84s4z-python3.11-id-1.4.0
found 1.4.0 in filename of file in /nix/store/ry5xnk9k6pkyf7nb478vlnf5svf84s4z-python3.11-id-1.4.0

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.aiogithubapi
python311Packages.id
python311Packages.sigstore
python312Packages.aiogithubapi
python312Packages.id
python312Packages.sigstore

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ry5xnk9k6pkyf7nb478vlnf5svf84s4z-python3.11-id-1.4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.id https://github.com/r-ryantm/nixpkgs/archive/a2169b8f59fca53738c49d9dbc206dbdec302378.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a2169b8f59fca53738c49d9dbc206dbdec302378#python311Packages.id

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ry5xnk9k6pkyf7nb478vlnf5svf84s4z-python3.11-id-1.4.0
ls -la /nix/store/ry5xnk9k6pkyf7nb478vlnf5svf84s4z-python3.11-id-1.4.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

12 packages built:

python311Packages.aiogithubapi
python311Packages.aiogithubapi.dist
python311Packages.id
python311Packages.id.dist
python311Packages.sigstore
python311Packages.sigstore.dist
python312Packages.aiogithubapi
python312Packages.aiogithubapi.dist
python312Packages.id
python312Packages.id.dist
python312Packages.sigstore
python312Packages.sigstore.dist

Maintainer pings
cc @fabaff for testing.

Result of nixpkgs-review pr 306708 run on x86_64-linux 1

12 packages built:

python311Packages.aiogithubapi
python311Packages.aiogithubapi.dist
python311Packages.id
python311Packages.id.dist
python311Packages.sigstore
python311Packages.sigstore.dist
python312Packages.aiogithubapi
python312Packages.aiogithubapi.dist
python312Packages.id
python312Packages.id.dist
python312Packages.sigstore
python312Packages.sigstore.dist


GitHub URL Crashes application

Dev Home version
0.503.261.0
Windows build number
10.0.22621.2361
Other software
OS Build Version: 10.0.22621.2361.amd64fre.ni_release.220506-1250
.NET Version: .NET 6.0.21
Steps to reproduce the bug
Add a new repository, enter the url of a GitHub repo which is in an organisation different to main account.
Expected result
Repo should be cloned
Actual result
Application crashes
Included System Information
Physical Memory: 63.77GB (45.85GB free)
Processor Architecture: x64
Included Extensions Information
Extensions:
Microsoft.Windows.DevHome_0.503.261.0_x64__8wekyb3d8bbwe
Microsoft.Windows.DevHomeGitHubExtension_0.501.261.0_x64__8wekyb3d8bbwe

Hello @matty, is it a private repo and does the signed in account have access to it?

Hi @EricJohnson327. This is a private repo and the account has access. I am using the https URL of the repository by entering it in the "URL section" as the "Account" section doesn't show organisation repos.

Hi @EricJohnson327. This is a private repo and the account has access. I am using the https URL of the repository by entering it in the "URL section" as the "Account" section doesn't show organisation repos.

Same in my system. App crashes while adding repos as mentioned above through End-to-end setup -> clone repositories or Clone repositories itself.

Crashing has been fixed.  Please update to the newest version and try again.  If Devhome can't access a repo it will not crash.
#1835 adds a message notifying that no logged in accounts can access the repo.
If this is still crashing after upgrading to the most recent version, please re-open this bug.


datepicker can not change the language?

jquery ui datepicker

Datepicker control changed to Spanish
How to change ah, the default setting language changed, jquery ui datepicker or English


Pass room names in lowerCase to fix #89

Potentially fixes https://github.com/palavatv/palava-web/issues/89, not sure if wanted from a product perspective though - as described in the issue it makes some users wonder "why this software doesn't work", but it also kinda increases the possibility for name-clashes of roomIds

Hey, thanks for the suggestion! I can understand the problem and I think I am slightly in favor of switching to case-insensitve room names. I have one remark / side-node (it's kind of offtopic to this PR, but somewhat relevant):
I have the idea of changing the current auto-generated room names from the UUID-like naming schema to shorter tokens, a little bit like the YouTube IDs. The great thing if we keep the current case-sensitive room IDs would be that the short tokens could be even shorter, because single characters carry more information.
What do all think about this? @farao @KopierKatze @paulgoetze @juwi

Does anyone has an opinion here? :)

Closing as not actionable and to be discussed in #123


Rendering twice when first page is loaded

Describe the bug
Hello, thanks for all the hard work on this project.
I was working with the simple example and I noticed an intermittent issue that seems to be occurring in both Chrome and FF. When any page is initially loaded, it looks like the pages are occasionally rendered twice. This seems to be only occurring for me on the client side.
This can be reproduced by duplicating the simple example and inserting a console.log in the main component in any page (Homepage and SecondPage components in the example). Doing a hard refresh on the page a few times (less than 10 in my case) is usually sufficient to show the console.log displaying twice on the client side. In these cases the server will show only a single log message, while the client shows the log message twice.
I also noticed whenever the double render occurs the client side network traffic shows 21 requests. When it is functioning correctly (only a single render/log message) there are only 20 requests. The extra file in the double render situation is common.json.
Occurs in next-i18next version
4.4.2
Steps to reproduce

Duplicate the example/simple found in the repo.
Add a console.log("page rendered") just above the return statement in the main page component for both pages (index.js and second-page.js - screenshots for reference).
Launch the application and do a hard refresh until the console logs display "page rendered" twice in a row.

Expected behaviour
Expected behaviour is that the "page rendered" log message would only show once after a hard refresh.
Screenshots
package.json

page component with console.log

Single render (expected behavour)

Double render

OS (please complete the following information)

Device: MBP 2015 15"
Browser: Chrome 83.0.4103.97, Firefox 77.0

Looks like common.json is getting loaded in, in the second case, indicating the translations for some reason are not present. Can you reproduce this in prod mode, or just dev?

Thanks for the quick response. It looks like it's happening in both dev and prod mode. It seems much less frequent in prod with Chrome. However, the double render is happening on every reload in FF with prod mode.

I do see two render cycles in prod, as you described. However, I am not concerned about this on its own - this could be caused by any number of things.
I would be concerned if common.json was being fetched after a client side load in prod, but I cannot reproduce that behaviour.


update to use az-identity 1.7.0-beta.1

Update the azure-identity version to 1.7.0-beta.1 for passwordless usages.

/azp run java - spring - ci

/azp run java - spring - ci

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-identity-providers-core


The description of "Mailbox type limitations" section is not appropriate

I can understand that the on send feature is not supported for the following 3 scenario.

Shared mailbox
Offline mode
Group mailbox

But, the offline mode is not "Mailbox type". And the usage of the shared mailbox and the group mailbox is completely different. Therefore, it is not appropriate to describe these 3 scenarios at the same time.
The behavior for each scenario is as follows:

Shared mailbox scenario

If User A have the full access right of User B, User A can open User B's  mailbox using Ootw.
In this scenario, User A cannot send mail if OnSendAddinsEnabled is set to True for the policy that is set to User B.

Offline mode scenario

Basically, because the contents of the add-ins such as JavaScrip file, CSS file and HTML file are not cached in the client computer, the on send feature cannot work and the user cannot send mail in this scenario.
Depending on the behavior of browser software, the user might be able to use the add-in because it caches the contents of the add-in. However, the mail is not actually sent because Ootw is in the offline mode.

Group mailbox

The user cannot open the group mailbox in the same way as the shared mailbox. The Ootw user can access the group mailbox as the Office 365 Group.
The OnSendAddinsEnabled enabled user can post a message to the Office 365 Group. The user can reply to the existing Office 365 Group thread, too.

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

ID: 423fb893-bedd-e004-5102-c13c4bea8d50
Version Independent ID: f28b807f-0f3b-0bf5-c967-257fc55ec7f9
Content: On send feature for Outlook add-ins - Outlook Developer
Content Source: docs/add-ins/outlook-on-send-addins.md
Product: outlook
GitHub Login: @jasonjoh
Microsoft Alias: jasonjoh

@rykoma thank you for the feedback about this article. We'll look into this and will update the article as appropriate.

@ElizabethSamuel-MSFT looks like you've updated this article in recent months; can you please look into this issue? Thanks!

@rykoma: We've updated the article and the change should go live soon (likely later this week). Thanks again for your feedback!


Flutter Web: Regression - Widgets have random ghosting behavior  in master and dev branch -- Can be observed with Link widget but applies to others as well

Took me a while to figure out why my app was breaking and I wasn't getting any errors describing why. In the stable branch, Flutter is using version 6.0.3 of the Link widget from url_launcher, which seems to work fine. But when moving to dev and master that both use version 6.0.10 of the Link widget, weird things happen. Code example is provided below. I also tried changing the version of url_launcher back to 6.0.3 on master branch to downgrade it from 6.0.10 and it still did not work.
Expected behavior: Scrolling to work normally as it does in stable.
Actual behavior: After scrolling and reaching the footer and scrolling back up, the last image that was rendered makes a ghost rendering of itself that persists as you scroll back up, the route using the Link widget in the AppBar moves out of place or disappears altogether, and a ghost rendering of the AppBar is created. Scrolling is generally buggy. When removing the link widget, everything works normally. Functionality of the Link widget does not seem to be affected as clicking the button still navigates to the right link. It's just causing major rendering issues across the application for some reason.
[✓] Flutter (Channel master, 2.6.0-1.0.pre.191, on macOS 11.5.2 20G95 darwin-arm, locale en-US)
    • Flutter version 2.6.0-1.0.pre.191 at /Users/khari/Documents/dev/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 81142c1f9a (6 hours ago), 2021-09-05 00:41:02 -0400
    • Engine revision dbc97a09b4
    • Dart version 2.15.0 (build 2.15.0-82.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/khari/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.5)
    • Xcode at /Applications/Xcode-beta.app/Contents/Developer
    • CocoaPods version 1.10.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code (version 1.60.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.26.0

[✓] Connected device (2 available)
    • iPhone 12 Pro Max (mobile) • 175F58A7-794B-44B9-85FE-D67E9879E190 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 92.0.4515.159

import 'package:flutter/material.dart';
import 'package:url_launcher/link.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      home: MyHomePage(),
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
    );
  }
}

class MyHomePage extends StatelessWidget {
  const MyHomePage({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: RawScrollbar(
        thickness: 9,
        radius: const Radius.circular(15),
        child: CustomScrollView(
          slivers: [
            SliverAppBar(
              floating: true,
              automaticallyImplyLeading: false,
              expandedHeight: 252,
              backgroundColor: Colors.white,
              flexibleSpace: FlexibleSpaceBar(
                collapseMode: CollapseMode.pin,
                background: Column(
                  children: [
                    const SizedBox(height: 18),
                    Container(
                      padding: const EdgeInsets.symmetric(vertical: 18),
                      decoration: const BoxDecoration(
                        border: Border.symmetric(
                          horizontal: BorderSide(
                            color: Colors.red,
                            width: 2.0,
                          ),
                        ),
                      ),
                      width: 1080,
                      child: const Padding(
                        padding: EdgeInsets.symmetric(horizontal: 18.0),
                        child: _NavButtons(),
                      ),
                    ),
                  ],
                ),
              ),
            ),
            SliverToBoxAdapter(
              child: _PageBody(),
            ),
            const SliverToBoxAdapter(child: _Footer())
          ],
        ),
      ),
    );
  }
}

class _NavButtons extends StatelessWidget {
  const _NavButtons({
    Key? key,
  }) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Row(
      mainAxisAlignment: MainAxisAlignment.spaceEvenly,
      children: [
        Link(
            // Sometimes randomly disappears
            uri: Uri.parse("https://www.google.com"),
            builder: (context, func) =>
                TextButton(onPressed: func, child: Text("Route1"))),
        Text("Route2"),
        Text("Route3"),
        Text("Route4")
      ],
    );
  }
}

class _PageBody extends StatelessWidget {
  _PageBody({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Column(
      children: [
        SizedBox(
          height: 600,
          width: 300,
          child: Image.network(
            "https://images.unsplash.com/photo-1526336024174-e58f5cdd8e13?ixid=MnwxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8&ixlib=rb-1.2.1&auto=format&fit=crop&w=3334&q=80",
          ),
        ),
        SizedBox(
          height: 600,
          width: 300,
          child: Image.network(
            "https://images.unsplash.com/photo-1526336024174-e58f5cdd8e13?ixid=MnwxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8&ixlib=rb-1.2.1&auto=format&fit=crop&w=3334&q=80",
          ),
        ),
        SizedBox(
          height: 600,
          width: 300,
          child: Image.network(
            "https://images.unsplash.com/photo-1526336024174-e58f5cdd8e13?ixid=MnwxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8&ixlib=rb-1.2.1&auto=format&fit=crop&w=3334&q=80",
          ),
        ),
      ],
    );
  }
}

class _Footer extends StatelessWidget {
  const _Footer({Key? key}) : super(key: key);
  @override
  Widget build(BuildContext context) {
    return Container(
      width: MediaQuery.of(context).size.width,
      color: Colors.blue,
      height: 250,
      child: Center(
        child: TestButton(),
      ),
    );
  }
}

class TestButton extends StatelessWidget {
  const TestButton({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    const _testUrl = "https://google.com";
    return Link(
      target: LinkTarget.blank,
      uri: Uri.parse(_testUrl),
      builder: (
        BuildContext context,
        Future<void> Function()? followLink,
      ) =>
          TextButton(
        style: TextButton.styleFrom(
            padding: const EdgeInsets.all(
              18,
            ),
            backgroundColor: Colors.black,
            shape:
                RoundedRectangleBorder(borderRadius: BorderRadius.circular(9))),
        onPressed: followLink,
        child: Text(
          "Breaks Here When Reached",
        ),
      ),
    );
  }
}

So I removed the Link widget from my app, and while It did stop this exact error from occurring on the homepage of my app, this issue is still prevalent throughout my application.
Even thought this widget causes the issues with scrolling and ghosting, I am noticing ghost widgets (widgets stuck on the screen and not changing position while the rest of the application scrolls normally) in other parts of my application that I did not have before. Everything from widgets appearing on top of the SliverAppBar while scrolling to widgets from a previous page loaded over top of new pages that are being navigated to. There are times when I scroll where the application will act as if it has scrolled to the bottom but none of the widgets from the initial position have changed at all. The ghost widgets paint on top of everything so dropdowns are not visible when clicked on if a ghost widget is on top of it. However, even in this case, flutter still recognizes the clicks on my drop down menu as clicking it retains the correct functionality.
There's no way right now that Flutter web for me is usable on the master branch. I've re-downloaded flutter 3 times and it happens every time when switching to the mater branch. I believe this framework issue is deeper than just this widget but for some reason the widget easily triggers this bug. The ghosting and unexpected behavior

Hi, I think this is the same as what I've come across a few days back and you can check and see if it happens at the same version. https://github.com/flutter/flutter/issues/88688 and hopefully will be fixed in the same work in https://github.com/flutter/flutter/issues/86809. Do you get the same errors in your Dev Tools as I had?

Hi, I think this is the same as what I've come across a few days back and you can check and see if it happens at the same version. #88688 and hopefully will be fixed in the same work in #86809. Do you get the same errors in your Dev Tools as I had?

Different errors but same behavior. @yjbanov mentioned issues with the link widget in #86809 but I'm getting this behavior throughout my application at random it seems. Widgets like Link just make it worse.

Hi @khari998
It looks like a duplicate of https://github.com/flutter/flutter/issues/88688, reproducible test might be different but cause looks the same

@khari998 I verified the latest changes to master fix the issues you describe on your app, please give it another shot with flutter channel master!
dit@dit:~/github/repro-cases/issue_89497$ flutter --version
Flutter 2.6.0-6.0.pre.76 • channel master • git@github.com:ditman/flutter.git
Framework • revision fad5e4cf89 (22 minutes ago) • 2021-09-13 13:37:07 -0700
Engine • revision abb1980f65
Tools • Dart 2.15.0 (build 2.15.0-96.0.dev)


Add toss a coin

Add toss a coin and do update the README.md too

I could work on this task.

I could work on this task.

Assigned


HttpResponseData error

This tutorial is not working. The code below throws an error for the HttpResponseData and fails to run the update application. This is a public tutorial and yet it fails to meet the minimum requirements for a working environment.
public class MultiResponse
{
[CosmosDBOutput("my-database", "my-container",
Connection = "CosmosDbConnectionSetting", CreateIfNotExists = true)]
public MyDocument Document { get; set; }
public HttpResponseData HttpResponse { get; set; }
}
public class MyDocument {
public string id { get; set; }
public string message { get; set; }
}

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

ID: 62965f3a-d852-cbe8-3d01-a5126a16c660
Version Independent ID: 2af2bfc6-bf21-08c6-a874-467781a4af90
Content: Connect Azure Functions to Azure Cosmos DB using Visual Studio Code
Content Source: articles/azure-functions/functions-add-output-binding-cosmos-db-vs-code.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@LucaOtto
Thanks for your feedback! We will investigate and update as appropriate.

Apologies for the late reply @LucaOtto. This tutorial expects that you've already created a C# function app that uses .NET 8 Isolated. That project includes several package references, like Microsft.Azure.Functions.Worker.Core library which includes the HttpResponseData class. To get your sample to work, you can include this package reference in your csproj.
#please-close


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-25-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3613

Questions ?
Please refer to the Backport tool documentation


add ZEC t-address

Hello, I'd like to add ZEC transparent address wallet support, it's an easy integration. The z-shielded address needs more work. Anyway great project, congrats

Thank you!


More Verify Visibility

Add more messaging so it's apparent what steps are being run during molecule verify
Add line breaks between steps to help separate them visually
Standardize color (magenta) for verify messaging

:+1:
But the magenta color is close to red, don't you think it could be associated with an error instead of an information?

It's hard to say with terminal colors because people can configure their terminal programs to render colors however they want. My magenta and red look way different personally.  As far as defaults go, I think the two colors are different enough not to be an issue.


UnhandledPromiseRejectionWarning

Hi,
I am getting an error while fetching android package details :-1:
Package name:-  com.tvappagency.WeatherNation
this is an valid package .
Play store Url:-
https://play.google.com/store/apps/details?id=com.tvappagency.WeatherNation

This is app-store-scraper not google-play-scraper.


Support docker compose plugin to justfile

The Docker compose plugin way:
docker compose up

The Docker compose standalone way:
docker-compose up

Is there one way to support them both? I tried many in justfile but all failed.

I think we may need to test if the system has a docker-compose, and if it does not, use docker compose - something similar to the check we have in the cargo-install just command - but do it once when just starts up?

A temporary workaround could be to add an alias to bash

This is a common problem, that will still remain some years, until docker compose is the only command.
We solved this in a workshop launch control Bash script like @nyurik indicated: sniff for the variant and set an alias. See these lines i.e.:
# Sniff which Docker Compose variant is installed
# and set an alias.
# See https://github.com/geopython/geopython-workshop/issues/82
if command docker-compose --version &> /dev/null
then
  alias dockercompose='docker-compose'
  echo "Using docker-compose"
else
  if !command docker compose version &> /dev/null
  then
    echo "Neither docker-compose nor docker compose is available"
    echo "Check your Docker Installation"
    exit 1
  fi
  alias dockercompose='docker compose'
  echo "Using docker compose"
fi

..and then use the alias dockercompose. Never heard of just (other than my first name..) but seems something to be added in the justfile as bash is presumed? Will PR...

The approach above does not really work direct in a justfile because of the 'just-syntax'. But figured out an alternative, using standard var and -substitution, so an approach with oneliner:
dockercompose := `if docker-compose --version &> /dev/null; then echo "docker-compose"; else echo "docker compose"; fi`
.
.
up:
   {{ dockercompose }} up

up-build:
    {{ dockercompose }} up --build
.
.

There is a justfile in the repo root and the demo dir. Will go ahead with this approach.


Sanitize Style tab data by parsing it with Markdown

Initial code pass at Style data sanitization via Markdown parsing.

I'm not sure this solves the root problem as we've been discussing on the Gitter. Instead we probably need to use a separate sanitizer script. From Marked.js : "Instead use a sanitize library, like DOMPurify (recommended), sanitize-html or insane on the output HTML!"

I believe you are correct - none of these changes have been changing the result of the test cases, as we've seen in the Gitter chat.

Probably the first thing we need to solve is getting the title to be cloned at all.

Closing this PR as Markdown is not the correct way to sanitize the CSS.


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit 21727be:
:clock10: Pending: waiting for processors (24 builds ahead of you)
:warning: Docs Build is busy, currently there are 24 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 21727be:
:clock10: Full build: the average full build time is 7 min(s) 53 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 21727be:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


feat: scroll to top when registration state changes

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


The client reconnects during long-time receiving frequent messages.

Bug report
Describe the bug
If the server pushes many messages, for example, if DB has inserted 100k rows, the client will reconnect after ~40-120 sec.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Launch http://localhost:3000/stress
Open browser DevTools
Execute 100000
Wait for a little for the new message Connecting in the console

Expected behavior
The client doesn't disconnect while receiving messages.
Screenshots

System information

OS: macOS Big Sur
Browser: Google Chrome 88.0.4324.150 (Official Build) (x86_64)
Version of supabase-js: 1.0.6
Version of Node.js: v12.16.1

Additional context
I suppose this is because the client can't receive a response to the heartbeat message. Server process too busy because of a lot of messages in the message box.
The solution can be to reset the heartbeatTimer on receiving any message.  If we've just gotten the message, everything is ok with the server connection, and heartbeat is unnecessary, right?

@abc yep, I saw this while doing my tests for RAM explosion on huge # of inserts #125 issue b/c I was also doing 100k inserts. Thanks for reporting this! Let me take a look.

@abc3 apologies for not tackling this issue sooner!
Let me know what you think of PR #80.


Usage of keypoint visibility in the generation of keypoint_maps and paf_maps

Hi @Daniil-Osokin,
Again, thanks for sharing this great work!
I was checking your training code and wasn't sure about the following lines:
https://github.com/Daniil-Osokin/lightweight-human-pose-estimation.pytorch/blob/411ff9fd5f6125e1879cb73f6b4f90090184edad/datasets/coco.py#L71-L87
Is keypoint[2] stands for the visibility of a joint? If so, then in coco:
if visibility == 0 that keypoint not in the image.
if visibility == 1 that keypoint is in the image BUT not visible namely maybe behind of an object.
if visibility == 2 that keypoint looks clearly. not hidden.
Why you choose to add gaussian for those unavailable and occluded joints while ignore the visible ones?

Hi, code uses converted annotations, so initial COCO keypoint visibility value changed to internal one. Actually there is no need to convert visibility in this way, it is just a legacy.

@Daniil-Osokin
Got it, thank you.

got it


KAFKA-5716: Recent polled offsets may not be written/flushed at SourceTask.commit

@rhauch @tedyu @hachikuji
For now a test showing that the claimed problem is true. Should definitely not be committed - its a failing test. It fails trying to assert SourceTask.commit javadoc: Commit the offsets, up to the offsets that have been returned by {@link #poll()}
The contribution is my (@steff1193) original work and I license the work to the project under the project's open source license.

@matthedude Maybe you want to vote for KAFKA-5716?


Migrate away from JCenter

JFrog has announced that it will be shutting down JCenter on February 2nd 2022. JCenter is the sole repository hosting this library, so it will become unavailable after this date unless migrated to an alternative service.

Need to close this issue since it's already on mavenCentral
https://mvnrepository.com/artifact/com.github.pengrad/jdk9-deps/1.0

Awesome, thanks!

@jboxx according to that link, this library is only on JCenter:

There's no entry for it under the author's group ID on Maven Central

Update: JCenter will remain up indefinitely as a read-only repository.


Increase the amount the faucet mints to at least 1k?

Is your feature request related to a problem? Please describe.
It comes from here
https://discord.com/channels/799672011265015819/1176889593136693339/1243454643569299477
Describe the solution you'd like
Since creating a network (for test purposes) costs 1000, you have to do the “faucet” several times. This makes the testing process much more difficult.
There are 2 obvious solutions:

increase the amount the faucet mints to 1k
implement an additional parameter “--test” for the “faucet” command, which will return 1k faucet mints.

Describe alternatives you've considered
Leave it as is and waste time during testing

Implement --amount so another flag does not need to be created if someone wants just 100 or needs 2k


 causes console warning: "Invalid value for prop `navigate`..."

A quirk of using the V5.1 component prop of <Link> is that the component receives a navigate prop (which is helpful in some use-cases!) but if you passthrough that prop to a DOM component, then you'll get a React warning message in the console.
A workaround is simple: just strip out navigate before passing the props to any underlying component. Like this:
const CustomLink = props => {
  const { navigate, ...rest } = props;
  return (<a {...rest} />);
}

But it was unexpected to have to wrap my existing components to strip that prop, because I'd assumed that I could use existing <a>-based components as-is.
This behavior is on the boundary of a bug report and a feature request, because I'm not sure if it's expected to always have to wrap existing components. Is it expected?  Or is there something that react-router should do to prevent this React warning without requiring components to strip out the navigate prop?
This requirement (to strip out navigate before passing props to DOM) seems worth documenting when the component prop is documented.  In the meantime, I'm filing this issue to make it easy for folks to Google when they run into the same console warning.
Version
5.1.2 (on React 16.10.1)
Test Case
https://codesandbox.io/s/dank-waterfall-f0myq
import React from "react";
import ReactDOM from "react-dom";
import { Link, BrowserRouter } from "react-router-dom";

const CustomLink = props => <a {...props} />;
const App = () => (
  <BrowserRouter>
    <Link component={CustomLink} to={"/"}>Link</Link>
  </BrowserRouter>
);

ReactDOM.render(<App />, document.getElementById("root"));

Steps to reproduce

Load that page in the browser OR click the link in the page
Look at the console

Expected Behavior
No errors or warnings in the console
Actual Behavior
Warning: Invalid value for prop `navigate` on <a> tag.
Either remove it from the element, or pass a string or
number value to keep it in the DOM. For details, see
https://fb.me/react-attribute-behavior
    in a (at src/index.js:5)
    in CustomLink (created by Context.Consumer)
    in Link (at src/index.js:10)
    in Router (created by BrowserRouter)
    in BrowserRouter (at src/index.js:9)
    in App (at src/index.js:17)

We went through this same thing when React 16 landed. Much of the community needed to update to better handle props passing, as they were doing it unsafely. You shouldn't be passing them along blindly, especially to DOM elements.

Sounds right, thanks.


Added pfx to the "HTTPS options restore" section

I've merged the commit fixing the DeprecationWarning on retry and then added pfx to the fixed options.
Commit: https://github.com/markdboyd/got/commit/9a309bdbe7e2552c5bffbea253d58c39d6e6c3e3
Comment on PR: https://github.com/sindresorhus/got/pull/1364#issuecomment-682592072

Sorry, opened on the wrong branch


Detect unclosed ZiplineServices on iOS

We’ve already done it for JS and Android:
https://github.com/cashapp/zipline/issues/302
For native it’s still a TODO:
https://github.com/cashapp/zipline/blob/trunk/zipline/src/nativeMain/kotlin/app/cash/zipline/internal/bridge/leakCanaryNative.kt#L27

There’s a function called deinit on iOS that can do it.

Discussed today. Decision is to try to use WeakReference.
https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.native.ref/#:~:text=WeakReference,destroyed by the memory manager.


Doesn't work with Laravel Sanctum

Echo Version
1.0.3
Laravel Version
10.10
PHP Version
8.2
NPM Version
10.2
Database Driver & Version
No response
Description
Hi,
To be able to work with Laravel Sanctum, we should be able to to set a custom authoriser (axis) which is predefine for a cross-domain requests, similar as we need for Pusher (please check: https://laravel.com/docs/10.x/sanctum#authorizing-private-broadcast-channels)
But this is not possible if using Laravel Echo from Ably as there isn't an option to do so and you're getting "CSRF token mismatch." error when you try to auth to private channel.
I've tried to set csrfToken and bearerToken but it didn't worked.
Steps To Reproduce

Install new Laravel installation
Install Laravel Sanctum package
Install Laravel Echo from Ably
Follow instructions to setup Broadcast rules

@zoranlorkovic thanks for raising the issue. We will look into adding support for the same.

@sacOO7 do you have any planned date for the release? We are blocked with this error, any alternative solution? TIA

@KalanaPerera let me check if there is a way to use this feature without making explicit changes to the code

@zoranlorkovic @KalanaPerera It seems we already have a solution here, you need to pass requestTokenFn as an argument
echo = new Echo({
        broadcaster: 'ably',
        useTls: true,
        requestTokenFn: async (channelName: string, existingToken: string) => {
            let postData = { channel_name: channelName, token: existingToken };
            return await axios.post("/api/broadcasting/auth", postData);
        },
});

Basically this code is equivalent of
https://github.com/ably-forks/laravel-echo/blob/85f4dbcc01f8f54d5127a067a2ca1dc2f509cc22/src/channel/ably/auth.ts#L34-L49
I think we don't need to provide extra headers in case of axios. I will update README for the same.

@zoranlorkovic wait a minute, let me check on this 🙂

We have customized endpoint api/broadcasting/auth in case of ably-laravel-broadcaster. So, it will be a difference response than pusher one. It does expects existing token and channelName. As far as socket_id is concerned, it's automatically set by axios as a header here ->
https://github.com/ably-forks/laravel-echo/blob/85f4dbcc01f8f54d5127a067a2ca1dc2f509cc22/src/echo.ts#L157-L165
So, it will be implicitly read by the endpoint internally. We should know it, at the top level everything should work fine.

Also, don't forget to star both repos https://github.com/ably/laravel-broadcaster and https://github.com/ably-forks/laravel-echo/.
Ask your colleagues to do so too :P. We are looking for devs like you to raise issues like this with us :  )

Ah, you're right, sorry about that. I was looking at default Laravel api/boradcasting/auth endpoint.
I've just checked yours and indeed it does expect channel_name and token.
And it seems it does sends correct channel name when subscribing as I've noticed that in first call it makes to api/broadcasting/auth it's sending data:
{"channel_name":"private:App.Models.User.1","token":null}
but on every other request which is making every 45s or so it's just sending this data:
{"channel_name":null}

Okay, let me check that one too 👍

Hi @zoranlorkovic
By any chance did you set token expiry as 1 minute as per https://github.com/ably/laravel-broadcaster/tree/main#configure-advanced-features ?
If that's the case, it will try to renew the token every 1 minute. In such a case, no new channel is being authenticated, rather existing channels from existing_token will be re-authenticated

For every new channel.private()(private channel)  or channel.join()(presence channel), it will always send channel_name in the request.

Okay, is this still happening after making this change
        requestTokenFn: async (channelName: string, existingToken: string) => {
            let postData = { channel_name: channelName, token: existingToken };
            const res = await axios.post("/api/broadcasting/auth", postData);
            return res.data;
        },

Note that, we have modified the code to return res.data instead of res

This seems to resolve this issue. Now there are just two requests to api/broadcast/auth:
First one is with data:
{"channel_name":"private:App.Models.User.1","token":null}
result:
{
"token": "returnedToken"
}
Second request:
{"channel_name":null,"token":"returnedTokenFromPreviousRequest"}
result:
{
"token": "returnedTokenSameAsPrevious"
}
Is this excepted result?
Also that message:
Ably: Auth.requestToken(): token request signing call returned error; err = TypeError: undefined is not an object (evaluating 'jwtToken.split') seems to be gone now.

Ah, so sorry, don't know how I missed that additional code you've mentioned in https://github.com/ably-forks/laravel-echo/issues/26#issuecomment-1828234953 !
Repos already starred!

Thanks! Please feel free to raise more issues 👍.
There are no bugs reported in the library so far since the first release.
So, we are eagerly waiting for improvements that can be done to support new trends !!

Thank you for your help and quick replies @sacOO7 !
I've almost call it a day and returned back to Pusher but your quick replies really pushed me to stay and try again. Even after you've sent the solution an hour ago :)


Hide console window of chromedriver.exe

How can I hide the console window of chromedriver.exe? It can be done with Selenium for C# (see https://stackoverflow.com/questions/35818436/hide-silence-chromedriver-window) but I don't know to do with Atata framework

Here is the sample:
AtataContext.Configure().
    UseChrome().
        WithArguments("headless").
        WithDriverService(x => x.HideCommandPromptWindow = true).
    //...
    Build();

Thanks, it works fine.


No Detection Boxes drawn on image from Object_detection_image

Hi all,
As the title says, I'm trying to test my object detector on a specific image using the object_detection_image file, but for some reason, no boxes are being drawn over my image. The boxes array has nonzero elements, so I am assuming (perhaps incorrectly) that the object is being detected? No errors are given when I run it. Has anyone had this issue in the past and is there any way I could further troubleshoot to determine where the root of the problem is? I would love to see some boxes after all the training I did! For reference, I am using the faster_rcnn_inception_v2_coco model from the Tensorflow Model Zoo.

check ur loss during training. there are chances that if u do something wrong, it will just jump into the quadrillions!!

@rsbball11


Remove workarounds from #1240

Let's remove 3 workarounds introduced in #1240 after corresponding PR's/issue will be resolved in SDK:

https://github.com/aeternity/aepp-sdk-js/pull/1249
https://github.com/aeternity/aepp-sdk-js/issues/1261
https://github.com/aeternity/aepp-sdk-js/issues/1266

Current version of wallet doesn't have such problems. Feel free to reopen this issue, if it will pop up again.


Added a reference to the query to options before triggering the counting event

All other pre-sync events include a reference to the query in the options object so you can make changes to the query, this adds that reference for the counting event.

@kevinob11 Nice catch. I just realized that this event is not documented!
Would you be interested in adding documentation here? You just need to add a JSdoc comment, like this one.

Sure #1248


MiKo_1063 is now aware of some more phrases

@CodiumAI-Agent /describe

Title
MiKo_1063 is now aware of some more phrases

User description
@CodiumAI-Agent /describe

PR Type
enhancement, tests

Description

Added new abbreviation mappings for 'ctg' (category), 'ctlg' (catalog), and 'qty' (quantity) in the MiKo_1063_AbbreviationsInNameAnalyzer.
Updated tests to cover the new abbreviation mappings.
Introduced ncrunch code coverage exclusion markers in MiKo_2023_CodeFixProvider.

Changes walkthrough 📝
Relevant filesConfiguration changes

MiKo_2023_CodeFixProvider.csAdd ncrunch code coverage exclusion markers

MiKo.Analyzer.Shared/Rules/Documentation/MiKo_2023_CodeFixProvider.cs
Added ncrunch code coverage markers to exclude specific code blocks.

+3/-1

Enhancement

MiKo_1063_AbbreviationsInNameAnalyzer.csExtend abbreviation mappings in naming analyzer

MiKo.Analyzer.Shared/Rules/Naming/MiKo_1063_AbbreviationsInNameAnalyzer.cs

Added new abbreviation mappings for 'ctg', 'ctlg', and 'qty'.

+6/-0

Tests

MiKo_1063_AbbreviationsInNameAnalyzerTests.csAdd tests for new abbreviation mappings

MiKo.Analyzer.Tests/Rules/Naming/MiKo_1063_AbbreviationsInNameAnalyzerTests.cs
Added tests for new abbreviation mappings 'ctg', 'ctlg', and 'qty'.

+6/-0

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions


Please expose strings for localization

There are a few strings like "Delete Recording", "Cancel" or "Microphone Access Denied!". Could you please expose those so that we can localize them?

okay, great Idea.

Cool, thanks!


I want to use tooltip

Hi, I want to use angularUI tooltip per each item from the multi-select.
I try to do it this way:
$scope.objetivos.push({        id: v.id,        nombre: '' +                         v.nombre +                          '',        ticked: false });
What i am doing wrong? which is the right way to do this?
Thanks!

Hi @joaquinmautone ,
Unfortunately I have no experience in integrating directive within a directive like that. I suspect there's a problem during compilation. Not sure whether AngularJs can compile something like that.


Implement Comprehensive Dojo Storage Benchmarking

In an effort to improve our understanding of storage performance, taking as a base Cairo - add starknet testing methods for measuring performance and snapshotting, we are aiming to introduce benchmarking using unit tests. Our main goal is to isolate and benchmark the pure Dojo storage performance, eliminating any transaction overheads.
Storage Types to be Benchmarked:

Native Storage: Operations without integrating Dojo.
Simple Dojo Storage: Standard operations with the integration of Dojo.
Dojo Packing Storage: Operations with Dojo's packing feature.
Dojo Indexing Storage: Operations using Dojo's indexing.

For a comprehensive understanding of how Dojo performs across different scenarios, benchmarks should be conducted under the following complexities:

Simple Data Structures: Mainly basic structures.
Medium Complexity Data Structures: Intermediate level structures more complex than basic ones but not extremely intricate.
Complex Data Structures: Highly intricate, robust, and multifaceted structures.

Post-benchmarking, it's essential to store the results in a file for future integration into our git VCS. This will allow us to set up a workflow to consistently check for performance regression.
Suggested Development Workflow:

Simple Test Dojo Storage

Task: Begin with a basic test for Dojo storage.
Branch Name: 21-1-simple-test

Print Results

Task: Print benchmarking results to the console and store them in a file.
Branch Name: 21-2-print

Simple Benchmark

Task: Benchmark using simple data structures.
Branch Name: 21-3-simple-benchmark

Medium Benchmark

Task: Benchmark using medium complexity data structures.
Branch Name: 21-4-medium-benchmark

Complex Benchmark

Task: Benchmark using highly intricate data structures.
Branch Name: 21-5-complex-benchmark

Merged https://github.com/dojoengine/dojo/pull/1097


When Azure Data Lake Storage query acceleration can support Hong Kong?

The query acceleration feature is in public preview, and is available in the Canada Central and France Central regions.
When this feature can support Hong Kong?

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

ID: 62a6c1f4-9152-0f5a-b546-6ba9e1e2bf88
Version Independent ID: 282b084a-8184-29a0-799b-6f3a55dccdc5
Content: Filter data by using Azure Data Lake Storage query acceleration (preview)
Content Source: articles/storage/blobs/data-lake-storage-query-acceleration-how-to.md
Service: storage
Sub-service: data-lake-storage-gen2
GitHub Login: @normesta
Microsoft Alias: normesta

@zhangzexing789 Unfortunately, we don't have exact ETA. Regarding service general availability, I would suggest to keep an eye on Azure updates.
Azure updates provide information about important Azure product updates, roadmap, and announcements.

@zhangzexing789 Unfortunately, we don't have exact ETA. Regarding service general availability, I would suggest to keep an eye on Azure updates.
Azure updates provide information about important Azure product updates, roadmap, and announcements.

Thanks for your reply.


How to remove "Powered by Hugo and the Notepadium" footer credits?

Hugo Version:  v0.62.1-A1518704
Build Command: hugo
Hey how could I go about doing this? Love the theme, but I'm no web dev - I couldn't figure this one out. Thanks

You can overide footer:
In your site root, create an empty copyright.html at /layouts /partials/
.
└── layouts
    └── partials
        └── copyright.html

overide copyright.html
{{- $copyright := . -}}

{{- $copyright -}}

I appreciate the reply - However, I want to keep the copyright section and remove the "Powered by Hugo and the Notepadium" bit. (I use the copyright section for my email address).. Is this possible? Thanks mate

Try this:
copyright.html
{{- $copyright := . -}}

{{- $copyright -}}

<a<EMAIL_ADDRESS>to me


Use cache in travis

Codecov Report

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

@@           Coverage Diff           @@
##           master     #206   +/-   ##
=======================================
  Coverage   65.75%   65.75%
=======================================
  Files          30       30
  Lines        2669     2669
=======================================
  Hits         1755     1755
  Misses        732      732
  Partials      182      182

Continue to review full report at Codecov.

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


3338 make CVE modified url optional

Fixes Issue
Fix #3338
Description of Change
The goal of this PR is to make property cveUrlModified optional if cveUrlBase is changed so it is just a domain name change. Change has been performed in cli, ant & maven plugin. To prevent some duplication, a CveUrlParser interface has been created to have the same parsing logic for each tool.
Feel free to comment the change. :slightly_smiling_face:
Have test cases been added to cover the new functionality?
yes

Thanks for the PR! This has been an item on my list for a while.


⚠ Samsung has degraded performance

In 0a78961, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 1705 ms

Resolved: Samsung performance has improved in 34ad521.


Update the link

Fixes Issue #6216

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

@Yasir761 thank you for your contribution, but this is not how we run the project.
Please familiarise yourself with the Contributing Guide: https://github.com/EddieHubCommunity/LinkFree/blob/main/CONTRIBUTING.md
If you raise a Pull Request when an Issue has not been assigned to you, you run the risk of the work that you have done not being used.
As you can see from https://github.com/EddieHubCommunity/LinkFree/issues/6216 other people have asked to be assigned the Issue, so I will be closing this Pull Request.

@Yasir761 thank you for your contribution, but this is not how we run the project.
Please familiarise yourself with the Contributing Guide: https://github.com/EddieHubCommunity/LinkFree/blob/main/CONTRIBUTING.md
If you raise a Pull Request when an Issue has not been assigned to you, you run the risk of the work that you have done not being used.
As you can see from #6216 other people have asked to be assigned the Issue, so I will be closing this Pull Request.

My bad, sorry for all this.
Thank You


Update ANCM diagnostics doc for 3.0

React to/Add entries for

Changes in log strings https://github.com/aspnet/AspNetCore/pull/4515
Bitness mismatch event

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

ID: 4a2a7104-1d14-2e8a-0984-d92aa311c108
Version Independent ID: 5e3c0546-c579-afb9-5289-b14532c127eb
Content: Troubleshoot ASP.NET Core on Azure App Service and IIS
Content Source: aspnetcore/test/troubleshoot-azure-iis.md
Product: aspnet-core
Technology: aspnetcore-test
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@tdykstra Same ?: Are they going to take this? I was about to get to this one, too.

@shirhatti As we discussed earlier, I don't see how this topic can be maintained ... at least using the prior approach. It was created and maintained in a simpler age 👴 by reverse-engineering the error conditions to determine the error strings for a given condition.
The 2.2 updates that I made (https://github.com/aspnet/AspNetCore.Docs/pull/10319) don't match all of the original strings shown in diff on https://github.com/aspnet/AspNetCore/pull/4515, so it looks like there were intervening changes to the framework along the way. The history of  src/Servers/IIS/AspNetCoreModuleV2/CommonLib/resources.h doesn't indicate very many PRs, but the full history perhaps isn't shown (perhaps the repo moved?).
I wish all of these errors had been given stable framework error codes (looks like HRESULT is too general). That way, the strings could change and the topic wouldn't, and devs would just search the whole doc for a stable error code. I guess that there are other reasons why such a scheme wasn't instituted.
Anyway ... I'm not sure how to proceed here: There are too many error conditions and permutations of hosting to continue reverse engineering the outcomes. Since 2.2 strings in the doc don't match the diff, I'm scared to blindly find-'n-replace strings (by 'replace', I mean add 3.0 blocks or just update the 2.2 content).

@shirhatti I'm looking at this now. Any i-dears on this one?

I definitely don't want you to reverse engineer the failure conditions. I'd started writing a document that describes all failure conditions at https://github.com/aspnet/specs/blob/master/notes/ancm/startuperrors.md
If my doc is missing any failure scenarios, @ me. I'm on the hook to address that.
For scenarios where we've updated the error messages for grammar/spelling, I believe the EventIDs are still the same. Just spitballing here, but if we include the EventID in this document, folks should still be able to search in this document. Thoughts?

btw - ☝ that link 404s (but I only have public access, so that's prob a private repo).
Yeah, if EventID comes out in one of the locations (browser response in Dev env, Application Event Log, ANCM stdout log, or ANCM debug log). My impression was that they don't show up (but I certainly may have forgotten what shows up given the time that's passed). Output often includes HRESULT codes, which aren't specific enough to be keys for error conditions. At least they weren't in the old days. 👴
Even if EventID is there and will work as keys for the guidance (i.e., those 'things to check' lists that I put in for each error), how do we align the EventIDs with the conditions that cause them any easier than reverse-engineering the errors? That was the only reliable way to produce and maintain this doc in the old days.

@shirhatti Checking in on this one ... is the plan to take the new doc that you started writing and swap its text for most of the content in Common errors reference for Azure App Service and IIS with ASP.NET Core?
If so, I guess we'll keep the introduction but swap out everything else starting with the first error condition.
If that's the plan, do you want to paste your topic text in here for me to work it into a PR, or do you want to send the PR (i.e., take over this issue)?

Ping @shirhatti ... Checking in on this one ... should I leave it open. You were saying that you might have a total content replacement in the works. Is that right? The plan will be to keep the introduction here but swap everything else in the topic with your new bits. Is that correct? If so, should this remain on the November sprint, or should I move it back to December (or later)?

@Rick-Anderson ... There's no action here AFAIK. Whatever way it goes, I'm not going to have the time to do anything significant with this, so I'm removing my assignment. I'll leave it to you to assign or close.

@bradygaster  @shirhatti  if you can update https://github.com/aspnet/specs/blob/master/notes/ancm/startuperrors.md I'll get this documented.

@jkotalik @shirhatti  is there anything in https://github.com/aspnet/specs/blob/master/notes/ancm/startuperrors.md that should be migrated to this doc? If so, please reopen.


Manifest: Updated west.yml

Updated hal_telink

The following west manifest projects have been modified in this Pull Request:

Name
Old Revision
New Revision
Diff

hal_telink
https://github.com/telink-semi/hal_telink/commit/c01672a589740d85ff977c331e9f58659caccc80 (develop)
https://github.com/telink-semi/hal_telink/pull/60
telink-semi/hal_telink#60/files

Note: This message is automatically posted and updated by the Manifest GitHub Action.

In Zephyr heap is already working correct. stdlibc allocatots are not used.
You can check it using any project for example blinky and cpp.
Checker nas been already introduced in https://github.com/telink-semi/zephyr/commit/275b5e307824d857589f3d65fec8aac8731ce34c
So for now i'll check the sitiation with openthread mbedtls allocators in clean Zephyr.
If everything is fine we just need correctly setup Matter.
I described it in ticket.


Packed pilet has duplicated entries

Bug Report
For more information, see the CONTRIBUTING guide.
Prerequisites

[x] Can you reproduce the problem in a MWE
[x] Are you running the latest version?
[x] Did you perform a search in the issues?

Environment Details and Version

Windows 11 22H2
node 18.14.0
npm 9.5.0
piral-cli 1.0.1

Description
When I pack the pilet as tar file, die included files in /package/dist are there twice.
Steps to Reproduce
(See the MWE)

npm i
npm run build
pilet pack

Expected behavior
Every file from dist packed once.
Actual behavior
Every file from dist packed twice.
Possible Origin/Solution
Maybe a OS-dependent issue? Case-Sensitivity?

I think we already ruled out the case sensitivity on this one. I'll see when / under what circumstances this can be reproduced and what is the root cause.
I'll come back on this one.

Thanks for the repo - we could reproduce this. Fix is out in the preview (tag next on npm).

Thanks for the quick fix, works as expected!


Remove use of pkg_resources

https://importlib-resources.readthedocs.io/en/latest/migration.html#pkg-resources-resource-filename


[Question] Embedding An Instance of StateLossCallback In Application.VBE.MainWindow

Hello, this is just a general question.
I've been looking for a good way to natively handle (specifically) the closure/destruction of the VBA IDE main window.
I thought about embedding a reference to an instance of StateLossCallback into a CommandBarControl or ToolWindow and then adding that object to Application.VBE.CommandBars or Application.VBE.Windows.
This is more difficult to do than I expected; and I have not yet found a way to do it.
My question is, if I did somehow manage to do this, would StateLossCallback work as intended?
Many thanks for all your great work.

Hi @Finatra ,

closure/destruction of the VBA IDE main window

Closing the VBA window can be detected easily by using Win API calls - not sure about Mac though. However, if the window is actually destroyed as in DestroyWindow then that is a completely different thing as code debugging stops working entirely and trying to break into code in debug mode will cause a crash - in other words if the VBE window is ever destroyed then the application needs to be restarted anyway.
I am guessing you would rather "catch" the event of closing the VBE window.  In that case, yes, this will still work.
The StateLossCallback class has a major issue - it does not work if state is lost when code is already running e.g. Sub Test(): End: End Sub. Only works for state loss when code is not running e.g. Stop button.
My plan is to try to find a workaround in the next few weeks so that the class is reliable. There are other issues raised by other users, where this class causes the application to crash when the application is closed (it used to work fine).

Thanks for the reply!
I will keep looking for a good way to attach it to the VBE window.
Out of curiosity, I initially tried using WinAPI calls (by subclassing the VBE window) however it wasn't practical because it made interacting with the VBE unstable.
Every window message triggered a callback to my VBA code which slowed down the environment as it was constantly toggling the "[running]" state.
I could not find an external way to filter the window messages to reduce the number of callbacks.
I wanted to avoid the trivial solution of just periodically checking the window state.

Try this:
Option Explicit

Private myHook As Long

'https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-setwineventhook
Private Declare PtrSafe Function SetWinEventHook _
    Lib "user32.dll" (ByVal eventMin As Long _
                    , ByVal eventMax As Long _
                    , ByVal hmodWinEventProc As LongPtr _
                    , ByVal pfnWinEventProc As LongPtr _
                    , ByVal idProcess As Long _
                    , ByVal idThread As Long _
                    , ByVal dwFlags As Long) As Long
Private Declare PtrSafe Function UnhookWinEvent Lib "user32.dll" (ByVal hWinEventHook As Long)
Private Declare PtrSafe Function GetCurrentThreadId Lib "kernel32" () As Long
Private Declare PtrSafe Function GetCurrentProcessId Lib "kernel32" () As Long

Public Sub HookWinEvent()
    'https://learn.microsoft.com/en-us/windows/win32/winauto/event-constants
    Const EVENT_SYSTEM_FOREGROUND As Long = &H3
    Const WINEVENT_OUTOFCONTEXT As Long = 0
    #If Win64 Then
        Const NULL_PTR As LongLong = 0^
    #Else
        Const NULL_PTR As Long = 0&
    #End If
    '
    If myHook <> 0 Then UnhookWinEvent myHook
    myHook = SetWinEventHook(EVENT_SYSTEM_FOREGROUND _
                           , EVENT_SYSTEM_FOREGROUND _
                           , NULL_PTR _
                           , AddressOf WinEventProc _
                           , GetCurrentProcessId() _
                           , GetCurrentThreadId() _
                           , WINEVENT_OUTOFCONTEXT)
End Sub

Public Sub UnhookWEvent()
    If myHook <> 0 Then UnhookWinEvent myHook
    myHook = 0
End Sub

'https://learn.microsoft.com/en-us/windows/win32/api/winuser/nc-winuser-wineventproc
Public Sub WinEventProc(ByVal hWinEventHook As LongPtr _
                      , ByVal wEvent As Long _
                      , ByVal hWnd As LongPtr _
                      , ByVal idObject As Long _
                      , ByVal idChild As Long _
                      , ByVal idEventThread As Long _
                      , ByVal dwmsEventTime As Long)
    Debug.Print "A window was opened/closed"
    If hWnd = Application.VBE.MainWindow.hWnd Then
        Debug.Print "VBE was opened/closed"
    End If
End Sub

Anyway, there are a few issues with the above:

it seems to ignore the process and thread id and basically inform on all desktop windows
the callback is still called even after calling UnhookWinEvent myHook - maybe you can figure this one out
if state is lost then myHook will lose its value. Maybe use LibExcelBookItems to quickly store and retrieve. E.g. BookItem(ThisWorkbook, "myHook") = CStr(dword) to save and ```Debug.Print CLng(BookItem(ThisWorkbook, "myHook")) to retrieve.
You probably want to quickly exit the callback to avoid crashes so use an async call. E.g. the Terminate event of a class that you instantiate in the scope of the callback

Thanks! I'll give it a try!

Hi @Finatra
Did you have any success with the SetWinEventHook code? I was just thinking that I might use it to capture when the application is closing which should help with preventing some of the crashes.

Still looking into it.
I did fix the Unhook though:
The UnhookWinEvent() declaration was missing a return type. (gave it As Boolean)
I changed the hWinEventHook parameter of the WinEventProc() from LongPtr to Long.
Option Explicit

Private myHook As Long

'https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-setwineventhook
Private Declare PtrSafe Function SetWinEventHook _
    Lib "user32.dll" (ByVal eventMin As Long _
                    , ByVal eventMax As Long _
                    , ByVal hmodWinEventProc As LongPtr _
                    , ByVal pfnWinEventProc As LongPtr _
                    , ByVal idProcess As Long _
                    , ByVal idThread As Long _
                    , ByVal dwFlags As Long) As Long
Private Declare PtrSafe Function UnhookWinEvent Lib "user32.dll" (ByVal hWinEventHook As Long) As Boolean
Private Declare PtrSafe Function GetCurrentThreadId Lib "kernel32" () As Long
Private Declare PtrSafe Function GetCurrentProcessId Lib "kernel32" () As Long

Public Sub HookWinEvent()
    'https://learn.microsoft.com/en-us/windows/win32/winauto/event-constants
    Const EVENT_SYSTEM_FOREGROUND As Long = &H3
    Const WINEVENT_OUTOFCONTEXT As Long = 0
    #If Win64 Then
        Const NULL_PTR As LongLong = 0^
    #Else
        Const NULL_PTR As Long = 0&
    #End If
    '
    If myHook <> 0 Then UnhookWinEvent myHook
    myHook = SetWinEventHook(EVENT_SYSTEM_FOREGROUND _
                           , EVENT_SYSTEM_FOREGROUND _
                           , NULL_PTR _
                           , AddressOf WinEventProc _
                           , GetCurrentProcessId() _
                           , GetCurrentThreadId() _
                           , WINEVENT_OUTOFCONTEXT)
    Debug.Print "SetWinEventHook/myHook: " & myHook
End Sub

Public Sub UnhookWEvent()
    If myHook <> 0 Then Debug.Print "UnhookWinEvent: " & UnhookWinEvent(myHook)
    myHook = 0
End Sub

'https://learn.microsoft.com/en-us/windows/win32/api/winuser/nc-winuser-wineventproc
Public Sub WinEventProc(ByVal hWinEventHook As Long _
                      , ByVal wEvent As Long _
                      , ByVal hWnd As LongPtr _
                      , ByVal idObject As Long _
                      , ByVal idChild As Long _
                      , ByVal idEventThread As Long _
                      , ByVal dwmsEventTime As Long)
    Debug.Print "hWinEventHook: " & hWinEventHook
    Debug.Print "       myHook: " & myHook

    If hWinEventHook <> 0 Then
        If hWinEventHook <> myHook Then myHook = hWinEventHook
    End If

    'Debug.Print "A window was opened/closed"
    If hWnd = Application.VBE.MainWindow.hWnd Then
        'Debug.Print "VBE was opened/closed"
    End If
End Sub

Still experimenting.
Will update soon.

Ok, after some tinkering I figured out that the hook isn't called for ALL desktop windows.
It's only called for Application.VBE.MainWindow.
Only one window can be the FOREGROUND window at a time.
So, focusing back and forth between VBE and any other window will trigger the CallBack each time.
Focusing between two non-VBE windows does not trigger the CallBack.
I don't think EVENT_SYSTEM_FOREGROUND is the right event for detecting closure.
I also tried EVENT_OBJECT_CLOAKED and EVENT_OBJECT_HIDE; neither of which were better.
Regarding Unhooking:
The CallBack passes the hook's handle, so if the hook triggers after myHook has lost its state you can safely unhook using the hWinEventHook argument that was passed by the CallBack.
 Attempting to Unhook..."
        If UnhookWinEvent(hWinEventHook) Then
            Debug.Print "UnhookWinEvent(hWinEventHook:=" & hWinEventHook & ")=True 'Unhook Successful"
        Else
            Debug.Print "UnhookWinEvent(hWinEventHook:=" & hWinEventHook & ")=False 'Unhook Failed"
            Debug.Print "Attempting to Unhook via myHook..."
            If UnhookWinEvent(myHook) Then
                Debug.Print "UnhookWinEvent(myHook:=" & myHook & ")=True 'Unhook Successful"
            Else
                Debug.Print "UnhookWinEvent(myHook:=" & myHook & ")=False 'Unhook Failed"
            End If
        End If
        myHook = 0
        Exit Sub
    End If

    'Output
    If hWnd = Application.VBE.MainWindow.hWnd Then
        Debug.Print "The VBE window was opened/closed"
    Else
        Debug.Print "Another window was opened/closed"
    End If

End Sub

Hi @Finatra ,

The UnhookWinEvent() declaration was missing a return type. (gave it As Boolean)

😄 Yeah, sometimes my attention to detail goes down the drain. Thanks for finding that.

The CallBack passes the hook's handle, so if the hook triggers after myHook has lost its state you can safely unhook using the hWinEventHook argument that was passed by the CallBack.

Cool. I tried it and it works.
So what does this mean for you? Is this API code solving your problem, meaning you have no need for StateLossCallback anymore? Or, you don't like this approach and maybe you need something that works on Mac as well?
Best,
Cristian

It turns out that VBE.MainWindow never truly "closes" while its Host Application is running.
Closing the window just hides the window.
That being the case, it seems that even if I managed to embed a StateLossCallback object somewhere in the window, the callback would never trigger since hiding the window does not cause state loss.
I was able to monitor the events triggered by closing the VBE window using accevent.exe.
The event I want to hook is UIA_Window_WindowClosedEventId:
Public Const UIA_Window_WindowClosedEventId As Long = 20017

Although, it seems to be a "WinEvent" like EVENT_SYSTEM_FOREGROUND and belongs to one of the allocations listed here:
https://learn.microsoft.com/en-us/windows/win32/winauto/allocation-of-winevent-ids
It doesn't seem to work with SetWinEventHook.
Anyway, you're welcome to close this issue since this is not directly related to StateLossCallback and is mostly just for my own curiosity.
Thank you for your suggestions and your time!
-Ben

It turns out that VBE.MainWindow never truly "closes" while its Host Application is running.

Sorry I did not mention that sooner - I knew but I assumed you also knew. I did some tests a few years ago and found out that if you manually kill the VBE window (I mentioned this in my first comment above) then if the code stops on a breakpoint or on a Stop statement or on an unhandled error then the app will crash.
Thanks for giving me feedback on my suggestion. Will let you know when I get to improve this repo in a few weeks time.
Cheers


Provide a mac build please

Brief description
Jeez barry why.....
Extended description and links to related things
This space left intentionally blank
Additional context or questions
Like why?

Added a mac build.
Need to finailize the work flow for it though, there is some cert juggiling involved.

Also submitted a built to the Mac App Store. We'll see how that goes.
Need to tidy up the work flow, but otherwise should be able to do mac builds with new releases as well.
Mac Builds need to only use the mac certs, and windows builds need the special code signing cert, which makes it intereresting....

mac app store version in the queue


How to refresh slider?

Hello,
First of all thank you for your script.
I'm using it on a responsive design,  it happens that when i adjust browser window size, photo containers sizes don't adjust automatically. Is there a solution for this? How can i "re-initialize" lbSlider?Thanks.

Right now slider is not responsive. Last commit was more than a year ago... So I am thinking about completely rewrite it. If I do this I think responsiveness and some additional methods like "destroy" and "update" will be implemented.

So... no workaround until you rewrite it? There must be a way of
re-initialize it... :)
On Wed, Mar 11, 2015 at 5:13 PM, Andrew<EMAIL_ADDRESS>wrote:

Right now slider is not responsive. Last commit was more than a year
ago... So I am thinking about completely rewrite it. If I do this I think
responsiveness and some additional methods like "destroy" and "update" will
be implemented.
—
Reply to this email directly or view it on GitHub
https://github.com/equinox7/lbSlider/issues/3#issuecomment-78309225.

I can not advise you a good solution at the moment.


Add status checks to repository

In order to understand PRs better please add status checks to this repository including the following:

[ ] Codecov
[ ] Codacy
[ ] Code Style / isort (pull_request)
[ ] Tests / Tests (postgres)
[ ] Docker PR Build / Build Docker image
[ ] Code Style / flake8 (pull_request)

duplicate


Fixed the "==" constraint to a.i == b.i in PrepareSpec."with outer join"

Problem
Test case PrepareSpec."with outer join" was creating a meaningless join (a, b) <- qr1 join qr2 on ((a, b) => a.i == a.i)
Solution
Fixed the "==" constraint to a.i == b.i
Checklist

[x] Unit test all changes
[x] Update README.md if applicable
[ ] Add [WIP] to the pull request title if it's work in progress
[ ] Squash commits that aren't meaningful changes
[x] Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: juliano:x: b-gyulaYou have signed the CLA already but the status is still pending? Let us recheck it.