text:
Flink CDC是否支持读阿里的DRDS的全局binlog，报错如下

2021-03-24 19:36:03,520 INFO  io.debezium.connector.mysql.BinlogReader                     [] - Waiting for keepalive thread to start
2021-03-24 19:36:03,521 INFO  io.debezium.util.Threads                                     [] - Creating thread debezium-mysqlconnector-mysql_binlog_source-binlog-client
2021-03-24 19:36:03,522 ERROR io.debezium.connector.mysql.BinlogReader                     [] - Error during binlog processing. Last offset stored = null, binlog reader near position = /4
2021-03-24 19:36:03,527 INFO  io.debezium.connector.mysql.BinlogReader                     [] - Stopped reading binlog after 0 events, no new offset was recorded
2021-03-24 19:36:08,521 INFO  io.debezium.connector.common.BaseSourceTask                  [] - Stopping down connector
2021-03-24 19:36:08,521 INFO  io.debezium.connector.mysql.MySqlConnectorTask               [] - Stopping MySQL connector task
2021-03-24 19:36:08,521 INFO  io.debezium.connector.mysql.ChainedReader                    [] - ChainedReader: Stopping the binlog reader
2021-03-24 19:36:08,521 INFO  io.debezium.connector.mysql.BinlogReader                     [] - Discarding 0 unsent record(s) due to the connector shutting down
2021-03-24 19:36:08,522 INFO  io.debezium.connector.mysql.BinlogReader                     [] - Discarding 0 unsent record(s) due to the connector shutting down
2021-03-24 19:36:08,531 INFO  io.debezium.jdbc.JdbcConnection                              [] - Connection gracefully closed
2021-03-24 19:36:08,534 INFO  io.debezium.connector.mysql.MySqlConnectorTask               [] - Connector task finished all work and is now shutdown
2021-03-24 19:36:08,545 ERROR com.alibaba.ververica.cdc.debezium.DebeziumSourceFunction    [] - Reporting error:
org.apache.kafka.connect.errors.ConnectException: [12337214b6ce6000][172.16.176.72:3306][sdm]Unknown command Error code: 1047; SQLSTATE: HY000.
at io.debezium.connector.mysql.AbstractReader.wrap(AbstractReader.java:241) ~[flink-sql-connector-mysql-cdc-1.2.0.jar:1.2.0]
at io.debezium.connector.mysql.AbstractReader.failed(AbstractReader.java:207) ~[flink-sql-connector-mysql-cdc-1.2.0.jar:1.2.0]
at io.debezium.connector.mysql.BinlogReader$ReaderThreadLifecycleListener.onCommunicationFailure(BinlogReader.java:1142) ~[flink-sql-connector-mysql-cdc-1.2.0.jar:1.2.0]
at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:962) ~[flink-sql-connector-mysql-cdc-1.2.0.jar:1.2.0]
at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:595) ~[flink-sql-connector-mysql-cdc-1.2.0.jar:1.2.0]
at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:839) ~[flink-sql-connector-mysql-cdc-1.2.0.jar:1.2.0]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_111]
Caused by: com.github.shyiko.mysql.binlog.network.ServerException: [12337214b6ce6000][172.16.176.72:3306][sdm]Unknown command
at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:926) ~[flink-sql-connector-mysql-cdc-1.2.0.jar:1.2.0]
... 3 more
2021-03-24 19:36:09,564 INFO  io.debezium.embedded.EmbeddedEngine                          [] - Stopping the embedded engine
2021-03-24 19:36:09,578 INFO  io.debezium.embedded.EmbeddedEngine                          [] - Stopping the embedded engine
2021-03-24 19:36:09,584 WARN  org.apache.flink.runtime.taskmanager.Task                    [] - Source: Custom Source (1/1)#0 (6bf35819d2cc9bfadfbda675ca5e1234) switched from RUNNING to FAILED.
org.apache.kafka.connect.errors.ConnectException: [12337214b6ce6000][172.16.176.72:3306][sdm]Unknown command Error code: 1047; SQLSTATE: HY000.
at io.debezium.connector.mysql.AbstractReader.wrap(AbstractReader.java:241) ~[flink-sql-connector-mysql-cdc-1.2.0.jar:1.2.0]
at io.debezium.connector.mysql.AbstractReader.failed(AbstractReader.java:207) ~[flink-sql-connector-mysql-cdc-1.2.0.jar:1.2.0]
at io.debezium.connector.mysql.BinlogReader$ReaderThreadLifecycleListener.onCommunicationFailure(BinlogReader.java:1142) ~[flink-sql-connector-mysql-cdc-1.2.0.jar:1.2.0]
at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:962) ~[flink-sql-connector-mysql-cdc-1.2.0.jar:1.2.0]
at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:595) ~[flink-sql-connector-mysql-cdc-1.2.0.jar:1.2.0]
at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:839) ~[flink-sql-connector-mysql-cdc-1.2.0.jar:1.2.0]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_111]
Caused by: com.github.shyiko.mysql.binlog.network.ServerException: [12337214b6ce6000][172.16.176.72:3306][sdm]Unknown command
at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:926) ~[flink-sql-connector-mysql-cdc-1.2.0.jar:1.2.0]
... 3 more

目前还没有对接 DRDS。

Closing this issue because it was created before version 2.3.0 (2022-11-10). Please try the latest version of Flink CDC to see if the issue has been resolved. If the issue is still valid, kindly report it on Apache Jira under project Flink with component tag Flink CDC. Thank you!

authors: PatrickRen qingfengKnight wuchong

repo: ververica/flink-cdc-connectors


text:
[MySql] not to throw an exception when bin log format changed from row to others to stop job from endless restarting.

issue:
flink job get restarted and stuck at an exception  when bin log format changed from row to others
exception :
Caused by: io.debezium.DebeziumException: Received DML

versions:
flink 1.13
cdc 2.2.1
mysql  5.6
suggested solution:
not to throw an exception when bin log format changed from row to others
and increase the  bin log offset by one until the bin log format changes back to row

duplicated to #1017

Debezium has a issue to fix this DBZ-3949. We could set event.deserialization.failure.handling.mode to warn to skip this failure.

Closing this issue because it was created before version 2.3.0 (2022-11-10). Please try the latest version of Flink CDC to see if the issue has been resolved. If the issue is still valid, kindly report it on Apache Jira under project Flink with component tag Flink CDC. Thank you!

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
[flink-cdc-common]  Add Event API

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
As designed doc described, add defined Class for Event、SchemaChangeEvent、DataChangeEvent、FlushEvent
Solution
No response
Alternatives
No response
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

closed by https://github.com/ververica/flink-cdc-connectors/pull/2664.


text:
🛑 randomplanetfacts.xyz is down

