Is blackfish using non-blocking IO

Hey cool project! I took a quick look at the source code and I see that you are using recv to read data from the socket. As far as I know that function blocks if there is no data to be read. Did I get this right?  Are you planning to add non-blocking IO in the near feature?

Thank you :)
You're correct recv does block if there is no data.
The project currently supports non-blocking I/O using an event loop. An event loop is created using another module I have. I/O is then handled on separate queues with the handlers being passed back to the event queue/main thread.
I do intend to replace recv with something non blocking in the future. Currently, my main focus is on creating core functionality and clean API's which will be followed by under the hood tweaking to adjust things like this.
I'm also very open for contributions to help this process as well :)

I being thinking of doing something similar to this. Since you started this project I think it will make much more sense to contribute to this instead of a creating a new one. Have you consider using libuv for IO. It is what powers Nodejs. There is similar work already been done here I think that by using libuv you won't be bound by the amount of thread in the IO and the server will be able to handle more connections.

Contribution would be awesome.
I hadn't considered it before, but it makes a lot of sense to use it in my opinion. Node.js has proven its scalability, so Blackfish being powered by the same core makes perfect sense to increase it's performance.
I'll have a look at Caramel in more detail.
What proposal do you think would be better suited:
To use an existing swift wrapper around libuv i.e Caramel ?
or
Create a new one which has been built for purpose?
As I'm going to focus mainly on the public interface and core features, I'd be more than happy to let someone take ownership of the core libuv side of things. It could even work in the sense of how Express.js wraps around Node.js.

I think the best approach for this case would be to call libuv directly. I'll be more than happy to add that contribution once I finished my backlog on my own OSS projects!

I agree. I think being built to purpose is important.
I'll add libuv to the roadmap for 1.0
I've also seen a proposal in the Swift Package Manager mailing list that intends to support C projects as packages. This could prove useful for integration within Blackfish.

libuv is now added in with version 0.4.0, it requires having it installed on your system however. Read via the Wiki or README.md

Ohh nice!!!

It's only got support for networking atm but I'll extend it to the filesystem this week :)


Java extensions not working -- not getting import help, etc.

Issue Type: Bug
Open a Java Spring Boot project and introduce an import error in a Java class file.
The editor isn't detecting the error.
After a while, I get this message: "Extension host terminated unexpectedly."
I have updated vscode and rebooted to no avail.
This feature was working brilliantly until today, so now I'm sad.
VS Code version: Code 1.23.1 (d0182c3417d225529c6d5ad24b7572815d0de9ac, 2018-05-10T16:04:33.747Z)
OS version: Linux x64 4.13.0-41-generic

System Info

Item
Value

CPUs
AMD Ryzen 7 1700 Eight-Core Processor (16 x 3445)

GPU Status
2d_canvas: unavailable_softwareflash_3d: unavailable_softwareflash_stage3d: unavailable_softwareflash_stage3d_baseline: unavailable_softwaregpu_compositing: unavailable_softwaremultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_softwarevideo_decode: unavailable_softwarevideo_encode: unavailable_softwarevpx_decode: unavailable_softwarewebgl: unavailable_offwebgl2: unavailable_off

Load (avg)
1, 1, 0

Memory (System)
31.37GB (27.39GB free)

Process Argv
/usr/share/code/code .

Screen Reader
no

VM
0%

Extensions (5)

Extension
Author (truncated)
Version

java
red
0.24.0

vscode-java-debug
vsc
0.9.0

vscode-java-pack
vsc
0.3.0

vscode-java-test
vsc
0.6.1

vscode-maven
vsc
0.7.0

I think it might be an infinite loop terminated due to a memory leak.  When I open the developer tools, I see a message similar to what is shown here: https://github.com/redhat-developer/vscode-java/issues/337

Well, I had a pretty bad time for the last couple of hours.  I tried different versions of node, different versions of java, different java plugins, etc.
This problem was finally resolved when I removed the folder: $(HOME)/.config/Code
I tried doing a diff between the broken version and the new fixed version, but the folder is too massive for that to be readily accomplished.
Then I noticed something strange in the 'settings.json' file from the broken config.  A few trials seems to reveal the following line as the culprit (I don't know specifically how it got there):
   "java.jdt.ls.vmargs": "-noverify -Xmx1G -XX:+UseG1GC -XX:+UseStringDeduplication -javaagent:\"/home/brent/.vscode/extensions/GabrielBB.vscode-lombok-0.9.2/server/lombok.jar\" -Xbootclasspath/a:\"/home/brent/.vscode/extensions/GabrielBB.vscode-lombok-0.9.2/server/lombok.jar\"",
Note that you may need to 'killall code' to get rid of background instances when restarting vscode.


Fix #21857

Use current viewport info to predict the view line info after layout change.

@rebornix It's been quite a while that I worked in this code so not sure if there were any refactoring or design changes underwent.
So not sure why we need to change the cursor position explicitly now which was not needed before and was happening by triggering the scroll event. And what does this triggering of scroll event does now.
Thanks

@sandy081 Previously ViewLines got registered in viewEventDispatcher before View. So the workflow is like

Run command
Emit Scroll Request event
VIewLines receives this event, change layout
View receives this event, call back to Cursor to update the cursor position, which reads the layout info.

Right now, in change https://github.com/Microsoft/vscode/commit/45b6708cf30cad76981357544b9ab651c262ec42 , we registered View into the dispatcher first. Now the workflow becomes

Run command
Emit Scroll Request event
View receives this event, call back to Cursor to update the cursor position, which reads the old layout info and the cursor is not actually updated correctly.
ViewLines receives this event, change layout

So in this PR, I tried to update the cursor position explicitly instead of relying on event handlers in View parts as when the layout gets updated is not guaranteed, it depends on when we register all the view parts and which view part changes the layout. Make sense?

@rebornix That explains the root cause of the bug. Thanks for the explanation and @alexandrudima also mentioned the same.

This PR is obsolete


installation error

I am getting error as below;
How can I overcome this error?
./install.sh
Installed pv
Installed go
Installed python3
Installed ccze
Installed git
Installed pip
Installed pup
Dependency knockknock not found...
Dependency subfinder not found...
Installed ipcalc
Dependency asnmap not found...
Dependency naabu not found...
Dependency dnsx not found...
Installed httpx
Installed csvcut
Dependency dmut not found...
Installed dirsearch
Installed ffuf
Installed shodan
Dependency nuclei not found...
Installed nmap
Installed ansi2html
Installed xsltproc
Installed trufflehog
Dependency anew not found...
Installed interlace
Dependency subjs not found...
Dependency katana not found...
Dependency alterx not found...
Installed ./MISC/LinkFinder
Installed ./MISC/SecretFinder
Installed ./MISC/waymore
Installed ./MISC/xnLinkFinder
Installed ./MISC/fuzzing-templates
Installed ./MISC/fingerprints.json
Installed ./MISC/technologies.json
Installed /root/.gf/excludeExt.json
Installed /usr/share/dirb/wordlists/dicc.txt
[-]The following tools are not installed: knockknock subfinder asnmap naabu dnsx dmut nuclei anew subjs katana alterx
[] Installing knockknock
Installing Tool: knockknock: 0:00:00 [<=>                                                           ]
[] Installing ASNmap
Installing Tool: ASNmap: 0:00:02 [<=>                                                               ]
[] Installing mapCIDR
Installing Tool: mapCIDR: 0:00:05 [<=>                                                              ]
[] Installing Subfinder
Installing Tool: subfinder: 0:00:01 [<=>                                                            ]
[] Installing gau
Installing Tool: gau: 0:00:01 [<=>                                                                  ]
[] Installing waybackurls
Installing Tool: waybackurls: 0:00:00 [<=>                                                          ]
[] Installing TLSx
Installing Tool: TLSx: 0:00:01 [<=>                                                                 ]
[] Installing AlterX
Installing Tool: AlterX: 0:00:00 [<=>                                                               ]
[] Installing DNSx
Installing Tool: DNSx: 0:00:00 [<=>                                                                 ]
[] Installing anew
Installing Tool: anew: 0:00:00 [<=>                                                                 ]
[] Installing gf
Installing Tool: gf: 0:00:00 [<=>                                                                   ]
[] Installing qsinject
Installing Tool: qsinject: 0:00:00 [<=>                                                             ]
[] Installing qsreplace
Installing Tool: qsreplace: 0:00:00 [<=>                                                            ]
[] Installing subjack
Installing Tool: subjack: 0:00:02 [<=>                                                              ]
[] Installing webanalyze
Installing Tool: webanalyze: 0:00:00 [<=>                                                           ]
[] Installing nuclei
Installing Tool: nuclei: 0:00:02 [<=>                                                               ]
./install.sh: line 152: nuclei: command not found
[] Installing dmut
Installing Tool: dmut: 0:00:01 [<=>                                                                 ]
[] Installing nuclei
Installing Tool: nuclei: 0:00:01 [<=>                                                               ]
[] Installing naabu
Installing Tool: naabu: 0:00:01 [<=>                                                                ]
[] Installing Subjs
[*] Installing Katana
[-]Re-Run the Installation script to check what else pending..../install.sh
┌──(root㉿kali)-[/home/kali/chomtesh]
└─# ./chomte.sh
[-]The following tools are not installed: knockknock subfinder naabu dnsx dmut nuclei anew subjs katana

Try uninstalling existing go
sudo apt-get remove golang-go
sudo apt-get remove --auto-remove golang-go
Then ReRun install.sh
Please let me know if the issue persists.

Thank you for replying.
I tried but it didn't work. the same error still comes.

Try to manually install those tools
All those are GO based tools, might be environment issue.


Vimeo dowloader falls back to generic

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

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

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
No response
Provide a description that is worded well enough to be understood
This link contains all vimeo playlists. yt-dlp falls back to generic and downloads text data instead of parsing playlist
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', 'https://player.vimeo.com/video/1036872476/config?autopause=0&autoplay=1&background=0&badge=0&byline=0&bypass_privacy=1&chromecast=1&collections=0&color=FFFFFF&colors=000000%2CFFFFFF%2Cffffff&context=embed_playlist.4734835&controls=1&default_to_hd=0&external_embed=1&force_embed=1&fullscreen=1&h=a2b2114e78&like=0&logo=0&loop=0&outro_new=0&play_button_position=auto&playbar=1&portrait=0&quality_selector=1&referrer=https%3A%2F%2Fannualmeeting.hematology.org%2F&share=0&title=1&transcript=1&transparent=0&volume=1&watch_later=0&s=b7292ecf385056e57e2deb5fdbcaad4da642f1a5_1735552334', '-o', 'video.mp4']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp [65cf46cdd] (win_exe)
[debug] Python 3.10.11 (CPython AMD64 64bit) - Windows-10-10.0.17763-SP0 (OpenSSL 1.1.1t  7 Feb 2023)
[debug] exe versions: ffmpeg 2024-11-06-git-4047b887fc-full_build-www.gyan.dev (setts)
[debug] Optional libraries: Cryptodome-3.21.0, brotli-1.1.0, certifi-2024.12.14, curl_cffi-0.5.10, mutagen-1.47.0, requests-2.32.3, sqlite3-3.40.1, urllib3-2.3.0, websockets-14.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets, curl_cffi
[debug] Loaded 1837 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp)
[generic] Extracting URL: https://player.vimeo.com/video/1036872476/config?autopause=0&autoplay=1&background=0&badge=0&byline=0&bypass_privacy=1&chromecast=1&collections=0&color=FFFFFF&colors=000000%2CFFFFFF%2Cffffff&context=embed_playlist.4734835&controls=1&default_to_hd=0&external_embed=1&force_embed=1&fullscreen=1&h=a2b2114e78&like=0&logo=0&loop=0&outro_new=0&play_button_position=auto&playbar=1&portrait=0&quality_selector=1&referrer=https%3A%2F%2Fannualmeeting.hematology.org%2F&share=0&title=1&transcript=1&transparent=0&volume=1&watch_later=0&s=b7292ecf385056e57e2deb5fdbcaad4da642f1a5_1735552334
[generic] config?autopause=0&autoplay=1&background=0&badge=0&byline=0&bypass_privacy=1&chromecast=1&collections=0&color=FFFFFF&colors=000000,FFFFFF,ffffff&context=embed_playlist.4734835&controls=1&default_to_hd=0&external_embed=1&force_embed=1&fullscreen=1&h=a2b2114e78&like=0&logo=0&loop=0&outro_new=0&play_button_position=auto&playbar=1&portrait=0&quality_selector=1&referrer=https://annualmeeting.hematology: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
WARNING: [generic] URL could be a direct video link, returning it as such.
[debug] Formats sorted by: hasvid, ie_pref, lang, quality, res, fps, hdr:12(7), vcodec, channels, acodec, size, br, asr, proto, vext, aext, hasaud, source, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] config?autopause=0&autoplay=1&background=0&badge=0&byline=0&bypass_privacy=1&chromecast=1&collections=0&color=FFFFFF&colors=000000,FFFFFF,ffffff&context=embed_playlist.4734835&controls=1&default_to_hd=0&external_embed=1&force_embed=1&fullscreen=1&h=a2b2114e78&like=0&logo=0&loop=0&outro_new=0&play_button_position=auto&playbar=1&portrait=0&quality_selector=1&referrer=https://annualmeeting.hematology: Downloading 1 format(s): 0
[debug] Invoking http downloader on "https://player.vimeo.com/video/1036872476/config?autopause=0&autoplay=1&background=0&badge=0&byline=0&bypass_privacy=1&chromecast=1&collections=0&color=FFFFFF&colors=000000%2CFFFFFF%2Cffffff&context=embed_playlist.4734835&controls=1&default_to_hd=0&external_embed=1&force_embed=1&fullscreen=1&h=a2b2114e78&like=0&logo=0&loop=0&outro_new=0&play_button_position=auto&playbar=1&portrait=0&quality_selector=1&referrer=https%3A%2F%2Fannualmeeting.hematology.org%2F&share=0&title=1&transcript=1&transparent=0&volume=1&watch_later=0&s=b7292ecf385056e57e2deb5fdbcaad4da642f1a5_1735552334"
[debug] File locking is not supported. Proceeding without locking
[download] Destination: video.mp4
[download] 100% of   13.34KiB in 00:00:00 at 31.78KiB/s

