primordic/IssueDupesLite huggingface dataset:
Repository: processing/processing

Issue #5875: textFont and textSize acting unexpected when using push & pop
Created: 2019-06-05T17:32:29Z
Description


According to the reference  push() and pop() should affect, among others,  textAlign(), textFont(), textMode(), textSize().
Expected Behavior


When using push & pop the styling should be applied exclusivly to text inbetween the push & pop calls.
Current Behavior
The font & size styling is not being popped, and instead applied to subsequent calls to text() as well.
Steps to Reproduce


Here's a small sample to demonstrate the issue (make sure the font is installed on local machine when reproducing).
PFont cbi;

void setup()
{
  size(256, 256, P2D);
  cbi = createFont("Corbel Bold Italic", 12);
}

void draw()
{
  background(128);

  push(); 
  textFont(cbi);
  textSize(20);
  textMode(SHAPE);
  textAlign(CENTER);
  text("custom font", width/2, height/2);
  pop();
  
  
  // expecting this to be in default font & size
  // note alignment and mode are behaving as expected
  text("default font", width/2, height/2+30);

}


And here's the result;

Final note: the desired behaviour can be achieved by calling text before using push & pop, just using an empty string is sufficient;  text("", 0,0) However that seems like a strange way to get push & pop to behave appropriately.
Your Environment

 


Processing version: 3.5.3
Operating System and OS version: Windows 10

Duplicate issue #5897: textSize() not working as expected in P2D / P3D
Created: 2019-07-27T15:34:44Z
OSX 10.12.6
P5 3.5.3
The first textSize used in a sketch will influence every text after.
void setup() {
  size(600, 100, P2D);
}

void draw() {
  background(0);
  textSize(4);
  textSize(40);
  fill(255);
  text("Text broken in P2D / P3D", 50, 50);
}

Closing comment (2019-10-05T14:03:38Z): This is why createFont() exists, because OpenGL fonts are rendered as bitmaps, and you have to request a specific size.

The issue in the original post is that the default font is being used, and createFont() gets called with 4. The real fix here is to disable the default font. It's a nightmare to debug, as you can see there are lots of bugs in the repo because of it.
The noLoop() issue is more about how rendering behaves with OpenGL… You'll get different results on different machines. OpenGL just isn't built for rendering a single frame once and then stopping.
The push example is the same as #5875

No great solution here… simple one would be removing default fonts, which would fix the majority of this particular issue (largely by making its cause more evident).
We can't just call createFont() and rebuild all the bitmaps each time textSize() is called, because inside draw, you'll quickly be doing that thousands of times in just a few seconds. The “real” solution is major reworking of font handling in GL. That's certainly ideal, but I don't have time to do that, and help is not forthcoming.
Repository: processing/processing

Issue #1014: supported android platform
Created: 2013-02-10T17:11:19Z
Original author: mrcdr...@gmail.com (January 27, 2012 14:11:30)
Hi,
from the wiki page it seems that processing 2.0a4 supports anroid 2.1 platform. Is it true? I tried and only android 2.2 platform & emulator are working.
Best
Marco
Original issue: http://code.google.com/p/processing/issues/detail?id=976

Duplicate issue #1114: Use Swing JFileChooser not AWT FileDialog
Created: 2013-02-10T17:18:27Z
Original author: Mark.A.G...@gmail.com (May 06, 2012 10:51:49)
Would it be possible to change the File open/save actions to use the Swing JFileChooser instead of the AWT FileDialog? Under Linux the AWT FileDialog is a horrible and a pain to use, whereas the Swing JFileChooser more accurately reflects how other file dialogs work. You can see an example of the different dialogs in this Arduino issue: http://code.google.com/p/arduino/issues/detail?id=39
Original issue: http://code.google.com/p/processing/issues/detail?id=1076

Closing comment (2013-02-10T17:18:30Z): This issue is a duplicate of #1014
Repository: processing/processing

Issue #5110: Console window losing text
Created: 2017-06-04T13:59:46Z
I just installed Processing, version 3.3.4 on a Mac (OS 10.12.5).  The Console window displays only the most recently generated line or two of text, and there is no scroll bar.  For example, this program:
void setup() {
}
void draw() {
  println("In draw " + frameCount);
}

displays only the last two lines of text, regardless of how big the Console window is, and there is no scroll bar in the Console window. Doing Edit->Select All from the Console window only selects what is visible (not surprisingly).

Duplicate issue #5139: Console broken since version 3.3.4
Created: 2017-06-17T09:02:02Z
The console doesn't have a scrollbar anymore and doesn't show all the printed values. I've noticed this on Windows (on a students computer) while printing a camera.list array. However in OSX 10.10.5 this error is also present. See the test code below.
Test code
int [] numbers = { 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19 };

void setup() {
  printArray(numbers);
  noLoop();
}

void draw() {
}

Result in Processing 3.3.4 (the console shows only the last indexes and there is no way to scroll up):

Result in Processing 3.3 (as expected)

Closing comment (2017-06-17T09:07:52Z): Duplicate of #5110, now fixed. As noted in that thread there is a workaround (#5110 (comment)) until the next release comes out.
Repository: prometheus-community/windows_exporter

Issue #794: Windows exporter service stops when ever CPU or memory is high
Created: 2021-06-03T04:34:28Z
we have been experiencing the service being stopped state when ever the system has high CPU or memory.
I have used the 64bit installer to configure exporter and the service type is kept to automatic.
Is there any configuration i could ensure the service does not stops as monitoring metrics is quite important.  As alternative i am considering to write a script to check the service in certain interval and start it. But its more like a hack than solution.

