[I] Couchdb stoped writing to the journald logs [couchdb]

2024-04-01 Thread via GitHub
tahirshak opened a new issue, #5022: URL: https://github.com/apache/couchdb/issues/5022 [NOTE]: # ( ^^ Provide a general summary of the issue in the title above. ^^ ) ## Description We are using couchdb v 3.3.3 with the log settings as : ``` "log": {

Re: [I] Unable to query fields indexed by nouveau [couchdb]

2024-03-31 Thread via GitHub
GMishx commented on issue #4997: URL: https://github.com/apache/couchdb/issues/4997#issuecomment-2029154672 Will it make sense to use the field type of the index? We already have types `double`, `string` and `text` to differentiate the types of values. (just guessing) -- This is an

Re: [I] Unable to query fields indexed by nouveau [couchdb]

2024-03-29 Thread via GitHub
rnewson commented on issue #4997: URL: https://github.com/apache/couchdb/issues/4997#issuecomment-2027509718 posted a draft PR that addresses this, with some extensive prose on whether it's a good idea or not. -- This is an automated message from the Apache Git Service. To respond to the

[PR] use PointsConfigMap so numeric query and numeric range query work cleanly [couchdb]

2024-03-29 Thread via GitHub
rnewson opened a new pull request, #5021: URL: https://github.com/apache/couchdb/pull/5021 ## Overview Nouveau has a (somewhat ugly) extension to the query syntax that auto-detects if the searched _value_ is a number. if so, it switches to querying the field as a number.

Re: [PR] fix(`nouveau`): location of release artifacts on Windows [couchdb]

2024-03-28 Thread via GitHub
big-r81 merged PR #5020: URL: https://github.com/apache/couchdb/pull/5020 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] fix(`nouveau`): location of release artifacts on Windows [couchdb]

2024-03-28 Thread via GitHub
big-r81 opened a new pull request, #5020: URL: https://github.com/apache/couchdb/pull/5020 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

Re: [I] Unable to query fields indexed by nouveau [couchdb]

2024-03-28 Thread via GitHub
rnewson commented on issue #4997: URL: https://github.com/apache/couchdb/issues/4997#issuecomment-2025166485 that's helpful to know, thanks. I'm looking at changing the "magical" nature of numeric queries. I extended/altered the basic lucene query syntax to auto-detect numbers but it has

Re: [PR] Address vulnerabilities [couchdb-fauxton]

2024-03-28 Thread via GitHub
Antonio-Maranhao merged PR #1433: URL: https://github.com/apache/couchdb-fauxton/pull/1433 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [I] Unable to query fields indexed by nouveau [couchdb]

2024-03-28 Thread via GitHub
GMishx commented on issue #4997: URL: https://github.com/apache/couchdb/issues/4997#issuecomment-2024970658 BTW for context, I am translating the project [sw360](https://github.com/eclipse-sw360/sw360) which currently uses [couchdb-lucene](https://github.com/rnewson/couchdb-lucene) to

Re: [I] Unable to query fields indexed by nouveau [couchdb]

2024-03-28 Thread via GitHub
rnewson commented on issue #4997: URL: https://github.com/apache/couchdb/issues/4997#issuecomment-2024959631 ```jshell> var nf = NumberFormat.getInstance(Locale.getDefault()); nf ==> java.text.DecimalFormat@674dc jshell> nf.parse("4"); $5 ==> 4 jshell> nf.parse("4.2");

Re: [I] Unable to query fields indexed by nouveau [couchdb]

2024-03-28 Thread via GitHub
rnewson commented on issue #4997: URL: https://github.com/apache/couchdb/issues/4997#issuecomment-2024958991 ok, the short answer is that the (nouveau-specific) query parser interprets "4.2.0" as a number and performs a numeric query, not a text/string query. I'm surprised by that, but

Re: [I] Unable to query fields indexed by nouveau [couchdb]

2024-03-28 Thread via GitHub
rnewson commented on issue #4997: URL: https://github.com/apache/couchdb/issues/4997#issuecomment-2024928403 thanks. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [I] Unable to query fields indexed by nouveau [couchdb]

2024-03-28 Thread via GitHub
GMishx commented on issue #4997: URL: https://github.com/apache/couchdb/issues/4997#issuecomment-2024866438 Here are the outputs as requested. I am getting same results for GET and POST queries. Output of analyze: ``` $ curl --user "admin:admin" --silent

