Throws error “java.util.NoSuchElementException” on page load

I try to load the page using HtmlUnit, select the city "Белая Церковь" and see the availability of the drug in pharmacies, but even at the initial stage, when loading the page, I get an error java.util.NoSuchElementException. When I set the WebClient parameter (BrowserVersion.INTERNET_EXPLORER), then I get the page, but not completely. The HtmlUnit version is 2.48.0. Here is an example of my code, what am I doing wrong?
try {
            WebClient client = new WebClient(BrowserVersion.CHROME);
            client.setHTMLParserListener(HTMLParserListener.LOG_REPORTER);
            client.getOptions().setJavaScriptEnabled(true);
            client.getOptions().setCssEnabled(true);
            client.getOptions().setUseInsecureSSL(true);
            client.getCookieManager().setCookiesEnabled(true);
            client.getOptions().setThrowExceptionOnScriptError(false);
            client.getOptions().setThrowExceptionOnFailingStatusCode(false);
            client.setAjaxController(new NicelyResynchronizingAjaxController());
            client.getOptions().setRedirectEnabled(true);
            client.getOptions().setGeolocationEnabled(true);

            HtmlPage page = client.getPage("https://www.aptekanizkihcen.ua/ru/ynformatsyya-o-tovare/7891");
           //HtmlTextInput townInput = (HtmlTextInput) page.getByXPath("//input[contains(@class, 'dropdown-location-input')]").get(0);
            client.close();
    } catch (Exception ex) {
        ex.printStackTrace();
        throw new RuntimeException(ex);
    }

Have done some tests and this code passes here
    String url = "https://www.aptekanizkihcen.ua/ru/ynformatsyya-o-tovare/7891";

    try (WebClient webClient = new WebClient(BrowserVersion.FIREFOX)) {
        webClient.getOptions().setThrowExceptionOnScriptError(false);
        HtmlPage page = webClient.getPage(url);

        webClient.waitForBackgroundJavaScript(20_000);
        System.out.println("***********************************");
        System.out.println("***********************************");
        System.out.println(page.asXml());
        System.out.println("***********************************");
        System.out.println("***********************************");
        HtmlTextInput townInput = (HtmlTextInput) page.getByXPath("//input[contains(@class, 'dropdown-location-input')]").get(0);
        System.out.println(townInput.asXml());
        System.out.println("***********************************");
        System.out.println("***********************************");
    }

This page is really complicated including tons of javascript. I made a bugfix to make it work here - but maybe there are other problems.
Please check at twitter - i will inform if a new snapshot build is available with including the fix.

There is a new snapshot available - please try

Thanks for the answer. I checked and the page loads without problems. I have not yet been able to insert my value into the input and get a drop-down list to select the desired option, but this is probably not a library error.
I also tried to do it through Selenium WebDriver, everything was done there.

Thanks for your feedback. Feel free to ask more or open issues if you have other problems with HtmlUnit.


[cli] Log options in the configuration file

Multiple cli commands accepts a configuration file paramter (--config).
If someone is using it, from the logs we will not see the full command
what was executed, so it will be hard to start debugging the problem.
For this reason with this patch we will print out the extra options
from this configuration.

The feature is working, however, an error has been introduced. The tests are demonstrating this error and it is also reproducible locally:
[Errno 2] No such file or directory: 'config/logger.conf'
Failed to load logger configuration. Using built-in config.

@bruntib Fixed.


[GHSA-wqv4-9gr3-3qgh] Exposure of Sensitive Information to an Unauthorized Actor in Jenkins

Updates

References

Comments
Add some patch links related to CVE-2017-1000395.

Hi @sunSUNQ, unfortunately, we will not be accepting this contribution as the commits are duplicative of https://github.com/jenkinsci/jenkins/commit/7b1f8e96a8d97dd09e5e093fcdb010b3295acc77.


Bandwidth Metrics - measuring badnwidth overhead in beaconing process for bachelor thesis