Duplicate issue #950: Windows_exporter stop working  on some servers
Created: 2022-03-02T09:11:07Z
Windows_exporter v18.1 service stop working when there are hight usage of CPU or RAM and can't restart automatically , it need to be restarted manually every time .
i tested with some early version (v16 and v17) and i got the same issue,
The issue is happned in several servers .

Closing comment (2022-03-13T03:01:50Z): Duplicate of #794
Repository: prometheus-community/windows_exporter

Issue #813: High memory usage on .16.0
Created: 2021-07-01T20:09:04Z
Hello!
I have a couple of servers reporting high memory usage by the windows_exporter. I am using the default configuration/collectors. Is there anyway to limit the resource usage on the exporter?

Exporter version:
windows_exporter, version 0.16.0 (branch: master, revision: f316d81d50738eb0410b0748c5dcdc6874afe95a) build user:       appveyor-vm\appveyor@appveyor-vm build date:       20210225-10:52:19 go version:       go1.15.6 platform:         windows/amd64
OS Name:                   Microsoft Windows Server 2016 Standard
OS Version:                10.0.14393 N/A Build 14393
Handles  NPM(K)    PM(K)      WS(K)     CPU(s)     Id  SI ProcessName

1260     142 12748860   12496424 110,102.69  11388   0 windows_exporter

Duplicate issue #1063: Windows_exporter v0.19.0 memory leak
Created: 2022-09-16T14:51:06Z
Hello. We use windows_exporter v0.19.0 with this collectors: os,cpu,cpu_info,cs,memory,net,system,tcp,process,service,logical_disk,mssql,scheduled_task,textfile --collector.service.services-where="Name LIKE '%SQL%'", after upgrade from 0.17.1 we noticed memory leak.
In 0.19.0 we also added scheduled_task collector

Closing comment (2022-09-17T08:36:58Z): Do you continue to experience this behavior after disabling the scheduled_task collector? If so I wonder if this is related to #813
Repository: prometheus-community/windows_exporter

Issue #946: Service start timeout inside container servercore:ltsc2019 since v0.17.0
Created: 2022-02-21T21:23:02Z
Hello,
I discovered during a test to upgrade, that any version >= 0.17.0 are not more able to start as service inside a container.
If I launch it in CLI it works, but as service it fails.
I highly suspect #863 because even if IsWindowsService is the good practice it seems has been rewrited pretty recently in golang codebase due to bugs.
So maybe a golang update could solve the issue, else adding a workaround to "force" the service mode should be considered.
There is a similar trick on otel collector project : https://github.com/open-telemetry/opentelemetry-collector/blob/7ed3f75ef84d9e9d11b175a0859060f765faca0b/docs/troubleshooting.md#startup-failing-in-windows-docker-containers and used here https://github.com/open-telemetry/opentelemetry-collector/blob/4439e9b49c4de55bdc050ee4928b5b0c79c317cb/cmd/builder/internal/builder/templates/main_windows.go.tmpl#L32

Duplicate issue #962: kubernetes CreateObject SWbemLocator error: Invalid class string
Created: 2022-03-29T15:58:17Z
time="2022-03-29T15:56:28Z" level=info msg="Loading configuration file: /config.yml" source="config.go:37"
time="2022-03-29T15:56:28Z" level=debug msg="Initializing SWbemServices" source="exporter.go:250"
time="2022-03-29T15:56:28Z" level=fatal msg="CreateObject SWbemLocator error: Invalid class string" source="exporter.go:253"

default config out of kubernetes folder main on aks 1.23

Closing comment (2022-04-06T10:43:53Z): This might be a duplicate of #946. Does the container work when run via CLI, rather than as a service inside the container?
Repository: prometheus-community/windows_exporter

Issue #531: DHCP Collector error
Created: 2020-05-25T16:23:51Z
Hey, I wanted to check out the latest version of Windows_exporter (WMI_exporter) 0.12.0 on a Windows Server 2012 R2 with the new dhcp collector enabled. Unfortunately it throws the following message:
An error has occurred while serving metrics:

collected metric wmi_dhcp_denied_due_to_match_total counter:<value:0 >  has help "Total number of DHCP requests denied, based on non-matches from the Allow list (DeniedDueToNonMatch)" but should have "Total number of DHCP requests denied, based on matches from the Deny list (DeniedDueToMatch)"

Any tips how to resolve this?

Duplicate issue #566: DHCP collector error serving metrics
Created: 2020-07-06T16:41:07Z
Hello
I have problem with dhcp collector, when i try serving metrics, i get in error
An error has occurred while serving metrics:

collected metric windows_dhcp_denied_due_to_match_total counter:<value:0 >  has help "Total number of DHCP requests denied, based on non-matches from the Allow list (DeniedDueToNonMatch)" but should have "Total number of DHCP requests denied, based on matches from the Deny list (DeniedDueToMatch)"

windows exporter version v0.13.0
Enabled_collector="os,dhcp,dns,cpu,cs,memory,net,system,tcp"
Windows server 2012 r2 datacenter with dhcp server
Windows event log is empty

Closing comment (2020-07-07T06:54:44Z): This is a duplicate of #531.
It will be fixed in the next release!
Repository: prometheus-community/windows_exporter

