After last HA core update Chihiros integration cannot be loaded

Hallo, after last HA core update (2024.10.4 -> 2024.11.0) Chihiros integration cannot be loaded, this is the log message:
Something happened with HA so it can't use the integration. Tx.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^

AttributeError: type object 'ControlType' has no attribute 'SET_WINDOW_TITLE'
2024-11-07 07:19:44.884 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to import_module with args ('custom_components.chihiros',) in /usr/src/homeassistant/homeassistant/loader.py, line 1071: ComponentProtocol, importlib.import_module(self.pkg_path) inside the event loop; This is causing stability issues. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#import_module
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component
result = await _async_setup_component(hass, domain, config)
File "/usr/src/homeassistant/homeassistant/setup.py", line 334, in _async_setup_component
component = await integration.async_get_component()
File "/usr/src/homeassistant/homeassistant/loader.py", line 1023, in async_get_component
comp = self._get_component()
File "/usr/src/homeassistant/homeassistant/loader.py", line 1071, in _get_component
ComponentProtocol, importlib.import_module(self.pkg_path)

2024-11-07 07:19:44.990 ERROR (MainThread) [homeassistant.loader] Unexpected exception importing component custom_components.chihiros
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 1071, in _get_component
ComponentProtocol, importlib.import_module(self.pkg_path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

After  2024.11.1 update  the integration works fine  again 👏🏻


Update slf4j-log4j12 to 1.7.31

Updates org.slf4j:slf4j-log4j12 from 1.7.30 to 1.7.31.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.slf4j", artifactId = "slf4j-log4j12" } ]

labels: library-update, semver-patch

Superseded by #61.


Fieldsets as tabs

Is there any way to show fieldsets as tabs? Actually I'm using django-suit and looking for alternatives.

Good point. Added into TODO.

Thanks for this theme, it's awesome. FWIW, I second this!

@vade @minholi tab support implemented in #249

I see that the issue is closed, but the Pull request is not integrated in the project and does not appear in the release that came out yesterday, right?
Wouldn't it be better to leave it open until the pull request is accepted?

how stacked inline add to tab?


[BUG] azure-storage.jar and rxjava.jar version 2 support

Hi,
We have integrated our product with Azure Blob Storage and communicate using the Azure Java SDK jars. As a jar dependency, we are using the rxjava.jar (version 1.2.4). This version of rxjava.jar uses unsafe API from Oracle Java 11 SDK and hence not compatible with java 11. The rxjava jar provider has fixed these issues in latest version 2.x.x. This 2.x.x version is complete rewrite of library and azure-storage.jar (version 8.3.0) and azure-keyvault.jar (version 1.2.0) are not compatible with it. Can you please let us know when Microsoft will support the rxjava.jar (version 2.x.x)?
Exception or Stack Trace
Caused by: java.lang.NoClassDefFoundError: rx/functions/Func1
at com.ptc.windchill.objectstorage.azureblob.encryption.csekeyvault.CSEKeyVaultBlobEncryptConfig.getKeyVaultKey(CSEKeyVaultBlobEncryptConfig.java:86)
at com.ptc.windchill.objectstorage.azureblob.encryption.csekeyvault.CSEKeyVaultBlobFileWriter.setEncryptionPolicy(CSEKeyVaultBlobFileWriter.java:54)
at com.ptc.windchill.objectstorage.azureblob.BlobFileWriter.upload(BlobFileWriter.java:615)
at com.ptc.windchill.objectstorage.azureblob.BlobFileWriter.storeStreamUpload(BlobFileWriter.java:533)
at com.ptc.windchill.objectstorage.azureblob.BlobFileWriter.storeStreamMultipart(BlobFileWriter.java:410)
at com.ptc.windchill.objectstorage.azureblob.BlobFileWriter.storeUnKnownLengthStream(BlobFileWriter.java:322)
at com.ptc.windchill.objectstorage.azureblob.BlobFileWriter.storeStream(BlobFileWriter.java:281)
at com.ptc.windchill.objectstorage.azureblob.BlobFileWriter.storeStream(BlobFileWriter.java:228)
at wt.objectstorage.ContentFileWriter.storeStream(ContentFileWriter.java:97)
at wt.objectstorage.ContentFileWriter.storeStream(ContentFileWriter.java:66)
at wt.fv.StoreStreamListener.prepareToUpload(StoreStreamListener.java:207)
at wt.fv.StoreStreamListener.prepareToUpload(StoreStreamListener.java:165)
at wt.fv.StoreStreamListener.prepareToUpload(StoreStreamListener.java:128)
at wt.fv.uploadtocache.DoUploadToCache_Server.storeContentInVaultOnMaster(DoUploadToCache_Server.java:612)
at wt.fv.uploadtocache.DoUploadToCache_Server.storeSingleFile(DoUploadToCache_Server.java:1878)
at wt.fv.uploadtocache.DoUploadToCache_Server.doMultiPartUploadToCache_Server(DoUploadToCache_Server.java:1689)
... 55 more
Caused by: java.lang.ClassNotFoundException: rx.functions.Func1
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 71 more
Test the azure-storage.jar, azure-keyvault.jar and its dependencies with Java 11.
Using jdeps tool, scan the azure-storage.jar and its dependencies.
Any sample code (get Key from Key Vault Service) for azure-storage.jar, azure-keyvault.jar can be tested with java 11.
We expect that the azure-storage.jar, azure-keyvault.jar supports the rxjava.jar version 2.x.x
No screenshots
Setup:

OS: Centos 7
IDE : Eclipse
JDK- Oracle SE JDK 11
azure-storage.jar(8.3.0)
azure-keyvault.jar (1.2.0)
azure-keyvault-core.jar (1.2.0)
azure-keyvault-cryptography.jar (1.2.0)
azure-keyvault-extensions.jar (1.2.0)
azure-keyvault-webkey.jar (1.2.0)
rxjava.jar (1.2.4)

Additional context
We are upgrading the java support to version 11 for our product.

Type in my above bug report. Under setup section, rxjava.jar should be 2.2.14.

@rickle-msft can you please take a look?

@vinayak-kuchekar please note that we have shipped new major releases of the Azure SDK for Java including KeyVault and Storage.  The new versions have names starting with 'com.azure' instead of 'com.microsoft.azure'.  The new SDK versions have new features, better performance, and are more usable and consistent following the Azure SDK Design Guidelines.

There is also a blog post about these new versions here: https://techcommunity.microsoft.com/t5/Azure-SDK/November-2019-unified-Azure-SDK-GA/ba-p/1020875

You can find samples, migration guides, and documentation for the new major versions of the libraries here: https://github.com/azure/azure-sdk-for-java#client-ga-november-2019-releases

A community "Gitter" channel for Azure SDK for Java is also available here: https://gitter.im/Azure/azure-sdk-for-java?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge

Hi, @vinayak-kuchekar. v8.x.x of the Storage sdk has no interaction with rxJava and will not be doing any work to explicitly support it. If you are seeing No Class Def errors, you are likely running into some sort of dependency conflict that has to be resolved by pinning the desired version of the dependency in question in your pom. Please let us know if you have trouble with this.

@vinayak-kuchekar please reactivate if you still need help with this. Thanks


Last layer of the Llava-1.5 visual tower is not training

import numpy as np
import torch
from datasets import Dataset, features
from PIL import Image
from transformers import AutoModelForVision2Seq, AutoProcessor

from trl import DPOConfig, DPOTrainer

model_id = "trl-internal-testing/tiny-random-llava-1.5"
model = AutoModelForVision2Seq.from_pretrained(model_id)
ref_model = AutoModelForVision2Seq.from_pretrained(model_id)
processor = AutoProcessor.from_pretrained(model_id)

dataset = Dataset.from_dict(
    {
        "prompt": [
            "USER: <image>\nDescribe the image in great detail. ",
            "USER: <image>\nIs this bus in the USA? ",
            "USER: <image>\nGive a thorough description of the image. ",
            "USER: <image>\nWho are the people in the image? ",
            "USER: <image>\nWhat is written? ",
        ],
        "chosen": [
            "ASSISTANT: The image features a modern, multi-colored train. ",
            "ASSISTANT: Yes, it can be assumed that this bus is in the USA. ",
            "ASSISTANT: The image features a forest path. ",
            "ASSISTANT: There are two individuals, possibly girls or women. ",
            'ASSISTANT: "ccpb". ',
        ],
        "rejected": [
            "ASSISTANT: The image features a modern, colorful train. ",
            "ASSISTANT: No, it's not in the USA. ",
            "ASSISTANT: The image features a forest path surrounded by trees. ",
            "ASSISTANT: In the image, there are two individuals. ",
            'ASSISTANT: "ccpb". ',
        ],
        "images": [
            [Image.fromarray(np.random.randint(0, 255, (92, 33, 3), dtype=np.uint8))],
            [Image.fromarray(np.random.randint(0, 255, (64, 48, 3), dtype=np.uint8))],
            [Image.fromarray(np.random.randint(0, 255, (80, 152, 3), dtype=np.uint8))],
            [Image.fromarray(np.random.randint(0, 255, (57, 24, 3), dtype=np.uint8))],
            [Image.fromarray(np.random.randint(0, 255, (102, 48, 3), dtype=np.uint8))],
        ],
    }
)
dataset = dataset.cast_column("images", features.Sequence(features.Image()))

training_args = DPOConfig(
    output_dir="tmp_dir",
    per_device_train_batch_size=2,
    max_length=512,
    max_prompt_length=128,
    remove_unused_columns=False,
    report_to="none",
)
trainer = DPOTrainer(model=model, ref_model=ref_model, args=training_args, tokenizer=processor, train_dataset=dataset)

# Save the initial weights, so we can check if they have changed after training
previous_trainable_params = {n: param.clone() for n, param in trainer.model.named_parameters()}

trainer.train()

# Check that the trainable params have changed
for n, param in previous_trainable_params.items():
    new_param = trainer.model.get_parameter(n)
    if param.sum() != 0:  # ignore 0 biases
        if torch.allclose(param, new_param, rtol=1e-12, atol=1e-12):
            print(f"Parameter {n} has not changed after training")

[2024-08-16 14:26:16,425] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
 [WARNING]  async_io requires the dev libaio .so object and headers but these were not found.
 [WARNING]  async_io: please install the libaio-dev package with apt
 [WARNING]  If libaio is already installed (perhaps from source), try setting the CFLAGS and LDFLAGS environment variables to where it can be found.
 [WARNING]  Please specify the CUTLASS repo directory as environment variable $CUTLASS_PATH
 [WARNING]  sparse_attn requires a torch version >= 1.5 and < 2.0 but detected 2.4
 [WARNING]  using untested triton version (3.0.0), only 1.0.0 is known to be compatible
/fsx/qgallouedec/miniconda3/envs/trl/lib/python3.11/site-packages/deepspeed/runtime/zero/linear.py:47: FutureWarning: `torch.cuda.amp.custom_fwd(args...)` is deprecated. Please use `torch.amp.custom_fwd(args..., device_type='cuda')` instead.
  @autocast_custom_fwd
/fsx/qgallouedec/miniconda3/envs/trl/lib/python3.11/site-packages/deepspeed/runtime/zero/linear.py:66: FutureWarning: `torch.cuda.amp.custom_bwd(args...)` is deprecated. Please use `torch.amp.custom_bwd(args..., device_type='cuda')` instead.
  @autocast_custom_bwd
Casting the dataset: 100%|█████████████████████████████████████████████████████████████████| 5/5 [00:00<00:00, 1830.93 examples/s]
Map: 100%|███████████████████████████████████████████████████████████████████████████████████| 5/5 [00:00<00:00, 28.39 examples/s]
  0%|                                                                                | 0/9 [00:00<?, ?it/s]Could not estimate the number of tokens of the input, floating-point operations will not be computed
{'train_runtime': 2.7064, 'train_samples_per_second': 5.542, 'train_steps_per_second': 3.325, 'train_loss': 0.6846402486165365, 'epoch': 3.0}
100%|███████████████████████████████████████████████████████████████████████████████████████████████| 9/9 [00:02<00:00,  3.32it/s]
Parameter vision_tower.vision_model.encoder.layers.3.self_attn.k_proj.weight has not changed after training
Parameter vision_tower.vision_model.encoder.layers.3.self_attn.v_proj.weight has not changed after training
Parameter vision_tower.vision_model.encoder.layers.3.self_attn.q_proj.weight has not changed after training
Parameter vision_tower.vision_model.encoder.layers.3.self_attn.out_proj.weight has not changed after training
Parameter vision_tower.vision_model.encoder.layers.3.layer_norm1.weight has not changed after training
Parameter vision_tower.vision_model.encoder.layers.3.mlp.fc1.weight has not changed after training
Parameter vision_tower.vision_model.encoder.layers.3.mlp.fc2.weight has not changed after training
Parameter vision_tower.vision_model.encoder.layers.3.layer_norm2.weight has not changed after training
Parameter vision_tower.vision_model.post_layernorm.weight has not changed after training

https://github.com/huggingface/trl/blob/0956dc17cccd1d6301f059ded301dbcbfaf99970/tests/test_dpo_trainer.py#L989-L995

I thought Llava blocks gradients for the vision tower? My recollection is that freezing the vision tower is standard today with VLMs

I'm not sure that's what it really is, as it's not the complete vision tower, but just the last layer of just llava.


bump datafusion version

Which issue does this PR close?

N/A
Rationale for this change

Upgrade to latest DataFusion (we're releasing a new version in the next few days)
What changes are included in this PR?

Are there any user-facing changes?

@yahoNanJing @thinkharderdev @avantgardnerio PTAL when you can

Thanks @andygrove. All looks good except there's some checks failed.

This looks like it bumps Ballista to point at 312a7dd3b9642e64555bd0cfa90f4e10145ea103 which is a commit from 2022-08-31 (just after the arrow 21 upgrade)?
I have a fork of Ballista working against a newer Datafusion and arrow-rs 22. If we're going for it, I'd love to see us go all the way.

This looks like it bumps Ballista to point at 312a7dd3b9642e64555bd0cfa90f4e10145ea103 which is a commit from 2022-08-31 (just after the arrow 21 upgrade)?
I have a fork of Ballista working against a newer Datafusion and arrow-rs 22. If we're going for it, I'd love to see us go all the way.

I also have https://github.com/apache/arrow-ballista/pull/200 open, which brings us up to DataFusion as of yesterday (2022-09-10).

This PR uses DataFusion 8b59b207aaadd6f2c19c28d1f1431a0cb8d110ae which already uses Arrow 22


Update scala3-library to 3.0.2

Updates org.scala-lang:scala3-library from 3.0.1 to 3.0.2.
GitHub Release Notes - Version Diff - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala3-library" } ]

labels: library-update, semver-patch

Codecov Report

Merging #245 (3e7d4f2) into master (12bbf88) will increase coverage by 3.70%.
The diff coverage is n/a.

:exclamation: Current head 3e7d4f2 differs from pull request most recent head 30eec7a. Consider uploading reports for the commit 30eec7a to get more accurate results

@@            Coverage Diff             @@
##           master     #245      +/-   ##
==========================================
+ Coverage   66.29%   70.00%   +3.70%
==========================================
  Files          18       17       -1
  Lines         534      500      -34
  Branches       22       21       -1
==========================================
- Hits          354      350       -4
+ Misses        180      150      -30

Impacted Files
Coverage Δ

.../src/main/scala/io/github/vigoo/clipp/Parser.scala
93.80% <0.00%> (-0.11%)
:arrow_down:

.../io/github/vigoo/clipp/usageinfo/debug/debug.scala
0.00% <0.00%> (ø)

...io/github/vigoo/clipp/VersionSpecificParsers.scala

...hub/vigoo/clipp/usageinfo/UsagePrettyPrinter.scala
39.13% <0.00%> (+0.42%)
:arrow_up:

.../scala/io/github/vigoo/clipp/usageinfo/graph.scala
100.00% <0.00%> (+9.52%)
:arrow_up:

.../src/main/scala/io/github/vigoo/clipp/errors.scala
80.00% <0.00%> (+41.53%)
:arrow_up:

...e/src/main/scala/io/github/vigoo/clipp/clipp.scala
100.00% <0.00%> (+75.00%)
:arrow_up:

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 12bbf88...30eec7a. Read the comment docs.


Fix UnixUDPNet

The first step of refine UDP code for QUIC project.

Fix bugs in UnixUDPNet.cc

Start EventIO in UDPNetProcessor::UDPBind()
Fix wrong usage of IpEndpoint in UDPQueue::SendUDPPacket()

Fix UDP Echo Server in test_I_UDPNet.cc to verify above fixes are working
Make test_I_UDPNet.cc a check program using TextBox

Seems reasonable, although I think we should look at making the test program an AUTest. That will require a UDP client which is a bit more work.

[approve ci ICC]
[approve ci autest]

hello,I test udp transfer data through trafficserver,as follow:
udpclient(send file interval) -> trafficserver -> udpreceiver(receive data and save to file)
description:
udpclient send file data to trafficserver,and then trafficserver send those data to another udp receiver.
I found loss much packets when  the interval of sending is small in one computer,such as 10 macroseconds.But i just send file data to udpreceiver,it's ok,no packets loss. So i think trafficserver dosen't recvfrom data or send data as soon as possible or other bugs. Do you have some idea this problem?

I found here the size of udp sendbuf and recvbuf is too small ,only 1472 bytes, this also cause too more packets lost. I change  the size of udp sendbuf and recvbuf to 128K, it's also lost packets,but fewer
#define INK_ETHERNET_MTU_SIZE 1472
TSAction
INKUDPBind(TSCont contp, unsigned int ip, int port)
{
sdk_assert(sdk_sanity_check_continuation(contp) == TS_SUCCESS);
FORCE_PLUGIN_MUTEX(contp);
struct sockaddr_in addr;
ats_ip4_set(&addr, ip, htons(port));
return reinterpret_cast(udpNet.UDPBind((Continuation *)contp, ats_ip_sa_cast(&addr), INK_ETHERNET_MTU_SIZE, INK_ETHERNET_MTU_SIZE));
}

@jingshaoqi Thanks for your report. It looks like a problem of interface of INKUDPBind API.
Actually I didn't know there are tsapis of UDP;p

Pushed new commit.

Fix some signatures of stubs for latest master
Run udp echo server on ET_UDP thread
Use sizeof(payload)

I'm going to open another PR for AUTest.


[IOTDB-2932]Fix concurrent UnPin bug & Improve template implementation

Description
Fix concurrent UnPin bug
The Pin/UnPin status check of cacheEntry should be synchronized, otherwise the change may result in multi threads get wrong cache status and do extra unpin, which may result in negative semaphore value.
Improve template implementation
The old implementation of template check during insert takes low performance and is hard to understand. Thus the implementation is rewritten.

@bigreybear @SilverNarcissus PZTL


Address linter issues

tslint is now highlighting a bunch of code hygiene issues.
we need to address as many as possible, and adjust the rules to reflect our real goals for code style.

Not sure if this is the right place for it; but @benbrown and @johnataylor should we disable the TSLint if the mocha tests get a '1' status code?  I suppose the first question is actually "can we stop the travis build if a unit test fails?"

Disregard previous comment; we should run both regardless so that diligent devs clean up their code before it gets merged, even if the build breaks on a unit test... We should in the future evaluate whether or not tslint should throw errors or just warnings.

Work in progress in the benbrown/linter branch fyi

I've gone through all the files in botbuilder and botbuilder-ai now and updated them to the best of my ability. There are a few warnings still coming out of each project, which I'm still working on.

botbuilder-dialogs is now updated, and I've also merged in the recent changes from master.

The vast majority of linter errors have been corrected, and the linter rules have been updated. This has been merged!


✨[feature Request]: I would like to work on the nav-bar

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description

When we slide down the page then the nav bar hides , Due to this the nav links are not properly visible this can fixed by adding a backdrop filter to make it more visible.

I would also like to add a side nav bar while the website is in mobile view .

Use Case
Better visibility of the nav links at the top , Better UI. Makes it easier for the person to find the desired path.
Benefits
Right now nav link are not properly visible which makes it difficult to use the nav link to move to a different page.
While the website is in mobile view it doesn't show any nav-links , so for that i would like to add a side nav bar at the top left position.
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24EXTD contributor
[X] I have starred the repository

@Vatsal-Verma it is already assigned.


Instrument Plugin - (un)secure config xml

Running instrument plugin causes issues when there is xml in the (un)secure configuration (see screenshot)

This issue is fixed in https://www.nuget.org/packages/spkl/1.0.212-beta

No worries, cheers.


Development

[ ] Implement session expiry, input validation, and retry logic
[ ] Add forced logout on session expiry, improve validation, and update styles
[ ] Issue fix

Mistakenly pushed without rebase


Update to ROS launch tutorial

Just added some additional information the the prerequisites, as it is not clear to new comers that the package needs to be build for python in order to handle launch files. I build the package by cmake and looked all over for the setup.py, only to realize that I should have build the package for python in the first place.

This can also be backported to rolling and foxy.
Thanks for noticing that @knmcguire!

@Mergifyio backport rolling foxy

no problem! and thanks for accepting it.  Quite some process goes into this I see, very interesting!
So I'll probably propose some more changes in the future now that I'm going to the tutorials. This time I just pressed 'Edit on Github' which put me on this branch, but do you want me to rather propose the changes on Master or what is the preferred process here?

@knmcguire this repo doesn't have a main branch, but rather a separate branch for each ROS 2 distro. There is not any preference on where to target your fixes, as there could be some API differences between separate distros, and the backporting done here may not apply on every time. Just target your fixes to the one you are using and testing, and let others know if it should apply to other distros as well.

Got it, thanks!


[style]: adding a footer in the website will look great

What's the style idea?
I think every company should have a footer in this section where they can include their company details in official mail.
Add screenshots

Code of Conduct

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

Hey @Antara-3011
Absolutely! I'd love to work together with you on this! 💪 I completely agree—every company should definitely have a footer in their official emails to include their company details. It adds a professional touch and ensures transparency. Let's make this happen! 📧✨

devFind is an individual project, so there is not company associated with it.


Expose HTTP server to support calling close

In order to support cleanly shutting down the express app after calling run, the result of calling express's listen method must be returned. This adds support for:
var server = s3rver
      .setHostname('localhost')
      .setPort(4568)
      .setDirectory(S3_DIR)
      .setSilent(true)
      .run(function (err, host, port) {

      });

server.close(function(err) {

});

This is a pretty essential feature during testing.

Thank you!


Comment text wrong when comment is written while voting in

The problem
When a player votes in with a comment the comment text is wrong:
"hat sich angemeldet
in:
Komm leider etwas später heute"
Instead it should just be "Komm leider etwas später heute"
What version of Home Assistant Core has the issue?
2024.07.2
What version of Kadermanager Integration has the issue?
Latest
What type of installation are you running?
Home Assistant OS
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response

Should be fixed with release 1.3.1 - but is untested


iOS8.4 runtime error: no suitable image found.

Should this run ok in an iOS8.4 simulator?  Am I missing some setup step?  I'm getting:
dyld: Library not loaded: /System/Library/Frameworks/Contacts.framework/Contacts
  Referenced from: /Users/johnk/Library/Developer/CoreSimulator/Devices/1EE33EE4-FAEA-4E70-9838-F2CAB1854DE8/data/Containers/Bundle/Application/A84BD656-FFFB-48D1-91B3-908B1FE5B82B/My.app/MyApp
  Reason: no suitable image found.  Did find:
    /System/Library/Frameworks/Contacts.framework/Contacts: mach-o, but wrong architecture

It works fine in 9 and 10...
Update:  Getting this on the react-native-contacts-wrapper-example project as well:
dyld: Library not loaded: /System/Library/Frameworks/ContactsUI.framework/ContactsUI
  Referenced from: /Users/johnk/Library/Developer/CoreSimulator/Devices/1EE33EE4-FAEA-4E70-9838-F2CAB1854DE8/data/Containers/Bundle/Application/345BAC00-1E17-404A-A37C-D77FC3FB58E3/RNContactsWrapperExample.app/RNContactsWrapperExample
  Reason: no suitable image found.  Did find:
    /System/Library/Frameworks/ContactsUI.framework/ContactsUI: mach-o, but wrong architecture

under iOS 8.4.  So I'm guessing this approach won't work... :-\
Update#2: Ok, got it to work.  Apparently both the Contacts and the ContactsUI libraries must be added to the project and marked as optional.  This worked for both our project and the Example project cited above
Thanks

Thank you! It works for me

How would I go add the libraries to the project and marked them as optional? I am stuck with this issue.

I do not use this library but @johnckendall's answer works for me for a slightly different error I had relating to UserNotifications (with react native after integrating expo into a bare project, iOS 9 apps were crashing on boot due to the error below).
Reason: no suitable image found.
  Did find: /System/Library/Frameworks/UserNotifications.framework/UserNotifications: mach-o, but wrong architecture

I had to link both UserNotifications and UserNotificationsUI and both should be marked as optional.


Build failure: Executing genrule //java/elemental2/dom:w3c_event_patched failed

This commit seems to have broken the build: https://github.com/google/elemental2/commit/d15d5132a5668b8781d99ef22b5673b3b659e268
It assumes that https://github.com/google/closure-compiler/pull/3542 has already merged into google/closure-compiler, but this does not appear to be the case. As such, building elemental2 currently fails, since this diff does not apply cleanly.

Elemental2 automatically syncs in earlier than JsCompiler so this is expected at the head version when a change  is submitted.

Is there a rough ETA on the cycle completing? Looks like the lag time (of broken elemental2 and all downstreams) is 16+ hours.

I think closure guys are syncing every day or two days.

Just a heads up, this is still broken even though closure has merged that patch.
This is because w3c_event comes from
extern(
    name = "w3c_event",
    path = "browser/w3c_event.js",
)

and extern(...) uses the com_google_javascript_closure_compiler repository, which is not from git (that would be com_google_closure_compiler, defined here to read from github directly), but from rules_closure which specifies an old release.
This mismatch was discussed in https://github.com/google/elemental2/pull/135 - my understanding was that the conclusion from that was that we should stop using the "master" build, but only use the latest release. Likewise as discussed there, the extern() def does not read from the "master" branch, so I think it was premature to merge this. Would you consider reverting it so we can build this project (and downstream projects) again?
Alternatively, replace the extern(...) invocation above with an alias(...), like in #135?

My last comment were wrong for most of the extern files, I'm sorry.
We use extern files packaged in jscompiler binary (to be sure the api are sync between the externs used by the jscompiler and the interfaces defined in elemental2). So we need to wait that a new binary containing the changes in the externs is released. Then we update rules_closure repo to use this new release and that will fix the build.
We need to switch on a monthly release so people does not need to depend on master.

There is a PR open that will resolve this until the next release is shipped: https://github.com/google/elemental2/pull/138
As elemental2's build instructions direct users to use master (as does the tagged release, even though the tagged build appears to use a tagged version of closure-compiler, which may resolve this), it might make sense to fix this issue - any project following the readme instructions cannot build and hasn't been able to do so for just over a week.

To clarify;
Internally we use everything from HEAD version so any update goes directly here; I don't know anyway to delay that.
Externally we need to use the externs from the JsCompiler version used by rules_closure.
So there is no way to make head version work always until we stop looking at two different places.
@jDramaix is that something we could speed that up?

We could think about doing a monthly release (in sync with closure compiler release) so people can use this one instead of depending on master and update the build instructions.
Master will always be instable externally.
Or we could push changes to a branch instead of master and merge to master once this temporary branch is stable.

Do you expect instability after everything is moved under jscompiler and patches are gone?

The only way to remove patches is to write specific visitors. There is no way to fix everything in the extern file directly. EventListener is an example of api that would need post process to fix the generated java code.
Even if we get rid of the patches, we can have instability if they rename/move extern files (they did that recently and will do it again) and with integer entity files.

Note that we don't have instability with integer entity files as the jsinterop generator runs in non-strict mode in opensource and it emits a warning instead of an error.
So I guess if we can rid of the patches, master branch of elemental should stay stable. Closure guys will rename so extern files in the near future but then it should not happen anymore


CSP overriding and/or new UI.

There are two primary issues, one only applicable to themes, and the other applicable to both plugins and themes.

Text Content Type: https://raw.githubusercontent.com doesn't return text/css even for CSS files (which makes sense).
Any redirect within the included file will be fetched from the client, meaning the client must allow requests to that domain. Sadly, this is not the case due to Discord's strict CSP settings: "style-src 'self' 'unsafe-inline' https://cdn.discordapp.com https://*.hcaptcha.com https://hcaptcha.com" (specifically .css).

This would be relatively easy through Electron (reference: https://github.com/Vendicated/Vencord/blob/8cf4d2a2c0ffcca68d8627b4d8f15b5a0f2eb3c0/src/main/index.ts#L88), however as far as I can tell there's no built-in way to do this in gluon.
That leads me to my last idea; making our own embedded browser window library instead of using gluon.

For now, only themes without redirects will work. Things like @import won't work, however, custom fonts should work since https://github.com/therealnv6/catcord/commit/c6315b9ebf393a7a8886c88df97ea657ab5bb5fe, tested with https://raw.githubusercontent.com/DiscordStyles/discord-dyslexia/main/src/base.css

Added a way to use themes that do use import atrules by recursively handling the CSS through node in commit https://github.com/therealnv6/catcord/commit/ed1b80ea345c58b5716e68f38868668bae6108e6.
This is not the most ideal solution, but this is a temporary solution while I'm working on the CSP stuff.
Doing this for JavaScript (plugins, in the future) would be harder because they are relative file paths. Perhaps editing the main path with the relative path would be an option, but I'd rather implement a way to override the CSP.

Experimented with wry. For now sticking with GluonJS due to performance reasons.


fix(exec): temp files are now cleaned up

Fixes #353
The issue had to do with an exception being thrown, causing execSync() to skip the cleanup. This seems to fix the issue for each version of node we support

This also fixes an issue where shell.error() would sometimes indicate success, even if the process exited with non-zero status (like 12, for example).

@ariporad this should be ready for review

LGTM!


Thank you!!!!!

I look forward to your updates every time, it's really great!
It would be really cool if the four pieces of equipment would look like Ghost Rider when worn.


boost_python3 libraries not built correctly

The boost_python3 library uploaded to nuget.org (https://www.nuget.org/packages/boost_python3-vc140/) seems to be compiled against the wrong python version. The libraries

boost_python3-vc140-mt-1_64.lib
boost_python3-vc140-mt-gd-1_64.lib

export the symbol
struct _object * __cdecl boost::python::detail::init_module(char const *,void (__cdecl*)(void))

when they should export
struct _object * __cdecl boost::python::detail::init_module(struct PyModuleDef &,void (__cdecl*)(void))

See boost/python/module_init.hpp:
#  if PY_VERSION_HEX >= 0x03000000
BOOST_PYTHON_DECL PyObject* init_module(PyModuleDef&, void(*)());
#else
BOOST_PYTHON_DECL PyObject* init_module(char const* name, void(*)());
#endif

Make sure you actually compile boost_python3 for python3

https://svn.boost.org/trac/boost/ticket/13023

Binaries for 1.64 were taken from https://sourceforge.net/projects/boost/files/boost-binaries/1.64.0/

Switch to 1.65 should solve the problem.


Update MQTT pubsub to beta

Signed-off-by: shivam<EMAIL_ADDRESS>Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[ ] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[ ] Read the contribution guide
[ ] Commands include options for Linux, MacOS, and Windows within codetabs
[ ] New file and folder names are globally unique
[ ] Page references use shortcodes instead of markdown or URL links
[ ] Images use HTML style and have alternative text
[ ] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description

Issue reference

@shivamkm07 -  Can you add the link that points to the Component PR for merging and passing of the conformance tests? we need the trail to show that conformance these have been added.

@shivamkm07 - Can you add the link that points to the Component PR for merging and passing of the conformance tests? we need the trail to show that conformance these have been added.

@msfussell Description updated with links for conformance and certification PRs.


packaging: drop concourse helpers

they are in gitlab now to be re-usable for other packages as well
Signed-off-by: Maximilian Meister<EMAIL_ADDRESS>

I'll merge this right away if you don't mind to trigger a new build in concourse once travis is green


[AutoDiff] Fix falsely triggered precondition in Array.DifferentiableView.+ and .move

Dear everyone,
This PR adds a fix and tests that exercise falsely triggered preconditions in the Array.DifferentiableView.+ and .move(by:) methods in the standard library.
The fix implements a correct handling of .zero tangent vector, i.e. an empty [] array, in the back-propagation pass of the aforementioned methods. It avoids count mis-match when the de-concatenated gradient passed to +(...) pullback happens to be zero. I've also bundled-in a small rewording of the precondition error messages that now includes the invalid count besides the expected one.
I didn't bother fixing nor testing the forward-propagation pass Array.DifferentiableView._jvpContatenate since the plan is to remove these from the repository anyway. Is this assumption correct?
Resolves SR-14297.
Cheers,
Vojta
@rxwei or whoever happens to be the reviewer. This is my first PR, so I apologize for violating any standards upfront. I did my best to follow the Getting started and First PR guides but some things may have slipped through.
@vguerra I hope you like the improved precondition messages that now contain the invalid lengths! Thanks for the suggestion ;)

I didn't bother fixing nor testing the forward-propagation pass Array.DifferentiableView._jvpContatenate since the plan is to remove these from the repository anyway. Is this assumption correct?

Yep, this is correct.

@rxwei or whoever happens to be the reviewer. This is my first PR, so I apologize for violating any standards upfront. I did my best to follow the Getting started and First PR guides but some things may have slipped through.

Thanks for the contribution. It already looks great!

Thanks for the comments and the review, @rxwei.  I don't have a problem with any of them and the PR is already updated.
Now, a noob question. Can I trigger CI or does it run automatically?

Thanks! CI can only be triggered by contributors with commit access. I'll trigger it for you.

@swift-ci please test and merge


Appstudio update test-component-pac-bxaq

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-bxaq-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
2 minutes
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
22 seconds
deprecated-base-image-check

✅ Succeeded
22 seconds
inspect-image

✅ Succeeded
18 seconds
clair-scan

✅ Succeeded
32 seconds
clamav-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
18 seconds
label-check

✅ Succeeded
5 seconds
show-sbom

✅ Succeeded
8 seconds
show-summary


Remove PressListener.a11yListener

From #888, accessibility listeners can now be added directly with addInputListener, so adding PressListener as an input listener will add both a11y and non-a11y listeners. We had a separate way of adding PressListener's a11y listeners through PressListener.a11yListener, and usages currently look like this
    this.addInputListener( pressListener );
    this.addInputListener( pressListener.a11yListener );

Removing this will clean up PressListener quite a bit, and I think also fix a few things that are currently showing up on Bayes CT.
For instance, I think that this is happening because the click listener is called twice immediately, since it was added as a listener twice.
reactants-products-and-leftovers : accessibility-fuzzBoard : require.js : run
Uncaught Error: Assertion failed
Error: Assertion failed
    at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1544022425098/assert/js/assert.js:22:13)
    at GameModel.play (https://bayes.colorado.edu/continuous-testing/snapshot-1544022425098/reactants-products-and-leftovers/js/game/model/GameModel.js?bust=1544024544386:106:17)
    at Emitter.listener (https://bayes.colorado.edu/continuous-testing/snapshot-1544022425098/reactants-products-and-leftovers/js/game/view/SettingsNode.js?bust=1544024544386:178:15)
    at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1544022425098/axon/js/Emitter.js?bust=1544024544386:194:53)
    at PushButtonModel.fire (https://bayes.colorado.edu/continuous-testing/snapshot-1544022425098/sun/js/buttons/PushButtonModel.js?bust=1544024544386:155:25)

I verified that clicking on a button that uses PressListener with a keyboard is calling PressListener.click twice.

This means that ALL things using PressListener will also get a11y input listeners characteristic of buttons. Is this a problem?

a11yListener removed in the above commits and keyboard interaction with buttons seems to be working. It is a little too early to see if this fixed what was showing up on CT.

@zepumph do you have any opinions about https://github.com/phetsims/scenery/issues/903#issuecomment-444555403? Would it be a problem for things that extend PressListener like DragListener or FireListener?

There is a potential that if the methods are overridden, and they don't call the super type method, then we loose functionality (which is not a unique issue to a11y pressListener). No strong preference from me. To me it doesn't really seem like an improvement (though no worse either). I like that all the a11y stuff is consolidated and can be documented as such. I'm flexible however you would like to proceed.

After chewing on this a bit, I agree. And it seems unecessary/reckless to add click listeners everywhere when we don't need them.
I am going to revert the commits made 4 hours ago, and then rename instance functions focus blur and click on PressListener to handleFocus handleBlur, and handleClick to fix this issue.

Over slack @zepumph indicated concern over the lines required in keeping a11yListener and that maybe it should stay removed.
this.addInputListener( this._pressListener );
this.addInputListener( this._pressListener.a11yListener );

The case I am worried about is if a parent Node with a listener that extends PressListener has a child Node that uses PressListener. Since click bubbles it will be caught on the parent, always.
var parentNode = new Node( { tagName: 'div' } );
parentNode.addInputListener( new DragListener( ... ) };

var buttonChild = new Node( { tagName: 'button' } )
buttonChild.addInputListener( new PressListener() );

node.addChild( buttonChild );

If user presses enter on buttonChild, DragListener.click will be called on node above, but it isn't mean to act like an a11y button.

Possible solutions:

Basically what it used to be:

var buttonChild = new Node( { tagName: 'button' } )
var buttonListener = new PressListener();
buttonChild.addInputListener( buttonListener );
buttonChild.addInputListener( buttonListener.a11yListener );

parentNode.addChild( buttonChild );

Optionally include a11y listeners

var buttonChild = new Node( { tagName: 'button' } )
buttonChild.addInputListener( new PressListener( { includeA11yListener: true } ) );

Stop worrying so much, the extra click listeners won't cause problems.

I can't guarantee 3, but I also can't  think of a case that where it is wrong.

I would be good to talk about this during a11y meeting.

We discussed during meeting. We decided that for now we can add a function to DragListener that prevents the PressListener.click function from firing by adding a
    canClick: function() {
      return false;
    },

and using the implementation of canClick in canPress.
PressListener.prototype.canClick.call( this )

This seems somewhat of a workaround, but we are not sure if this is going to be an issue at all so this change feels very safe for now. I am going to go ahead and close this issue.


Admin page not loaded

Hi, please help, I setup everything good, but when I try to run admin page, it unable to load. Errors found in the browser developer console as below.

apparently its not an error, its just waiting the android app tracking feature activated.

It is an error. This needs to be re-opened.
The android app somehow becomes unusable because one cannot run the app without providing a transport id, which is only viewable in the admin page.
The instructions are also vague to begin with.
It does not specifically say where to create the admin folder in. inside the transport-tracker-map folder (i guess this is the only viable location)?
and if so, it still gives out that error message.
I have successfully deployed the backend and maps project in firebase, but there are no instructions there for the admin page. on how to set it up. just instructions to add api keys. but it does not work.


Should tensordot broadcast the contracted dimensions?

Should tensordot broadcast the contracted dimensions. For example, say we contract the first dimensions here
tensordot(ones((3, 3)), ones((1, 3)), axes=((0,), (0,)))

The dimension 3 and 1 do not match, but if we broadcast the arrays together first they both become shape (3, 3), after which they do match.
The spec is a little unclear about this https://data-apis.org/array-api/latest/API_specification/linear_algebra_functions.html#tensordot-x1-x2-axes-2. It says x2 must be compatible with x1 by broadcasting, which seems to imply unconditional broadcasting. But it also says "Each axis (dimension) x1_axes[i] for x1 must have the same size as the respective axis (dimension) x2_axes[i] for x2."
NumPy disallows broadcasting in contracted dimensions (it does broadcast non-contracted dimensions):
>>> np.tensordot(np.ones((3, 3)), np.ones((1, 3)), axes=((0,), (0,)))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<__array_function__ internals>", line 181, in tensordot
  File "./numpy/core/numeric.py", line 1110, in tensordot
    raise ValueError("shape-mismatch for sum")
ValueError: shape-mismatch for sum
>>> np.tensordot(np.ones((3, 3)), np.ones((1, 3)), axes=((1,), (1,)))
array([[3.],
       [3.],
       [3.]])

Pytorch broadcasts all dimensions, including contracted ones (note that pytorch still calls its axes argument dims)
>>> torch.tensordot(torch.ones((3, 3)), torch.ones((1, 3)), dims=((0,), (0,)))
tensor([[3., 3., 3.],
        [3., 3., 3.],
        [3., 3., 3.]])
>>> torch.tensordot(torch.ones((3, 3)), torch.ones((1, 3)), dims=((1,), (1,)))
tensor([[3.],
        [3.],
        [3.]])

Note that in either case, the resulting array shape is based on the non-broadcasted input shapes, so it's not as simple as wrapping the call with broadcast_arrays.
>>> np.tensordot(np.ones((3, 3)), np.ones((2, 3, 3)), axes=((-1,), (2,))).shape
(3, 2, 3)
>>> np.tensordot(np.ones((2, 3, 3)), np.ones((2, 3, 3)), axes=((-1,), (2,))).shape
(2, 3, 2, 3)

In today's call, we decided to align with NumPy's behavior, as advocated for by @leofang, @oleksandr-pavlyk, and @rgommers. Given PyTorch's relatively recent addition of tensordot and NumPy's alignment with matmul (which also does not broadcast the innermost two dimensions), seems reasonable to adopt NumPy's behavior in this instance.
@IvanYashchuk did mention elsewhere that PyTorch's behavior can match einsum behavior as follows. If we express the tensordot operation with dims=((1,), (1,)) using einsum ("ab,dc->ad" ), then NumPy would compute the same as torch.tensordot.
import torch
import numpy as np

 a1 = np.random.normal(size=(3, 3))
 a2 = np.random.normal(size=(3, 1))

np.einsum("ab,dc->ad", a1, a2)
# array([[ 1.44946877, -1.0152814 , -1.39638556],
#        [ 1.48299164, -1.03876252, -1.42868074],
#        [-0.37928214,  0.26566844,  0.36539187]])

torch.tensordot(*map(torch.from_numpy, (a1, a2)), dims=((1,), (1,)))
# tensor([[ 1.4495, -1.0153, -1.3964],
#         [ 1.4830, -1.0388, -1.4287],
#         [-0.3793,  0.2657,  0.3654]], dtype=torch.float64)

# A slower but equivalent way of computing the same as with np.einsum "ik,jn->ij"
# or torch.tensordot with dims=((1,), (1,))
result = np.zeros((3, 3))
for i in range(result.shape[0]):
  for j in range(result.shape[1]):
    for k in range(a1.shape[1]): # reducing dim/axis #1
      for n in range(a2.shape[1]): # reducing dim/axis #1
        result[i, j] += a1[i, k] * a2[j, n]
# array([[ 1.44946877, -1.0152814 , -1.39638556],
#        [ 1.48299164, -1.03876252, -1.42868074],
#        [-0.37928214,  0.26566844,  0.36539187]])

Given PyTorch's relatively recent addition of tensordot and NumPy's alignment with matmul (which also does not broadcast the innermost two dimensions), seems reasonable to adopt NumPy's behavior in this instance.

A summary of additional considerations for why the NumPy behavior is preferred:

In the case of ambiguity, it's better to raise an exception than to pick a behavior
In the future it's possible to add more behavior if desired; taking it away is not


Decide on version control conventions

We need to define a few things regarding how we use version control to ensure contributing is easy and maintains a consistent repo.
Firstly, what branching model are we going for? Currently, we seem to have adopted some version of oneflow / github flow, whereby there is one master branch, and features are developed on short lived feature/hotifx branches with descriptive names. This model appears to work well for us, so I propose that we continue to use it, but that we state as such in the documentation, particularly the documentation new contributors are likely to see. This is especially needed as we now appear to have a bot which automatically deletes merged branches, which is great for this style of development but is completely incompatible with, say, git flow. Therefore we should establish consensus on branching model sooner rather than later.
The second topic is somewhat more controversial: how do we wish to handle merges? Personally I am quite a firm believer in using merge commits with --no-ff. The reason for this is it allows for readable history and is very user-friendly; when I look through the git history I can clearly see the branches that commits live on, and I can identify which feature those commits belong to. This does result in merge commits, and some people argue that using rebase merges makes for "nicer history" because it has less merge commits. I disagree; history with less commits is only nicer if it makes for nicer reading. A fast-forward merge obfuscates the fact that there has been a merge and creates confusion for those reading the history - some branches have merge commits, some don't, and it all turns into hot, waxy, pungent garbage. Either way we should reach consensus on how we want to this and communicate this to new contributors.
Lastly, I'd like to discuss "commit quality" on branches. Generally, one should commit little and often (within reason) and then ensure their branched commits are of a reasonable standard (descriptive names, reasonable quantity of changes in each commit, all changes are tightly coupled) before they are merging. My perspective is that rewriting history on branches is acceptable to fix up commits, but that history should be immutable once merged to master, otherwise many nasty things can occur. In general, I don't think we should enforce commit quality beyond very minimal standards (no "fix", "fix?", "FIX" commit crap please), but we should still ensure this is known to new contributors, and potentially provide them with resources to learn git best practices.
Generally I think all of us understand how to and are making a good effort to use version control well, but the only way we can prevent the git history and the state of the repo from turning into a big bag of gore is by ensuring that we are all following the same workflow when we are integrating our contributions (obviously what you do in the privacy of your own branch does not concern me until it gets merged).
I look forward to seeing people's perspectives on this.

Firstly, what branching model are we going for? Currently, we seem to have adopted some version of oneflow / github flow, whereby there is one master branch, and features are developed on short lived feature/hotifx branches with descriptive names. This model appears to work well for us, so I propose that we continue to use it, but that we state as such in the documentation, particularly the documentation new contributors are likely to see. This is especially needed as we now appear to have a bot which automatically deletes merged branches, which is great for this style of development but is completely incompatible with, say, git flow. Therefore we should establish consensus on branching model sooner rather than later.

Agreed.

The second topic is somewhat more controversial: how do we wish to handle merges? Personally I am quite a firm believer in using merge commits with --no-ff. The reason for this is it allows for readable history and is very user-friendly; when I look through the git history I can clearly see the branches that commits live on, and I can identify which feature those commits belong to. This does result in merge commits, and some people argue that using rebase merges makes for "nicer history" because it has less merge commits. I disagree; history with less commits is only nicer if it makes for nicer reading. A fast-forward merge obfuscates the fact that there has been a merge and creates confusion for those reading the history - some branches have merge commits, some don't, and it all turns into hot, waxy, pungent garbage. Either way we should reach consensus on how we want to this and communicate this to new contributors.

I agree with this statement but remain open to other arguments and do not have strong feelings either way.

Lastly, I'd like to discuss "commit quality" on branches. Generally, one should commit little and often (within reason) and then ensure their branched commits are of a reasonable standard (descriptive names, reasonable quantity of changes in each commit, all changes are tightly coupled) before they are merging. My perspective is that rewriting history on branches is acceptable to fix up commits, but that history should be immutable once merged to master, otherwise many nasty things can occur. In general, I don't think we should enforce commit quality beyond very minimal standards (no "fix", "fix?", "FIX" commit crap please), but we should still ensure this is known to new contributors, and potentially provide them with resources to learn git best practices.

Agreed. Force push is blocked on master.

Generally I think all of us understand how to and are making a good effort to use version control well, but the only way we can prevent the git history and the state of the repo from turning into a big bag of gore is by ensuring that we are all following the same workflow when we are integrating our contributions (obviously what you do in the privacy of your own branch does not concern me until it gets merged).

I suggest finding more bots to help with this.

I'm going to block rebase merges in order to implement this.
Feel free to re-open this issue for further discussion as always.

Meant to add this earlier but I also agree wholeheartedly with the proposal.


Dev/update documentation website

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

You may want to also update the description of the schemas inside the various resources & data sources


Fix code scanning alert - Missing CSRF middleware

Tracking issue for:

[x] https://github.com/ikipm/task-manager/security/code-scanning/1

Solved! PR to dev created #28


Discussion about the GRIN optimizer

Hi,
Would you like to have a video meeting and discuss the details of the GRIN optimizer?
Cheers,
Csaba Hruska

Would this be a discussion about using your implementation of GRIN, the roadmap for the GRIN project, or something else?
I've managed to get past the SimpleDeadParameterElimination not working properly by implementing it (I think) correctly in Idris, but now I've got another problem so help would be appreciated.

The topic can be anything that is relevant, i.e. using the current GRIN implementation and also project future plans.
My schedule is quite flexible. What time works for you?

I'll email you, is the email in your github bio good?

Ok.

Huge thanks to Csaba, the discussion was very helpful.


PARQUET-933: Account for API changes in ARROW-728

Requires https://github.com/apache/arrow/pull/457

build passed here: https://travis-ci.org/wesm/parquet-cpp/builds/216936107. merging


Multi/Singel AudioPicker SQLITE_ERROR

D/EGL_emulation: eglMakeCurrent: 0xc4905ee0: ver 2 0 (tinfo 0xc3e17890)
I/chatty: uid=10086(com.anouar.hp.anohideappsano) RenderThread identical 2 lines
D/EGL_emulation: eglMakeCurrent: 0xc4905ee0: ver 2 0 (tinfo 0xc3e17890)
D/EGL_emulation: eglMakeCurrent: 0xc4905ee0: ver 2 0 (tinfo 0xc3e17890)
I/chatty: uid=10086(com.anouar.hp.anohideappsano) RenderThread identical 8 lines
D/EGL_emulation: eglMakeCurrent: 0xc4905ee0: ver 2 0 (tinfo 0xc3e17890)
D/EGL_emulation: eglMakeCurrent: 0xc4905ee0: ver 2 0 (tinfo 0xc3e17890)
I/chatty: uid=10086(com.anouar.hp.anohideappsano) RenderThread identical 1 line
D/EGL_emulation: eglMakeCurrent: 0xc4905ee0: ver 2 0 (tinfo 0xc3e17890)
W/.anohideappsan: Accessing hidden method Landroid/view/View;->getViewRootImpl()Landroid/view/ViewRootImpl; (light greylist, reflection)
Accessing hidden field Landroid/view/View$AttachInfo;->mVisibleInsets:Landroid/graphics/Rect; (light greylist, reflection)
W/.anohideappsan: Accessing hidden field Landroid/view/ViewRootImpl;->mAttachInfo:Landroid/view/View$AttachInfo; (light greylist, reflection)
D/EGL_emulation: eglMakeCurrent: 0xc4905ee0: ver 2 0 (tinfo 0xc3e17890)
W/.anohideappsan: Accessing hidden field Landroid/view/View;->mAccessibilityDelegate:Landroid/view/View$AccessibilityDelegate; (light greylist, reflection)
W/.anohideappsan: Accessing hidden field Landroid/os/Trace;->TRACE_TAG_APP:J (light greylist, reflection)
W/.anohideappsan: Accessing hidden method Landroid/os/Trace;->isTagEnabled(J)Z (light greylist, reflection)
Accessing hidden method Landroid/os/Trace;->asyncTraceBegin(JLjava/lang/String;I)V (light greylist, reflection)
Accessing hidden method Landroid/os/Trace;->asyncTraceEnd(JLjava/lang/String;I)V (light greylist, reflection)
W/.anohideappsan: Accessing hidden method Landroid/os/Trace;->traceCounter(JLjava/lang/String;I)V (light greylist, reflection)
D/EGL_emulation: eglMakeCurrent: 0xc4905ee0: ver 2 0 (tinfo 0xc3e17890)
E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.anouar.hp.anohideappsano, PID: 21232
android.database.sqlite.SQLiteException: no such column: width (code 1 SQLITE_ERROR): , while compiling: SELECT _id, _display_name, date_added, date_modified, _size, width, height, album, is_notification, is_alarm, is_ringtone, year, track, composer, artist FROM audio ORDER BY date_added DESC
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:179)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
at android.content.ContentProviderProxy.query(ContentProviderNative.java:418)
at android.content.ContentResolver.query(ContentResolver.java:802)
at android.content.ContentResolver.query(ContentResolver.java:752)
at android.content.ContentResolver.query(ContentResolver.java:710)
at com.crazylegend.audiopicker.audios.AudiosVM$queryAudios$2.invokeSuspend(AudiosVM.kt:94)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:56)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:738)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)
I/chatty: uid=10086(com.anouar.hp.anohideappsano) RenderThread identical 1 line
D/EGL_emulation: eglMakeCurrent: 0xc4905ee0: ver 2 0 (tinfo 0xc3e17890)
I/Process: Sending signal. PID: 21232 SIG: 9