In b03ee7d, randomplanetfacts.xyz (https://randomplanetfacts.xyz) was down:

HTTP code: 521
Response time: 208 ms

Resolved: randomplanetfacts.xyz is back up in 0c503e3 after 5 days, 14 hours, 32 minutes.

repo: vesahc/upptime-pln

license: MIT


text:
back-ticks fenced code blocks were indented (#366)

For the reason indentation itself is the semantics
of the basic code block [0], thus the backticks fenced
code blocks [1] will end up being escaped [2].
[0] https://www.markdownguide.org/basic-syntax#code-blocks
[1] https://www.markdownguide.org/extended-syntax/#fenced-code-blocks
[2] https://docs.nebula-graph.com.cn/2.0.1/4.deployment-and-installation/1.resource-preparations/
Could you please help see if it's the way to fix this(sorry, I didn't try to render it via mkdocs yet)?

Thank you for pointing out the format issues. To save your time, I co-authored this PR.
Code blocks following ordered lists or unordered lists must be indented accordingly, otherwise, GFM and mkdocs cannot render the order numbers correctly. I have fixed the indentation issues in the two docs and tested through mkdocs on my local machine and now the issues should be solved.

source: gharchive/pull-request

repo: vesoft-inc/nebula-docs-cn


text:
duplicate items were sent when delete edge | vertex .

duplicate items were sent when delete edge | vertex .
This is a graph bug,  need to using dedup node . instead of PR : #1244
recreate step :
CREATE SPACE test_space (partition_num=1,replica_factor=1, vid_type=fixed_string(30)); \
USE test_space; \
create tag t1(c1 fixed_string(40)); \
create edge e1(c1 fixed_string(40)); \
create edge index ei1 on e1(c1);

insert vertex t1(c1) values "1":("row"), "2":("row"), "3":("row")
insert edge e1(c1) values "1" -> "2"@0:("row"), "2" -> "1"@0:("row")
delete vertex "1","2"

What's the issue, I execute the ngql and nothing happened.

authors: Shylock-Hg bright-starry-sky

repo: vesoft-inc/nebula-graph


text:
Add estimate moved docs ratio unit test.

@geirst : please review

@toregge please merge after merge stop is lifted.

authors: geirst toregge

repo: vespa-engine/vespa


text:
Add cloud to SystemInfo

@bratseth

PTAL


text:
Remove undocumented and untested script

Script has an error (wrong Java class name) and gives no useful output (covered by metrics and other tools), removing
I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

@vekterli please take a look again


text:
Be more careful when adding extra overrides to summary map

@geirst : please review

👍


text:
slide中公式显示有问题

所有的 $$\LaTeX$$ 公式显示都坏掉了
e.g.炫酷反演魔术
好像是用的mathjax cdn炸了

这个issue应该close了（

repo: vfleaking/uoj

license: mit

license_source: bigquery


text:
Fixes 4070: Change apoc.ml.fromCypher prompt

Fixes 4070: Change apoc.ml.fromCypher prompt

LGTM


text:
Add some user and tech doc

it's not complete but it's a beginning
user documentation

[X] Idea products compatibility
[x] Opa version compatibility
[X] Faq (test duration and pass test )
[X] how to create new rego file and edit the template used for creation
[X] how to change highlighting color
[X] comment code

tech doc

[x] opa version used for test
[x] Architecture (project structure, kotlin gradle dsl, testing strategy)
[x] correct spelling mistakes noticed in #4
[X]  create rego file implementation

@asadali  thanks a lot for the review  !

repo: vgramer/opa-idea-plugin


text:
Syncing across devices with Github Gists

Addresses #115
+ New options floating table of content

To do

[ ] Add merge option when a gist database already exists
[x] Improve time to display in the popup
[ ] Update Popup UI if the user is on a Paper's page that gets deleted, and vice versa

All tests passing ✅

All tests passing ✅

All tests passing ✅

Merging in alpha stage see #115


text:
Replacing usage of 'eval' in repository

Hi,
While I was trying to figure out how to both enable users to use both "PyTorch" loss functions and custom loss functions (ref. pull request #22), I was made aware that usage of eval often is discouraged and can even be dangerous (if abused).
Therefore, I propose that we replace the three instances of it in this repository:
model.py:
def get_model_instance(model_arch, model_params):
    try:
        model = eval(model_arch)

metric.py
def get_metric_functions(metric_names):
    try:
        metric_fns = [eval(metric) for metric in metric_names]

trainer.py
   def _valid_epoch(self, epoch):
        self.model.eval()

I am not certain about what to replace it with. Any of you know?

The third example model.eval() seems to have nothing to do with this issue.
The eval() discouraged to use may refer to the first and second, which changes string into the variable handle. I don't understand how this can be dangerous but I felt this uncomfortable since the linter always complains about that. Maybe I can study this later. I will post some references here, if I find.
I think we can just replace the eval() with use of dictionary of function handles.

From now on, it seems that simple usage of eval() just like ours has no problem.
Here is reference

authors: SunQpark borgesa

repo: victoresque/pytorch-template


text:
Shopify Watch/Deploy Extra

Hey @greypants, I'm not certain this belongs in an extra but it seems fairly suitable. I've found this to be helpful recently.

👏  Nice!

@solomonhawk ping!

@greypants How does this look? (can you just verify that I've used handleErrors correctly in 09c8cf0 ?)

Looks pretty good! Could you add a config.json with the paths configured for the shopify folder structure?

authors: greypants solomonhawk

repo: vigetlabs/gulp-starter


text:
Code Generator can not detect #ifdef VALUE_CLASS_Char

When making my own FastUtil implementation i found out that VALUE_CLASS_Char is useless since it is wrongly defined in teh gensource.sh
so if anything that uses that predicate is basically not applied.

Fuck, this is so contorted it took me some time.
Your bug report should have been:
Maps with char values are missing the addToValue() method because the driver file mistakenly uses VALUE_CLASS_Char instead of VALUE_CLASS_Character.

@vigna Yeah i know. I already fixed it but i wasn't sure if it was used somewhere else since it falls under the byte,short,char category.

authors: Speiger vigna

repo: vigna/fastutil


text:
Spliterator and iterator use different ordering for sets

With the introduction of optimized spliterators in 8.5.x, the streaming order diverged from the iteration order for unordered collections. I don't think this violates any specification or documentation, but it could have some unintended consequences and I wanted to confirm that the divergence is intentional.
For example (on 8.5.12):
jshell> import it.unimi.dsi.fastutil.ints.*

jshell> var s = new IntOpenHashSet(new int[] { 0, 1, 2, 3 })
s ==> {0, 1, 3, 2}

jshell> s.toIntArray()
$4 ==> int[4] { 0, 1, 3, 2 }

jshell> s.toArray()
$5 ==> Object[4] { 0, 1, 3, 2 }

jshell> s.intStream().toArray()
$6 ==> int[4] { 0, 2, 3, 1 }

jshell> s.stream().toArray()
$7 ==> Object[4] { 0, 2, 3, 1 }

In version, 8.4.4 these arrays all have the same order. But in 8.5. the order is reversed for streams (except for 0, the null value).
I don't think this is strictly wrong, but I do think it could be surprising. For example, a user might build one array with toIntArray() and another with intStream().map(...).toArray(), incorrectly expecting that the mapped values correspond to the values at the same indices in the first array.

It's not intentional, but the contributor who wrote the SplitIterator implementation decided to enumerate by scanning the backing map forward (which makes sense, in particular when you split), whereas SetIterator always iterated backward (a pet peeve of mine a few years ago). In principle one might rewrite SetIterator with a forward logic, but really it makes no sense for a super-stable, super-tested class. Consider that the streams can be split and used in parallel, so you shouldn't really have any expectation about the iteration order.

authors: pburka vigna


text:
Tech Stack Update ( LOGO add )

I will like to add tech stack logo used in our project this will make our project attractive !! Will start to work on this issue as soon as i get assigned !!

Okay

I will like to add tech stack logo used in our project this will make our project attractive !! Will start to work on this issue as soon as i get assigned !!

Are you a GSSOC'21 participant?
If yes please mention it in your issues.

Which tech stack will you like to get updated ?

Which tech stack will you like to get updated ?

You are supposed to do research on it and update readme.md . Kindly do the same.

repo: vigneshshettyin/Bulk-Mailer


text:
Update scalameta to 4.8.12

About this PR
📦 Updates org.scalameta:scalameta from 4.8.11 to 4.8.12
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
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!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalameta" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalameta" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:semver-spec, commit-count:1

Superseded by #125.

repo: vigoo/metagen


text:
2023-12-25

執筆者名
ぺりー
記事タイトル
Vimで始める正規表現
記事 URL
https://satorunooshie.medium.com/vim-with-regexp-7baa93d1205c

投稿は完了しているので閉じますmm

repo: vim-jp/ekiden


text:
Function calls not highlighted in f-strings within {}

Line 1 shows a user-defined function.
In line 4, the call to hello() is properly highlighted.
Line 6 shows the member function join(), which is also properly highlighted.
However, both functions are not highlighted within f-strings (line 8 and 10).
I could not figure out from python.vim, why the build-in function str(), and the reserved words 'for' and 'in' are highlighted, but the above mentioned functions not.
Is this a bug?

it works now

repo: vim-python/python-syntax


text:
gm and g^ do not remember column for vertical motion in folds

Steps to reproduce
Given some text:
    Alice was beginning to get very tired of sitting by her sister on the bank, and
    of having nothing to do: once or twice she had peeped into the book her sister
    was reading, but it had no pictures or conversations in it, “and what is the use
    of a book,” thought Alice “without pictures or conversations?”

Create a fold of the middle two lines (jVjzf)
Position cursor on the fold
Type gm, note that :set ruler shows 59-1
Type k, the cursor navigates to line 1, column 1

Expected behaviour
When typing gm<Up> I expect Vim to use the current column (59) on the new line
Similarly, if using g^, the ruler shows 5-1 but hitting <Up> moves to column 1. However, g$ shows 83-1 in the ruler and hitting <Up> will move to column 83 on line 1, as expected.
The column is remembered and used if typing gm<Right>, g^<Right> or g$<Right>. The fold is opened and the caret is correctly moved.
Version of Vim
9.0 (2022 Jun 28, compiled Oct 19 2022 18:24:48)
Environment
VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Oct 19 2022 18:24:48)
macOS version - x86_64
Included patches: 1-800
Compiled by Homebrew
Logs and stack traces
No response

I looked into this a bit but will leave the rest to someone else, since it will take me too much time to understand everything and create a thorough patch.
Here are my findings, though:

I tested old versions and have concluded that this is not a regression.
The functions that are bugged, like nv_g_home_m_cmd() in normal.c, set w_set_curswant to TRUE, while a function that is not bugged (nv_g_dollar_cmd()) instead calls update_curswant_force(). If you replace the statement that sets w_set_curswant to TRUE with a call to update_curswant_force(), the bug seems to be fixed.

Updating w_curswant every time adds over head (quite a lot for a long line).
So, the solution could be to call update_curswant_force() if "curwin->w_cline"_folded is set.

authors: brammool citizenmatt simmsbra

repo: vim/vim

license: Vim


text:
Unmatched candidates are displayed on i_CTRL-X_CTRL-F & completeopt+=fuzzy

Steps to reproduce

vim --clean
set completeopt=menuone,noselect,fuzzy
insert path like /qqq that does not exist
type <c-x><c-f> to start files completion
files or directories don't have 'qqq' in their name, but they are displayed

Expected behaviour
Only candidates with a match (in the example above, files containing 'q' three times) are displayed.
If there are no matching files, nothing is displayed.
Version of Vim
9.1.618
Environment
OS: macOS Sonoma 14.5
Terminal: wezterm 20240203-110809-5046fc22
value of $TERM: xterm-256color
Shell: zsh 5.9 (arm-apple-darwin23.0.0)
Logs and stack traces
No response

@glepnir

authors: kawarimidoll techntools


text:
Global mark lost after executing a :vimgrep command

vim --version: 8.0 patches up to 1159
Operating system/version: Linux, Ubuntu 16.04
Terminal name/version: xfce4-terminal
$TERM: xterm-256color

Sometimes, one of the global marks I set on a file is lost, or changed to another file.
I think it happens after executing a :vimgrep command.
Here's a way to reproduce.
Create a temporary file:
$ touch /tmp/file

Start Vim to edit this file and set the global mark Z on it:
$ vim /tmp/file
mZ
:q

Start a new Vim session without any custom configuration, and load the file by pressing 'Z to check the global mark has been correctly set and saved in ~/.viminfo:
$ vim -Nu NONE
'Z
:q

It should work as expected. Now, restart a new Vim session, again with no custom configuration. Don't load the /tmp/file, and execute :vimgrep to search for a random pattern inside the /tmp directory.
$ vim -Nu NONE
:vimgrep /random_pattern/ /tmp/**/*

You will probably get the error E480 (No match: random_pattern), which is expected. But now, if you try to load the /tmp/file by pressing 'Z, instead of loading the file, Vim displays the error E92 (Buffer 2 not found). And if you execute :marks, you should see that the global Z mark is not set anymore.
It seems that Vim loaded /tmp/file to look for random_pattern, didn't find it, and thus wiped the buffer. And by wiping the buffer, the global mark is deleted.
Would it possible for :vimgrep to not wipe a buffer for which a global mark exists, and instead only delete it with :bdelete?

That's exactly what happens, if there are no matches in the buffer it is :bwipeout'd away here.

sounds familiar:
https://groups.google.com/d/msg/vim_dev/Z85RljTZOtw/6i7HM2e-gRgJ
reported by me and includes a patch to fix this behaviour. Back then the reaction was to declare this as a feature. Patch is still available here, don't know if it still applies and the test should be converted to a new style test.

@chrisbra Yes I agree with you. I would like to consider global marks as associated to file paths, like bookmarks in a web browser are associated to a url. Not to a buffer. So, I would prefer that :bwipe leaves global marks untouched.
But at the very least, a :vimgrep command, or any command other than :bwipe (& maybe commands closely related to it), should not delete a global mark. :vimgrep has nothing to do with :bwipe, it's just a detail of implementation that the user shouldn't be concerned with.

As a workaround, I'm experimenting a modified version of this code:
set viminfo^=!

fu! s:global_mark_set(char) abort
    let g:GLOBAL_MARK_{a:char} = { 'fpath': expand('%:p'), 'pos': getpos('.')[1:2] }
endfu

fu! s:global_mark_go(char) abort
    if !exists('g:GLOBAL_MARK_'.a:char)
        let info = get(filter(split(execute('marks'), '\n'), 'v:val =~# "^\\s*'.a:char.'"'), 0 , '')
        if !empty(info)
            let fpath = matchstr(info, '^\s*'.a:char.'\s\+\d\+\s\+\d\+\s\+\zs.*')
            let pos   = split(matchstr(info, '^\s*'.a:char.'\s\+\zs\d\+\s\+\d\+'))
            let g:GLOBAL_MARK_{a:char} = { 'fpath': fpath, 'pos': pos }
        else
            return ''
        endif
    endif

    try
        exe 'e '.g:GLOBAL_MARK_{a:char}.fpath
        call timer_start(0, {-> execute('call cursor(g:GLOBAL_MARK_'.a:char.'.pos)|redraw')})
    catch
        return 'echoerr '.string(v:exception)
    endtry

    return ''
endfu

fu! s:global_mark_build() abort
    for upper in map(range(char2nr('A'),char2nr('Z')), 'nr2char(v:val)')
        sil! exe "nno <silent> '".upper.' :<c-u>exe <sid>global_mark_go("'.upper.'")<cr>'
        sil! exe 'nno <silent> m'.upper.' :<c-u>call <sid>global_mark_set("'.upper.'")<cr>'
    endfor
endfu

call s:global_mark_build()

It installs wrapper mappings around all 'A, ..., 'Z, mA, ..., mZ commands, and saves / uses information about the marks in the viminfo file.

authors: LemonBoy chrisbra lacygoill


text:
maximizing the quickfix window "eats" a line when &laststatus == 1

In a pristine vim configuration the following commands
% vim -u NONE
:copen
CTRL-W O
:bdelete
CTRL-W O
:bdelete
will make the second quickfix window one line shorter than the first one. The command line will be drawn not on the last line but on the last but one line. This lost line is not restored even when the second quickfix window is closed. The same happens in gvim.
This does not happen when 'laststatus' is set to 0 or 2.

I am not sure what you are seeing. First of all, CTRL-W O does not exists, I suppose you mean :only (e.g. <C-W>o.  But nevertheless there is no quickfix window involved. I am missing something.

Sorry, there was a mistake in my first posting, the second CTRL-W O should be :copen instead. And you are right, I meant <C-W>o aka :only. Let me do this again, with screenshots.
I start pristine vim (v8.1.320 as distributed in debian/sid):
% vim -u NONE

:copen

:only

:bdelete

:copen  (This is where I've got it wrong in the first posting.)

:bdelete

Here we see that the command line appears on the penultimate line.
:set laststatus

And we've lost that last line until the end of the vim session.

authors: chrisbra tertium


text:
Does not keep the aspect ration when switching from smaller screen to larger screen.

Instructions: Replace the template text and remove irrelevant text (including this line)
Describe the bug
After splitting screen using sp if we move to some bigger monitor aspect ration get dis-propertionate.
To Reproduce
Detailed steps to reproduce the behavior:

Run vim on any 14'' (inch )screen
Split screen using sp
Move your terminal to some bigger screen (24'' inch)
You'll see change in aspect ratio.

Expected behavior
partition shape should not change in bigger screen.
Screenshots

Environment (please complete the following information):

VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Oct 13 2020 15:49:09)
Included patches: 1-1453

OS: [Ubuntu 18.04]

Terminal: GNOME Terminal

I see this also when resizing a terminal (with the mouse).
What happens is that the change in size is applied to the last window (until it runs out of space).
I'm not sure if this should be called a bug.  When increasing the size we could also make other windows bigger, but when reducing the size keeping the aspect ratio isn't that easy.


text:
May leak memory in completion when ga_grow() fails

Problem:  May leak memory in completion when ga_grow() fails.
Solution: Free "wca" when ga_grow() fails.
Fix #14248

thanks!

authors: chrisbra zeertzjq


text:
Fix setbufline()

Problem
When applying setbufline() with lines list to the buffer which sets foldmethod=expr, Vim sets lines into unintented buffer.
Repro steps (by @thinca)
reproduce.vim:
setlocal foldmethod=expr foldexpr=0
new
call setbufline(1, 1, [1, 2, 3])

$ vim --clean -S reproduce.vim
expected: lines [1, 2, 3] is into bufnr=1 buffer
actual: only 1 line [1] is into bufnr=1 buffer, lines [2, 3] is into bufnr=2 buffer (current buffer)
Solution

Change/restore curwin

Remaining problem: when setbufline() to hidden buffer, curwin keeps actual current window, this may cause unexpected buffer-state.

Codecov Report

Merging #2293 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2293      +/-   ##
==========================================
+ Coverage   74.42%   74.42%   +<.01%
==========================================
  Files          90       90
  Lines      132130   132139       +9
  Branches    30730    29017    -1713
==========================================
+ Hits        98341    98349       +8
+ Misses      33764    33761       -3
- Partials       25       29       +4

Impacted Files
Coverage Δ

src/evalfunc.c
83.44% <100%> (+0.03%)
:arrow_up:

src/if_xcmdsrv.c
83.99% <0%> (-0.18%)
:arrow_down:

src/if_py_both.h
76.09% <0%> (-0.15%)
:arrow_down:

src/window.c
80.79% <0%> (-0.07%)
:arrow_down:

src/eval.c
80.77% <0%> (-0.05%)
:arrow_down:

src/channel.c
82.44% <0%> (ø)
:arrow_up:

src/gui_gtk_x11.c
47.65% <0%> (ø)
:arrow_up:

src/gui.c
47.16% <0%> (ø)
:arrow_up:

src/ex_cmds.c
78% <0%> (+0.22%)
: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 53ec795...1d96053. Read the comment docs.

authors: codecov-io ichizok


text:
WIP: Filter found ctags by the type/kind

Especially when working with the linux kernel, ctags output often has dozens of entries and so far in vim there are no means to easily filter them by type (e.g. structure name or other types as specified in http://ctags.sourceforge.net/FORMAT). This (lack of) behavior is annoying, and targeted for improvement in the runtime/doc/todo.txt
Introducing a filter that will by default retain the old practice of displaying everything, but will only show a specific type of ctags records after a mapped letter is pressed on the keyboard.
To test the patch, do (for example):

Set up ctags as you would normally do and open a source code file
Put the cursor on a structure name somewhere
Press g ] or otherwise enter the mode where you see a list of tags
Press s to only see your structure's definition
*) If there are more than one screen worth of entries, you'd need to exit the more mode with q before the filter starts accepting keypresses. more will return upon refreshing the filter if necessary.
*) Press s again to clear the filter
Hit Enter to go to the entry number prompt

This patch only deals with one (my) user case so far, but I'm looking to expand it, hence the WIP prefix. Please help me by defining other cases here, if they are deemed necessary.
Please make your diff ignore whitespaces as these commits includes many indentation changes.

Codecov Report

Merging #2871 into master will decrease coverage by 0.01%.
The diff coverage is 56.3%.

@@            Coverage Diff             @@
##           master    #2871      +/-   ##
==========================================
- Coverage   75.44%   75.43%   -0.02%
==========================================
  Files          92       92
  Lines      134831   134842      +11
==========================================
- Hits       101724   101718       -6
- Misses      33107    33124      +17

Impacted Files
Coverage Δ

src/tag.c
72.39% <56.3%> (-0.02%)
:arrow_down:

src/term.c
59.62% <0%> (-0.21%)
:arrow_down:

src/message.c
74.59% <0%> (-0.2%)
:arrow_down:

src/if_xcmdsrv.c
84.53% <0%> (-0.18%)
:arrow_down:

src/window.c
81.89% <0%> (-0.1%)
:arrow_down:

src/ex_cmds2.c
78.58% <0%> (-0.1%)
:arrow_down:

src/gui_gtk_x11.c
47.68% <0%> (-0.05%)
:arrow_down:

src/channel.c
83.1% <0%> (-0.04%)
:arrow_down:

src/if_py_both.h
76.59% <0%> (ø)
:arrow_up:

src/eval.c
81.48% <0%> (+0.04%)
: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 606cb8b...5de039e. Read the comment docs.

Especially when working with the linux kernel, ctags output often has dozens of entries and so far in vim there are no means to easily filter them by type (e.g. structure name or other types as specified in http://ctags.sourceforge.net/FORMAT). This (lack of) behavior is annoying, and targeted for improvement in the runtime/doc/todo.txt
Introducing a filter that will by default retain the old practice of displaying everything, but will only show a specific type of ctags records after a mapped letter is pressed on the keyboard.
To test the patch, do (for example):

Set up ctags as you would normally do and open a source code file
Put the cursor on a structure name somewhere
Press g ] or otherwise enter the mode where you see a list of tags
Press s to only see your structure's definition
*) If there are more than one screen worth of entries, you'd need to exit the more mode with q before the filter starts accepting keypresses. more will return upon refreshing the filter if necessary.
*) Press s again to clear the filter
Hit Enter to go to the entry number prompt

