[WIP] Add firewall service

Which issue(s) this PR fixes:

Fixes #422
Additional comments:

This PR is a follow up on PR #452
Work in progress: the firewall rules are only implemented for HDFS DataNode. The goal of this PR for now is to get feedback on the implementation.
The implementation proposed here inherits the concepts of firewalld: zones and services. A service corresponds to a list of ports (+protocols) and a zone corresponds to a list of sources (~= IPs) and the rules that apply to them when accessing services on the host.
Possible negative impacts
Deploying erroneous firewall rules on hosts can have disastrous consequences, notably forbidding node operators to connect via SSH. I suggest that we implement a check that determines if Ansible will still be able to connect after the firewall rules deployment and if not abort it (see #480).
firewall role
A new firewall role is added to TDP. This role will always have to be run prior to services deployment. The role has been written to support multiple firewall services as a backend. For now only firewalld is supported. One can change which firewall service is used with firewall_service and the routing logic is managed in firewall.generic.
roles/firewall
├── firewalld
│   ├── handlers
│   ├── tasks
│   └── templates
└── generic
    └── tasks

Cluster level firewall
firewall_tdp_managed controls if TDP should generate firewall rules on the cluster nodes:

If yes, TDP ensures that all rules defined in firewall_rules are created on the right hosts and that firewalld is started.
If no, TDP ensures that all previously generated firewall rules are deleted.

https://github.com/TOSIT-IO/tdp-collection/blob/14809dd1a1c8c91778bf5ebe99b60a7daa0649fb/tdp_vars_defaults/firewall/firewall.yml#L5-L10
Firewall zones
By default, TDP will create 2 zones:

public: This zone corresponds to all the hosts outside of the TDP cluster that need access to its client endpoints (e.g. HDFS Web UI, Hive JDBC/ODBC).
internal: This zone corresponds to all the TDP cluster hosts. Internal ports need to be opened inside the cluster.

https://github.com/TOSIT-IO/tdp-collection/blob/14809dd1a1c8c91778bf5ebe99b60a7daa0649fb/tdp_vars_defaults/firewall/firewall.yml#L16-L26
Each zone has 4 properties:

name: A name for the zone
short: A short description of the rule that will be used in the firewalld zone definition
groups: The Ansible groups that are part of this zone. TDP will take care of mapping these groups to firewalld ipsets.
addresses: The other addresses that are part of this zone. Can be in the format address or address/mask.

Firewall rules
All open port rules are listed in the firewall_rules variable, with one list for each component. E.g. for hdfs_dn (HDFS DataNode):
https://github.com/TOSIT-IO/tdp-collection/blob/14809dd1a1c8c91778bf5ebe99b60a7daa0649fb/tdp_vars_defaults/firewall/firewall.yml#L40-L48
Each rule has 5 properties:

short: A short description of the rule that will be used in the firewalld service definition
port: The port to open and secure
protocol: The protocol authorized on this port
zones: The zones from which the port will be accessible.
state: present or absent. If absent, TDP will make sure that the port is removed from all rules.

Trying this out
If you want to try this on a TDP cluster, run playbooks/meta/firewall.yml. This will deploy firewall rules on hdfs_dn hosts and start firewalld. Note that other services installed on the same hosts (e.g. YARN RM) will stop functioning as no firewall rules will exist for them.
Low level implementation
TDP uses firewalld ipsets, services, and zones to set firewall rules (all generated files are prefixed with firewalld_files_prefix):

Firewalld ipsets: each Ansible group that is used in firewall_zones will be mapped to an ipset in /etc/firewalld/ipsets. E.g. /etc/firewalld/ipsets/tdp_tdp_cluster.xml:
<?xml version="1.0" encoding="utf-8"?>
<ipset type="hash:net">
  <short>tdp_cluster Ansible group</short>
  <entry><IP_ADDRESS></entry>
  ...
  <entry><IP_ADDRESS></entry>
</ipset>

Firewalld services: each TDP component has 1 service (in /etc/firewalld/services) for each of its firewalld_rules. A service contains the port number and protocol. E.g. /etc/firewalld/services/tdp_hdfs_dn_data_port.xml:
<?xml version="1.0" encoding="utf-8"?>
<service>
  <short>HDFS DataNode data transfer port</short>
  <port protocol="tcp" port="9866" />
</service>

Firewalld zones: Each zone in firewall_zones has 1 zone in /etc/firewalld/zones that defines the sources allowed to the zone's services. E.g. /etc/firewalld/zones/tdp_internal.xml:
<?xml version='1.0' encoding='UTF-8'?>
<zone>
  <short>TDP cluster internal zone</short>
  <source ipset="tdp_tdp_cluster"/>
  <service name="tdp_hdfs_dn_data_port"/>
  <service name="tdp_hdfs_dn_ipc_port"/>
  ...
</zone>

License agreement
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004 and that you give permission to TOSIT,
you have to acknowledge this by using the following check-box.

[x] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

[x] I hereby agree to grant TOSIT a copyright license to use my contributions.

I just noticed that the role does not work in Ansible 2.9 because https://github.com/ansible/ansible/pull/64959 has been fixed in Ansible 2.10.
I am looking for a workaround.

I just noticed that the role does not work in Ansible 2.9 because ansible/ansible#64959 has been fixed in Ansible 2.10.
I am looking for a workaround.

[x] Done

To do:

[ ] Remove firewall rules using the entire file names instead of {{ firewalld_files_prefix }}*.xml to avoid deleting files generated by the client

Rebased on master

As discussed previously, I will create several PRs for this branch to add firewall rules in small batches.


add PLTN

What is missing to move forward
@JeremyParish69

Pending addition of LISTING.md

Apologies for the delay, @PLTNDeploy, we've been working to finalize listing requirements.
Note that tokens can no longer be listed by new GitHub accounts. Is there a more credible GitHub user with a verifiable history that can vouch for this token?

Closing for now, can reopen


⚠ Bofrost.fr has degraded performance

In eb97fe5, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1839 ms

Resolved: Bofrost.fr performance has improved in d1e628a.


[ICON New]>Can we add the Conreq Icon?

Description
Hi man, can you add this icon?
https://styles.redditmedia.com/t5_2tgms/styles/communityIcon_tx03a4b0qbg81.png

Please tick the boxes

[X] You've read the docs
[X] You've checked for duplicate issues

@IIIdefconIII you can add this yourself using https://homarr.dev/docs/advanced/customizations/icons#using-your-icons
We don't add icons ourself for users. We only have icon repositories 😉

True True, i figured that out, just would be nice to have it included so future users wont have to ask the same queqstion.

EDIT: onyl figuring out why the plex pinmg status is in red while its up. nbut that another thiung, probable get it fixed this week if invest more time in Homarr

you just need to add the 401 or 403 code to the network tab. It's normal since pings don't use credentials.


I'm not sure what this error is, any idea?

The application was not opening for me so I tried the cmd method but I only got this error message. Any idea on how to fix this so I can use the sniffer? I did download all the things that were listed and have tried downloading npcap 1.60 instead of 1.70

Sorry about this I forgot one of the fixes that I could have tried.


bug:  Cannot set the NEXTAUTH_SECRET Environment Variable

Provide environment information
System:
OS: Linux 5.10 Ubuntu 20.04.5 LTS (Focal Fossa)
CPU: (8) x64 Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Memory: 20.61 GB / 25.00 GB
Container: Yes
Shell: 5.8 - /usr/bin/zsh
Binaries:
Node: 16.16.0 - ~/.asdf/installs/nodejs/16.16.0/bin/node
Yarn: 1.22.15 - ~/.asdf/installs/nodejs/16.16.0/bin/yarn
npm: 8.15.1 - ~/.asdf/plugins/nodejs/shims/npm
Describe the bug
I cannot set the environment variable NEXTAUTH_SECRET. However, I can set any other environment variable.
To reproduce
I just created a brand new project didn't install anything new. So i don't know if it is even reproducible or is it just a problem with my pc which I don't think it is because I can set any other environment variable just not `NEXTAUTH_SECRET'
Additional information
No response

What error do you try to get when you try and set the variable?

what is the ct3a version in package.json? and could you maybe post a minimal reproduction?

Why you want to set  ?
If you are useing NextAuth Library , I think you don't need that for auth .
https://next-auth.js.org/configuration/options#secret

Closing due to lack of reproduction. Feel free to reopen if you can provide more details.


[BUG] Negative test case got stuck in waiting for longhorn-ui pods

Describe the bug
Negative test case got stuck in waiting for longhorn-ui pods:
Waiting for longhorn-ui pods ['longhorn-ui-594c5488d4-lfkd6', 'longhorn-ui-594c5488d4-dntj4'] running, retry (108648) ...
Waiting for longhorn-ui pods ['longhorn-ui-594c5488d4-lfkd6', 'longhorn-ui-594c5488d4-dntj4'] running, retry (108649) ...
Waiting for longhorn-ui pods ['longhorn-ui-594c5488d4-lfkd6', 'longhorn-ui-594c5488d4-dntj4'] running, retry (108650) ...
Waiting for longhorn-ui pods ['longhorn-ui-594c5488d4-lfkd6', 'longhorn-ui-594c5488d4-dntj4'] running, retry (108651) ...
Waiting for longhorn-ui pods ['longhorn-ui-594c5488d4-lfkd6', 'longhorn-ui-594c5488d4-dntj4'] running, retry (108652) ...

# kubectl get pods -n long
horn-system
NAME                                                     READY   STATUS    RESTARTS       AGE
engine-image-ei-b907910b-6dkzp                           1/1     Running   11 (34h ago)   41h
csi-resizer-694f8f5f64-k8ltv                             1/1     Running   1 (34h ago)    34h
csi-attacher-5c4bfdcf59-cpzms                            1/1     Running   1 (34h ago)    34h
csi-snapshotter-959b69d4b-btcjj                          1/1     Running   1 (34h ago)    34h
csi-snapshotter-959b69d4b-dsx58                          1/1     Running   1 (34h ago)    34h
csi-provisioner-667796df57-gkpkl                         1/1     Running   1 (34h ago)    34h
csi-provisioner-667796df57-fn8cz                         1/1     Running   1 (34h ago)    34h
csi-attacher-5c4bfdcf59-kzpcn                            1/1     Running   1 (34h ago)    34h
csi-resizer-694f8f5f64-znr88                             1/1     Running   1 (34h ago)    34h
longhorn-manager-w2hz9                                   1/1     Running   26 (34h ago)   42h
engine-image-ei-b907910b-sl4tm                           1/1     Running   11 (34h ago)   41h
instance-manager-75da4986282239c5db5fdf6aef015a16        1/1     Running   0              34h
longhorn-csi-plugin-rbt5z                                3/3     Running   96 (34h ago)   41h
longhorn-csi-plugin-47dkr                                3/3     Running   89 (34h ago)   41h
longhorn-ui-594c5488d4-j854k                             0/1     Error     2              34h
longhorn-ui-594c5488d4-lfkd6                             1/1     Running   0              34h
csi-resizer-694f8f5f64-vm95f                             1/1     Running   0              34h
csi-snapshotter-959b69d4b-lz6lg                          1/1     Running   0              34h
csi-attacher-5c4bfdcf59-72whn                            1/1     Running   0              34h
csi-provisioner-667796df57-6hpjt                         1/1     Running   0              34h
longhorn-ui-594c5488d4-dntj4                             1/1     Running   0              34h
longhorn-driver-deployer-5cb967fdc9-mhdk9                1/1     Running   0              34h
longhorn-csi-plugin-528n4                                3/3     Running   33 (34h ago)   41h
longhorn-manager-hp5h2                                   1/1     Running   11 (34h ago)   42h
engine-image-ei-b907910b-lr6hd                           1/1     Running   11 (34h ago)   41h
instance-manager-0d7bcfc59f302c74c139e58e9e6c1fa1        1/1     Running   0              34h
longhorn-manager-kzbmr                                   1/1     Running   0              34h
instance-manager-893977a16bdc9882b64fedde3e27757e        1/1     Running   0              34h
share-manager-pvc-42c06475-5c03-49ef-9f47-93f6399304c6   1/1     Running   0              34h
share-manager-pvc-20ce7994-b962-4a8c-9bfc-5f0d22a174fe   1/1     Running   0              34h

/src/longhorn-tests/test_framework/terraform/aws/sles # kubectl logs longhorn-ui-594c5488d4-j854k -n longhorn-
system
unable to retrieve container logs for containerd://ac5c9b38b5c387d8a55c41ccac58bcdbbdc90491a8c97d30504b150d08ad84b7

/src/longhorn-tests/test_framework/terraform/aws/sles # kubectl describe pod longhorn-ui-594c5488d4-j854k -n longhorn-system
Name:                 longhorn-ui-594c5488d4-j854k
Namespace:            longhorn-system
Priority:<PHONE_NUMBER>
Priority Class Name:  longhorn-critical
Node:                 ip-10-0-2-198/<IP_ADDRESS>
Start Time:           Sat, 23 Mar 2024 13:55:11 +0000
Labels:               app=longhorn-ui
                      app.kubernetes.io/instance=longhorn
                      app.kubernetes.io/name=longhorn
                      app.kubernetes.io/version=v1.6.0-dev
                      pod-template-hash=594c5488d4
Annotations:          <none>
Status:               Failed
Reason:               Evicted
Message:              The node was low on resource: ephemeral-storage. Threshold quantity:<PHONE_NUMBER>, available: 5135032Ki. Container longhorn-ui was using 4Ki, request is 0, has larger consumption of ephemeral-storage.
IP:                   <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/longhorn-ui-594c5488d4
Containers:
  longhorn-ui:
    Container ID:   containerd://ac5c9b38b5c387d8a55c41ccac58bcdbbdc90491a8c97d30504b150d08ad84b7
    Image:          longhornio/longhorn-ui:master-head
    Image ID:       docker.io/longhornio/longhorn-ui@sha256:09e1054e5e96aaefd84224303e1c2a367ff290a80b9ba83c707ab7a4a06c19c6
    Port:           8000/TCP
    Host Port:      0/TCP
    State:          Terminated
      Reason:       Error
      Exit Code:    137
      Started:      Sat, 23 Mar 2024 13:55:29 +0000
      Finished:     Sat, 23 Mar 2024 13:59:48 +0000
    Ready:          False
    Restart Count:  2
    Environment:
      LONGHORN_MANAGER_IP:  http://longhorn-backend:9500
      LONGHORN_UI_PORT:     8000
    Mounts:
      /var/cache/nginx/ from nginx-cache (rw)
      /var/config/nginx/ from nginx-config (rw)
      /var/run/ from var-run (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-9dcjd (ro)
Conditions:
  Type               Status
  DisruptionTarget   True
  Initialized        True
  Ready              False
  ContainersReady    False
  PodScheduled       True
Volumes:
  nginx-cache:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  nginx-config:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  var-run:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  kube-api-access-9dcjd:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:                      <none>

https://ci.longhorn.io/job/private/job/longhorn-e2e-test/484/
To Reproduce
-t \"Power Off Node One By Once For More Than Pod Eviction Timeout While Workload Heavy Writing\" -v LATENCY_IN_MS:0 -v LOOP_COUNT:30 -v RETRY_COUNT:259200

Expected behavior

Support bundle for troubleshooting
supportbundle_985c5335-c8f8-4009-9772-5e711685fd7f_2024-03-25T00-33-17Z.zip
Environment

Longhorn version: master-head
Impacted volume (PV):
Installation method (e.g. Rancher Catalog App/Helm/Kubectl):
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:

Number of control plane nodes in the cluster:
Number of worker nodes in the cluster:

Node config

OS type and version:
Kernel version:
CPU per node:
Memory per node:
Disk type (e.g. SSD/NVMe/HDD):
Network bandwidth between the nodes (Gbps):

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Number of Longhorn volumes in the cluster:

Additional context
Probably checking all longhorn components is not required. The original implementation is good enough.

@c3y1huang Could you help check this? Thank you!

@c3y1huang Could you help check this? Thank you!

@c3y1huang Let's try to handle the issue in v1.8.0. We can put it off to v1.9 if you have any concerns. Thank you.


Add xsp testing on ci

no way...this software is evil

there was a way, but it is completely not useful as we need some sort of headless browser testing


Improve the Clojure Package README to Make it Easier to Get Started

Description
Improve the README in response to feedback from https://github.com/apache/incubator-mxnet/issues/12839
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[X] Changes are complete (i.e. I finished coding on this PR)
[X] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

@gigasquid Thanks for improving the document. :)
@aaronmarkham Can you take a look?
@mxnet-label-bot [pr-awaiting-review]

@daveliepmann @ChaiBapchya thanks so much for the review. I'll get to work on implementing the feedback shortly 😸

Feedback has been implemented. @ChaiBapchya, if you have time for second pass, please take a look 😸

An update on this - There is some collaboration going on in a PR in the originating repo https://github.com/gigasquid/incubator-mxnet/pull/2

@gigasquid Could you please look into comments given by @aaronmarkham
Also, could you make sure that CI is passing for your changes.

@ankkhedia @aaronmarkham Note that https://github.com/gigasquid/incubator-mxnet/pull/2 addresses a bunch of these remarks, along with other things, so it might be good to wait until that has been merged/rebased in.

so it might be good to wait until that has been merged/rebased in

Now's the time 😉

@aaronmarkham @ChaiBapchya @daveliepmann Could you please give a second pass to make sure your concerns has been addressed.

Just now I made a small PR to @gigasquid's branch that would satisfy my suggestion to add section links from the 3 install options to their instructions. But this is a minor nitpick—all my concerns have been addressed. Many thanks to Carin for shepherding this through.

Thanks @daveliepmann and @kohr-h for all your work 😸
Thanks @aaronmarkham for your feedback. I'll take a pass through it later and make sure all your items are addressed with the latest revision.

Thanks again @ChaiBapchya - I'll take a look to make sure your feedback is addressed with the latest merged revisions as well.

Thanks @daveliepmann and @kohr-h for all your work smile_cat

My pleasure!
I'll have a go at the instructions tonight and check if they actually work :wink: or if there are assumptions about the environment.

BTW, the test fail is a timeout by Travis (cap at about 50 minutes per build as it seems).

Hi @kohr-h Travis build failure is not a blocker for PR merge as of now. It is for informational purpose only.

Thanks @aaronmarkham - All your feedback has now been incorporated :)