the image picker and video picker works fine on emulators and real devices but audio picker crashes any help?

sorry can you explain more cuz i replace the same code from ImagePicker to
AudioPicker and the app cant get audios (crash at showpicker fun)
On Mon, Dec 21, 2020 at 7:14 PM FunkyMuse<EMAIL_ADDRESS>wrote:

Closed #2 https://github.com/FunkyMuse/MediaPicker/issues/2 via 41bc6ee
https://github.com/FunkyMuse/MediaPicker/commit/41bc6eecfc3419bea21cb14f9188d66038947aac
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FunkyMuse/MediaPicker/issues/2#event-4137108763, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AISYFAVWNNLLQT2WJK436RDSV6F7TANCNFSM4VEPWWKQ
.

sorry can you explain more cuz i replace the same code from ImagePicker to AudioPicker and the app cant get audios (crash at showpicker fun)
…
On Mon, Dec 21, 2020 at 7:14 PM FunkyMuse @.***> wrote: Closed #2 <#2> via 41bc6ee <41bc6ee> . — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AISYFAVWNNLLQT2WJK436RDSV6F7TANCNFSM4VEPWWKQ .

use the new version of the library

1.0.0 ?

now it's working fine thank you!


Fix account-roles table width

Changed description of permissions in table to decrease length. This is simpler and potentially less messy than addressing this via css. Kept "Managing" descriptors for members and teams to avoid confusion with identifying table column/rows at first glance.
Doc QA: Checked html rendering, no issues.
No Jira task to connect to.
Signed-off-by: Katrina Prosise<EMAIL_ADDRESS>Readiness

