function declaration error in truffle/lib/contracts.js

Hello, the execution of fruffle 1.0.1 fails due to  a syntax error in the declaration of update_sources function (truffle/lib/contracts.js:41)
update_sources(config, callback) {
I solved the issue changing it in:
update_sources: function(config, callback) {
Best Regards
Antonio Piccolo

Same issue.
Looks like the rest of the file was recently changed from the first format to the second, but update_sources was left out.

Whoops, fixed. Give it another shot - should be updated now to 1.0.2.
If this still doesn't work, I'd love to know the error, and feel free to reopen this ticket. That said, upgrading to node 5.0 should solve your issues as well. Cheers!


Pomodoro Support

I've been using this integration a lot. I haven't figured out how to do pomodoro timers though. I looked through the API and there doesn't appear to be a flag or attribute to differentiate the timer type. Do you know if the API supports pomodoro and whether we could extend the integration to support this?

I think Pomodoro support would need to be implemented in the plugin itself. It seems like a feature exclusive to the Desktop client, so it's probably not available for API users. I'll look into adding this with the Rewrite, although it's not a priority for me right now.


GPU not allocated after k3ai apply nvidia-gpu

Hi! I would like to make use of my machines GPU (single RTX A6000) on Kubeflow pipelines.
Currently, CPU-only works fine but I need to use GPU resources for training.
After executing
k3ai apply nvidia-gpu
and verifying that
kubectl get pods -A gives
NAMESPACE            NAME                                                  READY   STATUS             RESTARTS   AGE
default              gpu-operator-test                                     0/1     Pending            0          15h
jupyter              jupyter-minimal-6565df8f74-n2hww                      1/1     Running            1          15h
kube-system          coredns-f9fd979d6-dg9m9                               1/1     Running            1          15h
kube-system          coredns-f9fd979d6-ml5zp                               1/1     Running            1          15h
kube-system          etcd-demo-win-kind-control-plane                      1/1     Running            0          46m
kube-system          kindnet-s252v                                         1/1     Running            2          15h
kube-system          kube-apiserver-demo-win-kind-control-plane            1/1     Running            0          46m
kube-system          kube-controller-manager-demo-win-kind-control-plane   1/1     Running            1          15h
kube-system          kube-proxy-j5mns                                      1/1     Running            1          15h
kube-system          kube-scheduler-demo-win-kind-control-plane            1/1     Running            1          15h
kube-system          nvidia-device-plugin-daemonset-qpdwb                  1/1     Running            1          15h
kubeflow             cache-deployer-deployment-84866455bb-462nf            1/1     Running            1          15h
kubeflow             cache-server-5c98c678f8-m5dqs                         1/1     Running            4          15h
kubeflow             first-pipeline-5fxxc-1217708725                       0/2     Completed          0          15h
kubeflow             first-pipeline-5fxxc-1430651520                       0/2     Completed          0          15h
kubeflow             first-pipeline-5fxxc-201314523                        0/2     Pending            0          15h
kubeflow             first-pipeline-5fxxc-3777309308                       0/2     Completed          0          15h
kubeflow             first-pipeline-5fxxc-731956426                        0/2     Completed          0          15h
kubeflow             metadata-envoy-deployment-6756c995c9-xwg8j            1/1     Running            1          15h
kubeflow             metadata-grpc-deployment-7cb87744c7-gsghl             0/1     CrashLoopBackOff   18         15h
kubeflow             metadata-writer-574df45956-54cb2                      0/1     CrashLoopBackOff   10         15h
kubeflow             minio-5b65df66c9-dthpd                                1/1     Running            1          15h
kubeflow             ml-pipeline-68644d4ddc-kqbfx                          0/1     CrashLoopBackOff   18         15h
kubeflow             ml-pipeline-persistenceagent-ffc9cfb96-2p4n9          1/1     Running            1          15h
kubeflow             ml-pipeline-scheduledworkflow-6d669f9bd7-p5hsp        1/1     Running            1          15h
kubeflow             ml-pipeline-ui-86bf65ccf7-44bxj                       1/1     Running            1          15h
kubeflow             ml-pipeline-viewer-crd-64dbbc8cc5-6xqjr               1/1     Running            2          15h
kubeflow             ml-pipeline-visualizationserver-78bcc958cd-l6pp6      1/1     Running            1          15h
kubeflow             mysql-f7b9b7dd4-hfxlp                                 1/1     Running            1          15h
kubeflow             workflow-controller-557d46b4bd-2zxc8                  1/1     Running            1          15h
local-path-storage   local-path-provisioner-78776bfc44-58hjt               1/1     Running            2          15h

I thought GPU resources are now available to my cluster. But upon checking
user@user-desktop:~$ kubectl describe nodes
Name:               demo-win-kind-control-plane
Roles:              master
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=demo-win-kind-control-plane
                    kubernetes.io/os=linux
                    node-role.kubernetes.io/master=
Annotations:        kubeadm.alpha.kubernetes.io/cri-socket: unix:///run/containerd/containerd.sock
                    node.alpha.kubernetes.io/ttl: 0
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Wed, 07 Jul 2021 18:23:33 +0900
Taints:             <none>
Unschedulable:      false
Lease:
  HolderIdentity:  demo-win-kind-control-plane
  AcquireTime:     <unset>
  RenewTime:       Thu, 08 Jul 2021 10:05:49 +0900
Conditions:
  Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----             ------  -----------------                 ------------------                ------                       -------
  MemoryPressure   False   Thu, 08 Jul 2021 10:05:28 +0900   Wed, 07 Jul 2021 18:23:31 +0900   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure     False   Thu, 08 Jul 2021 10:05:28 +0900   Wed, 07 Jul 2021 18:23:31 +0900   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure      False   Thu, 08 Jul 2021 10:05:28 +0900   Wed, 07 Jul 2021 18:23:31 +0900   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready            True    Thu, 08 Jul 2021 10:05:28 +0900   Wed, 07 Jul 2021 18:23:57 +0900   KubeletReady                 kubelet is posting ready status
Addresses:
  InternalIP:  <IP_ADDRESS>
  Hostname:    demo-win-kind-control-plane
Capacity:
  cpu:                12
  ephemeral-storage:  959863856Ki
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             32539168Ki
  pods:               110
Allocatable:
  cpu:                12
  ephemeral-storage:  959863856Ki
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             32539168Ki
  pods:               110
System Info:
  Machine ID:                 94303fcf2f8d4ace8673d518890fb123
  System UUID:                b9b678e1-971c-41f1-a57c-be56e6fc028b
  Boot ID:                    8960095b-c1f1-4a43-83d6-621cc29dad3b
  Kernel Version:             5.4.0-77-generic
  OS Image:                   Ubuntu Groovy Gorilla (development branch)
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  containerd://1.4.0
  Kubelet Version:            v1.19.1
  Kube-Proxy Version:         v1.19.1
PodCIDR:                      <IP_ADDRESS>/24
PodCIDRs:                     <IP_ADDRESS>/24
ProviderID:                   kind://docker/demo-win-kind/demo-win-kind-control-plane
Non-terminated Pods:          (25 in total)
  Namespace                   Name                                                   CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age
  ---------                   ----                                                   ------------  ----------  ---------------  -------------  ---
  jupyter                     jupyter-minimal-6565df8f74-n2hww                       0 (0%)        0 (0%)      0 (0%)           0 (0%)         15h
  kube-system                 coredns-f9fd979d6-dg9m9                                100m (0%)     0 (0%)      70Mi (0%)        170Mi (0%)     15h
  kube-system                 coredns-f9fd979d6-ml5zp                                100m (0%)     0 (0%)      70Mi (0%)        170Mi (0%)     15h
  kube-system                 etcd-demo-win-kind-control-plane                       0 (0%)        0 (0%)      0 (0%)           0 (0%)         55m
  kube-system                 kindnet-s252v                                          100m (0%)     100m (0%)   50Mi (0%)        50Mi (0%)      15h
  kube-system                 kube-apiserver-demo-win-kind-control-plane             250m (2%)     0 (0%)      0 (0%)           0 (0%)         55m
  kube-system                 kube-controller-manager-demo-win-kind-control-plane    200m (1%)     0 (0%)      0 (0%)           0 (0%)         15h
  kube-system                 kube-proxy-j5mns                                       0 (0%)        0 (0%)      0 (0%)           0 (0%)         15h
  kube-system                 kube-scheduler-demo-win-kind-control-plane             100m (0%)     0 (0%)      0 (0%)           0 (0%)         15h
  kube-system                 nvidia-device-plugin-daemonset-qpdwb                   0 (0%)        0 (0%)      0 (0%)           0 (0%)         15h
  kubeflow                    cache-deployer-deployment-84866455bb-462nf             0 (0%)        0 (0%)      0 (0%)           0 (0%)         15h
  kubeflow                    cache-server-5c98c678f8-m5dqs                          0 (0%)        0 (0%)      0 (0%)           0 (0%)         15h
  kubeflow                    metadata-envoy-deployment-6756c995c9-xwg8j             0 (0%)        0 (0%)      0 (0%)           0 (0%)         15h
  kubeflow                    metadata-grpc-deployment-7cb87744c7-gsghl              0 (0%)        0 (0%)      0 (0%)           0 (0%)         15h
  kubeflow                    metadata-writer-574df45956-54cb2                       0 (0%)        0 (0%)      0 (0%)           0 (0%)         15h
  kubeflow                    minio-5b65df66c9-dthpd                                 20m (0%)      0 (0%)      100Mi (0%)       0 (0%)         15h
  kubeflow                    ml-pipeline-68644d4ddc-kqbfx                           250m (2%)     0 (0%)      500Mi (1%)       0 (0%)         15h
  kubeflow                    ml-pipeline-persistenceagent-ffc9cfb96-2p4n9           120m (1%)     0 (0%)      500Mi (1%)       0 (0%)         15h
  kubeflow                    ml-pipeline-scheduledworkflow-6d669f9bd7-p5hsp         0 (0%)        0 (0%)      0 (0%)           0 (0%)         15h
  kubeflow                    ml-pipeline-ui-86bf65ccf7-44bxj                        10m (0%)      0 (0%)      70Mi (0%)        0 (0%)         15h
  kubeflow                    ml-pipeline-viewer-crd-64dbbc8cc5-6xqjr                0 (0%)        0 (0%)      0 (0%)           0 (0%)         15h
  kubeflow                    ml-pipeline-visualizationserver-78bcc958cd-l6pp6       30m (0%)      0 (0%)      500Mi (1%)       0 (0%)         15h
  kubeflow                    mysql-f7b9b7dd4-hfxlp                                  100m (0%)     0 (0%)      800Mi (2%)       0 (0%)         15h
  kubeflow                    workflow-controller-557d46b4bd-2zxc8                   100m (0%)     0 (0%)      500Mi (1%)       0 (0%)         15h
  local-path-storage          local-path-provisioner-78776bfc44-58hjt                0 (0%)        0 (0%)      0 (0%)           0 (0%)         15h
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests     Limits
  --------           --------     ------
  cpu                1480m (12%)  100m (0%)
  memory             3160Mi (9%)  390Mi (1%)
  ephemeral-storage  0 (0%)       0 (0%)
  hugepages-1Gi      0 (0%)       0 (0%)
  hugepages-2Mi      0 (0%)       0 (0%)
Events:
  Type     Reason                   Age                From        Message
  ----     ------                   ----               ----        -------
  Normal   NodeHasSufficientMemory  15h (x5 over 15h)  kubelet     Node demo-win-kind-control-plane status is now: NodeHasSufficientMemory
  Normal   NodeHasNoDiskPressure    15h (x4 over 15h)  kubelet     Node demo-win-kind-control-plane status is now: NodeHasNoDiskPressure
  Normal   NodeHasSufficientPID     15h (x4 over 15h)  kubelet     Node demo-win-kind-control-plane status is now: NodeHasSufficientPID
  Normal   Starting                 15h                kubelet     Starting kubelet.

  Normal   NodeReady                15h                kubelet     Node demo-win-kind-control-plane status is now: NodeReady
  Normal   Starting                 55m                kubelet     Starting kubelet.
  Normal   NodeHasSufficientMemory  55m (x8 over 55m)  kubelet     Node demo-win-kind-control-plane status is now: NodeHasSufficientMemory
  Normal   NodeHasNoDiskPressure    55m (x8 over 55m)  kubelet     Node demo-win-kind-control-plane status is now: NodeHasNoDiskPressure
  Normal   NodeHasSufficientPID     55m (x7 over 55m)  kubelet     Node demo-win-kind-control-plane status is now: NodeHasSufficientPID
  Normal   NodeAllocatableEnforced  55m                kubelet     Updated Node Allocatable limit across pods
  Warning  readOnlySysFS            55m                kube-proxy  CRI error: /sys is read-only: cannot modify conntrack limits, problems may arise later (If running Docker, see docker issue #24000)
  Normal   Starting                 55m                kube-proxy  Starting kube-proxy.

GPU has not been allocated even though nvidia-device-plugin-daemonset-qpdwb  is running properly.
Thanks in advance for your help!

Hi, @j-cunanan, first of all, thanks for opening the issue, and really appreciated that you are using K3ai, I'm reviewing this right now, a couple of things:

I've updated the plugin to the latest version, could you give it try and see if anything changes?
What we do with the plugin is basically just pass the NVIDIA K8s YAML file so we assume the pre-requisites are satisfied.. if point 1 does not work could you try to follow their official documentation here? If it works I'll change the plugin to make use of the new GPU Operator

Thanks again for opening the issue!

Thank you for your quick resonse @alefesta !
1 did not work because I think I have'nt successfully done 2.
Doing the guide here: https://docs.nvidia.com/datacenter/cloud-native/kubernetes/install-k8s.html#option-2-installing-kubernetes-using-kubeadm
I successfully added my GPU without using the GPU operator but rather the multi-step method in the guide.
But when trying to add a GPU to a cluster made by kind or k3ai I couldn't make my GPU to work.
I'll probably take more time debugging this.
Thanks again!

Humm...
So for kind the problem is that is a DnD (Docker in Docker) see the long thread here they are still working on support GPU's. :(
For k3ai humm did you try to install k3s as a cluster (that is not a DnD) and then pass the GPU plugin? i.e.: k3ai init --local k3s && k3ai apply nvidia-gpu
I would say that the easiest path is to move the plugin to use the GPU operator directly.. it shouldn't be too much of a problem since we were already targeting the support for helm and shell/PowerShell scripts as part of a plugin.
Let me work on this should be ready in a couple of weeks :)

ah i see. So after k3ai init
I modified the .k3ai/config.yaml  set enable: true on the localKind cluster instance.
Based from above, k3ai apply nvidia-gpu is expected to not work, right?
So now, enabled the localK3s and ran k3ai init
but got
chmod: cannot access './home/user/k3s': No such file or directory
mv: cannot stat './home/user/k3s': No such file or directory

even though the file is there.

Ahhhhhhhhhhhhhhhhh "+data.Spec.Linux+"; chmod +x .$HOME/k3s; sudo mv .$HOME/k3s /usr/local/bin; my fault :) !!! Sorry about that.. in case if you look closely at the line above you'll notice a . in front of the $HOME ... that's why it cannot work. I'll fix that and I think is time to make a fix release of k3ai. Sorry about that really.

Ok I've fixed this will be in the next release of k3ai. Going to close this, thanks again for the issue @j-cunanan


SQL DB - Add support for geo-replication

Received customer request for SQL DB geo-replication. Do we have a plan to support this?
I think it is hard to design the behaviors to fit it into current OSB API Spec.
First of all, it should be another db-only service in OSBA and it is one service instance to manage two (or more) DBs on Azure.
The problem is that, we shouldn't provide only geo-replication DB creation. Failover also needs to be supported (or users need to do out-of-band operations just like what we discussed in #124). It seems that the only choice to support that for now is Update API. But it doesn't totally make sense. A better choice is the in-review new item in OSB API Spec, broker extensions: https://github.com/openservicebrokerapi/servicebroker/pull/431. It takes time to check in. Overall, it is still doable via Update API.
The whole failover process should be unbind->failover->bind->restage the app. So another problem is that, when the primary DB is down, unbinding could fail as the broker tries to delete the user. The failure is expected in such a situation. But, how does unbinding determine whether the failure is expected or not? Per OSB API Spec, there is no additional parameters for unbinding but service_id and plan_id: https://github.com/openservicebrokerapi/servicebroker/blob/v2.13/spec.md#unbinding.
Any thoughts?

Close via https://gist.github.com/arschles/54d6d33a43fb67412da6f0694e24826e


Inconsistent number of TCR21 token holders

Describe the bug
The number of TRC21 token holders is inconsistent in TomoIssuer.
To Reproduce
Steps to reproduce the behavior:

Open ToomoWallet and select TomoIssuer
The next page shows the TRC21 token (POMO) which I issued
The number of Holders is shown as 48.
I select the token name "Pomodoro (POMO)" to view token details
The next screen states the number of Holder (should be 'Holders') as only 40 the same as in TomoScan.

Expected behavior
I would expect the number of holders within the TomoIssuer token list to reflect that in TomoScan.
Device specification (please complete the following information):
Device: MOTO G6+
OS: Android Pie (v9)
TomoWallet version: V0.10

Hi, since the mobile app only render the web version of Tomoissuer, then this is Tomoissuer's problem. So please transfer your issue into this repo


Compile warnings 2

o Defines new types for usec_t and msec_t
o comment out unused functions
o type conversion errors

I messed up the commits here.


[th/version-via-ssh] ipu: also check BMC "FirmwareVersion" via SSH

Redfish might not be running, so we need the fallback check for the version via SSH.
https://github.com/bn222/cluster-deployment-automation/commit/c80a04e0a839fa52fd664a9062dc41f14a53a282#r148561539
Fixes: c80a04e0a839 ('ipu: fetch BMC "FirmwareVersion" via redfish HTTP API')

nice ty


Sharing PDF on IOS fails - file received but doesnot exists

See more info in https://stackoverflow.com/questions/66256974/receive-share-file-intents-with-flutter-with-ios
When sharing a PDF file,
I was able to receive the file intent in the App but couldn't open the file:
print("$path, exist ${await io.File(path).exists()}");
I was able to print the path but the exists method return false
NOTE:

works with no issues in android
works with no issues in IOS when sharing an image
only fails with files (PDF)

also seeing this fail with csv.

Hi, did you find a solution?

i've fired in a PR to try and fix this issue (#137)
try adding this to your pubspec.yaml file...
receive_sharing_intent:
    git:
      url: https://github.com/LazyDave76/receive_sharing_intent.git

Does it fix PDF opening on iOS?

@petodavid Yes, that pull request fixes the PDF opening issue on iOS. If you see the changes, @LazyDave76 did a brilliant hack on removing the "file://" prefix on the file path.

Thank you @LazyDave76 for your fix. It works for me to open xml files. Is there any chance to see that fix in the next release on pub.dev?

@KasemJaffer needs to merge this PR or copy my change into master before it will be released.  Have asked for it to be merged again.

Thank you @LazyDave76 for your fix. It works for me to open xml files. Is there any chance to see that fix in the next release on pub.dev?

@KasemJaffer needs to merge this PR or copy my change into master before it will be released.  Have asked for it to be merged again.

I'm running into this now.
I have modified the SharedMediaFile path entry to remove the leading "file://", but it still can't open the PDF file.
Images etc work fine. I am sharing from the Files app on iOS.
flutter: FileSystemException: Cannot retrieve length of file, path = '/private/var/mobile/Containers/Shared/AppGroup/25C349AB-60EA-43FB-8C2E-F9B79F16530A/Screenshot%202021-03-22%20at%2014.13.28.pdf' (OS Error: No such file or directory, errno = 2)
Did you solve it in the end?

No I didn't

Ok fixed it - it's because flutter doesn't like the path to be URL encoded, but iOS typically does (or this package does convert), so my workaround was to decode the URL encoding manually before trying to open the file, that works.
(Also remove the leading "file://" as mentioned above). Hope this helps somebody.

@mobikats
Wow, this is amazingly ugly. Does this mean, I have to make two hard coded changes to the URL and also wrap this logic into a block that is only executed if the platform is iOS? And all this only for PDF files?
Damn, why is this plugin not maintained anymore? This sucks!
Have you also tried #37? Does it work? Or is it even worth changing to the share_handler package?


Provide a test on the description page

Hi, thanks for integrating Bootstrap 4 with emails.
Can you put in the description of the program a test:
https://litmus.com/
Thank you

The screenshots on the homepage of https://bootstrapemail.com are actual test, you can click the different email clients to see the results of the different tests, they were taken in Litmus. I can't afford to pay for Litmus indefinitely so I only used it for a short time.


Exclude cells by default

Hi,
Great tool! Would it be possible to have an option to exclude all cells by default and only include cells that I tag with a particular tag? Because in my use case, I don't want to include most of the details and export a simplified and clean report.
Let me know what you think.
Thanks!

I had a similar idea: for any cell that's denoted as "code" I'd like the default to be output only.  Basically, I want any option that by default hides all code but displays the rest.


Created fizzbuzz in  python

Thank you for your PR!
Unfortunately a solution similar to yours has already been submitted :/
The goal is to find creative/abstract new solutions to FizzBuzz.
See The top 5 samples here.
Thanks anyway! :)


