mbed.h: No such file or directory with mbed new --mbedlib

mbed new --mbedlib not expand .h files.
Does https://mbed.org/users/mbed_official/code/mbed/builds/3a7713b1edbc has problem?
C:\mbed>mbed new test --mbedlib
[mbed] Creating new program "test" (git)
[mbed] Adding library "mbed" from "https://mbed.org/users/mbed_official/code/mbed/builds" at branch/tag "tip"
[mbed] Unpacking library build "3a7713b1edbc" in "C:\mbed\test\mbed"
[mbed] Unpacking library build "3a7713b1edbc" in "C:\mbed\test\mbed"
[mbed] Updating reference "mbed" -> "https://mbed.org/users/mbed_official/code/mbed/builds/3a7713b1edbc"
[mbed] Couldn't find build tools in your program. Downloading the mbed 2.0 SDK tools...

C:\mbed>cd test

C:\mbed\test>notepad main.cpp

C:\mbed\test>mbed compile -t GCC_ARM -m LPC11U35_401
Building project test (LPC11U35_401, GCC_ARM)
Scan: test
Compile [100.0%]: main.cpp
[Fatal Error] main.cpp@1,18: mbed.h: No such file or directory
[ERROR] .\main.cpp:1:18: fatal error: mbed.h: No such file or directory
 #include "mbed.h"
                  ^
compilation terminated.

[mbed] ERROR: "c:\python27\python.exe" returned error.
       Code: 1
       Path: "C:\mbed\test"
       Command: "c:\python27\python.exe -u C:\mbed\test\.temp\tools\make.py -t GCC_ARM -m LPC11U35_401 --source . --build .\BUILD\LPC11U35_401\GCC_ARM"
       Tip: You could retry the last command with "-v" flag for verbose output
---

C:\mbed\test>

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-345

@theotherjimmy @Timmmm Any progress on this?

Hi @screamerbg, Thanks for the reminder.
Hi @Timmmm, that file is part of the tools-release that we use for the online compiler. I have created a new tools release based on 5.11.3 that contains the diff you sent me in email. I'm going to test it as part of mbed-sdk-tools real quick, and push that into it's upstream when I'm done.

any news on how to build for mbed2 from mbed-cli ? I'm trying to reproduce the online compiler output for a nrf51_dongle blinkie, and am stuck at this point.
Thanks for your help!

