Optimize semaphore acquisition in GpuShuffledHashJoinExec

Closes https://github.com/NVIDIA/spark-rapids/issues/4539.
This PR adds an optimization for the shuffled hash join where the semaphore is not taken after the build side is fetched to the host (since we attempt to keep the build side on the host while we load the first batch from the stream side).
After the first stream batch is loaded, the semaphore has been acquired. We then proceed to bring the build batch to the GPU.
This code falls back to the old behavior in cases where batches are not serialized (our input is not a shuffle) and when the streams are empty.
It is in draft mode because I need to run more testing in NDS. I don't think the case where I need to loop over the build batch multiple times has been hit with my runs so far (other than unit tests), so I need to figure out a way to trigger that case.

So just to be clear this optimization can never work with UCX right?

So just to be clear this optimization can never work with UCX right?

Great point. I have missed a case where we need to ignore the config when UCX is turned on and we have compression on. If we don't do this, the fallback case right now doesn't handle compressed batches from the shuffle.

I added a commit that I think addresses many of the points, enough has changed that I think this needs another pass.
One comment from Jason wasn't addressed for sure:

Do we really need a buffered iterator on the stream-side batch? We just need to call hasNext which will grab the semaphore but I don't see the need for us to call next on the stream-side iterator. That also side-steps another bug here where we create a closeable buffered iterator but pass it to code that will never call close on it since it's just a regular iterator to that code.

We need something to hold on to that first stream batch. That doJoin pays no attention to this, so if there is an exception before that the first batch is popped, then the batch will be leaked.
I think one ugly option is to attach the closeable iterator to the task completion logic. I think we discussed doing this, but I am confirming that's the approach or if there's something better.

build

Looking into the test failures.

build

@jlowe @revans2 could you take another look when you have a chance?

@revans2 I replied to your comment just now in the original request, but adding a link here so we can continue if there's more I need to look into:

Still would like to know the answer to this. The things in the iterator need to be closed and can potentially be very large.

https://github.com/NVIDIA/spark-rapids/pull/4588#discussion_r799836101

build

Ok I have a bug with safeMap, I thought I had built this before I pushed it last, but obviously I didn't. I am going to retest the patch against real queries to be sure.

build

@jlowe @revans2 ok apologies. Now this should be ready.


Auto monitor celery tasks with environment support

Problem Statement
Currently monitor names are key names from celery beat schedule. Is it possible to append or prepend environment name so that we can differentiate tasks according to environment?
Solution Brainstorm
We can append or prepend environment name to monitor_name variable inside _patch_celery_beat_tasks function.

Hey @aemr3 !
Thanks for bringing this up.
Monitor check ins add the environment of your Sentry setup automatically to the check in.
But I just tried it and for me it was also not possible to filter the list of Cron Monitors by environment and see the check in from a environment that is not the default one (default is production)
I have asked the persons in the product team why this is happening.

I heard back from the API persons. This is a bug in ingesting the checkins. They will have a fix out later this week! (fyi @aemr3 )

Hey @antonpirker, thank you for looking into this.

This is fixed now.


Readme updates, plus bail out early when the gist fails to fetch

Hi there! I had to take a couple extra steps before this would work to update my gist, so I wanted to document them in the readme in case you want to keep the changes:

Forks have their Actions disabled, so the person who made the fork needs to reenable Actions + the spotify-box Workflow
I put my secrets as Environment secrets on my fork, not sure if this was right. But it meant the Workflow didn't have access to the secrets I had added till I specified what environment to use in the Action.
When the gist fails to fetch, we were continuing on, but that resulted in an error because something was undefined, so I just had it return early.
I updated the error message to include the gist ID when it fails to fetch, which was helpful for me to see that my secrets weren't getting loaded correctly because my gist ID was coming up blank.
Unless someone edits a file in their fork, the workflow won't run till you manually run it.

This pr is very helpful, thanks for your contribution!


Fullscreen Loading Videos

Hi
I saw this was previously an issue but was fixed but.....
After I add a blank for the loading then add the fullscreen one with Append
it just adds it with an 01 at the end and no option to choose eg 3 playfield.
I am currently renaming the second one and adding (SCREEN3) in my case but thought it would offer me a location
Thanks
Brent

I think there is a refresh bug in the list. Close the dialog or press reload, then the second asset appears. I've used this feature the last day, but noted this issue when used the first time.

My second asset appears ok - just with an 01

I have to rename that file and add (SCREEN3) to the end for it to work
I thought it would be like pinup popper media where it asks me to assign a location

I've re-read your initial message and didn't understand this message:

After I add a blank for the loading then add the fullscreen one with Append

I assume you've added a blank screen manually? The special behaviour of the loading screen view in the studio is that you can download a fullscreen loading video and press the the "Fullscreen" button. This will add a blank video so that the fullscreen loading video is actually played in fullscreen.
The "fullscreen" button is only available for the loading view and only enabled where there is one video without a "SCREEN" name.


Option to print metrics instead of sending to statsd.

A simple option --stdout for if you just want to see what the daemon is going to do without using nc or actually writing to statsd.
I didn't add any tests this time because it looked like it would just be mocking which object is constructed which doesn't seem that useful unless everything else is all very well covered.  Please let me know if you want me to add some.

Thank you for your pull request!
It seems to be a useful addition that we forgot to add ourselves. ;)
I'll ask Thijs to merge it tomorrow.

hi @bnkr thanks for your pull request. I want to merge this but after some changes.
--stdout doesn't resemble the change you're proposing, which would be when using stdout mysql-statsd would output and still send to statsd, but now it would only output(and can thus be misleading).
What I will do is refactor a bit, and open a pull request on your branch. :)

I've created a release with your updates, you can find them on pypi here:
https://pypi.python.org/pypi/mysql-statsd


feat(cross chain transfer): implement cross chain transfer page

add new page
add styles
remove unused styles

Reason: feat(cross chain transfer): implement cross chain transfer page
Closes [issue link]
Changes made (preferably with images/screenshots):

add new page
add styles
remove unused styles

Check off the following:

[ ] I have reviewed my changes and run the appropriate tests.
[ ] I have have run rush change to add the appropriate change logs.
[ ] I have added/edited docs.
[ ] I have added tutorials.
[ ] I have double checked and DEFINITELY added docs.

Right now it's just a copy from the old to the new page, right? I feel like we need to setup the page in such as way that it's easy to understand for everyone what exactly you need to fill in those fields, and we need to consider if all fields should always be visible etc. We have the chance now to set up the perfect UI for people who are not 100% familiar with all the complicated internals atm.

Merged PR. The common components created are valuable for other PR's


fix(paeckchen-core): external module bundling

external modules should not be resolved against browser-resolve

Coverage remained the same at 100.0% when pulling e4116d797dfb6da772f78d5372fc4e20f8e055b9 on core/externals into 27bf9034e30a95e877e02b2a0b8319932e7780ad on master.

Coverage remained the same at 100.0% when pulling ed4ec8a3f91bedfa7c400bfcf062bf857795c8dd on core/externals into 781b90a795b20e97b7151566632c8700404251da on master.


Store visibility status of sidebar menus in localstorage

Closes #51. The example only talked about the userlist, but keeping with the title, I did both that and the network list, split into separate commits if the latter isn't needed/wanted.

@PolarizedIons Do you want to also look into making network hiding work on desktop? Because the button is currently hidden and you can't hide it.

Alright, I first tried just doing the same as on mobile, but that moves part of the channel off of the screen, so I opted for just shrinking the channel when it's open, and expanding it when closed. The shrinking didn't look very good on mobile, so I kept that the same.
I also noticed a bug with how I was previously detecting the userlist opening (via the 'transitionend' event) when dragging: when you drag the menu open entirely (vs. just flicking it open) that event never gets triggered, so I moved that storage part into libs/slideout.js.
I also added a bugfix I noticed a lot while testing - the userlist opening/closing when going from "desktop" to "mobile" widths. Let me know if I should remove this.

So, I did a bit of investigating, and I've at least found how to get the 2 to show at the same time. If you move the network list toggle check that's on line 44-48, into init.js after openCorrectChannel, and you put the $("#loading").remove(); straight after it, then the loading screen is remove basically at the same time as the 2 sidebars are expanded.
With your code:

With this change:

I've put the changes up at this commit if you want to try them out. I think this would be a good addition.
It might be nice to make them both display none, then show them if we want to, then make them display and hide the loading screen at the same time, because then you won't get the animation on the first load, and all you'll see is the loading screen disappear and the page behind appear. I think it'll be much nicer. If I have time tomorrow I might investigate that. It might need some z-index changes as well.

Hey, @PolarizedIons, would you have any time to address the comments we left, and rebase/fix conflicts?

Closing this, superseded by @xPaw's #2235. Thanks for starting this, @PolarizedIons!! 🙏


Update README.rst

Update README.rst

h

I looked it up in the dictionary and do not see how this is an improvement.  https://blog.domenic.me/hacktoberfest/

Codecov Report

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

@@           Coverage Diff           @@
##           master     #890   +/-   ##
=======================================
  Coverage   73.45%   73.45%
=======================================
  Files          51       51
  Lines        4864     4864
  Branches      563      563
