ObsFit: a new cost function implementation for arbitrary observations (sparse, irregular, integrated, etc)

What changes does this PR introduce?
New "ObsFit" package:
An alternative to the pkg/profiles for model-observations comparisons. Given an observational dataset, ObsFit samples the model during the run at the time and location of observations, calculates the cost (sum of weighted misfits), and produces a model-equivalent output file that is directly comparable to the input file.
What is the current behaviour?
The main cost function options are pkg/ecco, which requires gridded datasets at fixed time intervals, and pkg/profiles, which requires a fixed number of depth levels and instantaneous time instances.
What is the new behaviour
With ObsFit, observations do not need to be on a regular grid or a fixed set of depths, making it an efficient tool for sparse and irregular datasets (e.g., altimetry or tomography data). Observations can be made of multiple samples that are averaged or integrated spatially and/or temporally. This implementation will make assimilation of many constraints much more efficient.
Does this PR introduce a breaking change?
No
Other information:
The code has been made available ( https://github.com/averdy/obsfit_mitgcm ) and already has users
It has been implemented in a simple verification experiment ( verification/global_oce_biogeo_bling )
A "README" file includes details on how to run the example, and how to pre-process observations to use with ObsFit
"To do" list:

ObsFit may not be the best name for this package; alternative suggestions are welcome!
cost_obsfit.F can be very slow for large datasets. This is where tiled fields are read, combined, and written to a global file. There is probably a more efficient way to do this (help appreciated!)
I/O routines active_file_* are adapted from pkg/profiles, which has a known problem with tangent linear runs (PR #873)
Compatibility with LLC grids is in development

Suggested addition to tag-index
New package "ObsFit"

@mjlosch I think I've addressed issues 3-5. Hopefully the verification expt runs now (I can't test it - bad timing).

Thanks @mjlosch ! I'm getting started on the manual entry. The verification experiment has been updated so that the gradient check is sensitive to the observations. I'll try to check if the nf_open/close are necessary (that part was copied from pkg/profiles). Regarding obsfit_inloop being called before the the_main_loop, maybe @jm-c has thoughts?

Regarding NF_OPEN/CLOSE, I found them unnecessary to include in the flow directives. Maybe they were historically required?

ObsFit may not be the best name for this package; alternative suggestions are welcome!

couple ideas :

sparsedata
sparseobs
profiles2 (to highlight the relation to pkg/profiles)
genprof (as in pkg/ecco's gencost and pkg/ctrl's genctrl)

ping @shoshanareich @mgoldberg10

Compatibility with LLC grids is in development

MeshArrays.jl can now be used to get the grid point coefficients and weights for profiles, and should work here too.
the original Octave/Matlab package (MITprof) can also be helpful here
a python version is being designed (see ECCO HackWeek 2024)

Would be great to give pointers for all three options in the docs related to this package as well as pkg/profiles, as we have users across packages.
Ultimately, it would be nice to have this fortran and embedded in MITgcm itself. The main difficulty would be to implement a global knn (or just nearest neighbor) to attach each data point to a tile. The rest could just be ported from MeshArrays.jl to F90, which should not be too difficult I think.
See "Interpolation Scheme" in this notebook and
(fig1,fig2,fig3)=MeshArrays.plot_examples(:interpolation_demo,Γ)

@gaelforget Thanks for the suggestions!

fig1,fig2,fig3)=MeshArrays.plot_examples(:interpolation_demo,Γ)

To try this out, as mentioned today, you can try via
1.1  ECCO-Docker
docker run -p 8888:8888 gaelforget/ecco-docker locally, or binder
1.2 or just install julia on your laptop
2.1 use Pluto (see bottom of page) + notebook url
2.2 in the Julia terminal
using MeshArrays, CairoMakie
Γ=GridLoad(ID=:LLC90,option="full")
(fig1,fig2,fig3)=MeshArrays.plot_examples(:interpolation_demo,Γ)

This package is now compatible with LLC grids, thanks to @shoshanareich!

This package is now compatible with LLC grids, thanks to @shoshanareich!

Yup, let me know if anyone finds any bugs!
@mgoldberg10 and I are developing ObsPrep, a python module for preprocessing datasets to create ObsFit input files for the LLC grid. We created a tutorial on how to use it, which we used to create a test input file you can find on the repo. Let us know if you have any questions!

Just a comment: Much of the NetCDF related discussion applies here, too: NF_CLOSE/NF_OPEN vs. NF_SYNC, (no) error handling, etc.

