CephFS Provisioner Input/Output Error

We are having issues with the cephfs provisioner against a few of our kube clusters:
The Provisioner runs correctly and I am able to create a PVC and mount it in my container but when i perform any operations against the mount I am presented with an I/O error.
kubectl exec -it test-pod touch /mnt/test --namespace=sre touch: cannot touch '/mnt/test': Input/output error
The behavior is visible outside the container as well, this is on a node with the cephfs pool mounted within the directories the provisioner created:
ls: cannot access /data/cephfs/volumes/kubernetes/kubernetes-dynamic-pvc-3041dba2-9415-11e7-862f-169051d230b2: Input/output error
total 0
drwxr-xr-x 1 root root 1 Sep  7 21:40 .
drwxr-xr-x 1 root root 2 Sep  7 21:40 ..
d????????? ? ?    ?    ?            ? kubernetes-dynamic-pvc-3041dba2-9415-11e7-862f-169051d230b2

[root@ceph-client001 tmysliwiec]# ls -la /data/cephfs/volumes/kubernetes/kubernetes-dynamic-pvc-3041dba2-9415-11e7-862f-169051d230b2
ls: cannot access /data/cephfs/volumes/kubernetes/kubernetes-dynamic-pvc-3041dba2-9415-11e7-862f-169051d230b2: Input/output error

I'm able to perform operations agains the cephfs everywhere else, and the cluster has been healthy and running mounts on tons of other non-kubernetes nodes. Not sure what would cause this behavior. Let me know if theres anything i can do to resolve this, thanks in advance!

I also got the same error, more details as below:
$ kubectl describe po/fs-mount-pod
...
Events:
  FirstSeen	LastSeen	Count	From			SubObjectPath	Type		Reason			Message
  ---------	--------	-----	----			-------------	--------	------			-------
  41s		41s		1	default-scheduler			Normal		Scheduled		Successfully assigned fs-mount-pod to node4
  41s		41s		1	kubelet, node4				Normal		SuccessfulMountVolume	MountVolume.SetUp succeeded for volume "default-token-txx5l"
  41s		8s		7	kubelet, node4				Warning		FailedMount		MountVolume.SetUp failed for volume "pvc-a45a87c3-95e1-11e7-b116-448a5b81d4bd" : CephFS: mount failed: mount failed: exit status 5
Mounting command: mount
Mounting arguments: <IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789:/volumes/kubernetes/kubernetes-dynamic-pvc-a468a609-95e1-11e7-a436-fa8092874d5d /var/lib/kubelet/pods/1eeb3320-95e2-11e7-b116-448a5b81d4bd/volumes/kubernetes.io~cephfs/pvc-a45a87c3-95e1-11e7-b116-448a5b81d4bd ceph [name=kubernetes-dynamic-user-a468a63c-95e1-11e7-a436-fa8092874d5d,secret=AQBZwbRZtOLULhAAiFMjKIb8Q35OlS1cpJaSrw==]
Output: mount error 5 = Input/output error

@kairen the mount completes successfully on my end, the I/O errors are when I try to read/write to the mount dir. Historically when i've seen mount error 5 with ceph it was the result of a failure to access your MDS servers. check if you can reach them from within your container.

I'm experiencing the same error as @kairen - externally from K8s I can mount all of the directory tree but not the final kubernetes-dynamic-pvc-... directory.  Ubuntu 16.04, Kernel 4.4.0

@tmysl @playworker can you mount manually the top level directory, i.e.
mount -o ceph <IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789:/volumes/ /mnt -o name=kubernetes-dynamic-user-a468a63c-95e1-11e7-a436-fa8092874d5d,secret=AQBZwbRZtOLULhAAiFMjKIb8Q35OlS1cpJaSrw==

@rootfs yes I can, same with the /volumes/kubernetes directory, it's only the final kubernetes-dynamic-pvc-... directory that I can't mount manually

@playworker there is a known limitation 3rd bullet here
I haven't tested newer kernel yet

Thanks @rootfs, I'm not particularly familiar with CephFS - what does the 3rd bullet mean?  It reads to me like it's has security implications rather than functional implications.
I guess we're talking about this limitation:  "Currently each Ceph user created by the provisioner has allow r MDS cap to permit CephFS mount."?

see "Path Restriction" here

@rootfs I'm sorry, I still don't understand why you think that each user being given the "allow r" MDS cap limitation is the cause of my issue.  The mount command has the user specified, when the provisioner created that user I assume they have been given the "allow r" capability and therefore should be able to mount the path specified?

@playworker can you post your ceph auth for user kubernetes-dynamic-user-a468a63c-95e1-11e7-a436-fa8092874d5d

My particular issue was to do with namespace support in the CephFS kernel driver, this wasn't introduced until kernel versions 4.7/4.8 (not sure exactly which), upgrading the Kubernetes workers to kernel version 4.10 has fixed the problem - thanks for your help everyone :)

Thanks Guys for all your comments - we were indeed running on centos 7/kernel 3.10.* - upon upgrading the kernel to mainline on one node and setting up a taint & toleration we were able to get the provisioner and accompanying test-pod to mount and allow us to manipulate the dir.

I tried to update my ubuntu's kernel from 4.4.0 to 4.10.0 (sudo apt install linux-image-4.10.0-28-generic) and after a reboot, the error is gone, everything's works fine from now on :)

I also encountered this problem, but I don't know how to solve this problem. Is it necessary to upgrade the ceph version to mimic? I am using "quay.io/external_storage/cephfs-provisioner:latest", I see someone modifying cephfs_provisoner.py to remove the namespace part, I don't know if it can be solved, and I don't know how to modify this image

@tmysl Hello, can you tell me the specific steps? Thank you

Upgrade the linux kernel to 4.10 and above or upgrade the ceph to mimic version

Already upgrade ceph to mimic,but no help.
ceph version
ceph version 13.2.1 (5533ecdc0fda920179d7ad84e0aa65a127b20d77) mimic (stable)
i will try upgrade the kernel to 4.10 now.

@kinzess how about the result now?

@majorinche first i upgrade my centos7 kernel from  3.10.* to 4.17.(kernel-ml-4.17.14-1.el7.elrepo.x86_64.rpm), all PGs lost.
then upgrade to 4.18.(kernel-ml-4.18.3-1.el7.elrepo.x86_64.rpm), all PGs back.
everything works fine now.

ok, i just add -disable-ceph-namespace-isolation=true in the deployment, Input/output error just gone
- args:
- '-id=cephfs-provisioner-1'
- '-disable-ceph-namespace-isolation=true'
command:
- /usr/local/bin/cephfs-provisioner

@majorinche   my 'Input/output error'  just gone, using your way. thanks you very much!!!


Adding a new node causes Spegel to malfunction

Spegel version
v0.0.14
Kubernetes distribution
k3s
Kubernetes version
v1.25.12
CNI
Multus CNI
Describe the bug
Hi, I'm a spegel newbie and I've encountered a peculiar issue. When there is only one node in the cluster, and a new node is added, the spegel on the first node stops functioning properly, and the newly added node is unable to pull images from neighboring nodes.
What's strange is that on the new node, the logs continuously report a containerd connection refusal, even when I attempt to elevate the spegel daemonset to privilege. However, this error still persists.
{"level":"info","ts":1706170489.3051467,"logger":"p2p","caller":"routing/p2p.go:73","msg":"leader is self skipping connection to bootstrap node"}
2024-01-25T16:16:49.305496660+08:00 {"level":"info","ts":1706170609.305183,"logger":"p2p","caller":"routing/p2p.go:73","msg":"leader is self skipping connection to bootstrap node"}
{"level":"info","ts":1706170729.3061342,"logger":"p2p","caller":"routing/p2p.go:73","msg":"leader is self skipping connection to bootstrap node"}
2024-01-25T16:20:49.148661980+08:00 {"level":"info","ts":1706170849.1483655,"caller":"state/state.go:42","msg":"running scheduled image state update"}
{"level":"error","ts":1706170849.1485598,"caller":"state/state.go:45","msg":"received errors when updating all images","error":"connection error: desc = \"transport: error while dialing: dial unix /run/k3s/containerd/containerd.sock: connect: connection refused\": unavailable","stacktrace":"github.com/xenitab/spegel/internal/state.Track\n\t/build/internal/state/state.go:45\nmain.registryCommand.func4\n\t/build/main.go:150\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\t/go/pkg/mod/golang.org/x/sync@v0.4.0/errgroup/errgroup.go:75"}
2024-01-25T16:20:49.305328089+08:00 {"level":"info","ts":1706170849.305113,"logger":"p2p","caller":"routing/p2p.go:73","msg":"leader is self skipping connection to bootstrap node"}
{"level":"info","ts":1706170969.3060563,"logger":"p2p","caller":"routing/p2p.go:73","msg":"leader is self skipping connection to bootstrap node"}

Currently, this issue can be avoided by restarting the spegel daemonset.

me too.The first time I installed spegel on my cluster, it worked fine, but when I add nodes, spegel affects the mirrors pulling mirrors, and the only way to fix it is to restart the daemonset. this problem affects the expansion of the cluster, and greatly affects the use of the spegel, it's very smart, and I like to use it very much, please fix this problem!

I do not understand why adding nodes is affecting the communication with the Containerd socket locally. From my perspective it just doesn't make sense. The thing is that k3s has embedded Spegel and it will be available in the next release. There were changes made in Spegel in regards to Containerd to allow Spegel to run in k3s that have not been pushed upstream yet. I think the way forward is to wait for the next release of k3s and use the embedded version instead.
https://docs.k3s.io/installation/registry-mirror?_highlight=spegel
@wenchao5211 are you also seeing these issues with k3s?

I followed this issuse, but k3s uses spegel as an experimental feature, and I don't want to use the experimental version for production!

I'm following this issuse, but I'm using spegel differently than k3s, I also don't think adding nodes affects local communication with Containerd sockets

Thx,I'll attempt to use the embedded Speigel with the new k3s setup.


Collaborative wallet

current url is not correct use this
https://help.bitcoinkeeper.app/knowledge-base/what-is-wallet/

Completed


Allow building for apple silicon

Tested on my M1 and this allowed me to finish the "First time setup" section in the readme (the godot project can run the haxe-built extension successfully)

Thanks!


Tab wrap - Allow to set a row limit

I searched for this issue and didn't see a duplicate, but apologies if I've missed it.
Request
Generally I strongly prefer the tab wrap behavior as opposed to scroll so I can more easily see which files I have open / have changes / errors / etc. However when many many tabs are open this loses you a lot of vertical real estate. Sure, I should probably just close a bunch of tabs, but it might be nice to be able to set a row limit. E.g. if Wrap Tabs is true, have a secondary setting called "Wrap Tab Row Limit" which defines how many wrapped rows are allowed before the default scrollbar behavior kicks back in. If I have it set to 3 when my open tabs exceed the available space of 3 rows it will start scrolling instead.
EDIT: I have noticed something like this happening automatically when too many tabs are open and the console / bottom panel is also open but it seems like it only kicks in when there's very little real estate to work with. Having finer control over this would be excellent.
Thanks for considering this and all of the great work on VS Code.

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Strange errors when running cifar_experiment.sh

The OS is Ubuntu 18.04. The environment is in the conda environment as indicated with all required dependencies in requirements.txt installed.
The script in the debug mode runs well. However, when I ran:
sh configs/cifar_experiment.sh

A strange error happened during the evaluation time:
Training: 100%|██████████| 800/800 [6:17:14<00:00, 28.29s/it, epoch=799, loss_avg=-.878]