[PR] Address vulnerabilities [couchdb-fauxton]

2024-03-28 Thread via GitHub
fryjordan opened a new pull request, #1433: URL: https://github.com/apache/couchdb-fauxton/pull/1433 ## Overview Vulnerabilities were found in Fauxton dependencies. The changes in this PR resolve them. ``` # npm audit report express <4.19.2 Severity: moderate

Re: [I] Unable to query fields indexed by nouveau [couchdb]

2024-03-28 Thread via GitHub
rnewson commented on issue #4997: URL: https://github.com/apache/couchdb/issues/4997#issuecomment-2024846858 You specify the `keyword` analyzer for all fields. for input "4.2.0" that tokenizes to "4.2.0". Can you show the result of querying the view with `?q=version:4.2.0`,

Re: [I] Unable to query fields indexed by nouveau [couchdb]

2024-03-28 Thread via GitHub
GMishx commented on issue #4997: URL: https://github.com/apache/couchdb/issues/4997#issuecomment-2024829125 @rnewson Even using the provided suggestions from #5018 fail for different case. I have a document with fields name and version. Version is stored as a string in couchdb and

[PR] Bump express from 4.18.1 to 4.19.2 [couchdb-fauxton]

2024-03-28 Thread via GitHub
dependabot[bot] opened a new pull request, #1432: URL: https://github.com/apache/couchdb-fauxton/pull/1432 Bumps [express](https://github.com/expressjs/express) from 4.18.1 to 4.19.2. Release notes Sourced from https://github.com/expressjs/express/releases;>express's releases.

Re: [I] Investigate using QuickJS as a Javascript Engine [couchdb]

2024-03-27 Thread via GitHub
nickva commented on issue #4448: URL: https://github.com/apache/couchdb/issues/4448#issuecomment-2024385080 > That is why I had also to patch the build_js.escript in order to remove the hardcoded quickjs path. In yocto build the quickjs will be available in PATH for couchdb build. I think

Re: [I] Investigate using QuickJS as a Javascript Engine [couchdb]

2024-03-27 Thread via GitHub
joaohf commented on issue #4448: URL: https://github.com/apache/couchdb/issues/4448#issuecomment-2024182609 Hi, The patch for src/couch_quickjs/rebar.config.script is really handy. And I think it makes sense. Most of Yocto Project work is related to fix cross compile build

Re: [PR] feat(`mango`): rolling execution statistics [couchdb]

2024-03-27 Thread via GitHub
pgj commented on PR #4958: URL: https://github.com/apache/couchdb/pull/4958#issuecomment-2022886142 Thank you all for your help too! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

Re: [PR] feat(`mango`): rolling execution statistics (exploration) [couchdb]

2024-03-27 Thread via GitHub
pgj commented on PR #4735: URL: https://github.com/apache/couchdb/pull/4735#issuecomment-2022888634 Closing this in favor of #4958. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

Re: [PR] feat(`mango`): rolling execution statistics (exploration) [couchdb]

2024-03-27 Thread via GitHub
pgj closed pull request #4735: feat(`mango`): rolling execution statistics (exploration) URL: https://github.com/apache/couchdb/pull/4735 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the

Re: [I] Inconsistent execution statistics for Mango queries [couchdb]

2024-03-27 Thread via GitHub
pgj closed issue #4560: Inconsistent execution statistics for Mango queries URL: https://github.com/apache/couchdb/issues/4560 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment.

Re: [PR] feat(`mango`): rolling execution statistics [couchdb]

2024-03-27 Thread via GitHub
pgj merged PR #4958: URL: https://github.com/apache/couchdb/pull/4958 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [I] Investigate using QuickJS as a Javascript Engine [couchdb]

2024-03-26 Thread via GitHub
nickva commented on issue #4448: URL: https://github.com/apache/couchdb/issues/4448#issuecomment-2021869435 @joaohf very interesting, I don't know much about Yocto project, so may not be able to help much with the diff. I did however apply this patch to make it easier for you a bit:

Re: [I] Investigate using QuickJS as a Javascript Engine [couchdb]

