Fix Windows Compilation Issues in joint_trajectory_controller and pid_controller (master branch)

Description:
This pull request addresses compilation issues encountered in the joint_trajectory_controller and pid_controller when building on Windows. The changes ensure compatibility with the Windows environment and improve overall stability.
Changes Made:

joint_trajectory_controller:

Modified conditional compilation flags to ensure compatibility with Windows builds.

pid_controller:

Added compile definitions for Windows to minimize namespace collisions and define math constants:if(WIN32)
  add_compile_definitions(
    # For math constants
    _USE_MATH_DEFINES
    # Minimize Windows namespace collision
    NOMINMAX
    WIN32_LEAN_AND_MEAN
  )
endif()

Testing:

Local tests have been run successfully, confirming that all modifications do not break existing functionality.

Please let me know if you have any questions or need further modifications. I appreciate your feedback!

I don't see the changes you listed in your description, are there commits missing?

It’s just the = sign and the CMakeLists changes in the commit: fixes for Windows compilation.

It’s just the = sign and the CMakeLists changes in the commit: fixes for Windows compilation.

I was just wondering, you write

Modified conditional compilation flags to ensure compatibility with Windows builds.

but only the lambda capture was changed for JTC.

What about: "Modifies the lambda capture in is_erase_value from [ ] to [=], which captures all outer scope variables by value."?

I'm totally fine with the changes you did, just the description was not matching ;)


Fix Acquire <-> OpenGHG linkage

Get the updated Fn routing functions working with Acquire and mock testing capabilities restored.

Done with #86


Remove Ellipsis Overflow on Story Posts

I believe this was designed for the "show more" cut-off point - but this doesn't work there anyway... :confounded:
This solves a somewhat rare issue in Blink's/Chrome(?) rendering which will add an ellipsis for any lines that "overflow" the container, instead of dropping the word to the next line.
Example:

 On the last full line the word "subs" is right up against the container's width and Chrome changes it to "su...".
Without text-overflow: ellipsis:

The text is not overflowing the container.

This might actually be for long links — to prevent them from overflowing the box?

This might actually be for long links — to prevent them from overflowing the box?

Why did I not think of this :facepunch: :dizzy_face:

Actually a solution:

Remove text-overflow: ellipsis as done here,
Add text-overflow: ellipsis and display: block to .comment-text a

:pray: update PR!


Devika AI is not responding when any text is searched

Devika AI is not responding when any text is searched.
I tried with multiple combinations of model and search engine. Still no luck, it seems there is an issue with api response.

post logs

PS D:\devikaAi> cd .\devika
PS D:\devikaAi\devika> python .\devika.py
24.04.23 15:21:09: root: INFO   : Initializing Devika...
24.04.23 15:21:09: root: INFO   : Initializing Prerequisites Jobs...
24.04.23 15:21:14: root: INFO   : Loading sentence-transformer BERT models...
24.04.23 15:21:18: root: INFO   : BERT model loaded successfully.
24.04.23 15:21:19: root: INFO   : Ollama available
24.04.23 15:21:21: root: INFO   : Devika is up and running!
Socket connected ::  {'data': 'frontend connected!'}
24.04.23 15:28:18: root: INFO   : SOCKET socket_response MESSAGE: {'data': 'Server Connected'}
24.04.23 15:28:18: root: INFO   : /api/data GET
24.04.23 15:28:18: root: DEBUG  : /api/data GET - Response: {"models":{"CLAUDE":[["Claude 3 Opus","claude-3-opus-20240229"],["Claude 3 Sonnet","claude-3-sonnet-20240229"],["Claude 3 Haiku","claude-3-haiku-20240307"]],"GOOGLE":[["Gemini 1.0 Pro","gemini-pro"]],"GROQ":[["LLAMA3 8B","llama3-8b-8192"],["LLAMA3 70B","llama3-70b-8192"],["LLAMA2 70B","llama2-70b-4096"],["Mixtral","mixtral-8x7b-32768"],["GEMMA 7B","gemma-7b-it"]],"MISTRAL":[["Mistral 7b","open-mistral-7b"],["Mistral 8x7b","open-mixtral-8x7b"],["Mistral Medium","mistral-medium-latest"],["Mistral Small","mistral-small-latest"],["Mistral Large","mistral-large-latest"]],"OLLAMA":[],"OPENAI":[["GPT-4 Turbo","gpt-4-turbo"],["GPT-3.5 Turbo","gpt-3.5-turbo-0125"]]},"projects":["rama"],"search_engines":["Bing","Google","DuckDuckGo"]}
24.04.23 15:28:18: root: INFO   : /api/get-agent-state POST
24.04.23 15:28:18: root: DEBUG  : /api/get-agent-state POST - Response: {"state":null}
24.04.23 15:28:21: root: INFO   : /api/get-agent-state POST
24.04.23 15:28:21: root: DEBUG  : /api/get-agent-state POST - Response: {"state":{"agent_is_active":true,"browser_session":{"screenshot":null,"url":null},"completed":false,"internal_monologue":null,"message":null,"step":null,"terminal_session":{"command":null,"output":null,"title":null},"timestamp":"2024-04-22 12:35:09","token_usage":370}}
24.04.23 15:28:33: root: INFO   : SOCKET server-message MESSAGE: {'messages': {'from_devika': False, 'message': 'Write code in java script to multiply two numbers', 'timestamp': '2024-04-23 15:28:33'}}

Request logs
24.04.23 15:28:21: root: DEBUG : /api/get-agent-state POST - Response: {"state":{"agent_is_active":true,"browser_session":{"screenshot":null,"url":null},"completed":false,"internal_monologue":null,"message":null,"step":null,"terminal_session":{"command":null,"output":null,"title":null},"timestamp":"2024-04-22 12:35:09","token_usage":370}}
24.04.23 15:28:21: root: INFO : /api/get-agent-state POST
24.04.23 15:28:18: root: DEBUG : /api/get-agent-state POST - Response: {"state":null}
24.04.23 15:28:18: root: INFO : /api/get-agent-state POST
24.04.23 15:28:18: root: DEBUG : /api/data GET - Response: {"models":{"CLAUDE":[["Claude 3 Opus","claude-3-opus-20240229"],["Claude 3 Sonnet","claude-3-sonnet-20240229"],["Claude 3 Haiku","claude-3-haiku-20240307"]],"GOOGLE":[["Gemini 1.0 Pro","gemini-pro"]],"GROQ":[["LLAMA3 8B","llama3-8b-8192"],["LLAMA3 70B","llama3-70b-8192"],["LLAMA2 70B","llama2-70b-4096"],["Mixtral","mixtral-8x7b-32768"],["GEMMA 7B","gemma-7b-it"]],"MISTRAL":[["Mistral 7b","open-mistral-7b"],["Mistral 8x7b","open-mixtral-8x7b"],["Mistral Medium","mistral-medium-latest"],["Mistral Small","mistral-small-latest"],["Mistral Large","mistral-large-latest"]],"OLLAMA":[],"OPENAI":[["GPT-4 Turbo","gpt-4-turbo"],["GPT-3.5 Turbo","gpt-3.5-turbo-0125"]]},"projects":["rama"],"search_engines":["Bing","Google","DuckDuckGo"]}
24.04.23 15:28:18: root: INFO : /api/data GET
24.04.23 15:21:21: root: INFO : Devika is up and running!
24.04.23 15:21:19: root: INFO : Ollama available
24.04.23 15:21:18: root: INFO : BERT model loaded successfully.
24.04.23 15:21:14: root: INFO : Loading sentence-transformer BERT models...
24.04.23 15:21:09: root: INFO : Initializing Prerequisites Jobs...
24.04.23 15:21:09: root: INFO : Initializing Devika...

I had the same issue.
I saw this in my logs:
openai.RateLimitError: Error code: 429 - {'error': {'message': 'You exceeded your current quota, please check your plan and billing details. For more information on this error, read the docs: https://platform.openai.com/docs/guides/error-codes/api-errors.', 'type': 'insufficient_quota', 'param': None, 'code': 'insufficient_quota'}}
and after correcting it, also this:
openai.PermissionDeniedError: Error code: 403 - {'error': {'message': 'Project proj_xZIG3B04CTPZw2VmeQyVuaS4does not have access to modelgpt-3.5-turbo-0125', 'type': 'invalid_request_error', 'param': None, 'code': 'model_not_found'}}
etc
and when one error occurs it all stops working.
You have to create a new project to get it working again


Add GLUE config name check

Fixes #130 by adding a name check to the Glue class

If tests are being added, any guidance on where to add tests would be helpful!
Tagging @thomwolf for review

Looks good to me. Is this compatible with the way we are doing tests right now @patrickvonplaten ?

If the tests pass it should be fine :-)

The test fails with an AssertionError because the name is not being passed to kwargs, however I'm not sure how to do that, because only the config file is being passed to the tests of all datasets?
 Each example is a sequence of words annotated\nwith whether it is a grammatical English sentence.')}

    def __init__(self, *args, **kwargs):
>       assert ('name' in kwargs and kwargs['name'] is not None), "Glue has to be called with a configuration name"
E       AssertionError: Glue has to be called with a configuration name

/usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597/glue.py:139: AssertionError
----------------------------- Captured stderr call -----------------------------
INFO:nlp.load:Checking ./datasets/glue/glue.py for additional imports.
INFO:filelock:Lock<PHONE_NUMBER> acquired on ./datasets/glue/glue.py.lock
INFO:nlp.load:Found main folder for dataset ./datasets/glue/glue.py at /usr/local/lib/python3.7/site-packages/nlp/datasets/glue
INFO:nlp.load:Found specific version folder for dataset ./datasets/glue/glue.py at /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597
INFO:nlp.load:Found script file from ./datasets/glue/glue.py to /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597/glue.py
INFO:nlp.load:Found dataset infos file from ./datasets/glue/dataset_infos.json to /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597/dataset_infos.json
INFO:nlp.load:Found metadata file for dataset ./datasets/glue/glue.py at /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597/glue.json
INFO:filelock:Lock<PHONE_NUMBER> released on ./datasets/glue/glue.py.lock
INFO:nlp.load:Checking ./datasets/glue/glue.py for additional imports.
INFO:filelock:Lock<PHONE_NUMBER> acquired on ./datasets/glue/glue.py.lock
INFO:nlp.load:Found main folder for dataset ./datasets/glue/glue.py at /usr/local/lib/python3.7/site-packages/nlp/datasets/glue
INFO:nlp.load:Found specific version folder for dataset ./datasets/glue/glue.py at /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597
INFO:nlp.load:Found script file from ./datasets/glue/glue.py to /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597/glue.py
INFO:nlp.load:Found dataset infos file from ./datasets/glue/dataset_infos.json to /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597/dataset_infos.json
INFO:nlp.load:Found metadata file for dataset ./datasets/glue/glue.py at /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597/glue.json
INFO:filelock:Lock<PHONE_NUMBER> released on ./datasets/glue/glue.py.lock
------------------------------ Captured log call -------------------------------
INFO     nlp.load:load.py:157 Checking ./datasets/glue/glue.py for additional imports.
INFO     filelock:filelock.py:274 Lock<PHONE_NUMBER> acquired on ./datasets/glue/glue.py.lock
INFO     nlp.load:load.py:320 Found main folder for dataset ./datasets/glue/glue.py at /usr/local/lib/python3.7/site-packages/nlp/datasets/glue
INFO     nlp.load:load.py:333 Found specific version folder for dataset ./datasets/glue/glue.py at /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597
INFO     nlp.load:load.py:346 Found script file from ./datasets/glue/glue.py to /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597/glue.py
INFO     nlp.load:load.py:356 Found dataset infos file from ./datasets/glue/dataset_infos.json to /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597/dataset_infos.json
INFO     nlp.load:load.py:367 Found metadata file for dataset ./datasets/glue/glue.py at /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597/glue.json
INFO     filelock:filelock.py:318 Lock<PHONE_NUMBER> released on ./datasets/glue/glue.py.lock
INFO     nlp.load:load.py:157 Checking ./datasets/glue/glue.py for additional imports.
INFO     filelock:filelock.py:274 Lock<PHONE_NUMBER> acquired on ./datasets/glue/glue.py.lock
INFO     nlp.load:load.py:320 Found main folder for dataset ./datasets/glue/glue.py at /usr/local/lib/python3.7/site-packages/nlp/datasets/glue
INFO     nlp.load:load.py:333 Found specific version folder for dataset ./datasets/glue/glue.py at /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597
INFO     nlp.load:load.py:346 Found script file from ./datasets/glue/glue.py to /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597/glue.py
INFO     nlp.load:load.py:356 Found dataset infos file from ./datasets/glue/dataset_infos.json to /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597/dataset_infos.json
INFO     nlp.load:load.py:367 Found metadata file for dataset ./datasets/glue/glue.py at /usr/local/lib/python3.7/site-packages/nlp/datasets/glue/fa7c9f982200144186b2831060b54199cf028e4bbdc5f40acd339ee343342597/glue.json
INFO     filelock:filelock.py:318 Lock<PHONE_NUMBER> released on ./datasets/glue/glue.py.lock

