text:
issue running mixtral with latest

Prerequisites
Please answer the following questions for yourself before submitting an issue.

[ x] I am running the latest code. Development is very rapid so there are no tagged versions as of now.
[ x] I carefully followed the README.md.
[ x] I searched using keywords relevant to my issue to make sure that I am creating a new issue that is not already open (or closed).
[x ] I reviewed the Discussions, and have a new bug or useful enhancement to share.

Expected Behavior
I expected a completion as other models work.
Current Behavior
CUDA error 719 at /home/adam/Downloads/llama-cpp-python/vendor/llama.cpp/ggml-cuda.cu:8008: unspecified launch failure
current device: 1
GGML_ASSERT: /home/adam/Downloads/llama-cpp-python/vendor/llama.cpp/ggml-cuda.cu:8008: !"CUDA error"
Environment and Context
Please provide detailed information about your computer setup. This is important in case the issue is not reproducible except for under certain specific conditions.

Physical (or virtual) hardware you are using, e.g. for Linux:

Architecture:            x86_64
CPU op-mode(s):        32-bit, 64-bit
Address sizes:         48 bits physical, 48 bits virtual
Byte Order:            Little Endian
CPU(s):                  12
On-line CPU(s) list:   0-11
Vendor ID:               AuthenticAMD
Model name:            AMD Ryzen 5 4600G with Radeon Graphics
CPU family:          23
Model:               96
Thread(s) per core:  2
Core(s) per socket:  6
Socket(s):           1
Stepping:            1
Frequency boost:     enabled
CPU max MHz:         3700.0000
CPU min MHz:         1400.0000
BogoMIPS:            7386.41
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtsc
p lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe
popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoe
xt perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2
cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsa
veerptr rdpru wbnoinvd cppc arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vm
save_vmload vgif v_spec_ctrl umip rdpid overflow_recov succor smca
Virtualization features:
Virtualization:        AMD-V
Caches (sum of all):
L1d:                   192 KiB (6 instances)
L1i:                   192 KiB (6 instances)
L2:                    3 MiB (6 instances)
L3:                    8 MiB (2 instances)
NUMA:
NUMA node(s):          1
NUMA node0 CPU(s):     0-11
Vulnerabilities:
Gather data sampling:  Not affected
Itlb multihit:         Not affected
L1tf:                  Not affected
Mds:                   Not affected
Meltdown:              Not affected
Mmio stale data:       Not affected
Retbleed:              Mitigation; untrained return thunk; SMT enabled with STIBP protection
Spec rstack overflow:  Mitigation; safe RET
Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2:            Mitigation; Retpolines, IBPB conditional, STIBP always-on, RSB filling, PBRSB-eIBRS Not affected
Srbds:                 Not affected

Operating System, e.g. for Linux:

$ uname -a

SDK version, e.g. for Linux:

Python 3.10.12

GNU Make 4.3
Built for x86_64-pc-linux-gnu

g++ (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Failure Information (for bugs)
Please help provide information about the failure if this is a bug. If it is not a bug, please remove the rest of this template.
Steps to Reproduce
python3 -m llama_cpp.server --model models/mixtral-8x7b-v0.1.Q4_K_M.gguf --n_gpu_layers 33 --host 0.0.0.0
Failure Logs
ggml_init_cublas: GGML_CUDA_FORCE_MMQ:   no
ggml_init_cublas: CUDA_USE_TENSOR_CORES: yes
ggml_init_cublas: found 2 CUDA devices:
Device 0: Tesla P40, compute capability 6.1
Device 1: Tesla P40, compute capability 6.1
llama_model_loader: loaded meta data with 25 key-value pairs and 995 tensors from ../text-generation-webui/models/mixtral-8x7b-v0.1.Q4_K_M.gguf (version GGUF V3 (latest))
...
...
llama_model_loader: - tensor  977:           blk.31.ffn_up.4.weight q4_K     [  4096, 14336,     1,     1 ]
llama_model_loader: - tensor  978:         blk.31.ffn_gate.5.weight q4_K     [  4096, 14336,     1,     1 ]
llama_model_loader: - tensor  979:         blk.31.ffn_down.5.weight q4_K     [ 14336,  4096,     1,     1 ]
llama_model_loader: - tensor  980:           blk.31.ffn_up.5.weight q4_K     [  4096, 14336,     1,     1 ]
llama_model_loader: - tensor  981:         blk.31.ffn_gate.6.weight q4_K     [  4096, 14336,     1,     1 ]
llama_model_loader: - tensor  982:         blk.31.ffn_down.6.weight q4_K     [ 14336,  4096,     1,     1 ]
llama_model_loader: - tensor  983:           blk.31.ffn_up.6.weight q4_K     [  4096, 14336,     1,     1 ]
llama_model_loader: - tensor  984:         blk.31.ffn_gate.7.weight q4_K     [  4096, 14336,     1,     1 ]
llama_model_loader: - tensor  985:         blk.31.ffn_down.7.weight q4_K     [ 14336,  4096,     1,     1 ]
llama_model_loader: - tensor  986:           blk.31.ffn_up.7.weight q4_K     [  4096, 14336,     1,     1 ]
llama_model_loader: - tensor  987:       blk.31.ffn_gate_inp.weight f16      [  4096,     8,     1,     1 ]
llama_model_loader: - tensor  988:          blk.31.attn_norm.weight f32      [  4096,     1,     1,     1 ]
llama_model_loader: - tensor  989:           blk.31.ffn_norm.weight f32      [  4096,     1,     1,     1 ]
llama_model_loader: - tensor  990:             blk.31.attn_k.weight q8_0     [  4096,  1024,     1,     1 ]
llama_model_loader: - tensor  991:        blk.31.attn_output.weight q4_K     [  4096,  4096,     1,     1 ]
llama_model_loader: - tensor  992:             blk.31.attn_q.weight q4_K     [  4096,  4096,     1,     1 ]
llama_model_loader: - tensor  993:             blk.31.attn_v.weight q8_0     [  4096,  1024,     1,     1 ]
llama_model_loader: - tensor  994:               output_norm.weight f32      [  4096,     1,     1,     1 ]
llama_model_loader: Dumping metadata keys/values. Note: KV overrides do not apply in this output.
llama_model_loader: - kv   0:                       general.architecture str              = llama
llama_model_loader: - kv   1:                               general.name str              = mistralai_mixtral-8x7b-v0.1
llama_model_loader: - kv   2:                       llama.context_length u32              = 32768
llama_model_loader: - kv   3:                     llama.embedding_length u32              = 4096
llama_model_loader: - kv   4:                          llama.block_count u32              = 32
llama_model_loader: - kv   5:                  llama.feed_forward_length u32              = 14336
llama_model_loader: - kv   6:                 llama.rope.dimension_count u32              = 128
llama_model_loader: - kv   7:                 llama.attention.head_count u32              = 32
llama_model_loader: - kv   8:              llama.attention.head_count_kv u32              = 8
llama_model_loader: - kv   9:                         llama.expert_count u32              = 8
llama_model_loader: - kv  10:                    llama.expert_used_count u32              = 2
llama_model_loader: - kv  11:     llama.attention.layer_norm_rms_epsilon f32              = 0.000010
llama_model_loader: - kv  12:                       llama.rope.freq_base f32              = 1000000.000000
llama_model_loader: - kv  13:                          general.file_type u32              = 15
llama_model_loader: - kv  14:                       tokenizer.ggml.model str              = llama
llama_model_loader: - kv  15:                      tokenizer.ggml.tokens arr[str,32000]   = ["", "", "", "<0x00>", "<...
llama_model_loader: - kv  16:                      tokenizer.ggml.scores arr[f32,32000]   = [0.000000, 0.000000, 0.000000, 0.0000...
llama_model_loader: - kv  17:                  tokenizer.ggml.token_type arr[i32,32000]   = [2, 3, 3, 6, 6, 6, 6, 6, 6, 6, 6, 6, ...
llama_model_loader: - kv  18:                tokenizer.ggml.bos_token_id u32              = 1
llama_model_loader: - kv  19:                tokenizer.ggml.eos_token_id u32              = 2
llama_model_loader: - kv  20:            tokenizer.ggml.unknown_token_id u32              = 0
llama_model_loader: - kv  21:            tokenizer.ggml.padding_token_id u32              = 0
llama_model_loader: - kv  22:               tokenizer.ggml.add_bos_token bool             = true
llama_model_loader: - kv  23:               tokenizer.ggml.add_eos_token bool             = false
llama_model_loader: - kv  24:               general.quantization_version u32              = 2
llama_model_loader: - type  f32:   65 tensors
llama_model_loader: - type  f16:   32 tensors
llama_model_loader: - type q8_0:   64 tensors
llama_model_loader: - type q4_K:  833 tensors
llama_model_loader: - type q6_K:    1 tensors
llm_load_vocab: special tokens definition check successful ( 259/32000 ).
llm_load_print_meta: format           = GGUF V3 (latest)
llm_load_print_meta: arch             = llama
llm_load_print_meta: vocab type       = SPM
llm_load_print_meta: n_vocab          = 32000
llm_load_print_meta: n_merges         = 0
llm_load_print_meta: n_ctx_train      = 32768
llm_load_print_meta: n_embd           = 4096
llm_load_print_meta: n_head           = 32
llm_load_print_meta: n_head_kv        = 8
llm_load_print_meta: n_layer          = 32
llm_load_print_meta: n_rot            = 128
llm_load_print_meta: n_gqa            = 4
llm_load_print_meta: f_norm_eps       = 0.0e+00
llm_load_print_meta: f_norm_rms_eps   = 1.0e-05
llm_load_print_meta: f_clamp_kqv      = 0.0e+00
llm_load_print_meta: f_max_alibi_bias = 0.0e+00
llm_load_print_meta: n_ff             = 14336
llm_load_print_meta: n_expert         = 8
llm_load_print_meta: n_expert_used    = 2
llm_load_print_meta: rope scaling     = linear
llm_load_print_meta: freq_base_train  = 1000000.0
llm_load_print_meta: freq_scale_train = 1
llm_load_print_meta: n_yarn_orig_ctx  = 32768
llm_load_print_meta: rope_finetuned   = unknown
llm_load_print_meta: model type       = 7B
llm_load_print_meta: model ftype      = mostly Q4_K - Medium
llm_load_print_meta: model params     = 46.70 B
llm_load_print_meta: model size       = 24.62 GiB (4.53 BPW)
llm_load_print_meta: general.name     = mistralai_mixtral-8x7b-v0.1
llm_load_print_meta: BOS token        = 1 ''
llm_load_print_meta: EOS token        = 2 ''
llm_load_print_meta: UNK token        = 0 ''
llm_load_print_meta: PAD token        = 0 ''
llm_load_print_meta: LF token         = 13 '<0x0A>'
llm_load_tensors: ggml ctx size =    0.39 MiB
llm_load_tensors: using CUDA for GPU acceleration
llm_load_tensors: mem required  =   70.71 MiB
llm_load_tensors: offloading 32 repeating layers to GPU
llm_load_tensors: offloading non-repeating layers to GPU
llm_load_tensors: offloaded 33/33 layers to GPU
llm_load_tensors: VRAM used: 25145.55 MiB
....................................................................................................
llama_new_context_with_model: n_ctx      = 2048
llama_new_context_with_model: freq_base  = 1000000.0
llama_new_context_with_model: freq_scale = 1
llama_kv_cache_init: VRAM kv self = 256.00 MB
llama_new_context_with_model: KV self size  =  256.00 MiB, K (f16):  128.00 MiB, V (f16):  128.00 MiB
llama_build_graph: non-view tensors processed: 1124/1124
llama_new_context_with_model: compute buffer total size = 187.35 MiB
llama_new_context_with_model: VRAM scratch buffer: 184.04 MiB
llama_new_context_with_model: total VRAM used: 25585.59 MiB (model: 25145.55 MiB, context: 440.04 MiB)
AVX = 1 | AVX2 = 1 | AVX512 = 0 | AVX512_VBMI = 0 | AVX512_VNNI = 0 | FMA = 1 | NEON = 0 | ARM_FMA = 0 | F16C = 1 | FP16_VA = 0 | WASM_SIMD = 0 | BLAS = 1 | SSE3 = 1 | SSSE3 = 1 | VSX = 0 |
INFO:     Started server process [144728]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit)
CUDA error 719 at /home/adam/Downloads/llama-cpp-python/vendor/llama.cpp/ggml-cuda.cu:8008: unspecified launch failure
current device: 1
GGML_ASSERT: /home/adam/Downloads/llama-cpp-python/vendor/llama.cpp/ggml-cuda.cu:8008: !"CUDA error"
Aborted (core dumped)

Do you get this same error when you run the llama.cpp equivalent of this?
git clone --recurse-submodules https://github.com/abetlen/llama-cpp-python.git
cd llama-cpp-python/vendor/llama.cpp/
mkdir build
cd build
cmake ..
cmake --build . --config Release
./bin/server --model models/mixtral-8x7b-v0.1.Q4_K_M.gguf --n-gpu-layers 33 --host 0.0.0.0
``

I doesn't look like bin is created from that. After building according to your suggesting I get the following error:
-bash: ./bin/server: No such file or directory
The debug info is below
dam@mojoserver:~/Downloads/llama-cpp-python/build$ cmake --build . --config Release
[  4%] Building C object vendor/llama.cpp/CMakeFiles/ggml.dir/ggml.c.o
[  9%] Building C object vendor/llama.cpp/CMakeFiles/ggml.dir/ggml-alloc.c.o
[ 13%] Building C object vendor/llama.cpp/CMakeFiles/ggml.dir/ggml-backend.c.o
[ 18%] Building C object vendor/llama.cpp/CMakeFiles/ggml.dir/ggml-quants.c.o
[ 18%] Built target ggml
[ 22%] Linking C static library libggml_static.a
[ 22%] Built target ggml_static
[ 27%] Linking C shared library libggml_shared.so
[ 27%] Built target ggml_shared
[ 31%] Building CXX object vendor/llama.cpp/CMakeFiles/llama.dir/llama.cpp.o
[ 36%] Linking CXX shared library libllama.so
[ 36%] Built target llama
[ 40%] Building CXX object vendor/llama.cpp/common/CMakeFiles/build_info.dir/build-info.cpp.o
[ 45%] Built target build_info
[ 50%] Building CXX object vendor/llama.cpp/common/CMakeFiles/common.dir/common.cpp.o
[ 54%] Building CXX object vendor/llama.cpp/common/CMakeFiles/common.dir/sampling.cpp.o
[ 59%] Building CXX object vendor/llama.cpp/common/CMakeFiles/common.dir/console.cpp.o
[ 63%] Building CXX object vendor/llama.cpp/common/CMakeFiles/common.dir/grammar-parser.cpp.o
[ 68%] Building CXX object vendor/llama.cpp/common/CMakeFiles/common.dir/train.cpp.o
[ 72%] Linking CXX static library libcommon.a
[ 72%] Built target common
[ 77%] Building CXX object vendor/llama.cpp/examples/llava/CMakeFiles/llava.dir/llava.cpp.o
[ 81%] Building CXX object vendor/llama.cpp/examples/llava/CMakeFiles/llava.dir/clip.cpp.o
[ 81%] Built target llava
[ 86%] Linking CXX static library libllava_static.a
[ 86%] Built target llava_static
[ 90%] Linking CXX shared library libllava.so
[ 90%] Built target llava_shared
[ 95%] Building CXX object vendor/llama.cpp/examples/llava/CMakeFiles/llava-cli.dir/llava-cli.cpp.o
[100%] Linking CXX executable llava-cli
[100%] Built target llava-cli

after running those commands using the llama.cpp project I get a successful load.
However when using something like autgen to talk to server I get the error "File not found"
Error: ... "role": "user"}], "model": "../../text-generation-webui/models/mixtral-8x7b-v0.1.Q4_K_M.gguf", "max_tokens": 4096, "stream": false, "temperature": 0.2}","response":"File Not Found"}
Load debug:
llama_new_context_with_model: n_ctx      = 512
llama_new_context_with_model: freq_base  = 1000000.0
llama_new_context_with_model: freq_scale = 1
llama_kv_cache_init: VRAM kv self = 64.00 MB
llama_new_context_with_model: KV self size  =   64.00 MiB, K (f16):   32.00 MiB, V (f16):   32.00 MiB
llama_build_graph: non-view tensors processed: 1124/1124
llama_new_context_with_model: compute buffer total size = 117.72 MiB
llama_new_context_with_model: VRAM scratch buffer: 114.54 MiB
llama_new_context_with_model: total VRAM used: 25324.09 MiB (model: 25145.55 MiB, context: 178.54 MiB)
Available slots:
-> Slot 0 - max context: 512
llama server listening at http://0.0.0.0:8080

