Hex colors for marker color

It is not possible to use hex for Marker Color value. We use Leaflet.awesome-markers plugin (https://github.com/lvoogdt/Leaflet.awesome-markers), in which the only colors allowed are: 'red', 'darkred', 'orange', 'green', 'darkgreen', 'blue', 'purple', 'darkpuple', 'cadetblue'.
When the color is not from the list above, it defaults to a red.
If you look into plugin's code, you will see a sprite (multiple images combined into one .png file) with the icons of above-mentioned colors:
https://github.com/lvoogdt/Leaflet.awesome-markers/blob/2.0/develop/dist/images/markers-plain.png

Thanks for all of the March 15th improvements.
As for leaflet.awesome-markers, I noticed that a different developer has taken over code maintenance on a different site. See this thread
https://github.com/lvoogdt/Leaflet.awesome-markers/issues/79
Here is leaflet.awesome-markers v2.0
https://github.com/sigma-geosistemas/Leaflet.awesome-markers
Would it be possible for you to switch us over this newer version? And if so, does that increase our color spectrum?

Jack,
They use the same .png files for the icons, but oddly enough have more markerColor options available: 'white', 'red','darkred', 'lightred', 'orange', 'beige', 'green', 'darkgreen', 'lightgreen', 'blue', 'darkblue', 'lightblue', 'purple', 'darkpurple', 'pink', 'cadetblue', 'white', 'gray', 'lightgray', 'black'.
Switching to this will double the number of colors in the palette, but we still won't be able to use hex or any other color code. In the ideal world the markers would be svg so that we can apply any colors to them, as opposed to raster images (although it might be possible to create some layers on top of a white marker and play with css to change their transparency, colors, etc – who knows).
A question: do we really need a wide variety of colors?

Thanks for investigating. When I looked at our current CSS code, I see that leaflet-awesome-markers v1 supports the 19 colors that appear in v2, even though the v1 documentation lists fewer colors.
https://github.com/JackDougherty/leaflet-maps-with-google-sheets-dev/blob/master/scripts/Leaflet.awesome-markers/leaflet.awesome-markers.css
So my goal is simply to make sure we're using the best available version of leaflet-awesome markers. If you have time today or Friday, please upload v2 into our dev code to see if it runs as expected. If yes, please add it there and update the README credits.

Just to chime in, I think it would be great to be able to map hex color codes to leaflet markers, in the same way that palettes are commonly mapped to points or polygons.

Also to chime in: indeed, many thanks! I also want to add my support for specific hex values to produce my map. I've made a map of LGBTQ historical sites to launch with my book but they don't carry the vibrancy of the people's stories withins. Given that maps lie so well, especially when it comes to color,  mapping in specific hex values would Leaflet maps shine.
And hallo @JackDougherty :)

Good to hear from you, Jack G (@jgieseking )
@ilyankou - would you please take another look at this issue and tell us what you recommend?