Migrate samples for EventHubs and ExtendedLocations

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Remove static flag for Query Rule

In #6 I erroneously set the static flag on the Query rule. This rule should not be static.
In #7 I changed the test_user method of the Query rule to accept an optional user parameter. This is the expected behaviour for static rules.
This PR reverts those changes.

@alexmuller essentially, static rules are unlikely to change frequently, they can be queried at any time and have a meaningful value. eg Has a user responded to a specific survey, have they commented more than once. Non-static rules are much more changeable and should be checked on every page load. eg is it a Monday, are they coming from Facebook


FIDO Alliance and Microsoft certification

Hi,
I would like to see the Nitrokey3 (and other Fido keys by Nitrokey) certified at the FIDO Alliance (https://fidoalliance.org/certification/) and Microsoft (https://learn.microsoft.com/en-us/azure/active-directory/authentication/concept-fido2-hardware-vendor).
Best regards
Sebastian

Why it'd be useful for me personally: in Czech Republic it is possible to access government services online using certified FIDO keys as described here: Security keys, settings and level of assurance.

Previous query on this matter: https://support.nitrokey.com/t/fido-authenticator-certification-level-1-l1/4079

This is a similar post: https://support.nitrokey.com/t/nitrokey-fido2-azure-ad/2078


[Feature Request] Remove href hyperlink auditing/ping?

From this post (see update at the bottom, with this chromium commit) i've discovered that sooner or later (the next stable switch?) chromium will remove the flag to disable the feature "hyperlink auditing" that will remain permanently enabled.
~I have to admit that it's the first time that i hear about it~(i already had it disabled), but it's something that should be removed in my opinion.
I've searched through the patches and i couldn't find any reference to "hyperlink auditing" or "ping" (this seems unrelated).
I we haven't removed the relevant code we should (in extra/?).
Edit: Or we could just enable back the option since for now the code checking for its value is still there (not future-proof?)?

Extensions like uBlock Origin can still block pings by the chrome.privacy or chrome.webRequest API. Of course, it would be better to not require extensions.

I'm failing to understand the value of a patch here. Is there any chance for hyperlink auditing pings to occur if they're disabled via chrome.privacy or chrome.webRequest? I'm also not convinced that the maintenance overhead of a patch is worth it over an extension that disabled hyperlink auditing. (However, if the APIs are to be removed eventually, then it would be a completely different story.)

I agree, this has to be carefully considered because the maintenance cost of this could become  substantial.
Right now this can still be controlled with chrome.privacy.websites.hyperlinkAuditingEnabled and that's what uBlock is depending on, but they could completely remove it sooner or later.
Will keep an eye on this and report back is something changes/needs to be addressed here.

I run ublock origin and hyperlink auditing was enabled in chrome:// flags. I had to go in and disable it separately. Maybe it was blocked anyway or maybe not. Either way its going away in the next chromium release. This shipped disabled in firefox by default, I don't understand why we can't have the same.

@forkoz Two main reasons:

A patch isn't worth it if an extension can disable this feature (as discussed above)
I don't like disabling features (though in this particular case, it's arguable whether this feature is needed at all).