Closing as #130 is fixed !


Code Highlighting

In order for the user to have more relation to the coding/programing aspect of the blocks and to help the user troubleshoot problems in the block stack creation in respect to the code, the generated code should highlight in conjunction with the selected blocks within the workspace.

Looks like #79 fixed this one, or at least gives it the current highlighting functionality that Trinket's blocks have.

Ready to close IMO.

I believe #79 did resolve this issue. It was just never linked with tags but i think we can go ahead and close this one.


Packaging self-contained pylearn2 for the PyPI release?

Since the goal of the project is to make deep neural networks and PyLearn2 more accessible, I'm wondering about packaging up the library along with the PyPI release of sknn.  It would be self-contained and sknn would load that up as a fallback...  What do you think?
It's not something that the PyLearn2 developers are considering right now (due to the overheads):
https://github.com/lisa-lab/pylearn2/issues/1493
... but could be worthwhile as part of this project.  We have some automated tests, and along with PyLearn2's test suite it can be pretty safe.
If there's already a PyLearn2 version installed then I think sknn should use that, maybe printing a debug message: "This is the packaged version of sknn but it's using a version of pylearn2 that's already installed."
Thoughts welcome!

Until pylearn2 as a release exist on pypi, your suggestion seems the only meaningfull solution.
Ideal situation would be:

pylearn2 exists as a wheel package with a perfectly predictable release commit,
you don't need (then) to re-include pylearn2 in scikit-neuralnetwork wheel.

I think I kind of agree with both comments above - packaging PyLearn2 makes the use of the library transparent.

OK, this seems to work, from the wrap branch.  Some links I found useful:
http://peterdowns.com/posts/first-time-with-pypi.html
https://tom-christie.github.io/articles/pypi/

