Feature: Custom Host improvements + Detect remote based on domain

My remote is like this: https://gitlab.common.cloud.tra.lala/tra/la/la-pltf/tra-pltf/lala-at/capacity/. It can be easily seen that it's a gitlab remote.
I would like when adding a custom host, to have a "copy from predefined template" dropdown which takes all settings from one of the default remotes from GitLink (Gitlab, Github, Gitea, etc.). I don't wanna have to add all of the "template fields" manually when they don't change:

It would be even nicer if maybe based on the domain gitlab.common.cloud.tra.lala, Gitlink could detect that this is a gitlab remote automatically, without me needing to create a custom host. In this case, in the notification I would get a message We've detected your remote as "Gitlab". If this is not correct, please select your remote and the same button as we get now.

One thing which works right now is to not set a Custom Host, but instead simply select Gitlab as host. The problem is i need to do this for every new repository i clone, which is less than ideal.

Yeah, having something in the plugin settings to register additional domains for a host would be nice for this. I'll take a look next week

This works with a minor caveat: it does not work right after cloning a project - the Intellij project window needs to be closed and reopened.
Step by step repro:

have intellij open with an existing project (p1) and have already setup the custom hosts.: custom.gitlab is my host
using File-> New->Project from Version Control, clone the repository https://custom.gitlab/myrepo
a new intellij window opens and intellij starts importing the project and dependencies etc. README is open by default
❌ if i right click on the readme, there's no gitlink entries
close the window for project myrepo, leave the other one open (p1)
open the project myrepo
✅ if i right click on readme (file is still open since last time), there are gitlink entries

Now it's even worse: step 6. is also broken: the host is not autoselected even after a project restart.
So with v4.1.4 i need to manually set the host, even though i have the domain registry set up.
IntelliJ IDEA 2022.2 EAP (Ultimate Edition)
Build #IU-222.2270.31, built on May 18, 2022
Licensed to IntelliJ IDEA EAP user: Cristian Pasat
Expiration date: June 17, 2022
Runtime version: 17.0.3+7-b423.10 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 10 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 6096M
Cores: 12
Registry:
    debugger.click.disable.breakpoints=true
    documentation.show.toolbar=true
    debugger.valueTooltipAutoShowOnSelection=true

Non-Bundled Plugins:
    some.awesome (1.14)
    org.nik.presentation-assistant (1.0.9)
    lermitage.intellij.extra.icons (2022.1.3)
    com.github.b3er.idea.plugins.arc.browser (0.32)
    org.asciidoctor.intellij.asciidoc (0.37.17)
    com.intellij.plugin.adernov.powershell (2.0.10)
    uk.co.ben-gibson.remote.repository.mapper (4.1.4)
    com.intellij.kubernetes (222.2270.31)
    BrowseWordAtCaret (3.0.5)
    izhangzhihao.rainbow.brackets (6.23)
    AceJump (3.8.7)

Kotlin: 222-1.7.20-dev-796-IJ2270.31

Weird, I couldn't reproduce this on my development machine, but I could on different machine. I've reverted a change that I suspected to be the most likely culprit which seems to have resolved the problem on the secondary machine i was testing with. Can you confirm what behaviour you're seeing now?

Tested again, the behaviour is smilar to my comment https://github.com/ben-gibson/GitLink/issues/191#issuecomment-1131227704.
i will copy paste it here for freshness:
Step by step repro:

have intellij open with an existing project (p1) and have already setup the custom hosts.: custom.gitlab is my host
using File-> New->Project from Version Control, clone the repository https://custom.gitlab/myrepo
a new intellij window opens and intellij starts importing the project and dependencies etc. README is open by default
❌ if i right click on the readme, there's no gitlink entries
close the window for project myrepo, leave the other one open (p1)
open the project myrepo
✅ if i right click on readme (file is still open since last time), there are gitlink entries


PHOENIX-6476 Index tool when verifying from index to data doesn't cor…

…rectly split page into tasks (#1240)

PHOENIX-6476 Index tool when verifying from index to data doesn't correctly split page into tasks

Fix failing tests, add comments

Break early when the matching set is found

@swaroopak cherry-pick to master

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  8s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

-1 :x:
mvninstall
17m 21s
root in master failed.

+0
hbaserecompile
24m 47s
HBase recompiled.

+1 :green_heart:
compile
1m  5s
master passed

+1 :green_heart:
checkstyle
0m 33s
master passed

+1 :green_heart:
javadoc
0m 53s
master passed

+0 :ok:
spotbugs
3m 21s
phoenix-core in master has 965 extant spotbugs warnings.

_ Patch Compile Tests _

-1 :x:
mvninstall
9m 38s
root in the patch failed.

+0
hbaserecompile
19m 59s
HBase recompiled.

+1 :green_heart:
compile
1m  3s
the patch passed

+1 :green_heart:
javac
1m  3s
the patch passed

-1 :x:
checkstyle
0m 34s
phoenix-core: The patch generated 12 new + 126 unchanged - 2 fixed = 138 total (was 128)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 50s
the patch passed

+1 :green_heart:
spotbugs
3m 32s
the patch passed

_ Other Tests _

-1 :x:
unit
114m 58s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 35s
The patch does not generate ASF License warnings.

172m 53s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1248/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1248

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaserebuild hbaseanti checkstyle compile

uname
Linux 998cc1b94b45 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
master / b6d9338

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

mvninstall
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1248/1/artifact/yetus-general-check/output/branch-mvninstall-root.txt

mvninstall
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1248/1/artifact/yetus-general-check/output/patch-mvninstall-root.txt

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1248/1/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1248/1/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1248/1/testReport/

Max. process+thread count
11416 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1248/1/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


State vs County data on map

Unclear if this is a bug or as intended, however this causes a poor experience.
Appears as though state of New York either a) extends beyond the county boundaries or b) certain counties are not included on map.
Result: Looks like an odd sliver of geography that has all of NY State's data associated with it.
Recommendation: If counties are available, show the counties only. Otherwise offer a toggle to view State-level data only.

Fixed!


Plan-626 mail history endpoint

you're missing the changes to the rbac task to let staff see everyone's? or is it already there?

The RBAC permissions were already there. There is code for mail_history in the rbac rake.
  "mail_history": {
      "index": true,

....
},


Create AYS template for 0-stor server

In this milestone the tlog will change its backend to use https://github.com/zero-os/0-stor instead of ardb.
We need to create an AYS template and logic in the SAL to deploy the 0-stor servers during the installation of the storage infrastructure.
Requirements :

[x] tlog AYS template
[x] Logic in SAL to deploy the 0-stor on top of disk like we do for arbd

Software Version
112ce78e9924585b2bed71c4fdf87df6db2f1c57


docs(cord): 03, 04, 05, 06, doc template created

Hey, I can't see what conflicts are in the branch, Could you help me out with that?

does it work now? I updated my branch to sync with the core repo so hopefully that's all I needed to do


Add Atom feeds for new beatmaps

Inserts a link in the head of every page to a feed of newly-uploaded
beatmaps. Additionally, when viewing a specific user's uploads, a
user-specific feed will be inserted.
Browsers/browser extensions will detect this and provide a button to
subscribe to the feeds.
The feed itself contains the beatmap image, information, as well as an
enclosure link to the actual beatmap zip file. With compatible feed
readers, this will enable easy auto-downloading.
Atom was chosen over RSS because it's a much cleaner specification and
pretty much every feed reader supports both anyway.
Fixes #20

@Byorun Should be all fixed up. I added the master -> theme redirection and added the feeds to the bulma theme.


Backporting fixes to 1.14.0

This is a backport of the following PRs to fix the actual issue, https://github.com/rust-lang/rust/issues/37969.

https://github.com/rust-lang/cargo/issues/3311 - first attempt to fix OpenSSL linkage on OSX
https://github.com/rust-lang/cargo/issues/3315 - second attempt to fix linkage
https://github.com/rust-lang/cargo/issues/3325 - fix a flaky test causing lots of CI problems
https://github.com/rust-lang/cargo/issues/3332 - actual fix for OpenSSL linkage on OSX
https://github.com/rust-lang/cargo/issues/3345 - first PR for automation changes
https://github.com/rust-lang/cargo/issues/3350 - second PR for automation changes
https://github.com/rust-lang/cargo/pull/3326 - update git2 to support netbsd
https://github.com/rust-lang/cargo/pull/3331 - update git2 to fix segfaults in tests
https://github.com/rust-lang/cargo/pull/3342 - update git2 to fix cert paths

r? @brson
(rust_highfive has picked a reviewer for you, use r? to override)

 Warning

Pull requests are usually filed against the master branch for this repo, but this one is against rust-1.14.0. Please double check that you specified the right target!

@bors: r+

:pushpin: Commit 6eb113a has been approved by alexcrichton

:hourglass: Testing commit 6eb113a with merge f91900c...

:broken_heart: Test failed - status-travis

Looks like that's another flaky test on OSX. That was fixed in https://github.com/rust-lang/cargo/pull/3331 which requires backporting https://github.com/rust-lang/cargo/pull/3326 as well. Those two PRs introduced a regression, however, which was fixed in https://github.com/rust-lang/cargo/pull/3342. I've now backported all three.

@bors: r+

:pushpin: Commit 1bb340e has been approved by alexcrichton

@bors: r+

:pushpin: Commit adf9312 has been approved by alexcrichton

:hourglass: Testing commit adf9312 with merge 2ada218...

:broken_heart: Test failed - status-appveyor

@bors: retry

:hourglass: Testing commit adf9312 with merge 6423f34...

:broken_heart: Test failed - status-travis

@bors: r+

:pushpin: Commit ea380cf has been approved by alexcrichton

:hourglass: Testing commit ea380cf with merge cf0b0bc...

:broken_heart: Test failed - status-travis

@bors: r+

:pushpin: Commit 977f263 has been approved by alexcrichton

@bors: p=1

:hourglass: Testing commit 977f263 with merge 8d63784...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 8d6378421598cd5e0effc2216a3c5a4d9fc0f493 to rust-1.14.0...


【Bug】Bug Need fix  -- dismatch output dimension with gloden

https://github.com/bytedance/ByteMLPerf/blob/c1d1835738cc17d974197f809fa503ec84e32d4d/byte_infer_perf/llm_perf/backends/GPU/gpu_scheduler.py#L60
Hi, We followed your script to test and found that there is a problem here, which needs to be modified
            # 5. add result to packet
            for i, gen_res in enumerate(generation_results):
                if gen_res.finish_reason:
                    batch[i].finish()
                batch[i].add_result(gen_res)

