[Bug]: Behaves differently locally than in a github-action

Minimal, reproducible example
Repo: https://github.com/ThibaultJanBeyer/DragSelect/tree/refactor/turborepo/DragSelect
I.e. failing remotely: https://github.com/ThibaultJanBeyer/DragSelect/actions/runs/6278010709/job/17050896924?pr=186

Error string
Various expects will have different results
Bug behavior

[X] Flaky
[ ] PDF

Background
I’m using puppeteer heavily for functional testing of my selection, drag and drop library, however, unfortunately, when I run my tests locally (i.e. moving mouse to coordinates X,Y and then pressing down and then moving to X+10,Y+20 and then releasing and then getting the selected values) behave differently (will output different elements between the coordinates) than within a github action.
Expectation
It should be exactly the same no matter which environment it is run on
Reality
In reality it is not
Puppeteer configuration file (if used)
launch: {
    args: ['--no-sandbox', '--disable-setuid-sandbox'],
    timeout: 30000,
    headless: true,
    dumpio: true, // Whether to pipe the browser process stdout and stderr
  },

Puppeteer version
21.3.3
Node version
20.3.1
Package manager
pnpm
Package manager version
8.7.6
Operating system
macOS

Are you adjusting your tests for the device pixel ratio?

If you could extra a minimal example from your code that demonstrates the issue, it'd be really helpful.

Thanks @OrKoN for the quick feedback!
Okay I’ll try adjusting the device pixel ratio (do you have a link on the docs here by any chance?)
And I’ll try to extract a minimal example to demonstrate the issue

While trying to create a minimal reproducible example I found another unrelated bug: https://github.com/puppeteer/puppeteer/issues/11014
Will continue trying…

Okay, I solved the other bugs which were not necessarily bugs but rather how the puppeteer works. So just https://github.com/puppeteer/puppeteer/issues/11014 seems like a real one. Going to close this issue thread now. Thank you!


CASMTRIAGE-6687: increase timeout for charts using etcd

Summary and Scope
Some charts using etcd cluster take more than 5 minutes (the default timeout setting) for deployment during the install or upgrade. This PR increases the timeout setting for those charts to 10 minutes.
Issues and Related PRs

Resolves CASMTRIAGE-6687
Change will also be needed in release/1.6

Testing
List the environments in which these changes were tested.
Tested on:

slice

Test description:
How were the changes tested and success verified? If schema changes were part of this change, how were those handled in your upgrade/downgrade testing?

Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?
Were continuous integration tests run? If not, why?
Was upgrade tested? If not, why?
Was downgrade tested? If not, why?
Were new tests (or test issues/Jiras) created for this change?

Risks and Mitigations
Low.
Pull Request Checklist

[ ] Version number(s) incremented, if applicable
[ ] Copyrights updated
[x] License file intact
[x] Target branch correct
[x] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

/backport release/1.6


Port old fuzzing code to Go's new fuzzing tools

As introduced by Go 1.18
See: https://go.dev/security/fuzz/

Hi, I am new to this project. May I have a try on this? @stv0g

Yes definitely! Just let me know if I can guide you or you need some other support.

Yes definitely! Just let me know if I can guide you or you need some other support.

Thanks! Actually I do have several questions：

I found that some of inputs generated by go-fuzzing did make sdp Unmarshaling crash which is because that the 'func (l *baseLexer) readField()' function may return empty string with a nil error.  I believe it is a bug here so am I supposed to fix it in the same PR? or I should make it a new issue?
Does it also need fuzzing test for sdp marshaling? If it is needed, there are so many fields in the sdp which makes the fuzzing test needs many arguments. I couldn't find a proper way to implement it.

I would do it in the same PR. Ideally in a separate commit.
And I think fuzzing is only really useful to test against maliciously crafted input data. Like SDPs received over the network.
So whenever we must process some external data..


Generate a work report

Worktime displays time spent per tag. Would it be possible to generate a report based on a date range?
I want to look at how much time was spent per task for all tasks in the current week.

This feature was present in Unfog predecessor. I plan to re-implement it with very soon, see this issue for the progression.

The worktime date range has been introduced in the last release. I would love to get your feedback :)

The worktime date range has been added in the last release. I would love your feedback :)

Worktime date range and due time added in v0.3.0 :tada:

Side note: I'm running zsh, therefore I have to escape the brackets.
Thanks for the quick update, but this isn't exactly what I requested.
Right now I'd have to run  unfog worktime +task1 and repeat for each task I've done in current week to determine time spent per task as there is no way for me to check the time spent on each tasks I've done in a week.
This just gives me an overview:
unfog: wtime global

DATE       |WORKTIME
2020-01-06 |1 min 21s 672ms
TOTAL      |1 min 21s 672ms```

What I'd like is to be able to fill a workcard like this:
![image](https://user-images.githubusercontent.com/8069846/71816464-93152000-307a-11ea-87eb-4e8d9bfe033a.png)

So something like this would work for me:
```unfog worktime \[060120 \]100120
unfog: wtime global