[x] Merge (pending reviews)
[ ] Merge after date or event
[ ] Draft

Overview
fixed table fit issues
Checklist
Optional. Add a 'x' to steps taken.
You can fill this out after opening the PR. "Did I..."

[ ] Run spelling and grammar check, preferably with linter.
[x] Avoid changing any header associated with a link/reference.
[ ] Step through instructions (or ask someone to do so).
[ ] Review for wordiness
[ ] Match tone and style of page/section.
[ ] Run make linkcheck.
[x] View HTML in a browser to check rendering.
[ ] Use semantic newlines.
[x] follow best practices for commits.

[x] Descriptive title written in the imperative.
[x] Include brief overview of QA steps taken.
[x] Mention any related issues numbers.
[x] End message with sign off/DCO line (-s, --signoff).
[x] Sign commit with your gpg key (-S, --gpg-sign).
[x] Squash commits if needed.

[x] Request PR review by a technical writer and at least one peer.

Comments
Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.

Docs for 2988969e4dc732d7c44cb2c1c6e58ed4833d2e3a are browsable at: https://ci.foundries.io/projects/fio-docs/builds/1882/docs/artifacts/html/index.html


Implement manifest groups

Summary or solution description
Added a NeoMetadata method to add groups in the metadata.
How to Reproduce
https://github.com/CityOfZion/neo3-boa/blob/5d2116fb02eccf3c1b34ac6d2ee94c9eca67be49/boa3_test/test_sc/metadata_test/MetadataInfoGroups.py#L1-L16
Tests
https://github.com/CityOfZion/neo3-boa/blob/5d2116fb02eccf3c1b34ac6d2ee94c9eca67be49/boa3_test/tests/compiler_tests/test_metadata.py#L313-L355
Platform:

