Add support for determining default branch when calling hub pull-request form worktree

PR created to address issue #2485.
When hub pull-request  is called from a worktree, hub does not correctly find the default branch for the repo.
This code is a bit of a hack; it attempts to check for worktree in the path pointed to by $GIT_DIR/.git of the worktree.
This should work for the default cause; however, I am not sure if it will work in all scenarios, specifically when users decide to set git config extensions.worktreeConfig true

On second thought, perhaps these changes should be added to Dir() function
https://github.com/github/hub/blob/b0db79dbf3988dd25c0053abc39a77fc92c46bfc/git/git.go#L26

Perhaps the fix is as simply as changing --git-dir to --git-common-dir
https://github.com/github/hub/blob/b0db79dbf3988dd25c0053abc39a77fc92c46bfc/git/git.go#L31

This PR just feels like we're making an already complicated approach even more complicated.

I completely agree.


Update combine-source-map dependency

Update combine-source-map dependency and bump minor version.
Downstream versions are erroring out in the 0.3.x chain.
fixes the following error:
Error: Cannot find module './source-map/source-map-generator'
    at Function.Module._resolveFilename (module.js:332:15)
    at Function.Module._load (module.js:282:25)
    at Module.require (module.js:361:17)
    at require (module.js:380:17)
    at Object.<anonymous> (P:\src\svn2.inxsol.com\hazready\trunk\Source\Hazready_VS\ExposureTrack.Website\_components\node_modules\browserify\node_modules\insert-module-globals\node_modules\combine-source-map\node_modules\inline-source-map\node_modules\source-map\lib\source-map.js:6:30)
    at Module._compile (module.js:426:26)
    at Object.Module._extensions..js (module.js:444:10)
    at Module.load (module.js:351:32)
    at Function.Module._load (module.js:306:12)
    at Module.require (module.js:361:17)
    at require (module.js:380:17)

I think that what you're seeing is this https://github.com/joyent/node/issues/6960

@zertosh nope, with the version change, it works just fine.  Now, viewing a really deep path in windows explorer, and the command prompt is another issue... but the npm install worked fine.

@tracker1 I think that thread talks about path handling in general - including require, which is the type of error you're seeing. The reason 0.6.1 probably works for you is because the source-map module gets deduped with combine-source-map's, so it's gets placed in a shallower directory. I'm pretty sure that if you move your project up a few directories, it'll work.
Regardless though, I'll go ahead with the update.

published as<EMAIL_ADDRESS>


helmfile: 0.40.1 -> 0.64.1

Motivation for this change
Update to latest release.
Things done

Adopt vgo2nix

Add me to maintainers

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)

Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"

[x] Tested execution of all binary files (usually in ./result/bin/)

[ ] Determined the impact on package closure size (by running nix path-info -S before and after)

[x] Assured whether relevant documentation is up to date

[x] Fits CONTRIBUTING.md.

@grahamcofborg build helmfile


The problem of reporting errors on argparse example

Recently, my annoying mistake in the autopep8 config took place
	...
	"autopep8.args": ["--global-config, ./config.lake8"]

instead
	...
	"autopep8.args": ["--global-config", "./config.lake8"]

There was error in the vscode logs (command pallete > show logs > autopep8) under the info level
2023-08-05 02:46:32.475 [info] cannot mix stdin and regular files.
The text of the error is sent, apparently, along with a class whose name says a lot more about my situation. It seems to me that it is worth changing something in the output of errors and in determining their level.

I will investigate and see if we can expose this issue better.


Use radio type for base16-theme-256-color-source and base16-highlight-mode-line

pcase checks both symbols and strings for backward compatibility.
Fixes #77

Awesome! This looks good to me. Thanks!


Polars for chemistry

Link to suggestion
https://bertiewooster.github.io/2023/03/10/Revisiting-a-Classic-Cheminformatics-Paper-The-Wiener-Index.html
Targeted section
Blog posts
Describe your suggestion
My blog post would be the first example of using Polars for science. It uses RDKit, one of the most popular packages for cheminformatics--the processing of chemical information. It points out helpful features of Polars including struct columns and unnest, joins, when-then-otherwise, and group_by.
Checklist

[X] checked if your suggestion is not already listed in Awesome Polars list.
[X] checked if it can fit in an existed section or suggest a new section and explain why your item does not fit into one and what would be the interest of your new section.
[X] checked when it's a repository if it's maintained (archived repository will be rejected).

Thanks @bertiewooster for your suggestion ! It will be added to the list !


unpin pdm on more CI jobs

Change Summary
Follow up to #6714
Related issue number
N/A
Checklist

[ ] The pull request title is a good summary of the changes - it will be used in the changelog
[ ] Unit tests for the changes exist
[ ] Tests pass on CI
[ ] Documentation reflects the changes where applicable
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

please review


Microsoft Visual Studio Code No Thai/ภาษาไทย Language Pack

Create Thai Language Pack

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

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


Feature Request: authPort in configuration

Hi there!
Would it be possible to add a configuration option that allows us to set the port of the Laravel instance used for auth?
I'm currently using Cloud9 as my editor and Apache is running on port 8080. I tried specifying the port in the "authHost" config option, but to no avail.
{
  "authHost": "<IP_ADDRESS>:8080"
}

Thanks!

I found a workaround. As it seemed like the authHost option was being parsed as an URI, I specified the protocol AND port. That worked.
{
  "authHost": "http://<IP_ADDRESS>:8080"
}

Thanks closing this then.


[Storage] [STG 95] Files Binary ACE

🚢

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-storage-file-share

@vincenttran-msft Just did a merge from main to the feature branch, and then feature branch to this binary ace branch. It looks like the _models.py and _share_client.py changes are not a part of the binary ace feature changes but caused initially when we had to merge main to the feature branch to test out test recording stuff. We decided to go with removing duplicate lines during discussion. Let me know if there's anything else I should do. Thanks for taking a look at the PR :D


Update packaging-uwp-apps.md

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Different signs for different types of diagnostics

Add support for different signs for diagnostics based on the type.
Currently in the config for diagnostics there is only a signs property. Instead of this it could be a table like this:
signs: {
    error: { '-', '=', '≡' },
    warning: { '-', '=', '≡' },
    info: { '-', '=', '≡' },
    hint: { '-', '=', '≡' },
}

This config would give the same look as it is currently, but one could use
signs: {
    error: {'E' },
    warning: { 'W' },
    info: { 'I' },
    hint: { 'H' },
}

to differentiate what type of diagnostic is that. I know currently it is possible to differentiate with highlight groups, but different signs would be more natural (at least for me, but this is an extra option, so the current behaviour can be kept if someone likes that as well)

Would you accept a PR for this?

sure

Here is the PR for this #80


max_steps: 256, streaming: true, buffer_size: 128 报错

Reminder

[X] I have read the README and searched the existing issues.

System Info
[2024-12-10 12:01:29,169] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
[WARNING]  async_io requires the dev libaio .so object and headers but these were not found.
[WARNING]  async_io: please install the libaio-dev package with apt
[WARNING]  If libaio is already installed (perhaps from source), try setting the CFLAGS and LDFLAGS environment variables to where it can be found.
[WARNING]  Please specify the CUTLASS repo directory as environment variable $CUTLASS_PATH
[WARNING]  sparse_attn requires a torch version >= 1.5 and < 2.0 but detected 2.3
[WARNING]  using untested triton version (2.3.1), only 1.0.0 is known to be compatible

llamafactory version: 0.8.4.dev0
Platform: Linux-5.10.0-33-cloud-amd64-x86_64-with-glibc2.31
Python version: 3.11.9
PyTorch version: 2.3.1+cu118 (GPU)
Transformers version: 4.43.1
Datasets version: 2.21.0
Accelerate version: 0.33.0
PEFT version: 0.12.0
TRL version: 0.9.6
GPU type: NVIDIA A100-SXM4-40GB
DeepSpeed version: 0.14.4

