Moondream v2 (CPU) crashes with images (post predict EOF error) on 0.4.1

What is the issue?
Moondream v2 seems to run into an issue with images on CPU with 0.4.1,
resulting in Error: POST predict: Post "http://<IP_ADDRESS>:33685/completion": EOF.
Does not seem to affect GPU.
~ $ ollama run moondream:v2 "please describe this image /home/kwi/demo-2.png" --verbose
Added image '/home/kwi/demo-2.png'
Error: POST predict: Post "http://<IP_ADDRESS>:34833/completion": EOF
~ $ ollama run moondream:v2 hi

 Hi

$ ollama --version
ollama version is 0.4.1

Only seems to happen with images, not text. The model loads and runs fine for text chat, but consistently crashes with EOF when attempting to process any image.
journalctl:
level=DEBUG source=server.go:423 msg="llama runner terminated" error="signal: aborted"
What i tried so far.

Differen images
Different CPUS (Ryzen 5 6600H, Ryzen 7 5700X, i5-3320M)
Other vision models (minicpm-v and llama seem to work fine)
Different quants
CLI and through API

I had an older laptop around with an outdated ollama 0.3.1 on it, that still worked fine. Upgrading to 0.4.1 caused the exact same error to appear as well.
OS
Linux
GPU
No response
CPU
Intel, AMD
Ollama version
0.4.1

probably #7441.
Server logs would clarify.

Yes, I think this is #7441 - let's track it there.


Schema registry (1/4)

See #1137 for reference

I added it then reverted it. I think we only need it on the server. We
can tag messages as they come in and before we persist them to the topic,
right? Even if that's the case it might be useful to return the version
to the client.
On Thu, Mar 1, 2018 at 2:56 PM, Matteo Merli<EMAIL_ADDRESS>wrote:

@merlimat commented on this pull request.
In pulsar-common/src/main/proto/PulsarApi.proto
https://github.com/apache/incubator-pulsar/pull/1232#discussion_r171706547
:

@@ -408,6 +408,7 @@ message CommandProducerSuccess {
// The last sequence id that was stored by this producer in the previous session
// This will only be meaningful if deduplication has been enabled.
optional int64  last_sequence_id = 3 [default = -1];

optional bytes schema_version = 4;

@mgodave https://github.com/mgodave I think we need the schema_version
in producer_success. That should be attached to messages when publishing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-pulsar/pull/1232#pullrequestreview-100608456,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAh9Fl9jpkjSbk3j_h9vwhY9-abVOkB5ks5taG6igaJpZM4SEH6p
.

We can tag messages as they come in and before we persist them to the topic, right?

That would mean that we need to re-serialize the protobuf each time. If the producer sets it, we just take whatever buffer we have and store that in bk.

I'm updating the code. In the ServerCnx we store a list of the Producers
for a Topic. Each producer has a publishing schema associated with it and
will tag the messages as they are produced, this way the client is
completely uninvolved. Does this sound reasonable? I'm in deep and it's
uncharted territory for me on this codebase.
On Thu, Mar 1, 2018 at 3:41 PM, David Rusek<EMAIL_ADDRESS>wrote:

I added it then reverted it. I think we only need it on the server. We
can tag messages as they come in and before we persist them to the topic,
right? Even if that's the case it might be useful to return the version
to the client.
On Thu, Mar 1, 2018 at 2:56 PM, Matteo Merli<EMAIL_ADDRESS>wrote:

@merlimat commented on this pull request.
In pulsar-common/src/main/proto/PulsarApi.proto
https://github.com/apache/incubator-pulsar/pull/1232#discussion_r171706547
:

@@ -408,6 +408,7 @@ message CommandProducerSuccess {
// The last sequence id that was stored by this producer in the previous session
// This will only be meaningful if deduplication has been enabled.
optional int64  last_sequence_id = 3 [default = -1];

optional bytes schema_version = 4;

@mgodave https://github.com/mgodave I think we need the schema_version
in producer_success. That should be attached to messages when publishing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-pulsar/pull/1232#pullrequestreview-100608456,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAh9Fl9jpkjSbk3j_h9vwhY9-abVOkB5ks5taG6igaJpZM4SEH6p
.

yeah, I see that... OK.
On Thu, Mar 1, 2018 at 3:44 PM, Matteo Merli<EMAIL_ADDRESS>wrote:

We can tag messages as they come in and before we persist them to the
topic, right?
That would mean that we need to re-serialize the protobuf each time. If
the producer sets it, we just take whatever buffer we have and store that
in bk.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-pulsar/pull/1232#issuecomment-369757306,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAh9FhYo6Qzuh-xreRXUe-HRIhIQjitbks5taHnjgaJpZM4SEH6p
.


[BUG] background visible

Description
In glow mode, the background is visible in the links.
You can check on my profile.
https://www.biodrop.io/oyepriyansh
Screenshots

Do you want to work on this issue?
No
Additional information
No response

I can give this a shot. Thanks!

I would like to take it up. Thankyou!

I am not able to reproduce the issue, can you give steps to reproduce

Hey! @oyepriyansh I can give it a try.

Hey! @oyepriyansh I can give it a try.

I am not the maintainer of this repository. You can just leave a comment here, and a maintainer may assign the task to you

Hey @oyepriyansh, can you give more details on the issue since everything looks fine when I open your site

@oyepriyansh ,

Everything looks fine when i open your site! Please provide more details

Could you provide the steps to reproduce the bug @oyepriyansh ? It seems like a lot of devs can't seem to replicate the bug, including me.

Tried it on Firefox, Edge, and Chrome but this looks fine to me.

Tried it on Safari Browser. The issue persists.

I could reproduce the issue (Safari). It seems like there is a rounded-full value missing on the parent div of the a. I would be happy to work on this issues 🙂

I could reproduce the issue (Safari). It seems like there is a rounded-full value missing on the parent div of the a. I would be happy to work on this issues 🙂

Thanks @YuriDevAT ! I have assigned this to you.

Conclusion
❗After thoroughly researching the topic, I came to the conclusion that either

reduce the effect in general or
leave it and hope for Safari Browser support in the future.

Why? My findings
Safari does not support Animation on selectors like ::before or ::after. When removing (or reducing) the animation, in this particular case it is the background-size on ::after which should be reduced to 100%, removes the buggy background, which is only a problem in Safari. Therefore it would make sense to get somehow the information if the user is currently in a Safari browser. I tried to use userAgent as well as @support but both did not work.
Result: The animation effect is not that intense anymore.
Example of @support
@supports
selector(:nth-child(1 of x)) {
...
}

More details:
I created an article on dev.to to explain in detail, share code and screenshots, and get help from other developers who are more experienced with CSS Animation.
Pull Request
Please let me know how I should proceed with this issue

If I should wait for someone who comes up with a better support rule which works for sure (but even those can be outdated soon),
if I should reduce the background-size in general, or
if I should leave it as it is (I guess, the issue gets closed, no PR needed)

Thank you @YuriDevAT for the detailed research 🚀
Can we see what it looks like using option 2 "the reduced background size"?

Please find the link to my codepen, which has currently the reduced background size.
https://codepen.io/YuriDevAT/pen/NWoPwpx
If you comment out line 61, you can see the difference. By setting the size down to 100%, the effect is almost only on the ::before and not that that WOW anymore.

I would like to take it up. Thankyou!

Please find the link to my codepen, which has currently the reduced background size.
https://codepen.io/YuriDevAT/pen/NWoPwpx
If you comment out line 61, you can see the difference. By setting the size down to 100%, the effect is almost only on the ::before and not that that WOW 👀 anymore.

it looks great @YuriDevAT 👍

I would like to take it up. Thankyou!

@mahesh-s33 this issue is already assigned, please check the assignee section in the issue first

I would like to take it up. Thankyou!

@mahesh-s33 this issue is already assigned, please check the assignee section in the issue first

Sure i'll collaborate once the PR is raised.


Wrong TS definition in GameObjectFactory for BitmapText

This Issue is about

An error in the TypeScript definitions

BitmapText has size and ALIGN properties, but game.add.bitmaptext has size and GROUP

PR #461

game.add.bitmapText has no ALIGN properties in GameObjectFactory.js
https://github.com/photonstorm/phaser-ce/blob/dc45d8279fd0c0e86577c1e7332d962765c65c55/src/gameobjects/GameObjectFactory.js#L459
GameObjectCreator.bitmapText is in L1594, not L1624
https://github.com/photonstorm/phaser-ce/blob/dc45d8279fd0c0e86577c1e7332d962765c65c55/typescript/phaser.d.ts#L1594
You should not directly modify line 1624 of the TS definition.


Refactor slate

Summarize:

upgrades to latest slate
adds new factories to create slate plugins
allow to customize built-in slate plugins more easily

fixes https://github.com/react-page/react-page/issues/713
BREAKING CHANGE:
slate has been updated to latest version and contains some breaking changes. So if you use custom slate plugins, these might need some changes.
content however will be migrated thanks to the awesome migration system of react-page 👍
BREAKING CHANGE:
The slate plugin customization of version 0.8.x of react-page no longer is supported.
If you had
const slatePlugin = slate([

  new slatePlugins.HeadingsPlugin({
    allowedLevels: [1, 2, 3],
    getComponent: ({ type }) => {
      return MyCustomHeadingsComponent
    },
  }),
// ... other slate plugins
]);

you now have to use this:
const slatePlugin = slate([

  slatePlugins.headings.h1(),
  slatePlugins.headings.h2(),
  slatePlugins.headings.h3(
    // customization is now more flexible, see below
   def => ({
      Component: MyCustomHeading3
   })
  ),

// ... other slate plugins
]);

customize slate plugins:
if you just use slate() all default plugins will be loaded as before, so you don't need to change anything
select plugins
if you don't want to use all plugins, you can define the list of all slate plugins yourself:

import slate, { slatePlugins } from "@react-page/plugins-slate";

// this is the list of all default plugins, remove the ones you don't need
const slatePlugin = slate([
    slatePlugins.headings.h1(),
    slatePlugins.headings.h2(),
    slatePlugins.headings.h3(),
    slatePlugins.headings.h4(),
    slatePlugins.headings.h5(),
    slatePlugins.headings.h6(),
    slatePlugins.link(),
    slatePlugins.lists.ul(),
    slatePlugins.lists.ol(),
    slatePlugins.lists.indention(),
    slatePlugins.emphasize.em(),
    slatePlugins.emphasize.strong(),
    slatePlugins.emphasize.underline(),
    slatePlugins.alignment.left(),
    slatePlugins.alignment.center(),
    slatePlugins.alignment.right(),
    slatePlugins.alignment.justify(),
    slatePlugins.paragraph(),
    slatePlugins.blockquote(),
    slatePlugins.code.mark(),
    slatePlugins.code.block(),
]);

also this allow to re-arange the plugins order
customizing existing plugins:
every of these built-in-plugins consume a customize function. E.g. if you want to change the component that is used to render the plugin:
 headings.h1(def => ({
    ...def,
    Component: props => (
        <MyCustomH1 style={{align: props.data.get("align")}}>{props.children}</MyCustomH1>
   )
  })),

typescript users should get nice types in the customize function. Also you can provide custom controls, see the built-in link plugin how this can be done. We will provide a more convenient way to add controls to your slate plugin in the near future.
create your slate plugin from scratch:
There are some factory functions that let you create plugins easily:
createComponentPlugin: allow to create a plugin which has a component (most built-in plugins use this factory).
createDataPlugin: this plugin toggles data on the current block or inline element, but does not render a component. E.g. the alignment-plugin uses that factory
createSimpleHtmlBlockPlugin: a more convenient variant of createComponentPlugin. It renders a simple component with a html-tag. used by plugins like headings or blockquote
createMarkPlugin: similar to createSimpleHtmlBlockPlugin but renders a "mark" with a hover button on selection
you can import these with:
import {pluginFactories} from '@react-page/plugins-slate'

initial comment
this is a big one
Makes creating new slate plugins as easy as:

const link: SlatePluginDefinition<LinkData> = {
  DEFAULT_NODE,
  type: 'LINK/LINK',
  object: 'inline',
  icon: <LinkIcon />,
  addHoverButton: true,
  addToolbarButton: true,
  Controls,
  deserialize: {
    tagName: 'a',
    getData: el => ({
      href: el.getAttribute('href') || '',
      openInNewWindow: el.getAttribute('target') === '_blank',
    }),
  },
  Component: ({ children, data }) => {
    return (
      <a
        target={data.get('openInNewWindow') ? '_blank' : undefined}
        href={data.get('href')}
      >
        {children}
      </a>
    );
  },
};

export default createComponentPlugin(link);

It enables to create new plugins much easier. In particular, because you don't have to deal with much of slate's complexity.
I wanted to refactor it, because i need to have a pageLink component in my project, which will not store the href of the target page, but its database-id and its custom link component will create the href based on that. Now this should be much easier and straight-forward to do. i will also add late a schema-based Control for it.
In the current state, the Link still has a somewhat complicated Controls Component (which displays inputs to insert/update a link) and i want to make that much simpler

This looks way better than what we had, it should also fix #498 and some other copy/pasting issues too, good work 👍

Since this nice improvments were merged, I'm having trouble with the slate plugin on Firefox (Windows). The Cursor jumps after some key strokes on the end of the last text chunk. So the first letter is on the right position and all following appear on another position.
Chrome is working fine.
Could somebody please check this behavior?
Just checkout master, install and start (with Firefox). Try typing inside the text.

hi @Fivedark, can confirm this problem also on firefox on mac


[BUG] 微调训练时要用transformers==4.27.1,而推理时却要用transformers==4.26.1

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
微调训练时要用transformers==4.27.1的版本，
而推理时却要用transformers==4.26.1的版本，
否则出错，
求统一版本！
Expected Behavior
求微调训练时和推理时transformers用统一版本4.27.1
Steps To Reproduce
ModuleNotFoundError: No module named 'transformers_modules.'
(d:\py310) D:\ChatGLM-6B>pip install transformers==4.26.1 -i https://mirrors.aliyun.com/pypi/simple/
Looking in indexes: https://mirrors.aliyun.com/pypi/simple/
Collecting transformers==4.26.1
Downloading https://mirrors.aliyun.com/pypi/packages/1e/e2/60c3f4691b16d126ee9cfe28f598b13c424b60350ab339aba81aef054b8f/transformers-4.26.1-py3-none-any.whl (6.3 MB)
---------------------------------------- 6.3/6.3 MB 4.3 MB/s eta 0:00:00
Requirement already satisfied: tqdm>=4.27 in d:\py310\lib\site-packages (from transformers==4.26.1) (4.65.0)
Requirement already satisfied: huggingface-hub<1.0,>=0.11.0 in d:\py310\lib\site-packages (from transformers==4.26.1) (0.13.2)
Requirement already satisfied: pyyaml>=5.1 in d:\py310\lib\site-packages (from transformers==4.26.1) (6.0)
Requirement already satisfied: numpy>=1.17 in d:\py310\lib\site-packages (from transformers==4.26.1) (1.24.2)
Requirement already satisfied: regex!=2019.12.17 in d:\py310\lib\site-packages (from transformers==4.26.1) (2022.10.31)
Requirement already satisfied: requests in d:\py310\lib\site-packages (from transformers==4.26.1) (2.28.2)
Requirement already satisfied: filelock in d:\py310\lib\site-packages (from transformers==4.26.1) (3.9.1)
Requirement already satisfied: packaging>=20.0 in d:\py310\lib\site-packages (from transformers==4.26.1) (23.0)
Requirement already satisfied: tokenizers!=0.11.3,<0.14,>=0.11.1 in d:\py310\lib\site-packages (from transformers==4.26.1) (0.13.2)
Requirement already satisfied: typing-extensions>=<IP_ADDRESS> in d:\py310\lib\site-packages (from huggingface-hub<1.0,>=0.11.0->transformers==4.26.1) (4.5.0)
Requirement already satisfied: colorama in d:\py310\lib\site-packages (from tqdm>=4.27->transformers==4.26.1) (0.4.6)
Requirement already satisfied: charset-normalizer<4,>=2 in d:\py310\lib\site-packages (from requests->transformers==4.26.1) (3.1.0)
Requirement already satisfied: certifi>=2017.4.17 in d:\py310\lib\site-packages (from requests->transformers==4.26.1) (2022.12.7)
Requirement already satisfied: idna<4,>=2.5 in d:\py310\lib\site-packages (from requests->transformers==4.26.1) (3.4)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in d:\py310\lib\site-packages (from requests->transformers==4.26.1) (1.26.15)
Installing collected packages: transformers
Attempting uninstall: transformers
Found existing installation: transformers 4.27.1
Uninstalling transformers-4.27.1:
Successfully uninstalled transformers-4.27.1
Successfully installed transformers-4.26.1
(d:\py310) D:\ChatGLM-6B>python main.py --do_predict --validation_file AdvertiseGen/dev.json --test_file AdvertiseGen/dev.json --overwrite_cache --prompt_column content --response_column summary --model_name_or_path ./output/checkpoint-3000 --output_dir ./output/checkpoint-2000 --overwrite_output_dir --max_source_length 64 --max_target_length 64 --per_device_eval_batch_size 8 --predict_with_generate --pre_seq_len 8 --quantization_bit 8
04/08/2023 18:55:09 - WARNING - main - Process rank: -1, device: cuda:0, n_gpu: 1distributed training: False, 16-bits training: False
04/08/2023 18:55:09 - INFO - main - Training/evaluation parameters Seq2SeqTrainingArguments(
_n_gpu=1,
adafactor=False,
adam_beta1=0.9,
adam_beta2=0.999,
adam_epsilon=1e-08,
Environment
- OS:window10
- Python:3.10
- Transformers:4.27.1/4.26.1
- PyTorch:2.11
- CUDA Support (`python -c "import torch; print(torch.cuda.is_available())"`) :11.7

Anything else?
无

在微调和推理的时候都应该使用4.27.1版本

不可能，绝对不可能。（曹操）
都用4.27.1 没问题。。


Docs for cider mention a .dir-locals.el that doesn't exist

https://github.com/djblue/portal/blob/3313b7baea86c422b06c3458d0362aa54272b745/doc/dev/editors.md?plain=1#L28
This linked file doesn't seem to exist in the repo anymore.

Good catch @Ramblurr, this use to live in the README so it should actually point to the one in the root of the repo. Did you want to put up a PR with the fix?


No module named 'super_faust'

Looks like the cookiecutter missed a bit of cutting because super_faust is found in my project :-P
make run-dev outputs:
replay_output_experiment_1  | Traceback (most recent call last):
replay_output_experiment_1  |   File "/usr/local/lib/python3.7/site-packages/faust/app/base.py", line 641, in discover
replay_output_experiment_1  |     module = importlib.import_module(name)
replay_output_experiment_1  |   File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module
replay_output_experiment_1  |     return _bootstrap._gcd_import(name[level:], package, level)
replay_output_experiment_1  |   File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
replay_output_experiment_1  |   File "<frozen importlib._bootstrap>", line 983, in _find_and_load
replay_output_experiment_1  |   File "<frozen importlib._bootstrap>", line 965, in _find_and_load_unlocked
replay_output_experiment_1  | ModuleNotFoundError: No module named 'super_faust'
replay_output_experiment_1  |
replay_output_experiment_1  | During handling of the above exception, another exception occurred:
replay_output_experiment_1  |
replay_output_experiment_1  | Traceback (most recent call last):
replay_output_experiment_1  |   File "/usr/local/bin/replay_output_experiment", line 11, in <module>
replay_output_experiment_1  |     load_entry_point('Replay-Output-Experiment', 'console_scripts', 'replay_output_experiment')()
replay_output_experiment_1  |   File "/replay_output_experiment/replay_output_experiment/app.py", line 18, in main
replay_output_experiment_1  |     app.main()
replay_output_experiment_1  |   File "/usr/local/lib/python3.7/site-packages/faust/app/base.py", line 672, in main
replay_output_experiment_1  |     self.discover()
replay_output_experiment_1  |   File "/usr/local/lib/python3.7/site-packages/faust/app/base.py", line 644, in discover
replay_output_experiment_1  |     f'Unknown module {name} in App.conf.autodiscover list')
replay_output_experiment_1  | ModuleNotFoundError: Unknown module super_faust in App.conf.autodiscover list
replay_output_experiment_replay_output_experiment_1 exited with code 1

Hi, thanks for de feedback. I know what is the problem. The project root is using a hardoded name instead of replacing it by the name generated by cookiecutter. I will fix it !

Hi again,
With this PR should be fixed https://github.com/marcosschroh/cookiecutter-faust/pull/12.

Cool, thank you.


Correct error path pool free pointer in sample

gTriageDumpDataArray points into the middle of a pool allocation that starts at pBuffer (and gBugcheckTriageCallbackRecord).

Thanks Dave, we appreciate the PR!  The change should reach the live site in a few minutes.


Copy portal to clipboard

This is another one of Jon's abandoned pull requests.
When you select a portal, if you copy it with (control/alt/command)-C, it fills the clipboard with:
a) the name of the portal
b) an intel-link to the portal
c) a google map-link to the portal (for directions)

