[ci] Set CI to run on Ubuntu 20.04

Workaround the spatialite issue
https://code.djangoproject.com/ticket/32935

Coverage: 99.795% (-0.0%) from 99.795% when pulling c3fb33a3d9f7c84c73486e1f223e68b8be2acee8 on ci-ubuntu-20.04 into dace7aadf7f3328aabde4279cbacd927ca860b74 on master.


Feature: Send notification when new chapter is published

Add a CRON job twice a day to check if new chapter is published on user's likes

Moved to Linear


input group segmented buttons double border

http://boosted.orange.com/v4-alpha/components/input-group/#segmented-buttons
Double border between action button and dropdown button

Fixed by https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/commit/bb34c619d1b527a26dbc7b013e4d4233a45efd7f


Check for error from ioctl in serial_port

Fixes #406

Can you squash this into 1 commit?

I recommend adding more information to the error message to help figure out why the call fails:
error_msg_ = std::string("Error getting number of available bytes from serial port (") + strerror(errno) + ")";

@malban I was planning to squash on merge.
@elliotjo  Yeah, I can make that change.

Updated with @elliotjo's suggestion and squashed per @malban's request


how display image from database using jquery ajax ? that received from php json encode

hello sorry to ask,but i am dying to know the answer,i want to display image in my bootgrid table from database,and what i know is that i have to use formatters ? but HOW ? that's my question,i got some example of my bootgrid table and side server code "
 var productTable = $('#data').bootgrid({   ajax: true,   rowSelect: true,   post: function()   {    return{     id: "b0df282a-0d67-40e5-8558-c9e93b7befed"    };   },   url: "load_data.php",   formatters: {    "commands": function(column, row)    {     return "<button type='button' class='btn btn-warning btn-xs update' data-row-id='"+row.book_id+"'>Edit</button>" +      "  <button type='button' class='btn btn-danger btn-xs delete' data-row-id='"+row.book_id+"'>Delete</button>";    },   }  });
here is my serverside code :
$query .= "  SELECT    book.data_id,    category.category_name,    book.data_name,    book.data_quotes,   book.image FROM product    INNER JOIN category    ON category.category_id = book.category_id ";
i know that this question is off topics because it's about issues or something like that,but REALLY,i need to know,and here is the thing,i receive the data from my php file in json data type ('json_encode'),that make me in much worse position,soooo,please help me

It is better to fetch Image Path from the database inside json_encode. On the front end, (javascript), render the cell using the imagepath inside an img tag of HTML


Duplicate meshes upon export, and original model is shifted back

Describe the bug
When trying to export the attached project file, the meshes of the three-part barrel and the shell container on the back are duplicated. The copies are resized and do not have the same parent as the original. The original model is also shifted along the y axis, but none of the objects show any change in their actual coordinates
To Reproduce
Steps to reproduce the behaviour:

Open the project file given
Export as gltf (you will see the model shift)
Re-import the exported file (you will see the duplicate meshes)

Expected behaviour
I just want the exported file to represent the model completely, and not have the original model be altered
Screenshots
The original model, notice in the inspector the armature has no translation

After export, the model is shifted. Notice that the inspector still shows no translation

The exported model. The meshes are duplicated and are outside of the armature in the scene tree

.blend file
turret_drone_1_bug.zip
Version

OS: Windows 10
Blender Version 2.92.0

Thank you guys in advance

Also I should point out that there are animations for the barrel meshes. In the exported model, the animations are re-assigned to the duplicated meshes, not the original. So when I use this model, I have to not only delete the duplicated meshes, I also have to re-assign the re-assigned animations

After some experimenting, I've determined that the animation is what's causing the problem. Delete the animations for the afflicted meshes in the NLA editor and you will see that the meshes are not duplicated anymore. The whole model still shifts after export though. Even remaking the meshes does not fix the problemd

Duplicate nodes when animating mesh parented to a bone is #1275.

This seems to be fixed in #1378

Fixed by 69746b2b31eeee080d5dfd3c74f1e02742795ed2


Path Not Found / Output Directory "Dist" Not Found

Environment

Operating System: Darwin
Node Version:     v16.14.2
Nuxt Version:     2.16.0-27358576.777a4b7f
Package Manager<EMAIL_ADDRESS>Builder:          webpack
User Config:      bridge, features, router, loadingIndicator, loading, ssr, target, publicRuntimeConfig, head, plugins, components, modern, render, buildModules, humansTxt, purgeCSS, googleAnalytics, pwa, robots, sitemap, fontawesome, modules, i18n, content, image, tailwindcss, generate, build
Runtime Modules<EMAIL_ADDRESS>8n<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Reproduction

Describe the bug
Hi Folks,
I just wanna share what i'm experiencing an error lately. I tried some deployment on jamstack provider and it's always failed with these error below

and i forgot what community forum i got the answered, but for me it's fixed by creating a new repo (or renaming the repo at least) and try to create a new project on the jamstack provider again.
hope it can helps for you are experiencing this.
Additional context
No response
Logs
No response

yes, I think we can track this at #31.


the training Mel must be 80 channels? I use the other shape, it has no error ,but inference

I use this shape of Mel to train the hifi gan, it has no any error when training. however, when I use the model to inference from tacotron file ,is reminds me it must be 80 channels

RuntimeError: Given groups=1, weight of size [512, 80, 7], expected input[1, 1000, 513] to have 80 channels, but got 1000 channels instead


Fixes for various AttributeArray-related compiler and Doxygen warnings

Signed-off-by: Peter Cucka<EMAIL_ADDRESS>>

@danrbailey I don't seem to be able to add you as a reviewer.  Can you look over these fixes?

