text:
I need nebula-operator arch=linux/arm64 image

I need nebula-operator arch=linux/arm64 image, thanks!

@wylovejzj OK, we will build arm64 image and push to docker hub.

thanks!发自我的手机-------- 原始邮件 --------发件人： "kevin.qiao" @.>日期： 2022年9月26日周一 上午10:12收件人： vesoft-inc/nebula-operator @.>抄送： wangyue @.>, Mention @.>主    题： Re: [vesoft-inc/nebula-operator] I need nebula-operator arch=linux/arm64 image (Issue #156)
@wylovejzj OK, we will build arm64 image and push to docker hub.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@wylovejzj  The image with latest tag has support arch linux/arm64.

ok,thank you very much!发自我的手机-------- 原始邮件 --------发件人： "kevin.qiao" @.>日期： 2022年10月9日周日 傍晚5:50收件人： vesoft-inc/nebula-operator @.>抄送： wangyue @.>, Mention @.>主    题： Re: [vesoft-inc/nebula-operator] I need nebula-operator arch=linux/arm64 image (Issue #156)
@wylovejzj  The image with latest tag has support arch linux/arm64.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@wylovejzj The image with latest tag has support arch linux/arm64.

Hi,  the  visit to the docker hub sometimes is unstable in china. Can you upload the docker artifacts to your Github Release just like redis-operator project in the link https://github.com/spotahome/redis-operator/releases ?

@wylovejzj The image with latest tag has support arch linux/arm64.

Hi,  the  visit to the docker hub sometimes is unstable in china. Can you upload the docker artifacts to your Github Release just like redis-operator project in the link https://github.com/spotahome/redis-operator/releases ?

could you plz try with some docker hub mirrors?
I.E. https://yeasy.gitbook.io/docker_practice/install/mirror

OK，it maybe a good way to achive docker images.

I will close the issue, please re-open it if you have other questions.

repo: vesoft-inc/nebula-operator


text:
Improve config proxy dumpcache command a bit

Log a bit when running, handle errors better, more output when something goes wrong

👍 Great

source: gharchive/pull-request

authors: hmusum jobergum

repo: vespa-engine/vespa

license_type: permissive

license_source: github-api


text:
Verify that SameElementItem is not touched by query canonicalization.

@bratseth PR

Test failure was unrelated


text:
Add Dockerfile & Mark Rain metric as Counter

Howdy,

Added a Dockerfile, maybe you can add a pipeline for automatic build and pushes to github registry.
Set Rain(mm) metric as prometheus counter, as the value constantly increases.

Note to self: This will break my grafana dashboards ;-)

oh, that was already changed here: https://github.com/vetinari/brickd_exporter/commit/7672eb6ea951ae4e1e6118f934de65fcbecd1e1d#diff-4c0db22217a539a55b78b9ac997a6fb2365452c054822af355b1e02a66749315

authors: tonobo vetinari

license: MIT


text:
[Bug] Command failed with code null

Escrcpy v1.26.3
macOS 15.0.1
在执行「开始镜像」操作时出现错误： Command failed with code null

搞定了
将设置中的 scrcpy 路径：/Applications/Escrcpy.app/Contents/Resources/extra/mac-arm64/scrcpy/scrcpy
修改成： /opt/homebrew/Cellar/scrcpy/2.7/bin/scrcpy

感谢反馈，我在 v1.26.3 中默认集成了 scrcpy,但是似乎没起作用，这确实导致了一些问题，我将在下个版本暂时禁用它，等待其彻底稳定后在开启。

source: gharchive/issue

authors: viarotel whjstc

repo: viarotel-org/escrcpy


text:
chore(main): release 1.28.1

:robot: I have created a release beep boop
1.28.1 (2024-12-20)
Performance Improvements

♻ Optimize QR code connection experience (86f5e69)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.28.1
:sunflower:


text:
Added draft architecure file

Added a PlantUML file with a draft architecture for flyxc

Summary by CodeRabbit

New Features

Introduced a visual architecture diagram outlining the system's structure and interactions between key components on Google Cloud Platform (GCP) and AWS.
Enhanced understanding of the system through clear representation of user interactions, data flow, and service integration.

Thanks @Fabian1535 !
I think you can create a doc folder at the source of the repo.
It would be nice to add a short description of the file and the way to generate an image in the top level CONTRIBUTING.md. That's also where we should insert the generated image when we are happy with it (the image file itself can go to the newly created doc folder).
Thanks!

Created doc folder and added some info on CONTRIBUTING.md

I just learned that GH markdown actually support diagrams: https://github.blog/developer-skills/github/include-diagrams-markdown-files-mermaid/
Maybe something to explore... and then there is no need to install anything

repo: vicb/flyXC


text:
ERROR: Invalid requirement: 'Package  Version' (from line 1 of requirements.txt)

Received the error after run pip install -r requirements :

"ERROR: Invalid requirement: 'Package  Version' (from line 1 of requirements.txt)"

requirements.txt:
Package              Version
-------------------- ---------
absl-py              0.15.0
anyio                3.5.0
asgiref              3.5.1
astor                0.8.1

@brukas  it has been modified, you can also check setup.py that has the code to extract clean required library format.


text:
Test fails: test_viewing_modes.py

This test is failing on Python 3.7 (macOS 10.12 Sierra):
$ python3.7 test_viewing_modes.py
..F.
======================================================================
FAIL: test_show_result_for_search_files (__main__.TestViewingModes)
Testing def show_result_for_search_files. Search by extension.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test_viewing_modes.py", line 137, in test_show_result_for_search_files
    shallow=False), True)
AssertionError: False != True

----------------------------------------------------------------------
Ran 4 tests in 0.004s

FAILED (failures=1)

A complete uninstall and reinstall seems to have solved this issue. I will reopen it if it happens again.

repo: victordomingos/Count-files


text:
Typo in documentation

Its super minor, but in the documentation for chance.url()
chance.url({path: 'images'})
=> 'ttp://tainvoz.net/images'

should be
chance.url({path: 'images'})
=> 'http://tainvoz.net/images'

Good find, fixed!

authors: alexsomeoddpilot victorquinn

repo: victorquinn/chancejs

license: mit

license_source: bigquery


text:
Include instructions for integration with eclipse

The project worked great and really made things easier. I think it would help eclipse newbies if you included an eclipse section in the documentation that explained that they should do the following:
right click on the project and click configure>convert to ceylon.
Also, in order to run a ceylon program in eclipse you must first right click on the project and click build path. then navigate to ceylon Build>build paths. Then change the output folder at the bottom of the window from target to target/classes.  Finally, click apply.

I don't have much experience with maven and eclipse, is this something you could kindly contribute ?

Ok. I'll do that

thanks!

repo: vietj/ceylon-maven-plugin


text:
Some discussion

Hi bro @dvbui

Great progress!
Do you need a sub-domain at vietspeak don't you? Please tell me.
I can work with front-end, so please tag me if you have no much time to handle it.

Good afternoon,
My current plan is to make sure that the new VietSpeak Bot becomes available ASAP for beta testing, so a front-end or a sub-domain is not needed at the moment. The current front-end is for testing purposes only and nor for production.

Sure! But no need to hurry.

authors: dvbui yeungon

repo: vietspeak/VietSpeakOJ


text:
Add Continuous Integration

Closes #3.
Things have never worked so well before.

[x] Generate C# protobuf sources
[x] Build libmediapipe_c on workflow dispatch

[x] Windows
[x] Linux (CPU)
[x] Linux (GPU)
[x] MacOS

[x] Deploy Nuget packages on pre-/release

[x] Mediapipe.Net.Framework.Protobuf
[x] Mediapipe.Net.Runtime.CPU
[x] Mediapipe.Net.Runtime.GPU

[x] Good release text
[ ] Deploy packages to GitHub

[ ] Deploy packages to Nuget (waiting for a Vignette Microsoft account)

Niget


text:
Update zio, zio-test, zio-test-sbt to 2.0.0-RC4

Updates

dev.zio:zio
dev.zio:zio-test
dev.zio:zio-test-sbt

from 2.0.0-RC3 to 2.0.0-RC4.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

labels: library-update, early-semver-pre-release, semver-spec-pre-release, commit-count:1

Superseded by #312.

repo: vigoo/clipp


text:
changed styling of main header and buttons

changed styling of main header and buttons

Good Job @krapirastogi

authors: krapirastogi vijayyprajapati

repo: vijayyprajapati/Share-Your-Bookmarks


text:
1.0.0 release

Once the https://github.com/vikejs/vike/labels/v1 release %3Astar2%3A tickets are implemented, Vike can be considered a feature complete, highly polished, and robust tool to build modern apps.
Plan:

[x] Rename vite-plugin-ssr to Vike.
[ ] Stable release of the https://github.com/brillout/vite-plugin-ssr/issues/578 (and soft-deprecate old design).
[ ] Promote and polish vike-react/vike-solid/vike-vue.
[ ] Add Bati's UI to https://vike.dev.
[ ] Implement https://github.com/vikejs/vike/labels/v1 release %3Astar2%3A tickets.
[ ] Rehaul marketing pages to target a wider audience with a more professional/dry tone. (The current copy has more of a personal/hobbyist/passionate tone.)
[ ] Make docs website prettier.
[ ] Marketing, marketing, and marketing. (Lots of comments and blog posts on social news sites, reach out to news sites & influencers, automatically track relevant news, ...)

Vike's V1 release alone is probably enough to grow to 100k weekly downloads, but we still want to invest in marketing to grow beyond 100k.

Is v1 okay?

@BlackCubeNo99 Yes the v1 roadmap is still the plan. (Althoug the Vike rename may happen earlier than planned.)

I just commented here to see the day Vike released v1 - To see your sweet of your efforts in a long time!
Thank you!

Rehaul marketing pages to target a wider audience with a more professional/dry tone. (The current copy has more of a personal/hobbyist/passionate tone.)

Please don’t. :) Professional/dry tone is very uninspiring, and the marketing pages are very detailed now, just like developers like it.

I do intend to keep a unique touch to Vike's copy (e.g. I'll probably keep the part about us being passionate), but I do think that a professional/dry tone is paramount for gaining trust: we're surious about what we do and I want to communicate that.

ETA: end of this summer.

repo: vikejs/vike


text:
Fix issue #836

Issue #836 (opened by me) fixed.

@Suiram1701 Thank you for the PR. I'll take care of this.

repo: vikramlearning/blazorbootstrap


text:
More than one rows in export file for one street

If same street has more than one maintenance dates in export file, only last one will stay.

should mainentance data separated into its own table?

Tried to fix with updating only next day data, but run into problems:
2016-01-28,Melkonkatu,"Parillinen puoli 12-18",00210,60.1506801,24.8828643
2016-01-28,Melkonkatu,"Pariton puoli 7-12",00210,60.1506801,24.8828643
So it will need maintenance table to handle multiple information


text:
[WIP] Rewrite wordcount plugin

