[$500] No background color displayed on emoji on search

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1697723567806059
Action Performed:

Open the app
Open any report
Click on emoji to open emoji picker
Search for any emoji eg: joy
Observe that no background color is displayed on first emoji in search
Press enter and observe that first emoji is selected

Expected Result:
App should display background color to first emoji on search as we select first emoji on enter click after search
Actual Result:
App does not display background color to first emoji on search
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/93399543/b5024f57-4e68-48cd-adc2-c9c5540798a1

Android: mWeb Chrome

https://github.com/Expensify/App/assets/93399543/a6d8a3c4-3443-4557-9983-1beb2f74886d

iOS: Native

https://github.com/Expensify/App/assets/93399543/beae24e8-945a-4450-bd0b-5454c489180e

iOS: mWeb Safari

https://github.com/Expensify/App/assets/93399543/6af08ac7-eee6-4266-83dc-1e08d88498b0

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/93399543/55a875a6-53a1-4d4b-8d68-c2db3fe9fd00
https://github.com/Expensify/App/assets/93399543/8b871991-ccb7-4d42-aacf-ba59c59a64a2

MacOS: Desktop

https://github.com/Expensify/App/assets/93399543/085876c6-3b70-4be9-9cb1-149f185620c7

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0136219e9671ca8f96
Upwork Job ID:<PHONE_NUMBER>534409216
Last Price Increase: 2023-10-19

Proposal
Please re-state the problem that we are trying to solve in this issue.
When searching in EmojiPicker, the first emoji isn't highlighted
What is the root cause of that problem?
We're showing focused emoji only when isUsingKeyboardMovement is true
https://github.com/Expensify/App/blob/18acd82f40153fc1e5091aea3217c532142e500e/src/components/EmojiPicker/EmojiPickerMenu/index.js#L440
But when the search input gets focused, this value is set to false
This is the root cause
What changes do you think we should make in order to solve the problem?
We need to set isUsingKeyboardMovement when searching emojis
Add the following code to filterEmojis function above this line
https://github.com/Expensify/App/blob/18acd82f40153fc1e5091aea3217c532142e500e/src/components/EmojiPicker/EmojiPickerMenu/index.js#L189
        setIsUsingKeyboardMovement(Boolean(searchTerm));

This works as expected

Result

What alternative solutions did you explore? (Optional)

I think we should handle it as a regression from this issue https://github.com/Expensify/App/issues/29004, we did not notice this behaviour changed and we want to keep it

@dylanexpensify can you pay @dhanashree-sawant for reporting this and we will hande a fix in the linked issue

Yes! @dhanashree-sawant please apply https://www.upwork.com/jobs/~01bf495fd961ad294a

Hi @dylanexpensify, if possible, can you send me invite or offer for the job?

Payment coming up!

@dhanashree-sawant invited!

Thanks @dhanashree-sawant I have accepted the invite.

invite sent!

done!


Fix yolo configuration with PipeCNN to get correct outputs

Need to play with precision config for fixed point representation as well as fixing pooling issues

Finally figured out how to configure the fixed point params for the weights file as well as how to merge the batch norm and scaling layers into the convolution layers.
Also figured out that the data we get out of PipeCNN needs to be multipled by 2^-f_out, where f_out is the number of fractional bits configured for the last layers output.
So I figured out the precision_config for frac_w (number of fractional bits for the weights in each layer),  problem now is how to figure out the precision_config for frac_din and frac_dout (number of fractional bits for the input and output data of each layer). The weights were easier to figure out since we have the weights file data and can just look at the range of values in each layer. The data in/out is tricker however, since we somehow have to figure out the range of values outputted from each layer. Opened an issue for it here: https://github.com/doonny/PipeCNN/issues/64
The paper does describe the technique they use to determine the fixed point values, but I dont know how we would go about doing this ourselves:

Ok so I converted our weights file to Keras and used this implementation of tiny-yolo to get the data output of each layer and see what the ranges of values were, and then came up with the appropriate fractional widths for each layer in our network:
I set the precision config according to these values and ran the classifier again and passed the results to YOLO.cpp. The values outputted from the network seem more "real" now, but the result is still incorrect. I think this is because the input/output of each layer is very different when using fixed point representation (will be large whole integers instead of floats), so looking at the data from keras which is floating point doesnt help. We will need to read the values outputted in each layer from PipeCNN directly. @nocduro do you have any idea how we can do this? Maybe adding something to conv_pipe.cl that will save the output of each layer to a file or something?

On the bright side, our weights and anchors and the rest of our config is working well! I recreated our PipeCNN network in Keras, used our weights, and got these results:

Nice work!

do you have any idea how we can do this? Maybe adding something to conv_pipe.cl that will save the output of each layer to a file or something?

I'll take a look at this tomorrow, I think we can actually do it right from main.cpp by reading out the buffers (?) before going onto the next layer. It might be a bit tricky since I believe some layers save their results different buffers.
Relevant loop: https://github.com/hammadj/Qwik-e-Classifier/blob/yolo/PipeCNN/project/host/main.cpp#L411

Yea, might be a bit tricky. main.cpp mostly just configures all the arguments for the cl kernel and sends it the input data and output data, doesnt really read the data back for intermediate layers. Here's the part where they actually extract data from the kernel: https://github.com/hammadj/Qwik-e-Classifier/blob/yolo/PipeCNN/project/host/main.cpp#L866

Truncating weight is easy, it is hard to truncate the featuremap, as it should be done at runtime. You need modification on Darknet itself.


Increase PSGallery timeout to 5 minutes

What does this PR do?

Increase timeout for E2E setup of PSGallery
Motivation

https://datadoghq.atlassian.net/browse/WINA-902
Follow up to https://github.com/DataDog/datadog-agent/pull/28679
Since loop was added, we've had two failures that hung on the first command execution until the timeout is triggered
Set-PSRepository PSGallery -InstallationPolicy Trusted

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Better support for rate limited calls

Is your feature request related to a problem? Please describe.
We are using OpenAI's GPT-4o model for evaluation, and are often getting rate limited. This manifests as the run for a prompt returning "API call error: TypeError: Cannot read properties of undefined (reading 'message')". Then I re-run the same config, and thanks to caching of the not-failed responses, it usually gets farther along.
Describe the solution you'd like
I think my ideal solution would be to wait when rate-limited and try again after the rate limit has expired, and to retry queries that fail in this way (perhaps up to a certain amount.)
It's also possible there are other intermittent errors (503? 5xx?) that we could handle in a similar way. But this is the most painful one for us at the moment.
Describe alternatives you've considered
Our workaround is to just re-run it manually until there are no API-related errors, but this seems less than desirable. It's possible we could parse through the recent runs to detect this and re-run with delay, but that seems like something the framework should handle. I've also turned down the concurrency and used the delay parameter, but this just makes it happen less often at the cost of potentially more delay than needed.
Additional context
Happy to try to look into this, especially if you have some pointers on where we could do this.

Based on searching the codebase for that error string, it looks like the code for my case is around:
https://github.com/promptfoo/promptfoo/blob/5e500625e3da15478e9f2838323a7d832bb23958/src/providers/openai.ts#L562
(although there are other providers where this would likely be useful as well)

I also see some tests for rate limiting at: https://github.com/promptfoo/promptfoo/blob/5e500625e3da15478e9f2838323a7d832bb23958/test/rateLimit.test.ts

Hey @panozzaj, thanks for the pointers. I was in that area of the codebase anyway so I made some improvements in #1981.  Hopefully that helps


Why is there no import prompt in *.vue?

在*.vue文件中，为什么没有导入提示;*.ts文件里是正常的。如图。
In *.ts, import prompt  work well

but in *.vue,no import prompt

Hey @jinglun2019,
I'm using Webstorm as the IDE of my choice and there it's working without any issue. Since you are using VSCode you probably should consider using the Volar plugin.


French lang update

Hi Fred,
why you want to change the permission files, from 0644 to 0755 (Execute permission).
Regards

Hi Diego,
I do not touch the file permissions, this should be the customer github...

Sorry Fred, but the right permissions are, 755 for directories, and 644 for files.


ACCUMULO-4518 Use Jekyll posts for releases

Made releases Jekyll posts so they now show in Latest News
and RSS feed.
Reorganized and simplified navbar
Created user manual, examples, and javadoc archive pages
Remove old documentation page
Moved 1.3 user manual to 1.3/ directory

LGTM!

Looks giggity giggity good.

It would be nice to update the download page to point directly to the new location of the release notes

It would be nice to update the download page to point directly to the new location of the release notes

I can do that

I like the new automatically release archive page


create revise_specs()

i keep using replace() or $<- to adjust my specs list, but neither of these is very clean
also, it would be nice to offer some argument checking in revise_specs at some point

heh. would it be too goofy to call this function respecs()?


Update production database: 1.2 -> 1.3

Created by: @bayegan Sep 08 2021 at 20:54 CET
Last updated: Jul 18 2022 at 11:03 CET
ClickUp ID: IK-1470
Update production database from 1.2 to 1.3.
Required for RIOT features.

Commented by: @bayegan Sep 08 2021 at 20:55 CET
@maprokes : FYI


Add shortcuts app

Awesome! Thanks for doing this! I was meaning to do something exactly like this but I never had time. It's nice using clockupdown as well, since it'll work on the new Bangle too.
Although I guess there's also the option in future of allowing BTN2 to be reassigned. I know sometimes people have asked if that is possible.


SAK-29983 Modified User ID to 'Username' on User Audit Log screen in …

…Site-Info.
changed username property value from 'user.eid' to 'user.displayId' in eventLog.jsp

changed username property value from 'user.eid' to 'user.displayId' in eventLog.jsp

