HOTFIX: Revert KAFKA-10199 which is causing compilation failures

Compilation is failing after these two commits:
> Task :streams:compileJava
/Users/jgustafson/Projects/kafka/streams/src/main/java/org/apache/kafka/streams/processor/internals/TaskManager.java:852: error: cannot find symbol
                        tasks.addPendingTaskToClose(restoringTask.id());
                             ^
  symbol:   method addPendingTaskToClose(org.apache.kafka.streams.processor.TaskId)
  location: variable tasks of type org.apache.kafka.streams.processor.internals.Tasks
1 error

And:

[2022-08-17T20:58:20.912Z] > Task :streams:compileTestJava

[2022-08-17T20:58:20.912Z] /home/jenkins/jenkins-agent/workspace/Kafka_kafka-pr_PR-12530/streams/src/test/java/org/apache/kafka/streams/processor/internals/TaskManagerTest.java:822: error: method setupForRevocation(Set<Task>,Set<Task>) is already defined in class TaskManagerTest

[2022-08-17T20:58:20.912Z]     private TaskManager setupForRevocation(final Set<Task> tasksInStateUpdater,

This patch reverts them.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@ijuma Thanks. I built locally and confirmed that streams:compileJava and streams:compileTestJava were successful.


Environment Config file

Hi,
Thanks for your great work. May I ask the config file of the training environment, such as requirements.txt file.
Thank you!

Thank you for your interest.
The requirements.txt file has been added to the project. If you have any questions or issues, please don't hesitate to contact me.

You can try two approaches: 1) Switch to more cost-effective base models like Qwen, ChatGLM, etc. 2) Use third-party OpenAI API providers, which may offer discounts. Both options can help reduce evaluation costs.

You need to modify loss_type=sigmoid, and both learning rate and beta need to be re-tuned. Generally speaking, set beta=0.01 and learning rate=5e-7.

Is this error occurring after installation when executing the program? I haven't encountered a similar issue on my end. Perhaps you could try upgrading to a newer version of trl and see if that helps?

All our environments are consistent with SimPO. At that time, I used the latest version of alignment-handbook. I suspect the update to alignment-handbook caused compatibility issues with trl. Thanks for pointing this out; we'll try to verify this environment alignment issue again.
AlpacaEval is indeed an expensive evaluation method. Without funding, finding an alternative is certainly an option.

Which model base and dataset are you running? Can you check wandb to see if the training process is normal?

Here is the result on DPO with llama3-8b-instruct (llama-3-8b-instruct-V1-simpo-0910-dpo-sigmoid-ln-False-beta-0.01-gamma-0.0-raito-0.0-lr-1e-6)


Failed to obtain metrics. The metrics service may not be available. undefined

This issue is maybe related to #19700 but I am not sure since the prometheus-agent logs this:
INFO[2019-09-11T21:02:39Z] Start listening for connections on <IP_ADDRESS>:9090
I installed a cluster on Openstack using the node provider for Openstack and so I have to take considerations to the security group (firewall) settings but I can't find information in the docs that I have to open any extra network ports to get the (Rancher) monitoring to work, besides maybe the node exporter host port (9796)?
In the Rancher GUI I get the error message
"Failed to obtain metrics. The metrics service may not be available.
undefined"
There are multiple errors (probobly related to one another) in different pods in the cattle-prometheus namespace.
prometheus

level=error ts=2019-09-12T07:49:52.151067283Z caller=klog.go:94 component=k8s_client_runtime func=ErrorDepth msg="/app/discovery/kubernetes/kubernetes.go:301: Failed to list *v1.Service: services is forbidden: User \"system:serviceaccount:cattle-prometheus:cluster-monitoring\" cannot list resource \"services\" in API group \"\" in the namespace \"cattle-prometheus\""
level=error ts=2019-09-12T07:49:52.151261445Z caller=klog.go:94 component=k8s_client_runtime func=ErrorDepth msg="/app/discovery/kubernetes/kubernetes.go:302: Failed to list *v1.Pod: pods is forbidden: User \"system:serviceaccount:cattle-prometheus:cluster-monitoring\" cannot list resource \"pods\" in API group \"\" in the namespace \"cattle-logging\""
level=error ts=2019-09-12T07:49:52.151435448Z caller=klog.go:94 component=k8s_client_runtime func=ErrorDepth msg="/app/discovery/kubernetes/kubernetes.go:301: Failed to list *v1.Service: services is forbidden: User \"system:serviceaccount:cattle-prometheus:cluster-monitoring\" cannot list resource \"services\" in API group \"\" in the namespace \"cattle-logging\""
level=error ts=2019-09-12T07:49:52.151624923Z caller=klog.go:94 component=k8s_client_runtime func=ErrorDepth msg="/app/discovery/kubernetes/kubernetes.go:320: Failed to list *v1.Pod: pods is forbidden: User \"system:serviceaccount:cattle-prometheus:cluster-monitoring\" cannot list resource \"pods\" in API group \"\" in the namespace \"kube-system\""
level=error ts=2019-09-12T07:49:52.151786978Z caller=klog.go:94 component=k8s_client_runtime func=ErrorDepth msg="/app/discovery/kubernetes/kubernetes.go:301: Failed to list *v1.Service: services is forbidden: User \"system:serviceaccount:cattle-prometheus:cluster-monitoring\" cannot list resource \"services\" in API group \"\" in the namespace \"default\""
level=error ts=2019-09-12T07:49:52.15185182Z caller=klog.go:94 component=k8s_client_runtime func=ErrorDepth msg="/app/discovery/kubernetes/kubernetes.go:320: Failed to list *v1.Pod: pods is forbidden: User \"system:serviceaccount:cattle-prometheus:cluster-monitoring\" cannot list resource \"pods\" in API group \"\" in the namespace \"ingress-controller\""
level=error ts=2019-09-12T07:49:52.151963066Z caller=klog.go:94 component=k8s_client_runtime func=ErrorDepth msg="/app/discovery/kubernetes/kubernetes.go:300: Failed to list *v1.Endpoints: endpoints is forbidden: User \"system:serviceaccount:cattle-prometheus:cluster-monitoring\" cannot list resource \"endpoints\" in API group \"\" in the namespace \"cattle-logging\""
level=error ts=2019-09-12T07:49:52.152162792Z caller=klog.go:94 component=k8s_client_runtime func=ErrorDepth msg="/app/discovery/kubernetes/kubernetes.go:300: Failed to list *v1.Endpoints: endpoints is forbidden: User \"system:serviceaccount:cattle-prometheus:cluster-monitoring\" cannot list resource \"endpoints\" in API group \"\" in the namespace \"cattle-prometheus\""
level=error ts=2019-09-12T07:49:52.152188605Z caller=klog.go:94 component=k8s_client_runtime func=ErrorDepth msg="/app/discovery/kubernetes/kubernetes.go:302: Failed to list *v1.Pod: pods is forbidden: User \"system:serviceaccount:cattle-prometheus:cluster-monitoring\" cannot list resource \"pods\" in API group \"\" in the namespace \"default\""
level=error ts=2019-09-12T07:49:52.152372483Z caller=klog.go:94 component=k8s_client_runtime func=ErrorDepth msg="/app/discovery/kubernetes/kubernetes.go:300: Failed to list *v1.Endpoints: endpoints is forbidden: User \"system:serviceaccount:cattle-prometheus:cluster-monitoring\" cannot list resource \"endpoints\" in API group \"\" in the namespace \"default\""
level=error ts=2019-09-12T07:49:52.152399279Z caller=klog.go:94 component=k8s_client_runtime func=ErrorDepth msg="/app/discovery/kubernetes/kubernetes.go:302: Failed to list *v1.Pod: pods is forbidden: User \"system:serviceaccount:cattle-prometheus:cluster-monitoring\" cannot list resource \"pods\" in API group \"\" in the namespace \"cattle-prometheus\""
level=error ts=2019-09-12T07:49:52.152560331Z caller=klog.go:94 component=k8s_client_runtime func=ErrorDepth msg="/app/discovery/kubernetes/kubernetes.go:320: Failed to list *v1.Pod: pods is forbidden: User \"system:serviceaccount:cattle-prometheus:cluster-monitoring\" cannot list resource \"pods\" in API group \"\" in the namespace \"ingress-nginx\""

level=error ts=2019-09-12T07:50:06.272020763Z caller=klog.go:102 component=k8s_client_runtime func=Errorf msg="Unable to decode an event from the watch stream: http2: server sent GOAWAY and closed the connection; LastStreamID=71, ErrCode=NO_ERROR, debug=\"\""

level=error ts=2019-09-12T07:50:12.311594518Z caller=klog.go:94 component=k8s_client_runtime func=ErrorDepth msg="/app/discovery/kubernetes/kubernetes.go:300: Failed to list *v1.Endpoints: Get https://<IP_ADDRESS>:443/api/v1/namespaces/cattle-logging/endpoints?limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:443: connect: connection refused

prometheus-config-reloader
KUBECONFIG=openstack.conf k -n cattle-prometheus logs prometheus-cluster-monitoring-0 prometheus-config-reloader

level=error ts=2019-09-11T21:02:37.89739243Z caller=runutil.go:49 msg="function failed. Retrying in next tick" err="trigger reload: reload request failed: Post http://localhost:9090/-/reload: dial tcp <IP_ADDRESS>:9090: connect: connection refused"

prometheus-agent
Note: INFO[2019-09-11T21:02:39Z] Start listening for connections on <IP_ADDRESS>:9090
KUBECONFIG=openstack.conf k -n cattle-prometheus logs prometheus-cluster-monitoring-0 prometheus-agent

INFO[2019-09-11T21:02:39Z] Start listening for connections on <IP_ADDRESS>:9090

