WikiSyllabus

Describe the Issue
To contribute to the open-source platform in mulearn called WikiSyllabus
Go to the src Folder

Navigate to the Wikisyllabus folder.
If you are contributing materials for other universities, create a new folder with the university's name (e.g., foldername: MG). Inside this folder, add a SUMMARY.md file and type the university's name (e.g., MG).

For contributions to KTU (Kerala Technological University):

There are two folders: 2019_scheme and 2015_scheme.

Inside each of these folders, there are seven folders, S1&S2 to S8.

Go to the folder corresponding to the semester you want to contribute.

Create a new folder with the course code as its name.

Add a SUMMARY.md file inside this folder and type the current folder's name, and the subject name. Add its index that your going to contribute md files
Example :-(If your Subject is C-programming)
# EST 102 - C PROGRAMMING
#### INDEX

- [Introduction to C Programming](./1intro.md)
- [Variables and Keywords](./2variables_keywords.md)
- [Datatypes](./3datatypes.md)

You can create one or more .md files in this folder. The names of these files should be specific to their content.

Adding Content to the .md File

If you have a PDF file, you can copy the text from the PDF and paste it into the .md file.
If there are any pictures in the PDF, take a screenshot and upload it at the appropriate position in the .md file.

If you are using GitHub for editing, you can easily drag and drop the image at the desired position.

If the study material you want to contribute is already present, do not add it again. However, if there are any changes or additions to the existing content, you can edit the corresponding .md file and add your content below the current one.

Adding Your Name to the Contributors List

Open the README.md file in the repository.
Add a new  inside the table like this:

.
Inside the  tag, add your details in the following format:

    Your_Name

  Give a symbol

Commit your changes and create a pull request.

All the files in this project are .md files. You would need to have Markdown knowledge to contribute to this project.

@Kochouseph26John What is the status of wikisyllabus task and bot in discord ?

There is an issue in production:-
How to get it:-
KTU
└── 2019_scheme
└── S6
└── CSE
└── CST306
Production Link:- WikiSyllabus
RESULT

Assign @vishakh-abhayan to solve it

There is an issue in production:-
How to get it:-
KTU └── 2019_scheme └── S6 └── CSE └── CST306
Production Link:- WikiSyllabus
RESULT

Assign @vishakh-abhayan to solve it

ok, i will look at it


ARROW-11482: [Rust] improve take kernel performance of PrimitiveArray

This PR simplifies the take_primitive a little bit and increases performance by using the new from_trusted_len_iterator API.
take i32 512            time:   [678.68 ns 692.27 ns 709.58 ns]
                        change: [-11.636% -10.615% -9.2359%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 15 outliers among 100 measurements (15.00%)
  5 (5.00%) high mild
  10 (10.00%) high severe

take i32 1024           time:   [1.1393 us 1.1477 us 1.1637 us]
                        change: [-18.397% -17.829% -17.075%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 9 outliers among 100 measurements (9.00%)
  1 (1.00%) low mild
  3 (3.00%) high mild
  5 (5.00%) high severe

take i32 nulls 512      time:   [643.87 ns 644.11 ns 644.37 ns]
                        change: [-20.604% -20.531% -20.458%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 13 outliers among 100 measurements (13.00%)
  2 (2.00%) low mild
  6 (6.00%) high mild
  5 (5.00%) high severe

take i32 nulls 1024     time:   [1.1381 us 1.1384 us 1.1387 us]
                        change: [-19.419% -19.054% -18.753%] (p = 0.00 < 0.05)
                        Performance has improved.

Thanks @ritchie46 !
Note that this collides with #9301 .

Thanks @ritchie46 !
Note that this collides with #9301 .

Right, great work on that PR! :) Then I will close this one.
I am also working on a perf increase of take_string. That one doesn't have collisions I presume?

Right, great work on that PR! :) Then I will close this one.

Thanks! :)

I am also working on a perf increase of take_string. That one doesn't have collisions I presume?

No collisions, just go ahead and ping me if you need any help or a review. Note that there may be out-of-bound reads on that code. It would be awesome if those were taken care of :)

Note that there may be out-of-bound reads on that code. It would be awesome if those were taken care of :)

Ah, right so we want to panic if we have out-of-bounds access even if check-bounds == false. There are quite some cases where I know upfront that all my indexes will be valid. Should we also expose an unsafe variant of the take kernels? Especially in groupby and join operations their performance is paramount.

in my experiments leading to #9301 I found no significant perf different between both variants and so did not consider an unsafe version, I admit that since the PR already offered a -30%, I also did not bother much ^_^
once all our implementations are safe, IMO we should get rid of the take options and potentially offer an unsafe version like you said. What imo is not cool is having an implementation whose safety depends on a parameter. :P

I admit that since the PR already offered a -30%, I also did not bother much ^_^

LOL.. That I can imagine.

What imo is not cool is having an implementation whose safety depends on a parameter. :P

Agreed. I must say that I really notice the public API getting more idiomatic as well. It feels good to be able to use iterators for the fastest implementation!


Windows, API->limit() generate an Error

Hello,
I make my development on Windows, when use your warpper and set this: $api->limit(x,y);  get a throw error: 'We could not load a valid limit interface.' (in LeagueWrap/Api.php => function limit() ).
This message isn't very "enlightening".
The problem is that the LeagueWrap/Limit/FileLimit.php want to create a file in '/tmp' folder but this folder do not exists in Windows! And another problem, wrapper need to have this folder in the drive root, where a app/script do not have permission to create a folder.
My drive tree:

C:
/xampp/htdocs/webapp/       <--- my .php scripts
/xampp/htdocs/webapp/vendor/LeagueWrap/...   <--- LoL wrapper
/xampp/php/                          <--- php .exe
/xampp/apache/                     <--- apache .exe
/xampp/tmp/                          <--- general /tmp folder, configured in php.ini

and I have to create this new folder to work correctly with your wrapper:

C:
/tmp/

One option is to inform the user that the folder does not exist (for him to manually create this folder) and another option is to set the location where this folder can be created, perhaps the folder where the webapp is running!
I'm not a *nix user and don't know if this problem can occurs in this *nix SO.
What you think?
Best regards,
LB
PS: Sorry my poor english!

Problem is Windows has other paths than Unix and this library is written to work on Unix. You can write your own filellimit implementation to use a custom path that's available on Windows though.

Thanks danijoo.
Best regards,
LB


chore: remove unused imports

These are all unused imports of files in Batteries, that are missed by shake because of noshake.

bors delegate+

bors merge


Organizations: Automatically manage devices for iOS

Describe the solution you'd like
The option to Automatically manage devices for iOS seems to only work for Individual accounts. It would be great if it also worked for iOS app belonging to an organization's team Id.
Describe alternatives you've considered
I could also manage this myself but it requires adding new devices each time we onboard somebody.
Additional context
https://docs.microsoft.com/en-us/appcenter/distribution/groups#automatically-manage-devices

Why, was this closed? Has the issue been fixed?

Thank you for the feature request! Currently, we are focusing on improving the reliability and performance of the service and new feature work is significantly reduced. To keep the team focused we are closing feature requests with no activity in the past 180 days. If you believe this is still relevant, feel free to create a new issue and tag this item so that we can review it. Sorry for the inconvenience.


C++ 20 compilation problem

