n-way-dimmer.js halts with undefined error string

Describe the bug
n-way-dimmer.js halts with undefined error string
Describe the bug
When pressing the on/off switch on the Shelly Plus dimmer with the n-way-dimmer.js script running, it'll error out and halt as a string is undefined.  From the console:
Running UpdateLightState:
Update Switch State from KVS - switchOn : true - KVSOn : true - switchBrightness : 43 - KVSBrightness
: 43
Uncaught ReferenceError: "error_message" is not defined
at ...nt(JSON.stringify(result), error_message, message);
^
in function "callbackfunction" called from ...Result, rpcCode, rpcMessage);
^

Not having any experience in js I can't tell what should be defining this string, hence the bug report for the experts.
A quick hacky fix is just to simply comment out the print.
To Reproduce

update device firmware to 1.4.4
two ShellyPlus Wall Dimmer devices connected to wifi over router-assigned static addresses
web console opened to each
from Scripts-> Library, select the n-way-dimmer.js script and install
change the IP addresses to the two nodes
press the power switch on one device which will cause the error shown above and halt the script

Hi,
I've written a new version of this script and fixed this problem.
Here is the summary of how it works:

Config: Defines the list of IP addresses for the dimmer devices in the group. Users need to change this group to their dimmer IP addresses. The wifi address will be filled automatically; please do not change this field.

Remote device control: It used to synchronize current dimmer state to other dimmers.

KVS Module: To Save current dimmer status to key-value store.

MAIN Module: Monitors state change events from the device.

Based on the event type, triggers the following actions:

If brightness or on/off state changes, calls updateKVSState to synchronize all devices.

If the KVS value changes, calls updateLightState to update the local device state.

You can find the script on the pull request here. Please test it to confirm that it works as expected.


Coroutine problem

I am facing a coroutine problem using openai

This should be fixed now.  You can pull from master and re-install or just install in dev mode.  If it's still happening, unset your WANDB_API_KEY with:
WANDB_API_KEY= python -m openui

Let me know if not and share some more of the stacktrace so I can see what's up.

i still got the error
WANDB_API_KEY= python -m openui
INFO (openui):  Starting OpenUI AI Server created by W&B...
INFO (openui):  Running API Server
Logged in as W&B user ke-zhang-rock.
View Weave data at https://wandb.ai/no-1-zone-team/openui-test-21/weave
INFO (uvicorn.error):  Started server process [42712]
INFO (uvicorn.error):  Waiting for application startup.
DEBUG (openui):  Starting up server in 42712...
INFO (uvicorn.error):  Application startup complete.
INFO (uvicorn.error):  Uvicorn running on http://<IP_ADDRESS>:7878 (Press CTRL+C to quit)
INFO (uvicorn.access):  <IP_ADDRESS>:54824 - "GET / HTTP/1.1" 200
INFO (uvicorn.access):  <IP_ADDRESS>:54824 - "GET /assets/index-2-rOUq-J.js HTTP/1.1" 304
INFO (uvicorn.access):  <IP_ADDRESS>:54825 - "GET /assets/index-OfmkY5JK.css HTTP/1.1" 304
INFO (uvicorn.access):  <IP_ADDRESS>:54824 - "GET /assets/textarea-4A01Dc6n.js HTTP/1.1" 304
INFO (uvicorn.access):  <IP_ADDRESS>:54825 - "GET /assets/index-VsdO9OoH.js HTTP/1.1" 304
INFO (uvicorn.access):  <IP_ADDRESS>:54825 - "GET /v1/session HTTP/1.1" 200
INFO (uvicorn.access):  <IP_ADDRESS>:54825 - "GET /assets/Builder-b4JJdzJb.js HTTP/1.1" 304
INFO (uvicorn.access):  <IP_ADDRESS>:54825 - "POST /v1/chat/completions HTTP/1.1" 200
ERROR (openui):  Server Error: unhandled errors in a TaskGroup (1 sub-exception)
Traceback (most recent call last):
  File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/responses.py", line 264, in __call__
    await wrap(partial(self.listen_for_disconnect, receive))
  File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/responses.py", line 260, in wrap
    await func()
  File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/responses.py", line 237, in listen_for_disconnect
    message = await receive()
  File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/uvicorn/protocols/http/h11_impl.py", line 535, in receive
    await self.message_event.wait()
  File<EMAIL_ADDRESS>line 214, in wait
    await fut
asyncio.exceptions.CancelledError: Cancelled by cancel scope 15453ee30

