[Question]: Why is the entire parsed md file divided into one chunk?

Describe your problem

The default settings are used. The chunk length of the md file is obviously longer than the setting, which should be due to the absence of a delimiter. The delimiter includes \n but cannot recognize the line break in md.

Platform: Windows WSL
Version: 1.14.1-dev

Carriage Return / Line Feed delimiter issue?

It is supposed to be like that, but I am not sure why it fails to recognize the line breaks in the md file. I use ragflow/readme.md as the document.

Could you please check and report back here, what kind of BOM (Byte Order Mark) the file has? This might be an en-/decoding issue.

Copy the content from the md file directly into a docx file, which can work properly, but it is best to be able to parse the md file directly.

Maybe it's a HTML parsing issue?! Haven't reproduced yet, Def, worth a look. Thanks for reporting.

What about turning down the chunk token number?
Or, set the delimitor: ##\n\r

@KevinHuSh Changing the delimiter or down the chunk token number for splitting does not seem to have an effect on md files; it still combines a large number of md documents into one single block.

I tried reinstalling the latest version of Nightly, but I am still getting the same result.

Do you get more than 1 chunk, if you use other templates (like HTML)? Maybe the chunk method decided to use just one chunk?

Using the QA mode can chunk normaly, it seems there is a bug in the general mode regarding MD chunking.
@Snify89

Additionaly, here I convert the readme.md to docx, and then chunk using general method. It work properly.


Feature: Allow provision of post-setup script to be run before bootstrap

Added in 3ffc47e23b5e5ee7b180f180d6ea1b53ea6aba72 (0.47.0)


Add API Guides

(Spawn off of meta Issue: https://github.com/opensearch-project/opensearch-clients/issues/56)
To help drive adoption of OpenSearch, and improve user's experience, we're working on adding more documentation for all clients. One of the strategies mentioned in said issue is writing a collection of articles serving as a User's Guide for each client. This issue will serve as a hub for all issues related to this topic.
Each Guide/Article will be a good-first-issue for new contributors to work on. There's already a Ruby version of each article that the articles on this repo should be based upon. Most of the time, we only need to replace the Ruby code blocks with the client code of this repo. Please refer to the meta issue for more details.

[ ] https://github.com/opensearch-project/opensearch-net/issues/185
[ ] https://github.com/opensearch-project/opensearch-net/issues/186
[ ] https://github.com/opensearch-project/opensearch-net/issues/187
[ ] https://github.com/opensearch-project/opensearch-net/issues/188
[ ] https://github.com/opensearch-project/opensearch-net/issues/189
[x] https://github.com/opensearch-project/opensearch-net/issues/190

Hi Thomas, when you have a moment I'd like to have this issue assigned to me. Thanks

@Djcarrillo6 Maybe comment on the issue for the specific guide you'd like to work on first, so that others can pick up other guides too if they want?

For sure @Xtansia , I'd like to work on #187 first..

For sure @Xtansia , I'd like to work on #187 first..

@Djcarrillo6 sorry, you need to comment on #187 itself, due to the way Github works, I can't assign it to you unless you "participate" on that actual issue


Integrate with FastFold

FastFold by @Konfekt leverages the same events as vim-stay:

Regarding compatability with FastFold, vim-stay must be loaded after FastFold so that mkview in vim-stay's BufWinLeave and BufWinEnter autocmds saves the syntax or expression foldmethod and not the manual foldmethod FastFold artificially imposes.

The BufLeave autocmd is curious as it seems accounted for by the BufWinLeave autocmd ?! If vim-stay only used that autocmd, than the timing would always be wrong, because the BufLeave autocmd is invoked too early. However, as things stand, the erroneous (that is, incompatible to FastFold) view file created by the BufLeave autocmd is overriden by the correct one from the BufWinLeave autocmd.

The problem is that when quitting a window, BufWinLeave sometimes fires after the window has been destroyed (the window number returned by getbufwinnr(bufnr) is -1 – see :h BufWinLeave, which warns of this, albeit a bit cryptically), which makes view creation impossible (:mkview needs a valid window). BufLeave OTOH always fires in a valid window, so both events are needed to catch “buffer leaving a view” situations. This also means vim-stay will at times save the spurious manual folds set by FastFold.

I’m not sure I can fully solve that on my end. One thing I can think of which could work, provided me and @Konfekt both change a few things:

refactor vim-stay to trigger view creation on a User autocommand (say BufViewLeave), with the current autocommands triggering this event instead of saving the view directly – that would be my part
have FastFold do silent doautocmd User BufViewLeave after it restores the fold method on BufWinLeave – that would be @Konfekt’s end.

Pros: load order of the plug-ins doesn’t matter anymore and all corner cases should be covered. Cons: views will be saved twice when vim-stay’s BufWinLeavehandler is triggered after FastFold’s.
I’m totally open to better ideas than that, but that’s what I can come up with right now.

Ok, sounds like a fine suggestion. As the only con is what's already status quo. So things can only get better.
So pasting silent doautocmd User BufViewLeave after s:Leave() | at
https://github.com/Konfekt/FastFold/blob/master/plugin/fastfold.vim#L214 and there we go?
Feel free to provide a pull request if it's more intricate than that, most easily discussed that way.

I’ve got something slightly more intricate in the works. Branch should be ready in half an hour at most, will let you know.

OK, I’ve rustled up something like an extensible, generic extension API for vim-stay, with FastFold integration as the first (and right now only) implementation. Care to take a look at (and maybe play around with) the fastfold-integration branch? No docs yet, I’ll add that if the scheme pans out.

Ok, looks fine. And as if no change on my end is any longer needed?
The only worry is that it depends on FastFold variables actually hidden to the user, so hopefully they will never change.
Perhaps I should document them as a reminder.

If you can see your way to APIfying your variables (i..e documenting them and guaranteeing they will be present, named and functioning like they are currently, barring major version changes in FastFold), yup, nothing to do on your end. Or you could pull in autoload/stay/integrate/fastfold.vim (with that exact directory path) into FastFold, to the same effect – the extension system works wherever in rtp the integration script is stored. The latter option would allow you to change the inner workings of FastFold without worrying about breaking compatibility with a 3rd party one, but it will add 1 Kb of code to your plug-in; if that is your choice, I can send you a PR.
Either way is fine with me, just let me know :).

Alright, as FastFold is a dead-simple plugin, I opted for option 1: You find
https://github.com/Konfekt/FastFold/commit/15f55bcf50d24c85a6f79440e29d91f4c9ae5159
and its improvement
https://github.com/Konfekt/FastFold/commit/38c66f476ca878f71e77519ca7744e9774d0422b
that document the w:lastfdm variable. The b:lastfdm variable is a crutch for guessing w:lastfdm.

Cool, I’ll merge the branch tomorrow and make FastFold support official. One last question: should I ignore b:lastfdm and only query the window-local variable?

Yeah, I saw that line and therefore commented on it. Can be safely ignored: By the time FastFold changes the foldmethod, always the window local version is used. The b:lastfdm stores the w:lastfdm of the same buffer that may be displayed in another window or tab; it is only one of many sources for guessing w:lastfdm.

I have a problem with this not working when I have multiple buffers/windows open.  If I put some diagnostics in the save_pre and save_post functions I can see that when I run 'zuz' in FastFold the pre and post functions are being called twice on each file (I assume due to the windo Enter and Leave).  I'm not sure if this is correct behaviour just on the 'zuz', but the problem appears to be in the post condition which only sets the fdm to manual if it differs from the FastFold saved value.
I think this behaviour should instead be to set fdm to manual if the FastFold saved value (w:lastfdm) exists.  This change has fixed it for me, but I don't understand the autocommand interactions well enough to know if there are side effects.

Hmm, that’s odd, as the two BufStaySave\* events are only separated by the session save command. Could you run the following for me, please?
set verbosefile=/somewhere/you/will/find/it/log.txt
augroup staydebug
  autocmd user BufStaySavePre,BufStaySavePost verbose echo reltimestr(reltime()) expand('<amatch>') expand('<abuf>') bufnr('%') winnr() &fdm get(b:, 'lastfdm', '')
augroup END

and try to trigger the error you described? Once you have done so succesfully, do
set verbosefile=
autocmd! staydebug
augroup! staydebug

or restart your Vim session and paste the contents of the above log.txt file here (unless it is humungous, then I’d prefer you upload it somewhere and just link to it in a comment :))

Hmm..., perhaps the issue is that FastFold only sets fdm=manual if the fdm was syntax or expr. Other foldmethods are computationally little demanding, and so there is no need to artifically impose fdm=manual.

I won't be able to run the debug for another 12 hours, but I think the issue is that the 'zuz' command cycles through all the windows but only changes the fdm on those that match the current buffer (this behaviour is correct).  By contrast, the save_pre always restores the original mode before saving (which is also correct) but because FoldFast is ignoring some windows the fdm is not restored by FoldFast and so is not different in the save_post and so is not restored by that either.
I believe the save_post behaviour as it stands is either redundant (when FoldFast restores the fdm itself) or non functional (when FoldFast does not restore the fdm) depending on the circumstances.

Hmm, that seems unlikely. to me: as I said, the only thing happening between the BufStaySavePre and BufStaySavePost events is the view session creation via :mkview (that is literally the whole code that is there), and barring exceptions aborting execution, the events will always fire in tandem.
@Parakleta I’m afraid I really do need that debug output  – take your time, 12 hours hence for you means I won’t look at it before next morning my time (I’m on GMT+1) :). Also, could you specify what exactly “is not working” ?

What @Parakleta says seems to nail it, see https://github.com/kopischke/vim-stay/blob/master/autoload/stay/integrate/fastfold.vim#L15 and https://github.com/kopischke/vim-stay/blob/master/autoload/stay/integrate/fastfold.vim#L23.
Supposedly that BufSave command is doing harm because FastFold cycles through all windows of the current buffer, and also only sets the foldmethod to manual if they were syntax or expr before.
Best solution: Store l:fdmlocal in w:fdmlocal https://github.com/kopischke/vim-stay/blob/master/autoload/stay/integrate/fastfold.vim#L15  and replace 'manual' in  https://github.com/kopischke/vim-stay/blob/master/autoload/stay/integrate/fastfold.vim#L23 by w:fdmlocal.

Hah, I think the issue is much simpler: I stupidly set the condition for restoring FastFold’s enforced manual fold method to always evaluate to false when the folds have been reset to w:lastfdm in BufStaySavePre. Replacing Lines 21 and 22 of stay#integrate#fastfold#save_post() by this
if &foldmethod isnot# 'manual' && exists('w:lastfdm')

should fix the issue. @Parakleta give it a try and report back, please?