Duplicate


Original file names on S3

thanks for the good library, its a great start for one of my projects. I was wondering why uploaded files on S3 have a random name (some number) instead of the original file name.
Is there a way to change that?

Can you please elaborate a bit more here.


fix typo err

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes # 618
Additional information
This is just a minor typo err about bootstrapKubeconfigDataStr
Special notes for your reviewer

Codecov Report

Merging #619 (1e973dc) into main (49a9cdb) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #619   +/-   ##
=======================================
  Coverage   68.99%   68.99%
=======================================
  Files          19       19
  Lines        1964     1964
=======================================
  Hits         1355     1355
  Misses        497      497
  Partials      112      112

Impacted Files
Coverage Δ

...s/infrastructure/bootstrapkubeconfig_controller.go
58.49% <100.00%> (ø)

@ruifaling Please sign the CLA

@shubham14bajpai @anusha94 ，thanks for your review! And I have signed the CLA,is there anything other I can do?This is my first pr about this project. I will be very happy to receive your guidance.


icons for external services are overlapping

@marek-berlin can u resolve this via GTM config pleasE?

done, nie wiem gdzie moge to oznaczyc jako finished.


Switch cluster-autoscaler to IRSA

What this PR does / why we need it
This PR allows cluster-autscaler to assume a specific IAM role for AWS API calls instead of using the instance profile.
Checklist

[x] Update changelog in CHANGELOG.md.

Trigger e2e tests

/run cluster-test-suites

/hold
capa-iam-operator needs to be released first.


Scene Tree Dock: added ability to cut/paste nodes.

Added ability to cut/paste of nodes on scene tree dock.
Of course we can just select nodes and move them via drag'n'drop to desired node, but cut/paste on tree/lists is something that is expected (nice to have, at least for Windows users).
This is how it works: https://i.imgur.com/7BdIdQY.gifv
Cut/paste icons: https://files.fm/u/w33v6624#_

It fails to build on X11 tools=yes: https://travis-ci.org/godotengine/godot/jobs/307510048
editor/scene_tree_dock.cpp: In member function 'void SceneTreeDock::_tool_selected(int, bool)':
editor/scene_tree_dock.cpp:511:16: error: 'CPC_ACTION' is not a class or namespace
     m.action = CPC_ACTION::NODE_CUT;
                ^
editor/scene_tree_dock.cpp:569:24: error: 'CPC_ACTION' is not a class or namespace
     if (item.action == CPC_ACTION::NODE_CUT)
                        ^

This is cool, probably too late for 3.0 (we are releasing beta imminently and feature freeze has kicked in).
but would be nice to merge after 3.0 is out. Does it support cutting and pasting between scenes? also would not Cuy/Copy/Paste make sense too?
Finally, the RMB menu likely is too crowded, so maybe it would need some reordering or using submenus for the least used options, too.

@akien-mga To be honest have no idea why it fails. May be some nix-user can advice why it fails, because compiles fine on Visual Studio and I don't use any special syntax there...
@reduz

Does it support cutting and pasting between scenes?

Yes, it is.

also would not Cuy/Copy/Paste make sense too?

I decided to start from just cut/paste (after all, at least having two of them is better than having nothing at all? :).
If people will like it, I was planned to add support for Copy in 3.1 :)
Problem is, since most of my recents PRs are not merged, its kinda uncomfortable for me to make new changes because either some of them requires my previous PRs or I have to carefully line-by-line merge PR changes within my local copy with up-to-date godot master instead of just files copy-over. So trying to make as much less changes, as possible.
P.S. I think its pretty safe to merge it into 3.0. Just try it, ensure yourself that is works pretty seamless and smooth. :) And just in case if you will do, don't forget to take also #13308, as it makes possible UX like "mouse clicked on empty space in scene tree dock to reset selection from current [non-root, for example] element, CTRL+V to paste element into root without manually selecting it".

Finally, the RMB menu likely is too crowded, so maybe it would need some reordering or using submenus for the least used options, too.
I think the same. But do nothing currently, due to feature freeze state. Once 3.1 development will be opened, I will start send more bold PRs :)

Maybe this doesn't need to be exposed in the RMB menu yet. It really is crowded. I'd also like Copy, though Ctrl+C is bound to "Copy node path" already.

Actually I assume that people will use hot keys. I added them just to let people know that these cut/paste command are exists :)
Initial problem with copy was that we already have Duplicate command there, didn't have enough time to decide. And yes, as you noted correctly - ctrl c is already bound. So I decided leave Copy implementation for 3.1, more time to think and experiment with.

Being able to copy nodes and trees between scenes is sorely lacking in Godot. If you can add this, it would be a massive boost to productivity :)

Can copy-paste as text too? could be interesting to share partial scene branches (something I have asked for visual script too), useful for tutorials, troubleshooting, etc., instead of sharing full projects or scene files.

@fracteed
@akien-mga
There is demonstration for cut-paste between scenes: https://i.imgur.com/qZn4TZf.gifv
Again, this my PR support cut-paste between scenes too. :)

@eon-s can you clarify your (feature) request? :) There is already "Copy Node Path", no? Or it's not work for you the way you want?

Like:
Copy a branch, paste on a text document.
Copy the text of a node branch structure, paste on a scene.

@eon-s Oh, now I see.
Looks like "Copy Node Path" support only one node, and can't work when multiple nodes are selected.

Copy a branch, paste on a text document.
Copy the text of a node branch structure, paste on a scene.
I can implement both as separate PR (for v3.1, too late for v3.0), but there is small problem as I just found - "Copy Node Path" copy node current name, not their type, so there is need to think about of a some kind of text "format" which can be reinterpreted correctly by Godot (for example CTRL+C on nodes branch, and CTRL+V it to text document like: "CurrentNodeName1 (NodeType) > CurrentNodeName2 (NodeType)", instead of current "CurrentNodeName1"_) and work fine for both ways (Nodes Branch -> Text Document and Text Document -> Nodes Branch), but this "format" assumes only nodes name/type, not nodes properties though having of which I assume can be kinda important for tutorials purpose. But I can be wrong.
In short, thing to think about.

@Krakean yes, it will need to copy everything, like a part of a scene file to keep relationships and values, I can open an issue with some example of this and ping you if interested.

@eon-s Yes, go ahead please. All details and possible test-cases. Will examine it after 3.0 release.

@Krakean awesome...this will be so useful! The screen capture goes so quickly, but does the menu option say "copy" or "cut" when you copy these? There should be an option for both. Also, does this allow copying/cutting a complex nested tree and maintaining this relationship when pasting? Anyway...great work so far :)

@fracteed

The screen capture goes so quickly, but does the menu option say "copy" or "cut" when you copy these?

Its only cut/paste. "Copy" a bit more complicated, so I decided to leave it for 3.1

Also, does this allow copying/cutting a complex nested tree and maintaining this relationship when pasting?

Allow. :)

@Krakean...thanks, I look forward to it. In all honesty, I think it would be rare for me to use a cut function, as I mainly want to copy arrangements of meshes,lights etc between scenes without having to instance them. Also copying particle systems between scenes would be very helpful...

IMO, this feature will be complete when copying will be supported. Cut doesn't add much compared to a simple drag and drop of the nodes, and cut/paste from one scene to another doesn't seem like a common use case. So I propose to postpone it to 3.1, and we can add functional copy, cut and paste working across scenes then as described in #3720.

@akien-mga Thing is, for example, for me much preferred way to do CTRL+X/V than dragging nodes by mouse, especially if you need to do this more than once. I assume that I'm not alone in this workflow.
So, why not just merge this PR? It does not ruin anything. Yes, it doesn't have Copy yet, but uhm, well, I assume that having even just Cut/Paste is better than just nothing at all (dragging only) :)
No one will be harmed due merge this PR :)
In v3.1 I'll add Copy.
Please, Remi. :)

bump? :)

@Krakean Are you still up for implementing Copy support? We're closing in on 3.1 alpha and later on the feature freeze, so time is running short.