@averdy I merge master-branch in (+ fix a merging conflict) so just be careful, when you get back to this branch, to get the latest (just with 'git pull") before making any new changes (any new commit).


Spike Animation Tools

Spike how existing tooling could be used or new tooling created to support users doing the following to animations with boxart.

View
Edit
Blend

Looking at Cocos Creator's animation mechanism and animachine I think there is an interesting and important problem unanswered in them. Responsive animations. How do you animate objects in a responsive website. The animation needs to deal with the context that the elements on the page may not have an absolute cartesian coordinate.

From thinking on this last week, and talking with some people, any first tool would provide the first step mentioned in the issue's body. A tool to view animations in the project. For those animations we need to define what an animation's definition looks like and what it animates can look like.
 An animation should be applicable to multiple armatures as long as they have some pieces that are named the same. Like duck typing, if an armature looks like a duck an animation for a duck can work on it.
Lets refer to animations as animation clips. Or clips for short. Clips take input from an armature and transforms wires in the armature for those inputs. Those transforms can be dom styles and element attributes or methods on the wires if they are there. Common methods will be to interact with particle systems, emitting particles, or starting animations  on armatures under a larger one allowing some clips to be constructions of smaller clips over a more complex armature.
Since we are working on top of React any first version will focus on that so we don't get stuck being something more generic. A more generic version that can work outside React on any DOM or even interact with Canvas framework objects is a great target but one we'll look to do later after we have a tool focused on React and BoxArt's helpers.
Armatures and Animations will be defined in JS but we should focus to make to define them so what they use can be understood by less technical team members. An armature is likely a subclass of Animated and instead of taking an animate function property takes an animation clip and a refs object. Instead of looking up elements by id or class or other dom selector, elements are stored on an object with keys  that the animation expects. The armature can define a hierarchy for itself but the animation won't know that hierarchy just the names of the nodes it defines. In common sprite animations, the armature should define what frames go to what assets. An animation isn't in charge of loading assets, an armature is, so the armature also translates sprite info from an animation clip into how that changes the relevant element.
We should look to take this first version of the tool into helping with editing. A timeline is a naturally desired feature but it'll be a later target. First we need a common editing surface. Non technical team members may not have a preferred text editor setup with a lot of the helpful tools and plugins a technical team member may have. A minimum editor for editing armatures and animations would be a good second target after being able to preview animations. Being able to bring up and identify compile errors  immediately while developing an animation would be greatly helpful. Since boxart-boiler is using babel we can probably take inspiration from babel-standalone for the editor and error prompt.
I think making an electron (or similar tool) wrapped version of the animation preview / mini-editor may be out of scope for this
All of these thoughts down I'm proposing a page generated by running the grunt (or npm start) command that provides the following features by milestones.
Milestone 1

Lists armatures
Lists animation clips
Previews an armature with a given animation clip

Can play forward, play backward, pause, step forward, step backward, set position in time
HMR on armature or animation updates the preview

Milestone 2

Preview

hover over element presents tooltip with its armature name
non-erroring changes in the editor updates the preview

Editor

Switch between Editor views
Edit armature js
Edit animation clip js
Babel compile in the browser and update the preview immediately
State js errors and note their line
Prompt when a change on the file system triggered HMR (hot module replacement) that update the currently modified armature or clip

Milestone 3

Preview

click on an element pauses (if not already paused) and lets you do standard transforms and see the resulting value, at this point it's up to the user to put their transform in the animation clip, this is just a vastly convenient way to find out what the transforms should be

To recap the original brief for this spike, the goal is to have animations be something that can be authored in isolation, then integrated into a game, but still viewed in comparative isolation for debugging purposes; i.e., here's how this one agent in the game should move; here's it moving in the real game; if it's not moving properly, pull it up on its own again to see whether the error is part of its animation code, or an interaction with another animation. (All of this is stated above, just re-wording for my own clarity)

The motivation for building an editor is to reduce the barrier to entry for non-programmer motion designers and editors: having an editor that can intelligently support on-boarding these users would significantly reduce friction and back-and-forth between motion designers and their supporting developers.
After discussion with @mzgoddard, I propose this re-cast of the prioritization, on the grounds that the editor is a large piece of work in and of itself and the preview/interaction capabilities of an animation viewer are relevant beyond the userbase that would be depending on this editor:
Milestone 2

Preview

hover over element presents tooltip with its armature name
click on an element pauses (if not already paused) and lets you do standard transforms and see the resulting value, at this point it's up to the user to put their transform in the animation clip, this is just a vastly convenient way to find out what the transforms should be

Milestone 3

Preview

non-erroring changes in the editor updates the preview

Editor

Switch between Editor views
Edit armature js
Edit animation clip js
Babel compile in the browser and update the preview immediately
State js errors and note their line
Prompt when a change on the file system triggered HMR (hot module replacement) that update the currently modified armature or clip

With the work items captured in #86, #87 and #88, this item can be closed. Thanks for the detailed write-up, @mzgoddard !


fix(esl-carousel): esl-carousel-dots does not re-renders after target re-definition

:tada: This issue has been resolved in version 5.0.0-beta.26 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Tapd stuck and not communicating with tapcli

I tried minting a number of new assets . At one point tapd appeared to get stuck and stopped responding to requests from tapcli .
tapd logs:
2023-07-05 18:32:12.511 [DBG] GRDN: Inspecting tx f0a2926add9e17787a3f3b4ecd48837d0bf56d54dcc1858bdf623fe5d4c28f67 for Taproot Asset address outputs
2023-07-05 18:32:12.512 [DBG] GRDN: Inspecting tx 263fe0af38ae17fec2ce2304c7727b3443fb9503750ba877568788019703efbb for Taproot Asset address outputs
2023-07-05 18:32:12.512 [DBG] GRDN: Inspecting tx 804baf6eb869774321ea9aaff40d5429306e29f6c7b18e3ec4ea3786849a48e1 for Taproot Asset address outputs
2023-07-05 18:32:12.512 [INF] GRDN: Starting main custodian event loop
2023-07-05 18:32:12.515 [INF] GRDN: BatchCaretaker(021507534593d69fe6efea1aa225879bbd6efe0f3f786ee8f192204b1e18f34630): transition states: BatchStateCommitted -> BatchStateBroadcast
2023-07-05 18:32:12.515 [INF] GRDN: BatchCaretaker(021507534593d69fe6efea1aa225879bbd6efe0f3f786ee8f192204b1e18f34630): extracted finalized GenesisTx
2023-07-05 18:32:12.522 [DBG] GRDN: Inspecting tx 68f1bc3cb7a19974462a1cba83de8bc878a3f3c97b1a853e7f491d9f1a4908d8 for Taproot Asset address outputs
2023-07-05 18:32:12.531 [INF] GRDN: BatchCaretaker(021507534593d69fe6efea1aa225879bbd6efe0f3f786ee8f192204b1e18f34630): transition states: BatchStateBroadcast -> BatchStateBroadcast
2023-07-05 18:32:12.969 [INF] PROF: Attempting to receive proof via sid=72daea4bc3abf0f6d6a667615c5dfc6289ad437eedea7c23cf5d704862353c21ba7e8b97999c7368e2aaa7f3e695d135fb804449f15e5ae4afe5237b5269cf62
2023-07-05 18:37:27.294 [DBG] GRDN: Inspecting tx 68f1bc3cb7a19974462a1cba83de8bc878a3f3c97b1a853e7f491d9f1a4908d8 for Taproot Asset address outputs
2023-07-05 18:37:27.306 [DBG] GRDN: Got chain confirmation: 68f1bc3cb7a19974462a1cba83de8bc878a3f3c97b1a853e7f491d9f1a4908d8
2023-07-05 18:37:27.306 [INF] GRDN: MintingBatch(021507534593d69fe6efea1aa225879bbd6efe0f3f786ee8f192204b1e18f34630): confirmed at block(hash=00000000000000162606d660ad5ab09562c5018dfb779f930164c236a1c9358c, height=2440527)
2023-07-05 18:37:27.306 [INF] GRDN: BatchCaretaker(021507534593d69fe6efea1aa225879bbd6efe0f3f786ee8f192204b1e18f34630), advancing from state=BatchStateConfirmed to state=BatchStateFinalized
2023-07-05 18:37:27.309 [DBG] GRDN: Registering asset with universe, key=(universe.Identifier) f6cd8c2ae720261eff3dca8d04cee5f30bf1d48d234032aea750a6323cab5581

tapcli logs:
(base) [ec2-user@ip-172-31-91-154 ~]$ tapcli assets list
[tapcli] unable to list assets: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: context deadline exceeded"
(base) [ec2-user@ip-172-31-91-154 ~]$ tapcli assets list
[tapcli] unable to list assets: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: read tcp <IP_ADDRESS>:48154-><IP_ADDRESS>:10029: i/o timeout"
(base) [ec2-user@ip-172-31-91-154 ~]$ tapcli assets list
[tapcli] unable to list assets: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: read tcp <IP_ADDRESS>:51400-><IP_ADDRESS>:10029: i/o timeout"

It looks as if tapd might be too busy (registering a minting event with a universe?) to accept further requests. I would be interested in seeing more tapd logs once they are produced.

Are you able to get a profile of right when it starts to hang?

Likely fixed by https://github.com/lightninglabs/taproot-assets/pull/431. Please re-open if able to reproduce.


Security: Authentication / Authorization

Secure our services.

This issue can be closed when we are able to authorize an authenticated user on clientapp with some roles with our minimalapi secured to a scope of roles.


chore(package): yarn.lock update

coverage: 97.619%. remained the same
when pulling 06b0df10892ff9eba1dead4af111ae5e521e6a90 on lockfile-update
into afb23fb6c98b4d0d9268c49a5b782c7c7852e03d on master.


When will the code be made public

thank you for your great work ，and How long do I need to learn this code

Please find the code in the repo.


SSH Agent showed "Trezor not ready" for Trezor T

Hi this is the first time I report an issue, I hope this is the right place to do so. This issue I have posted on reddit too:  https://www.reddit.com/r/TREZOR/comments/9uefl4/ssh_agent/
I tried to use SSH agent for the first time, followed every step here https://github.com/martin-lizner/trezor-ssh-agent but it just showed : Trezor not ready. I am not sure why. A similar case I found is https://github.com/martin-lizner/trezor-ssh-agent that it is not compatible with Trezor T, but that post was back in April so I would assume now Trezor T should be supported. Trezor already plugged in and unlocked with PIN but still the same. Will appreciate any help. Thanks.
This is the log file:
[05.11.2018 23:09:12] INFO: Java version: 1.8.0_191-b12 (64-bit)
[05.11.2018 23:09:12] INFO: Java home: C:\Program Files\Java\jre1.8.0_191
[05.11.2018 23:09:13] INFO: Trezor SSH Agent 1.0.3 started successfully
[05.11.2018 23:09:13] INFO: Existing settings file loaded: C:\Users\User\Trezor_Agent.properties
[05.11.2018 23:09:13] INFO: Trezor Service Started
[05.11.2018 23:09:13] INFO: Received USB event: SHOW_DEVICE_DETACHED
[05.11.2018 23:09:19] INFO: Request for operation: SSH2_AGENT_GET_IDENTITIES
[05.11.2018 23:09:19] WARNING: Trezor not ready.
[05.11.2018 23:09:40] INFO: Request for operation: SSH2_AGENT_GET_IDENTITIES
[05.11.2018 23:09:40] WARNING: Trezor not ready.
[05.11.2018 23:09:45] INFO: Request for operation: SSH2_AGENT_GET_IDENTITIES
[05.11.2018 23:09:45] WARNING: Trezor not ready.

Hi and thanks for visiting my project. Im afraid I have bad news, Trezor T is still not supported due to a missing API. Hopefully It will be released eventually.

I am having same issue with trezor (not T).  Is it the same reason?

Trezor 1 is supported - pls follow Troubleshooting section on project main page. Please provide logs if smth interesting shows up.

Apparently my Trezor One also has the same problem as reported by archills, which is also the same problem  as Trezor T

Any change on this?  It has been over 2 years now since the last comment about this issue.  Was hoping to be able to use my Trezor Model T for SSH Keys to remote into various Linux servers.  Can someone help me out on what my options might be?  Trezor is still selling their product as being able to be used to store SSH keys.  Thanks in advance for any help on this.


Problem with Quick Start example

Hi
I have a problem on: https://github.com/TuringLang/Turing.jl/edit/master/docs/_docs/using-turing/quick-start.md
The following error is raised.
ERROR: LoadError: MethodError: no method matching get_color_palette(::Symbol, ::RGBA{Float64}, ::Int64)
This looks like a problem in StatsPlots, but it is a bit off-putting.  I am using the latest Julia.
Any ideas?
All the best
Marco

Which package versions do you use? Can you post the output of ] st --manifest in the Julia REPL (see https://julialang.github.io/Pkg.jl/v1/managing-packages/#Adding-registered-packages-1)?

Hi
let me answer in pieces.
First of all, on a W10 machine and Julia 1.4.1 things seem to work without problems.
The problem I have is on an Ubuntu machine
PoolTesting/tests$ uname -a Linux giacinto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
The ] st --manifest yields the following.  Look at the next answer for the result of testing.
(@v1.4) pkg> st --manifest Status ~/.julia/environments/v1.4/Manifest.toml`
[621f4979] AbstractFFTs v0.5.0
[80f14c24] AbstractMCMC v1.0.1
[1520ce14] AbstractTrees v0.3.3
[79e6a3ab] Adapt v1.1.0
[0bf59076] AdvancedHMC v0.2.25
[5b7e9947] AdvancedMH v0.5.1
[46ada45e] Agents v3.2.1
[dce04be8] ArgCheck v2.0.0
[ec485272] ArnoldiMethod v0.0.4
[7d9fca2a] Arpack v0.4.0
[68821587] Arpack_jll v3.5.0+3
[4fba245c] ArrayInterface v2.9.0
[13072b0f] AxisAlgorithms v1.0.0
[39de3d68] AxisArrays v0.4.3
[6e4b80f9] BenchmarkTools v0.5.0
[76274a88] Bijectors v0.7.2
[b99e7846] BinaryProvider v0.5.10
[6e34b625] Bzip2_jll v1.0.6+2
[324d7699] CategoricalArrays v0.8.1
[aaaa29a8] Clustering v0.14.1
[3da002f7] ColorTypes v0.10.4
[5ae59095] Colors v0.12.2
[861a8166] Combinatorics v1.0.2
[bbf7d656] CommonSubexpressions v0.3.0
[34da2185] Compat v3.12.0
[e66e0078] CompilerSupportLibraries_jll v0.3.3+0
[88cd18e8] ConsoleProgressMonitor v0.1.2
[d38c429a] Contour v0.5.3
[a10d1c49] DBInterface v2.2.0
[9a962f9c] DataAPI v1.3.0
[a93c6f00] DataFrames v0.21.3
[864edb3b] DataStructures v0.17.19
[e2d170a0] DataValueInterfaces v1.0.0
[e7dc6d0d] DataValues v0.4.13
[163ba53b] DiffResults v1.0.2
[b552c78f] DiffRules v1.0.1
[b4f34e82] Distances v0.9.0
[31c24e10] Distributions v0.23.4
[ced4e74d] DistributionsAD v0.5.3
[ffbed154] DocStringExtensions v0.8.2
[366bfd00] DynamicPPL v0.8.2
[da5c29d0] EllipsisNotation v0.4.0
[cad2338a] EllipticalSliceSampling v0.2.2
[c87230d0] FFMPEG v0.3.0
[b22a6f82] FFMPEG_jll v4.1.0+3
[7a1cc6ca] FFTW v1.2.2
[f5851436] FFTW_jll v3.3.9+5
[1a297f60] FillArrays v0.8.11
[6a86dc24] FiniteDiff v2.3.2
[53c48c17] FixedPointNumbers v0.8.1
[59287772] Formatting v0.4.1
[f6369f11] ForwardDiff v0.10.11
[d7e528f0] FreeType2_jll v2.10.1+2
[559328eb] FriBidi_jll v1.0.5+3
[28b8d3ca] GR v0.48.0
[4d00f742] GeometryTypes v0.8.3
[d25df0c9] Inflate v0.1.2
[505f98c9] InplaceOps v0.3.0
[1d5cc7b8] IntelOpenMP_jll v2018.0.3+0
[a98d9a8b] Interpolations v0.12.10
[8197267c] IntervalSets v0.5.1
[41ab1584] InvertedIndices v1.0.0
[c8e1da08] IterTools v1.3.0
[82899510] IteratorInterfaceExtensions v1.0.0
[682c06a0] JSON v0.21.0
[5ab0869b] KernelDensity v0.5.1
[c1c5ebd0] LAME_jll v3.100.0+1
[1d6d02ad] LeftChildRightSiblingTrees v0.1.2
[dd192d2f] LibVPX_jll v1.8.1+1
[6f1fad26] Libtask v0.4.1
[093fc24a] LightGraphs v1.3.3
[d3d80556] LineSearches v7.0.1
[6fdf6af0] LogDensityProblems v0.10.3
[e6f89c97] LoggingExtras v0.4.1
[c7f686f2] MCMCChains v3.0.12
[856f044c] MKL_jll v2020.1.216+0
[1914dd2f] MacroTools v0.5.5
[dbb5928d] MappedArrays v0.2.2
[442fdcdd] Measures v0.3.1
[e1d29d7a] Missings v0.4.3
[6f286f6a] MultivariateStats v0.7.0
[d41bc354] NLSolversBase v7.6.1
[872c559c] NNlib v0.6.6
[77ba4419] NaNMath v0.3.3
[86f7a689] NamedArrays v0.9.4
[b8a86587] NearestNeighbors v0.4.6
[510215fc] Observables v0.3.1
[6fe1bfb0] OffsetArrays v1.1.0
[e7412a2a] Ogg_jll v1.3.4+0
[4536629a] OpenBLAS_jll v0.3.9+4
[458c3c95] OpenSSL_jll v1.1.1+4
[efe28fd5] OpenSpecFun_jll v0.5.3+3
[429524aa] Optim v0.22.0
[91d4177d] Opus_jll v1.3.1+1
[bac558e1] OrderedCollections v1.2.0
[90014a1f] PDMats v0.9.12
[d96e819e] Parameters v0.12.1
[69de0a69] Parsers v1.0.6
[ccf2f8ad] PlotThemes v1.0.3
[995b91a9] PlotUtils v0.6.5
[91a5bcdd] Plots v0.29.9
[2dfb63ee] PooledArrays v0.5.3
[85a6dd25] PositiveFactorizations v0.2.3
[33c8b6b6] ProgressLogging v0.1.3
[92933f4c] ProgressMeter v1.3.1
[1fd47b50] QuadGK v2.3.1
[b3c3ace0] RangeArrays v0.3.2
[c84ed2f1] Ratios v0.4.0
[3cdcf5f2] RecipesBase v0.8.0
[01d81517] RecipesPipeline v0.1.11
[189a3867] Reexport v0.2.0
[ae029012] Requires v1.0.1
[79098fc4] Rmath v0.6.1
[f50d1b31] Rmath_jll v0.2.2+1
[f2b01f46] Roots v1.0.2
[0aa819cd] SQLite v1.0.3
[76ed43ae] SQLite_jll v3.31.1+0
[992d4aef] Showoff v0.3.1
[699a6c99] SimpleTraits v0.9.2
[a2af1166] SortingAlgorithms v0.3.1
[276daf66] SpecialFunctions v0.10.3
[90137ffa] StaticArrays v0.12.3
[2913bbd2] StatsBase v0.33.0
[4c63d2b9] StatsFuns v0.9.5
[f3b207a7] StatsPlots v0.14.6
[ab02a1b2] TableOperations v0.2.1
[3783bdb8] TableTraits v1.0.0
[bd369af6] Tables v1.0.4
[5d786b92] TerminalLoggers v0.1.2
[9f7883ad] Tracker v0.2.7
[84d833dd] TransformVariables v0.3.8
[fce5fe82] Turing v0.13.0
[3a884ed6] UnPack v1.0.1
[ea10d353] WeakRefStrings v0.6.2
[cc8bc4a8] Widgets v0.6.2
[efce3f68] WoodburyMatrices v0.5.2
[83775a58] Zlib_jll v1.2.11+14
[700de1a5] ZygoteRules v0.2.0
[0ac62f75] libass_jll v0.14.0+2
[f638f0a6] libfdk_aac_jll v0.1.6+2
[f27f6e37] libvorbis_jll v1.3.6+4
[1270edf5] x264_jll v2019.5.25+2
[dfaa095f] x265_jll v3.0.0+1
[2a0f44e3] Base64
[ade2ca70] Dates
[8bb1440f] DelimitedFiles
[8ba89e20] Distributed
[9fa8497b] Future
[b77e0a4c] InteractiveUtils
[76f85450] LibGit2
[8f399da3] Libdl
[37e2e46d] LinearAlgebra
[56ddb016] Logging
[d6f4376e] Markdown
[a63ad114] Mmap
[44cfe95a] Pkg
[de0858da] Printf
[3fa0cd96] REPL
[9a3f8284] Random
[ea8e919c] SHA
[9e88b42a] Serialization
[1a1011a3] SharedArrays
[6462fe0b] Sockets
[2f01184e] SparseArrays
[10745b16] Statistics
[4607b0f0] SuiteSparse
[8dfed614] Test
[cf7118a7] UUIDs
[4ec0a83e] Unicode
(@v1.4) pkg>
`

