text:
Using existing exceptions defined and newly defined exceptions to alter behavior of the get_collection, create_collectionanddelete_collection` methods

Description of changes
get_collection, delete_collection and create_collection methods raised a ValueError. This was descriptive for the user to find what the error was but was inconvenient because it was the same Exception type for two different scenarios.
Resolves https://github.com/chroma-core/chroma/issues/982
Summarize the changes made by this PR.

Improvements & Bug fixes

Scenario 1 is when the user tries to get or delete a collection which does not exist. There was an exception already created in chromadb.errors called InvalidCollectionException we raise that in the two methods.
Scenario 2 is when a user tries to create a collection which already excepts. To this we created a new error in chromadb.errors called CollectionAlreadyExistsError and raise that in the respective function

New functionality

Raising proper exceptions

@bhashithe-air thank you very much for the PR. I think the issue you have identified around the consistency of the API is important with people deploying Chroma extensively in a Client/Server mode.
Please have a look at my review comments regarding response codes and a new error for collection not found.

@tazarov Thanks!
What do you think about the InvalidCollectionException, currently for many situations where the error "collection not found"; InvalidCollectionException is being used. Should I change it to reflect the error you suggest CollectionNotFoundError?

@tazarov Thanks!
What do you think about the InvalidCollectionException, currently for many situations where the error "collection not found"; InvalidCollectionException is being used. Should I change it to reflect the error you suggest CollectionNotFoundError?

Well, it's about consistency, cognitive load and intuitive of the code. While I understand your point InvalidCollectionException does seem counter-intuitive and does make one wonder what is exactly not valid about the collection. Let's wait for @HammadB's feedback and then we plan further changes (or no changes).

It does seem counter intuitive yes, i am in favor of your suggestion to use a new exception. But yes, we shall wait for @HammadB :)

I agree the InvalidCollectionException is underdefined, I prefer NotFound and more prescriptive errors.

@bhashithe-air, It looks better now :).
One suggestion for future PRs - please setup GPG and sign your commits

Thanks @tazarov, just learnt about the GPG signing for commits, I will make sure to sign my commits in the future.
Do you think anything else is needed for this PR? should i look at the whole repo and see if we need to define anything new?

LGTM. There are many other things to "fix" on the API but this is a step in the right direction. @HammadB wdyt?

@bhashithe-air, can you rebase off main so tests can pass?

@tazarov I synced just now.

@tazarov what is the latest on this?

@bhashithe-air, can you rebase/merge from the main so things are up to date, or give me write access to your repo so that I can do it?

@tazarov I added you to the repository. Do not have too much time to work on it today.

@tazarov I added you to the repository. Do not have too much time to work on it today.

Thank you @bhashithe-air, I will rebase this shortly.

@bhashithe-air, I redid your PR from a non-main branch in a new PR #1618. Feel free to close this one.

authors: HammadB bhashithe-air jeffchuber tazarov


text:
Please invite me to the GitHub Community Organization

Name
Avid Coder
Discord Username (if applicable)
No response
Additional Context
I would like to join the chryz-hub community after contributing to the organization a few times. Please review this issue. Thanks (:

@AvidCoder101 You are welcome to ChryzHub

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Add DNS-based services for IP

Based on https://community.cloudflare.com/t/can-1-1-1-1-be-used-to-find-out-ones-public-ip-address/14971/8
(Normalized parameter order based on dig -h)

@ct-martin Very cool commands! Thank you

source: gharchive/pull-request

authors: chubin ct-martin

repo: chubin/awesome-console-services

license: mit

license_source: bigquery


text:
WEBSITE IS NOT FINDING ANY WEATHER

@chubin ANY location I type into wttr.in comes out as a 404! PLEASE HELP!

same for me, every city returns a 404 error

same for me, every city returns a 404 error

I hope he finds a fix. (It's probably the weather server he is using is down.)

same for me, every city returns a 404 error

I hope he finds a fix. (It's probably the weather server he is using is down.)

most probably, yeah

Please test it now

Please test it now

It still doesn't work

Please test it now

yup, now it works, atleast for me

nvm it works now, thank you

@chubin It works now, thanks!

authors: ManOfDiamond Sussy-OS chubin gw8ndal


text:
Personalized view date pickers in IE 11

Hi
I have a problem displaying (and changing the CSS) for a right display on IE11 (very large datepickers)
What can I do, the CSS isn't easy to adapt on it ....
I have no problem with chrome but the standard is IE
Thanks
Pierre

Hi,
Sorry but that scheduler has not been designed to work well with IE, nor to be edited. It has been tested with Edge but still requires Chrome or at least Firefox for a better experience.
I'm not sure to understand what you mean by "right display". Are you trying to make it work in RTL? If the problem is about the datepicker so you may wan't to ask your questions directly to the people managing this project.
Btw today you can't expect to have a good experience with a browser like IE.

authors: PierreGiboni chuck-durst

repo: chuck-durst/pit-scheduler


text:
Can't seem to change directory

My attempts to use cd to change to the directory I wish to run further commands in does not appear to be working. The verbose log does not display much either.

Thanks @aarontropy :+1:

authors: brunowego pmcatominey

repo: chuckmo/grunt-ssh


text:
Cannot download weights

Hi,
can someone please upload the YoloV4 weights trained on VisDrone2020 on Google Drive or wetransfer.com?
These one can only be downloaded from China:
https://pan.baidu.com/s/1zOFyt_AFiNk0fAFa8yE9RQ
Extract code：xblu
Best regards,
Walter

Hi @walzimmer :
Here  is the link https://drive.google.com/file/d/1dQDjCoGKPWeRz7z-0TJI8fAeKMx13JYi/view?usp=sharing  ,you can try this

Unfortunately the model does not detect vans using these weights. On what classes have you trained the network on for how long (num. of epochs)?

The download link is down

authors: chumingqian davidpob99 walzimmer


text:
🛑 Hacker News is down

In 57dd1f0, Hacker News (https://news.ycombinator.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Hacker News is back up in a211079.

repo: chungvku/status


text:
🛑 Crossker is down

In 297fd98, Crossker (https://crossker.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 生意网 is back up in ab34e2f after .

repo: chwang-team/status-hao


text:
关于补全Golang的问题

开发环境是Ubuntu18.04LTS，vimplus使用的是./install.sh默认安装的。补全golang的时候，单独把.ycm_extra_conf.py文件放到了项目环境下，同时添加了当前项目的路径为补全路径。golang的安装是使用的apt方式，且添加的补全路径包含了/usr/share/go/src和/usr/lib/go-1.12。现在遇到的问题是，可以补全文档下的内容，但是无法补全golang的自带函数。暂时没有找到解决方案。也可能是我对vim不熟悉导致的。希望有明白的人可以指点下问题的原因。以下给出个人的配置。只把改动过的代码贴出来了：
import os
import ycm_core

# These are the compilation flags that will be used in case there's no
# compilation database set (by default, one is not set).
# CHANGE THIS LIST OF FLAGS. YES, THIS IS THE DROID YOU HAVE BEEN LOOKING FOR.
flags = [
'-Wall',
'-Wextra',
'-Werror',
'-Wno-long-long',
'-Wno-variadic-macros',
'-fexceptions',
'-DNDEBUG',
# You 100% do NOT need -DUSE_CLANG_COMPLETER in your flags; only the YCM
# source code needs it.
'-DUSE_CLANG_COMPLETER',
# THIS IS IMPORTANT! Without a "-std=<something>" flag, clang won't know which
# language to use when compiling headers. So it will guess. Badly. So C++
# headers will be compiled as C headers. You don't want that so ALWAYS specify
# a "-std=<something>".
# For a C project, you would set this to something like 'c99' instead of
# 'c++11'.
'-std=c++14',
# ...and the same thing goes for the magic -x option which specifies the
# language that the files to be compiled are written in. This is mostly
# relevant for c++ headers.
# For a C project, you would set this to 'c' instead of 'c++'.
'-x',
'golang',

# golang
'-isystem',
'$GOPATH/src',
'-isystem',
'/usr/lib/go-1.12',
]

# Set this to the absolute path to the folder (NOT the file!) containing the
# compile_commands.json file to use that instead of 'flags'. See here for
# more details: http://clang.llvm.org/docs/JSONCompilationDatabase.html
#
# You can get CMake to generate this file for you by adding:
#   set( CMAKE_EXPORT_COMPILE_COMMANDS 1 )
# to your CMakeLists.txt file.
#
# Most projects will NOT need to set this to anything; you can just change the
# 'flags' list of compilation flags. Notice that YCM itself uses that approach.
compilation_database_folder = ''

if os.path.exists( compilation_database_folder ):
  database = ycm_core.CompilationDatabase( compilation_database_folder )
else:
  database = None

SOURCE_EXTENSIONS = [ '.cpp', '.cxx', '.cc', '.c', '.m', '.mm', '.go']

你需要重新编译ycm，Go support: install Go and add --go-completer when calling install.py.

谢谢，问题解决了。
Go support:
cd ~/.vim/plugged/YouCompleteMe/
./install.py --go-completer
Then add your GOPATH , GOROOT and your project path to .ycm_extra_conf.py

谢谢，问题解决了。
Go support:
cd ~/.vim/plugged/YouCompleteMe/
./install.py --go-completer
Then add your GOPATH , GOROOT and your project path to .ycm_extra_conf.py

你好，请问你是怎么解决的呀，目前我出现很奇怪的问题，在有的目录可以补全标准库，有的便不可以

@StudentErick 可以看指点一下我吗，我遇到这个问题了，没有办法解决，按照你这样操作了。

authors: StudentErick chxuan luozhongxiangsi zhuobo

repo: chxuan/vimplus


text:
Format-number with precision 0 for -0.2 is -0

{{format-number  -0.2 decimal='.' thousand=',' precision=0}}
Here Output is -0
But I want is only 0

This addon is just a port of accounting.js, nothing more.
Can you check if accounting.js itself has this bug and report it if it does? If that's the case, it has to be fixed in accounting.js first

Same issue has been reported in accounting.js -
https://github.com/openexchangerates/accounting.js/issues/174

In that case we'll have to wait until it's fixed there and then backport the fix

authors: cibernox lakhanbaheti

repo: cibernox/ember-cli-accounting


text:
CI: bugtool fails to gather bpftool-map-dump-pinned contents (invalid argument)

Bugtool output for all bpftool-map-dump-pinned is failing. For example:
bpftool-map-dump-pinned--sys-fs-bpf-tc-globals-cilium_ct_any4_global.md:
> Error while running 'bpftool map dump pinned /sys/fs/bpf/tc/globals/cilium_ct_any4_global':  exit status 255

Error: can't get map info: Invalid argument

As seen in: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/17996/testReport/junit/Suite-k8s-1/17/K8sFQDNTest_Validate_that_multiple_specs_are_working_correctly/attachments/06e2612a_K8sFQDNTest_Validate_that_multiple_specs_are_working_correctly.zip

Maybe related to #10353

More likely that Cilium is shut down before running bpftool?

repo: cilium/cilium


text:
CI: GKE: DNS 'testds-service.default.svc.cluster.local' is not ready after timeout: 7m0s timeout expired"

Observed in at least the following tests:

K8sServicesTest Bookinfo Demo Tests bookinfo demo
K8sChaosTest Connectivity demo application Endpoint can still connect while Cilium is not running
K8sKafkaPolicyTest Kafka Policy Tests KafkaPolicies

(Above three are from same cluster run)
Bookinfo example failure
6a65889e_K8sServicesTest_Bookinfo_Demo_Tests_bookinfo_demo.zip
Stacktrace
/home/jenkins/workspace/Cilium-PR-K8s-GKE@2/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:514
DNS entry is not ready after timeout
Expected
    <*errors.errorString | 0xc0007b05a0>: {
        s: "DNS 'productpage.default.svc.cluster.local' is not ready after timeout: 7m0s timeout expired",
    }
to be nil
/home/jenkins/workspace/Cilium-PR-K8s-GKE@2/src/github.com/cilium/cilium/test/k8sT/Services.go:2483

Standard Output
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 4
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
Top 1 errors/warnings:
Unable to update ipcache map entry on pod add
Cilium pods: [cilium-6dbvq cilium-7t5sr]
Netpols loaded:
CiliumNetworkPolicies loaded:
Endpoint Policy Enforcement:
Pod                                                         Ingress   Egress
grafana-7fd557d749-xb75b
kube-dns-7c976ddbdb-fd88z
reviews-v2-6588f4df97-t8hmb
fluentd-gke-scaler-cd4d654d7-8brx9
kube-dns-7c976ddbdb-gtmv4
metrics-server-v0.3.6-64655c969-qwrft
stackdriver-metadata-agent-cluster-level-5d5694494c-cgh42
prometheus-d87f8f984-jvc7m
productpage-v1-5c79cf49d-rxf4b
reviews-v1-75cfdb45f-dtfxj
l7-default-backend-678889f899-mzbq4
ratings-v1-6bbfd59bf-npxt2
event-exporter-gke-8489df9489-6zwht
kube-dns-autoscaler-645f7d66cf-rngdp
details-v1-6675f948f7-5c6rr
Cilium agent 'cilium-6dbvq': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 21 Failed 0
Cilium agent 'cilium-7t5sr': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 33 Failed 0

Standard Error
00:25:01 STEP: Running BeforeAll block for EntireTestsuite K8sServicesTest Bookinfo Demo
00:25:01 STEP: Creating objects in file "/home/jenkins/workspace/Cilium-PR-K8s-GKE@2/src/github.com/cilium/cilium/test/k8sT/manifests/bookinfo-v1.yaml"
00:25:02 STEP: Creating objects in file "/home/jenkins/workspace/Cilium-PR-K8s-GKE@2/src/github.com/cilium/cilium/test/k8sT/manifests/bookinfo-v2.yaml"
00:25:03 STEP: Waiting for pods to be ready
00:25:03 STEP: WaitforPods(namespace="default", filter="-l zgroup=bookinfo")
00:25:48 STEP: WaitforPods(namespace="default", filter="-l zgroup=bookinfo") => <nil>
00:25:51 STEP: Waiting for services to be ready
00:25:53 STEP: Validating DNS without Policy
FAIL: DNS entry is not ready after timeout
Expected
    <*errors.errorString | 0xc0007b05a0>: {
        s: "DNS 'productpage.default.svc.cluster.local' is not ready after timeout: 7m0s timeout expired",
    }
to be nil
=== Test Finished at 2020-10-31T00:32:53Z====
00:32:53 STEP: Running JustAfterEach block for EntireTestsuite K8sServicesTest
===================== TEST FAILED =====================
00:32:55 STEP: Running AfterFailed block for EntireTestsuite K8sServicesTest
cmd: kubectl get pods -o wide --all-namespaces
Exitcode: 0
Stdout:
 	 NAMESPACE           NAME                                                        READY   STATUS    RESTARTS   AGE     IP              NODE                                          NOMINATED NODE   READINESS GATES
	 cilium-monitoring   grafana-7fd557d749-xb75b                                    1/1     Running   1          114m    10.44.1.20      gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 cilium-monitoring   prometheus-d87f8f984-jvc7m                                  1/1     Running   1          114m    10.44.2.82      gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>
	 cilium              cilium-6dbvq                                                1/1     Running   0          12m     10.128.15.213   gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>
	 cilium              cilium-7t5sr                                                1/1     Running   0          12m     10.128.15.209   gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 cilium              cilium-node-init-hlrvq                                      1/1     Running   0          12m     10.128.15.213   gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>
	 cilium              cilium-node-init-jv2kx                                      1/1     Running   0          12m     10.128.15.209   gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 cilium              cilium-operator-7bf98cd8b5-hx6cx                            1/1     Running   0          12m     10.128.15.209   gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 cilium              cilium-operator-7bf98cd8b5-k447m                            1/1     Running   0          12m     10.128.15.213   gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>
	 cilium              log-gatherer-25fft                                          1/1     Running   0          114m    10.128.15.213   gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>
	 cilium              log-gatherer-8xfhl                                          1/1     Running   0          114m    10.128.15.209   gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 default             details-v1-6675f948f7-5c6rr                                 1/1     Running   0          8m      10.44.1.178     gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 default             productpage-v1-5c79cf49d-rxf4b                              1/1     Running   0          8m      10.44.1.95      gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 default             ratings-v1-6bbfd59bf-npxt2                                  1/1     Running   0          7m59s   10.44.1.51      gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 default             reviews-v1-75cfdb45f-dtfxj                                  1/1     Running   0          8m      10.44.1.170     gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 default             reviews-v2-6588f4df97-t8hmb                                 1/1     Running   0          7m59s   10.44.2.217     gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>
	 kube-system         event-exporter-gke-8489df9489-6zwht                         2/2     Running   0          112m    10.44.2.161     gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>
	 kube-system         fluentd-gke-57sj9                                           2/2     Running   0          115m    10.128.15.213   gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>
	 kube-system         fluentd-gke-scaler-cd4d654d7-8brx9                          1/1     Running   1          162m    10.44.1.4       gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 kube-system         fluentd-gke-wz2rq                                           2/2     Running   0          114m    10.128.15.209   gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 kube-system         gke-metrics-agent-69wzq                                     1/1     Running   0          116m    10.128.15.209   gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 kube-system         gke-metrics-agent-f6qjn                                     1/1     Running   0          116m    10.128.15.213   gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>
	 kube-system         kube-dns-7c976ddbdb-fd88z                                   4/4     Running   0          42m     10.44.1.24      gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 kube-system         kube-dns-7c976ddbdb-gtmv4                                   4/4     Running   0          42m     10.44.2.28      gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>
	 kube-system         kube-dns-autoscaler-645f7d66cf-rngdp                        1/1     Running   1          162m    10.44.2.122     gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>
	 kube-system         kube-proxy-gke-cilium-ci-20-cilium-ci-20-2437f719-83df      1/1     Running   0          116m    10.128.15.209   gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 kube-system         kube-proxy-gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9      1/1     Running   0          116m    10.128.15.213   gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>
	 kube-system         l7-default-backend-678889f899-mzbq4                         1/1     Running   1          162m    10.44.1.22      gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 kube-system         metrics-server-v0.3.6-64655c969-qwrft                       2/2     Running   2          116m    10.44.2.30      gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>
	 kube-system         prometheus-to-sd-6g2f2                                      1/1     Running   0          116m    10.128.15.213   gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>
	 kube-system         prometheus-to-sd-cjtxz                                      1/1     Running   0          116m    10.128.15.209   gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 kube-system         registry-adder-2sxzk                                        1/1     Running   1          116m    10.128.15.209   gke-cilium-ci-20-cilium-ci-20-2437f719-83df   <none>           <none>
	 kube-system         registry-adder-l6t2l                                        1/1     Running   0          116m    10.128.15.213   gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>
	 kube-system         stackdriver-metadata-agent-cluster-level-5d5694494c-cgh42   2/2     Running   3          116m    10.44.2.172     gke-cilium-ci-20-cilium-ci-20-2437f719-r2w9   <none>           <none>

Stderr:

Fetching command output from pods [cilium-6dbvq cilium-7t5sr]
cmd: kubectl exec -n cilium cilium-6dbvq -- cilium service list
Exitcode: 0
Stdout:
 	 ID   Frontend              Service Type   Backend
	 1    10.47.253.48:80       ClusterIP      1 => 10.44.1.22:8080
	 2    10.128.15.213:31321   NodePort       1 => 10.44.1.22:8080
	 3    0.0.0.0:31321         NodePort       1 => 10.44.1.22:8080
	 4    10.47.245.53:443      ClusterIP      1 => 10.44.2.30:443
	 5    10.47.240.1:443       ClusterIP      1 => 34.105.67.212:443
	 6    10.47.242.56:3000     ClusterIP      1 => 10.44.1.20:3000
	 7    10.47.240.10:53       ClusterIP      1 => 10.44.1.24:53
	                                           2 => 10.44.2.28:53
	 8    10.47.250.45:9090     ClusterIP      1 => 10.44.2.82:9090
	 12   10.47.240.106:9080    ClusterIP      1 => 10.44.1.178:9080
	 13   10.47.255.239:9080    ClusterIP      1 => 10.44.2.217:9080
	                                           2 => 10.44.1.170:9080
	 14   10.47.241.219:9080    ClusterIP      1 => 10.44.1.95:9080
	 15   10.47.254.40:9080     ClusterIP      1 => 10.44.1.51:9080

Stderr:

cmd: kubectl exec -n cilium cilium-6dbvq -- cilium endpoint list
Exitcode: 0
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                  IPv6   IPv4          STATUS
	            ENFORCEMENT        ENFORCEMENT
	 935        Disabled           Disabled          1          k8s:cilium.io/ci-node=k8s2                                                        ready
	                                                            k8s:cloud.google.com/gke-nodepool=cilium-ci-20
	                                                            k8s:cloud.google.com/gke-os-distribution=cos
	                                                            reserved:host
	 1470       Disabled           Disabled          4          reserved:health                                                     10.44.2.81    ready
	 3302       Disabled           Disabled          28243      k8s:app=reviews                                                     10.44.2.217   ready
	                                                            k8s:io.cilium.k8s.namespace.labels.istio-injection=enabled
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:version=v2
	                                                            k8s:zgroup=bookinfo

Stderr:

cmd: kubectl exec -n cilium cilium-7t5sr -- cilium service list
Exitcode: 0
Stdout:
 	 ID   Frontend              Service Type   Backend
	 1    10.47.245.53:443      ClusterIP      1 => 10.44.2.30:443
	 2    10.47.240.1:443       ClusterIP      1 => 34.105.67.212:443
	 3    10.47.250.45:9090     ClusterIP      1 => 10.44.2.82:9090
	 4    10.47.253.48:80       ClusterIP      1 => 10.44.1.22:8080
	 5    10.128.15.209:31321   NodePort       1 => 10.44.1.22:8080
	 6    0.0.0.0:31321         NodePort       1 => 10.44.1.22:8080
	 7    10.47.240.10:53       ClusterIP      1 => 10.44.1.24:53
	                                           2 => 10.44.2.28:53
	 8    10.47.242.56:3000     ClusterIP      1 => 10.44.1.20:3000
	 12   10.47.240.106:9080    ClusterIP      1 => 10.44.1.178:9080
	 13   10.47.255.239:9080    ClusterIP      1 => 10.44.2.217:9080
	                                           2 => 10.44.1.170:9080
	 14   10.47.241.219:9080    ClusterIP      1 => 10.44.1.95:9080
	 15   10.47.254.40:9080     ClusterIP      1 => 10.44.1.51:9080

Stderr:

cmd: kubectl exec -n cilium cilium-7t5sr -- cilium endpoint list
Exitcode: 0
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                  IPv6   IPv4          STATUS
	            ENFORCEMENT        ENFORCEMENT
	 321        Disabled           Disabled          1          k8s:cilium.io/ci-node=k8s1                                                        ready
	                                                            k8s:cloud.google.com/gke-nodepool=cilium-ci-20
	                                                            k8s:cloud.google.com/gke-os-distribution=cos
	                                                            reserved:host
	 662        Disabled           Disabled          43839      k8s:app=reviews                                                     10.44.1.170   ready
	                                                            k8s:io.cilium.k8s.namespace.labels.istio-injection=enabled
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:track=stable
	                                                            k8s:version=v1
	                                                            k8s:zgroup=bookinfo
	 1771       Disabled           Disabled          12038      k8s:app=ratings                                                     10.44.1.51    ready
	                                                            k8s:io.cilium.k8s.namespace.labels.istio-injection=enabled
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:version=v1
	                                                            k8s:zgroup=bookinfo
	 1991       Disabled           Disabled          5847       k8s:app=details                                                     10.44.1.178   ready
	                                                            k8s:io.cilium.k8s.namespace.labels.istio-injection=enabled
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:track=stable
	                                                            k8s:version=v1
	                                                            k8s:zgroup=bookinfo
	 3101       Disabled           Disabled          9342       k8s:app=productpage                                                 10.44.1.95    ready
	                                                            k8s:io.cilium.k8s.namespace.labels.istio-injection=enabled
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:track=stable
	                                                            k8s:version=v1
	                                                            k8s:zgroup=bookinfo
	 3964       Disabled           Disabled          4          reserved:health                                                     10.44.1.176   ready

Stderr:

===================== Exiting AfterFailed =====================
00:33:48 STEP: Running AfterEach for block EntireTestsuite K8sServicesTest
00:33:49 STEP: Running AfterEach for block EntireTestsuite

[[ATTACHMENT|6a65889e_K8sServicesTest_Bookinfo_Demo_Tests_bookinfo_demo.zip]]
00:33:50 STEP: Running AfterAll block for EntireTestsuite K8sServicesTest Bookinfo Demo
00:33:50 STEP: Deleting resource /home/jenkins/workspace/Cilium-PR-K8s-GKE@2/src/github.com/cilium/cilium/test/k8sT/manifests/bookinfo-v1.yaml
00:33:51 STEP: Deleting resource /home/jenkins/workspace/Cilium-PR-K8s-GKE@2/src/github.com/cilium/cilium/test/k8sT/manifests/bookinfo-v2.yaml
00:33:52 STEP: Running AfterAll block for EntireTestsuite K8sServicesTest
00:33:52 STEP: Removing Cilium installation using generated helm manifest

This might somehow be caused by the K8sUpdates test since the GKE builds were green in the backport PR as soon as we removed the unquarantine of K8sUpdates. We might need to quarantine that test again :sweat:

Some initial findings (having run the quarantined K8sUpdates locally, followed by K8sIstioTest):
The reason why DNS lookups for Kubernetes services is not working, is because kube-dns is unable to connect to the K8s API server (normal DNS requests are served just fine):
$ kubectl logs -n kube-system kube-dns-7c976ddbdb-h7n6n -c kubedns
1125 10:55:52.262228       1 reflector.go:201] k8s.io/dns/pkg/dns/dns.go:193: Failed to list *v1.Service: Get https://10.39.240.1:443/api/v1/services?resourceVersion=0: dial tcp 10.39.240.1:443: i/o timeout
E1125 10:55:52.263123       1 reflector.go:201] k8s.io/dns/pkg/dns/dns.go:190: Failed to list *v1.Endpoints: Get https://10.39.240.1:443/api/v1/endpoints?resourceVersion=0: dial tcp 10.39.240.1:443: i/o timeout

An interesting observation here is that while the kube-dns pods are present in the CiliumEndpoints CRD, they are not considered managed endpoints by the cilium agent hosting them:
kubectl get cep -n kube-system
NAME                                                       ENDPOINT ID   IDENTITY ID   INGRESS ENFORCEMENT   EGRESS ENFORCEMENT   VISIBILITY POLICY   ENDPOINT STATE   IPV4          IPV6
event-exporter-gke-8489df9489-crshm                        2403          13780                                                                        ready            10.36.1.171
fluentd-gke-scaler-cd4d654d7-zttd5                         2805          53097                                                                        ready            10.36.2.46
kube-dns-7c976ddbdb-h7n6n                                  1793          5861                                                                         ready            10.36.1.137
kube-dns-7c976ddbdb-ksghm                                  2510          5861                                                                         ready            10.36.0.13
kube-dns-autoscaler-645f7d66cf-lcxcz                       1523          40043                                                                        ready            10.36.0.92
l7-default-backend-678889f899-w7kh8                        1063          2248                                                                         ready            10.36.1.176
metrics-server-v0.3.6-64655c969-bdcjn                      2121          36505                                                                        ready            10.36.0.71
stackdriver-metadata-agent-cluster-level-9dccb99b4-v5qh4   843           785                                                                          ready            10.36.2.254

$ kubectl get pod -n kube-system kube-dns-7c976ddbdb-h7n6n -o wide
NAME                        READY   STATUS    RESTARTS   AGE   IP            NODE                                                  NOMINATED NODE   READINESS GATES
kube-dns-7c976ddbdb-h7n6n   4/4     Running   0          20h   10.36.1.137   gke-sebastian-ci-force-2-default-pool-5077a7b5-5whr   <none>           <none>
$ kubectl get pod -n cilium -l k8s-app=cilium -o wide
NAME           READY   STATUS    RESTARTS   AGE   IP              NODE                                                  NOMINATED NODE   READINESS GATES
cilium-cq2kb   1/1     Running   0          20h   10.172.15.218   gke-sebastian-ci-force-2-default-pool-5077a7b5-xh88   <none>           <none>
cilium-n68zj   1/1     Running   0          20h   10.172.15.217   gke-sebastian-ci-force-2-default-pool-5077a7b5-6zcs   <none>           <none>
cilium-qslrp   1/1     Running   0          20h   10.172.15.216   gke-sebastian-ci-force-2-default-pool-5077a7b5-5whr   <none>           <none>
$ kubectl exec -n cilium -ti cilium-qslrp -- cilium endpoint list
ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                  IPv6   IPv4          STATUS
           ENFORCEMENT        ENFORCEMENT
174        Disabled           Disabled          4          reserved:health                                                     10.36.1.245   ready
528        Disabled           Disabled          1          k8s:cilium.io/ci-node=k8s1                                                        ready
                                                           k8s:cloud.google.com/gke-nodepool=default-pool
                                                           k8s:cloud.google.com/gke-os-distribution=cos
                                                           reserved:host

Some additional observations and theories:
The CEP garbage collector will not remove an entry if a pod with the same name still exists (source). It seems fair to assume that if there is a pod for a given CEP, that the entry is valid, because Cilium will restore any already existing endpoints from the bpf maps on the host.
However, in the case of K8sUpdates, it seems that we are explicitly cleaning up the BPF state between updates (source). The CEPs on the other hand seem to be kept (?). This leads to the above symptom where the CEP and pod exists, but the actual datapath endpoint does not.
Being an unmanaged pod on GKE is known to cause connectivity issues. This is why we restart all unmanaged pods on the GKE test suite (source). The RestartUnmanagedPodsInNamespace does not work here, because the kube-dns pods have existing CEPs, they are not restarted here, leading to the above connectivity issues.
It seems like one way to fix this would be to make sure to clean up the CEPs as well if we do ciliumCleanup in CI, assuming the CEP GC behavior is intended.

The cleanup in K8sUpdates test is intended to reset the cluster to a 'fresh' deployment of the old version of Cilium prior to performing the upgrade testing, so I think it would be reasonable to clear out all of the CEPs in that specific case.

Still happening here: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.13-net-next/387/testReport/junit/Suite-k8s-1/13/K8sServicesTest_Bookinfo_Demo_Tests_bookinfo_demo/, re-opening to encourage further reporting.

Still happening here: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.13-net-next/387/testReport/junit/Suite-k8s-1/13/K8sServicesTest_Bookinfo_Demo_Tests_bookinfo_demo/, re-opening to encourage further reporting.

The new failure did not happen on GKE, so it probably has a different root cause then the previous issue (which was very GKE specific). I'm unassigning myself for now from this.

The new failure did not happen on GKE, so it probably has a different root cause then the previous issue (which was very GKE specific). I'm unassigning myself for now from this.

Given title of this issue mentions GKE, I think we should track the failure you're seeing @jrajahalme in a separate issue. As Sebastian mentioned, a fix for the GKE specific variant has been made.

Given title of this issue mentions GKE, I think we should track the failure you're seeing @jrajahalme in a separate issue. As Sebastian mentioned, a fix for the GKE specific variant has been made.

Given title of this issue mentions GKE, I think we should track the failure you're seeing @jrajahalme in a separate issue. As Sebastian mentioned, a fix for the GKE specific variant has been made.

Hit the same failure as reported by @jrajahalme in https://github.com/cilium/cilium/issues/13833#issuecomment-757166485, opened #14598 to track the failure.

Given title of this issue mentions GKE, I think we should track the failure you're seeing @jrajahalme in a separate issue. As Sebastian mentioned, a fix for the GKE specific variant has been made.

Hit the same failure as reported by @jrajahalme in https://github.com/cilium/cilium/issues/13833#issuecomment-757166485, opened #14598 to track the failure.

authors: christarazi gandro joestringer jrajahalme pchaigno tklauser


text:
etcd: Fix gRPC load balancer issue

This bumps the etcd dependency in order to pull in
github.com/etcd-io/etcd/pull/11184 which is required to fix a gRPC load
balancer issue when using a k8s service name to connect to etcd.
Fixes: #9791
The upstream description of the issue can be found here:
https://github.com/etcd-io/etcd/issues/11176

This change is

test-me-please

Coverage increased (+0.003%) to 45.557% when pulling 21d06c1856f6712d559146ab748e412e768f824e on pr/tgraf/update-to-etcd-stable into 6d583fddff183b81b3a03400011d89bed31c503e on master.

authors: coveralls tgraf


text:
bpf: xdp generalization prep work

Last bigger chunk of changes needed for XDP that touches many places in our code base. After that, only local changes coming that don't require rebase anymore.

This change is

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

provision failure

test-me-please

test-me-please


text:
cilium.io/v2: move files around to reduce imports in API

The API should not have implementation functionality embedded in it. To
reduce the amount of footprint given when importing all of these
libraries we should the functionality logic out of the API package.
Signed-off-by: André Martins andre@cilium.io

test-me-please

Coverage decreased (-0.06%) to 44.617% when pulling 5bbf3da7727e0bbf79ee9f065a1b8cac54366c27 on pr/move-cilium-types into e99049ffbaf8d0ffae91feb0fe67413d86c67937 on master.

test-gke

Thanks for this!

authors: aanm coveralls davetashner


text:
v1.7 backports 2020-06-10

#11952 -- service: Clean up HealthCheckNodePort server when traffic policy changes  (@gandro)

Dropped testsuite changes due to major conflicts

#11947 -- Fix EndpointSlice support (@aanm)

Minor conflict due to v1.7 not using slim k8s structures

#11974 -- cilium: fixes transparent encryption (@jrfastab)

@jrfastab helped with the backport here, PTAL. Dropped second commit.

#11998 -- cilium, test: Only run sockops tests on 4.19 and bpf-next kernels (@jrfastab)

Minor conflicts, dropping 4.19 skip since v1.7 doesn't run v4.19 CI.

#11891 -- etcd: propagate Context from higher-level calls (@tklauser)

Once this PR is merged, you can update the PR labels via:
$ for pr in 11952 11947 11974 11998 11891; do contrib/backporting/set-labels.py $pr done 1.7; done

Skipping the following backports:

#11995 -- test: Wait for POD policy revision increment in all cases. (@jrajahalme)

Significant conflicts; I tried just pulling the version of the changes
from the PR but that resulted in test compile failures in code that
apparently doesn't exist in master, so naive conflict resolution is not
sufficient to provide a good backport. Dropping.

Several others where the authors have already been notified recently to
backport their PRs.

test-backport-1.7

test-backport-1.7

test-missed-k8s

authors: aanm joestringer


text:
docs: Update KPR limitations wrt IPsec

KPR is supported with Wireguard, but not with IPSec. This update of the docs reflects that.
Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[ ] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[ ] All commits are signed off. See the section Developer’s Certificate of Origin
[ ] Provide a title or release-note blurb suitable for the release notes.
[ ] Thanks for contributing!

Update of the KPR limitations page as KPR is supported with Wireguard but not with IPSec.
<!-- Enter the release note text here if needed or remove this section! -->

The Documentation workflow passed. There are no changes to the docs structure. Merging.

authors: pchaigno raymonddejong


text:
v1.14 Backports 2024-05-11

[ ] #32367 (@sayboras)

Once this PR is merged, a GitHub action will update the labels of these PRs:
 32367

/test-backport-1.14


text:
encryption: fix encryption when using ip pools

The refactoring in https://github.com/cilium/cilium/pull/8757/files removed code which causes bpf compilation to fail when using ip pools (tunnel_endpoint not declared)
I added what I believe to be the missing code back (tested successfully on our test cluster)
cc @jrfastab

This change is

code is fine but needs another patch to update daemon/sha, just run below.
make -C ./daemon apply-bindata

I did and added the file in my commit
It also compiles fine locally on my latptop
Could it be because I ran it from mac os?

strange, maybe try manual rebase and run the command again see if anything changes. Not sure why Mac would make any difference.

Executing the same command inside the build container generated a different sha
The check seems to be ok now

Coverage increased (+0.007%) to 44.155% when pulling 01d644f412a88720b700c554dab73aee6bcf5cfb on DataDog:lbernail/fix-netdev-encrypt-pools into a96d7f4fece419e714e726f3501e008ce61b88ac on cilium:master.

test-me-please

@lbernail Looks good. The commit needs a sign-off. We can wait until the CI has run before we rebase.

Sorry I forgot the sign-off. I just added it

test-me-please

authors: coveralls jrfastab lbernail tgraf


text:
Support local testing with one k8s VM.

Delete all old VMs regardless of the value of K8S_NODES.
Do not try to reprovision k8s2 when K8S_NODES=1.

This change is

never-give-me-the-odds

never-tell-me-the-odds

Coverage decreased (-0.005%) to 46.059% when pulling 35d4f8ea655978f016d4e68c3409e9543697c00c on pr/jrajahalme/local-testing-fixes into f694b3ba28ac2936c413fddec7771ef14a2c8808 on master.

test-me-please

authors: coveralls jrajahalme


text:
v1.5 backports 2020-01-09

#9821 -- identity: require global identity for empty labels (@borkmann)

Once this PR is merged, you can update the PR labels via:
$ for pr in 9821; do contrib/backporting/set-labels.py $pr done 1.5; done

This change is

sorry :(


text:
Remove --enable-process-ancestors flag

Tetragon does not use this flag, so let's just remove it instead of deprecating it first.

Yep wishful thinking it never existed.

authors: jrfastab michi-covalent

repo: cilium/tetragon


text:
🛑 CIOOS Pacific ERDDAP dataset DFO_MEDS_BUOYS is down

In e2c4612, CIOOS Pacific ERDDAP dataset DFO_MEDS_BUOYS (https://data.cioospacific.ca/erddap/tabledap/DFO_MEDS_BUOYS.htmlTable?STN_ID&time>=now-1week&distinct()) was down:

HTTP code: 502
Response time: 134 ms

Resolved: CIOOS Pacific ERDDAP dataset DFO_MEDS_BUOYS is back up in 6372aad after 7 minutes.

repo: cioos-siooc/cwatch-upptime


text:
Update sbt-ghpages to 0.7.0

Updates com.typesafe.sbt:sbt-ghpages from 0.6.3 to 0.7.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.sbt", artifactId = "sbt-ghpages" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "com.typesafe.sbt", artifactId = "sbt-ghpages" }
}]

labels: sbt-plugin-update, early-semver-major, semver-spec-minor, commit-count:1

Superseded by #205.

repo: circe/circe-spire


text:
ScalaJS support

As far as I understand, circe-yaml is not published as a ScalaJs lib.
Is there something I miss? If not, is there something preventing compilation into ScalaJs?
Thanks for your answer.

If not, is there something preventing compilation into ScalaJs?

Yes, this library depends on the Java Snake Yaml library, which isn't available for Scala.js (since it's written in Java).
Until recently, there weren't any YAML parsers written in pure Scala AFAIK. But now there is one from VirtusLab, so I created a fork of this project that uses it instead and cross-publishes for Scala.js
https://github.com/armanbilge/circe-scala-yaml/releases/tag/v0.0.1

Thanks very much for the link and the project, it looks really cool.

authors: armanbilge mbaechler

repo: circe/circe-yaml


text:
Can't zoom after creating a mobi file

Hi, I've used the tool in the past to convert manga, without problems. I updated yesterday to 5.13 and redownloaded kindlegen, and after converting a manga for my PW2 I am unable to zoom with both fingers as I used to be able to. I checked an old manga converted before with KCC and it zooms flawlessly. I also went as far as using the same source files for this old manga and converting it again with the updated version, and the same thing happens, can't zoom.
If it helps, when I try to zoom it just kinda refreshes the screen and 4 black squares appear for a second on the lower right part of it.
Also, panel mode works, and I can -kinda- zoom if I'm inside a panel, but it gets weird most of the time.
I'm attaching one pic of the normal view and another pic of what happens when I try to zoom.
Thanks in advance for any help you can give me, love your app nonetheless.

Huh it look like panel view stuck. You getting that black screen on every page?

Yes, when I try to zoom. It comes back to normal after a second, it's not like I get stuck there.

And on rectangular pages with graphic?

Yes, it's the same in every page. I can double tap the screen for panel view, and it works normally, separating the page into 4 zones that I can navigate, and I can zoom when I'm inside any of those zones (although it's somewhat buggy, I can't explain it clearly but the zoom resets to one of the corners sometimes). But if I exit panel mode (back to normal view), when I try to zoom, it just gives that black screen with the squares for a second and does nothing else. It doesn't hang kindle or anything, it simply does nothing. So, bottomline, I can't zoom normally, hahaha

Pinch zoom was always buggy. It never worked correctly for me. I think that one of firmware updates changed pinch zoom behavior and in combination with 5.x KCC changes this function was crippled completely.
And I doubt it will be back. Sorry.

I thought as much and installed 4.x, which brought back the zoom, so I
guess I'm sticking to that version, hahaha. Thanks anyways for your help!

Pinch zoom support will be back in 5.3.

authors: AcidWeb KiryuuKazuma

repo: ciromattia/kcc

license: ISC


text:
config --cache-dir appears not to be honoured, TART_HOME is honoured but doesn't work with external drive where command line client does

We have just bought a new SSD (mounted at /Volumes/SSD/) for extra storage and are attempting to use it to store Tart cache files.
Passing ['--cache-dir','/Volumes/SSD/tart/cache'] to gitlab-tart-executor config appears not to have any effect - no files are created under this directory.
I also tried setting TART_EXECUTOR_INTERNAL_CACHE_DIR=/Volumes/SSD/tart/cache in a wrapper script for gitlab-tart-executor, with no change in behaviour.
If we try to run tart clone ... with TART_HOME (as mentioned in https://github.com/cirruslabs/tart/issues/221) set to /Volumes/SSD/tartas various users, that works fine.
Setting TART_HOME in our gitlab-tart-executor wrapper script does seem to have an effect, but we then just get the following:

With 'ignore permissions' set on drive

2024/01/05 15:51:44 tart command returned non-zero exit code: "tart/VMStorageLocal.swift:4: Fatal error: 'try!' expression unexpectedly raised an error: Error Domain=NSCocoaErrorDomain Code=513 \"You don’t have permission to save the file “cache” in the folder “tart”.\" UserInfo={NSFilePath=/Volumes/SSD/tart/cache, NSUnderlyingError=0x6000015e4c60 {Error Domain=NSPOSIXErrorDomain Code=1 \"Operation not permitted\"}}"

With 'ignore permissions' unset on drive

2024/01/05 15:15:38 Pulling the latest version of gitlab.***.com:5555/infrastructure/build-apple-runner/python-core-updated:DIF-150-python-core-mk3...
2024/01/05 15:15:38 tart command returned non-zero exit code: "Error: You don’t have permission to save the file “gitlab.***.com/5555” in the folder “OCIs”."

The runner itself has root permissions, so there's no obvious reason why this would fail when TART_HOME=/Volumes/SSD/tart tart clone ... as both a normal user and as root works.
Setting TART_HOME to a different location on the internal drive in our gitlab-tart-executor wrapper script, however, does work.
Is there something we are missing? What diagnostics would be helpful?
Thanks,
Ellis

Update: it appears the permissions issue was due to MacOS App Permissions, and granting Tart Full Disk Access permissions allowed it to work. So for the time being we are using a wrapper script setting TART_HOME to the external disk.
However, the --cache-dir and TART_EXECUTOR_INTERNAL_CACHE_DIR settings still seem to have no effect.

Hello @griels 👋
It's weird that you had to give Tart "Full Disk Access" permission: I've tested the same scenario on my laptop with a USB stick (APFS-formatted) attached to /Volumes/WHATEVER, and Tart mounted the volume just fine and was able to write to it.
As for the --cache-dir, can you run the find /Volumes commands from inside of your pipeline to see if /Volumes/My Shared Files/cachedir gets created?
How does your wrapper script looks like? Does it forward all the arguments correctly?
Also, you might be hitting https://github.com/cirruslabs/tart/issues/687 if you're running macOS Sonoma 14.2.

authors: edigaryev griels

repo: cirruslabs/gitlab-tart-executor


text:
MEET.3.1v0.1 Move Wording to Rationale

The following wording in GWS.MEET.3.1v0.1 policy statement needs to be moved to the rationale section.

so that they are available by default when a host starts their meeting.

The changes outlined in the issue will be made and a PR will be created.

repo: cisagov/ScubaGoggles


text:
Resolve markdownlint Issues

🐛 Summary
Revert .mdl_config.yaml changes made in PR #5 and fix all issues flagged by pre-commit.
To run pre-commit locally,  run pre-commit markdownlint --all-files
To setup pre-commit, run ./setup-env.
If it fails to run, follow the instructions returned in the console. This includes installing pyenv pyenv-virtualenv, and adding its path to .zhrc.
To run the check-case-conflict hook, run pre-commit run check-case-conflict --all-files.
To run a different hook, replace check-case-conflict with the name of the hook. The list of available hooks is in .pre-commit-config.yaml

@Matthew-Grayson - Can we close this Issue with all the pre-commit fixes?

repo: cisagov/XFD


text:
Convert to requirements.txt

🚀 Feature Proposal
Switch from manually installing dependencies to a requirements.txt file.
Motivation
Please outline the motivation for the proposal.
Example
Please provide an example for how this feature would be used.
Pitch
Why does this feature belong in this project?

This was handled by #314.

authors: hillaryj mcdonnnj


text:
compiled dylib file into xcode 8

i am successfully build the *.a file and *.dylib file. but when i  import into my xcode project it shows me the error the error as follows
error:
dyld: Library not loaded: ios_local/lib/libopenh264.4.dylib
Referenced from: /var/containers/Bundle/~
Reason: image not found

base you description, I think the libopenh264.4.dylib is built for Mac OS, not for iOS.
can you provide your command line for make/build? thanks.

yes i am following this guideline [(https://trac.pjsip.org/repos/ticket/1947)] to generate *.a and *.dylib. and one think from the old version of xcode its supports the *.dylib but in the new version it only support the *.tbd file instead of the *.dylib.

close this one as it is too long, and not followed again.


text:
Convert intrinsics abstraction functions that require constants to macros.

Some intrinsics functions include parameters that are encoded into the
instruction and therefore must be constant. GCC can figure this out when
inlining, however Clang cannot. This is solved by converting these functions
into macros.

Closes #6

repo: cisco/thor


text:
rename tests directory to examples

and merge the content from /examples.md into it

Was done, merged. Closing this issue.


text:
Broken Link 'Java API'

The link 'Java API' links to http://citrusframework.org/apidocs/index.html which is a 404.

we should be using https://javadoc.io/doc/com.consol.citrus instead

Might wanna make sure there are versioned links as many links at https://javadoc.io/doc/com.consol.citrus were dead/empty.
Might also want to link to the javadoc from the user guide when a class is mentioned.

Regarding the dead/empty links. This should be an on demand service. So if you open a link it might take some time for the service to grab and render the javadoc for this specific API version.

authors: christerengman christophd svettwer

repo: citrusframework/citrus-website


text:
Evaluate switching build scripts to https://github.com/ewilde/crane

https://github.com/ewilde/crane is a build automation tool being created by City Index's Ed Wilde (who manages City Index's internal build infrastructure
I'd like to see whether we can replace our custom build scripts - build.xml.proj with this project

I don't think it's useful to remake build scripts of our existing using crane. However, we can try to use it for new projects.

Ok

authors: fandrei mrdavidlaing

repo: cityindex/LogSearchShipper


text:
Block File Uploads of Disallowed Types

There is no server side code checking that the files in the file upload question type are of an allowed type. It only happens on the client side, which can be bypassed by changing the filter in the dropdown.
Test example of an executable being uploaded:

We may want to look into addressing this with the program images work in #5676

Also related to https://github.com/civiform/civiform/issues/5218

@nb1701 do you have a sense of where this landed and it's priority level?

Mine was first and has more fun examples, but there's more in #6982 so we could just close this one.

authors: caitlinshk gwendolyngoetz isabelcshaw

repo: civiform/civiform


text:
addFile route for adding multiple uploaded files

Description
This is similar to the updateFile, and is called from S3 after a user adds a file to a question that supports multiple file uploads. It will add the file to a new scalar value (FILE_KEY_LIST) on the FileUploadQuestion. If a duplicate file is present, it does nothing (in practice, this replaces the file). This is just the backend support, front-end coming in a future PR.
This change only focuses on new usage, there will likely be some edits later to account for backwards compatibility.
Design doc: https://docs.google.com/document/d/1NQjkUjnY70dVMDSiG-wGNXZhqT4hjB58CHrLKsQ7-To/edit
Release notes
Checklist
General
Read the full guidelines for PRs here

[x] Added the correct label: < feature | enhancement | bug | under-development | dependencies | infrastructure | ignore-for-release | database >
[ ] Assigned to a specific person, civiform/developers, or a more specific round-robin list
[ ] Added an additional reviewer from outside your organization as FYI (if the primary reviewer is in the same organization as you)
[x] Created unit and/or browser tests which fail without the change (if possible)
[ ] Performed manual testing (Chrome and Firefox if it includes front-end changes)
[ ] Extended the README / documentation, if necessary

Instructions for manual testing
If instructions are needed for manual testing by reviewers, include them here.
Issue(s) this completes
Fixes #<issue_number>; Fixes #<issue_number>...

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#7694  👈
#7495
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @devin-civi and the rest of your teammates on  Graphite

Github notified me to review this, but doesn't look actually set to me.
@devin-civi is the TDD complete? The doc still shows it's draft and not approved.

TDD not complete yet, no. Yeah I'm not sure what's up with the assign, I was trying to auto-assign it, but it just stuck on the entire civiform-developers group instead?

authors: devin-civi gwendolyngoetz


text:
[Bug]: mc:  Unable to make bucket minio/modelshare. Your previous request to create the named bucket succeeded and you already own it.

What happened?
Docker Started on PC startup and tryed to start the programm but the container "createbuckets" keeps restarting and I cant Access the site.

when I open it I see that it permanently creates the error:
mc:  Unable to make bucket minio/modelshare. Your previous request to create the named bucket succeeded and you already own it.

Yesterday I set everything up and was even able to open the site (even though the site was empty with the error "Playfab not initialized, missing secret key or title id"). But today it doenst even seam to start.
Steps to reproduce the problem

Start it??

What should have happened?
I expected to be able to acces the site even though it would probably not work because of the error "Playfab not initialized, missing secret key or title id".
What platforms do you use to access the site?
Windows
What browsers do you use to access the site?
Google Chrome
Additional information, context and logs
No response

I have the same issue.

same here, if you solvet please share @tobbi64

same here, if you solvet please share @tobbi64

I only set it up because I thought that this is the way to add the civitai integration to Automatic1111.... It is not :D I have no clue how it works. I just followed the instructions on the GitHub. I don't know how to fix it.

authors: MaHDiaLaGaB osaket tobbi64

repo: civitai/civitai


text:
Refactoring

I played with some approaches to refactor the code just to understand what does and what doesn't matter for performance. I think performance has stayed the same with this version but I don't think the code has become any better really, it's just different :)
What puzzles me is the importance of the function that starts on line 864. I tried several alternatives but most of them lead to much more allocations and therefore slower loading. I don't really understand the magic that is happening there.
Feel free to close this PR without merging. I did this more for my own education and wanted to share it with you in case you are interested.

Interesting. I guess the main changes are you've added pushmissing! and pushval!, which use dispatch (on the element type) instead of branching (on kind). It's all equivalent though - either way the choice is known to the compiler.
The function at 864 parses a single item of data (e.g. a number or a string). It explicitly branches over the 8 types it needs to parse (numeric, numeric or missing, string, string or missing, etc.) because each case requires different code to do the parsing. If we didn't do this branch and used more generic code, then there would have to be some type instability or dynamic dispatch in order to handle the 8 type cases. Since this function is in a hot loop, this would slow things down a lot.
It's a lot like if you're calling some function f(x) where x is one of 8 types but the compiler doesn't know which, then it'll have to do dynamic dispatch to pick a method of f. If you're very lucky the compiler might know that x is a Union{T1, T2, ..., T8} and might generate fast dispatch code. It's much more likely the compiler will have given up an only know x isa Any and needs to do generic slow dynamic dispatch. In this scenario, you can essentially do the dispatch yourself by explicitly doing if x isa T1; f(x); elseif x isa T2; f(x); ...; end so that within each branch the type of `x is known and you get a nice type-stable statically-dispatched function.