So we now have three PRs for the same feature (#13309, #14810 and #19327) and implentation-wise we're preferring #19327 (though it still needs some more changes). Therefore closing as superseded by #19327. Thanks a lot for your work though!


Error Domain=com.alamofire.error.serialization.response Code=-1011 "Request failed: service unavailable (503)"

Dear Folks,
I am trying to send a message from my iPhone 6 / iOS 10.2.1 via Sensor Phone app. But I am getting this error. I have tried with both v1 and v2 versions. I get the same error. I have redeployed MMS twice and simulated this.
I am using below path to hit the mms server on HANA.
https://iotmmsiotservices-p194XXXXXXXtrial.hanatrial.ondemand.com/com.sap.iotservices.mms/v1/api/http/data/17a8f9d4-cdbd-4a4b-b67c-0000000000
I am working on a trial account.
Can some please help.
Regards
Amitabh

This error code means that backend is unavailable now.
Try to make request via Postman or Paw. And than use a library.

Issue resolved. Was calling the wrong MMS path.
Thanks
Amitabh


IDVA6-1145: Acsp membership for logged in user

Short description outlining key changes/additions

Implemented GET /acsp-members/
Add test for the relevant endpoint method
Follows LLD here:

https://companieshouse.atlassian.net/wiki/spaces/IDV/pages/4708106297/LLD+-+GET+acsp-members

JIRA Ticket Number
https://companieshouse.atlassian.net/browse/IDVA6-1145
Type of change

[x] New feature

Pull request checklist

[x] I have added unit tests for new code that I have added
[x] I have added/updated functional tests where appropriate
[x] The code follows our coding standards

An exhaustive list of peer review checks can be read here

CI: Security warnings found!

CI: Security warnings found!

CI: Security warnings found!

CI: Security warnings found!

CI: Security warnings found!

Krishna Patel
09:20
Hello :slightly_smiling_face:. I've just gone through the changes and they look good to me. Nice work!
FYI ^ going to merge now.

CI: Security warnings found!

CI: Security warnings found!


Use existing CultureInfo

Fixes #203. Given this fix CultureInfoCache could just as a easily be a helper function on the middleware since it's no longer an actual cache, but I wasn't sure if we would be able to get rid of the whole class like that. @DamianEdwards would that be possible?

:up::date: @DamianEdwards is OK with obsoleting it for now and just not using it anywhere. I've built that in now.

@ryanbrandenburg as discussed, is any change required to the middleware to ensure it uses the actual supplied instance of CultureInfo specified as being the default?

:shipit: after removing all the unrelated changes.

@DamianEdwards it appears we already used the existing instance of CultureInfo for DefaultRequestCulture so no change needed there.

Can we have a unit test, to make sure that's fix #203?


Update to prefixes for words starting with some, update to problematic words - #27

Description
Added some and somer to appropriate prefixes.
Added wednesday to problematic words and alphabetized existing.
Added tests for words starting with some , wednesday, and alphabetized existing test words.
Motivation and Context
Address the issue here: #27
How Has This Been Tested?

Tested with existing tests and added new words for testing:
  "some": 1,
  "somebodies": 3,
  "someone": 2,
  "somersault": 3,
  "somersets": 3,
  "somersetting": 4,

and
  "wednesday": 2,

Codecov Report

Merging #28 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #28   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           2      2
  Lines          74     74
=====================================
  Hits           74     74

Impacted Files
Coverage Δ

index.js
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0f5a304...28b5aac. Read the comment docs.

Thanks Autumn, released!


Wrong namespace

    public function deleteStore() {
      $it = new RecursiveDirectoryIterator( $this->storePath, RecursiveDirectoryIterator::SKIP_DOTS );
      $files = new RecursiveIteratorIterator( $it, RecursiveIteratorIterator::CHILD_FIRST );

500 Internal Server Error
Class 'SleekDB\RecursiveDirectoryIterator' not found (0)

Can not use deleteStore() function at all. How do you even commit code without checking? Starting to get disappointed, if it has this level of errors on the surface, it's getting obvious this code is not used at all, who knows what other bad things happen inside.

@dima-stefantsov I'm really sorry for the inconvenience; fix coming tomorrow :)

Hi @dima-stefantsov
I just did a new release version 1.0.3.
Please update to version 1.0.3 and this bug should be fixed now.
Please let me know if it works for you or if you are facing any other issues :)


[release/1.3] cherry-pick: runtime v2: Close platform in runc shim's Shutdown method.

Previously, the platform was closed as part of the Delete method when the
process was an init for a task and there were no more tasks after its deletion.
This can create problems if another task is created within the shim right after
the delete runs, which results in the platform being closed but the shim
continuing to run.
This change moves closing the platform to the Shutdown method after the shim's
context is canceled, which ensures the platform is only closed once the shim
is sure its done servicing containers.
Signed-off-by: Erik Sipsma<EMAIL_ADDRESS>Signed-off-by: Phil Estes<EMAIL_ADDRESS>

Needs #3908 to pass CI

Codecov Report

Merging #3907 into release/1.3 will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           release/1.3    #3907   +/-   ##
============================================
  Coverage        42.07%   42.07%
============================================
  Files              129      129
  Lines            14322    14322
============================================
  Hits              6026     6026
  Misses            7395     7395
  Partials           901      901

Flag
Coverage Δ

#linux
45.59% <ø> (ø)
:arrow_up:

#windows
37.01% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cbc39d6...e7a6dda. Read the comment docs.

LGTM

for discoverability:
backport of https://github.com/containerd/containerd/pull/3896
fixes https://github.com/containerd/containerd/issues/3895 for the 1.3 branch


Function expressions widen to {} in auto arrays

🔎 Search Terms
function expression widen widening auto array any empty objecr
🕗 Version & Regression Information

This is the behavior in every version I tried

⏯ Playground Link
https://www.typescriptlang.org/play?ts=5.5.0-dev.20240304#code/MYewdgzgLgBAhgJwQRhgXhgbQLoG4BQ+iKAdAA4CuEAFgBQBmFYwUAluDLQJQwDe+MGAgCmUCgjAwARFIIBfLgSJJkBAPRqYAPQD8hUJFjEATOix5CJ8lTrd0APj4Cho8ZJnzFlpMfWbd+EA
💻 Code
const arr1 = [];

arr1.push(function () {
  return "";
});

arr1;
// ^? const arr1: {}[]

const arr2 = [];

arr2.push(() => {
  return "";
});

arr2;
// ^? const arr2: (() => string)[]

🙁 Actual behavior
arr1's type after this .push is {}[]
🙂 Expected behavior
I'd expect the type at both of the checked locations to be the same ((() => string)[])
Additional information about the issue
Likely the difference comes from the fact that the function expression is context-sensitive - maybe this is just a design limitation. However, the same doesn't happen in JS with expando objects (TS playground):
const obj = {}

obj.foo = function () {
  return ""
}

const result = obj.foo
//    ^? const result: () => string

Wait, why is the function expression context-sensitive but the arrow function isn't?

Function expressions always have the implied this parameter. You can see how the problem gets "fixed" when we annotate it manually:
const arr3 = [];

arr3.push(function (this: unknown) {
  return "";
});

arr3;
// ^? const arr3: ((this: unknown) => string)[]


modified configurations for docker to show realtime active thread chart correctly

modified configurations for docker to show realtime active thread chart correctly using docker compose.

modified hbase version of quickstart app.

ping @koo-taejin


Cursor position after adding image

String emojiImage =
          'https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/${unifiedEmoji}.png';
final int index = insertQuillController!.selection.baseOffset;
final int length = insertQuillController!.selection.extentOffset - index;
insertQuillController!.replaceText(index, length, BlockEmbed.image(emojiImage), null);

Add image with image attribute, it is ok now, but after inserting image, the cursor position isn't correct position. it is showing earlier image inserted position.
for example
=>ABCDE[Cursor]
=>ABCDE[AddedImage]
=>ABCDE[Cursor][AddedImage]
after adding some text again, it shows cursor in correct position;
=>ABCDE[AddedImage]FG[Cursor]
How can I solve this issue?
Could you please kindly check it?
Thank you
Originally posted by @youth-flutter-dev in https://github.com/singerdmx/flutter-quill/discussions/688#discussioncomment-2264932

Hello there, on behalf the Flutter Quill Team I would like to thank you for opening your first issue. Your inputs and insights are valuable in shaping a stable and reliable version for all our users. Thank you for being part of the open-source community!

same for video

how about this pr?
https://github.com/singerdmx/flutter-quill/pull/1739


Document how token can be inserted in request for Apollo js client

We need a token to authenticate SC requests. We should add documentation on how we can do that. We need docs for the following:

Add token as a header for queries and mutations
Add token as a connection parameter for subscriptions: (refer: https://github.com/apollographql/apollo-link/issues/197). However I'm concerned how this will work and the token isn't available during the start time.

For reference: In SC's native websocket API, we send the token as a part of every request. So we do not face the same problem.

Is there currently a clean solution on how to change the token during runtime? For example if the user logs out and logs in with another account, and I want to resubscribe with the new token.

I am actively looking for a solution. @Jayesh333 did you find something?

Yess! After searching a lot, I found this in the official docs of Apollo - https://www.apollographql.com/docs/react/networking/authentication/
Not tested this, but looks good to me😊

I don't think this will work for the ws connection.

I just found a solution,
https://github.com/apollographql/apollo-server/issues/1505#issuecomment-419126391
This worked fine for me. The only issue I encountered is that "payload" argument wasn't added in the typescript file, so I suppose it's private.
Now the new issue I am getting when logging out and back in is "ObservableQuery with that id doesn't exist".

Hey @YourTechBud, the solution which @erodactyl seems to be the only proper solution as of now. I tried the subscription middleware as pointed in that solution like this:
const wsLink = new WebSocketLink({
  uri: websocketUrl,
  options: {
    reconnect: true,
  },
  webSocketImpl: ws,
})

const subscriptionMiddleware = {
  applyMiddleware: async (options, next) => {
    options.authToken = await getLoginToken()
    next()
  },
}

// add the middleware to the web socket link via the Subscription Transport client
wsLink.subscriptionClient.use([subscriptionMiddleware])

After doing this, the apollo client sends authToken in the payload object in every subscription start message. This solves all our problem. We just need to use the payload.authToken in the start message on the backend to authorize the subscription request.

Done documenting this. Will be published along with the release of v0.17.0

subscriptionClient is a private method.
ERROR in src/plugins/apollo.ts:52:8
TS2341: Property 'subscriptionClient' is private and only accessible within class 'WebSocketLink'.
    50 | }
    51 | // add the middleware to the web socket link via the Subscription Transport client
  > 52 | wsLink.subscriptionClient.use([subscriptionMiddleware])
       |        ^^^^^^^^^^^^^^^^^^

@abinhho can you see if this works: https://www.apollographql.com/docs/react/networking/authentication/


Publish version 1.0.0-alpha.1 to npm

Hi there,
Thanks for all the good work!
Kindly wanted to ask if you could publish the current version 1.0.0-alpha.1 to npm?
Would be greatly appreciated!
Thank you and keep it up!

Will get it up asap

Published to npm


Rename defaultValue,visable,setVisable on disclosure

As discussed in #1426, I have changed the name of defaultVisible, visible, and setVisible to defaultOpen, open, and setOpen respectively.
@diegohaz Can you please take a look and please let me know If something needs to be change.

Thank you for working on this @harshilparmar! The other components that are using visible need to be updated.

Nice! Thank you for working on this @harshilparmar!

It was my pleasure.Looking forward to more contribution 🚀 Thanks!!


TRP3's toolbar is above the World Map frame

Total RP 3's toolbar is incorrectly displayed above the world map frame, which is especially bad when the map is in fullscreen.

Blizzard don't set the strata of the world map frame to FULLSCREEN, instead they just raise it above the frame level of everything else one time (which is why things like pressing the talent hotkeys shows that panel above the map).
Only real fix is to change the default strata of the toolbar down to MEDIUM. Any higher and it'll overlay the map. This also fixes the other issue where the toolbar overlays our own frame when it itself is maximized.


[ERRAI-1106] Update com.google.elemental2 from 1.0.0-beta-1 to 1.0.0-RC1

JIRA: https://issues.jboss.org/browse/ERRAI-1106

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

ok to test

Jenkins please execute full downstream build

Jenkins please execute full downstream build

@tiagobento I don't think we have a downstream build setup for Errai. We might have to try building the workbench manually with this PR.

Had to revert this because one of our downstream projects (appformer) does not manage this dependency version. We will have to coordinate this upgrade there, and probably have them manage the version to avoid this issue in the future.


bump sketch-polyfill-fetch ^0.4.6 -> ^0.5.2

@skpm/builder has an old version of the sketch-polyfill-fetch library, since versions starting with ^0 are not treated the same way as ^1; meaning the latest version of the fetch polyfill will currently be 0.4.x.
Bumped the version of sketch-polyfill-fetch in @skpm/builder to get the bugfix from 0.5.2 which prevents certain cache settings.
Bumped @skpm/builder and @skpm/test-runner to new minor versions accordingly.

Thanks!


Npm to Yarn

Npm to Yarn

for installing tasks in parallel

Install & Start

yarn install + yarn start

Red: AS-IS (2m 30s ~ 4m 40s)
Blue: To-BE (57s ~ 1s)

AS-IS: 2m 30s ~ 4m 40s
To-BE: 57s ~ 1s


bring FLEx lite poc into lexbox

FLEx lite is the WeSay/LF replacement, right now it's just an aspnet core server that when run launches the users browser, we'll probably turn this into some kind of electron app in the future.
This also adds a CrdtCommits table to lexbox to facilitate syncing data. This should be considered experimental and subjet to change.There's also no auth right now, so this won't work as is, we need to get the openId stuff figured out and merged in before that will work. However FLEx lite is designed with offline in mind, so it'll work fine if it can't contact lexbox.
right now all the local webapp code lives in the backend folder, not sure that's the correct place for it. Thoughts?

1deb7d4bbfd5781f70298598556b8bf311462c32 seems to indicate that the new abstract change classes were a good move.


Drop table causes be crash

Describe the bug
Drop table causes be crash after schema change
To Reproduce
Steps to reproduce the behavior:

schema change
drop table
create table again

error log :
F0507 10:25:01.622939 19737 utils.cpp:1098] fail to destroy mutex. err=Device or resource busy