2019/09/11 21:02:40 http: proxy error: dial tcp <IP_ADDRESS>:9090: connect: connection refused
ERROR: logging before flag.Parse: W0912 03:32:36.367164       1 reflector.go:270] github.com/rancher/prometheus-auth/pkg/kube/namespaces.go:151: watch of *v1.Secret ended with: too old resource version: 141054 (144431)
ERROR: logging before flag.Parse: E0912 07:49:45.756778       1 streamwatcher.go:109] Unable to decode an event from the watch stream: http2: server sent GOAWAY and closed the connection; LastStreamID=343, ErrCode=NO_ERROR, debug=""

ERRO[2019-09-12T07:50:06Z] github.com/rancher/prometheus-auth/pkg/kube/namespaces.go:151: Failed to watch *v1.Secret: Get https://<IP_ADDRESS>:443/api/v1/secrets?resourceVersion=177223&timeoutSeconds=334&watch=true: dial tcp <IP_ADDRESS>:443: connect: connection refused
ERRO[2019-09-12T07:50:07Z] github.com/rancher/prometheus-auth/pkg/kube/namespaces.go:152: Failed to list *v1.Namespace: Get https://<IP_ADDRESS>:443/api/v1/namespaces?limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:443: connect: connection refused

exporter-node-cluster-monitoring-xxxx
KUBECONFIG=openstack.conf k -n cattle-prometheus logs exporter-node-cluster-monitoring-vj4rq

time="2019-09-12T13:28:45Z" level=error msg="ERROR: xfs collector failed after 0.103972s: failed to retrieve XFS stats: open /host/sys/fs/xfs/dm-21/stats/stats: no such file or directory" source="collector.go:132"
time="2019-09-12T15:35:45Z" level=error msg="ERROR: netclass collector failed after 0.114908s: could not get net class info: error obtaining net class info: could not access file operstate: no such device" source="collector.go:132"

grafana
KUBECONFIG=openstack.conf k -n cattle-prometheus logs grafana-cluster-monitoring-576c5d879f-5ntxs grafana

2019/09/13 07:20:46 http: proxy error: dial tcp <IP_ADDRESS>:9090: i/o timeout

Namespace: kube-system
metrics-server-xxxxxxxx
KUBECONFIG=openstack.conf k -n kube-system logs metrics-server-7f6bd4c888-zjnzt

E0912 07:50:13.306805       1 reflector.go:205] github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/client-go/informers/factory.go:130: Failed to list *v1.Node: Get https://<IP_ADDRESS>:443/api/v1/nodes?limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:443: connect: connection refused

Hi @caleno not sure if you use the hardening guide for rancher, but the log line that says the service account for cluster-monitoring is forbidden from listing services seems interesting. If you havent ran through the hardening guide, you might want to delete the service account token for cattle-prometheus and delete the pod to have it recreate both the service account token and the pod... let me know if that helps the prometheus pod progress.


allow gpgkey to be configured and use 2023 key by default

Description

Add gpgkey property to repo resource
Default to 2023 GPG key

Issues Resolved
Resolves #57
Check List

[x] A summary of changes made is included in the CHANGELOG under ## Unreleased
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable.

Released as: 5.4.0


Add sleep in iterator example to see bars

I've added the sleep to be able to see the bars when I run the example. They were very quickly done without a sleep.

Makes sense, thanks!


Small view fixes

On the "quick adjustment" page, present users get the orange background
Displays a card next to the names of those who have added their mecenat card number (in the admin/user and admin/vote_user list)
Changing some font sizes (I think the titles on the front page are too large)
Other small changes

+1


expose texture/image conversions as From/TryFrom

fixes #2169
Instead of having custom methods with reduced visibility, implement From<image::DynamicImage> for Texture and TryFrom<Texture> for image::DynamicImage

Love it!

bors r+


Persist all peers and make peer manager abstracted

Gonna need to do this for all the structures being saved onto the node so we can test things better on our node implementation. I'll do those in separate PR's just like this if it's okay.
Need to do this in order to test the thing I was changing originally.

Fixes https://github.com/BitcoinDevShop/mutiny-web-poc/issues/305


sinkv2 throughout drops in some cases

Before asking a question, make sure you have

[X] Searched existing Stack Overflow questions
[X] Googled your question
[X] Searched open and closed GitHub issues
[X] Read the documentation

What is your question?
In sinkv1 there is a sinkFlushInterval (by default 50ms). In sinkv2 the parameter is removed because it increases throughout in some cases. For example:
SinkV1:

SinkV2:

But later we found that in some other cases sinkv2 throughout drops:
SinkV1:

SinkV2:

In case 1, sinkv2 is better than sinkv1 because it doesn't waste 50ms to collect batch. But in case 2, sink1 is better because it spends some time to collect batch and really gets a larger batch.
It shows we need to do some tunes for the parameter.

/severity Major

When running case cdc_owner_switch_truncate_sync, we found that changefeed lag is much longer when cdc configuration debug.enable-new-sink is true (default setting for v6.3.0)

debug.enable-new-sink = true ( default), it takes ~ 50m to catch up upstream.

debug.enable-new-sink = false , it takes  ~30m to catch up with upstream


Distinguish between local and remote history frames in router.goBack()

This is sort of a continuation of #408, which was resolved before 1.0 but then basically un-resolved again later.
The core problem case is the following: Users visiting a page in an application might come there either from inside the application or from an external communication channel, possibly also a web app, that might live in the same browser history. When using browserHistory one is unable to distinguish between the two, so that a button triggering router.goBack() may lead outside the app, which is unwanted behaviour in many cases.
Ideally, there would be a router.peek() or router.canGoBack() etc. that can tell whether a consecutive router.goBack() would trigger a page unload or a router transition that can be used for example to hide "go back" navigation from the end user.
A partial solution would be to at least let the developer decide whether router.goBack should lead outside the domain (optional boolean argument indicating whether it should be left or trigger no action, boolean return value indicating whether a transition was triggered or not).

Please follow up on https://github.com/mjackson/history/issues/26 and related issues on history – these methods are proxied from the underlying history, and the routing logic does not manage the navigation.


deepin.deepin-gtk-theme: 17.10.9 -> 17.10.10

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/deepin-gtk-theme/versions.
meta.description for deepin.deepin-gtk-theme is: '"Deepin GTK Theme"'.
Compare changes on GitHub

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

directory tree listing: https://gist.github.com/e71cb0d01ab9577a069ff3ec530036c7

du listing: https://gist.github.com/44c8ae3525a0e59fb11b83a7c8de84ee

Outpath report (click to expand)

Outpath difference report
13 total rebuild paths
4 package rebuilds
4 x86_64-linux rebuilds
4 i686-linux rebuilds
1 x86_64-darwin rebuilds
4 aarch64-linux rebuilds
First ten rebuilds by attrpath
deepin.deepin-desktop-schemas
deepin.deepin-gtk-theme
deepin.deepin-metacity
deepin.deepin-wm

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4arsjnj2zd6fp8djqi6d4r7bkz34krp2-deepin-gtk-theme-17.10.10 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A deepin.deepin-gtk-theme https://github.com/r-ryantm/nixpkgs/archive/e90177421bd53f15d1318eaf7de53499cd07e4c2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4arsjnj2zd6fp8djqi6d4r7bkz34krp2-deepin-gtk-theme-17.10.10
ls -la /nix/store/4arsjnj2zd6fp8djqi6d4r7bkz34krp2-deepin-gtk-theme-17.10.10/bin

cc @romildo for testing.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: deepin.deepin-gtk-theme
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: deepin.deepin-gtk-theme
Partial log (click to expand)
install flags: SHELL=/nix/store/dsyc1z7ck08ga7l0b1jcxx35wj69qcii-bash-4.4-p23/bin/bash PREFIX=\$\(out\) install
mkdir -p /nix/store/zadh640vqailldyfsqprrl3x5vdzhm3a-deepin-gtk-theme-17.10.10/share/themes
cp -r deepin /nix/store/zadh640vqailldyfsqprrl3x5vdzhm3a-deepin-gtk-theme-17.10.10/share/themes/
cp -r deepin-dark /nix/store/zadh640vqailldyfsqprrl3x5vdzhm3a-deepin-gtk-theme-17.10.10/share/themes/
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/zadh640vqailldyfsqprrl3x5vdzhm3a-deepin-gtk-theme-17.10.10
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/zadh640vqailldyfsqprrl3x5vdzhm3a-deepin-gtk-theme-17.10.10
checking for references to /build in /nix/store/zadh640vqailldyfsqprrl3x5vdzhm3a-deepin-gtk-theme-17.10.10...
/nix/store/zadh640vqailldyfsqprrl3x5vdzhm3a-deepin-gtk-theme-17.10.10

Success on x86_64-linux (full log)
Attempted: deepin.deepin-gtk-theme
Partial log (click to expand)
install flags: SHELL=/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/bash PREFIX=\$\(out\) install
mkdir -p /nix/store/4arsjnj2zd6fp8djqi6d4r7bkz34krp2-deepin-gtk-theme-17.10.10/share/themes
cp -r deepin /nix/store/4arsjnj2zd6fp8djqi6d4r7bkz34krp2-deepin-gtk-theme-17.10.10/share/themes/
cp -r deepin-dark /nix/store/4arsjnj2zd6fp8djqi6d4r7bkz34krp2-deepin-gtk-theme-17.10.10/share/themes/
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/4arsjnj2zd6fp8djqi6d4r7bkz34krp2-deepin-gtk-theme-17.10.10
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/4arsjnj2zd6fp8djqi6d4r7bkz34krp2-deepin-gtk-theme-17.10.10
checking for references to /build in /nix/store/4arsjnj2zd6fp8djqi6d4r7bkz34krp2-deepin-gtk-theme-17.10.10...
/nix/store/4arsjnj2zd6fp8djqi6d4r7bkz34krp2-deepin-gtk-theme-17.10.10

