Discuss the use of hyperparameters in the quantization_w8a8_int8 script

What is the URL, file, or UI containing proposed doc change
https://github.com/vllm-project/llm-compressor/tree/main/examples/quantization_w8a8_int8
What is the current content or situation in question
Lack of recommendations on hyperparameters to use.
What is the proposed change
Add new content.
Additional context
Let's talk about some issues regarding the values of NUM_CALIBRATION_SAMPLES and smoothing_strength in the script.

First, let's talk about NUM_CALIBRATION_SAMPLES. I found that it is the main factor that determines the quantization time. When this value doubles, the overall quantization time will also double.
The increase in NUM_CALIBRATION_SAMPLES will not lead to a decrease in the accuracy of the final quantized model. In other words, without considering the quantization time and video memory usage, the larger this value, the better. However, this benefit has a limit.
Under the premise that other parameters remain unchanged, NUM_CALIBRATION_SAMPLES increases from 128 to 512, and a significant increase in the score can be seen after quantization. However, the increase from 512 to 1024 will increase the model score less. Basically, I imagine that this trend is similar to a logarithmic curve.
NUM_CALIBRATION_SAMPLES==2048 is a fairly sufficient setting. Under this setting, it takes two hours for a 12~14B model to be quantized on a dual-card 4090, and three hours for a 22B model to be quantized on a triple-card 4090. I think this setting takes into account the pursuit of accuracy of the quantized model and the cost of renting computing equipment.
So all my subsequent discussions will be based on NUM_CALIBRATION_SAMPLES==2048. In fact, all the models I quantized are like this. I don’t have much experience with other values of NUM_CALIBRATION_SAMPLES.

The parameter related to NUM_CALIBRATION_SAMPLES is MAX_SEQUENCE_LENGTH. I always keep the setting of 2048, which may mean that I missed something... Maybe changing this setting according to the maximum context length of the model will have unique findings, or 2048 is sufficient for it. I hope someone with experience will talk about it.

Finally, smoothing_strength is the most complex hyperparameter.
Different smoothing_strengths will greatly change the upper limit of the score that can be achieved by increasing NUM_CALIBRATION_SAMPLES. For example, for a model with an original score of 80, when smoothing_strength=0.3, no matter how NUM_CALIBRATION_SAMPLES is increased, the quantized score is less than 40, which means that the model's ability has been greatly damaged.
I checked the SmoothQuant paper and found a similar hyperparameter discussion in it, but it doesn't match at all. As shown in the screenshot in the paper, the recommended value range of this parameter is 0.4~0.6, while the recommended value in the script is 0.8.

So I didn't get any clues in the end, but I still found some patterns through repeated tests.
First, I adjusted smoothing_strength drastically, such as 0.2, 0.4, 0.6, 0.8, and then observed the output of llm-compressor during the quantization process. One of the values called "error" changed dramatically with smoothing_strength. Specifically, if smoothing_strength is set to a small value, such as 0.2, then llm-compressor will have very low "error" when quantizing the first few layers. On the contrary, when smoothing_strength is set to a large value, such as 0.9, then llm-compressor will have very low "error" when quantizing the last few layers.
That is to say, smoothing_strength specifies a region of the model, so that the layers in that region always get a smaller loss.
https://github.com/vllm-project/llm-compressor/blob/8b145324a9ee861c4e63e958c8285ac151786f8f/src/llmcompressor/modifiers/obcq/utils/sgpt_wrapper.py#L206

Then I started to test the retention/stimulation of the quantified ability when smoothing_strength takes different values.
This is very torturous, because every time I test, I will quantize a 13B model, which means two hours of waiting, and boring dotting on the coordinate system, guessing where the peak is. This makes me feel like an AI that automatically calculates gradient descent.
Hard work always pays off, and I found some rules:
Different models have different preferences. In general, 8B models like smoothing_strength~=0.80, 12~14B models like smoothing_strength~=0.85, and 22B models like smoothing_strength~=0.88.
This is just a general rule, there are exceptions, which will be discussed further later. But before that, I would like to mention some of my conjectures:
The model position specified by smoothing_strength is related to the difference in the properties of different layers of LLM. I remember that a paper found that the top, bottom, and center layers of LLM are different. The top layer is responsible for converting tokens into more complex semantic vectors for the central layer to process, and the bottom layer is responsible for converting logits from the end of the central layer for the decoder to process. Perhaps the position indicated by smoothing_strength is the junction of the central layer and the top layer?
For the abliterated model, if the appropriate smoothing_strength is used, the score will increase significantly, even exceeding the score of the official model that is not abliterated. This may mean that SmoothQuant plays an annealing role after abliterated, bridging the "gap" caused by abliterated in the model.

I designed some rules to verify my conjecture:
For a 13B model with num_hidden_layers==40, such as Nemo. Its preferred smoothing_strength is 0.85, and the quantized model is here:
https://huggingface.co/noneUsername/Mistral-Nemo-Instruct-2407-abliterated-W8A8-Dynamic-Per-Token
1-(6/40)=0.85, does this mean that I specified the 39th, 38th, 37th, 36th, 35th, and 34th layers through smoothing_strength and distinguished them from the 34 layers from 0 to 33?
However, I did not further verify this rule because I found that specifying exact values according to the rule does not always produce the best results. For example, Qwen2.5-Coder-14B-Instruct-abliterated, its num_hidden_layers is 48, and the preferred smoothing_strength is 0.91, but using 1-(4/48)=0.9166666666, that is, smoothing_strength=0.9166666666, the score obtained is lower than the score obtained by using smoothing_strength==0.91.

vllm (pretrained=/root/autodl-tmp/Qwen2.5-Coder-14B-Instruct-abliterated,add_bos_token=true,tensor_parallel_size=2,max_model_len=2048,gpu_memory_utilization=0.80,max_num_seqs=5), gen_kwargs: (None), limit: 250.0, num_fewshot: 5, batch_size: 5
|Tasks|Version|     Filter     |n-shot|  Metric   |   |Value|   |Stderr|
|-----|------:|----------------|-----:|-----------|---|----:|---|-----:|
|gsm8k|      3|flexible-extract|     5|exact_match|↑  |0.872|±  |0.0212|
|     |       |strict-match    |     5|exact_match|↑  |0.868|±  |0.0215|

vllm (pretrained=/root/autodl-tmp/output92,add_bos_token=true,tensor_parallel_size=2,max_model_len=2048,gpu_memory_utilization=0.80,max_num_seqs=5), gen_kwargs: (None), limit: 250.0, num_fewshot: 5, batch_size: 5
|Tasks|Version|     Filter     |n-shot|  Metric   |   |Value|   |Stderr|
|-----|------:|----------------|-----:|-----------|---|----:|---|-----:|
|gsm8k|      3|flexible-extract|     5|exact_match|↑  |0.852|±  |0.0225|
|     |       |strict-match    |     5|exact_match|↑  |0.848|±  |0.0228|

vllm (pretrained=/root/autodl-tmp/output916666666,add_bos_token=true,tensor_parallel_size=2,max_model_len=2048,gpu_memory_utilization=0.80,max_num_seqs=5), gen_kwargs: (None), limit: 250.0, num_fewshot: 5, batch_size: 5
|Tasks|Version|     Filter     |n-shot|  Metric   |   |Value|   |Stderr|
|-----|------:|----------------|-----:|-----------|---|----:|---|-----:|
|gsm8k|      3|flexible-extract|     5|exact_match|↑  |0.844|±  | 0.023|
|     |       |strict-match    |     5|exact_match|↑  |0.844|±  | 0.023|

vllm (pretrained=/root/autodl-tmp/output91,add_bos_token=true,tensor_parallel_size=2,max_model_len=2048,gpu_memory_utilization=0.80,max_num_seqs=5), gen_kwargs: (None), limit: 250.0, num_fewshot: 5, batch_size: 5
|Tasks|Version|     Filter     |n-shot|  Metric   |   |Value|   |Stderr|
|-----|------:|----------------|-----:|-----------|---|----:|---|-----:|
|gsm8k|      3|flexible-extract|     5|exact_match|↑  |0.872|±  |0.0212|
|     |       |strict-match    |     5|exact_match|↑  |0.872|±  |0.0212|

vllm (pretrained=/root/autodl-tmp/output90,add_bos_token=true,tensor_parallel_size=2,max_model_len=2048,gpu_memory_utilization=0.80,max_num_seqs=5), gen_kwargs: (None), limit: 250.0, num_fewshot: 5, batch_size: 5
|Tasks|Version|     Filter     |n-shot|  Metric   |   |Value|   |Stderr|
|-----|------:|----------------|-----:|-----------|---|----:|---|-----:|
|gsm8k|      3|flexible-extract|     5|exact_match|↑  |0.868|±  |0.0215|
|     |       |strict-match    |     5|exact_match|↑  |0.868|±  |0.0215|

vllm (pretrained=/root/autodl-tmp/output88,add_bos_token=true,tensor_parallel_size=2,max_model_len=2048,gpu_memory_utilization=0.80,max_num_seqs=5), gen_kwargs: (None), limit: 250.0, num_fewshot: 5, batch_size: 5
|Tasks|Version|     Filter     |n-shot|  Metric   |   |Value|   |Stderr|
|-----|------:|----------------|-----:|-----------|---|----:|---|-----:|
|gsm8k|      3|flexible-extract|     5|exact_match|↑  |0.852|±  |0.0225|
|     |       |strict-match    |     5|exact_match|↑  |0.852|±  |0.0225|

vllm (pretrained=/root/autodl-tmp/output85,add_bos_token=true,tensor_parallel_size=2,max_model_len=2048,gpu_memory_utilization=0.80,max_num_seqs=5), gen_kwargs: (None), limit: 250.0, num_fewshot: 5, batch_size: 5
|Tasks|Version|     Filter     |n-shot|  Metric   |   |Value|   |Stderr|
|-----|------:|----------------|-----:|-----------|---|----:|---|-----:|
|gsm8k|      3|flexible-extract|     5|exact_match|↑  |0.848|±  |0.0228|
|     |       |strict-match    |     5|exact_match|↑  |0.848|±  |0.0228|

This means that there are some rules for setting smoothing_strength that I am not aware of. Unfortunately, I can only find the best smoothing_strength through multiple attempts. For example, on
Phi-3-medium-4k-instruct, the best value of smoothing_strength is 0.885. Manually testing to three decimal places is really a crazy thing.
https://huggingface.co/noneUsername/Phi-3-medium-4k-instruct-W8A8-Dynamic-Per-Token
vllm (pretrained=/root/autodl-tmp/Phi-3-medium-4k-instruct,add_bos_token=true,tensor_parallel_size=2,max_model_len=2048,gpu_memory_utilization=0.80,max_num_seqs=2,enforce_eager=True), gen_kwargs: (None), limit: 250.0, num_fewshot: 5, batch_size: 1
|Tasks|Version|     Filter     |n-shot|  Metric   |   |Value|   |Stderr|
|-----|------:|----------------|-----:|-----------|---|----:|---|-----:|
|gsm8k|      3|flexible-extract|     5|exact_match|↑  |0.852|±  |0.0225|
|     |       |strict-match    |     5|exact_match|↑  |0.832|±  |0.0237|