hi, the reason of this problem is the schema change lock is not released when drop tablet.
This is a bug of BE, it will be solved in release 0.10 soon.


Wiki Update Request: Add Q&A and Big-Picture Page in English

What I've changed ?

Translate Big-Picture and Q&A Pages

Added 2 files Q&A_en-US.md and Big-Picture_en-US.md
Repo here

Commits:

305065d docs(Q&A_en-US.md): add QA page english version
bccb290 docs(Big-Picture_en-US): add Big-Picture page English version
d9f4469 fix(Q&A_en-US): bolder the title
8ad1640 doc(Big-Picture_en-US.md): add blank row
a7c83b1 docs(Q&A_en-US.md): add blank rows

Reviewers:

@tuoxiansp

💯Thanks for the awesome work !


Update project URLs

I guess the owner has changed his username. I noticed that the project URL in the NuGet package browser wasn't correct at least.

Thanks @matachi.
I'm working on adding support for .NET Core to Ookii Dialogs, and will release a new NuGet package in a few days, which will include the updates you've done.
I also need to do the same for ookii-dialogs-winforms which you're welcome to submit a PR if you wish.

Cool!
No problem, I have made a pull request on that repository as well now: https://github.com/augustoproiete/ookii-dialogs-winforms/pull/5


Group handling

First of all many thanks for the great work! The Tradfri adapter is one of the main parts in my HA.
I have a problem using groups when parts of them are not active. For example, if a bulb is not connected to the power, the status of the group resets. So if the group is turned on (state=true) - which was turned off before - the group will be reset to state=false.
If devices from a group are addressed directly, this behavior does not occur. The whole thing can be fixed with the virtual groups. Here the behavior is as I expect it to be.
But unfortunately I have another problem with virtual groups:
I recently bought the new outlets, which unfortunately do not appear in the device selection for virtual groups.
Is it possible to list the outlets in the device selection for virtual groups?

@AlCalzone can you please add support for the ikea outlets in the virtual groups? Currently I'm only able to add bulbs and drivers to a group.

