Cancel request before it is sent

Is it possible to cancel an action before the corresponding HTTP request is sent?
From the readme, here's what we have to work with before a message is sent.
gmail.observe.before('send_message', function(url, body, data, xhr){ }

I was thinking it might be possible to cancel the xhr request, but it hasn't even been sent yet.
The use case it to perform a check and prompt the user for confirmation if certain conditions are met.

From what I can tell, we're not really doing any error-checking or catching any exceptions in our XHR intercept code.
Based on that, I would guess that throwing an error in your before handler will effectively cancel the XHR. Bare in mind, I have not tested this, so I can not guarantee it to work.
With that said, this very issue here seems to confirm it (although in that case, it is reported as a bug): https://github.com/KartikTalwar/gmail.js/issues/360

Thanks. I may investigate that route. I also just discovered the abort() method on the xhr object. Just experimenting in the console it appeared aborting it before it was sent would keep it from being sent at all (as long as it was open()ed before being abort()ed). It's looking promising

I'm going to assume you figured this one out, and close it for now.
Please re-open if you still need something resolved.

I haven't been able to test it thoroughly, but it seems to be working, with no errors logged to the console. Thanks for the help!

Unfortunately it appears this is not working. Previously it was stopping requests most of the time. I had occasional issues, but it was hard to differentiate them from a bug I had in my logic. Having just fixed that I stepped through with the debugger and confirmed that the XHR was opened (readyState=1), abort()ed it, and Gmail tried to send the request anyway, with no error in the console. Of note, I do have network issues, but it shouldn't take a network to cancel a network request. My guess is Gmail re open()s the request.
What I'm basically doing is:
gmail.observe.before('send_message', function(url, body, data, xhr){
  if(condition) {
    xhr.abort();
  }
})

Try throwing instead? It's not clean, but I suspect it has a higher chance of success.

That's a good idea. Don't know why I didn't think of it. Unfortunately it appears to be having any effect, not even logging the error in the console (not sure that's even possible, but it appears to be happening).
I think I've figured out why I thought it was working before though. When you send an email without a body, Gmail asks you if you're sure. In my testing my prompt would come up first and end up suppressing Gmail's prompt. This made it look like sending was being canceled by me. As soon as you have text in the body though, Gmail no longer prompts, and my prompt ceases to work.

This type of functionality (obstructing Gmail) is not really core to this library, so I'm not sure how much effort we're going to put into it.
That said, if you could put together a minimal proof of concept, I could test and see if I can reproduce. I'm fairly certain throwing in the XHR send method should ruin any chance of success...

The ideas isn't really to obstruct Gmail, but to request confirmation before sending the email. In terms of implementation the two tend be about the same. If there were a way to hook into the click event on the send button that would be better, but then I know of no way to detect who the recipients are (necessary in order to decide whether confirmation is necessary).
My project is basically a fork of the gmail-chrome-extension-boilerplate, with about 15 lines of straight-forward JavaScript added, about half of which is logging. Anyway, I think it's very minimal: https://github.com/Nateowami/Blindfold.

I see. Thanks for the clarification and link to your actual production code.!
I think a better approach than trying to intercept and postpone the the send-event is to be the one initiating it.
Here's my suggestion. It's a bit more complex, but IMO no where near impossible to do:

Initiaite Gmail.JS anyway you prefer
Listen for new compose-windows.
On the new compose-window event you manipulate the DOM in two ways:

Get a handle for the send-button. Use CSS modifications to hide it.
Create a new button by reusing the existing button's innerHTML (thus preserving locailzation, etc) and inject this next to the hidden button.

When your button (which is the only one visible) is clicked, run your check, and if everything is OK, manually trigger a click on the hidden send-button via JS (or use the Gmail.JS API to do that for you)
You can do this by listening for new compose windows, and manipulating their DOM.

How about that?

I see. Thanks for the clarification and link to your actual production code!
I think a better approach than trying to intercept and postpone the the send-event is to be the one initiating it.
Here's my suggestion. It's a bit more complex, but IMO no where near impossible to do:

Initiaite Gmail.JS anyway you prefer
Listen for new compose-windows.
On the new compose-window event you manipulate the DOM in two ways:

Get a handle for the send-button. Use CSS modifications to hide it.
Create a new button by reusing the existing button's innerHTML (thus preserving locailzation, etc) and inject this next to the hidden button.

When your button (which is the only one visible) is clicked, run your check, and if everything is OK, manually trigger a click on the hidden send-button via JS (or use the Gmail.JS API to do that for you)
You can do this by listening for new compose windows, and manipulating their DOM.

How about that?

@josteink A cleaner way to handle point 3 might be to simply add an absolutely positioned overlay element to the button's parent.
Or, if you want to get really creative, add a capturing event listener to the send button's parent element that calls event.stopPropagation() if the event target is the send button.
Then when your custom dialog is closed, temporarily remove the capturing listener, trigger the button click, and add the event listener back to the parent element.
The advantage of this would be that you only have to know the selector for the send button.
The disadvantage is that if Gmail changes their toolbar design significantly to not wrap each button in layers and layers of containing elements, you might end up obscuring other functions. Probably still safer than direct DOM modification though.
(I've actually used this method once for a client. Lots of fun.)

Thanks for the suggestions. I considered hooking into the click event, but I didn't know how to get the list of email addresses from the To, CC, and BCC fields. Looking at the API a bit more though, I now see there's a recipient_change event that does just that.
I'm a bit confused about the documentation though:
gmail.observe.on('recipient_change', function(match, recipients) {
  console.log('recipients changed', match, recipients);
});

I'm not sure what "match" refers to. From experimenting in the console it appears to be a large DOM element holding everything but the header in the compose dialog. I'm guessing this is in order to find this element in the DOM tree in order to track down which compose dialog it came from?
Actually, with this event handler, maybe I don't even need to intercept a click--just change some styling or something as a warning.
Anyway, thanks so much for the help! Much appreciated. :smile:

The match is a compose object or it's a DOM element you can use to construct a compose object with.
Use the compose objects to get the information you need.


[SessionMiddleware] Give SessionMiddleware some attention

[x] Use Foundation.UUID
[x] Use Map instead of [String:Any] #216
[x] Make request session getters more convenient
[ ] Find a way to not force var request when modifying session
[ ] Integrate with SQL (??)
[ ] Fix memory leaks #152

Should we keep the example here?

Current coverage is 80.13% (diff: 72.72%)

Merging #218 into master will decrease coverage by 0.02%

@@             master       #218   diff @@
==========================================
  Files           194        194
  Lines         14939      14933     -6
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits          11974      11966     -8
- Misses         2965       2967     +2
  Partials          0          0

Powered by Codecov. Last update 60a33dc...685dd7d


Promote wledPixel in the web interface

I would like to propose a minor behavior change to the wledPixel text in the web interface top so by clicking on wledPixel will get you to the github page and not the internal page of the local wledPixel device.
Changes to indexPage.h

to:

In fact, I thought so too, currently it's useless, I'm already where the link points.

Well it has a usage, if you are in the Settings menu it will jump back to Home.


FR: Show all notes that are not in the hierarchy

I have thought to use a graph filter to filter the notes that are not linked to my hierarchy notes but as the number of hierarchy notes increases, this becomes not feasible.
Any thought to achieve this?

Hey :)
I guess you can use the Dataview plugin for this! If you field names are up, same, down, then the following dataview query will show notes not connected to your hierarchy (or atleast most of them):
list
where !up AND !same AND !down

This is working in 1.4.0!
There is a new "Ducks View" which shows notes not in the hierarchy.
It doesn't open by default, so you have to run the cmd to open it


Add Required Schema as SQL Create Table command

Hi @DevSpeak,
Please add Required Schema as SQL Create Table command so we can create it rapidly with Hasura console SQL window.
Thanks.

Have included it in the README.
I'm not good at SQL, so feel free correct me if something is broken.


[Multicast] removal of stale multicast routes

This commit removes the relevant stale multicast routes. When multicast sender Pods are deleted or stop sending multicast traffic in 10 minutes, the related multicast routes should be considered as stale and are removed with this commit. MRouted implements a similar stale routes cleanup mechanism in OpenBSD and NetBSD.
Periodically cleaning stale multicast routes would improve the readability of multicast routes, such as the readability of "ip mroute" output. Also, the memory consumption of Nodes could be slightly reduced(
running 28 multicast senders, each sending multicast traffic to 2000 multicast groups, around 16M Slab Unclaimable memory was consumed by 56000 multicast route entries, observed from Netdata).

Codecov Report

Merging #3242 (be213a1) into main (871806d) will decrease coverage by 2.05%.
The diff coverage is 22.58%.

@@            Coverage Diff             @@
##             main    #3242      +/-   ##
==========================================
- Coverage   59.80%   57.74%   -2.06%
==========================================
  Files         331      331
  Lines       28463    28468       +5
==========================================
- Hits        17022    16439     -583
- Misses       9557    10234     +677
+ Partials     1884     1795      -89

Flag
Coverage Δ

kind-e2e-tests
45.11% <0.00%> (-2.79%)
:arrow_down:

unit-tests
41.33% <29.16%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/agent/multicast/mcast_route_linux.go
32.60% <0.00%> (-19.12%)
:arrow_down:

pkg/agent/util/syscall/syscall_unix.go
0.00% <0.00%> (ø)

pkg/agent/multicast/mcast_route.go
66.66% <100.00%> (+2.31%)
:arrow_up:

...g/agent/apiserver/handlers/featuregates/handler.go
0.00% <0.00%> (-82.36%)
:arrow_down:

...kg/apiserver/registry/system/supportbundle/rest.go
20.45% <0.00%> (-54.26%)
:arrow_down:

pkg/support/dump_others.go
0.00% <0.00%> (-51.73%)
:arrow_down:

pkg/support/dump.go
8.19% <0.00%> (-48.47%)
:arrow_down:

...egator/apiserver/handlers/recordmetrics/handler.go
0.00% <0.00%> (-44.45%)
:arrow_down:

...g/agent/apiserver/handlers/addressgroup/handler.go
0.00% <0.00%> (-40.00%)
:arrow_down:

...agent/apiserver/handlers/appliedtogroup/handler.go
0.00% <0.00%> (-40.00%)
:arrow_down:

... and 32 more

/test-multicast-e2e

/test-multicast-e2e

/test-multicast-e2e

/test-multicast-e2e

/test-multicast-e2e

/test-multicast-e2e

/test-multicast-e2e

/test-all
/test-multicast-e2e
/skip-windows-all
/skip-ipv6-all
/skip-ipv6-only-all

Change all "staled" to "stale".
A few nits in the commit message:

Current multicast implementation doesn't support removal of staled multicast routes. If the multicast sender pods are deleted or stop sending multicast traffic in 10 minutes, the related multicast routes should be considered as staled and be removed by this pr.

Probably: "This commits removes the relevant stale multicast routes, when multicast sender Pods..."
pods -> Pods.

SMCRoute has similar behavior by default troglobit/smcroute@fd4f681 as well.

SMCRoute implements a similar stale route cleanup mechanism:
Remove "as well".