vllm (pretrained=/root/autodl-tmp/output1,add_bos_token=true,tensor_parallel_size=2,max_model_len=2048,gpu_memory_utilization=0.80,max_num_seqs=5), gen_kwargs: (None), limit: 250.0, num_fewshot: 5, batch_size: 5
|Tasks|Version|     Filter     |n-shot|  Metric   |   |Value|   |Stderr|
|-----|------:|----------------|-----:|-----------|---|----:|---|-----:|
|gsm8k|      3|flexible-extract|     5|exact_match|↑  |0.876|±  |0.0209|
|     |       |strict-match    |     5|exact_match|↑  |0.844|±  |0.0230|

The above is all my experience with the hyperparameter settings in the W8A8 quantization script. More discussions are welcome. By the way, I quantized them for playing erotic role playing (ERP). The best model at present is noneUsername/Mistral-Nemo-Instruct-2407-abliterated-W8A8-Dynamic-Per-Token.


LRU caching

Notes:
Need to resolve the following caching problems:

default arguments will need to be lists to prevent issues with caching
As the function input for getting documents will be the same, the only function we can really cache is get_all_documents.

Closing for now as this was a straightforward implementation that will require more thought


[FEAT]: Sorting and Folder Mangement

What would you like to see?

Please provide good folder management so that the documents uploaded can be managed. I have to upload 1000s of documents.
Also provide ability to rename the files, in some cases it is taking some other name than the file name. (issue with pdf only) but that is a pain

https://github.com/Mintplex-Labs/anything-llm/issues/554


remove delete button on current capture

do not allow delete button of a capture that is currently capturing......... seriously.

commit, closed

also includes highlighting the currently capturing file


DEA ignores environment variables with bracket characters in them

