Firebase Storage Upload/Download Failures

Description
I'm using firebase storage in order to upload some files and download those files later. I'm using the code down below in order to download the files from firebase storage.
func downloadFileFromFirebase(fireBasePath: String, localURL: String) {
let fireBaseStorage =  Storage.storage().reference()
let storeRef =  fireBaseStorage.child("(String(describing: fireBasePath))")
let downloadTask = storeRef.write(toFile: localURL)
downloadTask.observe(.progress) { snapshot in
// Updating the progress bar
}
downloadTask.observe(.success) { snapshot in
//Updating the UI
}
}
Here, what I noticed is that my downloadTask.observe closures are not invoking and I did some digging in the framework and found out that my task is never enqueued and the StorageDownloadTask is deallocated before that.

Line 110 is never executed.

Here in StorageReference on Line 204 we are creating a strong reference cycle with StorageDownloadTask but still it is deallocating before the enqueue implementation I don't know why. So, in order to confirm that issue is happening due to this deallocation reason, I deliberately created a retain cycle in StorageReference and made sure that the StorageDownloadTask is not deallocated.

And after creating this retain cycle my downloadTask.observe closures are invoking and I'm able to download the media from firebase storage. But this is not a solution to the problem as it will create retain cycle. Can somebody help with this problem and tell me why this is happening?
This problem started coming after 10.2.0 versions. Currently, I'm using the 10.24.0 version.
Reproducing the issue
No response
Firebase SDK Version
10.24.0
Xcode Version
15.3
Installation Method
CocoaPods
Firebase Product(s)
Storage
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

Sorry about the trouble @KunalxBhandari. I'm not able to reproduce. The only possible impacting change since 10.2.0 I see is https://github.com/firebase/firebase-ios-sdk/pull/10492 and I'm not sure why that would matter.
I'm not sure how the task could be deallocated between the StorageDownloadTask init and the task.enqueue() call.
Does adding a wait or sleep to the bottom of downloadFileFromFirebase make a difference?
Are you able to share a sample app that reproduces the issue?

@paulb777 I'm using putData, delete, putFile, getMetadata, downloadURL functions of Storage and all of these are working fine expect the write function which I'm using for downloading the file from firebase storage. But on using sleep it's working fine. Is there any particular reason why this function is behaving like this?

Hello, I'm facing a similar issue, where the downloadProgressBlock never gets called
line 134 never gets executed.

Any idea what could cause this ?

nor the fetcherCompletion

Does the app finish before the write completes?

I used the Thread.sleep(0.1) before my function body ends and now code is working fine. But like I explained, I was not getting the callback because the firebase object was deallocating. I don't know why that was happening but for now thread sleep seems to have worked for me.

I'm still not able to reproduce. When I add the code above into an app, I see the breakpoint in enqueueImplementation hit before the deallocation.
Would you share a fully reproducible example?

I would love to but unfortunately I can't.


Support for cargo.toml files

Miho really should be able to bump cargo.toml files too.

Supported now in v3.


Simple refactoring of JobContext.commit()

Refactor JobContext.commit() in preparation for parallelization for the commit logic:

Refactor the commit logic from the for loop into a separate method processDatasetCommit()
Refactor the check for support for failed WorkUnit handling into a separte method checkForUnpublishedWUHandling .
Move commitSequenceBuilder from a instance variable to a local variable in processDatasetCommit().

@zliu41 can you review?

Coverage decreased (-0.002%) to 43.638% when pulling 980ebd49bf1aa9abfbd703378d5410985e5b9c79 on chavdar:copy_publish_parallel into 5aeb0210a422e49d143c154a8950e1d278e44aa3 on linkedin:master.

Coverage decreased (-0.5%) to 43.157% when pulling 980ebd49bf1aa9abfbd703378d5410985e5b9c79 on chavdar:copy_publish_parallel into 5aeb0210a422e49d143c154a8950e1d278e44aa3 on linkedin:master.

Coverage increased (+0.3%) to 43.95% when pulling 9dc66f860d8377721134571aa2c380c109752570 on chavdar:copy_publish_parallel into 5aeb0210a422e49d143c154a8950e1d278e44aa3 on linkedin:master.

Coverage increased (+0.5%) to 44.148% when pulling 9dc66f860d8377721134571aa2c380c109752570 on chavdar:copy_publish_parallel into 5aeb0210a422e49d143c154a8950e1d278e44aa3 on linkedin:master.

LGTM

Coverage increased (+0.4%) to 44.072% when pulling 9dc66f860d8377721134571aa2c380c109752570 on chavdar:copy_publish_parallel into 5aeb0210a422e49d143c154a8950e1d278e44aa3 on linkedin:master.

Coverage increased (+0.4%) to 44.016% when pulling 9dc66f860d8377721134571aa2c380c109752570 on chavdar:copy_publish_parallel into 5aeb0210a422e49d143c154a8950e1d278e44aa3 on linkedin:master.


Implement ListAllCommand

As per title