Hello,
The library does not compile when C++20 is enabled. The std::result_of has been in removed in this version (https://en.cppreference.com/w/cpp/types/result_of).
Would it be possible to fix it?
Thank you.

Same problem here. Is the spdlog_setup project going to continue? It prevents us from updating spdlog and from being C++20 compatible, which is (going to be / already) a problem.
Thank you for your work and your time.


feat: Milestone 1

[x] Accordion
[x] Alert
[x] Alert dialog
[x] Badge
[x] Breadcrumb
[x] Button
[x] Typography

8cec3850d9cff6a3c910a8fba90ade8e55f88225


avoid to modify idl generate code in client

Bug Report
Please answer these questions before submitting your issue. Thanks!
I found java client use 10 idl files, c++ use 12 idl files, go use 11 idl files.
➜  grep 'namespace java' idl/* | wc -l
      10
➜  grep 'namespace go' idl/* | wc -l
      11
➜  grep 'namespace cpp' idl/* | wc -l
      12

Though java use 10 idl files, but java client only  generate 9 idl files code.
This is strange, and hard to maintain.
For java client,
I think either
just  remove namespace java from dns.thrift , not use the dns.thrift to generate java code.
or
use the generate code of dns.thrift, modify the java-thrift  lib.

What did you do?
If possible, provide a recipe for reproducing the error.

What did you expect to see?

What did you see instead?

What version of Pegasus are you using?

Maybe it's a mistake, I'll check it later!

@shalk

java client use 10 idl files, c++ use 12 idl files, go use 11 idl files

It's because each language client has different function set. For example, the admin-cli is using go-client to support some CLI commands, but the Java client doesn't have such function. So you can see the go-client use an extra idl/replica_admin.thrift.

Though java use 10 idl files, but java client only generate 9 idl files code

Yes, the dsn.thrift is used for place holder, I'll try to clarify it.


[Bug]: Mixtral8x7B very high spikes for Inter Token Latency (ITL)

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

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

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

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

CPU:
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Address sizes:                      46 bits physical, 57 bits virtual
Byte Order:                         Little Endian
CPU(s):                             128
On-line CPU(s) list:                0-127
Vendor ID:                          GenuineIntel
Model name:                         Intel(R) Xeon(R) Gold 6438Y+
CPU family:                         6
Model:                              143
Thread(s) per core:                 2
Core(s) per socket:                 32
Socket(s):                          2
Stepping:                           8
BogoMIPS:                           4000.00
Flags:                              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cat_l2 cdp_l3 invpcid_single cdp_l2 ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local split_lock_detect avx_vnni avx512_bf16 wbnoinvd dtherm ida arat pln pts hfi vnmi avx512vbmi umip pku ospke waitpkg avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq la57 rdpid bus_lock_detect cldemote movdiri movdir64b enqcmd fsrm md_clear serialize tsxldtrk pconfig arch_lbr ibt amx_bf16 avx512_fp16 amx_tile amx_int8 flush_l1d arch_capabilities
Virtualization:                     VT-x
L1d cache:                          3 MiB (64 instances)
L1i cache:                          2 MiB (64 instances)
L2 cache:                           128 MiB (64 instances)
L3 cache:                           120 MiB (2 instances)
NUMA node(s):                       2
NUMA node0 CPU(s):                  0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,54,56,58,60,62,64,66,68,70,72,74,76,78,80,82,84,86,88,90,92,94,96,98,100,102,104,106,108,110,112,114,116,118,120,122,124,126
NUMA node1 CPU(s):                  1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39,41,43,45,47,49,51,53,55,57,59,61,63,65,67,69,71,73,75,77,79,81,83,85,87,89,91,93,95,97,99,101,103,105,107,109,111,113,115,117,119,121,123,125,127
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit:        Not affected
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Not affected
Vulnerability Retbleed:             Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; Enhanced / Automatic IBRS; IBPB conditional; RSB filling; PBRSB-eIBRS SW sequence; BHI BHI_DIS_S
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected

Versions of relevant libraries:
[pip3] No relevant packages
[conda] Could not collect
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: N/A
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0    GPU1    GPU2    GPU3    CPU Affinity    NUMA Affinity   GPU NUMA ID
GPU0     X      NODE    SYS     SYS     0,2,4,6,8,10    0               N/A
GPU1    NODE     X      SYS     SYS     0,2,4,6,8,10    0               N/A
GPU2    SYS     SYS      X      NODE    1,3,5,7,9,11    1               N/A
GPU3    SYS     SYS     NODE     X      1,3,5,7,9,11    1               N/A

Legend:

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

🐛 Describe the bug
Mixtral8x7B (unquantized) is heavily lagging on 4 x L40. I see pauses of 3-5 seconds in my output streams:

On 2 x A100 this is not the case:

What could be the problem with the 4 x L40 setup?
Is it just the missing NVLink? But I have seen Smartphone-Demos, that are faster than that...it cannot be that bad.
I use the vLLM OpenAI docker container and the benchmarks/benchmark_serving.py with openai-chat, Sonnet and 4k In/500 Out Tokens. I tried with chunked_prefill and without, same problem.
services:
  vllm-mixtral-instruct:
    image: vllm/vllm-openai:v0.4.3
    container_name: vllm-mixtral-instruct
    ipc: host
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              capabilities: [ gpu ]
    environment:
      - HTTPS_PROXY=http://proxy.dev.init:3128
      - HTTP_PROXY=http://proxy.dev.init:3128
      - NO_PROXY=<IP_ADDRESS>/22,<IP_ADDRESS>/8
      - NVIDIA_VISIBLE_DEVICES=0,1,2,3
      - HF_TOKEN=$HF_TOKEN
      - VLLM_NO_USAGE_STATS=1
    volumes:
      - /mnt/sda/huggingface:/root/.cache/huggingface
      - .:/opt/vllm
    ports:
      - "8000:8000"
    command:
      - --model=mistralai/Mixtral-8x7B-Instruct-v0.1
      - --chat-template=/opt/vllm/template_mixtral.jinja
      # - --max-model-len=24576
      - --tensor-parallel-size=4
      - --swap-space=10
      - --gpu-memory-utilization=0.8
      - --max-num-batched-tokens=1024
      - --disable-log-requests
      - --enforce-eager
      - --enable-chunked-prefill
    restart: unless-stopped

May be related to #5535


The '+' signs are not visible on the document page

Attempted Debugging

[X] I have read the debugging page

Searched GitHub Issues

[X] I have searched GitHub for the issue.

Describe the Scenario
Hi,
I've been using bookstack for a long time. Recently, I came across a problem where after saving the document on the page, the '+' sign is not visible. The sign is visible when I edit the document and the search engine sees it because when I enter '+' in the search field, the system will indicate the document that contains it.
Have any of you encountered this problem? I am asking for help in solving it or a hint in which files I can look for a solution to the problem.
I attach photos with a graphic description of the problem.
Regards!

Exact BookStack Version
v21.12.1
Log Content
No response
PHP Version
7.3
Hosting Environment
Debian 10.

Hi @alabastrowa,
This is not something I can reproduce on our demo instance which runs the latest version.
I'd guess this issue is only relevant to an older version of BookStack and has since been addressed, or it's an issue specific to your environment.
If you upgrade to use the latest version, and the issue persists, I can help in diagnosing the potential issue further but I otherwise don't support older versions.

Hi,
Thanks for the answer. And is it possible for me to test install the bookstack version that I have, i.e. v21.12.1 without any modifications? I would like to compare the files on the new machine with what I have at home to find differences.
Unfortunately, I cannot find v21.12.1 online. Maybe you own it and it would be possible for you to share it with me?
Regards.

@alabastrowa I'm not sure I understand. Are you trying to see if your version has modifications? Is so, and you followed our general install guidance originally, your instance should be managed via git. You could run git status to show any changes that have been made to core app files.
Otherwise, you can get a download of the v21.12.1 files from the bottom of this release page, if that's what you're asking for.
Note: You should not install from a ZIP or plain files, you should manage the codebase via git otherwise updates will be difficult.

So how well do I understand the following files in the source code (zip) will allow me to install bookstack v21.12.1?

Sorry, I still don't really understand.
I do not advise installing/updating via ZIPs of source code. Unless using container-based options, installs should be managed via git as per our official documentation/guidance.


[JBallerina] Ambiguous type error for union types

Description:
The following program fails when compiling. The output of jballerina build command is also given below.
public function main() {
    MyRecord rec = {
        scopes: [["scope1"]]
    };
}

type MyRecord record {
    string[]|string[][] scopes;
};

Output:
Compiling source
    hello.bal
error: .::hello.bal:6:18: incompatible types: expected 'other', found 'other'
error: .::hello.bal:6:17: ambiguous type '(string[]|string[][])'

Duplicate of https://github.com/ballerina-platform/ballerina-lang/issues/16300, and will be fixed with https://github.com/ballerina-platform/ballerina-lang/pull/16301


Permanent Project States

Install Permanent states as "Organisation", "Sick".

Organisation is always default on page "Working Time"

Pause is also a state


merge jobs in go.yml

merge some jobs in workflow files go.yml so we can have
less concurrent jobs for one PR to reduce github runner waiting time.
Part of #2014
Signed-off-by: Lan Luo<EMAIL_ADDRESS>

Hi @tnqn @lzhecheng  I moved a part of #2245 to this PR since  this change will impact the required job items for a PR, and need maintainer to update the require items in github setting.

Codecov Report

Merging #2474 (a4a8bcb) into main (42077cb) will decrease coverage by 19.66%.
The diff coverage is n/a.

:exclamation: Current head a4a8bcb differs from pull request most recent head dd2ddcf. Consider uploading reports for the commit dd2ddcf to get more accurate results

@@             Coverage Diff             @@
##             main    #2474       +/-   ##
===========================================
- Coverage   61.70%   42.04%   -19.67%
===========================================
  Files         276      146      -130
  Lines       21317    18115     -3202
===========================================
- Hits        13154     7616     -5538
- Misses       6782     9817     +3035
+ Partials     1381      682      -699

Flag
Coverage Δ

kind-e2e-tests
?

unit-tests
42.04% <ø> (+0.81%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/util/k8s/name.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/agent/agent_linux.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/ovs/openflow/default.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/agent/config/node_config.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/apis/controlplane/helper.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/agent/cniserver/pod_configuration_linux.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/apis/controlplane/v1beta1/register.go
0.00% <0.00%> (-92.86%)
:arrow_down:

pkg/ovs/openflow/logs.go
9.52% <0.00%> (-90.48%)
:arrow_down:

pkg/apis/controlplane/register.go
0.00% <0.00%> (-90.00%)
:arrow_down:

pkg/agent/nodeportlocal/k8s/annotations.go
0.00% <0.00%> (-83.88%)
:arrow_down:

... and 239 more

@antoninbas ,  it might not a significant change, but merge jobs can help to reduce some repeated steps like code checkout, so even one job is longer than before, it's shorter than the total time of all merged jobs. each job is running in independent github runner, I believe it will also help to reduce the instance launch/shutdown time.

@antoninbas  thanks , I just resolved the conflicts.

/skip-all

Ignoring Kind test failure for this change


PartitionPlacementActor-fix

Actually when a grain is stopped and we ask a new activation, it is redeployed elsewhere. But when it is redeployed on the same node, the PartitionPlacementActor returns the previous address as it is never removed from the _myActors dictionary and never spawn the new actor. When an actor is terminated I remove this pid from _myActors to fix that.

Good catch!


Design analysis ready Zarr to allow updating with preliminary ERA5 data.

For phase 2, we'd like to produce surface and atmospheric Zarrs that can be updated with preliminary data. Specifically, we intend to backfill the raw data covering 1959 to 1978. It's possible that in the future, ECMWF will produce an even earlier backfill.  As I understand it, the standard structure of Zarr only allow appending to the end.
The aim for this issue would be to devise a means of avoiding recomputing our Zarr datasets whenever we want to include new data at earlier times.
For overall pipeline structure, I have the following sketch in mind:

For each epoch of preliminary data we ingest from ECMWF, we manually produce a new cloud optimized dataset. This can use the scripts in this project that we've already developed.
For recent data, we use Pangeo components update the cloud-optimized datasets (e.g. https://github.com/pangeo-forge/pangeo-forge-recipes/issues/447). These download and append steps can be automated to a regular cadence (monthly or quarterly).
For the analysis ready version, we create XArray-Beam pipelines to transform the Zarr datasets.
After a new cloud-optimized preliminary dataset is produced, we invoke the same XArray-Beam pipelines to update the analysis ready versions.

@shoyer @rabernat: Do either of you have any thoughts on how we could structure our Zarr to these ends?

Fixed by @DarshanSP19 and @dabhicusp; will mark closed.


"exec format error" with cilium set as default CNI in all.yml if you are installing to an ARM cluster

Details
What steps did you take and what happened:
Built a cluster per instructions on Raspberry Pi 4 nodes, using boot images based on latest ubuntu 20.04
What did you expect to happen:
CNI should start up using images built for ARM architecture
Anything else you would like to add:
cilium.yml runs a kubectl apply using a yml that references an incompatible image for ARM.
Additional Information:

Note: Anything to give further context to the bug report.

Looks like Cilium 1.10 supports ARM
Also - the quick installation process changed from 1.9 to 1.10. In the 1.10 install they aren't providing a quick-install.yml file. In 1.10 the quick install process uses a new installer.

Yep thanks for raising this I did run into this issue myself and had it in my list of TODOS.

@xUnholy - re ^^ I'm trying to figure out how to successfully build a cluster with calico as CNI instead of cilium (it appears cilium is set as default - which as of right now is broken for pi clusters.)
After fishing around I changed the value from cilium to calico in each of these locations:

group_vars/all.yml:                           cni_plugin: 'cilium'
group_vars/controlplane.yml           cni_plugin: cilium
roles/cni/defaults/main.yml              cni_plugin: cilium

I ran nuke.yml, then changed cilium to calico in above locations, then ran all.yml again. Everything looked good until the end:
TASK [cni : setup calico container network interface (cni)] ****************************************************************************************************************************************************
Saturday 11 September 2021  16:48:57 -0700 (0:00:00.218)       0:07:06.331 ****
skipping: [strawberry]
skipping: [blueberry]
skipping: [blackberry]
skipping: [gooseberry]
included: /Users/almondch/GH/raspbernetes/k8s-cluster-installation-1/ansible/roles/cni/tasks/calico.yml for hackberry

TASK [cni : applying calico] ***********************************************************************************************************************************************************************************
Saturday 11 September 2021  16:48:57 -0700 (0:00:00.269)       0:07:06.601 ****
fatal: [hackberry]: FAILED! => changed=true
  cmd:
  - kubectl
  - apply
  - -f
  - https://docs.projectcalico.org/manifests/calico.yaml
  delta: '0:00:11.712726'
  end: '2021-09-11 16:49:12.059033'
  msg: non-zero return code
  rc: 1
  start: '2021-09-11 16:49:00.346307'
  stderr: 'Error from server (InternalError): an error on the server ("") has prevented the request from succeeding'
  stderr_lines: <omitted>
  stdout: ''
  stdout_lines: <omitted>

PLAY RECAP *****************************************************************************************************************************************************************************************************
<IP_ADDRESS>                  : ok=1    changed=0    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0
blackberry                 : ok=64   changed=16   unreachable=0    failed=0    skipped=26   rescued=0    ignored=0
blueberry                  : ok=85   changed=17   unreachable=0    failed=0    skipped=26   rescued=0    ignored=0
gooseberry                 : ok=64   changed=16   unreachable=0    failed=0    skipped=26   rescued=0    ignored=0
hackberry                  : ok=121  changed=21   unreachable=0    failed=1    skipped=28   rescued=0    ignored=0
strawberry                 : ok=87   changed=17   unreachable=0    failed=0    skipped=28   rescued=0    ignored=0

update re ^^ - after manually applying the calico manifest I hit some certificate errors that prevented pods from completely starting up the CNI. Eventually all calico pods failed. I suspect some cruft in the OS level that the ansible playbooks weren't able to clean up was causing it. So I reimaged all nodes again and started fresh. Cluster build fine, using calico instead of cilium config changes noted above.

re ^^ now I'm noticing kube-proxy is not running. Guessing there is something going on the playbooks that disabled kube-proxy expecting cilium/eBPF stuff will be running instead...?

This final issue will be caused due to this configuration https://github.com/raspbernetes/k8s-cluster-installation/blob/93df5197a7b647db481b56c2dfd4b0ad635192c1/ansible/group_vars/controlplane.yml#L16
You've done well to troubleshoot these issues, if you want to push a fix for the cilium feel free otherwise I'll try get a fix out for it this week sometime.

^^ it was right in front of me inside controlplane.yml :-P


'true' by itself is parsed as 'True' in .bst files

See original issue on GitLab
In GitLab by [Gitlab user @aevri] on Feb 21, 2019, 11:37
Summary
In a .bst file, if I have a list item 'true', it will be parsed as 'True'. The same for 'false'. This appears to be an artefact of yaml interpreting it as an actual boolean value.
For example, this manual element will try to execute 'True' rather than 'true' during configure:
kind: manual
([[Gitlab user @]](https://gitlab.com/)): includes/important_things
config:
  configure-commands:
  - true

This isn't a very important issue. I sometimes do use stuff like this to debug my bst files.
Steps to reproduce
Adapting the great BuildStream first project doc:
# Note that your filesystem needs to be case-sensitive for this to fail.
bst init --project-name first-project
mkdir elements
cat > elements/true.bst <<EOF
kind: import

# Use a local source to stage our file
sources:
- kind: local
  path: true
EOF
touch true
bst build true.bst

What is the current bug behavior?
In the repro example, you will see:
true.bst [line 6 column 8]: Specified path 'True' does not exist

What is the expected correct behavior?
The element should build successfully.
Possible fixes

In GitLab by [Gitlab user @tristanvb] on Feb 22, 2019, 11:36
We fixed an issue in the past where some branch and tag names were being parsed as if they were integers,  by forcing the ints to be parsed as strings. This was especially important for the round tripping, where some tag names would change value after being parsed due to being treated as a number.
I suspect that if we are loading this value as a boolean, then this is also a bug when it comes to round tripping. I.e. it is possible (or likely even ?) that boolean values specified as true will end up being erroneously saved as True as a result of running bst track and rewriting a .bst file.
I am thinking that the right fix would be to treat booleans in the same way we treat numbers, and insert some manual string handling for loading boolean values from strings deep in _yaml.node_get().

In GitLab by [Gitlab user @danielsilverstone-ct] on Mar 29, 2019, 08:08
This was a side-effect of the way we were parsing YAML before !1257 was merged.  Now that it has been, I believe this issue is resolved.

In GitLab by [Gitlab user @danielsilverstone-ct] on Mar 29, 2019, 08:08
closed


Import Issues in Next.js 14 with Server Actions

Problem Description
An import issue has been identified in Next.js 14 when using Server Actions. Although the project functions using memoryDriver, import errors are observed in the console when running the project. Even when recreating the issue in a new empty Next.js 14 template with App Router, import issues persist in the console, although it works at least using memoryDriver.
A minimal reproducible example has been provided in StackBlitz.
Steps to Reproduce the Problem

Clone the repository bento-nextjs.
Run npm install to install the dependencies.
Run npm run dev to start the development server.

Console Output
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
<EMAIL_ADDRESS>./node_modules/bentocache/build/index.js
./bentocache.ts
./actions/counter.ts
./app/page.tsx

Project Dependencies
{
  "name": "bento-nextjs",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "bentocache": "^1.0.0-beta.8",
    "next": "14.2.0",
    "react": "^18",
    "react-dom": "^18"
  },
  "devDependencies": {
    "@types/node": "^20",
    "@types/react": "^18",
    "@types/react-dom": "^18",
    "eslint": "^8",
    "eslint-config-next": "14.2.0",
    "postcss": "^8",
    "tailwindcss": "^3.4.1",
    "typescript": "^5"
  }
}

Minimal Reproducible Example
The minimal reproducible example can be found in the provided StackBlitz.
Additional Information
Apparently, the import issue might be related to the usage of @poppinss/utils.
Any guidance or solution to address these import issues in Next.js 14 would be appreciated.
Thank you for your attention to this matter!
Sincerely,
Valentin

Hey. Thanks for the feedback
So, this is a problem with Next and more specifically Webpack. Here https://github.com/poppinss/utils/blob/develop/src/fs_import_all.ts#L47 we're using a dynamic await import, so with a variable. And webpack complains that it can't statically analyze what's imported.
So I would recommend two solutions:

Ignore and silence errors. As recommended and demonstrated by Typeorm here: https://typeorm.io/faq#how-to-use-webpack-for-the-backend. You could adapt the FilterWarning plugin to ignore this specific error
Use Turbopack. By testing on your repro, the error no longer appears when used with turbopack

There's the /* webpackIgnore */ ( https://webpack.js.org/api/module-methods/#webpackignore ) solution that could be applied, but I'm not sure I want to do it as Next will be migrating to Turbopack very soon. You can use a patch to use this solution if you prefer
Let me know if it sounds good to you!

Hello.
I faced the same issue since some months, and just ignored it until today.
I was using Bentocache to cache (in-memory) avatars URLs.
I'm now upgrading to Next Auth v5, and everything broke.
Got this error:

Import trace for requested module:
node:fs/promises
./node_modules/.pnpm/@poppinss+utils<EMAIL_ADDRESS>./node_modules/.pnpm/bentocache<EMAIL_ADDRESS>./src/config/bentocache.ts
./src/config/Auth/authOptions.ts
./src/components/layouts/navbar/NavbarLoginButton.tsx
node:path
Module build failed: UnhandledSchemeError: Reading from "node:path" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
at /home/stan/Deliv/dashboard_rtm/node_modules/.pnpm/> next@14.2.1_@babel+core@7.24.4_@opentelemetry+api@1.8.0_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:401757

Tried to patch it like this:
// next.config.js
/* v8 ignore start */
// Stryker disable all
// @ts-check

const { webpack } = require('next/dist/compiled/webpack/webpack');

const { withContentlayer } = require('next-contentlayer');
const withBundleAnalyzer = require('@next/bundle-analyzer')({
  enabled: process.env.ANALYZE === 'true'
});

const ignoreBuildErrors = process.env.IGNORE_BUILD_ERRORS === 'true';
const ignoreEslintDuringBuilds = process.env.IGNORE_ESLINT_DURING_BUILDS === 'true';

/** @type {import('next').NextConfig} */
const nextConfig = {
  // eslint-disable-next-line require-await
  async redirects() {
    return [
      /* eslint-disable perfectionist/sort-objects */
      {
        source: '/:lng/lp',
        destination: '/:lng/lp/sign-up',
        permanent: true
      },
      {
        source: '/lp',
        destination: '/lp/sign-up',
        permanent: true
      }
      /* eslint-enable perfectionist/sort-objects */
    ];
  },

  // * ... here!
  webpack: (config) => {
    config.plugins.push(
      new webpack.NormalModuleReplacementPlugin(/node:/, (resource) => {
        resource.request = resource.request.replace(/^node:/, '');
      })
    );
    return config;
  },

  eslint: {
    ignoreDuringBuilds: ignoreEslintDuringBuilds
  },

  images: {
    domains: ['cdn.discordapp.com']
  },

  typescript: {
    ignoreBuildErrors
  },

  reactStrictMode: true,
  swcMinify: true
};

module.exports = withBundleAnalyzer(withContentlayer(nextConfig));

// Stryker restore all
/* v8 ignore stop */

Generated 97 documents in .contentlayer
Failed to compile.
./node_modules/.pnpm/@poppinss+utils<EMAIL_ADDRESS>Module not found: Can't resolve 'fs/promises'
https://nextjs.org/docs/messages/module-not-found
Import trace for requested module:
./node_modules/.pnpm/bentocache<EMAIL_ADDRESS>./src/config/bentocache.ts
./src/config/Auth/authOptions.ts
./src/components/layouts/navbar/NavbarLoginButton.tsx
Build failed because of webpack errors

Built again from scratch a project with Next Auth v5.
./node_modules/.pnpm/@poppinss+utils<EMAIL_ADDRESS>Critical dependency: the request of a dependency is an expression

Import trace for requested module:
./node_modules/.pnpm/@poppinss+utils<EMAIL_ADDRESS>./node_modules/.pnpm/bentocache<EMAIL_ADDRESS>./src/config/bentocache.ts
./src/auth.ts
./src/app/api/[...nextauth]/route.ts

Failed to compile.

node:crypto
Module build failed: UnhandledSchemeError: Reading from "node:crypto" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
    at /home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:401757
    at Hook.eval [as callAsync] (eval at create (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:15:28858), <anonymous>:6:1)
    at Object.processResource (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:401682)
    at processResource (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:5308)
    at iteratePitchingLoaders (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:4667)
    at runLoaders (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:8590)
    at NormalModule._doBuild (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:401544)
    at NormalModule.build (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:403572)
    at /home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:82055
    at NormalModule.needBuild (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:407670)

Import trace for requested module:
node:crypto
./node_modules/.pnpm/@poppinss+utils<EMAIL_ADDRESS>./node_modules/.pnpm/bentocache<EMAIL_ADDRESS>./src/config/bentocache.ts
./src/auth.ts

node:fs/promises
Module build failed: UnhandledSchemeError: Reading from "node:fs/promises" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
    at /home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:401757
    at Hook.eval [as callAsync] (eval at create (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:15:28858), <anonymous>:6:1)
    at Object.processResource (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:401682)
    at processResource (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:5308)
    at iteratePitchingLoaders (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:4667)
    at runLoaders (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:8590)
    at NormalModule._doBuild (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:401544)
    at NormalModule.build (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:403572)
    at /home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:82055
    at NormalModule.needBuild (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:407670)

Import trace for requested module:
node:fs/promises
./node_modules/.pnpm/@poppinss+utils<EMAIL_ADDRESS>./node_modules/.pnpm/bentocache<EMAIL_ADDRESS>./src/config/bentocache.ts
./src/auth.ts

node:path
Module build failed: UnhandledSchemeError: Reading from "node:path" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
    at /home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:401757
    at Hook.eval [as callAsync] (eval at create (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:15:28858), <anonymous>:6:1)
    at Object.processResource (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:401682)
    at processResource (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:5308)
    at iteratePitchingLoaders (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:4667)
    at runLoaders (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:8590)
    at NormalModule._doBuild (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:401544)
    at NormalModule.build (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:403572)
    at /home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:82055
    at NormalModule.needBuild (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:407670)

Import trace for requested module:
node:path
./node_modules/.pnpm/@poppinss+utils<EMAIL_ADDRESS>./node_modules/.pnpm/bentocache<EMAIL_ADDRESS>./src/config/bentocache.ts
./src/auth.ts

node:url
Module build failed: UnhandledSchemeError: Reading from "node:url" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
    at /home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:401757
    at Hook.eval [as callAsync] (eval at create (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:15:28858), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:15:26012)
    at Object.processResource (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:401682)
    at processResource (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:5308)
    at iteratePitchingLoaders (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:4667)
    at runLoaders (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:8590)
    at NormalModule._doBuild (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:401544)
    at NormalModule.build (/home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:403572)
    at /home/stan/Deliv/next-auth-v5-test/node_modules/.pnpm/next@14.2.2_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:30:82055

Import trace for requested module:
node:url
./node_modules/.pnpm/@poppinss+utils<EMAIL_ADDRESS>./node_modules/.pnpm/bentocache<EMAIL_ADDRESS>./src/config/bentocache.ts
./src/auth.ts

./src/config/bentocache.ts
Dynamic Code Evaluation (e. g. 'eval', 'new Function', 'WebAssembly.compile') not allowed in Edge Runtime
Learn More: https://nextjs.org/docs/messages/edge-dynamic-code-evaluation

The error was caused by importing 'bentocache/build/index.js' in './src/config/bentocache.ts'.

Import trace for requested module:
  ./src/config/bentocache.ts
  ./src/auth.ts
  ./src/middleware.ts

Dynamic Code Evaluation (e. g. 'eval', 'new Function', 'WebAssembly.compile') not allowed in Edge Runtime
Learn More: https://nextjs.org/docs/messages/edge-dynamic-code-evaluation

Interesting...
It seems that the unification of the API using auth in Auth.js (formerly Next Auth) v5 reveals issues in Edge Runtime with Bentocache.


fixed issue#53578

Checklist:

[x] I have read and followed the contribution guidelines.
[ ] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

HI @KhushiSharma0313 !
I am going to close this PR since it looks like changes were made to the wrong files and it is not clear what issue this PR is targeting.
If you are interested in contributing in the future, please make sure to read through the guide first.
When you open a PR, make sure to link the issue that corresponds to the PR.
If you need help with contributing, it best to reach out on the forum or discord so people can help 👍


Cannot able to import python modules.

Python doesn't have cv2 installed by default.

Python doesn't have cv2 installed by default.

CV2 has installed already in Python but not able to sync with Unreal Engine 5


SME overhaul mixin doesn't recognize adept enchantments in SME

I loaded minecraft with the minimum settings required for the 'SME overhaul' mixin but an unexpected crash occurred.
net.minecraftforge.fml.common.LoaderExceptionModCrash: Caught exception from Rin's So Many Enchantments? (somanyenchantments)
Caused by: java.lang.NoClassDefFoundError: com/Shultrea/Rin/Ench0_4_0/EnchantmentAdept
Caused by: org.spongepowered.asm.mixin.transformer.throwables.MixinTransformerError: An unexpected critical error was encountered
Absolutely no idea why I'm getting NoClassDefFoundError even though SME is installed properly.
Only SME-related options were turned on.
are there any unspecified dependencies in the option?
crash-2023-09-11_17.43.30-client.txt

That class annoying imported Charm's EnchantmentHelper instead of Vanilla's EnchantmentHelper, it will be fixed in the next update.


Path params fix

Hello, here is the last PR fresh with the changes requested. Created another PR since my master branch was out of sorts. Let me know if you spot any problems. Thanks

@johnsusek cheers!


[fix] Fixes for all packages and dependencies

Status
PRODUCTION / DEVELOPMENT
Description

Fixed all the packages for its release.
Cleaned dependencies.
Added travis configuration for indigo and kinetic.

Related PRs
#1156 #1218
Todos

[X] Tests
[X] Documentation

I resolved conflict by my PR #1191 .

@yk-fujii thanks for fixing the conflict!

@kfunaoka @aohsato @kitsukawa
Please review :)


Django instrumentation silently doesn't work for ASGI requests

A user couldn't get the Django instrumentation working (https://pydanticlogfire.slack.com/archives/C06EDRBSAH3/p1722460460137619?thread_ts=1722440635.372479&cid=C06EDRBSAH3). With difficulty we realised that it was because they were using ASGI. In opentelemetry/instrumentation/django/middleware/otel_middleware.py you can see that ASGI requests are silently ignored when opentelemetry-instrumentation-asgi isn't installed.
Firstly, we should document this loudly.
Then for people who miss this point, we should either:

Try to detect ASGI requests and warn the user if needed. Not sure how easy this is.
Add a mandatory is_asgi parameter to instrument_django to force the user to tell us the situation, then raise an error if needed.
Always install opentelemetry-instrumentation-asgi with the django extra.
Remove the django extra and replace it with django-wsgi and django-asgi.

@samuelcolvin what do you think?

Remove the django extra and replace it with django-wsgi and django-asgi.

We can also just add django-async.

The first step here is to document this.

Remove the django extra and replace it with django-wsgi and django-asgi.

We can also just add django-async.

The idea is that the user has to be aware of the distinction and make an explicit choice. If they don't check docs carefully they may easily think that pip install logfire[django] should just work, they won't get an error at any point.

The easiest here is to add opentelemetry-instrumentation-asgi to the django extras...

In the meantime, while we don't solve this... I've added a note to the docs: https://github.com/pydantic/logfire/pull/630

We now have a note on the top of the Django page about this:


Bug: When running e2e test on a KIND cluster in local, find cypress issues

https://github.com/vmware-tanzu/cloud-native-security-inspector/issues/162#issuecomment-1429248314
Check above comment for reference.

I cannot repro this issue on my Mac


[ERROR] 15:13:55 Error: Cannot set headers after they are sent to the client

🔎 Search Terms
Error: Cannot set headers after they are sent to the client
🕗 Version & Regression Information

This is a crash
This changed between versions ______ and _______
This changed in commit or PR _______
This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
I was unable to test this on prior versions because _______

⏯ Playground Link
No response
💻 Code
// Your code here

🙁 Actual behavior
Using typescript to write the backend interface, this error message appears after a normal response to a request, causing the entire program to end abnormally, unable to respond to subsequent requests.
[ERROR] 15:13:55 Error: Cannot set headers after they are sent to the client
🙂 Expected behavior
The request is responded to normally and does not affect the normal execution of other requests.
Additional information about the issue
No response

Adding "@Res() res: Response" to the controller's method parameter successfully solved the response problem.
As:
`import { Controller, Get, Res } from '@nestjs/common';
import { Response } from 'express';
@Controller('test')
export class CatsController {
@Get()
testRes(@Res() res: Response) {
res.status(200).send('OK');
}
}`

It looks like this is a question rather than a bug report. This issue tracker is for tracking bugs and active work on TypeScript itself, rather than a general forum for programmers using TypeScript to get help or ask questions.
You can ask questions on sites like Stack Overflow. We are not able to provide one-on-one support on the issue tracker. Please read the issue template carefully - it has important information on what kinds of reports can be acted on here, as well as links to useful TypeScript resources. Thanks!


RuntimeError not showing up in Sentry log

sentry_version: 3.0.0
erlang: OTP 19/erts-8.3
elixir: 1.4.1
I noticed that certain errors don't get reported by sentry.
For example, I can see this error in my server log, but it does not show up in the sentry error list.
This error was raised as a RuntimeError as raise "Could not retrieve resource from Stripe."
I have use_error_logger set to true. I tested that the ThisWillError.real() error from the docs is reported when I paste that code into a remote_console.
%{"error" => %{"code" => "incorrect_cvc",
    "message" => "Your card's security code is incorrect.", "param" => "cvc",
    "type" => "card_error"}}
2017-03-25 00:40:55.646 [error] GenServer #PID<0.1732.0> terminating
** (RuntimeError) Could not retrieve resource from Stripe.
    (myapp) lib/stripe_client.ex:41: MyApp.StripeClient.post!/2
    (myapp) lib/billing/payment_source.ex:18: MyApp.Billing.PaymentSource.add!/2
    (myapp) web/channels/users_channel.ex:84: MyApp.UsersChannel.handle_in/3
    (phoenix) lib/phoenix/channel/server.ex:226: anonymous fn/4 in Phoenix.Channel.Server.handle_info/2
    (stdlib) gen_server.erl:601: :gen_server.try_dispatch/4
    (stdlib) gen_server.erl:667: :gen_server.handle_msg/5
    (stdlib) proc_lib.erl:247: :proc_lib.init_p_do_apply/3

  =CRASH REPORT==== 25-Mar-2017::00:40:55 ===
  crasher:
    initial call: Elixir.Phoenix.Channel.Server:init/1
    pid: <0.1732.0>
    registered_name: []
    exception exit: {#{'__exception__' => true,
                       '__struct__' => 'Elixir.RuntimeError',
                       message =>
                           <<"Could not retrieve resource from Stripe.">>},
                     [{'Elixir.MyApp.StripeClient','post!',2,
                          [{file,"lib/stripe_client.ex"},{line,41}]},
                      {'Elixir.MyApp.Billing.PaymentSource','add!',2,
                          [{file,"lib/billing/payment_source.ex"},{line,18}]},
                      {'Elixir.MyApp.UsersChannel',handle_in,3,
                          [{file,"web/channels/users_channel.ex"},{line,84}]},
                      {'Elixir.Phoenix.Channel.Server',
                          '-handle_info/2-fun-4-',4,
                          [{file,"lib/phoenix/channel/server.ex"},{line,226}]},
                      {gen_server,try_dispatch,4,
                          [{file,"gen_server.erl"},{line,601}]},
                      {gen_server,handle_msg,5,
                          [{file,"gen_server.erl"},{line,667}]},
                      {proc_lib,init_p_do_apply,3,
                          [{file,"proc_lib.erl"},{line,247}]}]}
      in function  gen_server:terminate/7 (gen_server.erl, line 812)
    ancestors: [<0.1727.0>]
    messages: []
    links: [<0.1583.0>,<0.1727.0>]
    dictionary: []
    trap_exit: false
    status: running
    heap_size: 4185
    stack_size: 27
    reductions: 19937
  neighbours:

Hi, thanks for reporting this!
Do you know if other errors within Phoenix channels report properly?

I'll try it out in a bit and let you know.

Tested generating an UndefinedFunctionError.
  # web/channels/users_channel.ex
  def handle_in("get_main_data", %{}, socket) do
    BadModule.does_not_exist()
    # some more code
  end

This error is reported in the server log, but the error does not show up in sentry.
[info] USERS_CHANNEL: [socket: %Phoenix.Socket{assigns: %{user_id: 10}, channel: MyApp.UsersChannel, channel_pid: #PID<0.1735.0>, endpoint: MyApp.Endpoint, handler: MyApp.UserSocket, id: nil, joined: true, pubsub_server: MyApp.PubSub, ref: "2", serializer: Phoenix.Transports.WebSocketSerializer, topic: "user:10", transport: Phoenix.Transports.WebSocket, transport_name: :websocket, transport_pid: #PID<0.1734.0>}]
2017-03-31 04:42:39.300 [error] GenServer #PID<0.1735.0> terminating
** (UndefinedFunctionError) function BadModule.does_not_exist/0 is undefined (module BadModule is not available)
    BadModule.does_not_exist()
    (myapp) web/channels/users_channel.ex:39: MyApp.UsersChannel.handle_in/3
    (phoenix) lib/phoenix/channel/server.ex:226: anonymous fn/4 in Phoenix.Channel.Server.handle_info/2
    (stdlib) gen_server.erl:601: :gen_server.try_dispatch/4
    (stdlib) gen_server.erl:667: :gen_server.handle_msg/5
    (stdlib) proc_lib.erl:247: :proc_lib.init_p_do_apply/3
Last message: %Phoenix.Socket.Message{event: "get_main_data", payload: %{}, ref: "2", topic: "user:10"}
State: %Phoenix.Socket{assigns: %{user_id: 10}, channel: MyApp.UsersChannel, channel_pid: #PID<0.1735.0>, endpoint: MyApp.Endpoint, handler: MyApp.UserSocket, id: nil, joined: true, pubsub_server: MyApp.PubSub, ref: nil, serializer: Phoenix.Transports.WebSocketSerializer, topic: "user:10", transport: Phoenix.Transports.WebSocket, transport_name: :websocket, transport_pid: #PID<0.1734.0>}

=CRASH REPORT==== 31-Mar-2017::04:42:39 ===
  crasher:
    initial call: Elixir.Phoenix.Channel.Server:init/1
    pid: <0.1735.0>
    registered_name: []
    exception exit: {undef,
                        [{'Elixir.BadModule',does_not_exist,[],[]},
                         {'Elixir.MyApp.UsersChannel',handle_in,3,
                             [{file,"web/channels/users_channel.ex"},
                              {line,39}]},
                         {'Elixir.Phoenix.Channel.Server',
                             '-handle_info/2-fun-4-',4,
                             [{file,"lib/phoenix/channel/server.ex"},
                              {line,226}]},
                         {gen_server,try_dispatch,4,
                             [{file,"gen_server.erl"},{line,601}]},
                         {gen_server,handle_msg,5,
                             [{file,"gen_server.erl"},{line,667}]},
                         {proc_lib,init_p_do_apply,3,
                             [{file,"proc_lib.erl"},{line,247}]}]}
      in function  gen_server:terminate/7 (gen_server.erl, line 812)
    ancestors: [<0.1734.0>]
    messages: []
    links: [<0.1734.0>,<0.1583.0>]
    dictionary: []
    trap_exit: false
    status: running
    heap_size: 2586
    stack_size: 27
    reductions: 6071
  neighbours:

What version are you on?  I'm able to get notifications of exceptions within Phoenix channels, so perhaps there is a configuration issue?  Can you gist your configuration?

I'm not certain that it's the same issue, but my colleague and I were both having issues with RuntimeError reporting as well. Him in a Phoenix channel, and me in a non-phoenix mix application (not behind a plug). I found that the problem was that the logging backend is not being added :error_logger.
When I run :error_logger.add_report_handler(Sentry.Logger) in my Application.start function explicitly the reporting seems to work correctly. Could it be some kind of async race condition with Sentry.start running before Logger.start? I'm not familiar enough with the application start lifecycle to know off the top of my head. I know there were some changes in Elixir 1.4 with how application dependencies are started.
@monicao can you try that snippet and see if yours is the same problem. The code would go here:
defmodule YourApp do

  def start(_type, _args) do
    import Supervisor.Spec

    children = []
    opts = [strategy: :one_for_one, name: YouApp.Supervisor]
    Supervisor.start_link(children, opts)

    #here
    :error_logger.add_report_handler(Sentry.Logger)
  end

@mmartinson Thanks, that totally worked!
@mitchellhenke I am on version 3.0.0. Here is a link to a gist with my config and the controller code I was using to reproduce the issue. It looks like this problem was not restricted to exceptions in phoenix channels.
Let me know if I can provide any additional info.

I was able to reproduce it, but not consistently.  You can check if it's running with:
GenEvent.which_handlers(:error_logger)
# => [:error_logger, Logger.ErrorHandler, Sentry.Logger]

It seems like it might be related to using Erlang releases/distillery, but I'm not 100% sure.
If you have the time, could you run the code above and confirm that it is indeed not running?  If it's not in the handlers, could you run your application via Mix and check the handlers that way as well?
Depending on the results of the above, it may be the case that we need to move to not trying to set it up within Sentry, and just have users add the report handler within their application.
For now, I'd set use_error_logger: false, and do the add_report_handler in your application as above.


pd: switch to grpc-rs

This replace grpc-rust with grpc-rs (Written on top of shared C core library grpc/src/core).
Pending

[x] pingcap/grpc-rs#5
[x] pingcap/grpc-rs#13
[ ] pingcap/kvproto#157

PTAL @BusyJay @disksing

@disksing
Seem we can use base:grpc branch here now.

PTAL @BusyJay @disksing

LGTM.


Winograd performance optimizations for KNL/M

weight update not done yet and optimizations for forward/backward might have made weight update performance worse.

No big issue: src/libxsmm_dnn_handle.c:1342:73: error: invalid conversion from ‘int’ to ‘libxsmm_convolution_prefetch_type’.

Added another commit. Hope this fixes the compiler error.

Codecov Report

Merging #185 into master will decrease coverage by 0.08%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #185      +/-   ##
==========================================
- Coverage   12.42%   12.33%   -0.09%
==========================================
  Files         202      202
  Lines       30366    30385      +19
  Branches     5943     5944       +1
==========================================
- Hits         3772     3749      -23
- Misses      26070    26099      +29
- Partials      524      537      +13

Impacted Files
Coverage Δ

src/libxsmm_dnn_convolution_winograd_backward.c
0% <ø> (ø)
:arrow_up:

src/libxsmm_dnn_convolution_winograd_forward.c
5.71% <ø> (ø)
:arrow_up:

...rc/generator_convolution_winograd_forward_avx512.c
0% <0%> (ø)
:arrow_up:

...rad_forward_custom_custom_input_trans_alpha6.tpl.c
0% <0%> (ø)
:arrow_up:

...tion_winograd_backward_custom_custom_inlined.tpl.c
0% <0%> (ø)
:arrow_up:

...ad_forward_custom_custom_output_trans_alpha6.tpl.c
0% <0%> (ø)
:arrow_up:

...rad_forward_custom_custom_input_trans_alpha4.tpl.c
0% <0%> (ø)
:arrow_up:

...ad_backward_custom_custom_input_trans_alpha4.tpl.c
0% <0%> (ø)
:arrow_up:

samples/dnn/layer_example_f32.c
0% <0%> (ø)
:arrow_up:

src/libxsmm_dnn.c
0.29% <0%> (ø)
:arrow_up:

... and 12 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 20d993e...677fc39. Read the comment docs.

Thank you Jongsoo for your contributions (not just this one), and good luck!
( Tiny comment [of course], for future commits - perhaps use some more phantasy for your commit messages ["update xyz.c" is what we know immediately when the file is pulled with Git] ;-)


Give ksp version compatibility caps to vanguard's suite of mods

I'm so used to missing commas that my hands wouldn't let me write "underscore"


6manhua source not working properly

Source information
1.4.10
Source language
chinese
Steps to reproduce
The comic won't load properly, it shows “No pages found”, but it normal display in the webview!

Expected behavior
normal display
Actual behavior
not working properly
Mihon/Tachiyomi version
0.16.3
Android version
Android 14
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

@AlphaBoom  Can you help me see what's causing this, please?🙏

@hsiayuchih don't ping contributors to bump your issue request. Contributors volunteer their own time & willingness to look and fix any issues they see fit, and aren't required to work on any specific issues.
Wait patiently or migrate to a different source, don't beg.

@hsiayuchih don't ping contributors to bump your issue request. Contributors volunteer their own time & willingness to look and fix any issues they see fit, and aren't required to work on any specific issues.
Wait patiently or migrate to a different source, don't beg.

Okay, thanks.


Bug/compiler

targetting multiple issues and creating golden dataset

This update is to fix some issues with

stacking
cleaned up all netlists to have only four flavors [nmos, nmos_rvt, lvtpfet, lvtnfet].
All transistors need to start from M].
Added regression test for final GDS.


Pass options to Phoenix.Channel

To control websocket logging

Ahoy, is config :drab, :phoenix_channel_options, [log_handle_in: false] supposed to disable the following message? If so, I probably did something wrong in my config! If not, would be great if I could suppress this message, it's getting a bit excessive...
    You may debug Drab functions in IEx by copy/paste the following:
import Drab.{Element, Live, Query, Core}
socket = Drab.get_socket(pid("0.749.0"))

    Examples:
socket |> set_style("body", backgroundColor: "red")
socket |> poke(text: "This assign has been drabbed!")
socket |> select(:htmls, from: "h4")
socket |> exec_js("alert('hello from IEx!')")

Many thx for making Drab!

This is a Drab message, and it shows only when started with iex in developer mode. There is no way to suppress it yet, but I would accept the PR with configuration option to hide this message.


spanner: Client library sending a high rate of BeginTransaction requests when database is deleted

Once a database is deleted and if the Java Spanner client is still left open, it starts sending a large number of BeginTransaction requests. The additional requests fail with status NOT_FOUND.
The following error just keeps repeating in the logs:
Nov 07, 2019 10:20:16 PM com.google.cloud.spanner.spi.v1.LoggingInterceptor$CallLogger log FINER: google.spanner.v1.Spanner/BeginTransaction[74f0a03d]: Start
Nov 07, 2019 10:20:16 PM com.google.cloud.spanner.spi.v1.LoggingInterceptor$CallLogger log FINER: google.spanner.v1.Spanner/BeginTransaction[74f0a03d]: Send: session: "projects/<project>/instances/<instance>/databases/<database>/sessions/<session>" options { read_write { } }
Nov 07, 2019 10:20:16 PM com.google.cloud.spanner.spi.v1.LoggingInterceptor$CallLogger log FINER: google.spanner.v1.Spanner/BeginTransaction[74f0a03d]: Closed with status Status{code=NOT_FOUND, description=Database not found: projects/<project>/instances/<instance>/databases/<database> resource_type: "type.googleapis.com/google.spanner.admin.database.v1.Database" resource_name: "projects/<project>/instances/<instance>/databases/<database>" description: "Database does not exist." , cause=null} and trailers Metadata(...)

I'm guessing this is happening in an attempt to replenish the pool.

@sebright

This is caused by an infinite loop that can occur during preparing sessions in the session pool. The session pool will try to prepare a session with a read/write transaction when a session is released into the pool. This process follows this logic:

A session is released into the pool (either as part of the session pool initialization or because a session is returned to the pool by a client).
If the current fraction of write-prepared sessions in the pool is less than the configured writeFraction, a BeginTransaction RPC will be scheduled.
The BeginTransact RPC will fail with a 'Database does not exist.' error. This will cause the session to be released into the pool without a prepared read/write transaction.
The release of the session into the pool will start the process at step 1 again. As no BeginTransaction call will succeed, the process will continue until the Spanner instance is closed.

@olavloite Thanks for fixing this!  I cherry-picked https://github.com/googleapis/google-cloud-java/pull/6789/commits/7c66ee4f3caf4a854fd6c5020169dce36e8b4d74, and it seems to have fixed the issue for me.

The BeginTransact RPC will fail with a 'Database does not exist.' error. This will cause the session to be released into the pool without a prepared read/write transaction.

@skuruppu
An orthogonal question related to this:
What should the client do when a database not found error is returned ?
options:

execute backend rpcs all customer requests and return NOT_FOUND (for database admin APIs for this specific database that got deleted)
for read / write APIs - should this invalidate the session pool (since sessions are no longer valid for a deleted db) and handle all subsequent requests with NOT_FOUND errors ?

this forces the customer to create a new db client after first NOT_FOUND error even though they recreate the database with the same name (but the backend database has obviously changed).
DatabaseId db = DatabaseId.of(project, instance, database);
DatabaseClient dbClient = spanner.getDatabaseClient(db);


Fails to initialize MySQL database

Info:

Docker version ($ docker --version): 17.10.0-ce, build f4ffd25
Laradock commit ($ git rev-parse HEAD): 0077de28a13feea669f9d46ef21c20477fa6dbb0
System info (Mac, PC, Linux): Windows
System info disto/version: Windows 10 Home

Issue:

When I run docker-compose up -d mysql I'm getting error. Following is the docker logs

[Note] Basedir set to /usr/
[Warning] The syntax '--symbolic-links/-s' is deprecated and will be removed in a future release
[Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
[ERROR] --initialize specified but the data directory has files in it. Aborting.
[ERROR] Aborting

I have tried deleting mysql folder under ~/.laradock\data and didn't work.
Expected behavior:

MySQL container to run without error
Reproduce:

Run docker-compose up -d mysql

Okay, so my logs from  laradock_mysql_1 suggested I visit this link and add innodb_force_recovery = 1 to my laradock/mysql/my.cnf file, which did not work.
A blatant copy-paste of the fatal error causing the issue to begin with brought me here where I found out that it appears to be a known bug with mysql 8, which is why...

I went to my laradock/.env, put MYSQL_VERSION=5.7 (instead of formerly 8.0),
did docker-compose down (to shut down and remove the containers from docker)
deleted my <Windows User Directory>/.laradock/mysql directory completely
docker-compose up -d'd the containers as usual, rebuilding them.

A quick docker ps shows the mysql container keeps running and so I can access it from my workspace.
Hope this helps anyone!

I have the same issue too
Starting laradock_mysql_1
Attaching to laradock_mysql_1
mysql_1                | Initializing database
mysql_1                | 2018-02-19T17:48:33.012983Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysql_1                | 2018-02-19T17:48:33.013025Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
mysql_1                | 2018-02-19T17:48:33.014393Z 0 [ERROR] --initialize specified but the data directory has files in it. Aborting.
mysql_1                | 2018-02-19T17:48:33.014466Z 0 [ERROR] Aborting
mysql_1                |
laradock_mysql_1 exited with code 1

I have the same issue too
Creating laradock_mysql_1
Attaching to laradock_mysql_1
mysql_1                | Initializing database
mysql_1                | 2018-03-20T07:56:12.959088Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysql_1                | 2018-03-20T07:56:12.959158Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
mysql_1                | 2018-03-20T07:56:12.963949Z 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
mysql_1                | 2018-03-20T07:56:14.812724Z 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
mysql_1                | 2018-03-20T07:56:14.813888Z 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
mysql_1                | 2018-03-20 07:56:14 0x7f77770cf740  InnoDB: Assertion failure in thread<PHONE_NUMBER>74208 in file fil0fil.cc line 896
mysql_1                | InnoDB: Failing assertion: success
mysql_1                | InnoDB: We intentionally generate a memory trap.
mysql_1                | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
mysql_1                | InnoDB: If you get repeated assertion failures or crashes, even
mysql_1                | InnoDB: immediately after the mysqld startup, there may be
mysql_1                | InnoDB: corruption in the InnoDB tablespace. Please refer to
mysql_1                | InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
mysql_1                | InnoDB: about forcing recovery.
mysql_1                | 07:56:14 UTC - mysqld got signal 6 ;
mysql_1                | This could be because you hit a bug. It is also possible that this binary
mysql_1                | or one of the libraries it was linked against is corrupt, improperly built,
mysql_1                | or misconfigured. This error can also be caused by malfunctioning hardware.
mysql_1                | Attempting to collect some information that could help diagnose the problem.
mysql_1                | As this is a crash and something is definitely wrong, the information
mysql_1                | collection process might fail.
mysql_1                |
mysql_1                | key_buffer_size=8388608
mysql_1                | read_buffer_size=131072
mysql_1                | max_used_connections=0
mysql_1                | max_threads=151
mysql_1                | thread_count=0
mysql_1                | connection_count=0
mysql_1                | It is possible that mysqld could use up to
mysql_1                | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68193 K  bytes of memory
mysql_1                | Hope that's ok; if not, decrease some variables in the equation.
mysql_1                |
mysql_1                | Thread pointer: 0x0
mysql_1                | Attempting backtrace. You can use the following information to find out
mysql_1                | where mysqld died. If you see no messages after this, something went
mysql_1                | terribly wrong...
mysql_1                | stack_bottom = 0 thread_stack 0x40000
mysql_1                | mysqld(my_print_stacktrace+0x2c)[0x55e7ef8410dc]
mysql_1                | mysqld(handle_fatal_signal+0x479)[0x55e7ef16ddf9]
mysql_1                | /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f7776cad0c0]
mysql_1                | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f7775439fff]
mysql_1                | /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f777543b42a]
mysql_1                | mysqld(+0x61f729)[0x55e7ef144729]
mysql_1                | mysqld(+0xf9772b)[0x55e7efabc72b]
mysql_1                | mysqld(_Z40fil_open_log_and_system_tablespace_filesv+0xeb)[0x55e7efac045b]
mysql_1                | mysqld(+0xe92207)[0x55e7ef9b7207]
mysql_1                | mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2e90)[0x55e7ef9ba6c0]
mysql_1                | mysqld(+0xd62a5b)[0x55e7ef887a5b]
mysql_1                | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x55e7ef1b947f]
mysql_1                | mysqld(+0xb0d316)[0x55e7ef632316]
mysql_1                | mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x55e7ef635400]
mysql_1                | mysqld(+0x641596)[0x55e7ef166596]
mysql_1                | mysqld(_Z11mysqld_mainiPPc+0xc6b)[0x55e7ef16814b]
mysql_1                | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f77754272e1]
mysql_1                | mysqld(_start+0x2a)[0x55e7ef15e82a]
mysql_1                | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
mysql_1                | information that should help you find out what is causing the crash.
laradock_mysql_1 exited with code 2