it is correct here. There are two possible reasons to finish the task: 1. the generated token_id is eos_token_id; 2. generated token_id len exceed max_new_tokens. we always add current token_id to output, and finish task based on finish_reason.

however, when we run on A100, it will raise an error if we do not change to the following modification. Please confirm it on chatglm case.

however, when we run on A100, it will raise an error if we do not change to the following modification. Please confirm it on chatglm case.

chatglm is out-of-date, and it will be removed later. There is a update today, you can try chatglm2 instead.


jenkins build git checkout failed

it happens randomly in deploy single box or cluster phase, log:
+ sudo docker exec -i 729fb7a9c71504de08c3f354864979f14a3a32ff53ff248c4e18e11110f1ab6d /bin/bash
++ echo PR-1840
++ cut -d- -f 2
++ echo PR-1840
++ cut -d- -f 2
+ rm -rf /cluster-configuration/cluster-configuration.yaml
+ rm -rf /cluster-configuration/k8s-role-definition.yaml
+ rm -rf /cluster-configuration/kubernetes-configuration.yaml
+ rm -rf /cluster-configuration/services-configuration.yaml
+ cd /pai
+ [[ PR-1840 == PR* ]]
+ git fetch origin pull/1840/head:PR-1840
From https://github.com/Microsoft/pai
 * [new ref]         refs/pull/1840/head -> PR-1840
+ git checkout PR-1840
fatal: Unable to create '/pai/.git/index.lock': File exists.

If no other git process is currently running, this probably means a
git process crashed in this repository earlier. Make sure no other git
process is running and remove the file manually to continue.

Fixed.


[Request] Compatibility with DrexHD's Vanish

Is your feature request related to a problem? Please describe.
When a server staff member has used /vanish, they are still subject to AfkPlus' automatic state changes (e.g., time-based setting of AFK status, movement-based clearing of AFK status). This reveals a vanished staff member to still be connected to the server.
Describe the solution you'd like
AfkPlus should ignore vanished players.
Describe alternatives you've considered
N/A
Additional context
N/A

This was added to my Multi Version branch.  The Vanish Mod support is new, and only partially tested.


fix: zh-cn learning environment page redirect

https://kubernetes.io/zh-cn/docs/setup/learning-environment/, align with EN version
Before:
No redirect
After:
Will redirect to https://kubernetes.io/zh-cn/docs/tasks/tools/

/lgtm

/approve


Random symbols in code

The code examples contain some random/garbled characters in them. For example, &#.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 24bd5a82-a8bf-e0ef-aa40-5bf57a3cdca4
Version Independent ID: 7b108cb7-d99b-abd2-d6ae-2c6690051d36
Content: Local and Global MS-DOS Device Names - Windows drivers
Content Source: windows-driver-docs-pr/kernel/local-and-global-ms-dos-device-names.md
Product: windows-hardware
GitHub Login: @windows-driver-content
Microsoft Alias: windowsdriverdev

Thanks for catching that, @Arush-Agarampur. I made the fix in the source and it'll go live when we next update later today.


unable to run vim-plug on WSL2

Cannot use PlugInstall or any other command in Vim or Neovim for WSL2. (windows 10)
Followed installing instructions but I always get a message:
E492: Not an editor command: PlugInstall
vim version and nvim version below
:version
VIM - Vi IMproved 8.1 (2018 May 18, compiled Apr 15 2020 06:40:31)
Included patches: 1-2269
Modified by<EMAIL_ADDRESS>Compiled by<EMAIL_ADDRESS>Huge version without GUI.  Features included (+) or not (-):
+acl               +cindent           +cursorshape       +file_in_path      +jumplist          +mksession         +mouse_xterm       +printer           +sound             +terminal          +virtualedit       -xim
+arabic            -clientserver      +dialog_con        +find_in_path      +keymap            +modify_fname      +multi_byte        +profile           +spell             +terminfo          +visual            -xpm
+autocmd           -clipboard         +diff              +float             +lambda            +mouse             +multi_lang        -python            +startuptime       +termresponse      +visualextra       -xsmp
+autochdir         +cmdline_compl     +digraphs          +folding           +langmap           -mouseshape        -mzscheme          +python3           +statusline        +textobjects       +viminfo           -xterm_clipboard
-autoservername    +cmdline_hist      -dnd               -footer            +libcall           +mouse_dec         +netbeans_intg     +quickfix          -sun_workshop      +textprop          +vreplace          -xterm_save
-balloon_eval      +cmdline_info      -ebcdic            +fork()            +linebreak         +mouse_gpm         +num64             +reltime           +syntax            +timers            +wildignore
+balloon_eval_term +comments          +emacs_tags        +gettext           +lispindent        -mouse_jsbterm     +packages          +rightleft         +tag_binary        +title             +wildmenu
-browse            +conceal           +eval              -hangul_input      +listcmds          +mouse_netterm     +path_extra        -ruby              -tag_old_static    -toolbar           +windows
++builtin_terms    +cryptv            +ex_extra          +iconv             +localmap          +mouse_sgr         -perl              +scrollbind        -tag_any_white     +user_commands     +writebackup
+byte_offset       +cscope            +extra_search      +insert_expand     -lua               -mouse_sysmouse    +persistent_undo   +signs             -tcl               +vartabs           -X11
+channel           +cursorbind        -farsi             +job               +menu              +mouse_urxvt       +postscript        +smartindent       +termguicolors     +vertsplit         -xfontset
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -Wdate-time  -g -O2 -fdebug-prefix-map=/build/vim-iU6mZD/vim-8.1.2269=. -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim        -lm -ltinfo -lnsl  -lselinux  -lcanberra -lacl -lattr -lgpm -ldl     -L/usr/lib/python3.8/config-3.8-x86_64-linux-gnu -lpython3.8 -lcrypt -lpthread -ldl -lutil -lm -lm

:version
NVIM v0.5.0-dev
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/cc -g -O2 -fdebug-prefix-map=/build/neovim-OqQfCc/neovim-0.5.0+ubuntu2+git202104182337-66f9dd3c6-d569569c9=. -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Og -g -Wa
ll -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_
GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/build/neovim-OqQfCc/neovim-0.5.0+ubuntu2+git202104182337-66f9dd3c6-d569569c9/build/config -I/build/neovim-OqQfCc/neovim-0.5.0+ubuntu2+git202104182337-66f9dd3c6
-d569569c9/src -I/build/neovim-OqQfCc/neovim-0.5.0+ubuntu2+git202104182337-66f9dd3c6-d569569c9/.deps/usr/include -I/usr/include -I/build/neovim-OqQfCc/neovim-0.5.0+ubuntu2+git202104182337-66f9dd3c6-d569569c9/build/src/nvim/auto -I/build/neovim-
OqQfCc/neovim-0.5.0+ubuntu2+git202104182337-66f9dd3c6-d569569c9/build/include
Compiled by buildd@lgw01-amd64-022

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info

Type:

[x ] Bug
[ ] Enhancement
[ ] Feature Request
[ ] Question

OS:

[ ] All/Other
[ ] Linux
[ ] OS X
[x ] Windows

Vim:

[x ] Terminal Vim
[ ] GVim
[x ] Neovim

Followed installing instructions

Which command did you run?

Vim and NeoVim commands as documentation states:
curl -fLo ~/.vim/autoload/plug.vim --create-dirs \
    https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim

and
sh -c 'curl -fLo "${XDG_DATA_HOME:-$HOME/.local/share}"/nvim/site/autoload/plug.vim --create-dirs \
       https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim'

solved with a pretty convoluted workaround reading the:versioninfo output
Seems that VIM root folder in WSL is/instead of  $HOME so placed the VIM config file in there inside a folder. Chowned to my user and then voilá. PlugInstall worked.
.vim/vimrc
Then NeoVim, reading :version info the init file seems to be at
"$VIM/sysinit.vim"
Odd enough, that folder in WSL is the $HOME folder  as in any other linux distribution
/home/user
So I created a file named sysinit.vim with all my configs and voilá. Working again....

we run curl -fLo ~/.vim/autoload/plug.vim --create-dirs \https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim and get the error:curl: (60) SSL certificate problem: self signed certificate More details here: https://curl.haxx.se/docs/sslcerts.html
So how to solve it ?

Thank you this worked for me too.
Had to create sysinit.vim in user\(username)\ folder. It worked
Neovim
Windows 10

I got same issue with vim on Ubuntu (WSL) and solved as below.
1. command:
curl -fLo ~/.vim/autoload/plug.vim --create-dirs
https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
2. create the ~/.vimrc file if not exist
As i run vim --version we have the following output, then we know
system is reading .vimrc file in home folder
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
defaults file: "$VIMRUNTIME/defaults.vim"
fall-back for $VIM: "/usr/share/vim"
then run following to create file if not yet have.
cd ~; touch .vimrc
3. in the .vimrc
call plug#begin(has('nvim') ? stdpath('data') . '/plugged' : '~/.vim/plugged')
" Declare the list of plugins.
Plug 'tpope/vim-unimpaired'
" List ends here. Plugins become visible to Vim after this call.
call plug#end()
Key point is because we put the file in autoload folder, it only load the plugin if
some function is called in the file.
Below is from https://learnvimscriptthehardway.stevelosh.com/chapters/53.html

Autoload lets you delay loading code until it's actually needed. You'll take a slight performance hit overall, but if your users don't always use every single bit of code in your plugin autoloading can be a huge speedup.
Here's how it works. Look at the following command:
:call somefile#Hello()
...
vim will load autoload/somefile.vim....

4. restart vim

call plug#begin(has('nvim') ? stdpath('data') . '/plugged' : '~/.vim/plugged')

I recommend that you keep it simple and call plug#begin without an argument unless you want to install plugins in a non-default directory. i.e. call plug#begin()

thank you @junegunn , it would be more simple to call call plug#begin() only.


Added more info

Added more information on how to correctly create the instance of a durable function.

@Neha-Kochhar : Thanks for your contribution! The author, @cgillum, has been notified to review your proposed change.


Docs: Updates CommandManager documentation

Alright! Although, there is no need to document the self parameter in methods.


Create online database of Open Science resources

The grand goal of the project looks more and more like a full database of resources for open science.   It would need to a searchable, sortable database with a flexible schema.   For example, a NoSQL database of some sort.
Most resources would need the following data:
Basic Type:  Organization, Project, Conference, Lecture, etc.
Contact info including URL, original content date, last edit date, last confirmed date
Organizations:
Name including abbreviations, logo, slogan
Legal status, approximate membership, founders and primary donors, contact info, focus, domain (or "cross diciplinary")
Projects:
Contributors sought, e.g., "in house", "post-docs", "citizen scientists"
Domain, scope, short and long summaries,
Name, contact info,
If the project goes this way, I expect discussions about schema will continue for the life of the project.