duplicate of https://github.com/NixOS/nixpkgs/pull/49499


Add a logo

We need a logo, here's an idea for starters, modifications of it and other artwork gratefully received:

Acceptance Criteria

Logo is added

Actually that doesn't look great on dark background, maybe this?

For reference here is the ophyd logo

@graeme-winter suggested losing the black beak:

where would the logo live @coretl ? I think github displays those only for orgs.
the ophyd-async logo is nice, and differs depending on the light/dark theme
what if we just add the beak without the back of the skull? the dodo-outline is still visible, or the beak could be smaller to be proportionate
https://blueskyproject.io/ophyd-async/main/index.html

where would the logo live @coretl ? I think github displays those only for orgs.

on the docs

what if we just add the beak without the back of the skull? the dodo-outline is still visible, or the beak could be smaller to be proportionate

sounds fine to me, I won't get round to it, but if someone else fancies playing around with inkscape then that would be good


Embedding fails - Not able to add documents

When I try to add documents, I get the error down below.
I installed Verba in a conda environment with pip. I am able to run llama3 and gpt4, but am not able to add documents.
(INFO) Importing...
(ERROR) Delete object! Unexpected status code: 500, with response body: {'error': [{'message': 'could not delete object from vector repo: delete from index "verba_config": delete local object: shard="x8U9x6HOhDpr": store is read-only'}]}.

I just got the same error, solved by running Verba from a new directory with permissions 777. Something like:
mkdir test
cp .env test
cd test
chmod 777 .
verba run

Interesting! Thanks for the issue, we'll have a look

Same.
I'm not sure if it's related, but I'm also getting this message: {"action":"read_disk_use","level":"warning","msg":"disk usage currently at 86.36%, threshold set to 80.00%"

Same here issue here.
Apple M2 Pro
MacOS Sonoma 14.5
Python 3.12.3

One way to solve it is run using Docker

I have confirmed that this issue is affected by several factors:

Project Folder Permissions: Ensure that the repository folder has the proper permissions before running verba start. Incorrect permissions can cause various issues.
Available Disk Space: Ensure that your disk space is below the threshold. If the disk is nearly full, the system may automatically switch to a read-only mode, which can lead to errors.
Environment Variables: Make sure that the environment variables OLLAMA_URL and OLLAMA_MODEL are set. You can find an example of these in the .env.example file.

Here are the errors I encountered:

flush halted due to shard READONLY status
could not delete object from vector repo: delete from index "verba_config": delete local object: shard="ifrwh8eZAyOJ": store is read-only
update vector: API Key: no api key found neither in request header: X-Openai-Api-Key nor in environment variable

The "store is read-only" error was misleading in my case because my disk was 98% full. and I was getting this error: Set READONLY, disk usage currently at 93.20%, threshold set to 90.00%
You can check the actual disk availability using the command df -h. After reducing the disk usage to below the threshold, everything worked fine:
I hope this helps in resolving the issue.


Fix extra-deps

Unfortunately, the versions of packages specified as extra-deps in the stack file in the previous pull  request do not properly point to the updated packages since none of the new package versinos have been uploaded to hackage yet.
This PR properly points to the commit hashes that include the dependency bounds fixes in the dependencies for this package.

I'm not sure of the policy on pointing to git commits, but until the packages get into a reproducible build plan, this is kind of the best we can do.
You will notice the CI failures on the last PR merged that "fixed" these deps; I think this PR will build clean.

Well then... any tips on getting this to pass CI? It builds properly on my machine, and all the tests pass... however, none of the CI builds pass.

@tdietert I've pushed, it worked locally for me. If it passes CI, I'll bump revision and push that to hackage as well.

woot :tada:
awesome, thanks!

You welcome! I think I'll not add back older versions unless it will be requested or there is a demand from people using those versions in it's own installations. As that would require a lot of maintenance burden. When 8.6 will out, I'll keep support for 8.4 though.


Why there is longer time to execute initial epoch while very less and uniform time to execute later epochs

Please make sure that the boxes below are checked before you submit your issue. If your issue is an implementation question, please ask your question on StackOverflow or join the Keras Slack channel and ask there instead of filing a GitHub issue.
Thank you!

[x] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/keras-team/keras.git --upgrade --no-deps

[x] If running on TensorFlow, check that you are up-to-date with the latest version. The installation instructions can be found here.

[ ] If running on Theano, check that you are up-to-date with the master branch of Theano. You can update with:
pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps

[ ] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

I have a doubt regarding the execution time of initial epochs in Keras. When I had started executing the InceptionV3 model on P100 GPU I see some strange behavior of execution never seen before. Therefore I am curious to know why this type of behavior occurs.

@deeppatel4557  Moving this issue to closed status as there has been no recent activity, in case you still face the error please create a new issue.Thanks!


how can I install specific version?

Currently, the instructions don't explain how to install a specific version of the package. I need to install version 1.1.0, for example. Please, update the instructions, if possible.

@deemp please, help

@yegor256, specify the version after the package name.
Example: stack install --resolver lts-22.16 eo-phi-normalizer-1.1.0
I agree that we should update the documentation.

This command is documented now here.
@yegor256, please close this issue if you don't have any further questions.


passing test fails if run in Windows on GH actions

I have a set of tests I run with pytest in my Windows build in on GH Actions.
I originally wrote this up as a pytest issue:
https://github.com/pytest-dev/pytest/discussions/9321
you can see some discussion there about the perspective from pytest.
but now it looks like it's a flaky issue since if I skip the test that's been marked with flaky, then the test passes.
from that issue above, the stdout for my pytest looks like this:
============================= test session starts =============================
platform win32 -- Python 3.8.10, pytest-6.2.5, py-1.11.0, pluggy-1.0.0
***dir: D:\a\<snip>
plugins: anyio-3.3.4, flaky-3.7.0, asyncio-0.16.0, mock-3.6.1, timeout-2.0.1
collected 32 items

test\test_utils.py ..                                                    [  6%]
test\test_client.py ......ss..ss..sss............s                       [100%]

============================== warnings summary ===============================
c:\hostedtoolcache\windows\python\3.8.10\x64\lib\site-packages\stringcase-1.2.0-py3.8.egg\stringcase.py:247
c:\hostedtoolcache\windows\python\3.8.10\x64\lib\site-packages\stringcase-1.2.0-py3.8.egg\stringcase.py:247
  c:\hostedtoolcache\windows\python\3.8.10\x64\lib\site-packages\stringcase-1.2.0-py3.8.egg\stringcase.py:247: DeprecationWarning: invalid escape sequence \W

<snip>

-- Docs: https://docs.pytest.org/en/stable/warnings.html
===Flaky Test Report===

test_cancel[Signals.CTRL_C_EVENT] passed 1 out of the required 1 times. Success!

===End Flaky Test Report===
=========================== short test summary info ===========================
SKIPPED [8] test\conftest.py:146: Set DUMMY_JCS to the name of an available JCS to test
============ 24 passed, 8 skipped, 6 warnings in 447.29s (0:07:27) ============
Error: Process completed with exit code 1.

I don't know how to solve this issue, so I just skipped it:
    if sys.platform == "win32":
        pytest.skip("this test doesn't work on GH actions on Windows?")


workflow_main/analyses/scripts/surveillance.py Not Filtering on surv_start_date

In development, workflow_main/analyses/scripts/surveillance.py is outputting a dataframe without taking surv_start_date into account. surv_start_date should override any other start date argument

Closing this issue; the workflow processing is working as intended. The surv_start_date provided in the config that opened this issue was improperly formatted (MM/DD/YYYY) which resulted in all data being included in the dataframe. Surv_start_date (and all dates) should be formatted as YYYY/MM/DD.


Markdown lexer

I am parsing and beautifying markdown in my biddle project.  I need to extract the parser and put it in a lexer file for this project.

This is largely complete.  I have validated most concerns and am in the final stages of validating edge cases.
Todo:

Finish validation of known edge cases.
Write test units
Pass validation build


python311Packages.pytoolconfig: 1.2.5 -> 1.2.6

Diff: https://github.com/bagel897/pytoolconfig/compare/refs/tags/v1.2.5...v1.2.6
Changelog: https://github.com/bagel897/pytoolconfig/releases/tag/v1.2.6
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.


global copy of phantomjs not found in 1.0.4

Hi!
Version 1.0.4 doesn't work with a global install of phantomjs.
Here is a short log of the npm install:
<EMAIL_ADDRESS>install D:\a\1\s\node_modules\phantomjs-prebuilt
node install.js

Considering PhantomJS found at C:\NPM\Modules\phantomjs.CMD
C:\NPM\Modules\phantomjs.CMD ...verifying
Writing location.js file
PhantomJS is already installed on PATH at C:\NPM\Modules\phantomjs.CMD