2024-03-26 Thread via GitHub
joaohf commented on issue #4448: URL: https://github.com/apache/couchdb/issues/4448#issuecomment-2021731343 Hi @nickva I did a first round building your branch in yocto context. The build was ok after some changes (please see the WIP patch

Re: [I] "apache.jfrog.io" no more available. Where are the .deb packages now? [couchdb]

2024-03-26 Thread via GitHub
hcgrove commented on issue #4489: URL: https://github.com/apache/couchdb/issues/4489#issuecomment-2020672652 We have our own mirror of the Ubuntu packages, and that still seems affected? We use `apt-mirror` to make that repo, the repositories apt-mirror is configured to mirror are:

Re: [I] Admin-level audit logging [couchdb]

2024-03-26 Thread via GitHub
mwasson74 commented on issue #1227: URL: https://github.com/apache/couchdb/issues/1227#issuecomment-2020405862 +1 in 2024 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment.

Re: [I] Unable to query fields indexed by nouveau [couchdb]

2024-03-26 Thread via GitHub
rnewson commented on issue #4997: URL: https://github.com/apache/couchdb/issues/4997#issuecomment-2019907296 no problem! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [I] Unable to query fields indexed by nouveau [couchdb]

2024-03-26 Thread via GitHub
GMishx commented on issue #4997: URL: https://github.com/apache/couchdb/issues/4997#issuecomment-2019891010 Hey, thanks for the updates. The documentation makes the type field more clear in #5018. -- This is an automated message from the Apache Git Service. To respond to the message,

Re: [I] Unable to query fields indexed by nouveau [couchdb]

2024-03-26 Thread via GitHub
rnewson commented on issue #4997: URL: https://github.com/apache/couchdb/issues/4997#issuecomment-2019878585 rehi (I've been out on vacation the last few weeks). I've mocked up a few approaches to this locally and I don't like any of them, they all either have a non-trivial overhead

Re: [PR] expand nouveau docs on field types [couchdb]

2024-03-26 Thread via GitHub
rnewson merged PR #5018: URL: https://github.com/apache/couchdb/pull/5018 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [I] Unable to query fields indexed by nouveau [couchdb]

2024-03-26 Thread via GitHub
rnewson closed issue #4997: Unable to query fields indexed by nouveau URL: https://github.com/apache/couchdb/issues/4997 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [PR] Remove unused build files [couchdb]

2024-03-26 Thread via GitHub
big-r81 merged PR #5019: URL: https://github.com/apache/couchdb/pull/5019 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [I] Investigate using QuickJS as a Javascript Engine [couchdb]

2024-03-25 Thread via GitHub
nickva commented on issue #4448: URL: https://github.com/apache/couchdb/issues/4448#issuecomment-2019338794 @joaohf there is now an option to completely disable Spidermonkey. For that add the `--disable-spidermonkey` option to `./configure`. Give that a try, I didn't test it extensively

Re: [PR] Add QuickJS as a Javascript engine option [couchdb]

2024-03-25 Thread via GitHub
nickva commented on PR #4627: URL: https://github.com/apache/couchdb/pull/4627#issuecomment-2019336436 Another update: * The scanner app moved to it's own PR https://github.com/apache/couchdb/pull/5014. With a sample plugin to detect CouchDB 4.x planned deprecated ddoc features.

Re: [PR] Add QuickJS as a Javascript engine option [couchdb]

2024-03-25 Thread via GitHub
nickva commented on code in PR #4627: URL: https://github.com/apache/couchdb/pull/4627#discussion_r1538552664 ## configure: ## @@ -298,7 +318,7 @@ if [ "${ARCH}" = "aarch64" ] && [ "${SM_VSN}" = "60" ]; then exit 1 fi -if [ "${ERLANG_OS}" = "unix" ]; then +if [

[PR] Remove unused build files [couchdb]

2024-03-25 Thread via GitHub
big-r81 opened a new pull request, #5019: URL: https://github.com/apache/couchdb/pull/5019 Breaking up is never easy, we know, but they have to go. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go

[PR] expand nouveau docs on field types [couchdb]

2024-03-25 Thread via GitHub
rnewson opened a new pull request, #5018: URL: https://github.com/apache/couchdb/pull/5018 Closes: https://github.com/apache/couchdb/issues/4997 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go

Re: [PR] Remove boot_dev_cluster.sh [couchdb]