I have not enough experience with databases to chime in here. However, I would like to follow the proven Software Carpentry (SWC, http://software-carpentry.org/) and Data Carpentry (http://www.datacarpentry.org/) workflows with the material hosted on GitHub as markdown. See e.g. the SWC lessons here: http://software-carpentry.org/lessons/. The material is then directly used for GitHub pages.
Such a scheme hopefully lowers the threshold for contributions.

While I do not doubt that might be useful I personally would speak against such a collection of as part of this project. The main aim should be to compile (timeless) core principles. Maintaining the content of database would be out of scope. Maybe an option for a later spin-off.

@aleimba brings up the issue of making it easy for people to contribute; hence the wish for a good online database tool with a simple web interface.  Unfortunately, contributions to long lists in GitHub or on Wikipedia tend to become increasingly intimidating as the lists grow.  A comment thread has the lowest technical barrier for a new contributor and the highest load for an approver or editor.   A good database web page would provide a low technical barrier for a new contributor and a low load for an approver or editor.
@konrad suggests a compilation of timeless principles.   To date, there is no single agreed upon truth but a continuously deepingly understanding of the issues.   There are the Budapest Open Access Initiative Statement of Principles, the Panton Principles, and more each day.   Having a list of these in a database would appear to be a good start.   More discussion might create an additional list.

For all topic suggestions we have an etherpad collecting material and ideas: https://pad.okfn.org/p/OpenScience101topicsuggestions

For an example of how such a collection of resources on a topic might look like, see https://www.biocatalogue.org/ .

Promo site for the researchers to go open
http://whyopenresearch.org/


Update “Grace Resources” location page

Let’s add a website address to the “Grace Resources” location page. We might also want to change the name from “Grace Resource Center, Inc” to something more friendly, like “Grace Resource Center”.
You can see the page here…
https://foodoasis.la/food-pantry/grace-resource-center-inc-/
And you can edit here…
https://github.com/foodoasisla/site/edit/master/_food-pantry/grace-resource-center-inc-.md
Google Maps may have more information…
https://goo.gl/maps/oL4o1gaKucn
And also Yelp…
https://www.yelp.com/biz/grace-resource-center-lancaster
Bonus Points: Change the name of the file to something simple like “grace-resource-center”. This will make the URL a little friendlier. To make this work, we also need to update the “uri” attribute inside the file.

💯 Patrick!
The updated page is live…
https://foodoasis.la/food-pantry/grace-resource-center/


provide support for https://openrouter.ai/

provide support for https://openrouter.ai/

add the following to utils/providers.py:
class OpenRouterProvider(LLMProvider):
def get_client_config(self) -> Dict[str, str]:
return {
"api_key": os.environ.get("OPENROUTER_API_KEY"),
"base_url": "https://openrouter.ai/api/v1",
}
def get_provider_name(self) -> str:
    return "openrouter"

PROVIDER_MAP = {
"openai": OpenAIProvider(),
"together": TogetherAIProvider(),
"ollama": OllamaProvider(),
"groq": GroqProvider(),
"anthropic": AnthropicProvider(),
"openrouter": OpenRouterProvider(),
# "google": GoogleProvider(),
\n

You can test it like:
from sentient import sentient
import asyncio
import nest_asyncio
nest_asyncio.apply()

custom_instructions = """
1. Directly go to youtube.com rather than searching for the song on google!

"""

#use with open ai
result = asyncio.run(sentient.invoke(
    goal="play shape of you on youtube",
    task_instructions=custom_instructions,
    provider="openrouter",
    model="openai/gpt-4o-2024-08-06"))

which model are you trying to use using open router?

https://github.com/sentient-engineering/sentient/pull/30

feel free to open this if you face any issue


Form ID for multiple forms seems like a implementation detail

And therefore shouldn't need to be handled by the end user. Ideally, sveltekit-superforms would generate a random ID and automatically assign to each form and pass it from client to server and vice-versa.

This could actually work automatically with use:enhance enabled. Then the client can both generate an id and add it to the payload when posting.
Without use:enhance, which is quite rare (especially combined with multiple forms), a requirement would then be to add a hidden field with the magic id variable.
Just have to think if there is some special case where this is not possible.


Friendlier features :)

Finally carved out the time to get to this...

Awesome work, this is great! Thanks so much Oliver!
Two small things before I merge:

Lets not mention the universal rendering just yet, it's going to take a bit more time before that is launched. (I want to make sure it's very solid and useable with different systems)