Issue #181: Event logging errors every minute
Created: 2018-03-31T11:31:43Z
It seems I deployed the MSI to machines that do not have MSMQ installed which is fine I guess, however every minute I get the following error in the event logs.
Perhaps it would be better to have it log this message to the event viewer when the services starts as I think every minute is too much or if it can handle this better when a collector has been enabled.
I.E IIS not installed on all target devices, however I don't want to be deploying different exporters to cater for the role of a server.
The description for Event ID 102 from source wmi_exporter cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
ERROR: msmq collector failed after 0.007022s: Exception occurred. (Invalid class )

Duplicate issue #217: Collector error handling
Created: 2018-06-25T20:35:12Z
Hello, wdyt about not logging errors about failed collector calls like https://github.com/martinlindhe/wmi_exporter/blob/bb67658853cc3cecc3d83e19c466838a54ed6be9/exporter.go#L105 or https://github.com/martinlindhe/wmi_exporter/blob/aecd90dcf127f1c26ade82939cafc1420eed1906/collector/dns.go#L185 on every prometheus scrape? it really noises logs. I think it is really useful to log it on exporter service start, but not on every scrape. Usually servers have some roles that are not enabled on all servers ( i.e AD DC, DNS, FileServices and etc) and having different collectors enabled for each server is a bit complicated if you want to do it using GPO installs.

Closing comment (2018-06-26T06:37:11Z): Hi,
This is a duplicate of #181. In general, this (configuring which collectors should be enabled) is what we consider a configuration management problem, rather than something that should be solved in the exporter.
This is then further complicated by the fact that it is not all that simple to determine if you get an error because the role is not installed, or because of some other problem (the errors are untyped, use quite vague strings to describe the problem, and those strings are also localized).
I would recommend investigating if you can make your installations only enable the collectors that you actually want enabled.
Repository: prometheus-community/windows_exporter

Issue #1009: IIS collector is broken on 0.18.1
Created: 2022-06-24T04:39:04Z
Hi,
windows_exporter 0.18.1 IIS collector is not working as expected when I delete the website in IIS.
Exporter 0.18.1 running on windows 2019 IIS 10
Reproduce the error : windows_exporter is working correctly. If I delete any the website in IIS. after that exporter has error. Only when I restart IIS the exporter will work again.
Exporter error like below:
An error has occurred while serving metrics:
324 error(s) occurred:

collected metric "windows_iis_current_anonymous_users" { label:<name:"site" value:"test.santino.com.vn" > gauge:<value:0 > } was collected before with the same name and label values
collected metric "windows_iis_current_blocked_async_io_requests" { label:<name:"site" value:"test.santino.com.vn" > gauge:<value:0 > } was collected before with the same name and label values
collected metric "windows_iis_current_cgi_requests" { label:<name:"site" value:"test.santino.com.vn" > gauge:<value:0 > } was collected before with the same name and label values
collected metric "windows_iis_current_connections" { label:<name:"site" value:"test.santino.com.vn" > gauge:<value:0 > } was collected before with the same name and label values
collected metric "windows_iis_current_isapi_extension_requests" { label:<name:"site" value:"test.santino.com.vn" > gauge:<value:0 > } was collected before with the same name and label values

Duplicate issue #1067: exporter fails with error 500
Created: 2022-09-26T08:26:56Z
Im using windows exporter v0.19.0 and when I launched http://localhost:9182/metrics
I get many errors saying "was collected before with the same name and label values"
such as "collected metric "windows_iis_current_anonymous_users" was collected before with the same name and label values"
and when I installed v0.16 this problem was solved. but with later version I got this error.

Closing comment (2022-10-02T22:37:15Z): Duplicate of  #1009
Repository: prometheus-operator/kube-prometheus

Issue #179: Verified TLS for targets
Created: 2019-08-08T19:30:47Z
What is missing?
Some targets are using insecureSkipVerify: true, which we could change by allowing an optional usage of cert-manager issuing valid certificates. The targets that would need this are:

kube-state-metrics
node-exporter
alertmanager
prometheus
k8s-prometheus-adapter

Kubernetes components are already scraped with valid certificates on providers where possible using the cluster CA.
Why do we need it?
We want a sound out of the box security story.
Environment
Any

Duplicate issue #468: Secure /metrics endpoints for components shipped with kube-prometheus
Created: 2020-03-24T10:00:35Z
What is missing?
We ship only few components with protected /metrics endpoints. This should be a default for all of them.
Why do we need it?
To have secure by default solution
Environment

kube-prometheus version: latest

Anything else we need to know?:
PR for securing prometheus-operator endpoint: #453
List of components which need securing:

"alertmanager-main"
"prometheus-k8s"
"kube-dns"
"grafana"
When component is secured, it should be removed from e2e test exclusion list in TestTargetsScheme test.

Closing comment (2021-03-02T20:03:08Z): Closing as a duplicate of #179
Repository: prometheus-operator/kube-prometheus

Issue #72: High CPU throttling on kube-rbac-proxy containers with default installation
Created: 2019-04-16T20:23:08Z
Using a reasonably small K8S cluster:

5 etcd nodes
3 master nodes
5 worker nodes

And deploying kube-prometheus using the jsonnet-bundler method at master, I immediately get alerts firing such as:

56% throttling of CPU in namespace monitoring for container kube-rbac-proxy-self in pod kube-state-metrics-5bd984db7b-m66m6.


67% throttling of CPU in namespace monitoring for container kube-rbac-proxy-main in pod kube-state-metrics-5bd984db7b-m66m6.


53% throttling of CPU in namespace runway-monitoring for container kube-rbac-proxy in pod node-exporter-7jlrq.