This patch only deals with one (my) user case so far, but I'm looking to expand it, hence the WIP prefix. Please help me by defining other cases here, if they are deemed necessary.
Please make your diff ignore whitespaces as these commits includes many indentation changes.

Hmm, filtering tags after listing them is rather limited.  I mostly use
autocomplete.
How about using something like:
:tag s/tagname

Where "s/" means of type "s" (struct).  Then I can do:
:tag s/tag<Tab>

To only complete structs.
Is "/" never used in an actual tag name?  An alternative is to separate
with a space:
:tag s tag<Tab>

For filtering the list, this assumes the type is always a single
character. Is that really true?
--
Vim is like Emacs without all the typing.  (John "Johann" Spetz)
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Well, in the ctags source the tag kind is denoted by a single "kind letter":
typedef struct sKindOption {
        boolean enabled;          /* are tags for kind enabled? */
        int letter;               /* kind letter */
        const char* name;         /* kind name */
        const char* description;  /* displayed in --help output */
} kindOption;

Moreover, I'm not sure whether there are languages that call for more than [26 letters + 10 numbers] kinds of tags, so everything will probably stay this way...
I'm pushing the commit with :tag <tagkind> <tagname> support. It would also be possible to use / as a separator. Please take a look!

Looked at this again, sorry it took so long.
The place to check for a match is around "First try matching with the pattern literally".
We do need to support multi-character kind names.
I do think to use something like {kind}/{tagname} is useful.  This can also be used in other places.
Not sure if a slash is the best character for separating the kind from the tagname.