An environment variable set with a bracket character in its name is currently refused by DEA both at staging and running stages
$ cf set-env hello-world 'SERVICES[ID]_METADATA_LONG_DESCRIPTION' 'a desc'
$ cf restage hello-world
Restaging app hello-world in org [..] / space [..;] as [...]...
-----> Downloaded app package (4.0K)
-----> Downloaded app buildpack cache (4.0K)
[...]
/bin/bash: line 7: export: `SERVICES[ID]_METADATA_LONG_DESCRIPTION=a desc': not a valid identifier
[...]

This does not fail the staging/running though, and requires careful inspection of the output logs to diagnose.
This reproduces with DEA shipped in cf-release v237.
This problem isn't present with diego version recommended with v237
This syntax is quite useful to be able to use environment variables with brackets in them, as this format is natively interpreted by spring boot for loading configuration properties with arrays and maps
Usage of this format may increase with potential native usage suggested in https://github.com/spring-cloud/spring-cloud-cloudfoundry-service-broker/issues/11#issue-153739842

Hi @gberche-orange ,
Unfortunately, this is not an issue with our code - it is simply the way that bash does variable expansion.  Specifically, bash does not allow square brackets in variable names.  Diego allows you to inject variables with square brackets because it does not pass them directly into the shell, but you still cannot read those variables or their values using Diego even though they may appear to have been set.  Diego's backend of garden-linux uses bash, just as we do.
We are closing the issue at this time - there is really nothing we could do to support this.
Thank you,
@ScarletTanager & @jberkhahn , CF RuntimeOG Team

Hi @ScarletTanager and @jberkhahn for your response.
I understand Diego indeed propagates such env vars with bracket characters in them, and apps are able to read them.
Here is a procedure I use to test it with a sample java application
$ git clone https://github.com/s-bortolussi/env-properties-demo.git
$ mvn build
$ cf push demo-env --no-start
$ cf set-env hello-world 'SERVICES[ID]_METADATA_LONG_DESCRIPTION' 'a desc'
$ cf start demo-env
$ cf curl <route>/env

Output of /env endpoint indeed displays the environment var being exported with bracket char in them:
systemEnvironment": {
[...]
    "SERVICES[ID]_METADATA_LONG_DESCRIPTION": "a desc",
[...]

We should also be able to verify the env var was probably set through cf ssh and display output of cat /proc/pid/environ to rule out any java-level transformation of this env var.
As described into http://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names brackets in env name is supported at the OS level (and hence could be supported in containers such as CF apps), but not supported in a standard way by shells such as bash.
I'm not sure how diego currently handles the environment variable setting to apparently not be affected by the bash limitation.
It might be interesting for DEAs though to fail on the rejected environment variable export, rather than simply display the error trace and proceed.
As a final note, I realize such unusual variable names are however not very portable (e.g. when running the same app on a local development box outside CF, bash would reject it), so we'll try to find a more portable environment variable format for our use case (https://github.com/Orange-OpenSource/static-creds-broker/issues/27 )

Hi @gberche-orange ,
An issue for us is that we cannot support something which is language-specific - for example, you could probably also read this variable in a golang app using Diego as well.  But whether or not the OS supports it (the OS does not do the variable interpolation, that's normally done by the shell, in our case /bin/bash, AFAIK), the shell does not, and that means that, even were we to figure out a way to set the variable, any app which relied on reading the variable via the shell would not be able to access it.  We tried your example of doing a cf ssh and then checking that we could read the variable, and this failed, since it relies on the shell's ability to do variable interpolation and expansion.  So as you note, it's as much about portability as anything.  I am anything but a Spring expert, but I'm pretty sure you'll be able to find something more portable fairly quickly.
We do appreciate your input, and we do wish we had a "happier" answer.
Best,
@ScarletTanager, CF RuntimeOG team


Seed not working for AtariEnv

First of all: Thank you for writing this nice wrapper! :)
I wanted to use the AtariEnv for evaluation and I realized that the seed method is not working.
I am not sure whether this is a bug or should be that way
from d4rl_atari.envs import AtariEnv
import numpy as np

env0 = AtariEnv("Pong", stack=True)
env0.seed(0)

env1 = AtariEnv("Pong", stack=True)
env1.seed(0)

env0.reset()
env1.reset()

for i in range(10):
    a = env0.action_space.sample()
    s0, *_ = env0.step(a)
    s1, *_ = env1.step(a)

    np.equal(np.array(s0), np.array(s1)).all()

The following code works:
from d4rl_atari.envs import AtariEnv
import numpy as np

env0 = AtariEnv("Pong", stack=True)
env0._env.seed(0)

env1 = AtariEnv("Pong", stack=True)
env1._env.seed(0)

env0.reset()
env1.reset()

for i in range(10):
    a = env0.action_space.sample()
    s0, *_ = env0.step(a)
    s1, *_ = env1.step(a)

    np.equal(np.array(s0), np.array(s1)).all()

@sebffischer Thanks for reporting this issue! Let me check.

I've solved this issue now at this commit https://github.com/takuseno/d4rl-atari/commit/8d1d3ff621d822a65adc2227441d7c220324f445 .


Need to add notes section.

Currently, our to-do app lacks a notes feature, which limits users' ability to add extra details or context to their tasks. Adding a notes functionality will enhance user experience and provide a more comprehensive task management solution.
Steps to reproduce the behavior:
1.Integrate a notes input field.
2.Enable users to add, edit, and delete notes.

okay, would you like to work on this issue?

Yes, I want to solve this problem. and I can add edit and more buttons to To-do section.

you can work on this issue. for the todo-edit button please create a separate issue

okay.


UX meeting agenda 10 August, 2016

Agenda:

Allow users to chose squiggly lines or boxes for errors and warnings. #9209

Refactor the view menu: https://github.com/Microsoft/vscode/issues/9924
Showing errors in the editor: https://github.com/Microsoft/vscode/issues/9062
Distinguishing two files with the same name: https://github.com/Microsoft/vscode/issues/8499

More discussion on the horizontal panel: https://github.com/Microsoft/vscode/issues/9659

Sorry to hijack the order of priority but I think horizontal editor layout should be # 1 because it is planned as item in the August iteration plan (https://github.com/Microsoft/vscode/issues/1749)

OK, lets spend some time discussing how we will know when we are done and how we will proceed with that item during August.

Also on the plan with UX impact: Extensible Icon support in the explorer (https://github.com/Microsoft/vscode/issues/10294)


I dont get it

I followed the instructions but all it does is boot the OS I chose.  Etcher already does that.  How do I actually use this to flash the EMMC?

I guess if you browse for an image it doesnt work right?  How do I flash the gnome ubuntu images to emmc ?  Why isnt ubuntu more of a focus ?

Hi. Can you be  bit more specific of what you mean by " all it does is boot the OS I chose" ? What difficulties did you encounter flashing emmc?


ECIS post composition / atritubre Text / CodedText

EHRbase version: 21

When the attribute of the template is defined like Text and Code Text  when the instance informs the Text value the server returns bad Requests
Sample if informs Text
..../attribute":"Value Text" --> Bad requests, Attribute value of class TERMINOLOGY_ID does not match existence 1..1, ....
Sample if informs coded Text  returns 200 and create the composition
..../attribute|code":"Code",
..../attribute|terminology":"1.22.2332.22",
..../attribute|value":"Sample Value",

@xarranzm
please provide the an opt file as well as a flat example.

I send the opt, a sample with problems and a sample without problems. In the tree cases the attribute are definend as Text and Coded_Text.
flat_CCCE_ok.txt
flat_CCCE_ko.txt
OPT.zip
The differences between the examples are:
1)
"clinical_course/meap/soap_headings/assessment_a/clinical_synopsis/synopsis": "Avaluació -TEXTO LIBRE",
"clinical_course/meap/soap_headings/assessment_a/clinical_synopsis/synopsis|code": "-",
"clinical_course/meap/soap_headings/assessment_a/clinical_synopsis/synopsis|terminology": "-",
"clinical_course/meap/soap_headings/assessment_a/clinical_synopsis/synopsis|value": "Avaluació -TEXTO LIBRE",

"clinical_course/meap/clinical_synopsis/synopsis": "Altres -TEXTO LIBRE",
"clinical_course/meap/clinical_synopsis/synopsis|code": "-",
"clinical_course/meap/clinical_synopsis/synopsis|terminology": "-",
"clinical_course/meap/clinical_synopsis/synopsis|value": "Altres -TEXTO LIBRE",

"clinical_course/meap/service_request/current_activity/service_name": "Derivacions -TEXTO LIBRE",
"clinical_course/meap/service_request/current_activity/service_name|code": "Derivacions -TEXTO LIBRE",
"clinical_course/meap/service_request/current_activity/service_name|terminology": "Derivacions -TEXTO LIBRE",
"clinical_course/meap/service_request/current_activity/service_name|value": "Derivacions -TEXTO LIBRE",

You can save it with
clinical_course/meap/soap_headings/assessment_a/clinical_synopsis/synopsis|other": "Avaluació -TEXTO LIBRE"
note the other
this is because the template contains explizite choice between DV_TEXT and DV_CODED_TEXT
 <node_id>at0002</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
            <rm_attribute_name>value</rm_attribute_name>
            <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
            </existence>
            <match_negated>false</match_negated>
            <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_TEXT</rm_type_name>
                <occurrences>
                    <lower_included>true</lower_included>
                    <upper_included>true</upper_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>false</upper_unbounded>
                    <lower>1</lower>
                    <upper>1</upper>
                </occurrences>
                <node_id/>
            </children>
            <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_CODED_TEXT</rm_type_name>
                <occurrences>
                    <lower_included>true</lower_included>
                    <upper_included>true</upper_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>false</upper_unbounded>
                    <lower>1</lower>
                    <upper>1</upper>
                </occurrences>
                <node_id/>
            </children>
        </attributes>

instead of a impliziert one
 <node_id>at0002</node_id>
        <attributes xsi:type="C_SINGLE_ATTRIBUTE">
            <rm_attribute_name>value</rm_attribute_name>
            <existence>
                <lower_included>true</lower_included>
                <upper_included>true</upper_included>
                <lower_unbounded>false</lower_unbounded>
                <upper_unbounded>false</upper_unbounded>
                <lower>0</lower>
                <upper>1</upper>
            </existence>
            <match_negated>false</match_negated>
            <children xsi:type="C_COMPLEX_OBJECT">
                <rm_type_name>DV_TEXT</rm_type_name>
                <occurrences>
                    <lower_included>true</lower_included>
                    <upper_included>true</upper_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>false</upper_unbounded>
                    <lower>1</lower>
                    <upper>1</upper>
                </occurrences>
                <node_id/>
            </children>
        </attributes>

it is interpreted by the webtemplate (get /ehrbase/rest/ecis/v1/template/Clinical course), on which flat is based
as a DV_CODED_TEXT with a other input
  {
                                                    "id": "synopsis",
                                                    "name": "Synopsis",
                                                    "localizedName": "Synopsis",
                                                    "rmType": "DV_CODED_TEXT",
                                                    "min": 1,
                                                    "max": -1,
                                                    "localizedNames": {
                                                        "en": "Synopsis"
                                                    },
                                                    "localizedDescriptions": {
                                                        "en": "The summary, assessment, conclusions or evaluation of the clinical findings."
                                                    },
                                                    "aqlPath": "/content[openEHR-EHR-SECTION.adhoc.v1 and name/value='MEAP']/items[openEHR-EHR-SECTION.soap.v0]/items[at0003]/items[openEHR-EHR-EVALUATION.clinical_synopsis.v1]/data[at0001]/items[at0002]/value",
                                                    "inputs": [
                                                        {
                                                            "suffix": "value",
                                                            "type": "TEXT"
                                                        },
                                                        {
                                                            "suffix": "code",
                                                            "type": "TEXT",
                                                            "listOpen": true
                                                        },
                                                        {
                                                            "suffix": "other",
                                                            "type": "TEXT"
                                                        }
                                                    ]
                                                }

I have to think about /research the spec here. It properly should accept it with out the  other as DV_TEXT.
However in  your cases want any DV_TEXT or DV_CODED_TEXT.
Since DV_CODED_TEXT is also a DV_TEXT you do not need to set expliziert in the template (just remove the DV_CODED_TEXT node ) and then
clinical_course/meap/clinical_synopsis/synopsis": "Altres -TEXTO LIBRE"
would work

Thank you for your support


The certificate-bound access token generation flow to the APIM resident key manager.

Description
Requesting the addition of the certificate-bound access token generation functionality to the APIM-4.2.0 resident key manager, as the current version only supports certificate-bound access token validation in APIM-4.2.0.
Affected Component
APIM
Version
4.2.0

Public fix: https://github.com/wso2/carbon-apimgt/pull/12217

Master fix added using

https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/2355
https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/2418
https://github.com/wso2/carbon-apimgt/pull/12217


Incomplete link: Wikipedia link for vi is wrong/incomplete in REAME.md

Under the What is Vim? section in README.md, there is a link to the Wikipedia page for Vi, but it leads to the common references page for Vi on Wikipedia.
Expected: It should lead to the vi (text editor) page.

thanks, I am fixing it now.


Resistance to pentest? 33C3

Hello,
Thanks for sharing this promising tool.
How resistant is it against attacks exposed at 33C3 Gone in 60 seconds?
Gone in 60 Milliseconds, Intrusion and Exfiltration in Server-less Architectures
https://media.ccc.de/v/33c3-7865-gone_in_60_milliseconds
Things like shared temp in lambda, AWS IAM rules, exfiltration through meta
code still not released on https://github.com/Miserlou/Mackenzie/

Hi @juju4
The talk is about exploitation/exfiltration after you've found a vulnerability in a Lambda application. E.g. what to do after you've achieved remote code execution. As best we know, our IAM roles follow least privilege, we don't leave data behind in /tmp, and our code is pretty secure. If you find a vulnerability, or overly permissive IAM roles, let us know and we'll be happy to fix. Thanks!


CL110 False Humidity Reading

Describe the bug
The humidity for the CL110 Sensor is missing the factor x100. I'm not sure if this is a problem with HomeAssistant.
The displayed humidity in HA is "0,5512 %" an in PanelServer "55.12 %".
Versions

HomeAssistant: 2024.6.3
Integration: v0.5.0

Logs

[ ] Attached logs to this issue

Fixed in v0.5.1, please verify.

Perfect. Thanks 👍


Using howdy only for gdm

Hello there,
Can someone append to the https://github.com/boltgolt/howdy/wiki/Only-using-howdy-for-specific-authentication-types article how would gdm-auth would work?
I have gotten e.g. the https://askubuntu.com/a/1304887/645458 working, but gdm seems to have a lot of files 😕
ua@h /etc/pam.d$ ls -lah gdm-*
-rw-r--r-- 1 root root 1,2K Νοε  10  2020 gdm-autologin
-rw-r--r-- 1 root root 1,4K Νοε  10  2020 gdm-fingerprint
-rw-r--r-- 1 root root  383 Νοε  10  2020 gdm-launch-environment
-rw-r--r-- 1 root root 1,3K Νοε  10  2020 gdm-password
ua@h /etc/pam.d$

Feel free to add it, the wiki can be edited by anyone.

I know 😅
My question was: I don't know/understand how does gdm work in this case.
I was hoping someone who have done it could add his/her walkthrough

You need to add the module to the gdm-password file with the options you want (auth  sufficient  pam_howdy.so for example if you want to authenticate only with it it succeeds).

You have to add it in the first lines, but make sure to test with another service that you don't use (maybe su) before to not lock you out.


Admission policies + some extra stats for cachebench

This is the first part of what was formerly the background data movement + tier admission PR

This change is

I rebased the PR, the outstanding issues from the review to address are:
cachelib/allocator/MemoryTierCacheConfig.h line 72 at r1 (raw file):
}
// TODO: move it to MMContainer config

Looks like we need to address this TODO comment. Not sure why it should be per tier.
cachelib/allocator/memory/MemoryAllocator.h line 652 at r1 (raw file):
}
// TODO:
what is it?
cachelib/allocator/memory/MemoryAllocatorStats.h line 58 at r1 (raw file):
}
constexpr size_t getTotalMemory() const noexcept {
should it be renamed to getTotalAllocMemory?
cachelib/allocator/memory/MemoryPool.h line 311 at r1 (raw file):
void setNumSlabsAdvised(uint64_t value) { curSlabsAdvised_ = value; }
// TODO:
Again, we broken incapsulation. Not sure that we have to merge some hacks to develop branch.


Users can choose one of the cards which is then their card for the next 24 hours

still open?
does it work in dev?


optionally return non-zero error code when function run sees error

We want to support returning a non-zero error code anytime a module sees an error during a run. Unfortunately, since older versions of the Shopify CLI auto-update, we can't do this my default and make a breaking change. Instead, i opted to implement this change behind an option --non-zero-exit-code-for-module-errors. In the Shopify CLI, we can update new versions to start calling this flag.
When the flag isn't provided, nothing changes. When it is provided, we return exit code 1. Heres an example output with the flag:
 ✘  ~/src/github.com/Shopify/function-runner   js.return-error-when-module-errors  function-runner -f 'panic-configurable-fuel.wasm' -i 'input.json' -e run --non-zero-exit-code-for-module-errors
            Input
{ manually truncated }
            Logs

thread '<unnamed>' panicked at src/run.rs:24:5:
oh no - something terrible has happened
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error while executing at wasm backtrace:
    0: 0x17c4e - <unknown>!<wasm function 366>
    1: 0x84a9 - <unknown>!<wasm function 14>
    2: 0x13f68 - <unknown>!<wasm function 108>
    3: 0x17bf8 - <unknown>!<wasm function 355>
    4: 0x171b0 - <unknown>!<wasm function 243>
    5: 0x17182 - <unknown>!<wasm function 242>
    6: 0x57b8 - <unknown>!<wasm function 9>

        Invalid Output

         JSON Error

EOF while parsing a value at line 1 column 0

        Resource Limits

Input Size: 125.00KB
Output Size: 19.53KB
Instructions: 11M

     Benchmark Results

Name: panic-configurable-fuel.wasm
Linear Memory Usage: 1088KB
Instructions: 150.943K
Input Size: 4.98KB
Output Size: 0B
Module Size: 112KB

Error: The Function execution failed. Review the logs for more information.
 ✘  ~/src/github.com/Shopify/function-runner   js.return-error-when-module-errors  echo $?
1

I think we stopped auto-updating in this PR, which was released in the 3.65.0 version on August 2. I wonder if that's enough time that it would be okay to ship this PR as the default behaviour.
@nickwesselman Do you have an opinion on this?


Android: Migrate deprecated support library to AndroidX

I had time and I was bored, and I saw that support library is deprecated so I decided to migrate godot to androidX (using built in Android Studio migrator, and testing that the android editor still works afterword)

Thanks!
Can you fix the formatting issues reported by travis.
Can the commit be cherry-picked onto the 3.2 branch? If not, can you provide a backport PR for the 3.2 branch.

Of course! It would be done sometime today

@m4gr3d https://github.com/godotengine/godot/pull/37929 3.2 backport

@m4gr3d anything else?

@akien-mga anything else?

@m4gr3d Does this look good to you now?

@thebestnom @akien-mga Sorry for the delay. The code looks good, I just need to validate the androidx migration doesn't introduce build errors with existing projects and samples.
I should be done validating by tomorrow.

I should be done validating by tomorrow.

Bump :)

I should be done validating by tomorrow.

Bump :)

Totally dropped off my radar, on it now :)

Thanks!


Calling .AsStream() on a pipe that is an IPC stream adds another adapter

In the case where a Pipe is actually an IPC Stream, the fact that we see it as a Pipe already suggests that there's a stream-to-pipe adapter on it. Sticking on another adapter means we're handing back a stream->pipe->stream object. The underlying stream should be unwrapped when the pipe is just an adapter to just return the original stream instead of stacking adapters.

I can't unwrap a Pipe to be a stream because in the meantime the Pipe has eagerly started reading from the stream. Unwrapping the stream would abandon the bytes that the pipe already read.
But I did enable unwrapping a stream that was covering up a pipe.


Add file log handler

Include file handler (probably the rotating version) in logging: https://github.com/nautls/ergomatic/blob/f5739b513273f830b911a4800f3981eabed6e83e/src/log.ts#L13
Will make it easier for users to give us logs in case of errors, etc
Using RotatingFileHandler requires calling setup on the handler, which means we have to move all logger creation in async methods, currently loggers are created in the constructor

FileHandler added in #12
RotatingFileHandler would require a bigger refactor, put it off until later
Related issue: https://github.com/denoland/deno_std/issues/3538 describing why it would require a refactor

Actually, it looks like RotatingFileHandler being async might be a deno bug: https://github.com/denoland/deno_std/issues/3538#issuecomment-1676942783


Update browser-resolve dependency.

The underlying resolve library has a bug in versions <1.1.7 which means it doesn't work on Windows when using relative paths (like .). This breaks the npm.globals config on Windows. I can confirm that updating this dependency does fix it.

:+1:
I was going to do this myself after https://github.com/defunctzombie/node-browser-resolve/issues/78. Thanks!
@paulmillr merge this one


Add SSL Certificate

Add an SSL Certificate so that we can use HTTPS requests. Use Certbot to do so.

Followed the instructions at https://certbot.eff.org/instructions?ws=nginx&os=ubuntufocal
Was super easy this time around since I am using Nginx


[BUG] Unable to download model weights from Huggingface

Hello,
I attempted to load Cambrian model weights from huggingface.
I used following commands to do so:
from transformers import AutoModelForCausalLM
model = AutoModelForCausalLM.from_pretrained("nyu-visionx/cambrian-8b")
However, I received error message saying:
ValueError: The checkpoint you are trying to load has model type cambrian_llama but Transformers does not recognize this architecture. This could be because of an issue with the checkpoint, or because your version of Transformers is out of date.
I tried to run the codes with different transformers version but I always had this error message.

Our model is not integrated into transformers. You have to install our repo to load and use our models (see inference.py).

Got it. Thanks.


luci-base: Show multiple upstream interface

Several devices have multiple upstream interfaces, for example a fixed
and a mobile broadband connection. Currently, only one upstream
interface is shown per address family in Luci. So in my example, one of
the interfaces would not appear on the Status-page.
This PR introduces support for showing multiple upstream interfaces on
the Status-page. The code is not very complicated. get_status_by_route()
has been extended to return a list of all routes, and
get_wannet()/get_wan6net() now returns all upstream interfaces.
I could not find any other (active) users of these three functions than
calls triggered from the Status-page, so changing the default behavior
should be fine. get_wandev()/get_wan6dev() called get_status_by_route(),
but I could not find any place where those functions were called. I
removed the dev-functions instead of keeping the old
get_status_by_route().
On the status page, the wan/wan6-variables have been replaced with
arrays. When populating the html, we now iterate through these arrays
and create one element for each interface.
I have tested the code with different interface types, v4, v6, as well as
disconnecting and connecting interfaces. The status is updated and the
correct interfaces (or sometimes none at all) are shown.
Signed-off-by: Kristian Evensen<EMAIL_ADDRESS>

Can you please provide a screenshot displaying the changed behaviour?

for me, the current is like this

@lucize - thanks :) Will merge after the code issues are addressed

@jow- Thanks for the comments. I (should have) addressed all of them now. I am not sure if you would like me to rebase + force push, or just push. I chose the latter and then I can merge the commits if you want that instead.

@kristrev - thanks for integrating the requested changes. Yes please squash the two commits and force-push.

Fixed, commits are squashed + pushed.

Perfect - thanks!


WIP: DBZ-1234 Remove deprecated features and configuration options

https://issues.jboss.org/browse/DBZ-1234

@Naros, as this is labelled with "WIP", what other things are you planning to add? Could you also rebase this to the current master? Thanks!

@jpechane, here's one more thing I'm considering to drop: the "adaptive_time_microseconds" value for the PG connector's "time.precision.mode"; this was added to keep compatibility with earlier behaviors at some point, but it's prone to value loss for large TIME values. So I don't think there's actual value in having it and it wouldn't be there hadn't this (arguably, incorrectly) existed before. WDYT?

@gunnarmorling Agrre. I've went through the docs and it seems to be the only one not completed.

No worries :) Seems we're in agreement of its removal then.
On a related note, I've filed https://github.com/debezium/debezium/pull/884 and the a corresponding doc update for removing a deprecated SMT option.

as this is labelled with "WIP", what other things are you planning to add? Could you also rebase this to the current master? Thanks!

@gunnarmorling I had marked this WIP as I knew the SMT option was still pending, but it looks like you took care of that as a part of PR #884, so at this point all which remains is what @jpechane mentioned which I'll add.

Excellent, thanks!

@jpechane @gunnarmorling Let me know if there is anything I missed or that you'd like to see changed with how I handled the adaptive time.precision.mode commit.

how I handled the adaptive time.precision.mode commit.

I think that's fine. I've just pushed one minor commit to get the enum value via its parse() method as this also deals with trimming the value.

@Naros, could you also prepare the wording for the migration notes and add it as a comment to the JIRA issue (I've already done it for the SMT option). Thanks!

Applied. Thanks a lot, @Naros!


Started http server

Hi Prisma Team! My Prisma Client just crashed. This is the report:
Versions

Name
Version

Node
v14.3.0

OS
darwin

Prisma
2.3.0

Description
Started http server

Logs
m        accessType,
  prisma-client         count(*) as count,
  prisma-client         sum(charge) as charge
  prisma-client       from RawUser
  prisma-client       left join AdRawUser on RawUser.id = AdRawUser.rawUserById
  prisma-client       where RawUser.createdAt >= "2020-07-22T20:50:59.419Z" && RawUser.createdAt <= "2020-07-22T21:50:59.419Z"
  prisma-client       group by storeById, accessType
  prisma-client     )  +0ms
  plusX Execution permissions of /Users/hj.kang/Documents/GitProject/danbi-api/node_modules/.prisma/client/query-engine-darwin are fine  +174ms
  prisma-client Client Version 2.3.0  +262ms
  prisma-client Engine Version e11114fa1ea826f9e7b4fa1ced34e78892fe8e0e  +0ms
  plusX Execution permissions of /Users/hj.kang/Documents/GitProject/danbi-api/node_modules/.prisma/client/query-engine-darwin are fine  +2s
  prisma-client Prisma Client call:  +2s
  prisma-client prisma.queryRaw(
  prisma-client       select
  prisma-client         storeById,
  prisma-client         accessType,
  prisma-client         count(*) as count,
  prisma-client         sum(charge) as charge
  prisma-client       from RawUser
  prisma-client       left join AdRawUser on RawUser.id = AdRawUser.rawUserById
  prisma-client       where RawUser.createdAt >= "2020-07-22T21:50:59.419Z" && RawUser.createdAt <= "2020-07-22T22:50:59.419Z"
  prisma-client       group by storeById, accessType
  prisma-client     )  +0ms
  plusX Execution permissions of /Users/hj.kang/Documents/GitProject/danbi-api/node_modules/.prisma/client/query-engine-darwin are fine  +233ms
  prisma-client Client Version 2.3.0  +319ms
  prisma-client Engine Version e11114fa1ea826f9e7b4fa1ced34e78892fe8e0e  +0ms
  plusX Execution permissions of /Users/hj.kang/Documents/GitProject/danbi-api/node_modules/.prisma/client/query-engine-darwin are fine  +2s
  prisma-client Prisma Client call:  +2s
  prisma-client prisma.queryRaw(
  prisma-client       select
  prisma-client         storeById,
  prisma-client         accessType,
  prisma-client         count(*) as count,
  prisma-client         sum(charge) as charge
  prisma-client       from RawUser
  prisma-client       left join AdRawUser on RawUser.id = AdRawUser.rawUserById
  prisma-client       where RawUser.createdAt >= "2020-07-22T22:50:59.419Z" && RawUser.createdAt <= "2020-07-22T23:50:59.419Z"
  prisma-client       group by storeById, accessType
  prisma-client     )  +0ms
  plusX Execution permissions of /Users/hj.kang/Documents/GitProject/danbi-api/node_modules/.prisma/client/query-engine-darwin are fine  +190ms
  prisma-client Client Version 2.3.0  +318ms
  prisma-client Engine Version e11114fa1ea826f9e7b4fa1ced34e78892fe8e0e  +0ms
  plusX Execution permissions of /Users/hj.kang/Documents/GitProject/danbi-api/node_modules/.prisma/client/query-engine-darwin are fine  +2s
  prisma-client Prisma Client call:  +2s
  prisma-client prisma.queryRaw(
  prisma-client       select
  prisma-client         storeById,
  prisma-client         accessType,
  prisma-client         count(*) as count,
  prisma-client         sum(charge) as charge
  prisma-client       from RawUser
  prisma-client       left join AdRawUser on RawUser.id = AdRawUser.rawUserById
  prisma-client       where RawUser.createdAt >= "2020-07-22T23:50:59.419Z" && RawUser.createdAt <= "2020-07-23T00:50:59.419Z"
  prisma-client       group by storeById, accessType
  prisma-client     )  +0ms
  plusX Execution permissions of /Users/hj.kang/Documents/GitProject/danbi-api/node_modules/.prisma/client/query-engine-darwin are fine  +162ms
  prisma-client Client Version 2.3.0  +249ms
  prisma-client Engine Version e11114fa1ea826f9e7b4fa1ced34e78892fe8e0e  +0ms
  plusX Execution permissions of /Users/hj.kang/Documents/GitProject/danbi-api/node_modules/.prisma/client/query-engine-darwin are fine  +2s
  prisma-client Prisma Client call:  +2s
  prisma-client prisma.queryRaw(
  prisma-client       select
  prisma-client         storeById,
  prisma-client         accessType,
  prisma-client         count(*) as count,
  prisma-client         sum(charge) as charge
  prisma-client       from RawUser
  prisma-client       left join AdRawUser on RawUser.id = AdRawUser.rawUserById
  prisma-client       where RawUser.createdAt >= "2020-07-23T00:50:59.419Z" && RawUser.createdAt <= "2020-07-23T01:50:59.419Z"
  prisma-client       group by storeById, accessType
  prisma-client     )  +0ms
  plusX Execution permissions of /Users/hj.kang/Documents/GitProject/danbi-api/node_modules/.prisma/client/query-engine-darwin are fine  +202ms
  prisma-client Client Version 2.3.0  +291ms
  prisma-client Engine Version e11114fa1ea826f9e7b4fa1ced34e78892fe8e0e  +0ms
  plusX Execution permissions of /Users/hj.kang/Documents/GitProject/danbi-api/node_modules/.prisma/client/query-engine-darwin are fine  +2s
  prisma-client Prisma Client call:  +2s
  prisma-client prisma.queryRaw(
  prisma-client       select
  prisma-client         storeById,
  prisma-client         accessType,
  prisma-client         count(*) as count,
  prisma-client         sum(charge) as charge
  prisma-client       from RawUser
  prisma-client       left join AdRawUser on RawUser.id = AdRawUser.rawUserById
  prisma-client       where RawUser.createdAt >= "2020-07-23T01:50:59.419Z" && RawUser.createdAt <= "2020-07-23T02:50:59.419Z"
  prisma-client       group by storeById, accessType
  prisma-client     )  +0ms
  plusX Execution permissions of /Users/hj.kang/Documents/GitProject/danbi-api/node_modules/.prisma/client/query-engine-darwin are fine  +224ms

@hjkang-danbi Thanks, can you please share your schema and the Prisma client query that fails? A minimal reproduction would help up triage this quickly.

Closing due to inactivity


Feature request: multizip_eq (and izip_eq!)

Seems the only reason this doesn't exist is that nobody has done it yet. Should I make a PR?

zip_eq kills performance pretty well, so I've been uncomfortable with it. We could change it around to use exact size iterators and check up front, but that also makes them less useful, doesn't it?  Any thoughts on this?

I wouldn't really have expected it to work with non-ExactSizeIterators. For me it's simply a nice additional assertion (which has already caught one bug for me where I accidentally refered to a wrong slice).

Aha. For example filtering will make an iterator non-ESI and I can imagine that's exactly when zip_eq is needed, if equal length is the assumption.
Maybe we can give update the "contract" of it to allow it to panic up front, for exact size iterators, but otherwise defer to late checking? That would still kill performance until specialization is available, though.


Bluebird PromisifyAll throws error

Hi,
I was trying to promisify jwt-simple api by using bluebirds Promise.promisifyAll method. It does promisify it but at runtime bluebird throws an error as follows:
Possibly unhandled Error: Algorithm not supported
at Object.jwt_encode [as encode] (/Users/nosh/repos/dineawayserver/node_modules/jwt-simple/lib/jwt.js:114:11)
at Object.encodeAsync (eval at makeNodePromisifiedEval (/Users/nosh/repos/dineawayserver/node_modules/sequelize/node_modules/bluebird/js/main/promisify.js:201:12), :12:22)
From previous event:
at Object.encodeAsync (eval at makeNodePromisifiedEval (/Users/nosh/repos/dineawayserver/node_modules/sequelize/node_modules/bluebird/js/main/promisify.js:201:12), :7:21)
could this be that the library does not support async? or am I doing something wrong.

The API is not async at all, there is no reason to promisify it. You can just call it:
var jwt = require('jwt-simple');
var resuilt = jwt.encode(payload, secret);
console.log(result);

@petkaantonov That's right. :+1:


Is sqlite-vec supported?

Pretty much the question: is there a way to support sqlite-vec?
Thanks in advance,
Nuno

Since sqlite-wasm does not support dynamically loading extensions, you will have to recompile sqlite-wasm in order to add the sqlite-vec extension to it. They have documentation about how to do that here.
There was also a demo that Ben Holmes did where he implemented vector search with SQLocal by just storing the vectors as BLOBs, so you can check out that video and see if it might fit your use case.


No longer require the /data suffix in the path for RandomSecrets usin…

…g kvV2, improve the spec documentation for paths, and fixes #154

I saw you changed several comments, but the corresponding crds have not been regenarated.

I saw you changed several comments, but the corresponding crds have not been regenarated.

The comment should be there in the CRDs... what is missing?


fix(swc): fix incorrect types path in package.json

In @swc/core package, types path in package.json is ./lib/index.d.ts, but it should be ./index.d.ts

 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.


Uncaught TypeError: CookieConsent.init is not a function

Hi,
with using this demo and the latest Beta version (3.0.0-rc.7) I get an error as in the topic. Can it be fixed?
Regards!

Hi @gyurmey2,
there are 2 major versions of cookieconsent — v2 and v3 — and they are substantially different. If you want to check out a demo configuration for v3, please refer to the v3.0-beta branch.
You could also check out the live (work in progress) playground for v3.

@orestbida thank you very much.
I made changes, but now I get CookieConsent is not defined error, but only when I try to compile. There is no problem with v2.8.8.

Mhm, there's a warning saying that import is not available, probably related to jsbin. I'd recommend to use Stackblitz for a live demo.
There are a few live demos that you can inspec on Stackblitz and CodeSandbox

Yes, I know, It was just a sample code snippet for inspection. The problem, however, remains.

I cannot tell what the issue is unless you provide a full demo with the problem (a react, laravel, vue, vite ... app); There is nothing wrong with the jsbin snippet itself.

Thank you. Examples below:
Without import.
With import.

Found the issue!
If you want to use import in a script, you must specify type="module:
<script type="module" src="index.js"></script>

In the import statement, you can either import the whole plugin:
import * as CookieConsent from 'vanilla-cookieconsent';

or some specific API methods only:
import { run } from 'vanilla-cookieconsent';

run({...});

you must use the same name as the one you specified in the import, in this case it's CookieConsent:
import * as CookieConsent from 'vanilla-cookieconsent';

CookieConsent.run({...});

It works! Thanks a lot.

Hello @orestbida ,
I updated the library with v3 (especially for lenis) and the import is no longer correct.
The problem now is that I end up with a JS error: Uncaught (in promise) TypeError: can't convert undefined to object
Here is my old code:
`import * as CookieConsent from 'vanilla-cookieconsent';
export const cookie = {
init: function () {
//const CookieConsent = initCookieConsent();
CookieConsent.run({
current_lang: 'fr',
autoclear_cookies: true,
page_scripts: true,
languages: {
        },
        gui_options: {

        },
        onModalReady: ({modalName, modal}) => {
            if(modalName === 'preferencesModal'){
                console.log('hello')
                $('#s-bl').attr('data-lenis-prevent', '')
                //modal.querySelector('.s-bl').setAttribute('data-lenis-prevent', '');
            }
        }
    });

    return CookieConsent;

},

}
export default cookie;`
I don't see where the problem is, can you help me ? Thanks in advance, nicolas

@dngraphisme,
you need to provide a valid config. object with at least the following 2 properties: language, categories. This is mentioned in the Getting Started page.


Fixing time comparison to look for past deltas

CATEGORY
Choose one

[x] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
On a line chart using the advanced analytics with time shift 1 year incorrectly evaluates to 366 days as the delta and as a result shows incorrect data. parse_human_timedelta looks forward in time when evaluating the human timedelta to number of days, but it's used in time compare to look back in time and compare current points to a previous delta. Around leap years the number of days 1 year ahead is not the same as 1 year behind. More details of the issue are in #7311
I'm keeping parse_human_timedelta the way it is and adding another function to specify that we want the past delta (so -1 year if we are given 1 year), and returning a positive timedelta as we were previously. I looked into just making parse_human_timedelta return a negative delta, but it makes the logic below look a bit more confusing with delta =+ parse_human_timedelta(...) when it would actually be subtracting the negative delta.
NOTE: This will change the data for time shift (1 year, 1 month,...) but it will be accurate.
TEST PLAN

ADDITIONAL INFORMATION

[x] Has associated issue: fixes #7311
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS

Codecov Report

Merging #7616 into master will increase coverage by <.01%.
The diff coverage is 87.5%.

@@            Coverage Diff             @@
##           master    #7616      +/-   ##
==========================================
+ Coverage   65.24%   65.24%   +<.01%
==========================================
  Files         435      435
  Lines       21503    21505       +2
  Branches     2379     2379
==========================================
+ Hits        14030    14032       +2
  Misses       7353     7353
  Partials      120      120

Impacted Files
Coverage Δ

superset/utils/core.py
88.25% <100%> (+0.04%)
:arrow_up:

superset/viz.py
71.93% <50%> (ø)
: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 fc3b043...af1ddc1. Read the comment docs.

ping @john-bodley


Example is only a cmd prompt

The example is merely a command prompt, not an actual example of this cmdlet.

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

ID: 18696f54-bc1e-9216-1dcb-5eb8ff24278d
Version Independent ID: ca716a63-5604-be52-af85-30c84f3545ae
Content: Get-CMDistributionStatus (ConfigurationManager)
Content Source: sccm-ps/ConfigurationManager/Get-CMDistributionStatus.md
Product: configuration-manager
Technology: configmgr-other
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

The PowerShell docs are auto-generated from the ConfigMgr module. We have limited resources to maintain the over 1100 cmdlet articles for this module (along with the 3200 articles in ConfigMgr core docs). We rely on community support from members like you to assist. If you have a sample example to share for this cmdlet, you can either share that via this feedback system, or submit an edit to the article to contribute your example. For more information, see How to use the Configuration Manager docs.

Thanks to @baardhermansen for submitting an edit to the article to add this example! It should go live with daily publishing later this afternoon (Pacific).


[Bug]: Parameter renaming is not working for named arguments

Description
$title
https://user-images.githubusercontent.com/26381349/190577007-ddb57240-426a-448f-818f-adaf73c129a3.mp4
Steps to Reproduce
No response
Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
Editor
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Blocked by #37924

Once #38448 PR is merged will continue the work for this issue.

This issue will be fixed with the #38448 PR.


SonarQube - cannot see client-app and two test projects

SonarQube - cannot see client-app and test projects.

Partially solved: SonarQube has now two projects for Client-App (with tests) and WebApi/Backend. To solve: unit tests are not visible to sonar for backend.

Issue resolved: added missing --collect:"XPlat Code Coverage"; and report generator to convert coverage.cobertura.xml to SonarQube.xml.


texlive: mktexlsr not available on PATH

Describe the bug
The mktexlsr.pl script is usually installed onto the PATH as mktexlsr, but is only available directly from the Nix store (e.g. /nix/store/y4qnj1mhr7gm26bcxpk3lb4875wyf83y-texlive-texlive-scripts-58791/scripts/texlive/mktexlsr.pl).
Steps To Reproduce

Install texlive-combined, e.g. /nix/store/my6nskw81axgw8n4kap21qckbsryqwxz-texlive-combined-full-2021.20210408.
Try to run mktexlsr, which is not available. Note that man mktexlsr does display a man page for the suffix-less mktexlsr as expected.

Expected behavior
As this is important to managing a user texmf root – not managed by Nix, e.g. in $HOME, or a project-specific directory –, the script should probably be available, as it usually is part of a texlive install (and the man page in fact still is).
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"aarch64-darwin"`
 - host os: `Darwin 21.5.0, macOS 12.4`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.6.1`
 - channels(dpn): `""`
 - channels(root): `"nixpkgs-22.05pre338661.3c52ea8c921"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