Lets mention the generators, either as its own point or in some description. (I think they're worthy of their own point though) When users run $ npm run generate in the terminal, they can quickly add new components, containers (+ reducers, actions, constants), routes, sagas and selectors without having to remember to import things or setting up the boilerplate code.

Thank you so much, this is great start!

Thanks for the feedback: the generators sound awesome & well worth highlighting!
I thought that letting folks know that SSR is at least under active discussion might be a good thing (since no deadline is mentioned), but I get your rationale. I'll be making an exploratory PR for that shortly :)

Awesome, looking forward!

I'll merge it for now, we can do incremental updates while it's live anyway. Awesome work @oliverturner, thanks for the help & discussions!


METRON-2266: REST debug instructions

Contributor Comments
This PR adds instructions to the metron-rest README for starting the REST application in debug mode in Intellij.  A Maven profile is provided along with setup instructions and screenshots.
Testing
Spin up full dev and follow instructions in the Local Development section of the metron-rest README.  The REST application should start without error and be available at http://localhost:8080/swagger-ui.html.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[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)?

For code changes:

[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 metron folder via:
mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh

[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?

For documentation related changes:

[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
mvn site

[x] Have you ensured that any documentation diagrams have been updated, along with their source files, using draw.io? See Metron Development Guidelines for instructions.

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

@merrimanr I see below exception when I start the REST, it's looking for a znode /hbase/hbaseid where as I see it as /hbase-unsecure/hbaseid in my full dev
`2019-09-27 12:59:55.685 ERROR 86632 --- [           main] o.a.h.h.z.RecoverableZooKeeper           : ZooKeeper exists failed after 4 attempts
2019-09-27 12:59:55.703 ERROR 86632 --- [           main] o.a.h.h.z.ZooKeeperWatcher               : hconnection-0x4065456c0x0, quorum=localhost:2181, baseZNode=/hbase Received unexpected KeeperException, re-throwing exception
org.apache.hadoop.hbase.shaded.org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /hbase/hbaseid
at org.apache.hadoop.hbase.shaded.org.apache.zookeeper.KeeperException.create(KeeperException.java:99) ~[hbase-shaded-client-1.1.2.jar:1.1.2]
at org.apache.hadoop.hbase.shaded.org.apache.zookeeper.KeeperException.create(KeeperException.java:51) ~[hbase-shaded-client-1.1.2.jar:1.1.2]`

+1 by verification, Thanks @merrimanr !!


Support for more than one project

This is the case of our own repo https://github.com/readthedocs/readthedocs.org, where we have the docs and dev projects.
Currently, using the action more than once will override the previous comment
https://github.com/readthedocs/readthedocs-preview/blob/1029696f6a69477ff98e50ddb239e649f86ec384/action.yaml#L51
We should make the comment easier to locate, instead of using a plain ---- as separator, we could use a comment as a delimiter of the start/end of the comment. For example:
<!-- rtd-preview {project} start -->
Content
<!-- rtd-preview {project} end -->

That way, the current "separator" would be part of the template itself
---
:books: Documentation preview :books:: {docs-pr-index-url}

I liked the idea of using an HTML comment for this! 👍🏼

This done in c70557245b0ae077da1a8aeef7f259e88f2916f6

I tested it at https://github.com/readthedocs/sphinx-hoverxref/pull/220 and it worked.


(DX) Rewrite to official nuxt 3 module-builder

I would like to recommend a rewrite of the current module structure to the official nuxt 3 module-builder.
I know that this module was developed really early but I think one can make it work with the current module-builder that has a support for TS which can help developers to have more type safe Storyblok actions.
If you like, I can create a PR with that change. I don't expect any breaking changes here as the composable and the module interface will be the same. The only difference will be the TS support.
Let me know what you think about it :)

Awesome work @alvarosabu !


Add E2E test: [Trigger] At least one red/orange/yellow GloFAS station should be visible

### Tasks
- [ ] Add E2E automation script

Moved to Dev Ops


Ocultar registro del navbar

Current dependencies on/for this PR:

main:

PR #97 👈

This comment was autogenerated by Freephite.


Adding of WatchGuard Reputation Authority

http://www.reputationauthority.org/lookup.php?ip=<IP_ADDRESS>

Closing. As it looks like Ian took care of this. PLease open another if not.


Quirks for Smartthings MultiV4

I am assuming this one will be left open until the accelerometer cluster can be properly implemented, but sending this one also due to battery reports working.


Update manifests/t/Tencent/QQ/<IP_ADDRESS>997/Tencent.QQ.locale.en-US.yaml

Fixes an issue where this package has multiple different monikers
Microsoft Reviewers: Open in CodeFlow

Needs Attention

@wingetbot run

[Policy] reset feedback

[Policy] Needs-Attention

@wingetbot run

@wingetbot run


blocks skipped in "Latest Blocks" display

I just noticed this on test.bitpay.com.

It also shows age as "a few seconds ago" for blocks that were mined earlier than that.

It's because the query is based on date and not block height, and since dates can be out of order, a block can exist on the previous/next day, or in the future, and not appear. It's more apparent on testnet.


The size of 'out' and 'rfp_feat' is not match

Thanks for your error report and we appreciate it a lot.
in resnet.py 305
out = out + rfp_feat
The size of 'out' and 'rfp_feat' is not match
Through debugging, I found that the problem lies in resnet.py lines of 607 RFP_ forward(). x = layer.rfp_ forward(x, rfp_ In feat), layer does not operate on img, resulting in x is tensor(img) in this statement. Finally, in the RFP_ In forward (), lead to The size of 'out' and 'rfp_feat' is not match.
In fact, I didn't make any changes to the program. I just called your resnet.py in my program.
I don't know if it's a version problem? We look forward to your reply.

Hi @sunpeng96
If the size doesn't match, it's likely that your input size does not satisfy the requirement of the backbone. You can start debugging from this.


Can only specify boundary conditions per-axis with ghost.ghost

As asked on SO
The current ghost.ghost function allows specifying a few different types of B.C. but they're always the same for both y-boundaries and both x-boundaries.  This makes perfect sense for periodic boundaries, but less so for Dirichlet boundaries.
As @mrocklin commented, ghost.ghost_internal can accomplish most of this but it would be good if it were exposed in ghost.ghost, e.g.
g = da.ghost.ghost(x, depth={0: 1, 1: 1}, boundary={0: 100, 1: 100, 2: 0, 3: 0})

Pinging @stefanv

In the scikit-image use-case, a feature that would be useful is to only ghost "to the inside" of the array, i.e. to ghost, but to crop the ghosted array to the original image extents.
The reason for this is that scikit-image has specialized handling of boundaries, which sometimes causes artefacts.  If ghosting pads out those edges, these (desired) artefacts will disappear.

@stefanv that is currently possible with ghost_internal.
Perhaps this would be best exposed by adding a internal_boundary keyword argument to da.ghost.ghost. Which takes dict keyed with axes and valued with depths. If an axis in this dictionary is not specified then it will be taken from the boundary kwarg. And if just the internal_boundary is specified for an axis, the external boundary will be zero.

Note I mixed up boundary and depth above, but have since edited the comment to fix this.^

There should be an easy way to say: "do what you normally do, just don't go outside the array boundaries"

Ideally this option ends up within the da.Array.map_overlap function which, I think, has the most user friendly API so far.  I think that this function came out of @cowlicks early work with skimage.
At the moment the boundary=None option defaults to reflect.  Perhaps None should actually mean "no boundary."

@mrocklin there are currently two arguments for specifying the ghosting. depth and boundary. Which, more verbosely, mean "depth of ghosting" and "external ghosting type". If someone specifies a ghosting depth, but no boundary type, I think they would still expect some ghosting to happen.
One reason reflect might be the default is because this is the behavior for some skimage filters.

@stefanv we could have an internal_ghosting_only=True/False kwarg in ghost. However I think an internal_depth kwarg would be valuable since it would allow the user to have internal ghosting which differs from external ghosting.

If someone specifies a ghosting depth, but no boundary type, I think they would still expect some ghosting to happen

I agree.  But would the expect ghosting on the boundary?

One reason reflect might be the default is because this is the behavior for some skimage filters.

This is a good reason to keep the default as reflect.  I wonder if we should set the default to boundary='reflect' in the function signature and then use boundary=None to mean internal ghosting only.

@gforsyth you can specify the external boundary conditions per axis.
In [1]: import numpy as np; import dask.array as da

In [2]: a = da.from_array(np.arange(16).reshape(4, 4), chunks=(2,2))

In [3]: g = da.ghost.ghost(a, depth={0: 1, 1:2}, boundary={0:42, 1:'reflect'})

In [4]: g.compute()
Out[4]:
array([[42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42],
       [ 1,  0,  0,  1,  2,  3,  0,  1,  2,  3,  3,  2],
       [ 5,  4,  4,  5,  6,  7,  4,  5,  6,  7,  7,  6],
       [ 9,  8,  8,  9, 10, 11,  8,  9, 10, 11, 11, 10],
       [ 5,  4,  4,  5,  6,  7,  4,  5,  6,  7,  7,  6],
       [ 9,  8,  8,  9, 10, 11,  8,  9, 10, 11, 11, 10],
       [13, 12, 12, 13, 14, 15, 12, 13, 14, 15, 15, 14],
       [42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42]])

But you cannot specify the internal boundary conditions, the internal boundary conditions just copy the elements of the chunks next to them. We could possibly change this, but I'm not sure this is what you want.
And currently the depth argument is the depth of the boundary for both internal and external boundaries. We could easily change this so this by adding a internal_depth argument which would default to be the same as depth if it is not provided.

I suspect that @gforsyth wanted to have different boundary conditions on the left vs right or top vs bottom, which is not currently supported.

That's what I was thinking of.  I was just playing around with solving PDEs in Dask and if you're doing something that's elliptic and you want to set one side of your domain to 0 and the other 3 to 100 that doesn't work the way ghost is currently set up.

@gforsyth Perhaps a good api here would be to allow tuples as values in the boundary argument like:
In [1]: import numpy as np; import dask.array as da

In [2]: a = da.from_array(np.arange(16).reshape(4, 4), chunks=(2,2))

In [3]: g = da.ghost.ghost(a, depth={0: 1, 1:2}, boundary={0: (33, 42), 1:('reflect', 66)}

In [4]: g.compute()
Out[4]:
array([[33, 33, 33, 33, 33, 33, 33, 33, 33, 33, 33, 66],
       [ 1,  0,  0,  1,  2,  3,  0,  1,  2,  3,  3, 66],
       [ 5,  4,  4,  5,  6,  7,  4,  5,  6,  7,  7, 66],
       [ 9,  8,  8,  9, 10, 11,  8,  9, 10, 11, 11, 66],
       [ 5,  4,  4,  5,  6,  7,  4,  5,  6,  7,  7, 66],
       [ 9,  8,  8,  9, 10, 11,  8,  9, 10, 11, 11, 66],
       [13, 12, 12, 13, 14, 15, 12, 13, 14, 15, 15, 66],
       [42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 66]])

Note that doing something like this with the depth argument would make internal depth ambiguous.
If I understand correctly this is distinct from what @stefanv wants.

I think that would work well for specifying the external boundaries.  Does it make any sense to also have a depth tuple possible?  You might need to have a reflection that's 2-deep for a Neumann boundary but only need a 1-deep for Dirichlet on the opposite boundary.

Hrrr.  Just realized that that would necessitate a separate depth kwarg for internal vs. external boundaries otherwise it's going to be very ambiguous.

Noting your example array
In [4]: g.compute()
Out[4]:
array([[33, 33, 33, 33, 33, 33, 33, 33, 33, 33, 33, 66],
       [ 1,  0,  0,  1,  2,  3,  0,  1,  2,  3,  3, 66],
       [ 5,  4,  4,  5,  6,  7,  4,  5,  6,  7,  7, 66],
       [ 9,  8,  8,  9, 10, 11,  8,  9, 10, 11, 11, 66],
       [ 5,  4,  4,  5,  6,  7,  4,  5,  6,  7,  7, 66],
       [ 9,  8,  8,  9, 10, 11,  8,  9, 10, 11, 11, 66],
       [13, 12, 12, 13, 14, 15, 12, 13, 14, 15, 15, 66],
       [42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 66]])

the external boundary depth doesn't particularly matter -- if it were the difference between a Neumann and Dirichlet boundary the extra bit of memory required to pad out a Dirichlet boundary one column further than necessary is negligible.
That said, g[:-2] seems to be a reflect while g[:-1] is Dirichlet.  I imagine it's just an editing error from mocking up the boundary tuple example but so long as both g[:-2] and g[:-1] were both 66 in the above example that would cover the use cases I have.

One thing to keep in mind when evaluating all these new options, is that
preferably all keywords should be usable in combination with each other.
The API becomes terribly convoluted when you have "use this keyword unless
than one is specified, in which case we change the meaning of the first or
ignore it".

Agreed.  My suggestion for a depth tuple is unnecessary (and also ignored @cowlicks pointing out the inherent ambiguity in such a setup).  I think allowing tuples in the boundary  argument is sufficient.

@gforsyth I'm giving a talk this weekend (about dask), so I'll probably get to this Monday. Unless someone beats me to it.
@stefanv how is this API for your usecase: boundary=None will mean no external boundaries, boundary={0:(1, None)} would pad the left boundary with ones, and not add a boundary on the right, and it will default to `boundary='reflect'.

Perfect.

@stefanv I think #681 partially serves your needs.


Fixed #5895: cast warnings.

@hardening fixed the warnings you saw along with a few others where we require const casts.


"IndexError: list index out of range" in FbTime.span_meta_to_date

There seems to be a problem with the code on line 68 in FbTime.py. The problem is in the array call for date_arr[2]. It seems to assume that the array is longer then 2 but in my case the array is only of length 2.
What is happening in these lines?

Hi Dylan, thanks for raising the issue. span_meta_to_date takes an argument span_str as an argument. Could you provide the contents of span_str where the IndexError occurs?

No problem.
It says: Friday, March 30, 2018 at 10:18pm UTC+02. It seems the data formatting is slightly different with the March.

Okay, the problem is caused by a second comma after "March 30". Fix involves removing the second comma if it exists. Please pull the master branch and confirm that the problem is fixed, then I'll close the issue. Thank you!


Element overlapping side-navbar

Graph's Menu bar is overlapping the main-nav bar.

Solution:
Try increasing z-index of side-nav
Graph is implemented in

Plot Graph
Integration
Differentiation
Laplace

You can test from any of the following

Read

Please assign this issue.

I would love to work on this issue. Please assign this to me?

@sayna3311 Sorry! First come first serve. Be active to our issues. New issues will be available soon.

@RituCs Feel free to ask doubts, if any

assign it to me gssoc21

Today is the last date @RituCs
11 March,2021 (11:59 PM IST)

I would love to work on this issue. Please assign this to me?

Do you want to contribute?

I would love to work on this issue. Please assign this to me?

Do you want to contribute?

Yes, I want to! :)

Feel free to ask your doubts, if any
Deadline 14 March,2021 (11:59 PM IST)

I'm a GSSOC'21 participant kindly assign me this issue. I would love to work in this.

@rk05-lenavo Do you want to work on this issue?

@sairish2001 Yes sir. Sure

Feel free to ask your doubts, if any
Deadline 21 March,2021 (11:59 PM IST)

Hi..I would like to work on this issue under GSSOC'21. Kindly assign me this issue.

@anjali7786 Go ahead
Feel free to ask your doubts, if any
Deadline 24 March,2021 (11:59 PM IST)


Warning: socket.send() raised exception [asyncio]

So I'm using this from an AUR package on Arch Linux, with ArmCord flatpak and arRPC (but this also happened to me back when i was using the normal discord app from base repos). After some time and probably some resource usage, the script just starts doing... this.

I can CTRL-C out of the script (and it floods my terminal with asyncio errors if i do that), launch it again and keep going, but that needs manual intervention. Maybe there should be a way to auto-restart the script if this kind of thing happens? Like, the script does not stop on these exceptions, but it also does not function until a restart.
This is the commit the AUR package is based on.

Perhaps there could be a change in the code where the tool closes upon an exception rather than remaining open. :thinking:
Discord-py-interactions does something like that. If a connection error occurs, then the Python program should be terminated. If you wish to keep it running in the event of a terminating exception, then you'll need an external script that will do that for you.
Although, that shouldn't really be the focus. The focus probably should be why this happens. It may be useful if you go to your configuration file (if it exists) and set the debug variable to true. It should look like this:
config.toml
[global]
debug = true

After that, send the error message here.

The error message is approximately 40 000 lines of this:
  File "/usr/lib/python3.12/asyncio/streams.py", line 741, in readexactly
    raise self._exception
  File "/usr/lib/python3.12/site-packages/discordrp_mpris/__main__.py", line 91, in run
    await self.tick()
  File "/usr/lib/python3.12/site-packages/discordrp_mpris/__main__.py", line 182, in tick
    op_recv, result = await self.discord.set_activity(activity)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/discord_rpc/async_.py", line 176, in set_activity
    return await self.send_recv(data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/discord_rpc/async_.py", line 144, in send_recv
    reply = await self.recv()
            ^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/discord_rpc/async_.py", line 163, in recv
    op, length = await self._recv_header()
                 ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/discord_rpc/async_.py", line 105, in _recv_header
    header = await self._recv_exactly(8)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/discord_rpc/async_.py", line 252, in _recv_exactly
    return await self.reader.readexactly(size)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

repeating over and over again.

Is there also a specific exception mentioned somewhere?

Just in case this wasn't obvious already, error handling is … not exactly the forte of this project. Partially because I personally didn't run into many but also because even when running into them, I wasn't sure what exactly to do to remedy the situation. Close the connection and try to start over? Close the application with an exit code to signal errors (and make the systemd unit fail)? Provide configuration for retries? Those are all questions I didn't want to answer back in the day and haven't really looked into again since.
I'll see if I can find some time in the coming weeks to overhaul the code since there are quite a few thinks I've learned since 2018.
Related: #11.


Adding webhooks for service and deployment resources

To be finished and proposed after the #776 is merged.

you need this for deployment and service: https://github.com/openstack-k8s-operators/dataplane-operator/blob/main/main.go#L144-L151

Done. Thanks for the pointer.

recheck - retry limit

recheck

This will need some adjustments to kuttl tests, along with rebase. Please do not merge until then.

New asserts should be in after rebase.

/retest

recheck

/lgtm

Cherry-picked ca02cfc383a2dc50496fcd74b5bae1ac40a82314 in https://github.com/openstack-k8s-operators/dataplane-operator/pull/809 to fix kuttl on main

recheck

recheck

/recheck - post-failure on docs build, gem file unavailable


add CompilationProblemResult interface to solve duplicate code problem

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

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

I really appreciate that you're avoiding code duplication but personally I believe you're doing it in the wrong way. You could obtain the same result avoiding to introduce a new interface just to reuse the 2 default methods in there with a "fake" inheritance. In particular you could move the implementations of those 2 default methods inside 2 static methods in an utility class and pass to it the object and message as arguments.
I'm closing this pull request. Please let me know if what I'm suggesting makes sense and you will send a second pull request. Thanks.

Ok, i'll add an utility class with static methods


Create bucket in Frankfurt region throws a location constraint error

I receive a location constraint error after running the following command:
aws s3api create-bucket --bucket $CONFIG_BUCKET_NAME --region $AWS_DEFAULT_REGION
$CONFIG_BUCKET_NAME=[allowed bucket name]
$AWS_DEFAULT_REGION=eu-central-1
The specific error is:
An error occurred (IllegalLocationConstraintException) when calling the CreateBucket operation: The unspecified location constraint is incompatible for the region specific endpoint this request was sent to.

Fixed.
Works with the core s3 command:
aws s3 mb $KOPS_STATE_STORE --region $AWS_DEFAULT_REGION


Adding a custom SDK resolver

Problem
The default SDK resolver loading only looks for resolvers in $(MSBuildToolsDirectory32)/SdkResolvers (source).
Most of the time, this path is going to be C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\SdkResolvers. Writing files here requires admin permissions.
My scenario: I'm looking for a way to share a common set of targets and props across ASP.NET Core's 500+ csproj files, which are scattered among repos. We've tried PackageReference, but continually run into limitations. I've written and tested a custom SDK resolvers. It seems promising, but there is no easy way to make this available for MSBuild for VS and dotnet.exe without getting elevated permissions to write into the VS folder and/or C:\Program Files\dotnet folder.
Request
Provide a way to register custom SDK resolvers without needing to write into the MSBuild tools folder.
Ideas

Similar to <UsingTask>, add  <UsingSdkResolver> directive that takes an assembly path.
Add another search path, such as $(MSBuildUserExtensionsPath)/$(MSBuildRuntimeType)/SdkResolvers

I would like to use this to make it easier to add support for other project types, like Rust. Ideally, a directory level configuration could point to a path containing an SDK. It'd work like directory.build.props where parent dirs are searched. I'd put that along the solution file.
Also, there should be a way (NuGet?) to distribute sdks. The aforementioned config file could point to a NuGet package with an SDKs folder in it, then it'd be automatically downloaded and added to the search path.
Then something like Visual Rust can package its targets as an SDK and distribute it on NuGet.

@onovotny fyi there is an issue for a NuGet resolver at https://github.com/NuGet/Home/issues/5220

@dasMulli Thanks for the pointer!
My ask when designing this feature is that it's not tied to .NET. That is, it should ideally support any project type that uses CPS to enable it to have its own SDK. The example I'm thinking of right now is Rust, but it can apply to any other language/platform.

Another example of the need for this: it's impossible to know of all possible installations of MSBuild. For example, OmniSharp (what powers VS Code) bundles the MSBuild runtime, which means the MSBuild folder and SdkResolver lookup path is %USERPROFILE%\.vscode\extensions\ms-vscode.csharp-1.12.0-beta4\bin\omnisharp\msbuild\SdkResolvers.

I would very much like to define a repo-level SDK for some project types that are custom to our repo. If MSBuild would be willing to search for SDKs similar to how @onovotny described, that would be awesome.

Would it be possible for MSBuildSDKsPath to behave like PATH in that you can have multiple paths to sdk folders (already on disk). MSBuildSDKsPath can be overridden by environment if I understood correctly

After reading some more of the discussions, it might be good to mention that for us it makes sense if a source tree can actually contain their own SDK(s) in the actual tree.
Having something like searching in the parent folders for an SDK config file would also help deployment on both developers and build machines, since they retrieve the source tree anyway.
I guess the resolver API would allow one to write a vs extension that actually scans parent folders for an SDK config file, but when I install this as a VS extension, will it also work from command line msbuild?

Would like to throw in my two cents, how I do the target resolution up to now:
<Import Project="$([MSBuild]::GetDirectoryNameOfFileAbove($(MSBuildThisFileDirectory), Smart.targets))\Smart.targets" />
That smart target file is located in the root folder of a branch / workspace and redirects to other targets that belongs to my build framework. From what I understood up to now, the SDK stuff is nothing else than two imports of a props and target file. So I think you could probably do something similar like I do.
The advantage is, whenever you want to change the build behavior for some projects under a specific folder you can simply throw a Smart.targets file within their parent folder and it will be automatically taken. Another advantage is of course that it doesn't matter where your projects are located, there is no relative path that needs to be updated.

Auto-import of props/targets file already exists - [Directory.Build.props / .targets](https://docs.microsoft.com/en-us/visualstudio/msbuild/customize-your-build#directorybuildprops-example) files in the directory hierarchy will automatically be imported.
The SDK feature is mostly about re-using shared logic so I don't think it will be common to add SDKs to a repo (but maybe if you have 3 different types of project and want 3 different imports..).

Would it be possible for MSBuildSDKsPath to behave like PATH in that you can have multiple paths to sdk folders (already on disk).

This is actually a good idea and could be used as quick-fix for problems like https://github.com/dotnet/cli/issues/6178 where some SDKs are only distributed in VS but you'll want the main SDKs to be loaded from the CLI folder and only fall back to a VS path. (current solution is to copy the SDK folder)

@dasMulli wow, thanks for the hint regarding the auto-import. That will help me alot. Is that already working in VS 2015/MSBuild 14 or has it been introduced with VS 2017 / MSBuild 15 ?

That feature is new in MSBuild 15

This issue is causing periodic problems for Roslyn contributors. While the .NET SDK gets installed into the expected directory, Roslyn always relies on a particular version of the SDK for reasons that vary over time. We would like the ability to restore the SDK itself as part of our Restore.cmd script, and have that SDK get resolved automatically as part of both build and IDE scenarios.
Leveraging this functionality will improve our ability to engage and retain external contributors by improving "pit of success" approach to development. Eventually we would like the complete restore process to happen inside Visual Studio (if/when necessary with minimal overhead), but until we reach that point a reasonable approach is Clone/Restore.cmd/Open solution. Until this feature is implemented, we are left with an unfortunate "manually installed things" step.

An orthogonal issue for these dev scenarios is probably support for a relative path in global.json (I can't find the issue now, I thought there was one in core-setup..).
That way a custom restore script could download a package into e.g. a .dotnet-cli folder and that version would then be used.

Leveraging this functionality will improve our ability to engage and retain external contributors by improving "pit of success" approach to development

Indeed. As the design stands now it's relatively easy to setup the command line build for a repo to "just work".  The build can fully bootstrap all of the needed components even on a clean Windows machine.
However the same is simply not true for the Visual Studio based experience. Open Roslyn.sln, Build and you're likely to be hit with an error message from our build
The 2.2.0 SDK is required to build this repo. It can be install here https://dotnetcli.blob.core.windows.net/dotnet/Sdk/2.2.0-preview1-007622/dotnet-sdk-2.2.0-preview1-007622-win-x64.exe

That's really unfortunate and frankly confusing to our users. Why is building from the command line possible when building from Visual Studio fails?

we are left with an unfortunate "manually installed things" step

Indeed. Worse is that it requires installing as "admin". Outside the initial VS install it shouldn't be necessary to use admin to build any repo. It's generally a sign that we need to be more easily extensible.

That's really unfortunate and frankly confusing to our users. Why is building from the command line possible when building from Visual Studio fails?

I use command line but it doesn't find msbuild https://github.com/dotnet/roslyn/issues/23564
This might be important; I don't have VS 15.x, just VS 15.5 Preview 3
I tried to manually run msbuild but there is a MSBuild.dll in the new sdk, not exe.
/cc @sharwell

Should I uninstall sdk and run restore  to download it? (I'm not sure if it does though)


ARROW-3024: [C++] Remove mutex in MemoryPool implementations

Codecov Report

Merging #2403 into master will increase coverage by 2.16%.
The diff coverage is 92%.

@@            Coverage Diff             @@
##           master    #2403      +/-   ##
==========================================
+ Coverage   84.67%   86.84%   +2.16%
==========================================
  Files         293      237      -56
  Lines       45459    42690    -2769
==========================================
- Hits        38492    37073    -1419
+ Misses       6926     5617    -1309
+ Partials       41        0      -41

Impacted Files
Coverage Δ

cpp/src/arrow/allocator-test.cc
100% <ø> (ø)
:arrow_up:

cpp/src/arrow/memory_pool-test.cc
100% <ø> (ø)
:arrow_up:

cpp/src/arrow/memory_pool-test.h
100% <100%> (ø)
:arrow_up:

cpp/src/arrow/memory_pool.cc
67.27% <90%> (+1.17%)
:arrow_up:

rust/src/array.rs

go/arrow/array/boolean.go

go/arrow/internal/testing/tools/bool.go

rust/src/memory_pool.rs

go/arrow/math/uint64_sse4_amd64.go

go/arrow/memory/buffer.go

... and 50 more

Continue to review full report at Codecov.

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


Wrong connection type colors after importing project

It happened to me multiple times. So I devided to report it as a bug.
I sticked to 3 default connection types, assigning them colors as follows:
development - green
test - orange
production - red
Everytime I export project and import onto other machine I got as follows:
development - no color (white)
test - green
production - red (unchanged)
It seems, that colour of dev env is always applied to test one. Maybe it's just array/collection shift while iterating objects. Just guess.
With regards

thanks for the bug report

Hello @michalk-k

development - no color (white)
test - green
production - red (unchanged)

This are default connection types colours.
When exporting a project to DBeaver on another machine, the connection type colour settings are not saved - the default ones are used.
As a workaround, you can create new connection types and colours and use them. These types must be preserved when exporting the project.


devnet network issue

yesterday I deployed 3 VM's and after e.g. 30 min upto 60 min I lost all network access to it
machines where in ghent datacenter
I lost connection for yggdrasil as well as webgateway as wel ipv4 (which was only configured on one)
it might be issue with network in ghent or so but we need to know
I think having this monitoring will help we are talking about, lets make sure we measure networks and maybe also network traffic between machines
K.

can we get the contract id or the node id? otherwise it might be hard to debug.

checked the contracts and they went on the grace period, and the deployments got paused. can you please fund this account with some TFTs, and let's see if they will go back to being reachable?

verified on devnet
made a multiple deployment and multiple contracts and went to grace period
after funding the account all the deployment in the next cycle got back up and working
steps made:

go to weblets
deploy vm
transfer your wallet to make contracts go grace
fund the profile again
wait for an hour
make sure that deployments are back online again


Negative offsets

Hi!
I have a somewhat strange request. My GPU is unstable if run on stock clocks, but works perfectly fine if slightly underclocked. Would it be possible to allow negative offsets in this application?
Thanks!

Hi, I no longer have an Nvidia GPU but my app already takes i32 as input so if the Nvidia control library supports negative values it should just work.

Huh, it works now. I could have sworn it crashed the last time I tried.
Sorry for that, and thanks!


the dockerhub image needs to be updated

https://github.com/buchgr/bazel-remote#useful-endpoints says that e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 should always be available.
Repro
docker run -v /path/to/cache/dir:/data -p 9090:8080 -p 9092:9092 buchgr/bazel-remote-cache
curl --head --fail http://localhost:9090/cas/e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Expected
200
Actual
curl: (22) The requested URL returned error: 404 Not Found
Notes
> bazel-remote % curl http://localhost:9090/status

{
 "CurrSize": 0,
 "MaxSize":<PHONE_NUMBER>,
 "NumFiles": 0,
 "ServerTime":<PHONE_NUMBER>,
 "GitCommit": "ae546fc99a1bd7addd63269879e634545cdfcc1b"
}
`

FWIW, I just tried building from master locally and this problem is fixed already.
I will leave the issue open as an indication that docker image needs to be updated. Please feel free to close it.

Right- sorry about that. I will leave this open until @buchgr is able to update dockerhub.

Done. Pushed master and v1.1.0.
Thanks @vors and @mostynb !


integration normalizr

Thank you for the work already done. This app is a great way to get started.
Could you point me in the right direction on how to integrate normalizr? (I want to be able to manage more complex relationships in the data...)

Could you please provide some context — what kind of API response you have and what data structure on the client you are looking for?

The data structure looks roughly like this:
collection
  pieceIds: [piece]
  name: string
  authorId: persona
  reviewerId: persona

piece
  collectionId: collection
  blob: string
  state: string

persona
  name: string
  email: string

The API returns the ids, but they are not mapped to the respective models. Eg, I cannot load a specific collection and have the authorId and reviewerId auto-populate the fields in the app.

Sorry, i'm a little overwhelmed by regular work, but i'll give it a look asap.


SignInWithCustomToken method in Xamarin.Firebase.iOS.Auth give System.InvalidCastException.

Hi,
I trying to use SignInWithCustomToken method with the latest version of Xamarin.Firebase.iOS.Auth (v.5.0.2) with my existing code that worked well with the previous version.
Somehow, after I update the package, it gave me this below error:
System.InvalidCastException.
Specified cast is not valid
at (wrapper castclass) System.Object.__castclass_with_cache(object,intptr,intptr)
at ObjCRuntime.Runtime.ConstructNSObject[T] (System.IntPtr ptr, System.Type type, ObjCRuntime.Runtime+MissingCtorResolution missingCtorResolution) [0x00050] in <6a026a6503ca4935b5bb3ed241d053fe>:0
at ObjCRuntime.Runtime.GetNSObject[T] (System.IntPtr ptr) [0x000d1] in <6a026a6503ca4935b5bb3ed241d053fe>:0
at ObjCRuntime.Trampolines+SDAuthResultHandler.Invoke (System.IntPtr block, System.IntPtr user, System.IntPtr error) [0x00016] in <2a6853d2bb50451d907ffe64206d0142>:0
at (wrapper native-to-managed) ObjCRuntime.Trampolines+SDAuthResultHandler.Invoke(intptr,intptr,intptr)
I suspect the problem with the completion handler because when I set the completion handler to be null, I didn't get above error & everything is looking fine.

@munirahkamaluddin  could you please provide a small sample project that demonstrates the issue.

No response for over two weeks closing

Hey @newky2k
I am getting exactly same error with the latest version latest version of Xamarin.Firebase.iOS.Auth (v.5.0.4). I am using the following code in AppDelegate
public override bool FinishedLaunching(UIApplication app, NSDictionary options)
        {
            global::Xamarin.Forms.Forms.Init();
            LoadApplication(new App());

            Firebase.Core.App.Configure();

            var token = "{mytokenreturnedfromapiby-await FirebaseAuth.DefaultInstance.CreateCustomTokenAsync(uid)}";

            Auth.DefaultInstance.SignInWithCustomToken(token, async (User user, NSError error) =>
            {
            });

            return base.FinishedLaunching(app, options);
}

Using the following three packages

Xamarin.Firebase.iOS.Auth - v5.0.4
Xamarin.Firebase.iOS.CloudFirestore - v0.13.3
Xamarin.Firebase.iOS.Core - v5.1.3
Xamarin.Forms - v<IP_ADDRESS>7583

I can confirm this is still an issue with a custom token as per @faizworks  sample code.
Using SignInAsync(token) from <IP_ADDRESS> does work but it appears to have some issues with Firestore not then being authenticated.
Can this be reopened or does a new issue need raising?

Bump

Same issue here. Which issue should I be following instead?

I've raised #213 , Sample code given in this is valid but needs a way of generating a custom token


test(nodebuilder): fuzzer for fullClient.DataAvailability submission

This change presents a fuzzer for testing out fullClient data availability submission, in which the inputs to .Submit are mutated then the responses tested out to check for logical conformation. I ran this fuzzer for about 8 hours on my machine, but ideally we should get this repository up on oss-fuzz for continuous fuzzing.

Kindly cc-ing @Wondertan @liamsi

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

Project coverage is 46.23%. Comparing base (2469e7a) to head (dc872fd).
Report is 338 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3835      +/-   ##
==========================================
+ Coverage   44.83%   46.23%   +1.39%
==========================================
  Files         265      314      +49
  Lines       14620    18140    +3520
==========================================
+ Hits         6555     8387    +1832
- Misses       7313     8727    +1414
- Partials      752     1026     +274

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


oiiotool: make sure to propagate channel formats of input to output

Oiiotool took care to remember the data format of the first input file
it reads, and proagate that to the outputs (if not explicitly set by
-d).  And the -d could handle specifying per-channel data types. But we
didn't handle the case of remembering per-channel data types from the
input and propagating to the output.
Example:
oiiotool -create 64x64 3 -d R=half,G=float,B=half -o test.exr

properly makes a half/float/half mixed file. But then subsequently,
oiiotool test.exr -o out.exr

lost that info, saving it entirely as float/float/float.
With this patch, this works properly, and out.exr will correcly end up
as half/float/half.
I believe this fixes #1445

This works for the test cases that I have for #1445

Great, I'll merge it, then.


Disables accessory control when NO_RESPONSE was triggered

Here is the improvement of NO_RESPONSE implementation. If NO_RESPONSE was triggered and Home.app was not reopened, user still can control device as described here https://github.com/oliverrahner/node-red-contrib-homekit-bridged/issues/48. The improvement fixes this undesired behavior.

@radionoise thanks for PR!
Could you move code from HAPServiceNode.js to CharacteristicUtils.js?
Maybe do it like this. Merge those two _if_s in getSupported into one if (both push to supported array). Add your code in this one if case.
@crxporter and @NorthernMan54
You were active in Issue #48
Could you test this change if it works properly according to you?

Done

I’ll be ready to check later today - is there a branch to download with this change alongside the newest dev branch changes?
I struggle with figuring out which version to download...

I moved the code to getSupported function. However, getSupported function name doesn't suit well because we are creating subscription for set events here. I think that we should extract it to another function, or change the function name to something like getSupportedAndSubscribe or something. @Shaquu what do you think?

@radionoise well we can change to the name you have proposed :)

What about the first IF?
if (characteristic.props.perms.indexOf("pw") > -1) {
    supported.read.push(cKey);

    //What in this case?
}

if (
    characteristic.props.perms.indexOf("pr") +
    characteristic.props.perms.indexOf("ev") >
    -2
) {
    supported.write.push(cKey);

    characteristic.on("set", function(newVal, callback) {
	                    callback(node.accessory.reachable === false ? "no response" : null);
	                });
}

@Shaquu I didn't really get it about merging two IFs in getSupported function. What did you mean exactly? I moved my code into getSupported function as you proposed to get rid of the extra forEach loop.
About first if clause. I think we should subscribe only to writable characteristics.

@Shaquu I've updated my feature branch with your dev one. @crxporter can test it in my branch https://github.com/radionoise/node-red-contrib-homekit-bridged/tree/feature/no-response-improved

I was writing about merging ifs since you were adding subscriber on all elements in supported array previously. And when you moved it to getSupported then you omitted some characteristics. I will not argue. I am not a specialist :) And what you say has a sense - we should only subscribe to writable.
I assume you tested it yourself and it works fine for you?

Yes that works fine for me. We can wait for @crxporter feedback. I think he would like to test it :).

I didn’t get to it yesterday, I will test today.

This works much better than before. I'll put my "stamp of approval" on it.
I used the @radionoise no-response-improved branch.
Some notes will need to be made in the documentation so things are clear that if you are using the On characteristic to send "NO_REPSONSE" then you have to send a new "On" value to clear the no response status. Not a problem, just as always users need to know what they're doing.
I tested with a dimmer. I'm able to send On ture/false/NO_RESPONSE and it works great. I like that if I click it after sending no response (but Home app hadn't updated) then it bumps over to no response. This is how native homekit things usually work! BUT if I set On to NO_RESPONSE and then send brightness values - the switch will still update brightness levels.
Again this isn't a problem just an observation how it works.
@Shaquu from my point of view, 0.6.0 (with the no response added) is ready - no breaking changes from previous upgrades. Only potential is a little extra work switching parent/child nodes if 0.6.0 assumes everything is child.