OS: Windows 10 x64
Python version: Python 3.7

(Optional) Additional context
The Csharp version doesn't seem to have a way to add groups in the metadata using the smart contract, it's only done manually.

Task linked: CU-2kwg7uv Implement manifest groups


[bug] Update choice list vertical positions

With NBGL updates, the current position for choice lists are no longer correct, and should be updated.
#206 highlight this issue on the first choice for Stax. But every choice is to be updated, on Stax and Flex.

Fixed in #208


Vnet peering between two vnets in different resource groups

Describe the bug
I am trying to creating a peering between two different vnets in different resource groups but it doesn't seem to work. I tried the command below:
az network vnet peering create -g vnet1rg --name vnet1vnet2peer --vnet-name vnet1 --remote-vnet vnet2 --allow-vnet-access
I get the following error message
Resource /subscriptions//resourceGroups/vnet1rg/providers/Microsoft.Network/virtualNetworks/vnet2 referenced by resource /subscriptions//resourceGroups/vnet1rg/providers/Microsoft.Network/virtualNetworks/vnet1/virtualNetworkPeerings/vnet1vnet2peer was not found. Please make sure that the referenced resource exists.
This seems to indicate that it is trying to vnet2 in the vnet1rg. So I change the resource group to vnet2rg:
az network vnet peering create -g vnet2rg --name vnet1vnet2peer --vnet-name vnet1 --remote-vnet vnet2 --allow-vnet-access
Then I get the following:
The Resource 'Microsoft.Network/virtualNetworks/vnet1' under resource group 'vnet2rg' was not found.
I see no provision for specifying two resource groups. Any help would be much appreciated.
To Reproduce
Try creating a peering between two vnets in different resource groups
az network vnet peering create -g vnet1rg --name vnet1vnet2peer --vnet-name vnet1 --remote-vnet vnet2 --allow-vnet-access
Expected behavior
Expect a peering to be created between vnet1 and vnet2
Environment summary
Azure cloud shell

