Engineering Checklist for Onboarding James

New Engineer Onboarding Checklist
Special Notes

[x] Paste a link to the general onboarding ticket, which includes the onboarding authorization, here: https://github.com/cloud-gov/product/issues/3109

Complete additional cloud.gov trainings

    Federal employees and staff contractors, expand this section. Not applicable to project contractors.

Engineers who are federal employees or staff contractors have a Contingency Plan role and may participate in Incident Response, so they must complete the CP and IR trainings. Project contractors do not need to complete these trainings. Check one of the following:

[ ] Coordinate with your onboarding buddy to schedule Contingency Planning training within 60 days. (and annually after that). This will cover the following document, which you should also review before or after training:

[ ] Read the Contingency Plan.

[ ] Coordinate with your onboarding buddy to schedule Incident Response Training within 60 days of joining the team (and annually after that). This will cover the following document, which you should also review before or after training:

[ ] Read the Incident Response Guide.

Slack channels
Project contractors: Your buddy will add you to the private channel for your project.

    Federal employees and staff contractors, expand this section:

Your onboarding buddy will add you to these Slack channels:

[ ] #cg-aws-security - private channel where bots post security notices
[ ] #cg-billing - private business development channel (if applicable)
[ ] #cg-incidents - private channel for incident response
[ ] #cg-ops-banter - private channel for operations/engineering banter
[ ] #cg-priv-compliance - private channel for security and compliance discussions

Google Groups

    Federal employees and staff contractors, expand this section:

[ ] cloud.gov AWS
[ ] cloud.gov Notifications (🗣)
[ ] cloud.gov Operations
[ ] cloud.gov Security
[ ] cloud.gov Support (🗣)

Channels marked with (🗣) receive a lot of messages, either from customers or bots, and you may want to mute them.

Learn our policies and procedures
In addition to the topics in the trainings section, review the following documents:

[x] Review the cloud.gov open source policy guidance about protecting sensitive information.
[ ] Read the Continuous Monitoring Strategy, particularly the cloud.gov team responsibilities.
[ ] Read the Configuration Management Plan.
[x] Read the cloud.gov Security Policies and Procedures. These documents explain the high-level policies and procedures we must comply with while running cloud.gov, sorted into security control "families" They explain that we follow GSA IT security policy, and they provide a summary of the procedures in our System Security Plan.
[x] Review the System Security Plan (the latest version lives on Google Drive; look for "cloud.gov System Security Plan (SSP)" as a .docx file). Of particular note for onboarding: Section 9 (System Description) and Section 10 (System Environment)
[x] Review the team's Engineering Practices. Some of these are mandatory because they fulfill FedRAMP requirements.

Getting to know cloud.gov
Resources on cloud.gov:

[x] View the video: A Technical Overview of cloud.gov
[x] Read the Delivery Process document to learn about how we work.
[ ] Read our service disruption guide to learn how we handle customer-facing service disruptions.

Resources on CloudFoundry/BOSH:

[x] Look at Opensourced content for cloud foundry training classes: zero to hero (beginner), bosh/operator, and microservices
[x] Here is some training materials: GitHub - CloudCredo/training-operating-the-foundry: Training materials for Operating a Platform: BOSH and Everything Else
[x] Very thorough documentation on BOSH: Ultimate Guide to BOSH
[x] BOSH 101 presentation recording and slides

Getting hands-on with cloud.gov:

[x] Sign up for a cloud.gov sandbox using your GSA email address and start experimenting to get familiar with the basics of the PaaS from a user's perspective.

This is also required in order to make you a platform admin once you've completed the Cybersecurity and Privacy training.

Engineering-specific items
Machine admin rights

[x] In order to install development tools on your Mac, you will need to request local admin rights by submitting a ServiceDesk ticket using this justification. If you're unable to create a ticket for yourself, your onboarding buddy can create one for you.

Engineering account management
Before starting this section, you must complete:

GSA IT Security & Privacy Awareness Training
Role-based trainings listed under Learn our policies and procedures

[ ] (Waiting on seats) Add them as an agent to the cloud.gov support Zendesk (Ask a cloud.gov member with admin access to Zendesk to add them).

N/A ~AWS user names should be identical across accounts so that permissions can be correctly managed by Terraform.~

N/A ~Create AWS Accounts by following these instructions. These accounts should be setup as read-only at the start, and once the 3 mandatory cloud.gov trainings are complete they will be switched to full admin accounts and added to the audit input file:~

N/A ~AWS Commercial accounts~
N/A ~AWS GovCloud accounts~
N/A ~Ensure new person creates a 55-day Google Calendar reminder to update passwords, which expire every 60 days~

N/A ~Add them to Nessus Manager via the GUI~

N/A ~Add them to the ScanAdmins team in Settings > Groups~

N/A ~You are a member of the Cloud Operations team, which means you have additional administrative permissions:~

