Automated cherry pick of #3005: fix: tenant filter fail to work

Cherry pick of #3005 on release/2.10.0.
#3005: fix: tenant filter fail to work

/approve
/lgtm

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.10.0@223b197). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             release/2.10.0   #3006   +/-   ##
================================================
  Coverage                  ?   7.46%
================================================
  Files                     ?     414
  Lines                     ?   66064
  Branches                  ?       0
================================================
  Hits                      ?    4931
  Misses                    ?   60710
  Partials                  ?     423

Flag
Coverage Δ

#aFlag
7.46% <ø> (?)

Impacted Files
Coverage Δ

pkg/cloudcommon/db/fetch.go
0% <ø> (ø)

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 223b197...969b49b. Read the comment docs.


Cloudpickle and force numpy pip version

Pull Request Description
What issue does this change request address?
What are the significant changes in functionality due to this change request?

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Job Test qsubs sawtooth on 82334d5 : canceled by @joshua-cogliati-inl
not needed

Job Test qsubs sawtooth on 82334d5 : invalidated by @joshua-cogliati-inl
civet problems

Job Test qsubs sawtooth on 82334d5 : canceled by @joshua-cogliati-inl
not needed

Code combined with other code and moved to #2365


WpfPlot fails to load in Visual Studio when using .NET Framework

Description
Upon trying to reproduce the plot as explained in CookBook, error is encountered when a wpfPlot control is added to the window xaml. The message reads: "Could not load file or assembly 'ScottPlot.WPF version 4.0.35, Culture=neutral' or one of its dependencies. The system can not find the file specified.".
This is a design-time error. When we run the program, it runs without errors,.  While the program runs, the reporting of error in designer is annoying.
To Reproduce
Create a new visual studio wpf project. I used Visual Studio 2019 with .Net Framework 4.7.2. Add the control. Visual studio shows squiggly blue lines and you see the above mentioned error in tool tip text.
Screenshots
If applicable, add screenshots to help explain your problem
At design time, the control shows:

The error helper:

Hey @bhairav-thakkar, thanks for reporting this!
I think this is the same issue as #466 and #356 - see those for the solution (updating your csproj format).
I'll research this topic more and see if I can figure out how to prevent this issue in the future

Hey @swharden , thank you so much for the super prompt reply. I followed the solution proposed on #356, but I still see the squiggly lines and the designer does not show the wpfplot.

Just to confirm, did you try making a new .NET Core WPF project and adding ScottPlot? Does it work then?
... then you modified the .csproj file and edited TargetFramework to read net472, does it work then?
Learning more about which step fails will be helpful.

No, I made a new .NET Framework project and added ScottPlot. In the csproj file, if I change the TargerFramework from v4.7.2 to net472, the project breaks with a message -out of range.

No, I made a new .NET Framework project and added ScottPlot.

I'm pretty sure this is the problem.
Create a .NET Core project, then modify the csproj file so it builds targeting .NET Framework.
The difference is that the .NET Core new project wizard creates SDK-style csproj files, and the .NET Framework new project wizard does not. I still don't know why, but it seems the WpfPlot requires SDK-style csproj files to function at design time.

Oh ok. Got it. Thanks. I will check that out. I was wondering what should be the best approach to include the wpfplot in an existing .Net framework project.

Hi @swharden , I find the same issue even if I create a new core project and change the targetframework. Attaching the file for your reference.
WpfApp2.zip

Thanks for sending that ZIP! It indeed fails on my computer, but I took a very close look at it and am surprised I can't spot the difference.
When I create a new project from scratch and do these steps, it works!

create a new .NET Core WPF project
manage nuget packages
install ScottPlot.WPF
drag/drop WpfPlot from the Toolbox onto the Window
rebuild (verify it works)
edit csproj to target net472
rebuild (still works)

Here's a zip of that project
WpfApp3.zip

hello Scott, I am having the same problem aswell, downloaded the zip you provided, opened it and the problem still exists. Functionally it has no effect but seeing the error message all the time might become frustrating over time. Below is the screenshot.

Thank you for your interest

hello Scott, I am having the same problem aswell, downloaded the zip you provided, opened it and the problem still exists. Functionally it has no effect but seeing the error message all the time might become frustrating over time.

@riquich Thanks for confirming you have this same issue! I just reformatted and installed a fresh Windows 10 and latest Visual Studio, and I now too get the same error message. Here are those details in a searchable format:
Exception: Cannot create an instance of "WpfPlot".
 at Microsoft.VisualStudio.DesignTools.Designer.InstanceBuilders.InstanceBuilderOperations.InstantiateType(Type type, Boolean supportInternal)
   at Microsoft.VisualStudio.DesignTools.Designer.InstanceBuilders.ClrObjectInstanceBuilder.InstantiateTargetType(ILocalInstanceBuilderContext context, ViewNode viewNode)
   at Microsoft.VisualStudio.DesignTools.Designer.InstanceBuilders.ClrObjectInstanceBuilder.Instantiate(ILocalInstanceBuilderContext context, ViewNode viewNode)
   at Microsoft.VisualStudio.DesignTools.WpfDesigner.InstanceBuilders.FrameworkElementInstanceBuilder.Instantiate(ILocalInstanceBuilderContext context, ViewNode viewNode)
   at Microsoft.VisualStudio.DesignTools.WpfDesigner.InstanceBuilders.UserControlInstanceBuilder.Instantiate(ILocalInstanceBuilderContext context, ViewNode viewNode)
   at Microsoft.VisualStudio.DesignTools.Designer.InstanceBuilders.LocalInstanceManager.CreateInstance(IInstanceBuilder builder, ViewNode viewNode)

TargetInvocationException: Exception has been thrown by the target of an invocation.
   at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
   at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
   at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(Type type, Boolean nonPublic)

FileNotFoundException: Could not load file or assembly 'ScottPlot.WPF, Version=4.0.35, Culture=neutral' or one of its dependencies. The system cannot find the file specified.
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.Assembly.Load(AssemblyName assemblyRef)
   at System.Windows.Navigation.BaseUriHelper.GetLoadedAssembly(String assemblyName, String assemblyVersion, String assemblyKey)
   at MS.Internal.AppModel.ResourceContainer.GetResourceManagerWrapper(Uri uri, String& partName, Boolean& isContentFile)
   at MS.Internal.AppModel.ResourceContainer.GetPartCore(Uri uri)
   at System.IO.Packaging.Package.GetPartHelper(Uri partUri)
   at System.IO.Packaging.Package.GetPart(Uri partUri)
   at System.Windows.Application.GetResourceOrContentPart(Uri uri)
   at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
   at ScottPlot.WpfPlot.InitializeComponent()
   at ScottPlot.WpfPlot..ctor()

I'm thinking this relates to how Visual Studio (which is 32-bit) caches DLLs, and 32-bit vs. 64-bit DLLs may not be agreeing with each other. An important note is that this is an error with Visual Studio designer, not with ScottPlot or the build system. As we've seen, the built application works fine.
A solution to stop displaying a design-time error message is to modify your project to target x64. It seems when this is done Visual Studio doesn't even attempt to display the control.