@m133225 @yl-coder is there an event to trigger the updating of the GUI without updating the model (or if it's not possible, at least without updating the local file)?

The GUI is tied to the model. There is no event to update the GUI. The list view is tied to the list that it is controlling. We will need to pass a filteredList to the Listview. And the ListAllCommand will simply set the predicate to show all person. And the SearchCommand will set a predicate to the filteredList show a subset of persons.
Currently, the FilteredList is not implemented yet. We need to change the list used in PersonListPanel to use FilteredList instead of ObservableList.
On 24 Aug 2016, at 6:26 PM, Joshua Lee <notifications<EMAIL_ADDRESS>wrote:
@m133225https://github.com/m133225 @yl-coderhttps://github.com/yl-coder is there an event to trigger the updating of the GUI without updating the model (or if it's not possible, at least without updating the local file)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/se-edu/addressbook-level4/issues/16#issuecomment-242020255, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIpoEANx0fto9kIyA9nbsmLWkoBE21Pmks5qjBxzgaJpZM4Jqh9T.

wait, so are we adding back what was taken out in df1119c3e1f88c3688639e794741f5181234415a? or doing a simpler version of what was taken out?
and by SearchCommand do you mean FindPersonsByWordsInNameCommand?


(feature/tuya-panel-kit-sophia):swipeout add onScrollEnd

Description
Based on the original Swipeout add event onScrollEnd
Type of change
Please select the relevant option.

[ ] New feature (non-breaking change which adds functionality)

Codecov Report

Merging #141 (5b53793) into master (a43968b) will decrease coverage by 0.01%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##           master     #141      +/-   ##
==========================================
- Coverage   90.78%   90.77%   -0.02%
==========================================
  Files         155      155
  Lines        7377     7379       +2
  Branches     2034     2035       +1
==========================================
+ Hits         6697     6698       +1
- Misses        559      560       +1
  Partials      121      121

Impacted Files
Coverage Δ

...tuya-panel-kit/src/components/swipeout/swipeout.js
98.58% <50.00%> (-0.70%)
:arrow_down:

Continue to review full report at Codecov.

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

@sunny-ali commit 信息不对，需要修改 https://github.com/tuya/tuya-panel-kit/pull/141/checks?check_run_id=3618622898#step:7:13


bug fix: All signers need to be set at once

see: https://github.com/solana-labs/solana/blob/418076ab3ea9f41171afa7075670e68640e5695d/web3.js/src/connection.ts#L3875

@neverything Hi, I am developing some Solana projects in PHP. I will work very active on this project. I forked this repo and modify. I want to merge to your repo ASAP. If you have more time, we can discuss this. I want to make this repo better.
Checkout: https://github.com/pantaovay/solana-php-sdk/commits/main

@pantaovay not officially a maintainer of this package, but working with it in a few projects myself.

Thanks @pantaovay!


Table of Contents under "In this article" is missing entries

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows
only has the "Available events" heading, but the individual events aren't listed:

They used to be listed, and it makes sense for them to be.
What changes are you suggesting?
Make level 3 headings appear in the sidebar under "In this article" again. It looks like commit 4cd28fd73522e65b6428fd5424cf5e6e3018effd caused them to disappear.
Additional information
No response

@bewuethr Thanks for opening and issue and linking to the commit. Great detective work! 🔍
I'm checking with the team on this one. 💛

@bewuethr Just dropping in to report that the individual events are now listed in the side bar again 🎉
Closing this issue out now 💖


Fix fold1 and foldMap1

This pull request fixes the functions fold1 and foldMap1 with the result that the fixed implementations append all elements in the correct order. 😄
PSCi, version 0.12.0
Type :? for help

> import Prelude
> import Data.Semigroup.Foldable
> import Data.List.Pointed
> map fold1 (prev =<< prev =<< fromFoldable ["1", "2", "3", "4", "5"])
(Just "12345")

Wow! That was quick! Thanks a lot!


Loadbalancer comes up ACTIVE, OFFLINE after creation

Title:

Loadbalancer comes up OFFLINE after creation, the expected status is ONLINE.
OpenStack Release
Liberty
Description
I ran into this problem during running Tempest scenario tests. It tries to create a loadbalancer, listener and pool member. It never get passed loadbalancer creation, since it expects ONLINE status for loadbalancer.
Agent Version
Liberty head with the disconnected feature present.

This PR has been merged through liberty->mitaka->master.


Assign plicy to a group

Is it not possible to assign a policy to a group of users? I want to assign a policy to 1500 students and i can not do this one by one student...

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

ID: f34f3188-0af5-f972-9d28-959f5f7866a2
Version Independent ID: fab26e11-a729-92a4-3ea6-8668dca55dd0
Content: What are Messaging policies in Teams?
Content Source: Teams/messaging-policies-in-teams.md
Service: msteams
GitHub Login: @tonysmit
Microsoft Alias: tonysmit

I am baffled by the same assignment issue. 84,000+ accounts and my choice is global or per user assignment? No group assignment including and preferably dynamic groups? In education user accounts come and go every day so something dynamic is greatly needed. Maybe a hierarchy where an individual assignment overrides group or domain assignment. Most large organizations have some sort of identity management. Populating custom attributes to base dynamic group filters can be very powerful if the groups could be used. Either I am missing something or just failing to understand the logic of having a policy based system and only manual user based assignment.

@olavase Thank you for this inquiry
I don't know how to assing a policy to a group of users without using global. Let me get this over to the Teams/Skype for Business team for investigation.
The team will get this prioritized into a sprint plan. Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

The only way I have been able to assign policy to multiple users is by using powershell. Even that is limited to about 50 lines before it cracks it and stops working. Really needs to be a better option to assign policies to users. Here is the script I have been using if you want to give it a shot and make it better.
$UsersFile = Import-Csv "D:\Users\desktop\userslist.csv"
$credential = Get-Credential
Import-Module SkypeOnlineConnector -global
$sfboSession = New-CsOnlineSession -Credential $credential -OverrideAdminDomain "domain.onmicrosoft.com"
Import-PSSession $sfboSession -allowclobber
foreach ($User in $UsersFile) {
grant-CsTeamsMessagingPolicy -Identity $User.UPN -PolicyName EduStudent_Custom -ErrorAction SilentlyContinue}

@nomorephones can you help us with this one?

@LolaJacobsen This capability is not currently available in the Teams admin center.  While the ability to make policy changes on groups of users is something that we are working on, unfortunately we don't yet have a committed date for release.

You've moved the settings from Settings > Services & add-ins > Microsoft Teams, to the new Teams and Skype dashboard and in that process removed the ability to apply settings easily to all our students licenses. Ridiculous
It was super easy back in 2017: https://blogs.technet.microsoft.com/skypehybridguy/2017/08/24/microsoft-teams-disable-private-chat-how-to/

I can't understand what possible reason you (Microsoft) have to remove the ability to assign policy to groups or Faculty/Students. You have always taught us to use groups for assigning permissions but in 2018 you suddenly step away from that principle? Also I can't understand why this would take so long to implement, I can't possibly be that difficult.

Any update on assigning policy to a group?

Another month and still no word on licensing for groups. What was wrong with Settings by user/license type in the old services/addins section? As @Per-Torben says, it can't possibly be that difficult.

@olavase - thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:  https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.

@officedocsbot close

Still doesn't seem possible. I just want to apply a policy to a group.

Aside from the spelling mistake in the title, I'm not sure why this got closed. It's as relevant as ever and I find myself here after searching around for potential solutions or suggestions.

@scanum why is this closed? This is still an issue support are unable to help with.

I believe they closed it early but you can now set up policies to automatically assign to groups/security groups using powershell.
https://docs.microsoft.com/en-us/microsoftteams/teams-policies
They should have provided this information before closing it down.

@bucketspodge that's a cheat as it's pulling users from a group and using ForEach-Object command to apply at a per user level.
Certainly wouldn't do it automatically if this command wasn't running periodically.

@RobFullerGBHS my apologises I did grab the wrong link. I believe this is the one I was thinking of.
https://docs.microsoft.com/en-us/microsoftteams/assign-policies

@bucketspodge New-CsGroupPolicyAssignment looks interesting thanks for the link!

@RobFullerGBHS No problem, I'm still trying to work out the rankings for my workplace and will then test it myself but looks hopeful.

Getting, Set-CsGroupPolicyAssignment : Access Denied. How did you get on?

Seen this update on the message center.
Updated March 4, 2020: To ensure the best experience we are adjusting the roll-out timeframe for this feature. We apologize for the inconvenience.
Teams administrators will soon be able to assign policies to a batch of users or to a group. We’ll be releasing this in late May (previously March).
This message is associated with Microsoft 365 Roadmap ID 61185.

Seen this update on the message center.
Updated March 4, 2020: To ensure the best experience we are adjusting the roll-out timeframe for this feature. We apologize for the inconvenience.
Teams administrators will soon be able to assign policies to a batch of users or to a group. We’ll be releasing this in late May (previously March).
This message is associated with Microsoft 365 Roadmap ID 61185.

Yeah that would explain the access denied! Thanks for the heads up.


Introduces extra check to create "partial" yamls

Now we have 3 kubernetes yamls: (same for openshift):

/config/deploy/kubernetes/kubernetes.yaml: All the stuff without the CSI driver stuff
/config/deploy/kubernetes/kubernetes-csi.yaml: ONLY the CSI driver stuff
/config/deploy/kubernetes/kubernetes-all.yaml: EVERYTHING (kubernetes.yaml + kubernetes-csi.yaml)

Now the user can easily deploy/remove the CSI driver related resources.
kubernetes-all.yaml and openshift-all.yaml is used for the local deployment scripts and olm

Do we need kubernetes-all.yaml?

Do we need kubernetes-all.yaml?

its mainly for dev stuff, the user doesn't need it AFAIK.
but its nicer in dev scripts to have 1 kubectl apply instead of 2


:bug: Fix configuration not being merge

Fix #687.

Codecov Report

Merging #1117 (734a2d6) into master (7bb9af9) will increase coverage by 0.53%.
The diff coverage is 30.43%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master    #1117      +/-   ##
==========================================
+ Coverage   22.79%   23.33%   +0.53%
==========================================
  Files          22       22
  Lines        1610     1633      +23
==========================================
+ Hits          367      381      +14
- Misses       1179     1186       +7
- Partials       64       66       +2

Impacted Files
Coverage Δ

internal/agent/agent.go
43.10% <ø> (ø)

internal/agent/install.go
5.28% <30.43%> (+5.28%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@jimmykarily I'm having troubles understanding why upgrade with opensuse works, but fails with alpine. Is this random?

The tests run perfectly well locally with:
earthly +all --IMAGE=quay.io/kairos/core-alpine-opensuse-leap:latest --FLAVOR=alpine-opensuse-leap
MEMORY=9048 \
KVM=true \
USE_QEMU=false \
CPUS=4 \
MACHINE_DISPLAY=true \
KEEP_VM=true \
CREATE_VM=true \
CONTAINER_IMAGE=ttl.sh/kairos-alpine-opensuse-leap-3b5156b9945a9180077d5c7c157265079c72b6e4:8h \
ISO=/home/xxx/Software/spectro-cloud/kairos/build/kairos-core-alpine-opensuse-leap.iso \
FLAVOR=alpine \
ginkgo run -v --label-filter upgrade-with-cli tests/

This will probably change when we are done with the refactoring described here: https://github.com/kairos-io/kairos/issues/209#issuecomment-1464224461
Up to now, the kairos config tried to be both: a specific config for the kairos-agent and a generic config for every component (kcrypt, elemental-cli etc).
After the refactoring, any consumer that needs the full (generic) config, will use the new collector package and if needed will unmarshal that to a more "specific" struct.
Having said this, there is no need to block this PR since the refactoring is in progress and hasn't touched this file yet.

@jimmykarily you'll have to approve and merge since I can't do it.


docs: fixed typo in "Get started with multi-host networking"

Hali,
It is just a minimal HTML typo, HTML tag wasn't closed.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fixed-typo-in-get-started-guide" git@github.com:lmesz/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Actually, the tag is correct. We use these to hide the metadata on GitHub, but still being able to access it when building the documentation using Hugo. We decided to use the same syntax as "conditional comments" in internet explorer, see https://msdn.microsoft.com/en-us/library/ms537512(v=vs.85).aspx#dlhidden

Okay I see the other docs, but can you explain me why the getting started guide looks like how it looks like in the pic ?

Ah, I think there was an issue with trailing spaces after the closing tag; in the 1.9 release tag, there's trailing spaces after the tag, which caused it not being removed from the output; https://raw.githubusercontent.com/docker/docker/v1.9.0/docs/userguide/networking/get-started-overlay.md
To check the generated documentation, you can run make docs in your git repo, which will build the documentation and start a web server to test it (given you have docker configured locally)


Running restricted set of unit tests on Travis PR.

NOTE: Has #2475 as diffbase.

@dhermes this has a conflict too. Otherwise LGTM.

@daspecster I just rebased and it seemed to fix itself?

Build time down from 20 minutes to about 7.5 minutes. But it used to be consistently under 4, so I still have work to do.

I don't see any special handling for changes in core/ -- because it is a dependency for everything else, should we be falling back to running all tests when any change happens there?

@tseaver I've got a change coming down the pipe which computes a package dependency graph and then follows the tree to populate a more-full list of changes. Thanks for being heads up!


Extension Disambiguation

Construct 0.1.0 introduces a cleaned up Extension API. Instead of modules providing register, and unregister functions, extensions and now subclasses of the Extension base class. Extensions can provide
actions, tasks, and template paths.
I'd like to move toward more focused Extensions and provide the following Extension Types:

ActionProvider - provides actions
TemplateProvider - provides template paths
ContextProvider - inject dependencies into context before each task executes
HostProvider - host application interface with uniform api across apps

Implemented HostExtension type in Construct 0.1.18.


Driver crash with OVR space calibration and Natural Locomotion

See here for info in NaLo: https://github.com/SlimeVR/SlimeVR-Server/issues/25
Affected user's discord: Tera#0564

Second for Natural Locomotion. Causes SteamVR to crash if both SlimeVR server and Natural Locomotion are running at the same time, regardless of launch order.

Seconded - coming from Vive trackers, this caused unexpected crashes. I figured it out on my own but this friction should ideally not exist. Also, would be cool to use both vive trackers and slimevr at the same time

Also as a third, same thine. Sorry if that's extremely redundant, in dire needs of this I am getting extra trackers from ALVR (using two quest 2's) it works amazingly well, but I cant use the slime vr diy kit I've built with it now since I cannot calibrate my space using this tool.

Should be fixed in #14


Improve the readme with Dockerfile examples

Same patch as https://github.com/gocd-contrib/docker-elastic-agents/pull/14.


it  can not be used in k8s1.23.1 duo to incompatible types for comparison

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What version of the Traefik's Helm Chart are you using?
latest
What version of Traefik are you using?
2.5.6
What did you do?
nothing
What did you see instead?
Error: template: traefik/templates/_podtemplate.tpl:306:17: executing "traefik.podTemplate" at <eq .type "secret">: error calling eq: incompatible types for comparison
What is your environment & configuration?
k8s version： 1.23.1
Additional Information
Error: template: traefik/templates/_podtemplate.tpl:306:17: executing "traefik.podTemplate" at <eq .type "secret">: error calling eq: incompatible types for comparison

Could you please provide your value file.
Are setting some volumes?
Would any of those miss a type?

Default values for Traefik
image:
name: traefik
defaults to appVersion
tag: "2.5.6"
pullPolicy: IfNotPresent

Configure the deployment

deployment:
enabled: true
Can be either Deployment or DaemonSet
kind: Deployment
Number of pods of the deployment (only applies when kind == Deployment)
replicas: 1
Amount of time (in seconds) before Kubernetes will send the SIGKILL signal if Traefik does not shut down
terminationGracePeriodSeconds: 60
The minimum number of seconds Traefik needs to be up and running before the DaemonSet/Deployment controller considers it available
minReadySeconds: 0
Additional deployment annotations (e.g. for jaeger-operator sidecar injection)
annotations: {}
Additional deployment labels (e.g. for filtering deployment by custom labels)
labels: {}
Additional pod annotations (e.g. for mesh injection or prometheus scraping)
podAnnotations: {}
Additional Pod labels (e.g. for filtering Pod by custom labels)
podLabels: {}
Additional containers (e.g. for metric offloading sidecars)
additionalContainers: []
# https://docs.datadoghq.com/developers/dogstatsd/unix_socket/?tab=host
# - name: socat-proxy
# image: alpine/socat:1.0.5
# args: ["-s", "-u", "udp-recv:8125", "unix-sendto:/socket/socket"]
# volumeMounts:
#   - name: dsdsocket
#     mountPath: /socket
Additional volumes available for use with initContainers and additionalContainers
additionalVolumes: []
# - name: dsdsocket
#   hostPath:
#     path: /var/run/statsd-exporter
Additional initContainers (e.g. for setting file permission as shown below)
initContainers: []
# The "volume-permissions" init container is required if you run into permission issues.
# Related issue: https://github.com/traefik/traefik/issues/6972
# - name: volume-permissions
#   image: busybox:1.31.1
#   command: ["sh", "-c", "chmod -Rv 600 /data/*"]
#   volumeMounts:
#     - name: data
#       mountPath: /data
Custom pod DNS policy. Apply if hostNetwork: true
dnsPolicy: ClusterFirstWithHostNet
Additional imagePullSecrets
imagePullSecrets: []
# - name: myRegistryKeySecretName
Pod disruption budget
podDisruptionBudget:
enabled: false
maxUnavailable: 1
maxUnavailable: 33%
minAvailable: 0
minAvailable: 25%
Use ingressClass. Ignored if Traefik version < 2.3 / kubernetes < 1.18.x
ingressClass:
true is not unit-testable yet, pending https://github.com/rancher/helm-unittest/pull/12
enabled: true
isDefaultClass: true
Use to force a networking.k8s.io API Version for certain CI/CD applications. E.g. "v1beta1"
fallbackApiVersion: ""
Activate Pilot integration
pilot:
enabled: false
token: ""
Toggle Pilot Dashboard
dashboard: false
Enable experimental features
experimental:
plugins:
enabled: false
kubernetesGateway:
enabled: false
appLabelSelector: "traefik"
certificates: []
# - group: "core"
#   kind: "Secret"
#   name: "mysecret"
# By default, Gateway would be created to the Namespace you are deploying Traefik to.
# You may create that Gateway in another namespace, setting its name below:
# namespace: default
Create an IngressRoute for the dashboard
ingressRoute:
dashboard:
enabled: true
# Additional ingressRoute annotations (e.g. for kubernetes.io/ingress.class)
annotations: {}
# Additional ingressRoute labels (e.g. for filtering IngressRoute by custom labels)
labels: {}
rollingUpdate:
maxUnavailable: 1
maxSurge: 1

Configure providers

providers:
kubernetesCRD:
enabled: true
allowCrossNamespace: false
allowExternalNameServices: false
# ingressClass: traefik-internal
# labelSelector: environment=production,method=traefik
namespaces: []
# - "default"
kubernetesIngress:
enabled: true
allowExternalNameServices: false
# labelSelector: environment=production,method=traefik
namespaces: []
# - "default"
# IP used for Kubernetes Ingress endpoints
publishedService:
enabled: false
# Published Kubernetes Service to copy status from. Format: namespace/servicename
# By default this Traefik service
# pathOverride: ""

Add volumes to the traefik pod. The volume name will be passed to tpl.
This can be used to mount a cert pair or a configmap that holds a config.toml file.
After the volume has been mounted, add the configs into traefik by using the additionalArguments list below, eg:
additionalArguments:
- "--providers.file.filename=/config/dynamic.toml"
- "--ping"
- "--ping.entrypoint=web"
volumes: []
- name: public-cert
mountPath: "/certs"
type: secret
- name: '{{ printf "%s-configs" .Release.Name }}'
mountPath: "/config"
type: configMap
Additional volumeMounts to add to the Traefik container
additionalVolumeMounts: []
For instance when using a logshipper for access logs
- name: traefik-logs
mountPath: /var/log/traefik
Logs
https://docs.traefik.io/observability/logs/
logs:
Traefik logs concern everything that happens to Traefik itself (startup, configuration, events, shutdown, and so on).
general:
# By default, the logs use a text format (common), but you can
# also ask for the json format in the format option
# format: json
# By default, the level is set to ERROR. Alternative logging levels are DEBUG, PANIC, FATAL, ERROR, WARN, and INFO.
level: ERROR
access:
# To enable access logs
enabled: false
# By default, logs are written using the Common Log Format (CLF).
# To write logs in JSON, use json in the format option.
# If the given format is unsupported, the default (CLF) is used instead.
# format: json
# To write the logs in an asynchronous fashion, specify a bufferingSize option.
# This option represents the number of log lines Traefik will keep in memory before writing
# them to the selected output. In some cases, this option can greatly help performances.
# bufferingSize: 100
# Filtering https://docs.traefik.io/observability/access-logs/#filtering
filters: {}
# statuscodes: "200,300-302"
# retryattempts: true
# minduration: 10ms
# Fields
# https://docs.traefik.io/observability/access-logs/#limiting-the-fieldsincluding-headers
fields:
general:
defaultmode: keep
names: {}
# Examples:
# ClientUsername: drop
headers:
defaultmode: drop
names: {}
# Examples:
# User-Agent: redact
# Authorization: drop
# Content-Type: keep
metrics:
datadog:
address: <IP_ADDRESS>:8125
influxdb:
address: localhost:8089
protocol: udp
prometheus:
entryPoint: metrics
statsd:
address: localhost:8125
globalArguments:

"--global.checknewversion"
"--global.sendanonymoususage"

Configure Traefik static configuration
Additional arguments to be passed at Traefik's binary
All available options available on https://docs.traefik.io/reference/static-configuration/cli/
Use curly braces to pass values: helm install --set="additionalArguments={--providers.kubernetesingress.ingressclass=traefik-internal,--log.level=DEBUG}"
additionalArguments:

--api
--api.insecure=true
#- --configfile=/etc/traefik/traefik.yaml
#- --insecureskipverify            #如果后端服务是https协议时不验证其证书
#- --defaultEntryPoints=http,https #traefik同时开启HTTP和HTTPS服务
--entrypoints=Name:https Address::443 TLS #HTTPS服务监听在443端口
--entrypoints=Name:http Address::80 #HTTPS服务监听在443端口，与http跳转https配置冲突，只能配置一项；
#- --entrypoints=Name:http Address::80 Redirect.EntryPoint:https #HTTP监听在80端口，并将流量重定向至https
--certificatesresolvers.letsencrypt.acme                         #开启证书验证
<EMAIL_ADDRESS> #用于注册的邮箱地址
--certificatesresolvers.letsencrypt.acme.storage=/data/acme.json  #证书申请临时文件存储位置
#- --certificatesresolvers.letsencrypt.acme.acmeLogging=true        #打开日志，方便排错
#- --certificatesresolvers.letsencrypt.acme.entryPoint=https        #证书类型，必需指向到一个443端口
#- --certificatesresolvers.letsencrypt.acme.httpchallenge.entrypoint=http    # 验证域名时使用的协议
--certificatesresolvers.letsencrypt.acme.dnschallenge                     # 域名验证方式
--certificatesresolvers.letsencrypt.acme.dnschallenge.provider=alidns     # 域名提供商
--certificatesresolvers.letsencrypt.acme.dnschallenge.delaybeforecheck=5  # 验证域名延时

- "--providers.kubernetesingress.ingressclass=traefik-internal"
- "--log.level=DEBUG"
Environment variables to be passed to Traefik's binary
env:

name: ALICLOUD_ACCESS_KEY              # 添加环境变量ALICLOUD_ACCESS_KEY
value: LTAI52t1HPvR1s1NxrEwSs4tntL7              # 阿里云RAM账号的access_key
name: ALICLOUD_SECRET_KEY              # 添加环境变量ALICLOUD_SECRET_KEY
value: B9dfmPX2mbfs3ZbKa4gPp1Mx1QCBTsNcOhG                  # 阿里云RAM账号的access_secret
#env: []

- name: SOME_VAR
value: some-var-value
- name: SOME_VAR_FROM_CONFIG_MAP
valueFrom:
configMapRef:
name: configmap-name
key: config-key
- name: SOME_SECRET
valueFrom:
secretKeyRef:
name: secret-name
key: secret-key
envFrom: []
- configMapRef:
name: config-map-name
- secretRef:
name: secret-name
Configure ports
ports:
The name of this one can't be changed as it is used for the readiness and
liveness probes, but you can adjust its config to your liking
traefik:
port: 8080
# Use hostPort if set.
# hostPort: 9000
#
# Use hostIP if set. If not set, Kubernetes will default to <IP_ADDRESS>, which
# means it's listening on all your interfaces and all your IPs. You may want
# to set this value if you need traefik to listen on specific interface
# only.
# hostIP: <IP_ADDRESS>
# Override the liveness/readiness port. This is useful to integrate traefik
# with an external Load Balancer that performs healthchecks.
# healthchecksPort: 9000

# Defines whether the port is exposed if service.type is LoadBalancer or
# NodePort.
#
# You SHOULD NOT expose the traefik port on production deployments.
# If you want to access it from outside of your cluster,
# use `kubectl port-forward` or create a secure ingress
expose: true
# The exposed port for this service
exposedPort: 8080
# The port protocol (TCP/UDP)
protocol: TCP

web:
port: 8000
# hostPort: 8000
expose: true
exposedPort: 80
# The port protocol (TCP/UDP)
protocol: TCP
# Use nodeport if set. This is useful if you have configured Traefik in a
# LoadBalancer
# nodePort: 32080
# Port Redirections
# Added in 2.2, you can make permanent redirects via entrypoints.
# https://docs.traefik.io/routing/entrypoints/#redirection
#redirectTo: websecure
websecure:
port: 8443
# hostPort: 8443
expose: true
exposedPort: 443
# The port protocol (TCP/UDP)
protocol: TCP
# nodePort: 32443
# Set TLS at the entrypoint
# https://doc.traefik.io/traefik/routing/entrypoints/#tls
tls:
enabled: true
# this is the name of a TLSOption definition
options: foobar
certResolver: foobar #letsencrypt
#domains: []
domains:
- main: wxaiops.com
sans: "*.wxaiops.com"
metrics:
port: 9100
# hostPort: 9100
# Defines whether the port is exposed if service.type is LoadBalancer or
# NodePort.
#
# You may not want to expose the metrics port on production deployments.
# If you want to access it from outside of your cluster,
# use kubectl port-forward or create a secure ingress
expose: true
# The exposed port for this service
exposedPort: 9100
# The port protocol (TCP/UDP)
protocol: TCP
TLS Options are created as TLSOption CRDs
https://doc.traefik.io/traefik/https/tls/#tls-options
Example:
tlsOptions:
default:
sniStrict: true
preferServerCipherSuites: true
foobar:
curvePreferences:
- CurveP521
- CurveP384
tlsOptions: {}
Options for the main traefik service, where the entrypoints traffic comes
from.
service:
enabled: true
type: ClusterIP
#type: LoadBalancer
Additional annotations applied to both TCP and UDP services (e.g. for cloud provider specific config)
annotations: {}
Additional annotations for TCP service only
annotationsTCP: {}
Additional annotations for UDP service only
annotationsUDP: {}
Additional service labels (e.g. for filtering Service by custom labels)
labels: {}
Additional entries here will be added to the service spec.
Cannot contain type, selector or ports entries.
spec: {}
# externalTrafficPolicy: Cluster
# loadBalancerIP: "<IP_ADDRESS>"
# clusterIP: "<IP_ADDRESS>"
loadBalancerSourceRanges: []
# - <IP_ADDRESS>/32
# - <IP_ADDRESS>/16
externalIPs: ['<IP_ADDRESS>']
# - <IP_ADDRESS>
One of SingleStack, PreferDualStack, or RequireDualStack.
ipFamilyPolicy: SingleStack
Create HorizontalPodAutoscaler object.

autoscaling:
enabled: false
minReplicas: 1
maxReplicas: 10
metrics:
- type: Resource
resource:
name: cpu
targetAverageUtilization: 60
- type: Resource
resource:
name: memory
targetAverageUtilization: 60
Enable persistence using Persistent Volume Claims
ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
After the pvc has been mounted, add the configs into traefik by using the additionalArguments list below, eg:
additionalArguments:
- "--certificatesresolvers.le.acme.storage=/data/acme.json"
It will persist TLS certificates.
persistence:
enabled: true
name: data
existingClaim: ""
accessMode: ReadWriteOnce
#size: 128Mi
size: 2Gi
storageClass: ""
path: /data
annotations: {}
subPath: "" # only mount a subpath of the Volume into the pod
If hostNetwork is true, runs traefik in the host network namespace
To prevent unschedulabel pods due to port collisions, if hostNetwork=true
and replicas>1, a pod anti-affinity is recommended and will be set if the
affinity is left as default.
hostNetwork: false
Whether Role Based Access Control objects like roles and rolebindings should be created
rbac:
enabled: true
If set to false, installs ClusterRole and ClusterRoleBinding so Traefik can be used across namespaces.
If set to true, installs namespace-specific Role and RoleBinding and requires provider configuration be set to that same namespace
namespaced: false
Enable to create a PodSecurityPolicy and assign it to the Service Account via RoleBinding or ClusterRoleBinding
podSecurityPolicy:
enabled: false
The service account the pods will use to interact with the Kubernetes API
serviceAccount:
If set, an existing service account is used
If not set, a service account is created automatically using the fullname template
name: ""
Additional serviceAccount annotations (e.g. for oidc authentication)
serviceAccountAnnotations: {}
resources: {}
requests:
cpu: "100m"
memory: "50Mi"
limits:
cpu: "300m"
memory: "150Mi"
affinity: {}
# This example pod anti-affinity forces the scheduler to put traefik pods
# on nodes where no other traefik pods are scheduled.
# It should be used when hostNetwork: true to prevent port conflicts
podAntiAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
- labelSelector:
matchExpressions:
- key: app
operator: In
values:
- {{ template "traefik.name" . }}
topologyKey: failure-domain.beta.kubernetes.io/zone
nodeSelector: {}
tolerations: []
Pods can have priority.
Priority indicates the importance of a Pod relative to other Pods.
priorityClassName: ""
Set the container security context
To run the container with ports below 1024 this will need to be adjust to run as root
securityContext:
capabilities:
drop: [ALL]
readOnlyRootFilesystem: true
runAsGroup: 65532
runAsNonRoot: true
runAsUser: 65532
podSecurityContext:
fsGroup: null
#fsGroup: 65532

sorry  it sees  format issue, i will send u values.yml  by email

| |
zwd19880317
|
|
@.***
|
签名由网易邮箱大师定制
Hi , Samuel,
Thank you for your great support. The  attachment is my values file.
 Friendship remind：  the access key and values is not right.

env:

name: ALICLOUD_ACCESS_KEY              # 添加环境变量ALICLOUD_ACCESS_KEY
value: LTAI52t1HPvR1s1NxrEwSs4ntL7              # 阿里云RAM账号的access_key
name: ALICLOUD_SECRET_KEY              # 添加环境变量ALICLOUD_SECRET_KEY
value: B9dfmPX2mbfs3ZbKa4gPp1Mx1QCBTsNcOhG                  # 阿里云RAM账号的access_secret

On 05/15/2022 @.***> wrote：
Could you please provide your value file.
Are setting some volumes?
Would any of those miss a type?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Roles and responsibilities high level picture

Within the final section a high-level overview of the roles and responsibilities of the team might be valuable for getting the context across. https://review.docs.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/data-management/strategy?branch=collab-data-mesh-v1#foster-commitment-communication-and-engagement
I could imagine that this picture might help here:

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

ID: 42a648bf-51ec-f9da-6c4f-d721616fcdb1
Version Independent ID: 7bdb8bfa-289e-bee5-bc45-a0a6fb78d5ff
Content: Integrate data management and analytics into your cloud adoption strategy - Cloud Adoption Framework
Content Source: docs/scenarios/data-management/strategy.md
Service: cloud-adoption-framework
Sub-service: scenario
GitHub Login: @BrianBlanchard
Microsoft Alias: brblanch

Have a look at the following section, and add what we need to add, we are adding some of the stuff from MS Digital as well:
https://review.docs.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/data-management/organize?branch=collab-data-mesh-v1

#assign: @mboswell

We have a drawing like this but needs to be tidied up before it is ready for public consumption.
#label:"data management and analytics"

@simonlid I think this article  describes it quite well, which is indeed linked with the initial content. Nevertheless, I think a picture here would also be beneficial for the reader.

@ralphke and @mboswell - It looks like this issues was reported on an in-progress collaboration branch. If this was not addressed prior to publication of that branch, can you open a new issue from the published doc?


DRILL-6824: Handle schema changes in MapRDBJsonRecordReader

@amansinha100 can you please review the PR? Thanks!

@gparai can you describe the issue ? The JIRA does not have much details.  Thanks.

Based on the description in the JIRA, the changes lgtm.   +1


Fix CIDR ingress lookup

test-me-please

test-me-please

test-me-please

test-me-please

04:04:13     k8s2-1.10: E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
04:04:13     k8s2-1.10: E: Unable to lock directory /var/lib/apt/lists/
04:04:13 The SSH command responded with a non-zero exit status. Vagrant
04:04:13 assumes that this means the command failed. The output for this command
04:04:13 should be in the log above. Please read the output to determine what
04:04:13 went wrong.


Erroe

Exception encountered while executing operation ServiceApiError: Could not match JWT signature to any of the bindings
i have used the same configuration file structure as provided in the esample

@gigikj  - Thanks for posting the question. This error typically comes when there is an issue in the input private key.
Could you please check 2 things in your configuration -

The contents of your private.key file.
The private.key file reference in your JSON file.

The JSON contains the path and name of the private key file and the private key file actually contains the key. Could you please check if the above 2 configurations are correct in your setup?
Please let us know if you still face any difficulties. We would be happy to help.


fix: change Buf to Protoc for proto generating

Hi @b00f
Description
based on our discussion about Buf and Protoc in ./Makefile in Discord, I fixed the Buf problem with replace it with Protoc .
the make proto command did not work correctly and I tried to fix it
Related issue(s)

Fixes #590 (.proto problems)

@ZigBalthazar I think we still need the removed files in .py, .js, and ...


feature request: expose client api

i'm really enjoying using this, it would be nice if we could create websocket clients too

Unfortunately the turbo-http library currently only has the server implementation. If they ever add an HTTP client we could reconsider adding this.

Maybe a turbo-ws-client library would make more sense? :)

