<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>debug on Jaaved Ali Khan</title><link>https://jaaved.netlify.app/tags/debug/</link><description>Recent content in debug on Jaaved Ali Khan</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 10 Jul 2023 14:21:27 +0400</lastBuildDate><atom:link href="https://jaaved.netlify.app/tags/debug/index.xml" rel="self" type="application/rss+xml"/><item><title>Roam-ref protocol debugging</title><link>https://jaaved.netlify.app/notes/202109072254-roam_ref_protocol_on_windows_troubleshooting_org_roam/</link><pubDate>Mon, 10 Jul 2023 14:21:27 +0400</pubDate><guid>https://jaaved.netlify.app/notes/202109072254-roam_ref_protocol_on_windows_troubleshooting_org_roam/</guid><description>It seems to work on my PC without the “tricks” I am writing in the new chapter. Two things worth checking:
Have started Emacs Server? – e.g. M-x server-start Have loaded org-protocol and org-roam-protocol? – e.g. M-x load-library Alternative to M-x, you can put this in your config.
(server-start) (require &amp;#39;org-protocol) (require &amp;#39;org-roam-protocol) image 1432×1286 55.9 KB</description></item><item><title>ssl - curl –cacert vs python requests verify - Stack Overflow</title><link>https://jaaved.netlify.app/notes/202109291945-ssl_curl_cacert_vs_python_requests_verify_stack_overflow/</link><pubDate>Mon, 10 Jul 2023 14:21:22 +0400</pubDate><guid>https://jaaved.netlify.app/notes/202109291945-ssl_curl_cacert_vs_python_requests_verify_stack_overflow/</guid><description>&amp;hellip; it&amp;rsquo;s an intermediate CA
Having only the intermediate CA in the trust store is not sufficient for validation of the certificate, at least not with the current versions of Python. This feature would require the use of the OpenSSL flag X509_V_FLAG_PARTIAL_CHAIN for verification, which is neither currently exposed by Python nor set by default.
Contrary to this curl sets this flag by default in newer versions and thus works.</description></item><item><title>Authentication failed with Django APM agent</title><link>https://jaaved.netlify.app/notes/202110101308-failed_to_verify_server_certificate_apm_go_agent_with_eck_elastic_observability_apm_discuss_the_elastic_stack/</link><pubDate>Mon, 10 Jul 2023 14:21:20 +0400</pubDate><guid>https://jaaved.netlify.app/notes/202110101308-failed_to_verify_server_certificate_apm_go_agent_with_eck_elastic_observability_apm_discuss_the_elastic_stack/</guid><description>My use case # APM Django agent was not able to communicate with APM server, was failing with error:
Oops. That didn&amp;#39;t work. The following error occured: JSON decoding error while fetching server information: Expecting value: line 1 column 1 (char 0) Failed to submit message: &amp;#39;HTTP 401: {&amp;#34;error&amp;#34;:&amp;#34;authentication failed: missing or improperly formatted Authorization header: expected \&amp;#39;Authorization: Bearer secret_token\&amp;#39; or \&amp;#39;Authorization: ApiKey base64(API key ID:API key)\&amp;#39;&amp;#34;}\n&amp;#39; Following the solution and creating following manifest file worked:</description></item></channel></rss>