I wrote up some more changes yesterday and wanted to file a follow-up PR after testing the instructions, but the very slow download of MKL from Intel's servers stopped me :snail:
I'm gonna push it tonight.

After solving an issue with the Scala package build with MKL-DNN (see #13096) I can now confirm that the instructions for building everything from source work as advertised.
That said, I'm curious what this message means when I run lein test:
INFO  MXNetJVM: Try loading mxnet-scala from native path.
INFO  MXNetJVM: Try loading mxnet-scala-linux-x86_64-gpu from native path.
INFO  MXNetJVM: Try loading mxnet-scala-linux-x86_64-cpu from native path.
WARN  MXNetJVM: MXNet Scala native library not found in path. Copying native library from the archive. Consider installing the library somewhere in the path (for Windows: PATH, for Linux: LD_LIBRARY_PATH), or specifying by Java cmd option -Djava.library.path=[lib path].
INFO  org.apache.mxnet.util.NativeLibraryLoader: Loading libmxnet-scala.so from /lib/native/ copying to mxnet-scala

Does that mean that it uses the Scala package from my local Maven repository? How can I find out what package is loaded?

@kohr-h Thanks for digging in and solving the Scala build issue with MKL-DNN.
The message you are seeing Loading libmxnet-scala.so from /lib/native/ copying to mxnet-scala means that the native library is being extracted out of the jar, copies it to a temp file, and then loads it into memory from there https://github.com/apache/incubator-mxnet/blob/master/scala-package/core/src/main/scala/org/apache/mxnet/util/NativeLibraryLoader.scala#L92
From my point of view, this seems like a desirable thing. I'm wondering what other Scala people think? Is the message still appropriate for users? @nswamy @lanking520

Thanks for clearing up the origin of the message @gigasquid. I assumed something like that, but warnings are always a bit unsettling, in particular when they don't exactly say what's going on. Here, for instance, it would be a much more comforting if the message also mentioned the jar explicitly, so that one could see it's the jar that's just been built manually.

I think this is ready to merge. Thanks everyone for their hard work in improving the documentation and making it easier for users to get started 💯
@kohr @nswamy @lanking520 I'll move the concerns about the message Loading libmxnet-scala.so from /lib/native/ copying to mxnet-scala out to another issue so we can continue the conversation.

The related issue created https://github.com/apache/incubator-mxnet/issues/13108


Enhance NgpSelect Component to Match the Dropdown Menu UI from Headless UI

Feature Type
Enhancement
Feature Description
The current NgpSelect component provides basic functionality, but the UI for the options within the select tag is not visually appealing or modern. I propose enhancing the component's design to mirror the Dropdown Menu from the Headless UI library. This will involve implementing a more polished and user-friendly dropdown interface, including improved styles, animations, and interactions.
Angular Primitives

HeadlessUI

Thank you for offering to contribute! Following our discussion on Discord, we will retain the ngpSelect primitive as is, as there are use cases for enhancing the native select.
We would like to support completely custom selects, and we will do this with a new set of primitives, 'ngpListbox'.
I did start this quite a while back but discontinued it in favour of other primitives with the intent to have this feature at some point. The code can be found here https://github.com/ng-primitives/ng-primitives/tree/2eeaf18c7b15eb82a7c4e14dabc6d252f369f9ec/packages/ng-primitives/select/src which should serve as a good reference however we would rename select to listbox.
I suspect much of the API can be the similar and you can draw inspiration from.
One thing I never got round to was supporting the dropdown being placed at the document level, rather than inline which is a potential use case. I was thinking we could add a structural directive for this, something like '*ngpListboxPortal' that could be added to the dropdown to support this. I'm open to suggestions with the name. This could potentially be added at a later point so not necessarily needed at this point.

Regarding the structural directive for placing the dropdown at the document level, I think it would be better if we named it ngpDropdownContainer.
What do you think?

If you suspect it can be used across multiple primitives in future then that seems like a good name, for example, we will have combobox and menus etc in future, all will need similar functionality where they may be hoisted to the document level, if this directive could be used in one or more of these cases, this would be great! If it's is something that is specific to listbox the I would have listbox in the name.
We are pre-1.0 so we do have the flexibility to rename in future if needed 😊

From my previous experience we could have a *ngpPortalContainer structural
directive as it can be later attached to dropdowns, menus, popovers or
anything really and we can have the feature related content separated.
I'm not that familiar with hostDirectives but if that feature allows it we
can re-export this structural directive to have the basic functionality
(managing the layout, position and layers) and we can add feature specific
things like keyboard navigation, interaction on top of it.
One of the hardest part of developing a library is naming things :D
And returning to the original topic, a listbox component, can be a
composition of other features like, button, popover, input (for filtering
results) and angular/cdk's ListKeyManager.
On Sat, Aug 3, 2024, 15:56 Ashley Hunter @.***> wrote:

If you suspect it can be used across multiple primitives in future then
that seems like a good name, for example, we will have combobox and menus
etc in future, all will need similar functionality where they may be
hoisted to the document level, if this directive could be used in one or
more of these cases, this would be great! If it's is something that is
specific to listbox the I would have listbox in the name.
We are pre-1.0 so we do have the flexibility to rename in future if needed
😊
—
Reply to this email directly, view it on GitHub
https://github.com/ng-primitives/ng-primitives/issues/24#issuecomment-2266719810,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPCPYFQBPL56WXMUC54O5DZPTOP5AVCNFSM6AAAAABL5YPVQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRWG4YTSOBRGA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

From my previous experience we could have a *ngpPortalContainer structural
directive as it can be later attached to dropdowns, menus, popovers or
anything really and we can have the feature related content separated.

yes, having thought a little bit about this I think having a dedicated portal primitive might be a good idea here. I guess we can leave this feature now for select and come back to it.

I'm not that familiar with hostDirectives but if that feature allows it we
can re-export this structural directive to have the basic functionality
(managing the layout, position and layers) and we can add feature specific
things like keyboard navigation, interaction on top of it.

Yes so we have directives for roving focus which can handle a lot of keyboard navigation etc via host directives.
I suspect it will be something like this:
...
This directive would handle keyboard navigation etc.
Then to make it appear at the document level you could apply the portal directive
...
Something like that

One of the hardest part of developing a library is naming things :D

ha, it certainly is!!

And returning to the original topic, a listbox component, can be a
composition of other features like, button, popover, input (for filtering
results) and angular/cdk's ListKeyManager.

yes, the select button could use the ngpButton as a host directive to add that functionality, and it would just enhance it will functionality to launch the dropdown on click. We have the roving focus directives for keyboard navigation so they can also be used as host directives to add that functionality to dropdown and dropdown options etc.. so absolutely, we can leverage a lot of existing functionality 😊

popover, input (for filtering results) and angular/cdk's ListKeyManager.

Just noticed you mention popover, yes that could be a good candidate for the dropdown menu, perhaps the following would work fine:
<div *ngpPopover ngpListboxDropdown>...</div>

I have a ticket open for popover I guess that is perhaps something either I or someone should work on soon so we can incorporate it. Good suggestion


tlog slave syncer : improvement

Slave syncer feature is still in very initial stage, some improvement needed:

[ ] report to 0-orch  in case of failed replay. We might not need this because storage API already do this.
[ ] improve performance of  slave syncer's replay callback. It currently being executed per sequence. We can at least defer the flush() here.
[ ] it currently always use tlog player to write to slave, it seems we can also use storage API directly. Although we still need to use tlog player.
some point mentioned #576
some points mentioneded at #475

[need to think more about it]

blocked by #596


Profile of Gama Richard William

Name
Gama Richard William
Profile Image

Country
South Sudan
Region
Pagirinya Refugee Settlement
Organisation
No response
Languages
English(Very Good), Ma'di Language(Very Good), Local Arabic(Basics)
Skill 1
Web & Software
Qualifications for Skill 1

Bachelor's Degree in Software Engineering and Application Development

Created Musics Website reached at www.g2gmusics.com

Skill 2
Data Analysis
Qualifications for Skill 2
No response
Skill 3
Open Source & Knowledge
Qualifications for Skill 3
Undergone through the ASKnet Track 2 Program for focusing on Open Source Documentation Software (Github)
Skill 4
No response
Qualifications for Skill 4
No response
describe yourself
Talented Software Engineer with experience (2+ years) in delivering innovative technological solutions on various platforms including salesforce to support Organizations.
Goal-Oriented individual with great skills and understanding of Databases management tools & various programming and scripting languages (HTML, CSS, JavaScript, python and Apex). Additionally, I have freelanced with many agencies to build web applications that meet the standards for web design, user experience, best practices, usability and speed. My overall passion lies in responding to challenges by designing and building Web solutions aligned to the user's needs. Translating requirements into code and working across many different APIs, third-party integrations and databases.
E-Mail
<EMAIL_ADDRESS>Phone
+256785547653
WhatsApp
+256785547653
Website
No response
Telegram
@GamaRich
GitHub
https://github.com/PyGamma
LinkedIn
https://www.linkedin.com/in/gama-richard-75193317a/
Twitter
No response
Facebook
Gama Richard( Prosper Gammarays)
Instagram
No response
Mastodon
No response
WikiFab
No response
Other
No response

for time being am putting the profile on archive as we wait for @PyGamma to give us a green light on what to do there after.


[stable/prometheus-adapter] External metrics issue

Describe the bug
When using the chart to deploy the adapter to use with HPA after leaving the default values, in this case rules.default: true which implies that the external metrics list is empty (im not trying to use external metrics) the charts still deploys the APIService named external.metrics.k8s.io/v1beta1 causig me to have error: unable to retrieve the complete list of server APIs: external.metrics.k8s.io/v1beta1: the server could not find the requested resource  when calling kubectl api-resource (and other operations, ambassador wont deploy because of this missing api group
Version of Helm and Kubernetes:
kubectl:
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"archive", BuildDate:"2019-03-29T11:10:21Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.7-gke.10", GitCommit:"8d9b8641e72cf7c96efa61421e87f96387242ba1", GitTreeState:"clean", BuildDate:"2019-04-12T22:59:24Z", GoVersion:"go1.10.8b4", Compiler:"gc", Platform:"linux/amd64"}
helm:
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Which chart:
stable/prometheus-adapter
What happened:
Chart deploys a apiservice external.metrics and that api is unreachable causing different issues within the clusters
What you expected to happen:
Not to have that apiservice (perhaps if .Values.external == true)
How to reproduce it (as minimally and precisely as possible):
Install stable/prometheus-adapter and try to run ambassador via chart

I can confirm this issue. Tested with the image prometheus-adapter:v0.5.0. When I try to request GET /apis/external.metrics.k8s.io/v1beta1 on the pod directly I get the following result:
< HTTP/2 404
< content-type: application/json
< content-length: 179
< date: Wed, 22 May 2019 14:10:07 GMT
<
{
  "paths": [
    "/apis",
    "/apis/custom.metrics.k8s.io",
    "/apis/custom.metrics.k8s.io/v1beta1",
    "/healthz",
    "/healthz/ping",
    "/metrics",
    "/version"
  ]

So it seems that /apis/external.metrics.k8s.io/v1beta1 path is not available.

I posted a fix in #14389. I tested locally and cannot reproduce the issue after applying the fix.

Confirmed fix in 1.0.3


ARM: Core Stack Improvements/Bug fixes for 2.4 release

ARM Architecture related issues tentatively scheduled for v2.4 release
New features

[X] [Cortex-M] Support for Cortex-M1
[X] [Cortex-M] timing functionality based on DWT

Feature Enhancements

[x] [Enh. ARM Cortex-M] Add ARM Cortex-M test for IRQ target state management (#22133)
[x] [Enh. ARMv8-m] Make built-in stack overflow a default feature (=y)
[x] [Enh. ARCHitectures, Kernel] Support distinct ways for allocating stack areas for default and supervisor-only threads (#13637, #24714)
[x] [ARM] Make threads use K_THREAD_STACK_SIZEOF and remove workaround for ARM 's z_new_thread() (#14269, #24714)
[x] [Enh. Cortex-M] Clean-up and enhance SW vector relaying for Baseline Cortex-M (#26289)
[x] [Enh. Cortex-M] Extend SW vector relaying for Mainline Cortex-M (#26276)
[x] [Enh. Cortex-M] Include full register state in ARM Cortex M Exception Stack Frame  (#27495)
[x] [Enh Cortex-M] Lock scheduler while doing secure calls.

Bug Fixes

[x] [Bug ARM Cortex-M] Stack randomization for main thread (#23702)
[x] [Bug ARM Cortex-M] Vector Tables are not aligned properly in the linker (#26800)
[x] [Bug ARM Cortex-A,R,M] Vector Tables and Relay Vector table symbols are exported as GTEXT (#27039)
[x] [Bug QEMU] Fix timer driver on QEMU Cortex-M0 and restore test coverage (#26189)
[x] [Bug Cortex-M] Fix Cortex-M Boot with CONFIG_MULTITHREADING=n

Open items moved to #28729


Plans displaying agreement holders that were current (status A or B) but have since becomes “former” (P or C)

Approved/stands status plans should be snap show in time showing names of agreement holders in place at time of approval.
Plans in any other status (all the working statuses) should be updated to show only the current active (A/B) agreement holders
Questions for the future:

if an agreement is approved and a change happens to agreement holders should that be trapped somehow, a new copy of the plan be made indicating that client change requires RUP update? Notifications?

@micheal-w-wells Is this one done? I think so... If so, we can close.


Decide design

Ok, as the objective of this version is just to have a working version, no specific graphical design will be chosen but the following components must exist:

Object properties - Edit all inserted objects properties manually
Images - manage the sheet images. Add/Delete/Change order
Editor - This is the canvas where objects will be drawn. (staffs/notes/etc)
Keyboard reference - All keyboard functions and how to use them
Import/Export - Import a previously saved img2musicXML project or export it either to it's own format or to MusicXML 3.0


Shikimori tracking anime - HTTP error 404 (+ example how to fix it)

Steps to reproduce

Anime should be added to the list on Shikimori
Select this anime to track in the application
API returns HTTP error 404

Expected behavior
Anime should start tracking without errors
Actual behavior
HTTP error 404
Crash logs
No response
Aniyomi version
<IP_ADDRESS>
Android version
Android 12
Device
Xiaomi Redmi Note 9 Pro
Other details
I examined the request creation code in the ShikimoriApi.kt file and discovered the cause of the error:

If replace "mangas" with "animes" the tracking will work.
I checked it on a copy - HTTP error 404 no longer appeared.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] If this is an issue with an official manga extension and this issue can be replicated in the Tachiyomi app, that I should be opening an issue in Tachiyomi's extensions repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Same problem and don't know how to solve.

I described the fix in Other details.  But I've never used Github, and I don't know how to add it to the project.  The screenshot shows the place in the code that needs to be replaced with "animes".  This will solve the problem.

I described the fix in Other details.  But I've never used Github, and I don't know how to add it to the project.  The screenshot shows the place in the code that needs to be replaced with "animes".  This will solve the problem.

I tried to login my account today but password reset didn't work, I'll try again tomorrow and see if that change fixes it

I described the fix in Other details.  But I've never used Github, and I don't know how to add it to the project.  The screenshot shows the place in the code that needs to be replaced with "animes".  This will solve the problem.

I tried to login my account today but password reset didn't work, I'll try again tomorrow and see if that change fixes it

You can create a temporary email for a test account on Shikimori. For example, https://temp-mail.org/ru/

You can create a temporary email for a test account on Shikimori. For example, https://temp-mail.org/ru/

no need, I already resolved it. I'll probably PR tomorrow. I fixed that and labels.

should be fixed with https://github.com/aniyomiorg/aniyomi/commit/58817c724e2808072ff273329cee261d12084927


get_context() performance

Hello,
I`m using Timber in a theme with a lot of small shortcodes. Every shortcode is rendered by timber. In some cases, a page can consist of 50 shortcodes and more.
I had performance problems, because Timber:get_context needed ~100ms to run.
I tested, if my "timber_context" function (add_filter('timber_context', 'add_to_context');) was the problem, but it was runned only once, and when I disabled it, the performance problems persisted.
I helped myself by doing the following:
class giTimberHelper {
    private $cache_context = null;

    function get_timber_post_from_id($id, $translate = false) {
        $posts = $this->get_timber_posts_from_ids([$id], $translate);

        if ($posts) {
            return $posts[0];
        }
        else {
            return [];
        }
    }
}
$gi_timber_helper = new giTimberHelper();

and then initialize my context with
global $gi_timber_helper;
$context = $gi_timber_helper->get_timber_context();

I dont know where this low performance comes from, its a big site with a lot of plugins:
"wpackagist-plugin/post-thumbnail-editor": "2.4.6",
"wpackagist-plugin/timber-library": "0.21.10",
"wpackagist-plugin/types": "<IP_ADDRESS>",
"wpackagist-plugin/advanced-tinymce-configuration": "1.2",
"wpackagist-plugin/breadcrumb-navxt": "5.2.2",
"wpackagist-plugin/post-type-archive-links": "1.3.1",
"wpackagist-plugin/add-custom-fields-to-media": "1.2.5",
"wpackagist-plugin/json-rest-api": "1.2.3",
"wpackagist-plugin/post-duplicator": "2.8",
"wpackagist-plugin/post-types-order": "1.8.5",
"wpackagist-plugin/taxonomy-terms-order": "<IP_ADDRESS>",
"wpackagist-plugin/cms-tree-page-view": "1.2.32",
"wpackagist-plugin/admin-menu-tree-page-view": "2.6.9",
"wpackagist-plugin/velvet-blues-update-urls": "3.2.4",
"wpackagist-plugin/regenerate-thumbnails": "2.2.4",
"wpackagist-plugin/wordpress-seo": "2.3.5",
"wpackagist-plugin/gravity-forms-no-captcha-recaptcha": "1.0.7",
"wpackagist-plugin/wp-ffpc": "1.10.0",
"wpackagist-plugin/backwpup": "3.2.0",
"wpml-media",
"wpml-string-translation",
"wpml-translation-management",
"gravityforms",
"gravityforms-multilingual",
"gravityformsmailchimp",
"revslider",

Please tell me if you need more info...
And thank you for this great plugin: I would probably not develop Wordpress themes if it would not exist!

Tested it with a page with almost no plugins, and the problem persists.

i'm seeing some significant times for timber_context in new relic, on a theme that uses tons of shortcodes (via custom visual composer widgets). would love to find out more about this.

Is this still something you're actively working on or need addressed? Please respond in two weeks or we'll close this thread

Thank you for inquiring but I no longer am interested in following this issue

On Oct 10, 2018 at 4:03 PM,  <Maciej Palmowski (mailto:notifications@github.com)>  wrote:
Is this still something you're actively working on or need addressed? Please respond in two weeks or we'll close this thread
—
You are receiving this because you commented.
Reply to this email directly,   view it on GitHub (https://github.com/timber/timber/issues/742#issuecomment-428711235), or   mute the thread (https://github.com/notifications/unsubscribe-auth/AADcWVPSjxqHLq1VbbFtq2In-Z-ow6MVks5ujlKjgaJpZM4GgQG4).


Migrate CI from Travis to GitHub Actions

Unexpected coverage drop, will investigate separately, doesn't seem to be caused by the changes in the code.


Support .greenkeeperrc

Would be nice if configuration could be defined in a .greenkeeperrc as well. I've found this repo: https://github.com/greenkeeperio/rc. I assume that support for this is upcoming?

No, we are not planning on adding support for .greenkeeperrc in the near future. The rc repository was something used for the CLI.


Receding-horizon demo

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


#86dtu8yuk - Include how to use NEP17Contract to Calling contracts do…

Summary or solution description
Added an example utilizing the NEP17Contract interface to call a NEP17 contract in the calling-smart-contracts docuimentation.

coverage: 91.201%. remained the same
when pulling fc6fd89d82dd01482f771fe5ad9161a7eba6d892 on CU-86dtu8yuk
into 8c6f9aea0994c4d341f12d1208c97ea40f891deb on development.

coverage: 91.201%. remained the same
when pulling 845aa703bab3bb15467ce062fa3bc4ee002834ed on CU-86dtu8yuk
into 8c6f9aea0994c4d341f12d1208c97ea40f891deb on development.


Problem size limits exceeded

Hi,
I downloaded free edition version for CPLEX Studio.
However, I ran into an issues while I was running JaBbA.
CPLEX environment opened Rcplex: num variables=3295154 num constraints=3532753 CPLEX Error  1016: Community Edition. Problem size limits exceeded. Purchase at https://ibm.co/2s0wqSa. Error in Rcplex2(cvec = cvec, Amat = Amat, bvec = consmeta$b, sense = consmeta$sense,  :   Failed to optimize problem.
I noticed that free edition is limited to 1000 variable and 1000 constraints. We've applied to IBM academic version but they rejected our application. Is there any way to run this package at this point?
Thanks!

Yes you need the full version of CPLEX or gurobi for most genomes
The problem size is really large.   Are you providing the binned read depth in place of the segment input?  Or is the read depth data really noisy and hypersegmented?
Usually the problem size is about 40-150K
Marcin

From: mjko1210<EMAIL_ADDRESS>Sent: Monday, June 29, 2020 2:47 PM
To: mskilab/JaBbA
Cc: Subscribed
Subject: [mskilab/JaBbA] Problem size limits exceeded (#28)
Hi,
I downloaded free edition version for CPLEX Studio.
However, I ran into an issues while I was running JaBbA.
CPLEX environment opened Rcplex: num variables=3295154 num constraints=3532753 CPLEX Error 1016: Community Edition. Problem size limits exceeded. Purchase at https://ibm.co/2s0wqSa. Error in Rcplex2(cvec = cvec, Amat = Amat, bvec = consmeta$b, sense = consmeta$sense, : Failed to optimize problem.
I noticed that free edition is limited to 1000 variable and 1000 constraints. We've applied to IBM academic version but they rejected our application. Is there any way to run this package at this point?
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/mskilab/JaBbA/issues/28, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC73JEMHN5T3J5SDNJ6TFFLRZDOUVANCNFSM4OLPVYKA.

Yes. I'm using 10K bin for this run (308,838 bins in total) and my data was from linked reads sequencing. Could you give me little more details on how you define problem size?

I think 'gurobi' only provide free trial for academic version. How easy it is to run JaBbA with gurobi instead of CPLEX?  Thanks!

The problem size the number of variables + constraints in the MIP
It’s a function of the number of segments and junctions inputted to the graph.
Usually <10,000 segments and <1000 junctions will give you <100K problem size - you have >3M
Sounds like you have either an order of magnitude more segments or junctions than an average highly rearranged cancer genome.  Too many segments can come from noisy read depth data or sensitive segmentation params.     Too many junctions can come from insufficient filtering of false positives
Linked reads have both issues
From: mjko1210<EMAIL_ADDRESS>Reply-To: mskilab/JaBbA<EMAIL_ADDRESS>Date: Monday, June 29, 2020 at 3:01 PM
To: mskilab/JaBbA<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [mskilab/JaBbA] Problem size limits exceeded (#28)
Yes. I'm using 10K bin for this run (308,838 bins in total) and my data was from linked reads sequencing. Could you give me little more details on how you define problem size?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/mskilab/JaBbA/issues/28*issuecomment-651301311__;Iw!!C6sPl7C9qQ!HoMngD37oFftWQRmd9HmAOsdtDoKxNEl5-ST51ZES-__UDYCXiBw8vrcsL223q1_HnI$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ABFUFY37WRA5CZILRZ23CS3RZDQHFANCNFSM4OLPVYKA__;!!C6sPl7C9qQ!HoMngD37oFftWQRmd9HmAOsdtDoKxNEl5-ST51ZES-__UDYCXiBw8vrcsL22_1ja4Ug$.

This message is for the recipient’s use only, and may contain confidential, privileged or protected information. Any unauthorized use or dissemination of this communication is prohibited. If you received this message in error, please immediately notify the sender and destroy all copies of this message. The recipient should check this email and any attachments for the presence of viruses, as we accept no liability for any damage caused by any virus transmitted by this email.

For gurobi just install the gurobi R package and use the gurobi flag in jba
https://www.gurobi.com/documentation/9.0/refman/ins_the_r_package.html
We haven’t actually tried it in a while, so let us know
Not sure why IBM rejected you but the full version should be available to all academic researchers
https://developer.ibm.com/docloud/blog/2019/07/04/cplex-optimization-studio-for-students-and-academics/
From: mjko1210<EMAIL_ADDRESS>Reply-To: mskilab/JaBbA<EMAIL_ADDRESS>Date: Monday, June 29, 2020 at 3:09 PM
To: mskilab/JaBbA<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [mskilab/JaBbA] Problem size limits exceeded (#28)
I think 'gurobi' only provide free trial for academic version. How easy it is to run JaBbA with gurobi instead of CPLEX? Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/mskilab/JaBbA/issues/28*issuecomment-651305108__;Iw!!C6sPl7C9qQ!GVgqAWM1hGWUgR-xtlneIvm6yPC-f0t62snph2BYgKEN9yK1CTBwBc1Qx5gOYqX8hJk$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ABFUFYYJQ6634WGFELQFZQDRZDRF5ANCNFSM4OLPVYKA__;!!C6sPl7C9qQ!GVgqAWM1hGWUgR-xtlneIvm6yPC-f0t62snph2BYgKEN9yK1CTBwBc1Qx5gOUwaF93Q$.

This message is for the recipient’s use only, and may contain confidential, privileged or protected information. Any unauthorized use or dissemination of this communication is prohibited. If you received this message in error, please immediately notify the sender and destroy all copies of this message. The recipient should check this email and any attachments for the presence of viruses, as we accept no liability for any damage caused by any virus transmitted by this email.

Please see first item in the FAQ.


Add additional PgTextExpressionMethods

I found myself implementing these in my own project, and thought it might be useful to others (and means I can drop it from my code in the future). As a result, here's a PR with the following:

Adds support for PostgreSQL's SIMILAR TO and NOT SIMILAR TO.
Adds support for ESCAPE to PostgreSQL's SIMILAR TO and NOT SIMILAR TO.
Added a summary of the changes to the changelog.

I think I've got everything necessary, but please let me know if there's more.

@weiznich Thanks for the super quick reviews!
I think I've got to the point where CI will pass (the last run was a fmt issue and a transient(?) issue on MacOS) but it apparently declined to run this time. Is there anything else you'd like to see here?


Previously, I use google-cloud-vertexai 0.3. I can't use service account json in 1.3.

Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Please run down the following list and make sure you've tried the usual "quick fixes":

Search the issues already opened: https://github.com/googleapis/google-auth-library-java/issues
Check for answers on StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform

If you are still having issues, please include as much information as possible:
Environment details

google-cloud-vertexai
OS type and version: Not related
Java version: Not related
version(s): 1.3.0

Steps to reproduce

Check the code example.
Previously, I can pass the Credentials to the VertexAI constructor.
Now, I can't.
Service account is more convenient for deployment instead of ADC.
How can I use service account json in the new version?

Code example
    private GoogleCredentials getGoogleCredentials() {
        if (googleCredentials == null) {
            try {
                List<String> defaultScopes =
                        PredictionServiceStubSettings.defaultCredentialsProviderBuilder().getScopesToApply();
                googleCredentials = GoogleCredentials.fromStream(new FileInputStream(serviceAccountFile)).createScoped(defaultScopes);
            } catch (IOException e) {
                throw new RuntimeException(e);
            }
        }
        return googleCredentials;
    }

    private VertexAI getVertexAI() {
        if (vertexAI == null) {
            vertexAI = new VertexAI(projectId, location, getGoogleCredentials());
        }
        return vertexAI;
    }

Stack trace
Any relevant stacktrace here.

External references such as API reference guides

?

Any additional information below
Following these steps guarantees the quickest resolution possible.
Thanks!

OK. I see. Use builder instead.


Add custom transparency to interactive plots

The static plots have the ability to pass an alpha array-like for the transparency of the points, I wanted to use this feature in interactive plots and it was fairly easy to add.
Most of the changes in the git diff are from running the black code formatter, lol

As requested by @richardmillson I rebased and split the commits into the actual changes and the code formatter changes.


validator: make example to carry v1beta1 version

As the controller API has been moved from alpha1 to beta1
the examples also has to follow
Signed-off-by: Humble Chirammal<EMAIL_ADDRESS>
/kind bug

NONE

/assign @bswartz

Oops! Good catch.
/lgtm
/approve


Incomplete execution on new versions of DietPi

PiVPN Issue Template

Issue
After much hassle I went back to raspbian and was able to get everything to work. During my many attempts to install and utilize PiVPN on DietPi 6.1 and 6.2 the install TUIs would stop shortly after the port and protocol selection. It never got to the FQDN or DNS server selection. However the pivpn command would still work and allow me to create .ovpn profiles. These profiles were incomplete as they did not have series of commands prior to the ca certificate block. It also appeared that the openvpn service never got to the point of starting due to there being no listening port active.
Have you searched for similar issues and solutions?
Yes and none were found.

Console output of curl install.pivpn.io | bash
  Output Here

Console output of pivpn add or pivpn add nopass
  OS wiped and replaced before issue determined to be valid. Results no longer exist.

Console output of pivpn debug
  OS wiped and replaced before issue determined to be valid. Results no longer exist.

Console Output of sudo iptables -t nat -S
  OS wiped and replaced before issue determined to be valid. Results no longer exist.

Console Output of sudo iptables -S
  OS wiped and replaced before issue determined to be valid. Results no longer exist.

output of sudo netstat -uanp | grep openvpn
  OS wiped and replaced before issue determined to be valid. Results no longer exist.

Have you taken any steps towards solving your issue?
 which?

@grahambo2015
We are unable to replicate any issues with DietPi + PiVPN currently:
https://github.com/Fourdee/DietPi/issues/1450#issuecomment-370178919

I'm using version 6.9 of DietPi and faced the same situation today.
The installation did finish after creating the private key, so I was not asked for a "Public IP or DNS" and everything else that should have come after this step.
DietPi rebooted and I was able to create a new client, but the ovpn file could not be stored, as the "opns" folder was not created in my local user folder.
I'm happy to share any additional information, if needed.

Hi Fourdee,
it was dietpi (root).
Thanks.

I did also find the install.log of this try. Are you interested to have a look at it?

@frdrrhr

I did also find the install.log of this try. Are you interested to have a look at it?

Hi,
Although we are unable to replicate this our end, if this is still an issue, please post the logs for us to review.

@Fourdee
This is the file:
install.log
If needed, I can add other stuff too.
Thx.

@frdrrhr
Thanks, apologies for the delay.
The logfile appears fine, no errors/issues reported.


NuGet targets, unable to resolve Microsoft.NETCore.App

Hi,
I followed closely the thread here: https://github.com/Microsoft/vsts-tasks/issues/3311
and it was said that improvement would be made so you could update more quickly the images on the agents, namely VS 2017.
I still cannot use .net core 2.0 in the Hosted VS 2017 as of today although .net core 2.0 preview 1 was released several weeks ago.
I cannot even use the Hosted linux and the official docker image as the Hosted linux agents are not available in my hosted agent pool in my team project (not released yet...).
Could you please clarify the plans?
C:\Program Files\dotnet\sdk\1.0.4\NuGet.targets(97,5): error : Unable to resolve 'Microsoft.NETCore.App (>= 2.0.0)' for '.NETCoreApp,Version=v2.0'.

Detected package downgrade: NETStandard.Library from 2.0.0-preview1-25301-01 to 1.6.1

The VS2017 hosted pool has VS 2017 with all features installed on it.  The issues from #3311 (latency while in preview going to release) are not relevant since the image now has the full release VS 2017.
I'm adding the packaging team for your nuget issue.
@alexmullans

I put a global.json as follow (this is the official sdk for preview 1 release):
{
    "sdk": {
        "version": "2.0.0-preview1-005957"
    }
}

but the VS 2017 agent still use the 1.0.4 sdk that does not support 2.0 packages.
C:\Program Files\dotnet\sdk\1.0.4\NuGet.targets(97,5): warning : Detected package downgrade: NETStandard.Library from 2.0.0-preview1-25301-01 to 1.6.1

So I think VS 2017 image does not natively provide the 2.0 preview 1 sdk.

@Jonathan34 can you try adding a NuGet Tool Installer task at the beginning of your build that specifies version 4.1.0?

From https://slb-swt-globalrealtime.visualstudio.com/WITSML%20Objects%20Library/_git/WITSMLObjectsLibrary
 * [new branch]      master        -> origin/master
 * [new branch]      netstandard20 -> origin/netstandard20
git checkout --progress --force 027fe7106bc56de70277291717df5e9f6fca00cd
Note: checking out '027fe7106bc56de70277291717df5e9f6fca00cd'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
  git checkout -b <new-branch-name>
HEAD is now at 027fe71... Enforce use of .net core 2.0 sdk
******************************************************************************
Finishing: Get Sources
******************************************************************************
******************************************************************************
Starting: Use NuGet 4.10
******************************************************************************
==============================================================================
Task         : NuGet Tool Installer
Description  : Acquires a specific version of NuGet from the internet or the tools cache and adds it to the PATH. Use this step to change the version of NuGet used in the NuGet Restore and NuGet Command steps.
Version      : 0.1.0
Author       : Microsoft Corporation
Help         :
==============================================================================
Downloading: https://dist.nuget.org/win-x86-commandline/v4.1.0/nuget.exe
Caching tool: NuGet 4.1.0 x64
Using version: 4.1.0
Found tool in cache: NuGet 4.1.0 x64
Using tool path: d:\a\_tool\NuGet\4.1.0\x64
Prepending PATH environment variable with directory: d:\a\_tool\NuGet\4.1.0\x64
******************************************************************************
Finishing: Use NuGet 4.10
******************************************************************************
******************************************************************************
Starting: Restore
******************************************************************************
==============================================================================
Task         : .NET Core
Description  : Build, test and publish using dotnet core command-line.
Version      : 1.0.2
Author       : Microsoft Corporation
Help         : [More Information](https://go.microsoft.com/fwlink/?linkid=832194)
==============================================================================

dotnet restore
  Installing Microsoft.Extensions.Configuration.FileExtensions 2.0.0-preview1-final.
...

Error: C:\Program Files\dotnet\dotnet.exe failed with return code: 1
"C:\Program Files\dotnet\dotnet.exe" restore "d:\a\1\s\Main\Source\proj\projA\projA.csproj"
  Restoring packages for d:\a\1\s\Main\Source\proj\projA\projA.csproj...
C:\Program Files\dotnet\sdk\1.0.4\NuGet.targets(97,5): warning : Detected package downgrade: NETStandard.Library from 2.0.0-preview1-25301-01 to 1.6.1  [d:\a\1\s\Main\Source\proj\projA\projA.csproj]
C:\Program Files\dotnet\sdk\1.0.4\NuGet.targets(97,5): warning :  projA (>= 13.0.200) -> Microsoft.Extensions.Configuration.Json (>= 2.0.0-preview1-final) -> NETStandard.Library (>= 2.0.0-preview1-25301-01)  [d:\a\1\s\Main\Source\proj\projA\projA.csproj]
C:\Program Files\dotnet\sdk\1.0.4\NuGet.targets(97,5): warning :  projA (>= 13.0.200) -> NETStandard.Library (>= 1.6.1) [d:\a\1\s\Main\Source\proj\projA\projA.csproj]
C:\Program Files\dotnet\sdk\1.0.4\NuGet.targets(97,5): warning : Detected package downgrade: NETStandard.Library from 2.0.0-preview1-25301-01 to 1.6.1  [d:\a\1\s\Main\Source\proj\projA\projA.csproj]
C:\Program Files\dotnet\sdk\1.0.4\NuGet.targets(97,5): warning :  projA (>= 13.0.200) -> Microsoft.Extensions.Configuration.Binder (>= 2.0.0-preview1-final) -> NETStandard.Library (>= 2.0.0-preview1-25301-01)  [d:\a\1\s\Main\Source\proj\projA\projA.csproj]
C:\Program Files\dotnet\sdk\1.0.4\NuGet.targets(97,5): warning :  projA (>= 13.0.200) -> NETStandard.Library (>= 1.6.1) [d:\a\1\s\Main\Source\proj\projA\projA.csproj]
C:\Program Files\dotnet\sdk\1.0.4\NuGet.targets(97,5): warning : Detected package downgrade: NETStandard.Library from 2.0.0-preview1-25301-01 to 1.6.1  [d:\a\1\s\Main\Source\proj\projA\projA.csproj]
C:\Program Files\dotnet\sdk\1.0.4\NuGet.targets(97,5): warning :  projA (>= 13.0.200) -> Microsoft.Extensions.Configuration.Abstractions (>= 2.0.0-preview1-final) -> NETStandard.Library (>= 2.0.0-preview1-25301-01)  [d:\a\1\s\Main\Source\proj\projA\projA.csproj]
C:\Program Files\dotnet\sdk\1.0.4\NuGet.targets(97,5): warning :  projA (>= 13.0.200) -> NETStandard.Library (>= 1.6.1) [d:\a\1\s\Main\Source\proj\projA\projA.csproj]
  Lock file has not changed. Skipping lock file write. Path: d:\a\1\s\Main\Source\proj\projA\obj\project.assets.json
  Restore completed in 542.52 ms for d:\a\1\s\Main\Source\proj\projA\projA.csproj.

Still fails :(

I am having the same issue, please count me in.

This issues seems to appears on visual studio 2017 actually, not sure it is related to the VSTS tasks anymore. I do not have a windows machine on hand but will try to check on a colleague's machine.

This is likely a consequence of the hosted agents not including preview versions of .net core.

probably it is one issue but even on a windows pc with .net core 2 preview 1 installed, the same issue appears when building with vs 2017. but not with the cli (on the same machine).

In my case it builds fine on my computer. It is just the VSTS task failing, probably because of the reason @jmyersmsft mentioned above.
@jmyersmsft This issue with hosted VSTS agents not having the latest bits of other things started to become a serious obstacle for me. I don't know if it is just me but I, as a developer, like to enjoy preview builds so that I can be ready for the future releases and also do my best to provide early feedback. As you might imagine, it is hard to give up on a build mechanism just because I prefer working on pre-release software. I am wondering if these pre-release software can be deployed to the hosted build agents (being VS 2017 agents in this case) once a major version is achieved? I don't mean to ask for every single beta release but at least for some releases like preview1, preview2, etc. This can be an automated task. May I ask for your opinion on that if you are the right person to ask? Thanks in advance!

@CoskunSunali that feedback will need to go back to @bryanmacfarlane. I'm from the package management service.

@CoskunSunali - customers rely on those images for production builds.  For tools that are globally installed, need to wait until released (and even then they can destabilize someone).
We maintain pools for each era of VS and when VS2018 previews come out then we will have a preview of that one.
The problem is customer one wants everything else stable but preview of tool y installed and customer 2 wants everything else stable but preview of tool x installed.
There's two solutions to it:

Create your own private agent on an azure VM.  You control your tool sets.  You get incremental source, packages, etc...
Pull the tools JIT.  .net core tools can be downloaded JIT at the front of the build.  We recently create tool installers for this very reason.  We will add a net core tools one for convenience (so you don't have to write a script).  See here:  https://youtu.be/Ie8EuvqJ0Hg

Also keep in mind that the reasons the builds start relative quickly is large elastic pools of machines from homogenous images in data centers.  There are machines waiting around with the one VS2017 image that you use and the customer relying on that image for production builds.  We will have a VS2015 pool and a VS2018 preview one when it comes out.

Or use the hosted linux agent and docker to build your app.
Or add a step similar to nuget installer that we put at the beginning that allows to pull any version.
If this is not resolved in the vs 2017 agent image, then i'll probably use docker.

@bryanmacfarlane I cannot disagree with anything you say. May I ask, what is your opinion on an agent that is specific for developers? I mean, having another one just like "VS 2017" but something like "VS 2017 Dev". Production customers would not be affected in that case.
By the way, I was able to use some PowerShell scripts to download the dotnet runtime as the first step of the build definition (as you mentioned). I also figured out how to use the dotnet.exe that shipped with that download and execute further commands like dotnet restore, etc. Please see https://stackoverflow.com/a/41741641
My current problem is somehow not being able to find the MSBuild version 15 (or 15.1?). The documentation states "15" but the build agent VS 2017 is unable to find it. The same goes for "15.1".
I tried pulling NuGet 4.1.0 using the NuGet Installer Tool to see if that would help but there is no documentation for how to refer to that downloaded custom version later on within the NuGet Packager and NuGet Publisher tasks. Your assistance would be highly appreciated on this matter.
Please see my comment at https://github.com/NuGet/Home/issues/5170#issuecomment-309064229

Yes, we have discussed multiple per era images ( and one could be dev ).  I like your idea of vs2017-dev because we would only do that for the latest vs ( we could also call it just vs dev ).  That mitigates the explosion of images and reduction of elasticity.
There's a couple other efforts that are just now taking shape
Tool installers - see video link above.  We need a net core template that allows and encourages JIT pulling net core tools be version decouple from image
Docker - we're working on ability to select the image to run your build in.  Works great for semi smaller images like net core.  Not as viable for full VS but something we're aware of.  Also related to yaml also in the works where you'll be able to declare image or images to run build and tests in.  This really is the ideal solution for all of us - your defined env really is the same between dev, CI, prod
We just recently added the ability to have multiple hosted pools.  We are also investing in the image generation process to turn around images faster.  That will be critical for a dev

Sounds great. Thanks for the details!
These tool installers, once they are well documented and expanded to a range of other useful tools (including .NET Core) will be useful and will solve the problems of many, I believe.
Regarding the video, I just watched it but did not really get the idea of how to really use the NuGet Tools Installer. It is also unknown to me if using NuGet 4.1.0 would really fix the MSBuild 15/15.1 issue. I would be grateful if you had a link to a blog post, document or something like that. I spent two days trying to figure out how to customize the NuGet Packager and NuGet Publishers to use the custom version of NuGet that is JIT pulled using NuGet Tools Installer and also fail finding the appropriate MSBuild version - even though it is the "VS 2017" agent and is supposed to have MSBuild 15/15.1 - I feel there is lack of documentation on it.
Thanks for your time! 👍

@bryanmacfarlane A few updates from my end.
I wrote a PS script that downloads NuGet 4.1.0 and saves into a folder. Then the rest of my build uses that one and the issue with MSBuild 15 seems to be resolved. It may be a bug with NuGet 4.0.
And I also realized that I don't have to use the NuGet Packager and NuGet Publisher tasks at all. It seems that dotnet pack and dotnet nuget push are what I was supposed to use for convenience.
Thanks for your time replying!

NuGet 4.1 does indeed fix some issues. As of tomorrow, you should be able to replace your PowerShell script with the new NuGet Tool Installer task, specify 4.1.0 as the version to install, then use the new NuGet task to restore packages as expected.
We're also working on updates to properly support dotnet pack and dotnet nuget push in the dotnet task, but they're a sprint or two away.

A workaround I used to build .net core 2.0 preview projects on VSTS:

Get dotnet-install.ps1 from https://github.com/dotnet/cli/tree/release/2.0.0-preview2/scripts/obtain. Make sure it is from the correct branch that your code needs.
Configure a PowerShell Script task to run this script. By default, this script will install the .net core sdk in $(LOCALAPPDATA)\Microsoft\dotnet.
Configure several Command Line tasks to run restore, build, test, and publish with dotnet cli. Instead of using dotnet directly, the full path of the installed sdk should be used, which is $(LocalAppData)\Microsoft\dotnet\dotnet.exe.

With the above steps, I can build the .net core 2.0 preview projects successfully with VSTS.

Final .net 2.0 is out and still not solved.
I've added NuGet Tool Installer task that installs v4.3.0 as well as .NET Core Tool Installer and still getting:

C:\Program Files\dotnet\sdk\1.0.4\NuGet.targets(97,5): error : Unable to resolve 'NETStandard.Library (>= 1.6.1)' for '.NETStandard,Version=v2.0'.

2017-08-16T15:44:41.1987575Z ##[section]Starting: Use NuGet 4.x
2017-08-16T15:44:41.2157578Z ==============================================================================
2017-08-16T15:44:41.2157578Z Task         : NuGet Tool Installer
2017-08-16T15:44:41.2157578Z Description  : Acquires a specific version of NuGet from the internet or the tools cache and adds it to the PATH. Use this step to change the version of NuGet used in the NuGet Restore and NuGet Command steps.
2017-08-16T15:44:41.2157578Z Version      : 0.1.1
2017-08-16T15:44:41.2157578Z Author       : Microsoft Corporation
2017-08-16T15:44:41.2157578Z Help         : [More Information](https://go.microsoft.com/fwlink/?linkid=852538)
2017-08-16T15:44:41.2157578Z ==============================================================================
2017-08-16T15:44:42.2564137Z You are using a query match on the version string. Behavior changes or breaking changes might occur as NuGet updates to a new version.
2017-08-16T15:44:42.3644154Z Downloading: https://dist.nuget.org/win-x86-commandline/v4.3.0/nuget.exe
2017-08-16T15:44:42.4644166Z Caching tool: NuGet 4.3.0 x64
2017-08-16T15:44:42.4714159Z Using version: 4.3.0
2017-08-16T15:44:42.4724170Z Found tool in cache: NuGet 4.3.0 x64
2017-08-16T15:44:42.4724170Z Using tool path: d:\a\_tool\NuGet\4.3.0\x64
2017-08-16T15:44:42.4724170Z Prepending PATH environment variable with directory: d:\a\_tool\NuGet\4.3.0\x64
2017-08-16T15:44:42.4804171Z ##[section]Finishing: Use NuGet 4.x

2017-08-16T15:44:42.4824163Z ##[section]Starting: Restore
2017-08-16T15:44:42.4834169Z ==============================================================================
2017-08-16T15:44:42.4834169Z Task         : .NET Core
2017-08-16T15:44:42.4834169Z Description  : Build, test, package, or publish a dotnet application, or run a custom dotnet command. For package commands, supports NuGet.org and authenticated feeds like Package Management and MyGet.
2017-08-16T15:44:42.4834169Z Version      : 2.0.5
2017-08-16T15:44:42.4834169Z Author       : Microsoft Corporation
2017-08-16T15:44:42.4834169Z Help         : [More Information](https://go.microsoft.com/fwlink/?linkid=832194)
2017-08-16T15:44:42.4834169Z ==============================================================================
2017-08-16T15:44:43.3298644Z SYSTEMVSSCONNECTION exists true
2017-08-16T15:44:43.3328644Z Saving NuGet.config to a temporary config file.
2017-08-16T15:44:43.3439930Z ##[warning]Can\'t find loc string for key: NGCommon_NoSourcesFoundInConfig
2017-08-16T15:44:43.3448653Z ##[warning]NGCommon_NoSourcesFoundInConfig d:\a\1\Nuget\tempNuGet_736.config
2017-08-16T15:44:43.3698655Z [command]"C:\Program Files\dotnet\dotnet.exe" restore d:\a\1\s\src\CommandStack\CommandStack.csproj --configfile d:\a\1\Nuget\tempNuGet_736.config --verbosity Detailed
2017-08-16T15:44:46.3920139Z   Restoring packages for d:\a\1\s\src\CommandStack\CommandStack.csproj...
2017-08-16T15:44:46.4455885Z C:\Program Files\dotnet\sdk\1.0.4\NuGet.targets(97,5): error : Unable to resolve 'NETStandard.Library (>= 1.6.1)' for '.NETStandard,Version=v2.0'. [d:\a\1\s\src\CommandStack\CommandStack.csproj]
2017-08-16T15:44:46.4704173Z   Generating MSBuild file d:\a\1\s\src\CommandStack\obj\CommandStack.csproj.nuget.g.props.
2017-08-16T15:44:46.4751984Z   Generating MSBuild file d:\a\1\s\src\CommandStack\obj\CommandStack.csproj.nuget.g.targets.
2017-08-16T15:44:46.4762048Z   Writing lock file to disk. Path: d:\a\1\s\src\CommandStack\obj\project.assets.json
2017-08-16T15:44:46.5172057Z   Restore failed in 79.89 ms for d:\a\1\s\src\CommandStack\CommandStack.csproj.
2017-08-16T15:44:46.5192052Z
2017-08-16T15:44:46.5192052Z   Errors in d:\a\1\s\src\CommandStack\CommandStack.csproj
2017-08-16T15:44:46.5202059Z       Unable to resolve 'NETStandard.Library (>= 1.6.1)' for '.NETStandard,Version=v2.0'.
2017-08-16T15:44:46.5202059Z
2017-08-16T15:44:46.5202059Z   NuGet Config files used:
2017-08-16T15:44:46.5202059Z       d:\a\1\Nuget\tempNuGet_736.config
2017-08-16T15:44:46.5552047Z ##[error]Error: C:\Program Files\dotnet\dotnet.exe failed with return code: 1
2017-08-16T15:44:46.5552047Z ##[error]Packages failed to restore
2017-08-16T15:44:46.5622062Z ##[section]Finishing: Restore

@Liero sorry to hear that. The NuGet tool installer won't help at all here - you'll want the .NET Core Tool Installer task and .NET Core task for your scenario. You mentioned you'd tried the .NET Core Tool Installer but were still having issues. Did you use "2.0.0" for the Version field in that task? If so, could you share the output here? I'd expect that to have been able to resolve the issue you're seeing.

Actually, three steps vere required to make it work: https://stackoverflow.com/questions/45717283/vsts-build-packages-failed-to-restore-unable-to-resolve-netstandard-library/45726277?noredirect=1#comment78457101_45726277
I believe it could work by default without the three steps...

@Liero I saw your SO post(s) earlier today and tried them, and I still experience this error currently.  I posted about it here: https://developercommunity.visualstudio.com/content/problem/159780/error-nu1100-unable-to-resolve-netstandardlibrary.html
I'm pretty sure the VS2017 hosted agent has the correct SDK bits, so it seems like the SDK version isn't the cause.  However, I still don't really have much idea what would be causing it.

@aggieben,
Does your build task have a NET Core Tool Installer "2.0.0" [1] build step before all of your other steps in the build?
[1]

@keithrob no - but like I said I verified in the output that the correct version of the SDK is being used (and in addition to that, I'm now using a global.json to ensure an error occurs if the correct version isn't available).
I did just figure this out, though.  I'm using Paket to manage my dependencies and I neglected to add NETStandard.Library to my paket.dependencies file.  So the root cause here was PEBKAC (problem exists between keyboard and chair). 😉

@aggieben,
Glad to hear the problem is resolved.  Curious, can you explain how you verified the correct version of the SDK?

I verified in the output

I have same issue I fixed it by "Add  https://api.nuget.org/ to trusted site on Internet Option"


Question about ARPL results in paper

Hello
Thanks for your wonderful job,  but I have a question:
Why the result in paper about ARPL is  much lower  than that in original ARPL paper.

Noticed that the data split is different, but these two results differs illogically a lot,
I want to know how do you reproduce the ARPL result in paper?
Do you reproduce it follow the ARPL optimizer and training setting or follow your setting in paper?
I have reproduce the ARPL, it is the same in ARPL paper, so it really confused me.

Thanks for your interest.
As you mentioned, the performance gap only comes from the different split information.
We used the ARPL's official GitHub implementation to reproduce the performance.
So, if you try to run with our publicized split information, you may get the same results in our table.
The reason why the performance gap is noticeable is that the split information is critical in the literature on open set recognition.
Suppose you have open set classes that one is very similar to a closed set class and the other not.
Then, we can expect the classifier to easily distinguish the latter open set class while the former is hard to be distinguished.
For these reasons, in the paper, we argued that the split information should be unified to fairly measure the performance between methods.


What should OmittedTypeAnnotation.code produce?

Today, it ends up putting the OmittedTypeAnnotation directly into the code.
We could keep that, and possibly just change the toString() of OmittedTypeAnnotation, but that seems a bit weird.
In https://dart-review.googlesource.com/c/sdk/+/365960/1 I tried to change the code object to just the string <omitted>, but that broke various tests - it looks like we are actually putting in the inferred type eventually through some magic smarts, at least in some scenarios. But, I don't really understand the mechanisms at play here.
cc @johnniwinther

In phase 1+2 augmentation libraries the omitted types are generated as OmittedType1,  OmittedType2, etc and replaced with the inferred type in phase 3 and merged augmentation libraries. I think we assert or throw if the type isn't inferred.

Ok, so you do expect to get the actual OmittedTypeAnnotation back?

The OmittedTypeAnnotation is a valid value. We should though always be able to generate the actual type in phase 3 (we even have an assert for this).
Do you see this is in the merged augmentation library?

I haven't seen any actual issues with this to be clear, I was just surprised to see the actual type annotations. All Code objects have a list of parts, which are documented as being only Identifier, String, and Code. But it does make sense that these are allowed, so I will just update the docs that they can also be OmittedTypeAnnotations.

Fwiw I actually ran into this because of an extension I had written on code objects, to emit a debug string, which didn't handle OmittedTypeAnnotation objects, so it fell back on toString().


VBLOCKS-XXXX Fix build

Updated circle CI Image.
Updated Video SDK version.
Updated Changelog.

Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

[X] I acknowledge that all my contributions will be made under the project's license.

Should we also add the xcshareddata/swiftpm/Package.resolved file since it's tracked by git ?


Update README.md

Proposal for improvement of the readme. Please check details for exactness...

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (main@a19c1a9). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #118   +/-   ##
=======================================
  Coverage        ?   85.52%
=======================================
  Files           ?       84
  Lines           ?     4803
  Branches        ?        0
=======================================
  Hits            ?     4108
  Misses          ?      695
  Partials        ?        0

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


HH-349 | refactor: use HDS icons, remove unused icons/svgs/styles

Description
refactor: use HDS icons, remove unused icons/svgs/styles
refs HH-349
Issues
Closes
Related
HH-349
Testing
Automated tests
Manual testing
Screenshots

cd apps/sports-helsinki/
yarn build
yarn start
accept all cookies
go to search page
refresh a few times
avot!

Additional notes

Hobbies-Helsinki branch is deployed to platta: https://harrastukset-pr660.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://tapahtumat-pr660.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://harrastukset-pr660.dev.hel.ninja :laughing::tada::tada::tada:

Sports-Helsinki branch is deployed to platta: https://liikunta-pr660.dev.hel.ninja :rocket::rocket::rocket:

EVENTS GRAPHQL PROXY is deployed to platta: https://events-graphql-proxy-pr660.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://liikunta-pr660.dev.hel.ninja :laughing::tada::tada::tada:

VENUE GRAPHQL PROXY is deployed to platta: https://venue-graphql-proxy-pr660.dev.hel.ninja :rocket::rocket::rocket:

Events-Helsinki branch is deployed to platta: https://tapahtumat-pr660.dev.hel.ninja :rocket::rocket::rocket:

Hobbies-Helsinki branch is deployed to platta: https://harrastukset-pr660.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://tapahtumat-pr660.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://liikunta-pr660.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://harrastukset-pr660.dev.hel.ninja :laughing::tada::tada::tada:

VENUE GRAPHQL PROXY is deployed to platta: https://venue-graphql-proxy-pr660.dev.hel.ninja :rocket::rocket::rocket:

Looks good to me, but it would be good if @melniiv would review this. I think that it's a good thing that we don't need to maintain the 3rd party icons, but the HDS is doing it for us. If they are updated, we can get the new ones by updating the HDS.


Unable to install from any targets

name: new
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/new...
chroot: failed to run command '/usr/local/bin/croutonversion': No such file or directory
Unmounting /mnt/stateful_partition/crouton/chroots/new...
name: xenial
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/xenial...
chroot: failed to run command '/usr/local/bin/croutonversion': No such file or directory
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...

Please describe your issue:

After the above, run sudo delete-chroot for both
Run sudo edit-chroot -all results in No chroots found in /mnt/stateful_partition/crouton/chroots
Run sudo crouton -t xfce

Installing xenial-amd64 chroot to /usr/local/chroots/xenial
Downloading bootstrap files...
W: Cannot check Release signature; keyring file not available /usr/share/keyrings/ubuntu-archive-keyring.gpg
I: Retrieving InRelease
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Chosen extractor for .deb packages: ar
Moving bootstrap files into the chroot...
Preparing chroot environment...
Installing brightness into the chroot...
Installing croutonpowerd into the chroot...
Installing croutonversion into the chroot...
Installing host-dbus into the chroot...
Installing host-wayland into the chroot...
cp: cannot create directory '/var/run/crouton/mnt/stateful_partition/crouton/chroots/xenial/usr/src/crouton': No such file or directory

sudo crouton -u

/usr/local/chroots/xenial already exists; updating it...
Preparing chroot environment...
Installing brightness into the chroot...
Installing croutonpowerd into the chroot...
Installing croutonversion into the chroot...
Installing host-dbus into the chroot...
Installing host-wayland into the chroot...
cp: cannot create directory '/var/run/crouton/mnt/stateful_partition/crouton/chroots/xenial/usr/src/crouton': No such file or directory

sudo delete-chroot xenial

Finished deleting /mnt/stateful_partition/crouton/chroots/xenial

sudo edit-chroot -all

No chroots found in /mnt/stateful_partition/crouton/chroots

sudo crouton -u

No chroots found in /mnt/stateful_partition/crouton/chroots
/usr/local/chroots/xenial does not exist; cannot update.
Valid chroots:

Not sure what is going on here. Even after deleting all chroots it still seems to think that xenial exists somewhere. Not sure where to find a file where this would be defined in.
If known, describe the steps to reproduce the issue:
This is a Chromebook that had xfce installed on it before. It hasn't been used ~2 years. I downloaded crouton again and ran the new command to add crouton to bin since Downloads no longer allows executables.

@tekstrand,
The message:

No chroots found in /mnt/stateful_partition/crouton/chroots
/usr/local/chroots/xenial does not exist; cannot update.
Valid chroots:

just means that the default chroot, xenial, is not installed nor are any other chroots.
I'm not sure why you are getting the error:

cp: cannot create directory '/var/run/crouton/mnt/stateful_partition/crouton/chroots/xenial/usr/src/crouton': No such file or directory

on a new installation.
it might be best to run: sudo delete-chroot *
Then reboot and try again.
Hope this helps,
-DennisLfromGA

sudo delete-chroot * results in
/mnt/stateful_partition/crouton/chroots/bin not found

I have searched around but found no directly related results. Any other ideas?

@tekstrand,
That message may just indicate that there are no chroots installed any longer.
If /usr/local/chroots/ has no chroots under it then your good to go.
If you find chroots in there then try to remove them manually with:

sudo rm -rf /usr/local/chroots/*

Any other ideas?

Yep, reboot and try again.
Hope this helps,
-DennisLfromGA

@DennisLfromGA,
Same error after attempting the recommendations.
cp: cannot create directory '/var/run/crouton/mnt/stateful_partition/crouton/chroots/xenial/usr/src/crouton': No such file or directory

Any log files I could look into?

@tekstrand,
Sorry, I'm stumped.
What's listed in here when you enter:

sudo ls -l /mnt/stateful_partition/crouton/chroots/xenial/usr/src/

Any log files I could look into?

You might be able to get the complete output in a file with:

sudo sh -x /usr/local/bin/crouton -t xfce 2>&1 | tee ~/crouton.out

Then examine ~/crouton.out when it finishes or errors & exits.
Hope this helps,
-DennisLfromGA

If you don't have any important local information. Then try a powerwash...

@MrHallway0 what is a "powerwash"? I've never heard that term.

Where you reset the device to the default. Also known as factory reset. Here are instructions: support.google.com/....


chore(cargo-codspeed): set verbosity to normal

Summary
cargo codspeed is printing with --verbose, which fills the log with lots of compilation messages that are uninteresting to normal users.
e.g. build benchmark step in https://github.com/web-infra-dev/oxc/actions/runs/6095539763/job/16539311128

This PR sets the verbosity to normal.
Test Plan
I ran the built binary on my project and sees no compilation messages.

Great, thank you! Merging this as well!


Upgrade to postcss 8

Currently, vue-tailwind declares the dependencies
postcss "^7"
tailwindcss "npm:@tailwindcss/postcss7-compat"

It would be nice if you could upgrade this to postcss 8 and remove the tailwind compatibility tag.

Yeah this is an interesting package, way too much config really, but not using all the current requirements of Tailwind is a dealbreaker.

@tobiasdiez tailwindcss/postcss is now a dev dependency so you can use whatever you like
It should have been like that from the beginning. I don't know how they got as dependencies.

Closing this but feel free to open if you have something more to add


Download failed: failed during retryable request: failed to write file: read tcp ... : read: connection reset by peer

2017/02/06 18:30:23 PivNet Resource version: 0.30.2
2017/02/06 18:30:23 Creating download directory: /tmp/build/get
2017/02/06 18:30:23 Getting release for product slug: 'elastic-runtime' and product version: '1.8.27'
2017/02/06 18:30:24 Accepting EULA for release with ID: 3974
2017/02/06 18:30:24 Getting product files
2017/02/06 18:30:24 Getting file groups
2017/02/06 18:30:25 Getting release dependencies
2017/02/06 18:30:25 Getting dependency specifiers
2017/02/06 18:30:25 Getting release upgrade paths
2017/02/06 18:30:26 Downloading files
2017/02/06 18:30:26 Filtering download links by glob
2017/02/06 18:30:26 Downloading filtered files
2017/02/06 18:30:26 Downloading: 'PCF Elastic Runtime' to file: '/tmp/build/get/cf-1.8.27-build.2.pivotal'
 4.65 GB / 5.05 GB [===========================================>---]  92.18% 44s
2017/02/06 18:31:11 Download failed: failed during retryable request: failed to write file: read tcp <IP_ADDRESS>:48360-><IP_ADDRESS>:443: read: connection reset by peer
ERROR: failed during retryable request: failed to write file: read tcp <IP_ADDRESS>:48360-><IP_ADDRESS>:443: read: connection reset by peer

Do this kind of failure allows for retrying/resuming the download?
Thanks!
Pierre

@pdelagrave To my mind, the resource should have retried. My guess is we have the errors that trigger retries scoped too narrowly. I'll open a bug for this and keep you up to date.

Same problem happened today with 0.30.0, with an error message that is a bit different.
2017/02/17 19:17:58 PivNet Resource version: 0.30.3
2017/02/17 19:17:58 Creating download directory: /tmp/build/get
2017/02/17 19:17:58 Getting release for product slug: 'pivotal-rabbitmq-service' and product version: '1.7.13-alpha.7'
2017/02/17 19:17:59 Accepting EULA for release with ID: 4372
2017/02/17 19:17:59 Getting product files
2017/02/17 19:17:59 Getting file groups
2017/02/17 19:18:00 Getting release dependencies
2017/02/17 19:18:01 Getting dependency specifiers
2017/02/17 19:18:01 Getting release upgrade paths
2017/02/17 19:18:01 Downloading files
2017/02/17 19:18:01 Filtering download links by glob
2017/02/17 19:18:01 Downloading filtered files
2017/02/17 19:18:01 Downloading: 'RabbitMQ for PCF' to file: '/tmp/build/get/p-rabbitmq-1.7.13-alpha.7.pivotal'
 752.04 MB / 788.60 MB [=========================================>--]  95.36% 3s
2017/02/17 19:18:06 Download failed: failed during retryable request: failed to write file during io.Copy: read tcp <IP_ADDRESS>:42940-><IP_ADDRESS>:443: read: connection reset by peer
ERROR: failed during retryable request: failed to write file during io.Copy: read tcp <IP_ADDRESS>:42940-><IP_ADDRESS>:443: read: connection reset by peer

Hrm, interesting. @dannysullivan any ideas? I think 0.30.3 should've had the fix.

On 0.30.7, we see the same behavior. What's most interesting is that the RST (in our environment as I observe it) is happening because the TCP window on the client side has dropped to zero and never seems to open back up. The proxy with which the resource is communicating ends the connection because of a zero window size timeout.
To flesh out the details a little more, the TCP window is the number of bytes that whoever sent the ACK packet can receive in subsequent packets. Watching TCP dumps, we see that the GO client establishes several connections outbound and transfers data as normal. Monitoring ACKs packets, we see it hits a point where the TCP window size goes from 65535 to zero over a handful of packets across all of the connections. Timeout seconds later, the loadbalancer closes the connection.
At first blush, this would appear to be an issue with the Downloader hanging or failing to pull data from the socket.

I'll poke around at trying to create a reproduction recipe, but I'm not sure how much flexibility I have in changing what the resource reaches out to. Pointers greatly welcomed.

@DRuggeri we just made some changes to our cache invalidation settings in Cloudfront, which we suspect was the root cause of this issue - please let us know if you're still seeing download failures.

That seems to have fixed it, actually. I'm mighty curious what the change was.

@DRuggeri we increased the Default TTL in our cache settings in Cloudfront - we were only seeing this error while downloading very large files, and our suspicion is that the cache would time out at some point in the download and interrupt the process.
I'll close this issue now, and we'll dive deeper into the problem if it resurfaces in the future.

@dannysullivan, I guess I was mistaken when I said this resolved the issue. I immediately had two successful downloads of large files, but that was apparently not nearly a large enough samples. I've had two failures since then.
I've updated my pipeline to attempt up to 50 times and will report back how many times it takes to succeed with the 2.45Gb opsman ova file.

Please reopen this issue, it is still a problem.

I can't view that story, but FWIW, I just had 50 failures to download the ERT tile which sucked up quite a bit of time.
upgrade-tile #26
started	1h 23m ago
finished	2m 18s ago
duration	1h 21m

@DRuggeri @haydonryan Are you still seeing this issue? We coordinated with Cloudfront support and made some changes to our configuration that have drastically reduced the number of errors we're seeing in our logs.

Closing because this seems to be resolved.

This happened this morning:
2017/06/20 09:53:52 PivNet Resource version: 0.31.0
2017/06/20 09:53:52 Creating download directory: /tmp/build/get
2017/06/20 09:53:52 Getting release for product slug: 'isolation-segment' and product version: '1.11.0'
2017/06/20 09:53:52 Accepting EULA for release with ID: 5803
2017/06/20 09:53:52 Getting product files
2017/06/20 09:53:53 Getting file groups
2017/06/20 09:53:53 Getting release dependencies
2017/06/20 09:53:53 Getting dependency specifiers
2017/06/20 09:53:54 Getting release upgrade paths
2017/06/20 09:53:54 Getting upgrade path specifiers
2017/06/20 09:53:54 Downloading files
2017/06/20 09:53:54 Filtering download links by glob
2017/06/20 09:53:54 Downloading filtered files
2017/06/20 09:53:54 Downloading: 'PCF Isolation Segment' to file: '/tmp/build/get/p-isolation-segment-1.11.0-build.61.pivotal'
 1.59 GB / 1.74 GB [==========================================>----]  91.31% 10s
2017/06/20 09:54:05 Download failed: failed during retryable request: failed to write file during io.Copy: read tcp <IP_ADDRESS>:35172-><IP_ADDRESS>:443: read: connection reset by peer
ERROR: failed during retryable request: failed to write file during io.Copy: read tcp <IP_ADDRESS>:35172-><IP_ADDRESS>:443: read: connection reset by peer

Thanks Pierre - we'll look into it.
On Tue, Jun 20, 2017 at 6:05 PM, Pierre Delagrave<EMAIL_ADDRESS>wrote:

This happened this morning:
2017/06/20 09:53:52 PivNet Resource version: 0.31.0
2017/06/20 09:53:52 Creating download directory: /tmp/build/get
2017/06/20 09:53:52 Getting release for product slug: 'isolation-segment' and product version: '1.11.0'
2017/06/20 09:53:52 Accepting EULA for release with ID: 5803
2017/06/20 09:53:52 Getting product files
2017/06/20 09:53:53 Getting file groups
2017/06/20 09:53:53 Getting release dependencies
2017/06/20 09:53:53 Getting dependency specifiers
2017/06/20 09:53:54 Getting release upgrade paths
2017/06/20 09:53:54 Getting upgrade path specifiers
2017/06/20 09:53:54 Downloading files
2017/06/20 09:53:54 Filtering download links by glob
2017/06/20 09:53:54 Downloading filtered files
2017/06/20 09:53:54 Downloading: 'PCF Isolation Segment' to file: '/tmp/build/get/p-isolation-segment-1.11.0-build.61.pivotal'
1.59 GB / 1.74 GB [==========================================>----]  91.31% 10s
2017/06/20 09:54:05 Download failed: failed during retryable request: failed to write file during io.Copy: read tcp <IP_ADDRESS>:35172-><IP_ADDRESS>:443: read: connection reset by peer
ERROR: failed during retryable request: failed to write file during io.Copy: read tcp <IP_ADDRESS>:35172-><IP_ADDRESS>:443: read: connection reset by peer
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pivotal-cf/pivnet-resource/issues/66#issuecomment-309905272,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOShk0ZsCWsgv4W38bXtOFcS4j--d5ECks5sGEIegaJpZM4L6J7_
.

--
Jim Thomson
Product Manager
<EMAIL_ADDRESS>917-538-9502

@jimbosity What about resuming the download with a new http request when this happen? Granted that won't fix the root cause but at that point it could be an acceptable solution given the amount of time spent on trying to fix it.


Validating nested params

Hey,
It doesn't seem to be possible to validate nested params at the moment. I was hoping this syntax would work:
params do
  param :job do
    param :title, presence: true
  end
end

Resolved by #71


Calls that are NOT permitted NOR blocked are NOT being answered

If a number calls in that is neither on the permitted list nor the blocked list are categorized as "Screened:not found". Here are the screened lines from the config file I am using:
SCREENED_ACTIONS = ("answer", )
#SCREENED_GREETING_FILE = "resources/general_greeting.wav"
SCREENED_RINGS_BEFORE_ANSWER = 0
My modem doesn't do voice. So what I want to happen is for these calls to be answered and immediately hung up on. I thought that "answer" alone would do that. It does that for "blocked" calls. But the phone keeps ringing until it goes into my telecom's voice mail.
In looking at the log below it appears that the code is trying to initiate the go off hook but this isn't being seen/acted upon by the modem for some time. Any idea why this might be the case?
Thanks

I think I found out... Being in the USA, nomorobo was being used. For whatever reason, perhaps it was not working or taking too long, the problem went away when I removed it from the config file. Thanks


Don't escape zsh prompt

This would result in a literal \ being printed on the prompt.

This was resolved in https://github.com/milkbikis/powerline-shell/pull/150. Sorry this didn't get merged. This project kind of fell stale for awhile.