ID | CONTEXT    | DATE            |WORKTIME
1  | task1 task2  | 2020-01-06 |1 min 21s 672ms
2  | task2            | 2020-01-06 |1 min 21s 672ms
TOTAL                                      |1 min 21s 672ms```

What I can do is to add a column WORKTIME at the end of the list table (after DUE)? This way you have access to the worktime per task.

What I can do is to add a column WORKTIME at the end of the list table (after DUE)? This way you have access to the worktime per task.

This is a good solution but list doesn't currently allow filtering with range. If you also add that then I'd satisfied.

Sounds good to me. Adding the WORKTIME column and the filtering system. I will let you know :)

I tried with zsh, I don't have the problem of [. It could be related to plugins?

I tried with zsh, I don't have the problem of [. It could be related to plugins?

Hmm, I think maybe oh-my-zsh enables filename generation

I will keep [ and ] and wait for other feedbacks. About the worktime, I decided to change the worktime command itself. It looks like this:

I will deploy the next release soon. Does it fit your needs?

Yeah that works great!

This report is now accessible with the --more option. By default (without this option), it shows the compact version of worktime. See https://github.com/unfog-io/unfog-cli#more.


Instruction data tables

Hey there,
I'm one of the Zydis (a x86-64 disassembler written in C) devs. I noticed you reported some definition bugs in the Intel xed repository.
As we are comparing our disassembly against xed and other disassemblers, we are curious to know if you do a similar thing and what sources you used for your data-tables. Did you compose them by hand using the official documentation?
Best regards

Only official Intel and AMD docs so far, but I know that sandpile has some undocumented instructions so will have a look there later.

Cool. Thanks for the answer.


Updating the Window Controls Overlay docs

Window Controls Overlay is shipping with Edge 105. So, I went over the docs written last year, and updated them.

Docs Build status updates of commit b2944c2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/progressive-web-apps-chromium/how-to/window-controls-overlay.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/media/my-tracks-draggable-titlebar.png
:white_check_mark:Succeeded
n/a (file deleted)

microsoft-edge/progressive-web-apps-chromium/media/my-tracks-titlebar.png
:white_check_mark:Succeeded
n/a (file deleted)

microsoft-edge/progressive-web-apps-chromium/media/my-tracks-titlebar-toggle.png
:white_check_mark:Succeeded
n/a (file deleted)

microsoft-edge/progressive-web-apps-chromium/media/vscode-titlebar.png
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/media/wco-draggable-titlebar.png
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/media/wco-reserved-titlebar.png
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/media/wco-toggle-button.png
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@diekus for info, here is an update for our WCO docs, in case you want to take a look.

Docs Build status updates of commit 7bd2b7f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/progressive-web-apps-chromium/how-to/window-controls-overlay.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/media/my-tracks-draggable-titlebar.png
:white_check_mark:Succeeded
n/a (file deleted)

microsoft-edge/progressive-web-apps-chromium/media/my-tracks-titlebar.png
:white_check_mark:Succeeded
n/a (file deleted)

microsoft-edge/progressive-web-apps-chromium/media/my-tracks-titlebar-toggle.png
:white_check_mark:Succeeded
n/a (file deleted)

microsoft-edge/progressive-web-apps-chromium/media/vscode-titlebar.png
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/media/wco-draggable-titlebar.png
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/media/wco-reserved-titlebar.png
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/media/wco-toggle-button.png
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[EIM] Improve Data Access in .NET Template

Platform

.NET WPF

Issue
https://microsoft.visualstudio.com/OS/_workitems/edit/39840739

This work is not started yet :)


Replace the font renderer with one without the issues of anti-aliasing/hinting/subpixel/baseline

Bevy version
Bevy 0.5.0.
What you did
Comparison between the font rendered by Bevy (ab_glyph) and Firefox (with subpixel disabled and subpixel enabled).
What you expected to happen
The font rendered with anti-aliasing in Bevy should be as rendered as close as possible as in Firefox (readable in small sizes, sharp, and correct positioning of glyphs).
What actually happened
Issue 1: aliasing
Font in Bevy is "bulkier". It is possible to notice that the anti-aliasing in Bevy generates a pixel with higher lightness than in the other implementations, that it is possible to notice single pixels without zooming-in (look at the letter e, for example).
The line on the top is Bevy, the line in the middle is Firefox with subpixel disabled, and the line bellow is Firefox with subpixel enabled:

The values indicated are the values of LCh lightness (using the color picker from GIMP). The lightness of the anti-alias in the Bevy implementation is 3-5 times than in the other implementations.
Issue 2: vertical positioning
Another issue is the positioning of the glyphs on the baseline. In Bevy, with certain fonts at certain font sizes, the glyphs will be rendered on the incorrect vertical position:

It only happens with certain sizes, but not others. The examples above (showing the aliasing issues) are rendered in the correct vertical position, but not at size 15.
Possible issue 3: sizing
The size defined in TextStyle does not match the size in other implementations. On the first image (showing the aliasing issues), for example, I had to use the size 14.5 to match the font size 12 in Firefox.
Additional information
I did this experiment using the font "Fredoka One" on Google Fonts for comparison.
Proposal
Replace the Bevy implementation with one of two existing solutions: fontdue or swash. It seems that these two libraries are the best options for font rendering in pure Rust. We should evaluate which features that both have or don't have that are important for Bevy.

Could you also test Bevy with its subpixel_glyph_atlas Feature enabled?

Issue 2: vertical positioning

Good ol' wavy text... https://github.com/bevyengine/bevy/issues/283, https://github.com/bevyengine/bevy/pull/725, https://github.com/bevyengine/bevy/pull/765

I noticed 1 and 2 while working on my Sudoku game, and strongly support this proposal. Clean text rendering is important and basically impossible to fix as an end user.

Could you also test Bevy with its subpixel_glyph_atlas Feature enabled?

Akoriam (on Discord showed that the first issue might be solved by applying (2.2) gamma correction in the font renderer and the aliasing of Bevy will look like the anti-aliasing of non-subpixel anti-aliasing of Firefox. What remains to determine if it is worth switching to fontdue or swash to 1) solve the bug with vertical positioning or to 2) have the features of those libraries (fontdue/swash) in Bevy.

Swash would also allow shaping.

Has there been any further discussion on this?

Not a great deal, but it seems clear that our current font rendering solution is inadequate. IMO, opening up a draft PR with a
backend swap and showing the before / after results would help us come to a concrete decision sooner.

A few weeks ago https://github.com/pop-os/cosmic-text was released.

Yep I'm in favor of exploring a migration to this.

Bevy now uses swash by way of cosmic-text.
As far as I can tell, all three issues enumerated in the description are now resolved.


[BUG] Unit test suite failed 2 test cases on Fedora Linux x86_6

When running the unit test suite of bpftime on Fedora Linux x86_64, I'm seeing 2 test cases failing consistently:
===============================================================================
test cases:   16 |   14 passed | 2 failed
assertions: 8385 | 8383 passed | 2 failed

The detailed errors for these 2 test cases are as following:
/home/agentzh/bpftime/runtime/unit-test/attach/test_function_address_resolve.cpp:26: FAILED:
  REQUIRE( addr == (void *)&malloc )
with expansion:
  0x00007f00edf33220 == 0x000000000040f1b0
with message:
  malloc addr resolved:<PHONE_NUMBER>65824

and also
/home/agentzh/bpftime/runtime/unit-test/tailcall/test_user_to_kernel_tailcall.cpp:64: FAILED:
  REQUIRE( prog_fd >= 0 )
with expansion:
  -1 >= 0

OK, I can firm that one of the test failure can be fixed by running make unit-test with sudo. Now only the test_function_address_resolve.cpp test failure remains.

Seems the CI is working with the test fixed. See #192 and #161


Add Windows CI support

Fixes #367

File is inspired from https://github.com/ensime/scala-debugger/blob/master/appveyor.yml. My understanding of Windows is limited, to say the least, but sounds like this should do it.
As AppVeyor is quite slow, I've removed crossTestBridges, which is the past running the test of the bridges, and left the unit and scripted tests. The reason why I'm removing the test of the bridges is speed. AppVeyor won't keep up the pace to run our intensive pipeline and these tests are the more likely to run successfully in Windows (since they are just a compiler plugin).  It goes without saying that the bridges are actually tested in scripted too, so that should be safe-ish.
Objections?

I'm happy with some, initial Windows testing over the current none. We can tweak over time.

I don't know if to be happy or not:
[error] (zincRoot/*:scripted) Failed tests:
[error] 	source-dependencies / canon
[error] 	source-dependencies / packageobject-and-traits
[error] 	source-dependencies / recorded-products
[error] Total time: 256 s, completed Jul 17, 2017 9:37:20 P

The most impressing part is that a pending test for Linux is passing for Windows: packageobject-and-traits. LOL.

Status:

[ ] source-dependencies/canon -> Looks like a scalac classpath error. Need to reproduce and report.
[ ] source-dependencies/recorded-products -> A simple error that assumes / instead of \.
[ ] source-dependencies/packageobjects-and-traits -> Looks like an uncovered IO error. To double-check.

@eed3si9n In one of my last comments, I mention one example in which our less precise way of testing integration tests via high-level tasks like compile bites us. I've experienced other similar cases personally. This is just a data point.

@jvican Cool. Thanks for pointing it out. These data points would indeed help in future discussions.

I'll close this for now (just to be sure not to lose the effort here I've cross-linked it in #367). Revival welcome!


bug: renaming a conversation changes the model used

I'm using gpt4 turbo by default (so it appears as a fine tuned model) but when I change the name of the chat afterwards the name of the model changes back to gpt3.5 turbo

Look's like all settings are being copied from Global settings instead of chat setting.

Fixed in release 3.3

Look's like all settings are being copied from Global settings instead of chat setting.

Hmm okay but i have not changed my global settings and they are not set to gpt3.5 but the gpt4 turbo
Thanks for the quick reply


New file for MH-S511 - 3 versions

To replace mh-s511-il.json

Superseded by https://github.com/zwave-js/node-zwave-js/pull/2151


[WIP] New overview endpoint

Description
New endpoint for getting an overview about the number of clusters that are being impacted by rules
At the moment, only the openapi specification has been pushed to the PR
Fixes #132
Type of change

New feature (non-breaking change which adds functionality)
Unit tests (no changes in the code)
REST API tests
Documentation update

Testing steps
N/A for the moment. OpenAPI spec manually checked using the OpenAPI tools validator

Codecov Report

Merging #207 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #207   +/-   ##
=======================================
  Coverage   49.28%   49.28%
=======================================
  Files          12       12
  Lines        1051     1051
=======================================
  Hits          518      518
  Misses        474      474
  Partials       59       59

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 cf48818...f70910d. Read the comment docs.


[WIP] Add host guest analysis

This begins adding host-guest analysis, updating scripts used for SAMPL6. So far I have a first pass at the TrimerTrip analysis, at least for the ranked submissions. Still to do (among other things):

[x] GDCC analysis
[ ] CD analysis
[ ] Separate analysis of non-ranked submissions

I have TrimerTrip and GDCC in now; I will go ahead and merge this and then handle CD in a separate PR.


[Added] Sortable BREAD Items

Making BREAD items sortable, this changes fields order on views Browse/Edit/Add.
Fixes #994.

How can i change the order of my fields in the edit-add view please ?

Hi @Rostom22 when you edit a BREAD item, you can easily order fields by drag-and-drop rows.
Don't forget to hit save, because this isn't working with AJAX.
If you're using a older version of Voyager, make sure you have the latest assets / migrations.
Good luck!

Hi, i tried to drag-and-drop but it'sn't working, also in te edit-add view the field appears in different order. thanks for your help.

Hello, when you say it doesn't work, the drag-and-drop UI effect is visible/working?
It seams you're not using the latest version.
Please check if you:

published Voyager views before, if so, you need to make sure you update them.
run the migration, if you did, you should see a new field named order in data_types table.

I suggest you to join us on Slack, it may be faster to help you.
Happy coding :)

Sorry i'm a begginer and i don't understand very well, i installed voyager with composer 5 days ago following the videos of devdojo. what's the Slack ? Thanks again !

It's ok, we all started somewhere :)
Please keep in mind that you need to know the basis of Laravel, otherwise it's hard to jump on a project like Voyager.
Slack channel is were the community hangs out. You can get support from there.
https://laravel-voyager.slack.com/

Hello, the drag-and-drop UI effect is not visible, to get the new version i just run composer update ? how can i get an invitation for slack ? thanks.


can rename pools to invalid identifiers

Description
pool names should be a valid identifier. but it can be edited to anything

there is no check done on the actor side for this. it should be added to the actor and probably ui as well

Verified
Branch: development_vdc
Commit: da50148a76d6e9a94699c00311e004cf50c1d878


Claim mapping is missing

Tested: version 1.0.1
None of the data received from LinkedIn is mapped to local claims. These fields are present and populated in the LinkedInAuthenticator class after successful auth: emailAddress, firstName, headline, id, industry,lastName
It seems though that the fields are not being transferred in any claim mapping to provisioning or to SAML SSO. I have tried setting up basic claim mapping for both emailAddress and email-address to http://wso2.org/claims/emailaddress without success.

Hi @robertgartman ,
Jira [1] created to track this issue. please follow the jira.
[1]https://wso2.org/jira/browse/ISCONNECT-37

@robertgartman, if you're using IS 5.3.0, I've attached a screenshot in [1] how I mapped the new linkedin claims I have created into wso2 basic claims in my Linkedin Identity Provider set-up. here's my update: [1]
https://wso2.org/jira/browse/ISCONNECT-38?focusedCommentId=131738&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-131738
HTH! It took me weeks to figure that out. IS connector docs are outdated and will not work for IS 5.3.0. Everybody failed to mention the "Advanced Claim Configuration" portion (or maybe I was just missing that).


Using Jira gem issue model for issue creation

Instead of hard coding the issue api url, allow the gem to build and
make the request in the 'receive_issue_impact_change' method. This may
resolve issues encountered with self-hosted JIRA such as Issue #72.
This also stops catching and rethrowing all exceptions in the
'receive_issue_impact_change' method. These errors should be handled by
the caller.

:+1:


Add servertiming header

Intorducing severtiming header. This required porting of 128bit TraceId, propagation changes and W3C propagator from otel repo.
@signalfx/instrumentation

@dszmigielski @johnbley the tests are failing because the server timing headers are missing for some "bad request" responses. I assume that we want the headers even on such cases, correct?

Flaky tests:
Same flaky test:
2021-04-29T21:49:09.7421340Z [xUnit.net 00:00:11.2138365]     Datadog.Trace.Tests.Sampling.RateLimiterTests.Limits_Approximately_To_Defaults [FAIL]
2021-04-29T21:49:09.7528908Z   X Datadog.Trace.Tests.Sampling.RateLimiterTests.Limits_Approximately_To_Defaults [8s 426ms]
2021-04-29T21:49:09.7530650Z   Error Message:
2021-04-29T21:49:09.7531725Z    Expected between 714 and 915, received 701 out of 4000 within 8140.0557 milliseconds.
2021-04-29T21:49:09.7532716Z Expected: True
2021-04-29T21:49:09.7533410Z Actual:   False
2021-04-29T21:49:09.7534159Z   Stack Trace:
2021-04-29T21:49:09.7537570Z      at Datadog.Trace.Tests.Sampling.RateLimiterTests.Run_Limit_Test(Nullable`1 intervalLimit, Int32 numberPerBurst, Int32 numberOfBursts, Int32 millisecondsBetweenBursts) in D:\a\1\s\test\Datadog.Trace.Tests\Sampling\RateLimiterTests.cs:line 86
2021-04-29T21:49:09.7539863Z    at Datadog.Trace.Tests.Sampling.RateLimiterTests.Limits_Approximately_To_Defaults() in D:\a\1\s\test\Datadog.Trace.Tests\Sampling\RateLimiterTests.cs:line 56
2021-04-29T21:49:15.2517370Z Results File: D:\a\_temp\VssAdministrator_WIN-16SS5M8JT0C_2021-04-29_21_49_00.trx
2021-04-29T21:49:15.2518686Z
2021-04-29T21:49:15.2535472Z Test Run Failed.
2021-04-29T21:49:15.2536534Z Total tests: 312
2021-04-29T21:49:15.2537779Z      Passed: 311
2021-04-29T21:49:15.2538716Z      Failed: 1
2021-04-29T21:49:15.2540200Z  Total time: 17.4239 Seconds

