(feat) beautify raw json body request

With the use of Monaco Editor, it isn't really clear from the UI how to format a raw JSON body request.
To overcome this, I have introduced a "beautify" button to format the raw request JSON.
It will only appear in the event that the request body is "raw" and the language chosen is "JSON". This is an identical feature to what Postman has.

Could you move the location of the button to near the language dropdown

Could you move the location of the button to near the language dropdown

PR has been updated to reflect this change:

This looks great! Thank you so much for this @thuoe


How to increase the Line Spacing/ Height in the Editor of Spyder

Problem Description
The Line Spacing in Spyder Editor is too small for me. But I cannot find a way to increase it.
What steps will reproduce the problem?

Just write some codes in the Editor.

What is the expected output? What do you see instead?
The Line Spacing can be adjusted.
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Package Versions

Spyder: 3.2.8
Python: 3.6
Qt:
PyQt:
Operating System: Win 10

Dependencies

PASTE DEPENDENCIES HERE

Sorry, this can't be adjusted in Spyder. Please try to use a different font family or size to fix this in your side.


CS3223: Fix copy paste error / typos

Found an error in the cost_leaf equation.
Also noticed one side of a "number of tuples" expression was missing.
:)

Thank you for the fixes @tjog, really appreciate it 🔥
I pushed the compiled PDF to your branch!


Let labels take a list of custom colors

🚀 Feature
Following up on discussion with @adamltyson on this image.sc post I think it would be nice if we allowed users to set their own list of colors for add_labels as an alternative to using random colors. If the user has more labels than colors we can just cycle through them.

There is another request for this here https://github.com/hci-unihd/covid-if-annotations/issues/5

As mentioned in the other issue, I would have two use cases for this:

adding a mode where some labels in the segmentation layer are hidden, i.e. their alpha value is set to 0
Synchronize the colors between a label layer and a points layer.