=======================================
  Hits         3573     3573
  Misses       1135     1135
  Partials      156      156

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 c0f1370...dc7f0a7. Read the comment docs.

Yes this change doesn't really add or clarify anything.


Release Google.Cloud.PubSub.V1 version 3.2.0

Changes in this release:
New features

Exactly once delivery (commit e93c4d3)
Add support for exactly once subscription (commit 46d8b0d)

Ignore the conventional commits failure here, btw - that's just because our release commits aren't conventional commits. If that turns out to be a real problem, we can change it, but I'm hoping it won't...

Ignore the conventional commits failure here, btw - that's just because our release commits aren't conventional commits. If that turns out to be a real problem, we can change it, but I'm hoping it won't...

Sure Jon.

Ignore the conventional commits failure here, btw - that's just because our release commits aren't conventional commits. If that turns out to be a real problem, we can change it, but I'm hoping it won't...

Sure Jon.

Created release for Google.Cloud.PubSub.V1-3.2.0


[coap] remove otCoapMessageSetMessageId()

Message ID is managed by CoAP agent. Allowing user setting it may result
in invalid usage. This PR removes this API and adds a new API to
initialize CoAP response message.

@LuDuda any comments?


Help needed?

Hey @m110 ,
I have been enjoying your content and your course (so far 😉 )! At work, we are on the journey to an event-driven-architecture and are leveraging SQS in specific quite a bit. We would really like to test out watermill as the backbone for this architecture but this package seems a bit "underdeveloped" (no offense!). Do you have concrete plans to maintain and support it or is this more something the community should take care of? I am just curious if you are looking for help to maintain/develop this package to bring it to a stable release? Or do you suggest to better fork and maintain in private?
Greetings from Berlin!

Hi @bastiankoetsier! Pls check this PR https://github.com/ThreeDotsLabs/watermill-amazonsqs/pull/14#issuecomment-1906021524
I've been using it for a while and works pretty good for my use case

@Mariscal6 thanks for the response! I saw the PR but was a bit discouraged/curious about the plans of this package. Hence my question for a "stable"/maintained release of it.

Hey @bastiankoetsier! We definitely want to support this package in the near future. It would be great to hear feedback from people who use SQS/SNS on production, as we currently don't. :)

Releasing a stable v1.0.0 is one of our goals for Q1. We're also happy to review contributions (I'm sorry if it takes long - please ping us if we don't reply right away!)

@roblaszczak is working on v1.0 right now, so I'm closing the issue. :)


[core] Add AnyStateConfig

This PR adds AnyStateConfig which can be used to type persisted state as the document mentioned.

Great, thank you! Can you add a quick changeset by running yarn changeset?
This will be a patch change. Your message can be something like:

Added the AnyStateConfig type, which represents any StateConfig<...>.


Web Editor not working (403 error)

When I write /lp editor there is some warnings in console, editor not working.
[LP] Preparing a new editor session. Please wait...
[13:20:03 WARN]: java.lang.RuntimeException: Request was unsuccessful: 403 -
[13:20:03 WARN]:        at me.lucko.luckperms.common.web.AbstractHttpClient.makeHttpRequest(AbstractHttpClient.java
:50)
[13:20:03 WARN]:        at me.lucko.luckperms.common.web.BytebinClient.makeHttpRequest(BytebinClient.java:69)
[13:20:03 WARN]:        at me.lucko.luckperms.common.web.BytebinClient.postContent(BytebinClient.java:94)
[13:20:03 WARN]:        at me.lucko.luckperms.common.web.WebEditor.post(WebEditor.java:138)
[13:20:03 WARN]:        at me.lucko.luckperms.common.commands.misc.EditorCommand.execute(EditorCommand.java:132)
[13:20:03 WARN]:        at me.lucko.luckperms.common.command.abstraction.SingleCommand.execute(SingleCommand.java:5
0)
[13:20:03 WARN]:        at me.lucko.luckperms.common.command.abstraction.SingleCommand.execute(SingleCommand.java:4
2)
[13:20:03 WARN]:        at me.lucko.luckperms.common.command.CommandManager.execute(CommandManager.java:202)
[13:20:03 WARN]:        at me.lucko.luckperms.common.command.CommandManager.lambda$executeCommand$1(CommandManager.
java:143)
[13:20:03 WARN]:        at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:
1700)
[13:20:03 WARN]:        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135
)
[13:20:03 WARN]:        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635
)
[13:20:03 WARN]:        at java.base/java.lang.Thread.run(Thread.java:844)

HTTP code 403 means access is forbidden which likely means your connection to the bytebin service has been blocked by Cloudflare for some reason. Have you been able to access the web editor from this server before?

I just installed luckperms today

What version of LP?

v5.0.140


Update allowselfservicepurchase-powershell.md

Updated to add PowerShell version requirement.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@cmcatee-MSFT Please merge this PR. Thanks.

Gentle reminder @cmcatee-MSFT Please merge this PR. Thanks

@cmcatee-MSFT are you able to take a look at this? :)

@snickler I've verified with the product group that the addendum is OK to add. Thanks!


Add an option removeOnly

Thank you for the plugin :+1:
It would be nice to see an option removeOnly.
Remove all comments marked as for example /*- */ with the ability to change it.
/*- Remove */

/* Leave */

Mark all comment with ! just to remove a few is a little bit annoying.

I think I would prefer a user-defined function, remove where you return true to remove and false to keep. Would appreciate a pull request for this, if not I'll have a look when I can. :+1:

Ok, I will try.

remove: false Keep all regular comments
removeAll Remove all comments marked as important
But what if I want to keep some comments marked as important? :smile:
For example /*! normalize.css */

A user supplied function would override those options.

It would be better that you implement it when you find the time :wink:

Do you mean something like this?
config
remove: function(comment) { return comment.indexOf('@') == 0; }

commentRemover.js
CommentRemover.prototype.canRemove = function (comment) {
    var remove = this.options.remove;
    if (remove) {
        return remove(comment);
    } else {
        var isImportant = comment.indexOf('!') === 0;
        if (!isImportant && comment.indexOf('#') !== 0) {
            return true;
        } else if (isImportant) {
            if (this.options.removeAll || this._hasFirst) {
                return true;
            } else if (this.options.removeAllButFirst && !this._hasFirst) {
                this._hasFirst = true;
                return false;
            }
        }
    }
};

Yep. It would need tests too.

https://github.com/ben-eb/postcss-discard-comments/commit/14abc58da293ba6fdc52a5830b049a25378c0272


feat: rewrite from scratch [BREAKING CHANGES]

The underlying Fetch implementation is rewritten from scratch, as the the previously used implementation (fetch-h2) has serious long-standing issues and its maintainer is unresponsive and doesn't seem to care.
BREAKING CHANGE: The exposed API, options etc have been aligned with node-fetch where possible. Due to the major
changes there are numerous breaking changes both in the API and the options.
Related Issues
fixes #20, #27, #32, #81
TODOs:

[x] improve doc: add more examples, describe breaking changes/migration tips, etc (README.md)
[x] improve code coverage, add more tests

as far as I can see,
index.d.ts exports Request, Response etc, but
index.js doesn't.
eg, if I want to use Response, I need to to:
const Response = require('@adobe/helix-fetch/request/response.js');

maybe it would be easier to:
const { Response } = require('@adobe/helix-fetch');

If Request, Response should not be used directly, they shouldn't be exported in index.d.ts.
(but it would be great, if we could use it in the unified actions, instead of node-fetch)

sure.  Request, Response, Headers` etc are already exported:
const { Request, Response } = require('@adobe/helix-fetch');

as far as I can see,
index.d.ts exports Request, Response etc, but
index.js doesn't.
eg, if I want to use Response, I need to to:
const Response = require('@adobe/helix-fetch/request/response.js');

maybe it would be easier to:
const { Response } = require('@adobe/helix-fetch');

If Request, Response should not be used directly, they shouldn't be exported in index.d.ts.
(but it would be great, if we could use it in the unified actions, instead of node-fetch)

sure.  Request, Response, Headers` etc are already exported:
const { Request, Response } = require('@adobe/helix-fetch');

sure. Request, Response, Headers etc are already exported:
const { Request, Response } = require('@adobe/helix-fetch');

ah sorry, I missed it when looking just at the diff:
https://github.com/adobe/helix-fetch/blob/3dbef15ce8c1d1ab45ad17dc216d5842bec01e02/src/fetch/index.js#L395

sure. Request, Response, Headers etc are already exported:
const { Request, Response } = require('@adobe/helix-fetch');

ah sorry, I missed it when looking just at the diff:
https://github.com/adobe/helix-fetch/blob/3dbef15ce8c1d1ab45ad17dc216d5842bec01e02/src/fetch/index.js#L395


Implement static if creation operator

https://github.com/Reactive-Extensions/RxJS/blob/master/doc/api/core/operators/if.md

Closed via https://github.com/ReactiveX/RxJS/pull/1348.


Table with compound expansion - text in first cell shifts position

When I hover over the Branches button in one of the last two rows, the text in the first cell will change position.
Steps to reproduce:

Resize your window so that the text in the table cells wrap
Hover over the Branches button (i.e. not one that is active)

Result: The text in the first cell will shift position as shown below.

Hi @jgiardino is this a blocking bug?