As is see you take phantomPackage._location (/phantomjs-prebuilt) instead of /phantomjs.
The provided CMD file points to the EXE file, but not necessary in your hardcoded folder.
It is unsafe to locate the EXE based from the CMD path.
The build-server (VSTS) was setup with your old path to the EXE, to workaround this problem.
Now all VSTS build with karma-phantomjs-launcher are broken.
I haven't a solution for this...rollback the to version 1.0.2 or start phantomjs via CMD.
:-(
Silvio

VSTS is Visual Studio Team Services

This was a problem for me as well. Ate up a couple days of my time. I also had to roll back to version 1.0.2 in order to get my VSTS builds working again. The only way I was able to figure it out was to diff the exact versions of the NPM modules installed between a passing build and a failing build.
I'm a little surprised that there wasn't more specific / useful error information about this with the logging set to DEBUG. Here are the relevant logs from my VSTS build when this failed:
DEBUG [config]: Loading config C:\a\1\s\...\karma.conf.js
DEBUG [plugin]: Loading karma-* from C:\a\1\s\...\node_modules
DEBUG [plugin]: Loading plugin C:\a\1\s\...\node_modules/karma-jasmine.
DEBUG [plugin]: Loading plugin C:\a\1\s\...\node_modules/karma-phantomjs-launcher.
DEBUG [plugin]: Loading plugin C:\a\1\s\...\node_modules/karma-spec-reporter.
DEBUG [web-server]: Instantiating middleware
DEBUG [reporter]: Trying to load reporter: spec
DEBUG [reporter]: Trying to load color-version of reporter: spec (spec_color)
DEBUG [reporter]: Couldn't load color-version.
INFO [karma]: Karma v1.5.0 server started at http://<IP_ADDRESS>:9876/
INFO [launcher]: Launching browser PhantomJS with unlimited concurrency
INFO [launcher]: Starting browser PhantomJS
DEBUG [temp-dir]: Creating temp dir at C:\Users\BUILDG~1\AppData\Local\Temp\karma-68217745
DEBUG [launcher]: C:\NPM\Modules\node_modules\phantomjs-prebuilt\lib\phantom\bin\phantomjs C:\Users\BUILDG~1\AppData\Local\Temp\karma-68217745/capture.js
WARN [launcher]: PhantomJS have not captured in 60000 ms, killing.
WARN [launcher]: PhantomJS was not killed in 2000 ms, sending SIGKILL.
WARN [launcher]: PhantomJS was not killed by SIGKILL in 2000 ms, continuing.
DEBUG [launcher]: Process PhantomJS exited with code -1
DEBUG [temp-dir]: Cleaning temp dir C:\Users\BUILDG~1\AppData\Local\Temp\karma-68217745
DEBUG [launcher]: PhantomJS failed (timeout). Not restarting.
DEBUG [karma]: Run complete, exiting.
DEBUG [launcher]: Disconnecting all browsers

@silvioboehme I was coming across this same issue and found that if I change the Default Agent Queue in the Options section of my build that the Karma unit tests start working again. Not sure if that is an Option for you but the new VS2017 build host doesn't seem to have this same issue -

@BrianMikinski Thank you for this tip.
I have changed all my agents to "Hosted 2017" because we need this for our VS2017 backend.
Now Karma-phantomjs-launcher 1.0.4 works fine.
The difference is, that the "Hosted 2017" Agent doesn't have phantomjs preinstalled.
On this agent phantomjs prebuild is downloaded in the npm install step.
I hope it stays that way.


Remove core_extensions from mail when running Ruby > 2.0

This PR removes all of the remaining core_extensions from mail, excluding backports from newer versions of Ruby. Each commit in this series removes a specific extension. I thought this would be easier to review as a series of commits than as a series of totally separate PRs but happy to switch.

Thanks @metcalf!!

Thank you! Very excited to 💥 these monkeypatches from our codebase.
Would you be willing to cut a release that includes this? If not I can cut one on our internal gem server but it's always nice to keep consistent with public releases.

They'll be included in the upcoming 2.7.0 minor release. I'd rather not do these removals in a 2.6.x point release.

Ok, thanks!
On Sat, May 6, 2017 at 9:27 AM Jeremy Daer<EMAIL_ADDRESS>wrote:

They'll be included in the upcoming 2.7.0 minor release
https://github.com/mikel/mail/milestone/5. I'd rather not do these
removals in a 2.6.x point release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mikel/mail/pull/1095#issuecomment-299650756, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AABBTKOD0zQOY0gB2F8CSTEAndcDvPxZks5r3J9-gaJpZM4NRCQT
.


Presentation 1 - Overview/project description - Short-term goals (learning databricks)

If you are done, close this issue when you get a chance


Cleanup temp files

Thank you @ederign !

@agilepro This PR removes all the temp files that I committed by mistake. Feel free to merge it.


Camaleon CMS in Rails 5, adding a new post the form disappear when updating the category

Hello anyone encounter this bug or weird behavior? i created a custom group/field everything was setup according to my required design but my problem is when i create a new post and select the category the custom fields disappear
Please see the video below
https://screencast.com/t/ZRBabKAnZvGb
GEMS
camaleon_cms = <IP_ADDRESS>
ruby = 2.5.1
rails = 5.2.1
THANK YOU and MORE POWER 👍

up

Fixed <IP_ADDRESS>!
Thanks for reporting


fix: added retry logic to fix sometimes cannot get pages immediately

Coverage decreased (-0.2%) to 14.019% when pulling 7d63295fb1ca9d47208f7238ceb139539b93c3c5 on bugfix/cannot-find-webview-pages into 5f3a3f4e5f13cc156fb1533c85013cb73b067308 on master.

+1


minimal-bootstrap.tinycc-musl: init at 0.9.27

Description of changes

Works towards replacing glibc-2.2 in the bootstrap chain. musl should also let tinycc bootstrap gcc4.7, skipping gcc2 as well.
I've chosen not to reuse the existing tinycc build helpers as they are somewhat coupled with meslibc. Stylistically I've been thinking it might be preferable to start using less abstractions for simpler code and better readability at the cost of some duplication.
Related #227914
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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/)
23.11 Release Notes (or backporting 23.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.

I think we can deduplicate them without things going crazy? Willing do to this for now to keep you unblocked but I think we can have abstractions that work.

In particular this is not taking advantage of the compiler vs libs split, instead doing some ad-hoc boostrapping within the package. We should distinguish tcc using musl from tcc built with musl, and then the compiler vs libs split will help here not feel like an extra hoop to jump throuhg.

Sounds good to me :+1: I'll do some homework on how the compiler and libs split and slot together

Would this be ok to merge? @Ericson2314


Holographic items do not work with lines below them.

Had a hologram with an item on it and then I added a new line and it got deleted

Sorry, wrong plugin


Patch up how we launch the beacon node with respect to genesis

What is wrong?
Refer this: https://github.com/ethereum/trinity/blob/master/trinity/config.py#L619
You'll see a genesis state/block are hardcoded into the config here.
We will need to assemble them from some genesis_data (shape TBD :)) just how it is handled in the eth1.0 chain.
How can it be fixed
An easy thing for now would be:
# build the `genesis_state` you want, and then the `genesis_block` from that.
genesis_data = (genesis_state, genesis_block)
config = BeaconChainConfig(
  genesis_data,
  # ... the rest of the arguments we want
)

# inside BeaconChainConfig.initialize_chain
def initialize_chain(self, base_db):
  gensis_state, genesis_block = self.genesis_data
  return cast('BeaconChain', self.beacon_chain_class.from_genesis(
    base_db=base_db,
    genesis_state=genesis_state,
    genesis_block=genesis_block,
  ))

This may already be in the pipeline in some of the work to get a runnable beacon node in which case we can just close this issue :)

Currently I'm trying to do in #517 is to create all Deposit in a directory. Then reuse the testnet command to create genesis state from those Deposits.


Uncaught TypeError in formbuilder.

Hello,
I'm trying to setup the project so i can run it locally.
I want to add a PageHeader component and modify the 'is' function or add a 'contains' function, to make it possible to check if a mult-select contains an option.
E.g., If the multi-select contains the option 'Other' i want a textfield to be shown.
However, i can't seem to get the project running locally.
When navigating to the formbuilder i get the following error:
Uncaught TypeError: t is not a function
Field.js:181 Uncaught TypeError: t is not a function
at t.value (Field.js:181)
at finishClassComponent (react-dom.development.js:13085)
at updateClassComponent (react-dom.development.js:13047)
at beginWork (react-dom.development.js:13715)
at performUnitOfWork (react-dom.development.js:15741)
at workLoop (react-dom.development.js:15780)
at HTMLUnknownElement.callCallback (react-dom.development.js:100)
at Object.invokeGuardedCallbackDev (react-dom.development.js:138)
at invokeGuardedCallback (react-dom.development.js:187)
at replayUnitOfWork (react-dom.development.js:15194)
The error seems to originate from<EMAIL_ADDRESS>Here are the steps which i have taken:

Downloaded source
Open folder in visual studio code
Run 'lerna bootstrap'
Navigate to 'packages\core'
'yarn run build'
Navigate to 'packages\atlaskit
'yarn run build'
Navigate to 'packages\formbuilder'
'yarn run build'
Navigate to 'packages\material-ui'
'yarn run build'
Navigate to 'packages\examples'
'yarn run start'
Open localhost:3001
Naviage to 'Formbuilder'

Produces the above exception.
Am i missing something?
Kind regards,
Jaap

Hi,
Thanks for raising this issue. I just ran through the steps I usually take:

yarn install
yarn bootstrap
yarn build
navigate to packages/examples
yarn start
Open browser at http://localhost:3001/

I've tested and it does appear to work fine for me. Can you try again following the steps I've used please?
Regards,
Dave

Hi Dave,
Sadly it is not working yet.
Here is what i did:
I've redownloaded the code and extracted it.
I've navigated to the root of the folder (with the lerna.json file in it).
Ran: yarn install (from CMD)
Ran: yarn bootrap
Ran: yarn build
The build command gives me the following error:
14 error build Errored while running script in 'react-forms-processor'
15 error execute callback with error
16 error Error: Command failed: yarn run build
16 error error Command failed with exit code 1.
16 error error Command failed with exit code 1.
16 error $ webpack --mode production
16 error Hash: 07beefdde2ad4163cda7
16 error Version: webpack 4.8.1
16 error Time: 9226ms
16 error Built at: 2019-07-01 20:52:49
16 error        Asset      Size  Chunks             Chunk Names
16 error     index.js  51.1 KiB       0  [emitted]  index
16 error index.js.map   215 KiB       0  [emitted]  index
16 error Entrypoint index = index.js index.js.map
16 error   [3] external "react" 42 bytes {0} [built]
16 error  [13] ./src/utilities/utils.js 19.1 KiB {0} [built]
16 error  [22] (webpack)/buildin/module.js 519 bytes {0} [built]
16 error  [35] ./src/renderer.js 7.67 KiB {0} [built]
16 error  [37] ./src/utilities/validation.js 13.3 KiB {0} [built]
16 error [104] (webpack)/buildin/global.js 509 bytes {0} [built]
16 error [120] ./src/index.js 1.18 KiB {0} [built]
16 error     + 114 hidden modules
16 error $ yarn build:flow
16 error $ ../../node_modules/flow-copy-source/bin/flow-copy-source.js --verbose --ignore '**/*{story,test}.js' src dist
16 error info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
16 error info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
16 error
16 error     at E:\react-forms-processor-master\node_modules\lerna\node_modules\execa\index.js:236:11
Any idea what could be wrong?
Kind regards,
Jaap

