text:
shell doesn't work as expected with Starship: disabled due to TERM=dumb > (tmux - zsh)

[X] I have searched the FAQ and the documentation for solutions.
[X] I have searched the issue tracker for similar issues (the closed issues too).
[X] I have searched the Discourse for any errors and solutions.
[X] I can reproduce my issue on the latest commit of Doom Emacs.
[X] I have read How to Debug Issues and found no solution.

What did you expect to happen?
When I do M-x :shell, it should work?
What actually happened?
Ptmux;]1337;SetKeyLabel=F1=👉 public/foo\Ptmux;]1337;SetKeyLabel=F2=🎋 main\Ptmux;]1337;SetKeyLabel=F3=🔥[?]\Ptmux;]1337;SetKeyLabel=F4=🔼 push\Ptmux;]1337;SetKeyLabel=F5=🔽 pull\Ptmux;]1337;SetKeyLabel=F6=F6\]2;~/src/public/foo[ERROR] - (starship::print): Under a 'dumb' terminal (TERM=dumb).
Starship disabled due to TERM=dumb >

https://user-images.githubusercontent.com/16493751/123158835-f2384180-d474-11eb-9c51-f8dd50f3db28.mov
Describe your attempts to resolve the issue
🤷♂
Steps to reproduce

Open the Terminal (zsh) with Starship installed
Start the doom $ emacs . &
Call M-x :shell

System Information
https://paste.ubuntu.com/p/sNmKB4CJSD/

As described in the FAQ, shell is more of a repl for your shell environment, and is not capable of most graphical display cases. The term, and vterm modules however are more sophisticated and will be able to handle starship with no problems at all.

I second using vterm. "TERM=dumb" is expected behavior here.

What @destroyer449 said. shell is not a terminal emulator and it's current behavior is behaving correctly. Use vterm or term if you want a terminal emulator.

Thanks! I tried both of term and vterm but I got some issues:
term:

vterm:
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [../vterm-module.so] Error 1
make[1]: *** [CMakeFiles/vterm-module.dir/all] Error 2
make: *** [all] Error 2

Should I create another issue for the vterm compilation error? 🤔

@Dentrax In this case, starship is putting out ansi codes that term does not recognize. Perhaps starship can't cope with TERM=eterm-color either. Try setting it to xterm256-color in your shell dotfiles when you're in Emacs. Otherwise this seems like a configuration issue on starship's side, but I'm not familiar with starship so I'm afraid you're on your own with that.
As for vterm, it tries to compile vterm-module.so at startup. If that process fails, you'll have to compile it manually. There are instructions for doing so in the vterm module's readme. If none of those work or you are on an unsupported system (Windows), then vterm is no longer an option.

authors: Dentrax destroyer449 hlissner jakeisnt


text:
Add go-add-tags for go-mode

Hello. This pull request add the package go-add-tags to :lang go module.
Here is a screencast of what it does (taken from repository):
https://github.com/syohex/emacs-go-add-tags/blob/master/image/go-add-tags.gif

done

Thanks for your help!

source: gharchive/pull-request

authors: babariviere hlissner

repo: hlissner/doom-emacs

license: MIT

license_type: permissive

license_source: github-api


text:
59782 - [Newsroom] Newsfeed- Sorting not working on search results by a date range

Priority 2 - High
Steps to Reproduce:

Open URL
Legacy newsroom page:
Homepage: https://newsroom.accenture.com/
Adobe Franklin migrated page:
Homepage: https://main--accenture-newsroom--hlxsites.hlx.live/
Click on Calender filter
Select the date 26 july 2023 - 27 july 2023
Expected (Legacy Newsroom Page): All articles of 26 july 2023 - 27 july 2023 should be visible

Actual (Migrated Page): Only 26july 2023 date article is visble and is not arrange alphabetical.

Azdo Link: https://dev.azure.com/accenturecio26/WebContentDigAssetMgmt_PR1093/_workitems/edit/59782
cc: @ravkiran @amol-anand @raymond-pogi

Alphabetical order is invalid, the only issue is the mismatch of result between legacy and migrated pages

source: gharchive/issue

authors: jjjaspher veejayricana

repo: hlxsites/accenture-newsroom


text:
Added new Accessibe script to load delayed

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #30
Test URLs:

Before: https://main--danaher-ls-aem--hlxsites.hlx.page/
After: https://feat-30-accessible--danaher-ls-aem--hlxsites.hlx.page

@rgravitvl  and @mhaack - I have now updated, solved the conflict and also added it to be ignored on the lint checks.  Please can you review and provide honest feedback

repo: hlxsites/danaher-ls-aem


text:
Footer

Fix #3
Test URLs:

Before: https://main--hsf-commonmoves--hlxsites.hlx.page/
After: https://footer--hsf-commonmoves--hlxsites.hlx.page/

Sharepoint:
https://adobe.sharepoint.com/:w:/r/sites/HelixProjects/_layouts/15/Doc.aspx?sourcedoc={CEE1840B-83CA-4D96-A2C4-C032A8A840E2}&file=footer.docx&action=default&mobileredirect=true

Still needs some work in mobile views. I'd suggest starting at 300px and make sure it works there, then go up to desktop.

authors: AmyJZhao bstopp

repo: hlxsites/hsf-commonmoves


text:
[Bug]: The image is rotate to its original position (rotate is cancelled) when crop ratio is selected

Package Version
5.1.3
Flutter Version
3.22.3
Platforms
Web
How to reproduce?
Go to crop editor. Press Rotate. Then Done. Go to Crop Editor. Press Ratio. Select proportion. The image is rotate to its original position (Rotate is cancelled)
https://www.youtube.com/watch?v=Rt15G7D2Ceg
Logs (optional)
No response
Example code (optional)
Example code

Device Model (optional)
Google Chrome

This isn't an issue, it's intended behavior, as outlined here.
There are two reasons why I reset the crop state when the aspect ratio changes:

If, for example, the user rotates the image 90 degrees and then selects a 9:16 aspect ratio, it would apply the ratio flipped (16:9), which could be confusing for the user.
Changing the aspect ratio requires the editor to recalculate several elements, so it's easier to manage when it always starts from the default rotation. While it's technically possible to maintain the rotation, it would require additional code to implement.


text:
Alterar documentos NKS para grupo FB NKS

Alterar o texto para Grupo Facebook. Alterar o símbolo.

Passar o link para o grupo e para o site na página principal e remover da página de perfil. Retirar o texto das frases da página principal.

repo: hmapedro/SportNow-NKS


text:
Fix: POST /invites/redeem/{email} Case Insensitive

Change description

Fix: POST /invites/redeem/{email} - must be able compare emails case intensively for both request param and value stored in db
Add FT for POST /invites/redeem/{email} being case insensitive
Add FT for GET /users/by-email/{email} being case insensitive

[!IMPORTANT]
This PR requires manual testing by QA. Please notify the QA team @hmcts/pre-rec-evidence-qa.

QA instructions

Ensure coverage is sufficient for automated tests
Test Case 1:

User has an email in the database that is not fully lowercase i.e. Test.User@Hmcts.net (and has an invite to the portal).
Running POST /invites/redeem/{email} should work for non-matching email- i.e. test.user@hmcts.net

Test Case 2:

User has an email in the database that is lowercase test.user@hmcts.net (and has an invite to the portal).
Running POST /invites/redeem/{email} should work for non-matching email i.e. Test.User@Hmcts.net

This has been tested manually and it looks good.

repo: hmcts/pre-api


text:
Expose async interface in ManagementSDK

Most of the async methods from ManagementUtil are called with .Result and no awaitable Tasks are exposed. Hence, the ManagementSDK cannot be consumed in a async manner from a C# application.
There should be equivalent methods marked async in the ManagementSDK.
Also .Result should be converted to .GetAwaiter().GetResult() to get better stack traces in thrown exceptions.

Hi,
I would like to use this api from my own C# app. How can I achieve that, everytime I do a request (for example to get all experiments in my workspace) the app just gets stucked in the rest call!
Thank you

authors: Cheesebaron njss

license: mit

license_source: bigquery


text:
ZeroPadding2D slow down the inference

Hi Thang,
like the title already mentioned, using the ZeroPadding2D layer extremely slow down the inference, so we don't gain much from removing 1x1-conv and skips branches.
I found out that we only need ZeroPadding2D for 3x3 conv with stride 2 branches (halving the dimension). Meaning: you can remove most of the ZeroPadding2D layers and set padding to 'same' for those cases.
Best,
Vinh

found out, that Conv2D with padding = same and stride = 2, tensorflow puts 2 new lines on the bottom and right side of the input feature map. Therfore, the perception field of 1x1 and 3x3 convolution is not the same.
You can fix the bug when converting the deploy model by padding the 1x1 to 3x3 with:
padding = tf.constant([[0, 2], [0, 2], [0, 0], [0, 0]])


text:
Picture Settings

Hi,
I finally found solution to change e.g. picture presets. Please see my last comment at:
https://community.home-assistant.io/t/lg-webos-change-picture-setting-mode-with-scripts/262915
Maybe this could be useful for your project as well?
Thanks and regards
Helge

Additional discussion: https://github.com/merdok/homebridge-webos-tv/issues/371

repo: hobbyquaker/node-red-contrib-lgtv


text:
Calling functions individually

I am attempting to use .toLatLon()
import mgrs m=mgrs.MGRS() m.toLatLon('some MGRS')
but get a tree error:
--RTreeError: Error in "Convert_MGRS_To_Geodetic": MGRS Errors: String Error --
Am i doing something incorrect? When i run it with the Lat/Lon variables, then .toMGRS(); it works fine. Without it, doing it all together as in the example, it provides tree errors.

please provide a test case that fails.

This still fails on mgrs 1.3.6:
>>> import mgrs
>>> m = mgrs.MGRS()
>>> c = '15TWG0000049776'
>>> c
'15TWG0000049776'
>>> d = m.toLatLon(c)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.7/dist-packages/mgrs/__init__.py", line 98, in toLatLon
    core.rt.Convert_MGRS_To_Geodetic( c, plat, plon)
  File "/usr/local/lib/python3.7/dist-packages/mgrs/core.py", line 81, in check_error
    raise RTreeError(msg)
mgrs.core.RTreeError: Error in "Convert_MGRS_To_Geodetic": MGRS Errors: String Error

authors: Jeak MM-California hobu

repo: hobu/mgrs


text:
SP controlpanel()?

So I'm doing the example from #590, and I can't do a controlpanel() on the SP.  Is there a way to do this?

Only Model implements .controlpanel() right now.

I'll make it so you can make that a Model

Hmm, but I think Models might still only work with .solve ...

Yea, that was the error I was getting.  Sorry, should have posted:
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-7-dcd8be9650e5> in <module>()
----> 1 m.controlpanel()

/Users/codykarcher/Dropbox (MIT)/Research/gpkit/gpkit/constraints/costed.pyc in controlpanel(self, *args, **kwargs)
     83         """
     84         from ..interactive.widgets import modelcontrolpanel
---> 85         return modelcontrolpanel(self, *args, **kwargs)

/Users/codykarcher/Dropbox (MIT)/Research/gpkit/gpkit/interactive/widgets.pyc in modelcontrolpanel(model, *args, **kwargs)
     94     """
     95