@radionoise could you add some information about features from this PR in README?

I've improved it a little bit more. Now NO_RESPONSE can be triggered on optional characteristic too. Also you can reset it by sending valid value of any characteristic (not only the one you triggered NO_RESPONSE previously). @crxporter can you test it again please?
@Shaquu I will update README as soon as @crxporter will confirm that everything works as expected :)

One word. We have a file for tests. If you ever come to idea how to make it better to test our stuff then please tell me or update it yourself. Tests are running using mocha module (we start it from root of project with npm test)

Tested, looks good.
This is going to be much easier to use / explain to users now that the NO_RESPONSE state will go away with ANY other characteristic sent instead of having to send back to the same as before.

Updated README. @Shaquu It seems that PR is ready for merge

@radionoise thank you very much for contribution! I am really happy to see you guys working on that module :)
@crxporter thanks for tips and help with testing!


Add derivedFrom to register maker (rust version only)

#158

If it works correctly, it makes sense to do similar for make_peripheral, make_cluster and make_field.

Derive a field does not result in derive an enum, but literally derive a field:
TIMER0:
  CR:
    _modify:
      IDR:
        derivedFrom: RELOAD

Clears enums and add attribute to field.
            <field derivedFrom="RELOAD">
              <name>IDR</name>
              <description>Selects, if Reload Register number is incremented, decremented or not modified</description>
              <bitRange>[27:26]</bitRange>
              <access>read-write</access>
            </field>