Here is the final result of ] test Turing.
`Test Summary:                                                               | Pass  Error  Total
Turing                                                                      | 9930      7   9937
core                                                                      |  245      2    247
ad.jl                                                                   |  211      2    213
adr                                                                   |    2             2
passing duals to distributions                                        |    6             6
general AD tests                                                      |    1      1      2
Tracker, Zygote and ReverseDiff + logdet                              |    6             6
Tracker & Zygote + fill                                               |   12            12
Tracker, Zygote and ReverseDiff + MvNormal                            |    5             5
Tracker, Zygote and ReverseDiff + Diagonal Normal                     |    5             5
Tracker, Zygote and ReverseDiff + MvNormal Interface                  |  170           170
Simplex Tracker, Zygote and ReverseDiff (with and without caching) AD |    2             2
PDMatDistribution AD                                                  |           1      1
Hessian test                                                          |    2             2
container.jl                                                            |   34            34
inference: forwarddiff                                                    | 3190      1   3191
samplers                                                                | 3190      1   3191
gibbs.jl                                                              |   24            24
hmc.jl                                                                |   19      1     20
constrained bounded                                                 |    1             1
contrained simplex                                                  |    2             2
hmc reverse diff                                                    |    2             2
matrix support                                                      |           1      1
multivariate support                                                |              No tests
hmcda inference                                                     |    4             4
hmcda constructor                                                   |    2             2
nuts inference                                                      |    2             2
nuts constructor                                                    |              No tests
check discard                                                       |    2             2
AHMC resize                                                         |    3             3
Regression tests                                                    |    1             1
is.jl                                                                 | 3002          3002
mh.jl                                                                 |   26            26
ESS                                                                   |   11            11
SMC                                                                   |   25            25
PG                                                                    |   35            35
resample.jl                                                           |    5             5
io.jl                                                                 |   41            41
dynamichmc.jl                                                         |    2             2
variational algorithms : forwarddiff                                      |    6             6
inference: tracker                                                        | 3190      1   3191
samplers                                                                | 3190      1   3191
gibbs.jl                                                              |   24            24
hmc.jl                                                                |   19      1     20
constrained bounded                                                 |    1             1
contrained simplex                                                  |    2             2
hmc reverse diff                                                    |    2             2
matrix support                                                      |           1      1
multivariate support                                                |              No tests
hmcda inference                                                     |    4             4
hmcda constructor                                                   |    2             2
nuts inference                                                      |    2             2
nuts constructor                                                    |              No tests
check discard                                                       |    2             2
AHMC resize                                                         |    3             3
Regression tests                                                    |    1             1
is.jl                                                                 | 3002          3002
mh.jl                                                                 |   26            26
ESS                                                                   |   11            11
SMC                                                                   |   25            25
PG                                                                    |   35            35
resample.jl                                                           |    5             5
io.jl                                                                 |   41            41
dynamichmc.jl                                                         |    2             2
variational algorithms : tracker                                          |    6             6
inference: reversediff                                                    | 3190      1   3191
samplers                                                                | 3190      1   3191
gibbs.jl                                                              |   24            24
hmc.jl                                                                |   19      1     20
constrained bounded                                                 |    1             1
contrained simplex                                                  |    2             2
hmc reverse diff                                                    |    2             2
matrix support                                                      |           1      1
multivariate support                                                |              No tests
hmcda inference                                                     |    4             4
hmcda constructor                                                   |    2             2
nuts inference                                                      |    2             2
nuts constructor                                                    |              No tests
check discard                                                       |    2             2
AHMC resize                                                         |    3             3
Regression tests                                                    |    1             1
is.jl                                                                 | 3002          3002
mh.jl                                                                 |   26            26
ESS                                                                   |   11            11
SMC                                                                   |   25            25
PG                                                                    |   35            35
resample.jl                                                           |    5             5
io.jl                                                                 |   41            41
dynamichmc.jl                                                         |    2             2
variational algorithms : reversediff                                      |    6             6
variational optimisers                                                    |    8             8
stdlib                                                                    |   70      2     72
distributions.jl                                                        |   68      2     70
distributions functions                                               |    1             1
distributions functions                                               |    1             1
distributions functions                                               |    1             1
single distribution correctness                                       |   65      2     67
Correctness test for single distributions                           |   65      2     67
UnivariateDistribution                                            |   59            59
MultivariateDistribution                                          |    6             6
MatrixDistribution                                                |           2      2
Wishart{Float64,PDMat{Float64,Array{Float64,2}},Int64}          |           1      1
InverseWishart{Float64,PDMat{Float64,Array{Float64,2}}}         |           1      1
RandomMeasures.jl                                                       |    2             2
utilities                                                                 |    1             1
modes                                                                     |   18            18
ERROR: LoadError: Some tests did not pass: 9930 passed, 0 failed, 7 errored, 0 broken.
in expression starting at /home/marco/.julia/packages/Turing/GMBTf/test/runtests.jl:12
ERROR: Package Turing errored during testing
(@v1.4) pkg>`