N/A ~Make them an admin](https://cloud.gov/docs/ops/managing-users/#managing-admins) of the platform.~
N/A ~Add them to the platform-ops team in GitHub.~
N/A ~Add them as an admin on the cg-django-uaa docs~
N/A ~Add them to our dockerhub org and ensure we're not over our license count~
N/A ~Add them as Technical users to Ubuntu Advantage (Admin users for leads and supervisors)~

Additional compliance setup/review

[x] Install caulking git leak prevention by following the README
[x] Verify caulking by running make audit and pasting a screenshot as a comment on this GitHub issue
[x] Set GPG signing set up for GitHub (instructions here) and paste the output of git config commit.gpgsign as a comment on this GitHub issue

Install a development environment for cloud.gov

Note: Make sure you have followed the instructions in Machine admin rights at the top of this section to get local admin rights on your machine before moving forward

[x] Install Homebrew (brew)
[ ] Clone the product repo, cd into it, and run brew bundle install to install everything in Brewfile.
[ ] Verify CloudFoundry installation via the CLI (once an existing cloud.gov teammate has made your cloud.gov admin account)

cf login -a api.fr.cloud.gov --sso
cf orgs

As a cloud.gov team member, you should have a long list of organizations
If you have none or one (e.g. sandbox) org, please reach out to your onboarding buddy

N/A ~Configure aws-vault by following our directions~
N/A ~Fix fly, the Concourse CLI, by running xattr -d com.apple.quarantine $(brew --prefix)/bin/fly. Concourse does not sign fly with an Apple Developer account, so you must use xattr to manually remove the binary from quarantine. Verify by running fly -h in your command line.~
N/A ~Install cloud.gov dev tools by cloning the cg-scripts repo: run git clone https://github.com/cloud-gov/cg-scripts.git in your command line~

Figure out your first tasks
Project contractors: Check in with your project lead about first tasks.
Federal employees and staff contractors, expand this for instructions:
The engineering team currently contains the following squads, each with their own projects:

Assurance, which focuses on security and compliance
Platform, which maintains and improves cloud.gov, focusing on internals like our AWS architecture and Cloud Foundry
Customer Success, which focuses on customer-facing features like service brokers and observability tools

If you are not already assigned to a particular squad, work with your onboarding buddy to join squad standups and learn what each squad is working on.
Assurance-specific items
These items are only mandatory for someone stepping into an Assurance squad role, but you are welcome to subscribe even if you are on another squad:

[x] Subscribe to CISA alerts/updates: https://www.cisa.gov/about/contact-us/subscribe-updates-cisa
[x] Subscribe to FedRAMP mailing lists: https://public.govdelivery.com/accounts/USGSA/subscriber/topics?qsp=USGSA_2224
[ ] Read Compliance Lead documents at root of the Google Drive Security and Compliance folder

NOTES:
1.
Clone the product repo, cd into it, and run brew bundle install to install everything in Brewfile.
Error: homebrew/cask-versions was deprecated. This tap is now empty and all its contents were either deleted or migrated.
Tapping homebrew/cask-versions has failed!
2.
The following links resolve to resources that have moved:

Read the Continuous Monitoring Strategy, particularly the cloud.gov team responsibilities.
Read the Configuration Management Plan.
Read our service disruption guide to learn how we handle customer-facing service disruptions.

Would be useful to have this link added to the git setup since ssh is required: https://handbook.tts.gsa.gov/tools/github/#2-set-up-local-git-configuration


PubID 1.0: "-l" after part not related to any PubID element

for NBS SP 535v2a-l "-l" is not described in PubID 1.0, I cannot find what this element could be.
Originally posted by @mico in https://github.com/metanorma/pubid-nist/issues/153#issuecomment-1516605082

Now -l parsed as part of "volume".


HDDS-3868. Implement getTrashRoot and getTrashRoots in o3fs

What changes were proposed in this pull request?
Override the default Hadoop FS impl.
Currently o3fs moves trash under:
o3fs://bucketName.volumeName.om/user/userName/.Trash/Current/...

New trash location will be:
o3fs://bucketName.volumeName.om/.Trash/userName/Current/...

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3868
How was this patch tested?
Added a simple test testGetTrashRoot.

Thanks @xiaoyuyao  for the review. Will commit shortly.


refine conv doc

完善Conv1D/Conv2D/Conv3D/Conv1DTranspose/Conv2DTranspose/Conv3DTranspose 文档
新增权重shape说明

the Docs-NEW stucked on paddle.to_tensor function in the Conv1D's sample codes.
and I run it on another xly machine, stucked too.
paddle.utils.run_check() is also stucked.
the xly machine's driver version is 450.66, V100.
but i run the code successfully on a dev-machine, driver 460.27.04,T4.


Add sideEffects: false to react-router-dom package.json

Webpack 4.0 introduced support for a sideEffects flag in a project's package.json: https://webpack.js.org/guides/tree-shaking/#mark-the-file-as-side-effect-free. This is awesome because we can now get Webpack's tree shaking to work as intended for most, if not all projects. 🎉
I've noticed that in my projects where I've used react-router-dom, the recommended import syntax (eg. import { Route } from 'react-router-dom') still pulls in the entire library. While react-router-dom and it's associated packages aren't that large, I'm a bit of a performance junkie 😃. All this PR does is add the sideEffects: false flag to the react-router-dom package. I created a simple test repo to demo the effects of this flag: https://github.com/taylorc93/react-router-test. I'm noticing ~20KB of minified JS removed from my bundle as a result of this change.
 From what I can see, there aren't any, but I could definitely be missing something. Let me know what you think / if there's anything else you need from me to get this merged!
Side note: Love this project, I've been using it for years and it's worked fabulously. Keep up the great work!

Can we add this to the other packages as well? I put it on Redux as well. It doesn't really hurt, since we don't modify globals.

@timdorr All set

Thanks!


Add unit tests to cover all possible errors raised.

We need to make sure that any method that raises an error has a test for it where it actually raises an error.

Top level classes:
package counters
manager.go:CreateDomain()
manager.go:DeleteDomain()
manager.go:GetDomains()
manager.go:AddToDomain()
manager.go:DeleteFromDomain()
manager.go:GetCountForDomain()
package server
server.go:handleTopRequest() // http.error
server.go:handleTopDomainRequest() // http.error
server.go:ServeHTTP() // http.error
package storage
manager.go:newManager()
manager.go:Create()
manager.go:SaveData()
manager.go:LoadData()
manager.go:getFileFromCache()
manager.go:loadAllInfo()
manager.go:SaveInfo()

also under package counters/wrappers all methods that raise an error

great job can you start writing tests for those?

Yeah sure
Am 14.08.2015 1:47 vorm. schrieb "Seif Lotfy"<EMAIL_ADDRESS>
great job can you start writing tests for those?
—
Reply to this email directly or view it on GitHub
https://github.com/seiflotfy/counts/issues/31#issuecomment-130888999.


conmon needs to support --detatch and non --detach mode

In kpod exec we want to maintain the tty with the container.
Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

@bot retest please

Red Hat CI and centos aren't happy, but neither have any details to click through to check?

Closing since I opened this PR in CRI-O.


No content in the webui

Hi, I have the same issue as here: https://github.com/ipfs-shipyard/ipfs-webui/issues/157
I have added the API settings and listen port as on that post, and I can load the webui, but it contains no info.
It is running on a headless server
Initializing daemon...
Adjusting current ulimit to 2048...
Successfully raised file descriptor limit to 2048.
Swarm listening on /ip4/<IP_ADDRESS>/tcp/4001
Swarm listening on /ip4/<IP_ADDRESS>/tcp/4001
Swarm listening on /ip6/::1/tcp/4001
Swarm listening on /p2p-circuit/ipfs/QmNpprVJP3beQkmX2VGB5K9hVtsEuDHtZ9YTLK1HUentME
Swarm announcing /ip4/<IP_ADDRESS>/tcp/4001
Swarm announcing /ip4/<IP_ADDRESS>/tcp/4001
Swarm announcing /ip6/::1/tcp/4001
API server listening on /ip4/<IP_ADDRESS>/tcp/5001
Gateway (readonly) server listening on /ip4/<IP_ADDRESS>/tcp/8080
Daemon is ready

Hello @djh82uk! In which address are you accessing Web UI?

Hi, I am using http://<IP_ADDRESS>:5001/webui

@djh82uk you need to use localhost:5001, it is the only address that is whitelisted (<IP_ADDRESS> also doesn't work)

Hi, I edited the config to allow connections from other than localhost.  It's a headless server so accessing from localhost is not an option.  The API is also set to listen on the network IP

Anyone got any thoughts on this? I can't be the only one running it on a headless server?

i have running both  ui and daemon locally, still can't connect

Editing config is not enough -- AFAIK it is hardcoded to localhost.
See:

https://github.com/ipfs-shipyard/ipfs-webui/issues/591
https://discuss.ipfs.io/t/how-can-i-enable-remote-connection-to-webui/698

Closing in favour of https://github.com/ipfs-shipyard/ipfs-webui/issues/836


feat: regenerate asset data 10/03/2024

Generated from CI.

Sanity test looking good! https://jam.dev/c/7db6d8bb-75e0-4927-b318-ef00b15176c5


Seedset protoclass

Adressing issue #16 : adding seedset functionality to last outstanding prototype function 'protoclass'

Coverage remained the same at 100.0% when pulling 57a45a09a3cfc55218fd87819d3d7a06f5848d98 on sjanssen2:seedset_protoclass into ad1a2072504dc5694e08abfd1a09f91ae7e388d9 on biocore:master.

@qiyunzhu ready for a review

I cannot say that I understand this PR fully, but the code looks good!
@qiyunzhu I'm not able to merge, because I'm not a member of this project.

@tkosciol Thank you! The code is to let the prototype selection function take a pre-defined set of "seeds", which are guaranteed to be selected as prototypes. The remaining prototypes will be calculated based on them.

Hi @qiyunzhu I never replied to your question. You are right: elements of the seedset are made prototypes in a random ordering until all are "consumed".
Since at least |seedset| elements will be returned as prototypes (even if the user set num_prototypes to a smaller number) the ordering should not matter.


Touch screen support

this needs touch screen support it would be so awesome. I will see what I can contribute.

Ah this sounds interesting.


Incorrect Argo CD Application Repo Path When Switching Git Servers in CD Pipeline

Description
When a CD pipeline is created and an application is added from the 'github' gitserver, the deployment works correctly. However, if the CD stage is modified to remove the application deployed from 'github' and add an application that uses 'gerrit' as the gitserver, the Argo CD application repo path remains incorrect. The path still points to the 'github' repository instead of updating to the 'gerrit' repository. This bug needs to be researched and fixed.
Steps to Reproduce

Create a CD pipeline and add an application from the 'github' gitserver.
Deploy the pipeline and verify the deployment works correctly.
Modify the CD stage to remove the application deployed from 'github'.
Add an application that uses 'gerrit' as the gitserver.
Observe the Argo CD application repo path.

Expected Result
The Argo CD application repo path should update to point to the 'gerrit' repository when the application is changed to use 'gerrit' as the gitserver.
Actual Result
The Argo CD application repo path still points to the 'github' repository instead of updating to the 'gerrit' repository.

Issues moved to the cd-pipeline-operator


CI: fetch packages info if server tests fail

Hi, this closes #2777.
I used pip list --outdated. So basically, this script is only necessary because of the 'past X days' requirement.
see my (other) experimental branch for demo run that fails on purpose: https://github.com/tal66/elyra/actions/runs/2477060776

General question: currently the output is sorted by package name, which makes perfect sense if one wants to quickly check if one of the 'usual suspects' (packages that have broken Elyra in the past) has changed:
Newer version for <google-api-python-client>:
 - released 2.50.0  2022-06-07	(>)
 - current  1.12.11

Newer version for <google-auth>:
 - released 2.7.0  2022-06-07	(>)
 - current  1.35.0

Newer version for <google-cloud-core>:
 - released 2.3.1  2022-06-09	(=)
 - current  2.3.1

Newer version for <google-cloud-storage>:
 - released 2.4.0  2022-06-08	(>)
 - current  1.44.0

Newer version for <ipykernel>:
 - released 6.13.1  2022-06-06	(=)
 - current  6.13.1

Newer version for <jupyter-client>:
 - released 7.3.4  2022-06-08	(=)
 - current  7.3.4

Newer version for <jupyter-server>:
 - released 1.17.1  2022-06-07	(=)
 - current  1.17.1

Newer version for <jupyterlab>:
 - released 3.4.3  2022-06-07	(=)
 - current  3.4.3

Newer version for <kfp-server-api>:
 - released 1.8.2  2022-06-10	(=)
 - current  1.8.2

Newer version for <networkx>:
 - released 2.8.3  2022-06-04	(>)
 - current  2.6.3

Newer version for <notebook>:
 - released 6.4.12  2022-06-07	(=)
 - current  6.4.12

Newer version for <pipenv>:
 - released 2022.6.7  2022-06-07	(>)
 - current  2020.11.15

Newer version for <pylint>:
 - released 2.14.1  2022-06-06	(=)
 - current  2.14.1

Newer version for <requests>:
 - released 2.28.0  2022-06-09	(=)
 - current  2.28.0

Newer version for <watchdog>:
 - released 2.1.9  2022-06-10	(=)
 - current  2.1.9

However, since we are also running automated daily tests (e.g. https://github.com/elyra-ai/elyra/actions/runs/2478594976) where probably sorting the output by the most recent change date (in descending order) might be a bit more useful. Would be interested in hearing what other think.

We've discussed this in todays's dev meeting and decided to leave the report output as is for now.


Improve addressing

src/local_ip.rs was calling out to the hostname binary, which isn't a portable way of getting the local address - macOS doesn't have the binary at all and on my Linux distro hostname takes -i instead of -I. Spark uses the SPARK_LOCAL_IP environmental variable, so I used it too.
The master address and port were passed around lots of places, then later converted to a SocketAddr, it's simpler to just immediately create a SocketAddr and pass that around without needing to worry about parsing errors.
I added unit tests for the reading of the addresses, but one part that needs more attention are the couple of places where <IP_ADDRESS>:{} was hard coded as the master address, which now use the configurable value.

thanks @steven-joruk


DOC: add acetazolamide example to stats.fisher_exact

Add a realistic example to stats.fisher_exact:
Emma V. Low et al. "Identifying the lowest effective dose of
acetazolamide for the prophylaxis of acute mountain sickness:
systematic review and meta-analysis."
BMJ, 345, :doi:`10.1136/bmj.e6779`, 2012.

It also add a note with a comparison against stats.boschloo_exact to show Fisher's test's lower power and also that it assumes a double conditioning on the marginals.

In the paper they only speak in terms of odd-ratio, they don't calculate Fisher's test.

Did you see my comment about phrasing the null hypothesis in terms of the odds ratio? https://github.com/scipy/scipy/pull/17707#pullrequestreview-1235047634

Thanks @tupui!


PlatformException: InvocationTargetException - Null Object Reference in enableCamera Method for ZegoExpressEngine

Environment

Technology
Version

Flutter version
3.24.4

Plugin version
4.16.12

Android version
14.0

iOS version
-

macOS version
-

Xcode version
-

Google Chrome version
-

Device information: Samsung F15 5G
Description
Expected behavior:  Should Enable Camera when enable camera button is pressed.
Current behavior:
Throwing error:
Unhandled Exception: PlatformException(InvocationTargetException, [enableCamera] Attempt to invoke virtual method 'void im.zego.zegoexpress.ZegoExpressEngine.enableCamera(boolean, im.zego.zegoexpress.constants.ZegoPublishChannel)' on a null object reference, null, null) E/flutter (28411): #0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:648:7) E/flutter (28411): #1      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:334:18) E/flutter (28411): <asynchronous suspension> E/flutter (28411): #2      ZegoExpressImpl.enableCamera (package:zego_express_engine/src/impl/zego_express_impl.dart:1258:12) E/flutter (28411): <asynchronous suspension> E/flutter (28411): #3      ZegoExpressEngineDevice.enableCamera (package:zego_express_engine/src/zego_express_api_device.dart:278:12) E/flutter (28411): <asynchronous suspension> E/flutter (28411): #4      ZegoUIKitCore.turnOnLocalCamera (package:zego_uikit/src/services/internal/core/core.dart:881:5) E/flutter (28411): <asynchronous suspension> E/flutter (28411):
Steps to reproduce

class CallPage extends StatefulWidget {
  const CallPage({Key? key}) : super(key: key);

  @override
  State<StatefulWidget> createState() => CallPageState();
}

class CallPageState extends State<CallPage> {
  @override
  Widget build(BuildContext context) {
    return SafeArea(
      child: ZegoUIKitPrebuiltCall(
          appID: KeyCenter.instance.appID /*input your AppID*/,
          appSign: KeyCenter.instance.appSign /*input your AppSign*/,
          userID:
              "${Provider.of<ProfileViewModel>(context, listen: false).profile?.id}",
          userName:
              "${Provider.of<ProfileViewModel>(context, listen: false).profile?.firstName}",
          callID: 'call',
          config: ZegoUIKitPrebuiltCallConfig.oneOnOneVideoCall()

            /// support minimizing
            ..topMenuBar.isVisible = true
            ..topMenuBar.buttons = [
              ZegoCallMenuBarButtonName.minimizingButton,
              ZegoCallMenuBarButtonName.showMemberListButton,
              ZegoCallMenuBarButtonName.soundEffectButton,
            ]),
    );
  }
}

Open above page
Clicked on Camera Icon to enable camera.
Thrown this error.

Did you enter the wrong app ID or app sign?

Did you enter the wrong app ID or app sign?

Yes sorry for late update i have given the appsign key wrong. Now its working we can close the case.


docs: fix the data-deep-link-smudge-delay attribute in the tabs example

Closes https://github.com/zurb/foundation-sites/issues/10090

Please do the same for

https://foundation.zurb.com/sites/docs/accordion.html
I already changed it in the past afaik.
https://github.com/zurb/foundation-sites/commit/5aa4b9296c37050d8274f57d3ac898c94bf384a6#diff-8330a7afbe207dd8500be047b28255fb

Ah sorry, I was on the wrong branch. Thank you.


Insert subcircuit button still visible even if there are no subcircuits

Describe the bug
A clear and concise description of what the bug is: When there are no SubCircuits there shouldn't be a button to Add SubCircuit as it may be confusing to first time users.
Similiar behaviour is observed when trying to open offline projects.
To Reproduce
Steps to reproduce the behavior:

Go to https://circuitverse.org/simulator
Click on Circuit -> Insert Subcircuit
See error

Expected behavior
If there are no subcircuits or offline projects, no button indicating Insert SubCircuit or Open Project should be visible respectively.
Screenshots

Desktop (please complete the following information):

OS: Ubuntu
Browser: Chrome
Version: 18.04

Are you working on this issue? (Yes/No)
Yes

As far as this issue is concerned , the button is not clickable so that will not create a confusion but disabling it will be good.

Yes! button is non clickable but when i first time used simulator i was a bit confused what this button is for if there are no offline projects :)


Potential for numerous files to be missed on indexing

This is a multi (at least 2) tiered issue.

Spoons handling of finding source directories defined in pom.xml needs to be improved. Two issues found:

If a module/pom file doesn't specify <sourceDirectory> and/or <testSourceDirectory>, it falls back to a default for whichever were missing (src/main/java and src/test/java respectively), even if they would be defined in an ancestor up the pom hierarchy. This issue at the time of writing has been addressed locally, PR incoming soon:tm:
Ref: POM inheritance
Spoon doesn't interpolate ${project.basedir}, which was encounted in some repos. PR mentioned above will also address this.

Theory: in multi-maven-project scenarios (>1 pom.xml file in a repo), in root pom files that don't act as aggregators (aka don't define a <module> block), maven projects that aren't the root project would be missed, and therefore not indexed. This could be addressed in lsif-java itself by comparing the discovered-by-Spoon projects and comparing it to the discovered-by-filesystem-tree-walking pom.xml files/projects, and adding the missing projects to the Spoon model's input resources.
Ref: POM aggregation

PR created @ https://github.com/INRIA/spoon/pull/3562

@Strum355 is this still relevant after switching away from Spoon?

Closing this since it's no longer relevant


Switch garage stuff to alerts instead of a trigger

See the following from a conversation:

@Noke the reminder that the garage is open will only fire once.. mybe put those phones in a group to avoid duplicating code. might want to take a look at https://home-assistant.io/components/alert/

this is what I use to remind me my coffee pot is on https://hastebin.com/pifavojeru.vbs

using mqtt from opengarage and this is much more reliable now.


Pretrained SCNN

Thank you for code. If I understand correctly code you realized SCNN from https://arxiv.org/pdf/1712.06080.pdf in lane-detection-model folder. Do you have pretrained model for tensorflow? Can you share that?

@mikeedi , the total training epochs are 9 w. Currently, I have not tested other learning rate schemes.

@cardwing : Mentioning training episodes 9w means is it 9 Weeks ? is my interpretation right ?
Are you utilizing the GPUs for training?

@chokkarapu , 90 k episodes. Besides, I use GPUs to accelerate training.

Typically, it will take 2~3 days to train SCNN on my own machine (GeForce GTX TITAN X).

@mikeedi , @chokkarapu , please use the latest code since I have found that using sgd+momentum can make the model converge much faster than pure sgd.

Typically, it will take 2~3 days to train SCNN on my own machine (GeForce GTX TITAN X).

Great....Thats good to hear...what is your GPU memory size in terms of GB?

12 GB.


Refactor interaction of service config process.

In GitLab by @liyanq528 on Nov 15, 2017, 17:43

In GitLab by @sokril on Nov 8, 2019, 07:41
fix with pr#616

In GitLab by @wknet123 on Nov 8, 2019, 07:41
Closing it as fixed.

In GitLab by @sokril on Nov 8, 2019, 08:14
closed

In GitLab by @sokril on Nov 8, 2019, 08:14
assigned to @sokril


Update app_tr.arb

Fixing translation error

Thank you. Can you change the target branch to feature/v2.1.0. this is our next release branch.


process_request_headers does not have access to the request body

Sometimes the request header depends on the body. I propose adding an override-able function def process_request_headers(header, body), do: headers. It would require only minimal change here:
https://github.com/myfreeweb/httpotion/blob/c79314b91df2cc8e43835b509efd682820d87fb4/lib/httpotion.ex#L149
and could be used in parallel with process_request_headers/1 much likedef process_response_body(body) and def process_response_body(_headers, body) do today.

oh yeah, we can do that in a backwards compatible way, cool. Do you want to send a pull request for this?

yep! https://github.com/myfreeweb/httpotion/pull/128

merged.
By the way, GitHub can auto close issues if you say "fixes #number" in a PR description or commit message :)