authors: cjdoris jbrea


text:
Serialising traceback objects

Python traceback objects are not picklable, and hence PyException cannot always be serialised.
As a fix, serialise the b field of a PyException as None. Or possibly always serialize traceback to None? Or to Unpicklable()?
Optional extra: if we detect that tblib is installed, allow pickling of traceback.
Document this behaviour in the compat section.

And what about other things that can't be pickled?

In fact Python Exceptions are already picklable - the __traceback__ field is skipped. So we get all this behaviour for free if we just change PyException to be a wrapper around a single Python Exception object.

Or perhaps leave the fields separate as-is, but treat PyException as a wrapper type around the v property. When normalising, set v.__traceback__ to t. When serialising, just serialise v. When deserialising, set t=pytype(v) and b=v.__traceback__ and isnormalised=true.


text:
pynder.errors.RequestError: 500

I followed all your steps how to start this project but it show this error

Hello  XXXX
Traceback (most recent call last):
File "/usr/local/bin/tindetheus", line 10, in
sys.exit(command_line_run())
File "/usr/local/lib/python3.6/dist-packages/tindetheus/tindetheus.py", line 781, in command_line_run
main(args, defaults['facebook_token'], defaults['XAuthToken'])
File "/usr/local/lib/python3.6/dist-packages/tindetheus/tindetheus.py", line 575, in main
likes_left=args.likes, x_auth_token=x_auth_token)
File "/usr/local/lib/python3.6/dist-packages/tindetheus/tindetheus.py", line 343, in init
self.session.profile.distance_filter = self.search_distance
File "/usr/local/lib/python3.6/dist-packages/pynder/models/me.py", line 32, in set
instance.init(instance._api.update_profile(profile), instance._api)
File "/usr/local/lib/python3.6/dist-packages/pynder/api.py", line 98, in update_profile
return self._post("/profile", profile)
File "/usr/local/lib/python3.6/dist-packages/pynder/api.py", line 63, in _post
return self._request("post", url, data=data)
File "/usr/local/lib/python3.6/dist-packages/pynder/api.py", line 54, in _request
raise errors.RequestError(result.status_code)
pynder.errors.RequestError: 500