Adding @mcoker to this. I'm not sure what we consider blocking bugs. It doesn't break functionality. But if this is a component that is being requested by a product team, I would bump it up in priority, given the possible visibility of this.

Agreed, it’s just a visual bug and only impacts compound expansion, so it’s not blocking, but we should sort it out after the release.

:tada: This issue has been resolved in version 2.6.13 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add skill descriptions

PoE has so many skills that it's tough to remember exactly what each one does. Would be nice if, at the least, the modifiers and skill effects could be listed with the skill tooltip (e.g., 'adds 2-4 cold damage')

Duplicates https://github.com/Openarl/PathOfBuilding/issues/487


Return the array key when appending a new item

Is it a good idea to return the array key when appending a new item to it?
Example:
var arr=[]

var key = arr.append(123)#0

var key1 = arr.append(321)#1

What would be the use case? Does any language do this on their append or push_back methods?
I don't see much point in returning this value which would always be the size of the array minus 1, i.e the index of the last element. If you need it, you can just get arr.size() - 1.
To return this value, append() would actually need to call this too, this index information is not readily available to return. (See Array::push_back() in core/array.cpp). And the Vector<T>::push_back() it calls from core/vector.h already returns a boolean value to indicate failure or success, so it can't return the index.

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!


Sample using Conductor and a single Activity architecture

Hi everyone,
I decided to try making a sample that only uses a single Activity architecture using the Conductor library.
I've put the branch up here and I'd really appreciate any feedback!
It turned out to not be too difficult, the Activities and Fragments became Controllers and everything else stayed the same. I had to do some interesting code around getting the DrawerLayout working and constantly changing the ActionBar to have new stuff in it.
The main thing left to do is that it broke a few of the Espresso tests and also made most of them super flakey.
The problem is that the test no longer knows that it needs to wait while the next Controller loads (I guess Espresso is usually aware of Activity transitions and I no longer have that crutch).  I had a look at using IdlingResource to solve this, but I'm not experienced with Conductor or Espresso, I'll keep working on it.
Also, the hermetic UI tests of individual Activities will probably never work hermetically since I don't think I can jump into a specific Controller like you can with Activities, you need to navigate there.

Hey Greg,
I've labelled this as request, although it's not actually a request, since you already finished it.
It's a great example of what we wanted the community to do with this project!
Before adding it to the list of external samples I'd ask you to:

Solve UI tests
Explain in the README what the library does and what design decisions you made

I don't think you need Idling Resources for that, unless you're doing things outside of the main thread.

Cool ok! I'll try to find some time soon to finish it off and polish it a little / add more documentation.

Hi Jose,
I managed to spend some time on it today.
The Espresso tests are all working now, mostly through small refactorings in the Espresso methods that were being called and by turning off the animations on the device I was using for the testing. The only weird thing I had to do in the end was use the IdlingResource to track whether the Navigation Drawer had finished animating open/closed (explained in the README).
I also polished the code a bit more and updated the README to explain how the architecture works.
It's all been pushed to this branch.
Let me know if you have any feedback!

Hey greg, looks good!
Have you used cloc to take the LOC?

Yep, it's in the README

Cool, adding it to the list!

Done! Thanks Greg!
https://github.com/googlesamples/android-architecture/blob/master/README.md

Great! Thanks Jose!


Fix very minor typos

#hacktoberfest

Looks like the correct spelling of fulfill is based on geography; I'm in the US so I'll keep the American spelling :)
Thanks for the other typo catch! Merged ✨


New logger rebased

TODO:

[x] increased message size field to 16 bits
[x] multi-instance topics (ongoing)
[x] update FlightPlot and jMAVlib (ongoing)
[ ] add parameter which lists topics to be logged with per-topic rates
[ ] reduce topic sizes or allow logging a subset of fields
[ ] improve polling logic (eliminate usleep? perhaps a decimation factor per/topic)
[ ] nuttx_next_cmake test; might shed light on buffer overflows
[ ] determine why SD card write blocks longer than fsync (test with nuttx_next)
[ ] fix ROS
[ ] SITL test
[ ] higher rate for EKF2 replay?

previous conversation at https://github.com/PX4/Firmware/pull/4117

@tumbili This seems to work properly running VTOL missions in SITL with the changes I made in commit 0b747fe   So it hasn't broken the publication of MC and FW virtual attitude setpoints.
But I don't know why there were multiple #topics in the message defs before.

@LorenzMeier Travis is failing the fmu-v2_default build on a flash overrun. Any suggestions on why, and how to fix that?

As part of this upgrade has there been any consideration given to using the sensor timestamps from when the data is read in the driver? Currently we are throwing that (more accurate) timestamp away and logging only the time when the sdlog2 thread got around to reading the next batch of uORB topics.
If we're trying to look at high performance / fast transient system response this timing approach seems quite poor.

@NaterGator I agree with that and I think this is the plan.

@NaterGator That is the main point of the new logger. Take a look at the code: e.g. https://github.com/PX4/Firmware/blob/newLogger/msg/sensor_gyro.msg#L1
Timestamps are now in every message, and it is now possible to resample to a uniformly sampled time series to do Fourier analysis.

@kd0aij timestamps in every message sounds much much better.

Impulse response analysis using 250Hz gyro and 125Hz rate setpoint data. Roll control latency is only 32 msec if there are no errors in the analysis:

@kd0aij @dagar @LorenzMeier I was playing around with the new logger and find it great! However, it would be nice if we can allow to specify which entries of a message to be logged, rather than just logging the entire message. Some of the messages have become really large (e.g. vehicle attitude) and in order to keep logging rate relatively low you have to reduce the topic logging interval which in turn will make analysis more difficult (imagine controller tuning on a racer).
So I was thinking of the following:
In the message folder we could have a text file which specifies which field of each topic should be logged. The python script which does orb topic header auto-generation would look into this file and sort the data struct such that the message fields which are supposed to be logged come first. Doing so will allow us in the logger to just copy a certain length of the struct into the log buffer (right now the entire struct is just copied into the log  buffer https://github.com/PX4/Firmware/pull/4197/files#diff-64b21add574f1f3f059c2abc18eae7d6R358).
Is this a good approach or do you have something better in mind?

It would be nice if we didn't need to choose, but that's probably not realistic. What about some kind of annotation in the actual msg definition?

@dagar Totally fine with me! I was only thinking that changing the actual message format does not make a lot of sense.  I find a text file quite handy because then you don't need to go through every message. And e.g. if this text file does not exist we could log everything. It's really up to us how we implement it in the end.
Given that you invested quite some time in the auto-generation is that something you might have time to look at?

@dagar My main goal would be to have the ability to log parts of a uORB message, nothing more.

I'd hope that we could select the topics to be logged and the rates at which to log them at runtime. It would then be easier to use the limited bandwidth for different purposes without having to recompile/reflash.

From a design standpoint, the overly long topics should probably be broken up into smaller topics.

We have @againagainst and @DrTon to thank for autogeneration. I just resurrected their work from an older PR that was beyond rebasing. Other than higher quality logs for analysis my interest in this was largely not wanting to specify what to log in sdlog2 boilerplate (laziness).
Could we just log everything by default and blacklist entire messages or fields within messages as needed? Sometimes things that aren't obvious become very important when reviewing data after a crash.

Logging everything is not an option unless we want to increase the number of allowed file descriptors. But messages like ekf2_replay probably should never be in the default list.

@dagar I don't really mind how we realize it, I just want to be able to specify which fields to be logged. My idea was to do this as efficient as possible, e.g. I didn't want to go through the orb struct in the logger and check for which fields need to be logged. But in case you have a very good idea that would also be fine.

My obvious first choice would be to fix underlying issues so the logging system is not artificially IO constrained. Once we've exhausted that option could we describe the terse logging structure on a logging config file stored on / read from the SD card?
During initial development it will probably be somewhat tedious to setup the configuration, but we should be able to plumb it up to a UI where you sync with the AP to get a list of log topics and fields. In the UI you would just check boxes next to topics you want to slice up, check off each field you want to be logged. Write the slicing configuration at the head of each logfile so the parsers can read the log properly.

@NaterGator Yes, sounds good. My problem at the moment is that I need to generate log files for ekf2 replay. It's very important that we have no dropouts so on e.g. the Pixhawk we need to constrain our data rate with which we write on the SD card. Therefore, logging all topics is IMO not possible (unless someone does something magic which allows us to log much faster). So what we have done until now was to disable logging for most of the other topics when we record a replay log. However, it would be much nicer if you could still log other fields from other topics with a high rate.

@tumbili the SDIO interface (at spec) is capable of writing at about 6 MB/s. If my memory serves me correctly I believe we're actually getting something closer to 10s of KB/s write performance, so we should have a lot of room for improvement.

@NaterGator Our problem is that the file write() can block for 250msec or longer, so to achieve 6MB/sec throughput we would need to buffer at least 1.5MB. Perf counters around the write and fsync show that the write is consistently blocking longer than the fsync, which might indicate a problem with the driver (maybe write is doing a sync every time?)

@kd0aij , @NaterGator
Please keep in mind the overhead of the FAT file system.

@davids5 yes, the FAT filesystem is adding overhead, but we're orders of magnitude away from where we should be. The issue we're experiencing is not going be the FAT filesystem overhead unless the NuttX FAT implementation is egregiously bad and nobody has complained yet (which seems dubious).

@dagar @davids5 What would it take to merge the newLogger branch with nuttx_next_cmake? The diff is huge going either direction...

Let's get them both synced with up master first and then try. I'll rebase newLogger.

px4fmu-v2 is out of flash after a rebase. Commenting out the mpu9250 driver for now.

newLogger rebased on master
Previous version is here incase I broke something - https://github.com/dagar/Firmware/tree/newLogger_orig

Does anyone have a clue how to fix ROS?
/sitl/catkin_ws/src/Firmware/src/platforms/ros/nodes/attitude_estimator/attitude_estimator.cpp:98:12:
error: 'px4::vehicle_attitude' has no member named 'timestamp'
  msg_v_att.timestamp = px4::get_time_micros();
            ^

@dagar Something went wrong with your rebase; sdlog2 replaced logger

@kd0aij was it one of the SITL configs? They weren't updated.
Try now.

One more tuning session for attitude control mode on the S250AQ with new logger. Raised MC_ROLL_P and MC_PITCH_P to 10.0. Response was a bit twitchy, with some oscillations, but latency is only 88msec:

Reducing the pitch and roll P gains to 8.0 eliminated the oscillations and increased the latency to about 100msec. Still very low latency for tilt control:

@dagar It was the fmu-v4 config. I'll check that one.

there's something wrong with my checkout of the branch: the fmu-v4 config is wrong (sdlog2 instead of logger), and I show a different sha for the Tools/genmsg submodule:
On branch newLogger
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   Tools/genmsg (new commits)
	modified:   src/lib/ecl (new commits)

no changes added to commit (use "git add" and/or "git commit -a")
04:48:47 {newLogger} ~/git/kd0aij/PX4/secondPX4/Firmware$ git submodule status
 4c69d3e31d615ac065e5d51ecfc73740f4d908cf NuttX (nuttx-6.27-340-g4c69d3e)
 26a86f04bcec0018af6652b3ddd3f680e6e3fa2a Tools/gencpp (0.4.6-47-g26a86f0)
+72f0383f0e6a489214c51802ae12d6e271b1e454 Tools/genmsg (0.3.6-143-g72f0383)
 9155c8f955e05c969bcd932b705b98d98845f228 Tools/jMAVSim (remotes/origin/HEAD)
 7c1ae0c6ee71195f51cd22bd75b33a7f19872eb4 Tools/sitl_gazebo (remotes/origin/HEAD)
 ee19a96312a7323ad05ae7597c5e96e510ec46ac cmake/cmake_hexagon (ee19a96)
 bf251caef3dbf610e5152115a2d81e00e54ab7e7 mavlink/include/mavlink/v1.0 (heads/master)
 d6ef668f4564e1c158910c52df7d71114bd2ca4e src/lib/DriverFramework (remotes/origin/HEAD)
+f86ef3478219b4b1c31e17b8f308df4b69eda2f7 src/lib/ecl (heads/master-40-gf86ef34)
 07fba8322a16cb2dac47e6a8ac7d21ec346313ff src/lib/matrix (heads/master)
 702f6f05608885d3be993edb01394212bd2dade1 src/modules/uavcan/libuavcan (v1.0.0rc2-11-g702f6f0)
 c99458533a9b4c743ed51537e25989ea55944908 unittests/googletest (release-1.7.0)

It's probably easier to just nuke it.
git fetch --all
git reset --hard upstream/newLogger  # depending on your configuration
rm -rf build_*
git submodules deinit -f .
git submodule update --init --recursive
make px4fmu-v4_default

Thanks. The "reset --hard" fixed the stale config problem.
Was the genmsg submodule supposed to change with the rebase though?

Ah good catch. There's my daily dose of submodule hate.

@dagar Seems to be flying OK after the rebase

@kd0aij that's great. What do you see as the next steps? Can we get it cleaned up and working to the point that it could be merged in master, but only optionally enabled with a param? I think we'd get a lot more testing.

Offering both in parallel sounds like a fair plan. We can start with just doing that on Pixracer.

@tumbili I added a shell script to my fork of FlightPlot to make it easier to generate CSV files from .ulg logs:
https://github.com/kd0aij/FlightPlot/blob/master/generate_csv.sh
If you run that, you'll get an OpenFile dialog; just pick the logfile and it will generate a CSV file for each topic in the same folder as the log.

my fork of FlightPlot for displaying .ulg files: https://github.com/kd0aij/FlightPlot

@dagar @tumbili The recent changes to uORB on master seem to make it impossible to rebase this branch without breaking things. But I don't understand the autogen changes well enough to do the merge.

@kd0aij I rebased this on master! tested on a Pixracer.

@tumbili The actuator_outputs message has the size of the float32 array hardwired to 16, regardless of the value of NUM_ACTUATOR_OUTPUTS and the number of valid outputs. Perhaps we could be smarter about making this message only as large as necessary to contain the number of valid outputs.

Jenkins test this please.

@kd0aij @dagar @LorenzMeier This logger has some memory issues. If you put more topics you have to increase the stack drastically otherwise the system crashes. It does not make any sense because there is no topic data being allocated.

topics
	add_topic("sensor_accel");
	add_topic("sensor_baro", 100);
	add_topic("manual_control_setpoint");
	add_topic("vehicle_rates_setpoint");
	add_topic("sensor_gyro");
	add_topic("vehicle_attitude_setpoint");
	add_topic("vehicle_attitude");
	add_topic("actuator_outputs");
	add_topic("battery_status", 100);

disarmed
 171 logger                         59  0.372   804/ 3096 250 (250)  w:sig
 172 log_writer                      0  0.000   332/ 1016  60 ( 60)  w:sem

armed
 171 logger                      11850 19.152  2756/ 3096 250 (250)  w:sig
 173 log_writer                    941  1.754   684/ 1016  60 ( 60)  w:sem

both stacks are increasing when armed

there should only be one message buffer on the stack at any given time, but its size will depend on the topic:
				size_t msg_size = sizeof(message_data_header_s) + sub.metadata->o_size;
				uint8_t buffer[msg_size];

Is it possible that it's not the number of topics, but which topics are subscribed?

In any case, setting the stack sizes to a safe value will require imposing an upper limit on msg_size

@kd0aij Can you add some more topics and see if you get the same issue?

@tumbili I added the sensor_combined topic, and the stack usage did not change

How's everyone testing this? Working towards getting this in master I'm going to only include it in px4fmu-v4/posix sitl and keep sdlog2 working by default. I'll add a param to switch loggers. Any objections? I can do a px4fmu-v2_logger build if it would facilitate testing.

A switchable variant in master would be extremely helpful.

I'm testing by checking out newLogger and building px4fmu-v4_default. Is there a problem with that?

@kd0aij no you're fine. My main point was px4fmu-v2 is pretty tight on space so it won't have both sdlog2 and logger.

Alright I've fixed the build, rebased on master, and restored sdlog2 as default.
New param
SYS_LOGGER
0 - sdlog2 (default)
1 - logger (only available on px4fmu-v4 and posix_sitl_default)
@kd0aij @tumbili @LorenzMeier let's verify we didn't break anything and get this in master where we can continue picking away at logger without the nasty rebasing and build problems.

...and travis-ci says px4fmu-v2_default is out of space.

Has anyone actually taken a look at the breakdown of ROM usage? Is the problem the template heavy uavcan?

@dagar @LorenzMeier I just flew this in stabilize, altctl and acro modes with sys_log = 1 and everything looks OK

@kd0aij @dagar @LorenzMeier We still have some problem with this. My logs were always corrupted when I was using this together with ekf2 (the format strings were not even appearing in the log). Then I switched over to the q estimator and logging when armed was working. However, I then tried to enable logging from the beginning and then it even failed with the q estimator. So this told me that it seems to depend when exactly the logger is started compared to the other apps.
I verified that if I remove the logger from the startup script and just start it manually in the terminal after the system has booted then the logger works fine and the logs are not corrupted anymore.

@kd0aij @dagar @LorenzMeier Below is the list of topics I was logging. Even when ekf2 replay topic is active I get about 100kB/s which is very good I find. Once I have cleaned out other redundant data in the topics this will drop considerably. Also the replay topic contains a lot of redundant data (gps, flow and range finder topics are logged even if they are not updated).
add_topic("manual_control_setpoint", 10);
	add_topic("vehicle_rates_setpoint", 10);
	add_topic("vehicle_attitude_setpoint", 10);
	add_topic("vehicle_attitude", 10);
	add_topic("actuator_outputs", 50);
	add_topic("battery_status", 100);
	add_topic("vehicle_command", 100);
	add_topic("actuator_controls", 10);
	add_topic("vehicle_local_position_setpoint", 30);
	add_topic("rc_channels", 100);
	add_topic("ekf2_innovations", 20);
	add_topic("commander_state", 100);
	add_topic("vehicle_local_position", 10);
	add_topic("vehicle_global_position", 10);
	add_topic("system_power", 100);
	add_topic("servorail_status", 100);
	add_topic("mc_att_ctrl_status", 50);
	add_topic("control_state");
	add_topic("estimator_status", 100);
	add_topic("vehicle_status", 20);
	add_topic("vehicle_land_detected", 100);
	add_topic("ekf2_replay");

Got a step closer. Valgrand gave this indication in SITL:
pxh> ==11843== Thread 16 log_writer:
==11843== Syscall param write(buf) points to uninitialised byte(s)
==11843==    at 0x4E4635D: ??? (syscall-template.S:81)
==11843==    by 0x4B32B4: px4::logger::LogWriter::run() (log_writer.cpp:141)
==11843==    by 0x4B33F1: px4::logger::LogWriter::run_helper(void*) (log_writer.cpp:73)
==11843==    by 0x4E3F181: start_thread (pthread_create.c:312)
==11843==    by 0x596147C: clone (clone.S:111)
==11843==  Address 0x5e6f9a1 is 12,705 bytes inside a block of size 204,800 alloc'd
==11843==    at 0x4C2B800: operator new[](unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==11843==    by 0x4B1E34: px4::logger::Logger::Logger(unsigned long, unsigned int, bool) (logger.cpp:231)
==11843==    by 0x4B2EC0: px4::logger::Logger::run_trampoline(int, char**) (logger.cpp:172)
==11843==    by 0x42D5DE: entry_adapter(void*) (px4_posix_tasks.cpp:103)
==11843==    by 0x4E3F181: start_thread (pthread_create.c:312)
==11843==    by 0x596147C: clone (clone.S:111)
==11843==

It seems like the buffer is written into the logfile even if nothing has been written to it.
Tested this by initializing the buffer with a character. The character was printed into the logfile at the very beginning.

Eclipse can't tell whether the implementation of param_for_index(unsigned) is taken from param.c or param_shmem.c, and the source code doesn't have any comments explaining why there are 2 versions.

@kd0aij it's param/param.c for NuttX and param/param_shmem.c for Posix and QuRT.
@tumbili as a work around (temporary?) I moved rc.logging closer to the end of rcS and both sdlog2 and logger are working.
@LorenzMeier - we're continuing to have space issues with px4fmu-v2_default and GCC 4.8. Is removing blinkm and snapdragon_rc_pwm from this build acceptable?
In general with logger disabled is this branch acceptable for master? Are the uorb changes okay even without logger? Can we get a fresh set of eyes to do a code review focusing on the changes outside of logger.

@dagar We need the snapdragon output driver on v2. I think its time to move on to FMUv4 hardware for new developments like this one. Could you get yourself a Pixracer? There will also be full Pixhawk-like versions of FMUv4 at some point.

@LorenzMeier logger isn't built in px4fmu-v2_default, but other changes in this PR increase the final binary by about 4KB which just pushes us over the edge now that lis3mdl is in.
So what options do we have? Can we stop building any of these for px4fmu-v2_default? I don't see any good options.

sf0x

sf10a

srf02

lis3mdl

ets_airspeed - anyone still using this with a pixhawk?

bst

frsky_telemetry

trone

mpu9250 - tridge said there are rare pixhawks with an mpu9250, but this is by far the largest of these options next to uavcan

DriverFramework - I don't know anything about this, but could it be disabled until it's actually going to be used on px4fmu-v2?

move uavcan to a separate build and make it an option for flashing in QGC. Obviously not a great option.

logger is now burning 40% cpu

logger burns 20% cpu with fewer topics subscribed; test flown with these topics and Q estimator:
	add_topic("sensor_accel", 10);
	add_topic("sensor_baro", 100);
	add_topic("sensor_gyro", 10);
	add_topic("manual_control_setpoint", 10);
	add_topic("vehicle_rates_setpoint", 10);
	add_topic("vehicle_attitude_setpoint", 10);
	add_topic("vehicle_attitude", 10);
	add_topic("actuator_outputs", 50);
	add_topic("battery_status", 100);
//	add_topic("vehicle_command", 100);
//	add_topic("actuator_controls", 10);
//	add_topic("vehicle_local_position_setpoint", 30);
//	add_topic("rc_channels", 100);
//	add_topic("ekf2_innovations", 20);
//	add_topic("commander_state", 100);
//	add_topic("vehicle_local_position", 10);
//	add_topic("vehicle_global_position", 10);
//	add_topic("system_power", 100);
//	add_topic("servorail_status", 100);
//	add_topic("mc_att_ctrl_status", 50);
//	add_topic("control_state");
//	add_topic("estimator_status", 100);
	add_topic("vehicle_status", 20);

Rolls and flips in rattitude mode are fun and easy:

@kd0aij can you do a quick test with SYS_LOGGER 0 (sdlog2). If we're sure sdlog2 is still fine and can slightly reduce the build size we can merge this.

sdlog2 looks OK

@kd0aij @dagar Can you please try and enable logging from start? You just have to give it the -e flag.
I'm not able to get an uncorrupted log with this setting.
Pointers to the code:
https://github.com/PX4/Firmware/blob/newLogger/src/modules/logger/logger.cpp#L389
Here is where the logging is started when if doesn't need to wait for the vehicle to be armed.

@kd0aij @dagar Hm, I just did another test with the recent branch and the problems don't appear. I can log with ekf2 from beginning and the logs look fine.
However, cpu usage is at 40 %.

@kd0aij @dagar I pushed a fix for the cpu usage, see last commit.

@tumbili Any ideas for reducing px4fmu-v2_default size? https://github.com/PX4/Firmware/pull/4197#issuecomment-213516275

Removed bst, gpio_led, and srf02 from px4fmu-v2_default just to get the build passing.

@dagar Thanks for making the checks pass! I'll continue testing this and hope we can get this into master as soon as possible.

@kd0aij @dagar I did some more testing with this. The corrupted logs which I was seeing seems to be related to a lack of memory. When I reduce to logbuffer size form 34 to 20 things seem to be working fine. EKF2 used more memory than the q estimator so I guess this was the reason why I was having problems.

I'm getting hardfaults on both R7 and R12 pixracers after running for at least 30 minutes. Still seeing the non-printable characters at the end of the mavlink log filename, but there doesn't seem to be anything wrong with that bit of code. Reducing the log buffer size from 32 to 20K did not fix it.
Any suggestions on where else to look, and does that corrupt filename provide any clues?

@LorenzMeier Does https://github.com/PX4/Firmware/commit/14a20e31122c20a435101ae5c9393a384c56255d have any relation to the hardfault I'm seeing?

I much rather suspect the logger. But try if it fixes it for you.

I'm seeing the hardfault with the logger started but not logging
On Mon, Apr 25, 2016 at 7:06 AM Lorenz Meier<EMAIL_ADDRESS>wrote:

I much rather suspect the logger. But try if it fixes it for you.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/PX4/Firmware/pull/4197#issuecomment-214309332

For space issues the old EKF is a big offender. The top 3 consumers of flash space are:
00009560 T AttPosEKF::FuseOptFlow()
00012296 T AttPosEKF::FuseMagnetometer()
00032912 T AttPosEKF::CovariancePrediction(float)
(use arm-none-eabi-nm -C -t d -S --size-sort <path to elf> to get flash consumption by function)
Seems wise to audit the map periodically and make sure we're not introducing bloat, even if the v4 is the way forward and currently has ample flash space.

Keeping all these commits rebased on master is becoming difficult and the incremental history is probably not that valuable. I squashed everything int newLogger2. We can keep newLogger around for now.
Continued here: #4365


fix: update to eye v9.6.10

fix: update to eye v9.6.10

:tada: This PR is included in version 12.3.7 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
v12.3.7

Your semantic-release bot :package::rocket:


Add support for net-* secret informer filtering

Proposed Changes

Part of the work here: https://github.com/knative-sandbox/net-istio/commit/d5f9c0a00c0d4fd68208650fd84e89c33c1e1aa2
Introduces an annotation knative.dev/enable-secret-informer-filtering-by-cert-uid on Serving CR to trigger the related behavior. This can be done as follows: knative.dev/enable-secret-informer-filtering-by-cert-uid: true.
In the future is should be removed as the behavior will become the default.
Due to how informers are consumed this cannot reside in a config map as setup needs to happen early before sharedmain is called. Thus it is passed to net-istio via en env var.
Annotations are common on CRs to fine-tune behavior.
A similar approach will be needed for net-kourier. The annotation will cover that too.

To test this follow instructions here.
/cc @houshengbo
Release Note

Users can enable informer filtering by decorating Serving CR with annotation `knative.dev/enable-secret-informer-filtering-by-cert-uid`:`true`.

/retest

/cc @nak3 @dprotaso

Operator CR already supports spec.deployments to override replicas, labels, nodeSelector and so on - docs link.
So I wonder that it is better to support spec.deployments.env in general like:
  deployments:
  - name: net-istio-controller
    env:
    - container: controller
      name: ENABLE_SECRET_INFORMER_FILTERING_BY_CERT_UID:
      value: "true"

Actually net-kourier supports some env variables like https://github.com/knative-sandbox/net-kourier#setup-tls-certificate but operator cannot configure them.

@nak3 sure :) that is an option if overriding env vars can be supported. One benefit of this PR is simpler UX.

It is good to think of supporting overriding env in general.
Let's see if there are other use cases. If @nak3 @skonto @dprotaso folks happen to know any, plz share them.

Let's see if there are other use cases. If @nak3 @skonto @dprotaso folks happen to know any, plz share them.

All controllers have KUBERNETES_MIN_VERSION env variables and some users want to change it. In fact, https://github.com/knative/operator/issues/915 was requested.
Some other env variables are also requested by https://github.com/knative/operator/issues/915#issuecomment-1065141629.

I will work on a PR for the env support. From a UX perspective it might be better to have specific fields as the CR is the API users should use and not the env vars.

I suggest we close this PR for now, since we merge the one supporting evn vars, which can meet the requests for filtering resources. We can revisit this change, when the request for filtering gets more mature.


AMD ApexChart isn't being loaded

Using RequireJs and AMD ApexCharts (apexcharts.amd.js)
define([
    "js/modules/OEE/apex-charts/apex-charts_amd",
],
function (apexChart) {

});

'apexChart' results in null. Is this a bug or am I doing something wrong?

Hi @sgba00 , did you solve in your case? I have the same problem.


Unable to view Plotly Graphs

Issue Type: Bug
Before one of the updates, I was able to view Plotly graphs on the interactive window. However, now when I run the codes, nothing shows up.
import plotly.express as px
px.histogram([1,2,2,3,3,3,4,4,5])

Extension version: 2020.9.111407
VS Code version: Code 1.49.1 (58bb7b2331731bf72587010e943852e13e6fd3cf, 2020-09-16T23:21:17.533Z)
OS version: Darwin x64 19.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz (8 x 2300)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 4, 3

Memory (System)
8.00GB (0.19GB free)

Process Argv
--crash-reporter-id 1c10e725-cce8-4b0e-a802-f154460bc76e

Screen Reader
no

VM
0%

THanks for reportin gthi sissue. Unfortunately I'm unable to replicate this issue at my end.
Please could you provide the following information:

Version of Python use
Output from the console window (there might be some errors)

Select the command Toggle Developer Tools
Provide the output from the console window

Output from the console window for Interactive Window

Select the command Open WebView Developer Tools
Provide the output from the console window

Hi, thanks for responding.

I'm currently using Python 3.7.7

Here is the output from the console window after I clicked Toggle Developer Tools

/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5407 Overwriting grammar scope name to file mapping for scope source.r.
Old grammar file: file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/extensions/r/syntaxes/r.tmLanguage.json.
New grammar file: file:///Users/jaoming/.vscode/extensions/ikuyadeu.r-1.4.6/syntax/r.json
register @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5407
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5407 Overwriting grammar scope name to file mapping for scope source.sql.
Old grammar file: file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/extensions/sql/syntaxes/sql.tmLanguage.json.
New grammar file: file:///Users/jaoming/.vscode/extensions/ms-mssql.mssql-1.9.0/syntaxes/SQL.plist
register @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5407
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5407 Overwriting grammar scope name to file mapping for scope source.yaml.
Old grammar file: file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/extensions/yaml/syntaxes/yaml.tmLanguage.json.
New grammar file: file:///Users/jaoming/.vscode/extensions/redhat.vscode-yaml-0.11.0/syntaxes/yaml.tmLanguage.json
register @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5407
workbench.html:1 A cookie associated with a cross-site resource at https://visualstudio.com/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] (node:33986) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] Starting WebSocket: RAW/api/kernels/0717b675-9c12-4334-89f6-71f6b3733a5a
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] Kernel: connected (0717b675-9c12-4334-89f6-71f6b3733a5a)
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] Starting WebSocket: RAW/api/kernels/a9c5f161-bc18-4846-a58b-b5aa00ac4b19
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] Kernel: connected (a9c5f161-bc18-4846-a58b-b5aa00ac4b19)
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] Starting WebSocket: RAW/api/kernels/7dc20975-c523-4126-bbfa-bf0b15f94be0
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] Kernel: connected (7dc20975-c523-4126-bbfa-bf0b15f94be0)
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4127 [Embedded Page] Starting WebSocket: BOGUS_PVSC/api/kernels/7dc20975-c523-4126-bbfa-bf0b15f94be0
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4127 [Embedded Page] Kernel: connected (7dc20975-c523-4126-bbfa-bf0b15f94be0)
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] Starting WebSocket: RAW/api/kernels/7a9daac9-b416-4ad1-823c-14c254ddee7e
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] Kernel: connected (7a9daac9-b416-4ad1-823c-14c254ddee7e)
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] Kernel: starting (7a9daac9-b416-4ad1-823c-14c254ddee7e)
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4127 [Embedded Page] Could not create web worker(s). Falling back to loading web worker code in main thread, which might cause UI freezes. Please see https://github.com/Microsoft/monaco-editor#faq
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4127 [Embedded Page] Failed to construct 'Worker': Script at 'vscode-webview-resource://5903c262-8384-4421-bfd4-0fb1af47ab95/file///editor.worker.js' cannot be accessed from origin 'vscode-webview://5903c262-8384-4421-bfd4-0fb1af47ab95'.
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] rejected promise not handled within 1 second: Error: The task was cancelled.
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] stack trace: Error: The task was cancelled.	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:363450	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:363744	at Immediate.<anonymous> (/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:364107)	at processImmediate (internal/timers.js:439:21)
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604 [[object Object]]The task was cancelled.
$onExtensionRuntimeError @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604 Error: The task was cancelled.
	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47
	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47
	at Immediate.<anonymous> (/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47)
	at processImmediate (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/internal/timers.js:439)