Periodically cleaning of staled multicast routes would improve the readability of multicast route, such ip mroute.

route -> routes
such as readability of "ip mroute" output.

Also, memory consumption of antrea agents could be slightly reduced

antrea-agents

updated, thanks

/test-multicast-e2e

/test-flexible-ipam-e2e

/test-flexible-ipam-e2e

/test-flexible-ipam-e2e

/test-multicast-e2e

/test-multicast-e2e

/test-multicast-e2e

/test-multicast-e2e

/test-flexible-ipam-e2e

/test-flexible-ipam-e2e

/test-flexible-ipam-e2e

One comment, others LGTM.
BTW, don't forget to rebase your patch on main branch, and resolve candidate conflicts.

rebased

/test-multicast-e2e

/test-multicast-e2e

/test-multicast-e2e

/test-flexible-ipam-e2e

/test-flexible-ipam-e2e

/test-flexible-ipam-e2e

/test-all

/skip-conformance the test succeeded


Windows Phone and Band Application Communication Timeout with Azure

Hi Everyone,
I have been using the Windows Phone and Band Application to stream my sensor readings to Azure. However, Ive noticed that the application stops streaming data to Azure after about 30-45 minutes. The application is responsive but it looks like the Band is not updating the sensor readings.
Is there a timeout on the Bluetooth connection between the band and the phone? Is there a timeout on the phone itself that is causing this problem?
If none of these are reasonable, what code would I have to insert in the Application to periodically reset the Bluetooth connection to the band?
Thanks for your help!

For starters, the WP app has been developed for short time demos and trials. It doesn't run in the background and the first thing you might want to do is to enable the app to run in the background.

Thanks for your comment and applogies about the late reply. I found the issue to be lifetime of SAS token.
I would like to enable background application as well. How would I do this? Ive enabled location services in the application manifest. What code do I need in the body to keep the application alive?


Enhance UI of the "Become Volunteer" button

Description of the issue
The volunteer here button can be made more catchy which further catalyze in attracting more volunteers.

About me
I am a tech-enthusiast and an aspiring developer, passionate about Front-end technologies such as React.
Please assign me this issue under GGSoC'24. Looking forward to contribute an learn in the process.

hey its not currently required


Use http.get built-in cache rather than cache.star

Pass ttl_seconds to http_get and let it handle caching, rather than using cache.star explicitly. This is the preferred practice and is generally more efficient.

✨✨ Here's an AI-assisted sketch of how you might approach this issue saved by @rohansingh using Copilot Workspace v0.22
Topic

Remove apps/pslcricket entirely, since it doesn't work

Before

apps/pslcricket/manifest.yaml and apps/pslcricket/psl_cricket.star still exist in the repository.
The pslcricket app is still referenced in the runtime_exceptions array in the .github/scripts/check-apps.sh file.
The pslcricket app is not removed from the repository as per the task requirement.

After

apps/pslcricket/manifest.yaml and apps/pslcricket/psl_cricket.star have been deleted from the repository.
The pslcricket app has been removed from the runtime_exceptions array in the .github/scripts/check-apps.sh file.

Plan

apps/pslcricket/manifest.yaml (DELETE)
apps/pslcricket/psl_cricket.star (DELETE)
.github/scripts/check-apps.sh (CHANGE)

Remove the pslcricket app from the runtime_exceptions array

Sketch of implementation

View the changes
Details

Code analyzed at 4ca7716fa14c25e39d857c065767316df9d5d7ce

Remove the pslcricket app from the repository

Delete apps/pslcricket/manifest.yaml
Delete apps/pslcricket/psl_cricket.star
Remove the pslcricket app from the runtime_exceptions array in .github/scripts/check-apps.sh

For more details, open the Copilot Workspace session.


Proposal: Support multiple different gateways with filtering options for function services

This proposal relates to #55.
The OpenFaaS API Gateway discovers function services in a Docker Swarm based on the presence of a function label (or the func label on external providers). This behaviour is problematic if there are multiple instances of the API Gateway running, where each gateway is meant to cover different sets of services.
For example, in a multi-tenant environment, there may be more than one API Gateway deployed within the same swarm for different purposes. Or, there may be multiple deployments of a single stack for different branches of development. Functions meant for a certain API Gateway “leak” into other gateways because individual gateways do not have the ability to determine which specific functions are meant for them.
There are several possible ways to support multiple instances of the API Gateway in a single swarm.
Options
A: Allow the function label to be customized
function is currently coded as a literal string in the gateway to filter for OpenFaaS functions. This could be made into a configurable item so that gateways can be set to look for custom labels.
Here's an example of a gateway and a function configured to use custom_function as a label for function services.
gateway:
    image: functions/gateway:latest-dev
    environment:
        faas_function_label: 'custom_function'

echoit:
    image: functions/alpine:health
    labels:
        custom_function: "true"
    environment:
        fprocess: "cat"

Pros

Simple to change. The string function only appears in 4 places. A config can be added for something like faas_fuctions_label that defaults to function and is passed where needed.
Functions can have multiple labels to associate themselves with multiple distinct gateways.

Cons

A changing label key (as opposed to the label value) might not be desirable.