I do get #2 but I thought the main use of ungoogled chromium was to have privacy enhancement. It seems  akin to leaving search autocomplete "off" by default. I did not mean purge pings completely from the code.

This is extraordinary, surely Ungoogled chrome is all about stopping Google from tracking you. The Hyperlink Auditing (URL Ping) option is there precisely to enable Google (and others) to track you. I was surprised to discover that the option is not even disabled in the current release of Ungoogled Chrome - why is that?
Is it the case that the option to disable is being removed from Chromium itself or just Google's chrome? Or am I being naive thinking there is a difference?
If from Chromium itself then, unfortunately the maintenance hit has to taken if Ungoogled Chrome is to continue to be relevant.

@chebourne As I have already discussed above, you can still disable hyperlink auditing via an extension. Therefore, we don't need to change any more code at this time. The lower the impact our code changes make, the faster we can keep up with newer versions of Chromium.


worktop/storage

Or worktop/kvs or worktop/database
Depends if/how Durable Objects get worked in or if they should be their own separate module.

NOTE@SELF: Port this over from App2

A new worktop/durable module was added in #80, which means there's no reason for this ticket to remain open. The new module is available under the worktop@next version and will released in the next stable (non-@next) version.
It's possible a new worktop/storage module would surface in the future, but probably not in the way(s) suggested earlier in this ticket.


Make "internal" plugins normal plugins

Final thing to do is renaming external.js to plugins.js

Internal plugins don't have plugin objects yet. We'd have to pretty much move external.js into index.js for it to apply to all plugins.

yes something like that should be done


error when using prefix ... converts array to vararg

code
+package sandobx

+alias org.eolang.txt.sprintf
+alias org.eolang.io.stdout

[args] > app
  stdout > @
    sprintf
      "%d %d %d"
      ...* 1 2 3

result

@IngeniariusSoftware try again, should work now (I deployed version 0.21.0 to objectionary)

Job gh:cqfn/eo#489 is not assigned, can't get performer


Add plugin trigger API

This PR adds API for triggering an action when a Gradle plugin is applied to a project.
This is a wrapper API for Gradle's PluginContainer.withType(..) own API, but made tidier.

@dmitrykuzmin, PTAL.


SQL Server RevEng: Configure SqlServerDbContextOptionsBuilder

We could generate things like UseRowNumberPaging() and EnableRetryOnFailure() depending on the version of SQL Server we're scaffolding from.

Hmm, looks like this will require a significant change. We currently don't have access to the connection (or connection string) at the place where these are generated.

Note to implementer, use the following logic:

When SERVERPROPERTY('EngineEdition') is 5, generate .EnableRetryOnFailure()
When connection.ServerVersion is less than 11, generate .UseRowNumberForPaging()

Instead of passing the connection, providers should annotate the database model instead. We'll pass those annotations to this method to possibly be handled.

Closing old issue as this is no longer something we intend to implement.

EF Core Power Tools creates a readme with a proposed DbContextOptionsBuilder


Why are the mobile apps showing up as provisioned services?

Description
In my opinion, it is confusing to have the created mobile apps showing up as provisioned services. IS there a purpose to have these shown to the user and not hidden?
Environment
Operating system: MacOS 10.13.5
OpenShift versions: 3.9
Steps to reproduce

Create a mobile app from the service catalog
Navigate to your project

Hi @davidffrench,
Thanks for your feedback. This repo is now deprecated and is replaced by Mobile Developer Console. Could you please give it a try and if you still experience the same problem, please open a new issue in that project.
Thanks.


feat: Support version in generate script (box/box-codegen#418)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 2 (100.0%)  changed or added relevant lines in 2 files are covered.
9 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 41.328%

Files with Coverage Reduction
New Missed Lines
%

src/schemas.generated.ts
9
35.34%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
6653

Relevant Lines:
12263

💛  - Coveralls


Modified Batch file for Windows, if it's called directly

I was tricked by the first install and clicked on my Windows 10 on the gitblit.cmd and nothing happens. I looked into it and a environment Variable "CD" is used, but never set. I modified the batch file, so the current directory of the batch file is used as root folder for the classpath. So it worked without anything else to modify.
So nothing like set up a environment variable is needed.

The CD variable is a dynamic variable and does not need to be set explicitly. It is automatically set by cmd.exe.
Did you encounter problems because you do call the batch file from a different directory than the Gitblit directory, or because you somehow have CMD Extensions disabled?
In any case I would prefer to use a dedicated variable, like gbhome or something like that, instead of overwriting the automatic variable.

I automated it with the build-in variables from Windows NT cmd. It is the current directory, but not the directory of the batch file.
So it don't works if you start it for example in the Windows explorer.

Yes, it wouldn't have worked for that use case. Thank you for fixing it. If you don't mind, I'll change it to use a different variable name.

Actually, I cannot reproduce this problem. Testing this under Windows 10 when I double-click on gitblit.cmd in the Windows Explorer, the server starts without problems. It even works when I create a link and place it in a different directory, then double-click the link.
What does not work, is running the gitblit.cmd command on the command line from a different folder, e.g. gitblit 1.9.1\gitblit.cmd. But this would even need one more change, setting the base folder correctly.
I don't know if the latter is a often used use case, but we can still make it work. Still, I'll rather do it without setting explicit variables.


fixing model V1 reading and localized-concept path in V2

This PR fixes the following 2 issues

There was an error reading Time from yaml concept in V1
Currently there is only support for localized_concept (underscore separated) in V2 and some glossaries are using localized-concept (dash separated). So I've added support for both of these directory names.

Released version 2.0.6 for this change.


better make love of wireMesssage and GC

no need to use pool for wireMessage, cause it doesn't leave context of a function.
it is better to allocate it once before loop and reuse.
allocation on a stack didn't work, cause when it were passed to Decode(interface{}) it were copied to a heap cause of conversion into interface{}.
but if allocate in a heap by taking pointer, then only pointer is copied to interface{}

Nice catch! Manually merged.


Suggestion for eliminating forgetting to await bug

Search Terms
async await promise tslint
Suggestion
One bug that I see coming up frequently in people's code (which is also hard to debug / detect) is forgetting to put an await in front of an async function.   This could be eliminated by adding a compiler option that requires developers to explicitly mark when they don't want to await an async function.
Use Cases
This optional feature would greatly reduce hard to find bugs
Examples
await this.myAsyncFunction(someData)
nowait this.myAsyncFunction(someData)
this.myAsyncFunction(someData) TSLINT / COMPILER ERROR
Checklist
My suggestion meets these guidelines:

[ ] This wouldn't be a breaking change in existing TypeScript / JavaScript code
[ ] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. new expression-level syntax)