By the way, this issue also exists in texlive.combined.scheme-small


Better error message is needed

Cannot load custom model is not very helpful, is it possible to show more actionable error messages?

Hi, @elvisun!
Thank you for using flutter_mlkit and issueing.
How about official flutter_ml_vision plugin?
If you know flutter_mlkit is un official plugin and you think continue to use, I try implement it.

Hi,@azihsoyn,
official flutter_ml_vision plugin un support custom model,so i also continue to use!
thanks

Thanks 😄


VMware Virtual Platform not recognized in Preflight "Supported Computer" step

When PXE booting to VMware guest, the Supported Computer Model Check fails to register as supported, despite the following entries in the HWModels.txt

Virtual Machine
VMWare Virtual Platform
VMWare

I manually added the same entries to the local copy of HWModels.txt in case the service wasn't reading the copy hosted on my web server, still no luck.
The WMI properties match the potential values from HWModels.txt:

Any direction would be much appreciated, I'd like to not have to disable the Preflight checks when recording demos and testing new TS's.
FrontEnd 1.6.0
WebService 1.8.0

I had my wife look over the spelling to make sure that I didn't misspell anything, she pointed out the the HWModels.txt entry I put in has a capitalized "W" in VMware. So I tried it and sure enough, that's it. The entries appear to be case-sensitive.
Adding VMware Virtual Platform returns a successful preflight check now.


