qdrant vector store support

Expected Behavior
Qdrant vector database is not currently supported by Spring AI
Current Behavior
Qdrant vector database support along with all other vector stores as its benmarking is out performs all others.
Context
We are using Qdrant vector store to have all the embeddings stored, indexed and searched out of it.
So we would like Sping AI to support it.

Hi @radhakrishna67. I'll try to contribute this feature.

@Anush008 this will be appreciated!


helm delete rel-name --pruge wont delete kublet scraper service

What happened?
$: helm install stable/prometheus-operator --name rel-name
fin with code: 0
$: helm delete rel-name --purge
fin with code: 0
$: kubectl get service -n kube-system
NAME    TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)         AGE
kube-dns    ClusterIP   <IP_ADDRESS>      <none>        53/UDP,53/TCP   4d
metrics-server    ClusterIP   <IP_ADDRESS>   <none>        443/TCP         4d
rel-name-prometheus-operat-kubelet    ClusterIP   None             <none>        10250/TCP      8m15s
tiller-deploy    ClusterIP   <IP_ADDRESS>    <none>        44134/TCP       4d

Did you expect to see some different?
I would expect this service would have been deleted.
How to reproduce it (as minimally and precisely as possible):
-> same as What happened?
Environment
$: helm version
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}

Prometheus Operator version:

quay.io/coreos/prometheus-operator:v0.30.1

Kubernetes version information:

$: kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:23:09Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:02:58Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:

rke up --config myConfig.yaml

kubectl get nodes
NAME                     STATUS   ROLES                           AGE    VERSION
kubeh-1.intern   Ready    controlplane,etcd,node,worker   4d1h   v1.14.1
kubeh-2.intern   Ready    node,worker                     4d1h   v1.14.1
kubeh-3.intern   Ready    node,worker                     4d1h   v1.14.1

Anything else we need to know?:
kubectl describe service -n kube-system rel-name-prometheus-operat-kubelet
Name:              rel-name-prometheus-operat-kubelet
Namespace:         kube-system
Labels:            k8s-app=kubelet
Annotations:       <none>
Selector:          <none>
Type:              ClusterIP
IP:                None
Port:              https-metrics  10250/TCP
TargetPort:        10250/TCP
Endpoints:         <IP_ADDRESS>:10250,<IP_ADDRESS>:10250,<IP_ADDRESS>:10250
Session Affinity:  None
Events:            <none>

kubectl get service -n kube-system rel-name-prometheus-operat-kubelet -o yaml
apiVersion: v1
kind: Service
metadata:
  creationTimestamp: "2019-06-07T12:29:10Z"
  labels:
    k8s-app: kubelet
  name: rel-name-prometheus-operat-kubelet
  namespace: kube-system
  resourceVersion: "562541"
  selfLink: /api/v1/namespaces/kube-system/services/rel-name-prometheus-operat-kubelet
  uid: d9fcd27a-891f-11e9-81ae-005056ba4147
spec:
  clusterIP: None
  ports:
  - name: https-metrics
    port: 10250
    protocol: TCP
    targetPort: 10250
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

The helm chart is not part of this repo, nor is it used or maintained by us. Please report on the upstream helm charts repo.

The helm chart is not part of this repo, nor is it used or maintained by us. Please report on the upstream helm charts repo.


Spatial resolution of feature maps

Dear authors,
I have noticed the spatial resolution of the hierarchical feature maps are {1/2, 1/4, 1/8, 1/16} of the input resolution, which differs from the dimensions in your paper ( {1/4, 1/8, 1/16, 1/32} ). I guess this might be the cause why there are more than 33.56G FLOPs.

您好，请问关于MSCA的代码在哪儿呀，麻烦指路谢谢！


Closes: #1

Update validation.py python script
Fixed validate_user to check username doesn't start with . or _
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


Persisting the Spotify oauth information blows away the connectionStatus column in Dynamo

When the user authorizes the Twitch integration, we write a connectionStatus along with the rest of the record in DynamoDB. This is used as a status that is essential to the service.
When the user moves on and authorizes Spotify, this succeeds and updates the session token in Dynamo, but the connectionStatus field is now missing.

#39 closes this