TheSench commented on pull request #296:
URL: https://github.com/apache/solr/pull/296#issuecomment-937390843
--
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,
TheSench commented on pull request #296:
URL: https://github.com/apache/solr/pull/296#issuecomment-937823770
The next Solr would be ideal, but only so that more users can benefit. In
using a workaround already on my end.
--
This is an automated message from the Apache Git Service.
To res
TheSench commented on pull request #296:
URL: https://github.com/apache/solr/pull/296#issuecomment-937390843
Looks like the workflow is awaiting approval again after I fixed the merge
conflict.
--
This is an automated message from the Apache Git Service.
To respond to the message, please
TheSench commented on pull request #296:
URL: https://github.com/apache/solr/pull/296#issuecomment-936683714
As an alternate, you can also use this, which _should_ allow unauthenticated
access to listing configSets (and will after the bugfix):
```json
{
"authentication": {
TheSench commented on pull request #296:
URL: https://github.com/apache/solr/pull/296#issuecomment-929656179
[SOLR-15662](https://issues.apache.org/jira/browse/SOLR-15662) created.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Git
TheSench commented on pull request #296:
URL: https://github.com/apache/solr/pull/296#issuecomment-929656179
[SOLR-15662](https://issues.apache.org/jira/browse/SOLR-15662) created.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Git
TheSench commented on pull request #296:
URL: https://github.com/apache/solr/pull/296#issuecomment-929471727
This PR still needs a maintainer to approve the running of workflows.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHu
TheSench commented on pull request #296:
URL: https://github.com/apache/solr/pull/296#issuecomment-929471727
This PR still needs a maintainer to approve the running of workflows.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHu
TheSench commented on pull request #296:
URL: https://github.com/apache/solr/pull/296#issuecomment-922010030
> Also, as far as "integration" tests, in the Solr world, we just put them
all together! If it's a long running test, we label them with that attribute,
but in terms of the code lay
TheSench commented on pull request #296:
URL: https://github.com/apache/solr/pull/296#issuecomment-921930622
> Congrats on your first contribution! To make sure this does not stall, we
could consider opening a new JIRA issue for adding an integration test, and be
able to merge this one-lin
TheSench commented on pull request #296:
URL: https://github.com/apache/solr/pull/296#issuecomment-921732111
> So... Thoughts on putting in a Unit Test? I think there is going to be a
LOT of these types of issues, and that having tests would be great. I think you
might be creating a new st
11 matches
Mail list logo