I'm pretty sure tslint's no-floating-promise rule covers this.

Yeah.


Adapt perfmetrics recipe for cds data situation

This is a reduced version of the full performance metrics to match the current data availability at the cds site. To make sure that missing data sets do not inhibit execution, please use with the --skip-nonexistent command-line option of the tool.

It's not clear to me why we need a reduced version.
I though the --skip-nonexistent option would take care of this automatically.

@mattiarighi some variables are missing completely, leaving diagnostics without any data. So, this recipe missing some diagnostics compared to the normal recipe.

It could be due to a missing gsnAddCyclic = True plot resource in the plot script.
I will check and create a PR if appropriate.

Here's a picture:


Metrics should only be reported when request method matches

@PhilipGough as @unleashed says,  please add a proper test, so we don't miss this again! :)

@unleashed yes its covered in the integration test. Run make integration_coverage and it will generate the report.
I can probably hit it in the unit test also if we need to but bear in ind this code will be split between auth and report in the coming days to enable caching so its going to change quiet a bit anywayI guess

@PhilipGough we need to make sure that we check for a non-matching mapping rule.
Given those mapping rules:

POST /testingendpoint

Try to do a "GET" to /testingendpoint.
It should be denied.


🚧Create unit tests for extension methods

Complete The Item Below

[X] I have updated the title without removing the 🚧 emoji.

Description
Create unit tests for the following extension methods:

[ ] IsReleaseToDoIssue()
[ ] IsReleasePullRequest()
[ ] LogAsError()
[ ] LogAsInfo()
[ ] BuildReleaseNotesFilePath()
[ ] GetReleaseNotes()

Acceptance Criteria

[ ] Unit tests created for the following methods:

[ ] IsReleaseToDoIssue() method unit tests created
[ ] IsReleasePullRequest() method unit tests created
[ ] LogAsError() method unit tests created
[ ] LogAsInfo() method unit tests created
[ ] BuildReleaseNotesFilePath() method unit tests created
[ ] GetReleaseNotes() method unit tests created

ToDo Items

[X] Change type labels added to this issue.  Refer to the Change Type Labels section below.
[X] Priority label added to this issue.  Refer to the Priority Type Labels section below.
[X] Issue linked to the correct project (if applicable).
[ ] Issue linked to the correct milestone (if applicable).
[ ] Draft pull request created and linked to this issue (only required with code changes).

Issue Dependencies
No response
Related Work
No response
Additional Information:
Change Type Labels

Change Type
Label

Bug Fixes
🐛bug

Breaking Changes
🧨breaking changes

New Feature
✨new feature

Workflow Changes
workflow

Code Doc Changes
🗒documentation/code

Product Doc Changes
📝documentation/product

Priority Type Labels

Priority Type
Label

Low Priority
low priority

Medium Priority
medium priority

High Priority
high priority

Code of Conduct

[X] I agree to follow this project's Code of Conduct.

Closed without implementation
Reason: Project is not used anymore.


Utp cross client testing

As it currently stands there are 3 upcoming utp implementations : fluffy, trin and ultralight. It would be great to establish few practices and test cases which would guarantee compatibility between all of the clients.
Things we can do (in increasing complexity order):

Generate test vectors for encoding and decoding of each utp packet (DATA, FIN, STATE, SYN, RESET), each client could use them in their implementation unit test suites.
Describe few test cases each implementation need to pass in theirs integration suites between 2 nodes of the same type.
Each implementation could create test app which would start uTP instance with some config and expose simple api (via command line , json-rpc or whatever we decide) like:

connect
read
write
close

Having such app would make it possible to create CI integration test suite in each client or event test manually certain conditions between clients. Ideally we would also find/implement something similar to https://github.com/Shopify/toxiproxy but for udp transport (as discoverv5 works over udp) to inject network failures (lost packets, timeouts) while working on localhost
4. Imo gold standard test would be to have some small testnet (like 3 nodes, one of each type), with some monitoring attached, and every node would disseminate some content via OFFER/ACCEPT messages using utp. But this is more of the integration between utp subprotocol and history (or state) subprotocol.
It would be great to hear other teams thoughts on this topic :) cc: @victor-wei126  @acolytec3

Generate test vectors for encoding and decoding of each utp packet (DATA, FIN, STATE, SYN, RESET), each client could use them in their implementation unit test suites.

This should be doable for us in short order.

Describe few test cases each implementation need to pass in theirs integration suites between 2 nodes of the same type.
This would require us to have an integration test suite :grimacing:  This is a bit farther off but still doable.

Each implementation could create test app which would start uTP instance with some config and expose simple api (via command line , json-rpc or whatever we decide) like:
We more or less already have this via our browser client.  Should be easy enough to add whatever additional bits are needed to configure the stream, basically just agreed upon content to stream.

What is the exact difference between (2) and (3)?

Generate test vectors for encoding and decoding of each utp packet (DATA, FIN, STATE, SYN, RESET), each client could use them in their implementation unit test suites.

This is also doable for us. I think someone should create a test vector spec so we can test cross client compatibility.

Describe few test cases each implementation need to pass in theirs integration suites between 2 nodes of the same type.

By this I am thinking of tests like when A sends DATA B responds with STATE, and we test other things like handshake, etc. I suppose that can be done with ethportal_peertest--there is work being done to just spin up 2 trin nodes and pass tests between them. We could just start a utp connection and then pass messages, verifying the responses. @acolytec3 by "integration test suite" is what I just described somewhat to what you mean?

Each implementation could create test app which would start uTP instance with some config and expose simple api (via command line , json-rpc or whatever we decide)

It seems like ethportal_peertest could be used exactly for this. I feel like a good route to go would be doing (1) and then (3), since ultralight has browser client and trin has ethportal_peertest.

By this I am thinking of tests like when A sends DATA B responds with STATE, and we test other things like handshake, etc. I suppose that can be done with ethportal_peertest--there is work being done to just spin up 2 trin nodes and pass tests between them. We could just start a utp connection and then pass messages, verifying the responses. @acolytec3 by "integration test suite" is what I just described somewhat to what you mean?

More or less.  It should be a lot easier for us now that I've got a functioning CLI version of our client available to work with that is using all the same existing code as the browser client.  We can also support testing via ethportal_peertest as long as it is going to leverage json-rpc for the tests and just treat the portal network clients as a black box.  We're going to be adding a simple jsonrpc interface for the CLI version of Ultralight in the next few weeks so exposing specific endpoints for testing should be trivial at that point.

what are capabilites/interface of this ethportal_peertest app ?
I think one question here do want to test uTP by itself or only with OFFER/ACCEPT (or both) ?
Imo the next step would be to create spec describing json-rpc interface that such uTP test app such implement. After that we could define required testcases.

It's been awhile since I've played with it, but last I checked ethportal_peertest is just a testing framework that spins up two trin nodes, one being the boot node and the other the test node, ie, one under test. Then the boot node issues a suite of tests, like sending ping, or findcontent requests, and the test node responds and we check if the expected response was received.
I think we should test uTP by itself first to make sure all implementations work and they work together. After that we can just treat it as a black box and it will be pretty easy to do full tests with OFFER/ACCEPT as those are just protocol messages.

I think we should test uTP by itself first to make sure all implementations work and they work together.

Totally agree !
So my proposal is: let each team build a simple test app with json rpc interface which mirrors common utp operations
This will enable following things (in order of complexity):

Manual testing of compatibility between implementations - everyone will have simple way of checking some scenarios
Building some test scripts which we can share between teams, to test some basic scenarios.
Build something similar to https://github.com/marten-seemann/quic-interop-runner, where each team could publish its test app in docket container, and we will be to inject some faults between app by ns3 network simulator.

I have implemented simple test app in nim - https://github.com/status-im/nim-eth/pull/461/files, just for starters.
Wdyt @acolytec3 @victor-wei126  ? If you are 👍  on this, I will create doc utp-test-app-spec.md which will describe json rpc apic this app should implement. Imo it should be as simple as possible, so the creating such app is not a big burden for each dev team.

My instincts say that most of this scope can already be covered by just directly triggering the OFFER/ACCEPT flow between the clients which Ultralight can already do without any additional work.  If we want to go down this route, w could expose the specified RPC methods from our existing NodeJS Ultralight client so it's probably not a big deal from my perspective but maybe a little bit duplicative.  My main concern is exactly the point you raised that it not be too complex an operation to build it independently of our main effort.

@acolytec3 on one hand I kinda agree with you that some of the scenarios can be triggered through using OFFER/ACCEPT flow, but on the other hand OFFER/ACCEPT add several failure modes on top of uTP  and uTP itself is not so trivial protocol to get right.
My instinct here say that even if we won't need such app immediately (as we will be able to test some scenarios thorugh offer/accept) , ultimately we will hit some edge case scenarios which will force us to implement such app to test utp in isolation.
As I say this does not need to be anything fancy, only mirror utp interface (connect/write/read/close) through some external interface (imo json-rpc is good candidate here as every client in ethereum space have access to some library taking car of it)

Makes sense. Should be trivial for us to implement so I'll add that to our json-rpc this week.

Is there still an appetite to build out this separate uTP app for interop testing or are we satisfied that all of this is being covered by the existing uTP interop testing already done?


[FeatureRequest] process analysis / device trajectory

Hello,
It would be nice if falco could produce a full record of applications call.
something that can produce similar view that these products do
https://www.carbonblack.com/2016/05/10/patterns-of-attack-youre-looking-for-answers-not-just-indicators/
http://www.cisco.com/c/en/us/products/collateral/security/fireamp-endpoints/datasheet-c78-733181.html
Thanks

Could you give us a bit more context on what you have in mind? A full sysdig capture around the time an alert is triggered?

