How do I adapt or use it in openbullet2?

I recently saw your comment on the ob2 forum and wanted to know how to implement it. I was able to make it listen on <IP_ADDRESS>:8000 in ob2 and in the windows 10 cmd
PS C:> flare_bypass_server
←[32mINFO←[0m:     Started server process [←[36m29524←[0m]
←[32mINFO←[0m:     Waiting for application startup.
←[32mINFO←[0m:     Application startup complete.
←[32mINFO←[0m:     Uvicorn running on ←[1mhttp://<IP_ADDRESS>:8000←[0m (Press CTRL+C to quit)
←[32mINFO←[0m:     <IP_ADDRESS>:63267 - "←[1mGET / HTTP/1.1←[0m" ←[31m404 Not Found←[0m
←[32mINFO←[0m:     <IP_ADDRESS>:63460 - "←[1mGET / HTTP/1.1←[0m" ←[31m404 Not Found←[0m
←[32mINFO←[0m:     <IP_ADDRESS>:63475 - "←[1mGET / HTTP/1.1←[0m" ←[31m404 Not Found←[0m
I didn't quite understand how it's used, so I tried to send the URL in the headers and have the bypass understand it. But I don't know if I did it right. Could you explain to me how it's adapted or used in ob2? Thanks and good work with this great tool!

http://localhost:8000
cmd: request.get
url: https://www.pxxxxx.net/jwl/public/home-en.jsp
maxTimeout: 60000
accept: /
authorization: android-auth-120
from: android-nlFGNlnhpoYgbhoj
gql-access-token: smartworld
session-key: android-session-120
Content-Type: application/x-www-form-urlencoded
Host: polygon.net
Connection: Keep-Alive
Accept-Encoding: gzip
User-Agent:
my telegram is: https://t.me/withoutdudes

{"status":"error","message":"Error: Error solving the challenge. On step 'solving': No module named 'fcntl'","startTimestamp":1730929679.638392,"endTimestamp":1730929679.641323
I managed to solve almost all the errors, including the async one, but I can't run it on Windows since it's only for Linux.

{
"status": "error",
"message": "Error: Error solving the challenge. On step 'navigate to url': [Errno 111] Connect call failed ('<IP_ADDRESS>', 49607)",
"startTimestamp":<PHONE_NUMBER>.737345,
"endTimestamp":<PHONE_NUMBER>.775843
}
I also had errors like this on Linux. It didn't work at all.

root@Ubuntu-2204-jammy-amd64-base ~/flare-bypasser # flare_bypass_server -b xxxxxxxxxxxx:8000
[2024-11-06 20:25:35 +0000] [1057175] [INFO] Starting gunicorn 23.0.0
[2024-11-06 20:25:35 +0000] [1057175] [INFO] Listening at: http://xxxxxxxxxxxx:8000 (1057175)
[2024-11-06 20:25:35 +0000] [1057175] [INFO] Using worker: uvicorn.workers.UvicornWorker
[2024-11-06 20:25:35 +0000] [1057223] [INFO] Booting worker with pid: 1057223
[2024-11-06 20:25:35 +0000] [1057223] [INFO] Started server process [1057223]
[2024-11-06 20:25:35 +0000] [1057223] [INFO] Waiting for application startup.
[2024-11-06 20:25:35 +0000] [1057223] [INFO] Application startup complete.
2024-11-06 20:25:41,485 [nodriver.core.browser] [INFO]: starting
executable :/bin/google-chrome
arguments:
--remote-allow-origins=*
--no-first-run
--no-service-autorun
--no-default-browser-check
--homepage=about:blank
--no-pings
--password-store=basic
--disable-infobars
--disable-breakpad
--disable-component-update
--disable-backgrounding-occluded-windows
--disable-renderer-backgrounding
--disable-background-networking
--disable-dev-shm-usage
--disable-features=IsolateOrigins,site-per-process
--disable-session-crashed-bubble
--disable-search-engine-choice-screen
--user-data-dir=/tmp/uc_34f0xd0r
--disable-features=IsolateOrigins,site-per-process
--disable-session-crashed-bubble
--proxy-server=string
--no-sandbox
--remote-debugging-host=<IP_ADDRESS>
--remote-debugging-port=42023
2024-11-06 20:25:42,251 [nodriver.core.browser] [INFO]: enabling autodiscover targets
2024-11-06 20:25:42,263 [root] [INFO]: New instance of webdriver has been created to perform the request (proxy=string), timeout=60.0
2024-11-06 20:25:42,536 [root] [INFO]: Close webdriver
2024-11-06 20:25:42,537 [root] [ERROR]: Error solving the challenge. On step 'navigate to url': [Errno 111] Connect call failed ('<IP_ADDRESS>', 42023)
Error solving the challenge. On step 'navigate to url': [Errno 111] Connect call failed ('<IP_ADDRESS>', 42023)
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 375, in _resolve_challenge_impl
await self.save_screenshot('evil_logic')
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 203, in save_screenshot
await self._driver.save_screenshot(screenshot_file_without_ext + ".png")
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/browser_wrapper.py", line 139, in save_screenshot
await self._page.save_screenshot(image_path)
File "/usr/local/lib/python3.10/dist-packages/nodriver/core/tab.py", line 1196, in save_screenshot
await self.sleep()  # update the target's url
File "/usr/local/lib/python3.10/dist-packages/nodriver/core/connection.py", line 317, in sleep
await self.update_target()
File "/usr/local/lib/python3.10/dist-packages/nodriver/core/connection.py", line 392, in update_target
target_info: cdp.target.TargetInfo = await self.send(
File "/usr/local/lib/python3.10/dist-packages/nodriver/core/connection.py", line 411, in send
await self.aopen()
File "/usr/local/lib/python3.10/dist-packages/nodriver/core/connection.py", line 285, in aopen
self.websocket = await websockets.connect(
File "/usr/local/lib/python3.10/dist-packages/websockets/legacy/client.py", line 654, in await_impl
_transport, protocol = await self._create_connection()
File "/usr/lib/python3.10/asyncio/base_events.py", line 1076, in create_connection
raise exceptions[0]
File "/usr/lib/python3.10/asyncio/base_events.py", line 1060, in create_connection
sock = await self._connect_sock(
File "/usr/lib/python3.10/asyncio/base_events.py", line 969, in _connect_sock
await self.sock_connect(sock, address)
File "/usr/lib/python3.10/asyncio/selector_events.py", line 501, in sock_connect
return await fut
File "/usr/lib/python3.10/asyncio/selector_events.py", line 541, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
ConnectionRefusedError: [Errno 111] Connect call failed ('<IP_ADDRESS>', 42023)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 251, in _resolve_challenge
return await self._resolve_challenge_impl(req, start_time)
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 423, in _resolve_challenge_impl
raise Solver.Exception(str(e), step=step)
flare_bypasser.flare_bypasser.Solver.Exception: [Errno 111] Connect call failed ('<IP_ADDRESS>', 42023)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypass_server.py", line 82, in process_solve_request
solve_response = await solver.solve(solve_request)
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 222, in solve
res = await asyncio.wait_for(self._resolve_challenge(req), timeout=req.max_timeout)
File "/usr/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
return fut.result()
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 261, in _resolve_challenge
raise Solver.Exception(error_message, step=e.step)
flare_bypasser.flare_bypasser.Solver.Exception: Error solving the challenge. On step 'navigate to url': [Errno 111] Connect call failed ('<IP_ADDRESS>', 42023)
^C[2024-11-06 20:25:50 +0000] [1057175] [INFO] Handling signal: int
[2024-11-06 20:25:50 +0000] [1057223] [INFO] Shutting down
[2024-11-06 20:25:50 +0000] [1057223] [INFO] Waiting for application shutdown.
[2024-11-06 20:25:50 +0000] [1057223] [INFO] Application shutdown complete.
[2024-11-06 20:25:50 +0000] [1057223] [INFO] Finished server process [1057223]
[2024-11-06 20:25:50 +0000] [1057175] [ERROR] Worker (pid:1057223) was sent SIGINT!
[2024-11-06 20:25:50 +0000] [1057175] [INFO] Shutting down: Master
root@Ubuntu-2204-jammy-amd64-base ~/flare-bypasser # ^C
root@Ubuntu-2204-jammy-amd64-base ~/flare-bypasser # sudo ufw status
sudo ufw allow 42023
sudo: ufw: command not found
sudo: ufw: command not found
root@Ubuntu-2204-jammy-amd64-base ~/flare-bypasser # ufw status
Command 'ufw' not found, but can be installed with:
apt install ufw
root@Ubuntu-2204-jammy-amd64-base ~/flare-bypasser #
apt install ufw^C
root@Ubuntu-2204-jammy-amd64-base ~/flare-bypasser # flare_bypass_server -b xxxxxxxxx:8000
[2024-11-06 20:33:33 +0000] [1057586] [INFO] Starting gunicorn 23.0.0
[2024-11-06 20:33:33 +0000] [1057586] [INFO] Listening at: http://xxxxxxxxx:8000 (1057586)
[2024-11-06 20:33:33 +0000] [1057586] [INFO] Using worker: uvicorn.workers.UvicornWorker
[2024-11-06 20:33:33 +0000] [1057634] [INFO] Booting worker with pid: 1057634
[2024-11-06 20:33:33 +0000] [1057634] [INFO] Started server process [1057634]
[2024-11-06 20:33:33 +0000] [1057634] [INFO] Waiting for application startup.
[2024-11-06 20:33:33 +0000] [1057634] [INFO] Application startup complete.
2024-11-06 20:33:40,868 [nodriver.core.browser] [INFO]: starting
executable :/bin/google-chrome
arguments:
--remote-allow-origins=*
--no-first-run
--no-service-autorun
--no-default-browser-check
--homepage=about:blank
--no-pings
--password-store=basic
--disable-infobars
--disable-breakpad
--disable-component-update
--disable-backgrounding-occluded-windows
--disable-renderer-backgrounding
--disable-background-networking
--disable-dev-shm-usage
--disable-features=IsolateOrigins,site-per-process
--disable-session-crashed-bubble
--disable-search-engine-choice-screen
--user-data-dir=/tmp/uc_oo6k6u3y
--disable-features=IsolateOrigins,site-per-process
--disable-session-crashed-bubble
--proxy-server=string
--no-sandbox
--remote-debugging-host=<IP_ADDRESS>
--remote-debugging-port=38719
2024-11-06 20:33:41,634 [nodriver.core.browser] [INFO]: enabling autodiscover targets
2024-11-06 20:33:41,647 [root] [INFO]: New instance of webdriver has been created to perform the request (proxy=string), timeout=60.0
2024-11-06 20:33:42,314 [root] [INFO]: Screenshot saved to '0_evil_logic'
2024-11-06 20:33:42,352 [uc.connection] [INFO]: KeyError: ('DOM.scrollableFlagUpdated',)  during parsing of json from event : {'method': 'DOM.scrollableFlagUpdated', 'params': {'nodeId': 1, 'isScrollable': False}}
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/nodriver/core/connection.py", line 649, in listener_loop
event = cdp.util.parse_json_event(message)
File "/usr/local/lib/python3.10/dist-packages/nodriver/cdp/util.py", line 19, in parse_json_event
return _event_parsers[json["method"]].from_json(json["params"])
KeyError: 'DOM.scrollableFlagUpdated'
2024-11-06 20:33:44,260 [root] [INFO]: Screenshot saved to '1_after_challenge_check'
2024-11-06 20:33:44,610 [root] [INFO]: Screenshot saved to '2_no_challenge_found'
2024-11-06 20:33:44,610 [root] [INFO]: Challenge not detected!
2024-11-06 20:33:44,756 [root] [INFO]: Cookies got
2024-11-06 20:33:45,143 [root] [INFO]: Screenshot saved to '3_finish'
2024-11-06 20:33:45,143 [root] [INFO]: Solving finished
2024-11-06 20:33:45,143 [root] [INFO]: Close webdriver
2024-11-06 20:33:45,144 [nodriver.core.browser] [INFO]: terminated browser with pid 1057641 successfully
2024-11-06 20:33:45,144 [root] [INFO]: Solve result: <flare_bypasser.flare_bypasser.Response object at 0x7fab7f492ef0>
2024-11-06 20:34:07,910 [nodriver.core.browser] [INFO]: starting
executable :/bin/google-chrome
arguments:
--remote-allow-origins=*
--no-first-run
--no-service-autorun
--no-default-browser-check
--homepage=about:blank
--no-pings
--password-store=basic
--disable-infobars
--disable-breakpad
--disable-component-update
--disable-backgrounding-occluded-windows
--disable-renderer-backgrounding
--disable-background-networking
--disable-dev-shm-usage
--disable-features=IsolateOrigins,site-per-process
--disable-session-crashed-bubble
--disable-search-engine-choice-screen
--user-data-dir=/tmp/uc_bdcpv10b
--disable-features=IsolateOrigins,site-per-process
--disable-session-crashed-bubble
--proxy-server=string
--no-sandbox
--remote-debugging-host=<IP_ADDRESS>
--remote-debugging-port=47227
2024-11-06 20:34:08,668 [nodriver.core.browser] [INFO]: enabling autodiscover targets
2024-11-06 20:34:08,675 [root] [INFO]: New instance of webdriver has been created to perform the request (proxy=string), timeout=60.0
2024-11-06 20:34:08,946 [root] [INFO]: Close webdriver
2024-11-06 20:34:08,946 [root] [ERROR]: Error solving the challenge. On step 'navigate to url': [Errno 111] Connect call failed ('<IP_ADDRESS>', 47227)
Error solving the challenge. On step 'navigate to url': [Errno 111] Connect call failed ('<IP_ADDRESS>', 47227)
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 375, in _resolve_challenge_impl
await self.save_screenshot('evil_logic')
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 203, in save_screenshot
await self._driver.save_screenshot(screenshot_file_without_ext + ".png")
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/browser_wrapper.py", line 139, in save_screenshot
await self._page.save_screenshot(image_path)
File "/usr/local/lib/python3.10/dist-packages/nodriver/core/tab.py", line 1196, in save_screenshot
await self.sleep()  # update the target's url
File "/usr/local/lib/python3.10/dist-packages/nodriver/core/connection.py", line 317, in sleep
await self.update_target()
File "/usr/local/lib/python3.10/dist-packages/nodriver/core/connection.py", line 392, in update_target
target_info: cdp.target.TargetInfo = await self.send(
File "/usr/local/lib/python3.10/dist-packages/nodriver/core/connection.py", line 411, in send
await self.aopen()
File "/usr/local/lib/python3.10/dist-packages/nodriver/core/connection.py", line 285, in aopen
self.websocket = await websockets.connect(
File "/usr/local/lib/python3.10/dist-packages/websockets/legacy/client.py", line 654, in await_impl
_transport, protocol = await self._create_connection()
File "/usr/lib/python3.10/asyncio/base_events.py", line 1076, in create_connection
raise exceptions[0]
File "/usr/lib/python3.10/asyncio/base_events.py", line 1060, in create_connection
sock = await self._connect_sock(
File "/usr/lib/python3.10/asyncio/base_events.py", line 969, in _connect_sock
await self.sock_connect(sock, address)
File "/usr/lib/python3.10/asyncio/selector_events.py", line 501, in sock_connect
return await fut
File "/usr/lib/python3.10/asyncio/selector_events.py", line 541, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
ConnectionRefusedError: [Errno 111] Connect call failed ('<IP_ADDRESS>', 47227)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 251, in _resolve_challenge
return await self._resolve_challenge_impl(req, start_time)
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 423, in _resolve_challenge_impl
raise Solver.Exception(str(e), step=step)
flare_bypasser.flare_bypasser.Solver.Exception: [Errno 111] Connect call failed ('<IP_ADDRESS>', 47227)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypass_server.py", line 82, in process_solve_request
solve_response = await solver.solve(solve_request)
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 222, in solve
res = await asyncio.wait_for(self._resolve_challenge(req), timeout=req.max_timeout)
File "/usr/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
return fut.result()
File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 261, in _resolve_challenge
raise Solver.Exception(error_message, step=e.step)
flare_bypasser.flare_bypasser.Solver.Exception: Error solving the challenge. On step 'navigate to url': [Errno 111] Connect call failed ('<IP_ADDRESS>', 47227)

/usr/lib/python3.9/runpy.py:127: RuntimeWarning: 'flare_bypasser.flare_bypass_server' found in sys.modules after import of package 'flare_bypasser', but prior to execution of 'flare_bypasser.flare_bypass_server'; this may result in unpredictable behaviour
warn(RuntimeWarning(msg))
[2024-11-06 21:03:10 +0000] [1099566] [INFO] Starting gunicorn 23.0.0
[2024-11-06 21:03:10 +0000] [1099566] [INFO] Listening at: http://xxxxxxxxx:8000 (1099566)
[2024-11-06 21:03:10 +0000] [1099566] [INFO] Using worker: uvicorn.workers.UvicornWorker
[2024-11-06 21:03:10 +0000] [1099614] [INFO] Booting worker with pid: 1099614
[2024-11-06 21:03:10 +0000] [1099614] [INFO] Started server process [1099614]
[2024-11-06 21:03:10 +0000] [1099614] [INFO] Waiting for application startup.
[2024-11-06 21:03:10 +0000] [1099614] [INFO] Application startup complete.
module 'asyncio' has no attribute 'timeout'
Traceback (most recent call last):
File "/root/myenv/lib/python3.9/site-packages/flare_bypasser/flare_bypass_server.py", line 82, in process_solve_request
solve_response = await solver.solve(solve_request)
File "/root/myenv/lib/python3.9/site-packages/flare_bypasser/flare_bypasser.py", line 223, in solve
async with asyncio.timeout(req.max_timeout):
AttributeError: module 'asyncio' has no attribute 'timeout'
module 'asyncio' has no attribute 'timeout'
Traceback (most recent call last):
File "/root/myenv/lib/python3.9/site-packages/flare_bypasser/flare_bypass_server.py", line 82, in process_solve_request
solve_response = await solver.solve(solve_request)
File "/root/myenv/lib/python3.9/site-packages/flare_bypasser/flare_bypasser.py", line 223, in solve
async with asyncio.timeout(req.max_timeout):
AttributeError: module 'asyncio' has no attribute 'timeout'

Hi @madamesr1337 I fixed problem with python3.9 - you can try.
For debug Ubuntu-2204-jammy-amd64-base case I will add chrome running logs - it is in progress
Windows in progress too

{"status":"error","message":"Error: Error solving the challenge. On step 'solving': No module named 'fcntl'","startTimestamp":1730929679.638392,"endTimestamp":1730929679.641323
I managed to solve almost all the errors, including the async one, but I can't run it on Windows since it's only for Linux.

Can you provide "docker compose logs" or flare_bypass_server output (if you run without docker) ?

/usr/lib/python3.9/runpy.py:127: RuntimeWarning: 'flare_bypasser.flare_bypass_server' found in sys.modules after import of package 'flare_bypasser', but prior to execution of 'flare_bypasser.flare_bypass_server'; this may result in unpredictable behaviour warn(RuntimeWarning(msg)) [2024-11-06 21:03:10 +0000] [1099566] [INFO] Starting gunicorn 23.0.0 [2024-11-06 21:03:10 +0000] [1099566] [INFO] Listening at: http://xxxxxxxxx:8000 (1099566) [2024-11-06 21:03:10 +0000] [1099566] [INFO] Using worker: uvicorn.workers.UvicornWorker [2024-11-06 21:03:10 +0000] [1099614] [INFO] Booting worker with pid: 1099614 [2024-11-06 21:03:10 +0000] [1099614] [INFO] Started server process [1099614] [2024-11-06 21:03:10 +0000] [1099614] [INFO] Waiting for application startup. [2024-11-06 21:03:10 +0000] [1099614] [INFO] Application startup complete. module 'asyncio' has no attribute 'timeout' Traceback (most recent call last): File "/root/myenv/lib/python3.9/site-packages/flare_bypasser/flare_bypass_server.py", line 82, in process_solve_request solve_response = await solver.solve(solve_request) File "/root/myenv/lib/python3.9/site-packages/flare_bypasser/flare_bypasser.py", line 223, in solve async with asyncio.timeout(req.max_timeout): AttributeError: module 'asyncio' has no attribute 'timeout'
module 'asyncio' has no attribute 'timeout' Traceback (most recent call last): File "/root/myenv/lib/python3.9/site-packages/flare_bypasser/flare_bypass_server.py", line 82, in process_solve_request solve_response = await solver.solve(solve_request) File "/root/myenv/lib/python3.9/site-packages/flare_bypasser/flare_bypasser.py", line 223, in solve async with asyncio.timeout(req.max_timeout): AttributeError: module 'asyncio' has no attribute 'timeout'

I fixed problem with python3.9 - you can try.

root@Ubuntu-2204-jammy-amd64-base ~/flare-bypasser # flare_bypass_server -b xxxxxxxxx:8000 [2024-11-06 20:33:33 +0000] [1057586] [INFO] Starting gunicorn 23.0.0 [2024-11-06 20:33:33 +0000] [1057586] [INFO] Listening at: http://xxxxxxxxx:8000 (1057586) [2024-11-06 20:33:33 +0000] [1057586] [INFO] Using worker: uvicorn.workers.UvicornWorker [2024-11-06 20:33:33 +0000] [1057634] [INFO] Booting worker with pid: 1057634 [2024-11-06 20:33:33 +0000] [1057634] [INFO] Started server process [1057634] [2024-11-06 20:33:33 +0000] [1057634] [INFO] Waiting for application startup. [2024-11-06 20:33:33 +0000] [1057634] [INFO] Application startup complete. 2024-11-06 20:33:40,868 [nodriver.core.browser] [INFO]: starting executable :/bin/google-chrome
arguments: --remote-allow-origins=* --no-first-run --no-service-autorun --no-default-browser-check --homepage=about:blank --no-pings --password-store=basic --disable-infobars --disable-breakpad --disable-component-update --disable-backgrounding-occluded-windows --disable-renderer-backgrounding --disable-background-networking --disable-dev-shm-usage --disable-features=IsolateOrigins,site-per-process --disable-session-crashed-bubble --disable-search-engine-choice-screen --user-data-dir=/tmp/uc_oo6k6u3y --disable-features=IsolateOrigins,site-per-process --disable-session-crashed-bubble --proxy-server=string --no-sandbox --remote-debugging-host=<IP_ADDRESS> --remote-debugging-port=38719 2024-11-06 20:33:41,634 [nodriver.core.browser] [INFO]: enabling autodiscover targets 2024-11-06 20:33:41,647 [root] [INFO]: New instance of webdriver has been created to perform the request (proxy=string), timeout=60.0 2024-11-06 20:33:42,314 [root] [INFO]: Screenshot saved to '0_evil_logic' 2024-11-06 20:33:42,352 [uc.connection] [INFO]: KeyError: ('DOM.scrollableFlagUpdated',) during parsing of json from event : {'method': 'DOM.scrollableFlagUpdated', 'params': {'nodeId': 1, 'isScrollable': False}} Traceback (most recent call last): File "/usr/local/lib/python3.10/dist-packages/nodriver/core/connection.py", line 649, in listener_loop event = cdp.util.parse_json_event(message) File "/usr/local/lib/python3.10/dist-packages/nodriver/cdp/util.py", line 19, in parse_json_event return _event_parsers[json["method"]].from_json(json["params"]) KeyError: 'DOM.scrollableFlagUpdated' 2024-11-06 20:33:44,260 [root] [INFO]: Screenshot saved to '1_after_challenge_check' 2024-11-06 20:33:44,610 [root] [INFO]: Screenshot saved to '2_no_challenge_found' 2024-11-06 20:33:44,610 [root] [INFO]: Challenge not detected! 2024-11-06 20:33:44,756 [root] [INFO]: Cookies got 2024-11-06 20:33:45,143 [root] [INFO]: Screenshot saved to '3_finish' 2024-11-06 20:33:45,143 [root] [INFO]: Solving finished 2024-11-06 20:33:45,143 [root] [INFO]: Close webdriver 2024-11-06 20:33:45,144 [nodriver.core.browser] [INFO]: terminated browser with pid 1057641 successfully 2024-11-06 20:33:45,144 [root] [INFO]: Solve result: <flare_bypasser.flare_bypasser.Response object at 0x7fab7f492ef0> 2024-11-06 20:34:07,910 [nodriver.core.browser] [INFO]: starting executable :/bin/google-chrome
arguments: --remote-allow-origins=* --no-first-run --no-service-autorun --no-default-browser-check --homepage=about:blank --no-pings --password-store=basic --disable-infobars --disable-breakpad --disable-component-update --disable-backgrounding-occluded-windows --disable-renderer-backgrounding --disable-background-networking --disable-dev-shm-usage --disable-features=IsolateOrigins,site-per-process --disable-session-crashed-bubble --disable-search-engine-choice-screen --user-data-dir=/tmp/uc_bdcpv10b --disable-features=IsolateOrigins,site-per-process --disable-session-crashed-bubble --proxy-server=string --no-sandbox --remote-debugging-host=<IP_ADDRESS> --remote-debugging-port=47227 2024-11-06 20:34:08,668 [nodriver.core.browser] [INFO]: enabling autodiscover targets 2024-11-06 20:34:08,675 [root] [INFO]: New instance of webdriver has been created to perform the request (proxy=string), timeout=60.0 2024-11-06 20:34:08,946 [root] [INFO]: Close webdriver 2024-11-06 20:34:08,946 [root] [ERROR]: Error solving the challenge. On step 'navigate to url': [Errno 111] Connect call failed ('<IP_ADDRESS>', 47227) Error solving the challenge. On step 'navigate to url': [Errno 111] Connect call failed ('<IP_ADDRESS>', 47227) Traceback (most recent call last): File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 375, in _resolve_challenge_impl await self.save_screenshot('evil_logic') File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 203, in save_screenshot await self._driver.save_screenshot(screenshot_file_without_ext + ".png") File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/browser_wrapper.py", line 139, in save_screenshot await self._page.save_screenshot(image_path) File "/usr/local/lib/python3.10/dist-packages/nodriver/core/tab.py", line 1196, in save_screenshot await self.sleep() # update the target's url File "/usr/local/lib/python3.10/dist-packages/nodriver/core/connection.py", line 317, in sleep await self.update_target() File "/usr/local/lib/python3.10/dist-packages/nodriver/core/connection.py", line 392, in update_target target_info: cdp.target.TargetInfo = await self.send( File "/usr/local/lib/python3.10/dist-packages/nodriver/core/connection.py", line 411, in send await self.aopen() File "/usr/local/lib/python3.10/dist-packages/nodriver/core/connection.py", line 285, in aopen self.websocket = await websockets.connect( File "/usr/local/lib/python3.10/dist-packages/websockets/legacy/client.py", line 654, in await_impl _transport, protocol = await self._create_connection() File "/usr/lib/python3.10/asyncio/base_events.py", line 1076, in create_connection raise exceptions[0] File "/usr/lib/python3.10/asyncio/base_events.py", line 1060, in create_connection sock = await self._connect_sock( File "/usr/lib/python3.10/asyncio/base_events.py", line 969, in _connect_sock await self.sock_connect(sock, address) File "/usr/lib/python3.10/asyncio/selector_events.py", line 501, in sock_connect return await fut File "/usr/lib/python3.10/asyncio/selector_events.py", line 541, in _sock_connect_cb raise OSError(err, f'Connect call failed {address}') ConnectionRefusedError: [Errno 111] Connect call failed ('<IP_ADDRESS>', 47227)
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 251, in _resolve_challenge return await self._resolve_challenge_impl(req, start_time) File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 423, in _resolve_challenge_impl raise Solver.Exception(str(e), step=step) flare_bypasser.flare_bypasser.Solver.Exception: [Errno 111] Connect call failed ('<IP_ADDRESS>', 47227)
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypass_server.py", line 82, in process_solve_request solve_response = await solver.solve(solve_request) File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 222, in solve res = await asyncio.wait_for(self._resolve_challenge(req), timeout=req.max_timeout) File "/usr/lib/python3.10/asyncio/tasks.py", line 445, in wait_for return fut.result() File "/usr/local/lib/python3.10/dist-packages/flare_bypasser/flare_bypasser.py", line 261, in _resolve_challenge raise Solver.Exception(error_message, step=e.step) flare_bypasser.flare_bypasser.Solver.Exception: Error solving the challenge. On step 'navigate to url': [Errno 111] Connect call failed ('<IP_ADDRESS>', 47227)

Looks like problem with chrome start - I work on print chrome logs if its start failed

{"status":"error","message":"Error: Error solving the challenge. On step 'solving': No module named 'fcntl'","startTimestamp":1730929679.638392,"endTimestamp":1730929679.641323
I managed to solve almost all the errors, including the async one, but I can't run it on Windows since it's only for Linux.

Please, try latest version - fixed bug with xvfb usage on windows platform.

{ "status": "error", "message": "Error: Error solving the challenge. On step 'navigate to url': [Errno 111] Connect call failed ('<IP_ADDRESS>', 49607)", "startTimestamp":<PHONE_NUMBER>.737345, "endTimestamp":<PHONE_NUMBER>.775843 }
I also had errors like this on Linux. It didn't work at all.

For diagnostic this problem to exception added chrome process output, can you provide docker compose logs or flare_bypass_server command output (if you don't use docker)

Please, check last version (here much changes : windows support fix, arch support, py3.9 support fix), if some problem open issue. Thanks


Operation returned an invalid status code 'BadRequest'

Hi,
I am using the Power BI Actions extension with a Service principal. I keep running into the same message;
Operation returned an invalid status code 'BadRequest'
The service principal has all API deligated permissions for Power BI and is part of a secutiry group. The service principal and security group are both admin of the Power BI workspace. In the power BI admin portal access for service principals to use Power BI API's is allowed for the entire organization. in DevOps a service connection is created based on the Service Principal.
Please find attached the error and the yaml file. What am I doing wrong?

Does the app have delegated or application permissions?

Hi,
The app has all delegated permissions. No application permissions.
Op 6 feb. 2021 om 14:56 heeft Maik van der Gaag<EMAIL_ADDRESS>het volgende geschreven:

Does the app have delegated or application permissions?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/maikvandergaag/msft-extensions/issues/257#issuecomment-774481262, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AE7RQSJRWHR7EWPUAZJO5N3S5VDBBANCNFSM4XGHSVGA.

Could you try application permissions. The extension uses the application for the security.

Hi,
I have granted Access consent to both application permissions in the App. Unfortunately I still have the same error.
<EMAIL_ADDRESS>

Oké, could you share the log files of the run with the system.debug variable with the value true added to the pipeline?

Hi,
Can you see the attached zip file with the logs?

No I don't see them

logs_661.zip
This is log file.

I posted the zip file via GitHub.
Op 6 feb. 2021 om 21:07 heeft Maik van der Gaag<EMAIL_ADDRESS>het volgende geschreven:

No I don't see them
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/maikvandergaag/msft-extensions/issues/257#issuecomment-774535782, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AE7RQSNL4SWCLP2TLMAVOEDS5WOQVANCNFSM4XGHSVGA.

This is the log file:
logs_661.zip

@mcharing: Is the workspace created by hand or by the extension. Could you try letting the extension make the workspace?

Hi,
The workspace was created by hand.
I run a new pipeline letting the extension make te workspace. The workspace is created and visible in Power BI Service. The Service Principal is the Admin of the workspace. Unfortunatly, the same BadRequest message comes up.
See log file:
logs_665.zip

@mcharing: Are you able to share the report? Or could you try an empty one?

Do you mean; share the report with you?
And what do mean with an empty one? A template?
Op 9 feb. 2021 om 16:42 heeft Maik van der Gaag<EMAIL_ADDRESS>het volgende geschreven:

@mcharinghttps://github.com/mcharing: Are you able to share the report? Or could you try an empty one?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/maikvandergaag/msft-extensions/issues/257#issuecomment-776033202, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AE7RQSOYQ3KXIIM6OWVMESDS6FJWFANCNFSM4XGHSVGA.

BTW I really appreciatie your effort!
Can it be a problem that my Power BI is North Europe while most of my resources are in West Europe?
Op 9 feb. 2021 om 16:42 heeft Maik van der Gaag<EMAIL_ADDRESS>het volgende geschreven:

@mcharinghttps://github.com/mcharing: Are you able to share the report? Or could you try an empty one?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/maikvandergaag/msft-extensions/issues/257#issuecomment-776033202, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AE7RQSOYQ3KXIIM6OWVMESDS6FJWFANCNFSM4XGHSVGA.

@mcharing: I meant if it would be possible to share the report that you are trying to import with me. This way I could check your scenario completly.
Besides that I would suggest to try to import a normal/empty pbix file to see if that works. This way you can check if it ins't something in the report that is causing the problem. Because there are some small restrictions on importing reports.
I think the location should not have an impact

Hi,
I create an new,empty report: test.pbix and changed the yaml to only publish the test.pbix. This raised the same error.
See attached the original report that I wanted to publish;
Sales.zip

Will check tomorrow if I can find time to publish the report

@mcharing: Checked today, I was able to deploy the report with the same version. I think you need to check the connection and see if the permissions are correctly applied.
you can maybe use the below link of someone who wrote an article about it.
https://gtrekter.medium.com/automate-you-power-bi-reports-deployment-using-azure-devops-5ada8915d401
Main thing I would try is to reconfigure the SP and Service Connection.

Hi,
I have set up a new DevOps project and a new SP. It works now! Thanks for the help!

Great !! Do you have any pointers what the issue was?

@mcharing , I'm having the same issue as you did. Any clue what might have been wrong with your initial service principal? Thx

I have never encountered this issue. Hope to get a clue sometime what goes wrong. I had several other people that had the same issue.

This is the log output, maybe it gives some insight?
021-02-24T15:44:04.9842845Z Starting Power BI Actions extension
2021-02-24T15:44:05.0320170Z ### Required Module is needed. Importing now...
2021-02-24T15:44:05.3412025Z ### Trying to import the incorporated module for PowerBI
2021-02-24T15:44:05.5571785Z ##[warning]The names of some imported commands from the module 'PowerBi' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2021-02-24T15:44:07.0147349Z Getting Power BI Workspace properties; mypowerbiworkspace
2021-02-24T15:44:08.5088519Z Trying to publish PowerBI File: D:\a_temp\PowerBIBuild\reports\Leads_insights.pbix
2021-02-24T15:44:08.5168183Z Checking for existing Reports with the name: Leads_insights
2021-02-24T15:44:09.1127624Z Done processing Power BI Actions
2021-02-24T15:44:09.4278271Z ##[error]Operation returned an invalid status code 'BadRequest'
2021-02-24T15:44:09.5029717Z ##[section]Finishing: Power BI Action: Publish

No clue yet. Setting up a new DevOps GIT project with a new Repo did the trick.
When a tried to copy a good working pipeline from the new repo to my old repo I again got the 'BadRequest' message so I deciced to just live with two projects instead of one.

Ok, I will investigate this further on my end and will close the issue for now.

I had the same issue. It was because my git repo has LFS enabled. I fixed the build pipeline to enable git LFS when checking out the power bi files. The release pipeline works.
trigger:
- main
pool:
  vmImage: 'windows-latest'

steps:
- checkout: self
  lfs: true
  clean: true

- task: PublishPipelineArtifact@1
  inputs:
    targetPath: '$(Pipeline.Workspace)'
    artifact: 'Reports'
    publishLocation: 'pipeline'

Thanks that certainly could have caused the issue

I am facing a similar issue. Even adding the lfs: true did not help. Is there any other factor causing this error?
2021-07-06T09:39:47.3339133Z ##[section]Starting: Power BI Action: Publish Report
2021-07-06T09:39:47.3472536Z ==============================================================================
2021-07-06T09:39:47.3472864Z Task         : Power BI Actions
2021-07-06T09:39:47.3473120Z Description  : Release Task Power BI Actions
2021-07-06T09:39:47.3473377Z Version      : 5.3.32
2021-07-06T09:39:47.3473596Z Author       :
2021-07-06T09:39:47.3473842Z Help         :
2021-07-06T09:39:47.3474104Z ==============================================================================
2021-07-06T09:39:49.9232274Z Starting Power BI Actions extension
2021-07-06T09:39:49.9313003Z ### Required Module is needed. Importing now...
2021-07-06T09:39:50.0411094Z ### Trying to import the incorporated module for PowerBI
2021-07-06T09:39:50.1710473Z ##[warning]The names of some imported commands from the module 'PowerBi' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2021-07-06T09:39:50.7572643Z Getting Power BI Workspace properties; PBIWORKSPACE
2021-07-06T09:39:51.6469201Z Trying to publish PowerBI File: D:\a\m\pbifile.pbix
2021-07-06T09:39:51.6494768Z Checking for existing Reports with the name: sample report
2021-07-06T09:39:52.7730919Z Done processing Power BI Actions
2021-07-06T09:39:52.9027175Z ##[error]Operation returned an invalid status code 'BadRequest'
2021-07-06T09:39:52.9608318Z ##[section]Finishing: Power BI Action: Publish Report


Implement multiple sprites

Requirement: As a user of the Codagotchi extension, I would like the ability to collect multiple creatures, so that I can do even more with Codagotchi as I code.

sprites have been designed by Forrest -- just need to be added in separate spritesheets


Add Laravel 6 support

Adds support for Laravel 6.0.
Thanks

Thanks @vblinden.
#50 addresses this, in full scope. Going with that one.


Incentivize ASP behavior in OOR Payments with double-spend prevention bond on the Liquid Network

Steven Roose proposed a very clever construction to prevent double-spends on Bitcoin network by having the "sender" to lock funds in a special bond contract on the Liquid Network. This allows anyone to burn those funds if the sender is caught double-spending the Bitcoin transaction.

A Bitcoin user who wants to make his Bitcoin transactions trust-worthy before confirmation would just need to tie money up in a "bond" UTXO on Liquid, which could be burned if a double spend from their Bitcoin public key were discovered.

In the context of Ark we could apply this approach to make Out-of-round Payments more trustworthy, having the ASP to lock a percentage of fees over-time or una tantum  big chunk of funds on the Liquid Network. If anytime the key used the ASP to double-spend the OOR VTXO goes onchain, can prove the involvement of the ASP and directly cause monetary damage to the ASP funds that would never be recoverable.
This dynamic is very interesting and can be structured similarly to insurance funds of derivative exchanges, where an over-time percentage of fees are held in a dedicated fund. The beauty of this is that anyone can trigger the burn, and the funds are managed programmatically by a covenant on the Liquid Network.
Problems/Caveats

The Liquid federation and the functionaries can decide to "de-peg" L-BTC in case a bond burn is executed. This is unlikely, as it would mean the death of the Liquid Network to give back money to an external party. The problem can be more serious if the majority of Liquid functionaries is also a "federated ASP", then thety could pull this off.
The contract could be replicated in any other chain (either UTXO or EVM based) if the Liquid Network decentralization is not enough: the ASP can have multiple bonds contract on multiple chains, lowering the risks considerably.
Instead of L-BTC (which is an IOU of real BTC held in the federated wallet) the ASP can use USDT, if the issuance/redemption is more trustworthy.

Does this mean increasing (doubling) the liquidity requirement of the ASP?

Well that bond can be funded overtime with a small cut from every round. Overtime it will grow to be so big that it doesn’t not need this “bond tax”
And with OOR you don’t have liquidity requirement as you can spend OOR for another new OOR, never joining a round (hence locking onchain liquidity)
Consider you DO NOT need a 1 to 1 relationship between one VTXO and one bond contract. The bond can be burnt with any double spend ever, just validates the known ASP public key did that.

This is REALLY interesting.

Some adjacent work https://x.com/btcanary55082/status/1821521712938197110?s=46


OLS-1009 bugfix: add label openshift.io/user-monitoring: false to ServiceMonitors

Description
Fix the bug that PrometheusOperatorRejectedResources alert is trigger if the namespace openshift-lightspeed does not have the label openshift.io/cluster-monitoring: true .
We add the label openshift.io/user-monitoring: false to ServiceMonitor so that the prometheus operator of User Workload Monitoring stack will not process these ServiceMonitors.
Type of change

[ ] Refactor
[ ] New feature
[x] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue # OLS-1009
Closes #

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

/test bundle-e2e-4-16

/lgtm
/approve

/override "Red Hat Konflux / ols-ui-tests-416 / test-bundle"
/override "Red Hat Konflux / ols-enterprise-contract / test-bundle"
/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-operator"
/override "Red Hat Konflux / ols-enterprise-contract / bundle"


[stable/falco] Add affinity to falco chart

Signed-off-by: cw-sakamoto<EMAIL_ADDRESS>What this PR does / why we need it:

We need to use affinity(not nodeSelector) in falco

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

Thanks for good the product maintenance.
/assign @nestorsalceda

@aixeshunter Thanks approve!
If you have permission, please also send /lgtm..
https://github.com/helm/charts/pull/17841

@aixeshunter
@nestorsalceda
@bencer
Can anyone please do /lgtm ... ?

/ok-to-test

/assign
/lgtm


Laracon 2024

Hey @taylorotwell, thanks for such a fantastic Laracon! The Concurrency stuff has been a huge feature I'm most excited for, so I gave it a go using your PR to tinker.
I'm not sure if intentional, but the php binary at https://github.com/laravel/framework/blob/laracon-2024/src/Illuminate/Concurrency/ProcessDriver.php#L31 is never found when using Laravel Herd.
I presume it's intended that we only use sync during local dev, and process for production? I understand this is still a draft, but if release is tomorrow I wanted to point out.
Thanks a ton for this regardless :)

@taylorotwell the PHP binary should definitely be configurable, we have a development server where you switch PHP per project basis and the global PHP is not the one that is used for the project and accessed via php8.2 artisan etc.. Maybe introduce a config and env variable?

I wonder if Octane would have its own concurrency driver since Swoole/OpenSwoole have a feature called "task workers".

@taylorotwell

Also, you forgot to add the documentation blocks for the Competition facade.

I'm trying to call Concurrency::run but got:
Illuminate\Contracts\Container\BindingResolutionException
Unresolvable dependency resolving [Parameter #0 [ <required> $app ]] in class Illuminate\Support\MultipleInstanceManager

Also it seems like defer uses sync driver.
How to configure this facade?

Please open an issue if you have found a problem. Comments in already merged PRs are mostly not looked after. You can also send in a PR to fix the problem directly.

I'm not sure if this is a issue. Maybe I'm just doing something wrong.

defer has a different feature set than dispatching jobs after the response, such as cancelling on bad status codes or always running.
defer is not tied to the queuing system. This means that models are not serialized / re-queried, reducing potential database queries and when captured models are deleted within the request the closure will still run.
If you love job classes and those tradeoffs mean jobs are the best answer for you, go for it.


gha: explicit branch and trigger in ariane-scheduled workflow

Let's use explicit bash variables to construct the trigger phrase, instead of directly using the matrix value.

Reviews are in. Marking as ready to merge, as full CI is not required.


Please add LICENSE file

It appears excalidraw is under a MIT license (https://github.com/excalidraw/excalidraw/blob/master/LICENSE), however excalidraw-vscode does not specify a license. Adding a license will allow users to determine what their rights are with respect to the software, and allow them to ensure they are meeting the developer's wishes regarding appropriate use.

There is a LICENSE in the extension directory: https://github.com/excalidraw/excalidraw-vscode/blob/master/extension/LICENSE
I don't know if it is necessary to also add it in the top level directory ?

To be honest I didn't notice it in the extension directory (thanks for the comment) but I think others may not as well.
I do think adding it at the top level will make it more visible, and may work with systems that expect to see it there (for example, I think GitHub expects it at the top level to assign a license to the repository for searches, in the about page, etc.)
Thank you for your work on this fantastic project! I find it incredibly useful, and with integration to vscode it is even better!


Better Documentation

I think lack of documentation is a huge road block for Diesel adoption.
Each time I try to get started with Diesel, I have to struggle hard to not drop it and just use one of the raw database libraries.
The guide is VERY basic, and the source docs don't offer much either.
I would imagine I'm not the only one suffering from such frustration.
As a positive example that could be emulated, I think Rocket has managed a very decent, well structured guide that makes it easy to get started with and use.

Yep!
Any concrete ideas what the documentation needs to cover that is currently missing? We want to add more guides (there is one PR to add a guide on updates), and any indicator what is needed the most would be helpful. :)

Off the top of my head, here is a raw structure for a guide.
You have probably put more thought into it, but I think this would be nice:

Quickstart:
A short single file (main.rs) example that shows how to create a migration, create a schema with table!, get a connection, insert and query some data.
Concise, just get you something running quickly.
Separate version for each backend would be nice.

Concepts

Schema: explain schema and DSL, and different ways to get one (infer, table! macro)
Models: explain the traits (Queryable, Insertable, identifiable) and how they are used + how deriving works
Migrations
Adapters (postgres, mysql, sqlite)

Queries

DSL:

basic insert/update/delete, arguments
querybuilder
Complex Queries (joins, ...)

With Models
Associations

Adapters
Documentation for setup and custom features for each database

Postgres
MySQL
Sqlite

Advanced

Custom Types (related traits, how to implement)
Handling Migrations (embed in binary, etc)
...

I'd also recommend not just writing more guides.
Especially with a ORM, having something like a reference where you can quickly look up how to do certain things is very valuable.
I'm not in love with how https://github.com/azerupi/mdBook looks, but it's good enough for Rust, so using that might be an option, and certainly less work than building something custom.

To add my two cents:
The single biggest thing that'd make Diesel easier to learn is to add way more query exmaples. Basic SELECT, INSERT, DELETE, and UPDATE queries are covered already, but anything for anything non-trivial I found it much easier to look at Diesel's tests than to look at the API docs.
In particular:

How do you use GROUP BYs? I can do simple things, but resorted to dropping to raw SQL because I couldn't figure out how to do a GROUP BY ___ HAVING filter.
I still have no clue how to do a JOIN with Diesel
I'm not sure there actually is a guide to dropping down to raw SQL -- I just kind of copy-pastad other code that seemed to work.
On a smaller note, I wasted a lot of time trying to finding ne_any. - A table of operators to functions (or even juts a a link to http://docs.diesel.rs/diesel/expression/expression_methods/global_expression_methods/trait.ExpressionMethods.html) would have saved a lot of time

Oh and also... I'm not sure how feasible this is, but I'd love a guide on how to read Diesel's compilation errors. They get pretty nasty, and sometimes I honestly have no clue how to use them to figure out what's wrong.

To suuport what @alanhdu said, i think the Queries section in my outline is by far the most important.

One think that I miss, is a list of all possible items. Like possible annotations for models in the struct. Sometimes, just a list of all the items helps as an index to see the possibilities.
Is not to make the information more easy to read, is to have a entry point to see all the information.
Now I'm searching if there is any annotation for telling diesel that ignore one field of the struct. I'm searching in the issues, in google, in the docs, but I don't find any place with all the possible functions, macros, annotations, etc of Diesel. In other frameworks I can read the full documentation in case of not finding the answer, here... there is no "all documentation".

Perhaps it might make sense to create a new repo specifically for the diesel.rs homepage? At the very least the existing guide could be expanded.

The repo homepage is sgrif/diesel.rs-website

Just as a heads up to others, @hobofan said he'd like to start a query builder guide, and @notryanb want to document model derives/traits.

Update - I'm currently working on updating the Associations docs for v1.0 and a separate guide for Joins.

I'd love to see more docs too - especially for sqlite.  This is my first try at Diesel with Sqlite3.  Most of the examples I find are for PG and unfortunately we don't have that option atm.  The examples on the repo for sqlite are extremely basic.  I managed to get my inserts and updates working but a basic select query is generating a ton of compiler errors that are hard to understand.  I can't imagine what a join requires.
I'd be happy to lend a hand if needed (even though I'm still a Rust noob at this point).  Thanks!

Once all open doc PRs today are merged, we will be able to add #![deny(missing_docs)] to the repo. #1407 (hopefully) addresses the "I don't know where to find things" issue (please comment on that PR with your feedback though). I've reviewed every single piece of documentation in the library over the past few weeks to make sure it's up to date (I likely missed a module somewhere, please open an issue if you find anything that is out of date or poorly documented). I'm hoping to publish ~10 more guides before the end of the year.
I realize not everything is documented as perfectly as it could be. If you have any concrete places where the documentation could be improved (even if it's just "I couldn't find/figure out X, here's where I looked") please open an issue.
However, I think we have sufficiently resolved the issue of "our docs generally suck" enough to close this.

i have readed the document. but i still dont know how to use "use schema::posts::dsl::*". diesel created these models or i have to write by myself?  i really dont know how to do it.


Add Integration test for the GraphQLQueryAnalysis

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This PR has removed tests-backend/src/test/resources/artifacts/AS/ghost/APIStatusMonitor.war. Please add it back


Allow user to override the view model activation when deserializing

I.e. give the user the ID saved in the layout and let the user decide how to activate the instance of that class.

This will probably be need for loading Documents that relate to user files?

@danwalmsley Was the https://github.com/wieslawsoltes/Dock/pull/38 part of this?

No, this is like say you want to open a document, yoir id moght need to contain some. Custome string so thw file can opened, not just ns. Type. DocumentViewModel


bug: fails with a remote S3 host

OS: Ubuntu 22.04.3
Minio:  docker RELEASE.2023-09-20T22-49-55Z
Description: I wanna serve a static file from a minio bucket called buck-website. I use Caddy with your plugin to serve a static index.html on both local host and remote host. I place the same index.html file in the root of buck-website bucket on both local and remote host.
Issue: Localhost works fine, remote host returns 404 - not found:
# Local works
curl  localhost:7000
Hello world!

# Remote - 404
curl localhost:7001 - returns 404

Caddy logs:
2023/10/07 13:09:25.942 DEBUG   http.handlers.file_server       sanitized path join     {"site_root": ".", "request_path": "/", "result": "."}
2023/10/07 13:09:32.110 DEBUG   http.handlers.file_server       no index file in directory      {"path": ".", "index_filenames": ["index.html", "index.txt"]}
2023/10/07 13:09:32.110 DEBUG   http.log.error  {id=wwhe1qrpa} fileserver.(*FileServer).notFound (staticfiles.go:629): HTTP 404 {"request": {"remote_ip": "<IP_ADDRESS>", "remote_port": "42206", "client_ip": "<IP_ADDRESS>", "proto": "HTTP/1.1", "method": "GET", "host": "localhost:7001", "uri": "/", "headers": {"User-Agent": ["curl/7.81.0"], "Accept": ["*/*"]}}, "duration": 6.167626911, "status": 404, "err_id": "wwhe1qrpa", "err_trace": "fileserver.(*FileServer).notFound (staticfiles.go:629)"}

Config:

Minio host: s3

index.html: hello world!

Check S3 port:

nc -zv s3 9000
Connection to s3 (xxx.xxx.xxx.xxx) 9000 port [tcp/*] succeeded!

Do you run both MinIO and Caddy in Docker?

I run minio in docker on both local and remote. Caddy is built from the latest source, including your plugin

Upd: If I add a pass_thru directive, caddy returns 200, but fails to find index.html. NGINX is able to serve the static website in that bucket
:7001 {
	file_server {
		fs s3 {
			endpoint "http://s3:9000"
			region "us-east-0"
			bucket "buck-website"
			force_path_style
		}
		pass_thru
	}
}

2023/10/07 20:09:34.923 INFO    serving initial configuration
2023/10/07 20:09:37.333 DEBUG   http.handlers.file_server       sanitized path join     {"site_root": ".", "request_path": "/", "result": "."}
2023/10/07 20:09:37.421 DEBUG   http.handlers.file_server       no index file in directory      {"path": ".", "index_filenames": ["index.html", "index.txt"]}

@tetra12 I'm not 100% sure what "remote" means in this case.
http://s3:9000 suggests you are trying to access a MinIO instance running in a container using DNS, but if Caddy doesn't run in a container, in the same network, etc. that's not going to work.
Can you create a reproducible environment to demonstrate the problem?
(Side note: I suspect at this point that the problem is not related to this library as it's merely a wrapper around AWS lib and io/fs)

I mean what I say. I personally use a fresh VPS instance, running minio docker and having a static IP. You can reproduce the issue with your own cloud or VPS instance. I provided enough info to reproduce

This issue is invalid. My bad. I had an issue with valid S3 credentials. Closing as invalid


arrow.get() with two strings should support an optional tzinfo

It would be great when you have a time stamp if could specify which tz it is in, even if the ts itself does not contain the information, such as local vs always forcing utc:
For instance something like this:
arrow.get('2014/02/05 09:23:44', 'YYYY/MM/DD HH:mm:ss', tzinfo=tz.tzlocal())

where the get factory would support something like:
        **Three** arguments, both ``str``, to parse the first according to the format of the second and the third is an optional tzinfo, defaulting to UTC::

:+1:
I agree. I had the same problem and it took me more time than I anticipated to find another "trick" to workaround this:
arrow.get(arrow.get('2014/02/05 09:23:44', 'YYYY/MM/DD HH:mm:ss').datetime, 'local')

which is uglier than the solution of @pombredanne , so I'll happily change it to his one

Will add this to the Wiki


build_and_push: detect fedora tag from Dockerfile

Detect automatically fedora tag from Dockerfile in build_and_push_action.
The goal is to automatically detect change between Fedora version, e.g.,
35->36.
The only place, from where version transition can be spotted is
Dockerfile.fedora.
The used tag has to be in format "36".
curl for getting the Dockerfile.fedora was used because we do not have
repository cloned at that point in the action.
Cloning the whole repository because of one Dockerfile would be ineffective.
Should fix https://github.com/sclorg/build-and-push-action/issues/14.

Otherwise LGTM.


Add support to directly provide crypto:PrivateKey and crypto:PublicKey in JWT signature configurations

Description:

$subject

Related to: #675

Proposal has been added here [1]
[1] - https://github.com/ballerina-platform/ballerina-library/issues/6515

Reopening this issue as we have reverted the change with this [1]
[1] - https://github.com/ballerina-platform/ballerina-library/issues/6628


Default Rest Version must be updated in Storage Datalake Service

For Datalake Storage, in the service side the default value for xMsVersion (rest version/x-ms-version header) is set to a old value which does not support OAUTH. Since this field is only optional, the customer requests are failing. Please update the default rest version

Any update on this?

This seems to be fixed with the latest regeneration. CLosing this issue


Color filter layer does not support raster cache

It seems that color filter layer still does not support raster cache, which may be affect performance.

/cc @flar @goderbauer

Is there an example of how and where this might be costing us some performance?

Is there an example of how and where this might be costing us some performance?

We have some businesses use ColorFilter and BackdropFilter in a ListView item usually, something like https://github.com/flutter/flutter/pull/99542. If the item is complex, it sometimes drops frames while scrolling.


Use basespace CLI to download run data

This PR replaces the old python script for downloading data from the Illumina BaseSpace Sequence Hub.
Resolves #8

The old method of downloading data created a directory within the run directory, which is different than this current method. We need to ensure that we can still demux the data. This may involve changing the demux scripts with the updated directory structure. The contents of the directories are the same.
New download app:
$ tree new_method -L 1
new_method
├── <run_id>.json
├── Config
├── Data
├── InstrumentAnalyticsLogs
├── InterOp
├── Logs
├── Recipe
├── RTAComplete.txt
├── RTAConfiguration.xml
├── RTALogs
├── RTARead1Complete.txt
├── RTARead2Complete.txt
├── RTARead3Complete.txt
├── RTARead4Complete.txt
├── RunCompletionStatus.xml
├── RunInfo.xml
├── RunParameters.xml
└── SampleSheet.csv

7 directories, 11 files

Old download app:
$ tree old_method -L 2
old_method
├──<run_id>
│   ├── Config
│   ├── Data
│   ├── InstrumentAnalyticsLogs
│   ├── InterOp
│   ├── Logs
│   ├── Recipe
│   ├── RTAComplete.txt
│   ├── RTAConfiguration.xml
│   ├── RTALogs
│   ├── RTARead1Complete.txt
│   ├── RTARead2Complete.txt
│   ├── RTARead3Complete.txt
│   ├── RTARead4Complete.txt
│   ├── RunCompletionStatus.xml
│   ├── RunInfo.xml
│   ├── RunParameters.xml
│   └── SampleSheet.csv
└── nohup.out

8 directories, 11 files

After some more investigation, this does not cause any issues with the demux app. Now instead of running the following:
singularity run \
  -B $resource_dir:/opt/resources -B $run_dir:/opt/analysis -B $bcl_dir:/opt/data \
  miptools.sif --app demux -s $sample_list -p $platform

where $run_dir is the directory of the project and bcl_dir=$run_dir"_<run id>", we must change $bcl_dir. We can just replace it with $run_dir as this is where the files from BaseSpace are now held:
singularity run \
  -B $resource_dir:/opt/resources -B $run_dir:/opt/analysis -B $run_dir:/opt/data \
  miptools.sif --app demux -s $sample_list -p $platform

We will get the same output. We may additionally want to consider slightly changing the demux script so that we no longer need to bind $run_dir to both /opt/analysis and /opt/data.


Add alternative dialogs/modals for confirm and onbeforeunload

I compiled qboard to true native applications using electron (#74) but since electron doesn't support alerts, all non-safe operations like overwriting and closing the app are blocked.

Save to JSON and PDF also fail; electron apps require manually invoking their download command

Out of scope in my view. Consider proposing the electron app as its own issue. It is not entirely trivial to port it to electron; some components like these need a different implementation.


Adobe Tags or Tags in Adobe Experience Platform ?

Issue in ./help/destinations/catalog/personalization/custom-personalization.md
This page mentions "Adobe Tags" but i think the name is "Tags in Adobe Experience Platform" as per the tags documentation

Thank you for submitting this issue. We will review the documentation and make the necessary updates as quickly as possible. Tracking internally in PLAT-114793.

We've updated the Tags naming and will close this issue. Thanks again for raising this!


Fixing broken UI library playground link

Fixing broken UI library playground link with a correct chromatic link.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/design/design-teams-app-ui-templates.md
89
10
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 18cf8e2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/design/design-teams-app-ui-templates.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/design/design-teams-app-ui-templates.md
89
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit bac00ac:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/design/design-teams-app-ui-templates.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/design/design-teams-app-ui-templates.md
89
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit b51ee1b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/design/design-teams-app-ui-templates.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Ignore some symbol table entries

Skip symbol table entries which have no name, or which aren't
NOTYPE. This gets rid of SECTION type symbols and re-enforces
an invariant which most of the code makes.
Without this, some programs get the wrong names when loaded
from an ELF with debug symbols.

Codecov Report

Merging #77 into master will decrease coverage by 0.13%.
The diff coverage is 0%.

@@           Coverage Diff            @@
##           master    #77      +/-   ##
========================================
- Coverage   56.14%    56%   -0.14%
========================================
  Files          22     22
  Lines        1710   1714       +4
========================================
  Hits          960    960
- Misses        594    596       +2
- Partials      156    158       +2

Impacted Files
Coverage Δ

elf.go
58.96% <0%> (-1.14%)
:arrow_down:

Continue to review full report at Codecov.

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


Compiled againt a different Node.js version error on loading

I have node version v.14.4.0, i installed last version of homebridge UI X. I have raspberry pi running Raspbian OS. When i try use Homebridge GUI (plugins tab) to search for broadlink-rm plugin (this repo), then clicked install. It execute sudo -E -n npm install homebridge-broadlink-rm@latest, then it install normally..
After that i restart homebridge to load plugin, then i got this error when it start.
[16/06/2020, 02:27:50] ERROR LOADING PLUGIN homebridge-broadlink-rm:
[16/06/2020, 02:27:50] Error: The module '/usr/local/lib/node_modules/hap-nodejs/node_modules/mdns/build/Release/dns_sd_bindings.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 83. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1250:18)
    at Module.load (internal/modules/cjs/loader.js:1049:32)
    at Function.Module._load (internal/modules/cjs/loader.js:937:14)
    at Module.require (internal/modules/cjs/loader.js:1089:19)
    at require (internal/modules/cjs/helpers.js:73:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/hap-nodejs/node_modules/mdns/lib/dns_sd.js:24:20)
    at Module._compile (internal/modules/cjs/loader.js:1200:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1220:10)
    at Module.load (internal/modules/cjs/loader.js:1049:32)
    at Function.Module._load (internal/modules/cjs/loader.js:937:14)

So homebridge broadlink plugin isnt working..
There is solution?

It's possible you have multiple versions of Node.js installed causing strange things to happen.
https://github.com/homebridge/homebridge/wiki/How-To-Fix-Node.js-Install-Issues-On-Linux


feat: checked, green text

What's changed:

frontend/components/tasks/toolbar/ToolbarArticle.vue: added title to enable user to view the text info on hover, added green text styling on isConfirmed = true status

This PR is made by following the discussion in the previous PR https://github.com/CLARIN-PL/doccano/pull/23 about green text feature.
Screenshots:

Thank you for the neat work! :) I think everything looks fine, I just have a few suggestions:

I really like that you put the article progress bar at the bottom of the viewer along with text count for the article. But since now we have "x of y texts" at the top and "x/y texts" at the bottom, maybe we can make it a bit more explicit by writing "Annotating x / y texts of the current article" at the bottom? Just for clarity's sake. XD
I personally prefer the article progress bar at the bottom with the previous color (blue) just to distinguish it from the whole progress bar on the right which is green XD

What do you think? Nevertheless I give my approval now XD

I personally think that the green texts will clash with the blue color, but if thats what you see fit, I will update the PR XD
Also this is just my personal preference, but I think you can use the feature 'request changes' instead, unless this change is not necessarily needed.  XD

I personally think that the green texts will clash with the blue color, but if thats what you see fit, I will update the PR XD Also this is just my personal preference, but I think you can use the feature 'request changes' instead, unless this change is not necessarily needed. XD

Yeah, I thought these suggestions are rather minor, that's why I didn't use the request change XD Anyway, I think it looks fine now, so you can update the PR and merge it. Perhaps on Monday on the meeting the others will have other suggestions 😅

Alright then, I will merge this. Thank you for the discussion, and we will see what the others have to say about this on Monday. XD


Drop HHVM support

Like most PHP packages, let's drop HHVM support in v2.0. v1.1 will continue to support it, but will only receive bug fixes.

I think its already removed as per this commit for v1.1: cf15dd9857649ca65976ceebb360fe105328cbd6

Yeah, this is mostly to remove leftovers.

Fixed in #654.


Docs - Fomik React Material-UI example missing onBlur for touched

Bug report
Current Behavior
On the docs https://formik.org/docs/examples/with-material-ui
the example is missing a very important prop to be passed into the TextField component
onBlur={formik.handleBlur}
This is needed to show errors when the user has clicked away from the TextField. Otherwise the errors wont show until you click submit. But in a lot of use cases, you want the submit button to be disabled until the form is valid.
Expected behavior
Add onBlur={formik.handleBlur}
I think this is straight-forward. let me know if you need actual examples to try this. i figure you can just add this prop to the editor at https://formik.org/docs/examples/with-material-ui  and try it there.

Because the editor is a linked codesandbox, what I think needs to happen is for the codesandbox itself to be edited. Do you know what the procedure for that is? Here is the sandbox in question:
https://codesandbox.io/embed/github/formik/formik/tree/master/examples/with-material-ui?fontsize=14&hidenavigation=1&theme=dark

not stale. this  should be a simple fix if we know where to do the change


[8.x] Add Transliterate shortcut to the Str helper

Description
Add a transliterate shortcut to the String helper.
I've added the by recommendation on a recent PR around fixing security exploit in the UI package.
In short, MYSQL and other DB hosts will transliterate special characters in queries, making it possible to bypass security checks and throttles.
In the case of the UI security exploit, by default, Laravel throttles login attempts by the applications email/username. However, if I use special characters to replace standard characters in my email when the email gets to the Database, the query parameters will transliterate. This means that<EMAIL_ADDRESS>will be read as<EMAIL_ADDRESS>by the Database. This made it was possible for a user to brute force a password by bypassing the login throttle.
Adding this shortcut will make it easier to implement a more elegant solution to the current UI fix while also making it easier for users to improve the security of their application or similar functionality by adding transliteration directly from the helper without needing prior knowledge of the ASCII package.

Some email addresses could genuinely have UTF-8 characters in them though, right? Or is that not allowed? 😅

Some email addresses could genuinely have UTF-8 characters in them though, right? Or is that not allowed? 😅

Currently, the only allowed special characters are ~!$%^&*_=+}{'?-. however for the exploit it doesn't really matter as that email is just generating a key to store against. So thankfully if emoji emails do become a thing, that fix will still hold up... Mostly 😛


custom wx_unit validation behavior

it might be convenient to define wx_unit behavior for tags beside quantity
Some ideas:

number and ndarray should validate like dimensionless ""
objects without a unit property could validate like dimensionless by default
validate timedelta against "s"

we should take a similar approach here to #86 (whatever that turns out to be in the end)


[New] Community Resource Submission

Please submit this issue only if YOU are the owner (or co-owner) of the associated resource - or have clear permission to share that with us from the owner. We will only use the resource title, description and link to redirect our readers to that article. Content that violates our Code of Conduct will not be accepted and be delisted if it was previously approved

Resource Title
Global Power Platform Bootcamp Korea - Hands on Lab material (in Korean)
https://aka.ms/gppbkr/appdev-in-a-day
Resource Type
Hands-on-Lab material & open-source project
Resource Description
This is a hands-on-lab session material for Korean speaking low-code developers and code-first developers to follow. It includes Power Apps and Power Automate, and custom connectors hosted on Azure Functions, integrated with Azure API Management.
Resource Tags
power-platform, power-apps, power-automate, power-platform-custom-connector
Your Name and GitHub profile
Justin Yoo @justinyoo
(Optional) Your Twitter profile
@justinchronicle
(Optional) Anything else we need to know
This is a good for workshop resource written in a language other than English.

Thanks!


docs-bug(Autocomplete): Examples autocomplete doesn't work

Documentation Feedback
examples don't work on main site - material.angular.io and stackblitz service
error in console:
main-es2015.807f533dcf8794ae3ae6.js:1 ERROR TypeError: Cannot read property 'selectors' of null
version 12.0.0-next.3 (because I can't checkout to the 11 version)
Affected documentation page: https://material.angular.io/components/autocomplete/examples

Some examples in Select don't work too
https://material.angular.io/components/select/examples

Should be fixed now. We accidentally deployed the wrong version.


sbt 0.13.13.tgz has a different directory layout than 0.13.12.tgz

(See the guidelines for contributing, linked above)
steps
export SBT_VERSION='0.13.12'
cp ./sbt.pub /tmp/sbt.pub
curl -fSL https://dl.bintray.com/sbt/native-packages/sbt/$SBT_VERSION/sbt-$SBT_VERSION.tgz -o sbt.tgz \
                 https://dl.bintray.com/sbt/native-packages/sbt/$SBT_VERSION/sbt-$SBT_VERSION.tgz.asc -o sbt.tgz.asc \
    && export GNUPGHOME="$(mktemp -d)" \
    && gpg --import /tmp/sbt.pub \
    && rm /tmp/sbt.pub \
    && gpg --batch --verify sbt.tgz.asc sbt.tgz \
    && rm -r "$GNUPGHOME" sbt.tgz.asc \
    && tar -zxC /root/ -f sbt.tgz \
    && rm sbt.tgz
export PATH="/root/sbt/bin:$PATH"

Works, but
problem
If you set SBT_VERSION to 0.13.13 it doesn't because the directory has been renamed from 'sbt' to sbt-launcher-0.13.13
expectation
I expect the directory layout to be the same
notes
otherwise I'd consider it a semver break.

Thanks for the report. I wonder if it's related to our bumping up sbt-native-packager.

although if you change it back, you're going to break me again, as I've now updated to the new path.

@eed3si9n Yes, I believe that is correct. The same happened to @fommil in Ensime: https://github.com/ensime/ensime-server/pull/1632

On Mac, the old one expanded to a directory named "sbt".
New one is now called "sbt-launcher-packaging-0.13.13". This is the problem right?
I think we should change it back to "sbt".

I'm not familiar with sbt-native-packager, but I've started a conversation with @muuki88 to try and fix this post-upgrade, for the next release.

@eed3si9n this isn't for macOs, this is on a Linux machine

My recommendation would be to fix soon and release <IP_ADDRESS>.tgz.

In the meantime, could we come up with a workaround to buffer this change? http://unix.stackexchange.com/questions/11018/how-to-choose-directory-name-during-untarring

I'm using export PATH="/root/sbt-launcher-packaging-$SBT_VERSION/bin:$PATH"

I haven't had the time yet to look at the new sbt release. Can I reproduce this behaviour when I publish sbt locally from the 0.13 branch and upgrade native-packager?

@muuki88 here's the repo - https://github.com/sbt/sbt-launcher-package/blob/master/CONTRIBUTING.md. start sbt with something like
$ sbt -Dsbt.build.version=0.13.13

I submitted a PR (https://github.com/sbt/sbt-launcher-package/pull/127)

This is now fixed, I think.

@eed3si9n nope it's still in sbt-launcher-packaging-$SBT_VERSION can you reopen until you upload a 3.13 that's not a semver break?


Added short code around include statement

/assign @JuleeB1
There's a few more notes

https://deploy-preview-10006--kubernetes-io-master-staging.netlify.com/docs/tasks/federation/federation-service-discovery/

/lgtm
/approve
/hold
(in case the hackathon peeps are tracking these somewhere else. @Bradamant3 ?)

/hold cancel
and thank you @mistyhacks for thinking of it. Improv all the way, though :-)


replace flake8 sorter with isort

There is no easy way to automatically satisfy flake8's linting requirements for sort order. Using isort there is.
I ran
isort --recursive nox

to automatically sort imports. Then I updated noxfile to test with isort rather than flake8.

I'm in favor of removing the isort call from the lint session.
On Tue, Aug 27, 2019 at 10:05 PM Chad Smith<EMAIL_ADDRESS>wrote:

Unfortunately isort’s output is not deterministic. It depends on what
packages you have installed, your working directory and probably other
factors. The build is now failing even though I ran the blacken session
locally. I will have to follow back up here. One solution may just be to
remove the isort check from nox’s lint session.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/theacodes/nox/pull/242?email_source=notifications&email_token=AAB5I45RTTUKUKXTCY5HQ7DQGYBR3A5CNFSM4IP5IZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5J43II#issuecomment-525585825,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB5I42QL3PQM3E5UIXARLLQGYBR3ANCNFSM4IP5IZ4A
.

tbh we should pin all of the lint/format tools so that contributors don't
get tangled in unrelated style updates.
On Wed, Aug 28, 2019 at 9:40 AM Chad Smith<EMAIL_ADDRESS>wrote:

@cs01 commented on this pull request.
In noxfile.py
https://github.com/theacodes/nox/pull/242#discussion_r318682235:

@@ -59,16 +58,19 @@ def cover(session):
@nox.session(python="3.7")
def blacken(session):
"""Run black code formater."""

session.install("black")
session.run("black", "nox", "tests", "noxfile.py", "setup.py")

session.install("black", "isort==4.3.21")

I pinned it because I thought it would fix the discrepancy between me
running it locally and the CI check, but it didn't. Still, it might help
keep the sort order more consistent between runs. I don't really feel
strongly either way.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/theacodes/nox/pull/242?email_source=notifications&email_token=AAB5I45N7SXCT7PCAWN4MJTQG2S6PA5CNFSM4IP5IZ4KYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCC7RZ3I#discussion_r318682235,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB5I43BMNKFHVHYONEQDHLQG2S6PANCNFSM4IP5IZ4A
.


The leaderboard is missing in https://paperswithcode.com/sota/text-classification-on-glue-qnli

Since it gets removed by the officials, we close this issue for now.


Jetson Nano Orin: libnvidia-ml.so does not found, msg="no GPU detected"

Hello everyone! I'm using a Jetson Nano Orin to run Ollama.

I'm using a jetson containers dustynv/langchain:r35.3.1.
To run this container :
docker run --it --runtime=nvidia --gpus 'all,"capabilities=graphics,compute,utility,video,display" --net host --name ollama -e NVIDIA_VISIBLE_DEVICES=all -e $DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix --privileged dustynv/langchain:r35.3.1
To verify the availability of GPU within the container, I ran CUDA-Samples, and the tests passed successfully.
Inside the container, I installed Ollama using curl -fsSL https://ollama.com/install.sh | sh.

The first time I did this, there was an error output during the installation:
...
>>> Installing NVIDIA repository ...
curl: (22) The requested URL returned error: 404
...
>>> Install complete. Run "ollama" from the command line.

I resolved this error by following #2302.
When I run ollama serve I have:

time=2024-03-13T09:14:02.769Z level=INFO source=images.go:710 msg="total blobs: 0"
time=2024-03-13T09:14:02.769Z level=INFO source=images.go:717 msg="total unused blobs removed: 0"
time=2024-03-13T09:14:02.770Z level=INFO source=routes.go:1021 msg="Listening on <IP_ADDRESS>:11434 (version 0.1.28)"
time=2024-03-13T09:14:02.770Z level=INFO source=payload_common.go:107 msg="Extracting dynamic libraries..."
time=2024-03-13T09:14:07.602Z level=INFO source=payload_common.go:146 msg="Dynamic LLM libraries [cuda_v11 cpu]"
time=2024-03-13T09:14:07.602Z level=INFO source=gpu.go:94 msg="Detecting GPU type"
time=2024-03-13T09:14:07.602Z level=INFO source=gpu.go:265 msg="Searching for GPU management library libnvidia-ml.so"
time=2024-03-13T09:14:07.607Z level=INFO source=gpu.go:311 msg="Discovered GPU libraries: []"
time=2024-03-13T09:14:07.607Z level=INFO source=gpu.go:265 msg="Searching for GPU management library librocm_smi64.so"
time=2024-03-13T09:14:07.608Z level=INFO source=gpu.go:311 msg="Discovered GPU libraries: []"
time=2024-03-13T09:14:07.608Z level=INFO source=cpu_common.go:18 msg="CPU does not have vector extensions"
time=2024-03-13T09:14:07.608Z level=INFO source=routes.go:1044 msg="no GPU detected"

I attempted: find / -name "*libnvidia-ml*"
/usr/local/cuda-11.4/targets/aarch64-linux/lib/stubs/libnvidia-ml.so
If I copy or move this library into one of the directories where Ollama searches for it and then run ollama serve:

time=2024-03-13T09:26:04.586Z level=INFO source=images.go:710 msg="total blobs: 0"
time=2024-03-13T09:26:04.587Z level=INFO source=images.go:717 msg="total unused blobs removed: 0"
time=2024-03-13T09:26:04.587Z level=INFO source=routes.go:1021 msg="Listening on <IP_ADDRESS>:11434 (version 0.1.28)"
time=2024-03-13T09:26:04.587Z level=INFO source=payload_common.go:107 msg="Extracting dynamic libraries..."
time=2024-03-13T09:26:09.371Z level=INFO source=payload_common.go:146 msg="Dynamic LLM libraries [cuda_v11 cpu]"
time=2024-03-13T09:26:09.371Z level=INFO source=gpu.go:94 msg="Detecting GPU type"
time=2024-03-13T09:26:09.371Z level=INFO source=gpu.go:265 msg="Searching for GPU management library libnvidia-ml.so"
time=2024-03-13T09:26:09.375Z level=INFO source=gpu.go:311 msg="Discovered GPU libraries: [/usr/lib/libnvidia-ml.so]"

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
WARNING:

You should always run with libnvidia-ml.so that is installed with your
NVIDIA Display Driver. By default it's installed in /usr/lib and /usr/lib64.
libnvidia-ml.so in GDK package is a stub library that is attached only for
build purposes (e.g. machine that you build your application doesn't have
to have Display Driver installed).
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
time=2024-03-13T09:26:09.377Z level=INFO source=gpu.go:323 msg="Unable to load CUDA management library /usr/lib/libnvidia-ml.so: nvml vram init failure: 9"
time=2024-03-13T09:26:09.377Z level=INFO source=gpu.go:265 msg="Searching for GPU management library librocm_smi64.so"
time=2024-03-13T09:26:09.378Z level=INFO source=gpu.go:311 msg="Discovered GPU libraries: []"
time=2024-03-13T09:26:09.378Z level=INFO source=cpu_common.go:18 msg="CPU does not have vector extensions"
time=2024-03-13T09:26:09.378Z level=INFO source=routes.go:1044 msg="no GPU detected"

I also attempted to use the Ollama container, but encountered the same result.
How can I resolve this issue?

@gab0220 Hello, sorry I missed your issue. I've been working on a patch for this which was just merged today in #2279. The next major release should include the changes that re-enable support for Jetsons. If you would like to run it sooner, you should pull the latest Ollama commit and compile it locally.
Note: Jetsons + GPU acceleration + containers is a bit weird compared to other machines. I would advise you check out dusty-nv  on Github if you're interested in learning how to get containers working properly on Jetson devices. In the mean time, I am not sure the Ollama container is built to support Jetsons and I haven't personally worked on it yet (coming soon).
In the mean time, you should be able to pull the repo and build locally for it to run. Check the documentation for more detailed instructions, and feel free to ping me if you run into any issues.

I attempted: find / -name "libnvidia-ml"
/usr/local/cuda-11.4/targets/aarch64-linux/lib/stubs/libnvidia-ml.so

The reason libnvidia-ml.so doesn't exist on Jetson devices is because NVidia didn't include the NVidia ML library in Jetpack prior to JP 6. What you had there is a "stub" library, which exists purely so you can compile with nvml support without having nvml library in your driver (to use the binary on another machine). The "stub" doesn't actually contain any code or implementation for code, so it won't work for the purposes of this project on devices running JP < 6.

Hello @remy415, thank you for your response.
I've upgraded the Jetpack to JP6, ensuring that libnvidia-ml.so is now correctly located in its designated directory. Following the manual installation steps outlined in the Linux installation guide and the accompanying tutorial for NVIDIA Jetson Devices, I successfully installed Ollama. The outcome yielded:
Mar 26 09:41:03 ubuntu systemd[1]: Started Ollama Service.
Mar 26 09:41:03 ubuntu ollama[964]: time=2024-03-26T09:41:03.379+01:00 level=INFO source=images.go:806 msg="total blobs: 5"
Mar 26 09:41:03 ubuntu ollama[964]: time=2024-03-26T09:41:03.382+01:00 level=INFO source=images.go:813 msg="total unused blobs removed: 0"
Mar 26 09:41:03 ubuntu ollama[964]: time=2024-03-26T09:41:03.382+01:00 level=INFO source=routes.go:1110 msg="Listening on [<IP_ADDRESS>:11434](https://<IP_ADDRESS>:11434/) (version 0.1.29)"
Mar 26 09:41:03 ubuntu ollama[964]: time=2024-03-26T09:41:03.386+01:00 level=INFO source=payload_common.go:112 msg="Extracting dynamic libraries to /tmp/ollama1468253564/runners ..."
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.954+01:00 level=INFO source=payload_common.go:139 msg="Dynamic LLM libraries [cpu cuda_v11]"
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.954+01:00 level=INFO source=gpu.go:77 msg="Detecting GPU type"
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.956+01:00 level=INFO source=gpu.go:191 msg="Searching for GPU management library [libnvidia-ml.so](https://libnvidia-ml.so/)"
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.964+01:00 level=INFO source=gpu.go:237 msg="Discovered GPU libraries: [/usr/lib/[libnvidia-ml.so](https://libnvidia-ml.so/)]"
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.977+01:00 level=INFO source=gpu.go:82 msg="Nvidia GPU detected"
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.977+01:00 level=INFO source=cpu_common.go:18 msg="CPU does not have vector extensions"
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.988+01:00 level=INFO source=gpu.go:109 msg="error looking up CUDA GPU memory: device memory info lookup failure 0: 3"
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.988+01:00 level=INFO source=routes.go:1133 msg="no GPU detected"
Mar 26 09:58:27 ubuntu systemd[1]: Stopping Ollama Service...
Mar 26 09:58:27 ubuntu systemd[1]: ollama.service: Deactivated successfully.
Mar 26 09:58:27 ubuntu systemd[1]: Stopped Ollama Service.
Mar 26 09:58:27 ubuntu systemd[1]: ollama.service: Consumed 8.728s CPU time.

I'll keep you informed.

Hello @remy415, thank you for your response.
I've upgraded the Jetpack to JP6, ensuring that libnvidia-ml.so is now correctly located in its designated directory. Following the manual installation steps outlined in the Linux installation guide and the accompanying tutorial for NVIDIA Jetson Devices, I successfully installed Ollama. The outcome yielded:
Mar 26 09:41:03 ubuntu systemd[1]: Started Ollama Service.
Mar 26 09:41:03 ubuntu ollama[964]: time=2024-03-26T09:41:03.379+01:00 level=INFO source=images.go:806 msg="total blobs: 5"
Mar 26 09:41:03 ubuntu ollama[964]: time=2024-03-26T09:41:03.382+01:00 level=INFO source=images.go:813 msg="total unused blobs removed: 0"
Mar 26 09:41:03 ubuntu ollama[964]: time=2024-03-26T09:41:03.382+01:00 level=INFO source=routes.go:1110 msg="Listening on [<IP_ADDRESS>:11434](https://<IP_ADDRESS>:11434/) (version 0.1.29)"
Mar 26 09:41:03 ubuntu ollama[964]: time=2024-03-26T09:41:03.386+01:00 level=INFO source=payload_common.go:112 msg="Extracting dynamic libraries to /tmp/ollama1468253564/runners ..."
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.954+01:00 level=INFO source=payload_common.go:139 msg="Dynamic LLM libraries [cpu cuda_v11]"
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.954+01:00 level=INFO source=gpu.go:77 msg="Detecting GPU type"
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.956+01:00 level=INFO source=gpu.go:191 msg="Searching for GPU management library [libnvidia-ml.so](https://libnvidia-ml.so/)"
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.964+01:00 level=INFO source=gpu.go:237 msg="Discovered GPU libraries: [/usr/lib/[libnvidia-ml.so](https://libnvidia-ml.so/)]"
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.977+01:00 level=INFO source=gpu.go:82 msg="Nvidia GPU detected"
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.977+01:00 level=INFO source=cpu_common.go:18 msg="CPU does not have vector extensions"
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.988+01:00 level=INFO source=gpu.go:109 msg="error looking up CUDA GPU memory: device memory info lookup failure 0: 3"
Mar 26 09:41:08 ubuntu ollama[964]: time=2024-03-26T09:41:08.988+01:00 level=INFO source=routes.go:1133 msg="no GPU detected"
Mar 26 09:58:27 ubuntu systemd[1]: Stopping Ollama Service...
Mar 26 09:58:27 ubuntu systemd[1]: ollama.service: Deactivated successfully.
Mar 26 09:58:27 ubuntu systemd[1]: Stopped Ollama Service.
Mar 26 09:58:27 ubuntu systemd[1]: ollama.service: Consumed 8.728s CPU time.

I'll keep you informed.

Following the manual installation steps outlined in the Linux installation guide and the accompanying tutorial for NVIDIA Jetson Devices, I successfully installed Ollama.

Their current release is 0.1.29 from two weeks ago, this is before the Jetson support merge was done. If you want to run this now, you'll have to compile the binary yourself on the system or wait for the release of 0.1.30. Please note that Jetpack already comes with the NVidia toolkit installed.
To do this, following the instructions here:

Ensure the following is installed:

cmake version 3.24 or higher
go version 1.22 or higher
gcc version 11.4.0 or higher

Ensure the LD_LIBRARY_PATH variable is set with your CUDA library paths. This is typically export LD_LIBRARY_PATH=/usr/local/cuda/lib64 but may vary if your system has been reconfigured.
Ensure you have git CLI tool installed, see github documentation.
Clone the github repo:

cd <project base directory>
git clone https://github.com/ollama/ollama.git
cd ollama

Build the binary. Note: setting export OLLAMA_SKIP_CPU_GENERATE="1" will speed up the build time for you as the ARM CPUs don't have the AVX extensions anyway.
Note the 3 dots in go generate ./...

go generate ./... && go build .

You should now be able to run Ollama with ./ollama serve and in another terminal ./ollama run <model>

Just a note: You shouldn't need to adjust the num_gpu parameter as it should be configured automatically. You should be able to just use the default dolphin model. If there's an issue where not all layers are offloaded, that means that either the model is too big, or there's an underlying issue with the application.

@remy415 how are we looking on Jetson's in 0.1.33?  If you set LD_LIBRARY_PATH to point to the hosts CUDA lib dir, are we still having problems?

@dhiltgen last time I built it, it worked just fine. I'll give it another run now

@dhiltgen It works great, just when I set the LD_LIBRARY_PATH it doesn't seem to use host libs:

Unless I did something wrong when compiling? I did a standard compile with no special options

or did you mean from the binary? I forgot to check that. I installed the latest binary and ran it with the ld_lib_path, same result as above: it worked just fine and seemed to use bundled libs

That's great news that the official binary is working without having to set LD_LIBRARY_PATH.  Ultimately the goal is not to require any special settings if possible, so it sounds like we've achieved that.
I'm going to go ahead and close this ticket.  Let me know if you think there's any lingering glitches we need to re-open it for.

@dhiltgen according to the logs, it did a GPU library search, found the bundled library and the libraries in the "default" directories, then selected the bundled library. I ran lsof and it does have the libraries at the /usr/local/cuda/lib64 directory open, but it all works so I think it's good as far as I can tell.


Can't find asset_locks.proto.sol

On running npm run copy-interop-contracts in the samples/besu/simpleasset, I ran into an error of cp: cannot stat '../../../common/protos-sol/asset_locks.proto.sol': No such file or directory.

The folder common/protos-js/common does not exist
➜  interoperation-node-sdk git:(main) ✗ make build-local
mkdir -p protos-js && \
        cp -r ../../../common/protos-js/common ./protos-js/ && \
        cp -r ../../../common/protos-js/corda ./protos-js/ && \
        cp -r ../../../common/protos-js/driver ./protos-js/ && \
        cp -r ../../../common/protos-js/fabric ./protos-js/ && \
        cp -r ../../../common/protos-js/msp ./protos-js/ && \
        cp -r ../../../common/protos-js/networks ./protos-js/ && \
        cp -r ../../../common/protos-js/peer ./protos-js/ && \
        cp -r ../../../common/protos-js/relay ./protos-js/ && \
        cp -r ../../../common/protos-js/identity ./protos-js/ && \
        cp -r ../../../common/protos-js/package.json ./protos-js/
cp: cannot stat '../../../common/protos-js/common': No such file or directory
make: *** [makefile:8: build-local] Error 1

Issue has been resolved. protoc wasn't installed in the system.


IA-1539: iterate all perms to find landing page

Some profiles were not correctly redirected when they didn't have permission for the landing page
Self proof reading checklist

[X] Did I use eslint and black formatters
[X] Is my code clear enough and well documented
[X] Are my typescript files well typed

Changes

change getFirstAllowedUrl to keep looking for eligible route if the first permission found isn't linked to any routes

How to test

create a user without the permission to forms but with the untranslated permission iaso_beneficiaries and at least 1 other permission (except the polio ones)
log in with that user

Print screen / video
There's no point really, just login and see if you get a the 401 screen
Notes
The bug happened because of a dangling permission after a migration. Removing that permission is part of another ticket.
Anyway it's good to have a more robust fallback method, because we've had permissions leading to nowhere before.

I don't get the failing test. It passes locally. @codeKameleon @beygorghor , any suggestion is welcome


Require iOS 8 in the podspec

Based on the release notes: https://github.com/mixpanel/mixpanel-iphone/releases/tag/v2.9.0

Hi @yas375 that line refers to the coming update v3.0.0.
We are currently still compatible with iOS 7

OIC. sorry :)

No apologies needed. Thanks for the PR!