[Bug]: Performance : very slow inference for Mixtral 8x7B Instruct FP8 on H100 with 0.5.0 and 0.5.0.post1

Your current environment
Collecting environment information...
PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.3 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.35

Python version: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (64-bit runtime)
Python platform: Linux-5.15.0-107-generic-x86_64-with-glibc2.35
Is CUDA available: N/A
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration:
GPU 0: NVIDIA H100 80GB HBM3
GPU 1: NVIDIA H100 80GB HBM3

Nvidia driver version: 555.42.02
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A

CPU:
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Address sizes:                      45 bits physical, 48 bits virtual
Byte Order:                         Little Endian
CPU(s):                             16
On-line CPU(s) list:                0-15
Vendor ID:                          GenuineIntel
Model name:                         Intel(R) Xeon(R) Gold 5418Y
CPU family:                         6
Model:                              143
Thread(s) per core:                 1
Core(s) per socket:                 1
Socket(s):                          16
Stepping:                           8
BogoMIPS:                           3999.99
Flags:                              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves avx512_bf16 wbnoinvd arat avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq rdpid cldemote movdiri movdir64b fsrm md_clear flush_l1d arch_capabilities
Hypervisor vendor:                  VMware
Virtualization type:                full
L1d cache:                          768 KiB (16 instances)
L1i cache:                          512 KiB (16 instances)
L2 cache:                           32 MiB (16 instances)
L3 cache:                           720 MiB (16 instances)
NUMA node(s):                       1
NUMA node0 CPU(s):                  0-15
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit:        KVM: Mitigation: VMX unsupported
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Unknown: No mitigations
Vulnerability Retbleed:             Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; Enhanced IBRS; IBPB conditional; RSB filling; PBRSB-eIBRS SW sequence; BHI Syscall hardening, KVM SW loop
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected

Versions of relevant libraries:
[pip3] opentelemetry-instrumentation-transformers==0.10.3
[conda] Could not collect
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: N/A
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0    GPU1    CPU Affinity    NUMA Affinity   GPU NUMA ID
GPU0     X      NV6     0-15    0               N/A
GPU1    NV6      X      0-15    0               N/A

Legend:

  X    = Self
  SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
  NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
  PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
  PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
  PIX  = Connection traversing at most a single PCIe bridge
  NV#  = Connection traversing a bonded set of # NVLinks
