Devajith

Results 17 comments of Devajith

I tried adding amazon. They have a stringent policy against web scraping. Every request returns an HTML page given below: To discuss automated access to Amazon data, please contact [email protected]....

Tried that too. Exactly copying the headers in the browser didn't work. I guess they have some other mechanism to prevent scraping.

Wikipedia already has an open API, we don't have to parse the webpages. Here's the search api : https://m.mediawiki.org/wiki/API:Search_and_discovery

Tablegen'd file for reference: ```bash dvalapar@emmanouil:~/work/root (dev.cling-tablegen)$ llvm-tblgen-16 -I /home/dvalapar/work/root/interpreter/llvm-project/llvm/include /home/dvalapar/work/root/interpreter/cling/include/cling/Interpreter/ClingOptions.td -gen -opt-parser-defs /*===- TableGen'erated file -------------------------------------*- C++ -*-===*\ |* *| |* Option Parsing Definitions *| |* *| |* Automatically...

> Try to change these lines. on Windows, the binaries are in the `$/bin` directory, `$` being only known at build time Thanks @bellenot

Detecting if a debugger is attached isn't very straightforward unless on Windows. I can add something similar to the solution here: https://stackoverflow.com/questions/3596781/how-to-detect-if-the-current-process-is-being-run-by-gdb, but not sure if that's ideal.

New warning message (for reference): ![Screenshot from 2024-02-09 11-19-18](https://github.com/root-project/root/assets/29475282/cb204f9e-b92b-4bdb-ac5b-d5f7dfe87333)

> New warning message (for reference): ![Screenshot from 2024-02-09 11-19-18](https://private-user-images.githubusercontent.com/29475282/303646838-cb204f9e-b92b-4bdb-ac5b-d5f7dfe87333.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDc0OTUyMjEsIm5iZiI6MTcwNzQ5NDkyMSwicGF0aCI6Ii8yOTQ3NTI4Mi8zMDM2NDY4MzgtY2IyMDRmOWUtYjkyYi00YmRiLWFjNWItZDVmN2RmZTg3MzMzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAyMDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMjA5VDE2MDg0MVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTI5MmNiYTg0NTdlN2Q3MjY3MWE0NWU1NmVkN2FhNTk3NWUyMTUwNWIwNGUxODEwZmMwNWNhZWRiMTM5NjRmMTgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.k-Aaea9NdahxJyiwhhybi-JgL-1CD-WJDYlSoIohm_8) @pcanal: This is how the warning message looks like. The warning (-Wdeprecated-declarations) I think make sense for deprecating this feature.

Added JIRA issues in the PR description. Couldn't find any open GitHub issues.

> In principle LGTM; is it possible to test this in our infrastructure, to make sure the warning pops up where we expect it and that the "feature" continues to...