That works for me.  It's basically the same as what I figured out.  Should the &foldmethod be &l:foldmethod instead?
I still have an issue with FastFold not setting the mode to manual when first loading a buffer but I think this is unrelated, so I'll keep digging for that.

It's basically the same as what I figured out.

It’s exactly what you figured out originally, actually :). The whole ensuing thread about duplicated events, cycling windows  and FastFold restoring stuff (some of which is way off base, and none of which is actually relevant, except incidentally) just obfuscated that for me. Sorry for being slow, and for introducing the bug, of course – will fix in next release.

Should the &foldmethod be &l:foldmethod instead?

&setting gets the actual setting; local if set locally, global if not, while &l:setting gets you nothing when the setting is global, so that is the correct test here (bit of a moot point in our case, really, as foldmethod is window-local, but we cover possible future shifts in its semantics that way).

I wonder if there is a way to make it not order-dependent?

The integration module’s point is to do exactly that: ensure vim-stay and FastFold play nice with each other, independently of load order. I think we (@Konfekt and I) might have overlooked the load scenario when we talked about compatibility. @Parakleta try what happens when you change this line of the patched integration module to:
autocmd User BufStayLoadPost,BufStaySavePost unsilent call stay#integrate#fastfold#save_post()

That change has the effect of resetting the fdm to the default setting rather than the view setting.  FastFold's lastfdm is set to the default value that prevailed before the view was loaded (by its BufWinEnter firing before loadview) and then save_post is restoring that value rather than the post-view value.
I think you could doautocmd FastFold BufWinEnter if g:loaded_fastfold after loading the view but it feels a bit clumsy.  It's starting to feel too coupled between the two plugins.
FastFold could export its BufWinEnter and BufWinLeave actions as functions and you could stitch them into your pre/post load and save behaviour and disable the equivalent FastFold autocommands, effectively hijacking its behaviour and sequencing it yourself.
As a general integration architecture I think something like that may be your only option since you have no control over the order of BufWinEnter and BufWinLeave autocommands.  In fact a specific plugin load order wont work in general because you want the Enter and Leave sequences to be in opposite orders as a stack.

That change has the effect of resetting the fdm to the default setting rather than the view setting.

It should set it to manual; I thought the problem was

FastFold not setting the mode to manual when first loading a buffer

and that should fix it as far as interference from loading a vim-stay view is concerned,  provided you have patched save_post() as described above.

Sorry, I wasn't very clear in my description.  I skipped a bit.
The change you have proposed does leave the l:foldmethod set to manual correctly, the issue is that FastFold never gets to see the loadview fdm value, and so its lastfdm value holds the default value.  Basically save_post is wiping out the loadview fdm value before FastFold has a chance to cache it.

Ah, now I understand – you’re right of course, the view session can load a different foldmethod. That seems easily solvable, tho, by calling a dedicated load_post() instead of save_post() in the BufStayLoadPost autocommand, which would issue a FastFoldUpdate command.

Yes of course, FastFoldUpdate does exactly what is needed here.  I'm about to sign off for the weekend, I'll have another fiddle and do some more testing on Monday.

@Parakleta I’ll do the fiddling, you do the testing :). Checks this thread on Monday.
@Konfekt any furthers thoughts?

I am a bit lost. Regarding

That change has the effect of resetting the fdm to the default setting rather than the view setting. FastFold's lastfdm is set to the default value that prevailed before the view was loaded (by its BufWinEnter firing before loadview) and then save_post is restoring that value rather than the post-view value.

one should note that there is also a SessionPost autocmd event fired by every loadview (there is do autocmd SessionPost in every view file) that resets fdm to manual.
@Parakleta, what exactly goes wrong with the proposed solution at https://github.com/kopischke/vim-stay/issues/5#issuecomment-72935831 ?

one should note that there is also a SessionPost autocmd event fired by every loadview (there is do autocmd SessionPost in every view file) that resets fdm to manual.

Good call – the root cause of the load issue is that vim-stay suppresses all autocommands when loading a session as I found it significantly slows down buffer window entries, even on a fast machine and when there are no autocommands listening to that event. That is fine for the occasional manual load, but it’s a deal breaker for a plug-in that does as many loading as vim-stay.
I have added manual triggering of SessionLoadPost to the view restoration of the upcoming release, which doesn’t seem to cause the same slowdown (not sure I even want to know… the Ways of Vim are Inscrutable) – that should fix that part of the interaction with FastFold.

@Parakleta could you give the preliminary 1.2 branch a whirl?

I cannot make it misbehave now, seems all good.  Thanks.

@Konfekt any comments before I release this?

Hmm.. Works fine when thr user uses syntax or expression folding, but in fact FastFold does not enter at all for other foldmethods. So resetting the fold method to thr previous one on the Post event is more compliant..

resetting the fold method to thr previous one on the Post event is more compliant..

Not sure if I follow  your meaning. Are we talking about BufStaySavePost here?

Yep, but I was mistaken. In that case the lastfdm is not Set. So I think it's Alright.

In that case the lastfdm is not Set.

vim-stay never touches the fold method unless w:lastfdm is set, so I guess this is not an issue solvable on my side (if it is one at all?). Will release tomorrow, then

Yep, looks good. I think FastFold never creates lastfdm if it doesn't touch anything.

Good to know, thanks :), For the purpose of this integration module, I am going to assume that the state of w:lastfdm is consistently well defined (i.e. it is always set to they last user defined fold method when FastFold is active, and unset when it is not). That is its API contract, right?

I pushed a commit that ensures this. Hopefully this does not break anything else.
Is all of this going to be reflected in your pull request as well? I will think about it when I've more leisure.

Is all of this going to be reflected in your pull request as well? I will think about it when I've more leisure.

I’ll update it to reflect the changes, then.


Question about the context

Hello,
In the documentation of the REST API, it's possible to use the context to keep a short conversational memory, but I didn't find how to use it with the JavaScript API. Is it implemented?

🤔, oh I think I found it, I didn't see GenerateRequest and GenerateResponse, sorry

For noobs like me:
import {Ollama} from 'ollama'

let ollama = new Ollama({
  host: "http://localhost:11434"
})

const result1 = await ollama.generate({
  model: 'llama2',
  prompt:'You are Yoda. Who is Vader?',
  context: []
})

console.log("🤖", result1.response)

const result2 = await ollama.generate({
  model: 'llama2',
  prompt:'Who are his children?',
  context: result1.context
})

console.log("🤖", result2.response)


count rows

We already count the number of rows returned anyway, we may as well output it too.

Resolved with commit 6b843f39e25cd3b27cd3ef0afbbb2e2b154a0ab2.


Fix a misguide of release doc.

Use the official key file.

I am not sure which is better :) download.* looks like a link for outside, such as download page. I am quite sure about this.


kicost: init at 1.1.18

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[ ] Fits CONTRIBUTING.md.

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

Ofborg reports: error: undefined variable 'XlsxWriter'

Hello can I get another review please ?

Hello, is there something I can do to help with merging ?

Hello, is there something I can do to help with merging ?

Post your pr in the discourse! See https://discourse.nixos.org/t/prs-already-reviewed/2617

Hello, is it possible to merge with 1.1.18 ?

@ofborg build kicost


Looking for scrub bar thumbnails plugin

Just wondering if there's a plugin that will show thumbnails above the scrub bar when hovering over the scrub bar yet (assuming thumbnail images have already been generated)?
I can see there's one on globo.com but understand you might not be open sourcing that one.
If not I'll have a look at building one.
Thanks!

@tjenkinson as far as I know, nope! :)
This will be awesome! You always help a lot, thanks once again. :beers:

hey @tjenkinson AFAIK globo.com thumb preview extend seek time component. Tell me if there's something I can do on my side to help u developing this feature.

Starting work on this here :)
https://github.com/tjenkinson/clappr-thumbnails-plugin

:clap: will be following the project, closing this for now

Any idea why mediaControl doesn't exist on this._core on line 23?
I'm off out now but will carry on debugging later

import {UICorePlugin, Events} from 'clappr'
import './style.css'

export default class ScrubThumbnailsPlugin extends UICorePlugin {
  get name() { return 'scrub-thumbnails' }

  get attributes() {
    return {
      'class': this.name
    }
  }

  constructor(core) {
    super(core)
    console.log("core", core)
    this._core = core
    this._init()
  }

  _init() {

    // this._core.mediaControl does not exist here

    console.log("init", this._core);
    this.listenTo(this._core.mediaControl, Events.MEDIACONTROL_CONTAINERCHANGED, this._onContainerChanged)
    this.listenTo(this._core.mediaControl, Events.MEDIACONTROL_RENDERED, this._renderInMediaControl)

  }

  _renderInMediaControl() {
    console.log("renderInMediaControl")
  }

  _onContainerChanged() {
    console.log("container changed")
  }

  destroy() {
    console.log("destroying")
  }

  render() {
    console.log("render", this.$el)
    this.$el.html("test");
   // this._core.mediaControl.$el.find('.media-control-right-panel').append(this.el)
    return this
  }
}

Nevermind found the issue.
I had
plugins: {
   container: [ClapprThumbnailsPlugin]
 }

instead of
plugins: {
   core: [ClapprThumbnailsPlugin]
}

Maybe a check could be performed when the plugins are loaded in to make sure what they are extending makes sense for the type they're being loaded in as?

@tjenkinson I totally agree with you, I was in the same situation as you last Friday. We should create an issue for it.

Done :)
https://github.com/clappr/clappr/issues/584

Next question :P
Is the core property on UICorePlugin part of the api which can be used by plugins or not? I'm presuming it is but the level selector plugin seems to store it in again after getting it from the constructor (although it's actually storing it back over itself).
https://github.com/clappr/clappr-level-selector-plugin/blob/master/src/main.js#L29

@tjenkinson yes, it is! https://github.com/clappr/clappr/blob/master/src/base/ui_core_plugin.js#L7
Level selector is not using it right, beyond that LS even call super after code. (which is something wrong too, I think)

Cool thanks. Yes it is webpack gave me errors about that when I initially had it that way

It looks like if an exception is thrown it is caught somewhere and not printed to the console.
I am currently doing
console.log("in render")
throw "test"

in the render() function. The first message is logged to the console but then there's nothing.

did you enable Logger to debug?
https://github.com/clappr/clappr/blob/master/src/plugins/log/log.js#L23
We log when almost all events are triggered (either its success or exception).
Although, throw "s" should be seen as an exception not an debug info.

Think version 1 is finished!
http://tjenkinson.me/clappr-thumbnails-plugin/
Look allright?
No I never touched the logger. Will look at that next.

it looks awesome!