$onExtensionRuntimeError @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] rejected promise not handled within 1 second: Error: The task was cancelled.
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] stack trace: Error: The task was cancelled.	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:363450	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:363744	at Immediate.<anonymous> (/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:364107)	at processImmediate (internal/timers.js:439:21)
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604 [[object Object]]The task was cancelled.
$onExtensionRuntimeError @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604 Error: The task was cancelled.
	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47
	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47
	at Immediate.<anonymous> (/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47)
	at processImmediate (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/internal/timers.js:439)
$onExtensionRuntimeError @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] rejected promise not handled within 1 second: Error: The task was cancelled.
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] stack trace: Error: The task was cancelled.	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:363450	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:363744	at Immediate.<anonymous> (/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:364107)	at processImmediate (internal/timers.js:439:21)
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604 [[object Object]]The task was cancelled.
$onExtensionRuntimeError @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604 Error: The task was cancelled.
	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47
	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47
	at Immediate.<anonymous> (/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47)
	at processImmediate (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/internal/timers.js:439)
$onExtensionRuntimeError @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4127 [Embedded Page] Uncaught ReferenceError: Plotly is not defined
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1706   ERR No application in the Launch Services database matches the input criteria.: Error: No application in the Launch Services database matches the input criteria.
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] Starting WebSocket: RAW/api/kernels/439ee3fc-251a-47a9-962c-dbaf693f04f3
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] Kernel: connected (439ee3fc-251a-47a9-962c-dbaf693f04f3)
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] Starting WebSocket: RAW/api/kernels/23cc7ecc-f0ab-419e-bfeb-da3348412bd1
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] Kernel: connected (23cc7ecc-f0ab-419e-bfeb-da3348412bd1)
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4127 [Embedded Page] Could not create web worker(s). Falling back to loading web worker code in main thread, which might cause UI freezes. Please see https://github.com/Microsoft/monaco-editor#faq
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4127 [Embedded Page] Failed to construct 'Worker': Script at 'vscode-webview-resource://a7506af4-7200-4940-b01c-48c17396372d/file///editor.worker.js' cannot be accessed from origin 'vscode-webview://a7506af4-7200-4940-b01c-48c17396372d'.
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] rejected promise not handled within 1 second: Error: The task was cancelled.
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] stack trace: Error: The task was cancelled.	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:363450	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:363744	at Immediate.<anonymous> (/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:364107)	at processImmediate (internal/timers.js:439:21)
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604 [[object Object]]The task was cancelled.
$onExtensionRuntimeError @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604 Error: The task was cancelled.
	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47
	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47
	at Immediate.<anonymous> (/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47)
	at processImmediate (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/internal/timers.js:439)