Reproduction
CUDA_VISIBLE_DEVICES=0,1,2,3,4,5,6,7 HF_ENDPOINT=https://hf-mirror.com llamafactory-cli train examples/curriculum/phi3_dpo_curriculum.yaml
Expected behavior
期望逐步加载数据
Others
配置文件：
model
model_name_or_path: LordNoah/phi3-sft
method
stage: dpo
do_train: true
finetuning_type: full
deepspeed: examples/deepspeed/ds_z3_config.json
dataset
dataset: ultrafeedback_curriculum
template: phi
cutoff_len: 1024
max_steps: 256
overwrite_cache: true
preprocessing_num_workers: 1
streaming: true
buffer_size: 128
output
output_dir: saves/phi3-curriculum/curriculum
logging_steps: 5
save_strategy: "no"
plot_loss: true
overwrite_output_dir: true
save_only_model: true
train
per_device_train_batch_size: 2 #4
gradient_accumulation_steps: 2 #4
learning_rate: 2.0e-7
num_train_epochs: 3
lr_scheduler_type: cosine
warmup_ratio: 0.05 #0.1q
bf16: true
ddp_timeout: 180000000
resume_from_checkpoint: False
eval
val_size: 64
per_device_eval_batch_size: 4
eval_strategy: steps
eval_steps: 5000
###报错信息
[INFO|trainer.py:2134] 2024-12-10 11:57:08,144 >> ***** Running training *****
[INFO|trainer.py:2135] 2024-12-10 11:57:08,144 >>   Num examples = 8,192
[INFO|trainer.py:2136] 2024-12-10 11:57:08,144 >>   Num Epochs = 9,223,372,036,854,775,807
[INFO|trainer.py:2137] 2024-12-10 11:57:08,144 >>   Instantaneous batch size per device = 2
[INFO|trainer.py:2140] 2024-12-10 11:57:08,144 >>   Total train batch size (w. parallel, distributed & accumulation) = 32
[INFO|trainer.py:2141] 2024-12-10 11:57:08,144 >>   Gradient Accumulation steps = 2
[INFO|trainer.py:2142] 2024-12-10 11:57:08,144 >>   Total optimization steps = 256
[INFO|trainer.py:2143] 2024-12-10 11:57:08,145 >>   Number of trainable parameters = 3,821,079,552
0%|                                                                                | 0/256 [00:00<?, ?it/s][rank0]: Traceback (most recent call last):
[rank0]:   File "/opt/conda/envs/sto/lib/python3.11/site-packages/accelerate/data_loader.py", line 633, in _fetch_batches
[rank0]:     batch = concatenate(batches, dim=0)
[rank0]:             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/opt/conda/envs/sto/lib/python3.11/site-packages/accelerate/utils/operations.py", line 620, in concatenate
[rank0]:     return type(data[0])({k: concatenate([d[k] for d in data], dim=dim) for k in data[0].keys()})
[rank0]:                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/opt/conda/envs/sto/lib/python3.11/site-packages/accelerate/utils/operations.py", line 620, in
[rank0]:     return type(data[0])({k: concatenate([d[k] for d in data], dim=dim) for k in data[0].keys()})
[rank0]:                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/opt/conda/envs/sto/lib/python3.11/site-packages/accelerate/utils/operations.py", line 623, in concatenate
[rank0]:     return torch.cat(data, dim=dim)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]: RuntimeError: Sizes of tensors must match except in dimension 0. Expected size 1024 but got size 576 for tensor number 1 in the list.
[rank0]: The above exception was the direct cause of the following exception:
[rank0]: Traceback (most recent call last):
[rank0]:   File "/root/projects/SP-STO/src/llamafactory/launcher.py", line 23, in
[rank0]:     launch()
[rank0]:   File "/root/projects/SP-STO/src/llamafactory/launcher.py", line 19, in launch
[rank0]:     run_exp()
[rank0]:   File "/root/projects/SP-STO/src/llamafactory/train/tuner.py", line 56, in run_exp
[rank0]:     run_dpo(model_args, data_args, training_args, finetuning_args, callbacks)
[rank0]:   File "/root/projects/SP-STO/src/llamafactory/train/dpo/workflow.py", line 88, in run_dpo
[rank0]:     train_result = trainer.train(resume_from_checkpoint=training_args.resume_from_checkpoint)
[rank0]:                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/opt/conda/envs/sto/lib/python3.11/site-packages/transformers/trainer.py", line 1938, in train
[rank0]:     return inner_training_loop(
[rank0]:            ^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/opt/conda/envs/sto/lib/python3.11/site-packages/transformers/trainer.py", line 2236, in _inner_training_loop
[rank0]:     for step, inputs in enumerate(epoch_iterator):
[rank0]:   File "/opt/conda/envs/sto/lib/python3.11/site-packages/accelerate/data_loader.py", line 677, in iter
[rank0]:     next_batch, next_batch_info = self._fetch_batches(main_iterator)
[rank0]:                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/opt/conda/envs/sto/lib/python3.11/site-packages/accelerate/data_loader.py", line 635, in _fetch_batches
[rank0]:     raise RuntimeError(
[rank0]: RuntimeError: You can't use batches of different size with dispatch_batches=True or when using an IterableDataset.either pass dispatch_batches=False and have each process fetch its own batch  or pass split_batches=True. By doing so, the main process will fetch a full batch and slice it into num_processes batches for each process.

buffer_size: 128
preprocessing_batch_size: 128
streaming: true
accelerator_config:
  dispatch_batches: false

buffer_size: 128
preprocessing_batch_size: 128
streaming: true
accelerator_config:
  dispatch_batches: false

感谢，现在可以运行了，但能否设置epoch数呢？现在是跑完一个epoch就结束了

能吧


Switch to k3s Uninstall Script

We mange our own way of cleaning up nodes, however we should rely on k3s's uninstall script that is placed there when k3s is installed.
https://rancher.com/docs/k3s/latest/en/installation/uninstall/
server nodes
/usr/local/bin/k3s-uninstall.sh
agent nodes
/usr/local/bin/k3s-agent-uninstall.sh
We will also want to be sure we can run this multiple times without failure (part of the reason it was extracted from this).
I think we can check to see if it exists first before running and assume if it does not that it's a clean system.  Not the best but open to ideas.

I can tackle this change if you like. I've already made the necessary changes, but before creating a PR I'd like to discuss them with you.
First off, regarding the uninstall scripts. They call /usr/local/bin/k3s-killall.sh which stops the service and kills all processes, and then unmount and remove all files, including the uninstall scripts themselves. Basically this means, checking for it's existence is a safe way of assuming if the system is clean or not. Any error in their execution would prevent said scripts from being removed.
The question I have is:
a) should we use the script from get.k3s.io to install k3s? It would take care of downloading the appropriate binary for the given CPU architecture, creating the proper service files and generating the uninstall scripts for us.
b) or should we copy the uninstall scripts from templates?
Personally I would suggest switching to the script from get.k3s.io:

It is officially supported and maintained, reducing the need for template maintenance in k3s-ansible
It adds automatic support for systemd and openrc
k3s-ansible's responsibility would be more focused on "k3s cluster installation orchestration" and the official script takes care of "node installations"

Looking forward to your/any feedback.
Sam

If you want to have a look at my proposed changes, you can find them here: https://github.com/techno-tim/k3s-ansible/compare/master...hdensity:k3s-ansible:k3sscripts

@timothystewart6 Here's rendered scripts for each:
/usr/local/bin/k3s-killall.sh
/usr/local/bin/k3s-killall.sh
#!/bin/sh

[ $(id -u) -eq 0 ] || exec sudo $0 $@

for bin in /var/lib/rancher/k3s/data/**/bin/; do
    [ -d $bin ] && export PATH=$PATH:$bin:$bin/aux
done

set -x

for service in /etc/systemd/system/k3s*.service; do
    [ -s $service ] && systemctl stop $(basename $service)
done

for service in /etc/init.d/k3s*; do
    [ -x $service ] && $service stop
done

pschildren() {
    ps -e -o ppid= -o pid= | \
    sed -e 's/^\s*//g; s/\s\s*/\t/g;' | \
    grep -w "^$1" | \
    cut -f2
}

pstree() {
    for pid in $@; do
        echo $pid
        for child in $(pschildren $pid); do
            pstree $child
        done
    done
}

killtree() {
    kill -9 $(
        { set +x; } 2>/dev/null;
        pstree $@;
        set -x;
    ) 2>/dev/null
}

remove_interfaces() {
    # Delete network interface(s) that match 'master cni0'
    ip link show 2>/dev/null | grep 'master cni0' | while read ignore iface ignore; do
        iface=${iface%%@*}
        [ -z "$iface" ] || ip link delete $iface
    done

    # Delete cni related interfaces
    ip link delete cni0
    ip link delete flannel.1
    ip link delete flannel-v6.1
    ip link delete kube-ipvs0
    ip link delete flannel-wg
    ip link delete flannel-wg-v6

    # Restart tailscale
    if [ -n "$(command -v tailscale)" ]; then
        tailscale set --advertise-routes=
    fi
}

getshims() {
    ps -e -o pid= -o args= | sed -e 's/^ *//; s/\s\s*/\t/;' | grep -w 'k3s/data/[^/]*/bin/containerd-shim' | cut -f1
}

killtree $({ set +x; } 2>/dev/null; getshims; set -x)

do_unmount_and_remove() {
    set +x
    while read -r _ path _; do
        case "$path" in $1*) echo "$path" ;; esac
    done < /proc/self/mounts | sort -r | xargs -r -t -n 1 sh -c 'umount -f "$0" && rm -rf "$0"'
    set -x
}

do_unmount_and_remove '/run/k3s'
do_unmount_and_remove '/var/lib/rancher/k3s'
do_unmount_and_remove '/var/lib/kubelet/pods'
do_unmount_and_remove '/var/lib/kubelet/plugins'
do_unmount_and_remove '/run/netns/cni-'

# Remove CNI namespaces
ip netns show 2>/dev/null | grep cni- | xargs -r -t -n 1 ip netns delete

remove_interfaces

rm -rf /var/lib/cni/
iptables-save | grep -v KUBE- | grep -v CNI- | grep -iv flannel | iptables-restore
ip6tables-save | grep -v KUBE- | grep -v CNI- | grep -iv flannel | ip6tables-restore

/usr/local/bin/k3s-uninstall.sh
#!/bin/sh
set -x
[ $(id -u) -eq 0 ] || exec sudo $0 $@

/usr/local/bin/k3s-killall.sh

if command -v systemctl; then
    systemctl disable k3s
    systemctl reset-failed k3s
    systemctl daemon-reload
fi
if command -v rc-update; then
    rc-update delete k3s default
fi

rm -f /etc/systemd/system/k3s.service
rm -f /etc/systemd/system/k3s.env

remove_uninstall() {
    rm -f /usr/local/bin/k3s-uninstall.sh
}
trap remove_uninstall EXIT

if (ls /etc/systemd/system/k3s*.service || ls /etc/init.d/k3s*) >/dev/null 2>&1; then
    set +x; echo 'Additional k3s services installed, skipping uninstall of k3s'; set -x
    exit
fi

for cmd in kubectl crictl ctr; do
    if [ -L /usr/local/bin/$cmd ]; then
        rm -f /usr/local/bin/$cmd
    fi
done

rm -rf /etc/rancher/k3s
rm -rf /run/k3s
rm -rf /run/flannel
rm -rf /var/lib/rancher/k3s
rm -rf /var/lib/kubelet
rm -f /usr/local/bin/k3s
rm -f /usr/local/bin/k3s-killall.sh

if type yum >/dev/null 2>&1; then
    yum remove -y k3s-selinux
    rm -f /etc/yum.repos.d/rancher-k3s-common*.repo
elif type rpm-ostree >/dev/null 2>&1; then
    rpm-ostree uninstall k3s-selinux
    rm -f /etc/yum.repos.d/rancher-k3s-common*.repo
elif type zypper >/dev/null 2>&1; then
    uninstall_cmd="zypper remove -y k3s-selinux"
    if [ "${TRANSACTIONAL_UPDATE=false}" != "true" ] && [ -x /usr/sbin/transactional-update ]; then
        uninstall_cmd="transactional-update --no-selfupdate -d run $uninstall_cmd"
    fi
    $uninstall_cmd
    rm -f /etc/zypp/repos.d/rancher-k3s-common*.repo
fi


Add an option to include/exclude e-bike rides types in fitness trend

Fitness graph doesn't currently include e-bike rides. While the engine definitely helps, e-bike riding still has an impact over fatigue and fitness. :)

@metacosm Can you provide a backup of your history? Thanks

@thomaschampagne is there a way to do so privately? Don't really want to expose my history publicly…

Sure email me at<EMAIL_ADDRESS>

@metacosm i will bring that later in 6.1.0 with list of type of sports to include/exclude

@metacosm I will finally bring it earlier in v6.0.1 as "quick win" (fixing release of just released v6.0.0)
Toggle option like this

@metacosm Will toggle icon seems legit for you?
Icon database: https://material.io/icons/
I identified "power" or "power settings new"

@thomaschampagne power looks good, a little worried it might be confused with the other lightning icon, though

@metacosm you right. any other solution?

Also a tooltip text is displayed on mouse over icon

I don't have a better idea, apart maybe, though it might look weird, ev_station

@metacosm Nice one ;) Also battery charging full

or motorcycle

@thomaschampagne battery charging full might be best!

@metacosm Ready for 6.0.1 ;)
(je suis de Meylan ;))

@thomaschampagne merci!
(Et oui, je sais que tu es du coin! ^_^)

@metacosm Si jamais tu veux bien tester que tout est OK avant release finale, tu peux télécharger le dernier build de develop:
https://bintray.com/thomaschampagne/stravistix/travis-ci-builds/develop#files
Si bugs je ré ouvre le ticket.
Merci,
Tom

