Feature Request: Manage multiple pin-drops from one instance

Although it is currently possible to run multiple instances of the scan with different accounts, AND see the scan results of all instances within each individual instance, one is unable to see/move a pin-drop that is not created in that instance.
Use case:

Open a scan at location "A" using PCT act. ALPHA in client omega
Open a scan at location "B" using PTC act. BETA in client zeta
Notice scanning appear around location "B" in client omega, in addition to scan around location "A"
3a. Notice cannot see pin-drop from client zeta in client omega
Notice the vice-a-versa of 3 & 3a

I believe it should be possible to observe in client omega when the pin at location "B" is created by client zeta. I'm less confident about the inverse (finding a pin that is already present).
🎸 keep on rocking 🎸 @mchristopher

It seems like allowing multiple logins from one client start to make more sense than trying to further integrate separate processes?


WIP: Migrate WattTime provider to new structure

Towards #44
TODO: Migrate unit test and remove old code.

Stale


Time to add AWS Timestream :)

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

AWS just launched AWS Timestream (time series database similar to Druid)


support for ES v5.x.y RC

Hi,
When are you planning to release an RC for the transport layer that supports ES 5.x.y?
Thanks!

Done.


Suggestion: Arm builds for Docker

It would be nice for Docker builds to support Arm so I can run this locally on a single-board computer at home or something similar.

Opened #59
A test manifest was published to ghcr.io/tailscale-dev/tclip:multiarch if you want to give it a try in the meantime.


##[error]ADFT0029: Unknown object type: BigDataPool.

Hello Kamil,
Thank for you adding the new notebook activity type. However, we are receiving an additional error when deploying the new notebook activity. This is for when using a bigDataPool in synapse (Dedicated SQL Pool).
Error: ##[error]ADFT0029: Unknown object type: BigDataPool.
Thanks.

Can you attach json file representation of the pipeline that contains this notebook activity?

Hey @NowinskiK! So this is related to the "sparkPool" key present in the "typeProperties" of the Synapse notebook activity. It looks like the construction of the Synapse activity in JSON doesn't follow the exact layout of other activities in ADF.
I attached one of the pipelines we use with the Synapse activity, PL_HRAPI_MDW_CodeTableJobs.txt, which starts on line 519; the "sparkPool" key, specifically, starts 614:
"sparkPool": { "referenceName": {"value": "IntegOraSynsp",  "type": "Expression"}, "type": "BigDataPoolReference"}


Deleted a unnecessary variable assignment in SQLCompiler.get_related_…

…selections.

It seems Jenkins has some issues with postgresql databases.


Support Orders & Shipments V2.1

Added (breaking) support for Orders & Shipments V2.1, should become a new major version.
For changes see:
Orders
Shipments
Summary of API changes;

pagination for orders introduced
multiple fields renamed/removed
filters added (FBR/FBB)

Tests are failing since the bol.com test environment does not support their new v2.1 version, how should I approach this?

As discussed we will create tests that will work with a static file as example response from the API, based on the example in the Bol Plaza API docs.


Allow for compiled package tgz to be uploaded

@drnic bosh moved towards compiled release instead of compiled packages, which should work with resource. https://bosh.io/docs/compiled-releases.html

Can you please update the readme for how we upload compiled-releases with this resource?


Feature/phone regexp

Confirmed against the following test values
phone("123") -> invalid
phone("9999999999") -> valid (no country code, no +)
phone("19999999999") -> valid (country code, no +)
phone("+9999999999") -> invalid (no country code, +)
phone("+19999999999") -> valid (country code, +)

This seems good to go.


Peer to Peer Code Review

Hi @joseheco and @qwibbler, I love your project! And all of the little added details are very fun to experience as a user, great job!  💥 👏
I would like to make a suggestion about the background color to the even numbered books on the list, because with transparent background is hard to read the text. Maybe a solution could be just to add a css rule like the following:
#bookList ul:nth-child(even) {
    background-color:  /*some color*/;
}

Happy coding!

Hi guys, :wave:
I have the opportunity to see your project and I really liked it.
I have one suggestion that could come in handy:

Here you could improve your project by adding some way to highlight the section you are seeing now.

Another thing I noticed was that the background image for the sections for the saved books disappeared because of a broken link, I'm not sure how can you fix this problem, but I think this page could help.
Happy coding! :smile:  :four_leaf_clover:


Blog Tags: Create get blog tag function

Can get blog tag item from id.
TEST=manual
gw bootRun and postman works.
Change-Id: If5b81205f772c93716f3a1ef887d7331b79cc583

Code Review comments can be found at https://gerrithub.io/q/If5b81205f772c93716f3a1ef887d7331b79cc583


Metric-server unable to collect metrics

Version:

k3s version v1.0.0 (18bd921c)
Describe the bug

To Reproduce

Start 3 VMs running Fedora Server 31, make sure they can reach each other
Open firewall portsfirewall-cmd --add-port=6443/tcp
firewall-cmd --add-port=6443/tcp --permanent
firewall-cmd --add-port=10250/tcp
firewall-cmd --add-port=10250/tcp --permanent
firewall-cmd --add-port=8472/udp
firewall-cmd --add-port=8472/udp --permanent

Install k3s without starting the servicecurl -sfL https://get.k3s.io | INSTALL_K3S_SKIP_START=true sh -

Add environment variables for servicecat >/etc/systemd/system/k3s.service.env <<EOF
[Service]
Environment="K3S_TOKEN=XXX"
# only on node1
Environment="K3S_CLUSTER_INIT=true"
# only on node2 & node3
Environment="K3S_URL=https://node1:6443"
EOF

Start k3s service

Expected behavior

kubectl top node and kubectl top pod should work on all three nodes, and no errors should show in the logs.
Actual behavior

kubectl top node shows only node1 when run on node1, <unknown> for the other two nodes, and errors with "Error from server (ServiceUnavailable): the server is currently unable to handle the request (get nodes.metrics.k8s.io)." when run on node2 or node3.
Additional context

The following is spammed in the logs for node2 and node3:
Dec 19 14:57:57 node2.localdomain k3s[2607]: E1219 14:57:57.392837    2607 controller.go:114] loading OpenAPI spec for "v1beta1.metrics.k8s.io" failed with: failed to retrieve openAPI spec, http error: ResponseCode: 503, Body: Error trying to reach service: 'dial tcp <IP_ADDRESS>:443: connect: no route to host', Header: map[Content-Type:[text/plain; charset=utf-8] X-Content-Type-Options:[nosniff]]
Dec 19 14:57:57 node2.localdomain k3s[2607]: I1219 14:57:57.392915    2607 controller.go:127] OpenAPI AggregationController: action for item v1beta1.metrics.k8s.io: Rate Limited Requeue.
Dec 19 14:57:57 node2.localdomain k3s[2607]: E1219 14:57:57.889042    2607 available_controller.go:416] v1beta1.metrics.k8s.io failed with: Operation cannot be fulfilled on apiservices.apiregistration.k8s.io "v1beta1.metrics.k8s.io": the object has been modified; please apply your changes to the latest version and try again
Dec 19 14:57:58 node2.localdomain k3s[2607]: I1219 14:57:58.896597    2607 controller.go:107] OpenAPI AggregationController: Processing item v1beta1.metrics.k8s.io
Dec 19 14:57:58 node2.localdomain k3s[2607]: E1219 14:57:58.935020    2607 available_controller.go:416] v1beta1.metrics.k8s.io failed with: Operation cannot be fulfilled on apiservices.apiregistration.k8s.io "v1beta1.metrics.k8s.io": the object has been modified; please apply your changes to the latest version and try again

I have this problem, and fixed it by editing /var/lib/rancher/k3s/server/manifests/metrics-server/metrics-server-deployment.yaml
   nodeName: vmpkube001.agrotis.local # Restric to run on my master       containers:       - name: metrics-server         image: rancher/metrics-server:v0.3.6         args:         - --kubelet-insecure-tls         - --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname

Hi Any Update on this. I am facing same issue with centos 7

In --cluster-init version v1.17.4+k3s1, I get similar issue with metric-server
Apr 05 21:05:52 master-12 k3s[1640]: I0405 21:05:52.090207    1640 iptables.go:155] Adding iptables rule: -s <IP_ADDRESS>/16 ! -d <IP_ADDRESS>/4 -j MASQUERADE --random-fully Apr 05 21:05:52 master-12 k3s[1640]: I0405 21:05:52.091926    1640 iptables.go:155] Adding iptables rule: ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/24 -j RETURN Apr 05 21:05:52 master-12 k3s[1640]: I0405 21:05:52.093615    1640 iptables.go:145] Some iptables rules are missing; deleting and recreating rules Apr 05 21:05:52 master-12 k3s[1640]: I0405 21:05:52.093734    1640 iptables.go:167] Deleting iptables rule: -s <IP_ADDRESS>/16 -j ACCEPT Apr 05 21:05:52 master-12 k3s[1640]: I0405 21:05:52.095800    1640 iptables.go:155] Adding iptables rule: ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/16 -j MASQUERADE --random-fully Apr 05 21:05:52 master-12 k3s[1640]: I0405 21:05:52.097867    1640 iptables.go:167] Deleting iptables rule: -d <IP_ADDRESS>/16 -j ACCEPT Apr 05 21:05:52 master-12 k3s[1640]: I0405 21:05:52.098338    1640 iptables.go:155] Adding iptables rule: -s <IP_ADDRESS>/16 -j ACCEPT Apr 05 21:05:52 master-12 k3s[1640]: I0405 21:05:52.099295    1640 iptables.go:155] Adding iptables rule: -d <IP_ADDRESS>/16 -j ACCEPT Apr 05 21:05:52 master-12 k3s[1640]: E0405 21:05:52.640725    1640 available_controller.go:419] v1beta1.metrics.k8s.io failed with: failing or missing response from https://10.43.16 Apr 05 21:05:53 master-12 k3s[1640]: E0405 21:05:53.684812    1640 available_controller.go:419] v1beta1.metrics.k8s.io failed with: Operation cannot be fulfilled on apiservices.apir lines 1-26