$onExtensionRuntimeError @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] rejected promise not handled within 1 second: Error: The task was cancelled.
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] stack trace: Error: The task was cancelled.	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:363450	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:363744	at Immediate.<anonymous> (/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:364107)	at processImmediate (internal/timers.js:439:21)
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604 [[object Object]]The task was cancelled.
$onExtensionRuntimeError @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604 Error: The task was cancelled.
	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47
	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47
	at Immediate.<anonymous> (/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47)
	at processImmediate (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/internal/timers.js:439)
$onExtensionRuntimeError @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] rejected promise not handled within 1 second: Error: The task was cancelled.
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] stack trace: Error: The task was cancelled.	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:363450	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:363744	at Immediate.<anonymous> (/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:364107)	at processImmediate (internal/timers.js:439:21)
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604 [[object Object]]The task was cancelled.
$onExtensionRuntimeError @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604 Error: The task was cancelled.
	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47
	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47
	at Immediate.<anonymous> (/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47)
	at processImmediate (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/internal/timers.js:439)
$onExtensionRuntimeError @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] rejected promise not handled within 1 second: Error: The task was cancelled.
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284 [Extension Host] stack trace: Error: The task was cancelled.	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:363450	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:363744	at Immediate.<anonymous> (/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:364107)	at processImmediate (internal/timers.js:439:21)
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:284
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604 [[object Object]]The task was cancelled.
$onExtensionRuntimeError @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604 Error: The task was cancelled.
	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47
	at /Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47
	at Immediate.<anonymous> (/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47)
	at processImmediate (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/internal/timers.js:439)