Still, the main feature of this project is that it uses the turbo-http library, and if the base on which this package is built doesn't support them yet imo there's no "good" way to do it other than going for a replacement which works such as the ws library.


Git.clone with cli arguments returns invalid repo path

I want to be able to specify command line arguments directly to clone, the returned repository has an invalid path assigned.
Here are some examples:
URL followed by cli arguments:
iex(20)> {_, repo} = Git.clone ["https://github.com/tuvistavie/elixir-git-cli", "--depth=1"]
{:ok, %Git.Repository{path: "/private/tmp/--depth=1"}}
iex(21)> Git.pull repo
spawn: Could not cd to /private/tmp/--depth=1
{:error, %Git.Error{args: [], code: 2, command: "pull", message: ""}}

CLI arguments, followed by URL
iex(24)> {_, repo} = Git.clone ["--depth=1", "https://github.com/tuvistavie/elixir-git-cli"]
{:ok,
 %Git.Repository{
   path: "/private/tmp/https:/github.com/tuvistavie/elixir-git-cli"
 }}
iex(25)> Git.pull repo
spawn: Could not cd to /private/tmp/https:/github.com/tuvistavie/elixir-git-cli
{:error, %Git.Error{args: [], code: 2, command: "pull", message: ""}}

Currently using something along these lines as a workaround for http/s urls:
clone = fn(repo, args) ->
 Git.clone! [repo] ++ args
 URI.parse(repo).path
 |> Path.rootname
 |> Path.basename
 |> Git.new