I'm on k3s version v1.18.6+k3s1 (6f56fa1d). This also made kubectl really slow to respond if I pointed my kubeconfig server: IP address to any other controller node than the first one I stood up. If I kubectl say get nodes against the first controller node it was ms fast. If I pointed it to controller node 2 or 3 it would take ~35 seconds to return get nodes.
Once I update the arg values for metrics server to the values luisbrandao suggested kubectl get nodes returned results fast no matter what controller ip my kubeconfig was pointed at.  and my controller logs were also not filled with all kind of metric server errors, retries, timeouts, and warnings.
        - --kubelet-insecure-tls
        - --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname

I am also seeing this, on 1.19.2-k3s1 on a 3-node RPi4 cluster - all nodes are control nodes.
In the secondary control nodes' logs (but not in the primary's logs), there are lots of these:
Oct 04 21:36:53 pi3.example.com k3s[25106]: E1004 21:36:53.462130   25106 available_controller.go:437] v1beta1.metrics.k8s.io failed with: Operation cannot be fulfilled on apiservices.apiregistration.k8s.io "v1beta1.metrics.k8s.io": the object has been modified; please apply your changes to the latest version and try again
Oct 04 21:36:58 pi3.example.com k3s[25106]: E1004 21:36:58.508805   25106 available_controller.go:437] v1beta1.metrics.k8s.io failed with: failing or missing response from https://<IP_ADDRESS>:443/apis/metrics.k8s.io/v1beta1: Get "https://<IP_ADDRESS>:443/apis/metrics.k8s.io/v1beta1": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Oct 04 21:36:59 pi3.example.com k3s[25106]: E1004 21:36:59.405102   25106 controller.go:116] loading OpenAPI spec for "v1beta1.metrics.k8s.io" failed with: failed to retrieve openAPI spec, http error: ResponseCode: 503, Body: error trying to reach service: dial tcp <IP_ADDRESS>:443: i/o timeout
Oct 04 21:36:59 pi3.example.com k3s[25106]: I1004 21:36:59.405183   25106 controller.go:129] OpenAPI AggregationController: action for item v1beta1.metrics.k8s.io: Rate Limited Requeue.
/apis/metrics.k8s.io/v1beta1": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

The metrics-server pod is apparently healthy and running on pi1. The service is apparently OK:
$ kubectl get services -n kube-system -o wide metrics-server
NAME             TYPE        CLUSTER-IP    EXTERNAL-IP   PORT(S)   AGE   SELECTOR
metrics-server   ClusterIP   <IP_ADDRESS>   <none>        443/TCP   21h   k8s-app=metrics-server

Trying to get stats from the primary control node sort of works but it can't see its own stats:
pi@pi1:~ $ sudo kubectl -v5 top nodes
NAME                       CPU(cores)   CPU%   MEMORY(bytes)   MEMORY%
pi2.example.com        292m         7%     1597Mi          20%
pi3.example.com        253m         6%     1577Mi          20%
pi1.example.com        <unknown>                           <unknown>               <unknown>               <unknown>

For secondary control nodes, it doesn't work:
pi@pi2:~ $ sudo kubectl -v5 top nodes
I1004 19:17:20.880717 2694661 helpers.go:199] server response object: [{
  "metadata": {},
  "status": "Failure",
  "message": "the server is currently unable to handle the request (get nodes.metrics.k8s.io)",
  "reason": "ServiceUnavailable",
  "details": {
	"group": "metrics.k8s.io",
	"kind": "nodes",
	"causes": [
	  {
		"reason": "UnexpectedServerResponse",
		"message": "error trying to reach service: dial tcp <IP_ADDRESS>:443: i/o timeout"
	  }
	]
  },
  "code": 503
}]
F1004 19:17:20.882321 2694661 helpers.go:114] Error from server (ServiceUnavailable): the server is currently unable to handle the request (get nodes.metrics.k8s.io)
[there's a big stack dump here - let me know if you need it]

I assume @luisbrandao's workaround will work, but obviously this needs a proper fix.

I tried updating the deployment as per the workaround (edited it with kubectl edit -n kube-system deployment.apps/metrics-server -o yaml rather than amending the file on disk). The change applied OK, pod was replaced and the metrics-server pod is now running on pi3. Alas, now pi1 and p2 have those errors in the logs and pi3 doesn't.
I restarted the metrics-server deployment, and the pod moved again, to pi2. Now pi1 and pi3 have the errors and pi2 doesn't.
So obviously the node can only see the metrics server when it's local. Does this imply a problem with the network setup? Should the metrics-server service have an external IP so the other nodes can see it? I'm new to k8s and pretty stuck here.

There is a solution/workaround posted in https://github.com/rancher/k3s/issues/1968#issuecomment-680219642 - similar to @luisbrandao's above but with a few more steps. It hasn't worked for me (yet!) but has for at least one other person - hopefully other people who find this issue might find it useful.
This doesn't change the fact that it should really work out of the box in k3s.


Medication order fulfillment delete

Script for deleting the fulfillment history for medication orders.
Medication orders previously contained fulfillment histories. This actually doesn't make sense as an order is a future concept and a fulfillment history is what happened. This also does not align with the QDM specification. This became an issue when trying to do QRDA exports because the
medication order QDM model did not support fulfillment history information. The UI for medication orders was changed to align with QDM, but previously entered medication orders still have fulfillment history which is no longer editable in the UI and affects calculations.
The script below removes the fulfillment history information. This will likely make patients fail. We will need to send out an email when we make this change.
To Test
See instructions here: https://jira.mitre.org/browse/BONNIE-660?focusedCommentId=97482&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-97482

This code exists in HQMF2JS (which is where the processing issues are occuring):
# returns cumulativeMedicationDuration in terms of days
hQuery.Medication::cumulativeMedicationDuration = (dateRange) ->
  #assuming that the dose is the same across fills and that fills is  stated in individual
  #doses not total amount. Will need to flush this out more at a later point in time.
  #Considering that liquid meds are probaly dispensed as total volume ex 325ml with a dose of
  #say 25ml per dose.  Will definatley need to revisit this.
  if this.administrationTiming() && this.dose() && @json['fulfillmentHistory']
    this.fulfillmentTotals(dateRange)
  else if this.administrationTiming() && this.allowedAdministrations()
    # this happens if we have a Medication, Order.
    cumulativeMedicationDuration = this.allowedAdministrations() / this.administrationTiming().dosesPerDay()
    # need to do in case of divide by zero error
    cumulativeMedicationDuration = 0 if isNaN(cumulativeMedicationDuration)
    cumulativeMedicationDuration

Should we also add a check for if the medication is an order here? If so, we do "administration timings". Otherwise, we do "fulfillment history" for calculations. I still think it's a good idea to do the script for DB cleanup purposes.

I ran the calculation tests against this code; 4 patients in 1 measure are failing after the rake task is run.


CI/e2e: intermittent failure in creating Kind cluster

Bug description:
An intermittent failure was observed in the CI due to Kind cluster creation failing:
[Tier 1][Bucket 9] Test TrafficSplit where each backend shares the same ServiceAccount ClientServerTrafficSplitSameSA
  Tests HTTP traffic from Clients to the traffic split Cluster IP
  /home/runner/work/osm/osm/tests/e2e/e2e_trafficsplit_same_sa_test.go:59
[BeforeEach] [Top Level]
  /home/runner/work/osm/osm/tests/framework/common.go:70
> ID for test:<PHONE_NUMBER>, Test dir (abs): /tmp/test-3037251730
Creating local kind cluster
[AfterEach] [Top Level]
  /home/runner/work/osm/osm/tests/framework/common.go:75

• Failure in Spec Setup (BeforeEach) [37.473 seconds]
[Tier 1][Bucket 9] Test TrafficSplit where each backend shares the same ServiceAccount [BeforeEach]
/home/runner/work/osm/osm/tests/framework/common.go:89
  ClientServerTrafficSplitSameSA
  /home/runner/work/osm/osm/tests/e2e/e2e_trafficsplit_same_sa_test.go:24
    Tests HTTP traffic from Clients to the traffic split Cluster IP
    /home/runner/work/osm/osm/tests/e2e/e2e_trafficsplit_same_sa_test.go:59

    Expected
        <*errors.withStack | 0xc00062f5a8>: {
            error: <*errors.withMessage | 0xc00073b340>{
                cause: <*errors.withStack | 0xc0005bb248>{
                    error: <*errors.withMessage | 0xc0001f4e80>{
                        cause: <*errors.withStack | 0xc0005bb218>{
                            error: <*errors.withMessage | 0xc0001f4e60>{
                                cause: <*errors.withStack | 0xc0005bb1e8>{
                                    error: <*errors.withMessage | 0xc0001f4e40>{
                                        cause: <*errors.withStack | 0xc0005bb1b8>{
                                            error: <*exec.RunError | 0xc0006bec80>{Command: ..., Output: ..., Inner: ...},
                                            stack: [..., ..., ..., ..., ..., ..., ..., ..., ...],
                                        },
                                        msg: "failed to get file",
                                    },
                                    stack: [0x266bb65, 0x266bb66, 0x26ae9b0, 0x26af59c, 0x2665ee7, 0xeb4fe1],
                                },
                                msg: "failed to get kubernetes version from node",
                            },
                            stack: [0x26af30c, 0x26af30d, 0x26af59c, 0x2665ee7, 0xeb4fe1],
                        },
                        msg: "failed to generate kubeadm config content",
                    },
                    stack: [0x26af7db, 0x26af7dc, 0x2665ee7, 0xeb4fe1],
                },
                msg: "failed to create kind cluster",
            },
            stack: [0x27c84e5, 0x27debda, 0x11d3003, 0x11d2c1c, 0x11d30e7, 0x11d8dad, 0x11d88f2, 0x1201351, 0x1200e67, 0x1200657, 0x1202e06, 0x1212478, 0x1212127, 0x27e5dd8, 0xf6f38f, 0xeb4fe1],
        }
    to be nil

    /home/runner/work/osm/osm/tests/framework/common.go:71
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS

Summarizing 1 Failure:

[Fail] [BeforeEach] [Tier 1][Bucket 9] Test TrafficSplit where each backend shares the same ServiceAccount ClientServerTrafficSplitSameSA Tests HTTP traffic from Clients to the traffic split Cluster IP
/home/runner/work/osm/osm/tests/framework/common.go:71

Is there any way to replicate this issue? Have we seen this in a while? As part of closing this issue, should we make sure we fail appropriately when the Kind cluster is not created properly?

Is there any way to replicate this issue? Have we seen this in a while? As part of closing this issue, should we make sure we fail appropriately when the Kind cluster is not created properly?

This has happened intermittently on the CI. I haven't seen this happen lately. Will close and reopen if it happens again.


fix contract wrapper and readme

I ran the ethereum worker registry contract unit tests and found some problems:

current codes do not comply with the deployed contracts, which causes the failure of transactions. Users may need to deploy brand new contract themself,
there is a bug in the ethereum_wrapper.py, namely representing tx hash without .hex() transformation.

I fixed the mentioned bugs and also embellished the readme file.

fixup issue #41

@Ram-srini default addresses are reserved in the new patch.


install docker 1.7 selinux takes very long time and restorecon exhausted CPU

My environment is Fedora 22 x86_64.  I met this problem when I upgrade to docker 1.7 from docker 1.6. Then I tried some combinations and the same issues occurs in these actions

Install docker 1.7 selinux
uninstall docker 1.7 selinux
upgrade to docker 1.7 with selinux

Also I cannot choose to install docker without docker-selinux package in Fedora 22
[root@localhost ~]# dnf install docker.x86_64
langpacks: No languages are enabled
Last metadata expiration check performed 0:00:00 ago on Tue Jul 28 10:15:42 2015.
Dependencies resolved.
langpacks: enabled languages are []
===========================================================================================================================================================================
 Package                                   Arch                              Version                                              Repository                          Size
===========================================================================================================================================================================
Installing:
 docker                                    x86_64                            1.7.0-6.git74e7a7a.fc22                              updates                            4.6 M
 docker-selinux                            x86_64                            1.7.0-6.git74e7a7a.fc22                              updates                             50 k

Transaction Summary
===========================================================================================================================================================================
Install  2 Packages

Total download size: 4.7 M
Installed size: 20 M
Is this ok [y/N]: y
Downloading Packages:
(1/2): docker-selinux-1.7.0-6.git74e7a7a.fc22.x86_64.rpm                                                                                70 kB/s |  50 kB     00:00
(2/2): docker-1.7.0-6.git74e7a7a.fc22.x86_64.rpm                                                                                1.0 MB/s | 4.6 MB     00:04
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                802 kB/s | 4.7 MB     00:05
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Installing  : docker-selinux-1.7.0-6.git74e7a7a.fc22.x86_64                                                                                1/2

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

ping @rhatdan I think these are your packages?

Please open a bugzilla on this issue.  Not a docker issue.

@dove-young could you open a bugzilla issue at RedHat / Fedora? I'll close this issue here. Thanks!


Please include tests in sdist

Please consider including tests in the source distribution. Linux distributions need  to run them, and the only alternative is using GitHub archives that are not guaranteed to be stable.

Thank you!


Set up a Gitbook for design documentation

Setting up a GitBook to store Keep design documentation outside of the Keep UI kit that's in Figma, such as best practices for error messaging, empty states, loading spinners, etc.

Drafting of the existing Keep design docs pulled out of Figma and now in GitBook (a much better place for doing things like unordered lists – yeesh, Figma is useless for that!)
GitBook is unlisted, but viewable here: https://keep-network.gitbook.io/keep-design-system/
@Gluzman any other design docs that you think would be good to add to this? Maybe the GitHub process as well?

Looking great.
Let’s review over zoom sometime soon.
Would love to also see an atomic approach to the system. From core elements to colors to bigger components.
We’ll want to duplicate this approach for tbtc as well I imagine.


Update readme to describe new NVM LTS syntax

Describe new NVM version syntax. Also bump versions in tests and docs

VALKHYLMHER VALENTIME VALKIRYE VENDETTA HAVED CHOSING GOD DISTURB FROM  MAIN LESS AERA SOVIETIC AERA FROM NEW RESPOWND HAVED CHANGING HALES OUT GATE OF UTOPIA


Strategy for merging branches in vmware-tanzu/antrea repo

Describe what you are trying to solve
All branches that are merged into master will be squashed.
Describe the solution you have in mind
Branches in vmware-tanzu/antrea repo, like ipv6, windows, should not be squashed.
@jianjuns @tnqn @antoninbas

@lzhecheng why don't you want them to be squashed? do you think having a single large commit is not a good idea?

@antoninbas Sometimes we break down a large PR into several small ones, right? I thought it should be the same.

That's true, as long as the individual commits are self-contained. I was just checking that we meant the same thing. "rebase" is disabled for the repo to avoid mistakes (PR with multiple commits which were meant to be squashed ends up being rebased because the wrong option is used when merging). However, these feature branches (e.g. ipv6) can definitely be treated differently. If I take care of merging it, I can temporarily enable rebase for the repo. Unfortunately, I don't think Github offers more granular controls (e.g. administrators can rebase but others cannot).

Thank you. Yes, I saw the case multiple commits in a PR, including "fix comments", got merged into master and the commit history looks not so good. Since Github doesn't support more granular control, let's save our efforts to temporarily enable/disable rebase and keep the repo as it is now.


Remove restoreKeys to clear cache after update

Description:
Suggestion (like commented here) to remove fallback hash key to avoid keeping dependencies "forever". Start with a completely clean cache whenever any dependency changes.
Related issue:
https://github.com/actions/setup-java/issues/269
Check list:

[ ] Mark if documentation changes are required.
[ ] Mark if tests were added or updated to cover the changes.

Hello @schuenadel. Could you please sync with the main branch ?

@dmitry-shibanov done ✅

This is a bad change, this effectively makes caching useless when the linked file like pom.xml has even a tiny change.

Yes, setup-java should use a per build system strategy for setting the restore-keys, for maven build system this change is really bad


can this network be deployed on cpus?

thanks.

+1

@hszhao Any reply to this? I tried training on cpu and it did not work.

Hi, currently only GPU version is supported as CPU training is much slower when compared to GPU training. To enable CPU training, you need to remove the CUDA part in 'tool/train.py' and modify the operators in 'model/san.py'.


Add support for line numbers

You should be able to automatically show line numbers via a showLineNumbers prop, and, additionally, you should be able to say what line number to start at (firstLineNumber?).
This would be very useful for when you want to show an entire file, but you want to put other things (like code review comments perhaps) between lines.

I'd love this feature. It would be great if you could specify an element to wrap each line. That way you could add line numbers and/or row highlighting.

@twe4ked I think an element to wrap each line is a bit more difficult than line numbers, since the number of dom elements on each line isn't defined and the spacing is achieved by the fact the pre respects white space/new lines

Yeah I thought that might be the case. It also gets tricky with highlights that go over multiple lines.

@PaulJuliusMartinez @twe4ked do you want to take a look at #27 and let me know what you think?

published the line numbers in 2.8.0


atomic-server embedded website hardcodes URIs to external resources

atomic-server embeds a single-page app which links to external resources at https://joepio.github.io/ and https://analytics.argu.co/.
Some users may not want to rely on those sites to be online - maybe for stability, speed, or privacy concerns. Some users may even want their service usable while disconnected from the internet.
Please - at least optionally, if not always - make atomic-server usable without dependency on external resources.

One approach might be to...
a) make the analytics conditional to a compile-time variable like use_analytics (which I would prefer was disabled by default but not a big deal).
b) make https://joepio.github.io/ a compile-time variable and ship all those externally hosted assets as example files - which concerned users could then build defined as `/assets/ and use a front-end web server (a.k.a. a reverse proxy) to to serve that content.  More elegant would obviously be if serving assets locally was implemented in the code.