Dan, I just build this version of OpenVDB under OSX 10.14.1 and I'm getting a lot of warnings - most of which seem to be related to points. Can you check and see which ones you can address?
Thanks,
Ken
Sorry for the verbose copy/past below but it's exactly indicative of the problem I'd like to address :-D
In file included from unittest/TestPointMove.cc:36:
../openvdb/points/PointMove.h:516:25: warning: 'set' is deprecated [-Wdeprecated-declarations]
targetArray.set(tgtOffset, sourceArray, std::get<2>(it));
^
../openvdb/points/PointMove.h:534:19: note: in instantiation of member function
'openvdb::v6_0::points::point_move_internal::GlobalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >::performMove' requested here
this->performMove(idx, leaf, offsets, moveIndices);
^
../openvdb/tree/LeafManager.h:766:77: note: in instantiation of member function
'openvdb::v6_0::points::point_move_internal::GlobalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >::operator()' requested here
for (typename LeafRange::Iterator it = range.begin(); it; ++it) mLeafOp(*it, it.pos());
^
../openvdb/tree/LeafManager.h:762:58: note: in instantiation of member function
'openvdb::v6_0::tree::LeafManager<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > >
>::LeafTransformer<openvdb::v6_0::points::point_move_internal::GlobalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > > >::operator()' requested here
threaded ? tbb::parallel_for(range, *this) : (*this)(range);
^
../openvdb/tree/LeafManager.h:527:19: note: in instantiation of member function
'openvdb::v6_0::tree::LeafManager<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > >
>::LeafTransformer<openvdb::v6_0::points::point_move_internal::GlobalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > > >::run' requested here
transform.run(this->leafRange(grainSize), threaded);
^
../openvdb/points/PointMove.h:802:27: note: in instantiation of function template specialization
'openvdb::v6_0::tree::LeafManager<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > >
>::foreach<openvdb::v6_0::points::point_move_internal::GlobalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > > >' requested here
targetLeafManager.foreach(globalMoveOp, threaded);
^
../openvdb/points/PointMove.h:823:5: note: in instantiation of function template specialization
'openvdb::v6_0::points::movePoints<openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >, (anonymous namespace)::OffsetDeformer, openvdb::v6_0::points::NullFilter>' requested here
movePoints(points, points.transform(), deformer, filter, objectNotInUse, threaded);
^
unittest/TestPointMove.cc:459:9: note: in instantiation of function template specialization
'openvdb::v6_0::points::movePoints<openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >, (anonymous namespace)::OffsetDeformer, openvdb::v6_0::points::NullFilter>' requested here
movePoints(*points, deformer);
^
../openvdb/points/AttributeArray.h:262:5: note: 'set' has been explicitly marked deprecated here
OPENVDB_DEPRECATED
^
../openvdb/Platform.h:49:49: note: expanded from macro 'OPENVDB_DEPRECATED'
#define OPENVDB_DEPRECATED  attribute ((deprecated))
^
In file included from unittest/TestPointMove.cc:36:
../openvdb/points/PointMove.h:632:25: warning: 'set' is deprecated [-Wdeprecated-declarations]
targetArray.set(tgtOffset, sourceArray, it.second);
^
../openvdb/points/PointMove.h:656:19: note: in instantiation of member function
'openvdb::v6_0::points::point_move_internal::LocalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >::performMove' requested here
this->performMove(idx, sourceOffset, leaf, offsets, moveIndices);
^
../openvdb/tree/LeafManager.h:766:77: note: in instantiation of member function
'openvdb::v6_0::points::point_move_internal::LocalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >::operator()' requested here
for (typename LeafRange::Iterator it = range.begin(); it; ++it) mLeafOp(*it, it.pos());
^
../openvdb/tree/LeafManager.h:762:58: note: in instantiation of member function
'openvdb::v6_0::tree::LeafManager<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > >
>::LeafTransformer<openvdb::v6_0::points::point_move_internal::LocalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > > >::operator()' requested here
threaded ? tbb::parallel_for(range, *this) : (*this)(range);
^
../openvdb/tree/LeafManager.h:527:19: note: in instantiation of member function
'openvdb::v6_0::tree::LeafManager<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > >
>::LeafTransformer<openvdb::v6_0::points::point_move_internal::LocalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > > >::run' requested here
transform.run(this->leafRange(grainSize), threaded);
^
../openvdb/points/PointMove.h:809:27: note: in instantiation of function template specialization
'openvdb::v6_0::tree::LeafManager<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > >
>::foreach<openvdb::v6_0::points::point_move_internal::LocalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > > >' requested here
targetLeafManager.foreach(localMoveOp, threaded);
^
../openvdb/points/PointMove.h:823:5: note: in instantiation of function template specialization
'openvdb::v6_0::points::movePoints<openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >, (anonymous namespace)::OffsetDeformer, openvdb::v6_0::points::NullFilter>' requested here
movePoints(points, points.transform(), deformer, filter, objectNotInUse, threaded);
^
unittest/TestPointMove.cc:459:9: note: in instantiation of function template specialization
'openvdb::v6_0::points::movePoints<openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >, (anonymous namespace)::OffsetDeformer, openvdb::v6_0::points::NullFilter>' requested here
movePoints(*points, deformer);
^
../openvdb/points/AttributeArray.h:262:5: note: 'set' has been explicitly marked deprecated here
OPENVDB_DEPRECATED
^
../openvdb/Platform.h:49:49: note: expanded from macro 'OPENVDB_DEPRECATED'
#define OPENVDB_DEPRECATED  attribute ((deprecated))
^
In file included from unittest/TestPointAdvect.cc:37:
In file included from ../openvdb/points/PointAdvect.h:47:
../openvdb/points/PointMove.h:516:25: warning: 'set' is deprecated [-Wdeprecated-declarations]
targetArray.set(tgtOffset, sourceArray, std::get<2>(it));
^
../openvdb/points/PointMove.h:534:19: note: in instantiation of member function
'openvdb::v6_0::points::point_move_internal::GlobalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >::performMove' requested here
this->performMove(idx, leaf, offsets, moveIndices);
^
../openvdb/tree/LeafManager.h:766:77: note: in instantiation of member function
'openvdb::v6_0::points::point_move_internal::GlobalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >::operator()' requested here
for (typename LeafRange::Iterator it = range.begin(); it; ++it) mLeafOp(*it, it.pos());
^
../openvdb/tree/LeafManager.h:762:58: note: in instantiation of member function
'openvdb::v6_0::tree::LeafManager<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > >
>::LeafTransformer<openvdb::v6_0::points::point_move_internal::GlobalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > > >::operator()' requested here
threaded ? tbb::parallel_for(range, *this) : (*this)(range);
^
../openvdb/tree/LeafManager.h:527:19: note: in instantiation of member function
'openvdb::v6_0::tree::LeafManager<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > >
>::LeafTransformer<openvdb::v6_0::points::point_move_internal::GlobalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > > >::run' requested here
transform.run(this->leafRange(grainSize), threaded);
^
../openvdb/points/PointMove.h:802:27: note: in instantiation of function template specialization
'openvdb::v6_0::tree::LeafManager<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > >
>::foreach<openvdb::v6_0::points::point_move_internal::GlobalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > > >' requested here
targetLeafManager.foreach(globalMoveOp, threaded);
^
../openvdb/points/PointMove.h:823:5: note: (skipping 2 contexts in backtrace; use -ftemplate-backtrace-limit=0 to see all)
movePoints(points, points.transform(), deformer, filter, objectNotInUse, threaded);
^
../openvdb/points/PointAdvect.h:203:13: note: in instantiation of function template specialization
'openvdb::v6_0::points::point_advect_internal::AdvectionOp<openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >,
openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::LeafNode<openvdb::v6_0::math::Vec3, 3>,
4>, 5> > > >, openvdb::v6_0::points::NullFilter, openvdb::v6_0::points::NullFilter>::resolveIntegrationOrder<1, true>' requested here
resolveIntegrationOrder<1, Staggered>(buildCache);
^
../openvdb/points/PointAdvect.h:219:13: note: in instantiation of function template specialization
'openvdb::v6_0::points::point_advect_internal::AdvectionOp<openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >,
openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::LeafNode<openvdb::v6_0::math::Vec3, 3>,
4>, 5> > > >, openvdb::v6_0::points::NullFilter, openvdb::v6_0::points::NullFilter>::resolveStaggered' requested here
resolveStaggered(buildCache);
^
../openvdb/points/PointAdvect.h:147:9: note: in instantiation of member function
'openvdb::v6_0::points::point_advect_internal::AdvectionOp<openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >,
openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::LeafNode<openvdb::v6_0::math::Vec3, 3>,
4>, 5> > > >, openvdb::v6_0::points::NullFilter, openvdb::v6_0::points::NullFilter>::operator()' requested here
(*this)(true);
^
../openvdb/points/PointAdvect.h:264:24: note: in instantiation of member function
'openvdb::v6_0::points::point_advect_internal::AdvectionOp<openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >,
openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::LeafNode<openvdb::v6_0::math::Vec3, 3>,
4>, 5> > > >, openvdb::v6_0::points::NullFilter, openvdb::v6_0::points::NullFilter>::cache' requested here
if (cached)     op.cache();
^
unittest/TestPointAdvect.cc:135:9: note: in instantiation of function template specialization
'openvdb::v6_0::points::advectPoints<openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >,
openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::LeafNode<openvdb::v6_0::math::Vec3, 3>,
4>, 5> > > >, openvdb::v6_0::points::NullFilter, openvdb::v6_0::points::NullFilter>' requested here
advectPoints(*pointsToAdvect, *velocity, integrationOrder, timeStep, steps);
^
../openvdb/points/AttributeArray.h:262:5: note: 'set' has been explicitly marked deprecated here
OPENVDB_DEPRECATED
^
../openvdb/Platform.h:49:49: note: expanded from macro 'OPENVDB_DEPRECATED'
#define OPENVDB_DEPRECATED  attribute ((deprecated))
^
In file included from unittest/TestPointAdvect.cc:37:
In file included from ../openvdb/points/PointAdvect.h:47:
../openvdb/points/PointMove.h:632:25: warning: 'set' is deprecated [-Wdeprecated-declarations]
targetArray.set(tgtOffset, sourceArray, it.second);
^
../openvdb/points/PointMove.h:656:19: note: in instantiation of member function
'openvdb::v6_0::points::point_move_internal::LocalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >::performMove' requested here
this->performMove(idx, sourceOffset, leaf, offsets, moveIndices);
^
../openvdb/tree/LeafManager.h:766:77: note: in instantiation of member function
'openvdb::v6_0::points::point_move_internal::LocalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >::operator()' requested here
for (typename LeafRange::Iterator it = range.begin(); it; ++it) mLeafOp(*it, it.pos());
^
../openvdb/tree/LeafManager.h:762:58: note: in instantiation of member function
'openvdb::v6_0::tree::LeafManager<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > >
>::LeafTransformer<openvdb::v6_0::points::point_move_internal::LocalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > > >::operator()' requested here
threaded ? tbb::parallel_for(range, *this) : (*this)(range);
^
../openvdb/tree/LeafManager.h:527:19: note: in instantiation of member function
'openvdb::v6_0::tree::LeafManager<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > >
>::LeafTransformer<openvdb::v6_0::points::point_move_internal::LocalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > > >::run' requested here
transform.run(this->leafRange(grainSize), threaded);
^
../openvdb/points/PointMove.h:809:27: note: in instantiation of function template specialization
'openvdb::v6_0::tree::LeafManager<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > >
>::foreach<openvdb::v6_0::points::point_move_internal::LocalMovePointsOp<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > > >' requested here
targetLeafManager.foreach(localMoveOp, threaded);
^
../openvdb/points/PointMove.h:823:5: note: (skipping 2 contexts in backtrace; use -ftemplate-backtrace-limit=0 to see all)
movePoints(points, points.transform(), deformer, filter, objectNotInUse, threaded);
^
../openvdb/points/PointAdvect.h:203:13: note: in instantiation of function template specialization
'openvdb::v6_0::points::point_advect_internal::AdvectionOp<openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >,
openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::LeafNode<openvdb::v6_0::math::Vec3, 3>,
4>, 5> > > >, openvdb::v6_0::points::NullFilter, openvdb::v6_0::points::NullFilter>::resolveIntegrationOrder<1, true>' requested here
resolveIntegrationOrder<1, Staggered>(buildCache);
^
../openvdb/points/PointAdvect.h:219:13: note: in instantiation of function template specialization
'openvdb::v6_0::points::point_advect_internal::AdvectionOp<openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >,
openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::LeafNode<openvdb::v6_0::math::Vec3, 3>,
4>, 5> > > >, openvdb::v6_0::points::NullFilter, openvdb::v6_0::points::NullFilter>::resolveStaggered' requested here
resolveStaggered(buildCache);
^
../openvdb/points/PointAdvect.h:147:9: note: in instantiation of member function
'openvdb::v6_0::points::point_advect_internal::AdvectionOp<openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >,
openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::LeafNode<openvdb::v6_0::math::Vec3, 3>,
4>, 5> > > >, openvdb::v6_0::points::NullFilter, openvdb::v6_0::points::NullFilter>::operator()' requested here
(*this)(true);
^
../openvdb/points/PointAdvect.h:264:24: note: in instantiation of member function
'openvdb::v6_0::points::point_advect_internal::AdvectionOp<openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >,
openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::LeafNode<openvdb::v6_0::math::Vec3, 3>,
4>, 5> > > >, openvdb::v6_0::points::NullFilter, openvdb::v6_0::points::NullFilter>::cache' requested here
if (cached)     op.cache();
^
unittest/TestPointAdvect.cc:135:9: note: in instantiation of function template specialization
'openvdb::v6_0::points::advectPoints<openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::points::PointDataLeafNode<openvdb::v6_0::PointIndex<unsigned
int, 1>, 3>, 4>, 5> > > >,
openvdb::v6_0::Grid<openvdb::v6_0::tree::Tree<openvdb::v6_0::tree::RootNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::InternalNode<openvdb::v6_0::tree::LeafNode<openvdb::v6_0::math::Vec3, 3>,
4>, 5> > > >, openvdb::v6_0::points::NullFilter, openvdb::v6_0::points::NullFilter>' requested here
advectPoints(*pointsToAdvect, *velocity, integrationOrder, timeStep, steps);
^
../openvdb/points/AttributeArray.h:262:5: note: 'set' has been explicitly marked deprecated here
OPENVDB_DEPRECATED
^
../openvdb/Platform.h:49:49: note: expanded from macro 'OPENVDB_DEPRECATED'
#define OPENVDB_DEPRECATED  attribute ((deprecated))
^