This is a major rewrite but the principles are mostly the same. The old code had a weird structure, unnecessary autocommands, and support for visual word counting hacked into it (and that's undocumented). The new implementation is significantly faster, and the code structure makes more sense (at least in my subjective opinion). Everything is complete except the documentation, which is why I tagged this [WIP]. If everything else is ok I'll update that.
The most major change is using a new function to interface with the formatter. Originally the formatter was itself responsible for actually getting the wordcount, which doesn't make sense, and also makes a lot more work for anyone wanting to write a formatter. Now the wordcount plugin itself handles the logic of getting the wordcount; a new function - to_string(), is called, which takes the wordcount number and formats it. Any formatter will support visual mode this way, since the visual wordcount is just passed to to_string(). The old format() function is still supported though, so nothing should break.
Because the wordcount plugin gets the wordcount itself, it can be cached so that the formatter only gets called when the wordcount has changed. That massively reduces calls to the formatter and I think it's the most significant optimisation to the logic.
I changed g:airline#extensions#wordcount#filetypes to support a list of filetypes, more intuitive than a pattern match (and ['all'] enables word-counting for all filetypes). The old pattern match is still tried if it isn't a list.
No CursorMoved autocommands are needed anymore, the logic is triggered directly from the statusline through airline#extensions#wordcount#get(). The old code registered CursorMoved autocommands and calculated the wordcount for all buffers, even ones that never had to display a wordcount - it was just never used in the statusline. So that's a massive optimisation for all buffers where the user doesn't want word-counting.
The code is also split up into more functions, with different functions being defined for compatiblity with old Vim/old-style formatters, a bit of a crude dynamic dispatch approach. I also set the locale specific seperator once only at plugin load (under the assumption that people don't change their locale in the middle of an editing session).
Some numbers (Vim 8.1, patches 1-374):
I typed in the same couple paragraphs of text with and without the rewrite. The major improvement is the reduction in calls the formatter. From:
FUNCTION  airline#extensions#wordcount#formatters#default#format()
    Defined: ~/.vim/devel/vim-airline/autoload/airline/extensions/wordcount/formatters/default.vim line 6
Called 709 times
Total time:   0.192237
 Self time:   0.118619

to:
FUNCTION  airline#extensions#wordcount#formatters#default#to_string()
    Defined: ~/.vim/devel/vim-airline/autoload/airline/extensions/wordcount/formatters/default.vim line 23
Called 143 times
Total time:   0.010432
 Self time:   0.010432

To measure the total improvement, compare the "main" function, which sets off the call chain to update b:airline_wordcount if necessary. In the old version that is s:wordcount_update() (called by autocommand):
FUNCTION  <SNR>94_wordcount_update()
    Defined: ~/.vim/devel/vim-airline/autoload/airline/extensions/wordcount.vim line 10
Called 711 times
Total time:   0.349182
 Self time:   0.156945

After the rewrite, it's airline#extensions#wordcount#get(), called from the statusline:
FUNCTION  airline#extensions#wordcount#get()
    Defined: ~/.vim/devel/vim-airline/autoload/airline/extensions/wordcount.vim line 69
Called 735 times
Total time:   0.124206
 Self time:   0.046229

So that's almost 3 times faster. For buffers where wordcounting is not enabled s:wordcount_update() would still run, and incur a performance cost. Now there is no performance penalty for filetypes where word counting is not used.
I documented the exact changes in each commit message. The plugin should still work reverting any number of commits I added.

thanks!

sorry, I thought this was ready to be included. If you could please create a new PR for the updated documentation that would be appreciated. Thanks.

in addition, I just saw a couple of errors from the wordcount() extension after merging this, however I am not able to reproduce. I fixed one possible error, but please check carefully that still everything works.

@flemingfleming I was not able to access g:airline#extensions#wordcount#filetypes since it is not given a default value. I'm not good at vimscript so this took a while for me to find (ashamed to say I spent too much time on this :P)
The documentation is not updated either so it doesn't reflect that this variable no longer exists. I just hacked it by adding it in manually again but it's probably not the fix you wanted... /me shrug
This was the line that suddenly stopped working
" let g:airline#extensions#wordcount#filetypes = g:airline#extensions#wordcount#filetypes . "|pandoc"
didn't work even after changing it to
call add(g:airline#extensions#wordcount#filetypes, "pandoc")
because of reasons described.

authors: chrisbra flemingfleming thomastanck

repo: vim-airline/vim-airline


text:
how to autopep8 a python file to --max-line-length 80

currently, it doesn't work, how to make this happen?
I could change in my private branch.

I think you just have to set the &textwidth property in your buffer?

how to set this to all *.py files?
I don't want to only set this to one buffer, which means I need to set buffer by buffer.

Use an autocommand. You can google or ask chatgpt on how to do this. It's a pretty common thing :)

authors: chtenb huangyingw

repo: vim-autoformat/vim-autoformat


text:
Update invite URL

Closes #308

こんな感じでどうでしょ?

LGTM :+1:

authors: mattn thinca


text:
Broken SELECT mode when remapping <LeftDrag>

Steps to reproduce

Create ~/leftdrag.vim:

set selectmode=key,mouse

function! MyFunc()
endfunction
noremap  <LeftDrag> <LeftDrag><Cmd>call MyFunc()<CR>
noremap! <LeftDrag> <LeftDrag><Cmd>call MyFunc()<CR>

Run vim:

vim --clean -g +'so ~/leftdrag.vim' README.md

Do text selection with mouse. Mode shown at the bottom is -- VISUAL --.

Expected behaviour
Mode shown at the bottom is -- SELECT --.
Version of Vim
8.2.4804
Environment
OS: Debian 11
Terminal: GUI
Logs and stack traces
No response

Inferring from the comment in the code this seems to be intentional:
/*
 * Start Select mode, if "c" is in 'selectmode' and not in a mapping or menu.
 */
    void
may_start_select(int c)
{
    VIsual_select = (stuff_empty() && typebuf_typed()
		    && (vim_strchr(p_slm, c) != NULL));
}

Sergey Vlasov wrote:

Steps to reproduce

Create ~/leftdrag.vim:

set selectmode=key,mouse

function! MyFunc()
endfunction
noremap  <LeftDrag> <LeftDrag><Cmd>call MyFunc()<CR>
noremap! <LeftDrag> <LeftDrag><Cmd>call MyFunc()<CR>

Run vim:

vim --clean -g +'so ~/leftdrag.vim' README.md

Do text selection with mouse. Mode shown at the bottom is -- VISUAL --.

Expected behaviour
Mode shown at the bottom is -- SELECT --.

This is not specific for , anything that follows  in the
mapping will make it not work.
Looking at the code, this was done for typed keys, not for mouse events.
I think we can allow for following typeahead when checking for a mouse
event, since they are not in a regular mapping, only intentional.
I can make a patch, but I'll leave it for someone else to make a test,
that is more work.
Without the patch it should also work when you put  at the end
of the mapping.
--
Micro$oft: where do you want to go today?
Linux: where do you want to go tomorrow?
FreeBSD: are you guys coming, or what?
/// 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    ///

authors: brammool noscript zeertzjq

repo: vim/vim

license: Vim


text:
TextYankPost is emitted after leaving Visual mode

If I start Vim with the following minimal vimrc (vim -Nu /tmp/vimrc some_file):
augroup my_textyankpost
    au!
    au TextYankPost * call s:hl_yanked_text()
augroup END

fu! s:hl_yanked_text() abort
    try
        if v:event.operator != 'y'
            return
        endif

        let text = v:event.regcontents
        let type = v:event.regtype
        if type ==# 'v'
            let text = join(v:event.regcontents, "\n")
            let pat = '\%'.line('.').'l\%'.virtcol('.').'v\_.\{'.strchars(text, 1).'}'
        elseif type ==# 'V'
            let pat = '\%'.line('.').'l\_.*\%'.(line('.')+len(text)-1).'l'
        elseif type =~# "\<c-v>".'\d\+'
            let width = matchstr(type, "\<c-v>".'\zs\d\+')
            let [line, vcol] = [line('.'), virtcol('.')]
            let pat = join(map(text, {i,v -> '\%'.(line+i).'l\%'.vcol.'v.\{'.width.'}'}), '\|')
        endif

        let id = matchadd('IncSearch', pat, 0, -1)
        call timer_start(150, {-> exists('id') ? matchdelete(id) : ''})
    catch
        echohl ErrorMsg
        echom v:exception
        echohl NONE
    endtry
endfu

And then copy some text, the latter is briefly highlighted with the highlight group IncSearch which is the purpose of the code. However, if I visually select some text, then press Escape to get back to normal mode, the selection is briefly highlighted. It seems that TextYankPost is emitted when you leave visual mode. I don't think it should because the help doesn't talk about leaving visual mode:
After text has been yanked or deleted in the current buffer.

Besides, if I delete the visual selection, a region of text whose dimension matches the one of the deleted text is briefly highlighted. It shouldn't because the function responsible for the highlighting (s:hl_yanked_text()) begins with the following check:
if v:event.operator != 'y'
    return
endif

It seems to indicate that when you leave visual mode, be it by pressing Escape or by deleting the visual selection, TextYankPost is emitted and the registered operator in v:event.operator is y, while it should be d when you delete the visual selection.

Here's a gif to illustrate.

Environment:

vim --version:      VIM - Vi IMproved 8.0  Included patches: 1-1397
Operating system:     Ubuntu 16.04.3 LTS
Terminal emulator:    rxvt-unicode v9.22
Terminal multiplexer: tmux 2.3
$TERM:              screen-256color
Shell:                zsh 5.3.1

Is v:event.regname * (star) in this case?

@andymass  Ah yes, you're right, v:event.regname is indeed *.

Initially, I thought it was a bug because I couldn't reproduce in Neovim v0.2.0, but it seems the event is emitted because by default Vim copies the visual selection in one of the two selection registers, *. It could be useful to implement a visual ring, for the last visually selected texts, similar to a kill ring for the last deleted texts.
For the moment, I changed the condition to test the name of the register:
    if v:event.operator != 'y' || v:event.regname ==# '*'
        return
    endif

Thank you @andymass, I'm closing the issue, since it doesn't seem to be a bug.

authors: andymass lacygoill


text:
add postfix proto main.cf.proto

Postfix updates include .proto files

Please also update the test: src/testdir/test_filetype.vim

authors: KodeToad brammool


text:
runtime(vim): Update base-syntax, match shebang lines

Match shebang lines in Vim9 and legacy script.
Mark these as an error if they appear anywhere other than the first line of a legacy-script file.  In Vim9 script these match as normal line comments rather than an error.

oh does this actually work? can we use a shebang line and run a vimscript directly? Is this documented somewhere?

Interesting, I wasn't aware. of this. I searched the help for shebang but didn't find anything, so let me add this help-tag

oh does this actually work? can we use a shebang line and run a vimscript directly? Is this documented somewhere?

interesting too, but how to run it directly? i tried the example in its help, then ./foo.vim seems failed.
// via bash cli
--
shane.xb.qian

You need to make it executable: chmod +x foo.vim && ./foo.vim

You need to make it executable: chmod +x foo.vim && ./foo.vim

yes, it was executable; after look into a bit more, seems the example of help was not accurate, it maynot find vim without path.
--
shane.xb.qian

The example worked for me correctly. Of course you need to remove the :q

no, just the shebang needed to specify where vim is as general shebang it is. :sweat_smile:
// but nevermind, it should be no common fixed answer where vim must be.
--
shane.xb.qian

How about this:
#!/bin/vim -S

let mylogbook='$HOME/logbook.md'
exe ':e ' .. mylogbook
$
put ='## ' .. strftime('%m. %b %Y')
norm! o

no, first line was the matter.

authors: Shane-XB-Qian chrisbra dkearns


text:
fix default shell

Sorry, https://github.com/vim/vim/commit/dcaa61384ca76e42f7feda5640fb85b58cee03e5 break default shell for termianl.

Codecov Report

Merging #1970 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1970      +/-   ##
==========================================
- Coverage   74.68%   74.68%   -0.01%
==========================================
  Files          77       77
  Lines      125779   125779
  Branches    28147    28147
==========================================
- Hits        93942    93941       -1
+ Misses      31837    31834       -3
- Partials        0        4       +4

Impacted Files
Coverage Δ

src/if_py_both.h
76.05% <0%> (-0.14%)
:arrow_down:

src/channel.c
81.75% <0%> (-0.09%)
:arrow_down:

src/os_unix.c
52.44% <0%> (-0.05%)
:arrow_down:

src/gui.c
45.66% <0%> (+0.15%)
:arrow_up:

src/if_xcmdsrv.c
86.48% <0%> (+0.18%)
:arrow_up:

src/version.c
80.2% <0%> (+1.01%)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-io mattn


text:
This commit confirms the completion of UML diagrams for phase 1.By ad…

…ding the structural UML diagram for the human detector, all UMLs are done and we can proceed with the actualization for the files in the libs folder

LGTM


text:
chore(feat-multi-module-components): release 0.76.7

:robot: I have created a release beep boop
0.76.7 (2022-11-18)
BugFixes

switching fogg gh ci to pull_request broke commits (#34) (7059854)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/vincenthsh/fogg/releases/tag/v0.76.7 :sunflower:

repo: vincenthsh/fogg


text:
Add new forms components

It would be good to have Switch and Range Form components.

Probably should implement these as plugins, since there is no APEX native components to generate them.

fixed in https://github.com/vincentmorneau/material-apex/commit/259d915564e5f6b3171f7a6fc15715bbff73861e

repo: vincentmorneau/material-apex


text:
Add Laravel 5 support

I'll try to get this done around the release of @laravel 5.

Yes please

This is merged in the 2.0.0 release.

Thanks a lot!

repo: vinkla/translator


text:
Errors when loading config

These are the errors I get when loading any config, including auto load. this makes the lib unusable for games that detect console outputs
The config loads fine, for the most part (only 1 keybind loads, no matter how many you assign)

1st error is because you have a Multi-select dropdown where you did Options.abc.Value = 'string' instead of Options.abc.Value[idx] = true/false
2nd error is coming from your script not LinoriaLib - specifically a slider callback

authors: kqmeta violin-suzutsuki

repo: violin-suzutsuki/LinoriaLib


text:
java.lang.RuntimeException: createContext failed: EGL_BAD_CONTEXT

09-21 17:53:45.852 3615-3720/com.hellovr E/AndroidRuntime: FATAL EXCEPTION: GLThread 31579
                                                           Process: com.hellovr, PID: 3615
                                                           java.lang.RuntimeException: createContext failed: EGL_BAD_CONTEXT
                                                               at com.google.vr.ndk.base.GvrSurfaceView$EglHelper.throwEglException(GvrSurfaceView.java:1226)
                                                               at com.google.vr.ndk.base.GvrSurfaceView$EglHelper.throwEglException(GvrSurfaceView.java:1217)
                                                               at com.google.vr.ndk.base.GvrSurfaceView$EglHelper.start(GvrSurfaceView.java:1051)
                                                               at com.google.vr.ndk.base.GvrSurfaceView$GLThread.guardedRun(GvrSurfaceView.java:1479)
                                                               at com.google.vr.ndk.base.GvrSurfaceView$GLThread.run(GvrSurfaceView.java:1323)

React Viro 1.1.0 on Samsung S8

Hi @leocavalcante,
We just tried a new Hello World Scene with React Viro 1.1.0 on our Samsung S8+ and it works.
So we have a few questions:

Is your Google VR Services updated to the latest version (via the Play Store)?
Are you running the Hello World Scene? If not, can you try the Hello World scene?

Thanks,

Closing due to inactivity.
If you still have issues, feel free to re-open this issue or create a new one.
The latest releases are here:
React Viro - https://docs.viromedia.com/docs/releases
ViroCore - https://virocore.viromedia.com/docs/releases
Thanks for using Viro!

authors: achuvm leocavalcante

repo: viromedia/viro


text:
fedora rawhide: Failed to pull from repository: g-io-error-quark

In edge-installer, virt-install is not able to boot BIOS VM with installer blueprint.
Fedora rawhide compose Fedora-Rawhide-20230716.n.0
osbuild-89-2.fc39.noarch.rpm
osbuild-composer-85-1.fc39.x86_64.rpm
weldr-client-35.11-1.fc39.x86_64.rpm
BIOS VM issue log:
================================================================================

================================================================================
Installation

1) [x] Language settings                 2) [x] Time settings
       (English (United States))                (America/New_York timezone)
3) [x] Installation Destination          4) [x] Network configuration
       (Automatic partitioning                  (Connected: enp1s0)
       selected)
