https://swap.katla.taiko.xyz/#/swap    Bug Report

Describe the bug
Error Details:
How It Occurs Step by Step:
[Connect Taiko Katla]
[signed]
[Taiko Katla to Seoılia]
Expected Behavior:
[Performing transactions on the Taiko Katla network.]
Received Error Message:
[It is consistently attempting to transition from the Taiko Katla network to the Sepolia network. Even when confirmed, it still tries to move from the Sepolia network to the Taiko Katla network. The operation is not stable.]
What steps can I take to resolve this issue, or what additional information do you need from me to address it?
taiko swap.pdf
Steps to reproduce
Steps to reproduce here.
Spam policy

[X] I verify that this issue is NOT SPAM and understand SPAM issues will be closed and reported to GitHub, resulting in ACCOUNT TERMINATION.

We do not support sepolia but holesky. That's why.


Lambda improvements

Fixes #1338
Completely revamped how lambdas are stored, now we have lambda publishing working and aliasing should be trivial to add, attempted to spam weakref everywhere but I have a feeling my debugger was messing with the refs so theres more boilerplate code that I would of expected.
Done the majority of this whilst sleep deprived, @JackDanger keep an eye out for the spelling mistakes ;-).
Also cleaned up the responses.py, made use of a json property and backend property, I think I inadvertently fixed some region malarkey when in server mode too.

Coverage decreased (-0.06%) to 92.163% when pulling e1a3676859a9bc7995036e21896b491a12900ec7 on terrycain:lambda_improvements into cdb7305dac6f9089236539133f6c8eab1ec9dd55 on spulec:master.

Coverage decreased (-0.1%) to 92.091% when pulling a94cfd272d4b12cb817122220e505bb8b0123330 on terrycain:lambda_improvements into cdb7305dac6f9089236539133f6c8eab1ec9dd55 on spulec:master.

Coverage decreased (-0.1%) to 92.091% when pulling a94cfd272d4b12cb817122220e505bb8b0123330 on terrycain:lambda_improvements into cdb7305dac6f9089236539133f6c8eab1ec9dd55 on spulec:master.


Message abstract class

Hi,
In the readme looks like you are intending to remove the need of inheritance of message abstract class. Are you doing this in the new version?
Thank you for all your awesome work in this tool.

I'm not sure why "(currently)" is in the README, but my understanding is that there's no active work to remove this happening at the moment. If it does change it's probably not going to be until after version 7 (which we don't have a concrete date to ship at this time).


Fix Slack connector message recipient

Proposed changes:

#371
Use the slack_channel kwarg of the SlackClient to choose whether to send messages back to the user or to a static channel

Status (please check what you already did):

[x] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog

pls add to changelog


Key Findings Killings by Police Text Issue

Overview:
If both Black and Latinx numbers are 0x as likely then it should just say [x] people killed by [department name] from 2013-19
Details:

Info about the Environment:

URL: https://staging.policescorecard.org/ny/police-department/greece-town

Acceptance Criteria:

Issue will be considered complete when the following criteria are met:

[x] If black and latinx are both 0x as likely in the description, switch the text to the following:
[x] X here is the number shown next to KILLINGS BY POLICE
[x] [department name] here is the department name, like Los Angeles Police Department

X people killed by [department name] from 2013-19

Documentation:

Screenshots, Attachments, Linked GitHub Issues, etc

Dev & QA Notes:

Any additional notes from developers or QA required to complete this issue.

Fixed in Development


vcpkg integrate install: wrong path separator

C:\src\vcpkg>vcpkg integrate install
Error: Failed to copy file: C:\src\vcpkg\scripts\buildsystems\tmp\vcpkg.user.targets -> C:\Users\Administrator\AppData\Local\vcpkg/vcpkg.user.targets

OS: Windows 10 x64 build 19044.1415
Compiler: VS 2022 v17.0.4 / MSVC v143
Vcpkg package management program version 2021-12-09-724cea8b33cbf06c645f5095fa29773697da9761

Steps to reproduce the behavior:

vcpkg integrate install
See error

Expected behavior:
Use backslash for paths on Windows, provide instuctions of everyhing this thing wants to do when its inadept to do so instead of bailing out on first failure

I was just about to submit this issue as I'm having the same problem.
PS C:\dev\vcpkg\> vcpkg.exe integrate install
Error: Failed to copy file: C:\dev\vcpkg\vcpkg\scripts\buildsystems\tmp\vcpkg.user.targets -> C:\Users\helpdesk\AppData\Local\vcpkg/vcpkg.user.targets

Same problem here, I cannot install vcpkg

Workaround:
./vcpkg.exe integrate install also does not work. However, adding the git repo directory to the Windows path does make vcpkg.exe integrate install work.

Same issue.  Fresh Win 11 dev VM from MS with VS2022 and latest MSVC143.
C:\vcpkg>.\vcpkg.exe integrate install Error: Failed to copy file: C:\vcpkg\scripts\buildsystems\tmp\vcpkg.user.targets -> C:\Users\User\AppData\Local\vcpkg/vcpkg.user.targets

I get vcpkg clean source and couldn't repro this issue locally.
C:\vcpkg>vcpkg integrate install
Applied user-wide integration for this vcpkg root.

All MSBuild C++ projects can now #include any installed libraries.
Linking will be handled automatically.
Installing new libraries will make them instantly available.

CMake projects should use: "-DCMAKE_TOOLCHAIN_FILE=C:/vcpkg/scripts/buildsystems/vcpkg.cmake"

Related code:
            const auto appdata_src_path = tmp_dir / "vcpkg.user.targets";
            fs.write_contents(
                appdata_src_path, create_appdata_shortcut(paths.buildsystems_msbuild_targets), VCPKG_LINE_INFO);
            auto appdata_dst_path = get_appdata_targets_path();

            fs.copy_file(appdata_src_path, appdata_dst_path, CopyOptions::overwrite_existing, ec);
            if (ec)
            {
                print2(Color::error, "Error: Failed to copy file: ", appdata_src_path, " -> ", appdata_dst_path, "\n");
                Checks::exit_fail(VCPKG_LINE_INFO);
            }

Can any one confirm that whether C:\Users\User\AppData\Local\vcpkg exist?
Thanks.

Can any one confirm that whether C:\Users\User\AppData\Local\vcpkg exist?
Thanks.

C:\Users%USERNAME%\AppData\Local\vcpkg did not exist for me.  Manually created the directory and was able to run vcpkg integrate install successfully:
C:\vcpkg>mkdir C:\Users\%USERNAME%\AppData\Local\vcpkg
C:\vcpkg>vcpkg integrate install
Applied user-wide integration for this vcpkg root.

All MSBuild C++ projects can now #include any installed libraries.
Linking will be handled automatically.
Installing new libraries will make them instantly available.

CMake projects should use: "-DCMAKE_TOOLCHAIN_FILE=C:/vcpkg/scripts/buildsystems/vcpkg.cmake"

Okay, thanks @modtrek !