Add LdapConfig to type+doc structure of LdapService soft-config

I think this is a helpful pattern for our non-trivial xh soft-configs, especially ones like this with an internal data structure (servers).
Left as draft because I haven't run the code yet to test. I'm thinking we should sort out how to enable LdapService for Toolbox using our Azure Entra instance - does that make sense to you guys?  Is that anything we've already tried as part of overall LdapService development?

Wowzers
Seems very promising/helpful.

FYI my intention is still to get this merged.  I want to find a good way to test it locally - looking at https://hub.docker.com/r/bitnami/openldap


Resolve the Flaky Test - TestWaitCustomTask_PipelineRun

Changes
Fix #5653
I'm openning this PR as a tentative solution to address #5653:
TL;DR: TestWaitCustomTask_PipelineRun/Wait_Task_Retries_on_Timeout has been flaky for a while. This PR stops the PipelineRun reconciler from cancelling Run when it detects that the task-level Timeout configured for the Run has passed, which will address the flake (similar to https://github.com/tektoncd/pipeline/pull/5134 which addresses TestPipelineRunTimeout).
Some other useful information, many thanks to @abayer, @lbernick and @jerop:

Run should only be canceled when

The PipelineRun as a whole has timed out, either due to PipelineRun.Spec.Timeout's value or PipelineRun.Spec.Timeouts.Pipeline's value.
It's a non-finally PipelineTask, PipelineRun.Spec.Timeouts.Tasks is set, and that value has elapsed.
It's a finally PipelineTask, PipelineRun.Spec.Timeouts.Finally is set, and that value has elapsed.

For TaskRun, pipelinerun reconciler don't cancel it when it times out.

This change only applies to task-level Timeout, i.e. when PipelineTask.Timeout is set for a Run.
cc @pritidesai  Will this commit have any other side effect?

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Has Docs included if any changes are user facing
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[x] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
ACTION REQUIRED: Starting from this release, Custom Task Runs controllers need to implement the `Timeout` on your own,  PipelineRun reconciler would not set `Run.Spec.Status == RunCancelled` upon Run timeout.

/kind flake

Run should only be canceled when its uplevel PipelineRun is timed out

A clarification: a Run is cancelled for timing out when any of the following are true:

The PipelineRun as a whole has timed out, either due to PipelineRun.Spec.Timeout's value or PipelineRun.Spec.Timeouts.Pipeline's value.
It's a non-finally PipelineTask, PipelineRun.Spec.Timeouts.Tasks is set, and that value has elapsed.
It's a finally PipelineTask, PipelineRun.Spec.Timeouts.Finally is set, and that value has elapsed.

Appreciate all the info @jerop! Updated the PR description and release note.

/test tekton-pipeline-unit-tests
cloud events flake

@jerop and @XinruZhang I was wondering, without this feature how will custom task controller "reconcile" and take action on timed-out task. Basically, this would cause that trigger.

Hi Prashant, thanks for keeping eye on this issue!
If the Run controller handles the timeout correctly -- mark the Run as Failed on timeout, then we wouldn't have any problem.
If the Run controller doesn't implement the TimeOut functionality, the entire PipelineRun will eventually fail on pipeline-level timeout.

Hi Xinru,
Thanks!, that part is understood. Suppose a custom task is performing an action and is stuck for some reason. The custom task controller will not get to "reconcile" it until it is updated in someway.
The reconcile is triggered not periodically but whenever there is an update. I need to test this out, to be sure.

Oh I see, great point! After thinking more about it, I think that would be a concern of Custom Run controller right? A custom controller can requeue a key after a period of time, similar to
https://github.com/tektoncd/pipeline/blob/db4c05c0294ad33a2f6e7b17cacf53526139616d/test/custom-task-ctrls/wait-task/pkg/reconciler/reconciler.go#L108-L116

Is this scalable? when number of objects are large. Do you think the overhead of examining a large number of run object by custom task controller, every object's "timeout time" can impact performance?


Activate Open Collective

Supersedes #489, fixes #1105.

This is probably enough to get started. I also added the "sponsors" buttons on GitHub. Closing this.


Health checks

Updated OSU BW test to run in parallel with PBS, added stream test, and updated readme to explain how to run it.

@JonShelley we discussed this already with @garvct and @kanchanm on how to organize these heathchecks. Please move the OSU script in to the /apps/osu directory the healthchecks should run these and do checkings of the returned value based on the SKU size.

@JonShelley we discussed this already with @garvct and @kanchanm on how to organize these heathchecks. Please move the OSU script in to the /apps/osu directory the healthchecks should run these and do checkings of the returned value based on the SKU size.

I'm not sure I understand. The changes I made were to run the ring test in parallel using a HPC image and PBS. This is a health check in my mind and is in the right location. Am I missing something? @kanchanm  and @garvct , thoughts?


MB-8577 Devseed refactor to better support sub-scenarios

Description
Sub-scenarios are a recent addition to the generate-test-data script we use to seed our database. This PR refactors, cleans up and introduces a new pattern on how to seed the database in the devseed.go file. It should now be "easier" to add in a new sub-scenario, run a single sub-scenario and hopefully organizes the different seed data as we continue to add more cases.
I figured I start with the devseed.go file since that's the one we're using to seed local data during development. The other scenario files e2ebasic.go and bandwidth.go are used for other cases.
Reviewer Notes
Is there anything you would like reviewers to give additional scrutiny?

I moved out the functions that helped seeded the database into the shared.go file since the functions were acting as helpers
There is a new file subscenarios.go that stores all the subscenario functions that is added to the devseed list. Originally, I wanted to create a new sub-directory to keep things a bit more organize but ran into a circular reference when trying to clean up the different functions being used in the different named scenarios. So for now, we have the subscenarios.go file in the scenario directory.

Setup
Add any steps or code to run in this section to help others prepare to run your code:
Reset and migrate your local database
make db_dev_reset db_dev_migrate

Clear out binary and regenerate generate-test-data
rm -rf ./bin
make bin/generate-test-data

Run script. We'll use shipment_hhg_cancelled sub-scenario as an example. The full list can be found here.
generate-test-data --named-scenario="dev_seed" --named-sub-scenario="shipment_hhg_cancelled" --db-env="development"

You can check if the seeded data is present by running the app as a TOO:
make server_run
make office_client_run

Code Review Verification Steps

[ ] Code follows the guidelines for Logging
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
Wiki

Messages

:book:
:link: MB-8577

  Generated by :no_entry_sign: dangerJS against 36e030c2f364c7af5db1e8af9c6ccd245b36012f

These changes look good to me. I ran it and it works as stated. I really like having the functions that create the data being in a shared file. It makes the devseed.go file much easier to work with. Two comments:

Can you update https://github.com/transcom/mymove/wiki/Test-Data-Generation#updating-scenarios with info on where things should be added/updated?
It looks like you added error handling to some of the functions, which is surfacing some issues with createPPMWithPaymentRequest and createPPMReadyToRequestPayment (invalid status transitions). I'm not sure if that should be fixed before this gets merged or if those would be better to comment out in this pr and have a followup to get in there and properly fix them.

Just updated the wiki and fixed those two seed data functions! Thanks!

One issue I noticed is that some scenarios don't create the required users. For example, subScenarioHHGOnboarding doesn't create office users. Can we make sure all subscenarios create the appropriate users?

One issue I noticed is that some scenarios don't create the required users. For example, subScenarioHHGOnboarding doesn't create office users. Can we make sure all subscenarios create the appropriate users?

Okay, each sub-scenarios will have office users now. I also updated the Makefile for the db_dev_e2e_populate and db_dev_fresh to take in a variable DEVSEED_SUBSCENARIO to specify the sub-scenarios. We can run it like so:
DEVSEED_SUBSCENARIO=shipment_hhg_cancelled make db_dev_e2e_populate

Sweet. Thanks! I tested it and it's working as expected.


Failed to establish HTTP/2 connection.. - 0.3.10

Hi,
I've updated to 0.3.10 as I was experiencing the download issues where it would 'finish' at a random percentage occasionally however it looks like I'm unable to get it to fetch now. I've attached the output from upgrading and what happens when attempting to pull for new dataset.
PS D:\HIBP> dotnet tool update --global haveibeenpwned-downloader --version 0.3.10 Tool 'haveibeenpwned-downloader' was successfully updated from version '0.2.8' to version '0.3.10'.
PS D:\HIBP> haveibeenpwned-downloader  "D:\HIBP\pwnedpasswords_ntlm1" -n -o
Hash ranges downloaded: 0%
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #7 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #8 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #9 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
System.Net.Http.HttpRequestException: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection.
  at void System.Net.Http.HttpConnectionPool.ThrowGetVersionException(HttpRequestMessage request, int desiredVersion)

  at async ValueTask<HttpResponseMessage> System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, bool async, bool doRequestAuth, CancellationToken cancellationToken)

  at async ValueTask<HttpResponseMessage> System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, bool async, CancellationToken cancellationToken)

  at async ValueTask<HttpResponseMessage> System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, bool async, CancellationToken cancellationToken)

  at async Task<HttpResponseMessage> System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, bool disposeCts, CancellationTokenSource pendingRequestsCts,