Sorry, I forgot to check for existing issues :-/
I guess what I propose here might be easier to do short-term.  If you disagree or if this one turns out to be not-so-simple after all then simply close it.  In other words, let's limit this one to doing a "quickfix" and discuss beautiful solutions at #185 ;-)

Agreed, let's opt for making these variable for now!
On Sun, 17 Oct 2021 at 21:36, Jonas Smedegaard @.***>
wrote:

Sorry, I forgot to check for existing issues :-/
I guess what I propose here might be easier to do short-term. If you
disagree or if this one turns out to be not-so-simple after all then simply
close it. In other words, let's limit this one to doing a "quickfix" and
discuss beautiful solutions at #185
https://github.com/joepio/atomic-data-rust/issues/185 ;-)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/joepio/atomic-data-rust/issues/189#issuecomment-945182208,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQVBEP4TBIWDNRM64P5AXLUHMQSDANCNFSM5GFB6KIA
.

That was quick. Thanks!


If you have a rogue Verilog file in the current directory, the Verilator backend picks it up

To reproduce:

Pick an existing unit-test
Run unit-test w/verilator backend
Copy the generated Verilog file to the current working directory and introduce a bug in it
Re-run the test. The test now fails because it picks up the wrong Verilog file.

I have created Firrtl PR #758
Needs careful review.

PR #758 was merged some time ago


Can we make use of git submodules?

https://github.blog/2016-02-01-working-with-submodules/
Can we use a git submodule in hpcflow and matflow repos to link to this repo for the GHAs workflows?
And also for common documentation?

I am closing this, as it is duplicating this other issue.


feat: roundtrip FixedSizeList Scalar to protobuf

Which issue does this PR close?
Closes #8224.
Rationale for this change
This scalar type was missing from the protobuf serialization. Adding it for completeness.
What changes are included in this PR?
Updates protobuf to add a FixedSizeList scalar variant. I've re-used the same serialization mechanism as list, to minimize the changes needed.
Are these changes tested?
I've added a roundtrip test, which I think should be sufficient. I'm not deeply familiar with the proto module codebase, so if you have additional suggestions for tests, I am all ears.
Are there any user-facing changes?
This should be a backwards compatible change to the protobuf messages.

Thanks @wjones127 and @yukkit


Android: support find add-to-app mode flutter.sdk

hello? is there something wrong?

i don't known. see my comment. and what problem does it resolve? how can i test it?

In add-to-app projects like this one https://github.com/flutter/samples/tree/main/add_to_app/multiple_flutters
first run flutter pub get in multiple_flutters_module it will generate .android directory
after gradle sync there will be no flutter.sdk in main Android(multiple_flutters_android) project local.properties file, but in multiple_flutters_module/.android/local.properties
currently the plugin will just look at local.properties file in main android project.

thanks for your explanation


Adding support for non-master default branch in git

resolves #3057
Description
Adding support for non-master default branch in git
Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