@kmuseth - I think all of these warnings are related to using "deprecated" core library functionality in our unit tests, which raises an interesting question about what to do in this case. When marking a function "deprecated", I would typically not remove the unit tests that test the functionality which is now marked deprecated (because that functionality is still accessible).
It seems like the best solution might be to include a -Wno-deprecated-declarations compiler flag when just building the unit tests. Other alternative solutions could be - include that flag for compilation, include pragma disables for that warning around the specific functionality that calls into deprecated functions or just to remove any unit tests for deprecated functionality. Thoughts? @pcucka would be good to hear any suggestions you might have on this one too.

The unit tests are our primary means of code coverage testing, so I'm not in favor of disabling any compiler warnings globally for those files.  I'd recommend either using pragmas (as localized as possible) or just removing those tests; to me, "deprecated" is more or less synonymous with "unsupported".


Export mint client from protocol sdk

Current dependencies on/for this PR:

main

PR #365   👈

This stack of pull requests is managed by Graphite.


Add Remark Command based on tutorial

Completed tutorial on adding a new command, we can follow up on this on the upcoming discussion to decide if we want to keep this command.
Currently DO NOT MERGE this branch into master yet.

Codecov Report

Merging #19 (5236a41) into master (5f1ca00) will decrease coverage by 0.04%.
The diff coverage is 75.38%.

@@             Coverage Diff              @@
##             master      #19      +/-   ##
============================================
- Coverage     72.15%   72.11%   -0.05%
- Complexity      399      416      +17
============================================
  Files            70       73       +3
  Lines          1232     1291      +59
  Branches        125      131       +6
============================================
+ Hits            889      931      +42
- Misses          311      326      +15
- Partials         32       34       +2

Impacted Files
Coverage Δ

.../seedu/address/logic/parser/AddressBookParser.java
88.88% <0.00%> (-11.12%)
:arrow_down:

...in/java/seedu/address/logic/parser/ParserUtil.java
89.74% <0.00%> (-7.48%)
:arrow_down:

...eedu/address/logic/parser/RemarkCommandParser.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/PersonCard.java
0.00% <0.00%> (ø)

...c/main/java/seedu/address/model/person/Remark.java
75.00% <75.00%> (ø)

...java/seedu/address/logic/commands/EditCommand.java
97.05% <100.00%> (+0.04%)
:arrow_up:

...va/seedu/address/logic/commands/RemarkCommand.java
100.00% <100.00%> (ø)

...a/seedu/address/logic/parser/AddCommandParser.java
100.00% <100.00%> (ø)

...ain/java/seedu/address/logic/parser/CliSyntax.java
85.71% <100.00%> (+2.38%)
:arrow_up:

...c/main/java/seedu/address/model/person/Person.java
97.82% <100.00%> (+0.20%)
:arrow_up:

... and 3 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Introduce genesis_params.json.

Changes