CancellationToken originalCancellationToken)

 at async Task<TResult> Polly.Retry.AsyncRetryEngine.ImplementationAsync<TResult>(Func<Context, CancellationToken, Task<TResult>> action, Context context, CancellationToken cancellationToken, ExceptionPredicates shouldRetryExceptionPredicates,

ResultPredicates<TResult> shouldRetryResultPredicates, Func<DelegateResult<TResult>, TimeSpan, int, Context, Task> onRetryAsync, int permittedRetryCount, IEnumerable<TimeSpan> sleepDurationsEnumerable, Func<int, DelegateResult<TResult>, Context,

TimeSpan> sleepDurationProvider, bool continueOnCapturedContext)

at async Task<TResult> Polly.AsyncPolicy'1.ExecuteAsync(Func<Context, CancellationToken, Task<TResult>> action, Context context, CancellationToken cancellationToken, bool continueOnCapturedContext)

  at async Task<Stream> PwnedPasswordsDownloader.GetPwnedPasswordsRangeFromWeb(int i, bool fetchNtlm) in /_/src/HaveIBeenPwned.PwnedPasswords.Downloader/Program.cs:187

  at async Task PwnedPasswordsDownloader.ProcessRanges(Settings settings) in /_/src/HaveIBeenPwned.PwnedPasswords.Downloader/Program.cs:227

  at async Task PwnedPasswordsDownloader.ProcessRanges(Settings settings) in /_/src/HaveIBeenPwned.PwnedPasswords.Downloader/Program.cs:224

  at async Task PwnedPasswordsDownloader.ProcessRanges(Settings settings) in /_/src/HaveIBeenPwned.PwnedPasswords.Downloader/Program.cs:240

  at async Task PwnedPasswordsDownloader.ProcessRanges(Settings settings) in /_/src/HaveIBeenPwned.PwnedPasswords.Downloader/Program.cs:240

Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #10 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #1 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #2 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Finished downloading all hash ranges in 626ms (1.60 hashes per second).
Failed request #4 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #6 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
Failed request #3 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
We made 0 Cloudflare requests (avg response time: NaNms). Of those, Cloudflare had already cached 0 requests, and made 0 requests to the Have I Been Pwned origin server.
Failed request #5 while fetching . Exception message: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection..
PS D:\HIBP>