Can you explain this change?

If user has a displayId(cases when displayId is not same as eid) it is better to show the displayId as eid does not mean much to end user.


Summarise runtime config at startup

Via @mikkelhegn, broken out from #1850:

I still think at least an acknowledgement of what runtime config was loaded would be great. ...
Using [llm_remote] and [key_value_store.remore_redis] runtime-config from /mikkels/fancy/setup.toml
That level of detail I think would be a good balance.

(Ivan again) Printing the file name is particular attractive if the runtime config is coming from an environment variable where it's not visible on the command line.

Thx @itowlson


Database restructuring, better handling of Challenge and Task instances

Merged Test.java and Implementation.java into a single class TaskImplementation.java. Added new attributes to support handling of tasks and their implementations. Created new class ChallengeImplementation.java to handle instances of challenges. (Adding tests while lramirez checks the code integrity)

@lramirez this took way more time than I anticipated. I added database-field constraints which broke the simple testing setup. Took hours to get things sorted out. Now everything should be good to go.


[6.0] [DebugInfo] Salvage debug info for allocations in SILSROA

Explanation: Debug Value instructions pointing to an allocation split by SILSROA were dropped. This PR fixes this by recreating debug values for each new allocation introduced by SILSROA. Also, when an empty struct or tuple is split, a debug value of undef is emitted in place of the allocation and the previous debug values, to avoid losing track of the 0-size variable.
Scope: Adds debug value instructions in the SILSROA pass
Original PR: #72776
Risk: Low, only debug instructions are added
Testing: New tests have been added
Issue: None
Reviewer:  @adrian-prantl

@swift-ci please test


Use TLS

This uses native-tls to enable TLS for the connections.
Without it, this can only do unencrypted connections.
The reason for the lack of TLS I believe is because we've been using a local proxy (StrongDM) which handles TLS internally; the actual PG connection is unencrypted. If we want to use this in production, directly connecting to the database, we need TLS.
This should still create a portable executable since it uses the native MacOS TLS implementation + statically linked OpenSSL on Linux.

So the precise plan is to enable that option for us since AWS doesn't sign their certs (shame on them), but I think it's worth delegating to a config option rather than the default since I agree that it's the wrong behaviour.


'torch' module not found during 'stable-fast' installation

Environment Information:

Python Version: 3.10.13
Virtual Environment: venv (confirmed)
torch Version: 2.1.0 (installed in the venv)
pip Version: 23.3.1
OS: Linux

Problem Description:
When trying to install the stable-fast package, I encounter a ModuleNotFoundError: No module named 'torch'. I have confirmed that torch is installed in the virtual environment using pip list. Also, no package conflicts were detected with pip check.
Attempted Solutions:

Reconfirmed the installation of torch in the virtual environment.
Tested in a different virtual environment.

Additional Information:
The same error occurs when installing directly from the GitHub repository and from PyPI.
I would appreciate any suggestions or solutions to this problem.

@Prof-Cheese That sounds impossible. Can you confirm that torch is available in you env? What's the output of python3 -m torch.utils.collect_env and pip3 list?

Thank you for your response. Here are the requested details:
Output of python3 -m torch.utils.collect_env:

PyTorch version: 2.1.0+cu121
CUDA used to build PyTorch: 12.1
Python version: 3.10.13
OS: Manjaro Linux (x86_64)
Is CUDA available: True
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 3060
Nvidia driver version: 535.129.03

Output of pip list:

torch: 2.1.0
torchaudio: 2.1.0
torchvision: 0.16.0
triton: 2.1.0
diffusers: 0.23.1
numpy: 1.26.2
[and other installed packages...]

I confirm that torch is installed in my environment. I hope this information helps in diagnosing the issue with installing stable-fast.

For thoroughness, I have taken screenshots of both pip3 list and pip list outputs. Additionally, I want to mention that when I rebuilt the venv, I switched Python from version 3.11 to 3.10, but unfortunately, the issue persisted with both versions.

@Prof-Cheese Take a look at this
https://stackoverflow.com/questions/32004958/python-module-not-found-in-virtualenv

Problem Summary
Initially, I encountered an issue where torch was not recognized in my virtual environment. Following your advice and this Qiita article, I resolved the torch detection issue. However, now I'm facing a new problem.
/work/image/venv/lib/python3.10/site-packages/torch/cuda/init.py:138: UserWarning: CUDA initialization: CUDA unknown error - this may be due to an incorrectly set up environment, e.g. changing env variable CUDA_VISIBLE_DEVICES after program start. Setting the available devices to be zero. (Triggered internally at ../c10/cuda/CUDAFunctions.cpp:108.)
return torch._C._cuda_getDeviceCount() > 0
No CUDA runtime is found, using CUDA_HOME='/usr/local/cuda-12.1'

Additional Observations

nvidia-smi confirms that the GPU and driver are recognized correctly.
Running torch.cuda.is_available() in Python returns a similar error:

import torch
print(torch.cuda.is_available())
/work/image/venv/lib/python3.10/site-packages/torch/cuda/init.py:138: UserWarning: CUDA initialization: CUDA unknown error - this may be due to an incorrectly set up environment, e.g. changing env variable CUDA_VISIBLE_DEVICES after program start. Setting the available devices to be zero. (Triggered internally at ../c10/cuda/CUDAFunctions.cpp:108.)
return torch._C._cuda_getDeviceCount() > 0
False

Request for Assistance
I am seeking advice or suggestions to resolve this CUDA error during the installation of stable-fast. Any help would be greatly appreciated.

Do you have cuda toolkit installed on your system？

Yes, I have the CUDA toolkit installed. Interestingly, the earlier error I mentioned stopped occurring after I updated the GPU drivers. However, now I'm encountering a new error related to GCC version incompatibility. Given these issues, I'm starting to feel that Arch Linux might not be the best fit for a server environment, so I'm considering trying a different Linux distribution. Thanks for your help and advice!


build-pyi-bundle.sh from calico failing to pull scientificlinux.org

alagalah@thing2:calico (master)$ ./build-pyi-bundle.sh
+ set -e
+ docker build -t calico-pyi-build -f pyi/Dockerfile .
Sending build context to Docker daemon 1.436 MB
Step 1 : FROM ringo/scientific:6.5
6.5: Pulling from ringo/scientific
e17be29fd402: Pull complete
d2c1575ed524: Pull complete
Digest: sha256:24ce650ea771a19fb9efe60dc31f533eccf0a74c28bcec6db4f26bee550e6e37
Status: Downloaded newer image for ringo/scientific:6.5
 ---> c4cbfd88c72c
Step 2 : MAINTAINER Shaun Crampton<EMAIL_ADDRESS> ---> Running in c19333a95b4a
 ---> 5abe3879a31a
Removing intermediate container c19333a95b4a
Step 3 : RUN yum -y groupinstall "Development tools";     yum -y install zlib-devel bzip2-devel openssl-devel ncurses-devel sqlite-devel
 ---> Running in 862f96a1fde1
http://ftp.scientificlinux.org/linux/scientific/6.5/x86_64/os/repodata/repomd.xml: [Errno 14] PYCURL ERROR 6 - "Couldn't resolve host 'ftp.scientificlinux.org'"
Trying other mirror.

< snip ... >

ERROR 6 - "Couldn't resolve host 'ftp.scientificlinux.org'"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: sl. Please verify its path and try again
The command '/bin/sh -c yum -y groupinstall "Development tools";     yum -y install zlib-devel bzip2-devel openssl-devel ncurses-devel sqlite-devel' returned a non-zero code: 1
alagalah@thing2:calico (master)$

This might be something to do with your environment?  I just tried this in an Ubuntu 16.04 GCE VM, from current master, and it succeeded.

Yes the issue was repeatable on my machine all day.

We found a problem with the docker network configuration (missing masquerade rule) that would have caused this.  Closing.


Add params and functions to allow recording and streaming SQL queries

Sorry didn't intend to open this PR here, just testing around in own fork

Updated the branch, should be ready for review.


Date parse error

Just a quick one...
Upgraded to 2.0.4 and started seeing this...
2017/05/04 10:03:14 [error] [plugin] [Forced] Date parse error: 2010-10-27 10:40:26 - DateTime::__construct(): Failed to parse time string (@2010-10-27 10:40:26) at position 8 (-): Double timezone specification
in /home/87707.cloudwaysapps.com/abwgaujfnm/public_html/craft/app/etc/plugins/BasePlugin.php (65)
in /home/87707.cloudwaysapps.com/abwgaujfnm/public_html/craft/plugins/feedme/FeedMe/Helpers/FeedMeDateHelper.php (45)
in /home/87707.cloudwaysapps.com/abwgaujfnm/public_html/craft/plugins/feedme/FeedMe/Helpers/FeedMeDateHelper.php (20)

What do the dates you're importing look like? 2010-10-27 10:40:26?


CardHeader without Avatar

I would really like to be able to remove the avatar prop from CardHeader and have it render without a a grey, blank avatar. Currently, you need to pass it an empty div to accomplish this. I will submit a PR

Hey, why did you close this?

I will open it again and make a pull request when I have some time later tonight.  I feel that if the card avatar prop is not set, it makes more sense to not render the avatar instead of it being being displayed greyed out. To achieve the no avatar look, you just need to pass in an empty div to the avatar prop. So I will make this the default if the prop is unassigned. Thanks for reaching out.
Sent from my iPhone

On Aug 24, 2015, at 12:25 PM, William Becker<EMAIL_ADDRESS>wrote:
Hey, why did you close this?
—
Reply to this email directly or view it on GitHub.

Ok, thanks! Was just wondering if you didn't think it was a problem anymore, since you closed it.

