Can't work out how to change timezone of a date for display

I have a model that creates a property as a moment instance, always at UTC time. When being displayed in my template, I'd like to have the moment changed to a different timezone. I've tried this in my .hbs template:
{{moment-format model.timestampUTC 'd MMM, HH:mm' timeZone='Australia/Sydney'}}

But it continues to output the time in UTC. I've also tried creating a computed property on my model like:
timestampLocal: computed('timestampUTC', function() {
	return this.timestampUTC.tz('Australia/Sydney');
})

However, this throws an error saying that there's no 'tz' function on that object.
Perhaps I'm not including the moment-timezone.js thing properly? I've tried adding this to my config/environment.js file, but no luck:
module.exports = function(environment) {

let ENV = {

	// etc. etc.

	moment: {
		includeTimezone: 'all'
	}
};

    return  ENV;
}

I feel like I'm missing something obvious...

I think you need to interact with the moment service to change the timezone for moment-format. Try setting the display timezone there and see if that gets you anywhere.

Turns out I hadn't correctly installed the 'moment-timezone' package. Once I installed this into my Ember solution (using bower) everything started working fine.
Thanks for the help @scottkidder


CPP: Add detail to the CPP-205 test

Add detail to the CPP-205 test, so that it's easier to tell which things are associated with which template / instantiation (see also the discover_walk changes https://github.com/Semmle/ql/pull/317/files#diff-9ebc04b7555032e8235243d1e995883d).
@jbj

I have no idea what this test does. Assigned @ian-semmle.

I think the test is failing because this PR assumes the presence of the discover_walk changes, so it should be on the next branch.

The expected output now needs 4 __va_list_tag::s

Updated with __va_list_tag::.

I believe this is ready to merge.


how to add item on the top of recyclerView

Hey! Its a great library!
I'm currently using it and got stuck to it..
When New item is added, it pops from bottom but i want to add it at top,
How can i achieve it.
@Override
    public void onFeedsChanged(final Feed_item_for_adapter mFeedSuper) {
        mRecyclerView.post(new Runnable() {`
            `@Override
            public void run() {`
                `mFastItemAdapter.add(mFeedSuper);`
                `mFastItemAdapter.notifyDataSetChanged();`
            }
        });
    }

@SahajRana you don't have to call the notify methods if you use the add, ... methods from the FastAdapter everything is handled for you.
If you want to add something on top just add it at position 0
https://github.com/mikepenz/FastAdapter/blob/develop/library/src/main/java/com/mikepenz/fastadapter/adapters/ItemAdapter.java#L341
mFastItemAdapter.add(0, mFeedSuper)

thanks.. it worked!


fix: set cursor block after closing input prompt from insert mode

I've noticed that after closing the input prompt from the insert mode, the cursor shape doesn't change back to block
How to reproduce:

open input prompt (e.g try to rename some file)
press enter to close it (from insert mode)
see that cursor shape is now bar (I guess it should be block as before opening yazi)

Before

https://github.com/sxyazi/yazi/assets/61150013/fb33b774-e1a9-4490-8ce8-be203a4c7b73

After

https://github.com/sxyazi/yazi/assets/61150013/22c7fa80-be8f-409d-93c0-b4164ec8ab51

(Not sure that I placed Term::set_cursor_block() to the right place)

Thank you for your PR and detailed explanation!
It seems that for users whose default cursor is not a block, set_cursor_block doesn't make sense.
I think it's best to change set_cursor_block to set_cursor_default and use SetCursorStyle::DefaultUserShape instead of SetCursorStyle::BlinkingBlock here.

 It makes more sense, I updated it

Okay I'll update this one too, but I'm not sure that we should show default shape in normal mode, if user's default shape is bar, then this might be confusing (same shape in both normal and insert modes)?

Oh! I didn't think of that...
Keeping it as a block in normal mode should make sense, and it should restore to the default upon exiting.

Thank you, merged!

I think this issue persists when confirming There are … tasks running, sure to quit? (y/N) to exit the program. I didn't look at the code, but maybe that code path avoids the fix.


Add 'docker compose up --wait' functionality

I need this for my API services that have healthchecks to confirm that they are operational.

Thanks, ideally, we should have a compose file with a healthcheck, then verify that without "wait" the container is up, but the healthcheck is not validated, but with "wait" as soon as the function ends, the healthcheck is valid.
I have a bit of time this afternoon, I'll implement this test. You'll be able to use this as reference for future pull requests :)

this test is a bit slow, but it really makes sure the flag is working :)


Update config-settings.rst

Updates for: https://github.com/mattermost/docs/issues/3845

Yep, thanks, @sadohert, that was the main review area. :)

Looks good although I noticed that the TOC has mysteriously disappeared from administration/config-settings.rst. I don't see any direct changes in this PR that would have led to it.

Thanks, @amyblais. I made the "Configuration in database" and "Environment variables" into sections - they were above the TOC entry though, so it looks like that caused the TOC to disappear. Sorted now.
I'd like to move the environment variables section to a more prominent position - that's a separate PR though.

/check-cla

/check-cla


Rename github API parameter: limit -> per_page

Description
Previously the github api uses the 'limit' parameter to set the maximum number
of entries returned in a response. The name was changed to 'per_page'. I changed
all occurances of the limit paramter with the new name.
Motivation and Context

By default the github API returns a limited number of results for the "/user/teams" endppint. AFAIR its something in the range of 20. If a user is member of >20 teams, the oauth2_proxy will only get the first 20 and does not know about the remaining teams. This leads to an "Invalid Account" response, even if the user is a member of the required team.
How Has This Been Tested?

I built a new docker image with my modifications and deployed it into my setup. With these changes I am able to authenticate with an affected user account.
Checklist:

[ ] My change requires a change to the documentation or CHANGELOG.
[ ] I have updated the documentation/CHANGELOG accordingly.
[x] I have created a feature (non-master) branch for my PR.

https://github.com/bitly/oauth2_proxy/pull/613 noted that the documented max value for this param is 100, not 200 (also I wonder when "limit" changed to "per_page", can't find "limit" mentioned anywhere anymore ...)

Thanks for the feedback 👍
After some problems while installing the go dependencies I was able to excute the provider tests on my local machine. Its my first contact with go ;) Also thanks for the hint for how to fix the tests again ;)
At least the provider tests are passing on my local machine. Do I have to tweak something to make the build in Travis working? As far as I can see the error in Travis is related to some linting issues?!

Changes are superseed by #102


Sync with master

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues.

Fixes #
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, releated PRs, TODO items or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

:exclamation: No coverage uploaded for pull request base (jballerina@1daa3fa). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             jballerina   #15864   +/-   ##
=============================================
  Coverage              ?    9.23%
  Complexity            ?     2334
=============================================
  Files                 ?     1487
  Lines                 ?    75414
  Branches              ?     9852
=============================================
  Hits                  ?     6966
  Misses                ?    67733
  Partials              ?      715

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 1daa3fa...6a40a5e. Read the comment docs.


Panning on selection is

It seems to me that an auto-centering feature was added that engages when an object is selected. The map will pan to the center of the object, irrespective of where I selected the object. This makes editing large objects, such as long paths, very cumbersome and annoying as the editor will pan away from the part of the object that I wanted to edit. Thanks.

I have also noticed this. Sometimes the object is even off screen, e.g. a length of road that goes around a hill, and the map centres at the focal point of the arc, with no arc visible.

Welcome, @polychloriert. iD shouldn't be moving the map just because you click on something. Do you have steps to reproduce this behavior? Or a screencapture?

Thanks for the quick reply. I just checked again and the described behavior is no longer present. Weird. Thanks anyway :)

Ah, got it again. If I had to speculate, I'd see it is some kind of state bug during editing.
How to reproduce it:

Edit a feature that is considerably larger than the current map pane
Let the editor pan the map at least once to focus on the nect/current node (happens during repeated node deletion for example)
Now, when seleting another feature, the map will always pan to its center of mass
The behavior can be fixed temporarily by reloading the page. Only until the above steps are repeated, of course.

@polychloriert Weird!! Definitely a bug. Thanks for reporting and for the detailed steps.

No, thank YOU for working on iD - it keeps getting better and better :)


Fix preserveResolvers for root resolvers

Here is a test that show that that last commit in #96 broke preserveResolvers for root resolvers.
Turns out, that test was already there, but no mock was in mockMap so nothing could take precedence.
@helfer I'll work on a fix.

And here is the fix, @helfer

I spoke too fast. None of this code, or the previous fix for that matter, take into account the fact that mocks and resolvers can return promises. Will fix.

Alright, there was more than a few problems with the implementations from 3 weeks ago, where we were trying to merge both mock and resolver.
      field.resolve = (...args) => {
        const mockedValue = mockResolver(...args);
        const resolvedValue = oldResolver(...args);
        return typeof mockedValue === 'object' && typeof resolvedValue === 'object'
          ? Object.assign({}, mockedValue, resolvedValue) : resolvedValue;
      };

this wouldn't work if either mockedValue or resolvedValue were promises, which are supported by GraphQL (I added a test),
typeof mockedValue === 'object' was just wrong, since Javascript arrays are also objects (I added a test),
Object.assign() only works for enumerable properties. This is a problem if either mockedValue or resolvedValue use Object.defineProperty to implement access to their properties (I added a test). This is a real issue if you use the popular sequelize ORM for example. Say, you store records in a database, with the name column. If you retrieve a row using sequelize's findOne, you will get an object foo, which does not have an enumerable name property, but defines one using Object.defineProperty. It works perfectly fine when fed to GraphQL (via graphql-sequelize for example), because the GraphQL execution engine will access the property using foo.name or foo['name'] down the road. There is no assumption as to whether that property is enumerable or not (and owned).

Here is the new version (see commit in that PR):
      field.resolve = (...args) => Promise.all([
        mockResolver(...args),
        oldResolver(...args),
      ]).then(values => {
        const [mockedValue, resolvedValue] = values;
        if (isObject(mockedValue) && isObject(resolvedValue)) {
          return new Proxy({}, {
            get: (target, key) => {
              const value = resolvedValue[key];
              return value === undefined ? mockedValue[key] : value;
            },
          });
        }
        return resolvedValue;
      });

uses Promise.all() to handle promises,
uses isObject() to ignore arrays,
returns a Proxy that overrides the dot and bracket operators and uses the corresponding key in resolvedValue or in mockedValue otherwise.

Now the issue with Proxies is that they can not be transpiled by Babel. They are supported by Node 6. I don't know what kind of Node compatibility you guys want to maintain.
You could return a plain object instead of the Proxy:
       return Object.assign({}, mockedValue, resolvedValue);

but you would give up support for properties defined through Object.defineProperty.
What do you think @helfer?

Oh, wow, I clearly didn't look closely enough then. The dangers of relying too much on tests when they don't actually cover enough possible cases...
At the moment I think we cannot support only node 6, we also have to support node 4. I think it's fine to not support Object.assignProperty properties, we just have to document it somewhere.
Thanks a lot, by the way, this is great stuff! Once you rebase the PR, I will take a careful look this time.

@helfer OK done (hopefully). I reverted back to Object.assign() instead of Proxy. I left the Proxy solution and the corresponding test in comments, if you don't mind.

Ok, perfect! I merged another PR, so you need to do another rebase.If you have time, it would be great if you could add that comment I mentioned in the test as well. Ping me on slack when you've rebased, so I can merge it right away so we don't have to do another rebase etc.
PS: Oh, and if you could add an entry in the changelog that would be very nice as well.

Looks like the linter is not happy. Maybe you can try defining the function that runs inside the forEach outside the while loop?

Awesome, thanks so much!


[Bug]: vllm infer for Qwen2-VL-72B-Instruct-GPTQ-Int8

Your current environment

The output of `python collect_env.py`
$python collect_env.py
WARNING 11-26 09:49:49 cuda.py:22] You are using a deprecated `pynvml` package. Please install `nvidia-ml-py` instead, and make sure to uninstall `pynvml`. When both of them are installed, `pynvml` will take precedence and cause errors. See https://pypi.org/project/pynvml for more information.
Collecting environment information...
PyTorch version: 2.4.0+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Alibaba Group Enterprise Linux Server 7.2 (Paladin) (x86_64)
GCC version: (GCC) 9.2.1 20200522 (Alibaba 9.2.1-3 2.17)
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.30

Python version: 3.8.18 (default, Sep 11 2023, 13:40:15)  [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.10.134-13.al8.x86_64-x86_64-with-glibc2.17
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA A800-SXM4-80GB
GPU 1: NVIDIA A800-SXM4-80GB

Nvidia driver version: 470.161.03
cuDNN version: Probably one of the following:
/usr/local/cuda/targets/x86_64-linux/lib/libcudnn.so.8.9.3
/usr/local/cuda/targets/x86_64-linux/lib/libcudnn_adv_infer.so.8.9.3
/usr/local/cuda/targets/x86_64-linux/lib/libcudnn_adv_train.so.8.9.3
/usr/local/cuda/targets/x86_64-linux/lib/libcudnn_cnn_infer.so.8.9.3
/usr/local/cuda/targets/x86_64-linux/lib/libcudnn_cnn_train.so.8.9.3
/usr/local/cuda/targets/x86_64-linux/lib/libcudnn_ops_infer.so.8.9.3
/usr/local/cuda/targets/x86_64-linux/lib/libcudnn_ops_train.so.8.9.3
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                128
On-line CPU(s) list:   0-127
Thread(s) per core:    2
Core(s) per socket:    32
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 106
Model name:            Intel(R) Xeon(R) Platinum 8369B CPU @ 2.90GHz
Stepping:              6
CPU MHz:               3499.987
CPU max MHz:           3500.0000
CPU min MHz:           800.0000
BogoMIPS:              5800.00
Virtualization:        VT-x
L1d cache:             48K
L1i cache:             32K
L2 cache:              1280K
L3 cache:              49152K
NUMA node0 CPU(s):     0-31,64-95
NUMA node1 CPU(s):     32-63,96-127
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 invpcid_single intel_ppin ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local split_lock_detect wbnoinvd dtherm ida arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq rdpid fsrm md_clear pconfig flush_l1d arch_capabilities

Versions of relevant libraries:
[pip3] atorch==1.2.1
[pip3] flake8==6.1.0
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.23.5
[pip3] nvidia-cublas-cu12==<IP_ADDRESS>
[pip3] nvidia-cuda-cupti-cu12==12.1.105
[pip3] nvidia-cuda-nvrtc-cu12==12.1.105
[pip3] nvidia-cuda-runtime-cu12==12.1.105
[pip3] nvidia-cudnn-cu12==<IP_ADDRESS>
[pip3] nvidia-cufft-cu12==<IP_ADDRESS>
[pip3] nvidia-curand-cu12==<IP_ADDRESS>
[pip3] nvidia-cusolver-cu12==<IP_ADDRESS>
[pip3] nvidia-cusparse-cu12==<IP_ADDRESS>
[pip3] nvidia-ml-py==12.560.30
[pip3] nvidia-nccl-cu12==2.20.5
[pip3] nvidia-nvjitlink-cu12==12.6.68
[pip3] nvidia-nvtx-cu12==12.1.105
[pip3] pynvml==11.4.1
[pip3] pyzmq==25.1.2
[pip3] sentence-transformers==3.2.0
[pip3] torch==2.4.0
[pip3] torchaudio==2.4.0
[pip3] torchpippy==0.1.1+cecc4fc
[pip3] torchvision==0.19.0
[pip3] transformers==4.46.2
[pip3] transformers-stream-generator==0.0.5
[pip3] triton==3.0.0
[conda] atorch                    1.2.1                    pypi_0    pypi
[conda] numpy                     1.24.1                   pypi_0    pypi
[conda] nvidia-cublas-cu12        <IP_ADDRESS>                 pypi_0    pypi
[conda] nvidia-cuda-cupti-cu12    12.1.105                 pypi_0    pypi
[conda] nvidia-cuda-nvrtc-cu12    12.1.105                 pypi_0    pypi
[conda] nvidia-cuda-runtime-cu12  12.1.105                 pypi_0    pypi
[conda] nvidia-cudnn-cu12         <IP_ADDRESS>                 pypi_0    pypi
[conda] nvidia-cufft-cu12         <IP_ADDRESS>                pypi_0    pypi
[conda] nvidia-curand-cu12        <IP_ADDRESS>               pypi_0    pypi
[conda] nvidia-cusolver-cu12      <IP_ADDRESS>               pypi_0    pypi
[conda] nvidia-cusparse-cu12      <IP_ADDRESS>               pypi_0    pypi
[conda] nvidia-ml-py              12.560.30                pypi_0    pypi
[conda] nvidia-nccl-cu12          2.20.5                   pypi_0    pypi
[conda] nvidia-nvjitlink-cu12     12.6.68                  pypi_0    pypi
[conda] nvidia-nvtx-cu12          12.1.105                 pypi_0    pypi
[conda] pynvml                    11.4.1                   pypi_0    pypi
[conda] pyzmq                     25.1.2                   pypi_0    pypi
[conda] sentence-transformers     3.2.0                    pypi_0    pypi
[conda] torch                     2.4.0                    pypi_0    pypi
[conda] torchaudio                2.4.0                    pypi_0    pypi
[conda] torchpippy                0.1.1+cecc4fc            pypi_0    pypi
[conda] torchvision               0.19.0                   pypi_0    pypi
[conda] transformers              4.46.2                   pypi_0    pypi
[conda] transformers-stream-generator 0.0.5                    pypi_0    pypi
[conda] triton                    3.0.0                    pypi_0    pypi
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.6.3.post1
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
Could not collect

NVIDIA_VISIBLE_DEVICES=GPU-8146fa97-b89e-8d8a-006e-a33b4db5f764,GPU-640d8674-21b7-6141-a8a4-bd4c619c05d4
LD_LIBRARY_PATH=/opt/conda/lib/python3.8/site-packages/cv2/../../lib64::/opt/conda/lib/python3.8/site-packages/aistudio_common/reader/libs/:/opt/taobao/java/jre/lib/amd64/server/:/usr/local/cuda/lib64:/opt/conda/lib/python3.8/site-packages/aistudio_common/reader/libs/:/opt/taobao/java/jre/lib/amd64/server/:/usr/local/cuda/lib64:/opt/conda/lib/python3.8/site-packages/aistudio_common/reader/libs/:/opt/taobao/java/jre/lib/amd64/server/:/usr/local/cuda/lib64:/opt/conda/lib/python3.8/site-packages/aistudio_common/reader/libs/:/opt/taobao/java/jre/lib/amd64/server/:/usr/local/cuda/lib64:/opt/conda/lib/python3.8/site-packages/aistudio_common/reader/libs/:/opt/taobao/java/jre/lib/amd64/server/:/usr/local/cuda/lib64
NVIDIA_DRIVER_CAPABILITIES=all
CUDA_MODULE_LOADING=LAZY

Model Input Dumps
No response
🐛 Describe the bug
running the following code for Qwen2-VL-72B-Instruct-GPTQ-Int8 in vllm:
import torch, os
from transformers import AutoProcessor
from transformers import Qwen2VLForConditionalGeneration # adding this line could leads to error
from vllm import LLM, SamplingParams
from qwen_vl_utils import process_vision_info

MODEL_PATH = "local/models/Qwen2-VL-72B-Instruct-GPTQ-Int8"
llm = LLM(
    model=MODEL_PATH,
    limit_mm_per_prompt={"image": 10, "video": 10},
    tensor_parallel_size=2
)

Adding the line "from transformers import Qwen2VLForConditionalGeneration" will leads to error:

WARNING 11-26 09:52:54 cuda.py:22] You are using a deprecated pynvml package. Please install nvidia-ml-py instead, and make sure to uninstall pynvml. When both of them are installed, pynvml will take precedence and cause errors. See https://pypi.org/project/pynvml for more information.
INFO 11-26 09:53:03 gptq_marlin.py:107] The model is convertible to gptq_marlin during runtime. Using gptq_marlin kernel.
INFO 11-26 09:53:03 config.py:905] Defaulting to use mp for distributed inference
INFO 11-26 09:53:03 llm_engine.py:237] Initializing an LLM engine (v0.6.3.post1) with config: model='/mnt/282062/pretrained_models/Qwen2-VL-72B-Instruct-GPTQ-Int8', speculative_config=None, tokenizer='/mnt/282062/pretrained_models/Qwen2-VL-72B-Instruct-GPTQ-Int8', skip_tokenizer_init=False, tokenizer_mode=auto, revision=None, override_neuron_config=None, rope_scaling=None, rope_theta=None, tokenizer_revision=None, trust_remote_code=False, dtype=torch.float16, max_seq_len=32768, download_dir=None, load_format=LoadFormat.AUTO, tensor_parallel_size=2, pipeline_parallel_size=1, disable_custom_all_reduce=False, quantization=gptq_marlin, enforce_eager=False, kv_cache_dtype=auto, quantization_param_path=None, device_config=cuda, decoding_config=DecodingConfig(guided_decoding_backend='outlines'), observability_config=ObservabilityConfig(otlp_traces_endpoint=None, collect_model_forward_time=False, collect_model_execute_time=False), seed=0, served_model_name=/mnt/282062/pretrained_models/Qwen2-VL-72B-Instruct-GPTQ-Int8, num_scheduler_steps=1, chunked_prefill_enabled=False multi_step_stream_outputs=True, enable_prefix_caching=False, use_async_output_proc=True, use_cached_outputs=False, mm_processor_kwargs=None)
WARNING 11-26 09:53:03 multiproc_gpu_executor.py:53] Reducing Torch parallelism from 128 threads to 1 to avoid unnecessary CPU contention. Set OMP_NUM_THREADS in the external environment to tune this value as needed.
INFO 11-26 09:53:03 custom_cache_manager.py:17] Setting Triton cache manager to: vllm.triton_utils.custom_cache_manager:CustomCacheManager
(VllmWorkerProcess pid=8387) INFO 11-26 09:53:04 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=8387) ERROR 11-26 09:53:04 multiproc_worker_utils.py:229] Exception in worker VllmWorkerProcess while processing method init_device.
(VllmWorkerProcess pid=8387) ERROR 11-26 09:53:04 multiproc_worker_utils.py:229] Traceback (most recent call last):
(VllmWorkerProcess pid=8387) ERROR 11-26 09:53:04 multiproc_worker_utils.py:229]   File "/opt/conda/lib/python3.8/site-packages/vllm/executor/multiproc_worker_utils.py", line 223, in _run_worker_process
(VllmWorkerProcess pid=8387) ERROR 11-26 09:53:04 multiproc_worker_utils.py:229]     output = executor(*args, **kwargs)
(VllmWorkerProcess pid=8387) ERROR 11-26 09:53:04 multiproc_worker_utils.py:229]   File "/opt/conda/lib/python3.8/site-packages/vllm/worker/worker.py", line 166, in init_device
(VllmWorkerProcess pid=8387) ERROR 11-26 09:53:04 multiproc_worker_utils.py:229]     torch.cuda.set_device(self.device)
(VllmWorkerProcess pid=8387) ERROR 11-26 09:53:04 multiproc_worker_utils.py:229]   File "/opt/conda/lib/python3.8/site-packages/torch/cuda/init.py", line 420, in set_device
(VllmWorkerProcess pid=8387) ERROR 11-26 09:53:04 multiproc_worker_utils.py:229]     torch._C._cuda_setDevice(device)
(VllmWorkerProcess pid=8387) ERROR 11-26 09:53:04 multiproc_worker_utils.py:229]   File "/opt/conda/lib/python3.8/site-packages/torch/cuda/init.py", line 300, in _lazy_init
(VllmWorkerProcess pid=8387) ERROR 11-26 09:53:04 multiproc_worker_utils.py:229]     raise RuntimeError(
(VllmWorkerProcess pid=8387) ERROR 11-26 09:53:04 multiproc_worker_utils.py:229] RuntimeError: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method

I've tried uninstall pynvml, add "multiprocessing.set_start_method('spawn')" or "torch.multiprocessing.set_start_method('spawn')", it didn't work as well.
I'm using
NOTE:

I know the import line is unnecessarily, but it's really weird that an import line could leads to this error (at least to me)
I am not sure whether this issue is supposed to be raised in vllm project or qwen,or in transformers project, sorry if I am wrong but it is the llm=.... line that raise error and that's why I choose here.

Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

In most cases, this issue occurs because CUDA has already been initialized before the LLM initialization. You can debug it by checking if there's GPU usage after running from transformers import Qwen2VLForConditionalGeneration


Review Docker image: fileenv, entrypoint

Closes: #381
Closes: jeanpommier/ldap2pg#1
cc @jeanpommier

Hi Etienne,
Looks very neat.
Thanks !


Incorrect token targeted when using ci" or di" at the start of a string

Pretty minor bug but it seems that sometimes when executing ci" or di" (and related commands) at the start of a string (e.g. when your cursor is on the first " char), it targets the wrong token if that same char (") exists earlier in the line.
See example gif below. Notice that when executing di" at the start of "cat" it deletes the chars before it until the next quote rather than inside it (e.g. cat). Doing so at the start of "animal" here works as expected because there is no quote behind it. Also notice that doing this command in the middle of the string works as expected:

Note that the expected result is to delete everything inside the string here as it does in Vim.

@nightwing have you had the chance to take a look at this?


Hide deprecation messages when debugging node 8 with inspector protocol

These were added late before the Node 8 release:

Still having the warning as of Node 8.7.0 and VS Code 1.17.1:
Debugger listening on ws://<IP_ADDRESS>:23988/5b5294e3-fe2b-4f1c-9045-1998fd739672
For help see https://nodejs.org/en/docs/inspector
Debugger attached.
(node:6044) [DEP0062] DeprecationWarning: `node --inspect --debug-brk` is deprecated. Please use `node --inspect-brk` instead.

Do you have runtimeExecutable set in your launch config? If so it still uses --inspect --debug-brk. If not, can you set "trace": true and upload the log here?

@roblourens I do have runtimeExecutable set in my launch config. Is there a way to avoid passing --debug-brk for such a case?

Well, not at the moment. it looks like you're using the integratedTerminal but the message should still be cleaned up if you use the debug console instead.
This is annoying but I support versions of node that don't support --inspect-brk, and I don't want to spawn the runtimeExecutable to check the version, and I don't want to add yet another setting for it.

@roblourens As of Node.js 8.7.0 the problem is that execution stops on every single launch, which is very inconvenient for debug - change code - restart loop. That is the real reason in need of omitting --debug-brk option.

Hm, it should auto-continue, unless you have stopOnEntry set in your launch config.

Nope, i don't have stopOnEntry in my launch config. Should I fill a new issue for that? Here's how my launch.config looks like:
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch via nodemon",
            "type": "node",
            "request": "launch",
            "protocol": "inspector",
            "cwd": "${workspaceRoot}",
            "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/nodemon",
            "runtimeArgs": [
                "--exitcrash",
                "--config", "${workspaceRoot}/nodemon.json",
                "--exec", "${workspaceRoot}/node_modules/.bin/ts-node", "${workspaceRoot}/src/server.ts"
            ],
            "restart": true,
            "console": "integratedTerminal",
            "internalConsoleOptions": "openOnFirstSessionStart",
            "skipFiles": [
                "node_modules/**",
                "<node_internals>/**"
            ]
        },
        {
            "name": "Attach to node",
            "type": "node",
            "request": "attach",
            "protocol": "inspector",
            "restart": true,
            "port": 5858,
            "skipFiles": [
                "node_modules/**",
                "<node_internals>/**"
            ]
        }
    ]
}

If it start on the first line even though you don't have stopOnEntry set, please set "trace": true, run again, and upload the log here.

It waits 1s for the initial pause event, and one possibility is that it's taking longer than that, with ts-node and nodemon involved. Does it seem like it takes longer than 1s to start?
If not, can you set "trace": true, run again and upload the log?

@roblourens I'm not sure about timing. Maybe it's barely greater 1.0 second. The issue being reproduced on 2 windows machines and 1 macOS machine. Node.js 8.7.0, VS Code 1.17.1.
Logs: vscode-node-debug2.txt
Repo: node-typescript-vscode
Screenshot (what I see right after the start):

Ah, this seems exactly the same as https://github.com/Microsoft/vscode-node-debug2/issues/144. Let's continue there. I may just try to increase the timeout again. Not sure why Node 8.7 would be slower than 7.x


[Hub Generated] Review request for Microsoft.ContainerService/aks to add version preview/2024-03-02-preview

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

[!NOTE]
As of January 2024 there is no PR assignee. This is expected. See https://aka.ms/azsdk/pr-arm-review.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Click here to see the details of Step 1, Breaking Changes review
If you are in purview of Step 1 of the diagram, follow the Breaking Changes review process.
IMPORTANT! This applies even if you believe your PR was mislabeled, for any reason, including tool failure.

Click here to see the details of Step 2, ARM review
See https://aka.ms/azsdk/pr-arm-review.

 Click here to see the diagram footnotes
Diagram footnotes
[1] See ARM review queue (for PR merge queues, see [2]).
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
The ARM reviewer on-call engineer visits the merge queue twice a day, so the approximate ETA for merges is 12 - 24 hours.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[x] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with PR workflow diagram Step 2 (ARM review), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

For the failure in Swagger Avocado,

openShiftManagedClusters related API paths from aks/preview/2019-10-27-preview/openShiftManagedClusters.json are deprecated
fleets related API paths from aks/preview/2022-09-02-preview/fleets.json are supported, but are published as a separate SDK, see specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/readme.md

    "operationId": "LoadBalancers_Rebalance",

https://github.com/Azure/azure-openapi-validator/blob/main/docs/post-operation-id-contains-url-verb.md

Refers to: specification/containerservice/resource-manager/Microsoft.ContainerService/aks/preview/2024-03-02-preview/managedClusters.json:3836 in 19d06fc. [](commit_id = 19d06fcc530ac8b83e6452a26db4aa2e7a0cbbee, deletion_comment = False)

    }

Please review all the newly added properies in this PR and see if these can be represented as enums instead of booleans :
https://github.com/Azure/azure-openapi-validator/blob/main/docs/enum-instead-of-boolean.md

Refers to: specification/containerservice/resource-manager/Microsoft.ContainerService/aks/preview/2024-03-02-preview/managedClusters.json:8826 in 19d06fc. [](commit_id = 19d06fcc530ac8b83e6452a26db4aa2e7a0cbbee, deletion_comment = False)

    "allowServicePlacement": {

enum instead of boolean

Refers to: specification/containerservice/resource-manager/Microsoft.ContainerService/aks/preview/2024-03-02-preview/managedClusters.json:9875 in 19d06fc. [](commit_id = 19d06fcc530ac8b83e6452a26db4aa2e7a0cbbee, deletion_comment = False)

Can we make those checks in the check-in pipeline? This will save a lot of engineering time.

    }

Please review all the newly added properies in this PR and see if these can be represented as enums instead of booleans :
https://github.com/Azure/azure-openapi-validator/blob/main/docs/enum-instead-of-boolean.md
Refers to: specification/containerservice/resource-manager/Microsoft.ContainerService/aks/preview/2024-03-02-preview/managedClusters.json:8826 in 19d06fc. [](commit_id = 19d06fc, deletion_comment = False)

hi,
for advanced networking.observability
we have discussed that boolean is the better route for our api. We are using enablement field to turn on/off our addon and we are tying our features into the aks sku tiers - different aks skus = different features. I don't see any value in changing the boolean to an enum here.
we also had some discussion here: Advanced Networking - Overview (azure.com)

    }

Please review all the newly added properies in this PR and see if these can be represented as enums instead of booleans :
https://github.com/Azure/azure-openapi-validator/blob/main/docs/enum-instead-of-boolean.md
Refers to: specification/containerservice/resource-manager/Microsoft.ContainerService/aks/preview/2024-03-02-preview/managedClusters.json:8826 in 19d06fc. [](commit_id = 19d06fc, deletion_comment = False)

hi, for advanced networking.observability we have discussed that boolean is the better route for our api. We are using enablement field to turn on/off our addon and we are tying our features into the aks sku tiers - different aks skus = different features. I don't see any value in changing the boolean to an enum here. we also had some discussion here: Advanced Networking - Overview (azure.com)

I also don't see the benefit of using string to replace boolean. In this way I need an extra conversion from bool to string in our code and this is not meaningful. Boolean appears to be a more concise choice for me.

    "operationId": "LoadBalancers_Rebalance",

https://github.com/Azure/azure-openapi-validator/blob/main/docs/post-operation-id-contains-url-verb.md
Refers to: specification/containerservice/resource-manager/Microsoft.ContainerService/aks/preview/2024-03-02-preview/managedClusters.json:3836 in 19d06fc. [](commit_id = 19d06fc, deletion_comment = False)

Can you suggest a operation id? Another error would be hit if change to LoadBalancers_RebalanceLoadBalancers.

They likely want it to be called ManagedCluster_RebalanceLoadBalancers because it's hanging off of the managedCluster rather than a LoadBalancer?

They likely want it to be called ManagedCluster_RebalanceLoadBalancers because it's hanging off of the managedCluster rather than a LoadBalancer?

This can work

    "operationId": "LoadBalancers_Rebalance",

Try matthchr's suggested operationId

In reply to:<PHONE_NUMBER>

Refers to: specification/containerservice/resource-manager/Microsoft.ContainerService/aks/preview/2024-03-02-preview/managedClusters.json:3836 in 19d06fc. [](commit_id = 19d06fcc530ac8b83e6452a26db4aa2e7a0cbbee, deletion_comment = False)

    }

Please review all the newly added properies in this PR and see if these can be represented as enums instead of booleans :
https://github.com/Azure/azure-openapi-validator/blob/main/docs/enum-instead-of-boolean.md
Refers to: specification/containerservice/resource-manager/Microsoft.ContainerService/aks/preview/2024-03-02-preview/managedClusters.json:8826 in 19d06fc. [](commit_id = 19d06fc, deletion_comment = False)

hi, for advanced networking.observability we have discussed that boolean is the better route for our api. We are using enablement field to turn on/off our addon and we are tying our features into the aks sku tiers - different aks skus = different features. I don't see any value in changing the boolean to an enum here. we also had some discussion here: Advanced Networking - Overview (azure.com)

I also don't see the benefit of using string to replace boolean. In this way I need an extra conversion from bool to string in our code and this is not meaningful. Boolean appears to be a more concise choice for me.

Standard guidance is: replace boolean/switch properties with a more meaningful enum whenever possible.
A boolean will forever have two valid values (true or false). A string enum type is always preferred. Also, properties should always provide better values just than True and False. For example two switches "isTypeA" and "isTypeB" should be replaced with one enum "type": [A, B, DefaultType]. Enums are always a more flexible and future proof option because they allow additional values to be added in the future in a non-breaking way, e.g. [Enabled, Disabled, Suspended, Deallocated].
Note: do NOT define a 'boolean enum' with two values 'True and False'. This might be easier to 'extend' in terms of types, but semantically its confusing, and no better than a boolean.
Since its a strong suggestion, please review and confirm from your side.

you can always compare enum to enum in code

    }

Please review all the newly added properies in this PR and see if these can be represented as enums instead of booleans :
https://github.com/Azure/azure-openapi-validator/blob/main/docs/enum-instead-of-boolean.md
Refers to: specification/containerservice/resource-manager/Microsoft.ContainerService/aks/preview/2024-03-02-preview/managedClusters.json:8826 in 19d06fc. [](commit_id = 19d06fc, deletion_comment = False)

hi, for advanced networking.observability we have discussed that boolean is the better route for our api. We are using enablement field to turn on/off our addon and we are tying our features into the aks sku tiers - different aks skus = different features. I don't see any value in changing the boolean to an enum here. we also had some discussion here: Advanced Networking - Overview (azure.com)

I also don't see the benefit of using string to replace boolean. In this way I need an extra conversion from bool to string in our code and this is not meaningful. Boolean appears to be a more concise choice for me.

Standard guidance is: replace boolean/switch properties with a more meaningful enum whenever possible. A boolean will forever have two valid values (true or false). A string enum type is always preferred. Also, properties should always provide better values just than True and False. For example two switches "isTypeA" and "isTypeB" should be replaced with one enum "type": [A, B, DefaultType]. Enums are always a more flexible and future proof option because they allow additional values to be added in the future in a non-breaking way, e.g. [Enabled, Disabled, Suspended, Deallocated]. Note: do NOT define a 'boolean enum' with two values 'True and False'. This might be easier to 'extend' in terms of types, but semantically its confusing, and no better than a boolean.
Since its a strong suggestion, please review and confirm from your side.

you can always compare enum to enum in code

I see the value of enum overall, but for advanced network observability,  we only want to use this field to turn our feature on or off. The different features will be determined from ask cluster sku, so I don't think this feature will have any value from updating it to enum as stated.
If this is blocking the api, then we can update it, but we don't plan on having other states such as "deallocated" or "suspended". Pretty much we only want a simple on/off for observability

For a property with only two possible values, a boolean data type is the most suitable choice. Changing it to a string enum would introduce unnecessary complexity.

/pr RequestMerge

@ramoka178 want to mark this PR approved based on your review or does it need further review?


Remove IndexDao dependency from RedisExecutionDAO

Hey,
I was going through RedisExecutionDAO and it seems that in a lot of functions IndexDao is called either to index or get values. I am not able to understand why would we not have such call in a layer above this i.e. ExecutionService.java. The issue is that it is misleading, when I do a executionDAO.createWorkflow(wf); it writes to both Redis and internally indexes the workflow using an index dao. Also, if I want to switch-off indexing, I will have to touch the RedisExecutionDao and all other DAOs that internally call index().
Also, it will enable us to easily build features like asyncIndexer and completely switching off Indexing (maintaining one less component in production, if I am fine with giving up some features) as requested in a few tickets.
@cyzhao @v1r3n @apanicker-nflx @kishorebanala Would love to know your views on the same. Let me know if I missed something here.
P.S : I will be willing to write a design change proposal for review and submit a PR if this is something that is aligned with the overall goal for conductor.

@mudit3774 I agree, we wanted to change this as well but didn't get a chance yet, you are welcome to submit a PR.

@cyzhao : Thanks! I will try to pick this up in the second half of August.
I wanted to discuss a few design changes :

Some DAO functions completely depend on indexDAO, specifically : addTaskExecLog, getWorkflowsByCorrelationId and addMessage etc. I am assuming, we can live with NOOP in these methods unless we plan to implement them at a later stage.

Would it make sense to pull out an archived service to interact with archived workflows using indexDAO ?

Also, I will break it down into smaller changes and open independent tickets.

@mudit3774  your plan sounds good to me, please proceed.


Open from local file

Hey,
is there a way to use your package with a local file?
I tried to use resource_path('apidoc/openapi.yaml') in your config and it seems that is doesnt work.

If I let your package on default, the default documentation looks like this:

Other than this... Thank you for your take on this, as I love Stoplight to design my APIs and only need a way to show them on my site.

This is unplug CDN returning a 404 for the style script, I have passed this onto Stoplight support now, and should receive an answer soon, so I can either publish an update or find a fix.
I noticed on twitter you said you were using PHP 7, I will push an update to allow PHP 7 also, as there isn't too much going on that "needs" PHP8 - it is just a general practice I follow

@K2ouMais Also, having just tested - the path to the file needs to be a URL that can be reached by the browser. I would recommend:
Route::get('openapi', function () {
    return response()->file(config('stoplight.openapi.path));
})->name('openapi');

Then in your ENV you can add the correct path, or override the configuration.

Are you getting the same CDN problem. I am asking because I wanted to test your package at my working place and the problem could be on my side and eventually I have to ask our administrators to open the firewall to the CDN.
Thank you for all the effort.

Thank you for supporting PHP 7.4... I think there will be another release. I reported some bugs to the stoplight elements repository and these were already merged.


cleanup: simplify parser_test

parser_test only needed the directory-names for the tests to run.
This replaces f.Readdir() with f.Readdirnames() to only return the names.

LGTM (not a maintainer approval)

LGTM

LGTM


Issue installing from pip

I get the following error:
/usr/local/lib/python3.11/site-packages/pydantic/_internal/_config.py:341: UserWarning: Valid config keys have changed in V2:

'allow_population_by_field_name' has been renamed to 'populate_by_name'
'smart_union' has been removed
warnings.warn(message, UserWarning)
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/fastavro/read.py", line 2, in
from . import _read
File "fastavro/_read.pyx", line 10, in init fastavro._read
File "/usr/local/lib/python3.11/lzma.py", line 27, in
from _lzma import *
ModuleNotFoundError: No module named '_lzma'

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/data/PycharmProjects/Dignity/main.py", line 10, in
from Utilities.Memory import Memory
File "/home/data/PycharmProjects/Dignity/Utilities/Memory.py", line 4, in
from Utilities.Journal import Journal
File "/home/data/PycharmProjects/Dignity/Utilities/Journal.py", line 7, in
import agentforge.tools.SemanticChunk as Chunker
File "/home/data/PycharmProjects/AgentForge/src/agentforge/tools/SemanticChunk.py", line 1, in
from semantic_chunkers import StatisticalChunker
File "/usr/local/lib/python3.11/site-packages/semantic_chunkers/init.py", line 1, in
from semantic_chunkers.chunkers import (
File "/usr/local/lib/python3.11/site-packages/semantic_chunkers/chunkers/init.py", line 1, in
from semantic_chunkers.chunkers.base import BaseChunker
File "/usr/local/lib/python3.11/site-packages/semantic_chunkers/chunkers/base.py", line 5, in
from semantic_router.encoders.base import BaseEncoder
File "/usr/local/lib/python3.11/site-packages/semantic_router/init.py", line 1, in
from semantic_router.hybrid_layer import HybridRouteLayer
File "/usr/local/lib/python3.11/site-packages/semantic_router/hybrid_layer.py", line 6, in
from semantic_router.encoders import (
File "/usr/local/lib/python3.11/site-packages/semantic_router/encoders/init.py", line 7, in
from semantic_router.encoders.cohere import CohereEncoder
File "/usr/local/lib/python3.11/site-packages/semantic_router/encoders/cohere.py", line 4, in
import cohere
File "/usr/local/lib/python3.11/site-packages/cohere/init.py", line 155, in
from .aws_client import AwsClient
File "/usr/local/lib/python3.11/site-packages/cohere/aws_client.py", line 16, in
from .client import Client, ClientEnvironment
File "/usr/local/lib/python3.11/site-packages/cohere/client.py", line 21, in
from .utils import wait, async_wait, merge_embed_responses, SyncSdkUtils, AsyncSdkUtils
File "/usr/local/lib/python3.11/site-packages/cohere/utils.py", line 9, in
from fastavro import parse_schema, reader, writer
File "/usr/local/lib/python3.11/site-packages/fastavro/init.py", line 47, in
import fastavro.read
File "/usr/local/lib/python3.11/site-packages/fastavro/read.py", line 4, in
from . import _read_py as _read  # type: ignore
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/fastavro/_read_py.py", line 9, in
import lzma
File "/usr/local/lib/python3.11/lzma.py", line 27, in
from _lzma import *
ModuleNotFoundError: No module named '_lzma'
Seems like maybe something changed on cohere?

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

Lol. Put it on github. I'm not downloading an encrypted zip. You sus af

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx


The type of message is not explicit

Hello
I was looking in the doc if there was any method that would allow to explicitly extract the type of message.
I get very confused when capturing a Media type message, since a Media type message can be an Image, a video, an audio, etc.
When processing these types I can't capture the specific type of message
I would really appreciate your help with this issue Alex Albarca @aalbarca

Hi!
This is not a issue. Please request a feature on Discussions forum.
Duplicated https://github.com/netflie/whatsapp-cloud-api/discussions/92


WebkitGTK issue with libmanette dependency

Bug description
I am trying to compile Webkitgtk for a Wayland / Weston image for the iMX8X chipset. When trying to compile, CMake searches for a dependency for libmanette. This problem appears to be a CMake issue that was patched in later versions, see here for more info.
The Yocto platform is Dunfell, and the webkitgtk version is 2.32.1 from the dunfell branch
How To Reproduce
On a Wayland / Weston build (no X11 or Qt5), add webkitgtk via IMAGE_INSTALL. I can provide the board support tdx-reference-minimal-image.bb if needed.  My target does not require gamepads, so the work around was to set this variable to off using:
diff --git a/recipes-browser/webkitgtk/webkitgtk_2.32.1.bb b/recipes-browser/webkitgtk/webkitgtk_2.32.1.bb
index 252f5ff..1181848 100644
--- a/recipes-browser/webkitgtk/webkitgtk_2.32.1.bb
+++ b/recipes-browser/webkitgtk/webkitgtk_2.32.1.bb
@@ -72,6 +72,7 @@ EXTRA_OECMAKE = " \
                  -DENABLE_GTKDOC=OFF \
                  -DENABLE_MINIBROWSER=ON \
                  -G Ninja \
+		 -DENABLE_GAMEPAD=OFF \
                 "

 # Javascript JIT is not supported on powerpc
@@ -115,3 +116,4 @@ do_install_append() {
 FILES_${PN} += "${libdir}/webkit2gtk-4.0/injected-bundle/libwebkit2gtkinjectedbundle.so"
 FILES_${PN}-dbg += "${libdir}/webkit2gtk-4.0/injected-bundle/.debug/libwebkit2gtkinjectedbundle.so"
 FILES_${PN}-dbg += "${libdir}/webkitgtk/webkit2gtk-4.0/.debug/*"
+

Additional Information
I also ran into this issue and resolved by modifying the file as recommended by @adahl5.

This issue has been addressed already on the master branch with a packageconfig option that you can enable or disable. I have submitted a PR here for the dunfell branch: https://github.com/Igalia/meta-webkit/pull/453


feat(members): add member to a body. Fixes MEMB-794

added a modal to add members to a body, added a button that is displayed if you have permissions to do so. It's only accessible if you can see members globally (global:view:member), so admins only.

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Cannot read property 'Order' of undefined from shopify-express sdk

Issue summary

@shopify/shopify-api version:
Node version: 6.2.0
Operating system: macos

// Paste any relevant logs here

Expected behavior
I can use shopify.rest.Order.all to request order list
Actual behavior
it return UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'Order' of undefined from shopify-express sdk

@schapicool Please share how you are configuring the API ... this seems to indicate that the shopify object isn't being configured with the REST resource objects.


Inconsistency with bundle update (major vs minor/patch)

Here's a test case aiming to illustrate the inconsistency with bundle update foo with different --major/minor/patch. The only available gem versions are patches releases, so all three options should all behave the same but they don't for the minor and patch options.
I feel this inconsistency has to be bug. For sure, it makes it impossible to understand what is supposed to be going on.
Moved from https://github.com/chrismo/bundler-cases/issues/6

FWIW, I strongly disagree with bundler update foo changing needlessly bar's version (see #2016), so I'm kind of shooting myself in the foot here by pointing this out 😢
My christmas wish is that bundle update does change whatever you want, but that bundler makes an incompatible change for bundle update a_particular_gem and mimicks the new behavior of --minor/patch instead of bringing those inline with the current behavior.
If I can't get my christmas wish, I am still hoping for a way to do bundler update foo --whatever-options-you-d-like-me-to-type that won't change bar (no matter what / unless necessary, pick your favorite).

@marcandre that is my understanding of our actual plan for Bundler 2.0: make the logic of --minor and --patch the default. We're not sure if we'll manage to ship it in time for it to be your christmas present, though. 😆

OMG! Awesome!

I think in conjunction with the desire for a --conservative flag** (great name, hate typing it - too long?) ... we can have a little 1.x cake and eat it too here.
(** https://github.com/chrismo/bundler-cases/blob/master/cases/conservative/update/conservative_like_install.rb)
Also added PR with your case => https://github.com/chrismo/bundler-cases/pull/12

ha - this may be all that's needed to fix this:
--- a/lib/bundler/definition.rb
+++ b/lib/bundler/definition.rb
@@ -103,8 +103,6 @@ module Bundler
       end
       @unlocking ||= @unlock[:ruby] ||= (!@locked_ruby_version ^ !@ruby_version)

-      @gem_version_promoter = create_gem_version_promoter
-
       current_platform = Bundler.rubygems.platforms.map {|p| generic(p) }.compact.last
       add_platform(current_platform)

@@ -112,6 +110,8 @@ module Bundler
       eager_unlock = expand_dependencies(@unlock[:gems])
       @unlock[:gems] = @locked_specs.for(eager_unlock).map(&:name)

+      @gem_version_promoter = create_gem_version_promoter
+
       @source_changes = converge_sources
       @dependency_changes = converge_dependencies
       @local_changes = converge_locals


[BUG] Endpoint 0

I'm on LInux Mint 21.3 and as I check for endpoint, I ended up with 0 and can't able to use the program. I remember AudioRelay has some instruction to create virtual speaker in order to work which you can check it HERE but I'm not sure if it applies the same for audioshare. A help is very much appreciated, thank you.

The AudioReplay use PulseAudio. Audio Share use Pipewire. It may not work normally.
Linux Mint 21 seems like using pulse audio as default audio server. Can music player work normally before you installing Pipewire? Or your PC has an embedded sound card? If not, then you need a virtual device.
Copy the below config to ~/.config/pipewire/pipewire.conf.d/audio-share-sink.conf to create a virtual sink node.
context.objects = [
    {   factory = adapter
        args = {
           factory.name     = support.null-audio-sink
           node.name        = "Audio Share Sink"
           media.class      = Audio/Sink
           object.linger    = true
           audio.position   = [ FL FR ]
           priority.session = 1009
           priority.driver  = 1009
           monitor.channel-volumes = true
           monitor.passthrough = true
        }
    }
]

Run systemctl --user restart pipewire to restart the pipewire.
Then run as-cmd -l, you will see the new endpoint.
[abc@localhost ~]$ ./audio-share-server-cmd/bin/as-cmd -l
[2024-03-17 22:46:14.563] [info] pipewire header_version: 0.3.48, library_version: 0.3.67
endpoint_list:
        * id: 30   name: Audio Share Sink
total: 1

Then the as-cmd -b will work normally.

The AudioReplay use PulseAudio. Audio Share use Pipewire. It may not work normally.
Linux Mint 21 seems like using pulse audio as default audio server. Can music player work normally before you installing Pipewire? Or your PC has an embedded sound card? If not, then you need a virtual device.
Copy the below config to ~/.config/pipewire/pipewire.conf.d/audio-share-sink.conf to create a virtual sink node.
context.objects = [
    {   factory = adapter
        args = {
           factory.name     = support.null-audio-sink
           node.name        = "Audio Share Sink"
           media.class      = Audio/Sink
           object.linger    = true
           audio.position   = [ FL FR ]
           priority.session = 1009
           priority.driver  = 1009
           monitor.channel-volumes = true
           monitor.passthrough = true
        }
    }
]

Run systemctl --user restart pipewire to restart the pipewire. Then run as-cmd -l, you will see the new endpoint.
[abc@localhost ~]$ ./audio-share-server-cmd/bin/as-cmd -l
[2024-03-17 22:46:14.563] [info] pipewire header_version: 0.3.48, library_version: 0.3.67
endpoint_list:
        * id: 30   name: Audio Share Sink
total: 1

Then the as-cmd -b will work normally.

I actually have an embedded sound card, and seems like I have pipewire installed as well, do I need to do something here like removing pulseaudio or something? sorry kinda noob..

Run pactl to check the pipewire.

Run pactl info to check the pipewire.

seems like it's using pulseaudio :/

Follow the instrunction of https://linuxgenie.net/install-pipewire-on-linux-mint-21/.

Follow the instruction of https://linuxgenie.net/install-pipewire-on-linux-mint-21/.

I did manage to create a virtual speaker and enable pipewire, however, I cannot play any audio lol.

You must configure pipewire properly. Did you disable the pulse audio?

Follow  the instructions, you can't remove pulse audio directly. Because other system  components may require it.

Follow the instructions, you can't remove pulse audio directly. Because other system components may require it.

Yeah, I just did, it's working now, thanks...


As a developer, I need to fix the location and styling of the new experimental "linked data" block in the resource viewer

Where:
In the Resource viewer there is currently (in the Test version) a new experimental block for simulating how working with linked data would be. To see where the block is, look at Image 1.
What the problem is:
It is an experimental feature which occupies a large part of the Resource viewer page. Users may be confused about what it does. We would like to add it as an experimental feature a bit less prominent and more styled.
Approach:
Do very small fixes to solve only styling issues. The longer term solution will come with the redesign of the Resource viewer (separate project for 2019).
Acceptance criteria:

[x] Remove the current "linked data" block from the right side
[x] Place the current "linked data" block on the left side (see Image 2):
-- [ ] Create a new collapsible block called "Related content (experimental)"
-- [ ] Move the current "All data" block to a separate collapsible block, and place it at the end
[x] Change the "Linked data" block in the following aspects (see image 3):
[x] Title: rename the block from "Find related content based on these properties" to "Search for related content"
[x] Order all the metadata fields alphabetically
[x] Put the fields and their content in a sort of table style. That is, instead of having the field name on top and the content below, put the content of the field in front of the name of the field (as in Image 3).
[x] Add only the short name of the name of the metadata field, and add a tooltip to the field name with the full name of the field (as it is done in other parts of the Media Suite)

IMAGES
Image 1: where the block is

Image 2: How the blocks should look like when the user opens the Resource viewer

Image 3: How the new block should look like

@lilimelgar looks ok. This is an easy fix and should be done on Monday one day before the soft-launch

@lilimelgar @jblom
Last (pending) task for this issue (move All Data section to separated block) is done in a new branch since the original is already merged into master.
Branch: labo-components
task/#218-move-all-data-to-separated-block
The block is displayed folded as default in the same fashion as the 'experimental block'.
@lilimelgar : Please check it in that branch (unless merged before you can do it) and close issue if done.

Tested in branch task/#218-move-all-data-to-separated-block.
@lilimelgar : Pending: it was not possible to test with Desmet paper collection, since it doesn't work in this branch.
@avlisodraude, pending to check:

[ ] in the KB newspapers the blocks show in a different order
[ ] in the Open beelden collections the blocks show in a different order and the All data is not closed
[ ] in the OH collection the blocks show in a different order and the All data is not closed
[ ] in the radio collection the blocks show in a different order and the All data is not closed
[ ] in the television collection the blocks show in a different order and the All data is not closed

@lilimelgar Comment checked and it works ok.
Please test and comment/close the issue :-)

I tested this with all collections, it's all OK, except that I could not test the Desmet Film collection since it doesn't work properly in this branch. @avlisodraude Could you please check this with that collection to see why it's not loading?

@lilimelgar @jblom  : The issue is related to changes in Desmet Film Collection config (well, actually the data changed). It will be tested when the updated config file is available.

@jblom Is the Config file updated for testing this one?

@lilimelgar check the oteamdevel channel on Slack, I posted the mappings there

Tested in branch task/#218-move-all-data-to-separated-block. There seems to be a problem in this branch which doesn't allow me checking the resource viewer of the Desmet film collection. Since it's related to highlights, @jwassenaarbg: could you please check what the problem is?


should reductions return dense arrays?

Reductions on  SparseMatrixCSC return dense arrays. Should the same happen for GBMatrix?
Current behavior is
julia> using SparseArrays, SuiteSparseGraphBLAS

# dense matrices from sparse arrays' reductions for base types
julia> sum(sprand(5,5,0.1); dims=1)
1×5 Matrix{Float64}:
 0.0  0.0  0.623837  0.0  0.751621

julia> sum(sprand(5,5,0.1); dims=2)
5×1 Matrix{Float64}:
 0.0
 1.303100775231686
 0.09521454262437534
 0.34834841964204744
 1.4844961238290506

# sparse matrices from sparse arrays' reductions for this repo

julia> sum(GBMatrix(sprand(5,5,0.1)); dims=2)
5x1 GraphBLAS double matrix, bitmap by col
  1 entry, memory: 256 bytes

    (4,1)    0.9055

julia> sum(GBMatrix(sprand(5,5,0.1)); dims=1)
5x1 GraphBLAS double matrix, bitmap by col
  3 entries, memory: 256 bytes

    (2,1)    0.377595
    (3,1)    0.114248
    (5,1)    0.18736

It's not possible. If there's a missing row or missing column (which is totally possible per the spec) it is required to be sparse.  If a (subgraph) has no edges for that node then we have to return missing or some other "no-value" sentinel.
If there are no missing entries, then it will return a "dense" GBMatrix. That can then be unpacked or converted by a memcopy to a Matrix.
I'm working on a new library that should support something like this, but it's a ways off. And we still want to support the graph method.
More generally if you're asking about Matrix outputs specifically, that's a limitation right now that might be overcome in the future but I can't make any guarantees.

The semantics of GBMatrix seems not to be entirely consistent with that of an abstract array. GBMatrix chooses to ignore the fill value in reductions:
julia> x = GBMatrix([1,2], [2, 3], [1,2], fill=100000)
2x3 GraphBLAS int64_t matrix, bitmap by row
  2 entries, memory: 264 bytes

    (1,2)   1
    (2,3)   2

julia> x[1,1]
100000

julia> sum(x)
3

and so we have this weird thing that manually computing the sum with a for loop gives a different value compared to sum(x). This doesn't feel very safe.

Yes, so there's a significant issue here I've yet to resolve. The main problem is that fill isn't a construct in GraphBLAS, it's my own addition to make things more AbstractArray like as much as possible.
This is solvable for reduce pretty trivially, and I can do that, just counting the number of non-fills and doing a simple multiply is fine.
But then you get to multiplication and I don't have a great answer. Do you think A * B should account for arbitrary fill value? This gets into the weeds when you use various semirings. If I do take the fill value into account then I will be arbitrarily densifying a significant fraction of the time, pretty much whenever the fill value isn't 0, NoValue/missing, or [-]Inf.

Keep in mind also, the use of this library as a SparseArray is mostly secondary to its use for graph algorithms. The fill was intended to try and bridge the gap between a SparseMatrixCSC and a GBMatrix as much as possible, but only in a way that doesn't compromise its use for graphs.


Add with_alpha and multiply_alpha on DynamicColor

If the alpha channel is missing, these operations will do nothing.
Additionally, mark some functions on Missing as const.

For DynamicColor::multiply_alpha, I think that if the alpha is missing (and therefore 0.0), then the alpha remains missing.
But the interaction between that and DynamicColor::premultiply_split is not clear to me, since it treats a missing alpha as being opaque:
fn premultiply_split(self) -> ([f32; 3], f32) {
    // Reference: §12.3 of Color 4 spec
    let (opaque, alpha) = split_alpha(self.components);
    let premul = if alpha == 1.0 || self.missing.contains(3) {
        opaque
    } else {
        self.cs.layout().scale(opaque, alpha)
    };
    (premul, alpha)
}

So for the purposes of `multiply_alpha`, would we set it to not be missing and then set the alpha to the factor?

Same question for `with_alpha` where we're setting the alpha. Would we leave it missing or set it and clear the missing flag?

There's no code that clears missing flags, so maybe I'm wrong here and we should document that both things effectively do nothing when the alpha is explicitly missing?

We need multiply_alpha for supporting using DynamicColor with peniko::ColorStop / peniko::Gradient.

I've answered my own question for now by leaving the color unchanged when modifying the alpha channel if the alpha channel is missing.
This is what would have happened if one had done the same operation via DynamicColor::map.


1635 plug in validator tools

There's a couple TODOs that might need discussion. I'm also happy to refactor the else if logic in the validateConfigPaths() function to a switch statement if people think that might make it more readable.


Scrolling and vim

The pdf.js shortcuts to scroll to the next and the previous page are

next page: n, j and space bar,
previous page: p, k and shift+space bar.

Desired behavior:
Instead of having triple key combinations for scrolling the page, the shortcuts for simple (but more important) line scrollings are missing. It is desirable (and would be very useful) to adopt the vim-like behavior:

cursor down: j (line scrolling, same as cursor ↑),
cursor up: k (line scrolling, same as cursor ↓).

Please, also see Evince or Zathura. Both use this desired behavior.
Thank you.

Duplicate of #7019

pdf.js is integrated in various other programs, one example is LaTeX Workshop.
For this – and other reasons – it would really be important to fix this issue, as it breaks the workflows.
Thanks again.


UI : Added support for special character for Glossary

Describe your changes :

Issue : #9151
Restricted special character for Glossary and Term
Only Alpha Numeric with space is allowed

Type of change :

[x] Bug fix
[x] Improvement

Frontend Preview (Screenshots) :

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers
@open-metadata/ui

@chirag-madlani @Sachin-chaurasiya Change updated!


Reorg and refactor code around Blob abuse

Continuation of #1647. In #1647, I said the prevalent abuse of Blob (which is not much different from an all-consuming Object in many contexts) is to wrap anything in a Blob only for the sake of writing it to an output stream or compute a digest, which is an unnecessary and convoluted round-trip and making the target invisible underneath Blob.
Another complexity that hurt readability (to me at least) was the similarities between WriterBlob, BlobWriter, and Blob. Blob and WriterBlob look very similar,
public interface Blob {
  BlobDescriptor writeTo(OutputStream outputStream) throws IOException;
}

public interface BlobWriter {
  void writeTo(OutputStream outputStream) throws IOException;
}

but yet, you create a Blob (which is actually WriterBlob) out of BlobWriter
Blob writerBlob = Blobs.from(blobWriter);

and WriterBlob.writeTo() makes use of blobWriter.writeTo(). Before someone becomes familiarized with the code, all this will sound pretty confusing to them. With the Blob abuse I said at the top, this is aggravating.
Some highlighted changes:

Instead of going "something --> Blob.from(something) --> blob.writeTo()" to compute a digest or write to an output stream, I introduced DigestUtil to do it directly without the abuse.
Decoupled Blob from JsonTemplateMapper. Now JSON-related classes sit below Blob in the dependency graph.
Added JsonBlob. This makes sense because Blob sits above JsonTemplate.
Renamed BlobWriter to WritableContents, and moved it to the hash package that sits below Blob.
All Blob.writeTo() methods simply and consistently delegate to DigestUtil.computeDigest(). This resulted in removing BlobDescriptor.fromPipe(), which I think was not named or placed nicely, hose code is also duplicated some Blob.writeTo() method.
BlobDescriptor is merely a holder of (size, digest).

Another thing to note is that, there's no toBlob() functions anymore after #1647 and this. All blobs are constructed through Blobs.from().

For some unknown reason, compilation always fails on Kokoro MacOS with lots of NoClassDefFoundError and ClassNotFoundException. So weird.

It also looks like installing the plugin for integration tests is failing too?

Let me close this and reopen another one.


Implement --pid and SIGHUP

Hi guys
Thanks for having created granian, it's a great thing!
There's of course always potential for improvement, here's something I miss from gunicorn:

In gunicorn you can pass --pid which will write the gunicorn's pid (not the workers) into a simple file
Using that PID you can then send signals to the Main process, see https://docs.gunicorn.org/en/stable/signals.html
Most important one is probably HUP which will do a restart of the workers, which is very nice

Not sure I find the time to implement this, especially as I'm not a UNIX pro, but I could give it a try if no one wants to do this

Just to clarify: Granian already supports HUP signal to gracefully restart workers.
The --pid option sounds legit and easy to implement, targeting this for next minor.


Implement final feedback

Coverage increased (+8.7%) to 84.058% when pulling c1d52e2e67130b788370f9ead84207b9f5704da1 on implement-final-feedback into b77068c3f459e8d3184cf69096ada1d8b9c1caa5 on develop.


Added support for Copyright*

Similar to #3 adding support for Copyright*-files. E.g. lots of Kitware projects only have this file.

Note to self: don't delete this branch, see https://gitlab.opengeosys.org/ogs/ogs/-/issues/3415.


Avoiding FOUC in SSR — CSS doesn't update after updating its url() dependency

Describe the bug
I'm implementing my own solution for avoiding FOUC during SSR using Environment API. I'm aware that Vite doesn't offer any recommended path to do this (#16515), I tried implementing various iterations of Hiroshi's plugin linked in that issue, but I wasn't able to make it work, and I didn't need much of that logic for my app anyway.
My project has a single CSS entry point, and what I've found is that if I import it with ?url on SSR, insert the <link> tag, and HMR will just work upon updating the CSS out of the box! I don't know why 😅
However, I've now also found out that updating images imported by that CSS via url() aren't reflected in that CSS, even after a hard refresh. But I also see why — my SVG has already been inlined into the CSS, so the connection has been lost. I can work around this by forcing Vite not to inline during development via build.assetInlineLimit: () => false, now after refreshing the page I get the update, but I'd also like HMR too if possible. However, the build.assetInlineLimit thing doesn't feel like a workaround, but like a hack, I want to understand what's going on and how to do things the Vite way, whatever that might look like.
Any advice for me? Am I going about this the wrong way? Is Vite behaving here as expected by inlining the linked asset during development in SSR with the ?url import? This is something between a bug report and a question, I hope you don't mind me filing it here, it took me a long time to narrow it down.
This is a development-only issue.
Reproduction
https://github.com/silvenon/repro/tree/vite-avoiding-fouc-hmr-css-imports (note the branch name when cloning)
Steps to reproduce
# if you have GitHub CLI
# not sure if this works for cloning just that branch
gh repo clone silvenon/repro tmp-repro -- --branch vite-avoiding-fouc-hmr-css-imports
cd tmp-repro

# alternative to the above if you don't have gh or the --branch thingy doesn't work
git clone https://github.com/silvenon/repro.git tmp-repro
cd tmp-repro
git switch vite-avoiding-fouc-hmr-css-imports

npm install
npm run dev -- --open

edit the CSS file, it will get updated
edit the linked SVG file, for example change the stroke color, it won't get updated, even after a hard refresh

As you can guess, the repro (most likely) doesn't need React, I included it because it's easier for me to inline markup that way :smi
System Info
System:
    OS: macOS 15.1.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 226.16 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.18.1 - ~/.n/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 10.8.2 - ~/.n/bin/npm
    pnpm: 9.15.0 - /opt/homebrew/bin/pnpm
    bun: 1.1.29 - ~/.bun/bin/bun
  Browsers:
    Chrome: 131.0.6778.140
    Edge: 131.0.2903.99
    Safari: 18.1.1
  npmPackages:
    vite: ^6.0.3 => 6.0.3

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

It seems this happens without SSR: https://stackblitz.com/edit/vitejs-vite-nsqeovkr?file=src%2Fripples.svg&terminal=dev

Thanks for confirming and triaging!
Huh, I'm surprised to find this in regular client environment as well, I thought I tested this there and found the regular /ripples.svg link in the compiled development code, I'll let you know if I remember how I ended up with that.


Evaluate if we should generate external types

What problem does your feature solve?
Right now, UDTs can only be used if you have the host machinery available (either linked in, or by being guest). It's hard for me to imagine how this can conveniently be used to, for example, write a light-weight SDK which submits stellar-core transactions for a given contract because the SDK would itself depend on the host to convert UDTs to ScVal.
What would you like to see?
Consider whether we should generate "external" versions of the type. For example, versions that use std::vec::Vec instead of stellar_contract_sdk::Vec.
What alternatives are there?
Manually implement those types. Use the UDTs and link in the host.

I think with https://github.com/stellar/rs-stellar-token-contract/issues/45 we decided to not generate external types and just reuse SDK types. Closing because of this, but please reopen if we should still re-evaluate this.


Introduce configuration for TDD development

http://www.tdd-django-tutorial.com

Not important at this stage


fix: add "-D" for command, Update 4.styling.md

🔗 Linked issue
No issue, this is just a misunderstanding
📚 Description

When I used the CLI tool, it indicated that I should install development dependencies; however, the documentation did not mention this, which could lead to some misunderstanding.

It doesn't matter whether it's a dev dependency or not, as your package.json only contains dependencies used in development and when building. (Nuxt itself is installed as a normal dependency by default in newer versions.)
However, there is probably merit in aligning the docs with the Vue plugin's prompt.


Added support for artifacts compressed as '.gz'

Some repos compress artifacts to .gz files, which this PR adds support for:
https://github.com/evilmartians/lefthook/releases
> rokit add evilmartians/lefthook
🚀 Added version 1.7.14 of tool lefthook (took 250.96ms)
> where lefthook
C:\Users\user\.rokit\bin\lefthook.exe
> lefthook version
1.7.14

closes: #72

I will merge once CI finishes (didn't realize it needed to be approved still)!


Feat(eos_designs): IPv4/IPv6 address-family configuration for bgp_peer_groups defined under network services.

Change Summary
Provide facility to configure per address family settings for a BGP peer group defined under network services.
Related Issue(s)
Fixes #3873
Component(s) name
arista.avd.eos_designs
Checklist
Repository Checklist

[x] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation and documentation have been updated accordingly.
[x] I have updated molecule CI testing accordingly. (check the box if not applicable)

Moving to draft until comments have been addressed.


Is it possible to read the indexed data without Sourcegraph?

Hi there!
Is there a way to read the indexed data without using Sourcegraph?
I'm working on a project where the server should support LSP communication from indexed data and I was going to use LSIF until I read this post: SCIP - a better code indexing format than LSIF
The thing is that for LSIF I was going to use a tool like LSIF reader in order to get the data from the dump and then I was going to implement something to handle LSP communication.. but I'm not sure about how to do something like that using SCIP..
Is there a tool to do that?
Do I need a tool to do that?
I tried generating a dump of a javascript file using scip-typescript index --infer-tsconfig and the result wasn't human-readable
I hope it's ok to ask here, but let me know if not..
thank you :)

Hey Matias! It sounds like there are a couple of options.

Read SCIP natively in TypeScript code. You could do this using the generated TypeScript bindings, e.g. by adding a Git-based dependency in your package.json.
Convert SCIP to LSIF and use LSIF reader: It is possible to convert SCIP data to LSIF using the scip convert command.  For debugging purposes, you can inspect the index using:
# Generate index.scip using scip-typescript
protoc --decode=scip.Index -I /path/to/cloned/scip scip.proto < ./index.scip

The output of this shouldn't be consumed programmatically.

Thank you for your response! yes, it resolves my issue. I'm going with option 1 😄

I've created a PR to document this better. https://github.com/sourcegraph/scip/pull/69


[POSSIBLE BUG] Binance API Error

So I'm doing some debug work on the bot (I'm testing a new strategy) and this night it gives me the error in the picture up here; I don't think it is a matter of my own code as I have just replaced the condition in the strategy.py file and more probably this was due to a server error from Binance (but still I think it should be handled without crashing).
What do you think?
Note: The bot was running from 20:10 to 4:14 (UTC+2) that it the time when the exception happened

I don't know if this is the result. Ever since the upgrade to the .key file, I've been unable to build the images from docker-compose up --build. It gives they errors. Part of me was thinking it's a mac not reading the key correctly, but one of the .py isn't reading the key.  Could be a binance api  error as that's what I am using.

@letsautom8, can you help me with the Docker issue please? Seems having a separate .key file is causing issues with Docker. I read in the Telegram chat it may be due to a permission issue.

@xgiovi9810x, is this a persistent issue or did it just happen once?

@whittlem at least for me using Docker, it started once on the update with moving the keys from the config. I haven't been able to get it to work with docker-compose up --build since that update. I believe it was the 2.45.0 update. It doesn't appear to be persistent. I know this is the case with both the coinbasepro and binance keys.

@whittlem Nope but I didn't do a lot of real time test from that day.


[FEAT] Enhance gsheet translations pull python script

⚠ IMPORTANT: Please fill out this template to give us as much information as possible to consider/implement the feature.
Prerequisites

[ ] check this box if you have completed the following:

Reviewed the contributing guidelines and support files
Reviewed the README file for the repository you are working in
Searched for relevant instructions on our Discord server
Searched the issues of the repository you are working in to make sure one was not already filed

Summary

See this PR for more comments #691.
We needed to merge the PR to move on to integration of translations, but there's more work in enhancing the python script. Broadly,

we can provide better docs on how to create a google credentials file,
make more modular and distinct functionality such as only doing depunctuating in one method versus duplicating efforts in multiple methods, and
making the code overall less prone to bugs and errors from small changes in the gsheets

Motivation

Possible Alternatives

Additional Context

Could you show where there's multiple instances of depunctuation? I haven't touched this code too much, but definitely agree with your second point specifically. I'd be happy to make another issue out of that bullet point especially since that would be a great first issue, but I just want to be sure I have enough context 👍

Atleast in these two instances I have a depunctuate method and then I also include depunctuating functionality in another method

Could we make another issue for updating documentation as well? I could, but I'm not sure of everything that needs to go into the documentation here.
Other than that, I think we can close this issue. While it's definitely worthwhile mentioning that the code should be less prone to bugs, it's hard to quantify that into actionable items 👍

Yeah I get that. Is there a way to make related issues that are like subissues? Would it just be varying the issue title?

Within the issue you can reference this one just using #702 and it'll reference them in the conversation I believe, although I'm not sure that a new issue would need to be inherently linked just since we're ideally going to be having more discrete action items for the documentation issue

closing in lieu of issues #713 and #714


lodash/clonedeep is not recognized. Did you mean lodash.clonedeep

Currently have a problem building. Using Rollup, lodash/clonedeep references in source code are not being recognized. However lodash.clonedeep currently work.

HI Ethan,
Would you please provide more details on your flow and what library you are using?
Thanks,
Mo


Added fix to new row revert

Fixes a bug/oversight that was encountered during testing and mentioned in this issue:
Posted here for release DRI: https://github.com/microsoft/azuredatastudio/issues/24421
Will be ported into September release as this is a regression.
This should prevent the cell from moving in the new row, using the existing logic.

@smartguest can you also please add a link to the PR where this regression was introduced in the description?

and also please add a gif of the before and after behavior.


[Feature Request] Request to add support for quarto {.content-visible} and varients

When qmd needs to be rendered into formats extension not support (such as docx), I'd like to include a screenshot rather than code block. But seems like Lua script of this extension doesn't support quarto block.
Example:
::: {.content-visible when-format="pdf"}
\`\`\`pseudocode
#| label: alg-test-text-style
#| html-indent-size: "1.2em"
#| html-comment-delimiter: "//"
#| html-line-number: true
#| html-line-number-punc: ":"
#| html-no-end: false
#| pdf-placement: "htb!"
#| pdf-line-number: true

\begin{algorithm}
\caption{Test text-style}
\begin{algorithmic}
\Require some preconditions
\Ensure some postconditions
\Procedure{Test-Declarations}{}
  \State font families: {\sffamily sffamily, \ttfamily ttfamily, \normalfont normalfont, \rmfamily rmfamily.}
  \State font weights: {normal weight, \bfseries bold, \mdseries medium.
Requested Feature:

The block can still be rendered into algorithms environment when using quarto blocks.

Done with https://github.com/leovan/quarto-pseudocode/commit/47de25d153a6e4cf02bd6b17e4a572c45f1118b7, but this feature requires quarto v1.4.


Bridge: connecting wallets (bug)

As a new user that wants to use the bridge I must install 2 non-custodial wallets.

A wallet of my choice for Ethereum (MetaMask)
A wallet of my choice for Fuel (official Fuel wallet)

Upon successful installation of the wallets I would like to connect the wallets to the bridge.
In order to connect I click the respective "connect <wallet>" buttons.
The same pop-up to install wallets comes up because the site has not recognized that I have installed the wallets. In order to make the feature work as expected I had to refresh the page.
Upon refreshing the page clicking the "connect <wallet>" button prompted the pop-ups requesting connection and thus behaving as expected.

I use https://alpha.fuel.network/bridge?from=eth&to=fuel to bridge between sepolia (MetaMask) and Fuel (Fuel wallet) and it is working now.


It's a very cool tool, does it work on bash? or it depends on system(Linux/MacOS)?

It's a very cool tool, does it work on bash? or it depends on system(Linux/MacOS)?

does it work on bash?

@LiuKay I just checked to work on bash 😄
$ bash
$ echo '{"name": "ynqa"}' | jnv

Heya, I'm just testing this on my Kali system and can't seem to get it working? Any ideas?

@rxerium Probably need installation for jnv via some ways. Please see https://github.com/ynqa/jnv?tab=readme-ov-file#installation


(Proposal) Linux Support

So, I'm currently in the process of trying out Linux, and as expected, SMZ3 doesn't work! Here are some of the issues I was able to sort of identify:

Some directories used are specific to Windows, such as localappdata. Linux would need to use different directories for logs and stuff like that.
WPF is only in the .net windows SDK rather than the generic .net SDK. So, the UI just won't build at all on Linux. Technically I think it could run in Wine if there were a version that didn't go through an installer.
The speech recognition and text to speech rely on core Windows APIs that I'm not sure would even be available to Wine. I think we'd need alternative interface implementations that basically wouldn't do anything on Linux.

Of the above issues, I think the second one is probably the least trivial to overcome. I'm not sure of any good way to get around it outside of redoing the UI to not rely on WPF. The MSU Scripter was written in AvaloniaUI, and overall I thought it was quite nice and shares a lot of the same XAML as WPF. But I know there are a couple other cross platform libraries.
For overall approach, I can think of a few options.

Completely rewrite the UI for all platforms
I could create a fork for a Linux version so that this repo can stay as-is
A new project could be added with a potentially smaller UI. For example, the settings could be driven by a commandline interface, then it jumps right into the tracking window.

Just tossing this out there for discussion and thoughts.

The first step is definitely to pull out stuff from the front-end project into the other libraries.
After that, I'm not sure. I personally don't care about Linux, certainly not enough to overhaul things, but I haven't had the time and energy to work on anything myself anyway, so it doesn't matter too much to me. Ideally, the front end should only be a relatively small part of the code base anyway.
I'm not sure what the requirements for a Linux version would be, anyway. Would a pure command-line version be enough?
If not, I'm still interested in .NET MAUI, which is also based on XAML, so it should be similar enough. The last time I worked with it it worked well enough, although it lacked some things so the UI framework we use might just take some trial and error.
Not in favor of forking it just for the UI. I'd rather have it all in one place, whether it's a single multi-platform UI or multiple platform-specific UIs.

Yeah, I'll be the first to admit I'm probably the only one interested in this. Lol Maybe CPColin since I know he runs on Linux, though he's had problems getting C# apps running on Linux from my understanding (not sure if those were Linux native C# apps or Windows ones running in wine). Possibly Pink as well since she's talked about switching to Linux, but any version of Linux would most likely not have any sort of voice support, so she'd possibly still want to use the windows version for that.
Long story short, I may be the only person who would actually use it. Lol but I'm willing to be the one to do the heavy lifting, and I certainly don't want to make things a hassle for others to develop.
I can look into MAUI and do some testing with it, but I've heard some pretty negative things overall. Lots of half baked features and Microsoft kind of already seemingly losing a bit of interest in it. I know it's technically cross platform, but I believe Microsoft leaves the Linux port to the open source community, so I dunno how fleshed out it is. Still, I'll do some digging into it and see. I might make a test app and see what I can do.
Overall, i will say my main goals would be...

Make sure the Windows version stays the priority and doesn't lose any current functionality
Have at least a Linux UI with a map and item tracker. The got thing is that these are mostly driven from configurations, so for the most part changes to one OS would apply to the other.
Limit the burden on you, CPColin, or anyone else working on this.

Ideally, it would be great if the two were fully in sync outside of voice. But if MAUI doesn't do what we need and if a full conversion to a third party UI like Avalonia is out of the question, then it may just mean a separate, super bare bones Linux project.
So yeah, I guess the next step is for me to give MAUI a shot to see if it'll meet our needs.

So yeah. Looking into MAUI more, and it just doesn't seem like it would be the right avenue to go down for this purpose. Microsoft hasn't committed to making MAUI run on Linux, and the community driven one seems pretty far behind and lacking in support. Admittedly I'm not entirely sure why the MAUI Hybrid version doesn't run on Linux, but I'm not sure we'd want to go down that route anyway.
If the goal were a cross platform UI, I think we'd have a few options:

Avalonia UI - Again, this is what I used in the MSU Scripter, and it seems pretty good. There are some wonky things, but I sorted out those for the MSU Scripter. Either doing a Linux-only UI or doing a cross platform UI, this would probably be my choice.
Electron.Net - Everyone universally loves Electron, right? Right?! Seems decently supported, and Electron is... fine. Would not be my first choice, but I wouldn't hate it either.
Photino - Based on my research, seems sorta like Electron but faster yet less supported.
Gtk# - This is technically an option!

Again, my leanings are toward Avalonia since it's more familiar, seems to work well, and has no evidence that it might be going away any time soon.
But, my first priority will just be trying to get it to where I can easily develop and test without running in a VM. So my first goal will be just making a separate project in the solution (Randomizer.CrossplatformApp?) that will start as a command line tool for generating seeds and auto tracking. After that I can start working on stuff like the bingo goals and maybe slowly build up a UI over time. And who knows? Maybe by the time I get working on the UI portion, MAUI will be better ported to Linux and be more complete in general.

So thinking on this, something I may consider assuming a single shared UI isn't going to happen, is to move some of the UI into configs which can be shared. That way when a new setting or randomizer option gets added, it can be added to both easily. Could make some aspects a bit easier when upgrading in the future to MAUI or anything else.

I briefly looked into this, and one person on Reddit ended up using a MAUI/Blazor hybrid for Windows (and Android and iOS, but that's hardly relevant for this) and Photino/Blazor for Linux. I agree a true single shared UI is unfeasible, maybe we could try the same approach?


[PE-D][Tester E] Order history name requirements not specific

In your UG:

But this is part of your notes on command format:

It would help to have an additional requirement like

Name must be preceded with the prefix n/ (see add command for accepted name format)

Labels: severity.Medium type.DocumentationBug
original: sannie-beep/ped#12

Duplicate with #173