`

🐛 Describe the bug
Inference performance is very slow when using FP8 quantization for Mixtral 8x7B Instruct using the vllm docker image vllm/vllm-openai:v0.5.0 and v0.5.0.post1 on H100 HBM3.
The issue is reproducible with 2 FP8 quantized versions of Mixtral 8x7B Instruct :

neuralmagic/Mixtral-8x7B-Instruct-v0.1-FP8
comaniac/Mixtral-8x7B-Instruct-v0.1-FP8-v3

Using FP8 :
INFO 06-14 03:52:53 metrics.py:341] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 29.0 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.1%, CPU KV cache usage: 0.0%.
Using the Unquantized version :
INFO 06-14 03:55:20 metrics.py:341] Avg prompt throughput: 4.2 tokens/s, Avg generation throughput: 88.6 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
Startup logs for the FP8 model :
INFO 06-14 08:43:29 api_server.py:177] vLLM API server version 0.5.0.post1 INFO 06-14 08:43:29 api_server.py:178] args: Namespace(host=None, port=8000, uvicorn_log_level='info', allow_credentials=False, allowed_origins=['*'], allowed_methods=['*'], allowed_headers=['*'], api_key='sb3JhFU5BAKwPB5gYUksNNCsu', lora_modules=None, chat_template=None, response_role='assistant', ssl_keyfile=None, ssl_certfile=None, ssl_ca_certs=None, ssl_cert_reqs=0, root_path=None, middleware=[], model='/models/Mixtral-8x7B-Instruct-v0.1-FP8', tokenizer=None, skip_tokenizer_init=False, revision=None, code_revision=None, tokenizer_revision=None, tokenizer_mode='auto', trust_remote_code=False, download_dir='/models', load_format='auto', dtype='auto', kv_cache_dtype='auto', quantization_param_path=None, max_model_len=None, guided_decoding_backend='outlines', distributed_executor_backend=None, worker_use_ray=False, pipeline_parallel_size=1, tensor_parallel_size=1, max_parallel_loading_workers=None, ray_workers_use_nsight=False, block_size=16, enable_prefix_caching=False, disable_sliding_window=False, use_v2_block_manager=False, num_lookahead_slots=0, seed=0, swap_space=4, gpu_memory_utilization=0.95, num_gpu_blocks_override=None, max_num_batched_tokens=None, max_num_seqs=256, max_logprobs=20, disable_log_stats=False, quantization=None, rope_scaling=None, rope_theta=None, enforce_eager=False, max_context_len_to_capture=None, max_seq_len_to_capture=8192, disable_custom_all_reduce=False, tokenizer_pool_size=0, tokenizer_pool_type='ray', tokenizer_pool_extra_config=None, enable_lora=False, max_loras=1, max_lora_rank=16, lora_extra_vocab_size=256, lora_dtype='auto', long_lora_scaling_factors=None, max_cpu_loras=None, fully_sharded_loras=False, device='auto', image_input_type=None, image_token_id=None, image_input_shape=None, image_feature_size=None, image_processor=None, image_processor_revision=None, disable_image_processor=False, scheduler_delay_factor=0.0, enable_chunked_prefill=False, speculative_model=None, num_speculative_tokens=None, speculative_max_model_len=None, speculative_disable_by_batch_size=None, ngram_prompt_lookup_max=None, ngram_prompt_lookup_min=None, model_loader_extra_config=None, preemption_mode=None, served_model_name=['mixtral'], qlora_adapter_name_or_path=None, engine_use_ray=False, disable_log_requests=False, max_log_len=None) INFO 06-14 08:43:29 llm_engine.py:161] Initializing an LLM engine (v0.5.0.post1) with config: model='/models/Mixtral-8x7B-Instruct-v0.1-FP8', speculative_config=None, tokenizer='/models/Mixtral-8x7B-Instruct-v0.1-FP8', skip_tokenizer_init=False, tokenizer_mode=auto, revision=None, rope_scaling=None, rope_theta=None, tokenizer_revision=None, trust_remote_code=False, dtype=torch.bfloat16, max_seq_len=32768, download_dir='/models', load_format=LoadFormat.AUTO, tensor_parallel_size=1, disable_custom_all_reduce=False, quantization=fp8, enforce_eager=False, kv_cache_dtype=auto, quantization_param_path=None, device_config=cuda, decoding_config=DecodingConfig(guided_decoding_backend='outlines'), seed=0, served_model_name=mixtral) WARNING 06-14 08:43:29 fp8.py:48] Detected fp8 checkpoint. Please note that the format is experimental and subject to change. WARNING 06-14 08:43:36 utils.py:465] Found input_scales that are not equal for fp8 MoE layer. Using the maximum across experts for each layer. INFO 06-14 08:43:36 model_runner.py:160] Loading model weights took 43.7487 GB INFO 06-14 08:43:36 fused_moe.py:300] Using configuration from /usr/local/lib/python3.10/dist-packages/vllm/model_executor/layers/fused_moe/configs/E=8,N=14336,device_name=NVIDIA_H100_80GB_HBM3,dtype=float8.json for MoE layer. INFO 06-14 08:43:44 gpu_executor.py:83] # GPU blocks: 11865, # CPU blocks: 2048 INFO 06-14 08:43:46 model_runner.py:889] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI. INFO 06-14 08:43:46 model_runner.py:893] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing gpu_memory_utilizationor enforcing eager mode. You can also reduce themax_num_seqsas needed to decrease memory usage. INFO 06-14 08:44:14 model_runner.py:965] Graph capturing finished in 29 secs. INFO 06-14 08:44:14 serving_chat.py:92] Using default chat template: INFO 06-14 08:44:14 serving_chat.py:92] {{ bos_token }}{% for message in messages %}{% if (message['role'] == 'user') != (loop.index0 % 2 == 0) %}{{ raise_exception('Conversation roles must alternate user/assistant/user/assistant/...') }}{% endif %}{% if message['role'] == 'user' %}{{ '[INST] ' + message['content'] + ' [/INST]' }}{% elif message['role'] == 'assistant' %}{{ message['content'] + eos_token}}{% else %}{{ raise_exception('Only user and assistant roles are supported!') }}{% endif %}{% endfor %} WARNING 06-14 08:44:14 serving_embedding.py:141] embedding_mode is False. Embedding API will not work. INFO:     Started server process [1] INFO:     Waiting for application startup. INFO:     Application startup complete. INFO:     Uvicorn running on http://<IP_ADDRESS>:8000 (Press CTRL+C to quit)
This slowdown doesn't happen with this model : neuralmagic/Meta-Llama-3-8B-Instruct-FP8. In this case, an inference performance boost is indeed present using FP8 over unquantized.

Hi @Syst3m1cAn0maly this is a known issue with triton==2.3.0 which is unfortunately linked to torch==2.3.0. This will be resolved as we upgrade to torch==2.3.1, ongoing in this PR https://github.com/vllm-project/vllm/pull/5327 but blocked by xformers release

Thanks for this answer.
I will be waiting on this PR then.

is there a workaround for now?

Updating triton worked for me, as suggested by @mgoin (thanks ! :))
I used the following Dockerfile :
`FROM vllm/vllm-openai:v0.5.0.post1
RUN pip install -U triton==2.3.1`


Foundation.Slider: miscalculation of left handle with nonzero start value

Reproduction of error as well as demonstration of expected results: http://codepen.io/anon/pen/RrodPJ
It appears that a nonzero start value isn't taken into account when calculating the left handle's position on Foundation.Slider, resulting in (in some cases) a completely unusable slider.
Additionally, during creation of the reduced test cases, I noticed that the default options (start: 0, initialStart: 0, end: 100, initialEnd: 100) result in a missing fill upon initial render of double-sided sliders
EDIT: might actually be more weird math since data-initial-start="0" data-initial-end="200" data-start="50" data-end="100" doesn't result in the second quarter being filled, it results in the 50%-150% range being filled.

Interesting, if you have a solution, I'd love to see a pr for this.

Fixed by https://github.com/zurb/foundation-sites/pull/8506, will be in 6.2.1

hi,
the problem continues in the last version.
my solution:
slider.js line 178

dim = movement - (isNaN(handlePos) ? this.options.initialStart/((this.options.end-this.options.start)/100) : handlePos) + handlePct;

dim = movement - (isNaN(handlePos) ? ((this.options.end - this.options.initialStart) / 100) / ((this.options.end - this.options.start) / 100) : handlePos) + handlePct;


How to Reduce the Costs of your Azure IaaS VMs

原文：How to Reduce the Costs of your Azure IaaS VMs
链接：/content/cloud-advocate/2020-02/how-to-reduce-the-costs-of-your-azure-iaas-vms.md

@shinyzhu 翻译认领 原文：How to Reduce the Costs of your Azure IaaS VMs


CHAT

If someone says contains % content, the BOT will disconnect
Then an error: "Disconnected: Java. Util. UnknownFormatConversionException: Conversion = '%'
java.util.UnknownFormatConversionException: Conversion = '%'"

Fixed in the latest commit of the main branch. I will not release this now.
I will do a release when I have the time with 1.19 support and Microsoft login.
You can build it yourself :

Clone the repository
run ./gradlew shadowJar
In the directory build/libs/ take the jar with -all.jar

Umm... something wrong
PS E:\Downloads\MinecraftBOT-main> ./gradlew shadowJar
Starting a Gradle Daemon (subsequent builds will be faster)
FAILURE: Build failed with an exception.

What went wrong:
Could not determine the dependencies of task ':shadowJar'.

Could not resolve all dependencies for configuration ':runtimeClasspath'.
Could not find com.github.GeyserMC:MCProtocolLib:1.18.2-1.
Searched in the following locations:
- https://repo.maven.apache.org/maven2/com/github/GeyserMC/MCProtocolLib/1.18.2-1/MCProtocolLib-1.18.2-1.pom
- https://jitpack.io/com/github/GeyserMC/MCProtocolLib/1.18.2-1/MCProtocolLib-1.18.2-1.pom
- https://alwyn974.github.io/maven/com/github/GeyserMC/MCProtocolLib/1.18.2-1/MCProtocolLib-1.18.2-1.pom
- https://repo.opencollab.dev/maven-releases/com/github/GeyserMC/MCProtocolLib/1.18.2-1/MCProtocolLib-1.18.2-1.pom
Required by:
project :

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 31s

Umm... something wrong
PS E:\Downloads\MinecraftBOT-main> ./gradlew shadowJar
Starting a Gradle Daemon (subsequent builds will be faster)
FAILURE: Build failed with an exception.

What went wrong:
Could not determine the dependencies of task ':shadowJar'.

Could not resolve all dependencies for configuration ':runtimeClasspath'.
Could not find com.github.GeyserMC:MCProtocolLib:1.18.2-1.
Searched in the following locations:
- https://repo.maven.apache.org/maven2/com/github/GeyserMC/MCProtocolLib/1.18.2-1/MCProtocolLib-1.18.2-1.pom
- https://jitpack.io/com/github/GeyserMC/MCProtocolLib/1.18.2-1/MCProtocolLib-1.18.2-1.pom
- https://alwyn974.github.io/maven/com/github/GeyserMC/MCProtocolLib/1.18.2-1/MCProtocolLib-1.18.2-1.pom
- https://repo.opencollab.dev/maven-releases/com/github/GeyserMC/MCProtocolLib/1.18.2-1/MCProtocolLib-1.18.2-1.pom
Required by:
project :

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 31s


JupyterLab 1.0

It's just a pre-release, but it worth to migrate to considering it has:

find and replace
We have improved the performance of switching to a large notebook
Notify the user when a kernel is automatically restarted, for example, if crashes from an out of memory error

1.0 is coming very soon https://discourse.jupyter.org/t/jupyterlab-1-0-release-candidate-published/1438/8 (next week?) so it makes sense to test rc locally and hold with the update until it's officially released.

[ ] https://github.com/jupyter/docker-stacks/pull/894
[ ] https://github.com/plotly/plotly.py#jupyterlab-support-python-35

Done, installed 0.9.0dev helm chart since z2jh hasn't released the one with JupyterLab 1.0 yet.


[Bug]: Error in arrange():  In argument: ..1 = stat.  Caused by error: #> ! ..1 must be a vector, not a function, appearing when using plot_pizza "custom" comparison.

What happened?

ggshakeR version: 0.2.090
R version: 2023.08.0 - daily-170
I tried to make a custom comparison graph but it was not possible due to an error, i have followed every step in the tutorial but i could not figure it out.
is there any fix to it? is it the code or the function is not working properly?
i am using the daily build of r to avoid the CacheKey error present in the 2023.06 build.

i had a issue with the season_player parameters but i realized it was because of the short version "Last 365 Days" that was wrongfully inputed, the name was not matching the data frame.

library(worldfootballR)
library(ggshakeR)
library(reprex)
#> Warning: package 'reprex' was built under R version 4.2.3
library(worldfootballR)
library(ggshakeR)
data1 <-fb_player_scouting_report("https://fbref.com/en/players/65159211/Yuri-Alberto", pos_versus = "primary")
data2 <- fb_player_scouting_report("https://fbref.com/en/players/2e5e846d/Deyverson", pos_versus = "primary")
data1 <- data1[c(345,338,301,377,394,386,387,402,393,395), ]
data2 <- data2[c(210,203,166,242,259,251,252,267,258,260), ]
data <- rbind(data1, data2)
graph <- plot_pizza(data = data, type = "comparison", template = "custom",
player_1 = "Deyverson", player_2 = "Yuri Alberto",
season_player_1 = "2023 Série A",
season_player_2 = "2023 Série A",
color_compare = "#c1ef01", theme = "black")
#> Error in arrange():
#> ℹ In argument: ..1 = stat.
#> Caused by error:
#> ! ..1 must be a vector, not a function.
#> Backtrace:
#>      ▆
#>   1. ├─ggshakeR::plot_pizza(...)
#>   2. │ └─data1 %>% arrange(desc(stat), desc(Percentile)) %>% ...
#>   3. ├─dplyr::mutate(., Statistic = factor(Statistic, levels = Statistic))
#>   4. ├─dplyr::arrange(., desc(stat), desc(Percentile))
#>   5. ├─dplyr:::arrange.data.frame(., desc(stat), desc(Percentile))
#>   6. │ └─dplyr:::arrange_rows(.data, dots = dots, locale = .locale)
#>   7. │   ├─dplyr::mutate(data, :=("{name}", !!dot), .keep = "none")
#>   8. │   └─dplyr:::mutate.data.frame(data, :=("{name}", !!dot), .keep = "none")
#>   9. │     └─dplyr:::mutate_cols(.data, dplyr_quosures(...), by)
#>  10. │       ├─base::withCallingHandlers(...)
#>  11. │       └─dplyr:::mutate_col(dots[[i]], data, mask, new_columns)
#>  12. │         └─mask$eval_all_mutate(quo)
#>  13. │           └─dplyr (local) eval()
#>  14. ├─dplyr:::dplyr_internal_error("dplyr:::mutate_not_vector", <named list>)
#>  15. │ └─rlang::abort(class = c(class, "dplyr:::internal_error"), dplyr_error_data = data)
#>  16. │   └─rlang:::signal_abort(cnd, .file)
#>  17. │     └─base::signalCondition(cnd)
#>  18. └─dplyr (local) <fn>(<dpl:::__>)
#>  19.   └─rlang::abort(message, class = error_class, parent = parent, call = error_call)
graph
#> Error in eval(expr, envir, enclos): objeto 'graph' não encontrado
ggsave("comparacao.png", bg = "black", width = 2900, height = 2800, units = "px")
#> Error in ggsave("comparacao.png", bg = "black", width = 2900, height = 2800, : não foi possível encontrar a função "ggsave"

Hello Victor,
The package has a bug in it that needs to be fixed however all maintainers
of the package are busy 😅. I will try to get this ASAP (I’ve had others
send me similar emails) but bare with me as I’m the only active maintainer
:)
Thank you,
Abhishek
On Mon, Jul 3, 2023 at 4:24 PM Victor Paulino @.***>
wrote:

What happened?
ggshakeR version: 0.2.090
R version: 2023.08.0 - daily-170
I tried to make a comparison graph but it was not possible due to the
Error in ans[ypos] <- rep(yes, length.out = len)[ypos], so i repeated the
same code used as a example in the tutorial page but it was still appearing
and not generating any graph.
is there any fix to it? is it the code or the function is not working
properly?
i am using the daily build of r to avoid the CacheKey error present in the
2023.06 build.
library(worldfootballR)
library(ggshakeR)
library(reprex)
#> Warning: package 'reprex' was built under R version 4.2.3
data1 <- fb_player_scouting_report("
https://fbref.com/en/players/f586779e/Tammy-Abraham", pos_versus =
"primary")
data2 <- fb_player_scouting_report("
https://fbref.com/en/players/59e6e5bf/Dominic-Calvert-Lewin", pos_versus
= "primary")
data <- rbind(data1, data2)
comp_pizza <- plot_pizza(data = data, type = "comparison", template =
"outfielder",
player_1 = "Tammy Abraham", player_2 = "Dominic Calvert-Lewin",
season_player_1 = "Last 365 Days",
season_player_2 = "Last 365 Days",
color_compare = "#41ab5d", theme = "black")
comp_pizza
#> Warning in rep(yes, length.out = len): 'x' is NULL so the result will
be NULL
#> Error in ans[ypos] <- rep(yes, length.out = len)[ypos]: substituto tem
comprimento zero
—
Reply to this email directly, view it on GitHub
https://github.com/abhiamishra/ggshakeR/issues/123, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMMZTJDCUSUM3SSRSCQA5ADXOMZ7JANCNFSM6AAAAAAZ45GGBM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Moved all generationally identical cards to the same vGPU profiles.

This change will require users to reselect which vGPU profile they want to use, as this exposes only one vGPU compatible card instead of several like before. The outcome is having more profiles to select from, but users also need to be careful to select profiles only if they have adequate VRAM.

What about trying to mask out the generation instead of listing all cards? Currently we have a lot of IDs, I think we can simplify the tables and reduce maintenance by using range checks instead.


The game deletes songs that have an _intro from cybergrind playlists upon restart

If you have a song with an _intro after restarting cybergrind, it will be deleted from your playlist. If you try to go into the cybergrind without adding it back into your playlist, the game will crash.
Whats surprising is that I don't see anything in the playerlog that could cause this
LogOutput.log
Youtube Video

i experience this too, but theres no crash when i go back into the cybergind.


BIGTOP-3497. libcrypto.so should be provided for libhadoop.so.

https://issues.apache.org/jira/browse/BIGTOP-3497
libcrypto.so is required by OpensslCipher and OpensslSecureRandom of Hadoop.

I tested this by docker provisioner on CentOS 7 and Ubuntu 18.04.
CentOS 7:
$ ./docker-hadoop.sh --exec 1 hadoop checknative
2021-02-10 08:17:15,470 INFO bzip2.Bzip2Factory: Successfully loaded & initialized native-bzip2 library system-native
2021-02-10 08:17:15,473 INFO zlib.ZlibFactory: Successfully loaded & initialized native-zlib library
2021-02-10 08:17:15,477 WARN erasurecode.ErasureCodeNative: ISA-L support is not available in your platform... using builtin-java codec where applicable
2021-02-10 08:17:15,555 INFO nativeio.NativeIO: The native code was built without PMDK support.
Native library checking:
hadoop:  true /usr/lib/hadoop/lib/native/libhadoop.so.1.0.0
zlib:    true /lib64/libz.so.1
zstd  :  false
snappy:  true /usr/lib/hadoop/lib/native/libsnappy.so.1
lz4:     true revision:10301
bzip2:   true /lib64/libbz2.so.1
openssl: true /lib64/libcrypto.so
ISA-L:   false libhadoop was built without ISA-L support
PMDK:    false The native code was built without PMDK support.

Ubuntu 18.04:
$ ./docker-hadoop.sh --exec 1 hadoop checknative
WARNING: The DOCKER_IMAGE variable is not set. Defaulting to a blank string.
WARNING: The MEM_LIMIT variable is not set. Defaulting to a blank string.
2021-02-10 08:17:31,337 INFO bzip2.Bzip2Factory: Successfully loaded & initialized native-bzip2 library system-native
2021-02-10 08:17:31,340 INFO zlib.ZlibFactory: Successfully loaded & initialized native-zlib library
2021-02-10 08:17:31,344 WARN erasurecode.ErasureCodeNative: Loading ISA-L failed: Failed to load libisal.so.2 (libisal.so.2: cannot open shared object file: No such file or directory)
2021-02-10 08:17:31,344 WARN erasurecode.ErasureCodeNative: ISA-L support is not available in your platform... using builtin-java codec where applicable
2021-02-10 08:17:31,404 INFO nativeio.NativeIO: The native code was built without PMDK support.
Native library checking:
hadoop:  true /usr/lib/hadoop/lib/native/libhadoop.so.1.0.0
zlib:    true /lib/x86_64-linux-gnu/libz.so.1
zstd  :  false
snappy:  true /usr/lib/hadoop/lib/native/libsnappy.so.1
lz4:     true revision:10301
bzip2:   true /lib/x86_64-linux-gnu/libbz2.so.1
openssl: true /usr/lib/x86_64-linux-gnu/libcrypto.so
ISA-L:   false Loading ISA-L failed: Failed to load libisal.so.2 (libisal.so.2: cannot open shared object file: No such file or directory)
PMDK:    false The native code was built without PMDK support.

+1, also checked on CentOS 8 and Debian 10. Thanks @iwasakims.


Versioned JS and CSS bundles like main-1.0.2,js

Given a version number like 1.0.2, the script should create main-1.0.2.js, main-1.0.2,css and include the same in index.html. I know how to do this in gulp but prefer to use ionic-app-scripts. One option I can think of is to customise uglify script. Any suggestions?

Can you set the dest property? https://github.com/driftyco/ionic-app-scripts/blob/master/config/rollup.config.js#L32

Lot of config files need to be customised as many of them refer to main.js, etc. For the time being I am using ionic_build_dir in package.son to achieve versioned build.
"config": {
"ionic_build_dir": "www/build-1.0.2"
},

Thanks! We have reviewed this and i am going to close it for now as it is not something we want to include in our build process. I would advise that you continue to use the ionic_build_dir option to get this in your project. Thanks!


eden without any flag now shows help message instead of runtime error

Fix Issue #6 .

Thanks @xj! I fixed one issue (didn't return version info with -v) and created another. Thanks for the fix.


【compile Error】 swanky contract compile mytoken -v

I trying to develop token dapp (psp22) with swanky.
I create template project with swanky init command.
And I tried compile contract but bellow error occured.
why??
swanky contract compile mytoken -v

======== Found contracts ========
        mytoken
======== Compiling mytoken ========
warning: Both `/Users/harukikondo/.cargo/config` and `/Users/harukikondo/.cargo/config.toml` exist. Using `/Users/harukikondo/.cargo/config`
warning: Both `/Users/harukikondo/.cargo/config` and `/Users/harukikondo/.cargo/config.toml` exist. Using `/Users/harukikondo/.cargo/config`
ERROR: Error invoking `cargo metadata`

Caused by:
    `cargo metadata` exited with an error: warning: Both `/Users/harukikondo/.cargo/config` and `/Users/harukikondo/.cargo/config.toml` exist. Using `/Users/harukikondo/.cargo/config`
    warning: Both `/Users/harukikondo/.cargo/config` and `/Users/harukikondo/.cargo/config.toml` exist. Using `/Users/harukikondo/.cargo/config`
        Updating crates.io index
    error: failed to get `ink_engine` as a dependency of package `mytoken v0.1.0 (/Users/harukikondo/git/Astar-FT/mytoken/contracts/mytoken)`

    Caused by:
      failed to load source for dependency `ink_engine`

    Caused by:
      Unable to update registry `crates-io`

    Caused by:
      failed to fetch `https://github.com/rust-lang/crates.io-index`

    Caused by:
      process didn't exit successfully: `git fetch --force --update-head-ok 'https://github.com/rust-lang/crates.io-index' '+HEAD:refs/remotes/origin/HEAD'` (exit status: 255)
      --- stderr
      error: cannot open 'FETCH_HEAD': Permission denied