Next Future Settlement Block is not correctly implemented

What happened:
The DeFiChain Lightwallet shows a different/wrong next Future Settlement Block, then https://defiscan.live/blocks/countdown/NextFutureSwap.
So it’s not possible the click „continue“ in Lightwallet to prepare a swap for the next FutureSwap.
What you expected to happen:
Same/correct Next Future Settlement Block in Lightwallet and Blockchain/defiscan.
How to reproduce it (as minimally and precisely as possible):
The bug occurs with Lightwallet version 2.42.0.
From my understanding Android and iOS are booth impacted.
Anything else we need to know?:

As a workaround, it’s possible to switch ocean endpoint to alternative provider like https://ocean.mydefichain.com.
With mydefichain or with switch back to default provider, the correct Next Future Settlement Block is displayed.

Thanks in your reply.
I can't repeat the case and there is only one user who has come forward. I would suggest closing the issue. I apologize for the inconvenience.
Kind regards

Thanks in your reply.
I can't repeat the case and there is only one user who has come forward. I would suggest closing the issue. I apologize for the inconvenience.
Kind regards


Add drop and copy impls

This change is

Current dependencies on/for this PR:

main

PR #2500   👈

This comment was auto-generated by Graphite.


Long deletions can only have a reference allele of max 256 characters