Any updates on this?
Can't seem to remove the avatar in v0.13.1.


Export completions imcomplete

Describe the bug
I use LabelStudio for a text classification task, with 3 class.

The page shows that there are 1964 tasks, while there are 1972 completions.
When I export the result in csv format or in json format, there are only 1868 completions，and 9 label are NaN, which is not my preset label.

I go into the docker container, and see that there are 1964 items in the generated source.json, while there are only 1868 items in the generated completions directory. It seems that something has been missing.
To Reproduce
I use config.json to make some configs for label studio service. All labeling tasks are described in tasks.json. And then I run docker-compose up to start the service. I limit the memory 8G, and set restarts always.

The page shows that there are 1964 tasks, while there are 1972 completions.

I don't set any filters.

Environment (please complete the following information):

OS: Linux debian 4.9.0-3-amd64
docker image: heartexlabs/label-studio:latest, 482d577e4e96
docker-compose version: docker-compose version 1.23.2

@JisongXie It means you have more than one completion per tasks most likely.

It looks like you are using very old version of Label Studio, the latest version is 1.2 and the commit is fb66049089c82636a831034876fb9adf75ecafab.

@makseq thanks, I take a try with the latest version.

Hope the latest LS version fixed this issue.


Error Loading eBPF Objects (softirq_entry)

What happened?
Kepler seems to have problems with eBPF on my current setup. Kepler logs state:
failed to create eBPF exporter: error loading eBPF objects: field KeplerIrqTrace: program kepler_irq_trace: attach Tracing/TraceRawTp: raw_tp softirq_entry not supported

However softirq_entry is present at /sys/kernel/debug/ on the host. I did find the similar issue #727 which points to to a permission problem. Do I need to configure my host differently?
What did you expect to happen?
Installation succeeds.
How can we reproduce it (as minimally and precisely as possible)?
helm install kepler kepler/kepler --namespace kepler --create-namespace
Anything else we need to know?
OS: Ubuntu 20.04.3 LTS x86_64
Host: SYS-1019GP-TT<PHONE_NUMBER>
Kernel: 5.4.0-192-generic
CPU: Intel Xeon Silver 4208 (16) @ 3.200GHz
GPU: NVIDIA Quadro RTX 5000
GPU: NVIDIA Quadro RTX 5000
Memory: 95208MiB
Kepler image tag

I0905 08:13:52.281482       1 gpu.go:38] Trying to initialize GPU collector using dcgm
W0905 08:13:52.281702       1 gpu_dcgm.go:104] There is no DCGM daemon running in the host: libdcgm.so not Found
W0905 08:13:52.281727       1 gpu_dcgm.go:108] Could not start DCGM. Error: libdcgm.so not Found
I0905 08:13:52.281733       1 gpu.go:45] Error initializing dcgm: not able to connect to DCGM: libdcgm.so not Found
I0905 08:13:52.281739       1 gpu.go:38] Trying to initialize GPU collector using nvidia-nvml
I0905 08:13:52.281789       1 gpu.go:45] Error initializing nvidia-nvml: failed to init nvml. ERROR_LIBRARY_NOT_FOUND
I0905 08:13:52.281798       1 gpu.go:38] Trying to initialize GPU collector using dummy
I0905 08:13:52.281803       1 gpu.go:42] Using dummy to obtain gpu power
I0905 08:13:52.285110       1 exporter.go:100] Kepler running on version: v0.7.11
I0905 08:13:52.285158       1 config.go:284] using gCgroup ID in the BPF program: true
I0905 08:13:52.285182       1 config.go:286] kernel version: 5.4
I0905 08:13:52.285247       1 config.go:311] The Idle power will be exposed. Are you running on Baremetal or using single VM per node?
I0905 08:13:52.285302       1 power.go:53] use sysfs to obtain power
I0905 08:13:52.285315       1 redfish.go:169] failed to get redfish credential file path
I0905 08:13:52.289657       1 power.go:73] using acpi to obtain power
I0905 08:13:52.292851       1 exporter.go:89] Number of CPUs: 16
F0905 08:13:52.412014       1 exporter.go:140] failed to create eBPF exporter: error loading eBPF objects: field KeplerIrqTrace: program kepler_irq_trace: attach Tracing/TraceRawTp: raw_tp softirq_entry not supported

Kubernetes version

$ kubectl version
Client Version: v1.30.4+k3s1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.4+k3s1

Cloud provider or bare metal
Bare Meal
OS version

# On Linux:
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.3 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.3 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

$ uname -a
Linux gpu01 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Install tools
helm according to the docs with default values
Kepler deployment config

$ kubectl describe pod -l app.kubernetes.io/name=kepler -n kepler
Name:             kepler-9qknx
Namespace:        kepler
Priority:         0
Service Account:  kepler
Node:             gpu01/<IP_ADDRESS>
Start Time:       Thu, 05 Sep 2024 08:20:19 +0000
Labels:           app.kubernetes.io/component=exporter
                  app.kubernetes.io/name=kepler
                  controller-revision-hash=5d8c546465
                  pod-template-generation=1