OK, so the Turing test errors are unrelated and already fixed on the master branch. They are caused by some breaking changes in Distributions 0.2.23, hence they should be gone if you downgrade Distributions to 0.2.22 by running ] add<EMAIL_ADDRESS>I assume the problems that you experience when running the quick start examples are caused by the quite old version of Plots that you use. The latest release is 1.4.4 whereas you use 0.29.9, I guess this causes problems together with the latest release of StatsPlots (0.14.6). Can you try to upgrade plots to the latest release by running ] add<EMAIL_ADDRESS>It should display an error message that tells you which package is holding it back, if the update is not possible.

Thanks for the advice.
I will try all of this tomorrow.
All the best
Marco
On Mon, Jun 29, 2020 at 7:18 PM David Widmann<EMAIL_ADDRESS>wrote:

OK, so the Turing test errors are unrelated and already fixed on the
master branch. They are caused by some breaking changes in Distributions
0.2.23, hence they should be gone if you downgrade Distributions to 0.2.22
by running ] add<EMAIL_ADDRESS>I assume the problems that you experience when running the quick start
examples are caused by the quite old version of Plots that you use. The
latest release is 1.4.4 whereas you use 0.29.9, I guess this causes
problems together with the latest release of StatsPlots (0.14.6). Can you
try to upgrade plots to the latest release by running ] add<EMAIL_ADDRESS>It should display an error message that tells you which package is holding
it back, if the update is not possible.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TuringLang/Turing.jl/issues/1339#issuecomment-651252923,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAD5SWVAYGTHWVIKJ6TSOB3RZDEG3ANCNFSM4OLKKGJQ
.

--
Marco Antoniotti
Somewhere over the Rainbow

Hi
after a few updates, I can report that the first example works on my
Linux/Ubuntu machine.  The issue was the outdated Plots package.
All the best
Marco
On Mon, Jun 29, 2020 at 7:18 PM David Widmann<EMAIL_ADDRESS>wrote:

OK, so the Turing test errors are unrelated and already fixed on the
master branch. They are caused by some breaking changes in Distributions
0.2.23, hence they should be gone if you downgrade Distributions to 0.2.22
by running ] add<EMAIL_ADDRESS>I assume the problems that you experience when running the quick start
examples are caused by the quite old version of Plots that you use. The
latest release is 1.4.4 whereas you use 0.29.9, I guess this causes
problems together with the latest release of StatsPlots (0.14.6). Can you
try to upgrade plots to the latest release by running ] add<EMAIL_ADDRESS>It should display an error message that tells you which package is holding
it back, if the update is not possible.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TuringLang/Turing.jl/issues/1339#issuecomment-651252923,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAD5SWVAYGTHWVIKJ6TSOB3RZDEG3ANCNFSM4OLKKGJQ
.

--
Marco Antoniotti
Somewhere over the Rainbow

Great to hear that it works now! I'll close this issue then.


Add Railway deployment guide

This PR does the following:

Adds a guide on deploying and running remix-saas apps on Railway.
Adds a one-click deploy option to be up and running in less than 3 mins.

Disclaimer: I work at Railway and open to collaboration opportunities to ensure folks can deploy and scale this stack easily on our platform. Please let me know if the structure of the docs make sense.

Hello @unicodeveloper.
Looks good to me, although I'm not sure if I really want to have a specific file related to only deploying to Railway. Either this has been discussed before.
Remix-SaaS will soon move into Cloudflare, leaving away Fly.io and other related deployment services.

With that said, the doc provided looks good. Have you been able to test the deployment by simply following it? (I think so, right?).

Hello @unicodeveloper.
Looks good to me, although I'm not sure if I really want to have a specific file related to only deploying to Railway. Either this has been discussed before.

Hey @dev-xo thanks for the swift response. How would you prefer this to be?

Remix-SaaS will soon move into Cloudflare, leaving away Fly.io and other related deployment services.

Thanks for the heads up. Do you have an idea of the timeline you have for that? plus some folks might still need to use other Paas.

With that said, the doc provided looks good. Have you been able to test the deployment by simply following it? (I think so, right?).

Oh yes, this is a live link straight from the deployment template included in the guide. https://remix-saas-production.up.railway.app
Both the step by step guide and the deployment template works seamlessly.

We do not have a specific file related to "fly.io" deployment (rather the deployment file itself), but it seems like now it will be one specifically related to "railway," which seems unfair to me.
Either we have 2 files, one for Fly, and one for Railway, or we combine both.

With that said, what plans do you have on RailWay for the template? Any updates/modifications in mind? For example, you may want to swap the Fly.io SVG for the one from RailWay.
It would be great if at least the footer stays the same, where the author is provided, and the GitHub link to the original repository.

About Cloudflare. The swap to it will occur sooner rather than later, as Remix already provides some of the v3 flags for it. I think we may have the template active as legacy (the current version), but probably without any new updates/maintenance, although that will still allow Fly/Railway to deploy it, or simply use the legacy code.
I would have preferred to have a talk about this before (as some others like Convex Community did), but this is an MIT project, and I think it's still valid to already use the project or adapt it to other services, like Railway.

Closing for now; no response from OP.

Hello @dev-xo I had a busy day yesterday. Just getting to see this. And it's just early hours of the morning here (Thursday) in BST timezone.
We can combine both.

With that said, what plans do you have on Railway for the template?

Yes, I will swap the Fly.io SVG for Railway.
The template is already great to go for folks trying to get the stack setup/deployed. If there are any changes/updates, I will keep updating the template.

I would have preferred to have a talk about this before (as some others like Convex Community did), but this is an MIT project, and I think it's still valid to already use the project or adapt it to other services, like Railway.

Very open to talk/conversations about it. If you wanna jump on a call, I am ready. I can send an invite. @dev-xo

All good @unicodeveloper! Kinda busy here too, so nothing to worry about.
Combining both could do the job, and as far as I saw, the doc you provided looks already good, so can't add much more myself.
If you are up to come up with a new commit for it, I could review it and simply merge. Otherwise, I will look into it in the following days.
With that said, the template may still be able to check as Legacy code, so Fly/Railway and some others will be able to review the old docs or the original code (in this case, the Railway deployment).

Also, thanks for clarifying the provided questions.
Noticed there are some other Remix templates, so I think the usage on this one will be the same, and if that helps others to either use Railway itself or have a look at the original repository, that will be as good as it can be.

All good @unicodeveloper. Kinda busy here too, so nothing to worry about.
Combining both could do the job, and as far as I saw, the doc you provided looks already good, so can't add much more myself.
If you are up to come up with a new commit for it, I could review it and simply merge. Otherwise, I will look into it in the following days.

Okay, I can come up with a new commit for merging both into a single deployment doc.

With that said, the template may still be able to check as Legacy code, so Fly/Railway and some others will still be able to review the old docs or the original code (in this case, the Railway deployment).
Also, thanks for clarifying the provided questions.

Haha, i love clarifying a lot.

Noticed there are some other Remix templates, so I think the usage on this one will be the same, and if that helps others to either use Railway itself or have a look at the original repository, that will be as good as it can be.

You mean other Remix templates like the epic stack, blue stack and the rest?
Thanks @dev-xo


Builder creates array index tags

Hello, I have following code:
const xml2js = require("xml2js");
const xmlBuilder = new xml2js.Builder();

const text = `<?xml version="1.0" encoding="UTF-8"?><en-note><div>this is a note</div></en-note>`;

xml2js.parseString(text, function (err, result) {
    const noteContent = xmlBuilder.buildObject(result['en-note']);

    console.log("This has weird index tags inside:", noteContent);
});

I would expect this should produce following output:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

this is a note

But instead what I get is following weird output:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

  <0>t</0>
  <1>h</1>
  <2>i</2>
  <3>s</3>
  <4> </4>
  <5>i</5>
  <6>s</6>
  <7> </7>
  <8>a</8>
  <9> </9>
  <10>n</10>
  <11>o</11>
  <12>t</12>
  <13>e</13>

This probably doesn't work because you treat result['en-note'] as the root.
When parsing your XML, I get { div: [ 'this is a note' ] }.
When parsing the same XML without the en-note tag, I get { div: 'this is a note' }.
I just found this library, but I guess an array is most likely not a valid value for the root element, as that would mean that you had multiple root elements. So the library seems to work correct here.


Data parallelism

 Issue by larsbergstrom
Wednesday Jul 16, 2014 at 13:29 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/15712
This issue was labelled with: A-concurrency, A-libs, A-servo in the Rust repository

We  have attempted to gain parallelism in Servo, but in all cases where we  operate over a shared data structure, this requires a significant amount of unsafe code. We'd like to support:

Basic data-parallel operations
More complicated traversals (top-down, bottom-up, weighted-edge priority, topological, etc.) of either DAGs or graphs

Note that the key here is being able to define kernels of computation that work on the elements stored in these structures that ensure at least the illusion of ownership transfer between the shared data structure and kernel function and back is maintained.
CC: @pcwalton @nikomatsakis

We are planning to implement our own libraries in this space - please close.

Mind sharing the repo?


Don't allow new user-requested BMC dump while a user dump is in progress

We are forking a process and initiating dump process, in the
mean time if another dump request comes another child process will
be forked and so on causing N of dumps collected in parallel. Adding
restriction to collect one dump at a time, as the contents of the
dump will not vary if collected multiple times at the same time.

System is running out of memory as N no of dumps are collected
in the forked child processes. The check to see if space is available
is missed as it done prior to dump collection in the parent process
when the dump D-Bus entry is created.

Modified to return Not allowed error if user initiated dump
requests received while one is in progress.

Tested:
phosphor-dump-manager[21276]: Adding Dump Header :/usr/share/dreport.d/include.d/gendumpheader
phosphor-dump-manager[21276]: Thu Feb 24 05:02:20 UTC 2022 Successfully completed
phosphor-dump-manager[21274]: User initiated dump completed, resetting flag
Signed-off-by: Marri Devender Rao<EMAIL_ADDRESS>Change-Id: I954b5dfb74a2cbb3cca541de453a1b73f58fd20a