---> 96     sliders = model.interact(*args, **kwargs)
     97     sliderboxes = []
     98     for sl in sliders.children:

/Users/codykarcher/Dropbox (MIT)/Research/gpkit/gpkit/constraints/costed.pyc in interact(self, ranges, fn_of_sol, **solvekwargs)
     74         """
     75         from ..interactive.widgets import modelinteract
---> 76         return modelinteract(self, ranges, fn_of_sol, **solvekwargs)
     77
     78     def controlpanel(self, *args, **kwargs):

/Users/codykarcher/Dropbox (MIT)/Research/gpkit/gpkit/interactive/widgets.pyc in modelinteract(model, ranges, fn_of_sol, **solvekwargs)
     82             #     print(out)
     83
---> 84     resolve()
     85
     86     return widgets.interactive(resolve, **ranges)

/Users/codykarcher/Dropbox (MIT)/Research/gpkit/gpkit/interactive/widgets.pyc in resolve(**subs)
     65         try:
     66             try:
---> 67                 model.solve(**solvekwargs)
     68             except ValueError:
     69                 model.localsolve(**solvekwargs)

AttributeError: 'SignomialProgram' object has no attribute 'solve'

Okay, so now the following code works:
m = Model(objective, constraints)
sp = m.sp(require_signomials=False)
sp.localsolve('cvxopt', verbosity=1)
sp.controlpanel()

The control panel is more interesting off the bat if you set Re to 1e6.

@cjk12, @whoburg, these signomial programs that do not require signomials could probably use a catchier name: LocalPrograms? Which would imply you could create one with Model.lp()...

Did you push this?

oops, committed but did not push. Pushed now!

Ok, this is pretty cool...  Whatever nomenclature is fine with me.

can someone post the full working example?

from gpkit import VectorVariable, Variable, units, SignomialProgram
import gpkit
from gpkit.constraints.set import ConstraintSet

Re = Variable("Re", 1e6, "-", "Reynolds Number")
CL = Variable("C_L", "-", "Lift Coefficient")
CD = Variable("C_D", "-", "Drag Coefficient")

def xfoil(x0):
    return [CD >= 0.01]

class AeroModel(ConstraintSet):

    def as_gpconstr(self, x0):
        gpconstr = super(AeroModel, self).as_gpconstr(x0)
        if x0 and x0["Re"] >= 1e6:
            constraints = xfoil(x0)
        else:
            constraints = [CD >= 1. + CL**2]
        return ConstraintSet([gpconstr, constraints])

constraints = AeroModel([CL >= 1.0, Re >= 1e4*CL])

objective = CD

m = Model(objective, constraints)
sp = m.sp(require_signomials=False)
sp.localsolve('cvxopt', verbosity=1)
sp.controlpanel()

Thanks. @bqpd, yeah - I tend to think that ideally users would not need the lines
sp = m.sp(require_signomials=False)
sp.localsolve('cvxopt', verbosity=1)

and that Model.controlpanel() would just work. Might make sense to update the error logic that spits out No Signomials remained after substitution.
A more precise name for LocalProgramsmight be SequentialGP. Maybe we should rename CostedConstraintSet to SequentialGP? It's a model that can be solved as a sequence of GP's, and this includes the AeroModel above as well as SignomialProgram.

SequentialGP seems strictly less precise to me; we have a program whose constraints are a sequence of local approximations of GPs.

Closing this issue, will link in the PR thread.

yes, I think it's fine for localsolve to work for models that contain no signomials but that contain locally approximable constraints (e.g. for external solvers)

Hmm, okay! Great.

that sounded suspicious -- am I missing something? I guess the elephant in the room is whether localsolve should work for GPs?

Yup. See the PR for the added
    def as_posyslt1(self):
        raise ValueError("must be checked during solve")

which lets Cody's example Just Work.

authors: bqpd cjk12 whoburg

repo: hoburg/gpkit


text:
Fix handling wkt strings

Closes https://github.com/holoviz/hvplot/issues/1137
The issue was that rioxarray gets loaded after running the second cell, which triggered the first if clause, but we didn't handle WKT strings properly; this PR fixes that.
    def _process_crs(self, data, crs):
        """Given crs as proj4 string, data.attr, or cartopy.crs return cartopy.crs
        """
        if hasattr(data, 'rio') and data.rio.crs is not None:
            # if data is a rioxarray
            _crs = data.rio.crs.to_wkt()
            print("RIO")
        else:
            # get the proj string: either the value of data.attrs[crs] or crs itself
            _crs = getattr(data, 'attrs', {}).get(crs or 'crs', crs)
            print("NOT RIO")

Supersedes contaminated https://github.com/holoviz/hvplot/pull/1138
Note the notebook cell execution number

Thank you for finding the cause of the confusing behavior. Your changes stops the error, but I still find the behavior not to be ideal, e.g.,
import cartopy.crs as ccrs
import rioxarray
import xarray as xr
from hvplot.util import process_crs

crs = ccrs.RotatedPole(pole_longitude=177.5, pole_latitude=37.5)
ds = xr.Dataset(attrs={"crs": crs})

a1 = process_crs(ds.rio.crs.to_proj4())
a2 = process_crs(ds.attrs["crs"])

type(a1), type(a2)

Outputs: (cartopy.crs.PlateCarree, cartopy.crs.RotatedPole)
I think we should swap the order of the if statement.

Good catch! I believe if proj_is_latlong is making a wrong assumption that only PlateCarree is lat lon; rotated pole is also in latlong.
    A rotated latitude/longitude projected coordinate system
    with cylindrical topology and projected distance.

repo: holoviz/hvplot


text:
Warning message 'Setting non-parameter attribute' could be improved?

The warning
Setting non-parameter attribute html=[] using a mechanism took me quite a while to parse
when I first encountered it.
Could this be improved? It gets triggered by an invalid argument
setting that is a likely bug in the user code.
Ideally I'd like to see something like  'invalid argument html=[] in xxxx call'
that points me to the xxxx fn with the offending argument.

You're right, it could be improved. Thanks for the feedback.
We have an issue about stopping param from setting non-parameter class attributes, but haven't implemented the proposal yet. The wording and/or information reported will be improved at the same time.
The proposal is briefly outlined in https://github.com/ioam/param/issues/174#issuecomment-315636661 (although that's just about the mechanism; the exact wording and information reported in messages hasn't yet been decided).

superceded #174

authors: ceball ea42gh tonyfast

repo: holoviz/param


text:
s6 issues with 2022.05.1 Alpine base image

It appears that the latest Alpine base image (tagged 2022.05.1 on Git) includes a broken version of s6. The symptoms would appear as some seemingly random permission issues.
For example, if I attempt to build the Tailscale community add-on with
BUILD_FROM=home-assistant/amd64-base:latest

The resulting image would not be able to start tailscaled due to permission issues. Here's the output:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun tailscaled (no readiness notification)
s6-supervise tailscaled (child): fatal: unable to exec run: Permission denied
s6-supervise tailscaled: warning: unable to spawn ./run - waiting 10 seconds
^Cs6-rc: warning: received INT, aborting longrun transitions and exiting asap
s6-rc: warning: unable to start service legacy-services: command crashed with signal 2

However, if I use the 2022.05.0 image with
FROM ghcr.io/home-assistant/amd64-base@sha256:f6b67206817445082fff84b17a35da6c5f83592ec6a4d4c2496a2a99225dff84

The resulting image behaves as expected.
Based off of the release notes, there might be an issue with s6-overlay and/or Jemalloc, as these are the only relevant things that have been updated.

s6-supervise tailscaled (child): fatal: unable to exec run: Permission denied

Please read: https://developers.home-assistant.io/blog/2022/05/12/s6-overlay-base-images

repo: home-assistant/docker-base


text:
Microsoft Visual C++ 14.0 is required

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.64.1
Python release (python3 --version):
3.6
Component/platform:
Discovery + Cast / Windows 10
Description of problem:
Unable to install packages netdisco + pychromecast.

Error: Microsoft Visual C++ 14.0 is required. Get it with "Microsoft Visual C++ Build Tools": http://landinghub.visualstudio.com/visual-cpp-build-tools

I've installed MS Visual Studio 2017 + MS Visual Studio 2015 (with "Python Tools for Visual Studio (January 2017)" checked) + Microsoft Build Tools 2015 (from here) but I still have the same error 😞
Is there a bug or I missed something?
Expected:
Working components installation.
Problem-relevant configuration.yaml entries and steps to reproduce:
discovery:

media_player:
    - platform: cast

Traceback (if applicable):

Additional info:

Solved by checking "Compiler and library Visual C++ for ARM" in the MS Visual Studio 2017 installation.

It did not work for me

authors: LionelPaulus morteza-notash

repo: home-assistant/home-assistant


text:
KeyError when Darksky API call fails in units()

Home Assistant release with the issue: 86.4
Last working Home Assistant release (if known): N/A
Operating environment (Hass.io/Docker/Windows/etc.): Docker
Component/platform: Darksky
Description of problem:
If the API call to Darksky fails, the def units(self): fails with a KeyError because the JSON payload it parses to determine the units doesn't contain the keys it's looking for.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
weather:
  - platform: darksky
    api_key: !secret darksky_api
    mode: hourly
    name: "Hourly Forecast"

Traceback (if applicable):
2019-01-30 00:19:00 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py",
line 239, in async_update_ha_state attr = self.state_attributes or {}
File "/usr/lib/python3.6/site-packages/homeassistant/components/weather/__init__.py",
line 125, in state_attributes self.hass, self.temperature, self.temperature_unit,
File "/usr/lib/python3.6/site-packages/homeassistant/components/weather/darksky.py",
line 114, in temperature_unit return TEMP_FAHRENHEIT if 'us' in self._dark_sky.units \
File "/usr/lib/python3.6/site-packages/homeassistant/components/weather/darksky.py",
line 241, in units return self.data.json.get('flags').get('units')
AttributeError: 'NoneType' object has no attribute 'json'

Additional information:
Issue is here: https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/weather/darksky.py#L241
The solution would be to return some default value or derive the units from some other means, and I'm open to suggestions on how to resolve this.

Duplicate of #16898, but seems like your fix (#22101) did not solve the issue, as the error now is raised in a different location.

authors: Spiffo iamtpage


text:
Can't make authentication at google calendar

Home Assistant release with the issue: 0.87.1

Last working Home Assistant release (if known): I was using this component before but this process in needed once ( I moved to clean Docker container)
Operating environment (Hass.io/Docker/Windows/etc.): Docker, But it's not critical for this bug.
Component/platform: https://www.home-assistant.io/components/calendar.google/
Description of problem:
I try to make this:

After you have it running complete the Google authentication that pops up. It will give you a URL and a code to enter. This will grant your Home Assistant service access to all the Google Calendars that the account you authenticate with can read. This is a Read-Only view of these calendars.

So I Got this Code:

Like you can see the format of the code is ABC-ABC-ABC
But in google the format is ABCD-ABCD

So basically I can't continue :)

same issue here

Same here

Have you updated to 0.90? If not, try that. If you have updated, is this still a problem?
Thanks
-HA Github Issues Clean-up Crew

authors: Snipercaine VirtualL naofireblade thecesco


text:
Verisure stopped working in 0.89.1

Home Assistant release with the issue: 0.89.1

Last working Home Assistant release (if known): 0.84.1
Operating environment (Hass.io/Docker/Windows/etc.): ubuntu

Component/platform: Verisure

https://www.home-assistant.io/components/verisure/
Description of problem:
The Verisure platform stopped working when I updated.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
verisure:
  username: !secret verisure_username
  password: !secret verisure_password

Traceback (if applicable):
2019-03-12 12:28:33 ERROR (MainThread) [homeassistant.setup] Error during setup of component verisure
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/setup.py", line 154, in _async_setup_component
    component.setup, hass, processed_config)  # type: ignore
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 331, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 244, in _wakeup
    future.result()
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 244, in result
    raise self._exception
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/verisure/__init__.py", line 70, in setup
    HUB = VerisureHub(config[DOMAIN], verisure)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/verisure/__init__.py", line 116, in __init__
    self.jsonpath = jsonpath.jsonpath
AttributeError: module 'jsonpath' has no attribute 'jsonpath'

Additional information:
Verisure has always been working for me, but since I updated from 0.84.1 to 0.89.1, it completely stopped working.

I'm having the exact same problem. Tried installing newer version of jsonpath, no difference. Also did a test with an older version of vsure but same error in logs with no attribute 'jsonpath'.

Searching for the error message gives this as first result with the exact same error message, they're stating that using jsonpath is old. Not being a programmer it doesn't really help me redesign the verisure module if that is needed.
https://stackoverflow.com/questions/44366048/jsonpath-python-module-module-jsonpath-has-no-attribute-jsonpath

Seems to be same as in #19993

This is sadly still not working. I've tried manually installing jsonpath 0.75 and 0.81, no change. I tried renaming the Verisure directory and then upgrading, forcing a reinstall. Same problem. Has anyone gotten Verisure to work? Perhaps @persandstrom, @Danielhiversen or @turbokongen that have contributed to the Verisure component has an answer? Sorry to @ you guys, I'm getting a bit desperate.

I'm running 0.89.1 in docker and it works fine
I will try to run it outside of docker and see if I can replicate the error

I tried 0.92.2 without docker and that works for me as well.
I really don't know where to start.
@AndreasAhrens could you try to install jsonpath with pip and then test the following code in pyhton
import jsonpath

a = jsonpath.jsonpath

I would like to know if this is a general problem with jsonpath or related to homeassistant/python-versiure

I run hass in pipenv in an lxc container, and have the same problem as OP.
The code you wanted:
(homeassistant) root@home-assistant:~/.homeassistant# python3.6
Python 3.6.7 (default, Oct 22 2018, 11:32:17)
[GCC 8.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import jsonpath
>>> a = jsonpath.jsonpath

Installed packages:
(homeassistant) root@home-assistant:~/.homeassistant# pip list|grep -i jsonpath
jsonpath                0.75
jsonpath-rw             1.4.0

My upgrade routine:
(homeassistant) root@home-assistant:~/.homeassistant# cd ~/homeassistant/ && source bin/activate && python3.6 -m pip install --upgrade wheel homeassistant mysqlclient pip websocket-client
Requirement already up-to-date: wheel in ./lib/python3.6/site-packages (0.33.4)
Requirement already up-to-date: homeassistant in ./lib/python3.6/site-packages (0.92.2)
Requirement already up-to-date: mysqlclient in ./lib/python3.6/site-packages (1.4.2.post1)
Requirement already up-to-date: pip in ./lib/python3.6/site-packages (19.1.1)
Requirement already up-to-date: websocket-client in ./lib/python3.6/site-packages (0.56.0)
Requirement already satisfied, skipping upgrade: aiohttp==3.5.4 in ./lib/python3.6/site-packages (from homeassistant) (3.5.4)
Requirement already satisfied, skipping upgrade: python-slugify==3.0.2 in ./lib/python3.6/site-packages (from homeassistant) (3.0.2)
Requirement already satisfied, skipping upgrade: pytz>=2019.01 in ./lib/python3.6/site-packages (from homeassistant) (2019.1)
Requirement already satisfied, skipping upgrade: PyJWT==1.7.1 in ./lib/python3.6/site-packages (from homeassistant) (1.7.1)
Requirement already satisfied, skipping upgrade: astral==1.10.1 in ./lib/python3.6/site-packages (from homeassistant) (1.10.1)
Requirement already satisfied, skipping upgrade: jinja2>=2.10 in ./lib/python3.6/site-packages (from homeassistant) (2.10)
Requirement already satisfied, skipping upgrade: pyyaml<4,>=3.13 in ./lib/python3.6/site-packages (from homeassistant) (3.13)
Requirement already satisfied, skipping upgrade: voluptuous-serialize==2.1.0 in ./lib/python3.6/site-packages (from homeassistant) (2.1.0)
Requirement already satisfied, skipping upgrade: voluptuous==0.11.5 in ./lib/python3.6/site-packages (from homeassistant) (0.11.5)
Requirement already satisfied, skipping upgrade: bcrypt==3.1.6 in ./lib/python3.6/site-packages (from homeassistant) (3.1.6)
Requirement already satisfied, skipping upgrade: requests==2.21.0 in ./lib/python3.6/site-packages (from homeassistant) (2.21.0)
Requirement already satisfied, skipping upgrade: ruamel.yaml==0.15.91 in ./lib/python3.6/site-packages (from homeassistant) (0.15.91)
Requirement already satisfied, skipping upgrade: cryptography==2.6.1 in ./lib/python3.6/site-packages (from homeassistant) (2.6.1)
Requirement already satisfied, skipping upgrade: attrs==18.2.0 in ./lib/python3.6/site-packages (from homeassistant) (18.2.0)
Requirement already satisfied, skipping upgrade: certifi>=2018.04.16 in ./lib/python3.6/site-packages (from homeassistant) (2019.3.9)
Requirement already satisfied, skipping upgrade: async-timeout==3.0.1 in ./lib/python3.6/site-packages (from homeassistant) (3.0.1)
Requirement already satisfied, skipping upgrade: six in ./lib/python3.6/site-packages (from websocket-client) (1.11.0)
Requirement already satisfied, skipping upgrade: yarl<2.0,>=1.0 in ./lib/python3.6/site-packages (from aiohttp==3.5.4->homeassistant) (1.1.1)
Requirement already satisfied, skipping upgrade: typing-extensions>=3.6.5; python_version < "3.7" in ./lib/python3.6/site-packages (from
aiohttp==3.5.4->homeassistant) (3.6.6)
Requirement already satisfied, skipping upgrade: idna-ssl>=1.0; python_version < "3.7" in ./lib/python3.6/site-packages (from aiohttp==3.5.4->homeassistant) (1.0.1)
Requirement already satisfied, skipping upgrade: chardet<4.0,>=2.0 in ./lib/python3.6/site-packages (from aiohttp==3.5.4->homeassistant)
(3.0.4)
Requirement already satisfied, skipping upgrade: multidict<5.0,>=4.0 in ./lib/python3.6/site-packages (from aiohttp==3.5.4->homeassistant) (4.1.0)
Requirement already satisfied, skipping upgrade: text-unidecode==1.2 in ./lib/python3.6/site-packages (from python-slugify==3.0.2->homeassistant) (1.2)
Requirement already satisfied, skipping upgrade: MarkupSafe>=0.23 in ./lib/python3.6/site-packages (from jinja2>=2.10->homeassistant) (1.0)
Requirement already satisfied, skipping upgrade: cffi>=1.1 in ./lib/python3.6/site-packages (from bcrypt==3.1.6->homeassistant) (1.11.5)
Requirement already satisfied, skipping upgrade: urllib3<1.25,>=1.21.1 in ./lib/python3.6/site-packages (from requests==2.21.0->homeassistant) (1.22)
Requirement already satisfied, skipping upgrade: idna<2.9,>=2.5 in ./lib/python3.6/site-packages (from requests==2.21.0->homeassistant) (2.7)
Requirement already satisfied, skipping upgrade: asn1crypto>=0.21.0 in ./lib/python3.6/site-packages (from cryptography==2.6.1->homeassistant) (0.24.0)
Requirement already satisfied, skipping upgrade: pycparser in ./lib/python3.6/site-packages (from cffi>=1.1->bcrypt==3.1.6->homeassistant) (2.18)

A restart, which shows the error:
(homeassistant) root@home-assistant:~/homeassistant# systemctl restart home-assistant && journalctl -u home-assistant -f
...
May 15 15:41:23 home-assistant hass[11351]: 2019-05-15 15:41:23 INFO (MainThread) [homeassistant.setup] Setting up persistent_notification
May 15 15:41:23 home-assistant hass[11351]: 2019-05-15 15:41:23 INFO (MainThread) [homeassistant.setup] Setup of domain persistent_notification took 0.0 seconds.
May 15 15:41:23 home-assistant hass[11351]: 2019-05-15 15:41:23 INFO (SyncWorker_9) [homeassistant.loader] Loaded lovelace from homeassistant.components.lovelace
May 15 15:41:23 home-assistant hass[11351]: 2019-05-15 15:41:23 INFO (SyncWorker_17) [homeassistant.loader] Loaded onboarding from homeassistant.components.onboarding
May 15 15:41:23 home-assistant hass[11351]: 2019-05-15 15:41:23 INFO (SyncWorker_5) [homeassistant.loader] Loaded system_log from homeassistant.components.system_log
May 15 15:41:23 home-assistant hass[11351]: 2019-05-15 15:41:23 INFO (SyncWorker_6) [homeassistant.loader] Loaded websocket_api from homeassistant.components.websocket_api
May 15 15:41:23 home-assistant hass[11351]: 2019-05-15 15:41:23 INFO (MainThread) [homeassistant.setup] Setting up logger
May 15 15:41:25 home-assistant hass[11351]: 2019-05-15 15:41:25 ERROR (MainThread) [homeassistant.setup] Error during setup of component verisure
May 15 15:41:25 home-assistant hass[11351]: Traceback (most recent call last):
May 15 15:41:25 home-assistant hass[11351]:   File "/root/homeassistant/lib/python3.6/site-packages/homeassistant/setup.py", line 156, in _async_setup_component
May 15 15:41:25 home-assistant hass[11351]:     component.setup, hass, processed_config)  # type: ignore
May 15 15:41:25 home-assistant hass[11351]:   File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
May 15 15:41:25 home-assistant hass[11351]:     result = self.fn(*self.args, **self.kwargs)
May 15 15:41:25 home-assistant hass[11351]:   File "/root/homeassistant/lib/python3.6/site-packages/homeassistant/components/verisure/__init__.py", line 68, in setup
May 15 15:41:25 home-assistant hass[11351]:     HUB = VerisureHub(config[DOMAIN], verisure)
May 15 15:41:25 home-assistant hass[11351]:   File "/root/homeassistant/lib/python3.6/site-packages/homeassistant/components/verisure/__init__.py", line 114, in __init__
May 15 15:41:25 home-assistant hass[11351]:     self.jsonpath = jsonpath.jsonpath
May 15 15:41:25 home-assistant hass[11351]: AttributeError: module 'jsonpath' has no attribute 'jsonpath'

Attempting to upgrade jsonpath:
(homeassistant) root@home-assistant:~/homeassistant# pip install --upgrade jsonpath
Collecting jsonpath
Installing collected packages: jsonpath
  Found existing installation: jsonpath 0.75
    Uninstalling jsonpath-0.75:
      Successfully uninstalled jsonpath-0.75
Successfully installed jsonpath-0.81

After a restart of hass, it's downgraded again:
(homeassistant) root@home-assistant:~/homeassistant# pip list|grep -i jsonpath
jsonpath                0.75

Let me know what else can be tested, and I'll post the output.

Tricky one...
I'm starting to suspect that HA don't load the module that it should, could there be a name collision?

Add the following line after include jsonpath  in verisures init file. _LOGGER.error('jsonpath module path, %s', jsonpath.__file__)
Check if the file that is logged is the jsonpath that we want to.

Start with a clean HA, and only add Verisure in the configuration.
If that works do test 1 again and see if it points to the same file as before.

May 16 15:31:20 home-assistant hass[26898]: 2019-05-16 15:31:20 INFO (MainThread) [homeassistant.setup] Setting up logger
May 16 15:31:21 home-assistant hass[26898]: 2019-05-16 15:31:21 ERROR (SyncWorker_17) [homeassistant.components.verisure] jsonpath module path, /root/homeassistant/bin/jsonpath.py
May 16 15:31:21 home-assistant hass[26898]: 2019-05-16 15:31:21 ERROR (MainThread) [homeassistant.setup] Error during setup of component verisure

That file looks like this:
#!/root/homeassistant/bin/python3.6
# -*- coding: utf-8 -*-
import re
import sys

from jsonpath_rw.bin.jsonpath import entry_point

if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])
    sys.exit(entry_point())

Could be some old override file?
I moved away that file, and it now seems to work.

@ways Seems like you have found a solution, but I do not know what the cause of that file ending up there is. Does anyone know where it comes from?

That's strange, I get a completely different error when I add the above code snippet.
2019-05-21 19:31:49 ERROR (MainThread) [homeassistant.setup] Error during setup of component verisure Traceback (most recent call last):   File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/setup.py", line 156, in _async_setup_component     component.setup, hass, processed_config)  # type: ignore   File "/usr/local/lib/python3.6/asyncio/futures.py", line 331, in __iter__     yield self  # This tells Task to wait for completion.   File "/usr/local/lib/python3.6/asyncio/tasks.py", line 244, in _wakeup     future.result()   File "/usr/local/lib/python3.6/asyncio/futures.py", line 244, in result     raise self._exception   File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 55, in run     result = self.fn(*self.args, **self.kwargs)   File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/verisure/__init__.py", line 67, in setup     _LOGGER.error('jsonpath module path, %s', jsonpath.__file__) NameError: name 'jsonpath' is not defined

@AndreasAhrens did you copy paste the wrong error message. Is this for a xiaomi_aqara component? I'm reading on my phone so I might miss something...

Verisure was working. Did (1) some non-related configuration changes, and (2) updated some pip packages (re-installed homeassistant-cli). Having restarted HA, I got the same errors as reported earlier in this thread (AttributeError: module 'jsonpath' has no attribute 'jsonpath' etcetera.)
Running homeassistant 0.97.2 on hassbian (buster).

Can confirm removing $HASERVERDIR/bin/jsonpath.py resolved the issue for me, too.

authors: AndreasAhrens krissen persandstrom pitah81 ways


text:
After clik on any link in Configuration screen it extend itself, but not displaying new page

Home Assistant release with the issue:

0.90
Last working Home Assistant release (if known):
0.89
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io
Component/platform:

Description of problem:
After cliking on any link in Configuration screen it extend itself, but not displaying new page
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:
You can see animated .gif file posted on forum: https://community.home-assistant.io/t/0-90-remote-ui-streams-user-groups/106670/128

Can confirm I'm experiencing the same bug with 0.90 (Docker). Here's a sample of the problem (rendered with Firefox):
https://community.home-assistant.io/t/0-90-remote-ui-streams-user-groups/106670/150


text:
TypeError: undefined is not an object (evaluating 'window.webkit.messageHandlers.externalBus.postMessage')

Home Assistant release with the issue:
0.92.1
Last working Home Assistant release (if known):
0.91.x
Operating environment (Hass.io/Docker/Windows/etc.):

arch
x86_64

dev
false

docker
true

hassio
false

os_name
Linux

python_version
3.7.3

timezone
Europe/Zurich

version
0.92.1

virtualenv
false

mode
storage

resources
4

views
12

Component/platform:
n/a
Description of problem:
Same error in log, multiple times.
2019-04-27 18:51:17 ERROR (MainThread) [frontend.js.latest.201904240] https://IP/frontend_latest/chunk.4e658893eb3987694e23.js:1:973 TypeError: undefined is not an object (evaluating 'window.webkit.messageHandlers.externalBus.postMessage')
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
n/a
Traceback (if applicable):
n/a
Additional information:

This is a front-end issue, what is your browser version?

This has to do with iOS app and a fix was submitted and merged already. Here is the bug fix PR I think: https://github.com/home-assistant/home-assistant-polymer/pull/3130
So I would assume it will probably be included in 0.92.2 or something.

authors: SeanPM5 WhistleMaster awarecan


text:
Yeelight is picked up by discovery (even with ignore enabled)

Home Assistant release with the issue:
arch: armv7
channel: stable
hassos: "2.12"
homeassistant: 0.101.2
hostname: hassio
logging: info
machine: raspberrypi3
supervisor: "192"
supported_arch:
- armv7
- armhf
timezone: Europe/Amsterdam

Last working Home Assistant release (if known):
0.98.x
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Integration:
discovery
Description of problem:
My Yeelight still being picked up by discovery. Even if I add yeelight to the discovery ignore list.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
discovery:
  ignore:
    - yeelight
    - apple_tv

Traceback (if applicable):

Additional information:
I use packages to include intergrations in my Home Assistant.

Issue still exists in version 0.102.0

Still broken in 0.105.5

The same behavior also in lates 108.8. Yeelight still found as home kit also if is it impossible to add trought this component.

authors: PAOLIG mikeage rgruyters


text:
Pushover name is no longer optional

I am using Home Assistnant 0.100.3 and my issue is with the pushover integration.
Since 5 november pushover does not work anymore for me. The first not working version is probably version 0.100.0.
I found the reason. In the configiration.yaml file, pushover is defined with:
notify:

name: NOTIFIER_NAME
platform: pushover
api_key: YOUR_API_KEY
user_key: YOUR_USER_KEY

The "name:" parameter is optional and defaults to "notify". I did not specify the "name:", and did send notifies with "notify.notify". This stopped working.
The name:" parameter is no longer optional, you have to specify it. It does not complain, but it does not work either. When sending a pushover message with "notify.notify" nothing happens. There is nothing on the logfiles and noting in the history and noting is received.
When a specify the "name:" as "pushover" and send a pushover message with "notify.pushover" it does work.
So my conclusion is that the "name:" parameter is no longer optional.
I did use a Raspberry PI 3B with Raspbian and a HA installation. The problem started there.
I now use a Raspberry PI 4B 2G with Hass.io (193). I had the same problem here, and now worked around it.
configuration.yaml.txt

@kgroot have you tried to update to newest version of HA?

@kgroot Have you added any other notify components to your config? As I understand it, the name config option is something which is part of the base notify component and not a specific platform, like Pushover. I believe this means that the default for any platform is "notify" and so, if you had added another notify platform to your config and that also didn't have the name option set, they could both potentially try to register their services as "notify.notify" and cause issues.

@springstan I am using the latest version of HA: 0.100.3. The problem started a few versions back, probably around the 0.100.0 version.
@gadgetchnnel You have a point. In the startup logging I see another notify:
2019-12-21 21:19:03 INFO (MainThread) [homeassistant.components.notify] Setting up notify.pushover
2019-12-21 21:19:05 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.samsungtv
2019-12-21 21:19:05 WARNING (MainThread) [homeassistant.components.mqtt] Data in your config entry is going to override your configuration.yaml: {'broker': '127.0.0.1', 'discovery': True, 'password': ***, 'port': 1883, 'username': ***}
2019-12-21 21:19:06 INFO (MainThread) [homeassistant.components.notify] Setting up notify.mobile_app
2019-12-21 21:19:10 INFO (MainThread) [homeassistant.components.automation] Initialized trigger X-Mas - Light on in the morning
I did not specify this as a notify, but it seems to be a notify entry anyway. This could even be my issue, then I added this mobile_app entry around the point where pushover messages stopped working. I did not make the connection, but this could very well be the cause. I think you solved my isuue! Thanks.

authors: gadgetchnnel kgroot springstan


text:
SynologyDSM integration doesn't handle 2-step authentication

The problem

I'm trying to enable synologyDSM integration on my NAS that has 2-step authentication.
Doesn't work out of the box, but I found the right calls to handle this.
Environment

Home Assistant release with the issue: 0.104.3
Last working Home Assistant release (if known): none
Operating environment (Hass.io/Docker/Windows/etc.):  Docker
Integration causing this issue:  synologydsm
Link to integration documentation on our website: -

Problem-relevant configuration.yaml

sensor:
  - platform: synologydsm
    host: !secret synology_addr
    port: 443
    username: !secret synology_login
    password: !secret synology_pwd
    monitored_conditions:
      - cpu_total_load
      - memory_real_usage
      - disk_smart_status
      - network_up

Traceback/Error logs

2020-01-27 00:36:20 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 284, in async_update_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 320, in _async_write_ha_state
    state = self.state
  File "/usr/src/homeassistant/homeassistant/components/synologydsm/sensor.py", line 235, in state
    return round(attr / 1024.0, 1)
TypeError: unsupported operand type(s) for /: 'NoneType' and 'float'

Additional information
Removing "-network_up" I don't have any more errors in log, but all sensors report nothing; they are seen as "- %" in UI.
I found that 2-step auth is not handled by the plugin.
Steps to fix:
query Auth API using:
https://nasdnsname/webapi/query.cgi?api=SYNO.API.Info&version=1&method=query&query=SYNO.API.Auth
If "maxVersion" is >=3 (mine is 6) then OTP code can be used.
So the authorization call would be:
https://nasdnsname/webapi/auth.cgi?api=SYNO.API.Auth&version=6&method=login&account=admin&passwd=password&session=Core&format=cookie&otp_code=OTPCode&enable_device_token=yes
using "enable_device_token" all fuure calls to avoid the need of the OTP code ;-)
Integration should be enabled by UI and ask if OTP is active or not (maybe there is a API even for that). If it is, ask for the OTP code and perform the first query.
From now on I expect the code to be the same as before.
Available for testing a new version of the integration.
Simone

Will look into it during #31030.
I'll test on DSM 6 with and without 2 step auth.
I will let you know, or subscribe to the PR.
Thanks for reporting !

Hi,
got an official answer from Synology support:
Step 1. Login with OTP and enable device token
query:
GET / HTTP/1.1
  webapi/auth.cgi
  ?api=SYNO.API.Auth&version=6&method=login&enable_device_token=yes&otp_code={otp_code}&account={account}&passwd={passwd}&device_name={device_name}

answer:
HTTP/1.1 200 OK
Content-type: text/plain;

{
   "data": {
       "did": "F0frflccRq3St5DERrmItae7C9HS5r6kR8VjfsqQWJv2bC3vCoYADD4q4OTzsvpOUahjZlIT46684G36ElKEYW12dApreP5lYyjaHSF8pH54SQnWIZZVaOrkSNtKNVT",
       "is_portal_port": false,
       "sid": "tMHwU7PPVGDAU1530LSN299702"
   },
   "success": true
}

Step 2. Login with device name and without OTP
query:
GET / HTTP/1.1
  webapi/auth.cgi GET HTTP/1.1
  ?api=SYNO.API.Auth&version=6&method=login&account=XXX&passwd=YYY&device_name=ZZZ&device_id=F0frflccRq3St5DERrmItae7C9HS5r6kR8VjfsqQWJv2bC3vCoYADD4q4OTzsvpOUahjZlIT46684G36ElKEYW12dApreP5lYyjaHSF8pH54SQnWIZZVaOrkSNtKNVT

answer:
HTTP/1.1 200 OK
Content-type: text/plain;

{
   "data": {
       "is_portal_port": false,
       "sid": "CujcTs2Wu7z3w1530LSN299702"
   },
   "success": true
}

Looking forward for your test ;-)
Simone

@Quentame did you get time to test ? :-)
Simone

In 4 days I will have 😉
Sent with GitHawk

In 4 days I will have 😉
Sent with GitHawk

May I test something ? 😇
Simone

Hi @chemelli74  !
4 days past, haven't seen them ! :man_facepalming: :sweat_smile:
But I was actually busy with iCloud and Synology DSM actually.
Right now we are not supporting 2-FA for Synology DSM, as you noticed.
Then, this is a feature request.
I precised the documentation accordingly on my component rework documentation PR:
https://github.com/home-assistant/home-assistant.io/pull/12597/files#diff-8d1d60502a5cdd9a7a22330a9f5efb39R89-R93
As you created an issue on the underlying library ProtoThis/python-synology#11 and HA feature request should only be on the forum https://community.home-assistant.io/c/feature-requests , I'm closing the issue here.
Best regards, and see you there ProtoThis/python-synology#11


text:
Extend websocket method usage to port 8002 in Samsung TV media player #17802

Description:
Related issue (if applicable): #17802
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Hi @2sheds,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Thanks for accepting this but I purposely left out the "fixed" part - I don't believe this alone fixes the issue, it still requires the patched samsungctl library for SSL websockets support.


text:
Implement ToggleController, RangeController, and ModeController in alexa

Description:
Implement AlexaToggleController, AlexaRangeController, and AlexaModeController interfaces.
The addition of these 3 controllers allow for additional utterances, and more granular customization, using Alexa.
AlexaToggleController:
Used for entity attributes that support on/off, e.g. fan.oscillate

Alexa, turn on the ice maker.
Alexa, turn off eco mode.
Alexa, is oscillate on for the tower fan?

AlexaRangeController:
Used for custom ranges that don't support 100 points of a percentage. e.g. fan.speed

Alexa, set the bedroom fan speed to 7.
Alexa, set the fan speed on the bedroom fan to maximum.
Alexa, turn up the bedroom fan speed.
Alexa, decrease the fan speed on the bedroom fan by 3.
Alexa, what is the bedroom fan speed?

AlexaModeController:
Used for changing modes. e.g. fan.direction

Alexa, what is the wash setting on the washer?
Alexa, set the wash cycle to cottons.
Alexa, set the wash setting on the washer to normal.
Alexa, increase the water temperature on the washer.

Currently implemented each of the controllers for fan entities, supporting oscillation (toggle), direction (mode), and speed (range). All existing controllers, Power/PowerLevel/Percentage are still exposed. The additional controllers just allow for additional utterances, and support changing attributes using utterances.
This PR also implements the Alexa Global Catalog, to support common, friendly, and custom names for CapabilityResources. e.g. "Alexa, turn on fan swivel", "Alexa, turn on fan rotation"
Notes:

These 3 controllers required modifications to the discovery Discover.Response in the class.AlexaCapibility; Created the additional objects capabilityResources, configuration, instance, and nonControllable. Defaulted them to None to prevent them from being included when they are not set. I welcome any suggestions for improvement of how this is implemented in these classes.

Currently creation of the CapabilityResources must be hard coded for entities that can support these additional controllers. Each controller class has a method to define the capability resource configuration depending on the instance(attribute) defined for the controller.  I would like to transition the creation of these to the config. Users can then define each of the additional controllers for certain entities, and control the properties such as min, max range, custom names for attributes, etc.

Related issue (if applicable): checks off 3 boxes in #24579
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the [development checklist][dev-checklist]
[x] Tests have been added to verify that the new code works.

I would like to transition the creation of these to the config. Users can then define each of the additional controllers for certain entities

I think that that is not a good idea. We should make sure that all entities are exposed in a way that makes sense. By adding it a config option, each user needs to solve it themselves instead of having developers fix it once and for all.

@balloob Can you take another look at this? Let me know if there is anything else or if this is just on hold. Thanks!
I have other PRs I've been waiting to submit that expand off these controllers.

Looks good ! Takes some time to review a 1000 lines of code 🙈

authors: balloob ochlocracy


text:
Add influxdb cloud

Proposed change

Added support for the new v2 cloud version that influxdb added. Copy is a heavy port from existing influxdb component. This will require that you have registered an account https://cloud2.influxdata.com/signup and copy your bucket and org from there website.
Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[x] New integration (thank you!)
[ ] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml
influxdb_cloud:
  url: "https://eu-central-1-1.aws.cloud2.influxdata.com"
  token: "xxx"
  bucket: "xxx"
  org: "xxx"

Additional information

The easiest way to get your bucket and org token is to click on the default bucket that was created for your new account and then copy it out of the url.

Link to documentation pull request:
Doing documentation now..

Checklist

[x] The code change is tested and works locally.
[x] Local tests pass. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist
[x] The code has been formatted using Black (black --fast homeassistant tests)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

not sure how to get this?

[x] No score or internal
[ ] 🥈 Silver
[ ] 🥇 Gold
[ ] 🏆 Platinum

Maybe I misunderstand Influxdb Cloud, but is it not just another place to host influxdb? If so, why do we need a new component?

Agreed, but its build of there new v2 client. Its not just cloud specific, could be used for non cloud instances as well. They have changed the API and released a new client. https://github.com/influxdata/influxdb-client-python.
Could integrate it into the existing component, but the variables are different and if the new library introduces newer functionality then the complexity of keeping a single implementation could get out of hand. Other option is to just call this one influxdb_v2 ?
Open to suggestions?

I think this should be merged into our existing influxdb integration.
Add a configuration option that allows the user to choose between v1/v2 APIs (ideally autodetected of course).

authors: frenck potgieterdl rohankapoorcom


text:
No more sound output on Odroid N2+ after updating to Supervisor 2023.11.0

Describe the issue you are experiencing
Earlier this week my system updated to HA Supervisor 2023.11.0
Immediate the sound output of the board's 3.5mm output (via VLC addon as always) stopped working.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Steps to reproduce the issue

Update to Supervisor 2023.11.0
Play some sound on local audio output via VLC addon

Anything in the Supervisor logs that might be useful for us?
Logger: homeassistant.components.vlc_telnet
Source: components/vlc_telnet/media_player.py:62
Integration: VLC media player via Telnet (documentation, issues)
First occurred: 8 november 2023 om 20:31:21 (2 occurrences)
Last logged: 10:15:38
Connection error: Failed to read: 0 bytes read on a total of undefined expected bytes. Partial bytes read: b''

System Health information
System Information

version
core-2023.11.1

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.11.6

os_name
Linux

os_version
5.15.90

arch
aarch64

timezone
Europe/Amsterdam

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
5000

Installed Version
1.33.0

Stage
running

Available Repositories
1328

Downloaded Repositories
7

AccuWeather

can_reach_server
ok

remaining_requests
19

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 9.5

update_channel
stable

supervisor_version
supervisor-2023.11.0

agent_version
1.4.1

docker_version
20.10.22

disk_total
113.9 GB

disk_used
91.6 GB

healthy
true

supported
true

board
odroid-n2

supervisor_api
ok

version_api
ok

installed_addons
Samba share (10.0.2), Duck DNS (1.15.0), Home Assistant Google Drive Backup (0.111.1), NGINX Home Assistant SSL proxy (3.5.0), Node-RED (15.1.0), Plex Media Server (3.3.2), Advanced SSH & Web Terminal (15.1.0), WireGuard (0.9.0), AdGuard Home (4.8.17), VLC (0.2.0), Zigbee2MQTT (1.33.2-1), Mosquitto broker (6.3.1), chrony (2.6.2), ESPHome (2023.10.6), File editor (5.6.0), HomePod Connect (28.8-ls118), Whisper (1.0.0), Piper (1.4.0), Music Assistant BETA (2.0.0b74), openWakeWord (1.8.2)

Dashboards

dashboards
1

resources
2

views
10

mode
storage

Recorder

oldest_recorder_run
8 november 2023 om 18:04

current_recorder_run
8 november 2023 om 19:05

estimated_db_size
104.43 MiB

database_engine
sqlite

database_version
3.41.2

Supervisor diagnostics
config_entry-hassio-f9c2513652a4f6291037d6fa4f7c58d8.json.txt
Additional information
No response

Having the same problem here. Weirdly enough pulse is trying to recognize two audio devices that are both not found.
Audio log:
[...]  W: [pulseaudio] module-udev-detect.c: Failed to open /proc/asound/card1: No such file or directory W: [pulseaudio] module-udev-detect.c: Failed to open /proc/asound/card0: No such file or directory E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer: unit failed.

The fix is currently on the beta channel. You can update the Audio plug-in specifically using:
ha audio update --version 2023.12.0

You might need to restart the VLC add-on after that.

Cool it's fixed. Is this part of 2023.12.1 version of supervisor?

The audio plug-in is updated separately. The 2023.12.0 version of the audio plug-in is on the stable channel since a couple of days.

It's not fixed for me. I'm on 2023.12.0. Haven't rebooted the Odroid yet though and my OS is also still on 11.2, so maybe those are reasons.

OS 11.2 should not matter, but reboot might be the problem. If the problem still persists after reboot, double check the audio plug-in version (using ha audio info from the terminal).

For me the situation is the same as my last message in: https://github.com/home-assistant/plugin-audio/issues/157#issuecomment-1850170144
So some sounds work, but f.i. TTS towards the speaker generates no sound. I suspect it has to do with the nr of hz of the audio source.

@GoSpursGoNL what HAOS version are you on? You are using the N2+ as well correct?
I've just double checked on my end, running this service runs on HAOS 11.4 + Supervisor 2023.12.0 + Core 2024.1.2
service: tts.google_translate_say
data:
  cache: false
  entity_id: media_player.vlc_telnet
  message: This is a hello world

I am not aware in any changes in HAOS 11.4 which should affect audio. Out of curiosity I've also downgraded to 11.2, and the same service call seems to work fine here.
My ha audio info output:
# ha audio info
audio:
  application: []
  card:
  - driver: module-alsa-card.c
    index: 0
    name: alsa_card.platform-sound
    profiles:
    - active: true
      description: Analog Stereo Output
      name: output:analog-stereo
    - active: false
      description: Digital Stereo (HDMI) Output
      name: output:hdmi-stereo
    - active: false
      description: Digital Surround 5.1 (HDMI) Output
      name: output:hdmi-surround
    - active: false
      description: Digital Surround 7.1 (HDMI) Output
      name: output:hdmi-surround71
    - active: false
      description: "Off"
      name: "off"
  input: []
  output:
  - applications: []
    card: 0
    default: true
    description: Built-in Audio Analog Stereo
    index: 0
    mute: false
    name: alsa_output.platform-sound.analog-stereo
    volume: 1
host: 172.30.32.4
update_available: false
version: 2023.12.0
version_latest: 2023.12.0

Can you test this again and check/upload the following logs:
ha core logs
ha audio logs
ha supervisor logs
ha host logs --identifier kernel

I switched to the Odroid M1 in the meantime: https://github.com/home-assistant/plugin-audio/issues/157#issuecomment-1850170109
That service call you proposed (adjusted to use my entity id for the speaker media player) produces no sound.
If I let it get cached to a local audio file, where will it be put on my disk?
I like to check if I play that file to the speaker if it produces sound, check the bitrate, adjust and try again. I think this is the problem for me: https://github.com/home-assistant/plugin-audio/issues/157#issuecomment-1850170172
ha audio info:
audio:
  application: []
  card:
  - driver: module-alsa-card.c
    index: 0
    name: alsa_card.platform-hdmi-sound
    profiles:
    - active: true
      description: Stereo Output
      name: output:stereo-fallback
    - active: false
      description: "Off"
      name: "off"
  - driver: module-alsa-card.c
    index: 1
    name: alsa_card.platform-rk809-sound
    profiles:
    - active: false
      description: Stereo Input
      name: input:stereo-fallback
    - active: false
      description: Stereo Output
      name: output:stereo-fallback
    - active: true
      description: Stereo Output + Stereo Input
      name: output:stereo-fallback+input:stereo-fallback
    - active: false
      description: "Off"
      name: "off"
  input:
  - applications: []
    card: 1
    default: true
    description: Built-in Audio Stereo
    index: 2
    mute: false
    name: alsa_input.platform-rk809-sound.stereo-fallback
    volume: 1
  output:
  - applications: []
    card: 0
    default: false
    description: Built-in Audio Stereo
    index: 0
    mute: false
    name: alsa_output.platform-hdmi-sound.stereo-fallback
    volume: 1
  - applications: []
    card: 1
    default: true
    description: Built-in Audio Stereo
    index: 1
    mute: false
    name: alsa_output.platform-rk809-sound.stereo-fallback
    volume: 1
host: 172.30.32.4
update_available: false
version: 2023.12.0
version_latest: 2023.12.0

Attached the other files. Thanks for assisting!
ha audio logs.txt
ha core logs.txt
ha host logs identifier kernel.txt
ha supervisor logs.txt

I switched to the Odroid M1 in the meantime: #157 (comment)

Whoops, sorry, I've missed that. I'll have to test on my end.
I've created a new issue from your comment to track the M1 issue (#162).

authors: GoSpursGoNL agners spudje therealhammer

repo: home-assistant/plugin-audio


text:
Add cleaning mode to zone

Hello :)
thank you for this awesome plugin! I have been using it for years now with my S50 and it works great.
I recently upgraded to a S6 and called it Louisa. I let Louisa clean in a special order when leaving my home (start vacuuming under the kitchen table, go to the bathroom last when the droplets on the floor hopefully dried off and so on) which is easy to implement using zones. However, with Louisa being able to mop, I would like her to vacuum first and mop afterwards (if there is time left before I come home).
Is is possible to add a mode option (vacuum or mop respectively vacuum intensity and mopping intensity)? It would be great if it was a parameter set in the zone coordinates like the number of cleanings. This would enable the entire cleaning process with one switch in the home app.
Best
Jan

That sounds like a great usage!
It is possible to mop today with the waterMode option. However, I don't think this plugin allows to use zone cleaning with waterMode...
I'd need to figure out the actual command to do so. But if the app can do it, it should be doable as well.

authors: afharo nixmeer


text:
Patch 1

:recycle: Current situation
Describe the current situation. Explain current problems, if there are any. Be as descriptive as possible (e.g., including examples or code snippets).
:bulb: Proposed solution
Describe the proposed solution and changes. How does it affect the project? How does it affect the internal structure (e.g., refactorings)?
:gear: Release Notes
Provide a summary of the changes or features from a user's point of view. If there are breaking changes, provide migration guides using code examples of the affected features.
:heavy_plus_sign: Additional Information
If applicable, provide additional context in this section.
Testing
Which tests were added? Which existing tests were adapted/changed? Which situations are covered, and what edge cases are missing?
Reviewer Nudging
Where should the reviewer start? what is a good entry point?

Thanks!

repo: homebridge/homebridge-config-ui-x


text:
Add badges to Readme.md

Fixes #2

Hello there and thank you very much for submitting a PR! I am going to close this PR because it has some of the same issues as those in PR #3; not least because it would not make sense for me to accept this PR instead of #3, which is pending at the moment for the issues I find with it.
In any case, thank you very much again! I would be helpful in the future if you could at least indicate that you would like to tackle the issue—it's helpful for both yourself and others and so that no work is duplicated.

repo: honmanyau/ising


text:
Figure out a city based on the series

For Pyvo the city fills the role of series; it was Brno Pyvo even if
was actually in Bratislava. The series name on Lanyrd isn't very useful,
because the meetup name changes through time as we join forces with
other communities.

:snake:

authors: encukou honzajavorek

repo: honzajavorek/lanyrd-pyvo-pull


text:
🛑 FWAw is down

In 5a52923, FWAw ($FWA_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FWAw is back up in 0dcef01 after 16 minutes.

repo: hoopybe/uptime


text:
🛑 FWB is down

In 17ddf8d, FWB ($FWB_SITE) was down:

HTTP code: 403
Response time: 393 ms

Resolved: FWB is back up in 153fc0f after 13 minutes.


text:
🛑 TPB is down

In 5e2859c, TPB ($TPB_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TPB is back up in 43d149e.


text:
TCP interface

statsd from v0.8.0 introduced the support for a TCP listener. This is useful in a number of cases, and I think it'd be good to have it in this Docker image.
For now I've forked the repository,changed the Dockerfile so it clones statsd v0.8.0 instead of v0.7.2, and updated the statsd configuration in conf/opt/statsd/config.js. Ideally it would be nice to be able to specify on which interface statsd should listen when the container is run.
Any thoughts how this could be implemented? Let me know if you feel that a PR for that would be useful.

PR in #91

repo: hopsoft/docker-graphite-statsd


text:
CDPD-3643 - Configure DAS in DE template.

Adding DAS in DE template.
Fix DAS service name in ExposedServices.
Fix Tez proto base directory in DE template.

Closes #6548
Closes #CDPD-3643

@harishjp checkstyle-main CI job failed, please fix it and then this should be ok

I have started a distrox cluster with these changes and with the modified bp, so LGTM

LGTM

authors: doktoric horadla23 szlta

repo: hortonworks/cloudbreak


text:
Created fluid-bootstrap theme with some initial components styled.

Revised package.json
Added FontAwesome to repo
Cleaned up project structure
Started theming and extending Bootstrap 4 for Fluid:

Overrode default variables and added new ones as needed.
Implemented styles for the following components:

Theme type and colors
Accordion
Alerts (aka snackbars)
Badges (including icons with badges)
Breadcrumbs
Buttons (including groups and pagination)

During the npm install I got the following error message:
found 53 vulnerabilities (18 low, 20 moderate, 14 high, 1 critical)
run `npm audit fix` to fix them, or `npm audit` for details

I think we should fix them to have a clear start.

Is there any reason why do we have variables in our _variables.scss which are not overridden? We can make our _variables.scss file more readable and shorter.

To address Toby's comments for the record:

I am working on resolving the npm audit items. This entails upgrading several packages, including moving Gulp up to ~v4. This seems to be incompatible with gulp-livereload-server, which is also the source of the remaining, not auto-fixable audit failures, so I am looking for a substitute.

For development purposes, I found it much easier to include all of the default variables in the customized file and then remove !default on the ones I need to override. We can remove all the !default values at some point in the future before we release, if everyone thinks that would be better.

authors: jgolieb tobias-istvan

repo: hortonworks/fluid-bootstrap-theme


text:
Exclure les fichiers statiques public/xxx.html de sonarcloud

Contexte / Problème
Dans le github action issue de sonarcloud, on se retrouve avec du duplicate code se trouvant dans les fichiers :

public/404.html
public/422.html
public/500.html

Cependant ces fichiers sont full statiques donc c'est normal que de la duplication soit présente.
Proposition
Apparament dans la config on peut rajouter des fichiers à exclure pendant l'analyse :

Priorité (Requis)

P3: Pas prioritaire

Je me permets de mettre ça en P3

authors: mininao navidemad

repo: hostolab/covidliste


text:
Rejection history not showing

Current behavior

Item is not showing rejection history when adding items to count:

https://dev-oms.hotwax.io/commerce/control/ViewOrder?orderId=10390

Count ID:
100663

We will pick this once the api will have support for returning rejection history of items.

Until then we should hide this from UI then

Verified and working fine in release v2.0.0. Hence, closing it.

repo: hotwax/inventory-count


text:
Force a redirect of the entire window

We use an external Auth provider, and if someone gets signed out of our app, subsequent fetch requests result in CORS violations, because Turbo (Drive and Frames) try to fetch the location from the "you're now signed out, please sign in again" redirect. This applies both to GET requests and to form submissions.
Similar to the way Turbo Drive lets you trigger a whole page refresh via the turbo-visit-control meta tag, I'm wondering if there can be a way to tell Turbo to handle redirects via window.location.href = response.location, perhaps via a Turbo-Redirect: window response header.

Now that I have read more of the docs, I'm actually wondering if this is a bug:

By default, Turbo Drive only loads URLs with the same origin—i.e. the same protocol, domain name, and port—as the current document. A visit to any other URL falls back to a full page load.

This applies to links clicked, but doesn't seem to be applying to redirects coming from visit requests.

Turbo should detect this and do a full page redirect. If anyone wants to look into that, please go ahead!

That's good know that it shouldn't be trying to fetch another host. I'll try to dig into more.

I think this is an issue with the fetch API itself. Fetch does not give you the ability to inspect the Location header on a redirect, so there is no way to prevent a CORS request from happening if you wanted to visit another host. I can work around this in Rails using the turbo event listeners and a custom status code. The custom status code prevents the fetch api from trying to handle the redirect, allowing my turbo event listener to inspect the Location header to determine what to do:

document.addEventListener("turbo:before-fetch-response", function (e) {
  const locationHeader = e.detail.fetchResponse.response.headers.get("Location") || "";
  if (locationHeader && !locationHeader.startsWith(window.location.origin)) {
    e.preventDefault();
    window.Turbo.visit(locationHeader);
  }
});

And the rails response (I left the custom status code in the 3xx range to attempt a semantic meaning):
class UsersController
  def create
    redirect_to "https://github.com", allow_other_host: true, status: 309
  end
end

Hmm, yeah, that's not easy. Could consider something like a custom parameter that could trigger the full redirect and then be stripped? Like ?_turbo_full_redirect=true.

Looking for a solution to this too, I'm using data-turbo="false" for now.

I think this is an issue with the fetch API itself. Fetch does not give you the ability to inspect the Location header on a redirect, so there is no way to prevent a CORS request from happening if you wanted to visit another host. I can work around this in Rails using the turbo event listeners and a custom status code. The custom status code prevents the fetch api from trying to handle the redirect, allowing my turbo event listener to inspect the Location header to determine what to do:

I implemented the same workaround but I have noticed it's not working with Safari, i.e. the browser is following the redirect irrespective of the status code used (309).

Has anyone found a solution to this bug? The suggested workaround (disabling turbo) doesn't work in my case because I'm using Turbo in case of failure.

We use a workaround in a Symfony project with a custom turbo stream action.
We have a listener that checks if the request is made with turbo and the response is an external redirect. In that case, we override the given  response with a new one rendering the following turbo-stream:
<turbo-stream
    action="redirect"
    data-url="{{ url }}"
    {% if timeout is defined %} data-timeout="{{ timeout }}" {% endif %}
></turbo-stream>

The custom stream action is defined in a controller connected to the page body.
import { Controller } from '@hotwired/stimulus';
import { StreamActions, visit } from "@hotwired/turbo";
export default class extends Controller
{
    connect()
    {
        StreamActions.redirect = function () {
            setTimeout(() => visit(this.getAttribute('data-url')) , parseInt(this.getAttribute('data-timeout') ?? 0));
        }
    }
}

Hi @ajgarlag, I'd also be interested, as I'm also using Hotwired Turbo within a Symfony project. However, I didn't really understand your workaround. The HTTP code 300 is Multiple Choices; what does this have to do with a redirect? If I understand well, your workaround force the redirect as expected ?
Would you be willing to share your listener here?

@Crovitche-1623 I chose the 300 HTTP status code because I wanted to represent the redirection intent, but I didn't want the browser to follow the redirection automatically.
The listener is available at https://gist.github.com/ajgarlag/69e3586a754728ff52e4470a61382eec#file-redirectresponsetoturbostreamlistener-php

@Crovitche-1623 Please, send me your feedback about the listener in the gist comments to avoid spamming this issue.

authors: Crovitche-1623 agrobbin ajgarlag bilogic devaniljr dhh dillonhafer iamFIREcracker

repo: hotwired/turbo


text:
Resolve Turbo Frame navigation bug

The scenario
Imagine a List-Details style page layout, with navigation links on the left and the contents of the page on the right:
<turbo-frame id="list">

    Article #1

    <turbo-frame id="preview_article_1" src="/articles/1/preview">
      Some preview text
    </turbo-frame>

  Next Page
</turbo-frame>

<turbo-frame id="details">

Details

</turbo-frame>

The #list element is a <turbo-frame> to handle pagination, and the #details element is a <turbo-frame> as well. The  elements within the #list frame drive the #details frame through their [data-turbo-frame="details"]. The  element nests a third kind of <turbo-frame> that is specific to the resource being linked to. It asynchronously loads in preview content with a [src] attribute.
The problem
Clicking the Article #1 text within the  element drives the #details frame as expected.
However, clicking the Some preview text within the  element's nested <turbo-frame> element navigates the entire page.
This is demonstrated in the following reproduction script:

Copy-paste into `bug.rb`, then execute `ruby bug.rb`
require "bundler/inline"

gemfile(true) do
  source "https://rubygems.org"

  git_source(:github) { |repo| "https://github.com/#{repo}.git" }

  gem "rails"
  gem "propshaft"
  gem "puma"
  gem "sqlite3"
  gem "turbo-rails"

  gem "capybara"
  gem "cuprite", "~> 0.9", require: "capybara/cuprite"
end

ENV["DATABASE_URL"] = "sqlite3::memory:"
ENV["RAILS_ENV"] = "test"

require "active_record/railtie"
require "action_controller/railtie"
require "action_view/railtie"
require "action_cable/engine"
require "rails/test_unit/railtie"

class App < Rails::Application
  config.load_defaults Rails::VERSION::STRING.to_f

  config.root = __dir__
  config.hosts << "example.org"
  config.eager_load = false
  config.session_store :cookie_store, key: "cookie_store_key"
  config.secret_key_base = "secret_key_base"
  config.consider_all_requests_local = true
  config.action_cable.cable = {"adapter" => "async"}
  config.turbo.draw_routes = false

  Rails.logger = config.logger = Logger.new($stdout)

  routes.append do
    root to: "application#index"
  end
end

Rails.application.initialize!

ActiveRecord::Schema.define do
  create_table :messages, force: true do |t|
    t.text :body, null: false
  end
end

class Message < ActiveRecord::Base
end

class ApplicationController < ActionController::Base
  include Rails.application.routes.url_helpers

  class_attribute :template, default: DATA.read

  def index
    render inline: template, formats: :html
  end
end

class ApplicationSystemTestCase < ActionDispatch::SystemTestCase
  driven_by :cuprite, using: :chrome, screen_size: [1400, 1400], options: {
    js_errors: true,
    headless: false
  }
end

Capybara.configure do |config|
  config.server = :puma, {Silent: true}
  config.default_normalize_ws = true
end

require "rails/test_help"

class TurboSystemTest < ApplicationSystemTestCase
  test "reproduces bug" do
    visit root_path

    binding.irb
    click_link "Drive #details to ?key=1"
  end
end

__END__

<!DOCTYPE html>

    <%= csrf_meta_tags %>

    <meta name="turbo-prefetch" content="false">

    <turbo-frame id="list">
      <% 1.upto(5).each do |key| %>
        <%= link_to({key:}, data: {turbo_frame: "details"}) do %>
          <turbo-frame id="frame_<%= key %>">
            Drive #details to <%= {key:}.to_query %>
          </turbo-frame>
        <% end %>
      <% end %>
    </turbo-frame>

    <turbo-frame id="details">
      <%= params.fetch(:key, "0") %>
    </turbo-frame>

The solution
When observing click events, utilize the findLinkFromClickTarget to find the nearest  element to the click target so that that element's ancestors are used to determine which <turbo-frame> to target instead of risking the possibility of using one of its descendants.

@afcapel could you review this change?

@jorgemanrubia are you able to review this change?


text:
Add Flake8 Python linter

This would replace the https://github.com/houndci/python repo.

🍔

@gylaz When this deploys, could you add a note do houndci/python stating that it's no longer used. Or, can we delete it?

authors: gylaz jayroh teoljungberg

repo: houndci/linters


text:
Integrating Wordhop plugin

Wordhop provides a toolkit to monitor bots for problems and take over
live. Visit https://www.wordhop.io/ to add Wordhop to Slack and start
getting alerts.

Closing the PR for now. Caught a potential bug.

repo: howdyai/botkit-starter-slack


text:
dsync and dcp: allow user to control syncing of xattrs

Rather than always copying xattrs, introduce a new option
"--xattrs | -e" to allow the user to control how this is done.
Options are
"none"        Copy no xattrs
"all"         Copy all xattrs (prior default)
"non-lustre"  Copy non-lustre xattrs (new default)
"libattr"        Copy xattrs not indicated as "skip" in /etc/xattr.conf
Copying xattrs is now independent of --preserve for owner, perms,
etc.
Lustre uses xattrs to record important information such as how the file
data should be distributed among the Lustre servers.  As a result,
copying the lustre xattrs prevents certain default values from taking
effect.
If "non-lustre" option is in effect, xattrs named in lustre
source file lustre_idl.h as of this writing are not synced (see
XATTR_NAME_SOM and friends).  In addition, xattrs with prefix
"lustre" are not synced.
Signed-off-by: Olaf Faaland faaland1@llnl.gov

@ofaaland , there are too many issues to track.  No problem that you weren't aware.  I just wanted to list them here because your work here will help address them.
We can also add these separately in dcp if you want.
We still have dcp1 and dcp because they implement two different algorithms.  Depending on the situation, one can be faster than the other.  Eventually, it'd be nice to roll both algorithms into one tool, but that's still future work.

Thanks again @ofaaland .  Sorry to be so tardy on this.  Great work.  I found a few things to check, but otherwise it looks good.
We use sphinx to generate our man pages from the rst files.  I can help you set that up.

Hi @adammoody , I fixed up the issues you found, and also added a test.  I ran the test bash file by hand, rather than using nose2 and the python test-runner because I'm not sure how it works - but it should work, I've included a python wrapper copied from the dcp test.
I found doc/README.md and followed the instructions to setup and run Sphinx.  It ran, and it updated the man pages to reflect my .rst updates, but it also made a bunch of markup changes that are unrelated to my work.  So perhaps the version of Sphinx is different or there's some other Sphinx configuration I haven't done.  Here's an example:
 .TP
 .B \-b, \-\-blocksize SIZE
 Set the compression block size, from 1 to 9.
-Where 1=100kB <E2><80><A6> and 9=900kB. Default is 9.
+Where 1=100kB ... and 9=900kB. Default is 9.
 .UNINDENT
 .INDENT 0.0
 .TP

Because I don't know the reason for those markup changes, I've discarded the changes Sphinx made for now.  Let me know how to proceed.
Thanks!

dsync test output:
Testing dsync
PASSED verify of option none for /mnt/xfs/dest type xfs
PASSED verify of option all for /mnt/xfs/dest type xfs
SKIPPED verify of option non-lustre
PASSED verify of option libattr for /mnt/xfs/dest type xfs

Thanks @ofaaland .  That's great!
I just gave you a couple of files that I used to install sphinx and then build the man pages.  It's been a while since I tried myself, so it could just be due to a newer sphinx version like you say.
We could also merge without the changes to the man files and generate the new man pages in a later commit if you want.  I often only update the rst files in my commits and forget all about needing to regenerate the man pages until we stamp a new release.

OK, I fixed up those issues, removed a couple of whitespace issues that snuck in, and hand-tested dcp to make sure -X works.  I think it's ready to go.
I think it makes sense to update the man pages in a separate commit, in case there are other unrelated man page changes.  But I'll take your sphinx files and see if I still get markup changes.
Thanks @adammoody

Looks like the markup changes are not due to the process I followed - I get the same results using your scripts.  There is at least one other content change (for DAOS) to the .rst files that isn't yet reflected in the man pages, so I think a man-page-only commit makes sense.

Thanks, @ofaaland .  This is good to go, but we've got a conflict on some rst files due to a change that snuck in.  Would you please update to resolve those, and then we can merge?

Thanks @adammoody.  Rebased on master and fixed the conflicts.

Really nice addition, @ofaaland !

authors: adammoody ofaaland

repo: hpc/mpifileutils


text:
[FEATURE]: Expotential Moving Average (EMA)

Describe the feature
The EMA is used to train many models, an example can be found here: https://github.com/CompVis/latent-diffusion/blob/main/ldm/modules/ema.py
But with model sharding it is unclear how to implement ema properly. It would be really nice to have a sample to showcase how to implement ema properly in Colossal AI.

https://github.com/hpcaitech/ColossalAI/blob/main/examples/images/diffusion/ldm/models/autoencoder.py#L11
We have updated a lot. This issue was closed due to inactivity. Thanks.

authors: binmakeswell taoisu

repo: hpcaitech/ColossalAI


text:
Sa 176 - Added DeleteVolume function and renamed the existing DeleteVolume to DeestroyVolumee

Fix :
Added DeleteVolume which doesnt make the volume offline and tries to delete the volume . It is expected from user to ensure volume is offline . wherein DestroyVolume makes the volume offline prior to delete .

Please add ckallianpur to review the fakeservice code.

Please add ckallianpur to review the fakeservice code.

This is not fakeservice changes

Please add ckallianpur to review the fakeservice code.

This is not fakeservice changes

Was the fakeservice code included in this PR by mistake?

Please add ckallianpur to review the fakeservice code.

This is not fakeservice changes

Was the fakeservice code included in this PR by mistake?

seems like fakeservice is included by mistake. will removed it from this PR

authors: rkumpf vidhutsingh

repo: hpe-storage/nimble-golang-sdk


text:
Enables drag and drop of annotated methods in Babylonian Browser

Drag and drop was previously only functioning for methods without annotations, since they are CompiledMethods instead of CSLayeredMethods. The BPBrowser, as a subclass of Browser, handled drag and drop only for CompiledMethod. Seeing as the CSBrowser supports drag and drop for CSLayeredMethods, the BPBrowser has been added support for CSLayeredMethod the same as CSBrowser does

Pull Request Test Coverage Report for Build 1180113465

0 of 20 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 65.964%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/Babylonian-UI.package/BPBrowser.class/instance/wantsMessageCategoriesDrop..st
0
4
0.0%

packages/Babylonian-UI.package/BPBrowser.class/instance/dropOnMessageCategories.at..st
0
16
0.0%

Totals

Change from base Build 1157840160:
-0.2%

Covered Lines:
5291

Relevant Lines:
8021

💛  - Coveralls

Is it also possible to drag annotated methods from a message list into the world, which should open a CodeHolder window with this?

Is it also possible to drag annotated methods from a message list into the world, which should open a CodeHolder window with this?

Hey Christoph, I was only assigned to enable drag 'n drop recategorization - therefore dragging into the world was not considered yet. If you desire this feature, feel free to open an issue and notify Patrick about it. Then it's likely I will do it soon

therefore dragging into the world was not considered yet

It already seems to work, I hadn't tested before, everything is fine :)

therefore dragging into the world was not considered yet

It already seems to work, I hadn't tested before, everything is fine :)

Have to correct my previous statement: CS-layered methods cannot be dragged into the world, or more concretely, no CodeHolder is opened then. But I think this needs to be fixed in ContextS directly. See PasteUpMorph>>dropSourceCode:event: [break]. @codeZeilen Should CSLayeredMethod override either #isMethodReference or #isCompiledMethod=

authors: JoeAtHPI LinqLover coveralls


text:
Add parameter in the qr code

As a dev, I want to be able to tell if a user is search this item site or came from the qr code. This has implications for the lending process.
Dependencies
Depends on:

#11

Acceptance criteria

[ ]  There is the parameter "src=qrcode" in the url after scanning the qr code

Storypoints
1

@DefineDan noticed that currently the "borrow" button won't be displayed after scanning a qrcode since the URL parameter provided and the one we check for (implemented in #99) don't match.
@FSadrieh Since it was in the acceptance criteria of this issue, could we re-open this (or open a new issue) so that the qrcode URL contains src=qrcode instead of source=qrcode?

authors: FSadrieh richartkeil


text:
Add location picker for rooms, buildings and locations

As a user I want to be able to pick a location on the map when adding a room, building or location so that I don't have to find out the geocoordinates.
Acceptance:

[ ] In the editors for rooms, buildings and locations there is a button for "select location on map"
[ ] When clicking the button, the map opens and the user can place a marker
[ ] When a marker is placed the editor opens again, with the marker's position entered


text:
Fix: Mobile friendly position tracking switch

This closes #234. We moved the position tracking switches below the language switch, which should make them visible on mobile devices.

We also tried replacing the switches by buttons and displaying them as Leaflet controls on the left side, but this turned out to be very complicated, so we did not implement it, since we have only a few days left for the project.

Nice icons!
Two things:

While this now looks right on some phones, my phone still displays the "HPI Navigator" inside the plus and minus buttons. This can be reproduced in Firefox "Responsive design mode" with the "Galaxy S20 Linux" preset, which has a similar aspect ratio. I am not sure if this is in your scope here though
The switches themselves are cached on Firefox, which means that the page may have them enabled when loading; in the MDN, they link to this SO answer, it would be nice if you could clean this / my mess ;D

Other than that, nothing I can complain about :)

authors: laugengebaeck niklasmohrin


text:
Incorrect cmdline default mapping for <S-Tab>

FAQ

[X] I have checked the FAQ and it didn't resolve my problem.

Issues

[X] I have checked existing issues and there are no open or closed issues with the same problem.

Neovim Version
0.7
Minimal reproducible full config
if has('vim_starting')
  set encoding=utf-8
endif
scriptencoding utf-8

if &compatible
  set nocompatible
endif

let s:plug_dir = expand('/tmp/plugged/vim-plug')
if !filereadable(s:plug_dir .. '/plug.vim')
  execute printf('!curl -fLo %s/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim', s:plug_dir)
end

execute 'set runtimepath+=' . s:plug_dir
call plug#begin(s:plug_dir)
Plug 'hrsh7th/nvim-cmp'
Plug 'hrsh7th/cmp-buffer'
Plug 'hrsh7th/cmp-nvim-lsp'
Plug 'hrsh7th/vim-vsnip'
Plug 'neovim/nvim-lspconfig'
call plug#end()
PlugInstall | quit

" Setup global configuration. More on configuration below.
lua << EOF
local cmp = require "cmp"
cmp.setup {
  snippet = {
    expand = function(args)
      vim.fn["vsnip#anonymous"](args.body)
    end,
  },

  mapping = {
    ['<CR>'] = cmp.mapping.confirm({ select = true })
  },

  sources = {
    { name = "nvim_lsp" },
    { name = "buffer" },
  },
}

cmp.setup.cmdline(':', {
  mapping = cmp.mapping.preset.cmdline(),
  sources = cmp.config.sources({
    { name = 'path' }
  }, {
    { name = 'cmdline' }
  })
})

EOF

lua << EOF
local capabilities = require('cmp_nvim_lsp').update_capabilities(vim.lsp.protocol.make_client_capabilities())

require'lspconfig'.cssls.setup {
  capabilities = capabilities,
}
EOF

Description
Pressing <S-Tab> performs the same action as <Tab>, even though separate functions are called. This is due to https://github.com/hrsh7th/nvim-cmp/blob/baa8646c248486fdd46e8a087ae5623165901b9f/lua/cmp/config/mapping.lua#L65
Steps to reproduce
:P<tab> brings up the default wildmenu (not configured with cmp). Pressing tab again will cycle to next entries.
Expected behavior
Pressing shift tab should move you to previous entries.
Actual behavior
Pressing shift tab cycles you to next entries (same as Tab)
Additional context
Also, just noticed this from the README, but is there a difference between the cmp.config.sources call in https://github.com/hrsh7th/nvim-cmp/blob/baa8646c248486fdd46e8a087ae5623165901b9f/README.md#L112 and https://github.com/hrsh7th/nvim-cmp/blob/baa8646c248486fdd46e8a087ae5623165901b9f/README.md#L120?

PR welcome

Done! This fixes it for me but I'll let you check if it breaks anything else.

In my environment, it will insert <S-Tab> literally...

@hrsh7th I was able to produce a minimal config with this behaviour (wildoptions=tagfile). Perhaps the lack of pum option breaks this.
if has('vim_starting')
  set encoding=utf-8
endif
scriptencoding utf-8

if &compatible
  set nocompatible
endif

let s:plug_dir = expand('/tmp/plugged/vim-plug')
if !filereadable(s:plug_dir .. '/plug.vim')
  execute printf('!curl -fLo %s/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim', s:plug_dir)
end

execute 'set runtimepath+=' . s:plug_dir
call plug#begin(s:plug_dir)
Plug 'hrsh7th/nvim-cmp'
Plug 'hrsh7th/cmp-buffer'
Plug 'hrsh7th/cmp-nvim-lsp'
Plug 'hrsh7th/vim-vsnip'
Plug 'neovim/nvim-lspconfig'
call plug#end()
PlugInstall | quit

set wildmenu
set wildmode=full
set wildoptions=tagfile

" Setup global configuration. More on configuration below.
lua << EOF
local cmp = require "cmp"
cmp.setup {
  snippet = {
    expand = function(args)
      vim.fn["vsnip#anonymous"](args.body)
    end,
  },

  mapping = {
    ['<CR>'] = cmp.mapping.confirm({ select = true })
  },

  sources = {
    { name = "nvim_lsp" },
    { name = "buffer" },
  },
}

cmp.setup.cmdline(":", {
  mapping = cmp.mapping.preset.cmdline(),
  view = { entries = "wildmenu" },
  sources = {
    { name = "path" },
  },
})
EOF

lua << EOF
local capabilities = require('cmp_nvim_lsp').update_capabilities(vim.lsp.protocol.make_client_capabilities())

require'lspconfig'.cssls.setup {
  capabilities = capabilities,
}
EOF

Here's a demo for the behaviour.
https://user-images.githubusercontent.com/62098008/167357787-9b3d9f2a-3c66-4d9e-a674-41cd37b58699.mp4


text:
io.circe.generic.extras.auto._

Hi,
I migrated to the new akka-http-json version, and now looks like that with the new import
import de.heikoseeberger.akkahttpcirce.FailFastCirceSupport._ and import io.circe.generic.extras.auto._ my code is not compiling and I am getting:
could not find implicit value for parameter encoder
however when I replaced it with import io.circe.generic.auto._ , the code compiles.
Any know issues ?
thanks,

Never used ...extras. Why would you want to do that?

well, simply because it have extra stuff :-)
for example
implicit val customConfig: Configuration = Configuration.default.withSnakeCaseKeys which allow to control how the json keys would look like

@mazorigal not sure if that might help, but this is how I'm getting snake case:
A trait to be mixed in your routes:
https://github.com/prascuna/scala-pills/blob/master/04-sample-rest-service/src/main/scala/scalapills/sample/routes/JsonSupport.scala
and your Configuration inside your DTOs package object
https://github.com/prascuna/scala-pills/blob/master/04-sample-rest-service/src/main/scala/scalapills/sample/models/package.scala
I don't manually import FailFastCirceSupport._

Is this still an issue?

@prascuna Thanks,
I would try it.

authors: hseeberger mazorigal prascuna

repo: hseeberger/akka-http-json


text:
Extend slide on optional/any/variant

optional/any/variant would really benefit from a short example. the wording on the slides is correct but the students likely won't understand what it's useful for.

I can take this up (can't assign myself) so commenting here

authors: sponce theanalyst

repo: hsf-training/cpluspluscourse


text:
能否添加在页脚部分自定义内容的功能

如题，打算把站点放公网上，想在页脚位置添加ICP备案号，但不晓得咋个弄上去

一个比较笨的办法是ps背景图，把文字作为图片的一部分。不过这样备案链接是不能用的。

authors: EvanVV chenweiask

repo: hslr-s/sun-panel


text:
🛑 blog is down

In d95a3ea, blog (https://blog.imzhp.com) was down:

HTTP code: 502
Response time: 1049 ms

Resolved: blog is back up in 0e93358 after 8 hours, 12 minutes.

repo: htmambo/upptime


text:
Quit Button

Add a quit button so that users can quit user side and join a new game.

this is possible now through #379 - if the player taps their name, a menu appears with a "Quit" option.

repo: hto-projects/friendivia