B: Look for a specific value or pattern in the function label
The value of the function label is not considered when reading for function services in MakeFunctionReader(). It's typically set to "true" in examples. A config could be added to specify a value or pattern to match on. So, something like the following (from gateway/reader.go#L41):
Before:
if len(service.Spec.TaskTemplate.ContainerSpec.Labels["function"]) > 0 {

After:
label_value := service.Spec.TaskTemplate.ContainerSpec.Labels["function"]
match, _ := regexp.MatchString(label_value_pattern, label_value)

if match {

A similar change would apply in swarmwatcher.AttachSwarmWatcher(). Here's an example service definition for gateway and a function.
gateway:
    image: functions/gateway:latest-dev
    environment:
        faas_label_value: 'some-custom-value'

echoit:
    image: functions/alpine:health
    labels:
        function: "some-custom-value"
    environment:
        fprocess: "cat"

Pros

Simple to change.
Using patterns for the label value could allow for interesting ways of selecting sets of function services.

Cons

Not sure how you would come up with a value when creating a function service spec in createhandler.makeSpec(). It currently sets the label value to "true".

C: Filter based on the stack namespace
If we assume that the gateway and its function services are deployed as part of the same stack, the gateway service's com.docker.stack.namespace label could be matched against function services.
Pros

As an option, this would be very convenient from a user standpoint for deployments where the gateway and service functions are together in the same stack.

Cons

Not sure how this would work for external providers.

D: Filter based on common networks
Function services could be filtered based on whether or not they share a common network with the gateway. Services that do not share a common network are not included.
Pros

This probably makes sense for all deployments. If the gateway cannot communicate with a function service because there isn't a route between them, it can't work anyways.

Cons

None?

Effort

Option A seems pretty simple. But, I'm not sure if it's a good idea.
Option B is also pretty simple. We'd need to somehow generate a string to match the label pattern when creating services.
Option C and D are already started on the filter_networks branch, I think. It'd need to be brought up to date and tested.

Another option that just occurred to me is to allow the gateway to be configured with arbitrary key-value matches on tags/labels. That would enable matching on stacks and any user-defined label.
The following would be the default behaviour.
gateway:
    image: functions/gateway:latest-dev
    environment:
        faas_function_constraint: 'function==true'

echoit:
    image: functions/alpine:health
    labels:
        function: "true"
    environment:
        fprocess: "cat"

A list of constraints could be passed.
gateway:
    image: functions/gateway:latest-dev
    environment:
        faas_function_constraint:
            - function==true
            - com.docker.stack.namespace==func
            - my_custom_key==my_custom_value

echoit:
    image: functions/alpine:health
    labels:
        function: "true"
        my_custom_key: my_custom_value
    environment:
        fprocess: "cat"

Derek add label: proposal

Related - multi-tenancy for Kubernetes backend - https://github.com/openfaas/faas-netes/issues/20

@kinghuang Is this proposal now possible thanks to these PRs?

CLI - Add label support
FaaS (Swarm) - Add label support
Faas-netes - Add custom labels

If there's something else that's needed, how about closing this and opening a new issue with the specifics. This issue is mostly related to adding/customizing labels which are now included.

Derek close: fixed


Table Question Answering Support?

Hi - Interested in support for table question answering models. It's noted that these aren't supported, but is there any reason they wouldn't work if leveraged?

Hi @xenova  - Thanks much for the response:
This model in particular is the one I'm interested in using with this library: https://huggingface.co/google/tapas-medium-finetuned-sqa
here's the example usage which is on the huggingface website.
# Use a pipeline as a high-level helper
from transformers import pipeline
import pandas as pd

# prepare table + question
data = {"Actors": ["Brad Pitt", "Leonardo Di Caprio", "George Clooney"], "Number of movies": ["87", "53", "69"]}
table = pd.DataFrame.from_dict(data)
question = "how many movies does Leonardo Di Caprio have?"

# pipeline model
# Note: you must to install torch-scatter first.
tqa = pipeline(task="table-question-answering", model="google/tapas-large-finetuned-wtq")

# result

print(tqa(table=table, query=query)['cells'][0])
#53

Big question was weather or not leveraging it just like this if I were to modify the supported models and tasks within this library and manually download and convert to ONNX?

I guess this does sound like an interesting addition to the library - considering how it could be used with HTML tables. Just one prerequisite: we use 🤗 Optimum for conversion, and from what I can tell, the library does not yet support the table-question-answering task. So, could you please open up a feature request there to add the task. You can link to this issue so we can track the progress here too. Once ready in Optimum, we'll be able to add it to transformers.js!


Missing locators on seeds pages

A lot of locators do not exist on the seed creation or details page.

The search function I think is a bug, the locators not.

It would be nice, but there is already so many things to pay attention to, I m not sure if it will help.
In general developers need to be more cautious when introducing new html elements.

I don't think anyone is not cautious on purpose, the problem is either that (1) they don't know what to be cautious about or (2) that it is simply too much to consider.
For me it is currently (1). I don't know what exactly to check in reviews.
@tschawax do you have some input about good interfaces between devs and QA related to HTML interfaces?


Static cookie required for zero-downtime deployments?

It seems that if an app does not have a static cookie set in a fly.io secret, then during deployment some instances may be unable to connect to nodes in primary region until those instances are replaced. So, for example, apps using fly_postgres_elixir could lose some writes.
If so, then maybe this should be mentioned in the docs (both here and in fly_postgres_elixir)?
Something like,  "Apps that require zero-downtime deployments should have a  RELEASE_COOKIE secret set so that all nodes can keep talking to primary region nodes during release rollouts"?

That's a good point. Thanks for suggesting this!

Thanks for the suggestion. I added it to both projects.

https://github.com/superfly/fly_rpc_elixir#prevent-temporary-outages-during-deployments
https://github.com/superfly/fly_postgres_elixir/#prevent-temporary-outages-during-deployments

Do the instructions make sense? Would they have helped you avoid the problem?


Remove Helm charts, which have moved to a separate repo

Pull Request Checklist

[ ] Description: Briefly describe the changes in this pull request.
[ ] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[ ] Testing: Have you written and run sufficient tests for the changes?
[ ] Code Review: Have you self-reviewed your code and addressed any coding standard issues?

Description
This PR removes the Helm templates and adds a README in their old location to point users to the new repo, https://github.com/open-webui/helm-charts.
Changelog Entry
Added

Adds kubernetes/helm/README.md

Fixed

N/A

Changed

N/A

Removed

All Helm files, including templates and chart, under the kubernetes/helm folder

Security

N/A

Breaking Changes

N/A

Additional Information

Closes https://github.com/open-webui/open-webui/issues/1757. Justification for moving Helm charts to a separate repo can also be found there.

LGTM, Thanks!


Create list components

Description
This PR introduces a new OrderedList and UnorderedList component to Primer per a discussion here.
Some Design Systems (like Charka) export OrderedList and UnorderedList components alongside a regular List component. I debating doing the same thing here but decided to keep the List API smaller and just export the two types of lists. Thoughts?

Integration

Does this change require any updates to code in production?

No, other than bumping primer version to include the new changes.
Merge checklist

[x] Added/updated tests
[x] Added/updated documentation
[x] Added/updated previews

Hey @AndrewRPorter, we had an internal conversation about this PR today. The good news: we like these components! The bad news: we think they should live in dotcom for now in the Primer::Experimental namespace. We're happy to help you out in moving everything over. Please don't hesitate to reach out!

Thanks for the heads up! I should have some time later this week/early next week to move this over.


bit locker is one of the best enterprise p;protectors I have ever heard of.

encryption science is very complicated I trust them a lot.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5476099c-9d70-97df-8ee6-bc442605cfbd
Version Independent ID: 49ca0628-bd88-e05b-b705-3b361b57512d
Content: BitLocker Group Policy settings (Windows 10)
Content Source: windows/security/information-protection/bitlocker/bitlocker-group-policy-settings.md
Product: w10
GitHub Login: @brianlic-msft
Microsoft Alias: justinha

Thank you for your feedback!


#17811 add opensearch driver

Closes #17811

Could you show how does connection page looks like for this driver and its connection url template?

Verified


Point transform issue

Hi,
I found a new issue,I have a location which is (lon, lat) (215018.25, 4824066.75), and the CRS is EPSG:32650. When I transform this location to epsg:4326 use this code:
lon, lat = 215018.25, 4824066.75
to_proj = pycrs.parse.from_ogc_wkt('GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["WGS 84",6378137,298.257223563,AUTHORITY["EPSG","7030"]],AUTHORITY["EPSG","6326"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.0174532925199433,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4326"]]').to_proj4()
from_proj = pycrs.parse.from_epsg_code(32650).to_proj4()
t_lon, t_lat = pyproj.transform(pyproj.Proj(from_proj), pyproj.Proj(to_proj), lon, lat)
print(t_lon, t_lat)

I got this result: -6.5258322207676605 43.51516233549309.
Which the lat is right, but the lon is wrong(the correct lon is about 113°),I think the question is located in the CRS’s center of Longitude.

I use gdaltransform got the correct answer:
gdaltransform -s_srs EPSG:32650 -t_srs EPSG:4326
215018.25 4824066.75

which print:
113.474167779232 43.5151623354931 0

What version of pyproj are you using?  I'm using pyproj 2.1.3, CRS is a new class in pyproj. If I need to change the code for a specific pyproj version I certainly can.
from pyproj import CRS, transform

wgs84 = CRS.from_epsg(4326)
utm50 = CRS.from_epsg(32650)

transform(utm50, wgs84, lon, lat)

Result:
(43.51516233549308,<PHONE_NUMBER>7923233)

The current version of pyproj CRS takes a lot of CRS representation.
Pyproj version 2+ can do a lot of this kind of CRS handling because the underlying C library PROJ does a lot of this now, which makes PyCRS library less necessary.

My pyproj version is 1.9.6.Dose your result correct? Should the lon lat reverse?

CRS won't work in pyproj version 1.9.6.
Here's code for 1.9.6.
from pyproj import transform, Proj
wgs84 = Proj(init="epsg:4326")
utm50 = Proj(init="epsg:32650")
lon, lat = 215018.25, 4824066.75

transform(utm50, wgs84, lon, lat)

Result:
(113.47416777923233, 43.51516233549308)

Should the lon lat reverse?
I don't know what is going on there.

Thanks!
I'll upgrade the pyproj version.But I think there is something wrong with the transform fn.

I have test the two methods. And got the same answer as you.The result of two methods was reverse.

If this is happening on the latest release, 2.2.1, it would be well worth reporting it to pyproj's repo.
The only issue with upgrade pyproj is that you will have to upgrade PROJ, too.

I'll try. What's your meaning of upgrade PROJ?

PROJ is the C library that is under the hood of pyproj.  pyproj 1.9.6 has PROJ 4.9.3(I think).  pyproj version 2+ required PROJ version 6+ .  Unless you have PROJ 6+, you won't be able intall pyproj 2+.

So was this a pyproj or pycrs issue?

Maybe it's caused by pyproj.

Sounds good, closing the issue then.


Create task with images from s3: are they copied to local cvat storage or not?

I wonder how image files are handled when I use s3-compatible storage (minio) as a source.
I searched docker cvat volumes and there was no image files in the corresponding task folder. On the other side, when I remove images in minio, they are still visible in cvat task.
Could someone clarify this?

They might be cached on the server in data/cache. Gradually they will be overwritten in this case.

@bsekachev Thanks for the quick response.
So permanent local copies of these image files are not created in cvat repository, right?

As far as I know, if we are talking about images and with enabled use_cache option, they are not copied. Related: https://opencv.github.io/cvat/docs/manual/advanced/data_on_fly/
As I told before, data/cache. The volume cvat_data mounted to several containers, for example to cvat_server.

thank you!


[C++][Parquet] Use the same environment setup script for Travis CI as local sandbox development

Currently the environment setups are slightly different, and so a passing Travis CI build might have a problem with the sandbox build and vice versa.
Reporter: Wes McKinney / @wesm
Assignee: Wes McKinney](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=wesm) / @wesm
Note: This issue was originally created as PARQUET-471. Please see the migration documentation for further details.

Wes McKinney / @wesm:
See patch https://github.com/apache/parquet-cpp/pull/54

Julien Le Dem / @julienledem:
Issue resolved by pull request 54
https://github.com/apache/parquet-cpp/pull/54


⚠ TiendaEnLinea has degraded performance

In bbbe4c1, TiendaEnLinea (https://www.fahorro.com/) experienced degraded performance:

HTTP code: 200
Response time: 5895 ms

Resolved: TiendaEnLinea performance has improved in 1e48313.


Using cls in integrated terminal sometimes freezes it

Testing #6654
on Windows, default PowerShell
I am sorry for the unclear steps, please ping me if you cannot repro

do some cds
do some lss
do a cls
sometimes it works, but very often it appears to freeze the terminal and the cursor is no longer visible
scrolling a bit seems to help...

The same problem occurs on Ubuntu 16.04 when using clear -- the cursor disappears

I believe I've reproduced this before, but I think it's one in the category of bugs that would require forking term.js.

I could be experiencing the same issue, not sure - when I type "cls" into command prompt, sometimes (with a full screen of text) it won't refresh until I hit another key (then it clears the screen and renders that key).
Windows 7, using Cmd and Powershell 2 as terminal

enter key down repeatly in terminal window.
key down cls command.

@leedonhyun thanks for the animation! That looks like this issue: https://github.com/Microsoft/vscode/issues/6738

Closing as a lot of changes have been made to clear logic in v1.2.


Add unreal engine reference to VS Documentation

Well, Unreal Engine already have his documentation page and stuff like that, but in the VS page didn't even mention the option if use UE4 to make games

⚠ Idea migrated from UserVoice
Created By: Diego Herrera
Created On: 2016/11/22 04:31:52 +0000
Votes at Migration: 1
Supporters at Migration: 1

This is a content suggestion, so will be closing soon, but want to make sure this gets on @erickson-doug's radar.


write on replicate before writing on leader

Description
fix #4145
How was this PR tested?
run unit tests
Review recommendation
git diff --ignore-all-space --color-moved main..  ingester.rs makes it less painful to compare, though far from perfect

@trinity-1686a same, can we merge this?

license checks panics. It seems to be an upstream issue in cargo-deny. I've opened a ticket: https://github.com/EmbarkStudios/cargo-deny/issues/595


What formula is used to calculate the value of memory in Resource table?

Description
I check the document, for example: The instance memory of a1.medium is 2048M, but memory in resource is 1392M, how to calculate reserve memory can get the value of 1392M?

These are estimated allocatable resources for the instance type given some overhead. https://karpenter.sh/docs/reference/instance-types/#resources:~:text=AWS instance types,default of AL2


Starting Ammonite - Dependency Not Found

I am trying to start ammonite, but I am getting the following error:
$ amm
Loading...
Compiling /path/to/my/home/predef.sc
Downloading https://repo1.maven.org/maven2/com/lihaoyi/ammonite-shell_2.12/1.1.0/ammonite-shell_2.12-1.1.0.pom
Downloading https://repo1.maven.org/maven2/com/lihaoyi/ammonite-shell_2.12/1.1.0/ammonite-shell_2.12-1.1.0.pom.sha1
java.lang.Exception: Failed to resolve ivy dependencies:
  com.lihaoyi:ammonite-shell_2.12:1.1.0
    not found: C:\Users\josephst\.ivy2\local\com.lihaoyi\ammonite-shell_2.12\1.1.0\ivys\ivy.xml
    not found: https://repo1.maven.org/maven2/com/lihaoyi/ammonite-shell_2.12/1.1.0/ammonite-
shell_2.12-1.1.0.pom
  ammonite.interp.Interpreter$DefaultLoadJar.ivy(Interpreter.scala:624)
  ammonite.predef.predef$.<init>(predef.sc:8)
  ammonite.predef.predef$.<clinit>(predef.sc)

When I try to get to (https://repo1.maven.org/maven2/com/lihaoyi/ammonite-shell_2.12/1.1.0/ammonite-shell_2.12-1.1.0.pom) in my browser I get a 404, so I do not think that it is any kind of proxy or certificate error, which I was was having previously, but solved.

Some more information:
I get the exact same error on Windows in the Git Bash, as well as on a Linux server.
I am using the excutable downloaded from (https://github.com/lihaoyi/Ammonite/releases/download/1.1.0/2.12-1.1.0)

I found #583. Following the solution there worked.


Default versions incorrect for older versions

A recent change removed important text "The C# compilers that are part of the Visual Studio 2017 installation or earlier .NET Core SDK versions target C# 7.0 by default."
IMO this text should be re-added, as well as information about langversion defaults for older VS versions.  According to https://docs.microsoft.com/en-us/visualstudio/releases/2019/servicing, VS2017 is still supported through 2027 and 2010 is still supported through July of this year.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5694e62b-c756-1f62-4014-2ceafa54c011
Version Independent ID: 3f01c378-22e4-197c-a862-ab4a924506c7
Content: C# language versioning - C# Guide
Content Source: docs/csharp/language-reference/configure-language-version.md
Product: dotnet-csharp
Technology: csharp-language-reference
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for writing this @chipplyman We should add that back in.
I've added it to our next sprint, and I've added the "up for grabs" label. You've included the text that should be restored in the description of this issue. If community members are interested in submitting a PR for this, we'll watch for it.


test(weaver/interoperation-node-sdk): fix broken nyc tests

Description
cd ./weaver/sdks/fabric/interoperation-node-sdk
$ yarn test
/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/ts-node/dist/index.js:851
            return old(m, filename);
                   ^
Error [ERR_REQUIRE_ESM]: require() of ES Module /home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/get-func-name/index.js from /home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/chai/lib/chai/utils/inspect.js not supported.
Instead change the require of index.js in /home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/chai/lib/chai/utils/inspect.js to a dynamic import() which is available in all CommonJS modules.
    at require.extensions.<computed> [as .js] (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/ts-node/dist/index.js:851:20)
    at Object.<anonymous> (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/chai/lib/chai/utils/inspect.js:4:15)
    at require.extensions.<computed> [as .js] (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/ts-node/dist/index.js:851:20)
    at Object.<anonymous> (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/chai/lib/chai/utils/objDisplay.js:11:15)
    at require.extensions.<computed> [as .js] (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/ts-node/dist/index.js:851:20)
    at Object.<anonymous> (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/chai/lib/chai/utils/getMessage.js:13:18)
    at require.extensions.<computed> [as .js] (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/ts-node/dist/index.js:851:20)
    at Object.<anonymous> (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/chai/lib/chai/utils/index.js:34:22)
    at require.extensions.<computed> [as .js] (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/ts-node/dist/index.js:851:20)
    at Object.<anonymous> (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/chai/lib/chai.js:25:12)
    at require.extensions.<computed> [as .js] (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/ts-node/dist/index.js:851:20)
    at Object.<anonymous> (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/chai/index.js:1:18)
    at require.extensions.<computed> [as .js] (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/ts-node/dist/index.js:851:20)
    at Object.<anonymous> (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/test/AssetManager.js:51:12)
    at m._compile (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/ts-node/dist/index.js:857:29)
    at require.extensions.<computed> [as .js] (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/ts-node/dist/index.js:859:16)
    at /home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/mocha/lib/mocha.js:250:27
    at Array.forEach (<anonymous>)
    at Mocha.loadFiles (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/mocha/lib/mocha.js:247:14)
    at Mocha.run (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/mocha/lib/mocha.js:576:10)
    at Object.<anonymous> (/home/peter/a/cacti-upstream/weaver/sdks/fabric/interoperation-node-sdk/node_modules/mocha/bin/_mocha:637:18) {
  code: 'ERR_REQUIRE_ESM'
}

=============================== Coverage summary ===============================
Statements   : 0% ( 0/184 )
Branches     : 0% ( 0/57 )
Functions    : 0% ( 0/19 )
Lines        : 0% ( 0/182 )
================================================================================
Handlebars: Access has been denied to resolve the property "statements" because it is not an "own property" of its parent.
You can add a runtime option to disable the check or this warning:
See https://handlebarsjs.com/api-reference/runtime-options.html#options-to-control-prototype-access for details
Handlebars: Access has been denied to resolve the property "branches" because it is not an "own property" of its parent.
You can add a runtime option to disable the check or this warning:
See https://handlebarsjs.com/api-reference/runtime-options.html#options-to-control-prototype-access for details
Handlebars: Access has been denied to resolve the property "functions" because it is not an "own property" of its parent.
You can add a runtime option to disable the check or this warning:
See https://handlebarsjs.com/api-reference/runtime-options.html#options-to-control-prototype-access for details
Handlebars: Access has been denied to resolve the property "lines" because it is not an "own property" of its parent.
You can add a runtime option to disable the check or this warning:
See https://handlebarsjs.com/api-reference/runtime-options.html#options-to-control-prototype-access for details

(add more description and relevant links)
Acceptance Criteria

Tests are passing OK

cc: @VRamakrishna @sandeepnRES

The real reason why I stumped upon this is that I wanted to upgrade nyc and when I tried to verify that the tests were still working after the upgrade I realized that they were broken to begin with.

https://github.com/hyperledger/cacti/security/dependabot/1038

Can i work around this issue? I can try

Can i work around this issue? I can try

@hollermay You are welcome to work on a fix! Give it a shot and let me know how it goes and if you'd like to take it to the finish line.

Sure! On it


[MiscDiagnostics] Fix a crash in OpaqueUnderlyingTypeChecker

Since opaque result type can reference generic parameters of context,
it cannot reply purely on "index" of the opaque generic parameter
while diagnosing a problem, it needs to perform a type substitution
using a substitution map of a particular candidate to determine the
underlying type.
Resolves: rdar://90456579

@swift-ci please test


FileSystemWatcher stops monitoring changes when root folder is deleted and recreated

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Have an empty repo; "master" with no root folder present (e.g. Unicorn).  Then checkout develop and create the required root folder (e.g. Unicorn). Perform initial serialization. All predicates gets serialized fine.
Add to git and commit develop
checkout master
Log will fill with a lot of

5636 19:23:58 INFO  Serialized item c:\Projects\TestDatastore\Unicorn\Core\sitecore\system\Dictionary\P\Publishing Items.yml deleted, reloading caches.
5636 19:23:58 WARN  All caches have been cleared. This can decrease performance considerably.

(as expected, GIT is cleaning house)
Ultimately GIT will have cleaned out, including the root folder Unicorn and switch to master is complete.
Now repeat the operation. Checkout develop (all items come back in) and then master. No log messages to be found - the FSW no longer reports the file deletions. Presumably because it gave up watching when the root folder was destroyed.
Please mention your Sitecore version, Rainbow version, and if also using Unicorn, your version of that too.
404-pre1

Ignore. They only get cached when processed, and git branching doesn't trigger processing.


MSFT_xServiceResource: Fix PSSA Issues

The PowerShell Script Analyzer issues in MSFT_xServiceResource need to be fixed.
This is the current result of running Invoke-ScriptAnalyzer:

This is part of #160


Flatpak cannot run any GUI software

For a while, I can't run any GUI software since three weeks ago.
I'm using Arch with Linux 6.4.10 and it complains about bubblewrap:
~ $ flatpak run com.github.tchx84.Flatseal
bwrap: Unexpected capabilities but not setuid, old file caps config?
error: Failed to sync with dbus proxy

I found out that this happens when I try to run any GUI applications like Discord or Unity Hub, but not in tty/pts mode without x11 such as GNU Octave command line mode.
Here are some version info:

flatpak: 1.15.4
bwrap: 0.8.0
dbus: 1.14.8

You need to report this here https://github.com/flatpak/flatpak/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc there's nothing the website can do about this.


Django

Is there an issue ? can you please explain this issue ? can I work on it

I can't understand exactly what are you saying, if there any issue please explain it...

I can't understand exactly what are you saying, if there any issue please explain it...

Is there any issue to work??

Is there any issue to work??

i dont think there is error...closing

i dont think there is error...closing


No mention of client connection in README

Thanks for sharing this!  I'm used to starting my openvpn sessions by creating a /etc/openvpn/name.conf file and doing sudo service openvpn start.  This failed horribly (emphasis on massive time sink) so I started googling and found an easier way for testing purposes:
# Below is the quickest way to test your VPN
$  sudo openvpn --config self.ovpn

Would you like a PR where I throw this tip into the readme somewhere elegantly or anything like that?
Also for debugging, would it be better to remove the -d switch in the command:
docker run --volumes-from $OVPN_DATA -d -p 1194:1194/udp --privileged -e DEBUG=1 kylemanna/openvpn

See #122 for general idea.
And thx again, you rock!

Merged your pull request, closing this issue.  If you have any more elaborate additions, be sure to consider adding them to the docs directory.


Pool: Fixed commented out tests

Also added constant to increase readability
Fixes #135

Those tests do not add any value and are removed.

I merged the variable backoff change.


Improve POSIX compatibility.

Add WIOCGETD to get terminal size which is used by some UNIXes.
Use atexit() for exit based functions
Hook SIGINT to invoke exit()
Use nanosleep() (usleep() is not a POSIX function)
Convert C++ comments to C comments.

Great stuff! Thank you very much.

Before I merge... Would you like to change the formatting for function void exit_message(void) with the bracket at the end of the line instead of a new line, to make it consistent with the clang-format convention in the project? And add the function declaration in the header? I can do it too, but that replaces the git blame credits.

What I don't understand in your code is the rnd function. If you simply want a pseudo-random number integer below x (but above zero) then you rand() % x will do it.


Heap use-after-free in stack_copy

The following input demonstrates a crash:
def class
ensure
  e e e e e e e e e e e e e e e e
end

[].map.a

ASAN report:
==26264==ERROR: AddressSanitizer: heap-use-after-free on address 0x62500000da30 at pc 0x0001013072f8 bp 0x7fff5eca6fb0 sp 0x7fff5eca6760
READ of size 16 at 0x62500000da30 thread T0
    #0 0x1013072f7 in __asan_memcpy (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x4d2f7)
    #1 0x10104f309 in stack_copy (mruby:x86_64+0x100159309)
    #2 0x10104f238 in mrb_env_unshare (mruby:x86_64+0x100159238)
    #3 0x101053762 in cipop (mruby:x86_64+0x10015d762)
    #4 0x1010726c4 in mrb_vm_exec (mruby:x86_64+0x10017c6c4)
    #5 0x10105dacf in mrb_vm_run (mruby:x86_64+0x100167acf)
    #6 0x101055a1e in mrb_run (mruby:x86_64+0x10015fa1e)
    #7 0x10108eb9a in ecall (mruby:x86_64+0x100198b9a)
    #8 0x101066230 in mrb_vm_exec (mruby:x86_64+0x100170230)
    #9 0x10105dacf in mrb_vm_run (mruby:x86_64+0x100167acf)
    #10 0x101055a1e in mrb_run (mruby:x86_64+0x10015fa1e)
    #11 0x1010533a4 in mrb_funcall_with_block (mruby:x86_64+0x10015d3a4)
    #12 0x10104ff77 in mrb_funcall_argv (mruby:x86_64+0x100159f77)
    #13 0x100fa07a2 in mrb_method_missing (mruby:x86_64+0x1000aa7a2)
    #14 0x101067c04 in mrb_vm_exec (mruby:x86_64+0x100171c04)
    #15 0x10105dacf in mrb_vm_run (mruby:x86_64+0x100167acf)
    #16 0x101055a1e in mrb_run (mruby:x86_64+0x10015fa1e)
    #17 0x10108eb9a in ecall (mruby:x86_64+0x100198b9a)
    #18 0x101066230 in mrb_vm_exec (mruby:x86_64+0x100170230)
    #19 0x10105dacf in mrb_vm_run (mruby:x86_64+0x100167acf)
    #20 0x101055a1e in mrb_run (mruby:x86_64+0x10015fa1e)
    #21 0x1010533a4 in mrb_funcall_with_block (mruby:x86_64+0x10015d3a4)
    #22 0x10104ff77 in mrb_funcall_argv (mruby:x86_64+0x100159f77)
    #23 0x100fa07a2 in mrb_method_missing (mruby:x86_64+0x1000aa7a2)
    #24 0x101067c04 in mrb_vm_exec (mruby:x86_64+0x100171c04)
    #25 0x10105dacf in mrb_vm_run (mruby:x86_64+0x100167acf)
    #26 0x101055a1e in mrb_run (mruby:x86_64+0x10015fa1e)
    #27 0x10108eb9a in ecall (mruby:x86_64+0x100198b9a)
    #28 0x101066230 in mrb_vm_exec (mruby:x86_64+0x100170230)
    #29 0x10105dacf in mrb_vm_run (mruby:x86_64+0x100167acf)
    #30 0x101055a1e in mrb_run (mruby:x86_64+0x10015fa1e)
    #31 0x1010533a4 in mrb_funcall_with_block (mruby:x86_64+0x10015d3a4)
    #32 0x10104ff77 in mrb_funcall_argv (mruby:x86_64+0x100159f77)
    #33 0x100fa07a2 in mrb_method_missing (mruby:x86_64+0x1000aa7a2)
    #34 0x101067c04 in mrb_vm_exec (mruby:x86_64+0x100171c04)
    #35 0x10105dacf in mrb_vm_run (mruby:x86_64+0x100167acf)
    #36 0x101055a1e in mrb_run (mruby:x86_64+0x10015fa1e)
    #37 0x10108eb9a in ecall (mruby:x86_64+0x100198b9a)
    #38 0x101066230 in mrb_vm_exec (mruby:x86_64+0x100170230)
    #39 0x10105dacf in mrb_vm_run (mruby:x86_64+0x100167acf)
    #40 0x101055a1e in mrb_run (mruby:x86_64+0x10015fa1e)
    #41 0x1010533a4 in mrb_funcall_with_block (mruby:x86_64+0x10015d3a4)
    #42 0x10104ff77 in mrb_funcall_argv (mruby:x86_64+0x100159f77)
    #43 0x100fa07a2 in mrb_method_missing (mruby:x86_64+0x1000aa7a2)
    #44 0x101067c04 in mrb_vm_exec (mruby:x86_64+0x100171c04)
    #45 0x10105dacf in mrb_vm_run (mruby:x86_64+0x100167acf)
    #46 0x101055a1e in mrb_run (mruby:x86_64+0x10015fa1e)
    #47 0x10108eb9a in ecall (mruby:x86_64+0x100198b9a)
    #48 0x101066230 in mrb_vm_exec (mruby:x86_64+0x100170230)
    #49 0x10105dacf in mrb_vm_run (mruby:x86_64+0x100167acf)
    #50 0x101055a1e in mrb_run (mruby:x86_64+0x10015fa1e)
    #51 0x1010533a4 in mrb_funcall_with_block (mruby:x86_64+0x10015d3a4)
    #52 0x10104ff77 in mrb_funcall_argv (mruby:x86_64+0x100159f77)
    #53 0x100fa07a2 in mrb_method_missing (mruby:x86_64+0x1000aa7a2)
    #54 0x101067c04 in mrb_vm_exec (mruby:x86_64+0x100171c04)
    #55 0x10105dacf in mrb_vm_run (mruby:x86_64+0x100167acf)
    #56 0x101091759 in mrb_top_run (mruby:x86_64+0x10019b759)
    #57 0x101162b95 in mrb_load_exec (mruby:x86_64+0x10026cb95)
    #58 0x1011634e5 in mrb_load_file_cxt (mruby:x86_64+0x10026d4e5)
    #59 0x100ef8be6 in main mruby.c:227
    #60 0x7fffbbbba234 in start (libdyld.dylib:x86_64+0x5234)

0x62500000da30 is located 4400 bytes inside of 8192-byte region [0x62500000c900,0x62500000e900)
freed by thread T0 here:
    #0 0x101310520 in wrap_realloc (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x56520)
    #1 0x100ff18e5 in mrb_default_allocf (mruby:x86_64+0x1000fb8e5)
    #2 0x100f728e8 in mrb_realloc_simple gc.c:202
    #3 0x100f72fce in mrb_realloc gc.c:216
    #4 0x10103175f in sym_intern (mruby:x86_64+0x10013b75f)
    #5 0x101031b19 in mrb_intern_static (mruby:x86_64+0x10013bb19)
    #6 0x1010d01c4 in mrb_mruby_string_ext_gem_init (mruby:x86_64+0x1001da1c4)
    #7 0x1010dc94f in GENERATED_TMP_mrb_mruby_string_ext_gem_init (mruby:x86_64+0x1001e694f)
    #8 0x10118258a in mrb_init_mrbgems (mruby:x86_64+0x10028c58a)
    #9 0x100ff1a71 in mrb_open_allocf (mruby:x86_64+0x1000fba71)
    #10 0x100ff1a17 in mrb_open (mruby:x86_64+0x1000fba17)
    #11 0x100ef7af8 in main mruby.c:171
    #12 0x7fffbbbba234 in start (libdyld.dylib:x86_64+0x5234)

previously allocated by thread T0 here:
    #0 0x101310520 in wrap_realloc (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x56520)
    #1 0x100ff18e5 in mrb_default_allocf (mruby:x86_64+0x1000fb8e5)
    #2 0x100f728e8 in mrb_realloc_simple gc.c:202
    #3 0x100f72fce in mrb_realloc gc.c:216
    #4 0x10103175f in sym_intern (mruby:x86_64+0x10013b75f)
    #5 0x101031126 in mrb_intern (mruby:x86_64+0x10013b126)
    #6 0x101031b5b in mrb_intern_cstr (mruby:x86_64+0x10013bb5b)
    #7 0x100f34920 in mrb_define_singleton_method (mruby:x86_64+0x10003e920)
    #8 0x100f3497f in mrb_define_class_method (mruby:x86_64+0x10003e97f)
    #9 0x1010ae601 in mrb_mruby_time_gem_init (mruby:x86_64+0x1001b8601)
    #10 0x1010be00f in GENERATED_TMP_mrb_mruby_time_gem_init (mruby:x86_64+0x1001c800f)
    #11 0x10118256f in mrb_init_mrbgems (mruby:x86_64+0x10028c56f)
    #12 0x100ff1a71 in mrb_open_allocf (mruby:x86_64+0x1000fba71)
    #13 0x100ff1a17 in mrb_open (mruby:x86_64+0x1000fba17)
    #14 0x100ef7af8 in main mruby.c:171
    #15 0x7fffbbbba234 in start (libdyld.dylib:x86_64+0x5234)

SUMMARY: AddressSanitizer: heap-use-after-free (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x4d2f7) in __asan_memcpy
Shadow bytes around the buggy address:
  0x1c4a00001af0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x1c4a00001b00: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x1c4a00001b10: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x1c4a00001b20: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x1c4a00001b30: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
=>0x1c4a00001b40: fd fd fd fd fd fd[fd]fd fd fd fd fd fd fd fd fd
  0x1c4a00001b50: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x1c4a00001b60: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x1c4a00001b70: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x1c4a00001b80: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x1c4a00001b90: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
Shadow byte legend (one shadow byte represents 8 application bytes):
  Addressable:           00
  Partially addressable: 01 02 03 04 05 06 07
  Heap left redzone:       fa
  Freed heap region:       fd
  Stack left redzone:      f1
  Stack mid redzone:       f2
  Stack right redzone:     f3
  Stack after return:      f5
  Stack use after scope:   f8
  Global redzone:          f9
  Global init order:       f6
  Poisoned by user:        f7
  Container overflow:      fc
  Array cookie:            ac
  Intra object redzone:    bb
  ASan internal:           fe
  Left alloca redzone:     ca
  Right alloca redzone:    cb
==26264==ABORTING
Abort trap: 6

This issue was reported by https://hackerone.com/ssarong

I think cef523c fixed this too.

Yes, it did. I'll close this.


Upgrade tins to version 1.8.0

Libraries.io has found that there is a newer version of tins that this project depends on.
More info: https://libraries.io/rubygems/tins/1.8.0

FYI:  Waiting for both:

coveralls (https://github.com/lemurheavy/coveralls-ruby) and
rubocop (https://github.com/bbatsov/rubocop) gems to upgrade.

Ok let's close this for now then


chore: use lossy compression on monthly wallpapers

Monthly wallpapers currently range in size from 10 MB to 30 MB. Once we have all 24 monthly wallpapers, they're going to take up around ~480 MB of the installation size. This is large enough that they'll take up around 10% of the installation size of Bluefin. That's hefty!
The file size could be reduced by applying lossy compression.
 Here's a comparison.

Can you spot the difference? The one on the right, which is lossy and included in this commit, has a slightly smoother film grain. And this is with 200% zoom; at 100% zoom, it's practically unnoticeable.
This marginal decrease in quality reduces file size by 85% - 95% and at the moment it already saves 177.6MB. If you ask me, it's definitely worth it! The gains will only continue as we add new wallpapers.
I believe there's merit to uploading the lossless variants somewhere, so I propose creating a new repository to host the lossless wallpapers alongside this commit.

I think we should try to do this with all artwork in the repo and make a new top-level directory for Art Assets that are uncompressed.
We can then have a ujust to download the images to /usr/local/share if having an easy to consume method makes sense.
Looking at the repo right now, the images are the single largest component.

Bazzite switched to jpegxl for their wallpapers and had substantial savings, we should just match them and the upstream gnome wallpapers switched to that too.

I like the idea of using jxl and compressing other files. I'll look into it, and for now I'll convert this commit to a draft

Alright, that should do! I solved a problem where the wallpapers would fail to load if they were applied before this change by using symlinks. Could probably remove 'em in a year or two, by then most users will have changed their wallpaper and their removal would affect next to no-one.
This should be ready to go.

Hold up, I'm going to convert this to a draft once more as I consider splitting it into multiple commits. There's a lot going on here now.


Rename rest apis with opensearch prefix

Issue #3
Description
Renames rest endoints with _opensearch path prefix

Is won't have legacy API to fallback to, so tests will start failing 50% of the time. I'd just write a couple of tests ensuring they hit the legacy paths for at least some use case and call it a day.

Agreed @dblock. Adding dedicated bwc tests.


Syntax error, Unexpected end of file extension_ow_repeater.php

Hey guys, good night.
I got this when i uploaded my theme to server: Parse error: syntax error, unexpected end of file in /home/postocic/public_html/wp-content/plugins/enhenyerowp-toolkit/includes/redux/extensions/ow_repeater/extension_ow_repeater.php on line 1
I don't understand what's wrong, someone can help? I will be very thankful.
Do you want to request a feature or report a bug?
(If this is a usage question, please do not post it here—post it on Stack Overflow instead. If this is not a “feature” or a “bug”, or the phrase “How do I...?” applies, then it's probably a usage question.)
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar.
What is the expected behavior?
Which versions of Redux, and which browser and OS are affected by this issue? Did this work in previous versions of Redux?

This does not appear to be related to redux, the javascript library.


Tests script are getting included in production build.

Hi
I am using creat-react-app for my project.  I am trying to reduce production bundle size and when I checked the bundle, found that tests javascript files are also referenced/included in the production bundle main.js .
Is there a way we can not include these test files?
Thanks
Manish

Can you make a simple repo to illustrate this bug?

Look at this main bundle:

which contains test file also.
I think we should exclude this tests script form the bundle.
Thanks
Manish

@saimonmoore @npverni @benpickles
Guys any input on above issue.
Thanks

+1
Seeing the same issue - or actually may I ask if it is expected to include test files (e.g. *.spec.js) in the build and if yes, what is the reason behind? (in my impression, Production build should run without any dependencies to the test files)
Thanks!


Updated to jenkins-lts 2.138.3

Running Jenkins with Java 10 and 11 is only experimental support. So I modified the dependency condition.
https://jenkins.io/blog/2018/06/17/running-jenkins-with-java10-11/

It's my mistake，I have updated it.

Thanks for your contribution!


Test API review changes

Dummy API changes to test API review gen for Python

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-template

/azp run python - template - ci


Support CESIUM_RTC glTF extension and use it for RTC_CENTER b3dm property

Currently when we find an RTC_CENTER property in a b3dm, we communicate that to the rendering engine by adding an RTC_CENTER property to the glTF's extras. By instead adding support for the CESIUM_RTC extension (even though it's technically a glTF 1.0 extension and we only do glTF 2.0), we'll make this a bit cleaner. And that would also make Cesium for Unreal able to load a bunch of models we've seen in the wild that use this extension with glTF 2.0 models even though it's not exactly to spec. e.g. https://twitter.com/uimac/status/1378339233568464900

Probably-related issue from the community forum:
https://community.cesium.com/t/i-could-show-ny-3d-tiles-but-i-couldnt-show-own-japanese-3d-tiles/12927/4

We should log a warning if/when the CESIUM_RTC extension is used, however, so that users are nudged toward producing fully spec-compliant tilesets.


Update for New Features

I made some small corrections and updated the channel creation FAQ for the new features recently introduced for an easier way to create a channel.
Description

Fixes

Thanks, made some small changes!


Bump to 0.1.7. Add CHANGELOG.md

I don't understand why builds are failing right now on travis. Seems like rustup.sh is allowing two toolchains to be mixed.

Seems to be a bug in the nightly builders.

We can trigger the builds manually tomorrow to send out new builds


hass.io won't start when zha component enabled

Home Assistant release (hass --version):
core-ssh:/config# hassio supervisor update
{
  "result": "error",
  "message": "Version 0.52 is already in use"
}
core-ssh:/config# hassio host update
{
  "result": "error",
  "message": "Version 1.0 is already in use"
}
core-ssh:/config# hassio homeassistant update
{
  "result": "error",
  "message": "Version 0.50.2 is already in use"
}

Component/platform:
zha
Description of problem:
After adding the zha component configuration and restarting Home Assistant never completes startup and the web UI is unavailable.
Running hassio homeassistant logs | grep zha only shows two lines:
2017-08-10 20:06:59 INFO (MainThread) [homeassistant.setup] Setting up zha
2017-08-10 20:07:09 WARNING (MainThread) [homeassistant.setup] Setup of zha is taking over 10 seconds.

The zigbee.db file is created in /config and is 45056 bytes in size.
Expected:
Successful startup and ability to join Zigbee devices or at the very least for homeassistant to still start even if the zha component can't be used.
Problem-relevant configuration.yaml entries and steps to reproduce:
zha:
  usb_path: /dev/ttyUSB1
  database_path: zigbee.db

Additional info:
Using a Nortek/GoControl Z-Wave & Zigbee USB Adaptor - Model HUSBZB-1.
core-ssh:/config# hassio host hardware
{
  "result": "ok",
  "data": {
    "serial": [
      "/dev/ttyUSB1",
      "/dev/ttyUSB0"
    ],
    "input": [],
    "disk": [],
    "audio": {
      "0": {
        "name": "bcm2835 - bcm2835 ALSA",
        "type": "ALSA",
        "devices": {
          "0": "digital audio playback",
          "1": "digital audio playback"
        }
      }
    }
  }
}

Having this same issue.  Same hardware as well.
{   "result": "error",   "message": "Version 0.53 is already in use" } core-ssh:~# hassio host update {   "result": "error",   "message": "Version 1.0 is already in use" } core-ssh:~# hassio homeassistant update {   "result": "error",   "message": "Version 0.51.2 is already in use" }
I have no other indication of what is going on just like you as well.  I know that it's zha doing it.  It is creating the file, but it doesn't do anything.

Hey, willbar are you running this from a docker container or hass.io?

As a new user of the HUSBZB-1 I have seen this issue as well.  It seems to happen randomly and I may need to try and restart hass 3-4 times until it will actually load up.  I am on version 0.58.1 installed in a venv on my raspberry pi3.  So far I have paired a few zigbee devices but I am also seeing this issue when I restart after adding a zwave device so I am not sure what the problem is.

New user here as well and I set up a new card with hass.io yesterday and I had the exact same problem. Never managed to get Homeassistant started with zha in the configuration. I don't have the exact numbers for the versions installed but I did a fresh installation with hass.io image for Raspberry PI 2, https://github.com/home-assistant/hassio-build/releases/download/1.1/resinos-hassio-1.1-raspberrypi2.img.bz2

FYI the issue still exists in 0.59.1 as well as 0.59
For other users having this issue I recommend restarting a few times until hass actually starts up.  That is what I have been doing and it seems to work for the most part.
If there are any more logs we can give to developers to get better stability please let me know and I will gladly supply more logs.

Ditto on 0.59.1.  I can't get it to start no matter what- running in a virtualenv.

Same issue as noted above.

I was able to get mine working after replugging my USB stick.  It seems
like the zha component has no failure mechanism for the usb device so if
it's not responsive then bootup of all of ha gets stalled.
On Dec 14, 2017 4:42 PM, "dexrex347"<EMAIL_ADDRESS>wrote:

Same issue as noted above.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/8922#issuecomment-351858481,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATttjfPrO4ceXcAUQIwnQaf-NgFYuOguks5tAaQ5gaJpZM4O0Ne2
.

@JustinPM I'm running the Hassbian image natively on a Raspberry Pi. Can we remove the waiting-for-reply label, as you can see a number of us are hitting this issue.

I ran into the same issue and spent days at a time trying to figure this out. Glad it wasn't something I was doing wrong - I was going a bit crazy over it.
My thread for help is here: https://community.home-assistant.io/t/web-interface-failing-to-come-up/42380/3
Hope this gets fixed.
I'm running hass.io over Ubuntu. When it works - it works great.

Me too, is the .db file not getting created/linked because it is in docker?

I tried hass.io and hassbian. Same Problem on both installations (OotB).
I am using XBee Pro S2C on a Sparkfun USB Dongle.
The Log seems same same. I inceased the Log Level to DEBUG:
2018-02-23 16:37:14 INFO (MainThread) [homeassistant.setup] Setting up zha 2018-02-23 16:37:14 DEBUG (MainThread) [zigpy_xbee.uart] Connection made 2018-02-23 16:37:14 DEBUG (MainThread) [zigpy.appdb] Loading application state from /home/homeassistant/.homeassistant/zigbee.db 2018-02-23 16:37:14 DEBUG (MainThread) [zigpy_xbee.api] AT command: AP (2,) 2018-02-23 16:37:14 DEBUG (MainThread) [zigpy_xbee.api] Command at (1, b'AP', b'\x02') 2018-02-23 16:37:14 INFO (MainThread) [homeassistant.setup] Setting up updater 2018-02-23 16:37:14 INFO (MainThread) [homeassistant.setup] Setup of domain updater took 0.0 seconds. 2018-02-23 16:37:14 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=updater> 2018-02-23 16:37:14 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.yr 2018-02-23 16:37:14 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: old_state=None, new_state=<state sensor.yr_symbol=unknown; friendly_name=yr Symbol, entity_picture=https://api.met.no/weatherapi/weathericon/1.1/?symbol=None;content_type=image/png, attribution=Weather forecast from met.no, delivered by the Norwegian Meteorological Institute. @ 2018-02-23T17:37:14.987835+01:00>, entity_id=sensor.yr_symbol> 2018-02-23 16:37:15 INFO (MainThread) [homeassistant.setup] Setting up tts 2018-02-23 16:37:15 INFO (MainThread) [homeassistant.setup] Setting up conversation 2018-02-23 16:37:15 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=conversation, service=process> 2018-02-23 16:37:15 INFO (MainThread) [homeassistant.setup] Setup of domain conversation took 0.0 seconds. 2018-02-23 16:37:15 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=conversation> 2018-02-23 16:37:15 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: old_state=<state sensor.yr_symbol=unknown; friendly_name=yr Symbol, entity_picture=https://api.met.no/weatherapi/weathericon/1.1/?symbol=None;content_type=image/png, attribution=Weather forecast from met.no, delivered by the Norwegian Meteorological Institute. @ 2018-02-23T17:37:14.987835+01:00>, new_state=<state sensor.yr_symbol=1; friendly_name=yr Symbol, entity_picture=https://api.met.no/weatherapi/weathericon/1.1/?symbol=1;content_type=image/png, attribution=Weather forecast from met.no, delivered by the Norwegian Meteorological Institute. @ 2018-02-23T17:37:15.833858+01:00>, entity_id=sensor.yr_symbol> 2018-02-23 16:37:15 INFO (MainThread) [homeassistant.setup] Setup of domain sensor took 2.3 seconds. 2018-02-23 16:37:15 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=sensor> 2018-02-23 16:37:15 INFO (MainThread) [homeassistant.setup] Setting up cloud 2018-02-23 16:37:15 INFO (MainThread) [homeassistant.setup] Setup of domain cloud took 0.0 seconds. 2018-02-23 16:37:15 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=cloud> 2018-02-23 16:37:16 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=tts, service=google_say> 2018-02-23 16:37:16 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=tts, service=clear_cache> 2018-02-23 16:37:16 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 1.0 seconds. 2018-02-23 16:37:16 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=tts> 2018-02-23 16:37:24 WARNING (MainThread) [homeassistant.setup] Setup of zha is taking over 10 seconds. 2018-02-23 16:37:24 INFO (MainThread) [homeassistant.core] Bus:Handling <Event system_log_event[L]: timestamp=1519403844.2756693, exception=, message=Setup of zha is taking over 10 seconds., source=bootstrap.py, level=WARNING>

Also running into this issue. Would appreciate any updates. I'm on Hassbian so let me know if you need extra information from me.
No amount of rebooting/restarting the service brings the zha component online.

Same issue here as well. Hassbian, raspberry pi 3 b+, using and XBee S2C on a Sparkfun USB Dongle. No rebooting/resetting/replugging usb helps.

Hey guys -
I just reinstalled via creating a new virtualenv with python 3.6 and it
works now.  Not sure if it was the fresh virtualenv, python 3.6, or the
newest version of hass, but it magically started working.
On Sat, Apr 7, 2018, 2:46 PM alexbremel<EMAIL_ADDRESS>wrote:

Same issue here as well. Hassbian, raspberry pi 3 b+, using and XBee S2C
on a Sparkfun USB Dongle. No rebooting/resetting/replugging usb helps.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/8922#issuecomment-379494509,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATttjR7ojwfZuWJgv44QR_2V7ZEcyaJ6ks5tmReigaJpZM4O0Ne2
.

Interesting - No such luck for me. Just tried a fresh install of raspbian, installed python 3.6.5, created a virtualenv, and installed homeassistant - still seeing the issue here.

broken for me, too
fresh install hass.io on raspberry pi today 0.66.1
works ok (HUSBZB-1) until I add
zha:
usb_path: /dev/ttyUSB1
database_path: /config/zigbee.db
hass.io web interface broken

Same issue here
2018-04-26 00:13:44 WARNING (MainThread) [homeassistant.setup] Setup of zha is taking over 10 seconds.
Added the XBee device i see it in my Docker container as /dev/ttyUSB0 - and the baud_rate options is not working.
I tested the XBee Pro S2C on my Win10 laptop and its confirmed working - and i see it in dmesg beeing added as USB device
Do i need some kind of special firmware for the XBee device?

2018-04-26 00:19:48 DEBUG (MainThread) [zigpy_xbee.uart] Connection made
2018-04-26 00:19:48 DEBUG (MainThread) [zigpy.appdb] Loading application state from /config/zigbee.db
2018-04-26 00:19:48 DEBUG (MainThread) [zigpy_xbee.api] AT command: AP (2,)
2018-04-26 00:19:48 DEBUG (MainThread) [zigpy_xbee.api] Command at (1, b'AP', b'\x02')
2018-04-26 00:19:58 WARNING (MainThread) [homeassistant.setup] Setup of zha is taking over 10 seconds.
2018-04-26 00:19:58 INFO (MainThread) [homeassistant.core] Bus:Handling <Event system_log_event[L]: timestamp=1524694798.7819579, level=WARNING, message=Setup of zha is taking over 10 seconds., exception=, source=bootstrap.py>

Same issue here using a HUSBZ-B1. Installed Hass.io on ubuntu server 18. Zwave works fine. Multiple reboots do not fix the problem. Initial zigbee.db file is successfully created. Commenting the component allows the system to boot. No errors in the log other than the 10 second warning.

I've got the same using XBee module

There has got to be a better way to debug this.  For me it's hit a point where it won't startup regardless.  Remove the old zigbee.db, plug / unplug device, reboot.
This is for the husbzb-1 device.
A dmesg has this printing on periodically.
cp210x ttyUSB1: failed set req 0x1e size 4 status: -32
cp210x ttyUSB1: failed to set baud rate to 300

For those that have it working say they get these messages as well, so it may be a red herring.

Anyone havet it working at all?

I was able to get it started at times on 0.68 and lower when my zigbee.db didn't have any devices registered.
Now with 0.69+ no combination works, even an empty zigbee.db.  I'm not sure if there were updates in 0.69.

I have the component working fine since I moved off a Pi and on to my own ubuntu server that I setup for home assistant.   I no longer see this issue with home assistant not loading.  I do see "zha taking longer than 10 seconds" but after 30-60 seconds things load up again.  I do know that on my faster hardware restarts are a lot faster so the time you need to wait may be longer than me.

@bakazm was the zigbee.db file created and could there be possible permission issues?
@dshokouhi I guess I'll have to be more patient and see what happens?  I haven't let it run longer than a few min like what @zenturacp references.  I am also not running on a pi, something a bit faster running on fedora with homeassistant in a container via hassio.

Unfortunately waiting doesn't resolve the issue

@zenturacp @MtotheKay @KLUSEK Thinking there might be a separate problem for those of us experiencing issues with the xbee s2c - I finally got my hands on a HUSBZB-1 (https://www.amazon.com/gp/product/B01GJ826F8), and after swapping to that have everything working fine now. Current hassbian image, latest updates applied to OS, homeassistant 0.68.1 - running on a raspberry pi 3 b+. Still get the taking longer than 10 seconds message, but otherwise things are behaving.

Looks like something needs to be updated on the hassio image side, further debugging I did here:
https://github.com/zigpy/bellows/issues/120

@dmulcahey Thanks for posting some suggestions.  I ran the udevadmin commands as noted in the first link and both ttyUSB0 and ttyUSB1 both report the same serial number so it won't help with the udev rules.   A dmesg doesn't seem to help either.

FYI this is still appearing with bellows 0.6.0 and zigpy 0.1.0 on homeassistant 0.70b7

I am using Ubuntu 17.10 in a VirtualBox VM with HA running in venv.  I'm using persistant names and having the same issues setting this up.

Have you tried flipping the devices? Just to make sure you’re pointing at the right one?

I have tried swapping them and restarting a few times now with no luck.

What does your full zha config look like? And can you jump on discord?

Zigbee
zha:
usb_path: /dev/zigbee
database_path: /home/homeassistant/.homeassistant/zigbee.db
zigbee is set to ttyUSB1 at the moment
I have also tried using ttyUSB1 and ttyUSB0  I am in the Home Assistant #general channel on discord

I've tried switching ttyUSB0 and ttyUSB1 as well to no avail.  The symlink variation doesn't work with hassio containers as the device symlinks don't transfer from the host to the container.
It seems to be however the zha component leverages the bellows libraries.  As I've been able to consistently get an ACK with a vanilla python container with zigpy and bellows libraries on ttyUSB1.
I have the typical zha config:
zha:
  usb_path: /dev/ttyUSB1
  database_path: /config/zigbee.db

After numerous troubleshooting steps on Discord with zombu2, we have discovered that the Nortek stick that I have only has the Zwave portion on it. I purchased mine from Gate Openers Unlimited on Amazon (https://www.amazon.com/s?marketplaceID=ATVPDKIKX0DER&merchant=A36RV344P5JWP3) - I am asking for a refund.

Interesting... can you outline the steps to verify if a Nortek / Linear HUSBZB-1 really has a zigbee radio in it? Some people with this stick have it working while others can't get it to work. Is it possible that some of them don't have zigbee?

@adamomg - was your stick a husbz-1 or husbzb-1? I started to see a lot of the first popping up while the second were really hard to find, and some of them were advertised in a fairly misleading fashion. I'm only seeing husbz-1's from the store you linked.

I dunno we tried to get my ttyUSB0 and ttyUSB1 working for at least an hour and it seems like it is a dud

At least for my situation, there is something wrong with the hassio x86_64 homeassistant image because I installed homeassistant in the python:alpine image and no issues with zha loading.

@alexbremel - I ordered a HUSBZB-1 and was sent a HUSBZ-1.

Husbzb-1 confirmed getting USB0 and 1.  Linux hassbian 4.9.80-v7+ #1098 SMP Fri Mar 9 19:11:42 GMT 2018 armv7l os ras pi 3b+.  Zwave component loads fine, hangs if I try to add zha.  DB was created, let sit overnight to see if it would load and no dice.

Confirmed having a Nortek HUSBZB-1
Attempt 1: NUC | HASS installed on Docker Container
Enabling ZHA on HUSBZB-1 does not work. Aeotec Z-Wave stick works fine. ConBee stick works fine. Tried booting with only Z-Wave side of the HUSBZB-1 enabled and HASS started up fine. Enabling ZHA breaks HASS.
Attempt 2: Rpi3 - HASS.IO
Same as results
Attempt 3: Rpi3 - Raspbian - HASS installed in a Virtual Enviroment
Same as results
Is there a way to test my HUSBZB-1 stick somewhere besides HASS?

@adamomg you can try running bellows on its own from the command line

See https://github.com/zigpy/bellows/issues/120
As best we can tell, there's a problem with bellows or zigpy* .  Would appreciate more feedback.

@dmulcahey @coreyo  I could dual boot on another partition on my desktop and install some ubuntu or something if someone wants to give me a quick rundown on how to help troubleshoot bellows/zigpy  My linux background is about 10 years old and rusty but its coming back.  I got a i5 3570-k and 12gb of mismatched ram in my desktop, running win 7 so I dont think a VM would work so well.

@adamomg I ordered mine from the same place. The manual that it came with says HUSBZB-1 and it shows as having 2 ports, one of which is labelled as zigbee... Does yours do the same? How can I verify if mine is also just a HUSBZ-1?

exact same issue - HUSBZB-1 and running official Home Assistant docker image on my QNAP. Z-wave starts up but if I enable zigbee, same issue as above posters.

they have bluetooth hooked up to the uart RX/TX pins (8/10). So you have to disable it in the config.txt file in the boot partition by adding dtoverlay=pi3-miniuart-bt to it and rebooting

any idea on how to do this on a hassio installation (since there is no /boot/ partition)?

You can put the SD card in to any other computer and modify it, /boot is fat32, so windows/mac should be able to read it. Windows doesn't support multiple partitions, but it should read the first one fine.

I have discovered that my adapter was faulty. I replaced and now everything works fine.

I grabbed my HUSBZB-1 stick from Home Controls Inc and started encountering these issues. Originally didn't connect the dots and spent a couple weeks troubleshooting on a thin client PC, an Odroid XU4, and a pi3
Per their advice I purchased a second stick -  and it has the same problem. They did mention they were aware there was a batch of sticks that had an issue when getting flashed but mine wasn't from the 'bad batch' either time. Using just a z-wave stick, or commenting out the zigbee portion resolves the issue every time.

FWIW I have just installed the Elelabs ZigBee Raspberry Pi Shield and once zha was configured hass.io wouldn't work. I thought it might be a conflict with my z-wave USB stick, but it wasn't. I was only able to get to work by moving from the 64-bit version of hass.io to the 32-bit version. I know the 64bit version is only in beta, but I thought I'd mention it here in other stumble over the same issue.
I was using version: 0.82.1

I am finding I have this same issue with a HUSBZB-1 stick as well but only if I restart home assistant from the reboot command.  If I reboot the entire raspberry pi, it will come up normally.  Currently only have 1 device installed through ZHA.

Same for me on NUC.  Issue with HUSBZB-1 stick as well but only if I restart home assistant from the restart command. If I reboot the entire raspberry pi, it will come up normally. Currently only have 1 device installed through ZHA.

Hi - helping issue springcleaning! Is this still an issue you are experiencing? Can you please try upgrading to the latest version of Home Assistant (0.90) and report back if this is still a problem? There has been a lot of zha enhancements lately! Thanks!

I can confirm I am experiencing this issue after moving from RPi to a X86-64 based HASS.io image.
What I've noticed is that if I stop all my containers, everything works locally, but if I start the supervisor (homeassistant/amd64-hassio-supervisor) container, it immediately stops working.
SO I tried to just start the home assistant container (homeassistant/qemux86-64-homeassistant) and that immediately got access to ZHA  (/dev/ttyUSB1) and everything is working fine, until I need to restart Home Assistant & have the supervisor running.


Ensure config file directory exists before creating config file

If the config file directory doesn't already exist, the application will crash on startup while trying to create the default configuration. Fix this by creating the directory.
Drive-by: Replace os.path functions by pathlib's functions

LGTM. However, please use semantic commit messages.
In this case it would be "fix: ensure config file dir exists".
Correct the commit message and I will merge.

No problem, I've just updated it. Feel free to update the PR title to match if you prefer.


Empty dialog fields overwritten when reordering Multifield Panel Items

Issue exists with the ACS Commons custom Multi Field Panel widget. Using the built-in dialog ordering mechanism (up/down arrows) to reorder items in the MFPanel list, empty/blank/optional dialog fields get overwritten by the item that is moved up or down. The values are no longer empty and persist if the dialog is saved.
To recreate:

Create a component dialog using the MFP widget; for example create a basic definitions (two-textfield MFP) as described here:
http://adobe-consulting-services.github.io/acs-aem-commons/features/widgets.html
Add this component to the design of a page or create a test page that uses this component
Open the dialog, and add four term/definitions to the dialog, but only fill out the 'term' field
In the third MFP item/row, fill out the 'definition' field w/ a test value
The 3rd item should be the only item w/ 'definition' included.
use the dialog MFP reordering mechanism to move the 3rd row up or down
the 3rd value will overwrite the empty values in the other rows, blowing away the empty values.

this makes reordering the items in a dialog w/ optional values difficult for authors.
you can also see this by filling out the bottom-most MFP row fully (term + definition), and adding a new, empty definition to the end of the list. Moving this item up to the middle of the list will cause the default empty fields to be overwritten by the data in other rows (starting with the bottom row).
This makes an otherwise awesome widget less usable for authors, especially around reordering.

I am also facing exactly the same behaviour. Reordering causes the empty field is overwritten by the value of item moved.

working on it

awesome looking forwards to checking the fix <3 this project

Has the issue of empty dialog fields being overwritten been solved?


Harmonize domain properties

    Hi,

I had a look at the domainProperty entry in the event schema.
It is stored as a ArrayList, but most methods creates it as a simple String URI entry.
In the required Stream process, you can only ask for single String domainProperty in the methods
https://cwiki.apache.org/confluence/x/i5NbDg
In the EventPropertyBuilder it is also just a single String
https://cwiki.apache.org/confluence/display/STREAMPIPES/01+Data+in+StreamPipes+|+Event+Properties#id-01DatainStreamPipes|EventProperties-EventPropertiyPrimitiveBuilder
But some methods in the EpProperty have a List Options
https://cwiki.apache.org/confluence/display/STREAMPIPES/01+Data+in+StreamPipes+|+Event+Properties#id-01DatainStreamPipes|EventProperties-EpProperty
It is intended to use multiple domainProperties?
An Example in the Geo Processors.
An Event can be a Geometry domain
but also be a Point
So I would like to add geometry and point as a vocabulary
If I have a processor, that asked for a geometry, I still can use it.
But if I have a processor that requires a Point, it is also valid
Although, you need then another method to read the ArrayList as well?
I think there are also some other examples not related to geo ;)
Originally posted by @flomickl in https://github.com/apache/streampipes/discussions/1185

@flomickl can you formulate an expected outcome? That would be great :)

@bossenti hope it is now easier to understand and the output clearer :)


sspop vs. ssload+sspinc

Opened to continue discussion from this mail list thread.
Initially, sspop was introduced as the only way to pop a return address from a shadow stack and was paired with  sschkra instruction to check  the shadow return address with that obtained from the data stack.  The sspop was motivated to reduce the code size of the program. Subsequently, a combination instruction sspopchk that  combined the functionality of the sspop and sschkra was introduced that leads to further code size reduction. The use of sspopchk is thus the preferred method for programs operating in shadow stack mode. With this change the sspop was retained to support the control stack mode. In control stack mode the program does not push a return address on the regular stack - the return address variable is held only on the shadow stack.
While originally motivated, the sspop introduces certain complexities for implementations due to its dual-dest nature as discussed at length in the email thread referenced above.
The use of sspop compared to a instruction pair ssload+sspinc does not lead to a significant code size increase as illustrated below. The function in control stack mode uses 6 additional code bytes. The function in shadow stack mode uses 4 additional code bytes. The extra load and store to the regular stack is elided in control stack mode.
control_stack_mode:    shadow_stack_mode:
 addi sp, sp, -24            addi sp, sp, -32
-c.sdsp x1, 24(sp)           c.sdsp x1, 24(sp)
+c.sspush x1                +c.sspush x1
:                                    :
-c.ldsp x5, 24(sp)           c.ldsp x5, 24(sp)
+ssload x1                  +c.sspopchk x5
+sspinc $1
 addi sp, sp, 24             addi sp, sp, 32
 ret                         ret

The sspinc can now also be used by unwinders to do fast unwinding. This removes a need for the ssp to be accessible using a URW CSR.
To support the micro-architecture simplification, the following is proposed:

Drop sspop and redefine the code points presently defined for it as ssload
Introduce a sspinc instruction that increments ssp by a non-zero unsigned 5-bit immediate scaled by XLEN/8
Change privilege at which ssp CSR can be accessed from URW to SRW

Proposed code points:
ssload x1 -<PHONE_NUMBER>00 00000   100 00001 ; x[1] = *[ssp]
ssload x5 -<PHONE_NUMBER>00 00000   100 00101 ; x[5] = *[ssp]
sspinc    -<PHONE_NUMBER>01 nzuimm  100 00000 ; ssp = ssp + nzuimm * XLEN/8

sspinc with nzuimm encoded as 0 is not supported.

PR to address the issue: https://github.com/riscv/riscv-cfi/pull/100/commits

The ssp CSR however will need to stay URW to support pthreads and coroutine type user mode thread switching.


OS-SPEC: initial commit

Should fix #127. Deprecates #218.
@cc @cdaylward @alban @jonboulle @vcaputo

cc @mpasternacki too

LGTM.
We can add more things later (such as /dev/pts) when the need arises.

This needs a reference and description from SPEC.md

@jonboulle Reference added to SPEC.md. See https://github.com/appc/spec/pull/221/files#diff-916b3e1e005fd96e3a0546715235477dR664

LGTM, roll on


Hi, when i try to run it, it shows the error below

Traceback (most recent call last):
File "C:\Users\HoxtonR\Desktop\LaMDA\LaMDA-pytorch-main\test.py", line 1, in
from lamda_pytorch.lamda_pytorch import LaMDA
File "C:\Users\HoxtonR\Desktop\LaMDA\LaMDA-pytorch-main\lamda_pytorch_init_.py", line 1, in
from lamda_pytorch.lamda_pytorch import LaMDA
File "C:\Users\HoxtonR\Desktop\LaMDA\LaMDA-pytorch-main\lamda_pytorch\lamda_pytorch.py", line 9, in
from config.config import CFG
ModuleNotFoundError: No module named 'config'

Hi @HoxtonR ,
I just pushed an update to fix the import errors you had listed. One of the last updates had changed the file directory structure.
The repository initially consisted of just the pre-training architecture for the model but I am actively updating it on a daily basis to include a full pre-training example. The training script is not fully implemented as a tokenizer needs to still be provided and the package manager needs to be implemented since this model requires specific libraries for scaling.
I will be updating consistently and keep this issue open for now.
Best,
Enrico


Check against accelerator instance instead of device type

What does this PR do?
Several places in the code base check accelerator availability by accessing the protected member AcceleratorConnector._device_type:
if trainer._device_type == DeviceType.GPU:
   ...

The member is protected and should not be accessed outside the connector
Which device type used is inherently defined by the accelerator, therefore one should check against the class of the currently used Accelerator
AcceleratorConnector._device_type is meant for internal use only

Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
I made sure I had fun coding 🙃
Part of #1 (it's a lie, this is just here to avoid noisy GitHub bot)

Closing in favor of #12069 which is more updated. Feel free to re-open if I'm wrong :)


Make scrollable-code-and-blockquote disable-able

From this snippet I gather that the scrollable-code-and-blockquote feature can't be disabled. Unfortunately, I hate it. :) What would it take to change that?

You can override the CSS of the feature. https://github.com/sindresorhus/refined-github/blob/b01263379d091df018286360968f48cadfe43a86/source/features/scrollable-code-and-blockquote.css

You can override the CSS of the feature. https://github.com/sindresorhus/refined-github/blob/b01263379d091df018286360968f48cadfe43a86/source/features/scrollable-code-and-blockquote.css

Ah! Makes sense, had not occurred to me. A checkbox might have saved me time in finding this, but your suggestion works for me.

Ah! Makes sense, had not occurred to me. A checkbox might have saved me time in finding this, but your suggestion works for me.

Since #6333 (version 23.2.11) you can disable the feature in the options page.
It's now called scrollable-areas


readme

Here's the readme for this one :)
If you can reply to my other ticket about this view, I'd love some insights :sweat_smile: :
https://github.com/saltcorn/leaflet-map/issues/3

Thank you!


Added source interface identifier to exportUSGstats function

Using the Prometheus input plugin, all of the 'unpoller_device_speedtest_XYZ' metrics collected only show 'All' as the port identifier. This is an unfortunate limitation for users who have multiple WANs set. I have addressed this limitation in my environment by modifying the code in this PR and compiling unpoller from source.

looks like one change needs to be made to pass the linter


output with Hills shows artifacts on export

When exporting I see artifacts in the png that don't exist in the preview, hiding Hills from the layer stack seems to resolve this. I suspect it's being rendered to disk in a different order.

Reloading the project and the output looks fine now, not sure what happened there. Thanks didn't realize I had those at the beginning as I was moving things around and removing steps in the generator, going to close this!


Execution failed for task ':upi_pay:compileDebugKotlin'. > A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction

Running Gradle task 'assembleDebug'...
e: C:\flutter.pub-cache\hosted\pub.dartlang.org\upi_pay-1.0.1\android\src\main\kotlin\com\drenther\upi_pay\UpiPayPlugin.kt: (78, 42): Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type Activity?
e: C:\flutter.pub-cache\hosted\pub.dartlang.org\upi_pay-1.0.1\android\src\main\kotlin\com\drenther\upi_pay\UpiPayPlugin.kt: (83, 15): Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type Activity?
e: C:\flutter.pub-cache\hosted\pub.dartlang.org\upi_pay-1.0.1\android\src\main\kotlin\com\drenther\upi_pay\UpiPayPlugin.kt: (97, 34): Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type Activity?
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':upi_pay:compileDebugKotlin'.

A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
Compilation error. See log for more details

Duplicate issue. Closing.

@drenther     can I link to the original error?

#60


word highlighting highlights half words

Using the following snippet where I'm highlighting onRecvPacket and noticed onRecvPacketProcessing is getting highlighted too:
```solidity /onRecvPacket/#g
```

Here's a stackblitz playground to see it in action: https://stackblitz.com/edit/github-j3wpz9?file=src%2Fpages%2Findex.mdx
We should discuss if this behavior is desirable or considered a bug.
cc @atomiks

Workaround is to use a range to scope it:
```solidity /onRecvPacket/1#g
```

I'm not sure we should auto-implement breaking on boundaries (e.g. punctuation, spaces) or not. We could maybe add a flag to do that? Kind of like regex flags which fits with the syntax...
b for break:
```solidity /onRecvPacket/b#g
```

I think regex is the way to go! Will do that