Can one of the admins verify this patch?

jenkins -> hardware


UI - continuously fetch sboms so they eventually appear after they are uploaded

@ctron This PR allows pulling data on the tab "products and containers" every 5 seconds to allow uploaded sboms to appear in the table list once they are ready.
I've been thinking about this use case. Unless we are able to make the 2 following endpoints to return the uploaded sbom immediately after they are uploaded then we will always need to continuously pull data in the UI. My point is, as long as there is a delay time (seconds or minutes) between uploading a file and indexing it, then the PULL approach is a must and not an option neither a workaround.

/api/v1/sbom/search GET (Search on table)

/api/v1/sbom?id=SBOM_ID GET (Get entity with details)

Puling data continuously is a common UI practice and it does not represent a risk of killing the backend's resources unless we prove otherwise

As long as we have the current architecture where the file is uploaded => file send to s3 => file is indexed, then we will always have a delay time (this applies regardless of whether we have a DB or nor). Even if we replace the index with a DB, I don't see how it would make things different.

What are your thoughts on this? If you have something in mind to tackle this issue from a different angle, could you please share it with me? It might be missing something

I agree that this is a valid workaround. I am not sure if it will introduce more problems than it will solve. Not because of a bad implementation, but because it things we didn't consider.
I would argue that this approach of workarounds lead to the current state of things.
I think it makes sense to keep this PR in our "bag of tricks", that we can pull it out when absolutely necessary. But let's try to avoid this for now.
One reason for this is: the index sync is currently one minute. Depending on the size of the index, that may be way to short. So we would need to increase it. And while it might technically be possible to poll for 5 or 10 minutes, a user wouldn't wait that long anyway.

Changing the status of this PR to Draft as some suggestions to be implemented came from @PhilipCattanach

After uploading an sbom the UI should show an Alert letting the user know that his file has been successfully uploaded
The default Tab on the Search page should be "Products and containers" as it is the natural way of looking at information. So the order of tabs will be: "Products and containers | packages | CVEs | Advisories"
The visualization of the CRDA report for each sbom should be done in the "Search main table" and it should be an action within the main table rather than a tab in the "details page".

@ctron Do you mind reviewing this PR please? The following changes were applied after your last review:

After uploading an sbom the UI should show an Alert letting the user know that his file has been successfully uploaded
The default Tab on the Search page should be "Products and containers" as it is the natural way of looking at information. So the order of tabs will be: "Products and containers | packages | CVEs | Advisories"
The visualization of the CRDA report for each sbom should be done in the "Search main table" and it should be an action within the main table rather than a tab in the "details page".

Those were suggestions from @PhilipCattanach
After this PR is merged I will start looking at https://issues.redhat.com/browse/TC-906

And this is how it should look like:
Screencast from 2024-01-22 09-57-14.webm


Xingpeng/add jre info

Can you verify if pkg installation would fail if jre is not available? Thanks!


Judgement Metric fix from config

fixed passing through whether we want to use cv or the test dataset metric as evaluation criterion for judging the best classifier

Lines 45-54 of the committed version of atm/worker.py are OBE, based on the other closed pull request.  I'll redo it.


Sort blend shapes in the inspector by ID instead of alphabetically

Fixes: https://github.com/godotengine/godot-proposals/issues/11155
Blend shapes (morph targets, shape keys) should be sorted by the physical order of the blend shapes, and the index should be converted to a name string.
Before (Godot 4.3)
The blend shape indices are scrambled.

After (this pr)
Notice the artist has used spacers.

This definitely makes sense.

@Jesusemora
Can you test with your samples and write if it works for you in the godotengine/godot#99231 pull request?

I was about to make the changes myself, you beat me to it, this was so fast.
I have compiled the code and tested it and it seems to work.
shapekeys appear in order by ID and alter the mesh appearance:

then I ran a script using the set method and it also works.

Thanks!


[Enhancement/Feature] [Integration] [SonarQube] Filter Applications out when syncing Projects

Motivation
Currently, SonarQube integration exports Applications when syncing Projects because it does not use qualifiers query string when talking to SonarQube API in its get_components method: https://github.com/port-labs/ocean/blob/main/integrations/sonarqube/client.py#L135
This results in Port displaying both Applications and Projects under Projects blueprint which is undesired.
Proposed Changes
Use qualifiers=TRK filter/query string when talking to SonarQube API to fetch Projects to exclude Applications.
SonarQube API docs: https://next.sonarqube.com/sonarqube/web_api/api/components?query=components
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Should work in the latest version 👍🏻


Clearly mark Phase 3 Rubric requirements that result in a rejected submission

Split the Unit Tests section, worth 25 pts, into Unit Tests (marked as a Prerequisite) and Unit Test Quality (25 pts).
Also marked Web Page Loads as a Prerequisite and moved its 10 points into Web API Works.
Resolves #76

Will not fix


Update Nexus Upgrade QDE Docs Page

Explanation of Work Needing Done
Need to go through and update the script on the nexus upgrade doc for QDE since the latest version of the nexus package on the CCR has package parameters for --params "'/BackupSslConfig'". Waiting for next version after V3.30.1-01 since this specific version has a bug when invoked in powershell with the connection test looping in shell. This next version as of writing this is current goin through the package moderation process.
References

ZenDesk Ticket

A PR has been merged to address this issue.

PR that was created is #251


Add support for integerish assertions

Fixes #18
type-wise, this should be identical as the is_numeric function call

Hi, thank you! Can you submit the same thing also to https://github.com/phpstan/phpstan-webmozart-assert? Thank you.

Hi, thank you! Can you submit the same thing also to https://github.com/phpstan/phpstan-webmozart-assert? Thank you.

I'll try, yes, sure. Thank you!

I'll try, yes, sure. Thank you!

Hi @ondrejmirtes, seems like the support is already there! https://github.com/phpstan/phpstan-webmozart-assert/commit/a5d6fa70732b5628e64b0a4552ac0c05264cabec however, it seems it would only accept string or int, not a float castable to int. Not sure if we should change that to also accept a float, as the original library does https://github.com/webmozarts/assert/blob/master/src/Assert.php#L102

Hi @ondrejmirtes, seems like the support is already there! https://github.com/phpstan/phpstan-webmozart-assert/commit/a5d6fa70732b5628e64b0a4552ac0c05264cabec however, it seems it would only accept string or int, not a float castable to int. Not sure if we should change that to also accept a float, as the original library does https://github.com/webmozarts/assert/blob/master/src/Assert.php#L102

@acasademont Would be great if you synced the implementation with phpstan-beberlei-assert :)

@acasademont Would be great if you synced the implementation with phpstan-beberlei-assert :)


CAD-3992 refine serialization constraints

Drop LedgerState l ValuesMK constraints for ToCBOR and FromCBOR
which were used only by the in-memory backend, and build that from the
ToCBOR and FromCBOR instance of k and v.
Define the new CodecMK map kind and use it to produce suitable codecs
depending on l :: LedgerStateKind.
Closes CAD-3992.

Base branch deleted, so reopened this PR at a different number https://github.com/input-output-hk/ouroboros-network/pull/3646


New Sample guidelines

Hello, SirBothersome here, I'm now taking charge of the LMMS samples repo. Before we get started here I think we should establish a few conventions for posting new samples.
Samples should be:
a) Made by you. At this point, if we're going to get this done in a timely manner, we should avoid using third-party samples. The process of contacting the owners, licensing, and clearing the samples is going to be a time drain. So let's skip that for now.
b) Functional. I'm essentially starting from scratch here. We need the basics, Acoustic drums, techno drums, some 808's and that's it for the moment niche samples like beatboxing or death metal screams are just going to clog the review process as of now
c) Varied. By which I mean, let's not just have 80 siney techno kicks and dubstep snares for our techno pack. We don't have to provide a full-spectrum key-labeled Kickdrum array. Just the essentials.
and d) Useful. This sample selection should be for producers, by producers, so please be sure that samples have minimal predelay, background noise and are eq'd/compressed for plug and play use.
Sorry if I'm bossy, but that's what I think we need to do.
God Bless and good day

The process of contacting the owners, licensing, and clearing the samples is going to be a time drain.

You do realise this is something that's scheduled for a version of LMMS after 1.2 (which is not even released yet), so I don't think time is really an issue. The problem I see here is that you never mentioned the importance of the quality of the samples. I think having high quality is very important and if this new sample pack is just there to replace the current samples with a similar quality but CC0 samples, it'd be the wrong approach.
So I disagree on accepting only self-made samples by people from the community, and disregarding something where some work was already done. Markus Hakala's kicks are something truly amazing and it would be sad if they weren't added to the new sample pack.

I'm now taking charge of the LMMS samples repo.

I won't add you to the sample editors team, which means you can work on this, but only from your fork, and the samples you provide will need to be reviewed prior to merging. That said, all help is appreciated and I wish you luck on this.