I was having the same problem. Changing the data folder worked for me.

In my case neither downgrading the mysql to 5.7 nor changing the data folder helped.

@andrzejkupczyk I'm having the exact same issue, same error log. I am using a fresh install of laradock/docker for windows/windows10. I've been searching for answers, there is a stackoverflow with some information with others having this exact issue, but it is not answered yet.

Thanks @bdahlinger but this issue looks a bit different.

Change version of mysql from latest to 5.7 in .env file. It worked for me.

Changing version to 5.7 fixed mine too.

Changing version to 5.7 fixed me the problem too.

I've tried changing to 5.7 but I'm still having issues. I've deleted the ~./laradock/data/mysql/ directory, cleared out images, rebuilt everything. modified Dockerfile for mysql, .env  in laradock. Not sure what else I'm missing.

I have fixed it. Disable AIO
https://stackoverflow.com/questions/48239668/fails-to-initialize-mysql-database-on-windows-10

this fixed for me
docker-compose down
rm -rf ~/.laradock/data/mysql

docker-compose up -d mysql

I'm having the same problem, on windows 10. The mysql container dies on creation. I have tried both using mysql 8 and 5.7 and have the same results. Everything else is updated and unchanged, fresh laravel project and fresh laradock clone.
docker-compose up mysql
Creating network "laradock_frontend" with driver "bridge"
Creating network "laradock_backend" with driver "bridge"
Creating network "laradock_default" with the default driver
Creating laradock_mysql_1 ... done
Attaching to laradock_mysql_1
mysql_1                | 2018-11-12T07:20:04.551569Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysql_1                | 2018-11-12T07:20:04.551611Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
mysql_1                | 2018-11-12T07:20:04.551614Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
mysql_1                | 2018-11-12T07:20:04.557707Z 0 [Note] mysqld (mysqld 5.7.24) starting as process 1 ...
mysql_1                | 2018-11-12T07:20:04.568103Z 0 [Note] InnoDB: PUNCH HOLE support available
mysql_1                | 2018-11-12T07:20:04.568155Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql_1                | 2018-11-12T07:20:04.568159Z 0 [Note] InnoDB: Uses event mutexes
mysql_1                | 2018-11-12T07:20:04.568161Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
mysql_1                | 2018-11-12T07:20:04.568164Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
mysql_1                | 2018-11-12T07:20:04.568479Z 0 [Note] InnoDB: Number of pools: 1
mysql_1                | 2018-11-12T07:20:04.568611Z 0 [Note] InnoDB: Using CPU crc32 instructions
mysql_1                | 2018-11-12T07:20:04.569934Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
mysql_1                | 2018-11-12T07:20:04.576741Z 0 [Note] InnoDB: Completed initialization of buffer pool
mysql_1                | 2018-11-12T07:20:04.579797Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mysql_1                | 2018-11-12T07:20:04.617416Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
mysql_1                | 2018-11-12 07:20:04 0x7fd578427740  InnoDB: Assertion failure in thread<PHONE_NUMBER>83424 in file ut0ut.cc line 942
mysql_1                | InnoDB: We intentionally generate a memory trap.
mysql_1                | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
mysql_1                | InnoDB: If you get repeated assertion failures or crashes, even
mysql_1                | InnoDB: immediately after the mysqld startup, there may be
mysql_1                | InnoDB: corruption in the InnoDB tablespace. Please refer to
mysql_1                | InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
mysql_1                | InnoDB: about forcing recovery.
mysql_1                | 07:20:04 UTC - mysqld got signal 6 ;
mysql_1                | This could be because you hit a bug. It is also possible that this binary
mysql_1                | or one of the libraries it was linked against is corrupt, improperly built,
mysql_1                | or misconfigured. This error can also be caused by malfunctioning hardware.
mysql_1                | Attempting to collect some information that could help diagnose the problem.
mysql_1                | As this is a crash and something is definitely wrong, the information
mysql_1                | collection process might fail.
mysql_1                |
mysql_1                | key_buffer_size=8388608
mysql_1                | read_buffer_size=131072
mysql_1                | max_used_connections=0
mysql_1                | max_threads=151
mysql_1                | thread_count=0
mysql_1                | connection_count=0
mysql_1                | It is possible that mysqld could use up to
mysql_1                | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68195 K  bytes of memory
mysql_1                | Hope that's ok; if not, decrease some variables in the equation.
mysql_1                |
mysql_1                | Thread pointer: 0x0
mysql_1                | Attempting backtrace. You can use the following information to find out
mysql_1                | where mysqld died. If you see no messages after this, something went
mysql_1                | terribly wrong...
mysql_1                | stack_bottom = 0 thread_stack 0x40000
mysql_1                | mysqld(my_print_stacktrace+0x2c)[0x55e44ff43cec]
mysql_1                | mysqld(handle_fatal_signal+0x479)[0x55e44f86f829]
mysql_1                | /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7fd5780050c0]
mysql_1                | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7fd576791fff]
mysql_1                | /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fd57679342a]
mysql_1                | mysqld(+0x628dab)[0x55e44f845dab]
mysql_1                | mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x55e45011389d]
mysql_1                | mysqld(+0xfa3601)[0x55e4501c0601]
mysql_1                | mysqld(+0xfa3c38)[0x55e4501c0c38]
mysql_1                | mysqld(Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8+0x2b0)[0x55e4501c9d60]
mysql_1                | mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x55e45017ee6e]
mysql_1                | mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x55e45014e0ba]
mysql_1                | mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x55e4500f1a33]
mysql_1                | mysqld(+0x627f1f)[0x55e44f844f1f]
mysql_1                | mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x55e4500be8ed]
mysql_1                | mysqld(+0xd6dd73)[0x55e44ff8ad73]
mysql_1                | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x55e44f8ba4ef]
mysql_1                | mysqld(+0xb148e6)[0x55e44fd318e6]
mysql_1                | mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x55e44fd34ad0]
mysql_1                | mysqld(+0x64af2e)[0x55e44f867f2e]
mysql_1                | mysqld(_Z11mysqld_mainiPPc+0xc71)[0x55e44f869af1]
mysql_1                | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fd57677f2e1]
mysql_1                | mysqld(_start+0x2a)[0x55e44f8601fa]
mysql_1                | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
mysql_1                | information that should help you find out what is causing the crash.
laradock_mysql_1 exited with code 2