See fix here:
https://github.com/cBioPortal/cbioportal-frontend/pull/2041/files#diff-2f72793754247af68a0708d569273751R301
We should handle this at the genome nexus server level.
Either

we should have some query field in then response that indicates what genomicLocation you used to query (this is the unedited version)

or

Figure out why we can only have max 256 characters for the reference allele. Is it at the genome nexus level or at the VEP level?

@inodb can you confirm we could close this ticket now?


winch: Use aarch64 backend for code emission.

This patch introduces basic Aarch64 code generation by using cranelift-codegen's backend.
This change does not:

Change the semantics of the code generation
Adds support for other Wasm instructions

The most notable change in this patch is how addressing modes are handled at the MacroAssembler layer: instead of having a canonical address representation, this patch introduces the addressing mode as an associated type in the MacroAssembler trait. This approach has the advantage that gives each ISA enough flexiblity to describe the addressing modes and their constraints in isolation without having to worry on how a particular addressing mode is going to affect other ISAs. In the case of Aarch64 this becomes useful to describe indexed addressing modes (particularly from the stack pointer).
This patch uses the concept of a shadow stack pointer (x28) as a workaround to Aarch64's stack pointer 16-byte alignment. This constraint is enforced by:

Introducing specialized addressing modes when using the real stack pointer; this enables auditing when the real stack pointer is used. As of this change, the real stack pointer is only used in the function's prologue and epilogue.

Asserting that the real stack pointer is not used as a base for addressing modes.

Ensuring that at any point during the code generation process where the stack pointer changes (e.g. when stack space is allocated / deallocated) the value of the real stack pointer is copied into the shadow stack pointer.

@cfallin regarding signal safety -- I did a verification with the program below, using bl_signal which as far as I can tell doesn't set up an alternative stack.

Signal handler
.global _start
.align 2