As far as I know, no current patch does this. It also doesn't work correctly with svd2rust: it tries to duplicate enumerations in the same module.

It also doesn't work correctly with svd2rust: it tries to duplicate enumerations in the same module.

Yeah. This is the bug.
Could you open issue in svd2rust repo?

https://github.com/rust-embedded/svd2rust/issues/745


H08: Cloud Operation -- update for correct python (3.10) logging levels

You must have log messages with each of the following levels: CRITICAL, ERROR, INFO, DEBUG, TRACE.

Python logging framework has these levels:
CRITICAL ERROR WARNING INFO DEBUG

Recommend closing without merge. Python logging library is written to be extensible, additional logging levels can be added easily, see https://bugs.python.org/issue31732#msg307164.


namespace for migrations

It would be useful to add a namespace to migrations. For example:
I want to apply the vendor/yiisoft/yii2/rbac/migrations/m140506_102106_rbac_init.php migration.
For that now I need to run: yii migrate --migrationPath=@yii/rbac/migrations
But would it be more convenient, if I made a local 'reference':
My migration in console/migrations/m150819_075235_rbac_init.php would be:
class m150819_075235_rbac_init extends \yii\rbac\migrations\m140506_102106_rbac_init { }
In this case the simple yii migration would install that 'custom' migration, too.