@screamerbg @theotherjimmy
When I download zipped archive from below:
https://os.mbed.com/users/mbed_official/code/mbed/archive/3a7713b1edbc.zip
I could not find following files in the archive:
drivers/*
hal/*
platform/*
mbed.h
targets.json

Also, same result (missing files in the mbed 2 library) by following command:
$ mbed import https://os.mbed.com/teams/mbed/code/mbed_blinky/
$ cd mbed_blinky
$ mbed deploy

@toyowata I replicated this issue as well:
~/Desktop/mbed-classic-program $ mbed deploy
[mbed] Working path "/Users/jenplu01/Desktop/mbed-classic-program" (program)
[mbed] Updating library "mbed" to rev #3a7713b1edbc
[mbed] Updating the mbed 2.0 SDK tools...
~/Desktop/mbed-classic-program $ mbed compile
[mbed] Working path "/Users/jenplu01/Desktop/mbed-classic-program" (program)
[Error] @,: Compiler version mismatch: Have 7.2.1; expected version >= 6.0.0 and < 7.0.0
Building project mbed-classic-program (K64F, GCC_ARM)
Scan: mbed-classic-program
Compile [100.0%]: main.cpp
[Fatal Error] main.cpp@1,10: mbed.h: No such file or directory
[ERROR] ./main.cpp:1:10: fatal error: mbed.h: No such file or directory
 #include "mbed.h"
          ^~~~~~~~
compilation terminated.

[mbed] ERROR<EMAIL_ADDRESS>returned error.
       Code: 1
       Path: "/Users/jenplu01/Desktop/mbed-classic-program"
       Command<EMAIL_ADDRESS>-u /Users/jenplu01/Desktop/mbed-classic-program/.temp/tools/make.py -t gcc_arm -m k64f --source . --build ./BUILD/K64F/GCC_ARM"
       Tip: You could retry the last command with "-v" flag for verbose output
---

Hey folks, I took a look and indeed mbed.h is missing for the releases with the hashes 65be27845400 and 3a7713b1edbc. I can confirm what @toyowata said (thanks very much!), the e95d10626187 revision does contain the mbed.h. If you need to work offline, I would recommend using that revision if possible. If you need the latest versions, I have found that the online compiler still seems to be working. I will be pursuing this issue more, thanks for raising this (and sorry for the slow response).

Hey everyone, just dropping in on you all to say I've encountered this issue today with revision 65be27845400, trying to compile mbed OS 2 with mbed CLI for a STM32F042K6 eval board. Anything new on this issue ?
`mbed compile --clean --target nucleo_f042k6 --toolchain GCC_ARM --profile debug
[mbed] Working path "/home/corentin/dev/test-mbed2-1" (program)
WARNING: MBED_GCC_ARM_PATH set as environment variable but doesn't exist
[Error] @,: Compiler version mismatch: Have 7.3.1; expected version >= 6.0.0 and < 7.0.0
Building project test-mbed2-1 (NUCLEO_F042K6, GCC_ARM)
Scan: test-mbed2-1
Compile [100.0%]: main.cpp
[Fatal Error] main.cpp@1,10: mbed.h: No such file or directory
[ERROR] ./main.cpp:1:10: fatal error: mbed.h: No such file or directory
#include "mbed.h"
^~~~~~~~
compilation terminated.
[mbed] ERROR: "/usr/bin/python" returned error.
Code: 1
Path: "/home/corentin/dev/test-mbed2-1"
Command: "/usr/bin/python -u /home/corentin/dev/test-mbed2-1/.temp/tools/make.py -t GCC_ARM -m nucleo_f042k6 --profile debug --source . --build ./BUILD/NUCLEO_F042K6/GCC_ARM-DEBUG -c"
Tip: You could retry the last command with "-v" flag for verbose output
---`

Thank you for raising this issue. Please note we have updated our policies and
now only defects should be raised directly in GitHub. Going forward questions and
enhancements will be considered in our forums, https://forums.mbed.com/ . If this
issue is still relevant please re-raise it there.
This GitHub issue will now be closed.

Apologies, this was closed in error by the automated bot - re-opening.

Internal Jira reference: https://jira.arm.com/browse/IOTBTOOL-467

How am i supposed to switch to the old revision? I changed my mbed.bld to

https://mbed.org/users/mbed_official/code/mbed/builds/e95d10626187

and ran mbed deploy

[mbed] Working path "/home/arjun/src/030" (program)
[mbed] Adding library "mbed" from "https://mbed.org/users/mbed_official/code/mbed/builds" at rev >#e95d10626187
[mbed] Unpacking library build "e95d10626187" in "/home/arjun/src/030/mbed"
[mbed] Updating the mbed 2.0 SDK tools...

but mbed still points to the latest revision
ls mbed

65be27845400/

Yes, this is urgent. It is no longer possible to retrieve older builds.
The issue with the newer builds appears to be related to the zip command failing to complete the job. There are also a lot of missing targets in the archive.

Still a problem.
This is issue should be fixed  ASAP to support Mbed OS 2 on small targets with 4 Kb of RAM.

is there any way to bump up the priority of this problem? Its been OVER A YEAR and this entire mbed platform remains COMPLETELY USELESS AND BROKEN.

not sure about python2 but with python 3 on 18.04
export program from webui as gcc-arm
edit line 39 in .temp/tools/build_profiles.py
from
if MBED_SDK_REV_MAP.has_key(build):
to
if build in MBED_SDK_REV_MAP:
manually install pyelftools
I manually downloaded the latest build rev #65be27845400 as well unpacked that into /mbed/.bld
and i think it worked after that, sorry for a little vague, going off memory

I manually downloaded the latest build rev #65be27845400 as well unpacked that into /mbed/.bld

If you use the fix in #969 then the manual download should not be needed. With this fix, mbed will download the revision successfully; since you were using Python3, it was getting stuck in an infinite loop after the file was downloaded.

FYI.  The step below works for me.
# install pyenv
# install python 2.7.15
# install gcc-arm-none-eabi-6-2017-q2-update

pip install virtualenv
python -m virtualenv .venv2
.venv2\Script\activate

pip install mbed-cli==1.10.1 pyelftools jsonschema

mkdir test
cd test
hg clone https://os.mbed.com/users/mbed_official/code/mbed-sdk-tools/ tools
pip install -r .\tools\requirements.txt
git clone https://github.com/ARMmbed/mbed-dev

# create your main.cpp

mbed compile -m your_target -t gcc_arm

It is all great, but mbed.h is still not found even with Python 2:
cd /tmp
$ mbed config -L
[mbed] Global config:
GCC_ARM_PATH=/home/user/Software/gcc-arm-none-eabi-9-2019-q4-major/bin

$ mbed new test-lib --mbedlib
[mbed] Working path "/tmp" (directory)
[mbed] Creating new program "test-lib" (git)
[mbed] Adding library "mbed" from "https://mbed.org/users/mbed_official/code/mbed/builds" at branch/tag "tip"
[mbed] Unpacking library build "65be27845400" in "/tmp/test-lib/mbed"
[mbed] Unpacking library build "65be27845400" in "/tmp/test-lib/mbed"
[mbed] Updating reference "mbed" -> "https://mbed.org/users/mbed_official/code/mbed/builds/65be27845400"
[mbed] Couldn't find build tools in your program. Downloading the mbed 2.0 SDK tools...

$ cd test-lib/
$ find . -name mbed.h
$ # (empty output)

cd /tmp
mbed import https://os.mbed.com/users/mbed_official/code/mbed_blinky/
cd mbed_blinky

$ mbed import https://os.mbed.com/users/mbed_official/code/mbed_blinky/
[mbed] Working path "/home/mate" (directory)
[mbed] Importing program "mbed_blinky" from "https://os.mbed.com/users/mbed_official/code/mbed_blinky" at latest revision in the current branch
[mbed] Adding library "mbed" from "https://mbed.org/users/mbed_official/code/mbed/builds" at rev #176b8275d35d
[mbed] Downloading library build "176b8275d35d" (might take a while)
[mbed] Unpacking library build "176b8275d35d" in "/home/mate/mbed_blinky/mbed"
[mbed] Couldn't find build tools in your program. Downloading the mbed 2.0 SDK tools...
[mbed] Auto-installing missing Python modules (jinja2, pyyaml, mbed_ls, mbed_host_tests, mbed_greentea, fuzzywuzzy)...
$ find . -name mbed.h
$ # (empty output)

So there is still nothing to compile. Any thoughts?

Hi @N0rbert
mbed new command
As reported here, library version 3a7713b1edbc and 65be27845400 don't have an mbed.h file and other header files.
You can use the hash version e95d10626187 or early one.
https://os.mbed.com/users/mbed_official/code/mbed/shortlog/
Open the mbed.bld by editor and change to...
http://mbed.org/users/mbed_official/code/mbed/builds/e95d10626187

Then deploy again with cache off.
$ mbed cache off
$ mbed deploy

Importing the mbed_blinky
I think the 176b8275d35d should be fine, but probably enabling library cache by Mbed-CLI seems working unexpectedly.  Maybe you can use the command below:
$ mbed cache off
$ mbed import https://os.mbed.com/users/mbed_official/code/mbed_blinky/

Thanks @toyowata. Your suggestion to change mbed.bld to that line and then mbed cache off and mbed deploy fixed the issue for me. Confusingly, ls mbed will still use the old revision name. So don't be mislead by the name of the directory (this must be a separate bug?)! I also needed to revert my CMSIS repo to an older version (5.4.0 worked for what I was trying to compile).

@toyowata thanks, but it fails.
$ cd /tmp
$ hg clone https://os.mbed.com/users/mbed_official/code/mbed_blinky/
$ cd /tmp/mbed_blinky
$ mbed cache off
$ echo "http://mbed.org/users/mbed_official/code/mbed/builds/e95d10626187" > mbed.bld
$ cat mbed.bld
http://mbed.org/users/mbed_official/code/mbed/builds/e95d10626187
$ mbed deploy
[mbed] Working path "/tmp/mbed_blinky" (program)
[mbed] Adding library "mbed" from "https://mbed.org/users/mbed_official/code/mbed/builds" at rev #e95d10626187
[mbed] Downloading library build "e95d10626187" (might take a while)
[mbed] Unpacking library build "e95d10626187" in "/tmp/mbed_blinky/mbed"
[mbed] Couldn't find build tools in your program. Downloading the mbed 2.0 SDK tools...
[mbed] Updating the mbed 2.0 SDK tools...

ends with strange thing that e95d10626187 is not a e95d10626187, it is 65be27845400:
$ ls mbed
65be27845400
$ find . -name mbed.h
$ # (no output)

@arvoelke @N0rbert
mbed deploy with -v option shows detail information.
$ mbed cache off
$ cat mbed.bld
http://mbed.org/users/mbed_official/code/mbed/builds/e95d10626187
$ mbed deploy -v
[mbed] Working path "/Users/toyowata/dev/mbed_blinky" (program)
[mbed] Adding library "mbed" from "https://mbed.org/users/mbed_official/code/mbed/builds" at rev #e95d10626187
[mbed] Trying to guess source control management tool. Supported SCMs: bld, hg, git
[mbed] Setting url to "http://mbed.org/users/mbed_official/code/mbed/builds/65be27845400" in /Users/toyowata/dev/mbed_blinky/mbed
[mbed] Downloading library build "e95d10626187" (might take a while)
^C[mbed] User aborted!
$ mbed ls
[mbed] Working path "/Users/toyowata/dev/mbed_blinky" (program)
mbed_blinky (#3451e643c64c, tag: tip)
`- mbed (#65be27845400)

hmm, it seems the Mbed-CLI download latest release of the library.
Now, my suggestion to use this step:
https://github.com/ARMmbed/mbed-cli/issues/805#issuecomment-610120652


[vx.dev] implements #128

[vx.dev] This PR implements #128, created by vx.dev.

[vx.dev]: This code snippet creates a login page with a registration option, a top menu, and a footer with a copyright statement. The login form defaults to phone number authentication. The UI is designed to be visually appealing with a clean and modern look.


The upload provider "strapi-provider-upload-yandex-cloud" doesn't implement the uploadStream function (Strapi 4.2.0)

Hello,
After I upgraded Strapi to 4.2.0 version, I run the "strapi develop" script in my project and get the followitn message:
Warning: The upload provider "strapi-provider-upload-yandex-cloud" doesn't implement the uploadStream function. Strapi will fallback on the upload method. Some performa
nce issues may occur.
Nevertheless, the administration panel works properly (http://localhost:1337/admin).
However, when I try to open "Media Library", I get an error in the Chrome DevTools - console:
TypeError: Cannot read properties of undefined (reading 'allPermissions')
Could you please solve the issue?

There was a problem in the original upload plugin: https://github.com/strapi/strapi/pull/13370
It's fixed in Strapi v 4.2.2.
Try to update to this version. Is the problem still active?

You are right, the problem has been solved, thank you)


RHDEVDOCS-4705-edit-thanosrulequeueisdroppingalerts-runbook

Language and style edits for this runbook.

/lgtm


Spec: In checked mode, void should allow any value.

This is the specification issue for #28935.

Punting to 1.24 per dart-leads discussion.

@dgrove
Dan is this a feature we want post 1.24 Dartium?

@eernstg seems like this is in the spec. Ready to close?

Done in 122345e3568e3191a7a91af2686c18d8ed40369f, closing.


feat(validate): export revalidate event from index

closes #102

Pull Request Test Coverage Report for Build 343

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 334:
0.0%

Covered Lines:
644

Relevant Lines:
644

💛  - Coveralls

Pull Request Test Coverage Report for Build 343

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 334:
0.0%

Covered Lines:
644

Relevant Lines:
644

💛  - Coveralls

Pull Request Test Coverage Report for Build 343

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 334:
0.0%

Covered Lines:
644

Relevant Lines:
644

💛  - Coveralls

Pull Request Test Coverage Report for Build 343

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 334:
0.0%

Covered Lines:
644

Relevant Lines:
644

💛  - Coveralls


Respond to ethics reviews

Summary

Following the ethics submission (c.f. #243), we now got feedback on our ethics submission. I've copied the responses/requests for clarifications into a Google Doc
Deadline
No strict deadline, but ideally asap!
What needs to be done?

[x] Get current ethics form into the doc
[x] Decide how to address the open questions
[x] Submit our response

Who can help?

It would be great to have

@GeorgiaHCA
@KirstieJane

help with this, given that you've both worked on the original submissions!

Updates

@GeorgiaHCA submitted our response last week, so this is done ✅

And we got the approval today! 🎉


Typo fixed in ClosingStandardOutputStreams.md

A typo has been fixed.

@maintainer please review this PR and merge if everything is okay!


Add filter node in the query plan for conditional joins

This refactors the implementation of conditional inner joins.  The post-join filter is now an explicit node in the query plan rather than an implementation detail of the join node.  This has the advantage of adding visibility into how many rows were manifested from the join and subsequently filtered.
Despite joins no longer using the conditional expression after this PR, I left the condition parameter in place for now.  When AST conditional join support is added to the plugin, we can use this condition parameter to convey an expression that should be translated to an AST and processed directly as part of the join rather than as a post-filter.

build


Individual background color option

It would be great if a background color can be applied per image
(when converting an alphatransparent PNG/transparent GIF to flat JPEG).
Related issue: https://github.com/herrstucki/responsive-loader/issues/50

It can: see https://github.com/herrstucki/responsive-loader/blob/master/test/sharp/index.js#L43 for an example.


Sprite asset with image format .png not rendering on safari

Hi!
I made a little hybrid game, i' tested all way around on edge, firefox, chrome, (also on android) and everything is fine except for safari. When i open safari i got a surprise. the player sprite becomes invisible. I have no idea why. Even if i use .jpg the image stills invalid.
Additional info:
i exported the image from gimp to .png (the same as others sprites)
filesize:31kb
resolution:284x175
Any suggestion? Should i change the .png format to another suggested? have you been here before? The image is just

Did you look at the network calls? Does the image load properly?

Thanks for your response!
Heres the link http://<IP_ADDRESS>:8000/
Actually works on chrome, firefox and edge. But the player sprites doesn't load on safari


Update for Xcode10 iOS 12

For #692
This PR will make the project build with Xcode 10. Involves updating pod dependencies.
@James-Sangalli Only merge after you have verified this builds with Xcode 9.x or you have upgraded to Xcode 10. It breaks on my Xcode 9.x, but maybe because I also have Xcode 10 on the same machine.

@James-Sangalli wonderful. Thanks!


Order of bootstrap grid system wrong

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
I seem to have found a problem with bootstrap. I'm using v5.3.0 via node modules structure (rather than the cdn) and when using these classes in this order:

test

col-xl-* always seem to get skipped. (basicly you cant' use xl, cause it get's overridden by the rest.)
I looked into the file structure and it seems that bootstrap is importing it via this way:

xl
sm
md
lg
xxl

I basicly can't use xl, since it get's overridden by the rest except for col-12
Reduced test cases
/
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome, Microsoft Edge
What version of Bootstrap are you using?
^v5.3.0

using a grid layout directly on  is not semantically appropriate. however applying so many classes might not achieve responsive behavior, usually you have to specify the few break points.
Bootstrap Grid
Bootstrap gird means to create layout on the basis of row and column.
so your output should be like this
`

Test

 `

You'll need to check your compiling tools so that they match our own. In our compiled CSS, the order is correct. This can be done with Clean CSS, CSS Nano, or similar. See<EMAIL_ADDRESS>for example.


Deployment on Dedicated Nodes Error Messages

Tested on devnet
Trying to deploy on any of the nodes available on the dedicated nodes tab in the portal without reserving a node gives an error as it is supposed to but the error is not clear or user friendly
Error: Failed to create contract on node: 21 due to Failed to apply createNodeContract in module smartContractModule with 21,,fcc667bbad59c37d2eb093e63fceed80,0 due to error: undefined

Suggestion: Dedicated nodes should not be available in the capacity filter for deployment once they are reserved or marked as dedicated nodes and available for reservation or they could be available in the capacity filter but marked as reserved/dedicated node.

Same issue when deploying from terraform the issue is unclear and the error message is not user friendly at all.
grid_network.net1: Creating...
grid_network.net1: Still creating... [10s elapsed]
╷
│ Error: Plugin did not respond
│
│   with grid_network.net1,
│   on main.tf line 12, in resource "grid_network" "net1":
│   12: resource "grid_network" "net1" {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ApplyResourceChange call. The
│ plugin logs may contain more details.
╵

Stack trace from the terraform-provider-grid_v0.1.27 plugin:

panic: runtime error: index out of range [24] with length 16

goroutine 97 [running]:
github.com/threefoldtech/substrate-client.(*Substrate).checkForError(0xc00000d2f0, 0xc0002cbc80, 0x2c, {0xff, 0x3a, 0xd0, 0x77, 0xc1, 0xd9, 0x64, ...}, ...)
        github.com/threefoldtech/substrate-client@v0.0.0-20220328075445-99d0ff259160/utils.go:237 +0x3dd
github.com/threefoldtech/substrate-client.(*Substrate).CreateNodeContract(0xc0005082d0, {0xf885d0, 0xc000122700}, 0x0, {0x0, 0x0, 0x0}, {0xc0005be320, 0x20}, 0x0)
        github.com/threefoldtech/substrate-client@v0.0.0-20220328075445-99d0ff259160/contract.go:184 +0x2c7
github.com/threefoldtech/terraform-provider-grid/internal/provider.deployConsistentDeployments({0xf7c3e8, 0xc00049ff20}, 0xc000468460, 0xf82200, 0xc0002e61a0, {0xf66ca0, 0xc0005084f8}, 0xc000296180)
        github.com/threefoldtech/terraform-provider-grid/internal/provider/common.go:402 +0x7eb
github.com/threefoldtech/terraform-provider-grid/internal/provider.deployDeployments({0xf7c3e8, 0xc00049ff20}, 0x0, 0x0, 0xf66ca0, {0xf66ca0, 0xc0005084f8}, 0xc000296180, 0x1)
        github.com/threefoldtech/terraform-provider-grid/internal/provider/common.go:334 +0x10b
github.com/threefoldtech/terraform-provider-grid/internal/provider.(*NetworkDeployer).Deploy(0xc0002d34b8, {0xf7c3e8, 0xc00049ff20}, 0xd)
        github.com/threefoldtech/terraform-provider-grid/internal/provider/resource_network.go:638 +0xb9
github.com/threefoldtech/terraform-provider-grid/internal/provider.resourceNetworkCreate({0xf7c3e8, 0xc00049ff20}, 0xc00022f6c0, {0xcbd040, 0xc000296180})
        github.com/threefoldtech/terraform-provider-grid/internal/provider/resource_network.go:681 +0x4f0
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).create(0xc0002130a0, {0xf7c378, 0xc000123a80}, 0x2, {0xcbd040, 0xc000296180})
        github.com/hashicorp/terraform-plugin-sdk/v2@v2.10.1/helper/schema/resource.go:341 +0x12e
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).Apply(0xc0002130a0, {0xf7c378, 0xc000123a80}, 0xc0004a9ba0, 0xc0001d7180, {0xcbd040, 0xc000296180})
        github.com/hashicorp/terraform-plugin-sdk/v2@v2.10.1/helper/schema/resource.go:467 +0x871
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).ApplyResourceChange(0xc00000d308, {0xf7c378, 0xc000123a80}, 0xc0002c1a40)
        github.com/hashicorp/terraform-plugin-sdk/v2@v2.10.1/helper/schema/grpc_provider.go:977 +0xd8a
github.com/hashicorp/terraform-plugin-go/tfprotov5/tf5server.(*server).ApplyResourceChange(0xc0001aae00, {0xf7c420, 0xc0005e7a10}, 0xc0004bb9d0)
        github.com/hashicorp/terraform-plugin-go@v0.5.0/tfprotov5/tf5server/server.go:603 +0x30e
github.com/hashicorp/terraform-plugin-go/tfprotov5/internal/tfplugin5._Provider_ApplyResourceChange_Handler({0xe023a0, 0xc0001aae00}, {0xf7c420, 0xc0005e7a10}, 0xc00049f440, 0x0)
        github.com/hashicorp/terraform-plugin-go@v0.5.0/tfprotov5/internal/tfplugin5/tfplugin5_grpc.pb.go:380 +0x170
google.golang.org/grpc.(*Server).processUnaryRPC(0xc0001fea80, {0xf8b9d0, 0xc000410000}, 0xc0000b0ea0, 0xc0003e2f60, 0x15c9ac0, 0x0)
        google.golang.org/grpc@v1.41.0/server.go:1279 +0xccf
google.golang.org/grpc.(*Server).handleStream(0xc0001fea80, {0xf8b9d0, 0xc000410000}, 0xc0000b0ea0, 0x0)
        google.golang.org/grpc@v1.41.0/server.go:1608 +0xa2a
google.golang.org/grpc.(*Server).serveStreams.func1.2()
        google.golang.org/grpc@v1.41.0/server.go:923 +0x98
created by google.golang.org/grpc.(*Server).serveStreams.func1
        google.golang.org/grpc@v1.41.0/server.go:921 +0x294

Error: The terraform-provider-grid_v0.1.27 plugin crashed!

This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.

same issue with tsclient
Rolling back deployments
/home/mohamed/Desktop/Github/tsclient2/grid3_client_ts/src/high_level/twinDeploymentHandler.ts:388
            throw Error(e);
                  ^
Error: Error: Failed to create contract on node: 22 due to Failed to apply createNodeContract in module smartContractModule with 22,,720f7455c4c6aba21d415e8badea0f7e,0 due to error: undefined
    at TwinDeploymentHandler.handle (/home/mohamed/Desktop/Github/tsclient2/grid3_client_ts/src/high_level/twinDeploymentHandler.ts:388:19)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async MachinesModule.deploy (/home/mohamed/Desktop/Github/tsclient2/grid3_client_ts/src/modules/machines.ts:76:27)
    at async MachinesModule.descriptor.value (/home/mohamed/Desktop/Github/tsclient2/grid3_client_ts/src/modules/utils.ts:14:16)
    at async MachinesModule.descriptor.value (/home/mohamed/Desktop/Github/tsclient2/grid3_client_ts/src/helpers/validator.ts:23:16)
    at async main (/home/mohamed/Desktop/Github/tsclient2/grid3_client_ts/scripts/single_vm.ts:45:17)


Trivial update to log line

The client keys were not printed as the map was not being traversed.
By converting to array it will be.
Also using __FUNCTION__ in place of __PRETTY_FUNCTION__ as it is more concise.

The __FUNCTION__ change is fine, but the map should definitely be consumed by the logger.

Without array:
2022-02-24 13:23:08,779 Debug [agora.node.TransactionRelayer] - agora.node.TransactionRelayer.TransactionRelayerFeeImp.relayTransactions: clients: { _input: { manager_version: 0X000000011FD23DE8, peers: 0X000000011FD23DE0, range_version: 0, range: [agora.network.Client.NetworkClient, agora.network.Client.NetworkClient, agora.network.Client.NetworkClient, agora.network.Client.NetworkClient, agora.network.Client.NetworkClient, agora.network.Client.NetworkClient] }, this: 0X000000011B874BD0 }

I'm not denying there's a bug, but I think the fix is wrong, logger should evaluate the range.

Updated the PeerRange to be ForwardRange so that it is logged as expected.


Add handling of 307 and 308 redirects

@aidanhs I took the commits from your PR, and did as I was saying in #18, removing the Seek bounds on Body. I'm not against finding a solution, but I wanted to get these valuable fixes that you made merged in sooner, and we can find the best solution later.
For anyone curious, it looks better if you add ?w=1 to the end of the diff on Github (removes the whitespace noise).
Closes #9
Closes #18

I'm fine with going back to closer to my original approach (approximately equal to this PR), but this isn't quite right for the behaviour that you're looking for. Specifically, it seems to me that the reader will be at EOF when trying to make a subsequent request as a result of a 307 or 308 redirect. This seems like really bad behaviour.
I'd propose one of two options to get my incremental fix in:

307 and 308 are returned as-is (as they are currently) if there's a body, which at least allows redirects without a body (e.g. GET) to work.
The knowledge of whether a body can be reused is exposed to send somehow, and it returns the 307/308 directly if it can't.

If you look back at #18 I've taken this PR and added a single tiny commit to implement suggestion 1.

@aidanhs Good catch! I've added the ability for send to know if the body can be reset, and return the response if it cannot. And with tests!

Might be worth adding a note to https://docs.rs/reqwest/0.1.0/reqwest/struct.RequestBuilder.html#method.body saying something like "The type of body will affect whether this request can be redirected. For example, since a Reader may not be seekable a 307 or 308 response to a PUT or POST will be returned as-is rather than trying to send the request (and body) again."

(Travis failure was nightly, there is a bug today's nightly cargo.)


Use autoversion client of docker-py if available (fixes #309)

We don't use the new AutoVersionClient class (https://github.com/docker/docker-py/blob/2dfab762241fa5f9d88dc785cf7fcf0a3e2dff8a/docker/client.py#L893), we just check whether it's there and if it is, we know that Client understands the 'auto' value of 'version'.

I'm working on the failed tests.

Done, please review.

LGTM (I would have implemented it differently though)

If we had a pytest fixture for the DockerTasker, which mocked Docker first, could we eliminate some duplicated code?

Rebased with both comments covered.

But I can't figure out why the fixture doesn't work when used in parametrized function, for example it  doesn't work in parametrized test_rpmqa_plugin(), while it's ok in test_rpmqa_plugin_exception().

Yes, I don't know what's going on there. Maybe a fixture wasn't such a good idea, sorry. :-(


Bridge requires user name and password if default port is changed (5.2.1)

I remember this being brought up in 5.2.0 RC testing.
Since several of us already had usernames and passwords added many never noticed.
and reverting to a previous build and adding a user fixed the issue.
However while attempting to debug a friends HA bridge I noticed this.
Using the default port of 80 the bridges loads fine, if you change the port when it restarts it goes to the login page.
Since no login was created you can't access the bridge.
I deleted the habridge.config file and restarted the bridge which loads the defaults. I created a login then changed the port and saved I was able to login  and access the bridge so I figured I would remove the user and that would allow access to the bridge without the log-in.  Nope! Still throws the login page up so I figured maybe the user never got deleted, but typing in the info I get user doesn't exist.

That is interesting. I saw that comment too and thought the user added  security at some point. But remembering that post, he did not add a user. Let me take a look.

I do not get the login page when changing the web server port.


FzfLua buffers shows errors, then open the buffers window with empty list.

Info

Operating System: MacOS
Shell: Zsh
Terminal: WezTerm
nvim --version: 0.91 release
fzf --version: 0.37.0 (brew)

[ ] The issue is reproducible with mini.sh

fzf-lua configuration

Using neovim with Astronvim distribution
  -- using lazy.nvim
  {
    "ibhagwan/fzf-lua",
    -- optional for icon support
    dependencies = { "nvim-tree/nvim-web-devicons" },
    config = function()
      -- calling `setup` is optional for customization
      local fzf = require("fzf-lua")
      fzf.setup()
      fzf.register_ui_select()
    end
  },

Description
Open nvim within the project folder (git), no buffer opened. Run cmd FzfLua buffers, all looking good, shows empty list.
open 2 or 3 files, run FzfLua buffers again, it shows this following errors
Error executing vim.schedule lua callback: ...liu/.local/share/nvim/lazy/fzf-lua/lua/fzf-lua/shell.lua:297: ...hare/nvim/lazy/fzf-lua/lua/fzf-lua/providers/buffers.lua:210: assertion failed!
stack traceback:
	[builtin#36]: at 0x01027b8620
	...liu/.local/share/nvim/lazy/fzf-lua/lua/fzf-lua/shell.lua:297: in function 'fn'
	...liu/.local/share/nvim/lazy/fzf-lua/lua/fzf-lua/shell.lua:71: in function <...liu/.local/share/nvim/lazy/fzf-lua/lua/fzf-lua/shell.lua:70>

This only happens in some of my projects. Don't know why/how this happens. And I don't know why it only happens in certain project folders.

If I remove this line from providers/buffers.lua:181, it will just work:
    if opts.color_icons then
      -- buficon = utils.ansi_codes[hl](buficon)
    end

If I print hl, the result is nil, seems like the buficon, hl = make_entry.get_devicon(filename, extension) function didn't return a valid hl

seems like the buficon, hl = make_entry.get_devicon(filename, extension) function didn't return a valid hl

It should return a default icon, do you have any customization for the devicons plugin?
Does it with with mini.sh within the same folder with the problematic extensions?

When I open a txt file or a java file, the hl is DevIconTxt or DevIconJava respectively, but the utils.ansi_codes does not have these keys. Here is the key dump of utils.ansi_codes:

This can easily be solved with a default color/icon fallback but I’m wondering why these don’t return the default icon on your system.
I’ll do some testing on my end.

It should return a default icon

The buficon variable is correct (which is the default icon), but the hl is nil.
If I step into the make_entry.lua:190
  if M._devicons then
    icon, hl = M._devicons.get_icon(file, ext:lower(), { default = true })
    -- here the hl is already nil
  elseif M._devicons_map then

On my system I also face a lot of errors like this, I feel they are related. I'm using the latest version of nvim-web-devicons plugin:
Unable to stat file Error loading remote config section '_devicons_geticons()'

https://github.com/ibhagwan/fzf-lua/commit/8b855fedfd50ef0e9e0484e2ee59e8dbac326c24
The above commit should get rid of the error.
Let's also try to understand what happened to your devicons setup, can you run the same commands and paste the output?
:lua vim.print(require("nvim-web-devicons").get_icon("build", "build", { default =true }))

DevIconBazelBuild
:lua vim.print(require("nvim-web-devicons").get_icon("1.java", "java", { default=true }))

DevIconJava

:lua vim.print(vim.api.nvim_get_hl(0, { name = "DevIconBazelBuild", link = true }))
{
  ctermfg = 113,
  fg = 9035857
}
:lua vim.print(vim.api.nvim_get_hl(0, { name = "DevIconJava", link = true }))
{
  ctermfg = 167,
  fg = 13385284
}

:lua vim.print(require("fzf-lua").utils.ansi_from_hl("DevIconBazelBuild", ""))
^[[38;2;137;224;81m^[[0m
^[[38;2;137;224;81m
:lua vim.print(require("fzf-lua").utils.ansi_from_hl("DevIconJava", ""))
^[[38;2;204;62;68m^[[0m
^[[38;2;204;62;68m

Unable to stat file Error loading remote config section '_devicons_geticons()'

This is also related, fzf-lua runs the heavier operations in a separate process and then queries the main instance (over named pipe) for the icon configuration, it seems this is failing.
(1) Can you try the running the min.sh and see if you get the same errors or the icons work as expected (i.e. with colors)?
sh -c "$(curl -s https://raw.githubusercontent.com/ibhagwan/fzf-lua/main/scripts/mini.sh)"

(2) Can you post the full output of:
:lua vim.print(require("nvim-web-devicons").get_icons())

For your last comment:
running mini.sh working all good. Icon and color looks correct.
Is this has something to do with lazy.nvim lazy loading mechanism?
Here is the dump of the second command when I use Astronvim:
{ <1>{
    icon = "󰈙"
  },
  [".babelrc"] = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "Babelrc"
  },
  [".bash_profile"] = {
    color = "#447028",
    cterm_color = "22",
    icon = "",
    name = "BashProfile"
  },
  [".bashrc"] = {
    color = "#447028",
    cterm_color = "22",
    icon = "",
    name = "Bashrc"
  },
  [".dockerignore"] = {
    color = "#2e5f99",
    cterm_color = "25",
    icon = "󰡨",
    name = "Dockerfile"
  },
  [".ds_store"] = {
    color = "#41535b",
    cterm_color = "239",
    icon = "",
    name = "DsStore"
  },
  [".env"] = {
    color = "#32310d",
    cterm_color = "236",
    icon = "",
    name = "Env"
  },
  [".eslintrc"] = {
    color = "#4b32c3",
    cterm_color = "56",
    icon = "",
    name = "Eslintrc"
  },
  [".gitattributes"] = {
    color = "#41535b",
    cterm_color = "239",
    icon = "",
    name = "GitAttributes"
  },
  [".gitconfig"] = {
    color = "#41535b",
    cterm_color = "239",
    icon = "",
    name = "GitConfig"
  },
  [".gitignore"] = {
    color = "#41535b",
    cterm_color = "239",
    icon = "",
    name = "GitIgnore"
  },
  [".gitlab-ci.yml"] = {
    color = "#aa321f",
    cterm_color = "124",
    icon = "",
    name = "GitlabCI"
  },
  [".gitmodules"] = {
    color = "#41535b",
    cterm_color = "239",
    icon = "",
    name = "GitModules"
  },
  [".gvimrc"] = {
    color = "#017226",
    cterm_color = "22",
    icon = "",
    name = "Gvimrc"
  },
  [".npmignore"] = {
    color = "#ae1d38",
    cterm_color = "161",
    icon = "",
    name = "NPMIgnore"
  },
  [".npmrc"] = {
    color = "#ae1d38",
    cterm_color = "161",
    icon = "",
    name = "NPMrc"
  },
  [".settings.json"] = {
    color = "#643995",
    cterm_color = "91",
    icon = "",
    name = "SettingsJson"
  },
  [".vimrc"] = {
    color = "#017226",
    cterm_color = "22",
    icon = "",
    name = "Vimrc"
  },
  [".zprofile"] = {
    color = "#447028",
    cterm_color = "22",
    icon = "",
    name = "Zshprofile"
  },
  [".zshenv"] = {
    color = "#447028",
    cterm_color = "22",
    icon = "",
    name = "Zshenv"
  },
  [".zshrc"] = {
    color = "#447028",
    cterm_color = "22",
    icon = "",
    name = "Zshrc"
  },
  _gvimrc = {
    color = "#017226",
    cterm_color = "22",
    icon = "",
    name = "Gvimrc"
  },
  _vimrc = {
    color = "#017226",
    cterm_color = "22",
    icon = "",
    name = "Vimrc"
  },
  ai = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "Ai"
  },
  awk = {
    color = "#3a4446",
    cterm_color = "238",
    icon = "",
    name = "Awk"
  },
  bash = {
    color = "#447028",
    cterm_color = "22",
    icon = "",
    name = "Bash"
  },
  bat = {
    color = "#40500f",
    cterm_color = "58",
    icon = "",
    name = "Bat"
  },
  bazel = {
    color = "#447028",
    cterm_color = "22",
    icon = "",
    name = "Bazel"
  },
  bmp = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Bmp"
  },
  brewfile = {
    color = "#701516",
    cterm_color = "52",
    icon = "",
    name = "Brewfile"
  },
  build = {
    color = "#447028",
    cterm_color = "22",
    icon = "",
    name = "BazelBuild"
  },
  bzl = {
    color = "#447028",
    cterm_color = "22",
    icon = "",
    name = "Bzl"
  },
  c = {
    color = "#3b69aa",
    cterm_color = "25",
    icon = "",
    name = "C"
  },
  ["c++"] = {
    color = "#a23253",
    cterm_color = "125",
    icon = "",
    name = "CPlusPlus"
  },
  cbl = {
    color = "#005ca5",
    cterm_color = "25",
    icon = "⚙",
    name = "Cobol"
  },
  cc = {
    color = "#a23253",
    cterm_color = "125",
    icon = "",
    name = "CPlusPlus"
  },
  cfg = {
    color = "#2f2f2f",
    cterm_color = "236",
    icon = "",
    name = "Configuration"
  },
  cjs = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "Cjs"
  },
  clj = {
    color = "#466024",
    cterm_color = "22",
    icon = "",
    name = "Clojure"
  },
  cljc = {
    color = "#466024",
    cterm_color = "22",
    icon = "",
    name = "ClojureC"
  },
  cljd = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "ClojureDart"
  },
  cljs = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "ClojureJS"
  },
  cmake = {
    color = "#526064",
    cterm_color = "59",
    icon = "",
    name = "CMake"
  },
  ["cmakelists.txt"] = {
    color = "#526064",
    cterm_color = "59",
    icon = "",
    name = "CMakeLists"
  },
  cob = {
    color = "#005ca5",
    cterm_color = "25",
    icon = "⚙",
    name = "Cobol"
  },
  cobol = {
    color = "#005ca5",
    cterm_color = "25",
    icon = "⚙",
    name = "Cobol"
  },
  coffee = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "Coffee"
  },
  commit_editmsg = {
    color = "#41535b",
    cterm_color = "239",
    icon = "",
    name = "GitCommit"
  },
  conf = {
    color = "#526064",
    cterm_color = "59",
    icon = "",
    name = "Conf"
  },
  ["config.ru"] = {
    color = "#701516",
    cterm_color = "52",
    icon = "",
    name = "ConfigRu"
  },
  containerfile = {
    color = "#2e5f99",
    cterm_color = "25",
    icon = "󰡨",
    name = "Dockerfile"
  },
  copying = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "License"
  },
  ["copying.lesser"] = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "License"
  },
  cp = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Cp"
  },
  cpp = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Cpp"
  },
  cpy = {
    color = "#005ca5",
    cterm_color = "25",
    icon = "⚙",
    name = "Cobol"
  },
  cr = {
    color = "#434343",
    cterm_color = "238",
    icon = "",
    name = "Crystal"
  },
  cs = {
    color = "#434d04",
    cterm_color = "58",
    icon = "󰌛",
    name = "Cs"
  },
  csh = {
    color = "#3a4446",
    cterm_color = "238",
    icon = "",
    name = "Csh"
  },
  cson = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "Cson"
  },
  css = {
    color = "#2c6ea3",
    cterm_color = "24",
    icon = "",
    name = "Css"
  },
  csv = {
    color = "#447028",
    cterm_color = "22",
    icon = "󰈙",
    name = "Csv"
  },
  cxx = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Cxx"
  },
  d = {
    color = "#325a13",
    cterm_color = "22",
    icon = "",
    name = "D"
  },
  dart = {
    color = "#03589C",
    cterm_color = "25",
    icon = "",
    name = "Dart"
  },
  db = {
    color = "#494848",
    cterm_color = "238",
    icon = "",
    name = "Db"
  },
  deb = {
    icon = "",
    name = "Deb"
  },
  default_icon = <table 1>,
  desktop = {
    color = "#563d7c",
    cterm_color = "54",
    icon = "",
    name = "DesktopEntry"
  },
  diff = {
    color = "#41535b",
    cterm_color = "239",
    icon = "",
    name = "Diff"
  },
  doc = {
    color = "#185abd",
    cterm_color = "26",
    icon = "󰈬",
    name = "Doc"
  },
  ["docker-compose.yaml"] = {
    color = "#2e5f99",
    cterm_color = "25",
    icon = "󰡨",
    name = "Dockerfile"
  },
  ["docker-compose.yml"] = {
    color = "#2e5f99",
    cterm_color = "25",
    icon = "󰡨",
    name = "Dockerfile"
  },
  dockerfile = {
    color = "#2e5f99",
    cterm_color = "25",
    icon = "󰡨",
    name = "Dockerfile"
  },
  docx = {
    color = "#185abd",
    cterm_color = "26",
    icon = "󰈬",
    name = "Docx"
  },
  drl = {
    color = "#553a3a",
    cterm_color = "238",
    icon = "",
    name = "Drools"
  },
  dropbox = {
    color = "#0049be",
    cterm_color = "26",
    icon = "",
    name = "Dropbox"
  },
  dump = {
    color = "#494848",
    cterm_color = "238",
    icon = "",
    name = "Dump"
  },
  edn = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Edn"
  },
  eex = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Eex"
  },
  ejs = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "Ejs"
  },
  elm = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Elm"
  },
  epp = {
    color = "#80530d",
    icon = "",
    name = "Epp"
  },
  erb = {
    color = "#701516",
    cterm_color = "94",
    icon = "",
    name = "Erb"
  },
  erl = {
    color = "#8a2b72",
    cterm_color = "89",
    icon = "",
    name = "Erl"
  },
  ex = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Ex"
  },
  exs = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Exs"
  },
  ["f#"] = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Fsharp"
  },
  f90 = {
    color = "#563b70",
    cterm_color = "53",
    icon = "󱈚",
    name = "Fortran"
  },
  ["favicon.ico"] = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "Favicon"
  },
  fish = {
    color = "#3a4446",
    cterm_color = "238",
    icon = "",
    name = "Fish"
  },
  fnl = {
    color = "#33312b",
    cterm_color = "236",
    icon = "🌜",
    name = "Fennel"
  },
  fs = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Fs"
  },
  fsi = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Fsi"
  },
  fsscript = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Fsscript"
  },
  fsx = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Fsx"
  },
  gd = {
    color = "#526064",
    cterm_color = "59",
    icon = "",
    name = "GDScript"
  },
  ["gemfile$"] = {
    color = "#701516",
    cterm_color = "52",
    icon = "",
    name = "Gemfile"
  },
  gemspec = {
    color = "#701516",
    cterm_color = "52",
    icon = "",
    name = "Gemspec"
  },
  gif = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Gif"
  },
  git = {
    color = "#b5391e",
    cterm_color = "160",
    icon = "",
    name = "GitLogo"
  },
  glb = {
    color = "#80581e",
    cterm_color = "94",
    icon = "",
    name = "BinaryGLTF"
  },
  gnumakefile = {
    color = "#526064",
    cterm_color = "59",
    icon = "",
    name = "Makefile"
  },
  go = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Go"
  },
  godot = {
    color = "#526064",
    cterm_color = "59",
    icon = "",
    name = "GodotProject"
  },
  gql = {
    color = "#ac2880",
    cterm_color = "126",
    icon = "",
    name = "GraphQL"
  },
  graphql = {
    color = "#ac2880",
    cterm_color = "126",
    icon = "",
    name = "GraphQL"
  },
  gruntfile = {
    color = "#975122",
    cterm_color = "130",
    icon = "",
    name = "Gruntfile"
  },
  gulpfile = {
    color = "#992e33",
    cterm_color = "88",
    icon = "",
    name = "Gulpfile"
  },
  h = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "H"
  },
  haml = {
    color = "#2f2f2d",
    cterm_color = "236",
    icon = "",
    name = "Haml"
  },
  hbs = {
    color = "#a04f1d",
    cterm_color = "130",
    icon = "",
    name = "Hbs"
  },
  heex = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Heex"
  },
  hh = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Hh"
  },
  hpp = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Hpp"
  },
  hrl = {
    color = "#8a2b72",
    cterm_color = "89",
    icon = "",
    name = "Hrl"
  },
  hs = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Hs"
  },
  htm = {
    color = "#aa391c",
    cterm_color = "124",
    icon = "",
    name = "Htm"
  },
  html = {
    color = "#ab3a1c",
    cterm_color = "124",
    icon = "",
    name = "Html"
  },
  hxx = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Hxx"
  },
  ico = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "Ico"
  },
  import = {
    color = "#2f2f2f",
    cterm_color = "236",
    icon = "",
    name = "ImportConfiguration"
  },
  ini = {
    color = "#526064",
    cterm_color = "59",
    icon = "",
    name = "Ini"
  },
  java = {
    color = "#992e33",
    cterm_color = "88",
    icon = "",
    name = "Java"
  },
  jl = {
    color = "#6c4b7c",
    cterm_color = "96",
    icon = "",
    name = "Jl"
  },
  jpeg = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Jpeg"
  },
  jpg = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Jpg"
  },
  js = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "Js"
  },
  json = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "Json"
  },
  json5 = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "Json5"
  },
  jsx = {
    color = "#158197",
    cterm_color = "31",
    icon = "",
    name = "Jsx"
  },
  ksh = {
    color = "#3a4446",
    cterm_color = "238",
    icon = "",
    name = "Ksh"
  },
  kt = {
    color = "#5f3ebf",
    cterm_color = "92",
    icon = "",
    name = "Kotlin"
  },
  kts = {
    color = "#5f3ebf",
    cterm_color = "92",
    icon = "",
    name = "KotlinScript"
  },
  leex = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Leex"
  },
  less = {
    color = "#563d7c",
    cterm_color = "54",
    icon = "",
    name = "Less"
  },
  lhs = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Lhs"
  },
  license = {
    color = "#686020",
    cterm_color = "58",
    icon = "",
    name = "License"
  },
  liquid = {
    color = "#4a6024",
    cterm_color = "58",
    icon = "",
    name = "Liquid"
  },
  lock = {
    icon = "󰌾",
    name = "Lock"
  },
  log = {
    color = "#333333",
    cterm_color = "236",
    icon = "󰌱",
    name = "Log"
  },
  lua = {
    color = "#366b8a",
    cterm_color = "24",
    icon = "",
    name = "Lua"
  },
  luau = {
    color = "#366b8a",
    cterm_color = "24",
    icon = "",
    name = "Luau"
  },
  makefile = {
    color = "#526064",
    cterm_color = "59",
    icon = "",
    name = "Makefile"
  },
  markdown = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Markdown"
  },
  material = {
    color = "#8a2b72",
    cterm_color = "89",
    icon = "󰔉",
    name = "Material"
  },
  md = {
    color = "#333333",
    cterm_color = "236",
    icon = "",
    name = "Md"
  },
  mdx = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Mdx"
  },
  mint = {
    color = "#44604a",
    cterm_color = "23",
    icon = "󰌪",
    name = "Mint"
  },
  ["mix.lock"] = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "MixLock"
  },
  mjs = {
    color = "#504b1e",
    cterm_color = "58",
    icon = "",
    name = "Mjs"
  },
  mk = {
    color = "#526064",
    cterm_color = "59",
    icon = "",
    name = "Makefile"
  },
  ml = {
    color = "#975122",
    cterm_color = "130",
    icon = "λ",
    name = "Ml"
  },
  mli = {
    color = "#975122",
    cterm_color = "130",
    icon = "λ",
    name = "Mli"
  },
  mo = {
    color = "#654ca7",
    cterm_color = "61",
    icon = "∞",
    name = "Motoko"
  },
  mp3 = {
    icon = "󰎆",
    name = "Mp3"
  },
  mp4 = {
    icon = "",
    name = "Mp4"
  },
  mustache = {
    color = "#975122",
    cterm_color = "130",
    icon = "",
    name = "Mustache"
  },
  nim = {
    color = "#514700",
    cterm_color = "58",
    icon = "",
    name = "Nim"
  },
  nix = {
    color = "#3f5d72",
    cterm_color = "24",
    icon = "",
    name = "Nix"
  },
  node_modules = {
    color = "#ae1d38",
    cterm_color = "161",
    icon = "",
    name = "NodeModules"
  },
  opus = {
    color = "#a55c01",
    cterm_color = "130",
    icon = "󰈣",
    name = "OPUS"
  },
  org = {
    color = "#4f7166",
    cterm_color = "66",
    icon = "",
    name = "OrgMode"
  },
  otf = {
    color = "#2f2f2f",
    cterm_color = "236",
    icon = "",
    name = "OpenTypeFont"
  },
  out = {
    icon = "",
    name = "Out"
  },
  ["package-lock.json"] = {
    color = "#7a0d21",
    icon = "",
    name = "PackageLockJson"
  },
  ["package.json"] = {
    color = "#ae1d38",
    icon = "",
    name = "PackageJson"
  },
  pck = {
    color = "#526064",
    cterm_color = "59",
    icon = "",
    name = "PackedResource"
  },
  pdf = {
    color = "#b30b00",
    cterm_color = "124",
    icon = "",
    name = "Pdf"
  },
  php = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Php"
  },
  pl = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Pl"
  },
  pm = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Pm"
  },
  png = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Png"
  },
  pp = {
    color = "#80530d",
    icon = "",
    name = "Pp"
  },
  ppt = {
    color = "#983826",
    cterm_color = "94",
    icon = "󰈧",
    name = "Ppt"
  },
  prisma = {
    color = "#333333",
    cterm_color = "236",
    icon = "󰔶",
    name = "Prisma"
  },
  pro = {
    color = "#725c2a",
    cterm_color = "94",
    icon = "",
    name = "Prolog"
  },
  procfile = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Procfile"
  },
  ps1 = {
    color = "#325698",
    cterm_color = "25",
    icon = "󰨊",
    name = "PsScriptfile"
  },
  psb = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Psb"
  },
  psd = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Psd"
  },
  psd1 = {
    color = "#4f5893",
    cterm_color = "60",
    icon = "󰨊",
    name = "PsManifestfile"
  },
  psm1 = {
    color = "#4f5893",
    cterm_color = "60",
    icon = "󰨊",
    name = "PsScriptModulefile"
  },
  py = {
    color = "#805e02",
    cterm_color = "94",
    icon = "",
    name = "Py"
  },
  pyc = {
    color = "#332d1d",
    cterm_color = "236",
    icon = "",
    name = "Pyc"
  },
  pyd = {
    color = "#332d1d",
    cterm_color = "236",
    icon = "",
    name = "Pyd"
  },
  pyo = {
    color = "#332d1d",
    cterm_color = "236",
    icon = "",
    name = "Pyo"
  },
  query = {
    color = "#607035",
    cterm_color = "58",
    icon = "",
    name = "Query"
  },
  r = {
    color = "#286844",
    cterm_color = "29",
    icon = "󰟔",
    name = "R"
  },
  rake = {
    color = "#701516",
    cterm_color = "52",
    icon = "",
    name = "Rake"
  },
  rakefile = {
    color = "#701516",
    cterm_color = "52",
    icon = "",
    name = "Rakefile"
  },
  rb = {
    color = "#701516",
    cterm_color = "52",
    icon = "",
    name = "Rb"
  },
  res = {
    color = "#992e33",
    cterm_color = "88",
    icon = "",
    name = "ReScript"
  },
  resi = {
    color = "#a33759",
    cterm_color = "125",
    icon = "",
    name = "ReScriptInterface"
  },
  rlib = {
    color = "#6f5242",
    cterm_color = "95",
    icon = "",
    name = "Rlib"
  },
  rmd = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Rmd"
  },
  ["robots.txt"] = {
    icon = "󰚩",
    name = "Robots"
  },
  rpm = {
    icon = "",
    name = "Rpm"
  },
  rproj = {
    color = "#286844",
    cterm_color = "29",
    icon = "󰗆",
    name = "Rproj"
  },
  rs = {
    color = "#6f5242",
    cterm_color = "95",
    icon = "",
    name = "Rs"
  },
  rss = {
    color = "#7e4e1e",
    cterm_color = "94",
    icon = "",
    name = "Rss"
  },
  sass = {
    color = "#a33759",
    cterm_color = "125",
    icon = "",
    name = "Sass"
  },
  sbt = {
    color = "#992e33",
    cterm_color = "88",
    icon = "",
    name = "sbt"
  },
  scala = {
    color = "#992e33",
    cterm_color = "88",
    icon = "",
    name = "Scala"
  },
  scm = {
    color = "#000000",
    cterm_color = "16",
    icon = "󰘧",
    name = "Scheme"
  },
  scss = {
    color = "#a33759",
    cterm_color = "125",
    icon = "",
    name = "Scss"
  },
  sh = {
    color = "#3a4446",
    cterm_color = "238",
    icon = "",
    name = "Sh"
  },
  sig = {
    color = "#975122",
    cterm_color = "130",
    icon = "λ",
    name = "Sig"
  },
  slim = {
    color = "#aa391c",
    cterm_color = "124",
    icon = "",
    name = "Slim"
  },
  sln = {
    color = "#643995",
    cterm_color = "91",
    icon = "",
    name = "Sln"
  },
  sml = {
    color = "#975122",
    cterm_color = "130",
    icon = "λ",
    name = "Sml"
  },
  sol = {
    color = "#36677c",
    cterm_color = "24",
    icon = "󰞻",
    name = "Solidity"
  },
  ["spec.js"] = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "SpecJs"
  },
  ["spec.jsx"] = {
    color = "#158197",
    cterm_color = "31",
    icon = "",
    name = "JavaScriptReactSpec"
  },
  ["spec.ts"] = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "SpecTs"
  },
  ["spec.tsx"] = {
    color = "#1354bf",
    cterm_color = "26",
    icon = "",
    name = "TypeScriptReactSpec"
  },
  sql = {
    color = "#494848",
    cterm_color = "238",
    icon = "",
    name = "Sql"
  },
  sqlite = {
    color = "#494848",
    cterm_color = "238",
    icon = "",
    name = "Sql"
  },
  sqlite3 = {
    color = "#494848",
    cterm_color = "238",
    icon = "",
    name = "Sql"
  },
  styl = {
    color = "#466024",
    cterm_color = "22",
    icon = "",
    name = "Styl"
  },
  sublime = {
    color = "#975122",
    cterm_color = "130",
    icon = "",
    name = "Suo"
  },
  suo = {
    color = "#643995",
    cterm_color = "91",
    icon = "",
    name = "Suo"
  },
  sv = {
    color = "#017226",
    cterm_color = "22",
    icon = "󰍛",
    name = "SystemVerilog"
  },
  svelte = {
    color = "#bf2e00",
    cterm_color = "160",
    icon = "",
    name = "Svelte"
  },
  svg = {
    color = "#80581e",
    cterm_color = "94",
    icon = "󰜡",
    name = "Svg"
  },
  svh = {
    color = "#017226",
    cterm_color = "22",
    icon = "󰍛",
    name = "SystemVerilog"
  },
  swift = {
    color = "#975122",
    cterm_color = "130",
    icon = "",
    name = "Swift"
  },
  t = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Tor"
  },
  tbc = {
    color = "#1e5cb3",
    cterm_color = "25",
    icon = "󰛓",
    name = "Tcl"
  },
  tcl = {
    color = "#1e5cb3",
    cterm_color = "25",
    icon = "󰛓",
    name = "Tcl"
  },
  terminal = {
    color = "#217929",
    cterm_color = "28",
    icon = "",
    name = "Terminal"
  },
  ["test.js"] = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "TestJs"
  },
  ["test.jsx"] = {
    color = "#158197",
    cterm_color = "31",
    icon = "",
    name = "JavaScriptReactTest"
  },
  ["test.ts"] = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "TestTs"
  },
  ["test.tsx"] = {
    color = "#1354bf",
    cterm_color = "26",
    icon = "",
    name = "TypeScriptReactTest"
  },
  tex = {
    color = "#3D6117",
    cterm_color = "22",
    icon = "󰙩",
    name = "Tex"
  },
  tf = {
    color = "#4732af",
    cterm_color = "55",
    icon = "",
    name = "Terraform"
  },
  tfvars = {
    color = "#4732af",
    cterm_color = "55",
    icon = "",
    name = "TFVars"
  },
  toml = {
    color = "#526064",
    cterm_color = "59",
    icon = "",
    name = "Toml"
  },
  tres = {
    color = "#666620",
    cterm_color = "58",
    icon = "",
    name = "TextResource"
  },
  ts = {
    color = "#36677c",
    cterm_color = "24",
    icon = "",
    name = "Ts"
  },
  tscn = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "󰎁",
    name = "TextScene"
  },
  tsx = {
    color = "#1354bf",
    cterm_color = "26",
    icon = "",
    name = "Tsx"
  },
  ttf = {
    icon = "",
    name = "TrueTypeFont"
  },
  twig = {
    color = "#466024",
    cterm_color = "22",
    icon = "",
    name = "Twig"
  },
  txt = {
    color = "#447028",
    cterm_color = "22",
    icon = "󰈙",
    name = "Txt"
  },
  unlicense = {
    color = "#686020",
    cterm_color = "58",
    icon = "",
    name = "License"
  },
  v = {
    color = "#017226",
    cterm_color = "22",
    icon = "󰍛",
    name = "Verilog"
  },
  ["vagrantfile$"] = {
    color = "#104abf",
    cterm_color = "26",
    icon = "",
    name = "Vagrantfile"
  },
  vala = {
    color = "#562b86",
    cterm_color = "54",
    icon = "",
    name = "Vala"
  },
  vh = {
    color = "#017226",
    cterm_color = "22",
    icon = "󰍛",
    name = "Verilog"
  },
  vhd = {
    color = "#017226",
    cterm_color = "22",
    icon = "󰍛",
    name = "VHDL"
  },
  vhdl = {
    color = "#017226",
    cterm_color = "22",
    icon = "󰍛",
    name = "VHDL"
  },
  vim = {
    color = "#017226",
    cterm_color = "22",
    icon = "",
    name = "Vim"
  },
  vue = {
    color = "#466024",
    cterm_color = "22",
    icon = "",
    name = "Vue"
  },
  wasm = {
    color = "#4539a4",
    cterm_color = "55",
    icon = "",
    name = "Wasm"
  },
  webmanifest = {
    color = "#504b1e",
    cterm_color = "58",
    icon = "",
    name = "Webmanifest"
  },
  webp = {
    color = "#6b4d83",
    cterm_color = "96",
    icon = "",
    name = "Webp"
  },
  webpack = {
    color = "#36677c",
    cterm_color = "24",
    icon = "󰜫",
    name = "Webpack"
  },
  woff = {
    icon = "",
    name = "WebOpenFontFormat"
  },
  woff2 = {
    icon = "",
    name = "WebOpenFontFormat2"
  },
  workspace = {
    color = "#447028",
    cterm_color = "22",
    icon = "",
    name = "BazelWorkspace"
  },
  xcplayground = {
    color = "#975122",
    cterm_color = "130",
    icon = "",
    name = "XcPlayground"
  },
  xls = {
    color = "#207245",
    cterm_color = "29",
    icon = "󰈛",
    name = "Xls"
  },
  xlsx = {
    color = "#207245",
    cterm_color = "29",
    icon = "󰈛",
    name = "Xlsx"
  },
  xml = {
    color = "#975122",
    cterm_color = "130",
    icon = "󰗀",
    name = "Xml"
  },
  xul = {
    color = "#975122",
    cterm_color = "130",
    icon = "",
    name = "Xul"
  },
  xz = {
    icon = "",
    name = "Xz"
  },
  yaml = {
    color = "#526064",
    cterm_color = "59",
    icon = "",
    name = "Yaml"
  },
  yml = {
    color = "#526064",
    cterm_color = "59",
    icon = "",
    name = "Yml"
  },
  zig = {
    color = "#7b4d0e",
    cterm_color = "94",
    icon = "",
    name = "Zig"
  },
  zip = {
    icon = "",
    name = "Zip"
  },
  zsh = {
    color = "#447028",
    cterm_color = "22",
    icon = "",
    name = "Zsh"
  }
}

Let's also try to understand what happened to your devicons setup, can you run the same commands and paste the output?

All of these commands are correct with no errors, even in the Astronvim setup. I use light background so the color values are different from yours as expected.

https://github.com/ibhagwan/fzf-lua/commit/9babc8e2104b55f6b8913d32e59c07a4fd73378e
Can you try the above commit?
It seems that the default icon in your setup is weird, according to what you posted the default icon contains no color or name in your setup:
<1>{
    icon = "󰈙"
  },

Whereas mine returns:
:lua vim.print(require("nvim-web-devicons").get_icons()[1])
{
  color = "#6d8086",
  cterm_color = "66",
  icon = "",
  name = "Default"
}
``

Is there any way for me to try your config? Is it on github?

Appreciate your effort for helping!!
Yes, it's Astronvim so you need to first clone their repo, and then clone my user repo inside their directory. My repo's readme has the two clone commands that you need to use.

Appreciate your effort for helping!! Yes, it's Astronvim so you need to first clone their repo, and then clone my user repo inside their directory. My repo's readme has the two clone commands that you need to use.

I think I found the issue where they mangle the default icon:
https://github.com/AstroNvim/AstroNvim/blob/43d458135a534beead8f32158c1d9293adb202dc/lua/plugins/configs/nvim-web-devicons.lua#L3
Can you try the latest commit and see if everything works and you're no longer getting errors?

Running on your latest commit, the buffers window show all icon in dark_grey so I guess it's not fixed.
Also, same issue after run FzfLua grep: Unable to stat file Error loading remote config section '_devicons_geticons()'

Running on your latest commit, the buffers window show all icon in dark_grey so I guess it's not fixed. Also, same issue after run FzfLua grep: Unable to stat file Error loading remote config section '_devicons_geticons()'

Alright, I'll try your repo.

Another input, when I open buffers in my nvim project, with a bunch of lua files opened, the buffers window shows all icon in correct color. But when I open a java project, and open some files like pom.xml, README.md and build, all of their icon color was gone. I'm super confused now.

Another input, when I open buffers in my nvim project, with a bunch of lua files opened, the buffers window shows all icon in correct color. But when I open a java project, and open some files like pom.xml, README.md and build, all of their icon color was gone. However both projects having the grep issue. I'm super confused now.

That's ok I'll figure this out, the reason this happens with grep (and files) is because these run in a separate process vs buffers runs within the main instance so they have slightly different methods of acquiring the icons/colors.

https://github.com/ibhagwan/fzf-lua/commit/000845dea264b3dca268ade5a807a1b7ff94fc8d - this should solve the  Error loading remote config section '_devicons_geticons()' error.

But when I open a java project, and open some files like pom.xml, README.md and build, all of their icon color was gone

This I'm still unsure what's happening here, can you narrow down this issue?

Is it all .xml files or just after you open a java project?
Does this happen in buffers, files or grep (or all)?

I see you have a special setup for Java (nvim-jdtls, etc), perhaps something in the file is causing this error?
If this happens only after opening  .java file can you try running lua vim.print(require("nvim-web-devicons").get_icon("build", "build", { default =true })) before and after opening the java project?

The java configuration will only be load if I open a java file, but the issue I'm experiencing happens without open a java file. All I opened are these three files:

build
pom.xml
README.md

If you create a new folder with only those three files, and create a git repo by just git init, and open all three files, then open buffers, it should reproduce.

Does this happen in buffers, files or grep (or all)?

Yes, happens to all of them. And it's pretty random, sometimes one file's icon got it's color, sometimes all three files showing dark_grey. Even if you just open buffers multiple times, each time the result are different.

Yes, happens to all of them. And it's pretty random, sometimes one file's icon got its color, sometimes all three files showing dark_grey. Even if you just open buffers multiple times, each time the result could be different.

Following your exact instructions it doesn’t reproduce, given the randomness I’m thinking this could also be some weird terminal bug affecting all colors, can you post a screenshot of the buffers screen when this happens?
I want to see if other colors such as the current and alternate buffers (# and %) appear colorful or are also grayed out.

some weird terminal bug affecting all colors

Tested on both iTerm2 and WezTerm, exact same issue.
And you can see from this last screenshot, now all xml files got the color, as previously they don't. Super random. I hope this is not related to performance. Our corporate laptop was heavily protected with a lot of virus scanner etc. So most of the time if it is related to I/O it could be slow down by the scanner.

ssh to a remote Linux VM, run the same setting on the same project with 15k+ files (with a different version of nvim 0.8.0), seems the issue is gone there. Maybe it is performance related?

ssh to a remote Linux VM, run the same setting on the same project with 15k+ files (with a different version of nvim 0.8.0), seems the issue is gone there. Maybe it is performance related?

I'm still struggling with this, why would performance impact the highlights? Why only some and why randomly?

how do you update the util.ansi_code table? I would assume this table gets build only once? But from the behavior on my laptop, sometimes this table gets wiped out? So at one time util.ansi_code['WhateverJava'] is valid but a few moment later the same call failed?

Ty for the kind words @liujoey!
Would you be able to try https://github.com/ibhagwan/fzf-lua/commit/c3983ed7d9cfeeb6617a57dadfaa0cede27614b5, I have a feeling this might help the situation.

how do you update the util.ansi_code table?

As for your question, util.ansi_code is never cleared or updated that's why I'm confused about your finding and the fact this is reproduced in buffers (which doesn't use an external process).
However, with files, git_files and grep it's a different story, since an external process is used, utils.ansi_code is being rebuilt each time at the startup of the external process from the table returned by _devicons_geticons() and then built inside setup_devicons_term_hls:
https://github.com/ibhagwan/fzf-lua/blob/c3983ed7d9cfeeb6617a57dadfaa0cede27614b5/lua/fzf-lua/make_entry.lua#L95-L113
with https://github.com/ibhagwan/fzf-lua/commit/c3983ed7d9cfeeb6617a57dadfaa0cede27614b5 the returned table should be consistent as it's no longer built in runtime but cached at startup instead, this should help performance and hopefully solve this issue as well.
Another unrelated issue I noticed with your setup is that your buffer names aren't aligned properly, the issue is due to your colorscheme defining a background value for FzfLuaBufNr in:
https://github.com/liujoey/astronvim/blob/0b4170533924789fa3cbd58f69e694587c259a32/highlights/edge.lua#L33
This causes the string to be too long (due to extra ansi escape sequence for both fg and bg) to negate the effect of the string.format alignment in:
https://github.com/ibhagwan/fzf-lua/blob/c3983ed7d9cfeeb6617a57dadfaa0cede27614b5/lua/fzf-lua/providers/buffers.lua#L187-L190
Let me know if you'd like this solved, I can make the alignment width configurable via opts.

I think I found the issue. In make_entry.lua:103 you have assert(info.name)
Given the setup from Astronvim, the _devicons.get_icons() can very well return a list of 273 icons, but two of them have NO NAME
{
  icon = "󰈙"
}
{
  icon = "󰈙"
}

And most bazrrrr thing is that, the position of these two icons appears random in the table, so in your for loop, because of that assert, the loop can be interrupted randomly when ever one of this nameless icon appears.
If I change this loop to this:
  for _, info in pairs(M._devicons and M._devicons.get_icons() or M._devicons_map) do
    -- assert(info.name)
    if info.name then
      i = i + 1
      local hlgroup = "DevIcon" .. info.name
      -- some devicons customizations remove `info.color`
      -- retrieve the color from the highlight group (#801)
      local hexcol = info.color or utils.hexcol_from_hl(hlgroup, "fg")
      if hexcol and #hexcol > 0 then
        local r, g, b = hex(hexcol)
        utils.cache_ansi_escseq(hlgroup, string.format("[38;2;%s;%s;%sm", r, g, b))
      end
    end
  end

Then everything works.

Good catch @liujoey!
I guess my last update does solve it for the external process since that uses M._devicons_map, does make me wonder how come the assert doesn’t popup.
I’ll remove the asset from the code.

That's also surprised me, I'm not a lua programmer, so I originally would assume assert at least should report an error if condition not met. But in this case it silently interrupt the for loop.
Yeah, please remove that assert and wrap the code with
if info.name then
  ...
end

https://github.com/ibhagwan/fzf-lua/commit/35c9795dde0cfea7fbac6fc38ec4bfbdb98eef89
Slightly improved on that, will use the map key as fallback since it usually matches the name anyways:
https://github.com/ibhagwan/fzf-lua/blob/35c9795dde0cfea7fbac6fc38ec4bfbdb98eef89/lua/fzf-lua/make_entry.lua#L104-L105
Let me know if this solves the last remaining issue and we can finally close this :-)

That's great, work perfectly!


[Wait for #1102] [FC/props] Wrap properties with properties

[FC/props] Wrap properties with properties

**Changes proposed in this PR:**
- Add base_properties for common use
- Change fc unit to property
- Add export test
- Add `uint_prop_tag` and it's handler

**Self evaluation:**
1. Build test: [X]Passed [ ]Failed [ ]Skipped
2. Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #1103. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/1103-202104091932260.095465898513794-edbaa166f777560519d71adf97b9bd929d198fe4/.

:octocat: cibot: @zhoonit, nntrainer/utils/base_properties.h does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @zhoonit, nntrainer/utils/base_properties.h does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md


Enforce -safe-string

Sorry, yet another safe-string related PR.. :/
It's just to enforce for future developments and also I realized the bytes dependency is pretty useless because yojson is only available only for OCaml >= 4.02 (where the Bytes module exists anyway).

Great. I'm releasing this.

opam-repository PR https://github.com/ocaml/opam-repository/pull/9868


Steve/i18n

Coverage decreased (-0.6%) to 75.362% when pulling 9b2818edcbffaaccd324f8c2b9b814db7d0ba620 on steve/i18n into a931ff00825cf5e607c003d2b5f297afa274d9a6 on master.


Incorrect srt file format

Hello community,
Thanks for this great tool. I used it and it seems to work pretty well for the moment. Still I had an issue when trying to overlay the *.srt file over my video using windows media player or camtasia.
I get an error message saying the srt file is not a compatible one.

And indeed when comparing the output with a compatible file, the time stamp are not in the correct format. The 2 issues I see :

time stamp uses "." instead of ","
time stamp is missing leading zeros

0:00:00,000 --> 0:00:23,780 --> incorrect
00:00:00**.000 --> 00:00:23.**780 --> correct

Am I correct ? If yes, how should I solve this ?
note : I used the following command
auto_subtitle KT_GoM_LicenseManagement_XTEs_Features.mp4 -o base/ --task translate --srt_only TRUE --language de --model base
Thank you

Hello,
I recommend using a subtitling software to import the generated .srt file and then re-export a subtitle file to be used in media player or vlc. Aegisub is a good open source option. As you mention, you must first replace all "." with "," in the original .srt for it to import correctly into Aegisub, from there you should have no issues with the leading zeroes.
Hope this helps.


Decide whether to use OSRM or Valhalla for simple ETAs

The decisions have been made in internal communications channels. We will use OSRM and Google API to get distance matrix.
OSRM initial implementation is done, but production usage requires self-hosted osrm server.


Update carrot.md

Fixed typo in generator T seed phrase - needs to be Monero Generator T, rather than Monero generator T to produce the serialized hex value provided.

Resolved in commit 70de8cac19910bb449757434aff90edfadb83320


DIDCOMM v2 does not allow for did:key.

DIDDoc must support service endpoints.
The standard practice would be to use did:peer with numalgo 2 which is effectively a did:key with a service endpoint

Lovely thanks
https://identity.foundation/peer-did-method-spec/

We now have Out-of-Band Invitation , DID Exchange, Trust Ping, Encrypted/Signed/Plaintext Messages with DIDComm V2 using DID Key. For this we have in-memory DID Document and Secrets resolvers


Verify file content write via MPU

Test Request
Description:
A clear and concise description of what the test is about.
Expected Behavior:
A clear and concise description of what you expected to happen.
Actual Behavior:
A clear and concise description of what actually happened.
Additional Context:
Add any other context about the problem here.

#100


simulation issue

latest version of app working as simulator either it is false or true and also rerouting is not working

Did you set the SimulateRoute to false? What was the result. Rerouting does not work on iOS?

On Oct 10, 2020, at 8:06 AM, gaurav472<EMAIL_ADDRESS>wrote:

latest version of app working as simulator either it is false or true and also rerouting is not working
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

yes but its still in simulation mode and rerouting doesn't work on any os its showing rerouting with loader and keep spinning

The following example sets the SimulationMode to false and it does not simulate. If True, it simulates. Does this not work for you?
await _directions.startNavigation(                                 wayPoints: wayPoints,                                 options: MapBoxOptions(                                     simulateRoute: false));

Yes, right
below method not working for me
await _directions.startNavigation(
origin: _origin,
destination: _destination,
mode: MapBoxNavigationMode.driving,
simulateRoute: false);

Upload a video that shows it’s not working

On Oct 12, 2020, at 5:19 AM, gaurav472<EMAIL_ADDRESS>wrote:

Yes, right
below method not working for me
await _directions.startNavigation(
origin: _origin,
destination: _destination,
mode: MapBoxNavigationMode.driving,
simulateRoute: false);
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

That method has been deprecated. Please use latest version

On Oct 12, 2020, at 5:19 AM, gaurav472<EMAIL_ADDRESS>wrote:

Yes, right
below method not working for me
await _directions.startNavigation(
origin: _origin,
destination: _destination,
mode: MapBoxNavigationMode.driving,
simulateRoute: false);
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

ok i will try after upgrading version

Not using latest code


Xeon v4 Dual

Hello
I have a problem with running dual E5-2667 v4, it displays error 79
On the zx-du99d4 v1.31 board
I see on cpu-z that you managed to run V4
I currently have BIOS MOD BIOS 2400 RAM CLOCK + MICROCODE LASTEST installed
On a single processor, everything starts correctly with a working turbo boost.

Hi, i recomend you to flash
https://github.com/jwagnervaz/DUAL-CPU-ZX-DU99D4-V1.31-BIOSMOD/tree/main/LASTEST
79 is related to GPU and maybe memory
maybe you need to check your GPU, this  have UEFI boot?
You can try to erase CMOS too.
All bios i had post here will work with any V3 or V4 E5


Casks with :latest install obsolete cached versions

Immediately after installing, the app requires the user to download the latest version.

https://github.com/caskroom/homebrew-cask/issues/13206.

Fixed.


BUG: scrollbar not visible in docs

Describe your issue.
The browser's scrollbar on the right is not visible when it is toggled by mouseover. I do not see the same behaviour for example in the NumPy docs which also use the pydata theme, so probably related to SciPy itself. To reproduce, just go to the docs page and hover over your browser's scrollbar.
Browser: Chrome
Scrollbar not toggled:

Scrollbar toggled:

Reproducing Code Example
not applicable

Error message
not applicable

SciPy/NumPy/Python version information
not applicable

Thanks @dschmitz89. This will be fixed with the new version of the theme in #16660


How to determine the branch info of a commit

if i clone code with this option:
opts := &git.CloneOptions{
		Progress:          progress,
		SingleBranch:      false,
		RecurseSubmodules: git.DefaultSubmoduleRecursionDepth,
		Depth:             1,
}

I will get multiple commits. there are first commit every branch. I don't know the commit belong to which branch.
type Commit struct {
	// Hash of the commit object.
	Hash plumbing.Hash
	// Author is the original author of the commit.
	Author Signature
	// Committer is the one performing the commit, might be different from
	// Author.
	Committer Signature
	// PGPSignature is the PGP signature of the commit.
	PGPSignature string
	// Message is the commit message, contains arbitrary text.
	Message string
	// TreeHash is the hash of the root tree of the commit.
	TreeHash plumbing.Hash
	// ParentHashes are the hashes of the parent commits of the commit.
	ParentHashes []plumbing.Hash

	s storer.EncodedObjectStorer
}

I find this interesting, too. How do you find out, which branches contain this commit?
like:
git branch --contains 5315f184b9bb23d41197daa5e2d2d9de20907a0c
or really 5315f184b9bb23d41197daa5e2d2d9de20907a0c -> branch:XXX

Sorry but this is not the right channel to ask questions please post your questions at:
https://stackoverflow.com/questions/tagged/go-git


http server: add unix network and graceful stop support

This PR adds:

ability to listen on the unix domain socket if --prefer-unix-socket flag is set. This feature allows to not occupy a port, maybe helpful in some scenarios (hostnetwork usage).
ability to stop gracefully, allowing the ongoing connections to close gracefully in case of a termination signal

Changes in the unit tests are related to a fact that the reading of the token was deduplicated - before it was done in checkParameters function and just after it, now it's done only once.

/unassign @thejasn


Unhandled error during execution of scheduler flush.

Version
3.0.11
Reproduction link
https://codepen.io/faxin/pen/NWdaRoZ
Steps to reproduce
in the given codepen( https://codepen.io/faxin/pen/NWdaRoZ ):

ctrl shift I open the browser devtool console tab.
click the 'x' in one of the tabs in the UI of sandbox.

you will see the reported errror in the console tab of browser devtools.
In my real project, the full warning and error message is as follow:
runtime-core.esm-bundler.js?9e79:38 [Vue warn]:
Unhandled error during execution of ref function

[Vue warn]: Unhandled error during execution of scheduler flush.
This is likely a Vue internals bug. Please open an issue at https://new-issue.vuejs.org/?repo=vuejs/vue-next

Index.vue?8b24:43 Uncaught (in promise) TypeError:
Cannot set property 'tab' of undefined
    at ref (Index.vue?8b24:43)
    at callWithErrorHandling (runtime-core.esm-bundler.js?9e79:154)
    at setRef (runtime-core.esm-bundler.js?9e79:3712)
    at unmount (runtime-core.esm-bundler.js?9e79:4724)
    at patchKeyedChildren (runtime-core.esm-bundler.js?9e79:4558)
    at patchChildren (runtime-core.esm-bundler.js?9e79:4425)
    at processFragment (runtime-core.esm-bundler.js?9e79:4171)
    at patch (runtime-core.esm-bundler.js?9e79:3784)
    at patchKeyedChildren (runtime-core.esm-bundler.js?9e79:4506)
    at patchChildren (runtime-core.esm-bundler.js?9e79:4449)

runtime-core.esm-bundler.js?9e79:1041 Uncaught (in promise) TypeError:
Cannot read property 'emitsOptions' of null
    at shouldUpdateComponent (runtime-core.esm-bundler.js?9e79:1041)
    at updateComponent (runtime-core.esm-bundler.js?9e79:4230)
    at processComponent (runtime-core.esm-bundler.js?9e79:4186)
    at patch (runtime-core.esm-bundler.js?9e79:3791)
    at patchKeyedChildren (runtime-core.esm-bundler.js?9e79:4506)
    at patchChildren (runtime-core.esm-bundler.js?9e79:4449)
    at patchElement (runtime-core.esm-bundler.js?9e79:4062)
    at processElement (runtime-core.esm-bundler.js?9e79:3871)
    at patch (runtime-core.esm-bundler.js?9e79:3788)
    at componentEffect (runtime-core.esm-bundler.js?9e79:4368)

What is expected?
the  :ref="tab => tabs[idx].tab = tab" works correctly.
What is actually happening?
the  tabs[idx] is undefined.

I don't know if it is really a bug, but the warning message says that it is likely a Vue internals bug, so I issued it here.

Please open the bug in Quasar first or open a bug report here without Quasar.

@posva
demo https://codepen.io/edison1105/pen/yLgzgxQ?editors=1010
steps:

open Console
click x of the last tab to remove the tab

I am not sure if this is a bug.
just a note here:
if ref is a function it will called when unset ref in unmount
  } else if (isFunction(ref)) {
    callWithErrorHandling(ref, owner, ErrorCodes.FUNCTION_REF, [value, refs])
  }

note the ref is
ref: tab => tabs[idx].tab = tab

When delete the last tab, the tabs will be changed, and then the patch is called. the error appears when the above set ref method is called in unmount, because tabs[idx] has been deleted before patch called.

thank you for your codepen demo, then this may be a bug from Quasar.

thank you for your codepen demo, then this may be a bug from Quasar.

I don't think so. see my demo without Quasar still got warning in the console.

I see it, showing the same error
vue.global.prod.js:1 TypeError: Cannot set property 'tab' of undefined
    at ref (eval at ea (vue.global.prod.js:1), <anonymous>:24:35)

so if this is not the correct way of setting a bunch of ref，what it the correct way to do it. Or how to access the children of a specific component since the $children attr is remove in vue3.

I have no idea.ping @HcySunYang

Here is the correct way of setting an array of refs: https://v3.vuejs.org/guide/composition-api-template-refs.html#usage-inside-v-for


build script update

adapt paths etc. to new name
remove dependency on and plugin (mvn plugin) since it is only used to extract version information of jar

fixed


Update Configure

Updated the Configure script to handle moloch installation device not having Internet connection

thanks for doing a PR, I needed a few more changes so I went ahead and just did it instead of having a conversation.


Evaluate other parquet module

https://github.com/apache/arrow/tree/master/go, sample can be found at https://github.com/apache/arrow/blob/master/go/parquet/cmd/parquet_reader/main.go

The "official" module does not seem to be developer friendly though I'm still trying more, I'm looking around now and https://github.com/parquet-go/parquet-go/tree/main may be another one that is worth trying.


bar width differs while bar.increment!

in ProgressBar#render_bar
(ratio * (bar_width - 2)).ceil + ((1-ratio) * (bar_width - 2)).floor is not always equal to bar_width - 2
for example, with @count = 5, @max = 17, ratio = 5.0/17.0, bar_width - 2 = 34, the result of left is 33, not 34.

@delta4d I've attempted to produce a failing test case for the count & max you gave, but it seems to work ok. What terminal width are you using? Can you modify my test to fail with the current implementation and then pass with yours?
Also, your existing code breaks an existing test, I think the bar width should always be rounded down, that way the bar isn't full [####### ] until it reaches 100% exactly.
Thanks!

Hi, thank you for reply.
My terminal width is 80. And sorry I am not familiar with rspec right now.
The following ruby code may fail.
# terminal_width 80
# bar_width 36

require'progress_bar'

MAX = 17

def width count
  bar = ProgressBar.new MAX
  bar.count = count
  bar.to_s.length
end

puts width(4) # 80
puts width(5) # 79

The failing test is bar_spec#at count=25, the expected #s length is 25/100*10=2.5, if it is rounded down, the expected output is [##________], not the original [###_______] in bar_spec.rb.

now that I test it again, I see that you're right. I wonder how I was getting different results before. I'll merge a test that I wrote and release shortly.

1.0.5 released


pull request for e2e test at 12/28/2016 18:15:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


FlutterHeadlessDartRunner should return an error on invalid launches.

Proposed API: -[FlutterHeadlessDartRunner initWithProject:(FlutterDartProject*) project completion: (LaunchResult) result];
with typedef void(^LaunchResult)(NSError*);

cc @bkonyi


Rebased geojson

Added parsing capabilities for Geojson documents (this is a rebased version of the changes proposed in PR #36 along with a few additional directly related improvements).
Additions

Handling for Geojson documents

Testing

Run the test_geojson test or test_all to test the functionality

Screenshots
Notes

Handling for GeometryCollections is not complete
Build issues were keeping everything from working if the implementation code wasn't in the header. I believe those issues have been fixed, so the implementation code will need to migrate from .hpp to .cpp

Todos

Complete the documentation

Indeed, I didn't notice those had snuck in.  I'll remove them.  I think I also want to fix a couple other things also ...

Ok @hellkite500 and @christophertubbs:  I have those cleaned up, and have actually moved code definitions to code files for the rest of the classes.  I may not have been entirely consistent about how I did this with constructors, so those may need to be modified (as part of this PR, or later).

@christophertubbs @robertbartel I wanted to give you a chance to see the comments in the review I posted.  I want to merge this as a starting point to iterate on unless you think there is anything we should address out of those comments


Finalize before first production deployment

This is pull request to make first production deployment of kbss website.
Issues to consider:

Main/Index page:

?! better picture for KBSS group (replace picture with carousel)

@blcham search unsplash ?
alternatively add to the picture some labels (such as hasChild, "is-a Child" ? :)

!? remove buttons "Open Mic" and "Teching" and just add links "Open mic sessions", "Teaching" instead ?

Research projects page:

I am kind of missing information about when it happend -- how about adding it into structured part of description?

@MichalMed if you feel there is too much stuff here, move something to separate tickets.

I have removed all the TODOs from all pages and moved it to tickets: #37, #38, #39.


SQLite: Dictionary not working

Dictionary not working (no rows inside) in case all these conditions are fullfilled:

table has at least 2 column referencing to the same (other) table
during creation of the table foreign keys have not been defined by named constraint

Example:
Let's create this table for look-up of strings:
CREATE TABLE txt (
	id INTEGER PRIMARY KEY,
	value TEXT
);
INSERT INTO txt(value) VALUES ('text1');
INSERT INTO txt(value) VALUES ('text2');
INSERT INTO txt(value) VALUES ('text3');

Not working dictionary:
CREATE TABLE foo_dict_bug (
	id INTEGER PRIMARY KEY,
	txtid1 INTEGER,
	txtid2 INTEGER
	FOREIGN KEY (txtid1) REFERENCES txt(id)
	FOREIGN KEY (txtid2) REFERENCES txt(id)
);

Same table but with working dictionary:
CREATE TABLE foo_dict_ok (
	id INTEGER PRIMARY KEY,
	txtid1 INTEGER,
	txtid2 INTEGER
	CONSTRAINT foo_dict_ok_FK_1 FOREIGN KEY (txtid1) REFERENCES txt(id),
	CONSTRAINT foo_dict_ok_FK_2 FOREIGN KEY (txtid2) REFERENCES txt(id)
);

Database: SQLite
DBeaver version: 7.0.1

@kezyr 2nd and 3d statements give me a mistake when trying to execute.
Are you sure that this statement is successfully executed?:
CREATE TABLE foo_dict_ok (
id INTEGER PRIMARY KEY,
txtid1 INTEGER,
txtid2 INTEGER
CONSTRAINT foo_dict_ok_FK_1 FOREIGN KEY (txtid1) REFERENCES txt(id),
CONSTRAINT foo_dict_ok_FK_2 FOREIGN KEY (txtid2) REFERENCES txt(id)
);

@kseniiaguzeeva thank you yes there is a small mistake - missing columns. Here is the correct tested 2nd code:
CREATE TABLE foo_dict_bug (
	id INTEGER PRIMARY KEY,
	txtid1 INTEGER,
	txtid2 INTEGER,
	FOREIGN KEY (txtid1) REFERENCES txt(id),
	FOREIGN KEY (txtid2) REFERENCES txt(id)
);

Here is corrected 3rd code block:
CREATE TABLE foo_dict_ok (
	id INTEGER PRIMARY KEY,
	txtid1 INTEGER,
	txtid2 INTEGER,
	CONSTRAINT foo_dict_ok_FK_1 FOREIGN KEY (txtid1) REFERENCES txt(id),
	CONSTRAINT foo_dict_ok_FK_2 FOREIGN KEY (txtid2) REFERENCES txt(id)
);

I am sorry for mistakes in code - I believed I can write it without testing. Now my codes works I double tested it... You can see the Dictionary problem.

I see both tables. Or do you mean smth other? Please see pic.

Yes, I mean problem that with one table I can see dictionary for foreign keys during insert/edit of rows and with other I can not see. See pictures:

This is the main difference between tables as seen in DBeaver:

Now I see. Thank you for the bug report.

Fixed

verified


Fix some URLs for attributes and commands

Fix URL for attributes values, info, properties, history and command history.
Attribute name and command name were missing.

Will be released shortly in 1.15

@bourtemb , thanks for the contribution

Ooops, it seems this was fixing the URLs when http://.../tango/rest/rc4/hosts/my_tango_host/10000/devices/sys/tg_test/1/attributes is requested but then the URL are wrong when http://.../tango/rest/rc4/hosts/acudebian7/10000/devices/test/universal/1/attributes/ampli
So my proposed fixed is also causing some issues in some cases it seems... Sorry about that...

No worries. This is not critical.
As an exercise you can write a test that enforces correct behavior here  :)

Another possible fix might be to revert my PR and to apply the following patch:```
diff --git a/src/main/java/org/tango/rest/rc4/JaxRsDevice.java b/src/main/java/org/tango/rest/rc4/JaxRsDevice.java
index 9347ea9..b9cd43d 100644
--- a/src/main/java/org/tango/rest/rc4/JaxRsDevice.java
+++ b/src/main/java/org/tango/rest/rc4/JaxRsDevice.java
@@ -68,7 +68,7 @@ public class JaxRsDevice {
Arrays.asList(deviceProxy.getProxy().toDeviceProxy().get_attribute_info_ex()), new Function<AttributeInfoEx, Object>() {
@Override
public Object apply(final AttributeInfoEx input) {

                   return DeviceHelper.attributeInfoExToResponse(input.name, href);

                   return DeviceHelper.attributeInfoExToResponse(input.name, href + "/" + input.name);
               }
           });

}
@@ -134,7 +134,7 @@ public class JaxRsDevice {
return Lists.transform(Arrays.asList(deviceProxy.getProxy().toDeviceProxy().command_list_query()), new Function<CommandInfo, Object>() {
@Override
public Object apply(final CommandInfo input) {

           return DeviceHelper.commandInfoToResponse(input, href);

           return DeviceHelper.commandInfoToResponse(input, href + "/" + input.cmd_name);
       }
   });

}

> As an exercise you can write a test that enforces correct behavior [here](https://github.com/tango-controls/rest-test-suite) :)

Good exercise indeed...

I have reverted this PR in #186
Could you please apply your changes/patch there? Thanks!

I have reverted this PR in #186
Could you please apply your changes/patch there? Thanks!

Done!