the /config url is an internal vimeo api url and will not be supported. as mentioned in your other issue, vimeo events are not yet supported


Fix GitHub Release Pipeline

Task:

auditing manylinux wheels is broken
make sure the release process works fine

issue was fixed


Fanimation ceiling fans defined in SmartThings not discovered

Describe The Bug:
I have 2 Fanimation ceiling fans and 1 Samsung TV defined in SmartThings.  The plugin discovers and enables the TV, but not the ceiling fans
To Reproduce:

Define fans in SmartThings
Operate fans using SmartThings app (confirm SmartThings setup)
Install and configure SmartThings Hombridge plugin
Restart Homebridge

Expected behavior:
Fans and TV instantiated in Homebridge
Logs:
Attached
Plugin Config:
Attached
Screenshots:
None
Environment:

Plugin Version: 1.5.17
Homebridge Version: 1.6.1
Node.js Version: 18.15.0
NPM Version: ?
Operating System:  DSM 7.2-64570 Update 1

SmartThings.txt
config.txt

@dficken , Thanks for the logs.  I am looking into this now.  It would seem from what you sent, the fan should be detected.

Thanks for the update. Please let me know if I can do anything more to help Thanks again, Dave Sent from my iPhoneOn Oct 7, 2023, at 11:16 AM, iklein99 @.***> wrote:
@dficken , Thanks for the logs.  I am looking into this now.  It would seem from what you sent, the fan should be detected.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@dficken , upgrade to 1.5.19 and give it a try.  Please let me know how that works.

Fans are discovered, but light control is wrong (should be dimmable)
￼
And, controls don’t work
[10/9/2023, 4:54:16 PM] [Smartthings Plug (IK)] [{"capability":"switch","command":"on"}] failed for Lanai Dining Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:16 PM] [Smartthings Plug (IK)] Command failed for Lanai Dining Fan
[10/9/2023, 4:54:19 PM] [Smartthings Plug (IK)] [{"capability":"fanSpeed","command":"setFanSpeed","arguments":[2]}] failed for Lanai Dining Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:19 PM] [Smartthings Plug (IK)] Failed to send setLevel command for Lanai Dining Fan
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] [{"capability":"fanSpeed","command":"setFanSpeed","arguments":[3]}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] Failed to send setLevel command for Lanai Living Fan
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] [{"capability":"fanSpeed","command":"setFanSpeed","arguments":[2]}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] Failed to send setLevel command for Lanai Living Fan
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] [{"capability":"fanSpeed","command":"setFanSpeed","arguments":[2]}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] Failed to send setLevel command for Lanai Living Fan
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] [{"capability":"fanSpeed","command":"setFanSpeed","arguments":[2]}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] Failed to send setLevel command for Lanai Living Fan
[10/9/2023, 4:54:27 PM] [Smartthings Plug (IK)] [{"capability":"switch","command":"on"}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:27 PM] [Smartthings Plug (IK)] Command failed for Lanai Living Fan
[10/9/2023, 4:54:28 PM] [Smartthings Plug (IK)] [{"capability":"switch","command":"on"}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:28 PM] [Smartthings Plug (IK)] Command failed for Lanai Living Fan
[10/9/2023, 4:54:28 PM] [Smartthings Plug (IK)] [{"capability":"switch","command":"on"}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:28 PM] [Smartthings Plug (IK)] Command failed for Lanai Living Fan
[10/9/2023, 4:54:28 PM] [Smartthings Plug (IK)] [{"capability":"switch","command":"on"}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:28 PM] [Smartthings Plug (IK)] Command failed for Lanai Living Fan

On Oct 9, 2023, at 1:47 PM, iklein99 @.***> wrote:
@dficken https://github.com/dficken , upgrade to 1.5.19 and give it a try. Please let me know how that works.
—
Reply to this email directly, view it on GitHub https://github.com/iklein99/homebridge-smartthings/issues/221#issuecomment-1753414932, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4ACXSYJCAX7YLZMCVZ6STX6Q2CNAVCNFSM6AAAAAA5PHB3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJTGQYTIOJTGI.
You are receiving this because you were mentioned.

Should have included this in my previous note.  Here’s how the device appears in SmartThings:
￼

On Oct 9, 2023, at 4:58 PM, David Ficken @.***> wrote:
Fans are discovered, but light control is wrong (should be dimmable)
<AF35C246-CE98-4A4D-A734-9D735E3C1C25.png>
And, controls don’t work
[10/9/2023, 4:54:16 PM] [Smartthings Plug (IK)] [{"capability":"switch","command":"on"}] failed for Lanai Dining Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:16 PM] [Smartthings Plug (IK)] Command failed for Lanai Dining Fan
[10/9/2023, 4:54:19 PM] [Smartthings Plug (IK)] [{"capability":"fanSpeed","command":"setFanSpeed","arguments":[2]}] failed for Lanai Dining Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:19 PM] [Smartthings Plug (IK)] Failed to send setLevel command for Lanai Dining Fan
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] [{"capability":"fanSpeed","command":"setFanSpeed","arguments":[3]}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] Failed to send setLevel command for Lanai Living Fan
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] [{"capability":"fanSpeed","command":"setFanSpeed","arguments":[2]}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] Failed to send setLevel command for Lanai Living Fan
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] [{"capability":"fanSpeed","command":"setFanSpeed","arguments":[2]}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] Failed to send setLevel command for Lanai Living Fan
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] [{"capability":"fanSpeed","command":"setFanSpeed","arguments":[2]}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:25 PM] [Smartthings Plug (IK)] Failed to send setLevel command for Lanai Living Fan
[10/9/2023, 4:54:27 PM] [Smartthings Plug (IK)] [{"capability":"switch","command":"on"}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:27 PM] [Smartthings Plug (IK)] Command failed for Lanai Living Fan
[10/9/2023, 4:54:28 PM] [Smartthings Plug (IK)] [{"capability":"switch","command":"on"}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:28 PM] [Smartthings Plug (IK)] Command failed for Lanai Living Fan
[10/9/2023, 4:54:28 PM] [Smartthings Plug (IK)] [{"capability":"switch","command":"on"}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:28 PM] [Smartthings Plug (IK)] Command failed for Lanai Living Fan
[10/9/2023, 4:54:28 PM] [Smartthings Plug (IK)] [{"capability":"switch","command":"on"}] failed for Lanai Living Fan: AxiosError: Request failed with status code 422
[10/9/2023, 4:54:28 PM] [Smartthings Plug (IK)] Command failed for Lanai Living Fan