2024-03-25 Thread via GitHub
nickva merged PR #5017: URL: https://github.com/apache/couchdb/pull/5017 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [I] Installing from yum repo fails repomd.xml signature could not be verified for couchdb [couchdb]

2024-03-25 Thread via GitHub
big-r81 closed issue #5016: Installing from yum repo fails repomd.xml signature could not be verified for couchdb URL: https://github.com/apache/couchdb/issues/5016 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

Re: [I] Installing from yum repo fails repomd.xml signature could not be verified for couchdb [couchdb]

2024-03-25 Thread via GitHub
big-r81 commented on issue #5016: URL: https://github.com/apache/couchdb/issues/5016#issuecomment-2018682967 All should work again! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

Re: [I] "apache.jfrog.io" trial expired [couchdb]

2024-03-25 Thread via GitHub
big-r81 commented on issue #5010: URL: https://github.com/apache/couchdb/issues/5010#issuecomment-2018682370 All should work again! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

Re: [I] "apache.jfrog.io" trial expired [couchdb]

2024-03-25 Thread via GitHub
big-r81 closed issue #5010: "apache.jfrog.io" trial expired URL: https://github.com/apache/couchdb/issues/5010 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

Re: [I] "apache.jfrog.io" no more available. Where are the .deb packages now? [couchdb]

2024-03-25 Thread via GitHub
big-r81 commented on issue #4489: URL: https://github.com/apache/couchdb/issues/4489#issuecomment-2018680384 fyi: all should be functional again! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

Re: [I] Swagger UI or Postman Collection [couchdb]

2024-03-25 Thread via GitHub
RafaelFigueiredo commented on issue #4213: URL: https://github.com/apache/couchdb/issues/4213#issuecomment-201838 > There is a Postman collection here: https://www.postman.com/galactic-comet-36406/workspace/couchdb/collection/15985155-f511300e-848e-4ab2-a0a2-da13cb2e1065

[PR] Remove boot_dev_cluster.sh [couchdb]

2024-03-25 Thread via GitHub
nickva opened a new pull request, #5017: URL: https://github.com/apache/couchdb/pull/5017 This script is not used anywhere. We start a dev cluster in dev/run for local development and for tests. -- This is an automated message from the Apache Git Service. To respond to the

Re: [I] "apache.jfrog.io" no more available. Where are the .deb packages now? [couchdb]

2024-03-25 Thread via GitHub
rnewson commented on issue #4489: URL: https://github.com/apache/couchdb/issues/4489#issuecomment-2018593219 if jfrog's uptime is insufficient for you (I think this incident is unlikely to occur again, fwiw) you can make your own mirror of our debian repository easily enough and pull

Re: [I] Nouveau Availability [couchdb]

2024-03-25 Thread via GitHub
rnewson commented on issue #5002: URL: https://github.com/apache/couchdb/issues/5002#issuecomment-2018014335 oh, and 3) yes, you would need to delete databases within each cluster separately, as db deletion is not propagated by replication. -- This is an automated message from the Apache

Re: [I] Nouveau Availability [couchdb]

2024-03-25 Thread via GitHub
rnewson commented on issue #5002: URL: https://github.com/apache/couchdb/issues/5002#issuecomment-2018012751 our slack is the best place for this kind of chat (couchdb.slack.com). a couple of notes; 1) the 'r' and 'w' fields under cluster do nothing, they are no longer used by

Re: [I] Nouveau Availability [couchdb]

2024-03-25 Thread via GitHub
Sliosh commented on issue #5002: URL: https://github.com/apache/couchdb/issues/5002#issuecomment-2017894768 Thanks for the fast fix. I will test this later. > as an aside, we strongly recommend that couchdb clusters do not span locations I thought that with the following

Re: [I] Installing from yum repo fails repomd.xml signature could not be verified for couchdb [couchdb]

2024-03-25 Thread via GitHub
CSLTech commented on issue #5016: URL: https://github.com/apache/couchdb/issues/5016#issuecomment-2017735278 See https://github.com/apache/couchdb/issues/5010 . All the apache jfrog repositories are down since friday. -- This is an automated message from the Apache Git Service. To

Re: [PR] nouveau: fix rexi_DOWN clause [couchdb]

2024-03-25 Thread via GitHub
rnewson merged PR #5015: URL: https://github.com/apache/couchdb/pull/5015 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[I] Installing from yum repo fails repomd.xml signature could not be verified for couchdb [couchdb]