end

Thanks for reporting. This should be fixed in the latest version.


URI forward error

Hi folks,
I'm little bit stucked (actually for few days :-)) within authorization process.
I've installed duckdns and nginx add-ons a week ago, and my router port forwarding is set from outer duckdns 8088 to 443 inside. HTTPS approach to hass is going pretty well.
In Azure environment I set URI address as a https://:8088/api/o365, and in a configuration.yaml I'd set http: row only according this https://help.konnected.io/support/solutions/articles/32000023964-set-up-hass-io-with-secure-remote-access-using-duckdns-and-nginx-proxy (without any basic_url).
I'm not able (like a newbie) to find what is wrong, in every try there is only one answer - invalid_request: The provided value for the input parameter 'redirect_uri' is not valid. The expected value is a URI which matches a redirect URI registered for this client application.
Can anybody help me? Some suggestion or hint? Probably there is a problem between a chair and a keyboard I suppose.
Really appreciated any hint ...
Thanks

Hi, im stucked too, but maybe this could help
https://github.com/PTST/O365-HomeAssistant
The reply URL specified in the request does not match the reply URLs configured for the application.
Please ensure that you have configured base_url in your http config https://www.home-assistant.io/integrations/http/#base_url and that you have added the correct reply url to your Azure app

Hi, im stucked too, but maybe this could help
https://github.com/PTST/O365-HomeAssistant
The reply URL specified in the request does not match the reply URLs configured for the application.
Please ensure that you have configured base_url in your http config https://www.home-assistant.io/integrations/http/#base_url and that you have added the correct reply url to your Azure app