From the help documentation, --remove-vnet accepts a name or resource ID.  You need to supply the resource ID from cross-subscriptions or cross-RG scenarios.

typo in last statement, I think you mean remote-vnet

Yep, you're right :)

I have the same issue  Spoke01-vnet  &  Hub01-vnet  are in different resorce groups so what would the syntax be for Hub01-vnet
az network vnet peering create -g Spoke01-vnet-rg -n Spoke01-vnetToHub01-vnet --vnet-name Spoke01-vnet --remote-vnet Hub01-vnet --allow-vnet-access --subscription xxxxxxxx-xxxxxxxxx-xxxxxxxxxxxxxxxx

I have the same issue Spoke01-vnet & Hub01-vnet are in different resorce groups so what would the syntax be for Hub01-vnet
az network vnet peering create -g Spoke01-vnet-rg -n Spoke01-vnetToHub01-vnet --vnet-name Spoke01-vnet --remote-vnet Hub01-vnet --allow-vnet-access --subscription xxxxxxxx-xxxxxxxxx-xxxxxxxxxxxxxxxx

if both Vnet in same resource group then the above command will work if the both Vnet is in different resource group then you have to use --remote-vnet-id of the Hub01-vnet. you can get this from vnet properties

Use --remote-vnet as --remote-vnet-id is deprecated.
--remote-vnet accepts now both the name of the vnet (if in the same resource group) or the resource id.