2024-03-25 Thread via GitHub
maiya22 opened a new issue, #5016: URL: https://github.com/apache/couchdb/issues/5016 Description Attempting to follow Installation using the Apache CouchDB convenience binary packages on a RedHat/CentOS system fails to install the package i am facing this issue couchdb is

Re: [I] "apache.jfrog.io" no more available. Where are the .deb packages now? [couchdb]

2024-03-25 Thread via GitHub
vectorselector commented on issue #4489: URL: https://github.com/apache/couchdb/issues/4489#issuecomment-2017566656 this issue should not be closed while the infrastructural single-point-of-failure exists, which was never addressed. this breaks apt for production systems -- This is an

Re: [I] Nouveau Availability [couchdb]

2024-03-25 Thread via GitHub
rnewson commented on issue #5002: URL: https://github.com/apache/couchdb/issues/5002#issuecomment-2017534078 I figured it out and have posted a PR to fix the fault tolerance. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[PR] nouveau: fix rexi_DOWN clause [couchdb]

2024-03-25 Thread via GitHub
rnewson opened a new pull request, #5015: URL: https://github.com/apache/couchdb/pull/5015 reported in https://github.com/apache/couchdb/issues/5002 the badrecord is because we execute the second clause of handle_message and mess up the internal state (just returning the Counters

Re: [I] Nouveau Availability [couchdb]

2024-03-25 Thread via GitHub
rnewson commented on issue #5002: URL: https://github.com/apache/couchdb/issues/5002#issuecomment-2017498815 further aside, you don't have to have a nouveau node for each couchdb node, you can safely point multiple couchdb nodes at the same nouveau node. whether this is better or worse for

Re: [I] Nouveau Availability [couchdb]

2024-03-25 Thread via GitHub
rnewson commented on issue #5002: URL: https://github.com/apache/couchdb/issues/5002#issuecomment-2017496690 as an aside, we strongly recommend that couchdb clusters do not span locations (offices in your case). the nodes of any given cluster should be very close together (<1ms ping time).

Re: [I] Nouveau Availability [couchdb]

2024-03-25 Thread via GitHub
rnewson commented on issue #5002: URL: https://github.com/apache/couchdb/issues/5002#issuecomment-2017449263 Nouveau will be marked EXPERIMENTAL in couchdb 3.4.0 as we gather feedback from the community. I certainly expect fault-tolerance from Nouveau so will look into your finding

Re: [I] "apache.jfrog.io" no more available. Where are the .deb packages now? [couchdb]

2024-03-25 Thread via GitHub
Nithe14 commented on issue #4489: URL: https://github.com/apache/couchdb/issues/4489#issuecomment-2017451527 Now it redirects to landing.jfrog.com and consistently returns an HTTP 409 error. At least for the RPM repo. -- This is an automated message from the Apache Git Service. To

Re: [I] Installing from yum repo fails with HTTP 403 error [couchdb]

2024-03-25 Thread via GitHub
maiya22 commented on issue #3966: URL: https://github.com/apache/couchdb/issues/3966#issuecomment-201760 i am facing this issue couchdb is failing due to below error etrieving key from https://couchdb.apache.org/repo/keys.asc Importing GPG key 0x7A00258D: Userid : "The

[PR] Optimize getParams + Prettify utils [couchdb-fauxton]

2024-03-24 Thread via GitHub
RedYetiDev opened a new pull request, #1431: URL: https://github.com/apache/couchdb-fauxton/pull/1431 ## Overview This PR optimizes the `getParams` function to prevent the use of needless statements (such as while loops). With less statements, the function will block the event

Re: [I] "apache.jfrog.io" trial expired [couchdb]

2024-03-24 Thread via GitHub
lore-10 commented on issue #5010: URL: https://github.com/apache/couchdb/issues/5010#issuecomment-2016856032 Hello, are there other ways to install couchDB while the issue gets fixed? I'm trying to set up a server but i get an error because of this. Thank you -- This is an automated

Re: [I] "apache.jfrog.io" trial expired [couchdb]

2024-03-24 Thread via GitHub
Lorenzo10122002 commented on issue #5010: URL: https://github.com/apache/couchdb/issues/5010#issuecomment-2016855400 Hello, are there other ways to install couchDB while the issue gets fixed? I'm trying to set up a server but i get an error because of this. Thank you -- This is an