On Oct 9, 2023, at 1:47 PM, iklein99 @.***> wrote:
@dficken https://github.com/dficken , upgrade to 1.5.19 and give it a try. Please let me know how that works.
—
Reply to this email directly, view it on GitHub https://github.com/iklein99/homebridge-smartthings/issues/221#issuecomment-1753414932, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4ACXSYJCAX7YLZMCVZ6STX6Q2CNAVCNFSM6AAAAAA5PHB3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJTGQYTIOJTGI.
You are receiving this because you were mentioned.

I’m having the same issue with a 422 response code when I try to control the fan. The plugin detects the fan and shows the current state but any attempt to change state results in 422 like the post above.

Same issue as above as I see the device but does not respond via HomeKit but does through Smart things - any update on this?

I’m also getting the same error with code 422

I’m having similar issues as described above. My ceiling fan/light are seen by Homebridge and successfully added to HomeKit, and status correctly but the following errors happen:

Light is shown as only off/on instead of off/on and dimmable
Any attempt to control fan or light fails with a 422 error.

@iklein99 is there any logs or info I can provide or help with debugging this?

@jwilson2899 , follow the instructions the attached and send the logs directly to me.  I need to see how Smartthings is reporting the capabilities to the plugin.
While you have the debug logs on, also reproduce the error / behavior.
Instructions for Producing a Detailed Log.pdf

@jwilson2899 , follow the instructions the attached and send the logs directly to me. I need to see how Smartthings is reporting the capabilities to the plugin.
While you have the debug logs on, also reproduce the error / behavior.
Instructions for Producing a Detailed Log.pdf

Thanks @iklein99, I gathered the log and emailed it to you as requested. Feel free to let me know if you need anything else.

@iklein99 is there anything else I can provide besides the logs I already sent you to try and move this forward? I'd like to help get this fixed since it's the last link of my Homekit setup I need to get everything fully functional.

@jwilson2899 , I've looked at the logs and I don't see why the device doesn't like the command that is being sent, but it doesn't.  The setFanSpeed command looks right, yet a 422 status code is returned which simply means that the syntax is right, but the command cannot be executed.  It doesn't appear that I can fix this.

@jwilson2899 , I've looked at the logs and I don't see why the device doesn't like the command that is being sent, but it doesn't. The setFanSpeed command looks right, yet a 422 status code is returned which simply means that the syntax is right, but the command cannot be executed. It doesn't appear that I can fix this.

Thanks for the update. Since this apparently affects multiple people based on the other comments here, is this something we can bring up with the SmartThings API people? Smart things app itself can control the device protons definitely seems to be something between when the plugin sends the request and it gets translated to send to the device.

just adding my support here for figuring this out -- I'm having the same issue above as described.  @Iklein99 I'd be happy to get in touch with the SmartThings team and see if if they can lend any thoughts about this issue if that might help move the ball forward.

just adding my support here for figuring this out -- I'm having the same issue above as described. @iklein99 I'd be happy to get in touch with the SmartThings team and see if if they can lend any thoughts about this issue if that might help move the ball forward.

That would be awesome if you could. It seems like @iklein99 is at a dead end from his end since it looks like all of his code is working as expected.

Any luck here? I'm also seeing a AxiosError: Request failed with status code 422. My access token is configured with very generous permissions, so I'm pretty sure it's not that.

Any luck here? I'm also seeing a AxiosError: Request failed with status code 422. My access token is configured with very generous permissions, so I'm pretty sure it's not that.

I never heard anymore on it. About 2 weeks ago I got a new router and the Fanimation fan would not connect to it, nor let me change the WiFi network. That was the last straw, so I replaced it with a Hunter that has HomeKit built in, and it works great.


L06

In class we made changes to:
--vector.js - it now includes a draw method for vectors from origin to vector end
--renderer.js - it now has two arrays that store vectors for drawing, and then draws them
--main.js - we tested drawing two vectors and their sum vector


mon: do not create mgr key on jewel

The CI on Docker is reporting the following error:
STDERR:
Error EINVAL: bad entity name
This is due to the fact that this auth entity name does not exist on
Jewel so we should not create that key when running Jewel containers.
Fixes: https://github.com/ceph/ceph-ansible/issues/1514
Signed-off-by: Sébastien Han<EMAIL_ADDRESS>

We must have missed this in #1499. @guits used ceph_stable_release to skip docker tasks that don't work with jewel i.e. https://github.com/ceph/ceph-ansible/blob/master/roles/ceph-mon/tasks/docker/main.yml#L128
Maybe checking the tag is a better approach though as ceph_stable_release doesn't really pertain to containers.

I don't think https://github.com/ceph/ceph-ansible/blob/master/roles/ceph-mon/tasks/docker/main.yml#L128 is properly evaluated since ceph_release_num is only declared in ceph-common, role that is skipped during a containerized deployment.
Am I missing something?

This patch should probably remove https://github.com/ceph/ceph-ansible/blob/master/roles/ceph-mon/tasks/docker/main.yml#L128 as well...

@leseb, yeah that's why we were using ceph_stable_release instead of ceph_release_num.

@andrewschoen ceph_stable_release is also part of ceph-common, I'm not sure how this is solving the issue. Or perhaps the CI puts it as an ENV var?
Anyway, what do you think about this patch?

@leseb yeah, it works because the CI is passing it in through extra-vars https://github.com/ceph/ceph-ansible/blob/master/tox.ini#L95
The patch works here but I'm concerned what happens when the tag is 'latest', or more concerning is the downstream container which will not mention jewel at all but will be based on jewel. We need some consistent way to know what ceph release the container is based on.
Also, I think you're right that this patch should maybe change https://github.com/ceph/ceph-ansible/blob/master/roles/ceph-mon/tasks/docker/main.yml#L128 as well.

@andrewschoen right, what about this approach? It should cover both upstream and downstream. However this does not address the case where the tag is 'latest'.

@leseb maybe we don't care about latest right now? We know upstream latest will always be > jewel. I don't believe downstream will ever use the latest tag.

@andrewschoen yes I think we don't care about latest for now, just pushed a new version.

jenkins test this please

jenkins test this please

jenkins test jewel-ansible2.2-update_cluster

jenkins test jewel-ansible2.2-docker_cluster

@leseb I don't think that ceph_docker_image_tag.find('jewel') != 1 is doing what we expect here? I couldn't find docs on that method at all. Perhaps we need to use search or match?
https://docs.ansible.com/ansible/playbooks_tests.html#testing-strings

@andrewschoen the command is correct, it's just that I need a and instead of a or.

I'm still seeing this using master branches of ceph-docker and ceph-ansible.
https://paste.fedoraproject.org/paste/MwD0750xAKzAnXi7YpmmZF5M1UNdIGYhyRLivL9gydE=

@djgalloway if you're using the ceph-docker CI process we were still depending on the 'latest' tag there which this PR doesn't support.
I'm addressing this here https://github.com/ceph/ceph-docker/pull/641/commits/67cf31047aa0914795b81f366517732c3c66db19


[CHALLENGE SUBMISSION]

Please provide the following information for your submission:
What is your name? (First, Last)
Barbara Forbes
Where is your GitHub Repo ?(With your challenge solution)
https://github.com/Ba4bes/25daysofserverless/tree/master/Day4potluck
What Challenge is this for? (Challenge number between 1 and 25)
This is challenge 4
( I had also entered challenge 2 in my first pull request; https://github.com/Ba4bes/25daysofserverless/tree/master/Day2Lucy )
(Optional) Anything else we should know? e.g., language used, location, blog post?
This is PowerShell with a CosmosDB. It isn't the cleanest code, but I had no luck finding any documentation about connecting a PowerShell Function App to a cosmosDB (or any DB for that matter). So it took a lot of trial and error :-). Guess I need to blog about it myself soon😁

THANK YOU FOR YOUR #25DaysOfServerless SUBMISSION
We checked out your repository. We're thrilled to say your solution is now listed in our Hall of Fame
Thank you for your contributions!
This issue is now resolved! 🎉


Failed sampling can result in valid arm configuration

Currently, if failing to sample a goal from TSRGoal, the retuned configuration is all 0s. This can be a valid configuration for some robots, resulting in a plan to an incorrect goal. Set the configuration to something outside joint limits if sampling failed.

Does it make more sense to return an invalid constant like a NaN or Double::MAX_VAL/POS_INFINITY?

Yup, i think so. making the change and testing it out now.

Ok, I've heard some people make arguments against using those values because they can trigger exception chains if they are accidentally used in mathematical computations, which can cause massive slowdowns, but I think the benefit of having a clear test expression and invalid mathematical results are useful.

Okay, have a look. I fixed it here: 1e4d5db2a5d32ef95c42829b6e89b102f2f86e52

LGTM.


SmartNodes - Added OSMOSIS

@smartnodesvalidators this PR changes too much so might need a fresh one I'm afraid


Do not require parens for defeffect

I got curious and wanted to play around and was able to make defeffect work without requiring parens.  No worries if you want to close (or re-implement) but I think it would be nice for those who follow it to be able to stay consistent.

Fixes #1

Thank you very much for your contribution!
The code is fine, however, the formatter is not amused about the multi parameter function without parenthesis. I will have a look at it tomorrow.

I don't think the multi-parameter one is important, I was just seeing if it worked, lol.  I think just being able to follow the one common style is what's important (as bikesheddy as it is, haha).

I added another commit which allows specs to be defined without parens as well (which was just an oversight).  If you're ok with it I can squash.

Seems great, CI is fine with it, tell me once u squashed it, I will then merge it :hugs:

Done, thank you!  And thanks again for the lib :)

@smoes Oh crap, I didn't noticed I'd removed all that whitespace!  I didn't mean to.  I guess it was set to auto-merge after I squashed!?

Sorry, ignore my comments.  I shouldn't have tried to squash right after waking up from a nap 🙃 I accidentally blew away both commits which auto-closed the PR.

The whitespace thing is no problem. I have had noticed them before.
Thanks for your contribution. Our first merge request <3


Issue in executing the main.py

Description
runfile('C:/Users/XXXXXX/XXXXXXX/XXXXX/XXXXX/XXXXX', wdir='C:/Users/XXXXX/XXXXX/XXXXXR/XXXXX/XXXXX/src')
Reloaded modules: api_data_provider
The swagger_ui directory could not be found.
Please install connexion with extra install: pip install connexion[swagger-ui]
or provide the path to your local installation by passing swagger_path=
The swagger_ui directory could not be found.
Please install connexion with extra install: pip install connexion[swagger-ui]
or provide the path to your local installation by passing swagger_path=