Yeah, I've been tinkering around with the thing on my own, and {kind}/{tagname} seems very comfortable - at least for the C/C++/python mix.
Honestly don't understand the case for multi-character kind names, but this oughtn't be much more difficult to do.
I'll update the PR in a couple weeks :)

(Just idea of extension of this: to add possibility to sort tags by type, when "-- More --" or "Type number and  (empty cancels):" invites for key press)

this is "WIP" for more than a year, therefore closing.

authors: brammool codecov-io emmrk tkhai


text:
Adjust Cygwin preprocessor directives

__CYGWIN__ and _WIN32 won't be defined at the same time since Cygwin
GCC 4.x. (That could happen only when Cygwin GCC 3.x was used with the
-mno-cygwin option.)
Actually, when windows.h is included, WIN32 and _WIN64 might be
defined, but that doesn't matter here.
Simplify the conditions.

I'm also thinking whether we should change __CYGWIN32__ to __CYGWIN__ or remove it, because __CYGWIN32__ is only defined in 32-bit Cygwin and not defined in 64-bit Cygwin.
This part might be better to be enabled in 64-bit Cygwin?
https://github.com/vim/vim/blob/c6d6d6aef1900109fd1ad43835791ba04eff764c/src/main.c#L2571-L2579
This part is outdated and can be removed:
https://github.com/vim/vim/blob/c6d6d6aef1900109fd1ad43835791ba04eff764c/src/vim.h#L64-L70
The following part might be also removed?
Files are opened in the binary mode by default in Cygwin, because Cygwin's mount command mounts the filesystems in the binary mode by default. I'm not sure what happens when a filesystem is mounted in the text mode, but it is not cared in our implementation for 64-bit Cygwin.
https://github.com/vim/vim/blob/c6d6d6aef1900109fd1ad43835791ba04eff764c/src/vim.h#L1578-L1586
This part can be removed:
https://github.com/vim/vim/blob/c6d6d6aef1900109fd1ad43835791ba04eff764c/src/pty.c#L49-L52
Maybe we can remove the condition  && !defined(__CYGWIN32__):
https://github.com/vim/vim/blob/c6d6d6aef1900109fd1ad43835791ba04eff764c/src/os_unix.c#L6344-L6347

We generally use "32" for "32 bits and up".  To distinguish from very old 16-bit windows.  Which we don't support anymore, thus "win32" is equivalent to "MS-Windows".  This is also used in has(), thus changing it causes more problems than it solves.
If Cygwin uses 32 for 32 bits and not 64 bits this gets confusing.  Just using CYGWIN would be clearer.
I suppose I can include this PR and other changes will follow.

If Cygwin uses 32 for 32 bits and not 64 bits this gets confusing. Just using __CYGWIN__ would be clearer.

Yes, __CYGWIN32__ is used only for 32 bits.
I created #9709.

authors: brammool k-takata


text:
Misaligned percent in Skills Tab (in mobile view)

Misaligned percent in Skills Tab
In mobile view of
https://vinaysomawat.github.io/
This may be a result of a misplaced <div> or omission of a <br> tag.
I, being an experienced web developer (since grade6) would be able to debug these out to make this wonderful portfolio website great again.

Can I work on this?


text:
ERC-20 Tokens Exercise

Implement a solution for the ERC-20 Tokens Exercise.

Submitted to Base Goerli: https://goerli.basescan.org/address/0xC9aAb50e212e8AD9e23CEC740369d4ae0876eF0D#code

repo: vince-grondin/base-camp


text:
Security Data Issues Secrets in clear text

Hi,url : https://github.com/vincent51689453/Digital_Twins_IC382/blob/0138c62857eacd63025a7123e56ada7822d6d6be/src/robot_deep_learning/src/third_party/models/research/syntaxnet/tensorflow/tensorflow/core/platform/cloud/testdata/service_account_credentials.json You have commit that need to remove from the github historyattacker can see it and use it ...encrypt your secrets !!!!Our Bug Help you to be more Secure and protect your data ?Buy me a coffee (or more likely a beer)https://www.paypal.com/paypalme/bugbounty1/150USDhttps://www.buymeacoffee.com/bugbounty☕☕☕☕☕

Really thanks for your reminder 🙇🏻♂🙇🏻♂

Really thanks for your reminder 🙇🏻♂🙇🏻♂


text:
stove UNICA NOBIS FIRE not climate ma number

hi, I've a questions..
Is possible to have a number.stufa_salotto_vent_rear?  now I have only climate:stufa_salotto_vent_rear but i cannot use to set in node red fan speed. in nodered..so if there are both one and the other it would be better
thanks

Hi! You can call the action climate.set_fan_mode from Node-RED. As destination use your climate.stufa_salotto_vent_rear