[PR] Implement a background db / ddoc / doc scanner [couchdb]

2024-03-23 Thread via GitHub
nickva opened a new pull request, #5014: URL: https://github.com/apache/couchdb/pull/5014 [WIP] Everything is place except docs and tests The app scans all the dbs and docs. It has a plugin system to allow gathering various things from a cluster. The first use is to scan all the

Re: [PR] Improve dist diagnostics [couchdb]

2024-03-23 Thread via GitHub
nickva merged PR #5013: URL: https://github.com/apache/couchdb/pull/5013 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Improve dist diagnostics [couchdb]

2024-03-23 Thread via GitHub
nickva commented on code in PR #5013: URL: https://github.com/apache/couchdb/pull/5013#discussion_r1536690522 ## src/mem3/src/mem3.erl: ## @@ -423,31 +424,127 @@ engine(Opts) when is_list(Opts) -> %% Check whether a node is up or down %% side effect: set up a connection to

Re: [PR] Improve dist diagnostics [couchdb]

2024-03-23 Thread via GitHub
nickva commented on code in PR #5013: URL: https://github.com/apache/couchdb/pull/5013#discussion_r1536690522 ## src/mem3/src/mem3.erl: ## @@ -423,31 +424,127 @@ engine(Opts) when is_list(Opts) -> %% Check whether a node is up or down %% side effect: set up a connection to

Re: [PR] Improve dist diagnostics [couchdb]

2024-03-23 Thread via GitHub
nickva commented on code in PR #5013: URL: https://github.com/apache/couchdb/pull/5013#discussion_r1536689480 ## src/mem3/src/mem3.erl: ## @@ -423,31 +424,127 @@ engine(Opts) when is_list(Opts) -> %% Check whether a node is up or down %% side effect: set up a connection to

Re: [PR] Improve dist diagnostics [couchdb]

2024-03-23 Thread via GitHub
jaydoane commented on code in PR #5013: URL: https://github.com/apache/couchdb/pull/5013#discussion_r1536682236 ## src/mem3/src/mem3.erl: ## @@ -423,31 +424,127 @@ engine(Opts) when is_list(Opts) -> %% Check whether a node is up or down %% side effect: set up a connection to

[PR] Improve dist diagnostics [couchdb]

2024-03-23 Thread via GitHub
nickva opened a new pull request, #5013: URL: https://github.com/apache/couchdb/pull/5013 * Monitor nodes membership in mem3_distribution and log unexpected `nodedown` reasons. * Enhance mem3_distribution gen_sever to keep track of the last few events for each node. This can help

Re: [PR] Bump webpack-dev-middleware from 5.3.3 to 5.3.4 [couchdb-fauxton]

2024-03-23 Thread via GitHub
Antonio-Maranhao merged PR #1430: URL: https://github.com/apache/couchdb-fauxton/pull/1430 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Bump webpack-dev-middleware from 5.3.3 to 5.3.4 [couchdb-fauxton]

2024-03-23 Thread via GitHub
dependabot[bot] opened a new pull request, #1430: URL: https://github.com/apache/couchdb-fauxton/pull/1430 Bumps [webpack-dev-middleware](https://github.com/webpack/webpack-dev-middleware) from 5.3.3 to 5.3.4. Release notes Sourced from

Re: [I] Installing from yum repo fails with HTTP 403 error [couchdb]

2024-03-22 Thread via GitHub
big-r81 commented on issue #3966: URL: https://github.com/apache/couchdb/issues/3966#issuecomment-2015437522 Thank you for the report. We are aware of the problem. The ASF Infra team is already working on it, unfortunately there is nothing we can do from our side. -- This is an automated

Re: [I] Installing from yum repo fails with HTTP 403 error [couchdb]

2024-03-22 Thread via GitHub
zamb3zi commented on issue #3966: URL: https://github.com/apache/couchdb/issues/3966#issuecomment-2015435417 Note: this exactly 2 years to the day to the original issue. Certificate expiry? -- This is an automated message from the Apache Git Service. To respond to the message, please log

Re: [I] Installing from yum repo fails with HTTP 403 error [couchdb]