I've done all the suggestions about and still getting an "Exit 1" on MYSQL

rm  -rf ~/.laradock/data/mysql
docker-compose up -d mysql

because mysql version different

I have the same problem.In windows10 system.
[Warning] The syntax '--symbolic-links/-s' is deprecated and will be removed in a future release
[Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
[Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
[Warning] You need to use --log-bin to make --log-slave-updates work.
libnuma: Warning: /sys not mounted or invalid. Assuming one node: No such file or directory
mbind: Operation not permitted
[ERROR] InnoDB: Operating system error number 22 in a file operation.
[ERROR] InnoDB: Error number 22 means 'Invalid argument'
[ERROR] InnoDB: File ./ib_logfile101: 'aio write' returned OS error 122. Cannot continue operation
[ERROR] InnoDB: Cannot continue operation.

I have fixed it. Disable AIO
https://stackoverflow.com/questions/48239668/fails-to-initialize-mysql-database-on-windows-10

this fixed for me too!~
thanks @nguyencongkrb

same problem, removing data files every time isn't a solution though for me.

+1

but what if you need the data?


[BUG] Combat Tracker in combination with monks little details

Describe the bug
When you pop-out the tracker and also have it opened in the sidebar, there is a loop which flickers the trackers.
happens in combination with monks little details
What version of FoundryVTT are you using?
Version 10 Build 288
To Reproduce
Steps to reproduce the behavior:
Create Combat
Begin combat
right-click combat symbol to popout extra combat window.
enjoy the flicker
Expected behavior
No flickering?
Screenshots
https://imgur.com/a/399QIB6
Additional context
Encounter Stats handlers.OnUpdateCombat No new round  - Logger.ts 7

Thanks for the bug submission, will get on this today.
Also referenced in bug ticket #383

That should now be fixed, I can no longer replicate the issue but if you still see the issue feel free to reopen this issue and let me know :)

Works like a charm! Thanks!


Fixed required-features not working with dependencies' features.

This should fix issue #3727.
@sgrif suggested making the documentation more clear as well. Should I submit a separate pull request or add a commit for that?

r? @brson
(rust_highfive has picked a reviewer for you, use r? to override)

@jbendig awesome, thanks so much for taking a look! Fix looks great to me :)
I'm gonna r+ here, but if you want to send a PR for updated docs that'd work great!
@bors: r+