Not the latter, even if it would be interesting too.
More to have a full record of executables launched on the system with process tree/forest, start/end time, user/group id, arguments.
A classical example is to show an office app or a browser starting a shell, some ifconfig/whoami command and ending with a root user app, shell or others.
Ideally the record is in a format which can be used visually easily (json for d3.js/elk?)

oh, so something similar to the spy_users sysdig chisel https://github.com/draios/sysdig/blob/dev/userspace/sysdig/chisels/spy_users.lua.
Where would you like to store this data?

And just to confirm, you don't want historical information, only a snapshot of the current state? I think with a sysdig capture around the time of the notification, you'd be able to visualize the current state fairly well.

spy_users is good but miss some stuff like end time, parent process
For example, I can't tell directly from spy_users if it's from an interactive shell, a cron, a shell trap or anything else
better if customizing output like
sysdig -c spy_users -p"%evt.num %evt.outputtime %evt.cpu %proc.name (%thread.tid) %proc.pname %evt.dir %evt.type %evt.info"

but -p doesn't seems as customizable as usual for chisel.
Yes, I want history.
A good example would be
http://www.d3noob.org/2014/03/visualize-linux-processes-via.html
with the addition of a time cursor (or play)
In this example, the input is csv format. I didn't found with a quick search if from a performance point of view csv or json is better.
sysdig can already output json but not for this chisel.
I think that's what needed

able to customize chisel output with more data
have json output
after more a d3.js to display either a state/snapshot, either the full history.
daemonize sysdig to record all the times which is what falco does if I'm not wrong. need to allow sub-tasks to do the chisel and record in specific log files.

is it correct?

I think we'd want to have falco write a trace file (augmented with additional information if necessary) and keep the analysis half confined to a separate program.
So I think this overlaps quite a bit with https://github.com/draios/falco/issues/81, although I'll keep this issue open as well for now.
Generally for chisels the output format is defined by the chisel. the -p argument to sysdg is used when outputting a stream of events.


Add Frax Finance Strategy to account for FXS in LP tokens

This allows Frax Finance to calculate FXS balances from free FXS tokens, as well LP tokens, both free and staked. It gives more weight to LP tokens that are staked for longer periods of time.

Thank you! 🙏🙏🙏