My question is did i got the wrong token?

The fact that it's logging you in and showing your name means the token is working.
Something is wrong with the pynder or the api since it's not letting you update your search distance in your profile. I'm not currently getting this error.
Can you verrify that you can't change the distance with ?
import pynder
session = pynder.Session(facebook_token, X_auth_token) # w/e you use to login
print(session.profile)
# change distance
session.profile.distance_filter = 5

Where should I check this code?

Just in a python or ipython console

it shows error: module 'pynder' has no attribute 'Session'

No something went wrong on the import. Your pynder should definitely have the alias Session. Try again, perhaps in a different folder.
mkdir temp
cd temp
python3
>>> import pynder
>>> session = pynder.Session(facebook_token, X_auth_token) # w/e you use to login
>>> print(session.profile)
>>> session.profile.distance_filter = 5

new type of error now will not accept my token
TypeError: init() got an unexpected keyword argument 'X_auth_token'

decided to use the native version, my question is where should be located the tinder folder?

new type of error now will not accept my token
TypeError: init() got an unexpected keyword argument 'X_auth_token'

Sorry. If you are using the facebook token you should use
session = pynder.Session(facebook_token='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx')
or if you are the xauthtoken you should use
session = pynder.Session(XAuthToken='xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx')
Are you still having issues with changing the profile distance?