:pushpin: Commit 0002d44 has been approved by alexcrichton

:hourglass: Testing commit 0002d44 with merge 833c66e...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 833c66eb40367176866a1e76cad45a14f79ea802 to master...


(cygwin) package doesn't update installer

Cygwin upgrade need to also check and update the installer https://cygwin.com/setup-x86_64.exe to the latest version

Copy from chocolatey Disqus, 2 month ago : It seems that 'cygwinsetup.exe' is not updated when a new version is pushed. Lately, I have been forced to update my packages by downloading the setup directly, without chocolatey...
Putting the setup-x86_64.exe in the choco install directory was solve my problem temprarily.

It's been updated July 13th so i think, you can close this issue.

setup file last updated 28 June 2020

Closing, as looking at our update script the latest version of the setup file gets downloaded on each new release.
As such, I don't believe there is much for us to do.
If you disagree, please let us know and we can re-open the issue.

@AdmiringWorm: Can you please reopen this ticket. It would be easy to actually rather track the setup version as it much more relevant to chocolatey as cygwin brings its own package manager. A good solution would be adding the setup version as in the cygwin version string.


Hive monad

Adds a Hive monad with the create table operations similar to the Hdfs monad in permafrost.

This is awesome. I am a bit concerned about the amount of duplication between Hive and Hdfs. Are we going to insist on their APIs remaining the same? If so, perhaps we should encapsulate some of the shared functions into a trait.

