ddev hostname should edit both WSL2 and Windows hosts file when used

Is there an existing issue for this?

[X] I have searched the existing issues

Run a Diagnostic and Paste Link Here
No response
Current Behavior
When using DDEV inside WSL and starting a new ddev project the first time ddev adds entries in the /etc/hosts file of the system to ensure the project.ddev.site domain can be resolved locally.
This does not work well on WSL as ddev is currently editing the hosts file inside WSL which is not exposed to the windows host, so accessing the website via a browser on the host system is not possible.
Additionally the WSL hosts file will be regenerated on every WSL start to pepresent the state of the windows one.
DDEV warns you about this fact by outputting:
You are on WSL2, so should also manually execute 'sudo ddev hostname some-project.ddev.site <IP_ADDRESS>' on Windows if you use a Windows browser.

This suggestion will only work if ddev is also installed on the windows host.
So you have to install ddev on Windows and inside WSL to be able to ensure the basic functionallity is working, wihtout the need to manually editing files.
Expected Behavior
I would expect ddev to work within WSL just as it does installed on a native operating system.
I don't expect to have to manually edit any files with an editor.
I don't expect to have to install and keep ddev up to date in Windows and WSL.
Steps To Reproduce

Setup DDEV inside WSL according the documentation https://ddev.readthedocs.io/en/stable/

Skip "Windows (traditional/legacy)"

Run ddev config and ddev start in a new project inside WSL
Try to access the website through a browser installed on the host system

Anything else?
This issue can be avoided by using the Windows binary inside WSL as proposed by the concept DDEV Interop Based WSL Integration, but @rfay had valid reasons for not implementing this concept as default.
This issue does affect the following issue of the DDEV Integration Plugin: https://github.com/php-perfect/ddev-intellij-plugin/issues/32

That warning only happens when either there's no internet or a non-ddev.site URL is in place. ddev hostname is not used otherwise.

Thanks for your fast response!
From my windows host resolving some-project.ddev.site is not possible while google.com is, so internet should be available.
Microsoft Windows [Version 10.0.22000.652]
(c) Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\nl>ping some-project.ddev.site
Ping-Anforderung konnte Host "some-project.ddev.site" nicht finden. Überprüfen Sie den Namen, und versuchen Sie es erneut.

C:\Users\nl>ping google.com

Ping wird ausgeführt für google.com [2a00:1450:4001:827::200e] mit 32 Bytes Daten:
Antwort von 2a00:1450:4001:827::200e: Zeit=6ms
Antwort von 2a00:1450:4001:827::200e: Zeit=4ms