Error: Command failed: cargo +nightly contract build --manifest-path contracts/mytoken/Cargo.toml
warning: Both `/Users/harukikondo/.cargo/config` and `/Users/harukikondo/.cargo/config.toml` exist. Using `/Users/harukikondo/.cargo/config`
warning: Both `/Users/harukikondo/.cargo/config` and `/Users/harukikondo/.cargo/config.toml` exist. Using `/Users/harukikondo/.cargo/config`
ERROR: Error invoking `cargo metadata`

Caused by:
    `cargo metadata` exited with an error: warning: Both `/Users/harukikondo/.cargo/config` and `/Users/harukikondo/.cargo/config.toml` exist. Using `/Users/harukikondo/.cargo/config`
    warning: Both `/Users/harukikondo/.cargo/config` and `/Users/harukikondo/.cargo/config.toml` exist.  Which contract language should we use? ink
? Which contract template should we use initially? psp22
? What should we name your initial contract? psp22
? What is your name? mashharuki
? What is your email?
? Do you want to download Swanky node? Yes
✔ Checking dependencies OK
✔ Copying template files OK
✔ Processing templates OK
✔ Initializing git OK
✔ Downloading Swanky node OK
✔ Installing dependencies OK
✔ Writing config OK
🎉 😎 Swanky project successfully initialised! 😎 🎉