5) [ ] Root password
       (Root account is disabled)

================================================================================
================================================================================
Progress

Setting up the installation environment
.
Configuring storage
Creating disklabel on /dev/vda
Creating ext4 on /dev/vda2
Creating ext4 on /dev/vda1
.
Running pre-installation scripts
.
Running pre-installation tasks
.
Installing the software
Starting pull of fedora/39/x86_64/iot from fedora
================================================================================
================================================================================
Error

The following error occurred while installing the payload. This is a fatal error
and installation will be aborted.

Failed to pull from repository: g-io-error-quark: opening repo:
opendir(/run/install/repo/ostree/repo): No such file or directory (1)

Press ENTER to exit:

Filed bug https://bugzilla.redhat.com/show_bug.cgi?id=2223289


text:
[Bug] mouse-movement not working when using some controlled props

Description
When controlled props are updated/restricted when handling the cameraChanged events, map can't be dragged anymore.
(source: #423)
Steps to Reproduce
https://codesandbox.io/p/devbox/snowy-dream-hnwmyh?file=%2Fsrc%2Fapp.tsx%3A19%2C1-20%2C1
Environment

Library version: 1.1.0
Google maps version: 3.57.4 (weekly)
Browser and Version: any
OS: any

Logs
No response

Hi, I am having this exact issue where I can't drag / interact with the map if I have controlled props and update them from the cameraChanged events. I saw this closed similar issue https://github.com/visgl/react-google-maps/issues/436 that was created after this issue was opened so is this fixed? 🤔

@shirleyodeng Unfortunately not, and it seems this is going to be very hard to fix (if possible at all), but I am on it.
In the meantime, can you tell me what you are using the controlled props for? Maybe there are alternative solutions that work for your use-case.

Thanks for the speedy reply @usefulthink.
I have a map component which has either one or two markers. If it has two markers, I would it to center the map accordingly on load. You can see that I've used markerOne's coordinates for the center. So I saw that on load, it will trigger a MapCameraChangedEvent so I thought this would returns the center of the map of the two markers and then set the props accordingly. But maybe I'm approaching this incorrectly - is there a better way?
const [mapCenter, setMapCenter] = useState({ lat: markerOne.lat, lng: markerOne.lng })
const [mapZoom, setMapZoom] = useState(defaultZoom)

  <Map
    center={mapCenter}
    zoom={mapZoom}
    mapId="mapId"
    onCameraChanged={(event) => {
      setMapCenter(event.detail.center)
      setMapZoom(event.detail.zoom)
    }}
  >
    <AdvancedMarker position={{ lat: markerOne.lat, lng: markerOne.lng }} />
    {!!markerTwo && <AdvancedMarker position={{ lat: markerTwo.lat, lng: markerTwo.lng }} /> }
  </Map>

Oh, that might actually be a different issue that could be fixable. The details are a bit difficult to explain, but I think I have an Idea whats wrong there, I'll have a look into this.
What you could try is to use the full CameraState instead of just the zoom and center props, for example:
const INITIAL_CAMERA_STATE = {
  center: {lat: 0, lng: 0},
  zoom: 5,
  heading: 0,
  tilt: 0
};

const MapComponent = () => {
  const [cameraState, setCameraState] = useState(INITIAL_CAMERA_STATE);

  return (
    <Map {...cameraState} onCameraChanged={(ev) => setCameraState(ev.detail)}></Map>
  );
};

If you now want to update the camera-center without touching the zoom (same goes the other way around), you can use the state setter function like this:
const updateCenter = useCallback(newCenter => {
  setCameraState(prevCameraState => {
    return {...prevCameraState, center: newCenter};
  });
}, []);

@usefulthink thank you for your suggestions!
I tried using the full camera state but I came across the same non-draggable issue on the map:
https://github.com/visgl/react-google-maps/assets/33064059/ca356144-d767-48e2-88e9-7e527f3bff7a
So I've gone with your latter suggestion and that's worked - thank you again 🙌

I had this same issue and struggled with it for a couple of days. Using the cameraEventHandler-method did nothing for me and ultimately for me it was  solved by changing
<Map
            className="relative top-0 w-full lg:max-h-full lg:flex-1"
            center={{ lat: 62.898, lng: 27.6782 }}
            zoom={6}
          >

to using

<Map
            className="relative top-0 w-full lg:max-h-full lg:flex-1"
            gestureHandling={'greedy'}
            defaultCenter={{ lat: 62.898, lng: 27.6782 }}
            defaultZoom={6}
          >

So to me it seems that the default-prefixed values are interfering with some of the eventHandler in the library itself.

I know this bug has been describe as "is going to be very hard to fix", but is there an update upon a possible fix ? or a workaround?
I had a workaround in place where ondrag event and onZoomChanged event I resseted the custom zoom and center position that I had previously set, but using center and zoom props, prevent the infowindows autopan functionnality.
So I'm in a situation where I can have the autopan on infowindow opening or the ability to zoom and center the map on a location and be able to drag and zoom the map manually after, but not both features.
That is a dealbreaker for the app we develop and if there is no solution, it would force us to compeltely redo the work.
Thanks

I know this bug has been describe as "is going to be very hard to fix", but is there an update upon a possible fix ? or a workaround?
I had a workaround in place where ondrag event and onZoomChanged event I resseted the custom zoom and center position that I had previously set, but using center and zoom props, prevent the infowindows autopan functionnality.
So I'm in a situation where I can have the autopan on infowindow opening or the ability to zoom and center the map on a location and be able to drag and zoom the map manually after, but not both features.
That is a dealbreaker for the app we develop and if there is no solution, it would force us to compeltely redo the work.
Thanks

Can you share the fix you made for this one? stuck in this for almost one week.

All possible solutions mentioned not working for me:
      <Map
        mapId='shared-widgets'
        zoom={zoom}
        onZoomChanged={onZoomChanged}
        onCameraChanged={handleCameraChange}
        controlSize={20}
        mapTypeId='hybrid'
        zoomControl={true}
        clickableIcons={false}
        disableDefaultUI={true}
        reuseMaps={true}
        defaultCenter={defaultBounds}
        center={defaultBounds}
        gestureHandling='greedy'
        streetViewControl={false}
        keyboardShortcuts={true}
        className={classes.swMapStyle}
      />

const onZoomChanged = (event: MapCameraChangedEvent) => {
const { detail: { zoom } } = event || {};
setState({
zoom,
});
};
const handleCameraChange = (event: MapCameraChangedEvent) => {
const { detail: { center: { lat, lng } } } = event || {};
setState({
defaultBounds: {
lat: lat,
lng: lng,
},
zoom,
});
};

I know this bug has been describe as "is going to be very hard to fix", but is there an update upon a possible fix ? or a workaround?
I had a workaround in place where ondrag event and onZoomChanged event I resseted the custom zoom and center position that I had previously set, but using center and zoom props, prevent the infowindows autopan functionnality.
So I'm in a situation where I can have the autopan on infowindow opening or the ability to zoom and center the map on a location and be able to drag and zoom the map manually after, but not both features.
That is a dealbreaker for the app we develop and if there is no solution, it would force us to compeltely redo the work.
Thanks

Can you share the fix you made for this one? stuck in this for almost one week.

I define the defaultZoom and center props at load with the default position of my map.
Then, when a user click on a card linked to a marker, I set the zoom props to the new zoom I want, and I change the state I use for the center props value, to use the new position.
After those change, if nothing done, I can't move or scroll the map with the mouse anymore.

What I have done to be able to, is to add those to event to the Map component :
I set sone states bfore
/* mapPos is a props of my component */
const [mapCenterPos, setMapCenterPos] = useState({ lat: mapPos.lat, lng: mapPos.lng });
const [mapZooming, setMapZooming] = useState(10);

useEffect(() => {
    setMapCenterPos(center);
  }, [center]);

  useEffect(() => {
    setMapZooming(mapZoom);
  }, [mapZoom]);

<Map
    ...
    defaultZoom={mapZoom}
    center={mapCenterPos}
    zoom={mapZooming}
    onDrag={() => { resetCenter() }}
    onZoomChanged={() => { resetZoom() }}
>...</Map>

and in those event, I reset the state I used to set the maps props :
const resetCenter = () => {
    setMapCenterPos(false);
  }

  const resetZoom = () => {
    setMapZooming(false);
  }

Sorry if I can't sahre all my code, it is compose of multiple components in a big project.
But the fix with the event that I have done, prevent the autopan feature to work as describe here : https://visgl.github.io/react-google-maps/docs/api-reference/components/info-window#infowindow-attached-to-marker
That the issue I still have and still need to fix ASAP

I know this bug has been describe as "is going to be very hard to fix", but is there an update upon a possible fix ? or a workaround?
I had a workaround in place where ondrag event and onZoomChanged event I resseted the custom zoom and center position that I had previously set, but using center and zoom props, prevent the infowindows autopan functionnality.
So I'm in a situation where I can have the autopan on infowindow opening or the ability to zoom and center the map on a location and be able to drag and zoom the map manually after, but not both features.
That is a dealbreaker for the app we develop and if there is no solution, it would force us to compeltely redo the work.
Thanks

Can you share the fix you made for this one? stuck in this for almost one week.

I define the defaultZoom and center props at load with the default position of my map.
Then, when a user click on a card linked to a marker, I set the zoom props to the new zoom I want, and I change the state I use for the center props value, to use the new position.
After those change, if nothing done, I can't move or scroll the map with the mouse anymore.

What I have done to be able to, is to add those to event to the Map component :
I set sone states bfore
/* mapPos is a props of my component */
const [mapCenterPos, setMapCenterPos] = useState({ lat: mapPos.lat, lng: mapPos.lng });
const [mapZooming, setMapZooming] = useState(10);

useEffect(() => {
    setMapCenterPos(center);
  }, [center]);

  useEffect(() => {
    setMapZooming(mapZoom);
  }, [mapZoom]);

<Map
    ...
    defaultZoom={mapZoom}
    center={mapCenterPos}
    zoom={mapZooming}
    onDrag={() => { resetCenter() }}
    onZoomChanged={() => { resetZoom() }}
>...</Map>

and in those event, I reset the state I used to set the maps props :
const resetCenter = () => {
    setMapCenterPos(false);
  }

  const resetZoom = () => {
    setMapZooming(false);
  }

Sorry if I can't sahre all my code, it is compose of multiple components in a big project.
But the fix with the event that I have done, prevent the autopan feature to work as describe here : https://visgl.github.io/react-google-maps/docs/api-reference/components/info-window#infowindow-attached-to-marker
That the issue I still have and still need to fix ASAP

Oh man you are a saviour 🫰

authors: JarmoKamux bdubetink niranjan404 shirleyodeng usefulthink

repo: visgl/react-google-maps


text:
How to update the map after a change in state?

Hello!
I'm testing the library and wanted to add custom Zoom-in Zoom-out buttons, but the map does not update when the zoom values updates.
I created a simple GoogleMap componet like this:
"use client";

import { APIProvider, Map } from "@vis.gl/react-google-maps";

export default function GoogleMap({ zoom }: { readonly zoom: number }) {
  const position = { lat: 53.54, lng: 10 };

  return (
    <APIProvider apiKey={process.env.NEXT_PUBLIC_GOOGLE_MAPS_API_KEY ?? ""}>

        <Map zoom={zoom} center={position} />

    </APIProvider>
  );
}

and then used it on another component like this:
"use client";

import { useState } from "react";
import GoogleMap from "./GoogleMap";

export default function Home() {
  const [zoom, setZoom] = useState(10);
  return (
    <>
      <GoogleMap zoom={zoom} />
      <button
        onClick={() => setZoom(zoom + 1)}
      >
        Zoom in
      </button>
      <button
        onClick={() => setZoom(zoom - 1)}
      >
        Zoom out
      </button>

Zoom: {zoom}

    </>
  );
}

When I change the zoom using the parent compent the child component does not update to reflect the new zoom value.
Here is a test repository: https://github.com/MauricioRobayo/google-maps-test

The fix for this is in the works here: #64. Should be ready to merge later this week.

This should be resolved with https://github.com/visgl/react-google-maps/commit/0b1d800dc5e4b9bf0b1ddb42b9fed392b23b8dae in v0.3. Let me know if you're still seeing problems.

It is working as expected now, thanks @usefulthink !

authors: MauricioRobayo usefulthink


text:
Hover effect

Title of the Pull Request

[x] Have you renamed the PR Title in a meaningful way?

Related Issue

Closes: #
Description

How Has This Been Tested? ⚙

Screenshots 📷

Type of change
What sort of changes have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

[x] My code follows the code style of this project.
[x] I have followed the contribution guidelines
[x] I have performed a self-review of my own code.
[x] I have ensured my changes don't generate any new warnings or errors.
[ ] I have updated the documentation (if necessary).
[x] I have resolved all merge conflicts.

This pull request adds hover effects to the social media buttons in review.html, enhancing the user experience.
I believe this change can be successfully merged into the main branch. Please review the changes and let me know if there are any further adjustments needed.
Thank you!

repo: vishanurag/Canvas-Editor


text:
PC, Surface Plots hard coded to "hot" Color Table

Describe the bug
If you look at the .xml files for Pseudocolor and Surface plots, they both specify hot as the the colorTableName attribute. This makes the default setting for these plot types to be a specific color table name instead of the proxy, Default and prevents these plots from, by default, obeying the default color table setting.
They should say Default. It looks like most other plots do.

@biagas / @cyrush do you see any downside to my just changing the .xml files to use Default instead of hot for colorTableName member and re-gening the plot classes?
VisIt's overall default color table is indeed also hot. However, for any user who has changed the overall default color table name(s), then this update would cause their default behavior for PC and Surface plots to change from hot to whatever their overall default color table is. But, I think this is low likelihood.

sounds like the right change to me

+1

authors: biagas cyrush markcmiller86

repo: visit-dav/visit


text:
fix crash

Description
Resolves #18725
I could have done a better job understanding why the code got into the state it did. But, the code blocks involved are more complex than I had time to fully understand. So, I've applied a fix that corrects the crash without understanding root cause.
Type of change

[x] Bug fix~~
[ ] New feature
[ ] Documentation update
[ ] Other

How Has This Been Tested?

Reminders:

Please follow the style guidelines of this project.
Please perform a self-review of your code before submitting a PR and asking others to review it.
Please assign reviewers (see VisIt's PR procedures for more information).

Checklist:

[x] I have commented my code where applicable.~~
[x] I have updated the release notes.~~
[ ] I have made corresponding changes to the documentation.
[ ] I have added debugging support to my changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have confirmed new and existing unit tests pass locally with my changes.
[ ] I have added new baselines for any new tests to the repo.
[x] I have NOT made any changes to protocol or public interfaces in an RC branch.~~

Thanks for the quick fix!


text:
"Invalid Component definition" when using Laravel Mix and

I keep running into the error "Invalid Component definition".
All the solutions I can find refer to removing "svg" from a test.
I'm using Laravel Mix https://github.com/JeffreyWay/laravel-mix/issues/350 but it suggested that svg's where removed from the test 2 years ago and shouldn't be interfering.
My SVG's also include <style> tags which may also be causing an issue, but I can't find anyway of debugging to check.
Here's what my webpack.mix.js looks like at the moment.
mix.webpackConfig({
    resolve: {
        extensions: ['.js', '.vue', '.json'],
        alias: {
            '@': __dirname + '/resources/assets/js'
        },
    },
    module: {
        rules: [
            {
                test: /\.svg$/,
                loader: 'vue-svg-loader',
            },
        ],
    }
})

mix
    .js('resources/assets/js/app.js', 'public/js/bundle.js')
    .sass('resources/assets/sass/app.scss', 'public/css/bundle.css')
    .version()
    .sourceMaps(true)

Here is the SVG:
<svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 87.67 68.52"><defs><style>.cls-1{fill:#fff;}.cls-1,.cls-2,.cls-4{fill-rule:evenodd;}.cls-2{fill:red;}.cls-3{mask:url(#mask);}.cls-4{fill:lime;}.cls-5{mask:url(#mask-2-2);}</style><mask id="mask" x="0" y="0" width="86.33" height="68.52" maskUnits="userSpaceOnUse"><g transform="translate(-19.91 -26)"><g id="mask-2"><path id="path-1" class="cls-1" d="M30,29.48A154.83,154.83,0,0,1,62.75,26a180.57,180.57,0,0,1,34,3.31h0a1,1,0,0,1,.81.91c.16,2.49.29,4.06.38,4.71q6.15,44.33,6.68,47.79a50.47,50.47,0,0,0,1.61,7.12,58.73,58.73,0,0,1-18.79,4.55,59.27,59.27,0,0,1-19.34-2L64,73.68,60.12,92.41a49.56,49.56,0,0,1-17.91,2A67.75,67.75,0,0,1,23,89.84,63.6,63.6,0,0,0,24.46,82q.38-3.35,4.54-48.07c0-.44.1-1.62.18-3.52h0A1,1,0,0,1,30,29.48Z"/></g></g></mask><mask id="mask-2-2" x="3.09" y="0" width="84.58" height="68.52" maskUnits="userSpaceOnUse"><g transform="translate(-19.91 -26)"><g id="mask-2-3" data-name="mask-2"><path id="path-1-2" data-name="path-1" class="cls-1" d="M30,29.48A154.83,154.83,0,0,1,62.75,26a180.57,180.57,0,0,1,34,3.31h0a1,1,0,0,1,.81.91c.16,2.49.29,4.06.38,4.71q6.15,44.33,6.68,47.79a50.47,50.47,0,0,0,1.61,7.12,58.73,58.73,0,0,1-18.79,4.55,59.27,59.27,0,0,1-19.34-2L64,73.68,60.12,92.41a49.56,49.56,0,0,1-17.91,2A67.75,67.75,0,0,1,23,89.84,63.6,63.6,0,0,0,24.46,82q.38-3.35,4.54-48.07c0-.44.1-1.62.18-3.52h0A1,1,0,0,1,30,29.48Z"/></g></g></mask></defs><title>2</title><g id="Page-1"><g id="Path-Copy-2"><path class="cls-2" d="M30,29.48A154.83,154.83,0,0,1,62.75,26a180.57,180.57,0,0,1,34,3.31h0a1,1,0,0,1,.81.91c.16,2.49.29,4.06.38,4.71q6.15,44.33,6.68,47.79a50.47,50.47,0,0,0,1.61,7.12,58.73,58.73,0,0,1-18.79,4.55,59.27,59.27,0,0,1-19.34-2L64,73.68,60.12,92.41a49.56,49.56,0,0,1-17.91,2A67.75,67.75,0,0,1,23,89.84,63.6,63.6,0,0,0,24.46,82q.38-3.35,4.54-48.07c0-.44.1-1.62.18-3.52h0A1,1,0,0,1,30,29.48Z" transform="translate(-19.91 -26)"/></g><g class="cls-3"><polygon id="Path-9" class="cls-4" points="8.12 66.72 13.58 10.16 13.58 1.06 7.24 4.05 0 64.27 8.12 66.72"/></g><g class="cls-5"><polygon id="Path-9-Copy" class="cls-4" points="82.12 66.75 74.09 10.1 74.09 1 80.43 4 87.67 64.22 82.12 66.75"/></g></g></svg>

Here is the generated component:

      export default {
        functional: true,
        render(_h, _vm) {
          const { _c, _v, data, children = [] } = _vm;

          const {
            class: classNames,
            staticClass,
            style,
            staticStyle,
            attrs = {},
            ...rest
          } = data;

          return _c(
            'svg',
            {
              class: [classNames,staticClass],
              style: [style,staticStyle],
              attrs: Object.assign({"id":"Layer_1","data-name":"Layer 1","xmlns":"http://www.w3.org/2000/svg","viewBox":"0 0 87.67 68.52"}, attrs),
              ...rest,
            },
            children.concat([_c('defs',[_c('mask',{attrs:{"id":"mask","x":"0","y":"0","width":"86.33","height":"68.52","maskUnits":"userSpaceOnUse"}},[_c('g',{attrs:{"transform":"translate(-19.91 -26)"}},[_c('g',{attrs:{"id":"mask-2"}},[_c('path',{staticClass:"cls-1",attrs:{"id":"path-1","d":"M30 29.48A154.83 154.83 0 0 1 62.75 26a180.57 180.57 0 0 1 34 3.31 1 1 0 0 1 .81.91c.16 2.49.29 4.06.38 4.71q6.15 44.33 6.68 47.79a50.47 50.47 0 0 0 1.61 7.12 58.73 58.73 0 0 1-18.79 4.55 59.27 59.27 0 0 1-19.34-2L64 73.68l-3.88 18.73a49.56 49.56 0 0 1-17.91 2A67.75 67.75 0 0 1 23 89.84 63.6 63.6 0 0 0 24.46 82q.38-3.35 4.54-48.07c0-.44.1-1.62.18-3.52a1 1 0 0 1 .82-.93z"}})])])]),_c('mask',{attrs:{"id":"mask-2-2","x":"3.09","y":"0","width":"84.58","height":"68.52","maskUnits":"userSpaceOnUse"}},[_c('g',{attrs:{"transform":"translate(-19.91 -26)"}},[_c('g',{attrs:{"id":"mask-2-3","data-name":"mask-2"}},[_c('path',{staticClass:"cls-1",attrs:{"id":"path-1-2","data-name":"path-1","d":"M30 29.48A154.83 154.83 0 0 1 62.75 26a180.57 180.57 0 0 1 34 3.31 1 1 0 0 1 .81.91c.16 2.49.29 4.06.38 4.71q6.15 44.33 6.68 47.79a50.47 50.47 0 0 0 1.61 7.12 58.73 58.73 0 0 1-18.79 4.55 59.27 59.27 0 0 1-19.34-2L64 73.68l-3.88 18.73a49.56 49.56 0 0 1-17.91 2A67.75 67.75 0 0 1 23 89.84 63.6 63.6 0 0 0 24.46 82q.38-3.35 4.54-48.07c0-.44.1-1.62.18-3.52a1 1 0 0 1 .82-.93z"}})])])])]),_c('g',{attrs:{"id":"Page-1"}},[_c('path',{attrs:{"d":"M30 29.48A154.83 154.83 0 0 1 62.75 26a180.57 180.57 0 0 1 34 3.31 1 1 0 0 1 .81.91c.16 2.49.29 4.06.38 4.71q6.15 44.33 6.68 47.79a50.47 50.47 0 0 0 1.61 7.12 58.73 58.73 0 0 1-18.79 4.55 59.27 59.27 0 0 1-19.34-2L64 73.68l-3.88 18.73a49.56 49.56 0 0 1-17.91 2A67.75 67.75 0 0 1 23 89.84 63.6 63.6 0 0 0 24.46 82q.38-3.35 4.54-48.07c0-.44.1-1.62.18-3.52a1 1 0 0 1 .82-.93z","transform":"translate(-19.91 -26)","fill":"red","fill-rule":"evenodd","id":"Path-Copy-2"}}),_c('g',{attrs:{"mask":"url(#mask)"}},[_c('path',{staticClass:"cls-4",attrs:{"id":"Path-9","d":"M8.12 66.72l5.46-56.56v-9.1L7.24 4.05 0 64.27l8.12 2.45z"}})]),_c('g',{attrs:{"mask":"url(#mask-2-2)"}},[_c('path',{staticClass:"cls-4",attrs:{"id":"Path-9-Copy","d":"M82.12 66.75L74.09 10.1V1l6.34 3 7.24 60.22-5.55 2.53z"}})])])])
          )
        }
      }
    ```

Could you try updating to the new version?

authors: robjbrain visualfanatic

repo: visualfanatic/vue-svg-loader


text:
Vit stuck on "loading..."

Hello there,
My vit stopped working and just shows "Loading..."

vit --help   =>  works
vit {string}    => works but shows only tasks with {string} in the title.

There are no errors anywhere.
What I tried and failed:

reinstalling
downloading the code from here and installing it  on a clean virtualenv
check if taskwarrior was broken (Removed plugins etc)
changing the default report on config.ini

If I ctrl-c vit I get this:
Traceback (most recent call last):
  File "/usr/bin/vit", line 33, in <module>
    sys.exit(load_entry_point('vit==2.0.0', 'console_scripts', 'vit')())
  File "/usr/lib/python3.9/site-packages/vit/command_line.py", line 5, in main
    Application(options, filters)
  File "/usr/lib/python3.9/site-packages/vit/application.py", line 75, in __init__
    self.loop.run()
  File "/usr/lib/python3.9/site-packages/urwid/main_loop.py", line 287, in run
    self._run()
  File "/usr/lib/python3.9/site-packages/urwid/main_loop.py", line 385, in _run
    self.event_loop.run()
  File "/usr/lib/python3.9/site-packages/urwid/main_loop.py", line 790, in run
    self._loop()
  File "/usr/lib/python3.9/site-packages/urwid/main_loop.py", line 814, in _loop
    ready, w, err = select.select(fds, [], fds)
KeyboardInterrupt

I'd appreciate any pointers to fix the issue.
Vit is such an important part of my work!
Thanks in advance,
RQ
PS: I did update to python3.9 last week but the issue only appeared last Friday and there are no issues or errors regarding python.

It sounds like there is one task in particular that is causing issues. To figure out what that task is:

First, backup everything.
Then, start "bisecting" your pending.data file to figure out which line causes the problem.
Then anonymize that line and post it here.

Let me know if (2) is confusing and I can give more details.

Thank you @scottkosty !
I didn't know a rogue task could brake vit!
I found and deleted the evil task on pending.data and I have my beloved vit back.
the task in question:
[annotation_1607673381:"autonote" description:"contact owner regarding blue the parrot" entry:"1607673181" modified:"1607680812"  project:"" status:"pending" tags:"tg,next" uuid:"a81b3ec1-0d89-4888-86b3-cf741ac0f67c"]
It can't be seen above but project has these characters:  "^[^["
I imagine that was the problem. Now, I have no idea how those got there.
Thanks again,
RQ

authors: redquixote scottkosty

repo: vit-project/vit


text:
fixing console errors for number input fields

Was getting a JS console error when calling setSelectionRange:
"Uncaught InvalidStateError: Failed to execute 'setSelectionRange' on 'HTMLInputElement': The input element's type ('number') does not support selection."

+1. I'm encountering this issue too.  What is the likelihood of this pull request being merged?

+1.  As far as I know this hasn't been affecting any input field functionality however it would be nice to see this issue fixed.

@Thomas101  I like your solution of 'try' better than specifically excluding number and email types since these are still supported in IE and FF and other places. Thanks! Putting this fix into dev.

authors: TheCrow1213 randydinh rjsmith tofutim

repo: vitalets/x-editable


text:
Couldn't Install Package because of Typescript Version

Describe the bug
npm install ajv-ts didn't succeed.
npm install ajv-ts
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: hyperbola-investor@undefined
npm ERR! Found: typescript@5.3.3
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"^5.1.6" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@"5.0.0" from ajv-ts@0.3.1
npm ERR! node_modules/ajv-ts
npm ERR!   ajv-ts@"*" from the root project

To Reproduce
Steps to reproduce the behavior:

Install latest Remix application
Run npm install ajv-ts
Notice above error

Expected behavior
Installation should work, shouldn't depend on a single version of Typescript?
Desktop (please complete the following information):

JS runtime : NodeJS

As a workaround, I can recommend installing with --force flag until fixed.

authors: rjvim vitalics

repo: vitalics/ajv-ts


text:
Version 1.19 still not working on Android 8

Version 1.1.9 not working on OnePlus 5 with Android 8. Scan didn't discover any beacon.
Version 1.1.8 not working on OnePlus 5 with Android 8. Scan didn't discover any beacon.
Version 1.1.1: Scan discover the beacon, but didn't execute any action.

Same issue on my Galaxy S8 Android 8

Same issue on Galaxy S8+

Also PIxel XL. Latest Play Store version.

Same for me on Pixel XL 2
Is this an easy fix?

New version is now working!

authors: aioue hvddrift maykar okatzer66 vincentBesseau

repo: vitas/beaconloc


text:
Correct full name of TD3

I corrected a simple typo in README.md where TD3 was written as Twin Dueling Deep Deterministic Policy Gradient. I believe it should be Twin Delayed Deep Deterministic Policy Gradient.

Thank you!

authors: seungjaeryanlee vitchyr

repo: vitchyr/rlkit


text:
fix: make it work when a default lang is specified

Description
<template lang="html">

foo

</script>

and

didn't work.
This PR fixes these.
requires https://github.com/vuejs/core/issues/7388
fixes https://github.com/vitejs/vite-plugin-vue/issues/17
Additional context

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

This PR is a bit low priority for me. Feel free to rebase this PR. I'd be happy to review it.

Rebased on https://github.com/vitejs/vite-plugin-vue/pull/223 :)

authors: dargmuesli sapphi-red

repo: vitejs/vite-plugin-vue


text:
【优化建议】关于使用Vite构建多页面应用时,构建产物丢失页面JS文件的问题建议

Description
遇到的问题
一个偶然的机会，我在开发一个使用Vite搭建的多页面应用项目时，使用了下面这样的配置：
export default defineConfig({
  build: {
    rollupOptions: {
      input: {
        index: 'index.html',
        'pageA/index': 'src/pages/pageA/index.html',
        'pageB/index': 'src/pages/pageB/index.html',
      }
    }
  }
})

(为了说明问题，我简化了不必要的配置项)
该项目使用vite server 命令运行时，一切正常，页面表现也如预期。
而当我使用vite buiild 命令构建时，构建过程正常， 但构建产物中的*/index.html等文件，丢失了本应该有的 script type='module' js文件引入， 而这些js文件实际已经被构建到dist/asset目录下。
经过几个小时的各种测试与分析，最终发现，正确的配置应当如下：
正确配置
import nodePath from 'node:path'

export default defineConfig({
  build: {
    rollupOptions: {
      input: {
        index: 'index.html',
        'pageA/index': nodePath.resolve(__dirname, 'src/pages/pageA/index.html'),
        'pageB/index': nodePath.resolve(__dirname, 'src/pages/pageB/index.html')
      }
    }
  }
})

结论
我认为这并非vitejs的一个bug，但是vitejs这么受前端开发者喜爱的工具，是否可以考虑对此进行一些有益的改进与优化？这应当会给vite的初学者解决掉一个难解的困惑， 也会让vite更符合文档中宣称的："这确保了与开发服务器的工作方式保持一致的结构。".
非常感谢！
Suggested solution
[建议]
建议在 vite build命令中，对于多页面应用(mpa)，对于使用了相对路径作为入口文件的配置，给予必要的控制台警告或者 强制报错。
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

### Tasks

Duplicate of #15992

Duplicate of #15992

感谢答复！
我仔细阅读了#15992以及相关的issue，并在更新vite版本到v5.2.11 之后，确认该问题已经被修复了！。
不过，我建议官方能在文档上进行一些必要说明，以避免一些未能及时更新新版vite的项目出现错误。

authors: sapphi-red windylaugit

repo: vitejs/vite


text:
Add option to disable '[vite] page realoaded.' console spam

Is your feature request related to a problem? Please describe.
I am always frustrated when with each keystroke I get a newline in my terminal.
Describe the solution you'd like
WAIT/DONE statuses as in 'yarn serve' with vue cli would do the job.
Describe alternatives you've considered
Minimize terminal, open browsers inspect, user '14 [vite] /src/App.vue template updated.' line for feedback.
Additional context
I'd love to see ' Dev server running at:' in light blue as an indication that things a running well, so just having an option to disable https://github.com/vitejs/vite/blob/5cdbc46dbdb0791f4968120a5d66c2e5537347ab/src/node/server/serverPluginHmr.ts#L178 this line should do the job.
P.S. Thanks for building vite!

Could consider changing this to console.debug which is hidden by default, add verbose in the log levels to see them show up.

Yeah we can probably make the terminal output just similar to Vue CLI.

Sorry for confusing. I meant the terminal output as an issue and browsers console as workaround I use now(no complains on current browser console output from me). Not sure if the same command I refered to prints to browsers console as well as terminal.
Yes, agreed, just copying Vue CLI's behaviour, if that's possible, seems like a way to go. Understand it's not a top priority considering project's experimental status, but felt like sharing the feedback.
Again - thanks for creating vue&vite!

Fixed in 2.0.

Fixed in 2.0.

authors: Jackbennett toinbis yyx990803


text:
Unable to build production build with relative links

Describe the bug
Currently, no matter what I do, Vite builds and outputs something like:
<script  type="module" crossorigin src="/assets/index.123456.js"></script>
<link rel="modulepreload" href="/assets/vendor.123456.js">
<link rel="stylesheet" href="/assets/index.123456.css">

The problem is the environment I deploy to routes to my app, meaning the origin root is not my app's root. (e.g. https://some-origin-here/my-app is the application root), as such all links to /assets/* are pointing to the wrong thing. it would be ideal (and way more portable) if the build defaulted to relative URLs.
I'm unable to find documentation outlining how I would build and output relative URLs.
Reproduction
This seems to be true of any Vite build app.
System Info
@vitejs/plugin-react@1.0.5
vite@2.6.13

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

For now, as a workaround, I'm just transforming the links with a node script doing a string replace. LMAO... it's not ideal.

How about base ?
It might work.

That's it. Thank you to you and to @yyx990803 for pointing me this way.

authors: benlesh stygian-desolator


text:
WebSocket connection can not work inside Docker container

Do NOT ignore this template or your issue will have a very high chance to be closed without comment.

Describe the bug
I use Docker container to develop a Vite app.
I use the default port 3000 for app, and expose 8080 from Docker container.
Normally I can open the app inside Docker container from host machine's browser with 127.0.0.1:8080.
The index.html page shown correctly, but the console of browser throw an error of WebSocket connection and infinitely refresh page:

[vite] connecting...
VM1722 vue.js:8446 You are running a development build of Vue.
Make sure to use the production build (*.prod.js) when deploying for production.
VM1719 client:25 WebSocket connection to 'ws://127.0.0.1:3000/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
(匿名) @ VM1719 client:25
VM1719 client:125 [vite] server connection lost. polling for restart...

The WebSocket connection port is the same as default port(or port set in vite.config.ts), and didn't use the port 8080.

Reproduction
Create a app inside a Docker container, expose a different port from Vite config, run.
After search in Vite's code, I find the WebSocket port is set in https://github.com/vitejs/vite/blob/master/src/client/client.ts#L35 and comes from the config file vite.config.ts.
To make it work, I modified the node_modules/vite/dist/client/client.js#L23, manually set the expose port 8080 and it works. The error gone.
I think the problem is caused by the script run in client, it get port from config in app, and can't get the port in browser.
If we could add a config item socketPort or is there a method to automatically get the right port in browser?
Many Thanks!
System Info

required vite version: 1.0.0-rc.4
required Operating System: debian 10 with Docker image node:12.18.3-alpine
required Node version: 12.18.3
Optional:

npm/yarn version: 1.22.0
Installed vue version (from yarn.lock or package-lock.json): vue@^3.0.0-rc.5
Installed @vue/compiler-sfc version: vue@^3.0.0-rc.5

Logs (Optional if provided reproduction)

Run vite or vite build with the --debug flag.
Provide the error log here.

Hi @angela-1 and @underfin ,
I am having issues setting up a basic vite project in docker. I documented the steps in this repo and readme.
This was the only docker-related issue I found in Vite gh and it seems like you got further than me. I tried looking in your latest vue project but didn't see any docker files. Do either of you have a basic config that works that you can share?
Thanks,
Carlos

@shortpoet
The issues from a privite project, and I have uploaded a new public project to show the structure.
You can see https://github.com/angela-1/azalea
You should read the README.md to make it work.

Wow, that is awesome! Thank you very much Angela!! 😊 千万谢谢你!!

@shortpoet
The issues from a privite project, and I have uploaded a new public project to show the structure.
You can see https://github.com/angela-1/azalea
You should read the README.md to make it work.

thanks, guy

Hey any news on merging this issue ? Would love to use vite on github codespace.

authors: angela-1 cpietsch shortpoet wozien


text:
Vite 3 - isProduction flipped to true in dev server after a production build

Describe the bug
Our CI spins up a Vite dev server after running a production build. For some reason, plugins receive isProduction: true in their resolvedConfig, even when mode: 'development' is explicitly set in the dev server's inline config.
Reproduction
https://stackblitz.com/edit/github-u7wgc4?file=package.json
System Info
System:
    OS: macOS 12.2
    CPU: (8) x64 Apple M1 Pro
    Memory: 41.20 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.18.1 - ~/.volta/tools/image/node/14.18.1/bin/node
    Yarn: 1.22.17 - ~/.volta/tools/image/yarn/1.22.17/bin/yarn
    npm: 8.4.0 - ~/.volta/tools/image/npm/8.4.0/bin/npm
  Browsers:
    Chrome: 103.0.5060.114
    Firefox: 102.0.1
    Safari: 15.3
  npmPackages:
    vite: 3.0.0-beta.10 => 3.0.0-beta.10

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hmm, this seems to be caused by the NODE_ENV being hard-set to production when running build, setting this persists across runs. 😅 I guess a fix would be to reset it post-build to the original value or account for mode: dev explicitly

https://github.com/vitejs/vite/blob/f020066e476c33f100a1881578c9dda051929dd1/packages/vite/src/node/config.ts#L361
https://github.com/vitejs/vite/blob/f020066e476c33f100a1881578c9dda051929dd1/packages/vite/src/node/config.ts#L480

@JoviDeCroock Worked out a PR with patak here! #9058
Seeing some nasty test runner issues though. Not sure what's going on there

authors: JoviDeCroock bholmesdev


text:
use reporter in ci as default reporter

Clear and concise description of the problem
config.test.reporters has many available options but non of them is same with current reporter in ci.
I really like the reporter in CI and it it possible to set it as default reporter instead of setting env CI=true?
Suggested solution
add an reporter default-ci or some similar name
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

In a similar vein, verbose with CI=true is also good. Especially as a potential "workaround" for #2602

Confirmed that the CI reporter is not subject to the degraded performance of other console reporters.
Thanks! Will use that for my use case now

authors: adam-arthur alok-runner trim21

repo: vitest-dev/vitest


text:
not matching snapshot affects console.log functionality when mocked

Describe the bug
When snapshot don't match (inline or file), console stop working. I am using a mock replacement for one test to document/show debug mode of my implementation. I don't want to use spy as I don't want to have polluted test runner console.
I know that this seems to be edge case, but anyway, it should not be affected 😬
Reproduction
Working code:

     function someMethod(options?: { debug: boolean }) {
        if (options?.debug) console.log('some debug info');
      }
      it('has debug mode issue', () => {
        const logMethod = console.log.bind(console);
        console.log = vi.fn();

        // calling method without debug mode
        someMethod();

        // no debug info yet as debug is false by default
        expect((console.log as Mock).mock.calls).toMatchInlineSnapshot('[]');

        // calling method with debug mode
        someMethod({ debug: true });

        expect((console.log as Mock).mock.calls).toMatchInlineSnapshot(`
        [
          [
            "some debug info",
          ],
        ]
      `);

        console.log = logMethod; // set back original method
      });

      function otherMethod() {
        console.log('some temporary console.log debug info');
      }
      it('has debug mode issue other', () => {
        expect(otherMethod()).toBeUndefined();
      });

It will log 'some temporary console.log debug info' into test runner console. Which is correct.. it used for debugging code.
but now try to change 'some debug info' in if (options?.debug) console.log('some debug info'); so snapshots don't match now.. 'some temporary console.log debug info' is not logged anymore, preventing code to be debugged via console logs while snapshot does not match
System Info
System:
    OS: macOS 12.6.8
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 32.83 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm
  Browsers:
    Chrome: 118.0.5993.117
    Firefox: 116.0.3
    Safari: 16.6
  npmPackages:
    @vitejs/plugin-vue: ^4.0.0 => 4.0.0
    @vitest/coverage-c8: ^0.28.1 => 0.28.1
    @vitest/coverage-v8: ^0.32.2 => 0.32.2
    vite: ^4.0.0 => 4.0.4
    vitest: ^0.34.6 => 0.34.6

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Voila https://stackblitz.com/edit/vitest-dev-vitest-jftnew?file=test%2Fsuite.test.ts thanks 🙏

This is expected behavior. expect throws an error, so code after it is not executed. You need to better structure your tests: you can restore console.log in afterEach hook or use vi.spyOn instead and enable test.restoreMocks in config file.

authors: luckylooke sheremet-va


text:
dark and light mode switch on docs

Clear and concise description of the problem
Thanks for working on vitest. users including me don't use dark and light mode always we switch every now and then. It would be great if there was a way to switch between themes.
Suggested solution
It would be great if there was a button to switch between light and dark themes on docs
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

There is ongoing work to create a new theme for VitePress, that will support light/dark mode. We are waiting for it to be ready. If someone wants to create a temporal switcher (maybe we need to wait one or two months), we could add it until the official theme is out

Implemented

authors: patak-dev sheremet-va veritem


text:
feat: add api options

Maybe we can only enable it when from cli?

upps, I need to add it to the docs...

upps, I need to add it to the docs...

I think that --host should be top-level in the CLI, but in the config, we should have all the API server options under an entry (like in vite server and preview). You can check available options here: CommonServerOptions. I think a good way to define this is to make api: boolean | CommonServerOptions. api: true being the same as api: {}

I think that --host should be top-level in the CLI, but in the config, we should have all the API server options under an entry (like in vite server and preview). You can check available options here: CommonServerOptions. I think a good way to define this is to make api: boolean | CommonServerOptions. api: true being the same as api: {}

You could implement all the options in this PR if you want, or only host, as you wish 👍🏼

You could implement all the options in this PR if you want, or only host, as you wish 👍🏼

You could implement all the options in this PR if you want, or only host, as you wish 👍🏼

Shoul we omit open and proxy?

You could implement all the options in this PR if you want, or only host, as you wish 👍🏼

Shoul we omit open and proxy?

Yes, lets omit both 👍🏼

Yes, lets omit both 👍🏼

Yes, lets omit both 👍🏼

I'll remove the open option from the inline options and remove from the omit on the type. I'll also remove https from the new guy: ApiConfig.
Maybe we can rename api to ui, I know it is a breaking change, but we're yet on on beta and all entries for the ui are on WIP.

Yes, lets omit both 👍🏼

I'll remove the open option from the inline options and remove from the omit on the type. I'll also remove https from the new guy: ApiConfig.
Maybe we can rename api to ui, I know it is a breaking change, but we're yet on on beta and all entries for the ui are on WIP.

ui refers to the browser app, but the api is going to be used for other tools too. We dont need a rename

ui refers to the browser app, but the api is going to be used for other tools too. We dont need a rename

@patak-dev so change addresses on jsdocs and on docs?

@patak-dev so change addresses on jsdocs and on docs?

@userquin updated the code so the CLI handling doesn't leak into the config, and removed <host> in the CLI because --host without a value should be a valid option. Could you check this is still working as you expect?
I think we could merge, and in a future PR we may want to show in the console the server addresses if --api is passed to the API

wtf, windows memory error is back:
F:\work\projects\quini\GitHub\antfu\vitest-main>vitest -o --global --api

 WATCH  F:/work/projects/quini/GitHub/antfu/vitest-main

e/test/mocked-no-mocks-same.test.ts (1)

node:internal/process/promises:246
          triggerUncaughtException(err, true /* fromPromise */);
          ^
 6: 00007FF7A9E22C87 uv_timer_stop+1207
 7: 00007FF7A9E1F25B uv_async_send+331
 8: 00007FF7A9E1E9EC uv_loop_init+1292
 9: 00007FF7A9E1EB8A uv_run+202
10: 00007FF7A9DEDC95 node::SpinEventLoop+309
11: 00007FF7A9C88660 v8::internal::wasm::SignatureMap::Freeze+35776
12: 00007FF7A9C83CB8 v8::internal::wasm::SignatureMap::Freeze+16920
13: 00007FF7A9E0F36D uv_poll_stop+557
14: 00007FF7AAC20C60 v8::internal::compiler::RepresentationChanger::Uint32OverflowOperatorFor+146416
15: 00007FFFAA587034 BaseThreadInitThunk+20
16: 00007FFFABCE2651 RtlUserThreadStart+33

@sheremet-va @patak-dev how about the docs?.
With the new options we can use it like this:

vitest -o --api
vitest -o --api 3001
vitest -o --api --port 3001
vitest -o --api.port 3001
vitest -o --api --host 192.168.1.37
vitest -o --api.host 192.168.1.37
vitest -o --api.port 3001 --api.host 192.168.1.37

Now that we have
vitest -o --api.port 3001
vitest -o --api.host 192.168.1.37
vitest -o --api.port 3001 --api.host 192.168.1.37

I think that we no longer need
vitest -o --api --port 3001
vitest -o --api --host 192.168.1.37
vitest -o --api 3001 --host 192.168.1.37
vitest -o --api --port 3001 --host 192.168.1.37

So we can simplify the cli handling and remove interpretCliApiConfig as @sheremet-va was proposing, no?

@patak-dev what about vitest -o --api? we're removing this guy forcing the user to provide the port.

@patak-dev now vitest -o --api also works for default port

authors: patak-dev userquin


text:
Problems with w2field of type 'select' (w2ui 1.5)

First issue:
The field can not be used as stand-alone. This may be related to #1225
It can however be used inside a w2form.
Second issue:
Rendering a w2field of type 'select' in a w2form looks really bad in Internet Explorer (tested with IE 11.0.9).
No issues in Chrome and Firefox.
Both problems can be seen in this fiddle: https://jsfiddle.net/hn9qzs8a/
This is how it looks in IE:

This is how it looks in Chrome:

@mpf82, can you please send me your email address to vitamlina@gmail.com

I've sent you an email to the adress on your github profile - the one you just posted seems to have a typo.
Cheers :)

Updated fiddle: https://jsfiddle.net/gjkd0a39/ - fiddle works with w2ui 2.0, issue still exists.
Noone is using IE anymore, so I guess the second issue can be ignored. Select field looks fine in Edge.

Closing this issue, since simply not all field types that are available in a w2form are available as w2field.


text:
post_create_commands prevent autoscaler from working

Hey,
I have an existing cluster on Hetzner and wanted to use a gateway / NAT server to have a fixed IP that I can whitelist in third party services (e.g. databases).
Followed this Hetzner community tutorial.
Original config (autoscaling works fine):
hetzner_token: ...
cluster_name: x-dev
kubeconfig_path: "..."
k3s_version: v1.30.3+k3s1
public_ssh_key_path: "..."
private_ssh_key_path: "..."
use_ssh_agent: false
ssh_allowed_networks:
  - 0.0.0.0/0
api_allowed_networks:
  - 0.0.0.0/0
private_network_subnet: 10.0.0.0/16
schedule_workloads_on_masters: false
masters_pool:
  instance_type: cpx21
  instance_count: 1
  location: nbg1
worker_node_pools:
  - name: autoscaled-cpx41
    instance_type: cpx41
    instance_count: 2
    location: nbg1
    autoscaling:
      enabled: true
      min_instances: 0
      max_instances: 5

New config (autoscaling stops working correctly):
hetzner_token: ...
cluster_name: x-dev
kubeconfig_path: "..."
k3s_version: v1.30.3+k3s1
public_ssh_key_path: "..."
private_ssh_key_path: "..."
use_ssh_agent: false
ssh_allowed_networks:
  - 0.0.0.0/0
api_allowed_networks:
  - 0.0.0.0/0
private_network_subnet: 10.0.0.0/16
schedule_workloads_on_masters: false
additional_packages:
  - ifupdown
post_create_commands:
  - apt update
  - apt upgrade -y
  - apt autoremove -y
  - |
    cat <<'EOF' >> /etc/systemd/network/10-ens10.network
    [Match]
    Name=ens10

    [Network]
    DHCP=yes
    Gateway=10.0.0.1
    EOF

masters_pool:
  instance_type: cpx21
  instance_count: 1
  location: nbg1

worker_node_pools:
  - name: autoscaled-cpx41
    instance_type: cpx41
    instance_count: 2
    location: nbg1
    autoscaling:
      enabled: true
      min_instances: 0
      max_instances: 5

Output:
Validating configuration......configuration seems valid.

=== Creating infrastructure resources ===
Network already exists, skipping.
Updating firewall...done.
SSH key already exists, skipping.
Placement group x-dev-masters already exists, skipping.
Server x-dev-cpx21-master1 already exists, skipping.
Server x-dev-cpx21-master1 already exists, skipping.
Waiting for successful ssh connectivity with server x-dev-cpx21-master1...
...server x-dev-cpx21-master1 is now up.

=== Setting up Kubernetes ===
Deploying k3s to first master x-dev-cpx21-master1...
[INFO]  Using v1.30.3+k3s1 as release
[INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.30.3+k3s1/sha256sum-amd64.txt
[INFO]  Skipping binary downloaded, installed k3s matches hash
[INFO]  Skipping installation of SELinux RPM
[INFO]  Skipping /usr/local/bin/kubectl symlink to k3s, already exists
[INFO]  Skipping /usr/local/bin/crictl symlink to k3s, already exists
[INFO]  Skipping /usr/local/bin/ctr symlink to k3s, already exists
[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[INFO]  Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[INFO]  env: Creating environment file /etc/systemd/system/k3s.service.env
[INFO]  systemd: Creating service file /etc/systemd/system/k3s.service
[INFO]  systemd: Enabling k3s unit
[INFO]  No change detected so skipping service start
Waiting for the control plane to be ready...
Saving the kubeconfig file to ...
...k3s has been deployed to first master x-dev-cpx21-master1 and the control plane is up.

=== Deploying Hetzner drivers ===

Creating secret for Hetzner Cloud token...
secret/hcloud configured
...secret created.

Deploying Hetzner Cloud Controller Manager...
serviceaccount/hcloud-cloud-controller-manager unchanged
clusterrolebinding.rbac.authorization.k8s.io/system:hcloud-cloud-controller-manager unchanged
deployment.apps/hcloud-cloud-controller-manager unchanged
...Cloud Controller Manager deployed

Deploying Hetzner CSI Driver...
serviceaccount/hcloud-csi-controller unchanged
storageclass.storage.k8s.io/hcloud-volumes unchanged
clusterrole.rbac.authorization.k8s.io/hcloud-csi-controller unchanged
clusterrolebinding.rbac.authorization.k8s.io/hcloud-csi-controller unchanged
service/hcloud-csi-controller-metrics unchanged
service/hcloud-csi-node-metrics unchanged
daemonset.apps/hcloud-csi-node configured
deployment.apps/hcloud-csi-controller configured
csidriver.storage.k8s.io/csi.hetzner.cloud unchanged
...CSI Driver deployed

Deploying k3s System Upgrade Controller...
namespace/system-upgrade unchanged
serviceaccount/system-upgrade unchanged
configmap/default-controller-env unchanged
deployment.apps/system-upgrade-controller unchanged
...k3s System Upgrade Controller deployed.

Deploying Cluster Autoscaler...
serviceaccount/cluster-autoscaler unchanged
clusterrole.rbac.authorization.k8s.io/cluster-autoscaler unchanged
role.rbac.authorization.k8s.io/cluster-autoscaler unchanged
clusterrolebinding.rbac.authorization.k8s.io/cluster-autoscaler unchanged
rolebinding.rbac.authorization.k8s.io/cluster-autoscaler unchanged
deployment.apps/cluster-autoscaler configured
...Cluster Autoscaler deployed.

What happens next is that autoscaling won't work. When it tries to add machines to the cluster, this error occurs in the autoscaler logs:
Failed to get node group options for autoscaled-cpx41: Not implemented
The new machine is requested correctly (present in the Hetzner console), but won't join the cluster. Is it a bug impacting existing autoscaling configurations or what should I do differently?
Thanks!

I suspect this may be due to some post create commands not being executed correctly on the autoscaled nodes, perhaps due to the yaml formatting. If you ssh into an autoscaled node, do you see the expected content in  /etc/systemd/network/10-ens10.network?

You're right, it's not been created. I can probably use ip route add but this multiple lines command was about making the changes permanent.
Is it happening because pipe symbol followed by a command with multiple lines isn't supported during configuration parsing? The command otherwise looked quite standard.

Out of curiosity can you test with v2.rc3 (on a temp cluster! don't use it on a production cluster yet) and see if you can reproduce the same issue? I am quite busy at the moment so I can't check this before the weekend or later.

Edit: Just tried with ip route add instead of the bigger command and it worked fine :)

Nice! I guess we can close this? Or actually would you mind adding a PR to the more-refactoring branch to add this info to the docs?

I am closing this, feel free to open another issue if you have others.

Thanks for the reply! I had a couple days off last week, will create a PR :)

@vitobotta can you allow me to create a new branch so that I can create this minor PR please?
Thanks and congrats for v2!

Hi! Since the branch I mentioned has been merged, just open a PR based on main :)

authors: Jboulery vitobotta


text:
Docs for running simulation

Is there any documentation/tutorial on how to run the simulator locally?

Not really. This is the binary we used for simulations: https://github.com/vitorenesduarte/fantoch/blob/main/fantoch_ps/src/bin/simulation.rs
I don't remember much anymore, but I think that this can be run with cargo run -p fantoch_ps --bin simulation.
Let me know if this doesn't work or if you have any other questions.

I had to change the path here: https://github.com/vitorenesduarte/fantoch/blob/main/fantoch_ps/src/bin/simulation.rs#L17
But otherwise, it seems to work. Thanks!

Glad to hear that!

authors: haraldng vitorenesduarte

repo: vitorenesduarte/fantoch


text:
initial fastlane structure

Someone requested to have your app included with F-Droid, so you will need these metadata (taken from its listing in my repo). Be welcome to use my Fastlane Cheat Sheet to build on this (eg adding per-release changelogs, a featureGraphic or additional screenshots).

Is the directory path a requirement? I'd like to put these inside docs/ if I can

It's a requirement, yes. The only alternative for F-Droid would be a shortened variant, but that again had to be in the root (/metadata/en-US/*). Doesn't work in subdirectories, sorry.

I just updated the description, logo and new screenshots :) Let's go!

Yes sir! Updated the config here and manually initiated an update of the Fastlane structure, so your changes will be reflected with the next sync. Future changes will be pulled whenever a new release was detected. Thanks – and as indicated in #20 be welcome to pick a badge if you want to link there :smiley:

authors: IzzySoft vitorpamplona

repo: vitorpamplona/amethyst


text:
PyCG on file text

Is there a simple way to call PyCG on a file contents instead passing files?

If you mean PyCG reading from the source code from the standard input, no PyCG does not currently support that.

I mean more like just passing file text as string instead of file.
Is there a fundamental reason why this would be hard?

It would require some refactoring since PyCG currently expects source files to be given as input. Can you give a use case where this functionality might be useful?

I have a dataframe with contents of several hundred thousands of files that I scraped, and I don't want to create a file for each one of them.

Sorry for the late reply, somehow missed the notification for that one.
The use case you are outlining makes sense. Unfortunately at this time, I don't have the resources to implement that, but I would be happy to assist you with an implementation plan.
I would start with the base processor (base.py:ProcessingBase). This class is in charge of reading the files from the input. This functionality needs to be refactored so that one can pass a string of file contents as an argument.

authors: lambdaofgod vitsalis

repo: vitsalis/PyCG


text:
Uncaught TypeError: this.tooltip is undefined

Perhaps I am doing something silly, but trying to recreate the tutorial line by line, I get this error when trying to add a tooltip.

code
import Vizzu from "https://cdn.jsdelivr.net/npm/vizzu@0.4.3/dist/vizzu.min.js";

let data = {
  series: [
  {
    name: 'Genres',
    type: 'dimension',
    values: [
    'Pop', 'Rock', 'Jazz', 'Metal',
    'Pop', 'Rock', 'Jazz', 'Metal',
    'Pop', 'Rock', 'Jazz', 'Metal'
    ]
  },
  {
    name: 'Types',
    type: 'dimension',
    values: [
    'Hard', 'Hard', 'Hard', 'Hard',
    'Smooth', 'Smooth', 'Smooth', 'Smooth',
    'Experimental', 'Experimental', 'Experimental', 'Experimental'
    ]
  },
  {
    name: 'Popularity',
    type: 'measure',
    values: [ 114, 96, 78, 52, 56, 36, 174, 121, 127, 83, 94, 58 ]
  }
  ]
};

let chart = new Vizzu('vizzu-tooltip')

chart.animate({ data });

chart.animate({
  config: {
    channels: {
      x: { set: ['Genres'] },
      y: { set: ['Popularity'] }
    }
  }
})

chart.feature('tooltip',true)

I am on vizzu@0.4.3, using npm live-server.

Hi!
When you call the constructor of Vizzu, it will initialize the library in an async manner. You can call feature() method only when the initialization is finished. To do this, you can use the initializing promise to chain your code after.
chart.initializing.then(chart => {
	chart.feature('tooltip',true);
	return chart;
})

Working example of your snippet:
https://jsfiddle.net/VizzuHQ/dk7b86vc/84/
I'm curious what dataviz you plan to build. That would be great if you could share it when it's ready!

: face_palm :
Thank you Laszlo! I am still finding my way around it, but will be glad to share when ready. This can be closed.

authors: jchrom simzer

repo: vizzuhq/vizzu-lib


text:
pvizio ImportError: cannot import name 'IPVersion' from 'zeroconf' (/usr/lib/python3.7/site-packages/zeroconf.py)

Hello,
Installed pyvizio on Fedora 31 using pip3 and have been unable to successfully run pyvizio;
$ pyvizio --ip=0 discover
Traceback (most recent call last):
File "/usr/local/bin/pyvizio", line 11, in
load_entry_point('pyvizio==0.1.21', 'console_scripts', 'pyvizio')()
File "/usr/lib/python3.7/site-packages/pkg_resources/init.py", line 489, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3.7/site-packages/pkg_resources/init.py", line 2852, in load_entry_point
return ep.load()
File "/usr/lib/python3.7/site-packages/pkg_resources/init.py", line 2443, in load
return self.resolve()
File "/usr/lib/python3.7/site-packages/pkg_resources/init.py", line 2449, in resolve
module = import(self.module_name, fromlist=['name'], level=0)
File "/usr/local/lib/python3.7/site-packages/pyvizio/init.py", line 45, in
from pyvizio.discovery.zeroconf import ZeroconfDevice, discover as discover_zc
File "/usr/local/lib/python3.7/site-packages/pyvizio/discovery/zeroconf.py", line 5, in
from zeroconf import IPVersion, ServiceBrowser, ServiceInfo, Zeroconf
ImportError: cannot import name 'IPVersion' from 'zeroconf' (/usr/lib/python3.7/site-packages/zeroconf.py)
I verified all dependencies were met so, I'm not sure why this is occurring.
Python 3.7.6
pip(3) 20.0.2
$ pip install -U pyvizio
Requirement already up-to-date: pyvizio in /usr/local/lib/python3.7/site-packages (0.1.21)
Requirement already satisfied, skipping upgrade: aiohttp in /usr/local/lib64/python3.7/site-packages (from pyvizio) (3.6.2)
Requirement already satisfied, skipping upgrade: click in /usr/lib/python3.7/site-packages (from pyvizio) (7.0)
Requirement already satisfied, skipping upgrade: jsonpickle in /usr/local/lib/python3.7/site-packages (from pyvizio) (1.2)
Requirement already satisfied, skipping upgrade: requests in /usr/lib/python3.7/site-packages (from pyvizio) (2.22.0)
Requirement already satisfied, skipping upgrade: tabulate in /usr/local/lib/python3.7/site-packages (from pyvizio) (0.8.6)
Requirement already satisfied, skipping upgrade: xmltodict in /usr/local/lib/python3.7/site-packages (from pyvizio) (0.12.0)
Requirement already satisfied, skipping upgrade: zeroconf in /usr/lib/python3.7/site-packages (from pyvizio) (0.23.0)
Requirement already satisfied, skipping upgrade: chardet<4.0,>=2.0 in /usr/lib/python3.7/site-packages (from aiohttp->pyvizio) (3.0.4)
Requirement already satisfied, skipping upgrade: async-timeout<4.0,>=3.0 in /usr/local/lib/python3.7/site-packages (from aiohttp->pyvizio) (3.0.1)
Requirement already satisfied, skipping upgrade: attrs>=17.3.0 in /usr/lib/python3.7/site-packages (from aiohttp->pyvizio) (19.1.0)
Requirement already satisfied, skipping upgrade: multidict<5.0,>=4.5 in /usr/local/lib64/python3.7/site-packages (from aiohttp->pyvizio) (4.7.4)
Requirement already satisfied, skipping upgrade: yarl<2.0,>=1.0 in /usr/local/lib64/python3.7/site-packages (from aiohttp->pyvizio) (1.4.2)
Requirement already satisfied, skipping upgrade: idna<2.9,>=2.5 in /usr/lib/python3.7/site-packages (from requests->pyvizio) (2.8)
Requirement already satisfied, skipping upgrade: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in /usr/lib/python3.7/site-packages (from requests->pyvizio) (1.25.7)
Requirement already satisfied, skipping upgrade: ifaddr in /usr/lib/python3.7/site-packages (from zeroconf->pyvizio) (0.1.6)

Looks like a name collision. Try updating now to 0.1.22 and see if that resolves the issue

Successfully installed pyvizio-0.1.23 via pip with no change in outcome.

You still see the following? ImportError: cannot import name 'IPVersion' from 'zeroconf' (/usr/lib/python3.7/site-packages/zeroconf.py)

If so, try cloning https://github.com/raman325/pyvizio and installing pyvizio using pip install -I <pyvizio repo directory> and then see if it works

OK looks like the issue is related to the fact that there was no minimum version specified for zeroconf. Try updating to latest which should upgrade your zeroconf version and allow you to run the commands

Worked like a charm.  Thank you for the quick response & turnaround!

repo: vkorn/pyvizio


text:
Error logging in: [Errno 8] nodename nor servname provided, or not known

I've created a file named accounts.txt with the following format:
username:password:email:email_password

After adding account details in the aforementioned format, I attempted to perform a login operation. However, I encountered an error during this process.
Log Output:
2023-09-12 14:17:48.433 | INFO     | twscrape.accounts_pool:login_all:155 - [1/1] Logging in USERNAME - MAILADDR
2023-09-12 14:17:50.142 | ERROR    | twscrape.login:next_login_task:181 - Error in LoginAcid: [Errno 8] nodename nor servname provided, or not known
2023-09-12 14:17:50.142 | ERROR    | twscrape.accounts_pool:login:141 - Error logging in to USERNAME: [Errno 8] nodename nor servname provided, or not known

Please assist in resolving this issue.
PS: i use custom domain mail address from yandex mail.
Versions:
twscrape: 0.8.0
SQLite client: 2.6.0
SQLite runtime: 3.41.2 (3.41.2)
Python 3.11.3

@yemregundogmus were you able to figure out what the solution for this issue was? I'm hitting the same error, let me know if you have any pointers to help solve this

Hello @varunmeds and @yemregundogmus, I figured this out on my side.
You need to add your provider server links in the imap.py  file and more precisely in the IMAP_MAPPING dictionary line 26.
IMAP_MAPPING: dict[str, str] = {
"yahoo.com": "imap.mail.yahoo.com",
"icloud.com": "imap.mail.me.com",
"outlook.com": "imap-mail.outlook.com",
"hotmail.com": "imap-mail.outlook.com",
"yourdomain.com": "yourproviderimap.com",
}
There might be better ways to deal with this @vladkens will probably know better but it work well on my side (I do have the issue #86 causing me some issues still.)

authors: BFAGIT varunmeds yemregundogmus

repo: vladkens/twscrape