@thomaschampagne everything looks good, just a quick UI nitpicking: it's difficult to quickly figure out which icon is associated with a checkbox: is it the one on the left or on the right? The fact that the icon is actually closer to the next checkbox than the one it is associated with is confusing.
Of course, by checking the whole sequence, you figure it out but clearer separation (maybe more space between each checkbox/icon pair) or visual association (box around each checkbox/icon pair) would help.

Maybe I should open a separate issue for this?
(retour à l'anglais pour la compréhension de tout le monde, même si je ne sais pas si tu as des contributeurs)

@metacosm Ok thanks i will handle that

Weird because it was clearer on the screenshot you posted earlier…

@metacosm It depends of the window width size

@metacosm I fixed like this:

30% & 70% width distribution


Update Actor class description and consume() docstring

description attribute of the Actor class is deprecated now
added missing docstring for the return value of consume() method

Can one of the admins verify this patch?


SSL configuration is Running - [BRIEF DESCRIPTION]

App Id: d3rg9crrppu2tu
Region: ap-southeast-1
Step: SSL configuration
Status: Running

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
A clear and concise description of what the issue/question is.
Error message
If there is an error message, please include it here.
Note: Be sure to check the message for sensitive information.
Additional information
Please add any other relevant information. Please feel free to include screenshots.

@vidhyasagarj SSL configuration can take up to 24 hours to complete. Please see the linked documentation and let us know if you still do not have an associated domain in that time frame.
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domains.html


Update the computation of x_hat in Pickles.Step_verifier / Pickles.Wrap_verifier to use 'chunked lagrange commitments'.

Fix #13016
Incidentally, at this point #13017 is also fixed.

An equivalent PR has landed. Closing.


PDF export makes title slide empty (almost)

I have a repo https://github.com/inesusvet/tests-talk
When I did pdf export I got a file with blank title slide. After this I had some experiments with changing title slide: changed ## to # and removing a code block (which was visible in pdf by the way) from the slide. No luck.
After a while I have just added an empty first slide to get the version I want to share. Now I removed the empty slide for reproducing the bug.
It is interesting that in the footer on first page in pdf document I can see github logo but no text inesusvet/tests-talk which is presented on other slides. Which makes me think about css error.

Are you using gitpitch.com or a local installation of the GitPitch server? I ask because I just tried Print Version in the menu for your presentation on gitpitch.com and the PDF generated appears to be rendered correctly. I see no blank slides or issues with the footer text or icon.

I used gitpitch.com
Let check if I can reproduce it now
Thank you
Ivan
On Wed, 15 Nov 2017 at 14:44, David Russell<EMAIL_ADDRESS>wrote:

Are you using gitpitch.com or a local installation of the GitPitch
server? I ask because I just tried Print Version in the menu for your
presentation on gitpitch.com and the PDF generated appears to be rendered
correctly. I see no blank slides or issues with the footer text or icon.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gitpitch/gitpitch/issues/134#issuecomment-344568612,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABqUG3CMMewHmkAQJp4iM2k7tAmj_yy2ks5s2s6OgaJpZM4QekaW
.

--
Всего хорошего
Иван

I have managed to reproduce it. I have a branch for a moment when I had that issue:
https://gitpitch.com/inesusvet/tests-talk/reproduce-blank-title-slide?grs=github&t=night
and pdf with "almost" empty title slide is here:
https://gitpitch.com/pitchme/print/github/inesusvet/tests-talk/reproduce-blank-title-slide/night/PITCHME.pdf
Hope that will help

This issue has proved to be incredibly subtle and difficult to debug. But I now believe the the underlying cause of the printing problem reported has to do with subtle timing differences when loading external fonts within the decktape printing engine.
Two of the six available themes have external dependencies on multiple Google fonts. The loading of these external dependencies over the network when generating PDF output results in the types of printing failures described on this thread.
The following collage demonstrates four successful attempts at printing the sample presentation, and two failures cases:

The two failures cases occur when using the night and the sky themes. These are the two themes with multiple external Google font dependencies.
The success cases occur when using any of the other themes: white, beige, moon, and black.
I do not have a code solution at this time. However, as a workaround, please apply any of the working themes and your presentation should print reliably. I recommend you apply your theme using the Theme Setting in your PITCHME.yaml to ensure your users/audience do not accidentally hit the same problem you have.
Can you please try out the workaround described here and update this thread with your results. Thanks.

Thank you.
My workaround was just adding blank title slide and export to pdf after cache timeout.
If there is no chance to fix this at the moment, I would recommend put a notification about this "known issue" to the docs (I was traversing them in order to find any clue with no luck)

Thanks for the suggestion @inesusvet to add a known issue about this. I decided to fix the issue instead. A patch is now live on gitpitch.com which should permanently resolve this issue.
As your reproducible test case showed, and as I verified, both the night and sky themes were potentially problematic. Here now is the first slide of your presentation rendered as a PDF using both of those themes:

If you do test this out yourself I'd appreciate it if you could share your results, either to confirm the patch works as expected or to let me know more work needs to be done.

That's awesome!
I can confirm that it works well now
Thank you very much for the spirit and actually fixing this stuff 👍


Is it possible/recommended to include API calls or webhook connections in a service?

In case the app was killed and the service needs to update the data to a server?
Not exactly an issue, just looking for a bit of a recommended practice advice.

From an android perspective:
A foreground task ( service ) is something that the user is aware of as opposed to a background service. Think of it like a music player. It is pretty unusual that it gets killed by the OS until and unless the user does so. You shouldn't worry about the service being killed. As for your question the foreground service pretty much stays alive even when the app is killed.

@Dev-hwang I recommend this issue closed.

Thanks! Wasn't sure if it was fine to have webhooks in it. I'll close the issue now.


Add markdown link check to actions

Resolves https://github.com/galacticcouncil/HydraDX-docs/issues/2

@jak-pan maybe you have ideas? The check is falling for all local URLs -can we somehow get the build running in the action?
Another option would be to run the check post-deploy against docs.hydradx.io

I think we don't need this. Not sure why I added the issue (probably because the broken links with non / links, we could just check that) I guess the build checks if the links are ok?

So building in pipeline and checking if it passed should be enough

true and also quite obvious! closing the PR, you can close the issue


[Jenkins-34817]Add job-dsl-plugin support for logstash

job-dsl-plugin is not supporting logstash plugin yet. This PR adds the support for it.

This is already supported by the automatically generated DSL:
job('example') {
  wrappers {
    logstashBuildWrapper()
  }
}

Except this is an available function in the jobs DSL:
job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/wrapper/WrapperContext.groovy
So I get the following when I try to add it:
Processing DSL script jobDefinitions.groovy
ERROR: (jobDefinitions.groovy, line 225) No signature of method: javaposse.jobdsl.dsl.helpers.wrapper.WrapperContext.logstashBuildWrapper() is applicable for argument types: () values: []
Def:
job('cleanup-oldbuilds') {
description 'Cleanup old master builds.'
logRotator (7, -1, -1, -1)
label "master"
triggers {
scm('@daily')
}
steps {
shell("echo 'test'");
}
wrappers {
logstashBuildWrapper()
}
}
So maybe this is on the Job-DSL side of things


feat(app.component): Move default boilerplate styles into their own css-file

Feature Description
When creating a new boilerplate app with ng new, the default styles are put at the top of app.component.html, even though the command also creates app.component.css, but leaves it empty. This forces the user to move and / or remove the default style from app.component.html.
The feature I am suggesting is to generate the default boilerplate app so that the default app.component styles are put inside the intended css-file.
Use cases
Lessen the amount of boilerplate cleaning inside app.component.html

I believe this is handled in the CLI. Transferring to the correct repo.


RMNI text clarification for issue #320

added explicit text detailing CLIC fields added to RNMI CSR mncause for issue #320

do we need to add text about RNMI NMRET and clic interrupt level?


Sweep: Add option to delete an experiment to the experiment card

As mentioned in https://github.com/OpenPipe/OpenPipe/issues/195, deleting an experiment is not currently a straightforward process. We should add an options dropdown to the experiment card that contains an option for deleting.

Checklist

[X] app/src/components/ExperimentCard.tsx

• Add a delete option in the dropdown menu of the experiment card.
• Implement an event handler for the delete option. When the delete option is clicked, it should call a function to delete the corresponding experiment.

[X] app/src/api/experiments.ts

• Add a function to delete an experiment. This function should send a DELETE request to the server with the id of the experiment to be deleted.

[X] app/src/pages/experiments/index.tsx

• Update the list of experiments after an experiment is deleted. The deleted experiment should be removed from the list of experiments.

Implemented in https://github.com/OpenPipe/OpenPipe/pull/206


[FLINK-2837][storm] various improvements for Storm compatibility

This pull request contains various fixes. Most prominently, the parsing logic for Storm topologies has been changed to support multiple inputs. The API has been redone slightly. Two new examples have been added.

refactor to use Storm's topology builder

remove FlinkTopologyBuilder

instantiate context-based StreamExecutionEnvironment (local or remote)

remove Flink and Storm behavior replicating classes

modify FlinkTopology to parse Storm topology directly

replace StormTestBase with StreamingTestBase

let the FiniteFileSpout finish in corner cases

expose taskId, fix off by one task id

add print example

FlinkTopologyBuilder changes (check if all inputs are available before processing)

correct package typo

support getter methods on TupleWrapper

two input support

add join example

update docs

use Flink file system access

I will integrate the changes of #1387. It would be great if we merged these changes afterwards.

I've rebased to the latest master and addressed your comments. I would like to merge this and programmatically fix the multiple inputs issue afterwards.

I've addressed your comments.

If Travis is green please merge. You can fix the last tiny comments directly before merging. No need to update this PR.

Thanks for your feedback!

Thanks for you patience. :)


chore(whale/sanity-testing): port over tests from whale ci newman

What this PR does / why we need it:
Ports over the sanity tests from https://github.com/JellyfishSDK/whale/blob/main/.github/workflows/ci/postman_collection.json as typescript + jest tests
Which issue(s) does this PR fixes?:
Part of #977
Additional comments?:

One thing to note is that the CI pipeline now builds whale twice. We can investigate in a future PR the possibility of sharing the build (output of the build workflow) with the sanity test env.

Every time I rerun the test, the system will build the image again. I wonder if the following code can change from docker.buildimage to docker.getimage
See https://github.com/JellyfishSDK/jellyfish/blob/main/jest.sanity.setup.js#L26
Refer to https://github.com/JellyfishSDK/jellyfish/blob/main/packages/testcontainers/src/containers/DockerContainer.ts#L141

Every time I rerun the test, the system will build the image again. I wonder if the following code can change from docker.buildimage to docker.getimage
if the image was built BEFORE

If the underlying (whale) code changes, will docker be aware and rebuild the image?

Every time I rerun the test, the system will build the image again. I wonder if the following code can change from docker.buildimage to docker.getimage
if the image was built BEFORE

@jingyi2811 thanks for the suggestion. But if the underlying (whale) code changes, will docker be aware and rebuild the image?