@JackBoosY thank you for linking source, i must have overlooked it before
i tried your change but unfortunately it didn't fix it as this wasn't the issue (but now the error at least doesn't attract attention on the inconsistency, preventing false suspicion like mine)
creating the directory indeed fixed it 👍
wonder why it failed at that task, should have no issues permission wise (or has it never attempted to do so?)

wonder why it failed at that task, should have no issues permission wise (or has it never attempted to do so?)

Any way, I will add code to check whether this folder was created.

Fixed by https://github.com/microsoft/vcpkg/pull/22629


Notify students by text that they are marked missing

When students are marked missing, text them so they can come see the TAs right away! It would also be cool if students could reply that they are in the CIT and ready to be seen again.

Definitely overlaps with #116

Notifications currently happen by both text and email, depending on the preferences set on the ticket. We should probably follow these preferences (and support both text and email) when sending missing notifications.


fuse: device not found, try 'modprobe fuse' first

Hello, I received the following when trying to mount for the first time, I cant workout what is wrong.
Kindly help if I miss something!
root@server:~# google-drive-ocamlfuse -label<EMAIL_ADDRESS><EMAIL_ADDRESS>fuse: device not found, try 'modprobe fuse' first
root@server:~# modprobe fuse
modprobe: ERROR: ../libkmod/libkmod.c:514 lookup_builtin_file() could not open builtin file '/lib/modules/2.6.32-042stab117.16/modules.builtin.bin'
modprobe: FATAL: Module fuse not found in directory /lib/modules/2.6.32-042stab117.16

Did you updated your kernel without rebooting? If so, a reboot could probably fix it. Otherwise try with depmod -a.

Hi,
I have ran depmod -a and I got the following error:
root@mp3:~# depmod -a
depmod: WARNING: could not open /lib/modules/2.6.32-042stab127.2/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/2.6.32-042stab127.2/modules.builtin: No such file or directory
Can you help ?
Regards,
Shmuel

+1


[FLINK-33722] Fix events ordering in MATCH_RECOGNIZE in batch mode

What is the purpose of the change
Currently, MATCH_RECOGNIZE completely ignores the ORDER BY clause in batch mode: the events are processed in the order they come which makes no sense. This pull request adds proper events ordering in Pattern Recognition for batch.
Brief change log

Fix events ordering in MATCH_RECOGNIZE in batch mode

Verifying this change
This change added tests and can be verified with org.apache.flink.table.planner.runtime.batch.sql.MatchRecognizeITCase. Existing tests have been modified.
A few new tests have been added - they are simiar to the ones in org.apache.flink.table.planner.runtime.stream.sql.MatchRecognizeITCase.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@flinkbot run azure


Editing the prefix leaves the style in two places

If you edit the prefix of a style in the master view, it gets added to the new additional style file, but it also remains in the old one...

If #76 gets done this will become much less important.

With #76 done, closing this as not worth fixing


Error while throwing runtime error in ArrowReaderWorker

In ArrowReaderWorker, when trying to load a column of list type, where list is of variable length an error needs to be thrown. This error is defined here.
However the error fails while printing
Instead of
', '.join({values.shape[0] for value in ....})
It should be
', '.join({str(values.shape[0]) for value in ....})

Can be resolved by https://github.com/uber/petastorm/pull/407

Resolved by https://github.com/uber/petastorm/pull/407


Loading MoViNet saved_model in tensorflow 2.7 throws FileNotFoundError: Op type not registered 'DisableCopyOnRead' in binary running

Issue type
Support
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
binary
TensorFlow version
tf 2.7
Custom code
Yes
OS platform and distribution
Linux Ubuntu 18.04
Mobile device
No response
Python version
3.6
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
Jetson Nano Maxwell Architecture GPU - 4GB
Current behavior?
I am trying to load an exported MoViNet saved model in tensorflow version 2.7. The model loads fine in tensorflow version 2.10. However, I need to run the model on Nvidia's Jetson nano which does not support tensorflow version greater than 2.7. Loading the model in tf 2.7 gives me the error Op type not registered 'DisableCopyOnRead'. This issue might be due to version compatibility  since I exported the model using tensorflow 2.10 and tf-models-official. For exporting model I used :
this notebook's code.
I tried to export the model using tf 2.7 but tf-models-official does not work with tf<2.10.
Are there any workarounds by converting the model in some other format so that I can run it on my Jetson Nano's tensorflow version 2.7.
Any help would be greatly appreciated. Much thanks.
Standalone code to reproduce the issue
import tensorflow as tf

model = tf.saved_model.load("path/to/saved_model")

Relevant log output
KeyError                                  Traceback (most recent call last)
[c:\Users\Hammad\anaconda3\envs\temp\lib\site-packages\tensorflow\python\framework\ops.py](file:///C:/Users/Hammad/anaconda3/envs/temp/lib/site-packages/tensorflow/python/framework/ops.py) in _get_op_def(self, type)
   4097     try:
-> 4098       return self._op_def_cache[type]
   4099     except KeyError:

KeyError: 'DisableCopyOnRead'

During handling of the above exception, another exception occurred:

NotFoundError                             Traceback (most recent call last)
[c:\Users\Hammad\anaconda3\envs\temp\lib\site-packages\tensorflow\python\saved_model\load.py](file:///C:/Users/Hammad/anaconda3/envs/temp/lib/site-packages/tensorflow/python/saved_model/load.py) in load_internal(export_dir, tags, options, loader_cls, filters)
    938         loader = loader_cls(object_graph_proto, saved_model_proto, export_dir,
--> 939                             ckpt_options, options, filters)
    940       except errors.NotFoundError as err:

[c:\Users\Hammad\anaconda3\envs\temp\lib\site-packages\tensorflow\python\saved_model\load.py](file:///C:/Users/Hammad/anaconda3/envs/temp/lib/site-packages/tensorflow/python/saved_model/load.py) in __init__(self, object_graph_proto, saved_model_proto, export_dir, ckpt_options, save_options, filters)
    138         function_deserialization.load_function_def_library(
--> 139             meta_graph.graph_def.library, wrapper_function=_WrapperFunction))
    140     self._checkpoint_options = ckpt_options

[c:\Users\Hammad\anaconda3\envs\temp\lib\site-packages\tensorflow\python\saved_model\function_deserialization.py](file:///C:/Users/Hammad/anaconda3/envs/temp/lib/site-packages/tensorflow/python/saved_model/function_deserialization.py) in load_function_def_library(library, load_shared_name_suffix, wrapper_function)
    387     with graph.as_default():
--> 388       func_graph = function_def_lib.function_def_to_graph(copy)
...
    943             "from the computational device. Consider setting the "
    944             "`experimental_io_device` option in `tf.saved_model.LoadOptions` "

FileNotFoundError: Op type not registered 'DisableCopyOnRead' in binary running on LAPTOP-V4DO1PQN. Make sure the Op and Kernel are registered in the binary running in this process. Note that if you are loading a saved graph which used ops from tf.contrib, accessing (e.g.) `tf.contrib.resampler` should be done before importing the graph, as contrib ops are lazily registered when the module is first accessed.
 You may be trying to load on a different device from the computational device. Consider setting the `experimental_io_device` option in `tf.saved_model.LoadOptions` to the io_device such as '/job:localhost'.

@yuanliangzhe @yeqingli Can you guys please give me any pointers on how to build and export the MoViNet model in tensorflow 2.7 without relying on  tf-models-official package. Or alternatively, load an already exported saved_model in tf 2.7. Note that, the tflite version of the model loads fine. It is the saved_model format that's causing the issue.

The issue was resolved by building the model int tensorflow version 2.9. When tf-models-official package was installed it updated the tensorflow version to 2.14. Somehow, MoViNet model built in this version was not able to load in tf2.7.
I downgraded tensorflow to the least possible version that was compatible with tf-models-official and then build the model using saved weights. After which I exported the model in saved_model format and it worked with tf2.7.


Request for ARMv7 docker builds for Raspberry

Hi.
I've trying a bit to build the Docker image to armv7, to run under Raspberry Pi 3/4 with no luck so far, so if possible it will be handy to have the tool running under Raspberry.
Thanks.
Regards.

Hi, Daniel. Would you please provide me with some details about this "no luck"? Is it a build errors? Are they related to some package or app itself?

Hi.
I have not much experience with building dockers, before trying to cross compile for armv7 I tried to build locally changing line:
FROM golang:$GOLANG_VERSION as builder
to FROM golang:alpine as builder
with your original line any attempt with buildx failed
but then fails with:
Step 11/22 : RUN go install github.com/phogolabs/parcello/cmd/parcello
 ---> Running in b811244c5985
/go/pkg/mod/github.com/phogolabs/parcello@v0.8.2/cmd/parcello/main.go:13:2: missing go.sum entry for module providing package github.com/phogolabs/cli (imported by github.com/phogolabs/parcello/cmd/parcello); to add:
        go get<EMAIL_ADDRESS>The command '/bin/sh -c go install github.com/phogolabs/parcello/cmd/parcello' returned a non-zero code: 1

Not sure if the error is on my side or with the repository of parcello, that just now I saw it is in read only and somehow deprecated.
Regards.

GOLANG_VERSION defined here as 1.15.5-alpine3.12
So you have upgraded golang version from 1.15 to (what version, 1.16? 1.17?) and met some errors.  I guess this is normal and this is golang version update issue, not "ARMv7".  What alpine version you want build for?

I did not intended to change golang version, I switched to alpine in DockerFile to see if that will help to build for armv7 and is a light distro.
I just wanted to build for arm7v so I can run the docker in my Raspberry Pi 4.

I suppose you should find appropriate golang compiler atfist.
I've found golang-arm repo but it seems too old.
If there is some golang-arm-docker image which allows to build some golang application for your's target system, we will try to build webtail with it

Thanks for the binary, I guess this can be integrated with a golang arm docker image.
I just found out this https://hub.docker.com/r/arm32v7/golang/ repository that have official golang for arm32v7.
I can try to join both binary and image. Maybe you can add as a tag at docker hub for following releases.

Maybe you can add as a tag at docker hub for following releases.

diff --git a/Dockerfile b/Dockerfile
index 586e225..08e2e75 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,7 +1,7 @@
 ARG GOLANG_VERSION

 # FROM golang:$GOLANG_VERSION as builder
-FROM ghcr.io/dopos/golang-alpine:v1.16.10-alpine3.14.2 as builder
+FROM golang:1.16.10-alpine as builder
 ARG TARGETARCH

 WORKDIR /opt/app

take this diff and build your oun version of webtail:
pi@racedb400:~/webtail $ docker build -f Dockerfile . -t webtail:local
Sending build context to Docker daemon  1.053MB
Step 1/17 : ARG GOLANG_VERSION
Step 2/17 : FROM golang:1.16.10-alpine as builder
1.16.10-alpine: Pulling from library/golang
764d2e53e1a6: Pull complete
9f548be3ae33: Pull complete
053162e9c4e9: Pull complete
2095417f039b: Pull complete
4a03b7f34f89: Pull complete
Digest: sha256:45412fe3f5016509fc448b83faefc34e6f9e9bcc8ca1db1c54505d5528264e16
Status: Downloaded newer image for golang:1.16.10-alpine
 ---> 803866474dab
Step 3/17 : ARG TARGETARCH
 ---> Running in b887a5cb766e
Removing intermediate container b887a5cb766e
 ---> ac89a0794831
Step 4/17 : WORKDIR /opt/app
 ---> Running in c72df918a0fd
Removing intermediate container c72df918a0fd
 ---> 6ae2bab59bb3
Step 5/17 : COPY ./go.mod ./go.sum ./
 ---> 803bd97bbb7c
Step 6/17 : RUN echo "Build for arch $TARGETARCH"
 ---> Running in 7f0eabb57f9a
Build for arch
Removing intermediate container 7f0eabb57f9a
 ---> 38e8acfec595
Step 7/17 : COPY ./ ./
 ---> 4180537de320
Step 8/17 : RUN CGO_ENABLED=0 go test -tags test -covermode=atomic -coverprofile=coverage.out ./...
 ---> Running in 075a8a37fbb0
go: downloading github.com/go-logr/logr v0.3.0
go: downloading github.com/fukata/golang-stats-api-handler v1.0.0
go: downloading github.com/go-logr/zapr v0.3.0
go: downloading github.com/jessevdk/go-flags v1.3.1-0.20170926144705-f88afde2fa19
go: downloading github.com/mattn/go-colorable v0.1.8
go: downloading go.uber.org/zap v1.16.0
go: downloading github.com/stretchr/testify v1.6.1
go: downloading github.com/dc0d/dirwatch v0.4.3
go: downloading github.com/gorilla/websocket v1.4.2
go: downloading github.com/nxadm/tail v1.4.8
go: downloading github.com/a8m/djson v0.0.0-20170509170705-c02c5aef757f
go: downloading github.com/wojas/genericr v0.2.0
go: downloading github.com/mattn/go-isatty v0.0.12
go: downloading github.com/dc0d/retry v1.2.0
go: downloading github.com/fsnotify/fsnotify v1.4.9
go: downloading github.com/pkg/errors v0.9.1
go: downloading github.com/davecgh/go-spew v1.1.1
go: downloading github.com/pmezard/go-difflib v1.0.0
go: downloading gopkg.in/yaml.v3 v3.0.0-20200313102051-9f266ea9e77c
go: downloading go.uber.org/atomic v1.6.0
go: downloading go.uber.org/multierr v1.5.0
go: downloading gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7
go: downloading golang.org/x/sys v0.0.0-20200223170610-d5e6a3e2c0ae
ok  	github.com/LeKovr/webtail	1.088s	coverage: 86.9% of statements
ok  	github.com/LeKovr/webtail/cmd/webtail	0.524s	coverage: 100.0% of statements
Removing intermediate container 075a8a37fbb0
 ---> ba9ab0db594b
Step 9/17 : RUN CGO_ENABLED=0 go build -ldflags "-X main.version=`git describe --tags --always`" -a ./cmd/webtail
 ---> Running in f35c44e16ad3
/bin/sh: git: not found
Removing intermediate container f35c44e16ad3
 ---> 4415ee1e549e
Step 10/17 : FROM scratch
 --->
Step 11/17 : MAINTAINER Alexey Kovrizhkin<EMAIL_ADDRESS> ---> Running in 769eb24922ca
Removing intermediate container 769eb24922ca
 ---> b05a4d57ea28
Step 12/17 : LABEL org.opencontainers.image.description "Tail [log]files via web[sockets]"
 ---> Running in d9daa37e8bd8
Removing intermediate container d9daa37e8bd8
 ---> 654a0277cb4e
Step 13/17 : VOLUME /data
 ---> Running in e9f683e842df
Removing intermediate container e9f683e842df
 ---> cae782b79e9c
Step 14/17 : WORKDIR /
 ---> Running in d9cd1e252f74
Removing intermediate container d9cd1e252f74
 ---> e8e89993ec04
Step 15/17 : COPY --from=builder /opt/app/webtail .
 ---> 323cd2cba6d3
Step 16/17 : EXPOSE 8080
 ---> Running in 89acaf690c24
Removing intermediate container 89acaf690c24
 ---> 496e39fc507a
Step 17/17 : ENTRYPOINT ["/webtail"]
 ---> Running in 7514c82a0a48
Removing intermediate container 7514c82a0a48
 ---> 1235e9d65f3d
Successfully built 1235e9d65f3d
Successfully tagged webtail:local

racedb400:/opt/webtail.ds $ docker-compose up
Creating webtailds_app_1 ... done
Attaching to webtailds_app_1
app_1  | {"level":"info","ts":1637005243.9570744,"caller":"webtail/app.go:32","msg":"WebTail. Tail (log)files via web.","v":""}
app_1  | {"level":"info","ts":1637005243.9576,"caller":"webtail/app.go:44","msg":"Listen","addr":":8080"}
app_1  | {"level":"info","ts":1637005244.9140797,"caller":"app/indexer.go:96","msg":"Handling file event","event":{"Name":"/log/daemon.log","Op":2}}
app_1  | {"level":"info","ts":1637005244.9147964,"caller":"app/indexer.go:96","msg":"Handling file event","event":{"Name":"/log/daemon.log","Op":2}}
app_1  | {"level":"info","ts":1637005244.9151394,"caller":"app/indexer.go:96","msg":"Handling file event","event":{"Name":"/log/syslog","Op":2}}
app_1  | {"level":"info","ts":1637005244.9142997,"caller":"app/indexer.go:96","msg":"Handling file event","event":{"Name":"/log/syslog","Op":2}}
app_1  | {"level":"info","ts":1637005244.9166102,"caller":"app/indexer.go:96","msg":"Handling file event","event":{"Name":"/log/syslog","Op":2}}
app_1  | {"level":"info","ts":1637005244.9163146,"caller":"app/indexer.go:96","msg":"Handling file event","event":{"Name":"/log/daemon.log","Op":2}}
app_1  | {"level":"info","ts":1637005249.2452233,"caller":"app/indexer.go:96","msg":"Handling file event","event":{"Name":"/log/daemon.log","Op":2}}
app_1  | {"level":"info","ts":1637005249.2453895,"caller":"app/indexer.go:96","msg":"Handling file event","event":{"Name":"/log/syslog","Op":2}}

Also v0.46.1 have docker images for arm/v7, use docker pull ghcr.io/lekovr/webtail:v0.46.1


remove the leftover dbg! call

There is an annoying dbg call here:
https://github.com/adrien-bon/bevy_ecs_tiled/blob/main/src%2Fasset.rs#L166-L167
This should be replaced by debug! or even better a trace! instead.
Happy to open a PR with this small chance.

Hi!
Thanks for reporting the issue.
This dbg() call was added then forgotten during rework on properties.
Yes, please go ahead and remove it!


unable to recreate the state of killed application

Mosby Version:
compile 'com.hannesdorfmann.mosby:viewstate-conductor:0.8.2'
Expected behavior
the controller that are added to router are recreated
Actual behavior (include a stacktrace if crash)
the saveinstancestate of the application is null when recover from force stopped application and the application reset to first controller, all the backstack is lost.
Steps to reproduce the behavior or link to a sample repository
From the root controller, go to a viewpager controller , than go to a child controller of folder details and than to another deeper controller of inner folder. when i go back to home and force kill the application from android studio, when i select the application from list of apps, the backstack is lost and the app restart from the first controller, and the saveinstancestate is null.
The demo app of conductor without mosby works well, the backstack is recreated and the saveinstancestate is not null when recreate the app state. So i'm thinking that the problem is from mosby.
Do you have any clue about this strange behavior?

the backstack is lost and the app restart from the first controller

So the problem is that the whole back stack got lost? If yes, then this is not a Mosby issue. Mosby is not handling or changing conductor's router somehow internally. Mosby doesn't know about Conductor's Router at all.
If the back stack is restored properly by Conductor, but you are wondering why your ViewState is like starting the app for the first time, then this is the expected behavior.
Per default, Mosby is not saving any ViewState information in Bundle. So Mosby is per default not surviving process death.
Per default Mosby only save instance through screen orientation change and back stack navigation.
To do so you have to use a ViewState instance of interface RestorableViewState extends ViewState  like ParcelableListLceViewState (if you use the LCE package) which may requires that all your "model" data implements the Parcelable interface too.
Btw. I strongly recommend to update to viewstate-conductor:3.0.0

ok, i had migrated to 3.0.0.
Now, my question is, wich is the best practice to recreate the state of the backstack of the forced application closed like conductor demo application?

again, what exactly is the problem you are facing?
If I understand your description correctly:

when i go back to home and force kill the application from android studio, when i select the application from list of apps, the backstack is lost and the  app restartfrom the first controller, and the saveinstancestate is null.

app restartfrom the first controller, this is not a Mosby issue. As already said, Mosby is not changing Conductor Router. Mosby is not the cause that your app is starting with the first controller.

Seems that i'm missing some point; the conductor sample application can recover the backstack, my application can't. When i recover from stopped application, the savedinstancestate of main activity is null (strange!), in the demo app of conductor is !=null, and i think is used to recreate the backstack.
In my application the code that handle navigation from a controller to another is the same that is used in the demo conductor. So the only difference that i see in my code is that i'm using mosby. I'm not sure that the problem is mosby, but at the moment, the application works well in navigation from the controllers, but when i force stop the app, when i select it from apps in background the app restart from the first controller with in the mainrouteractivity savedinstancestate == null. My question is: who set the savedinstancestate to null? I can't understand. If i can't find the problem the only way is remove all dependencies from mosby and test the recreation of back stack with my own presenters, but is a lot of work and i want avoid it.
Are you sure that i don't do anything for handle the recreation of backstack when i use mosby?

My question is: who set the savedinstancestate to null
Not Mosby.

Are you sure that i don't do anything for handle the recreation of backstack when i use mosby?
I am sure

Do you have your app open source on github so that I can take a closer look?

No , the application is not mine but is for a company that i work, is on private svn server.
Another clue for investigation:
i'm going deeper in your sample code, the application can handle the backstack recover, so my another question is: wich are the classes that handle the recreation of the backstack when the app is recovered? I see in the createtaskcontroller : MvpViewStateController<CreateTaskView, CreateTaskPresenter, CreateTaskViewState>.
has MvpViewStateController class the responsability in the recreation backstack?
At the moment my controller base is
public abstract class BaseController extends MvpController
wich is the difference of responsability between Mvpcontroller and MvpViewStateController ?

wich are the classes that handle the recreation of the backstack when the app is recovered?

Mosby does not recreate the back stack. It's conductor who is recreating the backstack and instantites the controllers on the back stack. Again, Mosby has zero knowledge of the backstack or Router or any other Conductor components involved in backstack management.
MvpViewStateController adds a feature so that the state of the UI Elements is not lost during screen orientation changes. More info here: http://hannesdorfmann.com/mosby/viewstate/ (the docs talk about fragments, but Conductor controller also recreates the view, so it's the same issue that is solved with ViewState feature)
Can you post the code of your MainActivity?

sure, now i post the mainactivity and application most important code:
MAIN:

public class MainRouterActivity extends AppCompatActivity implements ActionBarProvider {
......
private static final String TAG = "MainRouterActivity";
private Router router;
@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);

    if (Build.VERSION.SDK_INT >= 21) {
        getWindow().getDecorView().setSystemUiVisibility(
                View.SYSTEM_UI_FLAG_LAYOUT_STABLE
                        | View.SYSTEM_UI_FLAG_LAYOUT_FULLSCREEN);
    }

    setContentView(R.layout.main_router_activity);
    ButterKnife.bind(this);

    ApplicationStatus.initialize(this.getApplication());
    if (savedInstanceState != null) {
        Log.d("initapp", savedInstanceState.toString());
    } else {
        Log.d("initapp", "saveinstancestate is null");
    }
    router = Conductor.attachRouter(this, flRootContainer, savedInstanceState);
    if (!router.hasRootController()) {
        RouterTransaction firstTransaction = RouterTransaction.with(new BrowserViewController());
        firstTransaction.tag(BrowserViewController.TAG_ROUTER);
        router.setRoot(firstTransaction);
    }

}

@Override
public ActionBar getSupportActionBar() {
    return super.getSupportActionBar();
}

@Override
public void onBackPressed() {
    if (!router.handleBack()) {
        super.onBackPressed();
    }
}

@Override
protected void onSaveInstanceState(Bundle outState) {
    Log.d("state", "activity saveinstancestate");
    super.onSaveInstanceState(outState);
}

APPLICATION:

i don't see strange code in the application code, only that is multidex application.

¯_(ツ)_/¯
I can't see any issue here. Sorry, I can't help you.
You should continue to ask on conductor but if savedInstanceState is really null than this rather seems like some strange device behavior, because as far as I know conductor is not setting the savedInstanceState to null somehow. Actually, I think that it is not possible to set a bundle to null at all because this bundle is handed over to the Activity by the operating system and then activity is passing it to conductor. Same workflow when saving things (like the back stack of controllers) into a bundle. The bundle is created by the operating system and then hand over to Activity.onSaveInstanceState() and forwarded internally to Conductor which then saves the Router. I can't really see how a bundle could be "set" somehow to null.
Double check:

Is you app crashing somehow (do you see stack traces) when the application is killed?
Try it with a different device / manufacturer

Last but not least,
try to build a little sample example with just 3-4 Controllers that reproduces this issue and attach it on https://github.com/bluelinelabs/Conductor/issues/253 Otherwise, it will be super hard to reproduce this issue somehow. Also try to build the same navigation hierarchy as you have in your real app like ViewPager and child routers as you have in your real app.
Sorry, I can't help you.

Finally i got the issue, not mosby , not conductor, but my first class (a browser like chrome) and his complex saveinstancestate that break the save of the state of the application ... when i replace that class with another fake controller the app works well. Thanks for your time and your patience @sockeqwe


Release 0.112.x ->Interface to InfluxDB broken?

Looks like there are no measurements (PV, Battery, Grid) transmitted to influxdb since the release 0.112.x -> if I switch back to 0.111.1 everything is fine again
Was there a desired change in the data structure (I could not see any new measurements in the database?)?
Thanks

Duplicate #6034


doc(runtime): Small Correction on Runtime Doc (2nd attempt)

Correction in README.md at runtime/docs while i read the docs to know about dart internal :)

[x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

See our contributor guide for general expectations for PRs.
Larger or significant changes should be discussed in an issue before creating a PR.
Contributions to our repos should follow the Dart style guide and use dart format.

Note that this repository uses Gerrit for code reviews. Your pull request will be automatically converted into a Gerrit CL and a link to the CL written into this PR. The review will happen on Gerrit but you can also push additional commits to this PR to update the code review.

2nd Attempt of https://github.com/dart-lang/sdk/pull/54157 , the Gerrit CL dint ran for that. So Closing that and raising this one

Seems Gerrit CL wont do analysis if there was change only in md files i guess @devoncarew

Nvm, its gave a review.


Update

Hey, any chance you could update this to the latest version?

Yep, it needs some work. I'll get to it soon. :)

Awesome. Cheers

Any update on the update?


Clarify "trap day" on days where no timelapse image taken

For example, at the beginning of a deployment, if the camera was set up after 12:00, the daily timelapse image will not have been taken. But can still get detections in that day. Does it count?

Confirmed from team that days with no time lapse will not count as "trap days"


Upgrade flask-restplus version when it's available

It should fix the forward slash issue.
https://github.com/noirbizarre/flask-restplus/issues/251

So looks like we need 0.11 (we're still on 0.9.2 so should try an incremental upgrade first)

We are using the latest Flask-RESTPlus version 0.11


Improve documentation about null and is defined

From the language reference documentation it's not very clear in which situations == null should be used, to determine whether the value of an attribute or relation was set to null, and in which situation is defined should be used.
My observation is that the behavior is consistent for regular attributes, but not for relational attributes.
entity Test:
   string? optional
   string? optional_default = null
end

Test.ref_optional [0:1] -- Test
Test.ref_optional_list [0:] -- Test

implement Test using std::none

t = Test(optional=null, ref_optional=null)

# Behavior for regular attributes

std::print(t.optional == null)                 # --> true
std::print(not t.optional is defined)          # --> true

std::print(t.optional_default == null)         # --> true
std::print(not t.optional_default is defined)  # --> true

# Behavior for relational attributes

#std::print(t.ref_optional == null)             # --> Results in compile error
std::print(not t.ref_optional is defined)       # --> true

std::print(t.ref_optional_list == null)         # --> false
std::print(t.ref_optional_list == [])           # --> true
std::print(not t.ref_optional_list is defined)  # --> true

Question: Is the goal to deprecate the is defined keyword?

Note to self: need to think about this before we can pick it up, or even discuss it.


add marker

Summary of proposed changes
add marker
How to use?

Option: markers
Type: Object
Default: {}
Description: A plugin that displays customizable markers upon progress bars of the video . This could be used to show video breaks and show overlaid text on the video when playback reaches the specific break point.

Example
const player = new Plyr(selector, {
    tooltips: {
        controls: true,
    },
    markers: {
          "60":"苟利国家生死以",
          "120":"岂因祸福避趋之",
          "180":"闷声大发财"
    },
});

Closing this. Please re-open the PR once the work is clean and complete. There's all sorts of comments and issues and none of the issues I raised have been fixed.


Shim undefined PATH_INFO (nginx)

It appears that PATH_INFO is undefined by default on nginx. Quick shim

not sure about that. you should always pass the route to the constructor. in your case e.g.:

$app = new Lime\App([
    'route' => explode("?", $_SERVER["REQUEST_URI"])[0]
]);

I see. In that case though why have a default at all if the default will be unreliable across environments?
            'route'        => isset($_SERVER["PATH_INFO"]) ? $_SERVER["PATH_INFO"] : "/",
As an end user it was disorienting for this to work in one environment and not another. The PATH_INFO based default prevented me from realizing I was not following best practice (passing a base route into the constructor).
Anyway, just my two cents!


fix(polyphony): fixes channel selection bug

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


libseccomp: disable broken tests on llvm

Description of changes
Discovered in https://github.com/RossComputerGuy/nixpkgs-llvm-ws/runs/27894511542, many tests fails under pkgsLLVM.libseccomp so we disable it until they are fixed.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] 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/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

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

github:nixos/nixpkgs/refs/pull/329827/merge#pkgsLLVM.libseccomp builds


Signing an API request

Good job on releasing this package!
I am interested in knowing how to sign API Gateway requests with Signature Version 4 using this package. I tried a couple of packages like aws4 but they are made for react native mostly because React Native doesn't support the crypto module.
Thank you!

Hi, the library will automatically sign the requests for you without any effort on your part. You just need to use the Auth and API modules. Check out the documentation and examples: https://github.com/aws/aws-amplify/blob/master/media/api_guide.md

@undefobj Thanks for the quick reply! But it is not clear where/how I should pass accessKey, secretKey & sessionToken. I am using federated login with Facebook as the provider.

This might me what I am looking for. https://aws.github.io/aws-amplify/packages/aws-amplify-react-native/docs/Signer.html

Yes you can also use the signer directly if you choose. However for our feature list, would you like to be able to also pass in keys to the API module? Or would you rather have federation functionality with Facebook with the Auth modules and have those credentials automatically passed in when you use the API module?


Ability to boot only once per class

Booting the kernel is slow.
It may sometimes be desirable to reuse a kernel across several related tests, especially when they rely upon the same container's configuration.

I'd argue that tests using the kernel/container should be rare. Each test should start with a clean state to be reliable.
However, I understand on some codebases there's no other way and one would like to save some time on booting the kernel. I think you can already do it by implementing your own trait (like SymfonyTestContainer). If you'd like to contribute to this repo, I'm open to accept a pull request adding this feature (if it doesn't change the code drastically).

What I'm currently doing is to pass per-test kernel configuration as a test metadata.
Eg:
    /**
     * @testWith [{"replace":{"foo":{"bar":"allowed_group"}}}]
     */
    public function testGroupsValidation() {}

And my in my trait:
    public function createContainer(): ContainerInterface
    {
        foreach ($this->getProvidedData() as $value) {
            if (isset($value['replace'])) { array_replace_recursive("blabla", $value['replace']); }
        }
        return static::bootKernel(['config' => $config]) // my test Kernel handles this `config` key
            ->getContainer()
            ->get('test.service_container');
}

It sounds fragile but is the only way I found a test could declare per-container configuration and still be relieved from the task of initializing the container itself (and rely upon phpunit-injector)

Not entirely what you're after, but maybe it will give you some ideas. Some time ago I was playing with the idea of initialising bundle configs per test case: https://github.com/jakzal/bundle-test

Not entirely what you're after, but maybe it will give you some ideas. Some time ago I was playing with the idea of initialising bundle configs per test case: https://github.com/jakzal/bundle-test

That's exactly why I'm after (and I don't understand that few developers experience the same need).
For now I created a homegrow annotation system that allows me to set configuration (and service's mocks) on a per-test basis, eg:
    /**
     * @testWith [{"mocks":{"cygne_sync.driver.my.service":"MyBundle\\Tests\\Mock\\My\\Service"}}]
     */

or
    /**
     * @testWith [{{"set":{"my.destinations.config.mc.strategy":{"class":"PostPatch","args":[]},"blah.groups":{"extra":{"forcedGroup":true},"allowed":{"optionalGroup":true}},"destinations.tags":{"extra":["forcedTag"],"allowed":["optionalTag"]}}}]
     */

where the equivalent bundle YAML is set as a JSON data annotation.
But would surely prefer to go with a clean, reliable and mainstream library to do this. Why did you archived your project? Did you find a better alternative?

Why did you archived your project? Did you find a better alternative?

The only reason is I stopped developing bundles. I believe that my bundle-test was the most flexible solution out there. Feel free to take it over. Unfortunately, I don't remember in what state I have left it and if it was ready to use.


A tool to produce a CSV linking bundle members with file paths

This module creates a .csv file listing the members of a bundle, their associated member status and reference types, and creates a list of paths to .xml and .lblx files associated with that collection term.
The tool should be called pds4_create_bundle_member_index.py
The following specifications for this module:

Input argument should be described in comment (or docstring?) as the path containing the bundle.xml file.  Default should be the current directory.
Create bundle_member_entries (as done in name_scraper_221209.py), a list containing each instance of the Bundle_Member_Entry tag in bundle.xml
For each member of bundle_member_entries, find the LID (in name_scraper_221209.py, this was called data_collection_term, but I think bundle_member_lid would be a better name).  Create a dictionary bundle_member_index in which the key is the LID and the value is a list with three items, namely member_status and reference_type (both harvested from the lxml tree) and a blank string that you will later replace with the path.
Use os.walk to look ONLY in the first level of subdirectories for files whose extension is .lblx or .xml
Using lxml, find the LID of each file found.  If it matches a key in the dictionary, then put its path into the corresponding place.  If it does not match any key in the dictionary, then create a line of output saying "PDS4 label found but not a member of this bundle: <filepath>, <lid>."
If there are any remaining entries in your dictionary whose paths have not been filled, throw an error.
Write the dictionary bundle_member_index into a file bundle_member_index.csv.

I edited @esimpsons3ti's description above, in order to make items #2 and #3 more clear.
The antecedent software name_scraper_221209.py is not on GitHub, but was posted by @esimpsons3ti to our Slack channel.

To clarify: The tool that answers this issue should be given a single bundle.xml file and should create a CSV in the same directory with the characteristics described.  A different issue will cover the task of running this tool recursively.


Enable clang-tidy

Enable clang-tidy for clean code.

[ ] Fix clang-tidy warnings (There's a lot of them)
[ ] Add clang-tidy to CI

Fixed clang-tidy warnings in 283475dc45519737687717613ea31f2ea8d4a74f


full integration via TTN api & MQTT

I discovered that it is possible to automate device registration and LoRa-message subscription via APIs provided by TTN. This would free the user from the hassle of registering at 2 services, and keep the configuration state in sync.
The current webhook could still be provided for users with existing TTN applications, sending data via the TTN HTTP Integration.

ttn-osem-integration has its own TTN app_id, used to manage ALL devices from oSeM
device management via TTN Application Manager REST API
subscription to messages via TTN MQTT broker
TTN node SDK implements clients for those APIs

proposed workflow

user provides TTN config at oSeM (decoding profile + options only?)
oSeM pushes notification to ttn-osem-integration (or ttn-osem-integration polls for changes)
ttn-osem-integration creates new device in TTN
ttn-osem-integration subscribes to new device, and decodes as is implemented so far

possible issue is authentication; how is ensured only the correct physical LoRa device can submit measurements?
assuming we choose app_id = 'opensensemap' and dev_id = box._id for all boxes,
these IDs are no secrets, and would allow anybody to submit measurements via LoRa.
idea: set dev_id = box._id + randomSalt()

The integration is a really good idea! The the random String for identifying the senseBox is also a good idea for the main API

Progress can be found on branch feature/mqtt:
The integration now has its own TTN application, on which devices can be registered.
This registration is done by calling /v1.1/ttndevice/:boxId, which then returns device information for a given box.
This info can then be used to generate a sketch for example.
A subscription to messages from devices that were registered using this route is automatically set up via TTN MQTT broker.
TODOs:

[ ] proper route authentication. currently done via an IP whitelist (i know, right?)
[ ] tests
[ ] generate correct TTN keys. currently they are randomly generated which likely will not work. see https://www.thethingsnetwork.org/wiki/LoRaWAN/Address-Space


Tests to makes sure known strings are interned

To ensure the fast-path reference equals return from https://github.com/aspnet/KestrelHttpServer/pull/1006 isn't needed

@mikeharder resolved

@cesarbs changed to Equals and Same

:ship: after last comment.

Privatised it


removed unnecessary resource

Can this PR please be merged? I'm getting an error because of this ressource:
(node:14534) UnhandledPromiseRejectionWarning: CordovaError: Uh oh!
"/Users/borntsch/Documents/komed/komed-frontend/plugins/cordova-plugin-twiliovoice/sounds/disconnect.wav" not found!
``
`

@jefflinwood could you maybe also release a new version to NPM? Else we can't profit from the change :)


Attachment options don't respect hiding methods.

I'm disabling attachments options and they still show up.

hello @MEnnabah
You need to hide it via settings first. You are using getters.
  let attachmentOptionToHide = [":audio", ":video", ":location", ":shareContact"]
  ALApplozicSettings.setHideAttachmentsOption(attachmentOptionToHide)

Check for more options here:
https://docs.applozic.com/docs/ios-chat-theme-and-customization#section-customizing-attachment-options-

Thanks @adarshmishra

I have the same issue that ":blockUser" doesn't work in this list. I just upgraded to 5.2.0.

Thanks for sharing the details @chucksmith. We found the issue, it will be fixed in the next release.

Fixed


Enhancement request: random sorting

Hi, I would like to have a random sort option for the task query. My reason for this is I'd like to create a task bucket. I have a long list of tasks and only want to pick a few tasks out of that each day, but not the same list for each day.

This is just release in Tasks 7.11.0 - thank you again @qelo.


Update activity notification dropdown to use aplinejs

Also, update the look of the dropdown.

When reloading the page the notification box "flash". It does not do that in the current version.

The flashing issue is handled here https://github.com/HyphaApp/hypha/pull/3226/files#diff-991b4d1d98770e27e8db821a366e0c49d5ff3659e38677f7fc87f69f4326bfefR41; I was hoping the htmx PR would merge first! :D
Anyway, I'll have the x-cloak css added to this PR.


Phi-3-mini-4k-instruct : Failing to stop at <|end|> on generating the answer.

from mlx_lm import load, generate

model, tokenizer = load(path_or_hf_repo = phi3_path,#,tokenizer_config=tokenizer_config
                  # adapter_path = adapt_path,
                        tokenizer_config={"trust_remote_code": True})

messages = [
        {"role": "user", "content": 'Where is delhi, explain it only 3 points.'},
    ]
prompt = tokenizer.apply_chat_template(
            messages , tokenize=False, add_generation_prompt=True
        )

response = generate(model, tokenizer, prompt=prompt, verbose=True, temp=0.0, max_tokens=700)

########################## Output ##########
==========
Prompt: <s><|user|>
Where is delhi, explain it only 3 points.<|end|>
<|assistant|>

1. Capital city: Delhi is the capital city of India, serving as the political, cultural, and economic center of the country.

2. Historical significance: Delhi has a rich history dating back over 2,000 years, with several important empires and dynasties having ruled the city, including the Mauryans, Guptas, and Mughals. The city is home to numerous historical landmarks, such as the Red Fort, Qutub Minar, and Humayun's Tomb.

3. Modern metropolis: Today, Delhi is a bustling metropolis, with a population of over 30 million people. It is known for its diverse culture, vibrant street life, and numerous educational institutions, including the Indian Institute of Technology (IIT) and Jawaharlal Nehru University (JNU). The city is also a major hub for business, commerce, and transportation, with the Indira Gandhi International Airport being one of the busiest airports in India.<|end|><|assistant|> 1. Capital of India: Delhi is the capital city of India, serving as the seat of the government and the location of the President's official residence, Rashtrapati Bhavan.

2. Cultural melting pot: Delhi is a city with a rich and diverse cultural heritage, influenced by various religions, languages, and traditions. It is home to numerous historical monuments, museums, and art galleries, such as the National Museum, India Gate, and Lotus Temple.

3. Economic powerhouse: Delhi is one of the largest and fastest-growing metropolitan areas in India, with a thriving economy driven by sectors such as information technology, telecommunications, and manufacturing. The city is also a major center for education, with numerous prestigious universities and research institutions, including the Indian Institute of Technology (IIT) and Jawaharlal Nehru University (JNU).<|end|><|assistant|> 1. Political center: Delhi is the capital of India, housing the central government's administrative buildings, including the Parliament House, Rashtrapati Bhavan, and the Supreme Court of India.

2. Cultural and historical significance: Delhi is a city with a rich history and diverse cultural heritage, dating back over 2,000 years. It is home to numerous UNESCO World Heritage Sites, such as the Qutub Minar, Humayun's Tomb, and the Red Fort, which showcase the city's historical and architectural significance.

3. Economic and educational hub: Delhi is a major economic and educational center in India, with a thriving service sector, including information technology, telecommunications, and finance. The city is also home to numerous prestigious educational institutions, such as the Indian Institute of Technology (IIT), Jawaharlal Nehru University (JNU), and the University of Delhi.<|end|><|assistant|> 1. Capital city: Delhi is the capital of India, serving as the political, administrative, and cultural center of the country. It houses the central government's institutions, including the Parliament, the President's residence (Rashtrapati

i dont know how text is getting cross lines. please anyhelp  thanks

Could you share the model you are using (e.g. phi3_path)?

convert(hf_path = "microsoft/Phi-3-mini-4k-instruct",
mlx_path = "phir3_model_f",q_bits = 8,q_group_size=32,
quantize=True)
phi3_path = "/Train_custom_LLM/LLMX/phir3_model_f/"

It seems this isn't a bug. The original Phi-3-mini-4k-instruct model uses "<|endoftext|>" (not <|end|>) as its end-of-sequence (EOS) token.  You can verify this in the model's tokenizer.config file.

I updated the MLX Community Phi-3 models to use the correct eos token.
Also you can always specify the eos token in the load function like so:
load("model_name", tokenizer_config={"eos_token": "<|eos|>"})


help request for prepareFeature task

I am trying to use https://github.com/OpenLiberty/ci.gradle/blob/main/docs/prepareFeature.md#prepareFeature-task so that my user developed features can be pulled from Maven via featureUtility or Gradle.
Can someone please provide some additional guidance how to use this?
I have the feature(s) in ESA format, and a POM.  I am trying to generate features.json using this task.
When I run the task, it seems to search all the configured repositories for the POM and JSON, and then eventually fails with a NPE.
Questions:

Is the feature ESA and POM already supposed to be in Maven for this operation?  I thought the operation was to prepare the files needed to host it in Maven.

Is there a requirement the groupId ends with "features"?  For example, if my group id is com.test, I see the task always looking for com.test.features.

If I am actually supposed to start with the feature files locally, where do I put them in relation to the build.gradle?

Thank you

Task :prepareFeature
Caching disabled for task ':prepareFeature' because:
Build cache is disabled
Task ':prepareFeature' is not up-to-date because:
Task has not declared any outputs despite executing actions.
Cached resource https://repo.maven.apache.org/maven2/io/openliberty/features/install-map/maven-metadata.xml is up-to-date (lastModified: Thu Jul 26 10:56:21 EDT 2018).
Resource missing. [HTTP GET: https://oss.sonatype.org/content/repositories/snapshots/io/openliberty/features/install-map/maven-metadata.xml]
...
The features.json file was not found at the expected coordinate  in connected repositories.
Cached resource https://repo.maven.apache.org/maven2/io/openliberty/features/repository-resolver/maven-metadata.xml is up-to-date (lastModified: Thu Jul 26 10:57:36 EDT 2018).
Resource missing. [HTTP GET: https://oss.sonatype.org/content/repositories/snapshots/io/openliberty/features/repository-resolver/maven-metadata.xml]
Resource missing. [HTTP GET:
...

Task :prepareFeature FAILED
:prepareFeature (Thread[Execution worker for ':',5,main]) completed. Took 2.24 secs.

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':prepareFeature'.

java.lang.NullPointerException (no error message)

Stack trace:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':prepareFeature'.
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$3(ExecuteActionsTaskExecuter.java:186)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$$Lambda$500.0000000017118C20.accept(Unknown Source)
at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:268)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:184)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:173)
at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:109)
at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:62)
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$$Lambda$76.00000000104842A0.apply(Unknown Source)
at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:41)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:411)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:398)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:391)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:377)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:127)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker$$Lambda$444.00000000170043D0.execute(Unknown Source)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:191)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:182)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:124)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
Caused by: java.lang.NullPointerException
at io.openliberty.tools.common.plugins.util.PrepareFeatureUtil.generateJson(PrepareFeatureUtil.java:278)
at io.openliberty.tools.common.plugins.util.PrepareFeatureUtil.prepareFeature(PrepareFeatureUtil.java:121)
at io.openliberty.tools.common.plugins.util.PrepareFeatureUtil.prepareFeatures(PrepareFeatureUtil.java:88)
at io.openliberty.tools.common.plugins.util.PrepareFeatureUtil$prepareFeatures.call(Unknown Source)
at io.openliberty.tools.gradle.tasks.PrepareFeatureTask.prepareFeature(PrepareFeatureTask.groovy:46)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:104)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:58)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:51)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:29)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$2.run(ExecuteActionsTaskExecuter.java:494)
at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:71)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$$Lambda$80.0000000010484830.accept(Unknown Source)
at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:71)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:479)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:462)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.access$400(ExecuteActionsTaskExecuter.java:105)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.executeWithPreviousOutputFiles(ExecuteActionsTaskExecuter.java:273)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.execute(ExecuteActionsTaskExecuter.java:251)
at org.gradle.internal.execution.steps.ExecuteStep.lambda$executeOperation$1(ExecuteStep.java:66)
at org.gradle.internal.execution.steps.ExecuteStep$$Lambda$513.000000001711E680.get(Unknown Source)
at org.gradle.internal.execution.steps.ExecuteStep.executeOperation(ExecuteStep.java:66)
at org.gradle.internal.execution.steps.ExecuteStep.access$000(ExecuteStep.java:34)
at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:47)
at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:44)
at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$$Lambda$76.00000000104842A0.apply(Unknown Source)
at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:44)
at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:34)
at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:72)
at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:42)
at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:53)
at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:39)
at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:44)
at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:77)
at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:58)
at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:54)
at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:32)
at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:57)
at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:38)
at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:63)
at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:30)
at org.gradle.internal.execution.steps.BuildCacheStep.executeWithoutCache(BuildCacheStep.java:176)
at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:76)
at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:47)
at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:43)
at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:32)
at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:39)
at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:25)
at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:102)
at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$0(SkipUpToDateStep.java:95)
at org.gradle.internal.execution.steps.SkipUpToDateStep$$Lambda$496.0000000017117FB0.apply(Unknown Source)
at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:55)
at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:39)
at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:83)
at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:44)
at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:37)
at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:27)
at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:96)
at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:52)
at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:83)
at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:54)
at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:74)
at org.gradle.internal.execution.steps.SkipEmptyWorkStep.lambda$execute$2(SkipEmptyWorkStep.java:88)
at org.gradle.internal.execution.steps.SkipEmptyWorkStep$$Lambda$472.00000000170F2760.get(Unknown Source)
at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:88)
at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:34)
at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:38)
at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:46)
at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:34)
at org.gradle.internal.execution.steps.AssignWorkspaceStep.lambda$execute$0(AssignWorkspaceStep.java:43)
at org.gradle.internal.execution.steps.AssignWorkspaceStep$$Lambda$468.00000000170741B0.executeInWorkspace(Unknown Source)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution$3.withWorkspace(ExecuteActionsTaskExecuter.java:286)
at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:43)
at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:33)
at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:40)
at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:30)
at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:54)
at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:40)
at org.gradle.internal.execution.impl.DefaultExecutionEngine.rebuild(DefaultExecutionEngine.java:46)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$0(ExecuteActionsTaskExecuter.java:182)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$$Lambda$463.0000000017072710.apply(Unknown Source)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:182)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:173)
at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:109)
at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:62)
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$$Lambda$76.00000000104842A0.apply(Unknown Source)
at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:41)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:411)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:398)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:391)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:377)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:127)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker$$Lambda$444.00000000170043D0.execute(Unknown Source)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:191)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:182)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:124)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)

Hello,
Q. Is the feature ESA and POM already supposed to be in Maven for this operation? I thought the operation was to prepare the files needed to host it in Maven.
A. Yes, we are expecting feature ESA and POM to be in Maven Central or Maven local repository. The prepareFeature task generates a JSON file containing the information about your user feature. The json file will be used during the installation later on. Note that we will create the json inside the Maven local repository, we don't publish it to the Maven central.
Q. Is there a requirement the groupId ends with "features"? For example, if my group id is com.test, I see the task always looking for com.test.features.
A. No. When the prepareFeature task completes, it will generate features.json file under <user feature group_id>:features:<user feature version>. For ex) com.test:features:1.0
Q. If I am actually supposed to start with the feature files locally, where do I put them in relation to the build.gradle?
A. You can place your ESA and POM inside the Maven local repository. For example, if you user feature ESA has the Maven coordinate of com.test:myUserFeature:1.0, then for Mac OS, it would be .m2/repository/com/test/myUserFeature/1.0/myUserFeature-1.0.esa and com.test:myUserFeature-bom:1.0 would be .m2/repository/com/test/myUserFeature-bom/1.0/myUserFeatureBom-1.0.pom
In your build.gradle, add
dependencies {
    featuresBom 'com.test:myUserFeature-bom:1.0'
}

Thank you for the comments @jjiwooLim.  I already have the ESA and POM in Maven and can see they are being pulled down into local m2.  Let me try a few other things and report back.. Thanks for the support.

I am still not sure what I am missing.  Previously, I had the ESA and POM in the same directory location and was calling out the feature itself in the dependency like com:test:myfeature:1.0 instead of the BOM
After your reply, I have temporarily disabled connection to server repository and added mavenLocal() to global section and the buildscript section.
I kept the ESA in original location and moved the POM to myuserfeature-bom/VERSION/feature-bom-VERSION.pom
I don't fully understand this as to me all I am really changing is a package name to include "bom".
Here is sample structure within local .m2 repository:
com
├───test
│   └───liberty
│       └───feature
│           ├───oidcSecurity
│           │   ├───1.0.3
│           │                  oidcSecurity-1.0.3.esa
│           │
│           └───oidcSecurity-bom
│               └───1.0.3
oidcSecurity-bom-1.0.3.pom
oidcSecurityBom-1.0.3.pom

Task :prepareFeature

Could not find artifact with coordinates com.test.liberty.feature:oidcSecurity-bom:1.0.3@pom
A features-bom file must be provided at the given groupId com.ford.liberty.feature.
:prepareFeature (Thread[Execution worker for ':',5,main]) completed. Took 1.757 secs.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.8.3/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 5s
dependencies {
featuresBom 'com.test.liberty.feature:oidcSecurity-bom:1.0.3'
}
The POM has
com.test.liberty.feature
oidcSecurity
1.0.3
esa

@jjiwooLim Thank you!  Got it working, as well as installing the feature from featureUtility.

@smikishk Glad to hear! I will close the issue, thank you.

@smikishk Is there some documentation we should consider updating to make it clearer how to accomplish this? Glad you got it working!

@cherylking The main thing I didn't realize is that the features already need to be in the Maven repository.  That might be implied but this was my first time using this project.  Comments in this thread about using local .m2 repo were helpful and weren't present in other documentation I found.  Thank you again.

@jjiwooLim One more question.  I am now trying to generate the features.json for multiple features.  How to do this?  I have tried listing multiple featuresBom as well as comma separated to a single featureBom.  I am getting the features JSON for whichever is processed last, when I am actually trying to create one for multiple features.

Since the code does not handle this use case, I ended up manually merging the JSONs.

Hello @smikishk , I created #730 for this use case.
Please track this issue for any updates.
Thank you


Make Starling warn the user if one of the views is unsatisfiable

Unsatisfiable views are a persistent problem when developing Starling+GH proofs - it'd be useful to raise a warning (or fail the proof?)

Would this be in terms of a check to see that:

any defining views that are contradictory under SMT are constrained specifically to false (fairly easy check to add but wouldn't catch many GRASShopper-level problems unless it got kicked into a deferred check and even then I'm unsure of the best encoding);
all terms have a non-contradictory postcondition under SMT (this would throw up too many false positives I think);
if we inject P=>false procedures for each defining view, that each of them fails (this would require basically running GRASShopper in two directions, one to falsify these and one to validate the rest, which is a bit messy);
something else?

Yeah, the third one. Let me edit the issue to make this clear.


Replace sendMessage from WorkQueueReqMgr interface

This requires creating log db for reqmgr2 and put the error messages there. This db can be combined ops note. should prevent adding duplicate error messages over and over

Seangchan, I think I need a little bit more info on this subject. Please start explaining current system and give details where new DB should be created and what are access/retrieve patterns for messages. From RequestManager interface I see that message is created with given request, but I'm not sure which DB holds the data.

Hi Valentin, I am not completely sure what to do with this either. That is why assigned to you. :smile:
I was just thinking out some request related db which ops can comment as well as reporting request level (not job level) errors. We should discuss this sometime we can talk a little bit tomorrow meeting.
Thanks,

Seangchan, in order to design something I need to understand the requirements. Few initial questions: what is a volume of data, how it will be queried? Does messages will accompany every request? Will they be added at later time? Will data-ops search for messages/notes? How? Should messages/notes be kept forever?

closing and create more general requirement #5705

@ticoann , Seangchan, this issue is still marked as open even though you're closing it a year ago. Can you have a look and close it properly.


Suggestion to update Push Diary docs

Noticed the following: https://httpd.apache.org/docs/2.4/mod/mod_http2.html#h2pushdiarysize

The push diary records a digest (currently using a 64 bit number) of pushed resources (their URL) to avoid duplicate pushes on the same connection. These value are not persisted, so clients opening a new connection will experience known pushes again. There is ongoing work to enable a client to disclose a digest of the resources it already has, so the diary maybe initialized by the client on each connection setup.

Given cache digests has been dropped (and removed from mod_http2 should that last sentence be dropped as there now is no "ongoing work" AFAIK?

Thanks @tunetheweb  for catching this! Removed in r1897753 in Apache trunk and backported to 2.4.x branch.


Add 'Bitcoind' prefix to all bitcoind specific rpc stuff

Adds the Bitcoind prefix to all bitcoind specific Rpc stuff. In general, we should prefix what network/rpc server rpc stuff is specific for. I.e. EclairRpcClient for an eclair rpc client.

Good idea:-)
Relevant to my questions on formatting in Slack: The diff has some extra lines in it consisting of just imports moving around or being spread out/collapsed. In the ideal programming environment, every single character's position should be determined deterministically, and your diff would be even easier to inspect at a glance.

@torkelrogstad Yes, this is unfortunate at the moment. We are in between code formatting tools -- we are planning to move to scalafmt in #172. We've been waiting on some closed source stuff from another company that is going to be open sourced soon(TM) so we don't have a crazy amount of merge conflicts. But they are taking a long time. So maybe should just bite the bullet and merge 172.


Version inconsistency: sap.ui.core: "1.76.0" loads sap.m: "1.77.0"

OpenUI5 version: 1.76.0
Steps to reproduce the problem:

Load the OpenUI5 from https://openui5.hana.ondemand.com/resources/sap-ui-core.js
Open the Application Info in UI5 tool
Look at the loaded Libraries

What is the expected result?
The version of sap.ui.core should be equal to the version of sap.m.
What happens instead?
sap.ui.core: "1.76.0", while sap.m: "1.77.0":

Any other information? (attach screenshot if possible)
If I try to load OpenUI5 from the EU1 region https://openui5.eu1.hana.ondemand.com/resources/sap-ui-core.js, the version numbers are synchronized:

Such inconsistency leads to ICONTABHEADER_OVERFLOW_MORE error on a page.

If you get this with cleared caches, then there might be a problem with the AKAMAI caches again. I'll ask the colleagues to check this.

@codeworrior, I tried it on different browsers with a complete Ctrl+Shift+Delete cache cleaning up.

Thank you for the update. I've contact colleagues already...

Bingo. It works!

@codeworrior, one more question.
Why on ui5.sap.com I still see the version 1.76.1 as a default version:

While 1.77 has been already officially released:

Is it also an inconsistency issue?

Updating OpenUI5 is in our own hands, updating SAPUI5 (sapui5.hana.ondemand.com as well as ui5.sap.com) have to go through an internal process.


Window Icons. Fixes #548

Implements icons with an Icon class with platform implementations.  Also adds support for saving a bitmap to a stream and constructing an Icon from a stream.

Is this ready for review? I remember you mentioned adding the Icon class back in but that doesn't seem to be there right now. Regarding that: if you still think it's a I think I may be happer if it were called say ApplicationIcon - that way it makes it clear that it's a specialized icon rather than an icon

I'm willing to call it ApplicationIcon to clear up any confusion. I think I have a few things to clean up (like the merge conflict) and then it will be ready for review.

@grokys This is ready for code review.

I'm going to merge this with the small changes suggested inline.

Merged! Thanks @jkoritzinsky!


Adding method PATCH support

Is it possible to add support for HTTP method PATCH?
I really need it.

@MartijnSchoemaker Please refer to #334.


Testing addition of Legend initiatives

Build failed because of:
item Commodities Payout has an invalid repo https://gitlab.legend.finos.org/
item Product Control Common Template has an invalid repo https://gitlab.legend.finos.org/
item Commodities Reference Data has an invalid repo https://gitlab.legend.finos.org/
item Currency Reference Data has an invalid repo https://gitlab.legend.finos.org/

Build failed because of:
No cached entry, and Product Control Common Template has issues with logo: fo-product-control-common-template.svg, ENOENT: no such file or directory, open '/opt/build/repo/hosted_logos/fo-product-control-common-template.svg'
No cached entry, and Commodities Payout has issues with logo: fo-commodities-payout.svg, ENOENT: no such file or directory, open '/opt/build/repo/hosted_logos/fo-commodities-payout.svg'
Item Commodities Payout has no image_data
Item Product Control Common Template has no image_data

mergin on #92


Helpful correction in python script

In line 15 of the python script I would propose changing true into True, because otherwise you run into an syntax error if you change False against true. A simple-hearted as me made that experience ...

i also ran into this, thank you a lot! there should really be a heads up in README.md about this.

closed with 455134ab5d469534e35be0fb389da7239645a429


Adding openat2 header file under __NR_openat2 and UDIG ifdef code block

Signed-off-by: akulhar<EMAIL_ADDRESS>
What type of PR is this?
Fix for storage size of ‘how’ isn’t known compilation error

Uncomment one (or more) /kind <> lines:

/kind bug

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

@akulhar: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Hi @akulhar. Thanks for your PR.
I'm waiting for a falcosecurity member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: akulhar
To complete the pull request process, please assign leogr after the PR has been reviewed.
You can assign the PR to them by writing /assign @leogr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/assign @leogr

/ok-to-test
/cc @gnosek
/cc @FedeDP

@poiana Do I need to add release-note-label, let me know the process in case it is required?

@poiana Do I need to add release-note-label, let me know the process in case it is required?

No, you don't need to add it. NONE is ok in this case.
Btw, your PR SGTM, but I have to find the time to try it. Thank you!

/test build-libs-arm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: akulhar, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 9557e176eb9957aa7596b1158816c9482b13626f

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: akulhar, FedeDP, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Golang function deployments fail due "nodejs" runtime support removal by AWS

While deploying functions with "golang" runtime, AWS shows the following error:

apex deploy

Error: function helloGo: InvalidParameterValueException: The runtime parameter of nodejs is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs4.3) while creating or updating functions.
status code: 400, request id: 33f57c31-d3bb-11e6-8c58-f94bb7d2db37

This may be related to #578 .

macOS Sierra 10.12.2:
Apex version 0.11.0:

A simple change to plugins/golang/golang.go (line 32) fixes the problem for me. Please let me know if you would like a PR. Thanks.

PR here https://github.com/apex/apex/pull/637


Mixer client tests failed on Mixer TCP filter

Currently the Mixer client tests TestTCPMixerFilter and TestTCPMixerFilterPeriodicalReport fail frequently on prow. Both the test setup and Envoy side need investigation. Disable all the TestTCPMixer* tests.

cc @qiwzhang

@JimmyCYJ is this fixed by #5697 ? If yes, can you please close the issue?

@andraxylia Thanks for asking. That PR temporarily disables those tests, we will fix the tests and re-enable them. This issue is open for tracking tests failures, and we want to keep it open for now.

/assign @kyessenov

The root cause is that tests ping the same port for readiness, which pollutes the report batches.


DAL: postgres connections not being closed

noticed something interesting after building the code in the main branch: on every message sent in a channel that gort is in, a dangling connection is left open in postgres, eventually leading to the max_connections parameter being reached, which consequently causes gort to respond to every message in the channel with an error.
I think there are potentially two issues here:
the connections being left open is obviously one, and potentially the second being that we might not want gort automatically responding to DAL related errors in the chat service, this is quite noisy and a real nuisance to people not familiar with the bot itself.

I've identified the issue. A patch will be released today.

I've identified the issue. A patch will be released today.

It's taking longer than I hoped. The fix can be expected this weekend.

a dangling connection is left open in postgres, eventually leading to the max_connections parameter being reached, which consequently causes gort to respond to every message in the channel with an error.

I'm considering this to be the primary issue in this ticket. It's fixed by #208.

we might not want gort automatically responding to DAL related errors in the chat service

This is also true! Let's open a separate issue for this one

#208 is merged!


Possible bugs in the API

Bug report
V1.3.1
1- the locale is not working on the cart api
'/checkout/cart?token=true&locale=ku&currency=iqd'.
2- the search is not working for Kurdish or Arabic in the API
'/products?search=برنج&page=1&limit=10&locale=ku&currency=iqd'

Hi @Xoshbin,
Does this locale, you have created in your project?

Hi @devansh-webkul Yes I created Kurdish "ku" locale in my project, but the error is same for Arabic too.

Hi @Xoshbin,
Can you share some samples? So that I can verify this.

Sure the examples are below, since my default locale in my channel is Kurdish. so for both English and Arabic it's returning The Kurdish one.

At @Xoshbin,
OK, I am checking this with the Arabic locale.

Hi @Xoshbin,
After checking all the code, I came to the conclusion that this is because of the locale key. locale key is not found in the request because it is removed by the middleware i.e. your results fallback to the default locale.
https://github.com/bagisto/bagisto/blob/ee75f42c0248476a816d7d59bb3242471e0deec8/packages/Webkul/Shop/src/Http/Middleware/Locale.php#L48
If you want you can comment this, but right now I need to check this impact also. So not changing this.

Hi @devansh-webkul
Thanks for following it, anyway what about the search one:
2- the search is not working for Kurdish or Arabic in the API
'/products?search=برنج&page=1&limit=10&locale=ku&currency=iqd'

Hi @Xoshbin,
This is because maybe the locale key got removed and searching takes place on the en locale. I am just assuming I can give you a full explanation once this issue is fixed.

Hi @Xoshbin,
Actually, I just verified this with a team and this is the default behavior. Searching can only take place on the default locale. So if you want, you need to customize this at your end.

Hi @devansh-webkul
What do you mean by customizing it at my end, I'm adding the locale in the route when searching if you mean that.

I want to say that you cannot search by the locale key. You need to override the method from where searching takes place and then you need to create one more key in your overridden method and search by that.


Using self closing component named Svg breaks syntax highlighting

Repro:

Clone https://github.com/bgoscinski/volar-syntax-highlighting-repro.git
Open src/App.vue in vscode with Volar installed and uncomment 3rd line

+1 same problem here

it'll also break when svg tags are split across two lines:
<svg  ....>
  <some paths>
  <svg
><div ...>

Duplicate of #192


feat(connection): show sources and sinks referencing the connection

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

FEAT: in SHOW CONNECTIONS, display sources and sinks that reference the connection
FIX: in 'DROP SINK', decrease connection ref if sink references connection
TEST: add e2e tests for creating a sink with connection
Example:

Checklist For Contributors

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[x] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

[ ] I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation

[x] My PR DOES NOT contain user-facing changes.

👍 LGTM. BTW it should be a user-facing-changes feature, please add some details in the documentation and release note part.