Also, the guidelines themselves belong in a formatted wiki, not a bug tracker.  You can us this bug (#20) for now to discuss and agree up on guidelines, but the guidelines themselves should be placed in a document, not an issue thread and this issue should be closed.
Part of managing a team of contributors as well as a source repository is getting to know how the process works, hence reactions like this:

I won't add you to the sample editors team, which means you can work on this, but only from your fork, and the samples you provide will need to be reviewed prior to merging.

:+1:

@SirBothersome find another place to be bothersome, please.

@SirBothersome find another place to be bothersome, please.

Fair enough. How's about I disappear for a week and come back with some shiny new samples?
I doubt I'll be missed.
God Bless and good day


Leap: Add dependecies for mgr-push

What does this PR change?
Due to killing the Leap 15.5 reposync in the CI, we need those dependencies already fulfilled.
Fixes https://github.com/SUSE/spacewalk/issues/24979
uyuni-master-podman-min-suse:~/salt # venv-salt-call --local --file-root=. state.sls dom
/usr/lib/venv-salt-minion/lib64/python3.11/site-packages/salt/utils/pycrypto.py:26: DeprecationWarning: 'crypt' is deprecated and slated for removal in Python 3.13
  import crypt
/usr/lib/venv-salt-minion/lib/python3.11/site-packages/salt/modules/linux_shadow.py:21: DeprecationWarning: 'spwd' is deprecated and slated for removal in Python 3.13
  import spwd
local:
----------
          ID: suse_minion_mgr_push_requisites
    Function: pkg.installed
      Result: True
     Comment: 9 targeted packages were installed/updated.
     Started: 14:19:37.615343
    Duration: 35566.602 ms
     Changes:
              ----------
              hwdata:
                  ----------
                  new:
                      0.380-150<IP_ADDRESS>
                  old:
              libgudev-1_0-0:
                  ----------
                  new:
                      237-150400.1.6
                  old:
              python3-dmidecode:
                  ----------
                  new:
                      3.12.2-150400.18.64
                  old:
              python3-extras:
                  ----------
                  new:
                      1.0.0-4.22
                  old:
              python3-hwdata:
                  ----------
                  new:
                      2.3.5-150<IP_ADDRESS>
                  old:
              python3-libxml2:
                  ----------
                  new:
                      2.10.3-1505<IP_ADDRESS>
                  old:
              python3-pyudev:
                  ----------
                  new:
                      0.22.0+git.1642212208.d5630bf-150400.5.50
                  old:
              python3-rhnlib:
                  ----------
                  new:
                      5.0.3-2.1.uyuni
                  old:
              zchunk:
                  ----------
                  new:
                      1.1.16-1504<IP_ADDRESS>
                  old:

Summary for local
------------
Succeeded: 1 (changed=1)
Failed:    0
------------
Total states run:     1
Total run time:  35.567 s

With that, we can install mgr-push since the remaining dependencies can be met with the Uyuni Client Tools.
uyuni-master-podman-min-suse:~/salt # zypper in mgr-push
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following 5 NEW packages are going to be installed:
  mgr-push python3-mgr-push python3-spacewalk-client-tools python3-uyuni-common-libs spacewalk-client-tools

5 new packages to install.

----------
          ID: pkg_installed
    Function: pkg.installed
        Name: pkg_installed
      Result: true
     Comment: 1 targeted package was installed/updated.
     Started: 14:25:20.274864
    Duration: 64768.56
         SLS: packages.pkginstall
     Changed: python3-uyuni-common-libs:
                  old: ''
                  new:
                  -   install_date_time_t: 1.723724783E9
                      version: 5.0.4
                      epoch: null
                      release: 2.1.uyuni
                      arch: x86_64
              python3-spacewalk-client-tools:
                  old: ''
                  new:
                  -   install_date_time_t: 1.723724783E9
                      version: 5.0.7
                      epoch: null
                      release: 2.1.uyuni
                      arch: noarch
              python3-mgr-push:
                  old: ''
                  new:
                  -   install_date_time_t: 1.723724784E9
                      version: 5.0.2
                      epoch: null
                      release: 2.1.uyuni
                      arch: noarch
              mgr-push:
                  old: ''
                  new:
                  -   install_date_time_t: 1.723724784E9
                      version: 5.0.2
                      epoch: null
                      release: 2.1.uyuni
                      arch: noarch
              spacewalk-client-tools:
                  old: ''
                  new:
                  -   install_date_time_t: 1.723724784E9
                      version: 5.0.7
                      epoch: null
                      release: 2.1.uyuni
                      arch: noarch

uyuni-master-podman-ctl:~/spacewalk/testsuite # cucumber features/secondary/srv_push_package.feature
Capybara APP Host: https://uyuni-master-podman-srv.mgr.suse.de:8888
Initializing a twopence node for 'server'.
Host 'server' is alive with determined hostname uyuni-master-podman-srv and FQDN uyuni-master-podman-srv.mgr.suse.de
Node: uyuni-master-podman-srv, OS Version: 15.5, Family: opensuse-leap
Initializing a twopence node for 'server'.
Host 'server' is alive with determined hostname uyuni-master-podman-srv and FQDN uyuni-master-podman-srv.mgr.suse.de
Node: uyuni-master-podman-srv, OS Version: 15.5, Family: opensuse-leap
Activating HTTP API
Using the default profile...
# Copyright (c) 2015-2024 SUSE LLC
# Licensed under the terms of the MIT license.
@sle_minion @scc_credentials @under_debugging
Feature: Push a package with unset vendor
  In order to distribute software to the clients
  As an authorized user
  I want to push a package with unset vendor

  Scenario: Log in as admin user                  # features/secondary/srv_push_package.feature:12
      This scenario ran at: 2024-08-15 14:33:53 +0200
    Given I am authorized for the "Admin" section # features/step_definitions/navigation_steps.rb:401
      This scenario took: 12 seconds

  @under_debugging
  Scenario: Pre-requisite: mgr-push package must be installed on the SLES minion     # features/secondary/srv_push_package.feature:16
      This scenario ran at: 2024-08-15 14:34:05 +0200
Initializing a twopence node for 'sle_minion'.
Host 'sle_minion' is alive with determined hostname uyuni-master-podman-min-suse and FQDN uyuni-master-podman-min-suse.mgr.suse.de
Node: uyuni-master-podman-min-suse, OS Version: 15.5, Family: opensuse-leap
    Given I am on the Systems overview page of this "sle_minion"                     # features/step_definitions/navigation_steps.rb:413
    When I follow "Software" in the content area                                     # features/step_definitions/navigation_steps.rb:299
    And I wait until I see "Upgrade Packages" text                                   # features/step_definitions/navigation_steps.rb:39
    And I follow "Install"                                                           # features/step_definitions/navigation_steps.rb:284
    And I wait until I see "Installable Packages" text                               # features/step_definitions/navigation_steps.rb:39
    And I enter "mgr-push" as the filtered package name                              # features/step_definitions/navigation_steps.rb:846
    And I click on the filter button                                                 # features/step_definitions/navigation_steps.rb:818
    And I check "mgr-push" in the list                                               # features/step_definitions/navigation_steps.rb:924
    And I click on "Install Selected Packages"                                       # features/step_definitions/navigation_steps.rb:256
    And I click on "Confirm"                                                         # features/step_definitions/navigation_steps.rb:256
    Then I should see a "1 package install has been scheduled for" text              # features/step_definitions/navigation_steps.rb:591
    And I wait until event "Package Install/Upgrade scheduled by admin" is completed # features/step_definitions/common_steps.rb:164
      This scenario took: 27 seconds

  Scenario: Push a package with unset vendor through the SLES minion                                                               # features/secondary/srv_push_package.feature:30
      This scenario ran at: 2024-08-15 14:34:32 +0200
    When I copy unset package file on "sle_minion"                                                                                # features/step_definitions/command_steps.rb:1315
    And I push package "/root/subscription-tools-1.0-0.noarch.rpm" into "fake-base-channel-suse-like" channel through "sle_minion" # features/step_definitions/common_steps.rb:516
    Then I should see package "subscription-tools-1.0-0.noarch" in channel "Fake-Base-Channel-SUSE-like"                           # features/step_definitions/common_steps.rb:522
      This scenario took: 252 seconds

  Scenario: Check vendor of package displayed in web UI         # features/secondary/srv_push_package.feature:35
      This scenario ran at: 2024-08-15 14:38:44 +0200
    When I follow the left menu "Software > Channel List > All" # features/step_definitions/navigation_steps.rb:339
    And I follow "Fake-Base-Channel-SUSE-like"                  # features/step_definitions/navigation_steps.rb:284
    And I follow "Packages"                                     # features/step_definitions/navigation_steps.rb:284
    And I follow "subscription-tools-1.0-0.noarch"              # features/step_definitions/navigation_steps.rb:284
    Then I should see a "Vendor:" text                          # features/step_definitions/navigation_steps.rb:591
    And I should see a "Not defined" text                       # features/step_definitions/navigation_steps.rb:591
      This scenario took: 2 seconds

4 scenarios (4 passed)
22 steps (22 passed)
4m53.300s

Yes. We cannot sync Leap in the CI. We tried that last year, and it will be over ~100.00 packages to sync. So not practicable. That is also why we switched back to syncing SLES 15 SP4 in the Uyuni CIs again.


[IOTDB-405] cache results in the client and makes the display look nice.

cache results in the client and makes the display look nice.
https://issues.apache.org/jira/projects/IOTDB/issues/IOTDB-405

My test case is:
SET STORAGE GROUP TO root.turbine;
create timeseries root.turbine.d1.s0 with datatype=DOUBLE, encoding=GORILLA, compression=SNAPPY;
create timeseries root.turbine.d2.s0 with datatype=DOUBLE, encoding=GORILLA, compression=SNAPPY;
insert into root.turbine.d1(time,s0) values(4,4);
select * from root;


✨feat(ui)#10271:UI - Object Storage Service Part-1

Describe your changes :

I worked on #10271 and this PR includes the following things

Listing page for Object Store service
Details page for Object Store service
Support for add/update/delete service

Type of change :

[x] New feature

Frontend Preview (Screenshots) :

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

@chirag-madlani, I have addressed all the comments, please review them.

@ShaileshParmar11, thanks for the review, I will address all the comments in my next patch.


Beam/21742 add warning to risky kafka config

closes #21742

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

 The JVM requires that all non-public interfaces to be in the same package which will prevent the PipelineOptions proxy class to implement all of the interfaces.

gotcha. merging. Thanks John


Changes to not skip block payment

Clean and simple
#283

There are issues about blocked connections of miners?

You see the code, it will block there.

I think maybe this issue is related to miners are disconnected by pool randomly. We will see.

I don't fully understand the purpose of these changes.

Those arrays are circular buffers, I made it bigger to record more old tasks.
Anyway an easiest way to handle this issue (even if it sound strange that this is the issue) is to add in create_block after add_blobk if(res&&miner) {add_queue} and pop the block(and other infos thst you need to remember) in block_thread.

I'll change it to use a queue, I think it's better

@jonano614 now it is even simpler, i'm testing it actually on testnet

it's working

It's interesting that client and server both get POLLHUP but a peer should send FIN afaik to get POLLHUP on the other side.

i'll reopen it if the issue still won't be fixed is i think


Restart tests when the watcher finds changes

Clear and concise description of the problem
Vitest continues running old code, even when I edit the tests to something new. This makes it longer than it needs to be to see results of tests (and especially slower benchmarks) in the browser.
Suggested solution
Vitest should restart tests when their code (or source code they import) is changed on disk.
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

So, current workflow is:

Tests are running
Change source code
Start running tests
Change source code again
Still running tests against previous change
Stop running tests
Start running tests agains previous change

And you want this:

Tests are running
Change source code
Stop running tests
Start running tests agains new code

Yes. And if it’s running tests against the previous version twice, I suppose this is a performance bug rather than just a feature request.

This is implemented as far as I know.


🐛 Allow None as return type for bodiless responses

Fixes #9424
If the return annotation of the route function is exactly "None", return None for the typed annotation. This allows the status code 204 No Content to be used.

I tested this using pip install git+https://github.com/hofrob/fastapi@fix-return-no-content-future-annotations and it fixes my issue in #9723. :+1:

@csbasil I rebased after you approved it.
Are there any plans on merging this PR?

There's an alternative to this on https://github.com/tiangolo/fastapi/pull/5860.

There's an alternative to this on https://github.com/tiangolo/fastapi/pull/5860.

Yes, I thought it's not necessary to get the actual type in this case, since None is a reserved word anyway.
It might be a bit faster to compare the string further up in the stack, but that's probably negligible.
There may be other arguments about using one over the other.

@tiangolo can we get this merged? it will fix this issue 🙏


chore: update AFJ to v0.3.3

Summary of Changes
This PR primarily updates AFJ @aries-framework/core to v0.3.3. As part of this change ProofRecord was renamed to ProofExchangeRecord which requires and update @aries-framework/react-hooks to v0.4.0.
In addition to the new name ProofExchangeRecord the data structure of this object has changed requiring some parts of code dependent on it to be refactored.
Related Issues
Please reference here any issue #'s that are relevant to this PR, or simply enter "N/A" if this PR does not relate to any existing issues.
Pull Request Checklist
Tick all boxes below to demonstrate that you have completed the respective task. If the item does not apply to your this PR check it anyway to make it apparent that there's nothing to do.

[x] All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this);
[x] Updated LICENSE-3RD-PARTY.md for any added dependencies or vendored components;
[x] Updated documentation as needed for changed code and new or modified features;
[x] Added sufficient tests so that overall code coverage is not reduced.

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!
Pro Tip 🤓