This seems to be a CUDA thing on the llama.cpp side

I am going to close and continue issue with llama.cpp.
This is the error running the server from llama.cpp server:
llama_new_context_with_model: n_ctx      = 512
llama_new_context_with_model: freq_base  = 1000000.0
llama_new_context_with_model: freq_scale = 1
llama_kv_cache_init: VRAM kv self = 64.00 MB
llama_new_context_with_model: KV self size  =   64.00 MiB, K (f16):   32.00 MiB, V (f16):   32.00 MiB
llama_build_graph: non-view tensors processed: 1124/1124
llama_new_context_with_model: compute buffer total size = 117.72 MiB
llama_new_context_with_model: VRAM scratch buffer: 114.54 MiB
llama_new_context_with_model: total VRAM used: 25324.09 MiB (model: 25145.55 MiB, context: 178.54 MiB)
Available slots:
-> Slot 0 - max context: 512
llama server listening at http://0.0.0.0:8080
{"timestamp":1702752484,"level":"INFO","function":"main","line":3093,"message":"HTTP server listening","port":"8080","hostname":"0.0.0.0"}
all slots are idle and system prompt is empty, clear the KV cache
slot 0 is processing [task id: 0]
slot 0 : kv cache rm - [0, end)
CUDA error 719 at /home/adam/Downloads/llama.cpp/ggml-cuda.cu:8008: unspecified launch failure
current device: 1
GGML_ASSERT: /home/adam/Downloads/llama.cpp/ggml-cuda.cu:8008: !"CUDA error"
Aborted (core dumped)

@alienatorZ I am getting the same. Shorter prompts do fine, going from a Q6 to Q5 also increases the amount of tokens I can input before getting the same error.

I have similary error with oobabooga and mixtral
CUDA error 719 at /home/runner/work/llama-cpp-python-cuBLAS-wheels/llama-cpp-python-cuBLAS-wheels/vendor/llama.cpp/ggml-cuda.cu:8019: unspecified launch failure
current device: 0

authors: alienatorZ brandonrobertz kkaarrss zwilch

repo: abetlen/llama-cpp-python


text:
Added feature: new testimonial for mens

Feat: #15
Added new testimonial for mens
Both swiper component in the same container

It is responsive also

Misaligment is there @Faisalhs51

correct it Up.

there is still some misalingment in the swiper cards and minor issue in the navbar

Completed the changes
@abhay-raj19 please review it now

now it looks good @Faisalhs51 .

source: gharchive/pull-request

license: MIT

license_type: permissive

license_source: github-api


text:
Change flattenJSONObject to return POSIX compliant names

Closes https://github.com/abhilash1in/aws-secrets-manager-action/issues/20

Should I remove the lock?

@cbui Thank you for your contribution!

Should I remove the lock?

Yes, please. I'll update package-lock.json in a separate commit after bumping up a few dependencies.
The PR looks good on the first glance. Will take another look at merge it in.

Removed.

@cbui Thank you for your contribution!

Thank you for this action 🥇

@cbui @abhilash1in Just FYI I don't think this PR is working

authors: abhilash1in cbui emmanuelnk


text:
Feature: Adding new PRs

There are a lot of pending requests, including mine. I think it would be cool if they are checked/ reviewed 😄

This repo seems completely unattended!

source: gharchive/issue

authors: krishnapriya-n metaory


text:
gpt-4o-2024-05-13 does not exist

I can't finish the process and got the error message :
[GENERATE_CODE] Model not found Error code: 404 - {'error': {'message': 'The model gpt-4o-2024-05-13 does not exist or you do not have access to it.', 'type': 'invalid_request_error', 'param': None, 'code': 'model_not_found'}}
Is there any method to solve this issue.

Have you followed the instructions in the README to deposit $5 to get gpt 4 access?

@abi Hi, I have explored the screenshot to code in detail since some time and wish to contribute, is there any issue or feature which I can work upon? Thanks

Thanks, @naman1608 feel free to pick up any of the open issues.

authors: SongOnWater abi naman1608

repo: abi/screenshot-to-code


text:
idba_subasm processes using 2 threads per process, overloading server

I have noticed when running Athena with multiple threads that the spawned processes for idba_subasm are running with two threads apiece.

The Python code, which I am guessing processes the output, each actively use roughly one core apiece.

If we try to automate this a bit and run this on a cluster where the number of threads/cores per job can be set dynamically per job, for example SLURM:
athena-meta -t $SLURM_NPROCS --config myconfig.json

this leads to load problems.  For example, on a small 12 core node this launches Athena with 12 threads.  However, when I've monitored this via top there are 12 processes running (a mix of idba_asm and python) with the idba_subasm processes requested more threads than are available, roughly about 30-40% more, which is causing issues with load.
For the time being we're simply modifying the threads in the athena-meta call to about 2/3 of what are expected (8 threads for a 12 core node).  But is there a way to account for this within athena?

Hi,
Right now, each subassembly step using idba is specified to use 2 threads as a hard-coded constant.  I think your measure to scale back the number of threads to Athena compared to the resource limit so that the peak number of active threads is less than this limit is a good for now.   Are you observing significant performance degradation without doing that?
Thanks,
alex

Hi @abishara we were seeing the server running with a very high load which appeared to degrade overall performance. We're also running this SLURM using cgroups which can restrict resource use as well, though we are utilizing the entire node.

Hmm, is the solution you suggested working fine for now?  I guess I'm a little unclear on what you would like me to do.  I'm open to a suggestion if you have one now that I have explained the implementation detail.
Thanks,
alex

The workaround is fine for now, but I think the best fix would be for Athena to launch the various subassembly processes in a manner that scales to the threads set in the command line call, otherwise I expect other parallel steps can't take full advantage of the set number of threads.  Not sure how easy this would be to implement though.

I agree this is ideal, but I don't really see a simple solution for how to implement this at the moment.  Right now idba is invoked as a black box and I don't really have fine-grained control over how it uses threads.

Agreed.  I suspect the easiest solution may be to use the cluster-based approach (e.g. use SLURM to submit these as jobs).

authors: abishara cjfields

license: mit

license_source: bigquery


text:
converted project to class library

In case your interested, I have updated the project to a class library

Hi,
I'm not sure I understand why you have converted the project to a class library. The project has quite a few web files (js, apsx etc.), and the project being a web project generally makes things easier in Visual Studio.
You mentioned in #3 that is was to use in one of your own projects. What kind of project is this? I have no problems adding a reference to Skybrud.Social.Umbraco.