Expose token generation

It would be really great if I would be able to generate jwt tokens for my users when using horizon as a package to my server.

You can run hz make-token to manually create a token for a user. We just added this feature, so it's still undocumented and a bit immature. The generated tokens are also only valid for one day right now.

I have horizon as a package to my server and i need to write some custom
auth since there is none right now, so i wont be able to run hz commands, i
need to be able to generate a token if the user is allowed to get one.
tisdag 17 maj 2016 skrev Daniel Mewes<EMAIL_ADDRESS>
You can run hz make-token to manually create a token for a user. We just
added this feature, so it's still undocumented and a bit immature. The
generated tokens are also only valid for one day right now.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/rethinkdb/horizon/issues/398#issuecomment-219820819

Ok, so we should expose token generation in the horizon library explicitly. This seems simple, any comments @Tryneus ?

In #419 this would be:
horizon._auth.generate(<provider>, <identifier>)

Where provider is a string representing the provider name (ex. twitter) and identifier is any value (string, array, object, etc) that uniquely identifies the user for that provider (ex. twitter username).
You could also use the lower-level JWT APIs; however, doing so won't automatically create users in the internal horizon_internal.users and horizon_internal.auth_users tables for you.
horizon._auth._jwt.sign(<payload>) // -> string
horizon._auth._jwt.verify(<token>) // -> Promise<object>