I am working here on my bachelor thesis under supervision of the Net. Sec. Group from ETH Zürich. The goal of the thesis is to analyse the currently implemented beaconing algorithm in terms of bandwidth usage, i.e. analysing its bandwidth overhead and comparing this to possible new strategies.
My intention with this issue is to propose adding bandwidth metrics to the control-service for beaconing and path operations, and announce that I'm working on this actively to avoid duplication of work.
SCION is already using go-grpc-middleware V1 [1] to monitor certain metrics. go-grpc-prometheus [2] is the specific library enabling metric monitoring for gRPC. This library is missing the needed functionality for bandwidth monitoring, but is a good basis to start with. There was already an issue [3] and a PR [4] for integrating bandwidth monitoring to go-grpc-prometheus. The work was put on hold by their maintainers to move now everything to go-grpc-middleware V2.
The idea is to use a different fork from  go-grpc-prometheus and integrate the needed functionality to SCION similar to what was already be done in the PR.
[1] https://github.com/grpc-ecosystem/go-grpc-middleware
[2] https://github.com/grpc-ecosystem/go-grpc-prometheus
[3] https://github.com/grpc-ecosystem/go-grpc-prometheus/issues/85
[4] https://github.com/grpc-ecosystem/go-grpc-prometheus/pull/88

Hi @JST1703
Great to see that you are working in this direction.
Currently, there are no efforts underway from our sides with regards to bandwidth monitoring of the control plane and it's also not a priority right now.
Given that you want to use an experimental feature (not even merged yet) I suggest you integrate this in your own fork of the repository. We certainly don't feel comfortable integrating this in the main repository at this point in time.

I'm collaborating with @JST1703 on this. That's definitely the plan. Primary reason for this issue is to avoid duplicate work, but this seems cleared up now.

Cool thanks @cmeury! Please let us know about the your findings :)


Feature/refactor redux

WIP
Looking for feedback, I will try to add tests for actions/reducers.

Deployed to: http://staging.quran.com:32848

looking good! let me know when youre ready :)

@mmahalwy inshallah tonight, I need to change the filename to be camel-case.

Deployed to: http://staging.quran.com:32850

mashallah! this looks awesome!
Just my only thing is two things we need to figure out:

Filenaming: Some files are camel cased and others Pascal cased. Also, I thought the folder name would be descriptive enough (so redux/constants/audioplayer would not need to be redux/constant/audioPlayerTypes)
The store checks, do they belong in actions or do we still keep them in the module?

Done
I am thinking this would be a helper function, depending on how reusable it would be. The only usage I found was in the surah/connect.js, possible make the function live within that file.

Can I get the Jenkins output?

npm run build is failing during node ./node_modules/webpack/bin/webpack.js --config webpack/prod.config.js

i just tried manually and it worked - so probably a jenkins related issue

Deployed to: http://staging.quran.com:32768

okay lets merge this?


Black - trailing comma

I have noticed that we have merged the code below without problems regarding the black check in our CI:

The thing that I do not undestand is that when I am running black locally it is trying to add this trailing comma.
Is black configured in a different way in our CI? Or maybe I have some different configuration locally.

flake8 is configured to change the default max line length to 88 and to ignore the following PEP8 errors (default pattern of flake8 files on repositories):

E203: Whitespace before ':'
E266: Too many leading '#' for block comment
E501: Line too long (82 > 79 characters)
W503: Line break occurred before a binary operator

But, there's no instructions related to checking for trailing commas (no warnings are raised).
About Black, it runs with default options. I think we didn't change any option from it.
Look how Black deals with trailing commas here. It says it will remove trailing commas if the arguments fit in one single line, which is the case in this example. So, I think that's why travis won't complain about the missing commas at the end of the line. Maybe it's some different local configuration.
Actually, I have already noticed that, sometimes, some commits adds a trailing comma and others removes them.

About Black, it runs with default options. I think we didn't change any option from it.
Look how Black deals with trailing commas here. It says it will remove trailing commas if the arguments fit in one single line, which is the case in this example. So, I think that's why travis won't complain about the missing commas at the end of the line. Maybe it's some different local configuration.

But since Black removes the trailing commas, travis should have failed in this example.
This is the PR related to the example:
https://github.com/ross-rotordynamics/ross/pull/574/files
And here we have the travis build:
https://travis-ci.com/github/ross-rotordynamics/ross/jobs/347282600
Black passes without problem:

You are right.
And it's odd, because it runs fine with and without commas.

I think this is also an issue raised in Black repo. They are discussing pretty much the same thing. Look this issue.

I think you found the problem @rodrigomoliveira1 . It looks like they have introduced this in the last release:

And I am using the 19.3 release, so maybe that could be the problem.
I will update my version of black now and I think we can close this issue for now.