create a new .NET Framework 4.7.1 project
modify the build configuration for All Configurations and set platform target to x64
Install ScottPlot.WPF package with NuGet
rebuild the project
drag/drop a WpfPlot from the toolbox onto the window (it will fail to display)
close Visual Studio and open it again (it won't display an error anymore)

I'll keep investigating if there's something I can do to prevent this error in the future, because users shouldn't have to know how to do all this 😝

Hi Scott, thank you for the tip, it worked and removed the error !

Hi Scott, thank you for the tip, it worked and removed the error !

I'm glad you got it working! It's crazy how many hours this sucked up today, but I think I narrowed down the issue further: resizing a canvas in a WPF user control crashes the control in Visual Studio's designer view for .NET Framework (but not .NET Core) applications. What a mouthful! f06cfe316e92448d7fce1a4e1fccdaabc0a9d6a4 may fix the problem entirely. I'll publish this on NuGet shortly and update here when I do...

Ah man so close! That trick seemed to work locally, but not when it's on NuGet. I just released ScottPlot 4.0.36 and this issue persists. I think it may have to do with defining the AssemblyVersion, but I'll have to research this further...
https://github.com/swharden/ScottPlot/blob/caf440c3a02464ca592c66ab2d1fde38ae58d0f3/src/ScottPlot.WPF/ScottPlot.WPF.csproj#L21

Hi Scott, thanks for the endeavor, hope you find the solution soon, without much effort

Yay this is finally fixed in ScottPlot 4.0.37 🎉
Solution: AssemblyVersion must be in x.x.x.x format (cannot be x.x.x format) for .NET Framework, even though .NET Core doesn't seem to care.


Make annotation display in case overview list scale to large projects

Is your feature request related to a problem? Please describe.
Displaying all annotations for large projects is very slow. The RCA in #304 shows that for a project with 500+ samples and 10k+ annotated variants, the transferred data has a size of ~50MB. The mitigation implemented for #304 only prevents the user's browser from being overloading but is not a sustainable solution.
Describe the solution you'd like
Rather than load all data at once, provide an UI such that users can easily find the information that they need and also download the full dataset.
Describe alternatives you've considered
N/A
Additional context

#304
#307

Implementation Proposal
Instead of just dumping a table with all annotated variants, present the user with an interface that allows to select variants based on several criteria but also download a tabular file with all variants.
Affected Components

varfish-server

Affected Modules/Files

variants modules with urls, views, templates

Required Architectural Changes
N/A
Implementation Sketch

table will be paginated so the browser tab does not blow up
user can select to display 10, 25, 100 variants per page
user can select

case to select for AND/OR
display ACMG criteria AND/OR
display flags

of course there is a download "all annotated variants" link displayed as well


SVGMobject doesn't care for width and height defined in SVG

Description of bug / unexpected behavior
While playing around with https://github.com/ManimCommunity/manim/pull/1361, I have an SVG, a4dae70e0eb51266.txt, converted to .txt, where the width and height element are not taken into account while displaying.
Using Inkscape's, export to png.

Trying the same with this Code in Manim
from manim import *
config["background_color"] = WHITE
class HelloWorld(Scene):
    def construct(self):
        text = SVGMobject('a4dae70e0eb51266.svg')
        self.add(text)

I get rendering with manim -psql test.py

Expected behavior
What I am expecting is that the PNG rendered using Manim similar to rendered using Manim to match that of Inkscape. With bounding boxes and width and height element matching that of the SVG.
How to reproduce the issue

Code for reproducing the problem
from manim import *
config["background_color"] = WHITE
class HelloWorld(Scene):
    def construct(self):
        text = SVGMobject('a4dae70e0eb51266.svg')
        self.add(text)

Additional media files

Images/GIFs

Additional comments
On the other hand, I would like SVGMobject to draw things with the same size as the SVG itself and give a warning or something asking the user's to scale if the SVG has gone out of the screen or something. That would be super helpful for the Text and Tex objects because the consistency of size would be the size. For example, the size parameter will never work as expected with Text because the SVG is scaled and not drawn according to the size.

@MrMallIronmaker (since you worked n SVG object's previous), is it possible to implement these?

it is possible, it just requires a little bit of plumbing and calculating the right ratios. I'm not sure whether the default behavior should be to use the file scale (ideal behavior) or the screen scale (current behavior). I'm leaning towards the file scale with warnings if it's oddly small (<10% of screen perhaps?) or large (larger than whole screen)

The file scale seems to be the best as the user can later scale them to fit the screen but not otherwise. I had been trying to do the latter but wasn't able to achieve it to the best.

Now that there is support for Boolean operations in manim I think this should be easy to do.


chore: remove unused commitlint and husky

Background:

Husky and commitlint used to be used in the core and contrib repos.
They were removed from the core repo in https://github.com/open-telemetry/opentelemetry-js/issues/2078 because the DX was annoying. The changelog is not generated in the core repo, so it doesn't require strict adherence to "conventional commits" syntax to support that tooling.
A ".github/workflows/pr-title.yml" was added to the contrib repo in https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1068 to help ensure merged commits follow "conventional commits" (partly to help with changelog generation tooling).
Later, as a rider on https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1460#issuecomment-1809340627 the .husky/... config was removed from the contrib repo, again because its DX is just annoying, and unnecessary given the "pr-title" CI workflow.

Currently, the husky and commitlint deps remain in the contrib repo, but they are not used -- except to add some minor annoyances in some dev cases (some examples are below).

In a clean clone (e.g. after git clean -ffdx), running npm install --package-lock-only fails because of the husky usage in the "prepare" script:
% npm install --package-lock-only

><EMAIL_ADDRESS>prepare
> husky install

sh: husky: command not found
npm ERR! code 127
npm ERR! path /Users/trentm/tm/opentelemetry-js-contrib4
npm ERR! command failed
npm ERR! command sh -c husky install

npm ERR! A complete log of this run can be found in: /Users/trentm/.npm/_logs/2023-11-23T22_23_31_705Z-debug-0.log

I just saw the movement on #1829. I hope my merging this hasn't created toil for getting the release out.


Docsearch links with Github pages

Ran into a little trouble with my implementation - https://thedrone7.github.io/shieldbow/
Issue:
The docsearch results take the users to /shieldbow/shieldbow/page
BUT once on the 404 page due to this bug, clicking on the same docsearch result takes you to the correct page.
Expected
The docsearch results take the user to /shieldbow/page on the first attempt.

Yes, it's been done properly, it lists them properly and you can inspect the search result elements to verify that the links are also correct.

What's also weird, is once you are on the /shieldbow/shieldbow/api/... which is the 404 page, clicking on the same search result takes you to the correct page - /shieldbow/api/... too.

The issue is still there but I bought a domain and am now serving it on the domain so my users are fine for now.


Idempotency guards

This PR adds two simple lookups to the File Ingest Service, one for each ingest endpoint to abort any further processing if the file ID has already been processed.
As the entry in the outbox DAO is only created once everything else is done, we can reasonably assume that the presence of a corresponding entry means the ingest of a specific file has succeeded previously - at least inside the FIS.
This will still produce additional new secret entries in vault for the legacy path if something should crash before an entry is created, but the information is only propagated once in this case.
Also, decided to return to 202 for the no-op as well, as we don't need to distinguish between the new and already seen case on the client side and this would require a small change to the DS-Kit if we go with any other status code.

@lkuchenb
In batch mode individual failures are logged and then the process continues.
I'll change the code to return 204 for both endpoints if the payload has already been processed.
This will require a one line change in DS-Kit.

Changes to response status code as detailed above.
Also opted to change internal representation of file_secret to SecretStr and only get the value at the boundary to vault.
Should help with not accidentally logging sensitive information.

@mephenor also - should this be a major version bump due to the change of API behavior?


"Show Clang Tidy Info" content being analyzed

Environment

Operating System (e.g. Ubuntu 16.04 x64): Windows 10 Version 2004
IDE Version (e.g. CLion 2016.3.2): CLion 2020.2 EAP (#CL-202.5103.16)
Cppcheck executable version (cppcheck --version): 2.0
Cppcheck plugin version: 1.4.2

Expected behaviour
No analysis is performed.
Actual behaviour
The analysis is performed and causes an error since the file is just a temporary one and no longer available for analysis.
Steps to reproduce the behaviour

open a file
open the action dialog via CTRL+SHIFT+A and search for Show Clang Tidy Info
the clan-tidy info will be shown and the error popup from the plugin appears

The issues is possibly caused by the title of the file tab ending with the file name i.e. the .cpp extension causing it to be passed to the analysis. There's probably a different mechanism to figure out the file type within the plugins.

For background, this plugin is using the file extension to determine if Cppcheck should be run against it:
https://github.com/johnthagen/clion-cppcheck/blob/ca1eab8ef83ece978185ee4d4ce9f33724f795e0/src/com/github/johnthagen/cppcheck/CppcheckInspection.java#L236-L260

I figured. I wonder if this is a limit of the check() function and fixed by the newer visitor implementation. Since the documentation of the SDK is lacking it's hard to tell. I already contacted JetBrains about this a while ago and I got a contact about CLion-specific SDK question. I didn't have the time to follow up on this but I still plan to.

I have a fix for this.


Remove ca update for RH-IT-Root as it is used internally

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 66.447%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1915

Relevant Lines:
2882

💛  - Coveralls


lib: Fix broken parameter forwarding in lib tests

This broke Lix's use of the nixpkgs lib tests for regressions in Lix.
https://github.com/NixOS/nixpkgs/issues/272591#issuecomment-2156922537
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

(incorporated into https://github.com/NixOS/nixpkgs/pull/317772)

this pr is now redundant because the ones mentioned above have been reviewed and merged. yay!


Logging updates

This PR includes:

Removed logging at any level but debug for messages in the escrow loops.
Removed line feeds from all log levels but debug
Ensured stack traces are only logged in debug
Removed full event logging from info, moved to debug level.  Replaced with SAID in info.
Replaced print statements in grouping and delegating with logger.info statements.

@pfeairheller can you give a sense how this PR relates to this issue, we wanted to understand the status/next steps https://github.com/WebOfTrust/keripy/issues/763


ensure the local SP is refreshed

Both validate() and validate_pos() can make callbacks to perl subs,
potentially relocating the stack, so ensure SP points at the new stack.
This came out of testing the fairly flakey failure of App::JobLog on blead perl (https://rt.perl.org/Ticket/Display.html?id=127231).
I wasn't able to produce a regression test for P::V that demonstrated the problem.
Only indirectly related: you updated module versions to 1.23, but not the dist_version in Build.PL. This means the XS and module versions don't match, the loader falls back to the PP implementation and doesn't test the XS implementation at all.

This broke a lot of tests. I'm not sure exactly why though.

Weirder still, when I check out the branch and test on my own system all the tests pass.

Oh, that must be because of the Build.PL issue you noted.

I'm cargo culting a bit but it seems like all the SPAGAIN calls need a matching PUTBACK before the validate or validate_pos call. Take a look at https://github.com/autarch/Params-Validate/pull/9 and let me know if that fixes the problem you saw.


feat: align otter versions on ng update

Proposed change

Related issues

:bug: Fixes #(issue)
:rocket: Feature #(issue)

The migrations scripts won't update the projects package.json, only workspace root
We'll recommend using our version-harmonize mechanism to do that


[1.19] Collecting upgrade not working

According to the mod page, the upgrade should collect items in the ground, but nothing happens once I add it to the drawer.
Also, why does the upgrade have directions if it is supposed to collect all compatible items near it?

The drawer will collect items that are on the side specified in the direction, 1 block away, like a hopper

Oh, could you add an option to have (all) sides as an option? And also maybe upgrade versions of it that increase the distance?


Base: Transaction layout on Account Details

Someone has some feedback about Big Dipper in TG:

Can the transaction display go back to the previous version, which is, the transaction amount was displayed upfront? Now I have to click into it one by one to verify the transaction and it is too time consuming.

Current one:

UI

The ui did not work with the layout. It's currently not a top priority, we'll come back to this in the future


camera always rotates

I have a problem with this plugin my ios app is locked to not rotate, but the camera always rotates, do you know of any solution to this issue?

I am encountering the same issue. In my case the view list locked to landscape when the view loads. Upon initial load the camera is properly oriented. However, when the user tilts their phone forward, the camera rotates an additional 90 degrees.


Fix fcoeffs bug - energy injection rate not equal to specified

Bug fix required for fcoeffs wrt Constantinou 2015. scaling should be = 1/M for each zonal wavenumber, not 1/m.
Originally posted by @gvn22 in https://github.com/gvn22/ZonalFlow.jl/issues/23#issuecomment-1134519300

Solved in feature-gce2paper. Validated for linear and non-linear test cases.


Understanding adjaceny matrix

Hi Davide,
Thank you very much for the work.
I have some trouble understanding the adjaceny matrix. For instance a graph with n nodes. The bfs adjaceny matrix will have dimension(n, max_prev_node). I wonder what does each "slice" (1, max_prev_node) represent?
Thank you!
Best,
Nicolas

Hi Nicolas,
Happy to hear about your interest in our work!
Each "slice" (1, max_prev_node) describes whether that nodes is connected
(1) or not (0) with each of the previous "max_prev_node" nodes in the bfs
ordering. The adjancy matrix has binary values, meaning that the
connections or edges in the graph are unweighted.
You can find an example of bfs ordering in Fig.7 of our blogpost:
https://davide-belli.github.io/toulouse-road-network.
The attached image might also help you understanding the slicing. In the
image they talk about bfs frontier. In our case this is the same as the
last nodes in the bfs ordering.
Let me know if you have any other questions and good luck with your project.
Best,
Davide
On Wed, 26 Jan 2022, 12:52 Guo Zixun(Nicolas), @.***>
wrote:

Hi Davide,
Thank you very much for the work.
I have some trouble understanding the adjaceny matrix. For instance a
graph with n nodes. The bfs adjaceny matrix will have dimension(n,
max_prev_node). I wonder what does  represent?
Thank you!
Best,
Nicolas
—
Reply to this email directly, view it on GitHub
https://github.com/davide-belli/toulouse-road-network-dataset/issues/1,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AETXKXHOQMWFZT66XUGBY4TUX7OBFANCNFSM5M22QOZA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Add TLS support to Dialer and Listener with configuration options

Introduce TLS configuration options for both the Dialer and Listener, enabling secure connections. This update includes example usage for establishing encrypted and authenticated communication.

Codecov Report
Attention: Patch coverage is 76.47059% with 8 lines in your changes missing coverage. Please review.

Project coverage is 74.26%. Comparing base (da02d98) to head (9ee1c94).

Files with missing lines
Patch %
Lines

listener.go
60.00%
7 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #10      +/-   ##
==========================================
+ Coverage   74.18%   74.26%   +0.07%
==========================================
  Files           6        6
  Lines         616      649      +33
==========================================
+ Hits          457      482      +25
- Misses        116      123       +7
- Partials       43       44       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


macos m1 pro install vnpy_evo error,ERROR: Failed building wheel for ta-lib

macos m1 pro install vnpy_evo error
step:
git clone https://github.com/vnpy/vnpy_evo.git
cd vnpy_evo
python setup.py install
pip install -e .

error:

  Using cached https://pypi.tuna.tsinghua.edu.cn/packages/51/f3/8417c284db5b68f958d8421b331cb3d4ab4caf85a7af8110dede55b084aa/pyobjc_framework_ScriptingBridge-10.3.1-cp36-abi3-macosx_11_0_universal2.whl (8.5 kB)
Building wheels for collected packages: ta-lib
  Building wheel for ta-lib (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for ta-lib (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [42 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build/lib.macosx-14.0-arm64-cpython-311
      creating build/lib.macosx-14.0-arm64-cpython-311/talib
      copying talib/abstract.py -> build/lib.macosx-14.0-arm64-cpython-311/talib
      copying talib/deprecated.py -> build/lib.macosx-14.0-arm64-cpython-311/talib
      copying talib/__init__.py -> build/lib.macosx-14.0-arm64-cpython-311/talib
      copying talib/stream.py -> build/lib.macosx-14.0-arm64-cpython-311/talib
      running build_ext
      building 'talib._ta_lib' extension
      creating build/temp.macosx-14.0-arm64-cpython-311
      creating build/temp.macosx-14.0-arm64-cpython-311/talib
      clang -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -I/usr/include -I/usr/local/include -I/opt/include -I/opt/local/include -I/opt/homebrew/include -I/opt/homebrew/opt/ta-lib/include<EMAIL_ADDRESS><EMAIL_ADDRESS>-c talib/_ta_lib.c -o build/temp.macosx-14.0-arm64-cpython-311/talib/_ta_lib.o
      In file included from talib/_ta_lib.c:1235:
      In file included from /opt/homebrew/Cellar/python@3.11/3.11.9_1/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/_core/include/numpy/arrayobject.h:5:
      In file included from /opt/homebrew/Cellar/python@3.11/3.11.9_1/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/_core/include/numpy/ndarrayobject.h:12:
      In file included from /opt/homebrew/Cellar/python@3.11/3.11.9_1/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/_core/include/numpy/ndarraytypes.h:1909:
      /opt/homebrew/Cellar/python@3.11/3.11.9_1/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/_core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: "Using deprecated NumPy API, disable it with "          "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-W#warnings]
      #warning "Using deprecated NumPy API, disable it with " \
       ^
      talib/_ta_lib.c:10268:41: error: no member named 'subarray' in 'struct _PyArray_Descr'
          __Pyx_INCREF(((PyObject*)__pyx_v_d->subarray->shape));
                                   ~~~~~~~~~  ^
      talib/_ta_lib.c:1657:37: note: expanded from macro '__Pyx_INCREF'
        #define __Pyx_INCREF(r) Py_INCREF(r)
                                          ^
      /opt/homebrew/opt/python@3.11/Frameworks/Python.framework/Versions/3.11/include/python3.11/object.h:506:50: note: expanded from macro 'Py_INCREF'
      #  define Py_INCREF(op) Py_INCREF(_PyObject_CAST(op))
                                                       ^~
      /opt/homebrew/opt/python@3.11/Frameworks/Python.framework/Versions/3.11/include/python3.11/object.h:107:49: note: expanded from macro '_PyObject_CAST'
      #define _PyObject_CAST(op) _Py_CAST(PyObject*, (op))
                                                      ^~
      /opt/homebrew/opt/python@3.11/Frameworks/Python.framework/Versions/3.11/include/python3.11/pyport.h:24:38: note: expanded from macro '_Py_CAST'
      #define _Py_CAST(type, expr) ((type)(expr))
                                           ^~~~
      talib/_ta_lib.c:10269:38: error: no member named 'subarray' in 'struct _PyArray_Descr'
          __pyx_r = ((PyObject*)__pyx_v_d->subarray->shape);
                                ~~~~~~~~~  ^
      1 warning and 2 errors generated.
      error: command '/usr/bin/clang' failed with exit code 1
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for ta-lib
Failed to build ta-lib
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (ta-lib)

Please use the following command to install and make sure you have installed XCode and Homebrew before running:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/veighna-global/vnpy_evo/HEAD/install_macos.sh)"


fix(Alert): add prop to open in new tab

Overview

add newTab prop to Alert to open CTA in new tab

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: ABC-123
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

@codecaaron tagging u because u are also working on the Alert component

@natalieweesh we should probably just make this the default behavior.  I can't see a reason why we wouldn't want a new tab.

📬Published Alpha Packages:@codecademy/gamut-illustrations@0.4.19-alpha.bc925c.0@codecademy/gamut-labs@8.1.1-alpha.bc925c.0@codecademy/gamut@20.0.6-alpha.bc925c.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://601873d9d3f3681bab1b7ee0--gamut-preview.netlify.appDeploy Logs

Nit: this is a feat, not a fix :)

📬Published Alpha Packages:@codecademy/gamut-illustrations@0.4.19-alpha.ccc26e.0@codecademy/gamut-labs@8.2.0-alpha.ccc26e.0@codecademy/gamut@20.1.0-alpha.ccc26e.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60187b2b39e10300cecdc7ec--gamut-preview.netlify.appDeploy Logs

ok updated the cta to open in new tab by default, and the prop is now openInSameTab if you don't want to open the cta in a new tab

📬Published Alpha Packages:@codecademy/gamut-illustrations@0.4.19-alpha.b1cc3d.0@codecademy/gamut-labs@8.2.0-alpha.b1cc3d.0@codecademy/gamut@20.1.0-alpha.b1cc3d.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60187d14f0cc230137e05658--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-illustrations@0.4.19-alpha.ffaa3f.0@codecademy/gamut-labs@8.2.0-alpha.ffaa3f.0@codecademy/gamut@20.1.0-alpha.ffaa3f.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://601888d2942f580ca67c0464--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-illustrations@0.4.20-alpha.58665a.0@codecademy/gamut-labs@8.1.2-alpha.58665a.0@codecademy/gamut@20.2.0-alpha.58665a.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6018bfd2b7329f5fb1fc16d8--gamut-preview.netlify.appDeploy Logs


ODC-7182: Add pinned resources customization

Story:
https://issues.redhat.com/browse/ODC-7182
Solution Description:
Add pinned resources customization API based on https://github.com/openshift/enhancements/pull/1285
GIF:
https://user-images.githubusercontent.com/22490998/206478836-20a28adf-aff4-4764-86b8-049b5b3683d7.mov

/cc @jerolimov

/hold

/hold cancel

Added GIF

Changes look good, please make sure the enhancement is updated to reflect what we've agreed upon here and make sure that we get some SME review from the console team and the other reviewers on the enhancement to make sure they're ok with this API
Given recent activity on the enhancement, I'd expect to see an LGTM from @spadgett before we merge

/approve
/assign @spadgett for LGTM

/assign @spadgett

Propagating docs and px acks from the Epic
/label docs-approved
/label px-approved

As we have tested this on a cluster bot (see https://github.com/openshift/api/pull/1351#pullrequestreview-1220587190) and in agreement with @sanketpathak we add QE-approved for this change:
/label qe-approved


DATE PICKER

Good day,
I encountered an error in the date picker component; the date picker shows more dates than only the selected month.

This is my code:

Thank you

Now this is a strange one.
Your code is absolutely correct.
Thanks @resujentoezequiel for bringing this up. I'll look into this.

@resujentoezequiel I cannot seem to reproduce this error. Possible to remove bladewind and reinstall so we see if the problem fixes itself somehow. 😊

After I reinstalled the Bladewind library, the error or bug still appeared.
The tool versions I use are:
PHP - 8.2
Laravel - 11.8
Bladewind - 2.5.13

Okay. I will still try to reproduce this from my end.

@resujentoezequiel are you using other Javascript libraries apart from Alpine.js? Did some reading around and it appears other JS libraries can cause Alpine to reinitialise, resulting in components displaying twice.

Tried several permutations but just can't seem to reproduce this behaviour.

I got this issue and it occured when i added alpine js myself from the website to my , once i removed it, it was fine.


[PDI-17065] - Kafka Consumer step doesn't find sub transformation in …

…some
cases. Fix for localhost resolve

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -Dsurefire.runOrder=alphabetical -B -fn -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd clean install && mvn -B -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd site

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/java/org/pentaho/di/core/util/CurrentDirectoryResolver.java
  engine/src/main/java/org/pentaho/di/trans/StepWithMappingMeta.java
  engine/src/test/java/org/pentaho/di/trans/StepWithMappingMetaTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: <0.1% (click to expand)
org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -0.4% :small_red_triangle_down:
Complexity Change: -0.5% :small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -1.7% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Method Change: -1% :small_red_triangle_down:

org.pentaho.di.trans.steps.excelwriter.ExcelWriterStepMeta

Branch Change: -1.3% :small_red_triangle_down:
Complexity Change: -0.7% :small_red_triangle_down:

org.pentaho.di.trans.steps.ifnull.IfNullMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -1.9% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.StepWithMappingMeta

Branch Change: -0.6% :small_red_triangle_down:
Complexity Change: -0.7% :small_red_triangle_down:

org.pentaho.di.trans.steps.googleanalytics.GaInputStepMeta

Branch Change: -1.9% :small_red_triangle_down:
Complexity Change: -1.1% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.3% :small_red_triangle_down:

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/engine/src/main/java/org/pentaho/di/trans/StepWithMappingMeta.java

:heavy_exclamation_mark: 'if' is not followed by whitespace. at Line: 90 Column: 7

@mbatchelor, @kolinus, @mchen-len-son please review

@pentaho-lmartins, please review

Re-running wingman - this has been open for 13 days, and there could be new conflicts

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -Dsurefire.runOrder=alphabetical -B -fn -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd clean install && mvn -B -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd site

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/java/org/pentaho/di/core/util/CurrentDirectoryResolver.java
  engine/src/main/java/org/pentaho/di/trans/StepWithMappingMeta.java
  engine/src/test/java/org/pentaho/di/trans/StepWithMappingMetaTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: <0.1% (click to expand)
org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -0.4% :small_red_triangle_down:
Complexity Change: -0.5% :small_red_triangle_down:

org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change: -1% :small_red_triangle_down:
Complexity Change: -1% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Branch Change: -1.8% :small_red_triangle_down:
Complexity Change: -1.1% :small_red_triangle_down:
Instruction Change: -0.4% :small_red_triangle_down:
Line Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -3.3% :small_red_triangle_down:
Complexity Change: -3.9% :small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Branch Change: -2.6% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.sort.SortRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.StepWithMappingMeta

Branch Change: -0.6% :small_red_triangle_down:
Complexity Change: -0.7% :small_red_triangle_down:

@pentaho-lmartins, @mbatchelor please merge it. The restarted wingman was successful.


Support HTML5 contentEditable attribute

We should do two-way binding even for other elements than inputs, if there is contentEditable attribute.

:+1:

+1

+1

+1

+1

+1

+1

+1

:heavy_plus_sign:  1

+1

+1

:+1:

👍

+1

Hi everyone,
binding to contenteditable is not something we are going to support in core:

handling contenteditable in a robust and comprehensive way is very complex
Official support would take away a lot of resources from the (small) team that is handling AngularJs 1.x nowadays.
However, even with a larger team, contenteditable would be a huge project that would demand constant attention
We would have to duplicate / include a lot of code that has already been written by others that handles the various browser differences and quirks.
"binding to contenteditable" is not a clearly delineated concept. Support for "simple" binding will grow bigger as browser differences need to be handled, and might raise demand for complete WYSIWYG / rich text editors

Fortunately, there are already projects that handle contenteditable and rich text editors, some that are wrapped to integrate with Angular, and some that are specifically written for it. I didn't have time to test all projects, I just want to highlight textAngulars taBind directive, which handles "simple" contenteditable two-way binding with ngModel. This is as far as I can say the scope of this issue: no fancy editor, but simply a way to have a robust contenteditable that handles different input techniques and browser differences. I've created a plunker that shows a simple contenteditable that has been enhanced with taBind: http://plnkr.co/edit/kKPfk0LCXWrMpZ1gkblb?p=preview (textAngular also provides a full editor if you need one).


added cspc to edu domains

@iamjcoo First stage of verification passed, official domain is cspc.edu.ph as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.


Make compiledtrees work with recent sklearn API (0.21+)

Codecov Report

Merging #32 (98d6e4b) into master (c873907) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #32      +/-   ##
==========================================
+ Coverage   94.43%   94.48%   +0.05%
==========================================
  Files           4        4
  Lines         521      526       +5
==========================================
+ Hits          492      497       +5
  Misses         29       29

Impacted Files
Coverage Δ

compiledtrees/compiled.py
95.20% <100.00%> (+0.17%)
:arrow_up:

compiledtrees/tests/test_compiled.py
97.83% <100.00%> (ø)

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 c873907...98d6e4b. Read the comment docs.


Zones picking in HSQC depends on zoom region

If the HSQC (dataset 'cytisine' from General section) is selected for (manual) zone picking, the two crosspeaks of the diastereotopic H's @ 4.04 and 3.84 are 'recognized' as two peaks, if the zoom for picking is larger than at least the window 48-55 (in 13C) and 2.7-4.3 (in 1H). If you zoom in the latter area first and then do the picking, the right signal is not recognized. I could repeat this several tim

es.

We can not reproduce this problem. Can you upload an animated gif ?

I took a movie, here you can see it (first step - zones with full view, second step - zones from expansion)
bug_616.zip

It seems to me, that it does not appear any longer. What I noticed in the combined dataset (HSQC/HMBC Cytisine) is, that if I display only the HSQC and repeat the zone picking only on the HSQC, the dots to mark the zone frequencies/shifts are not visible
or the same happens (see screenshot

):

seems that the peak is not detected, I will have a look.


docs/README: adding details of how to contribute

Coverage remained the same at 96.499% when pulling 1d73acd1df4d1def97b40c8ad5a7b4a18e8d038f on bochaco:doc-contributing-section into d4cf6e51d3c56f8b38418e8102c3ccd525e39100 on maidsafe:master.

Coverage remained the same at 96.499% when pulling 1d73acd1df4d1def97b40c8ad5a7b4a18e8d038f on bochaco:doc-contributing-section into d4cf6e51d3c56f8b38418e8102c3ccd525e39100 on maidsafe:master.


Update Git to guard process tree walk from infinite recursion.

We found a hard-to-reproduce scenario where trace2_collect_process_info was stuck in an infinite loop walking the process tree. This issue tracks consuming a fixed version of Git.

The fixes for this have been incorporated with
#749
#779
@jeffhostetler - I think we can close this out?

Closing this out since the PRs have been merged.


Fix docker image location in README.md

A part of: #194

So I think we should only change this one when we actually deploy it, because that link will just be broken otherwise.

So I think we should only change this one when we actually deploy it, because that link will just be broken otherwise.

Yup, just created this for the future,

Yup, just created this for the future,

Actually, let me mark this as draft so we don't accidentally merge this.

Actually, let me mark this as draft so we don't accidentally merge this.


fix: move notFoundError to notExistError

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage

What this PR does / why we need it:
If the user set WEBHOOK_HOST environment variable, the webhook certs will be written to filesystem (/tmp/yurt-manager-webhook-certs by default), and the code has a type confusion of notExistError and notFoundError.
This PR also fix a null pointer dereference in updateIfNotExists.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

/LGTM

@fungaren Very appreciated you for posting pull request to fix bug of fs cert management.


Change Sprig Device to just sprig on main website

Change Sprig Device in step three on the main website to just sprig (its kinda known that the sprig is a device so sprig device seems off)

update game count as well from a sad 430 to the grand 800 we have

also finally did the thing i was holding off on. i updated my game to be beatable now 👍
so before it was this

you need to collect all green before you go to blue. If you go to blue early you need to reset so this was flawed so i removed that one green that is blocked

Also added a new level

ok so since i found a burst of inspiration heres a summary of what i did
1)update main website to not say "sprig device" and just say sprig
2) update game count on main website
3) update my own game so its beatable + audio

Changes to your game look good.
Change to the number of games looks good.
Not sure about 'sprig device', believe that's intentional.

alrighty ill change that back then

im getting carpet bombed with emails what is this 🙏


feat: Classes and instances for bitwise operations.

This declares notation (similar to that in F#) for bitwise operations, and declares supporting classes and instances.
No tests have yet been written, but I can add that if you have suggestions for where to put them.  This goes beyond what is in  #321 as far I can tell but does not include the tests from that.

I'm happy to create an issue to discuss or use Zulip to discuss the notation if that would be useful.  I looked at several different language choices before settling on the consistent triple-repeated symbols that F# used, but Unicode or other choices would be more concise.

@leodemoura @Kha I consider this robust enough to consider merging, but I'll definitely respond to comments if there are additional issues.  It's useful to rebase to master, I can do that, but it may be easier for you to rebase/merge when it doesn't conflict with other work.

merged


(ios15.6b1 iphone x) found internal error: No cdhash found. str loc at 0x12d2da4 and str ref at 0x12d2da

Not bug.

this is patching the kernel, please show the actual error


setup.py looks for libraries outside python 3.6 environment; possibly broken?

We install aix360 as specified in instruction using python 3.6 in a conda environment on Mac.

"conda create --name aix360 python=3.6
conda activate aix360"

Then we do clone without issue
"git clone https://github.com/Trusted-AI/AIX360
"

Now we setup dependencies
"pip install -e ."

However, the setup.py is looking and installing outside the 3.6 environment it seems. Error below.

Preparing metadata (setup.py) ... done
Requirement already satisfied: joblib>=0.11 in /usr/local/lib/python3.9/site-packages (from aix360==0.2.1) (1.1.0)
Requirement already satisfied: scikit-learn>=0.21.2 in /usr/local/lib/python3.9/site-packages (from aix360==0.2.1) (1.0.1)
Requirement already satisfied: torch in /usr/local/lib/python3.9/site-packages (from aix360==0.2.1) (1.10.0)
Requirement already satisfied: torchvision in /usr/local/lib/python3.9/site-packages (from aix360==0.2.1) (0.11.1)
Collecting cvxpy==1.0.31
Using cached cvxpy-1.0.31.tar.gz (947 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: cvxopt in /usr/local/lib/python3.9/site-packages (from aix360==0.2.1) (1.2.7)
Requirement already satisfied: Image in /usr/local/lib/python3.9/site-packages (from aix360==0.2.1) (1.5.33)
ERROR: Could not find a version that satisfies the requirement tensorflow==1.14 (from aix360) (from versions: 2.5.0rc0, 2.5.0rc1, 2.5.0rc2, 2.5.0rc3, 2.5.0, 2.5.1, 2.6.0rc0, 2.6.0rc1, 2.6.0rc2, 2.6.0, 2.7.0rc0, 2.7.0rc1)
ERROR: No matching distribution found for tensorflow==1.14
A hack to overcome this error was to install tensorflow manually.
Example: python3 -m pip install --upgrade https://storage.googleapis.com/tensorflow/mac/cpu/tensorflow-1.12.0-py3-none-any.whl

But when we can go to examples/tutorials and try HELOC notebook
aix360 is not found

Even if we do (!pip install aix360) to install within the conda python 3.6 environment, the installation does not help.
Is setup.py broken?
I tried on another Mac where I had python=3.7 installed and there was no problem.

Hey @biplav-s i too am facing the same issue when installing aix360==0.2.1, i tried creating an env with python3.6 and i was successfully able to install tensorflow==1.14, but it also has a torch dependency which is only available in pythonversions>=3.6.2 in which tensorflow==1.14 is not there.

i tried python3 -m pip install --upgrade https://storage.googleapis.com/tensorflow/mac/cpu/tensorflow-1.14.0-py3-none-any.whl for the error of tensorflow==1.14.0 not found

If your setup.py script is looking for libraries outside the Python 3.6 environment, there are a few potential reasons for this behavior. Here are some steps you can take to troubleshoot and address the issue:
Check Python Version Compatibility:
Ensure that the libraries you are using in your project are compatible with Python 3.6. Some libraries may require a higher version of Python, and if your setup.py script is attempting to install them in a Python 3.6 environment, it might lead to issues.
Update Python:
Consider updating your Python version to a more recent one, especially if the libraries you are using have dropped support for Python 3.6. You can use a virtual environment to manage Python versions for your project.
bash
Create a virtual environment with Python 3.6
python3.6 -m venv myenv
Activate the virtual environment
source myenv/bin/activate  # On Linux/macOS
or
myenv\Scripts\activate  # On Windows
Install dependencies
pip install -r requirements.txt
Review Dependencies:
Check your requirements.txt file or any other dependency file for specific version requirements. Make sure that the versions specified are compatible with Python 3.6.
Explicitly Specify Python Version in setup.py:
In your setup.py file, you can include a python_requires argument to specify the required Python version. For example:
python
setup(
# other setup.py configurations
python_requires='>=3.6,<3.7',
)
This helps ensure that the package is only installed in Python environments that meet the specified version requirements.
Consider using tox for Testing:
If you want to test your package against multiple Python versions, you can use a tool like tox. tox can create virtual environments for different Python versions and run your tests in each. This can help identify compatibility issues.
Check for Environment Variables:
Sometimes, issues might arise if there are conflicting environment variables affecting the Python interpreter's behavior. Check for any environment variables that might be influencing the Python environment.
Check Installation Log/Error Messages:
When you encounter issues during the installation process, review the error messages or logs. They often provide valuable information about what went wrong.
By addressing these points, you should be able to identify and resolve the issue with your setup.py script looking for libraries outside the Python 3.6 environment.

"I'm unable to recreate the installation errors mentioned ... on mac."

Try again.  ("I'm unable to recreate the installation errors mentioned ... on mac.")


Inconsistent processing of large numbers from other languages.

Because javascript cannot process large numbers, it becomes extremely difficult to work with integrated systems.
We have Java applications storing large long values to Datastore, which now has a type Integer in Datastore.  These are then unable to be read by systems using node.
While the node version can also STORE large values by using the datastore.int() method, when reading the value out of the database, it is automatically read as a number javascript type, and therefore truncated.

True, we currently return raw Number values for integer and double values. (Lines for reference: https://github.com/googleapis/nodejs-datastore/blob/357839b76f8c8b5e87cd44b350fefbc2d6c9d138/src/entity.js#L270-L276)
We should probably return our custom types, Int and Double. The downside is that the majority of the time, the user will want the parsed Number, as their values aren't out of bounds. However, we don't have any support for when a value is out of bounds, which isn't too good.
@JustinBeckwith any thoughts on if we should make this breaking change? I believe breaking changes don't scare us anymore?

Yeah I have already published a npm package just for us that uses the ‘long’ npm library, but using the Datastore “native” Int and Double objects would be preferable, if they support math operators (which I dont think they do). Otherwise I would say go with ‘long’ for Int and maybe ‘big-decimal’ or something for Double.
But from our side, break away with the changes! Claim it in the name of progress ;)

I kind of think we should take a similar approach to whats being suggested in https://github.com/googleapis/nodejs-bigquery/issues/6, essentially allowing a user to specify custom types to cast to. This has the added benefit of not being breaking.
@stephenplusplus @bcoe @JustinBeckwith thoughts?

@callmehiphop I very much like the idea of a consistent approach between the two libraries :+1:

@callmehiphop could I ask you take this one on?


[feature request] Numpy 2 compatibility

It seems like it is quite easy to make Thunder support NumPy 2, modulo dependencies (fdm, for example).
A temporary fix could be disabling envs with NumPy 2 in our CIs, https://github.com/Lightning-AI/lightning-thunder/pull/617.

triage review: let's do it! fdm is no longer supported; let's do what we need to refactor its use in tests or copy/fork the relevant code and update it


[rollup-plugin-index-html] Files emitted using Rollup emitChunk are incorrectly imported inside html.

JavaScript files emitted from plugins using Rollup emitChunk are incorrectly imported inside outputted html file. One example is https://github.com/surma/rollup-plugin-off-main-thread which outputs worker file to be later imported by worker itself. rollup-plugin-index-html creates script tag for it inside html file even though it shouldn't.
Probably related to https://github.com/open-wc/open-wc/issues/1153 using new assets api.

We've released @open-wc/rollup-plugin-html which addresses this.


Implementation of CI/CD in C/C++ Application(Linux) Using Shell and Docker Executor on GitLab

Proposed title of article
Implementation of CI/CD in C/C++ Application(Linux) Using Shell and Docker Executor on GitLab
Introduction paragraph (2-3 paragraphs):
Many executors with GitLab Runner are available for implementing CI/CD. Nevertheless, Shell and Docker are more popular with them and with these runners we can easily create a repository. These runners can be chosen based on the requirements and availability of the resources.
This article focuses mainly on the C/C++ Linux application's Shell and Docker executor and code in the Bash script is written. A bash script can be used to build and test the application.
Key takeaways:
In this article, the reader will understand:

what docker and shell executors are.
implementation of C/C++ on Shell Executor.
implementation of C/C++ on Docker Executor

References:
N/A

@carteblanchemunene
Sounds like a helpful topic - lets please be sure it add value beyond what is in the official docs and that it does not overlap with any existing EngEd articles or incoming topic suggestions (if you haven't already) to avoid any potential article closure. - approved


Task: Setup Infrastructure for Authentication BFF

Description
We need to setup infrastructure for Authentication
Additional Information
No response
Tasks
No response
Acceptance Criterias

[ ] Azure Container app i setup for all test environments
[ ] Deploy scripts for all environments in Github

see also task #41


Fetch params error

Since this morning i’m not able to control my AC anymore. I’ve updated the package this morning but no result. Have rebooted my complete system without results. Any help would be appreciated.
midea-air[MideaPlatform.ts] sendCommand (Intent: [updateValues] (fetch params?) attempt 1/2) returned error Invalid param wrong format: shadow_control_async response:null, 1001

Disabling plugin and rebooting homebridge worked.


[docs] Create docs to recommend when to use each API

Steps to reproduce
We have 3 main APIs in Pigment CSS: https://react-conf-2024-pigment-css.netlify.app/?slideIndex=31&stepIndex=0

I would much rather not make the same mistake as in https://youtu.be/UlY-Ixddjm0?si=WTs9IU9K47mOfUzE&t=1538. Meaning, we should document clearly when to use each prop so developers get consistency.

styled API:
Pros:

https://github.com/mui/pigment-css/issues/86#issuecomment-2132689102 can respond do props more easily.

Cons:

https://github.com/vercel/next.js/issues/35030 hides the host element to eslint rules.
Need to come up with names

Current behavior
No response
Expected behavior
No response
Context
No response
Your environment

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Search keywords: -

@oliviertassinari does/will Pigment CSS ever support the css prop like Emotion? For instance:

or is the solution here to use the css method? For instance:

@damusnet I doubt it. The sx prop seems to serve the same purpose.

Gotcha, thanks for the quick reply.
I was under the impression that sx was a little different, with support for things like px and py (that's fine), but maybe also stricter requirements (thought I read that border has to be a number, and can't be 1px solid red for instance). If it's a perfect superset, then that's great.

@damusnet The sx prop is meant to be a superset of the css prop, so border: 1px solid red should work.


Better error message for Backend Error

b/11969636
Currently some non transactional write can failed with:
Backend Error

We should provide a more comprehensive error about what happens, and hint the user that he should retry the operation.

API error messages are generally more informative in the v1beta3 API. In particular, query results are returned in smaller batches, so the API will not return "Backend Error" this scenario.


The current branch highlight in the graph

Hi source git team
Nice work! I like your client.
In the graph, it's hard to find the current branch. Is it possible to highlight it somehow? Bigger font, border, or anything else?

P.S. The branch on the screenshot looks better than on the actual screen because github scaled the image :)

There're two ways to locate current branch HEAD in commit histories.

Click the Navigate to HEAD button on the right of toolbar (just behind the name of current branch)
Select current branch from local branch tree

BTW, you can toggle the Only use monospace font in text editor option from Preference panel. It makes the HEAD commit more clear.

"Navigate to HEAD" - wow, so cool.
But it should be more obvious which branch is selected in the graph. It would be awesome if you could improve it :)

Git Extension does have pretty nice commits graph visual guides that could be taken as inspiration maybe

Git Extension does have pretty nice commits graph visual guides that could be taken as inspiration maybe  Also, seems quite similar to #388

Git Extensions also uses a bold font for the current branch.

SourceGit also use bold style current branch name and HEAD commit subject, you can turn on the Only use monospace in text editor option (bold style of monospaced font is a little bit hard to tell)

SourceGit also use bold style current branch name and HEAD commit subject, you can turn on the Only use monospace in text editor option (bold style of monospaced font is a little bit hard to tell)

Yes, I know. It's just not enough. It needs to be a bit bolder or bigger font size or something like that :)
It's not just me, I also showed the UI to my wife before creating the issues. She also can't tell which one is the current.

Yes, I know. It's just not enough. It needs to be a bit bolder or bigger font size or something like that :)
It's not just me, I also showed the UI to my wife before creating the issues. She also can't tell which one is the current.

I know the reason that why it is still hard to tell when you toggle the Only use monospace in text editor option. It is still a font issue. I've pushed commit that try to fix it.

Thank you! Looks much better! I hope I'll be able to try it myself soon :)

you can download the latest build from https://github.com/sourcegit-scm/sourcegit/actions/runs/10523555062

Cool! Yes, it's better. But I think it's possible to do it a bit better. Maybe you can change the checkmark background color? Maybe blue color like you doing with selected elements?
Thank you!

It's not just me, I also showed the UI to my wife before creating the issues. She also can't tell which one is the current.

me too

Cool! Yes, it's better. But I think it's possible to do it a bit better. Maybe you can change the checkmark background color? Maybe blue color like you doing with selected elements? Or green? Thank you!

It's even more invisible than the one next to it.

Cool! Yes, it's better. But I think it's possible to do it a bit better. Maybe you can change the checkmark background color? Maybe blue color like you doing with selected elements? Or green? Thank you!

It's even more invisible than the one next to it.

I mean background color, not a checkmark color. Blue background with a white icon. Or a green background with a white icon.
Can you try both variants? Sorry for bothering you.

I did it in ms paint 😂

Yes, I think you are in the right direction. It can be an icon background color or a branch name background color.
The color is not ideal for your color scheme. If you can play with it a bit more, it will be ideal.

I'm using this tool when I need additional color: https://coolors.co/

Dark Theme

Light Theme

@love-linger amazing! I love the dark one!

@love-linger

please try a white font color for the white theme. I think it looks better.

i'm not good at choosing colors, and I'm also not satisfied with the color scheme with the light theme...
It's a little difficult for me to find a suitable color. This needs to meet some conditions

it must be very different from existed colors, such as tags and normal branches
it should not use common accent colors

it would be nice if someone can help

it must be very different from existed colors, such as tags and normal branches
it should not use common accent colors

Maybe plain black could be enough for the light theme ? As it would be consistent with the white background that work rather well with the dark theme.
It's pretty simple but would stay unique in the current UI guidelines.

@love-linger please try inverted color from the dark theme - #0c0e21 with font color.

thank you very much. it looks nice. I will try it later

Look how Fork did it. They are using branch color for the branch name background and check mark for the current branch.

I do not want to make the UI/UX so complex.

Love it, it's much better!

So, I'm going to close this issue as complete.

Yep! Please push release to winget :)

The next version will be released next Monday, but WinGet users may need to wait one more day. This is because the PR submitted to WinGet is usually merged after one day.


Add a link to unix cheatsheet

Participants will be helped by a unix cheatsheet (as in the RNA-seq course)

fixed in #7


docs: include input and output

Description
Updates formatting and includes outputs table for reference. Based off #43.

Thanks @jef 😄


[backport] Increase timeout for CUDA 11.4 tests

Backport of #5575 by @kmaehashi

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit f0870dcfd7b1e6a28056e3252bf3142e6abe5568, target branch v9) succeeded!


DAG width wrong for parent runtime deployment triple

A test case for a bug in DagWidth

The main idea of the fix is to run the DagWidth algorithm on a transitive reduction of the original graph https://github.com/mvndaemon/mvnd/pull/286/commits/cb751474081013a6fbc7e73b7c553e233cd48d3e#diff-2567c5271a1b768680b79edefa025cd2515042e76bbd938626afb3c0ff817b2eR314-R345
As noob as I am in the Graph theory, I am not able to tell the Graph with algorithm now works correctly in all cases, but at least I was not able to find a counterexample.

Looks good to me.

Looks good to me.


chore: upgrade sn-api dependency

This change is

Codecov Report
Attention: Patch coverage is 96.29630% with 1 line in your changes missing coverage. Please review.

Project coverage is 82.11%. Comparing base (a78159d) to head (a08d5bf).
Report is 1 commits behind head on main.

Files
Patch %
Lines

crates/gateway/src/gateway.rs
80.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #343   +/-   ##
=======================================
  Coverage   82.11%   82.11%
=======================================
  Files          32       32
  Lines        1560     1560
  Branches     1560     1560
=======================================
  Hits         1281     1281
  Misses        215      215
  Partials       64       64

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Implement it in mono-repo once it's ready.


Bug 2089797: Cache object storer for subsequent uploads

Currently for each s3 profile that the PVs need to be
uploaded to, we connect to the s3 store for each volume
that is protected by the current instance of VRG.
This causes a 2 minute slowdown in case the s3 store is
unreachable, which can happen during failover cases.
For a workload with n PVCs as a result the failover takes
n*120 seconds, which is far too long.
This is fixed by connecting to the s3 profile once per VRG
reconciliation, and using the cached connection/storer to
perform subsequent uploads or error out immediately.
Alternative: was to upload PVs post creating VRs for the same
but that would still reconcile the current VRG for n*120
seconds in the second loop, hence is dropped as an
alternative.
Signed-off-by: Shyamsundar Ranganathan<EMAIL_ADDRESS>

@BenamarMk @raghavendra-talur @raghavendrabhat PTAL!

/bugzilla refresh


Update demo.html

google closure has moved to github

The next release will include a similar fix (making the URL relative as in the JavaScript tests).


Links in summary pointing to build scans apply latest query capabilities

Filter to executed, cacheable tasks using the recently introduced negation filter.
For Maven and Gradle.

Fixed for both Gradle and Maven in:

https://github.com/gradle/gradle-enterprise-build-validation-scripts/commit/7c910efdb48d1865c4b6e6aa01afea55e637c4a5
https://github.com/gradle/gradle-enterprise-build-validation-scripts/commit/05d6bf218758b439b1ed1f28cfce1a843d5af2d5


WARNING: redefinition of system 'generic': already defined in '`

This warning message is preventing the ReFrame building the required files without any error messages.
(myvenv2) [br-kolgu@login-02 excalibur-tests]$ reframe -c benchmarks/apps/babelstream -r --tag stddata
WARNING: redefinition of system 'generic': already defined in '<builtin>'
WARNING: redefinition of partition 'generic:default': already defined in '<builtin>'
[ReFrame Setup]
  version:           4.2.0
  command:           '/lustre/home/br-kolgu/excalibur-tests/myvenv2/bin/reframe -c benchmarks/apps/babelstream -r --tag stddata'
  launched by:       br-kolgu@login-02
  working directory: '/lustre/home/br-kolgu/excalibur-tests'
  settings files:    '<builtin>', '/home/br-kolgu/excalibur-tests/benchmarks/reframe_config.py'
  check search path: '/lustre/home/br-kolgu/excalibur-tests/benchmarks/apps/babelstream'
  stage directory:   '/lustre/home/br-kolgu/excalibur-tests/stage'
  output directory:  '/lustre/home/br-kolgu/excalibur-tests/output'
  log files:         '/tmp/rfm-1l0byjli.log'

[==========] Running 0 check(s)
[==========] Started on Fri May  5 10:49:10 2023

[----------] start processing checks
[----------] all spawned checks have finished

[  PASSED  ] Ran 0/0 test case(s) from 0 check(s) (0 failure(s), 0 skipped, 0 aborted)
[==========] Finished on Fri May  5 10:49:10 2023
Log file(s) saved in '/tmp/rfm-1l0byjli.log'

So it prints out test passed but the output or stage folders are not generated
The following change at the reframe_config.py file solves this issue:
        # {
        #     'name': 'generic',
        #     'descr': 'generic',
        #     'hostnames': ['.*'],
        #     'partitions': [
        #         {
        #             'name': 'default',
        #             'descr': 'Default system',
        #             'scheduler': 'local',
        #             'launcher': 'mpirun',
        #             'environs': ['default'],
        #         },
        #     ]
        # },  # end generic

Solved with the PR #141  comments


Feature Request: time component

Is there a simple way to consider / include time series data (or an arbitrary extra component/unit) or is this better left to post processing? E.g something that could solve for the following:
// a simple track
const timed = [
  { x: 0, y: 0, t: 0},
  { x: 0, y: 1, t: 1}, // speed == 1/t
  { x: 0, y: 1, t: 2}, // speed == 0
  { x: 1, y: 0, t: 3}, // speed == 1
];

simplify(timed, 0.5);
/*
[
  { x: 0, y: 0, t: 0},
  { x: 0, y: 1, t: 1}, // speed == 1
  { x: 1, y: 0, t: 3}, // speed == 0.5
];
*/

The algorithm is purely geometric and only considers the x and y coordinates, although it will still work as above (filtering out the duplicate point).

The algorithm is purely geometric and only considers the x and y coordinates, although it will still work as above (filtering out the duplicate point).

No worries - thanks for quick response; yes, above was the expected output from a purely geometric output (which shows losing the time context). Would you consider merging a branch for a time dimension (4D), similar to the 3D branch? Specifically for gps tracks.

No worries - thanks for quick response; yes, above was the expected output from a purely geometric output (which shows losing the time context). Would you consider merging a branch for a time dimension (4D), similar to the 3D branch? Specifically for gps tracks.

FYI - I was able to get a suitable result by running a second simplification on a speed vs time curve and combining with the position curve. The idea is not to lose speed variations on straight line geometries.
@mourner I notice your github pages example doesn't use lng, lat ... but in some issue responses you suggest mapping { x: lng, y: lat }. Would you expect any significant effect on curves spanning that much lat given non-linear lng distance?

FYI - I was able to get a suitable result by running a second simplification on a speed vs time curve and combining with the position curve. The idea is not to lose speed variations on straight line geometries.
@mourner I notice your github pages example doesn't use lng, lat ... but in some issue responses you suggest mapping { x: lng, y: lat }. Would you expect any significant effect on curves spanning that much lat given non-linear lng distance?

@theprojectsomething yeah, it may be a little skewed if you run it on the raw lng/lat coordinates, however you can mostly fix this (at least on city-level data) by scaling y values by Math.cos(lat * Math.PI / 180) prior to simplification (and then scaling back the output), where lat is the general latitude of the input (e.g. the first point).

@theprojectsomething yeah, it may be a little skewed if you run it on the raw lng/lat coordinates, however you can mostly fix this (at least on city-level data) by scaling y values by Math.cos(lat * Math.PI / 180) prior to simplification (and then scaling back the output), where lat is the general latitude of the input (e.g. the first point).


Event factory for handoff protocol

From https://github.com/microsoft/BotBuilder-Samples/tree/master/experimental/handoff-library with minor changes

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3

Pull Request Test Coverage Report for Build 104086

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 78.06%

Totals

Change from base Build 104013:
0.03%

Covered Lines:
21233

Relevant Lines:
27201

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3


Integrate nwb?

Maintenance-wise it would be a good idea to consume the configuration from a project such as https://github.com/insin/nwb . Now the problem is that it becomes quite painful to manage multiple projects that are based on the boilerplate.

Let's skip this. It's probably better to push some of that webpack configuration elsewhere and go from there.


Support user-defined types when generating schema

Currently, the schema function in ApiV1.kt does not handle user-defined types correctly. If a field has a type with a UDT registration, the corresponding UserDefinedType should be used as schema.
I've drafted an implementation at https://github.com/gschulze/kotlin-spark-api. However, I'm not sure whether this is the right place to do it.

Thank you very much!
Could I please ask you to create minimalistic example with UDT for me to be able to test it?

Hi, sorry for the late reply. I suggest waiting until both Support for Spark 2.4.x and 3.x has landed. I am happy to work on the issue once the structure has been finalized.

You'll be disappointed by new structure, but I don't have any idea on how to improve it yet :(

I suggest using Maven profiles whenever possible to target different Spark/Scala versions. I'll try to come up with something and open a separate issue.

I thought about it, but there are some troubles: most important parts (scala code and kotlin code creating encoders and so on, not extensions) are different. Also, that's not possible (IIRC) to release from different profiles at same time.

I filed a new ticket for building for specific environments, in particular Scala 2.11: https://github.com/JetBrains/kotlin-spark-api/issues/59

@gschulze with a couple of issues we already have working (and better!) implementation for both Spark 2.4 and Spark 3.0, so we can continue discussion on topic


API that returns the ranges modified

This would be an altered diff mode that returns the lines modified and the new lines, rather than a standard diff. Useful for embedding in IDEs.

I'd like to have a go at this.  It looks to me like what's needed is another function a lot like format_input(), but which instead of taking an reference to a T:Write to write the output returns something like Vec<(lineno, num_lines, Vec<String>)> in the Ok path for the lines changed.  I guess the WriteMode in the config would be ignored, but it would do the same as with WriteMode::Diff except for the formatting of the result.
I don't think any visible change to the rustfmt binary is needed or makes sense (though maybe similar information returned as JSON might be useful if anything wants to run the rustfmt binary instead of using the library.
Am I thinking along the right lines?

Hi @jugglerchris it would be great if you could have a go at this! (I'm on parental leave right now, so will be a bit slow to respond). Ideally we would just add another write_mode, but I guess that might be difficult. If that doesn't work, then adding a new function as you suggest sounds good. It would be nice to share as much code as possible between  the new function and format_input as possible since format_input is a bit complex.

I thought about a new write mode, but that doesn't directly help the RLS (which I understand is the motivating use case), since format_input can only return via the Option<&mut T:Write>.
I'll see if I can get something working and see how it goes!


Nuxt application page is empty while npm run builld is running

The nuxt application is running using npm start and its fine until you run npm run build is run on the background then the page will become empty (plain white page). Im using pm2 to supervise the application and restart when terminated and manually restart after build is finished (application will work again after restart). Then problem is the build time taking so long users may see empty page.
My question is, is this intended behavior? If yes, please let me know has to properly address it. thank you very much.
Versions

nuxt: v2.13.3
node: v10.18.1

Steps to reproduce
run npm start on 1st terminal then npm run build on 2nd terminal and visit any page.
What is Expected?
The application should maintain running and use the previous build files
What is actually happening?
I think the reason is the build is being removed from the server and browser cant get the requested page (404).

@jariesdev Yes, when the new build starts it deletes the last build's files. I'd suggest copying them to another directory in a Nuxt build hook and then serving that directory, assuming you want to use the pattern you've suggested.

@danielroe Thank you for quit response and for the suggestion I will try that. On the other hand, Im thinking of using cache such as nuxt-ssr-cache and I assume it will serve the cached files even i run build. I will try the build hook.

It is intended. You are not supposed to really run build on server for any production grade app. Use ci/cd, docker, etc

I walked in the same issue (kind of) with version v2.13.3. If you create a production version of your project (nuxt build) and then run it, it can't find a .xxxxxx.js file in the /dist/commons/ directory, but if you look in the directory the file is there. Maybe it's something with rights because of the dot before the file it's a hidden file. For now, we switched back to v2.13.2

@frontwero That is a different issue and will be fixed in 2.14 with https://github.com/nuxt/nuxt.js/pull/7667

@jariesdev I'm closing this as this is intended behaviour - but thanks for raising it! Feel free to get in touch on the Discord server if you have any more questions.


Adds queues

Description
Adds queue support.
Checklist

[ ] Add tests for these changes
[ ] Test coverage is not decreased
[ ] Entire test suite passes

Codecov Report

Merging #1 into master will increase coverage by 4.43%.
The diff coverage is 91.50%.

@@            Coverage Diff             @@
##           master       #1      +/-   ##
==========================================
+ Coverage   80.50%   84.94%   +4.43%
==========================================
  Files           4        5       +1
  Lines         277      352      +75
  Branches       40       50      +10
==========================================
+ Hits          223      299      +76
+ Misses         49       46       -3
- Partials        5        7       +2

Impacted Files
Coverage Δ

src/spellbot/__init__.py
78.18% <85.71%> (+4.29%)
:arrow_up:

src/spellbot/data.py
100.00% <100.00%> (+2.38%)
:arrow_up:

.../spellbot/versions/versions/6f160f1bf688_queues.py
100.00% <100.00%> (ø)

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 97ed419...446bed3. Read the comment docs.


[AKS] Restarting AKS will trigger a circular dependency on admission-webhook

Hi,
When deploying Charmed Kubeflow on AKS, kubeflow will prevent the cluster from restarting sucessfully, this is due to the admission-webhook pod getting stuck in it's juju-pod-init container.
Removing the mutatingwebhookconfiguration using kubectl resolves the situation and allows the cluster to heal.
[Steps to reproduce]
az aks create -g kubeflow-repro -n aks-repro-2 --kubernetes-version 1.21.7 --node-count 2 --node-vm-size Standard_B4ms --dns-name-prefix kf-sndbox -l westeurope --generate-ssh-keys
juju add-k8s --aks --resource-group kubeflow-repro --cluster-name aks-repro-2 aks-repro-br --storage default
juju bootstrap aks-repro-br
juju add-model kubeflow
juju deploy cs:kubeflow-lite

wait for the model to settle.
#### Reboot the cluster
az aks stop -n aks-repro-2 -g kubeflow-repro
# Wait for stop, then start the cluster,

az aks start -n aks-repro-2 -g kubeflow-repro
Observe the admission webhook gets stuck with:

kubectl get pods -A

Expected output:
Every 2.0s: kubectl get pods -A --context aks-repro-2

Every 2.0s: kubectl get pods -A --context aks-repro-2

NAMESPACE     NAME                                  READY   STATUS              RESTARTS   AGE
kube-system   azure-ip-masq-agent-mg7jx             1/1     Running             0          32s
kube-system   azure-ip-masq-agent-p4v2n             1/1     Running             0          22s
kube-system   coredns-845757d86-n7ctv               1/1     Running             0          8m42s
kube-system   coredns-845757d86-zfx9n               1/1     Running             0          8m42s
kube-system   coredns-autoscaler-5f85dc856b-pjdwq   1/1     Running             0          8m12s
kube-system   csi-azuredisk-node-k7mwr              3/3     Running             0          32s
kube-system   csi-azuredisk-node-xs4kl              3/3     Running             0          22s
kube-system   csi-azurefile-node-shsdf              3/3     Running             0          22s
kube-system   csi-azurefile-node-zggsb              3/3     Running             0          32s
kube-system   kube-proxy-8hnfv                      1/1     Running             0          22s
kube-system   kube-proxy-llw27                      1/1     Running             0          32s
kube-system   metrics-server-6bc97b47f7-rns96       0/1     Running             0          9m12s
kube-system   tunnelfront-f86fb4dbc-hmc8z           1/1     Running             0          8m12s
kubeflow      admission-webhook-7cd7d7796f-gg8tz    0/1     Init:0/1            0          8m12s
kubeflow      admission-webhook-operator-0          0/1     ContainerCreating   0          9m12s

[Workaround]
kubectl get mutatingwebhookconfigurations kubeflow-admission-webhook  -o yaml > kubeflow-webhook-config.yaml
kubectl delete mutatingwebhookconfigurations kubeflow-admission-webhook
# ..... wait for the cluster to heal. Waiting for admission-webhook to get to Running state.
# delete the uid and version elements of the YAML
kubectl apply -f kubeflow-webhook-config.yaml

Thanks,
Peter

hey @ca-scribner yes, here's the logs from the initContainer:
➜  aks kubectl logs -n kubeflow admission-webhook-575c9647c6-rpf5s -c juju-pod-init
2022-01-13 11:46:08 INFO juju.cmd supercommand.go:56 running jujud [2.9.22 0 07164c4b2c6a9f5b576b1c151bd85dd3a699be16 gc go1.14.15]
2022-01-13 11:46:08 DEBUG juju.cmd supercommand.go:57   args: []string{"/var/lib/juju/tools/jujud", "caas-unit-init", "--debug", "--wait"}
➜

I have tried to apply this workaround twice. Once it worked fine, but the second time the kubeflow-webhook-config.yaml was not applied correctly because the configuration of it changed meanwhile during kubeflow restart.

I have been able to reproduce this issue and we will look into a possible fix.

Hi @VariableDeclared, thanks for reporting this. I was able to reproduce the issue on AKS, just as you described. Apparently this is an issue with juju, in fact there have been multiple reports similar to this one. I have filed a bug (as the juju team requested) so we can find out a reliable workaround or a solution.
In the meantime, we can use your proposed workaround.

I am closing this issue as we are tracking the issue in launchpad. Feel free to re-open it or file a new one if you run into other issues.


Custom login HIJACK_AUTHORIZATION_CHECK not working like described in doc

At current moment it also REQUIRE change of decorator to

HIJACK_DECORATOR = 'django.contrib.auth.decorators.login_required'

or other similar decorator.
This not described in doc and require read almost full source code to understand.
without that code always ask for staff user/password is source user is not staff, so custom authorization check usless and not work.
Possible solution:

change default decorator to login_required
put into doc in section for HIJACK_AUTHORIZATION_CHECK note about need of change  HIJACK_DECORATOR too.

Most likely your request is no longer relevant after the release of version 3.0 (currently in pre-release status). If it is not, please reopen your ticket.


Adding new config and fixing formatting for tap-rest-api-msdk.

Adding the following new parameters to support the following PR made to tap-rest-api-msdk : https://github.com/Widen/tap-rest-api-msdk/pull/39.

backoff_type
backoff_param
backoff_time_extension
store_raw_json_message

These parameters are used to support the following three features to delivery required functionality for a new API.

It contains enhanced logic in the tap discovery to cache credentials to avoid having to re-authenticate for each stream. The API was erroring due to too many OAuth Requests in a quick succession.
Optional backoff logic has been built in allowing tap-rest-api-msdk to respond to http retry-after messages. This is configurable to use either the header or message responses. There is also a new setting which adds some additional time because sometime the requested wait time is longer enough. This feature was built in to meet the API's backoff requirements.
Optionally provides the ability to store the whole raw message. The feature is enabled by setting the store_raw_json_message to true. This is useful if you wish to offload, the flattening functionality to the likes of dbt. Where I have used this feature I tend to select only the primary key, the replication key, and the _sdc_raw_json field.
The use case for this was a dynamic schema with optional fields/columns which were not available in every record. In this situation the schema discovery did not pick up every field leading to missing data, it was elected that storing the raw json record was important - to ensure all data is preserved.

Points 2-3 are optional, and so the tap's behaviour does not change. For Point 1, the caching will speed up discovery and ingestion as credentials are cached.

I believe the review items are complete now and this is ready to be published. Thanks for the review.


Retry CI tests automatically

Using travis_retry command. Sometimes code contributors have to push a commit again to restart the tests failed with server problems. Auto retrying reduces them.

@weswigham Should this issue be closed?


Multiple Duplicate Entries in known_devices.yaml

Home Assistant release with the issue:

0.79.0
Last working Home Assistant release (if known):
0.78.3
Operating environment (Hass.io/Docker/Windows/etc.):

Raspbian
Component/platform:

discovery
Description of problem:
After upgrade to 0.79 my known_devices.yaml now has multiple entries of almost every device (5 atm).
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

What device tracker components are you using?

I have the same problem since updating to 0.80.0.dev0.
I have IOS in my config and using NMAP to track those devices. My own phone is in there four times.

What device tracker components are you using?

Ubus, nmap

I cleared out known_devices.yaml, and started fresh...It seems like the duplicated entries have stopped.

Tried to upgrade to 79.3 (which introduced some ugly bugs), so I reverted to 0.79.1, and the duplicates started again.....on every restart, a new set of items, from seemingly the ubus component.

The problem still persists on latest hassio/home-assistant version using nmap at least.