now I am using this working method to workaround the problem:
<?php
$alias = Yii::getAlias('@yii/rbac/migrations/m140506_102106_rbac_init.php');
Yii::$classMap['m140506_102106_rbac_init'] = $alias;

class m150819_075235_rbac_init extends m140506_102106_rbac_init { }

PS. my issue title is probably wrong, as it gives reference to the resolve, not to the problem. Please feel free to change.

Why you don't use old good require_once ?

klimov-paul, you have right!

Resolved by commit 8aa0e85


add ollama support

adding ollama support (local model)
how to setup:

install and run ollama https://ollama.ai/
run ollama run mistral to fetch the model (2gb of data)
run opencommit with OCO_AI_PROVIDER='ollama'

it's not perfect but can be a start to incorporating other models that are available through ollama.

wow, that's is super great, will get time on weekend to collab on that! thank you for the contribution <3

@di-sukharev  - any progress on PR?
I am really eager to try local model feature.
I am not familiar with node, and when I am trying execute nmp build on the @jaroslaw-weber  branch - it throws bunch of errors.

well, month has passed and i still dont have enough time to manage this, it's a beautiful contribution!
@jaroslaw-weber are there any specific parts you are concerned about?

@di-sukharev thank you for checking the PR :)
my concerns:

is gpt still working? i think i did not break anything but would be great if u could check
are you also able to run ollama? would be nice to have someone confirm it works

i think if those two are working then we can maybe merge v1.0 version of the local model feature?
what we could improve:

currently i hardcoded single model and it cannot be changed. but in the feature we could add option in config for local models (i can do it in next PR)
documentation improvements (maybe after getting feedback from some users)

I can help with testing and feedback ( if you advice how I can build and install this package "locally")
As for the improvement there are few things.
First, OCO_LOCAL_MODEL_LLAMA needs to be set and updated right after initial install of oco ( in the same manner as with api key)
And of course - more ollama model , including codellama, etc.

@senovr im pretty sure its quite straightforward to run this.
did u install all packages? what error did u get?
try this:
install and run ollama https://ollama.ai/
then:
npm i
npm run build
npm run ollama:start

My issue is not with installing ollama itself, but with building npm oco package from source.

Will be merging on ThursdayOn 2 Jan 2024, at 09:24, Jaroslaw Weber @.***> wrote:
@di-sukharev do you think we can deploy soon?
i have integrated ollama in similar tool and confirmed it works
insulineru/ai-commit#18
➜  repo_name git:(prod) ✗ ai-commit
Ai provider:  ollama
prompting ollama... http://localhost:11434/api/generate mistral
response:   Updated production environment variables in docker-compose-all.yaml: ENV_SECRET_NAME from 'prod-env-2023-12-28' to 'prod-env-2024-01-02'.
prompting ai done!
Proposed Commit:
Updated production environment variables in docker-compose-all.yaml: ENV_SECRET_NAME from 'prod-env-2023-12-28' to 'prod-env-2024-01-02'.
? Do you want to continue? Yes
Committing Message... 🚀
Commit Successful! 🎉
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

hi @jaroslaw-weber, still havent got a free minute to merge this properly, will be back asap

No problem don't rush :) it's open source, not your job

@jaroslaw-weber  , @di-sukharev  - sorry for being silent for a while.
Answering your question, I was able to build the code and perform some simple tests.
Short answer- it works 👍

<3 looking into it

@di-sukharev, thank you very much for mergin this into main.
Now, I have a question as a user:

I made ollama installation, ollama pull mistral, ollama serve, ollama run mistral.
I updated opencommit npm i -g opencommit@latest
I made oco config set OCO_AI_PROVIDER='ollama'
I also set a pre-commit hook.

When I run git add  - git commit, I got a commit message , but without (fix) (chore) (feature).
Will dig more into it.
My question to @jaroslaw-weber  - if I change model to something else, will it works?

@senovr it may work but those models are usually less powerful than gpt 4. But definitely you can try

@senovr i've only tested and merged it, shoutout to @jaroslaw-weber who implemented the feature!

@jaroslaw-weber , sorry for bothering you again )
Currently, you have hard-coded model name in your commit
const model = 'mistral'; // todo: allow other models
How I can change it to become opencommit-configurable?
In Dmitry's code, I seeing this row:
const MODEL = config?.OCO_MODEL || 'gpt-3.5-turbo';
Probably in ollama.ts we can do it similarly...
My second question is probaby goes to both of  you  @di-sukharev and @jaroslaw-weber :
in jaroslaw's code, there is a "promt" part before request to local llm:
/hoftix: local models are not so clever so im changing the prompt a bit...
    prompt += 'Summarize above git diff in 10 words or less';

Probably this is the case not having (chore) (fix) (feat) in commit message...
I can not locate similar promt when calling chatGPT api, can you tell me if such prompt exists?
BTW, let me know if we need to move this conversation in new issue )