decided to use the native version, my question is where should be located the tinder folder?

It doesn't really matter. You could put it off of the home user directory.

I have two different types of error: in docker version it shows error 400
but on native version cant find the location of tinder folder and because of that, it cant find the config file

in docker version it shows error 400

Strange since it was authenticating you the other day. How are you grabbing the facebook token? Or are you using the XAuthToken?

but on native version cant find the location of tinder folder and because of that, it cant find the config file

You need to run tindetheus withing the tinder folder, use cd to navigate to that folder. This folder is where your local database will be stored.

im using XAuthToken

It's possible it expires. I think it may only last like 30 hours or so?

ok, now this is the problem

requests.exceptions.SSLError: HTTPSConnectionPool(host='api.gotinder.com', port=443): Max retries exceeded with url: /profile (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:719)'),))

To clarify, was that error in the docker container when running session.profile.distance_filter = 5? Or can you provide the full traceback?

native but, second time is showing this

(tensorflow) C:\Users\MASKINEN\tinder>tindetheus
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:516: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint8 = np.dtype([("qint8", np.int8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:517: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint8 = np.dtype([("quint8", np.uint8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:518: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint16 = np.dtype([("qint16", np.int16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:519: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint16 = np.dtype([("quint16", np.uint16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:520: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint32 = np.dtype([("qint32", np.int32, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:525: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_resource = np.dtype([("resource", np.ubyte, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:541: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint8 = np.dtype([("qint8", np.int8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:542: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint8 = np.dtype([("quint8", np.uint8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:543: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint16 = np.dtype([("qint16", np.int16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:544: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint16 = np.dtype([("quint16", np.uint16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:545: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_qint32 = np.dtype([("qint32", np.int32, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:550: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_resource = np.dtype([("resource", np.ubyte, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\sklearn\externals\joblib_init.py:15: DeprecationWarning: sklearn.externals.joblib is deprecated in 0.21 and will be removed in 0.23. Please import this functionality directly from joblib, which can be installed with: pip install joblib. If this warning is raised when loading pickled models, you may need to re-serialize those models with scikit-learn 0.21+.
warnings.warn(msg, category=DeprecationWarning)
usage: tindetheus [-h] [--distance DISTANCE] [--image_batch IMAGE_BATCH]
[--model_dir MODEL_DIR] [--likes LIKES] [--version]
function
tindetheus: error: the following arguments are required: function
(tensorflow) C:\Users\MASKINEN\tinder>tindetheus browse
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:516: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint8 = np.dtype([("qint8", np.int8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:517: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint8 = np.dtype([("quint8", np.uint8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:518: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint16 = np.dtype([("qint16", np.int16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:519: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint16 = np.dtype([("quint16", np.uint16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:520: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint32 = np.dtype([("qint32", np.int32, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:525: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_resource = np.dtype([("resource", np.ubyte, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:541: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint8 = np.dtype([("qint8", np.int8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:542: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint8 = np.dtype([("quint8", np.uint8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:543: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint16 = np.dtype([("qint16", np.int16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:544: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint16 = np.dtype([("quint16", np.uint16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:545: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_qint32 = np.dtype([("qint32", np.int32, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:550: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_resource = np.dtype([("resource", np.ubyte, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\sklearn\externals\joblib_init.py:15: DeprecationWarning: sklearn.externals.joblib is deprecated in 0.21 and will be removed in 0.23. Please import this functionality directly from joblib, which can be installed with: pip install joblib. If this warning is raised when loading pickled models, you may need to re-serialize those models with scikit-learn 0.21+.
warnings.warn(msg, category=DeprecationWarning)
Traceback (most recent call last):
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\runpy.py", line 85, in run_code
exec(code, run_globals)
File "C:\Users\MASKINEN\Anaconda3\envs\tensorflow\Scripts\tindetheus.exe_main.py", line 9, in
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 781, in command_line_run
main(args, defaults['facebook_token'], defaults['XAuthToken'])
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 575, in main
likes_left=args.likes, x_auth_token=x_auth_token)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 337, in init
self.session = self.login(facebook_token, x_auth_token)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 374, in login
print('Hello ', session.profile)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\cached_property.py", line 35, in get
value = obj.dict[self.func.name] = self.func(obj)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\pynder\session.py", line 22, in profile
return Profile(self._api.profile(), self._api)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\pynder\api.py", line 87, in profile
return self._get("/profile")
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\pynder\api.py", line 52, in _get
return self._request("get", url)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\pynder\api.py", line 46, in _request
raise errors.RequestError(result.status_code)
pynder.errors.RequestError: 400
(tensorflow) C:\Users\MASKINEN\tinder>tindetheus browse
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:516: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint8 = np.dtype([("qint8", np.int8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:517: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint8 = np.dtype([("quint8", np.uint8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:518: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint16 = np.dtype([("qint16", np.int16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:519: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint16 = np.dtype([("quint16", np.uint16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:520: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint32 = np.dtype([("qint32", np.int32, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:525: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_resource = np.dtype([("resource", np.ubyte, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:541: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint8 = np.dtype([("qint8", np.int8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:542: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint8 = np.dtype([("quint8", np.uint8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:543: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint16 = np.dtype([("qint16", np.int16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:544: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint16 = np.dtype([("quint16", np.uint16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:545: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_qint32 = np.dtype([("qint32", np.int32, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:550: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_resource = np.dtype([("resource", np.ubyte, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\sklearn\externals\joblib_init.py:15: DeprecationWarning: sklearn.externals.joblib is deprecated in 0.21 and will be removed in 0.23. Please import this functionality directly from joblib, which can be installed with: pip install joblib. If this warning is raised when loading pickled models, you may need to re-serialize those models with scikit-learn 0.21+.
warnings.warn(msg, category=DeprecationWarning)
Traceback (most recent call last):
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\runpy.py", line 85, in run_code
exec(code, run_globals)
File "C:\Users\MASKINEN\Anaconda3\envs\tensorflow\Scripts\tindetheus.exe_main.py", line 9, in
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 781, in command_line_run
main(args, defaults['facebook_token'], defaults['XAuthToken'])
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 575, in main
likes_left=args.likes, x_auth_token=x_auth_token)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 337, in init
self.session = self.login(facebook_token, x_auth_token)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 374, in login
print('Hello ', session.profile)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\cached_property.py", line 35, in get
value = obj.dict[self.func.name] = self.func(obj)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\pynder\session.py", line 22, in profile
return Profile(self._api.profile(), self._api)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\pynder\api.py", line 87, in profile
return self._get("/profile")
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\pynder\api.py", line 52, in _get
return self._request("get", url)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\pynder\api.py", line 46, in _request
raise errors.RequestError(result.status_code)
pynder.errors.RequestError: 400

native but, second time is showing this

(tensorflow) C:\Users\MASKINEN\tinder>tindetheus browse
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:516: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint8 = np.dtype([("qint8", np.int8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:517: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint8 = np.dtype([("quint8", np.uint8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:518: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint16 = np.dtype([("qint16", np.int16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:519: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint16 = np.dtype([("quint16", np.uint16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:520: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint32 = np.dtype([("qint32", np.int32, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:525: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_resource = np.dtype([("resource", np.ubyte, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:541: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint8 = np.dtype([("qint8", np.int8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:542: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint8 = np.dtype([("quint8", np.uint8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:543: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint16 = np.dtype([("qint16", np.int16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:544: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint16 = np.dtype([("quint16", np.uint16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:545: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_qint32 = np.dtype([("qint32", np.int32, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:550: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_resource = np.dtype([("resource", np.ubyte, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\sklearn\externals\joblib_init.py:15: DeprecationWarning: sklearn.externals.joblib is deprecated in 0.21 and will be removed in 0.23. Please import this functionality directly from joblib, which can be installed with: pip install joblib. If this warning is raised when loading pickled models, you may need to re-serialize those models with scikit-learn 0.21+.
warnings.warn(msg, category=DeprecationWarning)
Traceback (most recent call last):
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\runpy.py", line 85, in run_code
exec(code, run_globals)
File "C:\Users\MASKINEN\Anaconda3\envs\tensorflow\Scripts\tindetheus.exe_main.py", line 9, in
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 781, in command_line_run
main(args, defaults['facebook_token'], defaults['XAuthToken'])
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 575, in main
likes_left=args.likes, x_auth_token=x_auth_token)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 337, in init
self.session = self.login(facebook_token, x_auth_token)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 374, in login
print('Hello ', session.profile)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\cached_property.py", line 35, in get
value = obj.dict[self.func.name] = self.func(obj)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\pynder\session.py", line 22, in profile
return Profile(self._api.profile(), self._api)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\pynder\api.py", line 87, in profile
return self._get("/profile")
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\pynder\api.py", line 52, in _get
return self._request("get", url)
File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\pynder\api.py", line 46, in _request
raise errors.RequestError(result.status_code)
pynder.errors.RequestError: 400

The 400 errors usually mean that you were unable to login. I've never used the XAuthToken, so I can't really comment about how it works. I know that it's time limited.
Have you gotten the 500 error again?  It's weird that you were able to login just fine the first time you posted the error message, but have since had issues logging in.

im gonna try with other profile, but it is very weird

@fuutf Any luck figuring this out?

nope im gonna try again with different profile

there is next type of problem
this time i have used the facebook token and found new type of problem

(tensorflow) C:\Users\MASKINEN\tinder>tindetheus browse
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:516: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint8 = np.dtype([("qint8", np.int8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:517: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint8 = np.dtype([("quint8", np.uint8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:518: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint16 = np.dtype([("qint16", np.int16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:519: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint16 = np.dtype([("quint16", np.uint16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:520: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint32 = np.dtype([("qint32", np.int32, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\dtypes.py:525: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  np_resource = np.dtype([("resource", np.ubyte, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:541: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint8 = np.dtype([("qint8", np.int8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:542: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint8 = np.dtype([("quint8", np.uint8, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:543: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint16 = np.dtype([("qint16", np.int16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:544: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint16 = np.dtype([("quint16", np.uint16, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:545: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint32 = np.dtype([("qint32", np.int32, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tensorboard\compat\tensorflow_stub\dtypes.py:550: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  np_resource = np.dtype([("resource", np.ubyte, 1)])
c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\sklearn\externals\joblib\__init__.py:15: DeprecationWarning: sklearn.externals.joblib is deprecated in 0.21 and will be removed in 0.23. Please import this functionality directly from joblib, which can be installed with: pip install joblib. If this warning is raised when loading pickled models, you may need to re-serialize those models with scikit-learn 0.21+.
  warnings.warn(msg, category=DeprecationWarning)
Traceback (most recent call last):
  File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\MASKINEN\Anaconda3\envs\tensorflow\Scripts\tindetheus.exe\__main__.py", line 9, in
  File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 781, in command_line_run
    main(args, defaults['facebook_token'], defaults['XAuthToken'])
  File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 575, in main
    likes_left=args.likes, x_auth_token=x_auth_token)
  File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 337, in __init__
    self.session = self.login(facebook_token, x_auth_token)
  File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\tindetheus\tindetheus.py", line 373, in login
    XAuthToken=x_auth_token)
  File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\pynder\session.py", line 18, in __init__
    self._api.auth(facebook_id, facebook_token)
  File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\pynder\api.py", line 28, in auth
    self._full_url('/auth'), json=data, proxies=self._proxies).json()
  File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\site-packages\requests\models.py", line 897, in json
    return complexjson.loads(self.text, **kwargs)
  File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\json\__init__.py", line 319, in loads
    return _default_decoder.decode(s)
  File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\json\decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\json\decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

never mind, ive decided to use docker and now it is working... finally! thanks mate

... 0).end()) File "c:\users\maskinen\anaconda3\envs\tensorflow\lib\json\decoder.py", line 357, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) `

This error looks like the one my PR tried to fix. https://github.com/charliewolf/pynder/pull/211 Try installing pynder from the pr https://github.com/charliewolf/pynder/pull/211#issuecomment-491353236

Otherwise I'm glad the docker version is working for you.

authors: cjekel fuutf

repo: cjekel/tindetheus


text:
Add explicit tests for Game.getIntersections

Probably make it return a vector of vectors instead of a seq of seqs, too, for fast lookups

This method was removed

license: isc