Annotations:      <none>
Status:           Running
IP:               <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  DaemonSet/kepler
Containers:
  kepler-exporter:
    Container ID:  containerd://9d1f5d14b5ee7e74dc723dc9734efdf1ad4f1d10eb548da8a2631240406107d2
    Image:         quay.io/sustainable_computing_io/kepler:release-0.7.11
    Image ID:      quay.io/sustainable_computing_io/kepler@sha256:72e7cd2e866c696900b9b9a33a72fc61a77d06e1c0300b08074784510da4013a
    Port:          9102/TCP
    Host Port:     9102/TCP
    Args:
      -v=$(KEPLER_LOG_LEVEL)
    State:          Terminated
      Reason:       Error
      Exit Code:    255
      Started:      Thu, 05 Sep 2024 08:21:57 +0000
      Finished:     Thu, 05 Sep 2024 08:21:57 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    255
      Started:      Thu, 05 Sep 2024 08:21:09 +0000
      Finished:     Thu, 05 Sep 2024 08:21:09 +0000
    Ready:          False
    Restart Count:  4
    Liveness:       http-get http://:9102/healthz delay=10s timeout=10s period=60s #success=1 #failure=5
    Environment:
      NODE_IP:                      (v1:status.hostIP)
      NODE_NAME:                    (v1:spec.nodeName)
      METRIC_PATH:                 /metrics
      BIND_ADDRESS:                <IP_ADDRESS>:9102
      CGROUP_METRICS:              *
      CPU_ARCH_OVERRIDE:
      ENABLE_EBPF_CGROUPID:        true
      ENABLE_GPU:                  true
      ENABLE_PROCESS_METRICS:      false
      ENABLE_QAT:                  false
      EXPOSE_CGROUP_METRICS:       false
      EXPOSE_HW_COUNTER_METRICS:   true
      EXPOSE_IRQ_COUNTER_METRICS:  true
      KEPLER_LOG_LEVEL:            1
    Mounts:
      /lib/modules from lib-modules (rw)
      /proc from proc (rw)
      /sys from tracing (rw)
      /usr/src from usr-src (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-jvxx5 (ro)
Conditions:
  Type                        Status
  PodReadyToStartContainers   True
  Initialized                 True
  Ready                       False
  ContainersReady             False
  PodScheduled                True
Volumes:
  lib-modules:
    Type:          HostPath (bare host directory volume)
    Path:          /lib/modules
    HostPathType:  DirectoryOrCreate
  tracing:
    Type:          HostPath (bare host directory volume)
    Path:          /sys
    HostPathType:  Directory
  proc:
    Type:          HostPath (bare host directory volume)
    Path:          /proc
    HostPathType:  Directory
  usr-src:
    Type:          HostPath (bare host directory volume)
    Path:          /usr/src
    HostPathType:  Directory
  kube-api-access-jvxx5:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              kubernetes.io/os=linux
Tolerations:                 node-role.kubernetes.io/control-plane:NoSchedule
                             node.kubernetes.io/disk-pressure:NoSchedule op=Exists
                             node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                             node.kubernetes.io/network-unavailable:NoSchedule op=Exists
                             node.kubernetes.io/not-ready:NoExecute op=Exists
                             node.kubernetes.io/pid-pressure:NoSchedule op=Exists
                             node.kubernetes.io/unreachable:NoExecute op=Exists
                             node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:
  Type     Reason     Age                 From               Message
  ----     ------     ----                ----               -------
  Normal   Scheduled  107s                default-scheduler  Successfully assigned kepler/kepler-9qknx to gpu01
  Normal   Pulled     107s                kubelet            Successfully pulled image "quay.io/sustainable_computing_io/kepler:release-0.7.11" in 564ms (564ms including waiting). Image size: 117793827 bytes.
  Normal   Pulled     106s                kubelet            Successfully pulled image "quay.io/sustainable_computing_io/kepler:release-0.7.11" in 459ms (459ms including waiting). Image size: 117793827 bytes.
  Normal   Pulled     90s                 kubelet            Successfully pulled image "quay.io/sustainable_computing_io/kepler:release-0.7.11" in 552ms (552ms including waiting). Image size: 117793827 bytes.
  Normal   Created    58s (x4 over 107s)  kubelet            Created container kepler-exporter
  Normal   Started    58s (x4 over 107s)  kubelet            Started container kepler-exporter
  Normal   Pulled     58s                 kubelet            Successfully pulled image "quay.io/sustainable_computing_io/kepler:release-0.7.11" in 490ms (490ms including waiting). Image size: 117793827 bytes.
  Warning  BackOff    23s (x8 over 105s)  kubelet            Back-off restarting failed container kepler-exporter in pod kepler-9qknx_kepler(63598b16-bf4d-4d1b-af97-55672ac817b4)
  Normal   Pulling    11s (x5 over 107s)  kubelet            Pulling image "quay.io/sustainable_computing_io/kepler:release-0.7.11"

Container runtime (CRI) and version (if applicable)
Containerd v1.7.20-k3s1
Related plugins (CNI, CSI, ...) and versions (if applicable)
No response

So I installed a newer version of the kernel and this fixed the issue. I think the minimum kernel requirements in the docs should be updated (or maybe I overlooked something?). I'd be happy to do this. Where do you think this should be stated best and what version is the minimum based on the eBPF features used?

Relates to: #1483
5.12 is the minimum supported kernel version: https://github.com/sustainable-computing-io/kepler/issues/1483#issuecomment-2144881310


Fix typos and markdowns

Found via these commands:
codespell -L crate,complies
markdownlint *.md --disable MD024

See a detailed description of the rules is available at
https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

Thanks for these fixes! I'm also bookmarking these tools for future (personal) use. They look very nice!

It seemed that I forgot to commit fixes for the markdown, please check, https://github.com/1Password/arboard/pull/74


New device: Pine64's Pinebook Pro

@samueldr @colemickens as promised here I am to try to work on samueldr/wip-pinebook-pro#25
The structure is the same of wip-pinebook-pro but the default kernel now is a custom kernel based on 5.16.18 with the patches from Manjaro. This way we have a working HDMI over Type-C.
I tried directly building from megous' kernel with poor results. I asked for help in the IRC/Matrix channel and in the end they suggested me to use the Manjaro's kernel PKGBUILD as reference.
I also slightly changed the README with this PR.
What do you think?
However please wait some days before merging PR since I want to better test this kernel, I had some kernel panics using 5.17.1 and I want to be sure they do not show up with this version .

Can't wait for this to be merged ^_^
@samueldr's repo worked very well for me as soon as I added console=tty0 to the kernel command line

The custom patched kernel isn't the default anymore since I had kernel panics several times. I tried many kernel versions with many different patches subsets but I didn't solved.
However I left the custom kernel (adding unstable to the name) in the overlay so if someone needs the DP alt mode over Type-C (I also added an "use at your own risk" in the README).
In my opinion this can be merged now, it's not what I hoped for, but at least it's a first step.

The custom patched kernel isn't the default anymore since I had kernel panics several times. I tried many kernel versions with many different patches subsets but I didn't solved. However I left the custom kernel (adding unstable to the name) in the overlay so if someone needs the DP alt mode over Type-C (I also added an "use at your own risk" in the README).
In my opinion this can be merged now, it's not what I hoped for, but at least it's a first step.

In this case I would not include the kernel for now as it will have no users, will bitrot and is already known not to work.

I think https://nixos.wiki/wiki/NixOS_on_ARM/PINE64_Pinebook_Pro should be updated now. I don't know how to do that, feel free to do it or point me in the correct direction

@miniBill I just added a reference to nixos-hardware in the wiki before  the other two repositories since I think the idea is that this place should become the new home for the Pinebook Pro. I think that page is really essential and any kind of information you want to add would be useful.
Maybe we should also open a PR to wip-pinebook-pro to change its README putting a link to this repository as the nix-community's unopinionated overlay (although they are the same currently).
Also, maybe this is not the best place to talk about this, still not sure about which place we could use.

I think https://nixos.wiki/wiki/NixOS_on_ARM/PINE64_Pinebook_Pro should be updated now. I don't know how to do that, feel free to do it or point me in the correct direction

The wiki has a login via github for quick sign/up.


All caps text in the tag component is harder to read

We advise against using all caps on GOV.UK, because it's harder for people to recognise words from their shape if they are in all caps.
But, we use all-caps in the tag component, which is current used in the phase banner and task list.
Done when

[ ] TBC
[ ] "Details of breaking change" section below completed to help with writing release notes

Details of breaking change

which users are affected: TBC
the change that’s been made: TBC
changes users will have to make: TBC
impact of users not making those changes: TBC

Design wise this is done, but approach to release needs to be discussed. See https://github.com/alphagov/govuk-frontend/pull/1549

I'd like to put an argument for keeping them as is, or to know if there's any evidence for this.
It's important that these tags look visually distinct on the page, and that they not look like links. In changing these to sentence case, I think we risk reducing the usability and distinctiveness of them.
As I understand it the guidance was based on research of reading comprehension for long form paragraphs of text. Was any of the research about single words in all caps? or do we have any evidence from usability testing that these are causing issues for users? It would be good to know if this change is based on any research or evidence of issues.

I'd like to put an argument for keeping them as is, or to know if there's any evidence for this.
It's important that these tags look visually distinct on the page, and that they not look like links. In changing these to sentence case, I think we risk reducing the usability and distinctiveness of them.
As I understand it the guidance was based on research of reading comprehension for long form paragraphs of text. Was any of the research about single words in all caps? or do we have any evidence from usability testing that these are causing issues for users? It would be good to know if this change is based on any research or evidence of issues.

Do you have any research which backs this up? I know they is a lot of research around All caps text reading for dyslexia and it being harder..

I'd like to put an argument for keeping them as is, or to know if there's any evidence for this.
It's important that these tags look visually distinct on the page, and that they not look like links. In changing these to sentence case, I think we risk reducing the usability and distinctiveness of them.
As I understand it the guidance was based on research of reading comprehension for long form paragraphs of text. Was any of the research about single words in all caps? or do we have any evidence from usability testing that these are causing issues for users? It would be good to know if this change is based on any research or evidence of issues.

Do you have any research which backs this up? I know they is a lot of research around All caps text reading for dyslexia and it being harder for them.

I've not personally ever seen issues with uppercase tags or heard from other teams that they were an issue (the uppercase aspect at least). As far as I know all the referenced research is about long-form blocks of text - not this sort of usage.
With that said, I'm not trying to argue there is no issue - only that we should keep in mind how this might otherwise impact the pattern. In a similar way to bold text - which should avoided in large blocks of text, but might make a specific piece of text clearer.

as a dyslexia person and someone how has done a lot of research around the topic. the way dyslexia people read is based on the shapes of words when something is all caps it looks like a block and can take more time for someone to read.
@tempertemper has done a lot of research into tags too and this was part of it.

Adding to what @mrkwrght says -  all capital letters are harder for users with dyslexia to read. The British Dyslexia Association advise against it (the bottom bullet point under the ‘readable fonts’ heading). Also the accessibility poster for users with dyslexia talks about this.

As discussed in the v4 prioritisation, we think this work would be good to do, but this is something that the task list working group will be looking at so it makes sense to wait and see what comes out of that. I'm going to move this into Nice To Have for now so we don't lose track of this work if the task list make a confident decision before v4 is released.

With the new design of the tag component which removes the forced uppercase, this is now solved.


what is 'tooling'?

I'm confused as to what the Tooling commit message means.
Thanks

@brujo-rojas I think, Tooling commit messages are used for commits which has added something that mechanized the process .Such as if you have configured some automated testing tools or added some auto deployment script. Basically when you have tooled(equipped) your application.

thanks 😄  I understand now

Thanks for answering @anuja-joshi! 😄


The return_route extension is utilized by coordinate-mediation and messagepickup

We are just clarifying some things in the protocol about the return_route as discussing the last DIF DID Comm meeting.
https://us02web.zoom.us/rec/share/iwQV16LJ9pDC_xInCSKfIIeSpagNEJDjJC4b55d8P3o4MWZDTthFA8ehMTovnThy.qUtcyz8pPHOlo9YG
Initial discussion in https://github.com/decentralized-identity/didcomm.org/issues/87

Added a suggestion, which adds a link, some clarification about frequency of the return-route header, and fixes a spelling error. This would apply to all the protocols.


Fix possible nil pointer access

There could be a nil pointer exception if the file is not found because that specific error is suppressed but not handled.

I was unable to create a backport for 1.21. @KN4CK3R, please send one manually. :tea:
go run ./contrib/backport 28428
...  // fix git conflicts if any
go run ./contrib/backport --continue

Since backport to v1.20 automatically failed, maybe it's OK to only backport to v1.21.


Run antivirus scan incorrect limitations/response

The following is not documented as a limitation or response:
When you send multiple API calls to run an antivirus scan for the same device, there are inconsistent results. It may depend on how much time has passed since you last issued the associated API call. Some duplicate calls returned the pending machine action instead of a new machine action and some duplicate calls returned HTTP 400 with the message "Action is already in progress".

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

ID: cddacda1-883b-3787-959a-4c4b84597424
Version Independent ID: e842b33c-4422-76e4-0bb1-b0e1cb66c818
Content: Run antivirus scan API
Content Source: microsoft-365/security/defender-endpoint/run-av-scan.md
Product: m365-security
GitHub Login: @mjcaparas
Microsoft Alias: macapara

@MastaDisasta Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/5992
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @MastaDisasta Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


update mmmarkdown, fixes link bug

fixes https://github.com/artsy/eigen/issues/266
I spent a good while tracking down where exactly the URL was being detected, making the change to pr to mmmarkdown, etc, then realized we didn't have the latest release and the problem appears to have been fixed.

Coooooool.

nice, a relative freebie

i'm going to update the markdown in admin so that the existing version of the app will display the links correctly.


Document how to enable access logging

It appears after https://github.com/cloudfoundry/tomcat-cnb/issues/5 that it is now possible to enable access logging for the image. However when we cat /layers/org.cloudfoundry.tomcat/catalina-base/logs/access_log.2020-01-10 after accessing our app, we don't see any logs reported.
How can we build or run the image so that it actually has access logs? It would be great to have some documentation for that.

Access logging does not got to log files within the container, as the filesystem would be ephemeral within the container and lost immediately on exit.  As with CF, access logs are printed to the console and each platform collects the output of the console in its own way.

We are fairly confident that the logs are also not going to standard out in our case.
We started the image with docker run -e LOGIN_CONFIG_URL=classpath:required_configuration.yml -e BPL_TOMCAT_ACCESS_LOGGING=true -p 9090:8080 cfidentity/uaa, and the first line of output is

Tomcat Access Logging enabled

Which based on https://github.com/cloudfoundry/tomcat-cnb/blob/21b67ea43ab6c3d6e6f69004c004feab7f944f3f/base/base.go#L123-L129 makes us think that we have enabled logging.
However, when we access our app  by going to http://localhost:9090/login, no output appears in either the window where we started the container, or in docker logs <container-name>.

During staging, what version of the Tomcat buildpack is used?
[builder] Cloud Foundry Apache Tomcat Buildpack 1.1.62
[builder]   Apache Tomcat Support 3.3.0: Contributing to layer
[builder]   Contributing Configuration
[builder]     Copying context.xml to /layers/org.cloudfoundry.tomcat/catalina-base/conf
[builder]     Copying logging.properties to /layers/org.cloudfoundry.tomcat/catalina-base/conf
[builder]     Copying server.xml to /layers/org.cloudfoundry.tomcat/catalina-base/conf
[builder]     Copying web.xml to /layers/org.cloudfoundry.tomcat/catalina-base/conf
[builder]   Contributing Access Logging Support
[builder]     Reusing cached download from buildpack
[builder]     Copying to /layers/org.cloudfoundry.tomcat/catalina-base/lib
[builder]     Writing .profile.d/access-logging
[builder]   Contributing Lifecycle Support
[builder]     Reusing cached download from buildpack
[builder]     Copying to /layers/org.cloudfoundry.tomcat/catalina-base/lib
[builder]   Contributing Logging Support
[builder]     Reusing cached download from buildpack
[builder]     Copying to /layers/org.cloudfoundry.tomcat/catalina-base/bin
[builder]     Writing /layers/org.cloudfoundry.tomcat/catalina-base/bin/setenv.sh
[builder]   Mounting application at /layers/org.cloudfoundry.tomcat/catalina-base/webapps/ROOT
[builder]     Writing CATALINA_BASE to launch
[builder]   Apache Tomcat 9.0.30: Contributing to layer
[builder]     Reusing cached download from buildpack
[builder]     Extracting to /layers/org.cloudfoundry.tomcat/tomcat
[builder]     Writing CATALINA_HOME to launch
[builder]   Process types:
[builder]     task:   catalina.sh run
[builder]     tomcat: catalina.sh run
[builder]     web:    catalina.sh run

In line with the title of the issue (but not the direction of the discussion), there is a need to improve the documentation on that flag and the others available at runtime.  I'll do that work as part of this.


Warnings running ansible-playbook main.yml

I'm getting these warning and not sure what I'm doing wrong
ansible-playbook main.yml
[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the
controller starting with Ansible 2.12. Current version: 3.7.3 (default, Jan 22
2021, 20:04:44) [GCC 8.3.0]. This feature will be removed from ansible-core in
version 2.12. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.
[WARNING]: Unable to parse /home/pi/internet-pi/inventory.ini as an inventory
source
[WARNING]: No inventory was parsed, only implicit localhost is available
[WARNING]: provided hosts list is empty, only localhost is available. Note that
the implicit localhost does not match 'all'
[WARNING]: Could not match supplied host pattern, ignoring: internet_pi
PLAY [internet_pi] *************************************************************
skipping: no hosts matched
PLAY RECAP *********************************************************************
Thanks

Hey,
Check that you have an inventory.ini in the directory
Thanks,
MiguelNdeCarvalho

Hello!
Same issue for me and I have the file inventory.ini in the directory
`phozon@computer:/mnt/c/Users/user/git/internet-pi$ ansible-playbook main.yml
[WARNING]: Ansible is being run in a world writable directory (/mnt/c/Users/user/git/internet-pi), ignoring it as an
ansible.cfg source. For more information see
https://docs.ansible.com/ansible/devel/reference_appendices/config.html#cfg-in-world-writable-dir
[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current
version: 3.7.3 (default, Jul 25 2020, 13:03:44) [GCC 8.3.0]. This feature will be removed from ansible-core in version
2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
[WARNING]: No inventory was parsed, only implicit localhost is available
[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match
'all'
[WARNING]: Could not match supplied host pattern, ignoring: internet_pi
PLAY [internet_pi] *****************************************************************************************************
skipping: no hosts matched
PLAY RECAP *************************************************************************************************************
phozon@computer:/mnt/c/Users/user/git/internet-pi$ ls
ansible.cfg  example.config.yml     images               inventory.ini  main.yml   requirements.yml  templates
config.yml   example.inventory.ini  internet-monitoring  LICENSE        README.md  tasks
phozon@computer:/mnt/c/Users/user/git/internet-pi$`

Hey,
How did you download the files @phoz0n? As I can see it is failing because of :
[WARNING]: Ansible is being run in a world writable directory (/mnt/c/Users/user/git/internet-pi), ignoring it as an
ansible.cfg source. For more information see

Thanks,
MiguelNdeCarvalho

Hello @MiguelNdeCarvalho I have cloned the git repository. I did not see that warning that you are mentioning. I will look into it, thanks!

Hey,
This warning is currently on your first line of the output that you sent.  Are you using this in WSL?
Thanks,
MiguelNdeCarvalho

My Bad Not Reading what it was telling me

@Buster351 - Is there any other issue you are having, or are you still having the issue in the first post?


 U: .

 U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4513/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 21s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 46s
master passed

+1 :green_heart:
checkstyle
1m  6s
master passed

-1 :x:
refguide
0m 45s
branch has 7 errors when building the reference guide.

+1 :green_heart:
spotless
0m 46s
branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 17s
the patch passed

+1 :green_heart:
checkstyle
1m  2s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  0s
The patch has no ill-formed XML file.

-1 :x:
refguide
0m 16s
patch has 7 errors when building the reference guide.

+1 :green_heart:
spotless
0m 44s
patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 14s
The patch does not generate ASF License warnings.

14m 18s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4513/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4513

Optional Tests
dupname asflicense checkstyle spotless xml refguide

uname
Linux eb3b3b357893 5.4.0-90-generic #101-Ubuntu SMP Fri Oct 15 20:00:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 414cfb30f6

refguide
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4513/1/artifact/yetus-general-check/output/branch-refguide.log

refguide
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4513/1/artifact/yetus-general-check/output/patch-refguide.log

Max. process+thread count
69 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4513/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

Arg.  U: .

 U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4513/2/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 30s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m  9s
master passed

+1 :green_heart:
checkstyle
1m  0s
master passed

-1 :x:
refguide
0m 49s
branch has 7 errors when building the reference guide.

+1 :green_heart:
spotless
0m 38s
branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 48s
the patch passed

+1 :green_heart:
checkstyle
1m  1s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  0s
The patch has no ill-formed XML file.

-1 :x:
refguide
0m 17s
patch has 7 errors when building the reference guide.

+1 :green_heart:
spotless
0m 44s
patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 10s
The patch does not generate ASF License warnings.

12m 21s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4513/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4513

Optional Tests
dupname asflicense checkstyle spotless xml refguide

uname
Linux 68c90b92a86e 5.4.0-90-generic #101-Ubuntu SMP Fri Oct 15 20:00:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / c24ba54147

refguide
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4513/2/artifact/yetus-general-check/output/branch-refguide.log

refguide
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4513/2/artifact/yetus-general-check/output/patch-refguide.log

Max. process+thread count
69 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4513/2/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Separate contract definitions from execution

So that we can keep contract definitions flexible and readily editable, they need to be defined outside of the main code base. To that end, define and implement a YAML-based contract definition language.

Done.


Fix glitch on separators with vibrancy effect

Now takes screenshot of the cell's content view instead of the whole cell.
This implies that the cell's separator will not move with the cell being swiped anymore.
This is the expected behavior if we want to mimic swipe effect in native iOS Mail app.
Related to issue #193.

Hi damien,
Thanks for the Pull Request. I can't merge because using cell.contentView instead of cell for the screenshot breaks swipping cells with accesory buttons/views. The problem is that accessory views are outside of cell's content view, that's why I take the screenshot of the whole cell.
I'll have an idea to fix this, will include in the next release if it works.


Firefox: can't change skin tone

The skin tone selector does not work on my Firefox 77 / macOS. For some reason, there's no activeElement on the focusout event when I click on a skin tone button.
https://github.com/nolanlawson/emoji-picker-element/blob/04f490a6cbfab567473cbcaa033d438d88b61535/src/picker/components/Picker/Picker.js#L587-L598

That blur event should only occur when you click _outside_of the skin tone picker. If you're trying to debug this, you may just comment out that entire thing, since it will probably be a bit annoying if, whenever you click inside of the DevTools, the skin tone picker disappears.
I can't repro in Firefox 77 on Ubuntu, so I wonder if this is an OS-specific thing? I'll try to find a Mac to check.

Huh, now that you mentioned... I checked and it only reproduces with an external Magic Trackpad. The Macbook's internal trackpad works fine. 🤦♂

Huh, well that's still a bug I'd like to fix... I wonder how that is possible?

I'll see if I can isolate it, I'm curious as well.

Okay, it seems it's purely a timing issue and that I've Skinner-boxed myself into a pattern that is not there. I haven't exactly figured out everything yet, but: the problem reproduces in Firefox and Safari (but not Chrome) when you take longer between mousedown and mouseup. It just so happens that using the external trackpad I click it down (slower) while the internal trackpad I tap (faster). If you're quick enough to click the button while the next frame kicks it (as per the await rAF part) it works. Otherwise the list gets hidden from underneath your nose.
Here's me holding down the trackpad on Firefox (notice the list disappears):

And here's Chrome, which on the mousedown already makes the button the activeElement, so I'm able to hold it down indefinitely:

Let me know if you're able to reproduce this on Linux!

Thanks for the detailed explanation. On Linux, I cannot reproduce either with a separate mouse or with my built-in Dell XPS trackpad, in either Chrome, Firefox, or GNOME Web (WebKit). I will try to grab a Mac so I can test there! (My wife has one; I'll just bug her to borrow it when she's done. :joy:)
If it's just a timing issue, then probably we can replace the requestAnimationFrame with something else (e.g. a setTimeout).
It's a shame that I can't use a more simple relatedTarget, but it's not supported in Safari. :disappointed:

Confirmed reproduce in Safari on MacOS. I'll write a fix.

Ah cool, let me know if I can help test it!


matching default functionality to slick

You took my attention to these lines in my last PR: https://github.com/kenwheeler/slick/blob/master/slick/slick.js#L54-L56
and I noticed this time around that the default for the dots content is actually { i + 1 } instead of { i }. So this basic change actually matches the default dot content for slick.
Here's a screenshot of the content from the first dot on slicks webpage.

This does, however, affect backwards compatibility. How would you like to proceed?
Also, I'm working on the customPaging option in a separate branch.

I'm going to close this until I can figure out why the build is failing

@akiran Any insight into why this is failing? I also pulled current master and npm run test failed locally with the same error.

@welbornio Since the error thrown did not provide much explanation (for me at least), I saw that the used version of PhantomJS was outdated (1.9). Latest version is 2.1.3 and updating to that seems to have fixed the problem.

@welbornio Ignore test failures for now.  I will fix the test setup soon and start writing tests.
In future, you can submit PR with code fix along with test .

It should not effect much, because that number will be replaced by dot if css and fonts are available.

@akiran do you mean as far as backward compatibility goes? I know that it's not a big change, but I have a use case on a project where we use the dots as numbered boxes, and we need the correct number.

Yes,  I mean its not a big problem for backward compatibility.
I will merge it today
On Tue, Feb 23, 2016 at 9:47 AM, Ethan Welborn<EMAIL_ADDRESS>wrote:

@akiran https://github.com/akiran do you mean as far as backward
compatibility goes? I know that it's not a big change, but I have a use
case on a project where we use the dots as numbered boxes, and we need the
correct number.
—
Reply to this email directly or view it on GitHub
https://github.com/akiran/react-slick/pull/244#issuecomment-187517916.

Awesome! Glad to hear it.


project preview not showing

Hi!
I have created a personal website and I have an issue with the "projects" section:
When I go to my list of projects in the main page, the project preview doesn't open. This means that in order to read the description of a project, my only option is to click on "all projects" and then open the project from there.
The thing is that this works perfectly fine when I use hugo server from my terminal. However, it doesn't work when I render my site and I don't know why... This is the link to my site, in case you want to take a look: https://irhuru.github.io/
I'm currently using MacOS (version 10.15.4) and Google Chrome, though I have tried with Safari as well and I still have the same problem.

Hi Irati! When I visit your site I see this in the console:
Mixed Content: The page at 'https://irhuru.github.io/' was loaded over HTTPS, but requested an insecure script
'http://irhuru.github.io/js/bundleOwlCarousel.afccb66….js'. This request has been blocked; the content must be
served over HTTPS.

How are you configuring your site address? Does your config.toml file have https:// in the baseURL?

I just realized there was a typo in that file!
Thanks 👍🏼

You're welcome! Glad you got it sorted out.


Release version 2.6.0

This is a component issue for 2.6.0.
Coming from opensearch-build__3081__. Please follow the following checklist.
Please refer to the DATES in that post.
How to use this issue

This Component Release Issue
This issue captures the state of the OpenSearch release, on component/plugin level; its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help.
Any release related work can be linked to this issue or added as comments to create visiblity into the release status.
Release Steps
There are several steps to the release process; these steps are completed as the whole component release and components that are behind present risk to the release. The component owner resolves the tasks in this issue and communicate with the overall release owner to make sure each component are moving along as expected.
Steps have completion dates for coordinating efforts between the components of a release; components can start as soon as they are ready far in advance of a future release. The most current set of dates is on the overall release issue linked at the top of this issue.
The Overall Release Issue
Linked at the top of this issue, the overall release issue captures the state of the entire OpenSearch release including references to this issue, the release owner which is the assignee is responsible for communicating the release status broadly.  Please contact them or @mention them on that issue for help.
What should I do if my plugin isn't making any changes?
If including changes in this release, increment the version on __2.x__ branch to __2.6.0__ for Min/Core, and __<IP_ADDRESS>__ for components. Otherwise, keep the version number unchanged for both.

Preparation

[x] Assign this issue to a release owner.
[x] Finalize scope and feature set and update the Public Roadmap.
[x] All the tasks in this issue have been reviewed by the release owner.
[x] Create, update, triage and label all features and issues targeted for this release with v2.6.0.

CI/CD

[x] All code changes for __2.6.0__ are complete.
[x] Ensure working and passing CI.
[x] Check that this repo is included in the distribution manifest.

Pre-Release

[ ] Update to the __2.6__ release branch in the distribution manifest.
[ ] Increment the version on the parent branch to the next development iteration.
[x] Gather, review and publish release notes following the rules and back port it to the release branch.git-release-notes may be used to generate release notes from your commit history.
[x] Confirm that all changes for __2.6.0__ have been merged.
[ ] Add this repo to the manifest for the next developer iteration.

Release Testing

[x] Find/fix bugs using latest tarball and docker image provided in parent release issue and update the release notes if necessary.
[x] Code Complete: Test within the distribution, ensuring integration, backwards compatibility, and performance tests pass.
[x] Sanity Testing: Sanity testing and fixing of critical issues found.
[x] File issues for all intermittent test failures.

Release

[ ] Complete documentation.
[ ] Verify all issued labeled for this release are closed or labelled for the next release.
[ ] Verify the release date mentioned in release notes is correct and matches actual release date.

Post Release

[ ] Prepare for an eventual security fix development iteration by incrementing the version on the release branch to the next eventual patch version.
[ ] Add this repo to the manifest of the next eventual security patch version.
[ ] Suggest improvements to this template.
[ ] Conduct a retrospective, and publish its results.

Tested the release candidate(opensearchstaging/opensearch:<IP_ADDRESS>56) using docker container.
ankikala$ curl -u 'admin:admin' -k "https://localhost:9200/_cat/nodes?v"
ip          heap.percent ram.percent cpu load_1m load_5m load_15m node.role node.roles                                        cluster_manager name
<IP_ADDRESS>           26          85  11    0.28    0.78     0.52 dimr      cluster_manager,data,ingest,remote_cluster_client *               follower1
ankikala$
ankikala$ curl -u 'admin:admin' -k "https://localhost:9201/_cat/nodes?v"
ip          heap.percent ram.percent cpu load_1m load_5m load_15m node.role node.roles                                        cluster_manager name
<IP_ADDRESS>           28          85  11    0.33    0.78     0.52 dimr      cluster_manager,data,ingest,remote_cluster_client *               leader1
ankikala$ curl -u 'admin:admin' -k -X PUT "https://localhost:9201/_cluster/settings?pretty" -H 'Content-Type: application/json' -d'
>   {
>     "persistent": {
>       "cluster": {
>         "remote": {
>           "remote-cluster": {
>             "seeds": [
>               "<IP_ADDRESS>:9300"
>             ],
>             "transport.ping_schedule": "30s"
>           }
>         }
>       }
>     }
>   }'
{
  "acknowledged" : true,
  "persistent" : {
    "cluster" : {
      "remote" : {
        "remote-cluster" : {
          "seeds" : [
            "<IP_ADDRESS>:9300"
          ],
          "transport" : {
            "ping_schedule" : "30s"
          }
        }
      }
    }
  },
  "transient" : { }
}
ankikala$ curl -k -u 'admin:admin' -X PUT "https://localhost:9200/remote-index?pretty" -H 'Content-Type: application/json' -d'
>   {
>     "settings": {
>       "index": {
>         "number_of_shards": 1,
>         "number_of_replicas": 0
>       }
>     }
>   }
>   '
{
  "acknowledged" : true,
  "shards_acknowledged" : true,
  "index" : "remote-index"
}
ankikala$
ankikala$ curl -k -u 'admin:admin' -X PUT "https://localhost:9201/_plugins/_replication/remote-index/_start?pretty" -H 'Content-Type: application/json' -d'
> {
>   "leader_alias": "remote-cluster",
>   "leader_index": "remote-index",
>   "use_roles": {
>     "leader_cluster_role": "all_access",
>     "follower_cluster_role": "all_access"
>   }
> }
> '

{
  "acknowledged" : true
}
ankikala$
ankikala$
ankikala$ curl -k -u 'admin:admin' "https://localhost:9200/_cat/indices?v"
health status index                        uuid                   pri rep docs.count docs.deleted store.size pri.store.size
green  open   remote-index                 794iZs_-Td-Utgw0WEGn1Q   1   0          0            0       208b           208b
green  open   .opensearch-observability    QQzOuxadRIaezY_JpYwzmQ   1   0          0            0       208b           208b
green  open   .opendistro_security         MPzQ1d8sQTaWsyv5H7e5mg   1   0         10            0     72.8kb         72.8kb
yellow open   security-auditlog-2023.02.28 8kj9JiSnT6KaKXsiPMZJ5A   1   1          7            0    130.3kb        130.3kb
ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_cat/indices?v"
health status index                        uuid                   pri rep docs.count docs.deleted store.size pri.store.size
green  open   remote-index                 RrEN4dSmRxCY2k9ODW94hw   1   0          0            0       208b           208b
green  open   .opensearch-observability    SPAvymEeSUWKPL-hQNYq4A   1   0          0            0       208b           208b
green  open   .opendistro_security         _SMkeeC1T8mjCkL8UpjGtA   1   0         10            0     72.8kb         72.8kb
yellow open   security-auditlog-2023.02.28 zv1PDlBqTKyBIXVfB1LD7A   1   1          4            0       58kb           58kb
ankikala$
ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "SYNCING",
  "reason" : "User initiated",
  "leader_alias" : "remote-cluster",
  "leader_index" : "remote-index",
  "follower_index" : "remote-index",
  "syncing_details" : {
    "leader_checkpoint" : -1,
    "follower_checkpoint" : -1,
    "seq_no" : 0
  }
}
ankikala$ curl -k -u 'admin:admin' -X POST "https://localhost:9200/remote-index/_doc/?pretty" -H 'Content-Type: application/json' -d'
>   {
>       "user" : "kimchy",
>       "post_date" : "2009-11-15T14:12:12",
>       "message" : "trying out Elasticsearch5"
>   }
>   '
{
  "_index" : "remote-index",
  "_id" : "U37omIYBW4n3o88yLPWW",
  "_version" : 1,
  "result" : "created",
  "_shards" : {
    "total" : 1,
    "successful" : 1,
    "failed" : 0
  },
  "_seq_no" : 0,
  "_primary_term" : 1
}
ankikala$
ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "SYNCING",
  "reason" : "User initiated",
  "leader_alias" : "remote-cluster",
  "leader_index" : "remote-index",
  "follower_index" : "remote-index",
  "syncing_details" : {
    "leader_checkpoint" : 0,
    "follower_checkpoint" : 0,
    "seq_no" : 1
  }
}
ankikala$ curl -k -u 'admin:admin' "https://localhost:9200/_plugins/_replication/leader_stats?pretty"
{
  "num_replicated_indices" : 1,
  "operations_read" : 1,
  "translog_size_bytes" : 245,
  "operations_read_lucene" : 0,
  "operations_read_translog" : 1,
  "total_read_time_lucene_millis" : 0,
  "total_read_time_translog_millis" : 5,
  "bytes_read" : 197,
  "index_stats" : {
    "remote-index" : {
      "operations_read" : 1,
      "translog_size_bytes" : 245,
      "operations_read_lucene" : 0,
      "operations_read_translog" : 1,
      "total_read_time_lucene_millis" : 0,
      "total_read_time_translog_millis" : 5,
      "bytes_read" : 197
    }
  }
}ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/follower_stats?pretty"
{
  "num_syncing_indices" : 1,
  "num_bootstrapping_indices" : 0,
  "num_paused_indices" : 0,
  "num_failed_indices" : 0,
  "num_shard_tasks" : 1,
  "num_index_tasks" : 1,
  "operations_written" : 1,
  "operations_read" : 1,
  "failed_read_requests" : 0,
  "throttled_read_requests" : 0,
  "failed_write_requests" : 0,
  "throttled_write_requests" : 0,
  "follower_checkpoint" : -1,
  "leader_checkpoint" : 0,
  "total_write_time_millis" : 185,
  "index_stats" : {
    "remote-index" : {
      "operations_written" : 1,
      "operations_read" : 1,
      "failed_read_requests" : 0,
      "throttled_read_requests" : 0,
      "failed_write_requests" : 0,
      "throttled_write_requests" : 0,
      "follower_checkpoint" : -1,
      "leader_checkpoint" : 0,
      "total_write_time_millis" : 185
    }
  }
}ankikala$
ankikala$ curl -k -u 'admin:admin' -X POST "https://localhost:9201/_plugins/_replication/remote-index/_pause?pretty" -H 'Content-Type: application/json' -d '{}'
{
  "acknowledged" : true
}
ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "PAUSED",
  "reason" : "User initiated",
  "leader_alias" : "remote-cluster",
  "leader_index" : "remote-index",
  "follower_index" : "remote-index"
}
ankikala$ curl -k -u 'admin:admin' -X POST "https://localhost:9201/_plugins/_replication/remote-index/_resume?pretty" -H 'Content-Type: application/json' -d '{}'
{
  "acknowledged" : true
}
ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "SYNCING",
  "reason" : "User initiated",
  "leader_alias" : "remote-cluster",
  "leader_index" : "remote-index",
  "follower_index" : "remote-index",
  "syncing_details" : {
    "leader_checkpoint" : 0,
    "follower_checkpoint" : 0,
    "seq_no" : 1
  }
}
ankikala$
ankikala$ curl -k -u 'admin:admin' -X POST "https://localhost:9200/remote-index/_doc/?pretty" -H 'Content-Type: application/json' -d'
>   {
>       "user" : "kimchy2",
>       "post_date" : "2009-11-15T14:12:12",
>       "message" : "trying out Elasticsearch5"
>   }
>   '
{
  "_index" : "remote-index",
  "_id" : "XX7pmIYBW4n3o88yuvVb",
  "_version" : 1,
  "result" : "created",
  "_shards" : {
    "total" : 1,
    "successful" : 1,
    "failed" : 0
  },
  "_seq_no" : 1,
  "_primary_term" : 1
}
ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "SYNCING",
  "reason" : "User initiated",
  "leader_alias" : "remote-cluster",
  "leader_index" : "remote-index",
  "follower_index" : "remote-index",
  "syncing_details" : {
    "leader_checkpoint" : 1,
    "follower_checkpoint" : 0,
    "seq_no" : 1
  }
}
ankikala$ curl -k -u 'admin:admin' -X POST "https://localhost:9201/_plugins/_replication/remote-index/_stop?pretty" -H 'Content-Type: application/json' -d '{}'
{
  "acknowledged" : true
}
ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "REPLICATION NOT IN PROGRESS"
}
ankikala$ curl -k -u 'admin:admin' -X POST "https://localhost:9201/remote-index/_doc/?pretty" -H 'Content-Type: application/json' -d'
>   {
>       "user" : "kimchy3",
>       "post_date" : "2009-11-15T14:12:12",
>       "message" : "trying out Elasticsearch5"
>   }
>   '
{
  "_index" : "remote-index",
  "_id" : "63DqmIYBCJZU_R3CVKtW",
  "_version" : 1,
  "result" : "created",
  "_shards" : {
    "total" : 1,
    "successful" : 1,
    "failed" : 0
  },
  "_seq_no" : 2,
  "_primary_term" : 4
}