@VasiliiSurov Off to a great start! It looks like there are a couple of code-style issues from flake8:
core/dbt/clients/git.py:118:51: E231 missing whitespace after ','
core/dbt/clients/git.py:120:5: E722 do not use bare 'except'


Does this project follow semver?

I'm just wondering if this project follows semantic versioning?
I ask because in version 3.14 there was a changed introduced in the Honeypot middleware that caused the default behavior of the middleware to change.
This change caused the contact form on my website to stop working.
I only ask because if it doesn't, I need to lock my composer version to a specific version rather than doing the "standard" ^3.0 in composer. Following semantic versioning, I would not have expected to have what is in actuality a BC break when going from 3.13.1 to 3.16.1.
Thanks for this library. I really like it.

Hello @adear11
Yes, I know that some "minor changes" in 3.x versions introduced breaking BC, and sorry by that. This is due this project started as something more experimental, but because its increasing popularity, I've started to follow semver from 3.14. So you can configure composer safety to "^3.14".

Thanks. I appreciate the info.


Develop HTML files for front end

Start developing the HTML files for the Front End views using Handlebars.js

Done


can you update to 1.20.1?

self explanatory

yeah, are there any plans for porting this mod to 1.20.2?

same


About Page

A new About page for myDiary linked to footer of the website

I would love to contribute.

Go ahead Create a PR I'll review

okay.
Will you describe what I have to do in details.

Create an About page on /about and connect it to the footer
The About page can consist of some writing describing what does the application does
You can refer to this screenshot too

shall I work on this ??

btw i've found and resolved an error while compiling may i raise a pull request ??

i've raised a PR #9 in response to issue #8 please merge it btw I'm workin on about page now


What is the difference between arm-64v7 and v7a? Can i download on v8a?

See in the README, module uses the official prebuilt ToyBox binaries from Landley site:
http://landley.net/toybox/bin
If you unzip the module installation file, you will see that three ToyBox binaries from the Landley are included:
toybox-aarch64
toybox-armv7m
toybox-armv7l
At the time of installation, module tests them one by one, in that order,
takes the first of the three that works on your platform and renames it and saves to:
/data/adb/modules/ToyBox-Ext/toybox-ext
E.g., if you have ARM v8, toybox-aarch64 should work for you and module will use that one for toybox-ext binary
If toybox-aarch64 does not work for you, module will test and install toybox-armv7m (or toybox-armv7l) as toybox-ext for your phone

If you don't believe :), you can test yourself, download the binaries from Landley, save them to eg:
/data/local/tmp
Mark them executable by:
chmod 755 /data/local/tmp/toybox-*
and test which of those Landley prebuilt binaries execute on your phone.
Use Terminal emulator and test eg:
/data/local/tmp/toybox-aarch64 --help
Eg, toybox-i486, toybox-mips64 and so will not work on ARM phones.
toybox-armv4l will work but that is for some ancient ARM devices (and I did not include into the module)
For ARM v7 and v8, only the above three make sense (all three will work) and the module installs the most appropriate one for your platform
You can check the file size and eg MD5 checksum between the installed toybox-ext and your downloaded ones, to see which one the module chose and installed

Btw, on the Landley ToyBox page:
https://landley.net/toybox
you can find the ToyBox source code and building instructions and build/compile the binary yourself and test on your phone
Eventually, you can replace the toybox-ext binary with another one, you must save it to the same place, make sure it is chmod 755, and reboot the phone

.


backgroundColorAlpha always transitions with 'white' as base

Not sure what I'm doing wrong.
When I transition an element with backgorundColorAlpha to a color opacity of 0 and then transition it back, it doesn't seem to work correctly for me.
Set transparent background:
elements.$dialog.velocity({
  backgroundColor: '#000000',
  backgroundColorAlpha: 0
})

Set alpha transparent background (same as rgba(0,0,0,0.5)).
elements.$dialog.velocity({
  backgroundColor: '#000000',
  backgroundColorAlpha: 0.5
})

The element results in different color, transitions with white instead of black, background-color: rgba(255, 255, 255, 0.498039);

Needs a demo / test case for us to look at - but definitely looks like an inconsistency there.


confusion of ModuleNotFoundError

Dear Mr. Colluca,
When I try your latest version, I encounter issues such as "ModuleNotFoundError: No module named 'snitch' "and other missing library function problems. This is the output from the shell when I run the command sudo docker run -it --rm -v ~/cpp/snitch_cluster:/work -w /work/target/snitch_cluster ghcr.io/pulp-platform/snitch_cluster:main make bin/snitch_cluster.vlt, which I have recorded in out.log.
out.log

Yes, indeed you have to locally install the package by running pip install -e .. Will update tutorial instructions as soon as possible.


Wildcard route collision

Folio Version
1.1.3
Laravel Version
10.22.0
PHP Version
8.2.3
Description
Hello team,
Thanks for the great job. Laravel Folio is really amazing.
Thus, I don't know if I should create a new issue for it has almost the same topic.
I still have some routes (files) that are not accessible due to collision with another wildcard route.

The route /create is not reachable. When trying to access it, Folio keeps using /{id} and just passes the term create as $id.
Steps To Reproduce
Create a new Laravel project using Folio and the following tree structure (without implicit model binding).

Can you create an Laravel application that faces this issue, push it to GitHub, an give me the link so I can try it locally please?

Nevermind. I understand the issue now. So, at the moment, if you are using something like:
create.blade.php
[User].blade.php

When passing /create, Folio will try to see if there is any user with the ID create. If not, it will try to match literal views, and of course, create.blade.php matches the given value, so create.blade.php will be used.
In your use case:
create.blade.php
[id].blade.php

The [id].blade.php does match the given /create, because the create string does match the given wildcard ID. I don't think there is an issue here, because wildcard views do take precedence over literal views at the moment.
@taylorotwell What's your opinion on this?

I can suggest one of the options below:

In FolioServiceProvider, we could introduce a property called $pipelinePriority (as is the case for middlewares in Kernel.php). This will be used to define precedence in the Folio route resolver.

Or, similarly, add a config key to hold this prioritization.

So either way, everyone could configure the priority regarding his use case.
I hope it makes sense !

@nunomaduro I think I'm gonna close this issue in favor of a new one... 🤔
I was wondering why I didn't use model binding and then remembered that I didn't because I was facing an issue with the connection used for binding resolution.
The thing is... It seems like the Folio route model binding resolution happens before middlewares are applied 🤔. Thus, in my case, I had a middleware in charge of changing the current database connection dynamically.
I tried using the default routing system in the same project and things started working as expected. Back to Folio, it's no longer working (resolving the suitable database connection).

Closed in favor of https://github.com/laravel/folio/issues/123


[HOLD for payment 2024-10-31][$250][Search v2.1] - In to field, selecting & unselecting contact, avatars of user in drop-down list flickers

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: 9.0.31-14
Reproducible in staging?: Y
Reproducible in production?: Y
Issue reported by: Applause Internal Team
Action Performed:

Launch app
Tap on a workspace chat
Submit an expense
Navigate to LHN and tap search at bottom
Tap filter
Scroll down to tap "to" field
Select and unselect the first contact

Expected Result:
In search to field, selecting and unselecting contact, avatars of user in drop-down list must not flicker.
Actual Result:
In search to field, selecting and unselecting contact, avatars of user in drop-down list flickers.
Workaround:
Unknown
Platforms:

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

Screenshots/Videos
https://github.com/user-attachments/assets/936401ab-50f2-4ac9-89e1-ef313a096c41

View all open jobs on GitHub

@sakluger  FYI 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

Hi! I'm from SWM and I would like to work on this issue.

Hey @dukenv0307, sorry for the delay. Here's a payment summary with a link to the Upwork offer.
Summarizing payment on this issue:
Contributor+: @dukenv0307 $250, sent offer via Upwork: https://www.upwork.com/nx/wm/offer/104686780

All paid, thanks!


Wrong redirected URL when installing new WordPress bedrock 1.13.0

[x] I've read the guidelines for Contributing to Roots Projects
[x] This request isn't a duplicate of an existing issue
[x] I've read the docs and followed them (if applicable)
[x] This is not a personal support request that should be posted on the Roots Discourse community

Description
When installing new WordPress with latest Bedrock version 1.13.0, the redirected URL to installation page is wrong, which is http://domain/WP_HOME/wp/wp-admin/install.php

If I change the URL to the right one which is http://domain/wp/wp-admin/install.php, all assets such as JS or CSS files' URLs are wrong.

Steps to reproduce

Clone bedrock from github
Run composer install
Access the bedrock to install new WordPress/BedRock instance

Expected behavior: Redirected to domain/wp/wp-admin/install.php
Actual behavior: Redirected to domain/WP_HOME/wp/wp-admin/install.php
Reproduces how often: 100%
Versions
You can get this information from referencing CHANGELOG.md. Also, please include the OS and what version of the OS you're running.
BedRock 1.13.0
Additional information
I believe that the behavior is from phpdotenv v4 because I have tried to upgrade to this version before, but it went crazy and I could not handle it.

Not seeing this with this testbed: https://github.com/austinpray/bedrock-testbed/tree/br-493
How exactly are you running this locally?

Ah never mind I can reproduce this by using the .env.example provided in the repo

https://github.com/austinpray/bedrock-testbed/tree/br-493-reproduced
working vs not working

@nhanledev see if this fixes your issue https://github.com/roots/bedrock/pull/494, it does for me

@austinpray I can confirm that changing from a single quote to double-quote of WP_HOME in .env file fixes this issue.

Sweet! Tagged a bugfix release https://github.com/roots/bedrock/releases/tag/1.13.1

On Azure Web Apps this issue persists, this is because the environment variables are defined in the "Application Settings", so there is no way to add single qoutes or double qoutes.
so my only option was just to write the full domain twice, like WP_HOME=http://example.test and WP_SITEURL=http://example.test/wp
Also, for some reason the Azure web app does not like the salt keys to have curly brackets and other symbols, so i wrote them with only numbers and letters and few symbols .


Switch to nyc

Switch to nyc front-end for istanbul and drop node 4 & 5 from CI because of this.  The latter is probably more controversial, but since node 6 is LTS now, I don't feel compelled to test anything else in CI.

Coverage remained the same at 100.0% when pulling 219fcb56b859aa28ba30069c9e5e9bab3276c896 on switch-to-nyc into a006e6e1fcaedfd92bb853c6b29d0d05bbfd74cf on master.