$onExtensionRuntimeError @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4604
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4127 [Embedded Page] Uncaught ReferenceError: Plotly is not defined
2/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1706   ERR No application in the Launch Services database matches the input criteria.: Error: No application in the Launch Services database matches the input criteria.
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/semver-umd/lib/semver-umd.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/tas-client/tas-client/ExperimentationService.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/tas-client/tas-client/FeatureProvider/TasApiFeatureProvider.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/tas-client/tas-client/FeatureProvider/FilteredFeatureProvider.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/tas-client/tas-client/FeatureProvider/BaseFeatureProvider.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/tas-client/tas-client/Util/AxiosHttpClient.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/tas-client/tas-client/ExperimentationServiceBase.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/tas-client/tas-client/ExperimentationServiceAutoPolling.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/tas-client/tas-client/Util/MemoryKeyValueStorage.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/tas-client/tas-client/Util/PollingService.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/vscode-textmate/release/main.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/xterm/lib/xterm.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/xterm-addon-unicode11/lib/xterm-addon-unicode11.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/xterm-addon-search/lib/xterm-addon-search.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/node-pty/lib/index.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/node-pty/lib/unixTerminal.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/node-pty/lib/terminal.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/node-pty/lib/eventEmitter2.js.map:
DevTools failed to load SourceMap: Could not load content for file:///Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/node-pty/lib/utils.js.map:

Output from the console after clicking on Open WebView Developer Tools

monaco.bundle.js:1 Could not create web worker(s). Falling back to loading web worker code in main thread, which might cause UI freezes. Please see https://github.com/Microsoft/monaco-editor#faq
we @ monaco.bundle.js:1
monaco.bundle.js:1 Failed to construct 'Worker': Script at 'vscode-webview-resource://a7506af4-7200-4940-b01c-48c17396372d/file///editor.worker.js' cannot be accessed from origin 'vscode-webview://a7506af4-7200-4940-b01c-48c17396372d'.
we @ monaco.bundle.js:1
VM80:1 Uncaught ReferenceError: Plotly is not defined
    at <anonymous>:1:203
    at t.value (vendors~nteract_transforms.bundle.js:2)
    at Ta (commons.initial.bundle.js:2)
    at Pa (commons.initial.bundle.js:2)
    at commons.initial.bundle.js:2
    at Object.t.unstable_runWithPriority (commons.initial.bundle.js:2)
    at Ms (commons.initial.bundle.js:2)
    at xs (commons.initial.bundle.js:2)
    at Es (commons.initial.bundle.js:2)
    at ms (commons.initial.bundle.js:2)
DevTools failed to load SourceMap: Could not load content for vscode-webview-resource://a7506af4-7200-4940-b01c-48c17396372d/file/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/datascience-ui/notebook/ipywidgets.js.map:
DevTools failed to load SourceMap: Could not load content for vscode-webview-resource://a7506af4-7200-4940-b01c-48c17396372d/file/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/datascience-ui/notebook/monaco.bundle.js.map:
DevTools failed to load SourceMap: Could not load content for vscode-webview-resource://a7506af4-7200-4940-b01c-48c17396372d/file/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/datascience-ui/notebook/commons.initial.bundle.js.map:
DevTools failed to load SourceMap: Could not load content for vscode-webview-resource://a7506af4-7200-4940-b01c-48c17396372d/file/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/datascience-ui/notebook/interactiveWindow.js.map:
DevTools failed to load SourceMap: Could not load content for vscode-webview-resource://a7506af4-7200-4940-b01c-48c17396372d/file/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/datascience-ui/notebook/vendors~dataresource~geojson~modeldebug~nteract_transforms~nteract_transforms_vsdom.bundle.js.map:
DevTools failed to load SourceMap: Could not load content for vscode-webview-resource://a7506af4-7200-4940-b01c-48c17396372d/file/Users/jaoming/.vscode/extensions/ms-python.python-2020.9.111407/out/datascience-ui/notebook/vendors~nteract_transforms.bundle.js.map:

Thanks, thats an odd error.

Please could you uninstall the extension & ensure the following folder has been deleted

/Users/jaoming/.vscode/extensions/ms-python.python-*

Reload VS Code
Install the extension again & try it.
What version of plotly do you have installed on your machine?
Also, please could you try the following:

Create a blank notebook (select command Python: Create New Blank Jupyter Notebook).
Add one cell with the python code
Run the cell
Confirm the plot isn't displayed
Save the notebook
Please upload the ipynb file here (I'd like to see the contents of the output, it is saved in the ipynb file).

I've deleted the file, reloaded VS Code and reinstalled the extension. It still didn't work.
I have Plotly Version = 4.10.0 installed.
I've uploaded the notebook here.
plotly_problem.ipynb.zip

Thanks, interesting, I can replicate the issue when opening your notebook.
Will dig into this.

Please could you let me know whant you get when you run the following in a notebook cell
import plotly.io as pio
print(pio.renderers.default)

Next, please could you change the default as follows:
import plotly.io as pio
pio.renderers.default = 'plotly_mimetype+notebook' # This is what I have on my machine and works for me.

For more information please check here https://plotly.com/python/renderers/

I get colab when i run the first code.
It worked for me when I changed it to plotly_mimetype+notebook. Thank you!
Is there a way to change the default?

Please check their documentation
The link I provided earlier contains some information.
The following might help
It is also possible to set the default renderer using a system environment variable. At startup, plotly.py checks for the existence of an environment variable named PLOTLY_RENDERER. If this environment variable is set to the name of an available renderer, this renderer is set as the default.


Weeder: Command exited with code -9

Context
Test Case
Weeder check
Failure / Counter-example
--- Weeder
weeder
error: Command exited with code -9!
Continuing...
./buildkite-script-15be0fbf-9d48-4997-b874-643c35bebbf3: line 5: 30308 Killed                  ./sr/bin/rebuild --build-dir=$BUILD_DIR --cache-dir=$CACHE_DIR

Resolution

QA

On Linux, if a process exits with -9, it's because it's been killed with SIGKILL.
Normally builds or processes are stopped with SIGTERM or SIGINT.
So I believe this build failure is probably due to the Linux OOM killer running on the Buildkite build agent.
It may have been another project's build running at the same time which used all the memory and caused our build to be zapped.
This would hopefully be a pretty rare situation.
@Anviking If you provide a link to the buildkite job, we examine the grafana host monitoring charts at the time of the build, and perhaps see the cause.

If you provide a link to the buildkite job, we examine the grafana host monitoring charts at the time of the build, and perhaps see the cause.

@rvl FYI they are linked indirectly through github:

But e.g. https://buildkite.com/input-output-hk/cardano-wallet/builds/15044

OK I see. The monitoring shows something gobbled all the memory at the time the build failed:

I wonder if it's a problem with weeder itself. Because after looking at the logs for packet-ipxe-2, the only jobs running around the same time were:

https://buildkite.com/input-output-hk/cardano-wallet/builds/15044#15be0fbf-9d48-4997-b874-643c35bebbf3 (weeder)
https://buildkite.com/input-output-hk/cardano-wallet/builds/15045#828bcede-9de4-4eae-87b3-aad77d844eb8 (docker)
https://buildkite.com/input-output-hk/cardano-wallet/builds/15045#2422a53a-c9fd-4503-9ebb-3728a8268eaa (lentil)

OK I see. The monitoring shows something gobbled all the memory at the time the build failed:

😮 nice finding!

I wonder if it's a problem with weeder itself.

✔ 🤔

Happened again in https://buildkite.com/input-output-hk/cardano-wallet/builds/15563#d800ef36-7911-4a15-aced-2e28621653ce/10267-10269. The weeder step was running for 27 minutes before it was killed.

After the weeder config fixes, I found this error on Buildkite:
incompatible hie file: /build/cardano-wallet/lib/text-class/.stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Test/Text/Roundtrip.hie
    expected .hie file version 8104 but got 8105
    weeder must be built with the same GHC version as the project it is used on

That is due to loading a cached .stack-work built with a previous compiler version.
Perhaps the weeder problem is due to corrupted .hie files or something like that?


New option for file name capitalization handling

In this update, I have added a new option for file name capitalization handling, which allows users to convert specific parts of the file name to title case (first letter capitalized, other letters lowercase), while preserving the original case of the original_name. The previous code only supported two formats: all uppercase and all lowercase for whole file name.
To implement this feature, I added a new conditional branch to check whether the 'capitalization' setting in the configuration file is set to 'title'. Users can specify the delimiter (in this case, ']') and how to handle different parts of the file name in the configuration file according to their needs.
Possible future improvement: Support for extension capitalization.
I hope this change will provide more flexibility and customization options.

Coverage: 90.553% (-0.06%) from 90.61% when pulling fdb6821e6fbfcb0ad860223f9371e0a8dd3aab7c on alterxyz:patch-1 into 76ad82303fcbf0e4ab421dbfbb39e4a4cc76aecc on jmathai:master.


XP configuration

Docs are not OK (at least for me):
customLaunchers: {
'IE7': {
base: 'WebDriver',
config: webdriverConfig,
browserName: 'internet explorer',
platform: 'Windows XP',
version: '10',
'x-ua-compatible': 'IE=EmulateIE7',
name: 'Karma'
}
},
Platform should be XP, and not 'Windows XP'.

Selenium sources would seem to confirm this:
https://github.com/SeleniumHQ/selenium/blob/1f2813a8eb6adf51aa7b3ac2f700d4617ff1205e/java/client/src/org/openqa/selenium/Platform.java#L46


Feature/use rejections option

This should resolve issue #485
please review

Correction: This fixes just the first part of #485, dealing with promises returned by swal, as requested. The issue should remain open to discuss the second part, dealing with promises returned to swal by preConfirm and inputValidator options.

Great job! Looks perfect to me. Special thanks for covering the new code with tests.
Please go ahead with the same approach for preConfirm and inputValidator options.

I released https://github.com/limonte/sweetalert2/releases/tag/v6.6.3 yesterday with this change, take a look.
Please feel free to submit any changes for this PR ot the PR related to the same approach for preConfirm and inputValidator options.

This has fallen under my radar :) I've just updated the TypeScript definition file and the README to take useRejections in account.
Thanks @ArlyMathiasen && @mattbrunetti for that feature I will totally use :)