Assuming there's a symlink to the pylearn2 within sknn, release looks like this now:
python setup.py sdist
twine upload -r test dist/*.tar.gz
```

(This applies to testpypi.python.org.)


Prepare for the next release

This finally completes the 2.31 release :)

Coverage: 59.376%. Remained the same when pulling a8b7dd2ec24106be39d5fd18aedf429dc4bb7038 on feature/prepare-next-release into cdcd298222ec1bd5c025292c6df5426e12b0cf5d on master.

Oh, I meant for this to auto-merge, but apparently forgot to arrange for that.
Sure, please merge anything you think is worthwhile and free of obvious problems. You did a great job of it during the last release cycle, too!


Update to Support Library 23.3.0

According to this page:

Changes for v7 Preference library:

Fixed issue where PreferenceFragmentCompat would crash if dividerHeight is specified. (Issue 204778)

I would update, but my SDK Manager says that the latest version is 23.2.1...

Mmm refresh maybe?

No luck, I even downloaded a new SDK manager and it still lists 23.2.1 as the latest...

Wait my Android SDK Manager displays 23.2.1 now. Maybe they unpublished it?

That would be a new low I guess.

@Gericop Thanks for taking the effort of maintaining the fix for preference workaround. I came back here to this repository again, after figuring several things were broken, after upgrading to latest support library.

23.3. is available for some days.

I know now, I'll update the things by Friday (I'm a bit busy now, university stuff, you know...)

Upgraded to v23.3.0. No real changes in the official API though...


Too easy to DoS

(echo -n "'" && (while true; do echo -n "a"; done)) | nc localhost <port num>
eats up all the memory until the VM dies.

Fred's http://erlang-in-anger.com around the beginning has some great ideas and resources on exactly this topic.


add pep badges

Codecov Report
Base: 62.04% // Head: 69.52% // Increases project coverage by +7.48% :tada:

Coverage data is based on head (8f05d76) compared to base (40e8014).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #53      +/-   ##
==========================================
+ Coverage   62.04%   69.52%   +7.48%
==========================================
  Files          14       14
  Lines        1283     1283
==========================================
+ Hits          796      892      +96
+ Misses        487      391      -96

Flag
Coverage Δ

unittests
69.52% <ø> (+7.48%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

nndt/vizualize.py
96.96% <0.00%> (+96.96%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Documentation: migration guide

I recently released jest-codemods to help migrating existing tests from AVA/Tape to Jest. Or at least give people a chance to try it out. 🍰
This issue is for creation a migration guide on the Jest documentation. @cpojer talked about this on the twitter thing.
I can write about the codemods, but I'll need some help for other test frameworks like Mocha, Karma, and what not.
A few open questions:

is it a new page on http://facebook.github.io/jest/docs/getting-started.html or part of that page?
which testing frameworks will we write about?
what are the most commonly used testing tools that we should write about, and consider making a codemod to in jest-codemods?

Let's add a new docs page "Migration to Jest" that mentions how to migrate from different test frameworks.

If you are using Jasmine or the test runner you are using uses Jasmine, Jest should be mostly compatible and easy to upgrade.
If you are using ava or tape, you can upgrade with jest-codemods
If you like chai, you can upgrade to Jest and continue to use chai.

A docs page can be added in the docs/ folder and is hooked up by updating the page that comes before and after. You can then npm install and npm start inside of the website/ folder to see your changes live.
I think it is good to start out with the migration document and see how far you can get. Then we can expand it later :)


Add support for resource directory

at least the methods and basic checks are  in place, I think.
Did I forget anything? Are there some more detailed checks that should be performed? E.g. should the plugin check for _host.canUseResourceDirectory() inside the Plugin<h, l>::clapResourceDirectory... methods?

Hi @Trinitou ,
Thank you very much this is perfect :ok_hand:
Cheers,
Alex


v4 preview is not handling when scheme is not specified in IAuthorizeData

When specifying a function with:
[FunctionName("MyFunction")]
[FunctionAuthorize] //no scheme identified and it should remain this way
public Task<IActionResult> Run([HttpTrigger("get")] HttpRequest)
{
  // ...
}

The changes introduce to v4 preview prevent from evaluator to consider a policy as no scheme is specified.
Authorization always fails

Fix is in for this issue


Bump @storyblok/js to latest version

Description
The current version of the @storyblok/js API in use is almost 4 years old. Is there a reason why it hasn't been upgraded to the latest version yet?
Suggested solution or improvement
Change the @storyblok/js dependency from ^3.0.8 to v6.8.1 or similar.
Additional context
No response
Validations

[X] Follow our Code of Conduct

Nevermind, I confused @storyblok/js with @storyblok/js-client


ci: conformance-gateway-api wait for images before matrix generation

Followup from https://github.com/cilium/cilium/pull/34707

/test

/test

/test


RAC5071: failed to copy artifact of PACKER_CACHE_BUILD

The PR fix the issue by:

split job PACKER_CACHE_BUILD into 2 jobs: OVA_CACHE_BUILD and VAGRANT_CACHE_BUILD

MasterCI builds ova only when job OVA_CACHE_BUILD  is not running .

MasterCI builds vagrant only when job VAGRANT_CACHE_BUILD  is not running.

@panpan0000 @changev @anhou @iceiilin

Jobs:
test for MasterCI: http://rackhdci.lss.emc.com/job/RAC5071/
OVA_CACHE_BUILD: http://rackhdci.lss.emc.com/job/OVA_CACHE_BUILD/
VAGRANT_CACHE_BUILD: http://rackhdci.lss.emc.com/job/VAGRANT_CACHE_BUILD/


[Bug] Closing via alt-tab changes window_x and window_y to large negative numbers preventing future runs.

Don't have a frim repro on this but if you have IV/Play running on your main monitor with some other programs and then alt-tab to bring up the switching menu, and then click on the close icon on the switching menu preview of IV/Play (see pic) it will sometimes write window_x and window_y to -32000 in the *.cfg file.

Not sure what the easiest solution would be, a check to never go negative for window_x or window_y?

Just saw this fix the other day, d'oh. Closing, thanks for the fix.


steinbock 0.10: cannot import 'register_translation' from 'skimage.feature'

Hi Jonas,
I get the error message below when trying to segment my images with steinbock 0.10.1 (command: steinbock segment deepcell --minmax on ubuntu 18.04). The command worked on the same dataset with steinbock 0.9.1 (with the same initial tensorflow warning).
Do you know how this can be fixed?
Thanks,
Nicolas
        WARNING:tensorflow:SavedModel saved prior to TF 2.5 detected when loading Keras model. Please ensure that you are saving the model with model.save() or tf.keras.models.save_model(), *NOT* tf.saved_model.save(). To confirm, there should be a file named "keras_metadata.pb" in the SavedModel directory.
Traceback (most recent call last):
  File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/app/steinbock/steinbock/__main__.py", line 5, in <module>
    steinbock_cmd_group(prog_name="steinbock")
  File "/opt/venv/lib/python3.8/site-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)
  File "/opt/venv/lib/python3.8/site-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/opt/venv/lib/python3.8/site-packages/click/core.py", line 1659, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/opt/venv/lib/python3.8/site-packages/click/core.py", line 1659, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/opt/venv/lib/python3.8/site-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/opt/venv/lib/python3.8/site-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/app/steinbock/steinbock/_env.py", line 90, in check_steinbock_version_wrapper
    return func(*args, **kwargs)
  File "/app/steinbock/steinbock/segmentation/_cli/deepcell.py", line 163, in deepcell_cmd
    for img_file, mask in deepcell.try_segment_objects(
  File "/app/steinbock/steinbock/segmentation/deepcell.py", line 81, in try_segment_objects
    app, predict = application.value(model=model)
  File "/app/steinbock/steinbock/segmentation/deepcell.py", line 33, in _mesmer_application
    from deepcell.applications import Mesmer
  File "/opt/venv/lib/python3.8/site-packages/deepcell/__init__.py", line 34, in <module>
    from deepcell import applications
  File "/opt/venv/lib/python3.8/site-packages/deepcell/applications/__init__.py", line 32, in <module>
    from deepcell.applications.application import Application
  File "/opt/venv/lib/python3.8/site-packages/deepcell/applications/application.py", line 37, in <module>
    from deepcell_toolbox.utils import resize, tile_image, untile_image
  File "/opt/venv/lib/python3.8/site-packages/deepcell_toolbox/__init__.py", line 30, in <module>
    from deepcell_toolbox import processing
  File "/opt/venv/lib/python3.8/site-packages/deepcell_toolbox/processing.py", line 37, in <module>
    from skimage.feature import peak_local_max, register_translation
ImportError: cannot import name 'register_translation' from 'skimage.feature' (/opt/venv/lib/python3.8/site-packages/skimage/feature/__init__.py)

Hi Nicolas, thanks for filing this! This is a bug and I'll release a fix asap, tomorrow the latest. Until then, version 0.10.0 should work. Sorry for this!

Fixed with https://github.com/BodenmillerGroup/steinbock/commit/94070453b2318faf02418e3ab9b636cce327bec2, version 0.10.2 is currently being built and released: https://github.com/BodenmillerGroup/steinbock/actions/runs/1550898968


fixup! CrateDB vector: Add vector store support

We talked about this today. Removing .all() at the end of the SQLAlchemy query does not change much. The test suite succeeds in the same way as beforehand.
/cc @ckurze

I think everything is correct on this end. While we were reviewing this together yesterday, I misjudged this as a potential issue, but in fact, there is none. Everything is correct on this end.


panic: runtime error: invalid memory address or nil pointer dereference

tlsx -u www.sina.com.cn -probe-status -self-signed

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x1 pc=0x103216df0]

goroutine 43 [running]:
github.com/projectdiscovery/tlsx/pkg/output.(*StandardWriter).formatStandard(0x1400058f050, 0x140001d6360)
	/Users/geekboy/Github/tlsx/pkg/output/output.go:179 +0x6f0
github.com/projectdiscovery/tlsx/pkg/output.(*StandardWriter).Write(0x1400058f050, 0x1033239a6?)
	/Users/geekboy/Github/tlsx/pkg/output/output.go:64 +0x40
github.com/projectdiscovery/tlsx/internal/runner.(*Runner).processInputElementWorker(0x140005bb100, 0x0?, 0x0?)
	/Users/geekboy/Github/tlsx/internal/runner/runner.go:166 +0x6d0
created by github.com/projectdiscovery/tlsx/internal/runner.(*Runner).Execute
	/Users/geekboy/Github/tlsx/internal/runner/runner.go:122 +0x58

@hktalent It works for me, are you able to reproduce this with the dev branch?
$ go run . -u www.sina.com.cn -probe-status -self-signed

  _____ _    _____  __
 |_   _| |  / __\ \/ /
   | | | |__\__ \>  <
   |_| |____|___/_/\_\  v1.0.0

                projectdiscovery.io

[WRN] Use with caution. You are responsible for your actions.
[WRN] Developers assume no liability and are not responsible for any misuse or damage.
www.sina.com.cn:443 [success]
[INF] Connections made using crypto/tls: 1, zcrypto/tls: 0, openssl: 0

@Mzack9999
go install github.com/projectdiscovery/tlsx/cmd/tlsx@latest


fix err ENOENT #44

We do want to throw this error when a file does not exist. Consumers of cosmiconfig (in this case, stylefmt) need to anticipate the error and act accordingly.


Stuck on old video driver 4.6 mesa 23.1.3

My video drivers are months out of date. I do the regular system updates but it just stays stuck on video driver 4.6 mesa 23.1.3. I am running ChimeraOS on a 5800x3d rx 6900XT system and don't have many issues with anything but would like to try to play Starfield and can't because of these old drivers. Any help on  how to update?

Switch to Unstable build.

My video drivers are months out of date. I do the regular system updates but it just stays stuck on video driver 4.6 mesa 23.1.3. I am running ChimeraOS on a 5800x3d rx 6900XT system and don't have many issues with anything but would like to try to play Starfield and can't because of these old drivers. Any help on how to update?

Do you use Stable 43-1?

Updates are done via the frzr utility when a system image has been tested and patched to ensure as close to a seamless transition as possible. We are currently in the testing phase for v44 which will come with a bump to the current mesa drivers. Please be patient while we work to ensure the most stable image possible.


view projection matrix multiplication

Hey folks, I'm trying to get my math right.
Currently I'm using https://github.com/gingerBill/gb/blob/master/gb_math.h (which is column-major opengl-like mat lib) with bgfx.
So the trouble is matrix ordering. My transformation graph is like this:
all_transforms = proj * view (* parent) * translation * rotation * scale
Considering position vector stands to the right it make sense, such as:
on_screen_pos_vec4 = (proj * (view * (translation * (rotation * (scale * position_vec4)))))
Each matrix multiplication here (let's say viewport * proj = A * B) is we take column from A and multiply it on row from B.
Everything would be fine if all matrix calculations were done outside of bgfx, though we have few exceptions: ordering of proj * view * model and how we multiply stuff in shaders. If we look in here and here plus in bx implementation here and here, one can find that bx uses column-major matrices with result = A * B multiplication operator which takes column of A and rows of B. And looks like in general bx math is designed to be column-major.
Assuming bx code is correct, because we set matrices from outside of bgfx, we get this multiplication order: (translation * rotation * scale) * view * projection which is obviously incorrect considering vec4MulMtx which expects vector from the right.
So the question is:

Does math on bgfx/bx side work correctly, assuming column major-matrices and row-major multiplication order of them?
Should we document this behavior in API/headers?

PS. Currently it's possible to hot fix this in vertex shader by doing something like this:
mat4 projViewWorld = mul(mul(u_proj, u_view), u_model[0]);
gl_Position = mul(projViewWorld, vec4(a_position, 1.0));

why don't you just transpose the matrices that you get from the outside. If you are using row major matrices in your code rowMajorResult = (scale* rotation * translation ) * view * projection  which in col major is basicly the colMajorResult = transpose(rowMajorResult )

@volcoma yes, we can transpose matrices to achieve similar results, I was just curious if there is a bug in bx math or not


[DO NOT MERGE] [Release 0.8] Signal for release

[This will need to be re-run after prototype feature is removed.]


There is no video in Windows 7 VFW

There is a bug that the image size of the output format is zero, this will cause the video frame can't be decompressed. The solution is adding following code in static BITMAPINFOHEADER icvBitmapHeader( int width, int height, int bpp, int compression = BI_RGB ) in cap_vfw.cpp:
"bmih.biSizeImage = widthheightbpp / 8;". I have tested it and passed.

@HawkQing, can you please create pull request with the proposed fix?

I stumbled on this while investigating an issue with video decompression using the Surface 4 camera driver and I don't think this is actually a problem. According to the MSDN documentation the biSizeImage field "may be set to zero for BI_RGB bitmaps" which is what is being created in this case. Just to be sure I tried changing it in my code and it didn't change anything for me.


Error whencreating bot from template.

I'm trying to follow instructions and I get an error, early on.
After I enter this command:
msbot clone services --name goc-bot-demo --luisAuthoringKey XXXX --folder "DeploymentScripts\en" --location westus
It creates almost everything, however I get this error when creating and importing LUIS.  I have verified the LUIS Authoring key.
Command failed: luis import application --region westus --appName "goc-bot-demo_General" --in DeploymentScripts\en\general.luis --authoringKey XXXXX --msbotgetaddrinfo ENOTFOUND westus.api.cognitive.microsoft.com westus.api.cognitive.microsoft.com:443
Any idea what might be causing this problem?

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

ID: 81426100-ac60-c692-0906-f9199deb2a6c
Version Independent ID: f9aa4064-fe22-71c8-6ac3-93b0d0fa1bdd
Content: Enterprise Bot Template Deployment - Bot Service
Content Source: articles/v4sdk/bot-builder-enterprise-template-getting-started.md
Service: bot-service
GitHub Login: @darrenj
Microsoft Alias: darrenj

This topic no longer exists. Closing.


Allow to build certain packages on non-Linux platforms

Following up on https://github.com/cilium/cilium/pull/16679#pullrequestreview-700694405
While building Cilium itself only makes sense for Linux, certain packages are imported by other projects - namely hubble and cilium-cli. These projects are also built for other platforms, mainly macOS and Windows. Moreover, some Cilium developers use macOS and might want to be able to at least build and unit test certain non-Linux-specific bits of Cilium on their development machines without running a VM.
This issue is about compiling a list of packages that should be buildable on non-Linux platforms (though maybe with certain features stubbed out), fixing these packages to build on all platforms and adding a CI test ensuring that future changes don't break them.
Preliminary list of packages
Direct dependencies in cilium-cli and hubble

api/v1/flow
api/v1/models
api/v1/observer
api/v1/peer
api/v1/recorder
api/v1/relay
pkg/hubble/api/v1
pkg/hubble/filters
pkg/k8s/apis/cilium.io/v2
pkg/k8s/client/clientset/versioned, pkg/k8s/client/clientset/versioned/scheme
pkg/monitor/api
pkg/versioncheck

Transitive dependencies in cilium-cli

pkg/version -- ref. #16679
pkg/fqdn, pkg/fqdn/dns, pkg/fqdn/matchpattern -- ref. #16806
pkg/option, pkg/mac, pkg/ip -- ref. https://github.com/cilium/cilium-cli/pull/825#discussion_r862737099
pkg/mtu, pkg/node -- ref. https://github.com/cilium/cilium-cli/pull/958#issuecomment-1318745049
pkg/metrics -- ref. https://github.com/cilium/cilium/pull/28367

Non-Linux specific bits

cilium-operator -- ref. https://github.com/cilium/cilium/pull/16679#issuecomment-876314630
dev-doctor

Others

pkg/cgroups, pkg/health/server, pkg/modules, pkg/mountinfo -- ref. #15355

Related:
#15355
#16679
#16806
https://github.com/cilium/cilium-cli/issues/231

In the meantime both hubble and cilium-cli have been moved in-tree and the tools are built for all supported release platforms as part of CI. This should catch build failures that this issue was trying to address. Thus closing.


birth of V4 SDK

Summary

Related Issue: # (issue number)
Change Type

[ ] Bug Fix
[ ] Refactor
[ ] New Feature
[ ] Breaking Change
[ ] Documentation Update
[ ] Performance Improvement
[ ] Other

Checklist

[ ] My code follows this project's style guidelines
[ ] I've reviewed my own code
[ ] I've added comments for any hard-to-understand areas
[ ] I've updated the documentation if necessary
[ ] My changes generate no new warnings
[ ] I've added tests that prove my fix is effective or my feature works
[ ] All unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published

Additional Information

Branch Naming

LGTM. Shall we merge?

LGTM. Shall we merge?

we have everything merged in v4?


When I Open Just One File in Initialized Git Folder - Source Control Shows Number of Changed Files

VSCode Version: 1.16.1
OS Version: Windows 10 1703 15063.632

When I Open Just One File in Initialized Git Folder - Source Control Shows Number of Changed Files. And project folder is not shows in explorer.
It's a Bug?
Steps to Reproduce:

Open folder with Initialized Git Repository in VSCode and make some changes in files
Then close VSCode
Open only one file from this folder in VSCode (with right mouse button)

Gif Demonstration:

Expected Behavior:
When I open just one file in Initialized Git Folder I need to see only this file. No any information from all project (as on gif).
Reproduces without extensions: Yes

We try to help you and start monitoring git repositories which contain files you edit. We believe this is a good thing.
Would you like a setting to disable this behaviour?

@joaomoreno

Would you like a setting to disable this behaviour?

Yes. If possible it will be great to have.

Do you want to attempt a PR?
I was thinking something like a git.autoRepositoryDetection setting, with a boolean value.

Fixed by https://github.com/Microsoft/vscode/pull/36183


doc formatting fixes

Checklist

[x] documentation is added or updated

This pull request is ready to merge

Merged, thanks for the fixups.


Update requirements.txt

I tried running the evaluate.py and ran into a TON of libraries that needed to be installed.
I wrote down the ones that I had to install. They were all for transformations. I added them in this commit.

Hi @Quetzalcohuatl: You can follow the steps for installation specified in the README.md [https://github.com/GEM-benchmark/NL-Augmenter#installation]. The main requirements.txt will contain some common libraries only and the transformation/filter specific libraries are present in their respective folders. Thanks!
Closing the PR.


Problem installing sentry-laravel (composer conflict)

Hello people,
I did some research before opening this problem and asking for help.
I'm having the following problem in my environment:
user@linux$ composer update --optimize-autoloader --no-dev
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - sentry/sentry-laravel 2.2.0 requires sentry/sdk ^3.0 -> satisfiable by sentry/sdk[3.0.0, 3.0.0-beta1].
    - sentry/sentry-laravel 2.x-dev requires sentry/sdk ^3.0 -> satisfiable by sentry/sdk[3.0.0, 3.0.0-beta1].
    - sentry/sdk 3.0.0 requires sentry/sentry ^3.0 -> satisfiable by sentry/sentry[3.0.0, 3.0.0-beta1, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.x-dev].
    - sentry/sdk 3.0.0-beta1 requires sentry/sentry 3.0.0-beta1 -> satisfiable by sentry/sentry[3.0.0-beta1].
    - sentry/sentry 3.0.0 requires ocramius/package-versions ^1.8 -> satisfiable by composer/package-versions-deprecated[1.10.99, <IP_ADDRESS>, 1.11.99, <IP_ADDRESS>, 1.8.0, 1.8.1, 1.8.2, dev-master, 1.x-dev], ocramius/package-versions[1.10.0, 1.10.1, 1.10.2, 1.10.x-dev,
 1.11.0, 1.11.x-dev, 1.8.0, 1.9.0, 1.9.x-dev].
    - sentry/sentry 3.0.0-beta1 requires ocramius/package-versions ^1.8 -> satisfiable by composer/package-versions-deprecated[1.10.99, <IP_ADDRESS>, 1.11.99, <IP_ADDRESS>, 1.8.0, 1.8.1, 1.8.2, dev-master, 1.x-dev], ocramius/package-versions[1.10.0, 1.10.1, 1.10.2, 1.10.
x-dev, 1.11.0, 1.11.x-dev, 1.8.0, 1.9.0, 1.9.x-dev].
    - sentry/sentry 3.0.1 requires ocramius/package-versions ^1.8 -> satisfiable by composer/package-versions-deprecated[1.10.99, <IP_ADDRESS>, 1.11.99, <IP_ADDRESS>, 1.8.0, 1.8.1, 1.8.2, dev-master, 1.x-dev], ocramius/package-versions[1.10.0, 1.10.1, 1.10.2, 1.10.x-dev,
 1.11.0, 1.11.x-dev, 1.8.0, 1.9.0, 1.9.x-dev].
    - sentry/sentry 3.0.2 requires ocramius/package-versions ^1.8 -> satisfiable by composer/package-versions-deprecated[1.10.99, <IP_ADDRESS>, 1.11.99, <IP_ADDRESS>, 1.8.0, 1.8.1, 1.8.2, dev-master, 1.x-dev], ocramius/package-versions[1.10.0, 1.10.1, 1.10.2, 1.10.x-dev,
 1.11.0, 1.11.x-dev, 1.8.0, 1.9.0, 1.9.x-dev].
    - sentry/sentry 3.0.3 requires ocramius/package-versions ^1.8 -> satisfiable by composer/package-versions-deprecated[1.10.99, <IP_ADDRESS>, 1.11.99, <IP_ADDRESS>, 1.8.0, 1.8.1, 1.8.2, dev-master, 1.x-dev], ocramius/package-versions[1.10.0, 1.10.1, 1.10.2, 1.10.x-dev,
 1.11.0, 1.11.x-dev, 1.8.0, 1.9.0, 1.9.x-dev].
    - sentry/sentry 3.0.4 requires ocramius/package-versions ^1.8 -> satisfiable by composer/package-versions-deprecated[1.10.99, <IP_ADDRESS>, 1.11.99, <IP_ADDRESS>, 1.8.0, 1.8.1, 1.8.2, dev-master, 1.x-dev], ocramius/package-versions[1.10.0, 1.10.1, 1.10.2, 1.10.x-dev,
 1.11.0, 1.11.x-dev, 1.8.0, 1.9.0, 1.9.x-dev].
    - sentry/sentry 3.0.x-dev requires ocramius/package-versions ^1.8 -> satisfiable by composer/package-versions-deprecated[1.10.99, <IP_ADDRESS>, 1.11.99, <IP_ADDRESS>, 1.8.0, 1.8.1, 1.8.2, dev-master, 1.x-dev], ocramius/package-versions[1.10.0, 1.10.1, 1.10.2, 1.10.x-
dev, 1.11.0, 1.11.x-dev, 1.8.0, 1.9.0, 1.9.x-dev].
    - ocramius/package-versions 1.9.x-dev requires php ^7.4.0 -> your PHP version (7.2.34-4+ubuntu16.04.1+deb.sury.org+1) overriden by "config.platform.php" version (7.2.30) does not satisfy that requirement.
    - ocramius/package-versions 1.9.0 requires php ^7.4.0 -> your PHP version (7.2.34-4+ubuntu16.04.1+deb.sury.org+1) overriden by "config.platform.php" version (7.2.30) does not satisfy that requirement.
    - ocramius/package-versions 1.8.0 requires php ^7.4.0 -> your PHP version (7.2.34-4+ubuntu16.04.1+deb.sury.org+1) overriden by "config.platform.php" version (7.2.30) does not satisfy that requirement.
    - ocramius/package-versions 1.11.x-dev requires php ^7.4.7 -> your PHP version (7.2.34-4+ubuntu16.04.1+deb.sury.org+1) overriden by "config.platform.php" version (7.2.30) does not satisfy that requirement.
    - ocramius/package-versions 1.11.0 requires php ^7.4.7 -> your PHP version (7.2.34-4+ubuntu16.04.1+deb.sury.org+1) overriden by "config.platform.php" version (7.2.30) does not satisfy that requirement.
    - ocramius/package-versions 1.10.x-dev requires php ^7.4.7 -> your PHP version (7.2.34-4+ubuntu16.04.1+deb.sury.org+1) overriden by "config.platform.php" version (7.2.30) does not satisfy that requirement.
    - ocramius/package-versions 1.10.2 requires php ^7.4.7 -> your PHP version (7.2.34-4+ubuntu16.04.1+deb.sury.org+1) overriden by "config.platform.php" version (7.2.30) does not satisfy that requirement.
    - ocramius/package-versions 1.10.1 requires php ^7.4.7 -> your PHP version (7.2.34-4+ubuntu16.04.1+deb.sury.org+1) overriden by "config.platform.php" version (7.2.30) does not satisfy that requirement.
    - ocramius/package-versions 1.10.0 requires php ^7.4.7 -> your PHP version (7.2.34-4+ubuntu16.04.1+deb.sury.org+1) overriden by "config.platform.php" version (7.2.30) does not satisfy that requirement.
    - composer/package-versions-deprecated 1.x-dev requires composer-plugin-api ^1.1.0 || ^2.0 -> no matching package found.
    - composer/package-versions-deprecated dev-master requires composer-plugin-api ^1.1.0 || ^2.0 -> no matching package found.
    - composer/package-versions-deprecated 1.8.2 requires composer-plugin-api ^1.1.0 || ^2.0 -> no matching package found.
    - composer/package-versions-deprecated 1.8.1 requires composer-plugin-api ^1.1.0 || ^2.0 -> no matching package found.
    - composer/package-versions-deprecated 1.8.0 requires composer-plugin-api ^1.1.0 || ^2.0 -> no matching package found.
    - composer/package-versions-deprecated <IP_ADDRESS> requires composer-plugin-api ^1.1.0 || ^2.0 -> no matching package found.
    - composer/package-versions-deprecated 1.11.99 requires composer-plugin-api ^1.1.0 || ^2.0 -> no matching package found.
    - composer/package-versions-deprecated <IP_ADDRESS> requires composer-plugin-api ^1.1.0 || ^2.0 -> no matching package found.
    - composer/package-versions-deprecated 1.10.99 requires composer-plugin-api ^1.1.0 || ^2.0 -> no matching package found.
    - Installation request for sentry/sentry-laravel ^2.2 -> satisfiable by sentry/sentry-laravel[2.2.0, 2.x-dev].

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.

Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

My composer file:
{
    "name": "laravel/laravel",
    "description": "The Laravel Framework.",
    "keywords": ["framework", "laravel"],
    "license": "MIT",
    "type": "project",
    "require": {
        "php": "^7.1.3",
        "doctrine/dbal": "^2.9",
        "fideloper/proxy": "^4.0",
        "htmlmin/htmlmin": "^5.7",
        "laravel/framework": "5.7.*",
        "laravel/tinker": "^1.0",
        "laravelium/sitemap": "^3.0",
        "sentry/sentry-laravel": "^2.2",
        "sunra/php-simple-html-dom-parser": "^1.5"
    },
    "require-dev": {
        "barryvdh/laravel-debugbar": "^3.2",
        "beyondcode/laravel-dump-server": "^1.0",
        "filp/whoops": "^2.0",
        "fzaninotto/faker": "^1.4",
        "mockery/mockery": "^1.0",
        "nunomaduro/collision": "^2.0",
        "phpunit/phpunit": "^7.0"
    },
    "autoload": {
        "classmap": [
            "database/seeds",
            "database/factories"
        ],
        "psr-4": {
            "App\\": "app/"
        }
    },
    "autoload-dev": {
        "psr-4": {
            "Tests\\": "tests/"
        }
    },
    "extra": {
        "laravel": {
            "dont-discover": [
            ]
        }
    },
    "scripts": {
        "post-root-package-install": [
            "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""
        ],
        "post-create-project-cmd": [
            "@php artisan key:generate"
        ],
        "post-autoload-dump": [
            "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
            "@php artisan package:discover"
        ]
    },
    "config": {
        "preferred-install": "dist",
        "sort-packages": true,
        "optimize-autoloader": true,
        "platform": {"php": "7.2.30"}
    },
    "minimum-stability": "dev",
    "prefer-stable": true
}

My php version:
user@linux$ php -v
PHP 7.2.34-4+ubuntu16.04.1+deb.sury.org+1 (cli) (built: Oct 18 2020 21:18:57) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.2.34-4+ubuntu16.04.1+deb.sury.org+1, Copyright (c) 1999-2018, by Zend Technologies

Has anyone been through this and managed to solve it? Thanks.

Hi, the issue is not really aptly named because it describes another issue but there is an similar open issue for it with 2 possible solutions that might work for you:

https://github.com/getsentry/sentry-laravel/issues/396#issuecomment-711175256
https://github.com/getsentry/sentry-laravel/issues/396#issuecomment-711373384

Try those out and see if it that works for you! Unfortunately we're still not sure why this is happening but with a future update this should be solved.

Hi, the issue is not really aptly named because it describes another issue but there is an similar open issue for it with 2 possible solutions that might work for you:

#396 (comment)
#396 (comment)

Try those out and see if it that works for you! Unfortunately we're still not sure why this is happening but with a future update this should be solved.

Thank you stayallive, but the solution did not work here.

This does not work for you (I added the sentry/sentry dependency)?
{
    "name": "laravel/laravel",
    "description": "The Laravel Framework.",
    "keywords": ["framework", "laravel"],
    "license": "MIT",
    "type": "project",
    "require": {
        "php": "^7.1.3",
        "doctrine/dbal": "^2.9",
        "fideloper/proxy": "^4.0",
        "htmlmin/htmlmin": "^5.7",
        "laravel/framework": "5.7.*",
        "laravel/tinker": "^1.0",
        "laravelium/sitemap": "^3.0",
		"sentry/sentry": "^3.0.4",
        "sentry/sentry-laravel": "^2.2",
        "sunra/php-simple-html-dom-parser": "^1.5"
    },
    "require-dev": {
        "barryvdh/laravel-debugbar": "^3.2",
        "beyondcode/laravel-dump-server": "^1.0",
        "filp/whoops": "^2.0",
        "fzaninotto/faker": "^1.4",
        "mockery/mockery": "^1.0",
        "nunomaduro/collision": "^2.0",
        "phpunit/phpunit": "^7.0"
    },
    "autoload": {
        "classmap": [
            "database/seeds",
            "database/factories"
        ],
        "psr-4": {
            "App\\": "app/"
        }
    },
    "autoload-dev": {
        "psr-4": {
            "Tests\\": "tests/"
        }
    },
    "extra": {
        "laravel": {
            "dont-discover": [
            ]
        }
    },
    "scripts": {
        "post-root-package-install": [
            "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""
        ],
        "post-create-project-cmd": [
            "@php artisan key:generate"
        ],
        "post-autoload-dump": [
            "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
            "@php artisan package:discover"
        ]
    },
    "config": {
        "preferred-install": "dist",
        "sort-packages": true,
        "optimize-autoloader": true,
        "platform": {"php": "7.2.30"}
    },
    "minimum-stability": "dev",
    "prefer-stable": true
}

Make sure to run composer update and possibly remove your vendor folder and/or composer.lock file to see if that helps.

This is should have been solved at least starting on version 2.3.0 maybe earlier.
I hope this also is solved for you, if not please re-open so we can investigate further!


Missing H264 decoder on Ubuntu 15.04

I get the following build error on Ubuntu 15.04, even though I've fetched all the documented dependencies.
/home/jake/catkin_ws/src/bebop_autonomy/bebop_driver/src/bebop_video_decoder.cpp:
In member function bool bebop_driver::VideoDecoder::InitCodec(uint32_t,
uint32_t):
/home/jake/catkin_ws/src/bebop_autonomy/bebop_driver/src/bebop_video_decoder.cpp:79:39:
error: CODEC_ID_H264 was not declared in this scope
codec_ptr_ = avcodec_find_decoder(CODEC_ID_H264);

Works fine on Ubuntu 14.04. Incompatibility with 15.04 could be considered a feature rather than a bug, given the versions that ROS supports.

Thank you for reporting this. I think it's a bug since the driver should be compilable on all distros that support ROS Jade.

It has been fixed in 8da8e188d1c6dd210d1d55937f59be5b4dfd5e98 .


How to save incremental changes to the index?

Hi Yury - When this index is used in production in a real use-case scenario, users would add vectors incrementally and would want to save incremental changes. Suppose the index is already 100 GB (just making up a number) and I save the index. Then a add a few vectors - say 1000. I would now like to persist the changes to disk but I don't want to write the whole index again from scratch. Does the library handle that? How?

Hi @siddhsql,
The library does not handle it. During insertions the graph of the previously added elements also change. One can save the delta, but the delta is sparse and storing it might take even more space.


Check that the argument passed to freeaddrinfo(3) is not NULL.

freeaddrinfo(NULL) will crash on OpenBSD and NetBSD, and also on systems
using musl libc such as Alpine Linux.

Thank you!


Unable to Verify Ghost Event Using Webhook

Issue Summary
Issue Title: Unable to Verify Ghost Event Using Webhook
Problem:
I am currently working on integrating webhooks from my Ghost website into my server, and I'm having trouble understanding how to verify that the events received by my server are indeed from my Ghost website and not from a potential malicious source.
Context:
I have set up webhooks in my Ghost website to notify my server of certain events such as new post creation, but I'm not sure how to implement authentication or headers to ensure that the incoming events are legitimate.
Request:
I would greatly appreciate it if someone could provide guidance on how to properly verify the authenticity of Ghost events received via webhooks. It would be especially helpful if there are specific steps or code examples that can be shared to illustrate the process.
Steps to Reproduce
Create a webhook
Send an  event
Ghost Version
Version: 5.67.0 Environment: Production Database: mysql8 Mail: SMTP
Node.js Version
Latest node version using alpine docker container
How did you install Ghost?
Docker
Database type
MySQL 8
Browser & OS version
Safari
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

This appears to be not a bug report but a feature request or support request.
Please ask this question at https://forum.ghost.org/
I'll look for it there.

You're right


Make pex ready

Moved things around so that we can easily create PEX files.

LGTM, ship it!

Coverage decreased (-6.39%) when pulling fb9bab5a34d428e45c19bc2a477fa2594ea65b59 on rgs1:make-pex-ready into 7a7565c5f9b4952934e16f8fbb6d7e3e581cce8a on twitter:master.


Native ALPN support in Java9

JDK9 with JEPS-244 appears to have native ALPN support. We're looking to use pushy for a project and like to know if any external libraries are needed for ALPNs support now, or is JDK9 sufficient?

I haven't tried it myself, but my understanding is that it should just work. To try it, you'd need to exclude netty-tcnative as a dependency and make sure you don't have alpn-agent as a javaagent or alpn-boot on your boot classpath.
Please let us know how it goes.


Output error when the response of deploygate.com has an error param

DeployGate can return a response with status code 200 and an error of body.
ipa distribute:deploygate command outputs Build successfully uploaded to DeployGate like below when a user set an invalid token. It's an inappropriate message because uploading is failed in fact.
$ ipa distribute:deploygate -a [INVALID_TOKEN] -u yoheimuta -f DemoApp.ipa -m "dummy message" -n
Build successfully uploaded to DeployGate

I think the response with error should cause to output an error message and be aborted like below.
# Used an invalid API key
$ ipa distribute:deploygate -a [INVALID_TOKEN] -u yoheimuta -f DemoApp.ipa -m "dummy message" -n
Error uploading to DeployGate: code=200, body={"error"=>true, "message"=>"you are not authenticated", "because"=>"you are not authenticated"}
# Used a valid API key
$ ipa distribute:deploygate -a [VALID_TOKEN] -u yoheimuta -f DemoApp.ipa -m "dummy message" -n
Build successfully uploaded to DeployGate

Merged with refactoring in afa72fd995c8c949a1df38648b243a5b8aa32ecd. Thanks, @yoheimuta!


How can i resolve domain by the clientIP?

Hi:
I`m confused by the dns resolve through the cllientIP, which i meaned is different region client resolve the same domain should get the different result.
Give me some advice,please.
best regards~

look the geodns project: https://github.com/abh/geodns project.

look the geodns project: https://github.com/abh/geodns

look the geodns project: https://github.com/abh/geodns

Can miekg/dns support it?

it uses miekg/dns.

Out of scope for this library.
On Tue, 13 Nov 2018, 16:24 Yasar Alev<EMAIL_ADDRESS>wrote:

it uses miekg/dns.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/miekg/dns/issues/812#issuecomment-438333892, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAVkW-z3mC-M5yMOHeIFy9Eo7yjbVUdiks5uuvI-gaJpZM4Ya9x8
.


Shutdown() panic under certain conditions

I believe the code in func (d *Discovery) Shutdown() error  must guard against d.memberList being nil.
Under certain startup conditions, memberList may not be fully initialized by the time this code runs.
If I can re-create the condition I'll post more details.

Hi @aathan, thank you for reporting this.
I'll investigate the problem. Is there any traceback for this problem? Which version do you use? v0.5.x tree already has a nil check in Discovery.Shutdown.

Hello,
I have backported the fix and released v0.4.6. I'm closing this issue now. If you have any further problems or questions, please don't hesitate to open an issue.


swc_bundler: does not properly bundle circular dependencies

Describe the bug
swc_bundler does not properly bundle circular dependencies.
Input code
circular1.ts
import * as circular2 from "./circular2.ts";

export function f1(): void {
  console.log("f1");
}

circular2.f2();

circular2.ts
import * as circular1 from "./circular1.ts";

export function f2(): void {
  console.log("f2");
}

circular1.f1();

Expected behavior
An emit something like:
function f2() {
    console.log("f2");
}
export function f1() {
    console.log("f1");
}
f1();
f2();

Current bundling outputs:
export function f1() {
    console.log("f1");
}
circular2.f2();
circular1.f1();

Version
Version: swc_bundler 0.9.1, swc_ecmascript 0.8.4, swc_common 0.10.3
Additional context
Working to integrate swc_bundler into Deno.  This is integration test "bundle_circular".

The emit is now:
export function f1() {
    console.log("f1");
}
f2();
function f2() {
    console.log("f2");
}
f1();

Which is technically slightly incorrect as this would result in:
f2
f1

Where as if the modules were loaded separately, it would result in:
f1
f2


Custom validation functions support

It may be useful to allow the caller to provide their own validation functions.
This PR adds support for overriding the default validation function globally or on a per-context basis.

Coverage increased (+0.1%) to 93.109% when pulling 3e11be4d75f3d6c0105c8888d246eced9351ca52 on allrod5:validate-function into 8944594b06276766d35af6058c00dd2b8ce8b49b on rochacbruno:master.

Coverage increased (+0.1%) to 93.109% when pulling 9fbcd07556a0ed4a2f598cc366de6e5d1538f141 on allrod5:validate-function into 8944594b06276766d35af6058c00dd2b8ce8b49b on rochacbruno:master.

Coverage increased (+0.1%) to 93.109% when pulling 9fbcd07556a0ed4a2f598cc366de6e5d1538f141 on allrod5:validate-function into 8944594b06276766d35af6058c00dd2b8ce8b49b on rochacbruno:master.

@allrod5 there are some conflicts because I merged your first PR first

Coverage increased (+0.05%) to 93.093% when pulling b0a017cf8e33d0de4981afd2173363e26243da1c on allrod5:validate-function into c9c5e491d4b35d4823c31a38bce7af6aafc7c485 on rochacbruno:master.

@rochacbruno Resolved'em

Coverage increased (+0.05%) to 93.093% when pulling 2b1743af0adc17841917b84915eeb5d5962cc3ea on allrod5:validate-function into c9c5e491d4b35d4823c31a38bce7af6aafc7c485 on rochacbruno:master.

Coverage increased (+0.05%) to 93.093% when pulling 3de2c9de5ee6a8c1faf48cb622323b152283ac25 on allrod5:validate-function into c9c5e491d4b35d4823c31a38bce7af6aafc7c485 on rochacbruno:master.


Stripping types should include ts-ignore comments

TypeScript Version:  3.8 latest, playground
Search Terms: remove ts-ignore comment
Code
// this is a comment that should be kept
const message: string = 'hello world';
// the below ts-ignore comment should be removed, since it has no meaning in a non-TS context
// @ts-ignore
console.log(message);

Expected behavior:
ts-ignore comment is stripped, other comments are kept.
Actual behavior:
all comments are kept including ts-ignore comments.
Playground Link: https://www.typescriptlang.org/play/#code/PTAEBcAsEsGdTqAhqAxgewLaYKYDtwJIlDZJ0BXAGwBNQAjHUAaxwAdwAoDPWQ3WLCQBzHAC5QfAE7Q8w0AF5QAckg4qVdKADu6KbWUBuTiCJNGm7RFgBaaMLx6mGbPlLlqJsAAFwt+45SONzovOhUOAB0msIAFAJCogCUhkA
Related Issues:

I do want to point out that @ts-ignore doesn't have to be on it's own line, you can write this
declare function doThingWithNumber(val:number): void
// this is a comment that should be kept
const message: string = 'hello world';
// @ts-ignore because this isn't expected to fail at runtime ever but might.
doThingWithNumber(message);

I would definitely not want the whole line to be removed, I'd kind of argue that just keeping the whole line makes a bit more sense than modifying the comment to only remove the @ts-ignore, especially since other compiler orders like @eslint-disable-next-line are still kept.

I don’t agree; ts-ignore is a directive to tsc, and once tsc has run, it’s irrelevant. The extra context is for the ts-ignore and is also irrelevant once emitted.

Eslint commands are for eslint; those are none of typescript’s business.

I was actually surprised to find @ts-expect-error comments in my generated .js files. Like @ts-ignore, these are pointless outside TypeScript code.

I was actually surprised to find @ts-expect-error comments in my generated .js files. Like @ts-ignore, these are pointless outside TypeScript code.

I was even running into issues where explicitly escaping a type error with @ts-expect-error was compiled to js code where that type error was no longer detected, failing our tests (because the expected error did not occur).

+1 to having an option to remove // @ts-ignore.
I'm using TypeScript to generate Adobe-friendly JS and ExtendScript which is really picky about comments with @ symbols.


Make SQBs composable for more flexible querying

Is your feature request related to a problem? Please describe.
Being able to compose query builders together to create subqueries would be a useful feature.
Describe the solution you'd like
Not sure about the exact Python syntax I want for this. It will require more thought and probably a substantial refactor.
Additional context
Some common use cases for subqueries are where in and where not in.

Another use case: select [columns] from ([subquery])

Two more:

select [columns] from [table] where [column] = ([subquery])
select [columns] from [table] join ([subquery]) [join_alias] on [table.column] = [join_alias.column]


Feature/kweiss/multimat_revamp

Summary

This PR is to fix the multimat unit tests
It does the following:

Make unit test compatible with the new layout-per-field feature
Fix traversal to run with just 1 component (until field2D with higher number of components are added)
Reduce unit test to use 1 component as that's temporarily hard-coded

Thanks @raineyeh !
Looks like there's a compiler error with our gcc8 test related to an incompatible return type for `SubMap::size()``
Could you please look into it?
https://dev.azure.com/healy22/Status Check Testiing/_build/results?buildId=3393&view=logs&j=1e949c51-e916-5ae4-436c-7a23f916c6ae&t=3cb93f51-2f5f-529e-e892-962657e1e8f0


Cannot build Realm as a static framework with Carthage

Goals
Carthage provides a handy guide on how to build your dependencies as static frameworks rather than dynamic frameworks. So far, this has worked great -- except for Realm.
My goal is to build all of my Carthage dependencies as static frameworks so that they don't have to be loaded dynamically when the app is launched, increasing launch time.
I am using the directions listed here:
https://github.com/Carthage/Carthage/blob/5b2d2ad23e740dd93cd81e8f273c013a15c490ff/Documentation/StaticFrameworks.md
Expected Results
The output of file Realm.framework/Realm should include current ar archive to indicate a static framework.
Actual Results
*** xcodebuild output can be found in /var/folders/b7/xhtbl2xn6_d46d9w6wjc_sd80000gn/T/carthage-xcodebuild.hK8fLb.log
*** Building scheme "Alamofire iOS" in Alamofire.xcworkspace
*** Building scheme "Nimble-iOS" in Nimble.xcodeproj
*** Building scheme "Quick-iOS" in Quick.xcworkspace
*** Building scheme "Realm" in Realm.xcworkspace
*** Building scheme "RealmSwift" in Realm.xcworkspace
*** Building scheme "SnapKit" in SnapKit.xcworkspace

maxmeyers$ file Carthage/Build/iOS/RealmSwift.framework/RealmSwift
Carthage/Build/iOS/RealmSwift.framework/RealmSwift: Mach-O universal binary with 4 architectures: [arm_v7:current ar archive] [arm64]
Carthage/Build/iOS/RealmSwift.framework/RealmSwift (for architecture armv7):	current ar archive
Carthage/Build/iOS/RealmSwift.framework/RealmSwift (for architecture i386):	current ar archive
Carthage/Build/iOS/RealmSwift.framework/RealmSwift (for architecture x86_64):	current ar archive
Carthage/Build/iOS/RealmSwift.framework/RealmSwift (for architecture arm64):	current ar archive

maxmeyers$ file Carthage/Build/iOS/Realm.framework/Realm
Carthage/Build/iOS/Realm.framework/Realm: Mach-O universal binary with 4 architectures: [i386:Mach-O dynamically linked shared library i386] [arm64]
Carthage/Build/iOS/Realm.framework/Realm (for architecture i386):	Mach-O dynamically linked shared library i386
Carthage/Build/iOS/Realm.framework/Realm (for architecture x86_64):	Mach-O 64-bit dynamically linked shared library x86_64
Carthage/Build/iOS/Realm.framework/Realm (for architecture armv7):	Mach-O dynamically linked shared library arm_v7
Carthage/Build/iOS/Realm.framework/Realm (for architecture arm64):	Mach-O 64-bit dynamically linked shared library arm64

RealmSwift is build correctly as a static framework, but Realm continues to build as a dynamic framework. Additionally, all of the other frameworks in our Cartfile are built as static frameworks.
Steps to Reproduce

Set up ld.py and carthage-build-static.sh as indicated in the link above
Run ./carthage-build-static.sh --platform iOS
file Carthage/Build/iOS/Realm.framework/Realm

Version of Realm and Tooling

Realm framework version: github "realm/realm-cocoa" "v2.8.3"
Realm Object Server version: N/A
Xcode version: Version 9.2 (9C40b)
iOS/OSX version: 10.13.2 (17C88)
Dependency manager + version: 0.27.0

@maxmeyers did you file a Carthage issue or changed the script to fix it? Am trying to follow the path you did, and any help is appreciated!

I did not do either of those things.
But CocoaPods just recently announced support for Swift static libraries, so that's probably what we'll try next.

I'm having issues using Carthage in any capacity with realm-cocoa-converter.

@jhoughjr This issue is closed. Please open another with all needed details (specially on how to reproduce). Thanks!


fix deduction not properly working

This should finally fix bfgroup/b2#368.
Background. After my b2 PR (bfgroup/b2#375) was merged, the build system is properly creating two alternatives for checked libraries (e.g. /openssl//ssl): before the deduced properties are added, and after that. What this does not result in, though, is build system actually compiling and linking corresponding files twice. This is because deduced-X are hidden features, and they do not affect the target path. As a result foo.o with address-model=32 , and foo.o with address-model=32 deduced-architecture=x86 result in the same file (e.g. gcc-13/debug/address-model-32/threading-multi/visibility-hidden/foo.o, notice the lack of architecture).
After some thinking, I decided that this is a flaw in how deduced platform features are implemented. They should not be hidden, because their presence affects binary compatibility.
This change removes deduced-X features, as their only purpose was hiding the related property from the path. Instead it fully relies on conditional property adding the deduced values for X feature if necessary.
NOTE: the unfortunate result of this change is that all targets in a Boost build will get architecture-A and address-model-M parts in the path.

That's probably the right thing to do, but it has the potential to breaking previously working builds on Windows due to path limits.
I'm not sure whether there's anything we can do about that, though.

(References https://github.com/bfgroup/b2/pull/375).

Yeah, I'm hitting Windows path limits when building with MinGW-w64:
...failed gcc.compile.c++ ..\..\bin.v2\libs\uuid\test\~hdr-decl-detail-basic_name_generator~hpp.test\gcc-8\release\address-model-64\architecture-x86\cxxstd-14-iso\threadapi-win32\threading-multi\visibility-hidden\~hdr-decl-detail-basic_name_generator~hpp.o...
gcc.compile.c++ ..\..\bin.v2\libs\uuid\test\~hdr-decl-detail-basic_name_generator~hpp.test\gcc-8\release\address-model-64\architecture-x86\cxxstd-1z-iso\threadapi-win32\threading-multi\visibility-hidden\~hdr-decl-detail-basic_name_generator~hpp.o
Assembler messages:
Fatal error: can't create ..\..\bin.v2\libs\uuid\test\~hdr-decl-detail-basic_name_generator~hpp.test\gcc-8\release\address-model-64\architecture-x86\cxxstd-1z-iso\threadapi-win32\threading-multi\visibility-hidden\~hdr-decl-detail-basic_name_generator~hpp.o: No such file or directory

If we keep this, https://github.com/bfgroup/b2/issues/378 will be urgently required. Or we need to figure out a way to enable --abbreviate-paths on the Boost side if B2 doesn't cooperate.

Another option is to special-case architecture and address-model and instead of adding address-model-64/architecture-x86/ to the path, just add x86-64/ to it.

https://github.com/boostorg/boost/pull/898


Add a way to get network interfaces without ifconfig

Apparently on some clusters ifconfig is configured to need root access. This was mentioned by @Phantom139 in https://github.com/dask/dask-jobqueue/issues/298.

OK I am going to merge this one.


Default value should be used in config when not set

Summary
On my work laptop, the user that's been configured has a different name from my personal laptop, so the root: path: setting which was generated does not work. I tried removing it, but when I run gopass I get the error: No gpg binary found: failed to init root store: need path
Steps To Reproduce

Remove the value for path from the root config.
Run a gopass command

Expected behavior
Running gopass commands should use the default values if they're not set in the config. Because my password store is at ~/.password-store on all my machines, gopass commands should work without setting the path.
Environment

OS: macOS High Sierra
OS version: Darwin sea-42-laptop.internal 17.5.0 Darwin Kernel Version 17.5.0: Fri Apr 13 19:32:32 PDT 2018; root:xnu-4570.51.2~1/RELEASE_X86_64 x86_64
gopass Version: gopass 1.7.2-git+HEAD go1.10.1 darwin amd64  - gpg 2.2.7 - git 2.17.0 - fs 0.1.0
Installation method: built manually from c36481bb9703c2d3b8918ab941c9e679a78ad638

Additional context
N/A

Thanks for reporting this issue. I agree that this is not optimal. We'll see how we can make it use a sensible default value.

Thanks for the quick response! Works great! Are there any plans to do this for all config values, or do you plan to stick with only the path?

The plan is to fall back to safe defaults for any config option in case it's not set.


privacy policy?

This extension seems to use Google Analytics for tracking, but I could not find any documentation that mentions what data is collected, how it is used, and/or who it is accessible to.
Both the Google Chrome Web Store Terms of Service and the Google Analytics Terms of Service seem to mandate use of a privacy policy.

There really isn't much to say, because the Analytics are used at its minimum

I was auditing my Chrome extensions today and saw that more data is being sent to Google Analytics than before. It looks like d353cc9d9fc69877b0adb15e879b566672fdf5cc and 0e207145d5a7d1dec74c1eece0dd5caa07917eff increased the amount of Google Analytics tracking, and that behavior around notifications and the artist and track being scrobbled is now being tracked.
Despite the fact that these changes were made in June and September of 2014, the privacy policy has not been updated to account for them. Even if it had, it's doubtful that anyone installing it would notice, since the privacy policy is still not linked from anywhere in the extension's description in the Chrome Web Store.
I really think:

the privacy policy should be linked from the extension's description in the Web Store and on the project's README
users should be prompted upon installation whether they want to enable Google Analytics tracking
all existing data in Google Analytics should be deleted, since none of the users who submitted it agreed to have it collected

Hi @david-sabata, any comment on the pull requests that @inverse made?

Hey @martey. To be honest I don't know why I added tracking of artist and track. It's like a year ago and  I don't think I looked at the data once. So I removed the code - 2e6646e12
As for the other commit you reference - it tracks notifications showing up, being clicked or failing. I believe that falls into "the extension usage tracking" noted in the privacy policy.
I also merged opt-out checkbox in settings and link to the privacy policy on the same page.
And last thing - GA data. I haven't found a way to selectively remove only the events data and I definitely don't agree that all data in GA should be removed.

Closing as I feel this is solved.


Broken link for advanced example

When I click the advanced template example link on the readme I get a GitHub 404 page.

Thanks for the report. I moved the repo last week and forgot to update the links. Will fix later today.

@chmac : Updated the README. https://github.com/cloud-atlas-ai/obsidian-ics/discussions/74 for your convenience.

@muness Awesome, thanks for the super fast response!


MCH halo cell exchange generic

Hello @ajocksch, Thank you for submitting the Pull Request!

In the file cscs-checks/mch/collectives_halo.py:

Line 68:9: E722 do not use bare 'except'
Line 70:23: E126 continuation line over-indented for hanging indent
Line 73:19: E126 continuation line over-indented for hanging indent

Do see the ReFrame Coding Style Guide

I hope it is generic enough; the new else branch is a bit guesswork

@jenkins-cscs retry none

Codecov Report

Merging #826 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #826   +/-   ##
=======================================
  Coverage   91.81%   91.81%
=======================================
  Files          80       80
  Lines        9982     9982
=======================================
  Hits         9165     9165
  Misses        817      817

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 2f05307...be081fe. Read the comment docs.


Update GSoC website

compile devoworm and OREL alumni efforts

@Orthogonal-Research-Lab - I've put the link in slack - let me know for other updates and links to add
https://www.jopro.org/mentoring-programs/google-summer-of-code-orel-devoworm

@jesparent check slack / discussion for Bradly's update


[NYS2AWS-71] allow node anti-affinity for Solr pods

https://xenitsupport.jira.com/browse/NYS2AWS-71
For DSNY, we need an option to enforce hostname anti-affinity for the Solr pods.
The goal of this PR is to support this functionality.

Hostname affinity is not enough, the EBS storage is linked to a zone, if you want spreading across different zones you should look at **topology.kubernetes.io/zone**=eu-west-1a
Therefore I would not call it hostnameAntiAffinity

@gert-glassee I rewrote the code to address this issue; can you check again? :)


Fails to properly escape the ;, {, }, <, and > characters

This may potentially allow a remote attacker to execute arbitrary commands.

This bug does not allow browserify under debian... Could you please fix it ?

Hey @atelic, can you provide an example how it fails to properly escape the mentioned characters?

Hello guys,
I could someone please add more details about the bug. @atelic @bastien-roucaries ?
Test case? anything.

see #19


Split Profanity.yml into three according to the profanity sureness by cuss tool

Split Profanity.yml into three (Likely, Maybe, Unlikely) according to the profanity sureness provided by cuss tool

Thanks! I'll get a new release out soon.


How to perform emergency stop when collision happens?

Hi everyone! When running automatic_control.py in CARLA 0.9.10, I notice that the vehicle will keeping moving after collision which is far from the reality. I'm wondering how vehicle can perform emergency stop after collision and then keep static.
To achieve this, I've made a few tries, but it doesn't work.
①CollisionSensor: automatic_control.py defines _on_collision() to illustrate the reaction on collision , but it's just statistical for HUD. Consequently, I add the reaction control through apply_control. However, it fails probably because the emergence stop command only work when collision happens. So the vehicles must keep colliding to maintain braking which is unrealistic.
Code:
def _on_collision(weak_self, event):
"""On collision method"""
self = weak_self()
if not self:
return
self._parent.apply_control(carla.VehicleControl(steer=0.0, throttle=0.0, brake=1.0, hand_brake=False))
actor_type = get_actor_display_name(event.other_actor)
self.hud.notification('Collision with %r' % actor_type)
impulse = event.normal_impulse
intensity = math.sqrt(impulse.x ** 2 + impulse.y ** 2 + impulse.z ** 2)
self.history.append((event.frame, intensity))
if len(self.history) > 4000:
self.history.pop(0)
②Agent: The mechanism of vehicle in automatic_control.py is agent. However, it's hard for agent to obtain collision information.(which is easy for actor)
If you have any insight, please give me some advices, thanks in advance!

Hey @EchoYJJ. According to your comment, "I'm wondering how vehicle can perform emergency stop after collision and then keep static.". This is exactly what you are doing with the collision sensor, you detect a collision, stop, and then when the collision is over, start again. If you want it to remain static my question is, until when? You'd have to add some kind of condition / timer once a collision is detected that will keep the vehicle static.
Regarding agents, what they try to do is predict whether or not a close-by actor is in their route, braking before they collide with it, but this is done using only waypoint lanes and roads, which fail miserably at junctions. We updated the agents for 0.9.12 but that is still an issue we have to resolve. In order to detect collisions, you can just copy the code that implements a collision sensor at automatic_control.py, and when a collision occurs, change a class varaible that you are monitoring on runtime.
Did any of this help? Not sure exactly what you are trying to do so I might be talking about something completely unrelated

Hi @glopezdiest ,thanks a lot for your reply. It really helps!


fix array_subindex() calls in polygon_clockwise()

The code has calls to array_subindex() that need to be updated to subindex().

Fixed in 34f9677035be27ccf517c948d75bcea31da1a935


onChange target is generic Element insted of HTMLInputElement or an element with value property

Description
When using the new onChange event, if I try to access event.target.value, typescript will throw this error: Property 'value' does not exist on type 'Element'.
If applicable, a MRE
https://stackblitz.com/edit/superforms-2-testing-cvxhuj?file=src%2Froutes%2F%2Bpage.svelte
Stackblitz doesn't seem to highlight typescript errors, but it's there.

Is it possible to provide a way to discriminate which type of input it is?
It would also be useful to have an accessor to the changed value

I have to be certain that the input cannot be something else, before narrowing the type. In the meantime, you can use something like if(e.target instanceof HTMLInputElement || e.target instanceof HTMLOptionElement)
Nice idea about the accessor, will add that in a future release.

@ciscoheat  For update forms, could it be possible to have a data comparator?
Let's say I want to add a button that's disabled as long as the data of the form hasn't change. If it's different than the initial data before submitting, it should somehow be true (data changed).

You can use isTainted for that: https://superforms.rocks/whats-new-v2#new-istainted-method

You can use isTainted for that: https://superforms.rocks/whats-new-v2#new-istainted-method

You are the greatest, it works perfectly! Thank you very much.

I'm gonna close this after reading the HTML specificationq Element has to be the default, since elements with contenteditable can also trigger the input event, so it can be pretty much anything.


Stage Arabic licenses for proofing

See: https://www.dropbox.com/s/pcueh9h1no2qmwy/Arabic HTML.rar?dl=0

Staged, but formatting is off. @robmyers can you help us discern what is wrong and/or missing in the HTML?
Links here:
http://cc4-ar-legalcode.legal.creativecommons.org/licenses/by-nc-sa/4.0/legalcode.ar
http://cc4-ar-legalcode.legal.creativecommons.org/licenses/by-nc/4.0/legalcode.ar
http://cc4-ar-legalcode.legal.creativecommons.org/licenses/by/4.0/legalcode.ar
http://cc4-ar-legalcode.legal.creativecommons.org/licenses/by-sa/4.0/legalcode.ar
http://cc4-ar-legalcode.legal.creativecommons.org/licenses/by-nc-nd/4.0/legalcode.ar
http://cc4-ar-legalcode.legal.creativecommons.org/licenses/by-nd/4.0/legalcode.ar
The files all now live in this branch: cc4-ar-legalcode/docroot
Thank you!

It looks like they have the wrong  code . We should replace it (except for the ) with something more like:
http://cc4-no-legalcode.legal.creativecommons.org/licenses/by-nc-sa/4.0/legalcode.no
The footer looks OK so probably doesn't need changing for this.

Attempted to fix header on by-nc-nd, and now nothing is on page. Fail.
http://cc4-ar-legalcode.legal.creativecommons.org/licenses/by-nc-nd/4.0/legalcode.ar
Can you tell what I did wrong @robmyers?

Definitely agree this is a really hard thing to do via Github! I'm going to try asking the team if someone knows how to fix it on their end. If not, you and I can go through it during our checkin next Tuesday.

OK cool. Yes this does sound like a good candidate for our checkin.

Any progress on this @robmyers @sarahpearson? If one of you could get back to the team on the main list that would be good. Mohammad is standing by to conduct the final proof. Thanks!

Rob and I have a call later this afternoon, and we'll discuss. I know he fixed the numbering, so the only thing left was integrating Hani's latest changes. One of us will update the thread shortly.


[BUG] org.opensearch.action.admin.indices.create.CreateIndexIT.testCreateAndDeleteIndexConcurrently flaky

https://github.com/opensearch-project/OpenSearch/pull/5418#issuecomment-1333013481
https://build.ci.opensearch.org/job/gradle-check/7464/
Not reproducible.
./gradlew ':server:internalClusterTest' --tests "org.opensearch.action.admin.indices.create.CreateIndexIT" -Dtests.seed=EA9B1803756CB3DA -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=en -Dtests.timezone=Etc/UTC -Druntime.java=19

https://github.com/opensearch-project/OpenSearch/issues/2105 may be related

[2023-12-14T03:22:51,283][WARN ][o.o.i.c.IndicesClusterStateService] [node_t2] [test][1] marking and sending shard failed due to [failed recovery]
org.opensearch.indices.recovery.RecoveryFailedException: [test][1]: Recovery failed from {node_t1}{unJbKf_RSSagBnE440OOrw}{a775_BliR_WvTYflMVyh7g}{<IP_ADDRESS>}{<IP_ADDRESS>:53213}{dimr}{shard_indexing_pressure_enabled=true} into {node_t2}{BzqQ9aUKSOWk7GHnGn8-Xg}{mKanlBDeSOavIkjr4PtdOQ}{<IP_ADDRESS>}{<IP_ADDRESS>:53215}{dimr}{shard_indexing_pressure_enabled=true} ([test][1]: Recovery failed from {node_t1}{unJbKf_RSSagBnE440OOrw}{a775_BliR_WvTYflMVyh7g}{<IP_ADDRESS>}{<IP_ADDRESS>:53213}{dimr}{shard_indexing_pressure_enabled=true} into {node_t2}{BzqQ9aUKSOWk7GHnGn8-Xg}{mKanlBDeSOavIkjr4PtdOQ}{<IP_ADDRESS>}{<IP_ADDRESS>:53215}{dimr}{shard_indexing_pressure_enabled=true})
	at org.opensearch.indices.recovery.RecoveryTarget.notifyListener(RecoveryTarget.java:136) [classes/:?]
	at org.opensearch.indices.replication.common.ReplicationTarget.fail(ReplicationTarget.java:180) [classes/:?]
	at org.opensearch.indices.replication.common.ReplicationCollection.fail(ReplicationCollection.java:212) [classes/:?]
	at org.opensearch.indices.recovery.PeerRecoveryTargetService$RecoveryResponseHandler.onException(PeerRecoveryTargetService.java:751) [classes/:?]
	at org.opensearch.indices.recovery.PeerRecoveryTargetService$RecoveryResponseHandler.handleException(PeerRecoveryTargetService.java:681) [classes/:?]
	at org.opensearch.telemetry.tracing.handler.TraceableTransportResponseHandler.handleException(TraceableTransportResponseHandler.java:81) [classes/:?]
	at org.opensearch.transport.TransportService$ContextRestoreResponseHandler.handleException(TransportService.java:1497) [classes/:?]
	at org.opensearch.transport.InboundHandler.lambda$handleException$5(InboundHandler.java:447) [classes/:?]
	at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:852) [classes/:?]
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
	at java.base/java.lang.Thread.run(Thread.java:840) [?:?]
Caused by: org.opensearch.indices.recovery.RecoveryFailedException: [test][1]: Recovery failed from {node_t1}{unJbKf_RSSagBnE440OOrw}{a775_BliR_WvTYflMVyh7g}{<IP_ADDRESS>}{<IP_ADDRESS>:53213}{dimr}{shard_indexing_pressure_enabled=true} into {node_t2}{BzqQ9aUKSOWk7GHnGn8-Xg}{mKanlBDeSOavIkjr4PtdOQ}{<IP_ADDRESS>}{<IP_ADDRESS>:53215}{dimr}{shard_indexing_pressure_enabled=true}
	... 9 more
Caused by: org.opensearch.transport.RemoteTransportException: [node_t1][<IP_ADDRESS>:53213][internal:index/shard/recovery/start_recovery]
Caused by: org.opensearch.index.engine.RecoveryEngineException: Phase[1] prepare target for translog failed
	at org.opensearch.indices.recovery.RecoverySourceHandler.lambda$prepareTargetForTranslog$22(RecoverySourceHandler.java:627) ~[classes/:?]
	at org.opensearch.core.action.ActionListener$1.onFailure(ActionListener.java:90) ~[classes/:?]
	at org.opensearch.core.action.ActionListener$4.onFailure(ActionListener.java:192) ~[classes/:?]
	at org.opensearch.core.action.ActionListener$6.onFailure(ActionListener.java:311) ~[classes/:?]
	at org.opensearch.action.support.RetryableAction.cancel(RetryableAction.java:127) ~[classes/:?]
	at org.opensearch.indices.recovery.RetryableTransportClient.lambda$cancel$1(RetryableTransportClient.java:120) ~[classes/:?]
	at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:852) ~[classes/:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
	at java.lang.Thread.run(Thread.java:840) ~[?:?]
Caused by: org.opensearch.common.util.CancellableThreads$ExecutionCancelledException: retryable action was cancelled
	at org.opensearch.indices.recovery.RetryableTransportClient.cancel(RetryableTransportClient.java:116) ~[classes/:?]
	at org.opensearch.indices.recovery.RemoteRecoveryTargetHandler.cancel(RemoteRecoveryTargetHandler.java:267) ~[classes/:?]
	at org.opensearch.indices.recovery.RecoverySourceHandler.cancel(RecoverySourceHandler.java:890) ~[classes/:?]
	at org.opensearch.indices.recovery.PeerRecoverySourceService$OngoingRecoveries.cancel(PeerRecoverySourceService.java:298) ~[classes/:?]
	at org.opensearch.indices.recovery.PeerRecoverySourceService.beforeIndexShardClosed(PeerRecoverySourceService.java:146) ~[classes/:?]
	at org.opensearch.index.CompositeIndexEventListener.beforeIndexShardClosed(CompositeIndexEventListener.java:121) ~[classes/:?]
	at org.opensearch.index.IndexService.closeShard(IndexService.java:634) ~[classes/:?]
	at org.opensearch.index.IndexService.removeShard(IndexService.java:618) ~[classes/:?]
	at org.opensearch.index.IndexService.close(IndexService.java:389) ~[classes/:?]
	at org.opensearch.indices.IndicesService.removeIndex(IndicesService.java:1044) ~[classes/:?]
	at org.opensearch.indices.cluster.IndicesClusterStateService.deleteIndices(IndicesClusterStateService.java:352) ~[classes/:?]
	at org.opensearch.indices.cluster.IndicesClusterStateService.applyClusterState(IndicesClusterStateService.java:282) ~[classes/:?]
	at org.opensearch.cluster.service.ClusterApplierService.callClusterStateAppliers(ClusterApplierService.java:608) ~[classes/:?]
	at org.opensearch.cluster.service.ClusterApplierService.callClusterStateAppliers(ClusterApplierService.java:595) ~[classes/:?]
	at org.opensearch.cluster.service.ClusterApplierService.applyChanges(ClusterApplierService.java:563) ~[classes/:?]
	at org.opensearch.cluster.service.ClusterApplierService.runTask(ClusterApplierService.java:486) ~[classes/:?]
	at org.opensearch.cluster.service.ClusterApplierService$UpdateTask.run(ClusterApplierService.java:188) ~[classes/:?]
	at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:852) ~[classes/:?]
	at org.opensearch.common.util.concurrent.PrioritizedOpenSearchThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedOpenSearchThreadPoolExecutor.java:283) ~[classes/:?]
	at org.opensearch.common.util.concurrent.PrioritizedOpenSearchThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedOpenSearchThreadPoolExecutor.java:246) ~[classes/:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
	at java.lang.Thread.run(Thread.java:840) ~[?:?]

Ran test for 500 times, it passed successfully.
[ec2-user@ip-172-31-72-21 OpenSearch]$ ./gradlew ':server:internalClusterTest' --tests "org.opensearch.action.admin.indices.create.CreateIndexIT.testCreateAndDeleteIndexConcurrently" -Dtests.seed=EA9B1803756CB3DA -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=en -Dtests.timezone=Etc/UTC -Dtests.timeoutSuite=108000000! -Dtests.iters=500
=======================================
OpenSearch Build Hamster says Hello!
  Gradle Version        : 8.7
  OS Info               : Linux 6.1.84-99.169.amzn2023.x86_64 (amd64)
  JDK Version           : 21 (Amazon Corretto JRE)
  JAVA_HOME             : /usr/lib/jvm/java-21-amazon-corretto.x86_64
  Random Testing Seed   : EA9B1803756CB3DA
  In FIPS 140 mode      : false
=======================================

> Task :server:internalClusterTest
WARNING: Using incubator modules: jdk.incubator.vector
Apr 24, 2024 6:13:28 PM sun.util.locale.provider.LocaleProviderAdapter <clinit>
WARNING: COMPAT locale provider will be removed in a future release

WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.opensearch.bootstrap.BootstrapForTesting (file:/home/ec2-user/OpenSearch/test/framework/build/distributions/framework-3.0.0-SNAPSHOT.jar)
WARNING: Please consider reporting this to the maintainers of org.opensearch.bootstrap.BootstrapForTesting
WARNING: System::setSecurityManager will be removed in a future release
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.gradle.api.internal.tasks.testing.worker.TestWorker (file:/home/ec2-user/.gradle/wrapper/dists/gradle-8.7-all/aan3ydargesu18aqyqjwhr3pc/gradle-8.7/lib/plugins/gradle-testing-base-8.7.jar)
WARNING: Please consider reporting this to the maintainers of org.gradle.api.internal.tasks.testing.worker.TestWorker
WARNING: System::setSecurityManager will be removed in a future release

BUILD SUCCESSFUL in 14m 47s
57 actionable tasks: 1 executed, 56 up-to-date
WARNING: The following functionality has been deprecated and will be removed in the next major release of the Develocity Gradle plugin. For assistance with migration, see https://gradle.com/help/gradle-plugin-develocity-migration.
- The deprecated "gradle.enterprise.testretry.enabled" system property has been replaced by "develocity.testretry.enabled"
- The "com.gradle.enterprise" plugin has been replaced by "com.gradle.develocity"

Ran CreateIndexIT file for 500 times, all tests passed successfully.
[ec2-user@ip-172-31-72-21 OpenSearch]$ ./gradlew ':server:internalClusterTest' --tests "org.opensearch.action.admin.indices.create.CreateIndexIT" -Dtests.seed=EA9B1803756CB3DA -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=en -Dtests.timezone=Etc/UTC -Dtests.timeoutSuite=108000000! -Dtests.iters=500
=======================================
OpenSearch Build Hamster says Hello!
  Gradle Version        : 8.7
  OS Info               : Linux 6.1.84-99.169.amzn2023.x86_64 (amd64)
  JDK Version           : 21 (Amazon Corretto JRE)
  JAVA_HOME             : /usr/lib/jvm/java-21-amazon-corretto.x86_64
  Random Testing Seed   : EA9B1803756CB3DA
  In FIPS 140 mode      : false
=======================================

> Task :server:internalClusterTest
WARNING: Using incubator modules: jdk.incubator.vector
Apr 24, 2024 6:30:08 PM sun.util.locale.provider.LocaleProviderAdapter <clinit>
WARNING: COMPAT locale provider will be removed in a future release

WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.opensearch.bootstrap.BootstrapForTesting (file:/home/ec2-user/OpenSearch/test/framework/build/distributions/framework-3.0.0-SNAPSHOT.jar)
WARNING: Please consider reporting this to the maintainers of org.opensearch.bootstrap.BootstrapForTesting
WARNING: System::setSecurityManager will be removed in a future release
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.gradle.api.internal.tasks.testing.worker.TestWorker (file:/home/ec2-user/.gradle/wrapper/dists/gradle-8.7-all/aan3ydargesu18aqyqjwhr3pc/gradle-8.7/lib/plugins/gradle-testing-base-8.7.jar)
WARNING: Please consider reporting this to the maintainers of org.gradle.api.internal.tasks.testing.worker.TestWorker
WARNING: System::setSecurityManager will be removed in a future release

BUILD SUCCESSFUL in 3h 7m 57s
57 actionable tasks: 1 executed, 56 up-to-date
WARNING: The following functionality has been deprecated and will be removed in the next major release of the Develocity Gradle plugin. For assistance with migration, see https://gradle.com/help/gradle-plugin-develocity-migration.
- The deprecated "gradle.enterprise.testretry.enabled" system property has been replaced by "develocity.testretry.enabled"
- The "com.gradle.enterprise" plugin has been replaced by "com.gradle.develocity"

new_concurrent_3.txt
Adding one of the thread dump where IT test was stuck after 10 tests. Test is getting stuck while doing the indexing, from the code perspective while doing shardBulkAction call, it's getting stuck.

ack @aasom143 . moving the Indexing label. thanks!

Closing in favour of https://github.com/opensearch-project/OpenSearch/issues/14312


Send message to private group

I need to send a message to a private group.
   m = await botClient.SendTextMessageAsync("@groupname", text, ParseMode.Html);
This code works correctly with public group, but I don't know how I can get and set the private group name to use it here.
It seems the format of invitation like this:
https://t.me/+upY3ZCgyLy42ZbMy
So how I can get the group name?

use chat id instead of chat name

use chat id instead of chat name

Probably that is the question. He doesn't know chat id.
At a glance I can advise to analyze input information from the chat (any input requests available for bot) and remember chat id. But most probably it is not what he actually asked...

He can get it. Any way he cant send to chat where he wasn't added. And once he was added - he knows chat id.

@KotM yes exactly, I think I need the chat ID.
@Fedorus could you please give me more details how to find the chat ID?
Which method I have to use?

@overstartup when bot added to the group it receives my_chat_member update and there you can get chat id, if its already added - on each update will be chat id

@Fedorus  I made the channel public and got it, then I used it in private type.  Thanks

Please follow issue template
If you want to chat, feel free to join our group.


Changed lstar unit in example to meters

It looks like the lstar unit in the example is still in inches because an lstar of 40 meters gives a chamber length of 7 meters which is huge. If it is supposed to be 40 meters than you can just close this PR.

Nice catch. Frankly, this repo is out of date and super buggy. This is a good nudge to start working on this again. I'll have another version out in a month or so with more features. Feel free to email me if you are interested in collaborating.