Thank you for your reporting.
In my case, I could compile psp22 contract with swanky.
I can not understand the cause of your issue clearly,but I think maybe this is your environment issue.
So please let me know your environment.

Did you already installed binaryen?
What is your cargo-contract version?
Please share the result of the command of "rustup show".

Thank you for replying!!

Did you already installed binaryen?
Yes.

What is your cargo-contract version?
cargo-contract 1.5.1-unknown-aarch64-apple-darwin

Please share the result of the command of "rustup show".

Default host: aarch64-apple-darwin
rustup home:  /Users/harukikondo/.rustup

installed toolchains
--------------------

stable-aarch64-apple-darwin
nightly-2022-06-30-aarch64-apple-darwin
nightly-2022-07-24-aarch64-apple-darwin
nightly-2022-08-15-aarch64-apple-darwin
nightly-aarch64-apple-darwin (default)
bpf

installed targets for active toolchain
--------------------------------------

aarch64-apple-darwin
wasm32-unknown-unknown

active toolchain
----------------

nightly-aarch64-apple-darwin (default)
rustc 1.68.0-nightly (0468a00ae 2022-12-17)

Thank you for your reporting. In my case, I could compile psp22 contract with swanky.
I can not understand the cause of your issue clearly,but I think maybe this is your environment issue. So please let me know your environment.

Did you already installed binaryen?
What is your cargo-contract version?
Please share the result of the command of "rustup show".

Thank you for replying!!

Did you already installed binaryen?
Yes.

What is your cargo-contract version?
cargo-contract 1.5.1-unknown-aarch64-apple-darwin

Please share the result of the command of "rustup show".

Default host: aarch64-apple-darwin
rustup home:  /Users/harukikondo/.rustup

installed toolchains
--------------------

stable-aarch64-apple-darwin
nightly-2022-06-30-aarch64-apple-darwin
nightly-2022-07-24-aarch64-apple-darwin
nightly-2022-08-15-aarch64-apple-darwin
nightly-aarch64-apple-darwin (default)
bpf

installed targets for active toolchain
--------------------------------------

aarch64-apple-darwin
wasm32-unknown-unknown

active toolchain
----------------

nightly-aarch64-apple-darwin (default)
rustc 1.68.0-nightly (0468a00ae 2022-12-17)

Thank you for sharing your information.
I match my environment to your environment, and I compiled again, but the error did not occurred.
Can you try to execute the commands as following?
cd contracts/psp22
cargo +nightly-2022-08-15 contract build

Thank you for sharing your information. I match my environment to your environment, and I compiled again, but the error did not occurred.
Can you try to execute the commands as following?
cd contracts/psp22
cargo +nightly-2022-08-15 contract build

OK. the result of command is below.
harukikondo@kondouharuakiranoMacBook-Pro mytoken % cargo +nightly-2022-08-15 contract build
warning: Both `/Users/harukikondo/.cargo/config` and `/Users/harukikondo/.cargo/config.toml` exist. Using `/Users/harukikondo/.cargo/config`
warning: Both `/Users/harukikondo/.cargo/config` and `/Users/harukikondo/.cargo/config.toml` exist. Using `/Users/harukikondo/.cargo/config`
2022-12-23T03:04:27.194410Z  INFO cargo_contract::crate_metadata: Fetching cargo metadata for Cargo.toml
ERROR: Error invoking `cargo metadata`

Caused by:
    `cargo metadata` exited with an error: warning: Both `/Users/harukikondo/.cargo/config` and `/Users/harukikondo/.cargo/config.toml` exist. Using `/Users/harukikondo/.cargo/config`
    warning: Both `/Users/harukikondo/.cargo/config` and `/Users/harukikondo/.cargo/config.toml` exist. Using `/Users/harukikondo/.cargo/config`
        Updating crates.io index
    error: failed to get `ink_engine` as a dependency of package `mytoken v0.1.0 (/Users/harukikondo/git/Astar-FT/mytoken/contracts/mytoken)`

    Caused by:
      failed to load source for dependency `ink_engine`

    Caused by:
      Unable to update registry `crates-io`

    Caused by:
      failed to fetch `https://github.com/rust-lang/crates.io-index`

    Caused by:
      process didn't exit successfully: `git fetch --force --update-head-ok 'https://github.com/rust-lang/crates.io-index' '+HEAD:refs/remotes/origin/HEAD'` (exit status: 255)
      --- stderr
      error: cannot open 'FETCH_HEAD': Permission denied