This should be fixed in the latest release (0.3.12).


Constructing message updates for bipartite graph

❓ Questions & Help

hey @rusty1s , I'm looking to have message updates for a bipartite graph, where each node set has a different update rule. Is that possible? I was looking around at the MessagePassing class, and I understand that the nodes can be indexed as x_N and x_M? How does it work if we want to have different operations for messages from N -> M vs M -> N?

To add on what I've tried, I attempted to adopt a similar style to R-GCN, where suppose I have a 5 x 5 bipartite graph such that we have 50 directed edges, each edge is associated with a type (hence I have 50 types). I wish to multiply each edge with its own parameter vector, hence I've implemented the following:
class edge_type_net(torch_geometric.nn.MessagePassing):
    def __init__(self, in_channels, out_channels, e_types, bias=True, **kwargs):
        super(edge_type_net, self).__init__(aggr='add', **kwargs)

        self.in_channels = in_channels
        self.out_channels = out_channels
        self.num_e_types = e_types

        # Parameter tensor for each edge type
        self.pw_facts = torch.nn.Parameter(torch.Tensor(e_types, in_channels, out_channels))

    def forward(self, x, edge_index, edge_type, size=None):
        return self.propagate(x=x, edge_index=edge_index, edge_type=edge_type, size=size)

    def message(self, x_j, edge_index_j, edge_type_j):
        w = torch.index_select(self.pw_facts, 0, edge_type_j)
        out = w * x_j
        out = torch.max(out, dim=2)[0]
        return out

    def update(self, aggr_out, x):
        return aggr_out

    def reset_parameters(self):
        size=self.in_channels
        uniform(size, self.pw_facts)