[ISSUE#1493] Azure Storage Accounts show container name only - should show storage + container name

Fixes #  1493
Description
Added container name variable and updated services' List Label to display Storage + Container name, only if it's a Blob Storage.
Specific changes

Add containerName variable to obtain the Service Container Name (If it's BlobStorage)
Update label used on get links when the Service Type is  BlobStorage

Testing

Replaced by #1648


Shovel buckets

For example, https://github.com/Ash258/Shovel-Ash258, does not shown, so, fix it.

The apps in https://github.com/Ash258/Shovel-Ash258/tree/main/bucket are not in .json format and ScoopSearch doesn't support indexing of .yaml manifests.


Revert "Xfail fluent and SwiftLint due to SR-9029"

This reverts commit 70ddb3726b8d69ba06c9f1f69dd9210184284035.
I fixed these in:
https://github.com/apple/swift/pull/19959

Going to wait for that other PR to land. Then I am going to trigger this.

@swift-ci test

The other commit landed.


Fix typo in tag

Change 'anonimity' tag to read 'anonymity'.

It's such a bad habit of mine. I fixed in so many times already, but always make the same mistake.


Template files in directory where md2pptx resides are no longer picked up

Search order should be:

Same directory as the Markdown file.
Path reference - such as ~/md2pptx/templates.
md2pptx install directory.

Fixed.


Use in anacrolix/torrent

I had some queries about uTP in anacrolix/torrent in https://github.com/anacrolix/go-libutp/issues/29, wherein this module was mentioned. There's some context in that issue.
Why do you provide TLS API? Shouldn't it be orthogonal to any uTP stuff?
Do you support dialling out from an existing UDP socket? This was a specific feature I supported in https://github.com/anacrolix/utp and https://github.com/anacrolix/go-libutp. Do you know if Transmission doesn't support this?
Are you interested in having this be the default uTP implementation in anacrolix/torrent?
Thanks!

I did some follow up testing. There are some issues in Close handling that lead to stalls and inability to cancel reads in this package. It also seemed to only operate successfully about 1/4 to 1/3 of the time that https://github.com/anacrolix/go-libutp does.


New Port: SuDokul

New Port for SuDokul
Game Information

Title: SuDokul
URL: https://github.com/Mode8fx/SuDokuL

Submission Requirements
CFW Tests
Ensure your game has been tested on all major CFWs:

[x] AmberELEC
[x] ArkOS
[x] JELOS

Resolution Tests
Test all major resolutions:

[x] 480x320
[x] 640x480
[x] 720x720 (RGB30)
[x] Higher resolutions (e.g., 1280x720)

File Structure

Your port should have the following structure:

portname/

port.json
README.md
screenshot.jpg
cover.jpg
Port Name.sh
portname/

Additional Resources
For an in-depth guide on creating a pull request, refer to: PortMaster Game Packaging Guide

We use a new header now
#!/bin/bash

XDG_DATA_HOME=${XDG_DATA_HOME:-$HOME/.local/share}

if [ -d "/opt/system/Tools/PortMaster/" ]; then
  controlfolder="/opt/system/Tools/PortMaster"
elif [ -d "/opt/tools/PortMaster/" ]; then
  controlfolder="/opt/tools/PortMaster"
elif [ -d "$XDG_DATA_HOME/PortMaster/" ]; then
  controlfolder="$XDG_DATA_HOME/PortMaster"
else
  controlfolder="/roms/ports/PortMaster"
fi

Done


How to get selected values in an array

HI i was trying to get the selected values in to an arry will you please help me how to get them ....

Hi @shivarambodumalla ,
you could do something like this:
var solOptions = { /* options omitted */ };
var sol = $('#mySelect').searchableOptionList();

// later

var selectedOptionsAsArray = sol.getSelection();

This will not give you the internal data structure but the actual selected checkboxes/radios instead.
Let me know if that helped you.
Cheers
Patrick

Hi,
How can I get the internal values, I don't want  the checkbox container
thank you

Hi @ikramcheb,
the internal data structure is attached to the input as sol-item data attribute so you could do this to convert the inputs to an array of the internal data representation:
var asInputs = sol.getSelection(),
    asInternalRepresentation = [];

// iterate over the selected items/dom elements
// extract the 'sol-item' data from it and store it in the other array
for (var i = 0; i < asInputs.length; i++) {
    asInternalRepresentation[i] = asInputs[i].data('sol-item');
}

Hi,
I got the following error
TypeError: asInputs[i].data is not a function
noting that sol.getSelections return an array of input, so the problem is how to extract the 'sol-item'

I thought I was returning jQuery objects but according to your error message it seems to be plain DOM elements then. The solution then is to wrap the object with jQuery again so
var asInputs = sol.getSelection(),
    asInternalRepresentation = [];

// iterate over the selected items/dom elements
// extract the 'sol-item' data from it and store it in the other array
for (var i = 0; i < asInputs.length; i++) {
    // change this
    // asInternalRepresentation[i] = asInputs[i].data('sol-item');
    // to this
    asInternalRepresentation[i] = $(asInputs[i]).data('sol-item');
}

should do the trick. Let me know if this worked.
Cheers

yes thanks,
just add label
$(asInputs[i]).data('sol-item').label


[$500] Workspace - Impossible to change workspace currency

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v1.4.59-0
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Precondition: User is logged in ND.  We should try to change name of already existing workspaces only.

Go to workspace profile.
Click on 'Default currency' > select any another currency

Expected Result:
Workspace currency is changed to newly selected.
Actual Result:
Workspace currency is not changed to newly selected.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/f775e5a0-f920-4410-9612-5e8af89ddf97

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01d779d698f27e25f6
Upwork Job ID:<PHONE_NUMBER>472347648
Last Price Increase: 2024-04-02

@kadiealexander I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

We think this issue might be related to the #collect project.

I think its related to this issue:
https://github.com/Expensify/App/issues/38928

Seems this can be fixed externally

i am no longer able to reproduce it on main .. is it still reproducible?

Issue is reproducible on latest main.
https://github.com/Expensify/App/assets/16502320/3f122358-5f45-4fd9-a18b-e75bc53014e8

Proposal
Please re-state the problem that we are trying to solve in this issue.
User is unable to change non-collect workspaces currency
What is the root cause of that problem?
the workspaces currency cannot be changed because in the updateGeneralSettings function we return if the customUnitID is undefined which is the case for all workspaces that are not "collect" workspace
https://github.com/Expensify/App/blob/3ca25eeccbfe4cef6c3ab4837ea05b42f96c9955/src/libs/actions/Policy.ts#L1510
What changes do you think we should make in order to solve the problem?
we need to change the condition above to either we can remove the || !customUnitID check completely:
    if (!policy)

or we can keep it but check that the current workspace has an outputCurrency property:
    if (!policy || (!customUnitID && !policy?.outputCurrency)) {

then to fix the typescript error in the optimistic, success and failure data we need to make sure that the customUnitID var is not undefined before modifying the customUnits property

change this to:

    ...(customUnitID && {
                    customUnits: {
                        [customUnitID]: {
                            ...distanceUnit,
                            rates: optimisticRates,
                        },
                    },
                }),

and here to:

               ...(customUnitID && {
                    customUnits: {
                        [customUnitID]: {
                            rates: finallyRates,
                        },
                    },
                }),

also here to:

                ...(customUnitID && {
                    customUnits: {
                        [customUnitID]: {rates: finallyRates},
                    },
                })

@hungvu193 Correct. The issue occurs with workspaces that are not of the collect type.

Proposal
Please re-state the problem that we are trying to solve in this issue.

Workspace - Impossible to change workspace currency

What is the root cause of that problem?

When we update the currency, this logic can return true because of customUnitID can be undefined

What changes do you think we should make in order to solve the problem?

We can remove the !customUnitID in this condition
Then, we need to call:

     Policy.openPolicyDistanceRatesPage(policyID);

once we visit the workspace currency picker screen (/settings/workspaces/policyID/profile/currency)

Then, we need to handle the offline mode. In this case, need to update this, this and this to just apply these change if customUnitID is not undefined

What alternative solutions did you explore? (Optional)

NA

Updated the RCA in my proposal, the solution is the same though.

This was fixed in follow up PR. We can close this

If we end up using solution from the proposals, lets pay $125 for their help.

I see that the changes are the same as in my proposal. just reminding you about the bounty as @mountiny stated. thanks

Kind reminder on this

$125 to @abzokhattab for their help cc @kadiealexander

Payouts due:

[ ] Contributor: $125 @abzokhattab (offer)

Upwork job is here.


Add dist folder in .gitignore file

https://github.com/MyPrivateRepositories/guide-open-source/issues/42


feat: zip and propagate private logs

Merge note_encrypted_logs and encrypted_logs into private_logs.
Propagate the fixed-size data of private logs instead of their hashes.

We don't have to re-hash the logs everywhere to check that they match the hashes in the public inputs anymore.
Change to L2 gas for private logs to be 0 because of the above.

Private reset kernel circuit silos contract address to the first field of private logs.

Which allows us to remove randomness and masked address for non-note logs.

Note tagging/discovery changes and tag siloing LGTM!
CC/ @nventuro it was either you or @iAmMichaelConnor that wanted to review encryption APIs?
CC/ @sklppy88, this affects note syncing in TXE.


[Bug] Change RDB output channels

I found more bugs about the RDN implementation after the PR https://github.com/open-mmlab/mmediting/pull/1292.
In the present version, self.mid_channels and self.channel_growth must be the same. Buggy codes:
https://github.com/open-mmlab/mmediting/blob/398572a2875c9a8f0f22059450056f055c88fca3/mmedit/models/backbones/sr_backbones/rdn.py#L114-L119
Explain: The first RDB outputs self.mid_channels channels (note that the output channel number of RDB must be the same with its input channel number, i.e., self.mid_channels). However, the second RDB is fed with self.channel_growth channels.
When self.mid_channels != self.channel_growth, the error occurs.
According to the RDN paper, the I/O channel numbers of all RDBs are self.mid_channels. As a result, the following GFF should be fed with self.mid_channels * self.num_blocks channels. Buggy codes:
https://github.com/open-mmlab/mmediting/blob/398572a2875c9a8f0f22059450056f055c88fca3/mmedit/models/backbones/sr_backbones/rdn.py#L121-L131
After this PR, self.mid_channels and self.channel_growth can be different. self.mid_channels is the parameter between RDBs, while self.channel_growth is the parameter inside each RDB.
Thank you.
@plyfager

Hey @ryanxingql , thanks for your contribution.
Can you create a unit test file (e.g., tests/test_models/test_restorers.py) and add a simple test case to ensure the modified code work well when mid_channels and channel_growth are different value?
The structure of the unit test can refer to TTSR, but can it can contain only one function to test the modified code.

Hi @LeoXing1996 , thanks for your reply.
I add the option channel_growth=32 to the cfg in the existing test file tests/test_models/test_backbones/test_sr_backbones/test_rdn.py.
In the buggy version, an error occurs. After this PR, this test runs successfully.
BTW, why don't we add these lines to the bottom of the test file?
if __name__ == '__main__':
    test_rdn()

Then we can simply run python tests/test_models/test_backbones/test_sr_backbones/test_rdn.py to run the test.

@ryanxingql My fault, I miss test_rdn.py under tests/test_models/test_backbones/test_sr_backbones/ folder.
I think this PR can be merged  🎉 .

@LeoXing1996 Thank you for your work!
I am also curious that how you run those test files.
Why don't we add these lines to the bottom of the test file?
if __name__ == '__main__':
    test_rdn()

Then we can simply run python tests/test_models/test_backbones/test_sr_backbones/test_rdn.py to run the test.
Is there any guidance of writing test files for people who want to add new models? Thank you.

@ryanxingql All unit tests are run with pytest. You can use the following command to run all the unit tests under the tests folder:
pytest -s tests/   # use -s flag to capture stdout

If you want to support new models you can refer to this tutorial. If you have any questions about the doc and implementation of MMEditing, please feel free to create an issue.
BTW, currently we are developing on 1.x version of MMEditing, which is based on MMEngine and MMCV 2.x. We strongly recommend you try and develop based on the new branch.

@LeoXing1996  Thank you!

@ryanxingql All unit tests are run with pytest. You can use the following command to run all the unit tests under the tests folder:
pytest -s tests/   # use -s flag to capture stdout

If you want to support new models you can refer to this tutorial. If you have any questions about the doc and implementation of MMEditing, please feel free to create an issue.
BTW, currently we are developing on 1.x version of MMEditing, which is based on MMEngine and MMCV 2.x. We strongly recommend you try and develop based on the new branch. RDB model in 1.x branch has the same bug, and we haven't had time to fix it yet. We would appreciate it if you could create another PR to fix this 🤣 .

OK I will fix it later. Good night!


WIP: webapp/src/logo/depviz: Update the depviz logo

Linking to the new SVG (in its outside-the-webapp location).
Also update the filenames from #72 to drop a redundant -logo.

Hmm, we probably need one of the more compact ideas from #14 as well.  The version which landed via #72 is too crunched in the header bar:

And once we get a suitable tiny logo in there, I'll need to adjust the offsets as well so the jump field can take advantage of the extra space.

the headerbar needs to change significantly. the whole site look is temporary-- it is not really usable atm.


Mentorship vue-page

I added the mentorship vue-page by observing the about.vue page
Please what do you think?

Oh no! I created from main... :( Let me try to clean this up


HAWQ-162. YARN containers are required evenly

When there are 3 hosts, 8 YARN containers are required, actually, resource broker should require 3, 3, 3 containers in 3 hosts

looks good.

The fix is good to me. +1


test(pageserver): add test_gc_feedback_with_snapshots

Problem
should be working after https://github.com/neondatabase/neon/pull/8328 gets merged
Summary of changes
adds a new perf benchmark case that ensures garbages can be collected with branches
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

The benchmark is running in the benchmarks(3) job, seems that the CI job is very smart at splitting those things...


[Question] Deployment with SSL

I'm using portainer in docker-compose. I'm using it to manage the server on which it's installed (I'm not using it to manage remote servers).
I followed the docs which showed this:
command: -H unix:///var/run/docker.sock

That works.
Now I want to enable SSL, and so I followed the docs which show this:
command:
  --ssl
  --sslcert /certs/live/DOMAIN/fullchain.pem
  --sslkey /certs/live/DOMAIN/privkey.pem

That also works, even though it doesn't include -H unix:///var/run/docker.sock.
What I don't understand is why for SSL I don't need to include -H unix:///var/run/docker.sock? Should I add that, or is it unnecessary?

@lonix1
-H unix:///var/run/docker.sock is just a shortcut command that will automatically create the default endpoint in Portainer at startup.
If you don't specify it, you'll be prompted to specify which Docker environment you want to connect Portainer to the first time you start it.

Ahh that explains it! When I didn't use that flag, and recreated portainer, I was asked that question which I hadn't seen before! :-)
Does that default refer to the "local" or "remote" option? I need the local one.

That default will refer to the local option.


Add GitHub's Green Software Directory

Insert URLs to the project here: https://github.com/github/GreenSoftwareDirectory

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as Good First Issue of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.
All new projects listed will be posted on our Mastodon channel.

@abbitude


Error message truncated at edge of screen, no way to scroll

When an error message is longer than the screen, there is no way to scroll the editor pane to the right to see what the rest of the error message says.

@microsoftsam Is this fixed with your change?

Yup.


Reproducing issue about ego Vehicle stop permanently for false positive objects

Dear Author, I am currently reproducing your work and I am seeing following issue.
When there is false positive of objects (most likely wrongly recognised as Pedestrian), the ego Vehicle permanently stops. According to the figure below, the the safety control mechanism think the false positive has velocity and will crash with vehicle.
I think the root of cause might be that Pedestrian in dataset always has constant velocity, therefore false positive objects always has velocity when neural network wrongly classify object as Pedestrian. However, I am confused as I also read your paper you have tracking code to further calculate the correct velocity.
I was wondering did you have this problem? Or this is my reproducing issue. Any hints will be helpful. Thank you!

Hi!
I also found this problem occasionally during my testing, my solutions are:

use more data
wait continous stop steps > 1200, the ego-car will go on without any restrictions : https://github.com/opendilab/InterFuser/blob/dcc2c20bba2c8656773baab5a552a27fb74e86dc/leaderboard/team_code/interfuser_controller.py#L262
or you can modift the code in the controller to get around this problem

I have another question about HybridEmbed. I saw it under init that you used with torch.no_grad():
https://github.com/opendilab/InterFuser/blob/dcc2c20bba2c8656773baab5a552a27fb74e86dc/interfuser/timm/models/interfuser.py#L37-L47
To my limit understanding,  with torch.no_grad() is used to disable gradient back propagation. I understand you might need it for image backbone because you can reuse the pertained model. But why is it also applied to lidar backbone since lidar backbone doesn't use pretrained model? Doesn't that disable the resnet ability to learn for a lidar backbone?
Thank you for your answer in advance.

Hi, the code is just used to get the feature_size when initializaing the module if we don't specify the feature_size. It foward the backbone with a zero tensor to get the shape of output.

For image backbone, we resue the pertrained model without any update. For lidar backbone, we update their parameters in the training stage. Detailed code is here: https://github.com/opendilab/InterFuser/blob/dcc2c20bba2c8656773baab5a552a27fb74e86dc/interfuser/train.py#L987

Thank you for your clarification, it is really helpful

Hi! I also found this problem occasionally during my testing, my solutions are:

use more data
wait continous stop steps > 1200, the ego-car will go on without any restrictions : https://github.com/opendilab/InterFuser/blob/dcc2c20bba2c8656773baab5a552a27fb74e86dc/leaderboard/team_code/interfuser_controller.py#L262
or you can modift the code in the controller to get around this problem

Dear Author, what is the meaning of stop steps? And what is the meaning of self.block_stop_sign_distance? I don't understand the explanation. Could you please explain more? Thank you very much! :)
https://github.com/opendilab/InterFuser/blob/dcc2c20bba2c8656773baab5a552a27fb74e86dc/leaderboard/team_code/interfuser_controller.py#L102

Hi, we find that in some cases, the agent gets stuck because it detects some non-existent objects or always recognizes there is a red light ahead. To bypass this kind of case in our controller, we use a variable to record the time steps that the ego-car doesn't move. And when this variable self.stop_steps is greater than 1200(in our setting), we will force the ego-car to go on, ignoring any restrictions.

self.block_stop_sign_distance: when the ego-car detects a stop sign, it will perfom a emergency stop. But after it's speed drops to 0, it possilby detects the same stop sign again and perfom a emergency stop agin... So we set this distance that if the car hasn't moved self.block_stop_sign_distance, it won't respond to stop sign.

Thank you for your clarification.
One more thing about  self.block_stop_sign_distance that confuses me is that  self.block_stop_sign_distance is set to 0 but the comment next to it says "# it means in 30m, stop sign will not take effect again". I don't understand that part. If  self.block_stop_sign_distance=1, does it mean that within 1 m, stop sign will not take effect again?

Sorry, the comment is misleading and i will fix it. When the car detects the stop sign, it will set self.block_stop_sign_distance to 2.0 ( https://github.com/opendilab/InterFuser/blob/dcc2c20bba2c8656773baab5a552a27fb74e86dc/leaderboard/team_code/interfuser_controller.py#L140 ).

If self.block_stop_sign_distance=1, does it mean that within 1 m, stop sign will not take effect again?
Yes, your unstanding is right. But before the ego-car detects a stop sign, this variable should be zero.

Thank you very much for your reply. It is really helpful! :)

@deepcs233 Dear Author, I was wondering what is the use of token_global?
https://github.com/opendilab/InterFuser/blob/e0682c350892a243cf40bf448622743f4b26d0f3/interfuser/timm/models/interfuser.py#L867-L870

The token_global is the global mean for each view input, and we hope to capture the global feature into one token. But we haven't ablated this design.

Sorry, the comment is misleading and i will fix it. When the car detects the stop sign, it will set self.block_stop_sign_distance to 2.0
https://github.com/opendilab/InterFuser/blob/dcc2c20bba2c8656773baab5a552a27fb74e86dc/leaderboard/team_code/interfuser_controller.py#L140

If self.block_stop_sign_distance=1, does it mean that within 1 m, stop sign will not take effect again?

Yes, your unstanding is right. But before the ego-car detects a stop sign, this variable should be zero.

Dear author, I have more questions.

You mention that when car detects the stop sign, it will set  it will set self.block_stop_sign_distance to 2.0. From the code, that corresponds to the case when stop_sign < 0.6. So lower stop_sign value represents higher probability of detecting stop sign?

Is the meaning of self.red_light_steps  similar to self.stop_steps ?https://github.com/opendilab/InterFuser/blob/dcc2c20bba2c8656773baab5a552a27fb74e86dc/leaderboard/team_code/interfuser_controller.py#L133

Is the meaning of if self.block_red_light  similar to self.block_stop_sign_distance ?
https://github.com/opendilab/InterFuser/blob/dcc2c20bba2c8656773baab5a552a27fb74e86dc/leaderboard/team_code/interfuser_controller.py#L136

What about the values of traffic_light_state and junction? (lower value represents higher probability or the other way around)

Since the safety distance is calculated from d_0/d_05/d_075/d_1/d_15/d_2.What is the meaning of d_0/d_05/d_075/d_1/d_15/d_2?
https://github.com/opendilab/InterFuser/blob/dcc2c20bba2c8656773baab5a552a27fb74e86dc/leaderboard/team_code/interfuser_controller.py#L208-L211

Hi！

Yes.
No. Our model sometimes always detect the non-existent red light and the agent will stop for a long time. At last, it will time out. So we set this variable to avoid the agent to stop for a red light with a long time.
It's explained in (2). These two variables are used together.
Higher value of traffic_light_state means higher probability of red or yellow lights. Lower value of junction means higher probability that the ego car is in the junction.
is the t in the code corresponds to the time step t in the paper?  Yes, d_05 means the maximum safe distance in 0.5 seconds. Others and so on. They are computed by this function: https://github.com/opendilab/InterFuser/blob/dcc2c20bba2c8656773baab5a552a27fb74e86dc/leaderboard/team_code/interfuser_controller.py#L172.

Hello, Shao Hao, when I look the controller code(interfused_controller.py), i have a question about the desired_speed.
In paper appendix B, it said the desired speed could get by solving the linear programming optimization
However, in code it is calculated as follow
desired_speed = max(                 0,                 min(                     4 * d_05 - speed - max(0, speed - 2.5),                     self.config.max_speed,                     2 * d_1 - 0.5 * speed - max(0, speed - 2.5),                 ), )
I do not understand the relations between the code and the linear programming, and what does mean of the code?
Looking for your replay. Thank you!

Hi, it's just a easy way to solve the linear programming problem. For safety, we directly compute the max speed that satifies all constrains. For example, in the code you provided, the term 4 * d_05 - speed - max(0, speed - 2.5) means that
desired_speed <= 4 * d_05 - speed - max(0, speed - 2.5)
The constrain comes from:
[desired_speed  (it means the speed after 0.5s)  + speed (it means the speed at present) + max(0, speed - 2.5) (for safety)] / 2 (get average speed) * 0.5 (driving time) < d_05 (it means the safety distance in 0.5s)
For clarity, the above inequality can be viewed as:
avg speed * driving time <= safety distance


issue tracker

ahoj, existuje nejaky verejny issue tracker? Ak by som sa chcel zapojit na com by som mohol pracovat?

Hi @xar !
Thanks for the suggestion and sorry for the late reply 😊  ...
We are currently working on making it easier for external people to contribute, which will include setting up a public issue tracker 🎉
We are currently upgrading our internal issue tracker (by Atlassian) to the shiny new version and will use it to create public milestones and issues.
For now I can share that we are looking for contributions in the following areas:

Making it stupidly simply to get started developing Web umenia on your own
Getting more content like articles and collections in English
Making the entire platform accessible in Slovak, English and Czech
Creating a ‘living pattern library’ to document our modular front-end design and make it easy to maintain and customise.

Is there any of those that sound interesting to you?

We are currently happily using the issues section here on GitHub for public issues.
Please keep submitting issues here. We have also added several issues ourselves that might provide a nice starting point for contributors.
Closing this issue...


Provision-EflowVM: improvement on registrationId parameter

Specify that the registrationId parameter on the Provision-EflowVM method can also be used when using DpsTPM provisioning.

@fgheysels : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@fgheysels : Thanks for your contribution! The author(s) have been notified to review your proposed change.

IMPORTANT: When this content is ready to merge, the reviewer must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"

Hi @fgheysels,
Thank you for your contribution. Your changes look good.
Thanks for improving the docs.
Pat
#sign-off


Grant permission to users, not devices

When Alice grants permission to Bob to access the internet through her current device, that permission grant should not be limited to only one of Bob's devices, and Alice should not be asked to choose which of his device(s) it applies to.  (Bob can trivially copy or swap his own device identifiers, so as a security matter, granting permission to a single device is impossible.)
To be specific, each permission grant allows a specified user to access a specified device.  Thus, the "Share Access" tab will show a list of users with whom one may share access through this device, or not, and the "Get Access" tab will show a list of devices (grouped by user) through which one has permission to access the internet, or not.
Assigning to @zahoriea for further consideration.  (Did you already create mocks for this?)

I don't object to this as I think it will be nicer for the majority of users who only use 1 tab, but I do think this will make both our code and UI more complex, as we will still need to keep the controls on the GET ACCESS tab per device.  So if we do this, going forward I think we would have two different looking rosters (GET which shows all controls per device, and SHARE which only shows users), and I think likewise our data structures in the uProxy core will need to be split so that we have some permissions on the RemoteInstance (whether we can get from them) and some on the User (whether we are willing to share with them)

I do think this will make both our code and UI more complex

It certainly breaks the symmetry between Get and Share, so I agree that it probably requires more code, including UI code. However, it also significantly reduces the amount of information and the number of actions/options displayed in the UI, so I'm not sure I agree that the UI would be "more complex"

our data structures in the uProxy core will need to be split so that we have some permissions on the RemoteInstance (whether we can get from them) and some on the User (whether we are willing to share with them)

I think this is a key point.  If we don't make this change before launch, then we will have users with stored permissions that are incommensurable with the new model, leading to a major problem.  That's why I think it's important that we fix this before launch.

This seems related to the chat we had in the fall about multi-device
management, cryptographic device keys and pairing devices.
Are you suggesting we try to support this issue without solving the crypto
first?
On Fri, Feb 27, 2015 at 11:40 AM, Benjamin M. Schwartz <
<EMAIL_ADDRESS>wrote:

I do think this will make both our code and UI more complex
It certainly breaks the symmetry between Get and Share, so I agree that it
probably requires more code, including UI code. However, it also
significantly reduces the amount of information and the number of
actions/options displayed in the UI, so I'm not sure I agree that the UI
would be "more complex"
our data structures in the uProxy core will need to be split so that we
have some permissions on the RemoteInstance (whether we can get from them)
and some on the User (whether we are willing to share with them)
I think this is a key point. If we don't make this change before launch,
then we will have users with stored permissions that are incommensurable
with the new model, leading to a major problem. That's why I think it's
important that we fix this before launch.
—
Reply to this email directly or view it on GitHub
https://github.com/uProxy/uproxy/issues/1014#issuecomment-76425416.

Outlining all the options here: https://docs.google.com/document/d/1p16jeodYUYF9tp2mh9nDVIHlKagzHZLYVHRKZLZkspw/edit#
I think crypto for user-authentication authogonal (you can either use a social network which is trusted to auth users, or you do crypto for sending messages); but either way you can do consent in an asymmetric user (getter) to instance (sharer) way.

@ryscheng yes, that is issue #708.  I've split the issue to track changing the user-visible behavior separately from inventing a cryptographic protocol for it.

Makes sense. Thanks for the clarification

Hi all, here's a first stab at this .. let me know if I'm capturing the intent here:

There are a couple of other new design elements pertaining to other bugs as well. You'll notice iconography in expanded and collapsed states for "pending" and "access granted" in issue https://github.com/uProxy/uproxy/issues/875 and a location for upload/download rates and time elapsed (or whatever data we decide to show) in issue https://github.com/uProxy/uproxy/issues/855 and https://github.com/uProxy/uproxy/issues/16
Feedback welcome! I was also reply to the other bugs individually.

PS, these may be easier to view/comment on in folio https://folio.googleplex.com/izzie/uProxy/022715 - User level permissions#%2FUserLevelPermissions_01.png%3Fz=half

Wow, beautiful!
I think all the mocks are correct, but there might be a misunderstanding in the annotations.  Under "USER-LEVEL PERMISSIONS", the text says "she grants access across all of her devices and you can choose which to proxy from".  I think this is not quite right.  If this said, "Roothu clicks 'Offer Access' on each of her devices so you can choose which to proxy from", I would agree.  However, as I noted above, the intention for this change is that each permission grant allows a specified user to access a specified device.
As a use case example, consider someone who has uProxy at home and at work, and wants to allow friends access to the internet from home, but not to the corporate network.

Thanks! :+1:
Final question, and then I think I'm clear on this model (and apologies if I'm getting in the weeds)
Suppose I have uProxy installed on a Work Laptop and a Personal Computer. I am currently online with my Work Laptop and my Personal Computer is asleep at home. Can I grant access to a device remotely? What about if that device is offline?
If the answer to these is "yes" then I will need to make a couple small changes to the "Share access" mocks.

I am currently online with my Work Laptop and my Personal Computer is asleep at home. Can I grant access to a device remotely?

I think we would love to be able to do this one day, but it is very far away, and requires considerable concept-design work on which we have not even started.  For the foreseeable future, each device can only control access to itself.

What about if that device is offline?

I hadn't even thought about this.  This is an interesting idea but it's definitely even further away, out in the dreamy mists.

Cool. Thanks!

If a user currently wants to control a remote device, I think our best strategy is point them to remote desktop tools (like Chrome Remote Desktop). As Ben says, this isn't planned for v1.

I think that we can pretty easily make a change so that the SHARE ACCESS tab only shows users, and when I grant access to Bob from my laptop, I am granting access to all of Bob's devices to my laptop only (and would have to permission him separately from my desktop).
I think the proposed changes to the GET ACCESS tab will be much more work and I'm not convinced it will be a better experience.  Specifically:

Having my friend permission or reject me for all their instances will be very difficult and not actually the behavior we want (I think this is similar to what Ben was saying above).
Having "ask for access" request access from all of my friend's instances will be hard to do, especially if they later sign on with more instances (do those instances immediately see my request?)
If we do decide to broadcast my request for proxy access to all of my friends instances, what happens to the instances that they haven't permissioned me on?  Do I later get to request access again from these instances?
I can think of a few more annoying questions if you want regarding this.

Any objection to just making the proposed changes to SHARE ACCESS but leaving the GET ACCESS tab alone?

Just discussed this with Lucas and I think we have a better plan:

We all seem to agree that SHARE ACCESS should only show users, not instances :)
For the GET ACCESS tab, we can show "ASK FOR ACCESS" as a control under the user (don't show any instances at this point).  Then each instance that we are permissioned for will appear in the UI, while any instance that we aren't permissioned for will be completely hidden from the UI.  Once you have permission to get access through multiple instances, you will see 1 start button per instance, plus only one "cancel" button (saying you don't want to have permission to proxy through any of that user's instances anymore).  We won't be making any of the changes described under the "USER-LEVEL PERMISSIONS" section of the mocks, as that would require keeping consent state in sync between multiple instances on the sharer side.
Once we make these changes, it will only make sense for the sharer to have set their device description (because this is only displayed to the get-access side).  We should prompt sharers to set a device description at the same time that we show the "sharing enabled" tooltip.

OK, I think all the thinking is converging nicely... putting it all in one place (same link as above):
https://docs.google.com/document/d/1p16jeodYUYF9tp2mh9nDVIHlKagzHZLYVHRKZLZkspw/edit#

@bemasc @dborkan @lucyhe and myself talked about this at the UI sync on Thursday. The outlined proposal SGTM and I think this bug is mostly "Ready for Work" (with the exception of the 'Name your device' dialog for first-time sharers ... I am happy to provide a mock for that)

Attached is a first stab at a first-time-sharing-on-any-given-device "Name device" flow. Feedback welcome!

It is a bit reliant on cleaning up the "Share access" icon tooltip in #1076 .. otherwise users may feel stuck in a bit of pop-up mayhem: the name device modal, success modal, and then share access icon popup

Great!

And maybe we should tell them how/where to look to change this later?

On the first idea, SGTM!
On the second, right now the Success modal reads "If you ever want to change it, you can do so within settings." Also made a version that points straight to the Settings hamburger instead:

Thoughts on wording/styling in either?

I just created https://github.com/uProxy/uproxy/issues/1077 for naming the device when a user shares for the first time.  We can do that work completely independently of permission changes, so let's keep this issue 1014 just for the permission change parts


Help!!! I need to  save the state of the game.

can I keep the bodies and their vectors and speed....when I reload the page? I use metter.js + PHP. is that even possible without changing your code very much?(very cool library, bro)

Try using MatterTools.Serializer on your world.

thanks)


Let middlewares modify metadata before dispatch

This is useful for middleware like commanded-audit-middleware, which would be able to put the command uuid inside metadata automatically.

Thanks @JoanZapata.


Microsoft.AzureCLI

https://dev.to/pradeepradyumna/azure-cli-get-repositories-list-1b40

Remove it from PC + clean-up - it doesn't support Azure DevOps Server.


typo and missing words

was:
understanding how this mechanic is an important piece...
should be:
understanding of how this mechanism behaves is an important piece...

Fixes #954

Ping. (I realize this is a minor commit, but just wanted to make sure I'm following the correct procedure, and that this fix doesn't fall through the cracks.)

Thank you for contributing to the TypeScript Handbook!
We are currently working through a large backlog of open PRs. As part of this, we're asking authors of PRs with active merge conflicts to assess if their changes are still needed, and if so, open a new PR.
For transparency, we are also working on a full-scale reimagining of the Handbook (see the TypeScript Roadmap), meaning we are largely closing down work on the current version of the Handbook. Typo fixes are always appreciated, but any new content should likely wait until the new Handbook is available so that it can be more naturally adapted to that format.


Make feathers-authentication match security documents

This pull request is a simple one that makes the code match the documentation.
Feathers.js documentation currently says HS512 is used for authentication, however, the default options in feathers-authentication appears to use HS256. Instead of issuing a pull request to decrease overall security of the authentication module, this pull request makes the defaults of feathers-authentication match the algorithm as described in the documentation.
Clearly one or the other is not fully accurate. 😄 This PR changes feathers-authentication to the HS512 default, but it may make more sense to change the document if this was intentional.
This is not reported as a security vulnerability because IMO it doesn't change the security posture of this application too much at this stage. Of course, a much better crypto person than I could say I am completely wrong and there are attacks on the HS256 construct that I am unaware of.
Warning
This hasn't been tested aside from changing the values and watching tests pass.

