More weaviate tests

FYI @hsm207
============================================================================================================ short test summary info ============================================================================================================
FAILED tests/test_langchain_units.py::test_make_add_db[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_zip_add[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_url_add[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_html_add[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_docx_add[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_md_add[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_eml_add[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_simple_eml_add[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_odt_add[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_pptx_add[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_simple_pptx_add[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_epub_add[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_png_add[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_png_add_gpu[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_png_add_gpu_preload[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_png_add_gpu_blip2[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
FAILED tests/test_langchain_units.py::test_simple_rtf_add[weaviate] - TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'
================================================================================== 17 failed, 26 passed, 8 skipped, 1 xpassed, 8 warnings in 501.87s (0:08:21) ==================================================================================

Traceback (most recent call last):
  File "/home/jon/miniconda3/envs/h2ollm/lib/python3.10/concurrent/futures/process.py", line 246, in _process_worker
    r = call_item.fn(*call_item.args, **call_item.kwargs)
  File "/home/jon/h2ogpt/utils.py", line 750, in _traced_func
    return func(*args, **kwargs)
  File "/home/jon/h2ogpt/tests/test_langchain_units.py", line 528, in test_png_add_gpu_blip2
    return run_png_add(captions_model='Salesforce/blip2-flan-t5-xl', caption_gpu=True, db_type=db_type)
  File "/home/jon/h2ogpt/tests/test_langchain_units.py", line 543, in run_png_add
    db = make_db_main(persist_directory=tmp_persistent_directory, user_path=tmp_user_path,
  File "/home/jon/h2ogpt/make_db.py", line 150, in make_db_main
    db = _create_or_update_weaviate_db(sources, use_openai_embedding, add_if_exists, verbose, hf_embedding_model, collection_name)
  File "/home/jon/h2ogpt/make_db.py", line 186, in _create_or_update_weaviate_db
    db = Weaviate(embedding_function=embedding, client=client, by_text=False, index_name=index_name)
TypeError: Weaviate.__init__() got an unexpected keyword argument 'embedding_function'

Also see during pytest:
100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 1/1 [00:00<00:00,  1.23it/s]
0it [00:00, ?it/s]
Exceptions: []
embedded weaviate is already listening on port 6666
FAILED

Seems like weaviate is not shutting down after test completed, which is odd since should be in fork.

Even pycharm showed problems, and db wasn't returned.  Trying tests again after changes

============================================================================================================ short test summary info ============================================================================================================
FAILED tests/test_langchain_units.py::test_make_add_db[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_zip_add[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_url_add[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_html_add[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_docx_add[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_md_add[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_eml_add[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_simple_eml_add[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_odt_add[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_pptx_add[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_simple_pptx_add[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_epub_add[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_png_add[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_png_add_gpu[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_png_add_gpu_preload[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_png_add_gpu_blip2[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
FAILED tests/test_langchain_units.py::test_simple_rtf_add[weaviate] - TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
================================================================================== 17 failed, 26 passed, 8 skipped, 1 xpassed, 8 warnings in 517.44s (0:08:37) ==================================================================================
(h2ollm) jon@pseudotensor:~/h2ogpt$

"""
Traceback (most recent call last):
  File "/home/jon/miniconda3/envs/h2ollm/lib/python3.10/concurrent/futures/process.py", line 246, in _process_worker
    r = call_item.fn(*call_item.args, **call_item.kwargs)
  File "/home/jon/h2ogpt/utils.py", line 750, in _traced_func
    return func(*args, **kwargs)
  File "/home/jon/h2ogpt/tests/test_langchain_units.py", line 580, in test_simple_rtf_add
    db = make_db_main(persist_directory=tmp_persistent_directory, user_path=tmp_user_path,
  File "/home/jon/h2ogpt/make_db.py", line 147, in make_db_main
    db = _create_or_update_weaviate_db(sources, use_openai_embedding, add_if_exists, verbose, hf_embedding_model,
  File "/home/jon/h2ogpt/make_db.py", line 186, in _create_or_update_weaviate_db
    db = Weaviate(embedding=embedding, client=client, by_text=False, index_name=index_name)
TypeError: Weaviate.__init__() missing 1 required positional argument: 'text_key'
"""

@pseudotensor I'll have a look next week. Any chance you can give me permission to push commits to this PR?

============================================================================================================ short test summary info ============================================================================================================
FAILED tests/test_langchain_units.py::test_zip_add[weaviate] - AssertionError: assert 3 == 1
FAILED tests/test_langchain_units.py::test_html_add[weaviate] - AssertionError: assert 4 == 1
FAILED tests/test_langchain_units.py::test_eml_add[weaviate] - AssertionError: assert 4 == 1
FAILED tests/test_langchain_units.py::test_simple_eml_add[weaviate] - assert 4 == 1
FAILED tests/test_langchain_units.py::test_pptx_add[weaviate] - AssertionError: assert 'Presentation' in 'Michelle holds a B.A. in Mathematics and Computer Science from Ursinus College. In her downtime, she enjoys spending quality time with her family and expressing her creativity by playing the bas...
FAILED tests/test_langchain_units.py::test_simple_pptx_add[weaviate] - AssertionError: assert 4 == 1
FAILED tests/test_langchain_units.py::test_epub_add[weaviate] - AssertionError: assert ('happy' in 'Hello World' or 'happiness' in 'Hello World')
FAILED tests/test_langchain_units.py::test_png_add[weaviate] - AssertionError: assert 4 == 1
FAILED tests/test_langchain_units.py::test_png_add_gpu[weaviate] - AssertionError: assert 4 == 1
FAILED tests/test_langchain_units.py::test_png_add_gpu_preload[weaviate] - AssertionError: assert 4 == 1
FAILED tests/test_langchain_units.py::test_png_add_gpu_blip2[weaviate] - AssertionError: assert 4 == 1
FAILED tests/test_langchain_units.py::test_simple_rtf_add[weaviate] - AssertionError: assert 'Microsoft' in 'Light;lue0;ed0lue255;ed0lue255;ed0lue0;ed255lue255;ed255lue0;ed255lue0;ed255lue255;tnbj\n4s18 4s18 21 Sample Rich Text Format Document'
================================================================================== 12 failed, 33 passed, 8 skipped, 1 xpassed, 8 warnings in 550.00s (0:09:09) ==================================================================================
(h2ollm) jon@pseudotensor:~/h2ogpt$

======================================================================================= 47 passed, 8 skipped, 1 xpassed, 8 warnings in 677.17s (0:11:17) ========================================================================================
(h2ollm) jon@pseudotensor:~/h2ogpt$ pytest -s -v tests/test_langchain_units.py

@hsm207 I fixed things probably, but please take a look.

Also see during pytest:
100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 1/1 [00:00<00:00,  1.23it/s]
0it [00:00, ?it/s]
Exceptions: []
embedded weaviate is already listening on port 6666
FAILED

Seems like weaviate is not shutting down after test completed, which is odd since should be in fork.

@pseudotensor the lifetime of an embedded weaviate instance follows the process that spawned it. So, in the context of a test, if the test creates an embedded weaviate instance, then it will be destroyed when the test is over.
For example, running a test script that has these two tests:
import weaviate
from weaviate.embedded import EmbeddedOptions

def test_foo():
    client = weaviate.Client(
    embedded_options=EmbeddedOptions()
    )

def test_bar():
    client = weaviate.Client(
    embedded_options=EmbeddedOptions()
    )

will result in the following output:

======================================================================= test session starts =======================================================================
platform linux -- Python 3.8.13, pytest-7.2.2, pluggy-1.0.0
rootdir: /workspaces/h2ogpt
plugins: xdist-3.2.1, anyio-3.7.0, cov-3.0.0, pythonpath-0.7.4, hypothesis-4.50.8
collected 2 items
../tests/test_demo_weaviate_embedded.py Started /root/.cache/weaviate-embedded: process ID 19235
{"action":"startup","default_vectorizer_module":"none","level":"info","msg":"the default vectorizer modules is set to "none", as a result all new schema classes without an explicit vectorizer setting, will use this vectorizer","time":"2023-06-05T12:07:59Z"}
{"action":"startup","auto_schema_enabled":true,"level":"info","msg":"auto schema enabled setting is set to "true"","time":"2023-06-05T12:07:59Z"}
{"level":"warning","msg":"Multiple vector spaces are present, GraphQL Explore and REST API list objects endpoint module include params has been disabled as a result.","time":"2023-06-05T12:07:59Z"}
{"action":"grpc_startup","level":"info","msg":"grpc server listening at [::]:50051","time":"2023-06-05T12:07:59Z"}
{"action":"restapi_management","level":"info","msg":"Serving weaviate at http://<IP_ADDRESS>:6666","time":"2023-06-05T12:07:59Z"}
{"action":"restapi_management","level":"info","msg":"Shutting down... ","time":"2023-06-05T12:07:59Z"}
{"action":"restapi_management","level":"info","msg":"Stopped serving weaviate at http://<IP_ADDRESS>:6666","time":"2023-06-05T12:07:59Z"}
.Started /root/.cache/weaviate-embedded: process ID 19278
{"action":"startup","default_vectorizer_module":"none","level":"info","msg":"the default vectorizer modules is set to "none", as a result all new schema classes without an explicit vectorizer setting, will use this vectorizer","time":"2023-06-05T12:07:59Z"}
{"action":"startup","auto_schema_enabled":true,"level":"info","msg":"auto schema enabled setting is set to "true"","time":"2023-06-05T12:07:59Z"}
{"level":"warning","msg":"Multiple vector spaces are present, GraphQL Explore and REST API list objects endpoint module include params has been disabled as a result.","time":"2023-06-05T12:07:59Z"}
{"action":"grpc_startup","level":"info","msg":"grpc server listening at [::]:50051","time":"2023-06-05T12:07:59Z"}
{"action":"restapi_management","level":"info","msg":"Serving weaviate at http://<IP_ADDRESS>:6666","time":"2023-06-05T12:07:59Z"}
{"action":"restapi_management","level":"info","msg":"Shutting down... ","time":"2023-06-05T12:07:59Z"}
{"action":"restapi_management","level":"info","msg":"Stopped serving weaviate at http://<IP_ADDRESS>:6666","time":"2023-06-05T12:07:59Z"}
.                                                                                [100%]
======================================================================== 2 passed in 0.73s ========================================================================

Notice that this set of messages:
{"action":"restapi_management","level":"info","msg":"Serving weaviate at [http://<IP_ADDRESS>:6666","time":"2023-06-05T12:07:59Z"}](http://<IP_ADDRESS>:6666%22%2C%22time%22:%222023-06-05t12:07:59Z%22%7D/)
{"action":"restapi_management","level":"info","msg":"Shutting down... ","time":"2023-06-05T12:07:59Z"}
{"action":"restapi_management","level":"info","msg":"Stopped serving weaviate at [http://<IP_ADDRESS>:6666","time":"2023-06-05T12:07:59Z"}](http://<IP_ADDRESS>:6666%22%2C%22time%22:%222023-06-05t12:07:59Z%22%7D/)

appears twice.
Therefore, if you see this message:

embedded weaviate is already listening on port 6666

It means either:

You had spawned embedded weaviate in a separate process that is still running e.g. you opened a python terminal and ran the code to create embeddded weaviate and did not exit the terminal, or

The vector store component is part of a global variable that persist for the entire test session

@pseudotensor the lifetime of an embedded weaviate instance follows the process that spawned it. So, in the context of a test, if the test creates an embedded weaviate instance, then it will be destroyed when the test is over.

Understood, but these test are wrapped in a subprocess fork call, and all tests are called sequentially with pytest (no -n X), so I'd expect every new test to be fully isolated.  The only case when this wouldn't be true is if weaviate launches a process and detatches from the parent.

I wrapped the tests int the wrap_test_forked decorator:
import weaviate
from weaviate.embedded import EmbeddedOptions
from tests.utils import wrap_test_forked

@wrap_test_forked
def test_foo():
    client = weaviate.Client(
    embedded_options=EmbeddedOptions()
    )

@wrap_test_forked
def test_bar():
    client = weaviate.Client(
    embedded_options=EmbeddedOptions()
    )

and the output still repeats 2x. So, we can conclude from this that weaviate does not launch a process and detaches it from the parent, right?

ok

this behavior might be due to weaviate/weaviate-python-client#349. We should upgrade the client once the fix is released.


Supercharge update: Total rewards recieved

For users who are supercharging now, display how many rewards they have claimed in the past.  sum of all previous distributions received in crypto currency (probably 1 stable coin)
Designs: TBA.
More context on slack
ENG:

[ ] Calculate every time screen is open (many network requests potentially) vs caching total and fetching when screen open (more complexity)
[ ] @gnardini has a list of addresses that do yield distributions
[ ] get txs from "yield addresses" to wallet address for every token

@nityarao designs TBC


feat: Add ability to customize Read More button destination in MissingAnnotationEmptyState component

Signed-off-by: Sergey Shevchenko<EMAIL_ADDRESS>Hey, I just made a Pull Request!
I've added the ability to customize the destination link for the Read More button in the MissingAnnotationEmptyState component.
A new prop link was added and it can be empty so it will not break backward compatibility. If the link is not specified then the default link Is used.
Use case:
For some plugins, it will be better to specify the Read More link destination to the documentation page of such plugin. For example, I want to specify such a link for the Prometheus plugin to https://roadie.io/backstage/plugins/prometheus/ or to my internal documentation page in confluence
This fix also addresses some changes related to #3217 IMO

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@Rugvip Updated


Is it possible to return the feature functions?

Thanks for developing a great tool!
I would like to be able to return the feature functions f_i() that are built using penalized B splines.
Is this possible?
I appreciate your help.

@edwardcjohnson hey there!
i think the gam  partial_dependence method might be what you're looking for.
with this method you can evaluate the feature functions on new data points.
if you call the method with X=None it will return the values of the feature function over an evenly sampled grid of points for nice plotting. (you can see some examples in the readme)
please let mw know if this works for you...
-dani

Hi @dswah ,
What I'm looking for is a method that would allow me to return the feature functions themselves (or perhaps a list of tuples where each element of the tuple represents some component of the feature function)?
What i'm interested in is seeing the 'nuts and bolts' of the feature functions so i'd like to see their construction.
Does that make sense?
Thanks!
-Edward

does that help?

This is exactly what I was looking for! Thank you very much for your help.


Correctly sort the version in branch cleaner

What this PR does / why we need it:
The branch cleaner sorts the version considering it string and in string comparison "100" is smaller than "99".  To prevent it this PR, first convert the string to an integer and then perform the comparison.
It will still fail if the major version is 99 and 100, but this will not happen in the near future.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

/kind bug

/lgtm
/approve


Simplify CapabilityRegistry

Improve CapabilityRegistry and surrounding code in a couple of ways

Make CapabilityRegistry an actor
Refactor CapabilityRegistry to duplicate less code
Ensure that SourceKitServer reports all capabilities of SwiftLanguageServer if the client doesn’t support dynamic capability registration. We were missing this for semantic tokens and inlay hits
Add a few doc comments

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test Windows

@swift-ci Please test Windows


Rethink API

Would be nice to make this library simpler to use. I've been thinking an API like this:
use afl;

fn main() {
    // Some setup can happen here

    // Loop that AFL will run
    afl::run(|inputted_string| {
        let _ = some_library::parse_string(inputted_string);
    });
}

inputted_string would be a String. the closure inside afl::run is the only thing that gets run upon every subsequent call by AFL using the deferred init strategy

Another idea here. Something like cargo bench:
#[fuzz]
fn test_fuzz(bytes: Vec<u8>) {
    ...
}

which can be invoked with something like cargo afl-fuzz

Nice! even simpler, I love it.
On Sat, Apr 23, 2016 at 11:44 AM, Corey Farwell<EMAIL_ADDRESS>wrote:

Another idea here. Something like cargo bench:
#[fuzz]fn test_fuzz(bytes: Vec) {
...
}
which can be invoked with something like cargo afl-fuzz
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/frewsxcv/afl.rs/issues/31#issuecomment-213767532

--
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: D1B3 ADC0 E023 8CA6

Note to future self:
rust-quickcheck implements a #[quickcheck] compiler plugin very similar to what I was thinking above.
example of usage
compiler plugin source


chore: dfx release 0.21.0

the tests that are broken will be resolved by https://github.com/dfinity/examples/pull/907

#907 covers this PR. closing.


Refactor DryRunExecutor

Problems Summary
Too many executing methods
See below for a list of DryRunExecutor methods that allow executing dryruns. It is cumbersome and confusing to have so many methods that basically do the same thing. Ideally, it would be nice to have a single method with the following API:
class DryRunExecutor:
    @singledispatch
    @classmethod
    def execute(
            cls: self,
            algod: AlgodClient,
            program: str,
            input: Any,
            *,
            mode: ExecutionMode = ExecutionMode.Application,
            abi_method_signature: Optional[str] = None,
            ... several more params such as sender, sp, is_app_create, accounts ...
        ):
            raise NotImplementedError("Implement execute method")

This makes use of functools singledispatch decorator
Inconsistent abi-type handling
Currently, graviton's dry run execution are inconsistent in how abi-information is handled. Some allow abi_argument_types and abi_return_types to be provided while some also allow abi_method_signature to be provided. The last parameter includes all the information that abi_argument_types and abi_return_types provides and therefore it is confusing to provide all the parameters.
After an investigation into the usage of dry run execution in PyTeal, it became apparent that in all relevant situations, an ABIReturnSubroutine object is available for inspection, and it comes with a method method_signature() which could be used to populate an abi_method_signature parameter for dry run execution.
Action Items
Streamline the dry run execution API by refactoring the dry run executing methods as follows:

[x] remove parameter abi_argument_types
[x] remove parameter abi_return_type
[x] add parameter abi_method_signature
[x] ~make all the current dry run executing methods private~ these have been deleted
[x] ~unify into a single execute() function using @singledispatch and @process.register to dispatch via input's type (Further investigation is required here. It may not be possible given the nesting of possible inputs (list[tuple] ... etc .... We may also prefer a multipledispatch approach taking into account the mode parameter's type. It may also be infeasible to dispatch directly and therefore we might need to match directly and delegate.)~ This didn't totally work out. However, we've unified everything into a run() method, with 2 companion convenience methods run_one() and run_sequence()
[x] prepare a PyTeal PR which adapts to this new API (https://github.com/algorand/pyteal/pull/628)
[ ] refactor supress_abi (not done)

List of dry run executing methods for refactoring

[x] DryRunExecutor.execute_one_dryrun()
[x] DryRunExecutor.dryrun_logicsig()
[x] DryRunExecutor.dryrun_app()
[x] DryRunExecutor.dryrun_logicsig_on_sequence()
[x] DryRunExecutor.dryrun_multiapps_on_sequence()
[x] DryRunExecutor.dryrun_app_pair_on_sequence()
[x] ABIContractExecutor.dryrun_app_on_sequence()

resolving thanks to #45


chore: chrome is a chromium browser; put them in one bullet.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Edge, Brave, Opera, and Vivaldi are all also Chromium-based browsers, so it doesn't really make sense to only group Chrome with Chromium.
src/interface as of right now on the main branch doesn't have any Svelte files in it, so it would be best to make that change a separate pull request, facing the svelte branch. It'll be eventually merged into main.
Kind Regards


[Bug][Console-UI] Conditional Authentication set to off state after click update button.

Download IS6.0.0-alpha3 snapshot
Download AA libraries using adaptive.sh script
Go to Console
Create an app
Go to sign-in method
Click TOTP authentication
Enable Conditional Authentication
Add Role-based Conditional Authentication
Click Update.

Actual Outcome: Conditional Authentication is off
Actual Outcome: Conditional Authentication should be on

This issue is fixed now @piraveena @Thumimku


Add spellcheck="false" attribute to ensure password isnt shared

Advanced spellcheck used by i.e. Chrome or Edge could enable sending sensitive data, like passwords, to servers that should never receive the data. Setting the attribute spellcheck="false" disallows sending said data.
See here or here.

Thanks for reporting!
It appears that this issue only affects websites that provide a "show password" JS widget that temporarily switches the field from type="password" to type="text". Since the Wagtail login form doesn't provide such a widget, this fix is not necessary.


Added retry policy allowing fallback from LOCAL_QUORUM to QUORUM initial...

This retry policy wraps the DowngradingConsistencyRetryPolicy, essentially applying the same logic, EXCEPT when the initial consistency level is set to LOCAL_QUORUM. In that case it first attempts at QUORUM, then falls back to ONE.
The idea is that you can make calls at LOCAL_QUORUM, which will fall back to QUORUM first if needed. The cost of full QUORUM is preferable in some use cases to ONE, where you want to be really sure a write made it. This is especially likely if RF=3 and you've lost two of your local replicas (resulting in the failed LOCAL_QUORUM).  Then if all else fails it goes to ONE.

Can one of the admins verify this patch?

Closing as per Sylvain's comment above: "Retry policies are completely customizable and because of that, we want to ship with a small amount of generic policies and let users have their own more specialized ones."


bug: https://ossinsight.io/analyze/abcd hang

could not fetch user data from api @Mini256

@634750802, We don't have any data about this user, because it will be inactive after 2019. You need to deal with the not found situation on the front end.
gharchive> select count(*) from github_events ge where actor_login = 'abcd';
+----------+
| count(*) |
+----------+
| 0        |
+----------+
1 row in set
Time: 0.054s

need to deal with the not found situation on the front end.

+1


attempt to prevent the robot from falling when it's tall

Consider, test, and implement ways to prevent the robot from falling when it is tall.
potential solutions could include, but are not limited to
cutting to half power at a height threshold
increasing the rate limiting at a threshold or progressively
using the gyroscope or accelerometer and the drive train to actively balance the robot

Use acceleration and vertical gyro? to balance the robot if it tips


Remove xvfb for saucelabs. Use wct instead of polymer-cli

This change is

based on this proposed change in skeleton : https://github.com/vaadin/vaadin-element-skeleton/pull/77

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 1 files at r1.
Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from Reviewable


Documentation with example

Hi,
I'm really poor in understanding how it works from the documentation. Could you explain it with an example ? And also I would like to know whether we need to do this process for ELB or for server domains.
For example,
Domain name: api.myapp.com (which is registered through different DNS provider, not route53)
ELB Domain: app-prod-web-987654xxxxx.us-west-2.elb.amazonaws.com (A Record)

letsencrypt-aws currently requires you to have DNS configured through route-53

Okay fine. At least provide an example for configuring with Route-53. Instead of just "string, integer" like that..


filter: exposed setSni() function to Lua for setting SNI value for upstream connections

This PR exposes a new method called setSni() in the LUA filter to dynamically set the SNI value from the LUA block. Currently, the auto_sni() only looks at the Host/Authority header to set this value and in our use-case we want to use a different header for setting the SNI while sending requests to the upstream clusters.
Commit Message: exposed a new setSni() function to Lua for setting SNI value for upstream connections.
Additional Description: Added a new function so that SNI value can be set dynamically from the LUA's envoy_on_request() block as auto_sni() only supports setting the Host/Authority header value as SNI currently.
Risk Level: Low
Testing: Unit Tests, Integration Tests
Docs Changes: Added setSni() method description in LUA docs.
Release Notes: Added
Platform Specific Features: N/A
Signed-off-by: Rohit Agrawal<EMAIL_ADDRESS>

@agrawroh Thank you for your contribution! I agree with why this feature is needed. But I have one question. Why we should add this support only for lua filter? I think that it will be better to have auto_sni arbitrary header support. WDYT? cc @lizan

I can also open up another small PR to add the arbitrary header support to auto_sni.

I can also open up another small PR for adding the arbitrary header support to auto_sni.

Cool. If we have auto_sni arbitrary header support, we no longer need lua specific setSni feature.

I can also open up another small PR for adding the arbitrary header support to auto_sni.

Cool. If we have auto_sni arbitrary header support, we no longer need lua specific setSni feature.

@Shikugawa I opened https://github.com/envoyproxy/envoy/pull/17995

With #17995 merged, do we still need this?

With #17995 merged, do we still need this?

No, I'll close it.


Build Landing Page

Follow the figma linked below to build the map page. All scaling should be dynamic to fit with any phone size. Build a page to divert between mentor login and hacker login. The login as mentor button should bring you to the second page, the "continue as hacker" button should bring you to the main app. This page should pop up each time you reopen the app. After a mentor has logged in it should pop them to the rest of the app.
You do not need to link to the page for now, include screenshots of the completed page in a reply to this issue when completed.
If you have any questions reply in this thread or dm me on discord. This should be completed by next Tuesday.
Figma: https://www.figma.com/file/UyW0Ex23gCO7cZvEb2HVfn/HackRPI-2024-Mobile-Figma?type=design&node-id=31%3A47&mode=design&t=C9i7Z0628zacMgCa-1

The X should use an icon from here: https://fontawesome.com/icons/x?f=classic&s=solid


[Question][client] 如何配置参数控制申请yarn资源的Task Manager 数量

Search before asking

[X] I had searched in the issues and found no similar question.

[X] I had googled my question but i didn't get any help.

[X] I had read the documentation: ChunJun doc but it didn't help me.

Description
jobmanager.memory.process.size
taskmanager.memory.process.size
taskmanager.cpu.cores
taskmanager.numberOfTaskSlots

这几个参数怎么配置能控制Task Manager ，改了很多次参数配置，Task Manager 的数量不知道是怎么推算出来的，配置了好几个就出来1个或者2、3个

Code of Conduct

[X] I agree to follow this project's Code of Conduct

完整参数：
sh bin/chunjun-yarn-perjob.sh -job script/hz_jzjbxx.json -jobName hz_jzjbxx -confProp  "{"jobmanager.memory.process.size":"2048m","taskmanager.memory.process.size":"13926m","taskmanager.numberOfTaskSlots":"16","yarn.containers.vcores":"8","parallelism":"104","yarn.application.name":"123456"}"
经过测试：  yarn的可用内存/taskmanager.memory.process.size  跟   parallelism/taskmanager.numberOfTaskSlots 这2个值哪个小取哪个


LUN-121: random order of vocabulary

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword LUN.
This PR continues the work from https://github.com/digitalfabrik/lunes-app/pull/166. I tried to implement all feedback I got.

Regarding the tests, I'm not sure if mocking the return value of Math.random is the right approach, as it isn't that straight forward and finding the right return value can be problematic, especially with growing test suits (https://github.com/digitalfabrik/lunes-app/pull/166/commits/d6e597d093fa6ee6c811a3eed416cabae077d7ab). Also, mocking Math.random inside WordChoiceExercise.spec.tsx leads to following error, which I am unablet to work out. (the other test suites run fine):
<--- Last few GCs --->

[10204:0000023D89EF3B20]    86503 ms: Mark-sweep 4299.2 (4378.5) -> 4044.1 (4123.5) MB, 4198.3 / 0.0 ms  (average mu = 0.231, current mu = 0.049) allocation failure scavenge might not succeed
[10204:0000023D89EF3B20]    92582 ms: Mark-sweep 4427.0 (4506.1) -> 4171.8 (4251.3) MB, 5662.5 / 0.0 ms  (average mu = 0.147, current mu = 0.069) allocation failure GC in old space requested

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 00007FF60E0E30AF v8::internal::CodeObjectRegistry::~CodeObjectRegistry+112511
 2: 00007FF60E072216 DSA_meth_get_flags+65542
 3: 00007FF60E0730CD node::OnFatalError+301
 4: 00007FF60E9A4B6E v8::Isolate::ReportExternalAllocationLimitReached+94
 5: 00007FF60E98F09D v8::SharedArrayBuffer::Externalize+781
 6: 00007FF60E83268C v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1468
 7: 00007FF60E82F7C4 v8::internal::Heap::CollectGarbage+4244
 8: 00007FF60E82D140 v8::internal::Heap::AllocateExternalBackingStore+2000
 9: 00007FF60E851A76 v8::internal::Factory::NewFillerObject+214
10: 00007FF60E584B6A v8::internal::DateCache::Weekday+1466
11: 00007FF60EA32541 v8::internal::SetupIsolateDelegate::SetupHeap+494417
12: 0000023D8C365F4D

Process finished with exit code 134

Any suggestions on how to approach the randomization inside the tests? I think just disabling randomization inside the tests should be fine, shouldn't it?


az aks get-credentials error

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az aks get-credentials
Errors:
The command failed with an unexpected error. Here is the traceback:
API version 2022-04-01 does not have operation group 'managed_clusters'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 663, in execute
    raise ex
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
    result = cmd_copy(params)
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/command_operation.py", line 112, in handler
    client = self.client_factory(self.cli_ctx, command_args) if self.client_factory else None
  File "/usr/lib/python3/dist-packages/azure/cli/command_modules/acs/_client_factory.py", line 22, in cf_managed_clusters
    return get_container_service_client(cli_ctx).managed_clusters
  File "/usr/lib/python3/dist-packages/azure/mgmt/containerservice/_container_service_client.py", line 492, in managed_clusters
    raise ValueError("API version {} does not have operation group 'managed_clusters'".format(api_version))
ValueError: API version 2022-04-01 does not have operation group 'managed_clusters'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az aks get-credentials --resource-group {} -n {}

Expected Behavior
Environment Summary
Linux-5.17.0-2-amd64-x86_64-with-glibc2.33, Debian GNU/Linux bookworm/sid
Python 3.10.4
Installer: DEB

azure-cli 2.37.0

Extensions:
azure-devops 0.24.0

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.0.0

Additional Context

route to CXP team

@wkalt Thanks for reaching out to us and sharing this feedback.
Looking at the below details, This is not the official Azure CLI published by Microsoft. Please see https://github.com/Azure/azure-cli/issues/19640.

Linux-5.17.0-2-amd64-x86_64-with-glibc2.33, Debian GNU/Linux bookworm/sid
Python 3.10.4
Installer: DEB

For now, please follow https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-linux?pivots=apt to install Azure CLI on stable/GA versions of Debian, like 11 Bullseye, instead of sid. Hope this helps.
For more information refer this: https://wiki.debian.org/DebianUnstable

Sid is forever doomed to being unstable.

Tagging similar issue here: https://github.com/Azure/azure-cli/issues/21254

@wkalt I wanted to do quick follow-up to check if you had a chance to look at my above comment. Please let us know if you need any further assistance on this. Awaiting your reply.

@wkalt The action is currently pending on you to follow the above action plan. We will now proceed with closure of this GitHub issue. If you need any further assistance on this issue in future, please feel free to reopen this thread. We would be happy to help.


Clone instructions do not respect SSH_DOMAIN variable when set as an environment variable

Description
I'm running with the docker image and have the following set as environment variables. The idea being to have a separate domain for ssh cloning of repositories as the primary domain goes via Cloudflare proxy (and therefore blocks the SSH protocol).
# file: docker-compose.yaml
gitea:
    image: gitea/gitea
    container_name: gitea
    hostname: git.mydomain.tld
    restart: always
    environment:
      - USER_UID=1000
      - USER_GID=1000
      - DB_TYPE=postgres
      - DB_HOST=db:5432
      - DB_NAME=gitea
      - DB_USER=gitea
      - DB_PASSWD=gitea
      # Customise
      - GITEA____APP_NAME="My Gitea Instance"
      - GITEA__server__DOMAIN="git.mydomain.tld"
      - GITEA__server__ROOT_URL="https://git.mydomain.tld"
      - GITEA__server__SSH_DOMAIN="clone.mydomain.tld"
    networks:
      - gitea
    volumes:
      - ./data/gitea:/data
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    depends_on:
      - db
      - redis
      - minio

On creating a new repository however I'm getting presenting with a SSH clone url which reflects the DOMAIN as opposed to the SSH_DOMAIN.
On investigation it seems as though this environment variable has not been respected and passed through to the underlying app.ini. If login into the container and inspect the file it shows the following:
# file: /data/gitea/conf/app.ini
...
[server]
APP_DATA_PATH    = /data/gitea
DOMAIN           = git.mydomain.tld
SSH_DOMAIN       = git.mydomain.tld
...

If I manually edit this file inside the container to adjust the SSH_DOMAIN variable and restart it then the setting is respected.
Gitea Version
1.16.5 built with GNU Make 4.3, go1.18 : bindata, timetzdata, sqlite, sqlite_unlock_notify
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Gitea is running with docker and docker-compose using image: gitea/gitea
Database
PostgreSQL

Voting up this issue.
Neither [server] DOMAIN nor [server] SSH_DOMAIN.
Version 1.17.1

Voting up this issue.
Neither [server] DOMAIN nor [server] SSH_DOMAIN.
Version 1.18.3+0

The only way this could not be working is if you're running the install page.
Why are you running the install page on every container restart?


TypeError: from_id() missing 1 required positional argument: 'service' in Session.from_id with 0.15.0

Describe the bug
This code started failing with version 0.15.0:
>       session = Session.from_id(session_id, backend=device)
E       TypeError: from_id() missing 1 required positional argument: 'service'

Steps to reproduce
Call Session.from_id without a service kwarg.
Expected behavior
What worked before should continue to work unless it's a major version breaking change.
Suggested solutions
Support the old interface.
Additional Information

qiskit-ibm-runtime version: 0.15.0
Python version: 3.8
Operating system: Ubuntu Focal

In this usage:

backend=device

device is a string name of a backend.

From the release notes I see this:

The backend parameter in from_id() is being deprecated because sessions do not support multiple backends. Additionally, the service parameter is no longer optional.

How is that a bug fix and not something that goes through a deprecation period first since it's an interface change?

There seems to be a related regression with this. It used to be that calling Session.from_id() with an invalid session ID would return an error message with the 4318 error code, bug I'm not seeing that now.
I have a very simple test like this:
def test_using_arbitrary_session_id_should_fail(service, device):
    session_id = 'test_using_arbitrary_session_id_should_fail'
    session = Session.from_id(session_id, service, backend=device)
    with pytest.raises(Exception) as ex:
        run_job(session=session)
        # https://internal-docs.quantum-computing.ibm.com/system-architecture/errors.html#c4318
        assert '4318' in str(ex)

After passing service into from_id() to workaround this issue, I'm getting a failure on the assertion because 4318 isn't in the error message - is that a regression in the client or the server? I can revert back to qiskit-ibm_runtime<0.15.0 to confirm.

is that a regression in the client or the server? I can revert back to qiskit-ibm_runtime<0.15.0 to confirm.

It's another regression in 0.15.0, it works fine in 0.14.0:
$ TEST_DEVICE=fake_backend1 tox -e staging -- tests/test_sessions.py::test_using_arbitrary_session_id_should_fail
GLOB sdist-make: /home/osboxes/ibmq/iqp-channel-e2e-tests/setup.py
staging recreate: /home/osboxes/ibmq/iqp-channel-e2e-tests/.tox/staging
staging installdeps: pytest, qiskit-ibm-provider, qiskit-ibm-runtime>=0.13,<0.15
staging inst: /home/osboxes/ibmq/iqp-channel-e2e-tests/.tox/.tmp/package/1/iqp-channel-e2e-tests-0.0.1.zip
staging installed: certifi==2023.7.22,cffi==1.16.0,charset-normalizer==3.3.2,cryptography==41.0.5,dill==0.3.7,exceptiongroup==1.1.3,ibm-cloud-sdk-core==3.18.0,ibm-platform-services==0.47.0,idna==3.4,iniconfig==2.0.0,iqp-channel-e2e-tests==0.0.1,mpmath==1.3.0,numpy==1.24.4,packaging==23.2,pbr==6.0.0,pluggy==1.3.0,ply==3.11,psutil==5.9.6,pycparser==2.21,PyJWT==2.8.0,pyspnego==0.10.2,pytest==7.4.3,python-dateutil==2.8.2,qiskit==0.45.0,qiskit-ibm-provider==0.7.2,qiskit-ibm-runtime==0.14.0,qiskit-terra==0.45.0,requests==2.31.0,requests-ntlm==1.2.0,rustworkx==0.13.2,scipy==1.10.1,six==1.16.0,stevedore==5.1.0,symengine==0.9.2,sympy==1.12,tomli==2.0.1,typing-extensions==4.8.0,urllib3==2.1.0,websocket-client==1.6.4,websockets==12.0
staging run-test-pre: PYTHONHASHSEED='1052335426'
staging run-test: commands[0] | pytest -v tests/test_sessions.py::test_using_arbitrary_session_id_should_fail
==================================================================================== test session starts ====================================================================================
platform linux -- Python 3.8.10, pytest-7.4.3, pluggy-1.3.0 -- /home/osboxes/ibmq/iqp-channel-e2e-tests/.tox/staging/bin/python
cachedir: .tox/staging/.pytest_cache
rootdir: /home/osboxes/ibmq/iqp-channel-e2e-tests
configfile: tox.ini
collected 1 item

tests/test_sessions.py::test_using_arbitrary_session_id_should_fail
-------------------------------------------------------------------------------------- live log setup ---------------------------------------------------------------------------------------
""2023-11-17 12:50:37" [    INFO] getting service (conftest.py:28)"
""2023-11-17 12:50:43" [    INFO] got service (conftest.py:33)"
PASSED                                                                                [100%]

===================================================================================== warnings summary ======================================================================================
.tox/staging/lib/python3.8/site-packages/qiskit/utils/algorithm_globals.py:170
  /home/osboxes/ibmq/iqp-channel-e2e-tests/.tox/staging/lib/python3.8/site-packages/qiskit/utils/algorithm_globals.py:170: DeprecationWarning: The class ``qiskit.utils.algorithm_globals.QiskitAlgorithmGlobals`` is deprecated as of qiskit 0.45.0. It will be removed no earlier than 3 months after the release date. This algorithm utility has been migrated to an independent package: https://github.com/qiskit-community/qiskit-algorithms. You can run ``pip install qiskit_algorithms`` and import ``from qiskit_algorithms.utils`` instead.
    algorithm_globals = QiskitAlgorithmGlobals()

.tox/staging/lib/python3.8/site-packages/qiskit/utils/algorithm_globals.py:49
  /home/osboxes/ibmq/iqp-channel-e2e-tests/.tox/staging/lib/python3.8/site-packages/qiskit/utils/algorithm_globals.py:49: DeprecationWarning: The property ``qiskit.utils.algorithm_globals.QiskitAlgorithmGlobals.num_processes`` is deprecated as of qiskit 0.45.0. It will be removed no earlier than 3 months after the release date. This algorithm utility belongs to a legacy workflow and has no replacement.
    self.num_processes = settings.get("num_processes", QiskitAlgorithmGlobals.CPU_COUNT)

.tox/staging/lib/python3.8/site-packages/qiskit/utils/algorithm_globals.py:120
  /home/osboxes/ibmq/iqp-channel-e2e-tests/.tox/staging/lib/python3.8/site-packages/qiskit/utils/algorithm_globals.py:120: DeprecationWarning: The property ``qiskit.utils.algorithm_globals.QiskitAlgorithmGlobals.num_processes`` is deprecated as of qiskit 0.45.0. It will be removed no earlier than 3 months after the release date. This algorithm utility belongs to a legacy workflow and has no replacement.
    parallel.CPU_COUNT = self.num_processes

.tox/staging/lib/python3.8/site-packages/qiskit/qpy/binary_io/circuits.py:27
  /home/osboxes/ibmq/iqp-channel-e2e-tests/.tox/staging/lib/python3.8/site-packages/qiskit/qpy/binary_io/circuits.py:27: PendingDeprecationWarning: The qiskit.extensions module is pending deprecation since Qiskit 0.45.0. It will be deprecated in a following release, no sooner than 3 months after the 0.45.0 release.
    from qiskit import extensions

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=============================================================================== 1 passed, 4 warnings in 7.59s ===============================================================================
__________________________________________________________________________________________ summary __________________________________________________________________________________________
  staging: commands succeeded
  congratulations :)

I'll revert the change and do a patch release 0.15.1


Consider removing or changing the "open issues" message

Verification

[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

Provide a detailed description of the proposed feature
When a build error occurs, we print a list of open issues that happen that have the formula's name in it:
https://github.com/Homebrew/brew/blob/c5f4d040a7d8a405097abb1d881d25138171372d/Library/Homebrew/exceptions.rb#L543-L546
While this is sometimes useful, it's not guaranteed these issues, and in particular pull requests, are actually relevant.
Unfortunately, people treat this as the gospel and will comment on PRs pushing us to get a move on. While a gauge of how widespread an issue can be useful, there's a lot of the time where the issue the user experienced is not actually relevant to what the PR is solving.
We should either make it much more clearer that the issues & PRs may not be relevant, or just remove it entirely.
What is the motivation for the feature?
One too many occurrences
How will the feature be relevant to at least 90% of Homebrew users?
Less maintainer stress on tricky PRs -> better project health
What alternatives to the feature have been considered?
Ignore the comments and move on

Unfortunately, people treat this as the gospel and will comment on PRs pushing us to get a move on. While a gauge of how widespread an issue can be useful, there's a lot of the time where the issue the user experienced is not actually relevant to what the PR is solving.

Would it be better if this only output issues?

We should either make it much more clearer that the issues & PRs may not be relevant, or just remove it entirely.

Agreed and not opposed to removing this. It also feels like most (all?) build errors are now from source which we don't technically support anyway.

Would it be better if this only output issues?

Probably. It's PRs that are the annoying ones.

It also feels like most (all?) build errors are now from source which we don't technically support anyway.

I think so.

Probably. It's PRs that are the annoying ones.

Cool could just drop those for now I reckon then.


No context available. ns.run() or ns.bind() must be called first

{     "status": 500,     "errstr": "No context available. ns.run() or ns.bind() must be called first.",     "data": "{\"errorMsg\":\"No context available. ns.run() or ns.bind() must be called first.\",\"stack\":\"Error: No context available. ns.run() or ns.bind() must be called first.    at Namespace.set (/xxx/node_modules/cls-hooked/context.js:36:11)    at Object.exports.setEntityManagerForConnection (/xxx/node_modules/typeorm-transactional-cls-hooked/src/common.ts:40:14)    at Task.<anonymous> (/xxx/node_modules/typeorm-transactional-cls-hooked/src/Transactional.ts:46:11)    at step (/xxx/node_modules/typeorm-transactional-cls-hooked/dist/Transactional.js:32:23)    at Object.next (/xxx/node_modules/typeorm-transactional-cls-hooked/dist/Transactional.js:13:53)    at /xxx/node_modules/typeorm-transactional-cls-hooked/dist/Transactional.js:7:71    at Promise._execute (/xxx/node_modules/thinkjs/node_modules/bluebird/js/release/debuggability.js:272:9)    at Promise._resolveFromExecutor (/xxx/node_modules/thinkjs/node_modules/bluebird/js/release/promise.js:473:18)    at new Promise (/xxx/node_modules/thinkjs/node_modules/bluebird/js/release/promise.js:77:14)    at __awaiter (/xxx/node_modules/typeorm-transactional-cls-hooked/dist/Transactional.js:3:12)    at transactionCallback (/xxx/node_modules/typeorm-transactional-cls-hooked/src/Transactional.ts:45:72)    at EntityManager.<anonymous> (/xxx/src/entity-manager/EntityManager.ts:138:34)    at step (/xxx/node_modules/tslib/tslib.js:133:27)    at Object.next (/xxx/node_modules/tslib/tslib.js:114:57)    at fulfilled (/xxx/node_modules/tslib/tslib.js:104:62)    at tryCatcher (/xxx/node_modules/thinkjs/node_modules/bluebird/js/release/util.js:16:23)    at Promise._settlePromiseFromHandler (/xxx/node_modules/thinkjs/node_modules/bluebird/js/release/promise.js:502:31)    at Promise._settlePromise (/xxx/node_modules/thinkjs/node_modules/bluebird/js/release/promise.js:559:18)    at Promise._settlePromise0 (/xxx/node_modules/thinkjs/node_modules/bluebird/js/release/promise.js:604:10)    at Promise._settlePromises (/xxx/node_modules/thinkjs/node_modules/bluebird/js/release/promise.js:683:18)    at Async._drainQueue (/xxx/node_modules/thinkjs/node_modules/bluebird/js/release/async.js:138:16)    at Async._drainQueues (/xxx/node_modules/thinkjs/node_modules/bluebird/js/release/async.js:148:10)    at Immediate.Async.drainQueues [as _onImmediate] (/xxx/node_modules/thinkjs/node_modules/bluebird/js/release/async.js:17:14)    at processImmediate (timers.js:637:19)\"}" }
Is there someone can help me?

Hello,
Seems you did not initialize the context
See
https://github.com/odavid/typeorm-transactional-cls-hooked/blob/master/README.md#initialization


[AutoPR batch/data-plane] Update documentation of Batch data plane swagger.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2885

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/1660


Ability to force browser session quit

Coverage increased (+0.03%) to 81.413% when pulling 01a40f13ab6ad68249e30b40136bf09a5b5af4c9 on feature/allow.force.free into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

Coverage increased (+0.03%) to 81.413% when pulling 01a40f13ab6ad68249e30b40136bf09a5b5af4c9 on feature/allow.force.free into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

Coverage increased (+0.03%) to 81.413% when pulling 01a40f13ab6ad68249e30b40136bf09a5b5af4c9 on feature/allow.force.free into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

Coverage increased (+0.03%) to 81.413% when pulling 01a40f13ab6ad68249e30b40136bf09a5b5af4c9 on feature/allow.force.free into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

Coverage increased (+0.03%) to 81.413% when pulling 01a40f13ab6ad68249e30b40136bf09a5b5af4c9 on feature/allow.force.free into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

@eGavr @sipayRT смотреть можно только на последний коммит, остальное - es6 и небольшой рефакторинг тестов

/ok


Table display in member's page

Display all tables of the event in the member's page upon login.

closed because #53 is merged to master successfully


[Task]add apache and alibaba sdk examples #3925

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #4199 (9ec309c) into master (af3a590) will decrease coverage by 0.35%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #4199      +/-   ##
============================================
- Coverage     70.48%   70.13%   -0.36%
+ Complexity     7229     7173      -56
============================================
  Files           969      969
  Lines         27033    27024       -9
  Branches       2407     2404       -3
============================================
- Hits          19054    18952     -102
- Misses         6522     6612      +90
- Partials       1457     1460       +3

Impacted Files
Coverage Δ

...n/httpclient/exception/ShenyuTimeoutException.java
0.00% <0.00%> (-33.34%)
:arrow_down:

...controller/ShenyuClientHttpRegistryController.java
77.77% <0.00%> (-22.23%)
:arrow_down:

...he/shenyu/common/timer/HierarchicalWheelTimer.java
68.00% <0.00%> (-18.00%)
:arrow_down:

...va/org/apache/shenyu/common/timer/TimingWheel.java
73.80% <0.00%> (-16.67%)
:arrow_down:

...ava/org/apache/shenyu/admin/utils/SessionUtil.java
78.94% <0.00%> (-15.79%)
:arrow_down:

...ache/shenyu/plugin/grpc/cache/GrpcClientCache.java
87.50% <0.00%> (-12.50%)
:arrow_down:

...ruptor/RegisterClientServerDisruptorPublisher.java
52.94% <0.00%> (-11.77%)
:arrow_down:

...a/org/apache/shenyu/common/utils/VersionUtils.java
35.71% <0.00%> (-10.72%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
54.25% <0.00%> (-9.58%)
:arrow_down:

.../org/apache/shenyu/common/timer/TimerTaskList.java
74.72% <0.00%> (-8.80%)
:arrow_down:

... and 45 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Clean up compiler warnings

@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.


311 add spinner and disable the upload button when upload files

We may need the same thing for "update" the file. This could be another task next. Thanks!


OpenSSL OCSP responder failing when request comes from MS Remote Desktop Service (Remoteapp)

Here is my scenario:
I have a root and intermediate CA in CentOS, with OpenSSL 1.0.2k-fips. I also set up a OCSP responder in the intermediate CA, to respond the status of issued certificates. I also have a Windows 2012 R2 server with Remote Desktop Services enabled. I issued a certificate for it using my OpenSSL intermediate CA.
When I use OpenSSL tools to check the status of the certificate, it returns with Response verify OK, certificate good.
$ openssl ocsp -CAfile chain.mydomain.crt.pem -url http://myfqdn-ocsp-responder:8888 -resp_no_certs -issuer int.mydomain.crt.pem -cert server.mydomain.crt.pem
Response verify OK
server.mydomain.crt.pem: good
        This Update: Oct 10 16:44:50 2018 GMT

When I use the RDP connection (either the RDP file itself or the RemoteApp webaccess, I get A revocation check could not be performed for the certificate error, although it lets me go through and continue. The Certificate has the OCSP information correctly, though.

But that´s really annoying for the users and I wanted to get rid of this error. In the OCSP responder server I get a couple of Invalid request errors and the log.tx has Responder Error: malformedrequest (1) message.
The OCSP responder was started with:
# openssl ocsp -index ../index.txt -port 8888 -rsigner certs/ocspserver.mydomain.crt.pem -rkey private/ocspserver.mydomain.key.pem -CA ../certs/int.mydomain.crt.pem -text -ignore_err -out log.txt&
On the OCSP responder I captured the traffic, and to my surprise it seems OpenSSL and MS RDP check the certificate status in very different ways:
For OpenSSL checking:
OCSP Request is sent, it has inside the hashAlgorithm, issuerNameHash, issuerKeyHash and serialNumber.
It receives back a OCSP Response with responseStatus: successful (0)
Wireshark capture image: request

Wireshark capture image: response

For MS RDP checking:
After the regular 3way handshake, the server sends an HTTP GET where the User-Agent is Microsoft-CryptoAPI/6.3 and the Full request URI is http://ocspserver.mydomain:8888/<a bunch of apparently random characters>
To that the OCSP responds with an OCSP Response packet with responseStatus: malformedRequest (1)
Following that event the server establishes a new 3way handshake, and now sends a OCSP Request, very similar to the one sent by OpenSSL. The OCSP responder responds with a OCSP Response with responseStatus: successful (0). That back and fourth is done 3 times.
Wireshark capture back and fourth image

Wireshark 1st request: server -> OCSP responder (HTTP GET)

Wireshark 1st response: OCSP responder -> server (OCSP)

Wireshark 2nd request: server -> OCSP responder (OCSP)

Wireshark 2nd response: OCSP responder -> server (OCSP)

Apparently the second request by MS RDP, which gets a successful response, is ignored.
Does anyone know why this is happening?
Thank you,

1.0.2 version is unsupported. Please open a new issue if you can reproduce the problem with 1.1.1 or 3.0 versions.


Added to_string_mut and to_string_mut_pretty

/// Serialize the given data structure as JSON into the pre-existing [`String``].
///
/// # Errors
///
/// Serialization can fail if `T`'s implementation of `Serialize` decides to
/// fail, or if `T` contains a map with non-string keys.
#[inline]
#[cfg(feature = "std")]
#[cfg_attr(docsrs, doc(cfg(feature = "std")))]
pub fn to_string_mut<T>(s: &mut String, value: &T) -> Result<()>
where
    T: ?Sized + Serialize,
{
    // to_writer() guarantees that it feeds only valid UTF-8 to the writer.
    let buf = unsafe { s.as_mut_vec() };
    let mut writer = std::io::Cursor::new(buf);
    to_writer(&mut writer, value)
}

/// Serialize the given data structure as pretty-printed JSON into the pre-existing [`String`].
///
/// # Errors
///
/// Serialization can fail if `T`'s implementation of `Serialize` decides to
/// fail, or if `T` contains a map with non-string keys.
#[inline]
#[cfg(feature = "std")]
#[cfg_attr(docsrs, doc(cfg(feature = "std")))]
pub fn to_string_mut_pretty<T>(s: &mut String, value: &T) -> Result<()>
where
    T: ?Sized + Serialize,
{
    // to_writer_pretty() guarantees that it feeds only valid UTF-8 to the writer.
    let buf = unsafe { s.as_mut_vec() };
    let mut writer = std::io::Cursor::new(buf);
    to_writer_pretty(&mut writer, value)
}

Ready for the review!


"module 'rainbow-delimiters' not found"

i'm setting up something wrong?

There is no setup function, it's a plug & play plugin (as Vim plugins are meant to be). You just install it an you are good to go. It will pick up your settings automatically. But from the looks of the error message it looks like the plugin cannot be found. How did you install it?

i'm installing using Lazy.

What do you get when you execute :lua =require 'rainbow-delimiters'? You should get a table that looks like this:
{
  disable = <function 1>,
  enable = <function 2>,
  hlgroup_at = <function 3>,
  strategy = {
    global = {
      on_attach = <function 4>,
      on_detach = <function 5>,
      on_reset = <function 6>
    },
    ["local"] = {
      on_attach = <function 7>,
      on_detach = <function 8>,
      on_reset = <function 9>
    },
    noop = {
      on_attach = <function 10>,
      on_detach = <function 11>,
      on_reset = <function 12>
    }
  },
  toggle = <function 13>
}

yep!

OK, then you should be good to go. Replace the line
local rainbow_delimiters = require("rainbow-delimiters").setup()

with
local rainbow_delimiters = require("rainbow-delimiters")

The only reason you need that table in the first place is to reference the two strategy objects. Otherwise you would not need it.

I fixed it a few minutes ago, but thanks
Em sáb, 2 de set de 2023 06:26, Alejandro Sanchez @.***>
escreveu:

OK, then you should be good to go. Replace the line
local rainbow_delimiters = require("rainbow-delimiters").setup()
with
local rainbow_delimiters = require("rainbow-delimiters")
The only reason you need that table in the first place is to reference the
two strategy objects. Otherwise you would not need it.
—
Reply to this email directly, view it on GitHub
https://github.com/HiPhish/rainbow-delimiters.nvim/issues/34#issuecomment-1703777559,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVZ7UI2ZEH5RXEPZYSLYA73XYL3TDANCNFSM6AAAAAA4IOIFLU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Allow patients with sent pledges to be marked urgent again

I rule and have completed some work on Case Manager that's ready for review!
A few funds have reported that postgres caused a slight change in how urgency works, and that they can no longer mark patients with sent pledges urgent. That was original intent, but funds are used to the not-quite-right version, so this PR implements the not-quite-right version. (I think the source of this is callbacks working slightly differently in activerecord than in mongoid, but exact details aren't that important, I don't think.)
This pull request makes the following changes:

remove pledge_sent from unmark-urgency criteria

no view changes
It relates to the following issue #s:

Fixes #2262

For reviewer:

Adjust the title to explain what it does for the notification email to the listserv.
Tag this PR:

feature if it contains a feature, fix, or similar. This is anything that contains a user-facing fix in some way, such as frontend changes, alterations to backend behavior, or bug fixes.
dependencies if it contains library upgrades or similar. This is anything that upgrades any dependency, such as a Gemfile update or npm package upgrade.

If it contains neither, no need to tag this PR.

Codecov Report

Merging #2264 (680c60f) into main (18716f5) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #2264   +/-   ##
=======================================
  Coverage   96.25%   96.25%
=======================================
  Files          79       79
  Lines        1655     1655
=======================================
  Hits         1593     1593
  Misses         62       62

Impacted Files
Coverage Δ

app/models/concerns/urgency.rb
93.75% <100.00%> (ø)

Continue to review full report at Codecov.

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


fix default end silence timeout and collectonresult

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Communication.CallAutomation


"not enough memory" for downloaded interrogator

Hello,
I decided to try the
blip2-opt-6.7b-coco
interrogator and it downloaded a large dataset

when it then tried to run on my directory of files, it apparently ran out of memory:
File "C:\Users\user\AppData\Local\Programs\Python\Python310\lib\site-packages\torch\nn\modules\linear.py", line 96, in init
self.weight = Parameter(torch.empty((out_features, in_features), **factory_kwargs))
RuntimeError: [enforce fail at ..\c10\core\impl\alloc_cpu.cpp:72] data. DefaultCPUAllocator: not enough memory: you tried to allocate 268435456 bytes.
I have 64 GB of system RAM and over 30GB free, so this made me wonder if my GPU was being used.  To that point, I have two RTX-3090 cards (24GB VRAM each), but that obviously wouldn't work for a larger memory need without some sort of active memory manager.
Is there some sort of additional headroom needed for the memory allocation?
Thanks.

I closed various apps and services, such that 51GB of RAM was available, which enabled loading the blip2-opt-6.7b-coco model without any errors.
Summary: there are no free lunches here, you need enough RAM to load any desired models.


Incorrect root detection

I use last version 5.1 and webpack dev server with these settings
devServer: {         contentBase: path.join(__dirname, "build"),         compress: true,         host: "<IP_ADDRESS>",         disableHostCheck: true,         port: 9000,         historyApiFallback: true     }
I init Navigo with default parameters (root= null). In previous version 4.8 after reload page Navigo detects root path well and show me right page. But now, after page reload, it shows me my home page again.
For example when i start page with URL "http://localhost:9000/schedule/3304" it thinks that root path is "/schedule/3304". But it is not correct.
I think this function has error:
_getRoot: function () {     if (this.root !== null) return this.root;     this.root = root(this._cLoc().split('?')[0], this._routes);     return this.root;   },
UPD: To fix this problem i should init Navigo with first parameter location.origin. I think u can add it to code to fix it too.

Finding the root URL was always tricky. The 5.x versions actually have a better route matching but maybe that part with guessing the root is not working the same way. I'm considering making that root parameter mandatory and we always have to provide it. In most of the cases the developer knows where the app is located.
Can you please post here your route definitions so I can reproduce your problem.
P.S.
I don't want to rely on location.origin because as far as I can see it is not supported everywhere.

It can be used in most modern browsers, i think.
My routes are very simple:
router.on('/session/:sessionId', (parameters) => this.executeController(SessionIndexController, parameters));
router.on('/schedule/:filmId', (parameters) => this.executeController(ScheduleIndexController, parameters));
router.on('/film/:filmId', (parameters) => this.executeController(FilmIndexController, parameters));
router.on('/select-city/:cityId', (parameters) => this.executeController(CitySelectController, parameters));
router.on('/select-city', (parameters) => this.executeController(CityIndexController, parameters));
router.on('/list/:when', (parameters) => this.executeController(HomeController, parameters));
router.on('/', (parameters) => this.executeController(HomeController, parameters));

I think this issue is super serious because it basically kills the route initialization itself whenever is not home, location.origin is supported since Safari 7 and IE11.
If you want to support older browsers, location origin can be easily covered by combining location.protocol, location.host and location.port.

So I started refactoring the router to use location.origin. However, that breaks a lot more stuff and I realized that it is against one of my core ideas. Navigo should work if you drop it on a page even tho that page is deeply nested. For example http://site.com/myapps/name/run.html. If we say that we are using location.origin as a root then the router will assume that the path for matching is myapps/name/run.html. So, I'll leave this issue open and will consider it when I start working on a new version.
P.S.
Navigo started as a small script for managing routing but became full with patches because it tries to cover lots of cases. I'm considering rewriting it in a simple form.

Hi @krasimir, I agree with the drop-in view you have about a router, no matter how deeply nested the route is. I think that is a big differenciator from other solutions, however I feel that nested path should be specified by the developer so the router works as expected when the application doesn't start from home.
For example, I have a web app with two routes, / for home and movie/:id for some speific section, if the user instead of accessing to home directly it goes to www.some.site.com/path/to/movie/286 the router kicks off at that path as home and to access a movie the url would be www.some.site.com/path/to/movie/286/movie/286.
I think that taking location.origin as based and a path specified by the developer will solve this compromise. Let me know if this insight helps, I would love to help you out on the re-write.
Cheers!

I'm in a constant battle with myself about how to design the router. What you just described is the second variant. The first one is how the router works now. Last couple of months I'm thinking about a rewrite of the whole thing and I may change it indeed as you are suggesting. It's just with the current code base will be nightmare. There are so many things that will break if we start using location.origin.

Yeah, I agree it will mess up with a lot of stuff. Probably a re-write would be best, and check current features as you tackle them in the new version. Either way, breaking changes and semver exist for something 😄

This suggestion of location.origin should be written at the documentation, and the backward compatible choice of location.protocol, location.host and location.port too.
The documentation says we should set the entry point on new Navigo() but doesn't suggest how. I was trying location.host (which didn't work) and hadn't think about location.origin until I saw this issue.
And thanks for the router :)

@jpenna What I meant by entry point was the root param of the constructor. In general, the next version will rely completely on that root param and it will be made mandatory, because trying to guess what it is is buggy.

@krasimir What I am saying is that it should be written here:

The constructor of the library accepts three argument - root, useHash and hash. The first one is the main URL of your application. If you call the constructor without parameters then Navigo figures out the root URL based on your routes. However, this proves to lead to bugs so I strongly recommend to set a root value: a known root value or if you want to set it dinamically you can use location.origin or build the root string with location.protocol, location.host and location.port.

Finding the root URL was always tricky. The 5.x versions actually have a better route matching but maybe that part with guessing the root is not working the same way. I'm considering making that root parameter mandatory and we always have to provide it. In most of the cases the developer knows where the app is located.
Can you please post here your route definitions so I can reproduce your problem.

Ok so, 3+ years later I'm almost done with the re-write :) . The new version 8.0.0 (you can get it atm via yarn add<EMAIL_ADDRESS>has a mandatory root param.
const router = new Navigo("/schedule");

router
  .on("/:id", (match) => {
    console.log("The id is " + match.data.id);
  })
  .resolve();

meaning that:

if you hit the server at "/" nothing happens
if you hit the server at "/schedule" nothing happens
if you hit the server at "/schedule/xxx" your handler is invoked
if you hit the server at "/schedule/xxx/boo" nothing happens

The example is here https://github.com/krasimir/navigo/tree/big-rewrite/examples/138


How to figure out or calculate the Resource limits to be set for opentelemetry-collector

Hi,
I'm using opentelemtry-collector via deployment mode in my kubernetes cluster.
I'm trying to figure out what is the least amount of resource limits I can set to this opentelemetry-collector so that it does not get OOM killed.
Can someone please help me understand how I can figure out or calculate the resource limits I need to set.
I'm using prometheus in the receiver part of the opentelemetry-collector's pipeline and trying to scrape apiserver_request_total metric from the kube-apiserver and couple of metrics from kube-state-metrics. Later perform some operations using metricstransform in the processor part of the otel pipeline.
Thanks!

Just my two cents. Setting limits on any workload is a hot topic that's widely discussed for many reasons. Especially when it comes to memory, which is a non-compressible resource and therefore can't be stretched the way CPU can be (by the way, CPU throttling is a silent enemy).
What values have you set? In my case, using a Helm chart for deployment, i have usage per pod like this
# kubectl top pod otel-demo-otelcol-$ID
NAME                                 CPU(cores)   MEMORY(bytes)
otel-demo-otelcol-84f4467bf6-5rjd5   19m          74Mi

As for memory limits, I've set it to 125Mi and haven't encountered any issues so far.

This doc may also be helpful: https://opentelemetry.io/docs/collector/scaling/


add note about flowrouter

add note to discourage people from proceeding with ironrouter on new projects. In reference to
https://forums.meteor.com/t/iron-rout-noob-question/25966/7

@chrisbutler  can you merge?

@Maxhodges flow router is now in basically the same state. i don't think this is necessary


Update URL

The URL we have used for this app in the past from Monday:
http://applications.accessapps.link:3011/
Is no longer working,.

Moving this application to Coolify.

Updated on Monday Apps board


I would like to have the primes that it checked to be saved into a text file for personal use.

I would like to have the primes that it checked to be saved into a text file for personal use.
I decompressed the .zip file, but the "cmd" command below does not work. I used the cd command to point to the folder containing the exe, but when i type the command "primesieve.exe 1000 --print > primes.txt" it creates an empty txt file called "primes". There is nothing in it. What i want is a list of primes from 1 to N, but the command only generate an empty file.

I tested your command "primesieve.exe 1000 --print > primes.txt" on my WIndows 7 machine, it creates a primes.txt file (not primes file!) with the primes from 0 to 1000. I suggest you first try if the command "primesieve.exe 1000 --print" works, it should print the primes from 0 to 1000 on the screen. If that works you rerun "primesieve.exe 1000 --print > primes.txt". Remember the primes are saved into primes.txt not primes.

Oh... i will try tomorrow. Please don't close the issue until i finish it.


feat: use-rect package

Description

Linked Issues
Additional context

@ramzzo lock file is not up to date. Can you run pnpm i locally and push again

packages/core/use-composable/src this code should be here. Let's not pack.

packages/core/use-composable/src this code should be here. Let's not pack.

Yeah, true

@ramzzo can you add minimal test for this?

@ramzzo can you add minimal test for this?

I wrote the test but I get an error like this:
packages/core/use-composable/tests/use-rect.test.ts [ packages/core/use-composable/tests/use-rect.test.ts ]
Error: Failed to resolve entry for package "@oku-ui/utils". The package may have incorrect main/module/exports specified in its package.json.

Even though I downloaded the oku-ui utils package, I get the error that the oku-ui utils package does not exist. so I can't run the test and see the result. I tried deleting and re-downloading the node_modules and lock file but the situation was the same.

vitest settings resolve add package, after working in test


Selection Event

Small PR that allows the selection-changed event to bubble past the shadow DOM boundary.

@darth-cheney i am assuming you are fine with this, merging


Include context parameter when dispatching events

https://linear.app/replay/issue/RUN-497/include-context-parameter-when-dispatching-events

Yeah, this was an annoying patch to work on, if I knew how long it would take up front I might have tried harder to find an alternative...


Anchors should move in FixedUpdate

Currently, AnchorableBehaviours move their transforms in Update(). This was a hold-over from the original (InteractionBehaviour-less) implementation of AnchorableBehaviours but it goes against our recommended practices for working with interaction objects and causes undesirable behavior when attaching UIs as AnchorableBehaviours to some in-scene Anchor.
This behaviour should intelligently switch itself on and off depending on whether there actually is an InteractionBehaviour attached to the AnchorableBehaviour.

Upgrading time estimate. I investigated a fix for this in Particles but was not able to reliably update the AnchorableBehaviour during FixedUpdate without jitter when the physics framerate is out of sync with the target render framerate.
Since we've solved this problem for the grasping objects in the IE, I may have just implemented a bad fix.. Unfortunately, we can't have Unity just interpolate arbitrary transforms; we would have to implement a custom interpolation when we desire AnchorableBehaviours to move during FixedUpdate (when they have Interaction Object children).

Update:
PR #991 added an example to the Basic UI scene for correctly moving a menu (by Transform, during Update) that propagates positions-but-not-momentums to child menu objects.
The catch is that the parent must be moved in Update, and usually Interaction-Objects-as-menus are moved via grasping, in FixedUpdate (during the grasped movement update).
Thus, a workaround and example is called for, with this specific case of utilizing AnchorableBehaviours.

UNITY-744, closing here.


Zero Trust Architecture

How it helps
Enhanced visibility and control By monitoring and controlling access to resources in real-time.
Improved visibility and control over network activities, makes  it easier to detect and respond to potential security incidents.
ZTA can help organizations comply with regulatory requirements by providing a framework for implementing security controls and monitoring access to sensitive data and resources.
ZTA provides a higher level of security by enforcing the principle of least privilege, ensuring that users and devices only have access to the resources they need, and limiting lateral movement within the network.

Hi @NIKITA-M-VERMA
You can think opening an Issue or PR is a kind of proposal. So, a proper title, contents along with the given template are important in open source contribution.
Let me close this issue and please retry. :)


DO NOT MERGE TESTS Hvolschenk feature/react linear progress

test for https://github.com/material-components/material-components-web-react/pull/425

Codecov Report

Merging #443 into master will increase coverage by 0.06%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #443      +/-   ##
==========================================
+ Coverage   96.09%   96.16%   +0.06%
==========================================
  Files          53       55       +2
  Lines        1819     1849      +30
  Branches      214      217       +3
==========================================
+ Hits         1748     1778      +30
  Misses         71       71

Impacted Files
Coverage Δ

packages/list/index.js
89.09% <ø> (ø)
:arrow_up:

packages/list/ListItem.js
87.5% <ø> (ø)
:arrow_up:

packages/text-field/Input.js
95.78% <100%> (+0.38%)
:arrow_up:

packages/typography/typography.js
100% <100%> (ø)

packages/typography/index.js
100% <100%> (ø)

Continue to review full report at Codecov.

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


Add optional PodDisruptionBudget to the Helm chart

The platform-engineer who deploys approver-policy using the Helm chart wants to avoid disruption of the approver-policy service when draining a node, for example.

[PodDisruptionBudget] ensures that a voluntary disruption, such as the draining of a Node, cannot proceed until at least one other replica has been successfully scheduled and started on another Node. The Helm chart has parameters to enable and configure a PodDisruptionBudget for each of the long-running cert-manager components.
https://cert-manager.io/docs/installation/best-practice/#poddisruptionbudget

They can use the following values.yaml to achieve this:
podDisruptionBudget:
   enabled: true

Testing
Without enabling PDB
$ helm upgrade --install -n venafi approver-policy _bin/scratch/image/cert-manager-approver-policy-v0.13.0-alpha.0-11-g6f7f6646bd238c-dirty.tgz
Release "approver-policy" does not exist. Installing it now.
NAME: approver-policy
LAST DEPLOYED: Wed Feb 28 10:09:08 2024
NAMESPACE: venafi
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
⚠  WARNING: Consider increasing the Helm value `replicaCount` to 2 if you require high availability.
⚠  WARNING: Consider setting the Helm value `podDisruptionBudget.enabled` to true if you require high availability.

CHART NAME: cert-manager-approver-policy
CHART VERSION: v0.13.0-alpha.0-11-g6f7f6646bd238c-dirty
APP VERSION: v0.13.0-alpha.0-11-g6f7f6646bd238c-dirty

cert-manager-approver-policy is a cert-manager project.

If you're a new user, we recommend that you read the [cert-manager Approval Policy documentation] to learn more.

[cert-manager Approval Policy documentation]: https://cert-manager.io/docs/policy/approval/

With PodDisruptionBudget enabled
$ helm upgrade --install -n venafi approver-policy _bin/scratch/image/cert-manager-approver-policy-v0.13.0-alpha.0-12-g075790a76f86b9-dirty.tgz  --set replicaCount=2 --set podDisruptionBudget.enabled=true --set image.tag=v0.12.1
Release "approver-policy" has been upgraded. Happy Helming!
NAME: approver-policy
LAST DEPLOYED: Wed Feb 28 10:22:50 2024
NAMESPACE: venafi
STATUS: deployed
REVISION: 4
TEST SUITE: None
NOTES:
CHART NAME: cert-manager-approver-policy
CHART VERSION: v0.13.0-alpha.0-12-g075790a76f86b9-dirty
APP VERSION: v0.13.0-alpha.0-12-g075790a76f86b9-dirty

cert-manager-approver-policy is a cert-manager project.

If you're a new user, we recommend that you read the [cert-manager Approval Policy documentation] to learn more.

[cert-manager Approval Policy documentation]: https://cert-manager.io/docs/policy/approval/

/hold while I test that this actually works on a multi-node cluster.

Demonstration of PodDisruptionBudget preventing disruption of the approver-policy service

Create three-node cluster

# kind.config.yaml
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
- role: worker
- role: worker

kind create cluster --config kind.config.yaml

Label and taint first worker only

kubectl label node kind-worker node-restriction.kubernetes.io/reserved-for=platform
kubectl taint node kind-worker node-restriction.kubernetes.io/reserved-for=platform:NoExecute

Deploy approver-policy

# values.yaml

image:
  tag: v0.12.1

replicaCount: 2

podDisruptionBudget:
  enabled: true

app:
  webhook:

    affinity:
      nodeAffinity:
       requiredDuringSchedulingIgnoredDuringExecution:
         nodeSelectorTerms:
         - matchExpressions:
           - key: node-restriction.kubernetes.io/reserved-for
             operator: In
             values:
             - platform

    tolerations:
    - key: node-restriction.kubernetes.io/reserved-for
      operator: Equal
      value: platform

kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.3/cert-manager.crds.yaml

helm upgrade approver-policy _bin/scratch/image/cert-manager-approver-policy-v0.13.0-alpha.0-12-g075790a76f86b9-dirty.tgz --install --create-namespace --namespace venafi --values values.yaml

Both Pods are assigned to first worker node

$ kubectl get pods -n venafi -o wide
NAME                                            READY   STATUS    RESTARTS      AGE     IP           NODE          NOMINATED NODE   READINESS GATES
cert-manager-approver-policy-78bdd57987-ps2jh   1/1     Running   4 (78s ago)   3m25s   <IP_ADDRESS>   kind-worker   <none>           <none>
cert-manager-approver-policy-78bdd57987-zkqn4   1/1     Running   4 (99s ago)   3m39s   <IP_ADDRESS>   kind-worker   <none>           <none>

Label and taint the second worker

kubectl label node kind-worker2 node-restriction.kubernetes.io/reserved-for=platform
kubectl taint node kind-worker2 node-restriction.kubernetes.io/reserved-for=platform:NoExecute

(Does not automatically trigger the re-scheduling of approver-policy Pod 2)

Drain worker node 1

$ kubectl drain kind-worker --ignore-daemonsets --delete-emptydir-data
node/kind-worker already cordoned
Warning: ignoring DaemonSet-managed Pods: kube-system/kindnet-pw4rl, kube-system/kube-proxy-lf94r
evicting pod venafi/cert-manager-approver-policy-78bdd57987-zkqn4
evicting pod venafi/cert-manager-approver-policy-78bdd57987-ps2jh
error when evicting pods/"cert-manager-approver-policy-78bdd57987-zkqn4" -n "venafi" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget.
pod/cert-manager-approver-policy-78bdd57987-ps2jh evicted
evicting pod venafi/cert-manager-approver-policy-78bdd57987-zkqn4
error when evicting pods/"cert-manager-approver-policy-78bdd57987-zkqn4" -n "venafi" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget.
evicting pod venafi/cert-manager-approver-policy-78bdd57987-zkqn4
error when evicting pods/"cert-manager-approver-policy-78bdd57987-zkqn4" -n "venafi" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget.
evicting pod venafi/cert-manager-approver-policy-78bdd57987-zkqn4
pod/cert-manager-approver-policy-78bdd57987-zkqn4 evicted
node/kind-worker drained

approver-policy Pods were moved to worker 2 one at a time

$ kubectl get pods -n venafi -o wide
NAME                                            READY   STATUS    RESTARTS   AGE   IP           NODE           NOMINATED NODE   READINESS GATES
cert-manager-approver-policy-78bdd57987-c9xdw   1/1     Running   0          12m   <IP_ADDRESS>   kind-worker2   <none>           <none>
cert-manager-approver-policy-78bdd57987-v62wp   1/1     Running   0          12m   <IP_ADDRESS>   kind-worker2   <none>           <none>

/unhold


esp32: fix naming of BT modem sleep orig config

It seems like the naming of the config for BTDM modem sleep orig mode has changed name in esp-idf. In the latest doc (5.2.3) it is referred to as CONFIG_BTDM_CTRL_MODEM_SLEEP_MODE_ORIG, https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-reference/kconfig.html#config-btdm-ctrl-modem-sleep-mode. I can find references to CONFIG_BTDM_MODEM_SLEEP_MODE_ORIG in 3.1, https://docs.espressif.com/projects/esp-idf/en/release-v3.1/api-reference/kconfig.html.
Furthermore, this has (now) an actual effect on modem mode. In a simple BLE sample where we advertise, the power consumption is reduced by over 50 % (from 70 to sub 30 mA on 3V).

@real-tintin, I don't se how this change has any effect at all. Also, hal_espressif is based on esp-idf v5.1.x, which does not have that change. We are planning to update do v5.3 soon.

I hear you.
But let me share some actual results of the power consumption. These are some the simple BLE sample which I mentioned. BLE is configured and enabled, advertisement i started. All using the Zephyr BT API's.
Without modem mode

With modem mode

The device boots and renders a spike and about 2 s of higher power consumption. I guess this is the radio. Then the usage drops significantly, when entering modem sleep (avg 30 mA compared to 70 mA without sleep). The following spikes are the rate of advertisement, which here is fast mode (100-150 ms).
Correct me if I'm wrong, but zephyr/esp32/src/bt/esp_bt_adapter.c is not managed by esp-idf, it belongs to this project? In esp-idf there are no (longer) any mentions of CONFIG_BTDM_MODEM_SLEEP_MODE_ORIG, instead CONFIG_BTDM_CTRL_MODEM_SLEEP_MODE_ORIG is used, configurable components/bt/controller/esp32/Kconfig.in.

I did some bisecting. The name change of the config in esp-idf occurred here:
commit 7c1c6697999b1f17eaeeb57bd09ae7db8a381cf5 (HEAD)
Author: zwj<EMAIL_ADDRESS>Date:   Thu Jul 9 20:58:13 2020 +0800

    component/bt: add BLE v5.0 feature for bluedroid host

This is between their v4.2 and v4.3.

@sylvioalves
I see the results you posted. How did you enable CONFIG_BTDM_MODEM_SLEEP_MODE_ORIG in there if there is no Zephyr's kconfig entry for CONFIG_BTDM_MODEM_SLEEP_MODE_ORIG? Did you manually enabled this in that file?
I think you are correct, we should have renamed CONFIG_BTDM_MODEM_SLEEP_MODE_ORIG to CONFIG_BTDM_CTRL_MODEM_SLEEP_MODE_ORIG (which we will).
I have a local PR that moves some of those BT/BLE kconfig entries to Zephyr's main repository. That will allow changing this configuration in the application itself.

I defined the configs in my application KConfig overlay, outside of Zephyr.
That sounds good. Better to define them in Zephyr. Let me know if I can help reviewing.


Monster activations in log

Also doing horror, evade, attacks and start of investigator/mythos phase.


Canvas background color unsettable

when setting styles { 'color' } for the PIXI renderer, color is always black, no matter what is given.
using physics/dist/physicsjs-full.min.js
pixi, in requirejs.config path is set to: pixi: 'physics/lib/pixi'
        require(['pixi'], function (PIXI)
        {
            window.PIXI = PIXI;
            // create a renderer
            var renderer = Physics.renderer('pixi', {
                el: 'PIXI',
                autoResize: false,
                width: bm.width,
                height: bm.height,

                styles: {
                    'color': '0x66FF99',
                }
            });

            // add the renderer
            world.add(renderer);
            // render on each step
            world.on('step', function ()
            {
                world.render();
            });
            // add the interaction
            world.add(Physics.behavior('interactive', {el: renderer.container}));
        });

I never had to set a color for the renderer, but normally what's needed is fillColor, without strings.
So even if the attribute was "color", you would not say {"color": n}, but {color: n}
and as I know, color codes are specified like: "#RRGGBB", not "0xRRGGBB" in Javascript.

It works while playing with code in the showcase online?

Ok... :/


Generic Host - just how generic?

We're looking at using the generic host in Blazor - unfortunately a few aspects aren't quite generic enough for our purposes.  I think it's worth looking into what things would change if we're using the generic host is in a minimal environment like WASM in the browser.
The only blocking issue I've run into so far is that the host builder creates a physical file provider, which will try to access the disk when created. https://github.com/aspnet/Hosting/blob/master/src/Microsoft.Extensions.Hosting/HostBuilder.cs#L137 This is a party foul in the browser 😢
I think long term we'd also want to replace https://github.com/aspnet/Hosting/blob/master/src/Microsoft.Extensions.Hosting/Internal/ConsoleLifetime.cs#L14

For now we're working around this by taking the code and implementing the abstractions ourselves, but it's not our desired state.
If we had the ability suppress creation of the file provider that would help.
I'm doing an experiment right now to determine what the impact is right now of adding hosting.abstractions to Blazor's in-browser set of dependencies to see what the impact is on our total dependency size. The way things are wired up in the host builder I'm not sure that we'll be able to get the linker to trim these extra dependencies.

@rynowak we would accept PRs :) Make sure to get an agreement with @davidfowl and @Tratcher though.

Oh cool beans.
So I did finish my investigation and found that generic host brings in additional 350kb or so of dependencies, which makes it totally unsuitable for Blazor. I don't think it's realistic for us to optimize this at a level where it's useful for Blazor. Feel free to close if you don't think there's anything valuable here.

Agreed, we should close this out.


Python Interpreter not Detected In VS Code Jupyter Notebook

Bug: Python interpreter not detected in Jupyter Notebook.
Error message: Python is not installed. Please download and install Python in order to execute cells in this notebook.
Python Version: 3.9
VS Code Version: 1.59.1

Error:

Closed.
Issue was happening because of PATH variable error


Refs #29145 Updated CIText to return case insensitive string values

Ticket 29145

Not sure this is something we should do.
>>> post = Post.objects.create(name="New Post")
>>> post.name == "NEW POST"

Will work but
>>> post = Post(name="New Post")
>>> post.name == "NEW POST"

Won't.
We moved away from running to_python on value assignment a few years ago and we don't do such thing for other fields such as ArrayField for example so I'm not convinced we should be doing anything here.

@v1kku Thanks for this patch :+1: , however I agree with Simon that this is error-prone. Moreover I don't think that we will be able to provide better solution. I'm going to close this ticket.

In response to charettes, I don't think that's unexpected behaviour, same thing is true with other fields since django doesn't do any field validation/cleaning in __init__
from datetime import time
from django.db import models

class Post(models.Model):
    posted = models.TimeField()

>>> p = Post(posted='12:00')
>>> p.posted == time(12)
False
>>> p.save()
>>> p = Post.objects.first()
>>> p.posted == time(12)
True


Support for Community Service as punishment

Describe the feature
When LEO give jail or warning or fine also add the ability to put them on probation to do community service. Just needs to accept a string of what probation entails. This is for use with prison scripts that have community service like rcore thanks
Additional Context
No response

This would be a field called "Community Service" (communityService?: string)? @dexslab

Yes this would be just that a string for community service arrest record and can be used in conjunction with fine like you can with jail time