2024-03-22 Thread via GitHub
zamb3zi commented on issue #3966: URL: https://github.com/apache/couchdb/issues/3966#issuecomment-2015429130 A similar issue has started happening today: ```apt update Get:1 http://security.debian.org/debian-security buster/updates InRelease [34.8 kB] Hit:2

Re: [I] "apache.jfrog.io" no more available. Where are the .deb packages now? [couchdb]

2024-03-22 Thread via GitHub
big-r81 commented on issue #4489: URL: https://github.com/apache/couchdb/issues/4489#issuecomment-2015379747 I would say, it's only temporary. I add a comment to the existing INFRA ticket. -- This is an automated message from the Apache Git Service. To respond to the message, please log

Re: [I] "apache.jfrog.io" trial expired [couchdb]

2024-03-22 Thread via GitHub
nickva commented on issue #5010: URL: https://github.com/apache/couchdb/issues/5010#issuecomment-2015373107 Thanks for your report. ASF infra is aware and are trying to restore the service. -- This is an automated message from the Apache Git Service. To respond to the message, please log

Re: [I] "apache.jfrog.io" no more available. Where are the .deb packages now? [couchdb]

2024-03-22 Thread via GitHub
cgerardin closed issue #5011: "apache.jfrog.io" no more available. Where are the .deb packages now? URL: https://github.com/apache/couchdb/issues/5011 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go

Re: [I] "apache.jfrog.io" no more available. Where are the .deb packages now? [couchdb]

2024-03-22 Thread via GitHub
cgerardin commented on issue #5011: URL: https://github.com/apache/couchdb/issues/5011#issuecomment-2015359803 Duplicate of #5010 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

Re: [I] "apache.jfrog.io" no more available. Where are the .deb packages now? [couchdb]

2024-03-22 Thread via GitHub
cgerardin commented on issue #5011: URL: https://github.com/apache/couchdb/issues/5011#issuecomment-2015356629 ![image](https://github.com/apache/couchdb/assets/76680083/b40dcbc6-1120-4fe7-bfb8-1bd305375d52) -- This is an automated message from the Apache Git Service. To respond to

[I] "apache.jfrog.io" no more available. Where are the .deb packages now? [couchdb]

2024-03-22 Thread via GitHub
cgerardin opened a new issue, #5011: URL: https://github.com/apache/couchdb/issues/5011 Hello there! ## Description Same as #4489, the Debian repository hosted on https://apache.jfrog.io/artifactory/couchdb-deb/ is not available anymore. ## Steps to Reproduce

[I] "apache.jfrog.io" trial expired [couchdb]

2024-03-22 Thread via GitHub
jmta opened a new issue, #5010: URL: https://github.com/apache/couchdb/issues/5010 The apache jfrog instance is down meaning it is not possible to download artifacts from the server ## Description As above ## Steps to Reproduce Open

Re: [I] "apache.jfrog.io" no more available. Where are the .deb packages now? [couchdb]

2024-03-22 Thread via GitHub
jmta commented on issue #4489: URL: https://github.com/apache/couchdb/issues/4489#issuecomment-2015336119 Hi, This issue appears to have returned, can I expect this JFrog instance to be back up soon? -- This is an automated message from the Apache Git Service. To respond to the

Re: [I] Response of /_up is Not valid Json on one Node [couchdb]

2024-03-22 Thread via GitHub
nickva commented on issue #5009: URL: https://github.com/apache/couchdb/issues/5009#issuecomment-2015274977 Thank you for your report. Yeah that looks like a bug we should fix. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[I] Response of /_up is Not valid Json on one Node [couchdb]

2024-03-22 Thread via GitHub
Sliosh opened a new issue, #5009: URL: https://github.com/apache/couchdb/issues/5009 ## Description We have a CouchDB Cluster with 3 Nodes. If we query /_up we get good responses on node 2 and 3, but on node 1 we get invalid json.

Re: [I] weatherreport not working with debian package [couchdb-pkg]

2024-03-19 Thread via GitHub
baylisscg commented on issue #123: URL: https://github.com/apache/couchdb-pkg/issues/123#issuecomment-2008564665 @sblaisot I can get it to run but then it can't connect to the node ```bash export PATH="${PATH}:/opt/couchdb/bin:/opt/couchdb/erts-12.3.2.15/bin/" cd