Serving Flask app "main" (lazy loading)
Environment: production
WARNING: This is a development server. Do not use it in a production deployment.
Use a production WSGI server instead.
Debug mode: on
Restarting with stat
An exception has occurred, use %tb to see the full traceback.

SystemExit: 1
Expected behaviour
Actual behaviour
Steps to reproduce
Additional info:
Spyder console is showing the mentioned issue, installed all the modules required. Please do the needful.
Output of the commands:

python --version
pip show connexion | grep "^Version\:"

Hi @SYKAMR , could you provide your main.py and all your installed packages (the output of pip freeze)?

import json
import os
import flask
from flask import render_template, request,Flask
from flask import  request, jsonify
import ast
from getrequestDetails import *
from check_user import *
from checkVnV_response import *
from flask import after_this_request
import connexion
from flask import Flask
Create the application instance
app = connexion.App(name, specification_dir='./')
app.app = Flask(name, static_url_path='/services/eln/register/static')
Read the swagger.yml file to configure the endpoints
app.add_api('swagger.yaml')
app.app.config["JSON_SORT_KEYS"]=False
app.app.config['SEND_FILE_MAX_AGE_DEFAULT'] = 0
app.app.secret_key = 'development key'
app.app = Flask(name,static_folder='/app/static')
list_current_file = []
def get_input_vnv(sample_id):
print("This is sample_id....",sample_id)
# sample_id = "sample:a2b07aae-9c4d-4ce6-ab88-fe593b6689ec"
url = "https://devstaging.snbstg5bup.perkinelmercloud.com/api/rest/v1.0/entities/" + sample_id + "/export?format=mol"
payload = {}
headers = {
    'x-api-key': 'v1/ax6PK9N35g83mRyeBzZtE6NMbEDrqrKLMwb3LV6B4ucz1ByUyn3+1kc3fC2C8FzD4vQ==',
}

response = requests.request("GET", url, headers=headers, data=payload, verify=False)
print("response from get_input vnv....",response.text)
# os.remove("static/sample.mol")
# os.remove("static/Vnv.png")
t = time.localtime()
timestamp = time.strftime('%b-%d-%Y_%H%M', t)
image_name = ("image" + timestamp+".png")
global list_current_file
list_current_file.append(image_name)
mol_name= ("mol" + timestamp+".mol")
list_current_file.append(mol_name)
with open('static/'+mol_name, "w+") as f:
    print("image file  modified")
    f.write(response.text)
m = Chem.MolFromMolFile('static/'+ mol_name)
Draw.MolToFile(m, 'static/'+image_name)
return response.text,image_name

@app.route('/services/eln/register/debugSignalAction', methods=['POST', 'GET'])
def debug_signalDetails():
dict_rep = {}
try:
dict_rep["headers"] = dict(request.headers)
except:
dict_rep["headers"] = {}
try:
    dict_rep["url"] = request.url
except:
    dict_rep["url"] = ""
try:
    dict_rep["ip_address"] = request.remote_addr
except:
    dict_rep["ip_address"] = ""
try:
    dict_rep["request_method"] = request.method
except:
    dict_rep["request_method"] = ""

try:
    dict_rep["query_parameter"] = request.args.to_dict()
except:
    dict_rep["query_parameter"] = ""

try:
    dict_rep["path_parameter"] = request.path
except:
    dict_rep["path_parameter"] = ""

try:
    dict_rep["data"] = request.form.to_dict()
except:
    dict_rep["data"] = {}

return dict_rep

@app.route('/services/eln/register/registrationPreCheck', methods=['POST','GET'])
def signalDetails():
sample_id,user_id,origin,url = request_details(request)
print("######################",sample_id,user_id,origin,url)
print(read(user_id,origin))
# sample_id ="sample:60c7f825-2d0d-473a-957a-52db7ef62517"
# user_id =106
# origin = "https://devstaging.snbstg5bup.perkinelmercloud.com"
# print(read(user_id, origin))
global list_current_file
# right_image_name= "Vnv.png"
respnse_strct,filename=get_input_vnv(sample_id)
left_image_name = filename
list_current_file.append(left_image_name)
stereoisomer_code,stereoisomer_name,error_msg,vnv_modification,right_flnam_rep,modified_strct= vnvresponse(respnse_strct)
print("^^^^^^",type(modified_strct),"^^^^",modified_strct)
if len(vnv_modification) !=0:
    modification_msg=vnv_modification[0]
    right_image_name=right_flnam_rep
    list_current_file.append(right_image_name)
    uniquness_check, uc_status_code = uc_response(modified_strct)
elif  len(vnv_modification) == 0:
    modification_msg = "There are no errors or modifications"
    right_image_name = filename
    list_current_file.append(right_image_name)
    uniquness_check,uc_status_code = uc_response(respnse_strct)
# print("....from main...",uniquness_check)
list_structure = []
count_struct = 0
unqc_check = ""
if uc_status_code == 200:
    if uniquness_check["hitCount"] != 0:
        # response_uc_sorted = sorted(uniquness_check["matches"], key=lambda k: k['matchType'])
        # response_uc_sorted_exact=
        # response_uc_sorted_stereoIsomerCode
        response_uc_sorted= sorted(uniquness_check["matches"], key=lambda e: (e['matchType'], e['parentNumber']))
        print("response_uc_sorted...",response_uc_sorted)
        for i in response_uc_sorted:
            dict_structure = {}
            dict_structure["matchType"] = i["matchType"]
            dict_structure["parentNumber"]=i["parentNumber"]
            dict_structure["stereoIsomerCode"] = i["stereoIsomerCode"]
            dict_structure["structureComment"] = i["structureComment"]
            with open("static/sample_" + str(count_struct) + ".mol", "w+") as f:
                f.write(i["matchStructure"])
            list_current_file.append("sample_"+str(count_struct) + ".mol")
            m = Chem.MolFromMolFile("static/sample_" + str(count_struct) + ".mol")
            Draw.MolToFile(m, "static/Vnv_" + str(count_struct) + ".png")
            dict_structure["matchStructure"] = "Vnv_" + str(count_struct) + ".png"
            list_current_file.append(dict_structure["matchStructure"])
            count_struct = count_struct + 1
            list_structure.append(dict_structure)
        print("...",list_structure)
        values_of_matchtype = [a_dict["matchType"] for a_dict in list_structure]
        print("Value for match type..",values_of_matchtype)

        if values_of_matchtype.count("EXACT") == 1 and values_of_matchtype.count("STEREOISOMER") == 0:
            unqc_check = "Your structure has an exact match."
        elif values_of_matchtype.count("EXACT") == 1 and values_of_matchtype.count("STEREOISOMER") >= 1:
            unqc_check = "Your structure has an exact match but also has stereoisomer matches."
        elif values_of_matchtype.count("EXACT") >= 1:
            unqc_check = "Your structure has more than one exact match, please request a curation to address duplicates prior to registration."
        elif values_of_matchtype.count("EXACT") == 0 and values_of_matchtype.count("STEREOISOMER") == 0:
            unqc_check = "Your structure is unique."
        elif values_of_matchtype.count("EXACT") == 0 and values_of_matchtype.count("STEREOISOMER") >= 1:
            unqc_check = "Your structure is unique but also has stereoisomer matches."
        elif values_of_matchtype.count("EXACT") == 0 and values_of_matchtype.count("STEREOISOMER") >= 0:
            list_structure=[]
            dict_0={}
            dict_0['StructureId'] = "Drawn Structure"
            dict_0['MF'] = None
            dict_0['MW'] = None
            dict_0['stereoIsomerCode'] = stereoisomer_code
            dict_0['Comment'] = ""
            dict_0['matchStructure'] = right_image_name
            list_structure.append(dict_0)

    else:
        list_structure=[]
        dict_0={}
        dict_0['parentNumber'] = "Drawn Structure"
        dict_0['MF'] = None
        dict_0['MW'] = None
        dict_0['stereoIsomerCode'] = stereoisomer_code
        dict_0['Comment'] = None
        dict_0['matchStructure'] = right_image_name
        list_structure.append(dict_0)
        unqc_check="There is no structure found in uniqueness check"

else:
    unqc_check = uniquness_check

code = str(stereoisomer_code) + "-" + str(stereoisomer_name)
print("...main file..",stereoisomer_code,error_msg)

@after_this_request
def remove_file(response):
    ext = [".png", ".mol"]
    global list_current_file
    try:
        files_in_dir = os.listdir("static")
        filtered_img_mol = [file for file in files_in_dir if file.endswith(tuple(ext))]
        files_to_remove=[x for x in filtered_img_mol if x not in list_current_file]
        for file in files_to_remove:
            os.remove("static/" + file)
        list_current_file=[]
    except Exception as e:
        list_current_file=[]
        print(e)

    return response

#return app.send_static_file('pre_check_form.html', left_image=left_image_name, right_image=right_image_name,code= code,error=modification_msg,check=list_structure,sweetalert="Registration Pre-Check",uc_msg=unqc_check)

return render_template('pre_check_form.html', left_image=left_image_name, right_image=right_image_name,code= code,error=modification_msg,check=list_structure,sweetalert="Registration Pre-Check",uc_msg=unqc_check)

@app.route('/services/eln/user/bearerTokenExchange.html')
def bearerTokenExchange_user_html():
return render_template('bearerTokenExchange.html')
@app.route('/services/eln/user/bearerTokenExchange')
def bearerTokenExchange():
# ToDo: Insert bearerTokenExchange code here
return jsonify({"request.path": request.path}, {"request.args": request.args}), 200
If we're running in stand alone mode, run the application
if name == 'main':
app.run(host='<IP_ADDRESS>', port=5000, debug=True)

Hi,
Is the data sufficient for your reference. Let me know if need anything from my end

Hi @SYKAMR, you didn't provide the installed packages.
But from your first error message, it seems like your issue should be fixed by installing connexion with the swagger-ui extra:
pip install connexion[swagger-ui]
If this doesn't fix your issue, please provide a minimal working example we can use to reproduce the issue.


when fetching groups, capture error 403 as rbac failure and cache result

Closes: #1317
Description

As part of a normal flow, /api/k8s/apis/user.openshift.io/v1/groups is queried from the project details page. There was however a check in place where this call was skipped if useUser().isAdmin === true. Instead of using this check, we ought to be checking rbac. If the user has permissions to get a resource, we should let them. By simply removing this check we now have to handle error 403. Or we could perform a self subject access review prior to making the call. I've opted to handle the 403 request as it provides the same feed back as first performing a self subject access review check. useAccessReview is a utility that can be used know if a user has permissions to perform an action. This utility would cache the result such that no further network calls are performed to get the same result. This means if a user is visiting a page and their permissions change in the process, they would require a refresh of the page / component to retrieve the new permissions. As such I have implemented a cache in useGroups when an error 403 occurs to mimic the same functionality.
No visible UI changes.
How Has This Been Tested?