Add genesis_params.json for setting blockchain, consensus, and network parameters
Deprecate NUM_VALIDATORS
Update scripts, README, tests
Fix broken sharding_test (#194)
Fix some bugs

Examples

For local testing, you can use GENESIS_CONFIGS_DIR=genesis-configs/dev env var and change the values inside the file as needed.
For testnet, you can use one of these (changes are applied to deploy & run scripts):

GENESIS_CONFIGS_DIR=genesis-configs/testnet-dev
GENESIS_CONFIGS_DIR=genesis-configs/testnet-staging
GENESIS_CONFIGS_DIR=genesis-configs/testnet-prod-spring
GENESIS_CONFIGS_DIR=genesis-configs/testnet-prod-summer

Notes

Will need to update the contents of genesis-configs/mainnet/ in the future

@platfowner @minsulee2 Updated the PR as discussed offline. PTAL!

reduced genesis-configs variations, and
enabled env vars to overwrite the genesis_params.json

Thanks for the review! Just checked that it passes both unit & integration tests. Now merging..


fix(#1244): prevent error when toggling native dropdown prop

[ ] Error in console while toggling checkbox in code Playground.

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

npm package (@BUGFIX dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@BUGFIX dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


"Load track as Route": only load track points from a file

(With low priority!)
As discussed in #356, currently not only track-points are loaded, but also rte-points!
As example when a route and a track were stored in the same gpx file (from brouter with "turnInstructionMode=3" !), both track and rte are loaded, this leads to unexpected results.
The function "Load Track as Route" only supports track-points, rte-points should be filtered!
Ess Bee

rte-points should be filtered

My opinion is, that it doesn't make sense to guess a route from the track, when there already is a route in the file. It should just skip the whole process and simply use those route points as end result.
Ideally ask the user what to do, in case they really don't want to use that route.

Hello Norbert,
My only (minor) problem is, that currently bothe the track and the route are loaded, so the tour is loaded twice---
No idea what is better:
the route points are intended for voice-hints, perhaps this is a good basis (or not?) for recalculating the tour...
By track the route points are not "guessed", I think the turf.simplify allgorithm has a mathematic basis?... better or not as the route ? I do not know..
As routes are not used every day, a "filter" should be for me satisfying solution.
But of course, the best solution should be examined...
I will try to start some tests in the next week.
Ess Bee

Hello Norbert,
As promised I started some tests with "load a route", I wil try below to describe the results and my remarks.
It is a long text / complex topic, I am still not sure the need is high enough to start an implementation.
Regards
Ess Bee
I think, two variants of routes should be considered for a "load" in the Brouter-web:
1- the route was created manually
Only few tools creates pure route-files (I only know one under windows)
"Manually created" is a kind of guarranty that only a limited number of route-points are created
The probality that a route point and a junction point coincide is quite null
2- the route was calculated by a router
Example: Brouter with option "turnInstructionMode=3
In this case the track and the route are available (example a gpx file containing the track and a route of the tour with the voice-hints)
The probality that  route points and junction points coincide is very high
Case 1:
Quite nobody uses practically routes, so I think the need is very low...
Anyway this load could be interesting for people who want to change one or more points of the route.
Implementation should be a limited effort, as no "simplify" or workarround for #356 are necessary
(because quite no risk to get trouble as reported in #356)
The use case "enrich a track with turn instructions" is not really of interest here:
Navigation-app generally supports routes as input, further most of them (Osmand, Orux, Locus) can use the Brouter-app for routing (and get the voice-hints of the Brouter)!!!
Example Osmand:  last year I opened an issue fort this feature, but it works fine now:
https://github.com/osmandapp/Osmand/issues/8524
Case 2:
Same issue as reported in #356 (verified during a test)
the workarround as described in #356 (pull #369) can not be used, as the middle of 2 rtept´s is not on the route
AND (without new function) the available track can be loaded (with "Load Track as Route").
I started tests...
But it is not easy to compare the results getted using the track with the results getted using the route.
(see in attachements "afterRTEload.jpg" vs. "afterTRACKload.jpg")
Example (Freiburg_Titisee.gpx)
Using the Route part of the gpx:
57 rtept´s
Simplified WP´s  49
Result: errors in voice-hints (or points outside the tour if worarround foe #356 was applied)
Remark: by testing with the route of a 800 km tour, an unexpected number of route-points remained after turf.simplify:
Input Route(voice): 1.159 rtept´s   ==> 440 after simplify  ????? resulting in an URL of 8 kb. (==> error under Unbutu, Ok under windows..)
Using the Track part of the gpx:
1.158 trkpt´s
Simplified WP´s:  47 trkpt´s
Result: OK when applying the workarround for #356)

rte-points should be filtered

My opinion is, that it doesn't make sense to guess a route from the track, when there already is a route in the file. It should just skip the whole process and simply use those route points as end result.

This is precisely what the Kurviger (and Cruiser) app by the import menu do (free to set) offer.

The (imo) most prefered import selection thereby is.

Display the (trk) track as a very nice usefull overlay reference template.
Use the (rte)route for the routing (re)calculation + add navigation instructions.
By the comfort of the visual track reference template eventually fine tune and add some extra steering Shaping Points.

And then, to crown it all, export and transfer your result as a gpx navigation track that contains both the turnpoints as well as the Shaping and Via Planner points.
https://github.com/nrenner/brouter-web/issues/499
When you later so reimport this gpx navigation track again, you will so immediately get a 100% faithful replica with wich you directly can work further with.
The best choice at (re)import (imo) is to use this navigation track both than as visual passive overlay track display as well as to import this track usable as a route by the integrated planner points, so that if desired, you can directly start working with it to produce a new (re)design if you indeed want to do so.

The passive visible reference track display template is thereby very comfortably helpful to estimate any (un)desired changes.

2 - the route was calculated by a router

The probality that route points and junction points coincide is very high

Creating a route where you are going to place the waypoints where you actually expect the turnpoints near road junctions ? You cannot think of anything more wrong than such route export.  It is asking for trouble to design with this.  The slightest deviation between the route points and the underlying routing data all too often causes very annoying mini track glitches and so annoying false turn instructions.
Rule: The (rte) routes must be qualitative and never should offer routing points at the critical positions where roads converge.

Since it remains a little quiet on this rather "difficult" to realise subject.
Is it possible that the conjunction with the U-turn question is not noticed?
So still this extra comment.
Automatically converting a nice quality imported track.
Wrong false turn instructions are particularly annoying.
For years a theme that I follow in the Locus forums.
Often thought "eureka" now at last  good solution.
After testing every time there appears to be NO solution.
So it is still best to retrace manually using the track template.
Faster and better quality IF you click AFTER the street functions.
Some evolution since 2 years but still no final.

Divide planner points by automatic distance tickmarks on the imported standard track.

The chance that a tickmark falls on the "wrong" road is relatively small, but still there.
A tickmark close to street junctions is allowed, if it is "caught" on the road to be followed.
Even with a comfortable turnlist, you can hardly detect which R/L/Rs are so falsely wrong.

Some Kurviger app experiences.

False turn instructions appear after many tests always accompanied by 'short' trackglitches.
Out and returns trackglitches over the same path, at the returning point so is a 'real' U-turn;
U-turns are, almost always undesirable. An single exception is possible and so should be allowed.
U-turn (GH generates) support was thus requested in the Kurviger (web) and app and is realised.
Be a little bit happier with the annoying errors now, because you can at least detect them through the U-turns.
Find the not planned unusual bad U-turns in the turn list. Thereby you should keep (indicate) the planned U-turns.
Manually correcting harmfull planner points positions solves the false turn instructions issue but the repair still takes too long.

U-turn support requested in BRouter.
With the extra input from dev @afischerdev I think there is now progress.
Please read this (long tread).
https://github.com/abrensch/brouter/issues/436#
Possibly a chance of an Eureka one day ?


Backup failure leaves tablet unusable

I've noticed that sometimes when backing up a vttablet using the google storage APIs return an error, for example:

W1110 01:00:07.587892      13 rpc_server.go:67] TabletManager.Backup(concurrency:4 )(on usc1b-0000001503 from ) error: can't backup files: googleapi: Error 503: Backend Error, backendError

When this happens the backup process doesn't recover gracefully. MySQL isn't restarted and the tablet just stays in a broken state unless we manually go in an reset mysql.
We should recover from these errors more gracefully and start MySQL again

The fix for this is included in PR: https://github.com/youtube/vitess/pull/2263

The fix has been merged.

@rnavarro reports that there may be a regression here.


Can it be used as installer ?

Is it related to this ? https://github.com/NixOS/nixpkgs/issues/21662

This isn't part of the linked RFC, however hopefully it could serve as a useful tool that may be added to the graphical installer.

related https://github.com/nix-gui/nix-gui/issues/77


wazevo: add bit count instructions clz, ctz

This introduces the front-end and back-end for clz, ctz (in terms of rbit+clz).
It originally also introduced popcnt for the front-end, but this requires
VCNT in the backend, which is probably worth its own separate PR.
Contextually, this also introduces a partial implementation for bitRR.
First PR to the wazevo, so I am not entirely sure that the generated
code for the SSA and the backend is correct, let me know if there are errors,
I am really figuring out a lot of stuff, including the framework :)
Signed-off-by: Edoardo Vacchi<EMAIL_ADDRESS>

Although I am not sure about its correctness, this PR may be a good starting point if you haven't dug into wazevo yet since it is really tiny @ncruces

Next time let's add reference to the issue #1496


Minor fixes and adjustments

🆑 Changelog 🆑

Added: Gave the "joingame" command it's respective description.

Changed: Removed some unnecessary lines from SyndicateDiplomat Job.

Changed: Central Command Officials supervisors in their job description.

Fixed: Infinite anchoring bug when deconstructing plastic flaps. (You now melt the flaps back to plastic using a welder)

Signed-off-by: Andre19926<EMAIL_ADDRESS>

You should upstream some of these.


Conflict with vim-fugitive since 3899f848a751b2f8e6d45fa1fe3f723491999f6f

environment

vim:

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 17 2016 07:39:04)
Included patches: 1-1829
Modified by<EMAIL_ADDRESS>Compiled by<EMAIL_ADDRESS>Huge version with GTK2-GNOME GUI.
What is your airline configuration:

let g:airline_powerline_fonts = 1
if !exists('g:airline_symbols')
  let g:airline_symbols = {}
endif
let g:airline_symbols.space = "\ua0"

" Enable the list of buffers
let g:airline#extensions#tabline#enabled = 1

if you are using terminal:

terminal: terminator
$TERM variable: xterm
color configuration (:set t_Co?):
" Colors set

if has('gui_running')
  set background=dark
  colorscheme solarized
  set guifont=DejaVu\ Sans\ Mono\ for\ Powerline\ 9
else
  "colors theme configuration (console)
  if &term == "linux" || &term == "screen.linux"
    set t_Co=8
    colorscheme zenburn
  else
    set t_Co=256
    colorscheme zenburn
  endif
endif

if you are using Neovim:

does it happen in Vim: ???

actual behavior
Using fugitive, I use :Gwrite then :Gcommit to commit my changes.
Since 3899f848a751b2f8e6d45fa1fe3f723491999f6f, after editing the commit message, a new window reading the .git/index of the repository is left open
expected behavior
This window was closing automatically
I explained the issue on vim-fugitive also : https://github.com/tpope/vim-fugitive/issues/648

duplicate of #1317 , actually commit c02d774 should have fixed it. cc @gregorias

Sorry missed that one.
Although, I'm still having this bug with the following commit
vim-airline: c02d774b053f8e364fae46e905d80f0e1cf3f34f
vim-fugitive: b754bc2031f21a532c083dd0d072ba373bbe3a37
It only happens in vim in console mode. I don't see this window left open in GUI mode.

I'll take a look this weekend.

The root cause here is that fugitive:

Makes a system call
Runs commands that cause airline bar to be redrawn. This process makes a system call that returns an error.
Fugitive checks the error status from 1. and gives us this weird window if it is set to an error.

Concretely:

Fugitive calls the system command in plugin/fugitive.vim:23
A few lines below a redraw is called, which causes the airline bar to recompute the VCS information. Since this is an earlier vim, before 8.0, a synchronous system call is used (see airline#util#system).
Fugitive checks v:shell_error for the command done in 1. but it has been overridden by commands done in 2.
Anytime v:shell_error is set, fugitive bugs out like that.

It looks like it would be best to take it to vim-fugitive. It would need to either reorder the error check and redraw operation or fix its behaviour when :shell_error is set. Using vim 8.0 or neovim will also fix this issue.
vim-airline may partially mitigate this by not calling mercurial when has_lawrencium is not set, but this wouldn't guarantee reoccurrence of this error. Any other reason for shell_error would cause this bug to appear.

CC @tpope for comment. please see above comment, it looks like the error checking logic for vim-fugitive needs to be adjusted for async calls.

closing, as this is a fugitive bug.


spreadsheet: Entering marks on chrome issues

On Chrome (Version 69.0.3497.100 (Official Build) (64-bit)) on MacOS (10.13.6), when I enter a number in a field, the number disappears immediately, but the total is correct.  In the image below I have entered a 1 in the bottom left box, so the total on the right is correct, but I only see the 1 when I refresh the page.

I just noticed that if I enter a 0 is does stay even after I delete it.

This was fixed by #3582


Hardcoded assumption for number of NI instances in GOCART2G

The GOCART2G grid component assumes that at least one instance of NI is present:
https://github.com/GEOS-ESM/GOCART/blob/e2245c26e6c4931eadfbb479676a1851cd40b6eb/ESMF/GOCART2G_GridComp/GOCART2G_GridCompMod.F90#L968
This will cause runtime failures in configurations without NI.

@rmontuoro, thanks for bringing this up. Yes, I just opened another issue, related to this (https://github.com/GEOS-ESM/GOCART/issues/222). We need to be able to selectively turn off the GOCART2G components like was eminently doable in GOCART.  This is one example of issues that prevent that.


Updated 2020 syllabus

@NeroArcher
Hi thanks for the PR! Please remember that PRs should be submitted to the staging branch first. Can you pull from staging first and submit a new PR to it? Thanks!


Oddity with Vizier's tables endpoint in a new science use case

Mysterious issue with CDS tables metadata.
tablesV=registry.search(
    servicetype='tap', keywords=['vizier'], includeaux=True
    )[0].service.tables
print(f"Found {len(tablesV)} tables from Vizier")

for s in registry.search(
    servicetype='tap', keywords=['heasarc'], includeaux=True
    ):
    if 'heasarc' in s.ivoid:
        tablesH=s.service.tables
        break
print(f"Found {len(tablesH)} tables from HEASARC")

for t in tablesH:
    print("works for HEASARC")
    break
try:
    for t in tablesV:
        break
except Exception as e:
    print(f"fails for Vizier:{e}")

gives
Found 47595 tables from Vizier
Found 1004 tables from HEASARC
works for HEASARC
fails for Vizier:1:0: no element found

Through the debugger, I see that the failure is coming from the fact that when you have an object that’s the result of asking for a tapservice.service.tables query, when you iterate over the tables, that goes into each pyvo.io.vosi.vodataservice.Table object and calls get_table_file() on the URL, e.g.,
http://tapvizier.u-strasbg.fr/TAPVizieR/tap/tables/J/AJ/144/129/refs
and gets an error 200 in return.  That in turn gets checked but passes through this try and you end up at line 168 with an empty response content and an exception.
 163                  try:
 164                      response.raise_for_status()
 165                  except requests.RequestException as ex:
 166                      raise DALServiceError.from_except(ex, tables_url)
 167
 168  ->                table = vosi.parse_tables(response.raw.read).get_first_table()
 169                  self._cache[name] = table

And I get that 200 error for this table J/AJ/144/129 but not for another I randomly selected,
http://tapvizier.u-strasbg.fr/TAPVizieR/tap/tables/j/aj/156/275/refs
Seem to get the same thing with or without the ‘/refs’ at the end:  a VOTtable that has the references for all the tables.
So a few questions:

Why doesn't response.raise_for_status() not trap the 200 I get from the command-line?
Why is something that is fetched for a specific table returning the same long thing for all tables in the case of Vizier?
And why doesn't this work for Vizier?

I'll poke around a bit more when I have time, but figured I'd ask if anybody knows how this is supposed to work.

This works now using the latest astropy and pyvo. Reopen if you still see this or something similar.


createColorChart.js ignores selected color space

I'm experiencing problem with this script. The color space selected with the main radio button is ignored and the document is created in default (new-file) space. It's possible to still use the script by setting new default and closing/opening illustrator, but it's looks like a bug. Thanks.
Experienced on AI CC 2020 v24 x64, Win 10 x64.

Hi izumitelj.
Thanks for the bug report. I was able to confirm it here as well.
I'll fix it.

Fixed a bug.

Hi sky-chaser, thanx for the fix!
I can confirm that it resolved this bug 🚀


RFID LF (100-150khz) support

Hello,
I'm currently looking into this project, and it seems very intresting, however i'd like to have RFID LF support (especially for reading animal chips that are 134.2khz). I'm currently looking for suitable modules at a decent price that could be integrated on this, and if I manage to find something useful, i'll submit a PR with my modifications.
I am opening this issue to track progress. Also, if anyone already made some research about this i'd be happy to hear what you found and thoughts. @controlpaths , as you designed the board : do you have any insights or advice, or things to be careful about while choosing and modifying the kicad project ?
From what i saw, there are some GPIO pins available on the RP2040, so a UART module would be OK, but a I2C or SPI one would do too.  I noted that both UART from the rp2040 are used (for external USB & esp com for wifi), but from what I understand, that would mean that we can use at most two of those three features at the same times, which is not that a big limit imho : use cases where wifi, external USB as well as lf rfid are used at the same time doesn't seem likely.

Hi! The problem with low frequencies is that the antenna is bigger than for hundreds of MHz. I don't know modules for that frequency, but if you find it, it will need a PCB antenna.


Bug in reduction

I think I have found a bug. I boiled it down to the following MWE:
using LoopVectorization

function f(A)
    N1 = size(A, 1)
    N2 = size(A, 2)
    b = zeros(N1)
    for i = 1:N1
        for j = 1:N2
            b[i] += A[i, j]
        end
    end
    return b
end

function fturbo(A)
    N1 = size(A, 1)
    N2 = size(A, 2)
    b = zeros(N1)
    for i = 1:N1
        @turbo for j = 1:N2
            b[i] += A[i, j]
        end
    end
    return b
end

A = rand(1000, 500)
f1 = f(A)
f2 = fturbo(A)
all(f1 .≈ f2)

returns:
ERROR: LoadError: KeyError: key Symbol("###RHS###3###") not found
Stacktrace:
 [1] getindex(h::Dict{Symbol, LoopVectorization.Operation}, key::Symbol)
   @ Base .\dict.jl:481
 [2] add_reduction!(ls::LoopVectorization.LoopSet, var::Symbol, reduceddeps::Vector{Symbol}, deps::Vector{Symbol}, vparents::Vector{LoopVectorization.Operation}, reduction_ind::Int64, elementbytes::Int64, instr::LoopVectorization.Instruction)
   @ LoopVectorization C:\Users\me\.julia\packages\LoopVectorization\h0HPD\src\parse\add_compute.jl:579
in expression starting at c:\Users\me\test.jl:20

In the MWE, putting the @turbo before the outer loop instead fixes the issue. In my actual application, however, that is not possible because I need to do some more complex computations there.
julia> versioninfo()
Julia Version 1.7.2
Commit bf53498635 (2022-02-06 15:21 UTC)
Platform Info:
  OS: Windows (x86_64-w64-mingw32)
  CPU: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-12.0.1 (ORCJIT, skylake)
Environment:
  JULIA_EDITOR = code
  JULIA_NUM_THREADS = 11

By the way, I believe the code above did work with LoopVectorization roughly half a year ago, but I sadly can't find the exact version I was using then.

The following does not address the root issue, but it may be useful. Would the following modification work for your application? A scalar temporary (which will be more efficient than since it avoids the access/store), and, also support arbitrary indexing.
function fturbo2(A)
    b = zeros(size(A, 1))
    for i = axes(A, 1)
        b′ = zero(eltype(A))
        @turbo for j = axes(A, 2)
            b′ += A[i, j]
        end
        b[i] = b′
    end
    return b
end

I'd suggest this as a better fix:
function fturbo(A)
    N1 = size(A, 1)
    N2 = size(A, 2)
    b = zeros(N1)
    @turbo for i = 1:N1
        for j = 1:N2
            b[i] += A[i, j]
        end
    end
    return b
end

This is basically a duplicate of:
https://github.com/JuliaSIMD/LoopVectorization.jl/issues/331

In the MWE, putting the @turbo before the outer loop instead fixes the issue. In my actual application, however, that is not possible because I need to do some more complex computations there.

That's unfortunate. LV will in general do better the more loops it is allowed to transform and optimize.
@andrewjradcliffe's suggestion is the way to work around this issue.
It's easy to do this manually, but I'd be happy to accept a PR that automates the process.

By the way, I believe the code above did work with LoopVectorization roughly half a year ago, but I sadly can't find the exact version I was using then.

This code never worked.

Would the following modification work for your application?

Thanks for the suggestion! I can modify my original code to make this work.

This is a duplicate of:
https://github.com/JuliaSIMD/LoopVectorization.jl/issues/331

Also thanks for linking the relevant issue! I understand what the problem is now. By the way, I love the package and am looking forward to seeing the rewrite when it's ready :)

This code never worked.

Then my memory is probably failing me. I edited the original post.


Add APIs like df.groupby.apply(udf) or df.apply(udf) that give greater freedom

refer to

polars.map_groups
polars.dataframe.group_by.GroupBy.map_groups

Hi @ztsweet,
Good feature request! One question i have is that can we always expect the output of map_groups to be a single row?


How can I calibrate the Quadruped 12dof (Solo12) ?

How can I calibrate the Quadruped 12dof (Solo12) ?

We use a calibration tool to find the zero position of the legs.
Do you have that tool?
https://github.com/open-dynamic-robot-initiative/open_robot_actuator_hardware/blob/master/mechanics/general/robot_calibration.md#calibration-tool-quadruped-12dof


[Bug]: Removing a Testset that is referenced by an Evaluation Model causes an Internal Server Error

Describe the bug
When you remove a testset that is in use by an evaluation, it causes an internal server error when you go to the evaluation page.
To Reproduce
Steps to reproduce the behavior:

Create any evaluation with any testset of your choice
Navigate to the testset page, and delete the testset that is in use
Navigate to the evaluations page, you'll get: "Internal Server Error"

Expected behavior
A modal should be displayed that tells users that deleting the testset will change the testset to a dummy testset in the evaluation using the testset being deleted.

We have decided to solve this issue by disallowing users to remove testsets used by evaluations.
The expected behavior is show a modal letting the users know that they cannot do this action unless they remove a certain list of evaluations


Consider cores reserved by the system (with focus on Slurm)

Slurm provides feature core specialization: https://slurm.schedmd.com/core_spec.html
Crusher@OLCF started to reserve 8 cores per node by default (link)

Slurm’s core specialization default will change: Slurm --core-spec or -S value will be set to 8. This will provide a symmetric distribution of cores per GCD to the application and will reserve one core per L3 cache region.

Core specialization could be disabled with -S 0

The general philosophy is that we abstract things that are common across schedulers and we provide "pass-through" for those that aren't. So if this is something found in other schedulers, we should probably add it to the API. Otherwise, use spec.attributes.custom_attributes = {'slurm.core-spec': '0'}. And it looks like this isn't documented...

Otherwise, use spec.attributes.custom_attributes = {'slurm.core-spec': '0'}

this looks good, thank you! Thus, this approach would always work, and in case of extending API, it will be just another way to describe this behavior

this approach would always work

Yes, but only for SLURM. So use with caution.


remove unnecessary attributes from BulkCreateIndicesRequest/Response

please add changes and mention the incompatibility to previous versions.

ack


Add git safe.directory support

fix #63

Add support for git config safe.directory
Enabled by default for the directory which is being cloned (imo this should be what users want/expect)
Default is set to $CI_WORKSPACE but can be adjusted via env var PLUGIN_SAFE_DIRECTORY

Works for me with image pats22/plugin-git:2.0.13 (based on plugin-git:2.0.3)
+ git init -b main
Initialized empty Git repository in /woodpecker/src/gitea.<owner>.com/<owner>/<repo>/.git/
+ git config --global safe.directory /woodpecker/src/gitea.<owner>.com/<owner>/<repo>
+ git remote add origin https://gitea.<owner>.com/<owner>/<repo>.git

LGTM but don't know if this will not break anything in local/ssh runners?

LGTM but don't know if this will not break anything in local/ssh runners?

What could potentially break?
Btw, I noticed I am not the only one running into this issue though some might handle it silently: https://codeberg.org/forgejo/forgejo/src/branch/forgejo/.woodpecker/testing-amd64.yml#L53

LGTM but don't know if this will not break anything in local/ssh runners?

What could potentially break?
Btw, I noticed I am not the only one running into this issue though some might handle it silently: https://codeberg.org/forgejo/forgejo/src/branch/forgejo/.woodpecker/testing-amd64.yml#L53

When multiple jobs run on the same host in parallel one will override others safedir.

Maybe this could be changed to set the default safe directory only if it's not already set?

@lafriks if it's not global set there is no race condition or change in the host config

Is there anything left or is this ready to merge? :)

@6543 this will now conflict for parallel jobs on local/ssh instances

it should not ... as git global config change should not create race conditions ...

Afaik safe.directory is an array, so maybe it will be added to it. Otherwise we could change it to use --add

I'm for --add if it exist to be explicite

As this is needed only for local/ssh I think it should be preconfigured to have safedir where all workspace directories will be created. It would be enough to check if safedir is set as parent dir for current workspace than not set it


Error while building simple example

Hi. I'm getting this error when building the simple example on Debian. I have already installed all dependencies listed in the getting started section.
github.com/diamondburned/gotk4/pkg/glib/v2
github.com/diamondburned/gotk4/pkg/glib/v2
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:23451:10: could not determine kind of name for C.GPathBuf
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:13452:10: could not determine kind of name for C.g_bookmark_file_copy
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:45:42: could not determine kind of name for C.g_bookmark_file_get_type
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:15535:10: could not determine kind of name for C.g_date_time_new_from_unix_local_usec
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:15585:10: could not determine kind of name for C.g_date_time_new_from_unix_utc_usec
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:17060:10: could not determine kind of name for C.g_date_time_to_unix_usec
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:48:42: could not determine kind of name for C.g_dir_get_type
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:17177:4: could not determine kind of name for C.g_dir_unref
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:50:42: could not determine kind of name for C.g_hmac_get_type
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:9360:10: could not determine kind of name for C.g_log_writer_syslog
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:23463:2: could not determine kind of name for C.g_path_buf_clear
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:23483:10: could not determine kind of name for C.g_path_buf_clear_to_path
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:23823:10: could not determine kind of name for C.g_path_buf_equal
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:23513:10: could not determine kind of name for C.g_path_buf_free_to_path
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:23537:10: could not determine kind of name for C.g_path_buf_init
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:23567:10: could not determine kind of name for C.g_path_buf_init_from_path
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:23609:10: could not determine kind of name for C.g_path_buf_pop
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:23663:10: could not determine kind of name for C.g_path_buf_push
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:23699:10: could not determine kind of name for C.g_path_buf_set_extension
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:23756:10: could not determine kind of name for C.g_path_buf_set_filename
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:23785:10: could not determine kind of name for C.g_path_buf_to_path
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:60:42: could not determine kind of name for C.g_rand_get_type
/go/pkg/mod/github.com/diamondburned/gotk4/pkg@v0.3.1/glib/v2/glib.go:13088:10: could not determine kind of name for C.g_utf8_truncate_middle

I was using debian in a devcontainer. Once I ran it on the host, the problem is gone


error while downloading from YouTube

(HTTP 403 Forbidden) , you do not have permission to view the webpage.

Sorry, this report is lacking any information that could help us. Please reread our issue reporting guidelines that go into detail of how to make a good bug report.
All I can say is that YouTube downloads work fine for me. I am therefore closing this issue. Please comment or open a new issue with all of the information mentioned in the issue reporting guidelines. Thanks!


Python error: InitDatetime: Could not import datetime C API

Describe the bug
When installing sertit[full], ArcgisPro fails to run some built in function (for example CreateMapTilePackage) with the following error:
Fatal Python error: InitDatetime: Could not import datetime C API
Python runtime state: initialized
ImportError: PyCapsule_Import could not import module "datetime"

Current thread 0x0000349c (most recent call first):
  File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 532 in <lambda>
  File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\management.py", line 17341 in CreateMapTilePackage
  File "D:\environment\test.py", line 9 in <module>

Extension modules: numpy.core._multiarray_umath, numpy.core._multiarray_tests, numpy.linalg._umath_linalg, numpy.fft._pocketfft_internal, numpy.random._common, numpy.random.bit_generator, numpy.random._bounded_integers, numpy.random._mt19937, numpy.random.mtrand, numpy.random._philox, numpy.random._pcg64, numpy.random._sfc64, numpy.random._generator, arcgisscripting._arcgisscripting, gapy._gapy, arcpy_wmx._arcpy_wmx, lxml._elementpath, lxml.etree, lxml.objectify, _brotli, zstandard.backend_c, simplejson._speedups (total: 22)

Code To Reproduce
Environment:

Python version: 3.9, 3.11
sertit-utils version: 1.43.4

Explanation
Installing pyarrow in the env causes this error. Uninstalling it will not solve the issue, you have to build your env from scratch.
The chain depedencies is: sertit -> dask[complete] -> dask-expr -> pyarrow

✅ The dependency to dask[complete] has been removed with version 1.44.1 to resolve this issue.


Build issue of Harmonica Library during CI process

Describe the bug
A clear and concise description of what the bug is.
Since 1 week prior, during CI process it seems to have issues of building harmonica plugin
* What went wrong:
Could not determine the dependencies of task ':shadowJar'.
> Could not resolve all dependencies for configuration ':runtimeClasspath'.
   > Could not find com.improve_future:harmonica:2.0.0.
     Searched in the following locations:
       - file:/root/.m2/repository/com/improve_future/harmonica/2.0.0/harmonica-2.0.0.pom
       - https://repo.maven.apache.org/maven2/com/improve_future/harmonica/2.0.0/harmonica-2.0.0.pom
       - https://jaspersoft.jfrog.io/jaspersoft/third-party-ce-artifacts/com/improve_future/harmonica/2.0.0/harmonica-2.0.0.pom
       - https://jitpack.io/com/improve_future/harmonica/2.0.0/harmonica-2.0.0.pom
       - https://jcenter.bintray.com/com/improve_future/harmonica/2.0.0/harmonica-2.0.0.pom
     Required by:
         project :

When I look up jitpack, it seems
harmonica is stilling depending on the jcenter to build the plugin.
Reference Link

From the Link, you can find the build.log of several recent versions that occur the errors which is

ERROR: Time-out getting container status

To Reproduce
Steps to reproduce the behavior:
During the CI process, it did not occur any error but it is occurring errors during the ./gradlew build -x test
Expected behavior
As I am using ./gradlew build on the CI process, my expected behavior is to be built without any issues.
Environment:
I will share the Environment information from my CI

OS: Ubuntu latest
Database: Postgres (not specifically defined version so it would be the latest too)
JDK/JRE: JDK
Version: 17

Additional context
Possible replacing using jcenter would be the key to resolve?... IDK

FYI,
In Local (which already had built with Harmonica 2.0.0)

./gradlew build -x test -> Success

After changing the version to previous version (1.1.24)

./gradlew build -x test -> Fail

CI Environment

./gradlew build -x test -> Fail

Error messages are the same as the one provided above (Could not find com.improve_future:harmonica:)

https://testfairy.com/blog/jcenter-and-bintray-is-shutting-down-what-to-do/

It might be another link that can be helpful...?


Updated how we refer to key and region

To make it easier and more obvious.

This article no longer exists in the repo. I'll close the PR now.


Write API docmentaion using rswag

Hello Team
In this PR I have documented the house rental API using swagger and RoR by making the following changes

Add rswag and rspec-rails gems to gemfile
Created integration specs to describe and test API
Generate swagger JSON file

To check the rswag generated front-end, find it at http://localhost:3000/api-docs
Feel free to drop and recommendations or changes to improve the quality of the code
Thanks. 👍 .

Hi @NabilHY ,
Congratulations! 🎉
Your project is complete!  There is nothing else to say other than... it's time to merge it 🚀 :
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


fixed sidebar with native scroll

its possible to set the layout to fixed sidebar with admin lte scrollbar ?

Added in commits:
https://github.com/sjefvanleeuwen/blazor-adminlte/commit/e0617d0f716466277b94560415082193154f45b9
https://github.com/sjefvanleeuwen/blazor-adminlte/commit/ca06182a696ccd1f4476aebde15b9734bbb72e25

Available in Release 0.1.0 https://github.com/sjefvanleeuwen/blazor-adminlte/releases/tag/0.1.0
https://www.nuget.org/packages/Blazorized.AdminLte/0.1.0

Dear sjefvanleeuwen,
I meant, how to enable fixed sidebar with the adminlte 3.x scrollbar ?
isn't a system sidebar uses (os-scrollbar)
https://adminlte.io/themes/v3/pages/layout/fixed-sidebar.html


Just format selected lines

Sometimes I want to be able to restrict the formatting just to the selected text.

This feature is supported, just select the code which you want to format, and run the command.


Add "number of accumulations"

Closes #30

Fine for me. The numbers 00000xx are in fact arbitrary, until we publish :)

@Zack-83 & @RainerStosch if you two are now fine with the definition:
A setting datum that specifies the desired number of measurements a spectrometer has to perform to produce an usable spectrum. then we can merge.

But please let me do the merge.

Fine for me.

Your definition sounds more general. Ours is possibly more precise. Feel free to find a suitable compromise :)


css: remove unecessary border

search button already has borders on the right edges.

Thanks. Will deploy this tomorrow.


[SPARK-11771][YARN][TRIVIAL] maximum memory in yarn is controlled by two params have both in error msg

When we exceed the max memory tell users to increase both params instead of just the one.

Test build #46057 has started for PR 9758 at commit 4e530a1.

Test build #46057 has finished for PR 9758 at commit 4e530a1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/46057/
Test PASSed.

Merged build finished. Test PASSed.

Test build #46120 has started for PR 9758 at commit 5e38c39.

Test build #46121 has started for PR 9758 at commit 9125fcf.

Test build #46120 has finished for PR 9758 at commit 5e38c39.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/46120/
Test PASSed.

Test build #46121 has finished for PR 9758 at commit 9125fcf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

OK, merging into master 1.6

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/46121/
Test PASSed.


Sporadic issue - jquery.crs.js not running 80% of the time in a large project

I am making some modification on a large website which downloads a lot of JS file. This may have resulted in sporadic failure. To be explicit, the failure is the "select" tag with class "crs-country" is not populated at all. Digging into the issue, I found that the "_init" function is not being called every time.
I have found a workaround myself, namely to do the following:
1. Comment out: Line 9 to 21 and  Line 469 to Line 474.
2. Comment out: Line 467 ==> "$(_init)" and replace it with "$( document ).ready(_init);"
This seems to have resolved my issue.

Hmm, strange! The second point shouldn't be necessary: those two are identical (See http://api.jquery.com/ready/).
In case you don't want to modify the source code, you can also just run the init() function whenever you want, like on DOM ready. See this section: https://github.com/benkeen/country-region-selector#plain-vanilla-js-example
That allows you to ensure the select fields are always initialized.


Tables readme update

closes #5906
Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[ ] C++ Guidelines
[ ] Doxygen docs
[ ] Unit tests
[ ] No unwanted commits/changes
[ ] Descriptive title/description

[ ] PR is single purpose
[ ] Related issue listed

[ ] Comments in source
[ ] No typos
[ ] Update changelog
[ ] Not work-in-progress
[ ] External references or docs updated
[ ] Self review of PR done
[ ] Any breaking changes?

Missing these link references at the bottom:
[azure_sub]: https://azure.microsoft.com/free/
[azure_cli]: https://docs.microsoft.com/cli/azure


img-viewer is not working with ionic 4

This plugin does not work in Ionic 4 and it should be indicated

i have also problem my angular version 7+
ionic:4.12.0
rxjs:6.3.2
image viewer :2.9.0
(i had try rxjs latest version rxjs and rxjs5.5.2&6.3.3

In dependencies, you can see that requires Angular 5 and RxJs 5. So, is not compatible with Angular 7+. 😭

@Riron Any update on this please?
I am using Angular 7 and ionic 4

dup of #128


Add support for DSE 6.9 and HCD

What this PR does:
Adds support for DSE 6.9 and HCD. Removes DSE 7.x.x support.

DSE 6.9 behaves like DSE 6.8 installations
HCD behaves like Cassandra 4.1 and newer installations

Which issue(s) this PR fixes:
Fixes #659
Fixes #660
Checklist

[ ] Changes manually tested
[x] Automated Tests added/updated
[ ] Documentation added/updated
[x] CHANGELOG.md updated (not required for documentation PRs)
[x] CLA Signed:  DataStax CLA

k8ssandra-client to use in image_config:
k8ssandra-client: "k8ssandra/k8ssandra-client:16a31a04"

That node_replace failure is the only real one - but it's not caused by this PR (and it's a failure in the test code / management-api, it seems pkill doesn't suddenly work in our images anymore).
The process of replacing node still works.


Remove TODO comment from sskdf.c

Fixes #12993
The implementation follows the standards/recommendations specified by https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Cr2.pdf.

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

More info is specified in the issue.

This pull request is ready to merge

Thanks. Merged to master.


feat: expose _RenderingContext.emptyContext

This change makes the static var emptyContext public, so I can use it in my custom renderer.
That's necessary because when creating a custom renderer, It's impossible to run HTML._render since one of its arguments is a _RenderingContext and it doesn't expose initializers.

can I ask what you are implementing?

Sure, I'm implementing a renderer that outputs a more snapshot-friendly html, like this.
I use snapshot testing for 100% of my HTML tests and also HTTP tests that outputs HTML, and the default pretty format isn't very snapshot friendly compared to the example above. For instance, if I have an <input> with a bunch of attributes, and later decide to change only one of the attributes, my snapshot tests would show that only the placeholder line changed.
Example diffs:
With the default pretty print
- <input a="b" b="c" c="l" d="e">
+ <input a="b" b="c" c="I" d="e">

With diff-friendly
<input a="b"
       b="c"
-      c="l"
+      c="I"
       d="e">

is it something that should go in the package?

IDK if it fits the core lib, my use-case is to use this specifically with the swift-snapshot-testing library.

I see, I can tell you that writing a correct and efficient html-formatter is quite tough ; )
I essentially gave up, because the current pretty-printer has bugs and I thought about removing it.
however, I think your use-case is probably the best reason to have something like pretty-print at all, so I would not mind if we add a formatting option to the renderFormatted() that fits your needs. I could see this being useful for many people.
if you are up for it that is, I have no issue with this one change here.

to clarify, the tricky bit is that adding line breaks within "inline" elements (say between  or ) would produce a different output, because the browser interprets a line break as whitespace and adds a blank basically...

to clarify, the tricky bit is that adding line breaks within "inline" elements (say between  or ) would produce a different output, because the browser interprets a line break as whitespace and adds a blank basically...

That's one thing I don't really care for my use-case, which makes the implementation much easier. I don't want the renderer to try doing it in an optimal way that cares about browsers quirks. I'm only using it for snapshot tests, not for rendering on the browser. In fact, I'll never send that HTML to the browser, not sure why anyone would.
What I need is to keep the rendered html as close as possible to what is actually sent, but adding a bunch of predictable break-lines to help with diff reading. If I remove/add spaces to my html to fix some weird rendering, the snapshot will have that extra/removed space in the diff as well, that's the behavior I want.
What do you think? If you agree with that approach, then I already have this like 80% implemented in my fork, I can send another PR soon

I'll merge your change, we can always figure out how to deal with formatting in the core package later.


Fix Python PreCommit dependency compatibility test not run or redundant setup

Followup of #24866
It is found that dataframe compatibility matrix tests are actually not exercised after splitting due to a typo.
Also, sharded precommits set up full version of pyarrow and pytorch compatibility test tasks, but most of them do not have test run. Observed that most of these tests costs >20 min run, where about 10 minutes are contributed by the tox setup for these compability test tasks. This is inefficient. Moved these tasks to be exercised by beam_PreCommit_Python_Coverage which deals with precommit tests exercised by single py version (currently is Py38).
Please add a meaningful description for your change here

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

[ ] 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.

Python_Dataframes precommit now has Task like :sdks:python:test-suites:tox:py38:testPy38pandas-15 running: https://ci-beam.apache.org/job/beam_PreCommit_Python_Dataframes_Commit/225/console
Python_Examples precommit now costs 14 min compared to ~25 min before: https://ci-beam.apache.org/job/beam_PreCommit_Python_Examples_Commit/275/ other jobs also costs ~10 min shorter
Python_Coverage now runs pyarrow and pytorch compatibility matrix tests.
Ready for review now. R: @damccorm

Python_Coverage now becomes slowest task and can costs > 1h when jenkins nodes are full. Not ideal. The dependency tasks can actually run in parallel

https://ci-beam.apache.org/job/beam_PreCommit_PythonDocker_Commit/14639/ actually succeeded. merge for now.


Exception Handling

Does this library use exception handling?
I am using this library in PyCharm and it keep crashing it.
It crashes PyCharm whenever I enter any query that does not get processed by EODHD server.
For example, the following crashes PyCharm cause end date is invalid.
resp = api.get_historical_data("MSFT.US", "1m", "2023-01-01 23:56:00", "2023-02-30 23:59:00")
The following also crashes PyCharm cause it exceed the 120 days limit.
resp = api.get_historical_data("MSFT.US", "1m", "2022-01-30 23:56:00", "2023-01-30 23:59:00")
Any query that does not get processed by your server crashes PyCharm.

Hello, I do not think that it's a good position for PyCharm to crash on any 'unhandled' or 'incorrect' reply, I do belive you should have to ask guys from JetBrains why it happens. As I see you do request the data in datetime, but our documentation provides timestamps for intraday data.

I see the exception handling uses sys.exit(), that's why PyCharm keep shutting down every time a query does not get processed. It shutdown the interpreter.
Can I make suggestion?
Instead of shutting down the interpreter, when an invalid date is entered, perhaps the API can automatically find the nearest valid date? For example, if the last date input is February 30, the API can adjust it to February 28.
Another option, is to allow the end user to retrieve all valid dates on the server for a given stock, before sending the complete query.

All good. I made some changes and its working fine now.
Thank you.


Fix use of Unicode connection string in Python2

If a Unicode connection string is used, hash.update throws an exception about invalid encoding.

This forces everything to UTF8.  Do any databases expect latin1, where extended characters would completely change if we encoded as UTF-8?  I don't want to rush something as important as the connect method.
One problem with setting the metadata encodings on the connection is you have to have a connection first.  I'd like to use a "context" like the SSLContext, etc., since that seems to be becoming a Python standard, and provide a connect method there.  Perhaps pyodbc 5.x

As far as I can see, this is only used internally for connection string hashing and doesn't ever reach any ODBC calls itself.

Ha!  I completely missed that.  Thanks.


Bug fix for AQCU-1021.

Caused by an error in expandYLims that actually shrunk Y-lims.

Coverage remained the same at 97.695% when pulling 024cfae2c5cdd8e17dad3cb69a1f3990fb254c4f on dpattermann-usgs:uvhydroBugFixes into fc90a1647ee9d7174465b91a73b6529633b05233 on USGS-R:master.

@zmoore-usgs You wanna look at this for a sanity check, too? I want to make sure that this makes sense.

Coverage remained the same at 97.695% when pulling 24260e80aa649735a50fcf6dc82a7263ccfab736 on dpattermann-usgs:uvhydroBugFixes into fc90a1647ee9d7174465b91a73b6529633b05233 on USGS-R:master.

Coverage remained the same at 97.695% when pulling 24260e80aa649735a50fcf6dc82a7263ccfab736 on dpattermann-usgs:uvhydroBugFixes into fc90a1647ee9d7174465b91a73b6529633b05233 on USGS-R:master.

Coverage decreased (-0.02%) to 97.671% when pulling e98af30fc310da9e5a6cdc5df4445d2fb183ce6a on dpattermann-usgs:uvhydroBugFixes into fc90a1647ee9d7174465b91a73b6529633b05233 on USGS-R:master.

Coverage decreased (-0.02%) to 97.671% when pulling 3e84853233e5819ff9cd69b04ab31ab4f66ceacd on dpattermann-usgs:uvhydroBugFixes into fc90a1647ee9d7174465b91a73b6529633b05233 on USGS-R:master.

Coverage increased (+0.004%) to 97.699% when pulling 6938a088c3fcd8182d504667e65140e00fca4258 on dpattermann-usgs:uvhydroBugFixes into fc90a1647ee9d7174465b91a73b6529633b05233 on USGS-R:master.


add Returns for  rest api.

Add Returns for  rest apidocs.

Thx

Codecov Report

Merging #262 (2a63006) into master (e953109) will increase coverage by 0.10%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #262      +/-   ##
==========================================
+ Coverage   70.74%   70.85%   +0.10%
==========================================
  Files          41       41
  Lines        7438     7465      +27
==========================================
+ Hits         5262     5289      +27
  Misses       1669     1669
  Partials      507      507

Impacted Files
Coverage Δ

server/rest.go
67.64% <100.00%> (+1.10%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e953109...2a63006. Read the comment docs.


Check filesystem on all found devices in initqueue

Signed-off-by: David Cassany<EMAIL_ADDRESS>

@mudler finally this ended amost as you first implementation 😅 At the end there only a couple of minor changes:

devices detected by lsblk and do not relay on udev links (e.g. /dev/disk/by-partuuid) which could be missing if corrupted and MSDOS vs GPT differ on available identifiers.
It does the check in the main loop so if the script is executed more than once the filesystem check and loop image check are not executed over the same devices again

yeah it is not obvious until you deep dive into it, quite time consuming also to try that out... anyhow , looks good!

yeah it is not obvious until you deep dive into it, quite time consuming also to try that out... anyhow , looks good!

Yes indeed. In fact the current implementation only works for the test cases if all partitions are found in cos-loop-img stage, for which there are no guarantees. Since all partitions are in the same device udev catches all them at once, but if something like COS_PERSISTENT is pointing to another device that appears later than COS_STATE we are screwed, not only for the systemd-fsck, also for the cos-mount-layout.sh script and initramfs stage.
So a good practice I guess it should be keeping all the partitions that are required at boot (initrd stage) into a single device and keep any other persistent device out of the layout config and add them as regular systemd units in initramfs stage. I guess this is not much of a problem for the edge, but for the cloud I think this is a valid concern.

yeah it is not obvious until you deep dive into it, quite time consuming also to try that out... anyhow , looks good!

Yes indeed. In fact the current implementation only works for the test cases if all partitions are found in cos-loop-img stage, for which there are no guarantees. Since all partitions are in the same device udev catches all them at once, but if something like COS_PERSISTENT is pointing to another device that appears later than COS_STATE we are screwed, not only for the systemd-fsck, also for the cos-mount-layout.sh script and initramfs stage.
So a good practice I guess it should be keeping all the partitions that are required at boot (initrd stage) into a single device and keep any other persistent device out of the layout config and add them as regular systemd units in initramfs stage. I guess this is not much of a problem for the edge, but for the cloud I think this is a valid concern.

That would be enough imho to mention in the docs as specific case. It is a fine tuning-based on the derivative scope, we could also provide an example so we don't miss the gained knowledge here


Contribute to Course content

Contribute to Course content

There are conflicts during merge, waiting for resolving conflicts on contributor's side


feat: Add a stream interception to the onDragOver event

The Question：
Calls when an element has been dropped into the grid from outside，The trigger frequency of ondragover events is too high, causing the problem of stuck

The Solution:
ondragover adds interception
The Effect

Please don't commit package.json changes and built files.

Please, keep in mind that inside onDragOver handler end user could  do some actions to affect dnd process, e.g. apply e.dataTransfer.dropEffect, which affects visual look of mouse pointer, ability to dop (e.g. prevents drop if set to 'none') and could be used later in onDrop handler.
If onDragOver is throttled - dropEffect will be applied not immediately and this could produce bugs in end-user applications.
So, in my opinion only re-render of grid layout could be trottled to improve performance, but all DnD-related staff (like call of onDragOver handler etc.) should be handled immediately. In other way - there is very high risk of various DnD bugs for the end users.


missing disabled prop for Select, File and Floating label Components

noticed missing disabled prop for Select, File, and Floating label Components.
can we add it? I think respective native HTML form components support this property

Do you want to add disabled to label as well?
If so I need to remove the label form the Select component and other components.

My usecase is , I have to disable (make read only) some form fields for certain   users.
No need to disable label

outlined option is also missing for  Floating label Component.
I was able to emulate it with standard Input, Label  and Helper Components

<form method="post" on:submit|preventDefault={save}>

  <Input type="text" id="displayName" {inputClass} bind:value="{item.displayName.value}"
			   placeholder="Display Name"/>
  Display Name

  {#if error?.displayName}
  <Helper class={helpClass}>{error.displayName}</Helper>
  {/if}
</form>

I added {...$$restProps} to those components.
Now you should be able to add any props such as disabled, etc.
I close the issue for now.
Please let us know if you have any more.
Thanks.


Inline webworker issue since 2.3.4

Describe the bug
As of vite 2.3.4 (maybe due to https://github.com/vitejs/vite/pull/3468), inline webworkers generate Uncaught SyntaxError: Unexpected token 'export'. This error was not produced in chrome in vite 2.3.3 (see repro link below)
Reproduction
https://github.com/tjk/vite-inline-webworker-issue
System Info
  System:
    OS: Linux 5.10 Ubuntu 20.04.2 LTS (Focal Fossa)
    CPU: (16) x64 11th Gen Intel(R) Core(TM) i9-11900KF @ 3.50GHz
    Memory: 9.61 GB / 12.38 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 12.18.1 - ~/.asdf/installs/nodejs/12.18.1/bin/node
    Yarn: 1.22.5 - ~/.asdf/shims/yarn
    npm: 6.14.5 - ~/.asdf/installs/nodejs/12.18.1/bin/npm
  npmPackages:
    @vitejs/plugin-vue: ^1.2.3 => 1.2.3
    vite: 2.3.4 => 2.3.4

Used package manager: yarn

Relevant links:

https://discord.com/channels/804011606160703521/814182556068085760/856051587273064489
https://github.com/vitejs/vite/pull/2494#discussion_r598314757
https://github.com/vitejs/vite/pull/2494

I've tested the repro in Vite 2.8.6. The issue seems to be fixed now.


Support multiple -join ips

Hi
Is it possible to -join multiple ips?

hey @justinclayton,
would a fleet systemd file, like so: https://gist.github.com/skippy/94645f8442203dc37b5b
help?

hey @justinclayton,
would a fleet systemd file, like so: https://gist.github.com/skippy/94645f8442203dc37b5b
help?

+1. Multiple join IPs are useful to increase failure tolerance. Given just one IP, agent may fail to join the cluster when the target machine is down.

You all know you can do more joins via the API once it's booted, right?
On Sun, Jan 11, 2015 at 9:42 AM, Семён<EMAIL_ADDRESS>wrote:

+1. Multiple join IPs are useful to increase failure tolerance. Given just
one IP, agent may fail to join the cluster when the target machine is down.
—
Reply to this email directly or view it on GitHub
https://github.com/progrium/docker-consul/issues/27#issuecomment-69498583
.

--
Jeff Lindsay
http://progrium.com

@progrium yes, that's how we're solving for this. Each consul server has a sidekick unit file that puts its ip into etcd and then periodically does an explicit join of the others that have already done so using docker exec. There's probably a more elegant solution somewhere, but it works for us.

@progrium, yes, but specifying multiple join ips when starting new agent is just much simpler when there is a fixed list of server agents with static ips. Otherwise, as @justinclayton mentioned, you'll have to use docker exec, which is buggy at the moment.
Anyway, thank you for all the great and inspiring work! =)

:+1:

+1

I would really like this as well, same usecase as above systemd script that takes many ipaddress (some might be dead) and tries to join all of them. a single --join= --join= would be easier than looping until ew find something to join.

:+1:

You can do multiple joins or whatever Consul arguments you like now.


Add SURF EKF land Da scheme to APS2G rose/cylc suite

|    by<EMAIL_ADDRESS>

Issue migrated from trac:121 at 2024-01-31 18:05:29 +1100

<EMAIL_ADDRESS>changed owner from ibc599 to ixd548

<EMAIL_ADDRESS>changed status from new to assigned

<EMAIL_ADDRESS>commented

thanks Imtiaz for discussion.
We are looking at what needs to be changed to allow this to happen.
Robin

<EMAIL_ADDRESS>commented

Test suite is at:
https://accessdev.nci.org.au/trac/browser/roses/a/a/1/1/9
Change-Set is at https://accessdev.nci.org.au/trac/changeset/421/roses

<EMAIL_ADDRESS>commented

This ticket concerns a major enhancement to the APS2G rose/cylc suite. Namely the implementation of a new land surface data assimilation (DA) scheme. Once the changes have been tested, it is expected that this new land DA scheme will become operational in the Bureau's numerical weather prediction system.

<EMAIL_ADDRESS>commented

hi everyone
is this an infrastructure issue or user suite issue ?
If the latter then maybe this ticket system is not suitable ?
Robin

<EMAIL_ADDRESS>commented

Since the rose suites can be browsed using this TRAC, it makes sense that this TRAC system should be used for project management of the rose suites and users be allowed to open tickets relevant to suite development.

<EMAIL_ADDRESS>commented

Milestone Future deleted

<EMAIL_ADDRESS>removed milestone (was Future)

<EMAIL_ADDRESS>changed component from User Interfaces to ACCESS model