Release latest updates to master

📥 Proposed changes
Get the latest additions (mainly the Select packages) published to canary

Merged manually


'wagtailsites' is not a registered namespace

Publishing the root page creates a 500 error page.
Steps to Reproduce

edit the root page (a page model) and publish (or unpublish) it

NoReverseMatch at /admin/pages/1/

'wagtailsites' is not a registered namespace

Error during template rendering

In template /usr/local/lib/python3.7/dist-packages/wagtail/admin/templates/wagtailadmin/pages/listing/_page_title_explore.html, error at line 8

{% if page.is_site_root %}
{% if perms.wagtailcore.add_site or perms.wagtailcore.change_site or perms.wagtailcore.delete_site %}

{% endif %}
{% endif %}

It doesn't occure on a fresh 2.11 install website.
It doesn't happen when saving as draft, only when (un)publishing. When saving as draft, the changes are saved, as well as states of (un)publishing.
Technical details

Python version: 3.7.3
Django version: 2.2.17 or 3.1.3
Wagtail version: 2.11.2
Browser version: Firefox 83 Ubuntu

Anything I can look for in my code or provide more details here? Thanks for help.

I think it was purely my fault, as 'wagtail.sites' was once removed from the Apps list in settings.


complete integration test for pulling image with labels

complete integration test for pulling image with labels
ref issue: https://github.com/containerd/containerd/pull/5945
Signed-off-by: Zou Nengren<EMAIL_ADDRESS>

/cc @fuweid @estesp

/cc @fuweid @estesp


Remove usage of deprecated parameters

In https://github.com/projectsyn/commodore/pull/192, some parameter values were deprecated. This component is affected by this change and needs to adapt. See the commodore change log for the details.

#7 has been merged. Can we close this issue?


Picture Updated Event

Is it possible to have an event (or have the doorbell last updated timestamp set again) when the doorbell picture that is within the entity url is updated?
states.camera.doorbell.attributes.entity_picture
There doesn't seem to be a way to know when the image is changed in that property and it can be a while after a doorbell event is raised.
The doorbell last changed and last updated timestamps dont get updated when the image is changed.
For example. My doorbell sees motion. I cast the image that is hosted at states.camera.doorbell.attributes.entity_picture and it can be an image from yesterday. A few seconds a picture card using that image is updated with the fresh image.

there will be a specific sensor in new version for latest notification picture


Patch the shebang of files specifed with bin field

Sometimes files specified with the bin field of package.json are missing
their executable bits when they are extracted[1]. npm must be setting their
executable bits at some stage of npm install life cycle because by the
time the command is complete, they are executable. But at "preinstall"
stage, which is when we patch the shebangs, those files are not
executable thus skipped by the patchShebangs function.
To fix this, jq is used to get the files specified with the "bin" field of
"package.json and the ones missing their executable bit are chmod'ed and patched.
[1]: E.g., package/bin.js extracted from https://registry.npmjs.org/prebuild-install/-/prebuild-install-6.0.1.tgz has its executable bit correctly set while the one from doesn't https://registry.npmjs.org/prebuild-install/-/prebuild-install-6.1.4.tgz

While trying to package https://github.com/eez-open/studio, using this commit patches 7 extra files, where at least one of those are used during the install. Without this commit, unpatched shebangs produces an error similar to
sh: /build/node_modules/better-sqlite3/node_modules/.bin/prebuild-install: /usr/bin/env: bad interpreter: No such file or directory.

Also somewhat related, currently this project uses hook scripts (specifically "preinstall" hook) to patch the shebangs. But as far as I can tell, hook scripts are removed from npm v7[1][2]. Do you have any plans to change the way shebangs are patched in a way that could also work with npm v7?
[1] https://github.com/npm/cli/issues/2692
[2] https://github.com/npm/cli/pull/3486

Wow, I didn't see https://github.com/nix-community/npmlock2nix/pull/107

hook scripts are removed from npm v7

good to know!
we can run the lifecycle scripts manually
https://github.com/nix-community/npmlock2nix/blob/60b003cadaa90673f3ab43ff6aca5877f421b021/internal.nix#L288-L302
fixme: this does not-yet handle the case of a missing scripts field in package.json

while were at it, we could fully replace npm install with bash scripts : P

much easier in javascript
https://github.com/milahu/npm-install-mini
forked from the lockfile parser https://github.com/npm/logical-tree
i use the same folder structure like pnpm (deep node_modules with symlinks),
but my "store" is in node_modules/.pnpm, not in $HOME/.pnpm-store
$ diff -rq node_modules.pnpm node_modules | grep ^Only

Only in node_modules.pnpm: .modules.yaml
Only in node_modules.pnpm/.pnpm: lock.yaml
Only in node_modules.pnpm/.pnpm: node_modules

works at least with cowsay ^^

$ npx cowsay "mooh!"  I read your comments by chance because this tab was left open. I opened an issue regarding the removal of hook scripts just now, to make it more visible. It was quite unlikely the maintainers would read these messages.


📃: Binary Tree

:red_circle: Title : Binary Tree
:red_circle: Aim : Binary Tree DSA
:red_circle: Brief Explanation : Showing all the basic operations on Binary Tree using a menu-driven program.
Screenshots 📷

N/A

:white_check_mark: To be Mentioned while taking the issue :

Full name : Anushka Mahajan
What is your participant role? (Mention the Open Source Program name. Eg. GSOC, GSSOC, SSOC, JWOC, etc.) GSSOC 24' Extended Contributor

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Uppada Pavitra Manaswini Reddy
GSSoC24' Extended Contributor
Im interested to contribute please assign me.

Uppada Pavitra Manaswini Reddy
GSSoC24' Extended Contributor
Im interested to contribute please assign me.

Hi @Pavitra-s-Workspace you can raise another issue , I will assign that issue to you. All the best

Uppada Pavitra Manaswini Reddy
GSSoC24' Extended Contributor
Im interested to contribute please assign me.

Hi @Pavitra-s-Workspace you can raise another issue , I will assign that issue to you. All the best

ok, Thank you.


promptfoo: 0.43.1 -> 0.47.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/promptfoo/promptfoo/releases.
meta.description for promptfoo is: Test your prompts, models, RAGs. Evaluate and compare LLM outputs, catch regressions, and improve prompt quality.
meta.homepage for promptfoo is: https://www.promptfoo.dev/
meta.changelog for promptfoo is: https://github.com/promptfoo/promptfoo/releases/tag/0.46.0
Updates performed

NPM version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.46.0 with grep in /nix/store/1ysn0qd915id02nb69icikdxhh744bh2-promptfoo-0.46.0
found 0.46.0 in filename of file in /nix/store/1ysn0qd915id02nb69icikdxhh744bh2-promptfoo-0.46.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
promptfoo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1ysn0qd915id02nb69icikdxhh744bh2-promptfoo-0.46.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A promptfoo https://github.com/r-ryantm/nixpkgs/archive/ee2522ae8b07d267051692e6c19471f4c84fdd1e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ee2522ae8b07d267051692e6c19471f4c84fdd1e#promptfoo

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1ysn0qd915id02nb69icikdxhh744bh2-promptfoo-0.46.0
ls -la /nix/store/1ysn0qd915id02nb69icikdxhh744bh2-promptfoo-0.46.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

promptfoo

Maintainer pings
cc @silvergasp for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/promptfoo/promptfoo/releases.
meta.description for promptfoo is: Test your prompts, models, RAGs. Evaluate and compare LLM outputs, catch regressions, and improve prompt quality.
meta.homepage for promptfoo is: https://www.promptfoo.dev/
meta.changelog for promptfoo is: https://github.com/promptfoo/promptfoo/releases/tag/0.47.0
Updates performed

NPM version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.47.0 with grep in /nix/store/vdg5g2spzpwss2yxykg9hm0w07d8vwn8-promptfoo-0.47.0
found 0.47.0 in filename of file in /nix/store/vdg5g2spzpwss2yxykg9hm0w07d8vwn8-promptfoo-0.47.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
promptfoo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vdg5g2spzpwss2yxykg9hm0w07d8vwn8-promptfoo-0.47.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A promptfoo https://github.com/r-ryantm/nixpkgs/archive/92f1c7f323310d38e0dde0d27939c6aee711703d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/92f1c7f323310d38e0dde0d27939c6aee711703d#promptfoo

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vdg5g2spzpwss2yxykg9hm0w07d8vwn8-promptfoo-0.47.0
ls -la /nix/store/vdg5g2spzpwss2yxykg9hm0w07d8vwn8-promptfoo-0.47.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

promptfoo

Maintainer pings
cc @silvergasp for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/promptfoo/promptfoo/releases.
meta.description for promptfoo is: Test your prompts, models, RAGs. Evaluate and compare LLM outputs, catch regressions, and improve prompt quality.
meta.homepage for promptfoo is: https://www.promptfoo.dev/
meta.changelog for promptfoo is: https://github.com/promptfoo/promptfoo/releases/tag/0.48.0
Updates performed

NPM version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.48.0 with grep in /nix/store/p2vcxfibwl6w8zbf0yy9281xnj9avf3z-promptfoo-0.48.0
found 0.48.0 in filename of file in /nix/store/p2vcxfibwl6w8zbf0yy9281xnj9avf3z-promptfoo-0.48.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
promptfoo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/p2vcxfibwl6w8zbf0yy9281xnj9avf3z-promptfoo-0.48.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A promptfoo https://github.com/r-ryantm/nixpkgs/archive/76c84ce6ad8a67715ee6c0bffe6957192923614f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/76c84ce6ad8a67715ee6c0bffe6957192923614f#promptfoo

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/p2vcxfibwl6w8zbf0yy9281xnj9avf3z-promptfoo-0.48.0
ls -la /nix/store/p2vcxfibwl6w8zbf0yy9281xnj9avf3z-promptfoo-0.48.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