In my WSL both the ddev domain, as well as google is reachable
nl@XPS-9510-NL:~/projects/some-project$ ping some-project.ddev.site -c 1
PING localhost (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from localhost (<IP_ADDRESS>): icmp_seq=1 ttl=64 time=0.023 ms

--- localhost ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.023/0.023/0.023/0.000 ms
nl@XPS-9510-NL:~/projects/some-project$ ping google.com -c 1
PING google.com (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from fra24s11-in-f14.1e100.net (<IP_ADDRESS>): icmp_seq=1 ttl=117 time=5.68 ms

--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 5.682/5.682/5.682/0.000 ms

Do I understand you right, that the ddev hostname notices shouldn't appear at all?
Can I provide you any additional debug information?
I'm also available in discord.
Thanks for your help!

You can ping dkdkskdj.ddev.site on the Windows side and you should see it hit <IP_ADDRESS>. This is just a function of DNS and the DNS wildcard for *.ddev.site.
There is a problem with certain routers though where DNS rebinding is prohibited, this could be your situation, as described in https://ddev.readthedocs.io/en/latest/users/troubleshooting/#dns-rebinding-prohibited - but I'd think that would affect WSL2 and Windows equally.
Again, lookup of *.ddev.site is not (normally) a feature of ddev, it's a feature of DNS configuration. If your Windows system can't resolve it, you'll find others that can, and we can chase the problem on your specific system.

Yes, adding ddev.site to the whitelist solved this issue for me. But this issue might be more more important than you might think. Everyone of my colleagues helping me test the plugin had the same issue. AVM (FritzBox) has quite a large market share, at least in germany. Also this might be a problem in enterprise environments, as admins will not be happy to open their firewalls for rebinding attacks.
As this issue was about the host entry, it has lower priority to me now. But the actual problem of setting the host entries from WSL still exists.
Your decission if you like to keep this issue open or close it as my actual problem with that is solved.

I have always wanted ddev hostname to update both hosts files ever since the beginning, to work around this class of problems, kept hoping for a contribution that would solve it. sudo.exe ddev.exe hostname on the Windows side could be executed by ddev hostname.  The message emitted by ddev hostname currently was a workaround.

#2409 is related of course
#2578

maybe this could be useful?
https://github.com/shayne/go-wsl2-host

Thanks so much @morvy, please continue to keep your eyes open! - It seems go-wsl2-host only adds an IP address on the Windows side to access the WSL2 environment directly.  The goal here is for ddev to be able to add a *.ddev.site or other additional_hosts or additional_fqdns entry that gets added in wsl2 into the Windows hosts files.

There is a problem with certain routers though where DNS rebinding is prohibited, this could be your situation, as described in https://ddev.readthedocs.io/en/latest/users/troubleshooting/#dns-rebinding-prohibited - but I'd think that would affect WSL2 and Windows equally.

Thanks i think that was it! Link changed to: https://ddev.readthedocs.io/en/stable/users/troubleshooting/#dns-rebinding-prohibited
and here the tutorial for Fritzbox: https://github.com/drud/ddev/issues/2409#issuecomment-686718237

@nico-loeber @morvy @mhsdesign and anybody else, would love it if you could test https://github.com/drud/ddev/pull/4377 - the binary should be in the PR in just a few minutes. You will need both the Windows and linux binaries/installers.


Description line in the wrong spot

Quick patch ... Idk how this got past three of us! 🙈

@guardrex Thank you for catching this.


DA at multiple resolution

Description
This feature will allow different geometries to be used for h(x) and B.
Features:

Variable changes: Use the correct geometry and interpolate bkg/traj to the "B" geometry
Increment interpolation: Similar to State, but only uses a 2d interpolation
Addition of 3dvar test using 2 geometries

Issue(s) addressed
closes #417
closes #436
Issues NOT addressed

VertConv and BkgErr will currently not work with different geometries between bkg (or traj) and incr. (#436 )
Duplication of States in Increment "diff"

Testing
How were these changes tested? in container only
What compilers / HPCs was it tested with? gnu
Are the changes covered by ctests? addition of a 3dvar test with 2 geometries

@travissluka : Just addressed travis-ci's tantrum about uncovered code. I think this is ready for review ... And as I write this, I realized I didn't check valgrind. Oops ... I'm sure it's fine!

i'm running it through valgrind now


Standalone helm support for PowerFlex

Is this a new chart?
Yes/No
What this PR does / why we need it:
This PR address , standalone helm support for PowerFlex , it updates all the required files in csi-vxflexos
Which issue(s) is this PR associated with:

#Issue_Number
https://github.com/dell/csm/issues/877

Special notes for your reviewer:
Checklist:
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] Chart Version bumped
[ ] Variables are documented in the chart README.md
[ ] Title of the PR starts with the chart name (e.g. [charts_dir/mychartname]) if applicable

Please include the GitHub issue link in the PR description.

Done


ACK runtime update to v0.19.2

Description of changes:

ACK runtime update to v0.19.2 . Release Notes

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm


A functional question about face effects

Hello，
I want to implement a project.
like:
When I look in the mirror, the camera in the mirror automatically recognizes the position of the face and adds facial effects.
The key issue is that the location of the face recognized by the camera may not be the same as the position in the   mirror.
Do you have any good ideas?
thanks!

Please refer to http://forum.magicmirror.builders for support and troubleshooting.
I'm closing this issue for now. If you feel this issue should remain open, please let me know.

thanks


Binder ordering no longer matters

This fixes #18

I just realised I didn't fix the letrec case

Ok, will hold off merging for now.

I've started trying to fix it, but I'm a little stuck. I thought this would work https://github.com/LightAndLight/inspection-testing/blob/binder-ordering-wip/Test/Inspection/Core.hs#L94
but it fails two tests. I need to go do other things for a while, so I'm leaving it here in case you have any ideas.

@LightAndLight Sorry for dropping the ball on this. Is this still something you are working on?

No worries. I have't touched it since last year

I just ran into this bug when trying to test a core plugin, something I'm particularly keen to make sure I got right. Since I can't control the order of the binding groups, this is a pretty big blocker for me!
The PR seems pretty dead --- do either of you (@nomeata , @LightAndLight ) want a hand with it?

Fixed via https://github.com/nomeata/inspection-testing/commit/30d76bfe521bbdc98b4a60a25461be784ba4b17d instead, please let me know if that does not address your needs, and thanks for your contribution.


Unable to publish app to appcenter from JenkinsCI running on mac node.

Running appcenter login fails with message:
Error: Could not add password to keychain: security: SecKeychainItemCreateFromContent (<default>): User interaction is not allowed.
Problem is that appcenter stores token in keychain and Jenkins is connected to mac node over ssh.

Hi @rhaly. I'd like to make sure I understand the scenario. You want to communicate with App Center through the CLI from inside a CI job, running with Jenkins. You're trying to perform the operation appcenter login --token <token> or appcenter login --user <user> --password <password>. This operation fails, with that error about the key chain? The error mentions user interaction. It looks like it means interaction with the key chain. Just to be sure though, you're not just running appcenter login without arguments? That would open interactive login mode, which doesn't work in CI because it requires user action.
Since you mention Node, which version of Node is the job running with? The App Center CLI only supports Node version 10.*.

Hi @anywherepilot .
I'm using appcenter login --token <token>. I've meant node as Jenkins Node it's other name for agent.
But there is node.js installed on mac agent with version 12.16.3. Everything runs fine when im running appcenter login --token from local machine, but fails over ssh.

Hi @rhaly. Since the CLI indeed needs access to the key chain to store the password - this is the purpose of appcenter login - you will need to have this access. If your user does not have that access, as appears to be the case, then you cannot use appcenter login. That doesn't mean you cannot use other appcenter commands. You'll just have to use the token parameter which each invocation. You could write a little wrapper script to handle this for you, if you can't obtain the required permissions.

That works for me thanks for help.


[RFC] Drop Keepkey

Should we drop support for the Keepkey?
Keepkey is a clone of the Trezor, so we currently just reuse the Trezor implementation. As such, trezorlib and the TrezorClient needs a couple of modifications to support the Keepkey. However these changes do make updating Trezor things harder to ensure that Keepkey still work. Furthermore, doing so also means that we lose Trezor functionality.
The specific incompatibility between the Trezor and Keepkey that causes the issues is that the Features message differs. Using a stripped down Features message to support will result in lost functionality on the Trezor. I've tried a couple of other things to try to swap out the the module implementing the message either don't work, or involve hijacking some very internal things in Python that we probably shouldn't be doing. In the latter case, while it may work for the CLI tool, it's possible that library users won't work.
Instead of doing some weird Python thing, we could instead copy the trezorlib implementation and just make it Keepkey specific (note that the actual keepkeylib is not usable for us as it is based on an older trezorlib that phones home and would require even more significant modification to fit our standards). So Keepkey would be implemented as a separate device instead of as a Trezor device. However this will mean that there's a lot of duplicated code and we still have to go through the work of patching trezorlib to work with the keepkey every time it is updated.
But there's also the question of whether it is even worthwhile to keep the Keepkey. It does not seem like the Keepkey is actually used. So in that case, we could probably just drop it entirely without any adverse effect on the users of HWI.

There is a 6.6.0 release of python-keepkey here: https://github.com/keepkey/python-keepkey/releases/tag/v6.6.0 - it might include some improvements that address the main painpoints.
It would be ideal if python-trezor dependency could be used as is (modulo stuff you don't want in HWI - we could work together to make it easier to remove), but because it's patched to support Keepkey is well, it creates extra friction while updating it.

@prusnak I still think it is preferable to make trezorlib be able to support the keepkey, either through direct modification, or more extensive upstream changes that makes it possible to have different messages for different devices (I am working on a modification that would allow this that could be upstreamed, it is not keepkey specific).
Even though keepkey has their own python library, I have found it difficult to modify it to meet the standards we use. Furthermore, given the similarities between trezor and keepkey, I think it's a waste of space to duplicate the Trezor implementation for the keepkey just to use the keepkey library. It also ends up being a bit of a waste of time when implementing new features as it has to be implemented twice, in basically identical ways (but slightly different because the libraries have slightly different APIs even though underneath they do the same thing).

With the new trezorlib, I've worked out a slightly more permanent solution. Given that the keepkey seems to still be maintained, support for it will not be dropped in the foreseeable future.


Missing keys in static_dict when loading pre-trained teacher model

When I tried to run your code with WRN_CIFAR10_adv.t7 you provided as the teacher model, I got a missing keys issue:

I am pretty sure that I chose the right net and set a valid path for teacher model when running.
Can you figure out why I can't load teacher model? Thanks a lot.

Have you tried putting the model in DataParallel before you load the model weights?  Like after line 88 of main.py.

Have you tried putting the model in DataParallel before you load the model weights? Like after line 88 of main.py.

Thanks for replying. I didn't use DataParallel. Actually I use the same code as yours, except the parameter settings are different.

You should try that.  I do not remember if that model was saved in DataParallel, and that is the most common cause of the error message you posted above.  Sorry, I did this project a very long time ago, and it was my first project, so I did not do a good job of making things reproducible!

You should try that. I do not remember if that model was saved in DataParallel, and that is the most common cause of the error message you posted above. Sorry, I did this project a very long time ago, and it was my first project, so I did not do a good job of making things reproducible!

Thank you! I will have a try.


New Rule (Link): Office document loads remote HTML template

heads up, not ignoring this, it's just really expensive on backtesting, so I haven't had much luck validating tp/fp ratios.

😭  On a 3 day retro, returned 9 FP's and no TP's.
Lots of docx's with meeting agendas or forms. Might need to refactor our approach here

How do we feel about adding the FTS snippet?

How do we feel about adding the FTS snippet?

We can give it a go!


Only bind keys in normal mode if using fish_default_key_bindings

In Vi mode, Ctrl + r is used for redo by default, which conflicts with __fzf_search_history. I believe the correct way to handle this is to only bind keys in insert mode.
Also added handler for mode switching like autopair.fish.

Interesting, there's more demand for this than I thought. This was initially proposed in #153. Can you take a look at the work I started in #158 to see if it'll be adequate to address this issue?

I saw that PR but forgot it when I made this. Will take a look later

@kidonng how come you closed this PR?

I haven't got the time to see #158, but since this is an issue already being worked on, I think it's better to close it. If I see it necessary we can reopen later.

I realized #158 won't fix this, though it'll make it easier for users to workaround it. Yeah let's just explore this when Ctrl+R = redo on the next release of fish. I don't want to make updates for fish master branch.

I don't want to make updates for fish master branch.

That's a point I forgot to mention. Though it doesn't hold water, one don't have to actually use master branch of fish, they just need to drop the latest fish_vi_key_bindings.fish into ~/.config/fish/functions. In fact this is what I do personally.
(It's a bless to be able to easily override/backport latest feature/fix into fish, thanks to the autoload feature.)


Build failures on OSX

I'm unable to install mpack on OSX (details below), and it seems to be leading to a problem installing neovim (related to https://github.com/neovim/neovim/issues/4573, I think).
Here's the output of the build failure:
$ luarocks install mpack
lmpack.c:185:11: warning: implicit declaration of function 'lua_objlen' is invalid in
      C99 [-Wimplicit-function-declaration]
    len = lua_objlen(L, -1);
          ^
lmpack.c:1056:14: error: unknown type name 'luaL_reg'; did you mean 'luaL_Reg'?
static const luaL_reg unpacker_methods[] = {
             ^~~~~~~~
             luaL_Reg
/usr/local/include/lauxlib.h:26:3: note: 'luaL_Reg' declared here
} luaL_Reg;
  ^
lmpack.c:1062:14: error: unknown type name 'luaL_reg'; did you mean 'luaL_Reg'?
static const luaL_reg packer_methods[] = {
             ^~~~~~~~
             luaL_Reg
/usr/local/include/lauxlib.h:26:3: note: 'luaL_Reg' declared here
} luaL_Reg;
  ^
lmpack.c:1068:14: error: unknown type name 'luaL_reg'; did you mean 'luaL_Reg'?
static const luaL_reg session_methods[] = {
             ^~~~~~~~
             luaL_Reg
/usr/local/include/lauxlib.h:26:3: note: 'luaL_Reg' declared here
} luaL_Reg;
  ^
lmpack.c:1077:14: error: unknown type name 'luaL_reg'; did you mean 'luaL_Reg'?
static const luaL_reg mpack_functions[] = {
             ^~~~~~~~
             luaL_Reg
/usr/local/include/lauxlib.h:26:3: note: 'luaL_Reg' declared here
} luaL_Reg;
  ^
lmpack.c:1092:3: warning: implicit declaration of function 'luaL_register' is invalid
      in C99 [-Wimplicit-function-declaration]
  luaL_register(L, NULL, unpacker_methods);
  ^
2 warnings and 4 errors generated.

Error: Build error: Failed compiling object lmpack.o

OSX: 10.10.5
lua: Lua 5.2.4  Copyright (C) 1994-2015 Lua.org, PUC-Rio
luarocks: 2.3.0

lua 5.1 header defines:
#define luaL_reg        luaL_Reg

Looks like lua 5.2 removed that. I think we require luajit or lua 5.1.

Should have been closed by https://github.com/tarruda/libmpack/pull/5


Running same query hangs

Issue Type: Bug
Running against localdb
Steps to repro:

Open the connections, expand the localdb entry
Expand to find a database in the local db.
Expand to find a table.
Right click to Select top 1000 rows.
Results are produced.
Click "Run" on the toolbar above the query window.
Hangs. Status bar says "Executing query". Query window now unresponsive and has to be closed and reopened.

Expected result:

Query is re-executed.

Azure Data Studio version: azuredatastudio 1.16.1 (16801c522df68e63218b39ccb5b4a7431f9bf667, 2020-03-23T22:08:06.892Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.73GB (18.87GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

Could be related #9170

can repro, its completely consistent. Using a local postgres db.Azure Data Studio 1.16.1 on Ubuntu 16.04. I do not think it's related to #9170

I'm going to move to the postgres project repo since bugs are tracked separately for that component.  Thanks for reporting this issue.


Add nix option in terraform and fix run-nixos-anywhere.sh

The current terraform module does not accept nix options.
Therefore, it may not work properly when needing --options pure-eval false and so on.
I add nix_options to the terraform module to address this issue.
Also, I fixed an issue where $tmpdir/keys could not be created again when multiple disk_encryption_key_scripts were specified in run-nixos-anywhere.sh, resulting in an error.

Also, I fixed an issue where $tmpdir/keys could not be created again when multiple disk_encryption_key_scripts were specified in run-nixos-anywhere.sh, resulting in an error.

The example shown in All-In-One seems wrong.
decrypt-zfs-key.sh is shown to redirect, but even within the script I am trying to create a file with the redirect.
As shown in ./decrypt.sh > $tmpdir/key/0 (./decrypt.sh like echo "test" > key.txt), there is a double redirect, but is it as intended?

Also, I fixed an issue where $tmpdir/keys could not be created again when multiple disk_encryption_key_scripts were specified in run-nixos-anywhere.sh, resulting in an error.

The example shown in All-In-One seems wrong. decrypt-zfs-key.sh is shown to redirect, but even within the script I am trying to create a file with the redirect. As shown in ./decrypt.sh > $tmpdir/key/0 (./decrypt.sh like echo "test" > key.txt), there is a double redirect, but is it as intended?

Fixed. I checked again with the orignal machine where I took this from.

@Mic92
Sorry for the late reply and work.
I have corrected the points you pointed out, so please check.,

Thank you for the correction.

On a separate matter, there is no ignore_systemd_errors option in all-in-one, is this intentional?
If not, is it okay to add it? or should I separate PR?

@mergify queue

On a separate matter, there is no ignore_systemd_errors option in all-in-one, is this intentional? If not, is it okay to add it? or should I separate PR?

Probably just an oversight, we can add it there as well.


various json ddl conversion issues

When converting JSON ddls to ruby we have a few issues:

all numbers from json files are floats when handled as interface{} so we need to improve some things there to avoid panics
all validations are shown as :foo when its a regex, so that becomes :.+ which is bad
output type is always shown, sometimes as ""
the word aggregate should be before the names of aggregate funcs

closed via incorrectly tagged https://github.com/choria-io/mcorpc-agent-provider/pull/130


Store path information

The Location constructor should get an extra argument for path information. That makes filename derivation in cloogle-tags easier, as well as in cloogle.org where we need it to link to source (now, the links to modules in the clean-compiler don't work, for example, because it doesn't use hierarchical modules).
(Perhaps combining the two line numbers in a tuple will be faster because it reduces function arity.)

Resolved in https://github.com/clean-cloogle/Cloogle/commit/28c7b3fcd99bd96539d742fee87e1e77fb12e79a.


pods with static ip need to have same metadata has dynamic ip pods

Signed-off-by: Girish Moodalbail<EMAIL_ADDRESS>

Do we need this? I don't think the command overwrites previously set values?

@shettyg the command overwrites the previously set values. See below
# ovn-nbctl --version
ovn-nbctl (Open vSwitch) 2.10.1
DB Schema 5.13.0
# ovn-nbctl lsp-add join test0
# ovn-nbctl --may-exist lsp-add join test0 -- set logical_switch_port test0 external-ids:namespace=default
# ovn-nbctl get logical_switch_port test0 external-ids:namespace
default

Usecase-1
It is possible to pin a POD to a particular node and enforce a particular static IP on it through OVN annotations. When this happens, those logical_switch_ports will not have pod=true and other metadata. This creates problem in syncPods() and other places where we look for logical_switch and namespace values.
Usecase-2
Update the pod spec, that had dynamic IP before, to pin it to a particular IP address on the node. For this use case, what we have today should work.


cloud-init fails to parse user_data

Hi I have been trying to bring up a coreOS cluster using openstack heat orchestration. with Heat one can specify the user data as resources.
I am able to create a coreos cluster when I use cloud config resource for user data. one can also specify a software config resource as user data something like
#!/bin/sh
echo "The two is bar" > /tmp/two
Both of them do not give any problem. But when I try to club them into another resource of type multipartmime resource and use that as the user_data ,the clout-init fails to parse the user_data with the below error message.
Jan 22 22:46:19 host-10-20-30-75 coreos-cloudinit[532]: Failed to parse user-data: Unrecognized user-data header: Content-Type: multipart/mixed; boundary="===============2575908242629671258=="
Jan 22 22:46:19 host-10-20-30-75 coreos-cloudinit[532]: Continuing...
Jan 22 22:46:19 host-10-20-30-75 coreos-cloudinit[532]: Processing cloud-config from meta-data
Jan 22 22:46:19 coreosstack-tvecoreos01-yhxuulyjbzh4.novalocal coreos-cloudinit[532]: 2015/01/22 22:46:19 Set hostname to coreosstack-tvecoreos01-yhxuulyjbzh4.novalocal
Jan 22 22:46:19 coreosstack-tvecoreos01-yhxuulyjbzh4.novalocal coreos-cloudinit[532]: 2015/01/22 22:46:19 Authorized SSH keys for core user
Jan 22 22:46:19 coreosstack-tvecoreos01-yhxuulyjbzh4.novalocal coreos-cloudinit[532]: 2015/01/22 22:46:19 Updated /etc/environment
Jan 22 22:46:19 coreosstack-tvecoreos01-yhxuulyjbzh4.novalocal systemd[1]: oem-cloudinit.service: main process exited, code=exited, status=1/FAILURE
Jan 22 22:46:19 coreosstack-tvecoreos01-yhxuulyjbzh4.novalocal systemd[1]: Failed to start Cloudinit from EC2-style metadata.
Jan 22 22:46:19 coreosstack-tvecoreos01-yhxuulyjbzh4.novalocal systemd[1]: Unit oem-cloudinit.service entered failed state.
any inputs are much appreciated.

coreos-cloudinit does not support multipart userdata. It needs to either be a script (beginning with "#!") or a cloud-config (beginning with "#cloud-config"). If you need both, your best bet is to include the scripts as oneshot services in your config.

thanks for the real quick reply crawford.
So here with coreos, if I need to have few commands run by cloud-init along with cloud-config, it should be inside the cloud-config as bootcmd: or runcmd: is it? or did you mean something else.

We don't support the full cloud-init spec (as you found out) and don't support bootcmd or runcmd. You'll want to use coreos.units. i.e.:
#cloud-config

coreos:
  units:
    -
      name: hello.service
      runtime: true
      command: start
      content: |
        [Service]
        ExecStart=/usr/bin/echo Hello World!

You can use https://coreos.com/validate/ to help quickly verify that your config is at least valid.

oh my bad. I will try with the coreos units. thanks again.

No problem. Let me know if you run into trouble.


unknown should be narrowable to {}

TypeScript Version:  3.6.0-dev.20190711
Search Terms: unknown narrow toString hasOwnProperty
Code
function f1(o: unknown) {
  if (o) {
    o.toString();
  }
}
function f2(o: {}|null|undefined) {
  if (o) {
    o.toString();
  }
}

Expected behavior:
Both succeed.
From user perspective I believe unknown behaves like an alias for the second type.  So another way of looking at this problem is that given f1's signature, it's hard to explain why to someone to need to switch it to f2's signature based on whether the body needs narrowing.
Actual behavior:
f1 invalid on the toString, Object is of type 'unknown'.
Playground Link:
http://www.typescriptlang.org/play/#code/GYVwdgxgLglg9mABMAjACjgLkeA1mOAdzAEpEBvAKEURmEQzKpprgDoo4BlKAJxjABzNCQDc1RAF9K00JFgJkAJgzZykgD5gQAGx0bwAEwCmwAccNMJdBnCstE7Tj35CR4mtMlA
Related Issues:
In this comment
https://github.com/microsoft/TypeScript/issues/28131#issuecomment-433106959
@ahejlsberg says it's a limitation of the CFA.
This bug talks about other approaches to narrowing unknown:
https://github.com/microsoft/TypeScript/issues/25720
and in particular @andy-ms points out a bug that feels similar:
https://github.com/microsoft/TypeScript/issues/25720#issuecomment-407237691

Also running into this when dealing with JSON, as the result of unmarshaling is reasonably unknown, and result ? result.toString() : "" doesn't type check...

PR is out at #49119


gerrit up fails to un-draft

Pushing draft then following with a gerrit up fails with the following output.
? Topic "AddressBook" was previously saved as a *draft*, are you sure you want to un-draft it? Yes
Pushing to origin (refs/for/master/AddressBook)
remote: Resolving deltas: 100% (7/7)
remote: Processing changes: refs: 1, done
To ssh://user@server/repo
! [remote rejected] HEAD -> refs/for/master/AddressBook (no changes made)
error: failed to push some refs to 'ssh://user@server/repo'
gerrit ERROR Error while pushing commit.

Workaround was to amend my commit before trying to upload it.
gerrit version 0.1.0

Taking a look at the line ! [remote rejected] HEAD -> refs/for/master/AddressBook (no changes made) it seems like the the commit you were trying to push was already in Gerrit

It was already in gerrit but as a draft.  I was trying to un-draft it.

Hmmm I see, either gerrit up should be made smarter or an undraft command should be created...

Right

Fixed by https://github.com/shanesmith/gerrit-cli/commit/4233f18d9f2bd560d9ea516bbd15e90f2a45d059


(Docs) Default command for s3 image registry fails

In https://github.com/kontena/kontena/blob/master/docs/using-kontena/image-registry.md,
it instructs users who want to setup an image registry on s3 to use the following command:
kontena registry create --s3-bucket=<bucket_name> --s3-region=<optional_aws_region>

Doing this results in a failure. The service will start and say it's running but will be in a constant state of restarting. Viewing the logs gives you the following information (repeated every ~5 seconds):
2017-07-22T21:39:55.000Z [1]: ~~ Kontena Registry ~~
2017-07-22T21:39:55.000Z [1]:
2017-07-22T21:39:55.000Z [1]:
2017-07-22T21:39:55.000Z [1]: panic: On Amazon S3 this storage driver can only be used with v4 authentication
2017-07-22T21:39:55.000Z [1]:
2017-07-22T21:39:55.000Z [1]: goroutine 1 [running]:
2017-07-22T21:39:55.000Z [1]: panic(0xb7db80, 0xc420385b40)
2017-07-22T21:39:55.000Z [1]: 	/usr/local/go/src/runtime/panic.go:500 +0x1a1
2017-07-22T21:39:55.000Z [1]: github.com/docker/distribution/registry/handlers.NewApp(0x10667c0, 0xc42033d3e0, 0xc4201e7500, 0x10667c0)
2017-07-22T21:39:55.000Z [1]: 	/go/src/github.com/docker/distribution/registry/handlers/app.go:123 +0x3908
2017-07-22T21:39:55.000Z [1]: github.com/docker/distribution/registry.NewRegistry(0x7f345ea95198, 0xc42033d3e0, 0xc4201e7500, 0xc4201e7500, 0x0, 0x0)
2017-07-22T21:39:55.000Z [1]: 	/go/src/github.com/docker/distribution/registry/registry.go:86 +0x213

The fix was simple enough but figuring it out took quite a while. This is the command that I ran:
kontena registry create --s3-v4auth --s3-bucket=<bucket_name> --s3-region=<optional_aws_region>

After running that new command, the registry started up and I was able to push to it just fine.
I propose either updating the docs with that new command, or updating the registry create command to default that flag to true.

#2242 fixes the docs, but I think the CLI default should also be changed to --s3-v4auth. Does someone who can readily test this want to make a PR? @jakolehm @jnummelin


Adding egl build

FYI, some of the logic may be ported to the common superbuild: https://gitlab.kitware.com/paraview/common-superbuild/-/merge_requests/563


Merge "ui-router-core" imports

Thought I'd help out a bit since the split of core to it's own repo/package. I tried to organize imports the same way: libs (angular, ui-router-core) > local (relative stuff)
Feel free to request changes if there's something you want me to edit.
EDIT: Rebased and removed all ng2 changes.

Let's close this, imports has already been merged and committed in master branch.

@csvn sorry for duplicating your work. I really really do appreciate the pull requests!

No problem! It's not a simple thing to sync :)


Fix missing recover while occur panic in handler

Hi there,
Process exit.
By default rcpServer can't recover handler panic.
Because of the recover code at top of ServeConn, but handler process in different coroutine and no recover.
Useless for process handler and outbound messages.
https://github.com/micro/go-micro/blob/master/server/rpc_server.go#L160
Missing recover
https://github.com/micro/go-micro/blob/master/server/rpc_server.go#L398-L403
Reference:
https://github.com/golang/go/wiki/PanicAndRecover

Some other way to do it by handler wrapper. But must keep the wrapper first.
I think should do it in core framework.
example
s := micro.NewService(
	micro.Name("demo.srv.test"),
	micro.Version("latest"),

        // Must keep recover wrapper first
	micro.WrapHandler(func(handlerFunc server.HandlerFunc) server.HandlerFunc {
		return func(ctx context.Context, req server.Request, rsp interface{}) error {
			defer func() {
				if r := recover(); r != nil {
					log.Log("panic recovered: ", r)
					log.Log(string(debug.Stack()))
				}
			}()

			return handlerFunc(ctx, req, rsp)
		}
	}),
)

Thanks very much. Is @tencent using micro?

@asim  TKS for reply.
We try to use micro in small team. Internal promotion and use it.
Personally, I'm very interested in micro. Awesome design 👍

Thank you, very exciting to see micro at tencent. Please let me know how things progress. It would be amazing to see tencent adopt it at a bigger scale.


PAYG with Custom Images?

We want to use one of the SQL Server editions discussed here, but wish to create and deploy our own image using Packer or Azure Image Builder so that we can control what is installed. Can we use the Pay-as-you-Go model with custom images?

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

ID: 2a863cb0-c5d3-87d6-7c4d-28a1316d70f8
Version Independent ID: e56cf79c-d919-92d7-d3a0-05ada08ba17b
Content: Manage costs effectively for SQL Server on Azure virtual machines
Content Source: articles/virtual-machines/windows/sql/virtual-machines-windows-sql-server-pricing-guidance.md
Service: virtual-machines-sql
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

@jonathaneckman Yes, you can use images using Packer or Azure Image builder in Pay-As-You-Go subscription model. The billing model is on the subscription level.
Hope this answers your query.
Thanks.

I used the wrong term. I was referring to the pay-per-usage VM billing model, not the pay-as-you-go subscription model. Specifically, this sentence from this article:
“Paying the SQL Server license per usage means that the per-second cost of running the Azure VM includes the cost of the SQL Server license.”
I’d like to pay per-second using a custom SQL Server image instead of buying licenses.

@jonathaneckman Thanks for clarifying your question.
I am checking with the internal team on this, will update here once I get the response.

Hi @jonathaneckman , thank you for contacting Microsoft! Actually, the two are the same thing (pay as you go, and pay per usage) but you've pointed out that using the two terms interchangeably might be confusing so I'll review this internally. But yes, you can enable the "pay per usage" model for a custom image - just register with the SQL VM resource provider, and specify the 'payg' as the license type.
I hope that helps and please let us know if we can  be of further assistance :)
Thanks!
Masha from the SQL Docs team

Perfect. Thanks!


Add dropped packets to network counters

We want these for the metrics as well. I just forgot to add them to the previous PR.

@monstermunchkin we probably don't need an additional API extension as there won't have been a release between this and the last PR (https://github.com/lxc/lxd/pull/9174), and "dropped" packets can conceivably also be considered an "error" and so fit into the previous API extension.

@monstermunchkin we probably don't need an additional API extension as there won't have been a release between this and the last PR (#9174), and "dropped" packets can conceivably also be considered an "error" and so fit into the previous API extension.

@tomponline I could also just reword the latest API extension. What do you think?


Associativity and distributivity of plus in T1.

Complete all proof in file draft_plus_assoc.v

Wow! Very impressive!
Next step should be to put each of these lemmas in the most suited place, right? @Casteran any suggestion?

Very nice !
I suggest to place the main  lemmas into T1.v (provisionally: T1.v is quite big, and I plan to create a library Epsilon0/Ordinal_arithmetic, but later).
Likewise, I think some generic lemmas and tactics about compare deserve to be exported into a Prelude/Comparable library (with type classes), but it’s not urgent. What do you think about this change?
About Coq V8.11 and V8.12: Shall we maintain the compatibility ? If I remember well some messages, there are some warnings which will turn to errors in the future versions of Coq.

Le 21 juin 2021 à 08:55, Théo Zimmermann @.***> a écrit :
Wow! Very impressive!
Next step should be to put each of these lemmas in the most suited place, right? @Casteran https://github.com/Casteran any suggestion?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/coq-community/hydra-battles/pull/36#issuecomment-864777774, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJW6FCQKOV66XNVKY73KCMDTT3O4VANCNFSM47AMPHKA.

Let's drop compatibility with 8.11-8.12 if you agree. I will prepare a PR doing this.

@Casteran I've done the squashing. Are you OK with merging now? We have started working with Jérémy on moving the generic lemmas and tactics to a Comparable module in another branch.

Fine!
I’ll merge in a few minutes.
Envoyé de mon iPhone

Le 22 juin 2021 à 12:03, Théo Zimmermann @.***> a écrit :
@Casteran I've done the squashing. Are you OK with merging now? We have started working with Jérémy on moving the generic lemmas and tactics to a Comparable module in another branch.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Nice work ! Thanks !


Encrypted tokens in travis

We need to be able to keep up with the IBM API and test with real tokens.
Describe the solution you'd like
I want to discuss putting encrypted variables using travis (
https://docs.travis-ci.com/user/environment-variables/) so that the tests for ibm.py work.
Describe alternatives you've considered
Running these tests locally once in a while with private tokens is an alternative. This is especially because we do not necessarily want to run tests on the real IBM device every time someone makes a PR. However, if there is a way to make sure that only after all changes have been implemented, the final version of the PR gets tested on the real device, then it would be great. For this, I suggest that by default, we ignore testing with the tokens (by skipping them when something is WIP) but just before finally merging a PR, we do the test once. This could either be a hook or essential requirement by CI (similar to how every PR needs an approval from a maintainer)
@josh146 This also resolves the lowering of test coverage in the lastest PRs due to ìbm.py`

An encrypted IBM Q token has been added to .travis.yml in commit 2134385


Electrum server via Tor is not returning up-to-date data..?

Chasing a bug described here:  https://github.com/BlueWallet/BlueWallet/issues/3210
quote:

I noticed when opening Bluewallet configured to use my own raspiblitz electrum server via tor it doesnt refresh the wallet (shows no new transactions) no  matter how long i wait.
But when i open my Phoenix Wallet which is also connected to the Electrum server right before opening Bluewallet it instantly gets the new transactions  and everything works as intended.

frankly, this sounds very weird to me and I have no idea where to start debugging.

https://github.com/BlueWallet/BlueWallet/issues/3210#issuecomment-856157773

a clue:
echo  -e -n '{"id": 1, "method": "server.version", "params": ["bluewallet", "1.4"]}\n{"id": 2, "method": "blockchain.headers.subscribe", "params": []}\n' | nc oq3bcnn3ceyg4efmq3wed24n363xla7nf6esj2cc4zxez6wauhwb7wyd.onion 50001 -i 1 -x <IP_ADDRESS>:9050

nc: connection failed, SOCKSv5 error: TTL expired

^^^ sometimes it works sometimes not.
my guess is that something is wrong with Tor

@exitfiat

I updated tor on my raspiblitz and restarted it. I could refresh the wallet in bluewallet but i dont know if this is a fix or it stops working again sometimes.
Will watch it, mayve the problem solves itself.

closing for inactivirty


Using *.log extension for saved log files (fixes #490)

Codecov Report

Merging #491 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master     #491   +/-   ##
=======================================
  Coverage   77.18%   77.18%
=======================================
  Files          11       11
  Lines        1284     1284
=======================================
  Hits          991      991
  Misses        232      232
  Partials       61       61

Flag
Coverage Δ

#unittests
77.18% <0%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

selenoid.go
87.09% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c7d11ea...c4270fa. Read the comment docs.


[WIP] Debug 885

Fixes #

Proposed Changes

Release Note

Docs

6/6 Worked
/test pull-knative-sandbox-eventing-kafka-broker-integration-tests

7/7 Worked
/test pull-knative-sandbox-eventing-kafka-broker-integration-tests

8/8 Worked
/test pull-knative-sandbox-eventing-kafka-broker-integration-tests

Is this the test that is failing in other PRs as well? Can we merge it?

9/9 Worked
/test pull-knative-sandbox-eventing-kafka-broker-integration-tests

There are some glitches in the verify deps GH action, i'm going to check it out

No there are disabled tests.


Improve Documentation for APIs

The documentation is terrible for leveraging the paralus APIs. The endpoint link redirects one to the github page which has no information other than swagger JSONs. I had to examine network connections to even see what APIs are called, and even then I can't figure out how to authenticate through the APIs. I needs much better documentation so I don't have to hunt through the code.

@techmaharaj need your help with this

Sure, let us sync up in our call to get this done.

@estein9825 I can understand the pain. We are making swagger page available for Paralus. Tracking issues:

https://github.com/paralus/paralus/issues/97
https://github.com/paralus/website/issues/54

Marking this as duplicate. Will close this once API doc is available.


App crashes on open on Tonomy Staging

Steps to reproduce

Clear app storage on Tonomy Staging
creating a new account, skip PIN
Click skip Biometric

Expected behaviour

Navigate to user home

Actual behaviour

App crashes
if I reopened the app then I am briefly shown the user home screen, and then the app crashes

fixed bug in antelope did resolver and pushed v 0.2.3


Accept different sampling filters on resize

Currently on a resize, the Gaussian sampling filter is always used;

the image crate offers various other sampling filters: https://docs.rs/image/0.19.0/image/enum.FilterType.html

[x] Nearest

[x] Triangle

[x] CatmullRom

[x] Lanczos3

[x] Gaussian (also the default)

syntax:

Must have a syntax limited to tokens available in the ASCII set
Must support letters, numbers and some type of word separator
Must be unordered
Must support both Key Value and Flag
Must be reusable as syntax (i.e. like a general "data structure") with sic script v1
Should be accessible to type from the command line
Should be accessible to type within a file
Should be easy to read

Ideas for syntax:

resize x y <optional format>

resize 4 5 == resize 4 5 :sampling_filter gaussian

resize 4 5 :sampling_filter lanczos3

resize 4 5 -sampling-filter lanczos3

resize 4 5 +sampling-filter lanczos3

resize 4 5 #sampling-filter lanczos3

resize 4 5 (sampling-filter: lanczos3)

resize 4 5 {sampling-filter: lanczos3}

selected choice:

setopt resize <option> <option value>

setflag resize <flag>

resize <x> <y>

examples:
cargo run -- --apply-operations "setopt resize sampling_filter triangle;resize 50 50" ./resources/bwlines.png ./target/o.png
--
PR: #102
Related:

#45 (Add keep-aspect-ratio flag or option to resize)

implemented in #102


How to build Etcher from source, Void Linux MUSL

Distro: Void Linux x86_64-MUSL
Hey guys, I'm trying to figure out how to compile Etcher from source so I can have it work on Void Linux.
Makefile:188: No Sentry token found (ANALYTICS_SENTRY_TOKEN is not set)
Makefile:194: No Mixpanel token found (ANALYTICS_MIXPANEL_TOKEN is not set)
Available targets: help info lint lint-js lint-sass lint-cpp lint-html lint-spell test-spectron test-gui test-sdk test-cli test sanity-checks clean distclean changelog webpack package-electron package-cli cli-develop installers-all publish-all electron-develop electron-installer-appimage electron-installer-debian electron-installer-redhat cli-installer-tar-gz publish-aws-s3

Have you checked the instructions in the docs, or more specifically CONTRIBUTING.md#cloning-the-project?

Does Electron even work on Void Linux MUSL? (IIRC MUSL is an alternative libc package?)

Oh dang that's right, my bad! I forgot about that.
I will find out soon, lurch.

https://pastebin.com/VywpfBnR

npm start

<EMAIL_ADDRESS>start /home/kzn/Compiles/etcher
electron lib/start.js

events.js:165
throw er; // Unhandled 'error' event
^
Error: spawn /home/kzn/Compiles/etcher/node_modules/electron/dist/electron ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:201:19)
at onErrorNT (internal/child_process.js:379:16)
at process._tickCallback (internal/process/next_tick.js:114:19)
at Function.Module.runMain (module.js:692:11)
at startup (bootstrap_node.js:194:16)
at bootstrap_node.js:666:3
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:207:12)
at onErrorNT (internal/child_process.js:379:16)
[... lines matching original stack trace ...]
at bootstrap_node.js:666:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: electron lib/start.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!  It would appear I'm unable to get Etcher to build on Void MUSL... Not sure why exactly, but the info is there if any of you can better interpret the errors, this is new territory for me unfortunately.

I've never used Void Linux myself, but have you seen #2011 ?

./etcher-1.3.1-x86_64.AppImage: No such file or directory
-_- what is wrong with this thing?? Even when I click on it in the file it does the same thing... ugh...
I know flatpak works, do you guys have a flatpak image perhaps?

./etcher-1.3.1-x86_64.AppImage: No such file or directory

IIRC people get that (confusing) error message when trying to run the 64-bit AppImage on a 32-bit Linux distro. But perhaps using MUSL versus glibc also triggers the same error? *shrug*

I know flatpak works, do you guys have a flatpak image perhaps?

#2019

I can't make AppImages work no matter what I do, a flatpak image would be nice, BUT....
Being able to build-from-source is always more preferable. Its a shame electron isn't supported by Void MUSL. I have to get Electron installed before I can compile Etcher... Haven't been able to get it to install.

I'm trying to figure out how to get Electron installed on Void MUSL but it seems impossible, I don't know.... :/

This is what I get when I try to start electron with npm start:
https://pastebin.com/syAbXR90
electron-quick-start, npm start:
https://pastebin.com/PZyba3su
And when trying to launch Etcher:
https://pastebin.com/eLbyrM9v

Can confirm AppImages don't work for me either, says the file doesn't exist even though its been made executable, even when clicking it in the file manager it claims it doesn't exist.

If even Electron doesn't run on Void MUSL, then there's no chance that Etcher (which is built on top of Electron) will run on Void MUSL.


ng build -prod fails to clean up files

Please provide us with the following information:

OS?  Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Windows 10

Versions. Please run ng --version. If there's nothing outputted, please
run in a Terminal:
node --version
And paste the result here.
angular-cli: 1.0.0-beta.5
node: 5.6.0
os: win32 x64

Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
ng build works fine but ng build -prod fails giving error below. You can reproduce with my code from https://github.com/lamaan/angular2-salah-times

The log given by the failure. Normally this include a stack trace and some
more information.
C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times>ng build -prod
Cleanup error.
ENOTEMPTY: directory not empty, rmdir 'C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\tmp\broccoli_type_script_compiler-cache_path-973l28
5M.tmp\src\app'
Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\tmp\broccoli_type_script_compiler-cache_path
-973l285M.tmp\src\app'
at Error (native)
at Object.fs.rmdirSync (fs.js:806:18)
at rmkidsSync (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\quick-temp\node_modules\rimraf\rimraf.js:247:11)
at rmdirSync (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\quick-temp\node_modules\rimraf\rimraf.js:237:7)
at fixWinEPERMSync (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\quick-temp\node_modules\rimraf\rimraf.js:150:5)
at rimrafSync (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\quick-temp\node_modules\rimraf\rimraf.js:216:26)
at C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\quick-temp\node_modules\rimraf\rimraf.js:245:5
at Array.forEach (native)
at rmkidsSync (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\quick-temp\node_modules\rimraf\rimraf.js:244:26)
at rmdirSync (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\quick-temp\node_modules\rimraf\rimraf.js:237:7)
at fixWinEPERMSync (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\quick-temp\node_modules\rimraf\rimraf.js:150:5)
at rimrafSync (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\quick-temp\node_modules\rimraf\rimraf.js:216:26)
at C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\quick-temp\node_modules\rimraf\rimraf.js:245:5
at Array.forEach (native)
at rmkidsSync (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\quick-temp\node_modules\rimraf\rimraf.js:244:26)
at rmdirSync (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\quick-temp\node_modules\rimraf\rimraf.js:237:7)
Build failed.
The Broccoli Plugin: [BundlePlugin] failed with:
Error on fetch for angular2-google-maps/core.js at file:///C:/Users/Lamaan/AAAWork/shariahstandards.org/app/angular2-salah-times/tmp/bundle_plugin-input_base_pa
th-XrdEiDow.tmp/0/angular2-google-maps/core.js
Loading main.js
Error: ENOENT: no such file or directory, open 'C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\tmp\bundle_plugin-input_base_path-
XrdEiDow.tmp\0\angular2-google-maps\core.js'
at Error (native)

The broccoli plugin was instantiated at:
at BundlePlugin.Plugin (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\broccoli-plugin\index.js:10:31)
at BundlePlugin.CachingWriter [as constructor] (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\broccoli-caching-writer\i
ndex.js:21:10)
at BundlePlugin (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\angular-cli\lib\broccoli\angular-broccoli-bundle.js:10:3
6)
at Angular2App._getBundleTree (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\angular-cli\lib\broccoli\angular2-app.js:4
21:22)
at Angular2App._buildTree (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\angular-cli\lib\broccoli\angular2-app.js:159:2
1)
at new Angular2App (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\angular-cli\lib\broccoli\angular2-app.js:53:23)
at module.exports (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\angular-cli-build.js:8:10)
at Class.module.exports.Task.extend.setupBroccoliBuilder (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\angular-cli\lib
\models\builder.js:55:19)
at Class.module.exports.Task.extend.init (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\angular-cli\lib\models\builder.
js:89:10)
at new Class (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\core-object\core-object.js:18:12)
at Class.module.exports.Task.extend.run (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\angular-cli\lib\tasks\build.js:1
5:19)
at C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\angular-cli\lib\commands\build.js:32:24
at lib$rsvp$$internal$$tryCatch (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\rsvp\dist\rsvp.js:1036:16)
at lib$rsvp$$internal$$invokeCallback (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\rsvp\dist\rsvp.js:1048:17)
at lib$rsvp$$internal$$publish (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\rsvp\dist\rsvp.js:1019:11)
at lib$rsvp$asap$$flush (C:\Users\Lamaan\AAAWork\shariahstandards.org\app\angular2-salah-times\node_modules\rsvp\dist\rsvp.js:1198:9)

Mention any other details that might be useful.

this may be related:
http://stackoverflow.com/questions/33657172/ember-cli-cleanup-error-when-building

this was just windows not deleting files correctly and some other config errors which have now been resolved

I know this is closed but I'm facing the very same issue and was wondering how did you resolve this?

Just had to delete the tmp folder manually. Initially, it was quite large. But now, I rarely get the problem.
-----Original Message-----
From: "Sean"<EMAIL_ADDRESS>Sent: 15/06/2016 06:46
To: "angular/angular-cli"<EMAIL_ADDRESS>Cc: "lamaan"<EMAIL_ADDRESS>"State change"<EMAIL_ADDRESS>Subject: Re: [angular/angular-cli] ng build -prod fails to clean up files (#1068)
I know this is closed but I'm facing the very same issue and was wondering how did you resolve this?

You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
https://github.com/angular/angular-cli/issues/1068#issuecomment-226093773

I still get the error. I guess it depends on how large the app is.
On a basic app (just "ng new app") it works.
But, I don't know why, once I have a few components and routes, it gives me the above mentioned error. I tried to delete both "tmp" and "dist" folders before trying build -prod or serve -prod, but still gives the same error.

@MrCroft I can't say one way or another if it's a build bug or a code bug, but since we're moving away from SystemJS config in #1455 it might be a good idea to try that before opening an issue. There's no release yet though.

@filipesilva
Oh, I'm so sad! I was so avoiding webpack :)
Then again, I've got to hating webpack so so much simply because more and more examples out there were using it, going "against" the default (systemjs) approach of the cli, which was also the default approach in the angular docs/quickstart.
Now I'm wondering if it will be a quick and painless transition, to move my cli app from systemjs to webpack, once the cli will move away from systemjs and towards webpack.

I've WIP instructions in https://github.com/angular/angular-cli/pull/1456. Most people seem to think the transition is easy.

Hi,
I have now moved the code to the webpack version and am getting the following curious error from webpack trying to resolve a different dependency injection issue:
It seems that the Provider is not the correct type of provider?
https://github.com/lamaan/angular2-salah-times/tree/dictionary-with-injected-routes https://github.com/lamaan/angular2-salah-times/tree/dictionary-with-injected-routes
Lamaan
From: Filipe Silva<EMAIL_ADDRESS>Sent: 29 July 2016 18:29
To: angular/angular-cli<EMAIL_ADDRESS>Cc: lamaan<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [angular/angular-cli] ng build -prod fails to clean up files (#1068)
I've WIP instructions in #1456 https://github.com/angular/angular-cli/pull/1456 . Most people seem to think the transition is easy.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/angular/angular-cli/issues/1068#issuecomment-236211922 , or mute the thread https://github.com/notifications/unsubscribe-auth/AFcXknye6JGMmFwaPg4Nn9Z3zwYmpKf3ks5qahxQgaJpZM4IzxAR .  https://github.com/notifications/beacon/AFcXkhKtWQNTYaQ_PJR9-PcrXfym41FQks5qahxQgaJpZM4IzxAR.gif

Hi again,
I removed the dependency on angular2-google-maps to get it working.
Other problems found using web pack:

 Files are very big. It creates 5Mb main script file and 5 Mb map file. Which is very large for a small app like this.

 The source map cannot be parsed – at least by chrome which makes debugging only possible really with console.log.

 I cannot see how to include additional npm components as I did with system.js packages – so for now I have managed with using cdn.

Please can you let me know if and when you have any solutions to these?
Lamaan
From: Lamaan Ball<EMAIL_ADDRESS>Sent: 05 August 2016 07:39
To: 'angular/angular-cli'<EMAIL_ADDRESS>Subject: RE: [angular/angular-cli] ng build -prod fails to clean up files (#1068)
Hi,
I have now moved the code to the webpack version and am getting the following curious error from webpack trying to resolve a different dependency injection issue:
It seems that the Provider is not the correct type of provider?
https://github.com/lamaan/angular2-salah-times/tree/dictionary-with-injected-routes https://github.com/lamaan/angular2-salah-times/tree/dictionary-with-injected-routes
Lamaan
From: Filipe Silva<EMAIL_ADDRESS>Sent: 29 July 2016 18:29
To: angular/angular-cli<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Cc: lamaan<EMAIL_ADDRESS><EMAIL_ADDRESS>>; State change<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Subject: Re: [angular/angular-cli] ng build -prod fails to clean up files (#1068)
I've WIP instructions in #1456 https://github.com/angular/angular-cli/pull/1456 . Most people seem to think the transition is easy.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/angular/angular-cli/issues/1068#issuecomment-236211922 , or mute the thread https://github.com/notifications/unsubscribe-auth/AFcXknye6JGMmFwaPg4Nn9Z3zwYmpKf3ks5qahxQgaJpZM4IzxAR .  https://github.com/notifications/beacon/AFcXkhKtWQNTYaQ_PJR9-PcrXfym41FQks5qahxQgaJpZM4IzxAR.gif

@lamaan can you open a new issue for the issue you're still experiencing?


Delayed notifications firing immediately

Can you please fix the issue of delayed notifications firing immediately.. are you aware of that?

do you mind giving me a code snippet that you set up so I can look into this?  Thanks

Sorry for late reply. Thanks for your explanation and guidance. I really appreciate it.
On 12 Feb 2022, 9:36 PM +0500, Izumi Higa @.***>, wrote:

Hi @d7laungani , so, assuming you create a notification that repeats every day, I think the date components would look like this:
calendar.components([.hour, .minute], from: date)
Even if this date is a date from next month, the notification will start to get fired from tomorrow (or even today if the current time is before the specified hour) because the day info gets cut off by the date components.
In order for it to work properly, you'd have to do some complicated tricks like, create a non-repeating notification for next month first and then create another repeating one for after the firing date.
 Unless that is taken care of, I honestly don't feel much benefit to use this library.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>


⚠ Bofrost.fr has degraded performance

In c2d3ede, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1266 ms

Resolved: Bofrost.fr performance has improved in 98310ad after 10 minutes.


Emulated Hue: Device Unresponsive

Home Assistant release with the issue:
0.98.2
Last working Home Assistant release (if known):
0.97.2
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Component/platform:
/components/emulated_hue/
Description of problem:
My Alexa devices have been having trouble connecting/controlling the exposed lights and scripts in my Home Assistant instance. I suspect that this has to do with the latest Alexa update (iOS version 2.2.291375.0), since I that was right around when the issues started occurring.
I have checked to make sure that the integration is loaded and responded by navigating to
http://HA-IP-Address:8300/api/pi/lights
and seeing the correct list of devices.
I have deleted and re-added all of the devices 4 or 5 times and each time I see the same issue. After using the app to turn on the light, I see the message "Waiting for Royal Phillips Electronics", then the light turns on and then the app gives one of 2 messages: "Device malfunction" or "Device is unresponsive". After that I only ever see the error messages and the lights will not change.
Related to this could be the the new setting on the Alexa app. For all the device I've added (switch, script, etc.) there is a color setting with the ability to set a color. I'm not sure if the app is trying to set a color and being unsuccessful. When I go into the settings (on the Alexa app) for the entity I see the following information:

Connected via: [Echo Device]
Description: Royal Phillips Electronics smart device
Type: Light
Color Capabilities: Color
Enabled: True

For reference, the devices being exposed are 2 scripts and 3 GE smart light switches with dimming capabilities. They were working perfectly up until about a week ago.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
emulated_hue:
  host_ip: !secret hass_ip
  listen_port: 8300
  expose_by_default: false
  entities:
    light.ge_14295_in_wall_smart_toggle_dimmer_level:
      name: "Living Room"
      hidden: false
    light.ge_14295_in_wall_smart_toggle_dimmer_level_2:
      name: "Kitchen"
      hidden: false
    light.ge_14295_in_wall_smart_toggle_dimmer_level_3:
      name: "John's Room"
      hidden: false
    switch.monitors:
      name: "Monitors"
    script.tv_up:
      name: "Volume Up"
      hidden: false
    script.tv_down:
      name: "Volume Down"
      hidden: false

Traceback (if applicable):

Additional information:

I am also experiencing "device not found issues" with al devices I expose to alexa, with 0.98.1 and same after upgrading to 0.98.3.
The problem started today, I have been funning 0.98.1 for a few days with no issues, I can confirm it was working yesterday on 0.98.1 as I use this integration on a daily basis.
I wonder if this is an amazon-side issue. I tested the public API using curl with the token and it seems to still be working fine.

Hello.
I have the same issue, last version working was 0.97.2, after that one there were some apparently non-breaking changes since I didn't notice them on version details, but those broke my setup with this component and my lights.
My lights were reported like this before (just an example of the json object):
"9":{
"modelid":"HASS123",
"name":"Lightname",
"state":{
"bri":0,
"hue":0,
"on":false,
"reachable":true,
"sat":0
},
"swversion":"123",
"type":"Dimmable light",
"uniqueid":"entity_id"
}
And now those lights are like this:
"9":{
"modelid":"HASS321",
"name":"Lightname",
"state":{
"on":false,
"reachable":true
},
"swversion":"123",
"type":"On/off light",
"uniqueid":"entity_id"
}
Alexa reports the light as "non responsive", if I try to delete it and add it again it does not get added (not detected), once I revert back to the 0.97.2 version it gets detected again.
The issue is present in all 0.98.x versions.
Best regards.

Interesting... I haven't seen a change in JSON object (since I never checked it before trying to debug it), but this is what mine looks like for one of the lights:
 "9": {"modelid": "HASS123", "name": "Kitchen", "state": {"bri": 0, "hue": 0, "on": false, "reachable": true, "sat": 0}, "swversion": "123", "type": "Dimmable light", "uniqueid": "entity_id"}

@jbrody17 Which Alexa do you have?
can you please try to reset your Alexa? How to reset
after that try to re-discovering the light and check if you see the light with the model HASS321 in the app.

@croghostrider I have 2 Alexa Echos and 1 Alexa Dot. I will try to reset them

Having same issue also. As above it now seems that emulated hue is reporting all lights with a hue and sat value which is making alexa think everything is a colored bulb...

Same on mine. I have a ifan02 with tasmota and can still control the fan but not the light by Alexa
Odd thing I have noticed in the iOS app is that to turn a light on of off you have to hit on and almost right away hit it off and to turn it off hit off them instantly on

Maybe I’m missing something here but the if statement to determine what attributes are returned doesn’t look right to me?
if (entity_features & SUPPORT_BRIGHTNESS) or entity.domain != light.DOMAIN
That looks like it says, if the entity supports brightness OR is not in the light domain. If this is matched, state, brightness, hue , and sat are returned. Otherwise only state is returned. Shouldn’t it be if (entity_features & SUPPORT_BRIGHTNESS) or entity.domain == light.DOMAIN?

@croghostrider
Any update on when this will be fixed? Restarting all of the Alexa devices did not address the issue.
Is #26541 going to be part of the 0.99.0 release?
Definitely want my Alexa devices to go back to being useful :)

Same issue here. I've rediscovered devices multiple time with same "Unable to respond" result. I even went back to 97.2 and rediscovered devices. Seems like something has changed on amazons side. Devices use to be listed as "Dimmable Light" now they are all listed as "Royal Phillips Electronics smart device"

What port is your Emulated Hue Bridge running on? After reading some comments here, it could be Amazon's fault to communicate only on port 80. However, I didn't check by myself yet.

Thanks for the info. Mine is set to the default port 8300. I decided to try out nabu casa for now.

@lk3de I had been using the default 8300 for a while and tried using 80 with the same results. No luck

I've been doing some digging in to this. and have sniffed the network traffic between HA and Alexa to try and work out what is going on.
The issue appears to be with alexa 'checking' the bri: value after turning on the light. If the value is still '0' then it makes another request to set the brightness, which doesnt work properly and then reports "That value is out or range for device ____"
The exact symptoms I have is that emulated hue works perfectly for any device which has a (genuine) brightness component, but reports "value out of range" for anything which does not (i.e. switches).
For completeness here is (the important part of) my config.yaml:
switch:
  - platform: mqtt
    name: Aquarium
    command_topic: '/RF_Bridge/cmd'
    payload_on: 'RC,on=41'
    payload_off: 'RC,off=41'

emulated_hue:
  listen_port: 80
  expose_by_default: false

  entities:
    light.livingrm_side:
      name: "test"
      hidden: false
    switch.aquarium:
      name: "fish tank"
      hidden: false

Light.Livingrm_side is a dimmable TRADFRI bulb
Switch.aquarium is an mqtt controlled RF smart plug
A Summary of the network traffic seen when attempting to control switch.aquarium:
"Alexa turn on fish tank"
Alexa -> HA:    PUT request with JSON {"on":true}
HA -> Alexa:    200 'OK' with JSON {"success": {"/lights/switch.aquarium/state/on": true}}
Alexa -> HA:   GET
HA -> Alexa:    {"modelid": "HASS123", "name": "fish tank", "state": {"bri": 0, "hue": null, "on": true, "reachable": true, "sat": null}, "swversion": "123", "type": "Dimmable light", "uniqueid": "switch.aquarium"}
Alexa -> HA:   PUT {"bri":254}
HA -> Alexa:   200 'OK' with JSON {"success": {"/lights/switch.aquarium/state/on": false}}, {"success": {"/lights/switch.aquarium/state/bri": 254}}
Alexa -> HA:   GET
HA -> Alexa:   {"modelid": "HASS123", "name": "fish tank", "state": {"bri": 0, "hue": 0, "on": false, "reachable": true, "sat": 0}, "swversion": "123", "type": "Dimmable light", "uniqueid": "switch.aquarium"}

It appears Alexa requests to turn the switch on (PUT), which is successful. Then checks on it (GET) and is not happy that the brightness value is zero, so makes a second request (PUT) to set the brightness to 254. This 'works' but has the result of HA turning the light off again.
That's all I've got for now...I'll see if I can make any sense of the emulated hue code as to why this happens when I have time!

Minor update:
By changing the definition of the device from mqtt switch to mqtt light, and adding a (dummy) setting
    brightness_command_topic: /null

The device now works correctly with Alexa.

what about scripts?
my setup:
ha 0.98, alexa fw 644580520
discover none since alexa fw update :(

@mattfreeman1701 that sounds promising, but unfortunately all of my devices (none of them work) have a (genuine) brightness component. I will however note that after initially adding them, they adjust to requested brightness the very first time and then error after that.

Can confirm the same "value is out of range for device X response".
Updated to 0.99.0 yesterday, and have changed to port 80 from 8300, the problem still persists.

Yes I have very similar situation here happened since about 1 week or 10 days ago.
I'm in China at first I thought it was because my VPN was down and I thought it will be recover soon automatically.
But recently noticed alexa is still saying my device is not responding even if my VPN is working. So it's nothing else but from Alexa itself i guess the firmware has been upgrade recently and it's no longer well supporting virtual Philips Hue bridge as it used to be?

Fresh install of hassbian yesterday, same setup as Kanga-Who, same error.

The potential fix hasn't been merged yet.  Check out the title and click the PR for details.

do Paulus knows about this issue?
do HA guys doing anything to get out of this Aexa-Hue-HA mistery?

I dropped emulated hue because it constantly breaks because there's about 5 different developers making their own 'enhancements' over the past 5 months.  Then the latest amazon port change sealed the deal.
All of this coupled with the fact that Phillips hue could drop support for hue bridge gen 1's at any moment.  Meaning Amazon could follow suit.

Best alternative at this point is to switch to the Alexa Smart Home Skill. Takes 30 minutes or less to set up with AWS Lambda. That or pay $5/month for Nabu Casa.

It is possible that this is intention of this issue? Money rules the world, really?

@Petro31 Hue has already announced they're dropping the v1 hub next April.

@eracknaphobia that's funny because I thought they would at some point.
@novitibo did you read the response?  You seemed to gloss over the setup that doesn't cost money and focus on the $5 Nabu Casa portion.

Best alternative at this point is to switch to the Alexa Smart Home Skill.

Thanks for the advice @aneisch and @Petro31
Just finished setting up the Alexa Smart Home Skill. Only took 15-20 minutes mainly because of all the account creation. Works like a charm!

@mattfreeman1701
How did you change the description of your devices?

I'm a bit confused over where the problem may be. I'm on Hassio 98.5 and I initially had a file in config/emulated_hue_ids.json which contain my two virtual lights. (These worked fine under Hassio 88.4 but my SD card died about the same time as all these Hue problems started and now this is more difficult to pin down.)
After rebuilding my Pi using version 2.12 - Hassio 98.5, I did not have an emulated_hue folder in my custom components folder (but I did have the emulated_hue_ids.json file in config.)
So while trying to figure out why my emulated hue virtual bulbs were returning the wrong brightness valuse at the low end (1%-4%), I noticed the Alexa app's "device is unresponsive" and "does not support requested value" error messages.
After much reading, I found that I needed to change to port 80, so I did, I also found that I did not have the custom_components/emulated_hue folder and files - yet still was getting some traffic between Alexa and emulated hue bulbs although it was incorrect and error filled.
I added the custom_component/emulated_hue/hue_api.py script and hard booted the pi. No change in behavior.
I could see my two devices on port 80 as:
{"1": {"modelid": "HASS123", "name": "security check", "state": {"bri": 0, "hue": 0, "on": false, "reachable": true, "sat": 0}, "swversion": "123", "type": "Dimmable light", "uniqueid": "light.security_check"}, "2": {"modelid": "HASS123", "name": "Alexa Virtual Light", "state": {"bri": 0, "hue": 0, "on": false, "reachable": true, "sat": 0}, "swversion": "123", "type": "Dimmable light", "uniqueid": "light.alexa_virtual"}}
which seems to look correct but when I try to access them using the Alexa app, I see:
{"1": {"modelid": "HASS123", "name": "security check", "state": {"bri": 0, "hue": 0, "on": false, "reachable": true, "sat": 0}, "swversion": "123", "type": "Dimmable light", "uniqueid": "light.security_check"}, "2": {"modelid": "HASS123", "name": "Alexa Virtual Light", "state": {"bri": 36, "hue": null, "on": true, "reachable": true, "sat": null}, "swversion": "123", "type": "Dimmable light", "uniqueid": "light.alexa_virtual"}}
which has some null returns.
As part f my troubleshooting, I changed the modelId and swVersion in the hue_api.py to 133 and hard booted the pi again. But as you can see, it is returning 123 anyway.  However, when I access the port 80 api/pi/lights to see the above json returns, I also find a correlating error in the log:
Error handling request Traceback (most recent call last):   File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 418, in start     resp = await task   File "/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py", line 458, in _handle     resp = await handler(request)   File "/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py", line 119, in impl     return await handler(request)   File "/usr/src/homeassistant/homeassistant/components/http/real_ip.py", line 40, in real_ip_middleware     return await handler(request)   File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 125, in handle     result = handler(request, **request.match_info)   File "/usr/src/homeassistant/homeassistant/components/emulated_hue/hue_api.py", line 201, in get     entity = hass.states.get(entity_id)   File "/usr/src/homeassistant/homeassistant/core.py", line 886, in get     return self._states.get(entity_id.lower()) AttributeError: 'NoneType' object has no attribute 'lower'
where line 201 is not part of get_entity. It's the second lin in:
    async def put(self, request, username, entity_number):         """Process a request to set the state of an individual light."""         if not is_local(request[KEY_REAL_IP]):             return self.json_message('only local IPs allowed',                                      HTTP_BAD_REQUEST)
So a few questions arise:

How was my HA Hassio  implementation interfacing with emulated hue after only adding the emulated_hue: devices in configuration.yaml?
Why does it return null values after an interaction with Alexa?
Why doesn't the custom_components api folder have no effect?

While the Alexa app shows error states as I pointed out, I can interact with it almost successfully except for the wrong brightness vales at 1% - 4%.
I hope this is clear enough to help the efforts of those working on the problem.
Cheers,
Bart

Should be fixed by #28317 .


Import/Export collections from private github repos to share among teams.

Is your feature request related to a problem? Please describe.
I want to make collections version-controlled and shareable among teams from Github. Alternatively, If we can have roles permission and collections on the cloud with postwoman as a service.
Describe the solution you'd like
User should be able to sync their collections with another team member, using Github roles/permission on the synced repository.
Describe alternatives you've considered
One can always take an export and upload it to their repo as a JSON file to keep versioning maintained. The goal is to reuse Github's version control and roles/permissions and to avoid manually updating collections by exporting and importing.

Possible duplicate of #580 which will also cover roles and permissions for collections.


Add the possibility to create custom LinearTasks in python

If you are a python user and you want to create inverse kinematics (IK) or a task-based inverse
dynamics (TSID) task, you do need to write a C++ code. Indeed it is possible to write a class that inherits from TSIDLinearTask or IKLinearTask  and passes it to tsid or ik solvers. The following snippet can be used as starting point to build a custom TSID task, a similar approach can be used to define a custom IK task
import bipedal_locomotion_framework.bindings as blf

class CustomTSIDTask(blf.tsid.TSIDLinearTask):
    """ CustomTSIDTask represents a custom task for the tsid solver.

    The class must define the following functions:
    __init__(self): the constructor
    size(self) -> Get the size of the task. (I.e the number of rows of the vector b)
    is_valid(self) -> Determines the validity of the objects retrieved with getA() and getB()
    type(self) -> Get the type of the task. Namely equality or inequality

    Furthemore you have to populate the following attrubutes defined in TSIDLinearTask:
    self._description:str -> contains the description of the task
    self._A:numpy.ndarray[float64[m, n]]) -> matrix that describes the task A * x = b
    self._b: numpy.ndarray[float64[m, 1]]) -> vector that describes the task A * x = b

    Depending on the content of the task you may need to reimplement the following methods
    initialize(self, param_handler: blf.parameters_handler.IParameterHandler) -> usefull function to set parameters to the task
    set_variables_handler(self, variables_handler: blf.system.VariablesHandler) -> usefull function to set the variables
    update(self) -> update the content of the task
    """

    def __init__(self):

        blf.tsid.TSIDLinearTask.__init__(self)  # Without this, a TypeError is raised.

        # set the description of the task
        self._description = "Custom task"

    def size(self):
        # this is the number of rows of the vector b (in this example is equal to 1)
        return 1

    def is_valid(self):
        return True

    def type(self):
        # the types are defined in blf.tsid.TSIDLinearTask.Type
        return blf.tsid.TSIDLinearTask.Type.equality

Then you can use your custom task as follows
import bipedal_locomotion_framework.bindings as blf

# Instantiate the task
custom_task = CustomTSIDTask()

# Initialize your task
custom_task.initialize(param_handler)

# Create the solver
solver = blf.tsid.QPTSID()
priority = 0
solver.add_task(custom_task, 'custom_task', priority)

On conda macos there is this nice failure
../bindings/python/TSID/tests/test_TSID.py Fatal Python error: Illegal instruction

Current thread 0x000000011c3e5dc0 (most recent call first):
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/_pytest/python.py", line 183 in pytest_pyfunc_call
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/_pytest/python.py", line 1641 in runtest
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/_pytest/runner.py", line 162 in pytest_runtest_call
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/_pytest/runner.py", line 255 in <lambda>
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/_pytest/runner.py", line 311 in from_call
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/_pytest/runner.py", line 254 in call_runtest_hook
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/_pytest/runner.py", line 215 in call_and_report
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/_pytest/runner.py", line 126 in runtestprotocol
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/_pytest/runner.py", line 109 in pytest_runtest_protocol
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/_pytest/main.py", line 348 in pytest_runtestloop
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/_pytest/main.py", line 323 in _main
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/_pytest/main.py", line 269 in wrap_session
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/_pytest/main.py", line 316 in pytest_cmdline_main
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/_pytest/config/__init__.py", line 162 in main
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/_pytest/config/__init__.py", line 185 in console_main
  File "/usr/local/miniconda/envs/test/lib/python3.9/site-packages/pytest/__main__.py", line 5 in <module>
  File "/usr/local/miniconda/envs/test/lib/python3.9/runpy.py", line 87 in _run_code
  File "/usr/local/miniconda/envs/test/lib/python3.9/runpy.py", line 197 in _run_module_as_main

Probably related to conda/conda#9678 . Not sure what a quick workaround is.

Why is this happening now?

CC @paolo-viceconte @diegoferigo @CarlottaSartore

Probably related to conda/conda#9678 . Not sure what a quick workaround is.

Why is this happening now?

It is possible that the other tests were not using numpy or they were not using some specific numpy function that is instead used by this test?

It is possible that the other tests were not using numpy or they were not using some specific numpy function that is instead used by this test?

well np.zeros(), slicing and np.ones() were not used before
temp = np.zeros((10, variables_handler.get_number_of_variables()))
temp[:, variable.offset] = np.ones(10)
self._b = np.ones(10)

It is possible that the other tests were not using numpy or they were not using some specific numpy function that is instead used by this test?

well np.zeros(), slicing and np.ones() were not used before
temp = np.zeros((10, variables_handler.get_number_of_variables()))
temp[:, variable.offset] = np.ones(10)
self._b = np.ones(10)

I suspect this is what is triggering it. Note that I guess this is a problem that will not occur on real machines, just something that is occuring with virtual machine that do not support AVX instructions. For the time being you can just skip those tests on macOS.

In https://github.com/ami-iit/bipedal-locomotion-framework/pull/481 I tried to switch the blas implementation to netlib and blis, but the issue is still there, so I guess it is not a problem of blas implementation.

Bingo this is the problem:
I tested with https://github.com/GiulioRomualdi/blf-fastmac
blf.tsid.TSIDLinearTask.__init__(self)

however, I don't know how to fix it since that line is required as explained in https://pybind11.readthedocs.io/en/stable/advanced/classes.html#overriding-virtual-functions-in-python

(robotologyenv) Mac-1638874300540:build runner$ python3 test.py
[2021-12-07 11:21:46.641] [thread: 106743] [blf] [info] [QPTSID::initialize] 'verbosity' not found. T
he following parameter will be used 'false'.
Illegal instruction: 4

https://stackoverflow.com/questions/14268887/what-is-the-illegal-instruction-4-error-and-why-does-mmacosx-version-min-10

Are you sure that python3 is the one provided in the conda environment? What is the output of which python3?

Are you sure that python3 is the one provided in the conda environment? What is the output of which python3?

/Users/runner/miniforge3/envs/robotologyenv/bin/python3

In the recent past we had an "Illegal instruction" error for what in the end was just wrong memory access (see https://github.com/robotology/yarp-telemetry/issues/110). Did you tried to run python that runs this test on Linux under valgrind?

However, at this point for me we can disable the conda/macOS test and proceed.

That one was actually the problem, the test runs on fastmac


Ability to use the datetimepicker without the full Bootstrap CSS

As discussed in this issue: https://github.com/Eonasdan/bootstrap-datetimepicker/issues/1199
I gave it a first try to create a standalone CSS file. It seems to work pretty good already, at least on a page with just the datetimepicker. I've tested both inline and dropdown variant.
It adds one dependency though: it requires the glyphicon font from Bootstrap.

@Eonasdan does this remove any dependancy on bootstrap?

@sidonaldson removes the css dependency (you'll still need the font). You might still need some of the js see http://eonasdan.github.io/bootstrap-datetimepicker/Installing/#manual


Question about Preventing Outlier Tokens during Inference

Thank you for your very interesting work. I would like to ask about something mentioned in your paper: "Considering the auto-regressive inference pipeline of LLMs, we store these prefix tokens in the KV cache to prevent generating new outlier tokens during inference." I don't understand why storing outlier tokens in the prefix cache prevents the generation of new outlier tokens during inference. Could you please explain this further?

https://openreview.net/forum?id=vw0NurJ7UX


Add consistent bidder param types to docs

I'm in the process of trying to automate a 'Prebid builder' UI and would like bidder params consistently documented like below so new bidders can be scraped easily and added to our system.

Name
Scope
Description
Example
Type

one
required
Sets one.
'abcdefg'
string

two
required
Sets two.
123456
integer

three
optional
Sets three.
1.23456
float

four
optional
Sets four.
true
boolean

five
optional
Sets five.
{ cool: true }
object

six
optional
Sets six.
['300x250']
Array<string>

seven
optional
Sets seven.
['300x250', true]
Array<any>

eight
optional
Sets eight.
function () { }
function

I've currently got this type data in JSON format and could submit a PR quite easily to modify the docs.

thanks for the PR willviles.


Refactor lexer

I feel like the lexer could be simplified by dumbing the code down a bit then using a regex to validate floats and numbers.

Hey!
I just skimmed the lexer code; it doesn't look too complicated.  There is a talk by Rob Pike about writing lexers in Go, which details how the lexer for text/template is implemented.  Maybe that proves useful.

Thanks, I'll check out the code there. It's probably pretty good to compare a few techniques to implementing this.
Compared with https://github.com/rui314/8cc/blob/master/lex.c , The state machines in the  number/float/string lexing take up a bunch of space, even if it is fairly simple.

I think the performance of the lexer is fairly critical, currently i think most of the time is spent allocating new objects. I really want to emphasize clean code over performance as much as possible.


Modification on the statement in English output, to avoid isues on the CSV output

Details
The statement to English code had one bug on the if/else as the conditions != "\n" portion matched when the string was empty. Additionally, I've trimmed some new lines that were not necessary to tidy up the output.
Feel free to change the commit

worked with @adrivillab-bf. I think we are good to go here.


Fixing how build_ext is being imported to allow setup.py to run succe…

A StackOverflow question was posted with reference to this project:
http://stackoverflow.com/questions/32628134/distutils-setup-py-install-module-object-is-not-callable
There seems to be an issue in the setup.py on how the build_ext is attempted to be run. I tested on my end and the issue is when are not using the Distutils packaged inside Cython and your except block is executed instead to use the standard distutils package.
I ran the setup.py on my machine with the mod to ensure it ran.

Thanks.


sampleHeight bug

code:
let cartographicPosition = new Cesium.Cartographic()
cartographicPosition.longitude = mapUtil.angleToRadian(113.939499)
cartographicPosition.latitude = mapUtil.angleToRadian(22.5262237)
let takeOffheight = scene.sampleHeight(cartographicPosition)
result:
TypeError: Cannot read property 'x' of undefined
at n (Cesium.js:445)
at Function.s.fromCartesian (Cesium.js:445)
at we.sampleHeight (Cesium.js:526)

Hi @hieeyh
What happens when you click "Sample height" and "Sample height supported" in this demo?
Demo
It's possible that sampleHeight isn't supported on your setup. sampleHeightSupported would be the first thing to check.

Hi @hieeyh
What happens when you click "Sample height" and "Sample height supported" in this demo?
Demo
It's possible that sampleHeight isn't supported on your setup. sampleHeightSupported would be the first thing to check.

If theris a 2D billboard, it will report this error. But if exclude this 2D billboard, sometimes success, sometimes fail.

The example I posted should now work in #7115.
Example on offscreen-picking branch
@hieeyh if you have a chance would you mind testing your app with this build to see if it fixed your problem?
A link to download the build is here: http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/offscreen-picking/Cesium-1.49.0-offscreen-picking29051.zip


runtime: revert part of #6206

runtime: revert part of #6206
In container bundle, the runtime file has been reserved for runtime's
BinaryName like runc or crun 1. In #6206, we supported to use
absolute path as shim runtime name and also stored it in runtime
file2. It will be conflict if user wants to use BinaryName instead of
empty default value.
Before we figure out new filename for shim binary path, I would like to
revert the code from #6206 because the information has been stored in
container store service. If the shim runtime is absolute binary path,
we can just read it from container store service. If it is normal shim name
like io.containerd.runc.v2, we need to resolve it into binary path again,
which is the same to before pr #6206.
Fixes: #6534
Signed-off-by: Wei Fu<EMAIL_ADDRESS>

#6206

Before we figure out new filename for shim binary path, I would like to

revert the code
Should we figure out new name instead of reverting? :)
runtime-path ?

In container ecosystem, runtime is confusing word :) at least to me. And we are introducing sandbox api and so yeah. Runtime looks like any words 😂 I am ok to use other filename to fix it. Maybe less-confusing word

would shim-binary-path better?

#6536


Will building-blocks support collisions between grids?

This project seems very nice; I'm probably going to be using it as a voxel engine for my game (https://github.com/iMplode-nZ/Autofactory), but I need to run collisions between two different voxel grids, in which the grids can be split up. Will building-blocks support this or will I have to implement it myself? (Side note: It seems that this is most optimal in an octree representation of voxels)

BB does have an OctreeDBVT structure here.
Right now it only supports ray-casting and a more general visitor pattern.
I think it could eventually support collisions between two OctreeDBVTs. Maybe implementing some traits from ncollide3d could also help.


Tweak the mainpage

Goal
Discuss with your peers what you would like the homepage to show! It can be a good opportunity to tweak the app colors/layout etc.
As in #8, keep it simple (no big images, external assets, etc)
This can be an ongoing issue while you all keep implementing things.

I would like to propose a  small change to the homepage layout and the overall UI, which would include integrating it with @GusMeg's animated background #34.
If allowed, I'm ready to code.

Hello 👋! I would also like to contribute to this issue by adding more features and interactive aspects to our mainpage. I would like to create a typewriter effect highlighting "Buidl Guidl Batch 1" with a link embedded in our image, to integrate with @GusMeg animation in #34
Here's a demo on what I have built:
https://github.com/BuidlGuidl/batch1.buidlguidl.com/assets/93211672/a5889a47-893c-4e2d-8044-1ef34196b412
To take full advantage of learning with BG fams, I will also submit a PR for feedback 😄

Feel free to add more tweaks to it (as in #35), but I think this can be considered "done" :)


dracut: add module to start iSCSI root disk

The upstream Dracut iscsi module is much more than we need, and would require several workarounds for CL. For now, support only Oracle OCI in a hardcoded way.
For https://github.com/coreos/bugs/issues/2036.

Updated for comments.

If we want a more generic solution later, it'll probably still be cleaner to parameterize this code than to use the upstream module.


[Feature]: JOSS REVIEW Editable install deprecation

Summary
I cloned and performed an editable install using pip:
git clone https://github.com/IPESE/REHO.git
cd REHO
pip install -e . --extra-index-url https://pypi.ampl.com

and received the following warning:
DEPRECATION: Legacy editable install of REHO==1.1.4 from file:///Users/wusher_1/repository/REHO (setup.py develop) is deprecated. pip 25.0 will enforce this behaviour change. A possible replacement is to add a pyproject.toml or enable --use-pep517, and use setuptools >= 64. If the resulting installation is not behaving as expected, try using --config-settings editable_mode=compat. Please consult the setuptools documentation for more information. Discussion can be found at https://github.com/pypa/pip/issues/11457

Detailed design
Your design
Notes and comments
Your notes

Looks good.