If there are code changes, a new docker name needs to be given and rebuild is needed.

If it is too hard then just ignore it, I am using an old Mac book with an Intell processor. Running tests on every test unit takes me 5 to 10 minutes.

There is definitely room for optimization improvements to the sanity layer dedicating more time to the process. The current main use case for our whale sanity tests is mostly in our devops/releases processes. It's separated from the standard unit tests, as its a pretty heavy handed process so we decided to make it opt in. (No one wants to wait 5 - 10 minutes when running local unit tests) 😅


Make test variations simple with an option to pre-hash bindings

Sometimes, users want to be able to run variations of a scenario where the main difference is the data used in the operations.
The way this would work currently is that a user would either specify a different cycle range, or modify their binding functions with an initial function to remap the cycle range as seen by binding functions. Both achieve the same practical effect in most cases.
However, sometimes binding functions are intentionally used in a monotonically increasing way. For example, a user might need to lay more data into a regular data set starting from some sequence-oriented identifier. In this case, assigning a different cycle range makes sense, and can be considered incremental.
So, to cover both situations, we need the ability to do either or both of these:

Modify all active binding recipes with an initial permutation function.
Modify some active binding recipes with an initial permutation function.

The recommendation is to allow for modifying specific or named permutation functions automatically. This would allow binding functions to be named in a way that distinguishes some of them as always monotonic, or otherwise. A basic set of conventions for distinguishing these needs to be adopted, documented, and made consistent in all the included examples.

Elaboration on links for context and clarity...

Related to #380 because you can easily partition workloads (including data in ops) across activities or nodes with a pre-hashing function. For example, a 1M row ingest workload can be broken apart into ten separate 100K row workloads by prefixing each one as:

partition 1: Mod(100000L); Add(0L);
partition 2: Mod(100000L); Add(100000L);
partition 3: Mod(100000L); Add(200000L);
...

Related to #1958 because you can model these coordinate spaces separately and directly using a coordinate system which is not one-dimensional. In other words, the coordinate space can be a scalar vector of some length N to represent either N dimensions, or N 1-dimensional ordinals, or anything in between, depending on how it is needed to be used.

Related to #33 because the partioning ability above is a key requirement to make splitting workloads over nodes easy.


History size increase

What happened to the option to increase history log size in Spyder? I cannot find this option anywhere anymore

Hi @keeper90,
Which history log size are you searching for? Can you please let me know which plugin?

@steff456 Thank you for the reply. The history.py tab (next to the IPython console tab), the one that lists all your previous commands. I remember being able to set its max size (in lines) under preferences, but can no longer find such an option.

This option was removed in our 4.2.1. The explanation for that change is here: https://github.com/spyder-ide/spyder/pull/14443.
Now the default is 1000 lines. If you consider it should be higher, please suggest a new value.

@ccordoba12  Thank you for the explanation. I went ahead and modified the spyder source code locally to make it work. To be honest, I find it hard to believe that "this option doesn't add much value". The value is tremendous for people who code a lot and have dozens of scripts per project (as things work in research) and just want a way to quickly find some parts of code they coded n days ago. I'm sure a big part of python community is content with 1000 lines, but obviously some are not and it's always best to let the end user decide what such values should be.

@keeper90, I understand your points, but for us history is easily retrievable using IPython.
In any case, our plan is to improve that pane in Spyder 6 by using IPython history mechanism. When we do that, we could restore this option because it'd easy to make changes be applied instantly.

I agree with @keeper90. I've been using Spyder for the past 6 years for my research work which involves a lot of prototyping and as a result my history log (set to the maximum of 10,000 entries) gets filled within 6 months. This is mainly because I use F9 a lot, for example, to re-define a function with slight modifications instead of running the whole script.
The history log also provides an overview/timeline of the work one has done over the past few months. I usually take backups of the history log every 6 months, but now with just 1000 entries, I'll have to take backups every week, which is not practical.
Today, I updated from Spyder 4.1.4 to 5.0.3 and found about this new history limit (1000 entries). I have no option but to revert back to 4.1.4 or maybe 4.2.0, which I think is the last Spyder version with maximum history limit as 10,000.
@ccordoba12 I think 1000 is a good default value, but as @keeper90 said, it's best to let the end user decide these values, to the extent that they don't crash/slowdown the application. If you'd ask me, I would prefer a maximum limit of 50,000 or 100,000, if that's possible.

Hi @keeper90 May I ask you where to change to modify the 1000 line limit? My 1000 lines fill up in a few days or a week at most. I can't understand the motive behind limiting it to 1000 at all...

@ccordoba12 Thank you for the explanation. I went ahead and modified the spyder source code locally to make it work. To be honest, I find it hard to believe that "this option doesn't add much value". The value is tremendous for people who code a lot and have dozens of scripts per project (as things work in research) and just want a way to quickly find some parts of code they coded n days ago. I'm sure a big part of python community is content with 1000 lines, but obviously some are not and it's always best to let the end user decide what such values should be.

@ccordoba12 Thank you for the explanation. I went ahead and modified the spyder source code locally to make it work. To be honest, I find it hard to believe that "this option doesn't add much value". The value is tremendous for people who code a lot and have dozens of scripts per project (as things work in research) and just want a way to quickly find some parts of code they coded n days ago. I'm sure a big part of python community is content with 1000 lines, but obviously some are not and it's always best to let the end user decide what such values should be.

I totally agree the option to increase history buffer is important for many users. Can anyone please share the workaround to change the source code locally to increase the history buffer? Thanks!


mouseout event not firing in chrome?

Mouseout event not firing on a group that contains an element and a symbol (made form two elements). Event fires only on "element part" but not on "symbol part" of a group.
Happens only in Chrome (43.0.2357.81) whereas Mouseover event on the same group works fine.
Try following code:
draw = SVG('svgdrawing').size('100%', '100%');
var symbol = draw.symbol();
             symbol.circle(25).fill('#ffffff').stroke({ width: 2 }).dx(2).dy(2);
             symbol.polygon('10,3 5,12 11,12 6,22 19,10 11,10 17,3').fill('none').stroke({ width: 1 }).dx(2).dy(2);
             var selektor = draw.group();
 line = draw.line(100, 100, 100, 75).stroke({ width: 1 });
                             simbol = draw.use(symbol).move(87, 65);
selektor.add(line);
             selektor.add(simbol);
             selektor.style('cursor', 'pointer');
             selektor.on('mouseover',function () {
                 this.children()[0].stroke({ color: '#f06' });
                 this.children()[1].target.children()[0].stroke({ color: '#f06' });
                 this.children()[1].target.children()[1].stroke({ color: '#f06' });
             });
             selektor.on('mouseout',function () {
                 alert("mout");
                 this.children()[0].stroke({ color: '#000000' });
                 this.children()[1].target.children()[0].stroke({ color: '#000000' });
                 this.children()[1].target.children()[1].stroke({ color: '#000000' });
             });

Would be nice if you could format your code.
The event handling in svg.js is no magic.
When it works in all Browsers except Chrome it looks like a bug in chrome and not svg.js

Your're right. My post could stay as a warning for other users who might use same funcionality.


Debounce Cursor Moves When Jumping To Message/CommandLine

Describe the bug
mouse scrolling animation is triggered randomly when typing. This is so distracting.
https://user-images.githubusercontent.com/21097695/123016096-81971380-d3e7-11eb-8c6c-d33c400245aa.mp4
Desktop (please complete the following information):

OS: Windows 10
Neovide Version [built from source]
Neovim Version [0.5.0]

Please run neovide --log and paste the results here:
neovide_rCURRENT.log

Do you have lsp enabled? I think what might be happening is there is a message which is sending the cursor to the commandline every time it pops up.
I'll have to think a bit about how to fix that...

yes I have nvim builtin lsp enabled. You are correct. this is not reproducible in :new buffer

If you're using nvim-compe, for now put set shortmess+=c in your init.vim/.vimrc.

Thanks for the workaround @shaunsingh . Adding shortmess cmd minimized issue.. But still issue is there.

is this somehow related to #341 ?

@PyGamer0 @Kethku For me issue is still there even after this fix. Is it working for you guys with lsp enabled?
https://user-images.githubusercontent.com/21097695/123539555-f8217180-d757-11eb-9888-b9f29ebc767a.mp4

@Kethku Is this fixed completely. I am still seeing debounce effect randomly. But its not frequent as before but it still exists.


Astro vs X - Better sidebars via changing heading levels

Makes for a nicer sidebar, also extracted the most common differences that kept getting repeated throughout each framework and put them at the very top in a "usually this is the difference" section.

Alright, I'm acknowledging that:
the TITLE of the page is ASTRO vs X (which I like becase Astro is the important word, and SEO)
every HEADER is X vs ASTRO (which I think is important, or else the sidebar says "Astro... "Astro... etc. and is more difficult to navigate)
the language chart is ASTRO vs JSX (with corresponding rows in that order) (Which I also think makes sense because you want Astro first, to show what it IS, and then, here's what jsx is so you can compare. Plus, don't have to redo the table!)
So individually, all those things are ordered properly (imo). But together, it's inconsistent.
My gut says to err on keeping each individual element in its best version, even at the expense of overall consistency.

My gut says to err on keeping each individual element in its best version, even at the expense of overall consistency.

Agreed. I think each individual part is the way it is for good reasons and consistency doesn’t really justify changing them.

Not saying everything in the intro was strictly speaking needed... but I like having some clean, spaced out lines on the page with lots of white space as a first impression, before getting into the wall-of-text comparisons. So that's what I went with.


docker启动不起来