okey...just do it (i don't know what.. but I deleted and remaked the node and work fine)...now another question for you...please..
do you have a list of all the states and all the attributes of all the entities of the unique micronova nobis? Because I often can't figure out how to configure the nodes. for example: if I go into the entity's history, if you select the wood reserve it tells me the state is "ok" (I imagine it means that the wood is sufficient) but when it enters the wood reserve, how does the status change? So I would like a list for all the other entities too if possible thanks

I added them in  0.6.0

thanks for the replyI'm sorry to bother you for such simple things, unfortunately I'm not a programmer, and I'm not even that intelligent, for me the world of home automation is a new, intriguing and interesting world. unfortunately I lack the basics and often ask stupid questions. like for example the next one I'll make for you:I have searched and searched in every way to find a way to find by myself all the states and attribute names that an entity can have.For example also of all the entities of your work. I still don't understand how to use many of them because I don't know what states or attributes they can take on. Is there a way to figure this out? or simply where should I look for the necessary documentation to discover this data?Thank you again for your infinite patience with meInviato dal mio Galaxy
-------- Messaggio originale --------Da: Vincent Wolsink @.> Data: 27/11/24  07:48  (GMT+01:00) A: vincentwolsink/home_assistant_micronova_agua_iot @.> Cc: merlino1975 @.>, Author @.> Oggetto: Re: [vincentwolsink/home_assistant_micronova_agua_iot] stove UNICA
NOBIS FIRE not climate ma number (Issue #169)
Btw, wood reserve is a binary sensor so you can just use on or off
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

forgiveness, an observation and a request for explanation. If I may abuse your patience.I have made a routine that if I open the pellet door (the stove gives an AL16 alarm and gives me a minute to load the pellets otherwise the stove turns off) Alexa makes me count down e.g. there are 60 seconds left to load the pellets, or something like that.But when I open the door it doesn't start the routine immediately but after about 10 seconds or more. I don't understand if it's a problem with the entity, if it's a problem with my home assistant server, if I'm doing something wrong in writing the routine. or if it's alexa that's slow.What do you think about itInviato dal mio Galaxy
-------- Messaggio originale --------Da: Vincent Wolsink @.> Data: 27/11/24  07:48  (GMT+01:00) A: vincentwolsink/home_assistant_micronova_agua_iot @.> Cc: merlino1975 @.>, Author @.> Oggetto: Re: [vincentwolsink/home_assistant_micronova_agua_iot] stove UNICA
NOBIS FIRE not climate ma number (Issue #169)
Btw, wood reserve is a binary sensor so you can just use on or off
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

I have searched and searched in every way to find a way to find by myself all the states and attribute names that an entity can have.For example also of all the entities of your work. I still don't understand how to use many of them because I don't know what states or attributes they can take on. Is there a way to figure this out?

Usually you can find this in documentation. Since the states for this integration are dynamic and differ per stove I added them to the extra attributes for you, where applicable.

But when I open the door it doesn't start the routine immediately but after about 10 seconds or more. I don't understand if it's a problem with the entity, if it's a problem with my home assistant server, if I'm doing something wrong in writing the routine.

This integration (just like a majority of the integrations) relies on cloud polling for getting updates. This polling happens every 5 min. Which means worst case there is a 5 min delay between you opening the door and AL16 alarm happening. There is no way to make this faster since this will overload the cloud endpoints.


text:
[Mac] Display Above Full Screen Apps

Thanks for this project! It's a good combination of other solutions I've used that don't quite fit the use case I'm looking for.
One thing I've noticed is that if I'm working in a full screen app, say Firefox, and hit 'Control + E', my focus gets taken to the Desktop space with Geniemoji opened up. Is there a way for Geniemoji to be a modal window on top of full screen apps?

I'll try to implement this in the next week. Btw, you are on MacOS, right?

I have implemented this in v4.0.0, you can download it from the website here 👍

Yep, can confirm this works great now!

authors: tomershvueli virejdasani

repo: virejdasani/Geniemoji


text:
DexArchiveBuilderException using react-native-nyt-360-video

Environment

Development OS: Windows 10 Enterprise Edition (1903 Build18362.295)
Device OS & Version: Android 9
Version: ViroReact 2.16.0, React Native 0.59.3
Device(s): Samsung Galaxy S9 with security patch July 2019

Description
We are facing a DexArchiveBuilderException while starting an Android app using the React Viro plugin. We tried to add the multiDexEnabled true statement on the application gradle and analyzed the application deoendencies without success.
The only way to avoid this error is to remove the react viro plugin from the project.
Reproducible Demo

Dependencies
dependencies {
implementation project(':react-native-background-timer')
implementation project(':react-native-video')
implementation project(':react-native-background-fetch')
implementation project(':react-native-background-geolocation')
implementation project(':react-native-beacons-manager')
implementation project(':react-native-webview')
implementation project(':react-native-calendar-events')
implementation project(':react-native-maps')
implementation project(':react-native-nyt-360-video')
implementation project(':react-native-native-video-player')
implementation project(':react-native-vector-icons')
implementation project(':react-native-i18n')
implementation project(':react-native-device-info')
implementation project(':react-native-config')
implementation project(':react-native-gesture-handler')
implementation project(':react-native-geolocation-service')
implementation fileTree(dir: "libs", include: ["*.jar"])
implementation 'com.android.support:appcompat-v7:28.0.0'
implementation "com.facebook.react:react-native:+" // From node_modules
implementation project(':gvr_common')
implementation project(':arcore_client')
implementation project(path: ':react_viro')
implementation project(path: ':viro_renderer')
implementation 'com.google.android.exoplayer:exoplayer:2.7.1'
implementation 'com.google.protobuf.nano:protobuf-javanano:3.0.0-alpha-7'
implementation 'com.amazonaws:aws-android-sdk-core:2.7.7'
implementation 'com.amazonaws:aws-android-sdk-ddb:2.7.7'
implementation 'com.amazonaws:aws-android-sdk-ddb-mapper:2.7.7'
implementation 'com.amazonaws:aws-android-sdk-cognito:2.7.7'
implementation 'com.amazonaws:aws-android-sdk-cognitoidentityprovider:2.7.7'
}
dependencies.txt

We found that removing the react-native-nyt-360-video plugin the app will start and viro react works as expected.
Any idea?

repo: viromedia/viro


text:
test: add auth to inspect private container image registry

Some container image repo is private, inspecting it needs auth first. This PR addresses this scenario.

/test-rhel95-replace

/test-cs9-anaconda

/test-cs9-dev-bib-image


text:
log support requires CGO

#70 and #69 add log support, but it calls a clib, so now we no longer create a static build, but ref libc and friends
This also makes a releasing a no go, because I will probably have an incompatible libc.
go bc -ldflags="-extldflags=-static"
# github.com/virtual-kubelet/systemk
/usr/bin/ld: /tmp/go-link-075005359/000015.o: in function `_cgo_d744bec0c646_Cfunc_dlopen':
/tmp/go-build/cgo-gcc-prolog:90: warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-075005359/000025.o: in function `mygetgrouplist':
/home/miek/up/go/src/os/user/getgrouplist_unix.go:16: warning: Using 'getgrouplist' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-075005359/000024.o: in function `mygetgrgid_r':
/home/miek/up/go/src/os/user/cgo_lookup_unix.go:38: warning: Using 'getgrgid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-075005359/000024.o: in function `mygetgrnam_r':
/home/miek/up/go/src/os/user/cgo_lookup_unix.go:43: warning: Using 'getgrnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-075005359/000024.o: in function `mygetpwnam_r':
/home/miek/up/go/src/os/user/cgo_lookup_unix.go:33: warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-075005359/000024.o: in function `mygetpwuid_r':
/home/miek/up/go/src/os/user/cgo_lookup_unix.go:28: warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-075005359/000020.o: in function `_cgo_26061493d47f_C2func_getaddrinfo':
/tmp/go-build/cgo-gcc-prolog:58: warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
****

This creates a static bin on my setup.
Another downside of cgo is that per go routines stack is no longer 2k, it's 1M or something

mygetgrgid_r warning (and friends) might actually cause breakage

it does run on debian stable

ok, the dyn. linked binary runs on RH8 - which is good. I'm still going to add the PR to remove this all together, but it seems this usable at this point

For reference, the code as is in main has been validated by me in RHEL7, RHEL8 and Ubuntu 20.04.

authors: miekg pires

repo: virtual-kubelet/systemk


text:
Kibana 5.1.2 not displaying visualization

Testing this plugin on Kibana 5.1.2.
On any of the 3D visualizations, no visualizations are displayed and I get the following error.
TypeError: Cannot read property 'id' of undefined
    at Object.fn (kibana.bundle.js?v=14588:170)
    at Scope.$digest (commons.bundle.js?v=14588:39)
    at Scope.$apply (commons.bundle.js?v=14588:39)
    at done (commons.bundle.js?v=14588:37)
    at completeRequest (commons.bundle.js?v=14588:37)
    at XMLHttpRequest.xhr.onload (commons.bundle.js?v=14588:37)
(anonymous) @ commons.bundle.js?v=14588:38
(anonymous) @ commons.bundle.js?v=14588:37
$digest @ commons.bundle.js?v=14588:39
$apply @ commons.bundle.js?v=14588:39
done @ commons.bundle.js?v=14588:37
completeRequest @ commons.bundle.js?v=14588:37
xhr.onload @ commons.bundle.js?v=14588:37

Any ideas?

Hi,
I have been checking the code and this can only occur when there was a problem retrieving the metric configured. Are you sure you have correctly configured the metrics, and there is any data within the restrictions of buckets and metrics you have made?
Also, try to change to other metrics and buckets to see if any is working. I will check in detail if this problem persists.
Regards,
Vio

@virusu,
Thanks for responding.
I think I figured it out.  The error is not in relation to the chart.  What I found as the problem is that I hadn't added both buckets.  I was just doing count and date histogram so it wasn't built all the way out.

Oh, I see. That makes sense.
I will try to add something not to end the execution unexpectedly in this cases as it is doing now.
Contact me if there are any further issues.
Regards

The same question
Kibana 5.1.2
TypeError: Cannot read property 'id' of undefined
    at Object.fn (kibana.bundle.js?v=8467:173)
    at Scope.$digest (commons.bundle.js?v=8467:39)
    at Scope.$apply (commons.bundle.js?v=8467:39)
    at done (commons.bundle.js?v=8467:37)
    at completeRequest (commons.bundle.js?v=8467:37)
    at XMLHttpRequest.xhr.onload (commons.bundle.js?v=8467:37)


text:
Swagger Ui Custom Css

Is there a possibility to add a custom CSS to Ui?

I don't think there's any good mechanism built into the tool, at least not yet.
It's a little bit of a nuisance, but here's a workaround that should work:

load the entire Swagger UI html as a Stream with ISwashBuckleClient.GetSwaggerUi
read that Stream into a string
do string replacement to inject your custom CSS inline

It would look something like this:
    Stream ui = client.GetSwaggerUi("swagger.json");

    string theHtml = new StreamReader(ui).ReadToEnd();
    string extra = "<style>mycss</style>";
    // TODO: Inject 'extra' into 'theHtml'

    HttpResponseMessage response = new(HttpStatusCode.OK)
    {
        Content = new StringContent(theHtml, Encoding.UTF8, "text/html")
    };

Fixed

authors: Cliabhach SaMirzaei vitalybibikov


text:
Lib mode doesn't export types

Describe the bug
I'm using vitejs to build a react typescript library, I started building it with a plain rollup, but decided to migrate, so I have put everything accordingly. Fixed some bugs, added some packages, but when I export it, it doesn't export the typings (.d.ts) along with the es and umd files, even if I set declarations to true inside of the tsconfig. But it does export successfully both files.
I tried tweaking rollup but to no avail, and also couldn't find anything related to this in the issues or google at all.
Reproduction
Install vite with the "react-ts" template, follow the documentation steps to use lib mode, make a simple component and export it from the output file, and build it.
System Info
Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:
  System:
    OS: Windows 10 10.0.18363
    CPU: (8) x64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
    Memory: 10.24 GB / 15.96 GB
  Binaries:
    Node: 14.3.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.14.0 - D:\programas\laragon\bin\yarn\bin\yarn.CMD
    npm: 5.7.1 - ~\node_modules\.bin\npm.CMD
  Browsers:
    Chrome: 89.0.4389.128
    Edge: Spartan (44.18362.1474.0)
    Internet Explorer: 11.0.18362.1

Used package manager: yarn

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

[ 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 ] Provide a description in this issue that describes the bug.
[ 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.

Have you checked noEmit in tsconfig.json?
https://github.com/vitejs/vite/blob/8dbebeed4c1dd13e13aa7201ad6922d4d4c20368/packages/create-app/template-react-ts/tsconfig.json#L16
This doesn't work together with declaration: true
https://www.typescriptlang.org/tsconfig#noEmit

Just checked, same thing, exported files:

You can use tsc command to generate a single bundled declaration file, like this:
{
    "build:types": "tsc -m amd -t ESNext -d --isolatedModules false  --moduleResolution node --esModuleInterop --jsx react --outFile dist/index.js src/main.ts && rm -rf dist/index.js ",

}

@keelii, but shouldn't vite provide this solution by default since it natively supports typescript?

When vite do this for you, it's not cheap, and if you do it by using tsc, It is truly more natively.
Because even if you use tsc, it's not so fluently. you will need concat to a single d.ts file which is not directly supported will in typescript, you need some tricks to let it work.

Mh seems that it was already requested some time ago #2049
IMO it may make sense to generate declaration files in library mode, cause a published library should serve declarations. That just make the ecosystem a better place.

@Shinigami92, any dates or updates on when this would go to vitejs? That's the only thing that is preventing me from using on my company.

@darklight9811 I don't know if there is currently an open PR, if not please feel free to jump in and create one :slightly_smiling_face:

But even without this in core, this shouldn't prevent you to use it as you can generate the types on the side as was shown in the comments in this issue.

@patak-js, I don't know if I'm doing something wrong, but that command is not working and tweaking it also didn't work for me.

@darklight9811 also tried this? https://github.com/vitejs/vite/issues/2989#issuecomment-819597494

Just tried to use Vite for a serious project at my company and this is preventing me from using it as well. Generating type definitions is something that should be supported by default, especially when the Typescript support in Vite is as good as it is already. Really disappointed that this hasn't been considered as a standard feature so that devs don't have to deal with low-quality workarounds.

@samwightt As I already wrote here: https://github.com/vitejs/vite/issues/2989#issuecomment-825697272
I'm sorry for you that you may have a misunderstanding about how open source works :slightly_frowning_face:
But we give you everything you need to do a PR and nothing stops you from providing this much sought-after feature/fix
Do the world a favor and establish it for the entire community
And in the end, we're grateful for you resolving an issue the community had with Vite
Just assuming something should be supported right away and then being frustrated that it isn't and then doing nothing doesn't help anyone :shrug:

You can use https://github.com/egoist/tsup

I understand the reasoning behind not doing this but I think it should be reconsidered. If Vite did this by default it would be a sort of pit of success that would benefit the broader JS/TS community. If it's not the default and people start using Vite to build libraries I imagine we will have lots of them published without types. That in turn will lead to a lot of issues created and a lot of churn in the community.

@sanjade, I can't get it to work with sass files, any idea how?

@sanjade, I can't get it to work with sass files, any idea how?

What does sass have to do with TypeScript declarations?! Could you explain a bit?

If it's not the default and people start using Vite to build libraries I imagine we will have lots of them published without types.

This. Currently I'm actively discouraging people in my network from using Vite for libraries. Not having this on by default, especially when everything else in library mode just works, will objectively make the JS ecosystem worse. Usage of Typescript is only growing, so it would be good for Vite to be a good citizen and support this by default.
I'm not angry or annoyed that this is not the default, and I'm not expecting any work to be done to get this feature working. I just want to make sure that maintainers understand how big of a deal this feature is, and that not having it is a really glaring oversight when the rest of library mode is as polished as it is.

Closing this issue because it won't be solved anyway and I'm tired of dealing with vite's limitations.

Wait don’t close it. There are tags assigned to this issue. It will be fixed in near future.

Somehow I doubt that

But closing it will only make it worse. The devs won't even know this issue exists. So please reopen it.

@sanjade, they already said they won't do it, and you are free to make a PR that "won't be accepted in the foreseeable future"

@sanjade Do you like to create a feature request issue for this? Then we have a fresh new issue and we can better track it 🙂

Moved to #3461

repo: vitejs/vite


text:
Vite generates multiple copies of the same stylesheet

Describe the bug
I am using the following vite config option to make global styles available in React components without requirement of usage of "@import '../../syles/main" in each component file:
css: {
    preprocessorOptions: {
      scss: {
        additionalData: `
          @import "./src/styles/main";
        `
      }
    }
  }

it comes from https://github.com/vitejs/vite/issues/832
My main.scss looks like:
@import "./node_modules/normalize.css/normalize";

@import 'fonts';
@import 'colors';
@import 'breakpoints';
@import 'animations';
@import 'layers';

where fonts, colors, breakpoints, animations, layers include global variables.
It works fine in part I can use my variables inside component without importing the main SCSS file, but such approach causes an issue that I have multiple copies of the same stylesheet in a head section of page ( see the screenshot: https://imgur.com/a/k6hGnbP )
Reproduction

Create empty app (Vite, React, TSX)
Create a global main.scss file
Import partials _colors.scss and _fonts.scss to main.scss using @import
Create vite.config.js with option similar to described in a bug description section
Create at least two different components and add it to your App
Add some variables to colors.scss and fonts.scss
Use variables from colors.scss and fonts.scss in your two components from step 5 using build-in CSS modules support ([component].module.scss)
Run your app and look at head section

Expected result:
There is only one global stylesheet.
Actual result:
There are multiple copies of global stylesheet, where number of copies equals number of unique components,
UPDATE:
I've created a simplified app which one reproduces the issue:
https://github.com/tastytea-github/vite-global-import-issue-reproduction

Clone repo
Install deps with npm i
Run app with npm run dev
Look at head section of the rendered page in devtools

Expected state:
styles from main.scss are added globally only once.
Actual state:
styles from main.scss are included to each unique component.
System Info
No

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.

This may help with this issue:
vite/src/client/client.ts
Is this intended?
const supportsConstructedSheet = (() => {
  try {
    // new CSSStyleSheet()
    // return true
  } catch (e) {}
  return false
})()

Seems that
if (!style) {
     style = document.createElement('style')
     style.setAttribute('type', 'text/css')
     style.innerHTML = content
     document.head.appendChild(style)

in updateStyle is always triggered for some reason.

@akrabdev

Is this intended?
Intended to what? Sorry, I didn't get what you meant. I assume the code is commented because it refers to https://wicg.github.io/construct-stylesheets/ which one is still in "A Collection of Interesting Ideas".

in updateStyle is always triggered for some reason.
Sounds truly, but I currently have no idea why.

Please look at simplified repository I've created to see the issue reproduction (look at UPDATE in the issue description).

@sodatea Relating to added feat-css tag, I want to emphasize this issue is a bug, but not a feature, because currently Vite produces duplicated CSS in a bundle.

feat: css means the issue is related to the CSS bundling feature of Vite. It's not indicating that it is a feature request.

Hey guys, running into the same issue, which causes somewhat reduced performance for us. Hope to see a solution or explanation soon!

Any updates on this issue?

@patak-js Hello sir. Could you be so kind to pay attention to this issue?

This is a pretty huge issue. I tried building my project, and noticed that the compiled index.css file is enormous (over 1 MB) despite me only writing a few KB worth of CSS code. If you manually inspect the generated .css files, there are a lot of repeated CSS code.

This is a pretty huge issue. I tried building my project, and noticed that the compiled index.css file is enormous (over 1 MB) despite me only writing a few KB worth of CSS code. If you manually inspect the generated .css files, there are a lot of repeated CSS code.
EDIT: Currently using a workaround where I just import my global SCSS file in the top-most component of my project. In the case of Vue, it's the App.vue file:
<style lang="scss">   // Do not include the "scoped" attribute to allow the rules to propagate to the nested components.
@import "@/css/universal/universal.scss";
</style>

What's about autocomplete in files which utilize this global SCSS?

Any update on this issue?

bump

I'm having the issue with vite-plugin-ssr. I'm building a page with preact-client-routing example as startpoint.
The issue exists inside this untouched repo. Just clone and try.
If running npm run dev  the import './PageShell.css' inside PageShell.jsx is injected as stylesheet and additionally as <style /> tag in the head. You also see the styles always two times inside the styles inspector.

If running npm run build and npm run server:prod it is injected twice as stylesheet, here _default.page.client.jsx.2942c7fb.css.

I don't know if this is maybe related to vite-plugin-ssr.

Will check it in production build. It seems duplication of styles in dev mode is ok since Vite uses HMR. If production build doesn't generate duplicated styles, then is it enough.

This is how sass works. It is not a good choice to import files which include styles with additionalData since it leads to duplicated styles.
additionalData is prepended to every scss file which is imported from js.
Some related urls:

https://stackoverflow.com/questions/24182734/how-to-avoid-duplication-of-styles-in-scss
https://github.com/webpack-contrib/sass-loader/issues/145
https://github.com/vuejs/vue-loader/issues/110
https://sass-lang.com/blog/the-module-system-is-launched

@sapphi-red additionalData does prepend, but @use should reuse style if it is already in head.

Sorry my comment was wrong in some parts.
For the following reason,  it is not a good choice to import files which include styles with additionalData since it leads to duplicated styles.

Vite processes each css import (including sass/scss) indivisually. This is the same behavior with webpack.
additionalData is prepended to every scss file which is imported from js.

For example, if you set @use 'foo.scss' to additionalData and the follwing files exists.
// foo.scss
.foo { color: red; }

// bar.scss
.bar { color: green; }

// baz.scss
.baz { color: blue; }

// main.js
@import './bar.scss'
@import './baz.scss'

bar.scss becomes like below.
.foo { color: red; }
.bar { color: green; }

baz.scss becomes like below.
.foo { color: red; }
.baz { color: blue; }

So the final bundled css becomes like below.
.foo { color: red; }
.bar { color: green; }
.foo { color: red; }
.baz { color: blue; }

If all the scss is bundled at once, it could be deduped. But that is not possible to do during dev and also makes css splitting hard.

For the following reason, it is not a good choice to import files which include styles with additionalData since it leads to duplicated styles.
* Vite processes each css import (including sass/scss) indivisually. This is the same behavior with webpack.

* `additionalData` is prepended to **every** scss file which is imported from js.

I might be misinterpreting what you've said here, but for me with my development builds, I'm not using additionalData at all and am running into the issue of multiple copies of the same stylesheet being generated.

It will happen by the same reason for an example like below.
/* foo.css */
.foo { color: red; }

/* bar.css */
@import './foo.css'
.bar { color: green; }

/* baz.css */
@import './foo.css'
.baz { color: blue; }

// main.js
import './bar.css'
import './baz.css'

Will check it in production build. It seems duplication of styles in dev mode is ok since Vite uses HMR. If production build doesn't generate duplicated styles, then is it enough.

When I vite build instead of vite preview, the output CSS still has duplicate content.
@tastytea-github, did you experience the same?

running into this issue on the newer versions as well

please have a look at my answer to this (same) issue: https://github.com/nuxt/framework/discussions/8139#discussioncomment-3864265
TL;DR
Don't include scss files with actual css-rules via additionalData. Only files that include variables, mixins, etc.
Working example: https://stackblitz.com/edit/github-hq9bhi?file=app.vue

@dsvgl how i can add global css rules then?

I’m surprised this hasn’t been fixed yet

Here's what I've come up with:
const stripScssMarker = '/* STYLES STRIP IMPORTS MARKER */'

export default {
css: {
        preprocessorOptions: {
          scss: {
            additionalData: `@import "${projectRootDir}/shared_styles";${stripScssMarker}`
          }
        }
      },
plugins: [
{
          name: 'vite-plugin-strip-css',
          transform(src: string, id) {
            if (id.endsWith('.vue') && !id.includes('node_modules') && src.includes('@extend')) {
              console.warn(
                'You are using @extend in your component. This is likely not working in your styles. Please use mixins instead.',
                id.replace(`${projectRootDir}/`, '')
              )
            }
            if (id.includes('lang.scss')) {
              const split = src.split(stripScssMarker)
              const newSrc = split[split.length - 1]

              return {
                code: newSrc,
                map: null
              }
            }
          }
        }]
}

Just needs an additional import of the style file from index.html. I had to create a shared_styles_proxy.scss file which imports the shared_styles.scss because otherwise vite would tell me shared_style.scss was already imported.
The downside is that code that modifies the shared style doesn't work like this. We had to get rid of all @extend usages in our codebase, which luckily were only a few.
Hope this helps.

bump

up

Is this issue not fixable..?

Is this issue not fixable..?

It would be incredibly hard to fix it in a generic way, see my answer for a workaround that is applicable in certain circumstances (if you don't use @extend).

@dschmidt Yes I used your workaround. It works perfectly fine. 💘 Thanks.
I was facing an issue that was also removing other imports ( google fonts etc.. ) which I fixed by excluding my main file (which also had the fonts imports) from this replacement.

I am using vite with react.

const SPLIT_CSS_MARK = '/* ##SPLIT_CSS_MARK## */'
export default ({ command }) => {
  return defineConfig({
    ...
    plugins: [
      ...
      {
        // ⚙ custom plugin to remove duplicated css caused by css.preprocessorOptions.scss.additionalData
        name: 'vite-plugin-strip-css',
        transform(src: string, id) {
          if (id.includes('scss')) {
            if (id.includes('src/index.scss')) {
              // Keep the common file only in root css file
              return { code: src, map: null }
            }

            const split = src.split(SPLIT_CSS_MARK)
            const newSrc = split[split.length - 1]
            return { code: newSrc, map: null }
          }
        },
      },
    ],
    css: {
      preprocessorOptions: {
        scss: {
          additionalData:
            `@use "./src/styles/common.scss" as *;` + SPLIT_CSS_MARK,
        },
      },
    },
  })
}

authors: Alihd1 MrFoxPro RohitKaushal7 akrabdev cwe-spb dschmidt dsvgl jaydiazzz jpengelbrecht jrson83 mikeplus64 phasetri samarth-math sapphi-red sodatea tastytea-github wesleyboar


text:
fix: modulePreload false

Fixes #10773
Description
We currently share the same preload helper for injecting CSS stylesheets of dynamic imports. Even when modulePreload is set to false, we still need the preload import helper and preserve the CSS styles for the dynamically imported module.
We already had a test case for modulePreload: false, but one of the checks was wrong.
This fix isn't ideal, users that set modulePreload false would probably expect the import helper to be avoided. But at least the behavior is correct after this PR.
Related issue:

https://github.com/vitejs/vite/issues/13952

#13952 one isn't easy to solve as we need import.meta.url in the transform hook, and populate the deps for the dynamic import in generateBundle. If we don't find a good way to find if the preload helper is needed at transform time, maybe we could at least reduce the helper that is quite verbose now with no deps and then replace it back in generateBundle (even if we leave some white space to avoid messing with sourcemaps).

What is the purpose of this pull request?

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

Agreed. Not directly related, but the way we handle preloads may also get in the way to stabilize renderBuiltUrl. See https://github.com/vitejs/vite/discussions/13834#discussioncomment-6591530. I also don't know how to properly fix that one though if we need to wait until generateBundle. We could try add something to augmentChunkHash, using dynamicImports to precalculate all the URLs we'll need to inject in the marker.

/ecosystem-ci run

Same CI fails as in main, merging


text:
refactor: normalize publicDir when resolving config

Description
https://github.com/vitejs/vite/pull/15318#discussion_r1423607117
Additional context

What is the purpose of this pull request?

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

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

[x] Read the Contributing Guidelines, especially the Pull Request Guidelines.
[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] Update the corresponding documentation if needed.
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

/ecosystem-ci run

authors: patak-dev sapphi-red


text:
'No test found in suite' failure with passWithNoTests enabled

Describe the bug

I have a test suite with no tests, similar to

describe('My feature', () => {
  describe('my test suite', () => {
    // no tests here
  });
});

I am testing with passWithNoTests enabled (full command is vitest run --passWithNoTests --logHeapUsage)

My test suite fails:

 FAIL  tests/suite.test.ts > My feature > my test suite
Error: No test found in suite my test suite

I expected the test suite to pass.

I might be able to open a PR if you agree this should be changed.
Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-dubrh2?file=test%2Fsuite.test.ts
System Info
System:
    OS: Linux 5.15 Ubuntu 20.04.6 LTS (Focal Fossa)
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-1235U
    Memory: 2.16 GB / 7.62 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node
    npm: 9.5.1 - ~/.nvm/versions/node/v18.16.0/bin/npm
  npmPackages:
    @vitest/coverage-v8: ^0.33.0 => 0.33.0
    vitest: ^0.33.0 => 0.33.0

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.

This is intended behavior. All test files should contain at least one test.
This option just makes it so your tests don't fails if there are no test files matching filters.

authors: alexbostock sheremet-va

repo: vitest-dev/vitest


text:
exclude filter should not consider absolute path

Describe the bug
In our private CI system, all projects will be put into $HOME/.cache/projects when cloning repositories. However, Vitest's default exclude filter will ignore all the files whose paths contains .cache . This sounds OK when there're some directories called .cache in current working directory. But for us, $HOME/.cache isn't not a directory under current working directory.
When researching the logic of Vitest, I found that the absolute option of fast-glob was set to true, so all the test files (e.g. $HOME/.cache/projects/example.test.ts) will match that exclude filter, which causes Vitest exits with No test files found error.
Here is the absolute option: https://github.com/vitest-dev/vitest/blob/8693449b412743f20a63fd9bfa1a9054aa74613f/packages/vitest/src/node/workspace.ts#L140
I know we can change our Vitest config to let Vitest not ignore the paths contain .cache, but I'm still curious why the absolute option was enabled. In my opinion, both include and exclude options should only be considered under current working directory with relative path, not absolute path.
Reproduction
This issue can't be simulated with online sandbox or a reproduction repo, but this issue can be reproduced by moving a project to a directory called .cache. You can simply create a directory called .cache and move into it.
System Info
System: Linux
Vitest version: v0.33.0

Used Package Manager
pnpm
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.

ping @sheremet-va @patak-dev @antfu


text:
w2layout.onShow isn't firing?

hello vitman,
sorry to trouble you again but i don't appear to be able to get w2layout.onShow to fire with either an onShow object property or by using the after-object-creation method, as per:
http://w2ui.com/web/docs/w2layout.onShow
is something broken with it atm?
edit: some more information:
i'm showing the layout using w2layout.content after the page has been loaded, triggered by the user clicking a button.

onShow only fires if you use layout.show(...) and layout.hide(...) methods. It is not effected by layout.content(...)

vman, i don't mean to be a pain, but i think the fundamental problem is there isn't a callback option for parent.content()
in essence i was just hoping to be able to keep many child layouts loaded and swap them in/out of a parent layout without having to resort to parent.load() in order to reload/repopulate the child layouts.
but i'll try and hack a workaround, so you may close this again!

update: ok i worked around this by using a setTimeout immediately after calling parent.content()

I have content loaded with angular via async request, and I want to attach behavior to an element inside it's content. How can I know when element is created, meaning when content has been rendered inside panel?
Thanks
$('#layout').w2layout({
                name: 'name',
                panels: [
                    {
                        type: 'top',
                        hidden: false,
                        resizeable: false,
                        content: $compile('

')($scope),
                        size: 32,
                        ...
                        }
                    },
});

authors: dzona tristenator vitmalina


text:
w2grid - horizontal scrollbar broken on { fixedBody: false } grids

Thanks for w2ui the grid is a excellent and more full featured than many others I've tried including ng-grid / ui-grid, extjs grids, and jqxGrid.
I'm having trouble with the horizontal scrollbar though. It appears that the horizontal scrollbar isn't rendered with { fixedBody: false } grids.
See example here:
See http://jsfiddle.net/ilancopelyn/q18dq8ja/2/
Thanks.

This was 1.4.x issue. In current master it is fine. I have fixed it in 1.4 branch and recompiled latest code. Download: https://raw.githubusercontent.com/vitmalina/w2ui/w2ui-1.4/dist/w2ui.js or https://raw.githubusercontent.com/vitmalina/w2ui/w2ui-1.4/dist/w2ui.min.js and all will be good

Thanks for that. Is there a way to include extra space so that the horizontal scrollbar doesn't obscure the bottom-most row? I hacked it like this: line 5582:
var calculatedHeight = w2utils.getSize(columns, 'height')
                    + w2utils.getSize($('#grid_' + obj.name + '_records table'), 'height')
                    + 16; // HACK - additional vertical space for horizontal scrollbar

Actually please ignore. I've upgraded to 1.5.x (nightly) where I see you've fixed this issue. Thanks

I am glad it is working in 1.5.x. Also please note that frozen columns are in1.5.x too. I will look into the issue with 1.4.2 and will try to fix it.

authors: ilanc vitmalina


text:
Password reset and username reminder

I signed up for the demo instance of trybootcamp early on. I can no longer log in due to forgotten username and/or password. I can no longer register with my email address due to the existing user record.
A basic facility to reset password and/or remind of username to configured email address would be helpful.
@gissues:{"order":75,"status":"notstarted"}

On this, I would suggest an improvement on the user management implementation going for django-allauth, which implements all those functionalities.

Closing it. This issue has been referenced in other issues, also this requirement is part of a broader functionality also mentioned on #53 and #66.

authors: jfkw sebastian-code

repo: vitorfs/bootcamp


text:
Support multiline database view queries

Closes #292

@mqus Would you mind reviewing?

I'd be happy to review! Can you send me an invite? mqus at disroot dot org

authors: mqus vitusortner

repo: vitusortner/floor


text:
Use more specific don/ka types when writing to fumen (ド, コ, ドン, カッ, カ)

Since TJA files use only a single number to represent dons and kas (1 and 2 respectively), I have only been writing a single type of don/ka to the converted .bin file.
However, official fumens actually have 3 types of dons and 2 types of kas. And, different types will be used depending on how the dons and kas are grouped together:

Theoretically, my converter could track if a note is part of a triplet/quad/etc. and write the different notes accordingly. But, it might be quite tricky to programmatically detect groupings of notes.
Maybe what I could do is track "time since last note". If the time decreases (i.e. notes are closer together), we enter a "grouping". If the time stays the same, then we're still within the grouping. If the time increases (i.e. notes are further apart), we have exited the grouping. But, I don't know how foolproof that is if we consider BPMCHANGE commands, etc. 🤔

I assume that the logic goes like this:

Single notes just use ド (do) and カ (ka)
Groupings of 2 or more will always end on ドン (don) and カッ (ka~tsu)
If there are multiple don notes in a row in a grouping, they'll alternate between ド (do) and コ (ko)

For example:

DD -> ドドン -> Do-don
DDD -> ドコドン -> Do-ko-don
DDDDD -> ドコドコドン -> Do-ko-do-ko-don
DDDDK -> ドコドコカッ -> Do-ko-do-ko-katsu
KDK -> Is this カドカッ (Ka-do-katsu) or カドカッ (Ka-ko-katsu)? Presumably the former, right?

Groupings seem to include any set of notes with identical durations between them, e.g.:

(Note the katsu at the end, even when notes are spaced out)

I will have to be quite careful when keeping track of note groupings (tracking between-measure groupings, making sure to properly identify when a grouping ends, etc.).

It looks like there are a handful of approaches for clustering in 1D (see this SO answer). Many of them are using numpy / scipy, though. So, ideally, I would be able to implement something in pure Python?
I do think that the 1D clustering problem here is quite a bit simpler than the cases described on SO:

All of the ms timings of the notes are A) linear and B) unique
The spacing between ms timings is predictable and consistent
The smallest spacings (48th notes, 24th notes, 16th notes, 8th notes, etc.) are pretty much guaranteed to be grouped.

So, maybe I can come up with some sort of simplified algorithm to group the notes, given some assumptions.