Read our contribution guide at least once; it will save you a few review cycles!
Your PR will likely not be reviewed until all the above boxes are checked and all automated tests have passed.

PR template adapted from the Python attrs project.

@amanji When updating I think the data structure for a proof changed - I think. I didn't see "name" any more for the attribute but rather 0_first_name_uuid (for example) so I just parse it out removing the 0 and uuid. I'm going to double check the data structure by logging it and printing it as JSON to make sure.

@amanji I think the data structure for a proof changed. I didn't see the attribute name any more for a requested attribute or predicate but rather I see the format 0_some_attribute_uuid (for example, 0_first_name_uuid). I just parse it out removing the 0 and uuid. I've added a sample below. Also, I don't use the sort credentials fn call any more. I don't recall why we needed it but everything is working fine without it. You can see the changes in core/App/utils/helpers.ts
Here is an example of what requestedAttributes looks like now (requestedPredicates looks similar):
{
  "0_name_uuid": [
    {
      "credentialId": "944b0302-ae00-4bd4-bb21-e52cad6a2f16",
      "timestamp":<PHONE_NUMBER>,
      "revealed": true,
      "credentialInfo": {
        "referent": "944b0302-ae00-4bd4-bb21-e52cad6a2f16",
        "attrs": {
          "timestamp": "1674155922",
          "birthdate_dateint": "19990119",
          "date": "2018-05-28",
          "name": "Alice Smith",
          "degree": "Maths"
        },
        "schema_id": "6R31xMjdiEPAXehPzKpRLK:2:degree schema:87.78.25",
        "cred_def_id": "6R31xMjdiEPAXehPzKpRLK:3:CL:660414:faber.agent.degree_schema",
        "rev_reg_id": "6R31xMjdiEPAXehPzKpRLK:4:6R31xMjdiEPAXehPzKpRLK:3:CL:660414:faber.agent.degree_schema:CL_ACCUM:c20bb8ec-ea26-4946-a6a9-aa060f1a7be7",
        "cred_rev_id": "1"
      },
      "revoked": false
    }
  ],
  "0_date_uuid": [
    {
      "credentialId": "944b0302-ae00-4bd4-bb21-e52cad6a2f16",
      "timestamp":<PHONE_NUMBER>,
      "revealed": true,
      "credentialInfo": {
        "referent": "944b0302-ae00-4bd4-bb21-e52cad6a2f16",
        "attrs": {
          "timestamp": "1674155922",
          "date": "2018-05-28",
          "degree": "Maths",
          "birthdate_dateint": "19990119",
          "name": "Alice Smith"
        },
        "schema_id": "6R31xMjdiEPAXehPzKpRLK:2:degree schema:87.78.25",
        "cred_def_id": "6R31xMjdiEPAXehPzKpRLK:3:CL:660414:faber.agent.degree_schema",
        "rev_reg_id": "6R31xMjdiEPAXehPzKpRLK:4:6R31xMjdiEPAXehPzKpRLK:3:CL:660414:faber.agent.degree_schema:CL_ACCUM:c20bb8ec-ea26-4946-a6a9-aa060f1a7be7",
        "cred_rev_id": "1"
      },
      "revoked": false
    }
  ],
  "0_degree_uuid": [
    {
      "credentialId": "944b0302-ae00-4bd4-bb21-e52cad6a2f16",
      "timestamp":<PHONE_NUMBER>,
      "revealed": true,
      "credentialInfo": {
        "referent": "944b0302-ae00-4bd4-bb21-e52cad6a2f16",
        "attrs": {
          "birthdate_dateint": "19990119",
          "timestamp": "1674155922",
          "date": "2018-05-28",
          "degree": "Maths",
          "name": "Alice Smith"
        },
        "schema_id": "6R31xMjdiEPAXehPzKpRLK:2:degree schema:87.78.25",
        "cred_def_id": "6R31xMjdiEPAXehPzKpRLK:3:CL:660414:faber.agent.degree_schema",
        "rev_reg_id": "6R31xMjdiEPAXehPzKpRLK:4:6R31xMjdiEPAXehPzKpRLK:3:CL:660414:faber.agent.degree_schema:CL_ACCUM:c20bb8ec-ea26-4946-a6a9-aa060f1a7be7",
        "cred_rev_id": "1"
      },
      "revoked": false
    }
  ]
}

I believe we pull the attribute name from the proof request itself and map it through the returned credentials for the proof request from AFJ. The top level names (i.e. the object keys) don't do anything and shouldn't be relied on

@amanji Yup, I grab the data from here const format = await agent.proofs.getFormatData(proof.id) and map it. I think its a new location in the API.

Hi @amanji @jleach
Can you guys help with one question. In that attribute list how can I set the revealed attribute as False if I don't want to show my attribute in the present proof screen in my bifold app? I try to add those line in [core/App/utils/helpers.ts], but couldn't get the required result. So can you just help me out. And also want to is it possible to do it for Attributes list?


SYSNAME - system-defined data type in Azure SQL Server

Hello,
We have in our schema the system-defined data type SYSNAME used in some maintenance tables and procs and while applying the schema.sql with schema apply, for a database works but for another one we receive: Error: analyzing plan: unsupported type *mssql.SysNameType, not sure why.
Is the SYSNAME supported by atlas ?
Thanks.

I replicated this with below:
create schema logtest;
go
CREATE TABLE logtest.[ERR_FNR](
[Key] [int] NULL,
[ColumnName] [sysname] NOT NULL
) ON [PRIMARY]
GO
Applying the schema in DB1, it works:

while in the other DB2 it fails:

Hello @AnielaN994, I was unable to reproduce this issue, can you share more detail about DB2, like what version of it?


Fix Run Command

Thanks for putting this together. Can you fix this line? There's a lot of extra spaces and it's unclear what should be in quotation marks and what shouldn't. Using a codeblock for the actual command that should be entered into the terminal should help clear this up.
Run Fusion 360: "env WINEPREFIX =" / home / steve / .wine "wine C: \ windows \ command \ start.exe / Unix /home/YOUR-USER-NAME/.wine/dosdevices/c: / ProgramData / Microsoft / Windows / Start \ Menu / Programs / Autodesk / Autodesk \ Fusion \ 360.lnk "

Ok. Thank You very much for this information. :-)


More verbose output from yarn start

When running yarn start, there is no output between "Starting development server" and "Compiled successfully!". In the codebase of my large company, this means there is no output for over a minute. I want to debug our slow setup so I want to see what's going on in that minute. Is there any way to set a "verbose" mode that outputs what's going on during that time?
I've included a video of this from a fresh create-react-app for reference:
https://drive.google.com/file/d/1RkVN_O8RAzcNfw-Xb1iZCzdIfGMmgXYx/view

npm build --verbose
yarn --versbose start
this might give out some info

Does not work - we too need to get verbose output here.


Update alpine to 3.16, switch from bzr to breezy, resolve all vulnerabilities

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[x] Build-related changes
[ ] Other, please describe:

The PR fulfills these requirements:

[x] All tests are passing?
[ ] New/updated tests are included?
[ ] If any static assets have been updated, has ui/bindata.go been regenerated?
[ ] Are there doc blocks for functions that I updated/created?

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Vulnerabilities:
The current image has lots of vulnerabilities:

docker scan before upgrade (20 vulnerabilities)
Testing hound...

✗ Low severity vulnerability found in openssl/libcrypto1.1
  Description: Inadequate Encryption Strength
  Info: https://snyk.io/vuln/SNYK-ALPINE311-OPENSSL-1075739
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  and 19 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.1.1j-r0

✗ Medium severity vulnerability found in openssl/libcrypto1.1
  Description: NULL Pointer Dereference
  Info: https://snyk.io/vuln/SNYK-ALPINE311-OPENSSL-1075737
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  and 19 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.1.1j-r0

✗ Medium severity vulnerability found in openssl/libcrypto1.1
  Description: NULL Pointer Dereference
  Info: https://snyk.io/vuln/SNYK-ALPINE311-OPENSSL-1089241
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  and 19 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.1.1k-r0

✗ Medium severity vulnerability found in busybox/busybox
  Description: Out-of-bounds Read
  Info: https://snyk.io/vuln/SNYK-ALPINE311-BUSYBOX-1920721
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From: ca-certificates/ca-certificates@20191127-r2 ><EMAIL_ADDRESS>  and 2 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.31.1-r11

