id
stringlengths 4
10
| text
stringlengths 4
2.14M
| source
stringclasses 2
values | created
timestamp[s]date 2001-05-16 21:05:09
2025-01-01 03:38:30
| added
stringdate 2025-04-01 04:05:38
2025-04-01 07:14:06
| metadata
dict |
|---|---|---|---|---|---|
629215506
|
Create CODE_OF_CONDUCT.md.
Reverts v-shyase/oss-enterprise#5
Create CODE_OF_CONDUCT.md.
|
gharchive/pull-request
| 2020-06-02T13:44:11 |
2025-04-01T04:36:11.632737
|
{
"authors": [
"v-shyase"
],
"repo": "v-shyase/oss-enterprise",
"url": "https://github.com/v-shyase/oss-enterprise/pull/6",
"license": "CC-BY-4.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1570147460
|
[Feature request] Please support new protocols (❤️) we really need your help
Hello, good time, thanks to the creators of the powerful and excellent v2board script,
I and a group of v2board users are asking you and other friends who have the ability to do this, please support the latest and more advanced protocols such as (vless+xtls-rprx-vision / vless+xtls+http / trojan+ws & ... )
we really need them. We need it, in some countries connection problems have increased and GFw has become very powerful, old protocols no longer work properly.
Please help us, we have been waiting for this for a long time, thank you very much in advance .
Good luck to you dear ones .
If you're patient enough, you can wait for me for a few more months and I'll probably make a patch and sideload panel to get trojan with xtls supported
thank you.wait for you.
The butterfly said to the bear: I love you
The bear said: I want to sleep now, okay wake up, we will talk
The bear went into hibernation and never realized that the life of the butterfly is only 3 days
😀😍😁
Is there a new update coming?
thank you so much
Is there a new update coming?
Yes, we've already supported VLESS and XTLS(Aka VLESS flow)
Please read https://github.com/lotusproxy/lotusboard-docker/wiki/How-to-use-VLESS-and-XTLS
thank you so much
As for tcp + http configuration, how can I fill in the host value?
Could you please send the config template?
Please click on 编辑配置 ( which is a blue text on the top of TCP(transport selector)
thank you so much
Is there a new update coming?
Yes, we've already supported VLESS and XTLS(Aka VLESS flow)
Please read https://github.com/lotusproxy/lotusboard-docker/wiki/How-to-use-VLESS-and-XTLS
thank you so much
As for tcp + http configuration, how can I fill in the host value?
Could you please send the config template?
Please click on 编辑配置 ( which is a blue text on the top of TCP(transport selector)
{
"header": {
"type": "http",
"request": {},
"response": {}
}
}
I am using the basic configuration configuration, but the request host value is not automatically added for the user. Do you have a solution for it?
thank you so much
Is there a new update coming?
Yes, we've already supported VLESS and XTLS(Aka VLESS flow)
Please read https://github.com/lotusproxy/lotusboard-docker/wiki/How-to-use-VLESS-and-XTLS
thank you so much
As for tcp + http configuration, how can I fill in the host value?
Could you please send the config template?
Please click on 编辑配置 ( which is a blue text on the top of TCP(transport selector)
{
"header": {
"type": "http",
"request": {},
"response": {}
}
}
I am using the basic configuration configuration, but the request host value is not automatically added for the user. Do you have a solution for it?
Will push fix tomorrow
Hello
Has this problem been resolved?
thank you so much
Is there a new update coming?
Yes, we've already supported VLESS and XTLS(Aka VLESS flow)
Please read https://github.com/lotusproxy/lotusboard-docker/wiki/How-to-use-VLESS-and-XTLS
thank you so much
As for tcp + http configuration, how can I fill in the host value?
Could you please send the config template?
Please click on 编辑配置 ( which is a blue text on the top of TCP(transport selector)
{
"header": {
"type": "http",
"request": {},
"response": {}
}
}
I am using the basic configuration configuration, but the request host value is not automatically added for the user. Do you have a solution for it?
Will push fix tomorrow
Hello
Has this problem been resolved?
Sorry I forgot, will do tomorrow, btw today I fixed ss2022 in SIP008
thank you so much
Is there a new update coming?
Yes, we've already supported VLESS and XTLS(Aka VLESS flow)
Please read https://github.com/lotusproxy/lotusboard-docker/wiki/How-to-use-VLESS-and-XTLS
thank you so much
As for tcp + http configuration, how can I fill in the host value?
Could you please send the config template?
Please click on 编辑配置 ( which is a blue text on the top of TCP(transport selector)
{
"header": {
"type": "http",
"request": {},
"response": {}
}
}
I am using the basic configuration configuration, but the request host value is not automatically added for the user. Do you have a solution for it?
Will push fix tomorrow
Hello
Has this problem been resolved?
Sorry I forgot, will do tomorrow, btw today I fixed ss2022 in SIP008
Btw I don't suggest you do this, if you want to have cheaper internet, please use websocket transport
Inside Iran, this method works better
داداش یه راهنمایی میکنی تو فیلدها چی باید نوشت؟
داداش یه راهنمایی میکنی به جای این فیلدها چی باید نوشت؟
{
"header": {
"type": "http",
"request": {},
"response": {}
}
}
تو ریکوست و ریسپانس ؟
داداش یه راهنمایی میکنی به جای این فیلدها چی باید نوشت؟
{ "header": { "type": "http", "request": {}, "response": {} } }
تو ریکوست و ریسپانس ؟
xtls.github.io
thank you so much
Is there a new update coming?
Yes, we've already supported VLESS and XTLS(Aka VLESS flow)
Please read https://github.com/lotusproxy/lotusboard-docker/wiki/How-to-use-VLESS-and-XTLS
thank you so much
As for tcp + http configuration, how can I fill in the host value?
Could you please send the config template?
Please click on 编辑配置 ( which is a blue text on the top of TCP(transport selector)
{
"header": {
"type": "http",
"request": {},
"response": {}
}
}
I am using the basic configuration configuration, but the request host value is not automatically added for the user. Do you have a solution for it?
Will push fix tomorrow
Hello
Has this problem been resolved?
Sorry I forgot, will do tomorrow, btw today I fixed ss2022 in SIP008
Btw I don't suggest you do this, if you want to have cheaper internet, please use websocket transport
Inside Iran, this method works better
if ((string)$server['network'] === 'tcp') { $tcpSettings = $server['networkSettings']; if (isset($tcpSettings['header']['type'])) $config['type'] = $tcpSettings['header']['type']; if (isset($tcpSettings['header']['request']['path'][0])) $config['path'] = $tcpSettings['header']['request']['path'][0]; }
Why it's already supported? You need which part?
thank you so much
Is there a new update coming?
Yes, we've already supported VLESS and XTLS(Aka VLESS flow)
Please read https://github.com/lotusproxy/lotusboard-docker/wiki/How-to-use-VLESS-and-XTLS
thank you so much
As for tcp + http configuration, how can I fill in the host value?
Could you please send the config template?
Please click on 编辑配置 ( which is a blue text on the top of TCP(transport selector)
{
"header": {
"type": "http",
"request": {},
"response": {}
}
}
I am using the basic configuration configuration, but the request host value is not automatically added for the user. Do you have a solution for it?
Will push fix tomorrow
Hello
Has this problem been resolved?
Sorry I forgot, will do tomorrow, btw today I fixed ss2022 in SIP008
Btw I don't suggest you do this, if you want to have cheaper internet, please use websocket transport
Inside Iran, this method works better
if ((string)$server['network'] === 'tcp') { $tcpSettings = $server['networkSettings']; if (isset($tcpSettings['header']['type'])) $config['type'] = $tcpSettings['header']['type']; if (isset($tcpSettings['header']['request']['path'][0])) $config['path'] = $tcpSettings['header']['request']['path'][0]; }
Why it's already supported? You need which part?
对接vmess+tcp+http
原生V2board不支持tcp+http订阅下发，请自行寻找解决方法，或手动配置客户端文件。
在对接vmess+tcp+http时，v2board需要在传输协议配置中增加如下内容：
{
"header": {
"type": "http",
"request": {},
"response": {}
}
}
其中request和response中的内容请自行参照Xray-core文档设置。
Link XrayR : https://xrayr-project.github.io/XrayR-doc/dui-jie-v2board/v2board.html
I am implementing according to this command, the problem I have is that the value of request host is not automatically added for the client and I have to change the configuration manually. Is there a solution to automatically fill this value of request host?
Am I doing the configuration wrong?
Am I doing the configuration wrong?
Ah, I'll add that to neo-main later
Done, please switch to neo-main branch to test and test me if it's working
Done, please switch to neo-main branch to test and tell me if it's working
I can't find it, can you send the link? Thankful
Done, please switch to neo-main branch to test and tell me if it's working
I can't find it, can you send the link? Thankful
.gitsubmodule at root of lotusboard-docker
|
gharchive/issue
| 2023-02-03T16:57:57 |
2025-04-01T04:36:11.673678
|
{
"authors": [
"Mjeir",
"MrVb0",
"hodaslo",
"lotusproxy",
"okoklai"
],
"repo": "v2board/v2board",
"url": "https://github.com/v2board/v2board/issues/666",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1313283371
|
Feat: Change ALPN and default port of DNS over QUIC for rfc9250
#1834
Codecov Report
Merging #1878 (ca88ca0) into master (70e5eee) will decrease coverage by 0.11%.
The diff coverage is 100.00%.
@@ Coverage Diff @@
## master #1878 +/- ##
==========================================
- Coverage 38.82% 38.71% -0.12%
==========================================
Files 616 608 -8
Lines 36298 36160 -138
==========================================
- Hits 14094 14000 -94
+ Misses 20626 20592 -34
+ Partials 1578 1568 -10
Impacted Files
Coverage Δ
app/dns/nameserver_quic.go
72.64% <100.00%> (ø)
app/proxyman/outbound/errors.generated.go
0.00% <0.00%> (-100.00%)
:arrow_down:
common/task/task.go
88.88% <0.00%> (-7.41%)
:arrow_down:
testing/servers/tcp/tcp.go
81.81% <0.00%> (-5.46%)
:arrow_down:
testing/scenarios/common.go
75.00% <0.00%> (-4.29%)
:arrow_down:
app/proxyman/outbound/handler.go
36.61% <0.00%> (-4.23%)
:arrow_down:
transport/internet/udp/hub.go
73.61% <0.00%> (-4.17%)
:arrow_down:
transport/internet/system_listener.go
48.07% <0.00%> (-3.85%)
:arrow_down:
transport/internet/system_dialer.go
46.98% <0.00%> (-2.41%)
:arrow_down:
transport/internet/kcp/connection.go
69.61% <0.00%> (-2.21%)
:arrow_down:
... and 11 more
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 70e5eee...ca88ca0. Read the comment docs.
|
gharchive/pull-request
| 2022-07-21T13:42:25 |
2025-04-01T04:36:11.689565
|
{
"authors": [
"AkinoKaede",
"codecov-commenter"
],
"repo": "v2fly/v2ray-core",
"url": "https://github.com/v2fly/v2ray-core/pull/1878",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
120795849
|
Grid tooltip overlaps with menu
If the grid-row where I right-click has a tooltip, the tooltip is opened on top of the menu.
To get rid of the tooltip I have to move the mouse out of the menu, move it around a bit and then back.
It seems the menu has z-index 20000, and the tooltip has 20001
Hi, I'm facing the same issue. How to avoid it ? Have you find a solution ?
Thank you for your help.
The problem is still there.
When I test, I see that any tooltip that is open before I right-click is closed.
But if I move the mouse to the row and right-click before the tooltip is opened, I get the tooltip on top of the menu.
This is with Vaadin 7.6.7 and vaadin-context-menu 0.7.1
I get the same result with Vaadin 7.6.8 and vaadin-context-menu 0.7.4
Add following workaround to grid :
addItemClickListener(new ItemClickEvent.ItemClickListener() {
@Override
public void itemClick(ItemClickEvent event) {
if (event.getButton() == MouseEventDetails.MouseButton.RIGHT) {
removeAllActionHandlers();
JavaScript.getCurrent().execute("hideTooltip()");
for (Action.Handler actionHandler : getActionHandlers()) {
addActionHandler(actionHandler);
}
}
}
});
and implement in JS function hiding tooltip logic.
|
gharchive/issue
| 2015-12-07T15:17:14 |
2025-04-01T04:36:11.721926
|
{
"authors": [
"guttormvik",
"igolovan81",
"zealucard"
],
"repo": "vaadin/context-menu",
"url": "https://github.com/vaadin/context-menu/issues/7",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
180876634
|
Feature/keyboard input
Fixes #238, Fixes #248
This change is
Reviewed 15 of 16 files at r1.
Review status: 15 of 16 files reviewed at latest revision, 8 unresolved discussions.
vaadin-date-picker-behavior.html, line 15 at r1 (raw file):
'_selectedDateChanged(_selectedDate, i18n.formatDate)',
'_validateInput(_selectedDate, _minDate, _maxDate)',
'_focusedDateChanged(_focusedDate)'
Not sure, but should _ignoreFocusedDateChange be added to the _focusedDateChanged observer?
vaadin-date-picker-behavior.html, line 301 at r1 (raw file):
this.value = this._formatISO(selectedDate);
this._focusedDate = selectedDate;
this._cachedInputValue = this._inputValue = selectedDate ? this.i18n.formatDate(selectedDate) : '';
Should _cachedInputValue be added to the properties list?
demo/advanced.html, line 35 at r1 (raw file):
var datepicker = document.querySelector('vaadin-date-picker#finnish');
datepicker.i18n = {
Probably needs to be wrapped inside WebComponentsReady event. Breaks demo on IE11.
demo/index.html, line 106 at r1 (raw file):
</vaadin-date-picker>
<script>
var datepicker = document.querySelector('vaadin-date-picker#keyboard-input');
Needs to be wrapped inside WebComponentsReady event. Breaks demo on IE11.
docs/vaadin-date-picker-localization.adoc, line 88 at r1 (raw file):
},
parseDate: function(s) {
return moment(s, moment.localeData().longDateFormat('L')).toDate();
In demos we are using Sugar and in docs moment. Can these be unified?
docs/vaadin-date-picker-value.adoc, line 11 at r1 (raw file):
The user can select a date easiest by clicking or tapping on it on the dropdown overlay.
A date can also be selected with keyboard only either by typing the value to the input field or using arrow keys for focusing the desired date on the dropdown overlay and selecting it with space/enter.
I'd remove only word
test/form-input.html, line 190 at r1 (raw file):
});
it('should validate keyboard input (valid)', function(done) {
Can you add a test for validating a keyboard input when min/max property has been used?
test/keyboard-input.html, line 22 at r1 (raw file):
<script>
var isAndroid = /(android)/i.test(navigator.userAgent);
Can this variable be moved to common.js?
Comments from Reviewable
Review status: 12 of 17 files reviewed at latest revision, 8 unresolved discussions.
vaadin-date-picker-behavior.html, line 15 at r1 (raw file):
Previously, samiheikki (Sami Suo-Heikki) wrote…
> Not sure, but should `_ignoreFocusedDateChange` be added to the `_focusedDateChanged` observer?
Hmm..maybe not. We don't want the function to invoke until _focusedDate changes
vaadin-date-picker-behavior.html, line 301 at r1 (raw file):
Previously, samiheikki (Sami Suo-Heikki) wrote…
> Should `_cachedInputValue` be added to the properties list?
Done.
demo/advanced.html, line 35 at r1 (raw file):
Previously, samiheikki (Sami Suo-Heikki) wrote…
> Probably needs to be wrapped inside `WebComponentsReady` event. Breaks demo on IE11.
Shouldn't be needed. This demo works fine on IE11 at https://cdn.vaadin.com/vaadin-elements/latest/vaadin-date-picker/demo/advanced.html Some dependency is breaking the demos on IE11 but it doesn't relate to this PR (same issues in master). Must be fixed though.
demo/index.html, line 106 at r1 (raw file):
Previously, samiheikki (Sami Suo-Heikki) wrote…
> Needs to be wrapped inside `WebComponentsReady` event. Breaks demo on IE11.
Wrapping doesn't seem to help in this case. Some dependency is breaking the demos on IE11 but it doesn't relate to this PR (same issues in master). Must be fixed though.
docs/vaadin-date-picker-localization.adoc, line 88 at r1 (raw file):
Previously, samiheikki (Sami Suo-Heikki) wrote…
> In demos we are using Sugar and in docs moment. Can these be unified?
Sugar understands constructs like "20 days after tomorrow" which is nice and flashy for demos.
Our documentation on the other hand uses moment (which is also more well known) features (that aren't there in Sugar) for localization example so we'll need to stick to that.
docs/vaadin-date-picker-value.adoc, line 11 at r1 (raw file):
Previously, samiheikki (Sami Suo-Heikki) wrote…
> I'd remove `only` word
Done.
test/form-input.html, line 190 at r1 (raw file):
Previously, samiheikki (Sami Suo-Heikki) wrote…
> Can you add a test for validating a keyboard input when min/max property has been used?
Done.
test/keyboard-input.html, line 22 at r1 (raw file):
Previously, samiheikki (Sami Suo-Heikki) wrote…
> Can this variable be moved to common.js?
Done.
Comments from Reviewable
Review status: 12 of 17 files reviewed at latest revision, 10 unresolved discussions.
vaadin-date-picker-behavior.html, line 171 at r1 (raw file):
parseDate: function(text) {
var parts = text.split('/');
if (parts.length === 3) {
This works significantly different from the Sugar parser in the sense that it only works for all the three parts, while Sugar can take even a single number.
It also makes the date picker to only react on typing when the full date is entered. This might confuse users to think that the keyboard input is not supported at all.
Maybe allow day and month/day as well?
vaadin-date-picker-behavior.html, line 173 at r1 (raw file):
if (parts.length === 3) {
var date = new Date(0, 0);
date.setFullYear(parseInt(parts[2], 10));
Any number is treated as a full year here, even incomplete two-digit year “20” scrolls the overlay to the year 20AD, which is somewhat annoying.
Maybe support 2-digit years in some way?
Comments from Reviewable
Review status: 9 of 17 files reviewed at latest revision, 2 unresolved discussions.
vaadin-date-picker-behavior.html, line 171 at r1 (raw file):
Previously, platosha (Anton Platonov) wrote…
> This works significantly different from the Sugar parser in the sense that it only works for all the three parts, while Sugar can take even a single number.
>
> It also makes the date picker to only react on typing when the full date is entered. This might confuse users to think that the keyboard input is not supported at all.
>
> Maybe allow `day` and `month/day` as well?
Done.
vaadin-date-picker-behavior.html, line 173 at r1 (raw file):
Previously, platosha (Anton Platonov) wrote…
> Any number is treated as a full year here, even incomplete two-digit year “20” scrolls the overlay to the year 20AD, which is somewhat annoying.
>
> Maybe support 2-digit years in some way?
Done.
Comments from Reviewable
Reviewed 5 of 5 files at r2.
Review status: 12 of 17 files reviewed at latest revision, 2 unresolved discussions.
Comments from Reviewable
Review status: 12 of 17 files reviewed at latest revision, 3 unresolved discussions.
demo/index.html, line 107 at r3 (raw file):
<script>
var datepicker = document.querySelector('vaadin-date-picker#keyboard-input');
datepicker.set('i18n.parseDate', function(dateString) {
Something fishy still happening with IE11. For me the demos work with the master version but fails with this branch (both index.html and advanced.html). None of the date-pickers are shown.
In index.html I get the following error: Object doesn't support property or method 'set': index.html (107,11)
Comments from Reviewable
demo/index.html, line 107 at r3 (raw file):
Previously, samiheikki (Sami Suo-Heikki) wrote…
> Something fishy still happening with IE11. For me the demos work with the master version but fails with this branch (both index.html and advanced.html). None of the date-pickers are shown.
> In index.html I get the following error: `Object doesn't support property or method 'set': index.html (107,11)`
Done.
Comments from Reviewable
Reviewed 6 of 16 files at r1, 3 of 5 files at r2, 3 of 5 files at r3, 4 of 4 files at r4.
Review status: 16 of 17 files reviewed at latest revision, 8 unresolved discussions.
vaadin-date-picker-light.html, line 78 at r4 (raw file):
</iron-dropdown>
<content></content>
Why move the content insertion point below the dropdown?
vaadin-date-picker-light.html, line 105 at r4 (raw file):
attached: function() {
this.listen(this.inputElement, 'input', '_userInputValueChanged');
The inputElement is in light DOM, it might not be ready by this time, and also might change afterwards, right?
Can we listen for the bubbled input event on the light date picker hosting element instead?
demo/advanced.html, line 51 at r4 (raw file):
return monthName + ' ' + fullYear;
},
parseDate: function(dateString) {
Why do we need a workaround for a single month name here?
Maybe explain the reason with a comment line?
demo/index.html, line 87 at r4 (raw file):
</demo-snippet>
<h3>Keyboard input</h3>
Adding a third-party library Sugar and integrating it with a date picker by overriding a parser callback — this doesn’t feel like a basic use case / example.
Move to the advanced page, perhaps?
demo/index.html, line 111 at r4 (raw file):
var datepicker = document.querySelector('vaadin-date-picker#keyboard-input');
datepicker.set('i18n.parseDate', function(dateString) {
// See if we get exactly 1 match from the month names
We don’t have to explain the same month parser workaround twice, I think.
docs/vaadin-date-picker-value.adoc, line 10 at r4 (raw file):
= Handling the Value
The user can select a date easiest by clicking or tapping on it on the dropdown overlay.
IMO, The word “easiest” sounds a bit weird in this place of the sentence.
We probably shouldn’t assume that some way of entering is easier from another. Maybe just drop “easiest” from here?
test/keyboard-navigation.html, line 201 at r4 (raw file):
});
it('should select focused day with enter', function() {
Why did you remove this test?
Comments from Reviewable
Reviewed 1 of 1 files at r5.
Review status: all files reviewed at latest revision, 8 unresolved discussions.
Comments from Reviewable
Review status: 11 of 17 files reviewed at latest revision, 8 unresolved discussions.
vaadin-date-picker-light.html, line 78 at r4 (raw file):
Previously, platosha (Anton Platonov) wrote…
> Why move the content insertion point below the dropdown?
I thought it would be the simplest way to get around the issue with the overlay buttons focusing on tab. Just realized this just inverted the problem. Restored the original order and added tabIndex -1's to the buttons.
vaadin-date-picker-light.html, line 105 at r4 (raw file):
Previously, platosha (Anton Platonov) wrote…
> The `inputElement` is in light DOM, it might not be ready by this time, and also might change afterwards, right?
>
> Can we listen for the bubbled `input` event on the light date picker hosting element instead?
Done.
demo/advanced.html, line 51 at r4 (raw file):
Previously, platosha (Anton Platonov) wrote…
> Why do we need a workaround for a single month name here?
>
> Maybe explain the reason with a comment line?
Hmm...what do you mean? There is a comment for this.
The purpose for this was originally to fulfil a request that just typing 'fe' should immediately match to february. Sugar alone doesn't.
demo/index.html, line 87 at r4 (raw file):
Previously, platosha (Anton Platonov) wrote…
> Adding a third-party library `Sugar` and integrating it with a date picker by overriding a parser callback — this doesn’t feel like a basic use case / example.
>
> Move to the advanced page, perhaps?
It sure doesn't :) But there's an issue with Sugar's locales which are global. The advanced page uses 'fi' locale so we can't have both examples on the same page.
demo/index.html, line 111 at r4 (raw file):
Previously, platosha (Anton Platonov) wrote…
> We don’t have to explain the same month parser workaround twice, I think.
Done.
docs/vaadin-date-picker-value.adoc, line 10 at r4 (raw file):
Previously, platosha (Anton Platonov) wrote…
> IMO, The word “easiest” sounds a bit weird in this place of the sentence.
>
> We probably shouldn’t assume that some way of entering is easier from another. Maybe just drop “easiest” from here?
Done.
test/keyboard-navigation.html, line 201 at r4 (raw file):
Previously, platosha (Anton Platonov) wrote…
> Why did you remove this test?
The overlay is tested separately from the datepicker and the logic to selecting a date on close is now in datepicker level. Hitting enter in overlay just fires a 'close' request and doesn't perform value selection individually anymore. There's corresponding test in the new tests on the right level.
Comments from Reviewable
Reviewed 1 of 16 files at r1, 6 of 6 files at r6.
Review status: all files reviewed at latest revision, 1 unresolved discussion.
Comments from Reviewable
Review status: all files reviewed at latest revision, 5 unresolved discussions.
vaadin-date-picker-behavior.html, line 304 at r1 (raw file):
},
_focusedDateChanged: function() {
I'd prefer using function argument focusedDate here instead of this.focusedDate – just as a practice.
vaadin-date-picker-behavior.html, line 381 at r1 (raw file):
this.$.overlay.scrollToDate(this.$.overlay.focusedDate || this.$.overlay.initialPosition);
// Have a default focused date
this._ignoreFocusedDateChange = true;
Is the only reason for ignoring to prevent the input field value from changing during open?
vaadin-date-picker-behavior.html, line 559 at r6 (raw file):
// prevent scrolling the page with arrows
e.preventDefault();
if (!this._forwardKeysToOverlay) {
I think I need some rautalankaa to get the idea behind forwarding keys to the overlay or not. I guess there's a reason why we don't move the focus between the input and overlay to target the key events to the elements we want?
vaadin-date-picker-behavior.html, line 572 at r6 (raw file):
this._selectedDate = this.$.overlay.focusedDate;
}
this.close();
I'm thinking we should close on enter only when a date is focused?
Comments from Reviewable
Review status: all files reviewed at latest revision, 5 unresolved discussions.
vaadin-date-picker-behavior.html, line 304 at r1 (raw file):
Previously, Saulis (Sauli Tähkäpää) wrote…
> I'd prefer using function argument `focusedDate` here instead of `this.focusedDate` – just as a practice.
I generally tend to avoid that since it allows you to change the list of observed properties freely without worrying if the parameter list is still in sync. Is there some downside to this?
The parameters are needed if you want to access oldValue or splices, though, but that's not the case here.
vaadin-date-picker-behavior.html, line 381 at r1 (raw file):
Previously, Saulis (Sauli Tähkäpää) wrote…
> Is the only reason for ignoring to prevent the input field value from changing during open?
That's right. If you open a date-picker with empty/no value, you'll expect the input to remain empty while opening the dropdown
vaadin-date-picker-behavior.html, line 559 at r6 (raw file):
Previously, Saulis (Sauli Tähkäpää) wrote…
> I think I need some rautalankaa to get the idea behind forwarding keys to the overlay or not. I guess there's a reason why we don't move the focus between the input and overlay to target the key events to the elements we want?
Correct, we need to keep the focus on the input always because
1. The text must be selected while keyboard navigating (not possible on Safari without input focus)
2. The user must be able to start typing at any point even while "keyboard navigating" the overlay
vaadin-date-picker-behavior.html, line 572 at r6 (raw file):
Previously, Saulis (Sauli Tähkäpää) wrote…
> I'm thinking we should close on enter only when a date is focused?
So, you mean typing "today" and hitting enter wouldn't select a value? I recall this being a requested feature.
Comments from Reviewable
vaadin-date-picker-behavior.html, line 304 at r1 (raw file):
Previously, tomivirkki (Tomi Virkki) wrote…
> I generally tend to avoid that since it allows you to change the list of observed properties freely without worrying if the parameter list is still in sync. Is there some downside to this?
>
> The parameters are needed if you want to access oldValue or splices, though, but that's not the case here.
Ah, it's apparently a documented best-practice https://www.polymer-project.org/1.0/docs/devguide/observers#dependencies Fixed.
Comments from Reviewable
Reviewed 1 of 1 files at r7.
Review status: all files reviewed at latest revision, 5 unresolved discussions.
Comments from Reviewable
Reviewed 1 of 5 files at r3, 3 of 4 files at r4, 1 of 1 files at r5, 6 of 6 files at r6, 1 of 1 files at r7.
Review status: all files reviewed at latest revision, 4 unresolved discussions.
Comments from Reviewable
Review status: all files reviewed at latest revision, 5 unresolved discussions.
vaadin-date-picker.html, line 186 at r7 (raw file):
disabled$="[[disabled]]"
readonly$="[[readonly]]"
no-input$=[[_noInput]] />
Double quotes around the attribute value, please.
Comments from Reviewable
vaadin-date-picker.html, line 186 at r7 (raw file):
Previously, platosha (Anton Platonov) wrote…
> Double quotes around the attribute value, please.
Done.
Comments from Reviewable
Review status: 16 of 17 files reviewed at latest revision, 4 unresolved discussions.
Comments from Reviewable
Review status: 16 of 17 files reviewed at latest revision, 1 unresolved discussion.
vaadin-date-picker-behavior.html, line 572 at r6 (raw file):
Previously, tomivirkki (Tomi Virkki) wrote…
> So, you mean typing "today" and hitting enter wouldn't select a value? I recall this being a requested feature.
Shouldn't typing "today" focus the current date just like typing 2016/10/11 would? Also, I wouldn't want overlay close on enter if I quickly typo "toda" or something before hitting enter.
Comments from Reviewable
Reviewed 1 of 1 files at r8.
Review status: all files reviewed at latest revision, 1 unresolved discussion.
Comments from Reviewable
vaadin-date-picker-behavior.html, line 572 at r6 (raw file):
Previously, Saulis (Sauli Tähkäpää) wrote…
> Shouldn't typing "today" focus the current date just like typing 2016/10/11 would? Also, I wouldn't want overlay close on enter if I quickly typo "toda" or something before hitting enter.
Yes, when you type 'today' (no enter) today does focus (not with the default parser of course). And if you hit 'toda' + enter, the field will go invalid (as in specs).
The current implementation follows the spec + first round hallway testing results, and https://github.com/vaadin/components-team-tasks/issues/212 (conducted against 1.2.0-alpha2) should pinpoint any remaining UX issues that will be fixed later
Comments from Reviewable
Reviewed 1 of 1 files at r8.
Review status: all files reviewed at latest revision, 1 unresolved discussion.
Comments from Reviewable
Reviewed 4 of 16 files at r1, 2 of 5 files at r2, 1 of 5 files at r3, 2 of 4 files at r4, 1 of 1 files at r5, 5 of 6 files at r6, 1 of 1 files at r7, 1 of 1 files at r8.
Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.
Comments from Reviewable
|
gharchive/pull-request
| 2016-10-04T12:15:32 |
2025-04-01T04:36:11.835688
|
{
"authors": [
"Saulis",
"platosha",
"samiheikki",
"tomivirkki"
],
"repo": "vaadin/vaadin-date-picker",
"url": "https://github.com/vaadin/vaadin-date-picker/pull/247",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
328139467
|
Fix min max styling
Fixes #560
This change is
Review status: all files reviewed at latest revision, all discussions resolved.
Comments from Reviewable
|
gharchive/pull-request
| 2018-05-31T13:30:51 |
2025-04-01T04:36:11.839327
|
{
"authors": [
"YuriyVaadin",
"tomivirkki"
],
"repo": "vaadin/vaadin-date-picker",
"url": "https://github.com/vaadin/vaadin-date-picker/pull/562",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
357195175
|
Pressing Esc twice clears the dropdown list selection but not the value
Steps to reproduce:
Select a value
Reopen the dropdown -> the selected value is indicated with a checkmark
Press Esc twice
Reopen the dropdown -> No item is shown as selected (no checkmark)
I think this is probably the same issue as https://github.com/vaadin/vaadin-combo-box/issues/622
IMO this is a really nasty bug, as it can quite easily cause unexpected consequences when the user does not realize the value has been cleared.
Even after following the steps timePicker.value isn't cleared. So this is only visual?
Maybe only visual for the time-picker. The internal combo box selectedItem is cleared, that’s probably the root cause. The combo box does still also have the correct value.
So I guess the problem is not really in time picker, and only combo box (as time-picker does not have a selectedItem property). The potential danger is if a developer binds to the selectedItem in combo box.
|
gharchive/issue
| 2018-09-05T11:58:19 |
2025-04-01T04:36:11.887306
|
{
"authors": [
"jouni",
"tomivirkki"
],
"repo": "vaadin/vaadin-time-picker",
"url": "https://github.com/vaadin/vaadin-time-picker/issues/73",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
2159375548
|
Debugging is failing when starting
OS: MacOS 14
VSCode version: Version: 1.86.2 (Universal)
CodeLLDB version: CodeLLDB v1.10.0
Compiler: XCode/LLDB
Debuggee: C compiled file
Mac mini (Processor : 3.2 GHz 6-Core Intel Core i7)
Python 3.10.6
When I trigger debugging, the debugging fail.
Debug console:
Console is in 'commands' mode, prefix expressions with '?'.
Launching: (long text XYZ...)
Launched process 1971
Process exited with code -1.
Verbose log
"commandCompletions":true,"reproducer":false},"__sessionId":"2ff31ce7-69d9-4180-b321-4fdb06f3edd5"},"type":"request","seq":2}
[DEBUG codelldb::dap_codec] <-- {"seq":2,"type":"event","event":"output","body":{"category":"console","output":"Console is in 'commands' mode, prefix expressions with '?'.\n"}}
INFO(Python) 17:17:54 formatters: Initializing
INFO(Python) 17:17:54 formatters.rust: Initializing
Traceback (most recent call last):
File "/Users/ABC/.vscode/extensions/vadimcn.vscode-lldb-1.10.0/formatters/__init__.py", line 9, in __lldb_init_module
rust.__lldb_init_module(debugger_obj, internal_dict)
File "/Users/ABC/.vscode/extensions/vadimcn.vscode-lldb-1.10.0/formatters/rust.py", line 754, in __lldb_init_module
initialize_category(debugger_obj, internal_dict)
File "/Users/ABC/.vscode/extensions/vadimcn.vscode-lldb-1.10.0/formatters/rust.py", line 86, in initialize_category
max_string_summary_langth = debugger.GetSetting('target.max-string-summary-length').GetIntegerValue()
AttributeError: 'SBDebugger' object has no attribute 'GetSetting'
[DEBUG codelldb::dap_codec] <-- {"seq":3,"type":"event","event":"initialized"}
.
.
Later:
.
DEBUG codelldb::dap_session] Client has disconnected
[DEBUG codelldb::debug_session] End of the requests stream
[DEBUG codelldb::debug_session] DebugSession::drop()
[DEBUG codelldb] End of the debug session
[DEBUG codelldb] Exiting
Debug adapter exit code=0 (0x0), signal=null.
https://github.com/vadimcn/codelldb/discussions/456#discussioncomment-874122
Thx for the reply.
I already tried to remove codeLLDB extension and add it again. I also tried to remove the debugserver executable but none of the previous solutions worked for me :(
is this a problem in the OS or the extension itself?
|
gharchive/issue
| 2024-02-28T16:38:24 |
2025-04-01T04:36:11.900458
|
{
"authors": [
"akhodeir",
"lbb9507"
],
"repo": "vadimcn/codelldb",
"url": "https://github.com/vadimcn/codelldb/issues/1072",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2467719877
|
Is this dead library?
Just checking
Yes 👍
|
gharchive/issue
| 2024-08-15T09:23:10 |
2025-04-01T04:36:11.905151
|
{
"authors": [
"MikeeNachtigall",
"itsmikesharescode"
],
"repo": "vadimkorr/svelte-carousel",
"url": "https://github.com/vadimkorr/svelte-carousel/issues/166",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
733123390
|
Better readability for test logs
Before:
After:
@quarckster Thanks for doing this! 🔥💯🙌I like the new format a lot better. 👍 I'll merge this today!
|
gharchive/pull-request
| 2020-10-30T12:12:39 |
2025-04-01T04:36:11.963188
|
{
"authors": [
"quarckster",
"vakenbolt"
],
"repo": "vakenbolt/go-test-report",
"url": "https://github.com/vakenbolt/go-test-report/pull/10",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
665790457
|
Background photo needs to be changed
someone?
Done, vish ra bichi var
|
gharchive/issue
| 2020-07-26T14:23:49 |
2025-04-01T04:36:11.963906
|
{
"authors": [
"enqidu"
],
"repo": "vakhokoto/GithubExstension",
"url": "https://github.com/vakhokoto/GithubExstension/issues/15",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2219470825
|
Static data chip
Closes #133
These changes comment out the memory argument constraints. I'm not sure this is necessary, but I found it convenient to do so since we're convinced that the memory argument is unsound anyway, and Hadas is going to replace it.
Because of the commented out code the warnings are getting out of hand. I've cleaned up as much as makes sense so we can still track them. Please merge https://github.com/valida-xyz/valida/pull/136 into this before merging this, if it's ok with you.
|
gharchive/pull-request
| 2024-04-02T03:10:56 |
2025-04-01T04:36:11.981139
|
{
"authors": [
"morganthomas",
"thealmarty"
],
"repo": "valida-xyz/valida",
"url": "https://github.com/valida-xyz/valida/pull/134",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
2723340680
|
GCC <=12 is incompatible - CI is biased
Hi,
I tried to compile a container image with the module from valkey/valkey:8 (not yet on alpine).
A lot of errors happen.
I fixed this by downgrading GCC and G++ to v11.
Here is the Dockerfile that works:
FROM docker.io/valkey/valkey:8 as build
ARG SERVER_VERSION=8.0.0
RUN set -ex; \
apt-get update; \
apt-get install -y build-essential cmake git gcc-11 g++-11 pkg-config; \
update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-11 1; \
update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-11 1; \
mkdir -p /opt;
WORKDIR /opt
RUN set -ex; \
git clone https://github.com/valkey-io/valkeyJSON.git; \
mkdir -p /opt/valkeyJSON/build;
WORKDIR /opt/valkeyJSON/build
RUN set -ex; \
cmake .. -DVALKEY_VERSION=${SERVER_VERSION}; \
make
FROM docker.io/valkey/valkey:8
RUN mkdir -p /usr/lib/valkey
COPY --from=build /opt/valkeyJSON/build/src/libjson.so /usr/lib/valkey/libjson.so
CMD ["valkey-server", "--loadmodule", "/usr/lib/valkey/libjson.so"]
On Github Actions, Ubuntu version is not the latest, and not the one used by the main OCI Image. So the tests are OK on GitHub actions, but not with the official image.
Working on a fix, the ubuntu-latest runner has also started uding ubuntu 24 and the default is version 13, which is why the test is failing
|
gharchive/issue
| 2024-12-06T15:40:46 |
2025-04-01T04:36:12.000213
|
{
"authors": [
"metal3d",
"roshkhatri"
],
"repo": "valkey-io/valkeyJSON",
"url": "https://github.com/valkey-io/valkeyJSON/issues/17",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
210466747
|
Angular 4.0.0-rc.1
Since Angular 4.0.0-rc.1:
The <template> element is deprecated. Use <ng-template> instead
The result is that you can't click on an item from the result list of the Typeahead component.
I tried today 4.0.0-rc.2
minor changes are needed and it is starting to work
but it is kinda a breaking change
so I can publish it as @beta
ok?
@valorkin beta ist OK :)
@valorkin Thanks it would be useful to fix this deprecation error! Could you let us know when published? Cheers
@valorkin any news :) ?
@valorkin is working on that and he hopes that he can fix the whole problem this week...
FYI - Saw elsewhere - https://github.com/valor-software/ng2-bootstrap/pull/1770 that ng4 beta is available:
npm i -S ng2-bootstrap@beta
Yes, it is. Unfortunately not compatible with AoT
FYI: 2.0.0-rc.0 fixed this!
Silly question how do I get the 2.0.0.rc-0 please?
Install @beta
there are already 5 pages of issues about this single deprecation. Why you decided to fix it only in next major, that is not released?
It's extra small, could you please fix it with currently released major simply as bugfix? If there are dozens of users asking of this for few months, would be great to give them a smile...
Keep in mind that next, not stable, bc breaking release is not a solution for all users.
cc @valorkin @Martin-Wegner @fchiumeo
@keradus I guess the idea here is that version 1.x is dedicated to Angular 2.x. Angular >= 4 is covered by ngx-bootstrap@next
@keradus when I say @next version, I am literally mean it:
npm install ngx-bootstrap@next
I am trying to solve as a many issues as possible without breaking changes, then merging them in @next version and publishing
yet, as @next is unstable, as you could see from history of 10 PR and 5 sites of bug report, a lot of ppl are using current release with angular 4 with ease , only encountering that one violation. And while current release is stable, we like to use it. While @next release may be nice, it's not there yet, it may or may not contains bc breakers, every time you update you may end up with a little different version...
is there an issue with updating that deprecation on 1.x line ?
I can't do it in v 1.*
It's a breaking change
So it has to be v2
If only I had statics about ngx-bootstrap users,
Do they use v2 or v4 of angular
|
gharchive/issue
| 2017-02-27T12:10:42 |
2025-04-01T04:36:12.008505
|
{
"authors": [
"Martin-Wegner",
"conor-mac-aoidh",
"ctrl-brk",
"daBishMan",
"keradus",
"slubowsky",
"valorkin"
],
"repo": "valor-software/ng2-bootstrap",
"url": "https://github.com/valor-software/ng2-bootstrap/issues/1692",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2644721643
|
little scratch when used with some video
Hi I have used your extension and noticed that it produce from time to time some little scratch with some video like this one https://www.youtube.com/watch?v=Di2k06uNU1U
Any reason for that ?
Cannot reproduce.. either way not something I could do anything about. Soundfixer just configures Web Audio to do its thing.
I must have said that the issue is when using android firefox or android chrome but you are right this is an issue at Web Audio level
|
gharchive/issue
| 2024-11-08T17:39:12 |
2025-04-01T04:36:12.011805
|
{
"authors": [
"devpat02",
"valpackett"
],
"repo": "valpackett/soundfixer",
"url": "https://github.com/valpackett/soundfixer/issues/64",
"license": "Unlicense",
"license_type": "permissive",
"license_source": "github-api"
}
|
862780578
|
Update sbt-mdoc to 2.2.20
Updates org.scalameta:sbt-mdoc from 2.2.18 to 2.2.20.
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 = "org.scalameta", artifactId = "sbt-mdoc" } ]
labels: sbt-plugin-update, semver-patch
Superseded by #299.
|
gharchive/pull-request
| 2021-04-20T12:45:52 |
2025-04-01T04:36:12.016698
|
{
"authors": [
"scala-steward"
],
"repo": "valskalla/odin",
"url": "https://github.com/valskalla/odin/pull/281",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
149641597
|
Add benchmark link to README
Minor addition
Merged. Thanks for the link to template benchmarks!
|
gharchive/pull-request
| 2016-04-20T02:58:41 |
2025-04-01T04:36:12.023680
|
{
"authors": [
"escholtz",
"valyala"
],
"repo": "valyala/quicktemplate",
"url": "https://github.com/valyala/quicktemplate/pull/5",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
2717757731
|
OrcaFlex | ThreadCount PowerShell Script
first cut code done
see error below
hi @vamseeachanta I tried this on my local machine. I had to run this in a (admin mode) powershell. Could you try that ?
code was invalid. Updated the numeric code and it worked. Good job there mate.
|
gharchive/issue
| 2024-12-04T13:32:08 |
2025-04-01T04:36:12.025428
|
{
"authors": [
"getsivakumar",
"vamseeachanta"
],
"repo": "vamseeachanta/digitalmodel",
"url": "https://github.com/vamseeachanta/digitalmodel/issues/74",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1726413558
|
Remove references to "vanilla" in README
Fix #18
Keep up the great work and happy coding!
Closing this PR as #18 is already fixed.
|
gharchive/pull-request
| 2023-05-25T19:59:41 |
2025-04-01T04:36:12.034649
|
{
"authors": [
"Tao-VanJS",
"steren",
"zhengtu1122"
],
"repo": "vanjs-org/van",
"url": "https://github.com/vanjs-org/van/pull/19",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
775057396
|
Demo is down
The demo link in README returns a 404.
https://vanruesc.github.io/spatial-controls/public/demo
Thanks for the report 👍
I forgot to update the gh-pages branch after renaming master to main. It should work now.
|
gharchive/issue
| 2020-12-27T15:27:32 |
2025-04-01T04:36:12.036971
|
{
"authors": [
"marcofugaro",
"vanruesc"
],
"repo": "vanruesc/spatial-controls",
"url": "https://github.com/vanruesc/spatial-controls/issues/1",
"license": "Zlib",
"license_type": "permissive",
"license_source": "github-api"
}
|
2205012905
|
组件库支持 uniapp 开发app 吗？
组件库支持 uniapp 开发app 吗？
varlet 是 web 组件库，所以 webapp 是可以的，native 小程序不行～
varlet 是 web 组件库，所以 webapp 是可以的，native 小程序不行～
uniapp开发小程序，可以用吗？
|
gharchive/issue
| 2024-03-25T06:37:25 |
2025-04-01T04:36:12.092789
|
{
"authors": [
"JamesLi-dev",
"elarbor",
"haoziqaq"
],
"repo": "varletjs/varlet",
"url": "https://github.com/varletjs/varlet/issues/1549",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
217242617
|
Why can’t use regular if/else conditions inside a component definition?
In Section Conditional Rendering, It says:
You can’t use regular if/else conditions inside a component definition. The conditional (ternary) operator is your friend.
I think it is wrong. Because instead of
// if- else (big blocks)
function render() {
return condition ? (
<span>
Rendered when `truthy`
</span>
) : (
<span>
Rendered when `falsey`
</span>
)
}
this render function can also be written in a if/else way:
function render() {
if (condition) {
return (
<span>
Rendered when `truthy`
</span>
)
}
else {
return (
<span>
Rendered when `falsey`
</span>
)
}
}
Yes, I assume you can. What's the issue here?
@delanni Sorry. I didn't say it clearly. I have already updated my comment.
Though it will technically work, you'd probably want to extract a function to do this (pretty ugly otherwise). I think the most mileage you'll get out of ternarys as they apply to conditional rendering is when you are branching inside of a block of JSX, where 'if/else' truly will not work.
@F3n67u You're right. Sorry, it was a typo. Fixed it now.
You can use regular if/else conditions inside a component definition.
As @amsheehan pointed out - as the render function markup gets larger it is always advisable to split it up into logically smaller components and compose them.
|
gharchive/issue
| 2017-03-27T13:17:36 |
2025-04-01T04:36:12.116776
|
{
"authors": [
"F3n67u",
"amsheehan",
"delanni",
"vasanthk"
],
"repo": "vasanthk/react-bits",
"url": "https://github.com/vasanthk/react-bits/issues/5",
"license": "CC-BY-4.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
564351662
|
Day 449
Good morning! Here's your coding interview problem for today.
This problem was asked by Alibaba.
Given an even number (greater than 2), return two prime numbers whose sum will be equal to the given number.
A solution will always exist. See Goldbach’s conjecture.
Example:
Input: 4
Output: 2 + 2 = 4
If there are more than one solution possible, return the lexicographically smaller solution.
If [a, b] is one solution with a <= b, and [c, d] is another solution with c <= d, then
[a, b] < [c, d]
If a < c OR a==c AND b < d.
Identical to Day 101: https://github.com/vaskoz/dailycodingproblem-go/issues/212
|
gharchive/issue
| 2020-02-12T23:51:16 |
2025-04-01T04:36:12.121097
|
{
"authors": [
"vaskoz"
],
"repo": "vaskoz/dailycodingproblem-go",
"url": "https://github.com/vaskoz/dailycodingproblem-go/issues/907",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2174379849
|
Settings experiment virtual cam
Settings experiment virtual cam not showing. Do I need to install a plugin from the web?
In the current version of VCam, the virtual Camera is no longer experimental.
You can install it by following the instructions in the document below:
https://docs.vcamapp.com/v/en/virtual-camera/virtualcamera
I have the 0.10.1. version.
Can you upload the screenshot?
If possible, please update the app. Older versions are no longer supported.
I can't update as I have 12.7.3 version of MacOS.
Thanks for the screenshot!
Sorry, this Experiment tab's feature is only available in the supporter version.
This is a text localization bug and there is not enough explanation about the gray-out in the English version.
|
gharchive/issue
| 2024-03-07T17:29:48 |
2025-04-01T04:36:12.194852
|
{
"authors": [
"marjekikas",
"tattn"
],
"repo": "vcamapp/app",
"url": "https://github.com/vcamapp/app/issues/12",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
191828930
|
Issue with recv() in examples
I was experimenting with some of the examples, and I noticed that they seem to get stuck when executing a call to the recv() function.
For example, the sht.py example program gets stuck after presenting response feedback on the first trial, presumably because of the recv() call on line 69. Here's an example from the log file output:
1480196296567 0 {"_replace": {"OBJ": "Is this object a Greeble or a Groble?"}}
1480196296570 0 {"_task": {"good": {"_pp": "Correct"}, "bad": {"_pp": "Incorrect"}, "end": {"Trial": 32}}}
1480196296570 0 {"Trial": {"_nm": {"<=": 32}}}
1480196296571 0 {"OBJ": ""}
1480196296571 0 {"#btns": ["_i", "Groble", "Greeble"]}
1480196296571 0 {"Trial": 1}
1480196296571 0 {"OBJ": {"_bx": {"bd": "solid", "r": 0, "bg": "black", "bdc": "red", "bdw": 10, "w": 20, "h": 20, "pad": 0}}}
1480196298216 1 [1924,"#btns",{"Greeble":3}]
1480196298216 0 {"_pp": "Correct"}
1480196298217 0 {"_S": 2424, "_R": 0}
Similarly, the _math.py program gets stuck after the user submits an answer to the first math problem, presumably because of the recv() call on line 25. Again, from the log file:
1480197220529 0 {"_task": {"bad": {"#feedback": "Incorrect"}, "good": {"#feedback": "Correct"}}}
1480197220532 0 {"Add these numbers": {"#": 9}}
1480197220532 0 {"Add these numbers": {"+": 9}}
1480197220532 0 {"Answer": {"_ix": {}}}
1480197220532 0 {"#submit": {"Submit": 1, "_i": {}}}
1480197223048 1 [2767,"Answer","18"]
Any idea what might be causing this? Thanks!
By the way, if it helps I've got a remote server running stap with this issue:
http://138.197.23.155/taskServer/shj.htm
thanks for that.i believe i fixed the problem, try updating your repo( line 1005 changed in examples/taskServer/lib/stap.js )
|
|
|
| | |
|
|
|
| |
vdv7/stap
stap - Simple Task-Actor Protocol | |
|
|
On Sunday, November 27, 2016 5:42 PM, tylerburleigh <notifications@github.com> wrote:
By the way, if it helps I've got a remote server running stap with this issue:http://138.197.23.155/taskServer/shj.htm—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Thanks, that worked!
|
gharchive/issue
| 2016-11-26T21:57:43 |
2025-04-01T04:36:12.625572
|
{
"authors": [
"tylerburleigh",
"vdv7"
],
"repo": "vdv7/stap",
"url": "https://github.com/vdv7/stap/issues/1",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
215001059
|
Is it possible to use this package without bower?
with https://www.npmjs.com/package/pace-progress for example
Pace theme CSS file was not found: blue/pace-theme-minimal.css
Error: Pace theme CSS file was not found: blue/pace-theme-minimal.css
at Class.treeFor (/app/node_modules/ember-cli-pace/index.js:80:15)
at project.addons.map.addon (/app/node_modules/ember-cli/lib/broccoli/ember-app.js:538:22)
...
@server-may-cry Are you looking for https://www.npmjs.com/package/ember-cli-pace ?
@vectart yep.
I'am currently using that (this) package.
But it require bower
$ ember install ember-cli-pace
Yarn: Installed ember-cli-pace
installing pace
install bower package pace
I'm looking for this as well, since the Ember ecosystem in general is moving away from Bower. :)
This should be fairly easy to convert to not use bower as long as pace is available somewhere on NPM. I've just converted a bunch of bower-dependent addons to use NPM via ember-cli-node-assets
@jamesdixon can you give an example?
|
gharchive/issue
| 2017-03-17T13:19:43 |
2025-04-01T04:36:12.629696
|
{
"authors": [
"jamesdixon",
"server-may-cry",
"t4t5",
"vectart"
],
"repo": "vectart/ember-cli-pace",
"url": "https://github.com/vectart/ember-cli-pace/issues/39",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
225693721
|
Improve (+) button display
Remove the fading
Move the (+) on the left to get the same margin on the right than below
Possibly add a shadow below the (+) icon.
Validated in 0.3.13 ux_rework #1830
|
gharchive/issue
| 2017-05-02T13:24:24 |
2025-04-01T04:36:12.672708
|
{
"authors": [
"giomfo",
"jeangb"
],
"repo": "vector-im/riot-ios",
"url": "https://github.com/vector-im/riot-ios/issues/1195",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
1781801640
|
Paper branches
This makes it more convenient to use the branches of Paper, such as Folia, Purpur, etc
Thank you for the contribution! I will review it and merge soon. :)
|
gharchive/pull-request
| 2023-06-30T03:12:16 |
2025-04-01T04:36:12.715211
|
{
"authors": [
"KujouMolean",
"vectrixdevelops"
],
"repo": "vectrix-space/ignite",
"url": "https://github.com/vectrix-space/ignite/pull/137",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
704997781
|
Zygarde cube moves
First attempt at contributing...
Fixes #314
Method prose is copy-paste from Bulbapedia... I guess that's not the good way to do this but it seemed to me it was the perfect explanation and my english isn't good enough to offer better...
Thanks! I've been distracted by other projects but I'll try to get this
merged soon.
On Sat, Sep 19, 2020, 14:03 edcrfv notifications@github.com wrote:
First attempt at contributing...
Fixes #314 https://github.com/veekun/pokedex/issues/314
Method prose is copy-paste from Bulbapedia... I guess that's not the good
way to do this but it seemed to me it was the perfect explanation and my
english isn't good enough to offer better...
You can view, comment on, or merge this pull request online at:
https://github.com/veekun/pokedex/pull/316
Commit Summary
Zygarde cube moves
File Changes
M pokedex/data/csv/pokemon_move_method_prose.csv
https://github.com/veekun/pokedex/pull/316/files#diff-3571175666a69bb1a984876bec00330b
(1)
M pokedex/data/csv/pokemon_move_methods.csv
https://github.com/veekun/pokedex/pull/316/files#diff-0b590866a96e7167ebac91156e1d99be
(1)
M pokedex/data/csv/pokemon_moves.csv
https://github.com/veekun/pokedex/pull/316/files#diff-4b74531af13284118bf0f10864ee8acb
(40)
Patch Links:
https://github.com/veekun/pokedex/pull/316.patch
https://github.com/veekun/pokedex/pull/316.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/veekun/pokedex/pull/316, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABK3M6ULIW4PLGKGCMCQTTSGUMAZANCNFSM4RTHHJJA
.
Merged with the CLI. Sorry it took so long.
https://github.com/veekun/pokedex/commit/aaff9197553df2f709eb982216603255e3ae981f
|
gharchive/pull-request
| 2020-09-19T21:02:56 |
2025-04-01T04:36:12.737887
|
{
"authors": [
"edcrfv0",
"magical"
],
"repo": "veekun/pokedex",
"url": "https://github.com/veekun/pokedex/pull/316",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
1341373333
|
Use the correct published docker containers for the front end config based on the users machine/OS
Currently the VegaCapsule net_confs/config_frontends.hcl use published docker containers/images that are not compatible with Mac M1 computers.
Work is to be done in the following issue to publish docker containers/images that support M1 Macs.
https://github.com/vegaprotocol/frontend-monorepo/issues/1058
We need a way in VegaCapsule to ensure that based on the users machine/OS the correct containers/images are used.
It is expected that early users of VegaCapsule (market makers / people building strategies) will need the front ends and could very well be using M1 macs. Currently these users are unable to do so.
Blocked until the following is completed
https://github.com/orgs/vegaprotocol/projects/110/views/25
current PR: https://github.com/vegaprotocol/frontend-monorepo/pull/1104/files
thread for issue: https://vegaprotocol.slack.com/archives/C8WS7M50E/p1661245219957939
|
gharchive/issue
| 2022-08-17T08:25:14 |
2025-04-01T04:36:12.768642
|
{
"authors": [
"gordsport",
"mkjmdski"
],
"repo": "vegaprotocol/vegacapsule",
"url": "https://github.com/vegaprotocol/vegacapsule/issues/230",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1229982140
|
JSON stringify/unstringify feature
What's the Problem?
JSON stringify/unstringify feature
Solution/Idea
See how they do it here : Online JSON Tools
Alternatives
Could have a convert the JSON text to a stringified text and viceversa
Priorities
No response
DevToys Version
No response
Comments
Thank you very much !
Hello,
Thanks for your suggestion. There's more or less such a tool already:
Does this corresponds to what you're referring to?
It's not JSON specific, but it can unstringify and stringify something.
|
gharchive/issue
| 2022-05-09T16:40:16 |
2025-04-01T04:36:12.783293
|
{
"authors": [
"binaryfog",
"veler"
],
"repo": "veler/DevToys",
"url": "https://github.com/veler/DevToys/issues/517",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1802643023
|
Simplifier le réimport des données de la région
En attente de cocarto; pour l’instant le réimport est à faire à la main en spécifiant les paramètres à chaque fois.
Sur cocarto:
[x] Configuration de l’import
[x] MR
[x] Deuxième point cette issue](https://gitlab.com/CodeursEnLiberte/cocarto/-/issues/306) pour réutiliser le dernier import
Fait: on peut desormais refaire un import existant et on a mis en place un import quotidien
|
gharchive/issue
| 2023-07-13T09:46:24 |
2025-04-01T04:36:12.786018
|
{
"authors": [
"Tristramg",
"n-b"
],
"repo": "velo-iledefrance/observatoire-vif",
"url": "https://github.com/velo-iledefrance/observatoire-vif/issues/10",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
374002330
|
RSS 주소와 코드입니다~
저만쓰려고 대충만든거라
참고만하세요! rss 모듈 쓰시면 금방입니다! 30분도안걸려요
code url : https://github.com/ysm0622/velog-rss
rss api url : https://5y87w9v9sl.execute-api.ap-northeast-2.amazonaws.com/dev/
RSS기능을 직접 api에 추가하셔서
제 람다함수는 내리고 이 이슈는 닫습니다.
|
gharchive/issue
| 2018-10-25T15:21:11 |
2025-04-01T04:36:12.789405
|
{
"authors": [
"ysm0622"
],
"repo": "velopert/velog",
"url": "https://github.com/velopert/velog/issues/51",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1202717250
|
Changed fd_create to fd-create
Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
Changed the name of veracruz/sdk/rust-examples/fd_create to veracruz/sdk/rust-examples/fd-create
This is so that the naming convention matches with all the other folders in the directory.
Hi @AryanGodara, and thanks for your first Veracruz PR. Welcome to the project! 🎉
Developer Certificate of Origin
As this is your first commit to the Veracruz repository can you please certify that you have authorisation to contribute code using the Developer Certificate of Origin? This is a requirement of the Veracruz organization, which we agreed with the Linux Foundation when we were adopted. To do this, it's enough to include the following text in your PR message, at the top:
Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
Signed commits
Can I ask that you sign all of your commits using GPG? We adopted this rule a while ago as a security/integrity mechanism and code cannot be merged into the main Veracruz repository without this signing. If you don't know how to do this, then follow these instructions:
Generate a new GPG key: gpg --gen-key and follow the instructions asking for your name, email, etc.
List the GPG keys available: gpg --list-secret-keys --keyid-format=long. Make a note of the ID of the key you’ve just generated (it’s a long string of capital letters and numbers),
Export the public key component of the generated key to stdout : gpg --armor --export $KEYID where $KEYID is the long string of letters and numbers, above.
Go to your Github profile’s settings page, go to the Keys section, add a new GPG key and copy-paste the public key printed out above.
Tell Git to use this key when signing commits: git config --global user.signingkey $KEYID , again where $KEYID is the long string of letters and numbers, above.
Tell Git to always sign your commits: git config --global commit.gpgsign true (Note, as an alternative, you can choose not to set this but then you will always need to commit using git commit -S)
To test if your commits are being signed correctly, commit something on a local copy, and then use: git log --show-signature. Note that Github signs their own merge commits made to a repository when a pull request is merged, but the command above may not show the signed commits correctly (they’ll be highlighted in red) as you need to import Github’s public key to verify the signature. To do this, import Github’s key by: curl https://github.com/web-flow.gpg | gpg --import Showing the signatures in Git log should now work, and Git should recognise that Github’s merge commits were signed by Github (they should now be blue).
Once you've setup GPG signing, you usually have to export GPG_TTY=$(tty) in your terminal (or you'll get an error about a missing tty) prior to commiting/rebasing. Once that is done, edit your PR to sign all commits and push again.
(Can you also edit AUTHORS.markdown to add your name, and add the changed file to this PR, too?)
@dominic-mulligan-arm I've included the text in the PR message. I just need some time to figure out the GPG part. I'll do that and also update AUTHORS.markdown too, as soon as possible.👍
Excellent, thanks @AryanGodara! Are you running Ubuntu Linux? Installing GPG can be done with sudo apt-get install gnupg.
I'm using Debian with WSL2 on windows 11. Since it'll take time to dual boot ubuntu and I may lose some important data, I plan on doing it once the contribution period is over.
But thank you for providing the steps in such detail, it has really made my work much easier!!
@dominic-mulligan-arm
All the requested changes are done now.
Sorry for taking so long, WSL2 and Debian are super super slow for git.
I will make more corrections if required!
@AryanGodara unfortunately all of the commits in a PR need to be signed in order to be allowed into our main (if you click on the "Commits" tab at the top, you will see that two of the commits are not marked as "Verified", meaning merge will be blocked by our branch commit rules). To fix this, you can do the following steps:
Do git log and find the hash of the commit immediately prior to your first commit. Call this $HASH.
Do git reset --soft $HASH to do a "soft reset" on your branch to the state immediately prior to your first change, while keeping all of your changes in the Git staging area.
Do git commit to create a new, single commit capturing all of your changes, now signed by GPG.
Do git push --force-with-lease to update the pull request.
Also, it appears that the CI is failing due to build issues in the SDK. If you do git grep fd_create from within your Veracruz root repository, it should list the files that are still referring to the old fd_create which you have now renamed. Fixing those (which I presume are Makefiles, or similar build scripts) and adding them to the PR should solve the CI issue.
@dominic-mulligan-arm
I have fixed the first issue with the commits, as for the second one, this is the list of those files :-
administrator@DESKTOP-6HQEO4S:/mnt/d/veracruz/sdk/rust-examples$ git grep fd_create
fd-create/Cargo.toml:name = "fd_create"
fd-create/Cargo.toml:description = "Test of fd_create function"
fd-create/src/main.rs://! Test of fd_create function.
fd-create/src/main.rs: let mut file = libveracruz::fd_create()?;
fd-create/test.sh:RUNARGS="--program target/wasm32-wasi/debug/fd_create.wasm --input-source target/wasm32-wasi/debug"
Before moving forward, I just wanted to confirm, the task is to open these files and change very mention of "fd_create" to "fd-create".
Is this correct??
Hi @AryanGodara, you need to first cd ../../ into the Veracruz root directory before doing the git grep, otherwise you're only searching under ./sdk/rust_examples. I don't think any of those files are actually causing the issue that we are seeing with CI (and "fd_create" for the name of the test in the Cargo.toml file is actually idiomatic Rust, confusingly...). You can also look at the CI build logs to understand what the issue is, at the top of this page...
@dominic-mulligan-arm Sorry for taking so long, but I've updated all instances of fd_create to fd-create
(Except the ones that were either constt declarations, for examples :
const FD_CREATE_RUST_WASM: &'static str = "fd-create.wasm"; inside veracruz-server-test/src/main.rs
And I've commit the changes
I've corrected my previous mistake, and reverted all the times when I changed a function name from fd_create to fd-create.
Now all the changes are in .toml or .cargo files, or in the comments mentioning the 'directory : rust-examples/fd-create'
One possible error now may by that fd_create.wasm has been changed to fd-create.wasm everywhere, since I noticed it is created according to the project directory's name.
If there are more errors in the tests, I'll try to rectify those mistakes also
+1+1 = +1 reached, merging.
|
gharchive/pull-request
| 2022-04-13T03:53:00 |
2025-04-01T04:36:12.822014
|
{
"authors": [
"AryanGodara",
"dominic-mulligan-arm"
],
"repo": "veracruz-project/veracruz",
"url": "https://github.com/veracruz-project/veracruz/pull/397",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1194539788
|
Discuss the naming of Various Stores and need for different types of stores inside Veraison kvstore
Current implementation (as of 06/04/2022) has Endorsement Store and TrustAnchorStore.
Need to decide where Certification will reside? A separate store or part of Endorsement Store ?
Any other new types added(like SW Updates) needs a addition of stores.
Also the naming is confusing.
TrustAnchor are also a type of Endorsements. So how does the names uniquely identify the type of elements stored in the Store Type?
Need to discuss the same, via this issue and make a suitable change in the code base..
My two cents on this:
I don't think the number of stores needs to be an architectural issue, i.e. be reflected in the APIs. A single endorsement method as (suggested here https://github.com/veraison/veraison/pull/148#discussion_r843827241) should be enough with a filed within the Endorsement structure used to distinguish between the endorsement types. This "type" field can also be included in the ID URI, thus disambiguating the cases where a scheme uses the same ID derivation for trust anchor and a reference value set.
See also Issue #152
Resolved as it is decided to keep all Endorsements under one Umbrella for now!
|
gharchive/issue
| 2022-04-06T12:24:10 |
2025-04-01T04:36:12.837734
|
{
"authors": [
"setrofim",
"yogeshbdeshpande"
],
"repo": "veraison/veraison",
"url": "https://github.com/veraison/veraison/issues/151",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
970670948
|
A new home for this project? 😄
Hey Mike! First off, thank you for taking over with this project and providing an option for users wanting to build functions with Rust on Vercel. We really, really appreciate all of your work. I know that you're now looking for maintainers, and we're going to be putting more effort behind Rust support on Vercel.
We're started to create a Vercel Community GitHub organization, where we'll support community runtimes like Rust and friends. I've started the process of migrating this repo over to the community (https://github.com/vercel-community/rust)
Before proceeding further, I just wanted to check in with you and make sure this was okay. I've credited you in the repo 🙏 and would be happy to talk about next steps if you're okay with this!
Hi @leerob, thanks for the message and the update. I unfortunately haven't used vercel much in a while, nor rust, nor this project, so maintaining it has become a bit of a burden. With that said, I'm happy to transfer it over to vercel and the community, who will keep it much more up to date than I.
When it's been fully transferred, let me know and I'll archive this repo. Additionally, if there's anything I can do to help, let me know.
@mike-engel I sent you an invite to the org, where you'll be able to transfer it! I can't initiate it from my side unless you make me an admin here.
@leerob just to be clear, you'd like me to transfer this repo over to the vercel-community org? Apologies for the slow reply—currently on holiday. I was under the impression that you were copying everything manually into a new repo. Will that one be living side-by-side with vercel-rust after the transfer? I'm not clear on that.
Thanks!
@mike-engel Ideally we can transfer this repo over - I'll move the changes from the new repo back to here. This can preserve git history and also keep the deployment pipeline that's set up for publishing! Could you also give me NPM permissions for publishing then, as well? Thank you! Username: leerobinson
@leerob got it, thanks! Transferred over, and I've added you as a writer to the npm package.
|
gharchive/issue
| 2021-08-13T19:50:24 |
2025-04-01T04:36:12.847184
|
{
"authors": [
"leerob",
"mike-engel"
],
"repo": "vercel-community/vercel-rust",
"url": "https://github.com/vercel-community/vercel-rust/issues/43",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1020548951
|
Where is the source of flags used in i18nWidget?
I need to add another flag to the widget but for consistency in feeling and experience I don't want to use an arbitrary flag, where did you get the flags in the project?
@kave-me maybe https://github.com/HatScripts/circle-flags/tree/gh-pages/flags
|
gharchive/issue
| 2021-10-07T23:45:38 |
2025-04-01T04:36:12.855706
|
{
"authors": [
"culy247",
"kave-me"
],
"repo": "vercel/commerce",
"url": "https://github.com/vercel/commerce/issues/522",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2323240952
|
npm error: Could not resolve dependency: peer @remix-run/dev@"2.9.1" from @vercel/remix@2.9.2
Peer dependency from @vercel/remix@2.9.2 need to be updated. Here is the npm install error I get after bumping packages to "2.9.2":
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: dashboard@undefined
npm error Found: @remix-run/dev@2.9.2
npm error node_modules/@remix-run/dev
npm error dev @remix-run/dev@"2.9.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @remix-run/dev@"2.9.1" from @vercel/remix@2.9.2
npm error node_modules/@vercel/remix
npm error @vercel/remix@"2.9.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
I am a bit surprised that this error is happening, because I think there is an automated update mechanism in place, but it looks like the devDependencies are not updated correctly. Please fix.
Workaround is to use npm install --legacy-peer-deps.
Solved with '@vercel/remix@2.9.2-patch.2'
|
gharchive/issue
| 2024-05-29T12:45:51 |
2025-04-01T04:36:13.514731
|
{
"authors": [
"styxlab"
],
"repo": "vercel/remix",
"url": "https://github.com/vercel/remix/issues/116",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2763329228
|
[.WATCH.]full—Your Fault (2024) [.FULLMOVIE.] Sci-fi/Action Now Available Online
𝟶𝟽 𝚖𝚒𝚗𝚜 𝚊𝚐𝚘 — [𝙱𝚕𝚘𝚌𝚔𝚋𝚞𝚜𝚝𝚎𝚛] 𝚆𝚒𝚝𝚑 𝚝𝚑𝚎 𝚛𝚒𝚜𝚎 𝚘𝚏 𝚘𝚗𝚕𝚒𝚗𝚎 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚙𝚕𝚊𝚝𝚏𝚘𝚛𝚖𝚜 𝚊𝚗𝚍 𝚠𝚎𝚋𝚜𝚒𝚝𝚎𝚜 𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍𝚒𝚗𝚐 𝚘𝚛 𝚆𝚊𝚝𝚌𝚑𝚒𝚗𝚐 Your Fault 2024 𝚖𝚘𝚟𝚒𝚎𝚜 𝚘𝚗𝚕𝚒𝚗𝚎 𝚏𝚘𝚛 𝚏𝚛𝚎𝚎 𝙳𝚘 𝚢𝚘𝚞 𝚕𝚒𝚔𝚎 𝚖𝚘𝚟𝚒𝚎𝚜? 𝙸𝚏 𝚜𝚘 𝚝𝚑𝚎𝚗 𝚢𝚘𝚞’𝚕𝚕 𝚕𝚘𝚟𝚎 𝙽𝚎𝚠 𝙱𝚘𝚡𝚘𝚏𝚏𝚒𝚌𝚎 𝙼𝚘𝚟𝚒𝚎: Your Fault 2024 𝚖𝚘𝚟𝚒𝚎 𝚒𝚜 𝚘𝚗𝚎 𝚘𝚏 𝚝𝚑𝚎 𝚋𝚎𝚜𝚝 𝚒𝚗 𝚒𝚝𝚜 𝚐𝚎𝚗𝚛𝚎 𝚆𝚎 𝚠𝚒𝚕𝚕 𝚐𝚞𝚒𝚍𝚎 𝚑𝚘𝚠 𝚝𝚘 𝚠𝚊𝚝𝚌𝚑 Your Fault 2024 𝚖𝚘𝚟𝚒𝚎𝚜 𝚘𝚗𝚕𝚒𝚗𝚎 𝚝𝚑𝚛𝚘𝚞𝚐𝚑 𝚟𝚊𝚛𝚒𝚘𝚞𝚜 𝚠𝚎𝚋𝚜𝚒𝚝𝚎𝚜, 𝚎𝚗𝚜𝚞𝚛𝚒𝚗𝚐 𝚊 𝚜𝚎𝚊𝚖𝚕𝚎𝚜𝚜 𝚊𝚗𝚍 𝚕𝚎𝚐𝚊𝚕 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚎𝚡𝚙𝚎𝚛𝚒𝚎𝚗𝚌𝚎. Your Fault 2024 𝚠𝚒𝚕𝚕 𝚋𝚎 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚝𝚘 𝚆𝚊𝚝𝚌𝚑 𝚘𝚗𝚕𝚒𝚗𝚎 𝚘𝚗 𝙽𝚎𝚝𝚏𝚕𝚒𝚡’𝚜 𝚟𝚎𝚛𝚢 𝚜𝚘𝚘𝚗! 𝙳𝚘𝚗'𝚝 𝚖Your Fault 2024 𝚘𝚞𝚝! #Your Fault 2024 𝙼𝚘𝚟𝚒𝚎
𝙸𝙵 𝚈𝙾𝚄’𝚁𝙴 𝙴𝚇𝙲𝙸𝚃𝙴𝙳 𝙰𝙱𝙾𝚄𝚃 𝚂𝙴𝙴𝙸𝙽𝙶 𝚂𝙷𝙰𝙳𝙾𝚆’𝚂 𝚃𝙷𝚁𝙸𝙻𝙻𝙸𝙽𝙶 𝙳𝙴𝙱𝚄𝚃, 𝙺𝙴𝙴𝙿 𝚁𝙴𝙰𝙳𝙸𝙽𝙶 𝙱𝙴𝙻𝙾𝚆 𝚃𝙾 𝙵𝙸𝙽𝙳 𝙾𝚄𝚃 𝙷𝙾𝚆 𝚈𝙾𝚄 𝙲𝙰𝙽 𝚆𝙰𝚃𝙲𝙷 𝚂𝙾𝙽𝙸𝙲 𝚃𝙷𝙴 𝙷𝙴𝙳𝙶𝙴𝙷𝙾𝙶 𝟹!
Your Fault 2024 𝘪𝘴 𝘢 2024 𝘈𝘮𝘦𝘳𝘪𝘤𝘢𝘯 𝘴𝘦𝘹 𝘤𝘰𝘮𝘦𝘥𝘺 𝘥𝘳𝘢𝘮𝘢 𝘧𝘪𝘭𝘮 𝘸𝘳𝘪𝘵𝘵𝘦𝘯, 𝘥𝘪𝘳𝘦𝘤𝘵𝘦𝘥, 𝘢𝘯𝘥 𝘦𝘥𝘪𝘵𝘦𝘥 𝘣𝘺 𝘚𝘦𝘢𝘯 𝘉𝘢𝘬𝘦𝘳.
𝚆𝚘𝚗𝚍𝚎𝚛𝚒𝚗𝚐 𝚑𝚘𝚠 𝚝𝚘 𝚆𝚊𝚝𝚌𝚑 Your Fault 2024 𝙾𝚗𝚕𝚒𝚗𝚎? 𝚆𝚎 𝚑𝚊𝚟𝚎 𝚊𝚕𝚕 𝚘𝚏 𝚝𝚑𝚎 𝚍𝚎𝚝𝚊𝚒𝚕𝚜 𝚘𝚗 𝚝𝚑𝚎 𝙻𝚊𝚝𝚎𝚜𝚝 𝙴𝚗𝚐𝚕𝚒𝚜𝚑 𝚊𝚗𝚍 𝙷𝚒𝚗𝚍𝚒 & 𝚃𝚊𝚖𝚒𝚕 𝚂𝚞𝚋 𝙼𝚘𝚟𝚒𝚎𝚜, 𝚏𝚛𝚘𝚖 𝚜𝚑𝚘𝚠𝚝𝚒𝚖𝚎𝚜 𝚝𝚘 𝚂𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚒𝚗𝚏𝚘.
Your Fault 2024 𝚛𝚎𝚕𝚎𝚊𝚜𝚎 𝚍𝚊𝚝𝚎 Your Fault 2024 𝚛𝚎𝚟𝚒𝚎𝚠𝚜 Your Fault 2024 𝙼𝚘𝚟𝚒𝚎 𝚛𝚊𝚝𝚒𝚗𝚐 Your Fault 2024 𝚛𝚊𝚝𝚒𝚗𝚐 Your Fault 2024 𝚋𝚘𝚡 𝚘𝚏𝚏𝚒𝚌𝚎 𝚌𝚘𝚕𝚕𝚎𝚌𝚝𝚒𝚘𝚗 Your Fault 2024 Your Fault 2024 F𝚞LL M𝚘𝚟𝚒𝚎 D𝚘𝚠𝚗𝚕𝚘A𝚍 IN T𝚊𝚖𝚒𝚕 M𝚘𝚟𝚒𝚎𝚜D𝚊 𝟽𝟸𝟶𝚙, 𝟺𝟾𝟶𝚙, 𝟷𝟶𝟾𝟶𝚙 Your Fault 2024 F𝚞L𝚕 M𝚘𝚟𝚒𝚎 D𝚘𝚠𝚗𝚕O𝚊𝚍 IN F𝚒𝚕𝚖𝚢𝚣𝚒𝚕𝚕𝚊 Your Fault 2024 𝚏𝚞𝚕𝚕 𝚖𝚘𝚟𝚒𝚎 𝚍𝚘𝚠𝚗𝚕𝚘𝚊𝚍 𝚒𝚗 𝚑𝚒𝚗𝚍𝚒 𝚏𝚒𝚕𝚖𝚢𝚠𝚊𝚙 𝚖𝚙𝟺𝚖𝚘𝚟𝚒𝚎𝚣 Your Fault 2024 𝚍𝚘𝚠𝚗𝚕𝚘𝚊𝚍 𝚔𝚞𝚝𝚝𝚢𝚖𝚘𝚟𝚒𝚎𝚜 Your Fault 2024 𝚛𝚎𝚟𝚒𝚎𝚠 Your Fault 2024 𝙼𝚘𝚟𝚒𝚎 𝚛𝚎𝚟𝚒𝚎𝚠 Your Fault 2024 𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍 𝙵𝚛𝚎𝚎 Your Fault 2024 𝙵𝚞𝙻𝙻𝙼𝚘𝚟𝚒𝚎 Your Fault 2024 𝙵𝚒𝚕𝙼𝚢𝚣𝚒𝚕𝚕𝚊 𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍 𝙵𝚛𝚎𝚎 𝟽𝟸𝟶𝚙 Your Fault 2024 𝚠𝚑𝚎𝚛𝚎 𝚝𝚘 𝚠𝚊𝚝𝚌𝚑 𝚗𝚎𝚝𝚏𝚕𝚒𝚡 𝚑𝚒𝚗𝚍𝚒 𝚖𝚘𝚟𝚒𝚎𝚜 𝚏𝚘𝚛 𝚏𝚛𝚎𝚎 Your Fault 2024 𝚍𝚘𝚠𝚗𝚕𝚘𝚊𝚍 𝚏𝚛𝚎𝚎 𝚏𝚒𝚕𝚖𝚢𝚣𝚒𝚕𝚕𝚊 𝚖𝚙𝟺𝚖𝚘𝚟𝚒𝚎𝚣 Your Fault 2024 𝚍𝚘𝚠𝚗𝚕𝚘𝚊𝚍 𝚏𝚛𝚎𝚎 𝚏𝚒𝚕𝚖𝚢𝚣𝚒𝚕𝚕𝚊 𝚑𝚒𝚗𝚍𝚒 𝚍𝚞𝚋𝚋𝚎𝚍 Your Fault 2024 𝚍𝚘𝚠𝚗𝚕𝚘𝚊𝚍 𝚏𝚛𝚎𝚎 𝚏𝚒𝚕𝚖𝚢𝚠𝚊𝚙 𝚒𝚗 𝚑𝚒𝚗𝚍𝚒 CAN I Your Fault 2024 D𝚘𝚠𝚗𝚕𝚘𝚊𝚍 𝚔𝚞𝚝𝚝𝚢𝚖𝚘𝚟𝚒𝚎𝚜 𝚒𝚗 𝚝𝚊𝚖𝚒𝚕𝚛𝚘𝚌𝚔𝚎𝚛𝚜
𝟻𝟾 𝚖𝚒𝚕𝚕𝚒𝚘𝚗 𝚏𝚛𝚘𝚖 𝚝𝚑𝚎 𝚁𝚘𝚋𝚘𝚝 𝙳𝚛𝚎𝚊𝚖𝚜𝚊𝚕 𝚊𝚏𝚝𝚎𝚛 𝚎𝚡𝚌𝚕𝚞𝚍𝚒𝚗𝚐 𝚝𝚑𝚎 𝚝𝚠𝚘 𝙼𝙸𝙰 𝚖𝚊𝚛𝚔𝚎𝚝𝚜 𝙸𝚝’𝚍 𝚋𝚎 𝚊𝚗𝚘𝚝𝚑𝚎𝚛 𝚜𝚝𝚘𝚛𝚢 𝚒𝚏 𝚊𝚞𝚍𝚒𝚎𝚗𝚌𝚎𝚜 𝚍𝚒𝚍𝚗’𝚝 𝚕𝚘𝚟𝚎 𝚝𝚑𝚎 𝚏𝚒𝚕𝚖 𝚋𝚞𝚝 𝚝𝚑𝚎 𝚙𝚘𝚜𝚒𝚝𝚒𝚟𝚎 𝚛𝚎𝚌𝚎𝚙𝚝𝚒𝚘𝚗 𝚜𝚞𝚐𝚐𝚎𝚜𝚝𝚜 𝚝𝚑𝚊𝚝 𝚆𝚊𝚔𝚊𝚗𝚍𝚊 𝙵𝚘𝚛𝚎𝚟𝚎𝚛 𝚠𝚒𝚕𝚕 𝚘𝚞𝚝𝚙𝚎𝚛𝚏𝚘𝚛𝚖 𝚝𝚑𝚎 𝚕𝚎𝚐𝚜 𝚘𝚗 𝚝𝚑𝚒𝚜 𝚢𝚎𝚊𝚛’𝚜 𝚎𝚊𝚛𝚕𝚒𝚎𝚛 𝙼𝙲𝚄 𝚝𝚒𝚝𝚕𝚎𝚜 (𝙼𝚞𝚕𝚝𝚒𝚟𝚎𝚛𝚜𝚎 𝚘𝚏 𝙼𝚊𝚍𝚗𝚎𝚜𝚜 𝚊𝚗𝚍 𝙻𝚘𝚟𝚎 𝚊𝚗𝚍 𝚃𝚑𝚞𝚗𝚍𝚎𝚛 𝚑𝚊𝚍 𝚖𝚞𝚕𝚝𝚒𝚙𝚕𝚒𝚎𝚛𝚜 𝚘𝚏 𝟸𝟸 𝚊𝚗𝚍 𝟸𝟹 𝚛𝚎𝚜𝚙𝚎𝚌𝚝𝚒𝚟𝚎𝚕𝚢)
𝚆𝙷𝙴𝙽 𝚆𝙸𝙻𝙻 'Your Fault 2024' 𝙱𝙴 𝙰𝚅𝙰𝙸𝙻𝙰𝙱𝙻𝙴 𝙾𝙽 𝙱𝙻𝚄-𝚁𝙰𝚈 𝙰𝙽𝙳 𝙳𝚅𝙳?
𝙰𝚜 𝚘𝚏 𝚛𝚒𝚐𝚑𝚝 𝚗𝚘𝚠, 𝚠𝚎 𝚍𝚘𝚗'𝚝 𝚔𝚗𝚘𝚠. 𝚆𝚑𝚒𝚕𝚎 𝚝𝚑𝚎 𝚏𝚒𝚕𝚖 𝚠𝚒𝚕𝚕 𝚎𝚟𝚎𝚗𝚝𝚞𝚊𝚕𝚕𝚢 𝚕𝚊𝚗𝚍 𝚘𝚗 𝙱𝚕𝚞-𝚛𝚊𝚢, 𝙳𝚅𝙳, 𝚊𝚗𝚍 𝟺𝙺 𝚄𝚕𝚝𝚛𝚊 𝙷𝙳, 𝚆𝚊𝚛𝚗𝚎𝚛 𝙱𝚛𝚘𝚜 𝚑𝚊𝚜 𝚢𝚎𝚝 𝚝𝚘 𝚛𝚎𝚟𝚎𝚊𝚕 𝚊 𝚜𝚙𝚎𝚌𝚒𝚏𝚒𝚌 𝚍𝚊𝚝𝚎 𝚊𝚜 𝚝𝚘 𝚠𝚑𝚎𝚗 𝚝𝚑𝚊𝚝 𝚠𝚘𝚞𝚕𝚍 𝚋𝚎. 𝚃𝚑𝚎 𝚏𝚒𝚛𝚜𝚝 𝙽𝚞𝚗 𝚏𝚒𝚕𝚖 𝚊𝚕𝚜𝚘 𝚙𝚛𝚎𝚖𝚒𝚎𝚛𝚎𝚍 𝚒𝚗 𝚝𝚑𝚎𝚊𝚝𝚎𝚛𝚜 𝚒𝚗 𝚎𝚊𝚛𝚕𝚢 𝚂𝚎𝚙𝚝𝚎𝚖𝚋𝚎𝚛 𝚊𝚗𝚍 𝚠𝚊𝚜 𝚛𝚎𝚕𝚎𝚊𝚜𝚎𝚍 𝚘𝚗 𝙱𝚕𝚞-𝚛𝚊𝚢 𝚊𝚗𝚍 𝙳𝚅𝙳 𝚒𝚗 𝙳𝚎𝚌𝚎𝚖𝚋𝚎𝚛. 𝙾𝚞𝚛 𝚋𝚎𝚜𝚝 𝚐𝚞𝚎𝚜𝚜 𝚒𝚜 𝚝𝚑𝚊𝚝 𝚝𝚑𝚎 𝚜𝚎𝚚𝚞𝚎𝚕 𝚠𝚒𝚕𝚕 𝚏𝚘𝚕𝚕𝚘𝚠 𝚊 𝚜𝚒𝚖𝚒𝚕𝚊𝚛 𝚙𝚊𝚝𝚑 𝚊𝚗𝚍 𝚠𝚒𝚕𝚕 𝚋𝚎 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚊𝚛𝚘𝚞𝚗𝚍 𝚝𝚑𝚎 𝚑𝚘𝚕𝚒𝚍𝚊𝚢 𝚜𝚎𝚊𝚜𝚘𝚗.
𝙷𝙴𝚁𝙴'𝚂 𝙷𝙾𝚆 𝚃𝙾 𝚆𝙰𝚃𝙲𝙷 'Your Fault 2024 ' 𝙾𝙽𝙻𝙸𝙽𝙴 𝚂𝚃𝚁𝙴𝙰𝙼𝙸𝙽𝙶 𝙸𝙽 𝙰𝚄𝚂𝚃𝚁𝙰𝙻𝙸𝙰 & 𝙽𝙴𝚆 𝚉𝙴𝙰𝙻𝙰𝙽𝙳
𝚃𝚘 𝚠𝚊𝚝𝚌𝚑 'Your Fault 2024' (𝟸𝟶𝟸𝟺) 𝚏𝚘𝚛 𝚏𝚛𝚎𝚎 𝚘𝚗𝚕𝚒𝚗𝚎 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚒𝚗 𝙰𝚞𝚜𝚝𝚛𝚊𝚕𝚒𝚊 𝚊𝚗𝚍 𝙽𝚎𝚠 𝚉𝚎𝚊𝚕𝚊𝚗𝚍, 𝚢𝚘𝚞 𝚌𝚊𝚗 𝚎𝚡𝚙𝚕𝚘𝚛𝚎 𝚘𝚙𝚝𝚒𝚘𝚗𝚜 𝚕𝚒𝚔𝚎 𝙽𝚎𝚝𝚏𝚕𝚒𝚡 𝚊𝚗𝚍 𝙷𝚞𝚕𝚞, 𝚊𝚜 𝚖𝚎𝚗𝚝𝚒𝚘𝚗𝚎𝚍 𝚒𝚗 𝚝𝚑𝚎 𝚜𝚎𝚊𝚛𝚌𝚑 𝚛𝚎𝚜𝚞𝚕𝚝𝚜. 𝙷𝚘𝚠𝚎𝚟𝚎𝚛, 𝚙𝚕𝚎𝚊𝚜𝚎 𝚗𝚘𝚝𝚎 𝚝𝚑𝚊𝚝 𝚝𝚑𝚎 𝚕𝚎𝚐𝚊𝚕𝚒𝚝𝚢 𝚊𝚗𝚍 𝚜𝚊𝚏𝚎𝚝𝚢 𝚘𝚏 𝚞𝚜𝚒𝚗𝚐 𝚜𝚞𝚌𝚑 𝚠𝚎𝚋𝚜𝚒𝚝𝚎𝚜 𝚖𝚊𝚢 𝚟𝚊𝚛𝚢, 𝚜𝚘 𝚎𝚡𝚎𝚛𝚌𝚒𝚜𝚎 𝚌𝚊𝚞𝚝𝚒𝚘𝚗 𝚠𝚑𝚎𝚗 𝚊𝚌𝚌𝚎𝚜𝚜𝚒𝚗𝚐 𝚝𝚑𝚎𝚖. 𝙰𝚍𝚍𝚒𝚝𝚒𝚘𝚗𝚊𝚕𝚕𝚢, 𝚢𝚘𝚞 𝚌𝚊𝚗 𝚌𝚑𝚎𝚌𝚔 𝚒𝚏 𝚝𝚑𝚎 𝚖𝚘𝚟𝚒𝚎 𝚒𝚜 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚘𝚗 𝚙𝚘𝚙𝚞𝚕𝚊𝚛 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚙𝚕𝚊𝚝𝚏𝚘𝚛𝚖𝚜 𝚕𝚒𝚔𝚎 𝙽𝚎𝚝𝚏𝚕𝚒𝚡, 𝙷𝚞𝚕𝚞, 𝚘𝚛 𝙰𝚖𝚊𝚣𝚘𝚗 𝙿𝚛𝚒𝚖𝚎 𝚅𝚒𝚍𝚎𝚘, 𝚊𝚜 𝚝𝚑𝚎𝚢 𝚘𝚏𝚝𝚎𝚗 𝚘𝚏𝚏𝚎𝚛 𝚊 𝚠𝚒𝚍𝚎 𝚜𝚎𝚕𝚎𝚌𝚝𝚒𝚘𝚗 𝚘𝚏 𝚖𝚘𝚟𝚒𝚎𝚜 𝚊𝚗𝚍 𝚃𝚅.
𝙼𝚊𝚛𝚔 𝚢𝚘𝚞𝚛 𝚌𝚊𝚕𝚎𝚗𝚍𝚊𝚛𝚜 𝚏𝚘𝚛 𝙹𝚞𝚕𝚢 𝟾𝚝𝚑, 𝚊𝚜 𝚝𝚑𝚊𝚝'𝚜 𝚠𝚑𝚎𝚗 Your Fault 2024 𝚠𝚒𝚕𝚕 𝚋𝚎 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚘𝚗 𝙳𝚒𝚜𝚗𝚎𝚢+. 𝚃𝚑𝚒𝚜 𝚑𝚒𝚐𝚑𝚕𝚢 𝚊𝚗𝚝𝚒𝚌𝚒𝚙𝚊𝚝𝚎𝚍 𝚒𝚗𝚜𝚝𝚊𝚕𝚕𝚖𝚎𝚗𝚝 𝚒𝚗 𝚝𝚑𝚎 𝚏𝚛𝚊𝚗𝚌𝚑𝚒𝚜𝚎 𝚒𝚜 𝚙𝚊𝚌𝚔𝚎𝚍 𝚠𝚒𝚝𝚑 𝚝𝚑𝚛𝚒𝚕𝚕𝚒𝚗𝚐 𝚊𝚌𝚝𝚒𝚘𝚗 𝚊𝚗𝚍 𝚊𝚍𝚟𝚎𝚗𝚝𝚞𝚛𝚎, 𝚙𝚛𝚘𝚖𝚒𝚜𝚒𝚗𝚐 𝚝𝚘 𝚌𝚊𝚙𝚝𝚒𝚟𝚊𝚝𝚎 𝚊𝚞𝚍𝚒𝚎𝚗𝚌𝚎𝚜 𝚊𝚗𝚍 𝚕𝚎𝚊𝚟𝚎 𝚝𝚑𝚎𝚖 𝚌𝚛𝚊𝚟𝚒𝚗𝚐 𝚏𝚘𝚛 𝚖𝚘𝚛𝚎. 𝙲𝚊𝚙𝚝𝚒𝚟𝚊𝚝𝚎 𝚊𝚞𝚍𝚒𝚎𝚗𝚌𝚎𝚜 𝚊𝚗𝚍 𝚕𝚎𝚊𝚟𝚎 𝚝𝚑𝚎𝚖 𝚌𝚛𝚊𝚟𝚒𝚗𝚐 𝚏𝚘𝚛 𝚖𝚘𝚛𝚎.
𝙷𝚎𝚛𝚎 𝚒𝚜 𝚊 𝚌𝚘𝚖𝚙𝚛𝚎𝚑𝚎𝚗𝚜𝚒𝚟𝚎 𝚐𝚞𝚒𝚍𝚎 𝚘𝚗 𝚑𝚘𝚠 𝚝𝚘 𝚠𝚊𝚝𝚌𝚑 Your Fault 2024 𝚘𝚗𝚕𝚒𝚗𝚎 𝚒𝚗 𝚒𝚝𝚜 𝚎𝚗𝚝𝚒𝚛𝚎𝚝𝚢 𝚏𝚛𝚘𝚖 𝚝𝚑𝚎 𝚌𝚘𝚖𝚏𝚘𝚛𝚝 𝚘𝚏 𝚢𝚘𝚞𝚛 𝚘𝚠𝚗 𝚑𝚘𝚖𝚎. 𝚈𝚘𝚞 𝚌𝚊𝚗 𝚊𝚌𝚌𝚎𝚜𝚜 𝚝𝚑𝚎 𝙵𝚞𝚕𝚕 𝙼𝚘𝚟𝚒𝚎 𝚏𝚛𝚎𝚎 𝚘𝚏 𝚌𝚑𝚊𝚛𝚐𝚎 𝚘𝚗 𝚝𝚑𝚎 𝚛𝚎𝚜𝚙𝚎𝚌𝚝𝚎𝚍 𝚙𝚕𝚊𝚝𝚏𝚘𝚛𝚖 𝚔𝚗𝚘𝚠𝚗 𝚊𝚜 𝟷𝟸𝟹𝙼𝚘𝚟𝚒𝚎𝚜. 𝙸𝚖𝚖𝚎𝚛𝚜𝚎 𝚢𝚘𝚞𝚛𝚜𝚎𝚕𝚏 𝚒𝚗 𝚝𝚑𝚎 𝚌𝚊𝚙𝚝𝚒𝚟𝚊𝚝𝚒𝚗𝚐 𝚎𝚡𝚙𝚎𝚛𝚒𝚎𝚗𝚌𝚎 𝚘𝚏 Your Fault 2024 𝚋𝚢 𝚠𝚊𝚝𝚌𝚑𝚒𝚗𝚐 𝚒𝚝 𝚘𝚗𝚕𝚒𝚗𝚎 𝚏𝚘𝚛 𝚏𝚛𝚎𝚎. 𝙰𝚕𝚝𝚎𝚛𝚗𝚊𝚝𝚒𝚟𝚎𝚕𝚢, 𝚢𝚘𝚞 𝚌𝚊𝚗 𝚊𝚕𝚜𝚘 𝚎𝚗𝚓𝚘𝚢 𝚝𝚑𝚎 𝚖𝚘𝚟𝚒𝚎 𝚋𝚢 𝚍𝚘𝚠𝚗𝚕𝚘𝚊𝚍𝚒𝚗𝚐 𝚒𝚝 𝚒𝚗 𝚑𝚒𝚐𝚑 𝚍𝚎𝚏𝚒𝚗𝚒𝚝𝚒𝚘𝚗. 𝙴𝚗𝚑𝚊𝚗𝚌𝚎 𝚢𝚘𝚞𝚛 𝚖𝚘𝚟𝚒𝚎 𝚟𝚒𝚎𝚠𝚒𝚗𝚐 𝚎𝚡𝚙𝚎𝚛𝚒𝚎𝚗𝚌𝚎 𝚋𝚢 𝚠𝚊𝚝𝚌𝚑𝚒𝚗𝚐 Your Fault 2024 𝚘𝚗 𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜, 𝚊 𝚝𝚛𝚞𝚜𝚝𝚎𝚍 𝚜𝚘𝚞𝚛𝚌𝚎 𝚏𝚘𝚛 𝚘𝚗𝚕𝚒𝚗𝚎 𝚖𝚘𝚟𝚒𝚎 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐.
𝙽𝚘𝚠 𝚒𝚜 Your Fault 2024 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚏𝚘𝚛 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐? 𝙲𝚊𝚗 𝚢𝚘𝚞 𝚠𝚊𝚝𝚌𝚑 𝚒𝚝 𝚘𝚗 𝙳𝚒𝚜𝚗𝚎𝚢 𝙿𝚕𝚞𝚜 𝙷𝙱𝙾 𝙼𝚊𝚡 𝙽𝚎𝚝𝚏𝚕𝚒𝚡 𝚘𝚛 𝙰𝚖𝚊𝚣𝚘𝚗 𝙿𝚛𝚒𝚖𝚎? 𝚈𝚎𝚜 𝚠𝚎 𝚑𝚊𝚟𝚎 𝚍𝚒𝚜𝚌𝚘𝚟𝚎𝚛𝚎𝚍 𝚊𝚗 𝚊𝚞𝚝𝚑𝚎𝚗𝚝𝚒𝚌 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚘𝚙𝚝𝚒𝚘𝚗 𝚘𝚛 𝚜𝚎𝚛𝚟𝚒𝚌𝚎 𝙰 𝟷𝟿𝟻𝟶𝚜 𝚑𝚘𝚞𝚜𝚎𝚠𝚒𝚏𝚎 𝚕𝚒𝚟𝚒𝚗𝚐 𝚒𝚗 𝚊 𝚞𝚝𝚘𝚙𝚒𝚊𝚗 𝚎𝚡𝚙𝚎𝚛𝚒𝚖𝚎𝚗𝚝𝚊𝚕 𝚌𝚘𝚖𝚖𝚞𝚗𝚒𝚝𝚢 𝚊𝚕𝚘𝚗𝚐𝚜𝚒𝚍𝚎 𝚑𝚎𝚛 𝚑𝚞𝚜𝚋𝚊𝚗𝚍 𝚋𝚎𝚌𝚘𝚖𝚎𝚜 𝚌𝚘𝚗𝚌𝚎𝚛𝚗𝚎𝚍 𝚝𝚑𝚊𝚝 𝚑𝚒𝚜 𝚐𝚕𝚊𝚖𝚘𝚛𝚘𝚞𝚜 𝚌𝚘𝚖𝚙𝚊𝚗𝚢 𝚖𝚊𝚢 𝚋𝚎 𝚌𝚘𝚗𝚌𝚎𝚊𝚕𝚒𝚗𝚐 𝚍𝚒𝚜𝚝𝚞𝚛𝚋𝚒𝚗𝚐 𝚜𝚎𝚌𝚛𝚎𝚝𝚜 𝙰𝚝 𝚂𝚑𝚘𝚠𝚌𝚊𝚜𝚎 𝙲𝚒𝚗𝚎𝚖𝚊 𝚆𝚊𝚛𝚠𝚒𝚌𝚔 𝚢𝚘𝚞 𝚠𝚒𝚕𝚕 𝚠𝚊𝚗𝚝 𝚝𝚘 𝚎𝚗𝚜𝚞𝚛𝚎 𝚝𝚑𝚊𝚝 𝚢𝚘𝚞 𝚊𝚛𝚎 𝚊𝚖𝚘𝚗𝚐 𝚝𝚑𝚎 𝚏𝚒𝚛𝚜𝚝 𝚝𝚘 𝚠𝚒𝚝𝚗𝚎𝚜𝚜 𝚒𝚝 𝚂𝚘 𝚖𝚊𝚛𝚔 𝚢𝚘𝚞𝚛 𝚌𝚊𝚕𝚎𝚗𝚍𝚊𝚛𝚜 𝚊𝚗𝚍 𝚙𝚛𝚎𝚙𝚊𝚛𝚎 𝚏𝚘𝚛 𝚊 𝚖𝚘𝚟𝚒𝚎 𝚎𝚡𝚙𝚎𝚛𝚒𝚎𝚗𝚌𝚎 𝚕𝚒𝚔𝚎 𝚗𝚎𝚟𝚎𝚛 𝚋𝚎𝚏𝚘𝚛𝚎 𝚠𝚒𝚝𝚑 Your Fault 2024 𝚆𝚎 𝚊𝚕𝚜𝚘 𝚑𝚊𝚟𝚎 𝚊 𝚟𝚊𝚛𝚒𝚎𝚝𝚢 𝚘𝚏 𝙼𝚊𝚛𝚟𝚎𝚕 𝚖𝚘𝚟𝚒𝚎𝚜 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚝𝚘 𝚠𝚊𝚝𝚌𝚑 𝚘𝚗𝚕𝚒𝚗𝚎 𝚆𝚎 𝚊𝚛𝚎 𝚌𝚘𝚗𝚏𝚒𝚍𝚎𝚗𝚝 𝚝𝚑𝚊𝚝 𝚢𝚘𝚞 𝚠𝚒𝚕𝚕 𝚏𝚒𝚗𝚍 𝚜𝚘𝚖𝚎𝚝𝚑𝚒𝚗𝚐 𝚝𝚘 𝚜𝚞𝚒𝚝 𝚢𝚘𝚞𝚛 𝚝𝚊𝚜𝚝𝚎 𝚃𝚑𝚊𝚗𝚔 𝚢𝚘𝚞 𝚏𝚘𝚛 𝚛𝚎𝚊𝚍𝚒𝚗𝚐 𝚊𝚗𝚍 𝚠𝚎 𝚕𝚘𝚘𝚔 𝚏𝚘𝚛𝚠𝚊𝚛𝚍 𝚝𝚘 𝚜𝚎𝚎𝚒𝚗𝚐 𝚢𝚘𝚞 𝚜𝚘𝚘𝚗! Your Fault 2024 𝚒𝚜 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚏𝚘𝚛 𝚏𝚛𝚎𝚎 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚘𝚗 𝚘𝚞𝚛 𝚠𝚎𝚋𝚜𝚒𝚝𝚎 𝙵𝚞𝚛𝚝𝚑𝚎𝚛 𝚍𝚎𝚝𝚊𝚒𝚕𝚜 𝚘𝚗 𝚑𝚘𝚠 𝚢𝚘𝚞 𝚌𝚊𝚗 𝚠𝚊𝚝𝚌𝚑 𝚒𝚝 𝚏𝚘𝚛 𝚏𝚛𝚎𝚎 𝚝𝚑𝚛𝚘𝚞𝚐𝚑𝚘𝚞𝚝 𝚝𝚑𝚎 𝚢𝚎𝚊𝚛 𝚊𝚛𝚎 𝚘𝚞𝚝𝚕𝚒𝚗𝚎𝚍 𝙸𝚏 𝚢𝚘𝚞 𝚊𝚛𝚎 𝚊 𝚏𝚊𝚗 𝚘𝚏 𝚝𝚑𝚎 𝚌𝚘𝚖𝚒𝚌𝚜 𝚢𝚘𝚞 𝚠𝚘𝚗𝚝 𝚠𝚊𝚗𝚝 𝚝𝚘 𝚖Your Fault 2024 𝚝𝚑𝚒𝚜 𝚘𝚗𝚎! 𝚃𝚑𝚎 𝚜𝚝𝚘𝚛𝚢𝚕𝚒𝚗𝚎 𝚏𝚘𝚕𝚕𝚘𝚠𝚜 Your Fault 2024 𝚊𝚜 𝚑𝚎 𝚗𝚊𝚟𝚒𝚐𝚊𝚝𝚎𝚜 𝚑𝚒𝚜 𝚠𝚊𝚢 𝚑𝚘𝚖𝚎 𝚊𝚏𝚝𝚎𝚛 𝚋𝚎𝚒𝚗𝚐 𝚜𝚝𝚛𝚊𝚗𝚍𝚎𝚍 𝚘𝚗 𝚊𝚗 𝚊𝚕𝚒𝚎𝚗 𝚙𝚕𝚊𝚗𝚎𝚝 𝚃𝚑𝚒𝚜 𝚖𝚘𝚟𝚒𝚎 𝚒𝚜 𝚞𝚗𝚍𝚘𝚞𝚋𝚝𝚎𝚍𝚕𝚢 𝚊 𝚖𝚞𝚜𝚝-𝚠𝚊𝚝𝚌𝚑 𝚐𝚒𝚟𝚎𝚗 𝚒𝚝𝚜 𝚜𝚝𝚞𝚗𝚗𝚒𝚗𝚐 𝚟𝚒𝚜𝚞𝚊𝚕𝚜 𝚊𝚗𝚍 𝚊𝚌𝚝𝚒𝚘𝚗-𝚙𝚊𝚌𝚔𝚎𝚍 𝚙𝚕𝚘𝚝! 𝙿𝚕𝚞𝚜 𝚢𝚘𝚞 𝚌𝚊𝚗 𝚜𝚝𝚛𝚎𝚊𝚖 Your Fault 2024 𝚘𝚗𝚕𝚒𝚗𝚎 𝚏𝚘𝚛 𝚏𝚛𝚎𝚎 𝚝𝚑𝚛𝚘𝚞𝚐𝚑 𝚘𝚞𝚛 𝚠𝚎𝚋𝚜𝚒𝚝𝚎 𝙸𝚝 𝚘𝚏𝚏𝚎𝚛𝚜 𝚟𝚊𝚛𝚒𝚘𝚞𝚜 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚘𝚙𝚝𝚒𝚘𝚗𝚜 𝚜𝚞𝚌𝚑 𝚊𝚜 𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜 𝚁𝚎𝚍𝚍𝚒𝚝 𝚘𝚛 𝚃𝚅 𝚜𝚑𝚘𝚠𝚜 𝚏𝚛𝚘𝚖 𝙷𝙱𝙾 𝙼𝚊𝚡 𝚘𝚛 𝙽𝚎𝚝𝚏𝚕𝚒𝚡 𝚃𝚑𝚎 𝚛𝚎𝚕𝚎𝚊𝚜𝚎 𝚍𝚊𝚝𝚎 𝚒𝚗 𝚝𝚑𝚎 𝚄𝚂 𝚏𝚘𝚛 Your Fault 2024 𝚒𝚜 𝚂𝚎𝚙𝚝𝚎𝚖𝚋𝚎𝚛 𝟸𝟽 𝟸𝟶𝟸𝟺 𝚈𝚘𝚞 𝚌𝚊𝚗 𝚙𝚞𝚛𝚌𝚑𝚊𝚜𝚎 𝚝𝚒𝚌𝚔𝚎𝚝𝚜 𝚝𝚘 𝚠𝚊𝚝𝚌𝚑 𝚝𝚑𝚎 𝚏𝚒𝚕𝚖 𝚊𝚝 𝚢𝚘𝚞𝚛 𝚕𝚘𝚌𝚊𝚕 𝚖𝚘𝚟𝚒𝚎 𝚝𝚑𝚎𝚊𝚝𝚎𝚛 𝚘𝚗𝚕𝚒𝚗𝚎 𝙸𝚝 𝚠𝚒𝚕𝚕 𝚋𝚎 𝚠𝚒𝚍𝚎𝚕𝚢 𝚛𝚎𝚕𝚎𝚊𝚜𝚎𝚍 𝚊𝚕𝚕𝚘𝚠𝚒𝚗𝚐 𝚢𝚘𝚞 𝚝𝚘 𝚟𝚒𝚎𝚠 𝚒𝚝 𝚒𝚗 𝚙𝚎𝚛𝚜𝚘𝚗 𝙸𝚏 𝚢𝚘𝚞 𝚠𝚊𝚗𝚝 𝚝𝚘 𝚠𝚊𝚝𝚌𝚑 Your Fault 2024 𝚏𝚘𝚛 𝚏𝚛𝚎𝚎 𝚌𝚘𝚗𝚜𝚒𝚍𝚎𝚛 𝚕𝚘𝚘𝚔𝚒𝚗𝚐 𝚏𝚘𝚛 𝚊 𝚙𝚕𝚊𝚝𝚏𝚘𝚛𝚖 𝚝𝚑𝚊𝚝 𝚘𝚏𝚏𝚎𝚛𝚜 𝚊 𝚏𝚛𝚎𝚎 𝚝𝚛𝚒𝚊𝚕 𝚆𝚎 𝚊𝚕𝚠𝚊𝚢𝚜 𝚊𝚍𝚟𝚒𝚜𝚎 𝚘𝚞𝚛 𝚛𝚎𝚊𝚍𝚎𝚛𝚜 𝚝𝚘 𝚙𝚊𝚢 𝚏𝚘𝚛 𝚝𝚑𝚎 𝚌𝚘𝚗𝚝𝚎𝚗𝚝 𝚝𝚑𝚎𝚢 Your Fault 2024 𝚝𝚘 𝚌𝚘𝚗𝚜𝚞𝚖𝚎 𝚘𝚗𝚕𝚒𝚗𝚎 𝚊𝚗𝚍 𝚛𝚎𝚏𝚛𝚊𝚒𝚗 𝚏𝚛𝚘𝚖 𝚞𝚜𝚒𝚗𝚐 𝚒𝚕𝚕𝚎𝚐𝚊𝚕 𝚖𝚎𝚊𝚗𝚜 𝙲𝚞𝚛𝚛𝚎𝚗𝚝𝚕𝚢 𝚝𝚑𝚎𝚛𝚎 𝚊𝚛𝚎 𝚗𝚘 𝚙𝚕𝚊𝚝𝚏𝚘𝚛𝚖𝚜 𝚝𝚑𝚊𝚝 𝚑𝚊𝚟𝚎 𝚝𝚑𝚎 𝚛𝚒𝚐𝚑𝚝𝚜 𝚝𝚘 𝚜𝚝𝚛𝚎𝚊𝚖 Your Fault 2024 𝚘𝚗𝚕𝚒𝚗𝚎 𝙼𝙰𝙿𝙿𝙰 𝚑𝚊𝚜 𝚍𝚎𝚌𝚒𝚍𝚎𝚍 𝚝𝚘 𝚎𝚡𝚌𝚕𝚞𝚜𝚒𝚟𝚎𝚕𝚢 𝚜𝚌𝚛𝚎𝚎𝚗 𝚝𝚑𝚎 𝚖𝚘𝚟𝚒𝚎 𝚒𝚗 𝚝𝚑𝚎𝚊𝚝𝚎𝚛𝚜 𝚍𝚞𝚎 𝚝𝚘 𝚒𝚝𝚜 𝚝𝚛𝚎𝚖𝚎𝚗𝚍𝚘𝚞𝚜 𝚜𝚞𝚌𝚌𝚎𝚜𝚜 𝚃𝚑𝚎 𝚜𝚝𝚞𝚍𝚒𝚘 𝚍𝚘𝚎𝚜 𝚗𝚘𝚝 Your Fault 2024 𝚝𝚘 𝚌𝚘𝚖𝚙𝚛𝚘𝚖𝚒𝚜𝚎 𝚝𝚑𝚎 𝚛𝚎𝚟𝚎𝚗𝚞𝚎 𝚊𝚜 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚝𝚑𝚎 𝚖𝚘𝚟𝚒𝚎 𝚠𝚘𝚞𝚕𝚍 𝚘𝚗𝚕𝚢 𝚍𝚒𝚖𝚒𝚗𝚒𝚜𝚑 𝚝𝚑𝚎 𝚙𝚛𝚘𝚏𝚒𝚝𝚜 𝚗𝚘𝚝 𝚎𝚗𝚑𝚊𝚗𝚌𝚎 𝚝𝚑𝚎𝚖 𝙽𝚘𝚗𝚎𝚝𝚑𝚎𝚕𝚎𝚜𝚜 𝚜𝚎𝚛𝚟𝚒𝚌𝚎𝚜 𝚕𝚒𝚔𝚎 𝙵𝚞𝚗𝚒𝚖𝚊𝚝𝚒𝚘𝚗 𝙽𝚎𝚝𝚏𝚕𝚒𝚡 𝚊𝚗𝚍 𝙲𝚛𝚞𝚗𝚌𝚑𝚢𝚛𝚘𝚕𝚕 𝚊𝚛𝚎 𝚟𝚎𝚛𝚢 𝚕𝚒𝚔𝚎𝚕𝚢 𝚝𝚘 𝚊𝚌𝚚𝚞𝚒𝚛𝚎 𝚝𝚑𝚎 𝚏𝚒𝚕𝚖 𝙸𝚗 𝚝𝚎𝚛𝚖𝚜 𝚘𝚏 𝚠𝚘𝚛𝚕𝚍𝚠𝚒𝚍𝚎 𝚍𝚒𝚜𝚝𝚛𝚒𝚋𝚞𝚝𝚒𝚘𝚗 𝚒𝚝 𝚒𝚜 𝚠𝚘𝚛𝚝𝚑 𝚌𝚘𝚗𝚜𝚒𝚍𝚎𝚛𝚒𝚗𝚐 𝚠𝚑𝚒𝚌𝚑 𝚘𝚏 𝚝𝚑𝚎𝚜𝚎 𝚘𝚞𝚝𝚕𝚎𝚝𝚜 𝚠𝚒𝚕𝚕 𝚖𝚘𝚜𝚝 𝚕𝚒𝚔𝚎𝚕𝚢 𝚘𝚋𝚝𝚊𝚒𝚗 𝚝𝚑𝚎 𝚛𝚒𝚐𝚑𝚝𝚜 𝚄𝚗𝚏𝚘𝚛𝚝𝚞𝚗𝚊𝚝𝚎𝚕𝚢 Your Fault 2024 𝚒𝚜 𝚗𝚘𝚝 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚘𝚗 𝙽𝚎𝚝𝚏𝚕𝚒𝚡 𝚆𝚑𝚒𝚕𝚎 𝚝𝚑𝚎 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚐𝚒𝚊𝚗𝚝 𝚘𝚏𝚏𝚎𝚛𝚜 𝚊𝚗 𝚎𝚡𝚝𝚎𝚗𝚜𝚒𝚟𝚎 𝚌𝚊𝚝𝚊𝚕𝚘𝚐 𝚘𝚏 𝚃𝚅 𝚜𝚑𝚘𝚠𝚜 𝚊𝚗𝚍 𝚖𝚘𝚟𝚒𝚎𝚜 𝚝𝚑𝚒𝚜 𝚙𝚊𝚛𝚝𝚒𝚌𝚞𝚕𝚊𝚛 𝚏𝚒𝚕𝚖 𝚒𝚜 𝚗𝚘𝚝 𝚒𝚗𝚌𝚕𝚞𝚍𝚎𝚍 𝚆𝚎 𝚛𝚎𝚌𝚘𝚖𝚖𝚎𝚗𝚍 𝚘𝚞𝚛 𝚛𝚎𝚊𝚍𝚎𝚛𝚜 𝚎𝚡𝚙𝚕𝚘𝚛𝚎 𝚘𝚝𝚑𝚎𝚛 𝚍𝚊𝚛𝚔 𝚏𝚊𝚗𝚝𝚊𝚜𝚢 𝚏𝚒𝚕𝚖𝚜 𝚜𝚞𝚌𝚑 𝚊𝚜 Your Fault 2024 𝙾𝚗 𝚝𝚑𝚎 𝚘𝚝𝚑𝚎𝚛 𝚑𝚊𝚗𝚍 𝙲𝚛𝚞𝚗𝚌𝚑𝚢𝚛𝚘𝚕𝚕 𝚊𝚕𝚘𝚗𝚐 𝚠𝚒𝚝𝚑 𝙵𝚞𝚗𝚒𝚖𝚊𝚝𝚒𝚘𝚗 𝚑𝚊𝚜 𝚜𝚎𝚌𝚞𝚛𝚎𝚍 𝚝𝚑𝚎 𝚛𝚒𝚐𝚑𝚝𝚜 𝚝𝚘 Your Fault 2024 𝚊𝚗𝚍 𝚠𝚒𝚕𝚕 𝚘𝚟𝚎𝚛𝚜𝚎𝚎 𝚒𝚝𝚜 𝚍𝚒𝚜𝚝𝚛𝚒𝚋𝚞𝚝𝚒𝚘𝚗 𝚒𝚗 𝙽𝚘𝚛𝚝𝚑 𝙰𝚖𝚎𝚛𝚒𝚌𝚊 𝚆𝚎 𝚊𝚍𝚟𝚒𝚜𝚎 𝚘𝚞𝚛 𝚛𝚎𝚊𝚍𝚎𝚛𝚜 𝚝𝚘 𝚔𝚎𝚎𝚙 𝚊𝚗 𝚎𝚢𝚎 𝚘𝚞𝚝 𝚏𝚘𝚛 𝚝𝚑𝚎 𝚖𝚘𝚟𝚒𝚎 𝚘𝚗 𝚝𝚑𝚒𝚜 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚙𝚕𝚊𝚝𝚏𝚘𝚛𝚖 𝚒𝚗 𝚝𝚑𝚎 𝚞𝚙𝚌𝚘𝚖𝚒𝚗𝚐 𝚖𝚘𝚗𝚝𝚑𝚜 𝙰𝚍𝚍𝚒𝚝𝚒𝚘𝚗𝚊𝚕𝚕𝚢 𝙲𝚛𝚞𝚗𝚌𝚑𝚢𝚛𝚘𝚕𝚕 𝚜𝚞𝚋𝚜𝚌𝚛𝚒𝚋𝚎𝚛𝚜 𝚌𝚊𝚗 𝚎𝚗𝚓𝚘𝚢 𝚍𝚊𝚛𝚔 𝚏𝚊𝚗𝚝𝚊𝚜𝚢 𝚜𝚑𝚘𝚠𝚜 𝚕𝚒𝚔𝚎 𝙹𝚞𝚓𝚞𝚝𝚜𝚞 𝙺𝚊𝚒𝚜𝚎𝚗 𝚄𝚗𝚏𝚘𝚛𝚝𝚞𝚗𝚊𝚝𝚎𝚕𝚢 Your Fault 2024 𝚒𝚜 𝚗𝚘𝚝 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚘𝚗 𝙷𝚞𝚕𝚞 𝙷𝚘𝚠𝚎𝚟𝚎𝚛 𝚜𝚞𝚋𝚜𝚌𝚛𝚒𝚋𝚎𝚛𝚜 𝚌𝚊𝚗 𝚒𝚗𝚍𝚞𝚕𝚐𝚎 𝚒𝚗 𝚝𝚒𝚝𝚕𝚎𝚜 𝚕𝚒𝚔𝚎 𝙰𝚏𝚛𝚘 𝚂𝚊𝚖𝚞𝚛𝚊𝚒 𝚁𝚎𝚜𝚞𝚛𝚛𝚎𝚌𝚝𝚒𝚘𝚗 𝚘𝚛 𝙽𝚒𝚗𝚓𝚊 𝚂𝚌𝚛𝚘𝚕𝚕 𝙰𝚜 𝚏𝚘𝚛 𝙰𝚖𝚊𝚣𝚘𝚗 𝙿𝚛𝚒𝚖𝚎 𝚝𝚑𝚎 𝚌𝚞𝚛𝚛𝚎𝚗𝚝 𝚜𝚎𝚕𝚎𝚌𝚝𝚒𝚘𝚗 𝚍𝚘𝚎𝚜 𝚗𝚘𝚝 𝚏𝚎𝚊𝚝𝚞𝚛𝚎 Your Fault 2024 𝙽𝚎𝚟𝚎𝚛𝚝𝚑𝚎𝚕𝚎𝚜𝚜 𝚝𝚑𝚎 𝚏𝚒𝚕𝚖 𝚖𝚊𝚢 𝚎𝚟𝚎𝚗𝚝𝚞𝚊𝚕𝚕𝚢 𝚋𝚎𝚌𝚘𝚖𝚎 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚘𝚗 𝚝𝚑𝚎 𝚙𝚕𝚊𝚝𝚏𝚘𝚛𝚖 𝚊𝚜 𝚊 𝚟𝚒𝚍𝚎𝚘-𝚘𝚗-𝚍𝚎𝚖𝚊𝚗𝚍 𝚘𝚙𝚝𝚒𝚘𝚗 𝚒𝚗 𝚝𝚑𝚎 𝚌𝚘𝚖𝚒𝚗𝚐 𝚖𝚘𝚗𝚝𝚑𝚜 𝙵𝚊𝚗𝚜 𝚘𝚏 𝚏𝚊𝚗𝚝𝚊𝚜𝚢 𝚖𝚘𝚟𝚒𝚎𝚜 𝚌𝚊𝚗 𝚎𝚡𝚙𝚕𝚘𝚛𝚎 𝙰𝚖𝚊𝚣𝚘𝚗 𝙿𝚛𝚒𝚖𝚎𝚜 𝚘𝚏𝚏𝚒𝚌𝚒𝚊𝚕 𝚠𝚎𝚋𝚜𝚒𝚝𝚎 𝚏𝚘𝚛 𝚜𝚒𝚖𝚒𝚕𝚊𝚛 𝚌𝚘𝚗𝚝𝚎𝚗𝚝 𝚒𝚗𝚌𝚕𝚞𝚍𝚒𝚗𝚐 𝚝𝚑𝚎 Your Fault 2024𝚊𝚕 𝚜𝚑𝚘𝚠 𝙳𝚘𝚛𝚘𝚛𝚘 Your Fault 2024 𝚝𝚑𝚎 𝚕𝚊𝚝𝚎𝚜𝚝 𝚊𝚍𝚍𝚒𝚝𝚒𝚘𝚗 𝚝𝚘 𝚝𝚑𝚎 𝚏𝚛𝚊𝚗𝚌𝚑𝚒𝚜𝚎 𝚠𝚒𝚕𝚕 𝚋𝚎 𝚌𝚘𝚖𝚒𝚗𝚐 𝚝𝚘 𝙳𝚒𝚜𝚗𝚎𝚢+ 𝚘𝚗 𝙵𝚎𝚋𝚛𝚞𝚊𝚛𝚢 𝟾𝚝𝚑! 𝚃𝚑𝚒𝚜 𝚎𝚡𝚌𝚒𝚝𝚒𝚗𝚐 𝚗𝚎𝚠 𝚖𝚘𝚟𝚒𝚎 𝚙𝚛𝚘𝚖𝚒𝚜𝚎𝚜 𝚝𝚘 𝚍𝚎𝚕𝚒𝚟𝚎𝚛 𝚝𝚑𝚎 𝚜𝚊𝚖𝚎 𝚕𝚎𝚟𝚎𝚕 𝚘𝚏 𝚝𝚑𝚛𝚒𝚕𝚕 𝚊𝚗𝚍 𝚊𝚍𝚟𝚎𝚗𝚝𝚞𝚛𝚎 𝚊𝚜 𝚒𝚝𝚜 𝚙𝚛𝚎𝚍𝚎𝚌𝚎𝚜𝚜𝚘𝚛𝚜 𝚔𝚎𝚎𝚙𝚒𝚗𝚐 𝚟𝚒𝚎𝚠𝚎𝚛𝚜 𝚌𝚊𝚙𝚝𝚒𝚟𝚊𝚝𝚎𝚍! 'Your Fault 2024' 𝚒𝚜 𝚙𝚕𝚊𝚢𝚒𝚗𝚐 𝚗𝚘𝚠 𝚒𝚗 𝚝𝚑𝚎𝚊𝚝𝚎𝚛𝚜 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚒𝚗 𝚠𝚘𝚛𝚕𝚍𝚠𝚒𝚍𝚎.𝟶𝟺 𝚖𝚒𝚗𝚜 𝚊𝚐𝚘 — [𝙱𝚕𝚘𝚌𝚔𝚋𝚞𝚜𝚝𝚎𝚛] 𝚆𝚒𝚝𝚑 𝚝𝚑𝚎 𝚛𝚒𝚜𝚎 𝚘𝚏 𝚘𝚗𝚕𝚒𝚗𝚎 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚙𝚕𝚊𝚝𝚏𝚘𝚛𝚖𝚜 𝚊𝚗𝚍 𝚠𝚎𝚋𝚜𝚒𝚝𝚎𝚜 𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍𝚒𝚗𝚐 𝚘𝚛 𝚆𝚊𝚝𝚌𝚑𝚒𝚗𝚐 Your Fault 2024 𝚖𝚘𝚟𝚒𝚎𝚜 𝚘𝚗𝚕𝚒𝚗𝚎 𝚏𝚘𝚛 𝚏𝚛𝚎𝚎 𝙳𝚘 𝚢𝚘𝚞 𝚕𝚒𝚔𝚎 𝚖𝚘𝚟𝚒𝚎𝚜? 𝙸𝚏 𝚜𝚘 𝚝𝚑𝚎𝚗 𝚢𝚘𝚞’𝚕𝚕 𝚕𝚘𝚟𝚎 𝙽𝚎𝚠 𝙱𝚘𝚡𝚘𝚏𝚏𝚒𝚌𝚎 𝙼𝚘𝚟𝚒𝚎: Your Fault 2024 𝚖𝚘𝚟𝚒𝚎 𝚒𝚜 𝚘𝚗𝚎 𝚘𝚏 𝚝𝚑𝚎 𝚋𝚎𝚜𝚝 𝚒𝚗 𝚒𝚝𝚜 𝚐𝚎𝚗𝚛𝚎 𝚆𝚎 𝚠𝚒𝚕𝚕 𝚐𝚞𝚒𝚍𝚎 𝚑𝚘𝚠 𝚝𝚘 𝚠𝚊𝚝𝚌𝚑 Your Fault 2024 𝚖𝚘𝚟𝚒𝚎𝚜 𝚘𝚗𝚕𝚒𝚗𝚎 𝚝𝚑𝚛𝚘𝚞𝚐𝚑 𝚟𝚊𝚛𝚒𝚘𝚞𝚜 𝚠𝚎𝚋𝚜𝚒𝚝𝚎𝚜, 𝚎𝚗𝚜𝚞𝚛𝚒𝚗𝚐 𝚊 𝚜𝚎𝚊𝚖𝚕𝚎𝚜𝚜 𝚊𝚗𝚍 𝚕𝚎𝚐𝚊𝚕 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚎𝚡𝚙𝚎𝚛𝚒𝚎𝚗𝚌𝚎. Your Fault 2024 𝚠𝚒𝚕𝚕 𝚋𝚎 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚝𝚘 𝚆𝚊𝚝𝚌𝚑 𝚘𝚗𝚕𝚒𝚗𝚎 𝚘𝚗 𝙽𝚎𝚝𝚏𝚕𝚒𝚡’𝚜 𝚟𝚎𝚛𝚢 𝚜𝚘𝚘𝚗! 𝙳𝚘𝚗'𝚝 𝚖Your Fault 2024 𝚘𝚞𝚝! #Your Fault 2024 𝙼𝚘𝚟𝚒𝚎
𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜 𝚆𝚊𝚝𝚌𝚑 Your Fault 2024 𝙾𝚗𝚕𝚒𝚗𝚎 𝙾𝚗 𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜
𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜 𝚆𝚊𝚝𝚌𝚑 Your Fault 2024) 𝙾𝚗𝚕𝚒𝚗𝚎 𝙾𝚗 𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜
[𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜] Your Fault 2024 𝙵𝚛𝚎𝚎 𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍 𝟽𝟸𝟶𝚙, 𝟺𝟾𝟶𝚙, 𝟷𝟶𝟾𝟶𝚙 𝙼𝚘𝚟𝚒𝚎
Your Fault 2024 𝚈𝚃𝚂 𝚃𝚘𝚛𝚛𝚎𝚗𝚝 - 𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍 𝚈𝚒𝚏𝚢 𝙼𝚘𝚟𝚒𝚎
!𝚠𝙰𝚝𝙲𝚑!^𝚝𝚟^ Your Fault 2024 𝙾𝚗𝚕𝚒𝚗𝚎 𝙾𝚗 𝟺𝙺 𝚖𝚘𝚟𝚒𝚎𝚜 {𝟿𝚀𝚄𝟶𝟽𝚆 }
[.𝚆𝙰𝚃𝙲𝙷.] Your Fault 2024 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚞𝚕𝚕 𝙷𝚒𝚗𝚍𝚒 𝙳𝚞𝚋𝚋𝚎𝚍 𝙵𝚛𝚎𝚎
[!𝚆𝚊𝚃𝚌𝙷^]] Your Fault 2024 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚞𝚕𝚕 𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜 𝙷𝙳 𝙵𝚛𝚎𝚎
𝚆𝚊𝚝𝚌𝚑 Your Fault 2024 (𝙵𝚛𝚎𝚎) 𝙵𝚞𝚕𝚕𝙼𝚘𝚟𝚒𝚎 𝙾𝚗𝚕𝚒𝚗𝚎 𝚘𝚗 𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜
[𝙾𝚏𝚏𝚒𝚌𝚒𝚊𝚕/𝚃𝚅]* Your Fault 2024 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚛𝚎𝚎 𝙱𝚛𝚘𝚊𝚍𝚌𝚊𝚜𝚝
Your Fault 2024 𝙵𝚞𝚕𝚕 𝙼𝚘𝚟𝚒𝚎 𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍 𝟸𝟶𝟸𝟺
𝙳𝙾𝚆𝙽𝙻𝙾𝙰𝙳# Your Fault 2024 𝙵𝚄𝙻𝙻 𝙼𝙾𝚅𝙸𝙴
Your Fault 2024 𝙵𝚛𝚎𝚎 𝙾𝚗𝚕𝚒𝚗𝚎 𝚂𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝙸𝚝𝚊𝚕𝚢
𝚆𝚊𝚝𝚌𝚑 Your Fault 2024 𝙾𝚗𝚕𝚒𝚗𝚎 𝚂𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝙽𝚘𝚠 𝚄𝚜𝚊
Your Fault 2024 𝙵𝚛𝚎𝚎 𝙾𝚗𝚕𝚒𝚗𝚎 𝚂𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝙵𝚛𝚊𝚗𝚌𝚎
Your Fault 2024 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚛𝚎𝚎 𝚂𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚊𝚝 𝚑𝚘𝚖𝚎
Your Fault 2024 𝙵𝚛𝚎𝚎 𝚘𝚗𝚕𝚒𝚗𝚎: 𝚆𝚑𝚎𝚛𝚎 𝚝𝚘 𝚠𝚊𝚝𝚌𝚑 𝚂𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐
Your Fault 2024 𝙵𝚛𝚎𝚎 𝙾𝚗𝚕𝚒𝚗𝚎 𝚂𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚂𝚠𝚒𝚝𝚣𝚎𝚛𝚕𝚊𝚗𝚍
𝚆𝙰𝚃𝙲𝙷 Your Fault 2024 𝙼𝚘𝚟𝚒𝚎 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚞𝚕𝚕 𝙵𝚛𝚎𝚎 𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍
𝚆𝚊𝚝𝚌𝚑 Your Fault 2024 𝙵𝚞𝚕𝚕 𝙴𝚗𝚐𝚕𝚒𝚜𝚑 𝙼𝚘𝚟𝚒𝚎
𝙵𝚁𝙴𝙴~𝙼𝚘𝚟𝚒𝚎𝚂!! 𝙷𝙳 𝚆𝚊𝚝𝚌𝚑 Your Fault 2024 𝙵𝚄𝙻𝙻 𝙼𝚘𝚟𝚒𝚎
𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍 Your Fault 2024 𝟸𝟶𝟸𝟺 𝚃𝚘𝚛𝚛𝚎𝚗𝚝 𝙼𝚘𝚟𝚒𝚎 𝙸𝚗 𝙷𝙳
Your Fault 2024 𝚈𝚃𝚂 𝚃𝚘𝚛𝚛𝚎𝚗𝚝 - 𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍 𝚈𝚒𝚏𝚢 𝙼𝚘𝚟𝚒𝚎
Your Fault 2024 𝚈𝙸𝙵𝚈 - 𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍 𝙼𝚘𝚟𝚒𝚎 𝚃𝙾𝚁𝚁𝙴𝙽𝚃 - 𝚈𝚃𝚂
𝚆𝚑𝚎𝚛𝚎 𝚝𝚘 𝚠𝚊𝚝𝚌𝚑 Your Fault 2024 𝚏𝚛𝚎𝚎 𝚘𝚗𝚕𝚒𝚗𝚎 𝚜𝚝𝚛𝚎𝚊𝚖
Your Fault 2024 𝚘𝚗𝚕𝚒𝚗𝚎 𝚏𝚘𝚛 𝚏𝚛𝚎𝚎 𝚊𝚝 𝚑𝚘𝚖𝚎
Your Fault 2024 𝚏𝚞𝚕𝚕 𝙵𝚒𝚕𝚖 𝙾𝚗𝚕𝚒𝚗𝚎
𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍 Your Fault 2024 𝙴𝚗𝚐𝚕𝚒𝚜𝚑 𝟺𝟾𝟶𝚙 𝟺𝟶𝟶𝙼𝙱
𝚠𝚊𝚝𝚌𝚑 Your Fault 2024 𝚏𝚛𝚎𝚎 𝙼𝚘𝚟𝚒𝚎 𝚘𝚗𝚕𝚒𝚗𝚎 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐
Your Fault 2024 𝙼𝚘𝚟𝚒𝚎 𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍 𝟺𝟾𝟶𝚙,𝟽𝟸𝟶𝚙,𝟷𝟶𝟾𝟶𝚙
Your Fault 2024 𝟸𝟶𝟸𝟺 𝙼𝚘𝚟𝚒𝚎 𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍 𝙵𝚛𝚎𝚎 𝟽𝟸𝟶𝚙
[𝙾𝚏𝚏𝚒𝚌𝚒𝚊𝚕.𝚂𝚝𝚘𝚛𝚎] 𝚆𝚊𝚝𝚌𝚑!! Your Fault 2024 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚘𝚛 𝚂𝚝𝚛𝚎𝚊𝚖
𝚆𝙰𝚃𝙲𝙷 ! Your Fault 2024 𝙼𝚘𝚟𝚒𝚎. (𝟸𝟶𝟸𝟺) (𝙵𝚞𝚕𝚕𝙼𝚘𝚟𝚒𝚎) 𝙵𝚛𝚎𝚎 𝚂𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚘𝚗 𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜
𝚆𝚑𝚎𝚛𝚎 𝚃𝚘 𝚆𝚊𝚝𝚌𝚑 ‘𝚁𝚘𝚋𝚘𝚝 𝙳𝚛𝚎𝚊𝚖𝚜’ 𝙵𝚞𝚕𝚕𝚖𝚘𝚟𝚒𝚎 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚛𝚎𝚎 𝚂𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚊𝚝 𝙷𝚘𝚖𝚎
𝙷𝚎𝚛𝚎'𝚜 𝚂𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 ‘𝚁𝚘𝚋𝚘𝚝 𝙳𝚛𝚎𝚊𝚖𝚜’ 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚞𝚕𝚕𝚖𝚘𝚟𝚒𝚎 𝚂𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝙵𝚛𝚎𝚎 𝚊𝚝 𝙷𝚘𝚖𝚎
𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜.! Your Fault 2024 𝙵𝚞𝚕𝚕 𝙼𝚘𝚟𝚒𝚎 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚛𝚎𝚎
𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜 (𝟺𝚔-𝚆𝚊𝚝𝚌𝚑) Your Fault 2024 𝙵𝚞𝚕𝚕𝙼𝚘𝚟𝚒𝚎 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚛𝚎𝚎
𝚆𝙰𝚃𝙲𝙷 Your Fault 2024 𝙵𝚞𝚕𝚕 𝙷𝙳 𝙼𝚘𝚟𝚒𝚎 𝙾𝚗𝚕𝚒𝚗𝚎 𝚂𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝙵𝚛𝚎𝚎
Your Fault 2024 𝚆𝚊𝚝𝚌𝚑 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚞𝚕𝚕 𝙼𝚘𝚟𝚒𝚎 𝙵𝚛𝚎𝚎 𝙷𝙳 𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍
𝚆𝚊𝚝𝚌𝚑 Your Fault 2024 𝙵𝚞𝚕𝚕 𝙼𝚘𝚟𝚒𝚎 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚛𝚎𝚎 𝙷𝙳
Your Fault 2024 𝙼𝚘𝚟𝚒𝚎 (𝟸𝟶𝟸𝟺) 𝙾𝚗𝚕𝚒𝚗𝚎 𝚂𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝙵𝚛𝚎𝚎
𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜-(.𝚆𝙰𝚃𝙲𝙷.) Your Fault 2024 𝙼𝚘𝚟𝚒𝚎 𝙾𝚗𝚕𝚒𝚗𝚎
𝚆𝙰𝚃𝙲𝙷 Your Fault 2024 𝙵𝚞𝚕𝚕 𝙷𝙳 𝙼𝚘𝚟𝚒𝚎 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚛𝚎𝚎
𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜-𝚆𝙰𝚃𝙲𝙷! Your Fault 2024 𝙼𝚘𝚟𝚒𝚎 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚞𝚕𝚕 𝙷𝙳 𝙵𝚛𝚎𝚎 𝙿𝚞𝚝𝚕𝚘𝚌𝚔𝚎𝚛
(𝙷𝙳-𝚆𝙰𝚃𝙲𝙷) Your Fault 2024 - 𝙵𝚞𝚕𝚕 𝙷𝙳 𝙵𝚛𝚎𝚎 𝟽𝟸𝟶𝚙 𝙾𝚗 𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜
𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜™ – Your Fault 2024 𝙷𝙳 𝙵𝚄𝙻𝙻 𝚆𝙰𝚃𝙲𝙷 𝙾𝙽𝙻𝙸𝙽𝙴 𝙵𝚁𝙴𝙴
[.𝚆𝙰𝚃𝙲𝙷.] Your Fault 2024 𝙼𝚘𝚟𝚒𝚎 𝙾𝚗𝚕𝚒𝚗𝚎 (𝟸𝟶𝟸𝟺) 𝙵𝚞𝚕𝚕 𝙷𝙳 𝙵𝚛𝚎𝚎 𝙳𝙾𝚆𝙽𝙻𝙾𝙰𝙳 𝙷𝙴𝚁𝙴-𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜
Your Fault 2024-𝙵𝚞𝚕𝚕 𝚆𝚊𝚝𝚌𝚑 𝙵𝚛𝚎𝚎 𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍: 𝙾𝙿𝙴𝙽𝙻𝙾𝚁𝙳
𝟺𝙺 (𝚆𝙰𝚃𝙲𝙷) Your Fault 2024 !! 𝟷𝟸𝟹𝙼𝚘𝚟𝚒𝚎𝚜 𝙾𝙽𝙻𝙸𝙽𝙴 𝚆𝙰𝚃𝙲𝙷 𝙼𝙾𝚅𝙸𝙴
Your Fault 2024 𝚆𝚊𝚝𝚌𝚑 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚞𝚕𝚕 𝙼𝚘𝚟𝚒𝚎 𝙵𝚛𝚎𝚎 𝙷𝙳 𝙳𝚘𝚠𝚗𝚕𝚘𝚊𝚍
𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜 𝚆𝚊𝚝𝚌𝚑 Your Fault 2024 𝙵𝚞𝚕𝚕𝙼𝚘𝚟𝚒𝚎 𝙾𝚗𝚕𝚒𝚗𝚎 𝙵𝚞𝚕𝚕 𝙵𝚛𝚎𝚎
𝙽𝚘𝚠 𝚒𝚜 Your Fault 2024 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚏𝚘𝚛 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐? 𝙲𝚊𝚗 𝚢𝚘𝚞 𝚠𝚊𝚝𝚌𝚑 𝚒𝚝 𝚘𝚗 𝙳𝚒𝚜𝚗𝚎𝚢 𝙿𝚕𝚞𝚜 𝙷𝙱𝙾 𝙼𝚊𝚡 𝙽𝚎𝚝𝚏𝚕𝚒𝚡 𝚘𝚛 𝙰𝚖𝚊𝚣𝚘𝚗 𝙿𝚛𝚒𝚖𝚎? 𝚈𝚎𝚜 𝚠𝚎 𝚑𝚊𝚟𝚎 𝚍𝚒𝚜𝚌𝚘𝚟𝚎𝚛𝚎𝚍 𝚊𝚗 𝚊𝚞𝚝𝚑𝚎𝚗𝚝𝚒𝚌 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚘𝚙𝚝𝚒𝚘𝚗 𝚘𝚛 𝚜𝚎𝚛𝚟𝚒𝚌𝚎 𝙰 𝟷𝟿𝟻𝟶𝚜 𝚑𝚘𝚞𝚜𝚎𝚠𝚒𝚏𝚎 𝚕𝚒𝚟𝚒𝚗𝚐 𝚒𝚗 𝚊 𝚞𝚝𝚘𝚙𝚒𝚊𝚗 𝚎𝚡𝚙𝚎𝚛𝚒𝚖𝚎𝚗𝚝𝚊𝚕 𝚌𝚘𝚖𝚖𝚞𝚗𝚒𝚝𝚢 𝚊𝚕𝚘𝚗𝚐𝚜𝚒𝚍𝚎 𝚑𝚎𝚛 𝚑𝚞𝚜𝚋𝚊𝚗𝚍 𝚋𝚎𝚌𝚘𝚖𝚎𝚜 𝚌𝚘𝚗𝚌𝚎𝚛𝚗𝚎𝚍 𝚝𝚑𝚊𝚝 𝚑𝚒𝚜 𝚐𝚕𝚊𝚖𝚘𝚛𝚘𝚞𝚜 𝚌𝚘𝚖𝚙𝚊𝚗𝚢 𝚖𝚊𝚢 𝚋𝚎 𝚌𝚘𝚗𝚌𝚎𝚊𝚕𝚒𝚗𝚐 𝚍𝚒𝚜𝚝𝚞𝚛𝚋𝚒𝚗𝚐 𝚜𝚎𝚌𝚛𝚎𝚝𝚜 𝙰𝚝 𝚂𝚑𝚘𝚠𝚌𝚊𝚜𝚎 𝙲𝚒𝚗𝚎𝚖𝚊 𝚆𝚊𝚛𝚠𝚒𝚌𝚔 𝚢𝚘𝚞 𝚠𝚒𝚕𝚕 𝚠𝚊𝚗𝚝 𝚝𝚘 𝚎𝚗𝚜𝚞𝚛𝚎 𝚝𝚑𝚊𝚝 𝚢𝚘𝚞 𝚊𝚛𝚎 𝚊𝚖𝚘𝚗𝚐 𝚝𝚑𝚎 𝚏𝚒𝚛𝚜𝚝 𝚝𝚘 𝚠𝚒𝚝𝚗𝚎𝚜𝚜 𝚒𝚝 𝚂𝚘 𝚖𝚊𝚛𝚔 𝚢𝚘𝚞𝚛 𝚌𝚊𝚕𝚎𝚗𝚍𝚊𝚛𝚜 𝚊𝚗𝚍 𝚙𝚛𝚎𝚙𝚊𝚛𝚎 𝚏𝚘𝚛 𝚊 𝚖𝚘𝚟𝚒𝚎 𝚎𝚡𝚙𝚎𝚛𝚒𝚎𝚗𝚌𝚎 𝚕𝚒𝚔𝚎 𝚗𝚎𝚟𝚎𝚛 𝚋𝚎𝚏𝚘𝚛𝚎 𝚠𝚒𝚝𝚑 Your Fault 2024 𝚆𝚎 𝚊𝚕𝚜𝚘 𝚑𝚊𝚟𝚎 𝚊 𝚟𝚊𝚛𝚒𝚎𝚝𝚢 𝚘𝚏 𝙼𝚊𝚛𝚟𝚎𝚕 𝚖𝚘𝚟𝚒𝚎𝚜 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚝𝚘 𝚠𝚊𝚝𝚌𝚑 𝚘𝚗𝚕𝚒𝚗𝚎 𝚆𝚎 𝚊𝚛𝚎 𝚌𝚘𝚗𝚏𝚒𝚍𝚎𝚗𝚝 𝚝𝚑𝚊𝚝 𝚢𝚘𝚞 𝚠𝚒𝚕𝚕 𝚏𝚒𝚗𝚍 𝚜𝚘𝚖𝚎𝚝𝚑𝚒𝚗𝚐 𝚝𝚘 𝚜𝚞𝚒𝚝 𝚢𝚘𝚞𝚛 𝚝𝚊𝚜𝚝𝚎 𝚃𝚑𝚊𝚗𝚔 𝚢𝚘𝚞 𝚏𝚘𝚛 𝚛𝚎𝚊𝚍𝚒𝚗𝚐 𝚊𝚗𝚍 𝚠𝚎 𝚕𝚘𝚘𝚔 𝚏𝚘𝚛𝚠𝚊𝚛𝚍 𝚝𝚘 𝚜𝚎𝚎𝚒𝚗𝚐 𝚢𝚘𝚞 𝚜𝚘𝚘𝚗! Your Fault 2024 𝚒𝚜 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚏𝚘𝚛 𝚏𝚛𝚎𝚎 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚘𝚗 𝚘𝚞𝚛 𝚠𝚎𝚋𝚜𝚒𝚝𝚎 𝙵𝚞𝚛𝚝𝚑𝚎𝚛 𝚍𝚎𝚝𝚊𝚒𝚕𝚜 𝚘𝚗 𝚑𝚘𝚠 𝚢𝚘𝚞 𝚌𝚊𝚗 𝚠𝚊𝚝𝚌𝚑 𝚒𝚝 𝚏𝚘𝚛 𝚏𝚛𝚎𝚎 𝚝𝚑𝚛𝚘𝚞𝚐𝚑𝚘𝚞𝚝 𝚝𝚑𝚎 𝚢𝚎𝚊𝚛 𝚊𝚛𝚎 𝚘𝚞𝚝𝚕𝚒𝚗𝚎𝚍 𝙸𝚏 𝚢𝚘𝚞 𝚊𝚛𝚎 𝚊 𝚏𝚊𝚗 𝚘𝚏 𝚝𝚑𝚎 𝚌𝚘𝚖𝚒𝚌𝚜 𝚢𝚘𝚞 𝚠𝚘𝚗𝚝 𝚠𝚊𝚗𝚝 𝚝𝚘 𝚖Your Fault 2024 𝚝𝚑𝚒𝚜 𝚘𝚗𝚎! 𝚃𝚑𝚎 𝚜𝚝𝚘𝚛𝚢𝚕𝚒𝚗𝚎 𝚏𝚘𝚕𝚕𝚘𝚠𝚜 Your Fault 2024 𝚊𝚜 𝚑𝚎 𝚗𝚊𝚟𝚒𝚐𝚊𝚝𝚎𝚜 𝚑𝚒𝚜 𝚠𝚊𝚢 𝚑𝚘𝚖𝚎 𝚊𝚏𝚝𝚎𝚛 𝚋𝚎𝚒𝚗𝚐 𝚜𝚝𝚛𝚊𝚗𝚍𝚎𝚍 𝚘𝚗 𝚊𝚗 𝚊𝚕𝚒𝚎𝚗 𝚙𝚕𝚊𝚗𝚎𝚝 𝚃𝚑𝚒𝚜 𝚖𝚘𝚟𝚒𝚎 𝚒𝚜 𝚞𝚗𝚍𝚘𝚞𝚋𝚝𝚎𝚍𝚕𝚢 𝚊 𝚖𝚞𝚜𝚝-𝚠𝚊𝚝𝚌𝚑 𝚐𝚒𝚟𝚎𝚗 𝚒𝚝𝚜 𝚜𝚝𝚞𝚗𝚗𝚒𝚗𝚐 𝚟𝚒𝚜𝚞𝚊𝚕𝚜 𝚊𝚗𝚍 𝚊𝚌𝚝𝚒𝚘𝚗-𝚙𝚊𝚌𝚔𝚎𝚍 𝚙𝚕𝚘𝚝! 𝙿𝚕𝚞𝚜 𝚢𝚘𝚞 𝚌𝚊𝚗 𝚜𝚝𝚛𝚎𝚊𝚖 Your Fault 2024 𝚘𝚗𝚕𝚒𝚗𝚎 𝚏𝚘𝚛 𝚏𝚛𝚎𝚎 𝚝𝚑𝚛𝚘𝚞𝚐𝚑 𝚘𝚞𝚛 𝚠𝚎𝚋𝚜𝚒𝚝𝚎 𝙸𝚝 𝚘𝚏𝚏𝚎𝚛𝚜 𝚟𝚊𝚛𝚒𝚘𝚞𝚜 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚘𝚙𝚝𝚒𝚘𝚗𝚜 𝚜𝚞𝚌𝚑 𝚊𝚜 𝟷𝟸𝟹𝚖𝚘𝚟𝚒𝚎𝚜 𝚁𝚎𝚍𝚍𝚒𝚝 𝚘𝚛 𝚃𝚅 𝚜𝚑𝚘𝚠𝚜 𝚏𝚛𝚘𝚖 𝙷𝙱𝙾 𝙼𝚊𝚡 𝚘𝚛 𝙽𝚎𝚝𝚏𝚕𝚒𝚡 𝚃𝚑𝚎 𝚛𝚎𝚕𝚎𝚊𝚜𝚎 𝚍𝚊𝚝𝚎 𝚒𝚗 𝚝𝚑𝚎 𝚄𝚂 𝚏𝚘𝚛 Your Fault 2024 𝚒𝚜 𝚂𝚎𝚙𝚝𝚎𝚖𝚋𝚎𝚛 𝟸𝟽 𝟸𝟶𝟸𝟺 𝚈𝚘𝚞 𝚌𝚊𝚗 𝚙𝚞𝚛𝚌𝚑𝚊𝚜𝚎 𝚝𝚒𝚌𝚔𝚎𝚝𝚜 𝚝𝚘 𝚠𝚊𝚝𝚌𝚑 𝚝𝚑𝚎 𝚏𝚒𝚕𝚖 𝚊𝚝 𝚢𝚘𝚞𝚛 𝚕𝚘𝚌𝚊𝚕 𝚖𝚘𝚟𝚒𝚎 𝚝𝚑𝚎𝚊𝚝𝚎𝚛 𝚘𝚗𝚕𝚒𝚗𝚎 𝙸𝚝 𝚠𝚒𝚕𝚕 𝚋𝚎 𝚠𝚒𝚍𝚎𝚕𝚢 𝚛𝚎𝚕𝚎𝚊𝚜𝚎𝚍 𝚊𝚕𝚕𝚘𝚠𝚒𝚗𝚐 𝚢𝚘𝚞 𝚝𝚘 𝚟𝚒𝚎𝚠 𝚒𝚝 𝚒𝚗 𝚙𝚎𝚛𝚜𝚘𝚗 𝙸𝚏 𝚢𝚘𝚞 𝚠𝚊𝚗𝚝 𝚝𝚘 𝚠𝚊𝚝𝚌𝚑 Your Fault 2024 𝚏𝚘𝚛 𝚏𝚛𝚎𝚎 𝚌𝚘𝚗𝚜𝚒𝚍𝚎𝚛 𝚕𝚘𝚘𝚔𝚒𝚗𝚐 𝚏𝚘𝚛 𝚊 𝚙𝚕𝚊𝚝𝚏𝚘𝚛𝚖 𝚝𝚑𝚊𝚝 𝚘𝚏𝚏𝚎𝚛𝚜 𝚊 𝚏𝚛𝚎𝚎 𝚝𝚛𝚒𝚊𝚕 𝚆𝚎 𝚊𝚕𝚠𝚊𝚢𝚜 𝚊𝚍𝚟𝚒𝚜𝚎 𝚘𝚞𝚛 𝚛𝚎𝚊𝚍𝚎𝚛𝚜 𝚝𝚘 𝚙𝚊𝚢 𝚏𝚘𝚛 𝚝𝚑𝚎 𝚌𝚘𝚗𝚝𝚎𝚗𝚝 𝚝𝚑𝚎𝚢 Your Fault 2024 𝚝𝚘 𝚌𝚘𝚗𝚜𝚞𝚖𝚎 𝚘𝚗𝚕𝚒𝚗𝚎 𝚊𝚗𝚍 𝚛𝚎𝚏𝚛𝚊𝚒𝚗 𝚏𝚛𝚘𝚖 𝚞𝚜𝚒𝚗𝚐 𝚒𝚕𝚕𝚎𝚐𝚊𝚕 𝚖𝚎𝚊𝚗𝚜 𝙲𝚞𝚛𝚛𝚎𝚗𝚝𝚕𝚢 𝚝𝚑𝚎𝚛𝚎 𝚊𝚛𝚎 𝚗𝚘 𝚙𝚕𝚊𝚝𝚏𝚘𝚛𝚖𝚜 𝚝𝚑𝚊𝚝 𝚑𝚊𝚟𝚎 𝚝𝚑𝚎 𝚛𝚒𝚐𝚑𝚝𝚜 𝚝𝚘 𝚜𝚝𝚛𝚎𝚊𝚖 Your Fault 2024 𝚘𝚗𝚕𝚒𝚗𝚎 𝙼𝙰𝙿𝙿𝙰 𝚑𝚊𝚜 𝚍𝚎𝚌𝚒𝚍𝚎𝚍 𝚝𝚘 𝚎𝚡𝚌𝚕𝚞𝚜𝚒𝚟𝚎𝚕𝚢 𝚜𝚌𝚛𝚎𝚎𝚗 𝚝𝚑𝚎 𝚖𝚘𝚟𝚒𝚎 𝚒𝚗 𝚝𝚑𝚎𝚊𝚝𝚎𝚛𝚜 𝚍𝚞𝚎 𝚝𝚘 𝚒𝚝𝚜 𝚝𝚛𝚎𝚖𝚎𝚗𝚍𝚘𝚞𝚜 𝚜𝚞𝚌𝚌𝚎𝚜𝚜 𝚃𝚑𝚎 𝚜𝚝𝚞𝚍𝚒𝚘 𝚍𝚘𝚎𝚜 𝚗𝚘𝚝 Your Fault 2024 𝚝𝚘 𝚌𝚘𝚖𝚙𝚛𝚘𝚖𝚒𝚜𝚎 𝚝𝚑𝚎 𝚛𝚎𝚟𝚎𝚗𝚞𝚎 𝚊𝚜 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚝𝚑𝚎 𝚖𝚘𝚟𝚒𝚎 𝚠𝚘𝚞𝚕𝚍 𝚘𝚗𝚕𝚢 𝚍𝚒𝚖𝚒𝚗𝚒𝚜𝚑 𝚝𝚑𝚎 𝚙𝚛𝚘𝚏𝚒𝚝𝚜 𝚗𝚘𝚝 𝚎𝚗𝚑𝚊𝚗𝚌𝚎 𝚝𝚑𝚎𝚖 𝙽𝚘𝚗𝚎𝚝𝚑𝚎𝚕𝚎𝚜𝚜 𝚜𝚎𝚛𝚟𝚒𝚌𝚎𝚜 𝚕𝚒𝚔𝚎 𝙵𝚞𝚗𝚒𝚖𝚊𝚝𝚒𝚘𝚗 𝙽𝚎𝚝𝚏𝚕𝚒𝚡 𝚊𝚗𝚍 𝙲𝚛𝚞𝚗𝚌𝚑𝚢𝚛𝚘𝚕𝚕 𝚊𝚛𝚎 𝚟𝚎𝚛𝚢 𝚕𝚒𝚔𝚎𝚕𝚢 𝚝𝚘 𝚊𝚌𝚚𝚞𝚒𝚛𝚎 𝚝𝚑𝚎 𝚏𝚒𝚕𝚖 𝙸𝚗 𝚝𝚎𝚛𝚖𝚜 𝚘𝚏 𝚠𝚘𝚛𝚕𝚍𝚠𝚒𝚍𝚎 𝚍𝚒𝚜𝚝𝚛𝚒𝚋𝚞𝚝𝚒𝚘𝚗 𝚒𝚝 𝚒𝚜 𝚠𝚘𝚛𝚝𝚑 𝚌𝚘𝚗𝚜𝚒𝚍𝚎𝚛𝚒𝚗𝚐 𝚠𝚑𝚒𝚌𝚑 𝚘𝚏 𝚝𝚑𝚎𝚜𝚎 𝚘𝚞𝚝𝚕𝚎𝚝𝚜 𝚠𝚒𝚕𝚕 𝚖𝚘𝚜𝚝 𝚕𝚒𝚔𝚎𝚕𝚢 𝚘𝚋𝚝𝚊𝚒𝚗 𝚝𝚑𝚎 𝚛𝚒𝚐𝚑𝚝𝚜 𝚄𝚗𝚏𝚘𝚛𝚝𝚞𝚗𝚊𝚝𝚎𝚕𝚢 Your Fault 2024 𝚒𝚜 𝚗𝚘𝚝 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚘𝚗 𝙽𝚎𝚝𝚏𝚕𝚒𝚡 𝚆𝚑𝚒𝚕𝚎 𝚝𝚑𝚎 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚐𝚒𝚊𝚗𝚝 𝚘𝚏𝚏𝚎𝚛𝚜 𝚊𝚗 𝚎𝚡𝚝𝚎𝚗𝚜𝚒𝚟𝚎 𝚌𝚊𝚝𝚊𝚕𝚘𝚐 𝚘𝚏 𝚃𝚅 𝚜𝚑𝚘𝚠𝚜 𝚊𝚗𝚍 𝚖𝚘𝚟𝚒𝚎𝚜 𝚝𝚑𝚒𝚜 𝚙𝚊𝚛𝚝𝚒𝚌𝚞𝚕𝚊𝚛 𝚏𝚒𝚕𝚖 𝚒𝚜 𝚗𝚘𝚝 𝚒𝚗𝚌𝚕𝚞𝚍𝚎𝚍 𝚆𝚎 𝚛𝚎𝚌𝚘𝚖𝚖𝚎𝚗𝚍 𝚘𝚞𝚛 𝚛𝚎𝚊𝚍𝚎𝚛𝚜 𝚎𝚡𝚙𝚕𝚘𝚛𝚎 𝚘𝚝𝚑𝚎𝚛 𝚍𝚊𝚛𝚔 𝚏𝚊𝚗𝚝𝚊𝚜𝚢 𝚏𝚒𝚕𝚖𝚜 𝚜𝚞𝚌𝚑 𝚊𝚜 Your Fault 2024 𝙾𝚗 𝚝𝚑𝚎 𝚘𝚝𝚑𝚎𝚛 𝚑𝚊𝚗𝚍 𝙲𝚛𝚞𝚗𝚌𝚑𝚢𝚛𝚘𝚕𝚕 𝚊𝚕𝚘𝚗𝚐 𝚠𝚒𝚝𝚑 𝙵𝚞𝚗𝚒𝚖𝚊𝚝𝚒𝚘𝚗 𝚑𝚊𝚜 𝚜𝚎𝚌𝚞𝚛𝚎𝚍 𝚝𝚑𝚎 𝚛𝚒𝚐𝚑𝚝𝚜 𝚝𝚘 Your Fault 2024 𝚊𝚗𝚍 𝚠𝚒𝚕𝚕 𝚘𝚟𝚎𝚛𝚜𝚎𝚎 𝚒𝚝𝚜 𝚍𝚒𝚜𝚝𝚛𝚒𝚋𝚞𝚝𝚒𝚘𝚗 𝚒𝚗 𝙽𝚘𝚛𝚝𝚑 𝙰𝚖𝚎𝚛𝚒𝚌𝚊 𝚆𝚎 𝚊𝚍𝚟𝚒𝚜𝚎 𝚘𝚞𝚛 𝚛𝚎𝚊𝚍𝚎𝚛𝚜 𝚝𝚘 𝚔𝚎𝚎𝚙 𝚊𝚗 𝚎𝚢𝚎 𝚘𝚞𝚝 𝚏𝚘𝚛 𝚝𝚑𝚎 𝚖𝚘𝚟𝚒𝚎 𝚘𝚗 𝚝𝚑𝚒𝚜 𝚜𝚝𝚛𝚎𝚊𝚖𝚒𝚗𝚐 𝚙𝚕𝚊𝚝𝚏𝚘𝚛𝚖 𝚒𝚗 𝚝𝚑𝚎 𝚞𝚙𝚌𝚘𝚖𝚒𝚗𝚐 𝚖𝚘𝚗𝚝𝚑𝚜 𝙰𝚍𝚍𝚒𝚝𝚒𝚘𝚗𝚊𝚕𝚕𝚢 𝙲𝚛𝚞𝚗𝚌𝚑𝚢𝚛𝚘𝚕𝚕 𝚜𝚞𝚋𝚜𝚌𝚛𝚒𝚋𝚎𝚛𝚜 𝚌𝚊𝚗 𝚎𝚗𝚓𝚘𝚢 𝚍𝚊𝚛𝚔 𝚏𝚊𝚗𝚝𝚊𝚜𝚢 𝚜𝚑𝚘𝚠𝚜 𝚕𝚒𝚔𝚎 𝙹𝚞𝚓𝚞𝚝𝚜𝚞 𝙺𝚊𝚒𝚜𝚎𝚗 𝚄𝚗𝚏𝚘𝚛𝚝𝚞𝚗𝚊𝚝𝚎𝚕𝚢 Your Fault 2024 𝚒𝚜 𝚗𝚘𝚝 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚘𝚗 𝙷𝚞𝚕𝚞 𝙷𝚘𝚠𝚎𝚟𝚎𝚛 𝚜𝚞𝚋𝚜𝚌𝚛𝚒𝚋𝚎𝚛𝚜 𝚌𝚊𝚗 𝚒𝚗𝚍𝚞𝚕𝚐𝚎 𝚒𝚗 𝚝𝚒𝚝𝚕𝚎𝚜 𝚕𝚒𝚔𝚎 𝙰𝚏𝚛𝚘 𝚂𝚊𝚖𝚞𝚛𝚊𝚒 𝚁𝚎𝚜𝚞𝚛𝚛𝚎𝚌𝚝𝚒𝚘𝚗 𝚘𝚛 𝙽𝚒𝚗𝚓𝚊 𝚂𝚌𝚛𝚘𝚕𝚕 𝙰𝚜 𝚏𝚘𝚛 𝙰𝚖𝚊𝚣𝚘𝚗 𝙿𝚛𝚒𝚖𝚎 𝚝𝚑𝚎 𝚌𝚞𝚛𝚛𝚎𝚗𝚝 𝚜𝚎𝚕𝚎𝚌𝚝𝚒𝚘𝚗 𝚍𝚘𝚎𝚜 𝚗𝚘𝚝 𝚏𝚎𝚊𝚝𝚞𝚛𝚎 Your Fault 2024 𝙽𝚎𝚟𝚎𝚛𝚝𝚑𝚎𝚕𝚎𝚜𝚜 𝚝𝚑𝚎 𝚏𝚒𝚕𝚖 𝚖𝚊𝚢 𝚎𝚟𝚎𝚗𝚝𝚞𝚊𝚕𝚕𝚢 𝚋𝚎𝚌𝚘𝚖𝚎 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚘𝚗 𝚝𝚑𝚎 𝚙𝚕𝚊𝚝𝚏𝚘𝚛𝚖 𝚊𝚜 𝚊 𝚟𝚒𝚍𝚎𝚘-𝚘𝚗-𝚍𝚎𝚖𝚊𝚗𝚍 𝚘𝚙𝚝𝚒𝚘𝚗 𝚒𝚗 𝚝𝚑𝚎 𝚌𝚘𝚖𝚒𝚗𝚐 𝚖𝚘𝚗𝚝𝚑𝚜 𝙵𝚊𝚗𝚜 𝚘𝚏 𝚏𝚊𝚗𝚝𝚊𝚜𝚢 𝚖𝚘𝚟𝚒𝚎𝚜 𝚌𝚊𝚗 𝚎𝚡𝚙𝚕𝚘𝚛𝚎 𝙰𝚖𝚊𝚣𝚘𝚗 𝙿𝚛𝚒𝚖𝚎𝚜 𝚘𝚏𝚏𝚒𝚌𝚒𝚊𝚕 𝚠𝚎𝚋𝚜𝚒𝚝𝚎 𝚏𝚘𝚛 𝚜𝚒𝚖𝚒𝚕𝚊𝚛 𝚌𝚘𝚗𝚝𝚎𝚗𝚝 𝚒𝚗𝚌𝚕𝚞𝚍𝚒𝚗𝚐 𝚝𝚑𝚎 Your Fault 2024𝚊𝚕 𝚜𝚑𝚘𝚠 𝙳𝚘𝚛𝚘𝚛𝚘 Your Fault 2024 𝚝𝚑𝚎 𝚕𝚊𝚝𝚎𝚜𝚝 𝚊𝚍𝚍𝚒𝚝𝚒𝚘𝚗 𝚝𝚘 𝚝𝚑𝚎 𝚏𝚛𝚊𝚗𝚌𝚑𝚒𝚜𝚎 𝚠𝚒𝚕𝚕 𝚋𝚎 𝚌𝚘𝚖𝚒𝚗𝚐 𝚝𝚘 𝙳𝚒𝚜𝚗𝚎𝚢+ 𝚘𝚗 𝙵𝚎𝚋𝚛𝚞𝚊𝚛𝚢 𝟾𝚝𝚑! 𝚃𝚑𝚒𝚜 𝚎𝚡𝚌𝚒𝚝𝚒𝚗𝚐 𝚗𝚎𝚠 𝚖𝚘𝚟𝚒𝚎 𝚙𝚛𝚘𝚖𝚒𝚜𝚎𝚜 𝚝𝚘 𝚍𝚎𝚕𝚒𝚟𝚎𝚛 𝚝𝚑𝚎 𝚜𝚊𝚖𝚎 𝚕𝚎𝚟𝚎𝚕 𝚘𝚏 𝚝𝚑𝚛𝚒𝚕𝚕 𝚊𝚗𝚍 𝚊𝚍𝚟𝚎𝚗𝚝𝚞𝚛𝚎 𝚊𝚜 𝚒𝚝𝚜 𝚙𝚛𝚎𝚍𝚎𝚌𝚎𝚜𝚜𝚘𝚛𝚜 𝚔𝚎𝚎𝚙𝚒𝚗𝚐 𝚟𝚒𝚎𝚠𝚎𝚛𝚜 𝚌𝚊𝚙𝚝𝚒𝚟𝚊𝚝𝚎𝚍! 'Your Fault 2024' 𝚒𝚜 𝚙𝚕𝚊𝚢𝚒𝚗𝚐 𝚗𝚘𝚠 𝚒𝚗 𝚝𝚑𝚎𝚊𝚝𝚎𝚛𝚜 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚒𝚗 𝚠𝚘𝚛𝚕𝚍𝚠𝚒𝚍𝚎.𝚛𝚜 𝚊𝚟𝚊𝚒𝚕𝚊𝚋𝚕𝚎 𝚒𝚗 𝚠𝚘𝚛𝚕𝚍𝚠𝚒𝚍𝚎.
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
xdw
◑﹏◐
ALL TV LIVE
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
👉⏩🎥🅻🅸🆅🅴🔴▶️ ✅🟢 STREAM PLAY NOW ▶️
.
👉⏩🎥🆆🅰🆃🅲🅷🔴▶️ ✅🟢 PLAY NOW ONLINE
xdw
|
gharchive/issue
| 2024-12-30T14:59:15 |
2025-04-01T04:36:13.605406
|
{
"authors": [
"shizfs",
"tmakhs"
],
"repo": "vercel/swr",
"url": "https://github.com/vercel/swr/issues/3318",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2364783782
|
fix(turbopack): add no-op resolveAbsolutePath to browser runtime
Description
Reading import.meta.hot should work in the browser, it can just return a /ROOT/... path.
Fixes https://github.com/vercel/next.js/issues/66005
@sokra I don't think we have a way to do an execution test with the browser runtime, do we?
|
gharchive/pull-request
| 2024-06-20T15:57:23 |
2025-04-01T04:36:13.629579
|
{
"authors": [
"ForsakenHarmony"
],
"repo": "vercel/turbo",
"url": "https://github.com/vercel/turbo/pull/8549",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2756543710
|
docker publish fails because fetch request doesnt resolve
I have a multi stage docker image in a docker-compose. When I attempt to publish to verdaccio, publishes fail because a fetch isn't resolving.
I am on version 6, but this also happened on version 5 of verdaccio.
FROM build AS publish
RUN pnpm changeset pre enter beta
RUN pnpm changeset version
RUN NPM_CONFIG_REGISTRY=http://0.0.0.0:4873 pnpm -r publish --tag beta
RUN pnpm changeset pre exit
Running this stage here, I get a failure on the first package (None of the packages exist on npm at this time)
70.59 npm notice Publishing to http://localhost:4873/ with tag beta and restricted access
140.6 npm error code ECONNREFUSED
140.6 npm error errno ECONNREFUSED
140.6 npm error FetchError: request to http://localhost:4873/@mypackage failed, reason:
140.6 npm error at ClientRequest.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:130:14)
140.6 npm error at ClientRequest.emit (node:events:518:28)
140.6 npm error at emitErrorEvent (node:_http_client:101:11)
140.6 npm error at _destroy (node:_http_client:884:9)
140.6 npm error at onSocketNT (node:_http_client:904:5)
140.6 npm error at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {
140.6 npm error code: 'ECONNREFUSED',
140.6 npm error errno: 'ECONNREFUSED',
140.6 npm error type: 'system'
140.6 npm error }
140.6 npm error
140.6 npm error If you are behind a proxy, please make sure that the
140.6 npm error 'proxy' config is set properly. See: 'npm help config'
140.6 npm error A complete log of this run can be found in: /root/.npm/_logs/2024-12-23T18_24_37_665Z-debug-0.log
The docker compose file uses the verdaccio image.
networks:
npm-network:
driver: bridge
services:
services:
verdaccio:
image: verdaccio/verdaccio
ports:
- '4873:4873'
volumes:
- ./tmp/local-registry/storage:/verdaccio/storage
- './.verdaccio:/verdaccio/conf'
- './.verdaccio/config.yml:/verdaccio/conf/config.yaml'
environment:
- VERDACCIO_PORT=4873
- NPM_CONFIG_LOGLEVEL=info
packages:
build:
context: .
dockerfile: Dockerfile
depends_on:
- verdaccio
environment:
- NPM_REGISTRY=http://0.0.0.0:4873
volumes:
- .:/app
ports:
- '3000:3000'
volumes:
verdaccio-storage:
verdaccio-config:
It's a bit of a weird error - my suspicion is that because these packages do not exist, it doesn't resolve after proxying. But i'm not sure why that matters in this case.
I think you are missing the server log, you can check what's going there and if is need it increase the debug (see the wiki about how to do it). Aside from that seems non an issue in verdaccio.
From the npm log it looks like you use --access restricted but I don't see this anywhere else. Verdaccio doesn't support this "org/team" option.
As stated above, the Verdaccio log should tell you more (esp with DEBUG env set)
Hey - thanks for responses. You are right about the restricted part.
The interesting thing is that verdaccio works perfectly fine if i just deploy the verdaccio instance - and then try to publish from a new terminal.
So
docker compose up
new terminal publish, works great.
But my goal was really to automate this, so i was hoping to docker compose up which would run every step including publishing the packages.
When I try to publish from within the docker image, that error is occuring still. The tricky part is, it seems to swallow the debug logs so I can't really get them.
I see the debug logs if I just "spawn" verdaccio from my docker image, but once I start running new commands it seems to error.
I'm not a docker expert - i'm guessing I need to adjust a few things but I can report back if I can get some real logs for you. It seems like its not a verdaccio issue and more a my docker inexperience showing.
Was able to resolve it, sorry and thanks
|
gharchive/issue
| 2024-12-23T18:32:03 |
2025-04-01T04:36:13.635692
|
{
"authors": [
"juanpicado",
"mbtools",
"ryanbas21"
],
"repo": "verdaccio/verdaccio",
"url": "https://github.com/verdaccio/verdaccio/issues/5017",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1095383286
|
Swagger parser error
Als ik vanuit de README.md op het vastgoed linkje (onder Informatiedomeinen) klik, navigeert de browser naar https://vereniging-corponet.github.io/vera-openapi/Informatiedomeinen/Vastgoed.html. Op die Swagger pagina wordt een foutmelding getoond:
Parser error on line 5917
duplicated mapping key
Bedankt, is opgelost nu.
|
gharchive/issue
| 2022-01-06T14:40:40 |
2025-04-01T04:36:13.655385
|
{
"authors": [
"peterjanvandeput",
"shtrip"
],
"repo": "vereniging-corponet/vera-openapi",
"url": "https://github.com/vereniging-corponet/vera-openapi/issues/1",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
865229885
|
openclash设置页面更新的规则集和Dashboard里更新的规则集不一样吗？
openclash设置页面更新的规则集和Dashboard里更新的规则集不一样吗？
我在openclash设置页面下载了规则集，可以看到在rule-providers文件夹下看到对应文件会更新;但是在Dashboard里的规则页面点同意规则集更新后，在rule-providers看不到更新。
你先确认配置文件里面有没有写进去
|
gharchive/issue
| 2021-04-22T17:25:40 |
2025-04-01T04:36:13.687243
|
{
"authors": [
"vernesong",
"yanggis"
],
"repo": "vernesong/OpenClash",
"url": "https://github.com/vernesong/OpenClash/issues/1366",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2047391990
|
[Bug] 错误：绕过代理服务器地址设置失败，【undefined method `each' for nil:NilClass】
Verify Steps
[X] Tracker 我已经在 Issue Tracker 中找过我要提出的问题
[X] Latest 我已经使用最新 Dev 版本测试过，问题依旧存在
[X] Core 这是 OpenClash 存在的问题，并非我所使用的 Clash 或 Meta 等内核的特定问题
[X] Meaningful 我提交的不是无意义的 催促更新或修复 请求
OpenClash Version
v0.45.16-beta
Bug on Environment
Official OpenWrt
Bug on Platform
Linux-mipsle-softfloat
To Reproduce
2023-12-19 03:51:31 错误：绕过代理服务器地址设置失败，【undefined method each' for nil:NilClass】 2023-12-19 03:51:31 错误：绕过代理服务器地址设置失败，【undefined method each' for nil:NilClass】
2023-12-19 03:51:31 错误：绕过代理服务器地址设置失败，【undefined method each' for nil:NilClass】 2023-12-19 03:51:31 错误：绕过代理服务器地址设置失败，【undefined method each' for nil:NilClass】
2023-12-19 03:51:31 错误：绕过代理服务器地址设置失败，【undefined method each' for nil:NilClass】 2023-12-19 03:51:31 错误：绕过代理服务器地址设置失败，【undefined method each' for nil:NilClass】
2023-12-19 03:51:31 错误：绕过代理服务器地址设置失败，【undefined method each' for nil:NilClass】 2023-12-19 03:51:31 错误：绕过代理服务器地址设置失败，【undefined method each' for nil:NilClass】
2023-12-19 03:51:31 错误：绕过代理服务器地址设置失败，【undefined method each' for nil:NilClass】 2023-12-19 03:51:31 错误：绕过代理服务器地址设置失败，【undefined method each' for nil:NilClass】
2023-12-19 03:51:31 错误：绕过代理服务器地址设置失败，【undefined method each' for nil:NilClass】 2023-12-19 03:51:31 错误：绕过代理服务器地址设置失败，【undefined method each' for nil:NilClass】
2023-12-19 03:51:31 错误：绕过代理服务器地址设置失败，【undefined method each' for nil:NilClass】 2023-12-19 03:51:31 错误：绕过代理服务器地址设置失败，【undefined method each' for nil:NilClass】
2023-12-19 03:52:34 提示：检测到 Dnsmasq 正常工作，还原防火墙 DNS 劫持规则...
2023-12-19 03:51:31 OpenClash 启动成功，请等待服务器上线！
2023-12-19 03:51:29 第九步: 添加计划任务,启动进程守护程序...
2023-12-19 03:51:21 第八步: 重启 Dnsmasq 程序...
2023-12-19 03:51:21 提示：开始添加自定义防火墙规则...
2023-12-19 03:51:19 提示：正在根据防火墙端口转发和防火墙通信规则添加端口绕过规则...
2023-12-19 03:51:21 第八步: 重启 Dnsmasq 程序...
2023-12-19 03:51:21 提示：开始添加自定义防火墙规则...
2023-12-19 03:51:19 提示：正在根据防火墙端口转发和防火墙通信规则添加端口绕过规则...
2023-12-19 03:51:13 提示：在 FAKE-IP 模式下绕过中国 IP 可能会导致 Dnsmasq 加载时间过长，暂时劫持 DNS 至内核直到 Dnsmasq 正常工作...
2023-12-19 03:51:13 提示：在 FAKE-IP 模式下绕过中国 IP 可能会导致 Dnsmasq 加载时间过长，暂时劫持 DNS 至内核直到 Dnsmasq 正常工作...
2023-12-19 03:50:34 提示：检测到 Firewall4，使用 NFTABLE 规则...
2023-12-19 03:50:34 提示：DNS 劫持模式为 Dnsmasq 转发...
2023-12-19 03:50:33 第七步: 设置防火墙规则...
2023-12-19 03:50:33 第六步: 等待主程序下载外部文件...
2023-12-19 03:50:30 第五步: 检查内核启动状态...
2023-12-19 03:50:28 配置文件【/etc/openclash/定阅转换.yaml】测试成功...
2023-12-19 03:50:28 配置文件【/etc/openclash/定阅转换.yaml】测试成功...
2023-12-19 03:49:59 启动前调用内核测试配置文件...
2023-12-19 03:49:59 提示：检测到配置了 Meta 内核专属功能，调用 Meta 内核启动...
2023-12-19 03:49:59 第四步: 启动主程序...
2023-12-19 03:49:59 提示：开始运行自定义覆写脚本...
2023-12-19 03:49:43 第三步: 修改配置文件...
2023-12-19 03:49:43 提示：由于文件【 /etc/config/openclash 】被修改，暂停快速启动...
2023-12-19 03:49:42 第二步: 组件运行前检查...
2023-12-19 03:49:40 第一步: 获取配置...
2023-12-19 03:49:40 OpenClash 开始启动...
2023-12-19 03:49:40 第六步：删除 OpenClash 残留文件...
2023-12-19 03:49:28 第五步: 重启 Dnsmasq 程序...
2023-12-19 03:49:28 第四步: 关闭 Clash 主程序...
2023-12-19 03:49:28 第三步: 关闭 OpenClash 守护程序...
2023-12-19 03:49:21 第二步: 删除 OpenClash 防火墙规则...
2023-12-19 03:49:21 第一步: 备份当前策略组状态...
2023-12-19 03:49:21 OpenClash 开始关闭...
2023-12-19 03:49:21 OpenClash 重新启动中...
Describe the Bug
使用0.45.152版本正常，更新最新版本0.45.161与meta内核后，总是提示这个错误，以为是DNSmasq的问题，尝试过改用防火墙转发问题依旧存在，在小内存机器上会导致节点测速异常，连接速度缓慢，高占用资源，时间一长直接卡死！查了半天不知道哪里有问题，特来求助。
OpenClash Log
log看着还行，但事实上整个路由快卡死了
OpenClash Config
主机型号: Xiaomi Mi Router 3G
固件版本: OpenWrt 23.05.0-rc4 r23482-7fe85ce1f2
LuCI版本: git-23.051.66410-a505bb1
内核版本: 5.15.132
处理器架构: mipsel_24kc
#此项有值时,如不使用IPv6,建议到网络-接口-lan的设置中禁用IPV6的DHCP
IPV6-DHCP:
DNS劫持: Dnsmasq 转发
#DNS劫持为Dnsmasq时，此项结果应仅有配置文件的DNS监听地址
Dnsmasq转发设置: 127.0.0.1#7874
#===================== 依赖检查 =====================#
dnsmasq-full: 已安装
coreutils: 已安装
coreutils-nohup: 已安装
bash: 已安装
curl: 已安装
ca-certificates: 已安装
ipset: 已安装
ip-full: 已安装
libcap: 已安装
libcap-bin: 已安装
ruby: 已安装
ruby-yaml: 已安装
ruby-psych: 已安装
ruby-pstore: 已安装
kmod-tun(TUN模式): 已安装
luci-compat(Luci >= 19.07): 已安装
kmod-inet-diag(PROCESS-NAME): 已安装
unzip: 已安装
kmod-nft-tproxy: 已安装
Expected Behavior
难道是内核问题？
Screenshots
No response
OpenClash 调试日志.log
试一下160吧
https://github.com/vernesong/OpenClash/blob/04d90c47306f2b52f6e25118eb09c7d0ac55239b/dev/luci-app-openclash_0.45.160-beta_all.ipk
我觉得是V大 https://github.com/vernesong/OpenClash/commit/cfd3c0055b7cfeaea9fbe03f3fc9b4ce4aa428c2 搞出来的问题
试一下160吧 https://github.com/vernesong/OpenClash/blob/04d90c47306f2b52f6e25118eb09c7d0ac55239b/dev/luci-app-openclash_0.45.160-beta_all.ipk
我觉得是V大 cfd3c00 搞出来的问题
有可能 5e3902f 修了，但v大还没发新版本，会编译可以试一下。
折腾一下午，直接卸载重装了160解决问题，161版本其实watchdog修改一下也无须编译！
顺便问一下，现在china_domains.list白名单哪家比较全？
其实m核官方编译的那个 geosite 就够了。少数网址搞个rule provider自己本地加，也不用重启内核
m核CN部分的数据是从这来的 https://github.com/blackmatrix7/ios_rule_script/blob/master/rule/Clash/ChinaMax/ChinaMax_Domain_For_Clash.txt
根据数据来源来看应该没有更全的了，分类也详细，你ip数据也可以用这位大佬的 https://github.com/blackmatrix7/ios_rule_script/tree/master/rule/Clash/ChinaMax#数据来源
目前就是在用他的规则集,但我其实想找的是插件里面的自定义大陆域名列表配置文件（Dnsmasq Conf）的域名更新来源URL，这样可以直接绕过CN,不过核心处理，节省小内存机器的资源利用，不然加载规则集后对于小内存路由来说cpu受不了。
再次谢谢。
额，你说china_domains.list，我以为是clash规则
其实现有的Dnsmasq规则这个其实已经够用了，再全可能会过度匹配
因为几乎所有基于dnsmasq的都用这一个源，所以现在是一个比较平衡的状态了
硬搞我倒是有个办法，因为dnsmasq这东西，其实几个月更新一次都没啥问题
先下载一个你满意的大陆域名
比如就上面那个 https://github.com/blackmatrix7/ios_rule_script/blob/master/rule/Clash/ChinaMax/ChinaMax_Domain_For_Clash.txt
删了前面的说明和所有+.
所有行首加server=/行尾加/114.114.114.114
上传替换/etc/openclash/accelerated-domains.china.conf
反正已经生成了，传上来看看
文本编辑部分不用正则的话用手机版excle都能搞，慢一点罢了
如果不满足，追求更新，写成脚本放Action上，私库都行，oc订阅自己生成的文件就好
因为几乎所有基于dnsmasq的都用这一个源，所以现在是一个比较平衡的状态了
多谢回复，我知道更新accelerated-domains.china.conf` 这种方法，旨在探讨，既然了解到都用这一个源，那我就不用去手动画蛇添足了。
嗯，刚才看了一下，使用160版本目前较稳定，但郁闷的是，定阅源使用proxy-providers提取代理，其它group引用use, 控制面板测延迟会很慢，甚至会出现timeout；直接切换回机场直接定阅的配置文件对比，又正常了。。。同一时间，网络环境都一样，不知道是不是也是因为版本问题？
meta这边测延迟是两套系统
proxy-provider 和 proxy-group 相互独立
这两者间是完全无法互通延迟数据的。
控制面板也只调用proxy-provider的
就算你没有proxy-provider，内核内置https://cp.cloudflare.com/generate_204作为默认(好像是这个)
所以你的use就是这种情况
之前用的人少没人修。现在好像断断续续的在搞
然后 proxy-group 内部又搞小独立
- {name: a, type: url-test, include-all-providers: true, lazy: true, interval: 300, tolerance: 50, url: https://a.com/generate_204}
- {name: b, type: url-test, include-all-providers: true, lazy: true, interval: 300, tolerance: 50, url: https://b.com/generate_204}
- {name: c, type: url-test, include-all-providers: true, lazy: true, interval: 300, tolerance: 50, url: https://c.com/generate_204}
根据情况，这三者可以选到完全不同的代理上，这个倒是属于特性了
我的接受还有点问题，具体你可以去内核那边搜一下，反正很绕。
大体能理解你的说法，也还是有疑惑：
1.“meta这边测延迟是两套系统”是指覆写里meta配置里面的 启用统一延迟 ?如果是的话那与这无关，因为我尝试过开启后数值是好看，但与实际使用体验不符，我一直没有启用。
2.“proxy-provider 和 proxy-group 相互独立，这两者间是完全无法互通延迟数据的。控制面板也只调用proxy-provider的”
我的两个配置文件（机场定阅、自定义proxy-provider）这两者里面都有单独指定相同测试地址http://www.gstatic.com/generate_204。所以控制面板应该是调用这个对proxy-group进行测速而不是调用内核默认啊？判定原因是我的网络对cloudflare极其不友好，经常机器人验证。所以才有相同条件下，两个配置的测速完全不同。甚至tw节点总是比us慢或者timeout，而实际使用tw节点甩us一条街了，郁闷就是这一点了，不能直观选择最佳节点。
如图，proxy-provider所有延迟都是2000-3000ms,如果用机场定阅配置就基本在5000-2000ms了,tw节点延迟在1000ms以内与事实相符，所以还是有区别的，搞不明白使用proxy-provider时的测速机制。后续再观察了。
至于‘ proxy-group 内部又搞小独立’，因为没有细致分流的需求，所以倒是没必要了。
再次谢谢帮助，交流愉快。
1、统一延迟与此问题无关，统一延迟是算法减少延迟的参数，这个是特性 bug
2、所以说现在很绕，之前用的人少，开发者没精力的同时也认为影响不算大，就没管。现在用的人多了，同时有新大佬加入，最近逐渐在完善
我也遇到此问题，希望能加个开关，想用的自己打开
2023-12-22 18:25:06 错误：绕过代理服务器地址设置失败，【no implicit conversion of nil into String】
我也遇到此问题，希望能加个开关，想用的自己打开
2023-12-22 18:25:06 错误：绕过代理服务器地址设置失败，【no implicit conversion of nil into String】
不是开关的问题，是V大代码的错误
你报错的版本是v大提供的最新的dev还是自己拉代码编译的
如果是前者，换回 160 https://github.com/vernesong/OpenClash/blob/04d90c47306f2b52f6e25118eb09c7d0ac55239b/dev/luci-app-openclash_0.45.160-beta_all.ipk
如果是后者，建议重新发个issue
我也遇到此问题，希望能加个开关，想用的自己打开
2023-12-22 18:25:06 错误：绕过代理服务器地址设置失败，【no implicit conversion of nil into String】
不是开关的问题，是V大代码的错误
你报错的版本是v大提供的最新的dev还是自己拉代码编译的
如果是前者，换回 160 https://github.com/vernesong/OpenClash/blob/04d90c47306f2b52f6e25118eb09c7d0ac55239b/dev/luci-app-openclash_0.45.160-beta_all.ipk
如果是后者，建议重新发个issue
已换回157
在最新的46.003和46.005版本中依然有这个问题
|
gharchive/issue
| 2023-12-18T20:23:50 |
2025-04-01T04:36:13.715719
|
{
"authors": [
"ayanami-desu",
"bxyun0",
"qqrate",
"sangyishuje1123"
],
"repo": "vernesong/OpenClash",
"url": "https://github.com/vernesong/OpenClash/issues/3688",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2599239876
|
fix number width
I think it would be more appropriate to use 36 instead of 32.
Thanks!
|
gharchive/pull-request
| 2024-10-19T14:30:26 |
2025-04-01T04:36:13.776090
|
{
"authors": [
"dalance",
"nananapo"
],
"repo": "veryl-lang/doc",
"url": "https://github.com/veryl-lang/doc/pull/7",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1161520631
|
Wire in the real clcok and use an explicit RequestContext instead of …
…the dummy FakeRequestContext intended only for tests.
@geirst PR
@vekterli @toregge FYI
|
gharchive/pull-request
| 2022-03-07T14:50:44 |
2025-04-01T04:36:13.777882
|
{
"authors": [
"baldersheim",
"geirst"
],
"repo": "vespa-engine/vespa",
"url": "https://github.com/vespa-engine/vespa/pull/21578",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1291226388
|
Dump threads when network fails to start in order to find the blockin…
…g thread.
@bratseth or @bjorncs or @jonmv PR
Nice. I wonder if this could help with some unit tests that also fail with this error occasionally, if those weren't already fixed.
|
gharchive/pull-request
| 2022-07-01T10:29:39 |
2025-04-01T04:36:13.778926
|
{
"authors": [
"baldersheim",
"jonmv"
],
"repo": "vespa-engine/vespa",
"url": "https://github.com/vespa-engine/vespa/pull/23308",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
375456634
|
Create issue_template.md
According to the @mpdehaan idea about github vs. talk.vespene.io purposes.
Feel free to modify it.
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.
Yeah I was intending to write one at some point :)
What you have is about all I think we need to say, though I may want to tweak this some and will get to this shortly.
Thanks for the reminder and good idea!
I've just copy-pasted that from README.md inspired by this comment.
merged it, slightly tweaked, thanks again!
|
gharchive/pull-request
| 2018-10-30T12:09:41 |
2025-04-01T04:36:13.783247
|
{
"authors": [
"CLAassistant",
"mpdehaan",
"sm4rk0"
],
"repo": "vespene-io/vespene",
"url": "https://github.com/vespene-io/vespene/pull/38",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
743078151
|
Forgotten licenses for llbuild and spm
TODO
Copy licensed during executing install action.
https://github.com/vgorloff/swift-everywhere-toolchain/releases/tag/1.0.57
${HOME}/dev_kit/sdk/swift_source/swift-android-toolchain/usr/bin/swift-build
dyld: Library not loaded: @rpath/libCommands.dylib
Referenced from: /Users/lihanguang/dev_kit/sdk/swift_source/swift-android-toolchain/usr/bin/swift-build
Reason: image not found
Maybe forgot to copy libCommands.dylib? thanks.
True. It is forgotten alongside with other libraries. The whole folder lib wasn't copied :0
find ./ToolChain/Build/ -iname libCommands.dylib
./ToolChain/Build//darwin-host/spm/lib/libCommands.dylib
Will release version 1.0.58 today later.
btw: How I can reproduce error on my side? What should I build to get that error?
Thank you in advance!
btw: How I can reproduce error on my side? What should I build to get that error?
Download the toolchain_1.0.57
then type
${HOME}/dev_kit/sdk/swift_source/swift-android-toolchain/usr/bin/swift-build
Error will be reproduce, that is all.
Thanks.
The other item (maybe 😂 ):
Could you replace the LICENSE.TXT of LLVM to LICENSE.txt? Because my macOS case sensitive 😂 .
# installer.js
files.push(`${Paths.sourcesDirPath(Components.llvm)}/LICENSE.txt`);
Fixed in https://github.com/vgorloff/swift-everywhere-toolchain/releases/tag/1.0.58
|
gharchive/issue
| 2020-11-14T20:56:45 |
2025-04-01T04:36:13.803075
|
{
"authors": [
"Guang1234567",
"vgorloff"
],
"repo": "vgorloff/swift-everywhere-toolchain",
"url": "https://github.com/vgorloff/swift-everywhere-toolchain/issues/84",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1365901392
|
🛑 Sentry is down
In c5d5b30, Sentry (https://sentry9-th.line-apps.com/_health/) was down:
HTTP code: 503
Response time: 1528 ms
Resolved: Sentry is back up in a1a249a.
|
gharchive/issue
| 2022-09-08T09:35:14 |
2025-04-01T04:36:14.240281
|
{
"authors": [
"vichaos"
],
"repo": "vichaos/upptime",
"url": "https://github.com/vichaos/upptime/issues/227",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2066608448
|
🛑 Melody is down
In f5bb1b5, Melody (https://melody.line.me) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Melody is back up in c3885eb after .
|
gharchive/issue
| 2024-01-05T02:00:39 |
2025-04-01T04:36:14.242679
|
{
"authors": [
"vichaos"
],
"repo": "vichaos/upptime",
"url": "https://github.com/vichaos/upptime/issues/494",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
392842700
|
New suggestion for predictor
The epl predictor is a terrific project but humans are still unpredictable mostly even with data. Virtual football on the other hand is a case of pseudo-randomness which i believe a network with training can achieve high accuracy
@deven96 Yes, this is true. If I have the time, I'd have built a Reinforcement Learning agent that learns from real life past soccer matches & learns the strength and weaknesses of every team & players. This would be a more accurate system in predicting future matches.
|
gharchive/issue
| 2018-12-20T01:02:51 |
2025-04-01T04:36:14.284442
|
{
"authors": [
"deven96",
"victor-iyiola"
],
"repo": "victor-iyiola/epl-prediction",
"url": "https://github.com/victor-iyiola/epl-prediction/issues/1",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1992689617
|
🛑 Twitter is down
In de40b91, Twitter (https://twitter.com) was down:
HTTP code: 503
Response time: 9135 ms
Resolved: Twitter is back up in 97cb100 after 24 minutes.
|
gharchive/issue
| 2023-11-14T12:54:16 |
2025-04-01T04:36:14.290201
|
{
"authors": [
"victorbungey"
],
"repo": "victorbungey/status_page",
"url": "https://github.com/victorbungey/status_page/issues/14",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
990205933
|
data undefined
I’m getting the data back from graphql and it’s rendering to the template no problem, but when trying to pass the data to the chart (PolarChart) I get undefined. I don't believe this is a bug -- i'm sure I'm just overlooking something -- but I also thought it could be useful to post here incase someone in the future runs into a similar issue.
Even though i'm using Vue3 are registerables and ChartData still required like in the demo: https://codesandbox.io/s/demo-vue-chart-3-forked-e3yz2?file=/src/App.vuehttps://codesandbox.io/s/demo-vue-chart-3-forked-e3yz2?file=/src/App.vue -- i'm wondering, because in the documentation it says nothing like that is required for Vue 3.
You should be able to run the repo: https://github.com/edwardz8/vue3-hockey-graphql to see how the data is being logged in the console.
@edwardz8 Sorry for delay I was in vacations!
Do you still have the problem?
@victorgarciaesgi no worries! but last time i checked i was still getting the same error of data undefined
resolved. closing.
|
gharchive/issue
| 2021-09-07T17:38:00 |
2025-04-01T04:36:14.293574
|
{
"authors": [
"edwardz8",
"victorgarciaesgi"
],
"repo": "victorgarciaesgi/vue-chart-3",
"url": "https://github.com/victorgarciaesgi/vue-chart-3/issues/28",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2603990767
|
Use hugo.IsServer instead of .Site.IsServer
Fix the following error:
ERROR deprecated: .Site.IsServer was deprecated in Hugo v0.120.0 and will be removed in Hugo 0.136.0. Use hugo.IsServer instead.
Thanks!
|
gharchive/pull-request
| 2024-10-22T01:20:30 |
2025-04-01T04:36:14.294565
|
{
"authors": [
"g0rbe",
"victoriadrake"
],
"repo": "victoriadrake/hugo-theme-introduction",
"url": "https://github.com/victoriadrake/hugo-theme-introduction/pull/371",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
807781216
|
Implementation of automatic delay adjustment
With the new features the search and delete delays are automatically adjusted to minize the occurrence of rate limitations and maximize speed.
This change is
Sorry for taking so long to review pull requests, I've been very busy.
Have you tested this with how many messages? The original algorithm used to work well before discord made some changes, but since then people started to report being throttled more aggressively and some PRs have increased the default delays.
Hi victornpb, no worries.
I have tested it by deleting up to few thousands messages in various channels, had no problem.
The retry after value is usually way too high than the one that is reallyneeded, this algorithm adjusts the delay value towards a value that minimize the chances of being rate limited and maximizes the deletion speed.
The algorithm is not perfect but it makes deletion much faster as long as you have enough messages to delete because it takes a while to iterate and find a good value, usually few dozens messages.
Yes, when I originally implemented the logic it started with like 50ms delay and slowly increased until the API was happy.
But that only worked because the retry_after was usually around 500ms, the algorithm never tries to decrease the delay, it only increases, so it becomes extremely slow after getting throttled by like 30s. They are now trolling way sooner and much more aggressively.
|
gharchive/pull-request
| 2021-02-13T16:35:59 |
2025-04-01T04:36:14.298697
|
{
"authors": [
"giuliom",
"victornpb"
],
"repo": "victornpb/deleteDiscordMessages",
"url": "https://github.com/victornpb/deleteDiscordMessages/pull/179",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1798412035
|
Update scalafmt-core, scalafmt-dynamic to 3.7.8
About this PR
📦 Updates
org.scalameta:scalafmt-core
org.scalameta:scalafmt-dynamic
from 3.7.2 to 3.7.8
📜 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" } ]
Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
pullRequests = { frequency = "30 days" },
dependency = { groupId = "org.scalameta" }
}]
labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1
Superseded by #102.
|
gharchive/pull-request
| 2023-07-11T08:33:13 |
2025-04-01T04:36:14.369417
|
{
"authors": [
"scala-steward"
],
"repo": "vigoo/metagen",
"url": "https://github.com/vigoo/metagen/pull/101",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1210850056
|
在公式中怎么过滤某个字段值不为空？
如题：在query的withFilter("{fieldName}!=null")
怎么在过滤条件中 指定某个字段的值不为空，即只查询有字段有值的记录行
公式使用判断不为空可以使用 {fieldName} != BLANK()作为参数
解决了吗？如果没问题的话，24小时后我将关闭问题咯
resovle
|
gharchive/issue
| 2022-04-21T10:43:35 |
2025-04-01T04:36:14.374383
|
{
"authors": [
"shawndenggh",
"wangjiecpp"
],
"repo": "vikadata/vika.java",
"url": "https://github.com/vikadata/vika.java/issues/21",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
225335238
|
failed to find Build Tools revision 25.0.0
why i must be update my build too revision ?
my project already use with build tools revision 23
i get error like this
Building and installing the app on the device (cd android && ./gradlew installDebug)...
Failed to notify ProjectEvaluationListener.afterEvaluate(), but primary configuration failure takes precedence.
java.lang.IllegalStateException: failed to find Build Tools revision 25.0.0
at com.android.builder.sdk.DefaultSdkLoader.getTargetInfo(DefaultSdkLoader.java:93)
at com.android.build.gradle.internal.SdkHandler.initTarget(SdkHandler.java:89)
at com.android.build.gradle.BasePlugin.ensureTargetSetup(BasePlugin.groovy:507)
at com.android.build.gradle.BasePlugin.createAndroidTasks(BasePlugin.groovy:455)
at com.android.build.gradle.BasePlugin$_createTasks_closure13_closure17.doCall(BasePlugin.groovy:415)
at com.android.build.gradle.BasePlugin$_createTasks_closure13_closure17.doCall(BasePlugin.groovy)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:324)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:292)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1015)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:39)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112)
at com.android.build.gradle.internal.profile.SpanRecorders$2.call(SpanRecorders.groovy:52)
at com.android.builder.profile.ThreadRecorder$1.record(ThreadRecorder.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMet
thanks :)
You don't have to upgrade your build tools in your project, but you have to download 25.0.0 in Android SDK manager: https://developer.android.com/studio/intro/update.html#sdk-manager
already fix upgrade build tool in my project, but not run in android < 5
No activity for a long time. Closing. Please create new issue if re-encountered.
|
gharchive/issue
| 2017-04-30T15:49:34 |
2025-04-01T04:36:14.377336
|
{
"authors": [
"creativefull",
"vikeri"
],
"repo": "vikeri/react-native-background-job",
"url": "https://github.com/vikeri/react-native-background-job/issues/22",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
331131630
|
Missing from documentation: start vi from directory, where your script resides
I followed the documentation from
vdebug/doc/Vdebug.txt
I came to the point, that my php command line script stopped after start, but vi did not display the source code.
After I found out, that I have to start vi from the directory, where the script resides, it works.
This essential information is missing from vdebug/doc/Vdebug.txt.
@jm009 could you specify where you should add it in the documentation? I'm going to assume you are doing local debugging.
Chapter 4.1 Starting the debugger would be fine.
Feel free to open a PR @jm009
https://github.com/vim-vdebug/vdebug/pull/364
:-)
@jm009 great, really appreciate you took the time :+1:
|
gharchive/issue
| 2018-06-11T10:28:18 |
2025-04-01T04:36:14.415978
|
{
"authors": [
"BlackIkeEagle",
"jm009"
],
"repo": "vim-vdebug/vdebug",
"url": "https://github.com/vim-vdebug/vdebug/issues/363",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1614247084
|
doesn't work when pmenu open in command-line window
Steps to reproduce
vim --clean
q:
h <Tab>
<S-Tab>
Expected behaviour
The first selected pmenu entry should be un-selected and nothing inserted into the command-line window, this is how it works in the command-line (:h c_<S-Tab>) and that works fine for me, so it's not terminal emulator keybinding issue (tried several to rule that out).
Version of Vim
9.0.1341
Environment
OS: macOS 12.6.3
Terminal: WezTerm 20230212 $TERM: wezterm(tried on others as well, same issue) Shell:zsh`
Logs and stack traces
No response
If I try this literally then the "h" in the third step beeps. Did you mean ":h" instead?
When I use ":h " and then "" nothing strange happens.
What other terminals did you try?
With vim -Nu NONE you have to get into insert mode first, before start typing. Or just press <tab><s-tab>.
https://asciinema.org/a/3Fk1sp3KvgGTPvHaX4QbRbVG8
So the minimal steps to repro:
vim -Nu NONE
q:
<tab>
<s-tab>
https://asciinema.org/a/cI9e3zeyMWlTWbeXDfJKa2vTX
|
gharchive/issue
| 2023-03-07T21:38:40 |
2025-04-01T04:36:14.422279
|
{
"authors": [
"brammool",
"craigmac",
"habamax"
],
"repo": "vim/vim",
"url": "https://github.com/vim/vim/issues/12116",
"license": "Vim",
"license_type": "permissive",
"license_source": "github-api"
}
|
101749553
|
Ruby syntax highlighting w/ either cursorline or relativenumber causes lag from high CPU usage
With ruby syntax highlighting on, turning on cursorline or relativenumber
settings causes lag due to high CPU usage when moving the cursor up and down.
The conditions below exaggerbate the problem to help make it obvious and
reproducible, but the same problem exists at lesser scale with smaller terminal
sizes. This is a significant problem though, because when CPUs are otherwise
bogged down (eg. when pair programming with someone via screen share on Google
Hangouts), moving the cursor in a ruby file can be ridiculously slow.
What steps will reproduce the problem?
1. Temporarily rename ~/.vim/ and ~/.vimrc to ensure nothing but vanilla vim
2. Resize the terminal window so that ~100 lines are visible (normal for large
monitors)
3. Open a ruby file with non-trivial syntax:
https://raw.githubusercontent.com/rails/rails/f43f56e/activerecord/lib/active_re
cord/associations.rb
4. :syntax on
5. :set relativenumber
6. Hold down j or <down> for 1-2 seconds. (Ensure the system's keyboard repeat
rate is not slow, ideally maxed)
7. Notice that CPU usage for the vim process is at 100%, accompanied by choppy
redrawing and lag. Upon releasing the j/<down> key, buffered keypresses
continue to move the cursor down.
What is the expected behavior?
1. With the same file open and under the same conditions, :set syntax=java
2. Notice there is no longer excessive CPU usage or any lag when moving the
cursor up and down. The cursor stops moving immediately when the key is
released.
---
I understand that ruby's syntax is complex and nontrivial to parse. If there's
no clear way to reduce CPU usage for parsing ruby syntax for syntax
highlighting, are there other ways you can think of to prevent the syntax
highlighting from having to be recalculated when the screen is redrawn for
relativenumber and cursorline? Can we profile and find where the problem lies?
---
I can reproduce this in Vim 7.4 on both Ubuntu and OSX:
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Nov 12 2014 20:26:50)
MacOS X (unix) version
Included patches: 1-488
Compiled by Homebrew
Huge version without GUI. Features included (+) or not (-):
+acl +farsi +mouse_netterm +syntax
+arabic +file_in_path +mouse_sgr +tag_binary
+autocmd +find_in_path -mouse_sysmouse +tag_old_static
-balloon_eval +float +mouse_urxvt -tag_any_white
-browse +folding +mouse_xterm -tcl
++builtin_terms -footer +multi_byte +terminfo
+byte_offset +fork() +multi_lang +termresponse
+cindent -gettext -mzscheme +textobjects
-clientserver -hangul_input +netbeans_intg +title
+clipboard +iconv +path_extra -toolbar
+cmdline_compl +insert_expand +perl +user_commands
+cmdline_hist +jumplist +persistent_undo +vertsplit
+cmdline_info +keymap +postscript +virtualedit
+comments +langmap +printer +visual
+conceal +libcall +profile +visualextra
+cryptv +linebreak +python +viminfo
+cscope +lispindent -python3 +vreplace
+cursorbind +listcmds +quickfix +wildignore
+cursorshape +localmap +reltime +wildmenu
+dialog_con -lua +rightleft +windows
+diff +menu +ruby +writebackup
+digraphs +mksession +scrollbind -X11
-dnd +modify_fname +signs -xfontset
-ebcdic +mouse +smartindent -xim
+emacs_tags -mouseshape -sniff -xsmp
+eval +mouse_dec +startuptime -xterm_clipboard
+ex_extra -mouse_gpm +statusline -xterm_save
+extra_search -mouse_jsbterm -sun_workshop -xpm
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/local/share/vim"
Compilation: /usr/bin/clang -c -I. -Iproto -DHAVE_CONFIG_H
-F/usr/local/Frameworks -DMACOS_X_UNIX -Os -w -pipe -march=native
-mmacosx-version-min=10.10 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: /usr/bin/clang -L. -L/usr/local/lib -L/usr/local/lib
-F/usr/local/Frameworks -Wl,-headerpad_max_install_names -o vim -lm
-lncurses -liconv -framework Cocoa -fstack-protector
-L/System/Library/Perl/5.18/darwin-thread-multi-2level/CORE -lperl -framework
Python -lruby.2.0.0 -lobjc
AND
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug 15 2013 11:04:13)
Included patches: 1-5
Modified by pkg-vim-maintainers@lists.alioth.debian.org
Compiled by buildd@
Huge version without GUI. Features included (+) or not (-):
+arabic +file_in_path +mouse_sgr +tag_binary
+autocmd +find_in_path -mouse_sysmouse +tag_old_static
-balloon_eval +float +mouse_urxvt -tag_any_white
-browse +folding +mouse_xterm +tcl
++builtin_terms -footer +multi_byte +terminfo
+byte_offset +fork() +multi_lang +termresponse
+cindent +gettext -mzscheme +textobjects
-clientserver -hangul_input +netbeans_intg +title
-clipboard +iconv +path_extra -toolbar
+cmdline_compl +insert_expand +perl +user_commands
+cmdline_hist +jumplist +persistent_undo +vertsplit
+cmdline_info +keymap +postscript +virtualedit
+comments +langmap +printer +visual
+conceal +libcall +profile +visualextra
+cryptv +linebreak +python +viminfo
+cscope +lispindent -python3 +vreplace
+cursorbind +listcmds +quickfix +wildignore
+cursorshape +localmap +reltime +wildmenu
+dialog_con +lua +rightleft +windows
+diff +menu +ruby +writebackup
+digraphs +mksession +scrollbind -X11
-dnd +modify_fname +signs -xfontset
-ebcdic +mouse +smartindent -xim
+emacs_tags -mouseshape -sniff -xsmp
+eval +mouse_dec +startuptime -xterm_clipboard
+ex_extra +mouse_gpm +statusline -xterm_save
+extra_search -mouse_jsbterm -sun_workshop
+farsi +mouse_netterm +syntax
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -I/usr/include/tcl8.5 -D_REENTRANT=1
-D_THREAD_SAFE=1 -D_LARGEFILE64_SOURCE=1
Linking: gcc -L. -Wl,-Bsymbolic-functions -Wl,-z,relro -rdynamic
-Wl,-export-dynamic -Wl,-E -Wl,-Bsymbolic-functions -Wl,-z,relro
-Wl,--as-needed -o vim -lm -ltinfo -lnsl -lselinux -lacl -lattr -lgpm
-ldl -L/usr/lib -llua5.1 -Wl,-E -fstack-protector -L/usr/local/lib
-L/usr/lib/perl/5.14/CORE -lperl -ldl -lm -lpthread -lcrypt
-L/usr/lib/python2.7/config-x86_64-linux-gnu
Original issue reported on code.google.com by nil...@gmail.com on 13 Nov 2014 at 4:26
Thank you for this! set re=1 made set cursorline usable for me as well (VIM 7.4 on OSX).
Issue is in the runtime files: So please report there: vim-ruby/vim-ruby#243
Same happens with PHP syntax highlighting, as well as others.
Improving regex strings will help alleviate the lag, but the core problem still exists where the relativenumber option causes the regex to execute too often while holding down a cursor movement key.
Use the syntime command to find specific syntax patterns that are slow. We can then hopefully improve that performance.
Christian Brabandt wrote:
Use the syntime command to find specific syntax patterns that are
slow. We can then hopefully improve that performance.
When moving the cursor around, with 'relativenumber' or 'cursorcolumn'
set, cause a full redraw, because every line changes. I'm wondering if
it is possible to cache the result of syntax highlighting. It would
require storing the "attr" value, before it's mixed with other
attributes, such as from 'cursorcolumn'. So long as we don't scroll the
screen update would be much faster. These days memory is plenty, thus
that isn't a problem.
As soon as you page forward it's just as slow, of course, thus making
the syntax highlighting faster is still desired.
--
Google is kind of like Dr. Who's Tardis; it's weirder on the
inside than on the outside...
/// 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 ///
I have lazyredraw enabled and regexpengine set to 0.
In my case, it's foldmethod=syntax being responsible for the lag
TOTAL COUNT MATCH SLOWEST AVERAGE NAME PATTERN
4.496335 17040 104 0.021650 0.000264 rubyConditionalExpression \%(\%(^\|\.\.\.\=\|[{:,;([<>~\*%&^|+=-]\|\%(\<[_[:lower:]][_[:alnum:]]*\)\@<![?!]\)\s*\)\@<=\%(\\\n\s*\)\@<!
Forcing set regexpengine=1 doesn't improve the situation.
2016-01-08 2:12 GMT+03:00 Gregory Pakosz vim-dev-github@256bit.org:
I have lazyredraw enabled and regexpengine set to 0.
In my case, it's foldmethod=syntax being responsible for the lag
TOTAL COUNT MATCH SLOWEST AVERAGE NAME PATTERN
4.496335 17040 104 0.021650 0.000264 rubyConditionalExpression %(%(^|...=|[{:,;([<>~*%&^|+=-]|%(<[[:lower:]][[:alnum:]])@<![?!])\s)@<=%(\\n\s*)@<!
Forcing set regexpengine=1 doesn't improve the situation.
I see this pattern having quite a large number of look-behinds. Forcing
maximum amount of bytes here may help (search for \@123<= in :h /\@<=,
for some reason this does not have its own tag). Contacting syntax file
maintainer is needed to perform this change, I am not sure what numbers you
should exactly place there.
Most likely using @100<! in place of @<! (two occurences) and @100<=
(one I see so far) should work fine.
—
Reply to this email directly or view it on GitHub
https://github.com/vim/vim/issues/282#issuecomment-169837021.
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to vim_dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You should mentioned this here: vim-ruby/vim-ruby#243
Hey there,
I'm having the same issue using php files (even with small ones, ~120 lines, 4kB). I don't know about ruby files since I don't work with those but everything else I use (html, css, javascript) is ok. Problem didn't exist in 7.3.
Removing either syntax highlighting or cursorline (and relativenumber, but I don't use it) solves the issue, but I can't live without any of those ^^
I noticed after a few checks that removing HereDoc/NowDoc regex makes everything smooth again.
I just don't know how to do it properly so I edited the original php.vim file.
In case you wanted some informations:
TOTAL COUNT MATCH SLOWEST AVERAGE NAME PATTERN
0.225932 8239 0 0.000081 0.000027 phpHereDoc \(<<<\)\@<=\(\"\=\)\z(\(\I\i*\
0.223937 8239 0 0.000079 0.000027 phpHereDoc \(<<<\)\@<=\(\"\=\)\z(\(\I\i*\
0.220748 8239 0 0.000102 0.000027 phpHereDoc \(<<<\)\@<=\(\"\=\)\z(\(\I\i*\
0.200274 8239 0 0.000076 0.000024 phpHereDoc \(<<<\)\@<=\(\"\=\)\z(\I\i*\)\
0.093085 8239 0 0.000036 0.000011 phpFloat \(-\=\<\d+\|-\=\)\.\d\+\>
0.088690 40927 35269 0.000012 0.000002 phpParent [({[\]})]
0.063615 17808 10185 0.000024 0.000004 phpOperator [-=+%^&|*!.~?:]
0.052475 8485 246 0.000025 0.000006 phpOperator [-+*/%^&|.]=
0.047634 16258 8266 0.000014 0.000003 phpNumber -\=\<\d\+\>
0.045641 9500 1262 0.000014 0.000005 phpComparison \v[=<>-]@<![<>]\=?[<>]@!
0.040510 8239 0 0.000031 0.000005 phpNowDoc \(<<<\)\@<='\z(\(\I\i*\)\=\(ja
0.039808 8977 738 0.000016 0.000004 phpOperator ||\|\<x\=or\>
0.038677 8239 0 0.000030 0.000005 phpNowDoc \(<<<\)\@<='\z(\(\I\i*\)\=\(sq
0.037592 8239 0 0.000029 0.000005 phpNowDoc \(<<<\)\@<='\z(\(\I\i*\)\=\(ht
0.035145 8239 0 0.000018 0.000004 phpOperator &&\|\<and\>
0.032899 8239 0 0.000019 0.000004 phpNowDoc \(<<<\)\@<='\z(\I\i*\)'$
0.030615 8368 129 0.000013 0.000004 phpRelation [!=<>]=
0.025588 8755 516 0.000011 0.000003 phpComparison \v[=!]\=\=?
0.024676 8365 127 0.000011 0.000003 phpRelation [<>]
0.022235 23519 15896 0.000007 0.000001 phpIdentifier $\h\w*
0.020534 8239 615 0.000046 0.000002 phpComment //.\{-}\(?>\|$\)\@=
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Mar 31 2015 23:36:03)
Included patches: 1-488, 576
Modified by pkg-vim-maintainers@lists.alioth.debian.org
Compiled by jamessan@debian.org
Huge version without GUI. Features included (+) or not (-):
+acl -ebcdic +localmap +printer +title
+arabic +emacs_tags -lua +profile -toolbar
+autocmd +eval +menu -python +user_commands
-balloon_eval +ex_extra +mksession -python3 +vertsplit
-browse +extra_search +modify_fname +quickfix +virtualedit
++builtin_terms +farsi +mouse +reltime +visual
+byte_offset +file_in_path -mouseshape +rightleft +visualextra
+cindent +find_in_path +mouse_dec -ruby +viminfo
-clientserver +float +mouse_gpm +scrollbind +vreplace
-clipboard +folding -mouse_jsbterm +signs +wildignore
+cmdline_compl -footer +mouse_netterm +smartindent +wildmenu
+cmdline_hist +fork() +mouse_sgr -sniff +windows
+cmdline_info +gettext -mouse_sysmouse +startuptime +writebackup
+comments -hangul_input +mouse_urxvt +statusline -X11
+conceal +iconv +mouse_xterm -sun_workshop -xfontset
+cryptv +insert_expand +multi_byte +syntax -xim
+cscope +jumplist +multi_lang +tag_binary -xsmp
+cursorbind +keymap -mzscheme +tag_old_static -xterm_clipboard
+cursorshape +langmap +netbeans_intg -tag_any_white -xterm_save
+dialog_con +libcall +path_extra -tcl -xpm
+diff +linebreak -perl +terminfo
+digraphs +lispindent +persistent_undo +termresponse
-dnd +listcmds +postscript +textobjects
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -fPIE -fstack-protector-strong -Wformat -
Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim -lm -ltinfo -lnsl -
lselinux -lacl -lattr -lgpm -ldl
I didn't know if I had to start an new issue for that, sorry if it was the case.
Kind regards,
Lyn.
@Lynesth try to contact the php syntax file maintainer. perhaps he can come up with a better syntax RE for the phpHereDoc item.
@brammool
When moving the cursor around, with 'relativenumber' or 'cursorcolumn'
set, cause a full redraw, because every line changes. I'm wondering if
it is possible to cache the result of syntax highlighting. It would
require storing the "attr" value, before it's mixed with other
attributes, such as from 'cursorcolumn'. So long as we don't scroll the
screen update would be much faster. These days memory is plenty, thus
that isn't a problem.
Yes please to the power of 1 million. I would be willing to trade memory for superior scroll performance any day, every day.
Ruby files with relativenumber set along with regexpengine=0 or 2 results in terrible performance. PHP may have the same issue.
Caching syntax highlighting would be extremely beneficial especially since many Vim users enable relativenumber these days.
Known, see these issues:
Feature Request: cache syntax highlighting to improve 'relativenumber' scroll performance
api/ui: externalize 'relativenumber'
Please thumb-up those issues, with luck one day this issue will be corrected.
cursorline and relativenumber options have been greatly improved with patch 8.1.0372-8.1.0374. So closing.
Actually, I have a similar problem in ViM 8.2.532: when editing .tex files (with no additional plugins, checked with :scriptnames), if I have the option relativenumber set, then in insert mode ViM has a high CPU usage (~50/60% according to htop).
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Apr 8 2020 22:50:14)
Included patches: 1-532
Compiled by luxgiammi@ganimede
Huge version without GUI. Features included (+) or not (-):
+acl +cursorshape +jumplist +mouse_xterm +smartindent +vertsplit
+arabic +dialog_con +keymap +multi_byte +sound +virtualedit
+autocmd +diff +lambda +multi_lang +spell +visual
+autochdir +digraphs +langmap -mzscheme +startuptime +visualextra
-autoservername -dnd +libcall +netbeans_intg +statusline +viminfo
-balloon_eval -ebcdic +linebreak +num64 -sun_workshop +vreplace
+balloon_eval_term +emacs_tags +lispindent +packages +syntax +wildignore
-browse +eval +listcmds +path_extra +tag_binary +wildmenu
++builtin_terms +ex_extra +localmap -perl -tag_old_static +windows
+byte_offset +extra_search -lua +persistent_undo -tag_any_white +writebackup
+channel -farsi +menu +popupwin -tcl +X11
+cindent +file_in_path +mksession +postscript +termguicolors +xfontset
+clientserver +find_in_path +modify_fname +printer +terminal -xim
+clipboard +float +mouse +profile +terminfo -xpm
+cmdline_compl +folding -mouseshape -python +termresponse +xsmp_interact
+cmdline_hist -footer +mouse_dec +python3 +textobjects +xterm_clipboard
+cmdline_info +fork() -mouse_gpm +quickfix +textprop -xterm_save
+comments +gettext -mouse_jsbterm +reltime +timers
+conceal -hangul_input +mouse_netterm +rightleft +title
+cryptv +iconv +mouse_sgr -ruby -toolbar
+cscope +insert_expand -mouse_sysmouse +scrollbind +user_commands
+cursorbind +job +mouse_urxvt +signs +vartabs
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
defaults file: "$VIMRUNTIME/defaults.vim"
fall-back for $VIM: "/usr/local/share/vim"
Compilation:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc -L/usr/local/lib -Wl,--as-needed -o vim -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -ltinf
o -lnsl -lselinux -lcanberra -ldl -L/usr/lib/python3.7/config-3.7m-x86_64-linux-gnu -lpython3.7m -lcrypt -lpth
read -ldl -lutil -lm
|
gharchive/issue
| 2015-08-18T21:08:33 |
2025-04-01T04:36:14.448620
|
{
"authors": [
"GoogleCodeExporter",
"LuxGiammi",
"Lynesth",
"bluz71",
"brammool",
"chrisbra",
"gpakosz",
"joepestro",
"nicklozon",
"vim-ml"
],
"repo": "vim/vim",
"url": "https://github.com/vim/vim/issues/282",
"license": "Vim",
"license_type": "permissive",
"license_source": "github-api"
}
|
747628197
|
Vim9: misleading error when executing string where colon not written before "*" range
Describe the bug
In Vim9 script, a misleading error is raised when executing a string containing the * range, if the latter is not prefixed by a colon.
To Reproduce
Run this shell command:
vim -Nu NONE -i NONE -S <(cat <<'EOF'
vim9script
@s = 'blah'
def Func()
exe ':keepp *s/pat/rep/'
enddef
Func()
EOF
)
E492 is raised at runtime:
E492: Not an editor command: blah
Expected behavior
E1050 is raised at compile time:
E1050: Colon required before a range
Environment
Vim version: 8.2 Included patches: 1-2018
OS: Ubuntu 16.04.7 LTS
Terminal: xterm(362)
Additional context
Without :exe, E1050 is correctly raised at compile time:
vim9script
@s = 'blah'
def Func()
:keepp *s/pat/rep/
enddef
defcompile
E1050: Colon required before a range
Same thing if the * range is replaced with another range:
vim9script
@s = 'blah'
def Func()
exe ':keepp 123s/pat/rep/'
enddef
Func()
E1050: Colon required before a range
The original example can be simplified into this:
vim9script
@s = 'blah'
exe '*s/pat/rep/'
Not sure why the :substitute command is parsed as the "s register.
It's working as intended. I didn't know that * could be used as a replacement for @ to execute the contents of a register. Sorry for the noise.
Although, it's a bit weird that * is parsed as an Ex command:
vim9script
@s = 'string'
exe '*s'
E492: Not an editor command: string
Because according to :h :*, that should only be the case when the * flag is in 'cpo':
Note that the ":*" command is only recognized when the
'*' flag is present in 'cpoptions'. This is NOT the
default when 'nocompatible' is used.
Which is not the case in a Vim9 script, according to :h :vim9:
A side effect of `:vim9script` is that the 'cpoptions' option is set to the
Vim default value, like with: >
:set cpo&vim
I guess that :exe supersedes some logic here, and forces Vim to parse * as an Ex command...
See ":help :*", it's an old Vi command to execute the contents of a register. Has nothing to do with :substitute
Oh, about using ":" as the star command, even though '' is not in 'cpoptions': Well, the colon before a range is missing, thus it could not have the meaning of the Visual area. Should this be an error?
|
gharchive/issue
| 2020-11-20T16:36:33 |
2025-04-01T04:36:14.459307
|
{
"authors": [
"brammool",
"lacygoill"
],
"repo": "vim/vim",
"url": "https://github.com/vim/vim/issues/7335",
"license": "Vim",
"license_type": "permissive",
"license_source": "github-api"
}
|
964647609
|
make test failed in vim@8.2.3322 on centos8_aarch64 and not root
Hello,I meet a problem :make test failed in vim@8.2.3322 on centos8_aarch64 and not root
[distcc@centos8 vim]$ ls
CONTRIBUTING.md Filelist LICENSE Makefile README.md README.txt README_VIM9.md READMEdir ci configure nsis pixmaps removed_la_files.txt runtime src tools uninstall.txt vimtutor.bat vimtutor.com
[distcc@centos8 vim]$ make test\
……
Test_ex_shift_rightleft(): rightleft feature missing
Test_global_set_clipboard(): clipboard_working feature missing
Test_version_redirect(): cannot start the GUI
-------------------------------
Executed: 4200 Tests
Skipped: 384 Tests
FAILED: 12 Tests
Failures:
From test_digraph.vim:
Found errors in Test_digraph_get_function_encode():
Caught exception in Test_digraph_get_function_encode(): Vim(call):E1215: Digraph must be one character: あ @ command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraph_get_function_encode, line 7
Found errors in Test_digraph_getlist_function():
Caught exception in Test_digraph_getlist_function(): Vim(call):E1215: Digraph must be one character: き @ command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraph_getlist_function, line 2
Found errors in Test_digraph_set_function():
Caught exception in Test_digraph_set_function(): Vim(call):E1215: Digraph must be one character: あ @ command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraph_set_function, line 2
Found errors in Test_digraph_setlist_function():
Caught exception in Test_digraph_setlist_function(): Vim(call):E1215: Digraph must be one character: き @ command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraph_setlist_function, line 1
Found errors in Test_digraphs():
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 3: Expected '∞' but got '0'
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 8: Expected 'þ' but got '▒'
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 12: Expected ['ば', 'ば'] but got ['b', 'a']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 18: Expected ['е', '€', '€', '€'] but got ['=', 'e', 'u', 'E']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 24: Expected ['Р', '₽', '₽', 'П'] but got ['=', 'R', 'P', '=']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 33: Expected ['à', 'è', '!'] but got ['▒', '▒', '!']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 38: Expected ['á', 'é', ''''] but got ['▒', '▒', '''']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 43: Expected ['â', 'ê', '>'] but got ['▒', '▒', '>']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 48: Expected ['õ', 'u', '~'] but got ['▒', 'u', '~']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 53: Expected ['õ', 'ũ', '?'] but got ['▒', 'u', '?']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 58: Expected ['ō', 'ū', '-'] but got ['▒', 'u', '-']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 63: Expected ['ŏ', 'ŭ', '('] but got ['(', 'u', '(']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 68: Expected ['ḃ', 'ė', '.'] but got ['.', 'e', '.']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 73: Expected ['ä', 'ü', ':'] but got ['▒', '▒', ':']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 78: Expected ['¸', 'Ç', ','] but got ['▒', '▒', ',']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 83: Expected ['Ḇ', 'ṯ', '_'] but got ['_', 't', '_']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 88: Expected ['/', 'ł', '/'] but got ['/', 'l', '/']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 93: Expected ['Ő', 'ÿ', '"'] but got ['"', '▒', '"']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 98: Expected ['ų', 'Ę', ';'] but got [';', 'E', ';']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 103: Expected ['ǔ', 'Ě', '<'] but got ['<', 'E', '<']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 108: Expected ['ů', 'E', '0'] but got ['0', 'E', '0']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 113: Expected ['ủ', 'Ẻ', '2'] but got ['2', 'E', '2']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 118: Expected ['ư', 'E', '9'] but got ['9', 'E', '9']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 123: Expected ['у', 'б', '〓'] but got ['=', 'b', '_']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 128: Expected ['υ', 'β', '々'] but got ['*', 'b', '_']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 133: Expected ['ύ', 'b', '_'] but got ['%', 'b', '_']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 138: Expected ['+', 'ب', '〄'] but got ['+', 'b', '_']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 143: Expected ['ק', 'ב', 'ח'] but got ['+', 'B', 'X']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 148: Expected ['ǣ', 'Ǣ', 'X'] but got ['3', '3', 'X']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 153: Expected ['ㄚ', '4', 'X'] but got ['4', '4', 'X']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 158: Expected ['あ', 'ぁ', 'X'] but got ['5', '5', 'X']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 163: Expected ['ァ', 'ア', 'X'] but got ['6', '6', 'X']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 168: Expected ['¹', '²', '³'] but got ['▒', '▒', '▒']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 173: Expected ['₁', '₂', '₃'] but got ['s', 's', 's']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 177: Expected ['ß', '�'] but got ['▒', '▒']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 181: Expected ['á', 'Á'] but got ['▒', '▒']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 198: Expected ['␀', 'ü', '∞', 'l'] but got ['0', '▒', '0', 'l']
Found errors in Test_digraphs_option():
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 6: Expected '∞' but got '0'
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 11: Expected 'þ' but got '▒'
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 15: Expected ['ば', 'ば'] but got ['b', 'a']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 21: Expected ['е', '€', '€', '€'] but got ['=', 'e', 'u', 'E']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 27: Expected ['Р', '₽', '₽', 'П'] but got ['=', 'R', 'P', '=']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 36: Expected ['à', 'è', '!'] but got ['▒', '▒', '!']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 41: Expected ['á', 'é', ''''] but got ['▒', '▒', '''']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 46: Expected ['â', 'ê', '>'] but got ['▒', '▒', '>']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 51: Expected ['õ', 'u', '~'] but got ['▒', 'u', '~']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 56: Expected ['õ', 'ũ', '?'] but got ['▒', 'u', '?']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 61: Expected ['ō', 'ū', '-'] but got ['▒', 'u', '-']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 66: Expected ['ŏ', 'ŭ', '('] but got ['(', 'u', '(']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 71: Expected ['ḃ', 'ė', '.'] but got ['.', 'e', '.']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 76: Expected ['ä', 'ü', ':'] but got ['▒', '▒', ':']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 81: Expected ['¸', 'Ç', ','] but got ['▒', '▒', ',']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 86: Expected ['Ḇ', 'ṯ', '_'] but got ['_', 't', '_']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 91: Expected ['/', 'ł', '/'] but got ['/', 'l', '/']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 96: Expected ['Ő', 'ÿ', '"'] but got ['"', '▒', '"']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 101: Expected ['ų', 'Ę', ';'] but got [';', 'E', ';']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 106: Expected ['ǔ', 'Ě', '<'] but got ['<', 'E', '<']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 111: Expected ['ů', 'E', '0'] but got ['0', 'E', '0']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 116: Expected ['ủ', 'Ẻ', '2'] but got ['2', 'E', '2']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 121: Expected ['ư', 'E', '9'] but got ['9', 'E', '9']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 126: Expected ['у', 'б', '〓'] but got ['=', 'b', '_']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 131: Expected ['υ', 'β', '々'] but got ['*', 'b', '_']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 136: Expected ['ύ', 'b', '_'] but got ['%', 'b', '_']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 141: Expected ['+', 'ب', '〄'] but got ['+', 'b', '_']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 146: Expected ['ק', 'ב', 'ח'] but got ['+', 'B', 'X']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 151: Expected ['ǣ', 'Ǣ', 'X'] but got ['3', '3', 'X']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 156: Expected ['ㄚ', '4', 'X'] but got ['4', '4', 'X']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 161: Expected ['あ', 'ぁ', 'X'] but got ['5', '5', 'X']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 166: Expected ['ァ', 'ア', 'X'] but got ['6', '6', 'X']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 171: Expected ['¹', '²', '³'] but got ['▒', '▒', '▒']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 176: Expected ['₁', '₂', '₃'] but got ['s', 's', 's']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 180: Expected ['ß', '�'] but got ['▒', '▒']
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 201: Expected ['␀', 'ü', '∞', 'l'] but got ['0', '▒', '0', 'l']
Found errors in Test_digraphs_output():
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 3: Expected 'Eu € 8364' but got ''
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 4: Expected '=e € 8364' but got ''
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 5: Expected '=R ₽ 8381' but got ''
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 6: Expected '=P ₽ 8381' but got ''
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 7: Expected 'o: ö 246' but got 'o: ▒ 246'
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 8: Expected 'v4 ㄪ 12586' but got ''
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 9: Expected '''0 ˚ 730' but got ''
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 10: Expected 'Z% Ж 1046' but got ''
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 11: Expected 'u- ū 363' but got ''
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 19: Pattern '^\nNU ^@ 10 .*\nLatin supplement\n!I ¡ 161 .*\n.*\nCustom\\n.*\\<lt < 60\\>' does not match '\nNU ^@ 10 SH ^A 1 SX ^B 2 EX ^C 3 ET ^D 4 EQ ^E 5 AK ^F 6 BL ^G 7 BS ^H 8 HT ^I 9 LF ^@ 10 VT ^K 11 FF ^L 12 CR ^M 13 SO ^N 14 SI ^O 15 DL ^P 16 D1 ^Q 17 D2 ^R 18\nD3 ^S 19 D4 ^T 20 NK ^U 21 SY ^V 22 EB ^W 23 CN ^X 24 EM ^Y 25 SB ^Z 26 EC ^[ 27 FS ^\\ 28 GS ^] 29 RS ^^ 30 US ^_ 31 SP 32 Nb # 35 DO $ 36 At @ 64 <( [ 91 // \\ 92\n)> ] 93 ''> ^ 94 ''! ` 96 (! { 123 !! | 124 !) } 125 ''? ~ 126 DT ^? 127 PA ~@ 128 HO ~A 129 BH ~B 130 NH ~C 131 IN ~D 132 NL ~E 133 SA ~F 134 ES ~G 135 HS ~H 136 HJ ~I 137 VS ~J 138\nPD ~K 139 PU ~L 140 RI ~M 141 S2 ~N 142 S3 ~O 143 DC ~P 144 P1 ~Q 145 P2 ~R 146 TS ~S 147 CC ~T 148 MW ~U 149 SG ~V 150 EG ~W 151 SS ~X 152 GC ~Y 153 SC ~Z 154 CI ~[ 155 ST ~\\ 156 OC ~] 157\nPM ~^ 158 AC ~_ 159 NS | 160\nLatin supplement\n!I ▒ 161 ~! ▒ 161 Ct ▒ 162 c| ▒ 162 Pd ▒ 163 $$ ▒ 163 Cu ▒ 164 ox ▒ 164 Ye ▒ 165 Y- ▒ 165 BB ▒ 166 || ▒ 166 SE ▒ 167 '': ▒ 168 Co ▒ 169 cO ▒ 169 -a ▒ 170 << ▒ 171 NO ▒ 172\n-, ▒ 172 -- ▒ 173 Rg ▒ 174 ''m ▒ 175 -= ▒ 175 DG ▒ 176 ~o ▒ 176 +- ▒ 177 2S ▒ 178 22 ▒ 178 3S ▒ 179 33 ▒ 179 '''' ▒ 180 My ▒ 181 PI ▒ 182 pp ▒ 182 .M ▒ 183 ~. ▒ 183 '', ▒ 184\n1S ▒ 185 11 ▒ 185 -o ▒ 186 >> ▒ 187 14 ▒ 188 12 ▒ 189 34 ▒ 190 ?I ▒ 191 ~? ▒ 191 A! ▒ 192 A` ▒ 192 A'' ▒ 193 A> ▒ 194 A^ ▒ 194 A? ▒ 195 A~ ▒ 195 A: ▒ 196 A" ▒ 196 AA ▒ 197\nA@ ▒ 197 AE ▒ 198 C, ▒ 199 E! ▒ 200 E` ▒ 200 E'' ▒ 201 E> ▒ 202 E^ ▒ 202 E: ▒ 203 E" ▒ 203 I! ▒ 204 I` ▒ 204 I'' ▒ 205 I> ▒ 206 I^ ▒ 206 I: ▒ 207 I" ▒ 207 D- ▒ 208 N? ▒ 209\nN~ ▒ 209 O! ▒ 210 O` ▒ 210 O'' ▒ 211 O> ▒ 212 O^ ▒ 212 O? ▒ 213 O~ ▒ 213 O: ▒ 214 *X ▒ 215 /\\ ▒ 215 O/ ▒ 216 U! ▒ 217 U` ▒ 217 U'' ▒ 218 U> ▒ 219 U^ ▒ 219 U: ▒ 220 Y'' ▒ 221\nTH ▒ 222 Ip ▒ 222 ss ▒ 223 a! ▒ 224 a` ▒ 224 a'' ▒ 225 a> ▒ 226 a^ ▒ 226 a? ▒ 227 a~ ▒ 227 a: ▒ 228 a" ▒ 228 a@ ▒ 229 ae ▒ 230 c, ▒ 231 e! ▒ 232 e` ▒ 232 e'' ▒ 233 e> ▒ 234\ne^ ▒ 234 e: ▒ 235 e" ▒ 235 i! ▒ 236 i` ▒ 236 i'' ▒ 237 i> ▒ 238 i^ ▒ 238 i: ▒ 239 d- ▒ 240 n? ▒ 241 n~ ▒ 241 o! ▒ 242 o` ▒ 242 o'' ▒ 243 o> ▒ 244 o^ ▒ 244 o? ▒ 245 o~ ▒ 245\no: ▒ 246 -: ▒ 247 o/ ▒ 248 u! ▒ 249 u` ▒ 249 u'' ▒ 250 u> ▒ 251 u^ ▒ 251 u: ▒ 252 y'' ▒ 253 th ▒ 254 y: ▒ 255 y" ▒ 255\nCustom\naa B 12354 i D 12356 F 1235800 ^^ 8734 el l 108 lt < 60'
Found errors in Test_show_digraph():
command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_show_digraph line 3: Expected '\n<е> 1077, Hex 0435, Oct 2065, Digr e=' but got '\n<=> 61, Hex 3d, Octal 075'
From test_vim9_assign.vim:
Found errors in Test_assign_lambda():
Caught exception in Test_assign_lambda(): Vim(eval):E119: Not enough arguments for function: <lambda>2 @ command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_assign_lambda[13]..CheckScriptSuccess[6]..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/XScriptSuccess25, line 5
Found errors in Test_assignment_partial():
Caught exception in Test_assignment_partial(): Vim(eval):E119: Not enough arguments for function: ▒▒R194_Func @ command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_assignment_partial[15]..CheckScriptSuccess[6]..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/XScriptSuccess184, line 6
From test_vim9_expr.vim:
Found errors in Test_expr4_equal():
Caught exception in Test_expr4_equal(): Vim(eval):E119: Not enough arguments for function: len @ command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_expr4_equal[96]..CheckDefAndScriptSuccess[2]..CheckScriptSuccess[6]..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/XScriptSuccess155, line 93
From test_vim9_func.vim:
Found errors in Test_partial_call():
Caught exception in Test_partial_call(): Vim(eval):E119: Not enough arguments for function: setloclist @ command line..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_partial_call[25]..CheckDefAndScriptSuccess[2]..CheckScriptSuccess[6]..script /tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir/XScriptSuccess198, line 4
TEST FAILURE
make[2]: *** [Makefile:49: report] Error 1
make[2]: Leaving directory '/tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src/testdir'
make[1]: *** [Makefile:2271: scripttests] Error 2
make[1]: Leaving directory '/tmp/distcc/spack-stage/spack-stage-vim-8.2.3319-yfclkvfy7r6jh45mxy6hpzl2t22u3do3/spack-src/src'
make: *** [Makefile:39: test] Error 2
Can you help me correct them?
I am not sure. At least for the failing digraph test, I suspect the compiled vim is not running with utf-8 encoding, but with latin1 or something similar (or is built without the multibyte feature. Can you please check the :version output and post here?
@chrisbra Have you tested it on some common platforms? (Example: aarch64:centos8 suse) Why is the release so mundane?
12 test cases are the same no matter how many times I test them, can you tell me what you mean? I don't understand what you mean, or if you test them yourself, you will find the error.
[distcc@centos8 vim-8.2.3322]$ make test
……
Test_global_set_clipboard(): clipboard_working feature missing
Test_version_redirect(): cannot start the GUI
-------------------------------
Executed: 4426 Tests
Skipped: 95 Tests
FAILED: 12 Tests
Failures:
From test_digraph.vim:
Found errors in Test_digraph_get_function_encode():
Caught exception in Test_digraph_get_function_encode(): Vim(call):E1215: Digraph must be one character: あ @ command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraph_get_function_encode, line 7
Found errors in Test_digraph_getlist_function():
Caught exception in Test_digraph_getlist_function(): Vim(call):E1215: Digraph must be one character: き @ command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraph_getlist_function, line 2
Found errors in Test_digraph_set_function():
Caught exception in Test_digraph_set_function(): Vim(call):E1215: Digraph must be one character: あ @ command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraph_set_function, line 2
Found errors in Test_digraph_setlist_function():
Caught exception in Test_digraph_setlist_function(): Vim(call):E1215: Digraph must be one character: き @ command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraph_setlist_function, line 1
Found errors in Test_digraphs():
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 3: Expected '∞' but got '0'
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 8: Expected 'þ' but got '▒'
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 12: Expected ['ば', 'ば'] but got ['b', 'a']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 18: Expected ['е', '€', '€', '€'] but got ['=', 'e', 'u', 'E']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 24: Expected ['Р', '₽', '₽', 'П'] but got ['=', 'R', 'P', '=']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 33: Expected ['à', 'è', '!'] but got ['▒', '▒', '!']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 38: Expected ['á', 'é', ''''] but got ['▒', '▒', '''']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 43: Expected ['â', 'ê', '>'] but got ['▒', '▒', '>']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 48: Expected ['õ', 'u', '~'] but got ['▒', 'u', '~']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 53: Expected ['õ', 'ũ', '?'] but got ['▒', 'u', '?']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 58: Expected ['ō', 'ū', '-'] but got ['▒', 'u', '-']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 63: Expected ['ŏ', 'ŭ', '('] but got ['(', 'u', '(']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 68: Expected ['ḃ', 'ė', '.'] but got ['.', 'e', '.']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 73: Expected ['ä', 'ü', ':'] but got ['▒', '▒', ':']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 78: Expected ['¸', 'Ç', ','] but got ['▒', '▒', ',']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 83: Expected ['Ḇ', 'ṯ', '_'] but got ['_', 't', '_']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 88: Expected ['/', 'ł', '/'] but got ['/', 'l', '/']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 93: Expected ['Ő', 'ÿ', '"'] but got ['"', '▒', '"']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 98: Expected ['ų', 'Ę', ';'] but got [';', 'E', ';']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 103: Expected ['ǔ', 'Ě', '<'] but got ['<', 'E', '<']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 108: Expected ['ů', 'E', '0'] but got ['0', 'E', '0']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 113: Expected ['ủ', 'Ẻ', '2'] but got ['2', 'E', '2']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 118: Expected ['ư', 'E', '9'] but got ['9', 'E', '9']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 123: Expected ['у', 'б', '〓'] but got ['=', 'b', '_']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 128: Expected ['υ', 'β', '々'] but got ['*', 'b', '_']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 133: Expected ['ύ', 'b', '_'] but got ['%', 'b', '_']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 138: Expected ['+', 'ب', '〄'] but got ['+', 'b', '_']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 143: Expected ['ק', 'ב', 'ח'] but got ['+', 'B', 'X']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 148: Expected ['ǣ', 'Ǣ', 'X'] but got ['3', '3', 'X']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 153: Expected ['ㄚ', '4', 'X'] but got ['4', '4', 'X']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 158: Expected ['あ', 'ぁ', 'X'] but got ['5', '5', 'X']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 163: Expected ['ァ', 'ア', 'X'] but got ['6', '6', 'X']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 168: Expected ['¹', '²', '³'] but got ['▒', '▒', '▒']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 173: Expected ['₁', '₂', '₃'] but got ['s', 's', 's']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 177: Expected ['ß', '�'] but got ['▒', '▒']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 181: Expected ['á', 'Á'] but got ['▒', '▒']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs line 198: Expected ['␀', 'ü', '∞', 'l'] but got ['0', '▒', '0', 'l']
Found errors in Test_digraphs_option():
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 6: Expected '∞' but got '0'
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 11: Expected 'þ' but got '▒'
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 15: Expected ['ば', 'ば'] but got ['b', 'a']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 21: Expected ['е', '€', '€', '€'] but got ['=', 'e', 'u', 'E']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 27: Expected ['Р', '₽', '₽', 'П'] but got ['=', 'R', 'P', '=']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 36: Expected ['à', 'è', '!'] but got ['▒', '▒', '!']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 41: Expected ['á', 'é', ''''] but got ['▒', '▒', '''']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 46: Expected ['â', 'ê', '>'] but got ['▒', '▒', '>']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 51: Expected ['õ', 'u', '~'] but got ['▒', 'u', '~']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 56: Expected ['õ', 'ũ', '?'] but got ['▒', 'u', '?']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 61: Expected ['ō', 'ū', '-'] but got ['▒', 'u', '-']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 66: Expected ['ŏ', 'ŭ', '('] but got ['(', 'u', '(']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 71: Expected ['ḃ', 'ė', '.'] but got ['.', 'e', '.']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 76: Expected ['ä', 'ü', ':'] but got ['▒', '▒', ':']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 81: Expected ['¸', 'Ç', ','] but got ['▒', '▒', ',']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 86: Expected ['Ḇ', 'ṯ', '_'] but got ['_', 't', '_']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 91: Expected ['/', 'ł', '/'] but got ['/', 'l', '/']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 96: Expected ['Ő', 'ÿ', '"'] but got ['"', '▒', '"']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 101: Expected ['ų', 'Ę', ';'] but got [';', 'E', ';']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 106: Expected ['ǔ', 'Ě', '<'] but got ['<', 'E', '<']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 111: Expected ['ů', 'E', '0'] but got ['0', 'E', '0']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 116: Expected ['ủ', 'Ẻ', '2'] but got ['2', 'E', '2']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 121: Expected ['ư', 'E', '9'] but got ['9', 'E', '9']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 126: Expected ['у', 'б', '〓'] but got ['=', 'b', '_']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 131: Expected ['υ', 'β', '々'] but got ['*', 'b', '_']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 136: Expected ['ύ', 'b', '_'] but got ['%', 'b', '_']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 141: Expected ['+', 'ب', '〄'] but got ['+', 'b', '_']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 146: Expected ['ק', 'ב', 'ח'] but got ['+', 'B', 'X']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 151: Expected ['ǣ', 'Ǣ', 'X'] but got ['3', '3', 'X']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 156: Expected ['ㄚ', '4', 'X'] but got ['4', '4', 'X']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 161: Expected ['あ', 'ぁ', 'X'] but got ['5', '5', 'X']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 166: Expected ['ァ', 'ア', 'X'] but got ['6', '6', 'X']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 171: Expected ['¹', '²', '³'] but got ['▒', '▒', '▒']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 176: Expected ['₁', '₂', '₃'] but got ['s', 's', 's']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 180: Expected ['ß', '�'] but got ['▒', '▒']
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_option line 201: Expected ['␀', 'ü', '∞', 'l'] but got ['0', '▒', '0', 'l']
Found errors in Test_digraphs_output():
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 3: Expected 'Eu € 8364' but got ''
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 4: Expected '=e € 8364' but got ''
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 5: Expected '=R ₽ 8381' but got ''
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 6: Expected '=P ₽ 8381' but got ''
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 7: Expected 'o: ö 246' but got 'o: ▒ 246'
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 8: Expected 'v4 ㄪ 12586' but got ''
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 9: Expected '''0 ˚ 730' but got ''
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 10: Expected 'Z% Ж 1046' but got ''
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 11: Expected 'u- ū 363' but got ''
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraphs_output line 19: Pattern '^\nNU ^@ 10 .*\nLatin supplement\n!I ¡ 161 .*\n.*\nCustom\\n.*\\<lt < 60\\>' does not match '\nNU ^@ 10 SH ^A 1 SX ^B 2 EX ^C 3 ET ^D 4 EQ ^E 5 AK ^F 6 BL ^G 7 BS ^H 8 HT ^I 9 LF ^@ 10 VT ^K 11 FF ^L 12 CR ^M 13 SO ^N 14 SI ^O 15 DL ^P 16 D1 ^Q 17 D2 ^R 18\nD3 ^S 19 D4 ^T 20 NK ^U 21 SY ^V 22 EB ^W 23 CN ^X 24 EM ^Y 25 SB ^Z 26 EC ^[ 27 FS ^\\ 28 GS ^] 29 RS ^^ 30 US ^_ 31 SP 32 Nb # 35 DO $ 36 At @ 64 <( [ 91 // \\ 92\n)> ] 93 ''> ^ 94 ''! ` 96 (! { 123 !! | 124 !) } 125 ''? ~ 126 DT ^? 127 PA ~@ 128 HO ~A 129 BH ~B 130 NH ~C 131 IN ~D 132 NL ~E 133 SA ~F 134 ES ~G 135 HS ~H 136 HJ ~I 137 VS ~J 138\nPD ~K 139 PU ~L 140 RI ~M 141 S2 ~N 142 S3 ~O 143 DC ~P 144 P1 ~Q 145 P2 ~R 146 TS ~S 147 CC ~T 148 MW ~U 149 SG ~V 150 EG ~W 151 SS ~X 152 GC ~Y 153 SC ~Z 154 CI ~[ 155 ST ~\\ 156 OC ~] 157\nPM ~^ 158 AC ~_ 159 NS | 160\nLatin supplement\n!I ▒ 161 ~! ▒ 161 Ct ▒ 162 c| ▒ 162 Pd ▒ 163 $$ ▒ 163 Cu ▒ 164 ox ▒ 164 Ye ▒ 165 Y- ▒ 165 BB ▒ 166 || ▒ 166 SE ▒ 167 '': ▒ 168 Co ▒ 169 cO ▒ 169 -a ▒ 170 << ▒ 171 NO ▒ 172\n-, ▒ 172 -- ▒ 173 Rg ▒ 174 ''m ▒ 175 -= ▒ 175 DG ▒ 176 ~o ▒ 176 +- ▒ 177 2S ▒ 178 22 ▒ 178 3S ▒ 179 33 ▒ 179 '''' ▒ 180 My ▒ 181 PI ▒ 182 pp ▒ 182 .M ▒ 183 ~. ▒ 183 '', ▒ 184\n1S ▒ 185 11 ▒ 185 -o ▒ 186 >> ▒ 187 14 ▒ 188 12 ▒ 189 34 ▒ 190 ?I ▒ 191 ~? ▒ 191 A! ▒ 192 A` ▒ 192 A'' ▒ 193 A> ▒ 194 A^ ▒ 194 A? ▒ 195 A~ ▒ 195 A: ▒ 196 A" ▒ 196 AA ▒ 197\nA@ ▒ 197 AE ▒ 198 C, ▒ 199 E! ▒ 200 E` ▒ 200 E'' ▒ 201 E> ▒ 202 E^ ▒ 202 E: ▒ 203 E" ▒ 203 I! ▒ 204 I` ▒ 204 I'' ▒ 205 I> ▒ 206 I^ ▒ 206 I: ▒ 207 I" ▒ 207 D- ▒ 208 N? ▒ 209\nN~ ▒ 209 O! ▒ 210 O` ▒ 210 O'' ▒ 211 O> ▒ 212 O^ ▒ 212 O? ▒ 213 O~ ▒ 213 O: ▒ 214 *X ▒ 215 /\\ ▒ 215 O/ ▒ 216 U! ▒ 217 U` ▒ 217 U'' ▒ 218 U> ▒ 219 U^ ▒ 219 U: ▒ 220 Y'' ▒ 221\nTH ▒ 222 Ip ▒ 222 ss ▒ 223 a! ▒ 224 a` ▒ 224 a'' ▒ 225 a> ▒ 226 a^ ▒ 226 a? ▒ 227 a~ ▒ 227 a: ▒ 228 a" ▒ 228 a@ ▒ 229 ae ▒ 230 c, ▒ 231 e! ▒ 232 e` ▒ 232 e'' ▒ 233 e> ▒ 234\ne^ ▒ 234 e: ▒ 235 e" ▒ 235 i! ▒ 236 i` ▒ 236 i'' ▒ 237 i> ▒ 238 i^ ▒ 238 i: ▒ 239 d- ▒ 240 n? ▒ 241 n~ ▒ 241 o! ▒ 242 o` ▒ 242 o'' ▒ 243 o> ▒ 244 o^ ▒ 244 o? ▒ 245 o~ ▒ 245\no: ▒ 246 -: ▒ 247 o/ ▒ 248 u! ▒ 249 u` ▒ 249 u'' ▒ 250 u> ▒ 251 u^ ▒ 251 u: ▒ 252 y'' ▒ 253 th ▒ 254 y: ▒ 255 y" ▒ 255\nCustom\naa B 12354 i D 12356 F 1235800 ^^ 8734 el l 108 lt < 60'
Found errors in Test_show_digraph():
command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_show_digraph line 3: Expected '\n<е> 1077, Hex 0435, Oct 2065, Digr e=' but got '\n<=> 61, Hex 3d, Octal 075'
From test_vim9_assign.vim:
Found errors in Test_assign_lambda():
Caught exception in Test_assign_lambda(): Vim(eval):E119: Not enough arguments for function: <lambda>2 @ command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_assign_lambda[13]..CheckScriptSuccess[6]..script /home/sortf/vim-8.2.3322/src/testdir/XScriptSuccess25, line 5
Found errors in Test_assignment_partial():
Caught exception in Test_assignment_partial(): Vim(eval):E119: Not enough arguments for function: ▒▒R193_Func @ command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_assignment_partial[15]..CheckScriptSuccess[6]..script /home/sortf/vim-8.2.3322/src/testdir/XScriptSuccess183, line 6
From test_vim9_expr.vim:
Found errors in Test_expr4_equal():
Caught exception in Test_expr4_equal(): Vim(eval):E119: Not enough arguments for function: len @ command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_expr4_equal[96]..CheckDefAndScriptSuccess[2]..CheckScriptSuccess[6]..script /home/sortf/vim-8.2.3322/src/testdir/XScriptSuccess155, line 93
From test_vim9_func.vim:
Found errors in Test_partial_call():
Caught exception in Test_partial_call(): Vim(eval):E119: Not enough arguments for function: setloclist @ command line..script /home/sortf/vim-8.2.3322/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_partial_call[25]..CheckDefAndScriptSuccess[2]..CheckScriptSuccess[6]..script /home/sortf/vim-8.2.3322/src/testdir/XScriptSuccess198, line 4
TEST FAILURE
make[2]: *** [Makefile:49: report] Error 1
make[2]: Leaving directory '/home/sortf/vim-8.2.3322/src/testdir'
make[1]: *** [Makefile:2271: scripttests] Error 2
make[1]: Leaving directory '/home/sortf/vim-8.2.3322/src'
make: *** [Makefile:39: test] Error 2
Could you show the whole result of :version?
It turned out to be too long for my internet to upload as a file.
It is strange. The output of :version (or vim --version) is typically about 50 lines long.
It should be short enough to paste here.
[distcc@centos8 vim-8.2.3322]$ vim --version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jun 18 2020 15:50:36)
Included patches: 1-1763
Modified by <bugzilla@redhat.com>
Compiled by <bugzilla@redhat.com>
Huge version without GUI. Features included (+) or not (-):
+acl +farsi +mouse_sgr -tag_any_white
+arabic +file_in_path -mouse_sysmouse -tcl
+autocmd +find_in_path +mouse_urxvt +termguicolors
-autoservername +float +mouse_xterm +terminal
-balloon_eval +folding +multi_byte +terminfo
+balloon_eval_term -footer +multi_lang +termresponse
-browse +fork() -mzscheme +textobjects
++builtin_terms +gettext +netbeans_intg +timers
+byte_offset -hangul_input +num64 +title
+channel +iconv +packages -toolbar
+cindent +insert_expand +path_extra +user_commands
-clientserver +job +perl/dyn +vertsplit
-clipboard +jumplist +persistent_undo +virtualedit
+cmdline_compl +keymap +postscript +visual
+cmdline_hist +lambda +printer +visualextra
+cmdline_info +langmap +profile +viminfo
+comments +libcall +python/dyn +vreplace
+conceal +linebreak +python3/dyn +wildignore
+cryptv +lispindent +quickfix +wildmenu
+cscope +listcmds +reltime +windows
+cursorbind +localmap +rightleft +writebackup
+cursorshape +lua/dyn +ruby/dyn -X11
+dialog_con +menu +scrollbind -xfontset
+diff +mksession +signs -xim
+digraphs +modify_fname +smartindent -xpm
-dnd +mouse +startuptime -xsmp
-ebcdic -mouseshape +statusline -xterm_clipboard
+emacs_tags +mouse_dec -sun_workshop -xterm_save
+eval +mouse_gpm +syntax
+ex_extra -mouse_jsbterm +tag_binary
+extra_search +mouse_netterm +tag_old_static
system vimrc file: "/etc/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
defaults file: "$VIMRUNTIME/defaults.vim"
fall-back for $VIM: "/etc"
f-b for $VIMRUNTIME: "/usr/share/vim/vim80"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables -fstack-clash-protection -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/python3.6m -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc -L. -Wl,-z,relro -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -fstack-protector-strong -rdynamic -Wl,-export-dynamic -Wl,--enable-new-dtags -Wl,-z,relro -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -Wl,-z,relro -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -L/usr/local/lib -Wl,--as-needed -o vim -lm -lselinux -lncurses -lacl -lattr -lgpm -ldl -Wl,--enable-new-dtags -Wl,-z,relro -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -Wl,-z,relro -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -fstack-protector-strong -L/usr/local/lib -L/usr/lib64/perl5/CORE -lperl -lpthread -lresolv -ldl -lm -lcrypt -lutil -lc
Your result is from the wrong version of vim.
Could you go to the src directory and run ./vim --version?
[distcc@centos8 src]$ ./vim --version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Aug 10 2021 15:05:14)
Included patches: 1-3322
Compiled by root
Huge version with GTK2 GUI. Features included (+) or not (-):
+acl +file_in_path +mouse_urxvt -tag_any_white
+arabic +find_in_path +mouse_xterm -tcl
+autocmd +float +multi_byte +termguicolors
+autochdir +folding +multi_lang +terminal
-autoservername -footer -mzscheme +terminfo
+balloon_eval +fork() +netbeans_intg +termresponse
+balloon_eval_term +gettext +num64 +textobjects
+browse -hangul_input +packages +textprop
++builtin_terms +iconv +path_extra +timers
+byte_offset +insert_expand -perl +title
+channel +ipv6 +persistent_undo +toolbar
+cindent +job +popupwin +user_commands
+clientserver +jumplist +postscript +vartabs
+clipboard +keymap +printer +vertsplit
+cmdline_compl +lambda +profile +virtualedit
+cmdline_hist +langmap -python +visual
+cmdline_info +libcall -python3 +visualextra
+comments +linebreak +quickfix +viminfo
+conceal +lispindent +reltime +vreplace
+cryptv +listcmds +rightleft +wildignore
+cscope +localmap -ruby +wildmenu
+cursorbind -lua +scrollbind +windows
+cursorshape +menu +signs +writebackup
+dialog_con_gui +mksession +smartindent +X11
+diff +modify_fname -sodium -xfontset
+digraphs +mouse +sound +xim
+dnd +mouseshape +spell +xpm
-ebcdic +mouse_dec +startuptime +xsmp_interact
+emacs_tags -mouse_gpm +statusline +xterm_clipboard
+eval -mouse_jsbterm -sun_workshop -xterm_save
+ex_extra +mouse_netterm +syntax
+extra_search +mouse_sgr +tag_binary
-farsi -mouse_sysmouse -tag_old_static
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
defaults file: "$VIMRUNTIME/defaults.vim"
system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/usr/local/share/vim"
Compilation: /home/spack/spack/lib/spack/env/gcc/gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid -I/usr/include/harfbuzz -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/atk-1.0 -pthread -g -O2 -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: /home/spack/spack/lib/spack/env/gcc/gcc -L/usr/local/lib -Wl,--as-needed -o vim -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype -lSM -lICE -lXpm -lXt -lX11 -lSM -lICE -lm -ltinfo -lselinux -lcanberra -lacl -lattr -ldl
Do you mean that you need to test the corresponding vim version and install the corresponding binary file in the system so that the corresponding version is correct?
What is the output of the locale shell command?
@dpelle I don't know what you're trying to say.
@Tom-python0121 wrote:
I don't know what you're trying to say.
Since we see test failing with some Unicode characters, I'm wondering whether reproducing this issue depends on the locale (i.e. language, etc.). This is what the locale command in the shell gives me (I'm curious what it shows for you):
$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=nl_NL.UTF-8
LC_TIME=nl_NL.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=nl_NL.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=nl_NL.UTF-8
LC_NAME=nl_NL.UTF-8
LC_ADDRESS=nl_NL.UTF-8
LC_TELEPHONE=nl_NL.UTF-8
LC_MEASUREMENT=nl_NL.UTF-8
LC_IDENTIFICATION=nl_NL.UTF-8
LC_ALL=
[distcc@centos8 root]$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
Ah, I can reproduce the failing tests if I do:
$ cd vim/src/testdir
$ LC_ALL=C make test_digraph
...snip...
xecuted 14 tests in 0.145467 seconds
8 FAILED:
Found errors in Test_digraph_get_function_encode():
Caught exception in Test_digraph_get_function_encode(): Vim(call):E1215: Digraph must be one character: あ @ command line..script /home/pel/sb/vim/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraph_get_function_encode, line 7
Found errors in Test_digraph_getlist_function():
Caught exception in Test_digraph_getlist_function(): Vim(call):E1215: Digraph must be one character: き @ command line..script /home/pel/sb/vim/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraph_getlist_function, line 2
Found errors in Test_digraph_set_function():
Caught exception in Test_digraph_set_function(): Vim(call):E1215: Digraph must be one character: あ @ command line..script /home/pel/sb/vim/src/testdir/runtest.vim[486]..function RunTheTest[44]..Test_digraph_set_function, line 2
Found errors in Test_digraph_setlist_function():
...snip...
Yes, I wonder whether the test should check, that encoding is 'utf-8'
@Tom-python0121 can you check the encoding of the built vim? Are you building in some kind of chroot, where e.g. the default unicode locale is not available?
@chrisbra I don't know how to check the encoding of the built vim
Please show the output of :set enc? of the built vim version. So are you building in some kind of chroot, where the default locale is not available?
[distcc@centos8 vim-8.2.3322]$ ls
ci configure CONTRIBUTING.md Filelist LICENSE Makefile nsis pixmaps READMEdir README.md README.txt README_VIM9.md runtime src tools uninstall.txt vimtutor.bat vimtutor.com
[distcc@centos8 vim-8.2.3322]$ set enc?
[distcc@centos8 vim-8.2.3322]$
It doesn't seem to work.
please run the newly built vim binary. And in Vim enter :set enc?
or alternatively, try to run TERMINAL=dumb ./vim --clean -c ':set t_ti= t_te= enc?' -c ':q!'
[distcc@centos8 src]$ ./vim --clean -c ':set t_ti= t_te= enc?' -c ':q!'
E1187: Failed to source defaults.vim
Press ENTER or type command to continue
encoding=utf-8
(I slightly changed your message and removed the whitespace). So encoding looks good. Now the remaining question, are you running building and testing in some kind of a chroot, where the locale is not available?
[root@centos8 /]# ll
total 56
drwxr-xr-x. 2 root root 146 Jun 30 12:09 bad_files
lrwxrwxrwx. 1 root root 7 Nov 3 2020 bin -> usr/bin
drwxrwxrwx. 8 root root 4096 Apr 21 09:14 boot
drwxr-xr-x. 16 root root 2800 Aug 10 14:57 dev
drwxrwxrwx. 154 root root 12288 Aug 10 10:31 etc
drwxr-xr-x. 12 distcc distcc 163 Aug 10 15:01 home
lrwxrwxrwx. 1 root root 7 Nov 3 2020 lib -> usr/lib
lrwxrwxrwx. 1 root root 9 Nov 3 2020 lib64 -> usr/lib64
drwxrwxrwx. 2 root root 6 Nov 3 2020 media
drwxrwxrwx. 2 root root 6 Nov 3 2020 mnt
-rw-r--r--. 1 root root 24 Jul 10 11:37 No_such_file_as_this
drwxrwxrwx. 5 root root 45 Jun 25 10:16 opt
dr-xr-xr-x. 205 root root 0 Jan 1 1970 proc
drwxrwxr-x. 48 root root 4096 Aug 10 18:34 root
drwxr-xr-x. 46 root root 1220 Aug 6 14:08 run
lrwxrwxrwx. 1 root root 8 Nov 3 2020 sbin -> usr/sbin
drwxr-xr-x. 2 root root 6 Nov 3 2020 srv
dr-xr-xr-x. 12 root root 0 Jun 22 2018 sys
drwxrwxrwt. 67 distcc distcc 61440 Aug 10 19:12 tmp
drwxrwxrwx. 14 root root 188 Jul 28 11:40 usr
drwxr-xr-x. 23 root root 4096 Aug 4 12:30 var
Does it have anything to do with my authority?
okay, can you please explain in more details, how you do the whole compilation thing? Did you setup something? Are you setting some environment variables like LC_ALL=C or something similar. Please a bit more details here.
apparently you use distcc, that's why I am asking.
Could you show the exact commands which you used to build vim?
How did you get the source code of vim? Git or something else?
Do you set any special environment variables like VIM, VIMRUNTIME, or VIMPROG?
What does printenv | grep VIM show? (run on the shell)
@Tom-python0121 wrote:
[distcc@centos8 src]$ ./vim --clean -c ':set t_ti= t_te= enc?' -c ':q!'
E1187: Failed to source defaults.vim
That's not expected. Maybe the bug reporter ran some commands as root earlier and some files are only readable or writable as root, causing havoc when then running tests as non-root user? Try re-creating your git clone from scratch as a regular user.
I almost never login as root. It's always dangerous. Installing vim does not require being root.
I install vim like this for example:
$ cd vim
$ configure --with-features=huge --enable-gui=gtk3 --enable-luainterp=yes --with-luajit
$ make -j8
$ make test
$ sudo make install
It's not good indeed, but it usually happens, if you run the self-compiled vim without installation. That's because the vim cannot find the runtime directory. The test suite works around that by explicitly setting the $VIMRUNTIME environment variable.
@Tom-python0121 wrote:
[root@centos8 /]# ll
total 56
drwxr-xr-x. 2 root root 146 Jun 30 12:09 bad_files
lrwxrwxrwx. 1 root root 7 Nov 3 2020 bin -> usr/bin
drwxrwxrwx. 8 root root 4096 Apr 21 09:14 boot
drwxr-xr-x. 16 root root 2800 Aug 10 14:57 dev
drwxrwxrwx. 154 root root 12288 Aug 10 10:31 etc
drwxr-xr-x. 12 distcc distcc 163 Aug 10 15:01 home
lrwxrwxrwx. 1 root root 7 Nov 3 2020 lib -> usr/lib
lrwxrwxrwx. 1 root root 9 Nov 3 2020 lib64 -> usr/lib64
drwxrwxrwx. 2 root root 6 Nov 3 2020 media
drwxrwxrwx. 2 root root 6 Nov 3 2020 mnt
-rw-r--r--. 1 root root 24 Jul 10 11:37 No_such_file_as_this
drwxrwxrwx. 5 root root 45 Jun 25 10:16 opt
dr-xr-xr-x. 205 root root 0 Jan 1 1970 proc
drwxrwxr-x. 48 root root 4096 Aug 10 18:34 root
drwxr-xr-x. 46 root root 1220 Aug 6 14:08 run
lrwxrwxrwx. 1 root root 8 Nov 3 2020 sbin -> usr/sbin
drwxr-xr-x. 2 root root 6 Nov 3 2020 srv
dr-xr-xr-x. 12 root root 0 Jun 22 2018 sys
drwxrwxrwt. 67 distcc distcc 61440 Aug 10 19:12 tmp
drwxrwxrwx. 14 root root 188 Jul 28 11:40 usr
drwxr-xr-x. 23 root root 4096 Aug 4 12:30 var
Odd things in your root / directory:
file No_such_file_as_this should not be there
directory bad_files should not be there
/tmp and /home/ are owned by distcc instead root
date of /proc is: Jan 1 1970 ?!
That's a lot of suspicious things there already.
I can reproduce with LC_ALL=C make test_digraph.
It's not that 'encoding' is not set to utf-8, in the first function that fails an assert for &encoding does not fail.
Also scriptencoding utf-8 at the top of the file doesn't help. Strange.
Ah, the test does set encoding& instead of set encoding=utf-8
|
gharchive/issue
| 2021-08-10T06:43:01 |
2025-04-01T04:36:14.491561
|
{
"authors": [
"Tom-python0121",
"brammool",
"chrisbra",
"dpelle",
"k-takata"
],
"repo": "vim/vim",
"url": "https://github.com/vim/vim/issues/8742",
"license": "Vim",
"license_type": "permissive",
"license_source": "github-api"
}
|
1300020819
|
remove misleading :3mat from the documentation
When skimming over documentation it is easy to erroneously believe one can use ":3mat" command - see my recent bug report #10690 instantly closed by @chrisbra ))))
Thinking about it a bit, may be this is good idea to officially remove ":3mat" from the documentation. For normal use cases it is anyway not (really) available, it can be only used (as far as I understood) only in some exotic circumstances - for example that standard matchit plugin is deactivated?
Another "improvement" - documentation encourages plugin authors to use ":2mat". Is it not better to leave ":mat" and ":2mat" for interactive usage entirely and ask plugin authors to use matchadd() call directly?
On 2022-07-10, haron13-2019 wrote:
When skimming over documentation it is easy to erroneously believe one can use
":3mat" command - see my recent bug report #10690 instantly closed by @chrisbra
))))
Thinking about it a bit, may be this is good idea to officially remove ":3mat"
from the documentation. For normal use cases it is anyway not (really)
available, it can be only used (as far as I understood) only in some exotic
circumstances - for example that standard matchit plugin is deactivated?
Another "improvement" - documentation encourages plugin authors to use ":2mat".
Is it not better to leave ":mat" and ":2mat" for interactive usage entirely and
ask plugin authors to use matchadd() call directly?
I think your change goes too far. The :3match command does exist
and it can be used. In fact, it is used, by the matchparen
plugin. I don't think that hiding it or pretending that it doesn't
exist benefits the user. I certainly would not remove the mentions
of the matchparen plugin.
For example, matcharg(3) returns a different result than matcharg(4)
and :3match will work while :4match will fail. This could be
confusing to the user without an discoverable explanation.
The semi-reserved status of match ID 3 should be mentioned in a few
more places, such as ":help matchadd()", but I would not remove any
of the existing documentation on it.
Regards,
Gary
If someone reads the source of the matchparen (not matchit) plugin and tries to understand what it does when and how, he'll find that the :3match instruction is used. IMHO it runs totally against the whole Vim philosophy to have such a feature intentionally entirely undocumented: in Vim, everything is documented (or if not, it is an unintentional oversight).
Best regards,
Tony.
As mentioned, removing the :3match command and other info goes against the intention of having help for everything.
I'll include some remarks where a match is added that the ID three is being used by matchparen.
|
gharchive/pull-request
| 2022-07-10T21:27:11 |
2025-04-01T04:36:14.501755
|
{
"authors": [
"brammool",
"haron13-2019",
"tonymec",
"vim-ml"
],
"repo": "vim/vim",
"url": "https://github.com/vim/vim/pull/10691",
"license": "Vim",
"license_type": "permissive",
"license_source": "github-api"
}
|
929098766
|
Add support for elixir filetypes
resolves #8401
In this PR description I'm using ^[text] to signify a line in the file starting with "text" and followed by a space. I.e., column 1 is occupied by a non-whitespace character.
Notes
I removed *.sface as an elixir filetype, which was listed as such in the issue. While Surface is a relatively popular UI library for Elixir/Phoenix/LiveView, it's not part of elixir core. All the other filetypes are.
I checked the first 10 lines of every .ex file in OpenEuphoria and found that almost every file had a line either starting with ^-- or ^include . I added a regex check for these most common lines in the first commit. (One interesting result in GitHub search is "--" extension:ex language:elixir. One of the top results is a self-identified Euphoria4 file incorrectly identified by GitHub as an elixir file.)
There were only 3 of out 40+ .ex euphoria files in OpenEuphoria that were not correctly identified by ^-- or ^include
One could be detected via ^ifdef (in fact, top advanced GitHub results for this show misidentified euphoria files).
The other two could be detected via ^--[text] , where [text] is any word.
I included checks against both of these scenarios in the second commit.
Other Euphoria keywords that likely never begin a line of elixir code are ^without , ^constant , and ^integer . I corroborated this via a brief advanced GitHub search of type [keyword] extension:ex language:elixir. I left these out of dist#ft#ExCheck because I worry about being too expansive in our regex checks, which could risk edge-case misidentification.
I was unsure how to best test dist#ft#ExCheck, though I did add tests for the other elixir filetypes.
Questions
Lastly, do you recommend this PR include updates to vim/runtime/doc/syntax.txt and vim/runtime/doc/tags?
Thanks for the PR.
Can you please add a test for the dist#ft#ExCheck() function?
Exercising the three possible outcomes.
There are some examples near the end of test_filetype.vim.
Hey @brammool , added a Test_ex_file() covering the four match cases.
OK, but the test only checks getting "euphoria3". Well, there is a test getting "elixir" for an empty file, in the big table. Please add a test case using g:filetype_euphoria. Best is to use a file that detects as "elixir" first, then results in g:filetye_euphoria once that is set.
I actually had not added the empty-file test for file.ex, but since this will now be the new default filetype for that extension, I went ahead and added it there, in addition to testing again in the (now more robust) test of dist#ft#ExCheck.
I cleaned up the regex regarding the detection of lines starting with --. I was checking for both whitespace and non-whitespace, so just simplified it to ^--\|....
|
gharchive/pull-request
| 2021-06-24T10:49:14 |
2025-04-01T04:36:14.510192
|
{
"authors": [
"aegatlin",
"brammool"
],
"repo": "vim/vim",
"url": "https://github.com/vim/vim/pull/8446",
"license": "Vim",
"license_type": "permissive",
"license_source": "github-api"
}
|
1064828939
|
TermDebug with clean start
set pagination off before we start gdb - because attaching to a program with some shared objects and symbols will otherwise trigger the pagination during attach
removed -set target-async on because we already require GDB 7.12 and mi-async on was added with GDB 7.8 (also set this early, because when attaching to running programs we'll otherwise get a "can't set while program is running" error)
set args for gdb with server-prefix, follow on to #9079
split setting of internal gdb_cmd to allow direct comments for the settings and removed the intermediate cmd
With these changes:
my previous setup works faster (just as a note, it starts vim directly in debugging mode with -c 'Termdebug -ix script_which_enables_history executable' -c "call :TermDebugSemdCommand('server source big_gdb_script_which_attaches')")
for the very first time the attach option works for me also with programs that have many shared libraries loaded
:Termdebug -p 1234 works fine (Note: I think this should be either added to Termdebug help and the -p may be automatically done when Termdebug 1234 is used [ok brakes the rare debugging an executable which only consists of digits - do we care?] (which would of course also go to the Termdebug help...) as on environments where Vim works and GDB 7.12+ is used I see no reason to not let GDB decide which executable is running under the pid)
As I now see the message "startup done" only after the loaded symbols I think there's a high chance that this also fixes the many symbols issue which was the reasoning behind #4587. @bartlibert do you mind checking that?
Let me include this and then we can check for any issues.
I still see the issue with large projects (although the message seems to come later than before)
@bartlibert Can you please show what you exactly use and what happens with the updated code in there referenced issue (#4587, I guess)? This may provide some hints what is missing.
|
gharchive/pull-request
| 2021-11-26T22:11:26 |
2025-04-01T04:36:14.515452
|
{
"authors": [
"GitMensch",
"bartlibert",
"brammool"
],
"repo": "vim/vim",
"url": "https://github.com/vim/vim/pull/9231",
"license": "Vim",
"license_type": "permissive",
"license_source": "github-api"
}
|
305508474
|
Pattern copy
I haven't seen any functionality to copy a pattern. For example, when creating a 2nd part of a pattern I would like to be able to take the 1st part of the pattern as a basis and then add in slight variations (same goes for creating new patterns).
Is there a way to do this that I've missed? Or is this a feature you'd be interested in adding? If so, I'm happy to give it a go :)
Nope, you didn't miss anything :)
Unfortunately that pattern copy functionality doesn't exist in the original TR-808, and while there are lots of (not necessarily web based) 808 clones that try to provide productivity enhancements, the goal of this project is to provide 1:1 functionality with the original drum machine for historical and educational purposes. Due to that it is extremely unlikely that I'd add/integrate that functionality into this project.
I know that's probably a frustrating answer but I hope you can understand where I'm coming from.
Thanks for the answer. That makes perfect sense, so I totally understand where you're coming from
|
gharchive/issue
| 2018-03-15T11:13:37 |
2025-04-01T04:36:14.600399
|
{
"authors": [
"matthewh806",
"vincentriemer"
],
"repo": "vincentriemer/io-808",
"url": "https://github.com/vincentriemer/io-808/issues/25",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
67108121
|
Invalid paste handling
for example
[self.passNumber setMask:@"## ## ######"];
trying to insert 123456789 in empty text field
the result is 12 45 789123456789
Hello sadgb, thank you for contact.
Could give me more details of this bug?
I tried to reproduce it and could not.
thanks!
|
gharchive/issue
| 2015-04-08T11:28:05 |
2025-04-01T04:36:14.602287
|
{
"authors": [
"sadgb",
"viniciusmo"
],
"repo": "viniciusmo/VMaskTextField",
"url": "https://github.com/viniciusmo/VMaskTextField/issues/7",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
237423960
|
Beast CMakeLists.txt MSVC link fail
@ 6fab138150e6f61736a158c34c043a13d18e2f2a
I'm not 100% sure link_directories should go away. I had a link fail on MSVC 15.2 because system has several other libraries it tries to link in. Normally this isn't a problem if you download and install the boost libraries but since I built the boost libraries on a separate drive the link step didn't know where to find things like libboost_date_time.lib. The quick solution:
link_directories(${Boost_LIBRARY_DIR_RELEASE})
link_directories(${Boost_LIBRARY_DIR_DEBUG})
Why both? They might be disjoint directories.
Additionally this could potentially be fixed within find_package but that might be outside the scope of Beast :wink:
By the way the code I removed was wrong:
link_directories(${Boost_LIBRARY_DIR})
It should be Boost_LIBRARY_DIRS
I'm adding
This results in the following Additional Library Directories:
$(BOOST_ROOT)/stage/lib
$(BOOST_ROOT)/stage/lib/$(Configuration)
That should cover the case you mentioned
This was merged to version 64
https://github.com/vinniefalco/Beast/commit/8449697a2c225688a9cf8e4fcf01206d56903b85
If its still a problem feel free to re-open the issue or to create a new one, thanks!
|
gharchive/issue
| 2017-06-21T06:05:15 |
2025-04-01T04:36:14.606394
|
{
"authors": [
"cdacamar",
"vinniefalco"
],
"repo": "vinniefalco/Beast",
"url": "https://github.com/vinniefalco/Beast/issues/522",
"license": "BSL-1.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
221921367
|
1.0.0-b33
Require Visual Studio 2015 Update 3 or later
HTTP
Use fwrite return value in file_body
WebSocket
Set internal state correctly when writing frames
Add decorator unit test
Add write_frames unit test
Codecov Report
Merging #304 into master will increase coverage by 0.01%.
The diff coverage is 100%.
@@ Coverage Diff @@
## master #304 +/- ##
==========================================
+ Coverage 94.9% 94.92% +0.01%
==========================================
Files 88 88
Lines 6206 6207 +1
==========================================
+ Hits 5890 5892 +2
+ Misses 316 315 -1
Impacted Files
Coverage Δ
include/beast/core/prepare_buffers.hpp
100% <ø> (ø)
:arrow_up:
include/beast/zlib/inflate_stream.hpp
100% <ø> (ø)
:arrow_up:
include/beast/http/header_parser_v1.hpp
100% <ø> (ø)
:arrow_up:
include/beast/http/chunk_encode.hpp
100% <ø> (ø)
:arrow_up:
include/beast/http/basic_fields.hpp
100% <ø> (ø)
:arrow_up:
include/beast/core/dynabuf_readstream.hpp
100% <ø> (ø)
:arrow_up:
include/beast/zlib/deflate_stream.hpp
100% <ø> (ø)
:arrow_up:
include/beast/core/static_streambuf.hpp
100% <ø> (ø)
:arrow_up:
include/beast/core/buffer_cat.hpp
100% <ø> (ø)
:arrow_up:
include/beast/core/streambuf.hpp
100% <ø> (ø)
:arrow_up:
... and 27 more
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b8e5a21...ccefa54. Read the comment docs.
Attention:
@nctusdk
@matinko
|
gharchive/pull-request
| 2017-04-15T02:31:21 |
2025-04-01T04:36:14.621588
|
{
"authors": [
"codecov-io",
"vinniefalco"
],
"repo": "vinniefalco/Beast",
"url": "https://github.com/vinniefalco/Beast/pull/304",
"license": "BSL-1.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
484649924
|
Materials for ViroQuad don't render
Environment
Development OS: Windows
Device OS & Version: Windows 10 Home 64-bit
Version: ViroReact 2.16.0 and React Native 0.59.3
Device(s): iPhone6s iOS version 12.4
Description
Hey guys! I'm trying to render a ViroQuad after a marker is detected, but materials are not rendering, so I can't see the ViroQuad. Extra: Shadows are visible.
Reproducible Demo
render() {
return (
<ViroARImageMarker
target={"myTarget"}
onAnchorFound={this._onAnchorFound}
pauseUpdates={this.state.pauseUpdates}
>
... some code
<Viro3DObject
source={require('./res/objects/Munny.obj')}
type="OBJ"
scale={[.005, .005, .005]}
rotation={[0,-90,0]}
materials={this.state.texture}
animation={{ name: this.state.currentMunnyAnimation, run: this.state.animateMunny, loop: this.state.loopMunnyAnimation, onFinish: this._changeMunnyAnimation, interruptible: true }}
onClick={this._toggleButtons}
/>
<ViroText
text="A geeky creative agency"
style={styles.default_text}
width={1000}
materials={["white_mtl"]}
scale={[0,0,0]}
position={[0,0,.05]}
extrusionDepth={4}
animation={{ name: this.state.currentTextAnimation, run: this.state.animateText, loop: true, onFinish: this._changeTextAnimation, interruptible: true }}
/>
<ViroSpotLight
innerAngle={5}
outerAngle={60}
direction={[1,-1,-1]}
position={[-1,3,3]}
color="#ffffff"
castsShadow={true}
shadowMapSize={2048}
shadowNearZ={2}
shadowFarZ={7}
shadowOpacity={.2}
intensity={100}
/>
<ViroQuad
rotation={[-90, 0, 0]}
position={[0, -0.001, 0]}
width={.5} height={.5}
arShadowReceiver={true}
materials={["bone"]}
/>
</ViroARImageMarker>
</ViroARScene>
);
}
... more code
}
Thank you very much in advance!
Cheers!
Can you provide how the code where you've defined the "bone" material that you are setting on the quad?
Sure! It is:
bone: {
diffuseColor: "rgb(245,245,220)",
lightingModel: "PBR",
}
Interesting, so I don't think you can re-use the "AR Shadow Quad" that you have above (and apply another material on it). This is because that quad's material is already being used to generate the fake shadow that you see.
You can try using a separate second quad for your material instead (one without any arShadowReceiver references)
ok, now it works perfect! thank you for the advice!
|
gharchive/issue
| 2019-08-23T18:08:10 |
2025-04-01T04:36:14.666092
|
{
"authors": [
"dthian",
"tomascg2309"
],
"repo": "viromedia/viro",
"url": "https://github.com/viromedia/viro/issues/705",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1447443029
|
Create Component Navbar
Creation of the Navbar Component:
Navbar Mockup
https://docs.google.com/drawings/d/1N4wB9z9lZAHw7JOiO1rvy6LTY-06ieYnnuSoFdW5SRU/edit
Basic design completed - will push to main when ready
Waiting for more information to adjust to dropdowns
|
gharchive/issue
| 2022-11-14T06:02:49 |
2025-04-01T04:36:14.669211
|
{
"authors": [
"csonoda"
],
"repo": "virtual-campus-tour/virtual-campus-tour",
"url": "https://github.com/virtual-campus-tour/virtual-campus-tour/issues/2",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1521744924
|
Fetching community numbers from the API
Our home page takes a few seconds to render, technically because we are using APIs and web scraping to fetch 4 numbers -
YouTube subscriber count
Twitter follower count
Discord member count
Hashnode follower count
We fetch these values when the page is getting loaded from the views. Instead, we could bring them from the APIs (api.py) and update the numbers by making a get request to the API we create to improve the speed of the page.
yes, I think this is the reason of high initial server response time as mentioned in the page speed insights which is taking almost 3 seconds to load
|
gharchive/issue
| 2023-01-06T01:57:56 |
2025-04-01T04:36:14.682152
|
{
"authors": [
"VenkataBhaskarr",
"apoorv-on-git"
],
"repo": "virtual-tech-school/virtual-tech-school",
"url": "https://github.com/virtual-tech-school/virtual-tech-school/issues/8",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
3241562
|
Watch option does not reload the actual changed file
Running mocha with the --watch option will only reload the tests sources, and never reload changes in the application's source files. It means that it is actually impossible to fix the offending application code while running in watch mode. I assume this is not the desired behavior :-)
Attached commit fixes this by removing the changed file from the require-cache before re-running the suite.
haha, this is what happens when I dont use the feature at all :D
actually no, this doesn't fix anything, you're still not require()ing it af
Oh, thats a good point! Yeah, guess this would only reload changed files as long as they are require'd directly from one of the tests.
Anyways, that means the watcher feature is still kinda broken. Any ideas on how to fix it?
we'll have to walk the .parent properties and kill the cache for all of them
That will still not work quite as it should. Consider the following example:
in bar.js:
exports.foo = require("./foo");
in test/foo.js:
var foo = require('./bar').foo
// (...) tests for foo
Now changes to foo.js will not be reloaded and the test will fail somewhat unexpectedly until bar.js is changed...
IMHO, a better solution would be to invalidate cache for all watched files. I've done this already in my fork, here: https://github.com/bjoerge/mocha/commit/d256ad7602d4fa35b1d0c0b615f78bf0173641c4.
Let me know if you'd like me to send a new pull request.
yeah that would be fine too, no point with the while/shift though we can just forEach them
Same here, my project is split into several node_modules and anything in another module won't ever get reloaded.
@jareware you will want to investigate other options.
@mochajs/mocha what if we threw a "DEPRECATED" label on --watch in the docs? This would make me happy.
@boneskull yeah I get that feeling reading any issues related to watching here... :) The sad part is when you're e.g. transpiling a large codebase with Babel, the --watch method is a lot faster than an external watch tool (I've been using https://github.com/kimmobrunfeldt/chokidar-cli for that), as it only recompiles changed modules. Whereas the external one will just start from scratch every time.
|
gharchive/issue
| 2012-02-15T20:42:11 |
2025-04-01T04:36:14.707507
|
{
"authors": [
"bjoerge",
"boneskull",
"jareware",
"visionmedia"
],
"repo": "visionmedia/mocha",
"url": "https://github.com/visionmedia/mocha/issues/266",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
5887350
|
Calling .query() after .set() is ignored
The query parameter here get's dropped on the floor, since set() internally calls request() which processes the internal _query queue.
request.get('http://blah.com/')
.set('Accept', '*/*')
.query({ 'foo': 'bar' })
.end()
Recommendation is to move the _query processing logic into end().
Is this still an issue? This is really old.
Closing. Let me know if I need to re-open.
|
gharchive/issue
| 2012-07-27T22:13:25 |
2025-04-01T04:36:14.709399
|
{
"authors": [
"TooTallNate",
"defunctzombie"
],
"repo": "visionmedia/superagent",
"url": "https://github.com/visionmedia/superagent/issues/108",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
1659595360
|
Update nuxt.md due to typo
Typo, 2 times offlineReady instead of updateReady and offlineReady
@s0h311 it is needRefresh
@userquin oh, Now I commited it with the correct one.
|
gharchive/pull-request
| 2023-04-08T17:49:21 |
2025-04-01T04:36:14.744728
|
{
"authors": [
"s0h311",
"userquin"
],
"repo": "vite-pwa/docs",
"url": "https://github.com/vite-pwa/docs/pull/40",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1099494202
|
Unexpected error parsing sass module
Describe the bug
When importing a react component into hydrogen (which uses vite) i get a vite error
11:27:24 AM [vite] Error when evaluating SSR module /src/components/Header.client.jsx?no-proxy:
/home/ubuntu/vite-error/node_modules/@mytheme/header-menu/dist/header-menu.module.scss:1
.middle-bar {
^
SyntaxError: Unexpected token '.'
at Object.compileFunction (node:vm:352:18)
at wrapSafe (node:internal/modules/cjs/loader:1026:15)
at Module._compile (node:internal/modules/cjs/loader:1061:27)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
at Module.load (node:internal/modules/cjs/loader:975:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Module.require (node:internal/modules/cjs/loader:999:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object. (/home/ubuntu/vite-error/node_modules/@mytheme/header-menu/dist/header-menu.js:8:51)
at Module._compile (node:internal/modules/cjs/loader:1097:14)
11:27:24 AM [vite] Error when evaluating SSR module /src/components/Header.client.jsx:
/home/ubuntu/vite-error/node_modules/@mytheme/header-menu/dist/header-menu.module.scss:1
Reproduction
https://github.com/micalexander/vite-error
System Info
Need to install the following packages:
envinfo
Ok to proceed? (y)
System:
OS: Linux 5.11 Ubuntu 20.04.3 LTS (Focal Fossa)
CPU: (8) x64 Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz
Memory: 5.84 GB / 15.58 GB
Container: Yes
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 17.3.0 - ~/.nvm/versions/node/v17.3.0/bin/node
npm: 8.3.0 - ~/.nvm/versions/node/v17.3.0/bin/npm
Browsers:
Chrome: 97.0.4692.71
Firefox: 95.0.1
npmPackages:
vite: ^2.7.0 => 2.7.10
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.
I can't npm install in the repro. Looks like it's using a private package:
npm ERR! code E404
npm ERR! 404 Not Found - GET https://node.bit.dev/@zoxllc/zox.ui.header-menu/-/@zoxllc-zox.ui.header-menu-0.0.3.tgz - Not found
npm ERR! 404
npm ERR! 404 '@zoxllc/zox.ui.header-menu@https://node.bit.dev/@zoxllc/zox.ui.header-menu/-/@zoxllc-zox.ui.header-menu-0.0.3.tgz' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
According to the error message ?no-proxy. This doesn't seem to exist in Vite. Perhaps it's a bug in Hydrogen?
Closing due to lack of response, please provide a repro without the private package so this can be tested.
|
gharchive/issue
| 2022-01-11T18:29:41 |
2025-04-01T04:36:14.754388
|
{
"authors": [
"bluwy",
"micalexander"
],
"repo": "vitejs/vite",
"url": "https://github.com/vitejs/vite/issues/6460",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
976033866
|
fix: check for Blob before creating worker URL (close #4462)
Description
Fixes #4462
With server-side rendering, in my case Next.js, Blob isn't defined in Node.js. That causes the generated output for web workers to fail. This adds a check for the availability of Blob to the generated code. In its absence, the previous approach is being used. The concatenation of a long string introduces a slight inefficiency. However, I'm happy that things work again and the function WorkerWrapper may not even be called.
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.
I'm not really sure how to test this but I'm open to suggestions.
Can we implement a test for the new behavior that fails without the change?
I adapted the test from #3468 that introduced the use of Blob for creating a worker.
Could you please tell me if this is scheduled to be merged and released? It would really help with the issue that I have with using the current version of https://github.com/hms-dbmi/viv
|
gharchive/pull-request
| 2021-08-21T03:59:06 |
2025-04-01T04:36:14.760758
|
{
"authors": [
"Shinigami92",
"andreasg123"
],
"repo": "vitejs/vite",
"url": "https://github.com/vitejs/vite/pull/4674",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1323357345
|
fix(resolve): fix commonjs plugin 'HELPERS_ID'
Description
This PR fixes the commonjs HELPERS_ID (reference link) in resolve plugin.
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).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.
In fact, after #8743, this condition was never hit because commonjs plugin is always the first one.
https://github.com/rollup/plugins/blob/add3a350e99505e15790b4915c33b1fcc5bf00ec/packages/commonjs/src/index.js#L186-L199
Maybe we could simply remove this condition?
I'm not sure. I don't have much knowledge of the codebase but could a custom plugin change the ordering of internal plugins by implementing the options hook? If yes, then, you might still need to keep this condition. Or do you not care about what custom plugins do?
Interesting find @sapphi-red. I'd also prefer if we remove this condition instead since it won't be called. I don't think there will be a custom plugin that would sort Vite's resolve plugin to first, that would break many things.
FYI This was introduced in plugin-commonjs v22.0.0. The reason is described here.
|
gharchive/pull-request
| 2022-07-31T04:15:42 |
2025-04-01T04:36:14.767729
|
{
"authors": [
"bluwy",
"sagargurtu",
"sapphi-red"
],
"repo": "vitejs/vite",
"url": "https://github.com/vitejs/vite/pull/9460",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1703815348
|
vitest 0.31.0 breaks vi.fn
Describe the bug
Using vi.fn in vi.mock not working anymore after upgrading to vitest 0.31.0. The function with vi.fn returns only undefined, ignoring the own implementation.
I have attached two Stackblitz examples with two test files, one with vi.fn', the other without. You will see that on v0.30.0 both variants work, after upgrading to v0.31.0 only the one without vi.fn` works.
Reproduction
Stackblitz with vitest@0.30.0: https://stackblitz.com/edit/node-ltocvc
Stackblitz with vitest@0.31.0: https://stackblitz.com/edit/node-fsagxk
System Info
From stackblitz:
System:
OS: Linux 5.0 undefined
CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Memory: 0 Bytes / 0 Bytes
Shell: 1.0 - /bin/jsh
Binaries:
Node: 16.14.2 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 7.17.0 - /usr/local/bin/npm
npmPackages:
vite: 4.3.5 => 4.3.5
vitest: ^0.31.0 => 0.31.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.
Stackblitz doesn't even call vi.mock, but locally it works 🤔
This issue is probably a duplicate of https://github.com/vitest-dev/vitest/issues/3335
|
gharchive/issue
| 2023-05-10T12:26:44 |
2025-04-01T04:36:14.777482
|
{
"authors": [
"BC-M",
"sheremet-va"
],
"repo": "vitest-dev/vitest",
"url": "https://github.com/vitest-dev/vitest/issues/3340",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1846770127
|
Unexpected output when logging HTML in @vitest/ui
Describe the bug
Happened while writing tests for a Vite plugin load hook, using fs.readFileSync.
I was reading a Vue basic component, and the <template> turned into an HTML fragment, from a console.log in the Vitest UI.
This is the output when displaying it in Vitest UI:
Running the same readFileSync from Node:
Where Vitest UI turns it into an HTML fragment:
Let me know if you need any further explanations.
Also, if you can give me guidelines, I can most likely help to solve this via a PR!
Thanks again for Vitest! 🙏
Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-zhysj6?file=test/basic.test.ts&initialPath=__vitest__/
Run test:run to see proper output in console.
Run test:ui to see wrong output in side-panel of the test.
System Info
System:
OS: macOS 13.4
CPU: (10) arm64 Apple M1 Pro
Memory: 163.50 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.16.0 - ~/.volta/tools/image/node/18.16.0/bin/node
Yarn: 1.22.19 - ~/.volta/tools/image/yarn/1.22.19/bin/yarn
npm: 9.5.1 - ~/.volta/tools/image/node/18.16.0/bin/npm
pnpm: 8.6.1 - ~/.volta/bin/pnpm
Browsers:
Chrome: 115.0.5790.170
Safari: 16.5
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.
Fixed by https://github.com/vitest-dev/vitest/pull/4724
|
gharchive/issue
| 2023-08-11T12:49:35 |
2025-04-01T04:36:14.785368
|
{
"authors": [
"AriPerkkio",
"Tahul"
],
"repo": "vitest-dev/vitest",
"url": "https://github.com/vitest-dev/vitest/issues/3934",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1407029015
|
Vite 3 migration
Various changes to migrate to Vite 3.0. Only tested on Windows 11.
Use --api.port instead of --api.
Bind to 127.0.0.1 instead of localhost (breaking change)
Fix parsing error by escaping special characters in test names (e.g., "add 1 + 1" => "add 1 \+ 1")
Stop capitalizing the first character of the test file path name. I'm not entirely sure why this was being done originally, but it was creating a mismatch with the way vitest was gathering the test file names. Vitest does a simple case-sensitive .includes() check, so c:\ was not matching the C:\ in the paths that vitest is producing. This case-sensitive matching was breaking the "Debug Test" feature.
that good, hope this will be merge soon
Just tested it on mac. Looks great. Thanks!
@falynx please take a look, I tested you new code but the case sensitive on window still not working, it's fail on my windows computer on version 0.2.32
[INFO 2:35:05 PM]
> losa@0.0.0 test:run g:\small-cosmos\losa
> vitest run --config ./configs/vitest/vitest.config.ts "g:/small-cosmos/losa/libs/tester/src/lib/server/register.test.ts" "-t" "Register" "--api.port" "57204" "--api.host" "127.0.0.1"
[INFO 2:35:05 PM] WS Close
can you make a little change to update the driver to be uppercase on windows? @falynx
I get this, look like pnpm and yarn not recognize, maybe because of this.
@falynx what is your environment?
I'm thinking of check if it's window we uppercase?
@falynx thank you, it work on the example repo, maybe it happen on my project config, I will try to figure out
I understand now, it must be happen because I'm using vitest 3x instead of 2x which have different path result which cause test fail
@falynx it simply not work with vite 3, I dont know why :(
the basic project not work sir, I think maybe it computer or something, I try to modify it but give up, I just run vitest manually
https://drive.google.com/file/d/1CkfnobWuEH4k8qTkm5ky7HbP-9RJu_Gn/view?usp=sharing
finaly, the nodejs 18.1 is the problem
|
gharchive/pull-request
| 2022-10-13T02:14:14 |
2025-04-01T04:36:14.794580
|
{
"authors": [
"falynx",
"hiepxanh",
"zxch3n"
],
"repo": "vitest-dev/vscode",
"url": "https://github.com/vitest-dev/vscode/pull/94",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
123897499
|
w2utils.formatters: Use strict equality operators
The value checks introduced in 61f073bd also hide cells which contain numeric zero because 0 == '' is evaluated to true in JavaScript. Use strict equality operators to avoid the problem.
Test case: http://jsfiddle.net/2ttLd18o/
Good catch
|
gharchive/pull-request
| 2015-12-25T21:00:46 |
2025-04-01T04:36:14.800145
|
{
"authors": [
"vitmalina",
"yaegashi"
],
"repo": "vitmalina/w2ui",
"url": "https://github.com/vitmalina/w2ui/pull/1132",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
2356806040
|
refactor: Remove xml renderer
This relates to #1071 and #1191.
XML is not gone, just the old implementation should be removed.
We can discuss about it.
In the viur-meeting on 2024-06-21, we decided to remove the current XML renderer implementation now, and revive it later in a new attempt related to #1071.
|
gharchive/pull-request
| 2024-06-17T09:05:04 |
2025-04-01T04:36:14.804972
|
{
"authors": [
"phorward"
],
"repo": "viur-framework/viur-core",
"url": "https://github.com/viur-framework/viur-core/pull/1192",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
793442277
|
Composite-Composer-MetaComposer
Some discussed changes to the vivarium class structure include:
Making a Composite object, which has processes and topology attributes. This would be a short-lived object, as its processes and topology would be passed into an experiment for execution. An advantage would be improved application of developer tools, and type checking. Also, it could have its own initial_state method and merge method.
With the above change, Composer would return Composites.
Experiment could also accept Composite, and call its processes and topology attributes.
A MetaComposer would be a composer of Composers. In its generate_processes and generate_topology it would call its component Composers and merge their generated Composites.
Composites could also have a print_topology() method that would let you more easily see each variable and how it is connected. This could be done like experiment.state.get_config()
|
gharchive/issue
| 2021-01-25T14:45:27 |
2025-04-01T04:36:14.808360
|
{
"authors": [
"eagmon"
],
"repo": "vivarium-collective/vivarium-core",
"url": "https://github.com/vivarium-collective/vivarium-core/issues/51",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
874657249
|
Delete fixed-left-right-layout
This is not used anywhere.
noo, please don't delete stories! :smile:
ok, I was wrong about not getting used - could you adapt the stories to add minimal styling directly there?
noo, please don't delete stories! 😄
ok, I was wrong about not getting used - could you adapt the stories to add minimal styling directly there?
@nsams stories are back 😄
|
gharchive/pull-request
| 2021-05-03T15:07:29 |
2025-04-01T04:36:14.812664
|
{
"authors": [
"jamesricky",
"nsams"
],
"repo": "vivid-planet/comet-admin",
"url": "https://github.com/vivid-planet/comet-admin/pull/368",
"license": "BSD-2-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1791517590
|
[POC] Open/Close Live Editor and LiveCodeBlock
depends on https://github.com/vivid-planet/comet-docs/pull/22
I tried two things:
Add an Open/Close button to the Live Editor
https://github.com/vivid-planet/comet-docs/assets/13380047/b321414f-694d-426a-a9fb-f4103a971ba8
I swizzled the @docusaurus/theme-live-codeblock theme and added the button and styling changes.
First, I tried attaching the button without swizzling using the CSS classes and vanilla JS. However, there were two problems:
the theme uses CSS modules, meaning there is a suffix attached to the class. I wasn't sure how stable the suffix is, so I didn't want to rely on that
I didn't know where to place the JS to attach the button so it affects all stories. Also, doing this with vanilla JS felt wrong
Add a LiveCodeBlock component to avoid duplication of the transform code
I tried if it's possible to extract the configured from mdx to a dedicated file. This could be our default since probably 99% of the time stories will be tsx and the transformCode will be necessary.
@johnnyomair Do you see any downsides to this? (as I'm sure you thought of that too)
:clap: great!
one minor thing: Can you rename "Live Editor" to "Code" and remove the "Result" line
With this in place we now should convert all docs!
@nsams 👍
I made these changes here: https://github.com/vivid-planet/comet/pull/1170
Moved to main repository: https://github.com/vivid-planet/comet/pull/1170
|
gharchive/pull-request
| 2023-07-06T13:00:28 |
2025-04-01T04:36:14.817694
|
{
"authors": [
"johnnyomair",
"nsams",
"thomasdax98"
],
"repo": "vivid-planet/comet-docs",
"url": "https://github.com/vivid-planet/comet-docs/pull/23",
"license": "BSD-2-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1584540006
|
Implement is_empty
Ok thats a small line of code but i think that should do it. I didn't found any tests so on your risk 😅
Also: from lines like https://github.com/vizia/vizia/blob/new-style-system/crates/vizia_style/selectors/matching.rs#L993 i think selectors like :first-child and :last-child should be also done but ill check on this again.
https://github.com/vizia/vizia/blob/new-style-system/crates/vizia_style/selectors/matching.rs#L800
Yes seems like after this PR all Tree-structural pseudo-classes will be done 🤩
I know there aren't any unit tests for these but did you test them in your own example? I'm curious if the Nth child ones just work as well.
I know there aren't any unit tests for these but did you test them in your own example? I'm curious if the Nth child ones just work as well.
So is_empty works! but the nth-child ones are messed up.. going to fix those
YES! everything works now 🥳🎉🪅
The problem with nth-child was just that i had the css on the parent (.parent:last-child) and not on the child (.subeles:last-child).
This is now ready to get merged and mark every Tree-structural pseudo-class as done :D
|
gharchive/pull-request
| 2023-02-14T17:14:42 |
2025-04-01T04:36:14.864108
|
{
"authors": [
"DasLixou",
"geom3trik"
],
"repo": "vizia/vizia",
"url": "https://github.com/vizia/vizia/pull/308",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2550067844
|
[Performance]: Extremely low throughput
Proposal to improve performance
Hi all, I just started a vLLM server instance as follows:
python3 -m vllm.entrypoints.openai.api_server --model meta-llama/Meta-Llama-3-8B-Instruct --enforce-eager --max-num-seqs 16
However, the throughput seems to be extremely low (0.8, 0.9 token/s):
INFO: 2.36.8.92:56164 - "POST /v1/chat/completions HTTP/1.1" 200 OK
INFO 09-26 11:35:23 engine.py:288] Added request chat-cc6296ad51b74d88bf17ba75459c06aa.
INFO 09-26 11:35:25 metrics.py:351] Avg prompt throughput: 2.3 tokens/s, Avg generation throughput: 0.2 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.1%, CPU KV cache usage: 0.0%.
INFO 09-26 11:35:31 metrics.py:351] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 0.8 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.2%, CPU KV cache usage: 0.0%.
INFO 09-26 11:35:37 metrics.py:351] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 0.8 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.2%, CPU KV cache usage: 0.0%.
INFO 09-26 11:35:43 metrics.py:351] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 0.8 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.2%, CPU KV cache usage: 0.0%.
INFO 09-26 11:35:49 metrics.py:351] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 0.8 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.3%, CPU KV cache usage: 0.0%.
INFO 09-26 11:35:55 metrics.py:351] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 0.8 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.3%, CPU KV cache usage: 0.0%.
INFO 09-26 11:36:01 metrics.py:351] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 0.8 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.3%, CPU KV cache usage: 0.0%.
INFO 09-26 11:36:08 metrics.py:351] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 0.8 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.5%, CPU KV cache usage: 0.0%.
INFO 09-26 11:36:14 metrics.py:351] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 0.8 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.5%, CPU KV cache usage: 0.0%.
INFO 09-26 11:36:20 metrics.py:351] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 0.8 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 09-26 11:36:20 logger.py:36] Received request chat-3a7f5f25941f491ebe029b3e6b9771b8: prompt: '<|begin_of_text|><|start_header_id|>user<|end_header_id|>\n\nHere is the query:\nHey how are you?\n\nCreate a concise, 3-5 word phrase with an emoji as a title for the previous query. Suitable Emojis for the summary can be used to enhance understanding but avoid quotation marks or special formatting. RESPOND ONLY WITH THE TITLE TEXT.\n\nExamples of titles:\n📉 Stock Market Trends\n🍪 Perfect Chocolate Chip Recipe\nEvolution of Music Streaming\nRemote Work Productivity Tips\nArtificial Intelligence in Healthcare\n🎮 Video Game Development Insights<|eot_id|><|start_header_id|>assistant<|end_header_id|>\n\n', params: SamplingParams(n=1, best_of=1, presence_penalty=0.0, frequency_penalty=0.0, repetition_penalty=1.0, temperature=0.7, top_p=1.0, top_k=-1, min_p=0.0, seed=None, use_beam_search=False, length_penalty=1.0, early_stopping=False, stop=[], stop_token_ids=[], include_stop_str_in_output=False, ignore_eos=False, max_tokens=50, min_tokens=0, logprobs=None, prompt_logprobs=None, skip_special_tokens=True, spaces_between_special_tokens=True, truncate_prompt_tokens=None), prompt_token_ids: [128000, 128006, 882, 128007, 271, 8586, 374, 279, 3319, 512, 19182, 1268, 527, 499, 1980, 4110, 264, 64694, 11, 220, 18, 12, 20, 3492, 17571, 449, 459, 43465, 439, 264, 2316, 369, 279, 3766, 3319, 13, 86346, 5867, 84528, 369, 279, 12399, 649, 387, 1511, 311, 18885, 8830, 719, 5766, 55331, 15785, 477, 3361, 37666, 13, 46577, 38539, 27785, 4874, 3247, 49673, 16139, 382, 41481, 315, 15671, 512, 9468, 241, 231, 12937, 8152, 50730, 198, 9468, 235, 103, 24118, 39520, 32013, 26371, 198, 35212, 3294, 315, 10948, 45910, 198, 25732, 5664, 5761, 1968, 26788, 198, 9470, 16895, 22107, 304, 39435, 198, 9468, 236, 106, 8519, 4140, 11050, 73137, 128009, 128006, 78191, 128007, 271], lora_request: None, prompt_adapter_request: None.
INFO 09-26 11:36:20 engine.py:288] Added request chat-3a7f5f25941f491ebe029b3e6b9771b8.
What could be the cause? The underlying GPU is a NVIDIA RTX 4000 -- I tried switching from bf16 to fp16 but the issue persists. Thanks!
Report of performance regression
No response
Misc discussion on performance
No response
Your current environment (if you think it is necessary)
Collecting environment information...
WARNING 09-26 11:41:07 _custom_ops.py:18] Failed to import from vllm._C with ModuleNotFoundError("No module named 'vllm._C'")
/home/pasquale/vllm/vllm/connections.py:8: RuntimeWarning: Failed to read commit hash:
No module named 'vllm._version'
from vllm.version import __version__ as VLLM_VERSION
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A
OS: Ubuntu 24.04.1 LTS (x86_64)
GCC version: (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.39
Python version: 3.12.4 | packaged by Anaconda, Inc. | (main, Jun 18 2024, 15:12:24) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-6.8.0-41-generic-x86_64-with-glibc2.39
Is CUDA available: True
CUDA runtime version: 12.0.140
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA RTX 4000 SFF Ada Generation
Nvidia driver version: 535.183.01
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 46 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 20
On-line CPU(s) list: 0-19
Vendor ID: GenuineIntel
Model name: 13th Gen Intel(R) Core(TM) i5-13500
CPU family: 6
Model: 191
Thread(s) per core: 2
Core(s) per socket: 14
Socket(s): 1
Stepping: 2
CPU(s) scaling MHz: 59%
CPU max MHz: 4800.0000
CPU min MHz: 800.0000
BogoMIPS: 4992.00
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect user_shstk avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi vnmi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities
Virtualization: VT-x
L1d cache: 544 KiB (14 instances)
L1i cache: 704 KiB (14 instances)
L2 cache: 11.5 MiB (8 instances)
L3 cache: 24 MiB (1 instance)
NUMA node(s): 1
NUMA node0 CPU(s): 0-19
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Not affected
Vulnerability Mds: Not affected
Vulnerability Meltdown: Not affected
Vulnerability Mmio stale data: Not affected
Vulnerability Reg file data sampling: Mitigation; Clear Register File
Vulnerability Retbleed: Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2: Mitigation; Enhanced / Automatic IBRS; IBPB conditional; RSB filling; PBRSB-eIBRS SW sequence; BHI BHI_DIS_S
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected
Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] nvidia-cublas-cu12==12.1.3.1
[pip3] nvidia-cuda-cupti-cu12==12.1.105
[pip3] nvidia-cuda-nvrtc-cu12==12.1.105
[pip3] nvidia-cuda-runtime-cu12==12.1.105
[pip3] nvidia-cudnn-cu12==9.1.0.70
[pip3] nvidia-cufft-cu12==11.0.2.54
[pip3] nvidia-curand-cu12==10.3.2.106
[pip3] nvidia-cusolver-cu12==11.4.5.107
[pip3] nvidia-cusparse-cu12==12.1.0.106
[pip3] nvidia-ml-py==12.560.30
[pip3] nvidia-nccl-cu12==2.20.5
[pip3] nvidia-nvjitlink-cu12==12.6.68
[pip3] nvidia-nvtx-cu12==12.1.105
[pip3] pyzmq==26.2.0
[pip3] torch==2.4.0
[pip3] torchvision==0.19.0
[pip3] transformers==4.45.0
[pip3] triton==3.0.0
[conda] numpy 1.26.4 pypi_0 pypi
[conda] nvidia-cublas-cu12 12.1.3.1 pypi_0 pypi
[conda] nvidia-cuda-cupti-cu12 12.1.105 pypi_0 pypi
[conda] nvidia-cuda-nvrtc-cu12 12.1.105 pypi_0 pypi
[conda] nvidia-cuda-runtime-cu12 12.1.105 pypi_0 pypi
[conda] nvidia-cudnn-cu12 9.1.0.70 pypi_0 pypi
[conda] nvidia-cufft-cu12 11.0.2.54 pypi_0 pypi
[conda] nvidia-curand-cu12 10.3.2.106 pypi_0 pypi
[conda] nvidia-cusolver-cu12 11.4.5.107 pypi_0 pypi
[conda] nvidia-cusparse-cu12 12.1.0.106 pypi_0 pypi
[conda] nvidia-ml-py 12.560.30 pypi_0 pypi
[conda] nvidia-nccl-cu12 2.20.5 pypi_0 pypi
[conda] nvidia-nvjitlink-cu12 12.6.68 pypi_0 pypi
[conda] nvidia-nvtx-cu12 12.1.105 pypi_0 pypi
[conda] pyzmq 26.2.0 pypi_0 pypi
[conda] torch 2.4.0 pypi_0 pypi
[conda] torchvision 0.19.0 pypi_0 pypi
[conda] transformers 4.45.0 pypi_0 pypi
[conda] triton 3.0.0 pypi_0 pypi
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: N/A
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0 CPU Affinity NUMA Affinity GPU NUMA ID
GPU0 X 0-19 0 N/A
Legend:
X = Self
SYS = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
PHB = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
PXB = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
PIX = Connection traversing at most a single PCIe bridge
NV# = Connection traversing a bonded set of # NVLinks
Before submitting a new issue...
[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.
It was a GPU issue :) from nvidia-smi -q:
GPU Reset Status
Reset Required : Yes
Drain and Reset Recommended : No
Now it's up to 20 tokens/s!
|
gharchive/issue
| 2024-09-26T09:40:29 |
2025-04-01T04:36:14.937506
|
{
"authors": [
"pminervini"
],
"repo": "vllm-project/vllm",
"url": "https://github.com/vllm-project/vllm/issues/8847",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
40471792
|
Is markdown table must have header to rendering right
before i use MultiMarkdown to parse below table :
| ------------- | ------------- |
| Content Cell | Content Cell |
| Content Cell | Content Cell |
it's correct, but with Redcarpet didn't, i must add headers to make it right :
| First Header | Second Header |
| ------------- | ------------- |
| Content Cell | Content Cell |
| Content Cell | Content Cell |
the problem is something i needn't table headers, it's trouble to make page always show some empty rows on table top, any way can avoid that?
We're having this problem too. Is this by design, or could we change it?
I'm having this issue too - the README says tables can be read in PHP Markdown Extra if desired, and yet single line tables such as
| foo | bar |
Are not being rendered as tables.
This is pretty much a gating issue for Redmine users transitioning from Textile to Markdown.
|
gharchive/issue
| 2014-08-18T09:59:58 |
2025-04-01T04:36:14.946462
|
{
"authors": [
"farkwun",
"go2null",
"mwean",
"vince-styling"
],
"repo": "vmg/redcarpet",
"url": "https://github.com/vmg/redcarpet/issues/411",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
689398659
|
Fix strongSwan logging configuration
strongSwan logging configuration is reported as invalid in some OSes
(e.g Ubuntu 16.04) when starting the strongSwan services. It is probably
due to the strongSwan version change after the Antea Docker image is
updated to use Ubuntu 20.04. This commit fixes the strongSwan logging
configuration.
Codecov Report
Merging #1184 into master will decrease coverage by 14.65%.
The diff coverage is n/a.
@@ Coverage Diff @@
## master #1184 +/- ##
===========================================
- Coverage 56.10% 41.44% -14.66%
===========================================
Files 106 74 -32
Lines 11535 10507 -1028
===========================================
- Hits 6472 4355 -2117
- Misses 4496 5798 +1302
+ Partials 567 354 -213
Flag
Coverage Δ
#integration-tests
?
#unit-tests
41.44% <ø> (-0.09%)
:arrow_down:
Flags with carried forward coverage won't be shown. Click here to find out more.
Impacted Files
Coverage Δ
pkg/ovs/openflow/default.go
0.00% <0.00%> (-100.00%)
:arrow_down:
pkg/agent/config/node_config.go
0.00% <0.00%> (-100.00%)
:arrow_down:
pkg/ovs/openflow/logs.go
12.50% <0.00%> (-87.50%)
:arrow_down:
pkg/ovs/openflow/ofctrl_group.go
0.00% <0.00%> (-76.09%)
:arrow_down:
pkg/ovs/openflow/ofctrl_bridge.go
2.34% <0.00%> (-69.24%)
:arrow_down:
pkg/ovs/ovsconfig/ovs_client.go
0.00% <0.00%> (-65.27%)
:arrow_down:
pkg/ovs/openflow/ofctrl_action.go
16.99% <0.00%> (-65.22%)
:arrow_down:
pkg/ovs/openflow/ofctrl_builder.go
16.53% <0.00%> (-55.77%)
:arrow_down:
pkg/ovs/openflow/ofctrl_packetout.go
0.00% <0.00%> (-42.86%)
:arrow_down:
pkg/agent/openflow/pipeline.go
20.90% <0.00%> (-35.89%)
:arrow_down:
... and 48 more
works
I think it is not about Antrea release, but strongSwan version used in our image, depended on the Ubuntu version.
works
I think it is not about Antrea release, but strongSwan version used in our image, depended on the Ubuntu version.
sorry i meant earlier ubuntu release.. 16.04 :D
Should only depend on the Ubuntu version we use to build the Antrea Docker image. But the person who reported the issue mentioned it only happened for certain Node configurations...
Should only depend on the Ubuntu version we use to build the Antrea Docker image. But the person who reported the issue mentioned it only happened for certain Node configurations...
Right. But I do not understand why our CI e2e tests passed with no failure. Do you have an idea?
Should only depend on the Ubuntu version we use to build the Antrea Docker image. But the person who reported the issue mentioned it only happened for certain Node configurations...
Right. But I do not understand why our CI e2e tests passed with no failure. Do you have an idea?
Ok I guess might be the IPsec services failed to start, but traffic goes through without IPsec. Let me think about how to check this.
We know that IPsec coverage is broken: https://github.com/vmware-tanzu/antrea/issues/1043. The ovs-monitor-ipsec daemon was actually not starting correctly for a very long time (2 releases), and this did not get caught by the e2e tests. My guess is that the tests do not detect that the Agents do not get started properly after updating the manifest to enable IPsec. The issue is still open and assigned to @lzhecheng because we need to fix the tests. @lzhecheng, do you have cycles to work on it this week? If not, we can re-assign.
@jianjuns My guess is this needs to be changed: https://github.com/vmware-tanzu/antrea/blob/88a8df32b482ae27252bdee3a1496a34cbcf5b0d/test/e2e/connectivity_test.go#L211-L214. I think it returns immediately because it thinks all Pods are ready, but it must be looking at pre-update Pods, and it does not realize the new Pods are crashing.
You mean to check IPsec started correctly or not, or a better solution for Python3? I can look at the former.
/skip-all
We need a generic solution to make sure that the Antrea Agent Pods run correctly after the update to enable IPsec. Currently we do:
apply new YAML
run kubectl rollout status -w
make sure we have the correct number of Pods available
Apparently this is not enough to detect this case where the Pod crashes after a few seconds, so we need to improve it. We don't use the MinReadySeconds field in the DaemonSet spec, so we have to come up with something else.
Seems to me we can either check the container status, or run IPsec command inside the antrea-ipsec container.
I think the solution does not have to be tied to IPsec (or should not). So yes, maybe the solution is to spin for a couple seconds and make sure the Pods stay ready.
@jianjuns , I found this issue yesterday as well. I changed /var/log/strongswan/charon.log to charon without the path field you just added. It still failed and said /etc/strongswan.d/ovs.conf containes unexpected .. I am not sure if this solution solves this as well?
@antoninbas , I have some ipv6 e2e test failure to solve. It is great if you can help on it. Thank you!
I noticed that after antrea-ipsec.yml is applied, antrea-agent pods will repeatly switch between crash and running. Finally it turns crash. I am not sure if wait for just a few seconds will work? Maybe after the check, it turns crash again?
@lzhecheng : this PR is to fix the ovs.conf error: https://github.com/vmware-tanzu/antrea/pull/1191
|
gharchive/pull-request
| 2020-08-31T18:17:14 |
2025-04-01T04:36:14.971958
|
{
"authors": [
"abhiraut",
"antoninbas",
"codecov-commenter",
"jianjuns",
"lzhecheng"
],
"repo": "vmware-tanzu/antrea",
"url": "https://github.com/vmware-tanzu/antrea/pull/1184",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
749478163
|
[Flow Exporter] Improve e2e tests
fixes #1438
Codecov Report
Merging #1595 (69dc595) into master (9d3d10b) will decrease coverage by 6.11%.
The diff coverage is 31.58%.
@@ Coverage Diff @@
## master #1595 +/- ##
==========================================
- Coverage 63.31% 57.20% -6.12%
==========================================
Files 170 181 +11
Lines 14250 15308 +1058
==========================================
- Hits 9023 8757 -266
- Misses 4292 5583 +1291
- Partials 935 968 +33
Flag
Coverage Δ
kind-e2e-tests
44.23% <28.41%> (-11.15%)
:arrow_down:
unit-tests
40.38% <13.28%> (-0.90%)
:arrow_down:
Flags with carried forward coverage won't be shown. Click here to find out more.
Impacted Files
Coverage Δ
cmd/antrea-agent/agent.go
0.00% <0.00%> (ø)
cmd/antrea-agent/options.go
21.69% <0.00%> (+0.97%)
:arrow_up:
...gent/controller/noderoute/node_route_controller.go
46.06% <ø> (-0.41%)
:arrow_down:
.../agent/flowexporter/connections/conntrack_linux.go
28.37% <0.00%> (-0.79%)
:arrow_down:
pkg/agent/stats/collector.go
97.72% <ø> (ø)
pkg/apiserver/apiserver.go
73.95% <0.00%> (-12.07%)
:arrow_down:
pkg/apiserver/certificate/cacert_controller.go
38.73% <0.00%> (-17.65%)
:arrow_down:
pkg/apiserver/handlers/webhook/mutation_crd.go
0.00% <0.00%> (ø)
pkg/controller/networkpolicy/mutate.go
0.00% <0.00%> (ø)
pkg/controller/networkpolicy/tier.go
0.00% <ø> (-90.00%)
:arrow_down:
... and 78 more
Is there any benefit in adding TestFlowExporterWithRemoteServiceAccess with inter-node flows?
Currently it works similarly for local service(pod) and remote service(pod). Actually we cannot deploy the service to a specific node, right?
As the conntrack flows look different, if the endpoint (mapped pod) is on the same node or on a different node, IMO it is better to have separate tests. Currently, we ignore the flow record from the destination node in the case where the endpoint is on a different node, so the flow records for both cases look similar except for destination pod info. This behavior will change with flow aggregator implementation and the checks in e2e tests will be different.
AntreaProxy can select an endpoint/pod on a specific node based on sessionAffinity setting in the K8s service.
Got it. Added tests for remote service access. Thanks for clarification.
/testall
/test-all
/test-all
/test-e2e
/test-all-features-conformance
/test-all
/test-e2e
/test-conformance
/test-networkpolicy
/test-e2e
/test-e2e
/test-all
/test-all
/test-networkpolicy
|
gharchive/pull-request
| 2020-11-24T08:08:23 |
2025-04-01T04:36:14.990167
|
{
"authors": [
"codecov-io",
"srikartati",
"zyiou"
],
"repo": "vmware-tanzu/antrea",
"url": "https://github.com/vmware-tanzu/antrea/pull/1595",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1114190727
|
OpenSSF badge requirements: Code Analysis
Description of problem
The OpenSSF (formerly known as CII) Best Practices badge includes a section on Analysis with several requirements as described here:
https://bestpractices.coreinfrastructure.org/en/projects/5329#analysis
Proposed solution
Please review the requirements and respond this issue mentioning which ones the project already meets so the unmet ones can be tracked in separate issues.
As a reminder, achieving passing grade in the OpenSSF Best Practices is a minimum baseline of best practices considered by Linux Foundation for healthy open source projects.
Already met, see https://bestpractices.coreinfrastructure.org/en/projects/5329#analysis
|
gharchive/issue
| 2022-01-25T17:49:48 |
2025-04-01T04:36:14.992878
|
{
"authors": [
"davidmirror-ops"
],
"repo": "vmware-tanzu/cartographer",
"url": "https://github.com/vmware-tanzu/cartographer/issues/552",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1236304570
|
The latest version of TCE fails in installation of Windows, Mac and Ubuntu with Docker.
Bug Report
I tried to install the latest version of TCE in Windows, Mac and Ubuntu by following the official documentation. All fails!
Expected Behavior
Steps to Reproduce the Bug
Just follow the official documentation with Docker as deployment target.
Screenshots or additional information and context
Environment Details
Build version (tanzu version): v0.11.2
Deployment (Managed/Unmanaged cluster): Managed
Infrastructure Provider (Docker/AWS/Azure/vSphere): Docker
Operating System (client): Windows, Mac and Ubuntu
Diagnostics and log bundle
I need to downgrade to v0.9.2 and using the manual command "tanzu management-cluster create -i docker --name mtce -v 10 --plan dev --ceip-participation=false" to setup management cluster.
Detail (All cases are using Docker):
Linux - failed after "Starting control-plane", error is "Exit 1"
Mac - failed in "waiting for cert-manager to be available"
Windows - failed
I know TCE for Docker is experiment only but one of TCE purpose is facilitating Developer by leveraging local workstation. Hope it will be fixed soon. Thank you!
I spent my weekend in getting above result! :)
This is known to work successfully on all platforms, so there must be something in your environment causing problems. Maybe a proxy or firewall interfering with network connectivity?
I would recommend going through the bootstrap troubleshooting steps to see what errors the looks contain: https://tanzucommunityedition.io/docs/v0.12/ts-manually/
You may also want to just use unmanaged clusters for local workstation development as there are a lot less resource requirements.
This is known to work successfully on all platforms, so there must be something in your environment causing problems. Maybe a proxy or firewall interfering with network connectivity?
I would recommend going through the bootstrap troubleshooting steps to see what errors the looks contain: https://tanzucommunityedition.io/docs/v0.12/ts-manually/
You may also want to just use unmanaged clusters for local workstation development as there are a lot less resource requirements.
I am using home broadband which is simple and does not have any firewall or proxy. I can install unmanaged cluster successfully, very smooth. Only management-cluster fails in Windows, Mac and Linux(Ubuntu). In my case, I am using Docker which is experiment for TCE (TCE supports Docker in experimental way).
Hope TCE can support Docker and provide a smooth installation experience, like UiPath Community Edition (In the past), it can attract a lot of developers and promote this product.
Looking forward to see a new TCE soon!
Thank you!
Hey @vincentvc168 - we have some newer releases since this was opened. Could you try with the v0.12.1 release?
Also, are you running these different platforms under virtualization like Fusion or Workstation?
|
gharchive/issue
| 2022-05-15T14:31:05 |
2025-04-01T04:36:15.001021
|
{
"authors": [
"dvonthenen",
"stmcginnis",
"vincentvc168"
],
"repo": "vmware-tanzu/community-edition",
"url": "https://github.com/vmware-tanzu/community-edition/issues/4535",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1599255777
|
[release-1.9] Upgrade to latest dependencies
bumping pkg -dprotaso
/cc we don't use Prow
/assign we don't use Prow
Produced by: knative-sandbox/knobots/actions/update-deps
Codecov Report
Merging #512 (d0e6338) into release-1.9 (cd1012f) will not change coverage.
The diff coverage is n/a.
@@ Coverage Diff @@
## release-1.9 #512 +/- ##
============================================
Coverage 66.23% 66.23%
============================================
Files 38 38
Lines 2079 2079
============================================
Hits 1377 1377
Misses 657 657
Partials 45 45
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.
|
gharchive/pull-request
| 2023-02-24T20:44:34 |
2025-04-01T04:36:15.005122
|
{
"authors": [
"codecov-commenter",
"knative-automation"
],
"repo": "vmware-tanzu/sources-for-knative",
"url": "https://github.com/vmware-tanzu/sources-for-knative/pull/512",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
235382961
|
[E2E] automated e2e tests should fail gracefully when test bed setup is not ideal or some environment vars are not set
With the swarm test automation and govc integration, there are bunch of env variables need to be set inorder to execute tests locally. In an absence of ideal testbed or env. vars, tests are failing with out giving proper error message. It creates lot of confusion to the user and ends up spending more time.
This issue is to streamline the failure and provides meaningful information to user when run into test setup issues.
remove unnecessary environment variables from contributing.md too.
/CC @msterin
Here's my suggestion (copied from #1517 )
Verify the required environment variables are properly initialized before running e2e test
Clean up the Config DB if it already exists before running each test group
Maybe more...
@ashahi1 is already having partial fix so bringing back to his plate
Fixed as part of PR #1530
|
gharchive/issue
| 2017-06-12T22:21:56 |
2025-04-01T04:36:15.035240
|
{
"authors": [
"ashahi1",
"shaominchen",
"shuklanirdesh82"
],
"repo": "vmware/docker-volume-vsphere",
"url": "https://github.com/vmware/docker-volume-vsphere/issues/1398",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
162595209
|
[Issue] Harbor Database Migration Document Have a Error
on step 2: build image from dockerfile
cd harbor-migration
docker build -t migrate-tool
console:
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat .../harbor/migration/migration_harbor/Dockerfile: no such file or directory
.
@yhua123 thanks I will remove the step "cd harbor-migration"
verified
|
gharchive/issue
| 2016-06-28T03:31:58 |
2025-04-01T04:36:15.041284
|
{
"authors": [
"reasonerjt",
"yhua123"
],
"repo": "vmware/harbor",
"url": "https://github.com/vmware/harbor/issues/429",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
462034494
|
/usr/bin/python3: No module named tern error in vagrant running in windows 10 Personal computer
No module named tern
The documentation is insufficient
I used vagrant up with tern project in my local drive
To Reproduce
Steps to reproduce the behavior:
I followed the vagrant procedure as mentioned in the https://github.com/vmware/tern/blob/master/README.md#getting-started-with-vagrant
when I run the "python -m tern -l report -i debian:buster -f output.txt" command
Python command doesn't exist came
So I altered the command to python3 in step 2 and ran "python3 -m tern -l report -i debian:buster -f output.txt" command
threw below error
Error in terminal
/usr/bin/python3: No module named tern
Expected behavior
I was expecting the BOM report
Environment you are running Tern on
Enter all that apply
Operating System is Windows 10
Vagrant file https://github.com/vmware/tern/blob/master/vagrant/Vagrantfile
Python version (3.6 or higher)- 3.6.8
Hi @dineshr93, thanks for filing this issue.
Please try to cd into the tern directory on the vagrant VM before you run the command in question. You are correct that you will likely need to use python3 for the command and this should be updated in the documentation.
When I replicate the steps you mentioned and cd into the tern directory on the created VM, Tern runs without issue. If I run the command outside of the tern directory I can see the same error message as you are seeing. Here's what I did:
<Install VirtualBox>
<Install Vagrant>
$ git clone https://github.com/vmware/tern.git
$ cd tern/vagrant
$ vagrant up
$ vagrant ssh
$ cd tern
$ python3 -m tern -l report -i debian:buster -f output.txt
2019-06-28 20:05:42,842 - DEBUG - __main__ - Starting...
2019-06-28 20:05:42,842 - DEBUG - report - Setting up...
2019-06-28 20:05:43,861 - DEBUG - container - Checking if image "debian:buster" is available on disk...
2019-06-28 20:05:44,945 - DEBUG - container - Image "debian:buster" found
2019-06-28 20:05:48,963 - DEBUG - rootfs - Running command: sudo /home/vagrant/tern/tern/tools/fs_hash.sh /home/vagrant/tern/temp/0f28619fe69181d3af529d56692f1362b7a7c8a6bf8dc9ab0d6d4f9ef9b0004d/contents
2019-06-28 20:05:56,334 - DEBUG - rootfs - Running command: sudo mount -o bind temp/0f28619fe69181d3af529d56692f1362b7a7c8a6bf8dc9ab0d6d4f9ef9b0004d/contents temp/mergedir
2019-06-28 20:05:56,342 - DEBUG - common - Loaded from cache: layer "06fbb6a15a"
2019-06-28 20:05:56,345 - DEBUG - rootfs - Running command: sudo umount -rl temp/mergedir
2019-06-28 20:05:56,391 - DEBUG - report - Creating a detailed report of components in image...
2019-06-28 20:05:56,400 - DEBUG - rootfs - Running command: sudo rm -rf temp/0f28619fe69181d3af529d56692f1362b7a7c8a6bf8dc9ab0d6d4f9ef9b0004d/contents
2019-06-28 20:05:56,496 - DEBUG - report - Teardown...
2019-06-28 20:05:57,240 - DEBUG - rootfs - Running command: sudo rm -rf temp/mergedir
2019-06-28 20:05:57,248 - DEBUG - rootfs - Running command: sudo rm -rf temp/workdir
2019-06-28 20:05:57,271 - DEBUG - __main__ - Report completed.
2019-06-28 20:05:57,271 - DEBUG - __main__ - Finished
If I try to run the command outside of the tern directory I see:
[vagrant@ubuntu-bionic:~$ pwd
/home/vagrant
vagrant@ubuntu-bionic:~$ python3 -m tern -l report -i debian:buster -f output.txt
/usr/bin/python3: No module named tern.__main__; 'tern' is a package and cannot be directly executed
Can you give this a try and let me if it helps?
|
gharchive/issue
| 2019-06-28T13:26:32 |
2025-04-01T04:36:15.052369
|
{
"authors": [
"dineshr93",
"rnjudge"
],
"repo": "vmware/tern",
"url": "https://github.com/vmware/tern/issues/353",
"license": "BSD-2-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
454049968
|
Entering git repo throws "Cannot find gitstatus.sh"
Not sure what this is. Had this error once before, couldn't find the culprit and had to do clean install. Now after a few days of using the dotfiles again seeing this error.
Re-running bootstrap.sh did not help. The file is clearly present in the /bin folder, however still getting this error.
Oh, and thanks for these awesome dotfiles!
Upd: I've noticed my shell got switched back to bash instead of zsh. Switching to zsh made the issue disappear. But should this work under bash shell as well?
can you please run echo $PATH in the bash and post the result here, thanks. The file should be in the ~/bin/ directory not in /bin/.
Here's the difference between path variables in zsh and bash:
✓ ~→ bash
✓ ~→ echo $PATH
/usr/local/bin:/usr/sbin:/sbin:/usr/local/sbin:/home/sergio/bin:/usr/local/bin:/usr/sbin:/sbin:/usr/local/sbin:/home/sergio/bin:/usr/local/bin:/usr/sbin:/sbin:/usr/local/sbin:/home/sergio/bin:/usr/local/bin:/usr/sbin:/sbin:/usr/local/sbin:/home/sergio/bin:/home/sergio/.local/bin:/home/sergio/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/sergio/.local/bin:/home/sergio/.local/bin:/home/sergio/.local/bin:/home/sergio/.local/bin
✓ ~→ zsh
✓ ~→ echo $PATH
/usr/local/bin:/usr/sbin:/sbin:/usr/local/sbin:/home/sergio/bin:/usr/local/bin:/usr/sbin:/sbin:/usr/local/sbin:/home/sergio/bin:/usr/local/bin:/usr/sbin:/sbin:/usr/local/sbin:/home/sergio/bin:/usr/local/bin:/usr/sbin:/sbin:/usr/local/sbin:/home/sergio/bin:/usr/local/bin:/usr/sbin:/sbin:/usr/local/sbin:/home/sergio/bin:/home/sergio/.local/bin:/home/sergio/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/sergio/.local/bin:/home/sergio/.local/bin:/home/sergio/.local/bin:/home/sergio/.local/bin:/home/sergio/.local/bin
The file was present in the ~/bin directory, I checked that. Also it was on the path because I could just call $ gitstatus.sh from anywhere.
✓ ~→ cd dotfiles
✓ ~/dotfiles→ bash # switching to bash in a repo, and getting the error message right away
Cannot find gitstatus.sh!
Cannot find gitstatus.sh!
sergio@milleniumfalcon:~/dotfiles$ gitstatus # can still see the script on the path with autocomplete and execute it
gitstatus_pre-1.7.10.sh gitstatus.py gitstatus.sh
sergio@milleniumfalcon:~/dotfiles$ zsh # changing back to zsh - no error
any news here? found the same issue running this on WSL
here is my $PATH after running bootstrap.sh
/usr/local/bin:/usr/sbin:/sbin:/usr/local/sbin:/home/gersondias/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/mnt/c/ProgramData/DockerDesktop/version-bin:/mnt/c/Program Files/Docker/Docker/Resources/bin:/mnt/c/Python37/Scripts/:/mnt/c/Python37/:/mnt/c/Program Files (x86)/Microsoft SDKs/Azure/CLI2/wbin:/mnt/c/Program Files (x86)/Intel/iCLS Client/:/mnt/c/Program Files/Intel/iCLS Client/:/mnt/c/WINDOWS/system32:/mnt/c/WINDOWS:/mnt/c/WINDOWS/System32/Wbem:/mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/:/mnt/c/WINDOWS/System32/OpenSSH/:/mnt/c/Program Files/Microsoft VS Code/bin:/mnt/c/Program Files/dotnet/:/mnt/c/Program Files/Microsoft SQL Server/130/Tools/Binn/:/mnt/c/Program Files/Microsoft SQL Server/Client SDK/ODBC/170/Tools/Binn/:/mnt/c/ProgramData/chocolatey/bin:/mnt/c/Program Files/PowerShell/6/:/mnt/c/Program Files/Git/cmd:/mnt/c/Program Files (x86)/vim/vim80:/mnt/c/Program Files/nodejs/:/mnt/c/Program Files (x86)/Microsoft Visual Studio/2019/Enterprise/MSBuild/Current/Bin:/mnt/c/Program Files (x86)/Microsoft Visual Studio/2019/Enterprise/Common7/ide/Extensions/TestPlatform:/mnt/c/Users/GersonDias/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/GersonDias/AppData/Roaming/npm:/mnt/c/tools/Cmder:/mnt/c/Users/GersonDias/.dotnet/tools:/snap/bin
I personally didn't look into it yet, though I have a feeling that it has to do with .redpill files, specifically the bash setup. But I don't have much time ATM to debug this, and I also use zsh, so I don't encounter this issue unless I explicitly switch back to bash shell.
Hey, I found the same issue running that on WSL
here is my $PATH after running bootstrap.sh
/usr/local/bin:/usr/sbin:/sbin:/usr/local/sbin:/home/gersondias/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/mnt/c/ProgramData/DockerDesktop/version-bin:/mnt/c/Program Files/Docker/Docker/Resources/bin:/mnt/c/Python37/Scripts/:/mnt/c/Python37/:/mnt/c/Program Files (x86)/Microsoft SDKs/Azure/CLI2/wbin:/mnt/c/Program Files (x86)/Intel/iCLS Client/:/mnt/c/Program Files/Intel/iCLS Client/:/mnt/c/WINDOWS/system32:/mnt/c/WINDOWS:/mnt/c/WINDOWS/System32/Wbem:/mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/:/mnt/c/WINDOWS/System32/OpenSSH/:/mnt/c/Program Files/Microsoft VS Code/bin:/mnt/c/Program Files/dotnet/:/mnt/c/Program Files/Microsoft SQL Server/130/Tools/Binn/:/mnt/c/Program Files/Microsoft SQL Server/Client SDK/ODBC/170/Tools/Binn/:/mnt/c/ProgramData/chocolatey/bin:/mnt/c/Program Files/PowerShell/6/:/mnt/c/Program Files/Git/cmd:/mnt/c/Program Files (x86)/vim/vim80:/mnt/c/Program Files/nodejs/:/mnt/c/Program Files (x86)/Microsoft Visual Studio/2019/Enterprise/MSBuild/Current/Bin:/mnt/c/Program Files (x86)/Microsoft Visual Studio/2019/Enterprise/Common7/ide/Extensions/TestPlatform:/mnt/c/Users/GersonDias/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/GersonDias/AppData/Roaming/npm:/mnt/c/tools/Cmder:/mnt/c/Users/GersonDias/.dotnet/tools:/snap/bin
I have the same issue on WSL. Have you found any solutions @GersonDias ?
On wsl, I managed to prevent throwing "Cannot find gitstatus.sh" by executing zsh on your bash shell. by default, wsl runs bash shell. try also running chsh -s $(which zsh) to change your shell default.
I fixed this issue by copying bin/gitstatush.sh into .redpill/bash_prompt/. The problem is fairly obvious when you look at the code starting at line 9 in gitprompt.sh:
function git_prompt_dir() {
# assume the gitstatus.sh is in the same directory as this script
# code thanks to http://stackoverflow.com/questions/59895
if [ -z "$__GIT_PROMPT_DIR_BASH" ]; then
local SOURCE="${BASH_SOURCE[0]}"
while [ -h "$SOURCE" ]; do
local DIR="$( cd -P "$( dirname "$SOURCE" )" && pwd )"
SOURCE="$(readlink "$SOURCE")"
[[ $SOURCE != /* ]] && SOURCE="$DIR/$SOURCE"
done
__GIT_PROMPT_DIR_BASH="$( cd -P "$( dirname "$SOURCE" )" && pwd )"
fi
}
The comment says it all. The code assumes that gitstatus.sh is in the same directory with gitprompt.sh
|
gharchive/issue
| 2019-06-10T08:13:49 |
2025-04-01T04:36:15.110517
|
{
"authors": [
"GersonDias",
"raelik",
"roaldjap",
"serpro69",
"voku"
],
"repo": "voku/dotfiles",
"url": "https://github.com/voku/dotfiles/issues/38",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.