Feature: download files

Description
Add the capability to download files from a running container.
Resolves #48

This implementation is pretty bare bones: it blocks while downloading. This could cause problems with many concurrent users or very large repo's.
The download mechanism is streaming. It does not store the download somewhere in the middle.
It currently downloads a tar. Not sure if Windows explorer knows how to handle those.
Download is only on folder level (as implemented by @henrik997). File level downloads should be easy. You'll still get a tar.

Testing
Backend calls have been unit tested (with mock). Frontend has manually been checked.
Checklist

[x] My code follows the guidelines of this project: CONTRIBUTING.md
[ ] I updated the documentation with the new functionality
[x] I went through the code and removed all print statements, breakpoints and unused code
[ ] Error handling for all possible scenarios has been implemented
[x] I've add logging for all relevant operations
[x] I added the appropriate labels to this PR (enhancement/bug/documentation, effort, priority)

This implementation is pretty bare bones: it blocks while downloading. This could cause problems with many concurrent users or very large repo's.

Indeed, this could be an issue and there doesn't seem to be asynio support for the kubernetes-client python library: https://github.com/kubernetes-client/python/issues/323. This is another argument for using our custom file service inside the session container.

It currently downloads a tar. Not sure if Windows explorer knows how to handle those.

As far as I can see, it uses zip now. This should be fine for Windows users.

The implementation doesn't seem to work with large files unfortunately. I just tried it out with our largest model (~1GB), but the downloaded zip seems to be corrupted:
> unzip download\ \(5\).zip
Archive:  download (5).zip
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of download (5).zip or
        download (5).zip.zip, and cannot find download (5).zip.ZIP, period.

Version v2 branch is in #274


cmd/vet: decide on support for type parameters in the printf analyzer

This is a separate issue from #48704, because we need to make a non-trivial decision about the printf analyzer for 1.18.
The printf analyzer has come up several times in the context of updating tools for generics, because it is an example of where we might want to interrogate the type set of a type parameter -- see below.  After going back-and-forth, in my opinion we should be conservative and treat type parameters like interfaces, at least for 1.18.
For discussion, consider the following examples:
// Example 1
func _[T ~int](t T) {
  fmt.Printf("%s", t)  // is this a mismatching verb? t might be a fmt.Stringer.
}

// Example 2
func _[T any](t T) {
  fmt.Printf("%d", t)  // t might be integral, or a fmt.Formatter
}

// Example 3
func _[T int|float64](t T) {
  fmt.Printf(“%s”, t)  // this is provably an error
}

In all of these examples, there are elements of the type parameter type set that do not match the printf verb being used, but in Examples 1 and 2 there may be false positives:

In Example 1, the type argument must have int underlying, which doesn’t match %s, but we don’t know if it implements fmt.Stringer or fmt.Formatter.
In Example 2, the type argument can be any type, and we don’t know if it is integral, or a fmt.Formatter.
In Example 3, the type set is finite and we can prove that no type argument matches %s.

In the future we may want to report diagnostics in all three examples, but in the interest of caution I think we should allow all three for 1.18.  Vet has very high standards for avoiding false positives, and in Examples 1 and 2, the following  advice about interfaces from the printf source applies:

// Whether any particular verb is valid depends on the argument.
// The user may have reasonable prior knowledge of the contents of the interface.

We could reasonably produce a diagnostic just for Example 3, but I think it will probably be uncommon to have a finite type set, and it is OK to miss this true positive in the interest of simplifying the implementation.
The counter argument to doing nothing is that with the new embedded elements in interfaces, we can now express type sets more precisely and it is more likely that a mismatching verb is actually a user error.  There is some precedent here, in both directions:

we warn about arguments of interface type that did not implement error for %w (cf. #48931)
…but removed diagnostics for other verbs with arguments of interface type, as we can’t know if their dynamic type implements fmt.Formatter (cf. #36564).

This counter argument is compelling, and I think we should consider adding these diagnostics for 1.19 -- in fact I prototyped this in CL 351832 -- but for 1.18 in particular I am concerned that we don’t have a good understanding of how generics will be used, particularly when updating existing code, and having opinionated vet checks here may get in the way.
Regardless, I think this needs to be discussed (hence the issue).
CC @timothy-king @scott-cotton @mvdan

In my opinion:

Example 1 should emit a warning, because the type parameter may be instantiated with a type that does not implement fmt.Stringer, and for such parameters the format string is wrong.
Similarly for example 2. The warning should be suppressed only if every valid instantiation of T matches the formatting verb.

While it is true that “the user may have reasonable prior knowledge of the contents of an interface”, it is also the case that type sets can provide much more precision than interface types, and I think vet should make use of that extra precision.

Closing this as the associated proposal was accepted and implemented.


Incorrect agent result

null or an empty string are 2 user agent cases for bad bots. Nice to handle them too

Thanks for taking the time to report this.
I'm not entirely sure that assuming null and empty string are bots is a good idea. I agree in most cases they will probably be bots, but i think a lot of guess work is happening here. We only want to detect bots that specifically say they are a bot.
Thanks


Bug: Global and a filetype-specific LazyKey mapping for the same key disable each other

Did you check docs and existing issues?

[X] I have read all the lazy.nvim docs
[X] I have searched the existing issues of lazy.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.9.4
Operating system/version
macOS 14.1 (arm)
Describe the bug
This bug is related to the filetype-specific LazyKeys (#1076).
When setting two lazy keys, one global (without ft = …) and one for a buffer (with ft = …), activating one of them disables the other. While this makes somewhat sense for global keymaps to avoid conflicting keymaps, it is indeed often useful to modify the behavior of one keymap for a specific filetype. The current lazy.nvim behavior, however, prevents setting up such keymaps.
Steps To Reproduce

Add this to any plugin spec:

keys = {
	{ "R", function() print("global") end},
	{ "R", function() print("local") end, ft = "lua"},
},

Enter a lua file. Press R.
Enter a non-lua file. Press R.

Expected Behavior
the keymaps should not disable each other
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
	{
		"folke/tokyonight.nvim",
		keys = {
			{ "R", function() print("global") end },
			{ "R", function() print("local") end, ft = "lua" },
		},
	},

}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Thanks for the fix!
Unfortunately, it does not seem to be working. As far as I can tell, it appears that now the global LazyKey is now completely ignored (using :Telescope keymap, the global mapping does not appear at all, only the buffer-local mapping does when in a buffer of the respective filetype.).
Also, when there is a filetype-specific LazyKey and a global keymap done independently from lazy, the global keymap is removed as soon as the LazyKey is triggered.

You were right. If the local mapping was used first, the global one got deleted.
Should be fixed now. (will make a new release later)
If not, please provide a repro like your original one and the steps to reproduce it.


V2 - Corporate Console - Not able to add github username with hyphen in approval list

@sudhakar-proxima
Prerequisite

Create CLA Group with CCLA enabled
Sign CLA from corporate console

Steps to follow

Trigger below endpoint to add approval list with github username having special character
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/updateApprovalList
Below is the criteria provided by github for username

Found Working fine hence marking as closed. Please refer screencast attached for more details.


Dylan Graves / DS-Unit-1-Sprint-2-Data-Wrangling

Awesome Job Dylan!

try declaring your value_counts() as a variable and then you can use .head(10) to get the top ten.


doom upgrade issues

What did you expect to happen?
doom upgrade (no args) to run
What actually happened?
doom upgrade errors out

> Preparing to upgrade Doom Emacs and its packages...
x There was an unexpected error:
  Type: error
  Message:
    error
  Data:
    "Failed to fetch from upstream"
Run the command again with the -d (or --debug) switch to enable debug
mode and (hopefully) generate a backtrace from this error:
doom -d upgrade
If you file a bug report, please include it!

Steps to reproduce:

run bin/doom upgrade from the command-line

System information:

emacs   version    26.3
        features   NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS MODULES THREADS LCMS2
        build      Apr 24, 2020
        buildopts  (--enable-locallisppath=/usr/local/share/emacs/site-lisp --infodir=/usr/local/Cellar/emacs-mac/emacs-26.3-z-mac-7.9/share/info/emacs --prefix=/usr/local/Cellar/emacs-mac/emacs-26.3-z-mac-7.9 --with-mac --enable-mac-app=/usr/local/Cellar/emacs-mac/emacs-26.3-z-mac-7.9 --with-gnutls --with-modules)
        windowsys  mac
        daemonp    server-running
doom    version    2.0.9
        build      HEAD -> develop, seanfarley/develop, origin/develop, origin/HEAD ee5d0a878 2020-05-26 16:28:59 -0400
        dir        ~/projects/dotfiles/doom/
system  type       darwin
        config     x86_64-apple-darwin18.7.0
        shell      /usr/local/bin/bash
        uname      Darwin 18.7.0 Darwin Kernel Version 18.7.0: Tue Aug 20 16:57:14 PDT 2019; root:xnu-4903.271.2~2/RELEASE_X86_64 x86_64
        path       (~/.local/bin ~/.cargo/bin ~/projects/go/bin ~/Library/Python/3.7/bin ~/.npm/bin /opt/X11/bin /usr/local/bin /usr/local/sbin /usr/local/cuda/bin /usr/local/share/dotnet /usr/local/opt/coreutils/libexec/gnubin /usr/local/opt/make/libexec/gnubin /usr/local/opt/texinfo/bin /usr/local/Cellar/qt/5.14.2/bin /Library/TeX/texbin /usr/bin /bin /usr/sbin /sbin /usr/local/Cellar/emacs-mac/emacs-26.3-z-mac-7.9/libexec/emacs/26.3/x86_64-apple-darwin18.7.0/)
config  envfile    envvar-file
        elc-files  0
        modules    (:completion (company +auto +childframe) (ivy +childframe +icons +prescient) :ui doom doom-dashboard fill-column hl-todo indent-guides modeline nav-flash ophints (popup +all +defaults) pretty-code treemacs vc-gutter vi-tilde-fringe window-select workspaces zen :editor file-templates fold multiple-cursors (objed +manual) rotate-text snippets word-wrap :emacs (dired +icons) electric ibuffer undo vc :term vterm :checkers (syntax +childframe) spell grammar :tools ansible biblio debugger docker editorconfig eval gist (lookup +docsets +dictionary) lsp macos (magit +forge) make pdf prodigy upload :lang (cc +lsp) clojure common-lisp data emacs-lisp go hy (javascript +lsp) (latex +latexmk) lua markdown (org +brain +dragndrop +gnuplot +hugo +journal +jupyter +pandoc +pomodoro +present +roam) (python +cython +lsp) rest rst sh (swift +lsp) web :email mu4e :app irc :config (default +bindings +smartparens +snippets))
        packages   ((banner-comment) (bitwarden :recipe (:host github :repo seanfarley/emacs-bitwarden)) (col-highlight :recipe (:host github :repo emacsmirror/col-highlight)) (color-identifiers-mode) (counsel-jq) (discover-my-major) (dot-mode) (easy-hugo) (elisp-slime-nav) (embrace) (emr) (fancy-narrow) (focus) (goto-chg) (ialign) (lsp-focus :recipe (:host github :repo emacs-lsp/lsp-focus)) (lsp-origami) (lsp-treemacs) (magit-circleci) (mpdel) (ivy-mpdel) (mu4e-alert) (mu4e-patch :recipe (:host github :repo seanfarley/mu4e-patch)) (nerd-font :recipe (:host github :repo twlz0ne/nerd-fonts.el)) (nov) (org-ref) (package-lint) (page-break-lines) (pony-mode) (resize-window) (simple-httpd) (simple-mpc :recipe (:local-repo ~/projects/simple-mpc)) (sly-quicklisp) (sphinx-doc) (srefactor) (sx) (unfill) (webpaste) (whole-line-or-region) (which-key-posframe) (xonsh-mode :recipe (:host github :repo seanfarley/xonsh-mode)) (ztree))
        unpin      (n/a)
        elpa       (n/a)

Running with -p successfully runs. I tried to send that argument (manually) to M-x doom/upgrade from within emacs but got this error (in *Messages*):
Comint finished
error in process sentinel: progn: Symbol’s value as variable is void: doom-sync-window
error in process sentinel: Symbol’s value as variable is void: doom-sync-window

I'm having the same issue on macOS. I'm on commit
* 7ed96590e (HEAD -> develop, origin/develop) Fix #3232: wrong-type-argument arrayp error

Error
~/.emacs.d/bin(develop ✔) ./doom -d upgrade
- Debug mode on
> Preparing to upgrade Doom Emacs and its packages...
x There was an unexpected error:
  Type: error
  Message:
    error
  Data:
    "Failed to fetch from upstream"

Run the command again with the -d (or --debug) switch to enable debug
mode and (hopefully) generate a backtrace from this error:

  doom -d upgrade

If you file a bug report, please include it!

System Info
emacs   version    26.3
        features   JPEG RSVG IMAGEMAGICK GLIB NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS LCMS2
        build      Sep 02, 2019
        buildopts  (--disable-dependency-tracking --disable-silent-rules --enable-locallisppath=/usr/local/share/emacs/site-lisp --infodir=/usr/local/Cellar/emacs-plus/26.3/share/info/emacs --prefix=/usr/local/Cellar/emacs-plus/26.3 --with-xml2 --without-dbus --with-gnutls --with-imagemagick --with-modules --with-rsvg --with-ns --disable-ns-self-contained)
        windowsys  ns
        daemonp    server-running
doom    version    2.0.9
        build      HEAD -> develop, origin/develop 7ed96590e 2020-05-26 21:45:31 -0400
        dir        ~/.doom.d/
system  type       darwin
        config     x86_64-apple-darwin18.7.0
        shell      /bin/zsh
        uname      Darwin 18.7.0 Darwin Kernel Version 18.7.0: Mon Feb 10 21:08:45 PST 2020; root:xnu-4903.278.28~1/RELEASE_X86_64 x86_64

I had the same problem. Solved it by killing the Doom directory and reinstalling it following the installation guide. You can save everything in .local except for .local\straight.

Those are some strange errors, but it could be due to some breaking changes in the upgrader across versions. Older versions of Doom would naively just reload Doom core (in the same session) after pulling it, which is problematic if the code has changed drastically.
In newer versions of Doom, we rerun the whole command after pulling Doom, but folks upgrading from fairly old versions are likely to see errors.
If all else fails, try upgrading manually (it'll at least save you the pain of reinstalling everything from scratch.
cd ~/.emacs.d
git pull
doom sync -u

I'm not sure how I'd be running old versions of doom since I (almost) daily upgrade doom? I've just recently git pull --rebase and after a clean run of doom sync I'm still seeing this error.
Side request: can we get a version of M-x doom/upgrade (or doom/sync) that can take a parameter to only upgrade packages? Maybe C-u M-x doom/upgrade?

I tried git pull --rebase, then doom sync -u and am now still getting this error since last doom upgrade performed 8 hours ago:
> Synchronizing your config with Doom Emacs...
  > Regenerating envvars file at "~/.emacs.d/.local/env"
    - Ignoring HOME=/Users/yeongsheng
    - Ignoring PWD=/Users/yeongsheng/.emacs.d
    - Ignoring __CF_USER_TEXT_ENCODING=0x1F5:0x0:0x64
    - Ignoring SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.r2JxdiQ5eI/Listeners
    - Ignoring TERM=screen-256color
    ✓ Successfully generated "~/.emacs.d/.local/env"
  > Installing packages...
    → Building vue-mode...
    → Building vue-mode → Building mmm-mode...
x There was an unexpected error:
  Type: doom-package-error
  Message:
    Error with packages
  Data:
    "vue-mode"
    (error "mmm-class.el:0:0: error: scan-error: (Unbalanced parentheses 7955 12984)")

Run the command again with the -d (or --debug) switch to enable debug
mode and (hopefully) generate a backtrace from this error:

  doom -d sync -u

If you file a bug report, please include it!

Running doom -d sync -u generates the same error stack.

@yeongsheng-tan Please open a new issue. Your error is different from OP's. Please remember to include your M-x doom/info, as I cannot reproduce it.

"Failed to fetch from upstream"

@seanfarley What happens if you run these shell commands:
cd ~/.emacs.d
git remote add _upgrade https://github.com/hlissner/doom-emacs
git fetch --tags _upgrade develop

git remote add _upgrade https://github.com/hlissner/doom-emacs
git fetch --tags _upgrade develop

I get the following error when performed above commands:
> Preparing to upgrade Doom Emacs and its packages...
x There was an unexpected error:
  Type: error
  Message:
    error
  Data:
    "Failed to fetch from upstream"

Run the command again with the -d (or --debug) switch to enable debug
mode and (hopefully) generate a backtrace from this error:

  doom -d upgrade

If you file a bug report, please include it!

Closing this and re-opened as new issue at https://github.com/hlissner/doom-emacs/issues/3248

I did a rm -rf ~/.emacs.d and re-installed doom but I still get the same error.
I checked ~/.emacs.d/core/cli/upgrade.el and it seems
(or (zerop (car (setq result (doom-call-process "git" "fetch" "--tags" doom-repo-remote branch))))

Results in the execution of
~/.emacs.d/bin(develop ✗) git fetch --tags _upgrade remotes/origin/develop
fatal: couldn't find remote ref remotes/origin/develop

However running
~/.emacs.d/bin(develop ✗) git fetch --tags _upgrade develop
From github.com:hlissner/doom-emacs
 * branch              develop    -> FETCH_HEAD
 * [new branch]        develop    -> _upgrade/develop

Does seem to work.
I am on git version
~/.emacs.d/bin(develop ✗) git --version
git version 2.26.2

Dang. That seemed like it was going to work but it's the same error as @drayah (I'm on the same git version). I've also noticed that _upgrade is deleted after running (and failing) bin/doom upgrade.

What does git name-rev --name-only HEAD output from ~/.emacs.d?

$ cd ~/.emacs.d
$ git name-rev --name-only HEAD
remotes/origin/develop

Same result here

Give aec94f5 a try. I'm not sure if this is a difference between git 2.25 (what I have) and 2.26, or if there's an edge case where git name-rev outputs a fully qualified ref, but aec94f5 should deal with it. Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!

🎉 🥳 🎆  (just in case it wasn't obvious: aec94f5 worked!)

I had symptoms of the same issue - Failed to fetch from upstream - that led me here.
In my case, I recently globally configured git to use ssh instead of http using
git config --global<EMAIL_ADDRESS>https://github.com and forgot I had done so.
Removing the two lines this added to ~/.gitconfig resolved the issue.

I had a similar issue. My problem was that I had rogue _upgrade_develop branch, probably from a crashed upgrade, that was confusing the sequence of git commands to do the upgrade. Removing the branch fixed it for me.


Counter shows incorrect value in SQL Editor

System information:

Operating system (distribution) and version win10 x64
DBeaver version 7.0.1 EA

Describe the problem you're observing:
Counter shows incorrect value in SQL Editor.
Steps to reproduce, if exist:

Open SQL Editor
Execute script (e.g. select 1; select 2; select 3; )using Alt+X - 3 tabs+ Statistic appears
Try to execute script once again - Confirmation pop-up appears. Number of unpinned tabs is incorrect. Probably value is number of open tabs+number of tabs that will be open

Duplicate of #8189

Reopened. #8189 is about the incorrect translation to Russian.
This ticket is about Incorrect value in counter

Yep.
Fixed

verified


fix: move port validation and waiting logic into proxy server

Move wait for port logic into the proxy.

Running swa start http://localhost:3000 --run "npm:start" --app-location frontend now works properly
Moving the wait for API to just before starting the proxy means most of the function app output now prints before the proxy starts. This ensures that this message will no longer be hidden by the function app output:[swa] Available on:
[swa]     http://<IP_ADDRESS>:4280
[swa]     http://<IP_ADDRESS>:4280
[swa]
[swa] Azure Static Web Apps emulator started. Press CTRL+C to exit.

LGTM.


Closes #322

The functionality outlined in the issue #322 has been implemented. Haven't really nailed the UI looks. Would require some refining by a Frontend developer with an eye for style.\
Change 1

Change 2

In progress #661


Mlflow test

I used the default mlruns file store and I created a test to ensure the mlruns folder is removed. I tried to cover all the tests you requested. If there's anything I should change, just give me a shout.
I'm trying to get a docker container running with the mlflow server and a backend. I do think it's going to take a bit of time to figure out though because I'm not too clued up with docker. So hopefully these tests are ok for now.

Ey, this is looking good! 🚀
As you mentioned, probably the way to go is using docker, to avoid unexpected writes/deletes on local file systems, this is a breakthrough so I'll merge it, but if you agree, I'll leave the issue #30 open for now with a note.
I have some experience with docker, so this is what I can tell:

We should use a base image from python official docker hub, probably a slim version to make it light https://hub.docker.com/_/python
To exec the test inside the running container, we can use docker exec -it {test command}, the full command must be the one from github actions Tests
Here is a demo example with something similar I made
We have to check how to handle the current tests as they run in different O.S and python version to check compatibility, or we could try to run just this set of test on the container and remain the others as it is.

Thanks again!

Ok awesome, I've done a bit of the ground work so you can definitely leave it open. I'm trying to use testcontainers to run a container for the tests. I need to fix the setup and your demo looks like it'll be a lot of help, thanks! With the testcontainers I think we could just spin it up for the MLflow integration like this. So if I'm not mistaken that'll help with the last point?
It's a pleasure 💪🏽  I've been hunting for something to contribute to so I should be thanking you 😄

That looks interesting, I didn't know that package, it's worth to give it a try; it could help with the last point if the package itself has support for python 3.7+, Windows, Linux an MacOS, or the pip install would make the test fail
Awesome, I'm glad you got interested in this project, hope to keep seeing you around! 👍🏼


Update _redirects.htaccess

Description of the change: Updated source/_redirects.htaccess
Reason for the change: To fix broken redirects
Link to original source: https://github.com/sendgrid/docs/blob/develop/source/_redirects.htaccess
Closes #3215
Sorry for the erroneous pr #3220. I closed it.
@ksigler7

@Xndr7 thanks for taking this on and also for fixing it when the redirect deduplicator failed the build!

Hello @Xndr7,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Make subtitle capitalization consistent

"Pet Teleports" and "Dragon Egg Teleports" should be changed to "Pet teleports" (or perhaps mob-specific subtitles) and "Dragon Egg teleports" to be consistent with existing subtitles such as "Player teleports" and "Fox teleports".

Just released a commit that fixes the capitalization, never realized they were different lol.
As for the other suggestion, It may be a bit difficult as all pets teleport to you using the same method, but I’ll look into it


Origin/nr/dashboard

blablabla (to fill)

closing because was done as an example-- @noemieroberge will open a new one


Image compression doesn't work on iPhones

Uploading images on iPhones/iPads will work without compression, but uploading a 10MB image won't do.

I think I figured out the problem for the image compression but I don't have an iphone to test it. The problem is that mobile iOS has a limit to the height and width of a canvas.
 iPod Touch 16GB = 1448x1448
 iPad Mini       = 2290x2289
 iPhone 3        = 1448x1448
 iPhone 5        = 2290x2289
'''

Our code right now is setting the canvas dimensions to the photo dimensions.

It seems like the iphone's photo dimensions are larger than the max limit of the canvas dimensions. To solve this issue, the width and height of the canvas needs to be set smaller. When we draw the image on to the canvas, we also need to reduce the photo dimensions. Syntax for canvas drawing is:
var ctx = cvs.getContext("2d").drawImage(source_img_obj, 0, 0);

The code for drawing should go from :
'''
var cvs = document.createElement("canvas");
cvs.width = source_img_obj.width;
cvs.height = source_img_obj.height;
var ctx = cvs.getContext("2d").drawImage(source_img_obj, 0, 0);
'''
to:
'''
var cvs = document.createElement("canvas");
// will need to figure out best dimensions to scale down to
cvs.width = 2000;
cvs.height = 2000;
var ctx = cvs.getContext("2d").drawImage(source_img_obj, 0, 0, 2000, 2000);
'''

Super helpful, @hansoncyu ! Thanks for the detective work here. I have an iPhone 5 at home I can test with later.


Update certificate concepts doc, clarifying lack of root in tls.crt

Also contains other minor changes including grammar, removing trailing
whitespace and some small rewording.
Signed-off-by: Ashley Davis<EMAIL_ADDRESS>

/lgtm


Copy XPath is missing

The inspector panel should have a "Copy XPath selector" in its contextual menu.
Reported here: https://bugzil.la/987877
Florent

Should be implemented on the platform.
Honza


[BUG] TPCH test with exception: Filesystem closed

Describe the bug
I use blaze for TPCH testing, the execution is abnormal, is TPCH testing not supported now? Thank you
**Error log information **
3/10/11 16:01:41 INFO Executor: Finished task 5.0 in stage 5.0 (TID 421). 3033 bytes result sent to driver
23/10/11 16:01:41 ERROR TaskContextImpl: Error in TaskCompletionListener
java.lang.RuntimeException: native executing [partition=3] panics: Execution error: Execution error: output_with_sender[Filter] error: Execution error: output_with_sender[ParquetScan] error: Execution error: output_with_sender[ParquetScan]: output() returns error: Parquet error: External: External error: Java exception thrown at native-engine/datafusion-ext-commons/src/hadoop_fs.rs:77: Filesystem closed
23/10/11 16:01:41 ERROR Executor: Exception in task 9.0 in stage 5.0 (TID 425)
java.lang.RuntimeException: native executing [partition=9] panics: Execution error: Execution error: output_with_sender[Filter] error: Execution error: output_with_sender[ParquetScan] error: Execution error: output_with_sender[ParquetScan]: output() returns error: Arrow error: External error: External: External error: Java exception thrown at native-engine/datafusion-ext-commons/src/hadoop_fs.rs:77: Filesystem closed
23/10/11 16:01:41 ERROR Executor: Exception in task 3.0 in stage 5.0 (TID 419)
org.apache.spark.util.TaskCompletionListenerException: native executing [partition=3] panics: Execution error: Execution error: output_with_sender[Filter] error: Execution error: output_with_sender[ParquetScan] error: Execution error: output_with_sender[ParquetScan]: output() returns error: Parquet error: External: External error: Java exception thrown at native-engine/datafusion-ext-commons/src/hadoop_fs.rs:77: Filesystem closed
	at org.apache.spark.TaskContextImpl.invokeListeners(TaskContextImpl.scala:206)
	at org.apache.spark.TaskContextImpl.invokeTaskCompletionListeners(TaskContextImpl.scala:143)
	at org.apache.spark.TaskContextImpl.markTaskCompleted(TaskContextImpl.scala:136)
	at org.apache.spark.scheduler.Task.run(Task.scala:152)
	at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:548)
	at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1504)
	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:551)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:750)
23/10/11 16:01:41 INFO CoarseGrainedExecutorBackend: Got assigned task 446
23/10/11 16:01:41 INFO Executor: Running task 9.1 in stage 5.0 (TID 446)
23/10/11 16:01:41 INFO CoarseGrainedExecutorBackend: Got assigned task 447
23/10/11 16:01:41 INFO Executor: Running task 3.1 in stage 5.0 (TID 447)
23/10/11 16:01:41 INFO BlazeCallNativeWrapper: Start executing native plan
23/10/11 16:01:41 INFO BlazeCallNativeWrapper: Start executing native plan
23/10/11 16:01:41 INFO Executor: Finished task 3.1 in stage 5.0 (TID 447). 3033 bytes result sent to driver
23/10/11 16:01:41 ERROR Executor: Exception in task 9.1 in stage 5.0 (TID 446)
java.lang.RuntimeException: native executing [partition=9] panics: Execution error: Execution error: output_with_sender[Filter] error: Execution error: output_with_sender[ParquetScan] error: Execution error: output_with_sender[ParquetScan]: output() returns error: Arrow error: External error: External: External error: Java exception thrown at native-engine/datafusion-ext-commons/src/hadoop_fs.rs:77: Filesystem closed
23/10/11 16:01:41 INFO ShuffleBlockFetcherIterator: Getting 2000 (517.0 KiB) non-empty blocks including 0 (0.0 B) local and 2000 (517.0 KiB) host-local and 0 (0.0 B) push-merged-local and 0 (0.0 B) remote blocks
23/10/11 16:01:41 INFO ShuffleBlockFetcherIterator: Started 0 remote fetches in 70 ms
23/10/11 16:01:41 INFO CoarseGrainedExecutorBackend: Got assigned task 451
23/10/11 16:01:41 INFO Executor: Running task 17.1 in stage 5.0 (TID 451)
23/10/11 16:01:41 INFO BlazeCallNativeWrapper: Start executing native plan
23/10/11 16:01:41 INFO Executor: Finished task 17.1 in stage 5.0 (TID 451). 3033 bytes result sent to driver
23/10/11 16:01:42 INFO Executor: Finished task 4.0 in stage 7.0 (TID 440). 381619 bytes result sent to driver

To Reproduce
My CPU information：Intel(R) Xeon(R) Gold 6130 CPU
software: Spark 3.3.3 Hive:3.1.2 Hadoop 3.2.0
Spark Conf is the base configuration！
DataFormat：Parquet

@richox @yjshen thanks！

please try the config fs.hdfs.impl.disable.cache true

maybe we should stop closing hadoop fs in parquet scan operator

please try the config fs.hdfs.impl.disable.cache true

It didn't work，Is there a description of the types of data formats that Blaze supports now? and I would know the data sources that Blaze currently supports? For example, HBASE, etc

please try the config fs.hdfs.impl.disable.cache true

It didn't work，Is there a description of the types of data formats that Blaze supports now? and I would know the data sources that Blaze currently supports? For example, HBASE, etc

it's my fault, you would likely to try spark.hadoop.fs.hdfs.impl.disable.cache true.
currently only parquet is supported.

maybe we should stop closing hadoop fs in parquet scan operator
this behavior is known to cause "FileSystem closed" in some hadoop versions.

I think yes. The fs instance still exists although the fs is closed. Do you mind I raise a PR to fix this?

maybe we should stop closing hadoop fs in parquet scan operator
this behavior is known to cause "FileSystem closed" in some hadoop versions.

I think yes. The fs instance still exists although the fs is closed. Do you mind I raise a PR to fix this?

yes, of course.
and also remove the destructor in hadoop_fs.rs.

please try the config fs.hdfs.impl.disable.cache true

It didn't work，Is there a description of the types of data formats that Blaze supports now? and I would know the data sources that Blaze currently supports? For example, HBASE, etc

it's my fault, you would likely to try spark.hadoop.fs.hdfs.impl.disable.cache true. currently only parquet is supported.

It worked, thank you！


Total Cost $/Total cost shares shows incorrect data with existing short position

I sell 30 of outcome A so I have a short position of 30 @0.26

I add an open order to sell 150 shares of outcome B @0.8
My Open orders shows shows a total cost of 24.000 and total cost for shares of 30

need to think how to differentiate if user is short other outcome or long the order outcome. Need to discuss. not working until algo is figured out.

fixed - closing


METRON-829 Use Fastcapa with Kerberos

Yes, you can use Fastcapa with Kerberos with no code change.  I describe the entire process in the README.
This PR is dependent on #509 which explains the extra commits that are currently visible.
Pull Request Checklist

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.

[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[x] Have you included steps or a guide to how the change may be verified and tested manually?

[x] Have you ensured that the full suite of tests and checks have been executed in the root incubating-metron folder via:

[x] Have you written or updated unit tests and or integration tests to verify your changes?

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

[x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
bin/generate-md.sh
mvn site:site

#511 should be in master.

@JonZeolla I notice that the rendering of the code under the following text looks wonky.  Although, I have no idea why.  Any thoughts?

Ensure that the device was bound. It should be shown as a “network device using DPDK-compatible driver.”

Ah, I missed that, I was only reviewing the Kerberos section from the two commits.
It's because there are indented blank lines in the code block.  That's a known issue, if you remove the indentation or the empty lines it should fix it.

That was it.  Thanks @JonZeolla !

@cestella I had thought that the setup for the Bro Plugin (the work you did in #501) would be almost the same as the setup for Fastcapa.  My assumption was wrong though.  I had to create a JAAS configuration file which I don't see in the instructions that you created for the Bro Plugin.  Any idea why you didn't need to do that?  Are my instructions incorrect?

That shouldn't be required as librdkafka doesn't know anything about JAAS since JAAS is a Java thing and librdkafka is decidedly not.  It does ticket renewal literally by having you specify the keytab and the kinit command (the default one works).  I validated that by botching the kinit command in the librdkafka config and having it scream bloody murder in the logs periodically and stop working.

@cestella Thanks.  Duh. That makes sense.
Thinking back, I probably just needed the JAAS stuff since I was trying to test with the Kafka Console Producer before landing data with Fastcapa.  I'll work through the steps again and remove the JAAS stuff so as not confuse the instructions.

Ok.  The instructions should be ready-to-go now.

@nickwallen kick travis; that's an intermittent error.

+1 by inspection

Kicking Travis


How to get total distance travel by GT06 protocol based device

Hi @tananaev
How can I get total distance travel by device. I am using GT06 protocol based device.
I have gone through with database and find there is no field in database for total distance,
Can you please let me know.
Looking forward your reply.

You need to enable distance calculation in the config.


OMI version v1.6.10-2 missing from the repository

Details about the release: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-33640

I noticed the branch for that, do you have eta for PR and merge?


Add Bitwise operation

@mattn please help to review this PR

@doug-martin fixed lint, please re-run the CI

@XIELongDragon re-ran to get the output from golang ci, the issues are not annotated in the PR.


OmniSharp invalid CIL

From @darkoverlordofdata on October 28, 2016 20:27

VSCode Version: 1.6.1
OS Version: elementary OS 0.4 Loki (64-bit) - Built on "Ubuntu 16.04 LTS"

Steps to Reproduce:

Followed instructions at https://www.microsoft.com/net/core#ubuntu
Restart VSCode

Get the following output:
Starting OmniSharp server at 10/28/2016, 1:22:37 PM
Target: /home/bruce/Downloads/WindowsExplorer_C/WindowsExplorer_C.sln
OmniSharp server started wth Mono
Path: /home/bruce/Applications/omnisharp-ubuntu16-x64-netcoreapp1.0/OmniSharp
PID: 23323
Cannot open assembly '/home/bruce/Applications/omnisharp-ubuntu16-x64-netcoreapp1.0/OmniSharp': File does not contain a valid CIL image.
[ERROR] Error: Failed to start OmniSharp
Copied from original issue: Microsoft/vscode#14676

@darkoverlordofdata: the output above seems very strange. I'm not sure why it would try to launch a .NET Core version of OmniSharp with Mono, but I'm guessing that's the problem.
Did you set "omnisharp.useMono": true in your VS Code settings? If so, that won't work with the .NET Core version of OmniSharp. That version is standalone.

I'm having the same issue, is there anything I can try ?

Have you set the "omnisharp.path" and "omnisharp.useMono" settings?

Thanks for the reply.
its working now i deleted the extension and installed the latest beta using vsix, didn't use path or use mono the extension itself installed all the dependencies.

Makes sense. Out of curiosity, which version of the extension did you install? Was it from the VS Code marketplace? Or, was it one of the beta releases available on this repo?

I've set useMono to false, and it loads. That seems counter-intuitive since I'm on linux, wouldn't I want to use mono? Anyway, it them can compile, but it can't run - I get a message:
Run 'Debug: Download .NET Core Debugger' in the Command Palette or open a .NET project directory to download the .NET Core Debugger
But when I do that, nothing happens. It doesn't seem like this product is ready yet....

It's a bit counter-intuitive, but you downloaded the standalone OmniSharp that is built for Ubuntu. That version runs natively on Ubuntu and doesn't need Mono. There is a Mono build of OmniSharp that requires Mono to run.

Glad both of you got it working. Note that this should be much easier in the 1.5 release, which is coming soon.

I get something like:
[fail]: OmniSharp.MSBuild.ProjectFile.ProjectFileInfo The project 'd: \ Projects GIT \ Fennec Fox Solutions \ FoxAccount \ src \ FoxAccount.Application \ FoxAccount.Application.csproj' does not have any destination structure compatible with '.NETCoreApp, Version = v2.0 '.

Could you file a new issue rather than reporting on a year-old closed issue? Thanks!


Create gym.html

i have added a new code in your repo plz accept it and merge it
#hacktober-accepted

Yep, you are now banned from Hacktoberfest. Good luck with spamming.


Unify return value and errors

As #23 suggested, we should use unified scheme for error numbers and return values.  We have CSP_ERROR_NONE defined as 0 in csp_error.h but csp_queue, csp_semaphore, and csp_mutex uses 1, or pdTRUE / pdPASS as OK.
Because this is API breaking changes, it should only be for 2.0, as #23 suggested.
I'm creating this new issue becuase #23 is already closed.

This will have to wait until a 2.1 or subsequent release. Since 2.0 is already in release candidate.
Theres a lot of cleanup that I would like to perform if I had the change to do over. 😊

I didn't know 2.0 is that close.  There is no RC tag yet, right?
Would you give v2.1, or v3.0, tag to this?  Or did you mean we won't fix this?  I'm sure it's a huge change.

I think we want to go with zero as OK and negative values as error.
This means the change needs to be in csp/arch which is used much more seldom than csp io. But yes it IS somewhat of a bigger change.
I don't want to ignore it, because it IS an inconvenient inconsistency. So I would like to address some of these internal stuff in a major release.
The next API break will be in 2.1

I fixed the csp_send return value issue now

csp_mutex is gone now too

The CSP_QUEUE_OK changed was non breaking, since only the macros was used it was only a matter of changing the value, and fixing the return of the FreeRTOS queue functions.


my profile

resolves #issueNumber
Checklist for profile addition

[x] Name the PR fix: add <your-username>.
[x] You've added file named your-username.json in the profiles directory.
[x] You've linked the PR to the correct issue.

Other additions/changes

[x] Changes made in this PR are mentioned below
[x] Search previous suggestions before making a new one, as yours may be a duplicate.
[x] I acknowledge that all my contributions will be made under the project's license.
[x] I've read the contributing guidelines

This PR adds/fixes

Notes

fix: add yiga gilbert


Support for zooming only when pinching

this is usable in painting mode, you can paint by finger and also zoom in by two fingers

Mine implements custom modifier and i struggled to get zoom built in but failed :( so i just use separate zoomable modifier now

The purpose of this library is to easily achieve zooming, not to achieve complex behavior like that of a paint application.
I'm sorry I cannot meet your request.


WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary

As in the title; MQTT broker warnings about JSON results not being a dictionary ones.
Couple of houndred tousands a day. Had to enable DEBUG level of logs to be able to connect the error with Batmon and DalyBMS.
"WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary"
Exemplary Log from Batmon:
BEGIN
12:38:35 INFO [sampling] DalyBt(C6:6C:09:05:02:EC) times: connect=0.00s fetch=1.20s
12:38:40 INFO [sampling] DalyBMS: BmsSampl(46.7%,U=55.4V,I=0.00A,P=0W,q=0.9Ah/2,mos=nan°C)
12:38:41 INFO [sampling] DalyBMS volt=3937,3972,3942,3982,3947,3984,3932,3977,3945,3974,3933,3985,3952,3982 temp=[26]
12:38:41 INFO [sampling] DalyBt(C6:6C:09:05:02:EC) times: connect=0.00s fetch=1.30s
12:38:46 INFO [sampling] DalyBMS: BmsSampl(46.7%,U=55.4V,I=0.00A,P=0W,q=0.9Ah/2,mos=nan°C)
12:38:47 INFO [sampling] DalyBMS volt=3928,3974,3944,3989,3942,3995,3932,3985,3934,3981,3930,3995,3945,3998 temp=[26]
12:38:47 INFO [sampling] DalyBt(C6:6C:09:05:02:EC) times: connect=0.00s fetch=1.20s
12:38:53 INFO [sampling] DalyBMS: BmsSampl(46.7%,U=55.5V,I=-0.60A,P=-33W,q=0.9Ah/2,mos=nan°C)
12:38:53 INFO [sampling] DalyBMS volt=3940,3972,3953,3977,3953,3981,3952,3975,3949,3976,3952,3990,3957,3987 temp=[26]
12:38:53 INFO [sampling] DalyBt(C6:6C:09:05:02:EC) times: connect=0.00s fetch=1.25s
12:38:59 INFO [sampling] DalyBMS: BmsSampl(46.7%,U=55.4V,I=0.00A,P=0W,q=0.9Ah/2,mos=nan°C)
12:39:00 INFO [sampling] DalyBMS volt=3927,3973,3934,3981,3941,3984,3925,3975,3938,3976,3926,3980,3942,3978 temp=[26]
12:39:00 INFO [sampling] DalyBt(C6:6C:09:05:02:EC) times: connect=0.00s fetch=1.30s
END

Exemplary Log from HA:

BEGIN
2023-07-03 12:35:21.117 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/1 (qos=0): b'3.989'
2023-07-03 12:35:21.117 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.124 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/2 (qos=0): b'3.95'
2023-07-03 12:35:21.125 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.128 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/3 (qos=0): b'3.98'
2023-07-03 12:35:21.128 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.130 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/4 (qos=0): b'3.944'
2023-07-03 12:35:21.131 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.135 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/5 (qos=0): b'3.976'
2023-07-03 12:35:21.135 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.137 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/6 (qos=0): b'3.938'
2023-07-03 12:35:21.138 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.141 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/7 (qos=0): b'3.992'
2023-07-03 12:35:21.141 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.144 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/8 (qos=0): b'3.945'
2023-07-03 12:35:21.144 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.146 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/9 (qos=0): b'3.985'
2023-07-03 12:35:21.146 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.148 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/10 (qos=0): b'3.948'
2023-07-03 12:35:21.148 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.152 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/11 (qos=0): b'3.993'
2023-07-03 12:35:21.152 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.154 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/12 (qos=0): b'3.938'
2023-07-03 12:35:21.154 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.156 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/13 (qos=0): b'3.98'
2023-07-03 12:35:21.156 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.158 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/14 (qos=0): b'3.941'
2023-07-03 12:35:21.158 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.159 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/min (qos=0): b'3.938'
2023-07-03 12:35:21.160 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.162 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/min_index (qos=0): b'5'
2023-07-03 12:35:21.162 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.163 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/max (qos=0): b'3.993'
2023-07-03 12:35:21.163 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.164 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/delta (qos=0): b'0.055'
2023-07-03 12:35:21.164 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.165 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/average (qos=0): b'3.964'
2023-07-03 12:35:21.165 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.166 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/median (qos=0): b'3.963'
2023-07-03 12:35:21.166 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:21.513 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/temperatures/1 (qos=0): b'26'
2023-07-03 12:35:21.513 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:26.913 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/soc/total_voltage (qos=0): b'55.4'
2023-07-03 12:35:26.913 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.364 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/1 (qos=0): b'3.992'
2023-07-03 12:35:27.365 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.368 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/2 (qos=0): b'3.944'
2023-07-03 12:35:27.368 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.376 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/3 (qos=0): b'3.977'
2023-07-03 12:35:27.376 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.379 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/4 (qos=0): b'3.928'
2023-07-03 12:35:27.379 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.383 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/6 (qos=0): b'3.924'
2023-07-03 12:35:27.383 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.386 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/7 (qos=0): b'3.99'
2023-07-03 12:35:27.387 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.389 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/8 (qos=0): b'3.933'
2023-07-03 12:35:27.389 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.391 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/9 (qos=0): b'3.986'
2023-07-03 12:35:27.391 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.397 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/10 (qos=0): b'3.94'
2023-07-03 12:35:27.397 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.402 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/11 (qos=0): b'3.991'
2023-07-03 12:35:27.402 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.404 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/12 (qos=0): b'3.918'
2023-07-03 12:35:27.405 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.408 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/13 (qos=0): b'3.969'
2023-07-03 12:35:27.408 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.411 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/14 (qos=0): b'3.924'
2023-07-03 12:35:27.411 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.413 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/min (qos=0): b'3.918'
2023-07-03 12:35:27.414 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.416 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/min_index (qos=0): b'11'
2023-07-03 12:35:27.416 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.418 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/max (qos=0): b'3.992'
2023-07-03 12:35:27.419 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.421 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/max_index (qos=0): b'0'
2023-07-03 12:35:27.421 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.424 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/delta (qos=0): b'0.074'
2023-07-03 12:35:27.424 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.426 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/average (qos=0): b'3.957'
2023-07-03 12:35:27.426 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
2023-07-03 12:35:27.427 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on DalyBMS/cell_voltages/median (qos=0): b'3.9565'
2023-07-03 12:35:27.427 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary
END

Any insights? :)

YOu can ignore the warnings. Will fix it with the next update

Fixed with 0.0.64


Sample file missing

This page,  https://tableau.github.io/server-client-python/docs/samples#samples-list , has metadata_query.py in the list of sample files, but it doesn't exist in the repo at https://github.com/tableau/server-client-python/tree/master/samples

@ejoynes thanks for catching that. That sample file was recently added and will be part of the next TSC release. (The docs were already updated, so that made it confusing.) Until the next release, you can find that file on the development branch here:
https://github.com/tableau/server-client-python/blob/development/samples/metadata_query.py

Nice to see that the docs are actually getting read and that there is interest in the example for metadata queries :)
Sorry for the confusion, though!

Released in https://github.com/tableau/server-client-python/releases/tag/v0.17.0


workflows: clang-build: migrate to GitHub Secrets

2 weeks, upstream does not seem to care, closing.


CNContactStore.currentHistoryToken is alway nil on iOS 13 and iOS 14

Everything is good til I test on my iPhone iOS 13.2.
CNContactStore.currentHistoryToken always empty.
Can you add supporting iOS list into your doc.
Thanks for reading

Same to 14.0

I'll need running code to debug this...
Please create a minimal project that reproduces this problem, create a github project with its code, and link to it here. (See https://ootips.org/yonat/repex/)

Thanks for replying back
@yonat nothing change, just run your example in iOS 13.x or iOS 14.x.
The functions are not right anymore.

I found an answer on Apple Forums by an Apple Engineer. Link here
Its a bug in Swift.
So we can take currentHistoryToken from ObjC or we can get currentHistoryToken from CNFetchResult (from Apple Docs)

After double checked, I see store.currentHistoryToken nil from both ObjC and Swift (on iOS 13.x and 14.x).
I will wait for you confirm and update (if can).
Thanks

Sorry for responding late, I will be unavailable until Jun-14.

@yonat have any update?

Didn’t have a chance to check yet, will take a look next weekend.

Just checked this, I don't think i'll be able to support iOS 13 and 14. 😞
I'll raise the minimum target to iOS 15.


Linkvertise not being bypassed

Domain
linkvertise.com
Link
https://linkvertise.com/
Version
idk
What browsers are you seeing the problem on?
Microsoft Edge
What OS are you seeing the problem on?
Windows
Anything else?
When downloading mods specifically Minecraft, fast forward should be able to bypass linkvertise

Duplicate of #963


PR 1259 review additions

check if old.file is available at specified location, otherwise don'T start transformation and fail comparison

Thanks. Will adjust a bit more.


GEM vehicle parameters

I was looking at the GEM e2 vehicle spec sheet on the Polaris website (https://gem.polaris.com/en-us/e2/specs/) to verify the vehicle parameters provided in apollo/modules/common/data/gem_config.pb.txt. Few parameters like length, wheel_base, turning_radius seem to be different. What's the reason for this ? Is it intentional ? Thanks in advance.

@ankitvora7 that config file was written by our partners from AutonomousStuff. It'd be best if you could reach out to them regarding the parameters.

Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.


security(SR-5): Add SSRF protection to portal-api

Introduction
Fix for SR-5. Portal-API need SSRF protection
Resolution

added function to check if mongoId is valid
Added it to create and get bond, loan, get deal and download file
Added to tests

Just to check is Portal/Gef UI going to be done as separate PRs or as part of this one?


WITHIN OBJECT command with WHERE z?

I was hoping the last WITHIN command here would return the point inside2. It actually returns nothing.
$ tile38-cli
<IP_ADDRESS>:9851> FLUSHDB
{"ok":true,"elapsed":"4.37µs"}
<IP_ADDRESS>:9851>
<IP_ADDRESS>:9851> SET test outside1 POINT 15.20 52.58 1
{"ok":true,"elapsed":"18.225µs"}
<IP_ADDRESS>:9851> SET test outside2 POINT 15.20 52.58 2
{"ok":true,"elapsed":"6.091µs"}
<IP_ADDRESS>:9851>
<IP_ADDRESS>:9851> SET test inside1 POINT 46.49 52.37 1
{"ok":true,"elapsed":"5.861µs"}
<IP_ADDRESS>:9851> SET test inside2 POINT 46.49 52.37 2
{"ok":true,"elapsed":"4.784µs"}
<IP_ADDRESS>:9851>
<IP_ADDRESS>:9851> WITHIN test OBJECTS OBJECT '{"type":"Polygon","coordinates":[[[33.75,43.45],[59.32,43.45],[59.32,59.17],[33.75,59.17],[33.75,43.45]]]}'
{"ok":true,"objects":[{"id":"inside1","object":{"type":"Point","coordinates":[52.37,46.49,1]}},{"id":"inside2","object":{"type":"Point","coordinates":[52.37,46.49,2]}}],"count":2,"cursor":0,"elapsed":"82.687µs"}
<IP_ADDRESS>:9851> WITHIN test WHERE z 1.5 2.5 OBJECTS OBJECT '{"type":"Polygon","coordinates":[[[33.75,43.45],[59.32,43.45],[59.32,59.17],[33.75,59.17],[33.75,43.45]]]}'
{"ok":true,"objects":[],"count":0,"cursor":0,"elapsed":"35.083µs"}

What is the correct way to perform this query? Or is this unsupported, or even a bug?

I'll have to do a little more digging but this may be a bug (or at least a quirk). Currently GeoJSON polygons are limited to 2D. The Z where clause puts the query engine into 3D mode so the polygon is being ignored.
It's possible that this could be corrected, but in the meantime you can use BOUNDS instead:
<IP_ADDRESS>:9851> WITHIN test WHERE z 1.5 2.5 OBJECTS BOUNDS 43.45 33.75 59.17 59.32
{"ok":true,"objects":[{"id":"inside2","object":{"type":"Point","coordinates":[52.37,46.49,2]}}],"count":1,"cursor":0,"elapsed":"34.078µs"}

This would likely be a more efficient operation in the long run.

Thanks for the quick response. Given the internals you described the behavior makes sense. If the fix isn't easy, I'd suggest documenting this.
I used a box in the test case for simplicity, but my use case requires complex polygons so BOUNDS won't work.
I think I'll use a named field instead of z. Performance is worse but it should still be fine for our application.

For a future release, I think it's possible that the system might be able detect that polygon is 2D and do a BOUNDS with Z under the hood. The process the WITHIN on the results.
Thanks for filing this issue.

FYI, I just pushed an update that happens to address this issue. There's nothing tricky being done, it just queries over 2D and then filters the results on Z.


Allow user to edit packages

Mentioned in #287
Q: Should we restrict package edit to owners only?

Q: Should we restrict package edit to owners only?

Yes.

LGTM :+1:

Merged with master


Update packages & links

opencore download fixed
libvpx upgraded from 1.3.0 to 1.5.0
libvorbis upgraded from 1.3.4 to 1.3.5
pkg-config upgraded from 0.28 to 0.29
cmake upgraded from 3.0.2 to 3.5.0
x265 upgraded from 1.6 to 1.9
fdk_aac upgraded from 0.1.3 to 0.1.4

We were already utilizing curl's redirect functionality so I changed some urls to more readable/consistent urls
-- Entire script tested today 09-03-2016 23:33, and ran without issues on Ubuntu 15.10

Hi Mirabis,
Thank's for your work. I wasn't able to merge your pull request directly because the patch were done against a one year old version of my script. But I was able to add the updates of several packages manually. Best, Markus

Yeah I noticed after I did the pull request, my bad :(

No problem and thx for your work!


ENH: itkObjectToObjectOptimizerBase Must be explicitly instantiated

Move code to cxx file because this class must be explicitly
instantiated for each valid template type to support
dynamic casting necessary.

@dzenanz removing the number of file dependancies is important.  The .hxx file should be moved to the src directory.
The main point is to be clear that the definitions are only used in the compilation unit of the cxx file where explicit instantiation occurs.

@dzenanz Any further concerns?


5.4 RC 2 release notes

And related documentation updates.

Would put the changes to the upload_binary_data.md into a separate commit.

:+1: done


[Feature Request] Add buttons for manage the zoom on canvas (like roll20)

I don't know if this request is within the scope of this module, I tried to get some people from Roll20 to FoundryVTT the other day and as several of them were on touchpads (laptops without mouse), they complained about the absence of the zoom buttons (the buttons that Roll 20 holds at the top right) to which they are evidently used.
They didn't like the right-click option standard (or the middle variant of this module) very much.
Would it be possible as an additional feature to this module that already manages the touchpad and other settings to add the two buttons on the top right? a bit like the Visual Active Effects module does with the effects only with the two squares of plus and minus always fixed.

Can you share a screenshot from Roll20 of this feature?
Also, just in case, have you told these people that there is a touchscreen option in this module's settings, which should make zooming nicer on laptops?

Didn't know about the touchscreen option ty!
Here a little gif of roll20 and the buttons dedicated to the zoom.


Add animations to the button

I added an animation to the button when it is hovered and clicked.
Video of the animation
https://user-images.githubusercontent.com/94648837/194933593-3833757a-8add-47a6-80a3-7e96f0d33b17.mov

Try to deploy it

Hey @shivanidotcom, for some reason I can't deploy it. I get an error when trying to deploy, I have some problems with my nom package and terminal..


v4 bug on rpi 4

running the installer
Digest: sha256:1b6227fac037ce30c80c3374eee4f6906d6ff9003b9e0206be6ec4c3e5cfda1f
Status: Downloaded newer image for ghcr.io/coollabsio/coolify-builder:latest
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
exec /sbin/tini: exec format error

docker run \
  -v /data/coolify/source:/data/coolify/source \
  -v /var/run/docker.sock:/var/run/docker.sock \
  --privileged \
  --rm \
  docker:dind \
  docker compose \
    --env-file /data/coolify/source/.env \
    -f /data/coolify/source/docker-compose.yml \
    -f /data/coolify/source/docker-compose.prod.yml \
    up -d --pull always --remove-orphans --force-recreate

doing this in upgrade.sh fixed the issue for me


Transport: set libgit2's last_error (#576)

Previously, the propagated error from a custom transport would always be the
default "unknown error" as returned by Error::last_error if git_error_last
returns a null pointer. The attached test case is rather trivial, but can be
used to reproduce the old and new behaviour.

Thanks! Should there perhaps be a specialized version of set_err, though, which also forwards the class/code instead of overriding it with GIT_ERROR_NET?

👍


feat: enable simulations

Description
Enable simulations for non-beta app (without any custom modules).
ref: #354

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added appropriate labels to the PR
[ ] added ! to the type prefix if API or client breaking change
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

I'm not marking the simulations as required yet because I need to figure out how to inject MsgSetOrchestratorAddress messages so the thing won't panic. But that can be for a future PR.


Remove an obsolete (and now incorrect) comment in the pubspec.yaml

Oh my yes. I'll send more PRs to update the rest...

Oh my yes. I'll send more PRs to update the rest...


[FEATURE] Standalone PPL streams &  library

1. Overview
1.1 Introduction

Piped Processing Language (PPL), powered by OpenSearch, enables OpenSearch users with exploration and discovery of, and finding search patterns in data stored in OpenSearch, using a set of commands delimited by pipes (|). These are essentially read-only requests to process data and return results.

PPL is an OpenSearch query language alternative to DSL. It allows user to pipe output into new PPL commands, providing an experience that’s similar to the unix command line. Users can build the query command by command gradually and check intermediate results instead of getting a complex query correct at the first run. This makes the query easy to understand and allows users to correct any mistakes early. Since PPL is a generic language and not necessarily tied to OpenSearch, it is possible to separate PPL into a standalone Java library to use in other places such as data-prepper processor.
This document will focus on the design of PPL library and its integration with data-prepper, and also explore some other possibilities of PPL library.
1.2 Possible Use Cases
1. PPL for metrics extraction at ingestion time
Currently, PPL can be used in OpenSearch to aggregate multiple log lines at query time to get metrics (e.g. sum, average, standard deviation, etc). Users construct monitoring dashboards from these metrics to identify possible anomalies in their services. When an anomaly is found in metrics, users will then go to the corresponding logs to check the specific error messages. This workflow can be simplified by computing metrics at ingestion time instead of query time, which brings some benefits such as being able to use S3 as log storage to reduce indexing and storage costs (see https://github.com/opensearch-project/sql/issues/595 for more details). Integrating PPL into ingestion tools to achieve this can improve the user experience.
With PPL library decoupled from OpenSearch engine and integrated with ingestion tools, PPL queries used in OpenSearch to generate metrics can be pasted directly into ingestion setup. This allows metrics to be computed at ingestion time without additional configuration and learning efforts on the ingestion side. For example, data-prepper, logstash, fluentd might have different mechanisms to extract metrics. With a PPL plugin, users don’t need to learn how to configure metrics extractions for any of them. They only need to understand PPL.
2. PPL as a general command line tool
While there are many powerful tools in the command line, it can still be difficult to work with log/events data and perform meaningful computations, especially for csv or ndjson files. By implementing an input handler in the library in front of PPL engine, PPL will be able to read from STDIN or files on disk. Similar to q which lets users run SQL on csv files, PPL CLI will allow users to do the same operations they are familiar with in OpenSearch PPL to their files for analysis (for example, analyze csv downloaded from reporting plugin). This also allows them to run PPL in shell scripts or cron jobs for real time metrics monitoring without OpenSearch.
Sample usage:
tail -n 5000 ./app.log | java -jar PPL.jar \
    "source = - \
    | parse method=json \
    | where timestamp > '$(date -d'now-15min' +'%Y-%m-%dT%H:%M:%SZ')' \
    | stats count() as ip by host, response"

3. PPL as a connector to remote data sources
Additionally, it can be possible to add clients for other data sources (e.g. OpenSearch, Prometheus, S3). This gives user a consistent experience to connect to different data sources with the same experience.
Sample usage:
java -jar PPL.jar --config=ppl.yml \
    'source = s3.apache_logs \
    | parse method=grok "%{COMMONAPACHELOG}" \
    | where response = 404 \
    | stats count() as ip by host, response'

1.3 Project Goal Summary
Make PPL into a generic and universal language that can be used in different environments, including at ingestion time, to create a consistent query language experience.
2. Requirements
2.1 Functional Requirements
PPL core

Support more parse methods (json, grok) in addition to regex in parse command
Support more date formats (ISO, custom) for data type casts in cast() function
Support JSON schema for query response

PPL library

Syntax and in-memory computations in PPL library should be the same as OpenSearch PPL
Should allow user to define schema separately or use a default schema
Should be able to integrate with ingestion tools (data-prepper) through plugins

PPL library for command line usage (needs discussion or out of scope for P0)

Should be able to infer schema if input is JSON or CSV file
Support OpenSearch, S3, Prometheus as remote sources

2.2 Non-functional Requirements

Should be extensible: easy to integrate with other tools or add additional catalog
Query used for ingestion should be mostly the same as the original search query
Provide some help in UI for writing PPL queries to generate metrics from raw logs

3. High-Level Design
3.1 PPL Library
PPL Library will implement the in-memory version of the required components from the opensearch module. There will be no optimization since everything will be executed in memory and cannot be pushed down.

3.2 Comparison of OpenSearch PPL, PPL Library, and its integration with ingestion tools

3.2 Data-Prepper Integration

A new processor plugin will be added to data-prepper, which handles a batch of buffered logs at each time. The processor plugin will make calls to PPL library with logs and user queries. There can be two options to call PPL library:
Option 1: spawn a new process for PPL.jar
Will be used by non-Java ingestors.
ProcessBuilder builder = new ProcessBuilder("java", "-jar", "libppl.jar", configFile);
Process process = builder.start();
BufferedReader reader = new BufferedReader(new InputStreamReader(process.getInputStream()));
BufferedWriter writer = new BufferedWriter(new OutputStreamWriter(process.getOutputStream()));

// send logs to PPL
logs.forEach(logLine -> {
    writer.write(logs);
    writer.newLine();
});
writer.close();

// read PPL response
reader.lines();

Option 2: import PPL.jar as a dependency
Will be used by Java based ingestors.
public class LibPPLQueryActionFactory {
  public static LibPPLQueryAction create(Collection<Map<String, Object>> input);
}

public class LibPPLQueryAction {
  public void execute(String pplQuery);
}

why do we need to integration with S3 in the PPL library? It should be handled by the upstream or downstream, like DataPepper.  Direct integration only adds complexity to the PPL library itself.

Regarding DataPepper integration, how could we make sure all required docs are processed by the same PPL instance? The related docs could come from multiple sources and DataPepper may also have multiple workers for scalability. Would the DataPepper docs routing understand the PPL aggregation requirement?

why do we need to integration with S3 in the PPL library?

currently it's the only way to get raw logs to S3, but I agree it's not correct design. We can utilize conditional routing from data-prepper 2.0 to support multiple sinks

how could we make sure all required docs are processed by the same PPL instance?

just a thought we can have metrics at ingestion node level and aggregate again when displaying in UI, but i can still see issues. this will need more investigation with the data-prepper peer-forwarder

status update:
currently S3 library works inside data prepper as a processor plugin, sample pipeline configuration:
simple-sample-pipeline:
  workers: 1
  delay: "1000"
  source:
    http:
      ssl: false
      authentication:
        unauthenticated:
      port: 2021
  processor:
    - ppl:
        query:
          - "source = stdin | stats count() by method"
          - "source = stdin | stats count() as throughput"
          - "source = stdin | where status > 299 | stats count() as errors"
          - "source = stdin | stats avg(bytes) as avgBytes"
          - "source = stdin | stats sum(bytes) as totalBytes"
  sink:
    - stdout:
    - opensearch:
        hosts: [ "http://localhost:9200" ]
        insecure: true
        index: data_prepper_results

sample response
GET {{BASE}}/data_prepper_results/_search

      {
        "_index": "data_prepper_results",
        "_id": "8HVkO4EBJcL4QVEgLHSS",
        "_score": 1,
        "_source": {
          "count()": 2,
          "method": "DELETE",
          "timeReceived": "2022-06-06T23:40:29.666388Z"
        }
      },
      {
        "_index": "data_prepper_results",
        "_id": "8XVkO4EBJcL4QVEgLHST",
        "_score": 1,
        "_source": {
          "count()": 1,
          "method": "POST",
          "timeReceived": "2022-06-06T23:40:29.666388Z"
        }
      },
      {
        "_index": "data_prepper_results",
        "_id": "8nVkO4EBJcL4QVEgLHST",
        "_score": 1,
        "_source": {
          "count()": 2,
          "method": "GET",
          "timeReceived": "2022-06-06T23:40:29.666388Z"
        }
      },
      {
        "_index": "data_prepper_results",
        "_id": "83VkO4EBJcL4QVEgLHST",
        "_score": 1,
        "_source": {
          "count()": 2,
          "method": "PATCH",
          "timeReceived": "2022-06-06T23:40:29.666388Z"
        }
      },
      {
        "_index": "data_prepper_results",
        "_id": "9HVkO4EBJcL4QVEgLHST",
        "_score": 1,
        "_source": {
          "count()": 1,
          "method": "PUT",
          "timeReceived": "2022-06-06T23:40:29.666388Z"
        }
      },
      {
        "_index": "data_prepper_results",
        "_id": "9XVkO4EBJcL4QVEgLHST",
        "_score": 1,
        "_source": {
          "throughput": 8,
          "timeReceived": "2022-06-06T23:40:29.666388Z"
        }
      },
      {
        "_index": "data_prepper_results",
        "_id": "9nVkO4EBJcL4QVEgLHST",
        "_score": 1,
        "_source": {
          "errors": 4,
          "timeReceived": "2022-06-06T23:40:29.666388Z"
        }
      },
      {
        "_index": "data_prepper_results",
        "_id": "93VkO4EBJcL4QVEgLHST",
        "_score": 1,
        "_source": {
          "avgBytes": 16886.25,
          "timeReceived": "2022-06-06T23:40:29.666388Z"
        }
      },
      {
        "_index": "data_prepper_results",
        "_id": "-HVkO4EBJcL4QVEgLHST",
        "_score": 1,
        "_source": {
          "timeReceived": "2022-06-06T23:40:29.666388Z",
          "totalBytes": 135090
        }
      },
      {
        "_index": "data_prepper_results",
        "_id": "-XVkO4EBJcL4QVEgMnRj",
        "_score": 1,
        "_source": {
          "count()": 2,
          "method": "HEAD",
          "timeReceived": "2022-06-06T23:40:31.193580Z"
        }
      }

Currently working on implementing an independent log ingestion and output solution using PPL library, as there are a few dependencies blocked by data-prepper 2.0

accidentally closed the issue..
@dlvenable right, the source command is needed in OpenSearch PPL but is not necessary here since source is controlled by the pipeline's source. I kept it as a placeholder but I agree removing it would be better

source = stdin |  is meant for PPL CLI

Requirements

A rest endpoint for plugins in DP which can reload config. or live change config.
we need control plane apis for DP

@joshuali925 ,
There may be some confusion about getting events to S3 and OpenSearch. Data Prepper supports routing events to other pipelines.
I think the ideal solution is that the Data Prepper pipeline route events to two pipelines:

A raw Event pipeline to send to S3
A PPL Processor pipeline to produce results and send to OpenSearch.

I'm attaching a concept diagram of the pipelines that would be involved.


[New] Manage bookmarks

Description
This PR implements Manage bookmarks in Maps category.
URL to README: README
Linked Issue(s)

swift/issues/4895

How To Test

Tap the book button and tap a bookmark from the list to navigate to it on the map.
Tap the plus button and enter a name to add a bookmark with the current viewpoint to the map.

Screenshots

Thank you guys!


Record types syntax highlighting

Feature request: Need a syntax highlighting for record types.

@wendellestradairely This is an issue with the C# textmate grammar. You can set csharp.semanticHighlighting.enabled to true to get a better highlighting experience.

Closing as answered.


possibly repressed genomes

The following genomes did not download in Kalamari 5.3.3. I'm wondering if I need to replace these.
CP000927
CP000937
CP000949
CP000950
CP001010
NC_000907
NC_000915
NC_003454
NC_003888
NC_007644
NC_010465
NC_016771

I have removed or replaced these in HEAD. Those that are remaining have been transferred to the other csv file.

Need to find a way to automate this for plasmids.tsv


ISPN-8032 Add infinispan-hibernate-cache to bom

https://issues.jboss.org/browse/ISPN-8032

Pushed to master, thanks.


Freeze libroc version when building AAR on CI

Currently, when CI builds AAR, it uses libroc from master branch of roc-toolkit. It's not good because this way AAR builds are not reproducible.
What we need to do:

add ROC_VERSION parameter to android_docker.sh script; default value should be "master"; when cloning roc, checkout specified version

in release job on CI, specify ROC_VERSION explicitly, set it to roc-toolkit tag which is currently the latest

ROC_VERSION should support any git revision notation: tag name, branch name, or commit hash.

Fixed via #132.


Updated DTO

Implemented:

DTO can be inherited
DTO can be next types: String, Boolean, Float and int

@eliogrin
What is the approach of dto inheritance? Maybe you have use cases?
I think we need split this task into two independent:

inheritance of dto;
different types of attributes in dto;

@Invictum
For example you have 2 or more types of user, which one had several common parameters and several unique parameters. With inheritance in the DTO you can describe common parameters in one DTO class, and then implement different DTO classes for each user type. It will help to avoid code duplication.
Also, I can split it, if you would like, it's not a problem for me.

@eliogrin
Ok make sense. Let's split it into two tasks and discuss its separately. Current one could be transformed into inheritance related.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_08b0434d-e881-4d9e-8733-1d9d6dfe8bba/pull/1 is merged into live branch.
Auto archive content to https://github.com/huangmin-ms/docs-archive-test-target_08b0434d-e881-4d9e-8733-1d9d6dfe8bba.git

Docs Build status updates of commit 4e80db3:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-UserAccountBuildPermissionInsufficientError] Owner v-alji no longer has Read permission of the repository https://github.com/huangmin-ms/docs-archive-test-source. It might be due to recent GitHub changes on SSO. Please ask the owner v-alji to logon to Docs Portal https://ops.microsoft.com once again. If it is not the case, please ask anyone of Admin permission of the repo to assign a new owner via Docs Portal https://ops.microsoft.com

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 4e80db3:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-UserAccountBuildPermissionInsufficientError] Owner v-alji no longer has Read permission of the repository https://github.com/huangmin-ms/docs-archive-test-source. It might be due to recent GitHub changes on SSO. Please ask the owner v-alji to logon to Docs Portal https://ops.microsoft.com once again. If it is not the case, please ask anyone of Admin permission of the repo to assign a new owner via Docs Portal https://ops.microsoft.com

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Change image links to absolute path on server

File system and URL based access is now possible.
Please note that you will need a trust store to access URL resources.


Running the current buffer in Iron Repl by pressing  ?

Hello,
congratulations for your plugin, I could open the ipython terminal using my virtualenv in a splitted horizontal view and I'm grateful for that :-).
now, I would like to mimic the Python IDLE editor, and run the active buffer entirely, by pressing F5.
I could not find what mapping nor the command I should use for that.
thanks a lot.

Hello, sorry for my late reply. It works perfectly ! Thank you very much.

Thank you very much for this reply, it works but only for a single line file. Three print statements in a row don't make it:
print("line 1")
print("line 2")
print("line 3")
translate in the REPL to:
print("line 1")print("line2")print("line 3")

Weird. I just tested against master version, on linux, running nvim from the terminal and it pasted the whole file in in the repl. What's your setup?

Hello again,
I'm working on Windows.
Having setting up IronREPL from scratch on my Windows laptop, it works better:

each line is separated in the REPL

The following screen capture illustrates the three problems I encounter:

the ^[ characters appears after each line.
a space is inserted before the cursor location in the original file (here, the cursor was on the last character of the file).
there's no automatic execution of the code

The mapping :
map <F5> <Cmd>lua require("iron").core.send(vim.api.nvim_buf_get_option(0, "ft"), vim.api.nvim_buf_get_lines(0, 0, -1, false))<Cr>
The lua file
local iron = require('iron')

iron.core.add_repl_definitions{
  python = {
    venv_python = {
      command = "MyPath\\to\\ipython.exe"
    },
  }
}
iron.core.set_config{
preferred = { python = "venv_python"},
repl_open_cmd = 'rightbelow 10 split'

Also having some trouble on Windows 10 with extra characters and no automatic carriage return. If I have some time I may try to jump in here with you and figure some stuff out. Been meaning to learn about vim plugins but I am starting from zero. @hkumpy you're doing God's work here by the way.

New strategy I'm working on here: loop through the lines and send them one by one to the REPL. The code below sends only lines 4 through 8. Notice the "\n\r" send at the end which forces the execution on Windows:
lua my_table = vim.api.nvim_buf_get_lines(0, 4, 8, false); for i = 1, table.getn(my_table) do require("iron").core.send(vim.api.nvim_buf_get_option(0, "ft"), my_table[i]) end; require("iron").core.send(vim.api.nvim_buf_get_option(0, "ft"), "\n\r")

Seems like it should be simple but I'm having trouble getting start and end rows for a visual selection. Working with this vimscript function:
function! Show_position()
    let new_list = [getpos("'<")[1], getpos("'>")[1]]
    return new_list
endfunction

It seems like it's giving me the right numbers, but it's looping through every line which isn't great. Going to see if I can hook this up today.

I've got two lua functions that work with iPython in Windows. Use them with ipython --simple-prompt as the custom command. The first runs the entire file top to bottom:
lua my_table = vim.api.nvim_buf_get_lines(0, 0, -1, false); for i = 1, table.getn(my_table) do require("iron").core.send(vim.api.nvim_buf_get_option(0, "ft"), my_table[i]) end; require("iron").core.send(vim.api.nvim_buf_get_option(0, "ft"), "\n\r")

The second runs a visual selection, and depends on the Show_position() vimscript function from my last post:
lua local lower, upper = unpack(vim.api.nvim_call_function("Show_position", {})); my_table = vim.api.nvim_buf_get_lines(0, lower - 1, upper, false); for i = 1, table.getn(my_table) do require("iron").core.send(vim.api.nvim_buf_get_option(0, "ft"), my_table[i]) end; require("iron").core.send(vim.api.nvim_buf_get_option(0, "ft"), "\n\r")

The first command works fine either as a directly entered command or mapped to a key. The second command works beautifully every time when I run it manually but is always one command set behind when it's mapped to a key sequence in init.vim. I feel like I just can't win here!

First of all, sorry for taking this long to answer. Couldn't get much time to devote attention to my projects, unfortunately.
I found this line on fts/common.lua:
    new[#new] = new[#new] .. "\13"

\13 is "carriage return". I need to figure out if it's a windows machine so I can select between \13 and \13\10 (crlf).
Would you mind @baogorek trying the branch ttempt-fix-lf to check if it fixes your line-endings issues on windows?
Best regards and sorry once again,
Henry John Kupty

Hi @hkupty,
Here's the verdict on the branch attempt-fix-lf:

Using the default iPython REPL (v 7.9.0 running Python 3.6.8), your new branch successfully removes the crazy characters in the default iPython console, but still will not execute the command block with the ctr key combo in visual mode, leaving the block hanging in the console.

Using that same iPython REPL with the flag --simple-prompt (as shown in my own plugins.lua), ctr executes the entire block, but the newlines are lost.

Henry, I finally have a set of keymappings for this set of tasks that works. Along with the plugins.lua that uses the --simple-prompt version of iPython, this init.vim file contains 3 keymappings, the last being the one that sends a visual selection to the iPython editor. It works! And it's fast. But it does require the --simple-prompt iPython flag. You'll see from this emacs QA that things got more complicated for IPython around version 5.
One final note is that, for whatever reason, the nmap-ed <Plug>(iron-send-line) is way slower than the vmap-ed custom version. I'll still use it but I'm just curious as to why.
Ben

It's nice to see that it improved the situation.
I'm planning to do the following:

Verify if there are any other places that deal with line endings in the code;
Verify if either windows, ipython or ipython on windows require any special line-ending;
If this is the best we have for windows, then:

Check for windows also before starting the ipython interpreter, so we start --simple-prompt for windows.
try to find a way to deal with new-lines on --simple-prompt

Out of curiosity, have you tried the mapping I suggested as answer to this issue with my branch?
I think it might work better now as the line ending is somewhat better.
map <F5> <Cmd>lua require("iron").core.send(vim.api.nvim_buf_get_option(0,"ft"), vim.api.nvim_buf_get_lines(0, 0, -1, false))<Cr>

Regarding your keymaps, I think your mapping <localleader>s clashes with iron's default <localleader>sl, which leaves nvim pending for a while waiting for your input. You can disable
that by setting let g:iron_map_defaults = 0, but you'll have to map ctrand cp yourself or you can unmap <localleader>sl, which is also mapped to <Plug>(iron-send-line).

First, let g:iron_map_defaults = 0 really sped up my single line submit. Thank you!

Regarding finding a way to deal with new-lines on --simple-prompt, I know it's hideous, but this vmap works perfectly on my system:

vmap <localleader>s :lua lower, upper = unpack(vim.api.nvim_call_function("Show_position", {})); my_table = vim.api.nvim_buf_get_lines(0, lower - 1, upper, false); for i = 1, table.getn(my_table) do require("iron").core.send(vim.api.nvim_buf_get_option(0, "ft"), my_table[i]) end; require("iron").core.send(vim.api.nvim_buf_get_option(0, "ft"), "\n\r");<Cr><Cr>

Something's blocking me from mapping F5, but I mapped xyz to your command, while still in the test branch, and here's what it does:

In regular iPython, it sends all the code of the original file, but does not execute it. If I switch to
the console and press enter, there is a syntax error to a bad character that is invisible in the
console. After entering the code, it's showing up as a "?" (as in print('first line')?)
In --simple-prompt iPython, all the code is executed but without newlines, leading to syntax
errors.

It looks like I might have got the order wrong. In linux it's \n only. In win, it's \r\n, not \n\r. I just pushed a fix for that. Hopefully that'll fix it definitely :)

@hkupty I wish I had good new for you. I stayed on the same branch and ran :PlugUpdate and I saw a small change indicated. I disabled my custom functionality, restarted vim and tried everything over again. Unfortunately, it just didn't seem any different.
I'm happy to keep testing changes as long as you keep sending them, but I am bearish on the default iPython doing what we want it to, at least in its current incarnation. I bet if we went back to version 4 it'd be a delight.

There might be a way, based on prompt-toolkit's documentation:

A side effect of this is that the enter key will now insert a newline instead of accepting and returning the input. The user will now have to press Meta+Enter in order to accept the input. (Or Escape followed by Enter.)

I'll try to implement esc+enter for ipython and I'll let you know :,D

Great news. I found another hardcoded linefeed (\n or \13), specifically in python's unique formatting (bracketed paste + return, which itself is a form of esc+enter), and I made that one also use system-dependant line ending.
I'm really glad you're helping me out here as I don't have a windows machine to test this.

Glad there are still unexplored avenues. I updated this morning. iPython is still acting the same. I tried it with ordinary python 3.6.8 and it behaved more like simple-prompt mode on iPython, executing but no line breaks. Screenshots at the bottom. You'll see I have a few shell commands in the mix. These work perfectly when visually highlighting and pressing ctr to send to Powershell.
Happy to help and you're doing me a huge solid by building these tools. I've been looking for something that gets me Slimux-like functionality on Windows. Cygwin makes most REPLs unusable and WSL makes me go through 20 steps to see a plot.
If you'd like to interactively debug over Hangouts or something, I'm free most of the weekend (on Eastern Standard Time).

Based on what you described, I might have actually swapped CR and LF when implementing the windows version. If this doesn't work, then I think we'll be faster doing a Hangouts sessions.
As iron provides APIs, as well as other projects I have, like nvimux, we might think of a way of integrating them to get some functionality like that. :)

Let's jump on Hangouts. Nothing is changing for me when I make these updates. My gmail id is the same as the github id.

One of the things I'm learning about is this "Prompt Toolkit," which I think is causing all the issues for iPython. The rlipython tries to bring readline back but it's got some issues with IPython 7.


rclone not returning expected error code on Windows

I run a startup script on windows 7 ultimate 32-bit to backup some documents to dropbox automatically as soon as windows starts. My script checks the exit code generated by rclone and shows error message if it is not 0. The problem is when there is no internet connection rclone exits with exit code of 0 !
rclone tries 3 times to connect to dropbox and ends with error each time. But at the end it shows no errors !

Could you try this again with echo %ERRORLEVEL% after rclone has run?
As you can see when I try it in my Windows 7 VM, disabling networking with Virtualbox, I get the correct error level.
Thanks
Nick

@jackools - did Nick's proposal help you?

Yes. I found the problem. There was an error in my script which caused errorlevel for rclone to be always 0.
I added setlocal enabledelayedexpansion to the start of my script and the problem is solved.
This had nothing to do with rclone exit code and was a windows CMD problem.
Cheers.


Chart not drawing on Chrome version 45 (CRITICAL)

Chat will not draw on chrome version 45 (Latest update)

Hi @warapitiya, for me on mac everything works fine in the current chrome version 45.

Could you please provide information about your system (OS, full chrome version number)
Does the demo work for you http://grafiddle.github.io/angular-chart/ ?
Please open the console and copy us the errors.

###System:

OS : Mac
Chrome : Version 45.0.2454.85 (64-bit)

Tried on different Mac and Windows machines same happens. But when I move to Firefox it works fine. Also tired on Angular 1.4.0 & 1.4.5

MMh, it works all right in my browser with the exact same version, but I still don't get if the demo isn't working for you or the integration in your project?
And the error log would be nice to have.

We were not able to reproduce this bug without additional information about the failing configuration.