你好
docker run -d -p 1066:1066  hanhongyong/ms365-e5-renew-x:latest
启动不了容器
这是log
{"log":"\u001b[40m\u001b[32minfo\u001b[39m\u001b[22m\u001b[49m: Microsoft.Hosting.Lifetime[0]\n","stream":"stdout","time":"2023-01-26T08:39:36.218931443Z"}
{"log":"      Application is shutting down...\n","stream":"stdout","time":"2023-01-26T08:39:36.218987023Z"}
{"log":"\u001b[40m\u001b[1m\u001b[33mwarn\u001b[39m\u001b[22m\u001b[49m: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]\n","stream":"stdout","time":"2023-01-26T08:39:36.293889113Z"}
{"log":"      Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.\n","stream":"stdout","time":"2023-01-26T08:39:36.294025437Z"}
{"log":"\u001b[40m\u001b[1m\u001b[33mwarn\u001b[39m\u001b[22m\u001b[49m: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]\n","stream":"stdout","time":"2023-01-26T08:39:36.408418543Z"}
{"log":"      No XML encryptor configured. Key {bc329cf5-a681-461f-9283-f91ab4cbde2e} may be persisted to storage in unencrypted form.\n","stream":"stdout","time":"2023-01-26T08:39:36.408467944Z"}
{"log":"\u001b[40m\u001b[32minfo\u001b[39m\u001b[22m\u001b[49m: Microsoft.Hosting.Lifetime[0]\n","stream":"stdout","time":"2023-01-26T08:39:41.292160432Z"}
{"log":"      Waiting for the host to be disposed. Ensure all 'IHost' instances are wrapped in 'using' blocks.\n","stream":"stdout","time":"2023-01-26T08:39:41.292204559Z"}
{"log":"\u001b[40m\u001b[32minfo\u001b[39m\u001b[22m\u001b[49m: Microsoft.Hosting.Lifetime[0]\n","stream":"stdout","time":"2023-01-26T08:39:41.910594777Z"}
{"log":"      Now listening on: http://[::]:1066\n","stream":"stdout","time":"2023-01-26T08:39:41.910646512Z"}
{"log":"\u001b[40m\u001b[32minfo\u001b[39m\u001b[22m\u001b[49m: Microsoft.Hosting.Lifetime[0]\n","stream":"stdout","time":"2023-01-26T08:39:41.911127603Z"}
{"log":"      Application started. Press Ctrl+C to shut down.\n","stream":"stdout","time":"2023-01-26T08:39:41.911144358Z"}
{"log":"\u001b[40m\u001b[32minfo\u001b[39m\u001b[22m\u001b[49m: Microsoft.Hosting.Lifetime[0]\n","stream":"stdout","time":"2023-01-26T08:39:41.911344887Z"}
{"log":"      Hosting environment: Production\n","stream":"stdout","time":"2023-01-26T08:39:41.911359791Z"}
{"log":"\u001b[40m\u001b[32minfo\u001b[39m\u001b[22m\u001b[49m: Microsoft.Hosting.Lifetime[0]\n","stream":"stdout","time":"2023-01-26T08:39:41.911556696Z"}
{"log":"      Content root path: /app\n","stream":"stdout","time":"2023-01-26T08:39:41.911571321Z"}

vps是ipv6的，和这个是不是有关系

是不是vps的机器的不是amd的？

用arm版，作者的第一个arm的用不了

hanhongyong/ms365-e5-renew-x:arm64v8
试试这个？


Fix null reference exceptions on background task when looking for mis…

…sing imports.

First reviewer can merge this


Incorrect value for long strings/integers?

I have a very simple node script called parse.js:
var argv = require('yargs').argv;

console.log('* ' + argv._[0]);

When I run it from the command-line (Windows) ...
> node parse.js<PHONE_NUMBER>4888976
It's output is:
*<PHONE_NUMBER>4888980
As you can see, it's a few digits out. Could someone please explain why this is happening?

@gullyfoyle<PHONE_NUMBER>4888976 is larger than V8's Number.MAX_SAFE_INTEGER:
> Number.MAX_SAFE_INTEGER
9007199254740991
><PHONE_NUMBER>4888976 > Number.MAX_SAFE_INTEGER
true

Integers larger than this value begin to lose procession. One option would be accepting this value as a string:
var argv = require('yargs')
  .option('foo', {
    type: 'string'
  })

and then using a module like https://www.npmjs.com/package/big-integer for performing numeric operations.

Thank you so much. I knew it was probably something simple on my part.


No data visible in Sandbox

I have had multiple tries at installing the accelerator and the only successful one is in the default environment. It does not work in the Development environment which I can see from install instructions, so the current attempt is to a Sandbox environment.
While there are some disadvantages to following MS advice to installing to a Sandbox environment outlined here, this seems to be the recommended way to customise and manage the lifecycle.
Prior to installing the Project-Accelerator the data should be visible after installing the Microsoft Project Service Core. If I navigate through the managed solution called Project (msdyn_Project) in the default environment it has 3 components. One of them is a table called Project which has a list of current projects (including PWA in it). The same thing in the Sandbox has 3 components, but the table is called Plan and is blank.
I've run past this stage in other attempts but it seems to me if I can't see anything here, installing the Accelerator isn't going to fix it.
I've manually added connections into the environment to Planner, Project Roadmap and Project Online to see if this would make any difference, but no change. I've followed this  including setting up the environment without Dynamics M365 Apps, and also changed the security as specified.
Can anyone give me any hints on how to see why the plans table isn't being populated ... ?
How can I see what process / permission / flow / ? is failing and what population of the table is reliant on?
There are no errors anywhere I can see.
Any help appreciated.
Thanks.

Installed to default environment where it 'just works'. Gave up on multiple environments.


[Feature request] Deduplication of favorites

Cool extension, definitely makes for a better front page then the traditional FA one! Thanks.
Just a suggestion, but I often find that many people favorite the same piece of art in my list, it would be great to be able to only show the submission once, even if multiple people have favorited it.
If you want to attribute the favorite you could make the "Faved By" element a list.

Sorry for the late response! I hear you, sometimes posts really ring within the circle I follow and it fills the feed.
This is a contentious case where I also use it a lot and have an opinion and it happens to be that I want it ungrouped to see big posts take up more real estate :sweat_smile: but I could definitely just add a toggle switch for grouped/ungrouped.
The favs are ordered in chronological order so where should the grouped listing end up? I'd lean to most recently faved so it tends to hit the front page more often if it's popular.


Error with Azure DevOps 2020 onPremise

Hi,
I upgraded Azure DevOps on premise from version 2019 to 2020.1. Now we have problems with the Initialize Job task on release. The log is