class edge_model(torch.nn.Module):
    def __init__(self, in_channels, out_channels, e_types, n_embed, embed_size):
        super(edge_model, self).__init__()
        # Beliefs at each node
        self.embeds = torch.nn.Embedding(n_embed, embed_size)

        self.lbp = edge_type_net(in_channels, out_channels, e_types)

    def reset_parameters(self):
        self.embeds.reset_parameters()
        self.lbp.reset_parameters()

    def forward(self, x, edge_index, edge_type):
        x = self.embeds(x)
        x = self.lbp(x, edge_index, edge_type)

        return x

Running this keeps giving me an issue with the parameter size:
ValueError: Encountered node tensor with size 50 in dimension 0, but expected size 5.
I went to check the MessagePassing class and it says it should either be an int or tuple type? Not really sure what's the value I should put in because if I try various values, it complains of other dimensions that are wrong.


testing the submodule check

About the PR
Screenshots

Changelog

:cl:

add: Added fun!
remove: Removed fun!

dope


fix(build): wait for releases to be ready

What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
What this PR does / why we need it:
It happened several times that the release job failed just because the release was not found by GitHub API immediately after it had been created.
Some examples from the CI logs:
https://app.circleci.com/pipelines/github/falcosecurity/charts/120/workflows/fb349a0a-0f37-4ce7-b666-64854990aa6d/jobs/112
https://app.circleci.com/pipelines/github/falcosecurity/charts/120/workflows/9e467708-649a-463f-af0c-732b213b06a0/jobs/110
https://app.circleci.com/pipelines/github/falcosecurity/charts/114/workflows/bb91e320-84f4-4726-a365-93bafeaf8f30/jobs/105
Then I noticed that even though the logs reported:
Successfully packaged chart and saved it to: .cr-release-packages/falco-exporter-0.3.5.tgz
====> Using existing index at .cr-index/index.yaml
Error: GET https://api.github.com/repos/falcosecurity/charts/releases/tags/falco-exporter-0.3.5: 404 Not Found []

after a while, the GitHub API started to return the release metadata correctly. That let me think that maybe GitHub is processing new releases asynchronously.
For the above reason, this PR introduces a 5-seconds sleeping step as a workaround.
If it works, we can later find a better strategy to deal with this problem.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign leogr
You can assign the PR to them by writing /assign @leogr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 07137c011ed1a042cc8c51d7f84b876cbe591fd5

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Update indentation from 4 to 2 spaces

This PR updates REI's JavaScript indentation from 4 to 2 spaces.
Why?

2 spaces sufficiently conveys that you are in a new block while additionally preserving valuable horizontal real estate.
We are more in sync with industry and GitHub project styles and guides.

oh mah gersh!!!

I would ❤  the two space but I'm not too zealous about it.

@bonpixel I totally understand. I think the question really is, if you love it and most of our team feels the same way (which we can only know via our team vote), why are we not doing it? If, as a team, we are tolerating our style guide (i.e. most of us think "I don't get style x but that's just the way it is here at REI"), something is very wrong. Style evolves as developers evolve. Yes, style is not a personal preference which is why we put any changes up to a vote. As a team, we should not be constrained by our style guide and we its our obligation to make it work for us.

Could we review this in the next team meeting?  I'm not too sure how I feel about this.

@peripateticus Style guides are good servants but hateful masters.
I agree with your points. At the end of the day this thing exists to make things "better". Better is sometimes subjective, but let's not get caught up in the emotion of it and figure out what works best for the team.
It seems that more generally as a team we need to come to consensus as to the "how" (meaning how is it implemented) as opposed to the "what/why". ANY changes always seem painful, but they really shouldn't be.

Closing, went through the process and after a team vote there is a preference towards 4 spaces.


Mouseover/hover tags for edit and copy templates

Given my mistaken feature request before, it seems to me that the edit and copy template icons are not self-explanatory. Could we add mouseover/hover tags (or whatever they are called--those little yellow boxes that appear when you put your mouse over something) to these icons?

we do have mouseover text for those icons, at least in Firefox. are you not seeing them?
example from Dashboard:

I can confirm that they show up in Chrome as well, though I think there is an issue for clarifying what "edit" means.

i changed the title of this ticket to reflect above.
@NancyL what would you like the mouseover text for the Pencil icon to say?

"Edit template" or "Modify template". And the "copy" should be "Copy template". There should be something to clarify what you click on to actually enter data as well.


[Bug]: PointAnnotation draggable props not working on ios

Mapbox Implementation
Mapbox
Mapbox Version
default
Platform
iOS
@rnmapbox/maps version
10.1.9
Standalone component to reproduce
import React from 'react';
import {
  MapView,
  PointAnnotation,
  Camera
} from '@rnmapbox/maps';

const coordinates = [-74.00597, 40.71427];

const Map = () => {
  return (
    <MapView style={{flex: 1}}>
      <Camera centerCoordinate={[-74.00597, 40.71427]} zoomLevel={14} />
      <PointAnnotation
        id="selectedPoint"
        coordinate={coordinates}
        draggable />
    </MapView>
  );
}

export default Map;

Observed behavior and steps to reproduce
When props draggable is true, the PointAnnotation is not dragging at all.
Expected behavior
The PointAnnotation to drag.
Notes / preliminary analysis
Works fine at android
Additional links and references
No response