Evaluating:   0%|          | 0/30 [00:00<?, ?it/s]Model saved to outputs/cifar10_experiment/simsiam-cifar10-epoch800.pth
Files already downloaded and verified

Evaluating:   0%|          | 0/30 [00:00<?, ?it/s]
Traceback (most recent call last):
  File "main.py", line 116, in <module>
    main(args=get_args())
  File "main.py", line 113, in main
    linear_eval(args, backbone)
  File "/home/yl764/SimSiam/SimSiam/linear_eval.py", line 109, in main
    feature = model(images.to(args.device))
  File "/home/yl764/miniconda3/envs/simsiam/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/yl764/miniconda3/envs/simsiam/lib/python3.8/site-packages/torchvision/models/resnet.py", line 220, in forward
    return self._forward_impl(x)
  File "/home/yl764/miniconda3/envs/simsiam/lib/python3.8/site-packages/torchvision/models/resnet.py", line 203, in _forward_impl
    x = self.conv1(x)
  File "/home/yl764/miniconda3/envs/simsiam/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/yl764/miniconda3/envs/simsiam/lib/python3.8/site-packages/torch/nn/modules/conv.py", line 423, in forward
    return self._conv_forward(input, self.weight)
  File "/home/yl764/miniconda3/envs/simsiam/lib/python3.8/site-packages/torch/nn/modules/conv.py", line 419, in _conv_forward
    return F.conv2d(input, weight, self.bias, self.stride,
RuntimeError: Input type (torch.cuda.FloatTensor) and weight type (torch.FloatTensor) should be the same

Thanks!

I merged someone's pull request for ddp and something unexpected happened ... Will fix it asap!

I think now the problem is gone!


Export Browser and other types for typescript types

Currently, typescript support is limited as no types are exported except the main Wendigo class

Consider adding some tests in typescript


Fix git squash issue in user Instruction

While going through https://github.com/opendevstack/ods-pipeline/blob/master/docs/user-installation.adoc#instructions and calling as described:
git fetch --depth=1 https://github.com/opendevstack/ods-pipeline.git $pipelineGitRef:ods-pipeline-$pipelineGitRef && \
git checkout ods-pipeline-$pipelineGitRef && \
git subtree split --squash --prefix=deploy/cd-namespace -b subtree-split-branch-$pipelineGitRef && \
git checkout - && \
git subtree add --prefix=ods-pipeline subtree-split-branch-$pipelineGitRef

I received:
The '--squash' flag does not make sense with 'git subtree split'.

After discussing this with @michaelsauter the --squash flag should rather go to git subtree add...

FYI @oalyman I believe you encountered the same issue. Seems like my Git 2.30 does not complain, but Git 2.33+ does.

@michaelsauter yes I experienced the same issue.

Seeing the same thing with git version 2.34.1 and then did git subtree split without the --squash as documented on master at the moment. Looks like this should be removed or?

Yes, should have been removed. Fixed in https://github.com/opendevstack/ods-pipeline/commit/eebb3984f607d042f1ae33e2ff438a4f11b4e187.


ROS_ERROR bug in dyn_astar.h

hi
I found there an extra "%d" in #109 in dyn_astar.h, which will cause compile error. Please fix it.
ROS_ERROR("Ran out of pool, index=%d %d %d", idx(0), idx(1));
↓
ROS_ERROR("Ran out of pool, index=%d %d", idx(0), idx(1));

I have the same problem when run catkin_make [sad]
`
[ 85%] Built target flatland_viz_autogen
In file included from /home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/include/intermediate_planner/intermediate_planner.h:6,
from /home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/src/intermediate_planner.cpp:1:
/home/dmz/arena_ws/src/arena-rosnav/utils/misc/path_search/include/path_search/dyn_astar.h: In member function ‘bool AStar::Coord2Index(const Vector2d&, Eigen::Vector2i&) const’:
/home/dmz/arena_ws/src/arena-rosnav/utils/misc/path_search/include/path_search/dyn_astar.h:109:13: warning: format ‘%d’ expects a matching ‘int’ argument [-Wformat=]
109 |   ROS_ERROR("Ran out of pool, index=%d %d %d", idx(0), idx(1));
|             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/ros/noetic/include/ros/console.h:351:165: note: in definition of macro ‘ROSCONSOLE_PRINT_AT_LOCATION_WITH_FILTER’
351 |     ::ros::console::print(filter, rosconsole_define_location__loc.logger, rosconsole_define_location__loc.level, FILE, LINE, ROSCONSOLE_FUNCTION, VA_ARGS)
|                                                                                ^~~~~~~~~~~
/opt/ros/noetic/include/ros/console.h:390:7: note: in expansion of macro ‘ROSCONSOLE_PRINT_AT_LOCATION’
390 |       ROSCONSOLE_PRINT_AT_LOCATION(VA_ARGS);
|       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/ros/noetic/include/ros/console.h:575:35: note: in expansion of macro ‘ROS_LOG_COND’
575 | #define ROS_LOG(level, name, ...) ROS_LOG_COND(true, level, name, VA_ARGS)
|                                   ^~~~~~~~~~~~
/opt/ros/noetic/include/rosconsole/macros_generated.h:214:24: note: in expansion of macro ‘ROS_LOG’
214 | #define ROS_ERROR(...) ROS_LOG(::ros::console::levels::Error, ROSCONSOLE_DEFAULT_NAME, VA_ARGS)
|                        ^~~~~~~
/home/dmz/arena_ws/src/arena-rosnav/utils/misc/path_search/include/path_search/dyn_astar.h:109:3: note: in expansion of macro ‘ROS_ERROR’
109 |   ROS_ERROR("Ran out of pool, index=%d %d %d", idx(0), idx(1));
|   ^~~~~~~~~
In file included from /home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/bspline_optimizer_astar.h:6,
from /home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/include/intermediate_planner/intermediate_planner.h:24,
from /home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/src/intermediate_planner.cpp:1:
/home/dmz/arena_ws/src/arena-rosnav/utils/misc/path_search/include/path_search/dyn_astar.h:109:44: note: format string is defined here
109 |   ROS_ERROR("Ran out of pool, index=%d %d %d", idx(0), idx(1));
|                                           ~^
|                                            |
|                                            int
In file included from /home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/include/intermediate_planner/intermediate_planner.h:25,
from /home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/src/intermediate_planner.cpp:1:
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/polynomial_traj.h: In member function ‘void PolynomialTraj::init()’:
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/polynomial_traj.h:49:23: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector::size_type’ {aka ‘long unsigned int’} [-Wsign-compare]
49 |     for (int i = 0; i < times.size(); ++i)
|                     ^~~~~~~~~~~~
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/polynomial_traj.h: In member function ‘double PolynomialTraj::getLength()’:
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/polynomial_traj.h:185:23: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector<Eigen::Matrix<double, 2, 1> >::size_type’ {aka ‘long unsigned int’} [-Wsign-compare]
185 |     for (int i = 1; i < traj_vec2d.size(); ++i)
|                     ^~~~~~~~~~~~~~~~~
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/polynomial_traj.h: In member function ‘double PolynomialTraj::getMeanVel()’:
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/polynomial_traj.h:196:12: warning: unused variable ‘mean_vel’ [-Wunused-variable]
196 |     double mean_vel = length / time_sum;
|            ^~~~~~~~
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/polynomial_traj.h:197:3: warning: no return statement in function returning non-void [-Wreturn-type]
197 |   }
|   ^
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/polynomial_traj.h: In member function ‘double PolynomialTraj::getAccCost()’:
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/polynomial_traj.h:204:23: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector::size_type’ {aka ‘long unsigned int’} [-Wsign-compare]
204 |     for (int s = 0; s < times.size(); ++s)
|                     ^~~~~~~~~~~~
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/polynomial_traj.h: In member function ‘double PolynomialTraj::getJerk()’:
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/polynomial_traj.h:219:23: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector::size_type’ {aka ‘long unsigned int’} [-Wsign-compare]
219 |     for (int s = 0; s < times.size(); ++s)
|                     ^~~~~~~~~~~~
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/polynomial_traj.h: In member function ‘void PolynomialTraj::getMeanAndMaxVel(double&, double&)’:
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/polynomial_traj.h:251:23: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector::size_type’ {aka ‘long unsigned int’} [-Wsign-compare]
251 |     for (int s = 0; s < times.size(); ++s)
|                     ^~~~~~~~~~~~
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/polynomial_traj.h: In member function ‘void PolynomialTraj::getMeanAndMaxAcc(double&, double&)’:
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/traj_planner/include/traj_planner/polynomial_traj.h:290:23: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector::size_type’ {aka ‘long unsigned int’} [-Wsign-compare]
290 |     for (int s = 0; s < times.size(); ++s)
|                     ^~~~~~~~~~~~
In file included from /home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/include/intermediate_planner/intermediate_planner.h:28,
from /home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/src/intermediate_planner.cpp:1:
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/include/intermediate_planner/plan_container_mid.hpp: In member function ‘void GlobalData::getLandmarks(std::vector<Eigen::Matrix<double, 2, 1> >&)’:
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/include/intermediate_planner/plan_container_mid.hpp:172:19: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector::size_type’ {aka ‘long unsigned int’} [-Wsign-compare]
172 |      for(int i=0;i<landmark_points.size();i++){
|                  ~^~~~~~~~~~~~~~~~~~~~~~~~
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/include/intermediate_planner/plan_container_mid.hpp: In member function ‘Eigen::Vector2d GlobalData::getLocalTarget(Eigen::Vector2d&)’:
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/include/intermediate_planner/plan_container_mid.hpp:188:27: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector::size_type’ {aka ‘long unsigned int’} [-Wsign-compare]
188 |       if(id_last_landmark>=landmark_points_.size()){
|          ~^~~~~~~~~
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/src/intermediate_planner.cpp: In member function ‘bool InterPlanner::makeGlobalPlan(plan_msgs::MakeGlobalPlan::Request&, plan_msgs::MakeGlobalPlan::Response&)’:
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/src/intermediate_planner.cpp:178:18: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector<Eigen::Matrix<double, 2, 1> >::size_type’ {aka ‘long unsigned int’} [-Wsign-compare]
178 |     for(int i=0;i<global_path.size();i++){
|                 ~^~~~~~~~~~~~~~~~~~~
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/src/intermediate_planner.cpp: In member function ‘bool InterPlanner::optimizePath(double, std::vector<Eigen::Matrix<double, 2, 1> >, std::vector<Eigen::Matrix<double, 2, 1> >, UniformBspline&, InterPlanner::OptimizerType)’:
/home/dmz/arena_ws/src/arena-rosnav/utils/ros/rosnodes/intermediate_planner/src/intermediate_planner.cpp:270:21: warning: control reaches end of non-void function [-Wreturn-type]
270 |     Eigen::MatrixXd ctrl_pts;
|                     ^~~~~~~~
[ 85%] Linking CXX executable /home/dmz/arena_ws/devel/lib/intermediate_planner/intermediate_planner
[ 85%] Built target intermediate_planner
make: *** [Makefile:141: all] Error 2
Invoking "make -j12 -l12" failed
`


Fix and extend input functionality

Bug fix: Resolved issue with additional columns

Modified default value for additional columns
Implemented proper handling of string input from users
This addresses the bug reported in issue #47

Extended input functionality:

Added Alphadia configuration

thx!


linux-firmware-rpidistro: Use bullseye branch

Switch to using bullseye release 20210315-3+rpt3
License is pointed in different location in new repo structure WHENCE
file is gone too.
Fixes
https://github.com/YoeDistro/yoe-distro/issues/617
Signed-off-by: Khem Raj<EMAIL_ADDRESS>

This works for me; thanks.


Migrate to PS 0.15.0

I have code here however I'm missing node-fetch after migrating to spago. Could you help out adding it?

can you make a PR without changing the package manager? if you make a PR with only your code changes, i will review it and update everything else


client.connect() too big crashes ESP8266

If I make the client.connect() to big with a lastwill message it crashes the ESP every time I receive a message. Any known fix?

Hi,
just to clarify, you are connecting with a last will message. Then, whenever you received a message on a subscribed topic the ESP is crashing?
Does the crash happen if you connect without the will message?
How large are the messages you're dealing with?

Dude... Thanks so much. That fixed it. I didn't know about that setting before.


OFFSET / FETCH missing from SELECT syntax

On the page that desscribes the SELECT syntax (https://docs.microsoft.com/en-us/sql/t-sql/queries/select-transact-sql?view=sql-server-ver15), the syntax for OFFSET ... FETCH is missing.
Since (I think?) SQL Server 2012, SQL Server supports the ANSI standard "OFFSET nn ROWS FETCH mm ROWS ONLY" syntax, as an alternative to the non-standard TOP clause; but only when an ORDER BY is present.
The OFFSET ... FETCH option is completely missing from this page, though.
(It is documented here, though: https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2012/ms188385(v=sql.110)?redirectedfrom=MSDN)
[Enter feedback here]

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

ID: da7ee936-5d16-3ab9-97dc-35fceb3ebe29
Version Independent ID: 9daaeef8-0dc3-e241-5b65-fbe2b217e191
Content: SELECT (Transact-SQL) - SQL Server
Content Source: docs/t-sql/queries/select-transact-sql.md
Product: sql
Technology: t-sql
GitHub Login: @VanMSFT
Microsoft Alias: vanto

@HugoKornelis -- thank you for your feedback.
@VanMSFT -- please look into this issue.

Hello @HugoKornelis - Can you please clarify? We do list the ORDER BY clauses in the ORDER BY page, which is linked from the SELECT article.

Apologies for the late reply.
The documentation on https://docs.microsoft.com/en-us/sql/t-sql/queries/select-transact-sql?view=sql-server-ver15 starts with two versions of the main syntax, One for SQL Server / SQL Azure Database; and below that a second one for Azure Synapse Analytics and Parallel Data Warehouse.
In the second overview (for Azure Synapse Analytics and Parallel Data Warehouse), all clauses including ORDER BY are merely mentioned briefly, as a clear indication that the reader should use the links to more detailed information.
In the first overview (for SQL Server and Azure SQL Database), most clauses, are listed that way ... but ORDER BY is not! In this section, ORDER BY is described as "[ ORDER BY { order_by_expression | column_position [ ASC | DESC ] }     [ ,...n ] ]", which suggests that the link to the more detailed information about ORDER BY only applies to Azure Synapse Analytics and Parallel Data Warehouse.

Hi @HugoKornelis - ORDER BY is listed in the Syntax for SQL Server and Azure SQL Database as well:

Yes, I know that ORDER BY is in there as well. I said so myself.
What is missing is the FETCH / OFFSET option. That's what I reported.

Thanks for clarifying, @HugoKornelis! I understand that this can cause confusion for some, but as you inferred, we're hoping that users will open the ORDER BY article to get more information about the syntax available. This is the way that we currently structure our articles. We do appreciate the feedback, and will look to make improvements in the future with the feedback that we receive from this wonderful community.

If you hope that users open the ORDER BY article, then perhaps you should put a reference to the ORDER BY article in that place (similar to how you do it for Azure Synapse Analytics and Parallel Data Warehouse). Simple copy/paste. Would have taken you less time than the responses you sent to me.


[WIP]add RSA keypair generation module

Fixes support getting public key from rsa private key in starlark
Description of changes in release / Impact of release:
(insert text here)
Documentation
(insert text here)
Risks of this release
Is this a breaking change?

[ ] Yes
[x] No

If you answered Yes then describe why is it so
(insert text here if applicable)
Is there a way to disable the change?

[x] Use previous release
[ ] Use a feature flag
[ ] No

Additional details go here
(insert text here if applicable)

@la-luo - 👎 , can you use the pycryptodome interfaces?

@la-luo - 👎 , can you use the pycryptodome interfaces?

Closed, because of https://github.com/verygoodsecurity/starlarky/pull/90

Closed, because of #90


Just info: Welcome back, XXX

Hi
Just a FYI: I just signed up and the I got this on the dashboard:
Welcome Back,
As it is the first time I long in it's funny to get the 'Welcome back'

I removed the intro altogether. Thanks for notifying.


bug: live editor takes too long to render

Describe the bug
A clear and concise description of what the bug is.
When initially loading the website, the editor component takes a couple of seconds to load in. Some people can completely miss this by navigating away from the page (ie: going to the docs) before this component even renders.
To Reproduce
Steps to reproduce the behavior:

Use '...' as schema
Use '...' as documents
Run the following command: gql-gen ...

Expected behavior
A clear and concise description of what you expected to happen.
<Editor /> should be rendered almost immediately to the DOM. For people with slower connections, I think it's still a good idea to throw a loading indicator into that viewport as well.
Schema/Documents
Irrelevant.
Environment:
Irrelevant.
Additional context
Along with adding a loading indicator, is it possible to add the Editor component into website/core/? This would greatly improve the perf of rendering this component as no network requests need to be made and it can just be rendered straight into the DOM.
I experimented with this already but it seems like the core/ directory is not set up to use certain features, like CSS, ESM, etc. I don't need to do a whole refactor but can I add support for CSS and anything else that comes my way that's blocking me to get a PR open for review?
Note:
This would require me to touch up on the config in Webpack, which I'm more than comfortable doing. Because it's done this way, I am thinking there may be a reason that it was done this way. Are there any special considerations that I should take into account before making any drastic changes?
If allowed, maybe I could lazyload <Editor /> and wrap things in <React.Suspense /> in order to suspend the loading indicator for those on fast connections. Something like 300ms - 500ms? This would be a nice feature but I'm more concerned with the above issues. Thanks!

Fixed in the recent refactor, we also have a package for the executor and a package for the cli. The executor is able to run without any cli deps. @ardatan also added tree shaking and bundling so it will work  WAY faster when we'll release and deploy it (about 1-2 sec to load).

Fix available in 1.0.0 👍


[bug] thread 'main' has overflowed its stack (Windows 11 Tauri v2 beta)

Describe the bug
Got thread 'main' has overflowed its stack error on Windows. (Also tried on Mac and Linux and there is no problem)
I was developing an app on Mac. When I try to migrate to Windows, I got this error.
I have seen the same error message in other github issues, but I don't think it's the same problem.
Reproduction
I made a minimum reproduction project here https://github.com/HuakunShen/tauri-win-stackoverflow
Some explanation in repo README as well.
I simply added a few official plugins, and 2 capability files.
For me the reproduction project won't run with npm run tauri dev. But if I run rust code with release mode it will run.
pnpm dev # start frontend dev server

# in another terminal
cd src-tauri
cargo run # this still gives stack overflow error
cargo run --release # this will run

If I simply remove 3 unused plugins from Cargo.toml it will run.
If I remove some capabilities it will run.
Expected behavior
It should run.
Full tauri info output
❯ npm run tauri info

><EMAIL_ADDRESS>tauri
> tauri info

[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 125.0.2535.67
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.77.2 (25ef9e3d8 2024-04-09)
    ✔ cargo: 1.77.2 (e52e36006 2024-03-26)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.9.0
    - pnpm: 9.1.2
    - yarn: 1.22.22
    - npm: 10.5.2
    - bun: 1.1.4

[-] Packages
    - tauri [RUST]: 2.0.0-beta.20
    - tauri-build [RUST]: 2.0.0-beta.16
    - wry [RUST]: 0.40.0
    - tao [RUST]: 0.28.0
    - @tauri-apps/api [NPM]: 2.0.0-beta.12
    - @tauri-apps/cli [NPM]: 2.0.0-beta.18

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite

Stack trace
❯ pnpm tauri dev

><EMAIL_ADDRESS>tauri C:\Users\shenh\Desktop\tauri-win-stackoverflow
> tauri "dev"

    Running BeforeDevCommand (`pnpm dev`)

><EMAIL_ADDRESS>dev C:\Users\shenh\Desktop\tauri-win-stackoverflow
> vite

  VITE v5.2.11  ready in 130 ms

  ➜  Local:   http://localhost:1420/
  ➜  Network: use --host to expose
    Info Watching C:\Users\shenh\Desktop\tauri-win-stackoverflow\src-tauri for changes...
   Compiling tauri-win-stackoverflow v0.0.0 (C:\Users\shenh\Desktop\tauri-win-stackoverflow\src-tauri)
error: failed to remove file `C:\Users\shenh\Desktop\tauri-win-stackoverflow\src-tauri\target\debug\tauri-win-stackoverflow.exe`

Caused by:
  Access is denied. (os error 5)
 ELIFECYCLE  Command failed with exit code<PHONE_NUMBER>.
 ELIFECYCLE  Command failed with exit code 101

Additional context

If I simply remove 3 unused plugins from Cargo.toml it will run.
If I remove some capabilities it will run.

Which plugins and which capabilities?

If I simply remove 3 unused plugins from Cargo.toml it will run.
If I remove some capabilities it will run.

Which plugins and which capabilities?

@amrbashir
It may differ on different computers. I tried on another Win11 and it can handle a few more capabilities than the first Win11 I experimented with.
For example, doing any of the following will get rid of the stackoverflow error for me, but on your computer you may or may not need to remove a few more capabilities.
1. Remove remote urls from capabilities/ext.json
    "remote": {
        "urls": [
            "http://localhost:1566/*",
            "http://localhost:*"
        ]
    },

2. Remove all fs permissions in  capabilities/ext.json
"fs:allow-exists",
"fs:allow-stat",
"fs:read-all",
"fs:allow-mkdir",
"fs:allow-app-write",
"fs:allow-app-write-recursive",
"fs:allow-appcache-write",
"fs:allow-appcache-write-recursive",
"fs:allow-appconfig-write",

3. Remove all permissions in capabilities/main.json
I have tried to remove capabilities and plugins line by line to narrow down the cause but couldn't find a specific plugin causing this. They all work by themselves, but will stackoverflow when combined.
I think this is simply because the stack is full.
I am not familiar with very low level system programming, but from what I know Windows has a default 1MB stack size, Mac and Linux have 8MB stack size. I guess this is why.
I have tried to increase stack size with env var and some other options but still couldn't get it working.
set RUSTFLAGS=-C link-args=/STACK:16777216
cargo run

I got same error, but my cause is different, if I add more than around 10 commands, it will crash but not happening on my macos and linux devices

I got same error, but my cause is different, if I add more than around 10 commands, it will crash but not happening on my macos and linux devices

It's the same for me, I app also had ~30 commands. I didn't include them in the reproduction code for simplicity.

@FabianLars Can you take a look on this? This has been blocking me for a month.

Problem solved by increasing stack size.
I tried so many config/flags. This one works.
Add to .cargo/config.toml
[target.x86_64-pc-windows-msvc]
rustflags = [
	"-C", "link-arg=/STACK:8000000"
]

# 64 bit Mingw
[target.x86_64-pc-windows-gnu]
rustflags = [
    "-C", "link-arg=-Wl,--stack,8000000"
]

Reference: https://users.rust-lang.org/t/stack-overflow-when-compiling-on-windows-10/50818/7

I hit this too, in my case I just have 3 commands and some fs permissions.
I don't think this should be closed though, it's not normal and will leave a lot of people guessing what's wrong.
Maybe Tauri could use less stack memory by allocating more on the heap (Box)?

I hit this too, in my case I just have 3 commands and some fs permissions.
I don't think this should be closed though, it's not normal and will leave a lot of people guessing what's wrong. Maybe Tauri could use less stack memory by allocating more on the heap (Box)?

Makes sense, commands and plugins which are dynamically added could easily overflow the stack as the number grows. Ideally they should be allocated on stack.
I will reopen this.

Actually it looks like boxing for plugins was already introduced a long time ago: https://github.com/tauri-apps/tauri/commit/5e05236b4987346697c7caae0567d3c50714c198#diff-38a38d97761237a269af9bb9565a4a4cb5431f7324e53acf9581c5676eee1039L1209

same issue on my PC too.
win11 latest

same issue on my PC too. win11 latest
note, this doesnt fix my issue:
[target.x86_64-pc-windows-msvc]
rustflags = [
	"-C", "link-arg=/STACK:8000000"
]

# 64 bit Mingw
[target.x86_64-pc-windows-gnu]
rustflags = [
    "-C", "link-arg=-Wl,--stack,8000000"
]

How many plugins permissions and commands doyou have? Have you tried to increase the stack size beyond 8Mb? and note that the config shouldn’t be added to Cargo.toml, but config.toml

same issue on my PC too. win11 latest
note, this doesnt fix my issue:
[target.x86_64-pc-windows-msvc]
rustflags = [
	"-C", "link-arg=/STACK:8000000"
]

# 64 bit Mingw
[target.x86_64-pc-windows-gnu]
rustflags = [
    "-C", "link-arg=-Wl,--stack,8000000"
]

How many plugins permissions and commands doyou have? Have you tried to increase the stack size beyond 8Mb? and note that the config shouldn’t be added to Cargo.toml, but config.toml

ah I see, I don't have config.toml. I have had an app in v1 and it worked perfectly I'm trying to migrate into v2 and I saw this error now.
here is my  ui\src-tauri\capabilities\migrated.json
{
  "identifier": "migrated",
  "description": "Permissions that were migrated from v1 and additional required permissions",
  "local": true,
  "windows": [
    "main"
  ],
  "permissions": [
    "core:default",
    "os:default",
    "dialog:default",
    "dialog:allow-open",
    "dialog:allow-save",
    "dialog:allow-ask",
    "dialog:allow-message",
    "fs:allow-remove",
    "fs:allow-read-dir",
    "fs:allow-read-text-file",
    "fs:allow-app-write",
    "process:default",
    "shell:default"
  ]
}

fn main
   ...
    tauri::Builder::default()
        .plugin(tauri_plugin_shell::init())
        .plugin(tauri_plugin_process::init())
        .plugin(tauri_plugin_fs::init())
        .plugin(tauri_plugin_os::init())
        .plugin(tauri_plugin_dialog::init())
        .plugin(
            tauri_plugin_log::Builder::new()
                .targets([Target::new(TargetKind::Stdout)])
                .build(),
        )

        ...

after I manually created config.toml its fixed. Thank you!! <3
but is it the most appropriate way to solve this? I will be built this app soon on windows for another users. And little bit stressed if this will crash on their pcs :(

No idea. I belive it's fine as long as there is no memory leak. But if there is memory leak it would overflow anyway no matter if stack size is increased.
It nows has the same stack size as mac and linux so I assume they should now behave similarly.

anybody needing an immediate solution without changing stack size parameters can use
let context = std::thread::spawn(|| tauri::generate_context!())
  .join()
  .expect("context thread");

tauri::Builder::default()
  // ... snip ...
  .run(context)
  // ... snip ...

This is because the default thread stack size is set to 2MiB on all platforms, or higher if the platform sets it higher themselves. The main thread does not default to this.
If you need even MORE stack space, you can use std::thread::Builder::new().stack_size(bytes).
The context creates a lot of things at runtime from items consumed during build time. So there are lots of heap structures created, many of which have their values on the stack before they are passed in. So they all get created at once. With the new ACL system moving to plugins (and therefore the build system and the context), there are many more values - blowing pass the 1MiB size with enough plugins in your dependencies.
I'm looking at ways to get around this.

instead of the workaround being adding docs on how to fix this, we could also just use an 8MiB thread under the hood for the generated context code. would be a workaround for until we simplify the ACL generated code.
literally just wrap the current codegen in
::std::thread::Builder::new()
  .stack_size(8 * 1024 * 1024)
  .spawn(|| /* ... the current codegen output ... */)
  .expect("unable to create thread with 8MiB stack")
  .join()
  .expect("the generated `Context` panicked")

thoughts? @lucasfernog

anybody needing an immediate solution without changing stack size parameters can use
let context = std::thread::spawn(|| tauri::generate_context!())
  .join()
  .expect("context thread");

tauri::Builder::default()
  // ... snip ...
  .run(context)
  // ... snip ...

This is because the default thread stack size is set to 2MiB on all platforms, or higher if the platform sets it higher themselves. The main thread does not default to this.
If you need even MORE stack space, you can use std::thread::Builder::new().stack_size(bytes).
The context creates a lot of things at runtime from items consumed during build time. So there are lots of heap structures created, many of which have their values on the stack before they are passed in. So they all get created at once. With the new ACL system moving to plugins (and therefore the build system and the context), there are many more values - blowing pass the 1MiB size with enough plugins in your dependencies.
I'm looking at ways to get around this.

May I ask you if should I have to remove this after I update the latest version of Tauri or keep using it that way still safe? What do you recommend?

I just encountered the same issue.
Setting the following env before build fixed it
$env:RUSTFLAGS = "-C link-arg=/STACK:8000000"


RequestDocuments' updated_at attribute being updated for all previous versions

NOTE: This bug has already been fixed as part of 4200
Describe the bug in current situation
Whenever a new version of a document is created, all of the previous versions have their updated_at attributes updated with the current time as well.
Link bug to the User Story
Impact of this bug
It looks like all documents of all users are being impacted.
Chance of Occurring (high/medium/low/very low)
high (100%)
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
In local development and test-marshall/dev-marshall.
Steps to Reproduce
Happens whenever a new version of a document is created. For example, when 'renaming' an uploaded attachment.
Actual/ observed behaviour/ results
Expected behaviour
The updated_at attributes for all previous versions of the document should remain unchanged.
Screenshots/ Visual Reference/ Source
Private Zenhub Image

This bug has already been fixed as part of ticket 4200

Closing with 4200


Feature request - remove or replace "vote unchanged" alert

The "vote unchanged" alert is annoying from a UX point of view, it also doesn't fit with the UI theme. If it were a custom HTML/JS box closer to the dissenter window then it would be more likely to be read, easier to interact with and fit with the dissenter theme.
Instead of this alert it makes sense to me that the upvote/downvote buttons on comments you upvote/downvote should be a different colour although I appreciate that this means sending more data to the client so not ideal.

Hi @tom-merchant thank you for the suggestion. Will be working to come to a viable solution to this issue and to put in place a method to remove votes as well.


When a version is unknown but valid, assume a recent version

This allows the completion to be useful even when it has not yet been
updated for the most recent versions of the file format.

That mirrors my thinking behind the change.
My feeling is also that until Emacs Lisp gets a real YAML parser, any semantic awareness is a hack at best and should err on the side of leniency (in salt-mode we used indentation detection which causes a lot of hard-to-debug cases, and in gitlab-ci-mode I gave up and just accepted all the keywords everywhere because resolving anchors is too much work). In the meantime, integrating docker-compose config with Flycheck is high on my priority list, though...


dep: Update containers/image to 1c202c5d85d2ee531acb1e91740144410066d19e

@nalind @runcom PTAL
Signed-off-by: Mrunal Patel<EMAIL_ADDRESS>

Cool, thanks @mrunalp

Still seeing an issue with local tests. I have opened #354 for that.

Alright, should we merge this though?

@runcom Yes, because it definitely improves over status quo.


Dev

Description

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (refactoring and improving code)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

Additional context

How has this been tested

[x] I have run bash ./tools/test (at the root of the project) locally and passed
[x] I have tested this feature in the browser

updated


Rule request: Warn whenever any default value is provided in post_init

Default values should not be given in the arguments of __post_init__.  They should only be provided as default values for class-level init-only member variables.
from dataclasses import InitVar, dataclass

@dataclass
class C:
    x: InitVar[int] = 1

    def __post_init__(self, x: int = 4) -> None:
        print(x)  # noqa: T201

c = C()  # Prints 1!  4 is ignored.

The above text could be used for the Ruff rule warning message.

Interesting, thanks for raising this rule request. This seems like a reasonable rule to implement, most likely in a RUF category. What do you think? @AlexWaygood

Although, I couldn't really find any usages of such pattern: https://grep.app/search?q=def __post_init__\(self,%5B%5E%3D%5Cn%5D+%3D&regexp=true&filter%5Blang%5D%5B0%5D=Python

I agree this is a reasonable thing to have a rule for. There's no chance of false positives, and I think I remember hitting this footgun myself at one point in a previous project. The RUF category sounds good to me.


Nested Tabs

Is it possible to nest tabs?, It's too slow before upgrade to react 0.14

Ok in issue #1993 says it is a Chrome issue, is slow, in Firefox is working fine


Add option to enable/disable Razor formatter

https://github.com/dotnet/aspnetcore/issues/14271

Closing as this is covered by https://github.com/OmniSharp/omnisharp-vscode/pull/3594


Vision AI

Compile the meter firmware according to the wiki process, and some errors occur, please tell me how to solve it, and the fomo firmware can be started normally.

Hi，Have you flash the corresponding fomo model? What error occurs when compiling the meter firm

Compile the firmware in the same way, only fomo can, and then the above problem occurs in the mete.
No problems when compiling the firmware.

Is it right for the meter to appear like this?

Digital_meter compiles model.uf2 with pfld_meter_int8.tflite, or with another model_zone?

Hi, I have fixed the problem with the meter example, please re-pull the code, thanks!

Excuse me, will the serial port output a value after the meter is detected?
Do I also use the pfld_meter_int8.tflite file for compiling the model.uf2 of the firmware digital_meter? Still need to recompile the int8 file

Yes, you need to upload both firmware and the model.
After a successful upload, the example outputs a point at the end of a pointer. You can view the trace via the web

Whether the serial port output information can see the data tracked by wbe.

It is not tracked in the current version and may be considered for inclusion in the future. You can open the serial port as well as the web app at the same time

I also found a problem, after compiling make HW=grove_vision_ai APP=fomo && make flash, Total image size= 399 KB ( 0x63f10 ), and then compiling make HW=grove_vision_ai APP=meter && make flash, why Total image size= 399 KB ( 0x63f10 ) has not changed, because the first compilation size is 438KB, which is correct.

enen, when replacing a demo, you need a make clean, this should be caused by the existing makefile mechanism, we try to fix it, before that, please run make clean first.

There is a mismatch when following the steps to use the Seeed-Studio/edgelab-model-zoo water meter model.

I probably made changes to the ldscript that caused the current issue. Let me see how to fix it.

Looking forward to your solution to the results, all models of yolov5 do not match

(meter) Coordinates cannot be identified on the web page.
Has there been any progress on the above issues?

Hi,
You can get the latest relevant firmware as well as test models at this link
https://github.com/Seeed-Studio/Seeed_Arduino_GroveAI/releases/tag/v2.0.0

download grove_ai_v02-00.uf2 then load it
convert meter_seg7.tflite to .uf2 by uf2conv.py (-t <1-4> mean user define 1 - 4) then load it
open url https://seeed-studio.github.io/edgelab-web-app/#/
choose webserial & connect

We are in the process of reorganizing the interaction protocols between the device and the web-app, and will update the example when we are done with it.

convert meter_seg7.tflite to .uf2 by uf2conv.py (-t <1-4> mean user define 1 - 4) then load it
Where is this available? I can't complete according to your steps. Has the problem mentioned before been solved?

Hi， Hi, I have converted meter_seg7 to uf2, please go to https://github.com/Seeed-Studio/Seeed_Arduino_GroveAI/releases/tag/v2.0.0 to download it. For more models go to https://github.com/Seeed-Studio/edgelab-model-zoo


Get messages sent by employee

Added: https://github.com/belatrix/BackendAllStars/commit/5ce0433c813375b2abe995c8c9d96f82f8b24bfc


[Table] add Responsive table option

Closes: #9221

@Skaronator This seems to have a problem at narrower widths:

@mbrookes Fixed. Was only in the demo though.

Then it seems like that should be the default. I can't imagine a valid use-case for having the content overflow the container.

However the existing implementation already works as expected, without the additional prop:

Thats because the Demo Frame is using overflowX: 'auto' as well. It would look pretty ugly if it wouldn't do that. The only way to counter this would be to minimize the column count.

Then it seems like that should be the default. I can't imagine a valid use-case for having the content overflow the container.

Yes it should be always responsive IMO . The weird thing is Bootstrap 4 now has responsive classes for each view breakpoint. As you can see here they now have .table-responsive{-sm|-md|-lg|-xl}.
Just checked the github repo from bootstrap and looks like @pat270 added it via https://github.com/twbs/bootstrap/pull/22804

Thats because the Demo Frame is using overflowX: 'auto'

Yes, that's what I was suggesting should be the default.

The weird thing is Bootstrap 4 now has responsive classes for each view breakpoint.

I'm not clear on what happens there when above the breakpoint size at which overflowX: 'auto' is applied. Is the content hidden? (doesn't seem useful); Does it messily overflow? (Doesn't seem useful.) Something else?
For the purpose of this PR, I'd suggest making overflowX: 'auto' the default, and drop any references to "responsive". There'll be no need for the demo either, so the PR will be a one-line change. 👍

I'm not clear on what happens there when above the breakpoint size at which overflowX: 'auto' is applied. Is the content hidden? (doesn't seem useful); Does it messily overflow? (Doesn't seem useful.) Something else?

No clue. I think it just overflow and break the whole layout. Pretty ridiculous if you ask me.
I've updated the PR. All tables are now responsive.

Mh the display: block destorys the table layout on desktop. I could fix that by wrapping around a  and do the overflow on the div but I would like to avoid that.

The current table overflows by default [...] So I requested a responsive table option

Responsive isn't really the right word for it, rather not overflowing its container. I should have looked more closely at what component the style was applied to I didn't anticipate you having to move the container into the component.
Unfortunately the current solution introduces some new issues, so while I appreciate your efforts, it may be best to leave things as they are. If you wanted to make that more explicit in the docs by mentioning that the container needs to have overflowX: 'auto' applied that mightn't be a bad thing.

Skarantor, thanks for your efforts, but I"m closing this for now.


chore: format all files (incl .nr)

Closes #2
This PR:

sets up dprint to format all files
format all files
modifies the tests workflow

renames it to main
includes a style check
removes the node install and deps install in the tests job

Thanks! This looks slick! When I have some time, I'll remove nargo altogether since we can use bb.js directly to fetch the solidity verifier, so pretty much everything can go in hardhat tasks or node scripts

Oh I didn't know about bb.js.
Do you mean in this case it is not useful to have this merkle_trees Noir package anymore?
It is basically the whole content of this repo.

@signorecello should we merge this nonetheless?

It's definitely still useful, as BB.JS is just a TS interface to Barretenberg (which is C++ compiled to WASM). It doesn't provide any Noir circuits, it doesn't understand Noir at all hehe.
As for the nargofmt command, I checked with the team and apparently it was done by a grantee some time ago, before we had impl and traits, but there's no availability from the team to open this pandora's box now. Could be tackled by another grantee I suppose!
In any case using rustfmt seems like a great workaround. Let's merge it 😈

@sripwoud @signorecello
OT: I wonder if we should use Node in this repo. Is it worth it? Or is it better a Rust env?

@sripwoud @signorecello OT: I wonder if we should use Node in this repo. Is it worth it? Or is it better a Rust env?

based on the docs, deps with noir are rather managed with git url "a la rust".
See
https://noir-lang.org/docs/noir/modules_packages_crates/dependencies/#specifying-a-dependency
So using node sounds useless to me here. Should I make this change in this PR or separately?

So using node sounds useless to me here.

I agree, removing Node means some tools will not be supported anymore tho (e.g. czg, changelogithub), but that's fine..

Should I make this change in this PR or separately?

Maybe a new PR would be better!

I agree, removing Node means some tools will not be supported anymore tho (e.g. czg, changelogithub), but that's fine..

oh right
I rather meant have packages/merkle_trees node-free. But it is already :sweat_smile:
If the node dev deps are only at the root level it is fine imo actually.
Otherwise we ll need to find an alternative to make sure all this is setup (linting commits etc...)

@sripwoud

If the node dev deps are only at the root level it is fine imo actually.

The question is, are devs who use Noir more familiar with Rust or Node?


Ramp up DKP on cloud.gov team

In order to get @commit-dkp productively contributing to the cloud.gov team, @rememberlenny should help @commit-dkp complete a prescribed set of tasks that will bring them up to speed.
Directions:
@commit-dkp and @rememberlenny: Try to go through your checklists in order.
@rememberlenny: If you can’t complete any of the items on your checklist personally, you are responsible for ensuring that an appropriate person does it.
[This includes several theme-specific checklists - you probably won't need to go through all of the theme-specific items, but you can choose items from those that seem useful.]
New Person checklist
Getting to know cloud.gov

[x] Take judicious notes on what about this onboarding process or cloud.gov is confusing or frustrating. If you notice a problem (especially with things like documentation), you are more than welcome to fix it! At the very least, please share this information with your buddy, @rememberlenny, (or someone) at some point so we can make the team/platform better. (You can also file issues and pull requests on the template for Onboarding issues.)
[x] Figure out who your onboarding buddy, @rememberlenny, is (they should reach out to you) and make sure this issue is assigned to them.
[x] Read the team onboarding document for more context about cloud.gov.
[x] Check out the cloud.gov team roster sheet to get a sense of who's working on cloud.gov and in what capacity. (Note that we work closely with the 18F Infrastructure team, but they're not considered part of the cloud.gov team.)
[x] Bookmark the pertinent links listed here.
[x] Read the "What is it?" presentation for a rundown of what cloud.gov is and does
[x] Read through the Overview section of cloud.gov for a broader understanding of cloud.gov, especially as we present it to potential customers/users.
[x] Read the January 2016 cloud.gov "Executive Business Case" document for greater context about cloud.gov's potential impact in government.
[x] Deploy a sample application to cloud.gov to get familiar with the basics of the PaaS from a user's perspective.
[x] Check out the roadmap to get a high-level view of recently-completed, in-progress, and upcoming features.
[x] Install the ZenHub browser extension to enable you to see kanban boards, hierarchical issues, and burndown charts in GitHub.
[x] Read the Delivery Process document to learn about how we work.
[x] Join the cloud.gov team Google Group, so you can participate in team-wide internal communication.
[x] Consider joining [Cloud Foundry's Slack channels] (https://slack.cloudfoundry.org/) (we sometimes talk to folks in #gov and #gov-private – you'll need a team member to invite you to the latter).
[x] Figure out what themes you're likely to work in, and complete the checklist below that relates to it.
[x] Once you've finished the remaining checklists below, make suggestions for steps that would have improved your onboarding experience as pull requests on the onboarding checklist template used to make this issue.

Required items for all team members
These items help us fulfill security and compliance requirements (including for FedRAMP). If you get stuck, or if these requirements are confusing, ask for help from your buddy, @rememberlenny, or in a cloud.gov channel.

[x] Read the 18F Security Policies and Procedures. These documents (which are mostly quite short) explain the high-level policies and procedures we must comply with while running cloud.gov.
[x] Read the Incident Response Guide.
[x] Coordinate with your onboarding buddy, @rememberlenny, to go through Incident Response Training within 60 days of joining the team (and annually after that).
[x] Read the Contingency Plan.
[x] Read the Continuous Monitoring Strategy, particularly the cloud.gov team responsibilities.
[x] Coordinate with your onboarding buddy, @rememberlenny, to go through Contingency Planning training within 10 days if you'll be taking on a significant role in our Contingency Planning processes (or annually if not).
[x] Read the Configuration Management Plan.
[x] Read our sharing secret keys policy.
[x] Review the 18F requirements for password management.
[x] Review the 18F open source policy guidance about protecting sensitive information.
[x] Coordinate with your onboarding buddy, @rememberlenny, to go through nonpublic information training within 60 days of joining the team (and annually after that).
[x] Subscribe to the cloud.gov team calendar (click the + in the bottom right) so you know when assorted team meetings are happening in the various squads.
[x] Subscribe (through the GitHub watch function) to the cg-site GitHub repository notifications.

Theme-specific items
For explanations of our theme names, see this glossary.
Atlas-specific items

[x] Bookmark the Atlas kanban board view.
[x] Join the #cloud-gov-atlas channel on Slack.
[x] Watch Build Your Own Private Cloud Foundry to learn about running Cloud Foundry.
[x] Set up Cloud Foundry locally and push an app to it.
[x] Learn about BOSH: watch this video and see our manifests (and read this for levity).
[x] Get to know how UAA is deployed/integrated.
[x] Get familiar with Terraform by going through the getting started guide.
[x] Learn about Concourse and try a tutorial.
[x] Check out our staging and production Concourse instances, and take a look at some of our pipelines.
[x] Join the cloud.gov operations notifications Google Group, so you can see alert information if PagerDuty is unavailable
[x] Join the Cloud Foundry Slack.
[x] Get familiar with our AWS setup.

Agent Q-specific items

[x] Bookmark the Agent Q kanban board view.
[x] Join the #cloud-gov-agent-q channel on Slack.
[x] Read about Cloud Foundry services from a user perspective.
[x] Read about implementing services.
[x] Take a look at our existing brokers.
[x] Learn about Concourse: check out our staging and production instances, and take a look at some of our pipelines.
[x] Join the Cloud Foundry Slack.

Navigator-specific items
[Trimmed]
If developing

[x] Set up the landing/docs page, dashboard, and cg-style locally.

For review

[x] Review the dashboard: current prod, staging, and demo.

@rememberlenny checklist

[x] Introduce yourself to the new team member and give them some of your background so they know who you are.
[x] Identify a straightforward, well-groomed story in progress that involves their skills domain, schedule a meeting with the owner for an introduction (if it's not you), and setup pairing sessions several times in the first week on the project.
[x] Identify a straightforward, well-groomed first story, ideally something they could conceivably complete in their first two/three weeks using their existing skills. Discuss the context with them, then make them the assignee for the card.
[x] Make suggestions for how the onboarding experience could have been improved as PRs on the onboarding template.

Required items for all team members
These items help us fulfill security and compliance requirements (including for FedRAMP).

[x] Make sure they're in the list of people working on the project.
[x] Add their name, whether they're Cloud Ops (Atlas/AgentQ), and the date they joined the team to the training tracker.
[x] Add them to the @cloud-gov-team in Slack’s Team Directory, which also adds them to the right channels (or ask #admins-slack if you don't have permission to do this).
[x] Add them to the recurring cloud.gov meetings that are relevant for them in the team calendar.
[x] Ask #admins-github to add them to the @18F/cloud.gov team on GitHub.
[x] Ask #cloud-gov-skyporter to add them to Zendesk, so they can see how we handle non-18F support and get visibility of technical discussions happening with outside groups.

Atlas-specific required items

[x] Help them review and understand the responsibilities of becoming a Cloud Operations team member, as listed in our SSP.
[x] Ask #admins-github to have them added to the @18F/cloud-gov-ops team on GitHub. (For contractors: Confirm they have cleared GSA security review before doing this one!)
[x] If the new person is a contractor, ask #admins-github to have them added to the @18F/cloud-gov-contractors team on GitHub.
[x] Grant them access to the following: AWS GovCloud, Nessus Manager GUI, New Relic, PagerDuty, StatusPage.
[x] Make them an admin of the platform.
[x] Take them through AWS onboarding.
[x] Give them a walkthrough of cloud.gov from an architecture and repository perspective.

Improvement point:

Get to know how UAA is deployed/integrated.
What details to go over, links to follow, etc.

Finished today.

Last thing outstanding here is for [@commit-dkp - David Kane-Parry]  to make a PR with any updates/changes/tweaks based on his experience to make onboarding better for the next person.

Done pending DKP's PR

Submitted changes to the onboarding-changes branch.


fix: styling issues

Fixes #134
Fixes #135

Waiting for quarto-dev/quarto-cli#7116 to be merged ...

/render

/render


Issue with duration

When creating a new row of the record type time entry the duration field is not updated until after saving. Therefor some value needs to be added in order for it to be possible to save. I tried to not have the duration field mandatory but still got the same error.
https://github.com/BeverCRM/PCF-EditableTable/assets/137784064/a5eb4a92-ca59-4a74-abd6-8175cb7ccc42

Pretty sure you shouldn't make duration as required field, this is the dataverse setting not the PCF control, right?

@SigridBeWa,
Time Entry duration field calculation is an out-of-the-box feature implemented by MS. Unfortunately, we don't have access to this functionality from the editable grid.
In the new editable grid version, we will enable custom JS rules. One possible solution could be to manually implement a JS rule that will calculate duration based on start and end dates on field change
We'll keep this issue open to track the progress.
Let me know if you'll have further questions.

Hi Ruben,
Thanks for your reply. Do you have any plans for when this new editable grid will be released? And is the offline capabilities included in that release?
Best regards,
Sigrid Berg Wallin
@.***
Sigrid Berg Wallin
Product Owner, Lead to Cash
Mobile: +46 761 126596
<EMAIL_ADDRESS>Contact me on Teams: @.***
Alfa Laval Technologies AB
Address - 221 00 Lund - Sweden
Visit: Rudeboksvägen 1 - Lund - Sweden
Registration number:<PHONE_NUMBER>
Tel switchboard: +46 46 36 6500
https://www.alfalaval.comhttp://www.alfalaval.com/ -<EMAIL_ADDRESS>This e-mail is intended solely for the use of the individual or entity to whom it is addressed and its content shall be regarded
as confidential unless explicitly stated otherwise. If you have received this e-mail by mistake, please notify the sender
immediately by e-mail and delete this e-mail from your system. Personal data and email will be handled in accordance with
the Alfa Laval Privacy Policyhttps://www.alfalaval.com/privacy.
Classified by Alfa Laval as: Business
From: Ruben Aghajanyan @.>
Sent: den 4 juli 2023 11:04
To: BeverCRM/PCF-EditableTable @.>
Cc: Sigrid Wallin @.>; Mention @.>
Subject: Re: [BeverCRM/PCF-EditableTable] Issue with duration (Issue #20)
CAUTION. This e-mail originated from outside of Alfa Laval. Please be mindful of attachments and links.
@SigridBeWahttps://github.com/SigridBeWa,
Time Entry duration field calculation is an out-of-the-box feature implemented by MS. Unfortunately, we don't have access to this functionality from the editable grid.
In the new editable grid version, we will enable custom JS rules. One possible solution could be to manually implement a JS rule that will calculate duration based on start and end dates on field change
We'll keep this issue open to track the progress.
Let me know if you'll have further questions.

Reply to this email directly, view it on GitHubhttps://github.com/BeverCRM/PCF-EditableTable/issues/20#issuecomment-1619844628, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BA3GWADMTEKGRDZANBCOEXTXOPMAPANCNFSM6AAAAAAZUAM6DQ.
You are receiving this because you were mentioned.Message ID: @.***>

Hi Sigrid,
The new version which will be released within the next month will support offline mode.
The premium version which will be released in the next 2-3 months will have JavaScript functions. By using that functions you can write a rule to calculate duration from the start date and end date.

@SigridBeWa,
Closing this bug as per our discussion.


[Portswigger Lab] Bug instance not recognized

Hi,
thanks for the great tool!
I was playing with this Portswigger lab https://portswigger.net/web-security/request-smuggling/lab-ofuscating-te-header and I saw that this tool is not able to identify that as vulnerable, while Burp HTTP Request Smuggling extension is successful.
Is it something related to how Portswigger lab emulates RS or there could be ways to actually improving this tool?
Thanks again!

WOAH, it's unbelievable! The fact is so unacceptable 🤣 But of course, there is maybe another fact that you may have used Smuggler the wrong way, need confirmation from @defparam, did you get the same result when testing with Portswigger lab?


Error seen on navigating to CIS Benchmark tab from top left menu after deploying CIS benchmark

On master-head- commit id: ed274984

Deploy a hosted EKS cluster

Navigate to Dashboard --> Apps --> Charts --> Deploy CIS scan benchmark app on the cluster

From the top navigation bar, select CIS Benchmarks

Click on Scan --> Create

Error seen

On a refresh of the page, error is not seen anymore

Expected:
Error should not be seen even without a refresh of the page

@mantis-toboggan-md I don't think this is anything directly with CIS but the bigger general issues with refresh that we have.

Closing in favor of the umbrella issue of change events not working reliably.


Add chapter for rate limiting Astronomy methods

I added a brief explanation and an example snippet to add DDP rate limiting for Astronomy methods.

Thanks! Merging


eslint-plugin-codegen - incompatible with eslint-plugin-markdown

When using the eslint-plugin-markdown processor all markdown linting seems to fall over.

Yes I can imagine why. Both plugins define a processor for .md files. I am not sure how this can be resolved though, if eslint scopes processors to files rather than rules - I will see if eslint-plugin-codegen can use the same processor as the other library but the general problem of competing processors for file types will probably remain unless fixed by eslint.

I am facing this issue as well. @mmkal is there any related open issue on eslint? I found https://github.com/eslint/eslint/issues/11035 but it didn't seem what we really need here. How can I help?

@papb thanks for the offer! Maybe the easiest way would be to set up a minimal repro? I’d be happy to then contribute/collaborate on a fix. eslint’s usage of dependencies are super weird so probably the surest way to figure out the fix would be to use patch-package in a reproduction repo, then we can port the fix to here. The js output is unminified so it should be doable.


Suppress "confusing plusses"

How do you suppress detection of "confusing plusses" and / or related syntax? I don't see it documented.

@lukeapage Can you please explain the status of this issue? What do the labels mean and how do they jibe with it being closed?
You can reproduce it with this script:
var a, b = 0, c = 0;
a = b + ++c;
console.log(a);

script.js: line 2, col 9, Confusing plusses.

1 error

There were a number of issues all mentioning the ability to suppress warnings in the config. I meant to close this, create a new issue to cover that and link, but I didn't, sorry!
I've created it now:
https://github.com/jshint/jshint/issues/2551

@jmm @impinball as I commented here https://github.com/jshint/jshint/issues/2551#issuecomment-121148888
it is possible to suppress individual warnings in the config using the format
    "-W007": true

@lukeapage Ok, no problem, thank you!


Support for Jekyll 4.0

I've modified the Gemfile and .gemspec to allow this to work with Jekyll 4.0. I've tested it as much as I can with a new site I'm building. On a fresh jekyll site, I had to modify _config.yml and the Gemfile to include jekyll-paginator to avoid some deprecation warnings, but other than that, it seems to work.

Hope this PR gets merged ASAP.

Thanks for going through the process of testing this out! I've tested things out on my end and I'm not getting any errors so I think we are good to go with this change. Thanks again!


queen-attack:  verify ordering of actual/expected

In the Jasmine testing framework, it is convention to:
expect(actual).fn(expected)

But some test suites have the following:
expect(expected).fn(actual)

This causes the error messages to be confusing.
Please verify the queen-attack exercise to make sure that the expectations are ordered correctly. If they are, then this can be closed.
This issue will help to close #111

Got it

This one is OK and can be closed

Awesome!


pywal16: 3.6.0 -> 3.7.2; add {manpage,optional-dependencies,updateScript}

pywal16: 3.6.0 -> 3.7.1
pywal16: add man page
pywal16: add optional-dependencies
pywal16: add updateScript
pywal16: 3.7.1 -> 3.7.2

Full Changelog: https://github.com/eylles/pywal16/compare/3.7.0...3.7.1

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 359741

x86_64-linux

:white_check_mark: 2 packages built:

pywal16
pywal16.dist

aarch64-linux

:white_check_mark: 2 packages built:

pywal16
pywal16.dist

x86_64-darwin

:white_check_mark: 2 packages built:

pywal16
pywal16.dist

aarch64-darwin

:white_check_mark: 2 packages built:

pywal16
pywal16.dist

IMO we are ready to merge now


Table: fix wrong empty block height

Please make sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's contributing guide (中文 | English | Español | Français).
[ ] Make sure you are merging your commits to dev branch.
[ ] Add some descriptions and refer relative issues for you PR.

Closes #16581

现在的情况是 tag 出现时也有动画，之前是新添加的 tag 才有动画。


Fix misspelling in Flagger hero content - canaray

See here misspelling error for canary.
incorrect: canaray
correct: canary

Thanks for letting us know, @russomi!


[Perf] Lighthouse Scores

Seems like a few low-hanging fruits, I see a ticket https://github.com/ipfs/ipfs-website/issues/255, not sure if it's regarding the same.

Thanks for flagging. Bigger perf items are still in the backlog as there are some blocking issues we need to solve in order to get the asset resizing to play nice with IPFS hosting and static generation (once Nuxt Image v2 is out of RC). Hopefully soon tho 🤞

A few other optimizations still to land in the v3 launch list #272


[Bug] [Connector-V2][Postgres-CDC] Scanning unwanted database and tables which are not mentioned in Source

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
When we provide a hostname for Postgres-CDC connection and try to run the job we are seeing unwanted WARN logs which says TableDiscoveryUtils class is trying to scan for all the databases under the specified host. Even though we specify the database name in the source config we are still getting these unwanted warnings. Is there any way to avoid other databases and tables which are not part of the connection ?
SeaTunnel Version
seatunnel-2.3.8
SeaTunnel Config
env {
  execution.parallelism = 1
  job.mode = "STREAMING"
  checkpoint.interval = 5000
  read_limit.bytes_per_second=7000000
  read_limit.rows_per_second=400
}

source {

  Postgres-CDC {
    result_table_name = "employees"
    username = "postgres"
    password = "password"
    database-names = ["postgres"]
    schema-names = ["public"]
	slot.name = "employeeslot"
    table-names = ["postgres.public.employees"]
    base-url = "jdbc:postgresql://localhost:5432/postgres"
  }

}

transform {
}

sink {

	Console {
      source_table_name = "employees"
  }

}

Running Command
./bin/seatunnel.sh --config config/postgres-cdc.template --async -n postgrescdcsync

Error Exception
[915470173375299585] 2024-11-30 23:11:41,544 INFO  [.c.s.c.p.u.TableDiscoveryUtils] [hz.main.seaTunnel.task.thread-128] -                                                                              list of available databases is: [postgres, database2, database3]
[915470173375299585] 2024-11-30 23:11:41,544 INFO  [.c.s.c.p.u.TableDiscoveryUtils] [hz.main.seaTunnel.task.thread-128] - Read list of available tables in each database
[915470173375299585] 2024-11-30 23:11:41,606 WARN  [.c.s.c.p.u.TableDiscoveryUtils] [hz.main.seaTunnel.task.thread-128] -                                                                              skipping database 'database2' due to error reading tables: ERROR: cross-database references are not implemented: "database2.information_schema.tables"
  Position: 15
[915470173375299585] 2024-11-30 23:11:41,657 WARN  [.c.s.c.p.u.TableDiscoveryUtils] [hz.main.seaTunnel.task.thread-128] -                                                                              skipping database 'database3' due to error reading tables: ERROR: cross-database references are not implemented: "database3.information_schema.tables"
  Position: 15

Zeta or Flink or Spark Version
No response
Java or Scala Version
Jdk 1.8
Screenshots
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@hailin0 I'd like to fix it, please assign it to me, thx.


Generator without Repository

Is it possible to not use Repositories?

@twelvester Its not possible in direct way. But what you can do is, you can publish templates and then modify controller to your own way to make it work without repository.


Annotations conflict

DBFlow Version:
4.0.0-beta7
Description:
@ table annotation in conflict, could you tell me how to solve?

Im sorry I do not understand the issue. I need more info.

I use the entity class @Database (name = DBFlowDatabase.NAME, version = DBFlowDatabase.VERSION), the compiler wrong, suggesting that the error message is a conflict, and I should use the Notes of the DataBinding conflict! Now did not find a solution, please help you ok?

im sorry I don't understand.
First, "entity" should use @Table annotation, not @Database
Second, you should paste a screenshot of the compiler error here.
Third, "I should use the Notes of the DataBinding conflict!" If it's a DatabindingIssue, this is not a DBFlow issue.

Ok! thank you for your help! I am from China's Andrews developers, poor English ability to express!

No worries. Screenshots and error messages can help a lot.

Listen to your tips using @Table annotations have been resolved. Thank you！


Intermittent Error 8: Operation Not Permitted

With iPhone 7 we see only one error in over 40 upgrades. With iPhone XR the first upgrade after power-up works but all subsequent upgrades fail until we power cycle the target device.  The ZIP package contains the application and settings only.  ZIP package is 44KB is size.  The error usually happens near the start but sometimes happens after several packets are transferred.  The DFU secure_bootloader comes from SDK 15.2 and we use SoftDevice 6.1.1.  Target device is 52840.  We do NOT use bonding.  See the log output below.  I plan to increate the log verbosity and do another capture soon.  Any ideas how to debug this?
2019-07-02 08:50:59.400 > DFU state: Connecting
2019-07-02 08:51:00.831 > DFU state: Starting
2019-07-02 08:51:01.012 > DFU:Buttonless DFU indications enabled
2019-07-02 08:51:01.012 > DFU:Application with buttonless update found
2019-07-02 08:51:01.013 > DFU state: Enabling DFU Mode
2019-07-02 08:51:01.072 > DFU:Response (Op Code = 2, Status = 1) received
2019-07-02 08:51:01.072 > DFU:Bootloader name changed successfully
2019-07-02 08:51:01.101 > DFU:Response (Op Code = 1, Status = 1) received
2019-07-02 08:51:04.943 > DFU state: Starting
2019-07-02 08:51:04.971 > DFU:Secure DFU Control Point notifications enabled
2019-07-02 08:51:05.002 > DFU:Command object info (Max size = 256, Offset = 0, CRC = 00000000) received
2019-07-02 08:51:05.064 > DFU:Packet Receipt Notif disabled (Op Code = 2, Value = 0)
2019-07-02 08:51:05.065 > DFU:Command object sent (CRC = 2AF5FA37)
2019-07-02 08:51:05.092 > DFU:Checksum (Offset = 141, CRC = 2AF5FA37) received
2019-07-02 08:51:05.137 > DFU:Command object executed
2019-07-02 08:51:05.166 > DFU:Packet Receipt Notif enabled (Op Code = 2, Value = 12)
2019-07-02 08:51:05.287 > DFU:Data object info (Max size = 4096, Offset = 0, CRC = 00000000) received
2019-07-02 08:51:05.287 > DFU state: Uploading
2019-07-02 08:51:05.317 > DFU:Uploading firmware...
2019-07-02 08:51:05.513 > DFU:Checksum (Offset = 3660, CRC = 91858F4F) received
2019-07-02 08:51:05.631 > DFU:Error 8: Operation not permitted
2019-07-02 08:51:05.632 > DFU:Data object executed
2019-07-02 08:51:05.663 > DFU:Uploading firmware...
2019-07-02 08:51:05.730 > DFU error: DFUError 7024 bytes were sent while 0 bytes were reported as received

Below is the DFU log output with full verbosity.
2019-07-02 11:41:20.137 > DFU state: Connecting
2019-07-02 11:41:20.137 > DFU:[Callback] Central Manager did update state to: Powered ON
2019-07-02 11:41:20.137 > DFU:Connecting to MI.Tracer.Angle...
2019-07-02 11:41:20.137 > DFU:centralManager.connect(peripheral, options: nil)
2019-07-02 11:41:20.924 > DFU:[Callback] Central Manager did connect peripheral
2019-07-02 11:41:20.925 > DFU:Connected to MI.Tracer.Angle
2019-07-02 11:41:20.925 > DFU:Discovering services...
2019-07-02 11:41:20.925 > DFU:peripheral.discoverServices(nil)
2019-07-02 11:41:21.282 > DFU:Services discovered
2019-07-02 11:41:21.283 > DFU:Starting Secure DFU...
2019-07-02 11:41:21.283 > DFU:Connected to MI.Tracer.Angle
2019-07-02 11:41:21.283 > DFU:Services discovered
2019-07-02 11:41:21.283 > DFU:Secure DFU Service found
2019-07-02 11:41:21.283 > DFU:Discovering characteristics in DFU Service...
2019-07-02 11:41:21.284 > DFU:peripheral.discoverCharacteristics(nil, for: FE59)
2019-07-02 11:41:21.341 > DFU:DFU characteristics discovered
2019-07-02 11:41:21.341 > DFU state: Starting
2019-07-02 11:41:21.342 > DFU:Enabling indications for 8EC90003-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:21.342 > DFU:peripheral.setNotifyValue(true, for: 8EC90003-F315-4F60-9FB8-838830DAEA50)
2019-07-02 11:41:21.521 > DFU:Indications enabled for 8EC90003-F315-4F60-9FB8-838830DAEA50
2019-07-02 11:41:21.522 > DFU:Buttonless DFU indications enabled
2019-07-02 11:41:21.522 > DFU:Application with buttonless update found
2019-07-02 11:41:21.522 > DFU state: Enabling DFU Mode
2019-07-02 11:41:21.522 > DFU:Trying setting bootloader name to Dfu46387
2019-07-02 11:41:21.522 > DFU:Writing to characteristic 8EC90003-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:21.523 > DFU:peripheral.writeValue(0x02084466753436333837, for: 8EC90003-F315-4F60-9FB8-838830DAEA50, type: .withResponse)
2019-07-02 11:41:21.581 > DFU:Data written to 8EC90003-F315-4F60-9FB8-838830DAEA50
2019-07-02 11:41:21.582 > DFU:Indication received from 8EC90003-F315-4F60-9FB8-838830DAEA50, value (0x):200201
2019-07-02 11:41:21.582 > DFU:Response (Op Code = 2, Status = 1) received
2019-07-02 11:41:21.582 > DFU:Bootloader name changed successfully
2019-07-02 11:41:21.583 > DFU:Writing to characteristic 8EC90003-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:21.583 > DFU:peripheral.writeValue(0x01, for: 8EC90003-F315-4F60-9FB8-838830DAEA50, type: .withResponse)
2019-07-02 11:41:21.611 > DFU:Data written to 8EC90003-F315-4F60-9FB8-838830DAEA50
2019-07-02 11:41:21.611 > DFU:Indication received from 8EC90003-F315-4F60-9FB8-838830DAEA50, value (0x):200101
2019-07-02 11:41:21.612 > DFU:Response (Op Code = 1, Status = 1) received
2019-07-02 11:41:24.629 > DFU:[Callback] Central Manager did disconnect peripheral
2019-07-02 11:41:24.629 > DFU:Disconnected by the remote device
2019-07-02 11:41:24.629 > DFU:Scanning for the DFU Bootloader...
2019-07-02 11:41:24.672 > DFU:DFU Bootloader found with name Dfu46387
2019-07-02 11:41:24.673 > DFU:Connecting to Dfu39785...
2019-07-02 11:41:24.673 > DFU:centralManager.connect(peripheral, options: nil)
2019-07-02 11:41:25.414 > DFU:[Callback] Central Manager did connect peripheral
2019-07-02 11:41:25.414 > DFU:Connected to Dfu39785
2019-07-02 11:41:25.414 > DFU:Discovering services...
2019-07-02 11:41:25.415 > DFU:peripheral.discoverServices([FE59])
2019-07-02 11:41:25.473 > DFU:Services discovered
2019-07-02 11:41:25.473 > DFU:Secure DFU Service found
2019-07-02 11:41:25.474 > DFU:Discovering characteristics in DFU Service...
2019-07-02 11:41:25.474 > DFU:peripheral.discoverCharacteristics(nil, for: FE59)
2019-07-02 11:41:25.475 > DFU:DFU characteristics discovered
2019-07-02 11:41:25.475 > DFU:MTU set to 247
2019-07-02 11:41:25.475 > DFU state: Starting
2019-07-02 11:41:25.476 > DFU:Enabling notifications for 8EC90001-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:25.476 > DFU:peripheral.setNotifyValue(true, for: 8EC90001-F315-4F60-9FB8-838830DAEA50)
2019-07-02 11:41:25.502 > DFU:Notifications enabled for 8EC90001-F315-4F60-9FB8-838830DAEA50
2019-07-02 11:41:25.502 > DFU:Secure DFU Control Point notifications enabled
2019-07-02 11:41:25.502 > DFU:Writing to characteristic 8EC90001-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:25.502 > DFU:peripheral.writeValue(0x0601, for: 8EC90001-F315-4F60-9FB8-838830DAEA50, type: .withResponse)
2019-07-02 11:41:25.531 > DFU:Data written to 8EC90001-F315-4F60-9FB8-838830DAEA50
2019-07-02 11:41:25.532 > DFU:Notification received from 8EC90001-F315-4F60-9FB8-838830DAEA50, value (0x):<PHONE_NUMBER>00000000000000000000
2019-07-02 11:41:25.532 > DFU:Command object info (Max size = 256, Offset = 0, CRC = 00000000) received
2019-07-02 11:41:25.532 > DFU:Writing to characteristic 8EC90001-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:25.532 > DFU:peripheral.writeValue(0x01018d000000, for: 8EC90001-F315-4F60-9FB8-838830DAEA50, type: .withResponse)
2019-07-02 11:41:25.561 > DFU:Data written to 8EC90001-F315-4F60-9FB8-838830DAEA50
2019-07-02 11:41:25.562 > DFU:Notification received from 8EC90001-F315-4F60-9FB8-838830DAEA50, value (0x): 600101
2019-07-02 11:41:25.562 > DFU:Writing to characteristic 8EC90001-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:25.563 > DFU:peripheral.writeValue(0x020000, for: 8EC90001-F315-4F60-9FB8-838830DAEA50, type: .withResponse)
2019-07-02 11:41:25.592 > DFU:Data written to 8EC90001-F315-4F60-9FB8-838830DAEA50
2019-07-02 11:41:25.596 > DFU:Notification received from 8EC90001-F315-4F60-9FB8-838830DAEA50, value (0x): 600201
2019-07-02 11:41:25.596 > DFU:Packet Receipt Notif disabled (Op Code = 2, Value = 0)
2019-07-02 11:41:25.596 > DFU:Writing to characteristic 8EC90002-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:25.596 > DFU:peripheral.writeValue(0x128a010a4408011240080110341a02b60120002800300038d8d102422408031220cae77b7ffde7b4b46f94893675c7d40d6896a090532c8102972352575dcb7f00480052040801120010001a400996aecabe257d862fe6d58d23531b2937e3298f32ebad11ffe76eab0118ec835e0ccaf90bdda90f710346dc487a855ee392929fcbd9e4b72be79c4c35f80a6b, for: 8EC90002-F315-4F60-9FB8-838830DAEA50, type: .withoutResponse)
2019-07-02 11:41:25.596 > DFU:Command object sent (CRC = 1D99468E)
2019-07-02 11:41:25.597 > DFU:Writing to characteristic 8EC90001-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:25.597 > DFU:peripheral.writeValue(0x03, for: 8EC90001-F315-4F60-9FB8-838830DAEA50, type: .withResponse)
2019-07-02 11:41:25.622 > DFU:Data written to 8EC90001-F315-4F60-9FB8-838830DAEA50
2019-07-02 11:41:25.623 > DFU:Notification received from 8EC90001-F315-4F60-9FB8-838830DAEA50, value (0x): 6003018d0000008e46991d
2019-07-02 11:41:25.624 > DFU:Checksum (Offset = 141, CRC = 1D99468E) received
2019-07-02 11:41:25.624 > DFU:Writing to characteristic 8EC90001-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:25.624 > DFU:peripheral.writeValue(0x04, for: 8EC90001-F315-4F60-9FB8-838830DAEA50, type: .withResponse)
2019-07-02 11:41:25.653 > DFU:Data written to 8EC90001-F315-4F60-9FB8-838830DAEA50
2019-07-02 11:41:25.667 > DFU:Notification received from 8EC90001-F315-4F60-9FB8-838830DAEA50, value (0x): 600401
2019-07-02 11:41:25.668 > DFU:Command object executed
2019-07-02 11:41:25.668 > DFU:Writing to characteristic 8EC90001-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:25.668 > DFU:peripheral.writeValue(0x020c00, for: 8EC90001-F315-4F60-9FB8-838830DAEA50, type: .withResponse)
2019-07-02 11:41:25.697 > DFU:Data written to 8EC90001-F315-4F60-9FB8-838830DAEA50
2019-07-02 11:41:25.698 > DFU:Notification received from 8EC90001-F315-4F60-9FB8-838830DAEA50, value (0x): 600201
2019-07-02 11:41:25.698 > DFU:Packet Receipt Notif enabled (Op Code = 2, Value = 12)
2019-07-02 11:41:25.698 > DFU:Writing to characteristic 8EC90001-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:25.698 > DFU:peripheral.writeValue(0x0602, for: 8EC90001-F315-4F60-9FB8-838830DAEA50, type: .withResponse)
2019-07-02 11:41:25.817 > DFU:Data written to 8EC90001-F315-4F60-9FB8-838830DAEA50
2019-07-02 11:41:25.818 > DFU:Notification received from 8EC90001-F315-4F60-9FB8-838830DAEA50, value (0x):<PHONE_NUMBER>00000000000000000000
2019-07-02 11:41:25.819 > DFU:Data object info (Max size = 4096, Offset = 0, CRC = 00000000) received
2019-07-02 11:41:25.819 > DFU state: Uploading
2019-07-02 11:41:25.819 > DFU:Writing to characteristic 8EC90001-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:25.819 > DFU:peripheral.writeValue(0x010200100000, for: 8EC90001-F315-4F60-9FB8-838830DAEA50, type: .withResponse)
2019-07-02 11:41:25.847 > DFU:Data written to 8EC90001-F315-4F60-9FB8-838830DAEA50
2019-07-02 11:41:25.849 > DFU:Notification received from 8EC90001-F315-4F60-9FB8-838830DAEA50, value (0x): 600101
2019-07-02 11:41:25.849 > DFU:Data object 1/11 created
2019-07-02 11:41:25.849 > DFU:Uploading firmware...
2019-07-02 11:41:25.849 > DFU:Sending firmware to DFU Packet characteristic...
2019-07-02 11:41:25.998 > DFU:Writing to characteristic 8EC90001-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:25.999 > DFU:peripheral.writeValue(0x03, for: 8EC90001-F315-4F60-9FB8-838830DAEA50, type: .withResponse)
2019-07-02 11:41:26.042 > DFU:Data written to 8EC90001-F315-4F60-9FB8-838830DAEA50
2019-07-02 11:41:26.044 > DFU:Notification received from 8EC90001-F315-4F60-9FB8-838830DAEA50, value (0x): 6003014c0e00004f8f8591
2019-07-02 11:41:26.044 > DFU:Checksum (Offset = 3660, CRC = 91858F4F) received
2019-07-02 11:41:26.044 > DFU:Writing to characteristic 8EC90001-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:26.044 > DFU:peripheral.writeValue(0x04, for: 8EC90001-F315-4F60-9FB8-838830DAEA50, type: .withResponse)
2019-07-02 11:41:26.161 > DFU:Data written to 8EC90001-F315-4F60-9FB8-838830DAEA50
2019-07-02 11:41:26.163 > DFU:Notification received from 8EC90001-F315-4F60-9FB8-838830DAEA50, value (0x): 600408
2019-07-02 11:41:26.163 > DFU:Error 8: Operation not permitted    <====== FIRST ERROR HERE
2019-07-02 11:41:26.163 > DFU:Data object executed
2019-07-02 11:41:26.163 > DFU:Writing to characteristic 8EC90001-F315-4F60-9FB8-838830DAEA50...
2019-07-02 11:41:26.163 > DFU:peripheral.writeValue(0x010200100000, for: 8EC90001-F315-4F60-9FB8-838830DAEA50, type: .withResponse)
2019-07-02 11:41:26.192 > DFU:Data written to 8EC90001-F315-4F60-9FB8-838830DAEA50
2019-07-02 11:41:26.194 > DFU:Notification received from 8EC90001-F315-4F60-9FB8-838830DAEA50, value (0x): 600101
2019-07-02 11:41:26.194 > DFU:Data object 2/11 created
2019-07-02 11:41:26.195 > DFU:Uploading firmware...
2019-07-02 11:41:26.195 > DFU:Sending firmware to DFU Packet characteristic...
2019-07-02 11:41:26.252 > DFU:Disconnecting...
2019-07-02 11:41:26.253 > DFU:centralManager.cancelPeripheralConnection(peripheral)
2019-07-02 11:41:26.253 > DFU:[Callback] Central Manager did disconnect peripheral
2019-07-02 11:41:26.254 > DFU:Disconnected
2019-07-02 11:41:26.254 > DFU error: DFUError 7024 bytes were sent while 0 bytes were reported as received

Hi, which version of the library are you using?
Some things are very wrong here:

The Data object 1/11 should have 4096 bytes, and this is how many are sent. But only 3660 were received. This is the main issue, that is caused by too fast upload from the iPhone XR, that is not handled by the Dfu targ. You need to decrease the packetReceiptNotifications in DfuServiceInitiator to a small number, like 1-10 and try which is working for you.
Except from that, if the reported number of bytes is less than the object size  (3660 < 4096), the lib should try to resend the missing data if the CRC is valid, send the object again, or abort the DFU in worst case, But in your case it just continues to send 0x04 (Execute command), which should cause Operation not permitted, as it does.
After receiving this error, the process should abort, but in your case it just prints that Data object was executed, which is a lie, and continues sending object 2/11. This is very wrong.

Did you modify the library in any way?

Also, check out #308.

Hi, yes I agree the log seems strange. For example it seems like it tried to begin packet 2/11 before 1/11 was finished? I am using iOSDFUlibrary 4.4.1 unmodified. Here is the code:
            if let newImage = tracer.desiredFirmware, let selectedFirmware = DFUFirmware(urlToZipFile: newImage)              {                 // https://github.com/NordicSemiconductor/IOS-Pods-DFU-Library/blob/master/documentation.md                 let initiator = DFUServiceInitiator(queue: nil).with(firmware: selectedFirmware)                 initiator.logger = self; // - to get log info                 initiator.delegate = self; // - to be informed about current state and errors                 initiator.progressDelegate = self; // - to show progress bar                 nordicDFU = initiator.start(targetWithIdentifier: tracer.uuid)                 if (nordicDFU == nil) {                     commonAlert?.dismiss(animated: true, completion: { doAlert(vc: self, title: "Alert", message: "DFU failed to start")})                 }             }
Issue #308 does look similar. I will try setting packetReceiptNotifications to small number and test again.
Issue is also logged on DevZone:  https://devzone.nordicsemi.com/f/nordic-q-a/49260/dfu-fails-intermittently-with-error-8-operation-not-permitted

Just added this comment to DevZone:
@phillips77 suggested to set packetReceiptNotifications to a small number so tested on iPhoneXR with setting == 1 and now we get 6 straight upgrades passed which never happened before.  This implies the bootloader cannot handle the speed of the XR or there is some kind of flow control issues in the protocol.  However, the curious thing is the 1st upgrade after a power cycle always works and the 2nd upgrade almost always fails. This implies something is not getting set (or reset) in the bootloader when we trigger the upgrade.  The device gets into a state where a power cycle is required.

Clearly it's an issue with the dfu bootloader. I'll close the issue here and let's follow the DevZone case.


Modify updateTask Mutation to include 'subtasks' Property

This enhancement is needed to enable create suggested subtasks in plexo-platform. An alternative solution is to implement a createMultipleTasks mutation.

Close with<PHONE_NUMBER>af9bbc2e10e15ac052d3be50f4d430


fix #2712 support json with comment and #2713 to fail deployment if f…

…ail sync trigger

Discussed with @EricSten-MSFT that the MSDeploy's NewtonSoft.Json.dll needs to assembly binding accordingly.   At this moment, we (Kudu and MSDeploy siteextension) use the same NewtonSoft.Json.dll version <IP_ADDRESS>.


Error: Extension exceeds max size

Hi
Got this error when building / uploading the extension:

The extension has been uploaded and I can assign it to a field, but the sourced .js file is empty hence no input / ui is rendered for the field.

Thank you for your report.
I have reproduced the problem and will try to fix it soon.

Fixed in #194! Try pulling the master branch and redeploying it.

3.5x reduction! Awesome, thank you so much both for the extension and support.


doc: Documentation suggestions

Getting started Configure
npx msw init [PUBLIC_DIR]

Hi, @hehehai. Thanks for the suggestion, I love it. I haven't figured out how to make GitBook projects publicly editable, so I will update the Getting started step manually for now.

Updated! Getting started page uses npx msw init as the initialization command. Thank you once more.