Tested the release candidate(opensearchstaging/opensearch:<IP_ADDRESS>56) using docker container.
ankikala$ curl -u 'admin:admin' -k "https://localhost:9200/_cat/nodes?v"
ip          heap.percent ram.percent cpu load_1m load_5m load_15m node.role node.roles                                        cluster_manager name
<IP_ADDRESS>           26          85  11    0.28    0.78     0.52 dimr      cluster_manager,data,ingest,remote_cluster_client *               follower1
ankikala$
ankikala$ curl -u 'admin:admin' -k "https://localhost:9201/_cat/nodes?v"
ip          heap.percent ram.percent cpu load_1m load_5m load_15m node.role node.roles                                        cluster_manager name
<IP_ADDRESS>           28          85  11    0.33    0.78     0.52 dimr      cluster_manager,data,ingest,remote_cluster_client *               leader1
ankikala$ curl -u 'admin:admin' -k -X PUT "https://localhost:9201/_cluster/settings?pretty" -H 'Content-Type: application/json' -d'
>   {
>     "persistent": {
>       "cluster": {
>         "remote": {
>           "remote-cluster": {
>             "seeds": [
>               "<IP_ADDRESS>:9300"
>             ],
>             "transport.ping_schedule": "30s"
>           }
>         }
>       }
>     }
>   }'
{
  "acknowledged" : true,
  "persistent" : {
    "cluster" : {
      "remote" : {
        "remote-cluster" : {
          "seeds" : [
            "<IP_ADDRESS>:9300"
          ],
          "transport" : {
            "ping_schedule" : "30s"
          }
        }
      }
    }
  },
  "transient" : { }
}
ankikala$ curl -k -u 'admin:admin' -X PUT "https://localhost:9200/remote-index?pretty" -H 'Content-Type: application/json' -d'
>   {
>     "settings": {
>       "index": {
>         "number_of_shards": 1,
>         "number_of_replicas": 0
>       }
>     }
>   }
>   '
{
  "acknowledged" : true,
  "shards_acknowledged" : true,
  "index" : "remote-index"
}
ankikala$
ankikala$ curl -k -u 'admin:admin' -X PUT "https://localhost:9201/_plugins/_replication/remote-index/_start?pretty" -H 'Content-Type: application/json' -d'
> {
>   "leader_alias": "remote-cluster",
>   "leader_index": "remote-index",
>   "use_roles": {
>     "leader_cluster_role": "all_access",
>     "follower_cluster_role": "all_access"
>   }
> }
> '