The node-exporter alert is fired for all nodes (ie. all pods within the daemonset), so 13 times in my case.
Source code
The jsonnet libs in this repo have the following:
node-exporter
        container.mixin.resources.withLimits({ cpu: '20m', memory: '40Mi' }) +
kube-state-metrics
        container.mixin.resources.withLimits({ cpu: '20m', memory: '40Mi' });
Questions

is this throttling alert only caused by going over container cgroup limits or could this be external (ie. hypervisor side effects)
are the containers behaving normally (ie. not doing more work than they should)
is the 20m limit realistic in real world scenarios?
the values are not configurable through _config; can they be overridden nonetheless?

Duplicate issue #492: Default Prometheus ClusterRole is missing permissions compared to prometheus-operator documentation
Created: 2020-04-13T22:30:39Z
What happened?
The default Prometheus ClusteRole in kube-prometheus is missing some permissions compared to the Prometheus ClusterRole from documentation from the documentation of prometheus-operator
Did you expect to see some different?
Yes, I expected the ClusterRole provided by default with kube-prometheus installation to be the one indicated in the prometheus-operator documentation.
Environment

Prometheus Operator version:

kube-prometheus release-0.4

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:14:22Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.6", GitCommit:"72c30166b2105cd7d3350f2c28a219e6abcd79eb", GitTreeState:"clean", BuildDate:"2020-01-18T23:23:21Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"linux/amd64"}


Kubernetes cluster kind: kubeadm

Closing comment (2020-09-24T11:24:59Z): @brancz I want to have a go at documenting this. There is another mixin related to #72 that is undocumented and I want to try at least a basic documentation for both. Is that fine?
Repository: prometheus-operator/kube-prometheus

Issue #1511: The CustomResourceDefinition "prometheuses.monitoring.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes
Created: 2021-11-19T06:59:51Z
kubectl apply -f manifests/setup/
namespace/monitoring created
customresourcedefinition.apiextensions.k8s.io/alertmanagerconfigs.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/podmonitors.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/probes.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/prometheusrules.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/servicemonitors.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/thanosrulers.monitoring.coreos.com created
clusterrole.rbac.authorization.k8s.io/prometheus-operator created
clusterrolebinding.rbac.authorization.k8s.io/prometheus-operator created
deployment.apps/prometheus-operator created
service/prometheus-operator created
serviceaccount/prometheus-operator created
The CustomResourceDefinition "prometheuses.monitoring.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes
os：              rockylinux    8.5
cri:                containerd    1.4.12
kubernetes:  1.22.4 （init by kubeadm）

Duplicate issue #1681: prometheuses.monitoring.coreos.com  must have at most 262144 bytes
Created: 2022-03-15T06:52:13Z
[root@master setup]# kubectl apply -f 0prometheusCustomResourceDefinition.yaml
The CustomResourceDefinition "prometheuses.monitoring.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes

Closing comment (2022-03-15T09:13:03Z): Closing as a duplicate of #1511, #1533, prometheus-operator/prometheus-operator#4367, prometheus-operator/prometheus-operator#4355, prometheus-operator/prometheus-operator#4348, and #1474
Repository: prometheus-operator/kube-prometheus

Issue #1358: Adding additional scrape config for a target outside the kubernets cluster
Created: 2021-09-01T16:42:00Z
I deployed kube-prometheus in a cluster. Would it be possible to monitor, say an IoT device which is running 'fluent-bit' with node-exporter plugin (which should be scrap-able by prometheus) ?
This IoT device will be running inside the same LAN as the kuberentes cluster where kube-prometheus is deployed.
I know that we can configure prometheus-operator with additional scrape configs as shown here: https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/additional-scrape-config.md
But how can we do that with kube-prometheus?

Duplicate issue #1739: I have a need to monitor applications outside the cluster, how can I configure TLS  through ServiceMonitor
Created: 2022-04-25T10:27:32Z
Hello everyone，I have a need to monitor applications outside the cluster, how can I configure TLS and basic auth through ServiceMonitor？
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: node-exporter1
  namespace: monitoring
  labels:
    app: node-exporter
spec:
  jobLabel: node-exporter
  endpoints:
  - port: port
    interval: 30s
  selector:
    matchLabels:
      app: node-exporter
  namespaceSelector:
    matchNames:
    - monitoring

Closing comment (2022-04-28T15:35:22Z): Right now, I am not sure we have a good way to do this.
This looks like a duplicate of #1358 and there is a similar ask in prometheus-operator/prometheus-operator#4748
@paulfantom were you looking into a solution for this at some stage?
Repository: prometheus-operator/kube-prometheus

Issue #755: Master failing on AKS RBAC cluster v1.18.8 Adapter and Operator CrashLoopBackOff 
Created: 2020-11-05T12:54:56Z
Applied the manifests from master with all pre requisites on AKS v1.8.8.
Operator error : "Unhandled error received. Exiting..." err="communicating with server failed: an error on the server ("") has prevented the request from succeeding"
Adapter error : unable to install resource metrics API: unable to construct dynamic discovery mapper: unable to populate initial set of REST mappings: an error on the server ("") has prevented the request from succeeding
In master, the head is mentioned as not usable for v1.18.8 but in release 0.6 it is.
Edit : metrics-server running in kube-system is working as expected. Reinstalled the cluster now to make sure there were no misconfigurations.
Any help much appreciated, thanks