Be an admin, not a cluster-admin
Create a DS Project (or be shared one, as admin)
Navigate to the permissions tab inside the Project details
If you have access to groups -- you should see a dropdown for the group section, if you don't you will just have a text input
Using web inspector, check the network tab for calls to the /api/k8s/apis/user.openshift.io/v1/groups endpoint.
If the call is successful 200, subsequent calls will be made every time POLL_INTERVAL ticks (30s).
If the call is error 403, subsequent calls will not be made.

Test Impact

A followup PR with unit tests will be contributed.
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

/approve


Inspect binary data bug

crystal eval 'p File.read("/home/kostya/1.png")'
Invalid byte sequence in UTF-8 string (InvalidByteSequenceError)

ruby -e 'p File.read("/home/kostya/1.png")'
"\x89PNG\r\n\u001A\n\u0000\u0000\u0000\rIHDR\u0000\u0000\u0000A\u0000\u0000\u0000A\b\u0002\u0000\u0000\u0000\u0001\x95^\u0012\u0000\u0000\a\x89IDATh\x81\xEDZOL\u0014W\u0018\x9F\u001D\u0016\xD9MwH\xC7.Ig\x96=\xB8\av:\xDBJʺ\x86F\xD2\u0003\u0010\x9B\xAA\u000

in some places i just want to inspect data to debug it, but get this exception

Yes, I agree this is annoying. inspect should be resilient here. Or maybe String.new(...) should raise if it's not properly encoded in UTF-8. Related to #2130

#triage
Still an issue, the only part that has changed is a more informative error message:
Unexpected byte 0x89 at position 0, malformed UTF-8 (InvalidByteSequenceError)


fix(inductive_compiler/ginductive.cpp): debug code did not compile

Thanks @johoelzl for pointing this out. It compiled in Release mode because the offending lines are preprocessed out.

An assertion fires in init. I have a meeting, I'll fix this in an hour.


Bug: Clipping attachment prevents rendering of subsequent attachments in draw order

Attachments in the draw order after a clipping attachment are not rendered in PixiJS, even if they aren't clipped themselves. This occurs despite all elements being visible in the Spine editor.
Everything on the right side of the portal is supposed to be visible, as it is in the editor.

However, it looks like attachments after the clipping attachment in the draw order are not rendered in PixiJS.

Repo: https://github.com/FacePlace/pixi-spine-clipping-demo
pixi.js - 8.2.1
@pixi/spine-pixi  - 2.0.2

I believe I am also having the same issue with clipping not applying to the correct slots, with animations looking fine in the skeleton viewer, but not when ran in pixi. (I had some discussion on the matter in the PixiJS discord in the pixi-spine channel).