Investigated a bit further.
When i remove the below lines from the packages.json file located under the core folder the build is successful!
"postbuild": "yarn build:flow",
"build:flow": "../../node_modules/flow-copy-source/bin/flow-copy-source.js --verbose --ignore '**/*{story,test}.js' src dist"

I can also run the formbuilder example.
When running the postbuild command manually from the core folder i also get a windows script host error:

Besides that everything seems to run OK now.

Sorry it's taken a few days to get back to you. I don't use Windows for development so I'm assuming the problems you're facing might be environment based. If everything seems to me working as you say I'm going to close this issue.


Deepspeed zero3 + LoRA: RuntimeError: Only Tensors of floating point and complex dtype can require gradients

Please check that this issue hasn't been reported before.

[X] I searched previous Bug Reports didn't find any similar reports.

Expected Behavior
I expect deepspeed zero3 and 8-bit LoRA to be compatible and runs without error
Current behaviour
When loading model with deepspeed zero3 and 8-bit LoRA enabled, I ran into the error RuntimeError: Only Tensors of floating point and complex dtype can require gradients :

However, if you use zero3 in tandem with 4-bit qLoRA, or just do full fine-tuning with zero3 enabled, it works fine.
Steps to reproduce

Set up LoRA
enable deepspeed zero3
RuntimeError: Only Tensors of floating point and complex dtype can require gradients

Config yaml
base_model: NousResearch/Meta-Llama-3-8B
model_type: LlamaForCausalLM
tokenizer_type: AutoTokenizer

load_in_8bit: true
load_in_4bit: false
strict: false

datasets:
  - path: mhenrichsen/alpaca_2k_test
    type: alpaca
dataset_prepared_path:
val_set_size: 0
output_dir: ./outputs/lora-out

sequence_len: 4096
sample_packing: true
eval_sample_packing: true
pad_to_sequence_len: true

adapter: lora
lora_model_dir:
lora_r: 32
lora_alpha: 16
lora_dropout: 0.05
lora_target_linear: true
lora_fan_in_fan_out:
lora_modules_to_save:
  - embed_tokens
  - lm_head

wandb_project:
wandb_entity:
wandb_watch:
wandb_name:
wandb_log_model:

gradient_accumulation_steps: 4
micro_batch_size: 2
num_epochs: 4
optimizer: adamw_bnb_8bit
lr_scheduler: cosine
learning_rate: 0.0002

train_on_inputs: false
group_by_length: false
bf16: auto
fp16:
tf32: false

gradient_checkpointing: true
early_stopping_patience:
resume_from_checkpoint:
local_rank:
logging_steps: 1
xformers_attention:
flash_attention: true
s2_attention:

warmup_steps: 10
evals_per_epoch: 4
eval_table_size:
eval_max_new_tokens: 128
saves_per_epoch: 1
debug:
deepspeed: deepspeed_configs/zero3_bf16.json
weight_decay: 0.0
fsdp:
fsdp_config:
special_tokens:
   pad_token: <|end_of_text|>

Possible solution
(Putting on a tinfoil hat) I think it's a bug within axolotl code base as opposed to some deeper issue with deepspeed zero3, seeing as it works with qlora.
Which Operating Systems are you using?

[X] Linux
[ ] macOS
[ ] Windows

Python Version
3.11.10
axolotl branch-commit
main
Acknowledgements

[X] My issue title is concise, descriptive, and in title casing.
[X] I have searched the existing issues to make sure this bug has not been reported yet.
[X] I am using the latest version of axolotl.
[X] I have provided enough information for the maintainers to reproduce and diagnose the issue.

this is being worked on via PR#1852 and https://github.com/huggingface/transformers/pull/32943


[Feature] Don't display the content of the properties file in Concourse log view when collapsed

Hello,
Great work on this Concourse resource!
I just have one (I hope) small feature request: When one press on a job and look at its output, steps using this resource are outputting the whole content of the properties file. This floods to display with not so important data and it's hard to follow the rest of the steps. Is is possible to change keyval-resource to only show UPDATED and UUID fields when collapesed, and show the content of the properties file when expanded?

Uh, I checked the code. The whole resource-type is a hackish one, that encodes the jproperties file into VERSION string. So, what I'm asking is imposible. Closing the issue.


feat(ONYX-529): create new alert modal, add sticky modal headers and refactor

The type of this PR is: TYPE

This PR solves ONYX-549
Description
New Modal for alerts: sticky header with titles of each Step and sticky footer for Filters.
https://github.com/artsy/force/assets/17580625/5d724ca5-bc56-4410-97bc-d5f8dc316d47

Thank you!
@tam-kis I see we don't have the "Clear All" button on the Filters step any more. Was this change intentional?


Change back to spot instances

You can now start and stop spot instances:
https://aws.amazon.com/about-aws/whats-new/2017/09/amazon-ec2-spot-can-now-stop-and-start-your-spot-instances/

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Done.


any good idea for store something from handshake?

When the connection is authorized, we need to store something into client context, but in current interface, we can't do that directly. I can put something into handshake data, and indirect get it from client context. but there is no unity storage into client store with client session.

Why don't you apply addListeners.
@OnConnect
public void onConnect(SocketIOClient client) {
...
client.set("K", V); // put something data
...
}


[mask_rom] Add documentation for Memory Protection module

This documents the mask ROM's Memory Protection module which is
responsible for using Ibex's Enhanced Physical Memory Protection
(ePMP) feature to prevent the execution of unverified code.
Note that this module was originally part of the 'Lockdown' module
however since the 'Lockdown' module has evolved to solely specify
the memory protection scheme it has been renamed to more accurately
reflect its purpose.

Hi @mundaym, is it ok if we mark this as ready for review?

Hi @mundaym, is it ok if we mark this as ready for review?

Done.


Licensing

Hi ojacques,
Have found this module very helpful. However, I noticed that you do not have any licensing in place and was wondering if you would be willing to make your intentions clear in that respect. Thanks in advance for considering this.

Thanks @zerowon01 . I added the license - Apache v2.

Thank you very much.


[FLINK-1576] [gelly] improvements to the gelly examples.

Updated GraphMetrics, MusicProfiles and PageRank to run with and without parameters.
Added input descriptions to LabelPropagation and SSSP.
Fixed some minor issues in the SSSP example.
Fixed a bug in MusicProfiles that wasn't generating the user-user graph properly.
Changed the PageRank library method to initialize the vertex ranks.

Hi! If no comments here, I'd like to merge this one :)


'Chromeless' mode URL is not OK

Clicking to 'Chromeless' mode link leeds to an error page.

Thanks for letting me know @DominiqueVial , that URL needed to be updated - should be working now.


Multiple COLLECT gives wrong results with 3.8, works in 3.7.10

My Environment

ArangoDB Version:        3.8.0
Storage Engine:             RocksDB
Deployment Mode:       Leader/Follower ("Master/Slave")
Deployment Strategy:   systemd
Configuration:               Leader 3.7.10 replicated to follower 3.8.0
Infrastructure:               own
Operating System:        Ubuntu 18.04 (L) and 20.04 (F)
Total RAM in your machine:        256GB (L) and 32 GB (F)
Disks in use:        HDD
Used Package:              Ubuntu .deb

Component, Query & Data
Affected feature:
AQL query, COLLECT statement.
AQL query (if applicable):
FOR q IN queries
    SORT q.date DESC
    LIMIT 1000
    COLLECT resultStatus = q.result.status, requestStatus = q.request.status WITH COUNT INTO nb
    RETURN { resultStatus, requestStatus, nb }

AQL explain and/or profile (if applicable):
Explain on 3.8.0
Query String (191 chars, cacheable: true):
 FOR q IN queries
     SORT q.date DESC
     LIMIT 1000
     COLLECT resultStatus = q.result.status, requestStatus = q.request.status WITH COUNT INTO nb
 RETURN { resultStatus, requestStatus, nb }

Execution plan:
 Id   NodeType               Est.   Comment
  1   SingletonNode             1   * ROOT
 12   IndexNode         450882273     - FOR q IN queries   /* reverse skiplist index scan, projections: `request` */
  5   LimitNode              1000       - LIMIT 0, 1000
  6   CalculationNode        1000       - LET #6 = q.`result`.`status`   /* attribute expression */   /* collections used: q : queries */
  7   CalculationNode        1000       - LET #8 = q.`request`.`status`   /* attribute expression */   /* collections used: q : queries */
  8   CollectNode             800       - COLLECT resultStatus = #6, requestStatus = #8 AGGREGATE nb = LENGTH()   /* hash */
 11   SortNode                800       - SORT resultStatus ASC, requestStatus ASC   /* sorting strategy: standard */
  9   CalculationNode         800       - LET #10 = { "resultStatus" : resultStatus, "requestStatus" : requestStatus, "nb" : nb }   /* simple expression */
 10   ReturnNode              800       - RETURN #10