2021-04-29T21:49:28.9279954Z   X Datadog.Trace.Tests.Sampling.RateLimiterTests.Limits_Approximately_To_Defaults [8s 314ms]
2021-04-29T21:49:28.9282488Z   Error Message:
2021-04-29T21:49:28.9283538Z    Expected between 704 and 905, received 602 out of 4001 within 8041.0129 milliseconds.
2021-04-29T21:49:28.9284274Z Expected: True
2021-04-29T21:49:28.9284629Z Actual:   False
2021-04-29T21:49:28.9285108Z   Stack Trace:
2021-04-29T21:49:28.9286169Z      at Datadog.Trace.Tests.Sampling.RateLimiterTests.Run_Limit_Test(Nullable`1 intervalLimit, Int32 numberPerBurst, Int32 numberOfBursts, Int32 millisecondsBetweenBursts) in D:\a\1\s\test\Datadog.Trace.Tests\Sampling\RateLimiterTests.cs:line 86
2021-04-29T21:49:28.9287466Z    at Datadog.Trace.Tests.Sampling.RateLimiterTests.Limits_Approximately_To_Defaults() in D:\a\1\s\test\Datadog.Trace.Tests\Sampling\RateLimiterTests.cs:line 56
2021-04-29T21:49:33.9421362Z Results File: D:\a\_temp\VssAdministrator_WIN-16SS5M8JT0C_2021-04-29_21_49_18.trx
2021-04-29T21:49:33.9422642Z
2021-04-29T21:49:33.9440349Z Test Run Failed.
2021-04-29T21:49:33.9441636Z Total tests: 316
2021-04-29T21:49:33.9442548Z      Passed: 314
2021-04-29T21:49:33.9443474Z      Failed: 2
2021-04-29T21:49:33.9445210Z  Total time: 18.1409 Seconds

Some race condition here:
2021-04-29T21:49:23.8678895Z [xUnit.net 00:00:07.3318227]     Datadog.Trace.Tests.AgentWriterTests.WriteTrace_2Traces_SendToApi(synchronousSend: False) [FAIL]
2021-04-29T21:49:24.4205265Z   X Datadog.Trace.Tests.AgentWriterTests.WriteTrace_2Traces_SendToApi(synchronousSend: False) [5s 135ms]
2021-04-29T21:49:24.4207126Z   Error Message:
2021-04-29T21:49:24.4207994Z    Moq.MockException :
2021-04-29T21:49:24.4209069Z Expected invocation on the mock once, but was 0 times: x => x.SendTracesAsync(It.Is<Span[][]>(y => y.Single<Span[]>().Equals([TraceId:
2021-04-29T21:49:24.4210563Z ParentId: 0
2021-04-29T21:49:24.4211617Z SpanId:<PHONE_NUMBER>493136555
2021-04-29T21:49:24.4212420Z ServiceName:
2021-04-29T21:49:24.4213213Z OperationName:
2021-04-29T21:49:24.4213954Z Resource:
2021-04-29T21:49:24.4216770Z Type:
2021-04-29T21:49:24.4217579Z Start: 1/1/0001 12:00:00 AM +00:00
2021-04-29T21:49:24.4218428Z Duration: 00:00:00
2021-04-29T21:49:24.4219125Z Error: False
2021-04-29T21:49:24.4219812Z Meta:
2021-04-29T21:49:24.4220448Z Logs:
2021-04-29T21:49:24.4221042Z Metrics:
2021-04-29T21:49:24.4221686Z ])))
2021-04-29T21:49:24.4222366Z No setups configured.
2021-04-29T21:49:24.4223151Z No invocations performed.
2021-04-29T21:49:24.4223844Z   Stack Trace:
2021-04-29T21:49:24.4225655Z      at Moq.Mock.ThrowVerifyException(MethodCall expected, IEnumerable`1 setups, IEnumerable`1 actualCalls, Expression expression, Times times, Int32 callCount)
2021-04-29T21:49:24.4227652Z    at Moq.Mock.VerifyCalls(Mock targetMock, MethodCall expected, Expression expression, Times times)
2021-04-29T21:49:24.4228933Z    at Moq.Mock.Verify[T,TResult](Mock`1 mock, Expression`1 expression, Times times, String failMessage)
2021-04-29T21:49:24.4230024Z    at Moq.Mock`1.Verify[TResult](Expression`1 expression, Func`1 times)
2021-04-29T21:49:24.4231343Z    at Datadog.Trace.Tests.AgentWriterTests.<WriteTrace_2Traces_SendToApi>d__0.MoveNext() in D:\a\1\s\test\Datadog.Trace.Tests\AgentWriterTests.cs:line 37
2021-04-29T21:49:24.4233155Z --- End of stack trace from previous location where exception was thrown ---
2021-04-29T21:49:24.4234069Z    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
2021-04-29T21:49:24.4235166Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2021-04-29T21:49:24.4236268Z --- End of stack trace from previous location where exception was thrown ---
2021-04-29T21:49:24.4238321Z    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
2021-04-29T21:49:24.4239443Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2021-04-29T21:49:24.4240390Z --- End of stack trace from previous location where exception was thrown ---
2021-04-29T21:49:24.4241258Z    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
2021-04-29T21:49:24.4242262Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2021-04-29T21:49:28.4210804Z [xUnit.net 00:00:11.9079931]     Datadog.Trace.Tests.Sampling.RateLimiterTests.Limits_Approximately_To_Defaults [FAIL]
2021-04-29T21:49:28.9279954Z   X Datadog.Trace.Tests.Sampling.RateLimiterTests.Limits_Approximately_To_Defaults [8s 314ms]
2021-04-29T21:49:28.9282488Z   Error Message:
2021-04-29T21:49:28.9283538Z    Expected between 704 and 905, received 602 out of 4001 within 8041.0129 milliseconds.
2021-04-29T21:49:28.9284274Z Expected: True
2021-04-29T21:49:28.9284629Z Actual:   False
2021-04-29T21:49:28.9285108Z   Stack Trace:
2021-04-29T21:49:28.9286169Z      at Datadog.Trace.Tests.Sampling.RateLimiterTests.Run_Limit_Test(Nullable`1 intervalLimit, Int32 numberPerBurst, Int32 numberOfBursts, Int32 millisecondsBetweenBursts) in D:\a\1\s\test\Datadog.Trace.Tests\Sampling\RateLimiterTests.cs:line 86
2021-04-29T21:49:28.9287466Z    at Datadog.Trace.Tests.Sampling.RateLimiterTests.Limits_Approximately_To_Defaults() in D:\a\1\s\test\Datadog.Trace.Tests\Sampling\RateLimiterTests.cs:line 56
2021-04-29T21:49:33.9421362Z Results File: D:\a\_temp\VssAdministrator_WIN-16SS5M8JT0C_2021-04-29_21_49_18.trx
2021-04-29T21:49:33.9422642Z
2021-04-29T21:49:33.9440349Z Test Run Failed.
2021-04-29T21:49:33.9441636Z Total tests: 316
2021-04-29T21:49:33.9442548Z      Passed: 314
2021-04-29T21:49:33.9443474Z      Failed: 2
2021-04-29T21:49:33.9445210Z  Total time: 18.1409 Seconds

@pellared @johnbley @pjanotti Anything else is needed here or can we merge this PR?

We're good here I think


Comsats University Islamabad's student domain added

Comsats University Islamabad's student domain added

@faizankarim .idea/libraries/KotlinJavaRuntime.xml: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.


Files app crashing

Files app is crashing when you are transfering data (copying or moving files) and you try to open another app, such as Software Updater or Software center. Sometimes it crashed on opening another window of Files app.
It does not give you an error message. It just disappears from the screen and stops the data transfering process.
I'm using eOS Freya. My system is and was updated at the moment of those crashes. Kernel 3.16.0-46 running x64 on an AMD machine.
My linux runs in an ext4 partition on a ssd and I was copying data from a ntfs partition to a ext4 one. It also crashed while I was copying from a ntfs to another ntfs partition.
I don't do dual boot. I just use elementary. All those copies that crashed were made on spinning drivers that were mounted as part of /media/(user)/(drive label) tree automatically by Files app.

Unfortunately, this is not the place to file bugs with files. That can currently be done at https://bugs.launchpad.net/pantheon-files/+filebug
I am curious as to where linked to here in such a way as to cause this confusing?

Sorry. It was the first hint in "get envolved" page. I confess i didnt read


Support for GCP Pub/Sub Topic

What problem are you facing?
I'd like to provision a Pub/Sub Topic resource.

How could Crossplane help solve your problem?
Implement GCP PubSub managed resources from this API https://cloud.google.com/pubsub/docs/apis

@jacobstr could you let us know what bits (i.e. APIs/Concepts) of pubsub would be the most impactful for us to support?

Implemented by https://github.com/crossplane/provider-gcp/pull/241 but feel free to comment about additional features you'd like to see in PubSub group.


⚠ Bofrost.at has degraded performance

In fefb04d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2737 ms

Resolved: Bofrost.at performance has improved in 26261f9 after 26 minutes.


Application Manifest JSON Schema

Please provide JSON Schema (https://json-schema.org/) for Application Manifest YAML files to have ability to validate them.

I've been working on a draft 07 schema a bit here, and have definitions/types for (I think) all of the current attributes including titles and descriptions for IDE hints. It includes validation for attributes that have documented mutual exclusions such as routes, docker, health-check-http-endpoint (for incompatible health-check-type), and uses some non-standard deprecation attributes to mark features as such.
Most of the constraints and descriptions are based on the cf app manifests docs and STS4 manifest-yaml-language-server.
Current consumable versions are deployed at https://parkerm.gitlab.io/cf-manifest-schema/json/manifest.schema.json.
If there's interest in using this work I could submit a PR, but would need some guidance as to where the schema would go or how it should be integrated.

Hi @fitmanyak @ParkerM  thanks for reaching out. I've marked this an enhancement and will try to circle around again when we can.

As manifest parsing will be the responsibility of Cloud Controller (server-side), it seems to me the CAPI team should publish the JSON schema for the manifest. @ssisil @tcdowney

Thanks for pointing this out to us, @shalako.
@ssisil I think providing a JSON schema along with our docs here would definitely help clients consume the endpoint and we could test against it internally to guard against regressions as we make changes. Especially changes like #158669166 which will allow for multiple datatypes for the same attribute (hopefully JSON schema can handle this case 🤞). We already make use of JSON schema for our services endpoints to ensure compatibility with the Open Service Broker API (see these tests) so it's definitely not unprecedented.
Also big thanks to @ParkerM for the work on that draft schema, really helps to visualize what this could look like for the manifests. 💯

Especially changes like #158669166 which will allow for multiple datatypes for the same attribute (hopefully JSON schema can handle this case 🤞).

If I understand this part correctly, then JSON schema (at least draft 07) should be more than capable of handling such cases through the built-in logical operators. Basic example here.
E.g. if a service has parameter foo, we could constrain that specific param to either be a boolean, a non-negative number, or some other more complex type with the following:
"services": {
  "type": "array",
  "items": {
    "type": "object",
    "properties": {
      "name": {
        "type": "string"
      },
      "parameters": {
        "type": "object",
        "foo": {
          "oneOf": [
            {"type": "boolean"},
            {"type": "number", "minimum": 0},
            {"$ref": "#/definitions/superfoo"}
          ]
        }
      }
    }
  }
}

The $ref keyword is notably powerful for DRY/extensibility, and can also reference remote schemas. It may even be possible for service offerings to provide their own discoverable "live" schemas against which a generic manifest schema could be used to validate a manifest's services config, potentially preventing a botched deploy.

@tcdowney

I think providing a JSON schema along with our docs [here](http://v3-apidocs.cloudfoundry.org/version/3.68.0/index.html#app-manifest) would definitely help clients consume the endpoint

The Json schema are likely to be used by developers in their preferred IDE (e.g. in intellij), which automatically selects and downloads the associated Json schema based on registered file patterns (in our case ./manifest.yml) in http://schemastore.org/json/, and then provides completion as well as inline documentation/hints.
That'd be awesome in the future to have concourse pipeline submitting upstream PRs when new versions of the application manifest schema gets published, and leave it up to ides/app developers to select the appropriate version matching their CF deployment (see related https://github.com/SchemaStore/schemastore/issues/197#issuecomment-229690162)
CF web uis, may also need to download and use the Cf Json schema corresponding to the version of currently targetted api endpoint, and automatically generate user-facing forms to edit the application. It might be useful to have the json schema being downloadeable from an easily discoverable endpoint (e.g. json schema url be listed in /v2/info endpoint). Currently, the /v2/info endpoint returns an api_version such as "api_version": "2.123.0" whereas the apidocs endpoint seems to expect a capi version as path parameter such as https://apidocs.cloudfoundry.org/4.5.0/

Hi folks, I'm going to transfer this issue to CAPI since sever side manifest is handled by them in V3.


Handle mint tokens when account is not funded

In order to make an account exist in Stellar it should be funded at least 1 time.
If an account is not funded, a 404 error is encountered when reading token balance.
Disable mint test tokens button if account is not found, display instead "Fund wallet" in a disabled mode.


Fix broken debugger tests due to missing IFileSystem

For #https://github.com/microsoft/vscode-python/issues/8882
For #https://github.com/microsoft/vscode-python/issues/8895

Codecov Report

Merging #9189 into master will increase coverage by 0.32%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9189      +/-   ##
==========================================
+ Coverage    56.8%   57.12%   +0.32%
==========================================
  Files         550      550
  Lines       28938    29308     +370
  Branches     4441     4435       -6
==========================================
+ Hits        16438    16742     +304
- Misses      11560    11625      +65
- Partials      940      941       +1

Impacted Files
Coverage Δ

src/client/testing/serviceRegistry.ts
49.09% <0%> (-42.14%)
:arrow_down:

src/client/datascience/jupyter/jupyterUtils.ts
64.7% <0%> (-18.63%)
:arrow_down:

src/client/common/utils/platform.ts
64.7% <0%> (-11.77%)
:arrow_down:

src/datascience-ui/interactive-common/tokenizer.ts
35% <0%> (-5%)
:arrow_down:

src/client/linters/pylint.ts
94.82% <0%> (-3.45%)
:arrow_down:

src/client/providers/providerUtilities.ts
83.33% <0%> (-3.34%)
:arrow_down:

src/client/api.ts
78.57% <0%> (-3.25%)
:arrow_down:

src/client/testing/codeLenses/main.ts
40% <0%> (-2.86%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.36% <0%> (-2.28%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0%> (-1.57%)
:arrow_down:

... and 44 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 bbddaf9...9d23aba. Read the comment docs.

Thanks for taking care of this, @DonJayamanne!


Is there a docker image for arm architecture?

Hi,
I'm currently using Container-mon on my "normal" computers with following compose:
version: "3.8"
services:
  container-mon:
    container_name: container-mon
    image: ghcr.io/rafhaanshah/container-mon:latest
    restart: unless-stopped
    environment:
      - DOCKER_HOST=tcp://docker-proxy:2375
      - CONTAINERMON_NOTIFICATION_URL=telegram://${TELE_TOKEN}@telegram?channels=${TELE_ID}
      - CONTAINERMON_CRON=*/2 * * * *
    depends_on:
      - docker-proxy

  docker-proxy:
    container_name: docker_proxy
    image: tecnativa/docker-socket-proxy
    environment:
      - CONTAINERS=1
      - POST=0
    volumes:
      - '/var/run/docker.sock:/var/run/docker.sock'
    ports:
      - 2375:2375
    privileged: true
    restart: unless-stopped

but trying to use the same results in exec format error on raspberry pi's for the container-mon container indicating incompatible architecture.
Is there a way to build the docker image on arm architectures? Thanks for any info.

Hey, while I don't have a pre-built image for arm yet (I should get around to it at some point though) you can quite easily build an arm image yourself.
Clone the repo:
git clone https://github.com/RafhaanShah/Container-Mon && cd Container-Mon
Edit docker-compose.yaml with a text editor:

Replace image: ghcr.io/rafhaanshah/container-mon:latest with build: .

This should build the image on your Pi with the arm based version of the base image when you run it. 😄

Many thanks this worked great! Didn't know it's that easy to build, thanks for the steps.

As a sidenote on rpi 4 running 64bit no further steps needed to be taken, however on the zero, zero-w and rpi3b's it complained about too high docker-compose version, so I just changed version: "3.8" in docker-compose.yaml to version: "3" on top of the steps to make it work.

Ah, that's based on the version of the Docker Engine you've got installed, 3.8 is the latest compose file version
https://docs.docker.com/compose/compose-file/compose-versioning/

Hey! I (finally) have multi-platform images built, let me know if the latest ones work on your Raspberry Pi 😄

Good news! Can confirm it works on pi3b and pi4 (don't have the zeros anymore).

Awesome, thanks for checking! 😃


High CPU usage and very slow performance when using with Grammarly

I installed Grammarly recently and noticed that stackedit performs very slowly when Grammarly is enabled.  At the same time, chrome is using nearly 100% of one core, and stackit seems to try and sync with the cloud server continuously non-stop.  Is there anything I can do to prevent this from happening?

I'm having the same issue

Can confirm, too.

me too, the performance is so bad and cannot use stackedit properly

I agree with the slowing with Grammarly and this morning I also noticed that with Grammarly on there seems to be a new line created in the document for every character typed which may be contributing to the slow down.

I am having that issue too.
Should this issue raised here or to Grammarly.

same here when editing wiki articles. I have have grammerly enabled :'(

I see this issue when editing emails in google's inbox. They often take 30-40 seconds to open.

Yeah, I too have the same problem. Grammarly adds many empty lines and StackEdit becomes pretty slow.

That would be an issue with Grammarly, not the other way around.


New release for #![no_std] support

It would be cool to get a new release of gimli so that issue #138 is fixed on the latest release as well. This is needed so that addr2line can offer #![no_std] support itself, which is needed so that addr2line as well as gimli can be used inside the libstd library (https://github.com/gimli-rs/addr2line/issues/89, https://github.com/rust-lang/rust/issues/46439).
It is more than 6 months since the last release of gimli. I'd say it's reasonable to have a new release again.
Thanks!

@philipc was there anything else with regards to EndianReader that you wanted to land before we push out a new release? Or anything else in general?
Otherwise, I'm happy to push a new release.

No, I think it's good for a release.


Update to k8s 1.14.0 client libraries using go.mod

Signed-off-by: Tamal Saha<EMAIL_ADDRESS>

Also use<EMAIL_ADDRESS>


Get costs of upgrading the migration cost of 1.4-1.5

confirm we are testing with test data representative of what is in mainnet. Run an upgrade and accurately measure the migration cost of 1.4-1.5

onetime measurement for acceptance testing,


fix: error with currentExtent

name: Bug fix
about: Fixing a problem with Flutter Bottom Sheet.
assignees: MbIXjkee

Checklist

[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Is there an existing issue for this PR?

link issue here

[ ] Have the files been linted and formatted?
[ ] Have the docs been updated to match the changes in the PR?
[ ] Have the tests been updated to match the changes in the PR?
[x] Have you run the tests locally to confirm they pass?

Changes
currentExtent of FlexibleBottomSheet content has default value
What is the current behavior, and the steps to reproduce the issue?

Press the "Open BottomSheet" button
controller of _FlexibleBottomSheetState is not attached

What is the expected behavior?
The BottomSheet is shown and position value is 0.5
How does this PR fix the problem?
size value of DraggableScrollableController is used only when controller is attached

https://user-images.githubusercontent.com/23340521/192269505-cc990d5e-fb40-44b7-88ea-939820207fb2.mp4


There doesn't seem to be a way to open or save a project

Summary
There doesn't seem to be a way to open or save a existing project in the file menu
How to reproduce
-Open duality editor
-Goto the mainmenu->file
-See there is a save all but no save or open
Workaround

unknown

Analysis

unknown

Attachments

This is a side effect of the "one folder = one project" philosophy behind Duality. Opening another project would essentially mean "close this instance and open the one in the selected folder"

Yep, that's it. To open another project, you start the editor instance from its folder.
Closing this, since I don't think the intention of this was to change the fundamental design here, and the underlying question has been cleared up by @SirePi.

@ilexp can this be reopened its still not clear why this can't be added.
I don't see the benefit of only having 1 project.
there doesn't seem to be a way to open a existing one instead of creating an entirely new one every time the editor is ran

Ok so I now know how to open projects.
you have to run the dualitor executable inside the project folder.
this seems wrong can this be changed to actually use a project system?

It's not the standard approach, but there are good reasons for it too - like allowing each project to stick with its exact configuration of plugins and modules, and not forcing them to use some shared centrally installed version. Not requiring a central installation is also a feature.
While theoretically possible to change this, there's not really a great reason to do that right now, all impacts considered.

@ilexp The project can stick with the exact configuration with this method too just have the project have a asset and a addons folder
this is a major usability issue and might actually be steering people away from using this

this is a major usability issue and might actually be steering people away from using this

It's a different approach, yes, but I don't see how this is inherently less usable. Your project forms a self-contained unit with everything it needs to run and be edited. You can copy it around freely, move it to different machines, check it in and out of version control across devices without the need to install some software in a specific version on all of them. Overall, I'd consider this a plus 🙂

Our current approach ensures there are no global dependencies. This a big plus as it makes it possible to just download a project and open it without any problems with different installed versions.
With v4 our current approach makes even more sense as a duality project will basically be a bunch of a package references, your code and some resources. You can check this all into source control which makes it easy to see what changed in the past as there are no binaries.

@ilexp you can't do that with any other file structure too.
@Barsonax
all that would be needed would be a core addon in the addons folder.
that would be the engine.
then you could new, open and save your project anywhere on system of move it in the file explorer.
not only does it clean up the project folder but it also implements a common file menus

@ilexp you can do that with any other file structure too.

Let's assume there was a system-wide installation folder with the editor and engine, and a few different project folders somewhere else on the same machine. This is the typical way how applications work, and also the one where you would expect an "open project" menu item.
If you copy one of the projects to a different machine (manually or via version control), it won't work - because engine and editor are missing. To make it work, you'd now have to install the exact same version of engine and editor on that other machine, which is a complex issue in a package-based modular setup like ours. Next, imagine if you have not one project, but multiple projects, using different version configurations of the various packages. It will be very difficult and tedious to keep track of this.
On the other hand, the current system simply doesn't have this issue. You copy the project, and it's all in there, fully self-contained. Done.
And of course there's also the point Barsonax mentioned, the next step in this approach is to fully rely on VS package management and enable projects to be created and managed completely using native tools.

@ilexp your not listening to me.
the whole engine can be a in the plugins folder under <project_name>/plugins/core/ENGINE FILES HERE
it has nothing to do with the menu at all

As far as I can see, this issue turned into a proposed paradigm shift in how projects are managed with Duality, which I think we have discussed. You did not expand on or respond to the points I mentioned, and I seem to not understand what you are talking about - so I'm honestly not sure where else to go from here. I'd be fine with concluding here for now and leaving this as-is.


file timezone problem

Fluentd version: td-agent 1.0.2
I want to transfer logfile from CentOS to CentOS by fluentd.
I could transfer file but file switches at incorrect time.
My timezone is +0900.

output files (ls -l)
rw-r--r-- 1 root root  34201618  5月 15 09:02 test-log.20180514
rw-r--r-- 1 root root  40060437  5月 16 09:01 test-log.20180515
rw-r--r-- 1 root root   5943936  5月 16 10:47 test-log.20180516

I want files switch at 00:00 but actually they switch at 09:00 everyday.
When I set time_slice_format = %Y%m%d_%H files switch correctly. (test.log.20180516_01 is created at 01:00 )
how can I solve it?
config (input) :
<source>
 type tail
 format none
 path /var/log/test-log
 pos_file /var/log/td-agent/test-log.pos
 tag hostfrom.test-log
</source>

<match *.*>
 type forward
 <server>
  host hostlog
  port 24224
 </server>
</match>

config (output) :
<source>
 @type forward
 bind <IP_ADDRESS>
 port 24224
</source>

<match hostfrom.test-log>
 type file
 format single_value
 buffer_path /var/log/td-agent/buffer/test-log.buf
 path /log/test-log
 append true
 path_suffix
</match>

i got same issue

The problem is  %Y%m%d time rage causes incorrect time but %Y%m%d%Htime range has no problem, right?

Yes, %Y%m%d only happens.

Okay, will check.
For workaround, you can use timekey 3600 in <buffer> and %Y%m%d in the path.

For workaround, you can use timekey 3600 in  and %Y%m%d in the path.

It did not work because of config error.
[error]: config error file="/etc/td-agent/td-agent.conf" error_class=Fluent::ConfigError error="insufficient timestamp placeholders in path"
%Y%m%d%H in the path worked with timekey 3600

@f-ueno  I try to set %Y%m%d%H in path, but getting configure error...
<match message.*>
  @type file
  path /tmp/messages/transfer.${tag[1]}.%Y-%m-%d.%H%M.log
  compress gzip
  append true
  <buffer tag,time>
    @type file
    path /tmp/buffer/message
    timekey     1d
    timekey_wait 0
    flush_mode interval
    flush_interval 86400
  </buffer>
</match>

@luweiv9988 I think you should use correct path depending on timekey
%Y%m%d  with  timekey 1d
%Y%m%d%H  with  timekey 1h
%Y%m%d%H%M  with  timekey 1m

It seems time calculation with larger timekey has bug.
I'm now trying to fix the problem.

@repeatedly do you have any workaround if the problem is not fixed ?

@f-ueno Could you try #2054?


Unable to load client bug

Describe the bug
Was hoping worlds on the alt to scout raids, world swapper (the vanilla clients in game world switcher) suddenly just went blank, thought nothing of it because I could still click where worlds would be on the list/ click on favorited worlds, the issue duplicated onto a 2nd Runelite client i had open so I decided to just restart the computer. Relaunched runelite and was greeted with "Unable to launch client please review logs"
To Reproduce
Steps to reproduce the behavior:
Not Able to reproduce due to not being able to log in / access runescape
Expected behavior
N/a
Screenshots

Above is what I saw initially which prompted me to restart the client
Below is my current status with the client

Environment (please complete the following information):

OS: Windows
RuneLite version: <IP_ADDRESS>
Launcher version: <IP_ADDRESS>

client.log
launcher.log

Was able to fix the issue by logging out of runelite then force running the program as an administrator

Most likely not something caused by RuneLite - rather your internet connection with the Jagex servers. Closing as author marked issue as resolved.


[composer-extension] composer doesnt always open

after editing a comment, composer doesn't come up again when editing the main issue body
after creating a new issue, and giving it a label, composer will not open when editing that issue again

test comment

So I reproduced this and initially I though you were right because I reproduced it by adding the above comment, however upon further debugging it doesn't happen every time I edit the comment - to this point it seems a little random (but might just not understand the trigger yet).
What seems to be happening though is that the dom nodes for the form are recreated and so the injected iframe is lost. A couple solutions come to mind:

Try to figure out which nodes are being updated, watch for that and re-inject the iframe

Add an event listener to the Edit button and re-inject the iframe if it's missing

seems a little simpler so I'll try that solution first and see how it goes.


Fix for removal of cookie/survey banner in guide

Cookies set in #65 to remove cookie/survey banners in the guide are not always being applied. It may be easier to hide the banners using CSS.

Would it be simpler to hide the elements with CSS?

@fofr Updated with CSS fix instead 🙂


With compute api (possibly JES) approach, debug parameter is not passed correctly

It should go to variables property.

When constructing the object used to create the Job Request, the _DEBUG value should be passed in the variables section (not arguments).
To test whether this is successful, look at the _DEBUG value in the response when submitting any sasjs request.


Merge 7 -> 8

➡ Forward port
Port gz-sim7 to gz-sim8
Branch comparison: https://github.com/gazebosim/gz-sim/compare/gz-sim8...gz-sim7
Note to maintainers: Remember to Merge with commit (not squash-merge or rebase)

sorry @iche033 I didn't see you opened this. I already merged https://github.com/gazebosim/gz-sim/pull/2428

no problem, closing this one.


Error:  System.TypeInitializationException

Hello to all,
I've tried to define a database target, but iI've always the error: System.TypeInitializationException.
In the NLog. config with the follow simply target:
 I've the error, but with no attribute name, like:

it's ok.
My really target config is:

I've tried with NLog 4.1.0 / 4.2.0 with .net framework 4.0 (windows form application)
Thank's very much for any help
Claudio

Can you check the inner exception? That one tells the cause of this. (some static field which crashes)

HI, you can see the attached file.
NLog_Error.docx
Thank's,
Claudio

So the error is: layoutrender cannot found 'appsetting`.
You need also NLog.extended for that (see wiki).  Just install the latest https://www.nuget.org/packages/NLog.Extended/ - no additional config is needed.
Ps. I removed your docx with a screenshot

Hello,
ok now it's running,r, thank's !
But when a call Log, after an error (try catch), I haven't the row in my
table db, which my mistake ?
I didn't found some examples for windows form with database target....
Claudio
Il 2015-11-18 15:52 Julian Verdurmen ha scritto:

So the error is: layoutrender cannot found 'appsetting`.
You need also NLog.extended for that (see wiki [1]). Just install the latest https://www.nuget.org/packages/NLog.Extended/ [2] - no additional config is needed.
Ps. I removed your docx with a screenshot
--
Reply to this email directly or view it on GitHub [3].

--
CLAUDIO ORLANDI
IT Software
Indicom s.r.l. - Via Carnevali 39 - 20158 Milano
E-MAIL<EMAIL_ADDRESS>WEB: www.indicom.biz [4] - www.fatturafacile.com [5]
Links:
[1] https://github.com/NLog/NLog/wiki/Layout-Renderers
[2] https://www.nuget.org/packages/NLog.Extended/
[3] https://github.com/NLog/NLog/issues/1052#issuecomment-157738316
[4] http://www.indicom.biz
[5] http://www.fatturafacile.com

But when a call Log, after an error (try catch), I haven't the row in my
table db, which my mistake ?

Please check the internal log: https://github.com/NLog/NLog/wiki/Internal-Logging

I didn't found some examples for windows form with database target....

Everything is modular, so there are no special requirements to combine Windows.Forms + Database Target. This should work.

Hi Julian,
it works perfectly !! With internal log I found some error on NLog db
parameters definition
Thank You very much.
Claudio
Il 2015-11-18 18:38 Julian Verdurmen ha scritto:

But when a call Log, after an error (try catch), I haven't the row in my
table db, which my mistake ?

Please check the internal log: https://github.com/NLog/NLog/wiki/Internal-Logging [1]

I didn't found some examples for windows form with database target....

Everything is modular, so there are no special requirements to combine Windows.Forms + Database Target. This should work.
--
Reply to this email directly or view it on GitHub [2].

--
CLAUDIO ORLANDI
IT Software
Indicom s.r.l. - Via Carnevali 39 - 20158 Milano
E-MAIL<EMAIL_ADDRESS>WEB: www.indicom.biz [3] - www.fatturafacile.com [4]
Links:
[1] https://github.com/NLog/NLog/wiki/Internal-Logging
[2] https://github.com/NLog/NLog/issues/1052#issuecomment-157792591
[3] http://www.indicom.biz
[4] http://www.fatturafacile.com

OK closing this one :)
Thanks for the feedback!


UDP probe negative value for failure

Describe the bug
I am seeing negative values for failure counter metrics for the UDP probe type.
This is reflected both in the prometheus metric output for the failure metric counter and in prober logs.
Linux Version
22.04.2-Ubuntu
Cloudprober Version
v0.13.3
To Reproduce
cloudprober.cfg
`host: "redacted"
port: 8080
server {
type: UDP
udp_server {
port: 85
type: ECHO
}
}
probe {
name: "UDP-probes"
type: UDP
latency_unit: "ms"
udp_probe {
port: 85
}
targets {
file_targets {
file_path: "/opt/prober/vips.json"
}
}
interval_msec: 1000  # 1s
timeout_msec: 500   # 500ms
additional_label {
key: "dest"
value: "@target.name@"
}
additional_label {
key: "dest"
value: "@target.label.dest@"
}
additional_label {
key: "src"
value: "@target.label.src@"
}
}`
vips.json
{     "resource": [         {             "name": "redacted",             "ip": "redacted",             "port": 85,             "labels": {                 "dest": "redacted,                 "src": "redacted"             }         }     ] }
Steps to reproduce the behavior:
I've been unable to identity the pattern, which causes this behavior.
I have the same config and prober version applied to 50+ other hosts, which do not see negative values for failure rate counter.
This occurs for approx ~5 out of the 50 hosts we have installed prober to, where we see negative values for failure.
If we restart the counters reset and start positive, but will gradually decrement to negative values.

@Bashere1 is your success metric also bigger than total? Also, I am assuming you see positive failure delta in some cycles and then negative failure delta.. is that correct?
Also, do you have just one target? That's what it looks like from the config (vips.json), but wanted to make sure.

I did a little more digging and it appears that failure is a calculated metic.
It appears as if total isn't getting incremented or success is double incrementing.
TYPE total counter
total{ptype="tcp",probe="TCP-probes",dst="reacated",dest="reacated",src="reacated"}<PHONE_NUMBER>857770
total{ptype="udp",probe="UDP-probes",dst="reacated",dest="reacated",src="reacated"} 3007<PHONE_NUMBER>929
TYPE success counter
success{ptype="tcp",probe="TCP-probes",dst="reacated",dest="reacated",src="reacated"}<PHONE_NUMBER>857770
success{ptype="udp",probe="UDP-probes",dst="reacated",dest="reacated",src="reacated"} 3008<PHONE_NUMBER>929
TYPE latency counter
latency{ptype="tcp",probe="TCP-probes",dst="reacated",dest="reacated",src="reacated"} 30515.632<PHONE_NUMBER>770
latency{ptype="udp",probe="UDP-probes",dst="reacated",dest="reacated",src="reacated"} 138857.599<PHONE_NUMBER>929
TYPE failure counter
failure{ptype="tcp",probe="TCP-probes",dst="reacated",dest="reacated",src="reacated"} 0<PHONE_NUMBER>770
failure{ptype="udp",probe="UDP-probes",dst="reacated",dest="reacated",src="reacated"} -1<PHONE_NUMBER>929

Thanks @Bashere1 for additional information. Does failure keep growing to be even more negative over time.
I'll take a look at the code to see how can success be larger than total.

Yes, we do see positive failure delta in some cycles.
If I bring the dest host UDP port down failures will quickly climb back positive as expected.

Yes, if all things stay consistent negative values will keep trending down over time.

Okay. I've been trying to reproduce it, but unsuccessful so far. From your description, it seems you're able to reproduce it pretty consistently, would you say in about an hour? What's the latency between these hosts -- from your comment it seems to be in ~50ms range, is that correct?
I'll keep trying to reproduce it.

I am able to recreate consistently, but it only appears to be from a single src.
I've not seen this behavior from any other src host with prober installed.
I should have added more details, but I see this behavior even across very low latency connections from this src host to a number of dest pairs < 0.2ms.
I'm going to try to reinstall on another host within the same subnet of the problem host to see if the behavior repeats.
Is there any debugging that I can enable that would help?

If it's just a single host, trying on a different host will help.
A couple of more questions:

Do "source machines" act as "destination" too, for other sources?
Are you probing just one destination per source? Also, are there multiple UDP probes?
Earlier you mentioned approx 5 out of 50 hosts exhibiting this behavior, did you mean 5 targets out of 50 targets?

(I am still running the prober to reproduce, but I may not have that scale).

We have prober installed on about 50 hosts and within the 50 hosts we have a full mesh configuration setup where the src host will probe all other hosts.
source machines do not also act as dest
We only see this issue from a single src host to multiple dest, but those dest acting as a source do not see an issue to the other hosts in the mesh except for the single src host with the issue.
I installed on another compute within the same subnet and do not see this issue except to the known problem host acting as a dest.

This issue seems isolated to a single host and since it's such a perplexing issue I don't want to waste you time.

Thanks @Bashere1 for further testing! I'm going to close this issue then.


Check the type of a hot reload report message

See https://github.com/flutter/flutter/issues/7248

@johnmccutchan

Why are we receiving an invalid response?

If we want to be resilient to invalid data, we should probably be more defensive. This code assumes that there's a type entry and that if it has the magic value, that the rest of the data will be in the expected format. Is that a safe assumption?
If it is, then, with a test, LGTM.

Added a test.
This will check the type of the report message (if it's null/missing, it will return false).  If the type is as expected, it will continue with the preexisting rules.  @johnmccutchan would know if any other rules are needed.

@Hixie The service protocol guarantees responses with certain type field will have a certain shape.
LGTM


Constant int 23 on Entity.GetHashCode

Hello!
Is it a good practice to use the number 23 on the bellow expression as a default on the Entity.cs?
public override int GetHashCode()
{
    return (GetType().GetHashCode() ^ 93) + Id.GetHashCode();
}

Maybe I'm overreacting but magic numbers are prone to create errors. I suppose it would be better to leave that to the developer to choice the GetHashCode() implementation.
What do you think @EduardoPires ?

It is necessary. There is a definition of code quality from Microsoft:
CA2218: Override GetHashCode on overriding Equals
https://docs.microsoft.com/en-us/visualstudio/code-quality/ca2218


[Bug] Does not identify macOS OS/CPU/etc

Description of the bug
I deployed this via macOS in Docker Desktop on an M1 Mac Mini and despite having the privileged flag set to true as well as mounting the volume as directed in the docs, it does not identify the CPU, RAM, or OS.
It identifies the Arch as arm64, states the OS is unknown unknown, and identifies the Processor as - Brand, model of /, and frequency of /. It counts the cores and threads at 4/4
Various info is also wrong:

It only displays RAM available to Docker Desktop as opposed to the entire OS
The uptime is displayed incorrectly. Seems it's only reporting the uptime of Docker Desktop as opposed to the OS itself.

How to reproduce
Deploy with this YML:
services:
  dashdot:
    container_name: dashdot
    image: mauricenino/dashdot:latest
    restart: unless-stopped
    privileged: true
    environment:
      - DASHDOT_PORT=3001
    ports:
      - 9998:3001
    volumes:
      - /:/mnt/host:ro

Relevant log output
Lines
Actions
  },
������
  storage: {
    layout: [ { device: 'vda', brand: 'vda', size:<PHONE_NUMBER>8, type: 'HDD' } ]
  },
������
  network: {
    interfaceSpeed: 0,
    speedDown: 0,
    speedUp: 0,
    type: 'Wired',
    publicIp: ''
  },
  gpu: { layout: [] },
  config: {
    port: 3001,
    running_in_docker: true,
    accept_ookla_eula: false,
    use_network_interface: '',
    fs_device_filter: [],
    fs_type_filter: [ 'cifs', '9p', 'fuse.rclone', 'fuse.mergerfs', 'nfs4' ],
    fs_virtual_mounts: [],
    disable_integrations: false,
    show_host: false,
    custom_host: undefined,
    page_title: 'dash.',
    use_imperial: false,
    enable_storage_split_view: false,
    always_show_percentages: false,
    widget_list: [ 'os', 'cpu', 'storage', 'ram', 'network' ],
    os_label_list: [ 'os', 'arch', 'up_since' ],
    cpu_label_list: [ 'brand', 'model', 'cores', 'threads', 'frequency' ],
    storage_label_list: [ 'brand', 'size', 'type', 'raid' ],
    ram_label_list: [ 'brand', 'size', 'type', 'frequency' ],
    network_label_list: [ 'type', 'speed_up', 'speed_down', 'interface_speed' ],
    gpu_label_list: [ 'brand', 'model', 'memory' ],
    os_widget_grow: 2.5,
    os_widget_min_width: 300,
    enable_cpu_temps: false,
    cpu_widget_grow: 4,
    cpu_widget_min_width: 500,
    cpu_shown_datapoints: 20,
    cpu_poll_interval: 1000,
    storage_widget_grow: 3.5,
    storage_widget_min_width: 500,
    storage_poll_interval: 60000,
    ram_widget_grow: 4,
    ram_widget_min_width: 500,
    ram_shown_datapoints: 20,
    ram_poll_interval: 1000,
    speed_test_interval: 240,
    network_widget_grow: 6,
    network_widget_min_width: 500,
    network_shown_datapoints: 20,
    network_poll_interval: 1000,
    gpu_widget_grow: 6,
    gpu_widget_min_width: 700,
    gpu_shown_datapoints: 20,
    gpu_poll_interval: 1000,
    override: {
      os: undefined,
      arch: undefined,
      cpu_brand: undefined,
      cpu_model: undefined,
      cpu_cores: undefined,
      cpu_threads: undefined,
      cpu_frequency: undefined,
      ram_brand: undefined,
      ram_size: undefined,
      ram_type: undefined,
      ram_frequency: undefined,
      network_type: undefined,
      network_speed_up: undefined,
      network_speed_down: undefined,
      network_interface_speed: undefined,
      network_public_ip: undefined,
      storage_brands: [],
      storage_sizes: [],
      storage_types: [],
      gpu_brands: [],
      gpu_models: [],
      gpu_memories: []
    }
  }
}
Running speed-test (this may take a few minutes)...
First measurement [CPU]: [
  { load: 13.37839370741006, temp: 0, core: 0 },
  { load: 13.276557803494773, temp: 0, core: 1 },
  { load: 13.392866167823417, temp: 0, core: 2 },
  { load: 13.31298936030426, temp: 0, core: 3 }
]
First measurement [Network]: { up: 0, down: 0 }
First measurement [RAM]:<PHONE_NUMBER>
First measurement [Storage]: { layout: [ { load:<PHONE_NUMBER>92 } ] }
Speed-test completed successfully [speedtest-cli] {
  interfaceSpeed: 0,
  speedDown: 71252034.13551842,
  speedUp: 9484044.590437524,
  type: 'Wired',
  publicIp: '<redacted>>'
}

### Info output of dashdot cli

```shell
INFO
=========
Yarn: 1.22.19
Node: v18.12.1
Dash: 4.6.0

Cwd: /app
Hash: 68a114ef96f399acb69125364a744840b30c16d9
In Docker: true
In Podman: false
In Docker (env): true
Done in 0.32s.

What browsers are you seeing the problem on?
Firefox
Where is your instance running?
Other (Please specify below)
Additional context
macOS Monterey

Hello there, thanks for creating this issue! Unfortunately, hosting on macOS is not currently supported via docker for desktop. You could try running it from source.
I am sorry, but I will add that to the documentation to avoid confusion in the future.


c_idx cast to LongTensor in random sparse projection

Fixing https://github.com/openvinotoolkit/anomalib/issues/111

components[i, c_idx.long()] = data.double()

or

c_idx = [int(t.item()) for t in c_idx]
components[i, c_idx] = data.double()

It's taking really much time to get coreset from embedding. Is it expected in patchcore? I'm running on CPU with
num_workers: 1 # 36

It's taking really much time to get coreset from embedding. Is it expected in patchcore? I'm running on CPU with

Yes, the coreset computation in the training step is optimized for GPU. Inference should run fine on CPU.

@alexriedel1 Thanks for your contribution! Let's merge after CI passes.

@alexriedel1 There seems to be a minor black formatting issue. https://github.com/openvinotoolkit/anomalib/runs/5315789777?check_suite_focus=true Can you address it? I think it would be convenient for you if you install pre-commit hooks.
pip install pre-commit
pre-commit install
pre-commit run --all-files

@alexriedel1 There seems to be a minor black formatting issue. https://github.com/openvinotoolkit/anomalib/runs/5315789777?check_suite_focus=true Can you address it? I think it would be convenient for you if you install pre-commit hooks.
pip install pre-commit
pre-commit install
pre-commit run --all-files

I guess thats what black wanted to reformat. Unfortunately I wasnt abel to run the pre commit hooks..

I guess thats what black wanted to reformat. Unfortunately I wasnt abel to run the pre commit hooks..

Can you share the error? We will try to update the docs to address this.

I guess thats what black wanted to reformat. Unfortunately I wasnt abel to run the pre commit hooks..

Can you share the error? We will try to update the docs to address this.

It's an issue on my side. I'm having strange permission issues when trying to run the hooks so dont worry..


Logs on fr2 not working

Hi @ragibkl it seems logs on fr2 are not working can you check it out thank you

Hi @Tomatoide , thanks for the report.
I think fr2 ran out of disk space. I took down the services, spin it back up, and now it's fine again.
I suspect that the logs are not being cleared at the 10 mins interval as I had hoped, so maybe this is a bigger problem.

@Tomatoide , I've reworked the logs module here: https://github.com/ragibkl/dnsdist-acme/compare/065a430c1156ca50490878d87a111fa3d1c9f3bb...master
Also added table borders.
Deployed to fr1 and fr2. Please check them out and see if that actually works better.

Hi @Tomatoide , I've added the logs endpoint to the status page. https://status.bancuh.com/
Looks like there were some issues still. I've made some fixes to the logs endpoint. Let's see if this will fix it permanently.
The issue was related to how the logs file was consumed.


Unexpected type argument

Hi,
I am getting the following error when trying to use serde_tuple:
error[E0107]: wrong number of type arguments: expected 1, found 2

16 | #[derive(Debug, Serialize_tuple, Deserialize_tuple)]
   |                                  ^^^^^^^^^^^^^^^^^ unexpected type argument

The code that causes this is copy-pasted from the doc:
#[derive(Serialize_tuple, Deserialize_tuple)]
pub struct Foo<'a> {
    bar: &'a str,
    baz: i32
}

but it also happens if the struct is empty.

Thanks for reporting!
I just tested and I'm not able to replicate this with the latest rustcs (stable and nightly) and serde/serde_derive 1.0.92.
Could you provide some more information about your environment (versions for rustc, serde, serde_tuple, etc.) and/or the output of cargo-expand for the failing struct?

It probably has to do with standard library types in the generated code, like Result. Macros are supposed to refer to fully qualified paths only, as the name may mean something different in the caller's code.
struct Result; struct Ok; struct Err;
struct Option; struct Some; struct None;

#[derive(Deserialize_tuple)]
...

@kardeiz  @dtolnay is right, I'm facing the same issue when I have custom-defined Result in the same scope. If there is an easy fix available and you could fix it, it would be really great. Thanks

@kotofond I was in fact using a custom Result type (or rather its E type). Thank you for commenting, I sort of forgot about this bugreport, sorry!

@vojtechkral @kotofond Thanks, and sorry about that! I had forgotten to fully qualify Result and Result::Ok for the Deserialize side of things. I have fixed this and released 0.3.0.


Invalid Version: 2.4.0RC

Debug shown a message, "Invalid Version: 2.4.0RC3" and stopped at first line.
PHP version:  7.0.8
XDebug version:  2.4.0RC3
Adapter version:  19.2

I'm parsing the versions with semver, which wants a version like 2.4.0-RC3. You can fix the issue by updating to 2.4.0 stable

Should be fixed in 948446a93fa2ebd4b10f26056a1d1caa2f2c8542


Sweep the cache before uploading it

Description
Use cargo-sweep along with -Zmtime-on-use for removing unused data from the Travis cache.
cargo-sweep will remove all files that were not used during the current build, so for example old versions of dependencies. To be able to track this accurately it needs cargo/rustc to mark the files it uses during the current build, the -Zmtime-on-use flag is an unstable flag to tell it to do so.
With this implemented the files uploaded to Travis should only be the relevant ones, keeping the cache minimal and actually usable. This will then mean that future builds will only have to build what has changed and run much faster.
Motivation and Context
Fixes #243

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

I wish there were an easy way to look at the cache content, the ones from this branch are still half a gig larger than my testing on travis-ci.com and the test job is taking twice as long. But at least comparing https://travis-ci.org/rustasync/tide/builds/535025048 and https://travis-ci.org/rustasync/tide/builds/535036746 the latter used about half the time for the test job.
Once this is merged I might hit the "delete all caches" button on Travis and see if it creates a smaller cache inline with what I was seeing in the future.


BE district scraper: Avoid output with no data available

is it fine like that? or would it make more sense to output the entries, but with empty NewConfCases value?
I'm not fully sure, what is more reasonable...
resolves #1180

I think this is the way to go, just like the other scraper.

Thank you both!


Compile the tendermint and light-client crates to WASM

See: https://github.com/informalsystems/tendermint-rs/issues/463
This PR also adds a job to the CI to test that both crates can compile to WASM.

[x] Referenced an issue explaining the need for the change
[ ] Updated all relevant documentation in docs
[ ] Updated all code comments where relevant
[ ] Wrote tests
[ ] Updated CHANGELOG.md

I had to disable the only previously enabled acceptance test of the light node CLI for the test suite to pass (). Without this commit, cargo test --all-features --no-fail-fast would fail with:
       Doc-tests tendermint-light-client
    error[E0460]: found possibly newer version of crate `tendermint` which `tendermint_rpc` depends on
     --> /Users/coromac/Informal/Code/Current/tendermint-rs/light-client/src/components/io.rs:7:5
      |
    7 | use tendermint_rpc as rpc;
      |     ^^^^^^^^^^^^^^
      |
      = note: perhaps that crate needs to be recompiled?
      = note: the following crate versions were found:
              crate `tendermint`: /Users/coromac/Informal/Code/Current/tendermint-rs/target/debug/deps/libtendermint.rlib
              crate `tendermint`: /Users/coromac/Informal/Code/Current/tendermint-rs/target/debug/deps/libtendermint-735716e8d731096d.rmeta
              crate `tendermint_rpc`: /Users/coromac/Informal/Code/Current/tendermint-rs/target/debug/deps/libtendermint_rpc-ad41c355acf2752f.rlib

    error: aborting due to previous error

It is currently unclear why this error has appeared, though I suspect it is a bug in Cargo related to features flags (which we now use to disable non WASM-compatible code).

Since the test I had to comment out was just testing that the version number emitted by the light node CLI was correct, I feel like this should not be a blocker to merge this PR, though we will at some point need to figure out how to fix the issue anyhow (or just hope that a Cargo update will resolve it, might open an issue on the Rust bugtracker or post on /r/reddit in the meantime).


Broken links on waste report

Hi
If I visit https://the-lean-crate.github.io/waste/ several of the generated package-detail links are broken.
For example the top package there, tree-sitter-parsers, links to:
https://the-lean-crate.github.io/waste/tree-sitter-parsers
...which 404s.
And the 0.0.5 in "Waste in 0.0.5" links to:
https://the-lean-crate.github.io/waste/tree-sitter-parsers/0.0.5.html
...which also 404s.

Thanks for reporting, I wasn't aware.
Here is what I could find out thus far.

the state on disk works as expected, so running a local dev http server on my local working tree of https://github.com/the-lean-crate/waste can see the pages that aren't present on github.
git status on said working tree revealed that a lot of files weren't actually checked into the git repository
The files missing on GitHub were indeed added to the repocreate mode 100644 web-tree-sitter-sys/0.3.0.html
create mode 100644 web-tree-sitter-sys/0.4.0.html
create mode 100644 web-tree-sitter-sys/0.4.1.html
rewrite web-tree-sitter-sys/index.html (90%)

When pushing this it would send 159025 new objects (changed files, new files, changed trees, new trees)
Note that a clone of the waste repository prior to the commit above would also be missing the files in question

Indeed it looks like that criner fails to properly add new file to the tree. At some point it uses a git2 tree builder to achieve this quickly, maybe something goes wrong there.
For now I'd hold back on spending more time investigating, knowing that once I start using gitoxide for this, it will be reviewed naturally. Until then I hope its enough to work with the fixed report for now, which I can fix occasionally once there is demand.

I just find this awesome project and find the recent versions of my crate are missing. I think it is related to this issue.
https://the-lean-crate.github.io/waste/d1-pac/ only has 0.0.3 to 0.0.16, but I have released 0.0.23 3 days ago.


[apt] Move ntp to recommends

Requested by /u/RussianNeuroMancer).
Currently the BitcoinXT apt package depends on installing ntp. Is there a good reason for this or can we make it optional (recommended)?

If systemd-timesyncd is installed and running (timedatectl status) then as I understand synchronization can be configured via /etc/systemd/timesyncd.conf or via NTP= option in network interface description for networkd (again, if enabled and used).
My point is that there is other options for time synchronization besides ntpd.

Seems like latest package still depend on ntp daemon.

@RussianNeuroMancer Are you able to submit a PR?

I am not developer, I can't write fix for that.

@RussianNeuroMancer Can you try out the .deb package in https://github.com/bitcoinxt/bitcoinxt/issues/154 (first comment)? Does it solve this issue?

Yes, with this deb package ntp can be removed now. Thanks!

Seems like deb package in repository was built with old build.sh, so this change doesn't included in Debian repository.

There has not been a new release since the fix was merged.
It will be included in the next release.

Ok, I see. Thanks for fast answer!

Thank you for running XT :-)


Bond properties change when auto-mapping is applied

Affected versions: remote, standalone
Tested on Ketcher v2.2.1-104-gc7896113
Steps to reproduce:

Launch Ketcher.
Open the reaction
reaction_3.zip
Select the 'Reaction Auto-mapping Tool'.
Select any mode except 'Clear'.
Click the 'OK' button
Select the 'Reaction Auto-mapping Tool' again.
Select another mode except 'Clear'.
Click the 'OK' button.

Expected result:
9. Auto-mapping is applied. The mapping of atoms may change after selecting different modes.
Actual result:
9. Bond properties have been changed, "made/broken" and "order changes" reacting centers appear.

it is not a bug. AAM will use existing atom mapping and due to existing mapping the modes are different (clear, keep, alter)

This is behaviour is correct (approved by @AlexanderSavelyev )


Category - When categories are disabled, 'It's not here' page is seen when unselecting category

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.3.83-10
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Go to staging.new.expensify.com
Go to workspace chat > + > Request money > Manual
Create an expense with a category
On OD as admin, disable all the categorie
As the employee who created the expense in Step 2, go to the expense details page
Click on Category > Unselect the category

Expected Result:
'It's not here' page will not appear
Actual Result:
As the RHP slides away, 'it's not here' page is seen in RHP
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] Windows: Chrome
[x] MacOS: Desktop

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

Windows: Chrome

https://github.com/Expensify/App/assets/78819774/235e3c5e-3371-4a91-b70c-910eedf1c4c3

MacOS: Desktop

View all open jobs on GitHub

Not overdue. Will triage today.

I can reproduce this:
https://github.com/Expensify/App/assets/54866469/95c05122-9a1f-43e6-abbb-99cf518844d4

It's a little funky looking. I'd vote we have someone from the Callstack Wave 6 team take a look when they've got a spare moment. But I don't feel passionately about addressing it either.

Yeah, the more I think about this, I'm falling in the do nothing camp. It's a significant edge case that someone will be turning categories on/off entirely, and then removing categories from existing requests anyway.
Since this doesn't impact the user experience at all, I'm thinking we can just wait and see if any actual customers report this when it's being used (which I feel like they probably won't, because if you aren't looking for it, it isn't really noticeable.)

Going to close this for now. If anyone feels strongly we should change this, happy to re-open and can get callstack on it!


Add ovotech/vulcan

https://ovotech.github.io/vulcan

👍
That's a nice way to learn about a new refined module. :-)

@fthomas 👍 I also opened https://github.com/fthomas/refined/pull/654. :)


"Maintain focus ..." option has no effect in Spyder4

Problem Description
What steps reproduce the problem?

Open Tools > Preferences > Editor > Run Code and disable the "Maintain focus in the Editor after running cells or selections" option.
Execute Run > Run cell (or Crtl + Return)

What is the expected output? What do you see instead?
The cell is executed in the current/dedicated console as expected. However, the focus stays in the editor and does not switch to the console. This is the same behavior as when the "Maintain focus ..." option is enabled, i.e., disabling the option has no apparent effect. This seems to be a Spyder4 specific issue: In previous versions (Spyder3), the focus would switch to the console if the "Maintain focus ..." option was disabled.

Versions

Spyder version: 4.0.1
Python version: 3.6.7
Qt version: 5.12.5
PyQt version: 5.12.3
Operating System name/version: Windows 10

Also happens on an installation with Spyder 4.0.0, Windows 7 and Python 3.7.

Spyder always changes focus to console if running a cell (Ctrl+Return) - enabling "Maintain focus ..." option has no effect. Running selection (F9) stays focus in Editor. Also no effect of "Maintain focus ..." option.
Spyder: 5.2.0
Python 3.8
OS Linux

@pavolgaj, thanks for mentioning that. It seems that option is not working anymore (we don't know when it stopped doing it). I'll try to fix that for our next version (5.2.1) to be released shortly.

@pavolgaj, see PR #16977.

Running selection (F9) works fine, now. It changes or doesn't change focus according to "Maintain focus ..." option. But, the issue with the running cell is still there - it always changes focus to console.

Hi @pavolgaj did you try the changes in the PR metioned by @ccordoba12 (https://github.com/spyder-ide/spyder/pull/16977) ? I checked them and seems like the problem is solved with those changes (the focus in the Editor stays depending on the Maintain focus ... option when running code with the cell/selection funtionality). They will be available with Spyder 5.2.1 (our next release to be done)

Hi @dalthviz ,
yes, I tried the version from this PR. "Running selection" functionality is good. But, I still have problems with running cell (Ctrl+Return).

There are previous changes required to make that option work as expected. Please wait until 5.2.1 is released and if the option is not working for you, then open a new issue.


Outlier detection enforcing on 5xx status codes despite being explicitly configured not to

Bug description
Given the following DestinationRule, configured as per https://archive.istio.io/v1.5/docs/reference/config/networking/destination-rule/:
    outlierDetection:
      baseEjectionTime: 30s
      consecutive5xxErrors: 0
      consecutiveGatewayErrors: 5
      interval: 5s
      maxEjectionPercent: 25
      minHealthPercent: 50

Whilst i have configured is in the proxy-config clusters of the upstream:
        "outlierDetection": {
            "consecutive5xx": 0,
            "interval": "5s",
            "baseEjectionTime": "30s",
            "maxEjectionPercent": 25,
            "enforcingConsecutive5xx": 0,
            "consecutiveGatewayFailure": 5,
            "enforcingConsecutiveGatewayFailure": 100
        },

You can see this service is not producing gateway errors, only 500:

However you can see outliers being active based on this:

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[x] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
Outlier detection to only fire on gateway errors, not 500.
It would also be nice to be able to turn on outlier detection logging at a pod level with an annotation to debug this: https://github.com/istio/istio/issues/25219
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
1.5.7
How was Istio installed?
Helm
Environment where bug was observed (cloud vendor, OS, etc)
GKE 1.15

hmm.. this looks like an Envoy level issue. It is possible that we forgot to tune some magic knob in outlier detection (one not exposed to end user). @lambdai / @lizan / @PiotrSikora thoughts?

@Stono Could you paste the config dump?

You can see this service is not producing gateway errors, only 500:

I am not fully sure how (and whether) gateway error metric is be reported. The idea is gateway error is the TCP connect failure(not even established) between client envoy and server envoy. The connect is not even established, let alone a http request hitting the destination service. So when a gateway error occurs, we don't expect the destination service report a 5xx.

My point is that gateway error could happens w/o the corresponding metric at the dest envoy.
Actually this is important: gateway error is usually considered safe to retry b/c the http request is not received by destination.

@lambdai i'm not sure what you're getting at, there are no gateway errors.
The destination service is return a status code 500 (it has a very low error rate but its there) and these are tripping the envoy outlier detection.
They shouldn't be, because I have configured:
      consecutive5xxErrors: 0
      consecutiveGatewayErrors: 5

Which means only 502, 503 and 504 should be considered, as per the docs

Oh I think I understand, you're saying that the remote destination connection errors aren't being recorded?
I don't know if that's the case, as you can see from my two graphs the outliers certainly follow the 500 codes?

you're saying that the remote destination connection errors aren't being recorded?

That is my mental model. My impression is that gateway error should not be recorded by dest (consumer-gateway) but could be recorded by source envoy with 500.
Now that source envoy accept a http request, source envoy has to report response code :)
Basically for the source envoy in nginx pod, the envoy is rejecting a host from dest (consumer-gateway) by the error of source-envoy to dest-envoy: gateway error or a normal 5xx
But the istio-request-total(the very beginning image of the description) is tracking the errors of http request hitting source-envoy.

to be 100% clear, those 500 codes are coming from consumer-gateway, the application is returning 500s (its a bug in the app that needs fixing)

DetectorHostMonitorImpl::putResultNoLocalExternalSplit reveals the fact that the response code to downstream request(mapping to istio_request_total) is a source of outlier detection signal, BUT it's not the only one.
Take a real world example: if the retry does hide an destination workload failure, the response code is 200, but the outlier detection of that failing workload is accounted.
What's more, the host failure is normalized to a fake http response code from destination workload (consumer-gateway sidecar envoy is expected in this case), but that response code is not returned by destination envoy. It could be a tcp connect failure.
tl;dr
Both istio_request_totals from source sidecar envoy and from dest sidecar envoy is populate to outlier detector. But even the union amount of the tracked requests could be less than outlier detector's samples

I'm not really following, but I think you're saying they are hidden TCP failures that are contributing to the envoy outlier detection?
Also what do you mean fake http response code ?
How do we prove that?

FYI i've removed two variables:

Rolled back to 1.5.6
Removed http2 envoyFilter

No change in the amount of outlier active

I've finally got outlier detection logs working with some hacking, here are a few samples:
{"type":"SUCCESS_RATE","cluster_name":"outbound|80||app.consumer-gateway.svc.cluster.local","upstream_url":"<IP_ADDRESS>:8305","action":"EJECT","num_ejections":1,"enforced":true,"eject_success_rate_event":{"host_success_rate":99,"cluster_average_success_rate":99,"cluster_success_rate_ejection_threshold":99},"timestamp":"2020-07-14T09:21:38.530Z"}
{"type":"CONSECUTIVE_5XX","cluster_name":"outbound|80||app.consumer-gateway.svc.cluster.local","upstream_url":"<IP_ADDRESS>:8305","action":"UNEJECT","num_ejections":1,"enforced":false,"timestamp":"2020-07-14T09:22:08.533Z","secs_since_last_action":"30"}
{"type":"SUCCESS_RATE","cluster_name":"outbound|80||app.consumer-gateway.svc.cluster.local","upstream_url":"<IP_ADDRESS>:8305","action":"EJECT","num_ejections":1,"enforced":true,"eject_success_rate_event":{"host_success_rate":99,"cluster_average_success_rate":99,"cluster_success_rate_ejection_threshold":99},"timestamp":"2020-07-14T09:22:17.709Z"}
{"type":"CONSECUTIVE_5XX","cluster_name":"outbound|80||app.consumer-gateway.svc.cluster.local","upstream_url":"<IP_ADDRESS>:8305","action":"UNEJECT","num_ejections":1,"enforced":false,"timestamp":"2020-07-14T09:22:47.713Z","secs_since_last_action":"30"}
{"type":"SUCCESS_RATE","cluster_name":"outbound|80||app.consumer-gateway.svc.cluster.local","upstream_url":"<IP_ADDRESS>:8305","action":"EJECT","num_ejections":1,"enforced":true,"eject_success_rate_event":{"host_success_rate":99,"cluster_average_success_rate":99,"cluster_success_rate_ejection_threshold":99},"timestamp":"2020-07-14T09:24:51.298Z"}
{"type":"SUCCESS_RATE","cluster_name":"outbound|80||app.consumer-gateway.svc.cluster.local","upstream_url":"<IP_ADDRESS>:8305","action":"EJECT","num_ejections":1,"enforced":true,"eject_success_rate_event":{"host_success_rate":99,"cluster_average_success_rate":99,"cluster_success_rate_ejection_threshold":99},"timestamp":"2020-07-14T09:24:53.546Z"}
{"type":"CONSECUTIVE_5XX","cluster_name":"outbound|80||app.consumer-gateway.svc.cluster.local","upstream_url":"<IP_ADDRESS>:8305","action":"UNEJECT","num_ejections":1,"enforced":false,"timestamp":"2020-07-14T09:25:23.548Z","secs_since_last_action":"30"}
{"type":"CONSECUTIVE_5XX","cluster_name":"outbound|80||app.consumer-gateway.svc.cluster.local","upstream_url":"<IP_ADDRESS>:8305","action":"UNEJECT","num_ejections":1,"enforced":false,"timestamp":"2020-07-14T09:25:21.301Z","secs_since_last_action":"30"}

And this is configured with:
      outlierDetection:
        baseEjectionTime: 30s
        consecutive5xxErrors: 0
        consecutiveGatewayErrors: 5
        interval: 5s
        maxEjectionPercent: 25
        minHealthPercent: 50

Which translates to a cluster config of:
        "outlierDetection": {
            "consecutive5xx": 0,
            "interval": "5s",
            "baseEjectionTime": "30s",
            "maxEjectionPercent": 25,
            "enforcingConsecutive5xx": 0,
            "consecutiveGatewayFailure": 5,
            "enforcingConsecutiveGatewayFailure": 100
        }

I've noticed the CONSECUTIVE_5XX have enforced=false which i presume means they're just reporting? but then there is a SUCCESS_RATE which being enforced.  There are no CONSECUTIVE_GATEWAY_FAILURE being logged yet.

Seems like you're seeing outlier detection evictions due to the success rate std dev calculations, you should be able to disable that by setting enforcing_success_rate to 0.
This is a different detector than the consecutive 5xx one: instead of tracking how many 5xx it sees in a row, it compares the number of 5xx errors of a specific host vs all the other hosts and eject it if it falls outside of the configured std dev range.

OK so from an Istio wrapping envoy perspective, it feels invalid to have SUCCESS_RATE calculations enabled under the hood (as it's counter intuitive to the current configuration options of consecutive5xx and consecutiveGatewayFailure

I agree. We should enable success rate based outlier detection. PR to fix it https://github.com/istio/istio/pull/25534

@lambdai @ramaraochavali @howardjohn please can we reopen this until the 1.5 and 1.6 cherry-picks are in?
https://github.com/istio/istio/issues/25543
https://github.com/istio/istio/issues/25542

why is the success rate detector even active when the consecutive gateway error detector is explicitly set?

The default is to on (enforcing 100%) when you enable outlier detection by setting other detectors -  Should the default be off like enforcing_failure_percentage - may be yes. @snowp is there any specific reason on why it is enabled by default?

https://github.com/istio/istio/pull/25566 - 1.5
https://github.com/istio/istio/pull/25567 - 1.6

PRs to 1.5 and 1.6 are merged. So closing this

@ramaraochavali thank you for seeing this through. :)