Duplicate issue #756: Master failing on AKS RBAC cluster v1.18.8 Adapter and Operator CrashLoopBackOff 
Created: 2020-11-05T12:55:32Z
All the pre requisite CRD's were deployed. And webhook flags verified on the kube server too.
Operator error : "Unhandled error received. Exiting..." err="communicating with server failed: an error on the server ("") has prevented the request from succeeding"
Adapter error : unable to install resource metrics API: unable to construct dynamic discovery mapper: unable to populate initial set of REST mappings: an error on the server ("") has prevented the request from succeeding
metric-server is running on kube-system fine, able to reach kube-api

Closing comment (2020-11-05T13:43:52Z): Closing as duplicate of #755. Let's move the potential discussion into that thread.
Repository: prometheus-operator/kube-prometheus

Issue #1511: The CustomResourceDefinition "prometheuses.monitoring.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes
Created: 2021-11-19T06:59:51Z
kubectl apply -f manifests/setup/
namespace/monitoring created
customresourcedefinition.apiextensions.k8s.io/alertmanagerconfigs.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/podmonitors.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/probes.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/prometheusrules.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/servicemonitors.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/thanosrulers.monitoring.coreos.com created
clusterrole.rbac.authorization.k8s.io/prometheus-operator created
clusterrolebinding.rbac.authorization.k8s.io/prometheus-operator created
deployment.apps/prometheus-operator created
service/prometheus-operator created
serviceaccount/prometheus-operator created
The CustomResourceDefinition "prometheuses.monitoring.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes
os：              rockylinux    8.5
cri:                containerd    1.4.12
kubernetes:  1.22.4 （init by kubeadm）

Duplicate issue #1533: "prometheuses.monitoring.coreos.com" is invalid
Created: 2021-12-03T03:11:32Z
The CustomResourceDefinition "prometheuses.monitoring.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes

Closing comment (2021-12-03T09:07:37Z): Duplicate of #1511
Please use kubectl apply --server-side.
Repository: psf/requests

Issue #2255: Session requests should respect verify=False
Created: 2014-09-29T01:06:48Z
Using a website that has a self-signed cert, the following use of verify=False fails:
import requests
s = requests.Session()
r = s.get('https://selfsignedsite')
traceback
r = s.get('https://selfsidnedsite', verify=False)
traceback is the same about SSL3 not finding a valid cert
requests.get('https://selfsignedsite', verify=False)
traceback as above

Duplicate issue #2275: Content-Length header not checked by requests if not enough data is sent
Created: 2014-10-12T17:11:19Z
This is a feature request.
In our application we've noticed ~ 1 in 2500 GET requests is truncated early. The HTTP responses are typically 20K-2MB. This is certainly caused by network issues or dodgy HTTP servers and isn't a requests problem. By default requests 2.3.0 doesn't give any indication if the response body has a length smaller than the 'Content-Length' header indicated. The response object is presented as if nothing is amiss.
Requests is already doing some checks on Content-Length. When a response body is larger than a Content-Length header describes requests silently truncates the body. I've (yet) to find a way of detecting this case.
I would completely understand if the requests developers thought this type of check was outside the scope of the library - after all it is pretty easy to do this check in user code - but it seemed kind of anomalous given the super succinct high level api.
In a similar vein a Content-MD5 header check would be useful in our application but this is probably a lot more niche.

Closing comment (2014-10-12T17:41:08Z): Hi @squareproton
Let me start off by saying that we've had this requested in the past (see: #1938) so you would do well to read that discussion to understand why we will not ever add content-length checking to requests. (This is also vaguely related to #2255 and requests/toolbelt#41.)
If you read the thread that resulted from the last time this was suggested, you'll see that we do not add arbitrary or niche features to requests. If there's a high likelihood of users needed it (something greater than 90% of our current userbase) then we'll add it. You might understand how this makes requests far more maintainable, especially given we don't do much in the way of header checks.
What I am going to address here is the following:

Requests is already doing some checks on Content-Length. When a response body is larger than a Content-Length header describes requests silently truncates the body.

I'm fairly certain you're misunderstanding what you're receiving. Of course, if you can provide an example that reliably reproduces that, this would be most appreciated. I have never personally seen this behaviour, and I'd be surprised to hear that we're truncating large bodies. If that's happening anywhere, it might be httplib but I doubt it happens there either.
Repository: psf/requests

Issue #1577: Requests not timing out
Created: 2013-09-04T14:11:39Z
Got a strange case of failing timeout on a particular url, when trying in browser, seems like this page never completes loading...
The expected behavior would be for requests to timeout, however it is not happening:
this times out fine:
requests.get("http://www.iva.net/blog/", timeout=0.1)
but this doesn't:
requests.get("http://www.iva.net/blog/", timeout=1)
I'm on python 2.7.5 and requests 1.2.3

Duplicate issue #1617: Inconsistent ConnectionError Behavior
Created: 2013-09-24T01:52:34Z
Looking for guidance to solve the following problem:
On dev env / MacOSX, the following:
url = "http://insurance-guide.netfirms.com"
response = requests.get(url, timeout=90, verify=False, stream=True)
results in:
ConnectionError: HTTPConnectionPool(host='insurance-guide.netfirms.com', port=80): Max retries exceeded with url: / (Caused by <class 'socket.gaierror'>: [Errno 8] nodename nor servname provided, or not known)
on prod env / Centos 6, the exact same code never timesout and just stays stuck forever...
both env are python 2.7.5 and requests 1.2.3
what could be the cause of the diff behavior on prod vs dev?