This PR (https://github.com/pixijs/spine-v8/pull/29) should address the problem.
Not 100% sure will address all problems because I don't have access to your assets.


Introduce tests

ref #233
adds a few tests using Ava and NYC like other ZEIT projects

Awesome, thank you! 😊


Deterministic publish order

Currently the build extractors for Ivy and Gradle store the resulting list of artifacts to publish in a HashSet. This causes the artifacts to be published in a random order. This updates that to use a TreeSet and provides comparable implementations for related objects so that the published artifacts occur in a deterministic order. This is really helpful for us to determine when a build is complete. This would solve https://www.jfrog.com/jira/browse/GAP-181 in a more predictable manner than is currently implemented.

Hi @arothian,
Thanks for this contribution!
I am currently working on testing these changes and will let you know once I'm I will have any conclusions.


Error on Output explanation of fourth problem

In output explanation of fourth problem you added 20 days to 20/12/2019 and made it to 10/01/2020 but logically december has 31 days. So 09/01/2020 would be the correct date of expiry. Change this as soon as possible.

It is given in the problem statement that to assume each month has only 30 days.

In output explanation of fourth problem you added 20 days to 20/12/2019 and made it to 10/01/2020 but logically december has 31 days. So 09/01/2020 would be the correct date of expiry. Change this as soon as possible.

Thank you for your clarification.
On Sat, Dec 5, 2020 at 11:00 AM rohithmsr<EMAIL_ADDRESS>wrote:

It is given in the problem statement that to assume each month has only 30
days.
In output explanation of fourth problem you added 20 days to 20/12/2019
and made it to 10/01/2020 but logically december has 31 days. So 09/01/2020
would be the correct date of expiry. Change this as soon as possible.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SVCE-ACM/A-December-of-Algorithms-2020/issues/19#issuecomment-739129550,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANMVJEKGXCHVAMERLXTKYM3STHAQ3ANCNFSM4UOGXY7A
.

@suren003 Thank you for clarifying queries. Your support is greatly appreciated 💯

You updated problems for december 6 to december 9 but that doesn't show in
my forked repo. How should i update that in my repo?
On Sat, Dec 5, 2020 at 7:48 PM Krishnakanth Alagiri <
<EMAIL_ADDRESS>wrote:

@suren003 https://github.com/suren003 Thank you for clarifying queries.
Your support is greatly appreciated 💯
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SVCE-ACM/A-December-of-Algorithms-2020/issues/19#issuecomment-739256724,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANMVJEJRBDNC56D5QPV6HPLSTI6MNANCNFSM4UOGXY7A
.

I found the way and forked the changes into my repository. Thanks.
On Sun, Dec 6, 2020 at 9:37 AM suren dran<EMAIL_ADDRESS>wrote:

You updated problems for december 6 to december 9 but that doesn't show in
my forked repo. How should i update that in my repo?
On Sat, Dec 5, 2020 at 7:48 PM Krishnakanth Alagiri <
<EMAIL_ADDRESS>wrote:

@suren003 https://github.com/suren003 Thank you for clarifying
queries. Your support is greatly appreciated 💯
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SVCE-ACM/A-December-of-Algorithms-2020/issues/19#issuecomment-739256724,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANMVJEJRBDNC56D5QPV6HPLSTI6MNANCNFSM4UOGXY7A
.


Nuttx v3 master

Update to master -
N.B. To fit on V2 HW
The following are turned off on px4fmu-v2
new logger
drivers/snapdragon_rc_pwm
drivers/lis3mdl

I'm pretty sure they use drivers/snapdragon_rc_pwm.

@dagar - Thank you - OK I will work from your list.

How about blinkm?
drivers/blinkm

Are all of these range finders actively used?

drivers/srf02
drivers/sf0x
drivers/ll40ls
drivers/trone

Does anyone actually have an lis3mdl yet?

drivers/lis3mdl

How many pixhawks with an mpu9250 are in the wild?

drivers/mpu9250

We may be able to disable some new nsh command to save space
From nuttx_v3:
  [           dirname     free        mkfifo      rm          uname
  ?           date        help        mkrd        rmdir       umount
  basename    dd          hexdump     mh          set         unset
  break       df          kill        mount       sh          usleep
  cat         echo        ls          mv          sleep       xd
  cd          exec        mb          mw          test
  cp          exit        mkdir       ps          time
  cmp         false       mkfatfs     pwd         true

master:
  [           dd          hexdump     mkfifo      pwd         umount
  ?           df          kill        mkrd        rm          unset
  cat         echo        losetup     mh          rmdir       usleep
  cd          exec        ls          mount       set         xd
  cp          exit        mb          mv          sh
  cmp         free        mkdir       mw          sleep
  date        help        mkfatfs     ps          test


Documentation conflicts with reality

The documentation for conversion creation states that term_agreement is a boolean value and must be true for things to go ahead.  However, if you actually send boolean True through currencycloud.Conversion.create, it barfs complaining that the term_agreement must be true.
The only way to get it to actually work is to pass the literal string "true", which is of course boolean true, but then again so is "false".
If as the documentation states, the server requires a boolean true, then the client library needs to accept boolean values.  If however the server requires string "true" then the documentation should be amended or the server should be fixed to actually accept boolean values.

The documentation for retrieve multiple rates includes an example request that is not in fact a request for any rate at all, and the example response includes rates for two distinct currency pairs even though the arguments section only allows for one currency_pair argument.
When actually querying the API, I'm left trying to guess the behaviour:
One rate:
curl -X GET --header "X-Auth-Token: [redacted]" https://devapi.currencycloud.com/v2/rates/find?currency_pair=GBPUSD
{"rates":{"GBPUSD":["1.407700","1.408300"]},"unavailable":[]}

But how do you get more than one rate?
Passing currency_pair multiple times appears to just have the last argument overwrite the rest:
curl -X GET --header "X-Auth-Token: [redacted]" 'https://devapi.currencycloud.com/v2/rates/find?currency_pair=GBPUSD&currency_pair=EURCAD'
{"rates":{"EURCAD":["1.495000","1.495500"]},"unavailable":[]}

And even using PHP's kooky [] format fails, at least this time with a useful error:
curl -X GET --header "X-Auth-Token: [redacted]" 'https://devapi.currencycloud.com/v2/rates/find?currency_pair%5B=GBPUSD&currency_pair%5D=EURCAD'
{"error_code":"invalid_extra_parameters","error_messages":{"base":[{"code":"invalid_extra_parameters","message":"Invalid extra parameters:'{:\"currency_pair[\"=>\"GBPUSD\"}'","params":{"parameters":{"currency_pair[":"GBPUSD"}}}]}}

So either the documentation is lying and you can't get multiple rates, or you can, and the documentation is simply not documenting it.

The documentation describes parameters and their types from the server's REST invocation perspective and not from any given SDK (as type definition will vary from language to language). It's therefore correct to identify as boolean since it is a defined value in JSON (please see json.org)
There is an issue however in that the SDK does not map correctly the Python boolean True to the JSON true. We may address this in a future release.
Regarding multiple rates retrieval, the documentation wasn't lying but it wasn't being clear either. The correct way to retrieve multiple pairs is to provide the values in a comma separated sequence:
curl -k -X GET 'https://devapi.currencycloud.com/v2/rates/find?currency_pair=EURGBP,GBPUSD' -H 'X-Auth-Token: deadbeefdeadbeefdeadbeefdeadbeef'

or, in the case of the Python SDK:
rate = client.rates.find(currency_pair='EURGBP,GBPUSD')

We have addressed this deficiency in our documentation and now offer live testing on selected resources. Please try Get Detailed Rates, enter EURGBP,GBPUSD in the currency_pair value box and then Run the Code
Lastly, it shouldn't have taken this long to answer these questions. But it did, and for that we apologise. We will do much better from now on.


Ruff incorrectly ignores Python files included by negated pattern in .gitignore

Given the following .gitignore:
*
!/src/
!/src/**

and a file src/foo.py, ruff src/ outputs warning: No Python files found under the given path(s). Given that Git includes this file due to the negated pattern overriding the *, this seems like a bug.
This is with 0.1.6 and no Ruff configuration in pyproject.toml.

@BurntSushi -- We use the ignore crate for .gitignore behavior. Would you expect src/foo.py to be included based on the above? (It could definitely be an error on our side and not in the ignore crate, but wanted to check with you first.)

Seems like this might be https://github.com/BurntSushi/ripgrep/issues/1050

It might also be this: https://github.com/BurntSushi/ripgrep/issues/1757 (A fix was merged recently but I believe it has not been released yet.)
But yes, this looks like a bug in the ignore crate to me.

@BurntSushi -- We use the ignore crate for .gitignore behavior. Would you expect src/foo.py to be included based on the above? (It could definitely be an error on our side and not in the ignore crate, but wanted to check with you first.)

I would expect files that are checked into git with git add --force to be checked, but maybe that is just me? :thinking:

The ignore crate only reads .gitignore files. It doesn't actually read the git repository state to determine what's tracked and what isn't. One possible work-around to this is to ensure that .gitignore files are in sync with your repository state.

@BurntSushi - Did that fix go out in the latest version of ignore?

Yeah if the issue here is https://github.com/BurntSushi/ripgrep/issues/1757 then that's in the latest ignore release.
But https://github.com/BurntSushi/ripgrep/issues/1050 remains unfixed.

I actually can't reproduce this on v0.1.6. @henribru - is that the exact pattern and directory structure you were using?

I actually can't reproduce this on v0.1.6. @henribru - is that the exact pattern and directory structure you were using?

Yes. But I discovered something curious: It only seems to reproduce on Windows.


run flake8 on all templates in the create workflows

So that we see earlier whether during refactoring we killed flake8.

Closed by #170


Switched out Google+ login with generic Google login

@katfang please review and merge. Fixes #11
Should conform to the docs here: https://developers.google.com/identity/sign-in/ios/

Yaaay! Thanks for entertaining my nitpicks.
Merging in. :)


Not opening on tablet

Can not finish setup or get past fingerprint verification on a specific tablet.

Fixed 4ef6d429f85f9dfa56b9a164f843e02fceec09db


Excluding certain routes when BASIC_AUTH_FORCE = True

Hi, would you be interested in a patch that adds support for excluding certain routes when BASIC_AUTH_FORCE = True? I want to protect all endpoints with the exception of for example /healthcheck.

Related: exclude certain methods, like OPTIONS, which is required for CORS, but which can't contain Authorization header.

This might help: https://github.com/jpvanhal/flask-basicauth/pull/14 .

#14 resolves the CORS issue, but not the /healthcheck issue.
@domkck did you end up writing that patch?
I assume we just need something like @basic_auth.required, but the opposite.

@jpvanhal  this repo hasn't been updated in a while. Can you confirm that if I write a PR for this that you'll accept it?


Create Pagination logic

Pagination
Leverage gatsby-node.js to create a pre-filtered page of data per each of the 50 states. This will create some nice SEO opportunities to have a URL per state of black owned businesses. It will also allow us to properly categorize data that does not have complete information, and ensure that they can still be included and searched for on the site.

Another option is the split it up by category, but I think that will be partly dependent on how the quantity of data of each is split up.

@magnificode looks like this can be closed.  Great work @jbolda!


Kumma md file

Adding Kumma md file, for the new Kumma adapter.

Related PR: https://github.com/prebid/Prebid.js/pull/1512


Increase the KeepAlive timeout to 1.5x the connection's keepalive

This is per section <IP_ADDRESS> of the MQTT 3.1.1 spec:
If the Keep Alive value is non-zero and the Server does not receive a
Control Packet from the Client within one and a half times the
Keep Alive time period, it MUST disconnect the Network Connection to
the Client as if the network had failed [MQTT-3.1.2-24].
A client with a 20-second Keepalive was sometimes being disconnected before it
could send its next pingreq:
<0.20829.0>@vmq_mqtt_fsm:connected:411 [<0.20829.0>] stop due to keepalive expired

Hi @kellycampbell thanks for the PR - we'll try to review as soon as we have a moment free.

get_right_keepalive(KeepAlive) ->
    (KeepAlive * 3) div 2.

Maybe this is better, change the value in one place.

Hi all, I've created another PR #294 which should fix this issue.
The PR doesn't change when the keepalive timer is triggered (a heuristic of 0.75 * the client keepalive value), but will disconnect when, in a check, the last incoming packet is longer ago than 1.5 times the client keepalive value. I hope that makes sense.

fixed in #294

Sounds great. Thanks!

No problem, sorry for the delay.


fix(fe): fix refetch on window focus option

Description
window tab이 바뀔 때마다 refetch 해오는 문제를 해결합니다
캐싱을 위해 stale time을 추가했습니다
Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines
[x] Read the Contributing Guidelines and follow the Commit Convention
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

캐싱 추가하면 admin에서 문제나 contest 수정하면 적용 안될 것 같은데 해당 부분은 없는 게 좋을 것 같아요!


Integrate distributed inference with chat/server

This PR integrates distributed inference with the CLI options chat and server and implements Option 2b of #1376.
To test run on machine with 4 gpus:
python  torchchat.py chat llama3.1  --max-new-tokens 10  --distributed --tp 2 --pp 2
python  torchchat.py server  llama3.1  --max-new-tokens 10  --distributed --tp 2 --pp 2

This PR integrates distributed inference with the CLI options chat and server and implements Option 2b of #1376.
To test run on machine with 4 gpus:
python  torchchat.py chat llama3.1  --max-new-tokens 10  --distributed --tp 2 --pp 2
python  torchchat.py server  llama3.1  --max-new-tokens 10  --distributed --tp 2 --pp 2

Should torchchat generate work as well, code would suggest that we can do like so:
python  torchchat.py generate llama3.1  --max-new-tokens 10  --distributed --tp 2 --pp 2

@mikekgfb Yes, distributed generate was already working before this PR, thats why I did not list it separately.


Intellitrace support?

Is there a way to get Entity Framework Core queries to show up in the Diagnostic Tools window in Visual Studio?
Is this currently supported, or will it be?
I see that Application Insights can capture when a query occurs, but doesn't capture much detail (no script, no line numbers, etc.).

@joshmouch SQL Server queries should be showing up already. Are you asking this for some other provider?

No, I'm asking for SQL Server.
Do you need VS Ultimate to view them?
Would using the Microsoft.AspNetCore.TestHost.TestServer and initiating the requests from an xunit test cause them to not show up in any way?
The only events I see in the Diagnostic Tools are "Application Insight" events.

@joshmouch In full .NET Framework, SQL Client had Intellitrace integration. My understand is that this is not available in .NET Core. As of right now, I am not sure what is sending messages where, but I have opened #8009 to investigate and track this.


multi-stage build fails on Orange Pi Plus 2

Hello everybody!
While maintaining my server this afternoon I happily realized that the companion finally received an update for multiplatform support, so I was eager to check out the update.
Unfortunately Building the image on my Orange Pi Plus 2 fails with the following error:
# github.com/docker/docker/vendor/github.com/opencontainers/runc/libcontainer/system
src/github.com/docker/docker/vendor/github.com/opencontainers/runc/libcontainer/system/linux.go:119:89: constant<PHONE_NUMBER> overflows int

my docker-compose.yml:
letsencrypt-companion:
    build:  https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion.git
    container_name: ${CONTAINER_NAME}_letsencrypt-companion
    restart: always
    volumes:
      - certs:/etc/nginx/certs
      - conf.d:/etc/nginx/conf.d
      - vhost.d:/etc/nginx/vhost.d
      - html:/usr/share/nginx/html
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      NGINX_DOCKER_GEN_CONTAINER: ${CONTAINER_NAME}_docker-gen
      NGINX_PROXY_CONTAINER: ${CONTAINER_NAME}_nginx-web
      DHPARAM_BITS: 4096
      DEBUG: "true"
    depends_on:
      - nginx-web
      - docker-gen

Any idea whats causing this overflow?

Google tells me it looks like a nasty bug related to 32 bits Arch in either Go or Docker.
I'm not sure we can be of any help. :confused:

Closing due to inactivity.


Describe the philosophy of VISSL benchmark dataset contribution and enrich the list of available benchmarks (take 2)

This PR is a rebase of https://github.com/facebookresearch/vissl/pull/181, completed with a few additional benchmarks and improvements:

the number datasets has increased from 2 to 9 (mostly inspired by the VTAB benchmark suite and the CLIP paper)
data preparation scripts now all follow the same interface (same parameters to execute the script)
data preparation scripts now all automatically download the dataset in case this one is not present
some benchmarks have been moved out of "datasets" since their results are in line with the CLIP paper results

This PR needs to be further completed:

Documentation has been reworked, but still needs work to add all the scripts.
Benchmarks also need some polishing.

this is a LOT of really AWESOME work @QuentinDuval ! and look at all those new datasets numbers!! very exciting and the documentation is excellent. the PR is good to go. just one major comment for the full PR
we need to add the copyright # Copyright (c) Facebook, Inc. and its affiliates. All Rights Reserved to all the .py files at the very top as the very first line! :)

@QuentinDuval , it seems like we need to rebase the PR on latest vissl master (one gpu test that's failing is a flaky test but fixed in vissl master) :) We should also click on "Import to Phabricator" again (the import failed due to old master) :)

It looks like we figured out internally what was going on :) The next steps are:

You should commandeer your diff back . To do so, go to the phabricator and scroll all the way down to the "Comment" box and you will see the option Commandeer option when you click on Comment :)
Fix the linter errors -> we should likely do that in a follow-up PR and aim to land this PR as is without any further shipIT issues


How is syntax highlighting expected to work?

I'm using Markdown like this:
```csharp
// Some C# code
```

And it generates HTML like this:

  // Some C# code

That's great in terms of CommonMark.NET parsing - it definitely understands my Markdown properly. But the output isn't syntax-highlighted as I'd like it to be. Is there a known syntax-highlighting library/stylesheet which works well with this? It doesn't seem to be what Prettify expects, for example.
Apologies if this has already been covered somewhere - I haven't found it in the issues.

highlight.js supports this syntax for code blocks out of the box.
http://codepen.io/anon/pen/VPdOVo

Great, thanks. I now need to sort out some other aspects of my CSS, but this is great :)

Prism.js will also work: http://prismjs.com/


Add proper documentation

Add proper documentation

I don't know what generator to use. I could try using md files


Some text styles are white in the light version

This makes some text very hard to read. For example:

According to the style guide, @text-color-highlight and  @text-color-selected are set to white. Maybe these are the culprits?

Thanks for the issue. Looks like you're using 0.8.0. Development focus in now on 1.0 which was published briefly some time ago and unpublished due to the number of bugs in it.
If you want to try the latest version, download it and unzip it to C:\Users\jason\.atom\packages\.

Thanks! Awesome work!


ASCII of 5 added

Filled matrix with proper symbols so that a 5 digit is generated.

@im0vishal did you commit the code? currently, your PR shows no relevant file changes.


Use of unresolved identififer 'HighlightButton'

We've got some issues with the latest master:

You can't not use the HighlightButton type directly, as it's an implementation detail of BulletinBoard, and is hidden to apps to avoid animation issues when using it inside bulletin items.
However, if you update to the latest master (after 1c7243bbc0cd0842e51e62aaa80bffbb71d3b43f), you can use the following code:
public func makeInfoButton() -> HighlightButtonWrapper {

    let wrapper = HighlightButtonWrapper()
    let infoButton = wrapper.button

    infoButton.setImage(UIImage(named: "icon-calendar-single-remove"), for: .normal)

    infoButton.contentHorizontalAlignment = .center
    infoButton.contentVerticalAlignment = .top
    infoButton.autoresizingMask = .flexibleWidth

    wrapper.setContentHuggingPriority(UILayoutPriorityDefaultLow, for: .horizontal)
    wrapper.heightAnchor.constraint(equalToConstant: 44).isActive = true

    return wrapper

(P.S. Sorry for the delay 😬)

Closing this issue for now. Feel free to reopen it if you still need help.


not working in firefox 59.0b4 (64-bit)

drag and drop working all browser (chrome, IE) but not working in  firefox 59.0b4 (64-bit)

I am also having this issue.  It seems to work in Firefox on your demo, but it is not working in my app... however, I have no issues when using the app on Chrome.


primaryKey + type:'string' = unhelpful auto change to int

Waterline version<EMAIL_ADDRESS>from<EMAIL_ADDRESS>Node version: v6.3.1
NPM version: 3.10.3n
Operating system: Mac OS Yosemite

Setting a waterline model's attribute to be both:
primaryKey: true,
type: 'string', (or type: 'float', which is internally currently saved as a string)
Will result in the attribute automatically changing to an integer. This caused me at least an hour of headache, and should at least warn the user. An error would've been preferred, detailing that this isn't currently allowed.
In SQL, you CAN use a string as a primaryKey, as was my intention, since floats aren't an option. My user base will not fit in an "integer" field, thus requiring float/string. This is a problem that people making large-scale apps will hit.
In addition, using these two:
type: float/string,
autoIncrement: true,
I forgot what this does; but it either converts it to type:integer as well, or does something else weird. Attribute combination should probably have a little more error checking overall

Added version information


Fix django view json loads error

Discovered a bug when testing the django_chatterbot. This patch solves the problem.

Hi @barseghyanartur Thank you for the pull request. The example at https://github.com/gunthercox/django_chatterbot is no longer actively maintained. A while back the example was moved to: https://github.com/gunthercox/ChatterBot/tree/master/examples/django_app
It is very likely that the issue you encountered no longer exists in the updated version of the app. Would you mind confirming that?

@gunthercox:
I see. I'll confirm it tomorrow and let you know. Thanks!
Perhaps a notice "This is no longer actively maintained" with link to the well maintained version would be useful then.


Molecule packaging

TODO: Add more supported systems;

[ ] Al2022
[ ] Debian
[ ] Suse

Debian has some issues when installing the infra-agent inside a Docker container. Setting DEBIAN_FRONTEND=noninteractive solves the problem.


Release 0.17.1

Install specific salt version on AWS (#8131)
Revert "Introduce an 'svc' segment for DNS search" (#8568)

@googlebot CLAs are good, thanks!

cc @thockin: Holding on you. @ArtfulCoder says you want to fight for #8501

I would like to recommend : #8501 " Support old and new style dns service names."
The dns.go e2e test passed in Jenkins-gce-e2e-run-6266 though the entire e2e run is not complete. (part of build # 2622)
This is a multi-release rollout for adding svc label to DNS names for services.
I think we should have #8501 in 0.17.1 since its step 1 towards that goal.

I'm against this mainly because it hasn't had enough bake time, and we're only 5 days from 0.18.0. We'd like to ship 0.17.1 to GKE this week, and that PR increases the risk pretty dramatically due to almost no burn-in.

cc @roberthbailey @quinton-hoole

Will check shortly...
On May 21, 2015 10:52 AM, "Zach Loafman"<EMAIL_ADDRESS>wrote:

cc @roberthbailey https://github.com/roberthbailey @quinton-hoole
https://github.com/quinton-hoole
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/8626#issuecomment-104370502
.

Ran 38 of 43 Specs in 1425.264 seconds
SUCCESS! -- 38 Passed | 0 Failed | 1 Pending | 4 Skipped I0521 11:05:37.416564   18737 driver.go:96] All tests pass

Will wait for the final decision on #8501

Something went seriously pear-shaped in the 9:53AM run e2e continuous integration run today, immediately after #8501 merged.  I don't have any reason to suspect #8501 yet, but it's probably worth either excluding it from the release, or explicitly vindicating it from the above run.
Build #6266 (May 21, 2015 9:53:11 AM)
(11 failures / +8)
Kubernetes e2e suite.Reboot should reboot each node and ensure they function upon restart
Kubernetes e2e suite.Services should serve multiport endpoints from pods
Kubernetes e2e suite.Cluster level logging using Elasticsearch should check that logs from pods on all nodes are ingested into Elasticsearch
Kubernetes e2e suite.PD should schedule a pod w/ a readonly PD on two hosts, then remove both.
Kubernetes e2e suite.Networking should function for intra-pod communication
Kubernetes e2e suite.Shell tests that services.sh passes
Kubernetes e2e suite.Services should serve a basic endpoint from pods
Kubernetes e2e suite.PD should schedule a pod w/ a RW PD, remove it, then schedule it on another host
Kubernetes e2e suite.Density [Performance suite] should allow starting 30 pods per node
Kubernetes e2e suite.Services should be able to create a functioning external load balancer
Kubernetes e2e suite.Services should correctly serve identically named services in different namespaces on different external IP addresses

This discussion has timed out. If someone wants a 0.17.2, we can make it happen. Requesting merge.

The build following the 9:53am run (at 11:05am) timed out and failed after 90 minutes. Right now we have no successful e2e runs with #8501 at head so I don't think it makes sense to cherry pick it into the 0.17 release branch for 0.17.1.

@justinsb FYI -- 0.17.1 will have a couple of cherry picks for AWS cluster set up.

Agreed with @roberthbailey especially I saw dns failure consistently this morning.

I am going to merge this as is.


First Alpaka Kernel Rewrite + Initial Setup

Initial setup that allows Alpaka code to run alongside CUDA code, and the first rewrite of a kernel (ModuleRangesKernel) in Alpaka. Most of the commits here are just bringing the alpaka_move branch up to date with master btw.

Hi Gavin,
I took a look at the PR. However, it is a bit difficult to have a clear picture of the changes, since this PR seems to reapply all of the recent changes to the master.
Should we not freeze the developments of the alpaka_move branch, so that we can easily track down what changes with the migration? I understand that this could mean a lot of work at end, which may not be preferable.
The other solution would be to rebase both the SegmentLinking/alpaka_move branch and yours to the master developments, so that the differences between between them are only the alpaka related ones. To me, this seems like the optimal solution but I leave it to you and others to comment on the best way to do this.

Hey @VourMa I rebased alpaka_move so that now only the relevant commits are shown.

Merging this to have a basis for our alpaka setup in the common SegmentLinking/alpaka_move branch.
The plan would be to have a draft PR from SegmentLinking/alpaka_move to SegmentLinking/master to keep track of the whole migration (rebasing when needed) and have any discussion on our strategy there. We will be making incremental PRs from other branches to SegmentLinking/alpaka_move.


Bump the TF ARO provider version and test Private cluster without PIP

Due to the availability of deploying private clusters without a public IP is now GA, and with the support provided by the TF ARO provider (kudos to @datianshi), adjustments need to be made in the TF Code for deploying Private ARO clusters.
Testing needs to be conducted with the new version and new flags in the TF ARO code:
terraform {
  required_providers {
    azureopenshift = {
      source    = "rh-mobb/azureopenshift"
      version   = "0.2.0-pre"
    }
  }
}

and
network_profile {
    outbound_type = "UserDefinedRouting"
}

Testing work tracked in https://github.com/rh-mobb/terraform-aro/tree/feature/no_public_ip branch

Close this due to PR https://github.com/rh-mobb/terraform-aro/pull/24 is merged


ISSUE #15336 - Added type and status for test case list

Describe your changes:

added testCaseType and testCaseStatus query params for test case list endpoint
added status and entityLink fields in test_case table for query filter

Type of change:

[ ] Bug fix
[x] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My PR title is Fixes <issue-number>: <short explanation>
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

Improvement

[x] I have added tests around the new logic.
[x] For connector/ingestion changes: I updated the documentation.

Part of #15336 cc @ShaileshParmar11


First release of radseq

PR checklist

fixes based on linting tests. Removed params from nextflow.config tailored to testd-ataset.
updated documentation, in particular, the sample sheet section.

@Gabriel-A-Barrett for a first release, we'd need to do a community review first


Add new stable version 2022-09-01 and refine the folder structure

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

This pull request is to add a new stable version 2022-09-01 based on 2021-12-01-preview. No new apis are added and no update for current apis.
Also, old versions are removed to legacy folder. In new version 2022-09-01, we use sub-service folder to organize our specs

We support both flexible server and single server, so the avocado issues is as expected. All Model validation is against legacy version and we will not touch that specs any more. Since there is no actual update on apis, so we can ignore the breaking changes.

We support both flexible server and single server, so the avocado issues is as expected. All Model validation is against legacy version and we will not touch that specs any more. Since there is no actual update on apis, so we can ignore the breaking changes.

Then we can ignore legacy ModelValidation failure,


Mattermost moving to API version 4

Hey @makmu !
First, hugely appreciate you sharing this project back with the world. Fantastic work!
I wanted to let you know about our plans moving to API v4:
To make the Mattermost API web service easier to use and to offer more powerful options for these integrations, Mattermost will be moving to a new API version soon.  Highlights include:

Fully documented API endpoints
More in-depth access to server functionality
Wider use of established HTTP verbs
Consistent endpoint structures
A new and improved Go driver

We plan to release API version 4 on March 16th, with Mattermost server 3.7.  While the current API version 3 will be supported until September 16th, we recommend you begin using API version 4 soon after its release.
Contributing
API version 4 is an active and on-going project. If you're interested in helping contribute, please join our Mattermost community instance and the APIv4 channel.
We've prepared a contribution process for APIv4 and a progress tracker for new APIv4 enpoints to help you get started.
We're also open for suggestions on adding new API endpoints to help with your integration.

APIv4 support is now available with version 2.0 https://github.com/makmu/outlook-matters/releases/tag/v2.0.0


Python model unit test bug fixes

The AutoregressionX test was comparing to the wrong value from the source data.
The RegressionARIMA test had a copy/paste error in the model source data.

Looks good.  Merging this.


6.2.13 no longer works and causes error regarding stdout_lines

Please review the last commit to update 6.2.13 as it now causes an error in our build.

TASK [RHEL7-CIS : SCORED | 6.2.13 | PATCH | Ensure users' .netrc Files are not group or world accessible] ***

fatal: [<IP_ADDRESS>]: FAILED! => {"msg": "'list object' has no attribute 'stdout_lines'"}

Using ansible version: 2.9.6

Try reverting fe3cda35b5cf28e9ee35419a8bab2c9dfa6dba93?

Thanks. Not sure why CI didn't catch it the first time. Will revert.

#151 isn't compatible with #152
Part of #152 was changing all instances of users.stdout_lines to users.

So I guess it was a semantic conflict, not text conflict. I'll try to rerun CI immediately prior to merge, hopefully catching such things next time.

Hello,
I wanted to reach out and let you know that this issue is being closed. We have re-worked the role and want to start with a fresh issues list with this latest version. There was a post in the Ansible-Lockdown google group (https://groups.google.com/g/ansible-lockdown) with the details of the changes that are coming. Please checkout the thread titled RHEL 7 CIS and STIG Changes for all of the details, I also have the message pasted at below.
Please as you use the latest version and open issue tickets as you find them, it is the best way for us to improve the role for everyone. Thank you for being part of the community and providing awareness of problems or advice on improvement. Reporting is a huge part of improving this project.

Hello,
Thank you to everyone in the Ansible-Lockdown community who has contributed to RHEL7 STIG/CIS. Our team at MindPoint Group has been working with the entirety of the Ansible-Lockdown project, and we have some significant updates for both RHEL 7 STIG and CIS. With these updates, some larger changes have been made. I have these changes/updates outlined below.
Testing:

CI/CD - We have implemented some automated testing pipelines to test pull requests into the devel and main branches. With the current workflow, the community will PR into the devel branch (never the main branch) for review by the administrators. When your PR is created, the first check will remain the DCO check. The second check is a functional testing pipeline that will automatically perform a functional test of the branch the PR is initiated from. Once both tests pass, someone from the Administrator Team will review the changes and merge them into the devel branch. From there, an additional review is completed before the devel branch is merged into the main branch. Only the Admin Team will perform PRs/merges into the main branch. There is also an automated pipeline for PRs from devel to main. Please do not edit the .github/workflows files since those are used as part of the pipeline.
Compliance Checking – MindPoint Group has been working to create our own compliance audit scan tool. The tool uses a goss framework executable to run custom checks that we have created. The goal is to provide a more thorough check for control compliance and decrease the number of false positives/negatives. For example, it will check the configuration file related to the control and as well as checking if that configuration is active. With a smarter scan, we can hopefully identify attempts to trick scanners as well (for example stacking a parameter in a config file where the first instance is enabled and second disabled. Most audit tools search for the first instance but the application might look for the last instance of the parameter, thus making the scanning tool think it's enabled). In testing, we have found that our audit scan runs significantly faster than other audit tools, reducing audit times. Our audit tool and profiles will have their own repositories in the Ansible-Lockdown org, but within the remediation role there will be an integrated way to incorporate the audit. Keep an eye out for the audit tools as they are released. We plan on developing a goss audit profile for each current remediation role. Going forward, we plan to release a remediation role and goss audit tool profile simultaneously.
Role Updates:
RHEL 7 STIG/CIS – We have re-written much of the RHEL 7 STIG and CIS roles to increase clarity and readability and address some functionality items. We performed these updates while creating our goss testing framework for each of these roles. We plan on pushing our update to the devel and main branches. We will move the current devel and master branches to a devel_stable_ and master_stable_ branch in the respective repositories. Accordingly, community members who rely on the current version can still use that version going forward; this process will not remove what is currently there. The latest versions of the roles have also been updated to comply with the latest benchmarks.
Role Architecture – All roles will change with regard to the structure in the tasks folder. Taking CIS as an example, there will be a folder per section and yaml files for each sub-section. For example control 1.2.1 in CIS will be located in RHEL7-CIS/tasks/section_1/cis_1.2.x.yml. The cis_1.2.x.yml file will contain all controls related to section 1.2.x. This will hopefully make updates to roles a bit easier with less risk. This matches the architecture of our audit tool, creating consistency across remediation and audit platforms. The end goal is to repeat this architecture (the best we can) on STIG roles, but we are starting with CIS.
Existing PRs and Issues – With all of these changes comes the task of cleaning up existing PR’s and issues. Our plan is to close all of the existing PR’s and issues because of the re-work. Our team is growing and should be able to stay on top of the new issues and PRs as they come in.
Again, I would like to thank the community for your involvement in this project. The input and work from the community has contributed significantly to the success of this project. Please keep an eye out for these changes, which will be rolling out in the coming weeks.


release: v1.0.0a3

Signed-off-by: Jiri Kuncar<EMAIL_ADDRESS>

@jirikuncar Did you modify something in this pull request? I merged it but it does not seem to have marked this PR as merged. However I don't see any difference between the patch I just merged and the one here.


Optimized test PR description and their base PR number

#678  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @CatChen and the rest of your teammates on  Graphite


Retry mechanism on some BLE stack errors

Summary
This is a proposed enhancement for discussion.
Today, RxAndroidBle does not support retry mechanism, meaning it has to be handled by upper layer from the application.
An interesting enhancement would be to expose an interface that could be implemented by upper layer if some retry should be applied on conditions.
This could be applied mostly for write operations, and especially long write.
Example: It could be possible that on some tiny embedded devices, that incoming messages are not handled as fast as it is sent by the smartphone. Embedded device will then respond with a GATT_INSUF_RESOURCE                 0x11 and instead of just failing the all payload, a simple retry would be good enough to have it working.
Library version
1.4.3
Actual result
Today, the request is canceled, and for a long write, you will have to retry and mostly facing the same issue next time. Thus, the payload can't be sent.
Expected result
Upper layer implement a retry interface, and check if for example, BLE stack error code is worth a retry.

It took some time but we have finally merged #357 — should be available in 1.5.0-SNAPSHOT already and in 1.5.0 in the upcoming days. 🎉  Thank you for your effort 👍

Hi @dariuszseweryn, thank you!!! I don't see it in the 1.5.0-SNAPSHOT do you know when it will be available. I checked it from the versio uploaded this morning: rxandroidble-1.5.0-20180312.055735-7.aar.

It should be in the snapshot you've mentioned.

Hi @uKL from the source within the archive file, it is not unfortunately. Also this file has been generated before the branch being merged into master .

I merged it at 9:47 UTC
The build ran at 9:57 UTC https://travis-ci.org/Polidea/RxAndroidBle/builds/352249008
This is the artifact rxandroidble-1.5.0-20180312.095700-24.aar
https://i.imgur.com/g5uoxGV.png
I believe your cache is fooling around :)

Ok, I've figured out, https://oss.sonatype.org/content/repositories/snapshots/com/polidea/rxandroidble2 instead of https://oss.sonatype.org/content/repositories/snapshots/com/polidea/rxandroidble. My bad! Any idea when this will be part of rxandroidble2 ? Thanks again for all your hard work guys!

I suppose tomorrow :) We're getting close to a release od RxJava2. FYI, we have gitter for chats :) https://gitter.im/RxBLELibraries/RxAndroidBle


Fix transformation matrix calculation in CameraXBasic

This CL fixes transformation matrix calculation in CameraXBasic. The
transformation matrix here is almost identical to the one in
Camera2Basic except that CameraXBasic tries to merge the 2 scaling steps
together (scale back to the original buffer and scale it down to just
cover the viewfinder). In it, it makes false assumptions about the
orientation of the preview buffer. This assumption propagates the code
written below, causing additional scaling issues on landscape devices
with sensor orientation equal to 0. We rewrite the code here completely
to address the aforementioned issues.
Test: Tested on a 2-in-1 Chromebook and Google Pixel 3 and verified that
CameraXBasic preview looks fine on both devices in landscape and
portrait.

LGTM, thanks!


Cannot upgrade to WSL 2 even enable all the options

Windows version: 10.0.19041.264, windows 10 home edition

What you're doing and what's happening:

enable virtual machine platform
enable linux subsystem
install ubuntu 18.04 from windows store (work well on wsl 1)
enable virtualization in BIOS

What's wrong / what should be happening instead:
When I execute wsl --set-version Ubuntu-18.04 2, it said
"please enable virtual machine platform and enable virtualization in BIOS", but I already open these options

So confused..

Output of systeminfo?

Fantastic. Hours spending an answer on question «Why it worked before windows reinstall and broken after» found in... wtf...
Btw thanku you, your solution worked to me.


Player Indicators: Highlight other players only in wilderness

Is your feature request related to a problem? Please describe.
You can already achieve this by enabling highlight non-clan members whenever you enter the wildy.  The only thing this would really change is the need to toggle it every time you leave so you're not bombarded by dozens of names at the GE.
Describe the solution you'd like
Give us the option to highlight other players only when in the wilderness.  Not asking it to take into consideration whether or not they're attackable or not, just that they're there.

Duplicate of #3684


ACHI maninnet and wallet are synced but doesn't pay reward

You have a plots for farming or you clean ?