_start:
  stp x29, x30, [sp, #-16]!

  ;; Signal number, sigint in this case
  mov x0, #2

  ;; Load address of the handler
  adr x1, _signal_handler

  ;; Call bsd_signal to register the signal handler
  bl _bsd_signal

  ;; Unalign the sp;
  ;; simulate making space for word-wise pushes
  sub sp, sp, #8
  sub sp, sp, #8
  sub sp, sp, #8

;; Infinite loop;
;; simulate waiting
   loop: mov x0, #1  ;; Descriptor
   adr x1, _looping   ;; Message address
   mov x2, #5           ;; Length
   mov x16, #4         ;; Write
   svc #0                  ;; Call service
   b loop

;; Commented out since it will never make it here
;; ldp x29, x30, [sp], #16
;; ret

_signal_handler:
  stp x29, x30, [sp, #-16]!
  mov x0, #1             ;; Descriptor
  adr x1, _message  ;; Message address
  mov x2, #15           ;; Length
  mov x16, #4           ;; Write
  svc #0                    ;;  Call service

  ldp x29, x30, [sp], #16

  ;; Terminate the program (for demonstration purposes)
  ;; and to quit the infinite loop

  mov x0, #0      ;; Return code
  mov x16, #1     ;; Service code
  svc #0              ;; Call to terminate

_message: .ascii "Signal handled\n"
_looping: .ascii "Loop\n"

and the results confirm the theory that SP is aligned when entering the signal handler's frame. The program above runs successfully even though the stack pointer is not aligned to 16 before entering the loop. When the signal handler's code is changed to use an unaligned SP to address memory (e.g. stp x29, x30, [sp, #-24]!) we get a bus error crash as expected.

Ah, that's a really interesting outcome, thanks! Was this on macOS/aarch64 or Linux/aarch64? (I guess we'd want to make sure it's properly handled on both?)

Ah, that's a really interesting outcome, thanks! Was this on macOS/aarch64 or Linux/aarch64? (I guess we'd want to make sure it's properly handled on both?)

Yeah, tested in both.

MacOS Ventura 13.2: the linked example in my previous comment is the one I used in Mac.
For linux: I used Ubuntu 20.04.5. I tweaked the program above to use the right params for syscalls.


Lenient mode errors for returning nullable values from null-unmarked methods with a type-parameter return type

At the current main-eisop (76b33c9872c1ccc1b0fc9219ed70b2237b4e6db3) and still with #171:
class Issue172<E> {
  E e() {
    return null;
  }
}

$ ./demo Issue172.java
Issue172.java:3: error: [return.type.incompatible] incompatible types in return.
    return null;
           ^
  type of expression: null?
  method return type: E
1 error

This should be allowed because the return type should be read as E* (i.e., E with unspecified nullness), which permits null in lenient mode.
Since this error comes up only in null-unmarked code, we should be OK with suppressing the small number of times that it occurs. Still, I'm filing it for tracking.

(https://github.com/jspecify/jspecify-reference-checker/commit/76b33c9872c1ccc1b0fc9219ed70b2237b4e6db3#diff-ce82a59b06d0d82bfc6d06835d1b06ac15619bc3a71617d32189d041f02ca9c0R921 came to mind because I remembered seeing nullnessOperatorUnspecified, but undoing that change does not help.)

I've realized that my earlier testing was incomplete. And it turns out that this problem comes up more when I test fully.
On the bright side, my testing with #175 (well, with my variant of it) does appear to eliminate those errors. So we still look to be in good shape.

Yes, once #171 and #175 have both landed, I think we'll be ready to switch over.

(Or, come to think of it, I might be able to mostly work around this one if necessary. But I'm not sure, and it would be at least a little work.)

Fixed by #175.


feat(redux): basic configuration of redux fix #31

Ejected webpack config to resolve import components from src/
Removed import eslint due our new resolve path statement (/node_modules && /src)
Added a eslintignore file
Created basic structure for components (following atomic design)
Basic config for redux
Configured redux-devtools
Created Action Creator inside the reducers following a pretty common used pattern ducks-modular-redux
Used redux-actions lib to improve our reducers
Create a pages/Home and a reducers/testReducer component to test the redux config

It's a good start. However, it would be nice document standards in soon to-be-created issue about how should reducers and actions should be implemented, like predefined actions and generic actions creators to facilitate implementation.

@andrelas1 I think it make sense. Perhaps open an issue to that?


Rx Observable?

Any plans to have Rx Observable support?

I had also the idea of implementing this, just for replacing the async tasks.

I will take a look into this. I have worked a lot with rxjava and it shoudnt be to much to integrate.

That would be great, that way it could also be compatible with Retrofit (when using its RxJava instead of Call)

@diegoRodriguezAguila thats true. I also need this to make it compatible with my api client .

I had the idea of the api that looks like this:
Iron.chest().<String>get("key").subscribe(new Subscriber<String>() {

            @Override
            public void onError(Throwable e) {

            }

            @Override
            public void onNext(String s) {

            }

            @Override
            public void onCompleted() {

            }
        });

It looks good, it could also send updates when the related object gets modified, (instead of having to put an addOnDataChangeListener). Would Rx also be supported int the "*Store" Objects?

@diegoRodriguezAguila I would add a annotation option for enabling RxJava.

@diegoRodriguezAguila The idea to use the Observable for Object changes is great. Are you sure a Observable are calling the subscriber when for example a object got added to a Arraylist?
ArrayList<String> strings = new ArrayList<>();
        strings.add("string");
        Observable.just(strings).subscribe(new Subscriber<ArrayList<String>>() {
            @Override
            public void onCompleted() {

            }

            @Override
            public void onError(Throwable e) {

            }

            @Override
            public void onNext(ArrayList<String> strings) {
                Log.d("array", strings.size() + "");
            }
        });
        strings.add("string");

Array just called once.

I'm not sure but I think Observable.from is for this kind of situations, in order to get notified properly, and if an item is added, tou should call on next with the item added

@diegoRodriguezAguila Then the user has to use a different ArrayList like this:
public class ObservableList<T> {

        protected final List<T> list;
        protected final PublishSubject<T> onAdd;

        public ObservableList() {
            this.list = new ArrayList<T>();
            this.onAdd = PublishSubject.create();
        }
        public void add(T value) {
            list.add(value);
            onAdd.onNext(value);
        }
        public Observable<T> getObservable() {
            return onAdd;
        }
    }

No, that wouldn't be good, to force the user to use an specific type of collection. The key here is that as you are building the Observable and you know exactly when the event of adding the item is launched, (because is launched when the user makes something like MainStore.setContributors(contributors);) the subscriber could be saved and when the user changes the collecion, handle the event and call subscriber.onNext(...) or something like that. Or for example the Contributors list, could internally be that ObservableList wrapped object

I think we could get some ideas from Storio's tables Observables, they are also lists and I think is quite the same logic

I understand you totally wrong. I realized now that you mean the change listener not the transaction. Something like this could be possible i think: Iron.chest().get("key").asObservable(new Subscriper...).

Okay i decided now to go for Iron.chest().get("key"). When you add a subscriber on this onNext will get triggered on every change and on load.

Great! I think thats the whole point of observables, that way for example, if I have a user view, the moment the user saves its modified data, (and i'm currently subscribed on that view), I would get the data automatically updated to the screen. I think it could also work in collections? if I get all the users, (and I see the list on screen) and I add a new user the view would get updated.

You can test Version 0.7.1 now. I have updated the sample app:
Iron.chest().set("rxjava", "bla");
...extends RxActivity
```
Iron.chest().get("rxjava").compose(this.bindToLifecycle()).subscribe(new Subscriber() {
        @Override
        public void onError(Throwable e) {
            e.printStackTrace();
        }

        @Override
        public void onNext(String s) {
            Log.d("change", s);
        }

        @Override
        public void onCompleted() {

        }
    });

    Iron.chest().set("rxjava", "bla2");

    new Handler().postDelayed(new Runnable() {
        @Override
        public void run() {
            Iron.chest().set("rxjava", "bla3");
        }
    }, 2000);

The set and get methods use the scheduler threads so there are no async tasks needed anymore.

I have released Version 0.7.2 now, because i found a critical bug in the callback and i also reduced the methodcount (-6k Methods) and the jar size (-600kb).

Awesome, I'll check it out soon. BTW I suggest you to mark the "issue" as closed and tag it with that release (0.7.2) and add a "feature" label or something like that, it's better for people searching for something similar :)


Typescript doesn't recognise plugins

Version
3.0.0-rc.3
Reproduction link
https://github.com/eladcandroid/vue-cli-errors
Steps to reproduce
Create a new project with typescript and linter support
Install axios plugin with "vue ui"
Try to use this.$axios in HelloWorld.vue
What is expected?
No errors
What is actually happening?
Got a lint error - Property '$axios' does not exist on type 'HelloWorld'
(Less important but also got warning errors about semi-colons)

That's an issue in the axios plugin, which isn't maintained by us. It needs to account for type shims when used with typescript.

@Robula do you know how to do it for Store?
Property '$axios' does not exist on type 'Store<any>'


H3 text option displays as paragraph text.

When editor selects "subtitle H3" in the text component the font on the webpage is displayed as paragraph text (and has option to bold)
We need to have a distinction between the font sizes to visually indicate a subtitle.
Im not sure of the font scale set up now in the solution, but in Figma I feel like the defined H3 size (34.6pt for medium desktop) is too large for this purpose. I would suggest the size should be around 30pt for H3 (medium desktop). Happy to have a chat on this when the task is being looked at.

the H3 text option should work as requested, please verify @NickHaggerty1


Apache CouchDB build issues on PowerPC64LE

Im trying to build Apache CouchDB on PowerPC64LE.
I have installed all dependencies and following all the steps mentioned at https://github.com/apache/couchdb/blob/master/INSTALL.Unix.md
Ran into the following issues:-
Issue 1:-
==========
root@70a8290c0358:~/couchdb/couchdb# make release
==> config (compile)
ERROR: OTP release 18 does not match required regex 19|20|21
ERROR: compile failed while processing /root/couchdb/couchdb/src/config: rebar_abort
Makefile:123: recipe for target 'couch' failed
make: *** [couch] Error 1
root@70a8290c0358:~/couchdb/couchdb#
Solution/Workaround:-
======================
Latest version of erlang on PowerPC64LE is Erlang/OTP 18, could not find OTP 19 or greater for PowerPC64LE architecture.
sar@70a8290c0358:~/couchdb/couchdb$ erl
Erlang/OTP 18 [erts-7.3] [source] [64-bit] [smp:8:8] [async-threads:10] [kernel-poll:false]
Hence put in the following change in the file "rebar.config.script":-
-    {require_otp_vsn, "19|20|21"},
+    {require_otp_vsn, "18|19|20|21"},

Issue 2:-
==========
root@70a8290c0358:~/couchdb/couchdb# make release
.
.
.
make[1]: Entering directory '/home/sar/couchdb/couchdb/src/docs'
sphinx-build -b html -a -W -n -A local=1 -D latex_elements.papersize=a4 -d build/doctree src/ build/html
Traceback (most recent call last):
File "/usr/local/bin/sphinx-build", line 7, in
from sphinx.cmd.build import main
File "/home/sar/.local/lib/python2.7/site-packages/sphinx/cmd/build.py", line 39
file=stderr)
^
SyntaxError: invalid syntax
Makefile:32: recipe for target 'html' failed
make[1]: *** [html] Error 1
make[1]: Leaving directory '/home/sar/couchdb/couchdb/src/docs'
Makefile:520: recipe for target 'src/docs/build' failed
make: *** [src/docs/build] Error 2
Solution/Workaround:-
======================
Used commands "./configure --disable-docs" and "make release" so as to not build any documentation or manpages using Sphinx.
With this, I am able to build Apache CouchDB on PowerPC64LE, testing is pending though.
Any thoughts/help on the above two issues would be highly appreciated.

Please note, I was able to configure and build couchdb using non-root user though with disable-docs option.

Thanks @sarveshtamba .
We don't support Erlang 18 anymore. Explicitly, newer versions of CouchDB than 2.3.1 will require Erlang 19+ (or maybe newer). We will not go back to supporting lower versions of Erlang, so you'll need to compile and install Erlang from scratch.
You probably need Python 3 at this point for the documentation build; our build machines no longer run Sphinx with Python 2. I'd give that a try.

Hi,
Thanks for the reply.
I installed the following on Ubuntu 18.04 for PowerPC64LE inside a clean container:-

Python 3.6.7 (Python 2 version is not installed)
pip 9.0.1 from /usr/lib/python3/dist-packages (python 3.6)
Erlang/OTP 20 [erts-9.2] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:10] [kernel-poll:false]

I tried building latest CouchDB from the master branch - https://github.com/apache/couchdb.git
However now I am facing the following error:-
"CouchDB does not support this version of Erlang ("20.2.2")."
Does CouchDB depend on specific versions of Erlang? If so, are the exact version requirements documented anywhere?
Below are the version/configure details:-
sar@ca6f5b10ec5b:~/couchdb/couchdb$ py
py3clean           pybabel            pydoc3             pygettext3.6       python3-config     python3.6m         python3m-config
py3compile         pybabel-python3    pydoc3.6           pygmentize         python3.6          python3.6m-config
py3versions        pybuild            pygettext3         python3            python3.6-config   python3m

sar@ca6f5b10ec5b:~/couchdb/couchdb$ python3 -V
Python 3.6.7

sar@ca6f5b10ec5b:~/couchdb/couchdb$ pip3 -V
pip 9.0.1 from /usr/lib/python3/dist-packages (python 3.6)

sar@ca6f5b10ec5b:~/couchdb/couchdb$ erl -V
Erlang/OTP 20 [erts-9.2] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:10] [kernel-poll:false]

Eshell V9.2  (abort with ^G)
1>
[2]+  Stopped                 erl -V

sar@ca6f5b10ec5b:~/couchdb/couchdb$ ./configure
==> configuring couchdb in rel/couchdb.config
==> updating dependencies
CouchDB does not support this version of Erlang ("20.2.2").
Check https://docs.couchdb.org/en/latest/whatsnew/index.html for the
latest information on supported releases.
sar@ca6f5b10ec5b:~/couchdb/couchdb$

Hi there,
Unfortunately, we have had to blacklist a number of Erlang releases for bugs that can lead to scheduler collapse based on reports from IBM staff and confirmation from the Erlang developers.
See #1857 and #2047 .
Sorry about that.

Hi @wohali ,
I have managed to build Erlang/OTP <IP_ADDRESS> on Ubunutu 16.04 after resolving all dependencies for Erlang:-
    sar@50c649c461fc:~/otp$ erl -eval '{ok, Version} = file:read_file(filename:join([code:root_dir(), "releases", erlang:system_info(otp_release), "OTP_VERSION"])), io:fwrite(Version), halt().' -noshell
    <IP_ADDRESS>
    sar@50c649c461fc:/usr/local/lib/erlang$ cat releases/RELEASES
    %% coding: utf-8
    [{release,"Erlang/OTP","21","<IP_ADDRESS>",
              [{kernel,"<IP_ADDRESS>","/usr/local/lib/erlang/lib/kernel-<IP_ADDRESS>"},
               {stdlib,"<IP_ADDRESS>","/usr/local/lib/erlang/lib/stdlib-<IP_ADDRESS>"},
               {sasl,"3.3","/usr/local/lib/erlang/lib/sasl-3.3"}],
              permanent}].
    sar@50c649c461fc:~/couchdb/couchdb$ erl
    Erlang/OTP 21 [erts-<IP_ADDRESS>] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1]

    Eshell V<IP_ADDRESS>  (abort with ^G)
    1>

I tried building latest CouchDB from the master branch - https://github.com/apache/couchdb.git
However now I am facing the following error:-
    Running "copy:dist" (copy) task

    Running "copy:couchdb" (copy) task
    Created 4 directories, copied 22 files

    Done.
    make[1]: Entering directory '/home/sar/couchdb/couchdb/src/docs'
    sphinx-build -b html -a -W -n -A local=1 -D latex_elements.papersize=a4 -d build/doctree src/ build/html
    Running Sphinx v1.3.6
    making output directory...
    loading pickled environment... not yet created
    building [mo]: all of 0 po files
    building [html]: all source files
    updating environment: 124 added, 0 changed, 0 removed
    reading sources... [100%] whatsnew/index
    looking for now-outdated files... none found
    pickling environment... done
    checking consistency... done
    preparing documents...
    Theme error:
    unsupported theme option 'canonical_url' given
    Makefile:32: recipe for target 'html' failed
    make[1]: *** [html] Error 1
    make[1]: Leaving directory '/home/sar/couchdb/couchdb/src/docs'
    Makefile:520: recipe for target 'src/docs/build' failed
    make: *** [src/docs/build] Error 2

Am I missing anything?

Your Sphinx is outdated:
Running Sphinx v1.3.6

You need v1.7 at least, I believe.
I recommend you install python3-pip and do # pip3 install sphinx instead of relying on the very old Ubuntu 16.04 package.

Your Sphinx is outdated:
Running Sphinx v1.3.6

You need v1.7 at least, I believe.
I recommend you install python3-pip and do # pip3 install sphinx instead of relying on the very old Ubuntu 16.04 package.

Tried that, getting the below error:-
==> setup (compile)
Compiled src/setup_httpd_handlers.erl
Compiled src/setup_epi.erl
Compiled src/setup_sup.erl
Compiled src/setup_app.erl
Compiled src/setup_httpd.erl
Compiled src/setup.erl
==> rel (compile)
==> couchdb (compile)
Installing CouchDB into rel/couchdb/ ...
==> rel (generate)
WARN:  'generate' command does not apply to directory /home/sar/couchdb/couchdb
cp: cannot stat 'src/docs/build/man/apachecouchdb.1': No such file or directory
Makefile:407: recipe for target 'release' failed
make: *** [release] Error 1
sar@50c649c461fc:~/couchdb/couchdb$

Try with a brand new git clone, there's some bugs in the Makefile if the docs only partially fail to build that no one's ever cleaned up.
Sphinx makes the manpage in a second step, see https://github.com/apache/couchdb-documentation/blob/master/Makefile#L44-L45 . If that failed but the first step succeeded, it won't try again to build it today. You could also cd src/docs && make man to diagnose if there is a problem.
If that all still fails, let me know and I'll look at it next week.

Hi @wohali ,
I tried with a clean git clone of couchdb with all the pre-requisites installed.
I ran into the following issue:-
    make[1]: Entering directory '/home/sar/couchdb/couchdb/src/docs'
    sphinx-build -b html -a -W -n -A local=1 -D latex_elements.papersize=a4 -d build/doctree src/ build/html
    Running Sphinx v2.1.0
    making output directory... done
    building [mo]: all of 0 po files
    building [html]: all source files
    updating environment: 124 added, 0 changed, 0 removed
    reading sources... [100%] whatsnew/index
    looking for now-outdated files... none found
    pickling environment... done
    checking consistency... done
    preparing documents... done
    writing output... [100%] whatsnew/index

    Warning, treated as error:
    /home/sar/couchdb/couchdb/src/docs/src/api/server/common.rst:1489:Could not lex literal_block as "http". Highlighting skipped.
    Makefile:32: recipe for target 'html' failed
    make[1]: *** [html] Error 2
    make[1]: Leaving directory '/home/sar/couchdb/couchdb/src/docs'
    Makefile:520: recipe for target 'src/docs/build' failed
    make: *** [src/docs/build] Error 2

However I executed the workaround cd src/docs && make man as suggested and then re-built couchdb, the build completed successfully.
    Installing CouchDB into rel/couchdb/ ...
    ==> rel (generate)
    WARN:  'generate' command does not apply to directory /home/sar/couchdb/couchdb
    ... done

        You can now copy the rel/couchdb directory anywhere on your system.
        Start CouchDB with ./bin/couchdb from within that directory.

Question 1:-
Is this a known/documented issue and any resolution for this workaround?
Next, I started the couchdb instance as per steps in the INSTALL.Unix.md readme, and ran into following issues at startup:-
[error] 2019-06-10T08:25:53.103978Z couchdb@localhost emulator -------- Error in process <0.326.0> on node couchdb@localhost with exit value:
{database_does_not_exist,[{mem3_shards,load_shards_from_db,"_users",[{file,"src/mem3_shards.erl"},{line,403}]},{mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_shards.erl"},{line,378}]},{mem3_shards,load_shards_from_disk,2,[{file,"src/mem3_shards.erl"},{line,407}]},{mem3_shards,for_docid,3,[{file,"src/mem3_shards.erl"},{line,91}]},{fabric_doc_open,go,3,[{file,"src/fabric_doc_open.erl"},{line,38}]},{chttpd_auth_cache,ensure_auth_ddoc_exists,2,[{file,"src/chttpd_auth_cache.erl"},{line,187}]},{chttpd_auth_cache,listen_for_changes,1,[{file,"src/chttpd_auth_cache.erl"},{line,134}]}]}

I was able to resolve this after creating the three system databases manually on startup in another shell, while the couchdb instance was running in the first shell as per http://docs.couchdb.org/en/latest/setup/single-node.html:
curl -X PUT http://<IP_ADDRESS>:5984/_users
curl -X PUT http://<IP_ADDRESS>:5984/_replicator
curl -X PUT http://<IP_ADDRESS>:5984/_global_changes

Question 2:-
Initially I tried inside a docker container, however opening another shell in a docker container is not possible.
How do we proceed in this case?
Post this I was able to perform some operations as per https://guide.couchdb.org/draft/tour.html:-
    root@pts00452-vm13:~# curl http://<IP_ADDRESS>:5984/
    {"couchdb":"Welcome","version":"2.1.0-cf00dc2","features":["scheduler"],"vendor":{"name":"The Apache Software Foundation"}}
    root@pts00452-vm13:~# curl -X GET http://<IP_ADDRESS>:5984/_all_dbs
    ["_global_changes","_replicator","_users"]
    root@pts00452-vm13:~# curl -X PUT http://<IP_ADDRESS>:5984/baseball
    {"ok":true}
    root@pts00452-vm13:~# curl -X GET http://<IP_ADDRESS>:5984/_all_dbs
    ["_global_changes","_replicator","_users","baseball"]
    root@pts00452-vm13:~# curl -X PUT http://<IP_ADDRESS>:5984/baseball
    {"error":"file_exists","reason":"The database could not be created, the file already exists."}
    root@pts00452-vm13:~# curl -X PUT http://<IP_ADDRESS>:5984/plankton
    {"ok":true}
    root@pts00452-vm13:~# curl -X GET http://<IP_ADDRESS>:5984/_all_dbs
    ["_global_changes","_replicator","_users","baseball","plankton"]
    root@pts00452-vm13:~# curl -X DELETE http://<IP_ADDRESS>:5984/plankton
    {"ok":true}
    root@pts00452-vm13:~# curl -X GET http://<IP_ADDRESS>:5984/_all_dbs
    ["_global_changes","_replicator","_users","baseball"]

Let me know your thoughts on this.

@wohali any inputs?

I'm not sure about your problem with the build, but this shouldn't be happening. Will leave this open until someone can look at it. I'm out of time for this week, sorry.
You can open another shell in a Docker container: https://stackoverflow.com/questions/17903705/is-it-possible-to-start-a-shell-session-in-a-running-container-without-ssh
For any other user-level questions these are not CouchDB bugs and you should seek assistance on our<EMAIL_ADDRESS>mailing list or Slack, whichever you prefer.

Entire test suite for CouchDB v2.3(current master) executes successfully/passes with Erlang v21 and Elixir v1.8 on PowerPC64LE. Closing this issue. Thanks for all your help and support in getting this through.


feat: Add time zone fields to events

Adds support for time-zones for start and end dates in the Event entity

The date timezones shouldn't be editable through the UI


[Feature request] - Integrate MPT from MosaicML

feature
Hi dear LLaVa maintainers.
Mosaic has just released their new OpenSource model called MPT-7B and they claim it's fully open source and is matching LLaMa while having up to 65K token window!

Would be incredible to see it used inside LLaVa
https://www.mosaicml.com/blog/mpt-7b

Hi @altryne
It's released!  Thanks to the LLaVA-lightning, we are able to release it today.
Checkout the Tweet here.
Checkout the instructions here.

Incredible effort @haotian-liu 👏 Did NOT expect this to be resolved this quick! Super exciting! Thank you for the effort. (boosted on twitter)


ProofExchangeRecord does not contain information about request and received proof

It appears that  ProofExchangeRecord record does not contain any data about the sent proof request payload and proof received from the Prover.
As Verifier  I would like to show the content of the received proof on the UI (requested attributes / filled predicates), but it appears that ProofExchangeRecord record does not contain either the proof request payload which was sent or proof received from the Prover. It only contains the flag indicating the validity.
Also, I would like to have a history of requests/proofs.
What is the motivation for excluding this data from the record? Can we add this information?  Or I am looking at the wrong place?

It has been extracted into separate DidCommMessageRecords to make it easier to support multiple protocol versions without the message classes clashing.
You can call agent.proofs.getFormatData to retrieve the data you're looking for

Thank you for the clarification!


[Bug]: Adaptation Project Sample

OData Version
OData V2
Draft
Yes
Scenario
Fiori Adaptation Project
Environment
VSCode
UI5 Spreadsheet Component
0.33.1
What happened?
I was not able to run
https://github.com/spreadsheetimporter/sample-adaptation-banks
and I was not able to add the control to my own adaptation according to the steps in this blog
https://community.sap.com/t5/technology-blogs-by-members/how-to-add-excel-upload-to-any-standard-sap-fiori-app-tutorial-with-app/ba-p/13578225.
The control is being loaded from ../resources.
Uncaught (in promise) ModuleError: failed to load 'cc/spreadsheetimporter/v0_33_1/Component.js' from ../resources/cc/spreadsheetimporter/v0_33_1/Component.js: script load error
    at se (http://localhost:8082/resources/sap-ui-core.js:10:7148)
    at ne.failWith (http://localhost:8082/resources/sap-ui-core.js:10:4989)
    at HTMLScriptElement.i (http://localhost:8082/resources/sap-ui-core.js:10:10946)
Caused by: Error: script load error
    at HTMLScriptElement.i (http://localhost:8082/resources/sap-ui-core.js:10:10988)

To fix it I had to hardcode the path
const oComponent = this.base.getView().getController().getOwnerComponent();
oComponent.runAsOwner(async () => {
    this.spreadsheetUpload = await Component.create({
        usage: "customer.spreadsheetImporter",
        async: true,
        componentData: {
            context: this,
            fieldMatchType: "label",
            createActiveEntity: true,
        },
        url: "/sap/bc/ui5_ui5/sap/Z_XUP_v0_33_1",
        name: "cc.spreadsheetimporter.v0_33_1"
    });
    this.spreadsheetUpload.openSpreadsheetUploadDialog();
    this.getView().setBusy(false);
});

Do you know if there is a better way to tell the app where the control should be loaded from?
Relevant log output
Uncaught (in promise) ModuleError: failed to load 'cc/spreadsheetimporter/v0_33_1/Component.js' from ../resources/cc/spreadsheetimporter/v0_33_1/Component.js: script load error
    at se (http://localhost:8082/resources/sap-ui-core.js:10:7148)
    at ne.failWith (http://localhost:8082/resources/sap-ui-core.js:10:4989)
    at HTMLScriptElement.i (http://localhost:8082/resources/sap-ui-core.js:10:10946)
Caused by: Error: script load error
    at HTMLScriptElement.i (http://localhost:8082/resources/sap-ui-core.js:10:10988)

Spreadsheet Component Init
Not working:

const spreadsheetUploadComponent = await this.base.getView().getController().getOwnerComponent().createComponent({
    usage: "customer.spreadsheetImporter",
    async: true,
    componentData: {
        context: this,
        fieldMatchType: "label",
        createActiveEntity: true,
    }
})
spreadsheetUploadComponent.openSpreadsheetUploadDialog();

Manifest
{
  "fileName": "id_1710140995700",
  "namespace": "apps/cus.sd.custmat.manage/appVariants/customer.cus.sd.custmat.manage/changes",
  "layer": "CUSTOMER_BASE",
  "fileType": "change",
  "creation": "2024-03-11T07:09:55.700Z",
  "packageName": "$TMP",
  "reference": "customer.cus.sd.custmat.manage",
  "support": {
    "generator": "add-sapui5-component-usage-generator"
  },
  "changeType": "appdescr_ui5_addComponentUsages",
  "content": {
    "componentUsages": {
      "customer.spreadsheetImporter": {
        "name": "cc.spreadsheetimporter.v0_33_1",
        "lazy": false,
        "settings": {},
        "componentData": {}
      }
    }
  }
}

You wrote Environment: VSCode. Did you try to deploy it?
I think i can remember that it did not work there but when i deployed it it worked.
Your workaround should also work when deployed.

Well, i wrote in the blog post that the preview works :/
So i dont know the reason exactly, but it maybe works in BAS?

Hi @MARCxGAMBIT
can i still help you here?
Currently dont have a system to try adaption project.

My workaround works locally and deployed so it's all good for me. It's more of an FYI for you to maybe update your samples.

Yes, thank you.
I've only had one try with the adaptions so far.
There are still a few special features with the use of components.
There is currently still an open SAP ticket for this, so I need to improve the documentation.
Unfortunately, none of this has anything to do with my specific component, but with the general handling of resue components in the SAP system.
I will leave the issue open until I have improved the documentation.


Add the ability to define tags

Fixes #31

I can't think of a need since it'll get auto-populated from GH actions env vars. Maybe someone can convince me later

ship it