I added the source code project to my own project because I had to make
some changes but you implemented them a few days ago so I got to pull it
out and just use a compiled version :) yah!
The reason I made it a class library in case your wondering though is
because it was affecting my build process stuff. If its a web site project
then it expects some funky publishing files to be present. Class Libraries
don't need that.
Anyway, thanks again.
I am using your project to build this page
http://www.pampas.com.au/inspiration/ and we have another one coming out
soon which uses facebook. It will be combining items from multiple social
sources later.
Regards
On Wed, Feb 25, 2015 at 11:17 PM, Anders Bjerner notifications@github.com
wrote:

Hi,
I'm not sure I understand why you have converted the project to a class
library. The project has quite a few web files (js, apsx etc.), and the
project being a web project generally makes things easier in Visual Studio.
You mentioned in #3
https://github.com/abjerner/Skybrud.Social.Umbraco/issues/3 that is was
to use in one of your own projects. What kind of project is this? I have no
problems adding a reference to Skybrud.Social.Umbraco.
—
Reply to this email directly or view it on GitHub
https://github.com/abjerner/Skybrud.Social.Umbraco/pull/5#issuecomment-75950497
.

--
[image: Liquid Visual] http://ewide.com.au/Ben NormanWeb Developer / .NET
Specialiste  support@ewide.biz  t  (+61) 404 828 246
w  ewide.com.au

As the code is structured now, it would be easier for me to maintain as a web project (due to web files), so for now I will have to reject your pull request.
A plan for the future is however to separate the code into two separate projects - a class library only containing the C# classes, and web project containing JavaScript and CSS as well as .aspx files (and code-behind classes related to those). I haven't yet decided how I want to proceed, but there is a good chance that I will settle with this structure.

authors: EnterpriseWide abjerner


text:
Synchronous API for creating instances and Hot-reload fix

This PR mainly focuses on creating Ably instances in a synchronous manner.
The following changes were made possible as all other operations on each ably instances is an asynchronous operation.
If not async? then, Sync + Lazy = Slazy!!! 😉

All platform calls from dart side are made lazy
Singleton Ably library instances on Android side (iOS will be caught up)

A peek on new APIs
import 'package:ably_flutter_plugin/ably.dart' as ably;

final clientOptions = ably.ClientOptions.fromKey("<YOUR APP KEY>");
clientOptions.logLevel = ably.LogLevel.verbose; //optional
ably.Rest rest = ably.Ably.Rest(options: clientOptions);

function testRest(){
  ably.RestChannel channel = rest.channels.get('test');
  await channel.publish(name: "Hello", data: "Ably");
}

function testRealtime(){
  ably.Realtime realtime = ably.Ably.Realtime(options: clientOptions);
    realtime.connection.on().listen((ably.ConnectionStateChange stateChange) async {
    print('Realtime connection state changed: ${stateChange.event}');
  });
}

Hot-reload issue fix 🌶  ♻  🎉  🎉

registerAbly is now used to dispose off any registered platform instances
Android StreamsChannel source is replicated and necessary changes are made to dispose all listeners on hot-reload (Will be removing the streams_channel plugin dependency eventually)

NOTE: Draft PR supporting Android only.

@QuintinWillison @mattheworiordan @paddybyers Please share your feedback on the API. Will make necessary changes and proceed with implementing iOS platform related changes.

Thanks for the responses to my review comments, @tiholic.
I think there are still a few improvements before we can merge this. Thanks.

@QuintinWillison Yeah, this PR is still in draft state. I just getting some inputs on how the final API should look like.
Now that we have enough information to proceed further, I will finish iOS implementation and try to address all the unresolved comments from above.

@QuintinWillison iOS side caught up, if the runway is clear for landing, we can merge this.
Regarding the pubspec.lock changes, that was probably due to automatic minor version upgrade behavior.
^A.B.C will upgrade packages if minor version releases are available. If we need strict version for dependencies, we can go with package: 'A.B.C' instead of package: '^A.B.C' (ref: https://dart.dev/tools/pub/dependencies)
Updated DeveloperNotes with instructions on static code analysis (includes all build time checks)

Regarding pubspec.lock changes, I'm happy to leave things as they are for now and thank you for explaining. 😁
There is perhaps a wider discussion to be had here at Ably, across all client libraries, around dependency version management / auto management.

authors: QuintinWillison tiholic

repo: ably/ably-flutter


text:
Include docker image in metadata

Hi,
Would it be possible to add the docker image name:tag to the metadata? It is available from kube pod information and the container_id is already known from the log. This would allow to trace logs back to specific versions of pods/applications/containers in fast-moving environments, quite a valuable addition in my opinion.
I've looked through the code (I'm not a very experienced ruby developer) and it looks to me like this could be added without too much issues, but I'm not familiar enough to take a stab without getting some feedback where and how this would be best implemented..

Wrong repo, sorry..

repo: abonas/kubeclient


text:
Conan tag 20190416

As Conan exports the library list instead of using CMake targets, and Abseil can change the library names, we need to tag a specific version to list all correct   libraries.
When using all libraries together, a specific order must be respected. We have used --start-group solve any order problem, however this is not a good approach.
A new tag can be created monthly or when requested by issue.
/cc @lasote
related issue: https://github.com/conan-io/conan/issues/4928

@uilianries Thank you for this contribution. Could you please provide build/test logs/evidence before/after to prove that this change indeed does what it intends to do. Abseil does not have Conan in the regular CI build matrix so we need to see that this "does not harm" and "works as intended"
Thank you !

Hi @gennadiycivil !
To validate this build using Conan, you could follow these steps:
git clone https://github.com/uilianries/abseil-cpp.git
cd abseil-cpp
git checkout feature/conan-version
docker run --rm -v ${PWD}:/home/conan/project conanio/gcc8 /bin/bash -c "cd project && conan create . abseil/testing -tf .conan/test_package"

This Docker image contains Conan 1.17.1 + CMake 3.15 + GCC 8. It will build Abseil by running Conan. The version related in the Conan recipe is the latest commit available.
The folder .conan/test_package is a test to check if the generated Conan package is okay. It simulates an external project which consumes Abseil Conan package and build a minimal application. The test is only check the Conan package, not Abseil project.
You can read the full log here: build.log

I tried to validate this per your directions and got the following failure: build_fail.log
I snuck a find command into the docker commandline to see where the missing file wound up; any idea what's wrong here?

This PR hasn't had any activity in many months, so I'm going to close it.  Please reopen or start a new PR as appropriate if further changes are needed.

authors: gennadiycivil suertreus uilianries

repo: abseil/abseil-cpp


text:
🛑 Caja Registradora (App) is down