{
  "acknowledged" : true
}
ankikala$
ankikala$
ankikala$ curl -k -u 'admin:admin' "https://localhost:9200/_cat/indices?v"
health status index                        uuid                   pri rep docs.count docs.deleted store.size pri.store.size
green  open   remote-index                 794iZs_-Td-Utgw0WEGn1Q   1   0          0            0       208b           208b
green  open   .opensearch-observability    QQzOuxadRIaezY_JpYwzmQ   1   0          0            0       208b           208b
green  open   .opendistro_security         MPzQ1d8sQTaWsyv5H7e5mg   1   0         10            0     72.8kb         72.8kb
yellow open   security-auditlog-2023.02.28 8kj9JiSnT6KaKXsiPMZJ5A   1   1          7            0    130.3kb        130.3kb
ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_cat/indices?v"
health status index                        uuid                   pri rep docs.count docs.deleted store.size pri.store.size
green  open   remote-index                 RrEN4dSmRxCY2k9ODW94hw   1   0          0            0       208b           208b
green  open   .opensearch-observability    SPAvymEeSUWKPL-hQNYq4A   1   0          0            0       208b           208b
green  open   .opendistro_security         _SMkeeC1T8mjCkL8UpjGtA   1   0         10            0     72.8kb         72.8kb
yellow open   security-auditlog-2023.02.28 zv1PDlBqTKyBIXVfB1LD7A   1   1          4            0       58kb           58kb
ankikala$
ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "SYNCING",
  "reason" : "User initiated",
  "leader_alias" : "remote-cluster",
  "leader_index" : "remote-index",
  "follower_index" : "remote-index",
  "syncing_details" : {
    "leader_checkpoint" : -1,
    "follower_checkpoint" : -1,
    "seq_no" : 0
  }
}
ankikala$ curl -k -u 'admin:admin' -X POST "https://localhost:9200/remote-index/_doc/?pretty" -H 'Content-Type: application/json' -d'
>   {
>       "user" : "kimchy",
>       "post_date" : "2009-11-15T14:12:12",
>       "message" : "trying out Elasticsearch5"
>   }
>   '
{
  "_index" : "remote-index",
  "_id" : "U37omIYBW4n3o88yLPWW",
  "_version" : 1,
  "result" : "created",
  "_shards" : {
    "total" : 1,
    "successful" : 1,
    "failed" : 0
  },
  "_seq_no" : 0,
  "_primary_term" : 1
}
ankikala$
ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "SYNCING",
  "reason" : "User initiated",
  "leader_alias" : "remote-cluster",
  "leader_index" : "remote-index",
  "follower_index" : "remote-index",
  "syncing_details" : {
    "leader_checkpoint" : 0,
    "follower_checkpoint" : 0,
    "seq_no" : 1
  }
}
ankikala$ curl -k -u 'admin:admin' "https://localhost:9200/_plugins/_replication/leader_stats?pretty"
{
  "num_replicated_indices" : 1,
  "operations_read" : 1,
  "translog_size_bytes" : 245,
  "operations_read_lucene" : 0,
  "operations_read_translog" : 1,
  "total_read_time_lucene_millis" : 0,
  "total_read_time_translog_millis" : 5,
  "bytes_read" : 197,
  "index_stats" : {
    "remote-index" : {
      "operations_read" : 1,
      "translog_size_bytes" : 245,
      "operations_read_lucene" : 0,
      "operations_read_translog" : 1,
      "total_read_time_lucene_millis" : 0,
      "total_read_time_translog_millis" : 5,
      "bytes_read" : 197
    }
  }
}ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/follower_stats?pretty"
{
  "num_syncing_indices" : 1,
  "num_bootstrapping_indices" : 0,
  "num_paused_indices" : 0,
  "num_failed_indices" : 0,
  "num_shard_tasks" : 1,
  "num_index_tasks" : 1,
  "operations_written" : 1,
  "operations_read" : 1,
  "failed_read_requests" : 0,
  "throttled_read_requests" : 0,
  "failed_write_requests" : 0,
  "throttled_write_requests" : 0,
  "follower_checkpoint" : -1,
  "leader_checkpoint" : 0,
  "total_write_time_millis" : 185,
  "index_stats" : {
    "remote-index" : {
      "operations_written" : 1,
      "operations_read" : 1,
      "failed_read_requests" : 0,
      "throttled_read_requests" : 0,
      "failed_write_requests" : 0,
      "throttled_write_requests" : 0,
      "follower_checkpoint" : -1,
      "leader_checkpoint" : 0,
      "total_write_time_millis" : 185
    }
  }
}ankikala$
ankikala$ curl -k -u 'admin:admin' -X POST "https://localhost:9201/_plugins/_replication/remote-index/_pause?pretty" -H 'Content-Type: application/json' -d '{}'
{
  "acknowledged" : true
}
ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "PAUSED",
  "reason" : "User initiated",
  "leader_alias" : "remote-cluster",
  "leader_index" : "remote-index",
  "follower_index" : "remote-index"
}
ankikala$ curl -k -u 'admin:admin' -X POST "https://localhost:9201/_plugins/_replication/remote-index/_resume?pretty" -H 'Content-Type: application/json' -d '{}'
{
  "acknowledged" : true
}
ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "SYNCING",
  "reason" : "User initiated",
  "leader_alias" : "remote-cluster",
  "leader_index" : "remote-index",
  "follower_index" : "remote-index",
  "syncing_details" : {
    "leader_checkpoint" : 0,
    "follower_checkpoint" : 0,
    "seq_no" : 1
  }
}
ankikala$
ankikala$ curl -k -u 'admin:admin' -X POST "https://localhost:9200/remote-index/_doc/?pretty" -H 'Content-Type: application/json' -d'
>   {
>       "user" : "kimchy2",
>       "post_date" : "2009-11-15T14:12:12",
>       "message" : "trying out Elasticsearch5"
>   }
>   '
{
  "_index" : "remote-index",
  "_id" : "XX7pmIYBW4n3o88yuvVb",
  "_version" : 1,
  "result" : "created",
  "_shards" : {
    "total" : 1,
    "successful" : 1,
    "failed" : 0
  },
  "_seq_no" : 1,
  "_primary_term" : 1
}
ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "SYNCING",
  "reason" : "User initiated",
  "leader_alias" : "remote-cluster",
  "leader_index" : "remote-index",
  "follower_index" : "remote-index",
  "syncing_details" : {
    "leader_checkpoint" : 1,
    "follower_checkpoint" : 0,
    "seq_no" : 1
  }
}
ankikala$ curl -k -u 'admin:admin' -X POST "https://localhost:9201/_plugins/_replication/remote-index/_stop?pretty" -H 'Content-Type: application/json' -d '{}'
{
  "acknowledged" : true
}
ankikala$ curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "REPLICATION NOT IN PROGRESS"
}
ankikala$ curl -k -u 'admin:admin' -X POST "https://localhost:9201/remote-index/_doc/?pretty" -H 'Content-Type: application/json' -d'
>   {
>       "user" : "kimchy3",
>       "post_date" : "2009-11-15T14:12:12",
>       "message" : "trying out Elasticsearch5"
>   }
>   '
{
  "_index" : "remote-index",
  "_id" : "63DqmIYBCJZU_R3CVKtW",
  "_version" : 1,
  "result" : "created",
  "_shards" : {
    "total" : 1,
    "successful" : 1,
    "failed" : 0
  },
  "_seq_no" : 2,
  "_primary_term" : 4
}