I also looked at the image.sc post linked in the issue and I realized that for the second use-case the image layer with fixed color map makes more sense (I have just used the labels layer there to make zero transparent, otherwise I don't need any functionality provided by it).
However, for the first issue I think that passing a dict mapping label ids to colors would be the best solution. The color of a given label should then be determined like this:
color = color_dict.get(label_id, random_color(label_id))

Also, I would need to turn this mode on and off, so it should be possible to set the color_dict dynamically:
# set custom colors for the first labels
labels_layer.color_dict = {1: 'red', 2: 'green', 3: 'blue'}

# deactivate the custom colors
labels_layer.color_dict = {}

Let me know if this makes sense to you and if it's something that could be implemented in a rather short timeframe ;).

Let me know if this makes sense to you and if it's something that could be implemented in a rather short timeframe ;).

Yes, we should be able to turn this around pretty quickly (I'm imagining an initial PR in a few days from now, reviewed and merged by the end of the week). The more crisply we can specify it the faster.
I'm thinking that we will want to reuse some of the API paradigm that we use in the points layer and consider adding support for labels properties (see #1214) either in or immediately after this PR.
The points layer currently has the following for face and edge color
layer.*_colormap # colormap name, vispy colormap tuple
layer.*_color_mode # str with different modes, DIRECT, CYCLE, COLORMAP
layer.*_color_cycle # list of colors for the cycle
layer.*_color # rgba array, that could also be set to the name of a property
layer.properties # properties dict

For labels we could try and preserve this pattern, or instead of using a CYCLE use a dict. If we ignored the concept of properties we could just have
layer.colormap # colormap name, vispy colormap tuple
layer.color_mode # str with different modes, DICT, COLORMAP
layer.color_dict # dict of colors {1: 'red', 2: 'green', 3: 'blue'}

The above would be a simple PR that could get you what you need.
If we do want to use properties we'd need to decide what they look like, and so I will continue some discussion of that on #1214. Curious what @kevinyamauchi and @jni make of this so far

This is now closed by #1339


Add dog's state machine that determines the active behavior tree to run

...and make the dog feel sad when realizes that the man has died :)

Very cool!


Too low integrator accuracy leads to exception

Setting a too low integrator accuracy (or - given the parameter - too high) leads to the following exception:
std::exception in 'SimTK::State const & OpenSim::Manager::integrate(double)':
SimTK Exception thrown at AbstractIntegratorRep.cpp:428:
  Integrator step failed at time 0.49668703558495564 apparently because:
SimTK Exception thrown at AbstractIntegratorRep.cpp:547:
  Error detected by Simbody method AbstractIntegrator::takeOneStep(): Unable
to advance time past 0.496687.
  (Required condition 't1 > t0' was not met.)

I received the exception using ProstheticEnvs instantiated with integrator_accuracy >= 0.01. There were no problems with values <= 0.001.
Slightly more detailed information: I trained four walkers using different integrator accuracies: 0.1, 0.01, 0.001 and 0.00005 (default). This was the only parameter I modified and as mentioned above, there was a related occurence of errors.
I am on Windows 10 using the latest OpenSim version (Python 3.6.1) and followed the recommended installation instructions.

That's right, unfortunately, integration might not be possible with integrator accuracy set to high, I believe there is no workaround. @chrisdembia @carmichaelong is there any way to hack this?

I had temporarily introduced a change to allow setting integrator accuracy from Python/Matlab: https://github.com/opensim-org/opensim-core/commit/d09c42953eed8e1b07e014232eef27a73ca4d403 (this commit shows removing the change).

Thank you @chrisdembia . We actually do have an interface to change accuracy through this
https://github.com/kidzik/opensim-core/commit/550c2a15d56a918f5fe712d4050b8b5eba84eaeb
and this
https://github.com/stanfordnmbl/osim-rl/blob/master/osim/env/osim.py#L227-L233
However, @janEbert is trying to put very accuracy and it crashes. Is there any rule on how high it can go? or any hack to make it even less accurate than he is trying?

Sherm uses the terms "loose accuracy" and "tight accuracy" to avoid the ambiguity of "low accuracy" and "high accuracy."
That exception message just means the accuracy level is too loose.

Maybe emit a warning, clip the value or do not allow too high values?

Thanks @janEbert. I think the solution is a warning or clearer error message. It is not possible to clip the value because the appropriate clipping value depends on the model and motion.

@janEbert I created an issue in the simbody repository (https://github.com/simbody/simbody/issues/639).

It is not possible to clip the value because the appropriate clipping value depends on the model and motion.

This is an important point, and particularly tricky here since motions are being generated on the fly. That being said, it might be good to have a rough guideline somewhere. It sounds like @janEbert has found a cutoff accuracy that seems to work pretty well at 0.001, which agrees with what I've been using with a similar model.

Ah yes, giving guidelines is a good idea.


reverse public repo PR 2790 and move to private repo to fix sync PR

https://github.com/MicrosoftDocs/architecture-center/pull/2790 was merged with blocking issues in the public repo. Metadata issues are preventing the repo sync PR from being merged, https://github.com/MicrosoftDocs/architecture-center-pr/pull/2985. We're backing out the PR in the public repo and have moved the original commits to the private repo. We'll fix blocking items in the new PR and it will merge there. This PR deletes the files that were in the original pull request from master in this repository.

#Sign-Off

@EdPrice-MSFT: I'm sorry - only the author of this article, @pdevito3, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Thanks @EdPrice-MSFT


Motion does not work

Hello, it's me again. I have two issues concerning the motion detection.

After changing the video resolution the whole web interface gives an error to start RPi again. After a restart the new resolution is saved but motion doesn't work anymore. Somehow it can't handle the higher res. After changing back to the default res. motion works again.

After that I have installed the Web_Interface again. And everything worked perfect.

After a few days of running the RPi, I see motion doesn't work again. It should record but it doesn't. Everything is on default settings. I have no explanation.

Thank you.

I'm not aware of any motion problem specific to resolution unless you increase the preview size substantially which can increase the CPU load. After you re-installed did you still have a resolution problem? Was it repeatable?
If motion is stopping after a few days then one should first check the schedule log to see exactly what is happening? It is worth looking at the trouble-shooting section on the eLinux wiki which has a step by step guide on checking motion detection out.
Also unreliability can be caused by less than perfect power supply arrangements particularly as the camera draws a bit more current. You need to be sure that the PS can supply the load and that the voltage drop in the power cable is small.

I couldn't fix it, but the internal motion detection works.


npm install pcap doesn't work

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.22.27905\include\xkeycheck.h(255,1): warning C4005:  'inline': macro redefinition (compi
ling source file ..\pcap_binding.cc) [D:\business\x\node_modules\pcap\build\pcap_binding.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.22.27905\include\pcap-stdinc.h(69): message :  see previous definition of 'inline' (comp
iling source file ..\pcap_binding.cc) [D:\business\x\node_modules\pcap\build\pcap_binding.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.22.27905\include\xkeycheck.h(257,1): error C1189:  #error:  The C++ Standard Library for
bids macroizing the keyword "inline". Enable warning C4005 to find the forbidden define. (compiling source file ..\pcap_binding.cc) [D:\business\x\node_modules\pcap\build\pcap_binding.vcxproj]
D:\business\x\node_modules\pcap\pcap_session.cc(3,10): error C1083:  Cannot open include file: 'sys/ioctl.h': No such file or directo
ry [D:\business\x\node_modules\pcap\build\pcap_binding.vcxproj]

@GkqqNkKC just so you're aware, this is an ongoing discussion/issue here: 251
@jonahharris has taken ownership of the npm repo and plans to integrate his fix. Now, Idk if that addresses issues for WIN or not, but thought I would make you aware.

if you're using windows, see https://github.com/node-pcap/node_pcap/issues/249#issuecomment-586201286


IndicatorsControl color?

Hello all,
Is there a way to make the color of the indicatorscontrol black?

Hi you can define the style in the constructor, this is my sample
var indicators = new IndicatorsControl             {                 SelectedIndicatorStyle = new Style(typeof(Frame))                 {                     Setters = {                         new Setter { Property = BackgroundColorProperty, Value = Color.DarkGray.MultiplyAlpha(.8)},                         new Setter { Property = WidthRequestProperty, Value = 3}                     }                 },                 UnselectedIndicatorStyle = new Style(typeof(Frame))                 {                     Setters = {                         new Setter { Property = BackgroundColorProperty, Value = Color.LightGray.MultiplyAlpha(.5) },                         new Setter {Property = WidthRequestProperty, Value = 2}                     }                 },                 Margin = new Thickness(10, 0, 10, 7)             };

@reense hi
Yes, for sure
https://github.com/AndreiMisiukevich/CardView/issues/54

Thanks!!

@reense if you like this plugin, you can support it by setting star on this repo ;)


perf(cicd/ui): migrate from CRA/Craco to Vite

Overview
This migration from the current create-react-app build tooling is a pretty significant overhaul that touches quite a few areas. The primary reason for wanting to migrate is quicker dev server startup and production builds. It's also worth noting that the creator/lead maintainer of Webpack has stepped away from the project to work on a new build tool (Turbopack), causing some uncertainty for the long-term project roadmap as others step in to maintain.
Benchmarks
Dev server startup (yarn start)

Baseline:   52.74s
With Vite: 0.83s

Production build (yarn build)

Baseline: 96.95s
With Vite: 37.52s

All tests were performed using the latest from master (as of 11/30/22) on a 2021 M1 MBP (32GB). Average time was taken from 3 consecutive runs of the same test. Time spent generating graphql types (yarn generate) is excluded from comparison.
Major Changes

Local dev proxy server rewritten as Vite plugin (see devProxyPlugin.ts)
Frontend build pipeline no longer moves static assets from build/ to dist/. Vite outputs to dist by default.
Removal of manually prepending assets/ to certain urls. Vite should handle this automatically when hosting files between local dev and production builds.

What's left?

[ ] Fix Cypress startup
[ ] Fix remaining asset 404s (monaco editor library 3rd party JS and platform logos)

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

hey @stanbaker! Thanks so much for putting this together. I'm curious how important a change like this is for your team? In your description you mention the build times being the primary reason for the change, as well as some uncertainty about CRA's future leadership. How much of a blocker are build times for your team or is this just a nice to have?
The core team has some concerns about the risks of switching away from CRA due to all of the hidden complexities with single-page app builds and configurations that it takes care of for us. Also, while Vite certainly has a large following and usage, it's still somewhat less established than create-react-app (I feel less strongly about this than the risks of making the switch). Basically, we want to be very cautious and make sure we're doing the right thing here!
I think we're leaning towards holding off on this move until we have more signal that it's the right call, but we'd love to hear some more thoughts from you and your team.

hey @stanbaker! Thanks so much for putting this together. I'm curious how important a change like this is for your team? In your description you mention the build times being the primary reason for the change, as well as some uncertainty about CRA's future leadership. How much of a blocker are build times for your team or is this just a nice to have?
The core team has some concerns about the risks of switching away from CRA due to all of the hidden complexities with single-page app builds and configurations that it takes care of for us. Also, while Vite certainly has a large following and usage, it's still somewhat less established than create-react-app (I feel less strongly about this than the risks of making the switch). Basically, we want to be very cautious and make sure we're doing the right thing here!
I think we're leaning towards holding off on this move until we have more signal that it's the right call, but we'd love to hear some more thoughts from you and your team.

Hey @chriscollins3456, thanks for the feedback! This isn't a blocker/priority by any means, totally understand if you all would rather stick with what's working for now instead of taking some risk on entirely migrating build tooling! Closing this PR


fix: missing namespace for Type in C# JsonSerializerPreset

Description
The JsonSerializerPreset in C# cant determine the dependency. This PR adds the explicit type.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.584%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2371

Relevant Lines:
2417

💛  - Coveralls

/rtm


[NTI] Infer const for namespaces

debugger
In migrating tests to NTI, I'm seeing a lot of cases where type checking falls down due to things like the following:
var a = {};
/** @constructor */
a.B = function() {};

/** @param {!a.B} arg */
function f(arg) {}

This is fine in OTI, but NTI complains:
input0:5: WARNING - Type annotation references non-existent type a.B.
/** @param {!a.B} arg */
             ^^^

The warning can be fixed by adding @const to the namespace declaration, but if it's never reassigned, we should be able to infer that it's const and treat it as such.

I think it's good to require the @const. It gives a uniform way of defining a namespace, rather than the compiler trying to be smart. (We allow omitting the @const in externs for legacy reasons.)


PostgreSQL Support

Hi,
I tried to use it with PostreSQL and got errors. Could you please add support for PostreSQL database?
Thank you.

This is not something I'm willing to support as I have no need for it. Sorry! Feel free to open a pull request that adds support for PostgreSQL though.

Ok, thanks. I thought it should be easy to use Lumen with PostgreSQL - http://lumen.laravel.com/docs/database - it is supported by default. I am not PHP developer so I hope you will someday find time to test it and tweak it for the PostgreSQL support :-)


shutdown/halt service?

Is there a correct way to stop all keybase services? keybase ctl stop doesn't affect the GUI or the fuse daemon, as far as I can tell.
so far I've been doing:
keybase ctl stop
pkill Keybase
sudo umount /keybase

That looks about right, but I'd expect pkill kbfsfuse rather than sudo umount /keybase.

If you're on Linux, take a look at the first half of /usr/bin/run_keybase:
# Editing out all the echoes...
killall Keybase
fusermount -uz /keybase
killall kbfsfuse
killall keybase

I think the fusermount step is important -- I'm told scary things can happen if you umount a FUSE mount, but I don't know what they are.

(Maybe I should be using pkill instead of killall there? How standard is pkill?)

At some point I'd like to publish a systemd unit for all this stuff. I don't think we could rely on it by default, but folks on compatible distros who want to use systemctl could have the option. (Would need some way to suppress autofork in that case maybe?)

pkill's more broad (pattern matching on various fields, not solely on the process name) so I think we're right to use killall.

Hmm, there's this from man pkill:
-f, --full
       The pattern is normally only matched against the process name.  When -f is set, the full command line is used.

By default pkill matches on even more than that (e.g. the pid).

on OSX 11.11.5 umounting from GUI has almost no effect, the drive is quickly mounted after 1s. killing everything (both from cli or Activity Monitor) still leaves the drive mounted.
Options to stop GUI, ctl and umounting the drive should be available ootb.

It would be nice to have a way to turn off the filesystem or service! I don't use the keybase filesystem features, and even after closing keybase there are three processes using over 500GB of virtual RAM each. For some reason this always makes the OSX UI slow so I've uninstalled keybase.

+1 for way to shut down keybase and use it only when I need it.
Better support this wish than have people removing keybase because it bothers them.

Why is this not a thing? How is keybase even starting up I don't see a systemd unit for it?

We haven't taken a systemd dependency yet, though we might in the future. Right now we use ~/config/.autostart/keybase_autostart.desktop to start our 3 services (the keybase daemon, the kbfsfuse mount, and the GUI). If you want to disable autostart, there's a comment in that file about how to do it. (You can't just delete the file, though, because it'll get recreated.)
I do have the following function in my shell, for emergencies. Not guaranteed to be stable, of course:
kbdown () {
        if killall Keybase &> /dev/null
        then
                echo Shutting down Keybase GUI...
        fi
        if fusermount -uz /keybase &> /dev/null
        then
                echo Unmounting /keybase...
        fi
        if killall kbfsfuse &> /dev/null
        then
                echo Shutting down kbfsfuse...
        fi
        if killall keybase &> /dev/null
        then
                echo Shutting down keybase service...
        fi
}

@cjb, do you know what the current thinking is about whether quitting in the GUI should kill keybase/kbfsfuse?

If anyone wants to try out, I just wrote my first shot at keybase user unit files; placed them under /keybase/netvor/systemd-user.
Disclaimer: I'm just learning systemd; I'm almost sure I've missed something. The services are able to start but I haven't yad yet opportunity to try and re-login to see if they work properly. So, feedback is more than welcome; I'll update the files on the go. Also I'll gladly PR them somewhere if anybody tells me where.

I'll add a :+1: for having this actually be managed. I don't use the filesystem at all and don't want to. I just want the command line (not to mention the resource usage by keybase when I'm not even using it). This should definitely be considered a service and not a desktop startup script. Even if it remains as a desktop startup script it needs to be documented more thoroughly, it took me several minutes of Googling before I found the right term to get to this issue.

Hey hackers, I've also tried to manage keybase processes with systemd, but ran into minor issue with restarting of keybase process after updates. Maybe some of you will have ideas regarding issue #5355 ?

keybase ctrl app-exit works

can this be closed?  @panicbit's solution (keybase ctl app-exit) worked for me

For anyone else seeing this and wanting to stop keybase: Use keybase ctl stop. Using keybase ctl app-exit did nothing for me. Using stop immediately killed all the keybase processes and powertop no longer reports it completely dominating my battery. I haven't used Keybase in literally months and it's somehow consuming more power than Slack which is just completely bonkers insane.

this actually does not completely stop keybase from running.  It doesn't have the same effect as "show keybase" --> "quit keybase", which effectively stops all keybase processes from running

Looking forward to systemd support.

On all platforms, clicking Username -> Quit Keybase from the app, or Hamburger -> Quit Keybase from the systray widget should close all Keybase processes.
On all platforms, running keybase ctl stop in the command line should do the same thing.
On Linux using systemd, you can also run systemctl --user stop keybase keybase.gui kbfs keybase-redirector.
On Linux packages packaged by Keybase, you can also run run_keybase -k.
If any of the above doesn't work, please make a new ticket. Thanks!

That do not seem to be true

keybase ctl stop is nice. thank you for that command tip


Fix warning about incorrect workspace name

The workspace name for prometheus-cpp has been updated to the correct
canonical name.

Rebased and pushed, hope that's what you needed.


weighted least squares support

I just got basic weighted least squares support in my fork of SavitzkyGolay.jl.
As part of the development I added some basic unit tests to avoid any
regressions from the released version.
I'm planning to add some doc strings and update the README.md.  I
haven't had time because I need to get to using the new SG weights.
I'm sending a pull request to get more eyes on the code, suggestions,
and what not.  It should be backward compatible to the existing 0.7.0
release but the only tests I have are the 2 from the README examples.

Great work. I had the same idea: https://github.com/lnacquaroli/SavitzkyGolay.jl/issues/29
What about supporting any of the windows from DSP.jl as a valid weight vector?
In particular the triangular window yields very good results (see linked issue above). And there is also an 'optimal' weight vector, see this mathworks article, section 'Optimal Weights with Optimal Smoothness'.

The references I followed, including wikipedia, had the requirement that
the weights be positive. I'm not sure if it is valid or useful to have a non-positive
weight value(s).

I'm not really sure what you mean. All the windows in DSP.jl meet that requirement

The weight function cannot be zero.
A lot of the windowing functions go to zero so care must
be taken (usually at the edges) so the values are positive.

Update the README please as well and go on with the merge.

The purpose of DSP.jl is much broader than this package. The reason for the SG here to exist was to have a quick and easy implementation that doesn't rely on heavy dependencies. I'm OK with improving it, but making something similar to what exists wouldn't seem useful.

The purpose of DSP.jl is much broader than this package. The reason for the SG here to exist was to have a quick and easy implementation that doesn't rely on heavy dependencies. I'm OK with improving it, but making something similar to what exists wouldn't seem useful.

I would only use DSP.jl to define the windows. If you're going to use a SavitzkyGolay filter there is a 99% chance you area already using DSP.jl

I've updated the README and synchronized examples.  I wasn't able to make another pull request.  The current main head of my fork should be good to go.  You'll need to update the image link paths for your repository.  I don't know if there is an easier way to automate that.

Closing to try another pull request.


Fix zap logging adapter to work with latest pgx v5

Also update zap dependency to latest version

Thanks!


Expect and the "Accept:" header

Motivation
Our Rails back-end uses the Accept HTTP request header to determine what to send back to clients. It defaults to sending HTML unless told otherwise.
When we make a HTTP request that expects a JSON response, if the user's authentication session has expired, here's what happens:

Rails detects this and sends a 401 response
Because it did not see an Accept header, it defaults to sending back HTML - a fully rendered "You need to log in" HTML page
Because the Elm request expected a JSON response, it tries to run a JSON decoder on this HTML, which of course blows up because HTML is not JSON

In the NoRedInk/elm-rails package, we explicitly set the Accept header on all JSON requests to application/json, which prevents this.
However, sometimes we use other packages that do HTTP, and if they do not set this header, and we don't remember to override it to set it properly, we end up with production bugs when users are not authenticated.
Proposal
Http.Body stores a String for what Content-Type header should be set in the request. Http.jsonBody uses this to set Content-Type: application/json on any request that has a JSON body.
Http.Expect could similarly store a String for what Accept header should be set in the request. Http.expectJson could use this to set Accept: application/json on any request that expects a JSON response.
This would address this problem for anyone using elm/http with Rails or other servers that use the Accept header to make decisions about what format to use for responses.

I think this is reasonable and sound way of content-negotiation. We should definitely achieve this symmetry.
While I was updating my elm-http-xml package (https://github.com/ymtszw/elm-http-xml) to support<EMAIL_ADDRESS>I've found Http.Request data type was no more.
In older version of elm-http-xml, I've been supplying Accept: application/xml header at this layer.
But in 2.x of elm/http, there is no suitable interface to atomically add Accept header AND introduce corresponding decoding functions (in my case via Xml.Decode.Decoder type).


Add composer parallel install plugin

@PavelPrischepa couldn't complete automated test, it requires docker user credentials

@fortis It's because Travis secrets (Docker Hub user/password) aren't available within PRs. It's my mistake. I've disabled docker push in master branch.
Back to PR. The plugin already exists https://github.com/Wodby/drupal-php/blob/master/7.0/Dockerfile#L158. Does it works for you?

oh I just missed this, yes it works


[SPARK] fix merge into for delta

Problem
Symptoms: MERGE INTO is not generating column level lineage for delta queries.
This is connected with some other issues that should be resolved within this PR:

column level lineage is not tested for each supported spark version (its tests should be moved to app subproject)
column level lineage does not support including visitors per Spark version

Closes: #1919
Solution

run column lineage tests on all supported versions,
implement merge into per spark (per delta version)

Note: All schema changes require discussion. Please link the issue for context.

[ ] Your change modifies the core OpenLineage model
[ ] Your change modifies one or more OpenLineage facets

If you're contributing a new integration, please specify the scope of the integration and how/where it has been tested (e.g., Apache Spark integration supports S3 and GCS filesystem operations, tested with AWS EMR).
One-line summary:
Checklist

[ ] You've signed-off your work
[ ] Your pull request title follows our guidelines
[ ] Your changes are accompanied by tests (if relevant)
[ ] Your change contains a small diff and is self-contained
[ ] You've updated any relevant documentation (if relevant)
[ ] Your comment includes a one-liner for the changelog about the specific purpose of the change (if necessary)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
[ ] You've added a header to source files (if relevant)

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2023 contributors to the OpenLineage project

TODO: after merge modify file https://openlineage.io/docs/integrations/spark/spark_column_lineage -> change META-INF/services/io.openlineage.spark3.agent.lifecycle.plan.column.CustomColumnLineageVisitor to META-INF/services/io.openlineage.spark.agent.lifecycle.plan.column.CustomColumnLineageVisitor

Codecov Report

Merging #1958 (360ec7b) into main (9187496) will decrease coverage by 18.03%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@              Coverage Diff              @@
##               main    #1958       +/-   ##
=============================================
- Coverage     81.15%   63.13%   -18.03%
  Complexity      109      109
=============================================
  Files            88       29       -59
  Lines          3699      415     -3284
  Branches         29       29
=============================================
- Hits           3002      262     -2740
+ Misses          661      117      -544
  Partials         36       36

see 59 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Can't run the code

Hi, great work! However, I have a problem running it. I hope you can give me some suggestions.
When I ran the command python scripts/plan_maze2d.py --config config.maze2d --dataset maze2d-large-v1, it says I don't have module tap. So I install tap==0.2 and mc-bin-client==1.0.1. But it seems just support Python 2, so there are many errors.

I just modified the code and removed the requirement of tap.

tap is short for typed-argument-parser, installed in environment.yml:L16. I'd recommend checking out the installation section of the README.

tap is short for typed-argument-parser, installed in environment.yml:L16. I'd recommend checking out the installation section of the README.

Thanks for your reply. I slacked off and build the env based on the old env... The problem is solved now.


Implement String.prototype.replaceAll

Skip the https://github.com/tc39/test262/blob/main/test/built-ins/String/prototype/replaceAll/searchValue-replacer-RegExp-call.js due to regexp named groups.

Thanks!


Basic GP Tutorial

Hi,
I was working through your basic GP tutorial, and was trying to understand how the predictive distribution shown on line 9 relates to equations 2.23 and 2.24 of the Rasmussen textbook (the derived expressions for the predictive mean and covariance matrix for Gaussian process regression:

).
I expected the mean shown to be exactly expression 2.23, and the confidence intervals to be the mean +/- 2 times the standard deviations, obtained by taking the square root of the diagonal entries of the covariance matrix of expression 2.24.  While the mean obtained from expression 2.23 does match up with the predicted mean, the plotted confidence intervals are much larger than those obtained from the formula given in the Rasmussen book.  I attach a pdf of my modified jupyter notebook; the important plot is the last one.  Any guidance you can provide is much appreciated. Thanks.
basic_gp.pdf

The problem was that the tutorial's m.plot() function was plotting the confidence intervals for y* = f* + e$, whilst I was plotting those for f*.  After accounting for this difference, the confidence intervals shown by m.plot_f() and as calculated using the Rasmussen formula match up reasonably well.


Adding ionicons to the dependencies

When creating a new app and selecting a tabbed UI, the ionicons are not loaded (because they were left out from the dependencies).,

:+1:

@pmadruga There's merge conflicts, I think if you fix them maintainer/author would consider merging it in.

Please ignore this pull request and check https://github.com/diegonetto/generator-ionic/pull/195 instead.


⚠ API - Lens has degraded performance

In baaf801, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 502
Response time: 565 ms

Resolved: API - Lens performance has improved in 09383f9 after 6 minutes.


Possible incorrect port number listed in this document

"If unable to connect, allow inbound port 9443 on the Process Server and check if the problem still exits."
I think you mean port number 443 for HTTPS, not 9443.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d72ac543-7402-d3c3-150f-b85f009abe2c
Version Independent ID: f613426a-e18f-81ef-ddca-d2646e157cb1
Content: Troubleshoot replication issues for VMware VM and physical server replication to Azure with Azure Site Recovery
Content Source: articles/site-recovery/vmware-azure-troubleshoot-replication.md
Service: site-recovery
GitHub Login: @Rajeswari-Mamilla
Microsoft Alias: ramamill

@jogold9 Thanks for the feedback. We are actively investigating and will get back to you soon.

@jogold9 Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@jogold9 In a process server, the inbound port is 9443 and the outbound port is 443. VMs send replication data to the process server on port HTTPS 9443 inbound. So, 9443 is the right port. You can refer to https://docs.microsoft.com/en-us/azure/site-recovery/vmware-azure-architecture#replication-process for more info

#please-close

We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


feat: add curriculum-api 2023 config

Description

add curriculumApi2023 config to config/server.ts

Issue(s)
Progresses #1713
How to test

App should still run
There are no visible changes here, just plumbing

:tada: This PR is included in version 1.187.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


sync updated for demo

details see https://github.com/toschneck/microservices-demo/pulls/2

@guusvw my updates for the demo at the google roadshow

@guusvw can you review & merge. @scheeles can you give me access rights?


Gpu swap integration

Change MemoryManager to be an abstract interface. Provide GetMemoryManager() and GetMemoryManagerRef() for upper layers to transparently access MemoryManager. The default MemoryManager is CUDAMemoryManager.

@Sotskin @KarlLeell Please check this pull request. Before doing so, please read my email.

Another suggestion: comment out line 86 of gpu_swap_prefetch.cc, which call PrintHandles of swap function. For testing I think printing handles is unnecessary and takes time


Jetty to stackdriver logging with google custom logging handler

We are trying to deploy a Kubernetes cluster based on the gcr.io/google-appengine/jetty image, deployment is working fine and logs are appearing on stackdriver but multiple lines are split into multiple log entries and all of them are with Error severity.
We are trying to fix that by giving a custom logging.properties file to the Jetty server as shown in the attached Docker file as mentioned in the README here, which uses com.google.cloud.logging.LoggingHandler handler as shown in the attached flex.logging file.
But the server is failing to initialize after this change with the exception shown in  attached error file.
The error message is
 java.lang.ClassNotFoundException: com.google.cloud.logging.LoggingHandler
 Can't load log handler "com.google.cloud.logging.LoggingHandler"

But the dependency for this is included in Maven Java application pom.xml file.
<dependency>
  <groupId>com.google.cloud</groupId>
  <artifactId>google-cloud-logging</artifactId>
</dependency>

error.txt
flex.logging.txt
Dockerfile.txt

After modifying the Dockerfile adn adding a RUN command that looks like this it worked
RUN java -jar "$JETTY_HOME/start.jar" --create-startd --add-to-start=gcloud --approve-all-licenses
Basically we needed to add gcloud module, which is not added by default when deploying to GKE


Pcap viewer: Access denied

After logging into the dashboard, the Pcap viewer panel is saying "Access denied". I've followed the instructions for setting up the UI and can't figure out why I am receiving this.
Thanks in advance

Thanks , it is useful for my , i have also occured this issue.

it is help for me

pretty great,  after i add the part of [ "auth": "true"  ] in config path.  i  can see the login page message in pages, "http://<IP_ADDRESS>:5000/login" , and i try use the email and password base the help of "They are<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Both have a default password of opensoc. Access to the PCAP dashboard is based on having the pcap permission assigned. By default only<EMAIL_ADDRESS>has this permission. See the README for how to set permissions to AD groups in config.json. You can see the development LDAP schema in seed/ldap/content.ldif"
thanks


Update image ghcr.io/zoriya/kyoo_transcoder to d763c39

This PR contains the following updates:

Package
Update
Change

ghcr.io/zoriya/kyoo_transcoder
digest
363d076 -> d763c39

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


Slow training

Hi!
Thanks so much for the helpful training code and documentation. Apologies in advance for the naive question--I'm pretty new to machine learning.
I'm trying to train my own watermarking model at 48kHz with my own dataset on an H100 node with 8 GPUs (H100 80GB HBM3) on a remote SLURM cluster, but as I scale the batch size the training speed appears to drop proportionally. There also appears to be an unexpected behavior where I specify dataset.batch_size=k but the submitted config (logged by wandb) shows dataset.batch_size=k/8.
As an example, I ran experiments setting dataset.batch_size=8, which became dataset.batch_size=1, yielding a max training speed of about 1.67 steps / second and GPU utilization reaching averaging around 25%. When I set dataset.batch_size=128 (to yield dataset.batch_size=16), training speed dropped to around 0.3 steps / second. It seems to me that parallelization isn't working the way it should based on these results?
I've tried preprocessing my dataset to one-second clips and removing some of the augmentations (even running an experiment with only noise augmentations) to try to increase GPU utilization, but nothing I've tried has improved the training speed.
Is this to be expected? Roughly how long did the original model take to train, using what amount of compute?
Thank you so much!

@christianc102
Hi!
I encountered a similar issue during my training process. One thing that helped me was updating the data hyperparameters in the solver configuration, particularly the dataset.[train, valid, evaluate].num_samples parameters. I assume when these values don't align with your dataset size, it can lead to inefficient GPU utilization.
I hope this helps!

I found that the pesq operation in [audiocraft/solvers/watermark.py] is very time-consuming, so I skipped it.


Application is size is getting increase by 19 Mb

After adding the library the application size is getting increased by 19 Mb. Without library, the apk size is 5.3 Mb and after flutter_pdf_viewer library is added apk size reached to 24 Mb.
Pubspec.yml file
`name: flutter_movie_app
description: A new Flutter application.
dependencies:
flutter:
sdk: flutter
cupertino_icons: ^0.1.2
url_launcher: ^3.0.0
scoped_model: ^0.3.0
rxdart: ^0.18.1
flutter_pdf_viewer: ^0.0.4
http: ^0.12.0
flutter:
uses-material-design: true
fonts:
- family: Merriweather
fonts:
- asset: fonts/Merriweather-Regular.ttf
- asset: fonts/Merriweather-Bold.ttf
- asset: fonts/Merriweather-Italic.ttf
style : italic`

You're going to have to take that upstream, sorry.
https://github.com/barteksc/AndroidPdfViewer#why-resulting-apk-is-so-big

any idea what will be the apk size after generating split apk

@chhota89. No idea, I never had an issue with the APK size.
You might be interested in open_file plugin which opens the pdf in external app, and hence the apk size is minimal.


Chrome WebStore User Data Policy

Google announced User Data Policy ( https://developer.chrome.com/webstore/program_policies#userdata )
This extension gets and sends screen-capture and basic infomation (URL and title) of webpage user visits.
I think this extension is required "Privacy Policy Requirements" so we should add private policy page ( https://gyazo.com/doc/privacy ) link to Chrome Extension Webstore's page and inline install page.
FAQ: https://developer.chrome.com/webstore/user_data

we should add private policy page

Completely agree. Please do it!


EspAuthenticator does not work for google_id_token

Based on https://github.com/GoogleCloudPlatform/java-docs-samples/blob/master/appengine/endpoints-frameworks-v2/backend/src/main/java/com/example/echo/Echo.java#L128
  @ApiMethod(
      httpMethod = ApiMethod.HttpMethod.GET,
      authenticators = {EspAuthenticator.class},
      audiences = {"YOUR_OAUTH_CLIENT_ID"},
      clientIds = {"YOUR_OAUTH_CLIENT_ID"}
      )
  public Email getUserEmail(User user) throws UnauthorizedException {
    if (user == null) {
      throw new UnauthorizedException("Invalid credentials");
    }

    Email response = new Email();
    response.setEmail(user.getEmail());
    return response;
  }

I receive a 401 "Invalid credentials" response unless I delete the line authenticators = {EspAuthenticator.class},, in which case once EspAuthenticator is removed it continues to work.
Tested using API Explorer.

Please see https://stackoverflow.com/questions/43218379/authenticating-users-using-firebase-and-google-on-cloud-endpoints-and-api-expl for more.

@frankyn PTAL

Hi @gbhall!
After reading, it seems the stack overflow response was able to solve your issue.
Please feel free to reopen if this persists or file new issues!


Base zoom speed on browser refresh rate

Description
Bases zoom speed on the render rate of the user's browser.
Added fields in FrameRateMonitor to track the timestamps of the n most recent renders.
Then when calculating the zoom distance on each frame, adjust it based on the fps zoom speed to provide consistent experience for browsers with different speeds.
If the user wants faster or slower zoom, they can still adjust zoomFactor through the public api as before with the same effects.
Issue number and link
https://github.com/CesiumGS/cesium/issues/12187

Testing plan

Author checklist

[x] I have submitted a Contributor License Agreement
[x] I have added my name to CONTRIBUTORS.md
[x] I have updated CHANGES.md with a short summary of my change
[x] I have added or updated unit tests to ensure consistent code coverage
[x] I have updated the inline documentation, and included code examples where relevant
[x] I have performed a self-review of my code

posted this for initial review/feedback/discussion @ggetz. I still need to add unit tests.

This looks somewhat similar to what I dumped into a forum thread a while ago. The goal there was also to have an "average frame rate over the last n frames".
In that forum thread, I put this into some FpsTracker class. The reasons may be obvious. The functionality is encapsulated in a class where the name says what the class does (/* An FpsTracker tracks the FPS */ 😁  ). It offers a getAverageFps function directly. It avoids that const timeStamps = object._scene.frameState?.timeStamps; (aka Train Wreck). And it avoids the manual computation (with magic constants like 10 and 30) inside the handleZoom function.
The purpose of that FpsTracker there was to plug it into some MsseUpdater, which was supposed the update the maximum screen space error based on the average FPS. (Fleshing this out into a real feature is still on my TODO list - I think that this could make a whole lot of sense...).
tl;dr : If there was "something" where a function like getAverageFps was offered, then this could probably be re-used in multiple places...

I like your idea to create a FpsTracker class to make this more reusable. I will work on this change and update this PR when it is ready.

I like the idea of isolating the average FPS logic in one place. The update itself should probably still happen in Scene.js though.

We realized the existing FrameRateMonitor class provides close to the functionality this feature needs. We decided to make some small additions to it rather than create a new class (side notes: All the work up to this commit 331650c67d80b9011ec15a077fa7c8ea6e8b6f6d got re-written, so it may make sense to squash the early commits )
There may be questions as to why we dont get FPS from FrameRateMonitor.lastFramesPerSecond, this should be made clear by the doc updates included in this PR.
One open comment that I have not addressed: Including the target/idea browser refresh rate as constant value (30 as in 30hz) in the code. I am unsure if we should A) expose setting this in the API (but we already have zoomFactor in the public API) or B) set it in a more clear place, like a constants or system settings file.

Please excuse the comments on outdated code, I'm not sure how they snuck in there.

@lukemckinstry I'm going to close this to keep things tidy. If you or anyone else wants to update and finish this out, please feel free to re-open!


Support tachyons class overrides for layouts

Currently, the classes are explicitly listed in layouts, and it would be nice to override the defaults without overriding the styles in a custom .css. This could be either an all-in-one type thing, or perhaps per category (padding (ph/pv), scale (f*), align (tc/tj/etc).
For instance, the _default/list.html could have something like this:
    {{ $padding := .Site.Params.default_list_padding | default "ph3 ph5-l pv3 pv4-l" }}
    {{ $scale := .Site.Params.default_list_scale | default "f4" }}
    {{ $align := .Site.Params.default_list_align | default "tc-l" }}
    <section class="cf {{ $padding }} {{ $scale }} {{ $align }} center measure-wide lh-copy mid-gray">
      {{- .Content -}}
    </section>

#456