promptfoo

Maintainer pings
cc @silvergasp for testing.


[TASK]: Update Architecture Diagrams & READMEs

📝 Overview

Update documentation before implementing the client-side.
🖋 Details

Update arch diagrams to reflect the latest architecture.
Update READMEs to describe the current repository structure.

📚 References

n/a

https://github.com/SeiyaKobayashi/zkml-optimization/pull/31


All boxes are wrongly checked in Preferences

Hi, I've come across this in other themes as well, but evidently this theme also displays all checkboxes as checked in all panes in preferences even when they aren't:

This goes for all checboxes on all other Preferences panes as well so it's impossible to really know which boxes I actually do have checked.
Can you provide a fix to accurately display which preferences boxes are checked?

I'll try to get that fixed today

@leowill01 I think I fixed it. Can you let me know if it's working for you?

@lusignan Yes it is working! Thank you.


As a software developer, I want formal requirements & tests, in order to facilitate writing automated tests.

Relates To

#191

Duplicate Of

#191


Refactor path commands

To create a path command like `M0 0 L4 2 z', one has to write this, which uses parenthesis unnecessarily in my opinion:
SVG.path [ SA.d [ Abs (M 0.0 0.0), Rel (L 4.0 2.0), Z]

Moreover, it builds up a syntax tree representing this commands via an ADT before immediately printing those commands as strings. I don't see why this intermediary syntax tree is necessary.
I propose refactoring this code, so that we do not export constructors at all. Rather constructors become functions. Moreover, each of these functions produce the String version of the command but hides it in a Newtype that doesn't have its constructor exported, so no one can modify it once created:
SVG.path [ SA.d [ m Abs 0.0 0.0, l Rel 4.0 2.0, z]

newtype PathCommand = PathCommand String

m :: D -> Number -> Number -> PathCommand
m ref x_ y_ = PathCommand $ renderCommand <> show x_ <> " " <> show y_
 where
 renderCommand = case _ of
  Abs -> "M"
  Rel -> "m"

Hasn't this been fixed with commit 805e80f9cbb2d357f792745f116e65f65d5dcb46 ?
Can this issue be closed now?

Probably. Thanks for reminding me about this.


[Bug] Configuration window buttons appear behind the settings text

I'm on the current version of both Foundry and the macro and noticed that in the settings window under "Combat Helpers" the "Save Changes" and "Reset Defaults" buttons appear kind of behind the settings. They can still be operated though.

Does this occur when the module that adds those globe symbols is disabled? Also, what is that module?

Hi @trioderegion.
That's DF Settings Clarity - https://github.com/flamewave000/dragonflagon-fvtt/tree/master/df-settings-clarity
It shows which settings are world settings and which are client settings.
After disabling it, the buttons show up at the end of the window again. I'd like to use the other module further on and since it's just a minor interface bug it's fine if fixing it is not really a priority for you. The buttons still work even though DF Settings Clarity interferes with it.

I really have no idea why it would be doing that. We are just using a standard Form Application. Have you checked with the Author of Setting's Clarity? Feel free to ping me in that issue.
Not trying to shirk responsibility, just confused as to why this would happen.

After updating to your newest version today the issue has resolved itself. 🥳 Still thanks for the replies.

I'm not going to look a gift horse in the mouth, haha. Good to hear!


Add to guidelines for deleting master until release

Currently, there is a mixture of behaviour when a pipeline is in early development before release. Often the state of the default master branch is that it's just an empty template left from nf-core create
To make the default code as useful as possible whilst adhering to existing rules of branch management, @MaxUlysse proposed that we delete the master branch until the first release, setting dev as default. When preparing the first release we create master again and set it as the default.
In this PR I add to the guidelines to mention this, as well as adding to the nf-core tutorial.
This topic is open for debate - @nf-core/all please feel free to point out any potential problems with this new approach in the comments below.
TODO if merged:

[ ] Need new checks on the Pipeline Health webpage.
[ ] Check whether nf-core sync will tolerate the absence of a master branch (especially for --all)

@olgabot - one half-way method we discussed is to just make dev the default branch before the first release, without deleting anything. This is my preferred method - as you say, reduced churn and fewer steps (it's also something we can automate through the GitHub API easily without any risk).
The advantages are pretty much the same - latest code available as default instead of just a blank template; always developing on dev and never on master (before and after a release).
I guess the argument against this is that having master there could cause confusion about what should be on each branch. But as @olgabot says - not having master at all could also cause confusion. I'm not sure that either one approach is better than the other, and I think both are probably less confusing than what we do currently.
Thoughts?

Im happy with that. Confusion either way but probably best to keep it.
Not having  master = confusion as to why it isnt there...
Having (pre-release) master = confusion as to what its doing there...

@olgabot has a good point. Although I am not sure which one is the way to go, I think it depends on the target audience.
If audience is proficient users (of git) then it does not really matter, they will understand what is the point of doing it either way
If audience is beginner users (of git) then it is better to have master there for the reason Olga mentioned.
Therefore, for general audience I think it is better to change the default branch to dev and not delete the master.

I would prefer to leave it as is. The less steps one has to perform, the lower the barrier usually is for newcomers. So I agree with @olgabot and @kerimoff.

I would say that our current issue is that we have non-released pipelines that are developed on a master branch, some of them have not been touched for months.
For me, if a code is deemed stable enough to be on a master branch, it should be released already (even if it is lacking tools or docs).
We do adhere to semantic versioning 2.0.0, and I think we should already have more released pipelines, or at least, that's how I understand this part:

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.

I can see the problem with an empty master branch, or no master branch at all, so changing the default to dev is I think the least we should do.

I would prefer to leave it as is. The less steps one has to perform, the lower the barrier usually is for newcomers. So I agree with @olgabot and @kerimoff.

To clarify, the proposed changes (setting dev to default) means fewer steps for newcomers - newcomer users at least. The latest development code will run by default with nextflow run without having to specify -r dev
There's two extra steps for developers - setting dev as default and back again, but this can be checked and fixed automatically via the GitHub API so we can do this via the website. Pretty low barrier.
The only barrier I think is to know which branch to make PRs against. But again changing the default to dev means that new PRs will select that by default, which is probably what we want.
So we all have the same objective here - to lower the barrier for newcomers. That's what the proposed change is about 😄 It's just a question of which option does that most effectively.

I thought the target was newcomer nf-core developers, rather than users.
For a new user who wants to use a pre-release nf-core pipeline, I think having to explicitly set -r dev is useful visual signal.
Perhaps this could also be added to the create template code instructions as well and then removed later when it's made release-worthy.
My preference would be that the master show some kind of pre-release banner with instructions to use the dev branch, and stay the same as the create template until it's release.
But then that comes down to teaching developers how to use the tools and work exclusively on dev until a release version is ready.

Just to give an additional possibility, in the iarcbioinfo plateform we used to maintain 3 branches:

master=latest release (e.g. v1.0)
dev=development branch with minor changes
vX.Yb=version branch with major changes (e.g. v1.1b, this one is merged with the master to build a new release)
see an example with our needlestack pipeline

Thanks @tdelhomme - that's the same structure that we use for nf-core, except we just use patch instead of vX.Yb.
@mahesh-panchal

For a new user who wants to use a pre-release nf-core pipeline, I think having to explicitly set -r dev is useful visual signal.

Yup, this is a good point. However, I worry that instead people just run non-functioning code.

But then that comes down to teaching developers how to use the tools and work exclusively on dev until a release version is ready.

Agreed. We have said this for a while now, but it isn't really written down anywhere. The documentation changes in this PR aim to address that.

Yup, this is a good point. However, I worry that instead people just run non-functioning code.

I would have suggested making the main code then exit if it's not dev or version > 1.0, but that doesn't address the current repositories in their various states. This proposed solution would address that in a simple-ish manner.

Ok, so I think we're reaching towards consensus that this is an ok plan..? Make dev default on un-released pipelines. Would you be ok with this @olgabot?

Awesome. Thank you everyone! Merging..


Doubled size/rows shown in dashboard for two imports of the same file

This was reported a week ago in Support by a regular user, but yesterday I uploaded a CSV (two times) and the result in the dashboard is:

If I do a count(*) in both of them, I get 129171, but in the dashboard one of the two (rows and quota) gets doubled.

I'm not able to reproduce this with fixed, so perhaps this is not meant to be open.This happened to me a couple of days ago when the drag-and-drop was not working in my browser but after refreshing several imports had been created.


starting thoughts on Basic Income..

Santi.. did you envision a second token for 'basic income'?...or some other mechanism?

I included section but no details yet.


Error when enabling customfoodbar button in Config Manager

Error when enabling customfoodbar button in config manager
[Error  : Unity Log] NullReferenceException: Object reference not set to an instance of an object
Stack trace:
BetterUI.Patches.CustomElements+FoodBar.Update (Player player) (at :0)
BetterUI.GameClasses.BetterHud.UpdateFood (Player player) (at :0)
(wrapper dynamic-method) Hud.DMDHud::UpdateFood(Hud,Player)
(wrapper dynamic-method) Hud.DMDHud::Update(Hud)

Thank you for the report. It might take me a couple days to get to it.

all four custom bar elements really don't like it when you change the config ingame since they only get created in Awake, so they all throw null reference exceptions if you enable or disable them at the wrong time (the food bar throws different ones than the health and stamina bar though). Curiously, the creation of all but the xp bar is also dependent on enablePlayerHudEditing being enabled. Getting all the null references out of the way is not difficult of course, but would loading them at run time be worth the work?


No load image

At http://jekor.com/gressgraph

I missed this issue. I've since updated and tested it. Please let me know if it's not working.


Improvement: Managing Service Accounts

During the investigation, I have found some issues in the Managing Service Accounts docs. which I have improved in this PR like:

Mention RootCAConfigMap feature gate is Stabe in 1.21.

The feature gate RootCAConfigMap graduated to GA in v1.21 and therefore will be unconditionally enabled. This flag will be removed in v1.22 release. (#98033, @zshihang)

Instead of ImagePullSecrets it should be imagePullSecrets.

Hi @davidopp @lavalamp
Could you please take a Look!

/assign @deads2k
/unassign
@deads2k is better for auth related stuff

Hi @deads2k
PTAL!

Thanks @lavalamp  @irvifa for taking look in this.

/lgtm


curve3d /pathfollow rotation modes not working

Godot version:
3.2
OS/device including version:
win8
Issue description:
i use a pathFollow to move a obj along a path/curve3d
i animate the movment by changing the > pathFollow > Unit_offset per gd-script.
i need to rotate it with the path in Y direction.
PROBLEM 1
therefore i want to use PathFollow > RotationMode > Y
but the object starts spinning (rotating in Y) if i move it per scipt along the path. why?
i tryed everything... cant get it to follow the path and rotate with it... it spins like a helicopter along the path... so, not usable...
this do not happen if change the offset in the editor... just if i change it per gd.script at runtime
in the editor, however, roation is also buggy... but in another way... (try offset at end of path)
PROBLEM 2
so wtf but okay.... i change the PathFollow > RotationMode > to "oriented"
nice - no more spinning helicopter
BUT
now the curve (and my obj) tilts along the curve.(to one side only)
and that tilting gets more and more the further i travel along the path. why? whats that?
BTW: the points tilts in $Path.curve.get_baked_tilts() are all 0.
thats also not natural tilting like i read in the docs... it rotates more and more to one side as i travel the path
noting works here... curve / pathfollow and rotation is not usable any way i use it... or i miss a point???? its so simple... i just change the unit_offset per gd-scipt, thats all...
i tryed for weeks now... whats wrong here?
also i cant find nothing about that on the interwebs... strange.... nobody ever used this?
Steps to reproduce:
make a (somewhat complex) path/3Dcurve
change the pathFollow unit_offset per gd-scipt
try the PathFollow > RotationModes
Minimal reproduction project:

Duplicate of #3713 and #27137.


Some text is not visible in high contrast mode

To reproduce, change your theme to high contrast light.
The following UI is not visible in high contrast mode:

code blocks in comments on the description view (also need a border in high contrast mode)
code in comments is hard to distinguish from normal text
text of the comment button at the end of the description view (Fixed by #4368)

code in comments is hard to distinguish from normal text

I didn't change this one as it's already using a VS Code color and it also has a different font.


WIP - PDF Report preview

ROSS PDF ROTORDYNAMICS REPORT
This PR includes a preview of how the PDF generating code will function.
The folder API_Report contains a .py archive named Report.py.
When executed, this archive :

instantiates an example rotor;
saves an svg file containing the plot_rotor() output;
generates a PDF with all the data gathered.

Observations
I struggled trying to use Bootstrap. Therefore I've decided not to use it.
Nevertheless, after some further investigation, I've discovered the font and color pallet used on the Lumen theme.
What's next?

This API_Report folder will not exist initially. Being generated inside a rotor saving folder for every rotor.
In this PDF I will implement the tests assembled by @rodrigomoliveira1 .

Hi there!
I have marked this issue as stale because it has not had activity for 45 days.
Consider the following options:

If the issue refers to a large task, break it in smaller issues that can be solved in
less than 45 days;
Label the issue as wontfix or wontfix for now and close it.


Real time optic magnifying glass for Cesium

hii,
Can we magnifiy the objects in https://github.com/amitdiamant/magnify-3d there any magnifier in Cesium.
I know that there is magnifier.js library available out there but can we make a magnifier using Cesium.
Is there any other way to magnify or zoom that particular object from various objects.

@xjindf Hi! Cesium has mouse controls which you can zoom into your object. For some entities like models and billboards, you can also double click on it to zoom in automatically.
How would you use the magnifier feature in Cesium? Would love to learn more about your use case and how this feature could benefit/enhance your application. Please add any details about the feature (do you want to be able to change the size of the magnifier, what does it add to your application that you cannot achieve with the zoom mouse control, etc) that helps explain why this feature is useful.

Thank you for your reply. Maybe I can't express it clearly. I know the zoom function of the scene, but what I want to achieve is the aiming magnifying glass function similar to the sniper gun.

You can change the fov


Message receiver testing page

Mixed used of terms for GP suppliers, suggest stick to GP principal clinical system suppliers or acronymised as PCS suppliers.
Like sneder testing page, suggest TODOs are removed or reworded as holding statements

Duplicate of #26


Update volume options (fixes #27029)

ping @thaJeztah

let's ping @thaJeztah again :angel:

@cpuguy83 @thaJeztah  PTAL?

@mstanleyjones can we carry this please? Thanks!

I added a commit to address the comments left so far. I didn't turn the list into a table, since it is part of a larger multiply-nested list and tables can't easily go into lists. PTAL @LK4D4 @cpuguy83 and check my re-wording.

ping also @thaJeztah

ping @thaJeztah @cpuguy83


Bug: Can't select some files in column view

Description
When trying to select some files in column view by clicking them, Files closes all subsequent subfolders opened in columns and returns to the first column.
https://user-images.githubusercontent.com/2331058/232351898-5d8615ef-9948-4ab1-bed3-3e98c491582b.mp4
Steps To Reproduce

Open some folders in column view
Try to select files of different names and types (I haven't narrowed down the exact issue)
Some of them will cause the bug to happen

Requirements

eg. Fix crash that occurs when...
eg. Correct action happens when clicking...

Files Version
<IP_ADDRESS>
Windows Version
10.0.19044.2846
Log file
There are no logs about the bug in the debug.log file, but I attached it anyways. The bug happened at on 2023-04-16 around 9 PM.
debug.log

Thank you for bringing this to our attention, it also looks like the tag icon is misaligned but that's a separate issue.

Can you tell us how did you set these?

Can you tell us how did you set these?

Here it is

This seems to occur when a shortcut to a folder is selected and then a file further on is selected.
When a shortcut is selected, should the shortcut destination be opened in a new column as if it were a symbolic link?

Would it be worth checking the behavior in Finder?

The same behavior is observed in Finder. So this behavior should not be changed and the file should be opened correctly.

@rafaskb we implemented a fix and it'll be included in one of the next releases.


How to ensure the "active" pagination item, matches the current section when you load directly into a section that isn't the first section

For example to reproduce issue: https://projects.lukehaas.me/scrollify/examples/pagination/#third
The "active" item is indicating you are on the first section but we landed directly on the third.
Do I need to do some logic myself in the afterRender method to ensure the correct pagination item is set to "active" if a user doesn't load the page at the first section.

Yes, add logic to afterRender to handle that.

Thanks


gore can't import vendored packages

I'm trying to import a package inside a vendor subdirectory in my project. I get the following when importing directly:
gore> :import github.com/aws/aws-sdk-go
error: import: can't find import: vendor/github.com/aws/aws-sdk-go

I tried working around it by treating my vendor directory as a temporary GOPATH, and it worked:
ln -s $PWD/vendor /tmp/go/src
GOPATH=/tmp/go go install github.com/aws/aws-sdk-go
GOPATH=/tmp/go gore
gore> :import github.com/aws/aws-sdk-go
(no error)

This isn't really a workable solution though. Is there a way for gore to find these packages? I know they have to be go install'ed first - maybe that's part of the issue?

I suppose you need to specify absolute path of vendored package like github.com/your_name/your_product/vendor/github.com/aws/aws-sdk-go. go/importer package API does not permit to import from vendored packages now.

@syohex It doesn't appear to work that way either. I've tried prefixing the vendored package as if it were under a package named vendor, and still get the same :import: can't find import error.

I cannot reproduce. Please try after installing package.

It 'imports' it just fine. but its not actually usable.
gore version 0.2.6  :help for help
gore> :import bitbucket.org/jatone/example/vendor/github.com/nlopes/slack
gore> c := slack.New("xoxb-66382132692-YPzxusDnHT7GcaE0NKLaqW6l")
package main
	imports bitbucket.org/jatone/example/vendor/github.com/nlopes/slack: use of vendored package not allowed
error: exit status 1
exit status 1

gore version 0.2.6  :help for help
gore> :import example/vendor/github.com/nlopes/slack
gore> c := slack.New("junk")
package main
imports example/vendor/github.com/nlopes/slack: use of vendored package not allowed
error: exit status 1
exit status 1

Is this high on the list?

Yeah this is a bit of a nuisance.

Yeah this is a bit of a nuisance.

+1

gore uses go run to evaluate user inputs, creating temporary .go file. The problem is that, in order to handle vendored packages correctly, you have to put the temporary .go file at current directory, which could make cwd dirty.
Anyway we could attack this, with carefully crafted temporary filenames. I'm going to work on this when I have time.

Also related to https://github.com/motemen/gore/issues/69

any updates on this?

@syohex it looks only work under GOPATH, since go publish module feature, some project might not always under GOPATH. so that why someone meet issue can not load package in console. I'm a part of them.


[DOCS] Change the description to match the organization

Description
The description shown in the profile readme doesn't fully seem to match the organization itself.
It'd be great if it could be updated to match the organization so that other users can know what it is about and everything. 🙂

OMG i just forgot have this org on GitHub. Sorry but this is my first idea in opensource. But I need to re-think to maintain this organization. But i will appreciate if you want to start discussion again. :blush:


Failing migration to v2.0.0-alpha.2

Environment

Nautobot version: v2.0.0-alpha.2
Python version: 3.7
Database platform, version: Postgres
Middleware(s):

Steps to Reproduce

Import existing 1.5.14 dataset into Postgres
Run invoke debug

Expected Behavior
Migrations work

Observed Behavior
Migrations fail with following output:
nautobot_1       |   Applying extras.0060_role_and_alter_status... OK
db_1             | 2023-03-30 09:48:38.151 UTC [129] ERROR:  duplicate key value violates unique constraint "extras_role_slug_key"
db_1             | 2023-03-30 09:48:38.151 UTC [129] DETAIL:  Key (slug)=(loopback) already exists.
db_1             | 2023-03-30 09:48:38.151 UTC [129] STATEMENT:  INSERT INTO "extras_role" ("id", "created", "last_updated", "_custom_field_data", "name", "slug", "color", "description", "weight") VALUES ('5f4d5a5a-0cb9-44cc-bad8-b4a9c9c95863'::uuid, '2023-03-30'::date, '2023-03-30T09:48:38.150962+00:00'::timestamptz, '{}', 'Loopback', 'loopback', '9e9e9e', '', NULL)
nautobot_1       |   Applying extras.0061_collect_roles_from_related_apps_roles...Traceback (most recent call last):
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
nautobot_1       |     return self.cursor.execute(sql, params)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django_prometheus/db/common.py", line 71, in execute
nautobot_1       |     return super().execute(*args, **kwargs)
nautobot_1       | psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "extras_role_slug_key"
nautobot_1       | DETAIL:  Key (slug)=(loopback) already exists.
nautobot_1       |
nautobot_1       |
nautobot_1       | The above exception was the direct cause of the following exception:
nautobot_1       |
nautobot_1       | Traceback (most recent call last):
nautobot_1       |   File "/usr/local/bin/nautobot-server", line 6, in <module>
nautobot_1       |     sys.exit(main())
nautobot_1       |   File "/source/nautobot/core/cli.py", line 61, in main
nautobot_1       |     initializer=_configure_settings,  # Called after defaults
nautobot_1       |   File "/source/nautobot/core/runner/runner.py", line 263, in run_app
nautobot_1       |     management.execute_from_command_line([runner_name, command] + command_args)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line
nautobot_1       |     utility.execute()
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 413, in execute
nautobot_1       |     self.fetch_command(subcommand).run_from_argv(self.argv)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 354, in run_from_argv
nautobot_1       |     self.execute(*args, **cmd_options)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 398, in execute
nautobot_1       |     output = self.handle(*args, **options)
nautobot_1       |   File "/source/nautobot/core/management/commands/post_upgrade.py", line 82, in handle
nautobot_1       |     verbosity=options["verbosity"],
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 181, in call_command
nautobot_1       |     return command.execute(*args, **defaults)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 398, in execute
nautobot_1       |     output = self.handle(*args, **options)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 89, in wrapped
nautobot_1       |     res = handle_func(*args, **kwargs)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/core/management/commands/migrate.py", line 246, in handle
nautobot_1       |     fake_initial=fake_initial,
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/executor.py", line 117, in migrate
nautobot_1       |     state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
nautobot_1       |     state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/executor.py", line 227, in apply_migration
nautobot_1       |     state = migration.apply(state, schema_editor)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/migration.py", line 126, in apply
nautobot_1       |     operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/operations/special.py", line 190, in database_forwards
nautobot_1       |     self.code(from_state.apps, schema_editor)
nautobot_1       |   File "/source/nautobot/extras/migrations/0061_collect_roles_from_related_apps_roles.py", line 122, in populate_roles_from_related_app_roles
nautobot_1       |     create_equivalent_roles_of_ipaddress_role_choices(apps)
nautobot_1       |   File "/source/nautobot/extras/migrations/0061_collect_roles_from_related_apps_roles.py", line 57, in create_equivalent_roles_of_ipaddress_role_choices
nautobot_1       |     bulk_create_roles(apps, roles_to_create, ["ipam.ipaddress"])
nautobot_1       |   File "/source/nautobot/extras/migrations/0061_collect_roles_from_related_apps_roles.py", line 93, in bulk_create_roles
nautobot_1       |     new_role.save()
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/models/base.py", line 740, in save
nautobot_1       |     force_update=force_update, update_fields=update_fields)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/models/base.py", line 778, in save_base
nautobot_1       |     force_update, using, update_fields,
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/models/base.py", line 881, in _save_table
nautobot_1       |     results = self._do_insert(cls._base_manager, using, fields, returning_fields, raw)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/models/base.py", line 921, in _do_insert
nautobot_1       |     using=using, raw=raw,
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/models/manager.py", line 85, in manager_method
nautobot_1       |     return getattr(self.get_queryset(), name)(*args, **kwargs)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 1270, in _insert
nautobot_1       |     return query.get_compiler(using=using).execute_sql(returning_fields)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/models/sql/compiler.py", line 1416, in execute_sql
nautobot_1       |     cursor.execute(sql, params)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 98, in execute
nautobot_1       |     return super().execute(sql, params)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/cacheops/transaction.py", line 97, in execute
nautobot_1       |     result = self._no_monkey.execute(self, sql, params)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 66, in execute
nautobot_1       |     return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
nautobot_1       |     return executor(sql, params, many, context)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
nautobot_1       |     return self.cursor.execute(sql, params)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 90, in __exit__
nautobot_1       |     raise dj_exc_value.with_traceback(traceback) from exc_value
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
nautobot_1       |     return self.cursor.execute(sql, params)
nautobot_1       |   File "/usr/local/lib/python3.7/site-packages/django_prometheus/db/common.py", line 71, in execute
nautobot_1       |     return super().execute(*args, **kwargs)
nautobot_1       | django.db.utils.IntegrityError: duplicate key value violates unique constraint "extras_role_slug_key"
nautobot_1       | DETAIL:  Key (slug)=(loopback) already exists.

This is a known issue but thanks for submitting it so we can track it! :)

Fixed in #3596.


it great,thx!

it's a great work, save me a lot of time, thank you!

Hey there, thanks for the appreciation! Glad it could help... and let me know if you encounter any issues!


Add check name to SpaceCharacter check output message

Added check name to SpaceCharacter check output message

✔ Checklist:

[x] This PR has been added to CHANGELOG.md (at the top of the list);
[x] Docs have been added / updated (for bug fixes / features).

@pineapplethief Thank you for your contribution! ❤


Clarify host OS support

@MikeBazMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Heidilohr I know the Build doc lockdown is happening right about now, can we get this published before then?

This was apparently closed.  @Heidilohr do you know why?  The PR history doesn't show who closed it and there's no comments.


Create LICs 9-11 with corresponding unit tests

A member who did not implement these LICs should add one or more tests for the LICs.

This was already done with issue #37.


feat(cli): implemented the tmx loader and format changes

Should close #289

feat: Implement a new createTmxLoader() function in packages/cli/src/loaders/tmx.ts to handle loading and saving TMX subtitle files
test: Add two unit tests in packages/cli/src/loaders/index.spec.ts to validate parsing of simple SRT files
docs: Update @replexica/spec to include the SRT file format specification
chore: Generate changelogs for both 'replexica' and '@replexica/cli' packages using pnpm new

@maxprilutskiy please review this one


#7602: Ignore / skip failing tt_lib perf: roberta, stable_diffusion and skip regressed ttnn t5 and bert

@jliangTT @tt-dma
This should fix failing perf for GS.

https://github.com/tenstorrent/tt-metal/actions/runs/8744783239
Once this passes, we can merge.


Evaluation

Hello! Is the input of the evaluation function the control point of the Bezier curve or the 3D line? If the output of the model is the control point of the Bezier curve, do I need to convert the result into a 3D line for evaluation?

Hi, we are not using control points. To represent a centerline, we use a sequence of points located on the centerline. In the gts, 201 points represent a centerline. But for evaluation, we downsample to 11 points for efficiency concerns (https://github.com/OpenDriveLab/OpenLane-V2/blob/master/data/OpenLane-V2/preprocess.py#L31).

Is each line of gt represented by 201 points, is it too much?

The range covered in a single frame is 100m x 50m in the BEV, we provide these in order to describe lanes in detail. Please feel free to choose arbitrary number of points to use in your case.

OK.Thanks!


[Bug]: Horizontal Scroll Bar in Table Widget Gone

Is there an existing issue for this?

[X] I have searched the existing issues

Description
I have a table widget with more columns than will fit across the screen at once. In the past, there was a horizontal scroll bar at the bottom of the table that could be used to move the view to these columns, but this disappeared after yesterday's update. The only way I've found to scroll to these invisible columns is with the center wheel/button of the mouse.
Steps To Reproduce
In the editor, I can only get the horizontal scroll bar to appear in the table widget for a wide table if the table is the height of an integer number of rows. When I turn on cell wrapping and the rows become different heights based on the content, the horizontal scroll bar disappears because the table is no longer the height of an integer number of rows.
Public Sample App
No response
Environment
Production
Severity
Medium (Frustrating UX)
Issue video log
https://www.loom.com/share/4d80b47b1fd645ed80a7a8afe355aaee?sid=3a2c1df5-e647-4805-b952-e1029a570867
Version
Self hosted CE v1.25

on Cloud same issue

Just discovered that this issue affects the vertical scroll bars as well. https://www.loom.com/share/5772acb273634974ac2a610f17c4233a?sid=ca1a14b4-07e0-49f7-ac05-5867d24c5032

Another user reported this bug.

@bejenaru @sjr267 we have a preview of the fix here
https://ce-33806.dp.appsmith.com
Can you try it out and let us know if it solves the problem? You will need to create a new account on the URL I shared as it's a completely separate instance

Hi @Nikhil-Nandagopal
It is working ok on this instance!

@bejenaru glad to hear it, the fix should be merged in soon


Quantity not update

When you are about to confirm a tour, the amount should update the final value and is not loading properly
Screenshot attached

How to reproduze the user scenario

Pick a tour and go to confirm page and try to add or remove quantity

More details in how to contribute, read the contribution guidelines

Fixed and deployed 🚀


Add test and refactor reinhard_sample and Sample

Added a unit test for reinhard_sample
Used large_image tileIterator to implement Sample
Did PEP8 renaming

@jbeezley Can you please take a look?
Installing the requirements of girder, large_image and slicer_cli_web with a single command produces the following error:
Double requirement given: psutil>=4.2.0 (from -r /home/travis/build/DigitalSlideArchive/HistomicsTK/build/girder/plugins/large_image/requirements.txt (line 4)) (already in psutil==4.2.0 (from -r requirements.txt (line 9)), name='psutil')

I tried to install the requirements separately like this and it produced another error  saying
 ERROR: Failed to load plugin "large_image":
13: Traceback (most recent call last):
13:   File "girder/utility/plugin_utilities.py", line 97, in loadPlugins
13:     plugin, root, appconf, apiRoot, curConfig=curConfig)
13:   File "girder/utility/plugin_utilities.py", line 230, in loadPlugin
13:     pluginLoadMethod(info)
13:   File "girder/utility/plugin_utilities.py", line 479, in wrapped
13:     return func(*arg, **kw)
13:   File "/home/travis/build/DigitalSlideArchive/HistomicsTK/build/girder/plugins/large_image/server/base.py", line 193, in load
13:     from .rest import TilesItemResource, AnnotationResource
13:   File "/home/travis/build/DigitalSlideArchive/HistomicsTK/build/girder/plugins/large_image/server/rest/__init__.py", line 23, in <module>
13:     from .tiles import TilesItemResource
13:   File "/home/travis/build/DigitalSlideArchive/HistomicsTK/build/girder/plugins/large_image/server/rest/tiles.py", line 29, in <module>
13:     from ..models import TileGeneralException
13:   File "/home/travis/build/DigitalSlideArchive/HistomicsTK/build/girder/plugins/large_image/server/models/__init__.py", line 23, in <module>
13:     from .image_item import ImageItem
13:   File "/home/travis/build/DigitalSlideArchive/HistomicsTK/build/girder/plugins/large_image/server/models/image_item.py", line 32, in <module>
13:     from ..tilesource import AvailableTileSources, TileSourceException
13:   File "/home/travis/build/DigitalSlideArchive/HistomicsTK/build/girder/plugins/large_image/server/tilesource/__init__.py", line 24, in <module>
13:     from .base import TileSource, getTileSourceFromDict, TileSourceException, \
13:   File "/home/travis/build/DigitalSlideArchive/HistomicsTK/build/girder/plugins/large_image/server/tilesource/base.py", line 24, in <module>
13:     from ..cache_util import tileCache, tileLock, strhash, cached
13:   File "/home/travis/build/DigitalSlideArchive/HistomicsTK/build/girder/plugins/large_image/server/cache_util/__init__.py", line 20, in <module>
13:     from .cache import LruCacheMetaclass, tileCache, tileLock, strhash
13:   File "/home/travis/build/DigitalSlideArchive/HistomicsTK/build/girder/plugins/large_image/server/cache_util/cache.py", line 23, in <module>
13:     from cachetools import LRUCache, Cache, hashkey
13: ImportError: cannot import name hashkey

A new version of cachetools (2.0) was released yesterday.  I suspect that is the problem.  We will have to update to the new API or specify <2.0.0 in the requirements.

Aha! Can we put the restriction in large_image/requirements.txt?

Yes, we'll probably want to do cachetools>=1.1.6,<2.0.0.

Current coverage is 60.79% (diff: 100%)

Merging #209 into master will not change coverage

@@             master       #209   diff @@
==========================================
  Files             8          8
  Lines           352        352
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            214        214
  Misses          138        138
  Partials          0          0

Powered by Codecov. Last update ab0add5...7f70ed5


jupyterlab_vim stopped working for no apparent reason

I'm honestly clueless as to why this has happened. Came back to my laptop and it was as though the plugin was disabled. Sorry I can't provide any more information.

Sorry to hear that, were you able to solve this?


chore: add codecov to circleci config

Proposed changes

Adds Codecov to CircleCI config.
Types of changes

[x] Build (changes that affect the build system)

Checklist

[x] I have read the CONTRIBUTING documentation
[x] Lint and unit tests pass locally with my changes

Well. Closing and reopening the PR doesn't trigger a rebuild like it did with Travis. I really do not want to this with additional commits - could you rebuild manually from the dashboard @faustbrian?


fix: fixes for mobile rendering

Asana Task: 🛠 Orbit Polish

Some more styling to help with mobile.
Table display:
This introduces a soft hyphen around @ signs, if present, so a full email address breaks there. I tried a lot of other solutions, including:

Splitting @ parts into different elements; works, but it's complex/annoying
Zero width space: annoying, because it can land on the pasteboard if copied
This solution, but setting hyphenate-character to '' via inline CSS; bundler removed this I think?

Checklist

Tests:

( ) Has tests
(x) Doesn't need tests
( ) Tests deferred (with justification)

Product/Design sign off:

(x) Okayed the plan for the feature (e.g. the design files, or the Asana task)
( ) Reviewed the feature as implemented (e.g. on dev-green, or saw screenshots)
( ) No review needed

This solution, but setting hyphenate-character to '' via inline CSS; bundler removed this I think?

Did you try to put this in a style attribute, or did you try using Tailwind's support for arbitrary properties?

@lemald It was inline style. I'll dig into Tailwind's option 👍


Final presentation date

Please choose a date for the final presentation: project name and three dates in decreasing order of preference

Textbook AI: May 3rd, May 1st, April 29th

E.g.
TeamX
May 6
May 3
May 1

Color Sort
May 1
May 6
April 29

HeavilyArmedPenguins
May 1
May 3
May 6

BeRealForArt
May 3
May 6
May 1

ClassMate (RateMyClass)
April 29
May 1
May 3

GameGenie:
May 6
May 3
May 1

LiteLib:
May 1
May 3
April 29

BugHouse:
May 3
May 6
May 1

Gamesense:
May 6
May 3
May 1

Game Genie:
May 6
May 3
May 1

Moba:
May 6
May 3
May 1

2D Game:
May 3
May 1
April 29


View Analytics doesn't work on the self-hosted option.

Although the Self-Hosted's Shared link is already filled, the View Analytics page shows "Please enter your Shared Link under Self-Hosted Settings."
Plausible version 2.0.2.

Please try 2.0.3, which is about to be released in 3... 2... 1...


Fix a bug occurring when prepare_returns is invoked in metrics

Addressing issue: https://github.com/ranaroussi/quantstats/issues/272

Since this library no longer seems to be maintained, we have created a duplicate of it that we plan to maintain and improve over time. If you'd like to use our version check it out here: https://github.com/Lumiwealth/quanstats_lumi
Please feel free to fork and send your pull request to this new library, we will be actively monitoring the library and approving PRs


FastLED.h breaks if version > 3.4.0 is installed

After updating the aviationweather source, I reflashed my code. On reboot, the ESP only lit up the first LED on the string. I sequentially downgraded fastled.h from 3.6.0, to 3.5.0, to 3.4.0. The LEDs worked as intended once 3.4.0 was installed.

Just a bump - this was an issue for me as well, thanks for pointing it out 3.4.0,  works well for me now.


Strange snapshot output with High Order Components

I'm trying to snapshot a routed redux app, my test code is as follows:
const app = mount(renderApp());
const tree = enzymeToJson(app);
const snapshotFileName = path.join(__dirname, "App.enzyme.js.snap");
const snapshotName = "Enzyme App renders correctly";
expect(tree).to.matchSnapshot(snapshotFileName, snapshotName);

I'm using chai-jest-snapshot to do the snapshotting. The output I see in the snapshot file looks like this:
exports[`Enzyme App renders correctly`] = `
<Provider
  store={
    Object {
      "@@reduxReactRouter/routerStateSelector": [Function routerStateSelector],
      "dispatch": [Function anonymous],
      "getState": [Function getState],
      "history": Object {
        "__v2_compatible__": true,
        "createHref": [Function createHref],
        "createKey": [Function createKey],
        "createLocation": [Function createLocation],
        ...

Snapshot testing fails because some key values differ on each test execution.
However when I use react-test-renderer the snapshot output is just HTML and the snapshot comparisons work fine:
exports[`Jest App renders correctly`] = `

          <span
          ...

The code I ran to produce this is:
 const tree = renderer.create(renderApp()).toJSON();
 const snapshotFileName = path.join(__dirname, "App.jest.js.snap");
 const snapshotName = "Jest App renders correctly";
 expect(tree).to.matchSnapshot(snapshotFileName, snapshotName);

So the only difference appears to be calling the enzymeToJson() method rather than using the react-test-renderer equivalent.
Any help gratefully received.

Hi!
Yeah react-test-renderer and enzyme-to-json are working differently as react-test-renderer will display the output DOM elements. Have you tried using the Enzyme render wrapper? It should produce something closer to react-test-renderer, and in any case, you can use react-test-renderer if this is what you need.

I'll mark this as invalid for now because the output looks like what's expected to me, feel free to comment if you need help.

Not to be a pest, but I happen to side with @james-s-turner on this issue --- to my mind, the value of snapshots is that they are like freebie pinning tests, allowing you to refactor code in confidence that you haven't broken expected outputs (i.e. HTML). But if the serializer output includes internal details like Component names and prop values, it's no longer useful for refactoring, since those things are exactly what you'd be changing.
I also take your point that the render wrapper gives us the output we're looking for, but if we can't use mount we're missing out on some of the most powerful functionality that enzyme provides.
Any chance you'd be willing to reconsider this issue?

Hi @esimons,
My goal is to give output that looks like what you get using the Enzyme debug() helper. I unfortunately can't dig deeper in Enzyme wrappers. It looks as expected to me and I don't want to change the behaviour of these methods as I think it's a good thing not to go deeper in most cases.
For example I have components like that:
function SubComponent(props) {
  return The value is {props.value};
}

function MyComponent(props) {
  return <SubComponent value={props.value}/>;
}

If I want to unit test MyComponent, I prefer having this as a snapshot:
<SubComponent value={1}/>

than this:
The value is 1

The reason is that I don't want MyComponent snapshots to fail when SubComponent gets changed. All I want to know is that SubComponents are provided with the right props, then if the output is not right, SubComponent's unit tests should fail, not MyComponent's ones.
Let's say that I have 100 snapshots for MyComponent, 100 snapshots for SubComponent and SubComponent is changed, we need to replace the span by a div. In that case, we should update SubComponent's snapshots but why should MyComponent's snapshots fail?
I can hardly see a use case where you would like to do that, and if you do, the render wrapper should work fine. If you want to unit-test MyComponent, it's enough to check that SubComponents get the right props. Then you should test SubComponent and make sure it always renders the right elements given any values.
You can also do something like that:
expect(wrapper.find('SubComponent').mount()).toMatchSnapshot();

which will show what SubComponent is rendering.

Hey @adriantoine thanks for responding so quickly!
You make a great point, and I think you're right that in most cases we should be treating these snapshots as unit tests, rather than large-scoped tests of multiple components. In that sense shallow works wonders and will give you exactly the output you're looking for. And, as you pointed out earlier, if you wanted a larger-scoped test, you could use render to test actual HTML output.
My issue was that I was trying to use mount, which sits in an awkward place somewhere between those two poles and succeeds at neither, because it's basically outputting the combined data that shallow and render would give you (i.e. it renders out all child descendents, all the way down to leaf nodes, while also including custom component wrappers and props information between). So I would still kinda argue that the output of mount is not especially useful.
I can dig that we're not able to mess with the Enzyme wrappers here, though. I think I'll just have to change up my approach a bit. Thanks again, much appreciated!

I agree with @esimons and @james-s-turner.
If a function produces the same output the test should pass regardless of implementation details.
When you change a sub-component, the parent component's unit tests should fail because it's now doing something different.


Update README.md

Fixed typos, reformatted text to improve readability

Thanks! 👍

@lqez I'm looking forward to it being released ☺


Different Backbone

Thanks for your sharing.
If I want to use a different backbone such as PVCNN, does AutoGPart support it?

Hi,
Thanks for your attention.
I'm afraid that you need to write the backbone model you would like to use and set up the backbone in the main model's file such as model/motion_segmodel_cls_sea_v2.py like what we do self.conv_uniunet = PrimitiveNet(args) since only DGCNN and PointNet++ are supported currently.


Replace ; with , in csv files

I have replaced ; with , in csv files so that it is easier to view then on the site itself.

thanks for your effort - I don't see though why this is preferrable


MIC-495: DaiP: Identified need summary spacing on Intervention Details

Fixed spacing on identified needs details page
Fix for test on record-next-date page

Codecov Report
Attention: Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 60.04%. Comparing base (8e3db61) to head (e9f2089).

Files with missing lines
Patch %
Lines

...lop-an-initial-plan/next-review-date/controller.ts
50.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #174      +/-   ##
==========================================
+ Coverage   60.03%   60.04%   +0.01%
==========================================
  Files         193      193
  Lines        2647     2648       +1
  Branches      435      435
==========================================
+ Hits         1589     1590       +1
  Misses       1010     1010
  Partials       48       48

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Bug]: Packer is crashing while creating x86 snapshot

Description
Packer crashes while building the x86 snapshot.
Arm is running without errors.
==> hcloud.microos-x86-snapshot: 2023-07-17 12:01:05 (158 MB/s) - ‘openSUSE-MicroOS.x86_64-OpenStack-Cloud.qcow2’ saved [414580736/414580736] ==> hcloud.microos-x86-snapshot: ==> hcloud.microos-x86-snapshot: Provisioning with shell script: /var/folders/yz/q7cxzgw13b31vxjlq1xdjl9r0000gn/T/packer-shell1191919114 ==> hcloud.microos-x86-snapshot: + echo MicroOS image loaded, writing to disk...     hcloud.microos-x86-snapshot: MicroOS image loaded, writing to disk... ==> hcloud.microos-x86-snapshot: + ls -a ==> hcloud.microos-x86-snapshot: + grep -ie ^opensuse.*microos.*qcow2$ ==> hcloud.microos-x86-snapshot: + qemu-img convert -p -f qcow2 -O host_device openSUSE-MicroOS.x86_64-OpenStack-Cloud.qcow2 /dev/sda ==> hcloud.microos-x86-snapshot: /tmp/script_2705.sh: 4: qemu-img: not found ==> hcloud.microos-x86-snapshot: Provisioning step had errors: Running the cleanup provisioner, if present... ==> hcloud.microos-x86-snapshot: Destroying server... ==> hcloud.microos-x86-snapshot: Deleting temporary ssh key... Build 'hcloud.microos-x86-snapshot' errored after 1 minute 26 seconds: Script exited with non-zero exit status: 127. Allowed exit codes are: [0]
Kube.tf file
Not needed

Screenshots
No response
Platform
Mac

Well, "packer crashes" is not really the right term... if I read the logs right, qemu-imgcould not be found anymore, looks like Hetzner changed the image.

@kube-hetzner/core Can someone reproduce?

I just tested it with the latest version from master branch and it worked fine for me.
@ifeulner I think the image is not provided by Hetzner. The download URL is https://download.opensuse.org/repositories/devel:/kubic:/images/openSUSE_Tumbleweed/openSUSE-MicroOS.x86_64-OpenStack-Cloud.qcow2 and effectively you will be 302 redirected to a mirror that is close to you. See here:
# wget --timeout=5 --waitretry=5 --tries=5 --retry-connrefused --inet4-only https://download.opensuse.org/repositories/devel:/kubic:/images/openSUSE_Tumbleweed/openSUSE-MicroOS.x86_64-OpenStack-Cloud.qcow2
--2023-07-19 07:57:32--  https://download.opensuse.org/repositories/devel:/kubic:/images/openSUSE_Tumbleweed/openSUSE-MicroOS.x86_64-OpenStack-Cloud.qcow2
Resolving download.opensuse.org (download.opensuse.org)... <IP_ADDRESS>
Connecting to download.opensuse.org (download.opensuse.org)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://ftp.gwdg.de/pub/opensuse/repositories/devel%3A/kubic%3A/images/openSUSE_Tumbleweed/openSUSE-MicroOS.x86_64-OpenStack-Cloud.qcow2 [following]
--2023-07-19 07:57:32--  https://ftp.gwdg.de/pub/opensuse/repositories/devel%3A/kubic%3A/images/openSUSE_Tumbleweed/openSUSE-MicroOS.x86_64-OpenStack-Cloud.qcow2
Resolving ftp.gwdg.de (ftp.gwdg.de)... <IP_ADDRESS>
Connecting to ftp.gwdg.de (ftp.gwdg.de)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 414646272 (395M) [application/octet-stream]
Saving to: ‘openSUSE-MicroOS.x86_64-OpenStack-Cloud.qcow2’

openSUSE-MicroOS.x86_64-OpenStack-Cloud.qcow2  100%[=================================================================================================>] 395.44M   225MB/s    in 1.8s

2023-07-19 07:57:34 (225 MB/s) - ‘openSUSE-MicroOS.x86_64-OpenStack-Cloud.qcow2’ saved [414646272/414646272]
# ls -a | grep -ie '^opensuse.*microos.*qcow2$'
openSUSE-MicroOS.x86_64-OpenStack-Cloud.qcow2

@M4t7e I meant the Hetzner rescue image, this provides the qemu-img binary that is used to write the MicroOS image to disk. And that one was not found regarding to the logs provided above.

@ifeulner Yes, I also got it after I posted it and edited my comment immediately... sorry ^^
Here is how my image looks like and now I tested it about 5 times. Still can't reproduce...
==> hcloud.microos-x86-snapshot: + cat /etc/os-release
    hcloud.microos-x86-snapshot: PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
    hcloud.microos-x86-snapshot: NAME="Debian GNU/Linux"
    hcloud.microos-x86-snapshot: VERSION_ID="12"
    hcloud.microos-x86-snapshot: VERSION="12 (bookworm)"
    hcloud.microos-x86-snapshot: VERSION_CODENAME=bookworm
    hcloud.microos-x86-snapshot: ID=debian
    hcloud.microos-x86-snapshot: HOME_URL="https://www.debian.org/"
    hcloud.microos-x86-snapshot: SUPPORT_URL="https://www.debian.org/support"
    hcloud.microos-x86-snapshot: BUG_REPORT_URL="https://bugs.debian.org/"
==> hcloud.microos-x86-snapshot: + which qemu-img
    hcloud.microos-x86-snapshot: /usr/bin/qemu-img

Great @M4t7e, thanks for the info. It seems fixed then, they must have received complaints.

@Mammut-Felix can this be closed?

@Mammut-Felix @aleksasiriski I just doubled checked and all good, so closing this.


Implement attestation

Given that only enterprise usecases will probably need attestation, I won't be implementing this now.
However if your company really needs this you can sponsor me on GitHub Sponsors to work on this issue


Share 2.4 GHz frequency from the same adapter connected to 5.0 GHz

I have the following Wi-Fi card on my nettop:
[3.511768] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210
I can connect to 2.4 and 5.0 GHz networks successfully and share connection via the same card in 2.4 GHz mode. Now I connected to 5.0 GHz network and want to share internet via 2.4 GHz. My command is:
sudo create_ap wlp2s0 wlp2s0 -c 1 -w 2 --ieee80211n --ht_capab [HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-3839][DSSS_CCK-40] --country US SampleSSID SamplePasswd --freq-band 2.4
but I get the following error:
Config dir: /tmp/create_ap.wlp2s0.conf.KsVGb2e4
PID: 8093
Network Manager found, set ap26 as unmanaged device... DONE
wlp2s0 is already associated with channel 36 (5180 MHz), fallback to channel 36
Creating a virtual WiFi interface... ap26 created.

ERROR: Your adapter can not transmit to channel 36, frequency band 5GHz.

Doing cleanup..

Can create_ap be used to share connection via the second band?

wlan cards can only work on one frequency at one time


Blog section in the Arabic version

Assalamu Alaikum @alswajiab @BatoolMM the website does not have a blog section in the arabic version

The Blog use Quarto and we will open an issue to address this!

The Blog use Quarto and we will open an issue to address this!

Ok Ma @BatoolMM @alswajiab I will be waiting, please assign me to the task so we can add the blog dynamically, شكرلك


Documentation Request: How to alter the Apache config of a PHP application

Hi,
I wonder how I can make adjustements to the Apache Config for a PHP application? Like memory limits, upload limits etc.. Two things I'd like to configure:

Apache config for this very application
PHP config for this very application

For now look at the docs on Heroku for the buildpack, we'll add docs to our site in the future.
https://devcenter.heroku.com/articles/custom-php-settings

Alright, thank you. :)

Would be done via https://github.com/flynn/flynn/pull/2223


Do not overwrite existing labels on auto generated dependency upgrade…

Automation task to detect and file issue to upgrade dependencies is overwriting labels if issue already exists for that package but with older version details.

@weshaggard  @benbp Can you please review and approve this PR? Thanks


Disable turbo boost on dashboard box

I've noticed that the analysis benchmarks tend to be a bit faster after they haven't run for a while, but then are consistently about 12% slower for the following commits.

I suspect that the mac mini is enabling turbo boost for that first run after a long quiet period and then disabling it for subsequent runs. We should probably disable turbo boost for the dashboard box. The best source I could find for doing that was here: https://github.com/nanoant/DisableTurboBoost.kext.
@yjbanov

This is a non-trivial customization that will be hard to maintain (e.g. when we add/change build boxes we'll have to remember how to configure it correctly). I'm surprised that multiple runs of the benchmark doesn't solve this problem already.

This is a non-trivial customization that will be hard to maintain

No arguments here, but I do want to get reliable analysis numbers for the graphs. There are probably a few ways to get that, including having an analysis/benchmarking box with turbo boost disabled. Many of the comments that I found - for why people were trying to disable turbo boost - were benchmarking related.

I'm surprised that multiple runs of the benchmark doesn't solve this problem already.

Turbo boost is probably active for the first run, so that gets taken as the fastest number.
Let's keep this issue open so that we're aware of the issue.

Its not uncommon for perf frameworks to discard extremes or first n runs
explicitly.
On May 31, 2016 11:54 AM, "Devon Carew"<EMAIL_ADDRESS>wrote:

This is a non-trivial customization that will be hard to maintain
No arguments here, but I do want to get reliable analysis numbers for the
graphs. There are probably a few ways to get that, including having an
analysis/benchmarking box with turbo boost disabled. Many of the comments
that I found - for why people were trying to disable turbo boost - were
benchmarking related.
I'm surprised that multiple runs of the benchmark doesn't solve this
problem already.
Turbo boost is probably active for the first run, so that gets taken as
the fastest number.
Let's keep this issue open so that we're aware of the issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/4262#issuecomment-222785200,
or mute the thread
https://github.com/notifications/unsubscribe/ALTvi_gYKgpjQv_vM35igGGEXi_yQ2wOks5qHIP5gaJpZM4IpEq-
.

@devoncarew Should we close this given you landed https://github.com/flutter/dashboard_box/pull/79 and @yjbanov gave a reason to be skeptical about actually changing the hardware configuration?

sgtm


Failed to Execute Command in Laravel Queue

Q
A

Bug?
yes

FFmpeg Version
0.6.1

OS
18.04

Actual Behavior
The function run perfectly in controller function when upload a video. but due to time consuming task I put laravel queue for the same functionality.
Now the queue succsully dispacthed and when I process the queue with php artisan queue:work it getting error like below..
 [2020-03-18 05:53:01] production.ERROR: Alchemy\BinaryDriver\Exception\ExecutionFailureException: ffmpeg failed to execute command '/usr/bin/ffmpeg' '-y' '-i' '/home/forge/apertr.com/public/frontend/video/15927476571584510288.mp4' '-threads' '12' '-vcodec' 'libx264' '-acodec' 'libmp3lame' '-b:v' '1000k' '-refs' '6' '-coder' '1' '-sc_threshold' '40' '-flags' '+loop' '-me_range' '16' '-subq' '7' '-i_qfactor' '0.71' '-qcomp' '0.6' '-qdiff' '4' '-trellis' '1' '-b:a' '256k' '-ac' '2' '-pass' '1' '-passlogfile' '/tmp/ffmpeg-passes5e71b73dabd3b9x9qc/pass-5e71b73dabdb0' '/home/forge/apertr.com/frontend/posts/video/org-post/n-w-post-video-org/4965651901584510781.mp4' in /home/forge/apertr.com/vendor/alchemy/binary-driver/src/Alchemy/BinaryDriver/ProcessRunner.php:100

Anybody please give me a solutions to fix this issue. I can only work with Laravel queue because this functionality taking too many times for large sized videos.
Based on the reference I understood it may be a permission to issue. but I gave 777 permission to public folder(saving ffmpeg output).
Please give me an update on the same ..
Thank You

Please post the output of /usr/bin/ffmpeg -y -i /home/forge/apertr.com/public/frontend/video/15927476571584510288.mp4 -threads 12 -vcodec libx264 -acodec libmp3lame -b:v 1000k -refs 6 -coder 1 -sc_threshold 40 -flags +loop -me_range 16 -subq 7 -i_qfactor 0.71 -qcomp 0.6 -qdiff 4 -trellis 1 -b:a 256k -ac 2 /home/forge/apertr.com/frontend/posts/video/org-post/n-w-post-video-org/4965651901584510781.mp4 running manually in a shell.


How to use multiple symbols in ck editor for different data set

From this reference I had implemented the atWho functionality in CK editor using one symbol (@) for one data set.
But I was not able to to add another symbol (#) for another data set, can someone please explain how can I use multiple symbols in CK editor for different datasets as we are using in normal text area.
@Shade- Can you please help me with this?

var mentions_config = {
    at: "@",
    data: names,
    tpl: "
${name} ${email}
"
},
      hashtags_config = {
    at: "#",
    data: names,
    tpl: "
${name} ${email}
"
};

CKEDITOR.on('instanceReady', function(event) {

    var editor = event.editor;

    // Switching from and to source mode
    editor.on('mode', function(e) {
        load_atwho(this, mentions_config);
        load_atwho(this, hashtags_config);
    });

    // First load
    load_atwho(editor, mentions_config);
    load_atwho(editor, hashtags_config);

});

This should work. load_atwho() does not need to be edited.

@Shade- Thanks for your quick reply. I had tried the way you suggested.
But for me only hashtags are working, mentions are not being initiated.
Can you please check my code and let me know where I have been making the mistake?
my code:
  /* code for adding '@', '#' feature in ck editor */
  var mentions_config = {
    at: "@",
    data : ['feature','enhancement','bug','explore'],
    tpl: "@${data}"
  },

    hashtags_config = {
    at: "#",
    data : ['feature-','enhancement-','bug-','explore-'],
    tpl: "#${data}"
  };

  // Bind to every CKEditor instance that'll load in the future
  CKEDITOR.on('instanceReady', function(event) {

      var editor = event.editor;

      // Switching from and to source mode
      editor.on('mode', function(e) {
          load_atwho(this, mentions_config);
          load_atwho(this, hashtags_config);
      });

      // First load
      load_atwho(editor, mentions_config);
      load_atwho(editor, hashtags_config);
  });

  function load_atwho(editor, at_config) {

      // WYSIWYG mode when switching from source mode
      if (editor.mode != 'source') {

          editor.document.getBody().$.contentEditable = true;

          $(editor.document.getBody().$)
              .atwho('setIframe', editor.window.getFrame().$)
              .atwho(at_config);

      }
      // Source mode when switching from WYSIWYG
      else {
          $(editor.container.$).find(".cke_source").atwho(at_config);
      }
  }

Looks good to me. It might be that .atwho() overwrites the old attached events – you can check this by switching positions of load_atwho() calls and you should see mentions working and hashtags not.
If this is the case, at.js needs to be updated with chain capabilities instead of overwriting ones.

Thanks @Shade- I will check that as well.


NoyAcg cannot load comics images and cover images

Source information
NoyAcg 1.4.2
Source language
中文 (Chinese)
Steps to reproduce

Open NoyAcg image source;
Unable to successfully display the comic cover.

Expected behavior
Successfully displayed comic cover and title
Actual behavior
Only the title can be successfully displayed, the image is displayed as blank
Mihon/Tachiyomi version
0.16.5
Android version
Android 14
Other details
NoyAcg's App and Web can successfully load images
Acknowledgements

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

It seems to be back to normal, for reasons unknown…


heisenbug: see translation toggle not always working

sometimes, i deactivate "see translation", and still, the translations are still inserted in the page.

once in this mode, even after refreshing the page, the toggle still does not work.
actually, another problem with this: the preference is not stored in LocalStorage, so once the page is refreshed, it's always reset to 'see translation'. so i see two options:

either we remove completely the toggle (i don't think there are many users who would only use the speech feature)
or we fix it :)

So you mean you have disabled it and you want translations to be hidden?
The tooltip says: "Click to -> See Translation / Hear Pronunciation" so it doesn't imply that after you untoggle it you will hide all the translations? If you mean that you untoggled it and then click a word and still get translations, I am not able to replicate that.
Shouldn't this be a web issue?
I can add a value to track this in LocalStorage, I think a possible reason why it isn't done is because of the Extension, so for this case we might want to use a cookie instead.


Module / Package Refactor

Goals

Support browserify, webpack, bower, and Sentry's CDN (which means native bundled distribution)
Break raven.js into a more modular system, where the ideal installation doesnt use our CDN, but rather uses require() technologies
Combine raven-node and raven-js codebases and npm package

package.json can specify a 'browser' attribute to override this for npm

Get the codebase into a position for future code reuse between the two projects

Proposal
API
The primary target here is module-based usage, so the following should work:
var Raven = require('raven');

Raven.config().install()

Both the node.js client and the javascript client should expose the same APIs. That is, they should expose the spec from Sentry with identical arguments (to the best of their ability).
Code Exposure
Internally (via the module system) we want to expose a great deal of Raven. If we can, all of it. That said, 'raven' itself would only export the public namespaces, and you'd have to include other module(s) to get access to those.
Plugins
Modeled after webpack, instead of straight up patching, each plugin would have a load/unload hook responsible for it's behavior:
var ravenjQ = require('raven/plugins/jquery');

Raven.config({
	plugins: [new ravenjQ()]
});

Alternatively we could namespace builtin plugins:
Raven.config({
	plugins: [new Raven.plugins.jQuery()]
});

Bundling
We need to determine how best to bundle things with the umd wrapper. There are things like grunt-umd to aid with this.
See also: https://github.com/umdjs/umd/blob/ce6c20e318e58cd301ee929135cf651b02392c08/returnExports.js
This will still need a build task, but the primary resource for this is the Sentry CDN, so it's possible we can move the dist/ out of the codebase.
The raven.js bundle would expose the identical namespace as 'raven'. That is, only the public API and none of the others.
Notes

raven-node isn't very used
code reuse is the lowest priority, the goal is simply a better experience for end-users

:+1: to putting each plugin in its own module. The second option (Raven.plugins.jQuery) would mean they'd always be included in browser builds—even when you don't want them.
Also, if you already plan on using webpack, it can target UMD.

Echoing @matthewwithanm – :+1: to having each plugin in its own module.

Browserify can also build for UMD. It has the advantage of being able to expose build configure via package.json that parent packages can consume. Webpack has some very compelling features for building browser apps but I'm still very wedded to browserify since I publish a ton of modules.
For actually generating these UMD builds and getting the ./dist dir out of master, check out https://github.com/bendrucker/publicist
It's very much geared towards my style right now but I'd be happy to make it more configurable.

:+1:

While refactoring, keep in mind the possibility of offline use, see #279


Can't build the executable

Hi, dumb question here. I'm trying to build the executable and get the following error when doing stack install:

/Users/max/dev/advent-of-code-2022/app/AOC.hs:1:1: error:
    File name does not match module name:
    Saw: ‘Main’
    Expected: ‘AOC’
  |
1 | {-# LANGUAGE OverloadedStrings              #-}
  | ^

I'm pretty new to haskell ecosystem so there is a big chance I'm doing something wrong.

Solved. Had to rename aoc.hs.


Pluses becoming spaces in upstream string parameters

I have found that string parameters with pluses in them have the pluses replaced by spaces. I stopped this by URL-encoding the postData values in the SRDefaultHttpHelper postInternal:… method. I'm guessing that this ought to be done since the data is posted as application/x-www-form-urlencoded.
Is this a bug in SignalR-ObjC (I can submit a pull request if you like) or am I doing something wrong?

SRDefaultHttpHelper has been removed in favor of AFNetworking


How to change fonts for specific letters

Is there a way to update the font only for English letters and numbers? I know that changing the font updates all of the button's text with the following code.
override func viewWillSetupKeyboard() {
        super.viewWillSetupKeyboard()
        setup { [weak self] controller in
            VStack {
                Spacer()
                HStack {
                    SystemKeyboard(
                        state: controller.state,
                        services: controller.services,
                        buttonContent: {
                            $0.view
                                .font(.custom("Londrina Outline", size: 20))
                        }
                        ,
                        buttonView: { $0.view },
                        emojiKeyboard: { $0.view },
                        toolbar: { _ in }
                    ))
                    Spacer()
                }
            }
            .edgesIgnoringSafeArea(.all)
        }
    }

Hi @sagarthecoder!
You could check the controller.state.keyboardContext, and see if the .keyboardType is alphabetic or numeric, and the .keyboardLocale is english.


CIV-9615 View the defendants response - Dispute + Full paid

JIRA link
https://tools.hmcts.net/jira/browse/CIV-9615
Change description
View the defendants response screen in the scenario where the Defendant has Disputed the claim and states they have already paid the amount that they owe (and the amount they state paid is the full amount of the claim)
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Unblocked


Support for vitests 1.x (without forcing the dependencies)

Hi:
The current version has:
 "peerDependencies": {
...
    "vitest": ">=0.34.0"
  },

Which is good!
However npm interpret it as "vitest": ">=0.34.0 && < 1".
Could you change it to be more explicit to support vitests versions greater than 1? with something like:
 "peerDependencies": {
...
    "vitest": ">=0.34.0 || >=1.0.0"
  },

Thanks for your contribution! It's released


Implemented is_trained() and fixed bug for duplicate training on Parametric Models

Did some local changes on my own. LGTM if the CI passes.


Rename the tab model to Code Completion and add a description.

change tab model name
I think code completion is a more abstract and generic representation than the tab model.
Because tab is a way to accept code completion, it doesn't seem appropriate to call it by a formal name.
update code completion model description
Added information about FIM(Fill in the Middle) and the newest model, codegemma, to the code completion description, as well as the parameter sizes for each model.
Added llama3 as an example chat model.
It's not a code-specific LLM, but it has the highest human eval score of any open-source model.

@TyDunn Thanks for the review.
I agree with you, autocomplete is better than code-completion.
I've added all your suggestions, and renamed the file again.


LINK-1059 | Unify keyword set permissions with API

Description :sparkles:

Allow to create a keyword set only when user is admin in selected organization or organization is not selected and used is admin in any organization
Allow to update or delete keyword set only when user is admin in selected organization

NOTE! There is an open PR for Backend implementation at https://github.com/City-of-Helsinki/linkedevents/pull/563
Issues :bug:
Closes :no_good_woman:
LINK-1059

Codecov Report

Merging #167 (002dc93) into develop (aafd3fd) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff            @@
##           develop     #167   +/-   ##
========================================
  Coverage    99.70%   99.70%
========================================
  Files          499      498    -1
  Lines         9154     9159    +5
  Branches      1970     1975    +5
========================================
+ Hits          9127     9132    +5
  Misses          27       27

Impacted Files
Coverage Δ

src/domain/keywordSets/KeywordSetsPage.tsx
100.00% <ø> (ø)

src/domain/keywordSet/EditKeywordSetPage.tsx
100.00% <100.00%> (ø)

...keywordSet/createButtonPanel/CreateButtonPanel.tsx
100.00% <100.00%> (ø)

...ain/keywordSet/editButtonPanel/EditButtonPanel.tsx
100.00% <100.00%> (ø)

...rc/domain/keywordSet/hooks/useKeywordSetActions.ts
100.00% <100.00%> (ø)

...ification/KeywordSetAuthenticationNotification.tsx
100.00% <100.00%> (ø)

...omain/keywordSet/keywordSetForm/KeywordSetForm.tsx
100.00% <100.00%> (ø)

src/domain/keywordSet/utils.ts
100.00% <100.00%> (ø)

...rdSetActionsDropdown/KeywordSetActionsDropdown.tsx
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


AWS SpringFunctionInitializer missing support for Consumer's and Supplier's

It appears that support for Consumer and Supplier functions was removed in this diff: https://github.com/spring-cloud/spring-cloud-function/commit/083d5e3bf3bf030937b63c562f08756655c17f02#diff-934980775e5f2b8066472b737ac0cfcf
Is that right?
I am having trouble setting up a Supplier-based AWS Lambda, and can't see how it could work without the code removed in that diff.

I’d be happy to contribute this functionality.
Could you however give me some context as to why it was removed in the first place?  The commit message doesn’t really explain it, ”Harmonize AWS and azure adapters”


4 build-tests failing

I updated the README.md and noticed several Github build tests failing.
Were some dependent libraries updated such as pylint?
Maybe a future solution could be to specify a specific version of dependent libraries in https://github.com/thingsapi/things.py/blob/main/.github/workflows/tests.yml?
/cc @AlexanderWillner

@AlexanderWillner Possibly the changes made in #96 could help with this.

Green again here : https://github.com/thingsapi/things.py/pull/104

Basically fixed


Add Hack The South 2019

Is this Hack The South or Hack The South 2019?
I know I'm picky about these things....

Is this Hack The South or Hack The South 2019?
I know I'm picky about these things....

Just Hack The South, according to https://mlh.io/seasons/eu-2019/events