Hey @red-h, sorry for taking so long. The problem with groups is that the gateway does not inform us about changes. We have a bit more control over virtual groups.
The additional device types (plugs and blinds) will be available in v2.5.0 (should be on npm in a few minutes). Let me know if that works for you (I don't have anything but bulbs to test).

Thanks for the answer. Unfortunately I can only test the plugs, because I don't have any blinds either. But I will test the plugs in the virtual groups during the public holidays and I will give you feedback at least for these.
So, Thanks for that in advanced and wish you Merry Christmas
Red

Merry Christmas to you too!

I was able to test the new version shortly today. The plugs are now listed in the virtual groups. However, when the virtual group is triggered, the plugs are not acting. The other bulbs in the group behave normally.
Not sure if I can help you with logs etc. since there is nothing listed in the ioBrokers log tab.
Please let me know if I can assist with further tests or data.

Thanks for the test, I forgot some places where I needed to add plug support. Please try v2.5.1 (available in a couple of minutes).

I have some blinds, if you need some testing done I can be of service

What I found out right away is, that setting blinds in the Group does in fact work but the Percentage values are wrong. 0% closes the blinds and 100% opens them which should be exactly the other way round.
This is also true when directly changing the values in the blind objects. I can create a new issue if you want.

Hi all, In the meantime I had time to test the new version. The plugs are now working perfectly in virtual groups. Thanks a lot!

0% closes the blinds and 100% opens them which should be exactly the other way round.
This is also true when directly changing the values in the blind objects. I can create a new issue if you want.

That is on purpose. It is opposite to how it is in the IKEA app, but this way it aligns with other smart home technologies. For example, Alexa doesn't support blinds, so they are usually implemented as lights (where 0% is dark and 100% is full brightness).

Anyways, thanks for the testing guys!


Transferring multiple NFTs in a single QR Code

Is there any way to send multiples NFTs in a single QR Code?

Hey @notdanilo! Solana Pay transaction requests can work for any Solana transaction, so as long as you can do it in a single transaction it'll work.
If you're struggling to write such a transaction then please ask your question on solana.stackexchange.com - that's the best way to get help with things like this. You won't need to narrow your question to Solana Pay there, so should be able to get help from a much wider group of people. Thanks! :)


Different language?

Hi, i've tried your plugin, it helps.
But could there be a selection for different languages in the Search Term dialog?
For exmple, i can choose https://en.wikipedia.org/ or https://zh.wikipedia.org while entering the search term.
Thanks.

Sure, I can do this. I will also add a preferred language setting in the plugin settings.


Upload video issue

Hi,
Thanks for the great work. I encountered an error while trying to upload a video via the frontend canister deployed on my local node.
I've tested with the UI on the development server and it's works great.

I get same question , upload video failed .
Video Size : 32Mb
Video file format : mp4

Okay I think I identified the problem on the local node deployment :
Storing video thumbnail... video.ts:131 Unable to store video thumbnail: TypeError: Cannot convert a BigInt value to a number
Works on the devserver.


fixed a spelling error - changed 'yo' to 'you'

I spotted a spelling error and thought I should fix it.
All I did was change 'yo' to 'you' in the README file.

Indeed, thanks!


How to use the config.json file when launching IOPaint?

I was able to configure it and the file was saved, but it is not being used and I don't know which command-line arguments to use for it.

You can start iopaint using config by running iopaint start --config config.json

Thank you so much for replying so quickly! It worked! 😁


Periodicly most keyboard shortcuts involving Ctrl failing

From time to time Brackets gets into a state where the only keyboard shortcut that works is Ctrl-- (reduce font size). All other commands fail if I use the keyboard shortcut but work if I use the mouse or Alt-[arrow keys] to the menu item.
I think this is similar to https://github.com/adobe/brackets/issues/9588 but maybe not the exact same issue.
I'm on Windows Vista, US keyboard, Brackets 1.2 build 1.2.0-15697.  I'm doing brackets extension hacking so I do open & close windows and the developer tools a lot.
Following the suggestions in Issue 9588 I found that sometimes, after reloading without extensions, the shortcuts are are back to normal again... but if I open a second window using Debug->New Brackets Window shortcuts in that window are broken.  Sometimes if I reload the 2nd window, it will fix the shortcuts, but when I go back to the original window the shortcuts will be broken again.  Sorry I don't have a deterministic recipe here (if I find one I will be back!).
I was unable to follow Peter's suggestion about adding a breakpoint because DocumentCommandHandlers.js is now just one big eval();  Is there a trick here to expand it I don't know?
I do see some warnings similar to the following in the Console.
Deprecated: Do not use $().on/off() on Brackets modules and model objects. Call on()/off() directly on the object without a $() wrapper.
at new jQuery.fn.init (/brackets.js:481:36)
at n (file:///C:/Program%20Files%20(x86)/Brackets/www/thirdparty/thirdparty.min.js:559:405)
Let me know if you need more info!  I get into this state fairly often.

Another quick note, when I get into this state, the gutter in my editors does not render.

I get this issue very often, all keyboard combinations that involve Ctrl just stop working, especially after calling "Debug/New Brackets Window". One of the windows randomly stop reacting. The only workaround I have so far is shutting down all Brackets instances and launching again.

@jedkcanderson @DenisVuyka  If you're using Debug > New Brackets Window, then this is a duplicate of #8135.  I strongly suggest avoiding the New Brackets Window command as it is intended for debugging only, and has many serious problems.
Also, @jedkcanderson: what are you expecting to see in that space in the gutter?  Your screenshot looks normal to me.

@peterflynn Agreed, this looks like a duplicate.  Sorry about that, thought I had searched exhaustively.  From the your comments, and the comments in other bugs, the fix for this sounds involved.  Is that a fair assessment?  I ask because I have a team of developers who are starting to look at Brackets development and we're looking for ways we can help that are actively effecting us.
As for the gutter issue, here's a screenshot when the shortcuts are functioning.

@jedkcanderson The gutter marker you're seeing looks like part of the Brackets Git extension.  Normally I'd suggest filing a bug over there, but I suspect use of the buggy New Window command may be breaking that extension too (due to sharing one copy of Node) -- not the extension's fault, really.
Fixing the keyboard shortcuts in particular (#8135) shouldn't be that hard -- for a dev with native Windows programming experience (since that's where the fix must lie).  Fixing all the New Window command's problems is a much bigger undertaking, though.  If you're interested, I think a good first step would be to review the list of issues on the multiple windows feature card and then start a thread on brackets-dev to discuss further.


Not Compiling with Magic Leap Technical Preview(4.21)

I know I'm asking for too much but this would be cool to get it working on ML technical preview I'm unable to compile the plugin in a ML project ML is using 4.21 … it just pops up to compile it manually is there anything I could try to make it work?

Did you find browser update for 4.21??

BLUI currently will only work on Windows. CEF which this is based on may work on Linux and MacOS in addition, but there is no version of CEF for android or lumin which would preclude any magic leap version.


2.4.2 install fails on macos Mojave with Homebrew binutils

Build log here: https://gist.github.com/duckpuppy/aec6e9ca64ef1594c3e43b37531b806a
I'm getting a weird linker error when trying to build 2.4.2 on Mojave.  I installed 2.4.5 and 2.5.3 with no issues, but I get this error every time with 2.4.2, which unfortunately I need for a project.

I tested with putting /usr/bin ahead of /usr/local/bin so the built-in ar was used over the homebrew one from binutils and the build worked.  Later rubies seem to work with the brew installed ar, but not 2.4.2...

met this issue too, have not idea about it. why does libruby-static.a is  an ar achive?

@duckpuppy Thank you for reporting.
Homebrew's binutils are not supposed to be linked into /usr/local:
==> Caveats
binutils is keg-only, which means it was not symlinked into /usr/local,
because because Apple provides the same tools and binutils is poorly supported on macOS.

If you link it, then unexpected build errors can occur at your own risk.


Add doc(html_root_url) and other doc attrs to each crate

Also update to use https instead of http. This avoids mixed content
degradation on docs.rs.
The doc root URLs are correct as they are, the URL does not include the
crate name itself.

Trying the integer32 playground. Some of the examples don't compile over there, because they are doc-included from one crate to another.
One example is a bigint example (BigInt::from_bytes_be) which produces this playground gist

That's more or less a rustdoc bug and of course it won't compile on any playground.

Main motivation for this  PR is so that Zero is correctly linked in ndarray's docs (without generating & hosting num docs).
After an eventual docs.rs migration, it's relatively easy to pin the doc URLs on a minor version like "0.1" so that cross crate URLs are somewhat versioned.

Hmm, that's interesting.  In an ideal world, those doc examples would adapt their use statements depending on which crate they're shown from, but I have no idea how to accomplish that.

My only complaint about docs.rs is that it doesn't link the crate imports very well.
e.g. this https://docs.rs/num/0.1.36/num/bigint/index.html
vs. this http://rust-num.github.io/num/num/bigint/index.html
But maybe it would look better in general if we used explicit imports there instead of a wildcard.

Wouldn't it link that if the crates in question set up their doc_root_url?

I don't know -- if so, great!

Local test says yes. That will result in docs.rs's crate cross links pointing to rust-num.github.io for now.

By the way, you can control item inclusion in docs using #[doc(inline)] or #[doc(no_inline)] on glob imports.

I just tried this locally, to no effect:
pub mod bigint {
    #[doc(inline)]
    pub use num_bigint::*;
}

Aha. I've only ever used it for crate-internal imports, so I guess it doesn't work the way I assumed here.

@bluss, are these things that every single crate needs to do, or is this somehow specific to num? If it is a general problem, I'm wondering if people shouldn't just submit PRs to docs.rs or whatever to fix the default behaviors?

I suppose from docs.rs's perspective, it only sees the separate crates from crates.io, rather than the crate hierarchy present here in git.  And usually when you do a local cargo doc you get all dependency docs lumped together.

@briansmith All the crates need to do it as it is now. In the new centralized world, you're right that docs.rs could solve this much better. Rustdoc would need an override that tells it that everyone's root url is on docs.rs.

Anyway, the url updates look good.  Thanks!
@homu r+ ff2a350

:zap: Test exempted - status

Thank you


Can't locate on OpenStreetMap

Describe the bug
When i go to https://www.openstreetmap.org/ or https://wego.here.com/ i'm unable to locate myself on the map.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://www.openstreetmap.org/'
Click on 'Show my location'
See error

Expected behavior
Show my location on the map
Screenshots

Environment (please complete the following information):

OS/Platform and version: Windwos 10
ungoogled-chromium version: 89.0.4389.114

This is a duplicate of #1551

Closing this issue in favour of #1551


Feature request: service to force an image snapshot

I'd like to be able to create automations in HA for more complex timing logic or for intervals which may not survive a restart (e.g. daily). If there were a service exposed to call fetch_image, then I could do it with any external timing or event-based logic desirable. It might make sense in this case, to accept fetch_interval: 0 to disable built-in timing, but I can also just call the pause service on HA boot as a workaround.
What do you think about this idea?

I'm not sure what to think of the idea. It sounds very specific for your needs but not sure for what else. By the sounds of it you have a workaround. Contributions are welcome to make enhancements.


Bring action bar to bottom

Is your feature request related to a problem? Please describe.
Previously it was nice and easy to use K9 Mail one handed on a "usual sized" (i.e. big) Phone. With the "new" UI this does not work anymore.
One big drawback of the new UI is that in message view the action buttons are above the message at the top of the screen. So you can not easily reach them with your  finders that are at the bottom of the screen.
Describe the solution you'd like
Bring the buttons (action bar?) and controls in message view back to the bottom. At least optionally. So I can control the with the fingers that are at the bottom, holding the phone!
Describe alternatives you've considered
There are NONE. Either be smart and desing for a phone in one handed mode or don't make phone apps at all. In desktop it is ok to have controls at the top. But not on a phone.

I am posting to endorse this request/suggestion. I wouldn't normally do this but I fear that part of the reason for some of the recent changes having been made is because users haven't spoken clearly about things that they liked and hence there's been little reason not to introduce change, even if apparently unsolicited.
Incidentally, I wouldn't regard moving the action bar to the bottom as an 'enhancement' as such, more that moving the action bar to the top (away from your thumb and device hardware controls) in the first place as a human-computer interaction bug/issue, if you see what I mean.

because users haven't spoken clearly about things that they liked

People will certainly complain if they don't like things. If they are generally happy they don't tend to react much. That isn't a reason to change things. I always thought the old interface was extremely well thought out. I had tried other clients and tried to make them work the same way, but they were always a fail. K-9 was by far and away the best. Was.
I cannot get on with the new interface - it is taking far too long to do anything productive with the old, well thought out, minimal and informative intro screen now missing and replaced by a sliding side bar and jumbled info which is not as fast, convenient or effective. And the top buttons are completely unusable.
The colours are hideously bright. No check boxes for fast select. I could go on. Sorry, and and I know there is a lot of hard work there, but I can't work with it.
Even worse is you cannot easily restore the old version due to this Issue so I am going to have to recreate several accounts with all their settings now which will take me a very long time.
https://github.com/k9mail/k-9/issues/5000
Very annoying and frustrating.
All that glisters is not gold.

As a data point, Firefox for Android reworked the UI last year to have the address bar at the bottom for precisely the usability issue. To me the new UI is nicer, but the usability has dropped significantly.
Even with my big hands, it is now really awkward to use K9-Mail to go through my message list or to access the menus.
Please can this be marked as a bug/regression not an enhancement.

I hate to post +1 comments, but here we go... This is so annoying, that I just do that... Please move it to the bottom.

Like everyone else the action bar at the top is impossible to reach in one handed use.
Is there some sort of shortcut alternate to trigger delete email when looking at an email? That's the main use case I use it for and would be an acceptable work around for me.

I can only agree with the previous comments.
First thing i though with the new version: Cool a new version
Second thing I though: Why the hell did they move the action bar to the top?!
And what about the quick actions you could trigger by swiping and so on? Could not find them either!

This has made it IMPOSSIBLE for those with disabilities to use the app, or require you to set the phone down to be able to use the action bar at the top of the screen. Either move it back to the bottom, or allow users to elect if they want it at the top of bottom.

A nice fresh interface.
But the userability on the app has dropped significantly by moving the actions to the top.  You now need two hands on a large size phone.
I think most would prioritise userability over a sexy/slick interface

If you want to express you are affected by this issue and you want it fixed, it is usually enough to add a :+1: reaction to the issue description.
Just describing how much you like it in a comment adds no real value and only wastes the developers time (which need to read new comments) and bothers all subscribers with no updates on the issue.
If you want this to be fixed soon, please stop adding this sort of comments, just add a :+1: reaction to the issue.
Thanks!

I rolled back to 5600 because of this issue. Am looking forward to coming back when this issue is fixed.

Hi,
also I would like to add that at least for me, moving stuff to a side bar (in addition to the vastly increased number of taps required to do simple things as to get an overview about multiple accounts), has drastically reduced the ability to use the app "one handed"

+1
I've been holding off on criticizing the new interface to try and get to know it first.... But deleting or moving stuff is now quite painful. It shouldn't take 2 hands to achieve.

This issue is important to me because my thumb cannot reach the top button bar to tap the buttons.

In general I really like the new version, but this problem makes it nearly impossible to use K-9 mail with just a single hand on a "normal" (6") phone -- which is unfortunate because that worked fine before. So it would be great to have the option to move the menu bar down to the bottom of the screen. :)

Can only agree... K9 is no longer usable for me with one hand. This is a serious step backwards. Please at least put an option in to relocate the bar to the bottom.

Googled for a way to get the nav bar back to bottom. Stranded here.. please add the option to put it back down.

As a data point, Firefox for Android reworked the UI last year to have the address bar at the bottom for precisely the usability issue. To me the new UI is nicer, but the usability has dropped significantly.
Even with my big hands, it is now really awkward to use K9-Mail to go through my message list or to access the menus.
Please can this be marked as a bug/regression not an enhancement.

I'd see it as an enhancement and not a regression. However, I very much like when the main navigation items are at the bottom of the phone. Other data points are F-Droid and Aurora Store. Especially Aurora Store as they claim to be "Built upon latest Material Design guidelines" (from their GitLab readme).

In case someone wants to join the bug bounty: https://www.bountysource.com/issues/100118876-bring-action-bar-to-bottom :-)
https://github.com/k9mail/k-9/issues/5657 should be an easy addition after this ticket here would be implemented, if possible.

Does anyone have any suggestions on how the UI should look like?

There's some things to consider listed in the Material Design guidelines: https://material.io/components/app-bars-bottom

Does anyone have any suggestions on how the UI should look like?

Bring the complete upper bar to the bottom.

Here’s a screen shot – version 5.6  navigation bar on the bottom (who could possibly want it at the top.  I will abandon K9 if 5.6 ceases working and there is no task bar on the bottom working.
I’ve been using version 5.6 for years now – most recently on a Verizon Galaxy s22 ultra, before that on a Note9, before that on a S8+.
It works like a charm, not a single problem. The Ultra is now at Android 12.
Author: ACT FROM CHOICE
Read the Kirkus and other reviews   http://www.actfromchoice.com/sample-reviews-and-press here
Find it on Amazon and other booksellers
Please follow me on Twitter: @actfromchoice
And join me on LinkedIn

Robert Goldmann
Clarity & Performance Coaching
Executives, Professionals, Business owners
www.ClarityAndPerformance.com http://www.clarityandperformance.com/
www.ActFromChoice.com http://www.actfromchoice.com/
510.495.4444

From: DomoticaUser @.>
Sent: Wednesday, July 20, 2022 12:01 PM
To: thundernest/k-9 @.>
Cc: robtgmann @.>; Comment @.>
Subject: Re: [thundernest/k-9] Bring action bar to bottom (#5447)
Does anyone have any suggestions on how the UI should look like?
Bring the complete upper bar to the bottom.
—
Reply to this email directly, view it on GitHub https://github.com/thundernest/k-9/issues/5447#issuecomment-1190644780 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AVBK2XJHE6WPBDRB45TRAH3VVBEH3ANCNFSM5A7QZH6Q .
You are receiving this because you commented.  https://github.com/notifications/beacon/AVBK2XPLTIIV43H76GB2ZG3VVBEH3A5CNFSM5A7QZH62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOI334YLA.gif Message ID: @.*** @.***> >

Here’s a screen shot – version 5.6 navigation bar on the bottom (who could possibly want it at the top. I will abandon K9 if 5.6 ceases working and there is no task bar on the bottom working. I’ve been using version 5.6 for years now – most recently on a Verizon Galaxy s22 ultra, before that on a Note9, before that on a S8+. It works like a charm, not a single problem. The Ultra is now at Android 12.

Hi, @robtgmann  I am not able to see the screenshot could you please check?

Bringing the action bar to the bottom would look like this. Is this design ok to proceed further?

Is there any reason not to bring the back button down with it and free up the whole top?

I agree that the back button would be cool to have, but also the "answer" button, as most of the time I want to answer or leave the current message… If its because of a lack of space, I'd prefer to have the answer button than the search button.

Well I thought exactly the same thing: reply-button. This could maybe be realized via a floating action button (FAB). Either context sensitive:

"New message" in inbox/folder view
"Reply" in message view
And/or via an expandable button in case of reply, reply all, forward

Am 21. Juli 2022 14:48:45 MESZ schrieb Tobias Bora @.***>:

I agree that the back button would be cool to have, but also the "answer" button, as most of the time I want to answer or leave the current message… If its because of a lack of space, I'd prefer to have the answer button than the search button.
-- >
Reply to this email directly or view it on GitHub:
https://github.com/thundernest/k-9/issues/5447#issuecomment-1191443294
You are receiving this because you commented.
Message ID: @.***>

The screen shot was an attachment last time.  To reply, there’s an icon in the task bar leading to a choice of reply all, forward, forward as attachment, or share.   When sending a new message or replying, the send button is above the top along with other options.  If you want more on those, let me know.
Author: ACT FROM CHOICE
Read the Kirkus and other reviews   http://www.actfromchoice.com/sample-reviews-and-press here
Find it on Amazon and other booksellers
Please follow me on Twitter: @actfromchoice
And join me on LinkedIn

Robert Goldmann
Clarity & Performance Coaching
Executives, Professionals, Business owners
www.ClarityAndPerformance.com http://www.clarityandperformance.com/
www.ActFromChoice.com http://www.actfromchoice.com/
510.495.4444

From: Robert Goldmann @.>
Sent: Wednesday, July 20, 2022 12:24 PM
To: 'thundernest/k-9' @.>
Subject: RE: [thundernest/k-9] Bring action bar to bottom (#5447)
Here’s a screen shot – version 5.6  navigation bar on the bottom (who could possibly want it at the top.  I will abandon K9 if 5.6 ceases working and there is no task bar on the bottom working.
I’ve been using version 5.6 for years now – most recently on a Verizon Galaxy s22 ultra, before that on a Note9, before that on a S8+.
It works like a charm, not a single problem. The Ultra is now at Android 12.
Author: ACT FROM CHOICE
Read the Kirkus and other reviews   http://www.actfromchoice.com/sample-reviews-and-press here
Find it on Amazon and other booksellers
Please follow me on Twitter: @actfromchoice
And join me on LinkedIn

Robert Goldmann
Clarity & Performance Coaching
Executives, Professionals, Business owners
www.ClarityAndPerformance.com http://www.clarityandperformance.com/
www.ActFromChoice.com http://www.actfromchoice.com/
510.495.4444

From: DomoticaUser @.*** @.> >
Sent: Wednesday, July 20, 2022 12:01 PM
To: thundernest/k-9 @. @.> >
Cc: robtgmann @. @.> >; Comment @. @.***> >
Subject: Re: [thundernest/k-9] Bring action bar to bottom (#5447)
Does anyone have any suggestions on how the UI should look like?
Bring the complete upper bar to the bottom.
—
Reply to this email directly, view it on GitHub https://github.com/thundernest/k-9/issues/5447#issuecomment-1190644780 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AVBK2XJHE6WPBDRB45TRAH3VVBEH3ANCNFSM5A7QZH6Q .
You are receiving this because you commented.  https://github.com/notifications/beacon/AVBK2XPLTIIV43H76GB2ZG3VVBEH3A5CNFSM5A7QZH62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOI334YLA.gif Message ID: @.*** @.***> >

I would be happy with just the existing bar, moved to the bottom. If there was any customization, then why not just make it such that you can pick if you want the bar on the top or bottom, and which buttons and shown on the bar and whichever ones are not picked to show on the main bar the rest overflow into the three vertical dots. Move the back arrow along with the rest of the action bar. Basically, keep it all as it is if that makes things easy, but move it from the top of the screen, to the bottom of the screen. It's not a difficult to define ask. The existing design is impossible to use one handed, which makes things VERY difficult for those who have handicaps or have dexterity problems with one of the arms or hands!

I developed bottom bar like Samsung Mail. I think it has nice usability and is good-looking. I can make a pull request for that.

@rezazarchi If you succeed pushing your change, feel free to claim the bounty later: https://app.bountysource.com/issues/100118876-bring-action-bar-to-bottom

can m

What do you think? @cketti

We don't want to add a custom toolbar that looks and feels nothing like a platform component. Again, this is the design document that should be used for orientation: https://m2.material.io/components/app-bars-bottom
Structurally, https://github.com/thundernest/k-9/issues/5447#issuecomment-1191211633 looks close. But we probably don't need a toolbar at the top just to host the back button. The color of the toolbar at the bottom should match the current toolbar. Also, the actions in the toolbar should only contain message view actions.
This example from the material design site looks useful:

We don't want to add a custom toolbar that looks and feels nothing like a platform component. Again, this is the design document that should be used for orientation: https://m2.material.io/components/app-bars-bottom
Structurally, #5447 (comment) looks close. But we probably don't need a toolbar at the top just to host the back button. The color of the toolbar at the bottom should match the current toolbar. Also, the actions in the toolbar should only contain message view actions.
This example from the material design site looks useful:

I understand that. but my goal wasn't to bring the toolbar to bottom. I was looking for implementing useful action buttons on bottom side of the fragment for better usability in long aspect ratio devices.

Agree that a material design would be best, and I prefer the last two designs (whats the difference?) A LOT!


linear element's hitbox interweaved with holes

not a recent regression

https://excalidraw.com/#json=seAp8lS2iGYAV2FtuLFT-,PA6KsAwSEYmLiZ8Y-vF1yg (perma)

Looking into it turns out that isHittingElementNotConsideringBoundingBox is returning false due to which this is happening


Update create-zone-apex.mdx

Summary

This PR updates the documentation for creating DNS records on the zone apex. It also adds a personalized developer section, highlighting key projects related to roleplay servers.
Screenshots (optional)

Documentation Checklist

[ ] The documentation style guide has been adhered to.
[ ] If a larger change - such as adding a new page - an issue has been opened in relation to any incorrect or out-of-date information that this PR fixes.
[ ] Files that have changed name or location have been allocated redirects.

Additional Information

This update aims to improve the visual appeal of the DNS setup guide and introduce a personalized developer section that showcases ongoing roleplay server projects. The changes are designed to provide a more engaging user experience and ensure that the documentation remains up-to-date with the latest best practices.

Hi @iboss21 👋 Thank you for the suggestions. We only take care of Cloudflare products documentation in this repo.


Hero card overflow logic loses buttons when overflowing onto multiple cards in Node SDK 2.0.2

User the following dialog:
bot.dialog('/', function (session) {
    var msg = new builder.Message(session)
        .attachments([
            new builder.HeroCard(session)
                .title("Test Card")
                .subtitle("What happens when there's too much button love?")
                .text("Select an option\nYou know you want to")
                .buttons([
                    builder.CardAction.imBack(session, "yes", "Yes"),
                    builder.CardAction.imBack(session, "no", "No"),
                    builder.CardAction.imBack(session, "maybe", "Maybe"),
                    builder.CardAction.imBack(session, "other", "Other"),
                    builder.CardAction.imBack(session, "cancel", "Cancel"),
                    builder.CardAction.imBack(session, "one", "One"),
                    builder.CardAction.imBack(session, "two", "Two"),
                ])
                .images([
                    builder.CardImage.create(session, "https://avatars0.githubusercontent.com/u/621491?v=3&s=460"),
                ])
        ]);
   session.send(msg);
});

This will result in the card spilling over into a carousel of cards, except some of the buttons will be lost. See the screen shot of the above code where "other", "cancel" and "one" buttons have gone missing.

This same behaviour is seen in all Skype clients.

this a bug, thanks for reporting.

Steve, this works with my sample with 6 buttons, it looks like we are chunking at 6 but it's only rendering 3?


chore(deps): update python to >=3.9,<3.14

This PR contains the following updates:

Package
Type
Update
Change

python
dependencies
minor
>=3.9,<3.13 -> >=3.9,<3.14

Release Notes

containerbase/python-prebuild (python)
v3.13.0
Compare Source
Bug Fixes

deps: update dependency python to v3.13.0

Configuration
📅 Schedule: Branch creation - "before 4am every weekday also after 12pm and before 1pm every weekday" in timezone America/Toronto, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

 You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


Add dynaconf_merge fucntionality for dict and list settings.

If your settings has existing variables of types list ot dict and you want to merge instead of override then
the dynaconf_merge and dynaconf_merge_unique stanzas can mark that variable as a candidate for merging.
For dict value:
Your main settings file (e.g settings.toml) has an existing DATABASE dict setting on [default] env.
Now you want to contribute to the same DATABASE key by addind new keys, so you can use dynaconf_merge at the end of your dict:
In specific [envs]
[default]
database = {host="server.com", user="default"}

[development]
database = {user="dev_user", dynaconf_merge=true}

[production]
database = {user="prod_user", dynaconf_merge=true}

In an environment variable:
export DYNACONF_DATABASE='{password=1234, dynaconf_merge=true}'

Or in an additional file (e.g settings.yaml, .secrets.yaml, etc):
default:
  database:
    password: 1234
    dynaconf_merge: true

The dynaconf_merge token will mark that object to be merged with existing values (of course dynaconf_merge key will not be added to the final settings it is jsut a mark)
The end result will be on [development] env:
settings.DATABASE == {'host': 'server.com', 'user': 'dev_user', 'password': 1234}

The same can be applied to lists:
settings.toml
[default]
plugins = ["core"]

[development]
plugins = ["debug_toolbar", "dynaconf_merge"]

And in environment variable
export DYNACONF_PLUGINS='["ci_plugin", "dynaconf_merge"]'

Then the end result on [development] is:
settings.PLUGINS == ["ci_plugin", "debug_toolbar", "core"]

The dynaconf_merge_unique is the token for when you want to avoid duplications in a list.
Example:
[default]
scripts = ['install.sh', 'deploy.sh']

[development]
scripts = ['dev.sh', 'test.sh', 'deploy.sh', 'dynaconf_merge_unique']

export DYNACONF_SCRIPTS='["deploy.sh", "run.sh", "dynaconf_merge_unique"]'

The end result for [development] will be:
settings.SCRIPTS == ['install.sh', 'dev.sh', 'test.sh', 'deploy.sh', 'run.sh']

Note that deploy.sh is set 3 times but it is not repeated in the final settings.

The dynaconf_merge functionality works only for the first level keys, it will not merge subdicts or nested lists (yet).

@bmbouter @dkliban @psav @rsnyman
Now I got a better implementation, will help if you can give your inputs.

Looks good to me.

i just got back from PTO, so i'll chime in even after some delay
i have been observing behaviours and integrations, and to me it seems that stuff the very different needs in config file loading/merging for django vs other projects do look to me like something that the "strategy pattern" can solve nicely
i wonder if it would make sense to create some kind of "merge strategy" one can pass to dynaconf to sort out how configfiles with keys/names and env vars with dunder names map into the actual config, and what a "merge" should do when


get gallery from json list?

is it possible?

Yes. Build your html elements from your json and use as per all the examples.


JDBC engine using the overlay conf as session conf

:mag: Description
Issue References 🔗

Describe Your Solution 🔧
Like #6147, JDBC engine should overwriting the engine conf with the passed conf consider as the full session conf.
Types of changes :bookmark:

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests

Checklist 📝

[ ] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 58.43%. Comparing base (c1239f2) to head (9ca8b48).

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #6182      +/-   ##
============================================
- Coverage     58.46%   58.43%   -0.03%
  Complexity       24       24
============================================
  Files           649      649
  Lines         39312    39312
  Branches       5415     5415
============================================
- Hits          22982    22973       -9
- Misses        13859    13865       +6
- Partials       2471     2474       +3

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

Merged to master/1.9.1/1.8.2


Error message when viewing userpage not logged in

Is it because the message should display a more descriptive message or not appear at all when the user isn't authorized to follow another user (Because they aren't logged in)?

I think it catches an exception which we do not need to show to end user

Great i'll fix that


Adding Genomics coverage checking

Description
Issue: STEAM-846
This PR adds coverage checking for Genomics resources
Important Changes
Coverage checking has been added for the genomics section of the mCODE diagram in genomicsCoverage.js
Tests added for Genomics coverage checking in genomicsCoverage.test.js and accompanying genomicsBundle.json test bundle created.
Genomics IDs added to coverageProfileIds.js and coverageSectionIds.js
Testing Recommendations

Ensure that new tests cover sufficient cases and pass
Check that appropriate fields are checked for
Make sure that each field has a proper true/false value when it is covered or not

Checklists
Submitter:

[x] This PR describes why these changes were made.
[x] This PR is into the correct branch.
[x] This PR includes the correct GH issue reference.
[x] Comment added to the relevant GH issue(s) with a link to this PR
[x] Code diff has been reviewed (it does not contain: additional white space, not applicable code changes, debug statements, etc.)

@ACCT1 :

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] You have tried to break the code
[ ] Tested all recommendations listed in the "Testing Recommendations" section. The application behaves as expected with this PR.

DP1 - Could we add the appropriate Genomics bundle entries to the fullBundle.json file? Or did you intentionally leave that out during this PR?

DP1 - Could we add the appropriate Genomics bundle entries to the fullBundle.json file? Or did you intentionally leave that out during this PR?

I don't think we've updated anything in fullBundle.json in the last couple PRs. It was sort of just a placeholder to begin with. What do we want to do with it? It's currently only used as the input for the visualization, but ultimately user's will input their own bundles right?

Question: When comparing the bundle here to the example JSON's on the mCODE IG, we appear to have added a number of empty code.valueCodeableConcept.coding arrays. Could we speak to that addition a bit? I could see the benefit of having those fields in our test fixtures, but we probably don't want to add those empty values to the full bundle. Wanted to see what your thoughts were.

On all the slices? I could get get rid of the empty coding arrays there was no particular reason, the coverage checker only checks for the valueCodeableConcept. Because the examples on the IG are a lot of the fields we check for, I had to make a bunch of fields on my own for testing purposes and didn't have any actual example values to put in the valueCodeableConcept

Question: When comparing the bundle here to the example JSON's on the mCODE IG, we appear to have added a number of empty code.valueCodeableConcept.coding arrays. Could we speak to that addition a bit? I could see the benefit of having those fields in our test fixtures, but we probably don't want to add those empty values to the full bundle. Wanted to see what your thoughts were.

On all the slices? I could get get rid of the empty coding arrays. There was no particular reason, the coverage checker only checks for the valueCodeableConcept. Since the examples on the IG are missing a lot of the fields we check for, I had to make a bunch of fields on my own for testing purposes and didn't have any actual example values to put in the valueCodeableConcept

Yes on the slices. Specifically: We don't appear to have augmented the JSON examples in the past before. Did we want to start augmenting those example files so we can test full coverage in our test files, or was this just done for local development purposes? If it's the former, let's discuss; it's the latter (read: it sounds like the latter), then let's remove those additional, empty fields.

Question: When comparing the bundle here to the example JSON's on the mCODE IG, we appear to have added a number of empty code.valueCodeableConcept.coding arrays. Could we speak to that addition a bit? I could see the benefit of having those fields in our test fixtures, but we probably don't want to add those empty values to the full bundle. Wanted to see what your thoughts were.

On all the slices? I could get get rid of the empty coding arrays. There was no particular reason, the coverage checker only checks for the valueCodeableConcept. Since the examples on the IG are missing a lot of the fields we check for, I had to make a bunch of fields on my own for testing purposes and didn't have any actual example values to put in the valueCodeableConcept

After double checking, the full bundle already contained all jenny-m data available on the IG, including Genomics data elements. DP1 is all set.

Other than my question about the contrived, empty values this looks good to me.


Implement remove repo auto import button

In the management area for repo auto imports, implement the remove button (trash icon):

This should also include a confirmation modal with warning text that states:
All repositories added to MergeStat from this repo auto import (and their associated data) will be removed.

Closing since no longer relevant


Element API endpoints closes ageddesi/Mocked-API#107

Hey there, happy hacktoberfest!
Contribution guidelines asks for tests but endpoint and test issues are separate, i figured it was ok? Still starting with typescript. Tried some edge cases in insomnia though!

Hey @VLN37
We have updated our codebase to now have tests and swagger is no longer needed to be updated, instead we do OpenAPI comments directly in the API source file.
I have also pointed the merge target to our v0.13.0 which has the latest code on it. If you are able to resolve the conflict and if you have time update with the tests and OpenAPI Comments that would be ace 👍

I'll see what i can do.
Tried to link to the issue but it didn't work, any ideas on that?

Ahhh I follow what you mean now. If you want to do the tests I can assign that ticket to you as well and I will close them both at the same time for this PR.

0.13.0 already has commits for the issue i was pushing for... i guess it's whatever now...
Did learn some while at it, good luck fellow.

Ah sorry @VLN37 there is a lot going on the last 2 days, Thanks for the help. There is always some more smaller tasks if you have time.


[ci](cloud ut) trigger new teamcity pipeline cloud ut

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run cloudut

run buildall


memory usage inaccurate

the memory usage shown in activity monitor is higher than pfetch-rs.

Related to https://github.com/Macchina-CLI/libmacchina/issues/166


[core][branch] Add branches in tags table

Purpose

Linked issue: close #2753
Add branches column in tags table
Tests
Added test in TagsTableTest to get branches
API and Format
no
Documentation
yes

This PR will wait for #2748

+1