@senovr haha lol, please lets create a new issue, could you please create the PR, i will merge once done, please target it to the dev branch`

I have a PR from a little while ago that forks this PR to add support for changing the ollama model. I can update it and reopen it here if anyone is interested.
It's over here: https://github.com/jaroslaw-weber/opencommit/pull/1

Yeah forgot about mentioning that. I had some issue with generating commit message with the original prompt so I changed it. But feel free to modify that part :) Great that you guys follow up on this

As for hardcoding part of the model, I was going to work on this after my PR got merged but I got busy when it eventually got merged :) . Feel free to improve this part.


[RFE]  KMS migration helper

-->Is it linked to a user story? (use the "#" to tag the user story)
#50 - Result of Design meeting held on June 9th 2022 with @cvlc @mhmxs @vfiftyfive @rovandep
-->What do we want to build?
Trousseau to migrate from one KMS provider to another
-->Why do we want to build it?
Chaning KMS is not a common operation but if it happens it should done in a smooth and secure way.
As Trousseau is the broker between the k8s api manager and the KMS, it should help in replacing the secrets encrypted with the old KMS with the new KMS.
-->How do we want to design it?
#103 will provide the ability to run contiguous KMS provider plugin in sidecars
This will help to perform a replace transaction in a secure and transparent way.
A safe switch might need to be thought of to handle this migration with a human validation.

Migration scenario is carried within v2.
Documentation has to be writtent.


#7 Update docker instructions to cover UI feature flags

Explain how to set them
List what current feature toggles are available

Resolves #7

I will close this PR as #11 now supersedes it.


White area at bottom of dashboard

All of my dashboards have white area near the bottom. I am unsure how to get rid of it and would like the consistent grey background. I have selected tranparent background on all charts. It remains even when charts are removed. "Empty row" in the screenshot below has a transparent background.
Expected results
Expected grey background.
Actual results
Got white and grey background.
Screenshots
################# Screenshot 1###################

################# Screenshot 2 ###################

How to reproduce the bug

Go to any dashboard.
Scroll to bottom

Environment

superset version: 0.36.0
python version: python 3.6

Checklist
Make sure these boxes are checked before submitting your issue - thank you!

[x ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ x] I have reproduced the issue with at least the latest released version of superset.
[ x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

Seems to have resolved. Not sure why.


[FEATURE] #203 Initial version of the Extension point for resource icon

[DESC.] Initial version of the Extension point for resource icon. Project type is  not considered yet. We will consider the project type later.

I can't understand why two different commits can have exactly same commit messages.


Emit assembly attributes

We have a CommonAssemblyInfo.cs file that's included in all projects in the solution.
I wanted to add assembly attributes based that use GitInfo properties, as described in the README.
It seems this can't work in the case of InternalsVisibleTo because a shared file cannot import a unique namespace per consuming project.
Would it make sense to have a property that caused GitInfo to emit assembly attributes into the .g.cs file? I could them remove them from CommonAssemblyInfo.cs.

SDK-style projects already provide that. Or you can use MSBuilder.AssemblyMetadata. here's an example: https://github.com/moq/moq/blob/master/src/build/Version.targets

It's a UI app so we're not using SDK projects yet.
Thanks for the example. I can see that it's possible, but it's more work than I'm willing to chew on right now. It feels like this should be something done once in this repo, and made easily available to all users via a simple property.

Understood, but this project does not intend to be overly prescriptive as to how you use those values. You can fairly easily do what you want with the things I mentioned. It's a package reference plus a couple MSBuild items on you targets.

Thanks Daniel, I'll take another look.


issue with new static strategy

I'm using this laTrappe for testing.
I've been drawing dependency off on a fork for some time, but now getting back into the master branch, (via another fork!), and noticing that all the commits after
c0b41fea325b2cbda20e9d187bff864224894f50
are non-performing in one way or another.
This is the app I'm using for test:
https://github.com/kulicuu/laTrappe
The latest commits seem to run fine but notice the entry.coffee file doesn't load-- basically the client doesn't load successfully.
When I git checkout some commits like d2037735dbfc6b500af642993d5629e79fbd358c we actually get errors in the server console:
TypeError: Cannot call method 'use' of undefined
  at Object.load (/home/wylie/southernOcean/kulicuu/socketstreamDevs/laTrappe/node_modules/socketstream/lib/http/index.js:155:11)
  at start (/home/wylie/southernOcean/kulicuu/socketstreamDevs/laTrappe/node_modules/socketstream/lib/socketstream.js:102:10)
  at Object.exports.start (/home/wylie/southernOcean/kulicuu/socketstreamDevs/laTrappe/node_modules/socketstream/lib/socketstream.js:138:46)
  at Object.<anonymous> (/home/wylie/southernOcean/kulicuu/socketstreamDevs/laTrappe/laTrappe_local.coffee:35:35)
  at Object.<anonymous> (/home/wylie/southernOcean/kulicuu/socketstreamDevs/laTrappe/laTrappe_local.coffee:2:1)
  at Module._compile (module.js:456:26)

The later and latest commits seem to run well on the server side but the client doesn't load the entry file.
This commit f93652e4b16515d973a95ef59ab68ca6a4aef64c runs good.

Hmm, looks like I broke something with the static strategy.

Ah you got it cool !  I've been meaning to get to this, but also wondering  if anyone else could reproduce the error.  cool !

Sorry, didn't test it yet, was just apologizing as it seems to be my commits.

No problem and no rush at all ;}

I'd like to fix it. I'm not sure how to run your project though. tried calling
'coffee laTrappe_local' it cannot locate socket stream
Also you have a trailing comma in the package.son

I'm not sure what to expect with La Trappe. I see issues with Angular template script tags having IDs with the file path, which surely they shouldn't have.

Could I ask you to make a detailed bug report. Ideally a test setup that fails. We really want to move towards TDD.

Cool cool I'll do that tomorrow.

Right so here it is tomorrow.
I've fixed laTrappe and so you should be able to run it locally.
I've created a new clone of it and added the line "socketstream": "git://github.com/socketstream/socketstream.git#master", to the package.json flie.
The detailed bug report without inserting logging debris is Nothing.  There is no error output in the server console, and there is no error output in the browser console.
Looking at the differences between the html page source as delivered we have:
Bad
<!DOCTYPE html><link href="/_serveDev/css/laTrappe_local_alpha/main.styl?ts=1422794514966" media="screen" rel="stylesheet" type="text/css"><title>laTrappe</title><meta charset="utf-8"><panel></panel>

Good

<!DOCTYPE html><link href="/_serveDev/css/laTrappe_local_alpha/main.styl?ts=1422794740752" media="screen" rel="stylesheet" type="text/css"><title>laTrappe</title><meta charset="utf-8"><panel></panel>

Okay,
here is the good delivery of the code module: (accessed by ctrl-u for the source in Firefox and then clicking the link on first script.
https://gist.github.com/kulicuu/27206afb11851733d4e8
The bad one just gives the error CANNOT GET.
So that's basically the bug report as far as that goes.
For something more substantial, I could hunt around with my console logging gear on the server side.  Will get back to you.

Update
I've made another clone to analyze the new static work, not only to debug regarding this issue but also to see your development line here and to think about how to integrate with new work I'm doing with respect to the React integrations.

Hey, I want to find the discussion leading up to the development of the new static strategy; where would that be ?
Or /and, could you describe -- briefly or at length -- what you had in mind to accomplish with the new static strategy ?

Wow, cool code.  Lots of work here, not too sure raison d'etre yet, but lots here and it's very interesting.  Noticed will require some modifications (not too difficult) to bring it merge-able with the new Connect v3.3.4, and some of the files modded are the same.
Have you been able to reproduce the error I'm encountering ?  Again, it's serving the view but not the Javascript, so the entry file is never initialised.
laTrappe should be working now let me know if still any issues there.

Okay the problem was with the way I was integrating the Express and SocketStream stacks, as seen here.
I'm okay with dropping this usage and finding a better way.... at any rate it's on my thingstodo list to implement an upgrade to Express v4 and that will require some reworking anyway.  So I'm going to close this.
Thanks!


Location Header missing in POST HTTP response

I have a Logic App which calls the HTTP Post call for a refresh(https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-async-refresh#post-refreshes). I get a HTTP OK response and the refresh is initiated. However, I do not find the Location Header field in the response.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0193ed76-3eec-18ac-512f-45f8118dde34
Version Independent ID: 8e693833-3e45-2bb8-ddc2-d0c54936c3c1
Content: A New Feedback System Is Coming to docs.microsoft.com
Content Source: teamblog/a-new-feedback-system-is-coming-to-docs.md
Service: unspecified
Product: team-blog
GitHub Login: @EisenbergEffect
Microsoft Alias: EisenbergEffect

@adeenadayalan Thanks for leaving us site feedback.
Make sure to leave page feedback on the specific docs page of your inquiry or issue to ensure the content/product owner can respond quickly.
I'm closing this issue for now, but feel free to re-open it with site feedback if/as needed.


downgrading of tabulate

should fix issue https://gitlab.com/mmb-umcu/bactofidia-stable/-/issues/2

Build tested locally


Add script to easilly generate certificates

Is your feature request related to a problem? Please describe.
I'm having a lot trouble generating new certificates for open search. I have encountered this with Open Distro as well. I tried getting the DN's from the original certificates, but it still gives errors:
#!/bin/sh
#DN's are from the default configs
openssl genrsa -out root-ca-key.pem 2048
openssl req -new -x509 -sha256 -key root-ca-key.pem -subj "/DC=com/DC=example/O=Example Com Inc./OU=Example Com Inc. Root CA/CN=Example Com Inc. Root CA" -out root-ca.pem
openssl genrsa -out admin-key-temp.pem 2048
openssl pkcs8 -inform PEM -outform PEM -in admin-key-temp.pem -topk8 -nocrypt -v1 PBE-SHA1-3DES -out admin-key.pem
openssl req -new -key admin-key.pem -subj "/C=de/L=test/O=client/OU=client/CN=kirk" -out admin.csr
openssl x509 -req -in admin.csr -CA root-ca.pem -CAkey root-ca-key.pem -CAcreateserial -sha256 -out admin.pem
openssl genrsa -out esnode-key-temp.pem 2048
openssl pkcs8 -inform PEM -outform PEM -in esnode-key-temp.pem -topk8 -nocrypt -v1 PBE-SHA1-3DES -out esnode-key.pem
openssl req -new -key esnode-key.pem -subj "/DC=de/L=test/O=node/OU=node/CN=node-0.example.com" -out esnode.csr
openssl x509 -req -in esnode.csr -CA root-ca.pem -CAkey root-ca-key.pem -CAcreateserial -sha256 -out esnode.pem
rm admin-key-temp.pem
rm admin.csr
rm esnode-key-temp.pem
rm esnode.csr
rm root-ca.srl

Nodes won't accept the certs. Can you post a convenient script like this where you just have to enter some var's and it'll generate the certs?
The inital setup command has the certs embedded as well, but that leaves the cluster wide open for penetration if you don't update the admin cert.
Describe the solution you'd like
Simple script to generate a set of certs which nodes will accept (with the k8s cluster I don't mind the certs being the same for the nodes)
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@vrozov Could you look into this request?

This has improved with the improved documentation with regard to the certificates. But it would be beneficial to not have the same admin cert every time a new cluster is deployed. This poses a security risk when a user does not know this.

We are doing some "spring cleaning in the fall", and to make sure we focus our energies on the right issues and we get a better picture of the state of the repo, we are closing all issues that we are carrying over from the ODFE era (ODFE is no longer supported/maintained, see post here).
If you believe this issue should still be considered for current versions of OpenSearch, apologies! Please let us know by re-opening it.
Thanks!