Well apparently on IOS it works a little bit different. If you want to drag, you need to "long press" for at least 1sec and start dragging.


Update stub/forward-host notation to accept port and tls-auth-name

Fixes #546.

Thanks, good catch on the troff macro! I was wondering (but not too much apparently) why my text editor seemed to have different highlight at these points.


Sz evidence qc table wdl

This commit is about some modifications on EvidenceQC.wdl to save some of the metrics in one tsv file. The python script for these modifications was prepared in a separate PR (you can read more about it here and here.
I have tested the modified WDL on both Cromwell and Terra and it worked smoothly. both on Cromwell and Terra.

Cromwell test Succeeded: The .json metadata file for the succeeded cromshell job is attached to this commit, and the final output qc table is attached to this commit (ref_panel_1kg.evidence_qc_table.tsv in the zipped file).
Terra test Succeeded: The job history for the test on Terra can be found here and the out put tsv file from is attached to this commit (batch1.evidence_qc_table.tsv in the zipped file).  The json files for the input and output definition of Terra workflow, is also attached to this commit (terra_inputs_outputs.zip)

results.zip
terra_inputs_outputs.zip

This is looking good, thank you @shadizaheri! I am closing https://github.com/broadinstitute/gatk-sv/pull/451 since this PR replaces that; however, since @epiercehoffman had reviewed that, please implement those suggestions in this PR.

Thank you, @VJalili and @epiercehoffman, for your comments. I applied your suggestions and tested the updated version on Terra and Cromwell. The job succeeded on both, and I am attaching a zip file of the final outputted .tsv tables to this commit. I am going to close and merge this PR.
tables_terra_cromshell.zip


chore(lint): switch to Prettier

Overview
This PR is for switching from eslint-config-airbnb-base to eslint-config-carbon-base/prettier. Bulk formatting change is done as well.
Testing / Reviewing
Testing should make sure no component is broken.

Apologies, should've merged this one in prior - can you resolve the merge conflicts? Will merge after

@chrisdhanaraj Thank you for reviewing! Resolved the conflicts.


feat: add configure for triton

Description

Related Issue

Motivation and Context

@MinH-09 Fix conflicting.


Button to collapse, new tweets number on collapsed coloums, 2 rows

Basically, this.
and if possible, being able to have 2 rows, like better tweetdeck offers.

"and if possible, being able to have 2 rows, like better tweetdeck offers"
Can you demonstrate this for me?

sorry, im dumb, its not better tweetdeck that does it, I misremembered. but, I made quick mock-up of how it might look.(Ignore the political BS, i just like laughing at them)

Got it! Thanks!


⚠ Bofrost.si has degraded performance

In 0068508, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 2762 ms

Resolved: Bofrost.si performance has improved in b7836db.


Basic view generation of all collections

DESC

finish generation of all collections (digital exhibs / designs etc.)

TODOs

[x] implement glossar / list of entries --- keep it simple

depends on requirements


Add zstd compression/decompression support

Adds zstd compression, issue #22393

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[x] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @tvalentyn, @pabloem

R: @ryanthompson591 , @ahmedabu98
can you please have a look?

R: @ryanthompson591 , @ahmedabu98
can you please have a look?

There is an error:
Container does not include required Beam dependencies or has conflicting dependencies. If Beam dependencies have changed, you need to regenerate base_image_requirements.txt files. See: https://s.apache.org/beam-python-requirements-generate

I'll do that and push a commit here.
For future changes: please don't squash reviewed and unreviewed commits via force-push, until review has finalized.

thank you @tvalentyn, I wasn't sure the root cause of the error, lesson learned for next contributions


[Griffs feedback] Changes on Splash page

https://www.figma.com/design/tP7Arb2C8aDB05wCVxVVSB/Pairwise-RF6-->-Voting-App?node-id=1763-120596&t=TFoIin9il128HyXW-1

Ready for review https://www.figma.com/design/tP7Arb2C8aDB05wCVxVVSB/Pairwise-RF6-->-Voting-App?node-id=1763-120596&t=Fp3yTlMadXVi0DGb-1

@HrithikSampson https://www.figma.com/design/tP7Arb2C8aDB05wCVxVVSB/Pairwise-RF6-->-Voting-App?node-id=2411-90262&t=6EI1YJtqaVKTzqKO-1

@maryjaf , it is ready to be tested

there is a auto scroll logic to top of the page @HrithikSampson
https://github.com/user-attachments/assets/4da72b52-cc10-47a2-ab80-4de9538ea19e

Is it merged on staging? @HrithikSampson @mmahdigh

@maryjaf , it is ready to be tested.
@Moenick, just merged

there is a auto scroll logic to top of the page @HrithikSampson
Screen.Recording.2024-11-12.at.3.16.25.PM.mov

The problem has been fixed , thanks


update testing for dropdown

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.


More unit tests

Current coverage is 92.67%

Merging #51 into develop will increase coverage by +26.93% as of 34189ca

@@            develop     #51   diff @@
=======================================
  Files            11      11
  Stmts          1912    1870    -42
  Branches          0       0
  Methods
=======================================
+ Hit            1257    1733   +476
  Partial           0       0
+ Missed          655     137   -518

Review entire Coverage Diff as of 34189ca

Powered by Codecov. Updated on successful CI builds.


fix: Example cognitiveservices\data-plane\LUIS\Authoring

skip is an integer
take is an integer

Can one of the admins verify this patch?

This would need LUIS team to review
@mohabghanem

Noticed this was included in #4524 so I'll close this


App variable is not declared

while running this code on expo it says "Can't find variable: App" . So, I declared it using the const keyword and exported it default below the function

Why the changes still didn't appear in the website. I'm guessing it's the problem in circleci?

Why the changes still didn't appear in the website. I'm guessing it's the problem in circleci?

@rishikesh2003 The changes were applied only to the next docs, if you would like to see the changes in older, versioned docs you will need to update more files. You can read more about the versioning system in Readme:

https://github.com/facebook/react-native-website#versioned-docs


Logic bug in findString

Through 2.2.5, the findString template has this code:
<xsl:when test="exists($l)">
  <xsl:variable name="stringfile" select="$stringFiles[@xml:lang = $l]/@filename" as="xs:string*"/>
  <xsl:variable name="str" as="element()*">
    <xsl:for-each select="$stringfile">
      <xsl:sequence select="document(., $stringFiles[1])/*/*[@name = $id or @id = $id]"/><!-- strings/str/@name opentopic-vars:vars/opentopic-vars:variable/@id -->
    </xsl:for-each>
  </xsl:variable>

I've highlighted $stringFiles[1]. I think this must be wrong because the $stringfile variable is a list of filenames that is then iterated by the for-each but the for-each will only ever use the first value in $stringFiles. I think the correct behavior (or intended behavior) is to use the current item in the for-each loop.
The result of this bug should be that overrides are never found or are found if and only if the override happens to be the first one found.

The $stringFiles[1] to define the base URI of the stringfile relative URI and it's the same for all values in $stringfile. I don't see a bug.

I've got output that is pulling strings from multiple (pre-integration) variable files for the same language, so I think the code is working properly even if it looks odd.

Right you are. I misread the code. Sorry for the misreport.


[DOC] TransformedTargetForecaster missing

For example:
model = TransformedTargetForecaster(
    [
        ("deseasonalize", Deseasonalizer(model="multiplicative", sp=4)),
        ("detrend", Detrender(forecaster=PolynomialTrendForecaster(degree=1))),
        (
        "forecast",
            make_reduction(
                LinearRegression(),
                scitype="tabular-regressor",
                window_length=15,
                strategy="recursive",
            ),
        ),
    ]
)

The document never explains the automatic re-tend + re-seasonalize the output of the last step "forecast", before returning the predictions (in its original form) to the main program.

Thanks @zollen for raising the issue, would appreciate a PR for it.

Hi @zollen, was the issue resolved?

Let's pretend so.

Let's pretend so.

Hm, I thought there was an action here - the documentation should be updated?
What do you think, @zollen, would be the main action here?
Many apologies if my response (about PR) caused offense, it was meant to be entertaining and educating, not as patronizing, but not sure whether that came across. Sorry again.

Don't worry. I should be the one who do the apology as I closed the ticket without much comments.
I don't think it is an issue. I guess whoever uses this awesome mktime package should have already understood how arima works anyway.


[Tracking issue] Dapr Workflows Stable

This issue will be the source of truth for collating all tasks what must be complete in order for Workflows to progress to Stable, for the 1.15 release.
Dapr Runtime / durabletask-go

[ ] https://github.com/dapr/dapr/issues/7633
-- duplicate of https://github.com/dapr/dotnet-sdk/issues/1205
[ ] https://github.com/dapr/dapr/issues/7777
[ ] https://github.com/dapr/dapr/issues/7934
[ ] https://github.com/dapr/dapr/issues/7749
[ ] https://github.com/dapr/dapr/issues/6889
[ ] https://github.com/dapr/dapr/issues/7706
[ ] https://github.com/dapr/dapr/issues/6014
[ ] https://github.com/dapr/dapr/issues/3417
[ ] https://github.com/dapr/dotnet-sdk/issues/1195 (also has dotnet SDK work)

Contrib / State Store

[ ] [CosmosDb] https://github.com/dapr/dapr/issues/8004
[ ] [AzureSQL] https://github.com/dapr/dapr/issues/7570

Quickstarts

[ ] https://github.com/dapr/dotnet-sdk/issues/1234

Perf

[ ]

Docs

[ ] https://github.com/dapr/dapr/issues/6475

SDKs

[ ] [dotnet] https://github.com/dapr/dotnet-sdk/issues/1344
[ ] [dotnet] https://github.com/dapr/dotnet-sdk/issues/1293
[ ] [dotnet] https://github.com/dapr/dotnet-sdk/issues/1246
[ ] [dotnet] https://github.com/dapr/dotnet-sdk/issues/1225
[ ] [dotnet] https://github.com/dapr/dotnet-sdk/issues/1220
[ ] [dotnet] https://github.com/dapr/dotnet-sdk/issues/1216
[ ] [dotnet] https://github.com/dapr/dotnet-sdk/issues/1215
[ ] [dotnet] https://github.com/dapr/dotnet-sdk/issues/1203
[ ] [dotnet] https://github.com/dapr/dotnet-sdk/issues/1200
[ ] [dotnet] https://github.com/dapr/dotnet-sdk/issues/1195
[ ] [dotnet] https://github.com/dapr/dotnet-sdk/issues/1163 (also requires runtime work)
[ ] [dotnet] https://github.com/dapr/dotnet-sdk/issues/1140
[ ] [dotnet] https://github.com/dapr/dotnet-sdk/issues/1118

Hello, this keeps happening.  https://github.com/dapr/dapr/issues/7824

@olitomlinson I don't want to modify the issue directly but - https://github.com/dapr/dapr/issues/3417 appears to be unrelated to getting workflows to stable.

@dapr/approvers-dotnet-sdk @dapr/maintainers-dotnet-sdk  - Are all of these SDK issues proportionate, necessary, appropriate and is there bandwidth to get them completed for workflows to be stable?

@mikeee I wasn't clear btw, I fully expect the above list to be triaged for suitability by the maintainers for what is in and out of scope for 1.15 :)

@mikeee I wasn't clear btw, I fully expect the above list to be triaged for suitability by the maintainers for what is in and out of scope for 1.15 :)

Thought so, I'll await the dotnet-sdk maintainers to triage the SDK items

I'll be helping out with the triage of these items over the next few days.

@olitomlinson I think https://github.com/dapr/dapr/issues/3417 might be referring to GitHub actions workflows and not Dapr Workflow. If you agree, then we can probably take it off this list.

I went ahead and added [P_] next to the above issues for us to better see what work is a P0 for this release

@olitomlinson @cgillum I'll be going through the go, python and javascript SDKs to review the different changes we need pursuing SDK parity and workflows to become stable
So far this is a list of issue for the go sdk that I believe should be tracked here:

[ ] https://github.com/dapr/go-sdk/issues/611
[ ] https://github.com/dapr/go-sdk/issues/541
[ ] https://github.com/dapr/go-sdk/issues/634
[ ] https://github.com/dapr/go-sdk/issues/493
[ ] https://github.com/dapr/go-sdk/issues/497
[ ] https://github.com/microsoft/durabletask-go/issues/42
[ ] https://github.com/dapr/go-sdk/issues/635
[ ] https://github.com/dapr/go-sdk/issues/636

Here are the issues for the python SDK

[ ] https://github.com/dapr/python-sdk/issues/655
[ ] https://github.com/dapr/python-sdk/issues/738
[ ] https://github.com/dapr/python-sdk/issues/739
[ ] https://github.com/dapr/python-sdk/issues/740
[ ] https://github.com/dapr/python-sdk/issues/711

And the js sdk issues, the durabletask-js issues would need their counterpart issues created in the js-sdk repo:

[ ] https://github.com/microsoft/durabletask-js/issues/64
[ ] https://github.com/microsoft/durabletask-js/issues/47
[ ] https://github.com/microsoft/durabletask-js/issues/30
[ ] https://github.com/microsoft/durabletask-js/issues/13
[ ] https://github.com/dapr/js-sdk/issues/638
[ ] https://github.com/dapr/js-sdk/issues/639

@olitomlinson The top P0 item in the .NET SDK referencing https://github.com/dapr/dotnet-sdk/issues/1344 can be marked off as completed

Added prioritized list of Java SDK issues to the OP.

I've discovered that the workflow SDKs are inconsistent in the naming of callChildWorkflow / callSubWorkflow

dotnet, go,  and python use callChildWorkflow
java and javascript use callSubWorkflow

I believe the SDKs should strive for consistency where sensible, and should strive to be consistent with the docs which only refers to child workflows
I've raised tickets to bring the Java and JS SDKs inline with the others :

https://github.com/dapr/java-sdk/issues/1155
https://github.com/dapr/js-sdk/issues/643

I believe these would both be considered P0 as we want to go into the Stable release with method names that won't change.
Thoughts @yaron2 @artursouza ?

@olitomlinson I'd like to propose adding #7321 to the stabilization list as it's a named issue on the Workflow Limitations, but the issue was closed due to staleness.

I agree. I've reopened this and added this to the main list.
@cgillum what priority should be attached to this item? Are we intending to ship with CosmosDb support in 1.15?

@olitomlinson per an earlier discussion with @yaron2, I think the best path forward is to have a list of supported state stores for workflow, similar to actors (it would necessarily be a subset of actor state stores). Cosmos DB and similar state stores would not be on that list due to the issue you linked to. Unfortunately, I think there isn't enough time to work through those issues before Stable.

@cgillum Is there an issue somewhere that tracks progress of the NoSQL support and what's lacking?

@WhitWaldo I don't believe we have an issue tracking progress of this work. However, I do have an old PR that does the foundational work in the durabletask-go dependency to enable it: https://github.com/microsoft/durabletask-go/pull/50 ("state update chunking"). The main problem has been finding the time to validate and stabilize it.

@olitomlinson Possible additions to the list following the discussion in #Workflow by @NunzioCar:
https://github.com/dapr/dapr/issues/8322
https://github.com/dapr/dapr/issues/8323