Aaaaaalrighty y'all!
I looked into the issue. This gentleman (@wesleyvandevoorde) proposed marker changes from .png to .svg back in 2016, and submitted a pull request (https://github.com/lvoogdt/Leaflet.awesome-markers/pull/74) - which was never accepted. But I tested it and it works perfectly! So I updated the main repository https://github.com/DataVizForAll/leaflet-maps-with-google-sheets to include these changes.
Once you sync your repositories with the updated main one:

You can use any colors you want that would normally be accepted by a css style: names (darkblue), hex (#aa8653), rgba with transparencies (rgba(200,0,100,0.5)) - you name it!
Instead of using bourgeois FontAwesome icons, you need to start using names of Material Icons (https://material.io/tools/icons/). The selection of icons is on par with FontAwesome (and in addition you don't have to deal with FontAwesome's new annoying licensing).
The new markers also jump on hover!

Created a plugin for Leaflet with these changes: https://github.com/ilyankou/Leaflet.IconMaterial

Awesome! Thank you!!


Lists in markdown

I'm trying to add a list to a markdown file using the style guide specified in the Jekyll docs
However the list items are rendered with dashes instead of bullet points or numbers.

This is expected behaviour (unless the list really isn't rendering as a ul).


It should discover new replicas

Hello
Describe the bug
spring-cloud-kubernetes (fabric8) version: 3.1.0
spring-cloud version: 2023.0.0
spring-boot-admin version: 3.2.1
spring-boot version: 3.2.2
I'm using spring-boot-admin with spring-cloud-kubernetes to discover running services and pods on my cluster.
It's working well when I start spring-boot-admin (it discovers all services and pods) but if I had new replicas : nothing changes even after several hours.
However if I deploy a new service (even on an another namespace) everything gets discovered.
spring:
    cloud:
        kubernetes:
            client:
                no-proxy: ${KUBERNETES_SERVICE_HOST}
            discovery:
                namespaces:
                    - xxxx
                    - yyyy
                use-endpoint-slices: true
                service-labels:
                    discovery: sba-actuator

Hello @wind57, thanks for your response.
I disabled the use-endpoint-slices feature: now it's working like expected.
I suppose it's an use-endpoint-slices bug...

Seems like the InstanceRegisteredEvent is not being fired
https://github.com/spring-cloud/spring-cloud-kubernetes/blob/523971aae9923a9ab14edae398d873ef7ef85b3b/spring-cloud-kubernetes-discovery/src/main/java/org/springframework/cloud/kubernetes/discovery/KubernetesDiscoveryClientAutoConfiguration.java#L81

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Sorting variables

At the moment the variables are sorted in the json according to the creation date: this means that if I create a variable at a later time, it is sorted at the bottom, although in the Figma variables interface I drag it and reposition it in an order different.
Is it possible to have a sorting that follows that of the Figma interface?

One thing to note though: Strictly speaking, JSON objects are unordered:

An object is an unordered set of name/value pairs.

(source: https://www.json.org/json-en.html)
In other words, there's no guarantee a JSON parser will return object keys - and thus groups and tokens in the case of DTCG files - in the same order they appear in the file.
In practice many do, so there probably still is value in adding this feature. But, as explained above, there's no 100% guarantee other tools which read the generated files will honour the ordering.

If I may bump the Issue, any chance to reflect the order from Figma variables interface instead of the creation date?
We managed to feed into various pages directly from the JSON and it completely mixes up the documentation order for tokens list.


Add the sample of using Crosswalk runtime library with Gradle and Maven

BUG=XWALK-5744

Another, is it OK to use Android logos (images) from license point of view? And there is no license info for the sample code.

+@baleboy for the licensing question

ping @baleboy @zqzhang

Seems you removed the README file from this sample. Then I have no idea how to enable this sample from end user perspective and what it wants to demo.

There are no README file when creating project in Android Studio.

Customer need build it in Android Studio or command line to generate a APK for demo.

Then I have no idea how to enable this sample from end user perspective and what it wants to demo.

Customer need build it in Android Studio or command line to generate a APK for demo.

Is it possible to create one README.md like https://github.com/crosswalk-project/crosswalk-samples/blob/master/space-dodge-game/README.md?

Since you are publishing this on Github, a Readme explaining what this source code is for and how it was created is needed (even if the files are meant for a tool and not for a human - people may still stumble in this repository in other ways).

LGTM once the README is added.

@zqzhang  PTAL.

LGTM

@rakuco please help merge this PR, thanks.


chore: bdd-spring-1577962839 to 0.0.1

chore: Promote bdd-spring-1577962839 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Callbacks not working anymore

Hi MizunagiKB!
I'm very thankful that you made a PlayFab wrapper for Godot. I'm using your unofficial SDK since 10 months with very little problems. Since a few days callbacks are not working anymore (no code changes in my project, beta test run). In file PlayFabHttpClient.gd this code:
if status_curr != STATUS_BODY:     if _current_request.o_result != null:         if _current_request.o_result.update_count > 0:             _current_request = dispatch(_current_request)
via dispatch() is responsible for calling the registered callback functions. But now the last code line isn't executed anymore and therefore no callbacks are called.
Do you have the same behavior?
Any ideas how to solve it?
Many thanks in advance,
-Telestes
Godot version 3.5
PS: Yes, I contacted PlayFab, see here https://community.playfab.com/questions/143179/any-api-changes-to-clientregisterplayfabuser-and-l.html

Hello, @Telestes
Upon investigating the issue, I found a bug in the CRequest of the PlayFabHttpClient.gd that I created.
The problem was that when the response format data sent from Playfab was in chunk format, the data could not be read correctly. I have now modified this so that if the data is in chunk format, it will continue to read the data until it is complete.
About the cause
I do not know why Playfab changed from a normal response to a chunk format, but it is probably for the following reasons:
To handle more connections, they may have added async processing and returned the data in chunks.
Anticipating that the data size would increase, they may have decided to send the data in divided transmissions instead of all at once.
Either way, the fact that HTTP was not processed correctly is due to my code.
How to fix
I have just made a correction for this.
Please update PlayFab_GDScriptSdk and regenerate it with SDKGenerator.
https://github.com/MizunagiKB/PlayFab_GDScriptSdk
or
The direct modification is only in PlayFabHttpClient.gd, so it should work if you replace this.
https://github.com/MizunagiKB/PlayFab_GDScriptSdk/blob/main/proj/PlayFabSDK/PlayFabHttpClient.gd

Hello MizunagiKB,
thank you for updating the 'PlayFabHttpClient.gd' code, it is working fine with chunked responses.
If PlayFab goes back to unchunked responses in the future, will the new code handle this correct also like in the past?

Please take the following as a premise before reading this text.

This fix has not gone through code review or commercial product level testing.
Both Godot Engine and Playfab are constantly updating, so it is unclear whether they will work in the future.

The fixed code assumes that Godot Engine’s implementation of HTTPClient::has_response succeeds only once before getting the response.

https://github.com/godotengine/godot/blob/3.5/core/io/http_client.cpp

Therefore, this behavior is unknown in future versions of Godot Engine, so I made another fix that does not rely on this behavior.
I just committed it, so you can apply this fix by updating to the latest version.

https://github.com/MizunagiKB/PlayFab_GDScriptSdk/commit/9ad0c690fbf019cdb48b521dbdfaa5d026575071

About the question
The question you asked was “Does Playfab work even if it returns from Chunk to Body?”, which is about the behavior of HTTPClient implemented in Godot Engine.
I am not a developer of Godot Engine itself, but I can only judge from the results that are currently working, but in my 3.5.2, the actual data acquisition is done by read_response_body_chunk regardless of the response.
Please check the source code of Godot Engine to see how it actually works. Also, to verify the operation, you can create an HTTPServer that returns Body and Chunk for the same request and test both responses.
For example, you can prepare a test environment with the following code in Python.
import json

from fastapi import FastAPI
from fastapi.responses import JSONResponse, StreamingResponse

app = FastAPI()

response_count: int = 0
dictdata = {"strvalue": "0123456789ABCDEF", "intvalue": 1234}
jsontext = json.dumps(dictdata)

def gen_streaming_data():
    for v in jsontext:
        yield v

@app.post("/Client/RegisterPlayFabUser")
def Client_RegisterPlayFabUser():
    global response_count

    response_count += 1

    if response_count & 1:
        print("response body")
        return JSONResponse(dictdata)
    else:
        print("response chunked")
        return StreamingResponse(
            content=gen_streaming_data(),
            media_type="application/json",
        )

Thank you for creating this second 'PlayFabHttpClient.gd' update, it works and addresses possible future changes. In line 319 is one equal sign too much, it should be  status_curr = STATUS_DISCONNECTED
The issue can be closed.

Thank you for your bug report.
The issue has been resolved.
The bug you reported was indeed something that needed to be fixed.
Fortunately, we are always retrieving the current status at line 314.
Therefore, we were merely initializing the variable that holds the status, but it is true that we were performing an unintended operation.
If you hadn’t informed us, we might have left it as it is.
Your help was greatly appreciated.


⚠ St. Lawrence Global Observatory CKAN has degraded performance

In f5bdb2f, St. Lawrence Global Observatory CKAN (https://catalogue.ogsl.ca/en/) experienced degraded performance:

HTTP code: 200
Response time: 6558 ms

Resolved: St. Lawrence Global Observatory CKAN performance has improved in c72b5e5 after 6 minutes.


Unexpected forward strategy for MultipleHiddenInput

This is my code:
# forms.py
class MyForm(forms.ModelForm):
    multiple_field = forms.ModelMultipleChoiceField(widget=forms.MultipleHiddenInput(), queryset=whatever)

    class Meta:
        ...
        widgets = {
            'other_field': autocomplete.ModelSelect2(url='whatever-url', forward=['multiple_field', ]),
        }

# views.py
class MyAutocomplete(...):
    model = ...

    def get_queryset(self):
        qs = super().get_queryset()
        multiple_field = self.forwarded.get('multiple_field', None)
        ...

I expected to get a list of values on multiple_field variable on views.py. But it looks like in this context, getForwardStrategy returns single, so I get only the first value.
If I set the default widget for multiple_field, the behavior is correct.
I've also tried adding Field('multiple_field', multiple='') on the form, but it didn't work either.
As a workaround, I'll hide my field with CSS. But, Is it possible to get the correct behaviour with some other configuration?

Does it work when you just return "multiple" here?
https://github.com/yourlabs/django-autocomplete-light/blob/master/src/dal/static/autocomplete_light/autocomplete_light.js#L293

Does it work when you just return "multiple" here?

Yes.
And it also works if I remove element.length === 1 on this line.
Anyone knows why we need this first check ? It is not enough to check if the element has the "multiple" attribute to return "multiple"?
Which is the case when we have "multiple" and the length of the element is "one" that we want to get a single element instead of a list?


[BUG]Navigate Timeout

Describe the bug
Notice timeout function on Navigate is not working, after some debug found that in SBNavigateBlock you call default value at the end so this rewrites the set value. After commenting out this line though fixed but was not fully. It's work if commenting out but will catch timeout if you change value diff than 60 sec like
https://gyazo.com/3fc51d8c0c72d56142475b04015474e7
But if you leave it to default 60 sec and go to timeout then it won't catch the timeout exception and i can't find why https://gyazo.com/5c08e003304458015e1ce47c48055c8d
Version

Version Last Commit

Additional context
Any idea or help is welcome :)

That line is there just to set the timeout back AFTER the navigation, in case there are any other blocks that need to be processed so they can have a 60s timeout.

I though you add it for that reason but never any of DomToSource, GetCookies, Quit etc... Needed 60s i think. And about timing is my bad actually is is 60>=  then wont get into
` catch (OpenQA.Selenium.WebDriverTimeoutException)
{
data.Log(new LogEntry("Timeout on Page Load", Colors.Tomato));
            if (BanOnTimeout)
            {
                data.Status = BotStatus.BAN;
            }
        }`

https://gyazo.com/fbfdd14ce0f3fc4f020194cb118f1a10


Wrong path for toolbar.ini

Users are instructed to

However, what actually worked was ~/.config/xournalpp

This has been the source of some frustration. I am not sure if it only applies to linux (mint), but should be updated.

Just had the same problem, on arch.

Fixed in e39c469, I think this changed in Xournal++ at some point after I first made the repo.

This has been the source of some frustration. I am not sure if it only applies to linux (mint), but should be updated.

You are right, but be careful of your tone

Thank you for the patch, and the project. I meant no disrespect to the project, but wanted to be clear on this particular issue. Apologies if I caused offense!

It's ok, you didn't cause offense, and thanks for pointing out the issue.
(I just wanted to highlight that link because it was a bit close to things users sometimes comment like "It's broken. Fix it." or "This thing doesn't work and it's your fault my time was wasted." which can get frustrating and contribute to maintainer burnout.)


HBASE-25365 The log in move_servers_rsgroup is incorrect

HBASE-25365

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 14s
Docker mode activated.


Rephrase summaries requirement

From Gitter:
@fredliporace wrote:

Checking the use of summaries. The spec states "Summaries should summarize all values in every Item underneath the collection, including in any nested sub-Catalogs.". If 'all values' is to be interpreted as a requirement this increases significantly the implementation work. For CBERS case I consider that the only field that would be interesting (and easy) to include in summaries is the GSD for the CB4A/WPM camera, which has assets with 2m and 8m.

My response:

It seems we need a PR to rephrase this.
This was meant to say that for the fields you decide to add to summaries, you should list all potential values from all items underneath for that specific field.

@m-mohr I can work on this PR.

That would be great, @fredliporace ! Thanks.


Strange VPackBuilder behaviour

I got following code

VPackBuilder builder;
builder.add("key1", "value1");
builder.add("key2", "value2");
builder.close();

auto slice = builder.slice();
builder = VPackCollection::remove(slice, std::vector<std::string>{"key2"});

VPackBuilder newBuilder(builder.slice());
newBuilder.openObject();

newBuilder.add("key2", "value_new2");
newBuilder.add("key3", "value3");

std::cerr << "hasKey('key1') = " << newBuilder.hasKey("key1") << std::endl; // true
std::cerr << "hasKey('key2') = " << newBuilder.hasKey("key2") << std::endl; // true
std::cerr << "hasKey('key3') = " << newBuilder.hasKey("key3") << std::endl; // true
std::cerr << "hasKey('key4') = " << newBuilder.hasKey("key4") << std::endl; // false

newBuilder.close();

std::cerr << newBuilder.toJson() << std::endl; // {"key1": "value1"}

Expected behaviour: my json contains key1, key2 and key3 (and corresponding values).
Or at least I should get an error on attempt to add key2 and key3.
As result I solved my issue using newBuilder.add(VPackObjectIterator(builder.slice()));. But it wasn't obvious and took too much time.
Also seems such approach produces excessive copies that I want to avoid.

I see the following problems here:
VPackBuilder builder;
builder.add("key1", "value1");
builder.add("key2", "value2");
builder.close();

I guess the intention here is to produce an object with 2 keys, key1 and key2.
The code for this should be
VPackBuilder builder;
builder.openObject();
builder.add("key1", VPackValue("value1"));
builder.add("key2", VPackValue("value2"));
builder.close();

Otherwise you will get an need open compound value (Array or Object) error already on the first add(...) call.

This also looks problematic:
VPackBuilder newBuilder(builder.slice());
newBuilder.openObject();

because it will first assign an already created and closed (i.e. sealed) object to newBuilder, and then opening it again.
This may be a misconception, but the openObject() will add re-open an existing object contained in the Builder.
A Builder is designed to be used in an append-only fashion. So when calling openObject() here, it will start a new object behind the object that's already contained in the Builder.
If you want to start from scratch in an existing Builder object, you can always use builder.clear() to wipe all data from it.
Maybe can you elaborate a bit on the problem you are trying to solve, because I don't fully understand what the goal of the example code above is. Thanks!

What about
  std::string json = "{\"foo\":\"bar\",\"baz\":\"bark\",\"qux\":\"quz\"}";
  auto builder = VPackParser::fromJson(json);

  VPackBuilder replacements;
  replacements.openObject();
  replacements.add("baz", VPackValue("replaced"));
  replacements.close();

  auto result = VPackCollection::merge(builder->slice(), replacements.slice(), false, false);
  std::cout << result.toJson() << std::endl;

An alternative would be to only build the result object once, like this:
  std::string json = "{\"foo\":\"bar\",\"baz\":\"bark\",\"qux\":\"quz\"}";
  auto builder = VPackParser::fromJson(json);

  VPackBuilder result;
  result.openObject();
  for (auto it : VPackObjectIterator(builder->slice())) {
    if (it.key.stringView() == "baz") {
      result.add(it.key.stringView(), VPackValue("replaced"));
    } else {
      result.add(it.key.stringView(), it.value);
    }
  }
  result.close();
  std::cout << result.toJson() << std::endl;

Yes. Seems it solves my issue. I wanted to avoid copies and tried to modify the source object. But seems it's not an option.
Thanks!


feat(docs-site): mainnet docs

We need to add the following explorer for mainnet:

taikoscan.io (Block explorer by Etherscan)
taikoscan.network (Block explorer by Router scan)
taiko.socialscan.io  (Block explorer by SocialScan)

A couple of days later:

taiko.socialscan.io renamed to taikoscan.net
taiko.wtf (BCR explorer from zkPool)

We need to add the following explorer for mainnet:

taikoscan.io (Block explorer by Etherscan)
taikoscan.network (Block explorer by Router scan)
taiko.socialscan.io  (Block explorer by SocialScan)

A couple of days later:

taiko.socialscan.io renamed to taikoscan.net
taikonow.xyz (BCR explorer from zkPool)

I added them to rpc-configurations, if we want to add it to the main website maybe @bennettyong can help?


SSL connection fails on DNS round robin and ssl_context.check_hostname = True

We use a DNS round robin to connect to a Vertica cluster. Connecting with SSL and ssl_context.check_hostname = True doesn't work, because ssl_options.wrap_socket(raw_socket, server_hostname=host) in enable_ssl gets an IP address passed as server_hostname parameter, and that won't work with certificate hostname check.
Proposed patch:
patch.txt
peter

@petervanhooft Thanks for reporting this bug! The test suite lacks of SSL testing, so it is hard to verify it works.
Here are some of my advise to your patch:
--- vertica/connection.py-org	2019-02-05 14:20:49.345768826 +0100
+++ vertica/connection.py	2019-02-05 14:14:39.833451310 +0100
@@ -308,7 +308,7 @@
         ssl_options = self.options.get('ssl')
         self._logger.debug('SSL option is {0}'.format('enabled' if ssl_options else 'disabled'))
         if ssl_options:
-            raw_socket = self.enable_ssl(raw_socket, ssl_options)
+            raw_socket = self.enable_ssl(raw_socket, ssl_options, self.options['host'])
+ # "self.options['host']" would only work in specific situations.
+ # Since we introduced connection load balancing and failover (i.e. 'backup_server_node' option in
+ # vertica_python.connect()), which happens right before enabling SSL, so the server hostname may
+ # not be self.options['host'], but a hostname in self.options['backup_server_node']. You may need
+ # to save the actual connected hostname to a variable.
+ # I'm not super familiar with SSL, but is it reasonable to get the hostname from IP address with
+ # `socket.gethostbyaddr(host_ip)`?

         self.socket = raw_socket
         return self.socket
@@ -354,7 +354,7 @@

         return raw_socket

-    def enable_ssl(self, raw_socket, ssl_options):
+    def enable_ssl(self, raw_socket, ssl_options, server_hostname):
         from ssl import CertificateError, SSLError
         # Send SSL request and read server response
         raw_socket.sendall(messages.SslRequest().get_message())
@@ -364,7 +364,7 @@
             try:
                 if isinstance(ssl_options, ssl.SSLContext):
-                    host, port = raw_socket.getpeername()  <= This line would be useless if you pass a server_hostname value
-                    raw_socket = ssl_options.wrap_socket(raw_socket, server_hostname=host)
+                    raw_socket = ssl_options.wrap_socket(raw_socket, server_hostname=server_hostname)
                 else:
                     raw_socket = ssl.wrap_socket(raw_socket)
             except CertificateError as e:

It'd be great if you can share your settings and an example program for reproducing this bug.
You can create a pull request once you test your bugfix manually (Testing with different python versions would be better!). Please see CONTRIBUTING.md for how to create a pull request. We can postpone adding SSL connection tests to the test suite now. Thank you again!

Hi, I'm told by legal that I can't sign the CLA, but I can submit the patch directly.

is it reasonable to get the hostname from IP address withsocket.gethostbyaddr(host_ip)?
No, because you can have only one certificate per Vertica cluster, so the hostname won't match the certificate. I didn't test the case yet where you have your vertica cluster in a subdomain and have a wildcard certificate.

The patch I attached works with load balancing on/off, ssl on/off and ssl_context.check_hostname on/off and passes all tox tests.
vertica-ssl-patch.txt
peter

@petervanhooft Ok, I'm sorry that you cannot sign the CLA. We are glad to listen if you would like to tell us the reason, so that we can see if there is a workaround. If you don't sign the CLA, you are unable to merge your work to the repo. Do you authorize me to create a new PR with your patch and merge to master branch?

Hi, this is what I received:
I reviewed the CLA and I do not like the way it is signed only once. Once signed, it does not only cover your current patch but any future submission - I assume that any future submission bypasses the CLA (until the CLA is changed) and that such gating is done on a per-company and not on a per-user basis - in that case we have no control over what we are submitting in the future.
You are authorized to create a new PR with this patch and merge to master branch.
peter

@petervanhooft The lawyer from our side is still thinking about the CLA issue; in the meantime we need more test framework work to support SSL anyway, so we will likely want to implement your change ourselves as part of a broader effort to better support SSL. I'll keep this issue open until we decide what we will do. Thanks!

@sitingren is there any update on this issue, the company I work at currently faces the same issue. We have load balancing and having the check_hostname flag set to True causes failure. It sounds like you want to add more SSL tests, perhaps you can elaborate what you are looking for and I can try to get a PR together.

Thanks @dmitrypolo, you are welcome to create a new PR.
Adding SSL tests requires server configuration and client cert setup, which means we need to modify the test framework (.travis.yml and maybe other files). Currently I don't have a good idea about how hard it is.
If you don't add SSL tests with your PR, I recommend testing your bugfix manually with all combinations like #258. As of today, our target python versions are 2.7, 3.5, 3.6, 3.7.


Unable to 'download JSON Metadata for Pluto TV stream,' HTTP Error 404: Not Found (caused by <HTTPError 404: 'Not Found'>)

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2022.11.11 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
Hi everyone. Excuse my mistakes in the way I'm reporting this. I am a noob trying to make sense of this. I'm trying to download a move off Pluto TV (URL: https://pluto.tv/en/on-demand/movies/philadelphia-1993-1-1) but keep on getting the following error:
`` C:\video downloader>yt-dlp https://pluto.tv/en/on-demand/movies/philadelphia-1993-1-1
[PlutoTV] philadelphia-1993-1-1: Downloading JSON metadata
ERROR: [PlutoTV] Unable to download JSON metadata: HTTP Error 404: Not Found (caused by <HTTPError 404: 'Not Found'>); please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
C:\video downloader>yt-dlp -U
Latest version: 2022.11.11, Current version: 2022.11.11
yt-dlp is up to date (2022.11.11)
C:\video downloader> ``
Other URLs from the same website work just about fine, a few ones I've had success with:
https://pluto.tv/en/on-demand/movies/saving-private-ryan-paramount-pictures-lf-1998-1-1
https://pluto.tv/en/on-demand/movies/forrest-gump-1994-1-1
I dug through the forums and similar issues here, but couldn't figure exactly what should be done, so will greatly appreciate any feedback, and instructions-as simple as possible, PLEASE. It's a really favorite movie of mine, and may soon go away, so I want to grab it before it's gone.
Thanks everyone, in advance!
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', 'https://pluto.tv/en/on-demand/movies/philadelphia-1993-1-1']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.11.11 [8b64402] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg 2022-11-03-git-5ccd4d3060-full_build-www.gyan.dev (setts), ffprobe 2022-11-03-git-5ccd4d3060-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.15.0, brotli-1.0.9, certifi-2022.09.24, mutagen-1.46.0, sqlite3-2.6.0, websockets-10.4
[debug] Proxy map: {}
[debug] Loaded 1723 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2022.11.11, Current version: 2022.11.11
yt-dlp is up to date (2022.11.11)
[debug] [PlutoTV] Extracting URL: https://pluto.tv/en/on-demand/movies/philadelphia-1993-1-1
[PlutoTV] philadelphia-1993-1-1: Downloading JSON metadata
ERROR: [PlutoTV] Unable to download JSON metadata: HTTP Error 404: Not Found (caused by <HTTPError 404: 'Not Found'>); please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
  File "yt_dlp\extractor\common.py", line 674, in extract
  File "yt_dlp\extractor\plutotv.py", line 160, in _real_extract
  File "yt_dlp\extractor\common.py", line 1034, in download_content
  File "yt_dlp\extractor\common.py", line 998, in download_handle
  File "yt_dlp\extractor\common.py", line 868, in _download_webpage_handle
  File "yt_dlp\extractor\common.py", line 825, in _request_webpage

  File "yt_dlp\extractor\common.py", line 807, in _request_webpage
  File "yt_dlp\YoutubeDL.py", line 3692, in urlopen
  File "urllib\request.py", line 531, in open
  File "urllib\request.py", line 640, in http_response
  File "urllib\request.py", line 569, in error
  File "urllib\request.py", line 502, in _call_chain
  File "urllib\request.py", line 649, in http_error_default
urllib.error.HTTPError: HTTP Error 404: Not Found

I dug through the forums and similar issues here, but couldn't figure exactly what should be done

This is indeed the same problem as #4625, which currently has no known solution or workaround AFAIK. If one is found, that issue will be updated. Closing this issue as a duplicate


Preparation for next release series (0.5.x)

We will remove a lot of deprecated items, and rename some.
This is on the road towards an eventual 1.0 version of the library.
Notes

Numerical things will move because we don't want num-traits in itertools. linspace will move to a crate that uses num-traits
Use free functions to construct iterators that are sources. For example Unfold::new(x, y) → unfold(x, y). Follows libstd convention (std::iter::once).
Unstable/nightly parts will need to live in another crate
Rename and move stuff around to increase consistency. This is the best for the long run.
See the commits for an overview

See also #87
Fixes #86

In general: Unstable stuff should go in another crate, not here.
Turn on --feature=unstable in itertools 0.4 to see deprecation warnings.

Research shows StrideMut does have provable users in the wild, so deprecation will be reconsidered.

LGTM so far.
However, personally I'd:

Either move  (now) or re-export (some day) the free functions in the root so one can call, e.g.,  itertools::zip(a, b) directly. It would also kind of be nice to get rid of that long list of adapter structs in the root of the documentation but I don't know of a good way to do this.
Provide a prelude module (export Itertools and the free functions)? This can obviously be done later.
Move (now) some of the helper traits out of itertools::misc into separate crates. I'd be happy to donate tool's Cons trait if you want to maintain a crate for dealing with fixed-sized lists of things (splitting, joining, etc.) :wink:. To me, the name misc indicates that it doesn't really belong.

All the structs could go into a new module like itertools::types::. The hard decision is whether to leave them reexported in the main module (deprecated one version) or not.

Oh god, there is so much to do.
Any renaming scheme for these?

group_by: groups as vectors
group_by_lazy: groups as iterators,
chunks_lazy: chunks as iterators

If group_by was removed and the others lost the lazy part of the name, it would be consistent but one less useful adaptor.
And these:

combinations_n: combinations as vectors
combinations: combinations as pairs

→ Some kind of neat scheme that can be expanded for using 3-tuples too. And is consistent if we add equivalent "windows" variants.

@Stebalien The first order goal is to not have any dependencies in itertools

The first order goal is to not have any dependencies in itertools.

That's a bit unfortunate but understandable (although I don't think a few small no_std dependencies are really a problem).

Any renaming scheme for these?

Is the non-lazy GroupBy adapter really that useful? Can't one just write: iter.group_by_lazy(...).map(|(k, v)| (k, v.collect())? Is there some performance penalty? Also, given some useful functions (that may not really be useful enough to include):

A free-floating collect function.
Itertools::map_first and Itertools::map_second .

One could write iter.group_by(...).map_second(collect) (renamed group_by_lazy).

I think there's probably a performance penalty on the pretty large state machine thing in the group_by_lazy iterator. It's also got the distinction of being an IntoIterator adaptor confusingly enough, i.e. it doesn't return an iterator directly.
Ok. so that's what I think. Then I tried the benchmark. Take the benchmark that exist for group_by_lazy and try them with group_by.
The lazy iterators get the benefit of not making vectors here:
test group_by_1                               ... bench:      26,125 ns/iter (+/- 1,301)
test group_by_2                               ... bench:      41,493 ns/iter (+/- 1,653)
test group_by_lazy_1                          ... bench:       5,762 ns/iter (+/- 329)
test group_by_lazy_2                          ... bench:       8,282 ns/iter (+/- 197)

If we change so that we make vectors in the lazy benches too:
test group_by_1                               ... bench:      26,134 ns/iter (+/- 2,836)
test group_by_2                               ... bench:      40,151 ns/iter (+/- 1,547)
test group_by_lazy_1                          ... bench:      33,682 ns/iter (+/- 1,089)
test group_by_lazy_2                          ... bench:      52,549 ns/iter (+/- 2,432)

Now the misc module is dead. The various helper traits can be replaced with just massive multidispatch impls of existing traits like Iterator and From.

Hmm... this feels like something that could be fixed by specialization but I don't know the right abstraction.

multizip is a great addition. Can a multichain be added? Should multizip and multichain be in free module?
How about merging multizip and zip (multichain and chain)? So one always use the same name without worrying about the number of arguments: zip((a, b)) or zip((a, b, c)).

We discussed multichain in  #142 and I put my thoughts there.
I'm happy to have feedback and discussion about this. I think it would be a step back to require zip to take a tuple. .zip() specialization in libstd also has me thinking, either we need to reuse that in multizip somehow, or we need to replicate it. As it is in current nightly, a.zip(b).zip(c) can lead to very efficient autovectorized code if a, b, c are slices and the moon shines the right way on the optimizer and multizip((a, b, c)) can't do this.

Also note, multizip is not an addition but a new name for what was already there as izip!() and Zip::new.

Regarding free, I'd like to move everything in there to the top level, that seems great to me.

Thanks for the clarification.
Some other things.
How about adding collect_ for all collection types in std?

collect_vec() // already exist
collect_vec_deque()
collect_linked_list()
collect_string()
collect_binary_heap()
collect_hash_set()
collect_hash_map() for Item = (_, _)
collect_btree_set()
collect_btree_map() for Item = (_, _)

In my private code I have used collect_hash_set a lot in tests.
How about a way to collect to tuples?
// the problem here is that the produced items are lost if there are not enough items
let (a, b) = iter.next_tuple().unwrap(); // returns Option<(_, _)>
let (a, b, c) = iter.next_tuple().unwrap();

// or panic if there are not enough items
let (a, b) = iter.collect_tuple();
let (a, b, c) = iter.collect_tuple();

// and
for (a, b) in iter.tuples() { // this is similar to [T]::chuncks
}

What I want to do now is to add collect as a free function, and not collect_vec but just vec. Free functions like vec(Intoiterator) -> Vec<T> and hashset(IntoIterator) -> HashSet<T> are very useful.
The static size 2 chunks is definitely interesting, how to handle uneven sizes though?
Also .next_tuple() is an interesting idea.

Then again the 0.5 release bump is mostly focused on renaming and removing things! We can add new features whenever we want, but only break with a bump.

@Stebalien Warning, you might not want to learn this. When I need a free function from a trait method I sometimes use this syntax: <_>::collect. Only works for trait methods.

@bluss that's genius!

The collect (and vec, etc) as a free function idea is great.
tuples could return a iterator backed by MultiPeak, so the last items are not consumed from the iterator. Note that I think tuples could be used for any tuple size (max 8?):
for (a, b, c) in iter.tuples() {}
for (a, b, c, d) in iter.tuples() {}

Please, keep the focus on 0.5 release. Maybe a new issue should be open so we can talk about collecting to tuples.

I was wondering if this code using <_>::fmt was fugly or genious. https://github.com/bluss/rust-ndarray/blob/master/src/arrayformat.rs#L133-L151  Each one picks up the fmt method that is "primed" by the trait bound.  (I recently learned that the compiler works by kind of lifting the methods from an explicit trait bound into a priority class similar to that of inherent methods. That means that it will pick the particular method that corresponds to a trait bound, even if others would be applicable.)

Ok -- this will merge and be a prerelease itertools 0.5.0-alpha.0. Feedback, breaking changes, takebacks are welcome until the final 0.5.0

docs: https://docs.rs/itertools/0.5.0-alpha.0/itertools/


make elasticsearch index an environment variable for flask API

make index static for crawlers

@ivantha please check now!


Fix #24

Forward customPresentViewController completion to fix #24

Fixed by #21 pull request!
Will try to add to release today. Thanks for the input anyways :)

https://github.com/IcaliaLabs/Presentr/releases/tag/0.1.8


Root Certificatates release date frequency?

Dear JohnTHaller,
As I can see, prior to the last update was a year ago in 2022-July. Is this mean the future update can be expected in another year's time, in mid 2024?
Thank you for your answer, best regards,
Pocok

I'm going to update it quarterly. The certs don't update that often, but I think it will help people feel better about it.

Appreciate your quick reply!


Issue with /docs/getting-started-guides/logging/

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
In kubernetes.github.io/docs/getting-started-guides/logging.md, around line 132 we have:
You can also follow this link to the [settings tab](https://pantheon.corp.google.com/project/_/logs/settings).
This pantheon link seems to be an internal google-only link which shouldn't be there.
Proposed Solution:
Change the link. I don't know what the correct-one is.
Page to Update:
kubernetes.github.io/docs/getting-started-guides/logging.md
File on github: https://github.com/kubernetes/kubernetes.github.io/blame/master/docs/getting-started-guides/logging.md

Logging got a rewrite and now lives here: https://kubernetes.io/docs/user-guide/logging/overview/
If there's still issues, please feel free to open an new issue.


  An example project would demonstrate very quickly what is possible and what is not.

Hem, old issue but TemplateDoesNotExist happened to me too right now. In my case I forgot to add datatableview to INSTALLED_APPS. hth


Proper slicing in kernels

gpflow/kernels/base.py says # TODO(@awav): Convert when TF2.0 will support proper slicing.. We should link this to an open TensorFlow issue so that we can keep track of it.

Addressed by #1347


Alt-C not working on OSX

Using OSX Yosemite in bash with vim mode, Alt-C just prints out ç.
CTRL-T & CTRL-R work perfectly.
Thanks for a great tool and really awaiting the neovim support!

If you use iterm2, try this (excerpt from https://iterm2.com/faq.html)
Q: How do I make the option/alt key act like Meta or send escape codes?

A: Go to Preferences->Profiles tab. Select your profile on the left, and then open the Keyboard tab. At the bottom is a set of buttons that lets you select the behavior of the Option key. For most users, Esc+ will be the best choice.

It's important to note that if you have a GB keyboard; this will stop you being able to use the # character with alt+3 in iTerm. If you want to do this, you'll need to change your keyboard to Australian, which is exactly the same except £ and # are swapped.

Works great, thanks!
Maybe add this info to the readme?

Note that you don't necessarily need to change the behavior of the Alt key if you use it to type special characters. You may just use Esc+C instead of Alt-C to do fzf's fuzzy directory change.

If you are using a normal Mac OSX terminal (not iTerm2), here are two solutions:
Solution 1:
You can open your terminal, and in the menu at the top of the screen, open "Preferences", click the "Profiles" tab then go to "Keyboard" section and then check the checkbox that is called "Use Option as Meta key". The downside of this is that you can't type characters like øœåΩ®ü etc easily at the terminal.
So instead:
Solution 2:
You can send the "Meta" by typing pressing "Control-[", so then the solution to get fzf's awsome magical find-the-directory-and-cd-into-it feature is to simply press:
"Control-[ c". Similar to varepsilon's solution of hitting "Esc c".
Thanks!

If you use ZSH, add this line to .zshrc:
bindkey "ç" fzf-cd-widget

I use Fish with Vim keybindings and I used the Fish version of what @TheJavaGuy suggested
bind -M insert "ç" fzf-cd-widget

I needed to manually set alt-down and alt-up in iTerm:

The default was ^[[1;9A instead of ^[[1;3A.

Even adding ALT-C wasn't as pleasing to me as including the following at the bottom my ~/.fzf.zsh file. You do need to adjust the query if you don't have fd installed.

if type fd &> /dev/null; then
    cdc () {
        cd "$( fd -td | fzf )"
    }
    cdh () {
        cd "$( fd -td . $HOME | fzf )"
    }
fi

Just type cdc<ENTER> in the command prompt to change into a subdirectory. Use cdh<ENTER>  to search for a directory under the entire home directory. Create new definitions as needed. You won't have to delete the leftovers from using cd and ALT-C upon completion. Plus it was much faster for whatever reason. You could change it based on any other command equivalent instead of fd.

I use Fish(v3.3.1) and this helped for me
bind "ç" fzf-cd-widget

Getting something strange when doing this:
unknown option: -t

Anyone using iterm can also just rebind it to the expected behavior like so

For hyper the hyper terminal, you need to add the following to the config:
        modifierKeys: {
            altIsMeta: true,
        },

Without this setting, you will get the cedille ç instead of meta-c or alt-c
See https://apple.stackexchange.com/questions/445913/how-to-pass-option-c-to-hyper-terminal-rather-than-ç

Bash users: the given share/fzf/key-bindings.bash has:
# ALT-C - cd into the selected directory
bind -m emacs-standard '"\ec": " \C-b\C-k \C-u`__fzf_cd__`\e\C-e\er\C-m\C-y\C-h\e \C-y\ey\C-x\C-x\C-d"'
bind -m vi-command '"\ec": "\C-z\ec\C-z"'
bind -m vi-insert '"\ec": "\C-z\ec\C-z"'

So this can be additionally bound in the ~/.bashrc or similar to the cedille character as:
# ALT-C - cd into the selected directory
bind -m emacs-standard '"ç": " \C-b\C-k \C-u`__fzf_cd__`\e\C-e\er\C-m\C-y\C-h\e \C-y\ey\C-x\C-x\C-d"'
bind -m vi-command '"ç": "\C-z\ec\C-z"'
bind -m vi-insert '"ç": "\C-z\ec\C-z"'

Ok, so you need to do the opt-c or alt-c not after cd ** like as for tab. Actually in a empty prompt do opt-c and you will go into __fzf_cd__-ing. The tutorial video linked in the README.md was unclear about this at 04:18.
For Alacritty lovers, add this to ~/.config/alacritty/alacritty.yml:
key_bindings:
  - { key: F,  mods: Alt,           chars: "\x1bf"                       }
  - { key: B,  mods: Alt,           chars: "\x1bb"                       }
```.

**Mind the two spaces**.

Also, to find more of these useful bindings for alacritty, check out my [alacritty yml](https://github.com/vishalpaudel/dotfiles/blob/main/terminal/.config/alacritty/alacritty.yml)

None of the above working for me on zsh for some reason (just inserting a blank line) the widget solution from @TheJavaGuy didn't work for me either 🤦
So instead I use this:
bindkey -s 'ç' "fd --type d . --hidden | fzf --preview 'tree -C {} | head -50'^M"

Not very clean but it works. Probably something I'm missing, or there is a conflict somewhere, just leaving this here incase someone else has similar issues.

the earlier solution for alacritty did not work for me but this does in my alacritty.toml:
[keyboard]
bindings = [{ key = "C", mods = "Alt", chars = "\u001bc" }]

Likewise here is the updated Alacritty config from @vishalpaudel's suggestion:

For Alacritty lovers, add this to ~/.config/alacritty/alacritty.yml:
key_bindings:
  - { key: F,  mods: Alt,           chars: "\x1bf"                       }
  - { key: B,  mods: Alt,           chars: "\x1bb"                       }

key_bindings:
  - { key: F,  mods: Alt,           chars: "\u01bf"                       }
  - { key: B,  mods: Alt,           chars: "\u01bb"                       }

@davidfitzgerald-p Just had the same issue and I managed to get it working by changing iTerm2 preferences. The other suggestions didn't seem to work, only the key rebind seems to work. You just need to ensure it is a global keybind (not profile specific) and apply it to all sessions!


Android api documentation

This new Android implementation is clean and looks nice. It's also aligned with the mobile team to match the iOS one.
I would be okay @igr in give freedom for them. Unfortunately for the artifact name we need to follow Brian's recommend way.
Do you think make sense deprecated our Java one and use the android from our Java application?
Or should we keep Java separate from Android? If so, we need to do a major refactoring on this old Java one to be similar to Android.
In any case, the mobile team is doing a good job rethinking the api clients and eventually we will apply some of their findings on the JavaScript one too.
Let me know what you think.

@eduardolundgren I think it is a good idea to reuse it for Java and Android (like you do for web and node, right?). That's why I took the care of keeping the Android API compatible with Java. At the moment, it has only 2 methods that are not Java compatible (the ones related to provider auth).
But I have some concerns about this approach:

This is a client side api. The current Java api has code that seems to be used on server side only, which increases its complexity. We must keep the client simple.
We can evolve the api to do more complex stuff at some point, like offline syncing data. If we reach that, it is only going to work for Android, but we could try to do this pluggable in order to work with Java as well.

@sgosantos awesome, it's cleaner to separate the server side part from the client indeed.
From this discussion I would suggest to keep Android/Java client using the new code. That's the one we document publicly.
The old api-java can be cleaned and renamed to fulfill the server needs eventually as an internal engineering effort.
@igr wdyt?

I agree on @sgosantos, having reusable java and android is nice, but I am sure it can soon diverge in different ways, as usage patterns may be different. Not to mention differences between java7 and java8

I've updated the PR with the change of the dependency name and with the RxJava usage.

Merged (with some changes)! 🎉


HBASE-23149 hbase shouldPerformMajorCompaction logic is not correct

it is not correct in release version hbase1.4.9.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
15m 12s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:yellow_heart:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-1.4 Compile Tests _

:green_heart:
mvninstall
8m 22s
branch-1.4 passed

:green_heart:
compile
0m 40s
branch-1.4 passed with JDK v1.8.0_232

:green_heart:
compile
0m 43s
branch-1.4 passed with JDK v1.7.0_242

:green_heart:
checkstyle
1m 34s
branch-1.4 passed

:green_heart:
shadedjars
2m 48s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
0m 38s
branch-1.4 passed with JDK v1.8.0_232

:green_heart:
javadoc
0m 43s
branch-1.4 passed with JDK v1.7.0_242

:blue_heart:
spotbugs
2m 48s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
2m 45s
branch-1.4 passed

_ Patch Compile Tests _

:green_heart:
mvninstall
2m  1s
the patch passed

:green_heart:
compile
0m 41s
the patch passed with JDK v1.8.0_232

:green_heart:
javac
0m 41s
the patch passed

:green_heart:
compile
0m 45s
the patch passed with JDK v1.7.0_242

:green_heart:
javac
0m 45s
the patch passed

:broken_heart:
checkstyle
1m 31s
hbase-server: The patch generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
shadedjars
2m 45s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
2m 37s
Patch does not cause any errors with Hadoop 2.7.7.

:green_heart:
javadoc
0m 31s
the patch passed with JDK v1.8.0_232

:green_heart:
javadoc
0m 42s
the patch passed with JDK v1.7.0_242

:green_heart:
findbugs
2m 51s
the patch passed

_ Other Tests _

:green_heart:
unit
119m 52s
hbase-server in the patch passed.

:green_heart:
asflicense
0m 33s
The patch does not generate ASF License warnings.

171m 47s

Subsystem
Report/Notes

Docker
Client=19.03.4 Server=19.03.4 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-744/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/744

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 07ba2949becc 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-744/out/precommit/personality/provided.sh

git revision
branch-1.4 / 927981c

Default Java
1.7.0_242

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_232 /usr/lib/jvm/zulu-7-amd64:1.7.0_242

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-744/1/artifact/out/diff-checkstyle-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-744/1/testReport/

Max. process+thread count
4341 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-744/1/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.

@liuyongvs please fix checkstyle warning.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
0m 42s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:yellow_heart:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-1.4 Compile Tests _

:green_heart:
mvninstall
8m 10s
branch-1.4 passed

:green_heart:
compile
0m 40s
branch-1.4 passed with JDK v1.8.0_232

:green_heart:
compile
0m 43s
branch-1.4 passed with JDK v1.7.0_242

:green_heart:
checkstyle
1m 35s
branch-1.4 passed

:green_heart:
shadedjars
2m 43s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
0m 38s
branch-1.4 passed with JDK v1.8.0_232

:green_heart:
javadoc
0m 40s
branch-1.4 passed with JDK v1.7.0_242

:blue_heart:
spotbugs
2m 48s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
2m 44s
branch-1.4 passed

_ Patch Compile Tests _

:green_heart:
mvninstall
1m 55s
the patch passed

:green_heart:
compile
0m 38s
the patch passed with JDK v1.8.0_232

:green_heart:
javac
0m 38s
the patch passed

:green_heart:
compile
0m 45s
the patch passed with JDK v1.7.0_242

:green_heart:
javac
0m 45s
the patch passed

:broken_heart:
checkstyle
1m 28s
hbase-server: The patch generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
shadedjars
2m 39s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
2m 31s
Patch does not cause any errors with Hadoop 2.7.7.

:green_heart:
javadoc
0m 32s
the patch passed with JDK v1.8.0_232

:green_heart:
javadoc
0m 40s
the patch passed with JDK v1.7.0_242

:green_heart:
findbugs
2m 47s
the patch passed

_ Other Tests _

:green_heart:
unit
119m 12s
hbase-server in the patch passed.

:green_heart:
asflicense
0m 32s
The patch does not generate ASF License warnings.

155m 42s

Subsystem
Report/Notes

Docker
Client=19.03.4 Server=19.03.4 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-744/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/744

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 573cc26c1540 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-744/out/precommit/personality/provided.sh

git revision
branch-1.4 / 927981c

Default Java
1.7.0_242

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_232 /usr/lib/jvm/zulu-7-amd64:1.7.0_242

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-744/2/artifact/out/diff-checkstyle-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-744/2/testReport/

Max. process+thread count
4127 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-744/2/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.

@guangxuCheng  I have already fixed the  checkstyle warning of indentation

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
0m 38s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:yellow_heart:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-1.4 Compile Tests _

:green_heart:
mvninstall
8m 51s
branch-1.4 passed

:green_heart:
compile
0m 39s
branch-1.4 passed with JDK v1.8.0_232

:green_heart:
compile
0m 44s
branch-1.4 passed with JDK v1.7.0_242

:green_heart:
checkstyle
1m 35s
branch-1.4 passed

:green_heart:
shadedjars
2m 55s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
0m 40s
branch-1.4 passed with JDK v1.8.0_232

:green_heart:
javadoc
0m 38s
branch-1.4 passed with JDK v1.7.0_242

:blue_heart:
spotbugs
2m 54s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
2m 51s
branch-1.4 passed

_ Patch Compile Tests _

:green_heart:
mvninstall
1m 57s
the patch passed

:green_heart:
compile
0m 40s
the patch passed with JDK v1.8.0_232

:green_heart:
javac
0m 40s
the patch passed

:green_heart:
compile
0m 46s
the patch passed with JDK v1.7.0_242

:green_heart:
javac
0m 46s
the patch passed

:green_heart:
checkstyle
1m 30s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
shadedjars
2m 42s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
2m 31s
Patch does not cause any errors with Hadoop 2.7.7.

:green_heart:
javadoc
0m 30s
the patch passed with JDK v1.8.0_232

:green_heart:
javadoc
0m 38s
the patch passed with JDK v1.7.0_242

:green_heart:
findbugs
2m 54s
the patch passed

_ Other Tests _

:green_heart:
unit
120m 17s
hbase-server in the patch passed.

:green_heart:
asflicense
0m 33s
The patch does not generate ASF License warnings.

158m 12s

Subsystem
Report/Notes

Docker
Client=19.03.4 Server=19.03.4 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-744/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/744

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux f3699ca34524 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-744/out/precommit/personality/provided.sh

git revision
branch-1.4 / e3c0cb9

Default Java
1.7.0_242

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_232 /usr/lib/jvm/zulu-7-amd64:1.7.0_242

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-744/3/testReport/

Max. process+thread count
4206 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-744/3/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.


Add terraform openstack module for creating LB (via Neutron LBaaS).

 Added sample configuration to openstack-modules.sample.tf showing how this can be done to load balance across the control nodes, and across the edge nodes. I left the sample code commented out, so it has to be explicitly turned on.
Note: I found a bug in the terraform-openstack provider while testing this - https://github.com/hashicorp/terraform/pull/5557. Without this fix the creation of the LB may fail (it did more often than not for me).

One thing about this, we may not need all the commented code if it is just a sample file.
Terraform also joins all the files together, so it could be a separate file.
How about openstack-lb.sample.tf with no comments?

Pinging @sehqlr @Dacode45: Do either of you have a working Openstack environment?

I haven’t tried OS for a while, but I can take a look

On Jul 29, 2016, at 03:17, Langston Barrett<EMAIL_ADDRESS>wrote:
Pinging @sehqlr https://github.com/sehqlr @Dacode45 https://github.com/Dacode45: Do either of you have a working Openstack environment?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/CiscoCloud/mantl/pull/1263#issuecomment-236121977, or mute the thread https://github.com/notifications/unsubscribe-auth/ACnp5GrnrjW6VB5BxvjikbQWpQA9nECNks5qabcogaJpZM4HuIhY.


manpages: fix links when in version or translation

The links need to be rewritten to remove the extra path containing the
requested version or language, while still retaining the anchor.
For version, we cannot know before hand which version is presently
viewed, so we just drop to the latest version.
For language, we can be smarter and direct to content translated in
same language.
fixes #1382

This is still broken on Peffs deployment. The hrefs are unchanged.

That's expected: the fix is in the script that feeds the DB, and the DB is not regenerated when deployed on test.

nice effort @jnavila :) will try to double check locally this week - if you are confident feel free to merge it anyway

@pedrorijo91 It's a regex, so no confidence at all :gear:

I tried this locally and noticed some oddities:

the de link to the user manual goes to docs/user-manual/de, which makes sense. The stock version goes to docs/user-manual.html. That does work, but I wonder why we have the .html there. Ditto for the howto-index, but for some reason not for the api-index.

I tried testing the links for the API index (and the howto). But it looks like we don't actually build those in the first place? The links now go to docs/api-index (and docs/api-index/de), but there doesn't seem to be any content there.

The api-index is broken in the live english version as well. I think that file is just not hosted on git-scm. The .html ending of that file seems to get stripped here: https://github.com/git/git-scm.com/blob/2f81e0ce42cb616ce8dba9b3e76df93bfbbf9465/lib/tasks/index.rake#L80

That seems to be true of the howto-index links, as well? At least https://git-scm.com/docs/git points to https://git-scm.com/docs/howto-index.html which doesn't seem to work.

I guess I missed that in the original bug report.

@rimrul Thanks for confirming. So I think the big one to fix here is user-manual, and @jnavila's patch does indeed make that better. The weird .html thing is pre-existing, as well as the lack of howto/api content. So I think this works as advertised and can be merged.

Sorry for my lack of responsiveness. There are missing pages on git-scm.com wrt to git doc, which explains why some links are failing. The purpose of this fix is to correct the url rewritting only. It should extend to work correctly everywhere if we start generating missing pages.


adding parameters

I've made a few changes, to ensure internal logic, and also to enable the use of emep data files.


Parsing "Content-Security-Policy"

Description
Some API started adding "Content-Security-Policy" header to response. And sometimes this header value is split by \r\n  . As result you could receive "InvalidHeader" exception.
Example
Content-Security-Policy: \r\n
              default-src 'self'; \r\n
              script-src 'self' 'unsafe-eval' data: 'unsafe-inline' https://foo.com http://bar.com \r\n

Additional context
There is adding closure on CURLOPT_HEADERFUNCTION  in \GuzzleHttp\Handler\CurlFactory . This closure is taking headers by lines.
Solution
In my app I recall CurlHandler with another factory, where I re-implement closure for CURLOPT_HEADERFUNCTION . I'm checking if line started from CSP directive then I'm adding this line to previous headers item.

@GrahamCampbell what should be the fix for this? I am currently using laravel9


create json instance from raw json (unsigned char*)

I cant get nor set values if I try :
basic_ostream BOS = get_json_from_server(); // the json response from a server
json BOS_json = BOS;

If I am doing something wrong, whats the right way to create a json instance from raw json received from a webserver as basic_ostream?

Can anyone help me?

You need to have an istream, not an ostream.

What can I do if the http client I am using returns the response body as a "basic_ostream"?

That seems to be an odd thing for it to return.  What client are you using?

it was made by a friend, I was reading wrong, it actually returns "unsigned char*" and not "basic_ostream", my apologies.
but it does work still, how can I create a nlohmann::json instance from json (not Serialized) returned from a server?

json::parse()

that gives "Segmentation fault"

Where is the segmentation fault (stack trace)?  It could be a problem with the string itself.  Do you get the same fault if you use strlen() on the string?

@CheyenneForbes As @gregmarr said, the parse function can handle char *. Can you please add more precise description of your errors?

@CheyenneForbes Any update?

Hey, sorry for the delayed response, the client was actually sending a POST request instead of a GET request so the json instance was actually "empty bytes" when I was trying to add/get data, I thought the issue was with the json instance because when I opened the link in the browser it worked. I recommend that anyone using the json header file and plan to receive the json data from "outside" should do so in a try{}catch(){} block when application crashes due to "empty" data arent "acceptable", for example when being used in a web server

Thanks for the quick response!


javax.el in jersey-bean-validation is older than the one in dropwizard-validation

Which gives me warnings in my build when including dropwizard-jersey

@vrolijken Which version of Dropwizard are you using?
Just enforce using the version from dropwizard-validation and it should work. There's not much we can do about 3rd party libraries.

1.1.0, I'm busy crafting a pull request, did not expect feedback this fast ;-)


add sample for handling android-23 permission flow thru native-activity

#96 show how to handle them from java, it would be nice to have a sample that show how to initial a permission flow from C++.
/cc @Whiteseeker

This need to show how to extend native activity to implement the onRequestPermissionsResult callback.

/cc @claywilkinson said he managed to override the onRequestPermissionsResult method with a fragment.

In the Unity plugin, I wrote a Fragment that prompts for the permission if needed to access the auth token.  It works, I think it could be the model for a more general purpose approach for Native apps to work with the new permission model

run-time permission for audio are merged; that's is all needed for the repo now.  Like to close this one, any thoughts again it?  thanks

@ggfan, I think @claywilkinson approach is useful for app w/ nativeactivity when you can override dynamically the methods of the activity class to add the permission callback. But you can add dynamically a fragment instead.

correct, the callback mechanism is useful for the native-activity derived apps.  Theoetically run-time permission in that category could be done with:

derive a class from NativeActivity, and request the permission at the startup
use callback from jni side to take a native-callback pointer and do as it is processed in claywilkinson's  implementation.

we might cross this one later.

Just ran into this one and there hasn't been any activity here for a while... Did I just manage to miss the example, or is this still an issue?

@Cwiis The example of enabling it from application side could be found in camera sample:
https://github.com/googlesamples/android-ndk/blob/master/camera/basic/src/main/java/com/sample/camera/basic/CameraActivity.java
If you are expecting to have NativeActivity to have an interface to request permission automatically, no it is not there yet as I understand.

I like to close this one and if you have strong desire to add something in, yeah add a PR is great. I do look forward to having NativeActivity to have this functionality built-in: so NativeActivity keeps its cool of 0 java code in side the application.

This ought to be reopened - this bug is specifically about a NativeActivity example, not a Java example. Even if it involves some small amount of Java, an example of how to do this from a NativeActivity-based application would still be very useful.

the camera sample is derived from NativeActivity with camera permission request.
endless-tunnel, I believe, also needs disk write permission ( but never add it yet ) and should be added. Once that is done, enough usage of it inside sample.  But if you are looking for the integration inside NativeActivity for permission, that is not in the sample ( I would expect that would goes into NativeActivity's internal java code ).  Let me know I understood this wrong.  thx

I think I misunderstood the camera sample, and it's enough for now - but ideally, you wouldn't have to extend NativeActivity to process permissions, I think it ought to handle that case and provide a native API for it. I suppose this is a problem with the Android ndk though, and not these samples. Thanks for your patience!

this should work to bring permission flow to c++ until a proper sample comes up.
https://github.com/googlesamples/android-ndk/issues/636
unfortunately i need some help to make it work. this should work, theoretically.

this issue should be re-opened. NDK cannot do anything substantial without permissions. going back and forth to & from Java just for permission when an app architecture relies on turning runtime-permission  on and off will throttle the performance advantage expected from using NDK!/?


Allow pulling modules from insecure/self-signed registries and repos

What problem are you facing?
We're looking into managing our terraform modules from Crossplane, but are blocked by SSL certificate errors when pulling from our on-premise gitlab registry/repository.
connect failed: cannot get remote Terraform module: error downloading 'https://<module repo>?ref=main': /usr/bin/git exited with 128: Cloning into '/tf/d0703514-f1ed-4a74-a7d9-17ff4d6632ca'...
fatal: unable to access 'https://<module repo>': SSL certificate problem: unable to get local issuer certificate

How could Official Terraform Provider help solve your problem?
Allowing to either skip tls verify (this can be done by setting Insecure to true in the go-getter Client constructor) or setting the CA certificate would allow us to pull from self-signed registries

Hi,
I looked into this since we also need to pull from a self-signed repository. I found it is not enough to just add the Insecure: true to the go-getter client, since it is only used for when the go-getter client makes http requests.
However I found you can disable SSL check in git by setting the environment variable GIT_SSL_NO_VERIFY=true. This can be done in the controller config:
apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-terraform
spec:
  package: xpkg.upbound.io/upbound/provider-terraform:v0.10.0
  controllerConfigRef:
    name: provider-terraform
---
apiVersion: pkg.crossplane.io/v1alpha1
kind: ControllerConfig
metadata:
  name: provider-terraform
spec:
  env:
    - name: GIT_SSL_NO_VERIFY
      value: "true"

it ain't pretty, but it is a workarround.
I think the correct solution is to inject a configmap with root and intermediate certificates which needs to be trusted by the go-getter http/git client - but I have not looked into this yet or if it is even possible


I want my botchat to only run when I'm offline. How do I know I'm not online.

The api can only send messages from an account that it is logged into. Aka the account will always be online when it is running. You will need to find some other way to track this or use a different account.


How long will it take to finish a training process?

Thanks for your project, works pretty well for me. But now I am wondering a question that how long will it take to complete the whole process of training. I read the code, which indicates that total time steps is 5e6, and in each epochs it takes 5e3 time steps, according to my understanding, it will takes 1000 epochs to finish it.
I have trained it for 12 hours, with ~50 epochs finished, if my understanding above is correct, then it is very time-consuming for me to finish the training. Is there any misunderstanding toward my situation? What's more, if I terminate it now, will it continue training according to the result of this time? or it just train it again as very beginning?
Thanks a lot.

Hi,
In my experience 100 epochs should be enough to train the model. You can see a deeper discussion here: https://github.com/reiniscimurs/DRL-robot-navigation/issues/91
At each training time the model is initialized with random weights. If you want to continue training the model with saved weights, you need to load them with the load method.

Thanks for your reply, will keep trying.

Hello, how can I "load them with the load method"? Should I add some parameters after the python3 train_velodyne_td3.py command? Can you help me? Thank you very much!


 Would be more intuitive.
I personally have to look at the wall of text anyway to see what hotkey to press, might as well have mouse there and click instead.


CI implementation

[x] run all scenarios tests for each commit (doesn't matter what branch)
[X] run linters to check syntax

Pull created by Mishavint at 2023-04-04T13:29:05Z

Assignee is {'login': None}


Broken setup process

Started the "finish setup" process but it broke and I don't have an user now. I can still get into the admin with port forward but I can't access apps (times out) or single sign-on. It seems that it created the main domain with all its certs (e.g. kalm-cert and sso-domain-*) and I can go to the domain but I can't login. How can I create a user manually?

I got it to redo the setup but keeps failing on XHR failed loading: POST "http://localhost:3010/v1alpha1/initialize".

#137

The problem is that the setup or reconfigure process never finishes successfully. Timeouts keep happening and I never get to see the username/password created.

Seems you have a few issues that are talking about the same timeout problem. Could you please choose one for continue discussion then close the others?

closed for now, please check #150


Add support for switching TV on and off via CEC

Added two extra Alexa action to allow switching on and off the currently active CEC device by saying "Alexa, ask Kodi to switch (on/off) the (tv/television).
These two actions require the plugin from https://github.com/joshjowen/script.json-cec to be installed on Kodi, as there is currently no JSON API exposed for the CEC functionality.

In my opinion, this belongs somewhere else, like home automation software.  I don't think this skill is the place to turn on and off other equipment.

I'd hate to get involved with having to have a list of compatible plugins people need to install as well.

Hi Joe,
It's obviously up to you, but to be fair this is is a Kodi skill, and switching on and off the currently active CEC device IS a function Kodi supports out of the box using libCEC (since all the Raspberry Pi's have CEC Hardware). It even has functionality built-in to switch off the device when the screensaver kicks in. It's not like one is asking Kodi to switch on the kettle or some other device that has nothing to do with watching movies. Kodi and the TV it is connected to, are tightly coupled.
I agree having to use the plugin sucks, but at the moment Kodi doesn't expose the CEC functionality via JSON-RPC, so the plugin is the only way. If people don't need the functionality, they needn't install it. If the plug-in changes or stops working (unlikely since it is tiny and simple), it still doesn't break the skill, it just means that function won't work.

As this is a feature I would love to see I thought I'd give the pull request a go (using git fetch origin pull/240/head:240_cec to get the branch locally), however once deployed it breaks my endpoint with this error
"{u'message': u'An uncaught exception happened while servicing this request. You can investigate this with the zappa tail command.', u'traceback': ['Traceback (most recent call last):\\n', '  File \"/var/task/handler.py\", line 452, in handler\\n    response = Response.from_app(self.wsgi_app, environ)\\n', '  File \"c:\\\\users\\\\will\\\\appdata\\\\local\\\\temp\\\\pip-build-4ykpow\\\\Werkzeug\\\\werkzeug\\\\wrappers.py\", line 903, in from_app\\n', '  File \"c:\\\\users\\\\will\\\\appdata\\\\local\\\\temp\\\\pip-build-4ykpow\\\\Werkzeug\\\\werkzeug\\\\wrappers.py\", line 57, in _run_wsgi_app\\n', '  File \"c:\\\\users\\\\will\\\\appdata\\\\local\\\\temp\\\\pip-build-4ykpow\\\\Werkzeug\\\\werkzeug\\\\test.py\", line 884, in run_wsgi_app\\n', \"TypeError: 'NoneType' object is not callable\\n\"]}"
Reverting back to Master and redeploying fixes the issue

Great work on this project. The only thing I was surprised was missing in the project was actually turning on the TV. I can't use it with the TV off, and once I'm already holding the remote, it seems silly to use voice commands. Hope the kinks get worked out and it's merged 👍


1.5 criteria prep

Codecov Report
Patch and project coverage have no change.

Comparison is base (5275c80) 100.00% compared to head (3f1a643) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##               1.5     #1091    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           46        46
  Lines         2652      2414   -238
  Branches       396       354    -42
==========================================
- Hits          2652      2414   -238

Flag
Coverage Δ

foundry
?

production
100.00% <ø> (ø)

reference
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 29 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Could not find dependency "com.google.android.agera:agera:1.4.0"

Summary:
I get the following error message while building the project - Could not find dependency "com.google.android.agera:agera:1.4.0. The SDK Manager already has all the updates installed and there are no pending updates. Also, Android Studio is currently running on the latest stable build.
Steps to reproduce the issue:

Open Android Studio
Add the follwoing dependency to your project.
implementation 'com.google.android.agera:agera:1.4.0'
Build the project

Expected Behavior:
The project should build without any errors.
Observed Behavior:
The project build fails with the following error message - Could not find dependency "com.google.android.agera:agera:1.4.0"
Android Studio Version:
Android Studio 3.2.1
Build #AI-181.55<IP_ADDRESS>56338, built on October 9, 2018
JRE: 1.8.0_152-release-1136-b06 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
Screenshot:

Have you added jcenter() under repositories too, or just using something local and/or mavenCentral()?Agera is only published to jcenter

Hello @ernstsson,
Thank you so much for your reply.
Yes, I have jcenter() under repositories, here is my build.gradle(project) and build.gradle(app) file.
I am doing something wrong?

Agera seems to be currently missing from jcenter repository.
Or am I wrong?
https://jcenter.bintray.com/com/google/android/ doesn't have agera under it.

Looks like it suddenly went missing from jcenter the other day, no idea why. Added it back now, could you try again?

Is there any other repository which we could use instead of jcenter()? As it's going to be closed as I know


Switch to three-dots icon on sidebar toggle button

Current arrow icon causes some confusion because it also looks like a page changing button. It would be better to switch to the three-dots icon to eliminate any confusion.

Thanks for your contribution


Support ShouldPublishSymbols param in pipeline and set it to false for tool net-changelog-gen

Support ShouldPublishSymbols param in pipeline with default value "true"
Set it to false for net-changelog-gen because the tool needs to be PackAsTool and has some native binaries in its dependency which would be complained by the PublishSymbol step for missing BuildId for these native binaries. It's fine to not publish symbols for the tool.

I triggered a publish run at https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2866365&view=logs&j=6d7966cd-0423-5022-78e0-a1ae4dd99f62


Add Jenkins Pipeline support

https://jenkins.io/doc/book/pipeline/
Currently the plugin doesn't support Jenkins Pipeline.
If anyone has experience with implementing Pipeline support, please submit a Pull Request. 👍

I started here: https://github.com/TobiX/poll-mailbox-trigger-plugin/tree/pipeline - feel free to use that as a starting point.
That said, you probably should switch from hudson.util.Secret to the credentials plugin first, since I don't think the former is supported in pipelines...

Regarding secrets and credentials, there is a short documention on jenkins.io: https://jenkins.io/doc/developer/plugin-development/pipeline-integration/#handling-secrets

Can you please let me know if the issue is fixed with the pipeline jobs ?

@TobiX @nickgrealy - Can you please let me know if there is a way to use the plugin with Jenkins Pipeline Jobs?

Sorry, I can't provide that information. I no longer support this plugin.
On Thu, 2 Apr 2020 at 02:12, donepudi369<EMAIL_ADDRESS>wrote:

@TobiX https://github.com/TobiX @nickgrealy
https://github.com/nickgrealy - Can you please let me know if there is
a way to use the plugin with Jenkins Pipeline Jobs?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jenkinsci/poll-mailbox-trigger-plugin/issues/38#issuecomment-607307937,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMXR7IB22DPMAUYB3BGHQ3RKNKULANCNFSM4EQGHELA
.

--
Kind regards,
Nick Grealy
M: +61 4 0775 6895
E<EMAIL_ADDRESS>

@TobiX any update on this?

@Dibakarroy1997 Neither am I a maintainer of this plugin nor am I using it. I suspect this plugin doesn't have a maintainer at all at the moment.


Update Profile for Timm

Name
unchanged
Profile Image

Country
Germany
Region
Berlin
Hub
r0g agency
E-Mail
<EMAIL_ADDRESS>Phone
+4917661304615
WhatsApp
No response
Homepage
No response
Telegram
timmw
GitHub
timmwille
Twitter
No response
Facebook
No response
Instagram
No response
Mastodon
No response
WikiFab
Timm
Web
No response
Software
No response
Hardware
No response
Community
No response
Organizational Development
No response
Media & Art
No response
Data Security
No response
Open Source
No response
Repair
No response
Description
unchanged

not sure if it is cool to remove other peoples content btw ;)
Can we discuss this first?


@input:model-value doesn't allow to write negative numbers

We developed our custom numeric input based on this library.
Sadly we're facing a limitation, @input:model-value  doesn’t allow to start with - because it’s technically not a number until you put something behind the minus (thus it thinks it's null).
Here is the code of the custom component:
<template>
    <number
        class="number-input"
        :model-value="value"
        @input:model-value="onValueUpdated"
        decimal=","
        :separator="props.separator"
        :precision="props.precision"
        :min="props.min"
        :max="props.max"
        :suffix="props.suffix"
        :disabled="props.disabled"
        :placeholder="props.placeholder"
        :null-value="null"
    />
</template>

<script setup lang="ts">
    import { number } from '@coders-tm/vue-number-format';
    import { isNil } from 'lodash-es';
    import { watch, ref } from 'vue';

    interface Props {
        modelValue?: number | string | null;
        suffix?: string;
        precision?: number;
        separator?: string;
        min?: number;
        max?: number;
        placeholder?: string;
        disabled?: boolean;
    }

    interface Emits {
        (e: 'update:modelValue', value?: number): void;
    }

    const props = withDefaults(defineProps<Props>(), { precision: 2, separator: '.' });
    const emit = defineEmits<Emits>();

    const value = ref(props.modelValue);

    watch(
        () => props.modelValue,
        val => {
            value.value = val;
        },
    );

    const onValueUpdated = val => {
        if (!isNil(props.max) && val > props.max) {
            emit('update:modelValue', props.max);
        } else if (!isNil(props.min) && val < props.min) {
            emit('update:modelValue', props.min);
        } else {
            const adjustedVal = typeof val === 'string' ? (val.length > 0 ? parseFloat(val) : null) : val;
            emit('update:modelValue', adjustedVal);
        }
    };
</script>

I found a trick to workaround for our users for the time being but it's less than ideal.
The trick is to input the number as a positive number and hit - at the end to make it negative => http://recordit.co/6kNvHKAnBs
Would you have any idea/proposal to fix this usecase?
I already tried listening to keydown event for minus key and tryed to work with that but without success.
Perhaps you have an idea how this could be solved with or without change to the library itself 🧑🎓

@Germain-condo-group Firstly thanks for find this issue. I have solved it. Please check latest version.

Wonderful, I just tried latest version and it works flawlessly now.
Thanks for the fix in such short time!


Pinning to packaging < 22.0

safety version: 2.3.5
Python version: All
Operating System: All

Description
We are attempting to create virtual environments for our developers that include all production dependencies for their package plus all of our static analyzers and security checks, so they can reproduce our CI system locally. It has recently come up that the latest version of safety pins to packaging<22.0 which ~is incompatible~ requires some extra work to operate with some of our existing package dependencies.
Can you shed some more light on the comment in this commit: https://github.com/pyupio/safety/commit/aa1b1532818a1b2cb229b14907cad64c927fa8c6? What exactly is meant by "preventing issues?" Is this something that you could use help on or is on your roadmap to support?
What I Did
First look at my input file (reduced to show minimal reproducible error):
> cat test.in
pandera

Next, compile that file to a lockfile:
> pip-compile --no-emit-index-url --no-header --quiet --pip-args --no-input --resolver=legacy --output-file=test.txt test.in
> cat test.txt
mypy-extensions==0.4.3
    # via typing-inspect
numpy==1.23.5
    # via
    #   pandas
    #   pandera
packaging==22.0
    # via pandera
pandas==1.5.2
    # via pandera
pandera==0.13.4
    # via -r test.in
pydantic==1.10.2
    # via pandera
python-dateutil==2.8.2
    # via pandas
pytz==2022.6
    # via pandas
six==1.16.0
    # via python-dateutil
typing-extensions==4.4.0
    # via
    #   pydantic
    #   typing-inspect
typing-inspect==0.8.0
    # via pandera
wrapt==1.14.1
    # via pandera

Now to show the dev requirements:
> cat test-dev.in
-c test.txt

safety

And finally, attempt to lock that file:
> pip-compile --no-emit-index-url --no-header --quiet --pip-args --no-input --resolver=legacy --output-file=test-dev.txt test-dev.in
Could not find a version that matches packaging<22.0,==22.0,>=21.0 (from -c test.txt (line 7))
Tried: 14.0, 14.0, 14.1, 14.1, 14.2, 14.2, 14.3, 14.3, 14.4, 14.4, 14.5, 14.5, 15.0, 15.0, 15.1, 15.1, 15.2, 15.2, 15.3, 15.3, 16.0, 16.0, 16.1, 16.1, 16.2, 16.2, 16.3, 16.3, 16.4, 16.4, 16.5, 16.5, 16.6, 16.6, 16.7, 16.7, 16.8, 16.8, 17.0, 17.0, 17.1, 17.1, 18.0, 18.0, 19.0, 19.0, 19.1, 19.1, 19.2, 19.2, 20.0, 20.0, 20.1, 20.1, 20.2, 20.2, 20.3, 20.3, 20.4, 20.4, 20.5, 20.5, 20.6, 20.6, 20.7, 20.7, 20.8, 20.8, 20.9, 20.9, 21.0, 21.0, 21.1, 21.1, 21.2, 21.2, 21.3, 21.3, 22.0, 22.0
There are incompatible versions in the resolved dependencies:
  packaging==22.0 (from -c test.txt (line 7))

I realize there are some pretty simple workarounds in this case, and we are investigating tools like pip-compile-multi to solve this problem more robustly with our internal tooling, but I just wanted to flag in case others do not have the luxury of dodging a specific version of packaging. It could be someone is reliant on a new feature. I also acknowledge that this new version of packaging is hot off the press, and will take time to onboard. Let me know if I can help, I really like this tool!

I am sure I am not alone, but today github's dependabot updated one of my projects, dependency to packaging = ^22.0, which of course will not work in conjunction with safety 2.3.5.

Hi @dmaljovec and @qs5779,
Thanks for your interest in this issue.

Can you shed some more light on the comment in this commit: https://github.com/pyupio/safety/commit/aa1b1532818a1b2cb229b14907cad64c927fa8c6? What exactly is meant by "preventing issues?" Is this something that you could use help on or is on your roadmap to support?

Packaging 22.0 removed LegacyVersion, which Safety in some situations uses. It's in the roadmap, and we should solve it in the following minor releases.
There is already work in progress related to this issue. Indeed I'll request your help checking it when it gets released.
Thanks.

Awesome! Thanks for the quick reply and look forward to the update.

@yeisonvargasf Please let us know through this issue once that issue is solved. Thank you.
We have temporarily removed safety from our projects until this gets fixed.

@dashmug, the next version will solve this issue. We are near to releasing this new version.

Update here: we released a beta version (Feb 26) with significant changes and additional improvements.
This version ( https://pypi.org/project/safety/2.4.0b1/) should fix this issue. Could you try?
Let me know if this version works for you.

Hi,
packaging v23.1 is out, and the pre-release workaround is not working anymore with it:
poetry lock
Updating dependencies
Resolving dependencies... (11.5s)

Because safety (2.4.0b1) depends on packaging (>=21.0,<=23.0)
 and no versions of safety match >2.4.0b1,<3.0.0, safety (>=2.4.0b1,<3.0.0) requires packaging (>=21.0,<=23.0).
So, because <my-package> depends on both packaging (^23.1) and safety (^2.4.0b1), version solving failed.

Hi @nim65s, I'm sorry you're experiencing this issue; we revamped Safety CLI in the coming version 3.0 (this month); this 3.0 version will fix this issue with packaging and add more features and services.
I recommend you pin packaging if possible. If multiple users are having the same issue with 2.4.0.b1, we may look at how we can release a 2.4.0b2 version with a fix for this; otherwise, it's better to wait for Safety 3.0 this month, which is in a closed beta phase.

Like some previous users, we also have version conflicts. One of our dependencies uses packaging ^23.1 while safety forces it to <=23, which of course won't work. It's quite vexing when a well-known package like Safety rigidly pins to an outdated version of a dependency that's even more widely adopted.  So we hope you can at least push an update to b2 that is able to use the latest version or at least 23.1.

Hi, @Nachtalb  and @grutts; there is a 2.4.0b2 version that removes the upper clause restriction for the packaging dependency.

@yeisonvargasf What is the recommended solution at the moment? We are a paying custumer of PyUp.io and we want to switch from pipenv check to a tool working in poetry. I thought safety would be the right tool but this issues makes me feel bit concerned about the stability and maintenance policy of safety.
It was reported more than a year ago, 2.4.0b1 was published as workaround which stopped working, now 2.4.0b2 seems to be the workardound. 3.0 was promised in August 2023 and it is still in alpha version. The reason to use such a tool is to make us pass our software audit more easily and adding dependency on alpha or beta versions is contrary to this goal.
Why don't you release 2.4.0 as proper fix until 3.0 is ready?

@yeisonvargasf What is the recommended solution at the moment? We are a paying custumer of PyUp.io and we want to switch from pipenv check to a tool working in poetry. I thought safety would be the right tool but this issues makes me feel bit concerned about the stability and maintenance policy of safety.
It was reported more than a year ago, 2.4.0b1 was published as workaround which stopped working, now 2.4.0b2 seems to be the workardound. 3.0 was promised in August 2023 and it is still in alpha version. The reason to use such a tool is to make us pass our software audit more easily and adding dependency on alpha or beta versions is contrary to this goal.
Why don't you release 2.4.0 as proper fix until 3.0 is ready?

Hi @washeck. Please accept my apology for this sequence of events and the inconvenience caused. We are releasing version 3.0.0 within the next 24 hours, which supports the same safety check command from 2.4.0b2, so you will be able to upgrade to this version this week. Safety 3.0.0 includes native support for reporting on Poetry files. Full details on Safety 3.0.0, what changes it includes, and how to upgrade will be detailed here in GitHub and in our Documentation hub.
In addition to the release of version 3 this week, we will also be removing the beta flag on version 2.4.0, to support those who want to remain on version 2.x of safety.
We did not communicate clearly here, and I acknowledge that we must do better, both for Safety customers and the open source community. To ensure this won't happen again, we will also be moving to a public roadmap and maintenance schedule for Safety CLI 2.x and 3.x going forward, and adopting a trunk based development approach. In the meantime, I appreciate the feedback here and invite you to reach out at<EMAIL_ADDRESS>with any questions you have about safety cli, or any account-related questions.
Justin - CEO, Safety Cybersecurity

Hi @dmaljovec, @qs5779, @nim65s, @Nachtalb, @grutts, @washeck,
We hope this message finds you well. We wanted to follow up on the issue related to the pinning of packaging<22.0. We have made the necessary adjustments in Safety version 2.3.4, where we removed the use of LegacyVersion, effectively resolving the compatibility issues with packaging 22.0 and above. Additionally, our latest setup now specifies packaging>=21.0.
We believe this update should address the concerns raised and ensure smooth compatibility with dependencies. Could you please confirm if this resolves the issue on your end? Your feedback is invaluable, and we'd like to close this issue once we have confirmation from your side.
Thank you for your patience and support.
Best Regards,
The Safety Team

Could you please confirm if this resolves the issue on your end?

I'm not one of the people mentioned, but this appears to have solved the problem for me