2021-04-07T15:43:13.2796823Z ##[error]Downloading artifacts failed: System.AggregateException: One or more errors occurred. (You do not have permissions to perform this operation on the service connection. An Endpoint Administrator should add you to the Endpoint Readers group of this service connection.) ---> Microsoft.VisualStudio.Services.Security.AccessCheckException: You do not have permissions to perform this operation on the service connection. An Endpoint Administrator should add you to the Endpoint Readers group of this service connection.
   at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.HandleResponseAsync(HttpResponseMessage response, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.SendAsync(HttpRequestMessage message, HttpCompletionOption completionOption, Object userState, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.SendAsync[T](HttpRequestMessage message, Object userState, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.SendAsync[T](HttpMethod method, IEnumerable`1 additionalHeaders, Guid locationId, Object routeValues, ApiResourceVersion version, HttpContent content, IEnumerable`1 queryParameters, Object userState, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
   at Agent.Worker.Release.ReleaseServer.GetReleaseArtifactsFromService(Int32 releaseId, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.Agent.Worker.Release.ReleaseJobExtension.GetReleaseArtifacts(IExecutionContext executionContext)
---> (Inner Exception #0) Microsoft.VisualStudio.Services.Security.AccessCheckException: You do not have permissions to perform this operation on the service connection. An Endpoint Administrator should add you to the Endpoint Readers group of this service connection.
   at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.HandleResponseAsync(HttpResponseMessage response, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.SendAsync(HttpRequestMessage message, HttpCompletionOption completionOption, Object userState, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.SendAsync[T](HttpRequestMessage message, Object userState, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.SendAsync[T](HttpMethod method, IEnumerable`1 additionalHeaders, Guid locationId, Object routeValues, ApiResourceVersion version, HttpContent content, IEnumerable`1 queryParameters, Object userState, CancellationToken cancellationToken)<---

2021-04-07T15:43:13.2851674Z ##[error]One or more errors occurred. (You do not have permissions to perform this operation on the service connection. An Endpoint Administrator should add you to the Endpoint Readers group of this service connection.)

So far, I tried the same thing in a developer stage azure devops 2019 and we don't have issues. So, I think that the extension have a compability problem. We are making the connection to a Azure Devops 2020.1 on cloud through token connection.

I am experiencing the exact same symptoms.
I first experienced it testing an upgrade from TFS 2017 (update 2) to DevOps Server 2020.0.1 last week. The artifact link was to a DevOps Server 2019 instance.
To investigate further, I created 2 new DevOps Server 2020.0.1 (x64) instances. The 1st instance is my repo\build server, the 2nd the "Deployment" server. I just completed testing and encountered the same error. The agent and worker logs (machine/user names masked) are attached.
Worker_20210408-022900-utc.log
Agent_20210408-021222-utc.log
The setup on the 2nd instance is:
Service connection

Property
Value

Type
Azure Repos/Team Foundation Server

Authentication
Token Based Authentication

Connect URL
1st instance

Security
Both the Endpoint Administrators group and my domain account are assigned the "Administrator" role.

Pipeline
Permissions: Any pipeline may use this resource

Project
Permissions: Only current project.

Agent

Property
Value

Version
2.170.1

Run mode
Command line via Run.cmd

User
My domain account

Release pipeline
The test release pipeline has an ExternalTfsBuild artifact linked to a build on the 1st instance. The latest version of the TFS artifacts for Release Management extension is installed.

FYI, my issue was resolved by adding user: Project Collection Build Service (MyProject); to the "User" role of the service connection my release is accessing via the ExternalTfsBuild artifact link.


NOBUG: Fix gatsby build error

Jira Ticket:
None
Description:

Gatsby build error (https://github.com/bcgov/bcparks.ca/actions/runs/11620216166) was caused by library updates in the previous PR (https://github.com/bcgov/bcparks.ca/pull/1503), bring the Cheerio version back as a workaround

Approved to fix the failing build, but I'd be curious to hear what the error is. Hopefully it's possible to upgrade this some day to the stable version 👍

Yea it was a syntax error in the library. There should be another way to fix it so I'll investigate whenever I have time.
  14 | const { tree } = require('./tree')
  15 |
> 16 | const [nodeMajor, nodeMinor] = process.versions.node.split('.').map(v => Number(v))
     |                                       ^
  17 |
  18 | class BodyAsyncIterable {
  19 |   constructor (body) {

  WebpackError:TypeError: Cannot read properties of undefined (reading 'split')


evp_pkey_ctx_setget_params_to_ctrl(): Always properly set ctx.action_type

Fixes #24698
Some applicable translations are bidirectional so they have NONE action_type. However we need to set the real action_type in the ctx.
Tests exempted because this is not testable without an engine implementing the relevant ctrls.

That transient CI failure in BSD appears to be showing up again alot (though isn't relevant here)

This pull request is ready to merge

Merged to all the active branches. Thank you for the reviews.


fix: deleteDir  retry will fail at root workspace

Why:

deleteDir will fail on root workspace while retry

/lgtm
/approve


Details field in Status struct is not decoded properly

Bug Report
A recent change (https://github.com/hyperium/tonic/pull/345) added base64 encode/decode to the custom details member of Status.  Unfortunately it was not implemented properly, and as a result the details sent by the server are not the details received by the client.
Version
tonic v0.2.1
Platform
Linux shannon.assur.io 5.6.11-300.fc32.x86_64 #1 SMP Wed May 6 19:12:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Crates
tonic
Description
The test in https://github.com/hyperium/tonic/pull/345 is inadequate, as it tests only with a custom details value of &[1], meaning a single byte with value 0x01.
The encoding logic uses the base64 crate with an explicit config:
https://github.com/hyperium/tonic/blob/372da52e96114ca76cc221f3c598be82bfae970c/tonic/src/status.rs#L457
That part is correct.  The decode logic on the other hand is incorrect:
https://github.com/hyperium/tonic/blob/372da52e96114ca76cc221f3c598be82bfae970c/tonic/src/status.rs#L348-L349
It should be using decode_config with base64::STANDARD_NO_PAD.

While I still suspect there's a problem with missing decode_config, that's actually not the cause of my test failure.
Before this PR #345, any bytes passed with with_details would be returned verbatim from details().  That is no longer the case.  When creating a Status object with with_details(), the details are immediately base64 encoded, so Status::details() returns the base64 encoded details.  However, Status deserialized from an HTTP response header decodes the base64 encoding, so that Status::details() returns the decoded details.
This broke some tests I had that relied on the previous behavior.  Basically, I manually implemented base64 encoding/decode to work around the fact that tonic didn't do that.

Sorry for the mistaken bug report.  The change to  the behavior of details()  I noted above in the latest relese 0.2.1 is what caused my tests to fail, not a problem with base64 encoding as I first thought.
FWIW, I proved this to myself with a unit test, since the existing test code around custom details values was pretty minimal:
https://github.com/assuriosw/tonic/blob/bd84aab4846b5d45792187f2aed59f09d0f7f699/tonic/src/status.rs#L750-L760


Learn about authorization

Learn how to authorize frontend applications with backend (JWT).

https://www.youtube.com/watch?v=X80nJ5T7YpE


[Bug]:

Check for existing bug reports before submitting.

[X] I searched for existing Bug Reports and found no similar reports.

Expected Behavior
The plugin seems to have just stop working after the most recent update.  I get the attached error.

Current behaviour
see attachment
Reproduction
I really don't know.  After the update it seems to have been broken.
Which Operating Systems are you using?

[ ] Android
[ ] iPhone/iPad
[ ] Linux
[X] macOS
[ ] Windows

Obsidian Version Check
1.3.5
Plugin Version
3.4.5
Confirmation

[X] I have disabled all other plugins and the issue still persists.

Possible solution
No response

Hello!
Version 4.0 of RPG Manager has just been released. This is a complete re-writing of the plugin, and will impact all opened issues.
I am therefore closing this issue as it was related to v3.4 (now unsupported), but please feel free to re-open the task if the issue persists in the new version.
Ciao
Carlo


documentation

matchicons.lua
after spending more than 30 minutes looking, does matchicons.lua have to require dirx to work, matchicons.lua and https://github.com/chrisant996/clink-gizmos/issues/3 don't have this info both. the available options of functions from dirx is way more than the default cmd dir, is it able to work with the default dir
vscode_shell_integration.lua
installed clink-gizmos it comes with vscode_shell_integration.lua enabled.
vscode does have shell_integration related things, is it necessary to have vscode_shell_integration.lua to work with vscode

They're unrelated to each other.
Matchicons.lua adds icons to completions in Clink.
Dirx is an unrelated program that's a replacement for the dir command, and dirx happens to be able to show icons.
If you want fzf to show icons, then you need dirx or eza (which I'm pretty sure I documented explicitly, and included directions for setting up fzf to use dirx for icons).

those are two questions.
Matchicons.lua itself didn't mention any about dirx, while fzf.lua is the one did. usually, like Terminal-Icons module for powershell, it is able to display icons for files for ls command automatically. while Matchicons.lua itself didn't mention any about usage, so this issue is opened.
for the other one
vscode_shell_integration.lua it only mentioned Automatically enables shell integration for VSCode embedded terminal windows. in its documentation
it would be good if there is some explanation for new comers

usually, like Terminal-Icons module for powershell, it is able to display icons for files for ls command automatically.

CMD and Powershell are vastly different.  Don't try to compare them like that.

while Matchicons.lua itself didn't mention any about usage, so this issue is opened.

Matchicons.lua docs say what it does.
I'm not going to even try to document all the things it doesn't do.

for the other one
vscode_shell_integration.lua it only mentioned Automatically enables shell integration for VSCode embedded terminal windows. in its documentation
it would be good if there is some explanation for new comers

I recommend to refer to the VSCode documentation to learn about VSCode's shell integration feature.
I'm not going to spend my personal time documenting answers to all kinds of questions people could potentially ask.  Especially when they can answer the questions themselves with an Internet search.
If you would like to spend your time that way, I am happy to review a PR that you submit with suggested documentation changes.
I recognize that reading documentation and doing searches in a second language can be difficult and time consuming.  But that's not a problem I'm able to invest time in solving.


Delete operational-excellence.md

Reliability and operational-excellence under Azure Virtual network has exact same content. I think we can delete redundant content.
https://docs.microsoft.com/en-us/azure/architecture/framework/services/networking/azure-virtual-network/reliability
https://docs.microsoft.com/en-us/azure/architecture/framework/services/networking/azure-virtual-network/operational-excellence

Request you to review this review @v-stacywray
Cc: @Jak-MS

We cannot delete without a redirect in place.  @rakeshvarade89 -- since you are an FTE, you should be using the well-architected-pr repo for suggestions.  You'll get build feedback such as this.  Please close this here and re-open in well-architected-pr


[In-progress] Solve NFC OOM issue by DB

Moving NFC to ISPN is good for add/isMissing, but bad for the getAllMissing/clearMissing. I found ISPN doc mentioned that cache.keySet is a very expensive and VERY MUCH likely to cause OOM. The doc even suggests using it in testing evn but NOT on prod.
OTOH, DB fits very naturally when it comes to getAll/cleanMissing - a single sql is enough. I came up with this fix using H2. Please review it.
What I am thinking is: maybe we can use DB + ISPN. Using DB for backend data store, using ISPN to cache isMissing result. So that we can get good performance on both query operations and isMissing calls (which is on critical path). At the same time, we can avoid huge memory footprint. How do you think?

retest this please

@ruhan1 Are we planning to close this, or merge it eventually? I'm not sure what the status of this PR is.

This is not needed. Close it.

This is not needed. Close it.


Rendering UBOs

Should be able to render structs like this in the output GLSL:
layout (std140) uniform MyCustomData {
  highp float TIME;
  vec2 VIEWPORT_SIZE;
};

It works!
The usage is that you define a case class, add it to your env as an intersection type (with &) which allows you access to the fields, then you can write the UBO struct into your doc using ubo[MyCaseClass].

Fixes: https://github.com/PurpleKingdomGames/ultraviolet/pull/17


Align prompt position on the screen

I am using<EMAIL_ADDRESS>and the kind of task I'm using is showing subjects images. There is an intertrial interval between each image where subjects see a white cross for one second. I'd like to display a sentence under the image AND the same sentence under the white cross during the intertrial interval. I know I can achieve this through the PROMPT keyword like this:
type: jsPsychHtmlKeyboardResponse,
prompt: function(){return '
Each correct response gives you '+jsPsych.timelineVariable("points")+' point(s)
'},

I also want to fix the position of this sentence so that it doesn't change between the image and the white cross. I was able to do this by tuning the paragraph css so that this sentence is at the same position during the imaging trial and the intertrial interval. However, once I tried it on another computer with a different screen size, the positions are off again. Is there a solution to this?

Hi @HuangHam,
Forgive the quick response without much detail, but you could wrap the white cross in a
 that is the same height as the image. If the images vary in size you can wrap the images in a
 as well to ensure a consistent height.


Prometheus 2.54.0 error when starting

Image Name and Version
icr.io/ibmz/prometheus:2.54.0
Describe the bug
When starting the image, I get an error. Looks like the entrypoint is not correct.
To Reproduce
Steps to reproduce the behavior:
Started with the following command:
docker run --name prometheus --restart always -d --network monitoring -v prometheus-data:/prometheus -p 9090:9090 -d icr.io/ibmz/prometheus:2.54.0
Expected behavior
Start of the container without this error
Screenshots
Additional context
Add any other context about the problem here.

Screenshot

@hem2023 Apologies in advance for an unrelated comment - please try VictoriaMetrics instead. It is significantly more effective & efficient than Prometheues, while being a drop-in replacement.

@hem2023 thanks for lettings us know! As of this moment I am unable to recreate the failure.. I will continue to look into this though and will let you know if I can recreate the error you see.
Are you still encountering the entrypoint error?
~/prometheus$ docker run --name prometheus --restart always -d -v prometheus-data:/prometheus -p 9090:9090 -d icr.io/ibmz/prometheus:2.54.0
ff14e7b5b040d6f5e4b601455afc60c0f92fe41c6e5d7da8ccdf59e64f25cff7

~/prometheus$ docker logs ff14e7b5b040d6f5e4b601455afc60c0f92fe41c6e5d7da8ccdf59e64f25cff7
ts=2024-09-19T20:05:49.204Z caller=main.go:601 level=info msg="No time or size retention was set so using the default time retention" duration=15d
ts=2024-09-19T20:05:49.204Z caller=main.go:645 level=info msg="Starting Prometheus Server" mode=server version="(version=2.54.0, branch=non-git, revision=non-git)"
ts=2024-09-19T20:05:49.204Z caller=main.go:650 level=info build_context="(go=go1.22.5, platform=linux/s390x, user=root@buildkitsandbox, date=20240822-18:27:18, tags=netgo,builtinassets,stringlabels)"


hassbian-config upgrade homeassistant fails with wrong hash

Home Assistant release with the issue:

0.98.1
Last working Home Assistant release (if known):
0.97.2
Operating environment (Hass.io/Docker/Windows/etc.):

Hassibian
Component/platform:

Description of problem:
hassbian-config upgrade homeassistant
Fails to install new version
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):
INFO:homeassistant.util.package:Attempting install of home-assistant-frontend==20190828.0
ERROR:homeassistant.util.package:Unable to install package home-assistant-frontend==20190828.0: ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
    home-assistant-frontend==20190828.0 from https://www.piwheels.org/simple/home-assistant-frontend/home_assistant_frontend-20190828.0-py3-none-any.whl#sha256=45459517d4c0d41d217c93ad1e457fc7cf589bbeb041d69677359b9d65f61f62 (from -c /srv/homeassistant/lib/python3.7/site-packages/homeassistant/package_constraints.txt (line 14)):
        Expected sha256 45459517d4c0d41d217c93ad1e457fc7cf589bbeb041d69677359b9d65f61f62
             Got        7b06e5b2db4606b7a4c812ff9cd96e1909516598643dddbacf42b1ee1e137940

Additional information:

Which version of python do you have installed?
Do you have the latest version of the hassbian-config? Try hassbian-config --version to get your installed version.
If you do not have the latest version of either installed, I would suggest to update them first and then see if the issue persists.
Hopefully this resolves your problem, however if it does not you should consider opening an issue on the Github page of hassbian-config.

Python 3.7.3
hassbian-config --version
0.13.1
All current versions.

The only way I could get this working was manually downloading https://www.piwheels.org/simple/home-assistant-frontend/home_assistant_frontend-20190828.0-py3-none-any.whl
Check the hash
sha256sum home_assistant_frontend-20190828.0-py3-none-any.whl
45459517d4c0d41d217c93ad1e457fc7cf589bbeb041d69677359b9d65f61f62  home_assistant_frontend-20190828.0-py3-none-any.whl
Which is correct...
Then
pip3 install home_assistant_frontend-20190828.0-py3-none-any.whl

Glad you got it working.
Maybe your connection was disrupted during the initial download via hassbian-config upgrade homeassistant. Still I would recommend to create another issue in the hassbian-config repo to really get to the bottom of this issue

Not it either. I tried to install again via the script and it failed with the same error.

Have you upgraded from 0.97.2 to 0.98.1?
Because I have upgraded from 0.97.2 to 0.98.0 and then to 0.98.1 and I did not have any issues.

This has been a longer issue with piwheels according to this issue: #24968

So I see this is a issue they won't fix then. Sounds like someone needs a push to find out why.


Remove scipy stubs

Fix https://github.com/microsoft/python-type-stubs/issues/320. Stop bundling our own (ancient) scipy stubs in favor of https://github.com/jorenham/scipy-stubs.

no pipeline updates? these were ours i guess

When updating our bundled stubs, we just pull (mirror, including deletes) everything from here.


Write tests

Per title.

Addressed at https://github.com/cansin/next-with-sitemap/commit/933b4d1211c55f8dd9a44ee3ce8a9c4c9b28d420


"Incomplete header" on capsule that works with other browsers

Hi folks! I've deployed a capsule to gemini://byjp.cc, but Lagrange shows an "Incomplete Header" error when I visit it on my mac (v1.17.6), on iPhone (v1.17 (9) 2024-04-20).
This capsule works as expected using amfora (amfora gemini://byjp.cc), and works "manually" (with openssl s_client -crlf -connect byjp.cc:1965, typing "gemini://byjp.cc" and hitting return).
What's really weird is running the docker container locally, instead of with fly.io which is what's serving the production capsule, seems to be fine (using the same keys, and using /etc/hosts to point that domain to localhost).
I'd think this is a problem with how I've set up fly.io to serve my container, but amfora and openssl working seem to imply this isn't the case. I've checked the output from the openssl command to the fly.io hosted agora container and the locally served agora container, and they seem as identical as I think they need to be.
Any ideas? Is there a debug mode for Lagrange that would let me see the request/response text to debug further? What am I missing?

A guide for building my container locally, if anyone wants to try
I don't think it'd be necessary, but you can try the build locally yourself if you like (⚠ it's a substantial git repo of ~240MB, even shallow; and the rust builder container for amfora is ~500MB). The following assumes you have taskfile.dev, gohugo.io, pagefind.app, docker installed locally.
# Show my fly.io served capsule is broken (assumes macOS)
$ open /Applications/Lagrange.app "gemini://byjp.cc"

# Clone my repo, as little as is necessary
$ git clone --depth=1 https://github.com/by-jp/www.byjp.me.git

# Build my capsule, removing the parts meant for HTML servers
$ task build gemini-reduce

# Build the docker container
$ docker build -t byjp.cc .

# Run the docker container locally as a daemon
$ docker run -d -t -p 1965:1965 byjp-cc

# Add my domain to your /etc/hosts file, as a quick hack
$ echo "\n<IP_ADDRESS> byjp.cc" | sudo tee -a /etc/hosts

# Check your machine is hitting localhost for my domain
$ ping byjp.cc
PING byjp.cc (<IP_ADDRESS>): 56 data bytes

# Use amfora to check the local capsule is working
$ amfora gemini://byjp.cc

# Open your locally served capsule locally (assuming macOS)
$ open /Applications/Lagrange.app "gemini://byjp.cc"

When I try to connect to your server manually with openssl, I get this:
CONNECTED(00000003)
write:errno=104
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 299 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)

Something appears wrong here on your end... Have you tried connecting to your server from outside your local network, for example via a tethered phone, through a VPN, from a VPS, etc.?

Is there a debug mode for Lagrange that would let me see the request/response text to debug further?

There is no such mode, unless you rebuild the app (and the_Foundation) with debug messages enabled. However, since the problem can be reproduced without Lagrange, this appears unnecessary.

Great spot — my local network, or more likely something that affects terminal applications on my mac, is doing… something that's making my fly.io server look like it works when it doesn't.
I really appreciate the quick reply! I'll investigate and post here in case there's something stupid or weird that others may benefit from. Thank you!

🤦♂ I should have searched the fly.io forum; it looks like the shared IPv4 addresses they use prevent TCP-only apps like Agate from working correctly with in-app TLS termination.
Running fly ips allocate-v4, accepting the $2/mo fee, and removing the shared IP address from my app fixed the issue 😊
Thanks again @skyjake!


Error installing in Delphi 7

1: res file does not exist, it is recreated by delphy 7.
2: there is no.cfg file
3: when compiling Delphi 7 says that ULONG_PTR is undefined

PR are welcome, i can't give any delphi 7 support

You may add to source:
type ULONG_PTR = integer;


Clarify Ls-Series caching policy

Updated discussion on disk throughput to clarify that Ls attached disks are not cached (and why).

@DavidBerg-MSFT : Thanks for your contribution! The author, @jonbeck7, has been notified to review your proposed change.


Add Scope for BelgianGovernment.Belgium-eIDmiddleware version 5.0.5498

null
Microsoft Reviewers: Open in CodeFlow

@wingetbot waivers Add Validation-No-Executables


Feature request: Add includable module or Rails concern

As a Quality of life improvement, it would look much nicer and feel more idiomatic if we could do
include Gutentag::Taggable

instead of
Gutentag::ActiveRecord.call self

If you agree, I can submit a PR that does this

This has certainly been considered previously - see #30 and then #35. I'm happy enough to stick with the current approach, though the offer of a PR is certainly appreciated :)

My bad, I used https://github.com/pat/gutentag/issues?utf8=✓&q=is%3Aissue+concern+ to search for this and #30 is not in there because it doesn't contain the word concern, #35 is not in there because it's not an issue 😆
Feel free to close as wontfix although I'd certainly still appreciate an additional "convenience module" like this:
module Taggable
  def Taggable.included(klass)
    Gutentag::ActiveRecord.call klass
  end
end

I think I'll just close this without the convenience module - I'd rather avoid multiple ways of doing things, keeping the interface focused, though it is a neat suggestion.


Sample does not work on released Lollipop 5.0.

Sample does not compile with the released Lollipop 5.0

Could not reproduce the issue.


All AIDER_* environment vars may now be placed within .env

This PR addresses #630. I have left it in draft mode as I plan to add doc updates and perhaps some additional tests, but this is a first look.

This looks great to me. Some doc updates would be a nice addition if you can. I can also do it after the merge.
Let me know when you're ready to merge.

Shall I just merge this?

Ah, sorry I didn't explain further. Yes the code to generate the docs is in the repo.
It uses args formatter to render the sample yaml file, as well as a pretty markdown options page for the docs website.
https://github.com/paul-gauthier/aider/blob/main/aider/args_formatter.py
There's a docs build script that uses cog to render these sorts of docs in a pre-push git hook.
https://github.com/paul-gauthier/aider/blob/main/scripts/update-docs.sh

Can you fix the merge conflicts and the temp dir issue causing Windows tests to fail? I can merge after that.

Awesome, thanks for this!

FYI, I updated the docs and added a help formatter to produce a sample .env file.
https://aider.chat/docs/dotenv.html


Use the NSConcreteTask.setStartsNewProcessGroup private API to terminate subprocesses when the parent process exits

Would fix https://github.com/Carthage/ReactiveTask/issues/3. I'm not sure how to correctly test this but this passes the test suites at least.

Ugh. I hate using private APIs. But this seems like it's probably worth it.

Thanks @mdiep. I'm not a fan of this too, but it should work nicely.
However, it occurs to me that this would not be ideal in some cases, so I'll add a parameter to launch method to control the behavior.

Just updated: 9143189


Bottom to Top button should also be present in Photodetails Page for mobile users

Problem Description
Bottom to Top button should also be present in Photodetails Page! Since it contains Related Images section, that somewhat increases the length of the page.

Additional context
Want to work on this :)

I don't think this is required

On the desktop, there is no point in keeping that button
On tablets or mobile resolutions, the related images are fairly minimum that we can go to the top in just one swipe

Do wait for the opinions of members and other contributors :)

@hemanth-hk Yes, I agree that there's no point in keeping it in Desktop version, but it needs to be there in Mobile version especially, there it will enhance both user experience and usability!

Maybe it will increase the user experience but I'm not positive on it because as I said the number of related images is less and we can go to the top just in 1 swipe.

I'm inclined to agree with @hemanth-hk here, there is a limited number of related images, so this seems unnecessary.
That said, I'd like to input from @brenoferreira and @akmadian regarding the usability angle here. Blocking this from being worked on until we've discussed it further.

On the vast majority of mobile devices, tapping the top of the screen scrolls you back up to the top, so this functionality is already implemented from the mobile os side. I'm not sure how that functionality works in terms of accessibility though, so this may or may not be a good idea from an accessibility standpoint.
As for improvements to the UX, I don't think this is a good idea. Adding something to the screen that isn't needed is generally not a good idea, especially on smaller screens.

Thanks for your input @akmadian
I'll assign this to @AyanChoudhary so this is included in their upcoming work, one way or another.

Yes, I agree with @akmadian this isn't necessarily related to user accessibility but definitely concerns the UX. @annatuma it would be great if a design mockup could be provided for it.

The reason for the Back to Top button on the results page is just for convenience when users have scrolled maybe 5+ pages down. Users can always just hit the Home button on their keyboard, and on mobile tap the top of the screen does something similar, like @akmadian said.
Since the details page isn't that long, I don't think this is necessary.

Closing because the consensus for this suggestion seems to be that we do not want to move forward with an implementation.


cases where islandora_breadcrumbs caches aren't invalidated

Generally adding member relationships and members seems to generate breadcrumbs okay, but there's some edge cases where they're not showing due to the breadcrumb cache not becoming invalidated when one would expect it to.
STR:

Create a collection repository item; we'll call it B
Add a member to that collection - I created an image item; we'll call it A
Create another collection repository item; we'll call it C
Edit B to have a member relationship to C
Visit A, note the breadcrumbs display "B / A"
Clear the cache via drush cr
Visit A, note the change in breadcrumbs displaying "C / B / A"

Some fun investigation times
Looking at chunk of islandora_breadcrumbs that determines IslandoraBreadcrumbBuilder::applies() to a repository item, the Islandora-centric breadcrumbs don't apply if whatever configured referenceField is empty. So it falls back to the breadcrumb implementation upstream, which currently has broken cache invalidation.
Would seem that any time you're creating objects that don't have parents (yet), you're going to have an inconsistent experience with breadcrumbing.
Building up an applies() based on multiple parameters would help; checking the existence of field_model and checking the field_media_of relationship would let us build up more complete breadcrumbs. Can probably throw in a proof of concept for this if desired
Also I believe the build() implementation is supposed to implement $breadcrumb->addCacheTags()? To have better control over when they're invalidated as well as for that X-Drupal-Cache-Tags support.

@qadan, we call addCacheableDependency for each node in the chain (see https://github.com/islandora/islandora/blob/8.x-1.x/modules/islandora_breadcrumbs/src/IslandoraBreadcrumbBuilder.php#L81) which calls addCacheTags for each one. As far as I understand it, that should take care of it.
As for the applies, I think simply removing the  && !$node->get($this->config->get('referenceField'))->isEmpty() will let accomplish what we need. Simply having the member_of field should be sufficient.
I should have a PR shortly, but I won't be able to test it until I'm done testing a different PR.

Fixed.


Update Parsec C client

The current version of the Parsec C client - which was developed at the IETF hackathon - was designed with the old version of Parsec attestation API in mind. That API has been changed, prompting the need for an update to the client.

Done, see https://github.com/ionut-arm/parsec-se-driver/commit/4fa927dbc4102bb7ae62fe3c5e60f45285b71259


Provide an OpenSearch API source

Is your feature request related to a problem? Please describe.
I'd like to be able to point existing OpenSearch clients that perform ingestion to Data Prepper instead.
Describe the solution you'd like
Create a new source - opensearch_api which supports the Document APIs that perform ingestion.
Minimally, this can be:
source:
  opensearch_api:

Some more options:
source:
  opensearch_api:
    port: 9200
    ssl: true
    ssl_certificate_file: /path/to/certificate
    ssl_key_file: /path/to/private.key
    thread_count: 200
    authentication:
      http_basic:
        username: ingest_client
        password: ${{aws_secrets:ingest:password}}

Additional context
This can start with only the _bulk API and this could supersede #248. Over time we can add the other endpoints as well.
This would be available for _bulk using the path:
https://localhost:9200/_bulk

Tasks

[ ] #248
[ ] Support other ingestion APIs

Ideally, we can combine much of this code with the http source. It may be good to add a new project to Data Prepper for http-server-common which supports common HTTP code. Much of the code can be similar between the opensearch_api source and the http source.


experiment loop

I've wrote a little experiment loop that pretty much ports from Pinot. https://github.com/choderalab/pinot/tree/master/pinot/app
@jchodera I love your 'loss function in dataset' idea and I've included in my datasets object. meanwhile I also feel like to have loss functions defined over graphs would just be a little bit more flexible:
https://github.com/choderalab/espaloma/blob/master/espaloma/metrics.py
let me know what do you think

Sounds good, will update from way "loss function in dataset" was attempted in https://github.com/choderalab/espaloma/pull/20


chore(main): release 1.18.0

:robot: I have created a release beep boop
1.18.0 (2023-03-17)
Features

release: test release and publishing triggers (4426b88)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/briancaffey/pulumi-aws-django/releases/tag/v1.18.0 :sunflower:


Bolt  issue

We highly discourage implementing the code to parse request body data. It's not just for the sake of simplicity, but also for enhanced security. The Bolt framework verifies if a request originates from Slack and ensures the data is never manipulated. For this purpose, the framework parses body data as-is and verifies the x-slack-signature header in the request using the "Signing Secret", which is shared exclusively between Slack and you. Therefore, please consider relying on the Bolt framework instead of trying to implement everything on your own.
As you mentioned yesterday i have tried  using bolt but i am not receiving any payload when clicking  button in my slackapp.can you provide any sample code in java  to access the interactivepayload.

Hi @Harishkumarcratoflow, I will reply to this question in #1188

@seratch Ok

@PostMapping(value = "/slack-response", produces = MediaType.APPLICATION_JSON_VALUE)
public String responseAction(@RequestBody String payload,
@RequestHeader("X-Slack-Signature") String slackSignature,
@RequestHeader("X-Slack-Request-Timestamp") String requestTimestamp) {
	slackApp.event(ReactionAddedEvent.class, (req, ctx) -> {
		ReactionAddedEvent event = req.getEvent();
		if (event.getReaction().equals("white_check_mark")) {
			ChatPostMessageResponse message = ctx.client().chatPostMessage(r -> r
					.channel(event.getItem().getChannel()).threadTs(event.getItem().getTs())
					.text("<@" + event.getUser() + "> Thank you! We greatly appreciate your efforts :two_hearts:"));
			if (!message.isOk()) {
				ctx.logger.error("chat.postMessage failed: {}", message.getError());
			}
		}
		return ctx.ack();
	});

return "Ok";
}  this what i was trying but i cannot figure out the issue  when an event is happeing i am unable to process it  and send a response


Refactor and bug fix for the facebook "cover" for issue #378

In update_or_create_facebook_auth_response() do not sent in a value for
facebook_user_id as a search criteria, it is already in the defaults.
In organization_retrieve_for_api() move the facebook heal code to voter
controllers voter_retrieve_for_api().

👍


WTSVirtualChannelWrite failed!

When I use the /gfx-h264 param on the client side, The server side occurs the errors, as follows:
(I have already setup openh264 on both client and server)
[02:47:18:377] [16208:00000850] [INFO][com.freerdp.server.shadow.win] - SurfaceCopy x: 0 y: 0 width: 1920 height: 1080 right: 1920 bottom: 1080
[02:47:18:388] [16208:00001b5c] [INFO][com.freerdp.client.shadow] - Client from <IP_ADDRESS> is activated (1920x1080@32)
[02:47:18:424] [16208:00000850] [INFO][com.freerdp.server.shadow.win] - SurfaceCopy x: 1792 y: 256 width: 64 height: 192 right: 1856 bottom: 448
[02:47:18:431] [16208:00001b5c] [ERROR][com.freerdp.channels.rdpgfx.server] - WTSVirtualChannelWrite failed!
[02:47:18:431] [16208:00001b5c] [ERROR][com.freerdp.client.shadow] - SurfaceFrameCommand failed with error 1359
[02:47:18:431] [16208:00001b5c] [ERROR][com.freerdp.client.shadow] - Failed to send surface update
[02:47:18:431] [16208:00001b5c] [ERROR][com.freerdp.channels.rdpgfx.server] - WTSVirtualChannelWrite failed!
[02:47:18:431] [16208:00001b5c] [ERROR][com.freerdp.client.shadow] - DeleteSurface failed with error 1359
[02:47:18:431] [16208:00001b5c] [WARN][com.freerdp.client.shadow] - GFX release surface failure!
I found "context->priv->rdpgfx_channel"  NULL(0x00)? at line 123 in rdpgfx_main.c
Is there anyone can help? Thanks in advance!

@Zoson please provide details of your compilations and how you setup openh264.
Did you compile openh264 and what is version of same?

@ganeshjkale @akallabeth I think it's not about openh264, it seems like the RdpgfxServerContext->rdpgfx_channel is not initialized which is NULL (0x0000000000).
When I debug at line 1281 in libfreerdp/core/server.c.

@ganeshjkale @akallabeth The only code about to init the client->rdpgfx is at line 1788 in shadow_client.c, but it never be called!!!?

@ganeshjkale @akallabeth Or  is there any other way to init rdpgfx for using GFX H264?

The command code on Client side is '''''xfreerdp /v:xxxx /u:xxx /p:xxx /gfx-h264''''' . and I assign settings->GfxH264 = TRUE in shadow_client.c on Server side

@Zoson check the x11 shadow server as a reference, that one works and os used.


Task fails trying to look for requirements file when not specified

The task fails on ubuntu 16.04
2017-12-29T06:16:29.9427835Z [command]/home/****/myagent/_work/1/venv/build/bin/pip install -r /home/****/myagent/_work/1/s
2017-12-29T06:16:31.1832209Z Could not open requirements file: [Errno 21] Is a directory: '/home/****/myagent/_work/1/s'

Note: I did not give Pip requirements file path during configuring as its optional and I don't require it.

Crazy question, but did you specify the path to the folder with the requirements file or to the file itself?

@dazfuller The best I can remember is leaving that input from my side empty.

Ok by default it might be looking in the source folder.But what if I don't need a requirements file at all.

It's a good point and I've heard that from somewhere else recently. I'll look into making it optional

@niwsa I've just published an updated version which fixes the requirements file issue and adds in a test file pattern to help with test discovery. I've got a test build running with no requirements file and it's working for me, but let me know if it sorts out your problem.


Change a comment on the license

Why:
The license has changed.
What's being changed:

README.md
CC BY 4.0 → MIT license
Check off the following:

[x] For workflow changes, I have verified the Actions workflows function as expected.
[x] For content changes, I have reviewed the style guide.

@sinsukehlab thank you for fixing this typo. 🚀


Request for Missing Code Related to Contrastive Learning

Dear Author,
Hello! I recently read your article and am very intrigued by your research.
I attempted to access the relevant code, but unfortunately, I couldn't find the Code Related to Contrastive Learning mentioned in the article.
Would it be possible for you to provide the missing portion of the code? If this code is already included in another file, I would appreciate it if you could point that out.
Best regards

Got it, it seems that class DrugDecoyModel is the code I needed.


Doesn't seem to work

Hello, thank you for bringing this to my attention. It seems a recent Canary update broke the functionality of this and a few other plugins. I'll attempt to fix the plugin as soon as possible!

Thanks!

Same issue here. I just used this instead

Recent updates seem to be working, no reports of improper functionality


MultiPolygon and MultiLineString spatial type support

The problem:
When encountering MultiPolygon/MultiLineString GeoJSON data, there is no spatial type available for serialization.
Desired solution:
Stronger spatial type support and Microsoft.Azure.Documents.Spatial.Geometry types for MultiPolygon and MultiLineString, along the lines of existing Polygon/Point/LineString types
Alternatives:
Continue to use SQL Server or use an alternative DB provider.
Additional context;
When taking shapefile (*.shp) data and exporting it to GeoJSON format for import into Azure Cosmos documents, any data that is either multi polygon or multi line string cannot be directly serialized into a Microsoft.Azure.Documents.Spatial.Geometry type.
Is there any projection for including support for MultiPolygon and MultiLineString spatial types based on  Microsoft.Azure.Documents.Spatial.Geometry in the upcoming release?

Spatial types will be covered in Microsoft.Azure.Cosomos.Spatial namespce. There are few types already, please check https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.cosmos.spatial?view=azure-dotnet-preview
We will fill the missing types from DocumentClient (or V2.X SDK) in this namespace.
@simplynaveen20 can you please look into it?

One thing to note is that we should only port over the data types that are supported on the backend. I think only MultiPolygon is a missing structure while MultiLineString is missing and not supported on the backend.

MultiPolygon support added in <IP_ADDRESS>-preview
https://github.com/Azure/azure-cosmos-dotnet-v3/pull/79
MultiLineString is still not support in CosmosDB at this point .