I think if you solve this error, maybe you will able to compile.
When I searched by google the error, some solutions exist. Please check it.
error: cannot open 'FETCH_HEAD': Permission denied

I think if you solve this error, maybe you will able to compile. When I searched by google the error, some solutions exist. Please check it.
error: cannot open 'FETCH_HEAD': Permission denied

thank you!! I will try it!

@realtakahashi  I made it!!
warning ../../package.json: No license field
$ mocha -r ts-node/register "test/**/*.test.ts" --exit --timeout 20000

  psp22 test
    ✔ Assigns initial balance
    ✔ Transfer adds amount to destination account (64ms)
    ✔ Can not transfer above the amount (47ms)
    ✔ Can not transfer to hated account (104ms)

  4 passing (1s)

✨  Done in 5.51s.

env info
cargo contract version : cargo-contract 1.5.1-unknown-x86_64-apple-darwin
swanky version: @astar-network/swanky-cli/1.0.7 darwin-x64 node-v18.12.1
nodejs version: v18.12.1

rustup show result
Default host: x86_64-apple-darwin
rustup home:  /Users/harukikondo/.rustup

installed toolchains
--------------------

stable-x86_64-apple-darwin (default)
nightly-2022-06-30-x86_64-apple-darwin
nightly-x86_64-apple-darwin

installed targets for active toolchain
--------------------------------------

wasm32-unknown-unknown
x86_64-apple-darwin

active toolchain
----------------

stable-x86_64-apple-darwin (default)
rustc 1.66.0 (69f9c33d7 2022-12-12)

At first I was trying with MacOS with M1 chip, but the error could not be resolved, so I built the environment with normal MacOS and tried it and it worked.

This issue is resolved , so I closed this.


Restore request_id to Graveler logs

Also add request_id to some logs to actions.  Fixes #4566, and helps push
#2682 towards the finish line.

Tested by running locally manually.  I can now see:

request_id on Graveler logs about branch conflicts, e.g.:INFO   [2022-11-20T16:52:05+02:00]pkg/graveler/graveler.go:1785 pkg/graveler.(*KVGraveler).retryBranchUpdate.func1 Retrying update branch                     branchID=main host="localhost:8000" method=POST operation_id=MergeIntoBranch path=/api/v1/repositories/bar/refs/moo/merge/main request_id=bc71651e-1999-419f-8a30-11f3a82bb939 service_name=rest_api try=2

request_id on some actions log lines, notably the "filtering" one, e.g.:DEBUG  [2022-11-20T16:50:57+02:00]pkg/actions/service.go:226 pkg/actions.(*StoreService).Run Filtering actions                             host="localhost:8000" method=POST operation_id=Commit path=/api/v1/repositories/bar/branches/moo/commits record="{5mt5qbv13hou1ekh8jqg pre-commit bar s3://treeverse-ariels-test-us/repos/local-bar/ moo moo {1 admin add foo  2022-11-20 16:50:57.826849025 +0200 IST m=+515.643694361 [92d1379d90d81f5da73412137b65594106b3b32fdae34b24b5ec527e7ae24cbd] map[] 0}   }" request_id=e6bb0334-60fd-44f5-ad6e-8e4fb59f4341 service_name=rest_api spec="{pre-commit moo}"

However note that async actions log lines still do not include a request_id; opened #4615 about that.

Fixed, thanks!  Pulling once tests green.


Should we normalize a domain name without a scheme ?

I mean that if someone attempts to normalize "google.com" should our normalizer return null (like it does today) or should it should we return http://google.com
Maybe in the aggresive normalizer ?

Resp. http://google.com/ - yes, sounds reasonable.


BUG: Dark Mode for Rate-us section

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I have noticed an issue where the background of the "Rate-Our-Website" section is not changing when switching to dark mode. I would love to contribute to the project by fixing this issue.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Ok start working on this!


fix: Configure feature gates appropriately

The operator does not like feature gates being quoted.
Feature gates are also a flag based on presence. If the flag is present, it is understood to be true, absence leaves the default value.

@TylerHelmuth Can this be merged now?


Errors not colorized correctly in messages panel

Regression from April.
Current April stable bits :

Current RC build :

The spacing is also different from what it was.

Fix ported to release/1.18


MANIFEST file should be under control of the source repository

Currently, the manifest file is looked up relative to the target repository, since
in
https://github.com/ansys/ansys-tools-repo-sync/blob/84f9c7966a0959ed4287d8c41ba6ca2c3283de1c/ansys/tools/repo_sync/repo_sync.py#L53
we switch to the cloned repository, and the open the MANIFEST
https://github.com/ansys/ansys-tools-repo-sync/blob/84f9c7966a0959ed4287d8c41ba6ca2c3283de1c/ansys/tools/repo_sync/repo_sync.py#L123
This seems like a dangerous default, because what is being synced should be completely under control of the source repository.

IMO - this is no longer applicable. With the current implementation, we have to pass the path of the mainfest file in the current machine/working directory... and it is not dependent on the target repository. So, I'm guessing this issue is basically solved now. Closing! =)


Chopping materials in dedicated server spawns a black ball

Hi guys, i'm testing this project.
I played as a dedicated server and i found this bug:

Do you know what happens here?

does the ball move? or just stays

The ball just stays in its position(if the player turns around the position do it with it).

@chris-gong Did you fix it?

I'm currently in the process of remaking the feature so not yet.


Prebackuppod command assumes /usr/bin/tar exists

Describe the bug
Some prebackuppod jobs are failing with this error:
/bin/sh: /usr/bin/tar: not found

To Reproduce
n/a
Expected behavior
Backups run successfully.
Screenshots
n/a
Additional context
Here's the backup command:
/bin/sh, -c, /usr/bin/tar -cf - -C /usr/share/elasticsearch/data .

This only seems to be occurring on our elasticsearch images where tar is at the path /bin/tar. So I guess we either need to rely on $PATH (is it populated correctly in the context of the backup command?) or do some manual checks for the location of tar.

Another variant of this bug is:
Backup command:
/bin/sh, -c, /bin/busybox tar -cf - -C /usr/share/elasticsearch/data .

stderr:
/bin/sh: /bin/busybox: No such file or directory

elasticsearch images aren't busybox-based.

Confirming that either /bin/tar or just tar works. So I $PATH must be set correctly.


Uncaught Error: Missing "providerName" property for hyperclick provider.

[Enter steps to reproduce below:]

...
...

Atom Version: 1.2.1
System: Mac OS X 10.11.1
Thrown From: Atom Core
Stack Trace
Uncaught Error: Missing "providerName" property for hyperclick provider.
At /Volumes/Homer/nuclide/pkg/nuclide/hyperclick/lib/main.js:30

Error: Missing "providerName" property for hyperclick provider.
    at Object.consumeProvider (/Volumes/Homer/nuclide/pkg/nuclide/hyperclick/lib/main.js:30:13)
    at Provider.module.exports.Provider.provide (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/service-hub/lib/provider.js:30:52)
    at /Applications/Atom.app/Contents/Resources/app.asar/node_modules/service-hub/lib/service-hub.js:55:26
    at doNTCallback0 (node.js:419:9)
    at process._tickDomainCallback (node.js:389:13)

Commands

Config
{
  "core": {
    "disabledPackages": [
      "tree-view"
    ]
  },
  "editor": {
    "invisibles": {}
  }
}