✗ High severity vulnerability found in openssl/libcrypto1.1
  Description: Integer Overflow or Wraparound
  Info: https://snyk.io/vuln/SNYK-ALPINE311-OPENSSL-1075738
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  and 19 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.1.1j-r0

✗ High severity vulnerability found in openssl/libcrypto1.1
  Description: Improper Certificate Validation
  Info: https://snyk.io/vuln/SNYK-ALPINE311-OPENSSL-1089242
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  and 19 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.1.1k-r0

✗ High severity vulnerability found in openssl/libcrypto1.1
  Description: Out-of-bounds Read
  Info: https://snyk.io/vuln/SNYK-ALPINE311-OPENSSL-1569447
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  and 19 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.1.1l-r0

✗ High severity vulnerability found in busybox/busybox
  Description: Improper Handling of Exceptional Conditions
  Info: https://snyk.io/vuln/SNYK-ALPINE311-BUSYBOX-1090152
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From: ca-certificates/ca-certificates@20191127-r2 ><EMAIL_ADDRESS>  and 2 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.31.1-r10

✗ High severity vulnerability found in busybox/busybox
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-ALPINE311-BUSYBOX-1920714
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From: ca-certificates/ca-certificates@20191127-r2 ><EMAIL_ADDRESS>  and 2 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.31.1-r11

✗ High severity vulnerability found in busybox/busybox
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-ALPINE311-BUSYBOX-1920716
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From: ca-certificates/ca-certificates@20191127-r2 ><EMAIL_ADDRESS>  and 2 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.31.1-r11

✗ High severity vulnerability found in busybox/busybox
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-ALPINE311-BUSYBOX-1920723
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From: ca-certificates/ca-certificates@20191127-r2 ><EMAIL_ADDRESS>  and 2 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.31.1-r11

✗ High severity vulnerability found in busybox/busybox
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-ALPINE311-BUSYBOX-1920724
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From: ca-certificates/ca-certificates@20191127-r2 ><EMAIL_ADDRESS>  and 2 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.31.1-r11

✗ High severity vulnerability found in busybox/busybox
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-ALPINE311-BUSYBOX-1920740
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From: ca-certificates/ca-certificates@20191127-r2 ><EMAIL_ADDRESS>  and 2 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.31.1-r11

✗ High severity vulnerability found in busybox/busybox
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-ALPINE311-BUSYBOX-1920741
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From: ca-certificates/ca-certificates@20191127-r2 ><EMAIL_ADDRESS>  and 2 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.31.1-r11

✗ High severity vulnerability found in busybox/busybox
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-ALPINE311-BUSYBOX-1920749
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From: ca-certificates/ca-certificates@20191127-r2 ><EMAIL_ADDRESS>  and 2 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.31.1-r11

✗ High severity vulnerability found in busybox/busybox
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-ALPINE311-BUSYBOX-1920753
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From: ca-certificates/ca-certificates@20191127-r2 ><EMAIL_ADDRESS>  and 2 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.31.1-r11

✗ High severity vulnerability found in busybox/busybox
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-ALPINE311-BUSYBOX-1920756
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From: ca-certificates/ca-certificates@20191127-r2 ><EMAIL_ADDRESS>  and 2 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.31.1-r11

✗ High severity vulnerability found in apk-tools/apk-tools
  Description: Out-of-bounds Read
  Info: https://snyk.io/vuln/SNYK-ALPINE311-APKTOOLS-1246343
  Introduced through<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  Image layer: Introduced by your base image (alpine:3.11.7)
  Fixed in: 2.10.6-r0

✗ Critical severity vulnerability found in openssl/libcrypto1.1
  Description: Buffer Overflow
  Info: https://snyk.io/vuln/SNYK-ALPINE311-OPENSSL-1569451
  Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>ca-certificates/ca-certificates@20191127-r2, <EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>  and 19 more...
  Image layer: 'apk add go git subversion libc-dev mercurial bzr openssh tini'
  Fixed in: 1.1.1l-r0

✗ Critical severity vulnerability found in apk-tools/apk-tools
  Description: Out-of-bounds Read
  Info: https://snyk.io/vuln/SNYK-ALPINE311-APKTOOLS-1534687
  Introduced through<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>  Image layer: Introduced by your base image (alpine:3.11.7)
  Fixed in: 2.10.7-r0

Package manager:   apk
Project name:      docker-image|hound
Docker image:      hound
Platform:          linux/amd64
Base image:        alpine:3.11.7

Tested 52 dependencies for known vulnerabilities, found 20 vulnerabilities.

Base Image     Vulnerabilities  Severity
alpine:3.11.7  20               2 critical, 14 high, 3 medium, 1 low

Recommendations for base image upgrade:

Minor upgrades
Base Image      Vulnerabilities  Severity
alpine:3.12.12  0                0 critical, 0 high, 0 medium, 0 low

Alpine 3.11.7 is no longer supported by the Alpine maintainers. Vulnerability detection may be affected by a lack of security updates.

For more free scans that keep your images secure, sign up to Snyk at https://dockr.ly/3ePqVcp

-------------------------------------------------------

Testing hound...

Package manager:   npm
Target file:       /go/src/github.com/hound-search/hound/package.json
Project name:      hound
Docker image:      hound

✔ Tested hound for known vulnerabilities, no vulnerable paths found.

For more free scans that keep your images secure, sign up to Snyk at https://dockr.ly/3ePqVcp

Tested 2 projects, 1 contained vulnerable paths.

This upgrade handles all vulnerabilities found by Snyk in the container:

`docker scan` after upgrade (0 vulnerabilities)
Testing hound...

Package manager:   apk
Project name:      docker-image|hound
Docker image:      hound
Platform:          linux/amd64
Base image:        alpine:3.16.0

✔ Tested 61 dependencies for known vulnerabilities, no vulnerable paths found.

According to our scan, you are currently using the most secure version of the selected base image

For more free scans that keep your images secure, sign up to Snyk at https://dockr.ly/3ePqVcp

-------------------------------------------------------

Testing hound...

Package manager:   npm
Target file:       /go/src/github.com/hound-search/hound/package.json
Project name:      hound
Docker image:      hound

✔ Tested hound for known vulnerabilities, no vulnerable paths found.

For more free scans that keep your images secure, sign up to Snyk at https://dockr.ly/3ePqVcp

Tested 2 projects, no vulnerable paths were found.

Overview:
This updates the container to a supported version of Alpine. It also drops the patch version hardcoding from the alpine version so that non breaking security fixes will get built in automatically without risking breaking changes.
Switching from package bzr to breezy is a drop in and required by the upgrade. The command path and usage does not change between packages.
This has the added benefit that currently if you try to build the docker image on arm64 you get a gcc error. This PR also fixes that.

okay with the Create docker image check failure as should be able to push from this PR
#13 ERROR: failed to push ghcr.io/hound-search/hound:latest: unexpected status: 403 Forbidden
------
 > exporting to image:
------
ERROR: failed to solve: failed to push ghcr.io/hound-search/hound:latest: unexpected status: 403 Forbidden
Error: buildx failed with: ERROR: failed to solve: failed to push ghcr.io/hound-search/hound:latest: unexpected status: 403 Forbidden


Time Sery Is All You Need

Hey, I am going to tell you a funny thing: Time Sery Is All You Need (to reconstruct the topology)
Remember in HH model, we do some simulations, using 4 non-linear ODEs to get 4 time series $V(t), n(t), m(t), h(t)$?
Now, follow my instructions:

First, only pick $V(t)$, drop all other time series.
Second, choose 2 super-parameters $\tau$ and $n$
Third, save $V(t), V(t-\tau), V(t-2\tau) ... V(t-n\tau)$.

Then, we will get an amazing result: when you plot $V(t), V(t-\tau), V(t-2\tau) ... V(t-n\tau)$ in $n+1$ dimension and then use dimension-reduction technique like PCA to 4D, you can get the same topology as the original ODEs!
For example, below figure is for the case of Lorenz ODES.

My own simulation!
Just use GPT~

这是来自QQ邮箱的假期自动回复邮件。

你好，我是李品洁，已收到您发来的邮件，我会尽快处理，祝好~


Create SPARQLs corresponding to the APIs described in D4.1

All requests created and added to the Hit2Gap core platform


SetAsyncErrorAction fails when setting error object for second time

I'm call endpoint from effect to do some validations, call looks like this.
return this.service.validate()
    .pipe(
    map((response): Action => {
        if (response.hasError) {
        return new SetAsyncErrorAction(FORM_CONTROL, VALIDATION_ID, response.errors)
        }

        return new ClearAsyncErrorAction(FORM_CONTROL, VALIDATION_ID)
    }),
    catchError(error => of(new SetAsyncErrorAction(FORM_CONTROL, VALIDATION_ID, error))),
    startWith(new StartAsyncValidationAction(FORM_CONTROL, VALIDATION_ID))
    )

When network connection is lost (in this example) catchError is called and error is set with no issues. However if I make another call and receive error catchError is called again and app crashes.

Checking for such objects would be rather difficult. The general rule for ngrx is to only use safely serializable objects in actions and the store. Therefore, I won't provide a fix for this.


3.14 support

Since the BeagleBone's 3.14 kernel doesn't include capemgr, PyBBIO will need a new method of dynamic pinmuxing. This could be done through the existing cape-universal (https://github.com/cdsteinkuehler/beaglebone-universal-io), which would also require the user to enable overlays for any peripheral subsystems they want to use.

Check the comments on this particular post : https://plus.google.com/+EliasBakken/posts/Uhejy5jLuv4
panto says patches are coming through. Could stick to capemgr

That's 4.0 though. AFAIK BeagleBone's will still be shipping with 3.14 for now.

Closing this for now as it looks like the next BeagleBone release will have 4.1 instead of 3.14.


修改文档的拼写错误。

What this PR does / why we need it?
修改文档中的拼写错误。
Summary of your change
修改文档中的拼写错误。
Please indicate you've done the following:

[ ] Made sure tests are passing and test coverage is added if needed.
[ ] Made sure commit message follow the rule of Conventional Commits specification.
[ ] Considered the docs impact and opened a new docs issue or PR with docs changes if needed.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.