In 67226a1, Caja Registradora (App) (https://caja.absor.top) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Caja Registradora (App) is back up in e7ce37c.

repo: absortian/AbsorStatus


text:
Change in make:view panels to adminlte box

We use default Laravel panel use instead adminltebox

Solved in last commit https://github.com/acacha/adminlte-laravel/commits/master

https://github.com/acacha/adminlte-laravel/commit/ad1ebc374330120eab5f09ceba34844655d795dd

repo: acacha/adminlte-laravel


text:
Creatures on board lose healthChange, oppHealthChange and cardDraw attributes after participating in attack or use actions

Hi!
Disclaimer: this is going to have way too much text for what it's really worth 😂
I am currently working towards ensuring that gym-locm's engine is 100% consistent with referee-java in the sense that, if an identical match (including the deck shuffling) is played on both gym-locm's engine and referee-java by the same deterministic agents, then all (state -> actions -> next_state) tuples in that match should also be identical on both engines.
With that said, I noticed that, on referee-java, after a summoned creature participates in an ATTACK or USE action, its healthChange, oppHealthChange, or cardDraw attributes are set to zero (in case they weren't already). It's not a very important issue since I don't think any agents really care about those "summon-time abilities" after the creature have been summoned, but I'd like to ask if this behavior is intentional or is a very small bug, so I can fix accordingly on gym-locm's engine.
Here's an example:
(Turn X)
27 4 21 25 1
31 4 22 25 1
4 2
99 ATTACK 1 2
13 SUMMON 15 0 # creature 15 is summoned
9
113 4 0 0 6 2 4 ---G-- 4 0 0 -1
106 8 0 0 5 5 5 ---G-- 0 0 0 -1
77 12 0 0 7 7 7 B----- 0 0 0 -1
94 14 0 0 2 1 4 ---G-- 0 0 0 -1
13 16 0 0 4 5 3 ------ 1 -1 0 -1
81 18 0 0 9 6 6 BC---- 0 0 0 -1
99 2 1 0 3 2 3 ---G-- 0 0 0 0
99 1 -1 0 3 2 3 ---G-- 0 0 0 0
13 15 -1 0 4 5 3 ------ 1 -1 0 0 # creature 15 with "1 -1 0"

(Turn X+1, same player)
26 5 20 25 1
30 5 21 25 1
4 3
13 ATTACK 15 2 # creature 15 attacks
99 ATTACK 1 -1
106 SUMMON 7 0
10
113 4 0 0 6 2 4 ---G-- 4 0 0 -1
106 8 0 0 5 5 5 ---G-- 0 0 0 -1
77 12 0 0 7 7 7 B----- 0 0 0 -1
94 14 0 0 2 1 4 ---G-- 0 0 0 -1
81 18 0 0 9 6 6 BC---- 0 0 0 -1
79 20 0 0 8 8 8 B----- 0 0 0 -1
13 16 1 0 4 5 3 ------ 1 -1 0 0
99 1 -1 0 3 2 1 ---G-- 0 0 0 0
13 15 -1 0 4 5 1 ------ 0 0 0 0 # creature 15 now with "0 0 0"
106 7 -1 0 5 5 5 ---G-- 0 0 0 0

In case it's not intentional, what I think it's happening code-wise is very simple:
The CreatureOnBoard class on referee-java have these constructors:

public CreatureOnBoard (Card card, int lane), used on SUMMON.
public CreatureOnBoard (CreatureOnBoard creature), used on ATTACK or USE.

While constructor 1 carries on the "summon-time abilities" from the Card to the CreatureOnBoard instance, constructor 2 doesn't carry them from the old CreatureOnBoard instance to the new one, and since the default value for ints in Java is 0, they remain 0.

Nice catch - although, as you said, it does not have any actual impact.
As far as I remember, it was done for simplicity and efficiency (possibly even to not mislead players with 'unnecessary' values).
Our other implementations (Nim, Rust) do not work this way.

Thanks!

authors: acatai ronaldosvieira


text:
Add support for creating template tests

This could be done by having a create test button on the execution tab. We may need a test pane.

This issue has been moved to https://github.com/accordproject/react-components/issues/9

repo: accordproject/template-studio


text:
add the toClass component helper

In response to https://github.com/acdlite/recompose/issues/34.

Thanks!

authors: acdlite py-in-the-sky

repo: acdlite/recompose


text:
Train sentiment analysis in Web Worker

The sentiment analysis is a bit slow. Perhaps using a Web Worker would allow me to offload it to a different "thread"?

The problem is now that I can't get it to run only once. Instead, it keeps loading the model over and over until it gets rate limited 🤦♂

This was a good idea in principle, but it doesn't work.
I've added some UX improvements (i.e. just letting the user know that the email is being sent).

repo: aceade/sydfjords


text:
🛑 AceBlock Swagger UI is down

In 7decc72, AceBlock Swagger UI ($ACEBLOCK_SWAGGER_UI) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AceBlock Swagger UI is back up in 8173d3c.

repo: aceblockID/monitoring


text:
🛑 AceBlock Swagger UI is down

In 4c73eb7, AceBlock Swagger UI ($ACEBLOCK_SWAGGER_UI) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AceBlock Swagger UI is back up in b23b483.


text:
Support Node.js v19

It seems Node.js v19 is not yet supported?
yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
error @achrinza/node-ipc@9.2.5: The engine "node" is incompatible with this module. Expected version "8 || 9 || 10 || 11 || 12 || 13 || 14 || 15 || 16 || 17 || 18". Got "19.0.0"
error Found incompatible module.

Thanks for raising the issue! Support has been added to the necessary packages:

@achrinza/event-pubsub@5.0.8

https://www.npmjs.com/package/@achrinza/event-pubsub/v/5.0.8
https://github.com/achrinza/event-pubsub/releases/tag/v5.0.8

@achrinza/node-ipc@10.1.7

https://www.npmjs.com/package/@achrinza/node-ipc/v/10.1.7
https://github.com/achrinza/node-ipc/releases/tag/v10.1.7

@achrinza/node-ipc@9.2.6

https://www.npmjs.com/package/@achrinza/node-ipc/v/9.2.6
https://github.com/achrinza/node-ipc/releases/tag/v9.2.6

@achrinza/strong-type@1.1.4

https://www.npmjs.com/package/@achrinza/strong-type/v/1.1.4
https://github.com/achrinza/strong-type/releases/tag/v1.1.4

@achrinza/strong-type@0.1.10

https://www.npmjs.com/package/@achrinza/strong-type/v/0.1.10
https://github.com/achrinza/strong-type/releases/tag/v0.1.10

Thx a lot :muscle:

authors: achrinza jokay

repo: achrinza/node-ipc


text:
autoupgrade format "**" does not work as expected.

acorn version v0.6.0-81-g5856fe34+5856fe34
Steps to reproduce the issue:
Have the following image tags:
acorn images
REPOSITORY                           TAG          IMAGE-ID
mytest2                              v0.0.1-rc1   8705f66f67e6
mytest2                              v0.0.2       fa11bfd2b180

Deploy app with "**" autoupgrade tag in image
 acorn run -n mytestk3 --interval 15s "mytest2:v#.#.#**"
mytestk3
STATUS: ENDPOINTS[] HEALTHY[0] UPTODATE[0] [image-pull: waiting for image to satisfy auto-upgrade tag v#.#.#**]
STATUS: ENDPOINTS[] HEALTHY[0] UPTODATE[0] pending
STATUS: ENDPOINTS[] HEALTHY[0/1] UPTODATE[1] [containers: myweb1 ContainerCreating]
STATUS: ENDPOINTS[http://myweb1-mytestk3-11fcb466.local.on-acorn.io => myweb1:80] HEALTHY[0/1] UPTODATE[1] [containers: myweb1 ContainerCreating]
┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
| STATUS: ENDPOINTS[http://myweb1-mytestk3-11fcb466.local.on-acorn.io => myweb1:80] HEALTHY[1] UPTODATE[1] OK |
└─────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
| STATUS: ENDPOINTS[http://myweb1-mytestk3-11fcb466.local.on-acorn.io => myweb1:80] HEALTHY[1] UPTODATE[1] OK |
└─────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

App gets deployed with mytest2:v0.0.1-rc1 image.
Expected Behavior:
App should get deployed with mytest2:v0.0.2 image.

Never mind. I found a very easy fix for this.

Tested with acorn version v0.6.0-150-g76e7d0a4+76e7d0a4
acorn images
mynew                                    v0.0.1-rc1   df447c241e1a
mynew                                    v0.0.2       ced7ab440ace

acorn run -n mytestk3 --interval 15s "mynew:v#.#.#**"

acorn apps
NAME            IMAGE                                            HEALTHY   UP-TO-DATE   CREATED   ENDPOINTS                                                             MESSAGE
mytestk3        mynew:v0.0.2                                     1         1            14s ago   http://myweb1-mytestk3-11fcb466.local.on-acorn.io => myweb1:80        OK

repo: acorn-io/acorn


text:
Is it supposed to work on Heroku?

When I ran it locally, it worked. But when I deployed to Heroku (free tier, used default settings), the start page looked broken like the screen capture below, and I could not see the device page.
https://imgur.com/a/70MEi

It looks like Bower was not used to install the Polymer elements. Are there any logs in the developer console? It should work fine for me.

Thank you for the information. As a novice of Google Home and Node.js (I mean, I would have chosen another language if the sample were provided in different languages than Node.js), I just wanted to run it as it is. The only things I changed were the API key and the "start" script. At first I used the "start" as it was, but it did not run, so I changed it as the code below as showed in the read me.
  "scripts": {
    "start": "node cloud/smart-home-provider-cloud.js smart-home=\"https://****.herokuapp.com\"",
    "test": "echo \"Error: no test specified\" && exit 1"
  },

The build log.
-----> Node.js app detected
-----> Creating runtime environment

       NPM_CONFIG_LOGLEVEL=error
       NODE_VERBOSE=false
       NODE_ENV=production
       NODE_MODULES_CACHE=true
-----> Installing binaries
       engines.node (package.json):  >=6.2.2
       engines.npm (package.json):   unspecified (use default)

       Resolving node version >=6.2.2...
       Downloading and installing node 9.8.0...
       Using default npm version: 5.6.0
-----> Restoring cache
       Loading 2 from cacheDirectories (default):
       - node_modules
       - bower_components (not cached - skipping)
-----> Building dependencies
       Installing node modules (package.json + package-lock)
       up to date in 0.981s
-----> Caching build
       Clearing previous node cache
       Saving 2 cacheDirectories (default):
       - node_modules
       - bower_components (nothing to cache)
-----> Pruning devDependencies
       Skipping because npm 5.6.0 sometimes fails when running 'npm prune' due to a known issue
       https://github.com/npm/npm/issues/19356

       You can silence this warning by updating to at least npm 5.7.1 in your package.json
       https://devcenter.heroku.com/articles/nodejs-support#specifying-an-npm-version
-----> Build succeeded!
-----> Discovering process types
       Procfile declares types     -> (none)
       Default types for buildpack -> web
-----> Compressing...
       Done: 25M
-----> Launching...
       Released v4
       https://****.herokuapp.com/ deployed to Heroku

Application log when I accessed the site with a web browser.
2018-03-11T17:51:35.432362+00:00 heroku[router]: at=info method=GET path="/bower_components/paper-dialog/paper-dialog.html" host=*****.herokuapp.com request_id=fa5ad548-d855-45aa-9c23-865900ce9b7f fwd="27.118.**.**" dyno=web.1 connect=1ms service=23ms status=404 bytes=430 protocol=https
2018-03-12T17:43:47.750458+00:00 heroku[web.1]: Unidling
2018-03-12T17:43:50.447553+00:00 heroku[web.1]: Starting process with command `npm start`
2018-03-12T17:43:52.378449+00:00 app[web.1]:

2018-03-12T17:43:52.378474+00:00 app[web.1]: > smart-home-app-sample@0.0.1 start /app

2018-03-12T17:43:52.378477+00:00 app[web.1]: > node cloud/smart-home-provider-cloud.js smart-home="https://*****.herokuapp.com"

2018-03-12T17:43:52.378479+00:00 app[web.1]:
2018-03-12T17:43:52.829708+00:00 app[web.1]: config:  { devPortSmartHome: '3000',
2018-03-12T17:43:53.427085+00:00 heroku[web.1]: State changed from starting to up
2018-03-12T17:43:54.945724+00:00 app[web.1]: GET / 304 55.364 ms - -
2018-03-12T17:43:54.940445+00:00 heroku[router]: at=info method=GET path="/" host=*****.herokuapp.com request_id=30a1bc23-4836-487d-812b-3d886f756e2d fwd="27.118.**.**" dyno=web.1 connect=1ms service=75ms status=304 bytes=357 protocol=https
2018-03-12T17:43:55.228387+00:00 heroku[router]: at=info method=GET path="/getauthcode" host=*****.herokuapp.com request_id=53dfb6b6-7263-47d6-abbc-8cb4e148e729 fwd="27.118.**.**" dyno=web.1 connect=7ms service=16ms status=304 bytes=150 protocol=https
2018-03-12T17:43:55.233081+00:00 heroku[router]: at=info method=GET path="/src/my-app.html" host=*****.herokuapp.com request_id=7598852f-5b55-4e14-a531-652357132771 fwd="27.118.**.**" dyno=web.1 connect=11ms service=13ms status=304 bytes=238 protocol=https
2018-03-12T17:43:55.230755+00:00 app[web.1]: GET /getauthcode 304 5.979 ms - -
2018-03-12T17:43:55.518546+00:00 app[web.1]: GET /login?client_id=ZxjqWpsYj3&redirect_uri=/frontend&state=cool_jazz 304 3.197 ms - -
2018-03-12T17:43:55.518596+00:00 heroku[router]: at=info method=GET path="/login?client_id=ZxjqWpsYj3&redirect_uri=/frontend&state=cool_jazz" host=*****.herokuapp.com request_id=3b37ed7a-6132-4c20-bab3-81411734318d fwd="27.118.**.**" dyno=web.1 connect=1ms service=7ms status=304 bytes=238 protocol=https
2018-03-12T17:43:55.768753+00:00 heroku[router]: at=info method=GET path="/bower_components/polymer/polymer.html" host=*****.herokuapp.com request_id=2f0fcd8b-a50a-4bdb-8fe5-36e3cea50f5c fwd="27.118.**.**" dyno=web.1 connect=1ms service=6ms status=404 bytes=420 protocol=https
2018-03-12T17:43:55.771344+00:00 heroku[router]: at=info method=GET path="/bower_components/app-layout/app-header/app-header.html" host=*****.herokuapp.com request_id=4cc19f6c-940f-4cf7-bdf4-8139f2976d51 fwd="27.118.**.**" dyno=web.1 connect=1ms service=6ms status=404 bytes=437 protocol=https
2018-03-12T17:43:55.772484+00:00 heroku[router]: at=info method=GET path="/bower_components/app-layout/app-toolbar/app-toolbar.html" host=*****.herokuapp.com request_id=4bb1d7ba-129e-4e88-8e2c-dc686a4fbc5e fwd="27.118.**.**" dyno=web.1 connect=0ms service=6ms status=404 bytes=439 protocol=https
2018-03-12T17:43:55.772997+00:00 app[web.1]: GET /bower_components/app-layout/app-toolbar/app-toolbar.html 404 1.834 ms - 195
2018-03-12T17:43:55.777958+00:00 heroku[router]: at=info method=GET path="/bower_components/iron-icon/iron-icon.html" host=*****.herokuapp.com request_id=08f7387b-619f-4c76-bbbf-f83a32352641 fwd="27.118.**.**" dyno=web.1 connect=1ms service=5ms status=404 bytes=424 protocol=https
2018-03-12T17:43:55.778855+00:00 heroku[router]: at=info method=GET path="/bower_components/app-layout/app-scroll-effects/app-scroll-effects.html" host=*****.herokuapp.com request_id=f0c7db3e-c2fb-40e2-8620-80439123315b fwd="27.118.**.**" dyno=web.1 connect=0ms service=7ms status=404 bytes=453 protocol=https
2018-03-12T17:43:55.992372+00:00 heroku[router]: at=info method=GET path="/bower_components/iron-icons/communication-icons.html" host=*****.herokuapp.com request_id=1d17f76c-8825-4ead-b28c-c60497dc0695 fwd="27.118.**.**" dyno=web.1 connect=2ms service=2ms status=404 bytes=435 protocol=https
2018-03-12T17:43:55.993917+00:00 heroku[router]: at=info method=GET path="/bower_components/iron-icons/social-icons.html" host=*****.herokuapp.com request_id=34d1ed8b-ebb6-42e6-b3cd-51bec675ee6e fwd="27.118.**.**" dyno=web.1 connect=1ms service=2ms status=404 bytes=428 protocol=https
2018-03-12T17:43:56.013960+00:00 heroku[router]: at=info method=GET path="/bower_components/paper-input/paper-input.html" host=*****.herokuapp.com request_id=744db894-6b7d-4cd3-8da9-d7c2e721348f fwd="27.118.**.**" dyno=web.1 connect=2ms service=2ms status=404 bytes=428 protocol=https
2018-03-12T17:43:56.012290+00:00 heroku[router]: at=info method=GET path="/bower_components/iron-list/iron-list.html" host=*****.herokuapp.com request_id=0b19ba9d-855c-4ef9-af14-279a970f6cd8 fwd="27.118.**.**" dyno=web.1 connect=0ms service=3ms status=404 bytes=424 protocol=https
2018-03-12T17:43:56.234535+00:00 heroku[router]: at=info method=GET path="/bower_components/paper-toast/paper-toast.html" host=*****.herokuapp.com request_id=1a5b7eb7-dace-4369-9918-b4b127cc69c5 fwd="27.118.**.**" dyno=web.1 connect=8ms service=11ms status=404 bytes=428 protocol=https
2018-03-12T17:43:56.233275+00:00 app[web.1]: GET /bower_components/paper-icon-button/paper-icon-button.html 404 1.107 ms - 196
2018-03-12T17:43:56.233868+00:00 heroku[router]: at=info method=GET path="/bower_components/paper-icon-button/paper-icon-button.html" host=*****.herokuapp.com request_id=1404c12f-16cd-4f98-bdd3-d5867dd7e7fd fwd="27.118.**.**" dyno=web.1 connect=8ms service=11ms status=404 bytes=440 protocol=https
2018-03-12T17:43:56.243881+00:00 heroku[router]: at=info method=GET path="/images/assistant-small.png" host=*****.herokuapp.com request_id=743a3373-32fa-4dfd-925c-8d079ce009e9 fwd="27.118.**.**" dyno=web.1 connect=0ms service=3ms status=304 bytes=237 protocol=https
2018-03-12T17:43:57.487448+00:00 heroku[router]: at=info method=GET path="/service-worker.js" host=*****.herokuapp.com request_id=0ff20343-f953-4ed9-a213-5879a6971623 fwd="27.118.**.**" dyno=web.1 connect=1ms service=7ms status=200 bytes=964 protocol=https
2018-03-12T17:43:57.488511+00:00 app[web.1]: GET /service-worker.js 200 5.404 ms - 678
2018-03-12T17:43:56.015891+00:00 heroku[router]: at=info method=GET path="/bower_components/paper-dialog/paper-dialog.html" host=*****.herokuapp.com request_id=43a92199-c68f-48ac-88d6-7aa128d43d04 fwd="27.118.**.**" dyno=web.1 connect=2ms service=4ms status=404 bytes=430 protocol=https
2018-03-12T17:43:56.012496+00:00 heroku[router]: at=info method=GET path="/bower_components/paper-button/paper-button.html" host=*****.herokuapp.com request_id=20328ca9-a4fb-4c79-a706-27843d4a5758 fwd="27.118.**.**" dyno=web.1 connect=0ms service=2ms status=404 bytes=430 protocol=https
2018-03-12T17:43:55.778611+00:00 heroku[router]: at=info method=GET path="/bower_components/iron-icons/iron-icons.html" host=*****.herokuapp.com request_id=f5d743b8-0ef8-4172-80aa-386dd20fed1e fwd="27.118.**.**" dyno=web.1 connect=1ms service=5ms status=404 bytes=426 protocol=https

I don't see anything wrong with these logs, at least nothing to suggest an error in deployment.

I have tried other free Node.js hosting services like OpeNode, OpenShift, etc, but the results were always the same: that broken page. Probably because there was no way to run the following commands as stated in the page, because it is a restricted hosting environment.

npm install -g bower
bower install
cd ..

Probably there is a solution, but my knowledge on Node.js is too little. I will have to investigate more about bower and hosting,etc. I think this thread may be marked as closed.

I finally got it working on OpenShift. I had to go to Applications -> Pods -> Terminal, and cd to the frontend directory, and run bower install.

If you're using a hosting service based on git, you may need to include that in the build script or allow bower_components to be served on git (removing that from the .gitignore.

authors: Fleker HubKing

repo: actions-on-google/smart-home-nodejs


text:
Release based on PR

Hello, is there any functionality based on, for example, PR label so I can release with major/minor/patch update to release's tag?
I need it to automate release deploying with version changes (https://github.com/tenhobi/bachelors-thesis/issues/8)
e.g. :

release v0.1.1
then PR w/ label "minor"
release v0.2.0
then PR w/ label "major"
release v1.0.0

Shameless plug here: the behavior you're describing is implemented by this action → https://github.com/K-Phoen/semver-release-action

authors: K-Phoen tenhobi

repo: actions/create-release


text:
Update mingw in windows-2019 image

Description
Updates to a mingw build with a much more up-to-date runtime, but still with gcc 8.
From gcc 8.1.0 to 8.5.0, and mingw runtime 6 to 10.
Related issue:
Closes #10352
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

Updated branch to resolve conflict.

repo: actions/runner-images


text:
[ubuntu] Fix Ubuntu-20.04 image generation failure

Description
Ubuntu-20.04 image generation is failing due to the swift failure. This PR fixes the issue by updating the swift version signature for the latest version.
Image failure pipeline : https://dev.azure.com/mseng/AzDevNext.Deploy/_build/results?buildId=29077054&view=results
Related issue:
Check list

[ ] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

+1


text:
python 3.7 environment using setup-python broken in 20200705.1

Describe the bug
Builds using the setup-python Github Action end up with "inconsistent" python environment, only for runners with virtual environment version 20200705.1 (20200625.0 was/is working fine).
Area for Triage:

Question, Bug, or Feature?:
Bug
Virtual environments affected

[ ] macOS 10.15
[ ] Ubuntu 16.04 LTS
[x] Ubuntu 18.04 LTS
[ ] Ubuntu 20.04 LTS
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

(only Ubuntu 18.04 tested)
Expected behavior
Uninstalling pyyaml package should work without errors.
Actual behavior
Uninstalling the pyyaml package results in
FileNotFoundError: [Errno 2] No such file or directory: '/opt/hostedtoolcache/Python/3.7.8/x64/lib/python3.7/site-packages/PyYAML-5.3.1-py3.7-linux-x86_64.egg'

Note: This has been observed only when requesting a python environment (3.7) that was not yet installed on the runner.
When requesting python 3.8 using setup-python, this issue does not occur (in this case, pip considers pyyaml not to be installed).
Failing run with 20200705.1 : https://github.com/aiidateam/aiida-core/pull/4208/checks?check_run_id=850446697#step:5:495
Successful run with 20200625.0: https://github.com/sphuber/aiida_core/runs/850405963#step:5:452
Successful run with 20200705.1 (after switching from python3.7 to python3.8 env): https://github.com/aiidateam/aiida-core/pull/4229/checks?check_run_id=850252814#step:5:452
P.S. I'm aware that I'm not providing a "minimum working example" here - I'm currently pressed for time.
I hope this can still help pinpoint the issue in case others experience the same (and I can add more information later if needed).

@ltalirz , looks like between these image versions, Python was updated from 3.7.7 to 3.7.8. Probably, it could be the reason for errors.
Could you please try to specify exact version in your yaml to check if rollback to 3.7.7 works for you?
    - name: Set up Python 3.7
      uses: actions/setup-python@v1
      with:
        python-version: 3.7.7

Thanks, I've just tried this but I'm afraid this is not supported:
##[error]Version 3.7.7 with arch x64 not found
Available versions:

2.7.18 (x64)
3.5.9 (x64)
3.6.11 (x64)
3.7.8 (x64)
3.8.3 (x64)

https://github.com/ltalirz/aiida-core/runs/850587893

Oh, sorry, it is my mistake, you should specify version v2 to install versions on-flight.
  - name: Set up Python 3.7
      uses: actions/setup-python@v2
      with:
        python-version: 3.7.7

No problem - I confirm that rolling back to python 3.7.7 resolves the issue
https://github.com/ltalirz/aiida-core/runs/850614175?check_suite_focus=true#step:5:123
So perhaps the reason I am the only one noticing this is that we were using an outdated version of the setup-python github action?
If I go back to installing version 3.7 (meaning 3.7.8) with v2 of the action, should the problem disappear?

No, it won't resolve issue. The main feature of V2 is that it can install previous versions on-flight.
Looks like your code works correctly with Python 3.7.7 but fails with Python 3.7.8.
Could it be related to some updates / breaking changes / updated dependencies on Python side?

If my suspicion is correct, then simply calling "pip uninstall pyyaml" should fail.
This is what I get when I just do this:
https://github.com/ltalirz/aiida-core/runs/850664377?check_suite_focus=true#step:5:68

Ok - I was wrong. Uninstalling pyyaml works just fine: https://github.com/ltalirz/aiida-core/runs/850675461?check_suite_focus=true#step:5:52
In this case, I suspect the issue must somehow be related to our dependencies. Thanks for your help!

Just in case others run into this: The issue is with the installation of the specific pyyaml version we're using (5.1.2):
https://github.com/ltalirz/aiida-core/runs/850699055?check_suite_focus=true#step:5:97

Just mentioning that the issue with installing pyyaml 5.1.2 over an existing installation of pyyaml 5.3.1 does not seem to occur on the official python 3.7.8 docker containers.
I.e. the following runs fine:
docker pull python:3.7.8
docker run python:3.7.8 /bin/bash -c "python --version && pip install pyyaml==5.3.1 && pip install pyyaml==5.1.2"

Which may indicate that this is a specific issue of the virtual environment 20200705.1 ?

Hi @ltalirz , looks like pyyaml 5.3.1 is installed during aws-sam-cli installation and it not working properly, we are investigate how to resolve the issue.

The same also here - https://github.com/PyTorchLightning/pytorch-lightning/runs/889998403
for all OS (ubuntu-18.04, windows-2019, macOS-10.15) and python 3.6, 3.7 and 3.8

@Borda , Only "pytest (ubuntu-18.04, 3.7, minimal)" job fails with the same issue in your build. All other jobs failed differently.

Is there any workaround for this? I have PyYAML==5.1.2 in my requirements.txt file and I run into this issue, too. What's even more annoying is that other jobs testing my project on other python versions got cancelled because this one fails.

Okay, in my case the error line read:
File "/opt/hostedtoolcache/Python/3.7.8/x64/lib/python3.7/site-packages/pip/_vendor/pkg_resources/__init__.py", line 1731, in zipinfo
    return self._zip_manifests.load(self.loader.archive)
  File "/opt/hostedtoolcache/Python/3.7.8/x64/lib/python3.7/site-packages/pip/_vendor/pkg_resources/__init__.py", line 1688, in load
    mtime = os.stat(path).st_mtime
FileNotFoundError: [Errno 2] No such file or directory: '/opt/hostedtoolcache/Python/3.7.8/x64/lib/python3.7/site-packages/PyYAML-5.3.1-py3.7-linux-x86_64.egg'
##[error]Process completed with exit code 1.

I had this in requirements.txt:
PyYAML==5.1.2
Changing it to:
PyYAML==5.3.1

Solved my problem.
Seems that one of the installed packages required PyYAML==5.3.1, but for some reason my requirements file had older version (actually it was generated by pip freeze, so I have no idea how it happened).

Well, is it general pip issue or just this CI, if so we do not force users to install a newer version just because if CI tests, right?

@Borda @DataGreed we fixed the issue with python 3.7 a few days ago and started image deployment today. It usually takes 3-4 days to propagate to all the environments. Thank you for your patience.

@miketimofeev большое спасибо :)

Is this new normal?
ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.
Successfully installed Babel-2.8.0 Bootstrap-Flask-1.4 Faker-4.1.1 Flask-1.1.2 Flask-Babel-1.0.0 Flask-Login-0.5.0 Flask-WTF-0.14.3 Jinja2-2.11.2 MarkupSafe-1.1.1 PeeWee-3.13.3 SecretStorage-3.1.2 WTForms-2.3.1 argon2-cffi-20.1.0 blinker-1.4 cffi-1.14.1 coverage-5.2.1 cryptography-3.0 decorator-4.4.2 factory-boy-2.12.0 inflection-0.5.0 iniconfig-1.0.0 itsdangerous-1.1.0 jeepney-0.4.3 keyring-21.2.1 keyrings.cryptfile-1.3.4 markdown-3.2.2 more-itertools-8.4.0 packaging-20.4 pluggy-0.13.1 py-1.9.0 pycparser-2.20 pycryptodome-3.9.8 pyparsing-2.4.7 pytest-6.0.0 pytest-cov-2.10.0 pytest-factoryboy-2.0.3 pytest-flask-1.0.0 pytest-mock-3.2.0 python-dateutil-2.8.1 python-dotenv-0.14.0 python-magic-0.4.18 sentry-sdk-0.16.2 text-unidecode-1.3 texttable-1.6.2 toml-0.10.1 validators-0.16.0

We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.

aws-sam-cli 1.0.0 requires Flask~=1.0.2, but you'll have flask 1.1.2 which is incompatible.
aws-sam-cli 1.0.0 requires python-dateutil<2.8.1,~=2.6, but you'll have python-dateutil 2.8.1 which is incompatible.

@zgoda could you please provide the command, which produced such output?

It's a log from one of my workflows running on Python 3.7 runtime, can't recall exactly which one but https://github.com/zgoda/bip/runs/929067312 has the same output.
Basically Python 3.7 runtime has a lot of either outdated or pre-release packages installed, like:
2020-07-30T18:56:03.2115932Z   Attempting uninstall: itsdangerous
2020-07-30T18:56:03.2171330Z     Found existing installation: itsdangerous 2.0.0a1
2020-07-30T18:56:03.2177836Z     Uninstalling itsdangerous-2.0.0a1:
2020-07-30T18:56:03.2617111Z       Successfully uninstalled itsdangerous-2.0.0a1
2020-07-30T18:56:03.2780445Z   Attempting uninstall: MarkupSafe
2020-07-30T18:56:03.2846347Z     Found existing installation: MarkupSafe 2.0.0a1
2020-07-30T18:56:03.2854577Z     Uninstalling MarkupSafe-2.0.0a1:
2020-07-30T18:56:03.3272337Z       Successfully uninstalled MarkupSafe-2.0.0a1
2020-07-30T18:56:03.3367490Z   Attempting uninstall: Jinja2
2020-07-30T18:56:03.3425437Z     Found existing installation: Jinja2 3.0.0a1
2020-07-30T18:56:03.3436269Z     Uninstalling Jinja2-3.0.0a1:
2020-07-30T18:56:03.3853792Z       Successfully uninstalled Jinja2-3.0.0a1

Flask 1.0.4 and python-dateutil 2.8.0 are installed with aws-sam-cli but anyway they should not be in a runtime used to run tests.

@zgoda yeah, this is the same issue with aws-sam packages. It will be fixed on the next week's deployment.

@ltalirz we've completed image deployment. Could you check everything is fine now, please?

Thanks @miketimofeev - looks to me like the issue is resolved!

authors: Borda DataGreed ltalirz maxim-lobanov miketimofeev vsafonkin zgoda

repo: actions/virtual-environments


text:
Can't use nuke.build to build .net core app. Nuke is missing

Tool information

Tool name: Nuke
Add or update? Add
Desired version: 0.23.6
Approximate size:
If this is an add request:

Brief description of tool: A cross-platform build automation system with C# DSL.
URL for tool's homepage: http://www.nuke.build/

Area for Triage: .NET Core, .NET Framework
Question, Bug, or Feature?: Feature
Virtual environments affected

[ ] macOS 10.15
[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Can this tool be installed during the build?
No
Are you willing to submit a PR?
No

@miketimofeev hi any idea when this will be implemented?

@jubayerarefin sorry, it's still untriaged at the moment.
@alepauly can we add it?

@jubayerarefin by the way, could you try to install it during the run, looks like it's quite fast

I'll give it a try
With Kind Regards,
Jubayer Arefin

From: Mikhail Timofeev notifications@github.com
Sent: Tuesday, March 3, 2020 9:34:10 PM
To: actions/virtual-environments virtual-environments@noreply.github.com
Cc: Jubayer Arefin jubayer@dipu.com; Mention mention@noreply.github.com
Subject: Re: [actions/virtual-environments] Can't use nuke.build to build .net core app. Nuke is missing (#305)
@jubayerarefinhttps://github.com/jubayerarefin by the way, could you try to install it during the run, looks like it's quite fast
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/actions/virtual-environments/issues/305?email_source=notifications&email_token=AEKMHXCNM3NPIUSYOYTEEQ3RFUPPFA5CNFSM4KKDMKH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENT6RVA#issuecomment-594012372, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEKMHXBMIODSJO7O5KK5M23RFUPPFANCNFSM4KKDMKHQ.

@miketimofeev it can be installed during the run :)

Hello, @jubayerarefin
Feel free to open thread if you have any questions.

authors: al-cheb jubayerarefin miketimofeev


text:
Cannot build Python C extensions on Windows

Describe the bug
The following standard build command for C extensions in Python fails for all Windows environments for all supported Python versions:
python setup.py build_ext --inplace

It appears that the appropriate versions of Microsoft Visual C++ are not installed/configured.
Please note that the correct MSVC++ version varies across Python versions; see here for specifics.
Virtual environments affected

[ ] macOS 10.14
[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[x] Windows Server 2016 R2
[x] Windows Server 2019

Expected behavior
It should be possible to build Python C extensions in Windows virtual environments. For a Python build/test pipeline, this means selecting the correct version to use for a given Python version.
Actual behavior
This should be reproducible for any Python library with any C (or Cython) components on Windows. I encountered the issue while attempting to configure Github Actions for such a library that I maintain. An example of a failed build log is https://github.com/pydata/bottleneck/runs/240915673

Use the workflow file found here: https://github.com/pydata/bottleneck/commit/630a39884f66a52a24c470ec83b986606aca844f#diff-fd3c00174dcaf7b8a36765f1a3de6791
Build will fail at C compilation step  as the appropriate version of MS Visual C++ is not installed.

When fixed, it should be possible to build Python C extensions on Windows.

This is specific for Python 3.5, since it lacks the code needed to find recent versions of VS properly.
https://bugs.python.org/issue30389.  I was able to make it work by monkey-patching distutils._msvccompiler with code from 3.7.

@elprans The example I gave has it failing on 2.7 as well

@qwhelan Yea, 2.7 is a different story. It requires a very specific version of the MSVC compiler.

Ho @qwhelan Is that bug still actual for you?

@miketimofeev I switched back to another provider for Windows-based testing due to this bug, so can't say. There doesn't seem to be anyone suggesting this is fixed.

@qwhelan Closing this for now in that case. Feel free to reopen if you have any concerns.
Thank you!

authors: elprans miketimofeev qwhelan


text:
Install full version of Boost on Windows

Tool information

Tool name: boost

Area for Triage:
Question, Bug, or Feature?: Feature
Virtual environments affected

[ ] macOS 10.15
[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[ ] Windows Server 2016 R2
[x] Windows Server 2019

Description
Currently, only some stub install of boost seems provided in BOOST_ROOT. Libraries are not available, so they must be compiled in each workflow execution.
Can this tool be installed during the build?
choco install -boost-msvc-14.1 should do it. It's a large install (2+GB), so preferable not to do it at each workflow execution.

Hi @pitrou ! Thanks for reporting the issue.
Could you please provide some additional information about the problem, maybe it is possible to share some steps to reproduce?
Also, please, take a look at this ticket https://github.com/actions/virtual-environments/issues/74, it could be the same issue you are experiencing now. If so, the fix will be delivered in a couple of days.

@AlenaSviridenko I'm not sure what you mean here. According to my investigations, the Boost binary libraries are not provided in the BOOST_ROOT directory tree. This means that to actually link software with Boost, the Boost libraries have to be built first during the workflow execution, which is wasteful.
This issue is not about Boost.Build, which we are not using.

By the way, here is how we worked around the issue:
https://github.com/apache/arrow/pull/6325/files#diff-f656dcc6ce6cd7f889b4a660d36866d4R185
This change replaced ~10 minutes of compiling with ~3 minutes of downloading and installing the Boost binaries. Still, that's probably 3 wasted minutes on every build :-)

Hi, @pitrou
Could you please provide quick steps to reproduce the issue?

Hi, I have the same issue, my build fails with Boost 1.72:
https://github.com/Morgan-Stanley/binlog/runs/439567374?check_suite_focus=true
It was previously working with 1.69:
https://github.com/Morgan-Stanley/binlog/runs/426277644?check_suite_focus=true
The headers are found, but the libraries to be linked appears to have been built for a different version of msvc.

@erenon Hello,
Please try to use at the top in CMAKEList.txt
SET(Boost_USE_STATIC_LIBS OFF)
IF( WIN32 )
    # The auto-linking feature has problems with USE_STATIC_LIBS off, so we use
    # BOOST_ALL_NO_LIB to turn it off.
    # Several boost libraries headers aren't configured correctly if
    # USE_STATIC_LIBS is off, so we explicitly say they are dynamic with the
    # remaining definitions.
    ADD_DEFINITIONS(-DBOOST_ALL_NO_LIB -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_THREAD_DYN_LINK)
ENDIF( )

CMAKELIST.txt - https://pastebin.com/raw/G87fCHxB
My example:
jobs:
  build:
    runs-on: [windows-latest]
    steps:
      - name: git clone
        run: |
          cd $env:UserProfile\Desktop
          git clone https://github.com/Morgan-Stanley/binlog.git
          cd  binlog
          Invoke-WebRequest https://pastebin.com/raw/G87fCHxB -OutFile CMakeLists.txt
          mkdir Release
          cd Release
          cmake -DBINLOG_FORCE_TESTS=ON ..
      - name: Build
        run: |
          cd $env:UserProfile\Desktop\binlog
          cmake --build Release --config Release -j2
      - name: Test
        run: |
          cd $env:UserProfile\Desktop\binlog
          $Env:path += ";${env:BOOST_ROOT}\lib"
          cd Release
          ctest -VV -C Release

@al-cheb : wow, this is a really nice repro and fix!
Unfortunately, I don't get it.
Setting only BOOST_ALL_NO_LIB and BOOST_ALL_DYN_LINK doesn't work.
SET(Boost_USE_STATIC_LIBS OFF) is also needed, despite that the documentation says the default is OFF.
At least the build is now green... Thanks!

I'm not sure is this correct issue or not, BTW, the problem somehow related.
Seems like the initial problem has been solved. Partially. But now it looks like that "static crt" versions of boost 1.72 libraries are actually linked with dynamic version of CRT:
https://github.com/jinja2cpp/Jinja2Cpp/runs/492758600?check_suite_focus=true#step:3:169
libboost_filesystem-vc142-mt-x64-1_72.lib(path_traits.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MT_StaticRelease' in basic_tests.obj [D:\a\Jinja2Cpp\Jinja2Cpp\.build\jinja2cpp_tests.vcxproj]
libboost_filesystem-vc142-mt-x64-1_72.lib(path.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MT_StaticRelease' in basic_tests.obj [D:\a\Jinja2Cpp\Jinja2Cpp\.build\jinja2cpp_tests.vcxproj]
libboost_filesystem-vc142-mt-x64-1_72.lib(operations.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MT_StaticRelease' in basic_tests.obj [D:\a\Jinja2Cpp\Jinja2Cpp\.build\jinja2cpp_tests.vcxproj]

I'm pretty sure the project itself is OK:

Linking with boost 1.69 works fine
I tested the same build configurations on the other CI farm and it worked well

Hello, @flexferrum
Try to add flag /MT in CMakeLists.txt:
set(CMAKE_CXX_FLAGS_RELEASE "${CMAKE_CXX_FLAGS_RELEASE} /MT")

Hello, @al-cheb
I know this trick, but in this case it's unrelated. The root probolem is in another place.
Windows-2019 build uses boost cmake finder (non-standard) which is different from windows-2016 version (from the CMake distro). And this finder:

Has separate find methods for some libraries from boost. With this finder you can write find(boost_filesystem) and it will work
This finder ignores standard hints (such as BOOST_ROOT). I was failed to specify 1.69 version of boost for my builds

I managed to solve problem with my build. But, I think, usage of custom Boost 1.72 CMake finders for Windows-2019 host should be mentoined in the docs.

@flexferrum
BOOST_ROOT will be deprecated in several week.

@al-cheb

The BOOST_ROOT env variable will be deprecated in several week.
And what will be new way to point boost installation? Are there any docs regarding to this?

https://github.com/actions/virtual-environments/blob/releases/win19/20200301/images/win/Windows2019-Readme.md: BOOST_ROOT_1_69_0 and BOOST_ROOT_1_72_0

https://github.com/actions/virtual-environments/blob/releases/win19/20200301/images/win/Windows2019-Readme.md: BOOST_ROOT_1_69_0 and BOOST_ROOT_1_72_0

I read this. BTW I found no way to point CMake to the 1.69 installation. Looks like path to boost 1.72 cmake helpers is hardcoded somehow  in CMAKE_MODULES_PATH. But I'm not completely sure.

@flexferrum
We don't have any hardcoded path for CMAKE. Only predefined BOOST_ROOT=C:\hostedtoolcache\windows\Boost\1.72.0

@flexferrum
We don't have any hardcoded path for CMAKE. Only predefined: BOOST_ROOT=C:\hostedtoolcache\windows\Boost\1.72.0

I'm pretty sure about this. But in the windows-2016 (with Boost 1.69) environment CMake uses the default finder:
-- [ C:/Program Files/CMake/share/cmake-3.16/Modules/FindBoost.cmake:1463 ]

https://github.com/jinja2cpp/Jinja2Cpp/runs/495118084?check_suite_focus=true#step:3:184
On the windows-2019 it uses finder shipped with Boost 1.72:
-- Found Boost 1.72.0 at C:/hostedtoolcache/windows/Boost/1.72.0/lib/cmake/Boost-1.72.0

https://github.com/jinja2cpp/Jinja2Cpp/runs/495118215?check_suite_focus=true#step:3:192
Somehow CMake able to find these modules.

@flexferrum
What happens if try to delete C:/hostedtoolcache/windows/Boost/1.72.0/lib/cmake folder before build?

@al-cheb
It uses the standard CMake finder:
-- [ C:/Program Files/CMake/share/cmake-3.16/Modules/FindBoost.cmake:1463 ]

https://github.com/jinja2cpp/Jinja2Cpp/runs/498202815?check_suite_focus=true

@flexferrum
https://cmake.org/cmake/help/latest/module/FindBoost.html
If Boost was built using the boost-cmake project or from Boost 1.70.0 on it provides a package configuration file for use with find_package’s config mode. This module looks for the package configuration file called BoostConfig.cmake or boost-config.cmake and stores the result in CACHE entry “Boost_DIR”. If found, the package configuration file is loaded and this module returns with no further action. See documentation of the Boost CMake package configuration for details on what it provides.
Set Boost_NO_BOOST_CMAKE to ON, to disable the search for boost-cmake.

@al-cheb , thanks, I'll try. I still think, it should be mentoined in the docs.

@flexferrum , Sure I will add this section to the Windows2019-Readme.md.

The docs were updated. Feel free to open the thread if you have any questions.

authors: AlenaSviridenko al-cheb erenon flexferrum pitrou


text:
[All OSs] Go versions less than 1.16 will be removed and the default will be set to 1.17 on April, 11

Breaking changes
All pre-cached Go versions less than 1.16 will be removed from all operating systems. Version 1.17 will be set as the new default version.
Target date
April 11, 2022.
The motivation for the changes
According to our Software and image guidelines
 we support [3 latest minor versions of Go],
(https://endoflife.date/go) which are 1.16, 1.17 & 1.18 at the moment.
Version 1.17 will be the new default as it is most popular according to telemetry data.
Possible impact
If your project depends on a pre-installed Go version 1.15 it can be broken.
Virtual environments affected

[X] Ubuntu 18.04
[X] Ubuntu 20.04
[X] macOS 10.15
[ ] macOS 11
[X] Windows Server 2016
[X] Windows Server 2019
[ ] Windows Server 2022

Mitigation ways
To install any versions in runtime use:

https://github.com/actions/setup-go action for GH actions
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/go-tool?view=azure-devops task for AzDO

جميل جد @ #

[ ]

authors: ddobranic nauil


text:
feat: Inject system reducer automatically

Features:

Inject system reducer automatically
Support passing reducer object or single reducer function

Fix in 9503fa4


text:
Sailing mode to prevent trickle charging

Battery does a great job of limiting charging or manually discharging to a set percentage but could a feature like Al Dente's sailing mode be added to prevent trickle charging when the laptop is plugged in and has reached the specified charging limit?
Instead of just setting a "battery maintain" level, a charge limit level and a charge restart level would be set so the battery could drain down to a set point before charging restarts.
e.g. limit of 80% and restart point of 70% so the laptop charges to 80% and then uses power from the adapter but the battery is not being charged until its level slowly and naturally drops to 70%, and then charging restarts.
As it is, the laptop charges to 80% and then uses power from the adapter but is fairly constantly topping up the battery to keep it at 80%.

As far as I understand you are looking for an adjustable hysteresis in percent. Currently it is coded at 1%.
I implemented it as second argument for voltages limits:
E.g.
battery maintain 11.4V 0.2V
This will stop charging at 11.6V and restart at 11.2V.
It could also be implemented for percentages like so:
battery maintain 75 5
Which would lead to your example of 70%-80%

Hi Rene, having looked up what adjustable hysteresis means, yes, that's what I'm talking about. It's good to know it's already there with a ±1% swing.
Are you saying v1.2.2 can already use the "battery maintain 11.4V 0.2V" instruction and that a future release could have the ability to use the "battery maintain 75 5" instruction?  If so, the percentage example seems less technical and more user-friendly than the voltage example. I think the percentage approach would be a valuable addition.

I implemented it as second argument for voltages limits

I miss displaying real voltage instead of percentages.

authors: djbob2000 jk-aus rguca

repo: actuallymentor/battery


text:
🛑 Processors is down

In 98bd443, Processors ($STATUS_URL) was down:

HTTP code: 200
Response time: 121 ms

Resolved: Processors is back up in 9beda4f.

Resolved: Processors is back up in 9beda4f.

repo: acumenlabs/status-page


text:
⚠ Fetchers has degraded performance

In 06ca94d, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 301 ms

Resolved: Fetchers performance has improved in 25ebb53.


text:
🛑 Telemetry API is down

In d89c149, Telemetry API ($SECRET_SITE_4) was down:

HTTP code: 502
Response time: 9145 ms

Resolved: Telemetry API is back up in b4abc3f.

repo: adadaptedinc/upptime


text:
OSError 0 with MagTag

I was running code to fetch bitcoin and came across this mysterious error.
Traceback (most recent call last):
  File "code.py", line 82, in <module>
  File "code.py", line 74, in <module>
  File "/lib/adafruit_requests.py", line 585, in get
  File "/lib/adafruit_requests.py", line 563, in request
  File "/lib/adafruit_requests.py", line 423, in _get_socket
OSError: 0

Moving this to CircuitPython. For any issues on an S2 please file them there first.

authors: makermelissa tannewt


text:
Need connectivity support for AuraDB in Neo4jConfig

Currently the present config:Neo4jConfig for connecting to "nest-neo4j" to the db, doesn't support for AuraDB url's , as it is supporting the selfhosted connections only.

You should be able to use neo4j+s as the scheme and the aura connection uri, let me double-check.  The driver needs updating to the latest version anyway.

Thanks, Yes it' s started working after changing to neo4j+s, but it would be nice to just only pass the connection uri directly in to the config object.

Yeah, this is a bit of a hangover from pre-aura days when it made sense to define the scheme specifically.  The fromEnv() method should also be capable of reading the credentials.env file that is downloaded from the Aura console.  One day, maybe!

Ohh that would be nice, I will try to add that utility in my free time!


text:
Remove resend messages and only resend on reconnection

From spec: When a Client reconnects with Clean Start set to 0 and a session is present, both the Client and Server MUST resend any unacknowledged PUBLISH packets (where QoS > 0) and PUBREL packets using their original Packet Identifiers. This is the only circumstance where a Client or Server is REQUIRED to resend messages. Clients and Servers MUST NOT resend messages at any other time

#57

repo: adam-fowler/mqtt-nio


text:
Is there any way change the tpl language？

how can i change this with my language? is there any way?
我的英语不太好，请见谅。

You can use this method which accepts a custom template.
The default template is here. You can modify it to be in your language.

repo: adamabdelhamed/PowerArgs


text:
Marking middleware as unused when not in DEBUG

Description
Hi,
I read in Django documentation that there's a way to mark a middleware as unused at startup. And it is completelly skipped by Django. I'm refering to [https://docs.djangoproject.com/en/4.0/topics/http/middleware/#marking-middleware-as-unused](this entry in the doc).
Maybe this would be useful here when DEBUG=False ?
Thanks for this project.

It could maybe help but it would only save one if statement per request, which is a tiny overhead.

I understand. I was browsing the doc, I read this, and I thought it would be "useful" here ("useful" or at least logical). But I don't want to bother you with this. Thank you for quick answer.

You can always achieve the same effect using something like this:
if DEBUG:
    MIDDLEWARE = [
        "debug_toolbar.middleware.DebugToolbarMiddleware",
        "django_browser_reload.middleware.BrowserReloadMiddleware",
    ] + MIDDLEWARE

authors: adamchainz cpaquot julianwachholz

repo: adamchainz/django-browser-reload


text:
Video is not playing in Android

Hi ,
I am trying to play video from azure url but it's working fine in iOS not in Android .
please check this issue.

Same issue for me

I know these issues aren't being monitored but I'm getting a similar issue with amazon s3 links.  The links are public, the content type is video/mp4.  The links also work perfectly in chrome on android and UWP (haven't gotten a chance to test iOS)
For a bit more detail, when I press play, nothing happens.  However if I continue to press play/pause back and forth, the video will eventually play.  Once it finishes, I have to go through the same thing again to get it to play once more.

OK, I can confirm exo player (https://github.com/martijn00/ExoPlayerXamarin) works with my s3 urls.  Now I just need to figure out how to implement that into this codebase.  Is it possible for me to override the renderer in my codebase without me having to fork the code?


text:
MacOS Monterey and PHP

Document possible solutions for people who don't have the PHP available in the Bash CLI, as Monterey (macOS 12+) removed the builtin PHP.

I just upgraded to Monterey... bummed it stopped working. ☹

I don't have access to Monterey computer, but it should be "fairly simple" to provide a working guide - you only need to have PHP accessible to CLI. Homebrew version, MAMP, etc. It's just not been priority so far

I have php installed via Homebrew. Running which php in the terminal tells me the path is /usr/local/bin/php which matches an option in Alfred 4...

No luck though.

Ok, changing the script to be /usr/local/bin/php index.php "{query}" fixes the issue for me with Homebrew.

Odd that the dropdown option with /usr/local/bin/php doesn't work. 🤷♂

It is odd. It is also odd that your Homebrew installed PHP doesn't work as PHP. Do you not have your /usr/local/bin in the $PATH? I thought it was - so that you don't have to link every Homebrew application?

After some testing, I figured out it actually didn't use the Homebrew PHP on my machine either 😓 After figuring out what to do, I actually ended up exporting to $PATH, the same way @foxacid did it in #10. I should probably document this in readme :D

authors: HYR adamkiss

repo: adamkiss/alfred-kirby-search


text:
Stop using/installing curl in Windows images

Subj. I don't know any reason why we can't just use PowerShell to download files.
The only thing that might become a show-stopper is git-credential-helper.bat. I dunno whether PowerShell has that functionality.

BTW, Windows has curl preinstalled. And if I'm not mistaken, that covers all our supported versions (2019 LTSC is the oldest).

If the built-in curl in Windows works, then great. I recall it wasn't present on LTSC 2016, and I have had experience that some things are not available without a newer build of curl; but I doubt they affect us.

authors: TBBle slonopotamus


text:
🛑 relay.fedi.agency is down

In f226c1e, relay.fedi.agency (https://relay.fedi.agency/actor) was down:

HTTP code: 502
Response time: 360 ms

Resolved: relay.fedi.agency is back up in 9f634b8.


text:
🛑 relay.fedi.agency is down

In a6fe3c3, relay.fedi.agency (https://relay.fedi.agency/actor) was down:

HTTP code: 502
Response time: 565 ms

Resolved: relay.fedi.agency is back up in 6ad69d9.


text:
🛑 mastodon-relay.moew.science is down

In 412ef82, mastodon-relay.moew.science (https://mastodon-relay.moew.science/actor) was down:

HTTP code: 502
Response time: 594 ms

Resolved: mastodon-relay.moew.science is back up in 3f65f72.


text:
🛑 relay.froth.zone is down

In 9218fd1, relay.froth.zone (https://relay.froth.zone/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.froth.zone is back up in 62eb72b.


text:
🛑 relay.national-defence.network is down

In de209f1, relay.national-defence.network (https://relay.national-defence.network/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.national-defence.network is back up in 01e3434 after 274 days, 18 hours, 59 minutes.


text:
🛑 relay.intahnet.co.uk is down

In 02ff0f8, relay.intahnet.co.uk (https://relay.intahnet.co.uk/actor) was down:

HTTP code: 502
Response time: 15664 ms

Resolved: relay.intahnet.co.uk is back up in 624faf6 after 46 minutes.


text:
Pandas compatibility

I m trying to use pandas with 3.9 or 3.11 on usb stick and E:\python3.11

import pandas
Traceback (most recent call last):
File "", line 1, in
File "E:\python3.11\pandas_init_.py", line 16, in
raise ImportError(
ImportError: Unable to import required dependencies:
numpy:

IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
Importing the numpy C-extensions failed. This error can happen for
many reasons, often due to issues with your setup or how NumPy was
installed.
We have compiled some common reasons and troubleshooting tips at:
https://numpy.org/devdocs/user/troubleshooting-importerror.html

Please note and check the following:

The Python version is: Python3.11 from "E:\python3.11\python.exe"
The NumPy version is: "1.21.6"

and make sure that they are the versions you expect.
Please carefully study the documentation linked above for further help.
Original error was: No module named 'numpy.core._multiarray_umath'

I think this is due to an incompatibility between numpy, a dependency of pandas, and Windows 7 rather than a problem with Python. But I need some more information to determine whether this is the case.
I noticed that numpy 1.21.6 does not provide binary distributions for Python 3.11 at https://pypi.org/project/numpy/1.21.6/#files, so I'm not sure how you installed it. Did you do anything special to install numpy? And how did you install pandas? What version of pandas?

Thank you for reply,
had also test with our 3.9 version and have the same issue.
Best Regards
Bernard
----- Mail d'origine -----
De: adang1345 @.>
À: adang1345/PythonWin7 @.>
Cc: Bernard13090 @.>, Author @.>
Envoyé: Thu, 08 Dec 2022 14:55:58 +0100 (CET)
Objet: Re: [adang1345/PythonWin7] Pandas compatibility (Issue #6)
I think this is due to an incompatibility between numpy, a dependency of pandas, and Windows 7 rather than a problem with Python. But I need some more information to determine whether this is the case.I noticed that numpy 1.21.6 does not provide binary distributions for Python 3.11 at https://pypi.org/project/numpy/1.21.6/#files, so I'm not sure how you installed it. Did you do anything special to install numpy? And how did you install pandas? What version of pandas?—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Hi,
Thank you for advice.
I solved my problem with pandas.
E:\python3.11\Scripts
λ E:\python3.11\scripts\pip install --target E:\python3.11  pandas==1.5.2
Now had issue with tkinter.
Is there a way to install it.
λ E:\python3.11\scripts\pip install --target E:\python3.11  tkinter
ERROR: Could not find a version that satisfies the requirement tkinter (from versions: none)
ERROR: No matching distribution found for tkinter
----- Mail d'origine -----
De: adang1345 @.>
À: adang1345/PythonWin7 @.>
Cc: Bernard13090 @.>, Author @.>
Envoyé: Thu, 08 Dec 2022 16:34:53 +0100 (CET)
Objet: Re: [adang1345/PythonWin7] Pandas compatibility (Issue #6)
Closed #6 as completed.—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

tkinter is part of a Python installation and cannot be installed afterward with pip. It must be installed when you run the Python installer.

is tkinter include in python-3.11.1-embed-amd64.zip
----- Mail d'origine -----
De: adang1345 @.>
À: adang1345/PythonWin7 @.>
Cc: Bernard13090 @.>, Author @.>
Envoyé: Thu, 08 Dec 2022 19:22:41 +0100 (CET)
Objet: Re: [adang1345/PythonWin7] Pandas compatibility (Issue #6)
tkinter is part of a Python installation and cannot be installed afterward with pip. It must be installed when you run the Python installer.—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

No, the embeddable distribution of Python does not include tkinter. That is the case with official Python distributions as well.

Ok,
i had install Python on USB stick
copy directory missing from working python on c:
had try:
in cmd
PATH = %PATH%;E:\pythontest\DLLs
in python embeded
λ python
Python 3.9.9 (main, Sep 16 2022, 15:41:44) [MSC v.1929 64 bit (AMD64)] on win32

import sys
from pathlib import Path
pytohn_path=Path(sys.exec_prefix)
dlls_path=Path(pytohn_path,"DLLs")
tcl_path=Path(pytohn_path,"tcl")
sys.path.insert(0,str(dlls_path))
sys.path.insert(0,str(tcl_path))
import tkinter
Traceback (most recent call last):
File "", line 1, in
File "E:\pythontest\Lib\tkinter_init_.py", line 36, in
import _tkinter # If this fails your Python may not be configured for Tk
ImportError: DLL load failed while importing _tkinter: Le module spécifié est introuvable.

Have you an issue to import tkinter.
Best regards
Bernard
----- Mail d'origine -----
De: adang1345 @.>
À: adang1345/PythonWin7 @.>
Cc: Bernard13090 @.>, Author @.>
Envoyé: Thu, 08 Dec 2022 19:36:12 +0100 (CET)
Objet: Re: [adang1345/PythonWin7] Pandas compatibility (Issue #6)
No, the embeddable distribution of Python does not include tkinter. That is the case with official Python distributions as well.—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Hi, I'd like to keep this issue tracker focused on issues related to supporting newer Python versions on Windows 7, and not general issues with setting up Python. If you have an issue that occurs with the Python releases in this repository which does not occur with official Python releases, then the issue belongs in this tracker. Otherwise, it is an issue with setting up or using Python in general and should be asked elsewhere such as Stack Overflow or the Python Discourse.

Hi,
Thank you for this very constructive suggestion.
I have no problem with the official version precisely. That's why I thought you would have tested this possibility at home.
But if not, I will indeed look for an answer elsewhere.
The question has already been asked on stackowerflow without a conclusive answer.
Maybe you have a solution.
This takes nothing away from the fabulous work done for the adaptation to WIN7.
Best regards
Bernard
----- Mail d'origine -----
De: adang1345 @.>
À: adang1345/PythonWin7 @.>
Cc: Bernard13090 @.>, Author @.>
Envoyé: Sat, 17 Dec 2022 21:17:11 +0100 (CET)
Objet: Re: [adang1345/PythonWin7] Pandas compatibility (Issue #6)
Hi, I'd like to keep this issue tracker focused on issues related to supporting newer Python versions on Windows 7, and not general issues with setting up Python. If you have an issue that occurs with the Python releases in this repository which does not occur with official Python releases, then the issue belongs in this tracker. Otherwise, it is an issue with setting up or using Python in general and should be asked elsewhere such as Stack Overflow or the Python Discourse.—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


text:
Update percona toolkit to 3.2.0

remove old tests with 3.0.13
add test for 3.2.0
keep test for latest

Fixed by a48bc0aa89126419d5770bdf33b8c112946f5150

repo: adangel/liquibase-percona


text:
Error in stager/launcher

EmPyre Version
=================================================================
EmPyre: Python post-exploitation agent | [Version]: 1.2
OS Information (Linux flavor, Python version)
Server:
Debian 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux
Python 2.7.9
Victim:
OSX 10.11.6
Python 2.7.10 (default, Oct 23 2015, 19:19:21)
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
I am pasting the base64 encoded launcher oneliner into the terminal on the OSX victim. It makes the connectback, but I am not getting any info or "[+] Initial agent...".
The host I am using is http://:8080.
Screenshot of error, embedded text output, or Pastebin link to the error
On the client I am seeing the following errors:
File "", line 1, in
File "", line 12, in
File "", line 448, in
File "", line 411, in get_sysinfo
socket.gaierror: [Errno 8] nodename nor servname provided, or not known
Any additional information

@hland thanks for posting this issue. We think it may be an issue with the hostname query failing on the target side. I just pushed a fix for this, if you could re-test this it would be great! https://github.com/adaptivethreat/EmPyre/tree/dev-sysinfo

This works. Thanks for getting back to me so fast 👍 Should I close the issue or will you merge into master first?

Going to push to master due to the issue @hland. No problem this one could be a show stoper on a OP.

authors: hland killswitch-GUI

repo: adaptivethreat/EmPyre


text:
Smallest fixes from static source analyzer

Smallest fixes from static source analyzer (some security and speed optimization's)

Great, thank you. I'll merge this.
Which code analysis tool did you use?

PHPStorm with PHPInspections (EA)

authors: ademarre rusxakep

repo: ademarre/binary-to-text-php


text:
Prompt limit of 125

I have tested this in several ways.
It seems the current prompt limit when using wildcards is 125 (the value listed on the UI, next to the "Generate" button); after this value, the wildcards stop working.
Or at least, this is happening on my end.

Could you provide a concrete example? I tried this prompt which worked:
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
{red|blue}

Weirdly, it's working fine today.
Yesterday it failed all the time when I used any prompt (with Wildcards) above 125 (it would generate an img, but the wildcards were all ignored), and it started working again when the prompt was under 125.
Tested it several times yesterday, even after restarting the webui.
For some reason, it is working fine today, so I'll close this
This is a great script. Thanks!

authors: StewieGriffin adieyal

repo: adieyal/sd-dynamic-prompts


text:
The ordinal 315 could not be located in the dynamic link library

Seeing this on opening zcash-qt-wallet.exe on Windows 10 Home.

Tested on v0.1.9

OK, this has me baffled :(
While I figure out why this is happening, I've switched the Windows release to a full build which includes all dependencies. Hopefully that works. Can you download the v0.2.0 binaries and please give that a try?

What version of the OS are you using?

Yes I am up and running with v0.2.0 👍