Closing comment (2013-09-24T02:52:47Z): oh, but wait,
the proposed work around is not working here... :-(
ie
https://github.com/kennethreitz/requests/issues/1577#issuecomment-23794576
Fred~
On Mon, Sep 23, 2013 at 7:46 PM, Ian Cordasco notifications@github.comwrote:

@laruellef https://github.com/laruellef yeah I was just about to go
looking for that issue. It almost certainly seems related to #1577https://github.com/kennethreitz/requests/issues/1577.
We're still waiting on the urllib3 PR that @Lukasahttps://github.com/Lukasaalluded to in that issue so I'm going to close this while we wait for that
to work itself out so we can provide that interface to you.
That said, if you run into timeout issues again, and setting it lower
doesn't resolve your issue, then open an issue. Otherwise it might be safe
to assume it's related to #1577https://github.com/kennethreitz/requests/issues/1577
.
—
Reply to this email directly or view it on GitHubhttps://github.com/kennethreitz/requests/issues/1617#issuecomment-24971338
.
Repository: psf/requests

Issue #1573: Specify password for SSL client side certificate
Created: 2013-09-03T13:14:44Z
As far as I know currently it's not possible to specify the password for the client side certificate you're using for authentication.
This is a bit of a problem because you typically always want to password protect your .pem file which contains the private key. openssl won't even let you create one without a password.

Duplicate issue #2519: Client Certificates w/Passphrases?
Created: 2015-03-30T15:55:43Z
Hi,
client certificates can be specified with the "cert" parameter.  If I pass an encrypted client certificate, the underlying OpenSSL call will query for the corresponding passphrase, but that is not really a feasible way of handling this for a larger session with multiple calls, because the password is obviously not cached in any way.
Is there any way to pass the passphrase to a connection with API calls so it is then passed on to OpenSSL?
Cheers,
Toby.

Closing comment (2019-06-27T18:55:05Z): I believe this is a duplicate of #1573?
Repository: psf/requests

Issue #2018: Re-order proxy precedence.
Created: 2014-04-25T03:09:20Z
Session.trust_env = False turns off the checking of environment variables for options including proxy settings (*_proxy). But urllib picks up and uses these environment proxy settings anyway. requests should pass the trust_env setting on to urllib. (Although I'm not sure if urllib has a similar override.)
(Proxy setting precedence should be sorted out here as well. They way it is now, environment proxy settings will interfere with (rather than be over-ridden by) the proxies argument in Session.request or requests.request calls and the Session.proxies config regardless of trust_env settings.)

Duplicate issue #3197: session proxies not honored during request
Created: 2016-05-16T17:21:01Z
Using a session object and setting the proxies dictionary does not affect the proxies used during a request.
ex: Still tries to use system proxy.
s = requests.Session()
s.proxies = {'http': None, 'https': None}
s.post(url='http://10.0.1.1', json={'test': 'data'})

Using proxies during each request works, but it would be great to set them at the session level. Specifically if you potentially have dozens or ".post()" or ".get()" calls throughout your script.
Any thoughts?

Closing comment (2016-05-16T17:23:07Z): Thanks for this! This is a duplicate of #2018.
Repository: psf/requests

Issue #5710: idna 3.0 version package conflict
Created: 2021-01-01T12:29:46Z
idna released version 3.0 but requests has a dependency on idna<3, this makes it impossible to keep up to date on both packages.
Expected Result
I want to be able to install the latest idna package alongside the latest requests package
Actual Result
ERROR: Cannot install -r requirements.txt (line 12) and idna==3.0 because these package versions have conflicting dependencies.

The conflict is caused by:

    The user requested idna==3.0

    requests 2.25.1 depends on idna<3 and >=2.5

Reproduction Steps
try to run pip install on a requirements.txt file with
requests==2.25.1
idna==3.0

System Information
multiple Python versions (3.6 up to 3.9) running on Docker containers inside Drone CI/CD

Duplicate issue #5804: idna-3 is not supported
Created: 2021-04-28T22:58:53Z
idna-3 has been released on Jan 1st. However, requests still requires idna<3 preventing a lot of projects from upgrading.
Expected Result
requests supporting idna-3.1
Actual Result
requests force idna<3
Reproduction Steps
Errr, install requests? ;-)
System Information
$ python -m requests.help
{
  "chardet": {
    "version": "4.0.0"
  },
  "cryptography": {
    "version": "3.4.7"
  },
  "idna": {
    "version": "2.10"
  },
  "implementation": {
    "name": "CPython",
    "version": "3.9.4"
  },
  "platform": {
    "release": "5.11.16-gentoo-dist",
    "system": "Linux"
  },
  "pyOpenSSL": {
    "openssl_version": "101010bf",
    "version": "20.0.1"
  },
  "requests": {
    "version": "2.25.1"
  },
  "system_ssl": {
    "version": "101010bf"
  },
  "urllib3": {
    "version": "1.26.4"
  },
  "using_pyopenssl": true
}

Closing comment (2021-04-28T23:01:56Z): Hi @mgorny, this is a duplicate of #5710. Please be sure to check open issues before posting new ones. Thanks!
Repository: psycopg/psycopg2

Issue #685: Illegal instruction on compiled binary
Created: 2018-03-02T16:20:24Z
This is a very odd one and it took me ages to pinpoint the error down to psycopg2.
Basically, from what I can tell, python fails when importing psycopg2 in the stack of imports of my app. I installed psycopg2 via pip install psycopg2-binary, and the Illegal instruction: 4 pops up right after launching the app via python app.py. There is literally no stack trace, just this one error coming up. I'm using SQLAlchemy to connect to a database and the way I have been able to pinpoint it to the psycopg2 package is that by changing connection string to a sqlite db, the app works just fine.
I have no idea how reproducible this is, nor what type of info might be relevant, but:
$ clang --version
Apple LLVM version 9.0.0 (clang-900.0.39.2)
Target: x86_64-apple-darwin17.4.0
$ uname -a
Darwin MSB-MARK-D06126 17.4.0 Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64 x86_64
psycopg2-binary==2.7.4
[UPDATE]
I:

Ran: pip uninstall psycopg2-binary && pip uninstall psycopg2
Installed pg locally (in order to have pg_conf)
Ran: pip install --no-binary :all: psycopg2-binary although this would be equivalent to pip install --no-binary :all: psycopg2

Now it works. So it clearly is an instruction in the compiled binary that my system doesn't know how to interpret.

Duplicate issue #696: Getting Illegal instruction error on macOS
Created: 2018-03-26T08:43:44Z
After installation and connection to my django settings file I keep getting an 'illegal instruction: 4' error when i run any django command e.g python manage.py runserver

Closing comment (2018-03-26T09:46:50Z): Dupe of #685
Please install psycopg from source.
Repository: psycopg/psycopg2

Issue #884: RealDictRow.items() behave inconsistently on duplicate row names
Created: 2019-04-04T14:47:56Z
Hi,
When a SELECT query has two columns with the same name, cur.fetchone().items() behaves inconsistently:
>>> import psycopg2, psycopg2.extras
>>> db = psycopg2.connect('service=swh-replica', cursor_factory=psycopg2.extras.RealDictCursor)
>>> cur = db.cursor()
>>> cur.execute('SELECT 1 AS a, 2 AS a;')
>>> row = cur.fetchone()
>>> list(row.items())
[('a', 2), ('a', 2)]
>>> row
{'a': 2}
>>> len(row)
1

row.items() having a length not equal to len(row) causes bugs in users of this dictionary that expect them to be equal.
eg. we noticed this bug in a script that queries psycopg2 with a duplicate column name (unintentionally), and the RealDictRow ends up being passed to msgpack.packb, which produces corrupted data when this happens.
This issue happens on psycopg2 2.8, but not 2.7.7.

Duplicate issue #896: Cannot update column in a RealDictRow
Created: 2019-04-10T20:18:32Z
File "/x/y/.pyenv/versions/3.6.6/envs/z/lib/python3.6/site-packages/psycopg2/extras.py", line 282, in __setitem__
    super(RealDictRow, self).__setitem__(mapping[key], value)
graphql.error.located_error.GraphQLLocatedError: list indices must be integers or slices, not str

Example code:
row[col] = some_function(row[col], some_param).decode('utf-8')

(where row is an instance of RealDictRow)
psycopg2-binary v2.8.1
cc815e8

Closing comment (2019-04-10T21:49:27Z): It's probably more related to #884. Could you check if 4058f36 fixes the problem?
Repository: psycopg/psycopg2

Issue #425: manylinux wheels
Created: 2016-04-28T19:10:02Z
It would be nice to have the new manylinux wheels available on PyPI.
https://www.python.org/dev/peps/pep-0513/
https://github.com/pypa/manylinux

Duplicate issue #479: Provide Wheel (binary) distribution for OSX
Created: 2016-10-04T22:24:17Z
Is this fairly easy to do / on the roadmap?
We use OSX development machines and occasionally run into nasty errors when trying to compile psycopg2 from source, which in turn pulls some OpenSSL libraries which are not in standard location when using Homebrew with OSX. In general would be nice to be able to install psycopg2 quickly!
TL;DR what would be involved in getting a wheel for OSX? is it a CI build machine issue? Travis CI seems to support an OSX build environment, not sure what this project uses..

Closing comment (2016-10-05T06:59:26Z): Duplicate of #425
and all others: https://github.com/psycopg/psycopg2/issues?utf8=%E2%9C%93&q=is%3Aissue%20wheel
Repository: psycopg/psycopg2

Issue #517: `connect` with user/password = None fails in 2.7
Created: 2017-03-01T19:14:13Z
In the latest release (2.7), calling connect with user/password = None fails. In versions < 2.6.2 this would succeed
>>> from psycopg2 import connect
>>> connect(host='localhost', port=5432, database='basedb', user=None, password=None)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/patrick/.virtualenvs/sigopt/lib/python2.7/site-packages/psycopg2/__init__.py", line 130, in connect
    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: FATAL:  role "None" does not exist

Is this new expected behaviour? If so, should 2.7 be a new major release (3.0) to indicate backwards-incompatible changes?

Duplicate issue #523: Cannot leave out port number anymore (regression) in 2.7
Created: 2017-03-03T16:28:58Z
Port number now seem to be required when creating connections. This is a regression (imho) towards 2.6
    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
OperationalError: invalid port number: "None"```

Closing comment (2017-03-03T17:38:36Z): Seems like a duplicate of #517.
The problem is already fixed, will be released in 2.7.1.
Repository: psycopg/psycopg2

Issue #1032: The C module should be optional
Created: 2020-01-24T17:51:50Z
There should be a pure Python implementation of _psycopg.so using the libpq in cffi.
At install time compiling should be attempted, and the library should fall back to Python if import fails.

Duplicate issue #1077: Remove dependency on pg_config
Created: 2020-04-07T15:45:53Z
The dependency on pg_config in the installation process has too heavyweight dependencies.

Closing comment (2020-04-08T23:19:49Z): I had no doubt about that. Dupe of #1032 anyway.
Repository: psycopg/psycopg2

Issue #1753: High macOS deployment targets for psycopg2-binary
Created: 2024-11-19T10:50:21Z
This is a bug tracker
If you have a question, such has "how do you do X with Python/PostgreSQL/psycopg2" please write to the mailing list or open a question instead.
Before opening this ticket, please confirm that:

 I am running the latest version of pip, i.e. typing pip --version you get this version.
 I have read the installation documentation and the frequently asked questions
 If install failed, I typed pg_config on the command line and I obtained an output instead of an error.

Please complete the following information:

OS: macOS 13 arm64
Psycopg version: 2.9.10
Python version: 3.12.7
PostgreSQL version:
pip version: 24.3.1

The MACOSX_DEPLOYMENT_TARGET sets the minimum version of macOS that the psycopg2-binary wheels will install on so the introduction of setting MACOSX_DEPLOYMENT_TARGET to the CI runner version blocks installs on anything older than the CI runner. As of 2.9.10, pip install psycopg2-binary on a macOS <14.0 arm64 or <12.0 x86_64 machine will ignore the wheels, pull the sdist, probably fail to build from source and give the misleading advice to try pip install psycopg2-binary instead.
Judging by the lack of drop support for macOS 13 entries in the changelog and macOS 13 still having another year before its EOL date, I'm guessing that wasn't intentional?
Incidentally, why publish sdists for the psycopg2-binary package?

Duplicate issue #1756: Update psycopg2-binary 2.9.10 error
Created: 2024-11-25T04:25:48Z
OS: macOS 15.1.1
Psycopg version: 2.9.10
Python version: 3.9.9
PostgreSQL version: 16.1
pip version: 23.3.2
poetry version: 1.8.4
I updated psycopg2-binary version from 2.9.9 to 2.9.10 using poetry and I got the following error:

ld: library 'ssl' not found
clang: error: linker command failed with exit code 1 (use -v to see invocation)
error: command '/usr/bin/gcc' failed with exit code 1
at ~/Library/Application Support/pypoetry/venv/lib/python3.12/site-packages/poetry/installation/chef.py:164 in _prepare
160│
161│                 error = ChefBuildError("\n\n".join(message_parts))
162│
163│             if error is not None:
→ 164│                 raise error from None
165│
166│             return path
167│
168│     def _prepare_sdist(self, archive: Path, destination: Path | None = None) -> Path:
Note: This error originates from the build backend, and is likely not a problem with poetry but with psycopg2-binary (2.9.10) not supporting PEP 517 builds. You can verify this by running 'pip wheel --no-cache-dir --use-pep517 "psycopg2-binary (==2.9.10)"'.

Closing comment (2024-11-25T12:02:46Z): Hello,
this is probably just a manifestation of the problem reported in #1753.
You can specify psycopg != 2.9.10 (in the assumption that we will merge #1755 and fix the problem in the next version), or upgrade your OS. Psycopg 3 has likely the same problem and should receive a similar fix.
Repository: psycopg/psycopg2

Issue #884: RealDictRow.items() behave inconsistently on duplicate row names
Created: 2019-04-04T14:47:56Z
Hi,
When a SELECT query has two columns with the same name, cur.fetchone().items() behaves inconsistently:
>>> import psycopg2, psycopg2.extras
>>> db = psycopg2.connect('service=swh-replica', cursor_factory=psycopg2.extras.RealDictCursor)
>>> cur = db.cursor()
>>> cur.execute('SELECT 1 AS a, 2 AS a;')
>>> row = cur.fetchone()
>>> list(row.items())
[('a', 2), ('a', 2)]
>>> row
{'a': 2}
>>> len(row)
1

row.items() having a length not equal to len(row) causes bugs in users of this dictionary that expect them to be equal.
eg. we noticed this bug in a script that queries psycopg2 with a duplicate column name (unintentionally), and the RealDictRow ends up being passed to msgpack.packb, which produces corrupted data when this happens.
This issue happens on psycopg2 2.8, but not 2.7.7.

Duplicate issue #891: 2.7.7 to 2.8.1 - RealDictRow.items() behavior change
Created: 2019-04-08T23:48:08Z
When upgrading from 2.7.7 to 2.8.1 I noticed that RealDictRow does not behave the same. Previously, I was able to call items() on a RealDictRow and it'd return (key, value) tuples, like a Python dict.
In 2.8.1 it instead returns a (RealDictRow, ListOfKeys) as the first tuple. The remaining items are (key, value) pairs as expected.

Closing comment (2019-04-09T00:38:53Z): Yes, this is a duplicate of #884, the fix will be released in 2.8.2.
Your query has an undefined behaviour: you have two fields called the same way, what a name mapping would return is totally arbitrary. This bug affect only those queries which are broken anyway, so yes, a fix will be released soon, butfirst I'll wait a couple of days for feedback from other issued before packing 2.8.2.
Repository: pydantic/pydantic-ai

Issue #71: Add ability to customize model calls
Created: 2024-11-19T15:03:04Z
As noted in the OpenAI docs, there are various parameters to the API that are not currently exposed, such as temperature, frequency_penalty, logit_bias, etc. We should provide some way to control what values are used when the agent makes calls.

Duplicate issue #171: Multiple Responses with Gemini/Vertex LLM
Created: 2024-12-07T15:02:08Z
Gemini/Vertex has ability to provide multiple response with candidate_count='n' , can you add an ability in Agent API to utilize the same

Closing comment (2024-12-08T12:34:36Z): Thanks for creating the issue.
Duplicate of #71, let's continue the conversation there.