Hi, im stucked too, but maybe this could help
https://github.com/PTST/O365-HomeAssistant
The reply URL specified in the request does not match the reply URLs configured for the application.
Please ensure that you have configured base_url in your http config https://www.home-assistant.io/integrations/http/#base_url and that you have added the correct reply url to your Azure app

I have found a solution
You have to set in configuration.yaml file
o365:
alt_auth_flow: true
Then redirect uri in your Azure app set to "https://login.microsoftonline.com/common/oauth2/nativeclient"
And finally open the notification in HA to login to your account

Hi, im stucked too, but maybe this could help
https://github.com/PTST/O365-HomeAssistant
The reply URL specified in the request does not match the reply URLs configured for the application.
Please ensure that you have configured base_url in your http config https://www.home-assistant.io/integrations/http/#base_url and that you have added the correct reply url to your Azure app

I have found a solution
You have to set in configuration.yaml file
o365:
alt_auth_flow: true
Then redirect uri in your Azure app set to "https://login.microsoftonline.com/common/oauth2/nativeclient"
And finally open the notification in HA to login to your account

@vania137 Thank you so much for this! LEGEND!
Been stuck for hours on this and your comment to use alt_auth_flow had it working in 2 mins haha


Show tooltip why Metrics feature can't be installed

Describe the bug
Install Metrics button is disabled. Can't install prometheus to see metrics.
What am I doing wrong?
To Reproduce
Steps to reproduce the behavior:

Go to 'Cluster configuration'
Scroll down to 'Features'
Click on 'Install' for metrics

Expected behavior
Button is enabled, Prometheus is installing
Screenshots

Environment (please complete the following information):

Lens Version: 3.5.3
OS: Windows 10

Do you have cluster-admin rights to the cluster? Installation of Metrics feature requires that.

@nevalla, oh, it seems I don't.
If that's the reason, it would be nice to have a comprehensive description why the button is not enabled.

@jakolehm @nevalla Hi, it seems it is fixed by next-day commit
The line fixing the issue.
Please close it


Filetype exclude not work

My config
require("retrail").setup({
  -- Enabled filetypes.
  filetype = {
    -- Strictly enable only on `include`ed filetypes. When false, only disabled
    -- on an `exclude`ed filetype.
    strict = false,
    -- Included filetype list.
    include = {},
    -- Excluded filetype list. Overrides `include` list.
    exclude = {
      'help', 'startify', 'dashboard', 'packer', 'neogitstatus', 'nvimtree', 'trouble', 'alpha',
      'lir', 'Outline', 'spectre_panel', 'toggleterm', 'qf'
    }
  }
})

Dashboard still have highlight

Filetype is 'dashboard'

But when i do something like toggle the neo-tree, or close the lspinfo banner in the image above, it goes back to normal

Edit: I discover more, if the dashboard no longer have highlight, then it will "toggle" to my tree

Initial state

Hm ok, this is a sneaky bug.
It seems this is happening due your config not explicitly excluding "". Because of this, when Neovim launches (before the filetype is set to dashboard) the plugin checks and sees that "" isn't excluded and decides to enable itself on that window. This actually explains the behaviour you're seeing with nvim-tree as well.
This is actually a regression from 6dd0fe7, where I removed the FileType autocommand firing a refresh. For now as a quick fix add "" as an excluded filetype. The obvious patch here is to re-introduce the FileType trigger, but this may have unintended consequences regarding issue #2, so further testing is required before I can push that.

Fixed. Let me know if the problem persists for you, otherwise please close this issue.
I believe issues #2, #3 should not be affected by this, but if you're getting the E803 error please comment on issue #3.

Thanks the dashboard now fixed but what about this, i try to exclude 'neo-tree' and got this

And also I don't if it relate, but I saw the 'retrail' in the error, when I navigate between neotree and dashboard

And if I open with dashboard, it will have the trailing highlight on neo-tree, if I open a file, it not, and navigate around normally

This should be fixed as well now. See #3.
Closing this issue since it was solved in bb30f21.

It still happen to me when i switch buffer, I update to the last commit


servicebinding reconciliation errors prevent binding from being deleted

If the ServiceBinding is in an error state, it can block deletion of the binding.
I've seen several examples of this:

Go through the walkthrough without starting the service broker.
A.  kubectl create -f contrib/examples/walkthrough/ups-broker.yaml
B.  kubectl create namespace test-ns
C.  kubectl create -f contrib/examples/walkthrough/ups-instance.yaml
D.  kubectl create -f contrib/examples/walkthrough/ups-binding.yaml
E.  At this point you can't get rid of the binding.  Try kubectl delete -n test-ns servicebindings ups-binding
F.  The instance can't be deleted either because of the associated binding.

I used a Service Broker that had a non-bindable ClusterServiceClass.  I created a binding, but then the controller just kept logging an error like " 'Warning' reason: 'ErrorNonbindableServiceClass' References a non-bindable ClusterServiceClass (K8S: "ab24ffd54da0aefdea5277e0edce8425" ExternalName: "dh-hastebin-apb") and Plan ("default") combination" and I couldn't delete the binding.

I'm kind of lite on the details in #2 but I can reproduce if necessary (OpenShift with the Ansible Service Broker and hastebin service).
I believe another variation of example 1 can be achieved by modifying contrib/examples/walkthrough/ups-instance.yaml to point to a bogus class name.

I am not sure that I understand the first point here.  At point (E), what state are the ServiceInstance and ServiceBinding in?  That would be helpful to put into this issue for posterity.

From what I understand, the service instance exists but does not revolve to a service instance class.
The Service Instance is in a ready false state, but because we don't do any checking on accepting the binding, the binding instance gets created and then gets stuck in reconciliation and at this point you can't delete the bad SI nor the bad Binding because the binding is waiting for a class to be resolved, and will never happen.
The root of the issue is we need more admission filtering: #1521, but a side effect of not filtering is we can make bindings on not-ready service instance states.

serviceinstance after step C (doesn't change with any of the following steps)
apiVersion: servicecatalog.k8s.io/v1beta1
kind: ServiceInstance
metadata:
  creationTimestamp: 2017-11-02T20:54:45Z
  finalizers:
  - kubernetes-incubator/service-catalog
  generation: 1
  name: ups-instance
  namespace: test-ns
  resourceVersion: "6"
  selfLink: /apis/servicecatalog.k8s.io/v1beta1/namespaces/test-ns/serviceinstances/ups-instance
  uid: 0e8390a8-c010-11e7-bc33-0242ac110006
spec:
  clusterServiceClassExternalName: user-provided-service
  clusterServicePlanExternalName: default
  externalID: 37be5ef6-507d-4b9d-b040-efc508ff3b6a
  parameters:
    credentials:
      param-1: value-1
      param-2: value-2
  updateRequests: 0
status:
  asyncOpInProgress: false
  conditions:
  - lastTransitionTime: 2017-11-02T20:54:45Z
    message: 'The instance references a ClusterServiceClass that does not exist. References
      a non-existent ClusterServiceClass (ExternalName: "user-provided-service") or
      there is more than one (found: 0)'
    reason: ReferencesNonexistentServiceClass
    status: "False"
    type: Ready
  deprovisionStatus: NotRequired
  orphanMitigationInProgress: false
  reconciledGeneration: 0

servicebinding after step d:
apiVersion: servicecatalog.k8s.io/v1beta1
kind: ServiceBinding
metadata:
  creationTimestamp: 2017-11-02T20:55:37Z
  finalizers:
  - kubernetes-incubator/service-catalog
  generation: 1
  name: ups-binding
  namespace: test-ns
  resourceVersion: "7"
  selfLink: /apis/servicecatalog.k8s.io/v1beta1/namespaces/test-ns/servicebindings/ups-binding
  uid: 2d7db517-c010-11e7-bc33-0242ac110006
spec:
  externalID: ace90acc-c199-4721-9631-e14a08281881
  instanceRef:
    name: ups-instance
  secretName: ups-binding
status:
  conditions: []
  orphanMitigationInProgress: false
  reconciledGeneration: 0

perhaps we should block creating the binding if the instance is in a ready=false state?

I think it's fine having the binding in a retry loop while the instance is getting its references resolved. What we should do is just allow for quick-n-easy deletions of bindings that haven't hit the broker yet.

We cannot block the creation of any API resource due to the status of another resource.  Users will put multiple resources into a single yaml and call it with kubectl create -f.  So, we have to converge on the right state.
So, for the record, in this case the binding is not ready, so it's not clear to my what specifically blocks the deletion of the binding.  Does that make sense?

Thanks Paul, that makes sense.
From the controller logs, it appears controller_binding must reconcile the binding before it will allow a deletion.  And that always results in an error:
I1102 23:54:02.220632       1 controller.go:232] Error syncing ServiceBinding test-ns/ups-binding: ClusterServiceClass or ClusterServicePlan references for Instance have not been resolved yet
I1102 23:54:04.780854       1 controller_binding.go:165] ServiceBinding "test-ns/ups-binding": beginning to process resourceVersion: 49
I1102 23:54:04.780882       1 controller_binding.go:190] ServiceBinding "test-ns/ups-binding": Processing
I1102 23:54:04.780893       1 controller.go:232] Error syncing ServiceBinding test-ns/ups-binding: ClusterServiceClass or ClusterServicePlan references for Instance have not been resolved yet
I1102 23:54:08.865379       1 controller_manager.go:363] Health-checking connection with service-catalog API server
I1102 23:54:08.866680       1 controller_manager.go:259] Created client for API discovery
I1102 23:54:08.933092       1 controller_binding.go:81] ServiceBinding test-ns/ups-binding: received ADD/UPDATE event for: resourceVersion: 51
I1102 23:54:08.933224       1 controller_binding.go:165] ServiceBinding "test-ns/ups-binding": beginning to process resourceVersion: 51
I1102 23:54:08.933293       1 controller_binding.go:190] ServiceBinding "test-ns/ups-binding": Processing
I1102 23:54:08.933326       1 controller.go:232] Error syncing ServiceBinding test-ns/ups-binding: ClusterServiceClass or ClusterServicePlan references for Instance have not been resolved yet
I1102 23:54:09.929602       1 controller_binding.go:165] ServiceBinding "test-ns/ups-binding": beginning to process resourceVersion: 51
I1102 23:54:09.929638       1 controller_binding.go:190] ServiceBinding "test-ns/ups-binding": Processing
I1102 23:54:09.929650       1 controller.go:232] Error syncing ServiceBinding test-ns/ups-binding: ClusterServiceClass or ClusterServicePlan references for Instance have not been resolved yet
I1102 23:54:10.456455       1 controller_manager.go:363] Health-checking connection with service-catalog API server

Looking one last time at the servicebinding, I do see the deletion timestamp on there after issuing the delete:
[jaboyd@jboyd service-catalog (last-reconciled)]$ kubectl get servicebinding ups-binding -n test-ns -o yaml
apiVersion: servicecatalog.k8s.io/v1beta1
kind: ServiceBinding
metadata:
  creationTimestamp: 2017-11-02T20:55:37Z
  deletionGracePeriodSeconds: 0
  deletionTimestamp: 2017-11-02T23:54:08Z
  finalizers:
  - kubernetes-incubator/service-catalog
  generation: 2
  name: ups-binding
  namespace: test-ns
  resourceVersion: "51"
  selfLink: /apis/servicecatalog.k8s.io/v1beta1/namespaces/test-ns/servicebindings/ups-binding
  uid: 2d7db517-c010-11e7-bc33-0242ac110006
spec:
  externalID: ace90acc-c199-4721-9631-e14a08281881
  instanceRef:
    name: ups-instance
  secretName: ups-binding
status:
  conditions: []
  orphanMitigationInProgress: false
  reconciledGeneration: 0


inquiry on the selex type:42