pretty cool @tjenkinson : ), we should put it on README (external plugins)
https://github.com/tjenkinson/clappr-thumbnails-plugin

congrats @tjenkinson :beers:

and how to use VTT file for them?
is it possible to use VTT file across https://github.com/tjenkinson/clappr-thumbnails-plugin ?

@PooriaFarhad it doesn't at the moment but it might be possible to add this support. Please can you open an issue here and provide an ecample VTT file?


Add private option to fetchFromGitLab

Issue description
fetchFromGitHub has a private option, it would be nice if fetchFromGitLab did as well.
Steps to reproduce
Attempt to use fetchFromGitLab with a private repo. Experience pain.

Currently, I'm using fetchgitPrivate (https://www.mpscholten.de/nixos/2016/07/07/private-github-repositories-and-nixos.html)
  backend = fetchgitPrivate {
    url    = "ssh://git@gitlab.MY_COMPANY.com:MY_COMPANY_PORT/MY_USERNAME/MY_REPO.git";
    rev    = "XXXXX";
    sha256 = "YYYY";
  };

I have makefile
copy_gitlab_MY_COMPANY_com_key:
	sudo cp ~/.ssh/id_rsa secrets/gitlab.MY_COMPANY.com/id_rsa
	sudo cp ~/.ssh/id_rsa.pub secrets/gitlab.MY_COMPANY.com/id_rsa.pub
	sudo chown nixbld1:nixbld -R secrets/gitlab.MY_COMPANY.com
	sudo chmod 600 secrets/gitlab.MY_COMPANY.com/*
	sudo chmod 644 secrets/gitlab.MY_COMPANY.com/*.pub

I have shell.nix with NIX_PATH
  NIX_PATH = concatStringsSep ":" [
    (let
      sshConfigFile =
        pkgs.writeText "ssh_config" ''
          Host gitlab.MY_COMPANY.com
          IdentityFile ${toString ../secrets/gitlab.MY_COMPANY.com/id_rsa}
          StrictHostKeyChecking=no
        '';
    in
      "ssh-config-file=${sshConfigFile}"
    )
  ];

But I dont like that, this approach doenst work with sandbox

It would be better to use impureEnvVars to pass gitlab private token
but I can't pass  impureEnvVars to builder, nor from current shell, nor from /nix/configuration.nix nix.envVars
https://github.com/NixOS/nixpkgs/issues/45404
Progress so far https://github.com/srghma/nixpkgs/commit/2e696aac6d4328be1afa5e9bedb9a0d02d423ca4

Update:
Instead of the solution above, I'm using builtins.fetchGit now, as @symphorien suggested.
And it works perfectly. Repo is downloaded at evaluation time and since it uses git of the current user it uses ssh keys of current user too.
https://github.com/NixOS/nix/blob/475a0a54a9c28c311f0c05d129bb165e7c215efb/src/libexpr/primops/fetchGit.cc#L38-L43

@Fresheyeball I'm also using fetchGit with success on privately hosted GitLab. Please close this issue.

Could you guys put few words into the docs so new people could follow that? I found that quite a few people ask me over and over how to solve that issue and each time they are searching long hours over to find proper solution. Maybe we could have quite chapter in docs how to apply that within few minutes?

@srghma found this thread while trying to figure out fetchGit. Right now I get Could not create directory '/var/empty/.ssh'. :/. Any tips?

@tbenst do you use keys or ssh agent?
do you have this error before or after phases? If during some phase, you could find some phase and create that directory manually.

@spinus I just have the key in the default location ~/.ssh/id_rsa, with default permissions. I do not use ssh-agent. I believe the error is happening before phases.
{ lib, buildPythonPackage, fetchgitPrivate, setuptools, fetchgit
}:

buildPythonPackage rec {
  pname = "XXXX";
  version = "XXXX";
  src = fetchgit {
    url = "git@github.com:XXXX/${pname}.git";
    rev  = "XXXX";
    sha256 = "XXXX";
  };

  propagatedBuildInputs = [
    setuptools
  ];

  meta = with lib; {
    homepage = "https://github.com/XXXX";
    maintainers = with maintainers; [ tbenst ];
  };
}

Let’s keep this one open

@tbenst looking at  https://github.com/NixOS/nixpkgs/issues/43583#issuecomment-509921959
you write

found this thread while trying to figure out fetchGit. Right now I get Could not create directory '/var/empty/.ssh'

but I see in https://github.com/NixOS/nixpkgs/issues/43583#issuecomment-510665973 you are using fetchgit function from nixpkgs, it is not the same as builtins.fetchGit
As far as I know, You are getting this error, because fetchgit function from nixpkgs runs git command on behalf of nixbuildXXX user, but builtins.fetchGit runs git command on behalf of your current user, using git application from your $PATH

Huh, thank you @srghma!! I had no idea about fetchgit vs fetchGit.
I think we should keep open as fetchFromGitLab having a private option is still valid

@srghma, it is related to caching, which is controlled with tarball-ttl nix option. There are another issues:

paths fetched with builtins.fetchGit cannot be substituted from binary cache
existing store path is not recognized by nix without a supplementing cache entry in ~/.cache/nix/*.sqlite in the absence of which a git clone will happen preventing offline workflow


Change platform target for Views and Launcher to x86

Unfortunately GeckoFx is 32bit only causing the following build warning:
warning MSB3270: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "Geckofx-Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=3209ac31600d1857, processorArchitecture=x86", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.

This is a shame. Because of our user interface layer, our  entire application is forced into 32 bit. Maybe we can compile as  any cpu and have the UI project do 32 but, but launcher remains any cpu, which should default to 64 but on the appropriate machines.

All that being said, I should have asked if you tried just seeing views to 32 bit

The warning currently is on both projects, the UI appears to be working with or without this PR.
Test runners are also required to be running 32 bit to avoid Composer errors.
That said, I agree it's a shame (the alternative is to roll back to pre-GeckoFx, which is Windows only by the way)

It doesn't show it in the code, but before reinstating geckoFX I tried a few different web browser control libraries. This meant trying to change the build profiles in the way that's being described. I've come to two conclusions through doing this:

The flexibility is hamstrung by the fact that the browser control runs in a thread spawned by the launcher. This is to enable a communication channel. What might be more flexible is to spawn a process and change from inter-thread to inter-process communication (via wcf or whatever). This means the launcher and views can be separate build profiles and possibly separate solutions and repos.
It's a convenience to have one control that works in both Linux and Windows and will not significantly add to the code base to choose the right library for the right platform. There are CEF (chrome) based libraries that offer cross platform, but maybe something like an IBrowserProvider is worthwhile so these controls can be integrated in a uniform way.

The developers seem to intend GeckoFX to also run in linux. I'm just getting my mono environment setup to test this. The other library that I found to be fairly painless is:  http://cefsharp.github.io/

@mchandschuh The only effect of this PR is to remove the build warning mentioned above.
Launcher is already running as a 32bit process - can be verified with Environment.Is64BitProcess.
It is compiled using AnyCPU platform target with "Prefer 32 bit" option. If you uncheck it, on a 64bit machine Launcher will start as a 64bit process but Composer.GetExportedValueByTypeName will throw BadImageFormatException as expected (trying to load a 32bit library into a 64bit process).
@jameschch I agree that making Views an executable and using IPC would solve the 32/64 issue.
I also looked at the other libraries available (CefSharp, CefGlue, ChromiumFx) and they all have missing or experimental Linux support:
CefSharp - https://github.com/cefsharp/CefSharp/issues/1450
CefGlue - https://bitbucket.org/xilium/xilium.cefglue/issues/108/linux-support
ChromiumFx - https://bitbucket.org/chromiumfx/chromiumfx/issues/9/mono-support
so it looks like GeckoFx is the right choice after all: https://bitbucket.org/geckofx/geckofx/wiki/Home

Sadly forcing 32bit isn't really a viable option; making it a separate executable isn't a bad idea -- then it could be long running and open a new tab-view for each backtest which is run. On load the UX exe could also check if another instance of itself is running and if so, switch focus to that window.
Ideally this would be in the same repo for now though since we could use the toolbox projects easily (imagine UX on a IDataDownloader[] for LEAN to allow people to download data they needed from a list of providers).
We also brainstormed allowing saving the local .json backtest result files and allow opening them later, and saving the .json quantconnect.com results and opening them locally.
@jameschch, What do you think about spearheading this project? Making UX a standalone executable; switch focus to self on load; make LEAN IPC messaging handler; and make a UX side IPC receiver.

It sounds like a nice idea to extend the capabilities of the desktop client. At the moment I have several things not-quite-done that I'd really like to get squared away first.
I'd want to make sure the client was consistent with the overall architectural vision of the project so there may need to be some dialogue before it gets moving.

Closing as addressed by PR: https://github.com/QuantConnect/Lean/pull/550


EnvironmentDetector doesn't parse options separated with a space

Laravel Version: 5.8.21
PHP Version: 7.3.5
Database Driver & Version: N/A

Description:
The Symfony console component that is used by the Artisan console allows separating option names and values with either a space or an equals (=) sign. For example:
$ php artisan serve --port=9090
Laravel development server started: <http://<IP_ADDRESS>:9090>
$ php artisan serve --port 9090
Laravel development server started: <http://<IP_ADDRESS>:9090>

However, the --env option is only parsed correctly if you use an equals sign. If you use a space app()->environment() will return false.
This inconsistency is pretty confusing and difficult to debug. If you dump $this->option('env') in a command it will return the expected value but $app()->environment() will return false.
Steps To Reproduce:

Pass the --env flag to tinker, i.e. `php artisan tinker --env testing
Execute app()->environment() in the tinker shell

$ php artisan tinker --env=testing
Psy Shell v0.9.8 (PHP 7.3.5 — cli) by Justin Hileman
>>> app()->environment()
=> "testing"
>>>

$ php artisan tinker --env testing
Psy Shell v0.9.8 (PHP 7.3.5 — cli) by Justin Hileman
>>> app()->environment()
=> false
>>>

This appears to be happening because the environment detector uses $_SERVER['argv'] and  $_SERVER['argv'] splits the options into two separate array elements if you use a space instead of an equals sign, and the EnvironmentDetector expects a single element to contain both the name and the value.
$ php artisan tinker --env testing
Psy Shell v0.9.8 (PHP 7.3.5 — cli) by Justin Hileman
>>> $_SERVER['argv']
=> [
     "artisan",
     "tinker",
     "--env",
     "testing",
   ]

$ php artisan tinker --env=testing
Psy Shell v0.9.8 (PHP 7.3.5 — cli) by Justin Hileman
>>> $_SERVER['argv']
=> [
     "artisan",
     "tinker",
     "--env=testing",
   ]

Thanks for reporting. Welcoming any help with this.


wsl2 更新失败(退出代码: 1603)。 Error code: Wsl/CallMsi/Install/ERROR_INSTALL_FAILURE

Windows Version
22631.3737
WSL Version
2.2.4
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps

install Microsoft.WSL_<IP_ADDRESS>_x64_ARM64.msixbundle
start wsl

Expected Behavior
enter ubuntu
Actual Behavior
WSL 正在完成升级...
Warning 1946.Property 'System.AppUserModel.ID' for shortcut 'WSL.lnk' could not be set.
Warning 1946.Property 'System.AppUserModel.ToastActivatorCLSID' for shortcut 'WSL.lnk' could not be set.
Could not write value  to key \SOFTWARE\Classes\Directory\shell\WSL.   Verify that you have sufficient access to that key, or contact your support personnel.
更新失败(退出代码: 1603)。
Error code: Wsl/CallMsi/Install/ERROR_INSTALL_FAILURE
Diagnostic Logs
No response

https://github.com/microsoft/WSL/issues/11697#issuecomment-2168104220

Same problem. Maybe Windows update KB5039212 damaged it.
Everytime I execute wsl commands in PS, it shows
WSL 正在完成升级...
Warning 1946.Property 'System.AppUserModel.ID' for shortcut 'WSL.lnk' could not be set.
Warning 1946.Property 'System.AppUserModel.ToastActivatorCLSID' for shortcut 'WSL.lnk' could not be set.
Could not write value  to key \SOFTWARE\Classes\Directory\shell\WSL.   Verify that you have sufficient access to that key, or contact your support personnel.
更新失败(退出代码: 1603)。
Error code: Wsl/CallMsi/Install/ERROR_INSTALL_FAILURE

and when I enter a wsl distribution, it shows
WSL 正在完成升级...
Could not write value  to key \SOFTWARE\Classes\Directory\shell\WSL.   Verify that you have sufficient access to that key, or contact your support personnel.
更新失败(退出代码: 1603)。
Error code: Wsl/CallMsi/Install/ERROR_INSTALL_FAILURE

#11697 (comment)

It works, thanks a lot!

#11697 (comment)

有效，谢谢

#11697 (comment)

It works, thanks !


Improve handling of images with spaces in file name

Context

Summary
Wrap  encodeURI around source_url in calculateSrcSet and add a unit test for it.
Relevant Technical Choices

To-do

User-facing changes

Testing Instructions

[x] This is a non-user-facing change and requires no QA

This PR can be tested by following these steps:

Reviews
Does this PR have a security-related impact?

Does this PR change what data or activity we track or use?

Does this PR have a legal-related impact?

Checklist

[x] This PR addresses an existing issue and I have linked this PR to it in ZenHub
[x] I have tested this code to the best of my abilities
[x] I have verified accessibility to the best of my abilities (docs)
[x] I have verified i18n and l10n (translation, right-to-left layout) to the best of my abilities
[x] This code is covered by automated tests (unit, integration, and/or e2e) to verify it works as intended (docs)
[x] I have added documentation where necessary
[x] I have added a matching Type: XYZ label to the PR

Fixes #5969

Addressed feedback.


[Feature] Navbar Section

Navbar needs an improvement .

Navigation: The navbar provides a clear and consistent way for users to navigate a website.
User Experience: It enhances the overall user experience by helping users find information quickly and easily.
Branding and Identity: The navbar incorporates logos and branding elements to reinforce the website's identity.
Responsive Design: It adapts to different screen sizes, ensuring a mobile-friendly experience.
Call to Action: The navbar often includes prominent buttons or links for important actions or engagements.

Hello parthpathakpp1, thanks for opening a issue, your contribution is valuable to us. The maintainers will review this issue and provide feedback as soon as possible.

Can you assign me this issue under GSSOC'23.

Closing this as same issue as #25


Actaully lock accesses to OptionValueFileSpecList objects

The patch in r359029 missed a few accessors and mutators. This patch
also changes the lock to a recursive one as OptionValueFileSpecList::Clear()
can be invoked from some of the other methods.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@361440 91177308-0d34-0410-b5e6-96231b3b80d8
(cherry picked from commit 780aa8859164962b08181a02c1d9bab4f3cc5c79)

@swift-ci test and merge


Add support for debug build for rust providers #2298

Support for debug build for rust providers
This changes aims to enable building a rust provider in debug mode by enabling debug mode in the wasmcloud.toml
file like this.
[rust]
target_dir = "../../"

debug = true

Hey @Alex-omosa this looks great! Would you mind adding a test for this? You should be able to mostly copy one of the existing build tests!

Hello @vados-cosmonic.
I need a little help with the test cases that I've added.
When I do debug = false on the wasmcloud.toml, the test passes. However, when I do debug = true to test build in debug mode, I get this error No such file or directory (os error 2).

I'm just starting out with Rust, so I'm kinda stuck.
Your help is much appreciated.

Thanks @brooksmtownsend .
Please check the changes I've made.

Thanks @vados-cosmonic & @brooksmtownsend.
This was a valuable learning experience for me. I'm happy to continue contributing to the project.

Hey @Alex-omosa glad to hear it!
Looks like there's a way to make the implementation a little better (the tests are failing):
 thread 'rust_component' panicked at crates/wash-lib/tests/parser/main.rs:17:18:
assertion failed, expected Ok(..), got Err(missing field `debug`)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I think on this line here you need to make it an Option<bool> so that files can not specify debug.
For example if you look at rust_component.toml -- the debug option isn't there at all, so we need to make that possible!

Hey @Alex-omosa I've just added the last change, thanks for working on this -- this should merge as soon as tests pass.


Add an example for AMP cache. Fixes #87

I signed it!
2016-03-18 12:21 GMT+00:00 googlebot<EMAIL_ADDRESS>
Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).
[image: :memo:] Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the
company's name.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/ampproject/amp-by-example/pull/104#issuecomment-198328121

--
Chiara Chiappini

I added some additional explanations, PTAL

@sebastianbenz  PTAL

Can you include our test page for the get parameter sample: https://ampbyexample.com/g?value=Hello World The link will work once you remove the line including "template" in app.yaml.
Can you add a warning box to the redirect sample? You need to define the class warning which adds  a background color to the card, e.g. #F8BBD0.

<p class="card warning">If you move the location of the AMP Files on your server, make sure to set up a redirect from the old location to the new one. </p>

PTAL

I've added a few more comments.

Can you also please s/Url/URL/g

Changed background color for warning and added some margin.
PTAL.

@kul3r4 I've updated the PR with our changes. PTAL


[tour] Equivalent Binary Trees exercise uses Binary Search Tree (BST).

In the exercise "Equivalent Binary Trees" binary search trees (BST) are used but text uses term "binary tree". I suggest using binary search tree term instead of binary tree as it implies that nodes are inserted according to a rule (lesser elements go to the left). Technically speaking two binary trees that are not sorted and contain same elements will not necessarily return elements in order using "in order traversal" (left node, current node, right node). This technique will only work on binary search trees.

Seems like a duplicate of https://github.com/golang/tour/issues/403#issuecomment-401782939.

As a person with CS background, I can quickly get what it meant:

[1, 1, 2, 3, 5, 8, 13]. Yeah, of course, it's the result of an in-order tree walk for both structures!

But for someone not so familiar to things like the properties of binary search tree, the different kinds of tree traversals, it  might be confusing since there are no keywords related to "binary search tree" that they can use to Google.


Corrected path to team.md in readme.md

I approved and merge, but please use the correct branch name next time./


[Bug]: SimpleDirectoryReader with Remote s3 file system: "ValueError: {s3 bucket name/directory/file_name} is not in the subpath of {as if local fs} OR one path is relative and the other is absolute.

Bug Description
When attempting to use an s3 remote fs with "SimpleDirectoryReader"...error unless I manually set 'skip_because_hidden' to False. Get following error: "ValueError: {s3 bucket name/directory/file_name} is not in the subpath of {as if local fs} OR one path is relative and the other is absolute."
Where:

{s3 bucket name/directory/file_name} is the path to the file in my s3 bucket, starting at bucket_name
{as if local fs} is as if I wanted to append {s3 bucket name/directory/file_name} to my current working directory

Fixed by manually setting "skip_because_hidden" to False. Not sure what I did wrong. I also am using "input_dir" instead of "input_files"...because I passed in the directory of the files in my s3 bucket. For some reason there's a mix match...one part assuming I am using a local file system (or at least logging this way), and the other knowing I am using remote.
Version
0.10.16
Steps to Reproduce
Step one: Create simple function to get s3 fs info and return your bucket_name and 'AbstractFileSystem':
def get_s3_info() -> Tuple[str, AbstractFileSystem]:
""" returns the bucket name and file system needed for LlamaIndex """
fs = s3fs.S3FileSystem(anon=False)
bucket_name = bucket_name
return bucket_name, fs
Step Two: Attempt to Load Documents
def load_documents(directory_path: str, bucket_name: str = bucket_name, fs: AbstractFileSystem = s3_fs, filename_as_id: bool = True, num_files_limit=None, num_workers=1):
# construct the input_directory
input_dir = f"{bucket_name}/{directory_path}"

# return the directory reader
reader = SimpleDirectoryReader(input_dir=input_dir, filename_as_id=filename_as_id, num_files_limit=None, fs=fs)

return reader.load_data(show_progress=True, num_workers=num_workers)

My bucket currently has 3 files: 1 pdf, 1 ppt, and 1 HTML (testing diff MIME types...do not think this would cause the error).
Relevant Logs/Tracbacks
No response

@chrismaresca-scalinglabs thanks for bringing this up - included a fix in my PR here

Merged the above PR to fix this issue. Will close for now, feel free to re-open if the issue persists.


openssl: Support older TLS and DH key

Resolves #1641

Due to SMTP is much less optimistic in terms of new encryption standards and due to fallback to plaintext - better to have TLSv1.0 then plaintext. Small DH key at this time work as DoS at all.

Guys DEFAULT@SECLEVEL=2 for mail is too much...

We have discussed this and come to the conclusion that reducing the TLS security level of the whole system should not be necessary. Instead, we have implemented falling back to unencrypted transport when sending, but have chosen to maintain the stronger security for inbound connections.
See 0dc6824a8f0315ea42b08f7e6812b821b62489c9 for the alternative.

So fallback to unencrypted connection is more secure than at least some encryption? Very strange :/, sorry I don't get it

Falling back is must be in place as by smtp standards, but I still think for speaking with pubic MX is better with at least tls1.0 then with plain. For clients - encryption could be mandatory, without option to fallback and more strict encryption settings, e.g.: TLSv1.2 minimum.
You're absolutely correct of course. Opportunistic encryption is marginally more secure than no encryption. If someone wants to write the code for this and they can justify that changing the TLS settings system-wide will not reduce the security of other protocols, then it may well be worth considering. However, in the meantime I consider opportunistic SMTP encryption to be so weak that it's not worth compromising the security of any other part of the system to support it.
It would be much better if openssl's settings could be overridden for the opportunistic sending process only, but your reply implies that this isn't possible :(


Speech to Text functionality

Adding support for speech to text functionality.

Hi @simo101 thanks for the pull-request, we appreciate the help. We'll look into it

@RaphaelAudet You're welcome.

Anyone had chance to take a look at this?


Add Lens Studio

I've added Lens Studio, Snapchat's platform to create AR experiences

@robin-dela, it's an ideal pull request and with a correct label! Thank you!


No Web UI

Hi. I want to run Docker in the same Raspberry Pi as Klipper/Moonraker.
I installed Docker with this line commands:
curl -sSL https://get.docker.com | sh
sudo usermod -aG docker pi
My Docker installation is running well:
When I run command "docker run hello-world" I get the right info.
Then I created a folder called spool man and inside it I created a file called docker-compose.yml and a folder called data.
Inside docker-compose.yml I pasted the text:
version: '3.8'
services:
spoolman:
image: ghcr.io/donkie/spoolman:latest
restart: unless-stopped
volumes:
- ./data:/home/app/.local/share/spoolman
ports:
- "7912:8000"
environment:
- TZ=Europe/Lisbon # Optional, defaults to UTC
Then did run "chown 1000:1000 data".
Last command was:
docker compose up -d
I rebooted but I cannot get access to WebUI at <IP_ADDRESS>:7912 (my raspberry Pi IP is correct).
If I run the command "docker info", I get:
Server:
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 1
It appears that the container is not running. I tried to start it, but no success.
What can be the problem?

You should first of all try to get the docker logs of the container. Do
docker-compose logs
And see if it contains anything that looks like an error

Here is the log:
spoolman-spoolman-1  | Traceback (most recent call last):
spoolman-spoolman-1  |   File "/home/app/.venv/bin/uvicorn", line 5, in
spoolman-spoolman-1  |     from uvicorn.main import main
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/init.py", line 1, in
spoolman-spoolman-1  |     from uvicorn.config import Config
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/config.py", line 1, in
spoolman-spoolman-1  |     import asyncio
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/init.py", line 8, in
spoolman-spoolman-1  |     from .base_events import *
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/base_events.py", line 18, in
spoolman-spoolman-1  |     import concurrent.futures
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/init.py", line 8, in
spoolman-spoolman-1  |     from concurrent.futures._base import (FIRST_COMPLETED,
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/_base.py", line 7, in
spoolman-spoolman-1  |     import logging
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/logging/init.py", line 58, in
spoolman-spoolman-1  |     _startTime = time.time()
spoolman-spoolman-1  |                  ^^^^^^^^^^^
spoolman-spoolman-1  | PermissionError: [Errno 1] Operation not permitted
spoolman-spoolman-1  | Traceback (most recent call last):
spoolman-spoolman-1  |   File "/home/app/.venv/bin/uvicorn", line 5, in
spoolman-spoolman-1  |     from uvicorn.main import main
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/init.py", line 1, in
spoolman-spoolman-1  |     from uvicorn.config import Config
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/config.py", line 1, in
spoolman-spoolman-1  |     import asyncio
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/init.py", line 8, in
spoolman-spoolman-1  |     from .base_events import *
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/base_events.py", line 18, in
spoolman-spoolman-1  |     import concurrent.futures
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/init.py", line 8, in
spoolman-spoolman-1  |     from concurrent.futures._base import (FIRST_COMPLETED,
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/_base.py", line 7, in
spoolman-spoolman-1  |     import logging
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/logging/init.py", line 58, in
spoolman-spoolman-1  |     _startTime = time.time()
spoolman-spoolman-1  |                  ^^^^^^^^^^^
spoolman-spoolman-1  | PermissionError: [Errno 1] Operation not permitted
spoolman-spoolman-1  | Traceback (most recent call last):
spoolman-spoolman-1  |   File "/home/app/.venv/bin/uvicorn", line 5, in
spoolman-spoolman-1  |     from uvicorn.main import main
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/init.py", line 1, in
spoolman-spoolman-1  |     from uvicorn.config import Config
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/config.py", line 1, in
spoolman-spoolman-1  |     import asyncio
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/init.py", line 8, in
spoolman-spoolman-1  |     from .base_events import *
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/base_events.py", line 18, in
spoolman-spoolman-1  |     import concurrent.futures
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/init.py", line 8, in
spoolman-spoolman-1  |     from concurrent.futures._base import (FIRST_COMPLETED,
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/_base.py", line 7, in
spoolman-spoolman-1  |     import logging
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/logging/init.py", line 58, in
spoolman-spoolman-1  |     _startTime = time.time()
spoolman-spoolman-1  |                  ^^^^^^^^^^^
spoolman-spoolman-1  | PermissionError: [Errno 1] Operation not permitted
spoolman-spoolman-1  | Traceback (most recent call last):
spoolman-spoolman-1  |   File "/home/app/.venv/bin/uvicorn", line 5, in
spoolman-spoolman-1  |     from uvicorn.main import main
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/init.py", line 1, in
spoolman-spoolman-1  |     from uvicorn.config import Config
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/config.py", line 1, in
spoolman-spoolman-1  |     import asyncio
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/init.py", line 8, in
spoolman-spoolman-1  |     from .base_events import *
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/base_events.py", line 18, in
spoolman-spoolman-1  |     import concurrent.futures
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/init.py", line 8, in
spoolman-spoolman-1  |     from concurrent.futures._base import (FIRST_COMPLETED,
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/_base.py", line 7, in
spoolman-spoolman-1  |     import logging
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/logging/init.py", line 58, in
spoolman-spoolman-1  |     _startTime = time.time()
spoolman-spoolman-1  |                  ^^^^^^^^^^^
spoolman-spoolman-1  | PermissionError: [Errno 1] Operation not permitted
spoolman-spoolman-1  | Traceback (most recent call last):
spoolman-spoolman-1  |   File "/home/app/.venv/bin/uvicorn", line 5, in
spoolman-spoolman-1  |     from uvicorn.main import main
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/init.py", line 1, in
spoolman-spoolman-1  |     from uvicorn.config import Config
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/config.py", line 1, in
spoolman-spoolman-1  |     import asyncio
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/init.py", line 8, in
spoolman-spoolman-1  |     from .base_events import *
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/base_events.py", line 18, in
spoolman-spoolman-1  |     import concurrent.futures
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/init.py", line 8, in
spoolman-spoolman-1  |     from concurrent.futures._base import (FIRST_COMPLETED,
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/_base.py", line 7, in
spoolman-spoolman-1  |     import logging
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/logging/init.py", line 58, in
spoolman-spoolman-1  |     _startTime = time.time()
spoolman-spoolman-1  |                  ^^^^^^^^^^^
spoolman-spoolman-1  | PermissionError: [Errno 1] Operation not permitted
spoolman-spoolman-1  | Traceback (most recent call last):
spoolman-spoolman-1  |   File "/home/app/.venv/bin/uvicorn", line 5, in
spoolman-spoolman-1  |     from uvicorn.main import main
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/init.py", line 1, in
spoolman-spoolman-1  |     from uvicorn.config import Config
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/config.py", line 1, in
spoolman-spoolman-1  |     import asyncio
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/init.py", line 8, in
spoolman-spoolman-1  |     from .base_events import *
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/base_events.py", line 18, in
spoolman-spoolman-1  |     import concurrent.futures
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/init.py", line 8, in
spoolman-spoolman-1  |     from concurrent.futures._base import (FIRST_COMPLETED,
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/_base.py", line 7, in
spoolman-spoolman-1  |     import logging
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/logging/init.py", line 58, in
spoolman-spoolman-1  |     _startTime = time.time()
spoolman-spoolman-1  |                  ^^^^^^^^^^^
spoolman-spoolman-1  | PermissionError: [Errno 1] Operation not permitted
spoolman-spoolman-1  | Traceback (most recent call last):
spoolman-spoolman-1  |   File "/home/app/.venv/bin/uvicorn", line 5, in
spoolman-spoolman-1  |     from uvicorn.main import main
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/init.py", line 1, in
spoolman-spoolman-1  |     from uvicorn.config import Config
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/config.py", line 1, in
spoolman-spoolman-1  |     import asyncio
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/init.py", line 8, in
spoolman-spoolman-1  |     from .base_events import *
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/base_events.py", line 18, in
spoolman-spoolman-1  |     import concurrent.futures
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/init.py", line 8, in
spoolman-spoolman-1  |     from concurrent.futures._base import (FIRST_COMPLETED,
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/_base.py", line 7, in
spoolman-spoolman-1  |     import logging
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/logging/init.py", line 58, in
spoolman-spoolman-1  |     _startTime = time.time()
spoolman-spoolman-1  |                  ^^^^^^^^^^^
spoolman-spoolman-1  | PermissionError: [Errno 1] Operation not permitted
spoolman-spoolman-1  | Traceback (most recent call last):
spoolman-spoolman-1  |   File "/home/app/.venv/bin/uvicorn", line 5, in
spoolman-spoolman-1  |     from uvicorn.main import main
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/init.py", line 1, in
spoolman-spoolman-1  |     from uvicorn.config import Config
spoolman-spoolman-1  |   File "/home/app/.venv/lib/python3.11/site-packages/uvicorn/config.py", line 1, in
spoolman-spoolman-1  |     import asyncio
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/init.py", line 8, in
spoolman-spoolman-1  |     from .base_events import *
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/asyncio/base_events.py", line 18, in
spoolman-spoolman-1  |     import concurrent.futures
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/init.py", line 8, in
spoolman-spoolman-1  |     from concurrent.futures._base import (FIRST_COMPLETED,
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/concurrent/futures/_base.py", line 7, in
spoolman-spoolman-1  |     import logging
spoolman-spoolman-1  |   File "/usr/local/lib/python3.11/logging/init.py", line 58, in
spoolman-spoolman-1  |     _startTime = time.time()
spoolman-spoolman-1  |                  ^^^^^^^^^^^
spoolman-spoolman-1  | PermissionError: [Errno 1] Operation not permitted

This seems to be a known bug on Raspberry Pi 4, is that what you have?
Please follow this blog post and see if it works for you. https://blog.samcater.com/fix-workaround-rpi4-docker-libseccomp2-docker-20/


Vertical Scrolling Problem

I have the following structure.
An UINavigationController pushes a UIViewController with a xib with the following hierarchy:
-- UIView
--- AQGridView
AQGridView doesn't snap to the correct position (top one) after the bouncing animation have finished each time it is scrolled. The navigation bar of the UINavigationController overlaps the content displayed in the grid view.

Also — the XIB.
On Feb 28, 2012, at 11:46 PM, flexaddicted<EMAIL_ADDRESS>wrote:

I have the following structure.
An UINavigationController pushes a UIViewController with a xib with the following hierarchy:

UIView
-- AQGridView

AQGridView doesn't snap to the correct position (top one) after the bouncing animation have finished each time it is scrolled. The navigation bar of the UINavigationController overlaps the content displayed in the grid view.

Reply to this email directly or view it on GitHub:
https://github.com/AlanQuatermain/AQGridView/issues/115

Please post the code.  Thanks.
On Feb 28, 2012, at 11:46 PM, flexaddicted<EMAIL_ADDRESS>wrote:

I have the following structure.
An UINavigationController pushes a UIViewController with a xib with the following hierarchy:

UIView
-- AQGridView

AQGridView doesn't snap to the correct position (top one) after the bouncing animation have finished each time it is scrolled. The navigation bar of the UINavigationController overlaps the content displayed in the grid view.

Reply to this email directly or view it on GitHub:
https://github.com/AlanQuatermain/AQGridView/issues/115

I'm sorry. How can I post the code? Thank you in advance.

Could you create a GitHub repository and put your code there?
On Feb 28, 2012, at 11:54 PM, flexaddicted<EMAIL_ADDRESS>wrote:

I'm sorry. How can I post the code? Thank you in advance.

Reply to this email directly or view it on GitHub:
https://github.com/AlanQuatermain/AQGridView/issues/115#issuecomment-4218466

Ok, I'll do as soon as possible. Thank you again.


visionmedia (hamljs) module doesn't download

I changed   "hamljs": "^0.6.2" to "hamljs": "0.6.2" from your Package.json and now it works. Please update your package. Thanks :)

Closing as this is dependent to an older npm version.


[feature idea] can specify boxart border style per node/edge

as boxart is implemented (#16), it'd be a nice feature to be able to specify the border/edge styles in the diagram source text.
there are several box drawing chars in unicode (below).
specify these node attributes (or other more appropriate in mermaid-js) per node to render them other that the diagram's default:

weight

light (default)
heavy

style

solid (default)
double
double-dash
triple-dash
quadruple-dash

corner

square (default)
round

i have not found example in mermaid-js that edges can be styled with css-like attributes, only by typing the arrows with various chars for lines. we can follow this, although most of the line style are not standardized in mermaid-js, only "normal" (light) and "thick" (i'd translate it to unicode's heavy line, however it looks much more like the double lines) and maybe quadruple-dash looks like dotted.
so one options is to use mermaid-js syntax to change edges line style https://docs.mermaidchart.com/mermaid/flowchart/edges#edges-with-no-text

--> - light-solid (default) ─►
==> - heavy-solid ━►
##> - double (not found in mermaid-js) ═►
-_-> - double-dash light (not found in mermaid-js) ╌►
=_=> - double-dash heavy (not found in mermaid-js) ╍►
-_-_-> - triple-dash light (not found in mermaid-js) ┄►
=_=_=> - triple-dash heavy (not found in mermaid-js) ┅►
-.-> - quadruple-dash ┈►
=.=> - quadruple-dashheavy (not found in mermaid-js) ┉►

example
flowchart LR
node1 ==> node2
style node1 border-weight:heavy,border-style:quadruple-dash
style node2 corner:round

would render as:
┏┉┉┉┉┉┉┉┓     ╭───────╮
┋       ┋     │       │
┋ node1 ┋━━━━►│ node2 │
┋       ┋     │       │
┗┉┉┉┉┉┉┉┛     ╰───────╯

unicode chars
║ U+2551 BOX DRAWINGS DOUBLE VERTICAL

│ U+2502 BOX DRAWINGS LIGHT VERTICAL
┃ U+2503 BOX DRAWINGS HEAVY VERTICAL

╎ U+254E BOX DRAWINGS LIGHT DOUBLE DASH VERTICAL
╏ U+254F BOX DRAWINGS HEAVY DOUBLE DASH VERTICAL

┆ U+2506 BOX DRAWINGS LIGHT TRIPLE DASH VERTICAL
┇ U+2507 BOX DRAWINGS HEAVY TRIPLE DASH VERTICAL

┊ U+250A BOX DRAWINGS LIGHT QUADRUPLE DASH VERTICAL
┋ U+250B BOX DRAWINGS HEAVY QUADRUPLE DASH VERTICAL

╭ U+256D BOX DRAWINGS LIGHT ARC DOWN AND RIGHT
╮ U+256E BOX DRAWINGS LIGHT ARC DOWN AND LEFT
╯ U+256F BOX DRAWINGS LIGHT ARC UP AND LEFT
╰ U+2570 BOX DRAWINGS LIGHT ARC UP AND RIGHT

what do you think?

I agree, I definitely want to have something like this that implements different 'styles' of arrows, boxes etc. Like you mentioned, there are already syntactical definitions for these different kinds of arrows and I would like to adopt them somehow.
Good ideas!


Catalogue creation has some funny outputs with latest cwlutils

Enums are using full fragment fragment path
Paths are using full uri paths


Upgrade to QUnit 2.x

Hi,
all UI5 versions (have checked up to 1.44.7) are still using QUnit 1.18.0.
Having QUnit 2.x available would at a minimum allow us to use these really helpful features:

QUnit.only() to allow for working with that one test only
nested QUnit.module for grouping test on multiple levels

I've seen some discussion in #1105 to eventually go for an upgrade - wanted to +1 this with this enhancement-issue.
Sure there might be refactoring efforts involved, but only the above two listed features make up for that :)
Best, Volker

I totally agree. The refactoring effort for OpenUI5 is no longer our main concern. The real problem is that the qunit.js that we package is not only used by the OpenUI5 tests, but by many, many unit tests in upper layers (SAPUI5 and even apps build with UI5 - as far as they have unit tests).
We therefore consider to deviate from our normal practice (package only one version of each thirdparty software) and add a sap/ui/thirdparty/qunit2.js next to the existing one. After that addition, upper layers could decide on their own when to migrate.
Your next question most likely is: "When will you add it?". Any new open source that we add has to go through some internal approval process. Not sure what the status is for Qunit 2.0. I'll try to find out and update this issue.

excellent, good approach to have QUnit 1 + 2 co-exist.
Just took a peak myself in Black Duck and SRI: QUnit green (Black Duck) and grey (SRI), but only 1.x - want me to put in a request for 2.x to speed things up?

The internal approval process for including QUnit 2.1.1 has been started and a corresponding change has been prepared. We'll update this issue once there is significant progress.

Adding "approved" to say this will happen without further need to drive something

i am currently working on updating the tests, will post more details soon

Update: openui5 code base (all unit tests) have been lifted to QUnit 2.0 syntax now (phew that was some work). Real Migration to QUnit 2.0 is still pending though as we have some hard dependencies to dissolve first


Definition of interface SpiedMember

export interface SpiedMember {
    _func?: jasmine.Spy;
    _get?: jasmine.Spy;
    _set?: jasmine.Spy;
}

Can these properties be defined as non-nullable?
When strictNullChecks is set to true, following recommended usage produce error:
service._spy.toDataObject._func.and.returnValue({ id: null }); // Object is possible undefined

to avoid this error I must use following constructions, which looks dirty.
service._spy.toDataObject._func && service._spy.toDataObject._func.and.returnValue

Thanks @unlight! #5  will address the issue. In the meanwhile, you can use a typescript non-null assertion operator ! to achieve the same result without looking too dirty:
service._spy.toDataObject!._func.and.returnValue

--strictNullChecks is available in version 2.0.2. Closing the issue.


Succesfully tested on Linux

As you said it's untested on Linux. Now it isn't any longer.
I just installed this on Manjaro Cinnamon and it works perfectly. No issues.

Thanks @Eddi2015! Would you be willing to add a screenshot here just so I can see how it looks? I'll close it regardless. Also updated README to reflect the fact that it has been tested as of today.

I uploaded a screenshot with the light theme here: https://upload.disroot.org/r/LkHKtfrl#ItZdY6iXG3R4wmTRgu6vEnrHforU6/slHW1sVw1q9tw=
If you need a screenshot of the dark theme just tell me.


Wayland segfaults when trying to start from tty

Steps to reproduce
open tty (I opened with Ctrl-Alt-F2). Login. Type Hyprland
Expected outcome
Hyprland starts
Noted outcome
It segfaults.
hyprlandlogfile.log
My config is the example config that comes with the latest release as of the time I am writing this issue.
XDG_CACHE_HOME isn't set but I don't have a ~/.hyprland directory so I was unable to attach the file even though I'm running 0.24.1
hyprlandcoredump.txt
More about my environment
I am on pop os 22.04 LTS with wayland turned on.
Edit: I am using an amd-gpu.

I am on pop os 22.04 LTS with wayland turned on.

Makes sense.

ref: https://wiki.hyprland.org/Getting-Started/Installation/

Why did you close it, what do I need to do to get it to work.
When it said bleeding edge I thought it was just that I needed to compile some packages from source.
What kind of major issue is preventing me from using it on pop?!

because it's not a hyprland issue, as wlroots fails to open a backend. You can try launching from a tty and inspecting logs. Consider launching with HYPRLAND_LOG_WLR=1 to also print wlr errors.

What kind of major issue is preventing me from using it on pop?!

Everything is outdated.

Oh I see so nothing from Hyprland failed to open (yet). I have to check errors for wlroots. And also I'm ok with compiling some packages (even if I fall into dependency hell). Thanks for your help. If I need anymore, I will  go to the discord server. (Just joined it).


chia-plotter: init

Motivation for this change
Adds the chia-plotter project: https://github.com/madMAx43v3r/chia-plotter
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 132215 at e6fe32c9 run on x86_64-linux 1

1 package failed to build:

chia-plotter

2 suggestions:

warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/applications/blockchains/chia-plotter/default.nix:58:5:
   |
58 |     license = [ licenses.gpl3 ];
   |     ^

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/applications/blockchains/chia-plotter/default.nix:50:3:
   |
50 |   installPhase = ''
   |   ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.


Use clustermap to avoid state transitions from old resource

When reconstructing resources, if some hosts are down, and when they wake up, they would receive state transition messages for the old resources, which is to drop partitions. At the time, if the message of old resources comes before the message of new resources, ambry would drop those partitions. This is not good.
This PR fixes that by relying clustermap to provide the resource for a partition. If the resource provided by the clustermap is higher than the resource from the message, we would ignore this transition.

Codecov Report
Attention: 8 lines in your changes are missing coverage. Please review.

Comparison is base (5c461b4) 32.51% compared to head (e17412f) 17.02%.

Additional details and impacted files
@@              Coverage Diff              @@
##             master    #2631       +/-   ##
=============================================
- Coverage     32.51%   17.02%   -15.50%
+ Complexity     4462     2879     -1583
=============================================
  Files           806      806
  Lines         65237    65248       +11
  Branches       7951     7953        +2
=============================================
- Hits          21212    11106    -10106
- Misses        41794    53320    +11526
+ Partials       2231      822     -1409

Files
Coverage Δ

...ithub/ambry/clustermap/AmbryStateModelFactory.java
69.23% <100.00%> (+69.23%)
:arrow_up:

.../com/github/ambry/clustermap/HelixParticipant.java
47.76% <100.00%> (+42.87%)
:arrow_up:

...ub/ambry/clustermap/HelixClusterAgentsFactory.java
0.00% <0.00%> (-33.34%)
:arrow_down:

...m/github/ambry/clustermap/HelixClusterManager.java
42.09% <0.00%> (+3.44%)
:arrow_up:

...hub/ambry/clustermap/AmbryPartitionStateModel.java
33.68% <50.00%> (+33.68%)
:arrow_up:

... and 399 files with indirect coverage changes

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

The state transition message for the old resources is to drop these partitions.
What about the new resource message, is that trying to add back the same partitions? Or the new resource is irrelevant to the old partition?
When reconstructing resources, if some hosts are down, and when they wake up, they would receive state transition messages for the old resources, which is to drop partitions.
At the time, if the message of old resources comes before the message of new resources, ambry would drop those partitions. This is not good.

This PR fixes that by relying clustermap to provide the resource for a partition. If the resource provided by the clustermap is higher than the resource from the message, we would ignore this transition.


EdgeInsets.only or BorderRadius.only to accept an optional default parameter.

Use case
Currently to specify a padding different only on 1 side or 2 sides you have to type more than I think you should. This change will make the code less verbose and easier to follow. The change would be useful also in specifying a borderRadius, where the amount of repeated code is even greater (or to any .only method).

Proposal
EdgeInsets
const EdgeInsets.only(top: 20.0, default: 10.0)  will work the same as
const EdgeInsets.only(top: 20.0, left: 10.0, right: 10.0, bottom: 10.0)
or
const EdgeInsets.only(top: 20.0, bottom: 30.0, default: 10.0) will work the same as
const EdgeInsets.only(top: 20.0, bottom: 30.0, left: 10.0, right: 10.0)
BorderRadius
BorderRadius.only(
  topLeft: Radius.circular(0),
  default: Radius.circular(20.0)
)

will work the same as
BorderRadius.only(
  topLeft: Radius.circular(0),
  bottomLeft: Radius.circular(20.0),
  bottomRight: Radius.circular(20.0),
  topRight: Radius.circular(20.0)
)

really nice suggestion, would like to work on it if the proposal gets approved!

really nice suggestion, would like to work on it if the proposal gets approved!

Changing EdgeInsets.only in this way won't work because of const limitations.
That said, I'm not really convinced this is a problem. Flutter in general optimizes for readability, not brevity when writing. If you want things to be quick to write, rather than easy to read, then Flutter is going to be a painful experience throughout, not just with EdgeInsets and BorderRadius.

Changing EdgeInsets.only in this way won't work because of const limitations.
That said, I'm not really convinced this is a problem. Flutter in general optimizes for readability, not brevity when writing. If you want things to be quick to write, rather than easy to read, then Flutter is going to be a painful experience throughout, not just with EdgeInsets and BorderRadius.

Just figured out a shorter way to write the first example:
EdgeInsets.only(top: 20.0, left: 10.0, right: 10.0, bottom: 10.0)
Written like bellow works with the current syntax:
EdgeInsets.all(10.0).copyWith(top: 20.0)
I see your point. If it makes no sense and/or it's a difficult change then I guess people can use the shorter alternative that makes use of the copyWith method.

Just figured out a shorter way to write the first example:
EdgeInsets.only(top: 20.0, left: 10.0, right: 10.0, bottom: 10.0)
Written like bellow works with the current syntax:
EdgeInsets.all(10.0).copyWith(top: 20.0)
I see your point. If it makes no sense and/or it's a difficult change then I guess people can use the shorter alternative that makes use of the copyWith method.

This is just more code to maintain tbh

This is just more code to maintain tbh

I guess an option would be to introduce a new constructor, but yet again that is more code to maintain:
const EdgeInsets.withDefault(
      double value, {
      double left,
      double top,
      double right,
      double bottom,
    }) {
    return EdgeInsets.only(
      left: left ?? value,
      top: top ?? value,
      right: right ?? value,
      bottom: bottom ?? value,
    );
  }

Then we could use this as:
EdgeInsets.withDefault(10.0, top: 20.0)

instead of
EdgeInsets.only(left: 10.0, top: 20.0, right: 10.0, bottom: 10.0)

or the more inefficient
EdgeInsets.all(10.0).copyWith(top: 20.0)

Extension methods don't allow introducing new constructor for existing classes. That could've been a way to go about this on a project level.

I guess an option would be to introduce a new constructor, but yet again that is more code to maintain:
const EdgeInsets.withDefault(
      double value, {
      double left,
      double top,
      double right,
      double bottom,
    }) {
    return EdgeInsets.only(
      left: left ?? value,
      top: top ?? value,
      right: right ?? value,
      bottom: bottom ?? value,
    );
  }

Then we could use this as:
EdgeInsets.withDefault(10.0, top: 20.0)

instead of
EdgeInsets.only(left: 10.0, top: 20.0, right: 10.0, bottom: 10.0)

or the more inefficient
EdgeInsets.all(10.0).copyWith(top: 20.0)

Extension methods don't allow introducing new constructor for existing classes. That could've been a way to go about this on a project level.


Release: Clear Containers 3.0.5

No changes in this version for proxy.


Disabling an enchant in enchants.yml still gives enchantment book unless you remove categories

Example:

DoubleDamage:
Enabled: False
Name: 'DoubleDamage'
Color: '&7'
BookColor: '&b&l'
MaxPower: 5
Info:
Name: '&e&lDouble Damage'
Description:
- '&c&lSwords Only'
- '&3Has a chance to '
- '&3Deal double the damage'
Categories:
- 'T3'
This still gives you a book when you buy with xp

DoubleDamage:
Enabled: False
Name: 'DoubleDamage'
Color: '&7'
BookColor: '&b&l'
MaxPower: 5
Info:
Name: '&e&lDouble Damage'
Description:
- '&c&lSwords Only'
- '&3Has a chance to '
- '&3Deal double the damage'
Categories:
This doesn't give you a book when you buy with xp

Strange. Ill look into this.

I thought this was how it was supposed to work. XD I thought disabled enchants just don't do anything when equipped?

@Yukun99 yes they don't do anything but it shouldn't let you get them from the store. There is no reason to obtain it if it doesn't work.

Oh I thought they can't be obtained from the store, and only from commands? Okie then XD

I have checked and have not had this happen to me. Please make a new issue if in the next update you still have a problem


documentation: Improve the deprecation messages surrounding the GraphQLClient methods.

What are you missing in the docs
The @Deprecated("The RequestExecutor should be provided while creating the implementation.", ReplaceWith("Example: new DefaultGraphQLClient(url, requestExecutor);")) points toDefaultGraphQLClient, which is deprecated as well.
We need to suggest either CustomGraphQLClient, CustomReactiveGraphQLClient and WebClientGraphQLClient.
Creating a guide on when to use each of the clients mentioned above will help as well as provide examples of migrating from the deprecated method calls to the new clients.

I think the guide is already there: https://netflix.github.io/dgs/advanced/java-client/#usage

I think we are just missing a simple change in the GraphQLClient.kt file. Right now it reads...
graphql-dgs-client/src/main/kotlin/com/netflix/graphql/dgs/client/GraphQLClient.kt
59:    @Deprecated("The RequestExecutor should be provided while creating the implementation.", ReplaceWith("Example: new DefaultGraphQLClient(url, requestExecutor);"))
62:    @Deprecated("The RequestExecutor should be provided while creating the implementation.", ReplaceWith("Example: new DefaultGraphQLClient(url, requestExecutor);"))
116:    @Deprecated("The RequestExecutor should be provided while creating the implementation.", ReplaceWith("Example: new DefaultGraphQLClient(url, requestExecutor);"))
123:    @Deprecated("The RequestExecutor should be provided while creating the implementation.", ReplaceWith("Example: new DefaultGraphQLClient(url, requestExecutor);"))


watch function name conflicts with Vue's watch fn

As a workaround, we can import plugin as import { watch as watchFile } from 'tauri-plugin-fs-watch-api'; but it might be a good choice to change the function name into something like watchFile or watchDir or watchFS to avoid renaming the function.
It is not the best recommendation, but it might be good to consider this upcoming conflict

you should use the workaround you mentioned because it doesn't makes sense to change the function name at all, let alone for one framework.


Bug: Should not use Async methods in analyzers (CC0029)

Right now only DisposablesShouldCallSuppressFinalizeAnalyzer, for VB, is doing that.
See:
https://github.com/code-cracker/code-cracker/blob/master/src/VisualBasic/CodeCracker/Usage/DisposablesShouldCallSuppressFinalizeAnalyzer.vb#L38
This line: https://github.com/code-cracker/code-cracker/blob/master/src/VisualBasic/CodeCracker/Usage/DisposablesShouldCallSuppressFinalizeAnalyzer.vb#L51
Has to change from:
Dim syntaxTree = Await disposeMethod.DeclaringSyntaxReferences(0)?.GetSyntaxAsync(context.CancellationToken)

to:
Dim syntaxTree = disposeMethod.DeclaringSyntaxReferences(0)?.GetSyntax(context.CancellationToken)

And the method should not be async anymore.
More info: https://github.com/dotnet/roslyn/pull/13140

Closed in #863.


[Feature] Support adaptive DOP for except and union all

What type of PR is this：

[ ] BugFix
[x] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Relates to #15717.
Problem Summary(Required) ：

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

[FE PR Coverage Check]
:disappointed: fail : 0 / 2 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/planner/UnionNode.java
0
1
00.00%
[66]

:large_blue_circle:
com/starrocks/planner/ExceptNode.java
0
1
00.00%
[58]

run starrocks_admit_test

run starrocks_fe_unittest

run starrocks_fe_unittest

run starrocks_fe_unittest

run starrocks_fe_unittest

run starrocks_fe_unittest

run starrocks_fe_unittest

[FE PR Coverage Check]
:disappointed: fail : 0 / 2 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/planner/UnionNode.java
0
1
00.00%
[66]

:large_blue_circle:
com/starrocks/planner/ExceptNode.java
0
1
00.00%
[58]

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test


SW-5491/SW-5492 Added table settings button to common search filter

#2708  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tommylau523 and the rest of your teammates on  Graphite

Merge activity

Jun 7, 4:23 PM EDT: @tommylau523 merged this pull request with Graphite.


Update azure-websites-limits.md

Autoscale is not supported for Basic Tier of WebApps.

@toruita : Thanks for your contribution to the Azure documentation! The author, @azdocprs, has been notified to review your proposed change.

@cephalin - Please review the proposed changes.  Thanks

@toruita Thanks! #sign-off


RPC didn't work

Describe the bug
RPC didn't work in brave browser wallet.
Steps to reproduce
Need to compatible RPC for all browser wallet.
Spam policy

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

Can you show more error messages?


Different Indent guides between daemon vs standalone mode

What did you expect to happen?
In standalone emacs, indent guides are somewhat transparent:

What actually happened?
In emacs running as a daemon /usr/bin/emacs --daemon and opened as emacsclient -c, the indent guides look like:

Additional details:
default doom config with indent guides on
emacs 28

Interesting.  I also run it as a daemon and had seen the latter, and quickly turned it off.  I'd use it if it were lighter as in your first picture.

One thing i noticed, if you start emacs standalone (gui not daemon) first and then open emacsclient, then the transparency magically appears.

Sorry for the late response. As of 3907e75 this issue should be resolved. Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!


[CUR-638] Update ejs as per security warning in github

Description

Updated ejs as per https://github.com/oaknational/Oak-Web-Application/security/dependabot/99

Issue(s)
CUR-638
How to test
Check storybook and tests (which this module is a dep of) works ok.

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


feat: support new prefix (issue #83)

feat: support new prefix (issue #83)
Fixes #83
misc.
misc.
misc.
misc.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #80

PR #81

PR #82

PR #85   👈

This stack of pull requests is managed by Graphite.

Merge activity

Jan 9, 2:47 PM: Graphite rebased this pull request as part of a merge.


Getting Node.js 16 deprecation warnings when using this action

Been seeing the following warning when running workflows that use this action:
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20<EMAIL_ADDRESS>For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

I'm guessing a dependency bump + release is needed? Thanks!

Hello @ClementTsang
Thank you for the issue. We'll release it soon.

Hello @ClementTsang
What is the version of action in the workflow? The latest v1.3.0 uses nodejs 20 https://github.com/Wandalen/wretry.action/blob/js_action/action.yml#L55.

Ah, I found the confusion - in https://github.com/ClementTsang/bottom/actions/runs/7689540721, I was using Wandalen/wretry.action@a163f62ae554a8f3cbe27b23db15b60c0ae2e93c since that's what I saw was the hash in https://github.com/Wandalen/wretry.action/releases/tag/v1.3.0. That points to here, which matches what's currently in the master branch, but what's linked above that has the updated node version is the js_action branch.

If using
uses<EMAIL_ADDRESS>
here
https://github.com/pi-hole/FTL/blob/ce4407b53696b3fd1d5b76a4af7e7dfd1bd647eb/.github/workflows/build.yml#L90
isn't right, what are we supposed to use instead?

^ having the same issue
Really appreciate the dev work done on this action and any help in getting this fixed!

The only branch or tag with the node20 commit ba4878c3bf6fcdb73638487d901f06e2f24a7117 is js_action.
However this doesn't work
        uses: Wandalen/wretry.action@js_action

Because the script is broken
Wandalen/wretry.action/js_action/action.yml (Line: 39, Col: 18): Unrecognized named-value: 'inputs'. Located at position 9 within expression: toJSON( inputs )
Fail to load Wandalen/wretry.action/js_action/action.yml

The only option is to wait for a fix and release.


Enable codecov.io

This is mostly to see what it looks like, not sure if I'll merge yet.

Looks neat: https://codecov.io/gh/travis-ci/collectd-vsphere
Let's give it a go.


SFC is deprecated in @types/react

Hi, thanks for this really useful extension! From the @deprecated tag on React.SFC:

@deprecated
as of recent React versions, function components can no longer be considered 'stateless'.
Please use FunctionComponent instead.

Personally, I've found FC used as React.FC to be a more succinct form. Would you accept a PR changing the import?

Perfect :) thanks!


All HookResponse fields are Ignored for Post-Create

Reading the commentary on type HookResponse struct, it seems like every field inside HookResponse is ignored for post-create.
It is also non-blocking.
This means nothing that happens within post-create can change the state of the HTTP request that is going back to the client.

I have a use case where I only create the upload row in my db AFTER the S3 upload creation (e.g. creation of the .info file) is completed. This code is inside post-create. Thereafter, if my db row writing fails, I would like the entire request to die and notify client that everything didn't go through. It's ok that I have a dangling S3 .info file as the file system is not the source of truth but my db is.
This means that if we assume tusd lives inside another app, I am not sure how this implementation can promote atomicity. S3 (or any other store for that matter) can fail and db writing can fail too. The writing to S3 only occurs after pre-create too.
My workaround: I am trying to sandwich tusd as some sort of middleware inside gin so that after the tusd handler is done, my gin context takes over and send a 400 or 500 in case my db writing inside post-create fails. But it seems impossible to be able to do this as the post-create hook does not have any access at all to the original http handler's context. So I cannot pass anything down to the next handler. I also cannot insert something like a channel as I cannot find any place where this channel can be passed into the hook or later accessed again outside of the hook.
Please correct me if I am wrong. Any suggestions highly welcome! Thank you.
PS: I have made quite a number of questions and would be keen to contribute PRs with your guidance.

As you said correctly and as is mentioned explicitly in the docs at https://github.com/tus/tusd/blob/main/docs/hooks.md#list-of-available-hooks, post-create is non-blocking and therefore tusd does not wait for its completion before sending the response. Basically, what you are trying to do right now is not possible yet. I would recommend you to restructure your hooks implementation to create the DB entry in the pre-create hook, but mark it as preliminary. Preliminary meaning that the actual objects on S3 might not be created. But when the post-create, post-finish or post-receive hooks arrive you can start marking it as non-preliminary. Not the best solution, but something :)
I wonder how this could be improved in the future. The current design where post-create is delivered via a channel does not allow tusd to wait on the hook's completion.

Those are interesting concepts, thanks for sharing. When talking about hooks and events, we always have to consider two use cases: Using tusd as a package where events can be delivered via channels or function calls. And using tusd as a stand-alone program where hooks usually require contacting an external program. That makes it sometimes a bit more challenging to find a suitable approach for new hooks features :)


ref(getter): flatten the getter package tree

This flattens the getter package tree, adds tests, and changes a little
bit of the terminology to follow Go idioms. This also makes much of the
getter API private to begin with. This will give us more flexibility in
the future.

Along the way of improving tests, found an error in urlutil.go, fixed, and added tests.


consume stream from .map() ?

import HL from 'highland';
let files = ['a','b'];

    HL(files)
      .map(file => {
        let s = request(file).pipe(request.put({
          url: 'http://myserivce',
          headers: { 'Accept': 'text/plain' }
        }));
        return HL(s);
      })
      .series()
      .each(res => console.log(res); );

I'll never reach the .each func, do i anything wrong here?

Is request.put also a Readable or just a Writable? If it's just a Writable, you can't wrap it in a Highland stream. See the discussion in #444 for how to get around that.

It should be a also a Writeable stream.
I did some refactoring and it works now but i couldnt find out why.
Thanks anyway!


Update consistency level for cassandra visibility

What changed?
Use local_one consistency instead of one

Why?
In a multiple datacenter clusters, a consistency level of ONE is often desirable, but cross-DC traffic is not. LOCAL_ONE accomplishes this.

How did you test it?

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 0188dfb7-f47f-4477-8445-6883a141273c

0 of 0   changed or added relevant lines in 0 files are covered.
122 unchanged lines in 24 files lost coverage.
Overall coverage increased (+0.04%) to 57.342%

Files with Coverage Reduction
New Missed Lines
%

common/persistence/executionManager.go
2
78.94%

common/persistence/nosql/nosqlplugin/cassandra/gocql/consistency.go
2
46.67%

common/persistence/nosql/nosqlplugin/cassandra/tasks.go
2
75.57%

common/persistence/statsComputer.go
2
95.71%

common/task/fifoTaskScheduler.go
2
85.57%

common/task/parallelTaskProcessor.go
2
93.06%

common/task/weightedRoundRobinTaskScheduler.go
2
89.12%

common/util.go
2
53.73%

service/history/handler.go
2
47.28%

service/history/task/transfer_active_task_executor.go
2
72.24%

Totals

Change from base Build 0188d7c9-fb87-419e-b893-61f23adef50c:
0.04%

Covered Lines:
87190

Relevant Lines:
152053

💛  - Coveralls


[rov.2020.3] Add ONNX Slice-10 operator

Do we have an OpenVINO e2e tests passed with this version of nGraph?

Do we have an OpenVINO e2e tests passed with this version of nGraph?

I've just created a MR #7284 - can you please have a look and run the CIs that didn't start automatically?


[MPLUGIN-372] Descriptor mojo fails if super class is provided scope

https://issues.apache.org/jira/browse/MPLUGIN-372
Changes:

Bug: adjust descriptor mojo resolution scope to include provided scope as well
drop use of deprecated project.getRuntimeDependencies()
Sanitized generator and report mojos (injects both project and project.artifacts, just one is completely enough)
GeneratorUtils using Artifacts not Dependencies (as they were not needed)
JavaAnnotationsMojoDescriptorExtractor error reporting: report failed class at least

This change should be addressed, as it is crucial to put plugins maven deps to provided.

By just looking at the code I don't see weird things. This ticket confirms my feeling that there was something wrong, but I can't see the impact yet. I guess you can see only the difference if MNG-7097 is ready.

@rfscholte for the rest of your comments: well, as it can be seen, these are all uses of org.apache.maven.project.MavenProject#getArtifacts method, which in turn has JavaDoc saying "All dependencies that this project has...". Also, old (removed) code was calling it "dependencies", so I did not change that. The util class is aligned though.

ping

merged as 8f354439765afdbf6ce166d299791117576e90f2