During handling of the above exception, another exception occurred:

  + Exception Group Traceback (most recent call last):
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/middleware/errors.py", line 164, in __call__
  |     await self.app(scope, receive, _send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/middleware/sessions.py", line 83, in __call__
  |     await self.app(scope, receive, send_wrapper)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 62, in __call__
  |     await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
  |     raise exc
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
  |     await app(scope, receive, sender)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/routing.py", line 758, in __call__
  |     await self.middleware_stack(scope, receive, send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/routing.py", line 778, in app
  |     await route.handle(scope, receive, send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/routing.py", line 299, in handle
  |     await self.app(scope, receive, send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/routing.py", line 79, in app
  |     await wrap_app_handling_exceptions(app, request)(scope, receive, send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
  |     raise exc
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
  |     await app(scope, receive, sender)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/routing.py", line 77, in app
  |     await response(scope, receive, send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/responses.py", line 257, in __call__
  |     async with anyio.create_task_group() as task_group:
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 678, in __aexit__
  |     raise BaseExceptionGroup(
  | exceptiongroup.ExceptionGroup: unhandled errors in a TaskGroup (1 sub-exception)
  +-+---------------- 1 ----------------
    | Traceback (most recent call last):
    |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/responses.py", line 260, in wrap
    |     await func()
    |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/responses.py", line 249, in stream_response
    |     async for chunk in self.body_iterator:
    |   File "/Users/kezhang/src/openui/backend/openui/openai.py", line 15, in openai_stream_generator
    |     async for chunk in subscription:
    | TypeError: 'async for' requires an object with __aiter__ method, got coroutine
    +------------------------------------
ERROR (uvicorn.error):  Exception in ASGI application
Traceback (most recent call last):
  File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/responses.py", line 264, in __call__
    await wrap(partial(self.listen_for_disconnect, receive))
  File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/responses.py", line 260, in wrap
    await func()
  File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/responses.py", line 237, in listen_for_disconnect
    message = await receive()
  File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/uvicorn/protocols/http/h11_impl.py", line 535, in receive
    await self.message_event.wait()
  File<EMAIL_ADDRESS>line 214, in wait
    await fut
asyncio.exceptions.CancelledError: Cancelled by cancel scope 15453ee30

During handling of the above exception, another exception occurred:

  + Exception Group Traceback (most recent call last):
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/uvicorn/protocols/http/h11_impl.py", line 407, in run_asgi
  |     result = await app(  # type: ignore[func-returns-value]
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/uvicorn/middleware/proxy_headers.py", line 69, in __call__
  |     return await self.app(scope, receive, send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/fastapi/applications.py", line 1054, in __call__
  |     await super().__call__(scope, receive, send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/applications.py", line 123, in __call__
  |     await self.middleware_stack(scope, receive, send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/middleware/errors.py", line 186, in __call__
  |     raise exc
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/middleware/errors.py", line 164, in __call__
  |     await self.app(scope, receive, _send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/middleware/sessions.py", line 83, in __call__
  |     await self.app(scope, receive, send_wrapper)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 62, in __call__
  |     await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
  |     raise exc
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
  |     await app(scope, receive, sender)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/routing.py", line 758, in __call__
  |     await self.middleware_stack(scope, receive, send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/routing.py", line 778, in app
  |     await route.handle(scope, receive, send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/routing.py", line 299, in handle
  |     await self.app(scope, receive, send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/routing.py", line 79, in app
  |     await wrap_app_handling_exceptions(app, request)(scope, receive, send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
  |     raise exc
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
  |     await app(scope, receive, sender)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/routing.py", line 77, in app
  |     await response(scope, receive, send)
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/responses.py", line 257, in __call__
  |     async with anyio.create_task_group() as task_group:
  |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 678, in __aexit__
  |     raise BaseExceptionGroup(
  | exceptiongroup.ExceptionGroup: unhandled errors in a TaskGroup (1 sub-exception)
  +-+---------------- 1 ----------------
    | Traceback (most recent call last):
    |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/responses.py", line 260, in wrap
    |     await func()
    |   File "/Users/kezhang/src/openui/backend/venv/lib/python3.10/site-packages/starlette/responses.py", line 249, in stream_response
    |     async for chunk in self.body_iterator:
    |   File "/Users/kezhang/src/openui/backend/openui/openai.py", line 15, in openai_stream_generator
    |     async for chunk in subscription:
    | TypeError: 'async for' requires an object with __aiter__ method, got coroutine
    +------------------------------------

Same here.
After adding a print(type(subscription)) to openai_stream_generator, it seems that subscription returns as a coroutine.
Adding the following before the for loop temporarily solves the issue:
    if asyncio.iscoroutine(subscription_coroutine):
        subscription = await subscription_coroutine
    else:
        subscription = subscription_coroutine

The issue can also be fixed by removing wand & weave imports for now if tracking is not essential.

Appologies here, I just disabled the call to weave.init in server which will resolve this entirely.  There's a bug where it doesn't like the way I'm using generators.  Installing from master will resolve this issue.


Feature request - show error or warning when two functions have the same name

Is there a reason JSHint doesn't show an error or warning when two function declarations exist with the same name in the same scope?  Since JSHint catches variable names, I was wondering why not function names.
Use case:

I was writing test cases and using abbreviated function names - eventually writing two with the name "getPIP".  The test case failed for the first one appropriately and after realizing it was the result of an overwritten function, I wondered why jshint doesn't catch that.

If this was in a previous issue I apologize, I did wade through quite a few both open and closed without finding anything.

This is a duplicate of #1304 and #1019.

Ah "redefinition" was the word I should have searched.  Thanks for pointing those out.


Added name to input attribute and translations

Thank you for your efforts to make this component.
I've added a property to the text field with the purpose to obtain information within a form, as it did not have the property.
Also, I've added a translation feature.
You can accept the request or not, no problem =).
Best regards.

Hey @coderdiaz thank you for your contributions!
I'm currently away for a couple of weeks but will review when I return.

@charliekassel It's ok. Greetings.

Great, thanks.
And thank you for your contributions!

The changes are ready!


Vram required?

Thanks for the great work! What is the minimum Vram required?

Hi toyxyz, inferring a video of 250 frames requires approximately 20GB of GPU memory. If you encounter an issue with insufficient GPU memory, consider reducing the length of the guidance motion sequence.

@sdbds
Hi, the default motion-01 in inference.yaml has more than 500 frames. Maybe you could try switching to other set of example data with less frames.

@sdbds Hi, the default motion-01 in inference.yaml has more than 500 frames. Maybe you could try switching to other set of example data with less frames.

Thank u, it works.


Fix: Nuvoton print wifi_ping errors

Nuvoton print wifi_ping errors
Description
It is hard to know what went wrong when Nuvoton wifi_ping fails, therefore, we are printing error codes when it does
Checklist:

[ X ] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks


-cutLines, -deleteLines and -duplicateLines don't consider multiple selection ranges

Those methods operate only on the first selected range ATM. This may not be the expected behaviour when selecting multiple ranges either directly or by using one of XcodeBoost's multi-selection features (such as "Select Method Definitions").

Won't fix, as multiple selection ranges isn't a well supported feature in Xcode anyway.


What is the smallest increment that brightness accepts?

Question is in the title, what is the smallest increment that brightness accepts? Is it to one decimal place? 0.1 0.2 0.3 etc?

I just pass the brightness directly through to the OS APIs.  You can experiment and see (a) if your changes are preserved when you read the brightness back, and (b) if your changes actually have any visible appearance on the display.


The future of vars

Thanks to @gshank @joellabes @ChenyuLInx for a great discussion yesterday about all things vars! I'll do my best to summarize below.
Prompted by requests like:

vars should be definable outside dbt_project.yml (#2955)
vars should be available for resource configs defined in dbt_project.yml (#4873)
vars (defined in dbt_project.yml) can be set to Jinja-rendered expressions (#3105, #3658)
sources should be able to use macros to determine env-specific (and source-specific) namespacing (#4753)

When to recommend...?

vars
env vars
target-based logic
"pure" macros that return static values (available to set configs + template runtime code in .sql files, but not in .yml files)
generate_x_name macros (database/schema/alias of "executable" nodes, but not for sources)

Do we have any strong recommendations around when to use vars, and when to use env vars? I don't think so, at least not well-documented. Here are my own strong-ish opinions:
Env vars

Secrets — including credentials (if you need to check profiles.yml into version control), or git-related info in packages.yml
Any time of environment-based configuration that reliably differs between dev/prod/CI, e.g. a different source database per environment
"Run modes" that are going to differ in a predictable way

Vars

Configuring packages, using levers that the package maintainer has documented and made available, through well-understood means that you never
"Run modes," with sensible defaults that hold >95% of the time, that it may make occasional sense to "override" with arbitrary / unpredictable values (via CLI --vars)

One small note: dbt is smarter about partial parsing today with env vars (an actual partial re-parse) than with vars (will trigger a full re-parse, whether the change is in --vars or in dbt_project.yml). This is a temporary technical limitation only, and we plan to reach eventual parity.
Other types of config

target-based Jinja conditional expressions are nice when you want to surface the logic very close to where it's being used: {{ 3 if target.name == 'dev' else 100 }} days of data for a backfill, for instance.
generate_x_name macros have a leg up on the others, in that they have access to everything: all vars, env vars, target info, and the full node specification of the model/seed/snapshot/test. So if you have highly specific rules about what goes where (if X config, Y tag, Z materialization type, ...), the macro is the right place to encode that "rule." This logic just can't be (re)used anywhere else

Forward-looking vibes
While some of these changes are not mutually exclusive, I sensed two
Vibe 1: Vars are exactly like env vars.
You can (already) define both on the CLI:
$ dbt run --vars 'MY_VAR: True'
$ MY_VAR=True dbt run

They should available in all the same places and rendering contexts. That includes profiles.yml + packages.yml (places where only --vars are available today).
Vars can be defined in a .yml or .env file, in addition to dbt_project.yml. They're parsed first, regardless of where they're defined—even before profile information.
Vibe 2: Vars are a way to DRY up your project
Vars save and render static Jinja expressions, which can take env vars + target values as their inputs.
Following the example in #4753, imagine you've got:
sources:
  - name: source_one
    database: |
      {%- if 'other_country' in target.database -%} prod__other_country__source_one
      {%- elif target.name == 'prod' -%} prod__main_country__source_one
      {%- else -%} {{ target.database }}__source_one
      {%- endif -%}
    ...
  - name: source_two
    database: |
      {%- if 'other_country' in target.database -%} prod__other_country__source_two
      {%- elif target.name == 'prod' -%} prod__main_country__source_two
      {%- else -%} {{ target.database }}__source_two
      {%- endif -%}

We've proposed solving that with better source configurations (#3662), crucially the ability to configure multiple sources at once. But look again: Those configs are just slightly different.
The immediate instinct is to replace this with a macro, until you realize that macros aren't supported in .yml files today—at this point, primarily for reasons of rendering speed / parsing performance. And we can't tell a "pure" macro (static inputs + outputs) from a "dirty" one.
Instead, what if you could "save" a reusable Jinja expression / static snippet, in the form of a rendered var?
# dbt_project.yml
vars:
  my_project:
    source_database_prefix: |
      {%- if 'other_country' in target.database -%} prod__other_country__source_two
      {%- elif target.name == 'prod' -%} prod__main_country__source_two
      {%- else -%} {{ target.database }}__source_two
      {%- endif -%}

sources:
  - name: source_one
    database: {{ var('source_database_prefix') }}__source_one
    ...
  - name: source_two
    database: {{ var('source_database_prefix') }}__source_two

This feels much more intuitive for vars that are set in dbt_project.yml, versus the ones passed in for --vars. In fact, it feels like a bit of a disjuncture between them. Do we need a third kind of var...?

Vibes-wise, I'm most attached to the problems solved by Vibe 2, but I disagree with the approach to get there:

Do we need a third kind of var...?

What about a second type of macro? We could take inspiration from Redshift UDFs (and likely other things) which can attach hints (VOLATILE | STABLE | IMMUTABLE) to indicate whether the planner can recycle the same output for a given input.
It would be cool to be able to do something like this:
{% macro immutable generate_database_prefix() %}
      {%- if 'other_country' in target.database -%} prod__other_country
      {%- elif target.name == 'prod' -%} prod__main_country
      {%- else -%} {{ target.database }}
      {%- endif -%}
{% endmacro %}

sources:
  - name: source_one
    database: {{ generate_database_prefix() | trim }}__source_one
    ...
  - name: source_two
    database: {{ generate_database_prefix() | trim }}__source_two

and only allow this subset of macros in yaml files, where they would have access to target and env_vars/variables defined by --vars. Any immutable macro that tried to do anything to the database would be rejected.
Functionally, this would be identical to the variables envisaged above. I think it would aid in a cleaner mental model though - conceptually I think of vars as constant, exported values, not as snippets of code in their own right.
I could swing either way on whether we allow things like {{ run_started_at }} - at that point you're looking at STABLE as opposed to IMMUTABLE in redshiftese - I'm not averse to it but I can't think of a use case.

Regarding Vibe 2 I suggest the following extension on vars:
Folder-level variables
Imagine that we could define variables in the dbt_project.yml in models → <my_project> → <model_folder_name>.
This would be a very useful way to configure, e.g., mart schemas of which many technically similar ones exist by just defining mart/schema-specific variables which are then picked up by the models of this folder/schema.
Example:
'''yaml
vars:
global vars:
test_lake_load_ts_predicate: "(_lake_load_ts > (current_timestamp - interval '3 days'))"
test_mod_ts_predicate: "(_mod_ts > (current_timestamp - interval '3 days'))"
package-specific vars:
↓ current implementation ↓
dbt_artifacts:
dbt_artifacts_database: "lp_lake"
dbt_artifacts_schema: "raw_dbt_artifacts"
dbt_artifacts_table: "lp_prodb"
↑ current implementation ↑
models:
general model settings:
+persist_docs:
relation: true
columns: true
+post-hook:
- "{{ dbt_snow_mask.apply_masking_policy() }}"
packages:
dbt_artifacts:
# NOTE: To me it feels like a good idea to put package-specific variables
# rather here than in the global vars block above!
###### ↓ proposed change ↓ ######
vars:
dbt_artifacts_database: "lp_lake"
dbt_artifacts_schema: "raw_dbt_artifacts"
dbt_artifacts_table: "lp_prodb"
###### ↑ proposed change ↑ ######
+schema: core_dbt_artifacts
staging:
+schema: orig_dbt_artifacts
this project:
this_dbt_project:
mart_whatever:
  +schema: mart_whatever
  description:  A generic data mart

###### ↓ proposed change ↓ ######
vars:
    source_prefix: "whatever"
    database_name: "whatever_2"
###### ↑ proposed change ↑ ######

'''
Side note: As you can see, I also propose to put package-specific vars rather (or alternatively/additionally) into the models section of the specific package.
What do you all think about this?

I'm going to turn this into a GitHub discussion, since we're using those more frequently — for Bigger Improvements, in addition to Very Big Ideas.
We don't have immediate next steps, or concrete plans of when to schedule this work, but it's feedback (and confusion) that we get pretty consistently. By the time of dbt v2, I'd like to see us have better, more consistent, more intuitive answers for conditional configuration.


连接线的问题，界面一点点的小遗憾。

就是竖线位置有细微错位的地方。

Hey @kubulo
Thank you for reporting the issue! It must have been introduced with one of the recent logseq updates. There were similar issues with new versions breaking the bullet threading like this in the past.
I'm looking into this and doing my best with a quick fix today or tomorrow!

Hey again @kubulo,
I'm not able to reproduce this issue. Checked on two systems and screens with different resolutions.  I tried with different levels of indentation, also adding Chinese characters.
Are you using the latest version of logseq and the theme (currently it's 1.1.15)? I found the integrated check update function in logseq sometimes doesn't pull updates. You can try uninstalling and reinstalling the theme from the marketplace in that case.

This doesn't seem to be an issue anymore, so I'm closing it. Please leave a word if you still notice the problems, then we will open it again and tackle them 💪


MultiSubnetFailover settings in Knex package

Development
Knex version: 0.20.1
MSSql Database + Version 15.0
OS: macOS 10.14.6
@smorey2
How can we add settings in the connection config for connecting it to MSSQL Server Multi-Subnet Failover Clusters, right now it can't connect ?

It should be done in mssql driver's configuration... at least tedious seems support it https://github.com/tediousjs/tedious/issues/387 I don't know if node-mssql does.
Anyways knex should not care about it. Closing as this should be inmplemented in driver level.

Yes Tedious supports multiSubnetFailover.
Tedious Docs


[Bug] UX : The colour code in the Form widget property pane overlaps the field

Steps to reproduce:

Add a form widget
Click on the property pane of the widget
Click on the background-color
and observe

Observation:
It is observed that the form widget color palette overlaps on the field and user has less visibility on the field
Expectation:
The color palette must be placed in such a way that the user would be able to see and focus on the field
Screenshot

Resolved in #4413. Please check the deploy preview

Closing as it's been fixed.


Decompose cphase to two fSim gates

This implements the decomposition described in section VII F I of the supplement to the quantum supremacy paper.

PTAL

PTAL


Improve small candlestick rendering and support custom wick color

New Contributors:
please review CONTRIBUTING.md
Purpose:
Fixes the drawing of "Doji" candlesticks (i.e. open == close) #800
New Functionality:
Adds a check for the Doji case and adds a red line where otherwise the candle body would not be drawn.
OHLC[] arr = DataGen.RandomStockPrices(new Random(0), 10);
arr[5] = new OHLC(arr[5].open, arr[5].high, arr[5].low, arr[5].open, arr[5].time); // Ensure a doji session exists

plt.AddCandlesticks(arr);

Before:

After:

Currently the body of the candle is the colour passed into ColorDown (generally red), like the rest of the candlestick. I don't know if this is preferred, after all red implies that the price went down over the session, but the point of this PR is for when the price doesn't change. Perhaps someone with more interest in technical analysis can weigh in here.

That is good point @bclehmann. Often the candle wick is kept neutral. Black is often used against a white background. Here is an example with different backgrounds:

You could also leave it up to the user by making this color configurable and overwriting the existing settings.
I would not discard the green/red wicks completely. Some people like that. If it would be controllable via options that would be great ;)

I added a WickColor field which is by default System.Drawing.Color.LightGray. If SeparateWickColor is true then this colour is used instead of either ColorUp or ColorDown. This doesn't impact OHLCs at all.
Currently SeparateWickColor is true by default, which I leave to others to decide on which they think is better. I have not added a demo to illustrate the use of SeparateWickColor because if it gets changed to being off by default that demo would likely need to be changed to reflect that.

The grey wick is making me wonder if the candle bodies should have an outline?
I tried it and got this:

Perhaps LightGrey is too light, but I actually quite like this.

Hi @bclehmann
thank you for the quick feedback. The wicks look good 👍 . Normally they are relatively dark. Super cool if you can customize them. The outline I would make optional or very thin? Looks like the MS chart outline was no bigger than 1 px? You can see it here #800 in the reference image. If it's not complicated, you could make it customizable as well ;)

Hey @bclehmann and @AlgoExecutor, thanks for your input on this one!

Default styling is designed to closely mimic https://www.tradingview.com/chart

Customizing the wick (and border) color was a great idea, but I struggled with how to best expose this. I'm typically against using nullable value types because they can be confusing, but I think they make sense here (compared to a separate bool flag variable, or a magic color like Transparent to indicate no border).

I added some new examples to the cookbook demonstrating what it can do.

I'm worried I'm inviting chaos into the ScottPlot community with this one... but I made a demo designed to look like TC2000 😅 We'll see how much craziness it invites...

I love how this example shows a clear "consolidation period" and periods of "momentum", all resulting from a random number generator 😈
As a neuroscientist, I find the combination of chart reading and pattern hallucination fascinating.
Again I'm reminded of A Random Walk Down Wall Street

Thank you both @swharden and @bclehmann for the good work! I also had to laugh about the TC2000 chart :joy:. Looks like chaos is really coming - love it ;-)
You make a really good point. Reading charts is some kind of art. You just have to believe in it hard enough. Always reminds me of the tea cup pattern: https://www.investopedia.com/terms/c/cupandhandle.asp
Looks like the inventor had a deeper meaning in mind :upside_down_face:


Reference, or provide how to correctly limit the edgehub memory

Hi there, I am highly interested in the section on this page for "Reduce memory space used by Edge hub", but I don't see where I go to find out how to do this. Is there a setting to limit the edgeHub to xMB of memory? Or what are the mechanisms, and then links to detailed documentation to achieve this would be helpful!
Thanks!

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

ID: cf2368f4-6deb-ffb0-5e5a-eb73b5c7098e
Version Independent ID: c4d71d39-ebd9-da2b-251d-ca288bc733dc
Content: Prepare devices and deployments for production - Azure IoT Edge
Content Source: articles/iot-edge/production-checklist.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@hubez Thanks for the feedback! We are currently investigating and will update you shortly.

@hubez You can use Docker's container create options to specify memory limits for edge hub (or any module). See Memory setting under Container create options at https://docs.docker.com/engine/api/v1.18/:
{
       "HostConfig": {
         "Memory": xxx
      }
}

Reference: https://stackoverflow.com/questions/54343480/iot-edge-hub-testing-for-offline-storage?rq=1
https://github.com/Azure/iot-edge-v1/issues/537
Let us know if you have further questions.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Kubernetes integration with auto discovery

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
New Notification, New Monitor, Other
🔖 Feature description
The goal of the evolution would be to ensure that Uptime Kuma directly reads Ingress to self-configure HTTPs monitor.
And also with the possibility of creating custom config in the style:
apiVersion: uptime-kuma/v1
kind: tcp
metadata:
  name: home-assistant
spec:
  url: <IP_ADDRESS>
  port: 8123
  retry: 0
  alerting:
    slack:
      webhook: https://.......

or
apiVersion: uptime-kuma/v1
kind: ping
metadata:
  name: home-assistant
spec:
  url: <IP_ADDRESS>
  retry: 0
  alerting:
    slack:
      webhook: https://.......

✔ Solution
Create customressources uptime-kuma + RBAC
Uptime Kuma listen kubernetes API directly to read all configuration.
❓ Alternatives
No response
📝 Additional Context
No response

For a great example of something basic, hajimari is a good place to start.
https://github.com/toboshii/hajimari

For this, I'd use:
https://github.com/stakater/IngressMonitorController
with:
https://github.com/lucasheld/uptime-kuma-api

For this, I'd use: https://github.com/stakater/IngressMonitorController
with: https://github.com/lucasheld/uptime-kuma-api

Have you exemple to intergrate this tools into Uptime Kuma ?
I don't see Uptime Kuma compatibility :/

It has to be built ;)

Hi everyone!
I’ve developed a Kubernetes Ingress Monitor Controller called Kuma Ingress watcher. It is designed to automatically monitor Traefik IngressRoutes and/or Kubernetes Ingress in a Kubernetes cluster, creating corresponding monitors in Uptime Kuma. This controller is flexible and allows you to customize the monitoring configuration using annotations.
You can check out the Helm chart and the source code here.


Calls to Flagr:: EvaluationApi#post_evaluation with an empty body take an inordinate time to resolve

Calls to Flagr:: EvaluationApi#post_evaluation with an empty body take an inordinate time to resolve. Typically, in our systems, calls to that method with any body content are returned within < 1 ms, whereas calls with an empty body require up to 60 ms to process. The post_evaluation method should return instantly if the body is empty, as if the body was not provided.
Expected Behavior
When called with an empty body, flagr should respond immediately, and as it does today with a missing body.
Current Behavior
When called with an empty body (length 0), flagr takes an excessive amount of time to return (over 60 times the amount of time it takes with a body that has length greater than 0.
Possible Solution
Return immediately, treating it as a missing body.
Steps to Reproduce (for bugs)
Call /flagr/api/v1/evaluation with an empty body.
Context
This causes false errors in our system in which we think the system is slow to respond to a client, when in fact the client is providing an invalid request.
Your Environment

Version used (rbflagr-1.1.12):
Server type and version: 5.4.0-1038-aws #40-Ubuntu SMP Fri Feb 5 23:50:40 UTC 2021 x86_64 GNU/Linux
Operating System and version (uname -a): 5.4.0-1038-aws #40-Ubuntu SMP Fri Feb 5 23:50:40 UTC 2021 x86_64 GNU/Linux
Link to your project: (private repo)

I'm very curious about what this issue might be.
It could be in the rbflagr library rather than in flagr itself.
https://github.com/openflagr/rbflagr
https://github.com/openflagr/rbflagr/blob/1fc16ee47e02bcc4dc01a9304a24a54442f0a8d8/lib/rbflagr/api/evaluation_api.rb#L33-L71
https://github.com/openflagr/rbflagr/blob/1fc16ee47e02bcc4dc01a9304a24a54442f0a8d8/lib/rbflagr/api_client.rb#L349
Direct curls to the flagr api return immediately for both of the following scenarios.
[$]> curl -X "POST" "https://flagr.host.net/api/v1/evaluation"
{
  "code": 602,
  "message": "body in body is required"
}

[$]> curl -X "POST" "https://flagr.host.net/api/v1/evaluation" -H 'Content-Type: application/json; charset=utf-8' -d $'{}'
{
  "evalContext": {},
  "evalDebugLog": {
    "msg": "flagID 0 not found or deleted",
    "segmentDebugLogs": null
  },
  "timestamp": "2023-01-20T21:59:29Z"
}


Working code.

We still need to complete the README, I need to clean and comment the code, add more CSS styling, and comment out the "https://cors-anywhere.herokuapp.com/" portion of our MusixMatch API URLs. P.S. adding an error 404 redirect link or page for our API's would be a good idea (and include which API was not working in the 404 message).

No one responded and I have since updated the code


Linux Support

Are there any plans to add Linux support?

No plans at the moment. Perhaps in the future.


@alloy add analytics to email gallery link and gallery website

Per the conversation during sprint planning meeting, this adds analytics to the contact gallery via email link and the gallery website.

Code LGTM, but 🔴  on CI. You can merge it once you get that green 👍

💚
merging

"Clicked Contact Gallery" should be reserved for the button that leads to inquiry. We need a different schema for this.

In the future, it would be good to notify an analyst, so we avoid name duplication and we are consitent with properties (eg, we usually partner as opposed to gallery, and we call gravity id's (_id in force) id, and gravity slugs (id in force) slug

Sorry for the storm of comments, but we actually do not need an event for clicking "contact" -- there is a unique url for that view, eg "https://www.artsy.net/gagosian-gallery/contact". Would you mind if we removed that event altogether? And change the properties of the contact_gallery_website event to be:
partner_id: 4d8b92c44eb68a1b2c0004cb
partner_slug: gagosian-gallery


Don't Disable UTF-8 Module on Lua < 5.3

How are you using the lua-language-server?
Visual Studio Code Extension (sumneko.lua)
Which OS are you using?
Windows
What is the issue affecting?
Annotations, Libraries
Expected Behaviour
local utf8 = require("utf8") gives UTF-8 function definitions regardless of Lua version.
Actual Behaviour
local utf8 = require("utf8") only gives UTF-8 function definitions if Lua runtime version is 5.3 or later.
Reproduction steps
Reproducible with one line of code.
local utf8 = require("utf8")

On Lua runtime < 5.3, utf8 is unknown.
Additional Notes
Some Lua < 5.3 environments (e.g. love) provides Lua 5.3 utf8 module but this must be loaded separately using require.
It's reasonable to have utf8 in global namespace when user runtime is set to Lua 5.3 or later, but don't put the utf8 module in Lua 5.3 check, a.k.a. allow it to be loaded manually using require on earlier Lua version.
Log File
N/A, easily reproducible.

Should be resolved by setting runtime.builtin, but it dose not work now.


Refactor/consolidate in-memory-key-manager with wallet

Context
There's no practical benefit of keeping the InMemoryKeyManager separate from the wallet, in the same way
a particular hardware wallet would have, as most wallets will use the in-memory key manager
as the default.
Proposed Solution

Consolidate the in-memory-key-manager package with wallet.

Important Changes Introduced

Restructures the tests to reflect the source structure, removing source path mapping.
https://github.com/input-output-hk/cardano-js-sdk/pull/102/commits/955079143cbd564e3e1452b39a6a73c371f16bd2

Looks good. The tests are probably failing because it's missing a dependency: "bip39": "^3.0.4"

Yep, missed the failure since my local state had the package installed.

Additional important change listed above @mkazlauskas

Additional important change listed above @mkazlauskas

Is CSL not following semantic versioning? Either way I think it's ok to pin to specific CSL version because cardano-js-sdk users are supposed to get CSL indirectly anyway.

Is CSL not following semantic versioning? Either way I think it's ok to pin to specific CSL version because cardano-js-sdk users are supposed to get CSL indirectly anyway.

I'm not sure, but given the critical nature of this dep, I'd prefer we lock it and remove the chance of unexpected changes.


AudioEffectRecord returns all zero samples on Android

Godot version:
Tested on
v3.1.1.stable.official
and
v3.2.dev.custom_build.e23f5e641
OS/device including version:
Tested on
Android 9.0
and
Android 8.0
(Exported on Windows 10 Pro with Oracle JDK 8u221)
Issue description:
The data returned from AudioEffectRecord::get_recording() contains all zero values.  The size of the data sample appears to correlate with the length of the recording.  While the recorded data plays properly on Windows, it does not play at all on Android due to all samples being zero.
Steps to reproduce:
Export the sample project from the minimal reproduction project below to Android.
Look at the data returned from recording.get_data() in the sample project and it will contain all zeros.
Minimal reproduction project:
https://github.com/godotengine/godot-demo-projects/tree/master/audio/mic_record
Related issues/pull requests:
#30308

Permissions issue maybe?

Can confirm, this seems to be a simple permissions issue. I tried the mic record project, ran on my android tablet, recording was blank. Then I added the record from microphone permission in the export dialog, and viola, it was working. :smile:
It turns out there is a warning message already in logcat (although whether mere mortals will see this I don't know):
08-28 12:54:36.280 4381-4418/com.example.micrecord W/AudioRecord: AUDIO_INPUT_FLAG_FAST denied by client
08-28 12:54:36.280 125-2622/? W/ServiceManager: Permission failure: android.permission.RECORD_AUDIO from uid=10190 pid=4381
08-28 12:54:36.280 125-2622/? E/AudioFlinger: openRecord() permission denied: recording not allowed
08-28 12:54:36.280 4381-4418/com.example.micrecord E/AudioRecord: AudioFlinger could not create record track, status: -1
08-28 12:54:36.280 4381-4418/com.example.micrecord E/libOpenSLES: android_audioRecorder_realize(0x690c9210) error creating AudioRecord object
08-28 12:54:36.280 4381-4418/com.example.micrecord W/libOpenSLES: Leaving Object::Realize (SL_RESULT_CONTENT_UNSUPPORTED)
08-28 12:54:36.280 4381-4418/com.example.micrecord E/godot: **ERROR**: Condition ' res != ((SLuint32) 0x00000000) ' is true. returned: ERR_CANT_OPEN
08-28 12:54:36.280 4381-4418/com.example.micrecord E/godot:    At: platform/android/audio_driver_opensl.cpp:265:capture_init_device() - Condition ' res != ((SLuint32) 0x00000000) ' is true. returned: ERR_CANT_OPEN
08-28 12:54:38.310 4381-4381/com.example.micrecord D/dalvikvm: GC_FOR_ALLOC freed 371K, 5% free 7785K/8192K, paused 19ms, total 19ms
08-28 12:54:43.760 4381-4381/com.example.micrecord D/dalvikvm: GC_FOR_ALLOC freed 520K, 7% free 7773K/8332K, paused 26ms, total 26ms
08-28 12:54:49.420 4381-4381/com.example.micrecord D/dalvikvm: GC_FOR_ALLOC freed 512K, 7% free 7773K/8332K, paused 25ms, total 25ms

Enabling record audio in the export dialog indeed fixes this issue.  Thanks for confirming @lawnjelly


Update Tachometer.h

Added a function to return total tick count

there is no total tick count in library
if (ticks > window) {
            ticks = 0;


plugins: migrate gitops-profiles, pagerduty, search, register-component and techdocs to new composability API

Part of #3424
The search plugin router was already exported as SearchPage, so this is a breaking change for that plugin. As long as the app is migrated to using a flat top-level element structure and FlatRoutes it's not a breaking change though, so it's a bit lower impact as long as the create-app migration instructions are followed.

Tugboat has finished building the preview for this pull request!
Link:

https://pr4395-h5lapqnov0qspnmp2acllwolrmtpehch.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/601c46d214dc5863bcc2ea15

Tugboat has finished building the preview for this pull request!
Link:

https://pr4395-h5lapqnov0qspnmp2acllwolrmtpehch.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/601c46d214dc5863bcc2ea15

Tugboat has finished building the preview for this pull request!
Link:

https://pr4395-h5lapqnov0qspnmp2acllwolrmtpehch.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/601c46d214dc5863bcc2ea15

Tugboat has finished building the preview for this pull request!
Link:

https://pr4395-h5lapqnov0qspnmp2acllwolrmtpehch.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/601c46d214dc5863bcc2ea15


Contact journal (diary) entries disappear

Technical details
CASE 1

iPhone SE
CWA 1.10.1
iOS 14.4 and 14.3

CASE 2

iPhone 6s
CWA 1.10.1
iOS 14.4

Describe the bug

Contacts disappear from the contact journal

Steps to reproduce the issue

CASE 1

Go to Contact journal
Add persons
Go back, see entries
close CWA (swipe)
open CWA, check contacts

CASE 2

Create contact jounal entries using the same person

last day
and other days
after one day, with the last day being deleted, all other entries of the same person have disappeared

Expected behavior

Contacts shouldn't disappear, only after 14 days

@Ein-Tim Can you reproduce this? Thanks for the feedback.

@Ein-Tim Can you reproduce this? Thanks for the feedback.

Case 1 not reproducible, will test Case 2. Will report back here tomorrow.
Testing on both, iPhone 6s & XR

Case 1 not reproducible, will test Case 2. Will report back here tomorrow.
Testing on both, iPhone 6s & XR

IMHO somebody should test the behavior with an iOS update. Somebody here who is on iOS 14.3 and wants to update to 14.4?
If yes, please create some entries in the contact journal and close the App completely. Then, open the app back up after you updated (maybe even without WiFI).
Thanks!

IMHO somebody should test the behavior with an iOS update. Somebody here who is on iOS 14.3 and wants to update to 14.4?
If yes, please create some entries in the contact journal and close the App completely. Then, open the app back up after you updated (maybe even without WiFI).
Thanks!

Tested this:

Add entries to contact diary
Close App completely
Update from version 1.10.1 to 1.11.0
All entries still there

Tested this:

Add entries to contact diary
Close App completely
Update from version 1.10.1 to 1.11.0
All entries still there

Tested Case 2 too, not reproducible on my devices. 🤷♂

Tested Case 2 too, not reproducible on my devices. 🤷♂

Same here, I cannot reproduce either.

Same here, I cannot reproduce either.

Internal tracking ID: EXPOSUREAPP-4952

we have some indication that this issue is resolved by updating from iOS 14.3 to 14.4.

@Ein-Tim yep, can't be reproduced in 1.11 and 14.4. closing it. Thanks for feedback !


Upgrades jline 3.12.1 -> 3.16.0, to give support for xrvt terminals

Upgrades version for jline from 3.12.1 to 3.16.0. The upgrade is just to give support to xrvt terminal emulators (support given by 3.15.0 and later, in 3.16.0, other issues were fixed)

Thanks for the PR, @gtejedap!


Support other sources?

archive.is?

Hi @justingoldberg, and thanks for the note. As it's currently written, this library's code is quite specific to the Wayback Machine, and I don't personally see having time to support other services. That said, I'd be open to reviewing proposals for adding such functionality. (This isn't a promise to merge; but I'd be happy to link to other repositories that provide this functionality if not merged into this repository.)

unfortunately, waybackpack no longer works with the issues of archive.org  being DDoS or down the last week or so.


Export layers very slow on Big Sur

What went wrong?
I migrated to Big Sur and now Export Layers is very slow. When I do an export, I get a spinner for 30 to 90 seconds before the export starts. The actual file export proceeds at normal speed (a few seconds). I didn't notice performance problems before installing Big Sur.
GIMP has some known performance problems on Big Sur (link) but it's unclear if this is related.
It probably doesn't make sense to try to fix Export Layers until the underlying Big Sur issues are fixed in GIMP, so this is sort of a placeholder bug. But this could be some weird file system timeout in Big Sur.
(By the way, the Export Layers feature is very useful and I use it almost every day, so thank you for creating it.)
If you can, tell us the steps to reproduce the problem.
I have a 4623x4570 image, and I use "Export Layers (repeat)" to export to png.
Expected behavior: should start exporting files.
Observed behavior: spinner for a long, long time before export starts.
Configuration
Version of Export Layers: unknown
Version of GIMP:  2.10.14
Operating system: macOS Big Sur 11.1

Always happy to see someone enjoying using this plug-in :)
This was actually reported as an issue for GIMP itself and has been closed:
https://gitlab.gnome.org/GNOME/gimp/-/issues/5989
I am assuming that the latest GIMP 2.10 version fixes this. Hopefully this issue did not re-emerge with newer versions of macOS :)
Also, if you use multiple custom procedures applied before export, especially on large images, the export will natually be delayed since a considerable amount of time will be spent just on applying the procedures.


Install socket.io from npm install socket.io

familia@familia-dekstop:~$ npm install socket.io
npm WARN publish-everything<EMAIL_ADDRESS>Adding entire directory to tarball. Please add a
npm WARN publish-everything<EMAIL_ADDRESS>.npmignore or specify a 'files' array in the package.json
node-waf configure build
Checking for program g++ or c++          : /usr/bin/g++
Checking for program cpp                 : /usr/bin/cpp
Checking for program ar                  : /usr/bin/ar
Checking for program ranlib              : /usr/bin/ranlib
Checking for g++                         : ok
Checking for node path                   : ok /home/familia/.node_libraries
Checking for node prefix                 : ok /usr
'configure' finished successfully (0.272s)
Waf: Entering directory /home/familia/.node_libraries/.npm/ws/0.4.0/package/build' [1/4] cxx: src/validation.cc -> build/default/src/validation_1.o [2/4] cxx: src/bufferutil.cc -> build/default/src/bufferutil_2.o [3/4] cxx_link: build/default/src/validation_1.o -> build/default/validation.node [4/4] cxx_link: build/default/src/bufferutil_2.o -> build/default/bufferutil.node Waf: Leaving directory /home/familia/.node_libraries/.npm/ws/0.4.0/package/build'
'build' finished successfully (1.187s)
npm ERR! install failed Error: Required package: options(latest) not found. (Found: ["0.0.2"])
npm ERR! install failed (required by<EMAIL_ADDRESS>npm ERR! install failed     at /usr/share/npm/lib/build.js:192:19
npm ERR! install failed     at cb (/usr/share/npm/lib/utils/graceful-fs.js:32:9)
npm ERR! Error: Required package: options(latest) not found. (Found: ["0.0.2"])
npm ERR! (required by<EMAIL_ADDRESS>npm ERR!     at /usr/share/npm/lib/build.js:192:19
npm ERR!     at cb (/usr/share/npm/lib/utils/graceful-fs.js:32:9)
npm ERR! Report this entire log at http://github.com/isaacs/npm/issues
npm ERR! or email it to<EMAIL_ADDRESS>npm ERR! Just tweeting a tiny part of the error will not be helpful.
npm not ok

Please upgrade your very outdated version of npm.


Support User Definable Name in Fork API

As a developer, I want to write an app that allows a user to fork a repo and give their fork a new name.
The fork endpoint needs to support passing in a name for the newly created repo.  The UI allows you to do this.

Doing this where you have to use the repo edit API like Github.
There is one issue with our copy of Gitea, in that we are using mysql v5.5 and utf8mb4 collation, and this causes the new unique indexing of access_token.token_hash (after changing column sha1 to token_hash) and this makes the key of 100 characters (sha1's are 100 characters and set as varchar(255)) too long. Yet if you use mysql 5.7 or utf8 as the collation it will work. I had to run:
SET foreign_key_checks = 0;

ALTER TABLE access_token CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci;

SET foreign_key_checks = 1;

and then run the new version of gitea.
This is only for latest gitea (not v1.8, but probably v1.9) so probably won't have to do anything if we keep using v1.8 of gitea.

Just a reminder to add the above SQL to steps of updating to v1.9, unless we aren't using the same version of mysql as bg.door43.org (I forget if this applies to git.door43.org or not)


Extend auto-triage/mention feature to failing builds in e.g. quickstarts

Right now when one make a change to Quarkus, they may inadvertently break the Quickstarts. It's generally easy to solve, but hard to spot, because it's hard to get properly notified about these failures.
For example I mainly work on Hibernate extensions on Quarkus. If I wanted to get notified when Hibernate quickstart builds start failing, my only option would be to subscribe to this issue, and then I'll be notified for every single quickstart failure, including those for the (many) extensions unrelated to Hibernate.
Solution proposal
In the bot, we already have code that:

in some place, analyzes a build (in particular test failures) and reports problems, grouped by module.
in another place, analyzes which directories a PR changed, then applies labels to that PRs and notifies the relevant people.

We could imagine that, on Quickstart build failures, the Quarkus bot, or an action, would analyze the build result, group propblems them by quickstart or relevant extension, then would provide a detailed report on the dedicated issue, and @mention the people responsible for these quickstarts or the relevant extensions.

We have Quickstarts compilation check in our Quarkus CI - https://github.com/quarkusio/quarkus/blob/main/.github/workflows/ci-actions-incremental.yml#L853
Tests were skipped to save CI capacity, maybe we can reconsider that decision. wdyt?

Tests were skipped to save CI capacity, maybe we can reconsider that decision. wdyt?

No opinion on resource usage, but it may not be strictly necessary. We'll need a way to detect compilation failures and assign them to the right people anyway.


Create MoveIt Config for Spot (ROS 2 URDF)

This pull request replaces #2, which was closed after I deleted a merged branch before that PR was finished. Previously, the MoveIt config had been based on the URDF provided in the spot_ros repository, but that URDF had erroneous joint limits. The URDF provided by the spot_ros2 repository should have fewer errors. Therefore, this branch will:

[x] Replace the spot_ros submodule with spot_ros2.
[x] Generate a MoveIt configuration based on the URDF provided by the spot_ros2 repository.
[x] Launch a demonstration in the style of demo.launch from panda_moveit_config.

The only remaining comment from PR #2 mentioned updating gazebo.launch based on the finalized joint angles for the standing and arm_stowed group states.


Update resources for Git with DevOps manual

Overview of changes
I added the callout with the link requested in Issue #99
Why are these changes being made?
From issue
Detailed description of changes
I added the callout (used callout with title) and then added the link (given in issue) to the callout.
Issue ticket number/s and link
Issue #99 (https://github.com/dfe-analytical-services/analysts-guide/issues/99)
Checklist before requesting a review

[ x] I have checked the contributing guidelines
[ x] I have checked for and linked any relevant issues that this may resolve
[ x] I have checked that these changes build locally
[ x] I understand that if merged into main, these changes will be publicly available

Hi @aporsch1, thanks for fixing this issue for us 😄 How did you find our repo, if you don't mind me asking?

I am taking a class on open source software, right now, and we had to makea contribution to a project. I figured this seemed like a nice place to make a small contribution. I hope I was able to help a bit


Error message when sharing a world_2d between Viewports

Godot version
v4.0.beta7.official [0bb1e89fb]
System information
Windows 10, Intel Core i7 10750H, Intel UHD Graphics, NVIDIA Quadro T1000
Issue description
When the main world_2d is assigned to a SubViewport.world_2d, this error message is printed once per frame:
E 0:00:01:0044   draw_list_bind_uniform_set: Attempted to use the same texture in framebuffer attachment and a uniform (set: 3, binding: 0), this is not allowed.
  <C++-Fehler>   Condition "attachable_ptr[i].texture == bound_ptr[j]" is true.
  <C++-Quellcode>drivers/vulkan/rendering_device_vulkan.cpp:7707 @ draw_list_bind_uniform_set()

I was trying to display parts of the world in a different position with the second viewport (which is actually working with this setup + some Camera2Ds). I was not expecting an error message here, let alone one that doesn't tell me how to solve the problem as a user.
Steps to reproduce
Create a new project with a Node2D Scene. Attach a SubViewportContainer and a SubViewport below it. Attach a script to the SubViewport with this snippet:
func _ready():
	world_2d = ($"/root" as Window).world_2d

Minimal reproduction project
test.zip

I found this related issue: https://github.com/godotengine/godot/issues/31856
And I got my example to run without error by setting the visibility layer and light mask of the SubViewportContainer to 2 and setting the  Canvas Cull Mask of the SubViewport to 1.
The issue seems to be due to some recursive rendering issue. It would still be nice to have a better error message for this.

As a temporary solution, I found that putting the SubViewportContainer under a new CanvasLayer node breaks the rendering recursion.


Placeholder: Move end month earlier after targets are set up

Impacts to Indicators page, IPTT, and Targets table

We decided to prevent this rather than building in all the complexity required to support this.


The addon doesn't open web interface with ingress

Problem/Motivation
The addon doesn't open web interface with ingress

(Why the issue was filed)

Expected behavior
The addon opens its own web interface with ingress

(What you expected to happen)

Actual behavior
The addon doesn't open web interface with ingress

(What actually happened)

Steps to reproduce
Click on the "open web ui" button

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

That is correct and not a bug.
Unfortunately, Due to technical limitations in Uptime Kuma, it is impossible to provide Ingres support to the Uptime Kuna add-on.


Consider re-trying when connecting to a host

Description
Usually vstest.console is the host, and it starts testhosts that are a clients. But when UWP does remote deployment, then testhost is started as host, and vstest.console is client.
Client connection is attempted immediately after host process is started, which is usually not a problem. But there is race condition between how fast testhost can start, and when we try to connect to it. When testhost is slow to start up, or if we attach debugger to it, the client connection gets refused ("silently"), and ends up timing out.
This is in log:
12244, 74, 2022/03/21, 13:20:41.499,<PHONE_NUMBER>205, vstest.console.exe, Unable to connect to server,
Exception occurred: System.AggregateException: One or more errors occurred. --->
System.Net.Sockets.SocketException: No connection could be made because
the target machine actively refused it <IP_ADDRESS>:8020

But this is what user ends up seeing after waiting 90 seconds:
12244, 45, 2022/03/21, 12:45:09.904,<PHONE_NUMBER>692, vstest.console.exe, Test host failed to start Test host
 launched:True
test host exited: False
TpTrace Error: 0 :
12244, 45, 2022/03/21, 12:45:09.919,<PHONE_NUMBER>736, vstest.console.exe, ProxyDiscoveryManager.DiscoverTests:
Failed to discover tests: Microsoft.VisualStudio.TestPlatform.ObjectModel.TestPlatformException: vstest.console
process failed to connect to testhost process after 90 seconds. This may occur due to machine slowness,
please set environment variable VSTEST_CONNECTION_TIMEOUT to increase timeout.
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyOperationManager.ThrowExceptionOnConnectionFailure(Int32 connTimeout) in C:\p\vstest\src\Microsoft.TestPlatform.CrossPlatEngine\Client\ProxyOperationManager.cs:line 489
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyOperationManager.SetupChannel(IEnumerable`1 sources, String runSettings) in C:\p\vstest\src\Microsoft.TestPlatform.CrossPlatEngine\Client\ProxyOperationManager.cs:line 274
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyDiscoveryManager.DiscoverTests(DiscoveryCriteria discoveryCriteria, ITestDiscoveryEventsHandler2 eventHandler) in C:\p\vstest\src\Microsoft.TestPlatform.CrossPlatEngine\Client\ProxyDiscoveryManager.cs:line 144

Steps to reproduce
Have remote uwp test run, and automatically attach debugger to the testhost, and add breakpoint on startup.
Expected behavior
Client will retry using some retry policy. Or will show the error and immediately fail.
Actual behavior
The error is basically invisible, debugger breakpoints need to be set code that is after connection setup. User has to wait for the timeout to happen.

I'm having issues at the moment with some refactoring and now my UWP Test app won't work anymore. I'm getting the timeout message, but have no idea why it won't connect to the app (I see the UWP app launching still). I don't see a host log or anything, and I can't even debug in VS, so I have no idea where to get more info or know what the problem is.
I can set breakpoints if I try and debug the UnitTest app directly, but that doesn't work the same from the text explorer. It looks like there's some verbose tracing available in the UnitTestClient infrastructure, but I don't know if that's documented how to turn on from VS or the vstest.console.exe commandline (since it launches the app).
Any pointers would be appreciated to make these scenarios more understandable when the UWP host fails to reach back to the client and make the connection for testing to continue.

This is a new feature and won't be implemented, we are focusing on adding new features to Testing.Platform instead.  https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-platform-intro?tabs=dotnetcli


EnableLocal errors

If I set "EnableLocal" to true in config.json I get two errors after running a game:
"No Steam configuration and/or API key"
"Steam profile is not public"
After setting "EnableLocal" to false again and restarting, the issue goes away.
I'm not sure how long I have been seeing these errors, but I know thy weren't there in a previous release.
I have Steam Achievements disabled.

Can you try this?
https://github.com/Lacro59/playnite-successstory-plugin/issues/479#issuecomment-2191342743

Many thanks for the update. The error has changed with the dev version: "Steam has not been correctly configured in settings". Neither of the original 2 errors are showing now. I haven't been using the plugin for a while (due to the OP issue) so this is likely referring to something I need to do rather than an additional bug, I'll let you know if/when I have any further success.

Not sure why you have closed this as there is still a bug present. I have disabled steam achievements and the new error (Steam has not been correctly configured in settings") only appears when "EnableLocal" is set to true.

Is the issue still present with the latest version?


Merge meshes - multiple inputs and single surface checkbox

I've only just started playing with the examples, so I might have missed something that gets the same result I'm about to outline? Anyway...
It would add a lot of flexibility if the Merge meshes node would allow for multiple inputs.
As well as having an As single surface checkbox that merges everything into a single surface on the mesh, in order to minimise draw calls (I'm guessing this is much more complex than just merging surfaces - which is something I've done in gdscript before).
So for the simple tree example:

The trunk, branches, and sub-branches would all link their Extrude along curve outputs into Merge meshes with As single surface checked.
The leaves would do the same on their own Merge meshes node.
Then both of their outputs would go into another Merge meshes node without As single surface checked.

And now you have a single tree mesh with only 2 surfaces, which could be piped into a MultiMesh, or even just saved to disk via the inspector.

That's on my to-do list, Merge meshes should have a merge surface option and a dynamic slot system like the one in parent to node.

I got this working, including merging surfaces, and I could setup a pull request, but...
I copied the dynamic slot system in parent_to_node and:

The latest 0.3 release has a bug with the remove button leaving an unnamed input behind.
I see that you want to move the dynamic slot system into ConceptNode.

So I'm not sure if you'll want to add my changes yet?

Right I forgot about this, the whole default gui code is a mess... I'll move this part in the base class as soon as I can since there a few nodes that could benefit from this.

I moved the dynamic input system in the base class in c79993de9861813e106e51dbd09e87248272b22f
Merge Meshes and Parent to Node both use this now

Awesome!
I've just had a quick look and _inputs.size() in get_input_count() seems to include the dynamic inputs already, so it's returning a value with the dynamic inputs added twice:
https://github.com/HungryProton/concept_graph/blob/ead7fac1f88ddea6d69633b02507f0b1fe471dbc/src/core/concept_node.gd#L123-L126
Also if I replace Parent to node with Merge meshes in the simple_tree example, the trunk gets skipped as it's a single MeshInstance.
https://github.com/HungryProton/concept_graph/blob/ead7fac1f88ddea6d69633b02507f0b1fe471dbc/src/nodes/meshes/merge_meshes.gd#L27
Note: I'm not very experienced with contributing on Github, so can you let me know if this type of reply is ok, or could I have done this in a more helpful way?

Also, with these dynamic inputs...
In order to add separate inputs that stay after the dynamic inputs (like a Merge Surface checkbox), we'd have to shift it's id every time a dynamic input is added or removed right? I know the simple solution is to put all other inputs first, but that might not always be ideal.
I see that you want to decouple the input id from the visual position per #11, but even with that in place, we'd still have to shift the visual position around in the above situation ay?
It makes me wonder if the dynamic inputs should be implemented as an ARRAY input type which you access with a single input id/position? I'm not sure how feasible that is though, as a lot of that base class stuff is over my head at the moment.

Good catch with the get_input_counts
For merge meshes no line 27, it should be an issue because get_input always return an array, no matter how many items it have, even if there's a single one so the issue probably comes from something else.
Changing the id dynamically sounds like a lot of trouble. It's not an issue to put every static slot at the beginning. But I guess it could be possible to abstract that into a single slot to allow multiple types of dynamic inputs on the same node. I'll see what I can do before the next release as this breaks backward compatibility with previous templates.

Oh I see what you mean, it's the size check that should be <= 0 instead of one.
Fixed in 0034ccdd6fea8740ecf7950a0f30c18cc6917ace

Alright, this is broken again and I don't even know why. I'm giving up on this dynamic system and moving with your suggestion of allowing multiple connections to the same input.
Inputs that allow this will have the same color but a different shape (probably square) to make it clearer they're different.

It sucks when when that happens.
I think what I had in mind was still having the dynamic input points to connect to, but the implementation was an Array node type on the code side.
A single input might be simpler and more robust, but it makes removing connections a bit trickier.
The best option I can think of would be for each click on the input to pick up the next connection, based on the order they were added? Is that what you're thinking?

I'm thinking of using a single slot for multiple connections even if that means connections are harder to remove. Maybe adding a shortcut to remove a connection when hovering it?

That could be helpful too.
Iterating the connection selected on each click could be quite usable though, and might be easier to implement?

That could work too, thanks for the suggestion!

Not sure if these are visible enough but inputs that accepts multiple connections now have a square icon.
 7a2a1e904e92a99c92be76b9a874e87fbb55171a
Default behavior for GraphEdits with multiple connections is clicking the input slot will delete the first connection in order they were made. Clicking and holding will detach the connection and once it's reconnected, clicking and holding will select the next one. It's not ideal and I'm not sure the GraphEdit API actually expose enough things to change this behavior but I guess it's fine for now.


fields: keep entries order in errors list 2: son of fields: keep entries order in errors list

(This PR is a resubmission of #258.)
Three facets two consider:

New behaviour adds None for empty errors. Maybe it should add [] so users can avoid the extra is not None?
To localize errors, it's only necessary to add Nones up to the latest error, e.g. ['a', '', 'a'] -> [None, <errors>] instead of [None, <errors>, None]. It might be more convenient to have the error list the same length as the data.
If no errors, the old behaviour (errors == []) is kept. Ditto above on convenience.

This change makes sense to me. @whb07 I'm not sure why the tests don't look right on your machine, they appear to be passing on Travis.

I agree with the general goal of this PR. I’m aware for the need to be able to correctly enumerate the fields using FormField especially when doing an AJAX request.
I’ll have to check later what’s the reason as to what exactly that new test is asserting and why it’s passing. But from preliminary basic usage on clean servers for each one as noted above, the actual code as is, is not doing what it’s supposed to.

@davidism  how is having a list such as [{'username': ['Not a valid choice']}, None, None, None, None] help enumerate which field exactly needs to be addressed? Are the fields kept in order going in and going out? How do you ensure order when its posted ?

Hmm, good point, I think there's a related issue open about order of field list fields when not all of them are submitted. Not sure if that's solvable.

I mean it’s up to you, if you can don’t merge this in yet. I’ll see if we can come up with a viable way to enumerate properly. There are ordered dicts and other possible solutions now that python2.7 is EOL.
But as this goes, this does not appear to move FieldList forward. But it’s up to you @davidism

@whb07 Do you mean it's possible for data to be [<valid>, <invalid>], but the output to be either [[], <error>] or [<error>, []]? How would this happen? Are you referring to _extract_indices iterating over formdata keys (e.g. a-1 processed before a-0)? Because other than that, everything, as far as I can tell, maintains the order.
Also, I would expect FieldList to maintain order. Otherwise, it might be better to name it UnorderedFieldList :)

I'm saying multiple things that were quickly glossed over:

containers don't keep order
Even if you had an ordered container you wouldn't be able to control the order they come in via Flask etc...
A list filled with None is not very informative. This entire PR's purpose I thought was to help the user better understand which part exactly was invalid in a nested form.

There are ways to better address this, either give them an index or perhaps a hint as to the data that was inside the invalid field. The latter option might be better as all the parts are already there. I'll just submit a PR later to patch this up.

If FieldList isn't intended to be ordered, it should be renamed. List implies ordering.
Can you give an example of this? I assume you're talking about using HTML forms+POST, because the order of items in a JSON array wouldn't change. If so, it seems to me wtforms expects the subfields of FieldList to be named {fieldname}-{index} (or more generally, {prefix}{index}), in which case the order information is available and should be used in _extract_indices. I don't see anywhere else things can get re-ordered, but if I'm wrong please show me how that can happen.
The Nones (or []s as per @davidism's changes) themselves aren't informative. However, the presence of these in the list causes the position of the errors to match up with the data. The "index" you say should be given is what this provides, implicitly: the errors at position i correspond to the data at position i.

Maybe I should give more details of what my front-end looks like, though this sort of logic could also exist server side for validation, rendering, etc. Initial page load passes down a JSON description of the form (generated from the wtform), initial data; there's also the errors, which are initially empty, but also get updated from AJAX submissions. These variables go into a render function:
function render_form(field, data, errors) {
    const $err = render_errors(errors);
    let $widget;

    if (field.type == 'object') {
        $widget = [];
        for (const k of Object.keys(data)) {
            const $subwidget = render_form(field.subfields[k], data[k], errors[k]);
            $widget.push(

                {k}
                {$subwidget}

);
        }
    } else if (field.type == 'list') {
        $widget = [];
        for (let i = 0; i < data.length; ++i) {
            $widget.push(render_form(field.subfield, data[i], errors[i]));
        }
    } else if (field.type == 'text') {
        $widget = <input type="text" value={data}/>;
    } else if (/* other types */) { ... }

    return
{$err} {$widget}
;
}

Again the intent of the PR is correct. There should be better inspection for nested forms. But having a [{field: [error message here]}, None, None, None ] is just as helpful as the current way it is now. I't would be much more useful to hint within the error itself something like name or short_name which is an attribute already available to members under the FieldList.

I don't understand why you say the new behaviour is "just as helpful as the current way". I gave this example data:
[<valid>, <invalid>]

Error-wise, pre-patch, this is produced:
[<errors>]

The  might apply to either the first item, or the second, there's no way to tell. Post-patch, you get these errors:
[[], <errors>]

Now it's clear that the first item had no errors, and the second item had errors.
True, if the items containing errors were always a contiguous prefix of the list, as your examples all are, this wouldn't be necessary. You're totally right, in that case, it's unnecessary. However, it's possible that there exist i < j such that item[i] has no errors and item[j] has errors. In these cases, the post-patch is more helpful.
Or is your objection to having a string of []s at the end of the error list? It's true they're not necessary, since a user can assume any i > len(errors) has no errors and get the same information. It's similar to having []s for FormField subfields that have no errors: unnecessary, but harmless.


integration: remove inspect command

it was added to find the DHCP issue and doesn't provide a lot of value
and it crashes now with new DC syntax changes, so removing it.
Signed-off-by: Boris Glimcher<EMAIL_ADDRESS>

error before this PR is
unknown shorthand flag: 'c' in -c
See 'docker inspect --help'.
+ true


Support RPC 0.5.0

Describe your changes

[x] Add starknet_specVersion
[ ] Add starknet_getTransactionStatus, Add TXN_STATUS
[x] Update receipts

[x] Each receipt has its own data class
[x] Add execution_resources to receipts.
[x] Remove StarknetTransactionReceiptType, use StarknetTransactionType instead in this and similar cases

[x] Address return of BROADCASTED_TXN

[x] Make classHashes required in Transaction data classes

[x] Remove starknet_pendingTransactions
[x] Address changes to BLOCK_HEADER,  added PENDING_BLOCK_HEADER, changes to PENDING_BLOCK_WITH_TX_HASHES and PENDING_BLOCK_WITH_TX

[x] Add RESOURCE_PRICE, l1_gas_price, starknet_version

[x] Address removal of 0x1 as invoke v1 version - no changes, will be deserialized should another value be passed
[x] Address addition of DEPLOY_ACCOUNT_V1
[x] Improve handling of CONTRACT_ERROR: now contains data property with revert_reason.
[x] Trace API:

[x]  Add STATE_DIFF
[x] Update tx traces
[x] Update FUNCTION_INVOCATION, add ORDERED_EVENT, ORDERED_MESSAGE

[x] Add NUM_AS_HEX. Use NumAsHex instead of Felt where needed to avoid Felt overflow.
[x] #334
[x] Test on network
[ ] Test using devnet-rs
[x] Serializer fixes

[x] #341
[x] #317

Linked issues

Closes #313
Closes #341
Closes #334
Closes #317
Breaking changes

[x] This issue contains breaking changes

Pending devnet tests. https://github.com/0xSpaceShard/starknet-devnet-rs/issues/218


Is the repo abandoned?

3 years since the last commit. Many emojis are no longer processed.
Are there any alternatives? Or is it possible to add missing emojis?

should we fork it and continue to provide updates?

should we fork it and continue to provide updates?

If someone does it, it will be perfect.

i'm wondering the same thing and curious how this (outdated) library compares to icu4j.
While the purposes of two libraries is slightly different they both appear to serve the purpose of identifying Emoji's in strings so they can be automatically removed during server-side validation if needed.

Hello everyone. On my side I am using a fork from https://github.com/jefersonbitencourtv/emoji-java for the time being as it support Emojis 13.1. But it would be great to have this library maintained (there are a bunch of pull requests ready to add missing emojis).

I find this repo https://github.com/felldo/JEmoji and will use it


Added optimization for OpenSearch engine which were missing

Description
This PR added the optimization for Opensearch engine in this benchmarking tool. Along with the optimizations I have also upgraded the OS docker image to latest version(at the time of raising this PR) which is 2.14
Testing
I performed a local testing on a small dataset and a small configuration and I can see improvements in Opensearch results.
Sample run results
Cluster: single node with CI based docker setup
python3 -m run --engines opensearch-default --datasets glove-25-angular

Indexing
{
  "params": {
    "experiment": "opensearch-default",
    "engine": "opensearch",
    "dataset": "glove-25-angular",
    "parallel": 16,
    "method": {
      "parameters": {
        "m": 16,
        "ef_construction": 100
      }
    }
  },
  "results": {
    "post_upload": {},
    "upload_time": 52.828218106064014,
    "total_time":<PHONE_NUMBER>1007824
  }
}

Search
{
  "params": {
    "dataset": "glove-25-angular",
    "experiment": "opensearch-default",
    "engine": "opensearch",
    "parallel": 100,
    "config": {
      "knn.algo_param.ef_search": 128
    }
  },
  "results": {
    "total_time": 17.1585195150692,
    "mean_time": 0.013182678549340927,
    "mean_precisions": 0.9283049999999999,
    "std_time": 0.016356453433367828,
    "min_time": 0.0020476150093600154,
    "max_time": 0.7723487680777907,
    "rps":<PHONE_NUMBER>965589,
    "p95_time": 0.030238651664694766,
    "p99_time": 0.07367674464592752
  }
}

Please let me know if I need add this in upstream qadrant repo.

In the next PR I will add the support of faiss engine using cosinesiml distance function. I didn't add that functionality because faiss is only getting used when filters are present.

@filipecosta90


Fix for orchard issue #5869

This fixes a problem when using cloud services. The Azure web project had lost the msbuild tasks that copy the core, modules and themes folders from the Orchard.Web project over to the Azure Web project

Hi @mattcowen, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Is this to make Debug work? Because deployment worked just fine for me.

Yes, this is purely for getting the debugging of your cloud service in the local emulator. The project already contained what was required to deploy to a cloud service.
I'm simply adding what was in there before - not changed anything with what I've added.

I'm simply adding what was in there before

Can you point me to the commit where it was removed, just to be sure it was a mistake and not on purpose.

I've gone back to https://github.com/OrchardCMS/Orchard/commit/3e20412ef011f840a09b24aff62eeaddf42d5ec4
and can't find it by checking 5 or so commits on the way. There is a reference in this commit's version to a proj file that appears to copy modules and themes.
I can vouch for it working (if that helps).

this PR is a confirmed fix for cloud service deployments (confirmed on gitter)

nah @dcinzona turned out this isn't what was causing my issue, this just fixes debugging in the emulator

Ah, thanks for clarifying @carlwoodhouse - thought it did fix the issue based on the convo on gitter, but interesting to know it did not.

@dcinzona at the same so did i, but i also fixed something else which actually fixed it ..


Convert Superglue JS to typescript

All of superglue is written in ES6. For developers working with React, typescript has been a valuable tool to have. It would improve the developer experience if superglue was converted to Typescript.
Thoughts
Not all features of superglue can be converted to typescript.

digging is a feature that make it easy to create medium effort interactivity, but it works off of key paths (http://xyz.com/posts/?props_at=header.notifications)
Superglue also comes with UJS helpers, for example: using placeholders. Not sure what the best way to type this is.

Regardless, typing what we can is still a great step forward.

This task can be broken down into:
1 - add TypeScript first
2 - then we should be good to work on the other tasks mentioned here

Hi! I prototyped adding Typescript at RailsConf 2024, PR here: https://github.com/thoughtbot/superglue/pull/60
I've mostly been trying to follow this JS -> TS Migration guide -- still new to this!

Closing as we've fully moved  superglue.js to typescript. Thanks for giving this the start that it needed @johncardiologs


about ocsp

hi ，i want to use ocsp to check the certificate ， when the stream mode can support？

@zhiquy It's not yet ported to the stream subsystem but should be easy:
https://github.com/openresty/lua-resty-core/blob/master/lib/ngx/ocsp.lua
Will you create a pull request for it?


NaN value for predicate is currently 0 which is a bad idea

We should use the absence of a descriptor to indicate NaN

An "absence" will cause the property to missing on the decode.  We would then have to search for a side nan meta property which is problematic.
The correct solution is to use NSNull since we simply look at the image anyway.


Around_World€Arrow<$>+€

What version of Go are you using (go version)?

$ go version

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?

What did you expect to see?
What did you see instead?

Rojas_As_ManyKing%#*<^>+{€}=


chore: Simplify dagger implementation

Fixes #235

Change object instantiations to bindings
Add inject constructors to include in component graph

@arp95 @Shailesh351 @rohanagarwal94 Please review

@arp95 @Shailesh351 @rohanagarwal94 Please review

@niranjan94 @mariobehling Please merge


Whitelisting crashes Pi-hole 5.2 DNS resolver

Hey,
I updated Pi-hole to version 5.2 (FTL 5.3.1 // Web Interface 5.2)
When I whitelist a website via the edge plugin, the Pi-Hole DNS resolver crashes.
I have to login via IP to Pi-Hole (pi.hole don't work) and restart the DNS resolver in the settings dialog.

Same issue on Firefox and tested on Admin interface and it does not crash it only crashes with extension whitelist feature.

So i tried a clean Docker Installation of PiHole aswell as a clean installation on debian. With both installations and different urls etc it worked to whitelist them via the extension. Without any crashes.
Which color did the extension show after you whitelisted a domain?

extension goes red like pihole is disabled and then going to admin panel says cannot connect to api and i need to then reboot raspberry pi

I meant the color of the badge behind the url in the extension popup. After you click the whitelist button this should get some color.

i click green button to whitelist current site then area where it says the current URL turns green then extension show pihole as offline/Err and then seconds later pihole display i use shows "unable to communicate with pihole. aborting" then i need to remove power and boot it back up

From my point of view this is a problem caused by the update of PiHole. PiHole reports to the extension that the whitelist has worked. If it crashes after that the extension has no control over it.
For me it works with a current clean installation of PiHole (and any browser with the extension). So I would recommend to reinstall PiHole.

I will close this here, as this is probably a error that is caused by updating PiHole.

I will close this here, as this is probably a error that is caused by updating PiHole.


<EMAIL_ADDRESS>

Hello @jan-wassenberg, @eustas, @rhettstucki, modules you maintain (highway) have been updated in this PR. Please review the changes.


Fix some security issues in 2.19

I had to do some semver-major upgrades on some packages, but I verified that any breaking changes they made were limited to things we don't use.
All the remaining issues come from @bentley/react-scripts, except CVE-2022-31129.
https://github.com/iTwin/itwinjs-backlog/issues/390

I fixed CVE-2022-31129 by manually patching pnpm-lock.yaml. I don't know why this was needed, because all the dependencies on moment were version ranges satisfied by<EMAIL_ADDRESS>Somehow pnpm didn't detect that it could be updated when running rush update.


Problems with SendError

There is currently no way to create a SendError which means you have to resort to workarounds as per https://github.com/alexcrichton/futures-rs/issues/401.
I've been trying to use this to stream out a hyper body from a file in a performant fashion.
I've had to adjust the SendError struct to have a public member:
pub struct SendError<T>(pub T);

With that example snippet works:
//file is a FsReadStream from futures-fs
let file = self.fspool.read(path)
    .map(|bytes| {
        Ok(hyper::Chunk::from(bytes))
    })
    .map_err(|err| {
        SendError(Err(hyper::Error::Io(err)))
    });

let (tx, body) = hyper::Body::pair();

//ctx.handle() is a tokio remote handle
ctx.handle().spawn(tx.send_all(file).map(|_| ())
    .map_err(|_| ()));

Response::build().body(body)

If it's not a public field, you need to use the workaround mentioned:
let file = self.fspool.read(path)
    .map(|bytes| {
        Ok(hyper::Chunk::from(bytes))
    })
    .map_err(|err| {
        unimplemented!()
    });

I'm not sure this is the right approach, but I think being able to construct SendErrors would be a good workaround. Is there a reason why it's private?  If not I will raise a PR.

This was originally a private field to be maximally forwards-compatible from an implementation point of view, but the standard library uses a public field here and I don't think we're all that different, so I think it's fine to just go ahead and make this field public.

Hi,
I'm wondering if this did ever become public?

I would also like to see this become public 👍


[New practice exercise] Robot simulator

As we talked I proposed the approach with S3 class called "robot" and one generic method and one class method.
Becuase it is hard to force the implementation in this case I tried to suggest the implementation via:

Tests - one test if S3 class was defined and the others use class constructor. I cannot find a test for proper method dispatching, so move function could be also normal function.
Stub, which suggests object constructor, generic method and class method.

In example.R I proposed how I imagine S3 implementation for this exercise. I wanted it to be simple, cause this exercise does not justify full blown S3 implementation as there is only one class we can think of.
WDYT? Can I improve it somehow?

I don't know why the linter is complaining about the stub file, but not the example.R. We'll need @jonmcalder to comment on that, and any other linter issues.
I'll provisionally approve this now, but merging will need to wait for Jon's comments.

Approved provisionally, but linter issues need input from another reviewer.

I addressed some of the linter complaints but there are some inner errors of linter itself.
Look in the forum. I could take a look at this in the other PR.

I don't know why the linter is complaining about the stub file, but not the example.R.

I suspect linter can check if move.robot function belongs to the class robot of S3 system, maybe via methods() function.

@colinleach Could you look again? I solved the problem but the fact I had to use # nolint and it will be visible to student does not satisfy me.

Thanks this looks good!
And thanks also for addressing the outdated linter setup.
I'm not too fussed about adding in the #nolint comment in the stub to avoid the linter complaining - I was going to suggest that at least as a stop gap solution for now.
I did also consider it might confuse students slightly or be off-putting but even if it's not immediately clear a quick Google should make it obvious why it's there and it doesn't necessarily need to stay as part of their solution.
I just have the one gripe regarding types - feels like we should probably be a little stricter and expect integers, otherwise if we're ok with numerics then the example constructor shouldn't convert the type when creating the object.

should prompt students to implement a move generic but since the tests don't actually require or test for that it could be done > either way which I think is ok so (pending the issue regarding numeric vs integer types) I'm happy with this implementation as is > if you and @colinleach are.

I'm OK with that of course :).
Maybe it's a point for discussion during mentoring session about generics and dispatching.
I just wanted to introduce anything more than just a class (as that was already in triangle exercise).
Maybe later there will be exercises which give opportunity to build even more sophisticated S3 system based on already acquired knowledge.

Good work and thanks again!


Base template slots not filled on 404 page

What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.139.0-dacef0df92a9a20072b4eaa42003e1a63ace8f41+extended linux/amd64 BuildDate=2024-11-18T16:17:45Z VendorInfo=hugomods

I've bisected with past releases and this error seems to have been introduced in release 0.123.0
Does this issue reproduce with the latest release?
Yes
Issue
Hugo does not use the base template overrides for 404 pages,  resulting in missing or incomplete pages.
The example below shows the define block being ignored.
layouts/404.html

404 example

{{ define "main" }}

404 Not Found

The page you requested cannot be found.

      Return to the home page

{{ end }}

{{ if eq 1 1 }}

true

{{ else }}

false

{{ end }}

public/404.html

404 example

true

This example shows there is no 404.html generated in the public folder
layouts/404.html
{{ define "main" }}

404 Not Found

The page you requested cannot be found.

      Return to the home page

{{ end }}

https://gohugo.io/templates/base/#override-the-base-template

Code that you put outside the block definitions can break your layout. This even includes HTML comments. For example...

See @jmooring 's comment. This is unfortunate, but this is a limitation of Go templates, and not something we can fix.

This doesn't explain the second example in which nothing is generated.

Please use the forum (https://discourse.gohugo.io/) for questions and troubleshooting. We prefer to use GitHub for verified bugs and vetted enhancements. Thanks.


Limit mod request

So this list is basically some mods that i think would be cool to see in the modpack hehe

Survivality
Things

Need Patchouli, Trinkets, owo,,,,,,

Automobility
Particle Moths
Create addons (yay):

Create: Crystal Clear Refabricated
Create Addition
Create Extended Flywheels
Create Extended Cogwheels
Create Deco

EDIT: I FORGOT THE FUNNY DOOR MOD

Added some of the mods from this list, if there's any that remain that you think I should add, lemme know and I can provide some feedback on why or why not I'd include it in the pack. Thank you!


freecad: 1.0rc2 -> 1.0rc4

Update to FreeCAD 1.0rc4
Removes font issue patch which is now no longer required.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

The upstream bug https://github.com/FreeCAD/FreeCAD/issues/10514 has not been marked fixed yet, but it looks like there is a submit that should fix it.
LGTM, but I'd probably coordinate also with #347776 that adds some more configurability to FreeCAD so that you don't run into merge conflicts.


DATABASE_URL required when setting datasources.db.url

Bug description
I originally identified this as a regression of https://github.com/prisma/prisma/issues/2609.
DATABASE_URL is required, even when explicitly setting datasources.db.url in the PrismaClient constructor.
How to reproduce
Given the following,
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model User {
  // ...etc
}

import { PrismaClient } from '@prisma/client'

const url = `postgresql://user:pass@localhost/mydb`

const prisma = new PrismaClient({
  datasources: { db: { url } },
})

console.log('user count', await prisma.user.count())

Without setting DATABASE_URL, I get this error.
(node:35938) UnhandledPromiseRejectionWarning: Error:
Invalid `prisma.user.count()` invocation in
/Users/defrex/Code/treasure/api/src/prisma-repro.ts:19:47

  15 const prisma = new PrismaClient({
  16   datasources: { db: { url } },
  17 })
  18
→ 19 console.log('user count', await prisma.user.count()

  error: Environment variable not found: DATABASE_URL.
  -->  schema.prisma:7
   |
 6 |   provider = "postgresql"
 7 |   url      = env("DATABASE_URL")
   |

Validation Error Count: 1
    at PrismaClientFetcher.message [as _request] (/Users/defrex/Code/treasure/api/node_modules/@prisma/client/src/runtime/getPrismaClient.ts:999:51)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:35938) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:35938) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Expected behavior
I expect it to connect without needing to set the DATABASE_URL environment variable.
This error can be solved by setting DATABASE_URL to a "dummy" value that appears valid. Eg. DATABASE_URL=postgres://notarealhostname.
Environment & setup

OS: Mac OS
Database: Postgres
Prisma version: 2.2.0
Node.js version: 12.18.1

Do you get this output just when executing the count()?

Any DB query from that prisma object will do.

Do you have a .env file in your project root as well? We currently have a bug that this file is loaded by the CLI instead of just the prisma/.env as documented. This will be fixed on Monday if that is the reason.

I do have a .env in my project root, but it doesn't contain DATABASE_URL.

And to clarify, I do not have a prisma/.env file.

Exactly, the CLI currently does read the .env in the root although it should not. Can you try if putting the value in there fixes your issue?

Putting an incorrect but well-formed value for DATABASE_URL in .env does indeed remove the error, implying that the root .env is being read.
I'm not sure what this has to do with the issue though. The problem is that DATABASE_URL shouldn't be required at all, rather than where it should be specified.

That is just not supported, as we require a valid schema. You can replace the env("DATABASE_URL") with a nonsense value in the schema.prisma if you want, then no error message should appear and the explicitly defined wvalue will overwrite the nonsense value.

I still need it for introspection, and eventually migrations, locally. I guess I'll just live with setting a nonsense value in production. 🤷♀