Installed Packages
# User
autocomplete-python, v0.10.4
hyperclick, v0.0.0
nuclide-arcanist, v0.0.0
nuclide-blame, v0.0.0
nuclide-blame-provider-hg, v0.0.0
nuclide-blame-ui, v0.0.0
nuclide-buck-files, v0.0.0
nuclide-busy-signal, v0.0.0
nuclide-clang-atom, v0.0.0
nuclide-code-format, v0.0.0
nuclide-code-highlight, v0.0.0
nuclide-debugger-atom, v0.0.0
nuclide-debugger-hhvm, v0.0.0
nuclide-debugger-lldb, v0.0.0
nuclide-debugger-node, v0.0.0
nuclide-diagnostics-store, v0.0.0
nuclide-diagnostics-ui, v0.0.0
nuclide-diff-view, v0.0.0
nuclide-file-tree, v0.0.0
nuclide-file-watcher, v0.0.0
nuclide-find-references, v0.0.0
nuclide-flow, v0.0.0
nuclide-fuzzy-filename-provider, v0.0.0
nuclide-hack, v0.0.0
nuclide-hack-symbol-provider, v0.0.0
nuclide-health, v0.0.0
nuclide-hg-repository, v0.0.0
nuclide-home, v0.0.0
nuclide-installer, v0.0.0
nuclide-language-hack, v0.0.0
nuclide-objc, v0.0.0
nuclide-ocaml, v0.0.0
nuclide-open-filenames-provider, v0.0.0
nuclide-quick-open, v0.0.0
nuclide-recent-files-provider, v0.0.0
nuclide-recent-files-service, v0.0.0
nuclide-remote-projects, v0.0.0
nuclide-test-runner, v0.0.0
nuclide-toolbar, v0.0.0
nuclide-type-hint, v0.0.0
python-tools, v0.6.6
react, v0.12.10
react-snippets, v0.3.0

# Dev
No dev packages

Looks like one of the provider to the hyperclick service doesn't define a name. As far as I can tell this has nothing to do with Atom. You should probably report it on the nuclide repo since hyperclick is part of their codebase.


declare compliance with x-common 1.0.0, where applicable

For all non-generated exercises, I examined the x-common canonical data and determined whether the track was already compliant. If so, I marked it as such.

Maybe don't need to show students "converted from x-common by hand"

Actually I honestly don't think we need to merge these. These are informational, to tell us which exercises are up to date, but I can't think of a reason why students would need to know (tell me if you can think of one).


No such function: vector

According to this post, libsql should have native support for vectors. However, when I try to insert a vector like described in the post via libsql client I get LibsqlError: SQLITE_ERROR: no such function: vector. Any advice?
Version: "@libsql/client": "^0.6.2"

I am facing the same issue with Typescript. Were you able to find a solution?

@haaawk I didn't create it on turso but locally. Does this command apply locally as well?

@haaawk I didn't create it on turso but locally. Does this command apply locally as well?

Not at the moment.

The vector() function is now part of the Rust, JavaScript, and Python SDKs.


tooltips added sir

sir pls open my work
thanks

Coverage remained the same at 82.507% when pulling f24de522ed4a69eb8b4ad9758e71bb7de340b60e on oneLoveUser:tooltips into e8e70ef37a4f1303dc4e0cab2e3603883e5f6d5c on CircuitVerse:master.


Content in server side installation overview

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[ ] If the changes in this PR is part of the next future release, make this pull request against the docs-staging branch which will be published at the next release boundary. If the changes in this PR are part of the current release, use the default base branch, master. For more information about branches, see https://github.com/zowe/docs-site/tree/master#understanding-the-doc-branches.

[x] If this PR relates to GitHub issues in docs-site or other repositories, please list in Description, prefixed with close, fix or resolve keywords.

Description (including links to related git issues)
Please describe your pull request.
This pull request targets at the server-side component installation overview. Please feel free to modify the content.
#2961
:heart:Thank you!

The first picture contains the `install through containerization build' selection which is duplicated.

The first picture contains the `install through containerization build' selection which is duplicated.

Thank you for pointing this out. Will fix that soon.


Longpress letters are misplaced on iOS

I am using the Divvun keyboards iOS keyboard, and noticed that the longpress letters do not match up with what's specified in the sms.yaml layout file.  My problem was not finding Ææ under Ää or Øø under Öö like i expected, like seen in these pictures:

It does seem like this problem affects other letters as well, though. E.g. there is no
longpress letters available under Uu, although the layout specifies there be eight (U: Ü Ú Ù Û Ũ Ū Ụ Ů,  u: ü ú ù û ũ ū ụ ů).
I am using an iPhone SE with iOS 17.3.1 and Divvun Keyboards v3.2.5 (not dev).

When describing this bug, it is important to indicate whether the keyboard used is Apple's or Divvun's. The only thing we have control over is the Divvun keyboard app(s).
Apple has used our yaml keyboard layout files as inspiration, but they are not using them as a direct source, and are not bound to them.
Whose keyboard are the screen shots of?

The screenshots are of Divvun’s keyboard


Upgrade outdated to work with yarn 2

Impetus
jazelle outdated command does not work with Yarn v2.  As an example, running this in our monorepo yields the following error:
~/c/i/web-code ❯❯❯ jz outdated                                                                                main
@uber/bliss-portlets 0.2.* 0.2.9
Error: Command failed: /private/var/tmp/_bazel_amsmith/8b138622209f13bd3f8c3593776c51e6/external/jazelle_dependencies/bin/node /private/var/tmp/_bazel_amsmith/8b138622209f13bd3f8c3593776c51e6/external/jazelle/utils/../bin/yarn.js info @apollo/react-common version --json 2>/dev/null

    at exec (/private/var/tmp/_bazel_amsmith/8b138622209f13bd3f8c3593776c51e6/external/jazelle/utils/node-helpers.js:40:35)
    at outdated (/private/var/tmp/_bazel_amsmith/8b138622209f13bd3f8c3593776c51e6/external/jazelle/commands/outdated.js:45:37)

And yarn info @apollo/react-common version --json yields:
~/c/i/web-code ❯❯❯ yarn info @apollo/react-common version --json                                                     ✘ 1 main
Usage Error: No package matched your request