Indexes used:
 By   Name        Type       Collection   Unique   Sparse   Selectivity   Fields       Ranges
 12   idx_49159   skiplist   queries      false    false        99.64 %   [ `date` ]   *

Optimization rules applied:
 Id   RuleName
  1   move-calculations-up
  2   move-calculations-up-2
  3   use-indexes
  4   use-index-for-sort
  5   remove-unnecessary-calculations-2
  6   move-calculations-down
  7   reduce-extraction-to-projection

Optimization rules with highest execution times:
 RuleName                                    Duration [s]
 use-indexes                                      0.00009
 specialize-collect                               0.00003
 reduce-extraction-to-projection                  0.00002
 remove-unnecessary-calculations-2                0.00001
 use-index-for-sort                               0.00001

76 rule(s) executed, 2 plan(s) created

Explain on 3.7.10
Query String (191 chars, cacheable: true):
 FOR q IN queries
     SORT q.date DESC
     LIMIT 1000
     COLLECT resultStatus = q.result.status, requestStatus = q.request.status WITH COUNT INTO nb
 RETURN { resultStatus, requestStatus, nb }

Execution plan:
 Id   NodeType               Est.   Comment
  1   SingletonNode             1   * ROOT
 12   IndexNode         450916894     - FOR q IN queries   /* reverse skiplist index scan, projections: `request`, `result` */
  5   LimitNode              1000       - LIMIT 0, 1000
  6   CalculationNode        1000       - LET #6 = q.`result`.`status`   /* attribute expression */   /* collections used: q : queries */
  7   CalculationNode        1000       - LET #8 = q.`request`.`status`   /* attribute expression */   /* collections used: q : queries */
  8   CollectNode             800       - COLLECT resultStatus = #6, requestStatus = #8 WITH COUNT INTO nb   /* hash */
 11   SortNode                800       - SORT resultStatus ASC, requestStatus ASC   /* sorting strategy: standard */
  9   CalculationNode         800       - LET #10 = { "resultStatus" : resultStatus, "requestStatus" : requestStatus, "nb" : nb }   /* simple expression */
 10   ReturnNode              800       - RETURN #10

Indexes used:
 By   Name        Type       Collection   Unique   Sparse   Selectivity   Fields       Ranges
 12   idx_49159   skiplist   queries      false    false        99.43 %   [ `date` ]   *

Optimization rules applied:
 Id   RuleName
  1   move-calculations-up
  2   move-calculations-up-2
  3   use-indexes
  4   use-index-for-sort
  5   remove-unnecessary-calculations-2
  6   move-calculations-down
  7   reduce-extraction-to-projection

Dataset:
queries collection has 450M docs. In the 1000 docs selected in the query above, q.request.status is always null.
Size of your Dataset on disk:
A few hundred GBs
Steps to reproduce

Run query above on 3.7.10. Result, as expected, is

resultStatus
requestStatus
nb

null
null
1

ok
null
893

reject
null
22

wrong_referential
null
84

Run same query on 3.8.0, result is

resultStatus
requestStatus
nb

null
null
1000

Edit the query to collect only one column on 3.8

FOR q IN queries
    SORT q.date DESC
    LIMIT 1000
    COLLECT resultStatus = q.result.status WITH COUNT INTO nb RETURN { resultStatus, nb }

and result is as expected

resultStatus
nb

null
1

ok
893

reject
22

wrong_referential
84

Problem:
Multiple collect seems to break results in 3.8.0.
Is it because of q.request.status being always null in this subset of data ? Or because an index is used to retrieve subset of documents ? Rules applied seem quite different in respective explains.
Thanks a lot !
Expected result:
Same result as in 3.7.10.

Thanks for reporting this! I was able to narrow it down to a problem with the reduce-extraction-to-projection optimizer rule and nested attribute access with the same attribute name at the same level (here: status):
db._drop("coll");
db._create("coll");
db.coll.save({ result: {} });
db.coll.save({ result: {status: "ok" } });

/* wrong with result.status / request.status (both "status") */
db._query(`FOR d IN coll COLLECT resultStatus = d.result.status, requestStatus = d.request.status WITH COUNT INTO count RETURN { resultStatus, requestStatus, count }`);

/* fine with optimizer rule disabled */
db._query(`FOR d IN coll COLLECT resultStatus = d.result.status, requestStatus = d.request.status WITH COUNT INTO count RETURN { resultStatus, requestStatus, count }`,
  null, { optimizer: { rules: ["-reduce-extraction-to-projection"] }});

/* fine with result.status / request.other (different nested attribute names) */
db._query(`FOR d IN coll COLLECT resultStatus = d.result.status, requestOther = d.request.other WITH COUNT INTO count RETURN { resultStatus, requestOther, count }`);

I created an internal ticket BTS-562.

Fixed via https://github.com/arangodb/arangodb/pull/14801

Hi. We can confirm that the bug is fixed in v3.8.3
Many thanks !


Create PR Github Workflow

This should sanity check PRs, so you can't commit broken code

Beautiful


Update ScsiBlockDevice.kt

change :
private const val MAX_RECOVERY_ATTEMPTS = 20  To  private const val MAX_RECOVERY_ATTEMPTS = 1

Why??? I dont think that is useful.


implement gethostbyaddr for reverse lookups

Hi,
Thanks for this package! I have the need to make async reverse lookups.
I was able to add the gethostbyaddr from the pycares package here pretty quickly. Is this something that is interesting for you to support? If so please tell me if you need me to make changes to the testing or flesh out the documentation a bit more.
Please note that I don't know that much about the underlying mechanisms here.

@antonagestam Thank you! The patch looks solid and all I need to do is remove Python 3.3 from Travis.
I'll try to get some time in the next few weeks to get a new release out.
Cheers!

Cool! If you want to I can remove Python 3.3 in another commit to this PR as well.

Merge please! :)

I pushed a PR https://github.com/saghul/aiodns/pull/48 that removes 3.3 (tried adding 3.7 but travis failed to download so let's look at that later).

It's officially a pull request party 🥳Opened another one that both removes 3.3 and adds 3.7: https://github.com/saghul/aiodns/pull/49


Great taste!

Bergman, Wong kar-wai and Sion Sono!
The only mistake in the Read Me file is that there is no actual text - that would have been one hell of an interesting conversation ;-)

Haha, definitely something i'd love to read!
These are a few of my favorite film directors, nice to see someone noticed this :)


document processors setting

https://trello.com/c/sv9oyis4/2854

@mikethebeer heya. pushed a fixup. can you re-check?

retest this please


Replacing individual tiles referenced in the tilemap of the background

Is your feature request related to a problem? Please describe.
Hi, i m new to gbstudio but i m comfortable with the concept of tileset and tilemap, and i also watched different tutorials for the concept fo tileswapping with VM_REPLACE_TILE_XY that requires unique tiles to be addressed and swapped.
I m building a port of a game witch scene looks like this ( could be familiar to someone )

And my player needs to digs tunnels, swapping the green tiles with black tiles.
I wouldn't mind using the unique tile swap feature if it wasn't i have too many tiles i can't make them unique.
My game has for now a grid of 15x10 cells, of 4 tiles ( 16px grid in topdown 2d ) but to be honest so is 150 areas, but are 4 tiles each, getting to 600 tiles and i can't make those unique. If there was a way to to define tiles of 16px that maybe would work, but would make the game super choppy swapping  a large block each time.
Describe the solution you'd like
I wish there was, or if it exists i wish it was documented, a way to access the description of my current background and swap the value of the referenced tile in the tilemap. So if my tile X,Y has a tile 0, i want to set that position in the tilemap to contain tile 1 for example.
Describe alternatives you've considered
Additional context
Add any other context or screenshots about the feature request here.

I can see from the c code that both the tileset and the tilemap are available:
const struct background_t bg_bg_level1_redone = {
    .width = 33,
    .height = 22,
    .tileset = TO_FAR_PTR_T(bg_bg_level1_redone_tileset),
    .cgb_tileset = { NULL, NULL },
    .tilemap = TO_FAR_PTR_T(bg_bg_level1_redone_tilemap),
    .cgb_tilemap_attr = { NULL, NULL }
};

tilemap is a simple array of uchar so i'm trying to try to patch my own function starting from vm_replace_tile_xy
void vm_replace_tilemap_xy(SCRIPT_CTX * THIS, UBYTE x, UBYTE y, const background_t * background, INT16 idx_new_tile) OLDCALL BANKED {
    THIS;
    UWORD ofs = (image_tile_width * y) + x;
    ... ?
}

But my lack of understanding of the inner working of the memory models of the sdk and C in general are making it super hard.
background.tilemap is a far_ptr, so is a struct with .ptr that is a pointer to that struct of data.
But then how to write inside there i m not sure.

So far i tried to hijack vm_replace_tile_xy becasue is complicated to add a fully new functionality just  trying here and there:
i was expecting something like this to work:
void vm_replace_tile_xy(SCRIPT_CTX * THIS, UBYTE x, UBYTE y, far_ptr_t * tilemap, INT16 idx_start_tile) OLDCALL BANKED {
    THIS;
    UWORD ofs = (image_tile_width * y) + x;
    *(image_ptr + ofs) = idx_start_tile;
}

Since image_ptr is esactly a ptr to the current background tilemap, but all i get is a rebooting gameboy to a different scene

Is that area read only?

after cleaning up all the changes to the engine and trying from scratch i tried this:
void vm_replace_tile_xy(SCRIPT_CTX * THIS, UBYTE x, UBYTE y, UBYTE tileset_bank, const tileset_t * tileset, INT16 idx_start_tile) OLDCALL BANKED {
    THIS;
    UWORD ofs = (image_tile_width * y) + x;
     *(image_ptr) = idx_start_tile;
    *(image_ptr + ofs) = idx_start_tile;
    *(image_ptr + ofs + 1) = idx_start_tile;
    *(image_ptr + ofs + 2) = idx_start_tile;
    *(image_ptr + ofs + 3) = idx_start_tile;
}