Coverage remained the same at 100.0% when pulling 1dd8407a9a5fe28ba49ee1166cbb422d38bf0c8e on switch-to-nyc into a006e6e1fcaedfd92bb853c6b29d0d05bbfd74cf on master.


iot2050setup: Add arduino board pinout

Our reference design is UNO3.
Although you can query the specific pin through this:
https://cache.industry.siemens.com/dl/files/016/109779016/att_1018122/v1/iot2050_operating_instructions_en_en-US.pdf?download=true.
But this is not very intuitive.
It shows the block diagram of our arduino board,
which is convenient for query and use.
Signed-off-by: chao zeng<EMAIL_ADDRESS>

This is indeed very useful! I'm regularly searching for this layout in the web.
How about also explaining what is meant with "ICSP", this 6-pin connector?

yes, that is the 6-pin header.
The "ICSP" is from the arduino pinout, and in our operations guide also call this as ICSP.
We synchronize the abbreviation of this convention, I don't think we need too much description in this pinout.
how do you suggest?

How about something like this, to improve readability?
            +--------------------------------------------+
            |                                     A5/SCL |  IO19
            |                                     A4/SDA |  IO18
            |                                       AREF |
            |                                        GND |
            | N/C                                 SCK/13 |  IO13
            | IOREF                              MISO/12 |  .
            | RST                                MOSI/11 |  .
            | 3V3    +---+                         SS/10 |  .
            | 5V    -| A |-                        PWM/9 |  .
            | GND   -| R |-                        PWM/8 |  IO8
            | GND   -| D |-                              |
            | Vin   -| U |-                        PWM/7 |  IO7
            |       -| I |-                        PWM/6 |  .
      IO14  | A0    -| N |-                        PWM/5 |  .
      .     | A1    -| O |-                        PWM/4 |  .
      .     | A2     +---+                    UART_RTS/3 |  .
      .     | A3                              UART_CTS/2 |  .
      .     | A4/SDA   ICSP                    UART_TX/1 |  .
      IO19  | A5/SCL +-----------------------+ UART_RX/0 |  IO0
            |        | RST  SCK/13   MISO/12 |           |
            |        | GND  MOSI/11  5V      |           |
            |        +-----------------------+ __________/
            \_________________________________/

BTW, what is that notch at the bottom about, what should it represent?

notch
Surrounding ICSP with a dotted line is good advice.
the notch is just for looks.

BTW, what is that notch at the bottom about, what should it represent?

Almost every uno shield has such notch.


Fix scsi_id installation

systemd-udev must be installed to get the scsi_id binary.
Fixes this build error:
2020-11-23 07:36:50,815 - atomic_reactor.plugins.imagebuilder - INFO - cp: cannot stat '/usr/lib/udev/scsi_id': No such file or directory

BTW, why the driver needs extra copy of scsi_id?
Edit: because /lib/udev comes from the host, see https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/pull/459
cc @openshift/storage

/retest


Error when intermedia data type is not a struct type

Backend
VL (Velox)
Bug description
when define an intermediate type of the uadf without Row as:

and register a UDAF signature:

but an error occurs:

Spark version
None
Spark configurations
No response
System information
No response
Relevant logs
No response

@marin-ma

Is the root cause that UDF doesn't support struct?

Is the root cause that UDF doesn't support struct?

Multi-parameters in intermediate can be set in this way, but it is wried for users, when they want only to use a single type.
by the way, if the intermediate type is struct<XX_type>, the aggregate planNode can be transformed error.


Add grapqhl support for custom field definitions

As ...
Nelly - Network Engineer
I want ...
To be able to query custom fields via GraphQL
So that ...
I can use the GraphQL interface to get a list of all current custom fields as well as the custom field a custom field choice relates to.
I know this is done when...

I can query custom fields:

query {
  custom_fields {
    key
  }
}

I can query custom field choices and get the related custom field:

query {
  custom_field_choices {
    custom_field {
      key
    }
  }
}

Optional - Feature groups this request pertains to.

[ ] Automation
[ ] Circuits
[ ] DCIM
[ ] IPAM
[ ] Misc (including Data Sources)
[ ] Organization
[X] Apps (and other Extensibility)
[ ] Security (Secrets, etc)
[ ] Image Management
[ ] UI/UX
[ ] Documentation
[ ] Other (not directly a platform feature)

Database Changes
None
External Dependencies
None

Missing @extras_features("graphql") on the CustomField model declaration. Also missing on the Relationship model declaration, would probably make sense to add there as well.

Some prototype code in https://github.com/nautobot/nautobot/tree/u/glennmatthews-5917. Needs testing.

Let's cover all the extras features that make sense to also include support for.


False-Positive Non-terminating error upon calling java.exe

Describe the bug
Reporting an error upon calling java.exe, despite being able to connect to Jenkins without any issues
To Reproduce
Steps to reproduce the behavior:

run the EXE/Service with fully correct details

Expected behavior
Errors should be only when thing don't work as expected
Screenshots

Desktop (please complete the following information):

OS: Windows Server 2016
Version 1.0-Alpha

Additional context
java.exe : Aug 04, 2024 4:26:24 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
At line:265 char:1
+ & "$JavaPath\java.exe" -jar "$JenkinsPath\agent.jar" -url "$JenkinsUR ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Aug 04, 2024 4:...itializeWorkDir:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

``
writeErrorStream      : True
PSMessageDetails      :
Exception             : System.Management.Automation.RemoteException: Aug 04, 2024 4:46:46 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
TargetObject          : Aug 04, 2024 4:46:46 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
CategoryInfo          : NotSpecified: (Aug 04, 2024 4:...itializeWorkDir:String) [], RemoteException
FullyQualifiedErrorId : NativeCommandError
ErrorDetails          :
InvocationInfo        : System.Management.Automation.InvocationInfo
ScriptStackTrace      : at , : line 1
                    at <ScriptBlock>, <No file>: line 1

PipelineIterationInfo : {0, 0}
``

Fixed in Last Release


Parse .txt file to get a new random word #5

Implemented file read from words-alpha.txt to get random word.
Now calling Build() for a promise from index.js then creating the controller, store, and view once the promise is resolved with a fully built Store (with random word).
Also started the for loop in view.js at 1 instead of 0 since the starting string already had a " _ " in it.
Let me know if you have any questions!

Super awesome! Thanks! Make sure to check out the README to join our discord and join the organisation if you'd like!


QS clock, alarm and date are scrambled

Description
Drop down line is not in the middle and clock, date and alarm are scrambled in QS.
Edit QS is not working.
Steps to reproduce
Toggle New style from Android P
Toggle force dark theme
ROM info
Moto G5 Plus (XT1687) Android 8.1 stock version (security patch aug 01/18)
Module version (build version)
Android P-ify version 1.0.0 #153
Xposed log / logcat
Xposed log
Screen shots

P.S: I'm using other Xposed modules like GravityBox, I already disable it and issues still persist.
Thank you.

Hi bro how i Can use Android p ify on my phone Android 5.0 , i have xposed  , ????

Faresavoca, no, you can only use this module on Android 8.0/8.1


Attempting to pass data_dir flag with run_from_fasta.py does not overwrite the default directory

Passing in the data_dir flag does not seem to update the default path when searching for files such as pub_mmcif/mmcif_files

I've fixed the issue and will submit a pull request soon

Thank you for your report. I think the situation you happened to meet is a BUG already fixed in the upstream repository (dptech-corp:main). I am sorry that this fork was not timely synchronized. You may pull the newest commits and see if the bug is fixed. Thank you again for your interest in Uni-Fold.


[helm] Fixed persistency for Grafana

This is the copy of #1054 PR. Link to fork was lost for some reason. Recreating it, since issue is still valid. @gianrubio Please review.

thanks @vglafirov


Manual approval required for workflow run<PHONE_NUMBER>

Workflow is pending manual review.
URL: https://github.com/pushpendrasingh3/manual-approval/actions/runs/8250660187
Required approvers: [pushpendrasingh3]
Respond "approved", "approve", "lgtm", "yes" to continue workflow or "denied", "deny", "no" to cancel.

approved

All approvers have approved, continuing workflow and closing this issue.


add saving array length in bitwise operations

@IngeniariusSoftware I think that if two arrays are of different lengths, we must throw an exception

@yegor256/z everybody who has role REV is banned at #464; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@yegor256 we have another problem with bytes operation
ByteBuffer and BigInteger have diffrent system of storage number, for example number -25723423423423L
ByteBuffer: [-1, -1, -24, -102, -52, 124, 4, 65]
BigInteger: [-24, -102, -52, 124, 4, 65]
So if we do not know that we are working only with the int type it becomes a problem

@IngeniariusSoftware I don't think we need to work with BigInteger at all. We should just convert long to 8 bytes and that's it.

@yegor256 , what way do you intend to implement instead of BigInteger or do you suggest not working with bytes longer than 8?

@IngeniariusSoftware I would work with byte arrays directly, using for. Basically, iterating through elements and applying AND/OR operations to them. In case of shifting left/right, I would also try to work with the array. The algorithm would be more complex, by still possible to implement.

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


用户拖动PageView时禁止自动滑动

当PageView设置自动滑动时，用户拖动时禁止自动滑动；
解决PageView内存泄漏问题。

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

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


Add two sections to the VIP.RestrictedFunctions sniff.

Using ini_set() for alternating PHP settings, as well as other functions with ability to change configuration at runtime of your scripts, such as error_reporting(), is prohibited on the WordPress.com VIP platform. Allowed error reporting in production can lead to Full Path Disclosure.

See https://vip.wordpress.com/documentation/code-review-what-we-look-for/#settings-alteration
I've added the most obvious PHP functions which would relate to this. Careful review of the functions listed needed & appreciated.
Fixes #460

Looks good to me.

Thanks ;-)


UI for conversation management

The management of conversations should be done by none technical persons. Therefore we need a user friendly admin UI, that allows managing stored conversations.
Issue #5 - "Handle/manage lifecycle of stored conversations" requires a management "tool" that allows to manage stored conversations. Issue #32 specifies and implements the according API.
Acceptance criteria

[ ] The configuration options for #5 are manageable via U

todo: fix $inject problems in conversation-controller


export fields in diff reports for json

Review Error for zblach @ 2018-12-13 19:07:50 UTC
User failed mfa authentication

Review Error for samnrubin @ 2018-12-13 19:16:20 UTC
User must have write permissions to review


Add support for non named data types

Hi Firely team,
We have been trying to use Patch method to add some info to the existing objects, but there seems to be a trouble if the type is not the one specified in FHIR spec as Datatype (https://www.hl7.org/fhir/datatypes.html#open).
At the https://www.hl7.org/fhir/fhirpatch.html#anonymous there seems to be a description of how you can patch those objects.
So I investigated the issue and add support for this functionality. Could you please check it?
If you think that this could be done better or with different means - I would be glad to hear.

Hey @shaosss, thanks for contributing. I'll take a look into!


[TEST] Add autoscaling test

backport https://github.com/apache/camel-k/pull/3322

Release Note
NONE

@bouskaJ @squakez Heads up #3358 introduces some changes to the e2e tests. In particular the tests need to use unique operator ids when installing Camel K on the test namespaces. The same operator ids need to be used when running integrations.
Depending on what PR is merged 1st changes need to apply

Thanks @christophd - as this is a backport on a release branch, it should not be necessary

@squakez ah yes, just did a stupid copy & paste. thx

Failures are not related to this PR.


Namespace in module header

Problem
When looking at the module overview screen from the developer's perspective, it is unclear what cyclops means underneath the name of the module.

Solution
Add Namespace: in front of the namespace name -> “Namespace: cyclops”

I will like to take this


all: Treat 404 and some 403 as resource destroyed

Description

Allows the provider to treat some 404 and 403 API responses to set the
resource that is managed by it as "gone" where it makes sense.
Adds proper handling of the "403" status code when the traffic filter
rule has already been deleted on on the update_traffic_rules file.
It also adds some unit tests to assert this behavior.
Related Issues

Closes #193
Depends on elastic/cloud-sdk-go#258
How Has This Been Tested?

Manually in multiple ways and with unit tests.
Types of Changes

[x] Bug fix (non-breaking change which fixes an issue)

I have gone over the possible cases where a 403 might be thrown and what the implications will be, from the testing I've performed this are the possible scenarios as I see them. I haven't been able to get the API to throw me a 403 when acting as a public API user.
The 403 status code indicates that an authenticated user is not authorized to access a given resource. A full definition:

The HTTP 403 Forbidden client error status response code indicates that the server understood the request but refuses to authorize it.
This status is similar to 401, but in this case, re-authenticating will make no difference. The access is permanently forbidden and tied to the application logic, such as insufficient rights to a resource.

I'm really unsure when the API would return a 403 if it would at all.
Bear in mind that all testing has been performed against the currently deployed ESS version (MS-48).
Cases
Deployment is shut down, not deleted
When the deployment is "Terminated" in the UI or shut down through the API (same thing), the deployment can still be accessed through: GET /deployments/<id>, but the resources appear stopped. This will never trigger a 403 or 404, we simply process this in the provider and d.SetId("") and return early without an error.
Deployment is shut down and deleted
ECE
The API returns a 404, d.SetId("") and return early without an error.
ESS
I have never had the API return a 403 on a deployment that's created by the same user, due to the user's inability to delete a given deployment, thus we will always hit the first case described (Deployment is shut down, not deleted) in ESS.

Verbose log
$ ecctl --config ess deployment shutdown ef73c1f418162ddaa622d62b61024fbc -t
This action will delete the specified deployment ID and its associated sub-resources, do you want to continue? [y/n]: y
{
  "id": "ef73c1f418162ddaa622d62b61024fbc",
  "name": "my_example_deployment",
  "orphaned": {
    "apm": [],
    "appsearch": [],
    "elasticsearch": [
      {
        "dependents": [
          {
            "id": "dfda071940294497bb2ebf5233d33c33",
            "kind": "kibana"
          }
        ],
        "id": "8c15244ad39d46c6942f6a99793c2e8c"
      }
    ],
    "enterprise_search": [],
    "kibana": []
  }
}
Deployment [ef73c1f418162ddaa622d62b61024fbc] - [Elasticsearch][8c15244ad39d46c6942f6a99793c2e8c]: running step "perform-snapshot" (Plan duration 5.273251s)...
Deployment [ef73c1f418162ddaa622d62b61024fbc] - [Kibana][dfda071940294497bb2ebf5233d33c33]: running step "wait-until-stopped-ignore-allocator-status" (Plan duration 5.294255s)...
Deployment [ef73c1f418162ddaa622d62b61024fbc] - [Elasticsearch][8c15244ad39d46c6942f6a99793c2e8c]: running step "wait-until-stopped-ignore-allocator-status" (Plan duration 10.276262s)...
Deployment [ef73c1f418162ddaa622d62b61024fbc] - [Kibana][dfda071940294497bb2ebf5233d33c33]: running step "delete-instances" (Plan duration 10.297269s)...
Deployment [ef73c1f418162ddaa622d62b61024fbc] - [Elasticsearch][8c15244ad39d46c6942f6a99793c2e8c]: finished running all the plan steps (Total plan duration: 35.275891s)
Deployment [ef73c1f418162ddaa622d62b61024fbc] - [Kibana][dfda071940294497bb2ebf5233d33c33]: finished running all the plan steps (Total plan duration: 35.296894s)

$ terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

ec_deployment.example_minimal: Refreshing state... [id=ef73c1f418162ddaa622d62b61024fbc]

------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

$ ecctl --config ess deployment delete ef73c1f418162ddaa622d62b61024fbc --verbose
Using config file: /Users/marc/.ecctl/ess.yml
==================== Start of Request #0 ====================
DELETE /api/v1/deployments/ef73c1f418162ddaa622d62b61024fbc HTTP/1.1
Host: api.elastic-cloud.com
User-Agent: ecctl/v1.0.1
Accept: application/json
Content-Type: application/json
Accept-Encoding: gzip

====================  End of Request #0  ====================
==================== Start of Response #0 ====================
HTTP/1.1 404 Not Found
Content-Length: 67
Connection: keep-alive
Content-Type: application/json
Date: Thu, 03 Dec 2020 08:16:30 GMT
Server: fac/5c736b9
X-Request-Id: 946463ac66d4dc1992df083da540e57f

{"ok":false,"message":"The requested resource could not be found."}
====================  End of Response #0  ====================
[DELETE /deployments/{deployment_id}][404] deleteDeploymentNotFound  &{Errors:[]}

$ terraform plan

[Same result]

$ cat request.log
==================== Start of Request #1 ====================
GET /api/v1/deployments/ef73c1f418162ddaa622d62b61024fbc?convert_legacy_plans=false&enrich_with_template=true&show_metadata=true&show_plan_defaults=true&show_plan_history=false&show_plan_logs=false&show_plans=true&show_security=false&show_settings=true&show_system_alerts=5 HTTP/1.1
Host: api.elastic-cloud.com
User-Agent: elastic-terraform-provider/0.1.0-dev (cloud-sdk-go/2.8.0-ms48)
Accept: application/json
Authorization: [REDACTED]
Accept-Encoding: gzip

====================  End of Request #1  ====================
==================== Start of Response #1 ====================
HTTP/1.1 200 OK
Transfer-Encoding: chunked
Connection: keep-alive
Content-Type: application/json
Date: Thu, 03 Dec 2020 08:17:39 GMT
Server: fac/5c736b9
X-Cloud-Resource-Created: 2020-12-03T08:09:55.537Z
X-Cloud-Resource-Last-Modified: 2020-12-03T08:14:11.050Z
X-Cloud-Resource-Version: 7
X-Ratelimit-Interval: 1 second
X-Ratelimit-Limit: 50
X-Ratelimit-Remaining: 49
X-Ratelimit-Reset: Thu, 03 Dec 2020 08:17:39 GMT
X-Request-Id: 2cb0957d83221a21dd2821df6da8cfea

[...]

Conclusion
Seeing what we're seeing, I'm leaning towards removing the 403 case handling in the provider since users are unable to delete the deployments using the API, and in other types of installations ESSP or ECE they will get a 404 when the deployment truly can't be found.

I've opened #195 to fix the ec_deployments datasource

Thanks for the thorough reply @marclop :) I am in agreement with you that it's best to not check for 403s as there is a possibility that the users will be getting a 403 for an actual authorisation issue.
That said, you will get a 403 if the deployment has been completely deleted. I think @Kushmaro wanted to cover this case for disaster discovery. I would just like to double check we are all on the same page.
Regarding the traffic filter resource would there not be any implications of checking for a 403, given the possibility that the user might be hitting an actual authorisation error?

@karencfv @Kushmaro I've added the 403 status code to be treated again as deployment is gone.
Additionally, I've fixed a long failing integration test where the traffic filter rule is gone, a deployment potentially needs to be updated and the traffic rule was GET again, a 403 was clearly returned (see previously failing integration tests) and now that the 403 is handled, the test is passing (finally!).


Adding pip cache

Testing the cache with this run: https://github.com/CodeforHawaii/Hawaii-Zoning-Atlas/actions/runs/3682173173


'whenready' doesn't exist

Hello, I wanted to test electron but when I launch it I have an error:
D:\Users\USER0\Documents\NodeJS Projects\test\main.js:25
app.whenReady().then(createWindow)
    ^

TypeError: Cannot read property 'whenReady' of undefined
    at Object.<anonymous> (D:\Users\USER0\Documents\NodeJS Projects\radiocontroll\main.js:25:5)