Hi, I am just looking source codes for selex type 42 ( an 27) (SS_Label_Info_22.7.27 and SS_Label_Info_22.3.27) in SS_selex.tpl
Regardless of age or size selectivity, if selex type is 42, 1st parameter (sp(1) seems to have two roles i.e., "code" and "low_bin". On the other hand  sp(3) seems to be not used if selex type is 42. I am wondering if "low_bin" and "high_bin" should point to sp(2) and sp(3) respectively for selex type 42.

Thanks @yukio-takeuchi, there's definitely a bug in there which I think is my fault due to the changes introduced in this pull request: https://github.com/nmfs-stock-synthesis/stock-synthesis/pull/241 from January where I erroneously assumed that the first parameter is always the code, when in fact it appears that for selectivity pattern 42, the two extra bin range parameters precede the remaining parameters as indicated by the parameter labeling here: https://github.com/nmfs-stock-synthesis/stock-synthesis/blob/main/SS_readcontrol_330.tpl#L3398-L3404.
I've attempted a fix in commit 54b2993.
@yukio-takeuchi and @Rick-Methot-NOAA, can you look this over to see if the change makes sense or if we should make further modifications before opening a pull request?
I can also improve the documentation for selex pattern 42 to clarify the parameter order.

Thanks @iantaylor-NOAA for your quick work. It seems, the change is relevant to make type 42 workable.
Thanks again.

Thanks @yukio-takeuchi for taking a look.
@Rick-Methot-NOAA, I just opened PR #364 so you can just review this once if it looks OK.


feat: add a switch to control the auto-updating for mod file

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

2. What is the scope of this PR (e.g. component or file name):

add a switch to control the auto-updating for mod file
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

16 of 25 (64.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 41.92%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/client/update.go
11
13
84.62%

pkg/package/package.go
0
7
0.0%

Totals

Change from base Build<PHONE_NUMBER>7:
0.04%

Covered Lines:
4153

Relevant Lines:
9907

💛  - Coveralls


Use consistent naming in Properties panel

If we have to keep this weird tab in the UI, it should at least be consistent with every other mention of the VPL e.g. Node > Patch. Explanation > Select a patch to see its properties.

but a patch is a collection of nodes. This functionality relates to a single node.

Well no, in common user parlance, a patch is the basic unit of the VPL. There are various types eg nested patches etc.

keeping this. as discussed


No authentication issue for Custom HTTP Error pages.

Laravel Version: 5.6
PHP Version: 7.1.3
Database Driver & Version: MySQL

Description:
Not being able to get authenticated user on Custom HTTP Error pages stored in "resources/views/errors/*" files For example: "404.blade.php".

Yes. The session isn't available for these views. There are, however, ways to do this. See https://themsaid.com/laravel-55-better-404-response-20170921


Fix push with no configured module names

Read the config file to determine if a module name is present before trying to push to the remote. On no configured modules skip both push and archive steps.

Need to fix multi-module pushes.


Add files upload

@chinoel I am sorry, the domain student.kyungnam.ac.kr is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Fixed header: bug on Chrome in iOS

Hi!
Finding this bug ( http://imgur.com/a/j1WJl ) when I'm quickly swipe down on iOS.
The fixed header goes down a few pixels and I don't know why.
Has anyone had the same issue? thanks

Hi @jeanko84, could you share a url to watch this issue.


generateAuthUrl() generated url always asks for offline access

the generateAuthUrl() method generatates thee different urls for me, which differs from the access_type parameter
with access_type = 'online':
https://accounts.google.com/o/oauth2/auth?access_type=online&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile&response_type=code...

with access_type = 'offline':
https://accounts.google.com/o/oauth2/auth?access_type=offline&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile&response_type=code...

and without access_type (according to this example it should defaults to online):
https://accounts.google.com/o/oauth2/auth?scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile&response_type=code...

Regardless of the url, there is always a prompt asking for offline access.
The version of the library I've used: 0.9.6
The code I've used to generate the url:
var url = oauth2Client.generateAuthUrl({
    access_type: 'online',
    scope: 'https://www.googleapis.com/auth/userinfo.profile'
});

According to the OpenID documentation, access_type is optional and if it is absent, the server behaves as though it was "offline", which is exactly the behavior that the example indicates.
What is this "prompt asking for offline access"? I don't see anything like that in this library.

This prompt from google:

It seems that this only occurs, when my redirect_uri is localhost.

Greetings @Cir0X!  I'm having a little trouble reproducing this one.  I am using the example here:
https://github.com/google/google-auth-library-nodejs/blob/next/examples/oauth2.js
I changed the sample to use this for url generation, and even tried to force the consent dialog:
// Generate the url that will be used for the consent dialog.
const authorizeUrl = oAuth2Client.generateAuthUrl({
  access_type: 'offline',
  scope: [
    'https://www.googleapis.com/auth/userinfo.profile',
    'https://www.googleapis.com/auth/devstorage.read_write',
    'https://www.googleapis.com/auth/plus.me',
    'https://www.googleapis.com/auth/compute'
  ],
  prompt: 'consent select_account'
});

This generates a consent dialog, but nowhere does it ask me if I should allow offline access:

Note, my redirect_uri is set to localhost:3000.   I am also using the alpha npm release of our 1.0 library, which you can try out at npm install<EMAIL_ADDRESS>Given that this issue is nearly a year old, I'm going to go ahead and close it out.  if you can include detailed instructions on how to reproduce it - I'd be happy to take a look :)


Add option to set IPAM Helm deployment update strategy to Recreate

Description:  Add option to set IPAM Helm deployment update strategy to Recreate
Changes Proposed in PR: Added option to set IPAM Helm deployment update strategy to Recreate in the values.yaml
Fixes: #130
General Checklist

[x] Updated Added functionality/ bug fix in release notes
[x] Added examples for new feature
[x] Updated the troubleshooting guide or documentation

CRD Checklist

[x] Updated required CR schema

/azp run

/azp run

/azp run

/azp run


Remove the .new suffix inside the fips.checksum.new

This is urgent as there will always be a difference otherwise and the label will be always set.

@paulidale Could you please review? This unfortunately slipped through with the late change to use the .new suffix.

Hmm :(
But apparently this won't suffice and we might have to change the approach. Apparently setting the labels from the CI does not work. Probably due to some permissions problem.
Merging this anyway as the .new in the checksum needs to be fixed.

Merged. Thank you Tim for the swift review. Now on to the problem with setting labels.

Would just having the 'Checksum' build fail if their is a difference suffice for now (instead of doing the label?)

Would just having the 'Checksum' build fail if their is a difference suffice for now (instead of doing the label?)

I suppose it is the Workflow permissions setting in the repository settings. I suppose this is set to read-only for the openssl repository. I have it set to read write in the forked repo and that is the reason it works in the fork.
Not sure if we want to change that setting. If not, we will have to settle for the checksum fail meaning fips change.

I do not have access to the repository settings for the openssl/openssl repo to verify. I suppose only @openssl/omc members have.


Uncaught Error: The specified module could not be found./?~\AppData\Local\atom\app-1.54.0\res...

[Enter steps to reproduce:]

...
...

Atom: 1.54.0 x64
Electron: 6.1.12
OS: Unknown Windows version
Thrown From: Atom Core
Stack Trace
Uncaught Error: The specified module could not be found.
\?\C:\Users\danie\AppData\Local\atom\app-1.54.0\resources\app.asar.unpacked\node_modules\keyboard-layout\build\Release\keyboard-layout-manager.node
At electron/js2c/asar.js:138

Error: The specified module could not be found.
\\?\C:\Users\danie\AppData\Local\atom\app-1.54.0\resources\app.asar.unpacked\node_modules\keyboard-layout\build\Release\keyboard-layout-manager.node
    at process.func (electron/js2c/asar.js:138:31)
    at process.func [as dlopen] (electron/js2c/asar.js:138:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:828:18)
    at Object.func (electron/js2c/asar.js:138:31)
    at Object.func [as .node] (electron/js2c/asar.js:147:18)
    at Module.load (internal/modules/cjs/loader.js:645:32)
    at Function.Module._load (internal/modules/cjs/loader.js:560:12)
    at Module.require (/app.asar/static/index.js:72:46)
    at require (internal/modules/cjs/helpers.js:16:16)
    at customRequire (~/AppData/Local/atom/app-1.54.0/resources/app/static/<embedded>:1:723602)
    at get_KeyboardLayoutManager (~/AppData/Local/atom/app-1.54.0/resources/app/static/<embedded>:14:2799883)
    at get_manager (~/AppData/Local/atom/app-1.54.0/resources/app/static/<embedded>:14:2799985)
    at Object.getCurrentKeyboardLayout (~/AppData/Local/atom/app-1.54.0/resources/app/static/<embedded>:14:2800111)
    at e.keystrokeForKeyboardEvent (~/AppData/Local/atom/app-1.54.0/resources/app/static/<embedded>:14:1057803)
    at KeymapManager.keystrokeForKeyboardEvent (~/AppData/Local/atom/app-1.54.0/resources/app/static/<embedded>:11:1228079)
    at KeymapManager.handleKeyboardEvent (~/AppData/Local/atom/app-1.54.0/resources/app/static/<embedded>:11:1226064)
    at WindowEventHandler.handleDocumentKeyEvent (~/AppData/Local/atom/app-1.54.0/resources/app/static/<embedded>:11:284879)

Commands
     -2:50.5.0 core:save (input.hidden-input)

Non-Core Packages
80-synth-neon 2.6.0
emmet 2.4.3

Thanks for taking the time to contribute!
We noticed that this is a duplicate of https://github.com/atom/atom/issues/21285. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.a


How to delete

I apologize for the stupid question but right-clicking and selecting "Delete Aerial" inside the screensaver preferences does not work. The only reason I want to delete it is because I have two versions,one being the latest beta and I can't tell which is which. Thanks for your help and thanks so much for creating this.
-Running Yosemite 10.10.5, 2012 Mac Mini
Ryan

The screensaver will either be in /Users/YOURUSERNAME/Library/Screen Savers or /Library/Screen Savers. You can just delete it from there and it'll disappear from System Preferences.

Please close this issue if you've solved your problem.

Hi @hellonearth9,
Did you manage to uninstall the screensaver?

Waited months, no reply, so closing.


Transloco Locale License

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[x] Other... Please describe:

Current behavior
Transloco Locale package does not have a license associated.
Expected behavior
Add a license similar to Transloco main package https://github.com/ngneat/transloco/blob/master/LICENSE

The package.json is also missing the license property field.
Lack of licensing details might actually make your code not open-source:
http://opensource.stackexchange.com/q/1720/775

@AnttiApina We are looking into the licenses 😃


[BUG FIX] Add space type default and ef search parameter in warmup

Description
Warmup is used to load native library files into memory so that there are no initial latency penalties during search. The load process for search and warmup are very similar.
Currently, warmup api has a similar bug to #267. It does not default to a space type. For customers upgrading to 1.2 from ES 7.1 or 7.4 this will cause warmup failure. This only applies to 1.2. 1.1 and 1.0 do not have this bug in warmup.
Additionally, for nmslib, we allow the ef_search parameter to be set after indexing. To do this, we pass the parameter in during loading. In 1.2, we did not pass this parameter in. This will cause default ef_search to be used during warmup. To clean this up a bit, I abstracted generating load parameters into a utility function and used the same one for both search as well as warmup.
Issues Resolved
#255
Check List

[X] New functionality includes testing.

[X] All tests pass

[X] New functionality has been documented.

[X] New functionality has javadoc added

[X] Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #276 (fd8bd5e) into main (18e6e35) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##               main     #276   +/-   ##
=========================================
  Coverage     83.38%   83.38%
- Complexity      884      885    +1
=========================================
  Files           127      127
  Lines          3833     3834    +1
  Branches        361      361
=========================================
+ Hits           3196     3197    +1
  Misses          475      475
  Partials        162      162

Impacted Files
Coverage Δ

.../main/java/org/opensearch/knn/index/IndexUtil.java
56.66% <100.00%> (+3.93%)
:arrow_up:

...n/java/org/opensearch/knn/index/KNNIndexShard.java
93.02% <100.00%> (+0.16%)
:arrow_up:

.../main/java/org/opensearch/knn/index/KNNWeight.java
75.34% <100.00%> (-1.59%)
:arrow_down:

Continue to review full report at Codecov.

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


Choosing someone outside the initial 8

Hi,
Playing with the example application and I wonder how one selects a person outside the initial group of 8 displayed in the view.  Is there a gesture for cycling through all the people?

Hello!
Unfortunately, there is no such option as the control was intended for a limited number of people. I could actually take some time and create a selector list as a separate to choose and remove people? as well as displaying the whole list at once.

Thanks for replying.  I can appreciate that dealing with an unbounded list makes this much more completed.  Perhaps some gesture for circling through the people.  Anyway, nice work.


setup github actions through UI

you're killing me github

CI fails, because there is no test project yet, but should start succeeding once #59 is merged

Merged but suggest fixing that typo


Windows browser is not on hue

I configured the hue configuration file ip and port, but still can not visit, suggesting that can not access this site
[root@localhost /]# cd hue-release-3.6.0
[root@localhost hue-release-3.6.0]# build/env/bin/supervisor &
[1] 2706
[root@localhost hue-release-3.6.0]# starting server with options {'ssl_certificate': None, 'workdir': None, 'server_name': 'localhost', 'host': '<IP_ADDRESS>', 'daemonize': False, 'threads': 10, 'pidfile': None, 'ssl_private_key': None, 'server_group': 'hue', 'ssl_cipher_list': 'DEFAULT:!aNULL:!eNULL:!LOW:!EXPORT:!SSLv2', 'port': 8001, 'server_user': 'hue'}

3.6 is very old Hue.
Make sure
http_host=<IP_ADDRESS>
http_port=8000
so that the server listen from other hosts. Then <IP_ADDRESS>:8000 should open Hue

Thank you very much！The firewall of my centos is opened that can access this site!


Allow version to work despite connectivity

Can tower-cli please ...
a) permit 'version' to work even if there's no connectivity...
(pip)MBP:~$ tower-cli version
Error: There was a network error of some kind trying to connect to Tower.

The most common  reason for this is a settings issue; is your "host" value in `tower-cli config` correct?
Right now it is: "<IP_ADDRESS>".

b) permit --version, the same as for ansible/ansible-playbook commands
Thanks!

@phips Implemented in #188. Will come with tower-cli 3.0.0

Magic, thanks @jangsutsr!
Does it also work before trying to connect to the tower configure in the .cfg?

@phips That's how it works. We reversed the sequence of display tower-cli version and tower version, which internally mean cli's version will be displayed regardless of the state of remote tower server.


Memory Error When Pickling

I am getting MemoryError when writing out checkpoints consistently around the time 40 simulations have run (70k atoms, 8 rounds of 5 trajectories at 5ns each) using MaxEnt. I am using g5xlarge nodes on AWS (NVIDIA A10g; 16Gb RAM) and the pickle dump crashes around 5Gb written which is not adding up to me. Per the author of dill (in this thread: https://stackoverflow.com/questions/17513036/pickle-dump-huge-file-without-memory-error) it seems that maybe the klepto package would be more suitable for writing these checkpoints out.
In the meantime is it possible to restart from the log files rather than the checkpoints? I was writing out checkpoints every 5 rounds and it would be nice to not have to restart from 5 rounds ago, but either way I plan to run without checkpointing for the time being.

Serializing the entire simulation object might be impractical for large systems. I used this approach for convenience, but I will work on writing a method to restart a simulation object from the logs only. This would be basically an alternative constructor that reads the pickle file and performs some operations on the saved trajectory files. This will require that all the trajectory files are available exactly where the file handler object expects them. Please be patient as adding these changes might take a while because I have other responsibilities.
I was not aware of the klepto package. I still have to assess how easy it would be to replace dill with this package, but I will look into it!

Klepto is by the same author as dill and actually uses dill under the hood from my understanding. They gave an example of using it to serialize a large object in the stackoverflow page I linked.
I had one other question regarding how memory is handled in the MaxEnt workflow: are all of the openmm trajectories being stored in memory? I have my system crash somewhere in the range of 100-250ns pretty consistently and suspect this may be to blame, but am new to openmm so not sure. I should have mentioned this in my original post but I am using explicit solvent simulations with a class I wrote which inherits the InVacuoSim class in the same manner as the implicit solvent class (and as such my system is ~80k atoms).

I'm already working on the new restart procedure that uses the log files. That should be sorted out pretty soon.
About your second question: the trajectories are not stored in memory, but their projections in the collective variable space and the VAMPNet-transformed space are. If you are using a large number of collective variables (for example, all residue-pair distances) for a large protein, then you would probably run into issues. In this case, I suggest that you narrow down the collection of collective variables that go into the EntropyBasedSampling.features parameter.
I am looking at ways to improve the data efficiency so that there is no memory bloating. However, this will involve a significant amount of writing/reading .npy files to/from disk, which might result in slower execution.

This is great thank you! I appreciate all the time you have spent on this and the framework has been very useful so far.


Update package.json

added ability to use npm start for default gulp task, and npm test for gulp dev task

Not sure if PR's are being accepted, but this is just a helper idea.

Whats the benefit of doing this over just using gulp and gulp dev? Just curious :)

totally reasonable question my friend. No benefit. None. Zilch. Nada. Zero. Null. /dev/null.
Just offering since some JS devs have a common practice of running everything through npm scripts. Apart from that, they're totally reasonable people...(if you know your monty python).


Set New Date Header on Request Retry

This PR resolves an issue where the Date header wouldn't be updated on request retry. If the Date header isn't updated on request retry this could lead to an issue where the Date header becomes stale and is no longer considered valid by the service, correcting the pipelines created by the client builders to do so resolves this issue.

@gapra-msft or @rickle-msft when you get a chance could I get a review on this PR


Github workflow init

python-package-yml will run everytime someone pushes stuff to main
this can also be changed to be run on every pr before merging to main

The actions do not pass without tests so that should be fixed.
Github Actions should be also run when PR has been updated. This can be done with the following:
  push:
    branches:
      - master
  pull_request:
    branches: [master]
    types: [opened, synchronize]

A broken build should not be deployed to Heroku. If @vuorenkoski could add the relevant secrets to Github (nobody can read them after they have been set), this job could be used at  the end of CI:
    - name: Deploy to Heroku
      if: ${{ github.event_name == 'push' }}
      uses<EMAIL_ADDRESS>      with:
        heroku_api_key: ${{secrets.HEROKU_API_KEY}}
        heroku_app_name: "quantmark"
        heroku_email: ${{secrets.HEROKU_EMAIL}}

The actions do not pass without tests so that should be fixed.
Github Actions should be also run when PR has been updated. This can be done with the following:
  push:
    branches:
      - master
  pull_request:
    branches: [master]
    types: [opened, synchronize]

A broken build should not be deployed to Heroku. If @vuorenkoski could add the relevant secrets to Github (nobody can read them after they have been set), this job could be used at  the end of CI:
    - name: Deploy to Heroku
      if: ${{ github.event_name == 'push' }}
      uses<EMAIL_ADDRESS>      with:
        heroku_api_key: ${{secrets.HEROKU_API_KEY}}
        heroku_app_name: "quantmark"
        heroku_email: ${{secrets.HEROKU_EMAIL}}

The actions do not pass without tests so that should be fixed.
Github Actions should be also run when PR has been updated. This can be done with the following:
  push:
    branches: [main]
  pull_request:
    branches: [main]
    types: [opened, synchronize]

A broken build should not be deployed to Heroku. If @vuorenkoski could add the relevant secrets to Github (nobody can read them after they have been set), this job could be used at the end of CI:
    - name: Deploy to Heroku
      if: ${{ github.event_name == 'push' && matrix.python_version == '3.7' }}
      uses<EMAIL_ADDRESS>      with:
        heroku_api_key: ${{secrets.HEROKU_API_KEY}}
        heroku_app_name: "quantmark"
        heroku_email: ${{secrets.HEROKU_EMAIL}}

Implemented these to the workflow now

The actions do not pass without tests so that should be fixed.
Github Actions should be also run when PR has been updated. This can be done with the following:
  push:
    branches: [main]
  pull_request:
    branches: [main]
    types: [opened, synchronize]

A broken build should not be deployed to Heroku. If @vuorenkoski could add the relevant secrets to Github (nobody can read them after they have been set), this job could be used at the end of CI:
    - name: Deploy to Heroku
      if: ${{ github.event_name == 'push' && matrix.python_version == '3.7' }}
      uses<EMAIL_ADDRESS>      with:
        heroku_api_key: ${{secrets.HEROKU_API_KEY}}
        heroku_app_name: "quantmark"
        heroku_email: ${{secrets.HEROKU_EMAIL}}

Implemented these to the workflow now