Extract Splitter from the MapsManager

Hello @camillebrianceau! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file clinicadl/API_test.py:

Line 77:9: E266 too many leading '#' for block comment


Update pr-checks.yml

I can't figure this out. My guess is that there's some sort of unprintable char getting returned that is breaking things. But not sure why it's happening on CI only.
It's not really worth spending more time on this, so I think I'll just remove the failing test and getting things through.

I think I found the solution!
head -n 1 closes the pipe, replace with sed '1!d' and it works :)
          LATEST_NIGHTLY_TAG="$(gh api "repos/dsp-testing/codeql-cli-nightlies/releases" --jq ".[] | select(.draft == false) | .tag_name" | sed '1!d')"

          LATEST_NIGHTLY_VERSION="$(gh api "repos/dsp-testing/codeql-cli-nightlies/releases" --jq '.[] | select(.draft == false) | .body '| sed '1!d' | awk '{print $4}')"

I added the fix to #27

Rebasing on #27, which should be running.


CI on a big-endian system

It turns out, that pyarrow is not available for big-endian platforms - therefore running our tests on such platform is not very feasible (as it will take a long time to install pyarrow from the source package)


⚠ Bofrost.lu has degraded performance

In 1ec7757, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1111 ms

Resolved: Bofrost.lu performance has improved in 5596c68 after 35 minutes.


Lack of QA for changes to maintainers/maintainer-list.nix

Issue description
The file maintainers/maintainer-list.nix seems to be randomly edited by committers who feel like doing so, thereby ignoring data protection laws governing some regions where our contributors come from (e.g. https://github.com/NixOS/nixpkgs/pull/178656, https://github.com/NixOS/nixpkgs/pull/272199, https://github.com/NixOS/nixpkgs/pull/273137 as of before the force-push) guidelines our community gave to itself (e.g. https://github.com/NixOS/nixpkgs/pull/275328, https://github.com/NixOS/nixpkgs/pull/275370). Having our community guidelines ignored at random lets NixOS look unprofessional and can scare away contributors and supporters. Having data protection laws ignored might even lead to expensive liabilities for the NixOS foundation, meaning that the money would be missing when paying for servers or incentivizing contributors. Therefore, there should be some QA when editing that file.
A straightforward suggestion regarding this would be to install one or more maintainers for that file itself. These would have to review any PRs touching it before merging would be allowed. The maintainers should provide evidence that they are aware of laws governing personal data in the different jurisdictions we work with, and aware of our community guidelines.
Steps to reproduce

Wait
See commits happening where laws and/or community guidelines are being ignored

Technical details
Not applicable.

Let's please keep this scoped towards only discussing a QA process for the maintainers file, and not go into other points of disagreement from the issues that sparked this discussion.

A straightforward suggestion regarding this would be to install one or more maintainers for that file itself. These would have to review any PRs touching it before merging would be allowed.

Proposal in #275443.

Seems like the default mechanisms for maintainers who get pinged on file changes won't work well here. Most commits are probably contributors adding themselves to the file. If we assume that the TOFU model works for these, only exceptional commits would have to be checked manually, thereby reducing the workload. But this would require a smarter ofborg...

Hi, on GitHub and more specifically the nixpkgs repo we almost exclusively handle the technical side of things

Well, the maintainer list is currently maintained in code, so the platform where the repository resides should be an appropriate place to discuss how that's done.
Of course, one might argue that this is a mistake in the first place considering the unclear situation regarding how to comply with the GDPR with such a setup. If we go that route, then yes, maintenance of the list should also be discussed somewhere else.


elemental-cli: fix build version

Codecov Report
Patch coverage: 49.46% and project coverage change: -0.89 :warning:

Comparison is base (45aa692) 76.58% compared to head (c68ed66) 75.69%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1790      +/-   ##
==========================================
- Coverage   76.58%   75.69%   -0.89%
==========================================
  Files          59       63       +4
  Lines        5594     5776     +182
==========================================
+ Hits         4284     4372      +88
- Misses       1014     1094      +80
- Partials      296      310      +14

Impacted Files
Coverage Δ

pkg/constants/constants.go
82.25% <0.00%> (-7.22%)
:arrow_down:

pkg/types/v1/config.go
88.44% <ø> (ø)

pkg/types/v1/platform.go
53.33% <0.00%> (-3.01%)
:arrow_down:

cmd/config/config.go
74.34% <16.66%> (-4.40%)
:arrow_down:

cmd/init.go
40.62% <40.62%> (ø)

pkg/action/init.go
40.62% <40.62%> (ø)

pkg/features/features.go
60.49% <60.49%> (ø)

pkg/config/config.go
95.45% <100.00%> (+0.07%)
:arrow_up:

pkg/systemd/unit.go
100.00% <100.00%> (ø)

pkg/utils/common.go
80.05% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Read version from file and tag docker image in GitHub workflow

I just wanted to try the demo since it finally made it into master :rocket:
I realized, that we never created the version tag for the docker images. I'm not sure if that was planned in #61 but I figured we should fix this one quickly because the current master won't work (without adjustments at least).
So this PR just adds to the workflow by reading the version from the version file and tagging the docker image we are building already. [I tested the action on this branch already])https://github.com/KIT-MRT/arbitration_graphs/actions/runs/11611034651) so we should be good to go.

Awesome, I didn't realize the docker image CD is already setup :star_struck:


Authsign formating bug

Authsign json is saved in an additional json encode.
"{\"hash\":\"......

Seems that authsign data is read in as a string here
https://github.com/starlinglab/integrity-backend/blob/main/integritybackend/file_util.py#L216
But saved as if it was a dict being turning into a string
https://github.com/starlinglab/integrity-backend/blob/main/integritybackend/file_util.py#L221
To solve:
Load the string into a dict
authsign_proof = json.loads(r.text)

authsign_proof = r.json()

OR
Save it as a string
authsign_proof = r.text

Fix merged into dev, @YurkoWasHere this issue can be closed once dev is merged into main.


Allow worker to see their own submissions

Sometimes a worker may want to refer back to something they submitted. In the current case, they want to get back to the file they uploaded.
Presumably this would be attached to the Worker Status page.

it's really difficult to identify a particular task (row) we could let them navigate from Worker tab to a list view of all the tasks they did for that project but im not sure how to display these tasks other than task id (task worker id)

Figma page on this.

cjiang92398

@cjiang92398


TS-64 IMPROVEMENT - Update Share Page with Edit Team Sheet

WIP:
Two things here
1st - just updated the look of buttons. Updated to have a "+" for Create or Duplicate buttons. Now realize I want the edit icon for an Edit button. Also updated the colour of the Duplicate button - I think the Create Team Sheet and Duplicate Teamsheet should have look different/. I've gone with different colours like a createPrimary and createSecondary but maybe the duplicate button should be the same colour but just a ghost button (green border and text, white background)? Thoughts?
2nd - Reason for this this PR is described in the ticket
"When user is logged in and visiting the share page for one of their own teamsheets, updating the "Create Your Own" button to instead be an "Edit Team Sheet" button so that user can go back to the edit page.
Currently no way to navigate back to the edit page other than going back to my team sheets page and clicking edit link."
What I've currently done won't work as it will show the edit link to any logged in user.
Need to show the Edit teamsheet button if a) the user is logged in and b) that teamsheet belongs to that user.
Thinking we need a useCurrentUser hook and then compare that userId against the userId on the teamsheet.
Will update.
..
If not Logged in:

If Logged in:

So for client components we are going to wrap the entire app (in layout.tsx) in a global context containing the currentUser so we can pull it out wherever we want

just a reminder of what we decided to do here:

we were going to put a useContext around the whole app with the purpose of holding the current user
that way we will always have access to the current user in our client components
for server components, we get the user from kinde, then use prisma to get the record from our users table