Re: [PR] test(`couch_replicator`): fix reporting for unexpected test responses [couchdb]

2024-03-17 Thread via GitHub
pgj commented on PR #5006: URL: https://github.com/apache/couchdb/pull/5006#issuecomment-2002601325 The goal of this PR was achieved, closing it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

Re: [PR] test(`couch_replicator`): fix reporting for unexpected test responses [couchdb]

2024-03-17 Thread via GitHub
pgj closed pull request #5006: test(`couch_replicator`): fix reporting for unexpected test responses URL: https://github.com/apache/couchdb/pull/5006 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

Re: [PR] fix(`couch_replicator`): reporting for unexpected test responses [couchdb]

2024-03-17 Thread via GitHub
pgj closed pull request #5007: fix(`couch_replicator`): reporting for unexpected test responses URL: https://github.com/apache/couchdb/pull/5007 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the

Re: [PR] fix(`couch_replicator`): reporting for unexpected test responses [couchdb]

2024-03-17 Thread via GitHub
pgj commented on PR #5007: URL: https://github.com/apache/couchdb/pull/5007#issuecomment-2002600838 Closing this in favor #5007. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

Re: [PR] fix(`couch_replicator`): reporting for unexpected test responses [couchdb]

2024-03-17 Thread via GitHub
pgj commented on PR #5007: URL: https://github.com/apache/couchdb/pull/5007#issuecomment-2002600417 Thanks @big-r81 nevertheless. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

Re: [PR] Fix case clause error in replicator _scheduler/docs response [couchdb]

2024-03-17 Thread via GitHub
nickva merged PR #5008: URL: https://github.com/apache/couchdb/pull/5008 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Fix case clause error in replicator _scheduler/docs response [couchdb]

2024-03-17 Thread via GitHub
nickva commented on code in PR #5008: URL: https://github.com/apache/couchdb/pull/5008#discussion_r1527564359 ## src/couch_replicator/test/eunit/couch_replicator_scheduler_docs_tests.erl: ## @@ -133,9 +133,6 @@ t_scheduler_docs_total_rows({_Ctx, {RepDb, Source, Target}}) ->

Re: [I] Swagger UI or Postman Collection [couchdb]

2024-03-17 Thread via GitHub
trajche commented on issue #4213: URL: https://github.com/apache/couchdb/issues/4213#issuecomment-2002421740 We wrote a script that scrapes docs and converts it to OpenAPI 3.x: https://github.com/digitalnodecom/couchdb-swagger You have the [couchdb.json

Re: [PR] Fix case clause error in replicator _scheduler/docs response [couchdb]

2024-03-17 Thread via GitHub
pgj commented on code in PR #5008: URL: https://github.com/apache/couchdb/pull/5008#discussion_r1527471183 ## src/couch_replicator/test/eunit/couch_replicator_scheduler_docs_tests.erl: ## @@ -133,9 +133,6 @@ t_scheduler_docs_total_rows({_Ctx, {RepDb, Source, Target}}) ->

Re: [PR] Fix case clause error in replicator _scheduler/docs response [couchdb]

2024-03-16 Thread via GitHub
nickva commented on code in PR #5008: URL: https://github.com/apache/couchdb/pull/5008#discussion_r1527412175 ## src/couch_replicator/test/eunit/couch_replicator_scheduler_docs_tests.erl: ## @@ -133,9 +133,6 @@ t_scheduler_docs_total_rows({_Ctx, {RepDb, Source, Target}}) ->

[PR] Bump follow-redirects from 1.15.4 to 1.15.6 [couchdb-fauxton]

2024-03-16 Thread via GitHub
dependabot[bot] opened a new pull request, #1429: URL: https://github.com/apache/couchdb-fauxton/pull/1429 Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.15.4 to 1.15.6. Commits

Re: [PR] Fix case clause error in replicator _scheduler/docs response [couchdb]

2024-03-16 Thread via GitHub
pgj commented on code in PR #5008: URL: https://github.com/apache/couchdb/pull/5008#discussion_r1527139130 ## src/couch_replicator/test/eunit/couch_replicator_scheduler_docs_tests.erl: ## @@ -133,9 +133,6 @@ t_scheduler_docs_total_rows({_Ctx, {RepDb, Source, Target}}) ->

<    1   2   3   4   5   6   7   8   9   10   >