$ yarn info [-A,--all] [-R,--recursive] [-X,--extra #0] [--cache] [--dependents] [--manifest] [--name-only] [--virtuals] [--json] ...

It looks like the new yarn info command isn't a mirror of the v1 one.
Solution
Instead, we can use yarn npm info ... which provides the latest version for the request package.

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

!land


Proposal: Move Migration/Schema Tools out of Pop

Currently the migration and schema management tools are tied tightly to pop. I feel as though these tools, representing a bulk of the soda command should be moved to gobuffalo/fizz.
These rebuilt tools can be used by Pop, Gorm, etc... independently. These tools should strive to use only the std lib sql package. If that's not easily do-able, then sqlx will be allowed, but nothing else beyond that.
In addition to allowing projects, such as Pop and Buffalo, to continue using these tools, we can make them available to the wider Go community as whole who need things like migrations, but don't want to use something such as Pop.

My understanding is that this has been completed. https://github.com/gobuffalo/fizz, should issue still be open?


ES7 async and await keywords

Brackets does not properly highlight the JavaScript ES7 async and await keywords, and the following line is highlighted incorrectly as well.
Release 1.7 build 1.7.0-16898 (release b0a363b71)
build timestamp: Wed Jun 08 2016 12:27:56 GMT+0100
Windows 10 Pro x64

Hi @DaAwesomeP
We're updating CodeMirror in soon to be released version 1.8
You can test the highlighting here https://codemirror.net/mode/javascript/index.html and if it's incorrect, open an issue with https://github.com/codemirror/CodeMirror

Yeah, the new CodeMirror version works as expected. Thanks!


Ionic React: nx v15.8.x Generator fails with angular error

Describe the bug
Generating an Ionic React app using nxext@latest with NX v15.8 throws this error. Which is strange because it shouldn't need angular, right?
To Reproduce
nx generate @nxext/ionic-react:application staff-portal
>  NX  Generating @nxext/ionic-react:application
✔ Which starter template would you like to use? · sidemenu
 >  NX   Cannot install required package @nrwl/angular during a dry run.
Run the generator without --dryRun, or install the package with "npm install -D<EMAIL_ADDRESS>and try again.
   Pass --verbose to see the stacktrace.

I'll close this cause it's a duplicate. Already aware of the problem with 15.8

@msacchetti that's an bug, will be removed with the next release


Fixing /api/1.1/servers/{id} endpoint to not return empty response

What does this PR (Pull Request) do?

[x] This PR fixes #4867

Which Traffic Control components are affected by this PR?

CDN in a Box
Traffic Control Client Go
Traffic Ops

What is the best way to verify this PR?

Run the API v1 tests and make sure they all pass.
If this is a bug fix, what versions of Traffic Control are affected?

master

The following criteria are ALL met by this PR

[x] This PR includes tests
[x] I have explained why documentation is unnecessary
[x] This PR does not include an update to CHANGELOG.md
[x] This PR includes any and all required license headers
[x] This PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Additional Information

@ocket8888 - is this related to #4820 in any way? can they be merged together or do they address different problems?

They're different problems

@ocket8888 - you want to merge this?


CDS devs research insights

Interview guide:
https://docs.google.com/document/d/13WaXfEFRnnZzCol6jYP8mTJ5hk6k0p9Olq8vIw8EEOE/edit#heading=h.n1d0qafnheeb
Interviews notes:
Participant A → Notes
Participant B → Notes
Participant C → Notes
Participant D → Notes
Participant E → Notes
Participant F → Notes
Analysis and insights TBD.

taking raw notes to gather insights and highlights main points.

I have not yet started on this. But the plan is to start towards the end of this week.

A few highlights added to the product vision research refresher.

No progress on this.


add CHANGELOG and ADRs

NOTE: Includes placeholder ADR 0002 regarding the creation of this repo.
ARCHBOM-1213

What are your thoughts of having a changelog in each cookiecutter vs having a single changelog for entire repository? I am in favor of one changelog for entire edx-cookiecutters repository.

@jinder1s: I would say one changelog.  I could imagine different directories for ADRs if we are making template specific decisions, but that is TBD.


The IO#getb family of methods

With #11830 merged, we can now turn our attention to binary counterparts of IO#gets, which would consume bytes, instead of characters, delimited by some other byte or byte sequence, and optionally up to some limit on the number of bytes read. #gets has the following overloads:

#gets(limit : Int, chomp = false) : String?
#gets(delimiter : Char, limit : Int, chomp = false) : String?
#gets(delimiter : Char, chomp = false) : String?
#gets(delimiter : String, chomp = false) : String?
#gets(chomp = true) : String?

For #getb the delimiter would similarly be a UInt8 or Bytes, the limit would be for byte instead of character counts, and chomp would have no special behaviour for \n (which also trims \r\n). If the delimiter isn't given, the null byte (0_u8) is used. I suggest the following overloads:

#getb(delimiter : UInt8, *, limit : Int? = nil, chomp : Bool = false) : Bytes?
#getb(delimiter : Bytes, *, limit : Int? = nil, chomp : Bool = false) : Bytes?
#getb(*, limit : Int? = nil, chomp : Bool = true) : Bytes?

As with #gets, getb(Bytes.empty) is equivalent to getb_to_end. Note that the default value for chomp changes depending on whether delimiter is provided, to match #gets's interface.
If possible, #gets' overloads could also be restructured like this. (Note that no overload currently exists that can take both a String delimiter and a limit count.)

chomp defaults to true only when no other arguments are provided to #gets, but false in all the other overloads. I am not sure if this should change for both #gets and #getb.


Create form.html

Signup and Login Page

Are you a Customer or Business?
Customer
Business

Customer Signup Form

First Name:

Last Name:
<input type="text" id="customerLastName" name="customerLastName" required>

Email Address:
<input type="email" id="customerEmail" name="customerEmail" required>

Telephone Number:
<input type="tel" id="customerPhone" name="customerPhone" required>

Address:
<textarea id="customerAddress" name="customerAddress" required></textarea>

<input type="submit" value="Sign Up">

Business Signup Form

Business Name:

Contact Number:
<input type="tel" id="businessContact" name="businessContact" required>

Email Address:
<input type="email" id="businessEmail" name="businessEmail" required>

Business Address:
<textarea id="businessAddress" name="businessAddress" required></textarea>

Menu:
<textarea id="businessMenu" name="businessMenu" required></textarea>

<input type="submit" value="Sign Up">


Add a game data buffer to renderers

Depending on the distance to the server for both producer and the person who uses the renderer, frames can take a very varying amount of time until they travel both distances. This causes gameplay to appear "laggy".
By buffering frames for even a short time like 1 second, rendering would be much improved with the only downside being the delay.

Thanks! I think this is the next thing I'll be working on :)

Another thing you can do is to start the games simultaneously when you get the game_start event, as well as a x second buffer (1 should be enough). This way players can't screen-cheat and copy on same-piece rom sets (this is a huge issue cheating issue)

Frame Buffer added in https://github.com/timotheeg/nestrischamps/pull/85.
Changes for a simultaneous start should be its own issue. I'll open a new one later.


Custom CPU/Memory scale rule

Please provide us with the following information:

This issue is a: (mark with an x)

[X] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
Custom CPU/Memory scale rules are not accepted as intended.
Steps to reproduce

Define a custom scale type either memory or CPU

"scale": {
            "maxReplicas": 10,
            "minReplicas": 1,
            "rules": [
              {
                "custom": {
                  "metadata": {
                    "type": "Utilization",
                    "value": "60"
                  },
                  "type": "cpu"
                },
                "name": "cpu-scale"
              },
              {
                "custom": {
                  "metadata": {
                    "type": "Utilization",
                    "value": "75"
                  },
                  "type": "memory"
                },
                "name": "memory-scale"
              }
            ]
          },

Get the error similar to this: {"TimeStamp":"2024-03-20 04:24:11 \u002B0000 UTC","Type":"Warning","ContainerAppName":"tiley-dev","RevisionName":"tiley-dev--mqnaeyj","ReplicaName":"","Msg":"error parsing memory metadata: no type given in neither trigger.metadata.type or trigger.metricType","Reason":"KEDAScalerFailed","EventSource":"KEDA","Count":31}

Expected behavior [What you expected to happen.]
The scaling rule should work.
Actual behavior [What actually happened.]
The scaling is not working and replica number stays at 1 - get the error above.
Another thing I've tried is the "AverageValue" but that one was also not working either. Maybe I didn't set the value right. Say if the container is 0.5core and 1G ram, and I would like to scale up at 80% of CPU and 80% ram, should I set the value to be 0.4 cores and 0.8G ram? (then 400 and 800 respectively?)
"scale": {
            "maxReplicas": 10,
            "minReplicas": 1,
            "rules": [
              {
                "custom": {
                  "metadata": {
                    "type": "AverageValue",
                    "value": "400"
                  },
                  "type": "cpu"
                },
                "name": "cpu-scale"
              },
              {
                "custom": {
                  "metadata": {
                    "type": "AverageValue",
                    "value": "800"
                  },
                  "type": "memory"
                },
                "name": "memory-scale"
              }
            ]
          },

Additional context
Related to #740
Thank you!!

Hi, we double check your request, and it seems there was a tail whitespace cause the issue.

Hi @howang-ms,
Thanks for getting back to me.
I don't think this is the cause as I redeployed the container app and the behaviour stays the same behaviour.
From my testing, I'm using this configuration for a container app with 0.25 core CPU and 0.5Gi memory, it will instantly scale up to maximum replicas (10, in my case).
"scale": {
  "maxReplicas": 10,
  "minReplicas": 1,
  "rules": [
    {
      "custom": {
        "metadata": {
          "type": "AverageValue",
          "value": "400"
        },
        "type": "memory"
      },
      "name": "ram-scale"
    },
    {
      "custom": {
        "metadata": {
          "type": "AverageValue",
          "value": "200"
        },
        "type": "cpu"
      },
      "name": "cpu-scale"
    }
  ]
},

My goal is to set up a scaling rule that only scales up when the CPU or memory utilization is above 80%. Ideally I should use Utilization parameter like I mentioned above, but this parameter is somehow not accept by Azure container apps at the moment. Could you please let me know how I could achieve that?


Add documentation about YAML schemas

Several JSON schemas exist to assist in validation and editing of YAML files:

Schema for recyclarr.yml is here.
Schema for settings.yml is here.

Documentation should be added to the wiki that explains why one may want to use these. Personally, I only use VS Code so I'd center the explanation of their usage around that tool. Others may have experience with different tools that offer integration features for schemas.

VS Code can offer real-time analysis of your YAML files as you edit. If you mess up, it will underline issues with red-squigglies.
Usage of this extension for VS Code to provide schema analysis for YAML files.
Language server can be specified in YAML files. Documentation is here.
The template created by the create-config subcommand already inserts the language server spec at the top of the file.

I meant to transfer this issue to the wiki repo but never got to it. Will close this copy.


Rebuild local Vex verilogs with #582 fix.

Signed-off-by: Tim Callahan<EMAIL_ADDRESS>

@davidlattimore reported that hps_accel on proto2 did not function with this PR, and narrowed down the apparent introduction of an incompatibility to this commit: https://github.com/SpinalHDL/VexRiscv/commit/b2e61caf9e62d8febe59eaf654856edec73e5412.
I tried mnv2_first on Arty with this LiteX/VexRiscv/CfuPlugin bump, and it also seems to be malfunctioning.
--> I will see if the issue also shows up in Verilator simulation, and if so, add a regression test for it.

In fact the proj/mnv2_first project malfunction shows up even on current main, since that build directly uses an upstream VexRiscv build.
I've also confirmed that the same malfunctions also occur in Verilator.
Specifically, the malfunctions are:

project menu --> 1x1 test --> hang
TFLM unit tests --> hang
TFLM models --> mnv2 model --> any --> hang after 3 dots

Closing without merging; this is obsolete (superseded by #639).


VMWare doc missing image

https://help.sumologic.com/docs/integrations/containers-orchestration/vmware. .. Just above the header Sample log message, it says "The following image illustrates the collection process." however, there is no image. Can you load the image?
Slack Message

@nmohantyctr will look at this one.

resolved


[Master] wip - fix incremental parsing with dynamic import

Fix #16384

@sandersn can you please review this change


SA1119 false positive for parenthesis around x switch {} expression

https://github.com/n0099/open-tbm/blob/af3fe85e196e0ffaa0fa881e86b2c23999e0f736/c%23/imagePipeline/src/Ocr/PaddleOcrRecognizerAndDetector.cs#L25-L34
https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/operators/switch-expression

Created a pull request since similar cases are already allowed by SA1119.

@bjornhellander Is this not a duplicate of #3200 and/or #3460?

No. What caused it to trigger this time was the invocation on the last line of the provided repro code.
It can be simplified to this: await (x switch ...)(y) but it also triggers on this: (x switch ...)(y)


Add support for Azure Database for MySQL - Flexible Server

Description
Fixes #1230.

Added new test cases in Terratest to support new Azure MySql Flexible Server resource.
Update Azure SDK for GO to the minimum version (v57.1.0) that starts to expose methods for managing new resources; the old Azure MySQL Single Server is still being maintained in newer version of the sdk.
Minor changes on documentation at /examples/azure/README.md.

TODOs
Read the Gruntwork contribution guidelines.

[x] Update the docs.
[ ] Run the relevant tests successfully, including pre-commit checks.
[x] Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)
Added MySQL Flexible Server tests. [X]
Updated version of azure-sdk-go from 50.2.0 to 57.1.0. [X]
Migration Guide

Tried to run tests, and noticed that fails TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example

=== RUN   TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z test_structure.go:130: Copied terraform folder /home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example to /tmp/terraform-azure-mysqldb-flexible-example2144364670/project/examples/azure/terraform-azure-mysqldb-flexible-example
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z retry.go:91: terraform [init -upgrade=false]
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: Running command terraform with args [init -upgrade=false]
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: There are some problems with the configuration, described below.
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66:
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: The Terraform configuration must be valid before initialization so that
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: Terraform can determine which modules and providers need to be installed.
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: ╷
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │ Error: Invalid validation error message
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │   on variables.tf line 85, in variable "mysql_version":
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │   85:     error_message = "MySQL version for Flexbile Server instance should be 5.7 or 8.0.21"
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │ The validation error message must be at least one full sentence starting
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │ with an uppercase letter and ending with a period or question mark.
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │ Your given message will be included as part of a larger Terraform error
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │ message, written as English prose. For broadly-shared modules we suggest
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │ using a similar writing style so that the overall result will be
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │ consistent.
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: ╵
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66:
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z retry.go:99: Returning due to fatal error: FatalError{Underlying: error while running command: exit status 1; There are some problems with the configuration, described below.

Tried to run tests, and noticed that fails TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example

=== RUN   TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z test_structure.go:130: Copied terraform folder /home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example to /tmp/terraform-azure-mysqldb-flexible-example2144364670/project/examples/azure/terraform-azure-mysqldb-flexible-example
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z retry.go:91: terraform [init -upgrade=false]
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: Running command terraform with args [init -upgrade=false]
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: There are some problems with the configuration, described below.
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66:
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: The Terraform configuration must be valid before initialization so that
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: Terraform can determine which modules and providers need to be installed.
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: ╷
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │ Error: Invalid validation error message
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │   on variables.tf line 85, in variable "mysql_version":
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │   85:     error_message = "MySQL version for Flexbile Server instance should be 5.7 or 8.0.21"
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │ The validation error message must be at least one full sentence starting
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │ with an uppercase letter and ending with a period or question mark.
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │ Your given message will be included as part of a larger Terraform error
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │ message, written as English prose. For broadly-shared modules we suggest
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │ using a similar writing style so that the overall result will be
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: │ consistent.
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66: ╵
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z logger.go:66:
TestValidateAllTerraformModulesOnTerratest/home/circleci/project/examples/azure/terraform-azure-mysqldb-flexible-example 2023-02-14T21:17:44Z retry.go:99: Returning due to fatal error: FatalError{Underlying: error while running command: exit status 1; There are some problems with the configuration, described below.

Sorry for the inconvenient! Should be fixed now.
Running on local environment test regarding Flexible Server are working fine, version of terraform is 1.3.9.
Let me know if something else comes up!

@denis256 Let me know if there is anything else that there is need to be done. Unfortunately I cannot trigger any circleci build

Hey @denis256 sorry to disturb you but I was wondering if this PR will be approved or needs further adjustment. Thanks!

Hi @denis256, any update on this?

Hi, it is still not clear status of this PR:

title says [WIP]
there are conflicting files which prevent merging

Conflicting files
go.mod
go.sum

Hi, it is still not clear status of this PR:

title says [WIP]
there are conflicting files which prevent merging

Conflicting files
go.mod
go.sum

Hi @denis256, I have resolved merge conflicts.
I remove [WIP] from the title since tests are passing and no more updates from my side on my branch are needed.


ES6 transform-class-properties

Hello, first thanks for this project.
Just wanted to know how to reconfigure by adding a support of class properties especially for reactjs
Many thanks

Mix checks if there is .babelrc present in project root. For example, the reasonable default disregarding react support would be:
{
  "presets": [
    ["env", {
      "modules": false,
      "targets": {
        "browsers": "> 1%"
      }
    }]
  ]
}

Then you add whatever presets and plugins you need for react here after installing corresponding packages from npm. I am sure that babel-preset-env and babel-preset-react are already bundled with mix.
In short, this isn't really the concern of this project how you handle your babel transformations. The only gotcha is that declaring babel settings in package.json won't work from what I gather skimming through the source files.

An alternative way to add additional babel transformations would be to do something like this in your webpack.mix.js file.
var babelOptions = global.options.babel
if (!babelOptions.plugins)
	babelOptions.plugins = []

babelOptions.plugins.push("transform-decorators-legacy")
babelOptions.plugins.push("transform-class-properties")

I'm not sure there is a better way to get global.options, but there is code throughout the code base that accesses it that way, so monkey see monkey do :D


Add ability to stack bars

When creating a chart with bar series, add ability to switch between 'stacked' mode and 'grouped' mode.
Deliverable: The chart library has an option, 'barsStacked' that when set to true, renders the bars in stacked mode.

Create a new chartItem called bars-stacked that handles this. Keep the code separate from the grouped bars code.
Use d3.layout.stack() to figure out the offsets.
Store the series extents in the normalized internal data structure.

I have it working for positive values. Need to get it working for negative values, and then I am done.