@deontologician @Tryneus in this case, we could just expose these methods in a less scary way, but I think the real solution is a proper API for attaching auth providers to the server. Either way, we should probably start discussing the overall vision for the public server API before things just get tacked on (#345).

I think this is going to be part of the server refactor for plugins/middleware.


update npm packages

Fixes: #567
Depends on #564 being integrated to make sure trusswork's footer has been removed first.

Build failed because #564 not merged in.


[BUG] org.opensearch.cluster.allocation.AwarenessAllocationIT.testThreeZoneOneReplicaWithForceZoneValueAndLoadAwareness flaky

Describe the bug
New flaky test after https://github.com/opensearch-project/OpenSearch/pull/3563 got merged:
REPRODUCE WITH: ./gradlew ':server:internalClusterTest' --tests "org.opensearch.cluster.allocation.AwarenessAllocationIT.testThreeZoneOneReplicaWithForceZoneValueAndLoadAwareness" -Dtests.seed=CD3B9289D31206B8 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=nl -Dtests.timezone=Asia/Katmandu -Druntime.java=17

org.opensearch.cluster.allocation.AwarenessAllocationIT > testThreeZoneOneReplicaWithForceZoneValueAndLoadAwareness FAILED
    java.lang.AssertionError: unexpected
        at org.opensearch.test.InternalTestCluster.removeExclusions(InternalTestCluster.java:1912)
        at org.opensearch.test.InternalTestCluster.stopNodesAndClients(InternalTestCluster.java:1777)
        at org.opensearch.test.InternalTestCluster.stopNodesAndClient(InternalTestCluster.java:1764)
        at org.opensearch.test.InternalTestCluster.stopRandomNode(InternalTestCluster.java:1672)
        at org.opensearch.cluster.allocation.AwarenessAllocationIT.testThreeZoneOneReplicaWithForceZoneValueAndLoadAwareness(AwarenessAllocationIT.java:425)

        Caused by:
        java.util.concurrent.ExecutionException: MasterNotDiscoveredException[null]
            at org.opensearch.common.util.concurrent.BaseFuture$Sync.getValue(BaseFuture.java:286)
            at org.opensearch.common.util.concurrent.BaseFuture$Sync.get(BaseFuture.java:273)
            at org.opensearch.common.util.concurrent.BaseFuture.get(BaseFuture.java:104)
            at org.opensearch.test.InternalTestCluster.removeExclusions(InternalTestCluster.java:1910)
            ... 4 more

            Caused by:
            MasterNotDiscoveredException[null]
                at app//org.opensearch.action.support.clustermanager.TransportClusterManagerNodeAction$AsyncSingleAction$2.onTimeout(TransportClusterManagerNodeAction.java:282)
                at app//org.opensearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:394)
                at app//org.opensearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:294)
                at app//org.opensearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:697)
                at app//org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:739)
                at java.base@17.0.3/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
                at java.base@17.0.3/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
                at java.base@17.0.3/java.lang.Thread.run(Thread.java:833)

    MasterNotDiscoveredException[null]
        at app//org.opensearch.action.support.clustermanager.TransportClusterManagerNodeAction$AsyncSingleAction$2.onTimeout(TransportClusterManagerNodeAction.java:282)
        at app//org.opensearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:394)
        at app//org.opensearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:294)
        at app//org.opensearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:697)
        at app//org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:739)
        at java.base@17.0.3/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base@17.0.3/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base@17.0.3/java.lang.Thread.run(Thread.java:833)

To Reproduce
Steps to reproduce the behavior:
/gradlew ':server:internalClusterTest' --tests "org.opensearch.cluster.allocation.AwarenessAllocationIT.testThreeZoneOneReplicaWithForceZoneValueAndLoadAwareness" -Dtests.seed=CD3B9289D31206B8 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=nl -Dtests.timezone=Asia/Katmandu -Druntime.java=17

Expected behavior
On CI, the test is  flaky, see please https://ci.opensearch.org/logs/ci/workflow/OpenSearch_CI/PR_Checks/Gradle_Check/gradle_check_6061.log for example.,
Plugins
Standard.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):

CI

Additional context
Add any other context about the problem here.

Seed for repro steps
./gradlew ':server:internalClusterTest' --tests "org.opensearch.cluster.allocation.AwarenessAllocationIT.testThreeZoneOneReplicaWithForceZoneValueAndLoadAwareness" -Dtests.seed=6191C1DB4D571AC -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=lv -Dtests.timezone=Asia/Anadyr -Druntime.java=17

@imRishN Can you have a look at this test? Do we need 15 nodes for this test or could we scale it back to something like 12? three nodes per AZ?  This is pretty demanding for an integration test and I'm wondering if that's what's causing these intermediate timeout failures?

https://github.com/opensearch-project/OpenSearch/pull/5143

https://github.com/opensearch-project/OpenSearch/pull/5283

I'll take a look to this test and try to fix it

@imRishN lets take a look and get back

Another failure here: https://github.com/opensearch-project/OpenSearch/pull/6333#issuecomment-1442520331

Another failure: https://github.com/opensearch-project/OpenSearch/pull/7170#issuecomment-1509437495

Adding one more: https://github.com/opensearch-project/OpenSearch/pull/7203#issuecomment-1512357074

Another failure : https://github.com/opensearch-project/OpenSearch/pull/8758#issuecomment-1665393556

Another failure here - https://github.com/opensearch-project/OpenSearch/pull/10777#issuecomment-1774550373

Impacted PR #11711, see test report.

Investigated this issue. OpenSearch in a way follows greedy approach while allocating shards and doesn't compute the optimal allocation for all the shards that needs to be allocated. This approach based on certain filters and rules tries to control nodes where shards are assigned.
The unassigned shards causing test failure is due to the same above reason where a node where the shard was supposed to be assigned created a conflict with the awareness allocation decider. Hence, it is stuck in a state, waiting for space to allocate the unassigned shard because it cannot assign it to the only node with space. This also seemed more likely to happen in this particular test case because it is creating a 15 nodes cluster and over 120 shards which increases the probability of landing up in such a case. A smaller cluster with lesser shards would be less likely to land up in such a case.
This also seem to be a known issue after scrolling open issues in ElasticSearch/OpenSearch
Also added same in #7401

Closing the issue, test has been muted and will be fixed and enabled back after the fix in allocator

This issue isn't fixed - the test is disabled.  If we were to delete the test I'd be happy to close this issue; however, I suspect that we want to fix the underlying issue.  If there is another issue tracking the scroll issue please link it here.

@peternied, the merged PR which is muting the test links it to actual underlying issue. This is the merged PR muting the test - https://github.com/opensearch-project/OpenSearch/pull/11767. And the PR links the test to actual issue - https://github.com/opensearch-project/OpenSearch/issues/5908.
Feel free to close the issue if this suffices, else we can keep this opened


SWARM-1381: add test for using the RESTEasy Client

Motivation
Some dependency handling changes that went into Swarm 2017.6.0
broke the RESTEasy Client. A test that reproduces this is needed.
Modifications
Added testsuite-jaxrs-client which uses the JAX-RS Client,
provided by RESTEasy, to access a simple JAX-RS resource.
Result
More test coverage, no change to product.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you created a JIRA and used it in the commit message?
[x] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[ ] Have you built the project locally prior to submission with mvn clean install?

Don't merge yet -- this just reproduces an issue. Should be merged after fix.

retest this please

With #534 merged this should pass now

Fails because the snapshot deployment did fail I assume: https://ci.wildfly-swarm.io/job/wildfly-swarm-deploy/249/

Verify onnce https://github.com/wildfly-swarm/wildfly-swarm/pull/537 is merged

retest this please

i've cancelled these jobs for now as I'm not entirely sure how it works in terms of the changes not being built in CI yet

retest this please

Retest this please

After looking some further it seems the test doesn't fail due to CI quirks. I need to investigate this.

Superseded by #538


3D Tiles Inspector: report per-tile number of commnads/features/points/etc

@austinEng after skipping LODs or when you need a break can you add label visualization that displays per tile:

Number of commands (including derived commands for translucent styling if possible)
Number of features (hide if zero)
Number of points (hide if zero)
Number of triangles (hide if zero)

Probably use one LabelCollection for all debugging labels and create new lines in the strings, but do whatever you think.
Let's start with these, phase two could include:

Size of tile in MB
Number of external references
Size of textures
Number of instances
etc

This is a lot of data so we would probably add pickable point primitives for each tile (could even color code them based on heuristics on if the tile is "optimized" or not) that bring up the tile's details.
Similar to #5017

Fixed in #5188


gradle flywayMigrate -i gives Java heap space error

What version of Flyway are you using?
3.1
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin, SBT plugin, ANT tasks)
gradle
What database are you using (type & version)?
5.7.15 Homebrew
What operating system are you using?
Mac OS X El Captain/Centos
What did you do?
(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
gradle flywayMigrate -i
What did you expect to see?
BUILD SUCCESSFUL
What did you see instead?
* Exception is: org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':flywayMigrate'.         at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:84)         at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:55)         at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:61)         at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)         at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:88)         at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:45)         at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:51)         at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)         at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)         at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)         at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:233)         at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:215)         at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:74)         at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:55)         at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)         at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40) Caused by: java.lang.OutOfMemoryError: Java heap space         at org.flywaydb.core.internal.util.FileCopyUtils.copy(FileCopyUtils.java:117)         at org.flywaydb.core.internal.util.FileCopyUtils.copyToByteArray(FileCopyUtils.java:68)         at org.flywaydb.core.internal.util.scanner.classpath.ClassPathResource.loadAsBytes(ClassPathResource.java:100)         at org.flywaydb.core.internal.resolver.sql.SqlMigrationResolver.extractMigrationInfo(SqlMigrationResolver.java:140)         at org.flywaydb.core.internal.resolver.sql.SqlMigrationResolver.resolveMigrations(SqlMigrationResolver.java:112)         at org.flywaydb.core.internal.resolver.sql.SqlMigrationResolver.resolveMigrations(SqlMigrationResolver.java:41)         at org.flywaydb.core.internal.resolver.CompositeMigrationResolver.collectMigrations(CompositeMigrationResolver.java:126)         at org.flywaydb.core.internal.resolver.CompositeMigrationResolver.doFindAvailableMigrations(CompositeMigrationResolver.java:108)         at org.flywaydb.core.internal.resolver.CompositeMigrationResolver.resolveMigrations(CompositeMigrationResolver.java:94)         at org.flywaydb.core.internal.resolver.CompositeMigrationResolver.resolveMigrations(CompositeMigrationResolver.java:42)         at org.flywaydb.core.internal.info.MigrationInfoServiceImpl.refresh(MigrationInfoServiceImpl.java:96)         at org.flywaydb.core.internal.command.DbValidate$2.doInTransaction(DbValidate.java:136)         at org.flywaydb.core.internal.command.DbValidate$2.doInTransaction(DbValidate.java:131)         at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:72)         at org.flywaydb.core.internal.command.DbValidate.validate(DbValidate.java:131)         at org.flywaydb.core.Flyway.doValidate(Flyway.java:1014)         at org.flywaydb.core.Flyway.access$300(Flyway.java:52)         at org.flywaydb.core.Flyway$1.execute(Flyway.java:925)         at org.flywaydb.core.Flyway$1.execute(Flyway.java:919)         at org.flywaydb.core.Flyway.execute(Flyway.java:1320)         at org.flywaydb.core.Flyway.migrate(Flyway.java:919)         at org.flywaydb.core.Flyway$migrate$0.call(Unknown Source)         at org.flywaydb.gradle.task.FlywayMigrateTask.run(FlywayMigrateTask.groovy:30)         at org.flywaydb.gradle.task.FlywayMigrateTask$run.callCurrent(Unknown Source)         at org.flywaydb.gradle.task.AbstractFlywayTask.runTask(AbstractFlywayTask.groovy:75)

3.1 is ancient. Can you test with the latest version to see if it also occurs?

Hi,
The issue also occurs with the latest version of flyway.
I am planning to implement migrations over mysql database and my sample gradle.build looks like this:
buildscript {
    repositories {
        mavenCentral()
    }
    dependencies {
        classpath 'mysql:mysql-connector-java:5.1.34'
    }
}

plugins {
    id "org.flywaydb.flyway" version "4.0.3"
}

flyway {
    url = 'jdbc:mysql://localhost:3306/flywayTest'
    user = 'root'
    password = 'Test!23'
    schemas = ['flywayTest']
    baselineVersion = 1
    baselineDescription = "Let's go!"
}

`flywayMigrations vinayabhishek$ gradle flywayMigrate
Parallel execution is an incubating feature.
:flywayMigrate FAILED
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':flywayMigrate'.

Java heap space

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED
Total time: 1.6 secs`

It seems to occur while loading your migration files from the classpath. How large are they?

Any news?

buildscript {
    dependencies {
        classpath 'mysql:mysql-connector-java:5.1.34'
    }
}

plugins {
    id "org.flywaydb.flyway" version "4.0.3"
}

flyway {
    url = 'jdbc:mysql://<IP_ADDRESS>:3306/testbase'
    user = 'user'
    password = 'root!23'
    schemas = ['testbase']
    baselineVersion = 1
    baselineDescription = "Baselining DB Schema"
}

The problem was with the user not being privileged  to access the database.
Thanks for the follow up and sorry for the delayed response.


./gradlew app:iD -PfastBuild --offline --warning-mode all --stacktrace Caused by: java.lang.NoClassDefFoundError: com/android/build/gradle/tasks/factory/AndroidJavaCompile

This looks like it's a problem in FastCompileJavaTask. This isn't something that's a part of Gradle. My guess is that it's making a reference to an Android type and that type isn't on the classpath.

Oh I got it! Thank you very much!


Cannot be displayed on right side of large screens?

I have an iMac5K which has a screen resolution of 5120 x 2880.
When I move the keycastr display to about 2/3rds of the way on the right hand of the screen, it disappears permanently. I have to restart the app to get it back. Please advise.

I believe this is this: https://github.com/keycastr/keycastr/issues/175

Apologies for missing this issue before! Yes, there is a related issue in #175 but I'm surprised to see this happen on a single (albeit large) screen. The fix for #175 should also address this -- the backing frame for the visualizer is unreasonably large and things don't go well when it's mostly offscreen.


Select options editor enhancements

Editing an option, but only the value results in creation of an option with empty label. Empty label should be considered as "no label". clearing the label input should be regarded as "deleting the label"
https://user-images.githubusercontent.com/2109932/177144345-a3c89642-ffd6-47e6-9ad9-bce3a7435a39.mov

in the video above, also notice the horizontal scrollbar when the list is empty

You can add an option using the "enter" key, but there should be a "+" button to the side as well, for discoverability

@Janpot Can you add reference screenshot for this task ?

👍  done

You can add an option using the "enter" key, but there should be a "+" button to the side as well, for discoverability

A "+" button on the side of the input? Does the helper text on the input not make the "enter" feature discoverable?

A "+" button on the side of the input? Does the helper text on the input not make the "enter" feature discoverable?

As a thought exercise, imagine a search input. Which one has the better UX?

The one that has a magnifying glass icon inside
The one that has a helper text underneath that says "press Enter to search"


api: connection limits

What this PR does / why we need it:
Adds a container for connection-level settings to CTP called Connection. Currently, connection will only support the Limit attribute for setting the max concurrent limits. Limits will be enforced using the Envoy Connection Limit Filter.
When a CTP with a connection limit attaches to a Gateway, each Listener will inherit the parent gateway's limit. This proposal does not deal with Envoy listener runtime connection limits.
In the future, we can consider using this container for #2600, #2670, downstream TCP keepalive, connection local rate limits, ...
Which issue(s) this PR fixes:
Relates to #2685

/retest

/retest

/retest

/retest

/retest

/retest

/retest


NERDTreeToggle doesn't work!

Hi,
I'v just installed, changed the nerd tree toggle to  and got the following
E492: Not an editor command: NERDTreeToggle
I'm guessing that this means NERDTree isn't installed ?
Should we add all the plugins manually?
/Stephen.

apologies.. had to do :PluginUpdate to install the relevant plugins .. Thought this would happen automatically..
Time to code!


Fingerprint function failing

Hi, I'm getting this (obfuscated personal info):
cjones@cjones-mbp$ bimmerconnected fingerprint<EMAIL_ADDRESS>MyP@ssw0rd north_america WBY1234567890
usage: bimmerconnected [-h] {status,fingerprint,lightflash,image} ...
bimmerconnected: error: unrecognized arguments: WBY1234567890

cjones@cjones-mbp$ bimmerconnected fingerprint<EMAIL_ADDRESS>MyP@ssw0rd north_america
DEBUG:bimmer_connected.account:Getting vehicle list
DEBUG:bimmer_connected.account:getting new oauth token
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): b2vapi.bmwgroup.us:443
DEBUG:urllib3.connectionpool:https://b2vapi.bmwgroup.us:443 "POST /webapi/oauth/token HTTP/1.1" 400 None
ERROR:bimmer_connected.account:Unknown status code 400, expected 200
ERROR:bimmer_connected.account:{
  "error" : "invalid_grant",
  "error_description" : "the authN circuit failed"
}
Traceback (most recent call last):
  File "/Users/cjones/.local/share/virtualenvs/python-LG6-DRlH/bin/bimmerconnected", line 106, in <module>
    main()
  File "/Users/cjones/.local/share/virtualenvs/python-LG6-DRlH/bin/bimmerconnected", line 44, in main
    args.func(args)
  File "/Users/cjones/.local/share/virtualenvs/python-LG6-DRlH/bin/bimmerconnected", line 72, in fingerprint
    log_responses=time_dir)
  File "/Users/cjones/.local/share/virtualenvs/python-LG6-DRlH/lib/python3.6/site-packages/bimmer_connected/account.py", line 55, in __init__
    self._get_vehicles()
  File "/Users/cjones/.local/share/virtualenvs/python-LG6-DRlH/lib/python3.6/site-packages/bimmer_connected/account.py", line 181, in _get_vehicles
    self._get_oauth_token()
  File "/Users/cjones/.local/share/virtualenvs/python-LG6-DRlH/lib/python3.6/site-packages/bimmer_connected/account.py", line 88, in _get_oauth_token
    expected_response=200, post=True)
  File "/Users/cjones/.local/share/virtualenvs/python-LG6-DRlH/lib/python3.6/site-packages/bimmer_connected/account.py", line 128, in send_request
    raise IOError(msg)
OSError: Unknown status code 400, expected 200

macOS 10.14
Python 3.6.1
bimmer-connected 0.5.1
It's strange that it wouldn't work at all when I provided a VIN, and then if I leave the VIN off I get invalid_grant

@ipv6freely Thank you for the hint, there the documentation was outdated, you do not need the  argument any more.
BMW seems to have recently changed the urls of their servers. I did fix this for rest_of_world. Can you please try with the latest version and see if this also fixes is for north_america?

@m1n3rva verified that north_america is now working.


WIP: Introduce etcd playbook

Following effort in https://github.com/kubernetes/contrib/pull/967, this PR introduces etcd-setup playbook. Changes:

introduce localhost inventory
merge etcd_modified and etcd2_modified, update restart etcd task so it can be run as self-standing task

@stephenrlouie can you review?

@redhat-k8s-bot test please

I will rebase the PR once https://github.com/kubernetes/contrib/pull/967 gets merged.

@gouyang

Following effort in #967, this PR introduces etcd-setup and etcd-update playbooks.

I don't see an etcd-update here.
Restart changes look good. Lots of overlap with #967, but once thats merged and this is rebased it should be a much smaller PR.

Following effort in #967, this PR introduces etcd-setup and etcd-update playbooks.

I don't see an etcd-update here.

I have removed it as there is no way to set tags within a playbook [1]
[1] http://stackoverflow.com/questions/25674649/ansible-in-a-playbook-filter-a-role-by-tags-without-passing-at-the-command-l?answertab=votes#tab-top

@redhat-k8s-bot test please

looks good to me now