I'm happy to leave Hdfs, Hive as is and look at making things more shared when we need to add more to the core API. It hasn't changed for a while in Permafrost I think.

My concern is that, because it doesn't change often, by the time it does change the team could have expanded, and the people doing the change might no longer have the "big picture" in their heads (whereby we expect to keep duplicated code in two entirely separate projects in sync with one another).
I know it's a real pain though. What about adding comments to Hive and Hdfs which point out the existence of the other class to anyone coming along to work with the code in the future?

I added a comment saying they are similar.

Awesome. :+1:


chore: bump docker mysql version

Update MySQL version used on docker image building process.
Fixes #3527

LGTM. Merging this as it is blocking master.


lbrycrd no longer has a "master" branch

It has a v12_master, v17_master, and v19_master. This is not playing nicely with api.js, which seems to expect a "master" branch. It should use the default branch on the repository if possible. It would be okay if it used the latest tag. It looks like it has code to get the latest tag but often falls back to tag[0], which is "master".
Duplicate of https://github.com/lbryio/lbrycrd/issues/388

@kauffj do you think you can look at this one? A few people noticed it recently.

Fixed with the reintroduction of the master branch.


JLCPCB Unavailable Part/Suggestions

LQH32CN4R7M23L Inductor is on "inventory shortage" and is currently unavailable for SMT assembly.
The MP2359 is just listed as No part selected.
I found some USB 2.0 type C connectors that can probably be used:

AFAIK the CH340G can be replaced with the pin-compatible recommended-part-class CH340C, then the external oscillator crystal and capacitors  can be removed because the CH340C has them built in.
-The switches showed up as assembly-ready.

I have no idea if these are good suggestions or not as I have zero experience in PCB design.
Thank you for making this project!

For anyone interested in solution to mentioned issues, I made a fork with slight changes that could help. You can find it here.


BethesdaSoftworks.Bethesda version <IP_ADDRESS>

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

This application has quite wrong metadata already merged into main branch. I'm thinking of deleting this one and creating a new one.

I've created a new manifest for this application

You need to edit manifests/b/BethesdaSoftworks/Bethesda to manifests/b/Bethesda/Launcher

Try closing this pr and then reopening it to restart validation.

I think this extra file is causing the issue. https://github.com/microsoft/winget-pkgs/pull/15829/files#diff-83f03399d07cfae47d3ca618c4bae70efd0a36048ce440818aa1f10d21e17e98

Change the PackageIdentifier to Bethesda.Launcher; and update the folders and the file names.

updated per ask but will not validate now

I think this extra file is causing the issue. https://github.com/microsoft/winget-pkgs/pull/15829/files#diff-83f03399d07cfae47d3ca618c4bae70efd0a36048ce440818aa1f10d21e17e98

Thats what I was thinking but will not let me delete it.


deps(client): bump to<EMAIL_ADDRESS>

Proposed Changes
This PR bumps the variable outline to include a correction in the Tooltips:

related to https://github.com/bpmn-io/variable-outline/pull/2
Checklist
To ensure you provided everything we need to look at your PR:

[x] Brief textual description of the changes present
[x] Visual demo attached
[x] Steps to try out present, i.e. using the @bpmn-io/sr tool
[ ] Related issue linked via Closes {LINK_TO_ISSUE} or Related to {LINK_TO_ISSUE}

Updated changelog via https://github.com/camunda/camunda-modeler/pull/4486/commits/686772edd6e899a0729a4c0a64e975e144f1f9ad.

Updated changelog via https://github.com/camunda/camunda-modeler/pull/4486/commits/725e549c8cfccb6249a3978aa8c461085b497c06.


chore: add VerificationResult documentation and extend CсommitmentScheme trait

Description
This PR enhances the documentation and functionality of the lib.rs file by:

Adding comprehensive documentation for the VerificationResult type, detailing its purpose, use cases, and return values.
Extending the CommitmentScheme trait for improved modularity and usability.

These changes aim to make the codebase more readable and maintainable, ensuring clear guidelines for developers working with the verification and commitment functionality.
Key Places to Review

lib.rs file:

VerificationResult type: Added detailed documentation.
CommitmentScheme trait: Review the added extensions and ensure they align with the existing framework.

Checklist

[x] Targeted PR against the correct branch (main).
[x] Linked to GitHub issue or provided an explanation of the necessity of these changes.
[ ] Wrote unit tests (N/A for documentation updates but required for new trait methods).
[ ] Updated relevant documentation in the code.
[ ] Added relevant changelog entries to CHANGELOG.md for affected crates.
[x] Re-reviewed Files changed in the GitHub PR explorer.

Notes
If further clarification or updates are needed, please feel free to comment on this PR.

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