⚠ gorzdrav.org has degraded performance

In 1b88653, gorzdrav.org (https://gorzdrav.org) experienced degraded performance:

HTTP code: 200
Response time: 10461 ms

Resolved: gorzdrav.org performance has improved in 004144c.


PMID:29878109 RNA level

increased level of flocculin mRNA during vegetative growth
increased level of cell wall organization gene mRNA during vegetative growth

for 2 include synonym with "cell wall remodeling"

increased level of flocculin mRNA during vegetative growth FYPO:0006596
increased level of cell wall organization gene mRNA during vegetative growth FYPO:0006597
edit file: e9eb211633d007d552a03ede3069c10c0e7f3ca0
release: 775c5d9aa382ebbf049ef15dd0952f3da4b372bf


[ja] Translate content/en/docs/reference/glossary/customresourcedefinition.md into Japanese

Note that this issue is for Japanese Speaker
This is a Feature Request
What would you like to be added
Translate content/en/docs/reference/glossary/customresourcedefinition.md into Japanese
Why is this needed
There is no Japanese translation for this page
Comments

File to translate:

https://github.com/kubernetes/website/blob/main/content/en/docs/reference/glossary/customresourcedefinition.md

Original:

https://kubernetes.io/ja/docs/reference/glossary/?all=true#term-CustomResourceDefinition

日本語に翻訳する際は、以下のドキュメントを参考にしてください。

Japanese Localization document: https://kubernetes.io/ja/docs/contribute/localization/

/area localization
/language ja
/good-first-issue

/assign

Find the below link and this what you are expecting after translation.
customresourcedefinition.md

Thank you for your interest in the Japanese localization project!
Metadata keys are typically not translated. Also, note that we have some localization-specific rules; see https://kubernetes.io/ja/docs/contribute/localization/
Please note that these issues are created for Japanese speakers, thank you

Find the below link and this what you are expecting after translation. customresourcedefinition.md

@baswanthd
Don't translate key words. only translate content.
Please follow the procedure as mentioned by @Okabe-Junya

@baswanthd
I would like to raise a PR, if you are not working on it.

/triage accepted

/assign

@Okabe-Junya
PRのレービュウをお願いします。

Thanks @tamilselvan1102,
When opening a PR, please include close #<issue-number> in the description (so the issue will be automatically closed when the PR is merged).
Additionally, there is no need to mention (or /cc) me when you create a PR. There are many active reviewers in the Japanese l10n team. Only mention me if there is no response after a few days.
Thank you

@Okabe-Junya
understood, thank you