Hoping to see anything changing on screen, but nothing happens.
either my changes get overwritten by some screen refresh routine or i am writing bytes in the wrong area.


Not a bug report, just a thank you.

Just wanted to say you are an absolute legend, after struggling to do this myself I ended up dropping every bit of google fu I knew only to fail...

Thank you, it feels very nice when I learn that someone actually found my mod useful :smile:
Enjoy!


Updating the script with a working version

@cilwerner - Thanks for reviewing.
@franciscopgomes - Can you open a PR for this article from the repository that Chris linked in https://github.com/MicrosoftDocs/azure-docs/pull/123672#pullrequestreview-2166360965? This PR isn't mergable as-is.
Thanks!

@cilwerner - Thanks for reviewing.
@franciscopgomes - Can you open a PR for this article from the repository that Chris linked in #123672 (review)? This PR isn't mergable as-is.
Thanks!

Will do - thank you!


The fixer for Y0002 does not do anything for generics

Maybe this is a known limitation? var myList = Array.Empty<string>().ToList(); will suggest to use an explicit type, but the fixer does nothing, I'd hoped for a suggested change to List<string> myList = Array.Empty<string>().ToList(); .
(Yes one can argue that the type really is apparent here, but that's not the point. I just wanted a simple one-liner to demonstrate that the fixer doesn't do what I hoped).

This is certainly a bug. Thanks for opening the issue @xecrets.

@xecrets I just tested this. The behavior I'm seeing is different than your description:

The fixer does offer to use explicit type, but doesn't add imports, which is tracked by https://github.com/Youssef1313/YAnalyzers/issues/31


can tabBar not centered ?

currently, tabs are in the center of the tabbar,
,
can it support the style like this?

You need to at least provide the relevant code, ideally you should provide a minimum functioning example of your code.

answer myself ==, wrap a contaier and set alignment: Alignment.topLeft done
https://takeroro.github.io/2019/06/24/Flutter-tabBar一定要居中吗？/

close #34539 @shihaohong  it has been solved.


Add key shortcuts

Added CTRL+S, CTRL+Y and CTRL+Z as described in #315.

Don't merge this PR until Tobi merged my PR to his PR.
PR-ception!

Merged the one from BrainStone in.


HPX locks up when using at least 256 localities

The barrier implementation using an hierarchical tree currently is leading to a deadlock. This has been observed by trying to run an HPX application on 256 nodes. When setting hpx.lcos.collectives.cut_off to a very high value, the hang disappears.

Now I know why my infiniband tests stopped at 128 nodes

@sithhell What is a really high value?


Markdown quote tag escaped

Is there a way to allow the greater than  '>' symbol for quotes in markdown?

This is invalid HTML, so no... I think it would make sense to write a separate sanitize-markdown module.

We did an update .. please try again.

Please try what again?

Sorry, I miss-read the ticket.  It got this link at the same time we had a blockquote rendering issue.


Installation vs cluster ssh keys

Implementation slightly deviates from the design - the switch is part of the form-item, means it is not added as an extra field.
Behaviour:

If the image key is not set, the switch does not appear and the cluster-ssh text area works as before.
Otherwise (if it appears):

The switch is off when the two keys are different (means the user already provided different cluster key).
The switch is on if the two keys are equal or by default.

The textarea always shows the "effective" ssh cluster key (means even a copy of the installation key). If the switch is on, the text area is disabled for editation.

Cc @andybraren

@andybraren ,

IIRC the form currently says something like "this key is being hidden for security reasons" which might be true

This is probably relevant to the pull-secret. Since these SSH keys are public, there is probably no issue in revealing them.
Otherwise I got your point in hiding the textarea and moving the switch up. Will change this PR to that state.
I would postpone the kind of "file upload" for a later PR. So far the user can "copy to clipboard" the secret via a button right on the webpage and (s)he is instructed to do so. But I agree it makes sense in other cases.

perhaps troubleshooting / debug key? (vs install)
On Wed, Jul 22, 2020 at 9:38 AM Jiri Tomasek<EMAIL_ADDRESS>wrote:

@jtomasek commented on this pull request.
In src/components/clusterConfiguration/DiscoveryImageForm.tsx
https://github.com/mareklibra/facet-lib/pull/88#discussion_r458566925:

@@ -133,7 +133,7 @@ const DiscoveryImageForm: React.FC = ({
<TextAreaField
label="SSH public key"

Alternatively we could keep this one intact 'SSH public key' and in the
switch refer to this as 'Host discovery SSH key'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mareklibra/facet-lib/pull/88#discussion_r458566925,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAE5R4HYLV4IFL66Y7FMCTR42CORANCNFSM4PDSU7AQ
.

@andybraren , the textarea is hiding now.
Best-effort rewording:

in discovery modal: Host SSH public key for troubleshooting during discovery
in the cluster form: Host SSH Public Key for troubleshooting after installation

After re-reading all of the Jira comments and discussions in this PR, I think it really comes down to what @ohadlevy wrote:

IMHO 99/100 folks would always use the same ssh key.

I know @romfreiman thinks the same.
If that's true, then separate keys is an "Advanced" use case that we probably don't need to support for now. Maybe someday a user will have a strong use case and we can support it in an "Advanced" area/step of a future UI, but until then having two fields doesn't seem worth the UX impact. Wording changes only get us so far, and require more reading for everyone in the end.
What do we think about just keeping the SSH Public Key in the Discovery ISO modal and removing the second field entirely for now?
FYI @mgoldboi @jtomasek @nirfarkas

Not sure about behaviour for "erasing cluster ssh key". If the user wants the key for discovery image but does not want it further, (s)he can "switch off" syncing, remove content and save. Next-time (s)he enters the page, the switch is back to "on" (since the cluster.sshKey is empty string) and the page is marked as dirty.
So the user needs to switch syncing off again manually. But probably without additional info stored/provided by backend we can not handle this corner case right.

I rewrote the component into a Formik's field, so Formik handles state of the Switch and so the Discard button works properly now.
There is still an issue with the "removing the cluster ssh key" case. It can be done but after page refresh the switch is automatically back on "on" and so the form is marked as dirty (to be saved), since this is Switch's default and we have no way how to detect whether "empty cluster ssh key" is for the first-time or intentional. In such case, the user needs to manually turn the switch off and so the form turns to clean (not-dirty state). Support from backend would be needed if this appears to be an issue.
Such behaviour might be annoying if the "no-cluster-key" case is common. I doubt but let's see.

Rebased. Bunch of conflicts with #93.


Images get distorted with some advanced image layouts

Hey,
When clicking on Images with definitions like this
![[image.png|-grid]]  ![[image.png|-left]]
they get distorted (flated).
You can try on ITS-theme where they have these advanced options for image display.
It would be great if images selected from a grid looked normal
https://user-images.githubusercontent.com/73532672/133224558-fd1200f1-e1e4-4032-a3a4-c21ccb6b3963.mp4

Hey,
When clicking on Images with definitions like this
![[image.png|-grid]] ![[image.png|-left]]
they get distorted (flated).
You can try on ITS-theme where they have these advanced options for image display.
It would be great if images selected from a grid looked normal
https://user-images.githubusercontent.com/73532672/133224558-fd1200f1-e1e4-4032-a3a4-c21ccb6b3963.mp4

@danebace  Thanks for your feedback, I've fixed it in the latest version. You can update to v0.4.0:  https://github.com/sissilab/obsidian-image-toolkit/releases/tag/0.4.0.
There're many Obsidian themes, and some of them may affect the css styles.
I'm trying to find the problem out and fix it.


Added the feature of, only superuser can delete the members in the the team and also changed the sizes of images in the team list.

https://github.com/amfoss/fosswebsite/commit/e60ee27fe2574c730916493f73bcbc7cfdf03372

Please provide me with substantial description with screenshots on why these changes were made so that I can merge this request.
Other than that, I am happy to merge the request :)

Cool. Please resolve the merge conflict.

In the case of  "Added the feature of, only superuser can delete the members in the team." Only the superuser has the access to delete the member. Normal users cannot delete the members. The below image shows it.

In the above image it is the user who is logged in into the website.

In the case of "Changed the Title of the Members page to Members" The Title page is Events details before, but I changed to 'Members'.

Any changes in this pull request? @DheerajMalisetty


add resolution to collection temporal object

Given various datasets with temporal extents provide multiple timesteps within an extent, does it makes sense to add an optional duration property (consistent with RFC3339)?  Example below for model run with 3 hour time steps:
        "temporal": {
          "interval": [
            [
              "2020-05-23T00:00:00Z",
              "2020-06-02T00:00:00Z"
            ]
          ],
          "duration": "PT3H"
        }

this is already available in the spatio-temporal coordinate model of coverages, see the coverage examples provided with CIS.

@tomkralidis: indeed, makes sense to have the general n-D case in addition to BBOX. Here is the central link: https://github.com/opengeospatial/ogc_api_coverages/blob/master/standard/clause_9_subset.adoc - but it does not talk about the CRS construction, that is, eg, in CIS.

20210303 Coverages SWG call: Related to #96, and also to the synchronization with Common part 2

@pebau I get a 404 when trying to reach https://github.com/opengeospatial/ogc_api_coverages/blob/master/standard/clause_9_subset.adoc

@chris-little indeed, somehow shifting sands here...like the contents, the names keep changing as well:
https://github.com/opengeospatial/ogcapi-coverages/blob/master/standard/clause_9_coverage_rangesubset_subset_and_scaling.adoc

@jerstlouis Adding a duration may be problematic, in that results may be unexpected by the requester. Generally, durations and intervals are not consistent for calendars (they do not use conventional arithmetic), but they are consistent for formal temporal CRSs that have only one UoM and are soporphic to the number line.
Intervals, providing they are not 'subtracted', are safer.

SWG 2022-01-12: We clarified today that this issue was actually about including a "resolution", rather than "duration". This overlaps somewhat with the resolution specified in the Domainset axis description. A "resolution" could be added as an (optional?) component of the extent Uniform Additional Dimensions defined in common, in addition to interval and crs.

While I find this a very specific approach to a very specific question, I would not seriously object if the CIS schema is not changed. Options might be:

in the metadata section of CIS
in the Capabilities document equivalent

@pebau This is about offering the possibility to include additional information in the collection description at /collections/{collectionId}. No impact on CIS.
The OGC API specifications do not have a single direct equivalent of the WxS services Capabilities document.
Instead it has different for different aspects:

/ The API landing page (Common - Part 1)
/api (typically) The API definition (Common - Part 1)
/conformance The conformance definition (Common - Part 1)
/collections The list of collections (Common - Part 2)
/collections/{collectionId} The detailed collection resource (Common - Part 2)

@jerstlouis ok, thanks for the clarification!

SWG 2022-06-29: After reviewing the values syntax, we are realizing that the micro-syntax and the different ways that values is used might benefit from instead:

Only allowing explicit list of values -- NOTE: In CIS DomainSet, this can also be specified in the coordinate field of IrregularAxes
For the repetition mode, instead we would add repetitions and resolution properties to the extent and uad-extent schemas (this handles the different ValuesIsPoint vs. ValueIsArea as discussed in CIS#6
The lower/upperBound syntax is not necessary, as it is redundant with the lower and upper bounds already defined

We can try to synchronize this change with the values recently added to OGC API - Tiles and inform the EDR SWG about this change, and discuss in Common.
NOTE: The purpose of this is to allow describing resolution,repetitions and explicit list of coordinates where data is available (which can be done in the CIS domainset), but as a simple extensions to Collection extent/extent-uad dimensions.

Following feedback from last meeting, in PR #168, instead of values, grid is introduced as a member of extent dimensions, allowing to define either regular or irregular grids without introducing the ISO8601 micro-syntax. resolution and cellsCount (for regular grid) or coordiantes (for irregular grids) are specified separately. This should make things easier for clients. It alaso avoids the redundancy with the intervals (an overall one, and optional ones for separate parts) already defined in the extent. The schemas should also feel more familiar to people familiar with CIS, while remaining significantly simpler. (NOTE: This still does not affect the CIS resources, it is only for the collection description extent).
By using grid instead of values, we also avoid a conflict with EDR, allowing to serve a collection as both EDR and Coverages. For EDR, coordinates always quoted in values, even when numeric.
This approach follows what is being adopted in OGC API - Tiles (PR https://github.com/opengeospatial/ogcapi-tiles/pulls/124), where we also discussed this issue at length at the meeting last week.
@pebau @tomkralidis @chris-little
Could you please take a look to make sure we are all happy with this solution?

@jerstlouis +1 for grid in extent dimensions.  So then articulating a temporal resolution would look something like the the shorthand below?
extent:
    temporal:
        interval:
            grid:
                resolution: PT1H

@tomkralidis grid is outside of interval, so rather:
extent:
    temporal:
        interval: [ [ '2011-11-11T12:22:11Z', '2011-21-11T12:22:11Z' ] ]
        grid:
            resolution: 'PT1H'

ok, great.  +1

This issue has been resolved by PR #168.


Sample Size: Selecting the right sample size in your UX Research

Selecting the appropriate sample size for your UX Research

Five, ten, or twenty-five –
How many test participants?
February, 2015 Author: Ellen Francik, PhD, CUA, CXA
https://www.humanfactors.com/newsletters/how_many_test_participants.asp

First-click Testing 101
Your guide to creating and running effective first-click tests with Chalkmark'
https://www.optimalworkshop.com/learn/101s/first-click-testing/

A Beginner's Guide to First Click Testing
Clint Fontanella
Updated: June 24, 2022
Published: February 08, 2019
https://blog.hubspot.com/service/click-test

What is first click testing?
Modified: August 8th 2022 by Matt Ellis
https://www.pickfu.com/blog/first-click-testing/

How Many Test Users in a Usability Study?
Summary: The answer is 5, except when it's not. Most arguments for using more test participants are wrong, but some tests should be bigger and some smaller.
By  Jakob Nielsen  on June 3, 2012
Topics: User Testing
https://www.nngroup.com/articles/how-many-test-users/

Card Sorting: How Many Users to Test
Summary: Testing ever-more users in card sorting has diminishing returns, but test at least 15 users — 3 times more than you would in traditional usability tests.
By  Jakob Nielsen  on July 18, 2004
Topics: Information Architecture,  Research Methods
https://www.nngroup.com/articles/card-sorting-how-many-users-to-test/

How Many Participants for a UX Interview?
Summary: In the early stages of a UX-design project, recruit enough people to gain an in-depth understanding of users’ experiences and needs. The number of people needed for an interview study is often smaller than you think.
By  Maria Rosala  on October 31, 2021
Topics: Research Methods
https://www.nngroup.com/articles/interview-sample-size/

Sample Size Policy for Qualitative Studies Using In-Depth Interviews
Shari L. Dworkin
Archives of Sexual Behavior volume 41, pages 1319–1320 (2012)Cite this article
https://link.springer.com/article/10.1007/s10508-012-0016-6

Why You Only Need to Test with 5 Users
Summary: Elaborate usability tests are a waste of resources. The best results come from testing no more than 5 users and running as many small tests as you can afford.
By  Jakob Nielsen  on March 18, 2000
Topics: User Testing
https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/

Why 5 Participants Are Okay in a Qualitative Study, but Not in a Quantitative One
Summary: Qualitative usability testing aims to identify issues in an interface, while quantitative usability testing is meant to provide metrics that capture the behavior of your whole user population.
By  Raluca Budiu  on July 11, 2021
Topics: Research Methods
https://www.nngroup.com/articles/5-test-users-qual-quant/

Why You Cannot Trust Numbers from Qualitative Usability Studies
Summary: Qualitative usability studies have few users and variable protocol; numbers obtained from such studies are likely to poorly reflect the true behavior of your population due to large measurement errors.
By  Raluca Budiu  on May 23, 2021
Topics: Analytics & Metrics
https://www.nngroup.com/articles/true-score/

Data Is More than Numbers: Why Qualitative Data Isn’t Just Opinions
Summary: Systematically gathered qualitative data is a dependable method of understanding what users need, why problems occur, and how to solve them.
By  Page Laubheimer  on August 1, 2021
Topics: Research Methods
https://www.nngroup.com/articles/qualitative-rigor/

Quantitative Studies: How Many Users to Test?
Summary: When collecting usability metrics, testing with 20 users typically offers a reasonably tight confidence interval.
By  Jakob Nielsen  on June 25, 2006
Topics: Analytics & Metrics,  Research Methods,  User Testing
https://www.nngroup.com/articles/quantitative-studies-how-many-users/

How to Determine the Right Number of Participants for Usability Studies
By Janet M. Six and Ritch Macefield
January 4, 2016  6 Comments
https://www.uxmatters.com/mt/archives/2016/01/how-to-determine-the-right-number-of-participants-for-usability-studies.php

What sample size do you really need for UX research?
In which we demystify the potentially divisive question of sample size in UX research.
Kuldeep Kelkar
SVP, Services
2018-04-05
https://www.userzoom.com/ux-blog/what-sample-size-do-you-really-need-for-ux-research/

How Many Participants Do You Need for a Usability Study?
Enough’s enough. Here’s how to find your ideal sample size—the “sweet spot” that will deliver quality insights with the most efficiency.
Lizzy Burnam
https://www.userinterviews.com/blog/how-many-participants-do-you-need-for-a-usability-study


Fix Jade CI build pollution

It appears that the Jade CI is being polluted by the output of prior runs.  This needs removing, otherwise we're not getting a true clean build for this commit using the current tools, but rather some cached values (now out of date and not applicable) can interfere with the current build.

The CI here is fixed by forcing the cmake files to be rebuilt.
NOTE: the master build is currently failing with:
CMake Error at /tmp/cirrus-ci-build/test/work/jade/esp-idf/tools/cmake/project.cmake:296 (__project):
  The CMAKE_CXX_COMPILER:
    /tmp/cirrus-ci-build/test/work/jade/esp-idf-tools/tools/xtensa-esp32-elf/esp-2021r2-patch3-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-g++

Note earlier in the build we see:
Installing<EMAIL_ADDRESS>...
Extracting /tmp/cirrus-ci-build/test/work/jade/esp-idf-tools/dist/xtensa-esp32-elf-gcc8_4_0-esp-2021r2-patch5-linux-amd64.tar.gz to /tmp/cirrus-ci-build/test/work/jade/esp-idf-tools/tools/xtensa-esp32-elf/esp-2021r2-patch5-8.4.0

ie. this build installs 'esp-2021r2-patch5-8.4.0', but because of old/cached cmake files, is trying to use 'esp-2021r2-patch3-8.4.0' - which fails because this is not installed.
I can only assume this is happening because these builds are not proper clean builds, but are essentially incrementals (due to the 'work_cache' being copied in) - this is not something we've seen in our own CI.
The fix is to do a 'clean' when building the jade fw image (which is the smallest part of the build anyway, compared to fetching the toolchain repos and building them - which is helped by using the work_cache since we only update them once every few months - the jade 'master' code is usually updated every few days).  In any case the Jade C code is entirely rebuilt anyway - this extra 'clean' will just ensure the cmake files are recreated - minimal additional overhead.


Add SelectAction to ColumnSet in dotnet

ref: https://github.com/Microsoft/AdaptiveCards/issues/344

@EricDahlvang,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot