Rename repo and app

StockStratMemes was a temporary name. Rename to something better.

Delivered to master.
I renamed it to CryptoRetriever and gave it an MIT license file as well as updated the readme.
Commits
commit 4b71ba0dd8d4afc246a8f8ac326fa9ffd9ab922c
Author: Alex Hunt<EMAIL_ADDRESS>Date:   Wed Mar 16 19:02:37 2022 -0400
Issue16: Fixed the readme spacing.

commit 8fcd8e8391fb057b3d70c50cfa1136bb995b106c
Author: Alex Hunt<EMAIL_ADDRESS>Date:   Wed Mar 16 18:55:50 2022 -0400
Issue16: Renamed the app.

Testing

Built/Ran the app and made sure everything has the new name
Ran through the different menus to make sure they still work
Made a clean clone of the repository and verified it builds and runs out of the box


Add app version to UI

needed for understanding what version is deployed to prod/staging.

added to settings menu dropdown.


Preflight var check

setup preflight checks if the car directory is readable by the currrent user, not the apache owner.

fixed in [f7de9ae]


Rat in a Maze Problem

Type
Algorithm
Directory
Algorithms =>Backtracking => Rat in a Maze.cpp
Description
In this problem, there is a given maze of size N x N. The source and the destination location is top-left cell and bottom right cell respectively. Some cells are valid to move and some cells are blocked. If one rat starts moving from start vertex to destination vertex, we have to find that is there any way to complete the path, if it is possible then mark the correct path for the rat.
The maze is given using a binary matrix, where it is marked with 1, it is a valid path, otherwise 0 for a blocked cell.
NOTE: The rat can only move in two directions, either to the right or to the down.
Programming Language

[X] c++
[ ] c
[ ] python
[ ] java
[ ] kotlin
[ ] javascript
[ ] typescript
[ ] c#
[ ] swift
[ ] ruby
[ ] scala
[ ] go
[ ] php
[ ] haskell
[ ] bash

Can I work on this issue?

Can I work on this issue?

Can I work on this issue?

Unfortunately,no


[BUG] Change deposit verify view, basis points label to percentace

Describe the bug
When verifying a message deposit for removing from the RUNEPool, it shows Basis Points but should be labled Percentage
Expected behavior
Show label as Percentage
Screenshots

-v50

THORChain is always working with BasisPoint , so instead we should change the label


Installation of 3.5.3 .deb fails if 3.5.2 already installed

When running sudo dpkg -i dbeaver-ce_3.5.3_amd64.deb on a Linux Mint 17 64bit, with 3.5.2 already installed, will fail with the following error message:
Preparing to unpack dbeaver-ce_3.5.3_amd64.deb ...
rm: cannot remove ‘/usr/bin/dbeaver’: No such file or directory
dpkg: error processing archive dbeaver-ce_3.5.3_amd64.deb (--install):
 subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
 dbeaver-ce_3.5.3_amd64.deb

However, manually un-installing the application using sudo dpkg --remove dbeaver-ce allows the installation of 3.5.3 with the aforementioned command.

Yes, that's a bug in deb installer. Just fixed and published new debs.
Thanks for report!

That was quick! Thanks!


Too much time cost in airline#highlighter#highlight()

environment
Vim
➜  ~/.vim/bundle/vim-airline git:(master) vim --version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jul 11 2018 06:10:39)
Included patches: 1-1605
Compiled by<EMAIL_ADDRESS>Huge version without GUI.  Features included (+) or not (-):
+acl               +farsi             +mouse_sgr         -tag_any_white
+arabic            +file_in_path      -mouse_sysmouse    -tcl
+autocmd           +find_in_path      +mouse_urxvt       +termguicolors
-autoservername    +float             +mouse_xterm       +terminal
-balloon_eval      +folding           +multi_byte        +terminfo
+balloon_eval_term -footer            +multi_lang        +termresponse
-browse            +fork()            -mzscheme          +textobjects
++builtin_terms    +gettext           -netbeans_intg     +timers
+byte_offset       -hangul_input      +num64             +title
+channel           +iconv             +packages          -toolbar
+cindent           +insert_expand     +path_extra        +user_commands
-clientserver      +job               -perl              +vertsplit
-clipboard         +jumplist          +persistent_undo   +virtualedit
+cmdline_compl     +keymap            +postscript        +visual
+cmdline_hist      +lambda            +printer           +visualextra
+cmdline_info      +langmap           +profile           +viminfo
+comments          +libcall           +python            +vreplace
+conceal           +linebreak         -python3           +wildignore
+cryptv            +lispindent        +quickfix          +wildmenu
+cscope            +listcmds          +reltime           +windows
+cursorbind        +localmap          +rightleft         +writebackup
+cursorshape       +lua               -ruby              -X11
+dialog_con        +menu              +scrollbind        -xfontset
+diff              +mksession         +signs             -xim
+digraphs          +modify_fname      +smartindent       -xpm
-dnd               +mouse             +startuptime       -xsmp
-ebcdic            -mouseshape        +statusline        -xterm_clipboard
+emacs_tags        +mouse_dec         -sun_workshop      -xterm_save
+eval              -mouse_gpm         +syntax
+ex_extra          -mouse_jsbterm     +tag_binary
+extra_search      +mouse_netterm     +tag_old_static
   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: "/home/yunion/.usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -isystem /home/yunion/.usr/include  -isystem /home/yunion/.usr/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -L/home/yunion/.usr/lib -Wl,-rpath,/home/yunion/.usr/lib -L/usr/local/lib -Wl,--as-needed -o vim        -lm -lnsl   -lncurses -liconv -ldl  -L/home/yunion/.usr/lib
 -lluajit-5.1  -L/home/yunion/.usr/lib/python2.7/config -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic

Vim airline version
commit b790fd212088c0c882f16416f07cbd6035882028 (HEAD -> master, origin/master, origin/HEAD)
Merge: c3a814d a141918
Author: Christian Brabandt<EMAIL_ADDRESS>Date:   Mon Jun 18 08:39:53 2018 +0200

    Merge pull request #1750 from Mangero/arduino-whitespace

    Add Arduino to list of C-like languages

CentOS 7 Linux titan 3.10.0-514.26.2.el7.x86_64
Airline configuration
let g:airline_highlighting_cache = 1
" disable tagbar integration (can be slow)
let g:airline#extensions#tagbar#enabled = 0
let g:airline#extensions#wordcount#enabled = 0
let g:airline#extensions#whitespace#enabled = 0
" disable fugitive integration (takes up space)
let g:airline#extensions#branch#enabled = 0
" show filename (no (compressed) path) in the tab
let g:airline#extensions#tabline#enabled = 1
let g:airline#extensions#tabline#fnamemod = ':t'
" save tabline space
let g:airline#extensions#tabline#show_splits = 0
let g:airline#extensions#tabline#show_tab_type = 0
" no need to show "filetype<fileencoding[fileformat]"
let g:airline_section_x = ''
let g:airline_section_y = ''

actual behavior
I use vim with plugin vim-go.  The editor seems to slow down gradually over time.  I need to quit and reopen to start it over again.
:profile result shows that a lot of time was spent iterating g:airline#themes#{g:airline_theme}#palette[mode] inside function airline#highlighter#highlight()
Full profile.log attached.  It was generated just by moving the cursor between different windows a few times.
FUNCTION  airline#highlighter#highlight()
Called 12 times
Total time:   5.199249
 Self time:   0.794295

count  total (s)   self (s)
   12              0.000049   let bufnr = a:0 ? a:1 : ''
   12              0.000070   let p = g:airline#themes#{g:airline_theme}#palette

                              " draw the base mode, followed by any overrides
   12              0.000190   let mapped = map(a:modes, 'v:val == a:modes[0] ? v:val : a:modes[0]."_".v:val')
   12              0.000096   let suffix = a:modes[0] == 'inactive' ? '_inactive' : ''
   30              0.000096   for mode in mapped
   18              0.000088     if mode == 'inactive' && winnr('$') == 1
                                  " there exist no inactive windows, don't need to create all those
                                  " highlighting groups
                                  continue
                                endif
   18              0.000162     if exists('g:airline#themes#{g:airline_theme}#palette[mode]')
   12              0.000107       let dict = g:airline#themes#{g:airline_theme}#palette[mode]
 3324              0.012849       for kvp in items(dict)
 3312              0.015744         let mode_colors = kvp[1]
 3312              0.013170         let name = kvp[0]
 3312              0.015946         if name is# 'airline_c' && !empty(bufnr) && suffix is# '_inactive'
    6              0.000025           let name = 'airline_c'.bufnr
    6              0.000007         endif
 3312   1.091446   0.044705         call airline#highlighter#exec(name.suffix, mode_colors)

 9936              0.031345         for accent in keys(s:accents)
 6624              0.030404           if !has_key(p.accents, accent)
                                        continue
                                      endif
 6624              0.037262           let colors = copy(mode_colors)
 6624              0.035839           if p.accents[accent][0] != ''
 3312              0.017361             let colors[0] = p.accents[accent][0]
 3312              0.004331           endif
 6624              0.025435           if p.accents[accent][2] != ''
 3312              0.015959             let colors[2] = p.accents[accent][2]
 3312              0.004185           endif
 6624              0.021166           if len(colors) >= 5
 6624              0.040522             let colors[4] = get(p.accents[accent], 4, '')
 6624              0.008942           else
                                        call add(colors, get(p.accents[accent], 4, ''))
                                      endif
 6624   2.076114   0.098259           call airline#highlighter#exec(name.suffix.'_'.accent, colors)
 6624              0.009903         endfor
 3312              0.004052       endfor

                                  " TODO: optimize this
 3216              0.010949       for sep in items(s:separators)
 3204   1.443267   0.062909         call <sid>exec_separator(dict, sep[1][0], sep[1][1], sep[1][2], suffix)
 3204              0.004769       endfor
   12              0.000038     endif
   18              0.000020   endfor

see #1026, the FAQ and the related information. If you have further suggestions how to improve the performance, I am all ears ;)

BTW: it might also be related to your airline theme and syntax highlighting. Check the output of :syntime

I have read #1026 before, I tried.  The result is adding g:airline_highlighting_cache=1 to my config.  It does not resolve my issue.
I also tried syntime on , syntime report , but the output had no interesting output as far as I could tell.  I will try to log the output next time in case it may.
From the profile log output, I think the issue reported here is different from that of #1026, the editor works fine at startup, but the performance degrades over time, possibly things continue to add up in the palette dict.  I was expecting advice on this.

The airline#highlighter#highlight() func called only 12 times, yet it loops 3324 times inside.  That just does not smell right.

The airline#highlighter#highlight() func called only 12 times, yet it loops 3324 times inside. That just does not smell right.

Indeed. I'l have another look

I was hit by this as well and had to switch to some other statusline until this is fixed.

Pleased provided more information as asked several times

Am 10.10.2018 um 14:50 schrieb Johannes Wienke<EMAIL_ADDRESS>I was hit by this as well and had to switch to some other statusline until this is fixed.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

Here is my profile.log for that session:
https://gist.github.com/languitar/eecdacb3a81dd23fea6e37bc0e3b0b10

Have you looked into the FAQ?

Am 10.10.2018 um 15:40 schrieb Johannes Wienke<EMAIL_ADDRESS>Here is my profile.log for that session:
https://gist.github.com/languitar/eecdacb3a81dd23fea6e37bc0e3b0b10
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

Yes, I tried setting the caching, but then I frequently get broken renderings in airline.

It would be good information to mention at the beginning. When does the caching not work?

Am 10.10.2018 um 16:07 schrieb Johannes Wienke<EMAIL_ADDRESS>Yes, I tried setting the caching, but then I frequently get broken renderings in airline.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

In in active windows, some UTF-8 characters are rendered wrong. I'll try to provide a screenshot when I'm back at work.

That sounds like a font issue rather than a caching issue. That only happens when caching is enabled?

Am 11.10.2018 um 11:17 schrieb Johannes Wienke<EMAIL_ADDRESS>In in active windows, some UTF-8 characters are rendered wrong. I'll try to provide a screenshot when I'm back at work.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

left is without caching, right is with caching. See the artifcat at the bottom in the right version.

I wonder why that happens. Might be a terminal problem. Have you tried a terminal or the gui?

Am 11.10.2018 um 11:56 schrieb Johannes Wienke<EMAIL_ADDRESS>left is without caching, right is with caching. See the artifcat at the bottom in the right version.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

it's neovim in terminal. There's no gui verison I could test.

What terminal? Please test with vim as well

Am 11.10.2018 um 15:19 schrieb Johannes Wienke<EMAIL_ADDRESS>it's neovim in terminal. There's no gui verison I could test.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

termite v13. Same thing happens in stock vim.

Btw, my configuration is online here: https://github.com/languitar/config-vim

Several things to test:

Try with different terminals and also with a gui version
disable the unicode characters first, it actually looks a bit like a font problem (you can see those artifacts on the left side of your screenshot too)
show the output of :echo eval(&stl[2:])
try to provide a minimal example, that shows those problems. Then I have a chance to fix the caching problem.

thanks

Ok, things are not entirely gone with the "base16-bright" theme, but at least things are better.

Ah, your staircase separator confused me.

Which terminal does support termguicolors that I could test on this setup?

perhaps gnome-terminal or xfce-terminal? (just plain, without tmux or similar)

Without caching...

could that be a dup of #1807?

Ah, your staircase separator confused me.

Which terminal does support termguicolors that I could test on this setup?

perhaps gnome-terminal or xfce-terminal? (just plain, without tmux or similar)

Also happens in gnome-terminal.

Without caching...

could that be a dup of #1807?

As far as I can tell, not. The statusline deactivates properly, but the colors of some symbols are off in the deactivated statusline. Moreover, this simply doesn't happen without caching.

As far as I can tell, not. The statusline deactivates properly, but the colors of some symbols are off in the deactivated statusline. Moreover, this simply doesn't happen without caching.

So how do I reproduce this?

looks like the reverse attribute caused the problem. Can you please verify, taht 726b730 fixes the problem?

Yes, that looks better. Thanks a lot!

Good to know the progress.  Just to clarify, is this fix for "broken renderings in airline when cache enabled" or "getting slower over time"?  or both?

The rendering is fixed. I can't tell anything about the long-term performance with caching enabled. I have observed the slowdown only without caching, similar to the original report in this issue.

I am the original reporter ;)  The slowdown happened regardless of whether cache was enabled (I only tried to enable caching when seeing the slowdown in the first place, but later found it had no effect against the slowdown).  The theme is always "dark" in the terminal (I did not explicitly have it set in the .vimrc).

By the way, by caching I mean "g:airline_highlighting_cache = 1" in the vim config.

So if the caching does not solve the problem for you, what is causing your slowdown then?

at @yousong please check current head. I fixed another problem

@chrisbra roger that ;)

I just closed all other tabs and keep only one open (a single .go file with tagbar and nerdtree), then checked the content of palette dict and dumped it.  The lag is still acceptable and not that obvious but I think the size of the dict is big enough to be suspicious.
airline.palette.20181108.txt

For archive purposes, I dumped the content by "=string(g:airline#themes#{g:airline_theme}#palette) then p the content to a file.
It can be converted to json and viewed with jq
tr "'" '"' <b  | jq .normal -  | vim -

i don't need json. simply adding let a=<content> worked for me.
After inspection, I see that you have been editing many buffers. That is expected however.
An idea I have, is to check whether the buffer number still exists in the current window and only then re-create the highlighting. Other than that, I don't see anything wrong with it. And yes, in this case it is expected that the palette grows.

I implemented that in revision 09b5eb9
please check.

I used to have bufwipe=hidden enabled then disabled in https://github.com/yousong/dconf/commit/67b851f6694b77de391b5f14adf083379db134f0 and https://github.com/yousong/dconf/commit/7c2bc82cf242424d24a88f5db9e5d6386a4831ed respectively . It was disabled later because tagstack does not work with bufwipe=hidden enabled.
I am actually only aware of the existence of "buffers" in vim after using it for quite a while and I remembered people not recommending tabs for multiple file editing.
I will open another session and try the latest revision.  Thank you.

airline does not care about the bufwipe option (and it actually shouldn't matter, whether or not you are using Tabs for multiple file editing).

i consider this fixed.

@chrisbra , thank you for taking care of this.  I haven't yet reproduced the lag, so far so good.  But the palette dict is still big with only 1 tab open (no reclamation or cleanup on tab close).  Is this now expected behavior with the "recreate highlight group only for visible tabs" change?

Sometimes I still have issues with vim-airline highlight performance.
Plug 'machakann/vim-highlightedyank'

Plug 'antoinemadec/coc-fzf', {'branch': 'release'}

Plug 'vim-airline/vim-airline'

Plug 'lambdalisue/nerdfont.vim'

Plug 'lambdalisue/fern.vim'
Plug 'lambdalisue/fern-renderer-nerdfont.vim'
Plug 'lambdalisue/fern-hijack.vim'

Plug 'antoinemadec/FixCursorHold.nvim'

Plug 'sheerun/vim-polyglot'

Plug 'alunny/pegjs-vim'
call plug#end()

Well, re-creating the highlighting groups is expensive. What kind of a system is this? I think this will get better, once the vim9 script branch is merged. But I need to re-do this

2021, same issue persists. I cant use this plugin at all on my macbook air, its just not powerful enough...  BTW, it's an open source project, it lives from contributing. Complaining won't help to make it better. FWIW: since the various speed improvements I personally haven't seen this issue any more. Another possibility would be to test the vim9 branch, that is currently pending. I need some time to properly test and integrate it.

Am 06.05.2021 um 21:25 schrieb Skylar @.***>:

2021, same issue persists. I cant use this plugin at all on my macbook air, its just not powerful enough...
Reply to this email directly, view it on GitHub, or unsubscribe.

BTW: This:
191              1.991047  provider#python3#Call()
190              1.978191  UltiSnips#TrackChange()

This definitely does not come from airline

I think I may have found either the reason for this issue, or at least another source of slowdowns. I discovered this because I have been setting up Neovim's builtin LSP client which has this functionality for opening a "hover" window with the information for the symbol under the cursor (screenshot). I have been observing that my nvim setup would slow down over time, and today I got fed up with this and began investigating. Don't know why, but I thought that the floating windows were related to the issue, so I came up with a simple stress test which was a Python script which would repeatedly simulate presses of shift+K to trigger this hover window. The test was a success because it would consistently slow Vim down to a crawl after a few minutes of automatically pressing K. Anyway, after performing such a test, I ran the profiler and got a similar profile to the users above, i.e. most time is spent in the airline#highlighter module, s:get_syn in particular. After that I came up with this minimal vimrc which can be used for reproducing the bug:
set rtp+=~/.config/nvim/plugged/vim-airline

let s:iteration = 0
let s:existing_winnr = v:null

function! StressTestTimerCallback(timer) abort
  if s:existing_winnr && nvim_win_is_valid(s:existing_winnr)
    call nvim_win_close(s:existing_winnr, v:true)
  endif

  " Triggered on the last iteration.
  if empty(timer_info(a:timer))
    return
  endif

  let hlgroups_rough_count = len(split(execute('highlight'), "\n"))
  let text = printf('iteration:%d hlgroups:%d', s:iteration, hlgroups_rough_count)

  let bufnr = nvim_create_buf(v:false, v:true)
  call nvim_buf_set_option(bufnr, 'bufhidden', 'wipe')
  call nvim_buf_set_lines(bufnr, 0, -1, v:true, [text])
  call nvim_buf_set_option(bufnr, 'modifiable', v:false)
  let winnr = nvim_open_win(bufnr, v:false, {
  \ 'width': strdisplaywidth(text), 'height': 1,
  \ 'relative': 'cursor', 'row': 1, 'col': 0,
  \ 'style': 'minimal' })

  let s:existing_winnr = winnr
  let s:iteration += 1
endfunction

function! StressTestStart(total_iterations) abort
  let s:iteration = 0
  let s:existing_winnr = v:null
  call timer_start(100, 'StressTestTimerCallback', {'repeat': a:total_iterations})
endfunction

Needless to say, it requires Neovim, though it only seems to be effective on v0.5.0. To reproduce:

save the code to a file, like minimal_init.vim
run nvim -u minimal_init.vim
:call StressTest(200), 200 is the number of opened-and-immediately-closed floating windows, adjust because the lag may take some time to become apparent
The lag can be observed by switching to insert mode and back, for example.

Anyway... the issue in my setup seems to be that Airline creates a ton of highlight groups in airline#highlighter#exec for new windows and new buffers, but doesn't delete them. I doubt that this is specific to floating windows, it's just that the example above was the shortest thing I could come up with, though even opening new buffers causes a leak of highlight groups as well. Splitting windows and closing the splits might also do the trick. So yeah, I believe that the other users are essentially having "leaks" of highlight groups as well, and that s:get_syn is having trouble because of this. (Also I have to mention that prepending noautocmd to the line with nvim_open_win remedies the problem, but this should be applied only to plugins which are opening floating windows themselves and does not solve the underlying issue in Airline.)
Oh, and also, len(split(execute('highlight'), "\n")) is not an accurate measure of the total number of highlight groups because of the wrapping in :highlight, but it is enough to prove the point.
P. S. Here's my profile after running the prototype stress test for 13 minutes: profile.log.

so you are basically creating 200 random buffers? We could possibly clear the highlighting, if the old buffer no longer exists. But the highlighting group would still be there. That hints, that Vims datastructure is not optimized for too many highlighting groups (ping @brammool)
Also, can you please show the output of echo split(execute('highlight'), "\n") just resize the window large enough, such that no wrapping occurs. Just for 50 buffers should be enough.

it would also be interesting to see, how it runs on Vim9 Script

Anyway... the issue in my setup seems to be that Airline creates a ton of highlight groups in airline#highlighter#exec for new windows and new buffers, but doesn't delete them.

Oh and that is not possible.

FUNCTION  <SNR>126_get_syn()
    Defined: ~/.config/nvim/plugged/vim-airline/autoload/airline/highlighter.vim:44
Called 356588 times
Total time:  21.819761
 Self time:  21.819761

count  total (s)   self (s)
356588              0.365869     let color = ''
356588              9.068191     if hlexists(a:group)
241780              5.570819       let color = synIDattr(synIDtrans(hlID(a:group)), a:what, a:mode)
356588              0.171991     endif
356588              0.536942     if empty(color) || color == -1
                                  " should always exist
114808              3.668305       let color = synIDattr(synIDtrans(hlID('Normal')), a:what, a:mode)
                                  " however, just in case
114808              0.188707       if empty(color) || color == -1
                                    let color = 'NONE'
114808              0.042864       endif
356588              0.119569     endif
356588              0.284614     return color

So what we can see here is, hlexists() and synIDattr() are the bottleneck. That is calling inside Vims C core, I cannot improve it here with Vimscript.

Also, have you tried following the advice in the wiki? Basically about the caching and using a theme that does not switch colors?

so you are basically creating 200 random buffers?

Yes, but only because that's a reliable way of forcing the performance issue, intended to help debugging. While working as usual hlgroups are still being leaked, but the slowdown becomes apparent much earlier than Vim slows down to a crawl as with my stress test.

Also, have you tried following the advice in the wiki? Basically about the caching and using a theme that does not switch colors?

No, but I believe that I found a bug in the default implementation.

EDIT: and 200 random windows.

well, the highlighting groups are bound to buffers and you call something called nvim_create_buf(v:false, v:true) which makes it sound like it creates buffers.

No, but I believe that I found a bug in the default implementation.

of Vim? possible As I said the current API does not allow to delete highlighting groups. That is nothing vim-airline can fix. We might have to dig into the vim source to fix that.

nevertheless, I'll put it on my plate to dig this up in Vims source

of Vim? possible As I said the current API does not allow to delete highlighting groups. That is nothing vim-airline can fix. We might have to dig into the vim source to fix that.

(of Airline) Pardon my ignorance, didn't remember. As a matter of fact I've worked around the slowdowns in my setup using noautocmd when opening floating windows, but I'll test hlgroup caching.

well, the highlighting groups are bound to buffers and you call something called nvim_create_buf(v:false, v:true) which makes it sound like it creates buffers.

By the way: just creating random buffers and opening them in a single window doesn't trigger the leak.

Strange. Groups are still being leaked even with caching enabled.

By the way, you don't even need some overcomplicated floating window setup, apparently. Either I'm misunderstanding something, or Airline leaks groups even when just opening new buffers (with caching enabled, obviously). Try opening, like, five of them, then splitting the window and cycling through the buffers in both windows, and filtering groups with :filter /airline_c\d/ highlight or something.

Yes, I believe it is expected. It doesn't leak anything. It's just, once a buffer is displayed in a window it creates inactive highlighting groups, so that the statusline can display correctly even if the same buffer is in one window active while also displayed in another inactive window. And then it needs to create additional groups for those powerline glyphs, so that you have the nice from one foreground color to the next foreground color transition. And possibly again for the different accents. There is nothing leaking here.

But then... what is caching supposed to do? Oh, and I observe the same behavior with or without caching.

Yes, as I said airline creates new highlighting groups, once a buffer is displayed in a non-active window, because one buffer could be modified the groups need to differ. Hm, perhaps we can link them to a default group since they are usually all the same.  Also I am wondering why we have several _inactive_inactive groups. that does not look right.
caching prevents highlighting groups to be re-defined, even if they already exist.

Regardless, the fact still stands that hlexists and synIDattr don't like having to loop through a lot of defined hlgroups. Do you think this is a bug on the Vim side (i.e. the functions being slow) or on the Airline side (creating identical hlgroups)?

probably a mixture of both. A solution could be to use pre-defined groups, instead of creating a bunch of groups for each buffer for all different buffer states (and possibly we can save some of those, if we are not using powerline glyphs).
But still the core vim functions are slow.

Regardless, the fact still stands that hlexists and synIDattr
don't like having to loop through a lot of defined hlgroups. Do you
think this is a bug on the Vim side (i.e. the functions being slow) or
on the Airline side (creating identical hlgroups)?

The code assumes there aren't that many entries, thus it just does a
linear lookup in the table.
The lookup can be made much faster when using a dictionary (hash table).
However, then adding and removing groups becomes more expensive.
Probably the net effect is still positive, especially when there are a
lot of names.  And when there are not many groups the overhead is most
likely unnoticeable.
--
[clop clop]
GUARD #1:  Halt!  Who goes there?
ARTHUR:    It is I, Arthur, son of Uther Pendragon, from the castle of
Camelot.  King of the Britons, defeator of the Saxons, sovereign of
all England!
GUARD #1:  Pull the other one!
The Quest for the Holy Grail (Monty Python)
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


dashboard work

still need to finish:

[ ] site user stats
[ ] site global config
[ ] site growth+lemmyverse stats


max_token error when using OpenIA provider

Im receiving bellow error when i use any model from OpenAI provider.
I'm receiving bellow error when I use any model from OpenAI provider, even if I use a prompt like a simple Hello, how are you? (With no code selection input).
400 max_tokens is too large: 6000. This model supports at most 4096 completion tokens, whereas you provided 6000.

Code completion is working normaly.

You can try changing the Token limit setting by going to your "chat settings" menu.
Every model has a Token limit it can accept, which is essentially a character limit. Your error seems to be that you have a configuration exceeding these Token limits for the model you've selected.


In Az Network vnet-gateway update command the purpose of the add/remove/set parameters is unlcear

Most of the Gateway settings that need to be configured seem to be available. Either these params should be removed or their purpose should be specified clearly.

"add/remove/set" are not unique to this command. They are generic across nearly all of the CLI's update commands.
This is effectively a dupe of #1582.

Hi Travis – I agree. But do we really need it in this case? Most of the capabilities are already covered through other params. If we do need it then we have to at least specify which settings need it.
From: Travis Prescott<EMAIL_ADDRESS>Sent: Monday, February 13, 2017 8:33 AM
To: Azure/azure-cli<EMAIL_ADDRESS>Cc: Aanand Ramachandran<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Azure/azure-cli] In Az Network vnet-gateway update command the purpose of the add/remove/set parameters is unlcear (#2052)
"add/remove/set" are not unique to this command. They are generic across nearly all of the CLI's update commands.
This is effectively a dupe of #1582https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-cli%2Fissues%2F1582&data=02|01|aanandr%40microsoft.com|9c79235b72cc403ff5be08d4542ded3a|72f988bf86f141af91ab2d7cd011db47|1|0|636226003607193080&sdata=umECXZJLRxgksICVaUCSYsBmSsKFaKsfys%2B3i0v2IyE%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-cli%2Fissues%2F2052%23issuecomment-279444506&data=02|01|aanandr%40microsoft.com|9c79235b72cc403ff5be08d4542ded3a|72f988bf86f141af91ab2d7cd011db47|1|0|636226003607193080&sdata=qhBCLXzqGJYrw%2FFr1HHR1Q2h2m3vvSAIgoYXixDUXII%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAV3chTX0sMDeLXzEI6OchDs-LA7jn2Q8ks5rcIWlgaJpZM4L-222&data=02|01|aanandr%40microsoft.com|9c79235b72cc403ff5be08d4542ded3a|72f988bf86f141af91ab2d7cd011db47|1|0|636226003607193080&sdata=Udcz06Iw9znDHoucUAopXBTGfwiQl2E6dTWhIZOYpp4%3D&reserved=0.

By design, we have made a point to expose the generic parameters and the convenience flags for all of our update commands.

Ok. But can you document what those can be used for (to configure which settings)? This may be a P2 or a P3 bug.
From: Travis Prescott<EMAIL_ADDRESS>Sent: Monday, February 13, 2017 11:28 AM
To: Azure/azure-cli<EMAIL_ADDRESS>Cc: Aanand Ramachandran<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Azure/azure-cli] In Az Network vnet-gateway update command the purpose of the add/remove/set parameters is unlcear (#2052)
By design, we have made a point to expose the generic parameters and the convenience flags for all of our update commands.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-cli%2Fissues%2F2052%23issuecomment-279495855&data=02|01|aanandr%40microsoft.com|d5316a26ce264979b66808d45446708b|72f988bf86f141af91ab2d7cd011db47|1|0|636226108900681580&sdata=4nw1taK4tKZK%2FKRVdUtaV9ots4yidMcY5Ryyk9VIkJ4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAV3chScNQRIt69SoWoBketaAKnD7UJigks5rcK7FgaJpZM4L-222&data=02|01|aanandr%40microsoft.com|d5316a26ce264979b66808d45446708b|72f988bf86f141af91ab2d7cd011db47|1|0|636226108900681580&sdata=Mie77s3mv830MKBsuuLX8ygr2%2FFjafLcS%2BpPScZ8GlM%3D&reserved=0.


No example project, dead links everywhere

https://github.com/mulesoft/docs-mule-runtime/blob/2d0c4f59a037e5c36fbf41920d92d7df5fccd78c/modules/ROOT/pages/cache-scope.adoc contains a reference to Cache Scope with Salesforce Contacts. The project does not exist in anypoint exchange.
Instead or additionally, there exists a project Cache Scope with Fibonacci. The project contains an invalid file structure and cannot be checked out in the latest Anypoint Studio. https://eu1.anypoint.mulesoft.com/exchange/org.mule.examples/cache-scope-with-fibonacci/minor/1.4/
At the bottom of the page is a link to https://github.com/mulesoft/library-examples/blob/v1.4.0/cache-scope-with-fibonacci/README.md. Not even the repository exists anymore, let alone any project files.

@Miladiir Thx for your feedback. The Cache scope doc you are referencing is published here: https://docs.mulesoft.com/mule-runtime/latest/cache-scope

The documentation is very light on specifics. This does not tell me how the default strategy works.
In a scenario where I have four actions within a cache scope, what does the cache scope do exactly. Does it store each indidual result, or does in only store the input and output of the first and last action in the scope?
Alternatively, I could think of another scenario, where it will consider the input payload that is referenced in the first action and use the hash of this payload as a key and it will consider the output payload of the last action and cache that as the result.
So without trying this out with 3-4 scenarios, including vars, transfomers, http request etc, I simply do not know how the cache behaves. This will probably take like 1-2 hours.


Instrument tests with custom macro & export over OTLP

This PR uses a custom #[otel_test] macro to instrument daemon-tests and export the spans over OTLP to Jaeger, when the ITCHYSATS_TEST_INSTRUMENTATION environment variable is set to 1.
This currently uses the simple exporter. I tried the batch exporter, but this strangely caused some tests to hang.
TODOs

[x] Disable instrumentation option for CI
[x] Get gRPC to build on ARM CI, or swap it for tonic (which doesn't currently work)
[x] How can we configure the service name and log levels for crates other than daemon-tests?

Should I squash
Disable instrumentation by default for CI into the first commit?

It seems like the ARM build fails here due to use of gRPC-sys. I did try tonic, but it didn't actually work, so if we can get gprc working that'd be fantastic. The error is:
  CMake Error at CMakeLists.txt:9 (project):
    The CMAKE_CXX_COMPILER:
      aarch64-linux-gnu-g++
    is not a full path and was not found in the PATH.
    Tell CMake where to find the compiler by setting either the environment
    variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
    to the compiler, or to the compiler name if it is in the PATH.

Maybe g++ needs to be added to the path for the ARM run? I am not entirely familiar with this CI setup, though, so I'm not sure how to go about this

if anything, I'd slightly adjust the commit message to say "Disable test instrumentation by default on CI"

Cool, I will make sure to rename it when I rebase!
Another thing: it seems like the ARM build fails here due to use of gRPC-sys. I did try tonic, but it didn't actually work, so if we can get gprc working that'd be fantastic. The error is:
  CMake Error at CMakeLists.txt:9 (project):
    The CMAKE_CXX_COMPILER:
      aarch64-linux-gnu-g++
    is not a full path and was not found in the PATH.
    Tell CMake where to find the compiler by setting either the environment
    variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
    to the compiler, or to the compiler name if it is in the PATH.

Maybe g++ needs to be added to the path for the ARM run? I am not entirely familiar with this CI setup, though, so I'm not sure how to go about this

I'll have a look into this!

if anything, I'd slightly adjust the commit message to say "Disable test instrumentation by default on CI"

Cool, I will make sure to rename it when I rebase!
Another thing: it seems like the ARM build fails here due to use of gRPC-sys. I did try tonic, but it didn't actually work, so if we can get gprc working that'd be fantastic. The error is:
  CMake Error at CMakeLists.txt:9 (project):
    The CMAKE_CXX_COMPILER:
      aarch64-linux-gnu-g++
    is not a full path and was not found in the PATH.
    Tell CMake where to find the compiler by setting either the environment
    variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
    to the compiler, or to the compiler name if it is in the PATH.

Maybe g++ needs to be added to the path for the ARM run? I am not entirely familiar with this CI setup, though, so I'm not sure how to go about this

I'll have a look into this!

Try rebasing on this: https://github.com/itchysats/itchysats/pull/2410
(you can incorporate your PR in yours, or I can merge mine first if this fixes your problem)
I just added C++ compiler; if it's installed, cmake should be enough to make it work.
Note: it would be good to doublecheck with @bonomat whether we have access to C++ compiler on Raspiblitz, where we compile ItchySats too.

I've rebased on top of #2410

I've rebased on top of #2410

oh wow, we fixed the previous error, but there still seems to be some onerous error when cross-compiling to ARM.
I'll spin this up locally and see whether this can be solved. you sure tonic can't be used? 😅

The current compile error is from boringssl, so if we can get rid of that dependency we can make this work I think? gRPC lets us use openSSL rather, but I wonder if opentelemetry-otlp lets us use this...

The current compile error is from boringssl, so if we can get rid of that dependency we can make this work I think? gRPC lets us use openSSL rather, but I wonder if opentelemetry-otlp lets us use this...

we can give this a shot, from the perspective of opentelemetry it shouldn't make a difference.
I found some instructions online how we could use openssl instead:
https://stackoverflow.com/questions/54775076/how-to-cross-compile-a-rust-project-with-openssl

seems like it was already installed :)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'g++' instead of 'g++-aarch64-linux-gnu'
g++ is already the newest version (4:10.2.1-1).
g++ set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 88 not upgraded.

if anything, I'd slightly adjust the commit message to say "Disable test instrumentation by default on CI"

Cool, I will make sure to rename it when I rebase!
Another thing: it seems like the ARM build fails here due to use of gRPC-sys. I did try tonic, but it didn't actually work, so if we can get gprc working that'd be fantastic. The error is:
  CMake Error at CMakeLists.txt:9 (project):
    The CMAKE_CXX_COMPILER:
      aarch64-linux-gnu-g++
    is not a full path and was not found in the PATH.
    Tell CMake where to find the compiler by setting either the environment
    variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
    to the compiler, or to the compiler name if it is in the PATH.

Maybe g++ needs to be added to the path for the ARM run? I am not entirely familiar with this CI setup, though, so I'm not sure how to go about this

I'll have a look into this!

Try rebasing on this: #2410 (you can incorporate your PR in yours, or I can merge mine first if this fixes your problem)
I just added C++ compiler; if it's installed, cmake should be enough to make it work. Note: it would be good to doublecheck with @bonomat whether we have access to C++ compiler on Raspiblitz, where we compile ItchySats too.

seems like it was already installed :)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'g++' instead of 'g++-aarch64-linux-gnu'
g++ is already the newest version (4:10.2.1-1).
g++ set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 88 not upgraded.

interesting, as the CI job wouldn't pass before we added that commit 😳 maybe it cached it after first run or updated paths? no se.

interesting, as the CI job wouldn't pass before we added that commit 😳 maybe it cached it after first run or updated paths? no se.

sorry, I was not clear: the library is already installed on raspiblitz

Success in CI on ARM!! Woo!

Last issue is just around the IDE experience of re-exporting stuff. I'm not sure if this can be helped, though

Last issue is just around the IDE experience of re-exporting stuff. I'm not sure if this can be helped, though

It's a net positive change even with that small awkwardness. IMHO as long as it doesn't come up first, and happens only in tests, it's not too bad.

I've squished this down into two commits - one adding g++ to CI, and one adding instrumentation.

ARM build is failing again 😓

bors r+


📝 Sign Google CLA [Needed for Contribution] 📝

It would be nice if the Bot signed the CLA from Google,
for Contributions to Google Repositories.
It's a really easy Task that can be done in 3 minutes.
https://github.com/google/blockly/pull/2064
https://github.com/google/audion/pull/85
https://github.com/google/wear-screeninfo/pull/1
https://github.com/google/ioweb2015/pull/1542
https://github.com/google/virtual-tutors/pull/1
https://github.com/google/nogotofail/pull/118

So there's good news and bad news.
+1 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.
confused The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.
Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

Cool! There shouldn't be any problem doing this. I can log in and take care of this later tonight
Thanks!

So the @ImgBotApp account has already signed the CLA at https://cla.developers.google.com/clas
Not sure what the issue is here

That's weird, https://cla.developers.google.com/clas shows me that I have signed it too.
I don't see what the problem could be, I need to look deeper at it.

I'm curious if the bot can sign any cla application, such as the one here: https://github.com/Railcraft/Railcraft/pull/1512#issuecomment-430533968

@liach done :)

Could bot sign this as well? https://github.com/vespene-io/vespene/pull/29#issuecomment-434112048

@webknjaz done :)

Thanks :)

I need the Google CLA Signed. https://github.com/GoogleChromeLabs/ProjectVisBug/pull/227

So the bot has already signed the google CLA, but it is not getting picked up for some reason - see above in this thread.
It seems to work with CLA assistant, but not the google version.

Can you sign it on the issue's link? It works.

@mrmajik45 I did follow the issue link and it is signed, my guess is that there is a problem with the CLA tooling on the google side to read the username from a bot account because it shows something like imgbot[bot]
there's a pretty good thread about it here: https://github.com/cla-assistant/cla-assistant/issues/173

@dabutvin  would you mind asking your robot to sign this one as well? 😄
https://cla-assistant.io/temporalio/documentation?pullRequest=1389


Report type-related intrinsics to RyuJIT

We had this disabled because the way we represent runtime types is different from CoreCLR and reporting any of these led to asserts in RyuJIT and bad code.
This lets us optimize common patterns such as:

typeof(T) == typeof(byte)
foo.GetType() == typeof(Foo)

These patterns are pretty commonly used in high performance code paths, so having actual reflection there is pretty bad. This also lets us generate smaller code because a lot of these can be evaluated at compile time (this makes the ASP.NET WebApi sample in the repo 380 kB smaller).
Requires an updated RyuJIT, so this won't work until I get the RyuJIT portion in.
Fixes #5180.

Thank you for finding time to do this!


ADD an option to hide the "Block this site" as a suggestion

Hi Sir, can you add an option to hide the "Block this site" link behind every search result?
You know people only need to block some single sites, but the link shows everywhere, making it a mess on the search page.

I have just added this option (v2.3.0).


Adding support for Philips Aurelle square panel

This panel is basically the same as the rectangle version, just square.
I will create a pull request for the homeassistant.js file too.

Thanks!


Linux version?

Has anyone tried to run on Linux?

It build & opened fine on Linux thanks!
(but I get Error: could not find tiller - maybe a small walkthrough would help :-)
.


Add experimental filtering sampler

Signed-off-by: Maciej Szlosarczyk<EMAIL_ADDRESS>This would be one way to fix #16.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please ask for approval from maciej-szlosarczyk after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

For graphql events it would be activated like this:
  config :opentelemetry,
    sampler:
      {MvOpentelemetry.FilteringSampler,
        %{
          filter_list: [~r/graphql.resolve.field[a-z_\.]+/],
          default: {:parent_based, %{root: {:trace_id_ratio_based, 0.01}}}
        }}

LGTM label has been added.  Git tree hash: 015401c1aaa0d19703ad01b86cf7a9b18307809e

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: antonsatin
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [antonsatin]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Superseded by #25


Add test files to .npmignore

A lot of people complain about node_modules size. So it will be good to take care and clean npm package from unnecessary test files.
@JLHwung You can check npm package content by calling npm pack command and open generated .tgz file.

Great work! I don't realize the yarn.lock can be added to npmignore until I go through https://yarnpkg.com/lang/en/docs/yarn-lock/#toc-check-into-source-control carefully.


GeneSeqToFamily tutorial

Hi @anilthanki  we have changed the way we organize metadata in this repository: I have updated your PR. The metadata are now at the top of the tutorial.md or slides.html files

Hi @nsoranzo and  @anilthanki , I worked on phylogeny and gene families before, do you mind If I contribute to this tutorial?

Hi @Delphine-L please feel free to contribute also this is an old tutorial so it needs an update anyway

Hi @Delphine-L, we've assigned you since you indicated interest, let us know if you have time for working on this :)

Closing this 5 year old PR due to inactivity. Please feel free to re-open or create a new PR @anilthanki and/or @Delphine-L if you still want to add this tutorial


[Draft] Singular name example for storage

Description
Convert example module to check overall impact
Pipeline references

For module/pipeline changes, please create and attach the status badge of your successful run.

Pipeline

Type of Change
Please delete options that are not relevant.

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Update to documentation

Checklist

[ ] I'm sure there are no other open Pull Requests for the same update/change
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings
[ ] My code follows the style guidelines of this project
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (readme)
[ ] I did format my code

Closing together with corresponding issue after completing singular name conversion for module folders


gfortran wrapper adds a number of unused arguments on Darwin

Issue description
On Darwin the gfortran wrapper adds a number of unused arguments that are passed along to clang. clang displays a warning for each of these arguments:
$ gfortran hello.f90
f951: Avertissement: l'option de la ligne de commande « -Wformat=1 » est valable pour C/C++/ObjC/ObjC++ mais pas pour Fortran
f951: Avertissement: l'option de la ligne de commande « -Wformat-security » est valable pour C/C++/ObjC/ObjC++ mais pas pour Fortran
clang-5.0: warning: argument unused during compilation: '-D _FORTIFY_SOURCE=2' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-fstack-protector-strong' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '--param ssp-buffer-size=4' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-fno-strict-overflow' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-idirafter /nix/store/7zcsy4dhx1zcibmqjjnghcmd296bp4ii-Libsystem-osx-10.11.6/include' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-idirafter /nix/store/jrz4jlmjx0yycljlwc6rkr1i0v161zal-gfortran-7.3.0/lib/gcc/x86_64-apple-darwin/7.3.0/include-fixed' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-isystem /nix/store/qjmqrzk8nhn5maa093fhl3finczz72lw-libc++-5.0.2/include' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-isystem /nix/store/jd065p28z3ar0q6nljz479f9mm35v5qn-libc++abi-5.0.2/include' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-isystem /nix/store/llafcziny4071gkahynh9348yqfwvych-compiler-rt-5.0.2-dev/include' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-F/nix/store/2cf0hbdgyixp2jl3k6l5mdg15pvkn8ah-CF-osx-10.10.5/Library/Frameworks' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-isystem /nix/store/qjmqrzk8nhn5maa093fhl3finczz72lw-libc++-5.0.2/include' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-isystem /nix/store/jd065p28z3ar0q6nljz479f9mm35v5qn-libc++abi-5.0.2/include' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-isystem /nix/store/llafcziny4071gkahynh9348yqfwvych-compiler-rt-5.0.2-dev/include' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-F/nix/store/2cf0hbdgyixp2jl3k6l5mdg15pvkn8ah-CF-osx-10.10.5/Library/Frameworks' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-isystem /nix/store/qjmqrzk8nhn5maa093fhl3finczz72lw-libc++-5.0.2/include' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-isystem /nix/store/jd065p28z3ar0q6nljz479f9mm35v5qn-libc++abi-5.0.2/include' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-isystem /nix/store/llafcziny4071gkahynh9348yqfwvych-compiler-rt-5.0.2-dev/include' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-F/nix/store/2cf0hbdgyixp2jl3k6l5mdg15pvkn8ah-CF-osx-10.10.5/Library/Frameworks' [-Wunused-command-line-argument]

This makes the build log of some packages extremely large, and in turn it can cause build failures on Hydra because of the log size limit is exceeded.
/cc #45961
Steps to reproduce
cat <<EOF > hello.f90
program hello
  print *, "Hello World!"
end program hello
EOF
nix-shell -p gfortran --command "gfortran hello.f90"

Technical details

system: "x86_64-darwin"
host os: Darwin 17.7.0, macOS 10.13.6
multi-user?: no
sandbox: no
version: nix-env (Nix) 2.1
channels(smaret): "nixpkgs-18.09pre151052.4477cf04b67"
nixpkgs: /Users/smaret/Documents/Software/nixpkgs

I think that fortran on darwin is a rather under-maintained combination in nixpkgs ATM.

@LnL7 suggested the following fix for packages that use gfortran and clang on Darwin:
stdenv.mkDerivation {
  # ...
  NIX_CFLAGS_COMPILE = stdenv.lib.optionalString stdenv.cc.isClang
    "-Wno-unused-command-line-argument";
}

Could this be implemented in the wrapper itself rather than in each package that uses the wrapper?

This needs to be propagated to everything that uses gfortran? I think using gccStdenv for gfortran packages might be a better then. That's less likely to cause other problems.

I think auto-passing such an option is slightly risky over the long term, as it may hide other errors, e.g. user typos.  (No strong opinion.)  I wonder if using gfortran with clang is actually a "supported" combination upstream; I guess gccStdenv might be better, as you write.


Updating status of a couple of projects

This PR updates the following:

CVS book
Vision framework tutorial

I think the looks pretty good – nice work!

I think the looks pretty good – nice work!


change in filename cross compatibilty

I made a python script with a kdtree to compare the output from the CSB portal with the mbes-lib output.
the kdtree was construct with (lat, lon) values of the 3k points from mbes-lib.
Then asked the kdtree what was the nearest point from the 145 points given by the CSB portal.
The average euclidean distance of the (lat, lon) between the two sets of points was : 0.00015447     ->       +/- 150m
The average delta between each depth of these two coordinates was : 0.0010887711        ->       +/-  11cm


[build] Error on compilation with VSCode on Linux

I followed the instruction for make compilation and for VSCode IDE project, but when I try to start the debug I have this error:
/game: error while loading shared libraries: libraylib.so.301: cannot open shared object file: No such file or directory
The file is missing in the raylib/src folder. If I start the raylib/projects/scripts/build-linux.sh the compilation work and I can start the game. I don't understand what I'm missing.

@grevius5 maybe libraries are not in the path for game?

It seems a path configuration issue on the user side. Closing it.


Request: (PANE LAYOUT) STACKVIEW

Is it possible to add a stack layout for pane arrangement !?.

Please use the wezterm issue tracker instead of this one.


Update ADOT to v0.25.0

Issue #, if available: https://github.com/aws/eks-anywhere-packages/issues/786
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherrypick release-0.14


Short solution needed: "Using enum type" (golang)

Please help us write most modern and shortest code solution for this issue:
Using enum type (technology: golang)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

How to use ENUM type


how can i use single image as input

i want to test your BlazeFace on a single image, which calculator should i use? or take an opencv Mat as input of ImageTransformationCalculator?

You could try modifying the desktop TFLite object detection example in https://github.com/google/mediapipe/blob/master/mediapipe/docs/object_detection_desktop.md#tensorflow-lite-object-detection-demo to take a single image as input, e.g., replacing OpenCvVideoDecoderCalculator with https://github.com/google/mediapipe/blob/master/mediapipe/calculators/image/opencv_encoded_image_to_image_frame_calculator.cc.

@Nicol-Bolas  Thanks for using MediaPipe. My team would love to get feedback from you about your use of MediaPipe
It would be great if you could answer the below questions
What is your use case for MediaPipe?
Any feedback about how easy or difficult it is to use MediaPipe?
Thanks
Ming


multisig credentials

Given @pfeairheller 's recent push, shall we close this?

@AlexAndrei98

This is over a month old and we have a solution already merged, so closing this.


fixed live demo tags in usage and code

Closes #4092
Add the Experimental tags to the live demo on the Tag Usage and Code tabs
New
Add the Experimental tags to the live demo on the Tag Usage and Code tabs
Read-only
Dismissible (unstable)
Selectable (unstable)
Operational (unstable)

Do we want the word unstable in the dropdown similar to what we have on the Tile live demo? I think we should be consistent.

Do we want the word unstable in the dropdown similar to what we have on the Tile live demo? I think we should be consistent.

I think I removed the unstable by looking at AI slug label as the link says it's unstable but label doesn't. Made this like tile component now.


Porting the CAPI sample to the C# bindings side

This adds the CAPI sample for the C# bindings and adjusts the Nrt_append* APIs to not use varargs, as that is not compatible with .NET.
This also cleans up the .NET cmakelist files to build and perform their up to date checks based on the correct set of inputs.

@FiniteReality, could you review the CMake changes and @capnkenny could you review the CAPI changes?

Merging. As per the discussion with Monica in Discord, I'll be submitting a follow up PR to address the CMake requests.


⚠ Jenkins Plugins Artifactory has degraded performance

In 5776b32, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1228 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 0be22dd after 18 minutes.


Retain comments inside return statements

by including the return keyword in the parse tree, so its position is recorded for comment emit.
A simple
            if (node.expression) {
                emitLeadingCommentsOfPosition(node.expression.pos);
            }

inside emitReturnStatement is unsuitable, since multiline-inline comments are not collected as potential leading comments of a position (instead, they get collected as trailing comments for a prior token - in this case, the ReturnKeyword we never recorded the position of), and there's no point of reference to call emitTrailingCommentsOfPosition with.
Fixes #17532

I am slightly concerned about adding another token node for every return statement. At what point does the tree become concrete for all terminal nodes? Is that a cost we're willing to pay?

@DanielRosenwasser I think I could get the correct position by getting the statement start, skipping trivia, then adding "return".length; but that's another special case in the emitter for return statements, which also should be evaluated. If it works (it should?), then I'm OK swapping to doing it that way; its just a fair bit of late calculation for something we already recorded way back in the parser, but decided not to keep.
It's a matter of AST size vs emit time (a small delta, either way); so which is preferable to minimize?

I think I could get the correct position by getting the statement start, skipping trivia, then adding "return".length

This is the approach we took for PropertyAccess and it works well enough. Currently, emitReturnStatement uses writeToken which already does position tracking for source maps. We could augment that to emit comments as well, and possibly end up with higher fidelity for comment emit in other places.

This issue seems to affect all rhs expressions:
function f() {
  var a = /* foo */ 1;
  var b = (1 + /* bar */ a);
  return /* foobar */ (a + b);
}

compiles to
function f() {
    var a = 1;
    var b = (1 + a);
    return (a + b);
}

@scf37 It's not all RHS expressions, but rather all trailing comments of a token which appears in the middle of a parsed node. Once this fix is merged, I plan on looking into doing a similar operation to try to retain comments on other such tokens.

@weswigham Is there an issue for the other token positions where we don't preserve comments? If not, can you add one?

Opened - I was able to find a general issue about generally better comment emit - #2546 - but nothing specific to this area.


usage of redux connect and react-dnd-touch-backend

I got an issue with using redux connect. It works for html5-backend. But when I switch to touch-backend. I can not drag the item actually. Is there anyone met this kind of issue?
I did something like this
import { connect } from "react-redux";
import TouchBackend from "react-dnd-touch-backend";
import { DragDropContext } from "react-dnd";
class App extends Component {
...
}
App = DragDropContext(TouchBackend)(App);
export default connect(mapStateToProps)(App);

this only handles touch event. By drag do u mean w/ a mouse?

Thanks for reminding. It actually works on my real phone. But it doesn't work when I try to test it on chrome with mobile mode. Since I use mouse to simulate touch event. Thanks.


Registration component should match the mockup

New Mockup was provided here: https://github.com/5-gwoap/adopt-a-family/issues/21

Duplicate


Expose prometheus metrics

https://github.com/kubernetes-sigs/controller-runtime/pull/132 has been merged so now we can expose prometheus metrics from the operator.

Right now there is no way to get the configs out of the  operator or orchestrator or the mysql cluster pods, is that right?


Decouple Firebase?

Recently it looks like Firebase has become very integrated into Este - would it be possible to abstract and decouple certain pieces so that all references to Firebase can be removed entirely?

No. Este is monorepo.

I don't think he meant to move it away from este, but merely making it possible to just remove the firebase related files, and includes.

From my opinion, it would be nice to make it easy to maintain a project with Este as the base. Right now it can be hard to decouple. I prefer to keep Este as a remote to merge in changes, but don't want to get into merge hell if possible. Firebase is not used by a lot of people on the backend as there are tons of requirements for "inside the firewall" style hosting. In general if Este can be scrubbed to make it easier to maintain an external project, that is best in my opinion.

I completely agree @justinr1234 - Even make redux swappable if you ask me :P

Arguments to make Firebase optional are indeed receivable.
But please, don't remove Redux. It's the de facto way to manage state in React (these days actually).
This repo has strong opinions, but that's also what makes it compelling IMHO.

The success of an open source project has a lot to do with whether or not people feel compelled to contribute. Este can be painful to contribute to at times. Making strong opinions optional helps to alleviate burden on the multitude of people who could possibly use this project (say by way of "gulp remove-firebase"). The idea is to make as many things optional or swappable as possible.

The reason I suggested to have redux as an optional part, is because we use relay, and those two doesn't really go hand in hand, if you ask me. Of course, you can use both, but I'd rather use one, and not both. :)

@Multiply is right, and I agree with @justinr1234.  Sure, monorepo, whatever - but that assumes some agnostic features that are lite and can be easily decoupled if you want.  Firebase is very opinionated and either you're using Firebase or you aren't.  Not everything can be "monorepo", you either have one, or the other.  It's easy to strip out Bootstrap (we're using Foundation), but it's not so easy to strip out the Firebase stuff.  'queryFirebase' replaced the much more agnostic 'fetchComponentDataAsync'.  I apologize if I don't understand all of the changes - perhaps I'm wrong and it's easy to remove?

This is reason why I unfolow este in favour of react-starter-kit. It does not solve react-native either flux implementation but I quickly add redux support and react-intl support on top of redux

@steida I think what really threw me off was that queryFirebaseServer is only called when NOT in a Firebase environment, and I still didn't quite understand its need.  After spending some time trying to get server-side async loading working I realized this was basically just a rework of fetchComponentDataAsync.  I would recommend a namechange, perhaps pulling this out into its own file so that it's clearly separate from the Firebase logic.

No, it's not rework of fetchComponentDataAsync. It's new pattern - prerendering to initiate data fetching.

Sure you can refactor it and send PR. Thank you.

I'd be happy to send a PR if I knew more what was going on, but it doesn't seem to be working for me though.  It doesn't load dynamic data until the client-side kicks in.  The previous iteration I had it checking the UserAgent so I can load dynamic data server-side if it's a spider for SEO, or defer to the client if it's a browser.

I just tested server preloading, check firebase example source code. It works. You can control what should be preloaded on the server via some flag. Check code. It's easy.

I just tested server preloading, it works. Check firebase example source code on your computer. Note that Este example runs on Firebase static hosting, so there is no server rendering.
You can control what should be preloaded on the server via some flag. Check code. It's easy.

@steida Not quite sure I understand what you mean.  I don't need to preload anything, rather I would like to keep the page from rendering until the fetch promises complete.  This way, if a search engine is viewing the site they see any dynamic content that is reliant upon an external api.
We aren't using Firebase.  I've modified a TodosPage so that it fetches a list of Youtube videos within the 'componentDidMount' method, but it always renders the list in the browser, not the server.  If you do a 'view source' you see the original content before any dynamic content has loaded.
With your previous iteration this worked properly, albeit a bit touchy.  I found it only worked if I fetch the action on the top "page" level.  Perhaps I'm doing it wrong?

@steida I went back through and found your commit where you removed the Todos example along with the async fetch - https://github.com/este/este/commit/e192695c2d527297cfd40ae0ecc9804344ee3a86
I'm very curious to know the reasons for removing the Todos example and replacing with a strictly Firebase-dependent version.  Again, I apologize if I'm not exactly understanding everything, I'm still learning React/Redux and not quite familiar with all of the design patterns.  Your library and thoughts are much appreciated, thanks again.

@Mode7James For your scenario, it looks like you could use something like 'async-props'. Never tried it myself (so I'd be pleased to get your feedback :))
Of course, since 'async-props' is rather old in modern JS land (almost 6 months), it has probably already been replaced by something shinier ^^

If someone want to refactor new Este "double rendering" pattern, do it and then send pull request. Thank you. Related to https://github.com/este/este/issues/847


Http response stream not working on Flutter Web.

I'm trying to get a stream of bytes via http request. This works on mobile but not on web.
Basically, the response.stream works on MOBILE but not on WEB.
Steps to Reproduce
Run the code below, no libraries needed
Expected results:  The bytes printing on console
Actual results: Hangs forever on request, but ONLY on WEB, on mobile works perfectly.

Code sample
import 'package:flutter/material.dart';
import 'package:http/http.dart' as http;

void main() async {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key, required this.title}) : super(key: key);

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  http.Client client = http.Client();

  Stream<List<int>> getVideo() async* {
    String url = "URL_HERE";

    var request = http.Request("GET", Uri.parse(url));
    var response = await client.send(request);
    yield* response.stream;
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            Expanded(
                child: Center(
                    child: StreamBuilder<List<int>>(
              builder: (context, snapshot) {
                if (snapshot.hasData) {
                  print(snapshot.data);
                  return const Center(
                    child: Text("OK!"),
                  );
                }

                if (snapshot.hasError) {
                  return Center(
                    child: Text('ERROR ${snapshot.error}}'),
                  );
                }

                return const Center(
                  child: CircularProgressIndicator(),
                );
              },
              stream: getVideo(),
            ))),
          ],
        ),
      ),
    );
  }
}

Flutter doctor
[✓] Flutter (Channel stable, 2.8.1, on macOS 12.0.1 21A559 darwin-x64, locale
    pt-BR)
[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 13.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.63.2)
[✓] Connected device (2 available)

• No issues found!

Unfortunately I cannot share the URL that I'm using for security reasons, but the problem is the same as in Issue #79879
On the web console, I can see that the request was successful (200 OK) and I'm receiving the stream.
It's not a CORS problem, since I successfully receive the response.
Both on ANDROID and IOS works perfectly.
I already tried another way removing the await keyword from request and using the response.asStream().listen but the problem persists

Hi @danielWagnerr,
From what I can see, the issue is related to a 3rd party plugin rather than to Flutter itself. Please open the issue in the dedicated repository.
Closing, as this isn't an issue with Flutter itself.
If you disagree, please write in the comments,
providing your flutter doctor -v, your flutter run -v,  your pubspec.yaml
a minimal reproducible code sample that does not use 3rd party plugins,
and I will reopen it.
Thank you