Agreed. This is a good call and an oversight on my part. I forgot to update it. The intent is definitely to use HS512. The stronger the better. 💪
Good catch and thanks for the PR @micaksica2!

Shooooot! @marshallswain pointed out that this will break existing apps so we can't release it as a patch release. Going to revert it and we'll slate it for the v2.0.0 release.

@micaksica2 I'm going to create a v2.0.0 branch pretty quick here and will add these changes there.

Whatever works for you guys


some questions about RDIoU calculation. F(Θ(o), Θ(t), k, k)

Hello, thanks for your great work, RDIoU
I have some questions about RDIoU calculation.
RDIoU parameter setting

mentioned paper, Θ(o) = sin(Θ(gt))*cos(Θ(a)), Θ(t) = sin(Θ(a))*cos(Θ(gt)), k=1(default)

RDIoU Θ opereation
F(Θ(o), Θ(t), k, k) = min(Θ(o) +1/2, Θ(t) +1/2) - max(Θ(o) -1/2 + Θ(t) -1/2)
=> if ( Θ(o) < Θ(t) ) => Θ(o) +1/2 - Θ(t) - 1/2
=> Θ(o) - Θ(t) = sin(Θ(g))*cos(Θ(a)) - sin(Θ(a))*cos(Θ(g))
= sin( Θ(g) - Θ(a) )
=> else ( Θ(o) > Θ(t) ) => Θ(t) +1/2 - Θ(o) - 1/2
=> Θ(t)- Θ(o) = sin(Θ(a))*cos(Θ(g) - cos(Θ(g)*sin(Θ(a))
= sin( Θ(a) - Θ(g) )
thus, F(Θ(o), Θ(t), k, k) = sin( Θ(a) - Θ(g) ) (if Θ(o) > Θ(t) ) ,  sin( Θ(g) - Θ(a) ) ( if Θ(o) < Θ(t) )

it is RIoU work same operation (Θ), right?
I think, the operation of RIoU minimized difference that degree(=yaw) of rotated gt boxes and rotated predicted boxes. right?

Hi, sorry i cannot understand your question 1, but your understanding on question 2 is correct.


moved ConfigLoopsHip to hip_net.go for modular hip loops

turned out to work just fine after migration @rcoreilly . rebased and should be ready

Looks good but probably better in the long run to also use a HipModConfig struct instead of the args -- then if we need to add something in the future it is easier, and the comments provide info to user about the meaning etc.

also needs updated with merge.


Start spot cleaning

Implement command for starting a spot cleaning. It is cleaning a area of 1x1 meter area but 2 times.

I haven't considered adding this because i wasn't sure why you would trigger that when you have to position the robot anyway. But now it's there, i think it should work for local and cloud v1, not sure about cloud v2.
Actually, the wellbeing App doesn't seem to have this feature either, so not sure if its even possible to trigger it via that API.
In the other APIs the command are there, so it should work - i haven't tested it though because it's late and i don't want to annoy my neighbors :)


Changing Docker CVE scanning to work with Dependency Check Action

Change docker CVE scanning action to work on push with dependency check

Hey @josspo ! I'm going to close this PR, because Dependency Check does not scan Docker images, see https://github.com/jeremylong/DependencyCheck for more info.
The docker scan is something we can still implement using the current action. We can talk further on chat if you have any doubts or further suggestions.