?[90m    at Module._compile (internal/modules/cjs/loader.js:1158:30)?[39m
?[90m    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)?[39m
?[90m    at Module.load (internal/modules/cjs/loader.js:1002:32)?[39m
?[90m    at Function.Module._load (internal/modules/cjs/loader.js:901:14)?[39m
?[90m    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12)?[39m
?[90m    at internal/main/run_main_module.js:18:47?[39m

Code:
// Modules to control application life and create native browser window
const {app, BrowserWindow} = require('electron')
const path = require('path')

function createWindow () {
  // Create the browser window.
  const mainWindow = new BrowserWindow({
    width: 800,
    height: 600,
    webPreferences: {
      preload: path.join(__dirname, 'preload.js')
    }
  })

  // and load the index.html of the app.
  mainWindow.loadFile('index.html')

  // Open the DevTools.
  // mainWindow.webContents.openDevTools()
}

// This method will be called when Electron has finished
// initialization and is ready to create browser windows.
// Some APIs can only be used after this event occurs.
app.whenReady().then(createWindow)

// Quit when all windows are closed.
app.on('window-all-closed', function () {
  // On macOS it is common for applications and their menu bar
  // to stay active until the user quits explicitly with Cmd + Q
  if (process.platform !== 'darwin') app.quit()
})

app.on('activate', function () {
  // On macOS it's common to re-create a window in the app when the
  // dock icon is clicked and there are no other windows open.
  if (BrowserWindow.getAllWindows().length === 0) createWindow()
})

// In this file you can include the rest of your app's specific main process
// code. You can also put them in separate files and require them here.

my package.json
{
  "name": "electron-quick-start",
  "version": "1.0.0",
  "description": "A minimal Electron application",
  "main": "main.js",
  "scripts": {
    "start": "electron ."
  },
  "repository": "https://github.com/electron/electron-quick-start",
  "keywords": [
    "Electron",
    "quick",
    "start",
    "tutorial",
    "demo"
  ],
  "author": "GitHub",
  "license": "CC0-1.0",
  "devDependencies": {
    "electron": "^8.2.0"
  }
}

NodeJS version: v12.16.1
Thanks for help me.

try this:
const {app, BrowserWindow} = require('electron'); const path = require('path');
I think you are missing semi colons. It worked for me.

Did you run npm install && npm start, because I got the same error when only running npm start

@Maxsteel91Dev you need to run both npm install and npm start as stated above. it should work then.


Add give up button

Adds a give up button to return to the home screen during a run. Displays on both collapsed and expanded mode and requires confirmation from the user to prevent misclicks. #505

Nice! As an additional improvement (PR) on top of this, instead of just sending the user to the home screen, I think we can redirect them to the results page and still record their run. See marathon mode's give up button


feat(ci): Add docker windows test

Change Summary
Please summarise the changes this pull request is making here.
Checklist

[ ] Unit tests for the changes exist
[ ] Tests pass without significant drop in coverage
[ ] Documentation reflects changes where applicable
[ ] Test snapshots have been updated if applicable

Agreement
By submitting this pull request, I confirm that you can use, modify, copy and redistribute this contribution, under the terms of your choice.

@RobertCraigie feel free to add me as a reviewer in the future on Docker stuff. The duplication of the dockerfile here I think we might want to patch up in the future for easier maintenance (but not a big deal, Windows is admittedly always going to be a different beast so perhaps this split was inevitable)

@jacobdr Will do :)
Yeah I thought it best to keep it separate as I'm not that familiar with docker so running conditional commands or anything else that would be needed to make it work in the same Dockerfile didn't seem to be worth it to me, it also just might be worse to maintain.


Initialize Rust cache before installing binaries and additional components

I was hoping to reduce the time spent on binary installs, but unfortunately additional binaries are always reinstalled https://github.com/taiki-e/install-action/issues/577 — unfortunately that increases the cache size.
However, this does cache setup of the Rust toolchain which may save time. Since most of the Rust toolchain installation is just downloading components, and we still need to download the cache, there might not be much time saved here. The benefit is that the cache is generally closer to the runner on the network. Toolchain installation takes ~10s on Linux and >1m on Windows. It looks like there are some nice savings on Windows but it's less clear on Linux. The pre-commit job is 10s faster, but (perhaps due to the bug above) the test job is 8s slower.

@zanieb are you planning to work on this? I'd otherwise suggest that we close it or convert it into an issue.


Is there a way to install this on a HomeAssistant server running through windows

I have Home Assistant on a Windows machine-- is there a way to use this on windows?
Thank you!

https://www.youtube.com/watch?v=X27eVvuqwnY or https://home-assistant.io/getting-started/installation-docker/

I have Home Assistant installed on windows-- I was curious if I can run python-firetv through windows

Install python 2 for windows and should be fine

Really appreciate your replies...I'm having trouble getting past the first step  {swig libssl-dev python-dev libusb-1.0-0 } because I don't have access to apt-get on windows and pip isn't able to install whats needed

http://www.swig.org/Doc1.3/Windows.html
http://www.blogcompiler.com/2011/12/21/openssl-for-windows/
https://sourceforge.net/projects/tdm-gcc/files/Sources/Vanilla Sources/_Deprecated/python-dev/
https://github.com/libusb/libusb/wiki/Windows
And the faster route is https://forums.virtualbox.org/viewtopic.php?f=9&t=62452
And a Debain VM running home-assistant & the firetv server with a second VM running ZoneMinder are what I am using running on a windows7 box.

Thanks...I was trying to avoid VM, but looking at everything--it seems it will actually be easier. Thanks for your replies.


net-mgmt/zabbix-proxy: update template and chmod

With this PR the plugin can go stable. But please don't forget to chmod the setup.sh script.
You can decide if it's for 17.7.9 or 18.1 to fill the Changelog ;)

Release commit: https://github.com/opnsense/plugins/commit/8a84912b6


Back to latest alpine-fat image for Reverse Proxy

There was a version of "openresty/openresty:alpine-fat" (openresty/openresty:alpine-fat) that failed, see #68.
But it would be nice to check if this image version will work again in the future and return back to this version.

Issue https://github.com/com-pas/compas-architecture/issues/157 will be used to monitor the version, so no need to use latest, but can always use fixed version.


Mill compile error

using command "mill -i mill.scalalib.GenIdea/idea", it outputs the following error:
[info] compiling 1 Scala source to /Users/Test/test-mill/out/mill-build/compile.dest/classes ...
[error]  /Users/Test/test-mill/build.sc:25:23: not found: type Tests
[error]   object test extends Tests with ScalaTest {
[error]                       ^
[error] one error found
1 targets failed
compile Compilation failed

How to resolved it?

I solved this by downgrading the version of mill from 0.11.1 to 0.10.7.

@Sevenqi7 Thanks for you solution. Using the lower version can resolve this issue.

In mill 0.11, replacing Tests by ScalaTests solves it.
https://github.com/com-lihaoyi/mill/discussions/2462#discussioncomment-7478637


Removing zk role for windows hadoop/spark and setting the default siz…

…e to small in linux hadoop/spark case.

Can one of the admins verify this patch?

Hi @nemanja88, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (nemadj). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


Removed the POS


devicetracker googlemaps stop work in 0.97.0

device_tracker:

platform: google_maps
username<EMAIL_ADDRESS>password: password

Please fill out the issue template

You need to remove password from the config.
Documentation
The information is in the release notes.
0.97 Release Notes
Google Maps - Google Passwords are no longer required to be provided in your config. An external program is now required to obtain the necessary cookie file to place in your Home Assistant config directory. This is due to the authentication process being removed from the underlying package. Existing users should remove the password: entry from their config file (username is still required). The cookie file previously generated should still be valid and will allow the tracker to continue functioning normally until the cookie is invalidated. New users will need to follow the instructions on the Google Maps Location Sharing page to create their cookie file.(@shbatm - #25316) (google_maps docs)

Closing per above. Please report back if there's still some problem after correcting the config.

For something that used to work reliably to manually authenticating 3 times for 5 android devices over the last 5 days, usability is completely shot now.

@s2d4
come to the dark side -> WITH MEEEE


cmake: Split toolchain configuration into pre-and post-DT

Split up the toolchain configuration into two phases, generic and
target. The 'generic' phase configures the toolchain just enough to be
able to preprocess DT files. The 'target' phase completes the
configuration with target-specific configuration.

I would like to see this regression tested against all toolchains, but don't want to install all toolchains locally. Is this possible?

Codecov Report

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

@@           Coverage Diff           @@
##           master   #11810   +/-   ##
=======================================
  Coverage   48.29%   48.29%
=======================================
  Files         280      280
  Lines       43333    43333
  Branches    10375    10375
=======================================
  Hits        20929    20929
  Misses      18252    18252
  Partials     4152     4152

Continue to review full report at Codecov.

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

@SebastianBoe isn't the Zephyr SDK enough? That contains toolchains for all architectures

The xtools fails for x86 (added a comment about prefix changing).
-- @galak

Fixed.

The xtools fails for x86 (added a comment about prefix changing).
-- @galak

Fixed.

The xtools fails for x86 (added a comment about prefix changing).
-- @galak

Fixed.

@mped-oticon can you take a look at this.

BTW, this change breaks out-of-tree toolchains due to new expectations (fine with me), but should be clearly signalled.

we probably need a test for out-of-tree toolchains, no test, no guarantee a certain feature will continue to work, this is the sad reality and we need to improve this.

Temporarily closing the PR: https://github.com/zephyrproject-rtos/zephyr/pull/11810#discussion_r239772539

@mped-oticon are you happy with this now as-is?


Release requested attributes fix and dependency updates

Has been sitting in test for a long time, all looks well.

We actually have a script here that goes through creating a release in OWO from CLI  under the Creating a release version section https://australian-access-federation.slab.com/posts/aaf-development-workflow-d2fm1c97. If you need help with this I can step you through it

Ah yup, sure. Will hold for feedback.


react 16?

On github, it looks like v4.7.1 includes react & react-dom v16.0.0 as peerDependencies.
However, when I install latest from the npm registry, I get v4.7.2, published 7 months ago, with versions 14 and 15 of react and react-dom in the peerDependencies.

The latest version of react-tags is 4.7.3 now. Update me if this still occurs.

@mrdannael Hello. I have that error:
Component DropTarget(DragSource(Tag)) declared PropTypes instead of propTypes. Did you misspell the property assignment? when use react-tags.
just for notice

@Dictory I can't replicate the issue. Can you use jsfiddle or something similar to reproduce it?

@Dictory does the issue still occur ?  we have migrated to react 16 in latest version 4.9.1

@ad1992 sorry, now i doesn`t have error

awesome 👍 closing this issue


Close drivers on exit

This is a simpler version of https://github.com/docker/machine/pull/2635
It makes sure we don't have to call close everywhere we load a host.
Signed-off-by: David Gageot<EMAIL_ADDRESS>

LGTM

Did you running (including create) after building with -race?  Similar solutions in the past for me have tripped the race detector (due to the shared memory access), but this seems to happen all in a single goroutine so maybe it is fine.


issue of downloading resnet101 using ./misc/download_dataset.sh

Hello. I have an error with ./misc/download_dataset.sh. It says that the url for  https://drive.google.com/uc?id=0B1_fAEgxdnvJR1N3c1FYRGo1S1U is no longer accessible and the error says
"Cannot retrieve the public link of the file. You may need to change
the permission to 'Anyone with the link', or have had many accesses. "
Will there be a way to get around this error?
Thank you.

Hi @Credere1
I find I can download the file.


JAX vs TensorFlow perfomance

Can you share a notebook with time to accuracy comparison for both frameworks on TPU?

Thanks for the question! But that sounds out-of-scope for what we work on.

But we don't mind pointing you to things like table 1 of:
https://cloud.google.com/blog/products/ai-machine-learning/google-breaks-ai-performance-records-in-mlperf-with-worlds-fastest-training-supercomputer
So, suffice to say: you can get excellent performance out of JAX in the right circumstances. But performance is a very complicated question with many aspects, and one can't easily summarize it in a single notebook.

But we don't mind pointing you to things like table 1 of:
https://cloud.google.com/blog/products/ai-machine-learning/google-breaks-ai-performance-records-in-mlperf-with-worlds-fastest-training-supercomputer
So, suffice to say: you can get excellent performance out of JAX in the right circumstances. But performance is a very complicated question with many aspects, and one can't easily summarize it in a single notebook.

Thank you. I've already read this article. That's why I would like to know how you got these results.

The implementations are all public, see:
https://github.com/mlperf/training_results_v0.7/tree/master/Google/benchmarks
although those particular results were run on top of Google-internal infrastructure.
If you have specific questions, we can try to answer them.


Chat - No unread marker when messages are marked unread

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: v9.0.20-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:

Go to staging.new.expensify.com
Go to chat.
Send a few messages.
Mark any message as unread.

Expected Result:
There will be unread marker.
Actual Result:
There is no unread marker.
In self DM, when marking messages as unread, LHN report is not bolded.
Workaround:
Unknown
Platforms:

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

Screenshots/Videos
https://github.com/user-attachments/assets/5069cde6-c04f-49d0-b10d-ac6e004b692b

View all open jobs on GitHub

We think that this bug might be related to #vip-vsb

Proposal
Please re-state the problem that we are trying to solve in this issue.
There is no unread marker.
In self DM, when marking messages as unread, LHN report is not bolded.
What is the root cause of that problem?
We return early if the report action comes from the current user here. It comes from this PR
https://github.com/Expensify/App/blob/b7f7f1b4f36451b4e3a763ac717e1c8fd645ee5a/src/pages/home/report/ReportActionsList.tsx#L225-L228
In the past, we only checked this condition if messageManuallyMarkedUnread is undefined
What changes do you think we should make in order to solve the problem?
We should bring messageManuallyMarkedUnread back and update the condition to check the unread as we do in the past here
https://github.com/Expensify/App/blob/b7f7f1b4f36451b4e3a763ac717e1c8fd645ee5a/src/pages/home/report/ReportActionsList.tsx#L225-L228
What alternative solutions did you explore? (Optional)
NA

Reviewing shortly

I agree with @nkdengineer proposal. Let's bring
messageManuallyMarkedUnread back.
🎀 👀 🎀

Thanks, will raise a PR soon.

@hungvu193 The PR is here.

Thanks. I'll review it shortly

I think this issue is due for payment @kevinksullivan

@hungvu193 did we get the regression this caused fixed, though?

Looping in another BZ for your response as I am going OOO.

@hungvu193 did we get the regression this caused fixed, though?

I think it's fixed, I can seem to reproduce https://github.com/Expensify/App/issues/47481
https://github.com/user-attachments/assets/2413fd35-481a-4b53-9323-edc07b8d4885

little bump @lschurr for the payment summary 😄

@iwiznia are you able to weigh in here? Your comment indicates that the PR caused a regression, and that GH is still open: https://github.com/Expensify/App/issues/47481#top

Applause said:

Issue was found when executing this PR https://github.com/Expensify/App/pull/47393

If it was not that PR, what caused the regression?

@iwiznia The current RCA of https://github.com/Expensify/App/issues/47481 comes from https://github.com/Expensify/App/pull/45797 because we don't return early in shouldDisplayNewMarker if we already have a unread marker.

@lschurr Can you please post the payment summary here so we can close this one?

Payment summary:

Contributor: $250 @nkdengineer (paid in Upwork)
Reviewer: $250 @hungvu193 (please request in NewDot)

$250 approved for @hungvu193


Correctly handle table headers backline prepending

rustfmt is definitely my arch enemy...

Ok, updated so the check is better. :)
I also added the same for arrays.

Hm while this does technically work it's basically the same code. There's already a first field which should be handling this and I'm not sure why it's not working. I think it'd be best to investigate why that's not working as-is and see if there's a bug around its handling

The first field value is "correct" since we are in the first table. However, if we add a table inside another table, then maybe we should change this first value? Well, I can do it if you want like this.

@alexcrichton I can't find any easy solution to this problem. I might very well miss something obvious but if you try to change first value in SerializerSeq when initializing it, it has unwanted side effects. You also can't change the first value when running because it'd alter the parent too since it's a cell, something you don't want either. Therefore, all changes I tried didn't work and started to get bigger and bigger. This time, I think I reached the best possible change without side effects.
However, if you find a way to do it without changing half the code or having side effects, I'd be more than happy to have it!
PS: I updated the tests because one was useless and indent was weird sometimes...

Any news?

Anyone? I'd really like to have this merged and published so we can finally fix our issue in gtk-rs... :-/

Any news?

Sorry I don't have the time to invest in this (clearly!). I don't feel this is the right solution and I'm not comfortable merging this personally. I don't have the time though to help develop the right answer for this issue, but the general shape of it would have to do with tweaking the emission rather than after-the-fact trying to pop off newlines.

toml-rs has moved to https://github.com/toml-rs/toml_edit.  Feel free to rebase your PR against that repo and open a new issue there.


Multiple project windows

I would like to have multiple project windows so I can easily switch between projects/clusters/etc.. I would expect this to be in the system menus; "new monokle window", etc...

Need to consider how/if this affects state-mgmt in each window - especially if projects overlap.
Also - how handle settings


Support Specifying Registration Token Directly

Problem Statement
Currently, the project supports providing a Github Personal Access Token (PAT) and uses that token to call the Github API to request a Runner registration token. Using this method requires users to create and store a privileged (Admin scoped) token that has more permissions than it requires.
Requested Feature
Github now supports obtaining a scoped (Organization or Repository) registration token directly through the UI, which would eliminate the need for any kind of long-lived credentials to be stored. It would be great if we could specify the registration token rather than a PAT and the actions-runner-controller could just use the registration token directly rather than using the API to obtain one.
Additional Information
How to Obtain the Registration Token

Browse to https://github.com/organizations/{Org}/settings/actions/runners (Organization) or https://github.com/{Org}/{Repo}/settings/actions/runners (Repository)
Click the New Runner button (Organization) or New Self Hosted Runner button (Repository)
Copy the Github Runner token from the next screen. Note that this is the only time you will see this token. Note that if you exit the New {Self Hosted} Runner screen and then later return by clicking the New {Self Hosted} Runner button again, the registration token will be invalidated and a new token will be generated.

@mcalhoun Hey! You'd still need a PAT or App for other important API calls like made by ARC, like DeleteRunner, ListRunners, ListWorkflowJobs, etc. so this doesn’t much make sense.

Ahh...this actually makes sense since you are operating externally on the runners rather than calling the following within the runner itself:
./config.sh --unattended --url https://github.com/${github_org} --token $registration_token
./config.sh remove --unattended --token $registration_token

In the scenario above (calling register/deregister) within the container, it's possible to handle registration/deregistration without a PAT/Github App.
I'm wondering if the approach of the ARC could be altered to handle the registration and deregistration within the entrypoint script (by trapping SIGINT and SIGTERM) and therefore eliminating the need to call the Github APIs directly?
I'm not familiar enough with the internal workings to know if this is a possibility, but eliminating the need to have permanent credentials for the ARC would go a long way towards more of our customers adopting its use. Thanks!

calling the following within the runner itself:

@mcalhoun Hey! That is 50% correct. We do handle runner removal externally but for registration, we use vanilla config.sh.
Additionally, and you may already know, but when you use ephemeral runners, you don't need to explicitly remove the runner- it de-registers itself after the job run. So I'm still unsure how making it handle SIGTERM to de-register makes much difference.
I believe ARC's values reside in autoscaling and runner replicas management, which requires either PAT or GitHub App to call other GitHub Actions APIs. So just moving the de-registration process to a SIGTERM handler within the runner pod doesn't automatically remove the necessity of PAT and GitHub App as you originally wanted.
If you definitely don't need autoscaling or replicas management, that means you can just deploy your own runner pod by wrapping the upstream actions/runner into a container image, without ARC. I'm unsure how ARC can help that use-case 🤔
Maybe I'm missing something? Would you mind confirming?

Closing this as answered. But please feel free to reopen if I’m still missing something!

@Nuru The registration token eventually expires so it won't work in long run. Also, webhook delivery isn't guaranteed having an option to combine webhook-based autoscaling with metrics-based autoscaling might be useful for some folks(although not required).

@mumoshu I had heard that the token lasted longer, but now I found official documentation that says the token generated on the web page is only valid for 1 hour, so you are right, it is not a solution. Thank you for the explanation.

@Nuru Thanks for confirming! Let's ask GitHub to add more granular permission for that so that we no longer need admin access.


feat: [IDP]: Added the info on support for all step and stage variables in the Workflows Action to Trigger Harness Pipeline

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://673211607db181226cd6e281--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6732e890e1a0364a1726254b--harness-developer.netlify.app


Refactor the generated API to call common functions

Updated code gen logic: generate calls into the generic create/remove/get/set funcs in Translator class
Regenerate code in dataplane/standalone/sai/**
Create generic create/remove/get/set method in Translator class that for all all sai object types (unimplemented for now)
replace custom logger with  glog
I will rewrite switch.cc  and implement the translator methods in a followup PR

Thanks, can you give a brief overview of the parts of the change that's harder to understand so it's quicker for me to review? Without context I really don't know what is the logic behind the changes and I often find myself reading everything just to understand what it's doing first, which takes much longer than if there were context available beforehand so I know what I'm looking for while reviewing.

updated desc